Nexus Standards · Foundations and Governance · Foundations

Area · proposed

Start here and contribute

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 artifact of the area carries a UNI (Unique Nexus Identifier).

Applicable standardsReturn to Foundations and Governance
01Overview

Summary

Reading order23 sections
  1. 01ScopeScope and boundaries
  2. 02Taking partHow anyone takes part in open standards.
  3. 03Standards architectureFoundation, referenced and implementing layers
  4. 04Contribution channelsFrom a comment at a standards body to a registry change
  5. 05Nexus StandardsApplicable Nexus Standards
  6. 06System model and scenario simulatorSystem model and cascade scenario: Start here and…
  7. 07Working groupWorking group charter
UNI
requested · allocation in progress
Status
Proposednot yet listed in the registry
Last reviewed
area profile
Cite this page

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.

02Scope

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.

03Earth observation

Population, settlement and hazards in the Mediterranean

The map frames the Mediterranean as an example geography for start here and contribute; the frame gives context and is not a statement of where the standards apply. Shown at first: population density, 2020 (Gridded Population of the World v4.11, NASA SEDAC, CIESIN, Columbia University) and night-time lights, daily (VIIRS Black Marble, VNP46A2, NASA LAADS DAAC). The layer drawer adds flood water, 3-day composite (VIIRS Global Flood Product); active fires and thermal anomalies, last day (VIIRS NOAA-20 375 m, FIRMS); and true colour (VIIRS NOAA-20 corrected reflectance). NASA products are served through NASA GIBS under NASA's open data policy, with acknowledgement; population density is GPW v4.11 by CIESIN, Columbia University, under CC BY 4.0; coastlines, boundaries and place names come from NASA GIBS reference layers (© OpenStreetMap contributors, ODbL) and Natural Earth (public domain). Each layer shows its own observation date; full credits are given under the map. Other sources of the profile, such as ORCID public API (contributor identifiers for attribution) and OpenAlex works API (finding researchers already publishing in an OPEN area), are listed for reference.

The interactive map needs JavaScript; the layer list and sources are below.

Layers 2

People and hazards

Latest available

NASA GIBS / EOSDIS · ASTER GDEM (METI, NASA) · Blue Marble (NASA) · © OpenStreetMap contributors (ODbL) · Natural Earth

Loading the latest NASA imagery.

Drag to move. Ctrl or ⌘ and scroll, pinch or the buttons to zoom; hover for the values under the pointer; reset returns to the region.

Where people live, night-time lights and the floods and fires public institutions answer to, framed on the Mediterranean.Satellite and model products as NASA publishes them, each with its own date; indicators, not assessments of any place.

