Skip to content
StandardsTrust, Verification and AssuranceInfrastructure services
Area · proposed

Mfululizo wa majaribio ya ulinganifu

Maintains one open test corpus per standard and conformance class, run by three runners (browser test environment, continuous-integration action, hosted validator), with abstract tests tied to rule anchors, UNIs and SWHIDs, and external validators invoked for profiled standards. Test results are evidence, not certificates. Each artefact of the area carries a UNI (Unique Nexus Identifier).

Mfululizo wa majaribio ya ulinganifu
What this area is built from: the Nexus Standards it applies, the open standards it names and the data and feeds it reads, then the areas its record couples it with (marked).Source: the Nexus Standards registry: the area record.
  • Nexus Standards: NS-11, NS-13, NS-14.
  • Open standards: OGC API – Features (with OGC executable test suite pattern); JSON Schema 2020-12; SpatioTemporal Asset Catalog (STAC); SWHID v1.2.
  • Data and feeds: STAC JSON Schemas; OGC TEAM Engine executable test suites; web-platform-tests.
  • Couples with: Open standards development; Verification services; Developers and APIs.
Nexus Standards
3
NS-11, NS-13, NS-14
Open standards
4
named, never copied
Data and feeds
3
listed for reference
Couplings
3
with other areas
UNI
requested · allocation in progress
Hali
Proposednot yet in the catalogue
Last reviewed
area profile
Cite this page

Nexus Standards (2026). Conformance test suites: area brief, Trust, Verification and Assurance programme. Proposed. https://nexustandards.com/assurance/conformance-test-suites/. Last reviewed 17 October 2026.

Download the profile

Files include the credits and the licence statement and are generated in the browser; no data is transmitted. Downloads require JavaScript.

01Wigo

Scope and boundaries

An area of the Trust, Verification and Assurance programme (infrastructure services). The area profile sets out 4 matters in scope and 2 matters addressed by other areas.

In scope 4

  • Test corpus structure, rule anchors and corpus digests
  • Browser test environment, continuous-integration action and hosted runner
  • External validator integration (STAC, DCAT-AP, IATI, SDMX, CAP)
  • Implementation reports for exit from the Candidate stage

Out of scope 2

  • Issuing certificates or badges for passing tests
  • Testing closed standards on actual data (restricted profiles use synthetic data)

Jurisdictions Application in each jurisdiction is a national decision, taken by the National Standards Council (NSC) with the competent national authorities.

02Standards architecture

Foundation, referenced and implementing layers

The standards architecture of this context, from the foundation standards to the open standards referenced (grouped by type of relation) and the services and data sources that build on them.

The interactive view requires JavaScript; the sections below present the same records.

03Mchakato

The service pipeline

A request reaches the service with an explicit context; inputs are identified (NS-1) and validated against OGC API – Features (with OGC executable test suite pattern); the service processes them and writes records with provenance; results are published, resolved and monitored, and a correction flows back through the same path. Nexus Standards applied: NS-14, NS-11, NS-13. 8 operations in 5 phases, built from the area profile: the rows carry its own data sources, indicators, open standards, couplings and, where listed, hazards, and each operation names the rules it implements (11). Records and artefacts are cited by UNI (Unique Nexus Identifier) and version.

Kichunguzi cha michakato · Standards · ratibu na sahihisha

Mzunguko wa maisha wa kiwango

Hatua 17Awamu 6

Standards · ratibu na sahihisha

Mzunguko wa maisha wa kiwango

Mzunguko wa maisha wa kiwango · Njia ya NS-13 · Njia za michango · Njia ya IETF · Njia ya W3C · Njia ya OGC · Njia ya OASIS · Hatua za ISO na IEC · Ulinganifu · Mzunguko wa maisha wa rekodi · Uelekezaji · Ufuatiliaji.

