Skip to content

NXS · Foundations

NS-14 conformance and crosswalk to external standards, explained for implementers

NS-14 proposes how a Nexus artefact states its relation to external standards without copying them or overclaiming. This explainer covers the six relations, how precise a crosswalk can be, how claims are displayed, marks and the register.

As of
3 November 2026
Lees
10 minutes
Bewyse
15 sources, cited in order
Status
Proposed standard
Code
NS-14 · Conformance and crosswalk to external standards
NEXUS TWIN · WF-1 · NETWORKSEED d8c41a28NXS-MAIN.STANDARD.NS-14xyzSCHEMATIC · NETWORKST-02 · 0.242 0.246ST-03 · 0.616 0.494
WF-1 · network Schematic wireframe twin (network, decision under uncertainty). An illustration, not data.

Status and scope

A proposed standard. It is not adopted, approved or certified by any authority.

Code
NS-14 · Conformance and crosswalk to external standards
Omvang
How a Nexus artefact or context states, evidences and displays its relation to external standards.
Applies to
Every Nexus standard, artefact, context or page that names an external standard.
  1. 1 Verhoudings
  2. 2 Conformance claims
  3. 3 Display and marks
  4. 4 Register
  5. 5 Rules

01What NS-14 conformance and crosswalk is

What NS-14 conformance and crosswalk is

NS-14 conformance and crosswalk is the proposed Nexus Standard titled Conformance and crosswalk to external standards. Its identifier is NXS-STD-ST-000013 and its current version is 0.1.0, catalogued on 16 October 2026 1. The text is on the NS-14 page.

The page describes NS-14 as the nexus of standards in practice. It sets how a Nexus artefact or context states, evidences and displays its relation to external standards from bodies such as ISO, IEC, NIST, OGC, W3C, the UN system and sector regulators 1. It does this under three limits: no reproduction of their text, no overclaiming of equivalence and no use of their marks as part of a Nexus name 1.

NS-14 rests on NS-0, whose tenth principle it applies to marks, and works with NS-11, which supplies the attestations behind any claim 1,2,3. It is a preparatory working draft circulated for comment on 17 October 2026, and is not for implementation 1.

02Why relations to other standards need rules

Why relations to other standards need rules

Any new standard sits among existing ones. Readers want to know whether it replaces, repeats, narrows or extends what they already use. Loose wording here causes real harm. A page that says a product is aligned with a well-known standard may be read as a claim of formal conformity, when in fact nobody has tested anything.

The WTO's principles for international standards ask bodies to avoid duplicating or overlapping with the work of other international standardising bodies, through cooperation and coordination 4. Reusing what exists, and saying precisely how, is the practical side of that principle. NS-14 turns it into a vocabulary of relations, each tied to evidence, so that a reader can see what kind of link is claimed and what supports it 1.

03The six relations

The six relations

Clause 1 defines six relations and the evidence each requires 1. Cite means the Nexus Standard refers to the external standard as context; the evidence is its URL and identifier in the register. Profile means the Nexus Standard constrains or specialises an open external standard, and conformance is tested against that standard's own validator where one exists. NS-14 names STAC, DCAT, PROV-O, DataCite and CAP as examples 1.

Crosswalk means elements of the external standard map to Nexus elements such as clauses or record fields. The evidence is a crosswalk table in the register, and each row cites the external clause by number, never by text 1. Adopt means the ecosystem uses the external standard as it is for a function. NS-14 names ISO 3166, SPDX, ORCID and ROR, and the evidence is validation of values against the external scheme 1.

Extend means Nexus adds machine-readable, real-time or provenance elements that the external standard lacks. The extension is a Nexus clause or field, and the external standard is cited as the baseline. Gap means no external standard covers the concern, so Nexus specifies it, backed by a gap statement in the landscape study 1.

Fig. 01Six ways to relate to an external standard

Six ways to relate to an external standard Six columns: cite with a register URL; profile tested by the external validator; crosswalk with a table citing clause numbers; adopt with value validation; extend with a Nexus clause; gap with a gap statement. CiteURL and identifierProfileExternal validatorKruisverwysingTable by clausenumberAdoptValues validatedExtendNexus clause orveldGapingGap statement
Relations as published in NS-14 clause 1 1.1Sources: Nexus Standards, NS-14 clause 1. Figure CC BY 4.0. As of 3 November 2026.
Figure 1 in words

Column 1, cite: the external standard is context; evidence is its URL and identifier in the register. Column 2, profile: Nexus constrains an open standard; tested with its own validator where one exists. Column 3, crosswalk: elements map to Nexus clauses or fields; a register table cites clauses by number. Column 4, adopt: used as it is; values validated against the scheme. Column 5, extend: Nexus adds elements the standard lacks; the standard is the baseline. Column 6, gap: nothing covers the concern; Nexus specifies it.

