Standardekê pêş bixe
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).
- Step 1, OPEN: Proposal filed.
- Gava 2,
IN_REVIEW: Comments disposed. - Gava 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.
The process.
Process explorer · NXS · Process
Nexus development track (NS-13)
10 steps·5 stages·3 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.
01 Open area
- 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.
02 Working group
- 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.
- 03Working groupStep · chairs from two organisationsThe charter is public, with scope, exclusions, deliverables, schedule and decision rule. Drafts, issues and comments are public.
- 05Community draftRecord · working group editorsDrafts, issues and comment dispositions are public, each with a UNI. Chairs record each objection with its disposition.
03 Giştî
- 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.
- 06ProposedRecord · working groupThe standard is proposed and available for voluntary use by implementers ahead of adoption.
04 Implementation
- 07Two implementationsGate · two independent implementersImplementers run the Apache-2.0 test suite and publish results by reference. The group collects final specification agreements.
- 08CandidateRecord · working groupThe implementation report names the implementations, the suite version and the instant of each run.
05 Global Standards Council
- 09AdoptedDecision · the Global Standards Council (GSC)A permanent, dated edition. Errata stay open, and systematic review takes place every three years.
- 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
| Gav | Qonax | Xebitandin | Kî | Decision rule | Tomar |
|---|---|---|---|---|---|
| 01 | Deverê veke | Open 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 registry | an area is open when the registry lists it and no working group has been chartered | programme page with a call for participation |
| 02 | Koma xebatê | Working 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 organisations | consensus with recorded dissent; two co-chairs from different organisations | public charter |
| 03 | Koma xebatê | Community 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 editors | every normative statement gets an NS-10 clause; every draft carries a UNI | drafts with UNIs |
| 04 | Koma xebatê | Horizontal 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 groups | accessibility, internationalisation, privacy, security and accuracy of claims, reviewed before last call | review findings on record |
| 05 | Giştî | Public 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 recorded | at least thirty days (fourteen for errata, ninety for a new standard); each comment answered in writing | comments and dispositions |
| 06 | Giştî | Proposed (record). The standard is proposed and available for voluntary use by implementers ahead of adoption. | working group | entered when last call has closed and every comment has a disposition | proposed edition |
| 07 | Bicihanîn | Two 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 implementers | two independent implementations pass the open test suite; the results serve as implementation evidence | test results as evidence |
| 08 | Bicihanîn | Candidate (record). The implementation report names the implementations, the suite version and the instant of each run. | working group | entered when the implementation report is published | implementation report |
| 09 | Global Standards Council | Adopted (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 call | dated edition with a decision reference |
| 10 | Global Standards Council | Later edition or withdrawal (end). The record is retained and points to its successor. Earlier editions remain unchanged. | a later edition or a withdrawal decision | identifiers 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.
- Gav
- 5
- NS-13 lifecycle
- Pêşniyarkirî
- 15
- foundation standards
- Vekirî
- 349
- for proposals
- Pejirandî
- 0
- by the Council
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.
- Entry condition
- Qada ku di tomargehê de navê wê hatiye
- What exists
- A programme page inviting contributions and a working-group charter template
- Rêgez
- No draft text yet; a working group may be chartered under NS-13.
- Entry condition
- Komeke xebatê ya bi peymanname bi serok, berfirehî, derxistin, berhem, rîtma civînan û qaîdeya biryarê
- What exists
- Drafts developed in the open, with issues tracked publicly; each draft carries a UNI (Unique Nexus Identifier)
- Rêgez
- Decisions by consensus with dissent recorded; the chairs record each objection and its disposition.
- Entry condition
- Working-group consensus recorded; the four horizontal reviews completed; crosswalk entries complete with source links; machine-readable clauses (NS-10) for each normative statement; a conformance test suite
- What exists
- Public last call of at least thirty days, with comments dispositioned in the open
- Rêgez
- Horizontal reviews cover accessibility, internationalisation and translation, privacy and data protection, and security.
- Entry condition
- Du sepandinên serbixwe ji koma ceribandinê derbas dibin; li ser hemû şîroveyan biryar hatiye dayîn
- What exists
- Implementation report published
- Rêgez
- Test results constitute implementation evidence.
- Entry condition
- Pejirandin ji aliyê Encûmena Cîhanî ya Standardan ve di bin GOVERNANCE.md de tê tomarkirin, bi referansê di pêşgotinê de jêgirtî
- What exists
- Permanent edition with a dated edition identifier; errata process open
- Rêgez
- Systematic review every three years to confirm, revise or withdraw. Errata are additive and do not change normative meaning.
- Entry condition
- Weşaneke paşê an biryareke vekişandinê
- What exists
- The record is retained, with a forward reference to the later edition
- Rêgez
- Identifiers are neither deleted nor reused (NS1-R3).
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.
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.
Process explorer · NXS · Process
Nexus development track (NS-13)
10 steps·5 stages·3 gates
NXS · Process
Nexus development track (NS-13)
Çerxa jiyanê ya standardê · Rêça NS-13 · Kanalên beşdariyê · Rêça IETF · Rêça W3C · Rêça OGC · Rêça OASIS · Qonaxên ISO û IEC · Lihevbûn · Çerxa jiyanê ya tomarê · Rêkirin · Çavdêrî.
A chartered group drafts in public, reviews and last call precede proposal, two implementations precede candidacy, and the Global Standards Council records adoption.
01 Open area
- 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.
02 Working group
- 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.
- 03Working groupStep · chairs from two organisationsThe charter is public, with scope, exclusions, deliverables, schedule and decision rule. Drafts, issues and comments are public.
- 05Community draftRecord · working group editorsDrafts, issues and comment dispositions are public, each with a UNI. Chairs record each objection with its disposition.
03 Giştî
- 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.
- 06ProposedRecord · working groupThe standard is proposed and available for voluntary use by implementers ahead of adoption.
04 Implementation
- 07Two implementationsGate · two independent implementersImplementers run the Apache-2.0 test suite and publish results by reference. The group collects final specification agreements.
- 08CandidateRecord · working groupThe implementation report names the implementations, the suite version and the instant of each run.
05 Global Standards Council
- 09AdoptedDecision · the Global Standards Council (GSC)A permanent, dated edition. Errata stay open, and systematic review takes place every three years.
- 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
| Gav | Qonax | Xebitandin | Kî | Decision rule | Tomar |
|---|---|---|---|---|---|
| 01 | Deverê veke | Open 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 registry | an area is open when the registry lists it and no working group has been chartered | programme page with a call for participation |
| 02 | Koma xebatê | Working 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 organisations | consensus with recorded dissent; two co-chairs from different organisations | public charter |
| 03 | Koma xebatê | Community 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 editors | every normative statement gets an NS-10 clause; every draft carries a UNI | drafts with UNIs |
| 04 | Koma xebatê | Horizontal 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 groups | accessibility, internationalisation, privacy, security and accuracy of claims, reviewed before last call | review findings on record |
| 05 | Giştî | Public 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 recorded | at least thirty days (fourteen for errata, ninety for a new standard); each comment answered in writing | comments and dispositions |
| 06 | Giştî | Proposed (record). The standard is proposed and available for voluntary use by implementers ahead of adoption. | working group | entered when last call has closed and every comment has a disposition | proposed edition |
| 07 | Bicihanîn | Two 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 implementers | two independent implementations pass the open test suite; the results serve as implementation evidence | test results as evidence |
| 08 | Bicihanîn | Candidate (record). The implementation report names the implementations, the suite version and the instant of each run. | working group | entered when the implementation report is published | implementation report |
| 09 | Global Standards Council | Adopted (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 call | dated edition with a decision reference |
| 10 | Global Standards Council | Later edition or withdrawal (end). The record is retained and points to its successor. Earlier editions remain unchanged. | a later edition or a withdrawal decision | identifiers 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.
- OPEN2
- PÊŞNÛSA CIVAKÊ0
- PÊŞNIYARKIRÎ17
- BERENDAM0
- PEJIRANDÎ0
- GUHERTÎ an PAŞDEKIŞANDÎ0
Stages are derived from the status recorded in the registry.
| Standard | Rewş | Stage on the track | Rêgez | Next stage |
|---|---|---|---|---|
| NS-0 Destûr û prensîb | PÊŞNIYARKIRÎ | PROPOSEDstatus in the registry | 12 | CANDIDATE: Two independent implementations pass the test suite; all comments dispositioned |
| NS-1 The UNI and the artefact catalogue (grammar… | PÊŞNIYARKIRÎ | PROPOSEDstatus in the registry | 10 | CANDIDATE: Two independent implementations pass the test suite; all comments dispositioned |
| NS-2 Formata jêgirtin û navlêkirinê ji bo UNIyan | PÊŞNIYARKIRÎ | PROPOSEDstatus in the registry | 5 | CANDIDATE: Two independent implementations pass the test suite; all comments dispositioned |
| NS-3 Risk record UNIs (grammar, legacy crosswalk,… | PÊŞNIYARKIRÎ | PROPOSEDstatus in the registry | 0 | CANDIDATE: Two independent implementations pass the test suite; all comments dispositioned |
| NS-3b Dataset and product metadata profile (STAC,… | PÊŞNIYARKIRÎ | PROPOSEDstatus in the registry | 0 | CANDIDATE: Two independent implementations pass the test suite; all comments dispositioned |
| NS-4 Structure and drafting of Nexus Standards and… | PÊŞNIYARKIRÎ | PROPOSEDstatus in the registry | 0 | CANDIDATE: Two independent implementations pass the test suite; all comments dispositioned |
| NS-5 Figure, map and visualisation standard (with… | PÊŞNIYARKIRÎ | PROPOSEDstatus in the registry | 5 | CANDIDATE: Two independent implementations pass the test suite; all comments dispositioned |
| NS-6 Surface wiring (API header, panel provenance,… | SPECIFIED | PROPOSED (in NS-1)specified within NS-1; follows its stage | 0 | CANDIDATE: Two independent implementations pass the test suite; all comments dispositioned |
| NS-7 Rûpelên daketinê yên çareserker, etîketên meta yên rûpelê, nexşeya malperê | SPECIFIED | PROPOSED (in NS-1)specified within NS-1; follows its stage | 0 | CANDIDATE: Two independent implementations pass the test suite; all comments dispositioned |
| NS-8 Zenodo publishing workflow with legal gate,… | OPEN | OPENstatus in the registry | 0 | COMMUNITY DRAFT: A chartered working group with chairs, scope, exclusions, deliverables,… |
| NS-9 Contextual UNIs (deployments, instances,… | PÊŞNIYARKIRÎ | PROPOSEDstatus in the registry | 5 | CANDIDATE: Two independent implementations pass the test suite; all comments dispositioned |
| NS-10 Policies and clauses (machine-readable… | PÊŞNIYARKIRÎ | PROPOSEDstatus in the registry | 7 | CANDIDATE: Two independent implementations pass the test suite; all comments dispositioned |
| NS-11 Verification and monitoring (evidence,… | PÊŞNIYARKIRÎ | PROPOSEDstatus in the registry | 6 | CANDIDATE: Two independent implementations pass the test suite; all comments dispositioned |
| NS-12 Software, model and AI/ML artefacts (supply… | PÊŞNIYARKIRÎ | PROPOSEDstatus in the registry | 4 | CANDIDATE: Two independent implementations pass the test suite; all comments dispositioned |
| NS-13 Standards development process (open proposals,… | PÊŞNIYARKIRÎ | PROPOSEDstatus in the registry | 5 | CANDIDATE: Two independent implementations pass the test suite; all comments dispositioned |
| NS-14 Lihevhatin û nexşeya li standardên derveyî | PÊŞNIYARKIRÎ | PROPOSEDstatus in the registry | 5 | CANDIDATE: Two independent implementations pass the test suite; all comments dispositioned |
| NS-15 System model binding (identity levels,… | PÊŞNIYARKIRÎ | PROPOSEDstatus in the registry | 0 | CANDIDATE: Two independent implementations pass the test suite; all comments dispositioned |
| NS-16 UNI application profile (context names such as… | PÊŞNIYARKIRÎ | PROPOSEDstatus in the registry | 0 | CANDIDATE: Two independent implementations pass the test suite; all comments dispositioned |
| NRS Nexus Risk Standards: the systemic catalogue… | OPEN | OPENstatus in the registry | 0 | COMMUNITY 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.
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.
| Şopandin | Xebitandin | Derî | Kî biryarê dide | How the public takes part | Process document |
|---|---|---|---|---|---|
| Nexus Standards | 10 | Horizontal reviews, Public last call, Two implementations | the Global Standards Council (GSC), by a recorded decision | a public last call of at least thirty days; any person may comment, with identity recorded | NS-13: development process |
| IETF | 8 | WG adoption, WG last call, IETF last call | the IESG approves; the RFC Editor publishes | IETF last call: the whole community, two or four weeks; working groups are open to anyone | RFC 2026, The Internet Standards Process,… |
| W3C | 8 | AC review, Candidate Recommendation | W3C, after Advisory Committee review | wide review of public drafts; comments in the group’s public tracker | W3C Process Document |
| OASIS | 8 | Public review, Statements of use | OASIS organisational members, by ballot | public review through the comment list; thirty days for the first review | OASIS Technical Committee Process |
| OGC | 8 | OAB review, Public comment | OGC voting members, by Technical Committee vote | a public comment period announced by OGC | OGC Technical Committee Policies and… |
| ISO û IEC | 7 | Committee draft, Enquiry draft, Final draft | national bodies, by ballot at the enquiry and approval stages | through the national member bodies, which circulate the enquiry draft | ISO/IEC Directives, Part 1 |
Process explorer · NXS · Process
IETF standards track
8 gav·5 qonax·3 derî
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.
01 Authors
- 01Internet-DraftStart · any authorDrafts are posted to the Datatracker and expire unless replaced. An individual draft may be adopted by a working group.
02 Working group
- 03WG adoptionGate · working group chairsThe chairs call for adoption on the list; the draft becomes a working-group document.
- 05WG last callGate · working groupThe working group reviews the draft once more before it goes to the area director.
03 IESG
- 02IETF last callGate · the IETF communityThe whole community reviews the document; directorate reviews are recorded in the Datatracker.
- 04IESG evaluationDecision · the Internet Engineering Steering GroupArea directors ballot; the document is approved for publication or returned to the working group.
04 RFC Editor
- 06RFC EditorStep · the RFC Production CenterThe RFC Editor edits for clarity and consistency; authors and the area director approve before publication.
- 07RFC, Proposed StandardRecord · RFC EditorThe RFC is immutable; errata are recorded separately.
05 Maturity
- 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
| Gav | Qonax | Xebitandin | Kî | Decision rule | Tomar |
|---|---|---|---|---|---|
| 01 | Nivîskar | Internet-Draft (start). Drafts are posted to the Datatracker and expire unless replaced. An individual draft may be adopted by a working group. | any author | anyone may post; a draft is a work in progress and expires | an Internet-Draft, expiring after six months |
| 02 | Koma xebatê | WG adoption (gate). The chairs call for adoption on the list; the draft becomes a working-group document. | working group chairs | rough consensus judged by the chairs | a working-group draft |
| 03 | Koma xebatê | WG last call (gate). The working group reviews the draft once more before it goes to the area director. | working group | rough consensus; open issues resolved on the list | last-call comments on the list |
| 04 | IESG | IETF last call (gate). The whole community reviews the document; directorate reviews are recorded in the Datatracker. | the IETF community | two weeks for a working-group document, four for an individual submission | last-call announcement and comments |
| 05 | IESG | IESG evaluation (decision). Area directors ballot; the document is approved for publication or returned to the working group. | the Internet Engineering Steering Group | the IESG approves, with DISCUSS positions resolved | a ballot with positions |
| 06 | RFC Editor | RFC Editor (step). The RFC Editor edits for clarity and consistency; authors and the area director approve before publication. | the RFC Production Center | editorial changes only; authors approve the final text | AUTH48 state, then the RFC |
| 07 | RFC Editor | RFC, Proposed Standard (record). The RFC is immutable; errata are recorded separately. | RFC Editor | a Proposed Standard is a stable specification that has resolved known design choices | the RFC with its number |
| 08 | Gihîştin | Internet Standard (end). Under RFC 6410 the track has two maturity levels; advancement is a separate IESG decision. | the IESG, on a request | interoperable implementations and successful deployment, no errata of substance | an 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.
Process explorer · NXS · Process
W3C Recommendation track
8 steps·3 stages·2 gates
NXS · Process
W3C Recommendation track
A reviewed charter leads to working drafts, a Candidate Recommendation with implementation experience, Advisory Committee review, and a maintained Recommendation.
01 Advisory Committee
- 01CharterDecision · the Advisory Committee, on a W3C proposalMembers review the charter; the group is chartered with its deliverables and the patent policy terms.
- 06AC reviewGate · the Advisory CommitteeMembers review the Proposed Recommendation and may formally object.
02 Working group
- 02FPWDRecord · working groupThe first public draft on the technical-report page; wide review begins.
- 03Working DraftsStep · working group editorsDrafts iterate in the open; the group records issues and their resolution.
- 04Candidate RecommendationGate · working group, with the Director’s or Team’s decisionCandidate Recommendation gathers implementation experience; test suites and reports are published.
03 W3C decision
- 05Proposed RecommendationStep · W3CThe document is sent to the Advisory Committee with the implementation report.
- 07RecommendationOutcome · W3CA W3C Recommendation; patent commitments apply under the Patent Policy.
- 08MaintenanceRecord · working group or maintenance groupRecommendations are maintained; errata and amendments are recorded on the technical-report page.
W3C Process Document · W3C Patent PolicyAn 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
| Gav | Qonax | Xebitandin | Kî | Decision rule | Tomar |
|---|---|---|---|---|---|
| 01 | Advisory Committee | Charter (decision). Members review the charter; the group is chartered with its deliverables and the patent policy terms. | the Advisory Committee, on a W3C proposal | Advisory Committee review of scope, deliverables and patent policy | a chartered working group |
| 02 | Koma xebatê | FPWD (record). The first public draft on the technical-report page; wide review begins. | working group | publication starts the patent exclusion period | First Public Working Draft |
| 03 | Koma xebatê | Working Drafts (step). Drafts iterate in the open; the group records issues and their resolution. | working group editors | consensus of the group; horizontal review (accessibility, internationalisation, privacy, security) | successive drafts with change logs |
| 04 | Koma xebatê | Candidate Recommendation (gate). Candidate Recommendation gathers implementation experience; test suites and reports are published. | working group, with the Director’s or Team’s decision | implementation experience and wide review before advancing | a CR snapshot and an implementation report |
| 05 | W3C decision | Proposed Recommendation (step). The document is sent to the Advisory Committee with the implementation report. | W3C | the group shows it met the CR exit criteria | a PR for Advisory Committee review |
| 06 | Advisory Committee | AC review (gate). Members review the Proposed Recommendation and may formally object. | the Advisory Committee | formal objections handled under the Process | review responses |
| 07 | W3C decision | Recommendation (end). A W3C Recommendation; patent commitments apply under the Patent Policy. | W3C | a W3C decision after Advisory Committee review | the Recommendation |
| 08 | W3C decision | Maintenance (record). Recommendations are maintained; errata and amendments are recorded on the technical-report page. | working group or maintenance group | candidate amendments and errata under the Process | errata, amendments, new editions |
Table.The Advisory Committee reviews a charter; the working group publishes a First Public Working Draft and further drafts; Candidate Recommendation gathers implementation experience; Proposed Recommendation goes to Advisory Committee review; the W3C decision publishes the Recommendation, which is then maintained. The table shows the process as specified; it does not report the status of any standard, proposal or record. Sources: W3C Process Document · W3C Patent Policy.
Process explorer · NXS · Process
OASIS standards track
8 steps·3 stages·2 gates
NXS · Process
OASIS standards track
A technical committee drafts, public review gates the Committee Specification, statements of use make a candidate, and a membership ballot approves the OASIS Standard.
01 Technical Committee
- 01Technical CommitteeStart · OASIS members, under a charterThe committee’s charter and IPR mode are public; membership is through OASIS.
- 03Committee Specification DraftRecord · the technical committeeDrafts are numbered and public; working drafts precede them.
- 04Committee SpecificationDecision · the technical committeeThe specification is stable at this stage; implementers may build on it.
02 Public review
- 02Public reviewGate · anyone, through the comment listComments arrive on the comment list and are dispositioned by the committee.
- 05Statements of useGate · implementersOrganisations state that they have used the specification; the statements are public.
03 OASIS membership
- 06Candidate OASIS StandardRecord · the technical committeeA sixty-day public review of the candidate precedes the ballot.
- 07Membership ballotDecision · OASIS organisational membersThe ballot is a formal vote of the OASIS membership.
- 08OASIS StandardOutcome · OASISThe OASIS Standard is published; CAP 1.2 followed this path and was later published as an ITU-T Recommendation (X.1303 bis).
OASIS Technical Committee Process · OASIS IPR PolicyAn 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
| Gav | Qonax | Xebitandin | Kî | Decision rule | Tomar |
|---|---|---|---|---|---|
| 01 | Technical Committee | Technical Committee (start). The committee’s charter and IPR mode are public; membership is through OASIS. | OASIS members, under a charter | formed under the TC Process with a declared IPR mode | a technical committee with its IPR mode |
| 02 | Technical Committee | Committee Specification Draft (record). Drafts are numbered and public; working drafts precede them. | the technical committee | approved by a committee vote | a numbered draft |
| 03 | Public review | Public review (gate). Comments arrive on the comment list and are dispositioned by the committee. | anyone, through the comment list | a first review of thirty days; later reviews fifteen days on changes | comments and their dispositions |
| 04 | Technical Committee | Committee Specification (decision). The specification is stable at this stage; implementers may build on it. | the technical committee | a Special Majority vote after public review | the Committee Specification |
| 05 | Public review | Statements of use (gate). Organisations state that they have used the specification; the statements are public. | implementers | three statements of use for a Candidate OASIS Standard | three statements of use |
| 06 | OASIS membership | Candidate OASIS Standard (record). A sixty-day public review of the candidate precedes the ballot. | the technical committee | entry when statements of use are collected | the candidate with its statements of use |
| 07 | OASIS membership | Membership ballot (decision). The ballot is a formal vote of the OASIS membership. | OASIS organisational members | approval by the membership as the TC Process states | the ballot result |
| 08 | OASIS membership | OASIS Standard (end). The OASIS Standard is published; CAP 1.2 followed this path and was later published as an ITU-T Recommendation (X.1303 bis). | OASIS | published after the ballot; may be submitted to de jure bodies | the OASIS Standard |
Table.A technical committee produces a Committee Specification Draft; a public review gates the Committee Specification; with statements of use the specification becomes a Candidate OASIS Standard; a membership ballot approves it as an OASIS Standard, which may then be submitted to other bodies. The table shows the process as specified; it does not report the status of any standard, proposal or record. Sources: OASIS Technical Committee Process · OASIS IPR Policy.
Process explorer · NXS · Process
OGC standards track
8 steps·3 stages·2 gates
NXS · Process
OGC standards track
A chartered working group drafts, the Architecture Board reviews, public comment follows, and the Technical Committee votes; community standards take a shorter path.
01 Standards working group
- 01SWG charterStart · OGC members proposing the groupThe charter states scope and deliverables; the group works under the Technical Committee policies.
- 02Community submissionStart · a community, outside an OGC working groupThe STAC community’s specification is published by OGC as a Community Standard through this path.
- 05DraftRecord · the working groupThe group drafts the candidate standard and its conformance classes.
02 Technical Committee
- 03OAB reviewGate · the OGC Architecture BoardThe Architecture Board checks consistency with the OGC baseline.
- 04Public commentGate · anyoneComments received are dispositioned by the working group before the vote.
- 06TC voteDecision · OGC voting membersThe Technical Committee votes on the candidate standard or the community standard.
03 OGC publication
- 07PublicationOutcome · OGC staffThe standard is published with a document number on the OGC standards page.
- 08Community standardRecord · OGCThe community keeps maintaining the specification; OGC publishes the snapshot it approved.
OGC Technical Committee Policies and Procedures · OGC standardsAn 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
| Gav | Qonax | Xebitandin | Kî | Decision rule | Tomar |
|---|---|---|---|---|---|
| 01 | Standards working group | SWG charter (start). The charter states scope and deliverables; the group works under the Technical Committee policies. | OGC members proposing the group | charter approved by the Technical Committee | a chartered standards working group |
| 02 | Standards working group | Draft (record). The group drafts the candidate standard and its conformance classes. | the working group | consensus of the working group | a candidate standard |
| 03 | Standards working group | Community submission (start). The STAC community’s specification is published by OGC as a Community Standard through this path. | a community, outside an OGC working group | a community standard is submitted as is, with its usage justification | a submission with a justification |
| 04 | Technical Committee | OAB review (gate). The Architecture Board checks consistency with the OGC baseline. | the OGC Architecture Board | architecture and consistency review before public comment | review comments |
| 05 | Technical Committee | Public comment (gate). Comments received are dispositioned by the working group before the vote. | her kes | a public comment period announced by OGC | comments and dispositions |
| 06 | Technical Committee | TC vote (decision). The Technical Committee votes on the candidate standard or the community standard. | OGC voting members | approval by the Technical Committee electronic vote | the vote result |
| 07 | OGC publication | Publication (end). The standard is published with a document number on the OGC standards page. | Karmendên OGC | publication after the vote and the Planning Committee’s confirmation | the published standard with its document number |
| 08 | OGC publication | Community standard (record). The community keeps maintaining the specification; OGC publishes the snapshot it approved. | OGC | published as the community maintains it; the body does not develop it | a Community Standard |
Table.A standards working group is chartered and drafts; the Architecture Board reviews; the draft goes to public comment; the Technical Committee votes and OGC publishes. A community standard follows a shorter path: a submission with a justification, a vote and publication without an OGC working group. The table shows the process as specified; it does not report the status of any standard, proposal or record. Sources: OGC Technical Committee Policies and Procedures · OGC standards.
Process explorer · NXS · Process
ISO and IEC project stages
7 gav·4 qonax·3 derî
NXS · Process
ISO and IEC project stages
National bodies ballot a new work item, then committee, enquiry and final drafts in turn, before publication and systematic review; stage names cite the Directives.
01 Technical committee
- 01New work item proposalStart · a national body or liaison, to the committeeA proposal is balloted; it needs enough participating members committing to take part.
- 07Committee draftGate · the technical committeeThe committee draft is circulated for comment and consensus is sought.
02 Working group
- 06Working draftRecord · experts in the working groupExperts nominated by national bodies prepare the technical content.
03 National bodies
- 02Enquiry draftGate · all national bodiesThe draft international standard is circulated to every national body for ballot and comment.
- 03Final draftGate · all national bodiesThe final draft is balloted for approval.
04 Publication
- 04International StandardDecision · the central secretariatThe standard is published; its text is the body’s and is sold or licensed by the body and its national members.
- 05Systematic reviewOutcome · the technical committee and national bodiesEvery standard is reviewed periodically and confirmed, revised or withdrawn.
ISO/IEC Directives, Part 1 · ISO stages and resources for standards developmentAn 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
| Gav | Qonax | Xebitandin | Kî | Decision rule | Tomar |
|---|---|---|---|---|---|
| 01 | Technical committee | New work item proposal (start). A proposal is balloted; it needs enough participating members committing to take part. | a national body or liaison, to the committee | approval by the participating members’ ballot | an approved new work item |
| 02 | Koma xebatê | Working draft (record). Experts nominated by national bodies prepare the technical content. | experts in the working group | the working group prepares the draft | working drafts |
| 03 | Technical committee | Committee draft (gate). The committee draft is circulated for comment and consensus is sought. | the technical committee | committee consensus on the draft | committee comments and their resolution |
| 04 | National bodies | Enquiry draft (gate). The draft international standard is circulated to every national body for ballot and comment. | all national bodies | approval by the ballot rule the Directives state | the enquiry ballot result |
| 05 | National bodies | Final draft (gate). The final draft is balloted for approval. | all national bodies | approval by the ballot rule the Directives state; no technical comments at this stage | the approval ballot result |
| 06 | Weşan | International Standard (decision). The standard is published; its text is the body’s and is sold or licensed by the body and its national members. | the central secretariat | published after approval | the published standard |
| 07 | Weşan | Systematic review (end). Every standard is reviewed periodically and confirmed, revised or withdrawn. | the technical committee and national bodies | review within the period the Directives set | confirm, revise or withdraw |
Table.A new work item proposal is balloted by the national bodies; a working group prepares working drafts; the committee draft, the enquiry draft and the final draft are balloted in turn; the standard is published and reviewed systematically. Stage names are cited from the Directives. The table shows the process as specified; it does not report the status of any standard, proposal or record. Sources: ISO/IEC Directives, Part 1 · ISO stages and resources for standards development.
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.
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.
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.
The proposal lifecycle
| Rewş | Wate | Tomar |
|---|---|---|
| OPEN | A 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_REVIEW | Comments are collected in the open; each comment receives a disposition (accepted, rejected, deferred, open) with a reason. | şîrove |
LAST_CALL | A 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 / WITHDRAWN | The editors’ decision, with reasons, is recorded. | biryar |
| PEJIRANDÎ | The 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.
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.
Guhertokirin
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 an 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).
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.
Rêgez
| Rêgez | Nivîs |
|---|---|
| NS13-R1 | Every change to a standard, registry, clause or policy shall enter through a proposal with a UNI. |
| NS13-R2 | Participation 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-R3 | Last call shall be announced to every stakeholder group listed on the proposal; objections shall be dispositioned before acceptance. |
| NS13-R4 | Editors shall not adopt; authority decisions shall be recorded by reference. |
| NS13-R5 | Versions shall be semantic; registries shall be append-only; existing UNIs shall not be invalidated. |
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.
Pirs û bersiv.
Who may take part?
How long is last call?
Ji vê rûpelê delîl bidin.
Reports weşana sê mehane ya Konsorsiyûmê ye. Tiştê ku tu li ser vê mijarê dizanî dikare di çapa pêş de bibe delîl, dosya an rastkirin, bi navê te û di bin CC BY 4.0 de weşandî li cihê ku karê te bi xwe be.
- E-nameDergeha GW-STDJi vê rûpelê bişîneDelîl, rastkirin, doz, rêbaz, nirxandin, werger an têketina profîlê. Bi etîketa vê rûpelê digihîje, da ku edîtorê xwedî wê bistîne.
- ZenodoOpen depositDeposit it and submit to the communityPublish your own record on Zenodo with your ORCID iD, then submit it to the Reports community there. Curators review it; the DOI stays yours.
- ReportsNexus StandardsSee every way to contributeThe contribution types, how each is reviewed, what credit you receive, the licence and what is never accepted.
Tu carî daneyên şexsî, hûrgiliyên binesaza hesas an tiştekî ku mafê we yê parvekirinê tune ne neşînin. Beşdarî berî bikaranînê tê nirxandin; şandina wê nivîskarî an mafên edîtorî nade û sponsorî tu carî encamekê nakire.
Around the standards.
Beşdarî standardan bibe.
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.
Rewş û bikaranîn. Nexus Standards standardên pêşniyarkirî ne ku bi pêvajoyeke vekirî di bin NS-13 de hatine pêşxistin û ji bo bikaranîna dilxwazî hatine weşandin; ew ne belgename, ne akreditasyon û ne pejirandina rêkxistinê ne, û pejirandin biryara Encûmena Standardên Cîhanî û, li her welatî, ya Encûmena Standardên Neteweyî ya wê dimîne. UNI (Unique Nexus Identifier) berhemekê nas dike; wê belgename nake. Navên desteyên standardan û standardên wan aîdî parêzvanên wan in û tenê ji bo naskirina belgeyan têne bikaranîn; tu nivîsa standardeke derve li vir nayê dubarekirin. Nexus Standards bi tu desteya standardan a li vir hatiye binavkirin ve ne girêdayî ye, ji aliyê wê ve nayê piştgirîkirin û belgename nekiriye.
Lîsans: CC BY 4.0 ji bo nivîsa standardan, tomargeh, şema û daneyan; Apache-2.0 ji bo koda referansê. Standardên derve bi nav, hejmar û girêdanê di bin lîsansên xwe de têne jêgirtin. Dane, pirtûkxane û fontên aliyê sêyem lîsansên xwe diparêzin: binêre Agahdariyên aliyê sêyem.