Skip to content
ستانداردبنەماکان و حوکمڕانیبنەماکان
Area · proposed

لێرەوە دەست پێبکە و بەشداری بکە

The entry point for prospective contributors: the scope and limits of the Nexus Standards, which areas are open, how a community takes up an area by chartering a working group, how to submit a proposal or comment and receive a written disposition, and the sign-offs required (OWFa 1.0 for standards text, DCO 1.1 for tooling). It presents the Nexus Standards as an open and developing effort rather than a claim to cover every area. Each artefact of the area carries a UNI (Unique Nexus Identifier).

لێرەوە دەست پێبکە و بەشداری بکە
What this area is built from: the Nexus Standards it applies, the open standards it names and the data and feeds it reads, then the areas its record couples it with (marked).Source: the Nexus Standards registry: the area record.
  • Nexus Standards: NS-1, NS-9.
  • Open standards: CRediT Contributor Roles Taxonomy (ANSI/NISO Z39.104-2022); Citation File Format (CITATION.cff); Web Content Accessibility Guidelines (WCAG) 2.2; Developer Certificate of Origin 1.1.
  • Data and feeds: ORCID public API (contributor identifiers for attribution); OpenAlex works API (finding researchers already publishing in an OPEN area).
  • Couples with: Open areas and calls to build; How a standard is made; Working groups; Licensing and intellectual property.
Nexus Standards
2
NS-1, NS-9
ستانداردە کراوەکان
4
named, never copied
Data and feeds
2
listed for reference
پەیوەستبوونەکان
4
with other areas
UNI
requested · allocation in progress
دۆخ
Proposednot yet in the catalogue
Last reviewed
area profile
ئاماژە بەم پەڕەیە بدە

Nexus Standards (2026). Start here and contribute: area brief, Foundations and Governance programme. Proposed. https://nexustandards.com/foundations/movement-and-contribution/. Last reviewed 17 October 2026.

Download the profile

Files include the credits and the licence statement and are generated in the browser; no data is transmitted. Downloads require JavaScript.

02سنوور

Scope and boundaries

An area of the Foundations and Governance programme (foundations). The area profile sets out 5 matters in scope and 3 matters addressed by other areas.

In scope 5

  • Orientation (purpose, scope and limits) and reading order (NS-0, NS-1)
  • How to propose, comment, review and become an editor
  • Charter template and how a community takes up an open area
  • Contributor sign-offs and code of conduct
  • Attribution of contributors (CRediT roles, ORCID)

Out of scope 3

  • Paid membership tiers or sponsorship packages
  • Recruitment for any organisation’s staff roles
  • Any promise that a contribution will be adopted

Jurisdictions Application in each jurisdiction is a national decision, taken by the National Standards Council (NSC) with the competent national authorities.

03Taking part

How anyone takes part in open standards.

ڕێگاکانی بەشداریکردن

Four ways to take part

فێربە

Compare development processes

The Nexus track and the processes of the IETF, W3C, OASIS, OGC and ISO, each as an interactive diagram. Development processes compared.

دۆزینەوە

کام ستانداردەکان جێبەجێ دەبن

Select a sector, a hazard family, a capability and an artefact type; the registry identifies the relevant standards and states the reason for each. Routing console.

بەشداری بکە

At the standards body and in the Nexus Standards

Each package lists the participation channels of the body and their requirements; outcomes are recorded as public change records. Example package: STAC.

بنیاتنان

Areas open for development

95 areas named in the registry have no working group yet. A working group may be chartered for any of them under NS-13, and National Working Groups may contribute national inputs. All programme areas.

Process documents

Participation rules of the standards bodies

Registry entries for the process documents of the standards bodies, to be read at the source before joining a channel. Membership, patent policy and contributor agreements are determined by each body.