04The relations in practice

The relations in practice

The named examples show how different the relations are. A profile narrows a standard that already exists. The Common Alerting Protocol, an OASIS Standard since 1 July 2010, is a simple but general format for exchanging all-hazard emergency alerts and public warnings over all kinds of networks 5. A profile of CAP would keep the format and add constraints, so any message that meets the profile is still a valid CAP message.

The same holds for geospatial and catalogue data. STAC offers a common structure for describing and cataloguing spatiotemporal assets 6, and the W3C Data Catalog Vocabulary has been a Recommendation since 22 August 2024 7. A Nexus dataset profile can require extra fields while leaving the base format intact.

Adoption is simpler still: the external scheme is used as it is. SPDX, whose specification is published as ISO/IEC 5962:2021 and whose current version is 3.0 8, maintains the SPDX License List, which enables identification of licences by short identifiers 9. ORCID provides persistent identifiers for researchers as part of the wider digital infrastructure for sharing research information 10. Under NS-14, adopting these means validating values against the scheme, not redefining them 1.

A crosswalk sits between the two. The DataCite Metadata Schema 4.5, released on 22 January 2024, defines resource and relation types 11, and a Nexus record field can be mapped to one of them in a register table without either scheme changing.

05How precise a crosswalk can be

How precise a crosswalk can be

A crosswalk row says that one element corresponds to another, but correspondence comes in degrees. The W3C SKOS Reference, a Recommendation of 18 August 2009, offers a useful vocabulary for this 12. Its exactMatch property signals a high degree of confidence that two concepts can be used interchangeably across a wide range of applications. Its closeMatch property links concepts similar enough to be used interchangeably in some applications. Its broadMatch and narrowMatch properties state a hierarchical link 12.

NS-14 version 0.1.0 does not name SKOS or require a degree on each row 1. Readers of any crosswalk should still ask which kind of match is meant, because a close or broader match is not an equivalence. NS-14's ban on overclaiming equivalence points the same way 1.

Fig. 02How strong is a match?

How strong is a match? A ladder of three mapping strengths: broader or narrower match, close match usable interchangeably in some applications, and exact match usable interchangeably across a wide range. 01Broad or narrow matchHierarchical link02Close matchInterchangeable in some uses03Exact matchInterchangeable widely
Mapping properties as defined in the SKOS Reference 12. NS-14 version 0.1.0 does not yet require a degree on each crosswalk row 1.12,1Sources: W3C, SKOS Reference; Nexus Standards, NS-14. Figure CC BY 4.0. As of 3 November 2026.
Figure 2 in words

Three rising steps. Broad or narrow match: a hierarchical link between concepts. Close match: similar enough to use interchangeably in some information retrieval applications. Exact match, highlighted: a high degree of confidence that the concepts can be used interchangeably across a wide range of applications.

06Conformance claims and how they are shown

Conformance claims and how they are shown

Clause 2 sets the one route by which a context or artefact may claim a relation to an external standard 1. The claim must go through a clause set under NS-10 that cites that standard, and the clause set must be evaluated under NS-11 1. Prose alone is never enough (rule NS14-R2) 1.

The display wording is fixed. A claim reads as implements clauses derived from the named standard, followed by a count in the form n of m current PASS, with the identifiers of the attestations behind it 1. The words compliant and certification-style claims appear only when quoting an authority decision, by reference, from the body entitled to make it (rule NS14-R3) 1.

The count form has a practical virtue. A reader sees at once how many clauses are covered, how many currently pass and that the figure can change. Under NS-11, each pass is a dated attestation by a named evaluator, so the count can be traced to its evidence 3.

07Where another body runs its own certification

Where another body runs its own certification

Clause 2 adds a further limit: where a body operates its own certification, Nexus conformance is explicitly not that certification 1. Some standards bodies do run such schemes. The OGC Compliance Program, for example, distinguishes certification from registration, and only an implementation that has demonstrated alignment through that programme may use the OGC compliance mark 13.

Under NS-14, passing Nexus clauses derived from an OGC standard says nothing about that mark. A reader who needs the external body's own conformity statement must go to that body 1,13.

08Display, marks and the register

Display, marks and the register

Clause 3 governs names. External standards are named by their official identifiers, with the body's name as a reference. No Nexus name, subsite, product or page may compose a body's mark into its own name (rule NS14-R4) 1. Pages that list crosswalks carry a notice that names and standards belong to their stewards 1. The reason is practical as well as legal. A name that folds in another body's mark can suggest a partnership or an approval that does not exist, and readers rarely check. Keeping marks out of names, and citing bodies only as references, leaves no room for that reading 1,2.

