Skip to content
StandardsOpen Infrastructure and DevelopersAudiences
Area · proposed

For developers

The developer entry area of the Open Infrastructure and Developers programme is written for software engineers in every community who need schemas, a resolver, a command-line tool and a verification API that they can implement without seeking permission: deployment guidance, a test environment, the planned software development kits, the monitoring cycle and the STAC package, with supply-chain integrity requirements throughout. Each artefact of the area carries a UNI (Unique Nexus Identifier).

For developers
What this area is built from: the Nexus Standards it applies, the open standards it names and the data and feeds it reads, then the areas its record couples it with (marked).Source: the Nexus Standards registry: the area record.
  • Nexus Standards: NS-1, NS-3, NS-3b, NS-11, NS-12.
  • Open standards: OpenAPI Specification 3.1; JSON Schema 2020-12; SpatioTemporal Asset Catalog (STAC) 1.0; Supply-chain Levels for Software Artifacts (SLSA) 1.1; Sigstore signing and transparency log; SPDX; OpenID Connect Core 1.0 on OAuth 2.0.
  • Data and feeds: World Development Indicators; USGS earthquake GeoJSON summary feeds.
  • Couples with: Developers and APIs; Sandbox and simulated data; Software and supply chain; Conformance programme.
Nexus Standards
5
NS-1, NS-3, NS-3b
Open standards
7
named, never copied
Data and feeds
2
listed for reference
Couplings
4
with other areas
UNI
requested · allocation in progress
Imeko
Proposednot yet in the catalogue
Last reviewed
area profile
Cite this page

Nexus Standards (2026). For developers: area brief, Open Infrastructure and Developers programme. Proposed. https://nexustandards.com/open-infrastructure/for-developers/. 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.

01Ubungakanani bomsebenzi

Scope and boundaries

An area of the Open Infrastructure and Developers programme (audiences). The area profile sets out 5 matters in scope and 3 matters addressed by other areas.

In scope 5

  • A path through deployment guidance, the test environment, the planned software development kits, the monitoring cycle and the STAC package
  • Schemas (JSON Schema 2020-12) and OpenAPI 3.1 descriptions
  • The UNI resolver and X-Nexus-UNI header
  • Signing, SBOM and provenance for releases
  • Running conformance tests in continuous integration

Out of scope 3

  • Hosted services or support contracts
  • Proprietary SDKs
  • Production readiness claims for any implementation

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

02Entry point

Where developers start in the registry.

Imigangatho yangaphandle

External standards in these domains

46 external standards referenced for these domains.

