Hi Chris,
> However, this doesn't technically represent any statements about
> statements (i.e. metadata). How would I add a statement, explaining
> the attribution of each of these statements and the time when they
> were added? For example, if the first statement was "entered-by" a
> specific person on a specific date, I would represent this in RDF
> like:
Peter's example was just showing you the basics of getting an RDF
store going over Neo4j. He did not get into the complications of
reification (statements about statements).
You will need to use Sail quad store functionality. This is where you
have named graphs and you can make statements about named graphs.
Such issues are for an RDF mailing list. However, here is some
specifics in very brief notations so I don't have to type so much:
a knows b g1
b likes c g2
These are two quads -- spog. You can now make reference to the forth
component called the 'named graph' or 'context.'
a believes g2 g1
Thus, a is asserting that he believes that b likes c.
This is all possible through Blueprints Sail which is the binding you
can use to easily make Neo4j an RDF quad store. Blueprints Sail just
binds the Sail API to Neo4j. You will not think "Neo4j" in this
context, you will think "Sail." Sail is pretty standard Java-based RDF
API developed by OpenRDF. Thus, you should learn about Sail:
http://www.openrdf.org/documentation.jsp
Really fast. To add quads:
sailConnection.addStatement(new URIImpl(a), new URIImpl(knows), new
URIImpl(b), new URIImpl(g1));
To query quads, where null acts as a wildcard:
sailConnection.getStatements(new URIImpl(a), null, null, null);
Hope that gets you started.
Good luck with your project,
Marko.
http://markorodriguez.com
_______________________________________________
Neo4j mailing list
[email protected]
https://lists.neo4j.org/mailman/listinfo/user
