You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+27-26Lines changed: 27 additions & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,16 +45,16 @@ Property graph values must be converted into RDF values and vice versa. Blazegr
45
45
46
46
Blazegraph accepts user-supplied IDs (strings only) for vertices and edges. If no id is supplied a UUID will be generated. By default, TP3 ids and property keys are converted into URIs by prepending a <blaze:> namespace prefix. Property values are simply converted into datatyped literals.
47
47
48
-
Two fixed URIs are used and provided by the BlazeValueFactory to represent element labels (rdfs:label by default) and property values for Cardinality.list vertex properties (rdf:value by default). These can also be overriden as desired.
48
+
Two fixed URIs are used and provided by the BlazeValueFactory to represent element labels (rdf:type by default) and property values for Cardinality.list vertex properties (rdf:value by default). These can also be overriden as desired.
49
49
50
50
Property graph elements are represented as follows in Blazegraph:
51
51
52
52
# BlazeVertex john = graph.addVertex(T.id, "john", T.label, "person");
Vertices requires one statement, edges require two.
60
60
@@ -84,34 +84,34 @@ Cardinality.list uses a specially datatyped and monotonically increasing interna
84
84
85
85
Here is how the Tinkerpop3 "Crew" dataset looks when loaded into Blazegraph. Human-friendly IDs have been assigned to vertices and edge UUIDs have been abbreviated to 5 characters for brevity.
Currently **BlazeGraphEmbedded** is the only concrete implementation of the Blazegraph Tinkerpop3 API. BlazeGraphEmbedded is backed by an embedded (same JVM) instance of Blazegraph. This puts the enterprise features of Blazegraph (high-availability, scale-out, etc.) out of reach for the 1.0 version of the TP3 integration, since those features are accessed via Blazegraph's client/server API. A TP3 integration with the client/server version of Blazegraph is reserved for a future blazegraph-tinkerpop release.
@@ -439,11 +440,11 @@ Sample usage of this API can be found in SampleCode.demonstrateSparqlAPI(). Thi
0 commit comments