Skip to content
StandaardeGrondslae en beheerGrondslae
Area · proposed

The UNI and the artefact catalogue

Explains the UNI (Unique Nexus Identifier, NS-1): the grammar NXS-SCOPE-CAT[-REGION]-SERIAL[@VERSION], allocation only through the catalogue command-line tool, never deleted or reused, embedded in the artefact itself and resolvable at /uni/<uni>; and how record UNIs (NS-3) and contextual UNIs (NS-9) extend it. A UNI identifies and resolves an artefact; it does not certify it or authorise its use. Each artefact of the area carries a UNI (Unique Nexus Identifier).

The UNI and the artefact catalogue
What this area is built from: the Nexus Standards it applies, the open standards it names and the data and feeds it reads, then the areas its record couples it with (marked).Source: the Nexus Standards registry: the area record.
  • Nexus Standards: NS-1, NS-3, NS-7, NS-9.
  • Open standards: DataCite Metadata Schema 4.5; RFC 8141 Uniform Resource Names (URNs); SoftWare Hash IDentifier (SWHID) specification; Schema.org vocabulary; Data Catalog Vocabulary (DCAT) Version 3; DOI Handbook (the DOI system, standardised as ISO 26324, named only).
  • Data and feeds: DataCite REST API (DOI metadata for crosswalk and harvest tests); ROR data dump (organisation identifiers for publisher and creator fields); ORCID public data file.
  • Couples with: Conformance programme; Licensing and intellectual property; How a standard is made; Data and evidence.
Nexus Standards
4
NS-1, NS-3, NS-7
Open standards
6
named, never copied
Data and feeds
3
listed for reference
Couplings
4
with other areas
UNI
requested · allocation in progress
Status
Proposednot yet in the catalogue
Last reviewed
area profile
Cite this page

Nexus Standards (2026). The UNI and the artefact catalogue: area brief, Foundations and Governance programme. Proposed. https://nexustandards.com/foundations/the-uni/. Last reviewed 17 October 2026.

Download the profile

Files include the credits and the licence statement and are generated in the browser; no data is transmitted. Downloads require JavaScript.

02Omvang

Scope and boundaries

An area of the Foundations and Governance programme (foundations). The area profile sets out 5 matters in scope and 3 matters addressed by other areas.

In scope 5

  • UNI grammar, scopes, categories and the region segment (ISO 3166-1 alpha-3 or UN M49)
  • Allocation, versioning, supersession and withdrawal rules (NS1-R1 to NS1-R7)
  • Resolver behaviour, landing pages, JSON by content negotiation and the X-Nexus-UNI header (NS-7)
  • Crosswalks to DOI, ORCID, ROR, SWHID, Schema.org, DataCite and CodeMeta
  • Embedding rules for files, documents, datasets, figures and web pages

Out of scope 3

  • Minting DOIs or acting as a DOI registration agency
  • Trademark or brand use of codes; a scope code is not a product name
  • Any statement that a resolved record is true, approved or fit for a purpose

Jurisdictions Application in each jurisdiction is a national decision, taken by the National Standards Council (NSC) with the competent national authorities.

03Standards architecture

Foundation, referenced and implementing layers

The standards architecture of this context, from the foundation standards to the open standards referenced (grouped by type of relation) and the services and data sources that build on them.

The interactive view requires JavaScript; the sections below present the same records.

04Proses

The process in operation

A producer describes an artefact; its context codes are checked against the registries; the catalogue mints the UNI (Unique Nexus Identifier) and keeps the record; the UNI is embedded in the artefact and resolves to its landing page; versions share the UNI, and a withdrawn or replaced artefact keeps its record. 8 operations in 6 phases, built from the area profile: the rows carry its own data sources, indicators, open standards, couplings and, where listed, hazards, and each operation names the rules it implements (10).

Prosesverkenner · Standards · kodifiseer en korrigeer

Lewensiklus van 'n standaard

17 stappe6 fases

Standards · kodifiseer en korrigeer

Lewensiklus van 'n standaard

