Skip to content

NXS · Foundations

Inside NS-3: risk record UNIs

NS-3 proposes a UNI for every record of the risk data system, from observations to corrections. This explainer covers the grammar and record kinds, integer versions, legacy identifiers, append-only allocation, account isolation and honest failure.

As of
3 November 2026
Bacaan
10 minutes
Bukti
11 sources, cited in order
Status
Proposed standard
Kode
NS-3 · Risk record UNIs
NEXUS TWIN · WF-1 · GLOBESEED 900e7932NXS-MAIN.STANDARD.NS-3xyzSCHEMATIC · GLOBEST-01 · 0.720 0.547ST-02 · 0.710 0.733
WF-1 · globe Schematic wireframe twin (globe, climate system). An illustration, not data.

Status and scope

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

Kode
NS-3 · Risk record UNIs
Lingkup
A UNI for every record of the risk data system, allocated by one append-only service on the NS-1 grammar.
Berlaku untuk
Observation facts, source releases, indicators, measures, boundaries, chronotopes, corrections, analytical products and subjects.
  1. 1 Grammar
  2. 2 Legacy ids stay valid
  3. 3 Alokasi
  4. 4 What changes for ingest paths
  5. 4a Adopted paths
  6. 5 Follow-on

01What NS-3 risk record UNIs are

What NS-3 risk record UNIs are

NS-3 risk record UNIs is the proposed Nexus Standard titled Risk record UNIs (grammar, legacy crosswalk, allocation authority). Its identifier is NXS-STD-ST-000003 and its current version is 0.1.0, catalogued on 16 October 2026 1. The text is on the NS-3 page.

NS-1 gives artefacts such as software, reports, datasets and figures a UNI allocated by a catalogue 1,2. NS-3 extends the same grammar to the records of the risk data system: observation facts, source releases, indicators, boundaries, chronotopes, corrections, analytical products and subjects 1. These UNIs are allocated by a database service rather than a catalogue file, so that a record can be cited, resolved and crosswalked like any other artefact 1.

The standard repeats the boundary set by NS-1: a UNI identifies and resolves a record, and never vouches for the record's truth 1. NS-3 is a preparatory working draft circulated for comment on 17 October 2026, and is not for implementation 1.

02Why each data record needs a stable name

Why each data record needs a stable name

Risk analysis is built from very many small facts: a population count for a country in a year, a rainfall total for a district, a boundary line, a correction to last month's figure. Each fact passes through ingestion, cleaning, aggregation and modelling before it reaches a chart. When a figure is challenged, someone has to trace it back to the exact facts and versions it used.

That is only possible if every fact has a stable identifier and a version. NS-3 provides both, and it ties them to the same scheme used for reports and figures 1. A chart, its dataset and each observation it rests on can therefore be cited the same way under NS-2, whose record form is the record UNI at its record version with the source release 3.

03The grammar and the nine record kinds

The grammar and the nine record kinds

Clause 1 sets the grammar as NXS-GRX-<KIND>[-<REGION>]-<SERIAL>, which names the record concept, with an optional @<version> for one record version 1. The standard's examples are NXS-GRX-OB-KEN-000042@3, observation fact 42 for Kenya at version 3, and NXS-GRX-SR-000001, source release 1, which is global and has no region 1.

The version here is an integer record version, not a semantic version. NS-1 therefore accepts @3 as well as @1.2.0: an artefact carries a semantic version, a record an integer, and a reference with a semantic version is not a record reference 1,2.

Nine record kinds have two-letter codes 1. OB is an observation fact, SR a source release, IN an indicator definition, ME a measure definition and BD a boundary version. CT is a chronotope version, CR a correction record, AP an analytical product record and SU a subject such as a place, asset or organisation 1. Record kinds and artefact categories never share a code, and validation tools enforce the rule 1.

Fig. 01Anatomy of a record UNI

Anatomy of a record UNI Five stacked layers read the example: NXS-GRX scope, OB record kind, KEN region, 000042 serial and @3 integer record version. 01NXS-GRXData system scope02OBJenis catatan03KENOptional region04000042Serial, never reused05@3Integer record version
Segments as published in NS-3 clause 1 1.1Sources: Nexus Standards, NS-3 clause 1. Figure CC BY 4.0. As of 3 November 2026.
Figure 1 in words

