Nexus Standards · Identifier

Unique Nexus Identifier (UNI)

The UNI: catalog and resolver

The UNI (Unique Nexus Identifier) is one stable, machine-readable identifier for each artifact, paired with one catalog record stating what the artifact is, who created and publishes it, which rights apply and where it is held. The resolver returns the record for a UNI.

Read NS-1 How to cite a UNI

01Instrument

Read a UNI.

Type or paste a Uniform Nexus Identifier: each segment is decoded against grammar 0.2 and the region, when it names a country, is lit on the globe above.

02Canvas

The process.

UNI anatomy · parse, resolve, citeNexus Standards registry

prefixNXSfixedscope<SCOPE>32 codescat<CAT>38 artifact, 9 record codesregion<REGION>ISO 3166-1 or M49serial<SERIAL>six digits, allocatedversion@<VERSION>semver or record version

NXS-STD-ST-000001NXS-EWS-DS-KEN-000003NXS-GRX-RP-M002-000007@1.2.0NXS-GRX-OB-KEN-000042@3NXS-GCR-AR-000015

Illustrative identifier pattern. With script enabled, a UNI can be entered and each segment is checked against the registry, resolved to its record where one is published, and expressed as a URN, a resolver link and a citation.

UNI anatomyThe NS-1 grammar segment by segment, with the scope and category codes of the registry. Resolution links to the resolver; no identifier is allocated on this page.

03Grammar

Structure of a UNI

Grammar version 0.2 (context segments added 2026-10-16; every v0.1 identifier is unchanged and remains valid).

NXS-<SCOPE>-<CAT>[-<DOMAIN>][-<SECTOR>][-<REGION>][-<ENV>]-<SERIAL>[@<VERSION>] NXS-EWS-DS-000042                    dataset 42 of the multi-hazard monitoring and warning class NXS-EWS-DS-KEN-000003                a Kenyan monitoring and warning dataset NXS-GRX-RP-M002-000007@1.2.0         report 7 of the risk data class for Africa, version 1.2.0 NXS-GRX-AR-WAT-CAN-000012            article 12 of the risk data class on water in Canada NXS-GRX-DP-WAT-WUT-CAN-PRD-000001    production deployment 1 of the risk data class for Canadian water utilities (NS-9) NXS-GCR-AR-000015                    an article published by GCRI Canada NXS-STD-ST-000001                    this standard

Segment	Form	Meaning
`NXS`	fixed	Prefix. Chosen over `NEX` because it reads as a code, not a word, and because `NEX-` is crowded by brands. `NXS-S01` to `NXS-S20` are also the neutral identifiers of the functional system classes (section 2).
SCOPE	three letters	A functional system class (`EWS`, `EOP`, `SIG`, `GRX`, `OPS` and the others in section 2), an organisation (`GCR`, `GRF`, `GRA`, `NXO`) or a cross-cutting scope (`STD`, `LEG`, `GOV`, `PRG`)
CAT	two letters	Artifact category, mapped to Zenodo upload and publication types and to DataCite resource types (section 3); or a risk record kind (`OB`, `SR`, `IN`, `ME`, `BD`, `CT`, `CR`, `AP`, `SU`; NS-3). The two lists never share a code.
DOMAIN	optional, three letters	Domain code from `registry/domains.yaml` (`WAT` water, `ENE` energy, `FOO` food, `HLT` health, `BIO` biodiversity, `CLI` climate, `DRR`, `EWN`, `HUM`, `INF`, `SCH`, `SEC`, `ZTA`, `FNC`, `DSC`, `ERM`, `DRG`, `AIS`, `DAT`, `GSP`, `PRV`, `IDF`, `SFW`, `NAT`, `SDP`, `LIC`; proposed: `CMP`, `DTW`, `SNS`, `PNT`)
SECTOR	optional, three letters	Sector code from `registry/sectors.yaml` (`AGR`, `WUT`, `EUT`, `HSY`, `FNI`, `TRL`, `CIT`, `INM`, `DTC`, `PUB`, `RED`, `HUO`, `IGO`)
REGION	optional	ISO 3166-1 alpha-3 country code (`KEN`, `CAN`) or UN M49 area code written as `M` followed by three digits (`M002` Africa, `M142` Asia); registry `registry/regions.yaml`
ENV	optional, three letters	`PRD` production, `STG` staging, `LBX` lab, `FIX` fixture; used by contextual records (NS-9)
SERIAL	six digits	Allocated by a catalog or a record allocation authority per full prefix (SCOPE, CAT and context segments); never reused
VERSION	optional	Semantic version of an artifact (`1.2.0`) or the integer `recordVersion` of a risk record (`3`; NS-3). The UNI without a version names the concept.

