Skip to content
StandardsOpen Infrastructure and DevelopersInfrastructure services
Area · in the catalogue (planned)

Ontplooiingsdienste

Provides deployment of systems and components that conform to the standards, as catalogued contexts: blueprints, reproducible builds, signed images with SBOMs and SLSA provenance, verification at admission, and a contextual UNI and deployment record for every instance, so that what runs is traceable to what was built. Each artefact of the area carries a UNI (Unique Nexus Identifier).

Ontplooiingsdienste
What this area is built from: the Nexus Standards it applies, the open standards it names and the data and feeds it reads, then the areas its record couples it with (marked).Source: the Nexus Standards registry: the area record.
  • Nexus Standards: NS-9, NS-11, NS-12.
  • Open standards: Supply-chain Levels for Software Artifacts (SLSA); Sigstore (Cosign, Fulcio, Rekor); CycloneDX Bill of Materials (ECMA-424); OCI Image and Distribution Specifications; The Update Framework (TUF).
  • Data and feeds: endoflife.date API; OSV.dev vulnerability API; deps.dev API.
  • Couples with: Software and supply chain; Identification (the UNI); Monitoring services.
Nexus Standards
3
NS-9, NS-11, NS-12
Open standards
5
named, never copied
Data and feeds
3
listed for reference
Couplings
3
with other areas
Status
Proposedin the catalogue · planned · scope FAC
Last reviewed
area profile
Cite this page

Nexus Standards (2026). Deployment services: area brief, Open Infrastructure and Developers programme. Proposed. https://nexustandards.com/open-infrastructure/deployment-services/ · UNI NXS-STD-DC-000003. Last reviewed 17 October 2026.

Download the profile

Files include the credits and the licence statement and are generated in the browser; no data is transmitted. Downloads require JavaScript.

01Omvang

Scope and boundaries

An area of the Open Infrastructure and Developers programme (infrastructure services). The area profile sets out 4 matters in scope and 2 matters addressed by other areas.

In scope 4

  • Blueprints, build pipelines and the application catalogue lifecycle
  • Signing, SBOM generation and provenance at build
  • Admission policies and verification at deploy
  • Deployment records with contextual UNIs

Out of scope 2

  • Managed hosting for third parties
  • Operating national infrastructure on behalf of governments

Jurisdictions Application in each jurisdiction is a national decision, taken by the National Standards Council (NSC) with the competent national authorities.

02Standards architecture

Foundation, referenced and implementing layers

The standards architecture of this context, from the foundation standards to the open standards referenced (grouped by type of relation) and the services and data sources that build on them.

The interactive view requires JavaScript; the sections below present the same records.

03Proses

The service pipeline

A request reaches the service with an explicit context; inputs are identified (NS-1) and validated against Supply-chain Levels for Software Artifacts (SLSA); the service processes them and writes records with provenance; results are published, resolved and monitored, and a correction flows back through the same path. Nexus Standards applied: NS-9, NS-12, NS-11. 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 (11). Records and artefacts are cited by UNI (Unique Nexus Identifier) and version.

Prosesverkenner · Standards · kodifiseer en korrigeer

Lewensiklus van 'n standaard

17 stappe6 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.

  1. 01 Lei sendings

    1. 01Lei sendings na standaarde en profieleStap · Nexus StandardsNexus Standards lei elke kandidaatsending na die standaarde en profiele wat van toepassing is.
  2. 02 Profiele en ooreenstemming

    1. 02Stel sendingprofiele saamStap · Nexus StandardsNexus Standards stel sendingprofiele saam en teken enige nasionale aanvaarding aan waarvan die sendings afhang.
    2. 03Valideer bou-uitsette teen die profieleStap · Nexus StandardsNexus Standards valideer bou-uitsette teen die saamgestelde profiele en teken die bewyse aan.
    3. 04Moniteer konformiteit en teken verseëlde bewyse aanStap · Nexus StandardsGedurende die Aksieweek monitor Nexus Standards konformiteit en teken afwykings aan.
  3. 03 Voorstelle en beoordeling

    1. 05Afwykings en regstellings word veranderingsvoorstelleStap · Nexus StandardsAfwykings word veranderingsvoorstelle, en die regstelling word as 'n verandering aan die bewyse aangeteken.
    2. 06Siklusbevindings word veranderingsvoorstelleStap · Nexus StandardsBevindings uit 'n siklus word veranderingsvoorstelle: metode- en korreksiebevindings uit Verslae (F06) en dokketitems uit Nexus…
    3. 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.
    4. 08Beoordeel met die oog op 'n raadsbesluitStap · Nexus StandardsNexus Standards beweeg veranderingsvoorstelle deur beoordeling met die oog op 'n raadsbesluit.
  4. 04 Raadsbesluit

    1. 09Openbare laaste oproepStap · Global Standards CouncilDie Global Standards Council aanvaar by 'n tweederdemeerderheid ná 'n laaste oproep van negentig dae.
    2. 10Wêreldwye aanvaarding van 'n standaardBesluit · Global Standards CouncilDie Wêreldwye Standaarderaad besluit oor die aanvaarding van elke standaard ná 'n openbare laaste oproep.
  5. 05 Publiseer en identifiseer

    1. 11Assign a UNI and publishStep · Secretariat (GCRI Canada)Nexus Standards assigns UNIs and deposits publications under the publisher’s process.
    2. 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.
    3. 13Publiseer die jaar se aanvaarde veranderingeStap · Nexus StandardsBy hernuwing publiseer Nexus Standards die jaar se aanvaarde veranderinge en die nasionale aanvaardingstatus.
  6. 06 Nasionale aanvaarding en toepassing

    1. 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.
    2. 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.
    3. 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.
    4. 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
