RDF 1.2 Status Report
KGC 2026
•
30m
https://drive.google.com/file/d/1BZnMLbRIH0ZU-8ulqUZ9oCeqI1ZjGE1y/view?usp=share_link
Joint proposal with Adrian Gschwend and Pierre-Antoine Champin
RDF 1.2 is the culmination of years of work on improving the usability of reification in RDF. As the W3C RDF and SPARQL Working Group is nearing the end of its work, it is a good time to summarize what has been done and what the new standard will look like.
Reification in RDF is a historical feature that enables “statements about statements”. It was introduced with the very first draft version of RDF, but has always remained poorly understood and unpopular mainly because it is considered cumbersome (but also because its semantics were never properly defined). About 10 years ago, work emerged under the rubric “Reification Done Right”, eventually becoming the current work stream at W3C (long dubbed “RDF-star”). The improvements can also be seen as a way to provide functionality that Labeled Property Graph advocates have long claimed RDF does not have.
The W3C working group has labored hard to accommodate the different aspirations and viewpoints of “fixing reification”, and last year finally reached consensus. All existing RDF specifications have been updated to introduce a new term type, “triple terms”, into RDF, as well as providing syntactic shorthand for making it very easy to leverage the new feature. In addition, several other details in RDF 1.1 have been “fixed” or updated.
This presentation gives an overview of the new standard and offers an opportunity for the audience to ask any questions they might have.
Up Next in KGC 2026
-
Ensuring Customer Data Integrity with...
AI, graph analytics, and enterprise database features simplify building intelligent, connected applications. Hear from Industrial Scientific, a world leader in gas detection for worker safety programs, who was facing data integrity challenges because of data inconsistencies across multiple system...
-
Multi-Modal Knowledge Graphs for Agents
Most multimodal RAG stacks have a “split-brain” design: embeddings in a vector DB, relationships in a graph DB, and images/video/audio in blob storage. For an agent, that becomes a slow three-hop loop—similarity search, graph traversal, then a network fetch to load the actual frames for a VLM. Th...
-
How Graph Technology Reveals the Real...
https://drive.google.com/file/d/16JcyI8agX69uv4bGb_oV1LCuR-tzSmhZ/view?usp=share_link
Behind every public market lies an invisible network of investors, investees, and shared board seats — relationships. This talk shares how we combined Amazon Neptune's graph database capabilities with Linkuriou...