Matokeo ya mzunguko huwa mapendekezo ya mabadiliko, Baraza la Viwango la Dunia hupitisha baada ya mwito wa mwisho wa umma, na kila nchi huamua upitishaji wake.

  1. 01 Elekeza misheni

    1. 01Elekeza misheni kwenye viwango na wasifuHatua · Nexus StandardsNexus Standards huelekeza kila misheni inayopendekezwa kwenye viwango na wasifu vinavyotumika.
  2. 02 Wasifu na ulinganifu

    1. 02Kusanya wasifu wa misheniHatua · Nexus StandardsNexus Standards hukusanya wasifu wa misheni na hurekodi upitishaji wowote wa kitaifa ambao misheni hutegemea.
    2. 03Thibitisha matokeo ya ujenzi dhidi ya wasifuHatua · Nexus StandardsNexus Standards huthibitisha matokeo ya ujenzi dhidi ya wasifu ulioundwa na kurekodi ushahidi.
    3. 04Fuatilia ulinganifu na urekodi ushahidi uliofungwaHatua · Nexus StandardsWakati wa Wiki ya Utekelezaji Nexus Standards hufuatilia ulinganifu na kurekodi mikengeuko.
  3. 03 Mapendekezo na mapitio

    1. 05Mikengeuko na marekebisho huwa mapendekezo ya mabadilikoHatua · Nexus StandardsMikengeuko huwa mapendekezo ya mabadiliko, na marekebisho hurekodiwa kama mabadiliko kwa ushahidi.
    2. 06Matokeo ya mzunguko huwa mapendekezo ya mabadilikoHatua · Nexus StandardsMatokeo ya mzunguko huwa mapendekezo ya mabadiliko: matokeo ya mbinu na masahihisho kutoka Ripoti (F06) na vipengele vya orodha kutoka Nexus…
    3. 07Andaa na urekebishe hadharaniHatua · Kamati na vikundi kaziKamati za kiufundi na vikundi kazi huandaa rasimu na kurekebisha viwango katika mchakato wazi wa NS-13.
    4. 08Pitia kuelekea uamuzi wa barazaHatua · Nexus StandardsNexus Standards huendeleza mapendekezo ya mabadiliko kupitia mapitio kuelekea uamuzi wa baraza.
  4. 04 Uamuzi wa Baraza

    1. 09Mwito wa mwisho wa ummaHatua · Baraza la Viwango la KimataifaBaraza la Viwango la Kimataifa hupitisha kwa wingi wa theluthi mbili baada ya mwito wa mwisho wa siku tisini.
    2. 10Kupitishwa kwa kiwango dunianiUamuzi · Global Standards CouncilBaraza la Viwango la Dunia huamua upitishaji wa kila kiwango baada ya mwito wa mwisho wa umma.
  5. 05 Chapisha na utambulishe

    1. 11Assign a UNI and publishStep · Secretariat (GCRI Canada)Nexus Standards assigns UNIs and deposits publications under the publisher’s process.
    2. 12UNI hutambulisha na kamwe haitoi chetiRekodi · Nexus StandardsKila kitu cha mwaka wa programu kina kitambulisho kimoja, UNI chini ya NS-1, ili kiweze kutajwa, kupewa matoleo na kutatuliwa.
    3. 13Chapisha mabadiliko yaliyopitishwa ya mwakaHatua · Nexus StandardsWakati wa upyaishaji Nexus Standards huchapisha mabadiliko yaliyopitishwa ya mwaka na hali ya upitishaji wa kitaifa.
  6. 06 Kupitishwa na kutumika kitaifa

    1. 14Kupitishwa kitaifa na Baraza la Viwango la KitaifaUamuzi · Baraza la Viwango la KitaifaBaraza la Viwango la Kitaifa la kila nchi huamua upitishaji wa kitaifa: kupitisha kama ilivyo, kupitisha kwa wasifu (NS-16), kurekebisha, au kurejelea tu.
    2. 15Viwango vilivyopitishwa hufikia kozi na matoleoHatua · Nexus StandardsKila kiwango au wasifu uliopitishwa huwa moduli ya kozi katika Risk Academy (F09), na viwango hutumika katika matoleo ya Reports (R1).
    3. 16Upitishaji ni wa mwisho kwa kila mamlaka ya kisheriaKiwango · Baraza la Kitaifa la ViwangoUpitishaji ni wa mwisho kwa kila mamlaka ya kisheria, na GSC haina kura ya turufu juu ya uamuzi wa kitaifa. Hakuna chombo cha kimataifa chenye kura ya turufu.
    4. 17Rekodi za kupitishwa kitaifaRekodi · Nexus StandardsWasifu wa misheni ulioundwa na rekodi za upitishaji wa kitaifa huenda kwa Foundry wakati wa maandalizi ya utayari (F08).

