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

Conformance test suites

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).

Conformance test suites
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
स्थिती
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.

01व्याप्ती

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.

03प्रक्रिया

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.

प्रक्रिया अन्वेषक · Standards · संहिताबद्ध करा आणि दुरुस्त करा

मानक जीवनचक्र

17 पायऱ्या6 टप्पे

Standards · संहिताबद्ध करा आणि दुरुस्त करा

मानक जीवनचक्र

मानक जीवनचक्र · NS-13 मार्ग · योगदान माध्यमे · IETF मार्ग · W3C मार्ग · OGC मार्ग · OASIS मार्ग · ISO आणि IEC टप्पे · अनुरूपता · नोंद जीवनचक्र · मार्गनिर्देशन · देखरेख.

चक्रातील निष्कर्ष बदल प्रस्ताव बनतात, जागतिक मानके परिषद सार्वजनिक अंतिम आवाहनानंतर स्वीकारते, आणि प्रत्येक देश स्वतःचा स्वीकार ठरवतो.

  1. 01 मोहिमांचे मार्गनिर्देशन

    1. 01मोहिमांना मानके आणि प्रोफाइलकडे न्यापायरी · Nexus StandardsNexus Standards प्रत्येक उमेदवार मोहिमेला लागू मानके आणि प्रोफाइलकडे नेते.
  2. 02 प्रोफाइल आणि अनुरूपता

    1. 02मोहीम प्रोफाइल रचापायरी · Nexus StandardsNexus Standards मोहीम प्रोफाइल रचते आणि मोहिमा अवलंबून असलेला कोणताही राष्ट्रीय स्वीकार नोंदवते.
    2. 03उभारणीचे आउटपुट प्रोफाइलविरुद्ध प्रमाणित करापायरी · Nexus StandardsNexus Standards उभारणीचे आउटपुट रचलेल्या प्रोफाइलविरुद्ध प्रमाणित करते आणि पुरावा नोंदवते.
    3. 04अनुरूपतेवर देखरेख ठेवा आणि मोहोरबंद पुरावा नोंदवापायरी · Nexus Standardsकृती सप्ताहात Nexus Standards अनुरूपतेवर देखरेख ठेवते आणि विचलने नोंदवते.
  3. 03 प्रस्ताव आणि आढावा

    1. 05विचलने आणि दुरुस्त्या बदल प्रस्ताव बनतातपायरी · Nexus Standardsविचलने बदल प्रस्ताव बनतात, आणि दुरुस्ती पुराव्यातील बदल म्हणून नोंदवली जाते.
    2. 06चक्रातील निष्कर्ष बदल प्रस्ताव बनतातपायरी · Nexus Standardsचक्रातील निष्कर्ष बदल प्रस्ताव बनतात: पद्धत आणि दुरुस्ती निष्कर्ष अहवाल (F06) कडून आणि Nexus कडून कार्यसूची बाबी…
    3. 07खुलेपणाने मसुदा तयार करा आणि सुधारणा करापायरी · समित्या आणि कार्यगटतांत्रिक समित्या आणि कार्यगट NS-13 च्या खुल्या प्रक्रियेत मानकांचा मसुदा तयार करतात आणि सुधारणा करतात.
    4. 08परिषदेच्या निर्णयाकडे आढावापायरी · Nexus StandardsNexus Standards बदल प्रस्तावांना आढाव्यातून परिषदेच्या निर्णयाकडे नेते.
  4. 04 परिषद निर्णय

    1. 09सार्वजनिक अंतिम आवाहनपायरी · जागतिक मानके परिषदजागतिक मानके परिषद नव्वद दिवसांच्या अंतिम आवाहनानंतर दोन-तृतीयांश बहुमताने स्वीकारते.
    2. 10मानकाचा जागतिक स्वीकारनिर्णय · जागतिक मानके परिषदजागतिक मानके परिषद सार्वजनिक अंतिम आवाहनानंतर प्रत्येक मानकाच्या स्वीकाराचा निर्णय घेते.
  5. 05 प्रकाशित करा आणि ओळख द्या

    1. 11Assign a UNI and publishStep · Secretariat (GCRI Canada)Nexus Standards assigns UNIs and deposits publications under the publisher’s process.
    2. 12UNI ओळख देतो आणि कधीही प्रमाणन करत नाहीनोंद · Nexus Standardsकार्यक्रम वर्षातील प्रत्येक वस्तूला एक ओळखकर्ता असतो, NS-1 अंतर्गत UNI, जेणेकरून ती उद्धृत, आवृत्तीबद्ध आणि निराकरण करता येते.
    3. 13वर्षात स्वीकारलेले बदल प्रकाशित करापायरी · Nexus Standardsनूतनीकरणाच्या वेळी Nexus Standards वर्षात स्वीकारलेले बदल आणि राष्ट्रीय स्वीकार स्थिती प्रकाशित करते.
  6. 06 राष्ट्रीय स्वीकार आणि उपयोजन

    1. 14राष्ट्रीय मानके परिषदेकडून राष्ट्रीय स्वीकारनिर्णय · राष्ट्रीय मानके परिषदप्रत्येक देशाची राष्ट्रीय मानके परिषद राष्ट्रीय स्वीकार ठरवते: जसे आहे तसे स्वीकारणे, प्रोफाइलसह स्वीकारणे (NS-16), रूपांतर करणे, किंवा केवळ संदर्भ.
    2. 15स्वीकृत मानके अभ्यासक्रम आणि आवृत्त्यांपर्यंत पोहोचतातपायरी · Nexus Standardsप्रत्येक स्वीकृत मानक किंवा प्रोफाइल Risk Academy (F09) मध्ये अभ्यासक्रम विभाग बनतो, आणि मानके Reports आवृत्त्यांमध्ये (R1) लागू केली जातात.
    3. 16प्रत्येक अधिकारक्षेत्रासाठी स्वीकार अंतिम असतोमानक · राष्ट्रीय मानके परिषदप्रत्येक अधिकारक्षेत्रासाठी स्वीकार अंतिम असतो, आणि राष्ट्रीय निर्णयावर GSC ला नकाराधिकार नाही. कोणत्याही जागतिक संस्थेकडे नकाराधिकार नाही.
    4. 17राष्ट्रीय स्वीकार नोंदीनोंद · Nexus Standardsरचलेली मोहीम प्रोफाइल आणि राष्ट्रीय स्वीकार नोंदी सज्जता तयारीच्या वेळी (F08) Foundry कडे जातात.

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
पायरीPhaseसंचालनWhoDecision ruleनोंदImplements
01विनंतीRequest (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
02विनंतीIdentify 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
03प्रमाणीकरणValidate 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
07देखरेखMonitor (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
08देखरेखCorrection (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.

प्रणाली आणि जोडण्या

नियंत्रणे

  • NS-14 बाह्य मानकांशी अनुरूपता आणि तुलनात्मक संदर्भ
  • NS-11 सत्यापन आणि देखरेख (पुरावा, प्रमाणपत्रे, शून्य-विश्वास अनुरूपता निरीक्षण)
  • NS-13 मानके विकास प्रक्रिया (खुले प्रस्ताव, आढावा, आवृत्तीकरण, स्वीकार)
  • NRS-S9 System profile: NXS-AAP (Anticipatory action and triggers)
  • NRS-C11 अनुरूपता, पडताळणी आणि मानक देखभाल
  • 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)

निरीक्षण

  • 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
06प्रणालीगत जोडण्या

प्रणालीगत जोडण्या

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.
07मानके

लागू होणारी मानके

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.

थेट
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

10कार्यगट

Working group charter

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

व्याप्ती

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
11निर्देशक

निर्देशक

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

12सज्जता

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

मान्यता मार्ग

Global Risks Forum (GRF)

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

Read the recognition pathway

भांडवल मार्ग

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.

15Audiences

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.

क्षेत्रे 0

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

17स्रोत

स्रोत

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.

19शिक्षण आणि प्रशिक्षण

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.

20संपूर्ण जाळ्यात

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.

शिक्षण आणि प्रशिक्षण

Risk Academy

Courses and disciplines that teach the knowledge and methods practitioners need to apply these standards.

Technology and DataRAT-204 · Intermediate · 19 learning hoursManaging risk data, AI, digital infrastructure and technology risk responsiblyTake this course All courses and disciplinesListed in the education and training section of this page
21प्रमुख संज्ञा

प्रमुख संज्ञा

UNI
Unique Nexus Identifier: a persistent identifier that resolves an artefact to its record.
प्रस्तावित
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.
23संशोधन

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.

24प्रश्न

प्रश्न आणि उत्तरे.

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.
अहवालयोगदान द्या

या पानावरून पुरावा योगदान द्या.

Reports हे कन्सोर्टियमचे त्रैमासिक प्रकाशन आहे. या विषयाबद्दल तुम्हाला जे माहीत आहे ते पुढील आवृत्तीत पुरावा, उदाहरण किंवा दुरुस्ती बनू शकते, तुम्हाला श्रेय देऊन आणि ते तुमचे स्वतःचे काम असल्यास CC BY 4.0 अंतर्गत प्रकाशित.

Nexus Standards

वैयक्तिक डेटा, संवेदनशील पायाभूत सुविधांचा तपशील किंवा सामायिक करण्याचा तुम्हाला अधिकार नसलेले काहीही कधीही पाठवू नका. योगदानाचे वापरापूर्वी पुनरावलोकन केले जाते; ते पाठवल्याने कोणतेही लेखकत्व किंवा संपादकीय अधिकार मिळत नाहीत, आणि प्रायोजकत्वाने कधीही निष्कर्ष विकत घेता येत नाही.

मानके

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.

स्थिती आणि वापर. Nexus Standards ही NS-13 अंतर्गत खुल्या प्रक्रियेद्वारे विकसित केलेली आणि ऐच्छिक वापरासाठी प्रकाशित प्रस्तावित मानके आहेत; ती प्रमाणन, अधिस्वीकृती किंवा नियामक मंजुरी ठरत नाहीत, आणि स्वीकार हा जागतिक मानके परिषदेचा आणि प्रत्येक देशात त्याच्या राष्ट्रीय मानके परिषदेचा निर्णय राहतो. UNI (Unique Nexus Identifier) वस्तू ओळखतो; तो तिचे प्रमाणन करत नाही. मानके संस्थांची आणि त्यांच्या मानकांची नावे त्यांच्या विश्वस्तांची आहेत आणि केवळ दस्तऐवज ओळखण्यासाठी वापरली जातात; बाह्य मानकाचा कोणताही मजकूर येथे पुनरुत्पादित केलेला नाही. Nexus Standards येथे नमूद कोणत्याही मानके संस्थेशी संलग्न नाही, तिच्याकडून समर्थित किंवा प्रमाणित नाही.

परवाने: मानकांचा मजकूर, नोंदवह्या, स्कीमा आणि माहितीसाठी CC BY 4.0; संदर्भ कोडसाठी Apache-2.0. बाह्य मानके त्यांच्या स्वतःच्या परवान्याखाली नाव, क्रमांक आणि दुव्याद्वारे उद्धृत केली जातात. तृतीय-पक्ष माहिती, ग्रंथालये आणि फॉन्ट त्यांचे स्वतःचे परवाने राखतात: तृतीय-पक्ष सूचना पाहा.