UmgangathoIqumrhuRelationUkufikelela
NIST SP 800-207 Zero Trust ArchitectureNISTadoptvula
CISA Zero Trust Maturity Model Version 2.0CISA (US Cybersecurity and Infrastructure Security Agency)profilevula
OAuth 2.0 (RFC 6749) and OpenID Connect Core 1.0IETF and OpenID Foundationadoptvula
SPDX (System Package Data Exchange) specification; ISO/IEC 5962:2021SPDX project (Linux Foundation); ISO/IEC JTC 1adoptvula
CycloneDX Bill of Materials specification (ECMA-424)OWASP CycloneDX; Ecma International TC54crosswalkvula
OpenSSF Best Practices BadgeOpenSSFcitevula
OpenSSF ScorecardOpenSSFcitevula
SoftWare Hash IDentifier (SWHID) Specification V1.2; ISO/IEC 18670:2025Software Heritage; ISO/IEC JTC 1adoptvula
CodeMeta software metadata vocabularyCodeMeta projectadoptvula
Citation File Format (CITATION.cff)Citation File Format projectadoptvula
OpenAPI SpecificationOpenAPI Initiative (Linux Foundation)adoptvula
JSON Schema 2020-12JSON Schema organisationadoptvula
Schema.org vocabularySchema.org Community Group (W3C)adoptvula
Statistical Data and Metadata eXchange (SDMX); ISO 17369:2013SDMX sponsors (BIS, ECB, Eurostat, IMF, OECD, UN, World Bank); ISO/TC 154crosswalkvula
FAIR Guiding Principles for scientific data management and stewardshipWilkinson et al. 2016; GO FAIRadoptvula
CARE Principles for Indigenous Data GovernanceGlobal Indigenous Data Allianceadoptvula
W3C Data Catalog Vocabulary (DCAT) – Version 3W3C Dataset Exchange Working Groupadoptvula
W3C Decentralized Identifiers (DIDs) v1.0W3C DID Working Groupprofilevula
DataCite Metadata Schema 4.5DataCite Metadata Working Groupadoptvula
Digital Object Identifier system – ISO 26324ISO/TC 46/SC 9; International DOI Foundationcompatibility profile (restricted)paywalled
ORCID iD (subset of ISNI, ISO 27729)ORCID Inc.adoptvula
International Standard Name Identifier (ISNI) – ISO 27729ISO/TC 46/SC 9; ISNI International Agencycitepaywalled
Research Organization Registry (ROR)ROR (California Digital Library, Crossref, DataCite)adoptvula
Croissant: A Metadata Format for ML-Ready DatasetsMLCommons Croissant Working Groupcrosswalkvula
Datasheets for DatasetsGebru et al. (arXiv 2018; Communications of the ACM 2021)profilevula
ISO 8601-1:2019 Date and time – Representations for information interchange – Part 1: Basic rulesISO/TC 154adoptpaywalled
ISO 3166-1 Codes for the representation of names of countries and their subdivisions – Part 1: Country codesISO/TC 46; ISO 3166 Maintenance Agencyadoptfree-to-read
UN M49 Standard country or area codes for statistical useUnited Nations Statistics Divisionadoptvula
ISO/IEC 30173:2023 Digital twin – Concepts and terminologyISO/IEC JTC 1/SC 41compatibility profile (restricted)paywalled
ISO 23247 Automation systems and integration – Digital twin framework for manufacturingISO/TC 184citepaywalled
ISO/IEC 22123 Information technology – Cloud computingISO/IEC JTC 1/SC 38citepaywalled
Semantic Sensor Network Ontology (SOSA/SSN)W3C and OGCadoptvula
IEEE 1451 Smart transducer interface standardsIEEEcitepaywalled
Handbook on Constructing Composite Indicators (OECD and JRC) and JRC composite indicator guidanceOECD and European Commission JRCadoptvula
ISO 22739 Blockchain and distributed ledger technologies – VocabularyISO/TC 307citepaywalled
Global indicator framework for the Sustainable Development GoalsUN Statistical Commissioncrosswalkvula
Open Badges 3.01EdTech Consortiumadoptvula
ESCO European Skills, Competences, Qualifications and OccupationsEuropean Commissioncrosswalkvula
OWL 2 Web Ontology LanguageW3Cadoptvula
SKOS Simple Knowledge Organization System ReferenceW3Cadoptvula

A further 6 are listed on the crosswalk pages of the areas above.

Tools

Tools and records

Implementation status as recorded in the registry for each implementation.

UkuphunyezwaIndimaStandards for this community
IrekhodiTitleImeko
NXS-STD-ST-000001Nexus Standards NS-1 – the UNI and artefact catalogueuyilo lokuqala
NXS-STD-SW-000002UNI command-line tool (validate, parse, next, mint, catalogue, export) – reference implementationuyilo lokuqala
NXS-STD-SC-000001UNI artefact record schema v1uyilo lokuqala
NXS-STD-ST-000002Open-standards and open-source stack under the UNIuyilo lokuqala
NXS-STD-SW-000005UNI data profile (STAC, DCAT, PROV-O crosswalks), NS-3buyilo lokuqala
NXS-STD-ST-000003Nexus Standards NS-3 – risk record UNIs (grammar, legacy crosswalk, allocation authority)uyilo lokuqala
NXS-STD-ST-000012Nexus Standards NS-12 – software, models and AI/ML artefactsuyilo lokuqala

Resources and tooling

03Inkqubo yokusebenza

The participation pathway

Software engineers, Data engineers and Platform operators find the area and its open drafts, take part without a membership fee, comment in the open, join a working group, propose text and see each comment answered in writing; accepted work becomes a version, and national adoption is decided by each 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 (8). Records and artefacts are cited by UNI (Unique Nexus Identifier) and version.