Data: NASA GIBS · ASTER GDEM · Blue Marble · © OpenStreetMap contributors · Natural Earth · NASA EONETSources and licences

  • We acknowledge the use of imagery provided by services from NASA's Global Imagery Browse Services (GIBS), part of NASA's Earth Science Data and Information System (ESDIS). Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
  • We acknowledge the use of imagery provided by services from NASA's Global Imagery Browse Services (GIBS), part of NASA's Earth Science Data and Information System (ESDIS). Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
  • Center for International Earth Science Information Network (CIESIN), Columbia University. 2018. Gridded Population of the World, Version 4 (GPWv4): Population Density, Revision 11. NASA Socioeconomic Data and Applications Center (SEDAC). Licensed under CC BY 4.0. Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). doi:10.7927/H49C6VHW. CC BY 4.0
  • VIIRS Black Marble night-time lights, NASA Goddard Space Flight Center; distributed by the NASA Level-1 and Atmosphere Archive and Distribution System (LAADS DAAC); imagery via NASA GIBS. Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
  • VIIRS near-real-time products (flood, land surface temperature, snow cover, corrected reflectance), NASA LANCE; imagery via NASA GIBS. Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
  • NASA Fire Information for Resource Management System (FIRMS), VIIRS 375 m active fire product, NASA LANCE; vector tiles via NASA GIBS. Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
  • ASTER GDEM is a product of METI and NASA (ASTER Global Digital Elevation Model V003, NASA LP DAAC); imagery via NASA GIBS. Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). Cite as: NASA/METI/AIST/Japan Spacesystems and U.S./Japan ASTER Science Team (2019). ASTER Global Digital Elevation Model V003. doi:10.5067/ASTER/ASTGTM.003. NASA open data
  • Made with Natural Earth. Free vector and raster map data @ naturalearthdata.com. Public domain
  • © OpenStreetMap contributors (ODbL), via NASA GIBS (coastlines, boundaries, roads and place names). Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). ODbL
  • Blue Marble, NASA Earth Observatory; imagery via NASA GIBS. Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
  • Context on the globe and flat map: coastlines, boundaries, roads and place names from NASA GIBS reference layers (OpenStreetMap data, ODbL, © OpenStreetMap contributors); Blue Marble imagery as an optional base; 3D terrain and the elevation read-out from the ASTER GDEM elevation colour index (5 m to 200 m classes, exaggerated for legibility). Boundaries are drawn as published and imply no position on any territory.
  • Globe: MapLibre GL JS 6.9.1, BSD-3-Clause, © MapLibre contributors.
  • Live: NASA EONET Events are indicative, not authority warnings.
  • NASA GIBS: We acknowledge the use of imagery provided by services from NASA's Global Imagery Browse Services (GIBS), part of NASA's Earth Science Data and Information System (ESDIS).
  • Optional layers (3 sources in the layer list: live, forecast, observed and context) print their provider credit on the map and here when switched on; forecasts are model output and derived indices are estimates.

Layers and dates

  • Population density, 2020: Population: CIESIN, Columbia University, Gridded Population of the World v4.11 (2018), NASA SEDAC, CC BY 4.0 · static
  • Night-time lights, daily: VIIRS Black Marble (VNP46A2), NASA LAADS DAAC · 12 Oct 2026
  • Flood water, 3-day composite: VIIRS Global Flood Product, NASA LANCE · 14 Oct 2026
  • Active fires and thermal anomalies, last day: VIIRS NOAA-20 375 m (FIRMS), NASA LANCE FIRMS · 13 Oct 2026
  • True colour: VIIRS NOAA-20 corrected reflectance, NASA LANCE · 13 Oct 2026

04Process

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 cards carry its own data sources, indicators, open standards, couplings and, where listed, hazards, and each operation names the Nexus rules it implements (5).

Process · the development track: from a proposal to adoption (NS-13)8 operations · 5 phases
Start here and contribute: the development track: from a proposal to adoption (NS-13)A proposal with a UNI 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).
All operations in order (8)
  1. 01

    File a proposal start · Proposal

    Participation needs no membership fee; decisions are made by the recorded process.

    Who
    any person or organisation, identified by ORCID or ROR, or an agent under a mandate
    Decision rule
    every change to a standard, registry, clause or policy enters through a proposal with a UNI
    Record
    a proposal (nexus-proposal) with target, rationale, changes and stakeholder groups
    Implements
    NS13-R1, NS13-R2
  2. 02

    Open review step · Review

    Comments are collected in the open record of the proposal.

    Who
    any participant, with identity recorded
    Decision rule
    participation is open and free; identity is recorded
    Record
    comments in the open
    Implements
    NS13-R2
  3. 03

    Dispositions record · Review

    Nothing is decided in private channels.

    Who
    the editors
    Decision rule
    decisions are reasoned in writing
    Record
    a disposition per comment (accepted, rejected, deferred, open) with a reason
    Implements
    NS13-R2
  4. 04

    Last call gate · Last call

    The period is thirty days by default, fourteen for errata and ninety for a new standard.

    Who
    the editors
    Decision rule
    announced to every stakeholder group listed; objections are dispositioned before acceptance
    Record
    the announcement and lastCallEndsAt
    Implements
    NS13-R3
  5. 05

    Editors decide decision · Editors

    The decision and its reasons are recorded with the proposal.

    Who
    the editors
    Decision rule
    editors maintain the text and run the process; they do not adopt
    Record
    accepted, rejected or withdrawn, with reasons
    Implements
    NS13-R4
  6. 06

    New version record · Editors

    A major change needs a crosswalk and a migration note.

    Who
    the editors
    Decision rule
    versions are semantic; registries append-only; existing UNIs are never invalidated
    Record
    a semantic version; registries appended
    Implements
    NS13-R5
  7. 07

    GSC adoption decision · Adoption

    Adoption follows the Charter and is recorded as a reference.

    Who
    the Global Standards Council (GSC)
    Decision rule
    authority decisions are recorded references
    Record
    the decision reference that changes the standard's status
    Implements
    NS13-R4
  8. 08

    National adoption end · Adoption

    The NSC decides for its jurisdiction, engaging competent national authorities through its public-authority liaison; the GSC has no veto over a national decision.

    Who
    the National Standards Council (NSC) of each National Nexus Consortium
    Decision rule
    national adoption is a national decision; national law and language prevail
    Record
    a national decision: adopt, adapt or reference, with the national application profile
    Implements
    NS13-R4

