Identification (the UNI): standards that apply
The 3 standards listed for identification (the UNI) 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, NS-9.
- Open standards: DataCite Metadata Schema 4.5; Research Organization Registry (ROR); ORCID iD; SoftWare Hash IDentifier (SWHID) v1.2; Decentralized Identifiers (DIDs) v1.0; UN M49 standard country or area codes.
- Data and feeds: ROR REST API v2; DataCite REST API (DOIs); ORCID public API v3.0; Wikidata Query Service.
- Couples with: Registries and the resolver; Data and datasets; Documentation and publication; Naming, marks and intellectual property.
- Nexus Standards
- 5
- NS-1, NS-3, NS-6
- Open standards
- 6
- named, never copied
- Data and feeds
- 4
- listed for reference
- Couplings
- 4
- with other areas
The UNI and the artefact catalogue (grammar v0.2: domain, sector, region and environment segments)
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. |
Risk record UNIs (grammar, legacy crosswalk, allocation authority)
Status proposed · trust, authorisation and assurance; canonical risk data, records and provenance · NXS-STD-ST-000003.
NS-3 states its requirements in sections rather than in a table of rules.
Contextual UNIs (deployments, instances, programme instances)
Status proposed · trust, authorisation and assurance · NXS-STD-ST-000005.
| Rule | Text |
|---|---|
NS9-R1 | Each deployment or programme instance shall have one context record; the concept keeps its own UNI; context.ofUni is required and shall resolve. |
NS9-R2 | Context identifiers shall be allocated by the catalogue for their SCOPE; they shall not be derived from names or typed by hand. |
NS9-R3 | The supported claim level, legal state and conformance evidence of a context are its own; they shall not be inherited from the concept or from another context. |
NS9-R4 | Closing a context shall not delete it: context.validUntil is set and the status becomes WITHDRAWN or SUPERSEDED with supersededBy. |
NS9-R5 | Display names in context shall follow the marks policy; the UNI, not the name, is the key everywhere. |
Questions and answers.
Are these all the rules for identification (the UNI)?
What does a rule identifier such as NS1-R5 denote?
Around identification (the UNI).
Shape the standards for identification (the uni).
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 and use. The Nexus Standards are proposed standards developed through an open process under NS-13 and published for voluntary use; they do not constitute certification, accreditation or regulatory approval, and adoption remains a decision of the Global Standards Council and, in each country, of its National Standards Council. A UNI (Unique Nexus Identifier) identifies an artefact; it does not certify it. Names of standards bodies and their standards belong to their stewards and are used only to identify the documents; no text of an external standard is reproduced here. Nexus Standards is not affiliated with, endorsed by or certified by any standards body named here.
Licences: CC BY 4.0 for standards text, registries, schemas and data; Apache-2.0 for reference code. External standards are cited by name, number and link under their own licences. Third-party data, libraries and fonts keep their own licences: see Third-party notices.