Nexus Standards · Nexus Standards (institution) · National Standards CouncilAn outline of the designed programme cycle, not a record of operation: no cycle has run and every programme is at service level R0. Every Nexus Standard is at the PROPOSED stage and nexustandards.com governs the text and status of each one. A UNI identifies and never certifies; a validator report is evidence for review, not a conformance claim.

The operations, as a table
Process · the service pipeline8 operations · 5 phases
StepPhaseOperationWhoDecision ruleRecordImplements
01RequestRequest (start). The service covers: Test corpus structure, rule anchors and corpus digests, Browser test environment, continuous-integration action and hosted runner and External validator integration (STAC, DCAT-AP, IATI, SDMX, CAP).a client, a person or a machinethe context is explicit in the request or on the record, never inferreda request naming its context and inputsNS16-R20
02RequestIdentify inputs (step). Every input is resolved before it is used; an unresolved input is a typed refusal.the serviceinputs are cited by UNI and versioninputs resolved to their UNIs and versionsNS1-R5, NS2-R2, NS0-P12
03ValidationValidate OGC API (gate). Open standards of this area: OGC API – Features (with OGC executable test suite pattern), JSON Schema 2020-12, SpatioTemporal Asset Catalog (STAC) and SWHID v1.2.the service’s validatorvalidated against the open standard’s own schema or validator where one existsa validation run against OGC API – Features (with OGC executable test suite pattern) and JSON Schema 2020-12NS14-R2
04ProcessingProcess (model). Processing is reproducible from the inputs, the method version and the configuration.the servicethe method and version are recorded with the resultBrowser test environment, continuous-integration action and hosted runnerNS12-R1
05ProcessingWrite records (record). Results are written append-only; a correction adds a version.the serviceevery result carries what it was derived fromresult records with provenance and a record UNINS0-P7, NS1-R3
06PublicationPublish and resolve (step). Results are discoverable and citable by UNI.the servicewrites return the allocated UNI; citations resolveresults reachable through the resolver, with the X-Nexus-UNI headerNS1-R5, NS2-R5
07UfuatiliajiMonitor (exercise). Data sources the service reads: STAC JSON Schemas, OGC TEAM Engine executable test suites and web-platform-tests. Data sources are listed for reference; live data is displayed once licence review is complete.the monitoring servicemonitoring records are observations with record UNIsobservations of availability, drift and W3C Process Document Implementation experienceNS11-R4
08UfuatiliajiCorrection (end). Products that used a corrected record are listed and recomputed.the data stewarda correction never overwrites; dependent results are replayeda correction record that reaches every dependent resultNS1-R3, NS2-R4

Table.Operations in walking order; each row names the phase, the operation, its actor, its decision rule, the record it leaves and the rule identifiers it implements. The table shows the process as specified; it does not report the status of any standard, proposal or record. Sources: OGC API – Features (with OGC executable test suite pattern) · JSON Schema 2020-12 · NS-14: Conformance and crosswalk to external standards · NS-11: Verification and monitoring.

04Consoles

Routing, monitoring and verification tools

05System model

How a shock travels through this system

