Skip to content

NXS · Foundations

NS-3 risk record UNIs in water and food systems, explained for implementers

What the proposed NS-3 would mean for river readings, drinking-water figures, crop estimates, prices and food security data: one identifier and version per record, traceable corrections and legacy codes kept valid.

En date du
3 November 2026
Lecture
10 minutes
Éléments probants
13 sources, cited in order
Statut
Proposed standard
Code
NS-3 · Risk record UNIs
NEXUS TWIN · WF-1 · TERRAINSEED 0612e252NXS-M03.APPLIES.NS-3xyzSCHEMATIC · TERRAINST-01 · 0.647 0.615ST-02 · 0.534 0.583ST-03 · 0.427 0.234
WF-1 · terrain Schematic wireframe twin (terrain, basin and reservoir). An illustration, not data.

Status and scope

A proposed standard. It is not adopted, approved or certified by any authority.

Code
NS-3 · Risk record UNIs
Périmètre
A UNI for every record of the risk data system, here the water and food records the programme draws on.
S'applique à
Observations, releases, indicators, boundaries and corrections in water and food systems.
  1. 1 Grammaire
  2. 2 Legacy ids stay valid
  3. 3 Attribution
  4. 4a Adopted paths

01What NS-3 risk record UNIs mean for water and food systems

What NS-3 risk record UNIs mean for water and food systems

NS-3 risk record UNIs is the proposed Nexus Standard NS-3 that gives every record of the risk data system a UNI on the same grammar as other artefacts 1. Its record kinds include observation facts, source releases, indicator definitions, measure definitions, boundary versions, corrections, analytical products and subjects such as places or assets 1.

The Water and Food Systems programme lists NS-3 in five of its six areas: water risk, food and agriculture risk, agriculture and land use, water utilities and basins, and food security and nutrition risk, and also in the FAO and food security area 2. This explainer shows what NS-3 would mean for the records those areas use. It builds on the programme's standards landscape.

NS-3 is a preparatory working draft, version 0.1.0, circulated for comment on 17 October 2026 and not for implementation 1.

02Why water and food data need record identifiers

Why water and food data need record identifiers

The programme describes a chain in which a drought shows first in a basin, then in a harvest, then in a market price and a nutrition record 2. Each step in that chain is built from records: a discharge value at a gauge, a crop condition estimate, a monthly price, a survey result. Each comes from a different source with its own release cycle.

When those records lack stable names, joining them depends on file names and column headers that change between releases. An analyst who wants to show that low river flow preceded a poor harvest must be able to say exactly which discharge series, at which release, and which crop estimate, at which revision. NS-3 provides that name, and NS-2 provides the way to cite it 1,3.

03The grammar applied to water and food records

The grammar applied to water and food records

NS-3 writes a record UNI as NXS-GRX-<KIND>[-<REGION>]-<SERIAL>, with an optional @<version> 1. The version is an integer record version, not a semantic version 1. The standard's own example, NXS-GRX-OB-KEN-000042@3, is observation fact 42 for Kenya at version 3 1.

In water and food systems the kinds map naturally to familiar records. An observation fact, OB, could be one daily discharge value, one monthly price or one survey estimate. A source release, SR, could be one data release from a national service, an international archive or a statistical database. An indicator definition, IN, could name what an indicator measures. A boundary version, BD, could be one version of a basin or administrative boundary 1.

The region segment follows NS-1: a three-letter country code or a UN region written as M plus three digits 4. Points and global records carry no region 1.

Fig. 01Record kinds for water and food data

Record kinds for water and food data Four columns: observation facts such as a discharge value or price; source releases such as a data release; indicator definitions such as undernourishment; boundary versions such as a basin outline. OB observationDischarge valueMonthly priceSR releaseData releaseIN indicatorUndernourishmentBD boundaryBasin outline
Record kinds as published in NS-3 1; the examples are illustrations.1Sources: Nexus Standards, NS-3. Figure CC BY 4.0. As of 3 November 2026.
Figure 1 in words

Column 1, OB observation fact: a daily discharge value, a monthly price, a survey estimate. Column 2, SR source release: one release from a national service, archive or database. Column 3, IN indicator definition: what an indicator such as undernourishment measures. Column 4, BD boundary version: one version of a basin or administrative boundary.

