Skip to content
AmazingaNS-1Kuphakanyisiwe
NS-1

NS-1: The UNI and the artefact catalogue (grammar v0.2

NS-1 is a proposed Nexus Standard; the artefacts it governs are identified by UNIs (Unique Nexus Identifier). NS-1 gives every artefact the ecosystem produces one stable, machine-readable identifier, the UNI (Unique Nexus Identifier), and one catalogue record that says what the artefact is, who made it, who publishes it, what rights apply and where it lives. Code, services, schemas, datasets, models, reports, articles, figures, maps, lessons, policies and standards all follow the same scheme, so any agent, developer, researcher, machine or expert reader can find and cite an artefact the same way across all systems, rooms, runtimes, organisations and sites.

NS-1 in the catalogue
The standards NS-1 depends on and those that cite it, then its sections with one mark for each numbered requirement.Source: NS-1-identifier-and-artifact-catalog.md; the Nexus Standards registry.
  • NS-1 depends on: NS-2, NS-3, NS-3b, NS-4, NS-5, NS-6, NS-7, NS-8, NS-9, NS-13, NS-16.
  • NS-1 is cited by: NS-0, NS-2, NS-3, NS-3b, NS-4, NS-6, NS-7, NS-9, NS-10, NS-13, NS-15, NS-16.
  • Section 1, Where the standard lives: no numbered requirement.
  • Section 2, The UNI: no numbered requirement.
  • Section 3, Scope codes: no numbered requirement.
  • Section 4, Category codes: no numbered requirement.
  • Section 5, The record: no numbered requirement.
  • Section 6, Rules: R1, R2, R3, R4, R5, R6, R7, R8, R9, R10.
  • Section 7, Embedding: how each surface carries the UNI: no numbered requirement.
  • Section 8, Commands: no numbered requirement.
  • Section 9, The open-standards stack: no numbered requirement.
  • Section 10, Relationship to the other standards: no numbered requirement.
  • Section 11, Follow-on packages: no numbered requirement.
01Ukubuka konke

Summary

NS-1record
  1. Isimokuphakanyisiwe
  2. Responsible scopetrust
  3. Rules stated10
  4. Programme areas10
  5. Source filesrepository

Nexus Standards · proposed

Requirements
10
numbered rules
Sections
11
in the text
Depends on
11
NS-2, NS-3, NS-3b
Cited by
12
Nexus Standards
02The standard

NS-1: the standard

The text of NS-1 as it stands in the canonical repository (commit 2cbe0d41b5f8): 11 clauses, 2 sub-clauses and 10 identified requirements, each with its anchor and citation.

Code
NS-1
Title
I-UNI nekhathalogi yezinto (uhlelo lolimi v0.2: izingxenye zesizinda, umkhakha, isifunda nendawo)
Version
0.1.0
Isimo
KUHLONGOZIWE
Date
catalogue 2026-10-15 · circulated 17 October 2026
Unique Nexus Identifier
NXS-STD-ST-000001
Responsible scope
trust
Umthombo
standards/NS-1-identifier-and-artifact-catalog.md at 2cbe0d41b5f8

Preparatory working draft, circulated for review and comment. Not for implementation. Prepared and circulated by Saeed Valadbaygi, Chief Steward, Nexus Standards (saeed@therisk.global), 17 October 2026. Technical review area: TR-02. This document is not a Nexus Standard; it may change without notice and is not to be implemented, relied upon or cited as a Nexus Standard. Its stage is designated only by the Global Standards Council and its technical committees under NS-13. Recipients are invited to submit comments with supporting reasons, and to notify any patent rights of which they are aware. See the notice of circulation.

Isimo
KUHLONGOZIWE
Owner
the trust and assurance system (trust, authorisation, policy and assurance; NXS-S13)
Issuing fabric
UNI identifier fabric
Canonical home
this repository
Machine registry
registry/nexus-standards.yaml
Record schema
schemas/nexus-artifact-record.v1.json
STD catalogue
catalog/artifact-catalog.yaml
Reference CLI
node tools/nexus-id.mjs
Consumer implementations
registry/consumers.yaml

NS-1 gives every artefact the ecosystem produces one stable, machine-readable identifier, the UNI (Unique Nexus Identifier), and one catalogue record that says what the artefact is, who made it, who publishes it, what rights apply and where it lives. Code, services, schemas, datasets, models, reports, articles, figures, maps, lessons, policies and standards all follow the same scheme, so any agent, developer, researcher, machine or expert reader can find and cite an artefact the same way across all systems, rooms, runtimes, organisations and sites.

the trust and assurance system owns and versions the Nexus Standards. Every other system, site engine, editorial surface and agent applies them and never forks them. A UNI identifies and resolves; it never certifies truth, readiness or authority (V3 directive, section 12).

CiteNS-1, clause 0. NXS-STD-ST-000001@0.1.0. https://nexustandards.com/standards/ns-1/#nx-c-0

0. Where the standard lives

This repository is the canonical home of the Nexus Standards: the documents under standards/, the machine registry under registry/, the record schema under schemas/, the STD-scope catalogue under catalog/ and the reference CLI under tools/. Consuming repositories (nexus-foundry, the WordPress plugin, institutional sites) implement the standard, keep their own catalogues for their own scopes, and never fork the registry; registry/consumers.yaml lists them with their status. Paths written as server/..., src/... or scripts/... in this document are paths inside the nexus-foundry consumer.

CiteNS-1, clause 1. NXS-STD-ST-000001@0.1.0. https://nexustandards.com/standards/ns-1/#nx-c-1

1. The UNI

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

NXS-<SCOPE>-<CAT>[-<DOMAIN>][-<SECTOR>][-<REGION>][-<ENV>]-<SERIAL>[@<VERSION>] NXS-EWS-DS-000042                    dataset 42 of the early-warning system NXS-EWS-DS-KEN-000003                a Kenyan early-warning dataset NXS-GRX-RP-M002-000007@1.2.0         report 7 of the data system for Africa, version 1.2.0 NXS-GRX-AR-WAT-CAN-000012            article 12 of the data system on water in Canada NXS-GRX-DP-WAT-WUT-CAN-PRD-000001    production deployment 1 of the data system for Canadian water utilities (NS-9) NXS-GCR-AR-000015                    an article published by GCRI Canada NXS-STD-ST-000001                    this standard
SegmentIfomuMeaning
NXSfixedPrefix. Chosen over NEX because it reads as a code, not a word; NEX- is crowded by brands (Nexo, Nexi, Nexor) and NXS is already the neutral system prefix in public-identity.json
SCOPEthree lettersA canonical system (EWS, EOP, SIG, GRX, OPS...), an organisation (GCR, GRF, GRA, NXO) or a cross-cutting scope (STD, LEG, GOV, PRG)
CATtwo lettersArtefact category, mapped to Zenodo upload and publication types and to DataCite resource types; or an NXS-GRX (canonical data, provenance and risk) record kind (OB, SR, IN, ME, BD, CT, CR, AP, SU, NS-3). The two lists never share a code
DOMAINoptional, three lettersNexus 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)
SECTORoptional, three lettersSector code from registry/sectors.yaml (AGR, WUT, EUT, HSY, FNI, TRL, CIT, INM, DTC, PUB, RED, HUO, IGO)
REGIONoptionalISO 3166-1 alpha-3 (KEN, CAN) or UN M49 region as M + three digits (M002 Africa, M142 Asia); registry registry/regions.yaml
ENVoptional, three lettersPRD production, STG staging, LBX lab, FIX fixture; used by contextual records (NS-9)
SERIALsix digitsAllocated by the catalogue or the UNI fabric per full prefix (SCOPE + CAT + context segments), never reused
VERSIONoptionalSemantic version of an artefact (1.2.0) or the integer recordVersion of an NXS-GRX record (3, NS-3). The UNI without 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 the M49 form (checked by 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: the data system, water domain, Canada. The context name is what articles, pages, datasets, deployments, dashboards and code about that context carry as their 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 (HTML landing page for browsers, JSON for machines, /uni/<uni>.json 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 (grix.eo.stac.catalogue) are UNI v0. They are recorded as legacyUni on the new record for crosswalk and are never allocated again.

CiteNS-1, clause 1.1. NXS-STD-ST-000001@0.1.0. https://nexustandards.com/standards/ns-1/#nx-c-1-1

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 people never need to read. The allocation rules exist so that no code ever becomes ambiguous, including after future changes in other code lists.

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

Grandfathered: AAP, the system scope of the anticipatory-action system. It was allocated before CA-3 and lies inside the user-assigned range AAA–AAZ. It stays, under CA-8.

Technology domains proposed under these rules:

CodeIdLabelCrosswalks to
CMPcomputeCompute and accelerated infrastructureISO/IEC JTC 1/SC 38 and SC 39; ISO/IEC 22123
DTWdigital-twinsAmawele edijithali nokulingisaISO/IEC 30173:2023; ISO/IEC JTC 1/SC 41; ISO 23247
SNSsensingSensing and measurement networksOGC SensorThings API and SensorML; W3C/OGC SOSA/SSN; IEEE 1451
PNTpntUkuthola indawo, ukuzulazula nesikhathiIEEE 1588; ITU-T G.8271 and G.8272; ITU-R TF series; UN ICG

Sensing and positioning-navigation-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–QZZ. CA-3 catches this kind of collision before allocation.

CiteNS-1, clause 2. NXS-STD-ST-000001@0.1.0. https://nexustandards.com/standards/ns-1/#nx-c-2

2. Scope codes

IsistimuCodeIsistimuCode
nexus (posture, executive synthesis)CMDsig (signal, timing, PNT)SIG
northstar (common operating picture)NSTnsf (trust, authorisation)the trust and assurance system
dss (decisions)DSShub (knowledge, records)HUB
nexcore (compute, runtimes)CORstudio (composition, workflows)STU
nexq (packages, models, capabilities)NXQfactory (builds, signing)FAC
grix (data, provenance, risk)GRXapps (application lifecycle)APP
eop (earth observation)EOPrails (agreements, protocols)RLS
ews (early warning)EWSportals (public, client, partner delivery)POR
aap (anticipatory action)AAPlabs (research, simulations)LAB
net (network continuity)NET
op (instruments, calibration)OPS

Organisations: GCR The Global Centre for Risk and Innovation (GCRI Canada) · GRF The Global Risks Forum · GRA The Global Risks Alliance · NXO the consortium · ELP and OBS reserved organisation scopes (withdrawn before use; parseable, never issued). Cross-cutting: STD standards · LEG legal and IP · GOV governance · PRG programme · UXK UI/UX kit · ALL ecosystem-wide.

Scope codes are classification, not names. Public labels follow the name architecture standard (nexus-foundry the network's own records); the trust and assurance system as a code is fine, "the trust and assurance system" as a public product name is not. The canonical systemId and neutralId stay unchanged.

CiteNS-1, clause 3. NXS-STD-ST-000001@0.1.0. https://nexustandards.com/standards/ns-1/#nx-c-3

3. Category codes

CodeArtefactZenodoDataCite
SWSoftwaresoftwareSoftware
SVService or APIsoftwareService
SCSchema or contractotherOther
MGDatabase migrationsoftwareSoftware
WFWorkflowworkflowWorkflow
MDImodelimodelImodeli
DSDatasetdatasetDataset
EVIrekhodi lobufakazidatasetDataset
ARArticlepublication / articleJournalArticle
PPPreprintpublication / preprintPreprint
RPReportpublication / reportReport
TNTechnical notepublication / technicalnoteText
DCImibhalopublication / softwaredocumentationText
DLDeliverablepublication / deliverableReport
WPWorking paperpublication / workingpaperText
BKBook or chapterpublication / bookBook
CPConference paperpublication / conferencepaperConferencePaper
THThesispublication / thesisDissertation
PTPatentpublication / patentOther
STIzingapublication / otherIzinga
PCPolicy or directivepublication / otherText
PSPresentationpresentationText
POPosterposterText
FGFigureimage / figureImage
PLPlot or visualisationimage / plotImage
DGDiagramimage / diagramImage
PHPhotoimage / photoImage
MPMap productimage / otherImage
VDVideovideoAudiovisual
LSLesson or courselessonInteractiveResource
PYPhysical objectphysicalobjectPhysicalObject
PAParticipation recordotherOther
RSProgramme status recordotherOther
OTOtherotherOther

node tools/nexus-id.mjs export <uni> --format zenodo produces Zenodo deposition metadata; --format datacite produces a DataCite-shaped record, so a catalogued artefact can be deposited or minted a DOI without re-describing it.

CiteNS-1, clause 3.1. NXS-STD-ST-000001@0.1.0. https://nexustandards.com/standards/ns-1/#nx-c-3-1

3.1 The public Registry crosswalk

The registry at therisk.global/nexus-registry/ (publisher GCRI Canada) shows record ids NX-R-nnnnn (programme status), NX-P-nnnnn (publication), NX-E-nnnnn (evidence) and NX-C-nnnnn (participation) with a version, a hash and a state. Those forms become display aliases of UNIs: NX-R-47092 → NXS-GCR-RS-047092, NX-P → RP (or AR, PP, WP when the record says so), NX-E → EV, NX-C → PA. The registry version becomes currentVersion, the hash versions[].digest, the state registryState (REGISTERED, CORRECTION_OPEN, RIGHTS_HOLD, WITHDRAWN). The page says no public record has been released yet, so nothing live breaks. Full rule: registry/nexus-standards.yaml#registryCrosswalk.

CiteNS-1, clause 4. NXS-STD-ST-000001@0.1.0. https://nexustandards.com/standards/ns-1/#nx-c-4

4. The record

Each UNI has one record in the catalogue (schema: nexus-artifact-record.v1.json). Required: uni, title, scope, category, status, creators, publisherRef, publicationDate, rights, legalState, claimCeiling, locations. Optional: region, systemId, legacyUni, description, keywords, language, currentVersion, versions (with git SHA and sha256 digest), relatedIdentifiers (DataCite relation types, so parts, derivations, supersessions and citations form a graph), supersededBy, workPackageId, directiveRefs.

Assurance fields: legalState defaults to LEGAL_REVIEW_REQUIRED; claimCeiling never exceeds the claim registry (FIXTURE_VERIFIED, IMPLEMENTATION_COMPLETE, INTEGRATED, LAB_OBSERVED); publisherRef is the institution for institutional artefacts (the institution stays publisher of record; ownership of the technology does not make its owner the publisher).

CiteNS-1, clause 5. NXS-STD-ST-000001@0.1.0. https://nexustandards.com/standards/ns-1/#nx-c-5

5. Rules

RuleText
NS1-R1One UNI per artefact concept; versions share the UNI and differ in @VERSION
NS1-R2UNIs are allocated only through the catalogue (mint); never typed by hand
NS1-R3UNIs are never deleted or reused. Withdrawn artefacts keep their record (WITHDRAWN); replaced ones record supersededBy
NS1-R4Every record carries the required metadata; legalState defaults to review-required; claimCeiling stays inside the claim registry
NS1-R5The UNI is embedded in the artefact itself so machines and people can find the record (section 6)
NS1-R6Regional artefacts carry REGION; public regional or national use still follows the name architecture's geographic rules
NS1-R7Codes are classification, never product names
NS1-R8New scope, domain, sector and environment codes meet the allocation rules CA-1 to CA-10 (section 1.1) and enter through an NS-13 proposal
NS1-R9A code is never reassigned or deleted; a retired code is deprecated with supersededBy, and identifiers that use it stay valid
NS1-R10A PROPOSED identifier may be used and is shown with its status until the registry change is adopted
CiteNS-1, clause 6. NXS-STD-ST-000001@0.1.0. https://nexustandards.com/standards/ns-1/#nx-c-6

6. Embedding: how each surface carries the UNI

SurfaceOwnerHow
Source filesthe trust and assurance systemHeader comment Nexus-UNI: <uni>
Documents and reportsHUBFront matter uni: or first line Nexus-UNI: <uni>
Datasets and productsGRXSidecar <file>.uni.json with the record, or a uni key in STAC and DataCite metadata
Figures and mapsEOPCaption suffix [<uni>] and image metadata
Foundry HTTP APIsthe trust and assurance systemResponse header X-Nexus-UNI: <uni> on every JSON response whose body carries a uni (server/middleware/uniHeader.ts); GET /api/uni/catalog, GET /api/uni/:uni, GET /api/uni/:uni/export?format=zenodo|datacite|schema-org|codemeta|citation-cff|stac|dcat|prov under the trust and assurance system scope; public GET /uni/:uni for PUBLISHED, non-restricted records with Schema.org JSON-LD
Rooms and panelsSTURoom-binding projects the payload uni (or uniKey) per source and shows it as a link; any cell that is a UNI links to /uni/<uni>; the trust and assurance system room's Standards surface reads the catalogue (ns6StandardsRoomDefinitions.ts)
PassportsGRXPASSPORT_UNI_FIELD (nexus:uni) is the first field of the shared Identity section; format uni links valid UNIs to /uni/<uni> and shows legacy dotted ids unlinked; the account passport links its registered UNI
Landing and Trust pagesPOR<meta name="nexus-uni" content="<uni>"> and data-nexus-uni on the component root
WordPress plugin and institutional sitesPORPost meta _nexus_uni (validated; uni in the provenance REST body), <meta name="nexus-uni"> and X-Nexus-UNI are wired in the plugin (the network's own records); block attribute nexusUni follows in NS-6. See nexus-foundry the network's own records
Agentsthe trust and assurance systemMint through the CLI and embed the UNI in every artefact produced

Every surface in registry/nexus-standards.yaml#surfaces has a status. A surface without a declared embedding is non-compliant; PLANNED means the hook is specified and not yet wired. NS-6 wired the API header and routes, rooms and passports; landing-page meta tags and JSON-LD follow with the resolver pages (NS-7).

CiteNS-1, clause 7. NXS-STD-ST-000001@0.1.0. https://nexustandards.com/standards/ns-1/#nx-c-7

7. Commands

node tools/nexus-id.mjs validate NXS-EWS-DS-000042 node tools/nexus-id.mjs parse NXS-GRX-RP-M002-000007@1.2.0 node tools/nexus-id.mjs next --scope EWS --category DS --region KEN node tools/nexus-id.mjs mint --scope EWS --category DS --title "Kenya flood observations 2026" \ --path the approved sources of the network --region KEN --publisher GCRI_CANADA --work-package RF-21 node tools/nexus-id.mjs catalog validate        # npm run validate node tools/nexus-id.mjs catalog list --scope GRX node tools/nexus-id.mjs export NXS-STD-ST-000001 --format zenodo
CiteNS-1, clause 8. NXS-STD-ST-000001@0.1.0. https://nexustandards.com/standards/ns-1/#nx-c-8

8. The open-standards stack

registry/open-standards-stack.yaml fixes the external standards and indexes under the UNI. the network's own records crosswalks a record to Zenodo deposition metadata, DataCite 4.5, Schema.org JSON-LD (for landing pages and Google Dataset Search), CodeMeta 3.0 and CITATION.cff; zenodoClient.ts deposits to Zenodo (sandbox by default, dry-run by default, token supplied by the publishing institution) after the legal gate zenodoDepositEligibility (APPROVED, open or embargoed, SPDX licence). The returned DOI is written back as relatedIdentifiers[IsIdenticalTo, DOI], so the UNI stays the key and the DOI is the citable crosswalk. Zenodo is registered in the network's legal texts#zenodo and external-apis.yaml#zenodo.deposit at LEGAL_REVIEW_REQUIRED.

Runtime hooks (NS-6): room-binding sources accept uniKey, every RoomSourceProjection carries uni and the room view links it; passports carry PASSPORT_UNI_FIELD in the shared Identity section with format uni; every JSON API response with a uni carries X-Nexus-UNI; /api/uni serves the catalogue and exports. The Global Risks Index (NXS-GRX) recordUni adopts the NS-1 grammar for new records with dotted ids kept as legacyUni (NS-3).

CiteNS-1, clause 9. NXS-STD-ST-000001@0.1.0. https://nexustandards.com/standards/ns-1/#nx-c-9

9. Relationship to the other standards

  • Name architecture (the network's own records): public display names and trademark safety. NS-1 is the machine layer underneath it; the two never contradict because codes are never names.
  • Claim registry (the network's own records): claimCeiling on every record.
  • Legal registers (the network's legal texts/**): legalState, publisherRef, rights.license.
  • UNI identifier fabric (V3 directive section 12): artefacts are allocated by the catalogue file (reconstructable source, served by /api/uni and /uni); NXS-GRX records are allocated by PostgreSQL nexus_uni (NS-3, the network's own records).
  • Work items: every work item lists the UNIs it creates or changes in evidenceOutputs.
CiteNS-1, clause 10. NXS-STD-ST-000001@0.1.0. https://nexustandards.com/standards/ns-1/#nx-c-10

10. Follow-on packages

Delivered: NS-3 NXS-GRX record UNIs (allocation, grammar, crosswalk; WDI bootstrap in use), NS-3b STAC, DCAT and PROV-O profile (the network's own records), NS-6 surface wiring, NS-7 resolver landing pages. Open: NS-2 citation and attribution format · per-path adoption of the record allocator (realDataObservationIngest, open-data ingests) · NS-4 document template with uni front matter · NS-5 figure, map and visualisation standard (with the UI/UX kit) · NS-7b SPA landing-page meta tags and sitemap · NS-8 Zenodo publishing workflow with legal gate, DOI write-back and Software Heritage archival.

Change history

Versions from the catalogue; entries from the changelog that name this document.

VersionDateNote
0.1.015 October 2026current version in the catalogue
  • Unreleased NS-13 proposal NXS-STD-PC-000004 (OPEN; last call ends 2026-11-16), the first proposal held as a record under proposals/ and checked by npm run validate: NS-1 section 1.1 sets context code allocation rules CA-1 to CA-10 and rules NS1-R8 to NS1-R10. ISO 3166-1 reserved and user-assigned code elements and ICAO Doc 9303 codes are now refused. AAP is grandfathered. It proposes four technology domain codes: CMP compute and accelerated infrastructure, DTW digital twins and simulation, SNS sensing and measurement networks, and PNT positioning, navigation and timing. The domains registry becomes schemaVersion 1.1.0 (minor, additive).
  • 0.1.0 – 2026-10-16 NS-1 (the UNI and the artefact catalogue), NS-3 (NXS-GRX record UNIs) and NS-3b (STAC, DCAT, PROV-O profile) as PROPOSED documents under standards/.
03Ucwaningo

Research, sources and files

Recent research on NS-1

Recent peer-reviewed articles, preprints, datasets and reports on the subject of this standard, 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; PID graph; DataCite Metadata Schema; in-toto Attestation Frameworkcombined with: research; data; metadata; infrastructure; FAIRDerived from the subject of the standard and its rules, and the external standards of its crosswalk domains.

  • 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.

04In practice

Where it applies and how it is developed

How it is developed and how to take part, the standard as a process, and the programme areas that list it.

How NS-1 is developed, and how to take part

NS-1 is developed in the open under NS-13 (the stages and gates of NS-13). Working groups draft, councils decide the reserved matters, and anyone may propose a change, comment, submit an implementation report, object or appeal, without membership or fee.

05Amazinga angaphandle

Relation to external standards

NS-1 relates to external standards by identifier, clause number and URL (NS14-R1), and directs the reader to the issuing body.

06Kuyo yonke inethiwekhi

Learning, the network and questions

Risk Academy courses and disciplines

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

Izifundo

Izifundo

The correspondence between courses, disciplines and the Nexus Standards is maintained with Risk Academy and is subject to its academic review.

ImibikoNikela

Nikela ngobufakazi kusuka kuleli khasi.

I-Reports iyincwadi yekota ye-Consortium. Lokho oakwaziyo ngalesi sihloko kungaba ubufakazi, icala noma ukulungisa kuhlelo olulandelayo, kubongwe wena futhi kushicilelwe ngaphansi kwe-CC BY 4.0 lapho kungumsebenzi wakho.

Nexus Standards
Amazinga

Bamba iqhaza ezindinganisweni.

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.

Isimo nokusetshenziswa. Ama-Nexus Standards angamazinga ahlongozwayo athuthukiswe ngenqubo evulekile ngaphansi kwe-NS-13 futhi ashicilelwe ukuze asetshenziswe ngokuzithandela; akusona isitifiketi, ukugunyazwa noma imvume yomlawuli, futhi ukwamukela kuhlala kuyisinqumo se-Global Standards Council futhi, ezweni ngalinye, se-National Standards Council yalo. I-UNI (Unique Nexus Identifier) ihlonza into; ayiyiqinisekisi. Amagama ezinhlaka zamazinga namazinga azo angawabaphathi bawo futhi asetshenziswa kuphela ukuhlonza amadokhumenti; awukho umbhalo wezinga langaphandle okhiqizwe kabusha lapha. I-Nexus Standards ayihlangene, ayesekwa futhi ayiqinisekiswanga yinoma iyiphi inhlangano yamazinga eshiwo lapha.

Amalayisense: i-CC BY 4.0 embhalweni wezindinganiso, amarejista, amaskimu nedatha; i-Apache-2.0 kukhodi yereferensi. Izindinganiso zangaphandle zicashunwa ngegama, inombolo nesixhumanisi ngaphansi kwamalayisense azo. Idatha, amalabhulali namafonti abantu besithathu agcina amalayisense awo: bheka Izaziso zabantu besithathu.