Nexus Standards · Foundations and Governance · Cross-cutting capabilities

Area · listed in the registry (planned)

Open standards development

Defines how any participant proposes, debates, versions and adopts a Nexus Standard: the standards track from the Open to the Adopted stage, chartered working groups, consensus with recorded dissent, horizontal reviews, two independent implementations before adoption, OWFa 1.0 patent commitments and CC BY 4.0 text. Each artifact of the area carries a UNI (Unique Nexus Identifier).

01Overview

Summary

Area recordFoundations and Governance
  1. TierCross-cutting capabilities
  2. Registrylisted in the registry · planned
  3. Nexus StandardsNS-0, NS-13
  4. Open standards6
  5. Data sources3
  6. Couplings3
  7. Last reviewed17 October 2026

Area profile proposed for the Nexus Standards registry.

UNI
NXS-STD-DC-000003
Status
Proposedlisted in the registry · planned · scope STD
Last reviewed
area profile
Cite this page

Nexus Standards (2026). Open standards development: area brief, Foundations and Governance programme. Proposed. https://nexustandards.com/foundations/standards-development-standards/ · UNI NXS-STD-DC-000003. 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 (cross-cutting capabilities). The area profile sets out 4 matters in scope and 2 matters addressed by other areas.

In scope 4

  • Track stages and entry conditions (NS-13)
  • Working-group charters, chairs and decision rules
  • Horizontal reviews: accessibility, internationalisation, privacy, security and accuracy of claims
  • Licensing and IPR of standards text, data and tooling

Out of scope 2

  • Claiming liaison status with any body before it is confirmed
  • National standardisation procedures (handled by national members)

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 Levant and Jordan Valley

The map frames the Levant and Jordan Valley as an example geography for open standards development; 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 IETF Datatracker API and W3C technical reports feed, 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 Levant and Jordan Valley.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 service pipeline

A request reaches the service with an explicit context; inputs are identified (NS-1) and validated against RFC 6852 Affirmation of the Modern Paradigm for Standards (OpenStand); the service processes them and writes records with provenance; results are published, resolved and monitored, and a correction flows back through the same path. Nexus Standards applied: NS-0, NS-13. 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 (11). Records and artifacts are cited by UNI (Unique Nexus Identifier) and version.

Process · the service pipeline8 operations · 5 phases
Open standards development: the service pipelineA request reaches the service with an explicit context; inputs are identified (NS-1) and validated against RFC 6852 Affirmation of the Modern Paradigm for Standards (OpenStand); the service processes them and writes records with provenance; results are published, resolved and monitored, and a correction flows back through the same path. Nexus Standards applied: NS-0, NS-13.
All operations in order (8)
  1. 01

    Request start · Request

    The service covers: Track stages and entry conditions (NS-13), Working-group charters, chairs and decision rules and Horizontal reviews: accessibility, internationalisation, privacy, security and accuracy of claims.

    Who
    a client, a person or a machine
    Decision rule
    the context is explicit in the request or on the record, never inferred
    Record
    a request naming its context and inputs
    Implements
    NS16-R20
  2. 02

    Identify inputs step · Request

    Every input is resolved before it is used; an unresolved input is a typed refusal.

    Who
    the service
    Decision rule
    inputs are cited by UNI and version
    Record
    inputs resolved to their UNIs and versions
    Implements
    NS1-R5, NS2-R2, NS0-P12
  3. 03

    Validate RFC 6852 gate · Validation

    Open standards of this area: RFC 6852 Affirmation of the Modern Paradigm for Standards (OpenStand), RFC 2026 The Internet Standards Process, W3C Process Document and OGC Technical Committee Policies and Procedures.

    Who
    the service's validator
    Decision rule
    validated against the open standard's own schema or validator where one exists
    Record
    a validation run against RFC 6852 Affirmation of the Modern Paradigm for Standards (OpenStand) and RFC 2026 The Internet Standards Process
    Implements
    NS14-R2
  4. 04

    Process model · Processing

    Processing is reproducible from the inputs, the method version and the configuration.

    Who
    the service
    Decision rule
    the method and version are recorded with the result
    Record
    Working-group charters, chairs and decision rules
    Implements
    NS12-R1
  5. 05

    Write records record · Processing

    Results are written append-only; a correction adds a version.

    Who
    the service
    Decision rule
    every result carries what it was derived from
    Record
    result records with provenance and a record UNI
    Implements
    NS0-P7, NS1-R3
  6. 06

    Publish and resolve step · Publication

    Results are discoverable and citable by UNI.

    Who
    the service
    Decision rule
    writes return the allocated UNI; citations resolve
    Record
    results reachable through the resolver, with the X-Nexus-UNI header
    Implements
    NS1-R5, NS2-R5
  7. 07

    Monitor exercise · Monitoring

    Data sources the service reads: IETF Datatracker API, W3C technical reports feed and GitHub releases of the nexus-standards repository. Data sources are listed for reference; live data is displayed once licence review is complete.

    Who
    the monitoring service
    Decision rule
    monitoring records are observations with record UNIs
    Record
    observations of availability, drift and SDG 17.6.1
    Implements
    NS11-R4
  8. 08

    Correction end · Monitoring

    Products that used a corrected record are listed and recomputed.

    Who
    the data steward
    Decision rule
    a correction never overwrites; dependent results are replayed
    Record
    a correction record that reaches every dependent result
    Implements
    NS1-R3, NS2-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: RFC 6852 Affirmation of the Modern Paradigm for Standards (OpenStand) · RFC 2026 The Internet Standards Process · NS-0: Constitution and principles · NS-13: Standards development process.

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.

