Skip to content
标准标识符
唯一 Nexus 标识符(UNI)

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.

逐段解读 UNI
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 个前缀代码,例如 NXS。
  • SCOPE:32 个范围代码,例如 GRX。
  • CAT:38 个类别代码,例如 AR。
  • DOMAIN(可选):30 个领域代码,例如 WAT。
  • SECTOR(可选):13 个部门代码,例如 UTL。
  • REGION(可选):249 个区域代码,例如 CAN。
  • SERIAL:序列号,例如 000012。
  • @VERSION(可选):版本,例如 1.0.0。
01工具

解读 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流程

流程。

UNI 结构 · 解析、定位、引用Nexus Standards 登记册
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

示例标识符模式。启用脚本后,可输入 UNI,系统会对照登记册检查每一段,在记录已发布时解析到该记录,并以 URN、解析器链接和引用格式表示。

UNI 结构逐段解读 NS-1 语法,附登记册的范围和类别代码。解析链接指向解析器;本页不分配任何标识符。

范围代码
32
SCOPE
类别
38
CAT
领域
30
DOMAIN
区域
249
ISO 3166 alpha-3
03语法

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固定前缀。选择它而非 NEX because it reads as a code, not a word, and because NEX- is crowded by brands. NXS-S01 至 NXS-S20 are also the neutral identifiers of the functional system classes (section 2).
SCOPE三个字母A functional system class (EWS, EOP, SIG, GRX, OPS and the others in section 2), an organisation (GCR, GRF, GRA, NXO)或跨领域范围(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可选,三个字母Domain code from registry/domains.yaml (WAT 水, ENE 能源, FOO 食品, HLT 健康, BIO 生物多样性, CLI 气候, DRR, EWN, HUM, INF, SCH, SEC, ZTA, FNC, DSC, ERM, DRG, AIS, DAT, GSP, PRV, IDF, SFW, NAT, SDP, LIC;拟议: CMP, DTW, SNS, PNT)
SECTOR可选,三个字母部门代码,来自 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 亚洲);登记册 registry/regions.yaml
ENV可选,三个字母PRD 生产, STG 预发布, LBX 实验室, FIX 固定样例;供情境记录使用(NS-9)
SERIAL六位数字Allocated by a catalogue or a record allocation authority per full prefix (SCOPE, CAT and context segments); never reused
VERSION可选Semantic version of an artefact (1.2.0)或整数 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),因此标识符无需分隔符即可被确定性地解析。不含 CAT 和 SERIAL 的标识符即为 情境名称: 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)是情境的权威记录。

机器形式:URN urn:nexus:uni:NXS-EWS-DS-000042;解析器路径 /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 列出已发布记录);情境路径 /ctx/NXS-GRX-WAT-CAN (该情境的每条已发布记录);字段名 uni ,适用于每条记录、每个 API、每个模式和每张表。

Existing dotted identifiers (for example data.eo.stac.catalogue)为 UNI v0。它们被记录为 legacyUni ,置于新记录中以供对照,且永不再次分配。

1.1 情境代码分配

提议 NXS-STD-PC-000004 引入本节,状态为开放(OPEN);这些规则适用于此后分配的每一个代码。机器形式: 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-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 至 AAZ, QMA 至 QZZ, XAA 至 XZZ, ZZA 至 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-6每个代码一个概念。每个代码都有定义、包含和排除的内容,以及其对照的外部标准。
CA-7标识符为稳定的小写连字符英文。标签采用句首大写。两者均不编码状态。
CA-8仅可追加。代码绝不会被重新分配或删除。已停用的代码保留其条目,并带有 deprecated: true 和 supersededBy.
CA-9新代码保持 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.

沿用条款: AAP, the scope code of the anticipatory-action class, was allocated before CA-3 and lies inside the user-assigned range AAA 至 AAZ. It is kept under CA-8.

依据这些规则拟议的技术领域:

