(via: late2theparty:)
This is a VERY (very) well written introduction to RDF and it’s relevance to the NoSQL movement. The article stresses that RDF is, currently (as of April 2010), the only NoSQL solution that is standardised upon, which includes the ability to query it via an SQL-like query interface, such as SPARQL.
If you like to see a small N-Triples (an RDF export format) and SPARQL sample, see this stackoverflow post. Given [from stackoverflow]:
1 <- 2 -> 3
3 <- 4 -> 5
these are already subject predicate object form so just slap some URI notation on it, load it in the triple store and query at-will via SPARQL. Here it is in NT (N-Triples) format:
<http://mycompany.com#1> <http://mycompany.com#2> <http://mycompany.com#3> .
<http://mycompany.com#3> <http://mycompany.com#4> <http://mycompany.com#5> .
Now query for all nodes two hops from node 1:
SELECT ?node
WHERE {
<http://mycompany.com#1> ?p1 ?o1 .
?o1 ?p2 ?node .
}
This would of course yield <http://mycompany.com#5>.
What the example query is doing is identifying data associated with the specified input RDF ‘node’, and then requesting an RDF node adjacent to this node within another RDF triple/axis (forgive my terminology).
A notable RDF ‘store’ mentioned in the [comments of] the post above is Bigdata store, which is hailed as scaling very well (it is free and open-source).
Java RDF access libraries include Jena and Sesame, which intern should be accessible via JVM-compatible languages such as Scala.
