Riesgo climático: normas aplicables
Los 7 estándares incluidos para riesgo climático en el registro, cada uno con su estado, su UNI (Unique Nexus Identifier) y las reglas establecidas en su texto.
- Nexus Standards: NS-0, NS-1, NS-3, NS-3b, NS-9, NS-11, NS-14.
- Normas abiertas: marco de riesgo del Grupo de Trabajo II del IE6 del IPCC (amenaza, exposición, vulnerabilidad, respuesta); escenarios climáticos de la NGFS; CF Metadata Conventions; Recomendaciones del Grupo de Trabajo sobre Divulgaciones Financieras Relacionadas con el Clima; Acuerdo de París; SpatioTemporal Asset Catalog (STAC).
- Datos y flujos: reanálisis ERA5 (Copernicus Climate Data Store); proyecciones climáticas CMIP6 (Copernicus Climate Data Store); NGFS Scenario Explorer; Índice de Riesgo INFORM.
- Se acopla con: amenazas hidrometeorológicas; riesgo financiero y económico; amenazas compuestas y en cascada; adaptación climática y riesgo de transición.
- Nexus Standards
- 7
- NS-0, NS-1, NS-3
- Estándares abiertos
- 6
- citado, nunca copiado
- Datos y flujos
- 4
- indicado como referencia
- Acoplamientos
- 4
- con otras áreas
Constitución y principios
Status proposed · trust, authorisation and assurance · NXS-STD-ST-000004.
| Regla | Texto |
|---|---|
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 | Primero legible por máquina · Todo elemento normativo existe como datos (registro, esquema, cláusula) antes de existir como prosa; la prosa explica, los datos rigen. Una norma sin forma legible por máquina no es un Nexus Standard. |
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 | Honesto · Un UNI identifica y resuelve; nunca certifica. 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. |
El UNI y el catálogo de artefactos (gramática v0.2: segmentos de dominio, sector, región y entorno)
Status proposed · trust, authorisation and assurance · NXS-STD-ST-000001.
| Regla | Texto |
|---|---|
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 por defecto, requiere revisión; 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 de registros de riesgo (gramática, correspondencia con lo existente, autoridad de asignación)
Status proposed · trust, authorisation and assurance; canonical risk data, records and provenance · NXS-STD-ST-000003.
NS-3 enuncia sus requisitos en secciones y no en una tabla de reglas.
Perfil de metadatos de conjuntos de datos y productos (STAC, DCAT, PROV-O)
Status proposed · trust, authorisation and assurance; canonical risk data, records and provenance · NXS-STD-SW-000005.
NS-3b expone sus requisitos en secciones y no en una tabla de reglas.
UNI contextuales (despliegues, instancias, instancias de programa)
Status proposed · trust, authorisation and assurance · NXS-STD-ST-000005.
| Regla | Texto |
|---|---|
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 se establece y el estado pasa a ser WITHDRAWN or SUPERSEDED con supersededBy. |
NS9-R5 | Display names in context shall follow the marks policy; the UNI, not the name, is the key everywhere. |
Verificación y seguimiento (evidencia, atestaciones, observación de la conformidad de confianza cero)
Status proposed · trust, authorisation and assurance · NXS-STD-ST-000007.
| Regla | Texto |
|---|---|
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. |
Conformidad y correspondencia con normas externas
Status proposed · trust, authorisation and assurance · NXS-STD-ST-000013.
| Regla | Texto |
|---|---|
NS14-R1 | The text of an external standard shall not be reproduced; it shall be cited by identifier, clause number and URL. |
NS14-R2 | Relation claims shall come from the register and from clause sets, not from prose. |
NS14-R3 | "Compliant" and "certified" shall appear only as quotations of an authority decision cited by reference. |
NS14-R4 | Marks of standards bodies shall not form part of a Nexus name. |
NS14-R5 | Unverified register entries shall be displayed as unverified. |
Preguntas y respuestas.
¿Son estas todas las normas sobre riesgo climático?
¿Qué designa un identificador de regla como NS1-R5?
Around climate risk.
Dé forma a las normas sobre riesgo climático.
Se invita a los gobiernos, los reguladores, los organismos de normalización, la industria, el mundo académico y las comunidades a dar forma al catálogo antes de su primera versión oficial, prevista para 2030: comentar un borrador, proponer un cambio, unirse a un grupo de trabajo o acoger un ejercicio sobre el terreno.
Estado y uso. Las Nexus Standards son normas propuestas, elaboradas mediante un proceso abierto según NS-13 y publicadas para uso voluntario; no constituyen certificación, acreditación ni aprobación regulatoria, y su adopción sigue siendo una decisión del Global Standards Council y, en cada país, de su Consejo Nacional de Normas. Un UNI (Unique Nexus Identifier) identifica un artefacto; no lo certifica. Los nombres de los organismos de normalización y de sus normas pertenecen a sus titulares y se usan solo para identificar los documentos; aquí no se reproduce ningún texto de una norma externa. Nexus Standards no está afiliada a ningún organismo de normalización aquí nombrado, ni respaldada o certificada por él.
Licencias: CC BY 4.0 para el texto de los estándares, los registros, los esquemas y los datos; Apache-2.0 para el código de referencia. Los estándares externos se citan por nombre, número y enlace, conforme a sus propias licencias. Los datos, bibliotecas y fuentes tipográficas de terceros conservan sus propias licencias: véanse los Avisos de terceros.