کام ستانداردەکان جێبەجێ دەبن: کۆنسۆڵی ئاڕاستەکردن و پێکهێنەر
For a selected sector, hazard family, capability, jurisdiction and artefact type, the routing console identifies the corresponding programme areas of the registry, the Nexus Standards those areas list and the external standards in their domains, stating the reason for each; the composer turns the result into a draft profile that can be cited and downloaded. Each artefact carries a UNI (Unique Nexus Identifier).
- Hazard relations (NHS-1): 1,867
- Hazards (NHS-1): 905
- Risk standards: 348
- External standards: 253
- Regions (ISO 3166): 249
- Programme areas: 77
- Record categories: 38
- Scope codes: 32
- Domain codes: 30
- Sector codes: 13
پوختە
- 01Contextregistry identifiers, not free text
- 02Areassector, hazard and capability tags mapped to programme areas
- 04Externalregistry entries in the areas’ domains, by relation and access
- 05Profilea draft with citations, submitted as a proposal under NS-13
The same registry version always gives the same result.
- تۆمارگەکان
- 10
- published as data
- ستانداردەکانی مەترسی
- 348
- تۆمارەکان
- مەترسیدەرەکان
- 905
- NHS-1
- ستانداردی دەرەکی
- 253
- referenced, never copied
Context routing with reasons
The example below is computed when the page is built; in the browser, each selection is recomputed from the registry relations delivered with the page.
- SectorFinance, insurance and capital markets
- Hazard familyHydrometeorological hazard standards
- CapabilityData and datasets
- Jurisdictionany (jurisdiction is not yet tagged in the registry)
- Artefact typeDS · Dataset
4 areas · 8 Nexus Standards · 102 external entries.
ستانداردە جێبەجێبووەکان
| Nexus Standard | دۆخ | Why it is routed |
|---|---|---|
| NS-0 دەستوور و بنەماکان | پێشنیارکراو | Finance, insurance and capital markets; Hydrometeorological hazard standards |
| NS-1 The UNI and the artefact catalogue (grammar v0.2:… | پێشنیارکراو | Identification (the UNI) |
| NS-3 Risk record UNIs (grammar, legacy crosswalk,… | پێشنیارکراو | Hydrometeorological hazard standards; Data and datasets; Identification (the UNI) |
| NS-3b Dataset and product metadata profile (STAC, DCAT,… | پێشنیارکراو | Hydrometeorological hazard standards; Data and datasets |
| NS-9 Contextual UNIs (deployments, instances, programme… | پێشنیارکراو | Finance, insurance and capital markets; Identification (the UNI) |
| NS-10 Policies and clauses (machine-readable obligations:… | پێشنیارکراو | Finance, insurance and capital markets |
| NS-11 Verification and monitoring (evidence, attestations,… | پێشنیارکراو | Finance, insurance and capital markets; Hydrometeorological hazard standards; Data and datasets |
| NS-14 پابەندبوون و هاوتاکردن لەگەڵ ستانداردی دەرەکی | پێشنیارکراو | Finance, insurance and capital markets |
External standards in the areas’ domains (first 18 of 102)
| ستاندارد | لەش | پەیوەندی | دەستگەیشتن | Why it is routed |
|---|---|---|---|---|
| BCBS 239 Principles for effective risk data aggregation and risk… | Basel Committee on Banking Supervision… | adopt | کراوە | Finance, insurance and capital markets · domain Finance and capital |
| C2PA Content Credentials specification | Coalition for Content Provenance and… | adopt | کراوە | Data and datasets · domain Provenance and evidence |
| CARE Principles for Indigenous Data Governance | Global Indigenous Data Alliance | adopt | کراوە | Data and datasets · domain Data and datasets |
| DataCite Metadata Schema 4.5 | DataCite Metadata Working Group | adopt | کراوە | Identification (the UNI) · domain Identifiers and cataloguing |
| FAIR Guiding Principles for scientific data management and stewardship | Wilkinson et al. 2016; GO FAIR | adopt | کراوە | Data and datasets · domain Data and datasets |
| GOOS Essential Ocean Variables | IOC-UNESCO Global Ocean Observing System | adopt | کراوە | Finance, insurance and capital markets; Hydrometeorological hazard standards · domain Climate |
| Handbook on Constructing Composite Indicators (OECD and JRC) and JRC… | OECD and European Commission JRC | adopt | کراوە | Data and datasets · domain Data and datasets |
| in-toto Attestation Framework | in-toto project (CNCF) | adopt | کراوە | Data and datasets · domain Provenance and evidence |
| IPCC AR6 Working Group II – risk framing (hazard, exposure,… | Intergovernmental Panel on Climate… | adopt | کراوە | Finance, insurance and capital markets; Hydrometeorological hazard standards · domain Climate |
| ISO 3166-1 Codes for the representation of names of countries and… | ISO/TC 46; ISO 3166 Maintenance Agency | adopt | free-to-read | Identification (the UNI) · domain Identifiers and cataloguing |
| JSON-LD 1.1 | W3C | adopt | کراوە | Data and datasets · domain Data and datasets |
| OASIS Common Alerting Protocol Version 1.2 | OASIS Emergency Management TC | adopt | کراوە | Hydrometeorological hazard standards · domain Early warning and anticipatory action |
| OGC API – Features – Part 1: Core | Open Geospatial Consortium | adopt | کراوە | Data and datasets · domain Geospatial and Earth observation |
| OGC GeoSPARQL – A Geographic Query Language for RDF Data | OGC | adopt | کراوە | Data and datasets · domain Geospatial and Earth observation |
| OGC SensorML encoding standard | OGC | adopt | کراوە | Data and datasets · domain Geospatial and Earth observation |
| Open Badges 3.0 | 1EdTech Consortium | adopt | کراوە | Identification (the UNI) · domain Identifiers and cataloguing |
| ORCID iD (subset of ISNI, ISO 27729) | ORCID Inc. | adopt | کراوە | Identification (the UNI) · domain Identifiers and cataloguing |
| OWL 2 Web Ontology Language | W3C | adopt | کراوە | Data and datasets · domain Data and datasets |
Process explorer · NXS · Process
کام ستانداردەکان جێبەجێ دەبن
7 steps·4 stages·1 gate
NXS · Process
کام ستانداردەکان جێبەجێ دەبن
خولی ژیانی ستاندارد · ڕێڕەوی NS-13 · کەناڵەکانی بەشداری · ڕێڕەوی IETF · ڕێڕەوی W3C · ڕێڕەوی OGC · ڕێڕەوی OASIS · قۆناغەکانی ISO و IEC · گونجاندن · خولی ژیانی تۆمار · ئاڕاستەکردن · چاودێری.
Context tags resolve to programme areas, their standards and crosswalk domains, giving a reasoned list, a profile draft and, if chosen, a change proposal.
01 پەسەندکەر
- 01Context tagsStart · the adopterThe adopter selects a sector, a hazard family, a capability, a jurisdiction and an artefact type, each a controlled registry value.
02 Routing engine
- 02Programme areasStep · the engine, deterministicallyThe same registry version gives the same result; each row states which programme matched.
- 03Nexus StandardsStep · the engineStandards are listed with their status as recorded in the registry.
- 04External entriesStep · the engineExternal standards are named and linked; the relation is as recorded in the register.
- 05Relation and access filterGate · the engineEach row states its reason: programme, domain, relation and access.
03 ئەنجام
- 06Profile draftRecord · the adopter, from the resultThe composer turns the result into a profile draft for download.
04 Nexus Standards editors
- 07Change proposalOutcome · any person, with identity recordedA change proposal is a change request with the profile record; editors decide with written reasons.
Nexus Standards programme register · NS-14: crosswalk and conformance claims · NS-9: contextual UNIAn outline of how the work is designed to run; it does not report the status of any decision or record.
The operations, as a table
| هەنگاو | قۆناغ | کارکردن | کێ | Decision rule | تۆمار |
|---|---|---|---|---|---|
| 01 | پەسەندکەر | Context tags (start). The adopter selects a sector, a hazard family, a capability, a jurisdiction and an artefact type, each a controlled registry value. | پەسەندکەرەکە | tags are registry identifiers: sectors, hazard families, capabilities, categories and, where recorded, jurisdictions | a set of tags |
| 02 | Routing engine | Programme areas (step). The same registry version gives the same result; each row states which programme matched. | the engine, deterministically | sector, hazard and capability tags map to programmes by registry identifier | the matching programmes |
| 03 | Routing engine | Nexus Standards (step). Standards are listed with their status as recorded in the registry. | بزوێنەرەکە | the standards each programme lists, with status and rule count | the standards the areas list |
| 04 | Routing engine | External entries (step). External standards are named and linked; the relation is as recorded in the register. | بزوێنەرەکە | the entry’s domain is a crosswalk domain of the programme | register entries in the areas’ domains |
| 05 | Routing engine | Relation and access filter (gate). Each row states its reason: programme, domain, relation and access. | بزوێنەرەکە | adopt and profile first; paywalled crosswalk, profile and extend relations shown as compatibility profile (restricted) | the filtered list with reasons |
| 06 | ئەنجام | Profile draft (record). The composer turns the result into a profile draft for download. | the adopter, from the result | a profile cites every source by identifier and clause; the licence line travels with it | a profile as YAML and JSON with citations |
| 07 | Nexus Standards editors | Change proposal (end). A change proposal is a change request with the profile record; editors decide with written reasons. | any person, with identity recorded | every submission is a change proposal under NS-13 | a change proposal with the profile record |
Table.Each selection lights the operation it feeds; the result keeps its reasons. The table shows the process as specified; it does not report the status of any standard, proposal or record. Sources: Nexus Standards programme register · NS-14: crosswalk and conformance claims · NS-9: contextual UNI.
The routing is deterministic: the same registry version gives the same result, and each row states the area, domain and relation that routed it. Jurisdiction does not yet narrow the result, as the registry does not yet carry jurisdiction tags.
Composing a profile from standards and clauses
Select Nexus Standards and their rules, add external standards by registry entry, and view the profile as YAML or JSON for copying, citation or download.
kind: profile schemaVersion: "0.1.0-draft" title: "Profile draft" status: DRAFT nexusStandards: - id: NS-1 uni: NXS-STD-ST-000001 status: PROPOSED clauses: [NS1-R1, NS1-R2] - id: NS-3b uni: NXS-STD-SW-000005 status: PROPOSED clauses: [] - id: NS-11 uni: NXS-STD-ST-000007 status: PROPOSED clauses: [NS11-R1, NS11-R2] externalStandards: - id: stac relation: adopt clauses: [] licence: "Nexus Standards text, registries, schemas and data CC BY 4.0; reference code Apache-2.0" note: "A UNI (Unique Nexus Identifier) identifies an artifact; it does not certify it." submit: "a proposal under NS-13, recorded as a public change record"A profile is a draft stating which Nexus clauses and which external standards apply to an artefact or a context; external obligations are cited by identifier and clause number. Validation checks the structure of the draft. Composition takes place in the browser, and the draft is not transmitted.
Registry files used by the console
| Registry file | Content used |
|---|---|
| the sectors register | sectors and the programme area of each |
| the programme areas register | programme areas, the standards they list and their crosswalk domains |
| the external standards register | entries with body, version, relation, access and URL |
| the standards index | status and rules of the Nexus Standards |
| the Nexus Standards register | artefact categories (the artefact type) |
Per-rule artefact tags are being added to the registry; until then, the artefact type adds the identification standards area.
پرسیار و وەڵام.
Is a routed standard a requirement?
How is a profile submitted?
Around the standards.
بەشداری لە ستانداردەکاندا بکە.
Governments, regulators, standards bodies, industry, academia and communities are invited to shape the catalogue ahead of its first official release, targeted for 2030: comment on a draft, propose a change, join a working group or host a field exercise.
دۆخ و بەکارهێنان. Nexus Standards ستانداردی پێشنیارکراون کە لە ڕێگەی پرۆسەیەکی کراوەوە لەژێر NS-13 پەرەیان پێدراوە و بۆ بەکارهێنانی خۆبەخشانە بڵاو کراونەتەوە؛ بڕوانامە، متمانەپێدان یان ڕەزامەندیی ڕێکخەر نین، و پەسەندکردن بڕیاری ئەنجومەنی جیهانیی ستانداردەکان و، لە هەر وڵاتێکدا، ئەنجومەنی نیشتمانیی ستانداردەکانی ئەو وڵاتەیە. UNI (Unique Nexus Identifier) بەرهەمێک دەناسێنێت؛ بڕوانامەی پێ نادات. ناوی دەستەکانی ستاندارد و ستانداردەکانیان هی پارێزەرەکانیانن و تەنها بۆ ناساندنی بەڵگەنامەکان بەکاردێن؛ هیچ دەقێکی ستانداردێکی دەرەکی لێرەدا دووبارە نەکراوەتەوە. Nexus Standards پەیوەست نییە بە هیچ دەستەیەکی ستانداردی ناوهێنراو لێرەدا، و لەلایەن هیچیانەوە پشتگیری یان بڕوانامەی پێ نەدراوە.
مۆڵەتەکان: CC BY 4.0 بۆ دەقی ستانداردەکان، تۆمارگەکان، سکێماکان و داتا؛ Apache-2.0 بۆ کۆدی سەرچاوە. ستانداردە دەرەکییەکان بە ناو، ژمارە و بەستەر لە ژێر مۆڵەتەکانی خۆیاندا ئاماژەیان پێدەدرێت. داتا، کتێبخانە و فۆنتەکانی لایەنی سێیەم مۆڵەتەکانی خۆیان دەپارێزن: بڕوانە ئاگادارییەکانی لایەنی سێیەم.