Skip to content
worked example · monitoring console · events invented for illustration
StandardsMonitoring servicesWorked example
Worked example

Monitoring console: worked example

How the monitoring console reads once live data is available: differences between the registry version and the body’s latest release, comment periods closing, stale snapshots and change records. Every name, version and event on this page is invented for illustration. Change records carry a UNI (Unique Nexus Identifier).

The open registries
The machine-readable registries behind every page, by number of records. Each is published as data under CC BY 4.0.Source: the Standards registry (the registry, the NHS-1 list).
  • Hazard relations (NHS-1): 1,867
  • Hazards (NHS-1): 905
  • Risk standards: 348
  • External standards: 253
  • Regions (ISO 3166): 249
  • Programme areas: 77
  • Record categories: 38
  • Scope codes: 32
  • Domain codes: 30
  • Sector codes: 13
01Oorsig

Summary

Worked exampleinvented data
  1. Rows6 example standards
  2. Bodies3 example bodies
  3. Date16 October 2026 (example)
  4. Sourcenone; invented for illustration

The page makes no statement about any real standard or body.

Registries
10
published as data
Risikostandaarde
348
records
Gevare
905
NHS-1
Eksterne standaarde
253
referenced, never copied
02Konsole

The monitoring console with example data

Monitoring console · worked example · how the console reads once live data is availableWorked example

Process explorer · NXS · Process

Monitoring loop

7 steps4 stages1 gate

NXS · Process

Monitoring loop

Lewensiklus van 'n standaard · NS-13-spoor · Bydraekanale · IETF-spoor · W3C-spoor · OGC-spoor · OASIS-spoor · ISO- en IEC-fases · Konformiteit · Rekordlewensiklus · Roetering · Monitering.

A licence-reviewed source is retrieved with digests, each item becomes a change record checked for drift, and editors record a disposition through a change proposal.

  1. 01 Data source register

    1. 01Source listedDecision · the Secretariat, after licence reviewData sources are listed for reference; live data is displayed once licence review is complete.
  2. 02 Data service

    1. 02Change recordRecord · the data serviceEach feed item becomes a change record appended to the transparency log with an inclusion proof.
    2. 03Drift checkGate · the data serviceDrift is a comparison of two version strings; the register entry is corrected through a change proposal.
    3. 07Feed retrievedStep · the governed data serviceThe data service reads the feed named in the register entry and stores each response with its digest and retrieval time.
  3. 03 Pages

    1. 04NoticeStep · the page buildThe package page shows the latest change, its source and its date; an out-of-date snapshot is identified as such.
  4. 04 Nexus Standards editors

    1. 05DispositionDecision · Nexus Standards editorsThe editors determine what the change means for the register entry and the crosswalk; the page shows the disposition.
    2. 06Next retrievalOutcome · the data service, on scheduleThe loop continues on the schedule recorded in the register entry.

Feed update register (admitted feeds only) · Licensing rules · Registries and resolverAn outline of how the work is designed to run; it does not report the status of any decision or record.

The operations, as a table
Process · the monitoring loop7 operations
StepPhaseOperationWhoDecision ruleRecord
01Data source registerSource listed (decision). Data sources are listed for reference; live data is displayed once licence review is complete.the Secretariat, after licence reviewthe entry records the licence terms and the permitted deliveryan entry in the data source register
02Data serviceFeed retrieved (step). The data service reads the feed named in the register entry and stores each response with its digest and retrieval time.the governed data serviceretrieved on the source’s schedule; each response is stored unchangedthe response with digest and retrieval date
03Data serviceChange record (record). Each feed item becomes a change record appended to the transparency log with an inclusion proof.the data servicekind: release, errata, comment period, deprecation or supersession; version, date, URL, digesta change record with a UNI
04Data serviceDrift check (gate). Drift is a comparison of two version strings; the register entry is corrected through a change proposal.the data serviceregistered version compared with the latest release; deprecation and supersession flaggeda drift flag against the registered version
05PagesNotice (step). The package page shows the latest change, its source and its date; an out-of-date snapshot is identified as such.the page buildthe age of the information is stateda notice with date and source
06Nexus Standards editorsDisposition (decision). The editors determine what the change means for the register entry and the crosswalk; the page shows the disposition.Nexus Standards editorseach disposition is a change proposal under NS-13, with written reasonsa change proposal with the disposition
07Nexus Standards editorsNext retrieval (end). The loop continues on the schedule recorded in the register entry.the data service, on schedulethe source’s schedule, subject to the body’s termsthe next response

Table.From a data source to a change record, a version check, a notice and a disposition. The table shows the process as specified; it does not report the status of any standard, proposal or record. Sources: Feed update register (admitted feeds only) · Licensing rules · Registries and resolver.

Data feeds (worked example)example date: 16 October 2026
  1. Lewendig4
  2. Listed for reference1
  3. Stale snapshot1
  4. Version drift3
  5. Closing in 30 days2

Worked example: the names, versions and events are invented to illustrate the console and refer to no real standard or body.

Example standardBodyRegistry versionLatest from the bodyFeed stateLast changeAge
Sample standard A exampleSample body 12.02.1 driftregstreeksrelease2 h ago
Sample standard B exampleSample body 11.41.4regstreekscomment period openscloses in 12 days1 day ago
Sample standard C exampleSample body 23.13.1stale snapshotnone since the snapshotsnapshot 9 days old
Sample standard D exampleSample body 21.01.1 (deprecates 1.0) driftregstreeksdeprecation4 days ago
Sample standard E exampleSample body 355listed for referencenoneno live data
Sample standard F exampleSample body 320242026 driftregstreekssupersessioncomment period closes in 3 days6 days ago
03When live data is available

What changes on the monitoring console

  1. 01

    Licence review of the data source is completed

    The terms of use and the permitted form of delivery are recorded before any data is displayed.

  2. 02

    Each item is recorded with a digest

    A change record for each release, erratum, comment period, deprecation or supersession.

  3. 03

    Version differences and notices appear with their age

    The package page shows the latest change, its source and its age, and identifies a stale snapshot as such.

04Vrae

Questions and answers.

Are these real releases?
No. The data are invented for illustration. The monitoring console lists data sources for reference until licence review is complete.
Standaarde

Shape the standards for monitoring services.

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 en gebruik. Die Nexus Standards is voorgestelde standaarde wat deur 'n oop proses onder NS-13 ontwikkel en vir vrywillige gebruik gepubliseer word; hulle maak nie sertifisering, akkreditasie of regulatoriese goedkeuring uit nie, en aanvaarding bly 'n besluit van die Wêreldwye Standaarderaad en, in elke land, van sy Nasionale Standaarderaad. 'n UNI (Unique Nexus Identifier) identifiseer 'n artefak; dit sertifiseer dit nie. Name van standaardliggame en hul standaarde behoort aan hul rentmeesters en word slegs gebruik om die dokumente te identifiseer; geen teks van 'n eksterne standaard word hier gereproduseer nie. Nexus Standards is nie geaffilieer met, onderskryf deur of gesertifiseer deur enige standaardliggaam wat hier genoem word nie.

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. · worked example · monitoring console · events invented for illustration.