Nexus Standards · NS-3 · Proposed

NS-3

NS-3: Risk record UNIs (grammar, legacy crosswalk, allocation authority)

NS-3 is a proposed Nexus Standard; the artifacts it governs are identified by UNIs (Unique Nexus Identifier). NS-1 gives artifacts (software, reports, datasets, figures) a UNI allocated by a catalog. NS-3 gives risk records (observation facts, source releases, indicator and measure definitions, boundary versions, chronotope versions, corrections, analytical products and subjects) a UNI allocated by a record allocation authority, on the same grammar, so that a record can be cited, resolved and crosswalked like any other artifact. A UNI identifies and resolves a record; it never certifies the record's truth (NS0-P8).

01Instrument

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.

02Overview

Summary

NS-3record
  1. Statusproposed
  2. Responsible scopetrust, authorization and assurance; canonical risk data, records and provenance
  3. IdentifierNXS-STD-ST-000003
  4. Rules stated0
  5. Programme areas47
  6. Source filesrepository

Nexus Standards · proposed

03Status

Status of NS-3

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.

04Earth observation

Hazards and exposure in South Asia

The map frames South Asia as an example geography for the subject of NS-3; 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.

Flood water, active fires and surface heat beside population and night-time lights, framed on South 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 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

05Canvas

NS-3 among the standards.

Canvas · NS-3 among the standardsProcess diagram
NS-3 in the standard setThe standards that NS-3 cites, the standards that cite it, and the groups of programmes that list it, as recorded in the texts and the programme register.

Fig.The standards on which NS-3 builds, those that cite it and the programme areas where it applies, from the texts and the registry.

06Process

The standard as a process

An ingest writes a record; its kind and region are selected; the record identifier service allocates the serial inside a scoped transaction or refuses with a typed reason; legacy identifiers are crosswalked; versions and corrections are integers on the same UNI (Unique Nexus Identifier), and products cite records as recordUni@recordVersion. 8 operations in 5 phases; each states its actor, its decision rule, the record it leaves and the rule identifiers it implements (6 rules of NS-3 and the standards it applies).

Process · A risk record's UNI from ingest to correction8 operations · 5 phases
A risk record's UNI from ingest to correction (NS-3)An ingest writes a record; its kind and region are selected; the record identifier service allocates the serial inside a scoped transaction or refuses with a typed reason; legacy identifiers are crosswalked; versions and corrections are integers on the same UNI, and products cite records as recordUni@recordVersion.
All operations in order (8)
  1. 01

    Record written start · Ingest

    Each record kind has a two-letter code that never coincides with an artifact category: OB, SR, IN, ME, BD, CT, CR, AP and SU.

    Who
    the ingest path of the governed data service
    Decision rule
    a new record is identified at write time (section 4)
    Record
    an observation, source release, indicator, boundary, chronotope, correction, product or subject record
  2. 02

    Kind and region decision · Allocation

    The record concept takes the kind and, where the record is about one place, the region; versions are added as @<integer>.

    Who
    the ingest path
    Decision rule
    the grammar NXS-GRX-<KIND>[-<REGION>]-<SERIAL> (section 1)
    Record
    kind code and region (ISO 3166-1 alpha-3 or UN M49)
  3. 03

    Store available gate · Allocation

    When the authoritative store cannot be reached the ingest receives a typed state and the record carries it; no serial is invented.

    Who
    the record identifier service
    Decision rule
    offline is a typed refusal; there is no memory fallback (section 3)
    Record
    an allocation, or a typed unavailable state
    Implements
    NS0-P12
  4. 04

    Allocate serial step · Allocation

    An atomic counter per scope, kind and region issues the serial; every allocation is recorded and isolated by account.

    Who
    the record identifier service, inside a scoped transaction
    Decision rule
    serials are never derived or typed by hand
    Record
    one append-only allocation row per serial
    Implements
    NS1-R2
  5. 05

    Crosswalk legacy id step · Crosswalk

    Existing record ids keep working in references and are crosswalked to the new UNI when one is allocated, so correction dependencies keep resolving.

    Who
    the record identifier service
    Decision rule
    legacy ids stay valid and are never allocated again (section 2)
    Record
    the legacy id kept beside the new UNI
    Implements
    NS1-R3
  6. 06

    Record version record · Versioning

    Each state of a record is cited as its UNI and integer version; a reference with a semantic version is not a record reference.

    Who
    the governed data service
    Decision rule
    a record carries an integer version; an artifact a semantic one
    Record
    recordUni@recordVersion, an integer version
    Implements
    NS1-R1
  7. 07

    Correction step · Versioning

    A correction never overwrites: it records what changed and why, and every product that depends on the record can be replayed.

    Who
    the source or the data steward
    Decision rule
    corrections add a version and keep the earlier ones
    Record
    a correction record (CR) and a new version
    Implements
    NS1-R3
  8. 08

    Cited by products end · Use

    A product lists its record references as dependencies, so a correction reaches every product that used the record.

    Who
    products, figures and reports
    Decision rule
    derived works cite the records they use (NS-2)
    Record
    record references that a correction replay walks
    Implements
    NS2-R1, NS2-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-3: Risk record UNIs · NS-0: Constitution and principles · NS-1: The UNI and the artifact catalog · NS-2: Citation and attribution format for UNIs.