Clause 4 sets the register. It holds every external standard with its body, version, URL, domain, access model, relation and a verified flag. An unverified entry is displayed as unverified (rule NS14-R5) 1. Entries are append-only, and a superseded external version is kept with its successor noted 1. That matters because external standards move. DataCite, for instance, publishes documentation for version 4.7 of its metadata schema, which it dates to 2026 14. A register entry pinned to version 4.5 stays true about 4.5, and the newer version is recorded beside it rather than overwriting it.

Fig. 03From register to displayed claim

From register to displayed claim Four stacked layers: register entry, clause set citing the standard, attestations evaluated under NS-11, and the displayed claim as n of m current passes. 01Register entryVersion, relation, verified flag02Clause setCites the external standard03AttestationsEvaluated under NS-1104Displayed claimn of m current passes
Route as published in NS-14 clauses 2 and 4 1, with attestations under NS-11 3.1,3Sources: Nexus Standards, NS-14 and NS-11. Figure CC BY 4.0. As of 3 November 2026.
Figure 3 in words

Four layers from bottom to top. Register entry: body, version, URL, relation and verified flag. Clause set under NS-10: cites the external standard. Attestations under NS-11: one per clause, dated, by a named evaluator. Displayed claim, highlighted: implements clauses derived from the standard, n of m current passes, with attestation identifiers.

09The five rules in one place

The five rules in one place

Clause 5 condenses the standard into five rules 1. NS14-R1: no reproduction of external standard text; cite by identifier, clause number and URL. NS14-R2: relation claims come from the register and clause sets, never from prose. NS14-R3: compliant and certification-style wording appear only as quotations of an authority decision by reference. NS14-R4: marks of standards bodies are never part of a Nexus name. NS14-R5: unverified register entries are displayed as unverified.

10Differences and open questions

Differences and open questions

Three points are worth noting for implementers. First, NS-14 lists six relations but does not yet say how precise a crosswalk row must be, so two registers could record the same mapping at different strengths 1. Second, the profile relation relies on the external standard's own validator where one exists, and NS-14 does not yet say what happens where none exists 1. Third, the register is described, but its public view is not yet specified in the text 1.

These are matters a later version could settle through an NS-13 proposal 15.

11Who NS-14 serves and how to take part

Who NS-14 serves and how to take part

NS-14 serves readers who meet a Nexus artefact next to standards they already know: regulators, procurers, data stewards and engineers. It gives them a precise answer to the question of how the two relate, and a way to check it 1. It also protects the bodies whose work is cited, by keeping their text and marks out of Nexus material 1.

Changes follow the open process described on Develop a standard, and comments go through the contact form. The standards are published by The Global Centre for Risk and Innovation (GCRI) as Secretariat. The Global Risks Forum (GRF) and The Global Risks Alliance (GRA) take part as stakeholders like any other. Learners can study the subject in Risk Academy's Technology and Data course.

12Instruments named in or related to NS-14

The table lists external instruments that illustrate the NS-14 relations, as published on 3 November 2026. Each is maintained by its own issuer and applies on its own terms.

InstrumentNS-14 relation illustratedUitgawe
OASIS CAP 1.2Profile1 July 2010 5
W3C DCAT 3Profile22 August 2024 7
DataCite Metadata SchemaProfile or crosswalk4.5, 22 January 2024 11
SPDXAdopt3.0; ISO/IEC 5962:2021 8
ORCIDAdoptLive service 10
W3C SKOS ReferenceVocabulary for match strength18 August 2009 12
External instruments and the NS-14 relation each illustrates, as of 3 November 2026.

What this page does not claim: NS-14 is a proposed, preparatory working draft that its own page says is not for implementation, and no Nexus Standard has been adopted by the Global Standards Council or any National Standards Council. The examples of relations are illustrations; no profile, crosswalk or adoption described here has been evaluated. W3C, OASIS Open, DataCite, the SPDX project, OGC, the STAC community, ORCID and the WTO maintain their own instruments; Nexus Standards has no affiliation with any of them, and Nexus conformance is not any body's own conformity scheme.

Vrae

Vrae en antwoorde

What are the six NS-14 relations?

Cite, profile, crosswalk, adopt, extend and gap. Each says how a Nexus element relates to an external standard and what evidence supports it.

How is a relation to an external standard displayed?

As implements clauses derived from the standard, with a count of n of m current passes and the attestation identifiers behind it.

Can a Nexus page say it complies with an external standard?

