Hi Karl,
Apache Jena is based on RDF and linked data.
The graph data model is different to Tinkerpop's which is property
graphs. Neo4j provides property graphs with extensions.
RDF - a W3C standard, along with SPARQL, an RDF Query language are not
based on property graphs.
Property Graphs and RDF come from different heritages; addressing
different problems.
Data modelling is very important in the RDF view of the world - writing
down what the data means. This goes with publishing because it means the
data says what the data means to whoever is consuming it. In publishing,
you don't know the app/people are reading the data.
RDF uses URIs because globally unique names, that you can look up to
know what they are naming, are important for publishing data and for
data integration of disparate systems,often systems not under the
control of the group doing the integration.
Property graphs are more aimed at capture and processing rather than
modelling and integration. Currently, especially in analytics (where
the $$$ around processing is). Applications and database are built
together for a defined purpose.
Andy
https://www.slideshare.net/andyseaborne/two-graph-data-models-rdf-and-property-graphs
On 05/09/17 22:42, Karl Pietrzak wrote:
Hello everyone!
I'm trying to familiarize myself with JENA / Tinkerpop /etc., and I'm
trying to figure out where JENA hits into the Tinkerpop "ecosystem".
Would it be a "data system provider
<http://tinkerpop.apache.org/providers.html#data-system-providers>" like
neo4j because of TDB?
But it seems like Fuseki
<http://jena.apache.org/documentation/fuseki2/fuseki-run.html> provides an
HTTP layer on top of Tinkerpop, putting it in competition with Gremlin
Server <http://tinkerpop.apache.org/docs/3.3.0/reference/#gremlin-server>?
Any hints would be greatly appreciated.
Thank you!