Process · the service pipeline8 operations · 5 phases
StepPhaseOperationWhoDecision ruleRecordImplements
01RequestRequest (start). The service covers: Blueprints, build pipelines and the application catalogue lifecycle, Signing, SBOM generation and provenance at build and Admission policies and verification at deploy.a client, a person or a machinethe context is explicit in the request or on the record, never inferreda request naming its context and inputsNS16-R20
02RequestIdentify inputs (step). Every input is resolved before it is used; an unresolved input is a typed refusal.the serviceinputs are cited by UNI and versioninputs resolved to their UNIs and versionsNS1-R5, NS2-R2, NS0-P12
03ValidationValidate SLSA (gate). Open standards of this area: Supply-chain Levels for Software Artifacts (SLSA), Sigstore (Cosign, Fulcio, Rekor), CycloneDX Bill of Materials (ECMA-424) and OCI Image and Distribution Specifications.the service’s validatorvalidated against the open standard’s own schema or validator where one existsa validation run against Supply-chain Levels for Software Artifacts (SLSA) and Sigstore (Cosign, Fulcio, Rekor)NS14-R2
04ProcessingProcess (model). Processing is reproducible from the inputs, the method version and the configuration.the servicethe method and version are recorded with the resultSigning, SBOM generation and provenance at buildNS12-R1
05ProcessingWrite records (record). Results are written append-only; a correction adds a version.the serviceevery result carries what it was derived fromresult records with provenance and a record UNINS0-P7, NS1-R3
06PublicationPublish and resolve (step). Results are discoverable and citable by UNI.the servicewrites return the allocated UNI; citations resolveresults reachable through the resolver, with the X-Nexus-UNI headerNS1-R5, NS2-R5
07MoniteringMonitor (exercise). Data sources the service reads: endoflife.date API, OSV.dev vulnerability API and deps.dev API. Data sources are listed for reference; live data is displayed once licence review is complete.the monitoring servicemonitoring records are observations with record UNIsobservations of availability, drift and SLSA v1.0 Build L3NS11-R4
08MoniteringCorrection (end). Products that used a corrected record are listed and recomputed.the data stewarda correction never overwrites; dependent results are replayeda correction record that reaches every dependent resultNS1-R3, NS2-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: Supply-chain Levels for Software Artifacts (SLSA) · Sigstore (Cosign, Fulcio, Rekor) · NS-9: Contextual UNIs · NS-12: Software, model and AI/ML artefacts.

05System model

How a shock travels through this system

A system model of this area built from the registry: 4 systems, 4 sectors, 9 controls, 3 feeds, 2 indicators. 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.

Controls

  • NS-9 Kontekstuele UNI's (ontplooiings, instansies, programinstansies)
  • NS-12 Sagteware-, model- en KI/ML-artefakte (voorsieningsketting, modelkaarte, datastelblaaie)
  • NS-11 Verifikasie en monitering (getuienis, attestasies, zero-trust-ooreenstemmingwaarneming)
  • NRS-A6 Een-klik-ontplooiing en aanvaardingstelle
  • NRS-H106 Hazard family: Space technology and orbital infrastructure (NHS-1 tech.space-systems)
  • NRS-H47 Gevarefamilie: Strukturele en siviele faling (NHS-1 infra.structural)
  • NRS-H34 Gevarefamilie: Faling van afval en residu (NHS-1 poll.waste)
  • NRS-H93 Gevarefamilie: Identiteits-, vertrouens- en kriptografiese faling (NHS-1 cyber.identity)
  • NRS-S16 System profile: NXS-FAC (Blueprints, builds and signing)

