Skip to content
标准NS-4拟议
NS-4

NS-4:Nexus Standards 及文件的结构与起草(v0.2

NS-4 is a proposed Nexus Standard; the artefacts it governs are identified by UNIs (Unique Nexus Identifier). NS-4 is proposed: PROPOSED.

NS-4 in the catalogue
The standards NS-4 depends on and those that cite it, then its sections with one mark for each numbered requirement.Source: NS-4-document-template.md; the Nexus Standards registry.
  • NS-4 depends on: NS-0, NS-1, NS-2, NS-5, NS-7, NS-13, NS-14.
  • NS-4 被以下引用:NS-0、NS-1、NS-16。
  • Section 1, Foreword: no numbered requirement.
  • 第 2 节,引言:无编号要求。
  • Section 3, Scope: no numbered requirement.
  • 第 4 节,规范性引用文件:无编号要求。
  • Section 5, Terms and definitions: no numbered requirement.
  • 第 6 节,标准的结构:R5、R6、R7、R8。
  • 第 7 节,动词形式:R9、R10。
  • Section 8, Writing requirements: R11, R12, R13, R14, R15.
  • 第 9 节,需求登记册:R16、R17、R18。
  • Section 10, Conformance clause: R19, R20.
  • Section 11, Front matter and structure of other documents: R1, R2, R3, R4.
  • Section 12, Language and style: R21, R22, R23, R24.
  • Section 13, Conformance: R1, R4, R5, R20, R21, R24.
  • 第 14 节,附件 A(资料性):相对于 0.1 版的变更:R1、R4。
  • 第 15 节,参考文献:无编号要求。
01概览

摘要

NS-4记录
  1. 状态拟议
  2. 职责范围知识
  3. 规则已说明0
  4. 计划领域2
  5. 源文件存储库

Nexus Standards · proposed

要求
24
编号规则
章节
15
在文中
依赖于
7
NS-0, NS-1, NS-2
被引用于
3
Nexus Standards
02标准

NS-4: the standard

NS-4 在规范存储库(提交 2cbe0d41b5f8)中的现行文本:15 个条款、0 个子条款和 24 项已识别要求,每项均附有锚点和引用。

代码
NS-4
标题
Nexus Standards 和文件的结构与起草(v0.2:条款结构、助动词形式、已登记的要求;文件前置信息)
版本
0.2.0
状态
拟议
日期
catalogue 2026-10-16 · circulated 17 October 2026
Unique Nexus Identifier
NXS-STD-ST-000010
职责范围
知识
来源
standards/NS-4-document-template.md at 2cbe0d41b5f8

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

版本0.2.0(修订版工作草案;采纳后将取代 0.1 文件模板)
状态拟议 · 提案 NXS-STD-PC-000010
Prepared and circulated bySaeed Valadbaygi, Chief Steward, Nexus Standards (saeed@therisk.global), 17 October 2026
阶段预备性工作草案,供审阅和征求意见传阅。不得用于实施。阶段认定权保留给全球标准理事会(NS-13)
负责人WG-DEV 与编辑共同负责;委员会 TC-CORE
上级NS-1; process NS-13
要求NS4-R1 至 NS4-R24,登记于 registry/requirements.yaml
引用NS-4, Foreword. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-foreword

前言

This revision turns NS-4 from a document template into the drafting rules of the Nexus Standards. Version 0.1 fixed the front matter that gives a document its identity and provenance, and that front matter is retained unchanged in clause 9.

What 0.1 did not do was say how a standard states a requirement, how a reader distinguishes a requirement from advice, and how a conformance claim can be tested. Mature standards bodies settled these questions long ago [ISO-D2; RFC2119; RFC8174; W3C-P]. This revision adopts their settled practice in the Nexus voice and adds what a machine-readable programme needs: a register in which every requirement can be found, tested and traced.

引用NS-4, Introduction. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-introduction

引言

标准的有用程度,取决于两个独立方阅读后,能否对某事物是否符合标准得出相同判断。四项起草准则服务于这一目的:

  1. 结构固定,使读者知道该看哪里;
  2. a controlled vocabulary of obligation, so the reader knows what is required;
  3. 原子化要求,以便每项都可单独测试;
  4. a stated test, so the judgement does not depend on who makes it.
引用NS-4, clause 1. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-1

1. 范围

1.1 本文件规定:

引用NS-4, clause 1.1. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-1-1
  • the structure of Nexus Standards and of the specifications, policies and technical notes of the programme;
  • the verbal forms that express requirements, recommendations, permissions and possibilities;
  • 编写需求和登记需求的规则;
  • 生态系统中其他文件的前置部分和结构(第 9 条)。

1.2 It applies to every document of categories ST (standard), PO (policy), TN (technical note) and PC (proposal) drafted after its adoption, and to every existing NS document when that document is next revised. Clause 9 applies to documents of categories RP, DC, DL, WP, PP, AR, BK, CP and TH.

引用NS-4, clause 1.2. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-1-2

1.3 本标准不规定任何标准的内容、制定流程(NS-13)或合格评定(NS-14 和 NXS-STD-DC-000032).

引用NS-4, clause 1.3. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-1-3
引用NS-4, clause 2. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-2

2. 规范性引用文件

The following documents are referred to in the text in such a way that some or all of their content constitutes requirements of this document. For dated references only the edition cited applies. For undated references the latest edition applies.

  • NS-1, *Identifier and artefact catalogue*
  • NS-2,*引用与署名*
  • NS-13,*标准制定流程*
  • NS-14, *Conformance and crosswalk*
  • registry/requirements.yaml, *Register of normative requirements* (NXS-STD-DS-000013)
引用NS-4, clause 3. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-3

3. Terms and definitions

3.1 要求:文件内容中的一种表述,传达可客观验证的、须予满足的准则;若要声明符合该文件,则不允许偏离这些准则(参照 [ISO-D2])。

引用NS-4, clause 3.1. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-3-1

3.2 建议:表示在若干可能性中,推荐其中一种为尤其适合,而不排除其他可能。

引用NS-4, clause 3.2. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-3-2

3.3 permission: an expression conveying consent or liberty to do something.

引用NS-4, clause 3.3. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-3-3

3.4 possibility: an expression conveying that something is materially, physically or causally possible.

引用NS-4, clause 3.4. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-3-4

3.5 一致性对象:要求所适用的事物类型,例如记录、数据集、软件发布、组织或流程。

引用NS-4, clause 3.5. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-3-5

3.6 test method: the procedure by which conformance with a requirement is determined. It is one of:

引用NS-4, clause 3.6. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-3-6
  • automated: by a published executable test;
  • inspection:依据既定标准对制品进行检查;
  • audit: by examination of records and practice over a period;
  • demonstration: by observed performance.

3.7 规范性:声明方必须满足的内容。 资料性:用于解释、说明或致谢,声明方无须满足的内容。

引用NS-4, clause 3.7. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-3-7
引用NS-4, clause 4. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-4

4. 标准的结构

4.1 NS4-R5. A Nexus Standard shall contain the following elements in this order. An element marked conditional may be omitted only when it would be empty.

引用NS-4, NS4-R5. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r5
要素类型Conditional
标题规范性否
前言(状态、提案、负责方、与其他文件的关系、相对上一版本的变更)资料性否
引言(目的与依据)资料性是
1 Scope (what the document covers, and what it does not)规范性否
2 规范性引用文件规范性no; states "There are no normative references in this document." when there are none
3 术语和定义规范性no; refers to the Nexus-native risk vocabulary for terms it does not define itself
4 onwards: Requirements, organised by subject规范性否
符合性(符合性目标、级别、类别以及如何提出声明)规范性否
Annexes, each marked normative or informative任一是
Bibliography of informative references资料性是

4.2 NS4-R6. The scope shall be written as statements of fact. It shall not contain requirements.

引用NS-4, NS4-R6. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r6

4.3 NS4-R7. 规范性引用文件应以标识符引用;如指定某一带日期的版本,还应注明年份。不得复制外部文件的文本(NS14-R1)。

引用NS-4, NS4-R7. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r7

4.4 NS4-R8. A term defined in clause 3 shall be defined once, as a substitutable phrase without an article, and shall be used with that meaning throughout the document.

引用NS-4, NS4-R8. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r8

4.5 条款采用阿拉伯数字编号,最多四级(4.2.1.3)。附件以字母编序(附件 A)。

引用NS-4, clause 4.5. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-4-5
引用NS-4, clause 5. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-5

5. Verbal forms

5.1 NS4-R9. 应使用以下动词形式,且仅限于这些含义。

引用NS-4, NS4-R9. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r9
形式ExpressesNegative
应a requirementshall not
应a recommendation不应
可a permission无须
可以a possibility or capability不能

5.2 NS4-R10. The words "must", "required", "mandatory" and "is to" shall not be used to express a requirement. The word "must" may appear only to describe an external constraint, such as a law of nature or a legal duty that the document does not itself create.

引用NS-4, NS4-R10. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r10

5.3 第 5.1 条的各种表述形式对应 [RFC2119] 中的关键词,并依据 [RFC8174] 的澄清理解。同时作为互联网规范发布的 Nexus 文件可以说明这一对应关系。

引用NS-4, clause 5.3. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-5-3
引用NS-4, clause 6. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-6

6. 写作要求

6.1 NS4-R11. 每项要求应具有原子性:针对一个符合性对象只陈述一项义务。

引用NS-4, NS4-R11. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r11

6.2 NS4-R12. 每项要求均应以如下形式的要求标识符加以标识 <DOC>-R<n>,其中 <DOC> 是文档的简短代码(例如 NS4, IHP, NRS-C17)和 <n> 为正整数。标识符应以粗体写在包含该要求的句子开头。标识符绝不重复使用。被撤销的要求保留其标识符,状态为 WITHDRAWN.

引用NS-4, NS4-R12. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r12

6.3 NS4-R13. 要求应可验证。要求应陈述或引用判定符合性的准则。未给出明确准则的词语,例如“适当”“充分”“足够”“及时”和“最先进”,不得作为要求的唯一准则。

引用NS-4, NS4-R13. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r13

6.4 NS4-R14. 取决于某一数量的要求应说明该数量、其单位及容差,并符合该计划一旦通过的计量单位和测量标准(拟议的 NRS-C24)。

引用NS-4, NS4-R14. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r14

6.5 NS4-R15. 注释和示例应为资料性内容,不得包含要求。

引用NS-4, NS4-R15. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r15

6.6 一项要求可以引用另一份文件。对另一份文件中某项要求的引用,须注明其标识符。

引用NS-4, clause 6.6. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-6-6
引用NS-4, clause 7. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-7

7. 要求登记册

7.1 NS4-R16. 已通过或拟议的 Nexus 文件的每项要求均应记录于 registry/requirements.yaml 包括以下内容:

引用NS-4, NS4-R16. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r16
  • identifier;
  • document UNI;
  • 条款;
  • verbal form;
  • the conformance target;
  • 试验方法(第 3.6 条);
  • 可执行测试的引用,即方法所在之处 automated;
  • 状态。

7.2 NS4-R17. A requirement shall have one of the statuses PROPOSED, IN_COMMENT, ADOPTED, SUPERSEDED 或 WITHDRAWN。要求的状态不得先于其文件的状态。

引用NS-4, NS4-R17. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r17

7.3 NS4-R18. 验证器应拒绝:

引用NS-4, NS4-R18. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r18
  • 一个登记册条目,其标识符未出现在其所引用的条款中;
  • a document requirement identifier that is not registered;
  • 一个 automated requirement without a test reference once the document is in comment.

7.4 该登记册是生成合规检查清单、测试套件和本网站各项要求页面的来源。

引用NS-4, clause 7.4. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-7-4
引用NS-4, clause 8. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-8

8. 一致性条款

8.1 NS4-R19. 符合性声明应说明:

引用NS-4, NS4-R19. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r19
  • the conformance targets;
  • 任何符合性等级或类别;
  • 各级别或类别所包含的要求;
  • the form of a conformance claim.

8.2 NS4-R20. A conformance claim shall cite:

引用NS-4, NS4-R20. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r20
  • the document's UNI and version;
  • 所声称的级别或类别;
  • 支持性证据的证据质量等级(EQL);
  • the date of the claim;
  • 作出该声明的一方。

A claim never states or implies certification unless an accredited certification under the conformity assessment scheme supports it.

引用NS-4, clause 9. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-9

9. Front matter and structure of other documents

9.1 NS4-R1. 每份文件均应有扉页信息或首行 UNI。该记录应在文件共享之前生成。

引用NS-4, NS4-R1. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r1
--- uni: NXS-GRX-RP-M002-000007 version: 1.2.0 title: ... creators: [{ name: ..., orcid: ... }] publisherRef: GCRI_CANADA publicationDate: 2026-10-16 legalState: LEGAL_REVIEW_REQUIRED claimCeiling: INTEGRATED derivedFrom: [NXS-GRX-DS-M002-000003@2.0.0] conformsTo: [NS-0, NS-1, NS-2, NS-4] language: en ---

Plain Markdown without front matter starts with Nexus-UNI: <uni> on the first line (NS1-R5). HTML carries <meta name="nexus-uni"> and the Schema.org JSON-LD of the record (NS-7). Word, PDF and slide formats carry the UNI on the title page and in the document properties.

9.2 标准以外的文件遵循以下结构:

引用NS-4, clause 9.2. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-9-2
  1. Summary: what the document is, for whom, its supported claim level and its legal state, in one paragraph.
  2. Scope and definitions.
  3. 正文。
  4. Evidence and provenance: datasets, records, models and runs, cited by UNI (NS-2).
  5. 局限性。
  6. 符合性:所声明的标准和条款(NS-14)。
  7. 参考文献。
  8. 变更日志。

9.3 NS4-R2. Every number, figure and map in a document shall cite its source UNI (NS-2, NS-5).

引用NS-4, NS4-R2. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r2

9.4 NS4-R3. The limitations section shall be present. It shall state the supported claim level and the legal state in plain words.

引用NS-4, NS4-R3. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r3

9.5 NS4-R4. Versions shall be semantic in accordance with the maintenance procedure (NXS-STD-DC-000028)。数字或结论一旦变更,即为新版本,附变更日志条目和摘要。

引用NS-4, NS4-R4. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r4
引用NS-4, clause 10. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-10

10. 语言与风格

10.1 NS4-R21. Standards shall be written in plain, impersonal and precise language. Each sentence shall carry a single idea where a requirement is stated.

引用NS-4, NS4-R21. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r21

10.2 NS4-R22. 缩略语应在每份文件中首次使用时展开。

引用NS-4, NS4-R22. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r22

10.3 NS4-R23. No document shall name, promote or disparage a for-profit company, product or mark, except where a normative reference to a published standard requires it, and then only by the standard's identifier.

引用NS-4, NS4-R23. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r23

10.4 NS4-R24. 英文文本为准。译文遵循无障碍和语言政策(NXS-STD-PO-000002).

引用NS-4, NS4-R24. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r24
引用NS-4, clause 11. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-11

11. 符合性

11.1 本文件的符合性对象是 1.2 中所列类别的文件。

引用NS-4, clause 11.1. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-11-1

11.2 文件在满足其所属类别适用的 NS4-R1 至 NS4-R24 时,即符合 NS-4。NS4-R5 至 NS4-R20 适用于标准、政策、技术说明和提案。NS4-R1 至 NS4-R4 以及 NS4-R21 至 NS4-R24 适用于所有文件。

引用NS-4, clause 11.2. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-11-2
引用NS-4, Annex A. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-annex-a

附录 A(资料性):相对 0.1 版本的变更

Version 0.1版本 0.2
NS4-R1 to NS4-R4 (front matter, citation of numbers, limitations, semantic versions)在第9条中保留相同的标识符
No structure for standards第 4 条
No verbal forms第5条
表格中的规则原子化、可识别、可验证的要求(第 6 条)
无登记册第 7 条
No conformance clause ruleClause 8
引用NS-4, Bibliography. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-bibliography

参考文献

[ISO-D2], [RFC2119], [RFC8174], [W3C-P] in governance/programme/BIBLIOGRAPHY.md.

变更历史

Versions from the catalogue; entries from the changelog that name this document.

版本日期备注
0.1.02026年10月16日current version in the catalogue
  • 未发布的 NS-13 提案 NXS-STD-PC-000010 (OPEN,政策),由首席管理方 Saeed Valadbaygi 提出:首个工作计划。在 governance/programme/:参考文献(NXS-STD-DC-000027);关于信息危害和两用内容的政策(NXS-STD-PO-000001,在理事会作出决定前作为预防措施遵守);维护程序(NXS-STD-DC-000028);NHS-2 模型规范(NXS-STD-TN-000001);新工作项目 NRS-C17 至 NRS-C24(NXS-STD-DC-000029);工作流职权范围(NXS-STD-DC-000030);邀请和渠道(NXS-STD-DC-000031);无障碍与语言政策(NXS-STD-PO-000002);合格评定方案(NXS-STD-DC-000032);附函(NXS-STD-DC-000033)。另:NS-4 0.2 版(结构与起草)。 registry/requirements.yaml (NXS-STD-DS-000013,108 项要求)以及 registry/information-hazard-screen.yaml (NXS-STD-DS-000014),二者均由验证器强制执行。四项定向征集位于 registry/participation.yaml.
  • 0.2.0 – 2026-10-16 已起草 NS-0 章程;NS-2、NS-4、NS-5、NS-9、NS-10、NS-11、NS-12、NS-13、NS-14(PROPOSED)。类别 DP、PR、CL、AT;含 NS-9 背景的记录模式 v1.1;条款、政策、证明和提案模式。
03研究

研究、来源与文件

Recent research on NS-4

与本标准主题相关的近期同行评审文章、预印本、数据集和报告,在阅读时使用由登记册组合的检索词,从开放学术元数据服务(OpenAlex、Crossref、DataCite、Zenodo、arXiv、Europe PMC、OpenAIRE Graph)检索。每项成果均列出其作者、刊载处、年份、类型、开放获取状态和许可,并链接至其 DOI 或落地页。本站尚未启用实时显示的来源仅供参考,不予查询。

Search termsmachine-readable standards; standards development; requirements engineering; SMART standards; normative text; W3C Process Document; UK Government Open Standards Principlescombined with: standard; standards; requirements源自标准的主题及其规则,以及其对照领域的外部标准。

  • OpenAlexlisted for reference; not queried
  • Crossreflisted for reference; not queried
  • DataCitelisted for reference; not queried
  • Zenodolisted for reference; not queried
  • arXiv仅供参考;未查询
  • Europe PMClisted for reference; not queried
  • OpenAIRE Graphlisted for reference; not queried

本网站尚未启用任何来源的实时展示:所列来源仅供参考,均未被查询。待登记出版方在审查其条款后启用某一来源,近期成果将在此列出。仅提供元数据和链接:标题、作者、出版载体、年份、类型、开放获取状态和许可,均按各来源的记录呈现;所列成果仅供了解概况,未经审阅或认可。

04实践中

适用范围及制定方式

其制定方式和参与途径、作为流程的标准,以及列出该标准的计划领域。

NS-4 如何制定,以及如何参与

NS-4 is developed in the open under NS-13 (the stages and gates of NS-13). Working groups draft, councils decide the reserved matters, and anyone may propose a change, comment, submit an implementation report, object or appeal, without membership or fee.

05外部标准

与外部标准的关系

NS-4 通过标识符、条款编号和 URL 与外部标准建立关联(NS14-R1),并引导读者查阅发布机构。

06网络范围内

学习、网络与问题

Risk Academy 课程与学科

1 course and 1 discipline of Risk Academy (risksacademy.com) that teach the knowledge and methods of NS-4. Each course lists its level, stream and learning hours.

课程

学科

课程、学科与 Nexus Standards 之间的对应关系由 Risk Academy 共同维护,并须经其学术审查。

报告贡献

从本页贡献证据。

Reports 是联合体的季度出版物。您对该主题的了解可以在下一期中成为证据、案例或更正,署您的名,并在属于您本人作品的情况下以 CC BY 4.0 发布。

Nexus Standards
标准

参与标准工作。

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

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

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