Skip to content
AmazingaIngqalasizinda Evulekile NabathuthukisiAbabukeli
Area · proposed

Kubathuthukisi

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

Kubathuthukisi
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
Isimo
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.

01Ububanzi

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.

Amazinga angaphandle

External standards in these domains

46 external standards referenced for these domains.

IzingaBodyRelationAccess
NIST SP 800-207 Zero Trust ArchitectureNISTadoptvulekile
CISA Zero Trust Maturity Model Version 2.0CISA (US Cybersecurity and Infrastructure Security Agency)profilevulekile
OAuth 2.0 (RFC 6749) and OpenID Connect Core 1.0IETF and OpenID Foundationadoptvulekile
SPDX (System Package Data Exchange) specification; ISO/IEC 5962:2021SPDX project (Linux Foundation); ISO/IEC JTC 1adoptvulekile
CycloneDX Bill of Materials specification (ECMA-424)OWASP CycloneDX; Ecma International TC54crosswalkvulekile
OpenSSF Best Practices BadgeOpenSSFcitevulekile
OpenSSF ScorecardOpenSSFcitevulekile
SoftWare Hash IDentifier (SWHID) Specification V1.2; ISO/IEC 18670:2025Software Heritage; ISO/IEC JTC 1adoptvulekile
CodeMeta software metadata vocabularyCodeMeta projectadoptvulekile
Citation File Format (CITATION.cff)Citation File Format projectadoptvulekile
OpenAPI SpecificationOpenAPI Initiative (Linux Foundation)adoptvulekile
JSON Schema 2020-12JSON Schema organisationadoptvulekile
Schema.org vocabularySchema.org Community Group (W3C)adoptvulekile
Statistical Data and Metadata eXchange (SDMX); ISO 17369:2013SDMX sponsors (BIS, ECB, Eurostat, IMF, OECD, UN, World Bank); ISO/TC 154crosswalkvulekile
FAIR Guiding Principles for scientific data management and stewardshipWilkinson et al. 2016; GO FAIRadoptvulekile
CARE Principles for Indigenous Data GovernanceGlobal Indigenous Data Allianceadoptvulekile
W3C Data Catalog Vocabulary (DCAT) – Version 3W3C Dataset Exchange Working Groupadoptvulekile
W3C Decentralized Identifiers (DIDs) v1.0W3C DID Working Groupprofilevulekile
DataCite Metadata Schema 4.5DataCite Metadata Working Groupadoptvulekile
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.adoptvulekile
International Standard Name Identifier (ISNI) – ISO 27729ISO/TC 46/SC 9; ISNI International Agencycitepaywalled
Research Organization Registry (ROR)ROR (California Digital Library, Crossref, DataCite)adoptvulekile
Croissant: A Metadata Format for ML-Ready DatasetsMLCommons Croissant Working Groupcrosswalkvulekile
Datasheets for DatasetsGebru et al. (arXiv 2018; Communications of the ACM 2021)profilevulekile
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 Divisionadoptvulekile
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 OGCadoptvulekile
IEEE 1451 Smart transducer interface standardsIEEEcitepaywalled
Handbook on Constructing Composite Indicators (OECD and JRC) and JRC composite indicator guidanceOECD and European Commission JRCadoptvulekile
ISO 22739 Blockchain and distributed ledger technologies – VocabularyISO/TC 307citepaywalled
Global indicator framework for the Sustainable Development GoalsUN Statistical Commissioncrosswalkvulekile
Open Badges 3.01EdTech Consortiumadoptvulekile
ESCO European Skills, Competences, Qualifications and OccupationsEuropean Commissioncrosswalkvulekile
OWL 2 Web Ontology LanguageW3Cadoptvulekile
SKOS Simple Knowledge Organization System ReferenceW3Cadoptvulekile

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

Amathuluzi

Tools and records

Implementation status as recorded in the registry for each implementation.

UkuqalisaIndimaStandards for this community
RecordTitleIsimo
NXS-STD-ST-000001Nexus Standards NS-1 – the UNI and artefact cataloguedraft
NXS-STD-SW-000002UNI command-line tool (validate, parse, next, mint, catalogue, export) – reference implementationdraft
NXS-STD-SC-000001UNI artefact record schema v1draft
NXS-STD-ST-000002Open-standards and open-source stack under the UNIdraft
NXS-STD-SW-000005UNI data profile (STAC, DCAT, PROV-O crosswalks), NS-3bdraft
NXS-STD-ST-000003Nexus Standards NS-3 – risk record UNIs (grammar, legacy crosswalk, allocation authority)draft
NXS-STD-ST-000012Nexus Standards NS-12 – software, models and AI/ML artefactsdraft

Izinsiza namathuluzi

03Inqubo

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 wezinqubo · Standards · hlela futhi ulungise