Lewensiklus van 'n standaard · NS-13-spoor · Bydraekanale · IETF-spoor · W3C-spoor · OGC-spoor · OASIS-spoor · ISO- en IEC-fases · Konformiteit · Rekordlewensiklus · Roetering · Monitering.

Siklusbevindings word veranderingsvoorstelle, die Wêreldwye Standaarderaad aanvaar ná 'n openbare laaste oproep, en elke land besluit oor sy eie aanvaarding.

  1. 01 Lei sendings

    1. 01Route missions to standards and profilesStep · Nexus StandardsNexus Standards routes each candidate mission to the standards and profiles that apply.
  2. 02 Profiele en ooreenstemming

    1. 02Stel sendingprofiele saamStap · Nexus StandardsNexus Standards stel sendingprofiele saam en teken enige nasionale aanvaarding aan waarvan die sendings afhang.
    2. 03Valideer bou-uitsette teen die profieleStap · Nexus StandardsNexus Standards valideer bou-uitsette teen die saamgestelde profiele en teken die bewyse aan.
    3. 04Moniteer konformiteit en teken verseëlde bewyse aanStap · Nexus StandardsGedurende die Aksieweek monitor Nexus Standards konformiteit en teken afwykings aan.
  3. 03 Voorstelle en beoordeling

    1. 05Afwykings en regstellings word veranderingsvoorstelleStap · Nexus StandardsAfwykings word veranderingsvoorstelle, en die regstelling word as 'n verandering aan die bewyse aangeteken.
    2. 06Siklusbevindings word veranderingsvoorstelleStap · Nexus StandardsBevindings uit 'n siklus word veranderingsvoorstelle: metode- en korreksiebevindings uit Verslae (F06) en dokketitems uit Nexus…
    3. 07Stel op en hersien in die openbaarStap · Komitees en werkgroepeTegniese komitees en werkgroepe stel die standaarde op en hersien dit in die oop proses van NS-13.
    4. 08Beoordeel met die oog op 'n raadsbesluitStap · Nexus StandardsNexus Standards beweeg veranderingsvoorstelle deur beoordeling met die oog op 'n raadsbesluit.
  4. 04 Raadsbesluit

    1. 09Openbare laaste oproepStap · Global Standards CouncilDie Global Standards Council aanvaar by 'n tweederdemeerderheid ná 'n laaste oproep van negentig dae.
    2. 10Wêreldwye aanvaarding van 'n standaardBesluit · Global Standards CouncilDie Wêreldwye Standaarderaad besluit oor die aanvaarding van elke standaard ná 'n openbare laaste oproep.
  5. 05 Publiseer en identifiseer

    1. 11Assign a UNI and publishStep · Secretariat (GCRI Canada)Nexus Standards assigns UNIs and deposits publications under the publisher’s process.
    2. 12'n UNI identifiseer en sertifiseer nooit nieRekord · Nexus StandardsElke objek van die programjaar dra een identifiseerder, 'n UNI onder NS-1, sodat dit aangehaal, geweergaweer en opgelos kan word.
    3. 13Publiseer die jaar se aanvaarde veranderingeStap · Nexus StandardsBy hernuwing publiseer Nexus Standards die jaar se aanvaarde veranderinge en die nasionale aanvaardingstatus.
  6. 06 Nasionale aanvaarding en toepassing

    1. 14Nasionale aanvaarding deur die Nasionale StandaarderaadBesluit · Nasionale StandaarderaadElke land se Nasionale Standaarderaad besluit oor nasionale aanvaarding: aanvaar soos dit is, aanvaar met 'n profiel (NS-16), pas aan, of verwys slegs.
    2. 15Aangenome standaarde bereik kursusse en uitgawesStap · Nexus StandardsElke aangenome standaard of profiel word 'n kursusmodule by Risk Academy (F09), en standaarde word in Reports-uitgawes (R1) toegepas.
    3. 16Aanvaarding is finaal vir elke jurisdiksieStandaard · Nasionale StandaarderaadAanvaarding is finaal vir elke jurisdiksie, en die GSC het geen veto oor 'n nasionale besluit nie. Geen globale liggaam hou 'n veto nie.
    4. 17Nasionale aanvaardingsrekordsRekord · Nexus StandardsSaamgestelde missieprofiele en nasionale aanvaardingsrekords gaan na die Foundry by gereedheidsvoorbereiding (F08).

