Nexus Standards · NS-9 · Proposed
NS-9
NS-9: Contextual UNIs (deployments, instances, programme instances)
NS-9 is a proposed Nexus Standard; the artifacts it governs are identified by UNIs (Unique Nexus Identifier). A system, component, product or service exists once as a concept and many times in context: a multi-hazard warning system deployed for the water sector of one country, the same system for a regional food-security programme, a data product published for one region, an operations centre instance for one host city. NS-9 gives each context its own UNI, so that a page, a passport, a report, a policy, a clause or a monitoring record can name exactly which deployment it concerns, while the concept keeps one UNI. The public name does not change with context and does not infringe any mark.
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.
Summary
- Statusproposed
- Responsible scopetrust, authorization and assurance
- Identifier
NXS-STD-ST-000005 - Rules stated5
- Programme areas41
- Document
standards/NS-9-contextual-uni.md - Source filesrepository
Nexus Standards · proposed
Status of NS-9
Preparatory working draft, circulated for review and comment. Not for implementation. Prepared and circulated by The Secretariat of the Nexus Standards, Global Centre for Risk and Innovation (GCRI Canada) (public@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.
Population, settlement and hazards in Southeast Asia
The map frames Southeast Asia as an example geography for the subject of NS-9; the frame gives context and is not a statement of where the standards apply. Shown at first: population density, 2020 (Gridded Population of the World v4.11, NASA SEDAC, CIESIN, Columbia University) and night-time lights, daily (VIIRS Black Marble, VNP46A2, NASA LAADS DAAC). The layer drawer adds flood water, 3-day composite (VIIRS Global Flood Product); active fires and thermal anomalies, last day (VIIRS NOAA-20 375 m, FIRMS); and 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
People and hazards
Keyboard, with the map focused
Hold Ctrl or ⌘ and scroll to zoom
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.
Where people live, night-time lights and the floods and fires public institutions answer to, framed on Southeast Asia.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 Earth · NASA EONETSources 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
- 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 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
- 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
- NASA Fire Information for Resource Management System (FIRMS), VIIRS 375 m active fire product, NASA LANCE; vector tiles 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.
- Live: NASA EONET Events are indicative, not authority warnings.
- 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
- Population density, 2020: Population: CIESIN, Columbia University, Gridded Population of the World v4.11 (2018), NASA SEDAC, CC BY 4.0 · static
- Night-time lights, daily: VIIRS Black Marble (VNP46A2), NASA LAADS DAAC · 12 Oct 2026
- Flood water, 3-day composite: VIIRS Global Flood Product, NASA LANCE · 14 Oct 2026
- Active fires and thermal anomalies, last day: VIIRS NOAA-20 375 m (FIRMS), NASA LANCE FIRMS · 13 Oct 2026
- True colour: VIIRS NOAA-20 corrected reflectance, NASA LANCE · 13 Oct 2026
NS-9 among the standards.
Fig.The standards on which NS-9 builds, those that cite it and the programme areas where it applies, from the texts and the registry.
The standard as a process
A concept is deployed in a context; the context record names the concept, domains, sectors, jurisdictions, host and environment; the catalog of the scope allocates the contextual UNI (Unique Nexus Identifier); the display name is derived from the record; policies bind to the context and are evaluated for it; a closed context keeps its record. 7 operations in 6 phases; each states its actor, its decision rule, the record it leaves and the rule identifiers it implements (9 rules of NS-9 and the standards it applies).
All operations in order (7)
- 01
Concept UNI start · Concept
A system exists once as a concept and many times in context.
- Who
- the publisher of the system, component, product or programme
- Decision rule
- the concept keeps its own UNI
- Record
- the concept's own UNI and record
- Implements
- NS9-R1
- 02
Context record record · Context
Domains and sectors are registry codes; jurisdictions are ISO 3166 codes; the environment never raises the claim level.
- Who
- the host institution
- Decision rule
- one context record per deployment or programme instance; ofUni is required and resolves
- Record
- context.ofUni, domains, sectors, jurisdictions, hostRef, environment and validity
- Implements
- NS9-R1, NS9-R3
- 03
Allocate DP or PR step · Allocation
The identifier alone names the context: its domain, sector, region and environment segments are read from the record.
- Who
- the catalog of the scope
- Decision rule
- allocated by the catalog for its scope, never derived from names
- Record
- a contextual UNI of category DP or PR with its region
- Implements
- NS9-R2, NS1-R2
- 04
Display name step · Display
Every page, passport, report and monitoring record about the context carries the contextual UNI.
- Who
- the publishing surface
- Decision rule
- display names follow the name architecture; the UNI is the key
- Record
- the concept's public name with a context phrase derived from the record
- Implements
- NS9-R5, NS1-R5
- 05
Bind policies step · Binding
Policies and clauses name the context they apply to; monitoring observes the context.
- Who
- the policy author
- Decision rule
- a clause binds to a contextual UNI, never to a name (NS-10)
- Record
- clauses bound to the contextual UNI
- Implements
- NS10-R2
- 06
Own evidence gate · Binding
Nothing is inherited from the concept or from another context.
- Who
- an evaluator with a mandate
- Decision rule
- a context's claim level, legal state and evidence are its own
- Record
- attestations for this context
- Implements
- NS9-R3, NS11-R1
- 07
Close the context end · Closure
The record of a closed context remains and resolves.
- Who
- the host institution
- Decision rule
- closing a context never deletes it
- Record
- validUntil set; status WITHDRAWN or SUPERSEDED with supersededBy
- Implements
- NS9-R4
Fig.Phases read left to right; each card names the operation, its actor and the record it leaves, and each edge label names the hand-over. Play, step or scrub; the detail panel gives the full text of the selected operation. Sources: NS-9: Contextual UNIs · NS-1: The UNI and the artifact catalog · NS-10: Policies and clauses · NS-11: Verification and monitoring.
NS-9 clause by clause
6 clauses and 5 rules as stated in the standard, presented with numbered clauses, stable rule anchors, versions and changes.
Grammar (unchanged)
NS-9 adds no segment to the NS-1 grammar. A contextual UNI is an ordinary NS-1 identifier whose category is a context category and whose REGION segment carries the geography:
NXS-<SCOPE>-DP[-<REGION>]-<SERIAL> a deployment or instance of a system or component NXS-<SCOPE>-PR[-<REGION>]-<SERIAL> a programme or engagement instance (a pathway run in a context) NXS-EWS-DP-KEN-000001 deployment 1 of a monitoring and warning system in Kenya NXS-EWS-DP-M011-000003 deployment 3 of a monitoring and warning system in Western Africa (UN M49 011) NXS-GRX-DP-000002 a global deployment of a risk data system (no region) NXS-GCR-PR-COL-000001 GCRI Canada programme instance 1 in ColombiaUnder NS-1 grammar v0.2, a contextual UNI also carries the domain, sector and environment of the context as segments, so that the identifier alone names the context: NXS-GRX-DP-WAT-WUT-CAN-PRD-000001 is production deployment 1 of a risk data system for Canadian water utilities, and its context name NXS-GRX-WAT-WUT-CAN-PRD (the identifier without CAT and SERIAL) is the name that every page, article, dataset and dashboard about that deployment carries (NS-16). The context object below remains the record of truth: finer jurisdictions, several domains or sectors, the host and the validity window are recorded there, and the segments in the identifier are the primary ones.
DP (deployment or instance) and PR (programme instance) are artifact categories in registry/nexus-standards.yaml#categories (append-only, NS1-R3). Their Zenodo and DataCite mappings are other and Other: a deployment is catalogued, not deposited, unless its evidence is published separately.
The context record
A contextual record is an NS-1 record (schema v1.1) with a context object:
| Field | Meaning |
|---|---|
context.ofUni | The concept the context instantiates: the UNI of the system, component, product or programme (required). The record also carries relatedIdentifiers[IsPartOf, <ofUni>]. |
context.domains | One or more domains from registry/domains.yaml (water, energy, food, health, biodiversity, climate and the other registered domains). |
context.sectors | One or more sectors from registry/sectors.yaml. |
context.jurisdictions | ISO 3166-1 alpha-2 country codes and, where relevant, ISO 3166-2 subdivision codes, or INTL for international. |
context.hostRef | The institution, host city, tenant or programme that operates the context (an entity reference from the implementing institution's register of legal entities). |
context.environment | production, staging, lab or fixture; the environment never raises a claim ceiling. |
context.validFrom / context.validUntil | When the context is in operation; a closed context keeps its record. |
context.conformsTo | The Nexus Standards and the external standards (registry/external-standards.yaml ids) that this context claims and evidences (NS-11, NS-14). |
REGION in the identifier is the primary geography (one country or one M49 area); finer or multiple jurisdictions are recorded in context.jurisdictions. The identifier is allocated by the implementation's catalog for the SCOPE (NS1-R2); the catalog is append-only.
Resolution and display
/uni/NXS-EWS-DP-KEN-000001resolves to the landing page of the deployment: the concept it instantiates, its domains, sectors, jurisdictions, host and environment, its conformance claims with their evidence state, and the records (NS-3) it produces.- The display name is the neutral public name of the concept followed by a context phrase, for example "Early warning · Kenya · Water". 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 marks policy forbids (NS0-P10).
- Every page, passport, report and monitoring record about the deployment carries the contextual UNI (NS1-R5), and an
X-Nexus-UNIheader ornexus-unimeta tag names it.
Policies, clauses and monitoring
A policy or clause (NS-10) binds to a contextual UNI, not to a name: "clause C applies to NXS-EWS-DP-KEN-000001". Verification and monitoring services (NS-11) observe a contextual UNI and record conformance per context. An operational environment that evaluates and enforces policies is itself a context (DP, under the scope of its functional class, for example CMD or STU), so that what it enforces is identifiable.
Rules
| Rule | Text |
|---|---|
| NS9-R1 | Each deployment or programme instance shall have one context record; the concept keeps its own UNI; context.ofUni is required and shall resolve. |
| NS9-R2 | Context identifiers shall be allocated by the catalog for their SCOPE; they shall not be derived from names or typed by hand. |
| NS9-R3 | The claim ceiling, legal state and conformance evidence of a context are its own; they shall not be inherited from the concept or from another context. |
| NS9-R4 | Closing a context shall not delete it: context.validUntil is set and the status becomes WITHDRAWN or SUPERSEDED with supersededBy. |
| NS9-R5 | Display names in context shall follow the marks policy; the UNI, not the name, is the key everywhere. |
Adoption
The domain and sector registers (registry/domains.yaml, registry/sectors.yaml) were populated from a study of the published sites of the participating institutions and are extended through NS-13 proposals. Each implementation records its contexts in its own catalog under its own scopes. Typical first contexts are deployments per jurisdiction and environment, programme instances per country (for example GCRI Canada programme instances), host-city instances of recurring events (for example those of the Global Risks Forum) and engagement instances (for example those of the Global Risks Alliance).
Changes between versions
One published version is available (0.1.0); a comparison between versions is shown once a second version is published.
Clause numbers follow the sections of the document; rule identifiers (NS9-R1, NS9-R2, NS9-R3…) are stable anchors. With script enabled, each clause and rule has a permalink and a machine-readable view (YAML and JSON), and the j and k keys move between clauses.
Programme areas that list NS-9
41 programme areas list NS-9.
- Water risk standardsTierNexus domainsStatusplanned
- Energy risk standardsTierNexus domainsStatusplanned
- Food and agriculture risk standardsTierNexus domainsStatusplanned
- Health risk standardsTierNexus domainsStatusplanned
- Biodiversity and nature risk standardsTierNexus domainsStatusplanned
- Climate risk standardsTierNexus domainsStatusplanned
- Pollution and hazardous substance standardsTierHazard and threat familiesStatusplanned
- Built systems hazard standardsTierHazard and threat familiesStatusplanned
- Information and cyber-physical hazard standardsTierHazard and threat familiesStatusplanned
- Society, conflict and economy hazard standardsTierHazard and threat familiesStatusplanned
- Systemic and compound hazard standardsTierHazard and threat familiesStatusplanned
- Frontier and exponential technology hazard standardsTierHazard and threat familiesStatusplanned
- Agriculture and land useTierSectors and industriesStatusplanned
- Water utilities and basinsTierSectors and industriesStatusplanned
- Energy utilities and gridsTierSectors and industriesStatusplanned
- Health systemsTierSectors and industriesStatusplanned
- Finance, insurance and capital marketsTierSectors and industriesStatusplanned
- Transport, logistics and supply chainsTierSectors and industriesStatusplanned
- Cities and the built environmentTierSectors and industriesStatusplanned
- Industry and manufacturingTierSectors and industriesStatusplanned
- Digital, telecom and platformsTierSectors and industriesStatusplanned
- Public sector and governmentTierSectors and industriesStatusplanned
- Humanitarian and civil societyTierSectors and industriesStatusplanned
- International organisations and multilateralsTierSectors and industriesStatusplanned
- Identification (the UNI)TierCross-cutting capabilitiesStatuswired
- Naming, marks and intellectual propertyTierCross-cutting capabilitiesStatusplanned
- Recognition pathway, The Global Risks Forum (GRF)TierReadiness pathwaysStatusplanned
- Capital pathway, The Global Risks Alliance (GRA)TierReadiness pathwaysStatusplanned
- Deployment servicesTierInfrastructure servicesStatusplanned
- Operational contexts and policy enforcementTierInfrastructure servicesStatusplanned
- Technological and industrial hazard standardsTierHazard and threat familiesStatusplanned
- Chemical hazard standardsTierHazard and threat familiesStatusplanned
- Cyber and digital risk standardsTierHazard and threat familiesStatusplanned
- Financial and economic risk standardsTierHazard and threat familiesStatusplanned
- Political and governance risk standardsTierHazard and threat familiesStatusplanned
- Conflict and security risk standardsTierHazard and threat familiesStatusplanned
- Societal and information risk standardsTierHazard and threat familiesStatusplanned
- Compound and cascading hazard standardsTierHazard and threat familiesStatusplanned
- Frontier technology risk standardsTierHazard and threat familiesStatusplanned
- AI and autonomous systems risk standardsTierHazard and threat familiesStatusplanned
- Commons and command roomsTierInfrastructure servicesStatusplanned
Recent research on NS-9
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; digital twin; provenance of deployments; contextual metadata; DataCite Metadata Schema; ORCID iDcombined with: identifier; provenance; context; deployment; instanceDerived 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.
NS-9 in the standards repository
The text, schemas, machine-readable files, registry rows, tests and history behind NS-9, on the main branch of the canonical repository. Text, registry, schemas and catalog are CC BY 4.0; tools and tests are Apache-2.0.
Source text
| File | What it holds | Links |
|---|---|---|
standards/NS-9-contextual-uni.md | NXS-STD-ST-000005 | Raw · History · Suggest an edit |
standards/INDEX.md | status and document of every standard | History |
Schemas
| File | What it holds | Links |
|---|---|---|
schemas/nexus-artifact-record.v1.json | Nexus artifact record (NS-1) | Raw |
schemas/nexus-attestation.v1.json | Nexus conformance attestation (NS-11) | Raw |
schemas/nexus-clause.v1.json | Nexus clause (NS-10) | Raw |
schemas/nexus-subject-passport.v1.json | Nexus subject passport envelope (NS-15) | Raw |
Machine-readable files
| File | What it holds | Links |
|---|---|---|
catalog/artifact-catalog.yaml | catalog records · 2 mentions | First mention, line 275 |
Registry rows
| File | What it holds | Links |
|---|---|---|
registry/subsites.yaml | Nexus Standards subsites - the systemic architecture of nexustandards.com · 30 rows or mentions | Line 37 |
registry/ecosystem-coverage.yaml | Nexus ecosystem coverage register (programme B corpus read) · 20 rows or mentions | Line 255 |
registry/nexus-standards.yaml | Nexus Standards NS-1 - the UNI (Unique Nexus Identifier) and artifact catalog · 2 rows or mentions | Line 178 |
registry/standard-packages.yaml | Standard packages - one package per external open standard on nexustandards.com · 2 rows or mentions | Line 60 |
registry/domains.yaml | Nexus domains (NS-9 context.domains, NS-10 subject selectors) · 1 row or mentions | Line 2 |
registry/review-investigations.yaml | Circulation for technical review and comment, and the technical review areas · 1 row or mentions | Line 58 |
registry/sectors.yaml | Sectors and industries (NS-9 context.sectors, NS-10 subject selectors) · 1 row or mentions | Line 2 |
Tests and validators
| File | What it holds | Links |
|---|---|---|
tools/build-site-pages.mjs | tool or validator | Line 214 |
tools/site-open-standards.mjs | tool or validator | Line 435 |
tools/validate.mjs | tool or validator | Line 150 |
Change history
| File | What it holds | Links |
|---|---|---|
| Commits to the text | every change to the text | · |
CHANGELOG.md | notable changes, by version | · |
release/manifest.json | release manifest with file digests | in-toto statement |
| Releases | tagged releases of the repository | · |
Propose a change
| File | What it holds | Links |
|---|---|---|
| Open a proposal on NS-9 | issue form: target, kind, rationale (NS-13) | Template |
| Issue form: comment | issue form | Template |
| Issue form: errata | issue form | Template |
| Issues that mention NS-9 | open and closed | · |
| Pull request template | what a change must carry: target, kind, rationale, validation | · |
CONTRIBUTING.md | pull requests, sign-off and checks | · |
GOVERNANCE.md | how registry codes and texts change | · |
How NS-9 is developed, and how to take part
NS-9 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.
- Who decides what: the decision-rights matrix.
- The process: stages, gates, review windows and appeals.
- Open gateways and calls: how to propose, comment, join a working group or request activation.
- Develop a standard: the development track and the lifecycle of each standard.
- NS-13 in the canonical repository.
Relation to external standards
NS-9 relates to external standards by identifier, clause number and URL (NS14-R1), and directs the reader to the issuing body.
Recent research and sources
Peer-reviewed articles, preprints, reports and datasets on the subject of this standard, retrieved at the time of reading from open scholarly metadata services (OpenAlex and Crossref) and listed with authors, venue, year, type and access status, with a link to each work. Curated references and related standards are listed first; recent works matched by subject follow and are listed for orientation.
Curated references
- RFC 8141: Uniform Resource Names (URNs)
IETF / RFC Editor · 2017 · Standard - FAIR Data Maturity Model: specification and guidelines
Research Data Alliance · 2020 · Official publication - The FAIR Guiding Principles for scientific data management and stewardship
Scientific Data · 2016 · Peer-reviewed - DataCite Metadata Schema 4.5
DataCite · 2024 · Standard - RFC 4052: IAB Processes for Management of IETF Liaison Relationships
IETF / RFC Editor · 2005 · Standard - The New Global Rulers: The Privatization of Regulation in the World Economy
Princeton University Press · 2011 · Peer-reviewed - The Emergence of Governance in an Open Source Community
Academy of Management Journal · 2007 · Peer-reviewed - OGC Technical Committee Policies and Procedures
Open Geospatial Consortium · 2023 · Official publication
Related standards and frameworks
- SoftWare Hash IDentifier (SWHID) Specification V1.2; ISO/IEC 18670:2025
Software Heritage; ISO/IEC JTC 1 - DataCite Metadata Schema 4.5
DataCite Metadata Working Group - UN M49 Standard country or area codes for statistical use
United Nations Statistics Division - W3C Decentralized Identifiers (DIDs) v1.0
W3C DID Working Group - Research Organization Registry (ROR)
ROR (California Digital Library, Crossref, DataCite) - ORCID iD (subset of ISNI, ISO 27729)
ORCID Inc. - Digital Object Identifier system - ISO 26324
ISO/TC 46/SC 9; International DOI Foundation - Open Badges 3.0
1EdTech Consortium
Search terms, derived from the subject of the standard and its rules: persistent identifier; digital twin; provenance of deployments; contextual metadata; combined with: identifier; provenance; context; deployment; instance. With JavaScript enabled, recent works matching these terms are listed from OpenAlex and Crossref.
Risk Academy courses and disciplines
1 course and 1 discipline of Risk Academy (risksacademy.com) that teach the knowledge and methods of NS-9. Each course lists its level, stream and learning hours.
Courses
Disciplines
The correspondence between courses, disciplines and the Nexus Standards is maintained with Risk Academy and is subject to its academic review.
Programmes, tracks and courses for this standard
GCRI Canada and Risk Academy work on the subject of NS-9 in distinct roles (research and evidence; education and training). Each entry states why it corresponds and the step it offers; each institution sets its own terms of participation.
Research and evidence
GCRI Canada
Research programmes that produce the observations, models and assessments these records describe.
Nexus RegistryRecords programme status and participation.Apply to this programme therisk.globalAll programmes of GCRI CanadaEducation and training
Risk Academy
Courses and disciplines that teach the knowledge and methods practitioners need to apply these standards.
Technology and DataRAT-204 · Intermediate · 19 learning hoursManaging risk data, AI, digital infrastructure and technology risk responsiblyTake this course All courses and disciplinesListed in the education and training section of this pageQuestions and answers.
What is the status of NS-9?
What does applying NS-9 establish?
How is a change to NS-9 proposed?
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.
- GatewayGW-STDSend it from this pageEvidence, a correction, a case, a method, a review, a translation or profile input. It arrives tagged with this page, so the editor who owns it receives it.
- ZenodoOpen depositDeposit it and submit to the communityPublish your own record on Zenodo with your ORCID iD, then submit it to the Nexus Reports community. Curators review it there; the DOI stays yours.
- Nexus ReportsGCRISee every way to contributeThe contribution types, how each is reviewed, what credit you receive, the licence and what is never accepted.
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.
The same subject across the Consortium.
Around the 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.
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.