Nexus Standards · NS-3b · Proposed

NS-3b

NS-3b: Dataset and product metadata profile (STAC, DCAT, PROV-O)

NS-3b is a proposed Nexus Standard; the artifacts it governs are identified by UNIs (Unique Nexus Identifier). NS-3b specifies how a dataset or product identified by a UNI is described for the geospatial, open-data and provenance communities, so that one catalog record feeds a STAC catalog, a DCAT catalog and a PROV-O graph without being described again. The UNI stays the key; every external identifier is a crosswalk from it.

01Instrument

Read a UNI.

Type or paste a Uniform Nexus Identifier: each segment is decoded against grammar 0.2 and the region, when it names a country, is lit on the globe above.

02Overview

Summary

NS-3brecord
  1. Statusproposed
  2. Responsible scopetrust, authorization and assurance; canonical risk data, records and provenance
  3. IdentifierNXS-STD-SW-000005
  4. Rules stated0
  5. Programme areas14
  6. Source filesrepository

Nexus Standards · proposed

03Status

Status of NS-3b

Preparatory working draft, circulated for review and comment. Not for implementation. Prepared and circulated by The Secretariat of the Nexus Standards, Global Centre for Risk and Innovation (GCRI Canada) (public@therisk.global), 17 October 2026. Technical review area: TR-02. This document is not a Nexus Standard; it may change without notice and is not to be implemented, relied upon or cited as a Nexus Standard. Its stage is designated only by the Global Standards Council and its technical committees under NS-13. Recipients are invited to submit comments with supporting reasons, and to notify any patent rights of which they are aware. See the notice of circulation.

04Earth observation

The land surface from orbit in the Amazon Basin

The map frames the Amazon Basin as an example geography for dataset footprints and Earth observation metadata; the frame gives context and is not a statement of where the standards apply. Shown at first: true colour (VIIRS NOAA-20 corrected reflectance, NASA LANCE). The layer drawer adds land cover type (IGBP), yearly (MODIS Terra and Aqua land cover, MCD12Q1); enhanced vegetation index, rolling 8 days (MODIS Terra EVI); snow cover (VIIRS NOAA-20 NDSI); and sea ice concentration (GHRSST MUR). NASA products are served through NASA GIBS under NASA's open data policy, with acknowledgement; coastlines, boundaries and place names come from NASA GIBS reference layers (© OpenStreetMap contributors, ODbL) and Natural Earth (public domain). Each layer shows its own observation date; full credits are given under the map.

The interactive map needs JavaScript; the layer list and sources are below.

Layers 1

Earth observation

Latest available

NASA GIBS / EOSDIS · ASTER GDEM (METI, NASA) · Blue Marble (NASA) · © OpenStreetMap contributors (ODbL) · Natural Earth

Loading the latest NASA imagery.

Drag to move. Ctrl or ⌘ and scroll, pinch or the buttons to zoom; hover for the values under the pointer; reset returns to the region.

True-colour imagery, land cover, vegetation, snow and sea ice, framed on the Amazon Basin.Satellite and model products as NASA publishes them, each with its own date; indicators, not assessments of any place.