Fig.Phases read left to right; each card names the operation, its actor and the record it leaves, and each edge label names the hand-over. Play, step or scrub; the detail panel gives the full text of the selected operation. 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 artifact catalog.

05Taking part

How anyone takes part in open standards.

Ways to take part

Four ways to take part

Learn

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

Find

Which standards apply

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

Contribute

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

Build

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.

StandardBodyVersionRelationAccessVerified
RFC 2026 The Internet Standards Process - Revision 3 (BCP 9)IETFRFC 2026 (1996) with BCP 9 amendments; draft-ietf-procon-2026bis in progress (2026)citeopenverified
W3C Process Document (2025)World Wide Web Consortiumeffective 18 August 2025; Proposed Recommendation phase removedciteopenverified
OASIS Technical Committee Process and IPR PolicyOASIS Opencurrent TC Process; IPR Policy adopted 20 January 2005 with later revisionsciteopenverified
OGC Technical Committee Policies and ProceduresOpen Geospatial Consortium05-020r29citeopenverified
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 UNVERIFIEDciteopenverified
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 2012adoptopenverified
Regulation (EU) No 1025/2012 on European standardisationEuropean Parliament and Council25 October 2012 (UK retained copy at IP completion day)citeopenverified

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.

Hydrometeorological hazard · CAP 1.2

OASIS Common Alerting Protocol Version 1.2

OASIS Emergency Management TC · adopt

Geospatial and Earth observation · STAC

SpatioTemporal Asset Catalog (STAC) specification

STAC community; OGC Community Standard 25-004 · adopt

Provenance and evidence · PROV-O

W3C PROV-O: The PROV Ontology

W3C Provenance Working Group · adopt

Outcomes

Outcomes of a contribution

  1. 01

    A registry correction

    A version, year, URL or relation corrected in registry/external-standards.yaml, 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 Nexus clause

    An obligation adopted 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.

06Standards 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.

07Contribution channels

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.

