Nexus Standards · Consoles · Routing

Which standards apply

Which standards apply: routing console and composer

For a selected sector, hazard family, capability, jurisdiction and artifact type, the routing console identifies the corresponding programme areas of the registry, the Nexus Standards those areas list and the external standards in their domains, stating the reason for each; the composer turns the result into a draft profile that can be cited and downloaded. Each artifact carries a UNI (Unique Nexus Identifier).

01Overview

Summary

How routing worksdeterministic
  1. 01Contextregistry identifiers, not free text
  2. 02Areassector, hazard and capability tags mapped to programme areas
  3. 03Standardsthe Nexus Standards listed by those areas
  4. 04Externalregistry entries in the areas' domains, by relation and access
  5. 05Profilea draft with citations, submitted as a proposal under NS-13

The same registry version always gives the same result.

02Route

Context routing with reasons

The example below is computed when the page is built; in the browser, each selection is recomputed from the registry relations delivered with the page.

Routing console · which standards apply to my contextFrom the registry
Selected contextworked example
  1. SectorFinance, insurance and capital markets
  2. Hazard familyHydrometeorological hazard standards
  3. CapabilityData and datasets
  4. Jurisdictionany (jurisdiction is not yet tagged in the registry)
  5. Artifact typeDS · Dataset

4 areas · 8 Nexus Standards · 102 external entries

Nexus Standards that apply