Umhloli weenkqubo · Standards · ukuchaza nokulungisa

Umjikelo wobomi bomgangatho

Amanyathelo ali-17Izigaba ezi-6

Standards · ukuchaza nokulungisa

Umjikelo wobomi bomgangatho

Umjikelo wobomi bomgangatho · Indlela ye-NS-13 · Iindlela zokunikela · Indlela ye-IETF · Indlela ye-W3C · Indlela ye-OGC · Indlela ye-OASIS · Izigaba ze-ISO ne-IEC · Ukuhambelana · Umjikelo wobomi werekhodi · Ukuthumela · Ukubeka iliso.

Iziphumo zomjikelo ziba ziziphakamiso zotshintsho, iBhunga leMigangatho yeHlabathi liyamkela emva komnxeba wokugqibela woluntu, kwaye ilizwe ngalinye ligqiba ukwamkela kwalo.

  1. 01 Thumela iimishini

    1. 01Route missions to standards and profilesStep · Nexus StandardsNexus Standards routes each candidate mission to the standards and profiles that apply.
  2. 02 Iiprofayile nokuhambelana

    1. 02Qamba iiprofayile zeemishiniInyathelo · Nexus StandardsI-Nexus Standards iqamba iiprofayile zeemishini kwaye ibhale nakuphi na ukwamkelwa kwesizwe iimishini ezixhomekeke kuko.
    2. 03Qinisekisa iziphumo zokwakha ngokwamaprofayileInyathelo · Nexus StandardsI-Nexus Standards iqinisekisa iziphumo zokwakha ngokwamaprofayile aqanjiweyo kwaye ibhale ubungqina.
    3. 04Beka iliso kukuhambelana uze ubhale ubungqina obutywiniweyoInyathelo · Nexus StandardsNgexesha leVeki yeNtshukumo i-Nexus Standards ibeka iliso kukuhambelana kwaye ibhale ukuphambuka.
  3. 03 Iziphakamiso nophononongo

    1. 05Ukuphambuka nolungiso ziba ziziphakamiso zotshintshoInyathelo · Nexus StandardsUkuphambuka kuba ziziphakamiso zotshintsho, kwaye ulungiso lubhalwa njengotshintsho kubungqina.
    2. 06Iziphumo zomjikelo ziba ziziphakamiso zotshintshoInyathelo · Nexus StandardsIziphumo zomjikelo ziba ziziphakamiso zotshintsho: iziphumo zendlela nezolungiso ezivela Iingxelo (F06) nezinto zedokethi ezivela kwi-Nexus…
    3. 07Yila uze uhlaziye ekuhleniInyathelo · Iikomiti namaqela asebenzayoIikomiti zobugcisa namaqela asebenzayo ayila kwaye ahlaziye imigangatho kwinkqubo evulekileyo ye-NS-13.
    4. 08Uphononongo olusingise kwisigqibo sebhungaInyathelo · Nexus StandardsI-Nexus Standards ihambisa iziphakamiso zotshintsho kuphononongo zisingise kwisigqibo sebhunga.
  4. 04 Isigqibo sebhunga

    1. 09Umnxeba wokugqibela woluntuInyathelo · IBhunga leMigangatho yeHlabathiIBhunga leMigangatho yeHlabathi liyamkela ngesininzi sesibini kwisithathu emva komnxeba wokugqibela weentsuku ezingamashumi alithoba.
    2. 10Ukwamkelwa kwehlabathi komgangathoIsigqibo · IBhunga leMigangatho yeHlabathiIBhunga leMigangatho yeHlabathi ligqiba ukwamkelwa komgangatho ngamnye emva komnxeba wokugqibela woluntu.
  5. 05 Papasha uze uchonge

    1. 11Assign a UNI and publishStep · Secretariat (GCRI Canada)Nexus Standards assigns UNIs and deposits publications under the publisher’s process.
    2. 12I-UNI iyachonga kwaye ayize iqinisekiseIrekhodi · Nexus StandardsYonke into yonyaka wenkqubo ithwele isichongi esinye, i-UNI phantsi kwe-NS-1, ukuze icatshulwe, inikwe iinguqulelo kwaye isonjululwe.
    3. 13Papasha utshintsho olwamkelweyo lonyakaInyathelo · Nexus StandardsEkuhlaziyweni i-Nexus Standards ipapasha utshintsho olwamkelweyo lonyaka nemeko yokwamkelwa kwesizwe.
  6. 06 Ukwamkelwa nokusetyenziswa kwesizwe

    1. 14Ukwamkelwa kwesizwe liBhunga leMigangatho leSizweIsigqibo · IBhunga leMigangatho leSizweIBhunga leMigangatho leSizwe lelizwe ngalinye ligqiba ukwamkelwa kwesizwe: yamkela njengoko injalo, yamkela ngeprofayile (NS-16), lungelelanisa, okanye bhekisa kuphela.
    2. 15Imigangatho eyamkelweyo ifikelela kwizifundo nakwiinguquleloInyathelo · Nexus StandardsUmgangatho ngamnye owamkelweyo okanye iprofayile iba yimodyuli yekhosi kwi-Risk Academy (F09), kwaye imigangatho isetyenziswa kwiinguqulelo ze-Reports (R1).
    3. 16Ukwamkelwa kugqibelele kummandla wolawulo ngamnyeUmgangatho · IBhunga leMigangatho leSizweUkwamkelwa kugqibelele kummandla wolawulo ngamnye, kwaye i-GSC ayinalo ilungelo lokuvala isigqibo sesizwe. Akukho qumrhu lehlabathi linelungelo lokuvala.
    4. 17Iirekhodi zokwamkelwa kwesizweIrekhodi · Nexus StandardsIiprofayile zeemishini eziqanjiweyo neerekhodi zokwamkelwa kwesizwe ziya kwi-Foundry ngexesha lokulungiselela ukulungela (F08).

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