Five layers. NXS-GRX: the data system scope. OB: the record kind, here an observation fact; nine kinds exist. KEN: optional region, here Kenya. 000042: serial from the allocation service, never reused. @3, highlighted: the integer record version; a semantic version would mark an artefact instead.

04Regions in record UNIs

Regions in record UNIs

The optional region segment follows NS-1, where a region is a three-letter country code or a UN M49 region written as M plus three digits 2. The M49 standard of the United Nations Statistics Division is the source of those region numbers, such as 002 for Africa 4.

In the open-data paths that NS-3 records as in use, the region is the country dimension of the observation or its country place reference, while points and global records carry no region 1. A Kenyan population figure would therefore carry KEN, while a single weather point or a global aggregate would not.

05Legacy identifiers stay valid

Legacy identifiers stay valid

Clause 2 deals with the identifiers that records already carry 1. Some are keys built from a source and a code, such as identifiers for a World Bank source or an indicator code. Others are older dotted identifiers. All of them parse as legacy, keep working in references with a version, and are crosswalked to an NS-1 UNI when one is allocated 1.

Nothing is renamed in place 1. A new record carries a UNI on the NS-1 grammar. An existing record keeps its legacy key and gains the allocated UNI alongside it during the transition 1. Both forms are accepted when references are built and read, so that correction dependencies keep resolving while paths migrate 1.

06Allocation: one authority, append-only

Allocation: one authority, append-only

Clause 3 makes allocation the job of a single database service 1. Serials are never derived or typed by hand, following NS-1 rule NS1-R2 1,2. They come from an atomic counter for each combination of scope, kind and region, advanced only inside a scoped transaction 1.

Every allocation is one append-only row recording the tenant, workspace and account, the UNI, its kind, region and serial, the legacy identifier and the verified principal who asked 1. The legacy identifier is the idempotency key within an account: allocating the same legacy identifier twice returns the same UNI and says it was reused 1.

UNIs are never reused or reassigned 1. Attempts to update, delete or truncate the allocation log are refused, and a check keeps each UNI string equal to its component parts 1. Ordinary database sequences behave differently. The PostgreSQL documentation notes that sequence calls are never rolled back, so sequences cannot be used where gapless numbering is needed 5. NS-3 does not promise gapless serials; it promises that a serial, once issued, is never issued again 1.

Fig. 02Nine record kinds

Nine record kinds Three columns group nine record kinds: data and sources (observation fact OB, source release SR, correction CR); definitions (indicator IN, measure ME, boundary BD); context and products (chronotope CT, subject SU, analytical product AP). Data dan sumberOB observation factSR source releaseCR correctionDefinisiIN indicatorME measureBD boundaryContext and productsCT chronotopeSU subjectAP analytical product
Kinds as published in NS-3 clause 1 1. Record kinds never share a code with artefact categories.1Sources: Nexus Standards, NS-3 clause 1. Figure CC BY 4.0. As of 3 November 2026.
Figure 2 in words

Column 1, data and sources: observation fact OB, source release SR, correction record CR. Column 2, definitions: indicator definition IN, measure definition ME, boundary version BD. Column 3, context and products: chronotope version CT, subject SU for a place, asset or organisation, analytical product record AP.

07Isolation between accounts

Isolation between accounts

The allocation service is shared, but what each account records is not. NS-3 says serials are shared across accounts while each account's crosswalk from legacy identifiers stays private to it 1. Isolation uses the database's row-level security 1.

In PostgreSQL, tables can have row security policies that restrict, per user, which rows normal queries return or data changes affect 6. Superusers and roles with a bypass attribute always skip those policies, and table owners normally do too unless the table is set to apply them to its owner as well 6. NS-3 says its integration test runs as a role with neither privilege. The test checks that a forged scope writes nothing, that changes to the log are refused and that the migration can be reapplied with no effect 1.

08Honest failure: no silent fallback

Honest failure: no silent fallback

NS-3 is explicit about outages 1. When the allocation service is offline, callers receive a typed unavailable error, and there is no in-memory fallback that would hand out identifiers the authority never recorded 1.

