Nexus StandardsSpace weather, spectrum and timing risk standardsCrosswalk
Space weather, spectrum and timing risk

Space weather, spectrum and timing risk: crosswalk to external standards

The external standards in the crosswalk domains of space weather, spectrum and timing risk, from the register, with the relation each has to the Nexus Standards; every row links the source body, and relations are evidenced by attestations with their own UNIs (Unique Nexus Identifier). Names of standards bodies and their standards belong to their stewards and are used only to identify the documents; no text of an external standard is reproduced here. Nexus Standards is not affiliated with, endorsed by or certified by any standards body named here.

Back to Space weather, spectrum and timing risk All subsites
Crosswalk graph · space weather, spectrum and timing riskFrom the registry
Space weather, spectrum and timing risk: the crosswalk54 nodes on four orbits (Nexus Standards and consumers inside, then domains, external standards and issuing bodies) joined by 64 register links.
Nexus StandardsDomainsExternal standardsIssuing bodiesConsumers

3 Nexus Standards · 2 domains · 28 external standards · 20 issuing bodies · 1 consumers. Relations are register entries (adopt, profile, crosswalk, cite), never compliance claims; names belong to their stewards.

Crosswalk graph54 nodes and 64 links from registry/external-standards.yaml, registry/subsites.yaml and registry/consumers.yaml. Relations (adopt, profile, crosswalk, cite) are register entries, never compliance claims.

01Geospatial and Earth observation

Geospatial and Earth observation: 13 entries.

StandardBodyVersionRelationAccessVerified
ISO 19115-1:2014 Geographic information - Metadata - Part 1: FundamentalsISO/TC 2112014 with Amd 1:2018 and Amd 2:2020compatibility profile (restricted)paywalledverified
ISO 19157-1:2023 Geographic information - Data quality - Part 1: General requirementsISO/TC 2112023 (April 2023; replaces ISO 19157:2013)compatibility profile (restricted)paywalledverified
OGC API - Features - Part 1: CoreOpen Geospatial Consortium1.0.1 (17-069r4 corrigendum); Parts 2 and 3 also 1.0.1adoptopenverified
OGC API - Records - Part 1: CoreOpen Geospatial Consortium1.0 (20-004r1, International Standard)crosswalkopenunverified
SpatioTemporal Asset Catalog (STAC) specificationSTAC community; OGC Community Standard 25-0041.1.0 (OGC Community Standard); core text CC BY 4.0adoptopenverified
OGC GeoPackage Encoding StandardOpen Geospatial Consortium1.4.0 (12-128r19, 6 February 2024)citeopenverified
OGC SensorThings API Part 1: SensingOpen Geospatial Consortium1.1 (18-088); Part 2 Tasking Core 1.0; STAplus 1.0crosswalkopenunverified
RFC 7946 The GeoJSON FormatIETFProposed Standard (August 2016)adoptopenverified
UN-GGIM Integrated Geospatial Information Framework (IGIF)UN Committee of Experts on Global Geospatial Information Managementnine strategic pathwaysciteopenunverified
International Committee on Global Navigation Satellite Systems (ICG) interoperability and performance workUN Office for Outer Space Affairscurrentciteopenunverified
OGC SensorML encoding standardOGC2.0adoptopenunverified
CCSDS space data system standardsConsultative Committee for Space Data Systemscurrentciteopenunverified
OGC GeoSPARQL - A Geographic Query Language for RDF DataOGC1.1adoptopenunverified

Unverified entries rest on a secondary source for at least one field; the register says which.

02Canvas

Crosswalk evidence.

Canvas · crosswalk evidenceDesign, not a record
Space weather, spectrum and timing risk: how a relation to an external standard is evidencedRegister entries for the area by domain and relation; NS-14 says what evidence each relation needs and how a claim may be displayed. Names and standards belong to their stewards.

Fig.Register relations for the area and the evidence NS-14 requires before a claim is displayed. Design, not a record.

03Critical infrastructure

Critical infrastructure: 15 entries.

