- Код
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.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 |
| Этап | Preparatory working draft, circulated for review and comment. Not for implementation. Stage designation reserved to the Global Standards Council (NS-13) |
| Владелец | WG-DEV with the editors; committee TC-CORE |
| Родительский элемент | NS-1; process NS-13 |
| Требования | NS4-R1 to NS4-R24, registered in 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-introductionIntroduction
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:
- a fixed structure, so the reader knows where to look;
- a controlled vocabulary of obligation, so the reader knows what is required;
- atomic requirements, so each can be tested on its own;
- заданный критерий, чтобы суждение не зависело от того, кто его выносит.
Цитировать
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 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. Normative references
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, *Каталог идентификаторов и артефактов*
- NS-2, *Citation and attribution*
- 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-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 conformance target: the kind of thing to which a requirement applies, for example a record, a dataset, a software release, an organisation or a process.
Цитировать
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| Элемент | Вид | Условный |
|---|---|---|
| Название | нормативный | нет |
| Foreword (status, proposal, owners, relation to other documents, changes from the previous edition) | informative | нет |
| Introduction (purpose and rationale) | informative | да |
| 1 Scope (what the document covers, and what it does not) | нормативный | нет |
| 2 Normative references | нормативный | 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 | нормативный | нет |
| Conformance (conformance targets, levels, classes, and how a claim is made) | нормативный | нет |
| Annexes, each marked normative or informative | either | да |
| Библиография информативных источников | 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 Clauses are numbered in arabic numerals to at most four levels (4.2.1.3). Annexes are lettered (Annex 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. Глагольные формы
5.1 NS4-R9. The following verbal forms shall be used, and only with these meanings.
Цитировать
NS-4, NS4-R9. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r9| Форма | Expresses | Negative |
|---|---|---|
| shall | a requirement | shall not |
| should | a recommendation | не следует |
| 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 The forms of clause 5.1 correspond to the keywords of [RFC2119] as clarified by [RFC8174]. A Nexus document that is also published as an internet specification may state that correspondence.
Цитировать
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. Each requirement shall be atomic: it states one obligation on one conformance target.
Цитировать
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> is the document's short code (for example 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-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. A requirement that depends on a quantity shall state the quantity, its unit and its tolerance, in accordance with the units and measurement standard of the programme once adopted (proposed 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 A requirement may refer to another document. A reference to a requirement in another document cites its identifier.
Цитировать
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;
- документ UNI;
- clause;
- verbal form;
- the conformance target;
- the test method (clause 3.6);
- ссылка на исполняемый тест, где находится метод
automated; - status.
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;
- any conformance levels or classes;
- the requirements each level or class comprises;
- форма заявления о соответствии.
8.2 NS4-R20. Заявление о соответствии должно содержать ссылку на:
Цитировать
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 party making it.
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. Front matter and structure of other documents
9.1 NS4-R1. Вводный блок (front matter) или 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 ---Обычный Markdown без блока метаданных (front matter) начинается с Nexus-UNI: <uni> on the first line (NS1-R5). HTML carries <meta name="nexus-uni"> и Schema.org JSON-LD записи (NS-7). Форматы Word, PDF и слайдов содержат UNI на титульной странице и в свойствах документа.
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.
- Доказательная база и происхождение данных: наборы данных, записи, модели и расчёты с указанием UNI (NS-2).
- Limitations.
- Conformance: the standards and clauses claimed (NS-14).
- Источники.
- Change log.
9.3 NS4-R2. Каждое число, каждый рисунок и каждая карта в документе должны ссылаться на свой исходный 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. Версии должны быть семантическими в соответствии с процедурой сопровождения (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-1010. Язык и стиль
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-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. Английский текст является основным. Переводы выполняются в соответствии с политикой в области доступности и языков (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. Conformance
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-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
| Версия 0.1 | Version 0.2 |
|---|---|
| с NS4-R1 по NS4-R4 (вводная часть, цитирование чисел, ограничения, семантические версии) | Retained with the same identifiers in clause 9 |
| No structure for standards | Clause 4 |
| Без глагольных форм | Clause 5 |
| Правила в таблицах | Atomic, identified, verifiable requirements (clause 6) |
| No register | Clause 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-bibliographyBibliography
[ISO-D2], [RFC2119], [RFC8174], [W3C-P] в governance/programme/BIBLIOGRAPHY.md.
История изменений
Versions from the catalogue; entries from the changelog that name this document.
| Версия | Дата | Примечание |
|---|---|---|
0.1.0 | 16 октября 2026 года | 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 (ПРЕДЛОЖЕНО). Категории DP, PR, CL, AT; схема записи v1.1 с контекстом NS-9; схемы пунктов, политик, аттестаций и предложений.