04River and water records

River and water records

Hydrological data travel in exchange formats such as OGC WaterML, whose version 2.0 Part 1 covers time series 5. Archives such as the Global Runoff Data Centre, which operates under the auspices of the World Meteorological Organization, offer river discharge data collected on behalf of WMO 6.

NS-3 does not change these formats. It would give the records drawn from them a name. NS-3 lists record kinds including SR, OB and CR, the correction record kind 1.

Drinking-water records work the same way. WHO's Guidelines for drinking-water quality, fourth edition with the first and second addenda, set the health basis for national standards 7. The WHO/UNICEF JMP service ladders benchmark access 8. A country's reported share of safely managed drinking water would be an observation fact drawn from a named JMP release, so a figure citing it shows which release and version it used 1,8.

05Food, price and food security records

Food, price and food security records

SDG target 2.1 tracks the prevalence of undernourishment and the prevalence of moderate or severe food insecurity 9. Crop monitoring adds satellite indicators such as NDVI 10.

Each of these produces records that change. Statistical series are revised, crisis classifications are updated within a year, and satellite indicators are reprocessed. NS-3 never reuses or reassigns an identifier 1, so a briefing that quoted a figure keeps pointing to the record it used.

Fig. 02What an NS-3 identifier does

What an NS-3 identifier does A ladder of four steps: name the record, never reuse the number, note the correction record kind, remember that an identifier is not a verdict. 01Name the recordUNI grammar02Never reuseNever reused or reassigned03Correction kindCR record kind04Not a verdictA UNI never certifies truth
Rules as published in NS-3 1.1Sources: Nexus Standards, NS-3 (proposed). Figure CC BY 4.0. As of 3 November 2026.
Figure 2 in words

Four rising steps. Name the record: a UNI follows the published grammar. Never reuse the number: a UNI is never reused or reassigned. Correction kind: NS-3 lists a correction record kind, CR. Not a verdict, highlighted: a UNI identifies and resolves a record and never certifies that it is true.

06Corrections without losing the trail

Corrections without losing the trail

NS-3 includes a correction record kind, CR, and its allocation rules keep every identifier, once issued, from ever being reissued 1. Allocations are append-only, and attempts to change or delete the allocation log are refused 1.

For water and food analysis this matters because so many headline numbers are later revised. The 2026 edition of FAO's flagship report, for instance, estimates that 645 million people faced hunger in 2025 11. A later edition may revise that estimate. A record-level citation of the 2026 value, with its version, keeps the earlier statement checkable after the revision.

07Legacy identifiers from existing data paths

Legacy identifiers from existing data paths

Most water and food datasets already have identifiers of their own: station codes, indicator codes, series keys. NS-3 keeps them valid 1. They parse as legacy identifiers, keep working in versioned references and are crosswalked to an NS-1 UNI when one is allocated 1. Nothing is renamed in place 1.

NS-3 records that open-data paths already allocate observation UNIs for native indicators from the World Bank, the UN Statistics Division, WHO, the IMF and other statistical adapters, for public hazard events and for weather records 1. The region is the observation's country, and points and global records carry none 1.

08Deployments and contexts

Deployments and contexts

Records answer what was measured. NS-9 answers where and by which deployment 12. A monitoring system deployed for one country's water sector would have its own contextual UNI, and its records would name that context 12. That keeps a claim about one basin or country from being read as a claim about another, which matters when the programme's example geography spans more than one country 2,12.

Fig. 03From source to cited figure

From source to cited figure Three stacked layers: the NS-3 record with its version, the NS-9 deployment context, and the NS-2 citation in a figure or report. 01FicheNS-3 UNI and version02ContexteNS-9 deployment03CitationNS-2 in the figure
Layers as published in NS-3, NS-9 and NS-2 1,12,3.1,12,3Sources: Nexus Standards, NS-3, NS-9 and NS-2. Figure CC BY 4.0. As of 3 November 2026.
Figure 3 in words

Three layers from bottom to top. Record: an NS-3 observation or release with its version. Context: the NS-9 deployment. Citation, highlighted: an NS-2 citation in the figure or report.

