4 ms·

Before using RDF for graphs one should inform themselves on the differences between labeled property graphs and triple stores, and choose the model that best fi

by rapnie 7y ago

Before using RDF for graphs one should inform themselves on the differences between labeled property graphs and triple stores, and choose the model that best fit their use case. Take your time and beware of objectivity of article. Vendors try to lure you in. Following has some good info (but a Neo4j bias): https://dzone.com/articles/rdf-triple-stores-vs-labeled-property-graphs-whats https://dzone.com/articles/rdf-triple-stores-vs-labeled-prop...

emmanueloga_ 7y ago
Good point. Funny you mention that article: I remember encountering both that article and another one that provides some counterpoints! [1] Also, both those articles are a bit old: RDF* ([2],[3]) is a new extension for RDF that makes it easier to accomplish the same kind of things you can do with property graphs. RDF4j has support for RDF* in the roadmap! [4]. To me, the fact that RDF is 1) a simpler and more general model and 2) an open standard with multiple free and commercial implementations; makes RDF a more a attractive option than locking into a single proprietary implementation like Neo4j. -- 1: http://www.snee.com/bobdc.blog/2018/04/reification-is-a-red-herring.html http://www.snee.com/bobdc.blog/2018/04/reification-is-a-red-... 2: http://olafhartig.de/slides/RDFStarInvitedTalkWSP2018.pdf http://olafhartig.de/slides/RDFStarInvitedTalkWSP2018.pdf 3: http://blog.liu.se/olafhartig/2019/01/10/position-statement-rdf-star-and-sparql-star/ http://blog.liu.se/olafhartig/2019/01/10/position-statement-... 4: https://github.com/eclipse/rdf4j/issues/1484 https://github.com/eclipse/rdf4j/issues/1484
zozbot234 7y ago
RDF is an interoperability mechanism, it has nothing to do with the architecture you use internally for your database. You can have a PostgreSQL database and offer an endpoint for querying it via RDF.

4 ms·

Before using RDF for graphs one should inform themselves on the differences between labeled property graphs and triple stores, and choose the model that best fi

by rapnie 7y ago

emmanueloga_ 7y ago
Good point. Funny you mention that article: I remember encountering both that article and another one that provides some counterpoints! [1] Also, both those articles are a bit old: RDF* ([2],[3]) is a new extension for RDF that makes it easier to accomplish the same kind of things you can do with property graphs. RDF4j has support for RDF* in the roadmap! [4]. To me, the fact that RDF is 1) a simpler and more general model and 2) an open standard with multiple free and commercial implementations; makes RDF a more a attractive option than locking into a single proprietary implementation like Neo4j. -- 1: http://www.snee.com/bobdc.blog/2018/04/reification-is-a-red-herring.html http://www.snee.com/bobdc.blog/2018/04/reification-is-a-red-... 2: http://olafhartig.de/slides/RDFStarInvitedTalkWSP2018.pdf http://olafhartig.de/slides/RDFStarInvitedTalkWSP2018.pdf 3: http://blog.liu.se/olafhartig/2019/01/10/position-statement-rdf-star-and-sparql-star/ http://blog.liu.se/olafhartig/2019/01/10/position-statement-... 4: https://github.com/eclipse/rdf4j/issues/1484 https://github.com/eclipse/rdf4j/issues/1484
zozbot234 7y ago
RDF is an interoperability mechanism, it has nothing to do with the architecture you use internally for your database. You can have a PostgreSQL database and offer an endpoint for querying it via RDF.