Nexus Standards · Nexus Standards (institution) · National Standards CouncilAn outline of the designed programme cycle, not a record of operation: no cycle has run and every programme is at service level R0. Every Nexus Standard is at the PROPOSED stage and nexustandards.com governs the text and status of each one. A UNI identifies and never certifies; a validator report is evidence for review, not a conformance claim.

The operations, as a table
Process · the UNI from allocation to resolution (NS-1)8 operations · 6 phases
StepPhaseOperationWhoDecision ruleRecordImplements
01DescriptionDescribe artefact (start). The producer states what the artefact is, which scope publishes it, its category, and only the domain, sector, region and environment segments that are true of all of it.the producer: a person, an institution or an agent under a recorded mandateone UNI per artefact concept; codes classify, they never name a producta draft entry: title, scope, category and the context segments that are true of the artefactNS1-R1, NS1-R6, NS1-R7
02CodesCheck codes (gate). Scope, domain, sector and environment codes are three-letter registry codes; regions are ISO 3166-1 alpha-3 or UN M49. A missing code is proposed, never invented.the catalogue validatorevery segment is a registry code meeting CA-1 to CA-10; a new code enters through an NS-13 proposal and may be used, with its status shown, until adopteda validation result for every segmentNS1-R8, NS1-R10
03AllocationMint the UNI (step). The catalogue returns the next serial for the scope, category and context segments. The serial is never reused.the catalogue of the scopeUNIs are allocated only through the catalogue; never typed by handa UNI with a six-digit serial for the full prefixNS1-R2
04AllocationCatalogue record (record). One record per UNI says what the artefact is, who made and publishes it, what rights apply and where it lives.the catalogueevery record carries the required metadata; the legal state defaults to review-requiredthe record: title, scope, category, status, creators, publisher, date, rights, legal state, locationsNS1-R4
05EmbeddingEmbed the UNI (step). Source files carry a header line, documents front matter, datasets a sidecar or metadata key, figures a caption suffix, web pages a meta tag and APIs the X-Nexus-UNI header.the producer, on each surfacethe UNI is embedded in the artefact itself so that machines and people find the record (section 6)a header line, front matter, sidecar, caption suffix, meta tag or response headerNS1-R5
06ResolusieResolve the UNI (record). The resolver path returns the record; the URN form urn:nexus:uni:<UNI> and the citation forms of NS-2 point to the same record.the resolver (NS-7)a UNI identifies and resolves; it never certifiesa landing page for people and JSON for machines at /uni/<UNI>NS1-R5
07ResolusieNew version (step). A revision keeps the identifier of the concept; citations of a state cite the version.the producerversions share the UNI and differ in @VERSIONthe same UNI with a new @VERSIONNS1-R1
08RetirementWithdraw or replace (end). A withdrawn artefact keeps its record and identifier; a replaced one points to its successor, and identifiers that use a retired code stay valid.the publisher of recordUNIs are never deleted or reused; a retired code keeps its entrythe record kept with status WITHDRAWN, or with supersededByNS1-R3, NS1-R9

Table.Operations in walking order; each row names the phase, the operation, its actor, its decision rule, the record it leaves and the rule identifiers it implements. The table shows the process as specified; it does not report the status of any standard, proposal or record. Sources: DataCite Metadata Schema 4.5 · RFC 8141 Uniform Resource Names (URNs) · NS-1: The UNI and the artefact catalogue · NS-3: Risk record UNIs.

05Sistemiese koppelings

Sistemiese koppelings

