Nexus Standards · Develop a standard

NS-13

Develop a standard

NS-13 makes the development of the standards open, recorded and owned by the communities that use them. It follows the openness principles practised by the internet and web standards communities (open participation, due process, consensus, transparency, balance and availability) and adds three properties: every step is an identified artifact, the standard is data, and conformance is observed. Each proposal, comment and decision is identified by a UNI (Unique Nexus Identifier).

Read NS-13Governance
01Canvas

The process.

Canvas · the Nexus track, NS-13Process diagram · 10 operations
The Nexus development track: from an open area to an adopted standard (NS-13)An area is opened; a chartered working group drafts in public; horizontal reviews and a public last call precede the proposed stage; two independent implementations precede the candidate stage; adoption is a recorded decision of the Global Standards Council (GSC); a later edition takes its place, or a decision withdraws it. The diagram shows the process as specified; it does not report the status of any standard, proposal or record.
All operations in order (10)
  1. 01

    Open area start · Open area

    The registry lists the area and its programme page invites participation. A working group may be chartered under NS-13.

    Who
    any participant; area listed in the registry
    Decision rule
    an area is open when the registry lists it and no working group has been chartered
    Record
    programme page with a call for participation
  2. 02

    Working group step · Working group

    The charter is public and states the scope, exclusions, deliverables, meeting schedule and decision rule. Drafts, issues and comments are public.

    Who
    chairs from two organisations
    Decision rule
    consensus with recorded dissent; two co-chairs from different organisations
    Record
    public charter
  3. 03

    Community draft record · Working group

    Drafts, issues and comment dispositions are public artifacts, each with a UNI (Unique Nexus Identifier). The chairs record each objection with its disposition.

    Who
    working group editors
    Decision rule
    every normative statement gets an NS-10 clause; every draft carries a UNI
    Record
    drafts with UNIs
  4. 04

    Horizontal reviews gate · Working group

    Each review group reads the whole draft and records findings; a finding is dispositioned in writing before the public last call opens.

    Who
    five review groups
    Decision rule
    accessibility, internationalisation, privacy, security and accuracy of claims, reviewed before last call
    Record
    review findings on record
  5. 05

    Public last call gate · Public

    The draft, its crosswalk rows with source links, its clauses and its test suite are published for comment. Consensus with recorded dissent; a formal objection is answered in writing; appeals go to the Technical Management Division (technical) or the independent panel (process).

    Who
    any person, with identity recorded
    Decision rule
    at least thirty days (fourteen for errata, ninety for a new standard); each comment answered in writing
    Record
    comments and dispositions
  6. 06

    Proposed record · Public

    The standard is proposed and available for voluntary use by implementers ahead of adoption.

    Who
    working group
    Decision rule
    entered when last call has closed and every comment has a disposition
    Record
    proposed edition
  7. 07

    Two implementations gate · Implementation

    Implementers run the Apache-2.0 test suite and publish their results by reference; the working group collects the final specification agreements.

    Who
    two independent implementers
    Decision rule
    two independent implementations pass the open test suite; the results serve as implementation evidence
    Record
    test results as evidence
  8. 08

    Candidate record · Implementation

    The implementation report names the implementations, the suite version and the instant of each run.

    Who
    working group
    Decision rule
    entered when the implementation report is published
    Record
    implementation report
  9. 09

    Adopted decision · Global Standards Council

    A permanent edition with a dated edition identifier; the errata process remains open; systematic review takes place every three years.

    Who
    the Global Standards Council (GSC)
    Decision rule
    a recorded decision of the GSC after last call
    Record
    dated edition with a decision reference
  10. 10

    Later edition or withdrawal end · Global Standards Council

    The record is retained and points to its successor. Earlier editions remain unchanged.

    Who
    a later edition or a withdrawal decision
    Decision rule
    identifiers are permanent and are not reused (NS1-R3)
    Record
    record retained, supersededBy set

