Vir ontwikkelaars
The developer entry area of the Open Infrastructure and Developers programme is written for software engineers in every community who need schemas, a resolver, a command-line tool and a verification API that they can implement without seeking permission: deployment guidance, a test environment, the planned software development kits, the monitoring cycle and the STAC package, with supply-chain integrity requirements throughout. Each artefact of the area carries a UNI (Unique Nexus Identifier).
- Nexus Standards: NS-1, NS-3, NS-3b, NS-11, NS-12.
- Open standards: OpenAPI Specification 3.1; JSON Schema 2020-12; SpatioTemporal Asset Catalog (STAC) 1.0; Supply-chain Levels for Software Artifacts (SLSA) 1.1; Sigstore signing and transparency log; SPDX; OpenID Connect Core 1.0 on OAuth 2.0.
- Data and feeds: World Development Indicators; USGS earthquake GeoJSON summary feeds.
- Couples with: Developers and APIs; Sandbox and simulated data; Software and supply chain; Conformance programme.
- Nexus Standards
- 5
- NS-1, NS-3, NS-3b
- Open standards
- 7
- named, never copied
- Data and feeds
- 2
- listed for reference
- Couplings
- 4
- with other areas
- UNI
- requested · allocation in progress
- Status
- Proposednot yet in the catalogue
- Last reviewed
- area profile
Nexus Standards (2026). For developers: area brief, Open Infrastructure and Developers programme. Proposed. https://nexustandards.com/open-infrastructure/for-developers/. 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 (audiences). The area profile sets out 5 matters in scope and 3 matters addressed by other areas.
In scope 5
- A path through deployment guidance, the test environment, the planned software development kits, the monitoring cycle and the STAC package
- Schemas (JSON Schema 2020-12) and OpenAPI 3.1 descriptions
- The UNI resolver and X-Nexus-UNI header
- Signing, SBOM and provenance for releases
- Running conformance tests in continuous integration
Out of scope 3
- Hosted services or support contracts
- Proprietary SDKs
- Production readiness claims for any implementation
Jurisdictions Application in each jurisdiction is a national decision, taken by the National Standards Council (NSC) with the competent national authorities.
Where developers start in the registry.
Standaarde
Nexus Standards to read first
5 Nexus Standards selected for this community.
| Standaard | Title | Status | UNI |
|---|---|---|---|
| NS-1 | Die UNI en die artefakkatalogus (grammatika v0.2: domein-, sektor-, streek- en omgewingsegmente) | voorgestel | NXS-STD-ST-000001 |
| NS-3 | Risikorekord-UNI's (grammatika, oorerflike kruisverwysing, toewysingsgesag) | voorgestel | NXS-STD-ST-000003 |
| NS-6 | Oppervlakbedrading (API-kop, paneelherkoms, paspoorte, OpenAPI) | gespesifiseer | not yet allocated |
| NS-7 | Landingsbladsye van die oplosser, bladsy-metamerkers, werfkaart | gespesifiseer | not yet allocated |
| NS-12 | Sagteware-, model- en KI/ML-artefakte (voorsieningsketting, modelkaarte, datastelblaaie) | voorgestel | NXS-STD-ST-000012 |
Gebiede
Programme areas in these domains
12 programme areas in the domains of this community.
Health risk standards
NS-0, NS-1, NS-3, NS-9, NS-10, NS-11 · planned.
Sektore en bedryweGesondheidstelsels
NS-0, NS-3, NS-9, NS-11 · planned
Sektore en bedryweDigitaal, telekommunikasie en platforms
NS-0, NS-9, NS-11, NS-12 · planned
Sektore en bedryweNavorsing, akademie en onderwys
NS-0, NS-1, NS-2, NS-4, NS-8, NS-12 · planned.
Cross-cutting capabilitiesIdentification (the UNI)
NS-1, NS-3, NS-9 · wired
Cross-cutting capabilitiesData and datasets
NS-3, NS-3b, NS-11 · planned
Cross-cutting capabilitiesSoftware and supply chain
NS-12 · planned
Cross-cutting capabilitiesVisualisation, figures and maps
NS-5 · planned
Cross-cutting capabilitiesDokumentasie en publikasie
NS-2, NS-4, NS-7, NS-8 · planned
Cross-cutting capabilitiesIdentity, authorisation and zero trust
NS-11, NS-10 · planned
Cross-cutting capabilitiesProvenance and evidence
NS-3b, NS-11 · planned
Cross-cutting capabilitiesVerification and monitoring
NS-11 · planned
Eksterne standaarde
External standards in these domains
46 external standards referenced for these domains.
A further 6 are listed on the crosswalk pages of the areas above.
Gereedskap
Tools and records
Implementation status as recorded in the registry for each implementation.
| Implementering | Rol | Standards for this community |
|---|
| Record | Title | Status |
|---|---|---|
NXS-STD-ST-000001 | Nexus Standards NS-1 – the UNI and artefact catalogue | draft |
NXS-STD-SW-000002 | UNI command-line tool (validate, parse, next, mint, catalogue, export) – reference implementation | draft |
NXS-STD-SC-000001 | UNI artefact record schema v1 | draft |
NXS-STD-ST-000002 | Open-standards and open-source stack under the UNI | draft |
NXS-STD-SW-000005 | UNI data profile (STAC, DCAT, PROV-O crosswalks), NS-3b | draft |
NXS-STD-ST-000003 | Nexus Standards NS-3 – risk record UNIs (grammar, legacy crosswalk, allocation authority) | draft |
NXS-STD-ST-000012 | Nexus Standards NS-12 – software, models and AI/ML artefacts | draft |
The participation pathway
Software engineers, Data engineers and Platform operators find the area and its open drafts, take part without a membership fee, comment in the open, join a working group, propose text and see each comment answered in writing; accepted work becomes a version, and national adoption is decided by each National Standards Council (NSC). 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 (8). Records and artefacts are cited by UNI (Unique Nexus Identifier) and version.
Prosesverkenner · Standards · kodifiseer en korrigeer
Lewensiklus van 'n standaard
17 stappe·6 fases
Standards · kodifiseer en korrigeer
Lewensiklus van 'n standaard
Lewensiklus van 'n standaard · NS-13-spoor · Bydraekanale · IETF-spoor · W3C-spoor · OGC-spoor · OASIS-spoor · ISO- en IEC-fases · Konformiteit · Rekordlewensiklus · Roetering · Monitering.
Siklusbevindings word veranderingsvoorstelle, die Wêreldwye Standaarderaad aanvaar ná 'n openbare laaste oproep, en elke land besluit oor sy eie aanvaarding.
01 Lei sendings
- 01Route missions to standards and profilesStep · Nexus StandardsNexus Standards routes each candidate mission to the standards and profiles that apply.
02 Profiele en ooreenstemming
- 02Stel sendingprofiele saamStap · Nexus StandardsNexus Standards stel sendingprofiele saam en teken enige nasionale aanvaarding aan waarvan die sendings afhang.
- 03Valideer bou-uitsette teen die profieleStap · Nexus StandardsNexus Standards valideer bou-uitsette teen die saamgestelde profiele en teken die bewyse aan.
- 04Moniteer konformiteit en teken verseëlde bewyse aanStap · Nexus StandardsGedurende die Aksieweek monitor Nexus Standards konformiteit en teken afwykings aan.
03 Voorstelle en beoordeling
- 05Afwykings en regstellings word veranderingsvoorstelleStap · Nexus StandardsAfwykings word veranderingsvoorstelle, en die regstelling word as 'n verandering aan die bewyse aangeteken.
- 06Siklusbevindings word veranderingsvoorstelleStap · Nexus StandardsBevindings uit 'n siklus word veranderingsvoorstelle: metode- en korreksiebevindings uit Verslae (F06) en dokketitems uit Nexus…
- 07Stel op en hersien in die openbaarStap · Komitees en werkgroepeTegniese komitees en werkgroepe stel die standaarde op en hersien dit in die oop proses van NS-13.
- 08Beoordeel met die oog op 'n raadsbesluitStap · Nexus StandardsNexus Standards beweeg veranderingsvoorstelle deur beoordeling met die oog op 'n raadsbesluit.
04 Raadsbesluit
- 09Openbare laaste oproepStap · Global Standards CouncilDie Global Standards Council aanvaar by 'n tweederdemeerderheid ná 'n laaste oproep van negentig dae.
- 10Wêreldwye aanvaarding van 'n standaardBesluit · Global Standards CouncilDie Wêreldwye Standaarderaad besluit oor die aanvaarding van elke standaard ná 'n openbare laaste oproep.
05 Publiseer en identifiseer
- 11Assign a UNI and publishStep · Secretariat (GCRI Canada)Nexus Standards assigns UNIs and deposits publications under the publisher’s process.
- 12'n UNI identifiseer en sertifiseer nooit nieRekord · Nexus StandardsElke objek van die programjaar dra een identifiseerder, 'n UNI onder NS-1, sodat dit aangehaal, geweergaweer en opgelos kan word.
- 13Publiseer die jaar se aanvaarde veranderingeStap · Nexus StandardsBy hernuwing publiseer Nexus Standards die jaar se aanvaarde veranderinge en die nasionale aanvaardingstatus.
06 Nasionale aanvaarding en toepassing
- 14Nasionale aanvaarding deur die Nasionale StandaarderaadBesluit · Nasionale StandaarderaadElke land se Nasionale Standaarderaad besluit oor nasionale aanvaarding: aanvaar soos dit is, aanvaar met 'n profiel (NS-16), pas aan, of verwys slegs.
- 15Aangenome standaarde bereik kursusse en uitgawesStap · Nexus StandardsElke aangenome standaard of profiel word 'n kursusmodule by Risk Academy (F09), en standaarde word in Reports-uitgawes (R1) toegepas.
- 16Aanvaarding is finaal vir elke jurisdiksieStandaard · Nasionale StandaarderaadAanvaarding is finaal vir elke jurisdiksie, en die GSC het geen veto oor 'n nasionale besluit nie. Geen globale liggaam hou 'n veto nie.
- 17Nasionale aanvaardingsrekordsRekord · Nexus StandardsSaamgestelde missieprofiele en nasionale aanvaardingsrekords gaan na die Foundry by gereedheidsvoorbereiding (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
| Step | Phase | Operation | Who | Decision rule | Record | Implements |
|---|---|---|---|---|---|---|
| 01 | Discovery | Find the area (start). Learning pathways and calls are linked from the area. The developer entry area of the Open Infrastructure and Developers programme is written for software engineers in every community who need schemas, a resolver, a command-line tool and a verification API that they can implement without seeking permission: deployment guidance, a test environment, the planned software development kits, the monitoring cycle and the STAC package, with supply-chain integrity requirements throughout.. | Software engineers, Data engineers and Platform operators | standards, registries and schemas are published openly | the area page, its drafts and its calls | NS0-P1 |
| 02 | Discovery | Read the drafts (step). Nexus Standards of this area: NS-1, NS-3, NS-3b, NS-11, NS-12. | the participant | drafts carry UNIs and are cited by version | the current drafts with their UNIs | NS2-R2 |
| 03 | Joining | Join (step). No membership fee is required; agents take part under a recorded mandate. | the participant | participation is open and free; identity is recorded | an identity recorded with ORCID or ROR | NS13-R2 |
| 04 | Comment | Comment (record). Accepted, rejected, deferred or open: each disposition is written. | the participant | each comment receives a disposition with a reason | a comment in the open record of a proposal | NS13-R2 |
| 05 | Comment | Working group (step). Deliverables: Developer learning path with the STAC package as worked example, Reference command-line tool and schema examples and Continuous-integration template for running conformance tests. | the working group chairs | consensus with recorded dissent; two co-chairs from different organisations | Curate the developer path, maintain reference tools and examples, and triage implementer issues. | NS13-R2 |
| 06 | Proposal | Propose text (gate). Last call is announced to every stakeholder group listed on the proposal. | the participant or the working group | every change enters through a proposal; objections are dispositioned before acceptance | a proposal with a UNI, through last call | NS13-R1, NS13-R3 |
| 07 | Aanvaarding | New version (record). Contributors are credited; agents are credited as agents. | the editors | editors decide in writing; they do not adopt | a semantic version crediting contributors | NS13-R4, NS13-R5, NS2-R3 |
| 08 | Aanvaarding | Adoption (end). The GSC has no veto over a national decision. | the GSC; in each country the NSC | national adoption is a national decision | adoption by the Global Standards Council (GSC); national decisions by each NSC | NS13-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 · JSON Schema 2020-12 · NS-1: The UNI and the artefact catalogue · NS-3: Risk record UNIs.
From frameworks and sources to the applicable standards
Read from left to right; select or focus an item to trace its connections.
The interactive view requires JavaScript; the sections below present the same records.
Intended users
The area profile identifies 4 user communities.
- Software engineers
- Data engineers
- Platform operators
- Open-source maintainers
How a shock travels through this system
A system model of this area built from the registry: 5 systems, 4 sectors, 11 controls, 2 feeds, 1 indicator. 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.
Systems and couplings
- Vir ontwikkelaars
- Ontwikkelaars en API's Koppeling
- Sandbox en gesimuleerde data Koppeling
- Software and supply chain Coupling
- Konformiteitsprogram Koppeling
Controls
NS-1Die UNI en die artefakkatalogus (grammatika v0.2: domein-, sektor-, streek- en omgewingsegmente)NS-3Risikorekord-UNI's (grammatika, oorerflike kruisverwysing, toewysingsgesag)NS-3bDatastel- en produkmetadataprofiel (STAC, DCAT, PROV-O)NS-11Verifikasie en monitering (getuienis, attestasies, zero-trust-ooreenstemmingwaarneming)NS-12Sagteware-, model- en KI/ML-artefakte (voorsieningsketting, modelkaarte, datastelblaaie)NRS-C11Konformiteit, verifikasie en instandhouding van standaardeNRS-S5System profile: NXS-NXQ (Software, models and capability lifecycle)NRS-A1Standaarde as kode: masjienleesbare standaarde, vereistes en toetseNRS-S8System profile: NXS-EWS (Multi-hazard monitoring and warning)NRS-T8Risiko vir die integriteit van sagteware en voorsieningskettingsNRS-A6Een-klik-ontplooiing en aanvaardingstelle
Observation
- World Development Indicators (listed for reference)
- USGS earthquake GeoJSON summary feeds (listed for reference)
- Proportion of individuals using the Internet
Standards that apply
The area profile lists 5 Nexus Standards. Each is a proposed standard under development.
- 01
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.
- 02
NS-3 · Risk record UNIs (grammar, legacy crosswalk, allocation authority)
Status: proposed · 0 requirements stated. Read NS-3.
- 03
NS-3b · Dataset and product metadata profile (STAC, DCAT, PROV-O)
Status: proposed · 0 requirements stated. Read NS-3b.
- 04
NS-11 · Verification and monitoring (evidence, attestations, zero-trust conformance observation)
Status: proposed · 6 requirements stated. Read NS-11.
- 05
NS-12 · Software, model and AI/ML artefacts (supply chain, model cards, dataset sheets)
Status: proposed · 4 requirements stated. Read NS-12.
Open standards referenced
7 open standards, each with its relation as recorded in the register under NS-14. Hover over or focus a relation for its definition.
adopt7
OpenAPI Specification 3.1OpenAPI Initiative (Linux Foundation)listed in the register · openapi-3-1JSON Schema 2020-12JSON Schema organisationlisted in the register · json-schema-2020-12SpatioTemporal Asset Catalog (STAC) 1.0STAC community; OGC Community Standardlisted in the register · stacSupply-chain Levels for Software Artifacts (SLSA) 1.1OpenSSF (Linux Foundation)listed in the register · slsaSigstore signing and transparency logOpenSSF (Linux Foundation)listed in the register · sigstoreSPDXSPDX project (Linux Foundation)listed in the register · spdxOpenID Connect Core 1.0 on OAuth 2.0OpenID Foundation and IETFlisted in the register · oauth2-openid-connectRouting, monitoring and verification tools
Deployment
Reference deployments and a sandbox with worked examples.
Available · from the registryVerification console
Test suites, conformance statements and attestations for each standard, as recorded in the registry.
In progressMonitoring console
Version and source status for each standard, as published by the issuing bodies.
Each console computes from the registry and states its reasoning; decisions remain with the competent bodies.
Sistemiese koppelings
4 couplings link this area to other areas and programmes, each with the mechanism of the link.
- Developers and APIsOpen Infrastructure and DevelopersThe developer and API area documents the schemas, resolver and APIs this path starts from.
- Sandbox and simulated dataOpen Infrastructure and DevelopersDevelopers test against synthetic data and conformance suites in the test environment.
- Software and supply chainTrust, Verification and AssuranceReleases must carry signatures, SBOMs and provenance attestations under NS-12.
- Conformance programmeReadiness and AdoptionDevelopers publish implementation conformance statements for their implementations.
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
Developers learn how their implementations produce records that the GCRI Canada evidence pathway can read; GCRI Canada decides admissibility.
Die Global Risks Forum (GRF)
Developers see how an implementation’s conformance statements contribute to a programme’s trail that GRF may consider under its own rules.
Die Global Risks Alliance (GRA)
Developers see how verifiable records from their tools can be cited in GRA files; GRA decides capital readiness.
Each institution determines under its own rules what it accepts as evidence; a pathway reading is neither an approval nor investment advice.
Data sources
2 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.
- Lewendig
- 0
- on completion of licence review
- Listed in the data register
- 2
- licence terms recorded
- Proposed for the register
- 0
- licence terms to be recorded
- Delivery
- 2 governed service · 0 plugin · 0 browser · 0 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
USGS earthquake GeoJSON summary feedsfor reference
U.S. Geological Survey · real time
U.S. Government work (public domain)
governed data servicelisted in the data register.
World Development Indicatorsfor reference
World Bank · annual with quarterly updates
CC BY 4.0
governed data servicelisted in the data register.
Aanwysers
The area profile names 1 indicator, each with its framework and code.
Indicator names and codes are given as published by their stewards.
Working group charter
A proposed charter for this area, open to institutions and experts.
Curate the developer path, maintain reference tools and examples, and triage implementer issues.
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).
- Developer learning path with the STAC package as worked example
- Reference command-line tool and schema examples
- Continuous-integration template for running conformance tests
- OpenAPI Initiative liaison sought
- STAC community liaison sought
- OpenSSF liaison sought
- JSON Schema organisation liaison sought
Open research questions
3 questions identified as priorities for the working group.
- Reference tools must stay small while covering many profiles.
- Conformance tests need stable fixtures that do not reproduce licensed data.
- Supply-chain requirements add friction for small projects.
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.
Hazards, threats and sectors concerned
Hazards and threats 0
This area draws on the hazards of the areas it is coupled with.
Sektore 0
This area serves all sectors through the areas it is coupled with.
Bronne
4 references from peer-reviewed and official publications cited in the area profile, linked at the publishers’ own sites.
peer-reviewedModel cards for model reportingProceedings of the Conference on Fairness, Accountability, and Transparency (ACM) · 2019peer-reviewedThe FAIR Guiding Principles for scientific data management and stewardshipScientific Data · 2016- officialSecure Software Development Framework (SSDF) Version 1.1 (NIST SP 800-218)NIST · 2022
- officialZero Trust Architecture (NIST SP 800-207)NIST · 2020
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 termsresearch software; open source software; web API; software engineering; OpenAPI Specification; JSON Schema 2020-12Derived 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
2 courses 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.
Kursusse
Dissiplines
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.
Navorsing en bewyse
GCRI Canada
Research programmes that produce the observations, models and assessments these records describe.
Data and ComputeEngineers reproducible pipelines and data infrastructure.Apply to this programme Digital Public InfrastructureStudies interoperability and application interfaces.Apply to this programme LabsWorks on AI and scientific workflows.Apply to this programme therisk.globalAll programmes of GCRI CanadaGovernance, policy and convening
Die 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
Die Global Risks Alliance (GRA)
Industry programmes in which financial institutions build a shared understanding of systemic risk.
Fintech NexusExamines open finance and application interfaces in financial services.Join this programme globalriskalliance.comAll programmes of The Global Risks AllianceOnderwys en opleiding
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 Earth Observation and GIS for RiskRAT-201 · Introductory · 22 learning hoursMaps, satellites, terrain and open data for hazard and exposure analysis, with four hands-on labsTake this course All courses and disciplinesListed in the education and training section of this pageKernterme
- UNI
- Unique Nexus Identifier: a persistent identifier that resolves an artefact to its record.
- voorgestel
- 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
- Secure Software Development Framework (SSDF) Version 1.1 (NIST SP 800-218)
NIST · 2022 · Official publication - Zero Trust Architecture (NIST SP 800-207)
NIST · 2020 · Official publication - Model cards for model reporting
Proceedings of the Conference on Fairness, Accountability, and Transparency (ACM) · 2019 · Peer-reviewed - The FAIR Guiding Principles for scientific data management and stewardship
Scientific Data · 2016 · Peer-reviewed
Related standards and frameworks
- OpenAPI Specification 3.1
OpenAPI Initiative (Linux Foundation) - JSON Schema 2020-12
JSON Schema organisation - SpatioTemporal Asset Catalog (STAC) 1.0
STAC community; OGC Community Standard - Supply-chain Levels for Software Artifacts (SLSA) 1.1
OpenSSF (Linux Foundation) - Sigstore signing and transparency log
OpenSSF (Linux Foundation) - SPDX
SPDX project (Linux Foundation) - OpenID Connect Core 1.0 on OAuth 2.0
OpenID Foundation and IETF
Search terms, derived from the title and scope of the area: research software; open source software; web API; software engineering. With JavaScript enabled, recent works matching these terms are listed from OpenAlex and Crossref.
Questions and answers.
What is the status of the For developers area?
How are data sources presented?
How can this brief be amended?
Dra bewyse vanaf hierdie bladsy by.
Reports is die Konsortium se kwartaallikse publikasie. Wat jy oor hierdie onderwerp weet, kan bewyse, 'n saak of 'n korreksie in die volgende uitgawe word, aan jou toegeskryf en onder CC BY 4.0 gepubliseer waar dit jou eie werk is.
- E-posPoort GW-STDStuur dit vanaf hierdie bladsyGetuienis, 'n regstelling, 'n geval, 'n metode, 'n beoordeling, 'n vertaling of profielinset. Dit kom aan gemerk met hierdie bladsy, sodat die redakteur wat dit besit dit ontvang.
- 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.
Stuur nooit persoonlike data, sensitiewe infrastruktuurbesonderhede of enigiets wat u geen reg het om te deel nie. 'n Bydrae word voor gebruik beoordeel; die stuur daarvan verleen geen outeurskap of redaksionele regte nie, en borgskap koop nooit 'n bevinding nie.
Contribute to For developers
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.
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.