W3C home > Mailing lists > Public > www-rdf-interest@w3.org > September 2004

Re: Reification - whats best practice?

From: Leo Sauermann <leo@gnowsis.com>
Date: Wed, 08 Sep 2004 20:11:22 +0200
Message-ID: <413F4B4A.9060401@gnowsis.com>
To: Patrick.Stickler@nokia.com
CC: tpassin@comcast.net, www-rdf-interest@w3.org

When partick posts, it is always a good time to join my thread again:-)

>Well, technically, I don't see named graphs requiring any
>change to the RDF MT. It's really just about packaging and
>management by particular systems.
>
>Since named graphs are named by URIs, one can say what one
>likes about them. And per your suggestion above, one could
>also expect to have access to representations of those graphs
>via their URIs, and a common representation would be an RDF/XML
>serialization of the statements contained in that graph.
>  
>

That sounds like a fair approach. Your above ideas are technically 
logical, but I think too complicated
("at one time defined a subclass of rdf:Statement called rdfx:Assertion 
which corresponded to the reification of an asserted triple, ")
-this sounds like a long hacking night....

The thing with the named graph can be explained in a few words, thats 
what i like about it.

My use of this tech would look like this:

Documents do not exist in my thinking, I like Resources identified by URIS.
Such a resource can "contain" triples, like this email, I could add a 
few triples here:
leo kiss:kissed ingrid. (aka the first kissology triple)
Now this triple would be in the "named graph" identified by the uri of 
this mail (which is some email-message identifier)

If somehow the resource changes (i write some other triples here too) 
they would also be in the graph.

If someone has only the uri of the mail, he can get the triples somehow 
- some tech like gnowsis required.

If someone sees the triple in a triplestore, she could look the named 
graph/resource that caused the triple to exist.

So if I stumble accross a triple like
leo kiss:kissed crschmidt
I could see who sais things like this

(We actually had the problem that i kissed crschmidt because Julie, his 
IRC bot had a bug. And we didn't know where the triple came from, no 
source uri attached...)

all this sounds like it could work in the real world.

fellows and fellerines, who writes the triplestore that can this stuff 
and has a good jena interface? :-)

cheers
LEo

>The missing machinery is mostly on the query/processing side,
>or with the interchange of multiple graphs via a single
>serialization (which isn't technically manditory, since
>one could use multipart MIME and have each graph serialized
>separately using RDF/XML); not so much on the MT side.
>
>Patrick
>
>
>
>  
>
Received on Wednesday, 8 September 2004 18:11:42 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:52:09 GMT