CUE comprehensions precompute every query. CUE unification enforces every shape.
17 W3C specifications—from JSON-LD to Verifiable Credentials—as
zero-cost projections of the same typed dependency graph.
No triplestore. No SPARQL. Just cue export.
cue export -e <projection>Resources are structs with @type, depends_on, and metadata.
#Graph computes topology, depth, and critical path at eval time.
#Charter declares what must exist. #ComplianceCheck validates structural rules.
Both emit sh:ValidationReport automatically.
JSON-LD, SHACL, SKOS, EARL, OWL-Time, Dublin Core, PROV-O, schema.org, ODRL,
Activity Streams, Verifiable Credentials, W3C Org, DCAT. Each is a
cue export -e expression. No transformation layer.
No installation required. These run entirely client-side.
Click nodes in a live graph. See 6 W3C projections computed instantly—SHACL, SKOS, EARL, OWL-Time, PROV-O, and JSON-LD—from the same data.
D3 force-directed visualization of the apercue.ca project itself. Modules, patterns, views, and their dependencies as a live graph.
Live gate-by-gate tracking of the apercue.ca build. The project tracks its own progress using the system it defines.
Which W3C specs cover which patterns. A coverage matrix showing the full mapping from graph features to standard outputs.
A constraint-first governance charter for Canadian federal LLM deployment. 52 typed resources across 8 phases, with live SHACL compliance, OWL-Time scheduling, ODRL classification policies, PROV-O provenance chains, DCAT catalog, and VC attestation—all from one CUE dependency graph.
The same #Graph, #Charter, and W3C projection
patterns work across any domain. Not just infrastructure.
University CS curriculum as a dependency graph. Charter gates enforce degree requirements. CPM finds the optimal schedule.
Beef bourguignon as a prep dependency graph. Critical path finds the minimum cooking timeline.
Software release pipeline with schema:actionStatus lifecycle. Gap analysis surfaces what's blocking each milestone.
Multi-tier supply chain from raw materials to product. DCAT catalog, SHACL quality gates, CPM lead times.
Directive on ADM compliance, AIA impact levels, ODRL classification policies, and PROV-O provenance for Canadian federal LLM deployments. Full dashboard with 7 W3C projection panels.
Each spec is a CUE comprehension that projects the same underlying graph. No adapters. No converters. The data is the standard.
| Spec | CUE Pattern | Status |
|---|---|---|
| Core projections | ||
| JSON-LD 1.1 | vocab/context.cue | Implemented |
| SHACL | validation.cue, charter.cue | Implemented |
| SKOS | views/skos.cue, lifecycle.cue | Implemented |
| EARL | lifecycle.cue | Implemented |
| OWL-Time | analysis.cue | Implemented |
| Dublin Core | vocab/context.cue | Implemented |
| Extended projections | ||
| PROV-O | provenance.cue | Implemented |
| schema.org | schema_alignment.cue | Implemented |
| ODRL 2.2 | policy.cue | Implemented |
| Activity Streams 2.0 | activity.cue | Implemented |
| Verifiable Credentials 2.0 | credentials.cue | Implemented |
| W3C Org | views/org.cue | Implemented |
| VoID | void.cue | Implemented |
| RDFS/OWL | ontology.cue | Implemented |
| Web Annotation | annotation.cue | Implemented |
| DQV | quality.cue | Implemented |
| SHACL Shapes | shapes.cue | Implemented |
| Downstream (in quicue.ca) | ||
| Hydra Core | quicue.ca operator | Downstream |
| DCAT 3 | catalog.cue | Implemented |
Every query that would traditionally require a SPARQL endpoint is precomputed as a CUE comprehension at eval time. No query language. No query engine. The answers are structural.
Shape validation isn't a separate runtime step. CUE's type system is the SHACL engine. If a graph compiles, its shapes are valid. Constraint violations are compile errors, not runtime exceptions.
Adding PROV-O support meant writing provenance.cue. Adding ODRL
meant writing policy.cue. Each W3C projection is a single file
that projects the same graph. No framework changes needed.
The project's own build charter is tracked using #Charter and
#GapAnalysis—the same patterns it defines.
The charter page shows live gate progress.
The typed dependency graph pattern works for course prerequisites, cooking recipes, supply chains, housing retrofits, real estate transactions, and infrastructure. The W3C projections don't know or care what domain they're projecting. That generality is the point.
apercue.ca has been submitted to four W3C Community Groups. The evidence is reviewed by domain experts working on RDF mapping, data governance, and multi-context identity.
CUE as a declarative KG construction language. Use cases PR merged.
Compile-time governance as a lightweight dataspace primitive.
Struct-as-set types for resources participating in multiple contexts simultaneously.
Typed dependency graphs for physical asset lifecycle tracking.