Context segments. The four optional segments always appear in the order DOMAIN, SECTOR, REGION, ENV. Each is a three-letter code from its registry, and the registries are pairwise disjoint and disjoint from the scope codes and from the M49 form (checked by node tools/nexus-id.mjs catalog validate), so an identifier parses deterministically without separators. The identifier without CAT and SERIAL is the context name: NXS-GRX-WAT-CAN reads as the risk data class, water domain, Canada. Articles, pages, datasets, deployments, dashboards and code about that context carry the context name (NS-16); their UNIs differ only in CAT and SERIAL. A context name is never allocated and never carries a serial; the NS-9 contextual record (DP or PR) is the record of truth for a context.

Machine forms: URN urn:nexus:uni:NXS-EWS-DS-000042; resolver path /uni/NXS-EWS-DS-000042 (an HTML landing page for browsers and JSON for machines by content negotiation; /uni/<uni>.json is always JSON; /uni lists published records); context path /ctx/NXS-GRX-WAT-CAN (every published record of that context); field name uni in every record, API, schema and table.

Existing dotted identifiers (for example data.eo.stac.catalogue) are UNI v0. They are recorded as legacyUni on the new record for crosswalk and are never allocated again.

1.1 Context code allocation

Proposal NXS-STD-PC-000004 introduces this section and is OPEN; the rules apply to every code allocated from now on. Machine form: registry/nexus-standards.yaml identifier.codeAllocation. Check: node tools/nexus-id.mjs catalog validate.

A scope, domain, sector or environment code is a three-letter classification that machines parse and that people need not read. The allocation rules exist so that no code becomes ambiguous, including after future changes in other code lists.

Rule	Text
CA-1	A code is three capital letters A to Z. It contains no digits and never takes the UN M49 form (`M` followed by three digits).
CA-2	A code is unique across every registry: scopes, domains, sectors, environments and ISO 3166-1 alpha-3.
CA-3	A code is never one of the following, all listed in `registry/regions.yaml`, so that a future country assignment cannot collide:<br>• an ISO 3166-1 exceptionally, transitionally or formerly reserved code element;<br>• a code in the user-assigned ranges (`AAA` to `AAZ`, `QMA` to `QZZ`, `XAA` to `XZZ`, `ZZA` to `ZZZ`);<br>• an ICAO Doc 9303 nationality code.
CA-4	A code is a mnemonic of the English label: the first letter of the label's head term, followed by consonants that keep the code recognisable.
CA-5	A code is never a product name, a mark, a company name or a stock ticker, and never a word that reads as a brand.
CA-6	One concept per code. Each code has a definition, what it includes and excludes, and the external standards it crosswalks to.
CA-7	Ids are stable, lowercase kebab-case English. Labels are in sentence case. Neither encodes a status.
CA-8	Append-only. A code is never reassigned or deleted. A retired code keeps its entry with `deprecated: true` and `supersededBy`.
CA-9	A new code stays `PROPOSED`, with its proposal UNI, until the Global Standards Council adopts the registry change. An implementation may use a `PROPOSED` code and shall show its status.
CA-10	Adding a code is a minor, additive registry version. Changing what a code means is a major change and requires a crosswalk.

Grandfathered: AAP, the scope code of the anticipatory-action class, was allocated before CA-3 and lies inside the user-assigned range AAA to AAZ. It is kept under CA-8.

Technology domains proposed under these rules:

Code	Id	Label	Crosswalks to
`CMP`	`compute`	Compute and accelerated infrastructure	ISO/IEC JTC 1/SC 38 and SC 39; ISO/IEC 22123
`DTW`	`digital-twins`	Digital twins and simulation	ISO/IEC 30173:2023; ISO/IEC JTC 1/SC 41; ISO 23247
`SNS`	`sensing`	Sensing and measurement networks	OGC SensorThings API and SensorML; W3C/OGC SOSA/SSN; IEEE 1451
`PNT`	`pnt`	Positioning, navigation and timing	IEEE 1588; ITU-T G.8271 and G.8272; ITU-R TF series; UN ICG

Sensing and positioning, navigation and timing are separate codes because different communities standardise them: sensor and observation encodings on one side, timing and GNSS profiles on the other. A technology stream that covers both carries SNS and lists PNT as related.

A future quantum-technology code cannot be QTM or QNT, because both fall in the user-assigned range QMA to QZZ. CA-3 catches this kind of collision before allocation.

04Canvas

The grammar.

Canvas · the grammarProcess diagram

Fig.The UNI segment by segment, with the number of codes in each segment from the registry.

05Earth observation

Electrified and connected activity worldwide

