Nexus Standards · NS-6 · Specified
NS-6
NS-6: Surface wiring (API header, panel provenance, passports, OpenAPI)
NS-6 is a specified Nexus Standard; the artifacts it governs are identified by UNIs (Unique Nexus Identifier). NS-6 is specified: SPECIFIED in NS-1 section 6 and NS-16; implementation status per implementation in registry/consumers.yaml.
Summary
- Statusspecified
- Responsible scopetrust, authorization and assurance
- Identifiernot yet allocated
- Rules stated0
- Programme areas1
- Documentwithin NS-1
- Source filesrepository
Nexus Standards · proposed
Specification of NS-6
SPECIFIED in NS-1 section 6 and NS-16; implementation status per implementation in registry/consumers.yaml. Reference: registry/nexus-standards.yaml#surfaces.
Electrified and connected activity in East Asia
The map frames East Asia as an example geography for the subject of NS-6; the frame gives context and is not a statement of where the standards apply. Shown at first: night-time lights, daily (VIIRS Black Marble, VNP46A2, NASA LAADS DAAC) and population density, 2020 (Gridded Population of the World v4.11, NASA SEDAC, CIESIN, Columbia University). The layer drawer adds true colour (VIIRS NOAA-20 corrected reflectance). NASA products are served through NASA GIBS under NASA's open data policy, with acknowledgement; population density is GPW v4.11 by CIESIN, Columbia University, under CC BY 4.0; 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 2
Connected activity
Keyboard, with the map focused
Hold Ctrl or ⌘ and scroll to zoom
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.
Night-time lights and population density, the footprint of electrified, connected activity, framed on East Asia.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 EarthSources 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 Black Marble night-time lights, NASA Goddard Space Flight Center; distributed by the NASA Level-1 and Atmosphere Archive and Distribution System (LAADS DAAC); imagery via NASA GIBS. Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
- Center for International Earth Science Information Network (CIESIN), Columbia University. 2018. Gridded Population of the World, Version 4 (GPWv4): Population Density, Revision 11. NASA Socioeconomic Data and Applications Center (SEDAC). Licensed under CC BY 4.0. Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). doi:10.7927/H49C6VHW. CC BY 4.0
- 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
- 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.
- 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).
- Optional layers (3 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
- Night-time lights, daily: VIIRS Black Marble (VNP46A2), NASA LAADS DAAC · 12 Oct 2026
- Population density, 2020: Population: CIESIN, Columbia University, Gridded Population of the World v4.11 (2018), NASA SEDAC, CC BY 4.0 · static
- True colour: VIIRS NOAA-20 corrected reflectance, NASA LANCE · 13 Oct 2026
NS-6 among the standards.
Fig.The standards on which NS-6 builds, those that cite it and the programme areas where it applies, from the texts and the registry.
The standard as a process
Each surface listed in the registry declares how it carries the UNI (Unique Nexus Identifier); services return it as a response header, interfaces show it as a link, passports carry it first, landing pages carry a meta tag; a surface without a declared embedding is listed as such. 6 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-6 and the standards it applies).
All operations in order (6)
- 01
Surface registry start · Registry
Source files, documents, datasets, figures, APIs, interfaces, passports, landing pages and sites are listed with how each carries the UNI.
- Who
- the trust and assurance system
- Decision rule
- every surface declares its embedding
- Record
- the surfaces list in registry/nexus-standards.yaml with a status per surface
- Implements
- NS1-R5
- 02
Response header step · Services
Catalog, record and export routes answer with the UNI in the body and in the header.
- Who
- each service
- Decision rule
- the header names the record the response is about
- Record
- X-Nexus-UNI on every JSON response whose body carries a UNI
- Implements
- NS1-R5
- 03
Panels link UNIs step · Interfaces
Panels project the UNI of each source and show it as a link.
- Who
- each interface
- Decision rule
- a UNI shown is a UNI that resolves
- Record
- every cell that holds a UNI linked to /uni/<UNI>
- Implements
- NS1-R5, NS2-R5
- 04
Passport identity record · Interfaces
Valid UNIs link to the resolver; legacy dotted identifiers are shown unlinked.
- Who
- each passport
- Decision rule
- the passport carries the UNI first
- Record
- the UNI as the first field of the identity section
- Implements
- NS1-R5
- 05
Meta tag step · Pages
Institutional sites store the UNI with the post and print it in the page head.
- Who
- landing pages and institutional sites
- Decision rule
- pages carry the UNI as a meta tag
- Record
- <meta name="nexus-uni"> and data-nexus-uni on the component root
- Implements
- NS1-R5
- 06
Surface status end · Check
Planned embeddings read as planned until the hook is wired.
- Who
- the trust and assurance system
- Decision rule
- a surface without a declared embedding is recorded as such
- Record
- a status per surface in the registry
- Implements
- NS0-P8
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-6: Surface wiring · NS-1: The UNI and the artifact catalog · NS-2: Citation and attribution format for UNIs · NS-0: Constitution and principles.
Embedding of the UNI by surface
Each surface declares how it displays and resolves a UNI; a surface without a declared embedding does not conform to NS-6. Status is the implementation status of the surface.
| Surface | Responsible scope | Embedding | Status |
|---|---|---|---|
| http-apis | trust, authorization and assurance | httpApi | specified |
| panels-and-dashboards | visual composition and workflows | panel | specified |
| scientific-compute | canonical risk data, records and provenance | sourceFile | specified |
| data-products | canonical risk data, records and provenance | dataset | specified |
| docs-and-reports | knowledge, records and learning | markdown | specified |
| figures-and-maps | earth observation and digital twins | figure | specified |
| landing-and-resolver-pages | public, client and partner delivery | htmlPage | specified |
| content-management-systems | public, client and partner delivery | cms | specified |
| institutional-sites | public, client and partner delivery | htmlPage | specified |
| agents | trust, authorization and assurance | markdown | specified |
Programme areas that list NS-6
1 programme area list NS-6.
Recent research on NS-6
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 termsdata provenance; provenance tracking; API provenance; workflow provenance; JSON Schema 2020-12; OpenAPI Specificationcombined with: API; web services; data pipeline; reproducibility; lineageDerived 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.
NS-6 in the standards repository
The text, schemas, machine-readable files, registry rows, tests and history behind NS-6, 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
| File | What it holds | Links |
|---|---|---|
registry/nexus-standards.yaml | where NS-6 is specified | History |
standards/INDEX.md | status and document of every standard | History |
Registry rows
| File | What it holds | Links |
|---|---|---|
registry/ecosystem-coverage.yaml | Nexus ecosystem coverage register (programme B corpus read) · 10 rows or mentions | Line 124 |
registry/external-standards.yaml | External standards landscape that the Nexus Standards cite, crosswalk, profile, adopt or extend · 1 row or mentions | Line 566 |
registry/nexus-standards.yaml | Nexus Standards NS-1 - the UNI (Unique Nexus Identifier) and artifact catalog · 1 row or mentions | Line 238 |
registry/open-standards-stack.yaml | Open-standards and open-source stack under the UNI · 1 row or mentions | Line 136 |
registry/review-investigations.yaml | Circulation for technical review and comment, and the technical review areas · 1 row or mentions | Line 58 |
registry/subsites.yaml | Nexus Standards subsites - the systemic architecture of nexustandards.com · 1 row or mentions | Line 97 |
Tests and validators
| File | What it holds | Links |
|---|---|---|
tools/validate.mjs | tool or validator | Line 150 |
Change history
| File | What it holds | Links |
|---|---|---|
CHANGELOG.md | notable changes, by version | · |
release/manifest.json | release manifest with file digests | in-toto statement |
| Releases | tagged releases of the repository | · |
Propose a change
| File | What it holds | Links |
|---|---|---|
| Open a proposal on NS-6 | issue form: target, kind, rationale (NS-13) | Template |
| Issue form: comment | issue form | Template |
| Issue form: errata | issue form | Template |
| Issues that mention NS-6 | open and closed | · |
| Pull request template | what a change must carry: target, kind, rationale, validation | · |
CONTRIBUTING.md | pull requests, sign-off and checks | · |
GOVERNANCE.md | how registry codes and texts change | · |
How NS-6 is developed, and how to take part
NS-6 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.
- Who decides what: the decision-rights matrix.
- The process: stages, gates, review windows and appeals.
- Open gateways and calls: how to propose, comment, join a working group or request activation.
- Develop a standard: the development track and the lifecycle of each standard.
- NS-13 in the canonical repository.
Relation to external standards
NS-6 relates to external standards by identifier, clause number and URL (NS14-R1), and directs the reader to the issuing body.
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
- Identifiers for the 21st century: How to design, provision, and reuse persistent identifiers to maximize utility and impact of life science data
PLOS Biology · 2017 · Peer-reviewed - 20 Years of Persistent Identifiers - Which Systems are Here to Stay?
Data Science Journal · 2017 · Peer-reviewed - Unique, Persistent, Resolvable: Identifiers as the Foundation of FAIR
Data Intelligence · 2020 · Peer-reviewed - Decentralized Identifiers (DIDs) v1.0
W3C · 2022 · Standard - The many faces of publish/subscribe
ACM Computing Surveys · 2003 · Peer-reviewed - The dataflow model: a practical approach to balancing correctness, latency, and cost in massive-scale, unbounded, out-of-order data processing
Proceedings of the VLDB Endowment · 2015 · Peer-reviewed - MQTT Version 5.0
OASIS · 2019 · Standard - ORCID: a system to uniquely identify researchers
Learned Publishing · 2012 · Peer-reviewed
Related standards and frameworks
- W3C Verifiable Credentials Data Model v2.0
W3C Verifiable Credentials Working Group - SPDX (System Package Data Exchange) specification; ISO/IEC 5962:2021
SPDX project (Linux Foundation); ISO/IEC JTC 1 - CycloneDX Bill of Materials specification (ECMA-424)
OWASP CycloneDX; Ecma International TC54 - Sigstore (Cosign, Fulcio, Rekor)
OpenSSF (Linux Foundation); graduated project March 2024 - OpenSSF Best Practices Badge
OpenSSF - OpenAPI Specification
OpenAPI Initiative (Linux Foundation) - in-toto Attestation Framework
in-toto project (CNCF) - CodeMeta software metadata vocabulary
CodeMeta project
Search terms, derived from the subject of the standard and its rules: data provenance; provenance tracking; API provenance; workflow provenance; combined with: API; web services; data pipeline; reproducibility; lineage. With JavaScript enabled, recent works matching these terms are listed from OpenAlex and Crossref.
Risk Academy courses and disciplines
1 course and 1 discipline of Risk Academy (risksacademy.com) that teach the knowledge and methods of NS-6. Each course lists its level, stream and learning hours.
Courses
Disciplines
The correspondence between courses, disciplines and the Nexus Standards is maintained with Risk Academy and is subject to its academic review.
Programmes, tracks and courses for this standard
GCRI Canada and Risk Academy work on the subject of NS-6 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.
Research and evidence
GCRI Canada
Research programmes that produce the observations, models and assessments these records describe.
Digital Public InfrastructureStudies interoperability and application interfaces.Apply to this programme therisk.globalAll programmes of GCRI CanadaEducation and training
Risk Academy
Courses and disciplines that teach the knowledge and methods practitioners need to apply these standards.
Technology and DataRAT-204 · Intermediate · 19 learning hoursManaging risk data, AI, digital infrastructure and technology risk responsiblyTake this course All courses and disciplinesListed in the education and training section of this pageQuestions and answers.
What is the status of NS-6?
What does applying NS-6 establish?
How is a change to NS-6 proposed?
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.
- GatewayGW-STDSend it from this pageEvidence, a correction, a case, a method, a review, a translation or profile input. It arrives tagged with this page, so the editor who owns it receives it.
- ZenodoOpen depositDeposit it and submit to the communityPublish your own record on Zenodo with your ORCID iD, then submit it to the Nexus Reports community. Curators review it there; the DOI stays yours.
- Nexus ReportsGCRISee every way to contributeThe contribution types, how each is reviewed, what credit you receive, the licence and what is never accepted.
Never send personal data, sensitive infrastructure detail or anything you have no right to share. A contribution is reviewed before use; sending it confers no authorship or editorial rights, and sponsorship never buys a finding.
The same subject across the Consortium.
Around the 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.