Observation

  • endoflife.date API (listed for reference)
  • OSV.dev vulnerability API (listed for reference)
  • deps.dev API (listed for reference)
  • Hardened build platform with non-forgeable provenance
  • Project pins dependencies by hash (learning signal)
06Sistemiese koppelings

Sistemiese koppelings

3 couplings link this area to other areas and programmes, each with the mechanism of the link.

  1. Software and supply chainTrust, Verification and AssuranceAdmission verifies signatures, SBOMs and provenance predicates defined by NS-12 and refuses images that fail.
  2. Identification (the UNI)Data and EvidenceEach deployment receives a contextual UNI (NS-9, category DP) and records its own status as the host’s statement.
  3. Monitoring servicesOpen Infrastructure and DevelopersEvery deployed context registers its long-lived services so monitoring can observe freshness, drift and outages.
07Standaarde

Standards that apply

The area profile lists 3 Nexus Standards; the registry lists NS-9, NS-12 for this area. Each is a proposed standard under development.

  1. 01

    NS-9 · Contextual UNIs (deployments, instances, programme instances)

    Status: proposed · 5 requirements stated. Read NS-9 · Requirements for this area.

  2. 02

    NS-12 · Software, model and AI/ML artefacts (supply chain, model cards, dataset sheets)

    Status: proposed · 4 requirements stated. Read NS-12 · Requirements for this area.

  3. 03

    NS-11 · Verification and monitoring (evidence, attestations, zero-trust conformance observation)

    Status: proposed · 6 requirements stated. Read NS-11 · Requirements for this area.

09Data sources

Data sources

3 data sources named in the area profile, each with provider, licence, update frequency and delivery path.

Data sources

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
0
licence terms recorded
Proposed for the register
3
licence terms to be recorded
Delivery
1 governed service · 0 plugin · 0 browser · 1 snapshot · 1 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
  • deps.dev APIfor reference

    Google Open Source Insights · continuous

    CC BY 4.0 (data)

    governed data serviceproposed for the data register.

  • endoflife.date APIfor reference

    endoflife.date community · continuous

    MIT

    build-time snapshotproposed for the data register

  • OSV.dev vulnerability APIfor reference

    OpenSSF / Google · continuous

    Per-source licences aggregated by OSV.dev (many CC BY 4.0 or CC0)

    listed for referenceproposed for the data register.

10Werkgroep

Working group charter

A proposed charter for this area, open to institutions and experts.

Omvang

Maintain deployment records, admission policies and build provenance requirements.

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).

Deliverables · 3
  1. Deployment record profile (NS-9 DP)
  2. Admission policy clause pack
  3. Reference pipeline with SLSA provenance
Liaison targets · 3
  • OpenSSF liaison sought
  • Open Container Initiative liaison sought
  • CNCF TAG Security liaison sought
11Aanwysers

Aanwysers

The area profile names 2 indicators, each with its framework and code.

12Gereedheid

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.

Evidence pathway

GCRI Canada

GCRI Canada runs analyses only on deployments whose deployment record and image digests are catalogued.

Read the evidence pathway

Erkenningsroete

Die Global Risks Forum (GRF)

GRF recognises deployments by their contextual UNI and published deployment record.

Read the recognition pathway

Kapitaalroete

Die Global Risks Alliance (GRA)

GRA treats deployments without verified provenance as operational risk in any capital-readiness view.

Read the capital pathway

Each institution determines under its own rules what it accepts as evidence; a pathway reading is neither an approval nor investment advice.

13Research questions

Open research questions

2 questions identified as priorities for the working group.

  1. Reproducible container builds for scientific images with large binary dependencies.
  2. Deploying signed updates to intermittently connected national hosts.
14Restricted standards

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.

15Teikengroepe

Intended users

The area profile identifies 4 user communities.

  1. DevOps and platform engineers
  2. Release managers
  3. National host operators
  4. Security teams
16Hazards and sectors

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.

17Registry

Registry listing and depth pages

This area is in the catalogue (status: planned; scope FAC; 2 crosswalk domains). It has five depth pages and a register crosswalk of its domains.

