Ji bo pêşdebiran
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
- Standardên vekirî
- 7
- named, never copied
- Data and feeds
- 2
- listed for reference
- Girêdan
- 4
- with other areas
- UNI
- requested · allocation in progress
- Rewş
- 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.
Standards
Nexus Standards to read first
5 Nexus Standards selected for this community.
| Standard | Sernav | Rewş | UNI |
|---|---|---|---|
| NS-1 | UNI û kataloga berheman (rêziman v0.2: beşên qad, sektor, herêm û jîngehê) | pêşniyarkirî | NXS-STD-ST-000001 |
| NS-3 | UNIyên tomara xetereyê (rêzimanî, nexşeya veguhastina ji pergala kevin, desthilata veqetandinê) | pêşniyarkirî | NXS-STD-ST-000003 |
| NS-6 | Girêdana rûberê (sernivîsa API, koka panelê, pasaport, OpenAPI) | diyarkirî | not yet allocated |
| NS-7 | Rûpelên daketinê yên çareserker, etîketên meta yên rûpelê, nexşeya malperê | diyarkirî | not yet allocated |
| NS-12 | Berhemên nermalav, model û AI/ML (zincîra dabînkirinê, kartên modelê, pelên koma daneyan) | pêşniyarkirî | NXS-STD-ST-000012 |
Qad
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.
Sektor û pîşesazîPergalên tenduristiyê
NS-0, NS-3, NS-9, NS-11 · planned
Sektor û pîşesazîDîjîtal, telekom û platform
NS-0, NS-9, NS-11, NS-12 · planned
Sektor û pîşesazîLêkolîn, akademî û perwerde
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 capabilitiesBelgekirin û weşandin
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
Standardên derveyî
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.
Amûr
Tools and records
Implementation status as recorded in the registry for each implementation.
| Bicihanîn | Rol | Standards for this community |
|---|
| Tomar | Sernav | Rewş |
|---|---|---|
NXS-STD-ST-000001 | Nexus Standards NS-1 – the UNI and artefact catalogue | pêşnûme |
NXS-STD-SW-000002 | UNI command-line tool (validate, parse, next, mint, catalogue, export) – reference implementation | pêşnûme |
NXS-STD-SC-000001 | UNI artefact record schema v1 | pêşnûme |
NXS-STD-ST-000002 | Open-standards and open-source stack under the UNI | pêşnûme |
NXS-STD-SW-000005 | UNI data profile (STAC, DCAT, PROV-O crosswalks), NS-3b | pêşnûme |
NXS-STD-ST-000003 | Nexus Standards NS-3 – risk record UNIs (grammar, legacy crosswalk, allocation authority) | pêşnûme |
NXS-STD-ST-000012 | Nexus Standards NS-12 – software, models and AI/ML artefacts | pêşnûme |
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.
Lêgerînerê pêvajoyê · Standards · kod bike û rast bike
Çerxa jiyanê ya standardê
17 gav·6 qonax
Standards · kod bike û rast bike
Çerxa jiyanê ya standardê
Çerxa jiyanê ya standardê · Rêça NS-13 · Kanalên beşdariyê · Rêça IETF · Rêça W3C · Rêça OGC · Rêça OASIS · Qonaxên ISO û IEC · Lihevbûn · Çerxa jiyanê ya tomarê · Rêkirin · Çavdêrî.
Dîtinên çerxê dibin pêşniyarên guhertinê, Encûmena Standardên Cîhanî piştî banga dawî ya giştî dipejirîne, û her welat pejirandina xwe bi xwe diyar dike.
01 Rêkirina mîsyonan
- 01Route missions to standards and profilesStep · Nexus StandardsNexus Standards routes each candidate mission to the standards and profiles that apply.
02 Profîl û lihevhatin
- 02Profîlên mîsyonan pêk bîneGav · Nexus StandardsNexus Standards profîlên mîsyonan pêk tîne û her pejirandineke neteweyî ya ku mîsyon xwe dispêrinê tomar dike.
- 03Derketinên avakirinê li hember profîlan piştrast bikeGav · Nexus StandardsNexus Standards encamên avakirinê li hember profîlên pêkhatî piştrast dike û delîlan tomar dike.
- 04Çavdêriya lihevhatinê bike û delîlên mohrkirî tomar bikeGav · Nexus StandardsDi Hefteya Çalakiyê de Nexus Standards lihevhatinê dişopîne û cudabûnan tomar dike.
03 Pêşniyar û nirxandin
- 05Dûrketin û rastkirin dibin pêşniyarên guhertinêGav · Nexus StandardsDûrketin dibin pêşniyarên guhertinê, û rastkirin wekî guhertinek di delîlan de tê tomarkirin.
- 06Encamên çerxê dibin pêşniyarên guhertinêGav · Nexus StandardsDîtinên çerxekê dibin pêşniyarên guhertinê: dîtinên rêbaz û rastkirinê ji rêzeya Pergalên Stratejîk (F06) û babetên dosyayê ji Nexus…
- 07Bi eşkereyî amade bike û biguherîneGav · Komîte û komên xebatêKomîteyên teknîkî û komên xebatê standardan di pêvajoya vekirî ya NS-13 de amade dikin û nû dikin.
- 08Nirxandin ber bi biryara encûmenê veGav · Nexus StandardsNexus Standards pêşniyarên guhertinê bi rêya nirxandinê ber bi biryara encûmenê ve dibe.
04 Biryara encûmenê
- 09Banga dawî ya giştîGav · Encûmena Cîhanî ya StandardanEncûmena Cîhanî ya Standardan piştî banga dawî ya nod-rojî bi piraniya du-ji-sê dipejirîne.
- 10Pejirandina cîhanî ya standardekêBiryar · Encûmena Cîhanî ya StandardanEncûmena Standardên Cîhanî piştî banga dawî ya giştî li ser pejirandina her standardê biryar dide.
05 Biweşîne û nas bike
- 11Assign a UNI and publishStep · Secretariat (GCRI Canada)Nexus Standards assigns UNIs and deposits publications under the publisher’s process.
- 12UNI nas dike û qet sertîfîka nadeTomar · Nexus StandardsHer tiştekî sala bernameyê nasnavekî hildigire, UNI-yek di bin NS-1 de, da ku were jêgirtin, guhertoya wê were girtin û were çareserkirin.
- 13Guhertinên pejirandî yên salê biweşîneGav · Nexus StandardsDi nûkirinê de Nexus Standards guhertinên pejirandî yên salê û rewşa pejirandina neteweyî diweşîne.
06 Pejirandin û sepandina neteweyî
- 14Pejirandina neteweyî ji aliyê Encûmena Neteweyî ya Standardan veBiryar · Encûmena Neteweyî ya StandardanEncûmena Standardên Neteweyî ya her welatî li ser pejirandina neteweyî biryar dide: wekî xwe pejirandin, bi profîlekê pejirandin (NS-16), adaptekirin, an tenê referans.
- 15Standardên pejirandî digihîjin kurs û weşananGav · Nexus StandardsHer standard an profîleke pejirandî dibe modulek kursê li Risk Academy (F09), û standard di weşanên Reports de têne sepandin (R1).
- 16Pejirandin ji bo her herêma desthilatê dawî yeStandard · Encûmena Neteweyî ya StandardanPejirandin ji bo her herêma desthilatê dawî ye, û GSC tu vetoyê li ser biryareke neteweyî nîne. Tu dezgeheke cîhanî vetoyê nagire.
- 17Tomarên pejirandina neteweyîTomar · Nexus StandardsProfîlên mîsyonê yên pêkhatî û tomarên pejirandina neteweyî di amadekirina amadebûnê de diçin Foundry (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
| Gav | Qonax | Xebitandin | Kî | Decision rule | Tomar | 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 | Pêşniyar | 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 | Pejirandin | 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 | Pejirandin | 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.
Pergal û girêdan
- Ji bo pêşdebiran
- Pêşdebir û API Girêdan
- Qada ceribandinê û daneyên simulekirî Girêdan
- Software and supply chain Coupling
- Bernameya lihevhatinê Girêdan
Kontrol
NS-1UNI û kataloga berheman (rêziman v0.2: beşên qad, sektor, herêm û jîngehê)NS-3UNIyên tomara xetereyê (rêzimanî, nexşeya veguhastina ji pergala kevin, desthilata veqetandinê)NS-3bProfîla metadata ya daneset û berheman (STAC, DCAT, PROV-O)NS-11Piştrastkirin û çavdêrî (delîl, erêkirin, çavdêriya lihevhatina zero-trust)NS-12Berhemên nermalav, model û AI/ML (zincîra dabînkirinê, kartên modelê, pelên koma daneyan)NRS-C11Lihevhatin, piştrastkirin û parastina standardanNRS-S5System profile: NXS-NXQ (Software, models and capability lifecycle)NRS-A1Standard wek kod: standard, pêdivî û testên ku makîne dikare bixwîneNRS-S8System profile: NXS-EWS (Multi-hazard monitoring and warning)NRS-T8Xetera yekparebûna nermalav û zincîra dabînkirinêNRS-A6Kîtên bicihkirin û pejirandinê bi yek klîkê
Çavdêrî
- World Development Indicators (listed for reference)
- USGS earthquake GeoJSON summary feeds (listed for reference)
- Proportion of individuals using the Internet
Standardên ku têne sepandin
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.
Girêdanên pergalî
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.
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.
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.
- Zindî
- 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
- Radestkirin
- 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.
Nîşander
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.
Sektor 0
This area serves all sectors through the areas it is coupled with.
Çavkanî
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.
Kurs
Dîsîplîn
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.
Lêkolîn û delîl
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
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
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 AlliancePerwerde û rahênan
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 pageTêgehên sereke
- UNI
- Unique Nexus Identifier: a persistent identifier that resolves an artefact to its record.
- pêşniyarkirî
- 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.
Pirs û bersiv.
What is the status of the For developers area?
How are data sources presented?
How can this brief be amended?
Ji vê rûpelê delîl bidin.
Reports weşana sê mehane ya Konsorsiyûmê ye. Tiştê ku tu li ser vê mijarê dizanî dikare di çapa pêş de bibe delîl, dosya an rastkirin, bi navê te û di bin CC BY 4.0 de weşandî li cihê ku karê te bi xwe be.
- E-nameDergeha GW-STDJi vê rûpelê bişîneDelîl, rastkirin, doz, rêbaz, nirxandin, werger an têketina profîlê. Bi etîketa vê rûpelê digihîje, da ku edîtorê xwedî wê bistîne.
- 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.
Tu carî daneyên şexsî, hûrgiliyên binesaza hesas an tiştekî ku mafê we yê parvekirinê tune ne neşînin. Beşdarî berî bikaranînê tê nirxandin; şandina wê nivîskarî an mafên edîtorî nade û sponsorî tu carî encamekê nakire.
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.
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.