Fig.From an open area to an adopted edition: the actor at each operation, the decision rule and the record it leaves. Play steps through the track; selecting a card shows its operation. Sources: NS-13: development process · Nexus Standards operating model.

02The track

Stages of development

Each stage has an entry condition and a visible result. A standard is described by the stage it has reached; stage names follow GOVERNANCE.md.

  1. Entry condition
    Area named in the registry
    What exists
    A programme page inviting contributions and a working-group charter template
    Rule
    No draft text yet; a working group may be chartered under NS-13.

The track draws on the development processes of the IETF, W3C and OGC. Stages may be selected with the arrow keys or by pointer; without script, all stages are shown in order. Stage names follow GOVERNANCE.md.

03Earth observation

Population, settlement and hazards in Europe

The map frames Europe as an example geography for the development of a standard; the frame gives context and is not a statement of where the standards apply. Shown at first: population density, 2020 (Gridded Population of the World v4.11, NASA SEDAC, CIESIN, Columbia University) and night-time lights, daily (VIIRS Black Marble, VNP46A2, NASA LAADS DAAC). The layer drawer adds flood water, 3-day composite (VIIRS Global Flood Product); active fires and thermal anomalies, last day (VIIRS NOAA-20 375 m, FIRMS); and 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

People and hazards

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.

Where people live, night-time lights and the floods and fires public institutions answer to, framed on Europe.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
  • 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 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
  • 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
  • NASA Fire Information for Resource Management System (FIRMS), VIIRS 375 m active fire product, NASA LANCE; vector tiles 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).
  • 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

  • Population density, 2020: Population: CIESIN, Columbia University, Gridded Population of the World v4.11 (2018), NASA SEDAC, CC BY 4.0 · static
  • Night-time lights, daily: VIIRS Black Marble (VNP46A2), NASA LAADS DAAC · 12 Oct 2026
  • Flood water, 3-day composite: VIIRS Global Flood Product, NASA LANCE · 14 Oct 2026
  • Active fires and thermal anomalies, last day: VIIRS NOAA-20 375 m (FIRMS), NASA LANCE FIRMS · 13 Oct 2026
  • True colour: VIIRS NOAA-20 corrected reflectance, NASA LANCE · 13 Oct 2026

04Lifecycle

Each Nexus Standard on the development track

The lifecycle console reads the status of each standard against the track and shows its current stage, the entry condition met and the next stage. Selecting a standard moves the diagram to its stage.