ستانداردلەشوەشانپەیوەندیدەستگەیشتنپشتڕاستکراوە
RFC 2026 The Internet Standards Process – Revision 3 (BCP 9)IETFRFC 2026 (1996) with BCP 9 amendments; draft-ietf-procon-2026bis in progress (2026)citeکراوەپشتڕاستکراوە
W3C Process Document (2025)World Wide Web Consortiumeffective 18 August 2025; Proposed Recommendation phase removedciteکراوەپشتڕاستکراوە
OASIS Technical Committee Process and IPR PolicyOASIS Opencurrent TC Process; IPR Policy adopted 20 January 2005 with later revisionsciteکراوەپشتڕاستکراوە
OGC Technical Committee Policies and ProceduresOpen Geospatial Consortium05-020r29citeکراوەپشتڕاستکراوە
ISO/IEC Directives, Part 1 (procedures) with Consolidated ISO Supplement, and Part 2 (drafting)ISO and IECPart 1 and ISO Supplement edition 2024 (V01/2024); Part 2 edition year UNVERIFIEDciteکراوەپشتڕاستکراوە
RFC 6852 Affirmation of the Modern Paradigm for Standards (OpenStand principles)IAB, IEEE-SA, IETF, Internet Society, W3CInformational RFC (January 2013); affirmation signed 29 August 2012adoptکراوەپشتڕاستکراوە
Regulation (EU) No 1025/2012 on European standardisationEuropean Parliament and Council25 October 2012 (UK retained copy at IP completion day)citeکراوەپشتڕاستکراوە

Packages

Open standard packages

Each package presents the registry entry together with the body’s development process as a diagram, the clause map, the crosswalk, adoption, participation channels, tools and updates. Three packages are published; further packages will follow as the registry is extended.

Outcomes

Outcomes of a contribution

  1. 01

    A registry correction

    A version, year, URL or relation corrected in the external standards register, citing the source.

  2. 02

    A crosswalk entry

    A Nexus clause related to a part of the external document by number (NS-14), without reproducing its text.

  3. 03

    A clause of a standard

    An obligation taken up or profiled by a Nexus Standard, written as an NS-10 clause citing the source.

  4. 04

    A public change record

    Each change is submitted as a proposal under NS-13; the editors decide with written reasons, and the history is retained.

04پرۆسە

The process in operation

A proposal with a UNI (Unique Nexus Identifier) names its target and the stakeholder groups affected; comments are collected in the open and each receives a disposition; a last call is announced to every group listed; the editors decide with written reasons and record the new version; adoption is a decision of the Global Standards Council (GSC), and adoption in a country is a decision of its National Standards Council (NSC). 8 operations in 5 phases, built from the area profile: the rows carry its own data sources, indicators, open standards, couplings and, where listed, hazards, and each operation names the rules it implements (5).

گەڕۆکی پرۆسە · Standards · کۆدکردن و ڕاستکردنەوە

خولی ژیانی ستاندارد

17 هەنگاو6 قۆناغ

Standards · کۆدکردن و ڕاستکردنەوە

خولی ژیانی ستاندارد

