Skip to content
StandardsIdentifier
Unique Nexus Identifier (UNI)

The UNI: catalogue and resolver

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.

The UNI, segment by segment
Each segment of a Unique Nexus Identifier in reading order, with the number of codes the registry defines for it. Dashed segments are optional. A UNI identifies; it never certifies.Source: the Nexus Standards registry (identifier); the regions register.
  • 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.
01دستاویز

Read a 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.

02عمل

The process.

UNI anatomy · parse, resolve, citeNexus Standards registry
prefixNXSfixedscope<SCOPE>32 codescat<CAT>38 artefact, 9 record codesregion<REGION>ISO 3166-1 or M49serial<SERIAL>six digits, allocatedversion@<VERSION>semver or record version

Illustrative 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
03Grammar

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
SegmentفارمMeaning
NXSfixedPrefix. 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).
SCOPEthree lettersA 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)
CATtwo lettersArtefact 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.
DOMAINoptional, three lettersDomain code from registry/domains.yaml (WAT water, ENE energy, FOO food, HLT health, BIO biodiversity, CLI climate, 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)
SECTORoptional, three lettersSector code from registry/sectors.yaml (AGR, WUT, EUT, HSY, FNI, TRL, CIT, INM, DTC, PUB, RED, HUO, IGO)
REGIONoptionalISO 3166-1 alpha-3 country code (KEN, CAN) or UN M49 area code written as M followed by three digits (M002 Africa, M142 Asia); registry registry/regions.yaml
ENVoptional, three lettersPRD production, STG staging, LBX lab, FIX fixture; used by contextual records (NS-9)
SERIALsix digitsAllocated by a catalogue or a record allocation authority per full prefix (SCOPE, CAT and context segments); never reused
VERSIONoptionalSemantic 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 or 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

Proposal 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. Check: 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.

قاعدہText
CA-1A 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-2A code is unique across every registry: scopes, domains, sectors, environments and ISO 3166-1 alpha-3.
CA-3A 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-4A 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-5A 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-6One concept per code. Each code has a definition, what it includes and excludes, and the external standards it crosswalks to.
CA-7Ids are stable, lowercase kebab-case English. Labels are in sentence case. Neither encodes a status.
CA-8Append-only. A code is never reassigned or deleted. A retired code keeps its entry with deprecated: true and supersededBy.
CA-9A 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-10Adding 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:

کوڈIdلیبلCrosswalks to
CMPcomputeCompute and accelerated infrastructureISO/IEC JTC 1/SC 38 and SC 39; ISO/IEC 22123
DTWdigital-twinsڈیجیٹل جڑواں اور نقلی مشقیںISO/IEC 30173:2023; ISO/IEC JTC 1/SC 41; ISO 23247
SNSsensingSensing and measurement networksOGC SensorThings API and SensorML; W3C/OGC SOSA/SSN; IEEE 1451
PNTpntمقام کا تعین، رہنمائی اور وقت بندی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 and lists PNT as related.

A future quantum-technology code cannot be QTM or QNT, because both fall in the user-assigned range QMA to QZZ. CA-3 catches this kind of collision before allocation.

04Scopes

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.

کوڈKindلیبل
CMDنظاممربوط موقف اور انتظامی خلاصہ
NSTنظامشہری مشترکہ عملیاتی منظرنامہ
DSSنظامDecision support, cases and deliberation
CORنظامکمپیوٹنگ، نوڈز اور رن ٹائمز
NXQنظامسافٹ ویئر، ماڈلز اور صلاحیت کا دورِ حیات
GRXنظامCanonical risk data, records and provenance
EOPنظامزمینی مشاہدہ اور ڈیجیٹل جڑواں نمونے
EWSنظامکثیر خطرات کی نگرانی اور انتباہ
AAPنظامAnticipatory action and triggers
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
GCRorganisationThe Global Centre for Risk and Innovation (GCRI Canada)
GRForganisationGlobal Risks Forum
GRAorganisationGlobal Risks Alliance
NXOorganisationReserved organisation scope for a multi-party consortium (entity under legal review)
ELPorganisationReserved organisation scope (withdrawn before use)
OBSorganisationReserved organisation scope (withdrawn before use)
STDcross cuttingThe Nexus Standards themselves
LEGcross cuttingLegal, intellectual property and licensing
GOVcross cuttingGovernance, decisions and policy
PRGcross cuttingProgramme, waves and work items
UXKcross cuttingUI/UX kit, design tokens and assets
ALLcross cuttingEcosystem-wide
05Categories

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.

