Skip to content
StandardsDevelopers and APIsCrosswalk
Pêşdebir û API

Developers and APIs: crosswalk to external standards

The external standards in the crosswalk domains of developers and APIs, from the register, with the relation of each to the Nexus Standards. Each row links to the issuing body, and each relation is evidenced by attestations identified by UNIs (Unique Nexus Identifier).

Pêşdebir û API
What this area is built from, with the open standards it names marked: they are cited or crosswalked, never copied.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.
01Pêvajo

The process.

Crosswalk graph · developers and apisNexus Standards registry
Developers and APIs: crosswalk22 nodes on four orbits (Nexus Standards and implementing repositories at the centre, then domains, external standards and issuing bodies), joined by 22 recorded relations.
Nexus StandardsDomainsExternal standardsIssuing bodiesImplementing repositories
The crosswalk as a table: 10 external standards by domain
QadExternal standardIssuing bodyTêkilî
Software and supply chain integrityCitation File Format (CITATION.cff)Citation File Format projectadopt
Software and supply chain integrityCodeMeta software metadata vocabularyCodeMeta projectadopt
Software and supply chain integrityCycloneDX Bill of Materials specification (ECMA-424)OWASP CycloneDX; Ecma International TC54crosswalk
Software and supply chain integrityJSON Schema 2020-12JSON Schema organisationadopt
Software and supply chain integrityOCI Image Format SpecificationOpen Container Initiativeadopt
Software and supply chain integrityOpenAPI SpecificationOpenAPI Initiative (Linux Foundation)adopt
Software and supply chain integrityOpenSSF Best Practices BadgeOpenSSFcite
Software and supply chain integrityOpenSSF ScorecardOpenSSFcite
Software and supply chain integrityReproducible Builds definition and practicesReproducible Builds projectcite
Software and supply chain integritySPDX (System Package Data Exchange) specification; ISO/IEC…SPDX project (Linux Foundation); ISO/IEC JTC 1adopt

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.

Nexus Standards
3
NS-1, NS-6, NS-12
Standardên vekirî
6
named, never copied
Data and feeds
3
listed for reference
Girêdan
3
with other areas
02Software and supply chain integrity

Software and supply chain integrity

10 register entries.

StandardLaşGuhertoyTêkilîGihîştinPiştrastkirî
SPDX (System Package Data Exchange) specification; ISO/IEC 5962:2021SPDX project (Linux Foundation); ISO/IEC JTC 13.0.1 (December 2024); ISO/IEC 5962:2021 published 9 September 2021 covers an earlier 2.x versionadoptvekirîpiştrastkirî
CycloneDX Bill of Materials specification (ECMA-424)OWASP CycloneDX; Ecma International TC541.6 (9 April 2024; ECMA-424 ratified 26 June 2024); 1.7 and ECMA-424 2nd edition reported by one sourcecrosswalkvekirîpiştrastkirî
OpenSSF Best Practices BadgeOpenSSFpassing, silver, gold tierscitevekirîpiştrastkirî
OpenSSF ScorecardOpenSSFautomated checks scored 0–10citevekirîunverified
CodeMeta software metadata vocabularyCodeMeta project3.0 (2023); context lists 3.1 and the repository lists 4.0adoptvekirîpiştrastkirî
Citation File Format (CITATION.cff)Citation File Format project1.2.0adoptvekirîunverified
OpenAPI SpecificationOpenAPI Initiative (Linux Foundation)3.1.1 (24 October 2024); 3.1.2 and 3.2.0 dated 19 September 2025 in the repository changelogadoptvekirîpiştrastkirî
JSON Schema 2020-12JSON Schema organisation2020-12 (current per json-schema.org)adoptvekirîpiştrastkirî
OCI Image Format SpecificationOpen Container Initiative1.1adoptvekirîunverified
Reproducible Builds definition and practicesReproducible Builds projectcurrentcitevekirîunverified

Unverified entries rest on a secondary source for at least one field, as indicated in the register.

03Têkilî

Relation types and their evidence

TêkilîWateDelîl
citeThe Nexus Standard refers to the external standard as context.Identifier, version and URL in the register.
profileThe Nexus Standard constrains or specialises an open external standard (for example STAC, DCAT, PROV-O, DataCite, CAP).Conformance tests against the external standard’s own validator where one exists.
crosswalkElements of the external standard map to Nexus elements (clauses, record fields).A crosswalk table in the register entry; each row cites the external clause by number, never by text.
adoptThe Nexus Standards use the external standard as it is for a function (for example ISO 3166-1, SPDX, ORCID, ROR).Validation of values against the external scheme.
extendA Nexus Standard adds machine-readable, real-time or provenance elements that the external standard lacks.The extension is a Nexus clause or field; the external standard is cited as the baseline.
gapNo external standard covers the concern; a Nexus Standard specifies it.The gap statement in the landscape study.
04Pirs

Pirs û bersiv.

Does a crosswalk establish that a developers and APIs artefact conforms to these standards?
A crosswalk is a mapping. A relation is displayed as clauses derived from the external standard and their current results; any determination of conformity with an external standard rests with the body entitled to make it.
Why are some relations shown as compatibility profile (restricted)?
The standard is paywalled. Its text is not reproduced, and a compatibility profile of it is published only under an institutional arrangement with the issuing body.
Why are some entries marked unverified?
An unverified entry rests on a secondary source for at least one of name, body, version or year; NS14-R5 requires it to be shown as unverified.
Standards

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.

Rewş û bikaranîn. Nexus Standards standardên pêşniyarkirî ne ku bi pêvajoyeke vekirî di bin NS-13 de hatine pêşxistin û ji bo bikaranîna dilxwazî hatine weşandin; ew ne belgename, ne akreditasyon û ne pejirandina rêkxistinê ne, û pejirandin biryara Encûmena Standardên Cîhanî û, li her welatî, ya Encûmena Standardên Neteweyî ya wê dimîne. UNI (Unique Nexus Identifier) berhemekê nas dike; wê belgename nake. Navên desteyên standardan û standardên wan aîdî parêzvanên wan in û tenê ji bo naskirina belgeyan têne bikaranîn; tu nivîsa standardeke derve li vir nayê dubarekirin. Nexus Standards bi tu desteya standardan a li vir hatiye binavkirin ve ne girêdayî ye, ji aliyê wê ve nayê piştgirîkirin û belgename nekiriye.

Lîsans: CC BY 4.0 ji bo nivîsa standardan, tomargeh, şema û daneyan; Apache-2.0 ji bo koda referansê. Standardên derve bi nav, hejmar û girêdanê di bin lîsansên xwe de têne jêgirtin. Dane, pirtûkxane û fontên aliyê sêyem lîsansên xwe diparêzin: binêre Agahdariyên aliyê sêyem.