4 couplings link this area to other areas and programmes, each with the mechanism of the link.

  1. Conformance programmeFoundations and GovernanceEvery Implementation Conformance Statement and attestation is an AT record with its own UNI, so the conformance register is a query over the catalogue rather than a separate list.
  2. Licensing and intellectual propertyFoundations and GovernanceCatalogue records are released as CC0 1.0 metadata so that DataCite, Schema.org and STAC exports can be harvested without attribution friction, while the artefacts keep their own licences.
  3. How a standard is madeFoundations and GovernanceDrafts, proposals, last-call comments and authority decisions each carry a UNI, which gives the standards track a permanent, citable audit trail.
  4. Data and EvidenceData and EvidenceThe Data and Evidence programme profiles the record kinds (observation, source release, indicator, boundary) whose UNIs are minted under NS-3 by the governed data service.
06System model

How a shock travels through this system

A system model of this area built from the registry: 5 systems, 4 sectors, 8 controls, 3 feeds, 2 indicators. Select the components to include, choose an initiating hazard and run the scenario. Stress propagates through the hazard relations of the Nexus Hazard Standard (NHS-1), the exposure of each system, the recorded couplings and the sectors that carry the loss; adopted standards dampen transmission and live data sources support detection. All parameters are stated assumptions that the reader can adjust; results are illustrative scenario outputs for exercises and training, not forecasts or risk assessments.

Controls

  • NS-1Die UNI en die artefakkatalogus (grammatika v0.2: domein-, sektor-, streek- en omgewingsegmente)
  • NS-3 Risikorekord-UNI's (grammatika, oorerflike kruisverwysing, toewysingsgesag)
  • NS-7 Landingsbladsye van die oplosser, bladsy-metamerkers, werfkaart
  • NS-9 Kontekstuele UNI's (ontplooiings, instansies, programinstansies)
  • NRS-A5 Ingeboude lisensiëring en regte
  • NRS-C4 Risikodatamodel, identifiseerders en uitruiling
  • NRS-A3 Agentkoppelvlak na die standaarde
  • NRS-U16Universe-platformprofiel: Institutional Funds Nexus

Observation

  • DataCite REST API (DOI metadata for crosswalk and harvest tests) (listed for reference)
  • ROR data dump (organisation identifiers for publisher and creator fields) (listed for reference)
  • ORCID public data file (listed for reference)
  • Metadata is identified by a persistent identifier
  • Metadata is accessed through standardised protocol
07Standaarde

Standards that apply

The area profile lists 4 Nexus Standards. Each is a proposed standard under development.

  1. 01

    NS-1 · The UNI and the artefact catalogue (grammar v0.2: domain, sector, region and environment segments)

    Status: proposed · 10 requirements stated. Read NS-1.

  2. 02

    NS-3 · Risk record UNIs (grammar, legacy crosswalk, allocation authority)

    Status: proposed · 0 requirements stated. Read NS-3.

  3. 03

    NS-7 · Resolver landing pages, page meta tags, sitemap

    Status: in progress · 0 requirements stated. Read NS-7.

  4. 04

    NS-9 · Contextual UNIs (deployments, instances, programme instances)

    Status: proposed · 5 requirements stated. Read NS-9.

08Werkgroep

Working group charter

A proposed charter for this area, open to institutions and experts.

Omvang

Maintain NS-1, NS-3 and NS-9, the resolver behaviour (NS-7) and the crosswalks to other persistent identifier systems.

Institutions and experts are invited to charter this working group under NS-13 by filing a public change record. National Working Groups (NWGs) contribute national inputs and field exercises through their National Nexus Consortium (NNC).

Deliverables · 3
  1. NS-1 edition with a conformance class per embedding surface
  2. Crosswalk tables UNI to DataCite, Schema.org, CodeMeta and STAC with validator runs
  3. Resolver test suite (HTML, JSON, headers, sitemap) under Apache-2.0
Liaison targets · 3
  • DataCite (information exchange on metadata crosswalks sought) liaison sought
  • Research Organization Registry (ROR) community (information exchange sought) liaison sought
  • Software Heritage (SWHID crosswalk consultation sought) liaison sought
11Research questions

Open research questions

