Skip to content
AmazingaNS-16Kuphakanyisiwe
NS-16

NS-16: UNI application profile (context names NXS-GRX-WAT-CAN; how articles, documents, code, data, APIs and interfaces carry the UNI)

NS-16 is a proposed Nexus Standard; the artefacts it governs are identified by UNIs (Unique Nexus Identifier). NS-1 defines the identifier and NS-9 the contextual record. NS-16 fixes how the identifier is applied: the one pattern that an article, a document, a source file, a dataset, an API response, a page, a dashboard panel and a citation all follow, so that anyone reading NXS-GRX-WAT-CAN anywhere knows it is the data system, water domain, Canada, and can walk from the name to the record, from the record to the evidence, and back. The worked example throughout is an article about the data system's water work in Canada.

NS-16 in the catalogue
The standards NS-16 depends on and those that cite it, then its sections with one mark for each numbered requirement.Source: NS-16-uni-application-profile.md; the Nexus Standards registry.
  • NS-16 depends on: NS-0, NS-1, NS-2, NS-3, NS-3b, NS-4, NS-5, NS-9, NS-10, NS-11, NS-12, NS-13, NS-14, NS-15.
  • NS-16 is cited by: NS-1, NS-9.
  • Section 1, The pattern: R1, R2, R3, R4.
  • Section 2, Articles and publications (AR, PP, RP, TN, WP, BK, CP, PS, PO): R5, R6, R7, R8.
  • Section 3, Documents, standards, policies and clauses (DC, ST, PC, CL, TN, DL): R9, R10, R11.
  • Section 4, Code, schemas, migrations and models (SW, SV, SC, MG, WF, MD): R12, R13, R14, R15.
  • Section 5, Data and records (DS, EV; NS-3 record kinds): R16, R17, R18.
  • Section 6, APIs and services (SV): R19, R20, R21, R22.
  • Section 7, Interfaces: pages, rooms, dashboards and passports: R23, R24, R25, R26, R27.
  • Section 8, Worked example: the data system's water work in Canada: no numbered requirement.
  • Section 9, Conformance (NS-14): no numbered requirement.
  • Section 10, Open items: no numbered requirement.
01Ukubuka konke

Summary

NS-16record
  1. Isimokuphakanyisiwe
  2. Responsible scopetrust; knowledge; public
  3. Rules stated0
  4. Programme areas0
  5. Source filesrepository

Nexus Standards · proposed

Requirements
27
numbered rules
Sections
10
in the text
Depends on
14
NS-0, NS-1, NS-2
Cited by
2
Nexus Standards
02The standard

NS-16: the standard

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

Code
NS-16
Title
UNI application profile (context names NXS-GRX-WAT-CAN; how articles, documents, code, data, APIs and interfaces carry the UNI)
Version
0.1.0
Isimo
KUHLONGOZIWE
Date
catalogue 2026-10-16 · circulated 17 October 2026
Unique Nexus Identifier
NXS-STD-ST-000015
Responsible scope
trust; knowledge; public
Umthombo
standards/NS-16-uni-application-profile.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, HUB, POR
Parent
NS-1-identifier-and-artifact-catalog.md (grammar v0.2), NS-9-contextual-uni.md

NS-1 defines the identifier and NS-9 the contextual record. NS-16 fixes how the identifier is applied: the one pattern that an article, a document, a source file, a dataset, an API response, a page, a dashboard panel and a citation all follow, so that anyone reading NXS-GRX-WAT-CAN anywhere knows it is the data system, water domain, Canada, and can walk from the name to the record, from the record to the evidence, and back. The worked example throughout is an article about the data system's water work in Canada.

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

1. The pattern (NS16-R1 to NS16-R4)

