Skip to content
ستانداردموڵکە هاوبەشەکان و ژوورەکانی فەرماندەییستانداردە جێبەجێبووەکان
موڵکە هاوبەشەکان و ژوورەکانی فەرماندەیی

Commons and command rooms: standards that apply

The 3 standards listed for commons and command rooms in the registry, each with its status, UNI (Unique Nexus Identifier) and the rules stated in its text.

موڵکە هاوبەشەکان و ژوورەکانی فەرماندەیی
What this area is built from: the Nexus Standards it applies (marked), the open standards it names and the data and feeds it reads, then the areas it couples with.Source: the Nexus Standards registry: the area record.
  • Nexus Standards: NS-6, NS-9, NS-10, NS-11.
  • Open standards: OASIS EDXL Situation Reporting 1.0; OASIS Common Alerting Protocol Version 1.2; Activity Streams 2.0; Web Content Accessibility Guidelines (WCAG) 2.2.
  • Data and feeds: WMO Register of Alerting Authorities CAP feeds; INFORM Risk index data.
  • Couples with: Policies and clauses; Decision records and accountability; Monitoring services.
Nexus Standards
4
NS-6, NS-9, NS-10
ستانداردە کراوەکان
4
named, never copied
Data and feeds
2
listed for reference
پەیوەستبوونەکان
3
with other areas
01NS-9

UNIی ناوەڕۆکی (دامەزراندنەکان، نموونەکان، نموونەکانی پڕۆگرام)

Status proposed · trust, authorisation and assurance · NXS-STD-ST-000005.

یاسادەق
NS9-R1Each deployment or programme instance shall have one context record; the concept keeps its own UNI; context.ofUni is required and shall resolve.
NS9-R2Context identifiers shall be allocated by the catalogue for their SCOPE; they shall not be derived from names or typed by hand.
NS9-R3The supported claim level, legal state and conformance evidence of a context are its own; they shall not be inherited from the concept or from another context.
NS9-R4Closing a context shall not delete it: context.validUntil is set and the status becomes WITHDRAWN یان SUPERSEDED لەگەڵ supersededBy.
NS9-R5Display names in context shall follow the marks policy; the UNI, not the name, is the key everywhere.

Read NS-9 in full

02NS-10

سیاسەت و بڕگەکان (پابەندبوونە ئامێر-خوێندراوەکان: پێناسە، پابەندکردن، هەڵسەنگاندن و جێبەجێکردن)

Status proposed · trust, authorisation and assurance; integrated posture and executive synthesis · NXS-STD-ST-000006.

یاسادەق
NS10-R1Every obligation that an implementation enforces shall be a clause with a UNI; code may implement a rule, but no rule shall be enforced without a clause record that names it.
NS10-R2Subjects shall be contextual UNIs; names, labels or free text shall not bind.
NS10-R3The predicate shall be data in a declared language; evaluators shall record the engine and its version; two conformant evaluators shall reach the same result for the same clause and the same inputs.
NS10-R4External obligations shall be cited, not copied.
NS10-R5Failure effects shall be typed; refuse is the default for blocking clauses in production contexts.
NS10-R6A clause or policy whose legalState is other than APPROVED may be evaluated, but its results shall be displayed as claims under review.
NS10-R7Policies and clauses shall be append-only artefacts: withdrawal and supersession keep the record.

Read NS-10 in full

03NS-11

سەلماندن و چاودێری (بەڵگە، گواهییەکان، چاودێریی گونجان لەگەڵ zero-trust)

Status proposed · trust, authorisation and assurance · NXS-STD-ST-000007.

یاسادەق
NS11-R1A conformance statement shall rest on an attestation, and an attestation shall name an evaluator, a mandate, evidence references and a digest.
NS11-R2Under zero trust, subject and evaluator shall be distinct, and production evaluations shall run outside the subject’s trust boundary.
NS11-R3Missing or unresolvable evidence shall yield INDETERMINATE or REFUSED, never PASS (NS0-P12).
NS11-R4Attestations shall be append-only and superseded rather than changed; monitoring records shall be observations with record UNIs.
NS11-R5Every displayed conformance value shall carry its evaluation instant and its evaluator; projections shall not store verdicts.
NS11-R6Exports to Verifiable Credentials, in-toto or PROV-O are crosswalks; the Nexus attestation shall remain the record of truth.

Read NS-11 in full

04پرسیارەکان

پرسیار و وەڵام.

Are these all the rules for commons and command rooms?
They are the rules stated by the listed standards. The principles of NS-0 bind every standard; clauses specific to the area, where needed, are written under NS-10 and evaluated under NS-11.
What does a rule identifier such as NS1-R5 denote?
The number of the standard and the number of the rule within it. Rule identifiers are stable so that clauses, attestations and publications can cite them.
ستاندارد

Shape the standards for commons and command rooms.

Governments, regulators, standards bodies, industry, academia and communities are invited to shape the catalogue ahead of its first official release, targeted for 2030: comment on a draft, propose a change, join a working group or host a field exercise.

دۆخ و بەکارهێنان. Nexus Standards ستانداردی پێشنیارکراون کە لە ڕێگەی پرۆسەیەکی کراوەوە لەژێر NS-13 پەرەیان پێدراوە و بۆ بەکارهێنانی خۆبەخشانە بڵاو کراونەتەوە؛ بڕوانامە، متمانەپێدان یان ڕەزامەندیی ڕێکخەر نین، و پەسەندکردن بڕیاری ئەنجومەنی جیهانیی ستانداردەکان و، لە هەر وڵاتێکدا، ئەنجومەنی نیشتمانیی ستانداردەکانی ئەو وڵاتەیە. UNI (Unique Nexus Identifier) بەرهەمێک دەناسێنێت؛ بڕوانامەی پێ نادات. ناوی دەستەکانی ستاندارد و ستانداردەکانیان هی پارێزەرەکانیانن و تەنها بۆ ناساندنی بەڵگەنامەکان بەکاردێن؛ هیچ دەقێکی ستانداردێکی دەرەکی لێرەدا دووبارە نەکراوەتەوە. Nexus Standards پەیوەست نییە بە هیچ دەستەیەکی ستانداردی ناوهێنراو لێرەدا، و لەلایەن هیچیانەوە پشتگیری یان بڕوانامەی پێ نەدراوە.

مۆڵەتەکان: CC BY 4.0 بۆ دەقی ستانداردەکان، تۆمارگەکان، سکێماکان و داتا؛ Apache-2.0 بۆ کۆدی سەرچاوە. ستانداردە دەرەکییەکان بە ناو، ژمارە و بەستەر لە ژێر مۆڵەتەکانی خۆیاندا ئاماژەیان پێدەدرێت. داتا، کتێبخانە و فۆنتەکانی لایەنی سێیەم مۆڵەتەکانی خۆیان دەپارێزن: بڕوانە ئاگادارییەکانی لایەنی سێیەم.