Umjikelezo wempilo wezinga

Izinyathelo ezingu-17Izigaba eziyi-6

Standards · hlela futhi ulungise

Umjikelezo wempilo wezinga

Umjikelezo wempilo wezinga · Indlela ye-NS-13 · Imijelo yeminikelo · Indlela ye-IETF · Indlela ye-W3C · Indlela ye-OGC · Indlela ye-OASIS · Izigaba ze-ISO ne-IEC · Ukuhambisana · Umjikelezo werekhodi · Ukuqondisa · Ukuqapha.

Okutholakele emjikelezweni kuba iziphakamiso zezinguquko, i-Global Standards Council iyamukela ngemva kocingo lokugcina lomphakathi, futhi izwe ngalinye linquma ukwamukela kwalo.

  1. 01 Hambisa imishini

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

    1. 02Hlanganisa amaphrofayili emishiniIsinyathelo · Nexus StandardsI-Nexus Standards ihlanganisa amaphrofayili emishini futhi irekhode noma yikuphi ukwamukelwa kukazwelonke imishini ekuncike kukho.
    2. 03Qinisekisa imiphumela yokwakha ngokuqhathanisa namaphrofayelaIsinyathelo · Nexus StandardsI-Nexus Standards iqinisekisa imiphumela yokwakha ngokumelene namaphrofayela ahlanganisiwe futhi irekhode ubufakazi.
    3. 04Qapha ukuhambisana futhi ubhale ubufakazi obuvalwe ngophawuIsinyathelo · Nexus StandardsPhakathi neSonto Lokwenza i-Nexus Standards iqapha ukuhambisana futhi irekhode ukuphambuka.
  3. 03 Iziphakamiso nokubuyekezwa

    1. 05Ukuchezuka nokulungiswa kuba yiziphakamiso zoshintshoIsinyathelo · Nexus StandardsUkuchezuka kuba yiziphakamiso zoshintsho, futhi ukulungiswa kubhalwa njengoshintsho kubufakazi.
    2. 06Izitholakalo zomjikelezo ziba yizincomo zoshintshoIsinyathelo · Nexus StandardsOkutholakele emjikelezweni kuba iziphakamiso zezinguquko: okutholakele ngezindlela nokulungiswa okuvela ku- Imibiko (F06) nezinto zohlu lwamacala ezivela ku-Nexus…
    3. 07Bhala futhi ubuyekeze obalaIsinyathelo · Amakomidi namaqembu okusebenzaAmakomidi ezobuchwepheshe namaqembu okusebenza abhala futhi abuyekeze amazinga enqubweni evulekile ye-NS-13.
    4. 08Ukubuyekeza kuya esinqumweni somkhandluIsinyathelo · Nexus StandardsI-Nexus Standards ihambisa izicelo zokuguqula ngokubuyekezwa kuya esinqumweni somkhandlu.
  4. 04 Isinqumo somkhandlu

    1. 09Ubizo lokugcina lomphakathiIsinyathelo · Global Standards CouncilI-Global Standards Council iyamukela ngokuvumelana kwabayingxenye emibili kwezintathu ngemva kobizo lokugcina lezinsuku eziyikhulu namashumiayisishiyagalolunye.
    2. 10Ukwamukelwa komhlaba wonke kwezingaIsinqumo · Global Standards CouncilI-Global Standards Council inquma ukwamukelwa kwezinga ngalinye ngemva kocingo lokugcina lomphakathi.
  5. 05 Shicilela futhi uhlonze

    1. 11Assign a UNI and publishStep · Secretariat (GCRI Canada)Nexus Standards assigns UNIs and deposits publications under the publisher’s process.
    2. 12I-UNI iyahlonza futhi ayikaze inikeze isitifiketiIrekhodi · Nexus StandardsYonke into yonyaka wohlelo ithwala isihlonzi esisodwa, i-UNI ngaphansi kwe-NS-1, ukuze icashunwe, ibe nezinguqulo futhi ixazululwe.
    3. 13Shicilela izinguquko ezamukelwe zonyakaIsinyathelo · Nexus StandardsEkuvuselelweni i-Nexus Standards ishicilela izinguquko ezamukelwe zonyaka nesimo sokwamukelwa kazwelonke.
  6. 06 Ukwamukelwa nokusetshenziswa kuzwelonke

    1. 14Ukwamukelwa kuzwelonke nguMkhandlu Wamazinga KazwelonkeIsinqumo · UMkhandlu Wamazinga KazwelonkeI-National Standards Council yezwe ngalinye inquma ukwamukelwa kazwelonke: yamukela njengoba kunjalo, yamukela nephrofayela (NS-16), guqula, noma ukhombe kuphela.
    2. 15Amazinga amukelwe afinyelela ezifundweni nasezinhlelweni eziqoqiweIsinyathelo · Nexus StandardsIzinga ngalinye elamukelwe noma iphrofayili iba yimojula yesifundo e-Risk Academy (F09), futhi amazinga asetshenziswa ezinhlelweni eziqoqiwe ze-Reports (R1).
    3. 16Ukwamukelwa kuyisinqumo sokugcina kwezwe ngalinyeIzinga · National Standards CouncilUkwamukelwa kuyisinqumo sokugcina kwezwe ngalinye, futhi i-GSC ayinalo ilungelo lokuvimba isinqumo sikazwelonke. Alikho ibhodi lomhlaba elinelungelo lokuvimba.
    4. 17Amarekhodi okwamukelwa kazwelonkeIrekhodi · Nexus StandardsAmaphrofayela emishini ahlanganisiwe namarekhodi okwamukelwa kazwelonke aya ku-Foundry ekulungiseleleni 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