The map is framed on the world as context for the artifacts a UNI (Unique Nexus Identifier) identifies. Shown at first: night-time lights, daily (VIIRS Black Marble, VNP46A2, NASA LAADS DAAC) and population density, 2020 (Gridded Population of the World v4.11, NASA SEDAC, CIESIN, Columbia University). The layer drawer adds true colour (VIIRS NOAA-20 corrected reflectance). NASA products are served through NASA GIBS under NASA's open data policy, with acknowledgement; population density is GPW v4.11 by CIESIN, Columbia University, under CC BY 4.0; coastlines, boundaries and place names come from NASA GIBS reference layers (© OpenStreetMap contributors, ODbL) and Natural Earth (public domain). Each layer shows its own observation date; full credits are given under the map.

The interactive map needs JavaScript; the layer list and sources are below.

Layers 2

Connected activity

Latest available

NASA GIBS / EOSDIS · ASTER GDEM (METI, NASA) · Blue Marble (NASA) · © OpenStreetMap contributors (ODbL) · Natural Earth

Loading the latest NASA imagery.

Drag to move. Ctrl or ⌘ and scroll, pinch or the buttons to zoom; hover for the values under the pointer; reset returns to the region.

Night-time lights and population density, the footprint of electrified, connected activity, framed on World.Satellite and model products as NASA publishes them, each with its own date; indicators, not assessments of any place.

Data: NASA GIBS · ASTER GDEM · Blue Marble · © OpenStreetMap contributors · Natural EarthSources and licences

We acknowledge the use of imagery provided by services from NASA's Global Imagery Browse Services (GIBS), part of NASA's Earth Science Data and Information System (ESDIS). Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
We acknowledge the use of imagery provided by services from NASA's Global Imagery Browse Services (GIBS), part of NASA's Earth Science Data and Information System (ESDIS). Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
VIIRS Black Marble night-time lights, NASA Goddard Space Flight Center; distributed by the NASA Level-1 and Atmosphere Archive and Distribution System (LAADS DAAC); imagery via NASA GIBS. Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
Center for International Earth Science Information Network (CIESIN), Columbia University. 2018. Gridded Population of the World, Version 4 (GPWv4): Population Density, Revision 11. NASA Socioeconomic Data and Applications Center (SEDAC). Licensed under CC BY 4.0. Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). doi:10.7927/H49C6VHW. CC BY 4.0
VIIRS near-real-time products (flood, land surface temperature, snow cover, corrected reflectance), NASA LANCE; imagery via NASA GIBS. Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
ASTER GDEM is a product of METI and NASA (ASTER Global Digital Elevation Model V003, NASA LP DAAC); imagery via NASA GIBS. Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). Cite as: NASA/METI/AIST/Japan Spacesystems and U.S./Japan ASTER Science Team (2019). ASTER Global Digital Elevation Model V003. doi:10.5067/ASTER/ASTGTM.003. NASA open data
Made with Natural Earth. Free vector and raster map data @ naturalearthdata.com. Public domain
© OpenStreetMap contributors (ODbL), via NASA GIBS (coastlines, boundaries, roads and place names). Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). ODbL
Blue Marble, NASA Earth Observatory; imagery via NASA GIBS. Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
Context on the globe and flat map: coastlines, boundaries, roads and place names from NASA GIBS reference layers (OpenStreetMap data, ODbL, © OpenStreetMap contributors); Blue Marble imagery as an optional base; 3D terrain and the elevation read-out from the ASTER GDEM elevation colour index (5 m to 200 m classes, exaggerated for legibility). Boundaries are drawn as published and imply no position on any territory.
Globe: MapLibre GL JS 6.9.1, BSD-3-Clause, © MapLibre contributors.
NASA GIBS: We acknowledge the use of imagery provided by services from NASA's Global Imagery Browse Services (GIBS), part of NASA's Earth Science Data and Information System (ESDIS).
Optional layers (3 sources in the layer list: live, forecast, observed and context) print their provider credit on the map and here when switched on; forecasts are model output and derived indices are estimates.

Layers and dates

Night-time lights, daily: VIIRS Black Marble (VNP46A2), NASA LAADS DAAC · 12 Oct 2026
Population density, 2020: Population: CIESIN, Columbia University, Gridded Population of the World v4.11 (2018), NASA SEDAC, CC BY 4.0 · static
True colour: VIIRS NOAA-20 corrected reflectance, NASA LANCE · 13 Oct 2026

06Scopes

Scope codes

32 scope codes for systems, organisations and cross-cutting scopes. Codes classify; public labels follow the naming rules of the standards. When an identifier is entered in the parser above, the row of its scope is highlighted.

