Skip to content
StandardsConsolesRouting
کون سے معیارات لاگو ہوتے ہیں

Which standards apply: routing console and composer

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

The open registries
The machine-readable registries behind every page, by number of records. Each is published as data under CC BY 4.0.Source: the Standards registry (the registry, the NHS-1 list).
  • 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
01جائزہ

Summary

How routing worksdeterministic
  1. 01Contextregistry identifiers, not free text
  2. 02Areassector, hazard and capability tags mapped to programme areas
  3. 03Standardsthe Nexus Standards listed by those areas
  4. 04Externalregistry entries in the areas’ domains, by relation and access
  5. 05Profilea draft with citations, submitted as a proposal under NS-13

The same registry version always gives the same result.

Registries
10
published as data
خطرے کے معیارات
348
records
خطرات
905
NHS-1
بیرونی معیارات
253
referenced, never copied
02راستہ

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.

Routing console · which standards apply to my contextFrom the registry
Selected contextworked example
  1. SectorFinance, insurance and capital markets
  2. Hazard familyHydrometeorological hazard standards
  3. CapabilityData and datasets
  4. Jurisdictionany (jurisdiction is not yet tagged in the registry)
  5. 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)

معیارادارہRelationرسائی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 specificationCoalition for Content Provenance and…adoptکھلاData and datasets · domain Provenance and evidence
CARE Principles for Indigenous Data GovernanceGlobal Indigenous Data AllianceadoptکھلاData and datasets · domain Data and datasets
DataCite Metadata Schema 4.5DataCite Metadata Working GroupadoptکھلاIdentification (the UNI) · domain Identifiers and cataloguing
FAIR Guiding Principles for scientific data management and stewardshipWilkinson et al. 2016; GO FAIRadoptکھلاData and datasets · domain Data and datasets
GOOS Essential Ocean VariablesIOC-UNESCO Global Ocean Observing SystemadoptکھلاFinance, insurance and capital markets; Hydrometeorological hazard standards · domain Climate
Handbook on Constructing Composite Indicators (OECD and JRC) and JRC…OECD and European Commission JRCadoptکھلاData and datasets · domain Data and datasets
in-toto Attestation Frameworkin-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 Agencyadoptfree-to-readIdentification (the UNI) · domain Identifiers and cataloguing
JSON-LD 1.1W3CadoptکھلاData and datasets · domain Data and datasets
OASIS Common Alerting Protocol Version 1.2OASIS Emergency Management TCadoptکھلاHydrometeorological hazard standards · domain Early warning and anticipatory action
OGC API – Features – Part 1: CoreOpen Geospatial ConsortiumadoptکھلاData and datasets · domain Geospatial and Earth observation
OGC GeoSPARQL – A Geographic Query Language for RDF DataOGCadoptکھلاData and datasets · domain Geospatial and Earth observation
OGC SensorML encoding standardOGCadoptکھلاData and datasets · domain Geospatial and Earth observation
Open Badges 3.01EdTech Consortiumadoptکھلا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 LanguageW3CadoptکھلاData and datasets · domain Data and datasets

Process explorer · NXS · Process

کون سے معیارات لاگو ہوتے ہیں

7 steps4 stages1 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.

  1. 01 Adopter

    1. 01Context tagsStart · the adopterThe adopter selects a sector, a hazard family, a capability, a jurisdiction and an artefact type, each a controlled registry value.
  2. 02 Routing engine

    1. 02Programme areasStep · the engine, deterministicallyThe same registry version gives the same result; each row states which programme matched.
    2. 03Nexus StandardsStep · the engineStandards are listed with their status as recorded in the registry.
    3. 04External entriesStep · the engineExternal standards are named and linked; the relation is as recorded in the register.
    4. 05Relation and access filterGate · the engineEach row states its reason: programme, domain, relation and access.
  3. 03 Result

    1. 06Profile draftRecord · the adopter, from the resultThe composer turns the result into a profile draft for download.
  4. 04 Nexus Standards editors

    1. 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
Process · how a context is routed7 operations
مرحلہPhaseعمل درآمدWhoDecision ruleریکارڈ
01AdopterContext tags (start). The adopter selects a sector, a hazard family, a capability, a jurisdiction and an artefact type, each a controlled registry value.the adoptertags are registry identifiers: sectors, hazard families, capabilities, categories and, where recorded, jurisdictionsa set of tags
02Routing engineProgramme areas (step). The same registry version gives the same result; each row states which programme matched.the engine, deterministicallysector, hazard and capability tags map to programmes by registry identifierthe matching programmes
03Routing engineNexus Standards (step). Standards are listed with their status as recorded in the registry.the enginethe standards each programme lists, with status and rule countthe standards the areas list
04Routing engineExternal entries (step). External standards are named and linked; the relation is as recorded in the register.the enginethe entry’s domain is a crosswalk domain of the programmeregister entries in the areas’ domains
05Routing engineRelation and access filter (gate). Each row states its reason: programme, domain, relation and access.the engineadopt 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 resulta profile cites every source by identifier and clause; the licence line travels with ita profile as YAML and JSON with citations
07Nexus Standards editorsChange proposal (end). A change proposal is a change request with the profile record; editors decide with written reasons.any person, with identity recordedevery submission is a change proposal under NS-13a 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.

03Compose

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.

Composer · select standards and clauses; view, cite and download the profileFrom the registry
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.

04ماخذات

Registry files used by the console

Registry fileContent used
the sectors registersectors and the programme area of each
the programme areas registerprogramme areas, the standards they list and their crosswalk domains
the external standards registerentries with body, version, relation, access and URL
the standards indexstatus and rules of the Nexus Standards
the Nexus Standards registerartefact categories (the artefact type)

Per-rule artefact tags are being added to the registry; until then, the artefact type adds the identification standards area.

05سوالات

سوالات و جوابات۔

Is a routed standard a requirement?
No. The console lists the standards that the registry relates to the selected context and the reason for each. Obligations arise from law, contracts and the bodies entitled to set them.
How is a profile submitted?
The draft is downloaded to the reader’s device. It may then be submitted as a proposal under NS-13, by change request against the canonical repository.
معیارات

معیارات میں حصہ لیں۔

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۔ بیرونی معیارات کا حوالہ ان کے نام، نمبر اور لنک کے ساتھ ان کے اپنے لائسنسوں کے تحت دیا جاتا ہے۔ فریقِ ثالث کا ڈیٹا، لائبریریاں اور فونٹس اپنے اپنے لائسنس رکھتے ہیں: فریقِ ثالث کے نوٹس دیکھیں۔