Ji vir dest pê bike û beşdar bibe
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).
- 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.
Kurte
- 01ScopeScope and boundaries
- 02Taking partHow anyone takes part in open standards.
- 03Standards architectureFoundation, referenced and implementing layers
- 04Contribution channelsFrom a comment at a standards body to a registry change
- 05StandardsStandards that apply
- 06System modelHow a shock travels through this system
- 07Working groupWorking group charter
- Nexus Standards
- 2
- NS-1, NS-9
- Standardên vekirî
- 4
- named, never copied
- Data and feeds
- 2
- listed for reference
- Girêdan
- 4
- with other areas
- UNI
- requested · allocation in progress
- Rewş
- 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.
Files include the credits and the licence statement and are generated in the browser; no data is transmitted. Downloads require JavaScript.
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.
How anyone takes part in open standards.
Awayên beşdarbûnê
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.
Kîjan standard derbas dibin
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.
| Standard | Laş | Guhertoy | Têkilî | Gihîştin | Piştrastkirî |
|---|---|---|---|---|---|
| RFC 2026 The Internet Standards Process – Revision 3 (BCP 9) | IETF | RFC 2026 (1996) with BCP 9 amendments; draft-ietf-procon-2026bis in progress (2026) | cite | vekirî | piştrastkirî |
| W3C Process Document (2025) | World Wide Web Consortium | effective 18 August 2025; Proposed Recommendation phase removed | cite | vekirî | piştrastkirî |
| OASIS Technical Committee Process and IPR Policy | OASIS Open | current TC Process; IPR Policy adopted 20 January 2005 with later revisions | cite | vekirî | piştrastkirî |
| OGC Technical Committee Policies and Procedures | Open Geospatial Consortium | 05-020r29 | cite | vekirî | piştrastkirî |
| ISO/IEC Directives, Part 1 (procedures) with Consolidated ISO Supplement, and Part 2 (drafting) | ISO û IEC | Part 1 and ISO Supplement edition 2024 (V01/2024); Part 2 edition year UNVERIFIED | cite | vekirî | piştrastkirî |
| RFC 6852 Affirmation of the Modern Paradigm for Standards (OpenStand principles) | IAB, IEEE-SA, IETF, Internet Society, W3C | Informational RFC (January 2013); affirmation signed 29 August 2012 | adopt | vekirî | piştrastkirî |
| Regulation (EU) No 1025/2012 on European standardisation | European Parliament and Council | 25 October 2012 (UK retained copy at IP completion day) | cite | vekirî | piştrastkirî |
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.
OASIS Common Alerting Protocol Version 1.2
OASIS Emergency Management TC · adopt
Geospatial and Earth observation · STACSpatioTemporal Asset Catalog (STAC) specification
STAC community; OGC Community Standard 25-004 · adopt.
Provenance and evidence · PROV-OW3C PROV-O: The PROV Ontology
W3C Provenance Working Group · adopt
Outcomes
Outcomes of a contribution
- 01
A registry correction
A version, year, URL or relation corrected in the external standards register, citing the source.
- 02
A crosswalk entry
A Nexus clause related to a part of the external document by number (NS-14), without reproducing its text.
- 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.
- 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.
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).
Lêgerînerê pêvajoyê · Standards · kod bike û rast bike
Çerxa jiyanê ya standardê
17 gav·6 qonax
Standards · kod bike û rast bike
Çerxa jiyanê ya standardê
Dîtinên çerxê dibin pêşniyarên guhertinê, Encûmena Standardên Cîhanî piştî banga dawî ya giştî dipejirîne, û her welat pejirandina xwe bi xwe diyar dike.
01 Rêkirina mîsyonan
- 01Route missions to standards and profilesStep · Nexus StandardsNexus Standards routes each candidate mission to the standards and profiles that apply.
02 Profîl û lihevhatin
- 02Profîlên mîsyonan pêk bîneGav · Nexus StandardsNexus Standards profîlên mîsyonan pêk tîne û her pejirandineke neteweyî ya ku mîsyon xwe dispêrinê tomar dike.
- 03Derketinên avakirinê li hember profîlan piştrast bikeGav · Nexus StandardsNexus Standards encamên avakirinê li hember profîlên pêkhatî piştrast dike û delîlan tomar dike.
- 04Çavdêriya lihevhatinê bike û delîlên mohrkirî tomar bikeGav · Nexus StandardsDi Hefteya Çalakiyê de Nexus Standards lihevhatinê dişopîne û cudabûnan tomar dike.
03 Pêşniyar û nirxandin
- 05Dûrketin û rastkirin dibin pêşniyarên guhertinêGav · Nexus StandardsDûrketin dibin pêşniyarên guhertinê, û rastkirin wekî guhertinek di delîlan de tê tomarkirin.
- 06Encamên çerxê dibin pêşniyarên guhertinêGav · Nexus StandardsDîtinên çerxekê dibin pêşniyarên guhertinê: dîtinên rêbaz û rastkirinê ji rêzeya Pergalên Stratejîk (F06) û babetên dosyayê ji Nexus…
- 07Bi eşkereyî amade bike û biguherîneGav · Komîte û komên xebatêKomîteyên teknîkî û komên xebatê standardan di pêvajoya vekirî ya NS-13 de amade dikin û nû dikin.
- 08Nirxandin ber bi biryara encûmenê veGav · Nexus StandardsNexus Standards pêşniyarên guhertinê bi rêya nirxandinê ber bi biryara encûmenê ve dibe.
04 Biryara encûmenê
- 09Banga dawî ya giştîGav · Encûmena Cîhanî ya StandardanEncûmena Cîhanî ya Standardan piştî banga dawî ya nod-rojî bi piraniya du-ji-sê dipejirîne.
- 10Pejirandina cîhanî ya standardekêBiryar · Encûmena Cîhanî ya StandardanEncûmena Standardên Cîhanî piştî banga dawî ya giştî li ser pejirandina her standardê biryar dide.
05 Biweşîne û nas bike
- 11Assign a UNI and publishStep · Secretariat (GCRI Canada)Nexus Standards assigns UNIs and deposits publications under the publisher’s process.
- 12UNI nas dike û qet sertîfîka nadeTomar · Nexus StandardsHer tiştekî sala bernameyê nasnavekî hildigire, UNI-yek di bin NS-1 de, da ku were jêgirtin, guhertoya wê were girtin û were çareserkirin.
- 13Guhertinên pejirandî yên salê biweşîneGav · Nexus StandardsDi nûkirinê de Nexus Standards guhertinên pejirandî yên salê û rewşa pejirandina neteweyî diweşîne.
06 Pejirandin û sepandina neteweyî
- 14Pejirandina neteweyî ji aliyê Encûmena Neteweyî ya Standardan veBiryar · Encûmena Neteweyî ya StandardanEncûmena Standardên Neteweyî ya her welatî li ser pejirandina neteweyî biryar dide: wekî xwe pejirandin, bi profîlekê pejirandin (NS-16), adaptekirin, an tenê referans.
- 15Standardên pejirandî digihîjin kurs û weşananGav · Nexus StandardsHer standard an profîleke pejirandî dibe modulek kursê li Risk Academy (F09), û standard di weşanên Reports de têne sepandin (R1).
- 16Pejirandin ji bo her herêma desthilatê dawî yeStandard · Encûmena Neteweyî ya StandardanPejirandin ji bo her herêma desthilatê dawî ye, û GSC tu vetoyê li ser biryareke neteweyî nîne. Tu dezgeheke cîhanî vetoyê nagire.
- 17Tomarên pejirandina neteweyîTomar · Nexus StandardsProfîlên mîsyonê yên pêkhatî û tomarên pejirandina neteweyî di amadekirina amadebûnê de diçin 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
| Gav | Qonax | Xebitandin | Kî | Decision rule | Tomar | Implements |
|---|---|---|---|---|---|---|
| 01 | Pêşniyar | 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 mandate | every change to a standard, registry, clause or policy enters through a proposal with a UNI | a proposal (nexus-proposal) with target, rationale, changes and stakeholder groups | NS13-R1, NS13-R2 |
| 02 | Nirxandin | Open review (step). Comments are collected in the open record of the proposal. | any participant, with identity recorded | participation is open and free; identity is recorded | comments in the open | NS13-R2 |
| 03 | Nirxandin | Dispositions (record). Nothing is decided in private channels. | the editors | decisions are reasoned in writing | a disposition per comment (accepted, rejected, deferred, open) with a reason | NS13-R2 |
| 04 | Last call | Last call (gate). The period is thirty days by default, fourteen for errata and ninety for a new standard. | the editors | announced to every stakeholder group listed; objections are dispositioned before acceptance | the announcement and lastCallEndsAt | NS13-R3 |
| 05 | Editors | Editors decide (decision). The decision and its reasons are recorded with the proposal. | the editors | editors maintain the text and run the process; they do not adopt | accepted, rejected or withdrawn, with reasons | NS13-R4 |
| 06 | Editors | New version (record). A major change needs a crosswalk and a migration note. | the editors | versions are semantic; registries append-only; existing UNIs are never invalidated | a semantic version; registries appended | NS13-R5 |
| 07 | Pejirandin | GSC adoption (decision). Adoption follows the Charter and is recorded as a reference. | the Global Standards Council (GSC) | authority decisions are recorded references | the decision reference that changes the standard’s status | NS13-R4 |
| 08 | Pejirandin | 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 Consortium | national adoption is a national decision; national law and language prevail | a national decision: adopt, adapt or reference, with the national application profile | NS13-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.
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.
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 steps·3 stages·1 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.
01 Contributor
- 01Identify the bodyStart · the contributorEach standard package links to the issuing body, its working group or technical committee and its process document.
- 02Read IPR and participation rulesStep · the contributorParticipation rules differ by body, from no membership at the IETF to membership at OASIS.
- 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.
- 07Implement and testExercise · the contributorThe contributor runs the body’s test suite or validator, where the body publishes one.
02 The standards body
- 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.
- 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.
- 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.
- 08Implementation reportRecord · the body or the working groupImplementations are listed as submitted, in alphabetical order.
03 Nexus Standards
- 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.
- 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.
- 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
| Gav | Qonax | Xebitandin | Kî | Decision rule | Tomar |
|---|---|---|---|---|---|
| 01 | Contributor | Identify the body (start). Each standard package links to the issuing body, its working group or technical committee and its process document. | the contributor | the register names the body and links to its own page | the body’s page, linked from the package |
| 02 | Contributor | Read 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 contributor | membership, patent policy and contributor agreements are set by the body and read at the source | the requirements of the channel |
| 03 | The standards body | Join 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 committee | the channel belongs to the body and follows its process document | a list subscription, an issue account, a membership |
| 04 | The standards body | File 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 tracker | an issue is the body’s record, cited by URL | an issue with a stable link |
| 05 | The standards body | Public 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 process | the body decides under its own rules; the Nexus Standards record the public outcome | comment dispositions by the body |
| 06 | Contributor | Propose 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 channel | text is proposed through the body’s own channel; the body’s text remains with the body | a change request, an Internet-Draft or a comment with wording |
| 07 | Contributor | Implement and test (exercise). The contributor runs the body’s test suite or validator, where the body publishes one. | the contributor | a passing run is evidence of implementation | a test run with the suite version and time |
| 08 | The standards body | Implementation report (record). Implementations are listed as submitted, in alphabetical order. | the body or the working group | listed as the body publishes it, without ranking | the report, linked |
| 09 | Nexus Standards | Cite 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 editors | cited by identifier, clause number and URL (NS-14); a recorded relation does not imply equivalence | a crosswalk entry or a clause citing the source |
| 10 | Nexus Standards | Change 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 recorded | every change is submitted as a change proposal under NS-13 | a change proposal with a UNI |
| 11 | Nexus Standards | Register change (end). The register entry is amended and the package page is regenerated from it. | editors, with reasons on record | accepted, rejected or withdrawn in writing; the history is retained | the 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.
Standardên ku têne sepandin
The area profile lists 2 Nexus Standards. Each is a proposed standard under development.
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.
Pergal û girêdan
- Ji vir dest pê bike û beşdar bibe
- Qadên vekirî û bangên avakirinê Girêdan
- Standardek çawa tê çêkirin Girêdan
- Komên xebatê Girêdan
- Lîsanskirin û milkê hizrî Girêdan
Kontrol
NS-1UNI û kataloga berheman (rêziman v0.2: beşên qad, sektor, herêm û jîngehê)NS-9UNI yên çarçoveyî (belavkirin, mînak, mînakên bernameyê)NRS-E3Academy: jêhatîbûn, fêrbûna bi kirinê û belgenameNRS-H29Hazard family: Air pollution episodes (NHS-1 poll.air-quality)NRS-H88Malbata metirsiyê: Zirara binesaziya binê deryayê (NHS-1 infra.seabed)NRS-H107Malbata metirsiyê: Kombûn û yekrengiya binesaziya dîjîtal (NHS-1 tech.digital-concentration)NRS-I4Delîlên lêkolînê, dubarekirin û zanista vekirîNRS-H16Malbata metirsiyê: Qeşaya ser avê (NHS-1 cryo.floating-ice)
Çavdêrî
- 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
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).
- Contributor guide with sign-off steps
- Charter template and worked example of an area taken up by a community
- Code of conduct with an enforcement procedure
- Research Data Alliance (information exchange on community onboarding sought) liaison sought
- W3C Community Groups (information exchange sought) liaison sought
Girêdanên pergalî
4 couplings link this area to other areas and programmes, each with the mechanism of the link.
- 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.
- 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.
- 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.
- 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.
Open standards referenced
4 open standards, each with its relation as recorded in the register under NS-14. Hover over or focus a relation for its definition.
adopt4
CRediT Contributor Roles Taxonomy (ANSI/NISO Z39.104-2022)NISOproposed for the registerCitation File Format (CITATION.cff)Citation File Format projectlisted in the register · citation-cffWeb Content Accessibility Guidelines (WCAG) 2.2W3Cproposed for the registerDeveloper Certificate of Origin 1.1Linux Foundation (developercertificate.org)proposed for the registerRouting, monitoring and verification tools
Routing console
Select a sector, hazard family, capability and artefact type; the registry identifies the applicable standards and states the reasons.
Available · draft in the browserProfile composer
Combine standards and clauses into a draft profile with citations, in YAML or JSON; nothing is submitted.
Each console computes from the registry and states its reasoning; decisions remain with the competent bodies.
Open research questions
3 questions identified as priorities for the working group.
- How to keep the first contribution simple enough for practitioners in low-bandwidth settings while still collecting OWFa and DCO sign-offs.
- How to credit non-code, non-text work such as data curation, translation and review fairly in CRediT terms.
- How to sustain volunteer editors without creating paid roles that tilt influence.
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.
GCRI Canada
GCRI Canada decides under its own rules how contributions relate to its evidence work; contributing implies no acceptance by it.
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.
Global Risks Alliance (GRA)
The Global Risks Alliance (GRA) decides under its own criteria whether any contribution bears on capital readiness.
Each institution determines under its own rules what it accepts as evidence; a pathway reading is neither an approval nor investment advice.
Intended users
The area profile identifies 4 user communities.
- first-time contributors
- research and practitioner communities
- students and early-career professionals
- institutions exploring adoption
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.
Data sources
2 data sources named in the area profile, each with provider, licence, update frequency and delivery path.
Data sources are listed for reference; live data is displayed once licence review is complete.
- Zindî
- 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
- Radestkirin
- 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
OpenAlex works API (finding researchers already publishing in an OPEN area)for reference.
OurResearch (OpenAlex) · daily
CC0 1.0
build-time snapshotproposed for the data register
ORCID public API (contributor identifiers for attribution)for reference.
ORCID · continuous
CC0 1.0 (public data file)
direct browser readproposed for the data register.
Nîşander
The area profile names 1 indicator, each with its framework and code.
Indicator names and codes are given as published by their stewards.
Hazards, threats and sectors concerned
Hazards and threats 0
This area draws on the hazards of the areas it is coupled with.
Sektor 0
This area serves all sectors through the areas it is coupled with.
Çavkanî
3 references from peer-reviewed and official publications cited in the area profile, linked at the publishers’ own sites.
peer-reviewedMotivation, Governance, and the Viability of Hybrid Forms in Open Source Software DevelopmentManagement Science · 2006peer-reviewedCoase’s Penguin, or, Linux and The Nature of the FirmYale Law Journal · 2002- standardCRediT (Contributor Roles Taxonomy), ANSI/NISO Z39.104-2022NISO · 2022
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.
Risk Academy courses and disciplines
2 courses and 4 disciplines of Risk Academy (risksacademy.com) that teach the knowledge and methods of this area. Each course lists its level, stream and learning hours.
Kurs
Dîsîplîn
The correspondence between courses, disciplines and the Nexus Standards is maintained with Risk Academy and is subject to its academic review.
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.
Lêkolîn û delîl
GCRI Canada
Research programmes that produce the observations, models and assessments these records describe.
LabsOpens protocols and testbeds to research teams, universities and student teams, a route for first contributions.Apply to this programme CampaignsBuilds risk literacy and participation with communities, the public side of contribution.Apply to this programme therisk.globalAll programmes of GCRI CanadaGovernance, 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 ForumCapital, 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 AlliancePerwerde û rahênan
Risk Academy
Courses and disciplines that teach the knowledge and methods practitioners need to apply these standards.
Resilience Building 101RAF-102 · Introductory · 19.5 learning hoursConcepts, measures and investments that help people, infrastructure and organisations withstand and recover from shocksTake this course Science Policy 101RAF-103 · Introductory · 19.5 learning hoursBringing evidence on risk to decision makers honestly, clearly and usefullyTake this course All courses and disciplinesListed in the education and training section of this pageTêgehên sereke
- UNI
- Unique Nexus Identifier: a persistent identifier that resolves an artefact to its record.
- pêşniyarkirî
- 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.
Related areas
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
- Motivation, Governance, and the Viability of Hybrid Forms in Open Source Software Development
Management Science · 2006 · Peer-reviewed - Coase’s Penguin, or, Linux and The Nature of the Firm
Yale Law Journal · 2002 · Peer-reviewed - CRediT (Contributor Roles Taxonomy), ANSI/NISO Z39.104-2022
NISO · 2022 · Standard
Related standards and frameworks
- CRediT Contributor Roles Taxonomy (ANSI/NISO Z39.104-2022)
NISO - Citation File Format (CITATION.cff)
Citation File Format project - Web Content Accessibility Guidelines (WCAG) 2.2
W3C - Developer Certificate of Origin 1.1
Linux Foundation (developercertificate.org)
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.
Pirs û bersiv.
What is the status of the Start here and contribute area?
How are data sources presented?
How can this brief be amended?
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.
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.
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.