Skip to content
StandarStandar risiko airStandar yang diterapkan
Risiko air

Risiko air: standar yang berlaku

7 standar yang tercantum untuk risiko air di registri, masing-masing dengan statusnya, UNI (Unique Nexus Identifier), dan aturan yang dinyatakan dalam teksnya.

Standar risiko air
Unsur pembentuk bidang ini: Nexus Standards yang diterapkannya (ditandai), standar terbuka yang disebutkannya, serta data dan umpan yang dibacanya, kemudian bidang-bidang yang terhubung dengannya.Sumber: registri Nexus Standards: catatan area.
  • 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.
  • Data dan umpan: USGS Water Data APIs; prakiraan dan reanalisis banjir global GloFAS; mascon penyimpanan air terestrial GRACE/GRACE-FO; Aqueduct 4.0 Water Risk Atlas; presipitasi grid kuasi-global CHIRPS.
  • Terhubung dengan: Energi; Pangan dan pertanian; Kesehatan; Bahaya hidrometeorologi.
Nexus Standards
7
NS-0, NS-1, NS-3
Standar terbuka
6
disebutkan, tidak pernah disalin
Data dan umpan
5
dicantumkan sebagai rujukan
Keterkaitan
4
dengan area lain
01NS-0

Konstitusi dan prinsip

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

AturanTeks
NS0-P1Open · 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-P2Utamakan keterbacaan mesin · Setiap unsur normatif ada sebagai data (registri, skema, klausul) sebelum ada sebagai prosa; prosa menjelaskan, data yang mengatur. Standar tanpa bentuk mesin bukanlah Nexus Standard.
NS0-P3Identified · Every artefact, record, deployment, policy and clause carries a UNI (NS-1, NS-3, NS-9). Nothing is cited by a name alone.
NS0-P4Verified, 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-P5Zero 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-P6Real-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-P7Provenance 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-P8Jujur · UNI mengidentifikasi dan meresolusi; UNI tidak pernah menyertifikasi. 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-P9Nexus-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-P10Names 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-P11Community-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-P12Fail 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.

Baca NS-0 selengkapnya

02NS-1

UNI dan katalog artefak (tata bahasa v0.2: segmen domain, sektor, kawasan, dan lingkungan)

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

AturanTeks
NS1-R1One UNI shall identify one artefact concept; versions share the UNI and differ in @VERSION.
NS1-R2UNIs shall be allocated only through a catalogue (mint) or a record allocation authority (NS-3); they shall not be typed by hand.
NS1-R3UNIs shall not be deleted or reused. A withdrawn artefact keeps its record (WITHDRAWN); a replaced one records supersededBy.
NS1-R4Every record shall carry the required metadata; legalState secara bawaan memerlukan tinjauan; claimCeiling stays inside the claim registry.
NS1-R5The UNI shall be embedded in the artefact itself so that machines and people can find the record (section 6).
NS1-R6A regional artefact shall carry REGION; public regional or national use still follows the geographic rules of the marks policy.
NS1-R7Codes are classification and shall not be used as product names.
NS1-R8A 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-R9A code shall not be reassigned or deleted; a retired code is deprecated with supersededBy, and identifiers that use it remain valid.
NS1-R10A PROPOSED identifier may be used and shall be shown with its status until the registry change is adopted.

Baca NS-1 selengkapnya

03NS-3

UNI catatan risiko (tata bahasa, pemetaan silang warisan, otoritas alokasi)

Status proposed · trust, authorisation and assurance; canonical risk data, records and provenance · NXS-STD-ST-000003.

NS-3 menyatakan persyaratannya dalam bagian-bagian, bukan dalam tabel aturan.

Baca NS-3 selengkapnya

04NS-3b

Profil metadata set data dan produk (STAC, DCAT, PROV-O)

Status proposed · trust, authorisation and assurance; canonical risk data, records and provenance · NXS-STD-SW-000005.

NS-3b menyatakan persyaratannya dalam bagian-bagian, bukan dalam tabel aturan.

Baca NS-3b selengkapnya

05NS-9

UNI kontekstual (penerapan, instans, instans program)

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

AturanTeks
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 ditetapkan dan statusnya menjadi WITHDRAWN atau SUPERSEDED dengan supersededBy.
NS9-R5Display names in context shall follow the marks policy; the UNI, not the name, is the key everywhere.

Baca NS-9 selengkapnya

06NS-10

Kebijakan dan klausul (kewajiban yang dapat dibaca mesin: definisi, pengikatan, evaluasi, dan penegakan)

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

AturanTeks
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 adalah nilai bawaan untuk blocking klausul dalam konteks produksi.
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.

Baca NS-10 selengkapnya

07NS-11

Verifikasi dan pemantauan (bukti, atestasi, observasi kesesuaian zero-trust)

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

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

Baca NS-11 selengkapnya

08Pertanyaan

Tanya jawab.

Are these all the rules for water risk?
Itu adalah aturan yang dinyatakan oleh standar yang tercantum. Prinsip NS-0 mengikat setiap standar; klausul khusus bidang ini, jika diperlukan, ditulis berdasarkan NS-10 dan dievaluasi berdasarkan NS-11.
Apa yang dimaksud dengan pengenal aturan seperti NS1-R5?
Nomor standar dan nomor aturan di dalamnya. Pengenal aturan bersifat stabil sehingga klausul, atestasi, dan publikasi dapat mengutipnya.
Standar

Bentuk standar untuk risiko air.

Pemerintah, regulator, badan standar, industri, akademisi, dan komunitas diundang untuk membentuk katalog sebelum rilis resmi pertamanya yang ditargetkan pada 2030: berikan komentar pada draf, usulkan perubahan, bergabunglah dengan kelompok kerja, atau selenggarakan latihan lapangan.

Status dan penggunaan. Nexus Standards adalah standar usulan yang dikembangkan melalui proses terbuka berdasarkan NS-13 dan diterbitkan untuk penggunaan sukarela; standar ini bukan sertifikasi, akreditasi, atau persetujuan regulasi, dan adopsi tetap menjadi keputusan Global Standards Council serta, di setiap negara, Dewan Standar Nasionalnya. UNI (Unique Nexus Identifier) mengidentifikasi artefak; UNI tidak menyertifikasinya. Nama badan standar dan standarnya adalah milik pengelolanya dan hanya digunakan untuk mengidentifikasi dokumen; tidak ada teks standar eksternal yang direproduksi di sini. Nexus Standards tidak berafiliasi dengan, didukung oleh, atau disertifikasi oleh badan standar mana pun yang disebut di sini.

Lisensi: CC BY 4.0 untuk teks standar, registri, skema, dan data. Apache-2.0 untuk kode acuan. Standar eksternal dikutip dengan nama, nomor, dan tautan di bawah lisensinya sendiri. Data, pustaka, dan fon pihak ketiga mempertahankan lisensinya sendiri: lihat Pemberitahuan pihak ketiga.