A system model of this area built from the registry: 4 systems, 4 sectors, 9 controls, 3 feeds, 2 indicators. Select the components to include, choose an initiating hazard and run the scenario. Stress propagates through the hazard relations of the Nexus Hazard Standard (NHS-1), the exposure of each system, the recorded couplings and the sectors that carry the loss; adopted standards dampen transmission and live data sources support detection. All parameters are stated assumptions that the reader can adjust; results are illustrative scenario outputs for exercises and training, not forecasts or risk assessments.

Controls

  • NS-14 Ulinganifu na upatanisho na viwango vya nje
  • NS-11 Uthibitishaji na ufuatiliaji (ushahidi, uthibitisho, uchunguzi wa ulinganifu usio na imani)
  • NS-13 Mchakato wa kuandaa viwango (mapendekezo wazi, ukaguzi, matoleo, upitishaji)
  • NRS-S9 System profile: NXS-AAP (Anticipatory action and triggers)
  • NRS-C11 Ulinganifu, uthibitishaji na utunzaji wa viwango
  • NRS-S1 System profile: NXS-CMD (Integrated posture and executive synthesis)
  • NRS-S2 System profile: NXS-NST (Civilian common operating picture)
  • NRS-S3 System profile: NXS-DSS (Decision cases and deliberation)
  • NRS-S4 System profile: NXS-COR (Compute, nodes and runtimes)

Observation

  • STAC JSON Schemas (listed for reference)
  • OGC TEAM Engine executable test suites (listed for reference)
  • web-platform-tests (listed for reference)
  • Two independent implementations per feature (pattern for CANDIDATE exit)
  • Metadata complies with a community standard
06Miunganiko ya kimfumo

Miunganiko ya kimfumo

3 couplings link this area to other areas and programmes, each with the mechanism of the link.

  1. Open standards developmentFoundations and GovernanceA standard enters the Proposed stage only with a test for every MUST rule, and the Candidate stage only when two independent implementations pass.
  2. Verification servicesTrust, Verification and AssuranceThe hosted validator runs the same corpus to produce EVALUATED attestations.
  3. Developers and APIsOpen Infrastructure and DevelopersSoftware development kits and command-line tools are accepted only when they pass the corpus and the cross-language digest vectors.
07Viwango

Standards that apply

The area profile lists 3 Nexus Standards. Each is a proposed standard under development.

  1. 01

    NS-14 · Conformance and crosswalk to external standards

    Status: proposed · 5 requirements stated. Read NS-14.

  2. 02

    NS-11 · Verification and monitoring (evidence, attestations, zero-trust conformance observation)

    Status: proposed · 6 requirements stated. Read NS-11.

  3. 03

    NS-13 · Standards development process (open proposals, review, versioning, adoption)

    Status: proposed · 5 requirements stated. Read NS-13.

09Data sources

Data sources

3 data sources named in the area profile, each with provider, licence, update frequency and delivery path.

Data sources

Data sources are listed for reference; live data is displayed once licence review is complete.

Hai
0
on completion of licence review
Listed in the data register
0
licence terms recorded
Proposed for the register
3
licence terms to be recorded
Delivery
0 governed service · 0 plugin · 1 browser · 2 snapshot · 0 listed for reference
proposed paths in order of preference: governed data service, plugin, direct browser read, build-time snapshot; sources whose terms do not permit reuse are listed for reference only
  • OGC TEAM Engine executable test suitesfor reference.

    OGC · per release

    Apache-2.0 (test suite code)

    direct browser readproposed for the data register.

  • STAC JSON Schemasfor reference

    STAC community · per release

    Apache-2.0

    build-time snapshotproposed for the data register

  • web-platform-testsfor reference

    web-platform-tests project · continuous

    BSD 3-Clause

    build-time snapshotproposed for the data register

10Kikundi kazi

Working group charter

A proposed charter for this area, open to institutions and experts.

Wigo

Maintain the test corpus, runners and implementation reports.

Institutions and experts are invited to charter this working group under NS-13 by filing a public change record. National Working Groups (NWGs) contribute national inputs and field exercises through their National Nexus Consortium (NNC).

