Monitoring services: records and schemas
How the artefacts of monitoring services are identified, described and resolved: the scope, the record, the categories, the schemas and the catalogue entries of the applicable standards, each keyed by a UNI (Unique Nexus Identifier).
- Nexus Standards: NS-9, NS-10, NS-11.
- Open standards: OpenTelemetry specification; NIST Cybersecurity Framework 2.0; NIST OSCAL assessment results model; CloudEvents.
- Data and feeds: CISA Known Exploited Vulnerabilities catalogue; NVD CVE API 2.0.
- Couples with: Verification and monitoring; Commons and command rooms; Real-time fabric.
The process.
Artefact record (NS-1) · 32 fields · 12 required
unirequired stringThe UNI (Unique Nexus Identifier), NS-1 grammar, without @version.displayAliasstringPublic Registry short form (NX-R-47092) shown next to the UNI during the transition.registryStateenumPublic registry state; corrections keep the UNI and add a version.legacyUnistringDotted UNI v0 this record replaces, for crosswalk (for example data.eo.stac.catalogue).titlerequired stringdescriptionstringscoperequired stringcategoryrequired stringregionstringdomainstringDOMAIN segment code from the domains register (NS-1 v0.2); present when the identifier carries it.sectorstringSECTOR segment code from the sectors register (NS-1 v0.2).environmentenumENV segment code (NS-1 v0.2).contextNamestringNS-16 context name: the identifier without CAT and SERIAL; derived, never allocated.systemIdstringFunctional system class id (systemId) from the Nexus Standards register#scopes when scope is a SYSTEM.statusrequired enumcurrentVersionstringversionsarrayversionstringdatestringgitShastringdigeststringnotestring
creatorsrequired arraynamestringtypeenumaffiliationstringorcidstringrorstring
publisherRefrequired stringEntity reference of the publishing institution (registry/governance.yaml#bodies); the institution stays publisher of record for institutional artefacts.publicationDaterequired stringlanguagestringkeywordsarrayrightsrequired objectlicensestringSPDX licence identifier or expression, or a LicenseRef- string for a licence that has no SPDX identifier.rightsHolderRefstringaccessRightenumembargoDatestring
legalStaterequired enumclaimCeilingrequired enumlocationsrequired arraykindenumvaluestringdigeststring
relatedIdentifiersarrayrelationenumidentifierstringidentifierTypeenum
supersededBystringworkPackageIdstringdirectiveRefsarrayReferences to the recorded decisions or policies under which the artefact was produced.notesstringcontextobjectNS-9: this record is a deployment, instance or programme instance of the concept ofUni, in a context.ofUnistringdomainsarrayids from the domains registersectorsarrayids from the sectors registerjurisdictionsarrayhostRefstringenvironmentenumvalidFromstringvalidUntilstringconformsToarrayNexus Standard ids and the external standards register ids this context claims; evidence per NS-11
Example record · NXS-STD-ST-000001
{ "uni": "NXS-STD-ST-000001", "title": "Nexus Standards NS-1 - the UNI and artifact catalog", "scope": "STD", "category": "ST", "status": "DRAFT", "currentVersion": "0.1.0", "creators": [ { "name": "Global Centre for Risk and Innovation (GCRI)", "type": "Organizational" } ], "publisherRef": "GCRI", "publicationDate": "2026-10-15", "rights": { "license": "CC-BY-4.0", "accessRight": "open" }, "legalState": "LEGAL_REVIEW_REQUIRED", "claimCeiling": "INTEGRATED", "locations": [ { "kind": "repoPath", "value": "standards/NS-1-identifier-and-artifact-catalog.md" }, { "kind": "repoPath", "value": "registry/nexus-standards.yaml" } ], "workPackageId": "LEGAL-NAME-ARCHITECTURE-001" }Field crosswalk: Schema.org JSON-LD, DataCite, Zenodo, CodeMeta
| Record field | Schema.org | DataCite | Zenodo | CodeMeta | Source |
|---|---|---|---|---|---|
uni | identifier (PropertyValue, propertyID urn:nexus:uni) | alternateIdentifier (alternateIdentifierType NXS) | metadata.related_identifiers[] (scheme other) | identifier | draft |
title | name | titles[].title | metadata.title | name | draft |
description | description | descriptions[].description (Abstract) | metadata.description | description | draft |
scope | · | subjects[] (subjectScheme nexus-scope) | metadata.keywords[] | · | draft |
category | additionalType | types.resourceTypeGeneral | metadata.upload_type / publication_type / image_type | applicationCategory | registry |
region | spatialCoverage | geoLocations[].geoLocationPlace | metadata.locations[] | · | draft |
status | creativeWorkStatus | · | · | developmentStatus | draft |
currentVersion | version | version | metadata.version | version | draft |
versions | · | relatedIdentifiers (IsNewVersionOf, IsPreviousVersionOf) | versions (concept DOI) | · | draft |
creators | creator / author | creators[] | metadata.creators[] | author | draft |
publisherRef | publisher | publisher | metadata.publisher (Zenodo) | publisher | draft |
publicationDate | datePublished | publicationYear; dates[] (Issued) | metadata.publication_date | datePublished | draft |
language | inLanguage | language | metadata.language | · | draft |
keywords | keywords | subjects[] | metadata.keywords[] | keywords | draft |
rights.license | license | rightsList[].rightsIdentifier (SPDX) | metadata.license | license | draft |
rights.accessRight | conditionsOfAccess | · | metadata.access_right | · | draft |
legalState | · | · | · | · | draft |
claimCeiling | · | · | · | · | draft |
locations | url / contentUrl / codeRepository | alternateIdentifiers[] (URL) | files[] / metadata.related_identifiers[] | codeRepository / downloadUrl | draft |
relatedIdentifiers | isPartOf / citation / isBasedOn | relatedIdentifiers[] (relationType) | metadata.related_identifiers[] | isPartOf / referencePublication | draft |
supersededBy | · | relatedIdentifiers[] (IsObsoletedBy) | metadata.related_identifiers[] (isObsoletedBy) | · | draft |
workPackageId | · | · | · | · | draft |
directiveRefs | · | relatedIdentifiers[] (References) | metadata.related_identifiers[] (references) | · | draft |
context | · | · | · | · | draft |
Rows marked registry are taken from the category mappings to Zenodo and DataCite in the registry; rows marked draft are an editorial mapping to the public schemas and are not part of the registry.
Record explorerthe artefact record schema with example records from the standards catalogue (scope STD). A record describes an artefact and its provenance.
- Nexus Standards
- 3
- NS-9, NS-10, NS-11
- Open standards
- 4
- named, never copied
- Data and feeds
- 2
- listed for reference
- Couplings
- 3
- with other areas
Identifiers under scope NSF
the trust and assurance system is the system scope Trust, authorisation and assurance. An artefact of this area is identified as NXS-NSF-<CAT>-<SERIAL>, with an optional region segment for regional artefacts; serials are allocated only by the catalogue.
NXS-STD-ST-000001NXS-EWS-DS-KEN-000003NXS-GRX-RP-M002-000007@1.2.0NXS-GRX-OB-KEN-000042@3NXS-GCR-AR-000015Illustrative identifier pattern. With script enabled, a UNI can be entered and each segment is checked against the registry, resolved to its record where one is published, and expressed as a URN, a resolver link and a citation.
UNI anatomyThe NS-1 grammar segment by segment, with the scope and category codes of the registry. Resolution links to the resolver; no identifier is allocated on this page.
The form above is a pattern; codes classify artefacts and are not product names.
Content of a catalogue record
| Field set | Values |
|---|---|
| Required fields | uni, title, scope, category, status, creators, publisherRef, publicationDate, rights, legalState, claimCeiling, locations |
| Statuses | DRAFT, PUBLISHED, SUPERSEDED, WITHDRAWN |
| Rights states | LEGAL_REVIEW_REQUIRED, APPROVED, RESTRICTED, PROHIBITED |
| Assurance levels | FIXTURE_VERIFIED, IMPLEMENTATION_COMPLETE, INTEGRATED, LAB_OBSERVED |
Embedding of the UNI in the artefact
| Surface | How |
|---|---|
sourceFile | header comment: Nexus-UNI: <uni> |
| markdown | front matter uni: or first line Nexus-UNI: <uni> |
| dataset | metadata sidecar <file>.uni.json with the record, or a uni key in STAC or DataCite metadata |
| figure | caption suffix [<uni>] and image metadata |
httpApi | response header X-Nexus-UNI: <uni> |
htmlPage | <meta name="nexus-uni" content="<uni>"> and data-nexus-uni on the component root |
| cms | content metadata field _nexus_uni (validated), rendered as the nexus-uni meta tag and the X-Nexus-UNI header |
| panel | every projected record carries uni in the panel’s provenance and links it to the resolver |
Record kinds and artefact categories
Artefacts use categories mapped to Zenodo and DataCite resource types; records of the data fabric use record kinds (NS-3). The two lists share no code.
| Code | Record kind (NS-3) |
|---|---|
OB | Observation fact |
SR | Source release |
IN | Indicator definition |
ME | Measure definition |
BD | Boundary version |
CT | Chronotope version |
CR | Correction record |
AP | Analytical product record |
SU | Subject (place, asset, organisation) |
Machine-readable schemas
nexus-artifact-record.v1.jsonnexus-attestation.v1.jsonnexus-clause.v1.jsonnexus-policy.v1.jsonnexus-proposal.v1.jsonnexus-subject-passport.v1.json
Catalogue entries of the applicable standards
Records in the standards scope, with their status and rights state.
| UNI | Title | Category | Status | Rights state |
|---|---|---|---|---|
NXS-STD-ST-000007 | Nexus Standards NS-11 – verification and monitoring | ST | draft | under review |
Questions and answers.
Who allocates UNIs for monitoring services artefacts?
What does the resolver return?
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.