06The track

The Nexus development track (NS-13)

Canvas · the Nexus track, NS-13Process diagram · 10 operations
The Nexus development track: from an open area to an adopted standard (NS-13)An area is opened; a chartered working group drafts in public; horizontal reviews and a public last call precede the proposed stage; two independent implementations precede the candidate stage; adoption is a recorded decision of the Global Standards Council (GSC); a later edition takes its place, or a decision withdraws it. The diagram shows the process as specified; it does not report the status of any standard, proposal or record.
All operations in order (10)
  1. 01

    Open area start · Open area

    The registry lists the area and its programme page invites participation. A working group may be chartered under NS-13.

    Who
    any participant; area listed in the registry
    Decision rule
    an area is open when the registry lists it and no working group has been chartered
    Record
    programme page with a call for participation
  2. 02

    Working group step · Working group

    The charter is public and states the scope, exclusions, deliverables, meeting schedule and decision rule. Drafts, issues and comments are public.

    Who
    chairs from two organisations
    Decision rule
    consensus with recorded dissent; two co-chairs from different organisations
    Record
    public charter
  3. 03

    Community draft record · Working group

    Drafts, issues and comment dispositions are public artifacts, each with a UNI (Unique Nexus Identifier). The chairs record each objection with its disposition.

    Who
    working group editors
    Decision rule
    every normative statement gets an NS-10 clause; every draft carries a UNI
    Record
    drafts with UNIs
  4. 04

    Horizontal reviews gate · Working group

    Each review group reads the whole draft and records findings; a finding is dispositioned in writing before the public last call opens.

    Who
    five review groups
    Decision rule
    accessibility, internationalisation, privacy, security and accuracy of claims, reviewed before last call
    Record
    review findings on record
  5. 05

    Public last call gate · Public

    The draft, its crosswalk rows with source links, its clauses and its test suite are published for comment. Consensus with recorded dissent; a formal objection is answered in writing; appeals go to the Technical Management Division (technical) or the independent panel (process).

    Who
    any person, with identity recorded
    Decision rule
    at least thirty days (fourteen for errata, ninety for a new standard); each comment answered in writing
    Record
    comments and dispositions
  6. 06

    Proposed record · Public

    The standard is proposed and available for voluntary use by implementers ahead of adoption.

    Who
    working group
    Decision rule
    entered when last call has closed and every comment has a disposition
    Record
    proposed edition
  7. 07

    Two implementations gate · Implementation

    Implementers run the Apache-2.0 test suite and publish their results by reference; the working group collects the final specification agreements.

    Who
    two independent implementers
    Decision rule
    two independent implementations pass the open test suite; the results serve as implementation evidence
    Record
    test results as evidence
  8. 08

    Candidate record · Implementation

    The implementation report names the implementations, the suite version and the instant of each run.

    Who
    working group
    Decision rule
    entered when the implementation report is published
    Record
    implementation report
  9. 09

    Adopted decision · Global Standards Council

    A permanent edition with a dated edition identifier; the errata process remains open; systematic review takes place every three years.

    Who
    the Global Standards Council (GSC)
    Decision rule
    a recorded decision of the GSC after last call
    Record
    dated edition with a decision reference
  10. 10

    Later edition or withdrawal end · Global Standards Council

    The record is retained and points to its successor. Earlier editions remain unchanged.

    Who
    a later edition or a withdrawal decision
    Decision rule
    identifiers are permanent and are not reused (NS1-R3)
    Record
    record retained, supersededBy set