For open-data ingestion the rule is softened in one direction only. An outage never blocks an observation being written: the first outage trips a circuit for that pass, and the receipt reports allocation as unavailable with partial counts 1. The data is kept; the missing identifiers are visible and are filled in later. Where a caller supplies no verified account, allocation is reported as not requested rather than attempted under an assumed identity 1.

09Adopted paths: where record UNIs already apply

Adopted paths: where record UNIs already apply

Clause 4a records which ingestion paths use record UNIs 1. A bootstrap of the World Bank's World Development Indicators allocates source release and observation UNIs 1. World Development Indicators is the World Bank's compilation of cross-country comparable data on development 7.

The open-data path allocates an observation UNI for every observation the public-data plane writes 1. Its sources include native indicators from the World Bank, the UN Statistics Division, WHO, the IMF and other statistical adapters, public hazard events, and current, forecast and ensemble records from Open-Meteo 1. WHO publishes health statistics through its Global Health Observatory 8, and Open-Meteo offers its weather data under CC BY 4.0 9.

Account identity for allocation is read only from a request's verified claims, never from a header, body or query parameter 1. A product's provenance bundle maps both legacy and new forms, following the PROV-O profile of NS-3b 1. In W3C PROV-O, a derivation is a transformation of one entity into another 10.

Fig. 03How a record gets its UNI

How a record gets its UNI A ladder of four steps: a record with a legacy key, a request from a verified account, an append-only allocation, and a UNI crosswalked to the legacy key. 01Legacy keyStays valid02Verified requestAccount from claims only03AllocatedAppend-only, idempotent04CrosswalkedBoth forms resolve
Steps as published in NS-3 clauses 2 and 3 1.1Sources: Nexus Standards, NS-3 clauses 2 and 3. Figure CC BY 4.0. As of 3 November 2026.
Figure 3 in words

Four rising steps. Legacy key: the record's existing identifier stays valid. Verified request: the account comes only from verified claims. Allocated, highlighted: one append-only row per allocation; the same legacy key returns the same UNI. Crosswalked: the record carries both forms; references in either form resolve.

10The system model on the NS-3 page

The system model on the NS-3 page

The NS-3 page also carries an interactive system model that shows where the records NS-3 governs sit when a shock travels through a system 1. It is built from the standards registry: 26 hazards, 25 systems, 10 sectors, 13 controls, 18 data feeds and 17 indicators, drawn from the areas that list NS-3, such as cascading risk, finance and insurance, health, water, food and energy 1.

A reader chooses components and an initiating hazard and runs a scenario, with every parameter stated and adjustable 1. A map view places the same run on an example geography, the Philippines, using open data 1. The page is clear about its limits: the results are illustrative scenario outputs for exercises and training, not forecasts or risk assessments, and the model is not a reading of the standard's text 1.

11Differences and open questions

Differences and open questions

Three points are worth noting for implementers. First, NS-3 records that one internal builder path still accepts an account from a request header, and so does not yet forward identity for allocation 1. Second, the UNI is not yet held in its own queryable column for observations, so finding a record by its UNI means reading the record payload 1. Third, the record grammar shares NS-1's URN form, urn:nexus:uni: 2.

NS-3 lists the first two as follow-on work 1. Changes to the standard itself go through an NS-13 proposal 11.

12Who NS-3 serves and how to take part

Who NS-3 serves and how to take part

NS-3 serves analysts, data stewards, auditors and anyone who must trace a number back to its source. It makes each fact in a risk dataset individually citable and keeps the trail intact when facts are corrected 1.

Changes follow the open process on Develop a standard, and comments go through the contact form. 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. Learners can study related methods in Risk Academy's Technology and Data course.

13Instruments and sources related to NS-3

The table lists external instruments and data sources NS-3 names or relies on, as published on 3 November 2026. Each is maintained by its own issuer and applies on its own terms.

Instrument or sourceRelation to NS-3Edisi
PostgreSQL row securityIsolation between accountsVersion 18 documentation 6
PostgreSQL sequencesContrast with the allocation counterVersion 18 documentation 5
World Development IndicatorsFirst ingestion path in useLive page 7
UN M49Kode wilayahOnline edition 4
W3C PROV-OProvenance of derived products30 April 2013 10
External instruments and sources related to the proposed NS-3, as of 3 November 2026.