Canvas · from a comment at a standards body to a registry changeProcess diagram · 11 operations
Contributing through a standards body: from a comment to a register changeA 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 diagram shows the process as specified; it does not report the status of any standard, proposal or record.
All operations in order (11)
  1. 01

    Identify the body start · Contributor

    Each standard package links to the issuing body, its working group or technical committee and its process document.

    Who
    the contributor
    Decision rule
    the register names the body and links to its own page
    Record
    the body's page, linked from the package
  2. 02

    Read IPR and participation rules step · Contributor

    Participation rules differ: an IETF working group requires no membership; an OASIS technical committee requires membership; W3C groups have community and member forms.

    Who
    the contributor
    Decision rule
    membership, patent policy and contributor agreements are set by the body and read at the source
    Record
    the requirements of the channel
  3. 03

    Join a channel step · The standards body

    Mailing lists and their archives, issue trackers and public comment lists are listed per package with what each requires.

    Who
    the body's working group or committee
    Decision rule
    the channel belongs to the body and follows its process document
    Record
    a list subscription, an issue account, a membership
  4. 04

    File an issue record · The standards body

    An erratum, a question or a proposal becomes an issue in the body's tracker; the Nexus Standards cite it by link.

    Who
    the contributor, in the body's tracker
    Decision rule
    an issue is the body's record, cited by URL
    Record
    an issue with a stable link
  5. 05

    Public review gate · The standards body

    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.

    Who
    the body, under its process
    Decision rule
    the body decides under its own rules; the Nexus Standards record the public outcome
    Record
    comment dispositions by the body
  6. 06

    Propose text step · Contributor

    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.

    Who
    the contributor, in the body's channel
    Decision rule
    text is proposed through the body's own channel; the body's text remains with the body
    Record
    a pull request, an Internet-Draft or a comment with wording
  7. 07

    Implement and test exercise · Contributor

    The contributor runs the body's test suite or validator, where the body publishes one.

    Who
    the contributor
    Decision rule
    a passing run is evidence of implementation
    Record
    a test run with the suite version and time
  8. 08

    Implementation report record · The standards body

    Implementations are listed as submitted, in alphabetical order.

    Who
    the body or the working group
    Decision rule
    listed as the body publishes it, without ranking
    Record
    the report, linked
  9. 09

    Cite the outcome step · Nexus Standards

    The outcome at the body becomes a register entry: a corrected version, a new crosswalk entry or a clause that cites the source.

    Who
    Nexus Standards editors
    Decision rule
    cited by identifier, clause number and URL (NS-14); a recorded relation does not imply equivalence
    Record
    a crosswalk entry or a clause citing the source
  10. 10

    Change proposal record · Nexus Standards

    A change proposal is a pull request to the canonical repository, with a proposal record in the public change record. Editors decide with written reasons.

    Who
    any person, with identity recorded
    Decision rule
    every change is submitted as a change proposal under NS-13
    Record
    a change proposal with a UNI
  11. 11

    Register change end · Nexus Standards

    The register entry is amended and the package page is regenerated from it.

    Who
    editors, with reasons on record
    Decision rule
    accepted, rejected or withdrawn in writing; the history is retained
    Record
    the amended register entry and its history

Fig.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. Sources: OpenStand principles (RFC 6852) · NS-13: development process · NS-14: crosswalk and conformance claims.

08Nexus Standards

