Triples

Now that W3C RDF Star will put Semantic Graphs on-par with Labelled Property Graphs, it is time to address the final barrier, and that is the developer experience. To highlight this, I have produced a new simplified Semantic Web Layer Cake that highlights this capability. In essence, the left side is the traditional path with an open ontological view, and the right is the new path with more constrained and deterministic outcomes. The core technologies are SHACL and GraphQL. SHACL enables the rules to enforce quality and integrity on graph data and empowers industry conformance. In addition, SHACL can also represent classes and properties (using OWL constructs) but without the ontological overheads. GraphQL is the developer-friendly query/mutation interface with the power of introspection that simplifies the graph data interactions. This architecture will enable semantic graph data to flourish as it will provide a better balance between graph knowledge and application development. It would be a good strategy for W3C to investigate as future work to enable the knowledge web of the future. #Knowledge #Graph #RDF #SHACL #GraphQL #W3C

Validating SKOS with SHACL rules is critical for the integrity of graph databases. Below is an example where you have defined a SKOS ConceptScheme (which defines its own Shape to validate that it has used skos:inScheme for all Concepts with the correct ConceptScheme URI) Then you can define your specific Class shape and the relevant property (eg ex:myCategory) where the "value" is an instance of skos:Concept and also fits the node shape of the ConceptScheme shape. #SKOS #SHACL #Graph