3 questions identified as priorities for the working group.

  1. How a regional segment should behave when a boundary changes or a country code is retired, without breaking the never-reuse rule.
  2. Whether contextual UNIs for deployments disclose sensitive infrastructure detail when published, and which fields require restricted handling.
  3. How to deduplicate concepts that already hold a DOI or SWHID so that one artefact does not acquire competing primary identifiers.
12Gereedheid

Evidence, recognition and capital pathways

What each institution of the ecosystem draws from this area: The Global Centre for Risk and Innovation (GCRI Canada), as Secretariat, for evidence; The Global Risks Forum (GRF) for recognition; and The Global Risks Alliance (GRA) for capital.

Evidence pathway

GCRI Canada

GCRI Canada decides under its own rules which identified records it accepts as evidence; a resolvable UNI makes a record traceable but is not an acceptance.

Read the evidence pathway

Erkenningsroete

Die Global Risks Forum (GRF)

The Global Risks Forum (GRF) may use UNIs to reference contributions in its own processes and decides recognition independently of whether a record carries one.

Read the recognition pathway

Kapitaalroete

Die Global Risks Alliance (GRA)

The Global Risks Alliance (GRA) decides capital readiness under its own criteria; UNIs only let its reviewers trace an evidence chain to source records.

Read the capital pathway

Each institution determines under its own rules what it accepts as evidence; a pathway reading is neither an approval nor investment advice.

13Teikengroepe

Intended users

The area profile identifies 4 user communities.

  1. developers and integrators
  2. data stewards
  3. librarians and repository managers
  4. editors of documents and reports
14Restricted standards

Restricted compatibility profiles

Standards whose text is not openly available are named and linked only. Any compatibility profile is kept on protected pages until an arrangement with the issuing body is in place.

The working group may identify restricted standards relevant to this area; they are listed here by name and link.

15Data sources

Data sources

3 data sources named in the area profile, each with provider, licence, update frequency and delivery path.

Data sources

Data sources are listed for reference; live data is displayed once licence review is complete.

Lewendig
0
on completion of licence review
Listed in the data register
0
licence terms recorded
Proposed for the register
3
licence terms to be recorded
Delivery
0 governed service · 0 plugin · 1 browser · 2 snapshot · 0 listed for reference
proposed paths in order of preference: governed data service, plugin, direct browser read, build-time snapshot; sources whose terms do not permit reuse are listed for reference only
16Aanwysers

Aanwysers

The area profile names 2 indicators, each with its framework and code.

17Hazards and sectors

Hazards, threats and sectors concerned

Hazards and threats 0

This area draws on the hazards of the areas it is coupled with.

Sektore 0

This area serves all sectors through the areas it is coupled with.

18Bronne

Bronne

4 references from peer-reviewed and official publications cited in the area profile, linked at the publishers’ own sites.

  1. peer-reviewedThe FAIR Guiding Principles for scientific data management and stewardshipScientific Data · 2016
  2. officialFAIR Data Maturity Model: specification and guidelinesResearch Data Alliance · 2020
  3. standardDataCite Metadata Schema 4.5DataCite · 2024
  4. standardRFC 8141: Uniform Resource Names (URNs)IETF / RFC Editor · 2017
19Research hub

Recent research on this area

Recent peer-reviewed articles, preprints, datasets and reports on the subject of this area, retrieved at the time of reading from open scholarly metadata services (OpenAlex, Crossref, DataCite, Zenodo, arXiv, Europe PMC, OpenAIRE Graph) with search terms composed from the registry. Each work is listed with its authors, venue, year, type, open-access status and licence, and links to its DOI or landing page. Sources not yet enabled for live display on this site are listed for reference and are not queried.

Search termspersistent identifier; persistent identifiers; digital object identifier; PID infrastructure; DataCite Metadata Schema; RFC 8141 Uniform Resource NamesDerived from the title and scope of the area, the NHS-1 hazards it names and the open standards it lists.

  • OpenAlexlisted for reference; not queried
  • Crossreflisted for reference; not queried
  • DataCitelisted for reference; not queried
  • Zenodolisted for reference; not queried
  • arXivlisted for reference; not queried
  • Europe PMClisted for reference; not queried
  • OpenAIRE Graphlisted for reference; not queried

