-
Currently, the sam spec document (https://samtools.github.io/hts-specs/SAMv1.pdf) has the following for the mandatory SEQ field
10 SEQ String \*|[A-Za-z=.]+ segment SEQuence
![image](https://git…
-
# Context
The Base ZTDF specification includes a yet to be implemented `tdf_spec_version` field. This version field is sufficient in the context of of the OpenTDF ecosystem, but we also want to sup…
-
### Describe the inspiration for your proposal
Open API already has defined several formats that are arguably useful outside of the context of their spec, but I don't think we should add them to our …
-
I updated the basemaps in an attempt to get broader study region coverage, use updated data, and better document the approach ... but they ended up looking quite wrong. Not exactly sure why.
E.g. …
-
The Spec-Up-T tool is updated according to NPM's standard operating procedure, namely via `npm update`.
However, the installation itself (installed via `npx create-spec-up-t my-spec`) can also use …
-
We have a couple of versions of NTT floating around (including in the ML-KEM implementation, several of the Dilithium versions, and standalone in `Common/ntt`.
None of them really look like the ver…
-
### What is the bug?
Setting `reindex.remote.allowlist` in `spec.general.additionalConfig` doesn't seem to apply.
I have been looking through the docs for this specific key but could not find it…
-
Someone pointed out a broken link (see https://github.com/scientific-python/tools.scientific-python.org/pull/63), so apparently the netlify linkchecker doesn't work.
This came up in the specs repo…
-
Being able to specify stroke on outside or inside a closed path could open up a lot of great designs and less hacks like avoiding `paint-order` or clipping/masking svg elements. If the path isn't clos…
-
Spec-Up-T cannot run without `specs.json`. This is not ok since this config file belongs in the install that contains the glossary and that uses Spe-Up-T as an NPM package and not in the package itsel…