The operations, as a table
Process · the participation pathway8 operations · 5 phases
InyatheloPhaseUkusebenzaWhoDecision ruleIrekhodiImplements
01DiscoveryFind the area (start). Learning pathways and calls are linked from the area. The developer entry area of the Open Infrastructure and Developers programme is written for software engineers in every community who need schemas, a resolver, a command-line tool and a verification API that they can implement without seeking permission: deployment guidance, a test environment, the planned software development kits, the monitoring cycle and the STAC package, with supply-chain integrity requirements throughout..Software engineers, Data engineers and Platform operatorsstandards, registries and schemas are published openlythe area page, its drafts and its callsNS0-P1
02DiscoveryRead the drafts (step). Nexus Standards of this area: NS-1, NS-3, NS-3b, NS-11, NS-12.the participantdrafts carry UNIs and are cited by versionthe current drafts with their UNIsNS2-R2
03JoiningJoin (step). No membership fee is required; agents take part under a recorded mandate.the participantparticipation is open and free; identity is recordedan identity recorded with ORCID or RORNS13-R2
04CommentComment (record). Accepted, rejected, deferred or open: each disposition is written.the participanteach comment receives a disposition with a reasona comment in the open record of a proposalNS13-R2
05CommentWorking group (step). Deliverables: Developer learning path with the STAC package as worked example, Reference command-line tool and schema examples and Continuous-integration template for running conformance tests.the working group chairsconsensus with recorded dissent; two co-chairs from different organisationsCurate the developer path, maintain reference tools and examples, and triage implementer issues.NS13-R2
06ProposalPropose text (gate). Last call is announced to every stakeholder group listed on the proposal.the participant or the working groupevery change enters through a proposal; objections are dispositioned before acceptancea proposal with a UNI, through last callNS13-R1, NS13-R3
07AdoptionNew version (record). Contributors are credited; agents are credited as agents.the editorseditors decide in writing; they do not adopta semantic version crediting contributorsNS13-R4, NS13-R5, NS2-R3
08AdoptionAdoption (end). The GSC has no veto over a national decision.the GSC; in each country the NSCnational adoption is a national decisionadoption by the Global Standards Council (GSC); national decisions by each NSCNS13-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: OpenAPI Specification 3.1 · JSON Schema 2020-12 · NS-1: The UNI and the artefact catalogue · NS-3: Risk record UNIs.

04Alignment

From frameworks and sources to the applicable standards

Read from left to right; select or focus an item to trace its connections.

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

