Hey Norbert,
> I'm wondering why Neo4j provides an API based on a property graph model and
> is not using the classical graph approach G<V,E>?
> What are the advantages of this architecture? Any thoughts? Is Neo4j
> internally really based upon a property graph?
> What are the disadvantages of a property graph?
The ordering of ease of modeling for binary graph data structures is in a
hierarchy like this:
G = (V,E \subseteq {V \times V}) (undirected graph)
G = (V, E \subseteq (V \times V)) (directed graph)
G = (V, E \subseteq (V \times V), \Omega: E -> \Sigma)
(multi-relational graph)
G = (V, E \subseteq (V \times V), \Omega: E -> \Sigma, P : (V \cup E)
-> (\Sigma \times U) (property graph)
RDF is a multi-relational graph. The benefit of the multi-relational graph over
the property graph is that it more straightforward when it comes to modeling --
e.g. In property graph modeling, you tend to be confronted with this question:
"Is this a property or another vertex?") at the expense of verbosity ("How do I
model edge weight with a multi-relational graph?")
However, in theory, what you can express with a property graph, you can express
with an undirected graph.
http://arxiv.org/abs/0804.0277
Are you talking strictly in terms of expressivity in modeling, or other
"compute physics" oriented issues?
See ya,
Marko.
http://markorodriguez.com
_______________________________________________
Neo4j mailing list
[email protected]
https://lists.neo4j.org/mailman/listinfo/user