Deliverables · 3
  1. Test corpus for each proposed edition
  2. Three runners with identical results on the fixture set
  3. Implementation report template
Liaison targets · 3
  • OGC Compliance Program liaison sought
  • web-platform-tests maintainers liaison sought
  • STAC community liaison sought
11Viashiria

Viashiria

The area profile names 2 indicators, each with its framework and code.

12Utayari

Evidence, recognition and capital pathways

What each institution of the ecosystem draws from this area: The Global Centre for Risk and Innovation (GCRI Canada), as Secretariat, for evidence; The Global Risks Forum (GRF) for recognition; and The Global Risks Alliance (GRA) for capital.

Evidence pathway

GCRI Canada

GCRI Canada runs the corpus in its analytical workflows and cites the corpus digest and version with results.

Read the evidence pathway

Njia ya utambuzi

Global Risks Forum (GRF)

GRF lists implementation statements as submitted, with their test evidence and no ordering by score.

Read the recognition pathway

Njia ya mtaji

Global Risks Alliance (GRA)

GRA reads test results as evidence about a version at a point in time, not as a lasting guarantee.

Read the capital pathway

Each institution determines under its own rules what it accepts as evidence; a pathway reading is neither an approval nor investment advice.

13Research questions

Open research questions

2 questions identified as priorities for the working group.

  1. Tests for runtime behaviour (latency, availability) that are fair across very different hosts.
  2. Keeping external validators’ versions pinned without lagging behind their fixes.
14Restricted standards

Restricted compatibility profiles

Standards whose text is not openly available are named and linked only. Any compatibility profile is kept on protected pages until an arrangement with the issuing body is in place.

The working group may identify restricted standards relevant to this area; they are listed here by name and link.

15Hadhira

Intended users

The area profile identifies 4 user communities.

  1. Implementers and vendors
  2. Standards editors
  3. QA engineers
  4. Procurement officers
16Hazards and sectors

Hazards, threats and sectors concerned

Hazards and threats 0

This area draws on the hazards of the areas it is coupled with.

Sekta 0

This area serves all sectors through the areas it is coupled with.

17Vyanzo

Vyanzo

3 references from peer-reviewed and official publications cited in the area profile, linked at the publishers’ own sites.

18Research hub

Recent research on this area

Recent peer-reviewed articles, preprints, datasets and reports on the subject of this area, retrieved at the time of reading from open scholarly metadata services (OpenAlex, Crossref, DataCite, Zenodo, arXiv, Europe PMC, OpenAIRE Graph) with search terms composed from the registry. Each work is listed with its authors, venue, year, type, open-access status and licence, and links to its DOI or landing page. Sources not yet enabled for live display on this site are listed for reference and are not queried.

Search termsconformance testing; test suite; interoperability testing; OGC API – Features; JSON Schema 2020-12Derived from the title and scope of the area, the NHS-1 hazards it names and the open standards it lists.

  • OpenAlexlisted for reference; not queried
  • Crossreflisted for reference; not queried
  • DataCitelisted for reference; not queried
  • Zenodolisted for reference; not queried
  • arXivlisted for reference; not queried
  • Europe PMClisted for reference; not queried
  • OpenAIRE Graphlisted for reference; not queried

No source is enabled for live display on this site yet: the sources are listed for reference and none is queried. Once the publisher of record enables a source after its terms are reviewed, recent works are listed here. Metadata and links only: title, authors, venue, year, type, open-access status and licence as each source records them; works are listed for orientation, not reviewed or endorsed.

19Elimu na mafunzo

Risk Academy courses and disciplines

1 course and 2 disciplines of Risk Academy (risksacademy.com) that teach the knowledge and methods of this area. Each course lists its level, stream and learning hours.

20Katika mtandao mzima

Programmes, tracks and courses for this area

