- 코드
NS-4- 제목
- Nexus Standards 및 문서의 구조와 작성(v0.2: 조항 구조, 서술 형식, 등록된 요구사항, 문서 서두 정보)
- 버전
- 0.2.0
- 상태
- 제안됨
- Date
- catalogue 2026-10-16 · circulated 17 October 2026
- Unique Nexus Identifier
NXS-STD-ST-000010- 책임 범위
- 지식
- 출처
standards/NS-4-document-template.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-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 (working draft of the revision; on adoption it supersedes the 0.1 document template) |
| 상태 | PROPOSED · Proposal NXS-STD-PC-000010 |
| Prepared and circulated by | Saeed Valadbaygi, Chief Steward, Nexus Standards (saeed@therisk.global), 17 October 2026 |
| 단계 | 검토 및 의견 수렴을 위해 배포된 예비 작업 초안입니다. 이행용이 아닙니다. 단계 지정은 Global Standards Council(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-forewordForeword
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소개
A standard is useful to the degree that two independent parties, reading it, reach the same judgement about whether a thing conforms. Four drafting disciplines serve that end:
- 독자가 어디를 봐야 할지 알 수 있도록 고정된 구조;
- 독자가 무엇이 요구되는지 알 수 있도록 하는 의무 표현의 통제 어휘,
- atomic requirements, so each can be tested on its own;
- 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-11. 범위
1.1 This document specifies:
인용
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;
- the rules for writing requirements and for registering them;
- the front matter and structure of other documents of the ecosystem (clause 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-21.3 It does not specify the content of any standard, the development process (NS-13), or conformity assessment (NS-14 and 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-22. 인용 규범
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, *Citation and attribution*
- NS-13, *표준 개발 절차*
- NS-14, *적합성 및 대응*
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-33. Terms and definitions
3.1 requirement: an expression in the content of a document conveying objectively verifiable criteria to be fulfilled and from which no deviation is permitted if conformance with the document is to be claimed (after [ISO-D2]).
인용
NS-4, clause 3.1. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-3-13.2 recommendation: an expression conveying that, among several possibilities, one is recommended as particularly suitable, without excluding others.
인용
NS-4, clause 3.2. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-3-23.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-33.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-43.5 적합성 대상: 요구사항이 적용되는 대상의 종류. 예를 들어 기록, 데이터세트, 소프트웨어 릴리스, 조직 또는 프로세스.
인용
NS-4, clause 3.5. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-3-53.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-6automated: by a published executable test;inspection: by examination of an artefact against stated criteria;audit: by examination of records and practice over a period;demonstration: by observed performance.
3.7 normative: content that a claimant must satisfy. informative: content that explains, illustrates or credits, and that a claimant need not satisfy.
인용
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-44. Structure of a standard
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 |
|---|---|---|
| 제목 | normative | 아니요 |
| 서문(상태, 제안, 담당자, 다른 문서와의 관계, 이전 판과의 변경 사항) | informative | 아니요 |
| Introduction (purpose and rationale) | informative | 예 |
| 1 Scope (what the document covers, and what it does not) | normative | 아니요 |
| 2 Normative references | normative | no; states "There are no normative references in this document." when there are none |
| 3 용어와 정의 | normative | no; refers to the Nexus-native risk vocabulary for terms it does not define itself |
| 4 onwards: Requirements, organised by subject | normative | 아니요 |
| Conformance (conformance targets, levels, classes, and how a claim is made) | normative | 아니요 |
| Annexes, each marked normative or informative | either | 예 |
| Bibliography of informative references | informative | 예 |
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-r64.3 NS4-R7. A normative reference shall be cited by identifier and, where a dated edition is intended, by year. The text of an external document shall not be reproduced (NS14-R1).
인용
NS-4, NS4-R7. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r74.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-r84.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-55. 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| 형식 | 표현합니다 | Negative |
|---|---|---|
| shall | a requirement | shall not |
| should | a recommendation | should not |
| may | a permission | need not |
| can | a possibility or capability | cannot |
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-r105.3 5.1항의 형식은 [RFC8174]로 명확히 규정된 [RFC2119]의 키워드에 대응한다. 인터넷 사양으로도 발행되는 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-66. 작성 요건
6.1 NS4-R11. 각 요구사항은 단일해야 한다. 하나의 적합성 대상에 대해 하나의 의무를 명시한다.
인용
NS-4, NS4-R11. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r116.2 NS4-R12. Each requirement shall be identified by a requirement identifier of the form <DOC>-R<n>, where <DOC> 는 문서의 약식 코드입니다(예: NS4, IHP, NRS-C17) 및 <n> is a positive integer. The identifier shall be written in bold at the start of the sentence that contains the requirement. Identifiers are never reused. A withdrawn requirement keeps its identifier with status WITHDRAWN.
인용
NS-4, NS4-R12. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r126.3 NS4-R13. A requirement shall be verifiable. It shall state, or refer to, the criteria by which conformance is judged. Words without a stated criterion, such as "appropriate", "adequate", "sufficient", "timely" and "state-of-the-art", shall not be used as the sole criterion of a requirement.
인용
NS-4, NS4-R13. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r136.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-r146.5 NS4-R15. Notes and examples shall be informative and shall not contain requirements.
인용
NS-4, NS4-R15. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r156.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-77. Register of requirements
7.1 NS4-R16. Every requirement of an adopted or proposed Nexus document shall be recorded in registry/requirements.yaml with the following:
인용
NS-4, NS4-R16. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r16- identifier;
- document UNI;
- clause;
- verbal form;
- 적합성 목표;
- the test method (clause 3.6);
- the reference of the executable test, where the method is
automated; - 상태.
7.2 NS4-R17. A requirement shall have one of the statuses PROPOSED, IN_COMMENT, ADOPTED, SUPERSEDED 또는 WITHDRAWN. The status of a requirement shall not run ahead of the status of its document.
인용
NS-4, NS4-R17. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r177.3 NS4-R18. The validator shall refuse:
인용
NS-4, NS4-R18. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r18- a register entry whose identifier does not appear in the clause it cites;
- a document requirement identifier that is not registered;
- an
automatedrequirement without a test reference once the document is in comment.
7.4 The register is the source from which conformance checklists, test suites and the requirement pages of the site are generated.
인용
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-88. Conformance clause
8.1 NS4-R19. The conformance clause shall state:
인용
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 requirements each level or class comprises;
- 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;
- the level or class claimed;
- the evidence quality level (EQL) of the supporting evidence;
- 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-99. 기타 문서의 서두와 구조
9.1 NS4-R1. Front matter, or the first-line UNI, shall be present in every document. The record shall be minted before the document is shared.
인용
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 Documents other than standards follow this structure:
인용
NS-4, clause 9.2. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-9-2- Summary: what the document is, for whom, its supported claim level and its legal state, in one paragraph.
- Scope and definitions.
- Body.
- Evidence and provenance: datasets, records, models and runs, cited by UNI (NS-2).
- 한계.
- 적합성: 주장하는 표준과 조항(NS-14).
- 참고문헌.
- Change log.
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-r29.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-r39.5 NS4-R4. Versions shall be semantic in accordance with the maintenance procedure (NXS-STD-DC-000028). A changed number or conclusion is a new version with a change-log line and digest.
인용
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-1010. Language and style
10.1 NS4-R21. 표준은 평이하고 비인칭적이며 정확한 언어로 작성되어야 한다. 요구사항을 기술하는 각 문장은 하나의 개념만 담아야 한다.
인용
NS-4, NS4-R21. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r2110.2 NS4-R22. Abbreviations shall be expanded at first use in each document.
인용
NS-4, NS4-R22. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r2210.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-r2310.4 NS4-R24. The English text is the reference text. Translations follow the policy on accessibility and languages (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-1111. 적합성
11.1 The conformance target of this document is a document of the categories listed in 1.2.
인용
NS-4, clause 11.1. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-11-111.2 A document conforms to NS-4 when it satisfies NS4-R1 to NS4-R24 as they apply to its category. Requirements NS4-R5 to NS4-R20 apply to standards, policies, technical notes and proposals. Requirements NS4-R1 to NS4-R4 and NS4-R21 to NS4-R24 apply to every document.
인용
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-aAnnex A (informative): changes from version 0.1
| Version 0.1 | Version 0.2 |
|---|---|
| NS4-R1 to NS4-R4 (front matter, citation of numbers, limitations, semantic versions) | Retained with the same identifiers in clause 9 |
| No structure for standards | Clause 4 |
| 동사형 없음 | 제5조 |
| 표 안의 규칙 | Atomic, identified, verifiable requirements (clause 6) |
| 등록부 없음 | 제7조 |
| No conformance clause rule | Clause 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.
| 버전 | Date | 비고 |
|---|---|---|
0.1.0 | 2026년 10월 16일 | current version in the catalogue |
- 미발표 NS-13 제안
NXS-STD-PC-000010(OPEN, 정책), 수석 관리 주체 Saeed Valadbaygi 제안: 첫 번째 작업 프로그램.governance/programme/: 참고문헌(NXS-STD-DC-000027); 정보 재해(information hazards) 및 이중 용도 콘텐츠에 관한 정책 (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, 조항, 정책, 증명 및 제안 스키마.