دۆزینەوەکانی خول دەبنە پێشنیاری گۆڕانکاری، ئەنجومەنی جیهانیی ستانداردەکان دوای دوایین بانگەوازی گشتی پەسەندیان دەکات، و هەر وڵاتێک بڕیار لەسەر پەسەندکردنی خۆی دەدات.

  1. 01 ئاڕاستەکردنی ئەرکەکان

    1. 01Route missions to standards and profilesStep · Nexus StandardsNexus Standards routes each candidate mission to the standards and profiles that apply.
  2. 02 پرۆفایلەکان و گونجان

    1. 02پرۆفایلی ئەرکەکان پێکبهێنەهەنگاو · Nexus StandardsNexus Standards پرۆفایلی ئەرکەکان پێکدەهێنێت و هەر پەسەندکردنێکی نیشتمانی تۆمار دەکات کە ئەرکەکان پشتی پێدەبەستن.
    2. 03دەرچووەکانی دروستکردن بەراورد بە پڕۆفایلەکان پشتڕاست بکەرەوەهەنگاو · Nexus StandardsNexus Standards دەرچووەکانی دروستکردن بەراورد بە پڕۆفایلە پێکهێنراوەکان پشتڕاست دەکاتەوە و بەڵگەکان تۆمار دەکات.
    3. 04چاودێریی گونجان بکە و بەڵگەی مۆرکراو تۆمار بکەهەنگاو · Nexus Standardsلە ماوەی Action Week دا، Nexus Standards چاودێریی گونجان دەکات و لادانەکان تۆمار دەکات.
  3. 03 پێشنیار و پێداچوونەوە

    1. 05لادان و ڕاستکردنەوەکان دەبنە پێشنیاری گۆڕانکاریهەنگاو · Nexus Standardsلادانەکان دەبنە پێشنیاری گۆڕانکاری، و ڕاستکردنەوەکە وەک گۆڕانێک لە بەڵگەکەدا تۆمار دەکرێت.
    2. 06دۆزینەوەکانی خول دەبنە پێشنیاری گۆڕانکاریهەنگاو · Nexus Standardsدۆزینەوەکانی خولێک دەبنە پێشنیاری گۆڕانکاری: دۆزینەوەکانی میتۆد و ڕاستکردنەوە لە ڕاپۆرتەکان (F06) و بابەتەکانی خشتەی کار لە Nexus…
    3. 07بە ئاشکرا ڕەشنووس بکە و پێیدا بچۆرەوەهەنگاو · لیژنەکان و گرووپەکانی کارلیژنە تەکنیکییەکان و گرووپەکانی کار ستانداردەکان لە پرۆسەی کراوەی NS-13 دا ڕەشنووس دەکەن و پێیاندا دەچنەوە.
    4. 08پێداچوونەوە بەرەو بڕیاری ئەنجومەنهەنگاو · Nexus StandardsNexus Standards پێشنیارەکانی گۆڕانکاری لە ڕێگەی پێداچوونەوەوە بەرەو بڕیاری ئەنجومەن دەبات.
  4. 04 بڕیاری ئەنجومەن

    1. 09بانگەوازی کۆتایی گشتیهەنگاو · ئەنجومەنی جیهانیی ستانداردەکانئەنجومەنی جیهانیی ستانداردەکان دوای بانگەوازێکی کۆتایی نەوەد ڕۆژە بە زۆرینەی دوو لەسەر سێ پەسەند دەکات.
    2. 10پەسەندکردنی جیهانیی ستانداردێکبڕیار · ئەنجومەنی جیهانیی ستانداردەکانئەنجومەنی جیهانیی ستانداردەکان دوای دوایین بانگەوازی گشتی بڕیار لەسەر پەسەندکردنی هەر ستانداردێک دەدات.
  5. 05 بڵاوکردنەوە و ناساندن

    1. 11Assign a UNI and publishStep · Secretariat (GCRI Canada)Nexus Standards assigns UNIs and deposits publications under the publisher’s process.
    2. 12UNI دەناسێنێت و هەرگیز بڕوانامە ناداتتۆمار · Nexus Standardsهەر بابەتێکی ساڵی بەرنامە یەک ناسێنەر هەڵدەگرێت، UNI یەک لەژێر NS-1، بۆ ئەوەی ئاماژەی پێ بکرێت، وەشانبەندی بکرێت و چارەسەر بکرێت.
    3. 13گۆڕانکارییە پەسەندکراوەکانی ساڵەکە بڵاو بکەرەوەهەنگاو · Nexus Standardsلە کاتی نوێکردنەوەدا Nexus Standards گۆڕانکارییە پەسەندکراوەکانی ساڵەکە و دۆخی پەسەندکردنی نیشتمانی بڵاو دەکاتەوە.
  6. 06 پەسەندکردن و جێبەجێکردنی نیشتمانی

    1. 14پەسەندکردنی نیشتمانی لەلایەن ئەنجومەنی نیشتمانیی ستانداردەکانەوەبڕیار · ئەنجومەنی نیشتمانیی ستانداردەکانئەنجومەنی نیشتمانیی ستانداردەکانی هەر وڵاتێک بڕیار لەسەر پەسەندکردنی نیشتمانی دەدات: وەک خۆی پەسەند بکرێت، بە پڕۆفایلێک پەسەند بکرێت (NS-16)، بگونجێنرێت، یان تەنها ئاماژەی پێ بکرێت.
    2. 15ستانداردە پەسەندکراوەکان دەگەنە خول و وەشانەکانهەنگاو · Nexus Standardsهەر ستاندارد یان پرۆفایلێکی پەسەندکراو دەبێتە مۆدیولی خولێک لە Risk Academy (F09)، و ستانداردەکان لە وەشانەکانی Reports دا جێبەجێ دەکرێن (R1).
    3. 16پەسەندکردن بۆ هەر ناوچەیەکی دەسەڵات کۆتاییەستاندارد · ئەنجومەنی نیشتمانیی ستانداردەکانپەسەندکردن بۆ هەر ناوچەیەکی دەسەڵات کۆتاییە، و GSC هیچ ڤیتۆیەکی بەسەر بڕیارێکی نیشتمانیدا نییە. هیچ دەزگایەکی جیهانی ڤیتۆی نییە.
    4. 17تۆمارەکانی پەسەندکردنی نیشتمانیتۆمار · Nexus Standardsپڕۆفایلە پێکهێنراوەکانی ئەرک و تۆمارەکانی پەسەندکردنی نیشتمانی لە قۆناغی ئامادەکردنی ئامادەییدا دەنێردرێن بۆ Foundry (F08).

