Re: Generic "Graph" Use Cases

Richard Cyganiak wrote:
> On 7 Mar 2011, at 09:56, Nathan wrote:
>>>>>>> RDF datasets don't address the assertions about graphs UC very well.
>>>>>>> They can - with careful graph naming (naming the g-snap, not the g-box), the default graph can contain assertions about the properties of a graph, just like graph literals can be used for RDF datasets.  It's just there is "some assemble required".
>>>>>> There's a very critical detail here, the need to talk about a g-box, and the need to talk about a g-snap
>>>>> Just to be sure we're on the same page in this discussion, can you give an example for “talking about a g-box” and one for “talking about a g-snap”, in particular one where the distinction matters?
>>> I'd still be very interested in seeing an example for “talking about a g-box” and one for “talking about a g-snap”, in particular one where the distinction matters.
>> talking about a g-box:
>> every use case where the subject/object of a triple is a graph name or an information resource (for instance, VoID).

@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix foaf: <http://xmlns.com/foaf/0.1/> .
@prefix dcterms: <http://purl.org/dc/terms/> .
@prefix void: <http://rdfs.org/ns/void#> .

:DBpedia rdf:type void:Dataset ;
          foaf:homepage <http://dbpedia.org/> .

:DBLP rdf:type void:Dataset ;
       foaf:homepage <http://www4.wiwiss.fu-berlin.de/dblp/all> ;
       dcterms:subject <http://dbpedia.org/resource/Computer_science> ;
       dcterms:subject <http://dbpedia.org/resource/Journal> ;
       dcterms:subject <http://dbpedia.org/resource/Proceedings> .

:DBpedia void:subset :DBpedia2DBLP  .

:DBpedia2DBLP rdf:type void:Linkset ;
               void:target :DBpedia ;
               void:target :DBLP .

>> talking about a g-snap:
>> every use case where the subject/object of a triple should be a set of triples. (everything from adding provenance, tracking changes, through to annotations).

@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix swp: <http://www.w3.org/2004/03/trix/swp-1/> .
@prefix dc: <http://purl.org/dc/elements/1.1/> .
@prefix ex: <http://www.example.org/vocabulary#> .
@prefix : <http://www.example.org/exampleDocument#> .
:G1 { :Monica ex:name "Monica Murphy" .
       :Monica ex:homepage <http://www.monicamurphy.org> .
       :Monica ex:email <mailto:monica@monicamurphy.org> .
       :Monica ex:hasSkill ex:Management }

:G2 { :Monica rdf:type ex:Person .
       :Monica ex:hasSkill ex:Programming }

:G3 { :G1 swp:assertedBy _:w1 .
       _:w1 swp:authority :Chris .
       _:w1 dc:date "2003-10-02"^^xsd:date .
       :G2 swp:quotedBy _:w2 .
       :G3 swp:assertedBy _:w2 .
       _:w2 dc:date "2003-09-03"^^xsd:date .
       _:w2 swp:authority :Chris .
       :Chris rdf:type ex:Person .
       :Chris ex:email <mailto:chris@bizer.de> }

although the above is ambiguous, perhaps less ambiguous written as:

@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix swp: <http://www.w3.org/2004/03/trix/swp-1/> .
@prefix dc: <http://purl.org/dc/elements/1.1/> .
@prefix ex: <http://www.example.org/vocabulary#> .
@prefix : <http://www.example.org/exampleDocument#> .

{ :Monica ex:name "Monica Murphy" .
   :Monica ex:homepage <http://www.monicamurphy.org> .
   :Monica ex:email <mailto:monica@monicamurphy.org> .
   :Monica ex:hasSkill ex:Management }
     swp:assertedBy [
      swp:authority :Chris;
      dc:date "2003-10-02"^^xsd:date ] .

{ :Monica rdf:type ex:Person .
   :Monica ex:hasSkill ex:Programming } swp:quotedBy _:w2 .

: swp:assertedBy _:w2 .

_:w2 dc:date "2003-09-03"^^xsd:date ; swp:authority :Chris .
:Chris rdf:type ex:Person ; ex:email <mailto:chris@bizer.de> }

> What I'm looking for is an example, not a definition :-)

clearer?

Received on Monday, 7 March 2011 11:05:48 UTC