Data: NASA GIBS · ASTER GDEM · Blue Marble · © OpenStreetMap contributors · Natural Earth · NASA EONETSources and licences

  • We acknowledge the use of imagery provided by services from NASA's Global Imagery Browse Services (GIBS), part of NASA's Earth Science Data and Information System (ESDIS). Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
  • We acknowledge the use of imagery provided by services from NASA's Global Imagery Browse Services (GIBS), part of NASA's Earth Science Data and Information System (ESDIS). Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
  • VIIRS near-real-time products (flood, land surface temperature, snow cover, corrected reflectance), NASA LANCE; imagery via NASA GIBS. Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
  • MODIS land products (vegetation indices, gross primary production, land cover), NASA LP DAAC and LANCE; imagery via NASA GIBS. Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
  • GHRSST Level 4 MUR analyses, NASA Jet Propulsion Laboratory; distributed by the NASA Physical Oceanography DAAC (PO.DAAC); imagery via NASA GIBS. Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
  • ASTER GDEM is a product of METI and NASA (ASTER Global Digital Elevation Model V003, NASA LP DAAC); imagery via NASA GIBS. Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). Cite as: NASA/METI/AIST/Japan Spacesystems and U.S./Japan ASTER Science Team (2019). ASTER Global Digital Elevation Model V003. doi:10.5067/ASTER/ASTGTM.003. NASA open data
  • Made with Natural Earth. Free vector and raster map data @ naturalearthdata.com. Public domain
  • © OpenStreetMap contributors (ODbL), via NASA GIBS (coastlines, boundaries, roads and place names). Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). ODbL
  • Blue Marble, NASA Earth Observatory; imagery via NASA GIBS. Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
  • Context on the globe and flat map: coastlines, boundaries, roads and place names from NASA GIBS reference layers (OpenStreetMap data, ODbL, © OpenStreetMap contributors); Blue Marble imagery as an optional base; 3D terrain and the elevation read-out from the ASTER GDEM elevation colour index (5 m to 200 m classes, exaggerated for legibility). Boundaries are drawn as published and imply no position on any territory.
  • Globe: MapLibre GL JS 6.9.1, BSD-3-Clause, © MapLibre contributors.
  • Live: NASA EONET Events are indicative, not authority warnings.
  • NASA GIBS: We acknowledge the use of imagery provided by services from NASA's Global Imagery Browse Services (GIBS), part of NASA's Earth Science Data and Information System (ESDIS).
  • Past year, daily temperature and sunshine (NASA POWER): These data were obtained from the NASA Langley Research Center (LaRC) POWER Project funded through the NASA Earth Science/Applied Science Program..
  • Optional layers (9 sources in the layer list: live, forecast, observed and context) print their provider credit on the map and here when switched on; forecasts are model output and derived indices are estimates.

Layers and dates

  • True colour: VIIRS NOAA-20 corrected reflectance, NASA LANCE · 13 Oct 2026
  • Land cover type (IGBP), yearly: MODIS Terra and Aqua land cover (MCD12Q1), NASA LP DAAC · 2024
  • Enhanced vegetation index, rolling 8 days: MODIS Terra EVI, NASA LANCE · 13 Oct 2026
  • Snow cover: VIIRS NOAA-20 NDSI, NASA LANCE · 13 Oct 2026
  • Sea ice concentration: GHRSST MUR, NASA JPL PO.DAAC · 12 Oct 2026

05Canvas

NS-3b among the standards.

Canvas · NS-3b among the standardsProcess diagram
NS-3b in the standard setThe standards that NS-3b cites, the standards that cite it, and the groups of programmes that list it, as recorded in the texts and the programme register.

Fig.The standards on which NS-3b builds, those that cite it and the programme areas where it applies, from the texts and the registry.

06Process

The standard as a process

A UNI (Unique Nexus Identifier)-keyed record is described once and exported as a STAC Item, a DCAT 3 dataset and a PROV-O bundle; record references become provenance entities a correction replay can walk; status fields and licences are carried verbatim. 7 operations in 5 phases; each states its actor, its decision rule, the record it leaves and the rule identifiers it implements (3 rules of NS-3b and the standards it applies).