Context name   NXS-<SCOPE>[-<DOMAIN>][-<SECTOR>][-<REGION>][-<ENV>]            NXS-GRX-WAT-CAN Artifact UNI   NXS-<SCOPE>-<CAT>[-<DOMAIN>][-<SECTOR>][-<REGION>][-<ENV>]-<SERIAL>[@<VERSION>] NXS-GRX-AR-WAT-CAN-000012@1.0.0 Context record NXS-<SCOPE>-DP|PR[-<DOMAIN>][-<SECTOR>][-<REGION>][-<ENV>]-<SERIAL>   NXS-GRX-DP-WAT-CAN-000001
  • NS16-R1 One name, many artefacts. Everything about one context carries the same context name and differs only in CAT and SERIAL: the article NXS-GRX-AR-WAT-CAN-000012, the dataset NXS-GRX-DS-WAT-CAN-000004, the report NXS-GRX-RP-WAT-CAN-000002, the dashboard figure NXS-GRX-FG-WAT-CAN-000009, the deployment NXS-GRX-DP-WAT-CAN-000001, the clause NXS-GOV-CL-WAT-CAN-000003 (a clause's scope is its issuer, its context segments its subject).
  • NS16-R2 The name is derived, the UNI is allocated. A context name is never minted and never typed with a serial; it is computed from a UNI by dropping CAT and SERIAL. Writing NXS-GRX-WAT-CAN-000012 (no CAT) is an error, as is inventing a serial.
  • NS16-R3 Segments are codes, not words. WAT, CAN, WUT, PRD come from the registries (domains.yaml, sectors.yaml, regions.yaml, nexus-standards.yaml#identifier.environments); a jurisdiction label a form already holds (ISO 3166-1 alpha-2, GLOBAL, a regional label) maps to a REGION only through registry/jurisdictions.yaml, never by guess. A new domain or sector is a proposal under NS-13 before any artefact uses it. Prose spells the meaning next to the code on first use: "NXS-GRX-WAT-CAN (the data system, water, Canada)".
  • NS16-R4 Most specific true context, nothing more. An artefact carries only the segments that are true of all of it. A Canada-wide water article is …-WAT-CAN-…; a utilities-only article adds WUT; a global water method carries WAT alone; an artefact about two countries carries the M49 region that contains both or no REGION, with the countries in context.jurisdictions or the record's keywords. A segment is never added for search engine reasons.
CiteNS-16, clause 2. NXS-STD-ST-000015@0.1.0. https://nexustandards.com/standards/ns-16/#nx-c-2

2. Articles and publications (AR, PP, RP, TN, WP, BK, CP, PS, PO) (NS16-R5 to NS16-R8)

SurfaceCarriesExample
Front matter (Markdown, HTML head, DOCX core properties)uni, contextName, version, publisherRef, licenseuni: NXS-GRX-AR-WAT-CAN-000012, contextName: NXS-GRX-WAT-CAN
Title blocktitle; the UNI line under it in the document's identifier style; the context name as a chip"Water observations for Canadian basins" · NXS-GRX-AR-WAT-CAN-000012@1.0.0 · chip NXS-GRX-WAT-CAN
Running header or footerUNI with versionNXS-GRX-AR-WAT-CAN-000012@1.0.0 · page 3
Citation (NS-2)UNI, version, publisher, date, resolver URL… NXS-GRX-AR-WAT-CAN-000012@1.0.0. https://nexustandards.com/uni/NXS-GRX-AR-WAT-CAN-000012
Data and figures insideeach cited by its own UNI and version in the caption or table noteFigure 2 NXS-GRX-FG-WAT-CAN-000009@1, data NXS-GRX-DS-WAT-CAN-000004@2
WordPress_nexus_uni meta, <meta name="nexus-uni">, data-nexus-uni on the article root, slug derived from the title (never from the UNI)/water-observations-canadian-basins/
  • NS16-R5 An article's UNI is minted when the draft is created, not when it is published; the record is DRAFT until publication and never changes identifier.
  • NS16-R6 A new edition that changes claims is a new version (@2.0.0) of the same UNI; a translation is a version with language set; a new article is a new serial.
  • NS16-R7 Every number, figure, dataset and model the article relies on is cited by UNI and version; a claim without a citable record carries the NS-0 P6 wording ("not observed", "estimated", "declared").
  • NS16-R8 The article never names the system by a brand word; it names it by display name (NXS-GRX) and context name, with the meaning spelled on first use.
CiteNS-16, clause 3. NXS-STD-ST-000015@0.1.0. https://nexustandards.com/standards/ns-16/#nx-c-3

3. Documents, standards, policies and clauses (DC, ST, PC, CL, TN, DL) (NS16-R9 to NS16-R11)

  • NS16-R9 First line of every Markdown document: Nexus-UNI: <uni>; a context-specific document also carries the context name in its title block (NS-4). Standards themselves have no context segments (they are STD-scope and global).
  • NS16-R10 A policy or clause carries the issuer as SCOPE and the subject context as segments: NXS-GOV-PC-WAT-CAN-000001 is a governance policy for water in Canada; its appliesTo and subjects selectors list the same domain and jurisdiction, and the standards validator refuses a mismatch between segments and selectors.
  • NS16-R11 A clause's attestations (NXS-NSF-AT-…) carry no context segments of their own: the subject UNI inside the attestation carries them.
CiteNS-16, clause 4. NXS-STD-ST-000015@0.1.0. https://nexustandards.com/standards/ns-16/#nx-c-4

4. Code, schemas, migrations and models (SW, SV, SC, MG, WF, MD) (NS16-R12 to NS16-R15)

SurfaceCarriesExample
Source file header, line 1 or 2// Nexus-UNI: <uni> (the module's own UNI, scope of the owning system, no context segments)// Nexus-UNI: NXS-GRX-SW-000004
Context-specific module (a Canada water adapter)the module UNI with segments// Nexus-UNI: NXS-GRX-SW-WAT-CAN-000001
Package manifestnexus.uni, nexus.contextName"nexus": { "uni": "NXS-GRX-SW-000004" }
JSON Schema$id carries the repository path; x-nexus-uni carries the UNI"x-nexus-uni": "NXS-STD-SC-000002"
SQL migration-- Nexus-UNI: <uni> on line 2-- Nexus-UNI: NXS-GOV-MG-000001
Model card, dataset sheet (NS-12)uni, contextName, training-data UNIsNXS-GRX-MD-WAT-CAN-000002
Container image, SBOM, build attestationthe UNI as an OCI annotation org.nexus.uni and in the SBOM externalReferences
Gitcommit trailer Nexus-UNI: <uni> when a commit introduces or versions an artefact (optional, recommended)
  • NS16-R12 A code module's UNI identifies the module, not its deployments; a deployment is an NS-9 context record (DP) whose context.ofUni is the module or system UNI, and the deployment's context name (NXS-GRX-WAT-WUT-CAN-PRD) is what operators, dashboards and incident records use.
  • NS16-R13 The header UNI is checked by the repository validator against the catalogue; a header naming a UNI the catalogue does not hold fails CI.
  • NS16-R14 Configuration keyed by context uses the context name as the key (contexts["NXS-GRX-WAT-CAN"]), never a free-text label, so that configuration, records and pages join on one string.
  • NS16-R15 Identifiers in code are strings validated by the NS-1 library (parseNxsId); code never builds a UNI by concatenation except through formatNxsId with a serial the fabric returned.
CiteNS-16, clause 5. NXS-STD-ST-000015@0.1.0. https://nexustandards.com/standards/ns-16/#nx-c-5

5. Data and records (DS, EV; NS-3 record kinds) (NS16-R16 to NS16-R18)

  • NS16-R16 A dataset about a context carries the context segments: NXS-GRX-DS-WAT-CAN-000004. Its NS-3 records keep their own grammar (NXS-GRX-OB-CAN-000042@3): record kinds carry REGION and may carry DOMAIN and SECTOR; the dataset lists its records' UNIs in the STAC, DCAT and PROV-O crosswalks (NS-3b).
  • NS16-R17 Every table or file that stores records has a uni column or field holding the full UNI and, where it helps queries, a context_name column derived from it; the derivation is a function of the UNI, never a second source of truth.
  • NS16-R18 A map tile, figure or product rendered from data carries the UNIs of the data it rendered (NS-5) and its own UNI; a tile without a provenance UNI is a fixture and is labelled as one.
CiteNS-16, clause 6. NXS-STD-ST-000015@0.1.0. https://nexustandards.com/standards/ns-16/#nx-c-6

6. APIs and services (SV) (NS16-R19 to NS16-R22)

SurfaceCarries
Response headerX-Nexus-UNI: <uni of the primary record>; X-Nexus-Context: <context name> when the response is scoped to a context
Response bodyuni on every record; contextName on every list scoped to a context; never a derived score without the UNIs it came from
Requestcontext filters use the context name or its segments (?context=NXS-GRX-WAT-CAN or ?domain=WAT&region=CAN); never a free-text label
ResolverGET /uni/<uni> landing page or JSON; GET /ctx/<contextName> every published record of the context, newest first, by CAT
OpenAPIx-nexus-uni on the document and on every operation that serves a catalogued record
ErrorsRFC 9457 problem with uni and contextName when known, and the typed code (UNI_INVALID, UNI_NOT_IN_CATALOG, CONTEXT_UNKNOWN)
  • NS16-R19 A service's own UNI (SV) is in its health response; a service deployed for a context reports the deployment context record UNI (DP) and context name in /ready.
  • NS16-R20 An API never derives a context from the caller's address, language or tenant; the context is explicit in the request or on the record.
  • NS16-R21 List endpoints scoped to a context return records of that exact context name and, when ?include=narrower, of names that extend it (NXS-GRX-WAT-CAN includes NXS-GRX-WAT-WUT-CAN); never the reverse.
  • NS16-R22 Writes that create a catalogued artefact return 201 with the allocated UNI and the X-Nexus-UNI header; when the fabric is unavailable the response carries the typed uniAllocation state and the record stays DRAFT (NS-10/11 Commons adoption).
CiteNS-16, clause 7. NXS-STD-ST-000015@0.1.0. https://nexustandards.com/standards/ns-16/#nx-c-7

7. Interfaces: pages, rooms, dashboards and passports (NS16-R23 to NS16-R27)

ElementRule
Page head<meta name="nexus-uni">, <link rel="canonical"> to the resolver landing page, JSON-LD identifier
Umkhondo wokuzulazuladisplay name → context name chips in segment order → artefact: NXS-GRX › WAT › CAN › Article 000012
Identifier linethe full UNI with version in monospace, copy action, link to /uni/<uni>
Context chipNXS-GRX-WAT-CAN, one chip, links to /ctx/<contextName>; hovering spells each segment
Room panelevery row shows its UNI (or its typed pending state) and its supported claim level; a context panel is titled by the context name
Passport (NS-15)identity section: SU UNI first, then the contexts (DP, PR) the subject belongs to, each as a context chip
Filtersby segment with the registry labels (Domain: Water; Region: Canada), never free text
Empty state"No record is catalogued for NXS-GRX-WAT-CAN" with the typed reason, never a blank
  • NS16-R23 The UI never shows a score, badge, rank or "live" state for a context; it shows records, their UNIs and their recorded states (NS-0 P6).
  • NS16-R24 A context chip is where a context is named; free-text labels ("Canada water programme") are titles, never identifiers, and never appear without the chip.
  • NS16-R25 Tokens, type and both themes follow the UI kit; the identifier line uses the kit's monospace token; the chip uses the identifier style, never a brand colour.
  • NS16-R26 Every exported figure, CSV, PDF or image from a dashboard carries the UNIs of what it shows in its metadata and footer.
  • NS16-R27 Search indexes the UNI, the context name and each segment with its registry label, so that "Canada water" and NXS-GRX-WAT-CAN find the same records.
CiteNS-16, clause 8. NXS-STD-ST-000015@0.1.0. https://nexustandards.com/standards/ns-16/#nx-c-8

8. Worked example: the data system's water work in Canada

ThingUNIContext nameWhere it shows
The data systemNXS-GRX-SV-000001 (service)NXS-GRXsystem pages, health
Canadian water utilities production deploymentNXS-GRX-DP-WAT-WUT-CAN-PRD-000001NXS-GRX-WAT-WUT-CAN-PRDoperator room, /ready, incident records
Water observations dataset for CanadaNXS-GRX-DS-WAT-CAN-000004@2NXS-GRX-WAT-CANSTAC, DCAT, dataset page
One observation recordNXS-GRX-OB-CAN-000042@3NXS-GRX-CANrecord API, evidence lists
Water risk method cardNXS-GRX-MD-WAT-000002NXS-GRX-WATmethod registry
ArticleNXS-GRX-AR-WAT-CAN-000012@1.0.0NXS-GRX-WAT-CANnexustandards.com, citation, Zenodo deposit
Figure in the articleNXS-GRX-FG-WAT-CAN-000009@1NXS-GRX-WAT-CANcaption, export footer
Policy for Canadian water operatorsNXS-GOV-PC-WAT-WUT-CAN-000001NXS-GOV-WAT-WUT-CANCommons, room panel
Clause: observation coverageNXS-GOV-CL-WAT-CAN-000003NXS-GOV-WAT-CANCommons, evaluation
Attestation of the clause on the deploymentNXS-NSF-AT-000017none (subject carries the context)passport policy section, room panel

Reading any row: the display name tells which system, the chip tells where and about what, the UNI tells which artefact and version, the resolver tells what is recorded about it.

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

9. Conformance (NS-14)

LevelRequirements
NS-16 BasicR1, R2, R3, R9, R12, R13, R15, R19, R22, R23
NS-16 StandardBasic plus R4 to R8, R10, R14, R16, R17, R20, R21, R24, R27
NS-16 Fullevery rule

A consumer declares its level in registry/consumers.yaml; VERIFIED needs NS-11 attestations by a mandated evaluator (the repository validator and the API contract validator are the evaluators of R9, R13, R19 and R22).

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

10. Open items

  • NS16-O1 whether record kinds (NS-3) may carry DOMAIN and SECTOR in production allocations, or REGION only (fabric key change in nexus-foundry SQL 2033).
  • NS16-O2 the /ctx/ resolver's treatment of restricted records (count only, or omit).
  • NS16-O3 subdivision jurisdictions (ISO 3166-2, CA-ON) as a fifth segment or record-only; record-only until decided.
  • NS16-O4 (resolved 2026-10-16) how jurisdiction labels already held by forms reach the REGION segment: through registry/jurisdictions.yaml (alpha-2, GLOBAL and regional labels to alpha-3 or M49; EU deliberately absent), vendored and drift-tested by consumers.

Change history

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

VersionDateNote
0.1.016 October 2026current version in the catalogue

The changelog records no entry that names NS-16.

03Ucwaningo

Research, sources and files

Recent research on NS-16

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 termsapplication profile; metadata application profile; persistent identifiers; identifier scheme; Schema.org vocabulary; DataCite Metadata Schemacombined with: metadata; identifier; interoperability; dataDerived 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-16 is developed, and how to take part

NS-16 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-16 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 1 discipline of Risk Academy (risksacademy.com) that teach the knowledge and methods of NS-16. 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.