Fig.An area is opened; a chartered working group drafts in public; horizontal reviews and a public last call precede the proposed stage; two independent implementations precede the candidate stage; adoption is a recorded decision of the Global Standards Council (GSC); a later edition takes its place, or a decision withdraws it. Sources: NS-13: development process · Nexus Standards operating model.

Develop a standard: lifecycle console and development processes compared

07Nexus Standards

Applicable Nexus Standards

The area profile lists 2 Nexus Standards; the registry lists NS-0, NS-13 for this area. Each is a proposed standard under development.

  1. 01

    NS-0 · Constitution and principles

    Status: proposed · 12 requirements stated. Read NS-0 · Requirements for this area

  2. 02

    NS-13 · Standards development process (open proposals, review, versioning, adoption)

    Status: proposed · 5 requirements stated. Read NS-13 · Requirements for this area

08System model and scenario simulator

System model and cascade scenario: Open standards development

A system model of this area built from the registry: 4 systems, 4 sectors, 4 controls, 3 feeds, 2 indicators. 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-0 Constitution and principles
  • NS-13 Standards development process (open proposals, review, versioning, adoption)
  • NRS-I4 Research evidence, reproducibility and open science
  • NRS-U6 Universe platform profile: Development Finance Nexus

Observation

  • IETF Datatracker API (listed for reference)
  • W3C technical reports feed (listed for reference)
  • GitHub releases of the nexus-standards repository (listed for reference)
  • Fixed Internet broadband subscriptions per 100 inhabitants (participation context)
  • Adequate implementation experience, normally two independent implementations of each feature, before Recommendation
11Systemic couplings

Systemic couplings

3 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
Open standards development: systemic couplingsSystemic couplings of Open standards development as stated in the area profile: 1 area in Foundations and Governance, 1 area in other programmes and 2 programmes 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. Conformance test suitesTrust, Verification and AssuranceA standard cannot enter the Proposed stage without a test suite, or the Candidate stage without two independent implementations that pass it.
  2. Naming, marks and intellectual propertyFoundations and GovernanceContribution agreements (OWFa 1.0, DCO 1.1) and the licence set determine what may be accepted and published.
  3. Communities, Learning and ContributionCommunities, Learning and ContributionWorking groups and chapters in the Communities, Learning and Contribution programme are the bodies that move drafts along the track.
12Data sources

Data sources

3 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
3
licence terms to be recorded
Delivery
0 governed service · 1 plugin · 0 browser · 2 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
14Restricted 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.

15Working group

Working group charter

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

Scope

Maintain the process standard, its charters and its horizontal reviews.

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. NS-13 edition
  2. Working-group charter template
  3. Horizontal review checklists
Liaison targets · 3
  • W3C Community Groups programme liaison sought
  • Research Data Alliance liaison sought
  • Standards Council of Canada liaison sought
16Readiness

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 cites only adopted editions as normative and identifies proposed editions as drafts in its evidence.

Read the evidence pathway

Recognition pathway

The Global Risks Forum (GRF)

GRF recognises contributions to working groups on the public record of drafts, comments and dispositions.

Read the recognition pathway

Capital pathway

