TriG-REST

From RDF Working Group Wiki
Revision as of 16:32, 8 February 2012 by Gschreib (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Solution design

From message of Sandro, 4 Jan 2012:

 http://lists.w3.org/Archives/Public/public-rdf-wg/2012Jan/0021.html

Semantics of the name-graph relationship

The graph name is an IRI. This IRI represents a graph container. A GET operation on the IRI fetches the triples of this graph container.

Use-case examples deploying this solution

UC: access to crawler data, not time dependent

@@ ref needed, presented by cygri at 21 Dec meeting

Several systems want to use the data gathered by one RDF crawler. They don't need simultaneous access to older versions of the data.

Solution: use TriG or N-Quads with the fourth column (graph label) being the URL the content was fetched from.

 <http://example.org> 
   { ... triples recently fetched from there }

UC: access to crawler data, time dependent

Several systems want to use the data gathered by one RDF crawler. They need simultaneous access to older versions of the data.

Solution: use TriG or N-Quads with the fourth column being some identifier created at the time the retrieval was done. Then, some other data connects that identifier with the URL the content was fetched from.

 <http://crawler.example.org/r8571> 
   { ... triples fetched in retrieval 8671 }
       
 { 
   <http://crawler.example.org/r8571> 
     eg:source <http://example.org>;
     eg:date "2011-01-04T00:03:11"^^xs:dateTime
 }