کۆمەڵە تاقیکردنەوەکانی گونجان
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).
- 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
- ستانداردە کراوەکان
- 4
- named, never copied
- Data and feeds
- 3
- listed for reference
- پەیوەستبوونەکان
- 3
- with other areas
- UNI
- requested · allocation in progress
- دۆخ
- Proposednot yet in the catalogue
- Last reviewed
- area profile
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.
Files include the credits and the licence statement and are generated in the browser; no data is transmitted. Downloads require JavaScript.
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.
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.
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 · گونجاندن · خولی ژیانی تۆمار · ئاڕاستەکردن · چاودێری.
دۆزینەوەکانی خول دەبنە پێشنیاری گۆڕانکاری، ئەنجومەنی جیهانیی ستانداردەکان دوای دوایین بانگەوازی گشتی پەسەندیان دەکات، و هەر وڵاتێک بڕیار لەسەر پەسەندکردنی خۆی دەدات.
01 ئاڕاستەکردنی ئەرکەکان
- 01ئەرکەکان بەرەو ستاندارد و پڕۆفایلەکان ئاراستە بکەهەنگاو · Nexus StandardsNexus Standards هەر ئەرکێکی کاندید ئاڕاستەی ئەو ستاندارد و پرۆفایلانە دەکات کە جێبەجێ دەبن.
02 پرۆفایلەکان و گونجان
- 02پرۆفایلی ئەرکەکان پێکبهێنەهەنگاو · Nexus StandardsNexus Standards پرۆفایلی ئەرکەکان پێکدەهێنێت و هەر پەسەندکردنێکی نیشتمانی تۆمار دەکات کە ئەرکەکان پشتی پێدەبەستن.
- 03دەرچووەکانی دروستکردن بەراورد بە پڕۆفایلەکان پشتڕاست بکەرەوەهەنگاو · Nexus StandardsNexus Standards دەرچووەکانی دروستکردن بەراورد بە پڕۆفایلە پێکهێنراوەکان پشتڕاست دەکاتەوە و بەڵگەکان تۆمار دەکات.
- 04چاودێریی گونجان بکە و بەڵگەی مۆرکراو تۆمار بکەهەنگاو · Nexus Standardsلە ماوەی Action Week دا، Nexus Standards چاودێریی گونجان دەکات و لادانەکان تۆمار دەکات.
03 پێشنیار و پێداچوونەوە
- 05لادان و ڕاستکردنەوەکان دەبنە پێشنیاری گۆڕانکاریهەنگاو · Nexus Standardsلادانەکان دەبنە پێشنیاری گۆڕانکاری، و ڕاستکردنەوەکە وەک گۆڕانێک لە بەڵگەکەدا تۆمار دەکرێت.
- 06دۆزینەوەکانی خول دەبنە پێشنیاری گۆڕانکاریهەنگاو · Nexus Standardsدۆزینەوەکانی خولێک دەبنە پێشنیاری گۆڕانکاری: دۆزینەوەکانی میتۆد و ڕاستکردنەوە لە ڕاپۆرتەکان (F06) و بابەتەکانی خشتەی کار لە Nexus…
- 07بە ئاشکرا ڕەشنووس بکە و پێیدا بچۆرەوەهەنگاو · لیژنەکان و گرووپەکانی کارلیژنە تەکنیکییەکان و گرووپەکانی کار ستانداردەکان لە پرۆسەی کراوەی NS-13 دا ڕەشنووس دەکەن و پێیاندا دەچنەوە.
- 08پێداچوونەوە بەرەو بڕیاری ئەنجومەنهەنگاو · Nexus StandardsNexus Standards پێشنیارەکانی گۆڕانکاری لە ڕێگەی پێداچوونەوەوە بەرەو بڕیاری ئەنجومەن دەبات.
04 بڕیاری ئەنجومەن
- 09بانگەوازی کۆتایی گشتیهەنگاو · ئەنجومەنی جیهانیی ستانداردەکانئەنجومەنی جیهانیی ستانداردەکان دوای بانگەوازێکی کۆتایی نەوەد ڕۆژە بە زۆرینەی دوو لەسەر سێ پەسەند دەکات.
- 10پەسەندکردنی جیهانیی ستانداردێکبڕیار · ئەنجومەنی جیهانیی ستانداردەکانئەنجومەنی جیهانیی ستانداردەکان دوای دوایین بانگەوازی گشتی بڕیار لەسەر پەسەندکردنی هەر ستانداردێک دەدات.
05 بڵاوکردنەوە و ناساندن
- 11Assign a UNI and publishStep · Secretariat (GCRI Canada)Nexus Standards assigns UNIs and deposits publications under the publisher’s process.
- 12UNI دەناسێنێت و هەرگیز بڕوانامە ناداتتۆمار · Nexus Standardsهەر بابەتێکی ساڵی بەرنامە یەک ناسێنەر هەڵدەگرێت، UNI یەک لەژێر NS-1، بۆ ئەوەی ئاماژەی پێ بکرێت، وەشانبەندی بکرێت و چارەسەر بکرێت.
- 13گۆڕانکارییە پەسەندکراوەکانی ساڵەکە بڵاو بکەرەوەهەنگاو · Nexus Standardsلە کاتی نوێکردنەوەدا Nexus Standards گۆڕانکارییە پەسەندکراوەکانی ساڵەکە و دۆخی پەسەندکردنی نیشتمانی بڵاو دەکاتەوە.
06 پەسەندکردن و جێبەجێکردنی نیشتمانی
- 14پەسەندکردنی نیشتمانی لەلایەن ئەنجومەنی نیشتمانیی ستانداردەکانەوەبڕیار · ئەنجومەنی نیشتمانیی ستانداردەکانئەنجومەنی نیشتمانیی ستانداردەکانی هەر وڵاتێک بڕیار لەسەر پەسەندکردنی نیشتمانی دەدات: وەک خۆی پەسەند بکرێت، بە پڕۆفایلێک پەسەند بکرێت (NS-16)، بگونجێنرێت، یان تەنها ئاماژەی پێ بکرێت.
- 15ستانداردە پەسەندکراوەکان دەگەنە خول و وەشانەکانهەنگاو · Nexus Standardsهەر ستاندارد یان پرۆفایلێکی پەسەندکراو دەبێتە مۆدیولی خولێک لە Risk Academy (F09)، و ستانداردەکان لە وەشانەکانی Reports دا جێبەجێ دەکرێن (R1).
- 16پەسەندکردن بۆ هەر ناوچەیەکی دەسەڵات کۆتاییەستاندارد · ئەنجومەنی نیشتمانیی ستانداردەکانپەسەندکردن بۆ هەر ناوچەیەکی دەسەڵات کۆتاییە، و GSC هیچ ڤیتۆیەکی بەسەر بڕیارێکی نیشتمانیدا نییە. هیچ دەزگایەکی جیهانی ڤیتۆی نییە.
- 17تۆمارەکانی پەسەندکردنی نیشتمانیتۆمار · Nexus Standardsپڕۆفایلە پێکهێنراوەکانی ئەرک و تۆمارەکانی پەسەندکردنی نیشتمانی لە قۆناغی ئامادەکردنی ئامادەییدا دەنێردرێن بۆ Foundry (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
| هەنگاو | قۆناغ | کارکردن | کێ | Decision 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 machine | the context is explicit in the request or on the record, never inferred | a request naming its context and inputs | NS16-R20 |
| 02 | داواکاری | Identify inputs (step). Every input is resolved before it is used; an unresolved input is a typed refusal. | the service | inputs are cited by UNI and version | inputs resolved to their UNIs and versions | NS1-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 validator | validated against the open standard’s own schema or validator where one exists | a validation run against OGC API – Features (with OGC executable test suite pattern) and JSON Schema 2020-12 | NS14-R2 |
| 04 | Processing | Process (model). Processing is reproducible from the inputs, the method version and the configuration. | the service | the method and version are recorded with the result | Browser test environment, continuous-integration action and hosted runner | NS12-R1 |
| 05 | Processing | Write records (record). Results are written append-only; a correction adds a version. | the service | every result carries what it was derived from | result records with provenance and a record UNI | NS0-P7, NS1-R3 |
| 06 | بڵاوکراوە | Publish and resolve (step). Results are discoverable and citable by UNI. | the service | writes return the allocated UNI; citations resolve | results reachable through the resolver, with the X-Nexus-UNI header | NS1-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 service | monitoring records are observations with record UNIs | observations of availability, drift and W3C Process Document Implementation experience | NS11-R4 |
| 08 | چاودێری | Correction (end). Products that used a corrected record are listed and recomputed. | the data steward | a correction never overwrites; dependent results are replayed | a correction record that reaches every dependent result | NS1-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.
Routing, monitoring and verification tools
Verification console
Test suites, conformance statements and attestations for each standard, as recorded in the registry.
پلانی بۆ دانراوەDeployment
Reference deployments and a sandbox with worked examples.
Each console computes from the registry and states its reasoning; decisions remain with the competent bodies.
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سەلماندن و چاودێری (بەڵگە، گواهییەکان، چاودێریی گونجان لەگەڵ zero-trust)NS-13پرۆسەی پەرەپێدانی ستانداردەکان (پێشنیاری کراوە، پێداچوونەوە، وەشانبەندی، پەسەندکردن)NRS-S9پڕۆفایلی سیستەم: NXS-AAP (کاری پێشوەختی و دەستپێکەرەکان)NRS-C11گونجان، پشتڕاستکردنەوە و چاککردنەوەی ستانداردەکانNRS-S1System profile: NXS-CMD (Integrated posture and executive synthesis)NRS-S2System profile: NXS-NST (Civilian common operating picture)NRS-S3System profile: NXS-DSS (Decision cases and deliberation)NRS-S4System 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
پەیوەستبوونە سیستەمییەکان
3 couplings link this area to other areas and programmes, each with the mechanism of the link.
- 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.
- Verification servicesTrust, Verification and AssuranceThe hosted validator runs the same corpus to produce EVALUATED attestations.
- 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.
ستانداردە جێبەجێبووەکان
The area profile lists 3 Nexus Standards. Each is a proposed standard under development.
- 01
NS-14 · Conformance and crosswalk to external standards
Status: proposed · 5 requirements stated. Read NS-14.
- 02
NS-11 · Verification and monitoring (evidence, attestations, zero-trust conformance observation)
Status: proposed · 6 requirements stated. Read NS-11.
- 03
NS-13 · Standards development process (open proposals, review, versioning, adoption)
Status: proposed · 5 requirements stated. Read NS-13.
Open standards referenced
4 open standards, each with its relation as recorded in the register under NS-14. Hover over or focus a relation for its definition.
Data sources
3 data sources named in the area profile, each with provider, licence, update frequency and delivery path.
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
- جێبەجێکردن
- 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-testsبۆ ئاماژەweb-platform-tests project · continuous
BSD 3-Clause
build-time snapshotproposed for the data register
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).
- Test corpus for each proposed edition
- Three runners with identical results on the fixture set
- Implementation report template
- OGC Compliance Program liaison sought
- web-platform-tests maintainers liaison sought
- STAC community liaison sought
نیشاندەرەکان
The area profile names 2 indicators, each with its framework and code.
Indicator names and codes are given as published by their stewards.
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.
GCRI Canada
GCRI Canada runs the corpus in its analytical workflows and cites the corpus digest and version with results.
Global Risks Forum (GRF)
GRF lists implementation statements as submitted, with their test evidence and no ordering by score.
Global Risks Alliance (GRA)
GRA reads test results as evidence about a version at a point in time, not as a lasting guarantee.
Each institution determines under its own rules what it accepts as evidence; a pathway reading is neither an approval nor investment advice.
Open research questions
2 questions identified as priorities for the working group.
- Tests for runtime behaviour (latency, availability) that are fair across very different hosts.
- Keeping external validators’ versions pinned without lagging behind their fixes.
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.
Intended users
The area profile identifies 4 user communities.
- Implementers and vendors
- Standards editors
- QA engineers
- Procurement officers
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.
سەرچاوەکان
3 references from peer-reviewed and official publications cited in the area profile, linked at the publishers’ own sites.
peer-reviewedFrom Conceptualization to Implementation: FAIR Assessment of Research Data ObjectsData Science Journal · 2021peer-reviewedEvaluating FAIR maturity through a scalable, automated, community-governed frameworkScientific Data · 2019- officialW3C Process DocumentW3C · 2025
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.
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.
خولەکان
بوارە زانستییەکان
The correspondence between courses, disciplines and the Nexus Standards is maintained with Risk Academy and is subject to its academic review.
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.
توێژینەوە و بەڵگە
GCRI Canada
Research programmes that produce the observations, models and assessments these records describe.
LabsMaintains research protocols and reproducible records, including negative results.Apply to this programme Systems Science and ModellingDevelops reproducible modelling.Apply to this programme therisk.globalAll programmes of GCRI CanadaGovernance, policy and convening
Global Risks Forum (GRF)
Tracks that convene public authorities, researchers and institutions on the governance of shared risks.
Governance NexusExamines anti-capture and integrity arrangements.Join this track AI and Digital GovernanceExamines technology procurement and standards in the public sector.Join this track globalriskforum.comAll tracks of The Global Risks ForumCapital, finance and markets
Global Risks Alliance (GRA)
Industry programmes in which financial institutions build a shared understanding of systemic risk.
Financial Cyber and Operational ResilienceWorks on operational resilience testing and digital supply chains in finance.Join this programme Financial Crime and Fraud RiskExamines identity fraud and institutional integrity.Join this programme globalriskalliance.comAll programmes of The Global Risks Allianceپەروەردە و ڕاهێنان
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زاراوە سەرەکییەکان
- 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.
Related areas
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
- Evaluating FAIR maturity through a scalable, automated, community-governed framework
Scientific Data · 2019 · Peer-reviewed - From Conceptualization to Implementation: FAIR Assessment of Research Data Objects
Data Science Journal · 2021 · Peer-reviewed - W3C Process Document
W3C · 2025 · Official publication
Related standards and frameworks
- OGC API – Features (with OGC executable test suite pattern)
OGC - JSON Schema 2020-12
JSON Schema project - SpatioTemporal Asset Catalog (STAC)
OGC (Community Standard) - SWHID v1.2
SWHID working group / Software Heritage
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.
پرسیار و وەڵام.
What is the status of the Conformance test suites area?
How are data sources presented?
How can this brief be amended?
لەم لاپەڕەیەوە بەڵگە پێشکەش بکە.
Reports بڵاوکراوەی وەرزیی کۆنسۆرتیۆم ـە. ئەوەی تۆ لەسەر ئەم بابەتە دەیزانیت دەتوانێت لە وەشانی داهاتوودا ببێتە بەڵگە، کەیس یان ڕاستکردنەوە، بە ناوی خۆتەوە و لەژێر CC BY 4.0 بڵاو دەکرێتەوە کاتێک کاری خۆتە.
- ئیمەیڵدەروازەی GW-STDلەم لاپەڕەیەوە بینێرەبەڵگە، ڕاستکردنەوە، کەیس، میتۆد، پێداچوونەوە، وەرگێڕان یان زانیاریی پرۆفایل. بە نیشانەی ئەم لاپەڕەیەوە دەگات، بۆ ئەوەی ئەو سەرنووسەرەی خاوەنیەتی وەری بگرێت.
- ZenodoOpen depositDeposit it and submit to the communityPublish your own record on Zenodo with your ORCID iD, then submit it to the Reports community there. Curators review it; the DOI stays yours.
- ReportsNexus StandardsSee every way to contributeThe contribution types, how each is reviewed, what credit you receive, the licence and what is never accepted.
هەرگیز داتای کەسی، وردەکاریی هەستیاری ژێرخان یان هیچ شتێک مەنێرە کە مافی بڵاوکردنەوەت نییە. بەشدارییەک پێش بەکارهێنان پێداچوونەوەی بۆ دەکرێت؛ ناردنی ماف نابەخشێت بە نووسەرایەتی یان بەڕێوەبردنی ڕاگەیاندن، و پاڵپشتی دارایی هەرگیز دۆزینەوەیەک ناکڕێت.
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 بۆ کۆدی سەرچاوە. ستانداردە دەرەکییەکان بە ناو، ژمارە و بەستەر لە ژێر مۆڵەتەکانی خۆیاندا ئاماژەیان پێدەدرێت. داتا، کتێبخانە و فۆنتەکانی لایەنی سێیەم مۆڵەتەکانی خۆیان دەپارێزن: بڕوانە ئاگادارییەکانی لایەنی سێیەم.