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).
- 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
Summary
- Rows6 example standards
- Bodies3 example bodies
- Date16 October 2026 (example)
- Sourcenone; invented for illustration
The page makes no statement about any real standard or body.
- Registries
- 10
- published as data
- Risk standards
- 348
- records
- Hazards
- 905
- NHS-1
- External standards
- 253
- referenced, never copied
The monitoring console with example data
NXS · Process
Monitoring loop
Standard lifecycle · NS-13 track · Contribution channels · IETF track · W3C track · OGC track · OASIS track · ISO and IEC stages · Conformance · Record lifecycle · Routing · Monitoring.
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.
01 Data source register
- 01Source listedDecision · the Secretariat, after licence reviewData sources are listed for reference; live data is displayed once licence review is complete.
02 Data service
- 02Change recordRecord · the data serviceEach feed item becomes a change record appended to the transparency log with an inclusion proof.
- 03Drift checkGate · the data serviceDrift is a comparison of two version strings; the register entry is corrected through a change proposal.
- 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.
03 Pages
- 04NoticeStep · the page buildThe package page shows the latest change, its source and its date; an out-of-date snapshot is identified as such.
04 Nexus Standards editors
- 05DispositionDecision · Nexus Standards editorsThe editors determine what the change means for the register entry and the crosswalk; the page shows the disposition.
- 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
| Step | Phase | Operation | Who | Decision rule | Record |
|---|---|---|---|---|---|
| 01 | Data source register | Source listed (decision). Data sources are listed for reference; live data is displayed once licence review is complete. | the Secretariat, after licence review | the entry records the licence terms and the permitted delivery | an entry in the data source register |
| 02 | Data service | Feed 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 service | retrieved on the source’s schedule; each response is stored unchanged | the response with digest and retrieval date |
| 03 | Data service | Change record (record). Each feed item becomes a change record appended to the transparency log with an inclusion proof. | the data service | kind: release, errata, comment period, deprecation or supersession; version, date, URL, digest | a change record with a UNI |
| 04 | Data service | Drift check (gate). Drift is a comparison of two version strings; the register entry is corrected through a change proposal. | the data service | registered version compared with the latest release; deprecation and supersession flagged | a drift flag against the registered version |
| 05 | Pages | Notice (step). The package page shows the latest change, its source and its date; an out-of-date snapshot is identified as such. | the page build | the age of the information is stated | a notice with date and source |
| 06 | Nexus Standards editors | Disposition (decision). The editors determine what the change means for the register entry and the crosswalk; the page shows the disposition. | Nexus Standards editors | each disposition is a change proposal under NS-13, with written reasons | a change proposal with the disposition |
| 07 | Nexus Standards editors | Next retrieval (end). The loop continues on the schedule recorded in the register entry. | the data service, on schedule | the source’s schedule, subject to the body’s terms | the 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.
- Live4
- Listed for reference1
- Stale snapshot1
- Version drift3
- 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 standard | Body | Registry version | Latest from the body | Feed state | Last change | Age |
|---|---|---|---|---|---|---|
| Sample standard A example | Sample body 1 | 2.0 | 2.1 drift | live | release | 2 h ago |
| Sample standard B example | Sample body 1 | 1.4 | 1.4 | live | comment period openscloses in 12 days | 1 day ago |
| Sample standard C example | Sample body 2 | 3.1 | 3.1 | stale snapshot | none since the snapshot | snapshot 9 days old |
| Sample standard D example | Sample body 2 | 1.0 | 1.1 (deprecates 1.0) drift | live | deprecation | 4 days ago |
| Sample standard E example | Sample body 3 | 5 | 5 | listed for reference | none | no live data |
| Sample standard F example | Sample body 3 | 2024 | 2026 drift | live | supersessioncomment period closes in 3 days | 6 days ago |
What changes on the monitoring console
- 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.
- 02
Each item is recorded with a digest
A change record for each release, erratum, comment period, deprecation or supersession.
- 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.
Questions and answers.
Are these real releases?
Around monitoring services.
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 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 artefact; 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. · worked example · monitoring console · events invented for illustration.