NXS · Foundations
Inside NS-13: the open standards development process, step by step
NS-13 is the proposed rulebook for how Nexus Standards are proposed, debated, versioned and adopted. This explainer walks through who may take part, the proposal lifecycle, last call, the role of editors and councils, versioning and licensing.
- As of
- 3 November 2026
- Bacaan
- 10 minutes
- Bukti
- 15 sources, cited in order
- Status
- Proposed standard
- Kode
- NS-13 · Standards development process
Status and scope
A proposed standard. It is not adopted, approved or certified by any authority.
- Kode
- NS-13 · Standards development process
- Lingkup
- How Nexus Standards are proposed, debated, versioned and adopted, in the open.
- Berlaku untuk
- Every change to a Nexus Standard, registry, clause or policy.
- 1 Siapa yang boleh berpartisipasi
- 2 Siklus hidup usulan
- 3 Editor dan kewenangan
- 4 Pemberian versi
- 5 Lisensi standar
- 6 Aturan
01What the NS-13 open standards development process is
What the NS-13 open standards development process is
The NS-13 open standards development process is the proposed Nexus Standard that governs how the Nexus Standards themselves change. Its full title is Standards development process (open proposals, debate, versioning, adoption), its identifier is NXS-STD-ST-000008 and its current version is 0.1.0, catalogued on 16 October 2026 1.
Its page describes the aim in one sentence: to make the development of the standards open, recorded and owned by the communities that use them, in contrast to closed membership bodies and static editions 1. Like every Nexus Standard it rests on NS-0, whose principle of community-owned development it puts into practice 3. It is a preparatory working draft, circulated for review and comment on 17 October 2026, and is not for implementation 1.
02Why the process matters as much as the text
Why the process matters as much as the text
A standard is trusted for the way it was made. Regulators, procurers and engineers rely on a document because they can see who could take part, how objections were handled and who had the final word. That is why long-established bodies publish their process rules: the IETF in RFC 2026, part of Best Current Practice 9, and W3C in its Process Document, whose current edition is dated 18 August 2025 4,5.
The OpenStand affirmation of 2013 names the values these processes share: due process, broad consensus, transparency, balance and openness 6. The WTO's six principles for international standards add impartiality, effectiveness, coherence and attention to developing countries 7. NS-13 says it follows the openness principles of the internet and web standards communities and adds three things it says those bodies lack: every step is an identified record, the standard is data, and conformance is observed rather than audited 1.
Fig. 01The NS-13 proposal lifecycle
Figure 1 in words
Five rising steps. Open: a proposal is filed as a record with an identifier. In review: comments are collected in the open, each with a written disposition. Last call, highlighted: a fixed period announced to every stakeholder group, 30 days by default, 14 for errata and 90 for a new standard. Accepted, rejected or withdrawn: the editors' decision with reasons. Adopted: the authority decision that changes a standard's status, recorded in the legal registers.
03Siapa yang boleh berpartisipasi
Siapa yang boleh berpartisipasi
Clause 1 opens participation to anyone: governments, international organisations, academia, industry, civil society, communities, investors, implementers and other standards bodies 1. People take part as individuals identified by an ORCID iD and organisations by a ROR identifier, and software agents may take part only under a recorded mandate and marked as agents 1.
Participation needs no membership fee, and decisions are made by the recorded process, never by who pays 1. This is a deliberate contrast with membership-based consortia, where voting rights often depend on paid membership. Rule NS13-R2 restates it: participation is open and free, identity is recorded, and decisions are reasoned in writing 1.
04Siklus hidup usulan
Siklus hidup usulan
Clause 2 sets out five states for a proposal 1. A proposal is open once it is filed as a record with its own identifier. It names the target standard, section or registry path, the rationale, the changes and the stakeholder groups affected. It moves in review while comments are collected in the open, each with a disposition of accepted, rejected, deferred or open, and a reason.
It then enters last call, a fixed period announced to every stakeholder group: 30 days by default, 14 days for errata and 90 days for a new standard. Objections must be answered in writing 1. The editors then record a decision, accepted, rejected or withdrawn, with reasons. Finally, adopted is the authority decision that changes the standard's status, recorded in the owning institution's legal registers 1.
Every proposal, comment, decision and version is itself an identified, citable record, and nothing is decided in private channels 1. The last call is comparable to those of other bodies. RFC 2026 sets an IETF Last Call of no less than two weeks for a working group document and four weeks otherwise 4. W3C requires an Advisory Committee review of at least 28 days for a new charter 5. OASIS sets a first public review of at least 30 days 8, and OGC a 30-day public comment period 9.
Fig. 02Public review periods compared
Figure 2 in words
Column 1, proposed NS-13: last call of 30 days by default, 14 for errata and 90 for a new standard. Column 2, IETF under RFC 2026: Last Call of no less than two weeks for a working group document, four weeks otherwise. Column 3, W3C Process 2025: Advisory Committee review of a new charter, at least 28 days. Column 4, OASIS TC Process: first public review of at least 30 days. Column 5, OGC policies 05-020r29: a 30-day public comment period.
05Editors, councils and who decides
Editors, councils and who decides
Clause 3 separates running the process from deciding. Editors maintain the text and registries and run the process, but they do not adopt anything. They also step aside from proposals they raised, and the roster of editors, their mandates and recusals are records 1.
Adoption of a Nexus Standard is a decision of the Global Standards Council under its charter. Adoption in a country is a decision of that country's National Standards Council 1. The governance page describes these bodies 2. Neither has adopted any Nexus Standard: every standard in the catalogue is at most proposed 10. This split echoes the IETF, where consensus is judged by working-group chairs and approval rests with the Internet Engineering Steering Group, and where RFC 7282 explains that rough consensus means objections are addressed, not outvoted 4,11.
06Versioning and append-only registries
Versioning and append-only registries
Clause 4 adopts semantic versioning 1. A patch changes explanation only. A minor change is additive and backward compatible, such as new codes, optional fields or clauses marked informative or recommended. A major change alters a grammar, a required field or a blocking clause, and needs a crosswalk and a migration note 1. The scheme follows Semantic Versioning 2.0.0, which raises the major version for incompatible changes, the minor for backward-compatible additions and the patch for fixes 12.
Consumers state which versions they conform to, as NS-0 requires, and registries are append-only, so existing identifiers are never invalidated (rule NS13-R5) 1,3.
In practice this protects anyone who builds on a standard. A data publisher that conforms to version 1.2 of a standard can keep doing so when 1.3 adds an optional field, because a minor change cannot break it. A change that would break existing users must carry a new major number, a crosswalk from the old version and a migration note, so the cost of the change is visible before it is accepted 1,12. Because registries never delete entries, an identifier cited in a report or a dataset years earlier still resolves to the record it named 1.
07Lisensi standar
Lisensi standar
Clause 5 sets the licences: the text, registries, schemas and data are published under CC BY 4.0, and reference code under Apache-2.0, effective on public release 1,13,14. Contributions are made under the Developer Certificate of Origin, version 1.1, with a royalty-free patent licence for essential claims 1,15.
Implementations may be licensed as their authors choose, and no participant grants or receives a licence to another body's standard by taking part 1.
Fig. 03Who does what under NS-13
Figure 3 in words
Four layers from bottom to top. Participants: anyone, without a fee, proposes and comments, identified by ORCID, ROR or an agent mandate. Editors: maintain the text and registries, run the process, recuse on their own proposals and never adopt. Global Standards Council, highlighted: adopts a Nexus Standard by a recorded decision. National Standards Councils: decide adoption in each country.
08The five rules in one place
The five rules in one place
Clause 6 condenses the process into five rules, named NS13-R1 to NS13-R5 on the NS-13 page 1. NS13-R1 says every change to a standard, registry, clause or policy enters through a proposal with an identifier. NS13-R2 says participation is open and free, identity is recorded and decisions are reasoned in writing. NS13-R3 says last call is announced to every stakeholder group listed on the proposal and objections are dispositioned before acceptance. NS13-R4 says editors do not adopt and authority decisions are recorded references. NS13-R5 says versions are semantic, registries are append-only and existing identifiers are never invalidated.
09The process in use: open proposals on record
The process in use: open proposals on record
The change history on the NS-13 page shows the process being used on itself. Several proposals are listed with their own identifiers and the state OPEN, which means none has been accepted or adopted 1.
One of them, NXS-STD-PC-000008, proposes participation, cadence and gateways. It sets founding calls from 20 October 2026, an inaugural Council session on 12 January 2027 and a first quarterly review on 9 March 2027. It also proposes a monthly Council cadence on the second Tuesday at 14:00 UTC, 13 working groups, 8 expert communities and 4 open calls 1. These are proposals, not decisions: they take effect only if the process accepts them and the Council adopts them.
Another entry records the circulation of every document for technical review, with forty-three technical review areas and a call for technical review opening on 20 October 2026. The entry states that the circulation records no decision of any body 1. Reading the change history is the quickest way to see what is under discussion and where a comment is most useful.
10How NS-13 differs from membership bodies, and what it leaves open
How NS-13 differs from membership bodies, and what it leaves open
Two design choices set NS-13 apart. First, there is no fee and no membership tier, so no participant gains votes by paying 1. Second, the process is meant to be machine-readable: every proposal follows a published schema, nexus-proposal.v1.json, and every comment, decision and version is a record that software can read 1.
Some questions remain open while NS-13 is a draft. The governance page lists no constituted body yet and states that no body is described as constituted without a record 2. And because adoption has not happened, the claim that conformance can be observed rather than audited is still a design intent, not a demonstrated result 1. Readers who can test any of these are invited to comment through the process itself.
11How to take part
How to take part
The track is described step by step on Develop a standard 10. To propose a change, file a proposal naming the standard, the section and the rationale. To comment, respond during review or last call, and your comment will receive a written disposition 1. Comments and questions go through the contact form rather than email.
The governance page describes a Global Standards Council, four Technical Management Divisions, thirteen technical committees with their working groups, panels and a Secretariat, and states that councils decide the reserved matters, working groups draft, and everything else is open to any person without membership or fee 2. For the institutions of the wider network, see the Global Centre for Risk and Innovation, the Global Risks Forum and the Global Risks Alliance. Learners can study evidence and decision processes in Risk Academy's Science Policy 101.
12Processes and instruments related to NS-13
Processes and instruments related to NS-13
The table compares NS-13 with the process instruments of other bodies, as published on 3 November 2026. Each body's process applies only to its own work.
| Instrumen | Public review step | Edisi |
|---|---|---|
| Diusulkan NS-13 | Last call of 30 days by default (14 for errata, 90 for a new standard) | 0.1.0, proposed 1 |
| RFC 2026 (IETF) | IETF Last Call of at least two or four weeks | October 1996, BCP 9 4 |
| Dokumen Proses W3C | Advisory Committee review of a new charter, at least 28 days | 18 August 2025 5 |
| OASIS TC Process | First public review of at least 30 days | In force since 1 December 2020 8 |
| OGC 05-020r29 | 30-day public comment period | Version 29 9 |
What this page does not claim: NS-13 is a proposed, preparatory working draft that its own page says is not for implementation. Neither the Global Standards Council nor any National Standards Council has adopted it or any other Nexus Standard. The process instruments of the IETF, W3C, OASIS Open and OGC govern only those bodies' own work. Nexus Standards has no affiliation with any of them, and comparing review periods describes a similarity of practice, not an alignment claim.
Pertanyaan
Pertanyaan dan jawaban
Who can take part in developing a Nexus Standard?
Anyone, without a membership fee: individuals with an ORCID iD, organisations with a ROR identifier, and agents under a recorded mandate.
How long is the last call?
30 days by default, 14 days for errata and 90 days for a new standard, announced to every stakeholder group named on the proposal.
Can editors adopt a standard?
No. Editors run the process. Adoption is a recorded decision of the Global Standards Council, and in a country of its National Standards Council.
How are versions numbered?
With semantic versions: patch for explanation only, minor for backward-compatible additions, major for changes to a grammar, a required field or a blocking clause.
What is NS-13's own status?
Proposed. Version 0.1.0 is a preparatory working draft circulated on 17 October 2026 and not for implementation.
Ketentuan
Glosarium
- Panggilan terakhir
- A fixed public comment period before a decision; objections must be answered in writing.
- Disposisi
- The recorded answer to a comment: accepted, rejected, deferred or open, with a reason.
- Append-only registry
- A registry where entries are added but never deleted or changed in place, so identifiers stay valid.
- Semantic versioning
- A version scheme of major, minor and patch numbers that signals whether a change is incompatible, additive or a fix.
- Recusal
- An editor stepping aside from a decision on a proposal they raised.
Terkait
Further reading across the network
- All Nexus Standards
- NS-0: Konstitusi dan prinsip
- NS-1: The UNI and the artefact catalogue
- NS-11: Verification and monitoring
- NS-14: Conformance and crosswalk
- Mengembangkan standar
- Tata kelola Nexus Standards
- Foundations and Governance programme
- Constitution and principles area
- Glosarium
- The Global Risks Forum
- The Global Risks Alliance
Sumber
References
15 sources, numbered in the order they are first cited
- Nexus Standards (2026-10-16). NS-13: Standards development process (proposed). nexustandards.com. Accessed 2026-11-03.
- Nexus Standards (2026-11-03). Governance of the Nexus Standards. nexustandards.com. Accessed 2026-11-03.
- Nexus Standards (2026-10-16). NS-0: Constitution and principles (proposed). nexustandards.com. Accessed 2026-11-03.
- Internet Engineering Task Force (IETF) (1996-10). RFC 2026: The Internet Standards Process, Revision 3. www.rfc-editor.org. Accessed 2026-11-03.
- World Wide Web Consortium (W3C) (2025-08-18). W3C Process Document. www.w3.org. Accessed 2026-11-03.
- Internet Architecture Board (IAB) (2013-01). RFC 6852: Affirmation of the Modern Paradigm for Standards. www.rfc-editor.org. Accessed 2026-11-03.
- World Trade Organization (WTO) (2000). Principles for the Development of International Standards, Guides and Recommendations. www.wto.org. Accessed 2026-11-03.
- OASIS Open (2020-12-01). Technical Committee (TC) Process. www.oasis-open.org. Accessed 2026-11-03.
- Open Geospatial Consortium (OGC) (). OGC Technical Committee Policies and Procedures (05-020r29). docs.ogc.org. Accessed 2026-11-03.
- Nexus Standards (2026-11-03). Develop a standard. nexustandards.com. Accessed 2026-11-03.
- Internet Engineering Task Force (IETF) (2014-06). RFC 7282: On Consensus and Humming in the IETF. www.rfc-editor.org. Accessed 2026-11-03.
- Semantic Versioning (). Semantic Versioning 2.0.0. semver.org. Accessed 2026-11-03.
- Creative Commons (2013-11). Creative Commons Attribution 4.0 International Public License. creativecommons.org. Accessed 2026-11-03.
- Apache Software Foundation (2004-01). Apache License, Version 2.0. www.apache.org. Accessed 2026-11-03.
- The Linux Foundation (). Developer Certificate of Origin. developercertificate.org. Accessed 2026-11-03.
Catatan
Editorial record
Facts as of 3 November 2026. The NS-13 text, version and status were read on its page that day, and every external process instrument was checked at its issuer, except the Creative Commons licence, checked on 27 October 2026. The ROR site refused automated access, so ROR is named only as NS-13 names it. This page is reviewed at least every 180 days and whenever NS-13 changes version or status.
Published by the Standards desk, Nexus Standards. Drafted with AI assistance under the Nexus editorial constitution. To report an error, use the corrections page; corrections are dated and listed here.
Cite this article
Standards desk, Nexus Standards (2026, November 3). NS-13 open standards development process explained. Nexus Standards. https://nexustandards.com/ns-13-open-standards-development-process/
@online{standards2026ns13openstandardsdev,
author = {{Standards desk, Nexus Standards}},
title = {{NS-13 open standards development process explained}},
publisher = {Nexus Standards},
year = {2026},
month = {11},
url = {https://nexustandards.com/ns-13-open-standards-development-process/},
language = {en}
} TY - ELEC AU - Standards desk, Nexus Standards TI - NS-13 open standards development process explained PB - Nexus Standards PY - 2026 DA - 2026/11/03 UR - https://nexustandards.com/ns-13-open-standards-development-process/ LA - en ER -
Republish
Republish or translate this article free of charge, in print or online, under CC BY 4.0: keep the byline and Nexus Standards, link to the original and note any change. Figures, maps and twins made by the institutions carry the same licence; third-party data keeps its own credit line.
Attribution to paste
<p>Inside NS-13: the open standards development process, step by step — Standards desk, Nexus Standards, Nexus Standards. First published 3 November 2026 at <a href="https://nexustandards.com/ns-13-open-standards-development-process/">https://nexustandards.com/ns-13-open-standards-development-process/</a>. Republished under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/).</p>
Comment on this draft
Comments are taken clause by clause, with the exact text you propose and your evidence, through the comment form on this site.