Semantic Web vs. Property Graphs
michaeldebellis.com · 801 words · saved by 1 readers
Discusses the pros and cons of property graphs (Neo4J and Cypher) contrasted with the Semantic Web stack: RDF, OWL, SPARQL, SHACL, SWRL
A question that I often hear is whether developers should use property graphs or the Semantic Web stack. Property graphs, especially Neo4j and Cypher , have received a lot of attention recently and Neo4j is an excellent product but I think there are many good reasons for using the Semantic Web stack. First, to be clear property graphs provide about the same functionality as RDF. Both are languages for defining graphs, both have a query language specifically designed for their graphs (Cypher and SPARQL). The main differentiator for property graphs over RDF is the ability to have attributes/rela
related reading
- Semantic Weben.wikipedia.org
- SPARQLen.wikipedia.org
- Provenance-Aware Knowledge Representation: A Survey of Data Models and Contextualized Knowledge Graphslink.springer.com
- Demystifying ontologies: What ontologies really do in knowledge graphslinkedin.com
- [2003.02320] Knowledge Graphsarxiv.org
- What is a SEMANTIC Knowledge Graph?linkedin.com
- Against SQLscattered-thoughts.net
- The GraphRAG manifesto: Adding knowledge to GenAIneo4j.com
- Airtraceairtrace.io
- How does Atomic Data relate to Graph Databases?docs.atomicdata.dev
- QuickGraph#9 The fashion Knowledge Graph. Inferencing with Ontologies in Neo4j – Jesús Barrasajbarrasa.com
- Revolutionizing Semantic Search with RAG and Knowledge Graphslinkedin.com