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

Wasanidi programu na API

Publishes the reference tools, APIs, schemas and open-source components on which adopters build: OpenAPI 3.1 and AsyncAPI 3.0 contracts, JSON Schemas, software development kits in several languages with bit-identical UNI grammar and canonical JSON digests, the reference command-line tool, and editor and QGIS plugins, all under Apache-2.0. Each artefact of the area carries a UNI (Unique Nexus Identifier).

Wasanidi programu na API
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-1, NS-6, NS-12.
  • Open standards: OpenAPI Specification 3.1; AsyncAPI Specification 3.0; JSON Schema 2020-12; CodeMeta; RFC 8594 The Sunset HTTP Header Field; Semantic Versioning 2.0.0.
  • Data and feeds: APIs.guru OpenAPI directory; deps.dev API; GitHub REST API (releases).
  • Couples with: Conformance test suites; Registries and the resolver; Sandbox and simulated data.
Nexus Standards
3
NS-1, NS-6, NS-12
Open standards
6
named, never copied
Data and feeds
3
listed for reference
Couplings
3
with other areas
Hali
Proposedin the catalogue · planned · scope NXQ
Last reviewed
area profile
Cite this page

Nexus Standards (2026). Developers and APIs: area brief, Open Infrastructure and Developers programme. Proposed. https://nexustandards.com/open-infrastructure/developer-and-api/ · 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.

01Wigo

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

  • OpenAPI, AsyncAPI and Protobuf contracts
  • Software development kits (TypeScript, Python, R, Go, Rust) and command-line tool
  • Editor, CI and QGIS integrations
  • API versioning, deprecation and Sunset headers

Out of scope 2

  • Commercial support contracts
  • Hosting third-party applications

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.

03Mchakato

The service pipeline

A request reaches the service with an explicit context; inputs are identified (NS-1) and validated against OpenAPI Specification 3.1; 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-6, NS-12, NS-1. 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.

Kichunguzi cha michakato · Standards · ratibu na sahihisha

Mzunguko wa maisha wa kiwango

Hatua 17Awamu 6

Standards · ratibu na sahihisha

Mzunguko wa maisha wa kiwango

Mzunguko wa maisha wa kiwango · Njia ya NS-13 · Njia za michango · Njia ya IETF · Njia ya W3C · Njia ya OGC · Njia ya OASIS · Hatua za ISO na IEC · Ulinganifu · Mzunguko wa maisha wa rekodi · Uelekezaji · Ufuatiliaji.