کوڈCategoryDataCite type
SWSoftwareSoftware
SVService or APIService
SCSchema or contractدیگر
MGDatabase migrationSoftware
WFWorkflowWorkflow
MDماڈلماڈل
DSDatasetDataset
EVشواہد کا ریکارڈDataset
ARمضمونJournalArticle
PPPreprintPreprint
RPرپورٹرپورٹ
TNTechnical noteText
DCدستاویزاتText
DLDeliverableرپورٹ
WPWorking paperText
BKBook or chapterBook
CPConference paperConferencePaper
THThesisDissertation
PTPatentدیگر
STمعیارمعیار
PCPolicy or directiveText
PSPresentationText
POPosterText
FGشکلImage
PLPlot or visualisationImage
DGDiagramImage
PHPhotoImage
MPMap productImage
VDVideoAudiovisual
LSLesson or courseInteractiveResource
PYPhysical objectPhysicalObject
PAParticipation recordدیگر
RSProgramme status recordدیگر
DPDeployment or instance (NS-9 context)دیگر
PRProgramme instance (NS-9 context)دیگر
CLClause (NS-10 obligation)دیگر
ATConformance attestation (NS-11)دیگر
OTدیگردیگر
کوڈRecord kindNote
OBObservation factrecord kind (NS-3)
SRSource releaserecord kind (NS-3)
INIndicator definitionrecord kind (NS-3)
MEMeasure definitionrecord kind (NS-3)
BDBoundary versionrecord kind (NS-3)
CTChronotope versionrecord kind (NS-3)
CRCorrection recordrecord kind (NS-3)
APAnalytical product recordrecord kind (NS-3)
SUSubject (place, asset, organisation)record kind (NS-3)
06The record

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.

Record explorer · schema, example, crosswalkNexus Standards registry