Code	Kind	Label
`CMD`	system	Integrated posture and executive synthesis
`NST`	system	Civilian common operating picture
`DSS`	system	Decision support, cases and deliberation
`COR`	system	Compute, nodes and runtimes
`NXQ`	system	Software, models and capability lifecycle
`GRX`	system	Canonical risk data, records and provenance
`EOP`	system	Earth observation and digital twins
`EWS`	system	Multi-hazard monitoring and warning
`AAP`	system	Anticipatory action and triggers
`NET`	system	Network topology and continuity
`OPS`	system	Instruments, sensors and calibration
`SIG`	system	Signals, spectrum, timing and positioning, navigation and timing (PNT)
`the trust and assurance system`	system	Trust, authorization and assurance
`HUB`	system	Knowledge, records and learning
`STU`	system	Visual composition and workflows
`FAC`	system	Blueprints, builds and signing
`APP`	system	Application catalogue and lifecycle
`RLS`	system	Participants, agreements and protocols
`POR`	system	Public, client and partner delivery
`LAB`	system	Research, experiments and simulation
`GCR`	organisation	GCRI Canada
`GRF`	organisation	The Global Risks Forum
`GRA`	organisation	The Global Risks Alliance
`NXO`	organisation	Reserved organisation scope for a multi-party consortium (entity under legal review)
`ELP`	organisation	Reserved organisation scope (withdrawn before use)
`OBS`	organisation	Reserved organisation scope (withdrawn before use)
`STD`	cross cutting	The Nexus Standards themselves
`LEG`	cross cutting	Legal, intellectual property and licensing
`GOV`	cross cutting	Governance, decisions and policy
`PRG`	cross cutting	Programme, waves and work packages
`UXK`	cross cutting	UI/UX kit, design tokens and assets
`ALL`	cross cutting	Ecosystem-wide

07Categories

Artifact categories

38 artifact categories. Each maps to a DataCite resource type and a Zenodo upload type for export; the mapping is a crosswalk, and the UNI remains the key.

Code	Category	DataCite type
`SW`	Software	Software
`SV`	Service or API	Service
`SC`	Schema or contract	Other
`MG`	Database migration	Software
`WF`	Workflow	Workflow
`MD`	Model	Model
`DS`	Dataset	Dataset
`EV`	Evidence record	Dataset
`AR`	Article	JournalArticle
`PP`	Preprint	Preprint
`RP`	Report	Report
`TN`	Technical note	Text
`DC`	Documentation	Text
`DL`	Deliverable	Report
`WP`	Working paper	Text
`BK`	Book or chapter	Book
`CP`	Conference paper	ConferencePaper
`TH`	Thesis	Dissertation
`PT`	Patent	Other
`ST`	Standard	Standard
`PC`	Policy or directive	Text
`PS`	Presentation	Text
`PO`	Poster	Text
`FG`	Figure	Image
`PL`	Plot or visualization	Image
`DG`	Diagram	Image
`PH`	Photo	Image
`MP`	Map product	Image
`VD`	Video	Audiovisual
`LS`	Lesson or course	InteractiveResource
`PY`	Physical object	PhysicalObject
`PA`	Participation record	Other
`RS`	Programme status record	Other
`DP`	Deployment or instance (NS-9 context)	Other
`PR`	Programme instance (NS-9 context)	Other
`CL`	Clause (NS-10 obligation)	Other
`AT`	Conformance attestation (NS-11)	Other
`OT`	Other	Other

Code	Record kind	Note
`OB`	Observation fact	record kind (NS-3)
`SR`	Source release	record kind (NS-3)
`IN`	Indicator definition	record kind (NS-3)
`ME`	Measure definition	record kind (NS-3)
`BD`	Boundary version	record kind (NS-3)
`CT`	Chronotope version	record kind (NS-3)
`CR`	Correction record	record kind (NS-3)
`AP`	Analytical product record	record kind (NS-3)
`SU`	Subject (place, asset, organisation)	record kind (NS-3)

08The record

Content of a catalog record

The record schema with example records from the standards catalog, and the crosswalk of its fields to public metadata schemas.

Record explorer · schema, example, crosswalkNexus Standards registry

Nexus artifact record (NS-1) · 32 fields · 12 required

