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
- Standardên vekirî
- 5
- named, never copied
- Data and feeds
- 3
- listed for reference
- Girêdan
- 3
- with other areas
UNI û kataloga berheman (rêziman v0.2: beşên qad, sektor, herêm û jîngehê)
Status proposed · trust, authorisation and assurance · NXS-STD-ST-000001.
| Rêgez | Nivîs |
|---|---|
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. |
Rûpelên daketinê yên çareserker, etîketên meta yên rûpelê, nexşeya malperê
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.
Pirs û bersiv.
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.
Rewş û bikaranîn. Nexus Standards standardên pêşniyarkirî ne ku bi pêvajoyeke vekirî di bin NS-13 de hatine pêşxistin û ji bo bikaranîna dilxwazî hatine weşandin; ew ne belgename, ne akreditasyon û ne pejirandina rêkxistinê ne, û pejirandin biryara Encûmena Standardên Cîhanî û, li her welatî, ya Encûmena Standardên Neteweyî ya wê dimîne. UNI (Unique Nexus Identifier) berhemekê nas dike; wê belgename nake. Navên desteyên standardan û standardên wan aîdî parêzvanên wan in û tenê ji bo naskirina belgeyan têne bikaranîn; tu nivîsa standardeke derve li vir nayê dubarekirin. Nexus Standards bi tu desteya standardan a li vir hatiye binavkirin ve ne girêdayî ye, ji aliyê wê ve nayê piştgirîkirin û belgename nekiriye.
Lîsans: CC BY 4.0 ji bo nivîsa standardan, tomargeh, şema û daneyan; Apache-2.0 ji bo koda referansê. Standardên derve bi nav, hejmar û girêdanê di bin lîsansên xwe de têne jêgirtin. Dane, pirtûkxane û fontên aliyê sêyem lîsansên xwe diparêzin: binêre Agahdariyên aliyê sêyem.