Nexus Standards · Nexus Standards (institution) · National Standards CouncilAn outline of the designed programme cycle, not a record of operation: no cycle has run and every programme is at service level R0. Every Nexus Standard is at the PROPOSED stage and nexustandards.com governs the text and status of each one. A UNI identifies and never certifies; a validator report is evidence for review, not a conformance claim.

The operations, as a table
Process · the development track: from a proposal to adoption (NS-13)8 operations · 5 phases
هەنگاوقۆناغکارکردنکێDecision ruleتۆمارImplements
01پێشنیارFile a proposal (start). Participation needs no membership fee; decisions are made by the recorded process.any person or organisation, identified by ORCID or ROR, or an agent under a mandateevery change to a standard, registry, clause or policy enters through a proposal with a UNIa proposal (nexus-proposal) with target, rationale, changes and stakeholder groupsNS13-R1, NS13-R2
02پێداچوونەوەOpen review (step). Comments are collected in the open record of the proposal.any participant, with identity recordedparticipation is open and free; identity is recordedcomments in the openNS13-R2
03پێداچوونەوەDispositions (record). Nothing is decided in private channels.the editorsdecisions are reasoned in writinga disposition per comment (accepted, rejected, deferred, open) with a reasonNS13-R2
04Last callLast call (gate). The period is thirty days by default, fourteen for errata and ninety for a new standard.the editorsannounced to every stakeholder group listed; objections are dispositioned before acceptancethe announcement and lastCallEndsAtNS13-R3
05EditorsEditors decide (decision). The decision and its reasons are recorded with the proposal.the editorseditors maintain the text and run the process; they do not adoptaccepted, rejected or withdrawn, with reasonsNS13-R4
06EditorsNew version (record). A major change needs a crosswalk and a migration note.the editorsversions are semantic; registries append-only; existing UNIs are never invalidateda semantic version; registries appendedNS13-R5
07وەرگرتنGSC adoption (decision). Adoption follows the Charter and is recorded as a reference.the Global Standards Council (GSC)authority decisions are recorded referencesthe decision reference that changes the standard’s statusNS13-R4
08وەرگرتنNational adoption (end). The NSC decides for its jurisdiction, engaging competent national authorities through its public-authority liaison; the GSC has no veto over a national decision.the National Standards Council (NSC) of each National Nexus Consortiumnational adoption is a national decision; national law and language prevaila national decision: adopt, adapt or reference, with the national application profileNS13-R4

Table.Operations in walking order; each row names the phase, the operation, its actor, its decision rule, the record it leaves and the rule identifiers it implements. The table shows the process as specified; it does not report the status of any standard, proposal or record. Sources: CRediT Contributor Roles Taxonomy (ANSI/NISO Z39.104-2022) · Citation File Format (CITATION.cff) · NS-13: Standards development process · NS-1: The UNI and the artefact catalogue.

05Standards architecture

Foundation, referenced and implementing layers

The standards architecture of this context, from the foundation standards to the open standards referenced (grouped by type of relation) and the services and data sources that build on them.

The interactive view requires JavaScript; the sections below present the same records.

06کەناڵەکانی بەشداری

From a comment at a standards body to a registry change

Three lanes: the contributor, the standards body and the Nexus Standards. Each operation names the actor, the decision rule and the record it leaves.

Process explorer · NXS · Process

Contributing through a standards body

11 steps3 stages1 gate

NXS · Process

Contributing through a standards body

