GraphNews

6069 bookmarks
Newest
The RDF vs. LPG debate has shaped the graph community for years, but it may be pointing at the wrong distinction
The RDF vs. LPG debate has shaped the graph community for years, but it may be pointing at the wrong distinction
I couldn’t help myself. After reading Kurt Cagle's recent post comparing RDF 1.2 to Neo4j, I ended up going down the rabbit hole last night. The RDF vs. LPG debate has shaped the graph community for years, but it may be pointing at the wrong distinction. This short article explores an alternative; treating RDF as a hypergraph composed of interconnected named graphs, where observations, classifications, projections, constraints, and provenance all coexist as part of a single system. In this view, LPG-style structures are not competing models. They are projections within the same framework, tailored for specific analytical needs. By separating assertion from interpretation and embedding data contracts directly into the graph using SHACL, we can focus less on formats and more on how to manage and compose graph-based knowledge in a consistent way. I'm looking forward to exploring some code-forward examples in the next few weeks, and folding in the evolving SHACL 1.2 spec.
The RDF vs. LPG debate has shaped the graph community for years, but it may be pointing at the wrong distinction
·linkedin.com·
The RDF vs. LPG debate has shaped the graph community for years, but it may be pointing at the wrong distinction
Jens Jorgenson's Design Ontology Spec is a YAML file that defines your product's nouns, verbs, and composition rules before any code gets written
Jens Jorgenson's Design Ontology Spec is a YAML file that defines your product's nouns, verbs, and composition rules before any code gets written
Jens Jorgenson's Design Ontology Spec is a YAML file that defines your product's nouns, verbs, and composition rules before any code gets written
·linkedin.com·
Jens Jorgenson's Design Ontology Spec is a YAML file that defines your product's nouns, verbs, and composition rules before any code gets written
opencypher-compliance
opencypher-compliance
A package to scan Cypher queries before you port them between different graph databases. At the time of writing, the package measures compliance against the openCypher 9 specification across four graph database vendors:
·github.com·
opencypher-compliance
Semantic Foundations for AI-Ready Data: Why Governed Semantics, Open Standards, and Data Products Are the Prerequisites for Enterprise AI
Semantic Foundations for AI-Ready Data: Why Governed Semantics, Open Standards, and Data Products Are the Prerequisites for Enterprise AI
White Paper: "Semantic Foundations for AI-Ready Data: Why Governed Semantics, Open Standards, and Data Products Are the Prerequisites for Enterprise AI.," Synthesized with Claude Opus 4.6 (with guardrails) from Gartner D&A Summit 2026 proceedings, Gartner research publications, and industry analysis.
Semantic Foundations for AI-Ready Data: Why Governed Semantics, Open Standards, and Data Products Are the Prerequisites for Enterprise AI
·linkedin.com·
Semantic Foundations for AI-Ready Data: Why Governed Semantics, Open Standards, and Data Products Are the Prerequisites for Enterprise AI
What is the Difference Between a Semantic Layer and a Context Layer? When to Use a Knowledge Graph vs. a Context Graph - Enterprise Knowledge
What is the Difference Between a Semantic Layer and a Context Layer? When to Use a Knowledge Graph vs. a Context Graph - Enterprise Knowledge
The shift from "finding data" to "reasoning and understanding context" is the driver for a more robust context layer that needs to provide the operational nuances that are typically locked within systems, teams, and organizational silos.
·enterprise-knowledge.com·
What is the Difference Between a Semantic Layer and a Context Layer? When to Use a Knowledge Graph vs. a Context Graph - Enterprise Knowledge