代码ID标签对照至
CMPcompute计算与加速基础设施ISO/IEC JTC 1/SC 38 和 SC 39;ISO/IEC 22123
DTWdigital-twins数字孪生与仿真ISO/IEC 30173:2023; ISO/IEC JTC 1/SC 41; ISO 23247
SNSsensing传感与测量网络OGC SensorThings API 与 SensorML;W3C/OGC SOSA/SSN;IEEE 1451
PNTpnt定位、导航与授时IEEE 1588;ITU-T G.8271 和 G.8272;ITU-R TF 系列;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 视为相关。

未来的量子技术代码不能是 QTM 或 QNT,因为两者都落在用户自行分配的范围内 QMA 至 QZZ。CA-3 在分配之前即可发现此类冲突。

04范围

范围代码

针对 系统、组织和跨领域范围的 32 个范围代码。代码用于分类;公开标签遵循标准的命名规则。在上方解析器中输入标识符时,其范围所在行会高亮显示。

代码类型标签
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系统可视化组合与工作流
FAC系统蓝图、构建与签署
APP系统应用目录与生命周期
RLS系统Participants, agreements and protocols
POR系统公众、客户与合作伙伴交付
LAB系统Research, experiments and simulation
GCR组织全球风险与创新中心(Global Centre for Risk and Innovation,GCRI Canada)
GRF组织全球风险论坛(Global Risks Forum)
GRA组织全球风险联盟(Global Risks Alliance)
NXO组织Reserved organisation scope for a multi-party consortium (entity under legal review)
ELP组织保留的组织范围(使用前已撤销)
OBS组织保留的组织范围(使用前已撤销)
STD跨领域The Nexus Standards themselves
LEG跨领域Legal, intellectual property and licensing
GOV跨领域Governance, decisions and policy
PRG跨领域Programme, waves and work items
UXK跨领域UI/UX kit, design tokens and assets
ALL跨领域Ecosystem-wide
05类别

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 类型
SW软件软件
SV服务或 API服务
SC模式或契约其他
MG数据库迁移软件
WF工作流工作流
MD建模建模
DS数据集数据集
EV证据记录数据集
AR条JournalArticle
PP预印本预印本
RP报告报告
TN技术说明文本
DC文档文本
DL交付成果报告
WP工作论文文本
BK图书或章节书籍
CP会议论文ConferencePaper
TH论点学位论文
PT专利其他
ST标准标准
PC政策或指令文本
PS演示文稿文本
PO海报文本
FG图图像
PLPlot or visualisation图像
DG图示图像
PH照片图像
MP地图产品图像
VD视频视听作品
LS课程或课堂InteractiveResource
PY实物对象PhysicalObject
PA参与记录其他
RS计划状态记录其他
DP部署或实例(NS-9 情境)其他
PR计划实例(NS-9 情境)其他
CL条款(NS-10 义务)其他
AT符合性证明(NS-11)其他
OT其他其他
代码记录类型备注
OB观测事实记录类型(NS-3)
SR来源版本记录类型(NS-3)
IN指标定义记录类型(NS-3)
ME度量定义记录类型(NS-3)
BD边界版本记录类型(NS-3)
CT时空版本记录类型(NS-3)
CR更正记录记录类型(NS-3)
AP分析产品记录记录类型(NS-3)
SU对象(地点、资产、组织)记录类型(NS-3)
06记录

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.

记录浏览器 · 模式、示例、对照Nexus Standards 登记册

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