Lifecycle console · every Nexus Standard on the NS-13 trackFrom the registry
Canvas · the NS-13 trackProcess diagram · 10 operations
The Nexus development track: from an open area to an adopted standard (NS-13)An area is opened; a chartered working group drafts in public; horizontal reviews and a public last call precede the proposed stage; two independent implementations precede the candidate stage; adoption is a recorded decision of the Global Standards Council (GSC); a later edition takes its place, or a decision withdraws it. The diagram shows the process as specified; it does not report the status of any standard, proposal or record.
All operations in order (10)
  1. 01

    Open area start · Open area

    The registry lists the area and its programme page invites participation. A working group may be chartered under NS-13.

    Who
    any participant; area listed in the registry
    Decision rule
    an area is open when the registry lists it and no working group has been chartered
    Record
    programme page with a call for participation
  2. 02

    Working group step · Working group

    The charter is public and states the scope, exclusions, deliverables, meeting schedule and decision rule. Drafts, issues and comments are public.

    Who
    chairs from two organisations
    Decision rule
    consensus with recorded dissent; two co-chairs from different organisations
    Record
    public charter
  3. 03

    Community draft record · Working group

    Drafts, issues and comment dispositions are public artifacts, each with a UNI (Unique Nexus Identifier). The chairs record each objection with its disposition.

    Who
    working group editors
    Decision rule
    every normative statement gets an NS-10 clause; every draft carries a UNI
    Record
    drafts with UNIs
  4. 04

    Horizontal reviews gate · Working group

    Each review group reads the whole draft and records findings; a finding is dispositioned in writing before the public last call opens.

    Who
    five review groups
    Decision rule
    accessibility, internationalisation, privacy, security and accuracy of claims, reviewed before last call
    Record
    review findings on record
  5. 05

    Public last call gate · Public

    The draft, its crosswalk rows with source links, its clauses and its test suite are published for comment. Consensus with recorded dissent; a formal objection is answered in writing; appeals go to the Technical Management Division (technical) or the independent panel (process).

    Who
    any person, with identity recorded
    Decision rule
    at least thirty days (fourteen for errata, ninety for a new standard); each comment answered in writing
    Record
    comments and dispositions
  6. 06

    Proposed record · Public

    The standard is proposed and available for voluntary use by implementers ahead of adoption.

    Who
    working group
    Decision rule
    entered when last call has closed and every comment has a disposition
    Record
    proposed edition
  7. 07

    Two implementations gate · Implementation

    Implementers run the Apache-2.0 test suite and publish their results by reference; the working group collects the final specification agreements.

    Who
    two independent implementers
    Decision rule
    two independent implementations pass the open test suite; the results serve as implementation evidence
    Record
    test results as evidence
  8. 08

    Candidate record · Implementation

    The implementation report names the implementations, the suite version and the instant of each run.

    Who
    working group
    Decision rule
    entered when the implementation report is published
    Record
    implementation report
  9. 09

    Adopted decision · Global Standards Council

    A permanent edition with a dated edition identifier; the errata process remains open; systematic review takes place every three years.

    Who
    the Global Standards Council (GSC)
    Decision rule
    a recorded decision of the GSC after last call
    Record
    dated edition with a decision reference
  10. 10

    Later edition or withdrawal end · Global Standards Council

    The record is retained and points to its successor. Earlier editions remain unchanged.

    Who
    a later edition or a withdrawal decision
    Decision rule
    identifiers are permanent and are not reused (NS1-R3)
    Record
    record retained, supersededBy set

Fig.Select a standard in the table and the canvas shows the stage it is in; play walks the whole track. Sources: NS-13: development process · Nexus Standards operating model.

Standards by stage19 standards
  1. OPEN2
  2. COMMUNITY DRAFT0
  3. PROPOSED17
  4. CANDIDATE0
  5. ADOPTED0
  6. SUPERSEDED or WITHDRAWN0

Stages are derived from the status recorded in the registry.