Applicable Nexus Standards

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

  1. 01

    NS-1 · The UNI and the artifact catalog (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

09System model and scenario simulator

System model and cascade scenario: Start here and contribute

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.

Controls

  • NS-1 The UNI and the artifact catalog (grammar v0.2: domain, sector, region and environment segments)
  • NS-9 Contextual UNIs (deployments, instances, programme instances)
  • NRS-E3 Academy: competence, learning by doing and credentials
  • NRS-H29 Hazard family: Air pollution episodes (NHS-1 poll.air-quality)
  • NRS-H88 Hazard family: Seabed infrastructure damage (NHS-1 infra.seabed)
  • NRS-H107 Hazard family: Digital infrastructure concentration and monoculture (NHS-1 tech.digital-concentration)
  • NRS-I4 Research evidence, reproducibility and open science
  • NRS-H16 Hazard family: Floating ice (NHS-1 cryo.floating-ice)

Observation

  • 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
10Working group

Working group charter

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

Scope

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
11Systemic couplings

Systemic couplings

4 couplings link this area to other areas and programmes, each with the mechanism of the link. Select a card on the diagram to trace a coupling.

Diagram · the area and its couplingsProcess diagram
Start here and contribute: systemic couplingsSystemic couplings of Start here and contribute as stated in the area profile: 2 areas in Foundations and Governance, 2 areas in other programmes and 1 programme reached. Each coupling states the mechanism that links the two areas.

Fig.The area at the left; coupled areas in the same programme, coupled areas in other programmes and the programmes reached to the right.

  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.
12Open standards

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 register
13Consoles

Routing, monitoring and verification tools

Available · runs in the browser

Routing console

Select a sector, hazard family, capability and artifact type; the registry identifies the applicable standards and states the reasons.

Available · draft in the browser

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

14Research 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.
15Readiness

Evidence, recognition and capital pathways

What each institution of the ecosystem draws from this area: 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

Recognition pathway

The 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

Capital pathway

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

16Audiences

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
17Restricted 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.

18Data 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.

Live
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
Delivery
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
19Indicators

Indicators

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

SDG global indicator framework4.4.1Proportion of youth and adults with information and communications technology (ICT) skills, by type of skill

Indicator names and codes are given as published by their stewards.

20Hazards and sectors

Hazards, threats and sectors concerned

Hazards and threats 0

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

Sectors 0

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

21Sources

Sources

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

  1. peer-reviewedMotivation, Governance, and the Viability of Hybrid Forms in Open Source Software DevelopmentManagement Science · 2006
  2. peer-reviewedCoase's Penguin, or, Linux and The Nature of the FirmYale Law Journal · 2002
  3. standardCRediT (Contributor Roles Taxonomy), ANSI/NISO Z39.104-2022NISO · 2022
22Research 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.

23Education and training

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.

Courses

Course RAF-102 · Hazards and resilienceResilience Building 101Concepts, measures and investments that help people, infrastructure and organisations withstand and recover from shocksIntroductory · Foundation stream · 19.5 learning hoursTake this course · risksacademy.comCourse RAF-103 · Governance and policyScience Policy 101Bringing evidence on risk to decision makers honestly, clearly and usefullyIntroductory · Foundation stream · 19.5 learning hoursTake this course · risksacademy.com

Disciplines

Discipline · Systems and nexusNexus-Based Risk Management (NRM)risksacademy.comDiscipline · Governance and policyCapacity development and technical assistancerisksacademy.comDiscipline · Systems and nexusWater-energy-food-ecosystems nexusSystems and Nexus faculty: introduction to the nexus approachrisksacademy.comDiscipline · Risk scienceRisk information standards and interoperabilityGovernance and Policy faculty: participating in standards developmentrisksacademy.com

The correspondence between courses, disciplines and the Nexus Standards is maintained with Risk Academy and is subject to its academic review.

24Across the network

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.

Research and evidence

GCRI Canada

Research programmes that produce the observations, models and assessments these records describe.

Nexus LabsOpens protocols and testbeds to research teams, universities and student teams, a route for first contributions.Apply to this programme Nexus CampaignsBuilds risk literacy and participation with communities, the public side of contribution.Apply to this programme therisk.globalAll programmes of GCRI Canada

Governance, policy and convening

The 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

The 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

Education and training

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 page
25Key terms

Key terms

UNI
Unique Nexus Identifier: a persistent identifier that resolves an artifact to its record.
proposed
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.
27Research

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.

28Questions

Questions and answers.

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 listed in the registry. 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.
NRNexus Reports gateway · GW-STD

Contribute to Nexus Reports from this page.

Nexus Reports is the Consortium's quarterly publication. What you know about this subject can become evidence, a case or a correction in the next edition, credited to you and published under CC BY 4.0 where it is your own work.

Nexus Standards

Never send personal data, sensitive infrastructure detail or anything you have no right to share. A contribution is reviewed before use; sending it confers no authorship or editorial rights, and sponsorship never buys a finding.

Across the Consortium

The same subject across the Consortium.

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.

Propose a change All areas of Foundations and Governance

Status and use. The Nexus Standards are proposed standards developed through an open process under NS-13 and published for voluntary use; they do not constitute certification, accreditation or regulatory approval, and adoption remains a decision of the Global Standards Council and, in each country, of its National Standards Council. A UNI (Unique Nexus Identifier) identifies an artifact; it does not certify it. Names of standards bodies and their standards belong to their stewards and are used only to identify the documents; no text of an external standard is reproduced here. Nexus Standards is not affiliated with, endorsed by or certified by any standards body named here.

Licences: CC BY 4.0 for standards text, registries, schemas and data; Apache-2.0 for reference code. External standards are cited by name, number and link under their own licences. Third-party data, libraries and fonts keep their own licences: see Third-party notices.

Skip to toolbar