The Global Risks Alliance (GRA)

GRA relies on an edition only once its status and dated edition identifier are recorded in the register.

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.

17Research questions

Open research questions

2 questions identified as priorities for the working group.

  1. Balancing open participation with capture risk by well-resourced members.
  2. Running consensus fairly across time zones and languages with volunteer chairs.
18Audiences

Intended users

The area profile identifies 4 user communities.

  1. Standards developers and editors
  2. Working-group chairs
  3. Policy makers
  4. Researchers in standards governance
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.

Sectors 0

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

20Registry

Registry listing and depth pages

This area is listed in the registry (status: planned; scope STD; 2 crosswalk domains). It has five depth pages and a register crosswalk of its domains.

Crosswalk graph · open standards developmentNexus Standards registry
Open standards development: crosswalk to external standards42 nodes on four orbits (Nexus Standards and implementing repositories at the centre, then domains, external standards and issuing bodies), joined by 46 recorded relations.
Nexus StandardsDomainsExternal standardsIssuing bodiesImplementing repositories

2 Nexus Standards · 2 domains · 21 external standards · 17 issuing bodies · 0 implementing repositories. Relations (adopt, profile, crosswalk, cite) are as recorded in the register; names and standards remain with their stewards.

Crosswalk graph42 nodes and 46 links from the registry of external standards, programme areas and implementations (registry/external-standards.yaml, registry/consumers.yaml. Relations (adopt, profile, crosswalk, cite) are shown as recorded in the register.

Areas carry no geography of their own; the map shows where the bodies that issue the area's external standards are based.

Standards globe · Open standards development: issuing bodiesNexus Standards registry
Seats of the bodies that issue the external standards in the registerA plate carrée world map with Natural Earth coastlines, H3 resolution 2 hexagons at the public seats of 15 issuing bodies and one dot per seat. 21 register entries.
Issuing bodies' seats (15)H3 cells, resolution 2 (6); darker, more register entriesProgrammes, repositories and standards: not mapped
Issuing bodies and their seats (15)
BodySeatRegister entries
ISO/CASCOGeneva, Switzerland2
Open Source InitiativePalo Alto, California, United States2
W3CCambridge, Massachusetts, United States2
World Wide Web ConsortiumCambridge, Massachusetts, United States2
Creative CommonsMountain View, California, United States1
European Parliament and CouncilBrussels, Belgium1
IAB, IEEE-SA, IETF, Internet Society, W3CCambridge, Massachusetts, United States1
IETFWilmington, Delaware, United States1
IETF TrustWilmington, Delaware, United States1
ISO and IECGeneva, Switzerland1
OASIS OpenWoburn, Massachusetts, United States1
Open Geospatial ConsortiumArlington, Virginia, United States1
Open Knowledge FoundationLondon, United Kingdom1
SPDX Legal Team (Linux Foundation)San Francisco, California, United States1
UK Cabinet OfficeLondon, United Kingdom1

Issuing bodies are shown at the city of their public seat. The 1 programmes, 0 implementing repositories and 19 Nexus Standards have no location and are not mapped · 2 issuing bodies have no single public seat and are listed without a location: World Trade Organization; Free Software Foundation Europe

Standards globe15 issuing bodies with a public seat and 21 register entries, shown on H3 cells at resolutions 1 to 4. Seats are placed at city coordinates; programme areas, implementations and standards have no location and are not drawn. A static plate carrée map is shown where scripts are unavailable.

21Sources

Sources

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

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 termsstandards development; standardization process; open standards; W3C Process DocumentDerived 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.

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 ReportsPublishes versioned reports with a public corrections policy, a working model of recorded revision.Apply to this programme therisk.globalAll programmes of GCRI Canada

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
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.
cite
Relation in which the external standard is cited by identifier and URL as a reference.
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: standards development; standardization process; open standards. With JavaScript enabled, recent works matching these terms are listed from OpenAlex and Crossref.

28Questions

Questions and answers.

What is the status of the Open standards development area?
The area profile is a proposal to the Nexus Standards registry, and the area is 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
Nexus Standards

Contribute to Open standards development

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.

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