Developers and APIs: readiness pathways
The evidence that the readiness pathways of the Global Centre for Risk and Innovation (GCRI Canada), The Global Risks Forum (GRF) and The Global Risks Alliance (GRA) read from developers and APIs: the standards each pathway lists that this area also carries, each artefact identified by a UNI (Unique Nexus Identifier). Readiness is decided by each institution under its own rules.
- Nexus Standards: NS-1, NS-6, NS-12.
- Open standards: OpenAPI Specification 3.1; AsyncAPI Specification 3.0; JSON Schema 2020-12; CodeMeta; RFC 8594 The Sunset HTTP Header Field; Semantic Versioning 2.0.0.
- Data and feeds: APIs.guru OpenAPI directory; deps.dev API; GitHub REST API (releases).
- Couples with: Conformance test suites; Registries and the resolver; Sandbox and simulated data.
Summary
- Nexus Standards
- 3
- NS-1, NS-6, NS-12
- Open standards
- 6
- named, never copied
- Data and feeds
- 3
- listed for reference
- Couplings
- 3
- with other areas
Standards shared with the pathways
The standards this area lists against those each pathway lists; a shared standard is one listed by both in the registry.
| Programme | NS-0 | NS-1 | NS-3 | NS-3b | NS-6 | NS-9 | NS-10 | NS-11 | NS-12 | NS-13 | NS-14 | Listed |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Developers and APIsplanned | 2 | |||||||||||
| GCRI Canada evidence pathwayplanned | 5 | |||||||||||
| Recognition pathway, The Global Risks Forum (GRF)planned | 5 | |||||||||||
| Capital pathway, The Global Risks Alliance (GRA)planned | 4 |
Coverage matrixA filled cell indicates that the area lists the standard in the registry. Status terms are those of the registry.
GCRI Canada evidence pathway
What a project, dataset or model must carry to be admissible evidence in the GCRI Canada research and intelligence pipelines.
Recognition pathway, The Global Risks Forum (GRF)
What an institution, programme or deployment must evidence for GRF recognition records; records, not reputation.
Capital pathway, The Global Risks Alliance (GRA)
What a project or portfolio must evidence for capital-readiness assessment; never investment advice or endorsement.
Scope of readiness
- Readiness evidence informs, and does not constitute, an approval, endorsement or recognition decision.
- It is neither investment advice nor, by itself, a capital-readiness assessment.
- Each institution assesses the evidence and decides under its own rules.
Questions and answers.
What does applying these standards mean for a developers and APIs project?
Is the capital readiness pathway investment advice?
Around developers and APIs.
Shape the standards for developers and apis.
Governments, regulators, standards bodies, industry, academia and communities are invited to shape the catalogue ahead of its first official release, targeted for 2030: comment on a draft, propose a change, join a working group or host a field exercise.
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 artefact; 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.