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 is cited by: NS-0, NS-1, NS-16.
  • Section 1, Foreword: no numbered requirement.
  • Section 2, Introduction: no numbered requirement.
  • Section 3, Scope: no numbered requirement.
  • Section 4, Normative references: no numbered requirement.
  • Section 5, Terms and definitions: no numbered requirement.
  • Section 6, Structure of a standard: R5, R6, R7, R8.
  • Section 7, Verbal forms: R9, R10.
  • Section 8, Writing requirements: R11, R12, R13, R14, R15.
  • Section 9, Register of requirements: 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.
  • Section 14, Annex A (informative): changes from version 0.1: R1, R4.
  • Section 15, Bibliography: no numbered requirement.
01نظرة عامة

الملخص

NS-4record
  1. الحالةمقترح
  2. نطاق المسؤوليةالمعرفة
  3. المعرّفNXS-STD-ST-000010
  4. القواعد المعلنة0
  5. مجالات البرنامج2
  6. الملفات المصدريةالمستودع

⁨Nexus Standards⁩ · مقترح

المتطلبات
24
القواعد المرقمة
الأقسام
15
في النص
يعتمد على
7
NS-0, NS-1, NS-2
مُستشهَد به في
3
⁨Nexus Standards⁩
02المعيار

NS-4: the standard

The text of NS-4 as it stands in the canonical repository (commit 2cbe0d41b5f8): 15 clauses, 0 sub-clauses and 24 identified requirements, each with its anchor and citation.

الرمز
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 (working draft of the revision; on adoption it supersedes the 0.1 document template)
الحالةPROPOSED · Proposal NXS-STD-PC-000010
Prepared and circulated bySaeed 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

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

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:

  1. a fixed structure, so the reader knows where to look;
  2. a controlled vocabulary of obligation, so the reader knows what is required;
  3. atomic requirements, so each can be tested on its own;
  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 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
  • هيكل ⁨Nexus Standards⁩ والمواصفات والسياسات والمذكرات التقنية للبرنامج؛
  • 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-2

1.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-2

2. 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, *Identifier and artefact catalogue*
  • NS-2, *Citation and attribution*
  • NS-13, *Standards development process*
  • 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 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-1

3.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-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 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-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: 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-4

4. 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
العنصرالنوعمشروط
العنوانnormativeلا
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)normativeلا
2 Normative referencesnormativeno; states "There are no normative references in this document." when there are none
3 Terms and definitionsnormativeno; refers to the Nexus-native risk vocabulary for terms it does not define itself
4 onwards: Requirements, organised by subjectnormativeلا
Conformance (conformance targets, levels, classes, and how a claim is made)normativeلا
Annexes, each marked normative or informativeeitherنعم
Bibliography of informative referencesinformativeنعم

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

5. الصيغ الفعلية

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
الشكلExpressesNegative
shalla requirementshall not
shoulda recommendationshould not
maya permissionneed not
cana possibility or capabilitycannot

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 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-6

6. Writing requirements

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-r11

6.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> 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-r12

6.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-r13

6.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-r14

6.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-r15

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

7. 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 conformance target;
  • the test method (clause 3.6);
  • the reference of the executable test, where the method is 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-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 register entry whose identifier does not appear in the clause it cites;
  • a document requirement identifier that is not registered;
  • an automated requirement 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-8

8. 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;
  • 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;
  • 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-9

9. Front matter and structure of other documents

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

يبدأ ملف Markdown العادي الذي لا يتضمن مقدمة بيانات وصفية (front matter) بـ 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
  1. Summary: what the document is, for whom, its supported claim level and its legal state, in one paragraph.
  2. Scope and definitions.
  3. Body.
  4. Evidence and provenance: datasets, records, models and runs, cited by UNI (NS-2).
  5. Limitations.
  6. Conformance: the standards and clauses claimed (NS-14).
  7. References.
  8. 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-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. 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-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. 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-11

11. Conformance

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-1

11.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-a

Annex A (informative): changes from version 0.1

Version 0.1Version 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 standardsClause 4
No verbal formsClause 5
Rules in tablesAtomic, identified, verifiable requirements (clause 6)
No registerClause 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

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.016 أكتوبر 2026current version in the catalogue
  • Unreleased NS-13 proposal 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؛ ومخطط السجل v1.1 مع سياق NS-9؛ ومخططات البنود والسياسات والإقرارات والمقترحات.
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
  • ⁨Zenodo⁩مدرج للاطلاع؛ لا يُستعلم منه
  • arXivمدرج للاطلاع؛ لا يُستعلم منه
  • Europe PMClisted for reference; not queried
  • OpenAIRE Graphlisted for reference; not queried

لم يُفعَّل بعدُ أي مصدر للعرض المباشر على هذا الموقع: فالمصادر مدرجة للإحالة المرجعية ولا يُستعلم من أيٍّ منها. وبمجرد أن يفعّل الناشر المعتمد مصدرًا بعد مراجعة شروطه، تُدرج الأعمال الحديثة هنا. البيانات الوصفية والروابط فقط: العنوان، والمؤلفون، ومكان النشر، والسنة، والنوع، وحالة الوصول المفتوح، والترخيص كما يسجّلها كل مصدر؛ وتُدرج الأعمال للاسترشاد، لا بوصفها أعمالًا مُراجَعة أو مُعتمَدة.

04في التطبيق العملي

أين يُطبَّق وكيف يُطوَّر

كيف يُطوَّر وكيف تشارك فيه، والمعيار بوصفه عملية، ومجالات البرامج التي تُدرجه.

How NS-4 is developed, and how to take part

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 relates to external standards by identifier, clause number and URL (NS14-R1), and directs the reader to the issuing body.

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 وتُنشر للاستخدام الطوعي؛ وهي لا تشكّل شهادة أو اعتمادًا أو موافقة تنظيمية، ويظل الاعتماد قرارًا لـ Global Standards Council، وفي كل بلد لمجلسه الوطني للمعايير. يحدد UNI (Unique Nexus Identifier) المنتج ولا يعتمده. وأسماء هيئات المعايير ومعاييرها ملك لأصحابها ولا تُستخدم إلا لتحديد الوثائق؛ ولا يُستنسخ هنا أي نص من معيار خارجي. وNexus Standards غير منتسبة إلى أي هيئة معايير مذكورة هنا، ولا مؤيَّدة ولا معتمدة منها.

التراخيص: ⁨CC BY 4.0⁩ لنصوص المعايير والسجلات والمخططات والبيانات؛ و⁨Apache-2.0⁩ للشفرة المرجعية. تُستشهد بالمعايير الخارجية بالاسم والرقم والرابط وفق تراخيصها الخاصة. وتحتفظ بيانات الجهات الخارجية ومكتباتها وخطوطها بتراخيصها الخاصة: انظر إشعارات الجهات الخارجية.