Process · One record, three descriptions: the dataset and product metadata profile7 operations · 5 phases
One record, three descriptions: the dataset and product metadata profile (NS-3b)A UNI-keyed record is described once and exported as a STAC Item, a DCAT 3 dataset and a PROV-O bundle; record references become provenance entities a correction replay can walk; status fields and licences are carried verbatim.
All operations in order (7)
  1. 01

    UNI-keyed record start · Record

    The dataset or product is described once, in its catalog record.

    Who
    the publisher of record
    Decision rule
    the UNI stays the key; every external identifier is a crosswalk from it
    Record
    the catalog record of a dataset or product
    Implements
    NS1-R4
  2. 02

    STAC Item step · Profiles

    Each location becomes an asset with its checksum where a digest is recorded; a cite-as link points to the DOI where one exists.

    Who
    the export service
    Decision rule
    STAC 1.0 profile (section 1)
    Record
    an Item whose id is the UNI, with nexus properties and one asset per location
  3. 03

    DCAT 3 dataset step · Profiles

    Identifier, licence, publisher, creators with ORCID IRIs and the resolver landing page are mapped from the record.

    Who
    the export service
    Decision rule
    DCAT 3 profile (section 2)
    Record
    a dcat:Dataset in JSON-LD with one distribution per location
  4. 04

    PROV-O bundle step · Profiles

    Derived-from, revision, invalidation and membership relations become PROV-O predicates.

    Who
    the export service
    Decision rule
    DataCite relations map to PROV predicates (section 3)
    Record
    a prov:Bundle with one entity per UNI
  5. 05

    Record dependencies record · Provenance

    Record references keep their version, so a correction to one record can be traced to every product that used it.

    Who
    the export service
    Decision rule
    versions are revisions of their predecessors so that a correction replay can walk the graph
    Record
    record references as prov:used entities, each a specialisation of its record concept
    Implements
    NS2-R4
  6. 06

    Carry states as is gate · Checks

    Legal state, claim level and status pass through unchanged; a restrictive licence stays restrictive in every format.

    Who
    the export service
    Decision rule
    the profile describes and asserts nothing; a proprietary licence is never mapped to an open licence (section 4)
    Record
    status fields and licence carried verbatim
    Implements
    NS0-P8
  7. 07

    Export by format end · Export

    Catalogues, open-data portals and provenance graphs read the same record without a second description.

    Who
    any client
    Decision rule
    every catalogued artifact can be exported in each format
    Record
    format=stac, dcat or prov from the record's export path

Fig.Phases read left to right; each card names the operation, its actor and the record it leaves, and each edge label names the hand-over. Play, step or scrub; the detail panel gives the full text of the selected operation. Sources: NS-3b: Dataset and product metadata profile · NS-1: The UNI and the artifact catalog · NS-2: Citation and attribution format for UNIs · NS-0: Constitution and principles.

07Specification

NS-3b clause by clause

5 clauses and 0 rules as stated in the standard, presented with numbered clauses, stable rule anchors, versions and changes.

Versions0.1.016 October 2026current versionchangelog0.6.0 (2026-10-19), complete release
1

STAC

A record is exported as a SpatioTemporal Asset Catalog (STAC) Item conforming to STAC 1.1 (an Item that conforms to 1.0 remains readable). The Item's id is the UNI. It carries the properties nexus:uni, nexus:urn, nexus:scope, nexus:category, nexus:region, nexus:legalState, nexus:claimCeiling and nexus:status; one asset per location (with file:checksum when a digest is recorded); a cite-as link to the DOI when one exists; and related links to other UNIs. Geometry, bounding box and datetimes are only what the caller states; nothing is inferred from the REGION segment, because a country code is not a footprint. Without a stated extent, the Item has geometry: null and datetime: null, which STAC permits and which is the honest state. A set of records is exported as a STAC Collection of Items.

2

DCAT 3

A record is exported as a dcat:Dataset in JSON-LD under the W3C Data Catalog Vocabulary (DCAT) Version 3: dct:identifier carries the URN and the DOI; dct:license the SPDX licence IRI (or the LicenseRef- string unchanged); dct:publisher the publisher of record; dct:creator the persons and organisations, with ORCID iDs and ROR IDs as IRIs; one dcat:Distribution per location; dcat:landingPage the resolver page; and dct:relation the related identifiers. The honesty fields (nexus:legalState, nexus:claimCeiling, nexus:status) travel with the dataset.

3

PROV-O

A record is exported as a prov:Bundle (W3C PROV-O) with one prov:Entity per UNI. DataCite relation types map to PROV predicates:

relatedIdentifiers.relationPROV-O
IsDerivedFromprov:wasDerivedFrom
IsNewVersionOfprov:wasRevisionOf
IsObsoletedByprov:wasInvalidatedBy
IsVariantFormOf, IsIdenticalToprov:alternateOf
HasPartprov:hadMember
Compilesprov:hadPrimarySource
Other relations (IsPartOf, Requires, Cites and others)nexus: predicates, or omitted when they carry no provenance meaning

Record refs (<recordUni>@<recordVersion>, in legacy or NS-1 form) become prov:used entities. Each version is prov:specializationOf its record concept and prov:wasRevisionOf the previous version, so that the correction dependencies of a product form a graph that a correction replay can traverse. Legacy identifiers appear as nexus:legacy:<id> with nexus:legacyUni until a UNI is allocated.

4

Honesty

The profile describes; it does not assert truth, readiness or approval. legalState, claimCeiling and status are carried verbatim. A proprietary licence is stated as proprietary (STAC) or as the LicenseRef- string (DCAT) and is never mapped to an open licence.

5

Adoption

  • An implementation that serves exports offers format=stac, format=dcat and format=prov for every catalogued artifact it publishes (NS-1 section 6).
  • An ingest that allocates NS-3 record UNIs keeps the legacy recordUni as its key and reports ALLOCATED, NOT_REQUESTED or UNAVAILABLE (NS-3 section 4). The observation ref NXS-GRX-OB-<ISO3>-<serial>@<recordVersion> is what a product cites in its correction dependencies and what its PROV-O bundle turns into prov:used.
Δ

Changes between versions

One published version is available (0.1.0); a comparison between versions is shown once a second version is published.

Clause numbers follow the sections of the document; rule identifiers () are stable anchors. With script enabled, each clause and rule has a permalink and a machine-readable view (YAML and JSON), and the j and k keys move between clauses.

09Research hub

Recent research on NS-3b

Recent peer-reviewed articles, preprints, datasets and reports on the subject of this standard, retrieved at the time of reading from open scholarly metadata services (OpenAlex, Crossref, DataCite, Zenodo, arXiv, Europe PMC, OpenAIRE Graph) with search terms composed from the registry. Each work is listed with its authors, venue, year, type, open-access status and licence, and links to its DOI or landing page. Sources not yet enabled for live display on this site are listed for reference and are not queried.

Search termsSpatioTemporal Asset Catalog; DCAT; PROV-O; metadata profile; provenance metadata; geospatial metadata; Schema.org vocabulary; RFC 7946 The GeoJSON Formatcombined with: metadata; data; provenance; geospatialDerived from the subject of the standard and its rules, and the external standards of its crosswalk domains.

  • OpenAlexlisted for reference; not queried
  • Crossreflisted for reference; not queried
  • DataCitelisted for reference; not queried
  • Zenodolisted for reference; not queried
  • arXivlisted for reference; not queried
  • Europe PMClisted for reference; not queried
  • OpenAIRE Graphlisted for reference; not queried

No source is enabled for live display on this site yet: the sources are listed for reference and none is queried. Once the publisher of record enables a source after its terms are reviewed, recent works are listed here. Metadata and links only: title, authors, venue, year, type, open-access status and licence as each source records them; works are listed for orientation, not reviewed or endorsed.

10Source

NS-3b in the standards repository

The text, schemas, machine-readable files, registry rows, tests and history behind NS-3b, on the main branch of the canonical repository. Text, registry, schemas and catalog are CC BY 4.0; tools and tests are Apache-2.0.

Source text

FileWhat it holdsLinks
standards/NS-3b-dataset-and-product-metadata-profile.mdNXS-STD-SW-000005Raw · History · Suggest an edit
standards/INDEX.mdstatus and document of every standardHistory

Machine-readable files

FileWhat it holdsLinks
catalog/artifact-catalog.yamlcatalog records · 2 mentionsFirst mention, line 127