uni required stringThe UNI (Unique Nexus Identifier), NS-1 grammar, without @version.
displayAlias stringPublic Nexus Registry short form (NX-R-47092) shown next to the UNI during the transition.
registryState enumPublic registry state; corrections keep the UNI and add a version.
legacyUni stringDotted UNI v0 this record replaces, for crosswalk (for example data.eo.stac.catalogue).
title required string
description string
scope required string
category required string
region string
domain stringDOMAIN segment code from registry/domains.yaml (NS-1 v0.2); present when the identifier carries it.
sector stringSECTOR segment code from registry/sectors.yaml (NS-1 v0.2).
environment enumENV segment code (NS-1 v0.2).
contextName stringNS-16 context name: the identifier without CAT and SERIAL; derived, never allocated.
systemId stringFunctional system class id (systemId) from registry/nexus-standards.yaml#scopes when scope is a SYSTEM.
status required enum
currentVersion string
versions array
- version string
- date string
- gitSha string
- digest string
- note string
creators required array
- name string
- type enum
- affiliation string
- orcid string
- ror string
publisherRef required stringEntity reference of the publishing institution (registry/governance.yaml#bodies); the institution stays publisher of record for institutional artifacts.
publicationDate required string
language string
keywords array
rights required object
- license stringSPDX licence identifier or expression, or a LicenseRef- string for a licence that has no SPDX identifier.
- rightsHolderRef string
- accessRight enum
- embargoDate string
legalState required enum
claimCeiling required enum
locations required array
- kind enum
- value string
- digest string
relatedIdentifiers array
- relation enum
- identifier string
- identifierType enum
supersededBy string
workPackageId string
directiveRefs arrayReferences to the recorded decisions or policies under which the artifact was produced.
notes string
context objectNS-9: this record is a deployment, instance or programme instance of the concept ofUni, in a context.
- ofUni string
- domains arrayids from registry/domains.yaml
- sectors arrayids from registry/sectors.yaml
- jurisdictions array
- hostRef string
- environment enum
- validFrom string
- validUntil string
- conformsTo arrayNexus Standard ids and registry/external-standards.yaml ids this context claims; evidence per NS-11

Example record · NXS-STD-ST-000001

{ "uni": "NXS-STD-ST-000001", "title": "Nexus Standards NS-1 - the UNI and artifact catalog", "scope": "STD", "category": "ST", "status": "DRAFT", "currentVersion": "0.1.0", "creators": [ { "name": "Global Centre for Risk and Innovation (GCRI)", "type": "Organizational" } ], "publisherRef": "GCRI", "publicationDate": "2026-10-15", "rights": { "license": "CC-BY-4.0", "accessRight": "open" }, "legalState": "LEGAL_REVIEW_REQUIRED", "claimCeiling": "INTEGRATED", "locations": [ { "kind": "repoPath", "value": "standards/NS-1-identifier-and-artifact-catalog.md" }, { "kind": "repoPath", "value": "registry/nexus-standards.yaml" } ], "workPackageId": "LEGAL-NAME-ARCHITECTURE-001" }

Field crosswalk: Schema.org JSON-LD, DataCite, Zenodo, CodeMeta

Record field	Schema.org	DataCite	Zenodo	CodeMeta	Source
`uni`	identifier (PropertyValue, propertyID urn:nexus:uni)	alternateIdentifier (alternateIdentifierType NXS)	metadata.related_identifiers[] (scheme other)	identifier	draft
`title`	name	titles[].title	metadata.title	name	draft
`description`	description	descriptions[].description (Abstract)	metadata.description	description	draft
`scope`	·	subjects[] (subjectScheme nexus-scope)	metadata.keywords[]	·	draft
`category`	additionalType	types.resourceTypeGeneral	metadata.upload_type / publication_type / image_type	applicationCategory	registry
`region`	spatialCoverage	geoLocations[].geoLocationPlace	metadata.locations[]	·	draft
`status`	creativeWorkStatus	·	·	developmentStatus	draft
`currentVersion`	version	version	metadata.version	version	draft
`versions`	·	relatedIdentifiers (IsNewVersionOf, IsPreviousVersionOf)	versions (concept DOI)	·	draft
`creators`	creator / author	creators[]	metadata.creators[]	author	draft
`publisherRef`	publisher	publisher	metadata.publisher (Zenodo)	publisher	draft
`publicationDate`	datePublished	publicationYear; dates[] (Issued)	metadata.publication_date	datePublished	draft
`language`	inLanguage	language	metadata.language	·	draft
`keywords`	keywords	subjects[]	metadata.keywords[]	keywords	draft
`rights.license`	license	rightsList[].rightsIdentifier (SPDX)	metadata.license	license	draft
`rights.accessRight`	conditionsOfAccess	·	metadata.access_right	·	draft
`legalState`	·	·	·	·	draft
`claimCeiling`	·	·	·	·	draft
`locations`	url / contentUrl / codeRepository	alternateIdentifiers[] (URL)	files[] / metadata.related_identifiers[]	codeRepository / downloadUrl	draft
`relatedIdentifiers`	isPartOf / citation / isBasedOn	relatedIdentifiers[] (relationType)	metadata.related_identifiers[]	isPartOf / referencePublication	draft
`supersededBy`	·	relatedIdentifiers[] (IsObsoletedBy)	metadata.related_identifiers[] (isObsoletedBy)	·	draft
`workPackageId`	·	·	·	·	draft
`directiveRefs`	·	relatedIdentifiers[] (References)	metadata.related_identifiers[] (references)	·	draft
`context`	·	·	·	·	draft

Rows marked registry are taken from the category mappings to Zenodo and DataCite in the registry; rows marked draft are an editorial mapping to the public schemas and are not part of the registry.

Record explorerschemas/nexus-artifact-record.v1.json with example records from the standards catalog (scope STD). A record describes an artifact and its provenance.

09Resolver

Resolution of a UNI

The resolver path is /uni/{uni}: an HTML landing page for browsers and JSON for machines, for published records that are not restricted. The catalog file in the standards repository is the authoritative source of the records.

10Catalog

Records in the standards scope

104 records: the identifiers of the standards themselves, with their status and rights state.

UNI	Title	Status	Rights state
`NXS-STD-ST-000001`	Nexus Standards NS-1 - the UNI and artifact catalog	draft	legal review required
`NXS-STD-SW-000002`	UNI command-line tool (validate, parse, next, mint, catalog, export) - reference implementation	draft	legal review required
`NXS-STD-SC-000001`	UNI artifact record schema v1	draft	legal review required
`NXS-STD-ST-000002`	Open-standards and open-source stack under the UNI	draft	legal review required
`NXS-STD-SW-000005`	UNI data profile (STAC, DCAT, PROV-O crosswalks), NS-3b	draft	legal review required
`NXS-STD-ST-000003`	Nexus Standards NS-3 - risk record UNIs (grammar, legacy crosswalk, allocation authority)	draft	legal review required
`NXS-STD-SW-000006`	Nexus Standards repository validator (registry invariants, schema, STD catalog, embedded UNIs, register of implementations)	draft	legal review required
`NXS-STD-DC-000001`	Nexus Standards repository documentation (README, governance, contributing, agent boot)	draft	legal review required
`NXS-STD-SW-000007`	Nexus Standards site page generator and WordPress draft publisher	draft	legal review required
`NXS-STD-DC-000002`	Nexus Standards site pages for nexustandards.com (overview, NS-1, catalog and resolver, governance)	draft	legal review required
`NXS-STD-ST-000004`	Nexus Standards NS-0 - constitution and principles	draft	legal review required
`NXS-STD-ST-000005`	Nexus Standards NS-9 - contextual UNIs (deployments, instances, programme instances)	draft	legal review required
`NXS-STD-DC-000003`	Nexus Standards subsites (systemic architecture index and one landing page per subsite)	draft	legal review required
`NXS-STD-ST-000006`	Nexus Standards NS-10 - policies and clauses	draft	legal review required
`NXS-STD-ST-000007`	Nexus Standards NS-11 - verification and monitoring	draft	legal review required
`NXS-STD-ST-000008`	Nexus Standards NS-13 - open standards development process	draft	legal review required
`NXS-STD-SC-000002`	Nexus clause, policy, attestation and proposal schemas v1 (NS-10, NS-11, NS-13)	draft	legal review required
`NXS-STD-ST-000009`	Nexus Standards NS-2 - citation and attribution	draft	legal review required
`NXS-STD-ST-000010`	Nexus Standards NS-4 - structure and drafting of Nexus Standards and documents	draft	legal review required
`NXS-STD-ST-000011`	Nexus Standards NS-5 - figures, maps and visualization	draft	legal review required
`NXS-STD-ST-000012`	Nexus Standards NS-12 - software, models and AI/ML artifacts	draft	legal review required
`NXS-STD-ST-000013`	Nexus Standards NS-14 - conformance and crosswalk to external standards	draft	legal review required
`NXS-STD-RP-000001`	Standards landscape dossier: external risk, resilience, security, data and open-standards bodies crosswalked for the Nexus Standards	draft	legal review required
`NXS-STD-DS-000001`	External standards register (registry/external-standards.yaml): 151 standards with body, version, URL, domain, access, relation and verification flag	draft	legal review required
`NXS-STD-DS-000002`	Ecosystem coverage register: sites, 216 areas with governing standards and artifact kinds, 303 naming findings	draft	legal review required
`NXS-STD-ST-000014`	NS-15 System model binding (subjects, passports, chronotopes, routes, engines, cells, agents)	draft	legal review required
`NXS-STD-SC-000003`	Nexus subject passport envelope schema v1 (NS-15)	draft	legal review required
`NXS-STD-ST-000015`	NS-16 UNI application profile (articles, documents, code, data, APIs, interfaces)	draft	legal review required
`NXS-STD-RS-000002`	Process and pipeline graphs for the site DAG component (NS-13 track, body tracks, conformance, record lifecycle, routing, monitoring)	draft	legal review required
`NXS-STD-RS-000003`	Standard packages register: one page series per open standard (CAP 1.2, STAC, PROV-O as the template)	draft	legal review required
`NXS-STD-DC-000005`	Open standards packages index and the standard package page series (CAP 1.2, STAC, PROV-O: package, clause map, updates)	draft	legal review required
`NXS-STD-DC-000006`	Development tracks page: NS-13 lifecycle and the OASIS, W3C, IETF, OGC and ISO/IEC tracks as interactive graphs	draft	legal review required
`NXS-STD-DC-000007`	Contribute to an open standard: step-through guide and the channels of the packaged standards	draft	legal review required
`NXS-STD-DC-000008`	Standards pipelines page: routing, monitoring, conformance pipeline and record lifecycle graphs	draft	legal review required
`NXS-STD-SW-000008`	Site open-standards module: nxs-dag component (layout, SVG, play/step/scrub runtime) and the standard package page generator	draft	legal review required
`NXS-STD-RP-000004`	Standards development literature review: EU reform, SMART standards, living tracks, foundation processes, emerging-technology standards, conformance practice, feeds	draft	legal review required
`NXS-STD-RS-000004`	Feed-source proposals register: one proposed row per body feed (all LEGAL_REVIEW_REQUIRED)	draft	legal review required
`NXS-STD-SW-000009`	Tests for the open-standards site module (DAG layout, rendering, packages and stubs, routing data)	draft	legal review required
`NXS-STD-RS-000005`	Governance, legal structure, national adoption, open boundary and disclaimers register	draft	legal review required
`NXS-STD-SW-000010`	Governance documents generator	draft	legal review required
`NXS-STD-DC-000010`	Governance directory index	draft	legal review required
`NXS-STD-DC-000011`	Nexus Standards Charter (draft target)	draft	legal review required
`NXS-STD-DC-000012`	National adoption, adaptation and sovereignty	draft	legal review required
`NXS-STD-DC-000013`	Open boundary, IPR and licensing	draft	legal review required
`NXS-STD-DC-000014`	Legal structure and instruments	draft	legal review required
`NXS-STD-DC-000015`	Disclaimers and legal language	draft	legal review required
`NXS-STD-DC-000016`	Security, safety and continuity measures	draft	legal review required
`NXS-STD-DC-000017`	Go-live readiness	draft	legal review required
`NXS-STD-DC-000018`	Agent guide	draft	legal review required
`NXS-STD-DC-000019`	Site pages: stewardship, national adoption and open boundary	draft	legal review required
`NXS-STD-DC-000020`	Site pages: legal notices	draft	legal review required
`NXS-STD-RS-000006`	Feed updates from admitted official feeds (generated)	draft	legal review required
`NXS-STD-SW-000011`	Feed export importer	draft	legal review required
`NXS-STD-PC-000004`	Proposal: context code allocation rules and domain codes CMP, DTW, SNS, PNT	draft	legal review required
`NXS-STD-DS-000004`	Nexus Risk Standards catalogue (registry/risk-standards.yaml)	draft	legal review required
`NXS-STD-SW-000012`	Nexus Risk Standards document generator	draft	legal review required
`NXS-STD-DC-000021`	Nexus Risk Standards: the systemic architecture	draft	legal review required
`NXS-STD-PC-000005`	Proposal: Nexus Risk Standards systemic catalogue	draft	legal review required
`NXS-STD-DS-000005`	Nexus risk taxonomy: the full risk spectrum (registry/risk-taxonomy.yaml)	draft	legal review required
`NXS-STD-SW-000013`	Machine exports generator: ontology, taxonomy, shapes, JSON-LD, OSCAL, ODRL	draft	legal review required
`NXS-STD-SW-000014`	Release manifest, signing and zero-trust verification	draft	legal review required
`NXS-STD-SW-000015`	Read-only standards query layer	draft	legal review required
`NXS-STD-SW-000016`	Agent interface (Model Context Protocol server)	draft	legal review required
`NXS-STD-SW-000017`	Standards HTTP server	draft	legal review required
`NXS-STD-SW-000018`	Nexus Standards one-command CLI	draft	legal review required
`NXS-STD-PC-000006`	Proposal: full-spectrum completion, risk taxonomy and AI-native standards infrastructure	draft	legal review required
`NXS-STD-DC-000022`	Quick start: use the Nexus Standards in one command	draft	legal review required
`NXS-STD-DS-000006`	Nexus native register	draft	legal review required
`NXS-STD-DS-000007`	Nexus harmonisation register	draft	legal review required
`NXS-STD-DS-000008`	Nexus Risk Standards catalogue source	draft	legal review required
`NXS-STD-SW-000020`	Native authority extractor	draft	legal review required
`NXS-STD-SW-000021`	Risk Standards catalogue and taxonomy generator	draft	legal review required
`NXS-STD-PC-000007`	Native convergence of the Nexus Risk Standards	draft	legal review required
`NXS-STD-DS-000009`	Participation register: start-up, cadence, working groups, expert communities and gateways	draft	legal review required
`NXS-STD-SW-000022`	Cadence library (council, committee and working group sessions)	draft	legal review required
`NXS-STD-DC-000023`	Participate page of the Nexus Standards site	draft	legal review required
`NXS-STD-PC-000008`	Participation, cadence and gateways	draft	legal review required
`NXS-STD-DC-000024`	Participation, cadence and gateways (operating manual)	draft	legal review required
`NXS-STD-DS-000010`	Nexus risk vocabulary and risk classes	draft	legal review required
`NXS-STD-DS-000011`	Industries, industry groups and proposed sector codes	draft	legal review required
`NXS-STD-DS-000012`	Disciplines mapped to domains and NHS-1 hazard domains	draft	legal review required
`NXS-STD-PC-000009`	Risk atlas 1.1: NHS-1 1.1.0, risk vocabulary, industries, sectors and jurisdictions	draft	legal review required
`NXS-STD-DC-000025`	Risk atlas, vocabulary and classifications (guide)	draft	legal review required
`NXS-STD-DC-000026`	Expert audit of the Nexus Standards and the plan to make them world class	draft	legal review required
`NXS-STD-DC-000027`	Bibliography and acknowledgement of prior work	draft	legal review required
`NXS-STD-PO-000001`	Policy on information hazards and dual-use content	draft	legal review required
`NXS-STD-DC-000028`	Maintenance of Nexus Standards: systematic review, versioning, errata, stabilisation and withdrawal	draft	legal review required
`NXS-STD-DS-000013`	Register of normative requirements	draft	legal review required
`NXS-STD-TN-000001`	NHS-2 model specification: kinds, quantities, relations, evidence and provenance	draft	legal review required
`NXS-STD-DC-000029`	New work items NRS-C17 to NRS-C24: scope and justification	draft	legal review required
`NXS-STD-PC-000010`	New core risk standards NRS-C17 to NRS-C24	draft	legal review required
`NXS-STD-DC-000030`	Terms of reference of workstreams W1 to W8	draft	legal review required
`NXS-STD-DC-000031`	Invitations to the expert communities, councils and liaison organisations	draft	legal review required
`NXS-STD-PO-000002`	Policy on accessibility and languages	draft	legal review required
`NXS-STD-DC-000032`	Conformity assessment scheme (first proposed draft)	draft	legal review required
`NXS-STD-DC-000033`	Programme cover note of the Secretariat	draft	legal review required
`NXS-STD-DS-000014`	Information-hazard screening register	draft	legal review required
`NXS-STD-DS-000015`	Circulation for technical review and comment, and the technical review areas	draft	legal review required
`NXS-STD-DC-000034`	Notice of circulation for technical review and comment	draft	legal review required
`NXS-STD-SW-000023`	Circulation notice and technical review builder	draft	legal review required
`NXS-STD-SW-000024`	Nexus Standards repository check (open boundary, links and paths, syntax, information-hazard screen, proposals)	draft	legal review required
`NXS-STD-DC-000035`	Release policy of the open repository and the content of each release	draft	legal review required
`NXS-STD-RS-000007`	Roadmap of the Nexus Standards to the first official release (target 2030)	draft	legal review required
`NXS-STD-DC-000036`	Roadmap to 2030 and invitation to all stakeholders	draft	legal review required

11Questions

Questions and answers.

Is a UNI a brand or a product name?

No. A UNI is a catalogue code, comparable in kind to a DOI or an ISBN. It carries no trademark claim and is not presented as a product name.

Can a UNI be assigned manually?

No. Serials are allocated only through a catalog or the data fabric; a manually entered serial is invalid (NS1-R2).

What happens when an artifact is withdrawn?

Its UNI is retained; the record is marked withdrawn or points to the artifact that succeeded it. UNIs are not deleted or reused.

NRNexus Reports gateway · GW-STD

Contribute to Nexus Reports from this page.

Nexus Reports is the Consortium's quarterly publication. What you know about this subject can become evidence, a case or a correction in the next edition, credited to you and published under CC BY 4.0 where it is your own work.

Nexus Standards

Never send personal data, sensitive infrastructure detail or anything you have no right to share. A contribution is reviewed before use; sending it confers no authorship or editorial rights, and sponsorship never buys a finding.

Across the Consortium

The same subject across the Consortium.

Risk Academyrisksacademy.comRisk information standards and interoperabilityWhere it is taught

Around the Nexus Standards.

Nexus Standards

Take part in the standards.

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.

Propose a change Roadmap to 2030 Adopt and implement

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 artifact; 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.