Only by quoting, with a reference, an authority decision from the body entitled to make it. Otherwise the count of current passes is shown.

Does NS-14 reproduce external standards?

No. External standards are cited by identifier, clause number and URL, and their text is never reproduced.

What is NS-14's own status?

Proposed. Version 0.1.0 is a preparatory working draft circulated for review and comment, not for implementation, and changes go through NS-13 proposals.

Voorwaardes

Woordelys

Profile
A specialisation of an external standard that adds constraints while staying valid under it.
Kruisverwysing
A table mapping elements of one standard to elements of another, citing clauses by number.
Adopt
Use of an external scheme as it is, with values validated against it.
Gaping
A concern no external standard covers, which Nexus then specifies.
Mark
A name or logo that identifies a standards body or its scheme; never part of a Nexus name.

Comment on this draft

Comments are taken clause by clause, with the exact text you propose and your evidence, through the comment form on this site.

Bronne

References

15 sources, numbered in the order they are first cited
  1. Nexus Standards (2026-10-16). NS-14: Conformance and crosswalk to external standards (proposed). nexustandards.com. Accessed 2026-11-03.
  2. Nexus Standards (2026-10-16). NS-0: Constitution and principles (proposed). nexustandards.com. Accessed 2026-11-03.
  3. Nexus Standards (2026-10-16). NS-11: Verification and monitoring (proposed). nexustandards.com. Accessed 2026-11-03.
  4. World Trade Organization (WTO) (2000). Principles for the Development of International Standards, Guides and Recommendations. www.wto.org. Accessed 2026-11-03.
  5. OASIS Open (2010-07-01). Common Alerting Protocol Version 1.2. docs.oasis-open.org. Accessed 2026-11-03.
  6. STAC community (2026-11-03). STAC: SpatioTemporal Asset Catalogs. stacspec.org. Accessed 2026-11-03.
  7. World Wide Web Consortium (W3C) (2024-08-22). Data Catalog Vocabulary (DCAT), Version 3. www.w3.org. Accessed 2026-11-03.
  8. SPDX project, The Linux Foundation (2026-11-03). SPDX Specifications. spdx.dev. Accessed 2026-11-03.
  9. SPDX project, The Linux Foundation (2026-11-17). SPDX License List. spdx.org. Accessed 2026-11-17.
  10. ORCID (2026-11-03). About ORCID. info.orcid.org. Accessed 2026-11-03.
  11. DataCite e.V. (2024-01-22). DataCite Metadata Schema 4.5. schema.datacite.org. Accessed 2026-11-03.
  12. World Wide Web Consortium (W3C) (2009-08-18). SKOS Simple Knowledge Organization System Reference. www.w3.org. Accessed 2026-11-03.
  13. Open Geospatial Consortium (OGC) (2026-11-03). OGC Compliance Program. www.ogc.org. Accessed 2026-11-03.
  14. DataCite e.V. (2026). DataCite Metadata Schema 4.7 documentation. datacite-metadata-schema.readthedocs.io. Accessed 2026-11-17.
  15. Nexus Standards (2026-10-16). NS-13: Standards development process (proposed). nexustandards.com. Accessed 2026-11-03.

Record

Editorial record

Facts as of 3 November 2026. The NS-14 text, version and status were read on its page that day, and every external instrument was checked at its issuer the same day. The ISO and ROR sites refused automated access, so ISO 3166 and ROR are named only as NS-14 names them. This page is reviewed at least every 180 days and whenever NS-14 changes version or status. Text, visuals and data on this page are licensed CC BY 4.0.

Published by the Standards desk, Nexus Standards. Drafted with AI assistance under the Nexus editorial constitution. To report an error, use the corrections page; corrections are dated and listed here.

Cite this article

Standards desk, Nexus Standards (2026, November 3). NS-14 conformance and crosswalk explained. Nexus Standards. https://nexustandards.com/ns-14-conformance-and-crosswalk-to-external-standards/

Republish

Republish or translate this article free of charge, in print or online, under CC BY 4.0: keep the byline and Nexus Standards, link to the original and note any change. Figures, maps and twins made by the institutions carry the same licence; third-party data keeps its own credit line.

Attribution to paste
<p>NS-14 conformance and crosswalk to external standards, explained for implementers — Standards desk, Nexus Standards, Nexus Standards. First published 3 November 2026 at <a href="https://nexustandards.com/ns-14-conformance-and-crosswalk-to-external-standards/">https://nexustandards.com/ns-14-conformance-and-crosswalk-to-external-standards/</a>. Republished under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/).</p>

Share

EmailLinkedInBlueskyMastodon