Matokeo ya mzunguko huwa mapendekezo ya mabadiliko, Baraza la Viwango la Dunia hupitisha baada ya mwito wa mwisho wa umma, na kila nchi huamua upitishaji wake.

  1. 01 Elekeza misheni

    1. 01Elekeza misheni kwenye viwango na wasifuHatua · Nexus StandardsNexus Standards huelekeza kila misheni inayopendekezwa kwenye viwango na wasifu vinavyotumika.
  2. 02 Wasifu na ulinganifu

    1. 02Kusanya wasifu wa misheniHatua · Nexus StandardsNexus Standards hukusanya wasifu wa misheni na hurekodi upitishaji wowote wa kitaifa ambao misheni hutegemea.
    2. 03Thibitisha matokeo ya ujenzi dhidi ya wasifuHatua · Nexus StandardsNexus Standards huthibitisha matokeo ya ujenzi dhidi ya wasifu ulioundwa na kurekodi ushahidi.
    3. 04Fuatilia ulinganifu na urekodi ushahidi uliofungwaHatua · Nexus StandardsWakati wa Wiki ya Utekelezaji Nexus Standards hufuatilia ulinganifu na kurekodi mikengeuko.
  3. 03 Mapendekezo na mapitio

    1. 05Mikengeuko na marekebisho huwa mapendekezo ya mabadilikoHatua · Nexus StandardsMikengeuko huwa mapendekezo ya mabadiliko, na marekebisho hurekodiwa kama mabadiliko kwa ushahidi.
    2. 06Matokeo ya mzunguko huwa mapendekezo ya mabadilikoHatua · Nexus StandardsMatokeo ya mzunguko huwa mapendekezo ya mabadiliko: matokeo ya mbinu na masahihisho kutoka Ripoti (F06) na vipengele vya orodha kutoka Nexus…
    3. 07Andaa na urekebishe hadharaniHatua · Kamati na vikundi kaziKamati za kiufundi na vikundi kazi huandaa rasimu na kurekebisha viwango katika mchakato wazi wa NS-13.
    4. 08Pitia kuelekea uamuzi wa barazaHatua · Nexus StandardsNexus Standards huendeleza mapendekezo ya mabadiliko kupitia mapitio kuelekea uamuzi wa baraza.
  4. 04 Uamuzi wa Baraza

    1. 09Mwito wa mwisho wa ummaHatua · Baraza la Viwango la KimataifaBaraza la Viwango la Kimataifa hupitisha kwa wingi wa theluthi mbili baada ya mwito wa mwisho wa siku tisini.
    2. 10Kupitishwa kwa kiwango dunianiUamuzi · Global Standards CouncilBaraza la Viwango la Dunia huamua upitishaji wa kila kiwango baada ya mwito wa mwisho wa umma.
  5. 05 Chapisha na utambulishe

    1. 11Assign a UNI and publishStep · Secretariat (GCRI Canada)Nexus Standards assigns UNIs and deposits publications under the publisher’s process.
    2. 12UNI hutambulisha na kamwe haitoi chetiRekodi · Nexus StandardsKila kitu cha mwaka wa programu kina kitambulisho kimoja, UNI chini ya NS-1, ili kiweze kutajwa, kupewa matoleo na kutatuliwa.
    3. 13Chapisha mabadiliko yaliyopitishwa ya mwakaHatua · Nexus StandardsWakati wa upyaishaji Nexus Standards huchapisha mabadiliko yaliyopitishwa ya mwaka na hali ya upitishaji wa kitaifa.
  6. 06 Kupitishwa na kutumika kitaifa

    1. 14Kupitishwa kitaifa na Baraza la Viwango la KitaifaUamuzi · Baraza la Viwango la KitaifaBaraza la Viwango la Kitaifa la kila nchi huamua upitishaji wa kitaifa: kupitisha kama ilivyo, kupitisha kwa wasifu (NS-16), kurekebisha, au kurejelea tu.
    2. 15Viwango vilivyopitishwa hufikia kozi na matoleoHatua · Nexus StandardsKila kiwango au wasifu uliopitishwa huwa moduli ya kozi katika Risk Academy (F09), na viwango hutumika katika matoleo ya Reports (R1).
    3. 16Upitishaji ni wa mwisho kwa kila mamlaka ya kisheriaKiwango · Baraza la Kitaifa la ViwangoUpitishaji ni wa mwisho kwa kila mamlaka ya kisheria, na GSC haina kura ya turufu juu ya uamuzi wa kitaifa. Hakuna chombo cha kimataifa chenye kura ya turufu.
    4. 17Rekodi za kupitishwa kitaifaRekodi · Nexus StandardsWasifu wa misheni ulioundwa na rekodi za upitishaji wa kitaifa huenda kwa Foundry wakati wa maandalizi ya utayari (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: OpenAPI, AsyncAPI and Protobuf contracts, Software development kits (TypeScript, Python, R, Go, Rust) and command-line tool and Editor, CI and QGIS integrations.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 OpenAPI (gate). Open standards of this area: OpenAPI Specification 3.1, AsyncAPI Specification 3.0, JSON Schema 2020-12 and CodeMeta.the service’s validatorvalidated against the open standard’s own schema or validator where one existsa validation run against OpenAPI Specification 3.1 and AsyncAPI Specification 3.0NS14-R2
04ProcessingProcess (model). Processing is reproducible from the inputs, the method version and the configuration.the servicethe method and version are recorded with the resultSoftware development kits (TypeScript, Python, R, Go, Rust) and command-line toolNS12-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
07UfuatiliajiMonitor (exercise). Data sources the service reads: APIs.guru OpenAPI directory, deps.dev API and GitHub REST API (releases). 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 OpenSSF Scorecard MaintainedNS11-R4
08UfuatiliajiCorrection (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: OpenAPI Specification 3.1 · AsyncAPI Specification 3.0 · NS-6: Surface wiring · 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, 6 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-6 Uunganishaji wa nyuso (kichwa cha API, asili ya paneli, pasipoti, OpenAPI)
  • NS-12 Vitu vya programu, miundo na AI/ML (mnyororo wa ugavi, kadi za miundo, karatasi za seti za data)
  • NS-1UNI na katalogi ya vitu (sarufi v0.2: sehemu za kikoa, sekta, kanda na mazingira)
  • NRS-A3 Kiolesura cha mawakala kwa viwango
  • NRS-A6 Usambazaji kwa mbofyo mmoja na vifurushi vya upitishaji
  • NRS-C4 Modeli ya data za hatari, vitambulisho na ubadilishanaji

Observation

  • APIs.guru OpenAPI directory (listed for reference)
  • deps.dev API (listed for reference)
  • GitHub REST API (releases) (listed for reference)
  • Project is actively maintained (learning signal)
  • Metadata is accessed through standardised protocol
06Viwango

Standards that apply

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

  1. 01

    NS-6 · Surface wiring (API header, panel provenance, passports, OpenAPI)

    Status: in progress · 0 requirements stated. Read NS-6 · 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-1 · The UNI and the artefact catalogue (grammar v0.2: domain, sector, region and environment segments)

    Status: proposed · 10 requirements stated. Read NS-1 · Requirements for this area.

07Miunganiko ya kimfumo

Miunganiko ya kimfumo

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

  1. Conformance test suitesTrust, Verification and AssuranceSDKs are accepted only when they pass the cross-language digest vector suite and the corpus tests.
  2. Registries and the resolverOpen Infrastructure and DevelopersClients resolve UNIs and read records through the resolver API with X-Nexus-UNI headers (NS-6).
  3. Sandbox and simulated dataOpen Infrastructure and DevelopersDevelopers test every API against synthetic data before working with governed records.
08Data 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.

Hai
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 · 1 plugin · 0 browser · 1 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
  • APIs.guru OpenAPI directoryfor reference

    APIs.guru · continuous

    CC0 1.0

    build-time snapshotproposed for the data register

  • deps.dev APIfor reference

    Google Open Source Insights · continuous

    CC BY 4.0 (data)

    governed data serviceproposed for the data register.

  • GitHub REST API (releases)for reference

    GitHub · per release

    GitHub terms of service; repository content under its own licences.

    integration pluginproposed for the data register

10Kikundi kazi

Working group charter

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

Wigo

Maintain API contracts, software development kits and developer tooling.

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. OpenAPI and AsyncAPI contracts with linting
  2. Cross-language digest vector suite
  3. SDK release and deprecation policy
Liaison targets · 3
  • OpenAPI Initiative liaison sought
  • AsyncAPI Initiative liaison sought
  • OSGeo / QGIS project liaison sought
11Viashiria

Viashiria

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

12Utayari

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 uses the generated software development kits so that digests and UNIs match the reference implementation.

Read the evidence pathway

Njia ya utambuzi

Global Risks Forum (GRF)

GRF recognises contributions to the open tooling by their merged, DCO-signed commits.

Read the recognition pathway

Njia ya mtaji

Global Risks Alliance (GRA)

GRA reviewers can verify receipts and attestations independently with the open command-line tool.

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. Bit-identical canonical JSON across languages with different number and Unicode handling.
  2. Keeping five software development kits in step with additive API changes without breaking clients pinned to earlier versions.
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.

15Hadhira

Intended users

The area profile identifies 4 user communities.

  1. Software developers
  2. Research software engineers
  3. GIS developers
  4. Integrators at partner institutions
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.

Sekta 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 NXQ; 1 crosswalk domain). It has five depth pages and a register crosswalk of its domains.

Crosswalk graph · developers and apisNexus Standards registry
Developers and APIs: crosswalk to external standards22 nodes on four orbits (Nexus Standards and implementing repositories at the centre, then domains, external standards and issuing bodies), joined by 22 recorded relations.
Nexus StandardsDomainsExternal standardsIssuing bodiesImplementing repositories
The crosswalk as a table: 10 external standards by domain
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

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

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

Crosswalk graph22 nodes and 22 links from the registry of external standards, programme areas and implementations (the external standards register, the consumers register. Relations (adopt, profile, crosswalk, cite) are shown as recorded in the register.

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

Standards globe · Developers and APIs: 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 4 issuing bodies and one dot per seat. 10 register entries.
Issuing bodies’ seats (4)Equal-area cells (2); darker, more register entriesProgrammes, repositories and standards: not mapped
Issuing bodies and their seats (4)
BodySeatRegister entries
OpenSSFSan Francisco, California, United States2
OpenAPI Initiative (Linux Foundation)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 · 5 issuing bodies have no single public seat and are listed without a location: CodeMeta project; Citation File Format project; JSON Schema organisation; Open Container Initiative; Reproducible Builds project.

Standards globe4 issuing bodies with a public seat and 10 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.

18Vyanzo

Vyanzo

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

  1. peer-reviewedIntroducing the FAIR Principles for research softwareScientific Data · 2022
  2. peer-reviewedTowards FAIR principles for research softwareData Science · 2020
  3. standardOpenAPI Specification v3.1.1OpenAPI Initiative · 2024
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 termsweb API; API design; open API; research software; OpenAPI Specification; AsyncAPI Specificationcombined with: risk; disaster; hazard; resilience; early warningDerived 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.

21Katika mtandao mzima

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

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

Global Risks Alliance (GRA)

Industry programmes in which financial institutions build a shared understanding of systemic risk.

Fintech NexusExamines open finance.Join this programme globalriskalliance.comAll programmes of The Global Risks Alliance
22Istilahi kuu

Istilahi kuu

UNI
Unique Nexus Identifier: a persistent identifier that resolves an artefact to its record.
inapendekezwa
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.
24Utafiti

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: web API; API design; open API; research software; combined with: risk; disaster; hazard; resilience; early warning. With JavaScript enabled, recent works matching these terms are listed from OpenAlex and Crossref.

25Maswali

Questions and answers.

What is the status of the Developers and APIs 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.
RipotiChangia

Changia ushahidi kutoka ukurasa huu.

Reports ni chapisho la kila robo mwaka la Muungano. Unachojua kuhusu somo hili kinaweza kuwa ushahidi, kisa au sahihisho katika toleo lijalo, kikitajwa kwa jina lako na kuchapishwa chini ya CC BY 4.0 pale ambapo ni kazi yako mwenyewe.

Nexus Standards
Viwango

Contribute to Developers and APIs

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.

Hali na matumizi. Nexus Standards ni viwango vinavyopendekezwa vilivyoandaliwa kupitia mchakato wazi chini ya NS-13 na kuchapishwa kwa matumizi ya hiari; si uthibitisho, uidhinishaji wala idhini ya kidhibiti, na upitishaji unabaki kuwa uamuzi wa Baraza la Viwango la Dunia na, katika kila nchi, wa Baraza lake la Viwango la Kitaifa. UNI (Unique Nexus Identifier) hutambua kitu; haikithibitishi. Majina ya vyombo vya viwango na viwango vyao ni mali ya wasimamizi wake na yanatumika tu kutambua nyaraka; hakuna maandishi ya kiwango cha nje yanayonakiliwa hapa. Nexus Standards haihusiani na, haiidhinishwi wala haithibitishwi na chombo chochote cha viwango kilichotajwa hapa.

Leseni: CC BY 4.0 kwa matini ya viwango, rejista, miundo na data; Apache-2.0 kwa msimbo wa marejeo. Viwango vya nje hunukuliwa kwa jina, namba na kiungo chini ya leseni zake vyenyewe. Data, maktaba na fonti za wahusika wengine huhifadhi leseni zake: tazama Notisi za wahusika wengine.