Developers and APIs
Publishes the reference tools, APIs, schemas and open-source components on which adopters build: OpenAPI 3.1 and AsyncAPI 3.0 contracts, JSON Schemas, software development kits in several languages with bit-identical UNI grammar and canonical JSON digests, the reference command-line tool, and editor and QGIS plugins, all under Apache-2.0. Each artefact of the area carries a UNI (Unique Nexus Identifier).
- 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.
- 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
- Imeko
- Proposedin the catalogue · planned · scope NXQ
- Last reviewed
- area profile
Nexus Standards (2026). Developers and APIs: area brief, Open Infrastructure and Developers programme. Proposed. https://nexustandards.com/open-infrastructure/developer-and-api/ · UNI NXS-STD-DC-000003. Last reviewed 17 October 2026.
Files include the credits and the licence statement and are generated in the browser; no data is transmitted. Downloads require JavaScript.
Scope and boundaries
An area of the Open Infrastructure and Developers programme (infrastructure services). The area profile sets out 4 matters in scope and 2 matters addressed by other areas.
In scope 4
- OpenAPI, AsyncAPI and Protobuf contracts
- Software development kits (TypeScript, Python, R, Go, Rust) and command-line tool
- Editor, CI and QGIS integrations
- API versioning, deprecation and Sunset headers
Out of scope 2
- Commercial support contracts
- Hosting third-party applications
Jurisdictions Application in each jurisdiction is a national decision, taken by the National Standards Council (NSC) with the competent national authorities.
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.
The service pipeline
A request reaches the service with an explicit context; inputs are identified (NS-1) and validated against OpenAPI Specification 3.1; 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-6, NS-12, NS-1. 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 (11). Records and artefacts are cited by UNI (Unique Nexus Identifier) and version.
Umhloli weenkqubo · Standards · ukuchaza nokulungisa
Umjikelo wobomi bomgangatho
Amanyathelo ali-17·Izigaba 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.
01 Thumela iimishini
- 01Thumela iimishini kwimigangatho neeprofayileInyathelo · Nexus StandardsI-Nexus Standards ithumela imishini nganye engumgqatswa kwimigangatho neeprofayile ezisebenzayo.
02 Iiprofayile nokuhambelana
- 02Qamba iiprofayile zeemishiniInyathelo · Nexus StandardsI-Nexus Standards iqamba iiprofayile zeemishini kwaye ibhale nakuphi na ukwamkelwa kwesizwe iimishini ezixhomekeke kuko.
- 03Qinisekisa iziphumo zokwakha ngokwamaprofayileInyathelo · Nexus StandardsI-Nexus Standards iqinisekisa iziphumo zokwakha ngokwamaprofayile aqanjiweyo kwaye ibhale ubungqina.
- 04Beka iliso kukuhambelana uze ubhale ubungqina obutywiniweyoInyathelo · Nexus StandardsNgexesha leVeki yeNtshukumo i-Nexus Standards ibeka iliso kukuhambelana kwaye ibhale ukuphambuka.
03 Iziphakamiso nophononongo
- 05Ukuphambuka nolungiso ziba ziziphakamiso zotshintshoInyathelo · Nexus StandardsUkuphambuka kuba ziziphakamiso zotshintsho, kwaye ulungiso lubhalwa njengotshintsho kubungqina.
- 06Iziphumo zomjikelo ziba ziziphakamiso zotshintshoInyathelo · Nexus StandardsIziphumo zomjikelo ziba ziziphakamiso zotshintsho: iziphumo zendlela nezolungiso ezivela Iingxelo (F06) nezinto zedokethi ezivela kwi-Nexus…
- 07Yila uze uhlaziye ekuhleniInyathelo · Iikomiti namaqela asebenzayoIikomiti zobugcisa namaqela asebenzayo ayila kwaye ahlaziye imigangatho kwinkqubo evulekileyo ye-NS-13.
- 08Uphononongo olusingise kwisigqibo sebhungaInyathelo · Nexus StandardsI-Nexus Standards ihambisa iziphakamiso zotshintsho kuphononongo zisingise kwisigqibo sebhunga.
04 Isigqibo sebhunga
- 09Umnxeba wokugqibela woluntuInyathelo · IBhunga leMigangatho yeHlabathiIBhunga leMigangatho yeHlabathi liyamkela ngesininzi sesibini kwisithathu emva komnxeba wokugqibela weentsuku ezingamashumi alithoba.
- 10Ukwamkelwa kwehlabathi komgangathoIsigqibo · IBhunga leMigangatho yeHlabathiIBhunga leMigangatho yeHlabathi ligqiba ukwamkelwa komgangatho ngamnye emva komnxeba wokugqibela woluntu.
05 Papasha uze uchonge
- 11Assign a UNI and publishStep · Secretariat (GCRI Canada)Nexus Standards assigns UNIs and deposits publications under the publisher’s process.
- 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.
- 13Papasha utshintsho olwamkelweyo lonyakaInyathelo · Nexus StandardsEkuhlaziyweni i-Nexus Standards ipapasha utshintsho olwamkelweyo lonyaka nemeko yokwamkelwa kwesizwe.
06 Ukwamkelwa nokusetyenziswa kwesizwe
- 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.
- 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).
- 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.
- 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
| Inyathelo | Phase | Ukusebenza | Who | Decision rule | Irekhodi | Implements |
|---|---|---|---|---|---|---|
| 01 | Isicelo | Request (start). The service covers: OpenAPI, AsyncAPI and Protobuf contracts, Software development kits (TypeScript, Python, R, Go, Rust) and command-line tool and Editor, CI and QGIS integrations. | a client, a person or a machine | the context is explicit in the request or on the record, never inferred | a request naming its context and inputs | NS16-R20 |
| 02 | Isicelo | Identify inputs (step). Every input is resolved before it is used; an unresolved input is a typed refusal. | the service | inputs are cited by UNI and version | inputs resolved to their UNIs and versions | NS1-R5, NS2-R2, NS0-P12 |
| 03 | Ukuqinisekiswa | Validate OpenAPI (gate). Open standards of this area: OpenAPI Specification 3.1, AsyncAPI Specification 3.0, JSON Schema 2020-12 and CodeMeta. | the service’s validator | validated against the open standard’s own schema or validator where one exists | a validation run against OpenAPI Specification 3.1 and AsyncAPI Specification 3.0 | NS14-R2 |
| 04 | Processing | Process (model). Processing is reproducible from the inputs, the method version and the configuration. | the service | the method and version are recorded with the result | Software development kits (TypeScript, Python, R, Go, Rust) and command-line tool | NS12-R1 |
| 05 | Processing | Write records (record). Results are written append-only; a correction adds a version. | the service | every result carries what it was derived from | result records with provenance and a record UNI | NS0-P7, NS1-R3 |
| 06 | Publication | Publish and resolve (step). Results are discoverable and citable by UNI. | the service | writes return the allocated UNI; citations resolve | results reachable through the resolver, with the X-Nexus-UNI header | NS1-R5, NS2-R5 |
| 07 | Ukubeka iliso | Monitor (exercise). Data sources the service reads: APIs.guru OpenAPI directory, deps.dev API and GitHub REST API (releases). Data sources are listed for reference; live data is displayed once licence review is complete. | the monitoring service | monitoring records are observations with record UNIs | observations of availability, drift and OpenSSF Scorecard Maintained | NS11-R4 |
| 08 | Ukubeka iliso | Correction (end). Products that used a corrected record are listed and recomputed. | the data steward | a correction never overwrites; dependent results are replayed | a correction record that reaches every dependent result | NS1-R3, NS2-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 · AsyncAPI Specification 3.0 · NS-6: Surface wiring · NS-12: Software, model and AI/ML artefacts.
Routing, monitoring and verification tools
Profile composer
Combine standards and clauses into a draft profile with citations, in YAML or JSON; nothing is submitted.
Available · runs in the browserRouting console
Select a sector, hazard family, capability and artefact type; the registry identifies the applicable standards and states the reasons.
PlannedDeployment
Reference deployments and a sandbox with worked examples.
Each console computes from the registry and states its reasoning; decisions remain with the competent bodies.
How a shock travels through this system
A system model of this area built from the registry: 4 systems, 4 sectors, 6 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.
Iinkqubo nonxibelelwano
- Developers and APIs
- Conformance test suites Coupling
- Registries and the resolver Coupling
- Sandbox and simulated data Coupling
Izilawuli
NS-6Ukudityaniswa komphezulu (isihloko se-API, imvelaphi yephaneli, iipasipoti, i-OpenAPI)NS-12Isoftwe, imodeli nezinto ze-AI/ML (ityathanga lobonelelo, amakhadi eemodeli, amaphepha eeseti zedatha)NS-1I-UNI nekhathalogu yezinto (igrama v0.2: amacandelo enkalo, ecandelo, ommandla nokusingqongileyo)NRS-A3Ujongano lweearhente kwimigangathoNRS-A6Iikhithi zokusebenzisa nokwamkela ngokucofa kanyeNRS-C4Umzekelo wedatha yomngcipheko, izichongi notshintshiselwano
Uqwalaselo
- APIs.guru OpenAPI directory (listed for reference)
- deps.dev API (listed for reference)
- GitHub REST API (releases) (listed for reference)
- Project is actively maintained (learning signal)
- Metadata is accessed through standardised protocol
Imigangatho esebenzayo
The area profile lists 3 Nexus Standards; the registry lists NS-6, NS-12 for this area. Each is a proposed standard under development.
- 01
NS-6 · Surface wiring (API header, panel provenance, passports, OpenAPI)
Status: in progress · 0 requirements stated. Read NS-6 · Requirements for this area.
- 02
NS-12 · Software, model and AI/ML artefacts (supply chain, model cards, dataset sheets)
Status: proposed · 4 requirements stated. Read NS-12 · Requirements for this area.
- 03
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 · Requirements for this area.
Ukudibana kweenkqubo
3 couplings link this area to other areas and programmes, each with the mechanism of the link.
- Conformance test suitesTrust, Verification and AssuranceSDKs are accepted only when they pass the cross-language digest vector suite and the corpus tests.
- Registries and the resolverOpen Infrastructure and DevelopersClients resolve UNIs and read records through the resolver API with X-Nexus-UNI headers (NS-6).
- Sandbox and simulated dataOpen Infrastructure and DevelopersDevelopers test every API against synthetic data before working with governed records.
Data sources
3 data sources named in the area profile, each with provider, licence, update frequency and delivery path.
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
- 0
- licence terms recorded
- Proposed for the register
- 3
- licence terms to be recorded
- Delivery
- 1 governed service · 1 plugin · 0 browser · 1 snapshot · 0 listed for reference
- proposed paths in order of preference: governed data service, plugin, direct browser read, build-time snapshot; sources whose terms do not permit reuse are listed for reference only
APIs.guru OpenAPI directoryfor reference
APIs.guru · continuous
CC0 1.0
build-time snapshotproposed for the data register
deps.dev APIfor reference
Google Open Source Insights · continuous
CC BY 4.0 (data)
governed data serviceproposed for the data register.
GitHub REST API (releases)for reference
GitHub · per release
GitHub terms of service; repository content under its own licences.
integration pluginproposed for the data register
Open standards referenced
6 open standards, each with its relation as recorded in the register under NS-14. Hover over or focus a relation for its definition.
adopt6
OpenAPI Specification 3.1OpenAPI Initiative (Linux Foundation)listed in the register · openapi-3-1AsyncAPI Specification 3.0AsyncAPI Initiative (Linux Foundation)proposed for the registerJSON Schema 2020-12JSON Schema projectlisted in the register · json-schema-2020-12CodeMetaCodeMeta projectlisted in the register · codemetaRFC 8594 The Sunset HTTP Header FieldIETFproposed for the registerSemantic Versioning 2.0.0SemVer projectproposed for the registerWorking group charter
A proposed charter for this area, open to institutions and experts.
Maintain API contracts, software development kits and developer tooling.
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).
- OpenAPI and AsyncAPI contracts with linting
- Cross-language digest vector suite
- SDK release and deprecation policy
- OpenAPI Initiative liaison sought
- AsyncAPI Initiative liaison sought
- OSGeo / QGIS project liaison sought
Izalathisi
The area profile names 2 indicators, each with its framework and code.
Indicator names and codes are given as published by their stewards.
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.
GCRI Canada
GCRI Canada uses the generated software development kits so that digests and UNIs match the reference implementation.
I-Global Risks Forum (GRF)
GRF recognises contributions to the open tooling by their merged, DCO-signed commits.
I-Global Risks Alliance (GRA)
GRA reviewers can verify receipts and attestations independently with the open command-line tool.
Each institution determines under its own rules what it accepts as evidence; a pathway reading is neither an approval nor investment advice.
Open research questions
2 questions identified as priorities for the working group.
- Bit-identical canonical JSON across languages with different number and Unicode handling.
- Keeping five software development kits in step with additive API changes without breaking clients pinned to earlier versions.
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.
Intended users
The area profile identifies 4 user communities.
- Software developers
- Research software engineers
- GIS developers
- Integrators at partner institutions
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.
Registry listing and depth pages
This area is in the catalogue (status: planned; scope NXQ; 1 crosswalk domain). It has five depth pages and a register crosswalk of its domains.
Imigangatho esebenzayo
The rules of each listed standard, read through the specification reader.
Depth · CrosswalkUnxibelelwano
Every register entry in the area’s domains, by relation, with the crosswalk graph.
Depth · Records and schemasRecords and schemas
Scope, record, schema explorer and how a UNI resolves.
Depth · ConformanceUkuhambelana
Clauses, evidence and attestations for conformance assessment.
Depth · ReadinessUkulungela
The area alongside the three pathways, as a matrix.
The crosswalk as a table: 10 external standards by domain
| Indawo yolwazi | External standard | Issuing body | Relation |
|---|---|---|---|
| Software and supply chain integrity | Citation File Format (CITATION.cff) | Citation File Format project | adopt |
| Software and supply chain integrity | CodeMeta software metadata vocabulary | CodeMeta project | adopt |
| Software and supply chain integrity | CycloneDX Bill of Materials specification (ECMA-424) | OWASP CycloneDX; Ecma International TC54 | crosswalk |
| Software and supply chain integrity | JSON Schema 2020-12 | JSON Schema organisation | adopt |
| Software and supply chain integrity | OCI Image Format Specification | Open Container Initiative | adopt |
| Software and supply chain integrity | OpenAPI Specification | OpenAPI Initiative (Linux Foundation) | adopt |
| Software and supply chain integrity | OpenSSF Best Practices Badge | OpenSSF | cite |
| Software and supply chain integrity | OpenSSF Scorecard | OpenSSF | cite |
| Software and supply chain integrity | Reproducible Builds definition and practices | Reproducible Builds project | cite |
| Software and supply chain integrity | SPDX (System Package Data Exchange) specification; ISO/IEC… | SPDX project (Linux Foundation); ISO/IEC JTC 1 | adopt |
Nexus Standards in the graph: NS-6, NS-12. A relation is a register entry, never a compliance claim.
2 Nexus Standards · 1 domains · 10 external standards · 9 issuing bodies · 0 implementing repositories. Relations (adopt, profile, crosswalk, cite) are as recorded in the register; names and standards remain with their stewards.
Crosswalk graph22 nodes and 22 links from the registry of external standards, programme areas and implementations (the external standards register, the consumers register. 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.
Issuing bodies and their seats (4)
| Iqumrhu | Seat | Register entries |
|---|---|---|
| OpenSSF | San Francisco, California, United States | 2 |
| OpenAPI Initiative (Linux Foundation) | San Francisco, California, United States | 1 |
| OWASP CycloneDX; Ecma International TC54 | Geneva, Switzerland | 1 |
| SPDX project (Linux Foundation); ISO/IEC JTC 1 | San Francisco, California, United States | 1 |
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 · 5 issuing bodies have no single public seat and are listed without a location: CodeMeta project; Citation File Format project; JSON Schema organisation; Open Container Initiative; Reproducible Builds project.
Standards globe4 issuing bodies with a public seat and 10 register entries, shown in equal-area cells at four levels of detail. Seats are placed at city coordinates; programme areas, implementations and standards have no location and are not drawn. A still world map is shown where scripts are unavailable.
Imithombo
3 references from peer-reviewed and official publications cited in the area profile, linked at the publishers’ own sites.
peer-reviewedIntroducing the FAIR Principles for research softwareScientific Data · 2022peer-reviewedTowards FAIR principles for research softwareData Science · 2020- standardOpenAPI Specification v3.1.1OpenAPI Initiative · 2024
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 termsweb API; API design; open API; research software; OpenAPI Specification; AsyncAPI Specificationcombined with: risk; disaster; hazard; resilience; early warningDerived 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.
Risk Academy courses and disciplines
1 course and 3 disciplines of Risk Academy (risksacademy.com) that teach the knowledge and methods of this area. Each course lists its level, stream and learning hours.
Izifundo
Amasebe olwazi
The correspondence between courses, disciplines and the Nexus Standards is maintained with Risk Academy and is subject to its academic review.
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.
Uphando nobungqina
GCRI Canada
Research programmes that produce the observations, models and assessments these records describe.
Digital Public InfrastructureStudies interoperability and application interfaces.Apply to this programme Data and ComputeEngineers reproducible pipelines.Apply to this programme therisk.globalAll programmes of GCRI CanadaGovernance, 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 ForumCapital, 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.Join this programme globalriskalliance.comAll programmes of The Global Risks AllianceImfundo noqeqesho
Risk Academy
Courses and disciplines that teach the knowledge and methods practitioners need to apply these standards.
Technology and DataRAT-204 · Intermediate · 19 learning hoursManaging risk data, AI, digital infrastructure and technology risk responsiblyTake this course All courses and disciplinesListed in the education and training section of this pageAmagama 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.
Related areas
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
- Introducing the FAIR Principles for research software
Scientific Data · 2022 · Peer-reviewed - Towards FAIR principles for research software
Data Science · 2020 · Peer-reviewed - OpenAPI Specification v3.1.1
OpenAPI Initiative · 2024 · Standard
Related standards and frameworks
- OpenAPI Specification 3.1
OpenAPI Initiative (Linux Foundation) - AsyncAPI Specification 3.0
AsyncAPI Initiative (Linux Foundation) - JSON Schema 2020-12
JSON Schema project - CodeMeta
CodeMeta project - RFC 8594 The Sunset HTTP Header Field
IETF - Semantic Versioning 2.0.0
SemVer project
Search terms, derived from the title and scope of the area: web API; API design; open API; research software; combined with: risk; disaster; hazard; resilience; early warning. With JavaScript enabled, recent works matching these terms are listed from OpenAlex and Crossref.
Imibuzo neempendulo.
What is the status of the Developers and APIs area?
How are data sources presented?
How can this brief be amended?
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.
- I-imeyileIsango GW-STDIthumele kweli phephaUbungqina, ulungiso, imeko, indlela, uphononongo, inguqulelo okanye igalelo leprofayile. Ifika ineleyibhile yeli phepha, ukuze umhleli onoxanduva lwayo ayifumane.
- ZenodoOpen depositDeposit it and submit to the communityPublish your own record on Zenodo with your ORCID iD, then submit it to the Reports community there. Curators review it; the DOI stays yours.
- ReportsNexus StandardsSee every way to contributeThe contribution types, how each is reviewed, what credit you receive, the licence and what is never accepted.
Musa ukuthumela idatha yobuqu, iinkcukacha ezibuthathaka zeziseko zophuhliso okanye nantoni na ongenalungelo lokwabelana ngayo. Umnikelo uphononongwa phambi kokuba usetyenziswe; ukuwuthumela akunikezi bubhali okanye amalungelo okuhlela, kwaye uxhaso alusoze luthenge isigqibo.
Contribute to Developers and APIs
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.