NXS · Foundations
NS-9 contextual UNIs for deployments and instances: what the standard requires and who it serves
NS-9 proposes that every deployment or programme instance gets its own identifier and record, separate from the system it instantiates. This explainer covers the grammar, the context record, resolution and display, and how rules and evidence bind to a context.
- En date du
- 3 November 2026
- Lecture
- 10 minutes
- Éléments probants
- 12 sources, cited in order
- Statut
- Proposed standard
- Code
- NS-9 · Contextual UNIs
Status and scope
A proposed standard. It is not adopted, approved or certified by any authority.
- Code
- NS-9 · Contextual UNIs
- Périmètre
- One identifier and one record for each deployment, instance or programme instance of a concept.
- S'applique à
- Deployments of systems and components, programme instances, command rooms and commons instances.
- 1 Grammaire
- 2 The context record
- 3 Resolution and display
- 4 Policies, clauses and monitoring
- 5 Règles
- 6 Adoption
01What NS-9 contextual UNIs are
What NS-9 contextual UNIs are
NS-9 contextual UNIs is the proposed Nexus Standard titled Contextual UNIs (deployments, instances, programme instances). Its identifier is NXS-STD-ST-000005 and its current version is 0.1.0, catalogued on 16 October 2026 1. The text is on the NS-9 page.
The standard starts from a simple observation. A system, component, product or service exists once as a concept and many times in context 1. Its examples include an early-warning system deployed for Kenya's water sector, the same system for a Sahel food-security programme, a data product published for an African region and a command room instance for one host city 1.
NS-9 gives each context its own UNI, so that a page, passport, report, policy, clause or monitoring record can say exactly which deployment it is about 1. The concept keeps one UNI, and the public name never changes with context 1. Its parent is NS-1 1,2. It is a preparatory working draft circulated for comment on 17 October 2026, and is not for implementation 1.
02Why a deployment needs its own identity
Why a deployment needs its own identity
A statement about a system is often really a statement about one installation of it. A forecast service may be well tested in one country and barely configured in another. A data product may be complete for one region and partial for the next. If both share a single name and identifier, a reader cannot tell which one a claim describes, and good evidence from one context can quietly lend credibility to another.
NS-9 prevents that by giving each context its own record and its own evidence. Rule NS9-R3 says a context's supported claim level, legal state and conformance evidence are its own, and are never inherited from the concept or from another context 1. A well-tested deployment in one place says nothing, under NS-9, about a new one somewhere else.
03The grammar: no new segments
The grammar: no new segments
Clause 1 adds no segment to the NS-1 grammar 1. A contextual UNI is an ordinary NS-1 identifier whose category is a context category and whose region segment carries the geography. Two categories serve this purpose. DP marks a deployment or instance of a system or component. PR marks a programme or engagement instance, a pathway run in a context 1.
The standard's examples show the pattern 1. NXS-EWS-DP-KEN-000001 is deployment 1 of the early-warning system in Kenya. NXS-EWS-DP-M011-000003 is deployment 3 of the same system in Western Africa, using the UN M49 code 011. NXS-GRX-DP-000002 is a global deployment of the data system, with no region at all 1. The M49 standard of the United Nations Statistics Division lists Western Africa under the code 011 3.
With the context segments of NS-1 grammar version 0.2, the identifier can also carry the domain, sector and environment. NXS-GRX-DP-WAT-WUT-CAN-PRD-000001 is production deployment 1 of the data system for Canadian water utilities 1. Its context name, the identifier without category and serial, is the name every page, article, dataset and dashboard about that deployment carries 1,2.
Fig. 01One concept, many contexts
Figure 1 in words
Column 1, concept: the early-warning system, with one concept UNI. Column 2, Kenya: deployment 1, region KEN. Column 3, Western Africa: deployment 3, region M011 from UN M49. Column 4, global: deployment 2 of the data system, no region. Each context has its own record and evidence.
04The context record
The context record
Clause 2 defines the context record as an NS-1 record with a context object 1. The required ofUni field names the concept the context instantiates: the system, component, product or programme. The record also carries an IsPartOf relation to that concept 1. IsPartOf is one of the relation types in DataCite's controlled list, paired with HasPart 4.
The domains and sectors fields hold one or more codes from the Nexus registers. The jurisdictions field holds country codes, subdivision codes where relevant, or a marker for international contexts. The hostRef field names the institution, host city, tenant or programme that operates the context 1.
The environment field is production, staging, lab or fixture, and the environment never raises a supported claim level 1. The validFrom and validUntil fields say when the context is live, and a closed context keeps its record. The conformsTo field lists the Nexus and external standards the context claims and evidences, under NS-11 and NS-14 1,5,6.
The region in the identifier is the primary geography, one country or one M49 region. Finer or multiple jurisdictions go in the record 1. The identifier is allocated by the consumer's catalogue for the scope, never typed by hand, and the catalogue is append-only 1.
05Concept and context in other vocabularies
Concept and context in other vocabularies
The split between a concept and its instances is familiar from other standards. In W3C PROV-O, an entity that is a specialisation of another shares all aspects of the latter and additionally presents more specific aspects of the same thing 7. A deployment is, in that sense, a specialisation of its system. It shares everything the system is, and adds what is particular to one place: who hosts it, which sectors it serves, when it went live and what evidence it has gathered so far. NS-9 does not name PROV-O for this purpose, so the comparison is one of logic rather than a stated mapping 1.
The W3C Data Catalog Vocabulary makes a related distinction between a dataset and a distribution, which it defines as a specific representation of a dataset 8. NS-9 applies the same kind of separation to systems and programmes. One concept record holds what is true everywhere; each context record holds what is true in one place, at one time, under one host 1.
Fig. 02Inside a context record
Figure 2 in words
Six layers from bottom to top. Of: the concept UNI, required, with an IsPartOf relation. Domains and sectors: one or more codes. Jurisdictions: country and subdivision codes, or international. Host, highlighted: the institution, city, tenant or programme that operates it. Environment and validity: production, staging, lab or fixture, with start and end dates. Conforms to: the Nexus and external standards claimed and evidenced.
06Resolution and display
Resolution and display
Clause 3 sets how a contextual UNI resolves 1. Its resolver path leads to the deployment's landing page, which shows the concept it instantiates, its domains, sectors, jurisdictions, host and environment, its conformance claims with their evidence state and the records it produces 1. The resolution model follows NS-1, where a UNI also has a URN form in the syntax of RFC 8141 2,9.
The display name is the concept's neutral public name plus a context phrase, for example Early Warning · Kenya · Water 1. The context phrase is derived from the record, never typed by hand, and never combines a geographic term with a protected mark in a way the naming rules forbid 1. Every page, passport, report and monitoring record about the deployment carries the contextual UNI, in a response header or a meta tag 1.
07Catalogued, not deposited
Catalogued, not deposited
NS-9 maps both context categories to the generic types other and Other for Zenodo and DataCite 1. It adds that a deployment is catalogued, not deposited, unless its evidence is published separately 1.
The distinction matters. The DOI system is documented in the DOI Handbook, which describes it at business and technical levels 10. A running deployment is not a publication: it changes, and its evidence accumulates. NS-9 keeps it in the catalogue as a living record, while any report or dataset it produces can still be deposited and receive its own DOI.
08Policies, clauses and monitoring bind to the context
Policies, clauses and monitoring bind to the context
Clause 4 says a policy or clause under NS-10 binds to a contextual UNI, not to a name 1,11. The standard's example reads: clause C applies to NXS-EWS-DP-KEN-000001 1. Verification and monitoring services under NS-11 observe a contextual UNI and record conformance per context 1,5.
A command room or commons instance is itself a context, so what it enforces is identifiable 1. That closes a loop: the place where rules are enforced has its own identifier, record and evidence, and can be checked in the same way as the deployments it governs.
Fig. 03From context to evidence
Figure 3 in words
Four rising steps. Context: a deployment or programme instance with its own record. Bound clause: an NS-10 clause bound to the contextual UNI, never to a name. Monitored: NS-11 services observe the context. Evidence per context, highlighted: conformance recorded for this context only, never inherited.
09The five rules in one place
The five rules in one place
Clause 5 condenses NS-9 into five rules 1. NS9-R1: one context record per deployment or programme instance, the concept keeps its own UNI, and the ofUni field is required and must resolve. NS9-R2: context identifiers are allocated by the catalogue for their scope, never derived from names or typed by hand. NS9-R3: a context's supported claim level, legal state and conformance evidence are its own, never inherited.
NS9-R4: closing a context never deletes it; its end date is set and its status becomes withdrawn or superseded, with a pointer to its successor. NS9-R5: display names in context follow the naming rules, and the UNI, not the name, is the key everywhere 1.
10First contexts to catalogue
First contexts to catalogue
Clause 6 names the first contexts to be catalogued 1. They include tenant deployments and command rooms, and the host cities and national hubs of The Global Risks Forum (GRF). They also include programmes per country of The Global Centre for Risk and Innovation (GCRI), and capital-readiness engagements of The Global Risks Alliance (GRA) 1. Each consumer records its contexts in its own catalogue under its own scopes 1.
These are plans in a draft standard, not a list of contexts already catalogued.
11Differences and open questions
Differences and open questions
Two points are worth noting for implementers. First, the jurisdictions field in NS-9 uses two-letter ISO 3166-1 country codes, while the region segment of an NS-1 identifier uses three-letter codes 1,2. A context such as Kenya therefore appears as KEN in its identifier and in two-letter form in its record. Implementers will need a mapping between the two. Second, NS-9 says the environment never raises a claim level, but does not yet say whether a lab or fixture context may carry conformance claims at all 1.
These are matters a later version could settle through an NS-13 proposal 12.
12Who NS-9 serves and how to take part
Who NS-9 serves and how to take part
The NS-9 page invites governments, regulators, standards bodies, industry, academia and communities to shape the catalogue by commenting on a draft, proposing a change, joining a working group or hosting a field exercise 1.
Changes follow the open process on Develop a standard, and comments go through the contact form. The standards are published by GCRI as Secretariat, and GRF and GRA take part as stakeholders like any other. Learners can study related methods in Risk Academy's Technology and Data course.
13Instruments named in or related to NS-9
Instruments named in or related to NS-9
The table lists external instruments NS-9 names or resembles, as published on 3 November 2026. Each is maintained by its own issuer and applies on its own terms.
| Instrument | Relation to NS-9 | Édition |
|---|---|---|
| UN M49 | Region codes such as 011 for Western Africa | Online edition 3 |
| DataCite relation types | IsPartOf link from context to concept | Schema 4.5 4 |
| W3C PROV-O | Specialisation of an entity | 30 April 2013 7 |
| W3C DCAT 3 | Dataset and distribution distinction | 22 August 2024 8 |
| RFC 8141 (IETF) | URN form of the identifier | April 2017 9 |
What this page does not claim: NS-9 is a proposed, preparatory working draft that its own page says is not for implementation, and no Nexus Standard has been adopted by the Global Standards Council or any National Standards Council. The identifiers quoted are the standard's own examples; this page does not report any deployment as live. The UN Statistics Division, DataCite, W3C, the IETF and the International DOI Foundation maintain their own instruments; Nexus Standards has no affiliation with any of them, and a comparison of models is not an alignment claim.
Questions
Questions et réponses
What is the difference between a concept UNI and a contextual UNI?
The concept UNI names a system, product or programme once. A contextual UNI names one deployment or programme instance of it, in one place and time.
Does NS-9 change the NS-1 identifier grammar?
No. A contextual UNI is an ordinary NS-1 identifier with the category DP or PR and, where relevant, a region and other context segments.
Can a deployment rely on the evidence of its parent system?
No. A context's claim level, legal state and conformance evidence are its own and are never inherited from the concept or another context.
What happens when a deployment closes?
Its record stays. The end date is set and the status becomes withdrawn or superseded, with a pointer to any successor.
What is NS-9's own status?
Proposed. Version 0.1.0 is a preparatory working draft circulated for review and comment, not for implementation, and changes go through NS-13 proposals.
Conditions
Glossaire
- Contextual UNI
- A UNI that names one deployment or programme instance of a concept.
- Déploiement
- An installed, operating instance of a system or component in a particular context.
- Programme instance
- One run of a programme or engagement pathway in a particular context.
- Nom du contexte
- A UNI without its category and serial, carried by every page and artefact about that context.
- Host
- The institution, city, tenant or programme that operates a context.
Voir aussi
Further reading across the network
- All Nexus Standards
- NS-9: Contextual UNIs
- NS-1: The UNI and the artefact catalogue
- NS-10: Policies and clauses
- NS-11: Verification and monitoring
- NS-13: Standards development process
- NS-14: Conformance and crosswalk
- Élaborer une norme
- Gouvernance des Nexus Standards
- Glossaire
- Le Global Risks Forum
- La Global Risks Alliance
Sources
References
12 sources, numbered in the order they are first cited
- Nexus Standards (2026-10-16). NS-9: Contextual UNIs (proposed). nexustandards.com. Accessed 2026-11-03.
- Nexus Standards (2026-10-15). NS-1: The UNI and the artefact catalogue (proposed). nexustandards.com. Accessed 2026-11-03.
- United Nations Statistics Division (). Standard country or area codes for statistical use (M49). unstats.un.org. Accessed 2026-11-03.
- DataCite e.V. (2024-01-22). relationType: DataCite Metadata Schema 4.5 documentation. datacite-metadata-schema.readthedocs.io. Accessed 2026-11-03.
- Nexus Standards (2026-10-16). NS-11: Verification and monitoring (proposed). nexustandards.com. Accessed 2026-11-03.
- Nexus Standards (2026-10-16). NS-14: Conformance and crosswalk to external standards (proposed). nexustandards.com. Accessed 2026-11-03.
- World Wide Web Consortium (W3C) (2013-04-30). PROV-O: The PROV Ontology. www.w3.org. Accessed 2026-11-03.
- World Wide Web Consortium (W3C) (2024-08-22). Data Catalog Vocabulary (DCAT), Version 3. www.w3.org. Accessed 2026-11-03.
- Internet Engineering Task Force (IETF) (2017-04). RFC 8141: Uniform Resource Names (URNs). www.rfc-editor.org. Accessed 2026-11-03.
- International DOI Foundation (2025-12). DOI Handbook. www.doi.org. Accessed 2026-11-03.
- Nexus Standards (2026-10-16). NS-10: Policies and clauses (proposed). nexustandards.com. Accessed 2026-11-03.
- Nexus Standards (2026-10-16). NS-13: Standards development process (proposed). nexustandards.com. Accessed 2026-11-03.
Fiche
Editorial record
Facts as of 3 November 2026. The NS-9 text, version and status were read on its page that day, and every external instrument was checked at its issuer the same day. The ISO 3166 pages refused automated access, so ISO 3166 is named only as NS-9 names it. This page is reviewed at least every 180 days and whenever NS-9 changes version or status. Text, visuals and data on this page are licensed CC BY 4.0.
Published by the Standards desk, Nexus Standards. Drafted with AI assistance under the Nexus editorial constitution. To report an error, use the corrections page; corrections are dated and listed here.
Cite this article
Standards desk, Nexus Standards (2026, November 3). NS-9 contextual UNIs for deployments explained. Nexus Standards. https://nexustandards.com/ns-9-contextual-unis-deployments-and-instances/
@online{standards2026ns9contextualunisdep,
author = {{Standards desk, Nexus Standards}},
title = {{NS-9 contextual UNIs for deployments explained}},
publisher = {Nexus Standards},
year = {2026},
month = {11},
url = {https://nexustandards.com/ns-9-contextual-unis-deployments-and-instances/},
language = {en}
} TY - ELEC AU - Standards desk, Nexus Standards TI - NS-9 contextual UNIs for deployments explained PB - Nexus Standards PY - 2026 DA - 2026/11/03 UR - https://nexustandards.com/ns-9-contextual-unis-deployments-and-instances/ LA - en ER -
Republish
Republish or translate this article free of charge, in print or online, under CC BY 4.0: keep the byline and Nexus Standards, link to the original and note any change. Figures, maps and twins made by the institutions carry the same licence; third-party data keeps its own credit line.
Attribution to paste
<p>NS-9 contextual UNIs for deployments and instances: what the standard requires and who it serves — Standards desk, Nexus Standards, Nexus Standards. First published 3 November 2026 at <a href="https://nexustandards.com/ns-9-contextual-unis-deployments-and-instances/">https://nexustandards.com/ns-9-contextual-unis-deployments-and-instances/</a>. Republished under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/).</p>
Comment on this draft
Comments are taken clause by clause, with the exact text you propose and your evidence, through the comment form on this site.