09A worked illustration: tracing one drought figure

A worked illustration: tracing one drought figure

Consider, as an illustration rather than a reported case, a briefing that says river flow in a basin fell well below normal before a poor harvest and a rise in food insecurity. Under NS-3 each part of that sentence would point to records. The river flow would be a set of observation facts drawn from a named source release of a discharge archive, each with a region and a record version 1,6.

As an illustration, the GEOGLAM Crop Monitor reports crop conditions and anticipated yield outcomes 10, and the food insecurity figure from the SDG 2.1 indicators 9. The briefing would cite each in the record form of NS-2, as the record UNI at its version together with its source release 3. The reader would then have two things to check: the quoted number and the release it was drawn from. Neither depends on trusting the author of the briefing. This is a design intention of the proposed standard, and it has not been tested in deployment. It is offered here to show how a record name could be used, not to describe any existing briefing. The same reasoning would apply to a flood briefing: the figure and its source release are named once, and any later reader can follow the identifier back to the record. What the identifier cannot do is show that the figure is correct: a UNI identifies and resolves a record, and it never certifies that the record is true. Checking the figure remains the work of the issuer and of the reader.

A reviewer could then open each citation, see the value that was used, check whether a later version exists and judge whether the sequence of events is supported. Nothing in this changes how the underlying sources are produced; it changes how precisely they can be referred to, and how easily a disagreement about the numbers can be settled.

10What a reader would see

What a reader would see

Under NS-1, every UNI resolves: a browser receives a landing page and a machine receives JSON 4. For a water or food record, that landing page is where a reader would resolve the record 4. A reader would not need to know the internal structure of the data system to check a number; the identifier is enough.

Because the record UNI never vouches for the record's truth, the landing page would also show the record's source and status rather than any verdict on its quality 1.

11Honest failure when allocation is unavailable

Honest failure when allocation is unavailable

Water and food data often arrive in bursts: after a flood, at the end of a season or when a crisis report is released. NS-3 says an outage of the allocation service never blocks an open-data observation being written 1. The receipt reports allocation as unavailable with partial counts 1. There is no in-memory fallback that would hand out identifiers the authority never recorded 1.

12Differences and open questions

Differences and open questions

Three points are worth noting for water and food implementers. First, NS-3 names a boundary record kind but does not yet say how hydrological units such as basins relate to administrative regions in the region segment, which uses country or UN region codes 1,4. Second, the programme lists NS-3 across its areas, but its area profiles are proposed and do not yet name which external sources would be allocated first 2. Third, NS-3 itself notes follow-on work, such as making the UNI queryable in its own column 1.

These are matters a later version could settle through an NS-13 proposal 13.

13Who this serves and how to take part

Who this serves and how to take part

NS-3 in water and food systems would serve hydrologists, agricultural statisticians, food security analysts, utility operators and the people who rely on their numbers. It would make each figure in a chain from basin to nutrition traceable to its source and version 1,2.

Comments go through the contact form, and changes follow Develop a standard. The standards are published by The Global Centre for Risk and Innovation (GCRI) as Secretariat. The Global Risks Forum (GRF) and The Global Risks Alliance (GRA) take part as stakeholders like any other.

14Instruments and sources related to this explainer

The table lists external instruments and sources whose records NS-3 would name, as published on 3 November 2026. Each is maintained by its own issuer.

SourcesExample record kindÉdition
OGC WaterMLObservation facts in a time seriesWaterML 2.0 Part 1 5
Global Runoff Data CentreSource releases of discharge dataLive archive 6
JMP drinking waterObservation facts for service levelsOnline estimates 8
SDG 2.1 metadataIndicator definitionsMetadata repository 9
Water and food sources and the NS-3 record kinds that would name their records, as of 3 November 2026.

What this page does not claim: NS-3 and the Water and Food Systems programme are proposed, and NS-3 is a preparatory working draft not for implementation; no Nexus Standard has been adopted by the Global Standards Council or any National Standards Council. The mapping of sources to record kinds is an illustration of how NS-3 would apply, not a record of allocations made. WHO, UNICEF, FAO, OGC, the GRDC, the UN Statistics Division, FSIN and GEOGLAM maintain their own data and instruments; Nexus Standards has no affiliation with any of them.

