مخاطر المياه: المعايير المنطبقة
The 7 standards listed for water risk in the registry, each with its status, UNI (Unique Nexus Identifier) and the rules stated in its text.
- Nexus Standards: NS-0، NS-1، NS-3، NS-3b، NS-9، NS-10، NS-11.
- Open standards: OGC WaterML 2.0; OGC SensorThings API; WMO Information System 2.0 (WIS 2.0); Common Alerting Protocol Version 1.2; CF Metadata Conventions; Sendai Framework for Disaster Risk Reduction 2015–2030.
- البيانات والتدفقات: USGS Water Data APIs؛ التنبؤات العالمية بالفيضانات وإعادة التحليل من GloFAS؛ مخزون المياه الأرضية من GRACE/GRACE-FO (mascons)؛ Aqueduct 4.0 Water Risk Atlas؛ بيانات الهطول الشبكية شبه العالمية CHIRPS.
- يقترن بما يلي: الطاقة؛ الأغذية والزراعة؛ الصحة؛ مصادر الخطر الهيدرولوجية والجوية.
- Nexus Standards
- 7
- NS-0, NS-1, NS-3
- المعايير المفتوحة
- 6
- تُسمّى، ولا تُنسخ أبدًا
- البيانات والتغذيات
- 5
- مدرج للإحالة المرجعية
- الاقترانات
- 4
- مع مجالات أخرى
| القاعدة | النص |
|---|---|
NS0-P1 | Open · The standards, their registries, schemas, catalogues and reference tools are published in the canonical repository under the licences recorded in LICENSING.md. Participation in development is open to every community and stakeholder under GOVERNANCE.md. No standard depends on a proprietary artefact, product, account or mark to be applied. |
NS0-P2 | الأولوية للقابلية للقراءة الآلية · يوجد كل عنصر معياري في صورة بيانات (سجل، مخطط، بند) قبل أن يوجد في صورة نص؛ فالنص يشرح، والبيانات تحكم. والمعيار الذي ليس له صيغة آلية ليس من معايير Nexus Standards. |
NS0-P3 | Identified · Every artefact, record, deployment, policy and clause carries a UNI (NS-1, NS-3, NS-9). Nothing is cited by a name alone. |
NS0-P4 | Verified, not asserted · Conformance is a claim with evidence: receipts, digests, signed attestations and observations (NS-11). A claim without evidence is recorded as a claim, never as a fact, and the supported claim level of the implementation bounds every statement it makes. |
NS0-P5 | Zero trust · Authenticated is not authorised; entitled is not authorised; access is denied by default. Every verification, monitoring and enforcement path assumes no implicit trust between systems, tenants, sites or agents, and records who verified what under which mandate. |
NS0-P6 | Real-time · Standards express obligations that can be evaluated continuously against live records (observations, releases, corrections, deployments), and the standards themselves are versioned so that an implementation can state exactly which version it conforms to at any instant. |
NS0-P7 | Provenance everywhere · Every artefact records what it was derived from, who produced it, under which release and policy decision, and what corrected it (NS-3b, PROV-O profile). Corrections supersede; nothing is silently rewritten. |
NS0-P8 | الأمانة · يحدد معرّف UNI الهوية ويُحَل؛ ولا يصادق أبدًا. legalState defaults to review-required. Readiness, approval and production status are never implied by a standard, a status, a page, a score or a badge. |
NS0-P9 | Nexus-aware · Standards address cross-domain interdependence (water, energy, food, health, biodiversity, climate and the sectors they touch) explicitly: an obligation can reference artefacts in another domain, and cascades are first-class. |
NS0-P10 | Names are governed · Codes are never names. Public names follow the marks policy (governance/OPEN_BOUNDARY_IPR_AND_LICENSING.md, section 7). A system or component is shown by its neutral display name and its UNI; the UNI may change with context (NS-9), and no name infringes anyone’s mark. |
NS0-P11 | Community-owned development · Proposals, comments, decisions and versions of every standard are themselves artefacts with UNIs. The development process is specified (NS-13) and open, and authority to adopt is recorded, never assumed. |
NS0-P12 | Fail closed · Missing evidence, a missing legal state, a missing policy decision or unavailable verification results in a refusal with a typed reason, never in a pass. |
UNI وكتالوج المنتجات (القواعد v0.2: مقاطع المجال والقطاع والمنطقة والبيئة)
Status proposed · trust, authorisation and assurance · NXS-STD-ST-000001.
| القاعدة | النص |
|---|---|
NS1-R1 | One UNI shall identify one artefact concept; versions share the UNI and differ in @VERSION. |
NS1-R2 | UNIs shall be allocated only through a catalogue (mint) or a record allocation authority (NS-3); they shall not be typed by hand. |
NS1-R3 | UNIs shall not be deleted or reused. A withdrawn artefact keeps its record (WITHDRAWN); a replaced one records supersededBy. |
NS1-R4 | Every record shall carry the required metadata; legalState الوضع الافتراضي هو اشتراط المراجعة؛ claimCeiling stays inside the claim registry. |
NS1-R5 | The UNI shall be embedded in the artefact itself so that machines and people can find the record (section 6). |
NS1-R6 | A regional artefact shall carry REGION; public regional or national use still follows the geographic rules of the marks policy. |
NS1-R7 | Codes are classification and shall not be used as product names. |
NS1-R8 | A new scope, domain, sector or environment code shall meet the allocation rules CA-1 to CA-10 (section 1.1) and shall enter through an NS-13 proposal. |
NS1-R9 | A code shall not be reassigned or deleted; a retired code is deprecated with supersededBy, and identifiers that use it remain valid. |
NS1-R10 | A PROPOSED identifier may be used and shall be shown with its status until the registry change is adopted. |
معرّفات UNI لسجلات المخاطر (القواعد، والمطابقة مع الإرث السابق، وجهة التخصيص)
Status proposed · trust, authorisation and assurance; canonical risk data, records and provenance · NXS-STD-ST-000003.
يحدد NS-3 متطلباته في أقسام بدلًا من جدول قواعد.
ملف تعريف البيانات الوصفية لمجموعات البيانات والمنتجات (STAC وDCAT وPROV-O)
Status proposed · trust, authorisation and assurance; canonical risk data, records and provenance · NXS-STD-SW-000005.
يحدد NS-3b متطلباته في أقسام بدلًا من جدول قواعد.
معرّفات UNI السياقية (عمليات النشر، والنُّسخ، ونُسخ البرامج)
Status proposed · trust, authorisation and assurance · NXS-STD-ST-000005.
| القاعدة | النص |
|---|---|
NS9-R1 | Each deployment or programme instance shall have one context record; the concept keeps its own UNI; context.ofUni is required and shall resolve. |
NS9-R2 | Context identifiers shall be allocated by the catalogue for their SCOPE; they shall not be derived from names or typed by hand. |
NS9-R3 | The 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-R4 | Closing a context shall not delete it: context.validUntil يتم تعيينه وتصبح الحالة WITHDRAWN أو SUPERSEDED مع supersededBy. |
NS9-R5 | Display names in context shall follow the marks policy; the UNI, not the name, is the key everywhere. |
السياسات والبنود (التزامات مقروءة آليًا: التعريف والإلزام والتقييم والإنفاذ)
Status proposed · trust, authorisation and assurance; integrated posture and executive synthesis · NXS-STD-ST-000006.
| القاعدة | النص |
|---|---|
NS10-R1 | Every 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-R2 | Subjects shall be contextual UNIs; names, labels or free text shall not bind. |
NS10-R3 | The 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-R4 | External obligations shall be cited, not copied. |
NS10-R5 | Failure effects shall be typed; refuse هو الوضع الافتراضي لـ blocking بنود في سياقات الإنتاج. |
NS10-R6 | A clause or policy whose legalState is other than APPROVED may be evaluated, but its results shall be displayed as claims under review. |
NS10-R7 | Policies and clauses shall be append-only artefacts: withdrawal and supersession keep the record. |
التحقق والرصد (الأدلة والإفادات ورصد المطابقة وفق نهج انعدام الثقة)
Status proposed · trust, authorisation and assurance · NXS-STD-ST-000007.
| القاعدة | النص |
|---|---|
NS11-R1 | A conformance statement shall rest on an attestation, and an attestation shall name an evaluator, a mandate, evidence references and a digest. |
NS11-R2 | Under zero trust, subject and evaluator shall be distinct, and production evaluations shall run outside the subject’s trust boundary. |
NS11-R3 | Missing or unresolvable evidence shall yield INDETERMINATE or REFUSED, never PASS (NS0-P12). |
NS11-R4 | Attestations shall be append-only and superseded rather than changed; monitoring records shall be observations with record UNIs. |
NS11-R5 | Every displayed conformance value shall carry its evaluation instant and its evaluator; projections shall not store verdicts. |
NS11-R6 | Exports to Verifiable Credentials, in-toto or PROV-O are crosswalks; the Nexus attestation shall remain the record of truth. |
أسئلة وأجوبة.
Are these all the rules for water risk?
ماذا يدل معرّف القاعدة مثل NS1-R5؟
Around water risk.
شاركوا في صياغة المعايير الخاصة بمخاطر المياه.
تُدعى الحكومات والهيئات التنظيمية وهيئات المعايير والصناعة والأوساط الأكاديمية والمجتمعات إلى المساهمة في تشكيل الفهرس قبل إصداره الرسمي الأول المستهدف في عام 2030: التعليق على مسودة، أو اقتراح تغيير، أو الانضمام إلى فريق عامل، أو استضافة تمرين ميداني.
الحالة والاستخدام. Nexus Standards معايير مقترحة تُطوَّر عبر عملية مفتوحة بموجب NS-13 وتُنشر للاستخدام الطوعي؛ وهي لا تشكّل شهادة أو اعتمادًا أو موافقة تنظيمية، ويظل الاعتماد قرارًا لـ Global Standards Council، وفي كل بلد لمجلسه الوطني للمعايير. يحدد UNI (Unique Nexus Identifier) المنتج ولا يعتمده. وأسماء هيئات المعايير ومعاييرها ملك لأصحابها ولا تُستخدم إلا لتحديد الوثائق؛ ولا يُستنسخ هنا أي نص من معيار خارجي. وNexus Standards غير منتسبة إلى أي هيئة معايير مذكورة هنا، ولا مؤيَّدة ولا معتمدة منها.
التراخيص: CC BY 4.0 لنصوص المعايير والسجلات والمخططات والبيانات؛ وApache-2.0 للشفرة المرجعية. تُستشهد بالمعايير الخارجية بالاسم والرقم والرابط وفق تراخيصها الخاصة. وتحتفظ بيانات الجهات الخارجية ومكتباتها وخطوطها بتراخيصها الخاصة: انظر إشعارات الجهات الخارجية.