Developers and APIs: standards that apply
The 2 standards listed for developers and APIs in the registry, each with its status, UNI (Unique Nexus Identifier) and the rules stated in its text.
- 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
Surface wiring (API header, panel provenance, passports, OpenAPI)
Status specified · trust, authorisation and assurance · UNI not yet allocated.
NS-6 is specified elsewhere: SPECIFIED in NS-1 section 6 and NS-16; implementation status per implementation in the consumers register.
Software, model and AI/ML artefacts (supply chain, model cards, dataset sheets)
Status proposed · software, models and capability lifecycle; trust, authorisation and assurance · NXS-STD-ST-000012.
| Rule | Text |
|---|---|
NS12-R1 | Each software release shall carry a bill of materials, a build attestation and signatures as evidence of the UNI version. |
NS12-R2 | Each model shall carry a model card and each dataset a dataset sheet; both shall cite their sources by UNI. |
NS12-R3 | Agents shall act under recorded mandates and shall be credited as agents; they shall not adopt or certify. |
NS12-R4 | AI governance obligations shall be clauses bound to contextual UNIs and evaluated, not prose assurances. |
Questions and answers.
Are these all the rules for developers and APIs?
What does a rule identifier such as NS1-R5 denote?
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.