Skip to content
StandartlarNS-4Önerildi
NS-4

NS-4: Nexus Standards ve belgelerin yapısı ve yazımı (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.
  • Bölüm 12, Dil ve üslup: 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.
  • Bölüm 15, Kaynakça: numaralandırılmış gereklilik yoktur.
01Genel bakış

Özet

NS-4kayıt
  1. Durumönerildi
  2. Sorumlu kapsambilgi
  3. TanımlayıcıNXS-STD-ST-000010
  4. Belirtilen kurallar0
  5. Program alanları2
  6. Kaynak dosyalardepo

Nexus Standards · proposed

Gereksinimler
24
numaralandırılmış kurallar
Bölümler
15
metinde
Bağımlı olduğu
7
NS-0, NS-1, NS-2
Atıf yapanlar
3
Nexus Standards
02Standart

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.

Kod
NS-4
Başlık
Nexus Standards ve belgelerinin yapısı ve yazımı (v0.2: hüküm yapısı, fiil kipleri, kayıtlı gereksinimler; belge ön bölümü)
Sürüm
0.2.0
Durum
ÖNERİLDİ
Tarih
catalogue 2026-10-16 · circulated 17 October 2026
Unique Nexus Identifier
NXS-STD-ST-000010
Sorumlu kapsam
bilgi
Kaynak
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.

Sürüm0.2.0 (working draft of the revision; on adoption it supersedes the 0.1 document template)
DurumPROPOSED · Proposal NXS-STD-PC-000010
Prepared and circulated bySaeed Valadbaygi, Chief Steward, Nexus Standards (saeed@therisk.global), 17 October 2026
AşamaPreparatory working draft, circulated for review and comment. Not for implementation. Stage designation reserved to the Global Standards Council (NS-13)
SahipWG-DEV with the editors; committee TC-CORE
Üst öğeNS-1; process NS-13
GereksinimlerNS4-R1 to NS4-R24, registered in registry/requirements.yaml
Atıf yapınNS-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.

Atıf yapınNS-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.
Atıf yapınNS-4, clause 1. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-1

1. Kapsam

1.1 This document specifies:

Atıf yapınNS-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;
  • gereklilikleri yazma ve kaydetme kuralları;
  • 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.

Atıf yapınNS-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).

Atıf yapınNS-4, clause 1.3. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-1-3
Atıf yapınNS-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, *Tanımlayıcı ve yapıt kataloğu*
  • NS-2, *Citation and attribution*
  • NS-13, *Standards development process*
  • NS-14, *Uygunluk ve eşleştirme tablosu*
  • registry/requirements.yaml, *Register of normative requirements* (NXS-STD-DS-000013)
Atıf yapınNS-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]).

Atıf yapınNS-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.

Atıf yapınNS-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.

Atıf yapınNS-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.

Atıf yapınNS-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.

Atıf yapınNS-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:

Atıf yapınNS-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.

Atıf yapınNS-4, clause 3.7. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-3-7
Atıf yapınNS-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.

Atıf yapınNS-4, NS4-R5. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r5
UnsurTürKoşullu
Başlıknormativehayır
Foreword (status, proposal, owners, relation to other documents, changes from the previous edition)informativehayır
Introduction (purpose and rationale)informativeevet
1 Scope (what the document covers, and what it does not)normativehayır
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 subjectnormativehayır
Conformance (conformance targets, levels, classes, and how a claim is made)normativehayır
Annexes, each marked normative or informativeeitherevet
Bibliography of informative referencesinformativeevet

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

Atıf yapınNS-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).

Atıf yapınNS-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.

Atıf yapınNS-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).

Atıf yapınNS-4, clause 4.5. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-4-5
Atıf yapınNS-4, clause 5. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-5

5. Fiil kipleri

5.1 NS4-R9. The following verbal forms shall be used, and only with these meanings.

Atıf yapınNS-4, NS4-R9. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r9
BiçimExpressesNegative
shallbir gereklilikshall not
shoulda recommendationshould not
olabilira permissionneed not
cana possibility or capabilityyapamaz

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.

Atıf yapınNS-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.

Atıf yapınNS-4, clause 5.3. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-5-3
Atıf yapınNS-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.

Atıf yapınNS-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>, burada <DOC> is the document's short code (for example NS4, IHP, NRS-C17) ve <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.

Atıf yapınNS-4, NS4-R12. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r12

6.3 NS4-R13. Bir gereklilik doğrulanabilir olmalıdır. Uygunluğun hangi ölçütlerle değerlendirildiğini belirtmeli veya bu ölçütlere atıfta bulunmalıdır. “Uygun”, “yeterli”, “kâfi”, “zamanında” ve “son teknoloji” gibi belirli bir ölçüt içermeyen sözcükler, bir gerekliliğin tek ölçütü olarak kullanılmamalıdır.