A contributor joins a body’s channel under its rules, files issues, reviews, proposes and tests, and Nexus Standards cites the outcome through a change proposal.

  1. 01 Contributor

    1. 01Identify the bodyStart · the contributorEach standard package links to the issuing body, its working group or technical committee and its process document.
    2. 02Read IPR and participation rulesStep · the contributorParticipation rules differ by body, from no membership at the IETF to membership at OASIS.
    3. 06Propose textStep · the contributor, in the body’s channelWording goes to the body’s own channel. In Nexus Standards, the obligation becomes a clause (NS-10) citing the source clause.
    4. 07Implement and testExercise · the contributorThe contributor runs the body’s test suite or validator, where the body publishes one.
  2. 02 The standards body

    1. 03Join a channelStep · the body’s working group or committeeMailing lists and their archives, issue trackers and public comment lists are listed per package with what each requires.
    2. 04File an issueRecord · the contributor, in the body’s trackerAn erratum, a question or a proposal becomes an issue in the body’s tracker; the Nexus Standards cite it by link.
    3. 05Public reviewGate · the body, under its processPublic reviews and last calls are the body’s own stages. The monitoring console shows their dates once the body’s feed exists.
    4. 08Implementation reportRecord · the body or the working groupImplementations are listed as submitted, in alphabetical order.
  3. 03 Nexus Standards

    1. 09Cite the outcomeStep · Nexus Standards editorsThe outcome at the body becomes a register entry: a corrected version, a new crosswalk entry or a clause that cites the source.
    2. 10Change proposalRecord · any person, with identity recordedA change proposal is a change request to the canonical repository, with a public proposal record. Editors decide with reasons.
    3. 11Register changeOutcome · editors, with reasons on recordThe register entry is amended and the package page is regenerated from it.

OpenStand principles (RFC 6852) · NS-13: development process · NS-14: crosswalk and conformance claimsAn 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 · from a comment at a standards body to a registry change11 operations
هەنگاوقۆناغکارکردنکێDecision ruleتۆمار
01ContributorIdentify the body (start). Each standard package links to the issuing body, its working group or technical committee and its process document.the contributorthe register names the body and links to its own pagethe body’s page, linked from the package
02ContributorRead IPR and participation rules (step). Participation rules differ: an IETF working group requires no membership; an OASIS technical committee requires membership; W3C groups have community and member forms.the contributormembership, patent policy and contributor agreements are set by the body and read at the sourcethe requirements of the channel
03The standards bodyJoin a channel (step). Mailing lists and their archives, issue trackers and public comment lists are listed per package with what each requires.the body’s working group or committeethe channel belongs to the body and follows its process documenta list subscription, an issue account, a membership
04The standards bodyFile an issue (record). An erratum, a question or a proposal becomes an issue in the body’s tracker; the Nexus Standards cite it by link.the contributor, in the body’s trackeran issue is the body’s record, cited by URLan issue with a stable link
05The standards bodyPublic review (gate). Public reviews and last calls are the body’s own stages. The monitoring console shows their opening and closing dates once the body’s feed is available.the body, under its processthe body decides under its own rules; the Nexus Standards record the public outcomecomment dispositions by the body
06ContributorPropose text (step). Wording is submitted to the body’s own channel. In the Nexus Standards, the same obligation is expressed as a clause (NS-10) that cites the source by clause number.the contributor, in the body’s channeltext is proposed through the body’s own channel; the body’s text remains with the bodya change request, an Internet-Draft or a comment with wording
07ContributorImplement and test (exercise). The contributor runs the body’s test suite or validator, where the body publishes one.the contributora passing run is evidence of implementationa test run with the suite version and time
08The standards bodyImplementation report (record). Implementations are listed as submitted, in alphabetical order.the body or the working grouplisted as the body publishes it, without rankingthe report, linked
09Nexus StandardsCite the outcome (step). The outcome at the body becomes a register entry: a corrected version, a new crosswalk entry or a clause that cites the source.Nexus Standards editorscited by identifier, clause number and URL (NS-14); a recorded relation does not imply equivalencea crosswalk entry or a clause citing the source
10Nexus StandardsChange proposal (record). A change proposal is a change request to the canonical repository, with a proposal record in the public change record. Editors decide with written reasons.any person, with identity recordedevery change is submitted as a change proposal under NS-13a change proposal with a UNI
11Nexus StandardsRegister change (end). The register entry is amended and the package page is regenerated from it.editors, with reasons on recordaccepted, rejected or withdrawn in writing; the history is retainedthe amended register entry and its history

Table.A contributor identifies the standards body, reads its participation and intellectual property rules, joins a channel, files an issue, takes part in the public review, proposes text, and implements and tests; the body publishes the implementation report. The Nexus Standards cite the outcome through a change proposal that becomes a register correction, a crosswalk entry or a clause. The table shows the process as specified; it does not report the status of any standard, proposal or record. Sources: OpenStand principles (RFC 6852) · NS-13: development process · NS-14: crosswalk and conformance claims.

07ستاندارد

ستانداردە جێبەجێبووەکان

The area profile lists 2 Nexus Standards. Each is a proposed standard under development.

  1. 01

    NS-1 · The UNI and the artefact catalogue (grammar v0.2: domain, sector, region and environment segments)

    Status: proposed · 10 requirements stated. Read NS-1.

  2. 02

    NS-9 · Contextual UNIs (deployments, instances, programme instances)

    Status: proposed · 5 requirements stated. Read NS-9.