Nexus StandardStatusWhy it is routed
NS-0 Constitution and principlesPROPOSEDFinance, insurance and capital markets; Hydrometeorological hazard standards
NS-1 The UNI and the artifact catalog (grammar v0.2:…PROPOSEDIdentification (the UNI)
NS-3 Risk record UNIs (grammar, legacy crosswalk,…PROPOSEDHydrometeorological hazard standards; Data and datasets; Identification (the UNI)
NS-3b Dataset and product metadata profile (STAC, DCAT,…PROPOSEDHydrometeorological hazard standards; Data and datasets
NS-9 Contextual UNIs (deployments, instances, programme…PROPOSEDFinance, insurance and capital markets; Identification (the UNI)
NS-10 Policies and clauses (machine-readable obligations:…PROPOSEDFinance, insurance and capital markets
NS-11 Verification and monitoring (evidence, attestations,…PROPOSEDFinance, insurance and capital markets; Hydrometeorological hazard standards; Data and datasets
NS-14 Conformance and crosswalk to external standardsPROPOSEDFinance, insurance and capital markets

External standards in the areas' domains (first 18 of 102)

StandardBodyRelationAccessWhy it is routed
BCBS 239 Principles for effective risk data aggregation and risk…Basel Committee on Banking Supervision…adoptopenFinance, insurance and capital markets · domain Finance and capital
C2PA Content Credentials specificationCoalition for Content Provenance and…adoptopenData and datasets · domain Provenance and evidence
CARE Principles for Indigenous Data GovernanceGlobal Indigenous Data AllianceadoptopenData and datasets · domain Data and datasets
DataCite Metadata Schema 4.5DataCite Metadata Working GroupadoptopenIdentification (the UNI) · domain Identifiers and cataloguing
FAIR Guiding Principles for scientific data management and stewardshipWilkinson et al. 2016; GO FAIRadoptopenData and datasets · domain Data and datasets
GOOS Essential Ocean VariablesIOC-UNESCO Global Ocean Observing SystemadoptopenFinance, insurance and capital markets; Hydrometeorological hazard standards · domain Climate
Handbook on Constructing Composite Indicators (OECD and JRC) and JRC…OECD and European Commission JRCadoptopenData and datasets · domain Data and datasets
in-toto Attestation Frameworkin-toto project (CNCF)adoptopenData and datasets · domain Provenance and evidence
IPCC AR6 Working Group II - risk framing (hazard, exposure,…Intergovernmental Panel on Climate…adoptopenFinance, insurance and capital markets; Hydrometeorological hazard standards · domain Climate
ISO 3166-1 Codes for the representation of names of countries and…ISO/TC 46; ISO 3166 Maintenance Agencyadoptfree-to-readIdentification (the UNI) · domain Identifiers and cataloguing
JSON-LD 1.1W3CadoptopenData and datasets · domain Data and datasets
OASIS Common Alerting Protocol Version 1.2OASIS Emergency Management TCadoptopenHydrometeorological hazard standards · domain Early warning and anticipatory action
OGC API - Features - Part 1: CoreOpen Geospatial ConsortiumadoptopenData and datasets · domain Geospatial and Earth observation
OGC GeoSPARQL - A Geographic Query Language for RDF DataOGCadoptopenData and datasets · domain Geospatial and Earth observation
OGC SensorML encoding standardOGCadoptopenData and datasets · domain Geospatial and Earth observation
Open Badges 3.01EdTech ConsortiumadoptopenIdentification (the UNI) · domain Identifiers and cataloguing
ORCID iD (subset of ISNI, ISO 27729)ORCID Inc.adoptopenIdentification (the UNI) · domain Identifiers and cataloguing
OWL 2 Web Ontology LanguageW3CadoptopenData and datasets · domain Data and datasets
Canvas · how a context is routedProcess diagram · 7 operations
Which standards apply: from context tags to a profile draftContext tags (sector, hazard family, capability, jurisdiction, artifact type) resolve to programme areas; each area lists Nexus Standards and crosswalk domains; external entries are filtered by relation and access; the result is a list with reasons, a profile draft and, where the adopter chooses, a change proposal. The diagram shows the process as specified; it does not report the status of any standard, proposal or record.
All operations in order (7)
  1. 01

    Context tags start · Adopter

    The adopter selects a sector, a hazard family, a capability, a jurisdiction and an artifact type, each a controlled registry value.

    Who
    the adopter
    Decision rule
    tags are registry identifiers: sectors, hazard families, capabilities, categories and, where recorded, jurisdictions
    Record
    a set of tags
  2. 02

    Programme areas step · Routing engine

    The same registry version gives the same result; each row states which programme matched.

    Who
    the engine, deterministically
    Decision rule
    sector, hazard and capability tags map to programmes by registry identifier
    Record
    the matching programmes
  3. 03

    Nexus Standards step · Routing engine

    Standards are listed with their status as recorded in the registry.

    Who
    the engine
    Decision rule
    the standards each programme lists, with status and rule count
    Record
    the standards the areas list
  4. 04

    External entries step · Routing engine

    External standards are named and linked; the relation is as recorded in the register.

    Who
    the engine
    Decision rule
    the entry's domain is a crosswalk domain of the programme
    Record
    register entries in the areas' domains
  5. 05

    Relation and access filter gate · Routing engine

    Each row states its reason: programme, domain, relation and access.

    Who
    the engine
    Decision rule
    adopt and profile first; paywalled crosswalk, profile and extend relations shown as compatibility profile (restricted)
    Record
    the filtered list with reasons
  6. 06

    Profile draft record · Result

    The composer turns the result into a profile draft for download.

    Who
    the adopter, from the result
    Decision rule
    a profile cites every source by identifier and clause; the licence line travels with it
    Record
    a profile as YAML and JSON with citations
  7. 07

    Change proposal end · Nexus Standards editors

    A change proposal is a pull request with the profile record; editors decide with written reasons.

    Who
    any person, with identity recorded
    Decision rule
    every submission is a change proposal under NS-13
    Record
    a change proposal with the profile record

Fig.Each selection lights the operation it feeds; the result keeps its reasons. Sources: Nexus Standards programme register · NS-14: crosswalk and conformance claims · NS-9: contextual UNI.

The routing is deterministic: the same registry version gives the same result, and each row states the area, domain and relation that routed it. Jurisdiction does not yet narrow the result, as the registry does not yet carry jurisdiction tags.

03Earth observation

Hazards and exposure in South Asia

The map frames South Asia as an example geography for routing a question to the applicable standards; the frame gives context and is not a statement of where the standards apply. Shown at first: flood water, 3-day composite (VIIRS Global Flood Product, NASA LANCE); active fires and thermal anomalies, last day (VIIRS NOAA-20 375 m, FIRMS, NASA LANCE FIRMS); and population density, 2020 (Gridded Population of the World v4.11, NASA SEDAC, CIESIN, Columbia University). The layer drawer adds land surface temperature, day, 8-day composite (VIIRS NOAA-20 Level 3, 8-day); night-time lights, daily (VIIRS Black Marble, VNP46A2); and aerosol optical depth, daily (VIIRS NOAA-20 Deep Blue AOD). 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 3

Hazards and exposure

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.

Hazards and exposure, framed on South Asia. Layers as NASA publishes them, each with its own date.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 EONET · U.S. Geological SurveySources and licences

  • We acknowledge the use of imagery provided by services from NASA's Global Imagery Browse Services (GIBS), part of NASA's Earth Science Data and Information System (ESDIS). Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
  • We acknowledge the use of imagery provided by services from NASA's Global Imagery Browse Services (GIBS), part of NASA's Earth Science Data and Information System (ESDIS). Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
  • VIIRS 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
  • 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
  • MODIS and VIIRS atmosphere products, NASA LANCE and LAADS DAAC; imagery via NASA GIBS. Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
  • ASTER GDEM is a product of METI and NASA (ASTER Global Digital Elevation Model V003, NASA LP DAAC); imagery via NASA GIBS. Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). Cite as: NASA/METI/AIST/Japan Spacesystems and U.S./Japan ASTER Science Team (2019). ASTER Global Digital Elevation Model V003. doi:10.5067/ASTER/ASTGTM.003. NASA open data
  • Made with Natural Earth. Free vector and raster map data @ naturalearthdata.com. Public domain
  • © OpenStreetMap contributors (ODbL), via NASA GIBS (coastlines, boundaries, roads and place names). Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). ODbL
  • Blue Marble, NASA Earth Observatory; imagery via NASA GIBS. Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
  • Context on the globe and flat map: coastlines, boundaries, roads and place names from NASA GIBS reference layers (OpenStreetMap data, ODbL, © OpenStreetMap contributors); Blue Marble imagery as an optional base; 3D terrain and the elevation read-out from the ASTER GDEM elevation colour index (5 m to 200 m classes, exaggerated for legibility). Boundaries are drawn as published and imply no position on any territory.
  • Globe: MapLibre GL JS 6.9.1, BSD-3-Clause, © MapLibre contributors.
  • Live: NASA EONET Events are indicative, not authority warnings.
  • Live: U.S. Geological Survey 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 (8 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

  • 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
  • Population density, 2020: Population: CIESIN, Columbia University, Gridded Population of the World v4.11 (2018), NASA SEDAC, CC BY 4.0 · static
  • Land surface temperature, day, 8-day composite: VIIRS NOAA-20 Level 3, 8-day, NASA LANCE · 14 Sep 2026
  • Night-time lights, daily: VIIRS Black Marble (VNP46A2), NASA LAADS DAAC · 12 Oct 2026
  • Aerosol optical depth, daily: VIIRS NOAA-20 Deep Blue AOD, NASA LANCE · 13 Oct 2026

04Compose

Composing a profile from standards and clauses

Select Nexus Standards and their rules, add external standards by registry entry, and view the profile as YAML or JSON for copying, citation or download.

Composer · select standards and clauses; view, cite and download the profileFrom the registry
kind: profile schemaVersion: "0.1.0-draft" title: "Profile draft" status: DRAFT nexusStandards: - id: NS-1 uni: NXS-STD-ST-000001 status: PROPOSED clauses: [NS1-R1, NS1-R2] - id: NS-3b uni: NXS-STD-SW-000005 status: PROPOSED clauses: [] - id: NS-11 uni: NXS-STD-ST-000007 status: PROPOSED clauses: [NS11-R1, NS11-R2] externalStandards: - id: stac relation: adopt clauses: [] licence: "Nexus Standards text, registries, schemas and data CC BY 4.0; reference code Apache-2.0" note: "A UNI (Unique Nexus Identifier) identifies an artifact; it does not certify it." submit: "a proposal under NS-13, recorded as a public change record"

A profile is a draft stating which Nexus clauses and which external standards apply to an artifact or a context; external obligations are cited by identifier and clause number. Validation checks the structure of the draft. Composition takes place in the browser, and the draft is not transmitted.

05Sources

Registry files used by the console

Registry fileContent used
registry/sectors.yamlsectors and the programme area of each
registry/subsites.yamlprogramme areas, the standards they list and their crosswalk domains
registry/external-standards.yamlentries with body, version, relation, access and URL
standards/INDEX.mdstatus and rules of the Nexus Standards
registry/nexus-standards.yamlartifact categories (the artifact type)

Per-rule artifact tags are being added to the registry; until then, the artifact type adds the identification standards area.

06Questions

Questions and answers.

Is a routed standard a requirement?
No. The console lists the standards that the registry relates to the selected context and the reason for each. Obligations arise from law, contracts and the bodies entitled to set them.
How is a profile submitted?
The draft is downloaded to the reader's device. It may then be submitted as a proposal under NS-13, by pull request against the canonical repository.
NRNexus Reports gateway · GW-STD

Contribute to Nexus Reports from this page.

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

Nexus Standards
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.