UNI: کەتەلۆگ و چارەسەرکەر
The UNI (Unique Nexus Identifier) is one stable, machine-readable identifier for each artefact, paired with one catalogue record stating what the artefact is, who created and publishes it, which rights apply and where it is held. The resolver returns the record for a UNI.
- NXS: 1 prefix codes, for example NXS.
- SCOPE: 32 scope codes, for example GRX.
- CAT: 38 category codes, for example AR.
- DOMAIN (optional): 30 domain codes, for example WAT.
- SECTOR (optional): 13 sector codes, for example UTL.
- REGION (optional): 249 region codes, for example CAN.
- SERIAL: serial, for example 000012.
- @VERSION (optional): version, for example 1.0.0.
UNI یەک بخوێنەوە.
Type or paste a Uniform Nexus Identifier: each segment is decoded against grammar 0.2 and the region, when it names a country, is lit on the globe below.
The process.
NXS-STD-ST-000001NXS-EWS-DS-KEN-000003NXS-GRX-RP-M002-000007@1.2.0NXS-GRX-OB-KEN-000042@3NXS-GCR-AR-000015Illustrative identifier pattern. With script enabled, a UNI can be entered and each segment is checked against the registry, resolved to its record where one is published, and expressed as a URN, a resolver link and a citation.
UNI anatomyThe NS-1 grammar segment by segment, with the scope and category codes of the registry. Resolution links to the resolver; no identifier is allocated on this page.
- Scope codes
- 32
- SCOPE
- Categories
- 38
- CAT
- Domains
- 30
- DOMAIN
- هەرێمەکان
- 249
- ISO 3166 alpha-3
Structure of a UNI
Grammar version 0.2 (context segments added 2026-10-16; every v0.1 identifier is unchanged and remains valid).
NXS-<SCOPE>-<CAT>[-<DOMAIN>][-<SECTOR>][-<REGION>][-<ENV>]-<SERIAL>[@<VERSION>] NXS-EWS-DS-000042 dataset 42 of the multi-hazard monitoring and warning class NXS-EWS-DS-KEN-000003 a Kenyan monitoring and warning dataset NXS-GRX-RP-M002-000007@1.2.0 report 7 of the risk data class for Africa, version 1.2.0 NXS-GRX-AR-WAT-CAN-000012 article 12 of the risk data class on water in Canada NXS-GRX-DP-WAT-WUT-CAN-PRD-000001 production deployment 1 of the risk data class for Canadian water utilities (NS-9) NXS-GCR-AR-000015 an article published by GCRI Canada NXS-STD-ST-000001 this standard| بەش | فۆرم | واتا |
|---|---|---|
NXS | جێگیر | Prefix. Chosen over NEX because it reads as a code, not a word, and because NEX- is crowded by brands. NXS-S01 to NXS-S20 are also the neutral identifiers of the functional system classes (section 2). |
| SCOPE | three letters | A functional system class (EWS, EOP, SIG, GRX, OPS and the others in section 2), an organisation (GCR, GRF, GRA, NXO) or a cross-cutting scope (STD, LEG, GOV, PRG) |
| CAT | دوو پیت | Artefact category, mapped to Zenodo upload and publication types and to DataCite resource types (section 3); or a risk record kind (OB, SR, IN, ME, BD, CT, CR, AP, SU; NS-3). The two lists never share a code. |
| DOMAIN | optional, three letters | Domain code from registry/domains.yaml (WAT ئاو، ENE وزە، FOO خۆراک، HLT تەندروستی، BIO biodiversity, CLI کەشوهەوا، DRR, EWN, HUM, INF, SCH, SEC, ZTA, FNC, DSC, ERM, DRG, AIS, DAT, GSP, PRV, IDF, SFW, NAT, SDP, LIC; proposed: CMP, DTW, SNS, PNT) |
| SECTOR | optional, three letters | Sector code from registry/sectors.yaml (AGR, WUT, EUT, HSY, FNI, TRL, CIT, INM, DTC, PUB, RED, HUO, IGO) |
| REGION | هەڵبژاردەیی | ISO 3166-1 alpha-3 country code (KEN, CAN) or UN M49 area code written as M followed by three digits (M002 ئەفریقا، M142 Asia); registry registry/regions.yaml |
| ENV | optional, three letters | PRD production, STG قۆناغی ئامادەکاری، LBX تاقیگە، FIX fixture; used by contextual records (NS-9) |
| SERIAL | شەش ژمارە | Allocated by a catalogue or a record allocation authority per full prefix (SCOPE, CAT and context segments); never reused |
| وەشان | هەڵبژاردەیی | Semantic version of an artefact (1.2.0) or the integer recordVersion of a risk record (3; NS-3). The UNI without a version names the concept. |
Context segments. The four optional segments always appear in the order DOMAIN, SECTOR, REGION, ENV. Each is a three-letter code from its registry, and the registries are pairwise disjoint and disjoint from the scope codes and from the M49 form (checked by node tools/nexus-id.mjs catalog validate), so an identifier parses deterministically without separators. The identifier without CAT and SERIAL is the context name: NXS-GRX-WAT-CAN reads as the risk data class, water domain, Canada. Articles, pages, datasets, deployments, dashboards and code about that context carry the context name (NS-16); their UNIs differ only in CAT and SERIAL. A context name is never allocated and never carries a serial; the NS-9 contextual record (DP یان PR) is the record of truth for a context.
Machine forms: URN urn:nexus:uni:NXS-EWS-DS-000042; resolver path /uni/NXS-EWS-DS-000042 (an HTML landing page for browsers and JSON for machines by content negotiation; /uni/<uni>.json is always JSON; /uni lists published records); context path /ctx/NXS-GRX-WAT-CAN (every published record of that context); field name uni in every record, API, schema and table.
Existing dotted identifiers (for example data.eo.stac.catalogue) are UNI v0. They are recorded as legacyUni on the new record for crosswalk and are never allocated again.
1.1 Context code allocation
پێشنیار NXS-STD-PC-000004 introduces this section and is OPEN; the rules apply to every code allocated from now on. Machine form: registry/nexus-standards.yaml identifier.codeAllocation. پشکنین: node tools/nexus-id.mjs catalog validate.
A scope, domain, sector or environment code is a three-letter classification that machines parse and that people need not read. The allocation rules exist so that no code becomes ambiguous, including after future changes in other code lists.
| یاسا | دەق |
|---|---|
| CA-1 | A code is three capital letters A to Z. It contains no digits and never takes the UN M49 form (M followed by three digits). |
| CA-2 | A code is unique across every registry: scopes, domains, sectors, environments and ISO 3166-1 alpha-3. |
| CA-3 | A code is never one of the following, all listed in registry/regions.yaml, so that a future country assignment cannot collide:• an ISO 3166-1 exceptionally, transitionally or formerly reserved code element; • a code in the user-assigned ranges ( AAA to AAZ, QMA to QZZ, XAA to XZZ, ZZA to ZZZ);• an ICAO Doc 9303 nationality code. |
| CA-4 | A code is a mnemonic of the English label: the first letter of the label’s head term, followed by consonants that keep the code recognisable. |
| CA-5 | A code is never a product name, a mark, a company name or a stock ticker, and never a word that reads as a brand. |
| CA-6 | One concept per code. Each code has a definition, what it includes and excludes, and the external standards it crosswalks to. |
| CA-7 | Ids are stable, lowercase kebab-case English. Labels are in sentence case. Neither encodes a status. |
| CA-8 | Append-only. A code is never reassigned or deleted. A retired code keeps its entry with deprecated: true و supersededBy. |
| CA-9 | A new code stays PROPOSED, with its proposal UNI, until the Global Standards Council adopts the registry change. An implementation may use a PROPOSED identifier and shall show its status. |
| CA-10 | Adding a code is a minor, additive registry version. Changing what a code means is a major change and requires a crosswalk. |
Grandfathered: AAP, the scope code of the anticipatory-action class, was allocated before CA-3 and lies inside the user-assigned range AAA to AAZ. It is kept under CA-8.
Technology domains proposed under these rules:
| کۆد | ناسنامە | ناونیشان | Crosswalks to |
|---|---|---|---|
CMP | compute | Compute and accelerated infrastructure | ISO/IEC JTC 1/SC 38 and SC 39; ISO/IEC 22123 |
DTW | digital-twins | دووانەی دیجیتاڵ و لاساییکردنەوە | ISO/IEC 30173:2023; ISO/IEC JTC 1/SC 41; ISO 23247 |
SNS | sensing | Sensing and measurement networks | OGC SensorThings API and SensorML; W3C/OGC SOSA/SSN; IEEE 1451 |
PNT | pnt | شوێندۆزینەوە، ڕێنیشاندان و کات | IEEE 1588; ITU-T G.8271 and G.8272; ITU-R TF series; UN ICG |
Sensing and positioning, navigation and timing are separate codes because different communities standardise them: sensor and observation encodings on one side, timing and GNSS profiles on the other. A technology stream that covers both carries SNS و لیستەکان PNT وەک پەیوەندیدار.
A future quantum-technology code cannot be QTM یان QNT, because both fall in the user-assigned range QMA to QZZ. CA-3 catches this kind of collision before allocation.
Scope codes
32 scope codes for systems, organisations and cross-cutting scopes. Codes classify; public labels follow the naming rules of the standards. When an identifier is entered in the parser above, the row of its scope is highlighted.
| کۆد | جۆر | ناونیشان |
|---|---|---|
CMD | سیستەم | هەڵوێستی یەکخراو و کورتەی جێبەجێکار |
NST | سیستەم | وێنەی کارپێکردنی هاوبەشی مەدەنی |
DSS | سیستەم | Decision support, cases and deliberation |
COR | سیستەم | ژمێریاری، گرێکان و ژینگەی کارپێکردن |
NXQ | سیستەم | نەرمەکاڵا، مۆدێل و خولی ژیانی توانا |
GRX | سیستەم | Canonical risk data, records and provenance |
EOP | سیستەم | چاودێریی زەوی و دووانەی دیجیتاڵ |
EWS | سیستەم | چاودێری و ئاگادارکردنەوەی فرەمەترسیدەر |
AAP | سیستەم | کاری پێشوەختی و دەستپێکەرەکان |
NET | سیستەم | توپۆلۆجیای تۆڕ و بەردەوامی |
OPS | سیستەم | ئامێرەکان، هەستەوەرەکان و ڕێکخستنی پێوانە |
SIG | سیستەم | Signals, spectrum, timing and positioning, navigation and timing (PNT) |
the trust and assurance system | سیستەم | Trust, authorisation and assurance |
HUB | سیستەم | زانیاری، تۆمار و فێربوون |
STU | سیستەم | Visual composition and workflows |
FAC | سیستەم | نەخشە، بنیاتنان و واژۆکردن |
APP | سیستەم | کەتەلۆگی بەرنامەکان و خولی ژیانیان |
RLS | سیستەم | Participants, agreements and protocols |
POR | سیستەم | گەیاندن بە گشت، کڕیار و هاوبەش |
LAB | سیستەم | Research, experiments and simulation |
GCR | organisation | Global Centre for Risk and Innovation (GCRI Canada) |
GRF | organisation | Global Risks Forum |
GRA | organisation | Global Risks Alliance |
NXO | organisation | Reserved organisation scope for a multi-party consortium (entity under legal review) |
ELP | organisation | Reserved organisation scope (withdrawn before use) |
OBS | organisation | Reserved organisation scope (withdrawn before use) |
STD | cross cutting | The Nexus Standards themselves |
LEG | cross cutting | Legal, intellectual property and licensing |
GOV | cross cutting | Governance, decisions and policy |
PRG | cross cutting | Programme, waves and work items |
UXK | cross cutting | UI/UX kit, design tokens and assets |
ALL | cross cutting | Ecosystem-wide |
Artefact categories
38 artefact categories. Each maps to a DataCite resource type and a Zenodo upload type for export; the mapping is a crosswalk, and the UNI remains the key.
| کۆد | پۆل | DataCite type |
|---|---|---|
SW | نەرمەکاڵا | نەرمەکاڵا |
SV | Service or API | خزمەتگوزاری |
SC | Schema or contract | تر |
MG | Database migration | نەرمەکاڵا |
WF | ڕێڕەوی کار | ڕێڕەوی کار |
MD | مۆدێل | مۆدێل |
DS | کۆمەڵە داتا | کۆمەڵە داتا |
EV | تۆماری بەڵگە | کۆمەڵە داتا |
AR | ماددە | JournalArticle |
PP | پێش-چاپ | پێش-چاپ |
RP | ڕاپۆرت | ڕاپۆرت |
TN | Technical note | دەق |
DC | بەڵگەنامە | دەق |
DL | بەرهەمی ڕادەستکراو | ڕاپۆرت |
WP | Working paper | دەق |
BK | Book or chapter | کتێب |
CP | Conference paper | ConferencePaper |
TH | تێز | Dissertation |
PT | پاتێنت | تر |
ST | ستاندارد | ستاندارد |
PC | Policy or directive | دەق |
PS | Presentation | دەق |
PO | پۆستەر | دەق |
FG | وێنە | وێنە |
PL | Plot or visualisation | وێنە |
DG | دیاگرام | وێنە |
PH | وێنە | وێنە |
MP | بەرهەمی نەخشە | وێنە |
VD | ڤیدیۆ | بینراو و بیستراو |
LS | Lesson or course | InteractiveResource |
PY | Physical object | PhysicalObject |
PA | Participation record | تر |
RS | Programme status record | تر |
DP | Deployment or instance (NS-9 context) | تر |
PR | Programme instance (NS-9 context) | تر |
CL | Clause (NS-10 obligation) | تر |
AT | Conformance attestation (NS-11) | تر |
OT | تر | تر |
| کۆد | Record kind | تێبینی |
|---|---|---|
OB | Observation fact | record kind (NS-3) |
SR | Source release | record kind (NS-3) |
IN | Indicator definition | record kind (NS-3) |
ME | Measure definition | record kind (NS-3) |
BD | Boundary version | record kind (NS-3) |
CT | Chronotope version | record kind (NS-3) |
CR | Correction record | record kind (NS-3) |
AP | Analytical product record | record kind (NS-3) |
SU | Subject (place, asset, organisation) | record kind (NS-3) |
Content of a catalogue record
The record schema with example records from the standards catalogue, and the crosswalk of its fields to public metadata schemas.
Artefact record (NS-1) · 32 fields · 12 required
unirequired stringThe UNI (Unique Nexus Identifier), NS-1 grammar, without @version.displayAliasstringPublic Registry short form (NX-R-47092) shown next to the UNI during the transition.registryStateenumPublic registry state; corrections keep the UNI and add a version.legacyUnistringDotted UNI v0 this record replaces, for crosswalk (for example data.eo.stac.catalogue).titlerequired stringdescriptionstringscoperequired stringcategoryrequired stringregionstringdomainstringDOMAIN segment code from the domains register (NS-1 v0.2); present when the identifier carries it.sectorstringSECTOR segment code from the sectors register (NS-1 v0.2).environmentenumENV segment code (NS-1 v0.2).contextNamestringNS-16 context name: the identifier without CAT and SERIAL; derived, never allocated.systemIdstringFunctional system class id (systemId) from the Nexus Standards register#scopes when scope is a SYSTEM.statusrequired enumcurrentVersionstringversionsarrayversionstringdatestringgitShastringdigeststringnotestring
creatorsrequired arraynamestringtypeenumaffiliationstringorcidstringrorstring
publisherRefrequired stringEntity reference of the publishing institution (registry/governance.yaml#bodies); the institution stays publisher of record for institutional artefacts.publicationDaterequired stringlanguagestringkeywordsarrayrightsrequired objectlicensestringSPDX licence identifier or expression, or a LicenseRef- string for a licence that has no SPDX identifier.rightsHolderRefstringaccessRightenumembargoDatestring
legalStaterequired enumclaimCeilingrequired enumlocationsrequired arraykindenumvaluestringdigeststring
relatedIdentifiersarrayrelationenumidentifierstringidentifierTypeenum
supersededBystringworkPackageIdstringdirectiveRefsarrayReferences to the recorded decisions or policies under which the artefact was produced.notesstringcontextobjectNS-9: this record is a deployment, instance or programme instance of the concept ofUni, in a context.ofUnistringdomainsarrayids from the domains registersectorsarrayids from the sectors registerjurisdictionsarrayhostRefstringenvironmentenumvalidFromstringvalidUntilstringconformsToarrayNexus Standard ids and the external standards register ids this context claims; evidence per NS-11
Example record · NXS-STD-ST-000001
{ "uni": "NXS-STD-ST-000001", "title": "Nexus Standards NS-1 - the UNI and artifact catalog", "scope": "STD", "category": "ST", "status": "DRAFT", "currentVersion": "0.1.0", "creators": [ { "name": "Global Centre for Risk and Innovation (GCRI)", "type": "Organizational" } ], "publisherRef": "GCRI", "publicationDate": "2026-10-15", "rights": { "license": "CC-BY-4.0", "accessRight": "open" }, "legalState": "LEGAL_REVIEW_REQUIRED", "claimCeiling": "INTEGRATED", "locations": [ { "kind": "repoPath", "value": "standards/NS-1-identifier-and-artifact-catalog.md" }, { "kind": "repoPath", "value": "registry/nexus-standards.yaml" } ], "workPackageId": "LEGAL-NAME-ARCHITECTURE-001" }Field crosswalk: Schema.org JSON-LD, DataCite, Zenodo, CodeMeta
| Record field | Schema.org | DataCite | Zenodo | CodeMeta | سەرچاوە |
|---|---|---|---|---|---|
uni | identifier (PropertyValue, propertyID urn:nexus:uni) | alternateIdentifier (alternateIdentifierType NXS) | metadata.related_identifiers[] (scheme other) | ناسێنەر | پێشنووس |
title | ناو | titles[].title | metadata.title | ناو | پێشنووس |
description | description | descriptions[].description (Abstract) | metadata.description | description | پێشنووس |
scope | · | subjects[] (subjectScheme nexus-scope) | metadata.keywords[] | · | پێشنووس |
category | additionalType | types.resourceTypeGeneral | metadata.upload_type / publication_type / image_type | applicationCategory | تۆمارگە |
region | spatialCoverage | geoLocations[].geoLocationPlace | metadata.locations[] | · | پێشنووس |
status | creativeWorkStatus | · | · | developmentStatus | پێشنووس |
currentVersion | وەشان | وەشان | metadata.version | وەشان | پێشنووس |
versions | · | relatedIdentifiers (IsNewVersionOf, IsPreviousVersionOf) | versions (concept DOI) | · | پێشنووس |
creators | creator / author | creators[] | metadata.creators[] | نووسەر | پێشنووس |
publisherRef | بڵاوکەرەوە | بڵاوکەرەوە | metadata.publisher (Zenodo) | بڵاوکەرەوە | پێشنووس |
publicationDate | datePublished | publicationYear; dates[] (Issued) | metadata.publication_date | datePublished | پێشنووس |
language | inLanguage | زمان | metadata.language | · | پێشنووس |
keywords | وشە سەرەکییەکان | subjects[] | metadata.keywords[] | وشە سەرەکییەکان | پێشنووس |
rights.license | مۆڵەت | rightsList[].rightsIdentifier (SPDX) | metadata.license | مۆڵەت | پێشنووس |
rights.accessRight | conditionsOfAccess | · | metadata.access_right | · | پێشنووس |
legalState | · | · | · | · | پێشنووس |
claimCeiling | · | · | · | · | پێشنووس |
locations | url / contentUrl / codeRepository | alternateIdentifiers[] (URL) | files[] / metadata.related_identifiers[] | codeRepository / downloadUrl | پێشنووس |
relatedIdentifiers | isPartOf / citation / isBasedOn | relatedIdentifiers[] (relationType) | metadata.related_identifiers[] | isPartOf / referencePublication | پێشنووس |
supersededBy | · | relatedIdentifiers[] (IsObsoletedBy) | metadata.related_identifiers[] (isObsoletedBy) | · | پێشنووس |
workPackageId | · | · | · | · | پێشنووس |
directiveRefs | · | relatedIdentifiers[] (References) | metadata.related_identifiers[] (references) | · | پێشنووس |
context | · | · | · | · | پێشنووس |
Rows marked registry are taken from the category mappings to Zenodo and DataCite in the registry; rows marked draft are an editorial mapping to the public schemas and are not part of the registry.
Record explorerthe artefact record schema with example records from the standards catalogue (scope STD). A record describes an artefact and its provenance.
Resolution of a UNI
The resolver path is /uni/{uni}: an HTML landing page for browsers and JSON for machines, for published records that are not restricted. The catalogue file in the standards repository is the authoritative source of the records.
Records in the standards scope
104 records: the identifiers of the standards themselves, with their status and rights state.
| UNI | ناونیشان | دۆخ | Rights state |
|---|---|---|---|
NXS-STD-ST-000001 | Nexus Standards NS-1 – the UNI and artefact catalogue | پێشنووس | under review |
NXS-STD-SW-000002 | UNI command-line tool (validate, parse, next, mint, catalogue, export) – reference implementation | پێشنووس | under review |
NXS-STD-SC-000001 | UNI artefact record schema v1 | پێشنووس | under review |
NXS-STD-ST-000002 | Open-standards and open-source stack under the UNI | پێشنووس | under review |
NXS-STD-SW-000005 | UNI data profile (STAC, DCAT, PROV-O crosswalks), NS-3b | پێشنووس | under review |
NXS-STD-ST-000003 | Nexus Standards NS-3 – risk record UNIs (grammar, legacy crosswalk, allocation authority) | پێشنووس | under review |
NXS-STD-SW-000006 | Nexus Standards repository validator (registry invariants, schema, STD catalogue, embedded UNIs, register of implementations) | پێشنووس | under review |
NXS-STD-DC-000001 | Nexus Standards repository documentation (README, governance, contributing, agent boot) | پێشنووس | under review |
NXS-STD-SW-000007 | Nexus Standards site page generator and WordPress draft publisher | پێشنووس | under review |
NXS-STD-DC-000002 | Nexus Standards site pages for nexustandards.com (overview, NS-1, catalogue and resolver, governance) | پێشنووس | under review |
NXS-STD-ST-000004 | Nexus Standards NS-0 – constitution and principles | پێشنووس | under review |
NXS-STD-ST-000005 | Nexus Standards NS-9 – contextual UNIs (deployments, instances, programme instances) | پێشنووس | under review |
NXS-STD-DC-000003 | Nexus Standards subsites (systemic architecture index and one landing page per subsite) | پێشنووس | under review |
NXS-STD-ST-000006 | Nexus Standards NS-10 – policies and clauses | پێشنووس | under review |
NXS-STD-ST-000007 | Nexus Standards NS-11 – verification and monitoring | پێشنووس | under review |
NXS-STD-ST-000008 | Nexus Standards NS-13 – open standards development process | پێشنووس | under review |
NXS-STD-SC-000002 | Nexus clause, policy, attestation and proposal schemas v1 (NS-10, NS-11, NS-13) | پێشنووس | under review |
NXS-STD-ST-000009 | Nexus Standards NS-2 – citation and attribution | پێشنووس | under review |
NXS-STD-ST-000010 | Nexus Standards NS-4 – structure and drafting of Nexus Standards and documents | پێشنووس | under review |
NXS-STD-ST-000011 | Nexus Standards NS-5 – figures, maps and visualisation | پێشنووس | under review |
NXS-STD-ST-000012 | Nexus Standards NS-12 – software, models and AI/ML artefacts | پێشنووس | under review |
NXS-STD-ST-000013 | Nexus Standards NS-14 – conformance and crosswalk to external standards | پێشنووس | under review |
NXS-STD-RP-000001 | Standards landscape dossier: external risk, resilience, security, data and open-standards bodies crosswalked for the Nexus Standards | پێشنووس | under review |
NXS-STD-DS-000001 | External standards register: 151 standards with body, version, URL, domain, access, relation and verification flag | پێشنووس | under review |
NXS-STD-DS-000002 | Ecosystem coverage register: sites, 216 areas with governing standards and artefact kinds, 303 naming findings | پێشنووس | under review |
NXS-STD-ST-000014 | NS-15 System model binding (subjects, passports, chronotopes, routes, engines, cells, agents) | پێشنووس | under review |
NXS-STD-SC-000003 | Nexus subject passport envelope schema v1 (NS-15) | پێشنووس | under review |
NXS-STD-ST-000015 | NS-16 UNI application profile (articles, documents, code, data, APIs, interfaces) | پێشنووس | under review |
NXS-STD-RS-000002 | Process and pipeline graphs for the site DAG component (NS-13 track, body tracks, conformance, record lifecycle, routing, monitoring) | پێشنووس | under review |
NXS-STD-RS-000003 | Standard packages register: one page series per open standard (CAP 1.2, STAC, PROV-O as the template) | پێشنووس | under review |
NXS-STD-DC-000005 | Open standards packages index and the standard package page series (CAP 1.2, STAC, PROV-O: package, clause map, updates) | پێشنووس | under review |
NXS-STD-DC-000006 | Development tracks page: NS-13 lifecycle and the OASIS, W3C, IETF, OGC and ISO/IEC tracks as interactive graphs | پێشنووس | under review |
NXS-STD-DC-000007 | Contribute to an open standard: step-through guide and the channels of the packaged standards | پێشنووس | under review |
NXS-STD-DC-000008 | Standards pipelines page: routing, monitoring, conformance pipeline and record lifecycle graphs | پێشنووس | under review |
NXS-STD-SW-000008 | Site open-standards module: retired process-graph component (layout, SVG, play/step/scrub runtime) and the standard package page generator | پێشنووس | under review |
NXS-STD-RP-000004 | Standards development literature review: EU reform, SMART standards, living tracks, foundation processes, emerging-technology standards, conformance practice, feeds | پێشنووس | under review |
NXS-STD-RS-000004 | Feed-source proposals register: one proposed row per body feed (all LEGAL_REVIEW_REQUIRED) | پێشنووس | under review |
NXS-STD-SW-000009 | Tests for the open-standards site module (DAG layout, rendering, packages and stubs, routing data) | پێشنووس | under review |
NXS-STD-RS-000005 | Governance, legal structure, national adoption, open boundary and disclaimers register | پێشنووس | under review |
NXS-STD-SW-000010 | Governance documents generator | پێشنووس | under review |
NXS-STD-DC-000010 | پێڕستی ڕێنمای حوکمڕانی | پێشنووس | under review |
NXS-STD-DC-000011 | Nexus Standards Charter (draft target) | پێشنووس | under review |
NXS-STD-DC-000012 | وەرگرتن، گونجاندن و سەروەریی نیشتمانی | پێشنووس | under review |
NXS-STD-DC-000013 | سنووری کراوە، مافی خاوەندارێتیی فکری و مۆڵەتدان | پێشنووس | under review |
NXS-STD-DC-000014 | پێکهاتەی یاسایی و ئامرازەکان | پێشنووس | under review |
NXS-STD-DC-000015 | ڕەتکردنەوەی بەرپرسیارێتی و زمانی یاسایی | پێشنووس | under review |
NXS-STD-DC-000016 | ڕێکارەکانی ئاسایش، سەلامەتی و بەردەوامی | پێشنووس | under review |
NXS-STD-DC-000017 | ئامادەیی بۆ دەستپێکردن | پێشنووس | under review |
NXS-STD-DC-000018 | ڕێنمایی ئەیجێنت | پێشنووس | under review |
NXS-STD-DC-000019 | لاپەڕەکانی سایت: پارێزگاری، وەرگرتنی نیشتمانی و سنووری کراوە | پێشنووس | under review |
NXS-STD-DC-000020 | لاپەڕەکانی سایت: ئاگادارکردنەوە یاساییەکان | پێشنووس | under review |
NXS-STD-RS-000006 | Feed updates from admitted official feeds (generated) | پێشنووس | under review |
NXS-STD-SW-000011 | Feed export importer | پێشنووس | under review |
NXS-STD-PC-000004 | Proposal: context code allocation rules and domain codes CMP, DTW, SNS, PNT | پێشنووس | under review |
NXS-STD-DS-000004 | Nexus Risk Standards catalogue | پێشنووس | under review |
NXS-STD-SW-000012 | Nexus Risk Standards document generator | پێشنووس | under review |
NXS-STD-DC-000021 | Nexus Risk Standards: the systemic architecture | پێشنووس | under review |
NXS-STD-PC-000005 | Proposal: Nexus Risk Standards systemic catalogue | پێشنووس | under review |
NXS-STD-DS-000005 | Nexus-native risk taxonomy: the full risk spectrum | پێشنووس | under review |
NXS-STD-SW-000013 | Machine exports generator: ontology, taxonomy, shapes, JSON-LD, OSCAL, ODRL | پێشنووس | under review |
NXS-STD-SW-000014 | Release manifest, signing and zero-trust verification | پێشنووس | under review |
NXS-STD-SW-000015 | Read-only standards query layer | پێشنووس | under review |
NXS-STD-SW-000016 | Agent interface (Model Context Protocol server) | پێشنووس | under review |
NXS-STD-SW-000017 | Standards HTTP server | پێشنووس | under review |
NXS-STD-SW-000018 | Nexus Standards one-command CLI | پێشنووس | under review |
NXS-STD-PC-000006 | Proposal: full-spectrum completion, risk taxonomy and AI-native standards infrastructure | پێشنووس | under review |
NXS-STD-DC-000022 | Quick start: use the Nexus Standards in one command | پێشنووس | under review |
NXS-STD-DS-000006 | Nexus native register | پێشنووس | under review |
NXS-STD-DS-000007 | Nexus harmonisation register | پێشنووس | under review |
NXS-STD-DS-000008 | Nexus Risk Standards catalogue source | پێشنووس | under review |
NXS-STD-SW-000020 | Native authority extractor | پێشنووس | under review |
NXS-STD-SW-000021 | Risk Standards catalogue and taxonomy generator | پێشنووس | under review |
NXS-STD-PC-000007 | Native convergence of the Nexus Risk Standards | پێشنووس | under review |
NXS-STD-DS-000009 | Participation register: start-up, cadence, working groups, expert communities and gateways | پێشنووس | under review |
NXS-STD-SW-000022 | Cadence library (council, committee and working group sessions) | پێشنووس | under review |
NXS-STD-DC-000023 | Participate page of the Nexus Standards site | پێشنووس | under review |
NXS-STD-PC-000008 | Participation, cadence and gateways | پێشنووس | under review |
NXS-STD-DC-000024 | Participation, cadence and gateways (operating manual) | پێشنووس | under review |
NXS-STD-DS-000010 | Nexus-native risk vocabulary and risk classes | پێشنووس | under review |
NXS-STD-DS-000011 | Industries, industry groups and proposed sector codes | پێشنووس | under review |
NXS-STD-DS-000012 | Disciplines mapped to domains and NHS-1 hazard domains | پێشنووس | under review |
NXS-STD-PC-000009 | Risk atlas 1.1: NHS-1 1.1.0, risk vocabulary, industries, sectors and jurisdictions | پێشنووس | under review |
NXS-STD-DC-000025 | Risk atlas, vocabulary and classifications (guide) | پێشنووس | under review |
NXS-STD-DC-000026 | Expert audit of the Nexus Standards and the plan to make them world class | پێشنووس | under review |
NXS-STD-DC-000027 | Bibliography and acknowledgement of prior work | پێشنووس | under review |
NXS-STD-PO-000001 | Policy on information hazards and dual-use content | پێشنووس | under review |
NXS-STD-DC-000028 | Maintenance of Nexus Standards: systematic review, versioning, errata, stabilisation and withdrawal | پێشنووس | under review |
NXS-STD-DS-000013 | Register of normative requirements | پێشنووس | under review |
NXS-STD-TN-000001 | NHS-2 model specification: kinds, quantities, relations, evidence and provenance | پێشنووس | under review |
NXS-STD-DC-000029 | New work items NRS-C17 to NRS-C24: scope and justification | پێشنووس | under review |
NXS-STD-PC-000010 | New core risk standards NRS-C17 to NRS-C24 | پێشنووس | under review |
NXS-STD-DC-000030 | Terms of reference of workstreams W1 to W8 | پێشنووس | under review |
NXS-STD-DC-000031 | Invitations to the expert communities, councils and liaison organisations | پێشنووس | under review |
NXS-STD-PO-000002 | Policy on accessibility and languages | پێشنووس | under review |
NXS-STD-DC-000032 | Conformity assessment scheme (first proposed draft) | پێشنووس | under review |
NXS-STD-DC-000033 | Programme cover note of the Secretariat | پێشنووس | under review |
NXS-STD-DS-000014 | Information-hazard screening register | پێشنووس | under review |
NXS-STD-DS-000015 | Circulation for technical review and comment, and the technical review areas | پێشنووس | under review |
NXS-STD-DC-000034 | Notice of circulation for technical review and comment | پێشنووس | under review |
NXS-STD-SW-000023 | Circulation notice and technical review builder | پێشنووس | under review |
NXS-STD-SW-000024 | Nexus Standards repository check (open boundary, links and paths, syntax, information-hazard screen, proposals) | پێشنووس | under review |
NXS-STD-DC-000035 | Release policy of the open repository and the content of each release | پێشنووس | under review |
NXS-STD-RS-000007 | Roadmap of the Nexus Standards to the first official release (target 2030) | پێشنووس | under review |
NXS-STD-DC-000036 | Roadmap to 2030 and invitation to all stakeholders | پێشنووس | under review |
پرسیار و وەڵام.
Is a UNI a brand or a product name?
Can a UNI be assigned manually?
What happens when an artefact is withdrawn?
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 بۆ کۆدی سەرچاوە. ستانداردە دەرەکییەکان بە ناو، ژمارە و بەستەر لە ژێر مۆڵەتەکانی خۆیاندا ئاماژەیان پێدەدرێت. داتا، کتێبخانە و فۆنتەکانی لایەنی سێیەم مۆڵەتەکانی خۆیان دەپارێزن: بڕوانە ئاگادارییەکانی لایەنی سێیەم.