05Audiences

Intended users

The area profile identifies 4 user communities.

  1. Software engineers
  2. Data engineers
  3. Platform operators
  4. Open-source maintainers
06System model

How a shock travels through this system

A system model of this area built from the registry: 5 systems, 4 sectors, 11 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.

Izilawuli

  • NS-1I-UNI nekhathalogu yezinto (igrama v0.2: amacandelo enkalo, ecandelo, ommandla nokusingqongileyo)
  • NS-3 Ii-UNI zerekhodi yomngcipheko (igrama, uthelekiso lwakudala, igunya lokwabiwa)
  • NS-3b Iprofayile yemetadata yeseti yedatha neyemveliso (STAC, DCAT, PROV-O)
  • NS-11 Ukuqinisekiswa nokubekwa kweliso (ubungqina, iziqinisekiso, uqwalaselo lokuhambelana ngaphandle kokuthemba)
  • NS-12 Isoftwe, imodeli nezinto ze-AI/ML (ityathanga lobonelelo, amakhadi eemodeli, amaphepha eeseti zedatha)
  • NRS-C11 Ukuhambelana, ukuqinisekisa nokugcinwa kwemigangatho
  • NRS-S5 System profile: NXS-NXQ (Software, models and capability lifecycle)
  • NRS-A1 Imigangatho njengekhowudi: imigangatho efundeka ngoomatshini, iimfuno novavanyo
  • NRS-S8 System profile: NXS-EWS (Multi-hazard monitoring and warning)
  • NRS-T8 Umngcipheko wokuthembeka kwesoftware nekhonkco lobonelelo
  • NRS-A6 Iikhithi zokusebenzisa nokwamkela ngokucofa kanye

Uqwalaselo

  • World Development Indicators (listed for reference)
  • USGS earthquake GeoJSON summary feeds (listed for reference)
  • Proportion of individuals using the Internet
07Imigangatho

Imigangatho esebenzayo

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

  1. 01

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

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

  2. 02

    NS-3 · Risk record UNIs (grammar, legacy crosswalk, allocation authority)

    Status: proposed · 0 requirements stated. Read NS-3.

  3. 03

    NS-3b · Dataset and product metadata profile (STAC, DCAT, PROV-O)

    Status: proposed · 0 requirements stated. Read NS-3b.

  4. 04

    NS-11 · Verification and monitoring (evidence, attestations, zero-trust conformance observation)

    Status: proposed · 6 requirements stated. Read NS-11.

  5. 05

    NS-12 · Software, model and AI/ML artefacts (supply chain, model cards, dataset sheets)

    Status: proposed · 4 requirements stated. Read NS-12.

10Ukudibana kweenkqubo

Ukudibana kweenkqubo

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

  1. Developers and APIsOpen Infrastructure and DevelopersThe developer and API area documents the schemas, resolver and APIs this path starts from.
  2. Sandbox and simulated dataOpen Infrastructure and DevelopersDevelopers test against synthetic data and conformance suites in the test environment.
  3. Software and supply chainTrust, Verification and AssuranceReleases must carry signatures, SBOMs and provenance attestations under NS-12.
  4. Conformance programmeReadiness and AdoptionDevelopers publish implementation conformance statements for their implementations.
11Ukulungela

Evidence, recognition and capital pathways

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

Evidence pathway

GCRI Canada

Developers learn how their implementations produce records that the GCRI Canada evidence pathway can read; GCRI Canada decides admissibility.

Read the evidence pathway

Indlela yokwamkelwa

I-Global Risks Forum (GRF)

Developers see how an implementation’s conformance statements contribute to a programme’s trail that GRF may consider under its own rules.

Read the recognition pathway

Indlela yemali

I-Global Risks Alliance (GRA)

Developers see how verifiable records from their tools can be cited in GRA files; GRA decides 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.

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

Ngoku
0
on completion of licence review
Listed in the data register
2
licence terms recorded
Proposed for the register
0
licence terms to be recorded
Delivery
2 governed service · 0 plugin · 0 browser · 0 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
13Izalathisi

Izalathisi

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

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

14Iqela elisebenzayo

Working group charter

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

Ubungakanani bomsebenzi