What this page does not claim: NS-3 is a proposed, preparatory working draft that its own page says is not for implementation, and no Nexus Standard has been adopted by the Global Standards Council or any National Standards Council. The ingestion paths described are those NS-3 records about its own reference implementation; this page has not tested them. The World Bank, WHO, the IMF, the UN Statistics Division and Open-Meteo publish their own data under their own terms, and the PostgreSQL project, W3C and the IETF maintain their own instruments; Nexus Standards has no affiliation with any of them.

Pertanyaan

Pertanyaan dan jawaban

How does a record UNI differ from an artefact UNI?

It uses the same grammar under the data system scope, with a record kind code such as OB, and its version is an integer record version, not a semantic version.

Do existing record identifiers stop working?

No. Legacy identifiers keep working in versioned references and are crosswalked to an NS-1 UNI once one is allocated. Nothing is renamed in place.

Can a record UNI ever be reused?

No. Allocations are append-only, changes to the allocation log are refused, and a serial once issued is never issued again.

What happens if the allocation service is down?

Callers get a typed unavailable error with no in-memory fallback. Open-data writes continue and report the missing allocations for later.

What is NS-3's own status?

Proposed. Version 0.1.0 is a preparatory working draft circulated for review and comment, not for implementation, and changes go through NS-13 proposals.

Ketentuan

Glosarium

Record UNI
A UNI that names one record of the risk data system, such as an observation or source release.
Record version
An integer counting the versions of a record; a correction produces a new version.
Legacy identifier
An identifier a record carried before NS-3, kept valid and crosswalked to its UNI.
Idempotency key
A value that makes a repeated request return the same result instead of creating a duplicate.
Row-level security
Database policies that limit which rows each user can read or change.

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.

Sumber

References

11 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-15). NS-1: The UNI and the artefact catalogue (proposed). 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. United Nations Statistics Division (). Standard country or area codes for statistical use (M49). unstats.un.org. Accessed 2026-11-03.
  5. PostgreSQL Global Development Group (2026-11-03). PostgreSQL Documentation: CREATE SEQUENCE. www.postgresql.org. Accessed 2026-11-03.
  6. PostgreSQL Global Development Group (2026-11-03). PostgreSQL Documentation: Row Security Policies. www.postgresql.org. Accessed 2026-11-03.
  7. World Bank (2026-11-03). World Development Indicators. datatopics.worldbank.org. Accessed 2026-11-03.
  8. World Health Organization (WHO) (2026-11-03). Global Health Observatory. www.who.int. Accessed 2026-11-03.
  9. Open-Meteo (2026-11-03). Open-Meteo: Free Weather API. open-meteo.com. Accessed 2026-11-03.
  10. World Wide Web Consortium (W3C) (2013-04-30). PROV-O: The PROV Ontology. www.w3.org. Accessed 2026-11-03.
  11. Nexus Standards (2026-10-16). NS-13: Standards development process (proposed). nexustandards.com. Accessed 2026-11-03.

Catatan

Editorial record

Facts as of 3 November 2026. The NS-3 text, version and status were read on its page that day, and every external instrument and source was checked at its issuer the same day. The IMF data portal refused automated access, so the IMF is named only as NS-3 names it. This page is reviewed at least every 180 days and whenever NS-3 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 explained. Nexus Standards. https://nexustandards.com/ns-3-risk-record-unis/

Republish

Republish or translate this article free of charge, in print or online, under CC BY 4.0: keep the byline and Nexus Standards, link to the original and note any change. Figures, maps and twins made by the institutions carry the same licence; third-party data keeps its own credit line.

Attribution to paste
<p>Inside NS-3: risk record UNIs — Standards desk, Nexus Standards, Nexus Standards. First published 3 November 2026 at <a href="https://nexustandards.com/ns-3-risk-record-unis/">https://nexustandards.com/ns-3-risk-record-unis/</a>. Republished under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/).</p>

Proporsi

EmailLinkedInBlueskyMastodon