- 代码
NS-1- 标题
- UNI 和制品目录(语法 v0.2:领域、部门、区域和环境段)
- 版本
- 0.1.0
- 状态
- 拟议
- 日期
- catalogue 2026-10-15 · circulated 17 October 2026
- Unique Nexus Identifier
NXS-STD-ST-000001- 职责范围
- 信任
- 来源
standards/NS-1-identifier-and-artifact-catalog.mdat2cbe0d41b5f8
Preparatory working draft, circulated for review and comment. Not for implementation. Prepared and circulated by Saeed Valadbaygi, Chief Steward, Nexus Standards (saeed@therisk.global), 17 October 2026. Technical review area: TR-02. This document is not a Nexus Standard; it may change without notice and is not to be implemented, relied upon or cited as a Nexus Standard. Its stage is designated only by the Global Standards Council and its technical committees under NS-13. Recipients are invited to submit comments with supporting reasons, and to notify any patent rights of which they are aware. See the notice of circulation.
- 状态
- 拟议
- 负责人
- the trust and assurance system (trust, authorisation, policy and assurance;
NXS-S13) - 签发架构
- UNI identifier fabric
- 规范主页
- this repository
- 机器登记册
registry/nexus-standards.yaml- Record schema
schemas/nexus-artifact-record.v1.json- STD catalogue
catalog/artifact-catalog.yaml- 参考 CLI
node tools/nexus-id.mjs- 消费方实现
registry/consumers.yaml
NS-1 gives every artefact the ecosystem produces one stable, machine-readable identifier, the UNI (Unique Nexus Identifier), and one catalogue record that says what the artefact is, who made it, who publishes it, what rights apply and where it lives. Code, services, schemas, datasets, models, reports, articles, figures, maps, lessons, policies and standards all follow the same scheme, so any agent, developer, researcher, machine or expert reader can find and cite an artefact the same way across all systems, rooms, runtimes, organisations and sites.
the trust and assurance system owns and versions the Nexus Standards. Every other system, site engine, editorial surface and agent applies them and never forks them. A UNI identifies and resolves; it never certifies truth, readiness or authority (V3 directive, section 12).
引用
NS-1, clause 0. NXS-STD-ST-000001@0.1.0. https://nexustandards.com/standards/ns-1/#nx-c-00. 标准的所在位置
This repository is the canonical home of the Nexus Standards: the documents under standards/, the machine registry under registry/,即位于以下路径下的记录模式 schemas/, the STD-scope catalogue under catalog/ and the reference CLI under tools/. Consuming repositories (nexus-foundry, the WordPress plugin, institutional sites) implement the standard, keep their own catalogues for their own scopes, and never fork the registry; registry/consumers.yaml 列出它们及其状态。写作如下形式的路径 server/..., src/... 或 scripts/... in this document are paths inside the nexus-foundry consumer.
引用
NS-1, clause 1. NXS-STD-ST-000001@0.1.0. https://nexustandards.com/standards/ns-1/#nx-c-11. UNI
语法版本 0.2(情境段于 2026-10-16 加入;所有 v0.1 标识符均未改变,仍然有效)。
NXS-<SCOPE>-<CAT>[-<DOMAIN>][-<SECTOR>][-<REGION>][-<ENV>]-<SERIAL>[@<VERSION>] NXS-EWS-DS-000042 dataset 42 of the early-warning system NXS-EWS-DS-KEN-000003 a Kenyan early-warning dataset NXS-GRX-RP-M002-000007@1.2.0 report 7 of the data system for Africa, version 1.2.0 NXS-GRX-AR-WAT-CAN-000012 article 12 of the data system on water in Canada NXS-GRX-DP-WAT-WUT-CAN-PRD-000001 production deployment 1 of the data system for Canadian water utilities (NS-9) NXS-GCR-AR-000015 an article published by GCRI Canada NXS-STD-ST-000001 this standard| 段 | 形式 | 含义 |
|---|---|---|
NXS | 固定 | 前缀。选择它而非 NEX 因为它读起来像代码,而不是单词; NEX- 已被众多品牌(Nexo、Nexi、Nexor)占用,并且 NXS 已是以下位置的中性系统前缀 public-identity.json |
| SCOPE | 三个字母 | 一个规范系统(EWS, EOP, SIG, GRX, OPS……)、组织(GCR, GRF, GRA, NXO)或跨领域范围(STD, LEG, GOV, PRG) |
| CAT | 两个字母 | Artefact category, mapped to Zenodo upload and publication types and to DataCite resource types; or an NXS-GRX (canonical data, provenance and risk) record kind (OB, SR, IN, ME, BD, CT, CR, AP, SU,NS-3)。两份列表绝不共用同一代码 |
| DOMAIN | 可选,三个字母 | Nexus 领域代码,来自 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(KEN, CAN)或联合国 M49 区域,形式为 M + 三位数字(M002 非洲, M142 亚洲);登记册 registry/regions.yaml |
| ENV | 可选,三个字母 | PRD 生产, STG 预发布, LBX 实验室, FIX 固定样例;供情境记录使用(NS-9) |
| SERIAL | 六位数字 | Allocated by the catalogue or the UNI fabric per full prefix (SCOPE + CAT + context segments), never reused |
| VERSION | 可选 | Semantic version of an artefact (1.2.0)或整数 recordVersion NXS-GRX 记录的(3,NS-3)。不带版本的 UNI 指称概念 |
情境段。 四个可选段始终按 DOMAIN、SECTOR、REGION、ENV 的顺序出现;每个均为来自其登记册的三字母代码,各登记册两两互不相交,且与范围代码及 M49 形式不相交(由…检查 tools/nexus-id.mjs catalog validate),因此标识符无需分隔符即可被确定性地解析。不含 CAT 和 SERIAL 的标识符即为 情境名称, NXS-GRX-WAT-CAN:数据系统、水领域、加拿大。情境名称是有关该情境的文章、页面、数据集、部署、仪表板和代码所采用的名称(NS-16);它们的 UNI 仅在 CAT 和 SERIAL 上有所不同。情境名称从不分配,也从不带序列号;NS-9 情境记录(DP 或 PR)是情境的权威记录。
机器形式:URN urn:nexus:uni:NXS-EWS-DS-000042;解析器路径 /uni/NXS-EWS-DS-000042 (为浏览器提供 HTML 落地页,为机器提供 JSON, /uni/<uni>.json 始终为 JSON; /uni 列出已发布记录);情境路径 /ctx/NXS-GRX-WAT-CAN (该情境的每条已发布记录);字段名 uni ,适用于每条记录、每个 API、每个模式和每张表。
现有的点分标识符(grix.eo.stac.catalogue)为 UNI v0。它们被记录为 legacyUni ,置于新记录中以供对照,且永不再次分配。
引用
NS-1, clause 1.1. NXS-STD-ST-000001@0.1.0. https://nexustandards.com/standards/ns-1/#nx-c-1-11.1 情境代码分配
提议 NXS-STD-PC-000004 引入本节,状态为开放(OPEN);这些规则适用于此后分配的每一个代码。机器形式: registry/nexus-standards.yaml identifier.codeAllocation。校验: node tools/nexus-id.mjs catalog validate.
范围、领域、部门或环境代码是供机器解析、人们无需阅读的三字母分类。分配规则的存在是为了确保任何代码都不会产生歧义,包括在其他代码表日后发生变化之后。
| 规则 | 文本 |
|---|---|
| CA-1 | 三个大写字母 A–Z。不含数字,且绝不是 M 加三位数字形式的 UN M49。 |
| CA-2 | 在所有登记册中唯一:范围、领域、部门、环境以及 ISO 3166-1 alpha-3。 |
| CA-3 | 绝不是下列任何一项,均列于 registry/regions.yaml, so 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-4 | 英文标签的助记符:标签核心词的首字母,后接使代码仍可辨识的辅音字母。 |
| CA-5 | 绝不能是产品名称、标志、公司名称或股票代码,也绝不能是读起来像品牌的词。 |
| CA-6 | 每个代码一个概念。每个代码都有定义、包含和排除的内容,以及其对照的外部标准。 |
| CA-7 | 标识符为稳定的小写连字符英文。标签采用句首大写。两者均不编码状态。 |
| CA-8 | 仅可追加。代码绝不会被重新分配或删除。已停用的代码保留其条目,并带有 deprecated: true 和 supersededBy. |
| CA-9 | 新代码保持 PROPOSED,及其提案 UNI,直至全球标准理事会通过登记册变更。使用方可以使用 PROPOSED identifier but must show its status. |
| CA-10 | 新增代码属于次要的、增量式登记册版本。更改代码的含义属于重大变更,需要对照。 |
沿用条款: AAP,即预期行动系统的系统范围。它在 CA-3 之前分配,位于用户自定义范围之内 AAA–AAZ。依据 CA-8,它予以保留。
依据这些规则拟议的技术领域:
| 代码 | ID | 标签 | 对照至 |
|---|---|---|---|
CMP | compute | 计算与加速基础设施 | ISO/IEC JTC 1/SC 38 和 SC 39;ISO/IEC 22123 |
DTW | digital-twins | 数字孪生与仿真 | ISO/IEC 30173:2023; ISO/IEC JTC 1/SC 41; ISO 23247 |
SNS | sensing | 传感与测量网络 | OGC SensorThings API 与 SensorML;W3C/OGC SOSA/SSN;IEEE 1451 |
PNT | pnt | 定位、导航与授时 | IEEE 1588;ITU-T G.8271 和 G.8272;ITU-R TF 系列;UN ICG |
感知与定位-导航-授时是两个独立的代码,因为不同的社区对其进行标准化:一方面是传感器和观测编码,另一方面是授时和 GNSS 概况。涵盖两者的技术流带有 SNS 以及列表 PNT 视为相关。
未来的量子技术代码不能是 QTM 或 QNT,因为两者都落在用户自行分配的范围内 QMA–QZZ。CA-3 在分配之前即可发现此类冲突。
引用
NS-1, clause 2. NXS-STD-ST-000001@0.1.0. https://nexustandards.com/standards/ns-1/#nx-c-22. Scope codes
| 系统 | 代码 | 系统 | 代码 | |
|---|---|---|---|---|
| nexus(立场,执行综述) | CMD | sig(信号、授时、PNT) | SIG | |
| northstar (common operating picture) | NST | nsf (trust, authorisation) | 信任与保证系统 | |
| dss (decisions) | DSS | hub (knowledge, records) | HUB | |
| nexcore (compute, runtimes) | COR | studio (composition, workflows) | STU | |
| nexq(软件包、模型、能力) | NXQ | factory(构建、签名) | FAC | |
| grix(数据、来源追溯、风险) | GRX | apps(应用生命周期) | APP | |
| eop(地球观测) | EOP | 渠道(协议、规约) | RLS | |
| ews(早期预警) | EWS | 门户(公众、客户、合作伙伴交付) | POR | |
| aap (anticipatory action) | AAP | 实验室 (研究、模拟) | LAB | |
| net(网络连续性) | NET | |||
| 运行(仪器、校准) | OPS |
Organisations: GCR 全球风险与创新中心(Global Centre for Risk and Innovation,GCRI Canada) · GRF The Global Risks Forum · GRA The Global Risks Alliance · NXO 联合体 · ELP 和 OBS 保留的组织范围(使用前撤回;可解析,但从不签发)。跨领域: STD 标准 · LEG 法律与知识产权 · GOV 治理 · PRG programme · UXK UI/UX 工具包 · ALL ecosystem-wide.
范围代码是分类,不是名称。公开标签遵循名称架构标准(nexus-foundry the network's own records); the trust and assurance system 作为代码可以,但“信任与保证体系”作为公开产品名称则不可以。规范的 systemId 和 neutralId stay unchanged.
引用
NS-1, clause 3. NXS-STD-ST-000001@0.1.0. https://nexustandards.com/standards/ns-1/#nx-c-33. Category codes
| 代码 | Artefact | Zenodo | DataCite |
|---|---|---|---|
| SW | 软件 | software | 软件 |
| SV | 服务或 API | software | 服务 |
| SC | 模式或契约 | 其他 | 其他 |
| MG | 数据库迁移 | software | 软件 |
| WF | 工作流 | workflow | 工作流 |
| MD | 建模 | 模型 | 建模 |
| DS | 数据集 | 数据集 | 数据集 |
| EV | 证据记录 | 数据集 | 数据集 |
| AR | 条 | publication / article | JournalArticle |
| PP | 预印本 | publication / preprint | 预印本 |
| RP | 报告 | publication / report | 报告 |
| TN | 技术说明 | publication / technicalnote | 文本 |
| DC | 文档 | publication / softwaredocumentation | 文本 |
| DL | 交付成果 | publication / deliverable | 报告 |
| WP | 工作论文 | publication / | 文本 |
| BK | 图书或章节 | publication / book | 书籍 |
| CP | 会议论文 | publication / conferencepaper | ConferencePaper |
| TH | 论点 | publication / thesis | 学位论文 |
| PT | 专利 | publication / patent | 其他 |
| ST | 标准 | publication / other | 标准 |
| PC | 政策或指令 | publication / other | 文本 |
| PS | 演示文稿 | 演示文稿 | 文本 |
| PO | 海报 | 海报 | 文本 |
| FG | 图 | image / figure | 图像 |
| PL | Plot or visualisation | image / plot | 图像 |
| DG | 图示 | image / diagram | 图像 |
| PH | 照片 | image / photo | 图像 |
| MP | 地图产品 | image / other | 图像 |
| VD | 视频 | 视频 | 视听作品 |
| LS | 课程或课堂 | 课时 | InteractiveResource |
| PY | 实物对象 | physicalobject | PhysicalObject |
| PA | 参与记录 | 其他 | 其他 |
| RS | 计划状态记录 | 其他 | 其他 |
| OT | 其他 | 其他 | 其他 |
node tools/nexus-id.mjs export <uni> --format zenodo 生成 Zenodo 存缴元数据; --format datacite produces a DataCite-shaped record, so a catalogued artefact can be deposited or minted a DOI without re-describing it.
引用
NS-1, clause 3.1. NXS-STD-ST-000001@0.1.0. https://nexustandards.com/standards/ns-1/#nx-c-3-13.1 公共 Registry 对照
登记册地址: therisk.global/nexus-registry/ (出版方 GCRI Canada)显示记录编号 NX-R-nnnnn (计划状态), NX-P-nnnnn (publication), NX-E-nnnnn (evidence) and NX-C-nnnnn (参与)带有版本、哈希值和状态。这些形式成为 UNI 的 显示别名 : NX-R-47092 → NXS-GCR-RS-047092, NX-P → RP (或在记录注明时为 AR、PP、WP), NX-E → EV, NX-C → PA。登记册版本变为 currentVersion,即哈希值 versions[].digest,国家 registryState (REGISTERED, CORRECTION_OPEN, RIGHTS_HOLD, WITHDRAWN). The page says no public record has been released yet, so nothing live breaks. Full rule: registry/nexus-standards.yaml#registryCrosswalk.
引用
NS-1, clause 4. NXS-STD-ST-000001@0.1.0. https://nexustandards.com/standards/ns-1/#nx-c-44. The record
Each UNI has one record in the catalogue (schema: nexus-artifact-record.v1.json). Required: uni, title, scope, category, status, creators, publisherRef, publicationDate, rights, legalState, claimCeiling, locations. Optional: region, systemId, legacyUni, description, keywords, language, currentVersion, versions (with git SHA and sha256 digest), relatedIdentifiers (DataCite 关系类型,因此各部分、衍生、取代和引用关系构成一张图谱), supersededBy, workPackageId, directiveRefs.
保证领域: legalState 默认为 LEGAL_REVIEW_REQUIRED; claimCeiling 绝不超过索赔登记册(FIXTURE_VERIFIED, IMPLEMENTATION_COMPLETE, INTEGRATED, LAB_OBSERVED); publisherRef is the institution for institutional artefacts (the institution stays publisher of record; ownership of the technology does not make its owner the publisher).
引用
NS-1, clause 5. NXS-STD-ST-000001@0.1.0. https://nexustandards.com/standards/ns-1/#nx-c-55. 规则
| 规则 | 文本 |
|---|---|
NS1-R1 | One UNI per artefact concept; versions share the UNI and differ in @VERSION |
NS1-R2 | UNIs are allocated only through the catalogue (mint);绝不手工输入 |
NS1-R3 | UNIs are never deleted or reused. Withdrawn artefacts keep their record (WITHDRAWN);被取代者记录 supersededBy |
NS1-R4 | 每条记录均带有所需的元数据; legalState 默认为需审查; claimCeiling 保留在主张登记册之内 |
NS1-R5 | The UNI is embedded in the artefact itself so machines and people can find the record (section 6) |
NS1-R6 | Regional artefacts carry REGION; public regional or national use still follows the name architecture's geographic rules |
NS1-R7 | 代码是分类,绝非产品名称 |
NS1-R8 | 新的范围、领域、行业和环境代码须满足分配规则 CA-1 至 CA-10(第 1.1 节),并通过 NS-13 提案进入 |
NS1-R9 | 代码绝不重新分配或删除;已退役的代码将被弃用,并附带 supersededBy,使用它的标识符仍然有效 |
NS1-R10 | A PROPOSED identifier may be used and is shown with its status until the registry change is adopted |
引用
NS-1, clause 6. NXS-STD-ST-000001@0.1.0. https://nexustandards.com/standards/ns-1/#nx-c-66. 嵌入:各界面如何承载 UNI
| 地表 | 负责人 | 如何 |
|---|---|---|
| 源文件 | 信任与保证系统 | 标题注释 Nexus-UNI: <uni> |
| 文件和报告 | HUB | 前言 uni: 或第一道防线 Nexus-UNI: <uni> |
| 数据集和产品 | GRX | Sidecar <file>.uni.json 与记录一并,或一项 uni STAC 和 DataCite 元数据中的键 |
| 图表与地图 | EOP | Caption suffix [<uni>] 以及图像元数据 |
| Foundry HTTP APIs | 信任与保证系统 | 响应头 X-Nexus-UNI: <uni> 在每个正文携带一个 uni (server/middleware/uniHeader.ts); GET /api/uni/catalog, GET /api/uni/:uni, GET /api/uni/:uni/export?format=zenodo|datacite|schema-org|codemeta|citation-cff|stac|dcat|prov under the trust and assurance system scope; public GET /uni/:uni 适用于带有 Schema.org JSON-LD 的已发布(PUBLISHED)非受限记录 |
| 房间与面板 | STU | 房间绑定投射有效载荷 uni (或 uniKey) per source and shows it as a link; any cell that is a UNI links to /uni/<uni>; the trust and assurance system room's Standards surface reads the catalogue (ns6StandardsRoomDefinitions.ts) |
| Passports | GRX | PASSPORT_UNI_FIELD (nexus:uni) is the first field of the shared Identity section; format uni links valid UNIs to /uni/<uni> and shows legacy dotted ids unlinked; the account passport links its registered UNI |
| 落地页与信任页 | POR | <meta name="nexus-uni" content="<uni>"> 和 data-nexus-uni 位于组件根目录 |
| WordPress plugin and institutional sites | POR | 帖子元数据 _nexus_uni (validated; uni 在来源追溯 REST 正文中), <meta name="nexus-uni"> 和 X-Nexus-UNI are wired in the plugin (the network's own records); 区块属性 nexusUni follows in NS-6. See nexus-foundry the network's own records |
| 智能体 | 信任与保证系统 | Mint through the CLI and embed the UNI in every artefact produced |
各界面均位于 registry/nexus-standards.yaml#surfaces 具有状态。未声明嵌入方式的界面不合规; PLANNED 表示该钩子已完成规范但尚未接通。NS-6 已接通 API 标头和路由、房间和通行证;落地页元标签和 JSON-LD 将随解析页面(NS-7)一并推出。
引用
NS-1, clause 7. NXS-STD-ST-000001@0.1.0. https://nexustandards.com/standards/ns-1/#nx-c-77. 命令
node tools/nexus-id.mjs validate NXS-EWS-DS-000042 node tools/nexus-id.mjs parse NXS-GRX-RP-M002-000007@1.2.0 node tools/nexus-id.mjs next --scope EWS --category DS --region KEN node tools/nexus-id.mjs mint --scope EWS --category DS --title "Kenya flood observations 2026" \ --path the approved sources of the network --region KEN --publisher GCRI_CANADA --work-package RF-21 node tools/nexus-id.mjs catalog validate # npm run validate node tools/nexus-id.mjs catalog list --scope GRX node tools/nexus-id.mjs export NXS-STD-ST-000001 --format zenodo引用
NS-1, clause 8. NXS-STD-ST-000001@0.1.0. https://nexustandards.com/standards/ns-1/#nx-c-88. 开放标准栈
registry/open-standards-stack.yaml 确定 UNI. the network's own records crosswalks a record to Zenodo deposition metadata, DataCite 4.5, Schema.org JSON-LD (for landing pages and Google Dataset Search), CodeMeta 3.0 and CITATION.cff; zenodoClient.ts deposits to Zenodo (sandbox by default, dry-run by default, token supplied by the publishing institution) after the legal gate zenodoDepositEligibility (APPROVED, open or embargoed, SPDX licence). The returned DOI is written back as relatedIdentifiers[IsIdenticalTo, DOI], so the UNI stays the key and the DOI is the citable crosswalk. Zenodo is registered in the network's legal texts#zenodo 和 external-apis.yaml#zenodo.deposit at LEGAL_REVIEW_REQUIRED.
Runtime hooks (NS-6): room-binding sources accept uniKey, every RoomSourceProjection carries uni 房间视图将其链接;护照载明 PASSPORT_UNI_FIELD 在共享的“身份”部分中,并附格式说明 uni; every JSON API response with a uni carries X-Nexus-UNI; /api/uni serves the catalogue and exports. The Global Risks Index (NXS-GRX) recordUni adopts the NS-1 grammar for new records with dotted ids kept as legacyUni (NS-3).
引用
NS-1, clause 9. NXS-STD-ST-000001@0.1.0. https://nexustandards.com/standards/ns-1/#nx-c-99. Relationship to the other standards
- 名称架构 (
the network's own records):公开显示名称和商标安全。NS-1 是其下的机器层;二者绝不矛盾,因为代码从不是名称。 - Claim registry (
the network's own records):claimCeiling在每条记录上。 - 法律登记册 (
the network's legal texts/**):legalState,publisherRef,rights.license. - UNI identifier fabric (V3 directive section 12): artefacts are allocated by the catalogue file (reconstructable source, served by
/api/uni和/uni); NXS-GRX 记录由 PostgreSQL 分配nexus_uni(NS-3,the network's own records). - Work items: every work item lists the UNIs it creates or changes in
evidenceOutputs.
引用
NS-1, clause 10. NXS-STD-ST-000001@0.1.0. https://nexustandards.com/standards/ns-1/#nx-c-1010. Follow-on packages
Delivered: NS-3 NXS-GRX record UNIs (allocation, grammar, crosswalk; WDI bootstrap in use), NS-3b STAC, DCAT and PROV-O profile (the network's own records),NS-6 界面接线,NS-7 解析器着陆页。待定:NS-2 引用和署名格式 · 各路径对记录分配器的采用(realDataObservationIngest,开放数据摄取)· NS-4 文档模板,含 uni front matter · NS-5 figure, map and visualisation standard (with the UI/UX kit) · NS-7b SPA landing-page meta tags and sitemap · NS-8 Zenodo publishing workflow with legal gate, DOI write-back and Software Heritage archival.
变更历史
Versions from the catalogue; entries from the changelog that name this document.
| 版本 | 日期 | 备注 |
|---|---|---|
0.1.0 | 15 October 2026 | current version in the catalogue |
- 未发布的 NS-13 提案
NXS-STD-PC-000004(开放中;最后一轮征集于 2026-11-16 截止),首个提案作为记录保存在proposals/and checked bynpm run validate: NS-1 section 1.1 sets context code allocation rules CA-1 to CA-10 and rules NS1-R8 to NS1-R10. ISO 3166-1 reserved and user-assigned code elements and ICAO Doc 9303 codes are now refused.AAP属于沿用既有规定。它提出四个技术领域代码:CMP算力和加速基础设施,DTWdigital twins and simulation,SNS传感与测量网络,以及PNT定位、导航和授时。领域登记册升级为 schemaVersion 1.1.0(次要版本,增量式)。 - 0.1.0 – 2026-10-16 NS-1 (the UNI and the artefact catalogue), NS-3 (NXS-GRX record UNIs) and NS-3b (STAC, DCAT, PROV-O profile) as PROPOSED documents under
standards/.