Atıf yapınNS-4, NS4-R13. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r13

6.4 NS4-R14. Bir büyüklüğe bağlı olan gereklilik, programın benimsenecek birimler ve ölçüm standardına (önerilen NRS-C24) uygun olarak, bu büyüklüğü, birimini ve toleransını belirtmelidir.

Atıf yapınNS-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.

Atıf yapınNS-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.

Atıf yapınNS-4, clause 6.6. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-6-6
Atıf yapınNS-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:

Atıf yapınNS-4, NS4-R16. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r16
  • identifier;
  • belge UNI;
  • clause;
  • verbal form;
  • uyumluluk hedefi;
  • the test method (clause 3.6);
  • the reference of the executable test, where the method is automated;
  • status.

7.2 NS4-R17. Bir gereklilik şu durumlardan birine sahip olmalıdır PROPOSED, IN_COMMENT, ADOPTED, SUPERSEDED veya WITHDRAWN. The status of a requirement shall not run ahead of the status of its document.

Atıf yapınNS-4, NS4-R17. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r17

7.3 NS4-R18. The validator shall refuse:

Atıf yapınNS-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;
  • bir 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.

Atıf yapınNS-4, clause 7.4. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-7-4
Atıf yapınNS-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:

Atıf yapınNS-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. Bir uygunluk beyanı şunlara atıf yapmalıdır:

Atıf yapınNS-4, NS4-R20. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r20
  • belgenin UNI ve sürümü;
  • 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.

Atıf yapınNS-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.

Atıf yapınNS-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 ---

Ön bilgi bloğu (front matter) içermeyen düz Markdown şununla başlar 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:

Atıf yapınNS-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).

Atıf yapınNS-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.

Atıf yapınNS-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). Değişen bir sayı veya sonuç, değişiklik günlüğü satırı ve özet değeri ile birlikte yeni bir sürüm olur.

Atıf yapınNS-4, NS4-R4. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r4
Atıf yapınNS-4, clause 10. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-10

10. Dil ve üslup

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.

Atıf yapınNS-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.

Atıf yapınNS-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.

Atıf yapınNS-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).

Atıf yapınNS-4, NS4-R24. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-r-ns4-r24
Atıf yapınNS-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.

Atıf yapınNS-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.

Atıf yapınNS-4, clause 11.2. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-11-2
Atıf yapınNS-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

Sürüm 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 registerMadde 7
No conformance clause ruleClause 8
Atıf yapınNS-4, Bibliography. NXS-STD-ST-000010@0.2.0. https://nexustandards.com/standards/ns-4/#nx-c-bibliography

Kaynakça

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

Değişiklik geçmişi

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

SürümTarihNot
0.1.016 Ekim 2026current version in the catalogue
  • Yayımlanmamış NS-13 önerisi NXS-STD-PC-000010 (OPEN, politika), Baş Sorumlu Saeed Valadbaygi tarafından önerildi: ilk çalışma programı. İçinde governance/programme/: kaynakça (NXS-STD-DC-000027); bilgi tehlikeleri ve çift kullanımlı içeriğe ilişkin politika (NXS-STD-PO-000001, Konsey kararına kadar ihtiyaten uygulanmaktadır); bakım prosedürü (NXS-STD-DC-000028); NHS-2 model spesifikasyonu (NXS-STD-TN-000001); yeni çalışma kalemleri NRS-C17 ila NRS-C24 (NXS-STD-DC-000029); çalışma kolu görev tanımı (NXS-STD-DC-000030); davetler ve kanallar (NXS-STD-DC-000031); erişilebilirlik ve dillere ilişkin politika (NXS-STD-PO-000002); uygunluk değerlendirme programı (NXS-STD-DC-000032); ön not (NXS-STD-DC-000033). Ayrıca: NS-4 sürüm 0.2 (yapı ve yazım). registry/requirements.yaml (NXS-STD-DS-000013, 108 gereklilik) ve registry/information-hazard-screen.yaml (NXS-STD-DS-000014), her ikisi de doğrulayıcı tarafından uygulanır. Dört hedefli çağrı registry/participation.yaml.
  • 0.2.0 – 2026-10-16 NS-0 tüzüğü; NS-2, NS-4, NS-5, NS-9, NS-10, NS-11, NS-12, NS-13, NS-14 taslakları hazırlandı (ÖNERİLDİ). DP, PR, CL, AT kategorileri; NS-9 bağlamıyla kayıt şeması v1.1; madde, politika, beyan ve öneri şemaları.
03Araştırma

Araştırma, kaynaklar ve dosyalar

Recent research on NS-4

