Cities and the built environment: standards that apply
The 6 standards listed for cities and the built environment in the registry, each with its status, UNI (Unique Nexus Identifier) and the rules stated in its text.
- Nexus Standards: NS-0, NS-3, NS-5, NS-9, NS-10, NS-11.
- Open standards: Sendai Framework for Disaster Risk Reduction 2015–2030; Making Cities Resilient 2030 resilience roadmap and scorecard; OGC CityGML 3.0; OGC API – Features; SpatioTemporal Asset Catalog (STAC) 1.0.
- Data and feeds: Global Human Settlement Layer; WorldPop gridded population; Overture Maps buildings theme; OpenStreetMap; World Development Indicators.
- Couples with: Construction and real estate; Water utilities and basins; Public sector and government; Energy utilities and grids.
- Nexus Standards
- 6
- NS-0, NS-3, NS-5
- ستانداردە کراوەکان
- 5
- named, never copied
- Data and feeds
- 5
- listed for reference
- پەیوەستبوونەکان
- 4
- with other areas
| یاسا | دەق |
|---|---|
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 | Machine-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-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 | Honest · 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-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ەکانی تۆماری مەترسی (ڕێزمان، خشتەی گواستنەوەی کۆن، دەسەڵاتی تەرخانکردن)
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.
ستانداردی وێنە، نەخشە و بینراوکردن (لەگەڵ کیتی UI/UX)
Status proposed · earth observation and digital twins; visual composition and workflows · NXS-STD-ST-000011.
| یاسا | دەق |
|---|---|
NS5-R1 | Every visual artefact shall carry a UNI in its metadata and in its caption. |
NS5-R2 | Every rendered value shall trace to record UNIs and to a time of evaluation. |
NS5-R3 | Missing, degraded and insufficient-evidence states shall be rendered explicitly; no such state shall be coerced to a value. |
NS5-R4 | Licence-restricted or withheld features shall be counted and declared on the figure or map. |
NS5-R5 | Every visual artefact shall carry the accessibility and cartographic declarations of section 4 that apply to it. |
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 is set and the status becomes 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 is the default for blocking clauses in production contexts. |
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. |
سەلماندن و چاودێری (بەڵگە، گواهییەکان، چاودێریی گونجان لەگەڵ zero-trust)
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 cities and the built environment?
What does a rule identifier such as NS1-R5 denote?
Around cities and the built environment.
Shape the standards for cities and the built environment.
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 بۆ کۆدی سەرچاوە. ستانداردە دەرەکییەکان بە ناو، ژمارە و بەستەر لە ژێر مۆڵەتەکانی خۆیاندا ئاماژەیان پێدەدرێت. داتا، کتێبخانە و فۆنتەکانی لایەنی سێیەم مۆڵەتەکانی خۆیان دەپارێزن: بڕوانە ئاگادارییەکانی لایەنی سێیەم.