08مۆدێلی سیستەم

How a shock travels through this system

A system model of this area built from the registry: 5 systems, 4 sectors, 8 controls, 2 feeds, 1 indicator. Select the components to include, choose an initiating hazard and run the scenario. Stress propagates through the hazard relations of the Nexus Hazard Standard (NHS-1), the exposure of each system, the recorded couplings and the sectors that carry the loss; adopted standards dampen transmission and live data sources support detection. All parameters are stated assumptions that the reader can adjust; results are illustrative scenario outputs for exercises and training, not forecasts or risk assessments.

کۆنترۆڵەکان

  • NS-1UNI و کەتەلۆگی بەرهەمەکان (ڕێزمانی v0.2: بەشەکانی بوار، کەرت، هەرێم و ژینگە)
  • NS-9 UNIی ناوەڕۆکی (دامەزراندنەکان، نموونەکان، نموونەکانی پڕۆگرام)
  • NRS-E3 Academy: لێهاتوویی، فێربوون بە کردەوە و بڕوانامەکان
  • NRS-H29 Hazard family: Air pollution episodes (NHS-1 poll.air-quality)
  • NRS-H88 خێزانی مەترسیدەر: زیانی ژێرخانی بنی دەریا (NHS-1 infra.seabed)
  • NRS-H107 خێزانی مەترسیدەر: چڕبوونەوە و یەکڕەنگیی ژێرخانی دیجیتاڵ (NHS-1 tech.digital-concentration)
  • NRS-I4 بەڵگەی توێژینەوە، دووبارەکردنەوەی ئەنجام و زانستی کراوە
  • NRS-H16 خێزانی مەترسیدەر: سەهۆڵی سەرئاو (NHS-1 cryo.floating-ice)

چاودێری

  • ORCID public API (contributor identifiers for attribution) (listed for reference)
  • OpenAlex works API (finding researchers already publishing in an OPEN area) (listed for reference)
  • Proportion of youth and adults with information and communications technology (ICT) skills, by type of skill
09گرووپی کار

Working group charter

A proposed charter for this area, open to institutions and experts.

سنوور

Maintain onboarding content, the charter template, the contributor guide and the code of conduct.

Institutions and experts are invited to charter this working group under NS-13 by filing a public change record. National Working Groups (NWGs) contribute national inputs and field exercises through their National Nexus Consortium (NNC).

Deliverables · 3
  1. Contributor guide with sign-off steps
  2. Charter template and worked example of an area taken up by a community
  3. Code of conduct with an enforcement procedure
Liaison targets · 2
  • Research Data Alliance (information exchange on community onboarding sought) liaison sought
  • W3C Community Groups (information exchange sought) liaison sought
10پەیوەستبوونە سیستەمییەکان

پەیوەستبوونە سیستەمییەکان

4 couplings link this area to other areas and programmes, each with the mechanism of the link.

  1. Open areas and calls to buildCommunities, Learning and ContributionThe open-areas list in the Communities, Learning and Contribution programme is the inventory to which this area directs contributors; each area listed there carries the charter template maintained here.
  2. How a standard is madeFoundations and GovernanceA contribution enters the track as an issue or proposal with a UNI and moves through the stages; this area explains the path and the standards track applies it.
  3. Working groupsCommunities, Learning and ContributionChartering a working group moves an area from the Open stage to the Community Draft stage; the working-group index lists each charter.
  4. Licensing and intellectual propertyFoundations and GovernanceContributors meet the OWFa and DCO requirements before their first contribution is accepted, so IPR is settled at the outset.
13Research questions

Open research questions

3 questions identified as priorities for the working group.

  1. How to keep the first contribution simple enough for practitioners in low-bandwidth settings while still collecting OWFa and DCO sign-offs.
  2. How to credit non-code, non-text work such as data curation, translation and review fairly in CRediT terms.
  3. How to sustain volunteer editors without creating paid roles that tilt influence.
14ئامادەباشی

Evidence, recognition and capital pathways

What each institution of the ecosystem draws from this area: The Global Centre for Risk and Innovation (GCRI Canada), as Secretariat, for evidence; The Global Risks Forum (GRF) for recognition; and The Global Risks Alliance (GRA) for capital.

Evidence pathway

GCRI Canada

