- Nexus Standards: NS-0, NS-1, NS-3, NS-9, NS-10, NS-11.
- Open standards: OGC API – Features; NGFS climate scenarios; NIST Cybersecurity Framework 2.0; Recommendations of the Task Force on Climate-related Financial Disclosures; GHG Protocol Corporate Accounting and Reporting Standard.
- 数据和数据流:全球发电厂数据库;NASA Black Marble 夜间灯光(VNP46);Ember 电力数据;ENTSO-E 透明度平台;EIA 开放数据 API。
- 关联领域:水;关键基础设施与关键实体;气候;空间天气、频谱与授时。
- Nexus Standards
- 6
- NS-0, NS-1, NS-3
- 开放标准
- 5
- 列出名称,绝不复制
- 数据和数据流
- 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 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 | 诚实 · 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 以章节而非规则表的形式说明其要求。
| 规则 | 文本 |
|---|---|
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. |
问答。
这些就是能源风险的全部规则吗?
NS1-R5 这类规则标识符表示什么?
Around energy risk.
塑造能源风险的标准。
邀请政府、监管机构、标准机构、行业、学术界和社区在首个正式版本(目标为 2030 年)发布前共同完善该目录:对草案提出意见、提出变更建议、加入工作组或承办实地演练。
状态与用途。Nexus Standards 是根据 NS-13 通过公开流程制定、供自愿使用而发布的提议标准;它们不构成认证、认可或监管批准,采用与否仍由全球标准委员会以及各国的国家标准委员会决定。UNI(唯一 Nexus 标识符)用于识别制品,不对其进行认证。标准机构及其标准的名称归其管理者所有,仅用于识别相关文件;此处不转载任何外部标准的文本。Nexus Standards 与此处提及的任何标准机构均无隶属关系,也未获其认可或认证。
许可:标准文本、登记册、模式和数据采用 CC BY 4.0;参考代码采用 Apache-2.0。外部标准按名称、编号和链接引用,并适用其各自许可。第三方数据、库和字体保留其各自许可:见第三方声明。