GCRI Canada, The Global Risks Forum (GRF), The Global Risks Alliance (GRA) and Risk Academy work on the subject of this area in distinct roles (research and evidence; governance, policy and convening; capital, finance and markets; education and training). Each entry states why it corresponds and the step it offers; each institution sets its own terms of participation.

21Istilahi kuu

Istilahi kuu

UNI
Unique Nexus Identifier: a persistent identifier that resolves an artefact to its record.
inapendekezwa
A draft in the open development process that the Global Standards Council has not yet adopted. Each area profile is a proposal to the Nexus Standards registry.
cite
Relation in which the external standard is cited by identifier and URL as a reference.
adopt
Relation in which the external standard is used as published and values are validated against it.
profile
Relation in which a Nexus profile narrows or extends the external standard for a defined use, validated with the issuing body’s own tools where these exist.
change record
A public record of a proposed change under NS-13, decided by the editors with written reasons.
attestation
An evaluator’s recorded result for one clause and one subject under NS-11.
liaison sought
A liaison the working group intends to request from the issuing body; a liaison is established only when the body confirms it in writing.
23Utafiti

Recent research and sources

Peer-reviewed articles, preprints, reports and datasets on the subject of this area, retrieved at the time of reading from open scholarly metadata services (OpenAlex and Crossref) and listed with authors, venue, year, type and access status, with a link to each work. Curated references and related standards are listed first; recent works matched by subject follow and are listed for orientation.

Curated references

Related standards and frameworks

Search terms, derived from the title and scope of the area: conformance testing; test suite; interoperability testing. With JavaScript enabled, recent works matching these terms are listed from OpenAlex and Crossref.

24Maswali

Questions and answers.

What is the status of the Conformance test suites area?
The area profile is a proposal to the Nexus Standards registry; the area is not yet in the catalogue. Standards are adopted by the Global Standards Council after last call; in each country, adoption is a decision of its National Standards Council (NSC).
How are data sources presented?
Each data source is listed with its provider, licence, update frequency and delivery path, and links to the provider’s own publication.
How can this brief be amended?
Through a public change record under NS-13: a proposed amendment to the area profile or the registry, decided by the editors with written reasons.
RipotiChangia

Changia ushahidi kutoka ukurasa huu.

Reports ni chapisho la kila robo mwaka la Muungano. Unachojua kuhusu somo hili kinaweza kuwa ushahidi, kisa au sahihisho katika toleo lijalo, kikitajwa kwa jina lako na kuchapishwa chini ya CC BY 4.0 pale ambapo ni kazi yako mwenyewe.

Nexus Standards
Viwango

Contribute to Conformance test suites

Institutions and experts are invited to propose amendments, join the working group or propose data sources. National participation is organised through each country’s National Nexus Consortium (NNC) and its National Working Groups (NWGs); competent national authorities are engaged through official channels.

Hali na matumizi. Nexus Standards ni viwango vinavyopendekezwa vilivyoandaliwa kupitia mchakato wazi chini ya NS-13 na kuchapishwa kwa matumizi ya hiari; si uthibitisho, uidhinishaji wala idhini ya kidhibiti, na upitishaji unabaki kuwa uamuzi wa Baraza la Viwango la Dunia na, katika kila nchi, wa Baraza lake la Viwango la Kitaifa. UNI (Unique Nexus Identifier) hutambua kitu; haikithibitishi. Majina ya vyombo vya viwango na viwango vyao ni mali ya wasimamizi wake na yanatumika tu kutambua nyaraka; hakuna maandishi ya kiwango cha nje yanayonakiliwa hapa. Nexus Standards haihusiani na, haiidhinishwi wala haithibitishwi na chombo chochote cha viwango kilichotajwa hapa.

Leseni: CC BY 4.0 kwa matini ya viwango, rejista, miundo na data; Apache-2.0 kwa msimbo wa marejeo. Viwango vya nje hunukuliwa kwa jina, namba na kiungo chini ya leseni zake vyenyewe. Data, maktaba na fonti za wahusika wengine huhifadhi leseni zake: tazama Notisi za wahusika wengine.