StepPhaseOperationWhoDecision ruleRecordImplements
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
07UkwamukelwaNew 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
08UkwamukelwaAdoption (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.

05Ababukeli

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.

Systems and couplings

Controls

  • NS-1I-UNI nekhathalogi yezinto (uhlelo lolimi v0.2: izingxenye zesizinda, umkhakha, isifunda nendawo)
  • NS-3 Ama-UNI amarekhodi obungozi (uhlelo lolimi, ukuqhathanisa nezinhlelo ezindala, igunya lokwabela)
  • NS-3b Iphrofayili yemetadatha yedathasethi nomkhiqizo (STAC, DCAT, PROV-O)
  • NS-11 Ukuqinisekisa nokuqapha (ubufakazi, izifakazelo, ukuqapha ukuhambisana ngaphandle kokwethembana)
  • NS-12 Izinto zesofthiwe, zamamodeli nezama-AI/ML (uchungechunge lokuhlinzeka, amakhadi amamodeli, amashidi amaqoqo edatha)
  • NRS-C11 Ukuhambisana, ukuqinisekisa nokunakekelwa kwamazinga
  • NRS-S5 System profile: NXS-NXQ (Software, models and capability lifecycle)
  • NRS-A1 Amazinga njengekhodi: amazinga, izidingo nezivivinyo ezifundeka ngomshini
  • NRS-S8 System profile: NXS-EWS (Multi-hazard monitoring and warning)
  • NRS-T8 Ubungozi bobuqotho besofthiwe nobochungechunge lokuhlinzeka
  • NRS-A6 Amakhithi okufaka nokwamukela ngokuchofoza kanye

Observation

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

Standards that apply

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.

10Ukuxhumana kwezistimu

Ukuxhumana kwezistimu

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 yokuqashelwa

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 yezimali

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.

Bukhoma
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
13Izinkomba

Izinkomba

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

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

14Iqembu lokusebenza

Working group charter

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

Ububanzi

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.

Imikhakha 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 abalulekile

Amagama abalulekile

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.
24Ucwaningo

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

Questions and answers.

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

Nikela ngobufakazi kusuka kuleli khasi.

I-Reports iwushicilelo lwekota lwe-Consortium. Lokho okwaziyo ngalesi sihloko kungaba ubufakazi, icala noma ukulungiswa kuhlelo olulandelayo, kubongwe wena futhi kushicilelwe ngaphansi kwe-CC BY 4.0 lapho kungumsebenzi wakho.

Nexus Standards
Amazinga

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.

Isimo nokusetshenziswa. Ama-Nexus Standards angamazinga ahlongozwayo athuthukiswe ngenqubo evulekile ngaphansi kwe-NS-13 futhi ashicilelwe ukuze asetshenziswe ngokuzithandela; akusona isitifiketi, ukugunyazwa noma imvume yomlawuli, futhi ukwamukela kuhlala kuyisinqumo se-Global Standards Council futhi, ezweni ngalinye, se-National Standards Council yalo. I-UNI (Unique Nexus Identifier) ihlonza into; ayiyiqinisekisi. Amagama ezinhlaka zamazinga namazinga azo angawabaphathi bawo futhi asetshenziswa kuphela ukuhlonza amadokhumenti; awukho umbhalo wezinga langaphandle okhiqizwe kabusha lapha. I-Nexus Standards ayihlangene, ayesekwa futhi ayiqinisekiswanga yinoma iyiphi inhlangano yamazinga eshiwo lapha.

Amalayisense: i-CC BY 4.0 embhalweni wezindinganiso, amarejista, amaskimu nedatha; i-Apache-2.0 kukhodi yereferensi. Izindinganiso zangaphandle zicashunwa ngegama, inombolo nesixhumanisi ngaphansi kwamalayisense azo. Idatha, amalabhulali namafonti abantu besithathu agcina amalayisense awo: bheka Izaziso zabantu besithathu.