Registry rows

FileWhat it holdsLinks
registry/ecosystem-coverage.yamlNexus ecosystem coverage register (programme B corpus read) · 71 rows or mentionsLine 106
registry/standard-packages.yamlStandard packages - one package per external open standard on nexustandards.com · 14 rows or mentionsLine 53
registry/subsites.yamlNexus Standards subsites - the systemic architecture of nexustandards.com · 11 rows or mentionsLine 37
registry/open-standards-stack.yamlOpen-standards and open-source stack under the UNI · 4 rows or mentionsLine 56
registry/external-standards.yamlExternal standards landscape that the Nexus Standards cite, crosswalk, profile, adopt or extend · 3 rows or mentionsLine 1242
registry/review-investigations.yamlCirculation for technical review and comment, and the technical review areas · 1 row or mentionsLine 58

Tests and validators

FileWhat it holdsLinks
tools/build-risk-standards.mjstool or validatorLine 97
tools/build-site-pages.mjstool or validatorLine 292
tools/validate.mjstool or validatorLine 150

Change history

FileWhat it holdsLinks
Commits to the textevery change to the text·
CHANGELOG.mdnotable changes, by version·
release/manifest.jsonrelease manifest with file digestsin-toto statement
Releasestagged releases of the repository·

Propose a change

FileWhat it holdsLinks
Open a proposal on NS-3bissue form: target, kind, rationale (NS-13)Template
Issue form: commentissue formTemplate
Issue form: errataissue formTemplate
Issues that mention NS-3bopen and closed·
Pull request templatewhat a change must carry: target, kind, rationale, validation·
CONTRIBUTING.mdpull requests, sign-off and checks·
GOVERNANCE.mdhow registry codes and texts change·
11Develop and take part

How NS-3b is developed, and how to take part

NS-3b is developed in the open under NS-13 (the stages and gates of NS-13). Working groups draft, councils decide the reserved matters, and anyone may propose a change, comment, submit an implementation report, object or appeal, without membership or fee.

12External standards

Relation to external standards

NS-3b relates to external standards by identifier, clause number and URL (NS14-R1), and directs the reader to the issuing body.

13Research

Recent research and sources

Peer-reviewed articles, preprints, reports and datasets on the subject of this standard, retrieved at the time of reading from open scholarly metadata services (OpenAlex and Crossref) and listed with authors, venue, year, type and access status, with a link to each work. Curated references and related standards are listed first; recent works matched by subject follow and are listed for orientation.

Curated references

Related standards and frameworks

Search terms, derived from the subject of the standard and its rules: SpatioTemporal Asset Catalog; DCAT; PROV-O; metadata profile; provenance metadata; geospatial metadata; combined with: metadata; data; provenance; geospatial. With JavaScript enabled, recent works matching these terms are listed from OpenAlex and Crossref.

15Across the network

Programmes, tracks and courses for this standard

GCRI Canada and Risk Academy work on the subject of NS-3b in distinct roles (research and evidence; education and training). Each entry states why it corresponds and the step it offers; each institution sets its own terms of participation.

16Questions

Questions and answers.

What is the status of NS-3b?
NS-3b is proposed. It may be applied voluntarily; adoption follows last call and a decision of the Global Standards Council, and national adoption is decided by each National Standards Council.
What does applying NS-3b establish?
Applying NS-3b is a statement by the implementer, verifiable under NS-11 where machine-readable clauses exist.
How is a change to NS-3b proposed?
By a proposal naming NS-3b, the section concerned and the rationale; it passes review and last call under NS-13.
NRNexus Reports gateway · GW-STD

Contribute to Nexus Reports from this page.

Nexus Reports is the Consortium's quarterly publication. What you know about this subject can become evidence, a case or a correction in the next edition, credited to you and published under CC BY 4.0 where it is your own work.

Nexus Standards
Nexus Standards

Take part in the standards.

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 artifact; 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.