No source is enabled for live display on this site yet: the sources are listed for reference and none is queried. Once the publisher of record enables a source after its terms are reviewed, recent works are listed here. Metadata and links only: title, authors, venue, year, type, open-access status and licence as each source records them; works are listed for orientation, not reviewed or endorsed.

20Onderwys en opleiding

Risk Academy courses and disciplines

1 course and 2 disciplines of Risk Academy (risksacademy.com) that teach the knowledge and methods of this area. Each course lists its level, stream and learning hours.

21Oor die netwerk

Programmes, tracks and courses for this area

GCRI Canada, The Global Risks Forum (GRF), The Global Risks Alliance (GRA) and Risk Academy work on the subject of this area in distinct roles (research and evidence; governance, policy and convening; capital, finance and markets; education and training). Each entry states why it corresponds and the step it offers; each institution sets its own terms of participation.

Capital, finance and markets

Die Global Risks Alliance (GRA)

Industry programmes in which financial institutions build a shared understanding of systemic risk.

Financial Regulation NexusCompares regulatory and supervisory frameworks, the context in which supervised institutions read voluntary standards.Join this programme globalriskalliance.comAll programmes of The Global Risks Alliance
22Kernterme

Kernterme

UNI
Unique Nexus Identifier: a persistent identifier that resolves an artefact to its record.
voorgestel
A draft in the open development process that the Global Standards Council has not yet adopted. Each area profile is a proposal to the Nexus Standards registry.
crosswalk
Relation in which clauses of these standards are mapped to parts of the external standard by clause number, without reproducing its text.
profile
Relation in which a Nexus profile narrows or extends the external standard for a defined use, validated with the issuing body’s own tools where these exist.
adopt
Relation in which the external standard is used as published and values are validated against it.
change record
A public record of a proposed change under NS-13, decided by the editors with written reasons.
attestation
An evaluator’s recorded result for one clause and one subject under NS-11.
liaison sought
A liaison the working group intends to request from the issuing body; a liaison is established only when the body confirms it in writing.
24Navorsing

Recent research and sources

Peer-reviewed articles, preprints, reports and datasets on the subject of this area, retrieved at the time of reading from open scholarly metadata services (OpenAlex and Crossref) and listed with authors, venue, year, type and access status, with a link to each work. Curated references and related standards are listed first; recent works matched by subject follow and are listed for orientation.

Curated references

Related standards and frameworks

Search terms, derived from the title and scope of the area: persistent identifier; persistent identifiers; digital object identifier; PID infrastructure. With JavaScript enabled, recent works matching these terms are listed from OpenAlex and Crossref.

25Vrae

Questions and answers.

What is the status of the UNI and the artefact catalogue area?
The area profile is a proposal to the Nexus Standards registry; the area is not yet in the catalogue. Standards are adopted by the Global Standards Council after last call; in each country, adoption is a decision of its National Standards Council (NSC).
How are data sources presented?
Each data source is listed with its provider, licence, update frequency and delivery path, and links to the provider’s own publication.
How can this brief be amended?
Through a public change record under NS-13: a proposed amendment to the area profile or the registry, decided by the editors with written reasons.
VerslaeDra by

Dra bewyse vanaf hierdie bladsy by.

Reports is die Konsortium se kwartaallikse publikasie. Wat jy oor hierdie onderwerp weet, kan bewyse, 'n saak of 'n korreksie in die volgende uitgawe word, aan jou toegeskryf en onder CC BY 4.0 gepubliseer waar dit jou eie werk is.

Nexus Standards
Standaarde

Contribute to The UNI and the artefact catalogue

Institutions and experts are invited to propose amendments, join the working group or propose data sources. National participation is organised through each country’s National Nexus Consortium (NNC) and its National Working Groups (NWGs); competent national authorities are engaged through official channels.

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.