Skip to content
StandardsGeophysical hazard standardsStandards that apply
Geophysical hazard

Geophysical hazard: standards that apply

The 4 standards listed for geophysical hazard in the registry, each with its status, UNI (Unique Nexus Identifier) and the rules stated in its text.

Geophysical hazard standards
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-0, NS-3, NS-3b, NS-11.
  • Open standards: UNDRR-ISC Hazard Information Profiles; Common Alerting Protocol Version 1.2; RFC 7946 The GeoJSON Format; WMO Cataloguing of Hazardous Events (WMO-CHE); Sendai Framework Monitor indicators (report A/71/644; General Assembly resolution A/RES/71/276).
  • Data and feeds: USGS earthquake GeoJSON summary feeds; Global Volcanism Program volcano and eruption database; NCEI/WDS Global Historical Tsunami Database; NASA landslide nowcasts (LHASA) and Global Landslide Catalog.
  • Couples with: Technological and industrial hazard; Critical infrastructure and critical entities; Compound and cascading hazard; Atmosphere and air quality.
Nexus Standards
4
NS-0, NS-3, NS-3b
Open standards
5
named, never copied
Data and feeds
4
listed for reference
Couplings
4
with other areas
01NS-0

घटना आणि तत्त्वे

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

नियमText
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-P2Machine-readable first · Every normative element exists as data (registry, schema, clause) before it exists as prose; prose explains, data governs. A standard with no machine form is not a 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-P8Honest · A UNI identifies and resolves; it never certifies. 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.

Read NS-0 in full

02NS-3

जोखीम नोंद UNI (व्याकरण, जुना तुलनात्मक संदर्भ, वाटप प्राधिकरण)

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

NS-3 states its requirements in sections rather than in a table of rules.

Read NS-3 in full

03NS-3b

डेटासंच आणि उत्पादन मेटाडेटा प्रोफाइल (STAC, DCAT, PROV-O)

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

NS-3b states its requirements in sections rather than in a table of rules.

Read NS-3b in full

04NS-11

सत्यापन आणि देखरेख (पुरावा, प्रमाणपत्रे, शून्य-विश्वास अनुरूपता निरीक्षण)

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

नियमText
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

05प्रश्न

प्रश्न आणि उत्तरे.

Are these all the rules for geophysical hazard?
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 geophysical hazard.

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. बाह्य मानके त्यांच्या स्वतःच्या परवान्याखाली नाव, क्रमांक आणि दुव्याद्वारे उद्धृत केली जातात. तृतीय-पक्ष माहिती, ग्रंथालये आणि फॉन्ट त्यांचे स्वतःचे परवाने राखतात: तृतीय-पक्ष सूचना पाहा.