Skip to content
StandaardeOntwikkel 'n standaard
NS-13

Ontwikkel 'n standaard

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 artefact, the standard is data, and conformance is observed. Each proposal, comment and decision is identified by a UNI (Unique Nexus Identifier).

How a standard moves
The NS-13 proposal lifecycle, then the status of every standard in the registry today. No standard is adopted until the Global Standards Council decides.Source: NS-13 section 2; the Nexus Standards registry; the risk standards catalogue.
  • Step 1, OPEN: Proposal filed.
  • Step 2, IN_REVIEW: Comments disposed.
  • Step 3, LAST_CALL: Fixed period.
  • Step 4, DECISION: Editors decide.
  • Step 5, ADOPTED: Council adopts.
  • Foundation standards PROPOSED: 15.
  • Foundation standards SPECIFIED: 2.
  • Foundation standards OPEN: 1.
  • Risk standards OPEN: 348.
01Proses

The process.

Process explorer · NXS · Process

Nexus development track (NS-13)

10 steps5 stages3 gates

NXS · Process

Nexus development track (NS-13)

A chartered group drafts in public, reviews and last call precede proposal, two implementations precede candidacy, and the Global Standards Council records adoption.

  1. 01 Open area

    1. 01Open areaStart · any participant; area listed in the registryThe registry lists the area and its programme page invites participation. A working group may be chartered under NS-13.
  2. 02 Working group

    1. 02Horizontal reviewsGate · five review groupsEach review group reads the whole draft and records findings; a finding is dispositioned in writing before the public last call opens.
    2. 03Working groupStep · chairs from two organisationsThe charter is public, with scope, exclusions, deliverables, schedule and decision rule. Drafts, issues and comments are public.
    3. 05Community draftRecord · working group editorsDrafts, issues and comment dispositions are public, each with a UNI. Chairs record each objection with its disposition.
  3. 03 Public

    1. 04Public last callGate · any person, with identity recordedDraft, crosswalk, clauses and test suite go out for comment. Consensus with recorded dissent, and written answers to objections.
    2. 06ProposedRecord · working groupThe standard is proposed and available for voluntary use by implementers ahead of adoption.
  4. 04 Implementation

    1. 07Two implementationsGate · two independent implementersImplementers run the Apache-2.0 test suite and publish results by reference. The group collects final specification agreements.
    2. 08CandidateRecord · working groupThe implementation report names the implementations, the suite version and the instant of each run.
  5. 05 Global Standards Council

    1. 09AdoptedDecision · the Global Standards Council (GSC)A permanent, dated edition. Errata stay open, and systematic review takes place every three years.
    2. 10Later edition or withdrawalOutcome · a later edition or a withdrawal decisionThe record is retained and points to its successor. Earlier editions remain unchanged.

NS-13: development process · Nexus Standards operating modelAn outline of how the work is designed to run; it does not report the status of any decision or record.

The operations, as a table
Process · the development track, NS-1310 operations
StepPhaseOperationWhoDecision ruleRecord
01Open areaOpen area (start). The registry lists the area and its programme page invites participation. A working group may be chartered under NS-13.any participant; area listed in the registryan area is open when the registry lists it and no working group has been charteredprogramme page with a call for participation
02WerkgroepWorking group (step). The charter is public and states the scope, exclusions, deliverables, meeting schedule and decision rule. Drafts, issues and comments are public.chairs from two organisationsconsensus with recorded dissent; two co-chairs from different organisationspublic charter
03WerkgroepCommunity draft (record). Drafts, issues and comment dispositions are public artefacts, each with a UNI (Unique Nexus Identifier). The chairs record each objection with its disposition.working group editorsevery normative statement gets an NS-10 clause; every draft carries a UNIdrafts with UNIs
04WerkgroepHorizontal reviews (gate). Each review group reads the whole draft and records findings; a finding is dispositioned in writing before the public last call opens.five review groupsaccessibility, internationalisation, privacy, security and accuracy of claims, reviewed before last callreview findings on record
05OpenbaarPublic last call (gate). 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).any person, with identity recordedat least thirty days (fourteen for errata, ninety for a new standard); each comment answered in writingcomments and dispositions
06OpenbaarProposed (record). The standard is proposed and available for voluntary use by implementers ahead of adoption.working groupentered when last call has closed and every comment has a dispositionproposed edition
07ImplementeringTwo implementations (gate). Implementers run the Apache-2.0 test suite and publish their results by reference; the working group collects the final specification agreements.two independent implementerstwo independent implementations pass the open test suite; the results serve as implementation evidencetest results as evidence
08ImplementeringCandidate (record). The implementation report names the implementations, the suite version and the instant of each run.working groupentered when the implementation report is publishedimplementation report
09Global Standards CouncilAdopted (decision). A permanent edition with a dated edition identifier; the errata process remains open; systematic review takes place every three years.the Global Standards Council (GSC)a recorded decision of the GSC after last calldated edition with a decision reference
10Global Standards CouncilLater edition or withdrawal (end). The record is retained and points to its successor. Earlier editions remain unchanged.a later edition or a withdrawal decisionidentifiers are permanent and are not reused (NS1-R3)record retained, supersededBy set