GCRI Canada decides under its own rules how contributions relate to its evidence work; contributing implies no acceptance by it.

Read the evidence pathway

ڕێڕەوی ناسینەوە

Global Risks Forum (GRF)

The Global Risks Forum (GRF) decides recognition of contributors under its own programme rules; a contribution does not constitute GRF recognition.

Read the recognition pathway

ڕێڕەوی سەرمایە

Global Risks Alliance (GRA)

The Global Risks Alliance (GRA) decides under its own criteria whether any contribution bears on capital readiness.

Read the capital pathway

Each institution determines under its own rules what it accepts as evidence; a pathway reading is neither an approval nor investment advice.

15بینەران

Intended users

The area profile identifies 4 user communities.

  1. first-time contributors
  2. research and practitioner communities
  3. students and early-career professionals
  4. institutions exploring adoption
16Restricted standards

Restricted compatibility profiles

Standards whose text is not openly available are named and linked only. Any compatibility profile is kept on protected pages until an arrangement with the issuing body is in place.

The working group may identify restricted standards relevant to this area; they are listed here by name and link.

17Data sources

Data sources

2 data sources named in the area profile, each with provider, licence, update frequency and delivery path.

Data sources

Data sources are listed for reference; live data is displayed once licence review is complete.

زیندوو
0
on completion of licence review
Listed in the data register
0
licence terms recorded
Proposed for the register
2
licence terms to be recorded
جێبەجێکردن
0 governed service · 0 plugin · 1 browser · 1 snapshot · 0 listed for reference
proposed paths in order of preference: governed data service, plugin, direct browser read, build-time snapshot; sources whose terms do not permit reuse are listed for reference only
18نیشاندەرەکان

نیشاندەرەکان

The area profile names 1 indicator, each with its framework and code.

19Hazards and sectors

Hazards, threats and sectors concerned

Hazards and threats 0

This area draws on the hazards of the areas it is coupled with.

کەرتەکان 0

This area serves all sectors through the areas it is coupled with.

20سەرچاوەکان

سەرچاوەکان

3 references from peer-reviewed and official publications cited in the area profile, linked at the publishers’ own sites.

21Research hub

Recent research on this area

Recent peer-reviewed articles, preprints, datasets and reports on the subject of this area, retrieved at the time of reading from open scholarly metadata services (OpenAlex, Crossref, DataCite, Zenodo, arXiv, Europe PMC, OpenAIRE Graph) with search terms composed from the registry. Each work is listed with its authors, venue, year, type, open-access status and licence, and links to its DOI or landing page. Sources not yet enabled for live display on this site are listed for reference and are not queried.

Search termsopen collaboration; open source community; volunteer contribution; CRediT Contributor Roles Taxonomy; Citation File FormatDerived from the title and scope of the area, the NHS-1 hazards it names and the open standards it lists.

  • OpenAlexlisted for reference; not queried
  • Crossreflisted for reference; not queried
  • DataCitelisted for reference; not queried
  • Zenodolisted for reference; not queried
  • arXivlisted for reference; not queried
  • Europe PMClisted for reference; not queried
  • OpenAIRE Graphlisted for reference; not queried

No source is enabled for live display on this site yet: the sources are listed for reference and none is queried. Once the publisher of record enables a source after its terms are reviewed, recent works are listed here. Metadata and links only: title, authors, venue, year, type, open-access status and licence as each source records them; works are listed for orientation, not reviewed or endorsed.

23لە سەرانسەری تۆڕەکەدا

Programmes, tracks and courses for this area

GCRI Canada, The Global Risks Forum (GRF), The Global Risks Alliance (GRA) and Risk Academy work on the subject of this area in distinct roles (research and evidence; governance, policy and convening; capital, finance and markets; education and training). Each entry states why it corresponds and the step it offers; each institution sets its own terms of participation.

Governance, policy and convening

Global Risks Forum (GRF)

Tracks that convene public authorities, researchers and institutions on the governance of shared risks.

Research NexusConnects research networks across institutions, the community from which working groups draw contributors.Join this track globalriskforum.comAll tracks of The Global Risks Forum

Capital, finance and markets

Global Risks Alliance (GRA)

Industry programmes in which financial institutions build a shared understanding of systemic risk.

Financial Regulation NexusCompares regulatory and supervisory frameworks, the context in which supervised institutions read voluntary standards.Join this programme globalriskalliance.comAll programmes of The Global Risks Alliance
24زاراوە سەرەکییەکان

زاراوە سەرەکییەکان

