On 13/12/2020 19:34, Laura Morales wrote:
What's your interest in RDF*?
...
Another issue for me with property graphs, but I would like to hear your feedback on this, is that
properties are indexed globally and it's my understanding that they only accept one data type (eg.
Integer). So I'm not sure how indexing work over there from a storage point of view. I think they
would require me to define 2 properties instead of one or some kind of namespace, let's say
"ns1_age" and "ns2_age" where one property takes Integer and the other one
String for example. Which, at the end of the day, is the same thing as using RDF prefixes.
The two styles of graphs - labelled property graphs (LPG) and RDF - have
different heritages and usage and it shows.
The RDF ecosystem is about modelling, mergeable data, variety and scale
in a web style - i.e. distributed and multi-publisher with a strong
emphasis of being able to exchange data without messing up. So, for
example, data format standards matter a lot and system support and
fidelity of implementation for formats is very high. Users go "this
data does not work on that system" and submit bug reports - in LPG,
no-one is surprised if data doesn't transfer without preparation.
LPG comes from data analytics, data ingestion and ETL. There isn't a
shared data model and LPG systems have differences. The idea of smushing
data from different places together just isn't on their list of primary
use cases.
Andy