Bu standardın konusu üzerine güncel hakemli makaleler, ön baskılar, veri kümeleri ve raporlar; okuma sırasında kayıttan oluşturulan arama terimleriyle açık akademik üst veri hizmetlerinden (OpenAlex, Crossref, DataCite, Zenodo, arXiv, Europe PMC, OpenAIRE Graph) alınır. Her eser yazarları, yayın yeri, yılı, türü, açık erişim durumu ve lisansıyla listelenir ve DOI'sine veya açılış sayfasına bağlantı verilir. Bu sitede henüz canlı gösterim için etkinleştirilmemiş kaynaklar referans için listelenir ve sorgulanmaz.

Search termsmachine-readable standards; standards development; requirements engineering; SMART standards; normative text; W3C Process Document; UK Government Open Standards Principlescombined with: standard; standards; requirementsStandardın konusundan ve kurallarından ile eşleştirme alanlarındaki dış standartlardan türetilmiştir.

  • OpenAlexlisted for reference; not queried
  • Crossreflisted for reference; not queried
  • DataCitelisted for reference; not queried
  • Zenodolisted for reference; not queried
  • arXivreferans için listelenmiştir; sorgulanmaz
  • Europe PMClisted for reference; not queried
  • OpenAIRE Graphlisted for reference; not queried

Bu sitede henüz canlı gösterim için etkinleştirilmiş bir kaynak yoktur: kaynaklar başvuru amacıyla listelenir ve hiçbiri sorgulanmaz. Kayıtlı yayıncı, koşulları incelendikten sonra bir kaynağı etkinleştirdiğinde son çalışmalar burada listelenir. Yalnızca üstveri ve bağlantılar: her kaynağın kaydettiği şekliyle başlık, yazarlar, yayın yeri, yıl, tür, açık erişim durumu ve lisans; çalışmalar yön göstermek amacıyla listelenir, incelenmez veya onaylanmaz.

04Uygulamada

Nerede uygulandığı ve nasıl geliştirildiği

Nasıl geliştirildiği ve nasıl katılım sağlanacağı, bir süreç olarak standart ve onu listeleyen program alanları.

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.

05Harici standartlar

Dış standartlarla ilişki

NS-4, harici standartlarla tanımlayıcı, madde numarası ve URL üzerinden ilişki kurar (NS14-R1) ve okuyucuyu yayımlayan kuruma yönlendirir.

06Ağ genelinde

Öğrenme, ağ ve sorular

Risk Academy kursları ve disiplinleri

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.

Dersler

Disiplinler

Kurslar, disiplinler ve Nexus Standards arasındaki karşılık, Risk Academy ile birlikte sürdürülür ve onun akademik incelemesine tabidir.

RaporlarKatkıda bulunun

Bu sayfadan kanıt katkısında bulunun.

Reports, Konsorsiyumun üç aylık yayınıdır. Bu konuda bildikleriniz bir sonraki sayıda kanıt, örnek olay veya düzeltme olabilir; adınız belirtilir ve kendi çalışmanızsa CC BY 4.0 lisansıyla yayımlanır.

Nexus Standards
Standartlar

Standartlara katılın.

Hükümetler, düzenleyiciler, standart kuruluşları, sanayi, akademi ve topluluklar, 2030 için hedeflenen ilk resmî sürümden önce kataloğun şekillenmesine katkıya davet edilir: bir taslağa yorum yapın, bir değişiklik önerin, bir çalışma grubuna katılın veya bir saha tatbikatına ev sahipliği yapın.

Durum ve kullanım. Nexus Standards, NS-13 kapsamında açık bir süreçle geliştirilen ve gönüllü kullanım için yayımlanan önerilmiş standartlardır; sertifikasyon, akreditasyon veya düzenleyici onay niteliği taşımaz ve benimseme, Global Standards Council’ın ve her ülkede o ülkenin National Standards Council’ının kararı olarak kalır. Bir UNI (Unique Nexus Identifier) bir artefaktı tanımlar; onu sertifikalandırmaz. Standart kuruluşlarının ve standartlarının adları sahiplerine aittir ve yalnızca belgeleri tanımlamak için kullanılır; burada hiçbir dış standardın metni çoğaltılmaz. Nexus Standards burada adı geçen hiçbir standart kuruluşuyla bağlantılı değildir, onlar tarafından onaylanmamış veya sertifikalandırılmamıştır.

Lisanslar: standart metni, sicil, şema ve veriler için CC BY 4.0. Referans kod için Apache-2.0. Harici standartlara kendi lisansları altında ad, numara ve bağlantıyla atıf yapılır. Üçüncü taraf veri, kütüphane ve yazı tipleri kendi lisanslarını korur: bkz. Üçüncü taraf bildirimleri.