Skip to content
StandardsRegistries and the resolverStandards that apply
Registries en die oplosser

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.

Registries en die oplosser
What this area is built from: the Nexus Standards it applies (marked), the open standards it names and the data and feeds it reads, then the areas it couples with.Source: the Nexus Standards registry: the area record.
  • 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
01NS-1

Die UNI en die artefakkatalogus (grammatika v0.2: domein-, sektor-, streek- en omgewingsegmente)

Status proposed · trust, authorisation and assurance · NXS-STD-ST-000001.

RuleText
NS1-R1One UNI shall identify one artefact concept; versions share the UNI and differ in @VERSION.
NS1-R2UNIs shall be allocated only through a catalogue (mint) or a record allocation authority (NS-3); they shall not be typed by hand.
NS1-R3UNIs shall not be deleted or reused. A withdrawn artefact keeps its record (WITHDRAWN); a replaced one records supersededBy.
NS1-R4Every record shall carry the required metadata; legalState defaults to review-required; claimCeiling stays inside the claim registry.
NS1-R5The UNI shall be embedded in the artefact itself so that machines and people can find the record (section 6).
NS1-R6A regional artefact shall carry REGION; public regional or national use still follows the geographic rules of the marks policy.
NS1-R7Codes are classification and shall not be used as product names.
NS1-R8A 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-R9A code shall not be reassigned or deleted; a retired code is deprecated with supersededBy, and identifiers that use it remain valid.
NS1-R10A PROPOSED identifier may be used and shall be shown with its status until the registry change is adopted.

Read NS-1 in full

02NS-7

Landingsbladsye van die oplosser, bladsy-metamerkers, werfkaart

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.

Read NS-7 in full

03Vrae

Questions and answers.

Are these all the rules for registries and the resolver?
They are the rules stated by the listed standards. The principles of NS-0 bind every standard; clauses specific to the area, where needed, are written under NS-10 and evaluated under NS-11.
What does a rule identifier such as NS1-R5 denote?
The number of the standard and the number of the rule within it. Rule identifiers are stable so that clauses, attestations and publications can cite them.
Standaarde

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.

Status en gebruik. Die Nexus Standards is voorgestelde standaarde wat deur 'n oop proses onder NS-13 ontwikkel en vir vrywillige gebruik gepubliseer word; hulle maak nie sertifisering, akkreditasie of regulatoriese goedkeuring uit nie, en aanvaarding bly 'n besluit van die Wêreldwye Standaarderaad en, in elke land, van sy Nasionale Standaarderaad. 'n UNI (Unique Nexus Identifier) identifiseer 'n artefak; dit sertifiseer dit nie. Name van standaardliggame en hul standaarde behoort aan hul rentmeesters en word slegs gebruik om die dokumente te identifiseer; geen teks van 'n eksterne standaard word hier gereproduseer nie. Nexus Standards is nie geaffilieer met, onderskryf deur of gesertifiseer deur enige standaardliggaam wat hier genoem word nie.

Lisensies: CC BY 4.0 vir standaardteks, registers, skemas en data; Apache-2.0 vir verwysingskode. Eksterne standaarde word volgens naam, nommer en skakel onder hul eie lisensies aangehaal. Derdeparty-data, -biblioteke en -lettertipes behou hul eie lisensies: sien Kennisgewings van derde partye.