StandardBodyVersionRelationAccessVerified
IEC 62443 series Security for industrial automation and control systemsIEC TC 65 with ISA (ISA/IEC 62443)series; IEC 62443-2-1:2024 published 7 August 2024; horizontal standard since 2021citepaywalledverified
ISO 55000:2024 Asset management - Vocabulary, overview and principlesISO/TC 2512024 (edition 2, July 2024)citepaywalledverified
ISO 10218 Robotics - Safety requirements for industrial robotsISO/TC 2992025citepaywalledunverified
ISO 13482:2014 Robots and robotic devices - Safety requirements for personal care robotsISO/TC 2992014citepaywalledunverified
IEC 61508 Functional safety of electrical, electronic and programmable electronic safety-related systemsIEC TC 652010compatibility profile (restricted)paywalledunverified
IEEE 1588 Precision Clock Synchronization Protocol for Networked Measurement and Control SystemsIEEE2019citepaywalledunverified
ITU-T G.8271 Time and phase synchronization aspects of telecommunication networksITU-T SG15currentciteopenunverified
ITU Radio RegulationsITU-R2024citeopenunverified
ISO 37120:2018 Sustainable cities and communities - Indicators for city services and quality of lifeISO/TC 2682018compatibility profile (restricted)paywalledunverified
ISO 37123:2019 Sustainable cities and communities - Indicators for resilient citiesISO/TC 2682019compatibility profile (restricted)paywalledunverified
ISO 19650 Organization and digitization of information about buildings and civil engineering works (BIM)ISO/TC 59/SC 132018citepaywalledunverified
IEC 61511 Functional safety - Safety instrumented systems for the process industry sectorIEC TC 652016compatibility profile (restricted)paywalledunverified
Directive 2012/18/EU on the control of major-accident hazards involving dangerous substances (Seveso III)European Parliament and Council2012citeopenunverified
ICAO Annex 19 Safety ManagementInternational Civil Aviation Organization2nd editioncitepaywalledunverified
International Safety Management (ISM) CodeInternational Maritime Organizationcurrentcitepaywalledunverified

Unverified entries rest on a secondary source for at least one field; the register says which.

04Relations

What each relation means and what evidences it.

RelationMeaningEvidence
citeThe Nexus Standard refers to the external standard as context.URL and identifier in the register.
profileThe Nexus Standard constrains or specialises an open external standard (STAC, DCAT, PROV-O, DataCite, CAP).Conformance tests against the external standard's own validator where one exists.
crosswalkElements of the external standard map to Nexus elements (clauses, record fields).A crosswalk table in the register entry; each row cites the external clause by number, never by text.
adoptThe ecosystem uses the external standard as-is for a function (ISO 3166, SPDX, ORCID, ROR).Validation of values against the external scheme.
extendNexus adds machine-readable, real-time or provenance elements the external standard lacks.The extension is a Nexus clause or field; the external standard is cited as the baseline.
gapNo external standard covers the concern; Nexus specifies it.The gap statement in the landscape study.
05Learn and apply

Where Space weather, spectrum and timing risk is taught, worked on and run.

Risk Academy disciplines that teach Space weather, spectrum and timing risk, with their courses; the GCRI Canada, The Global Risks Forum (GRF) and The Global Risks Alliance (GRA) subsites that carry those disciplines; and the Nexus Foundry systems the standards name. Mappings are proposed for review (Risk Academy standards map, 2026-10-17); a link says a page on the same subject exists, never an endorsement or a conformance statement; framework names in course titles are named and linked, never reproduced.

Risk Academy

Disciplines and courses

06Questions

Questions and answers.

Does a crosswalk make a space weather, spectrum and timing risk artifact conformant to these standards?
No. A crosswalk is a mapping, not a conformance statement. A relation may be displayed only as clauses derived from the external standard and their current results, never as a compliance or certification statement unless the body entitled to decide has done so.
Why do some relations read compatibility profile (restricted)?
The standard is paywalled. Nexus Standards do not reproduce its text; a compatibility profile of it is built on simulated data and kept on restricted pages, and it is activated publicly only after an institutional arrangement with the issuing body is recorded (owner decision of 2026-10-16, counsel review pending).
Why are some entries unverified?
An unverified entry rests on a secondary source for at least one of name, body, version or year; NS14-R5 requires it to be shown as unverified.
Related

Around Space weather, spectrum and timing risk.

Nexus Standards

Shape the standards for space weather, spectrum and timing risk.

Every standard here is proposed. Changes enter as proposals under NS-13; conformance is shown by attestations under NS-11; nothing on this site is a certification, an approval or a readiness statement.

Propose a change See contact routes

Nexus Standards documents CC BY 4.0 · tooling Apache-2.0 · counsel review pending (DEC-2026-10-16-NEXUS-STANDARDS-OPEN-LICENCE). External standards are named and linked under their own licences; a UNI (Unique Nexus Identifier) identifies, it never certifies. · Generated from the Nexus Standards corpus at commit 437ae044c5cb (2026-10-17); proposed and open.

Skip to toolbar