Open standards development: conformance
How an implementer in open standards development demonstrates conformance: a self-assessment against the rules, clauses evaluated from evidence, attestations and a generated report. Each result names its evaluator and the time of evaluation, and each artefact is identified by a UNI (Unique Nexus Identifier).
- Nexus Standards: NS-0, NS-13.
- Open standards: RFC 6852 Affirmation of the Modern Paradigm for Standards (OpenStand); RFC 2026 The Internet Standards Process; W3C Process Document; OGC Technical Committee Policies and Procedures; ISO/IEC Directives Part 1 and Part 2; Creative Commons Attribution 4.0 International.
- Data and feeds: IETF Datatracker API; W3C technical reports feed; GitHub releases of the nexus-standards repository.
- Couples with: Conformance test suites; Naming, marks and intellectual property; Communities, learning and contribution.
پوختە
- 01Self-assessmentagainst the rules
- 02Clause setNS-10
- 03Evidencereferenced, not embedded
- 04AttestationNS-11, named evaluator
- 05Reportgenerated from results
- Nexus Standards
- 2
- NS-0, NS-13
- ستانداردە کراوەکان
- 6
- named, never copied
- Data and feeds
- 3
- listed for reference
- پەیوەستبوونەکان
- 3
- with other areas
Standards listed in the cross-cutting capabilities tier
The programme areas of this tier against the standards they list in the registry; the row for this area sets the initial scope of a self-assessment.
Coverage matrixA filled cell indicates that the area lists the standard in the registry. Status terms are those of the registry.
Conformance to NS-0
An implementation conforms to NS-0 when it:
- names the canonical repository and the versions of the standards it applies;
- does not fork a registry;
- runs the repository validator, or an equivalent, on the copies of the registries it uses;
- records its implementation status per standard in
registry/consumers.yamltruthfully;and - carries the honesty fields (
legalState,claimCeiling,status) on every record it publishes.
Conformance to NS-0 is a statement by the implementation, verifiable under NS-11. It is not a certification by the Secretariat or by the Global Standards Council.
Initial self-assessment for open standards development
The first rules of each applicable standard. A self-assessment is a statement by the implementer, verifiable under NS-11.
| یاسا | Requirement | ستاندارد |
|---|---|---|
NS0-P1 | Open · The standards, their registries, schemas, catalogues and reference tools are published in the canonical repository under the licences recorded in LICENSING.md. Participation in development is open to every community and stakeholder under GOVERNANCE.md. No standard depends on a proprietary artefact, product, account or mark to be applied. | NS-0 |
NS0-P2 | Machine-readable first · Every normative element exists as data (registry, schema, clause) before it exists as prose; prose explains, data governs. A standard with no machine form is not a Nexus Standard. | NS-0 |
NS0-P3 | Identified · Every artefact, record, deployment, policy and clause carries a UNI (NS-1, NS-3, NS-9). Nothing is cited by a name alone. | NS-0 |
NS13-R1 | Every change to a standard, registry, clause or policy shall enter through a proposal with a UNI. | NS-13 |
NS13-R2 | Participation shall be open and free of charge; identity shall be recorded (ORCID iD, ROR ID or an agent mandate); decisions shall be reasoned in writing. | NS-13 |
NS13-R3 | Last call shall be announced to every stakeholder group listed on the proposal; objections shall be dispositioned before acceptance. | NS-13 |
Attestations
One attestation is recorded per clause, per subject, per evaluation (AT category, append-only). Results: PASS; FAIL; INDETERMINATE (evidence missing or unresolvable); NOT_APPLICABLE (the subject was outside the clause’s selectors at that instant); REFUSED (the evaluator lacked a mandate or the evidence was not accessible; the refusal is itself recorded). An attestation carries a canonical digest and, optionally, a signature; certifiesTruth is always false. A later attestation supersedes an earlier one for the same clause and subject, and the history is kept.
Crosswalks: an attestation can be exported as a W3C Verifiable Credential under the Verifiable Credentials Data Model 2.0 (subject: the contextual UNI; issuer: the evaluator; evidence: the refs), as an in-toto attestation (for software subjects) or as a PROV-O activity (NS-3b). The Nexus attestation remains the key and the record of truth.
چاودێری
Monitoring is continuous evaluation together with observation records. For each bound policy and context, the monitoring service records (a) the latest attestation per clause, (b) coverage (which clauses have no current attestation, and why), (c) drift (a change in a subject’s records that invalidates an attestation) and (d) the availability of evaluators and evidence sources. Monitoring records are observations with record UNIs. Dashboards and panels are projections of them and show the timestamp and the evaluator for every value; no verdict is stored.
Reporting
A conformance report for a context is generated, not written: policy by policy and clause by clause, with attestation UNIs, evidence refs, conformance levels (NS-10 section 3) and the honesty fields. Reports are catalogued artefacts (RP) and may be published (NS-8) only when their legalState allows. A report does not say "certified" or "compliant" except when it quotes an authority decision by reference.
Display of conformance statements
A context (NS-9) or artefact claims a relation to an external standard only through a clause set (NS-10) that cites that standard and is evaluated (NS-11). The claim is displayed as "implements clauses derived from <standard> (n of m with a current PASS)", with attestation UNIs. It is never displayed as "compliant with" or "certified to" unless a decision of the body entitled to say so is referenced. Where a body operates its own certification, conformance under the Nexus Standards is explicitly not that certification.
پرسیار و وەڵام.
How does a conformance report in open standards development relate to the decisions of other bodies?
What happens when evidence is missing?
Around open standards development.
Shape the standards for open standards development.
Governments, regulators, standards bodies, industry, academia and communities are invited to shape the catalogue ahead of its first official release, targeted for 2030: comment on a draft, propose a change, join a working group or host a field exercise.
دۆخ و بەکارهێنان. Nexus Standards ستانداردی پێشنیارکراون کە لە ڕێگەی پرۆسەیەکی کراوەوە لەژێر NS-13 پەرەیان پێدراوە و بۆ بەکارهێنانی خۆبەخشانە بڵاو کراونەتەوە؛ بڕوانامە، متمانەپێدان یان ڕەزامەندیی ڕێکخەر نین، و پەسەندکردن بڕیاری ئەنجومەنی جیهانیی ستانداردەکان و، لە هەر وڵاتێکدا، ئەنجومەنی نیشتمانیی ستانداردەکانی ئەو وڵاتەیە. UNI (Unique Nexus Identifier) بەرهەمێک دەناسێنێت؛ بڕوانامەی پێ نادات. ناوی دەستەکانی ستاندارد و ستانداردەکانیان هی پارێزەرەکانیانن و تەنها بۆ ناساندنی بەڵگەنامەکان بەکاردێن؛ هیچ دەقێکی ستانداردێکی دەرەکی لێرەدا دووبارە نەکراوەتەوە. Nexus Standards پەیوەست نییە بە هیچ دەستەیەکی ستانداردی ناوهێنراو لێرەدا، و لەلایەن هیچیانەوە پشتگیری یان بڕوانامەی پێ نەدراوە.
مۆڵەتەکان: CC BY 4.0 بۆ دەقی ستانداردەکان، تۆمارگەکان، سکێماکان و داتا؛ Apache-2.0 بۆ کۆدی سەرچاوە. ستانداردە دەرەکییەکان بە ناو، ژمارە و بەستەر لە ژێر مۆڵەتەکانی خۆیاندا ئاماژەیان پێدەدرێت. داتا، کتێبخانە و فۆنتەکانی لایەنی سێیەم مۆڵەتەکانی خۆیان دەپارێزن: بڕوانە ئاگادارییەکانی لایەنی سێیەم.