UNI
Unique Nexus Identifier: a persistent identifier that resolves an artefact to its record.
پێشنیازکراو
A draft in the open development process that the Global Standards Council has not yet adopted. Each area profile is a proposal to the Nexus Standards registry.
adopt
Relation in which the external standard is used as published and values are validated against it.
change record
A public record of a proposed change under NS-13, decided by the editors with written reasons.
attestation
An evaluator’s recorded result for one clause and one subject under NS-11.
liaison sought
A liaison the working group intends to request from the issuing body; a liaison is established only when the body confirms it in writing.
26توێژینەوە

Recent research and sources

Peer-reviewed articles, preprints, reports and datasets on the subject of this area, retrieved at the time of reading from open scholarly metadata services (OpenAlex and Crossref) and listed with authors, venue, year, type and access status, with a link to each work. Curated references and related standards are listed first; recent works matched by subject follow and are listed for orientation.

Curated references

Related standards and frameworks

Search terms, derived from the title and scope of the area: open collaboration; open source community; volunteer contribution. With JavaScript enabled, recent works matching these terms are listed from OpenAlex and Crossref.

27پرسیارەکان

پرسیار و وەڵام.

What is the status of the Start here and contribute area?
The area profile is a proposal to the Nexus Standards registry; the area is not yet in the catalogue. Standards are adopted by the Global Standards Council after last call; in each country, adoption is a decision of its National Standards Council (NSC).
How are data sources presented?
Each data source is listed with its provider, licence, update frequency and delivery path, and links to the provider’s own publication.
How can this brief be amended?
Through a public change record under NS-13: a proposed amendment to the area profile or the registry, decided by the editors with written reasons.
ڕاپۆرتەکانبەشداری بکە

لەم لاپەڕەیەوە بەڵگە پێشکەش بکە.

Reports بڵاوکراوەی وەرزیی کۆنسۆرتیۆم ـە. ئەوەی تۆ لەسەر ئەم بابەتە دەیزانیت دەتوانێت لە وەشانی داهاتوودا ببێتە بەڵگە، کەیس یان ڕاستکردنەوە، بە ناوی خۆتەوە و لەژێر CC BY 4.0 بڵاو دەکرێتەوە کاتێک کاری خۆتە.

Nexus Standards
ستاندارد

Contribute to Start here and contribute

Institutions and experts are invited to propose amendments, join the working group or propose data sources. National participation is organised through each country’s National Nexus Consortium (NNC) and its National Working Groups (NWGs); competent national authorities are engaged through official channels.

دۆخ و بەکارهێنان. Nexus Standards ستانداردی پێشنیارکراون کە لە ڕێگەی پرۆسەیەکی کراوەوە لەژێر NS-13 پەرەیان پێدراوە و بۆ بەکارهێنانی خۆبەخشانە بڵاو کراونەتەوە؛ بڕوانامە، متمانەپێدان یان ڕەزامەندیی ڕێکخەر نین، و پەسەندکردن بڕیاری ئەنجومەنی جیهانیی ستانداردەکان و، لە هەر وڵاتێکدا، ئەنجومەنی نیشتمانیی ستانداردەکانی ئەو وڵاتەیە. UNI (Unique Nexus Identifier) بەرهەمێک دەناسێنێت؛ بڕوانامەی پێ نادات. ناوی دەستەکانی ستاندارد و ستانداردەکانیان هی پارێزەرەکانیانن و تەنها بۆ ناساندنی بەڵگەنامەکان بەکاردێن؛ هیچ دەقێکی ستانداردێکی دەرەکی لێرەدا دووبارە نەکراوەتەوە. Nexus Standards پەیوەست نییە بە هیچ دەستەیەکی ستانداردی ناوهێنراو لێرەدا، و لەلایەن هیچیانەوە پشتگیری یان بڕوانامەی پێ نەدراوە.

مۆڵەتەکان: CC BY 4.0 بۆ دەقی ستانداردەکان، تۆمارگەکان، سکێماکان و داتا؛ Apache-2.0 بۆ کۆدی سەرچاوە. ستانداردە دەرەکییەکان بە ناو، ژمارە و بەستەر لە ژێر مۆڵەتەکانی خۆیاندا ئاماژەیان پێدەدرێت. داتا، کتێبخانە و فۆنتەکانی لایەنی سێیەم مۆڵەتەکانی خۆیان دەپارێزن: بڕوانە ئاگادارییەکانی لایەنی سێیەم.