One typed CUE value, projected to
13 W3C specifications (8 full, 5 partial), plus Dublin Core and schema.org, as
compile-time projections of the same typed dependency graph.
No triplestore. For large graphs the closure is precomputed by
tools/toposort.py and CUE verifies and projects it.
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, OWL-Time, PROV-O, ODRL, Activity Streams, W3C Org,
DCAT and more, plus Dublin Core and schema.org terms. 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 (PROV-O, ODRL, ORG, schema.org, VC and Activity Streams) reimplemented in JavaScript and computed in the browser 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.
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.
Each spec is a CUE comprehension that projects the same underlying graph. No adapters. No converters. The data is the standard.
| Spec | CUE Pattern | Depth | Status |
|---|---|---|---|
| Core projections | |||
| JSON-LD 1.1 | vocab/context.cue | Full | Implemented |
| SHACL | validation.cue, charter.cue | Full | Implemented |
| SKOS | views/skos.cue, lifecycle.cue | Full | Implemented |
| EARL | lifecycle.cue (test plan only: every outcome is earl:untested) | Partial | Projection |
| OWL-Time | analysis.cue | Full | Implemented |
| Dublin Core (DCMI, not W3C) | vocab/context.cue | Vocabulary | Implemented |
| Extended projections | |||
| PROV-O | provenance.cue | Full | Implemented |
| schema.org (not W3C) | schema_alignment.cue | Vocabulary | Implemented |
| ODRL 2.2 | policy.cue | Partial | Implemented |
| Activity Streams 2.0 | activity.cue | Partial | Implemented |
| Verifiable Credentials 2.0 | credentials.cue (unsigned credential shape, no proof) | Structural | Projection |
| W3C Org | views/org.cue | Partial | Implemented |
| VoID | void.cue | Full | Implemented |
| RDFS/OWL | ontology.cue | Partial | Implemented |
| Web Annotation | annotation.cue | Partial | Implemented |
| DQV | quality.cue | Full | Implemented |
| DCAT 3 | catalog.cue | Full | Implemented |
| Downstream (in quicue.ca) | |||
| Hydra Core | quicue.ca operator | Partial | Downstream |
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 evaluates, its shapes are valid. Constraint violations are evaluation 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.
Two W3C Community Groups have a public artifact from this project: KG-Construct and Dataspaces. The other two are drafted.
Use cases contributed to the KG-Construct CG.
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.