apercue.ca

Compile-time W3C linked data from typed dependency graphs.

CUE comprehensions precompute all queries. CUE unification enforces all shapes. Every W3C artifact — JSON-LD, SHACL, DCAT, SKOS, OWL-Time — is a zero-cost projection of the same typed graph.

No triplestore. No SPARQL. No runtime validators. Just cue export.

Module: apercue.ca@v0
Source: github.com/quicue/apercue

Quick Start

cue mod init example.com/myproject@v0
# symlink apercue.ca into cue.mod/pkg/
cue eval . -e summary
cue export . -e gaps.shacl_report --out json
cue export . -e cpm.time_report --out json

Module Structure

PackageKey Patterns
vocab/#Resource, #TypeRegistry, JSON-LD @context, #VizData
patterns/#Graph, #CriticalPath, #ComplianceCheck, #CycleDetector, #ConnectedComponents, #Subgraph, #GraphDiff
charter/#Charter, #GapAnalysis, #Milestone
views/#TypeVocabulary (SKOS ConceptScheme)

W3C Spec Coverage

SpecPatternStatus
JSON-LD 1.1@context, @type, @idImplemented
SHACLsh:ValidationReportImplemented
SKOSskos:ConceptSchemeImplemented
EARLearl:AssertionImplemented
OWL-Timetime:IntervalImplemented
Dublin Coredcterms:requiresImplemented
DCAT 3dcat:CatalogPlanned
ODRL 2.2odrl:PolicyPlanned
Hydra Corehydra:ApiDocumentationPlanned

Examples

ExampleDomainResources
course-prereqsUniversity CS degree12 courses, 3 charter gates
recipe-ingredientsCooking (Beef Bourguignon)17 steps, critical path
project-trackerSoftware release10 tasks, status tracking
supply-chainLaptop assembly15 parts, 5 tiers

How Is This Different?

Traditional semantic web:

Data → RDF Triplestore → SPARQL Queries → SHACL Validator → JSON-LD Serializer
(4 runtime components, 4 failure points)

apercue.ca:

Data → cue export -e <projection>
(1 binary, 0 servers, compile-time guarantees)

Apache 2.0 — Source