Questions

Questions et réponses

What would a record UNI look like for a water or food observation?

NXS-GRX (canonical data, provenance and risk), a two-letter record kind such as OB, an optional region code, a six-digit serial and an integer version, for example NXS-GRX-OB-KEN-000042@3.

Does NS-3 change WaterML or the SDG indicators?

No. Those remain the formats and references. NS-3 only gives the records drawn from them a stable name and version.

What happens when a figure is revised?

The revision becomes a new record version. The earlier version stays citable, so statements that used it can still be checked.

Do existing station or indicator codes stop working?

No. They stay valid as legacy identifiers and are crosswalked to a UNI when one is allocated.

What is the status of NS-3 for water and food systems?

No. NS-3 and the programme are proposed, and NS-3 is a preparatory working draft not for implementation.

Conditions

Glossaire

Fait d'observation
One recorded value, such as a discharge reading or a price, with its time and place.
Version source
One published release of a dataset from its provider.
Record version
An integer counting the versions of a record; a correction produces a new one.
Discharge
The volume of water flowing past a point in a river per unit of time.
Legacy identifier
An identifier a record carried before NS-3, kept valid and crosswalked.

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.

Sources

References

13 sources, numbered in the order they are first cited
  1. Nexus Standards (2026-10-16). NS-3: Risk record UNIs (proposed). nexustandards.com. Accessed 2026-11-03.
  2. Nexus Standards (2026-10-17). Water and Food Systems: a programme of the Nexus Standards. nexustandards.com. Accessed 2026-11-03.
  3. Nexus Standards (2026-10-16). NS-2: Citation and attribution format for UNIs (proposed). nexustandards.com. Accessed 2026-11-03.
  4. Nexus Standards (2026-10-15). NS-1: The UNI and the artefact catalogue (proposed). nexustandards.com. Accessed 2026-11-03.
  5. Open Geospatial Consortium (OGC) (2026-11-03). OGC WaterML. www.ogc.org. Accessed 2026-11-03.
  6. Global Runoff Data Centre (GRDC), under the auspices of the World Meteorological Organization (2026-11-03). Global Runoff Data Centre. grdc.bafg.de. Accessed 2026-11-03.
  7. World Health Organization (WHO) (2022-03-21). Guidelines for drinking-water quality: fourth edition incorporating the first and second addenda. www.who.int. Accessed 2026-11-03.
  8. WHO/UNICEF Joint Monitoring Programme for Water Supply, Sanitation and Hygiene (JMP) (2026-11-03). Drinking water: JMP monitoring. washdata.org. Accessed 2026-11-03.
  9. United Nations Statistics Division (2026-11-03). SDG indicator metadata, target 2.1. unstats.un.org. Accessed 2026-11-03.
  10. GEOGLAM, Group on Earth Observations (2026-11-03). GEOGLAM Crop Monitor. www.cropmonitor.org. Accessed 2026-11-03.
  11. Food and Agriculture Organization of the United Nations (FAO), with IFAD, UNICEF, WFP and WHO (2026). The State of Food Security and Nutrition in the World. www.fao.org. Accessed 2026-11-03.
  12. Nexus Standards (2026-10-16). NS-9: Contextual UNIs (proposed). nexustandards.com. Accessed 2026-11-03.
  13. 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-3 text, the programme page and every external source were checked at the issuer that day. This page is reviewed at least every 180 days and whenever NS-3 or the programme 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-3 risk record UNIs in water and food systems. Water and Food Systems. https://nexustandards.com/water-food/ns-3-water-and-food-systems/

Republish

Republish or translate this article free of charge, in print or online, under CC BY 4.0: keep the byline and Water and Food Systems, 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-3 risk record UNIs in water and food systems, explained for implementers — Standards desk, Nexus Standards, Water and Food Systems. First published 3 November 2026 at <a href="https://nexustandards.com/water-food/ns-3-water-and-food-systems/">https://nexustandards.com/water-food/ns-3-water-and-food-systems/</a>. Republished under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/).</p>

Related across the Consortium

Share

EmailLinkedInBlueskyMastodon