Table.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. The table shows the process as specified; it does not report the status of any standard, proposal or record. Sources: NS-13: development process · Nexus Standards operating model.

Steps
5
NS-13 lifecycle
Voorgestel
15
foundation standards
Maak oop
349
for proposals
Adopted
0
by the Council
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 wat in die register benoem is
    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.

03Lifecycle

Each 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 standard on the NS-13 trackFrom the registry

Process explorer · NXS · Process

Nexus development track (NS-13)

10 steps5 stages3 gates

NXS · Process

Nexus development track (NS-13)

Lewensiklus van 'n standaard · NS-13-spoor · Bydraekanale · IETF-spoor · W3C-spoor · OGC-spoor · OASIS-spoor · ISO- en IEC-fases · Konformiteit · Rekordlewensiklus · Roetering · Monitering.

A chartered group drafts in public, reviews and last call precede proposal, two implementations precede candidacy, and the Global Standards Council records adoption.

  1. 01 Open area

    1. 01Open areaStart · any participant; area listed in the registryThe registry lists the area and its programme page invites participation. A working group may be chartered under NS-13.
  2. 02 Working group

    1. 02Horizontal reviewsGate · five review groupsEach review group reads the whole draft and records findings; a finding is dispositioned in writing before the public last call opens.
    2. 03Working groupStep · chairs from two organisationsThe charter is public, with scope, exclusions, deliverables, schedule and decision rule. Drafts, issues and comments are public.
    3. 05Community draftRecord · working group editorsDrafts, issues and comment dispositions are public, each with a UNI. Chairs record each objection with its disposition.
  3. 03 Public

    1. 04Public last callGate · any person, with identity recordedDraft, crosswalk, clauses and test suite go out for comment. Consensus with recorded dissent, and written answers to objections.
    2. 06ProposedRecord · working groupThe standard is proposed and available for voluntary use by implementers ahead of adoption.
  4. 04 Implementation

    1. 07Two implementationsGate · two independent implementersImplementers run the Apache-2.0 test suite and publish results by reference. The group collects final specification agreements.
    2. 08CandidateRecord · working groupThe implementation report names the implementations, the suite version and the instant of each run.
  5. 05 Global Standards Council

    1. 09AdoptedDecision · the Global Standards Council (GSC)A permanent, dated edition. Errata stay open, and systematic review takes place every three years.
    2. 10Later edition or withdrawalOutcome · a later edition or a withdrawal decisionThe record is retained and points to its successor. Earlier editions remain unchanged.

NS-13: development process · Nexus Standards operating modelAn outline of how the work is designed to run; it does not report the status of any decision or record.

The operations, as a table
Process · the NS-13 track10 operations
StepPhaseOperationWhoDecision ruleRecord
01Open areaOpen area (start). The registry lists the area and its programme page invites participation. A working group may be chartered under NS-13.any participant; area listed in the registryan area is open when the registry lists it and no working group has been charteredprogramme page with a call for participation
02WerkgroepWorking group (step). The charter is public and states the scope, exclusions, deliverables, meeting schedule and decision rule. Drafts, issues and comments are public.chairs from two organisationsconsensus with recorded dissent; two co-chairs from different organisationspublic charter
03WerkgroepCommunity draft (record). Drafts, issues and comment dispositions are public artefacts, each with a UNI (Unique Nexus Identifier). The chairs record each objection with its disposition.working group editorsevery normative statement gets an NS-10 clause; every draft carries a UNIdrafts with UNIs
04WerkgroepHorizontal reviews (gate). Each review group reads the whole draft and records findings; a finding is dispositioned in writing before the public last call opens.five review groupsaccessibility, internationalisation, privacy, security and accuracy of claims, reviewed before last callreview findings on record
05OpenbaarPublic last call (gate). 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).any person, with identity recordedat least thirty days (fourteen for errata, ninety for a new standard); each comment answered in writingcomments and dispositions
06OpenbaarProposed (record). The standard is proposed and available for voluntary use by implementers ahead of adoption.working groupentered when last call has closed and every comment has a dispositionproposed edition
07ImplementeringTwo implementations (gate). Implementers run the Apache-2.0 test suite and publish their results by reference; the working group collects the final specification agreements.two independent implementerstwo independent implementations pass the open test suite; the results serve as implementation evidencetest results as evidence
08ImplementeringCandidate (record). The implementation report names the implementations, the suite version and the instant of each run.working groupentered when the implementation report is publishedimplementation report
09Global Standards CouncilAdopted (decision). A permanent edition with a dated edition identifier; the errata process remains open; systematic review takes place every three years.the Global Standards Council (GSC)a recorded decision of the GSC after last calldated edition with a decision reference
10Global Standards CouncilLater edition or withdrawal (end). The record is retained and points to its successor. Earlier editions remain unchanged.a later edition or a withdrawal decisionidentifiers are permanent and are not reused (NS1-R3)record retained, supersededBy set