07Specification

NS-3 clause by clause

3 clauses and 0 rules as stated in the standard, presented with numbered clauses, stable rule anchors, versions and changes.

Versions0.1.016 October 2026current versionchangelog0.6.0 (2026-10-19), complete release
1

Grammar

NXS-GRX-<KIND>[-<REGION>]-<SERIAL>              the record concept   (recordUni) NXS-GRX-<KIND>[-<REGION>]-<SERIAL>@<version>    one record version   (recordUni@recordVersion) NXS-GRX-OB-KEN-000042@3     observation fact 42 for Kenya, version 3 NXS-GRX-SR-000001           source release 1 (global)

GRX is the scope code of the functional class for canonical risk data, records and provenance. The version segment of a record is the integer recordVersion. The NS-1 grammar therefore accepts @3 as well as @1.2.0: an artifact carries a semantic version and a record an integer. A ref with a semantic version is not a record ref.

KindCodeKindCode
Observation factOBChronotope versionCT
Source releaseSRCorrection recordCR
Indicator definitionINAnalytical product recordAP
Measure definitionMESubject (place, asset, organisation)SU
Boundary versionBD

Record kinds and artifact categories never share a code (registry/nexus-standards.yaml#recordCategories; node tools/nexus-id.mjs catalog validate enforces this).

2

Legacy identifiers remain valid

Implementations may already hold records under other identifiers, for example obs:<source>:<key>, uni:source:<source-id>, uni:indicator:<code> or dotted ids such as data.eo.stac.catalogue. Such identifiers parse as LEGACY, continue to work in <ref>@<version> refs, and are crosswalked to an NS-1 UNI when one is allocated. Nothing is renamed in place: a record carries either an NS-1 recordUni (new records) or a legacy recordUni together with the allocated uni (optional during the transition).

3

Allocation

Serials are never derived or typed by hand (NS1-R2). An implementation that holds risk records allocates their UNIs under these requirements:

  • The serial shall come from an atomic counter per (GRX, kind, region), advanced only inside a transaction scoped to a verified tenant.
  • Every allocation shall be one append-only record: tenant, workspace, account, UNI, kind, region, serial, legacy id and the verified principal.
  • The legacy id shall be the idempotency key within an account: allocating the same legacy id twice returns the same UNI and reports that it was reused.
  • UNIs shall not be reused or reassigned. Update, deletion and truncation of allocation records shall be refused, and the UNI string shall always equal its segment values.
  • Counters hold no tenant data and may be shared; the crosswalk from legacy id to UNI is private to the account.
  • The account and principal shall come only from verified claims, never from a header, body or query parameter.
  • When the allocation authority is unavailable, allocation shall fail with a typed unavailable state; there is no in-memory fallback.

Example: allocating kind OB, region KEN, legacy id obs:wdi:KEN.SP.POP.TOTL.2020 yields NXS-GRX-OB-KEN-000042; version 3 of that record is cited as NXS-GRX-OB-KEN-000042@3.

Δ

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 () 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.

08Where it applies

Programme areas that list NS-3

47 programme areas list NS-3.

09System model and scenario simulator

System model and cascade scenario: NS-3 Risk record UNIs

A system model of the context of NS-3 built from the registry: 26 hazards, 25 systems, 10 sectors, 13 controls, 18 feeds, 17 indicators. The systems are 35 of the 87 areas that list NS-3 (cascading and systemic risk, finance and insurance, health, water, food and energy, infrastructure, hazards); the model shows where the records, data and controls that NS-3 governs sit in a cascade, and is not a reading of the standard's text. Select the components to include, choose an initiating hazard and run the scenario. Stress propagates through the hazard relations of the Nexus Hazard Standard (NHS-1), the exposure of each system, the recorded couplings and the sectors that carry the loss; adopted standards dampen transmission and live data sources support detection. All parameters are stated assumptions that the reader can adjust; results are illustrative scenario outputs for exercises and training, not forecasts or risk assessments. The Map view places the same run on an example geography, The Philippines, a region suited to the hazards named, with open data: Natural Earth boundaries, an H3 hexagon grid and NASA satellite layers for the initiating hazard. The geography serves exercises and training and is not an assessment of that place.

Hazards

  • HIV epidemic
  • Tropical cyclone
  • Earthquake
  • Ice-jam flood
  • Toxic gas release
  • Persistent organic pollutants
  • Natech event
  • Dam failure
  • Storm surge (set off downstream)
  • Intense rainfall (set off downstream)
  • River flood (set off downstream)
  • Flash flood (set off downstream)
  • Dangerous surf (set off downstream)
  • Widespread power outage (set off downstream)
  • Mass displacement (set off downstream)
  • Coastal flood (set off downstream)
  • Aftershock sequence (set off downstream)
  • Fault surface rupture (set off downstream)
  • Soil liquefaction (set off downstream)
  • Slope slide (set off downstream)
  • Rockfall (set off downstream)
  • Tsunami (set off downstream)
  • Building collapse (set off downstream)
  • Water supply failure (set off downstream)
  • Disaster and conflict debris (set off downstream)
  • Food and feed contamination (set off downstream)

Systems and couplings

Controls

  • NS-0 Constitution and principles
  • NS-3 Risk record UNIs (grammar, legacy crosswalk, allocation authority)
  • NS-11 Verification and monitoring (evidence, attestations, zero-trust conformance observation)
  • NS-9 Contextual UNIs (deployments, instances, programme instances)
  • NS-10 Policies and clauses (machine-readable obligations: definition, binding, evaluation and enforcement)
  • NS-14 Conformance and crosswalk to external standards
  • NS-5 Figure, map and visualization standard (with the UI/UX kit)
  • NRS-H61 Hazard family: Cascading failure (NHS-1 sys.cascade)
  • NRS-H60 Hazard family: Supply-chain and flow disruption (NHS-1 sys.supply-chain)
  • NRS-H62 Hazard family: Compound and multi-hazard events (NHS-1 sys.compound)
  • NRS-H41 Hazard family: Animal-to-human spillover (NHS-1 health.zoonotic)
  • NRS-H65 Hazard family: Planetary boundary transgressions (NHS-1 planet.boundary)
  • NRS-H43 Hazard family: Livestock and aquaculture epizootics (NHS-1 health.animal-health)

Observation

  • WHO Disease Outbreak News (listed for reference)
  • WAHIS animal health events (listed for reference)
  • GBIF occurrence API and downloads (listed for reference)
  • ERA5 reanalysis (Copernicus Climate Data Store) (listed for reference)
  • CHIRPS quasi-global gridded precipitation (listed for reference)
  • USGS earthquake GeoJSON summary feeds (listed for reference)
  • PubChem compound, hazard and GHS classification records (listed for reference)
  • eMARS Major Accident Reporting System (listed for reference)
  • Copernicus EMS rapid mapping activations (listed for reference)
  • OpenStreetMap planet and replication (listed for reference)
  • FAOSTAT (listed for reference)
  • FEWS NET food security outlooks and data (listed for reference)
  • IPC food insecurity classifications (listed for reference)
  • World Development Indicators (listed for reference)
  • Global Human Settlement Layer (listed for reference)
  • WorldPop gridded population (listed for reference)
  • Overture Maps buildings theme (listed for reference)
  • OpenStreetMap (listed for reference)
  • International Health Regulations capacity and health emergency preparedness
  • Proportion of countries adopting relevant national legislation and adequately resourcing the prevention or control of invasive alien species
  • Total official international support for national DRR actions
  • Direct economic loss attributed to disasters in relation to global GDP
  • Number of parties to international multilateral environmental agreements on hazardous waste and other chemicals
  • Hazardous waste generated per capita and proportion treated
  • Mortality rate attributed to unintentional poisoning
  • Number of disruptions to basic services attributed to disasters
  • Proportion of agricultural area under productive and sustainable agriculture
  • Indicator of food price anomalies
  • Prevalence of moderate or severe food insecurity in the population, based on the Food Insecurity Experience Scale
  • Direct agricultural loss attributed to disasters
  • Agricultural land (% of land area)
  • Direct economic loss in relation to global GDP, damage to critical infrastructure and number of disruptions to basic services, attributed to disasters
  • Proportion of local governments that adopt and implement local disaster risk reduction strategies in line with national strategies
  • Proportion of urban population living in slums, informal settlements or inadequate housing
  • Percentage of local governments that adopt and implement local disaster risk reduction strategies in line with national strategies

Example geography

  • The Philippines: 184 H3 hexagons at resolution 4
  • Night lights tonight, outages (VIIRS Day/Night Band), NASA GIBS
  • Rain rate, last half hour (IMERG), NASA GIBS
  • Surface water through cloud, 30 m (OPERA DSWx-S1 radar), NASA GIBS
  • Surface soil moisture (SMAP), NASA GIBS
10Research hub

Recent research on NS-3

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 termsdisaster loss data; disaster loss database; hazard event identifier; disaster event database; loss and damage data; DataCite Metadata Schema; ORCID iDcombined with: disaster; hazard; riskDerived 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.

11Source

NS-3 in the standards repository

The text, schemas, machine-readable files, registry rows, tests and history behind NS-3, 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

FileWhat it holdsLinks
standards/NS-3-grix-record-uni.mdNXS-STD-ST-000003Raw · History · Suggest an edit
standards/INDEX.mdstatus and document of every standardHistory

Schemas

FileWhat it holdsLinks
schemas/nexus-clause.v1.jsonNexus clause (NS-10)Raw
schemas/nexus-subject-passport.v1.jsonNexus subject passport envelope (NS-15)Raw

Machine-readable files

FileWhat it holdsLinks
machine/catalogue.jsonldJSON-LD · 1 mentionRaw · First mention, line 890
machine/catalogue.oscal.jsonOSCAL JSON · 1 mentionRaw · First mention, line 1131
machine/catalogue.ttlTurtle (RDF) · 1 mentionRaw · First mention, line 1734
catalog/artifact-catalog.yamlcatalog records · 2 mentionsFirst mention, line 151

Registry rows

FileWhat it holdsLinks
registry/ecosystem-coverage.yamlNexus ecosystem coverage register (programme B corpus read) · 63 rows or mentionsLine 145
registry/subsites.yamlNexus Standards subsites - the systemic architecture of nexustandards.com · 29 rows or mentionsLine 37
registry/standard-packages.yamlStandard packages - one package per external open standard on nexustandards.com · 9 rows or mentionsLine 52
registry/nexus-standards.yamlNexus Standards NS-1 - the UNI (Unique Nexus Identifier) and artifact catalog · 4 rows or mentionsLine 73
registry/dags.yamlProcess and pipeline graphs rendered by the site's DAG component (nxs-dag) · 3 rows or mentionsLine 244
registry/open-standards-stack.yamlOpen-standards and open-source stack under the UNI · 2 rows or mentionsLine 105
registry/review-investigations.yamlCirculation for technical review and comment, and the technical review areas · 1 row or mentionsLine 58
registry/risk-standards.source.yaml'Nexus Risk Standards: the systemic catalogue' · 1 row or mentionsLine 425
registry/risk-standards.yaml'Nexus Risk Standards: the systemic catalogue' · 1 row or mentionsLine 927

Tests and validators

Change history

FileWhat it holdsLinks
Commits to the textevery change to the text·
CHANGELOG.mdnotable changes, by version·
release/manifest.jsonrelease manifest with file digestsin-toto statement
Releasestagged releases of the repository·

Propose a change

FileWhat it holdsLinks
Open a proposal on NS-3issue form: target, kind, rationale (NS-13)Template
Issue form: commentissue formTemplate
Issue form: errataissue formTemplate
Issues that mention NS-3open and closed·
Pull request templatewhat a change must carry: target, kind, rationale, validation·
CONTRIBUTING.mdpull requests, sign-off and checks·
GOVERNANCE.mdhow registry codes and texts change·
12Develop and take part

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

NS-3 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.

13External standards

Relation to external standards

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

14Research

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

Related standards and frameworks

Search terms, derived from the subject of the standard and its rules: disaster loss data; disaster loss database; hazard event identifier; disaster event database; loss and damage data; combined with: disaster; hazard; risk. With JavaScript enabled, recent works matching these terms are listed from OpenAlex and Crossref.

15Education and training

Risk Academy courses and disciplines

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

16Across the network

Programmes, tracks and courses for this standard

GCRI Canada and Risk Academy work on the subject of NS-3 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.

Data and ComputeEngineers public-interest data infrastructure.Apply to this programme therisk.globalAll programmes of GCRI Canada
17Questions

Questions and answers.

What is the status of NS-3?
NS-3 is proposed. It may be applied voluntarily; adoption follows last call and a decision of the Global Standards Council, and national adoption is decided by each National Standards Council.
What does applying NS-3 establish?
Applying NS-3 is a statement by the implementer, verifiable under NS-11 where machine-readable clauses exist.
How is a change to NS-3 proposed?
By a proposal naming NS-3, the section concerned and the rationale; it passes review and last call under NS-13.
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.