Crosswalk graph · deployment servicesNexus Standards registry
Deployment services: crosswalk to external standards37 nodes on four orbits (Nexus Standards and implementing repositories at the centre, then domains, external standards and issuing bodies), joined by 38 recorded relations.
Nexus StandardsDomainsExternal standardsIssuing bodiesImplementing repositories
The crosswalk as a table: 17 external standards by domain
DomainExternal standardIssuing bodyRelation
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
Supply chains and logisticsISO 28000:2022 Security and resilience – Security…ISO/TC 292crosswalk
Supply chains and logisticsISO/IEC 27036-2:2022 Cybersecurity – Supplier…ISO/IEC JTC 1/SC 27cite
Supply chains and logisticsNIST SP 800-161 Rev. 1 Cybersecurity Supply Chain Risk…NISTcite
Supply chains and logisticsOASIS Common Security Advisory Framework (CSAF) Version 2.0OASIS CSAF TCcite
Supply chains and logisticsOpenVEX specificationOpenVEX community (OpenSSF project)cite
Supply chains and logisticsSupply-chain Levels for Software Artifacts (SLSA)OpenSSF (Linux Foundation)adopt
Supply chains and logisticsWCO SAFE Framework of Standards to Secure and Facilitate…World Customs Organizationcite

Nexus Standards in the graph: NS-9, NS-12. A relation is a register entry, never a compliance claim.

2 Nexus Standards · 2 domains · 17 external standards · 16 issuing bodies · 0 implementing repositories. Relations (adopt, profile, crosswalk, cite) are as recorded in the register; names and standards remain with their stewards.

Crosswalk graph37 nodes and 38 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.

Areas carry no geography of their own; the map shows where the bodies that issue the area’s external standards are based.

Standards globe · Deployment services: issuing bodiesNexus Standards registry
Seats of the bodies that issue the external standards in the registerA world map with coastlines and equal-area cells at the public seats of 10 issuing bodies and one dot per seat. 17 register entries.
Issuing bodies’ seats (10)Equal-area cells (4); darker, more register entriesProgrammes, repositories and standards: not mapped
Issuing bodies and their seats (10)
BodySeatRegister entries
OpenSSFSan Francisco, California, United States2
ISO/IEC JTC 1/SC 27Geneva, Switzerland1
ISO/TC 292Geneva, Switzerland1
NISTGaithersburg, Maryland, United States1
OASIS CSAF TCWoburn, Massachusetts, United States1
OpenAPI Initiative (Linux Foundation)San Francisco, California, United States1
OpenSSF (Linux Foundation)San Francisco, California, United States1
OpenVEX community (OpenSSF project)San Francisco, California, United States1
OWASP CycloneDX; Ecma International TC54Geneva, Switzerland1
SPDX project (Linux Foundation); ISO/IEC JTC 1San Francisco, California, United States1

Issuing bodies are shown at the city of their public seat. The 1 programmes, 0 implementing repositories and 19 Nexus Standards have no location and are not mapped · 6 issuing bodies have no single public seat and are listed without a location: CodeMeta project; Citation File Format project; JSON Schema organisation; World Customs Organization; Open Container Initiative; Reproducible Builds project.

Standards globe10 issuing bodies with a public seat and 17 register entries, shown in equal-area cells at four levels of detail. Seats are placed at city coordinates; programme areas, implementations and standards have no location and are not drawn. A still world map is shown where scripts are unavailable.

18Bronne

Bronne

3 references from peer-reviewed and official publications cited in the area profile, linked at the publishers’ own sites.

19Research hub

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 termsdeployment; reproducible deployment; infrastructure as code; Sigstore; CycloneDX Bill of Materialscombined with: risk; disaster; early warning; research softwareDerived 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.

20Onderwys en opleiding

Risk Academy courses and disciplines

1 course 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.

21Oor die netwerk

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.

Governance, 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 Forum

Capital, 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 Alliance
22Kernterme

Kernterme

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.
profile
Relation in which a Nexus profile narrows or extends the external standard for a defined use, validated with the issuing body’s own tools where these exist.
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.
24Navorsing

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

Related standards and frameworks

Search terms, derived from the title and scope of the area: deployment; reproducible deployment; infrastructure as code; combined with: risk; disaster; early warning; research software. With JavaScript enabled, recent works matching these terms are listed from OpenAlex and Crossref.

25Vrae

Questions and answers.

What is the status of the Deployment services area?
The area profile is a proposal to the Nexus Standards registry, and the area is in the catalogue. Standards are adopted by the Global Standards Council after last call; in each country, adoption is a decision of its National Standards Council (NSC).
How are data sources presented?
Each data source is listed with its provider, licence, update frequency and delivery path, and links to the provider’s own publication.
How can this brief be amended?
Through a public change record under NS-13: a proposed amendment to the area profile or the registry, decided by the editors with written reasons.
VerslaeDra by

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.

Nexus Standards
Standaarde

Contribute to Deployment services

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.