StandardStatusStage on the trackRulesNext stage
NS-0 Constitution and principlesPROPOSEDPROPOSEDstatus in the registry12CANDIDATE: Two independent implementations pass the test suite; all comments dispositioned
NS-1 The UNI and the artifact catalog (grammar…PROPOSEDPROPOSEDstatus in the registry10CANDIDATE: Two independent implementations pass the test suite; all comments dispositioned
NS-2 Citation and attribution format for UNIsPROPOSEDPROPOSEDstatus in the registry5CANDIDATE: Two independent implementations pass the test suite; all comments dispositioned
NS-3 Risk record UNIs (grammar, legacy crosswalk,…PROPOSEDPROPOSEDstatus in the registry0CANDIDATE: Two independent implementations pass the test suite; all comments dispositioned
NS-3b Dataset and product metadata profile (STAC,…PROPOSEDPROPOSEDstatus in the registry0CANDIDATE: Two independent implementations pass the test suite; all comments dispositioned
NS-4 Structure and drafting of Nexus Standards and…PROPOSEDPROPOSEDstatus in the registry0CANDIDATE: Two independent implementations pass the test suite; all comments dispositioned
NS-5 Figure, map and visualization standard (with…PROPOSEDPROPOSEDstatus in the registry5CANDIDATE: Two independent implementations pass the test suite; all comments dispositioned
NS-6 Surface wiring (API header, panel provenance,…SPECIFIEDPROPOSED (in NS-1)specified within NS-1; follows its stage0CANDIDATE: Two independent implementations pass the test suite; all comments dispositioned
NS-7 Resolver landing pages, page meta tags, sitemapSPECIFIEDPROPOSED (in NS-1)specified within NS-1; follows its stage0CANDIDATE: Two independent implementations pass the test suite; all comments dispositioned
NS-8 Zenodo publishing workflow with legal gate,…OPENOPENstatus in the registry0COMMUNITY DRAFT: A chartered working group with chairs, scope, exclusions, deliverables,…
NS-9 Contextual UNIs (deployments, instances,…PROPOSEDPROPOSEDstatus in the registry5CANDIDATE: Two independent implementations pass the test suite; all comments dispositioned
NS-10 Policies and clauses (machine-readable…PROPOSEDPROPOSEDstatus in the registry7CANDIDATE: Two independent implementations pass the test suite; all comments dispositioned
NS-11 Verification and monitoring (evidence,…PROPOSEDPROPOSEDstatus in the registry6CANDIDATE: Two independent implementations pass the test suite; all comments dispositioned
NS-12 Software, model and AI/ML artifacts (supply…PROPOSEDPROPOSEDstatus in the registry4CANDIDATE: Two independent implementations pass the test suite; all comments dispositioned
NS-13 Standards development process (open proposals,…PROPOSEDPROPOSEDstatus in the registry5CANDIDATE: Two independent implementations pass the test suite; all comments dispositioned
NS-14 Conformance and crosswalk to external standardsPROPOSEDPROPOSEDstatus in the registry5CANDIDATE: Two independent implementations pass the test suite; all comments dispositioned
NS-15 System model binding (identity levels,…PROPOSEDPROPOSEDstatus in the registry0CANDIDATE: Two independent implementations pass the test suite; all comments dispositioned
NS-16 UNI application profile (context names such as…PROPOSEDPROPOSEDstatus in the registry0CANDIDATE: Two independent implementations pass the test suite; all comments dispositioned
NRS Nexus Risk Standards: the systemic catalogue…OPENOPENstatus in the registry0COMMUNITY DRAFT: A chartered working group with chairs, scope, exclusions, deliverables,…

Status follows standards/INDEX.md and GOVERNANCE.md, and the stage is derived from it. Proposals, public change records and their dispositions will be added to this console in a later release.

05Bodies compared

Development processes of the IETF, W3C, OASIS, OGC and ISO

Each process is described against the same questions: the number of operations, the decision points, the decision-maker and the means of public participation. Stage names are those of each body, with links to its process document.

TrackOperationsGatesWho decidesHow the public takes partProcess document
Nexus Standards10Horizontal reviews, Public last call, Two implementationsthe Global Standards Council (GSC), by a recorded decisiona public last call of at least thirty days; any person may comment, with identity recordedNS-13: development process
the IETF8WG adoption, WG last call, IETF last callthe IESG approves; the RFC Editor publishesIETF last call: the whole community, two or four weeks; working groups are open to anyoneRFC 2026, The Internet Standards Process,…
W3C8AC review, Candidate RecommendationW3C, after Advisory Committee reviewwide review of public drafts; comments in the group's public trackerW3C Process Document
OASIS8Public review, Statements of useOASIS organisational members, by ballotpublic review through the comment list; thirty days for the first reviewOASIS Technical Committee Process
OGC8OAB review, Public commentOGC voting members, by Technical Committee votea public comment period announced by OGCOGC Technical Committee Policies and…
ISO and IEC7Committee draft, Enquiry draft, Final draftnational bodies, by ballot at the enquiry and approval stagesthrough the national member bodies, which circulate the enquiry draftISO/IEC Directives, Part 1
Canvas · The IETF standards trackProcess diagram · 8 operations
The IETF standards track: Internet-Draft to Internet Standard (RFC 2026, RFC 6410)Authors post an Internet-Draft; a working group adopts it and runs its last call; the IETF-wide last call and the IESG evaluation follow; the RFC Editor publishes the RFC as a Proposed Standard; an Internet Standard needs interoperable implementations and deployment. The diagram shows the process as specified; it does not report the status of any standard, proposal or record.
All operations in order (8)
  1. 01

    Internet-Draft start · Authors

    Drafts are posted to the Datatracker and expire unless replaced. An individual draft may be adopted by a working group.

    Who
    any author
    Decision rule
    anyone may post; a draft is a work in progress and expires
    Record
    an Internet-Draft, expiring after six months
  2. 02

    WG adoption gate · Working group

    The chairs call for adoption on the list; the draft becomes a working-group document.

    Who
    working group chairs
    Decision rule
    rough consensus judged by the chairs
    Record
    a working-group draft
  3. 03

    WG last call gate · Working group

    The working group reviews the draft once more before it goes to the area director.

    Who
    working group
    Decision rule
    rough consensus; open issues resolved on the list
    Record
    last-call comments on the list
  4. 04

    IETF last call gate · IESG

    The whole community reviews the document; directorate reviews are recorded in the Datatracker.

    Who
    the IETF community
    Decision rule
    two weeks for a working-group document, four for an individual submission
    Record
    last-call announcement and comments
  5. 05

    IESG evaluation decision · IESG

    Area directors ballot; the document is approved for publication or returned to the working group.

    Who
    the Internet Engineering Steering Group
    Decision rule
    the IESG approves, with DISCUSS positions resolved
    Record
    a ballot with positions
  6. 06

    RFC Editor step · RFC Editor

    The RFC Editor edits for clarity and consistency; authors and the area director approve before publication.

    Who
    the RFC Production Center
    Decision rule
    editorial changes only; authors approve the final text
    Record
    AUTH48 state, then the RFC
  7. 07

    RFC, Proposed Standard record · RFC Editor

    The RFC is immutable; errata are recorded separately.

    Who
    RFC Editor
    Decision rule
    a Proposed Standard is a stable specification that has resolved known design choices
    Record
    the RFC with its number
  8. 08

    Internet Standard end · Maturity

    Under RFC 6410 the track has two maturity levels; advancement is a separate IESG decision.

    Who
    the IESG, on a request
    Decision rule
    interoperable implementations and successful deployment, no errata of substance
    Record
    an STD number

Fig.Authors post an Internet-Draft; a working group adopts it and runs its last call; the IETF-wide last call and the IESG evaluation follow; the RFC Editor publishes the RFC as a Proposed Standard; an Internet Standard needs interoperable implementations and deployment. Sources: RFC 2026, The Internet Standards Process, Revision 3 · RFC 6410, Reducing the Standards Track to Two Maturity Levels · RFC 7282, On Consensus and Humming in the IETF.

06Last call

Public last call and dispositions

  • Last call lasts at least thirty days for a proposed standard, fourteen days for an erratum and ninety days for a new standard; each comment receives a written disposition before acceptance.
  • Working groups decide by rough consensus with dissent recorded. A technical appeal goes to the co-chairs, the technical committee, the Technical Management Division and, on the record, the Global Standards Council; a process appeal goes to the independent Ethics, Conflicts and Appeals Panel.
  • Schemas and the registry use semantic versioning; documents use dated editions; changes to code lists are append-only.
07Systematic review

Systematic review every three years

Each adopted standard is reviewed every three years. The review concludes with a decision to confirm, revise or withdraw, recorded in the same way as an adoption decision. Errata are additive and do not change normative meaning; translations are informative.

08Who may participate, and where

Who may participate, and where

Anyone may participate: governments, international organisations, academia, industry, civil society, communities, investors, implementers and other standards bodies, as individuals (identified by ORCID iD) or organisations (identified by ROR ID), and agents acting under a recorded mandate and marked as agents. Participation requires no membership fee. Decisions are made by the recorded process, never according to who pays.

Participation takes place through public gateways: this public repository (proposals, issues and reviews), the institutional sites, the channels of the Secretariat and the sessions of the bodies (the Global Standards Council, its technical committees and working groups), as described in governance/PARTICIPATION_AND_CADENCE.md. No gateway requires a proprietary product, account or mark.

09The proposal lifecycle

The proposal lifecycle

StatusMeaningRecord
OPENA proposal is filed as an artifact with a UNI (nexus-proposal.v1.json), naming the target standard, section or registry path, the rationale, the changes (with a pull request or patch) and the stakeholder groups affected.proposal record
IN_REVIEWComments are collected in the open; each comment receives a disposition (accepted, rejected, deferred, open) with a reason.comments
LAST_CALLA fixed period (by default 30 days; 14 days for errata; 90 days for a new standard) is announced to all stakeholder groups; objections are answered in writing.lastCallEndsAt
ACCEPTED / REJECTED / WITHDRAWNThe editors' decision, with reasons, is recorded.decision
ADOPTEDThe decision of the Global Standards Council that changes the standard's status (the status ladder in GOVERNANCE.md) is recorded by reference.decisionRef

Every proposal, comment, decision and resulting version is itself an artifact (NS-1) and is cited (NS-2); no decision is taken in private channels.

10Editors and authority

Editors and authority

The Secretariat and the editors maintain the text and the registries and run the process; they do not adopt. Adoption of a Nexus Standard is a decision of the Global Standards Council under the Charter (governance/CHARTER.md), recorded by reference; adoption in a country is a decision of its National Standards Council (governance/NATIONAL_ADOPTION_AND_SOVEREIGNTY.md). An implementation that records adoption decisions verifies the mandate of the deciding body before it records the decision. Editors recuse themselves from proposals they raised. The editors' roster, their mandates and their recusals are records.

11Versioning

Versioning

Standards use semantic versions. A patch changes explanation only. A minor change is additive and backward compatible (new codes, optional fields, new clauses marked informative or recommended). A major change alters a grammar, a required field or a blocking clause and requires a crosswalk and a migration note. Implementations state the versions they conform to (NS-0 section 6). Registries are append-only (GOVERNANCE.md).

12Licensing of the standards

Licensing of the standards

The text, registries, schemas and data are published under CC BY 4.0 and the reference code under Apache-2.0, effective on public release (LICENSING.md). Contributions are made under the Developer Certificate of Origin, with a royalty-free patent licence for essential claims (governance/OPEN_BOUNDARY_IPR_AND_LICENSING.md). Implementations may be licensed as their authors choose, open or proprietary; no standard requires a particular licence of an implementation. Taking part grants or receives no licence to another body's standard.

13Rules

Rules

RuleText
NS13-R1Every change to a standard, registry, clause or policy shall enter through a proposal with a UNI.
NS13-R2Participation shall be open and free of charge; identity shall be recorded (ORCID iD, ROR ID or an agent mandate); decisions shall be reasoned in writing.
NS13-R3Last call shall be announced to every stakeholder group listed on the proposal; objections shall be dispositioned before acceptance.
NS13-R4Editors shall not adopt; authority decisions shall be recorded by reference.
NS13-R5Versions shall be semantic; registries shall be append-only; existing UNIs shall not be invalidated.
14Where

Submission of proposals

The canonical repository holds the standards, the registries and the proposal schema; a proposal is submitted as a pull request carrying a proposal record and a UNI. Canonical repository

15Questions

Questions and answers.

Who may take part?
Any stakeholder: standards bodies and their liaisons, public authorities, researchers, implementers and communities, including, in an activated jurisdiction, through the National Working Groups of its National Nexus Consortium. Participation is open and free of charge; identity is recorded (ORCID, ROR or a recorded mandate) and decisions are reasoned in writing (NS13-R2).
How long is last call?
Thirty days by default, fourteen days for errata and ninety days for a new standard; objections receive a written disposition before acceptance.
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

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.

Across the Consortium

The same subject across the Consortium.

Related

Around the 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.

Propose a change Roadmap to 2030Adopt and implement

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.