Standards profile
The candidate records both what it targets and what it does not yet claim. This avoids turning an implementation compatibility result into an unsupported conformance claim.
Profile claims
- Full Union profile
- not claimed until a qualified implementation passes the required feature matrix
- RDF
- RDF 1.2 Basic authoring profile with explicit VERSION labels
- SHACL
- SHACL 1.2 Core target; emitted constraints use the implementation-tested Core subset
- SPARQL
- SPARQL 1.2 target; competency queries use the portable basic graph-pattern subset
Normative and informative targets
| Target | Profile or specification |
|---|---|
| DCMI Terms | https://www.dublincore.org/specifications/dublin-core/dcmi-terms/ |
| OWL 2 | https://www.w3.org/TR/owl2-overview/ |
| PROV-O | https://www.w3.org/TR/prov-o/ |
| RDF 1.2 Concepts | https://www.w3.org/TR/2026/CR-rdf12-concepts-20260407/ |
| RDF profile | RDF 1.2 Basic |
| RDF 1.2 Turtle | https://www.w3.org/TR/2026/WD-rdf12-turtle-20260528/ |
| SHACL 1.2 Core | https://www.w3.org/TR/2026/WD-shacl12-core-20260516/ |
| SHACL profile | SHACL 1.2 Core working-draft subset used by this candidate |
| SKOS | https://www.w3.org/TR/skos-reference/ |
| SPARQL 1.2 Query | https://www.w3.org/TR/2026/WD-sparql12-query-20260605/ |
Assurance boundary
No full Union-profile claim
not claimed until a qualified implementation passes the required feature matrix
The technical validation page records the actual tested implementation and subset. Standards targets can be broader than the features exercised by one candidate corpus.
Comments
Loading comments…
Sign in to post a comment