CONCEPT Cited by 1 source
SHACL (Shapes Constraint Language)¶
Definition¶
SHACL — Shapes Constraint Language — is the W3C standard for expressing validation constraints over RDF graphs. A SHACL shape describes a class of target nodes and the constraints they must satisfy (required properties, cardinalities, value types, patterns, cross-property dependencies). A SHACL validator reports conformance + violations for a given data graph against a given shapes graph.
SHACL sits in the semantic-web stack alongside RDF and complements ontology languages (RDFS / OWL) — ontology defines what things mean, SHACL defines what things are required to look like.
Role in UDA¶
Netflix UDA chose "RDF and SHACL as the foundation" for its knowledge graph (sources/2025-06-14-netflix-model-once-represent-everywhere-uda). SHACL contributes shape / constraint primitives that Upper builds on + generalises for enterprise domain-modelling.
Known limitation UDA had to work around¶
The Netflix post flags a concrete SHACL gap explicitly:
"SHACL is not a modeling language for enterprise data. Designed to validate native RDF, SHACL assumes globally unique URIs and a single data graph. But enterprise data is structured around local schemas and typed keys, as in GraphQL, Avro, or SQL. SHACL could not express these patterns, making it difficult to model and validate real-world data across heterogeneous systems."
Translation:
- Global-URI assumption. SHACL expects every instance to have a globally unique URI. Real enterprise data keys records by local IDs (customer ID in System A, employee ID in System B)
- context — not by URIs.
- Single-graph assumption. SHACL's validation semantics operate on one data graph; enterprise data is spread across many systems, each with its own graph.
- Typed-key patterns unexpressed. GraphQL / Avro / SQL all use strongly-typed composite keys that aren't native SHACL constructs.
UDA's response: wrap a restricted SHACL subset inside Upper + generalise it for typed keys, local schemas, and cross-graph / cross-container validation.
Why the wiki cares¶
SHACL is the named shape-validation standard beneath an in- production enterprise knowledge graph (UDA) and the place where a real-world deployment had to deliberately extend and generalise the W3C primitive to fit enterprise data. This is the wiki's canonical "W3C-on-the-theory, custom-framework-on-the- deployment" note for shape validation.
Seen in¶
- sources/2025-06-14-netflix-model-once-represent-everywhere-uda — Netflix UDA foundational layer + enumerated limitation when applied to enterprise data.
Related¶
- concepts/rdf — SHACL validates RDF graphs.
- concepts/named-graph — the partitioning primitive that surfaces SHACL's single-graph-assumption problem.
- concepts/knowledge-graph · concepts/domain-model — the structures SHACL helps validate.
- concepts/upper-ontology — Upper restricts + generalises SHACL for enterprise domain modelling.
- concepts/semantic-interoperability — the goal SHACL partially serves.
- systems/netflix-uda · systems/netflix-upper — the deployment on the wiki.