示例记录 · 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" }
字段对照:Schema.org JSON-LD、DataCite、Zenodo、CodeMeta
记录字段Schema.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_typeapplicationCategory登记册
regionspatialCoveragegeoLocations[].geoLocationPlacemetadata.locations[]·草稿
statuscreativeWorkStatus··developmentStatus草稿
currentVersionversionversionmetadata.versionversion草稿
versions·relatedIdentifiers(IsNewVersionOf、IsPreviousVersionOf)versions(概念 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[](参考文献)metadata.related_identifiers[](references)·草稿
context····草稿

标注为“登记册”的行取自登记册中对 Zenodo 和 DataCite 的类别映射;标注为“草案”的行是对公共模式的编辑性映射,不属于登记册。

Record explorerthe artefact record schema with example records from the standards catalogue (scope STD). A record describes an artefact and its provenance.

07解析器

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目录

标准范围内的记录

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

UNI标题状态权利状态
NXS-STD-ST-000001Nexus Standards NS-1 – the UNI and artefact catalogue草稿审查中
NXS-STD-SW-000002UNI command-line tool (validate, parse, next, mint, catalogue, export) – reference implementation草稿审查中
NXS-STD-SC-000001UNI artefact record schema v1草稿审查中
NXS-STD-ST-000002UNI 之下的开放标准与开源技术栈草稿审查中
NXS-STD-SW-000005UNI data profile (STAC, DCAT, PROV-O crosswalks), NS-3b草稿审查中
NXS-STD-ST-000003Nexus Standards NS-3 – risk record UNIs (grammar, legacy crosswalk, allocation authority)草稿审查中
NXS-STD-SW-000006Nexus Standards repository validator (registry invariants, schema, STD catalogue, embedded UNIs, register of implementations)草稿审查中
NXS-STD-DC-000001Nexus Standards 代码库文档(README、治理、贡献、智能体启动)草稿审查中
NXS-STD-SW-000007Nexus Standards 网站页面生成器与 WordPress 草稿发布器草稿审查中
NXS-STD-DC-000002Nexus Standards site pages for nexustandards.com (overview, NS-1, catalogue and resolver, governance)草稿审查中
NXS-STD-ST-000004Nexus Standards NS-0 – constitution and principles草稿审查中
NXS-STD-ST-000005Nexus Standards NS-9 – contextual UNIs (deployments, instances, programme instances)草稿审查中
NXS-STD-DC-000003Nexus Standards 子站点(系统性架构索引以及每个子站点一个着陆页)草稿审查中
NXS-STD-ST-000006Nexus Standards NS-10 – policies and clauses草稿审查中
NXS-STD-ST-000007Nexus Standards NS-11 – verification and monitoring草稿审查中
NXS-STD-ST-000008Nexus Standards NS-13 – open standards development process草稿审查中
NXS-STD-SC-000002Nexus 条款、政策、证明和提案模式 v1(NS-10、NS-11、NS-13)草稿审查中
NXS-STD-ST-000009Nexus Standards NS-2 – citation and attribution草稿审查中
NXS-STD-ST-000010Nexus Standards NS-4 – structure and drafting of Nexus Standards and documents草稿审查中
NXS-STD-ST-000011Nexus Standards NS-5 – figures, maps and visualisation草稿审查中
NXS-STD-ST-000012Nexus Standards NS-12 – software, models and AI/ML artefacts草稿审查中
NXS-STD-ST-000013Nexus Standards NS-14 – conformance and crosswalk to external standards草稿审查中
NXS-STD-RP-000001标准格局档案:外部风险、韧性、安全、数据和开放标准机构与 Nexus Standards 的对照草稿审查中
NXS-STD-DS-000001External standards register: 151 standards with body, version, URL, domain, access, relation and verification flag草稿审查中
NXS-STD-DS-000002Ecosystem coverage register: sites, 216 areas with governing standards and artefact kinds, 303 naming findings草稿审查中
NXS-STD-ST-000014NS-15 系统模型绑定(主体、护照、时空体、路径、引擎、单元、智能体)草稿审查中
NXS-STD-SC-000003Nexus 主体护照封装模式 v1(NS-15)草稿审查中
NXS-STD-ST-000015NS-16 UNI 应用规范(文章、文档、代码、数据、API、接口)草稿审查中
NXS-STD-RS-000002网站 DAG 组件的流程与管线图(NS-13 轨道、主体轨道、一致性、记录生命周期、路由、监控)草稿审查中
NXS-STD-RS-000003标准包登记册:每个开放标准一个页面系列(以 CAP 1.2、STAC、PROV-O 为模板)草稿审查中
NXS-STD-DC-000005开放标准包索引及标准包页面系列(CAP 1.2、STAC、PROV-O:包、条款图、更新)草稿审查中
NXS-STD-DC-000006开发轨道页面:NS-13 生命周期以及 OASIS、W3C、IETF、OGC 和 ISO/IEC 轨道的交互图草稿审查中
NXS-STD-DC-000007为开放标准作贡献:分步指南以及打包标准的渠道草稿审查中
NXS-STD-DC-000008标准流水线页面:路由、监测、符合性流水线和记录生命周期图草稿审查中
NXS-STD-SW-000008Site open-standards module: retired process-graph component (layout, SVG, play/step/scrub runtime) and the standard package page generator草稿审查中
NXS-STD-RP-000004标准制定文献综述:欧盟改革、SMART 标准、动态轨道、基础流程、新兴技术标准、一致性实践、数据源草稿审查中
NXS-STD-RS-000004数据源提案登记册:每个机构数据源一条拟议行(全部 LEGAL_REVIEW_REQUIRED)草稿审查中
NXS-STD-SW-000009开放标准站点模块的测试(DAG 布局、渲染、包与桩、路由数据)草稿审查中
NXS-STD-RS-000005治理、法律结构、国家采用、开放边界和免责声明登记册草稿审查中
NXS-STD-SW-000010治理文件生成器草稿审查中
NXS-STD-DC-000010治理目录索引草稿审查中
NXS-STD-DC-000011Nexus Standards 章程(目标草案)草稿审查中
NXS-STD-DC-000012国家采用、调适与主权草稿审查中
NXS-STD-DC-000013开放边界、知识产权与许可草稿审查中
NXS-STD-DC-000014法律结构与文书草稿审查中
NXS-STD-DC-000015免责声明与法律措辞草稿审查中
NXS-STD-DC-000016安保、安全与连续性措施草稿审查中
NXS-STD-DC-000017上线就绪度草稿审查中
NXS-STD-DC-000018智能体指南草稿审查中
NXS-STD-DC-000019站点页面:管理、国家采用与开放边界草稿审查中
NXS-STD-DC-000020站点页面:法律声明草稿审查中
NXS-STD-RS-000006来自已准入官方数据源的数据更新(自动生成)草稿审查中
NXS-STD-SW-000011数据源导出导入器草稿审查中
NXS-STD-PC-000004提案:上下文代码分配规则及领域代码 CMP、DTW、SNS、PNT草稿审查中
NXS-STD-DS-000004Nexus Risk Standards catalogue草稿审查中
NXS-STD-SW-000012Nexus 风险标准文档生成器草稿审查中
NXS-STD-DC-000021Nexus 风险标准:系统性架构草稿审查中
NXS-STD-PC-000005提案:Nexus Risk Standards 系统性目录草稿审查中
NXS-STD-DS-000005Nexus-native risk taxonomy: the full risk spectrum草稿审查中
NXS-STD-SW-000013机器导出生成器:本体、分类体系、形状、JSON-LD、OSCAL、ODRL草稿审查中
NXS-STD-SW-000014发布清单、签名与零信任验证草稿审查中
NXS-STD-SW-000015只读标准查询层草稿审查中
NXS-STD-SW-000016智能体接口(Model Context Protocol 服务器)草稿审查中
NXS-STD-SW-000017标准 HTTP 服务器草稿审查中
NXS-STD-SW-000018Nexus Standards 一键式 CLI草稿审查中
NXS-STD-PC-000006提案:全谱系补全、风险分类体系和 AI 原生标准基础设施草稿审查中
NXS-STD-DC-000022快速入门:用一条命令使用 Nexus Standards草稿审查中
NXS-STD-DS-000006Nexus 原生登记册草稿审查中
NXS-STD-DS-000007Nexus 协调统一登记册草稿审查中
NXS-STD-DS-000008Nexus Risk Standards 目录来源草稿审查中
NXS-STD-SW-000020本地权威信息提取器草稿审查中
NXS-STD-SW-000021风险标准目录与分类体系生成器草稿审查中
NXS-STD-PC-000007Nexus 风险标准的原生融合草稿审查中
NXS-STD-DS-000009参与登记册:启动、节奏、工作组、专家社群和门户草稿审查中
NXS-STD-SW-000022会议节奏库(理事会、委员会和工作组会议)草稿审查中
NXS-STD-DC-000023参与 页面草稿审查中
NXS-STD-PC-000008参与、节奏与关口草稿审查中
NXS-STD-DC-000024参与、节奏与关口(运营手册)草稿审查中
NXS-STD-DS-000010Nexus-native risk vocabulary and risk classes草稿审查中
NXS-STD-DS-000011产业、产业组和拟议的部门代码草稿审查中
NXS-STD-DS-000012映射到各领域和 NHS-1 危害领域的学科草稿审查中
NXS-STD-PC-000009风险地图集 1.1:NHS-1 1.1.0、风险词表、行业、部门和法域草稿审查中
NXS-STD-DC-000025风险图集、词汇与分类(指南)草稿审查中
NXS-STD-DC-000026对 Nexus Standards 的专家审核以及使其达到世界一流水平的计划草稿审查中
NXS-STD-DC-000027参考文献与对既有工作的致谢草稿审查中
NXS-STD-PO-000001关于信息危害和军民两用内容的政策草稿审查中
NXS-STD-DC-000028Nexus Standards 的维护:系统审查、版本管理、勘误、稳定化和撤销草稿审查中
NXS-STD-DS-000013规范性要求登记册草稿审查中
NXS-STD-TN-000001NHS-2 模型规范:种类、数量、关系、证据和来源草稿审查中
NXS-STD-DC-000029新工作项目 NRS-C17 至 NRS-C24:范围与理由草稿审查中
NXS-STD-PC-000010新的核心风险标准 NRS-C17 至 NRS-C24草稿审查中
NXS-STD-DC-000030工作流 W1 至 W8 的职权范围草稿审查中
NXS-STD-DC-000031向专家社群、理事会和联络组织发出的邀请草稿审查中
NXS-STD-PO-000002无障碍与语言政策草稿审查中
NXS-STD-DC-000032合格评定方案(首份拟议草案)草稿审查中
NXS-STD-DC-000033Programme cover note of the Secretariat草稿审查中
NXS-STD-DS-000014信息危害筛查登记册草稿审查中
NXS-STD-DS-000015供技术审查和评议的分发,以及技术审查领域草稿审查中
NXS-STD-DC-000034供技术审查和评论的传阅通知草稿审查中
NXS-STD-SW-000023传阅通知与技术审查生成器草稿审查中
NXS-STD-SW-000024Nexus Standards repository check (open boundary, links and paths, syntax, information-hazard screen, proposals)草稿审查中
NXS-STD-DC-000035Release policy of the open repository and the content of each release草稿审查中
NXS-STD-RS-000007Roadmap of the Nexus Standards to the first official release (target 2030)草稿审查中
NXS-STD-DC-000036Roadmap to 2030 and invitation to all stakeholders草稿审查中
09常见问题

问答。

UNI 是品牌或产品名称吗?
不是。UNI 是一种目录代码,性质上类似于 DOI 或 ISBN。它不带任何商标主张,也不作为产品名称呈现。
UNI 可以手工分配吗?
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.
标准

参与标准工作。

邀请政府、监管机构、标准机构、行业、学术界和社区在首个正式版本(目标为 2030 年)发布前共同完善该目录:对草案提出意见、提出变更建议、加入工作组或承办实地演练。

状态与用途。Nexus Standards 是根据 NS-13 通过公开流程制定、供自愿使用而发布的提议标准;它们不构成认证、认可或监管批准,采用与否仍由全球标准委员会以及各国的国家标准委员会决定。UNI(唯一 Nexus 标识符)用于识别制品,不对其进行认证。标准机构及其标准的名称归其管理者所有,仅用于识别相关文件;此处不转载任何外部标准的文本。Nexus Standards 与此处提及的任何标准机构均无隶属关系,也未获其认可或认证。

许可:标准文本、登记册、模式和数据采用 CC BY 4.0;参考代码采用 Apache-2.0。外部标准按名称、编号和链接引用,并适用其各自许可。第三方数据、库和字体保留其各自许可:见第三方声明。