Nexus Standards · NS-7 · Specified

NS-7

NS-7: Resolver landing pages, page meta tags, sitemap

NS-7 is a specified Nexus Standard; the artifacts it governs are identified by UNIs (Unique Nexus Identifier). NS-7 is specified: SPECIFIED in NS-1 section 1 and NS-16 section 6; implementation status per implementation in registry/consumers.yaml.

01Overview

Summary

NS-7record
  1. Statusspecified
  2. Responsible scopepublic, client and partner delivery
  3. Identifiernot yet allocated
  4. Rules stated0
  5. Programme areas2
  6. Documentwithin NS-1
  7. Source filesrepository

Nexus Standards · proposed

02Where it is specified

Specification of NS-7

SPECIFIED in NS-1 section 1 and NS-16 section 6; implementation status per implementation in registry/consumers.yaml. Reference: registry/nexus-standards.yaml#identifier.resolver.

03Earth observation

Electrified and connected activity in North America

The map frames North America as an example geography for the subject of NS-7; 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

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 North America.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

04Canvas

NS-7 among the standards.

Canvas · NS-7 among the standardsProcess diagram
NS-7 in the standard setThe standards that NS-7 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-7 builds, those that cite it and the programme areas where it applies, from the texts and the registry.

05Process

The standard as a process

A request for /uni/<UNI (Unique Nexus Identifier)> is parsed and validated, the record is looked up, the response is negotiated (an HTML landing page for people, JSON for machines), versions and withdrawn states are shown with the record, and the page is listed in the sitemap. 7 operations in 5 phases; each states its actor, its decision rule, the record it leaves and the rule identifiers it implements (5 rules of NS-7 and the standards it applies).

Process · Resolving a UNI to its landing page7 operations · 5 phases
Resolving a UNI to its landing page (NS-7, specified in NS-1 section 1)A request for /uni/<UNI> is parsed and validated, the record is looked up, the response is negotiated (an HTML landing page for people, JSON for machines), versions and withdrawn states are shown with the record, and the page is listed in the sitemap.
All operations in order (7)
  1. 01

    Request /uni/<UNI> start · Request

    A citation, a link in an interface or a machine follows the resolver path.

    Who
    a person, a citation or a machine
    Decision rule
    citations resolve (NS-2)
    Record
    a request for the resolver path, the URN or the JSON path
    Implements
    NS2-R5
  2. 02

    Parse and validate gate · Parsing

    A malformed identifier is answered with a typed error; a legacy identifier is resolved through its crosswalk.

    Who
    the resolver
    Decision rule
    the identifier follows the NS-1 grammar
    Record
    the parsed segments, or a typed error
    Implements
    NS1-R7
  3. 03

    Look up the record step · Lookup

    The record is read from the catalog or the record store; a version suffix selects one state.

    Who
    the resolver
    Decision rule
    one record per UNI; versions share it
    Record
    the record and its versions
    Implements
    NS1-R1
  4. 04

    Retired records decision · Lookup

    A withdrawn record still resolves and says so; a record with a successor links to the record that follows it.

    Who
    the resolver
    Decision rule
    identifiers are never deleted; a replaced record points to its successor
    Record
    the record shown with its status and successor
    Implements
    NS1-R3
  5. 05

    Landing page record · Negotiation

    The landing page shows the record, its versions and its citation forms.

    Who
    the resolver
    Decision rule
    people receive a landing page
    Record
    an HTML page with the nexus-uni meta tag
    Implements
    NS1-R5
  6. 06

    JSON record record · Negotiation

    The same record in machine form, with the X-Nexus-UNI header.

    Who
    the resolver
    Decision rule
    machines receive JSON by content negotiation
    Record
    the record as JSON (/uni/<UNI>.json always JSON)
    Implements
    NS1-R5
  7. 07

    Sitemap entry end · Discovery

    Search engines and harvesters find landing pages through the sitemap.

    Who
    the resolver
    Decision rule
    published records are discoverable
    Record
    the landing page listed in the sitemap and in /uni

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-7: Resolver landing pages, page meta tags, sitemap · NS-2: Citation and attribution format for UNIs · NS-1: The UNI and the artifact catalog.

06Resolver

Resolver path and responses

Path template /uni/{uni}. NS-7: a resolver serves /uni (index) and /uni/<uni> as an HTML landing page (with the nexus-uni meta tag and Schema.org JSON-LD) or as JSON by content negotiation; /uni/<uni>.json is always JSON. A public resolver serves PUBLISHED, non-restricted records only. An implementation may also serve an authenticated catalog API under its own trust and assurance controls. The catalog file stays the reconstructable source.

08Research hub

Recent research on NS-7

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 termspersistent identifier resolution; reference rot; link rot; landing page; resolver; DataCite Metadata Schema; ORCID iDcombined with: identifier; identifiers; DOI; URL; webDerived 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.

09Source

NS-7 in the standards repository

The text, schemas, machine-readable files, registry rows, tests and history behind NS-7, 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
registry/nexus-standards.yamlwhere NS-7 is specifiedHistory
standards/INDEX.mdstatus and document of every standardHistory

Registry rows

FileWhat it holdsLinks
registry/standard-packages.yamlStandard packages - one package per external open standard on nexustandards.com · 6 rows or mentionsLine 115
registry/ecosystem-coverage.yamlNexus ecosystem coverage register (programme B corpus read) · 5 rows or mentionsLine 61
registry/open-standards-stack.yamlOpen-standards and open-source stack under the UNI · 4 rows or mentionsLine 46
registry/nexus-standards.yamlNexus Standards NS-1 - the UNI (Unique Nexus Identifier) and artifact catalog · 3 rows or mentionsLine 103
registry/subsites.yamlNexus Standards subsites - the systemic architecture of nexustandards.com · 2 rows or mentionsLine 79
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-site-pages.mjstool or validatorLine 292
tools/validate.mjstool or validatorLine 150

Change history

FileWhat it holdsLinks
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-7issue form: target, kind, rationale (NS-13)Template
Issue form: commentissue formTemplate
Issue form: errataissue formTemplate
Issues that mention NS-7open 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·
10Develop and take part

How NS-7 is developed, and how to take part

NS-7 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.

11External standards

Relation to external standards

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

12Research

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: persistent identifier resolution; reference rot; link rot; landing page; resolver; combined with: identifier; identifiers; DOI; URL; web. With JavaScript enabled, recent works matching these terms are listed from OpenAlex and Crossref.

13Education and training

Risk Academy courses and disciplines

1 course and 1 discipline of Risk Academy (risksacademy.com) that teach the knowledge and methods of NS-7. Each course lists its level, stream and learning hours.

14Across the network

Programmes, tracks and courses for this standard

GCRI Canada and Risk Academy work on the subject of NS-7 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.

Nexus RegistryMaintains registry interoperability.Apply to this programme therisk.globalAll programmes of GCRI Canada
15Questions

Questions and answers.

What is the status of NS-7?
NS-7 is specified. 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-7 establish?
Applying NS-7 is a statement by the implementer, verifiable under NS-11 where machine-readable clauses exist.
How is a change to NS-7 proposed?
By a proposal naming NS-7, 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.