Property Graph

Tips

"What should be a Property... Any data element that isn’t frequently used to access the graph directly, has no internal object complexity/multiplicity, and/or needs to always return with the rest of the data in the node is a good candidate for a Property."

http://www.snee.com/bobdc.blog/2018/04/reification-is-a-red-herring.html
- In RDF, "if you want to keep track of separate instances of a particular relationship, declare a class for that relationship and then create instances of it."

https://opencredo.com/blogs/making-sense-of-data-with-rdf-vs-lpg/
- "In property graphs, attribute values are just strings not linked to any other nodes in the graph. They can only represent literal values, rather than relationships and things. In contrast, values of RDF* properties can be both literal values (RDF literals) or nodes connected to other nodes in the graph."
- Capacity to represent edge attributes as nodes. As we mentioned above, unlike attributes in LPGs, RDF* edge attributes can be represented as nodes in the graph, allowing them to be treated as individual entities.
- Better expressivity. RDF* allows every LPG to be efficiently converted into an RDF model. On the other hand, LPGs cannot fully represent RDF* because of the rich expressivity of the latter.
- Arbitrarily complex edge descriptions. With RDF*, graph developers can attach complex descriptions to edges that represent connections to other nodes, literal values (strings), and inter-attribute relationships. In contrast, with LPG, edge properties can only be represented as literal key-value pairs.
https://stackoverflow.com/questions/38034049/is-optionality-mandatory-optional-and-participation-total-partial-are-same/38035173#38035173
- "Application with Cross-Domain Knowledge: RDF*"
- "Applications that Require Fast Search: LPG"
- "Data Provenance: RDF"Representing Temporal Dimension: RDF
- "Data Analytics: RDF*"AsyncAPI

Backlinks

Tips