Artefact record (NS-1) · 32 fields · 12 required

  • uni required stringThe UNI (Unique Nexus Identifier), NS-1 grammar, without @version.
  • displayAlias stringPublic Registry short form (NX-R-47092) shown next to the UNI during the transition.
  • registryState enumPublic registry state; corrections keep the UNI and add a version.
  • legacyUni stringDotted UNI v0 this record replaces, for crosswalk (for example data.eo.stac.catalogue).
  • title required string
  • description string
  • scope required string
  • category required string
  • region string
  • domain stringDOMAIN segment code from the domains register (NS-1 v0.2); present when the identifier carries it.
  • sector stringSECTOR segment code from the sectors register (NS-1 v0.2).
  • environment enumENV segment code (NS-1 v0.2).
  • contextName stringNS-16 context name: the identifier without CAT and SERIAL; derived, never allocated.
  • systemId stringFunctional system class id (systemId) from the Nexus Standards register#scopes when scope is a SYSTEM.
  • status required enum
  • currentVersion string
  • versions array
    • version string
    • date string
    • gitSha string
    • digest string
    • note string
  • creators required array
    • name string
    • type enum
    • affiliation string
    • orcid string
    • ror string
  • publisherRef required stringEntity reference of the publishing institution (registry/governance.yaml#bodies); the institution stays publisher of record for institutional artefacts.
  • publicationDate required string
  • language string
  • keywords array
  • rights required object
    • license stringSPDX licence identifier or expression, or a LicenseRef- string for a licence that has no SPDX identifier.
    • rightsHolderRef string
    • accessRight enum
    • embargoDate string
  • legalState required enum
  • claimCeiling required enum
  • locations required array
    • kind enum
    • value string
    • digest string
  • relatedIdentifiers array
    • relation enum
    • identifier string
    • identifierType enum
  • supersededBy string
  • workPackageId string
  • directiveRefs arrayReferences to the recorded decisions or policies under which the artefact was produced.
  • notes string
  • context objectNS-9: this record is a deployment, instance or programme instance of the concept ofUni, in a context.
    • ofUni string
    • domains arrayids from the domains register
    • sectors arrayids from the sectors register
    • jurisdictions array
    • hostRef string
    • environment enum
    • validFrom string
    • validUntil string
    • conformsTo arrayNexus 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 fieldSchema.orgDataCiteZenodoCodeMetaماخذ
uniidentifier (PropertyValue, propertyID urn:nexus:uni)alternateIdentifier (alternateIdentifierType NXS)metadata.related_identifiers[] (scheme other)identifierمسودہ
titlenametitles[].titlemetadata.titlenameمسودہ
descriptiondescriptiondescriptions[].description (Abstract)metadata.descriptiondescriptionمسودہ
scope·subjects[] (subjectScheme nexus-scope)metadata.keywords[]·مسودہ
categoryadditionalTypetypes.resourceTypeGeneralmetadata.upload_type / publication_type / image_typeapplicationCategoryregistry
regionspatialCoveragegeoLocations[].geoLocationPlacemetadata.locations[]·مسودہ
statuscreativeWorkStatus··developmentStatusمسودہ
currentVersionversionversionmetadata.versionversionمسودہ
versions·relatedIdentifiers (IsNewVersionOf, IsPreviousVersionOf)versions (concept DOI)·مسودہ
creatorscreator / authorcreators[]metadata.creators[]authorمسودہ
publisherRefناشرناشرmetadata.publisher (Zenodo)ناشرمسودہ
publicationDatedatePublishedpublicationYear; dates[] (Issued)metadata.publication_datedatePublishedمسودہ
languageinLanguagelanguagemetadata.language·مسودہ
keywordskeywordssubjects[]metadata.keywords[]keywordsمسودہ
rights.licenselicenserightsList[].rightsIdentifier (SPDX)metadata.licenselicenseمسودہ
rights.accessRightconditionsOfAccess·metadata.access_right·مسودہ
legalState····مسودہ
claimCeiling····مسودہ
locationsurl / contentUrl / codeRepositoryalternateIdentifiers[] (URL)files[] / metadata.related_identifiers[]codeRepository / downloadUrlمسودہ
relatedIdentifiersisPartOf / citation / isBasedOnrelatedIdentifiers[] (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.

07Resolver

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.

08فہرست

Records in the standards scope

104 records: the identifiers of the standards themselves, with their status and rights state.

UNITitleحیثیتRights state
NXS-STD-ST-000001Nexus Standards NS-1 – the UNI and artefact catalogueمسودہunder review
NXS-STD-SW-000002UNI command-line tool (validate, parse, next, mint, catalogue, export) – reference implementationمسودہunder review
NXS-STD-SC-000001UNI artefact record schema v1مسودہunder review
NXS-STD-ST-000002Open-standards and open-source stack under the UNIمسودہunder review
NXS-STD-SW-000005UNI data profile (STAC, DCAT, PROV-O crosswalks), NS-3bمسودہunder review
NXS-STD-ST-000003Nexus Standards NS-3 – risk record UNIs (grammar, legacy crosswalk, allocation authority)مسودہunder review
NXS-STD-SW-000006Nexus Standards repository validator (registry invariants, schema, STD catalogue, embedded UNIs, register of implementations)مسودہunder review
NXS-STD-DC-000001Nexus Standards repository documentation (README, governance, contributing, agent boot)مسودہunder review
NXS-STD-SW-000007Nexus Standards site page generator and WordPress draft publisherمسودہunder review
NXS-STD-DC-000002Nexus Standards site pages for nexustandards.com (overview, NS-1, catalogue and resolver, governance)مسودہunder review
NXS-STD-ST-000004Nexus Standards NS-0 – constitution and principlesمسودہunder review
NXS-STD-ST-000005Nexus Standards NS-9 – contextual UNIs (deployments, instances, programme instances)مسودہunder review
NXS-STD-DC-000003Nexus Standards subsites (systemic architecture index and one landing page per subsite)مسودہunder review
NXS-STD-ST-000006Nexus Standards NS-10 – policies and clausesمسودہunder review
NXS-STD-ST-000007Nexus Standards NS-11 – verification and monitoringمسودہunder review
NXS-STD-ST-000008Nexus Standards NS-13 – open standards development processمسودہunder review
NXS-STD-SC-000002Nexus clause, policy, attestation and proposal schemas v1 (NS-10, NS-11, NS-13)مسودہunder review
NXS-STD-ST-000009Nexus Standards NS-2 – citation and attributionمسودہunder review
NXS-STD-ST-000010Nexus Standards NS-4 – structure and drafting of Nexus Standards and documentsمسودہunder review
NXS-STD-ST-000011Nexus Standards NS-5 – figures, maps and visualisationمسودہunder review
NXS-STD-ST-000012Nexus Standards NS-12 – software, models and AI/ML artefactsمسودہunder review
NXS-STD-ST-000013Nexus Standards NS-14 – conformance and crosswalk to external standardsمسودہunder review
NXS-STD-RP-000001Standards landscape dossier: external risk, resilience, security, data and open-standards bodies crosswalked for the Nexus Standardsمسودہunder review
NXS-STD-DS-000001External standards register: 151 standards with body, version, URL, domain, access, relation and verification flagمسودہunder review
NXS-STD-DS-000002Ecosystem coverage register: sites, 216 areas with governing standards and artefact kinds, 303 naming findingsمسودہunder review
NXS-STD-ST-000014NS-15 System model binding (subjects, passports, chronotopes, routes, engines, cells, agents)مسودہunder review
NXS-STD-SC-000003Nexus subject passport envelope schema v1 (NS-15)مسودہunder review
NXS-STD-ST-000015NS-16 UNI application profile (articles, documents, code, data, APIs, interfaces)مسودہunder review
NXS-STD-RS-000002Process and pipeline graphs for the site DAG component (NS-13 track, body tracks, conformance, record lifecycle, routing, monitoring)مسودہunder review
NXS-STD-RS-000003Standard packages register: one page series per open standard (CAP 1.2, STAC, PROV-O as the template)مسودہunder review
NXS-STD-DC-000005Open standards packages index and the standard package page series (CAP 1.2, STAC, PROV-O: package, clause map, updates)مسودہunder review
NXS-STD-DC-000006Development tracks page: NS-13 lifecycle and the OASIS, W3C, IETF, OGC and ISO/IEC tracks as interactive graphsمسودہunder review
NXS-STD-DC-000007Contribute to an open standard: step-through guide and the channels of the packaged standardsمسودہunder review
NXS-STD-DC-000008Standards pipelines page: routing, monitoring, conformance pipeline and record lifecycle graphsمسودہunder review
NXS-STD-SW-000008Site open-standards module: retired process-graph component (layout, SVG, play/step/scrub runtime) and the standard package page generatorمسودہunder review
NXS-STD-RP-000004Standards development literature review: EU reform, SMART standards, living tracks, foundation processes, emerging-technology standards, conformance practice, feedsمسودہunder review
NXS-STD-RS-000004Feed-source proposals register: one proposed row per body feed (all LEGAL_REVIEW_REQUIRED)مسودہunder review
NXS-STD-SW-000009Tests for the open-standards site module (DAG layout, rendering, packages and stubs, routing data)مسودہunder review
NXS-STD-RS-000005Governance, legal structure, national adoption, open boundary and disclaimers registerمسودہunder review
NXS-STD-SW-000010Governance documents generatorمسودہunder review
NXS-STD-DC-000010Governance directory indexمسودہunder review
NXS-STD-DC-000011Nexus Standards Charter (draft target)مسودہunder review
NXS-STD-DC-000012National adoption, adaptation and sovereigntyمسودہunder review
NXS-STD-DC-000013Open boundary, IPR and licensingمسودہunder review
NXS-STD-DC-000014Legal structure and instrumentsمسودہunder review
NXS-STD-DC-000015Disclaimers and legal languageمسودہunder review
NXS-STD-DC-000016Security, safety and continuity measuresمسودہunder review
NXS-STD-DC-000017Go-live readinessمسودہunder review
NXS-STD-DC-000018Agent guideمسودہunder review
NXS-STD-DC-000019Site pages: stewardship, national adoption and open boundaryمسودہunder review
NXS-STD-DC-000020Site pages: legal noticesمسودہunder review
NXS-STD-RS-000006Feed updates from admitted official feeds (generated)مسودہunder review
NXS-STD-SW-000011Feed export importerمسودہunder review
NXS-STD-PC-000004Proposal: context code allocation rules and domain codes CMP, DTW, SNS, PNTمسودہunder review
NXS-STD-DS-000004Nexus Risk Standards catalogueمسودہunder review
NXS-STD-SW-000012Nexus Risk Standards document generatorمسودہunder review
NXS-STD-DC-000021Nexus Risk Standards: the systemic architectureمسودہunder review
NXS-STD-PC-000005Proposal: Nexus Risk Standards systemic catalogueمسودہunder review
NXS-STD-DS-000005Nexus-native risk taxonomy: the full risk spectrumمسودہunder review
NXS-STD-SW-000013Machine exports generator: ontology, taxonomy, shapes, JSON-LD, OSCAL, ODRLمسودہunder review
NXS-STD-SW-000014Release manifest, signing and zero-trust verificationمسودہunder review
NXS-STD-SW-000015Read-only standards query layerمسودہunder review
NXS-STD-SW-000016Agent interface (Model Context Protocol server)مسودہunder review
NXS-STD-SW-000017Standards HTTP serverمسودہunder review
NXS-STD-SW-000018Nexus Standards one-command CLIمسودہunder review
NXS-STD-PC-000006Proposal: full-spectrum completion, risk taxonomy and AI-native standards infrastructureمسودہunder review
NXS-STD-DC-000022Quick start: use the Nexus Standards in one commandمسودہunder review
NXS-STD-DS-000006Nexus native registerمسودہunder review
NXS-STD-DS-000007Nexus harmonisation registerمسودہunder review
NXS-STD-DS-000008Nexus Risk Standards catalogue sourceمسودہunder review
NXS-STD-SW-000020Native authority extractorمسودہunder review
NXS-STD-SW-000021Risk Standards catalogue and taxonomy generatorمسودہunder review
NXS-STD-PC-000007Native convergence of the Nexus Risk Standardsمسودہunder review
NXS-STD-DS-000009Participation register: start-up, cadence, working groups, expert communities and gatewaysمسودہunder review
NXS-STD-SW-000022Cadence library (council, committee and working group sessions)مسودہunder review
NXS-STD-DC-000023Participate page of the Nexus Standards siteمسودہunder review
NXS-STD-PC-000008Participation, cadence and gatewaysمسودہunder review
NXS-STD-DC-000024Participation, cadence and gateways (operating manual)مسودہunder review
NXS-STD-DS-000010Nexus-native risk vocabulary and risk classesمسودہunder review
NXS-STD-DS-000011Industries, industry groups and proposed sector codesمسودہunder review
NXS-STD-DS-000012Disciplines mapped to domains and NHS-1 hazard domainsمسودہunder review
NXS-STD-PC-000009Risk atlas 1.1: NHS-1 1.1.0, risk vocabulary, industries, sectors and jurisdictionsمسودہunder review
NXS-STD-DC-000025Risk atlas, vocabulary and classifications (guide)مسودہunder review
NXS-STD-DC-000026Expert audit of the Nexus Standards and the plan to make them world classمسودہunder review
NXS-STD-DC-000027Bibliography and acknowledgement of prior workمسودہunder review
NXS-STD-PO-000001Policy on information hazards and dual-use contentمسودہunder review
NXS-STD-DC-000028Maintenance of Nexus Standards: systematic review, versioning, errata, stabilisation and withdrawalمسودہunder review
NXS-STD-DS-000013Register of normative requirementsمسودہunder review
NXS-STD-TN-000001NHS-2 model specification: kinds, quantities, relations, evidence and provenanceمسودہunder review
NXS-STD-DC-000029New work items NRS-C17 to NRS-C24: scope and justificationمسودہunder review
NXS-STD-PC-000010New core risk standards NRS-C17 to NRS-C24مسودہunder review
NXS-STD-DC-000030Terms of reference of workstreams W1 to W8مسودہunder review
NXS-STD-DC-000031Invitations to the expert communities, councils and liaison organisationsمسودہunder review
NXS-STD-PO-000002Policy on accessibility and languagesمسودہunder review
NXS-STD-DC-000032Conformity assessment scheme (first proposed draft)مسودہunder review
NXS-STD-DC-000033Programme cover note of the Secretariatمسودہunder review
NXS-STD-DS-000014Information-hazard screening registerمسودہunder review
NXS-STD-DS-000015Circulation for technical review and comment, and the technical review areasمسودہunder review
NXS-STD-DC-000034Notice of circulation for technical review and commentمسودہunder review
NXS-STD-SW-000023Circulation notice and technical review builderمسودہunder review
NXS-STD-SW-000024Nexus Standards repository check (open boundary, links and paths, syntax, information-hazard screen, proposals)مسودہunder review
NXS-STD-DC-000035Release policy of the open repository and the content of each releaseمسودہunder review
NXS-STD-RS-000007Roadmap of the Nexus Standards to the first official release (target 2030)مسودہunder review
NXS-STD-DC-000036Roadmap to 2030 and invitation to all stakeholdersمسودہunder review
09سوالات

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

Is a UNI a brand or a product name?
No. A UNI is a catalogue code, comparable in kind to a DOI or an ISBN. It carries no trademark claim and is not presented as a product name.
Can a UNI be assigned manually?
No. Serials are allocated only through a catalogue or the data fabric; a manually entered serial is invalid (NS1-R2).
What happens when an artefact is withdrawn?
Its UNI is retained; the record is marked withdrawn or points to the artefact that succeeded it. UNIs are not deleted or reused.
معیارات

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

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