Skip to content
StandardsDevelopers and APIsStandards that apply
Ontwikkelaars en API's

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.

Ontwikkelaars en API's
What this area is built from: the Nexus Standards it applies (marked), the open standards it names and the data and feeds it reads, then the areas it couples with.Source: the Nexus Standards registry: the area record.
  • 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
01NS-6

Oppervlakbedrading (API-kop, paneelherkoms, paspoorte, 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.

Read NS-6 in full

02NS-12

Sagteware-, model- en KI/ML-artefakte (voorsieningsketting, modelkaarte, datastelblaaie)

Status proposed · software, models and capability lifecycle; trust, authorisation and assurance · NXS-STD-ST-000012.

RuleText
NS12-R1Each software release shall carry a bill of materials, a build attestation and signatures as evidence of the UNI version.
NS12-R2Each model shall carry a model card and each dataset a dataset sheet; both shall cite their sources by UNI.
NS12-R3Agents shall act under recorded mandates and shall be credited as agents; they shall not adopt or certify.
NS12-R4AI governance obligations shall be clauses bound to contextual UNIs and evaluated, not prose assurances.

Read NS-12 in full

03Vrae

Questions and answers.

Are these all the rules for developers and APIs?
They are the rules stated by the listed standards. The principles of NS-0 bind every standard; clauses specific to the area, where needed, are written under NS-10 and evaluated under NS-11.
What does a rule identifier such as NS1-R5 denote?
The number of the standard and the number of the rule within it. Rule identifiers are stable so that clauses, attestations and publications can cite them.
Standaarde

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 en gebruik. Die Nexus Standards is voorgestelde standaarde wat deur 'n oop proses onder NS-13 ontwikkel en vir vrywillige gebruik gepubliseer word; hulle maak nie sertifisering, akkreditasie of regulatoriese goedkeuring uit nie, en aanvaarding bly 'n besluit van die Wêreldwye Standaarderaad en, in elke land, van sy Nasionale Standaarderaad. 'n UNI (Unique Nexus Identifier) identifiseer 'n artefak; dit sertifiseer dit nie. Name van standaardliggame en hul standaarde behoort aan hul rentmeesters en word slegs gebruik om die dokumente te identifiseer; geen teks van 'n eksterne standaard word hier gereproduseer nie. Nexus Standards is nie geaffilieer met, onderskryf deur of gesertifiseer deur enige standaardliggaam wat hier genoem word nie.

Lisensies: CC BY 4.0 vir standaardteks, registers, skemas en data; Apache-2.0 vir verwysingskode. Eksterne standaarde word volgens naam, nommer en skakel onder hul eie lisensies aangehaal. Derdeparty-data, -biblioteke en -lettertipes behou hul eie lisensies: sien Kennisgewings van derde partye.