Table.Select a standard in the table and the canvas shows the stage it is in; play walks the whole track. The table shows the process as specified; it does not report the status of any standard, proposal or record. Sources: NS-13: development process · Nexus Standards operating model.

Standards by stage19 standards
  1. OPEN2
  2. GEMEENSKAPSKONSEP0
  3. VOORGESTEL17
  4. KANDIDAAT0
  5. AANVAAR0
  6. VERVANG of ONTTREK0

Stages are derived from the status recorded in the registry.

StandaardStatusStage on the trackRulesNext stage
NS-0 Grondwet en beginselsVOORGESTELPROPOSEDstatus in the registry12CANDIDATE: Two independent implementations pass the test suite; all comments dispositioned
NS-1 The UNI and the artefact catalogue (grammar…VOORGESTELPROPOSEDstatus in the registry10CANDIDATE: Two independent implementations pass the test suite; all comments dispositioned
NS-2 Aanhalings- en erkenningsformaat vir UNI'sVOORGESTELPROPOSEDstatus in the registry5CANDIDATE: Two independent implementations pass the test suite; all comments dispositioned
NS-3 Risk record UNIs (grammar, legacy crosswalk,…VOORGESTELPROPOSEDstatus in the registry0CANDIDATE: Two independent implementations pass the test suite; all comments dispositioned
NS-3b Dataset and product metadata profile (STAC,…VOORGESTELPROPOSEDstatus in the registry0CANDIDATE: Two independent implementations pass the test suite; all comments dispositioned
NS-4 Structure and drafting of Nexus Standards and…VOORGESTELPROPOSEDstatus in the registry0CANDIDATE: Two independent implementations pass the test suite; all comments dispositioned
NS-5 Figure, map and visualisation standard (with…VOORGESTELPROPOSEDstatus 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 Landingsbladsye van die oplosser, bladsy-metamerkers, werfkaartSPECIFIEDPROPOSED (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,…VOORGESTELPROPOSEDstatus in the registry5CANDIDATE: Two independent implementations pass the test suite; all comments dispositioned
NS-10 Policies and clauses (machine-readable…VOORGESTELPROPOSEDstatus in the registry7CANDIDATE: Two independent implementations pass the test suite; all comments dispositioned
NS-11 Verification and monitoring (evidence,…VOORGESTELPROPOSEDstatus in the registry6CANDIDATE: Two independent implementations pass the test suite; all comments dispositioned
NS-12 Software, model and AI/ML artefacts (supply…VOORGESTELPROPOSEDstatus in the registry4CANDIDATE: Two independent implementations pass the test suite; all comments dispositioned
NS-13 Standards development process (open proposals,…VOORGESTELPROPOSEDstatus in the registry5CANDIDATE: Two independent implementations pass the test suite; all comments dispositioned
NS-14 Konformiteit en ooreenkomstabel met eksterne standaardeVOORGESTELPROPOSEDstatus in the registry5CANDIDATE: Two independent implementations pass the test suite; all comments dispositioned
NS-15 System model binding (identity levels,…VOORGESTELPROPOSEDstatus in the registry0CANDIDATE: Two independent implementations pass the test suite; all comments dispositioned
NS-16 UNI application profile (context names such as…VOORGESTELPROPOSEDstatus 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 the standards index 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.

04Bodies 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.

TrackOperationsHekkeWie besluitHow 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

Process explorer · NXS · Process

IETF standards track

8 stappe5 fases3 hekke

NXS · Process

IETF standards track

An Internet-Draft is adopted and last-called by a working group, evaluated by the IESG and published as an RFC; Internet Standard needs interoperable deployment.

  1. 01 Authors

    1. 01Internet-DraftStart · any authorDrafts are posted to the Datatracker and expire unless replaced. An individual draft may be adopted by a working group.
  2. 02 Working group

    1. 03WG adoptionGate · working group chairsThe chairs call for adoption on the list; the draft becomes a working-group document.
    2. 05WG last callGate · working groupThe working group reviews the draft once more before it goes to the area director.
  3. 03 IESG

    1. 02IETF last callGate · the IETF communityThe whole community reviews the document; directorate reviews are recorded in the Datatracker.
    2. 04IESG evaluationDecision · the Internet Engineering Steering GroupArea directors ballot; the document is approved for publication or returned to the working group.
  4. 04 RFC Editor

    1. 06RFC EditorStep · the RFC Production CenterThe RFC Editor edits for clarity and consistency; authors and the area director approve before publication.
    2. 07RFC, Proposed StandardRecord · RFC EditorThe RFC is immutable; errata are recorded separately.
  5. 05 Maturity

    1. 08Internet StandardOutcome · the IESG, on a requestUnder RFC 6410 the track has two maturity levels; advancement is a separate IESG decision.

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 IETFAn outline of how the work is designed to run; it does not report the status of any decision or record.

The operations, as a table
Process · The IETF standards track8 operations
StepPhaseOperationWhoDecision ruleRecord
01AuthorsInternet-Draft (start). Drafts are posted to the Datatracker and expire unless replaced. An individual draft may be adopted by a working group.any authoranyone may post; a draft is a work in progress and expiresan Internet-Draft, expiring after six months
02WerkgroepWG adoption (gate). The chairs call for adoption on the list; the draft becomes a working-group document.working group chairsrough consensus judged by the chairsa working-group draft
03WerkgroepWG last call (gate). The working group reviews the draft once more before it goes to the area director.working grouprough consensus; open issues resolved on the listlast-call comments on the list
04IESGIETF last call (gate). The whole community reviews the document; directorate reviews are recorded in the Datatracker.the IETF communitytwo weeks for a working-group document, four for an individual submissionlast-call announcement and comments
05IESGIESG evaluation (decision). Area directors ballot; the document is approved for publication or returned to the working group.the Internet Engineering Steering Groupthe IESG approves, with DISCUSS positions resolveda ballot with positions
06RFC EditorRFC Editor (step). The RFC Editor edits for clarity and consistency; authors and the area director approve before publication.the RFC Production Centereditorial changes only; authors approve the final textAUTH48 state, then the RFC
07RFC EditorRFC, Proposed Standard (record). The RFC is immutable; errata are recorded separately.RFC Editora Proposed Standard is a stable specification that has resolved known design choicesthe RFC with its number
08MaturityInternet Standard (end). Under RFC 6410 the track has two maturity levels; advancement is a separate IESG decision.the IESG, on a requestinteroperable implementations and successful deployment, no errata of substancean STD number

Table.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 table shows the process as specified; it does not report the status of any standard, proposal or record. 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.

05Last 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.
06Systematic 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.

07Who 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.

08The proposal lifecycle

The proposal lifecycle

StatusMeaningRecord
OPENA proposal is filed as an artefact with a UNI (nexus-proposal.v1.json), naming the target standard, section or registry path, the rationale, the changes (with a change 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
AANVAARThe 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 artefact (NS-1) and is cited (NS-2); no decision is taken in private channels.

09Editors 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.

10Versioning

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

11Licensing 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.

12Rules

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.
13Where

Submission of proposals

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

14Vrae

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.
VerslaeDra by

Dra bewyse vanaf hierdie bladsy by.

Reports is die Konsortium se kwartaallikse publikasie. Wat jy oor hierdie onderwerp weet, kan bewyse, 'n saak of 'n korreksie in die volgende uitgawe word, aan jou toegeskryf en onder CC BY 4.0 gepubliseer waar dit jou eie werk is.

Nexus Standards
Standaarde

Neem deel aan die standaarde.

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 en gebruik. Die Nexus Standards is voorgestelde standaarde wat deur 'n oop proses onder NS-13 ontwikkel en vir vrywillige gebruik gepubliseer word; hulle maak nie sertifisering, akkreditasie of regulatoriese goedkeuring uit nie, en aanvaarding bly 'n besluit van die Wêreldwye Standaarderaad en, in elke land, van sy Nasionale Standaarderaad. 'n UNI (Unique Nexus Identifier) identifiseer 'n artefak; dit sertifiseer dit nie. Name van standaardliggame en hul standaarde behoort aan hul rentmeesters en word slegs gebruik om die dokumente te identifiseer; geen teks van 'n eksterne standaard word hier gereproduseer nie. Nexus Standards is nie geaffilieer met, onderskryf deur of gesertifiseer deur enige standaardliggaam wat hier genoem word nie.

Lisensies: CC BY 4.0 vir standaardteks, registers, skemas en data; Apache-2.0 vir verwysingskode. Eksterne standaarde word volgens naam, nommer en skakel onder hul eie lisensies aangehaal. Derdeparty-data, -biblioteke en -lettertipes behou hul eie lisensies: sien Kennisgewings van derde partye.