Registries and the resolver: standards that apply
The 2 standards listed for registries and the resolver in the registry, each with its status, UNI (Unique Nexus Identifier) and the rules stated in its text.
- Nexus Standards: NS-1, NS-3, NS-6, NS-7.
- Open standards: DataCite Metadata Schema 4.5; Schema.org; Data Catalog Vocabulary (DCAT) Version 3; FAIR Signposting profile; RFC 8615 Well-Known Uniform Resource Identifiers.
- Data and feeds: DataCite REST API (DOIs); ROR REST API v2; Software Heritage archive API.
- Couples with: Identification (the UNI); Sovereign stack; Indexing and discovery.
- Nexus Standards
- 4
- NS-1, NS-3, NS-6
- Open standards
- 5
- named, never copied
- Data and feeds
- 3
- listed for reference
- Couplings
- 3
- with other areas
UNI na katalogi ya vitu (sarufi v0.2: sehemu za kikoa, sekta, kanda na mazingira)
Status proposed · trust, authorisation and assurance · NXS-STD-ST-000001.
| Rule | Text |
|---|---|
NS1-R1 | One UNI shall identify one artefact concept; versions share the UNI and differ in @VERSION. |
NS1-R2 | UNIs shall be allocated only through a catalogue (mint) or a record allocation authority (NS-3); they shall not be typed by hand. |
NS1-R3 | UNIs shall not be deleted or reused. A withdrawn artefact keeps its record (WITHDRAWN); a replaced one records supersededBy. |
NS1-R4 | Every record shall carry the required metadata; legalState defaults to review-required; claimCeiling stays inside the claim registry. |
NS1-R5 | The UNI shall be embedded in the artefact itself so that machines and people can find the record (section 6). |
NS1-R6 | A regional artefact shall carry REGION; public regional or national use still follows the geographic rules of the marks policy. |
NS1-R7 | Codes are classification and shall not be used as product names. |
NS1-R8 | A new scope, domain, sector or environment code shall meet the allocation rules CA-1 to CA-10 (section 1.1) and shall enter through an NS-13 proposal. |
NS1-R9 | A code shall not be reassigned or deleted; a retired code is deprecated with supersededBy, and identifiers that use it remain valid. |
NS1-R10 | A PROPOSED identifier may be used and shall be shown with its status until the registry change is adopted. |
Kurasa za kutua za kitatuzi, meta tagi za ukurasa, ramani ya tovuti
Status specified · public, client and partner delivery · UNI not yet allocated.
NS-7 is specified elsewhere: SPECIFIED in NS-1 section 1 and NS-16 section 6; implementation status per implementation in the consumers register.
Questions and answers.
Are these all the rules for registries and the resolver?
What does a rule identifier such as NS1-R5 denote?
Around registries and the resolver.
Shape the standards for registries and the resolver.
Governments, regulators, standards bodies, industry, academia and communities are invited to shape the catalogue ahead of its first official release, targeted for 2030: comment on a draft, propose a change, join a working group or host a field exercise.
Hali na matumizi. Nexus Standards ni viwango vinavyopendekezwa vilivyoandaliwa kupitia mchakato wazi chini ya NS-13 na kuchapishwa kwa matumizi ya hiari; si uthibitisho, uidhinishaji wala idhini ya kidhibiti, na upitishaji unabaki kuwa uamuzi wa Baraza la Viwango la Dunia na, katika kila nchi, wa Baraza lake la Viwango la Kitaifa. UNI (Unique Nexus Identifier) hutambua kitu; haikithibitishi. Majina ya vyombo vya viwango na viwango vyao ni mali ya wasimamizi wake na yanatumika tu kutambua nyaraka; hakuna maandishi ya kiwango cha nje yanayonakiliwa hapa. Nexus Standards haihusiani na, haiidhinishwi wala haithibitishwi na chombo chochote cha viwango kilichotajwa hapa.
Leseni: CC BY 4.0 kwa matini ya viwango, rejista, miundo na data; Apache-2.0 kwa msimbo wa marejeo. Viwango vya nje hunukuliwa kwa jina, namba na kiungo chini ya leseni zake vyenyewe. Data, maktaba na fonti za wahusika wengine huhifadhi leseni zake: tazama Notisi za wahusika wengine.