Curate the developer path, maintain reference tools and examples, and triage implementer issues.

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. Developer learning path with the STAC package as worked example
  2. Reference command-line tool and schema examples
  3. Continuous-integration template for running conformance tests
Liaison targets · 4
  • OpenAPI Initiative liaison sought
  • STAC community liaison sought
  • OpenSSF liaison sought
  • JSON Schema organisation liaison sought
15Research questions

Open research questions

3 questions identified as priorities for the working group.

  1. Reference tools must stay small while covering many profiles.
  2. Conformance tests need stable fixtures that do not reproduce licensed data.
  3. Supply-chain requirements add friction for small projects.
16Restricted standards

Restricted compatibility profiles

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

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

17Hazards and sectors

Hazards, threats and sectors concerned

Hazards and threats 0

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

Amacandelo 0

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

18Imithombo

Imithombo

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

  1. peer-reviewedModel cards for model reportingProceedings of the Conference on Fairness, Accountability, and Transparency (ACM) · 2019
  2. peer-reviewedThe FAIR Guiding Principles for scientific data management and stewardshipScientific Data · 2016
  3. officialSecure Software Development Framework (SSDF) Version 1.1 (NIST SP 800-218)NIST · 2022
  4. officialZero Trust Architecture (NIST SP 800-207)NIST · 2020
19Research 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 termsresearch software; open source software; web API; software engineering; OpenAPI Specification; JSON Schema 2020-12Derived 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.

21Kuyo yonke inethiwekhi

Programmes, tracks and courses for this area

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

Governance, policy and convening

I-Global Risks Forum (GRF)

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

AI and Digital GovernanceExamines digital dependence and the governance of public infrastructure.Join this track globalriskforum.comAll tracks of The Global Risks Forum

Capital, finance and markets

I-Global Risks Alliance (GRA)

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

Fintech NexusExamines open finance and application interfaces in financial services.Join this programme globalriskalliance.comAll programmes of The Global Risks Alliance
22Amagama aphambili

Amagama aphambili

UNI
Unique Nexus Identifier: a persistent identifier that resolves an artefact to its record.
kuphakanyisiwe
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.
24Uphando

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: research software; open source software; web API; software engineering. With JavaScript enabled, recent works matching these terms are listed from OpenAlex and Crossref.

25Imibuzo

Imibuzo neempendulo.

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

Faka ubungqina obuvela kweli phepha.

I-Reports lupapasho lwekota lweConsortium. Oko ukwaziyo ngalo mxholo kunokuba bubungqina, imeko okanye ulungiso kuhlelo olulandelayo, kubongwe wena kwaye kupapashwe phantsi kwe-CC BY 4.0 apho ingumsebenzi wakho.

Nexus Standards
Imigangatho

Contribute to For developers

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.

Imeko nokusetyenziswa. I-Nexus Standards yimigangatho ecetywayo ephuhliswe ngenkqubo evulekileyo phantsi kwe-NS-13 kwaye ipapashelwe ukusetyenziswa ngokuzithandela; ayisiso isatifikethi, ugunyaziso okanye imvume yolawulo, kwaye ukwamkelwa kuhlala kusisigqibo seBhunga leMigangatho yeHlabathi kwaye, kwilizwe ngalinye, seBhunga lalo leMigangatho leSizwe. I-UNI (Unique Nexus Identifier) ichonga into; ayiyiqinisekisi. Amagama amaqumrhu emigangatho nemigangatho yawo ngawabagcini bawo kwaye asetyenziswa kuphela ukuchonga amaxwebhu; akukho mbhalo womgangatho wangaphandle uphindwe apha. I-Nexus Standards ayidibananga, ayixhaswanga okanye ayiqinisekiswanga nguwuphi na umbutho wemigangatho okhankanywe apha.

Iilayisenisi: CC BY 4.0 yombhalo wemigangatho, iirejista, iischema nedatha; Apache-2.0 yekhowudi yereferensi. Imigangatho yangaphandle icatshulwa ngegama, inombolo nekhonkco phantsi kweelayisenisi zayo. Idatha yamaqela esithathu, iilayibrari neefonti zigcina iilayisenisi zazo: bona iZaziso zamaqela esithathu.