- From: Pat Hayes <phayes@ihmc.us>
- Date: Wed, 16 May 2007 12:53:31 -0700
- To: samwald@gmx.at
- Cc: public-semweb-lifesci@w3.org, Eric.Jain@isb-sib.ch
> > I really would suggest the named graphs would be a better >> underpinning. Unlike reification, they do have a full semantics and a >> clear deployment model, and they follow in a long tradition of naming >> document-like semantic entities. And unlike RDF reification, they are >> not widely loathed, and they are fairly widely supported. > >Well, they are not supported by RDF/XML, which >(unfortunately) is the main serialization format >of RDF. Our paper suggests that the URI of the RDF/XML document be used as the name in this case. This works as long as you are consistent about it. Or, you could introduce 'naming RDF' documents whose sole purpose is to have a stable URI as the graph name and which then reference (eg by importing) the documents making up the intended graph. >Named graphs ARE supported by most triplestores, >but they are mostly already reserved for other >uses, like the representation of provenance >based on the RDF files that the triples were >loaded from. Reserved? In what sense? a single URi can have multiple properties and hence multiple uses. >I think we are also lacking a standard >vocabulary for graph - subgraph relations Indeed we are. This is a widely noted lack. Pat >, which would be needed if we want to represent graphs within graphs. > >-- Matthias > > > > >. >-- >Psssst! Schon vom neuen GMX MultiMessenger gehört? >Der kanns mit allen: http://www.gmx.net/de/go/multimessenger -- --------------------------------------------------------------------- IHMC (850)434 8903 or (650)494 3973 home 40 South Alcaniz St. (850)202 4416 office Pensacola (850)202 4440 fax FL 32502 (850)291 0667 cell phayesAT-SIGNihmc.us http://www.ihmc.us/users/phayes
Received on Wednesday, 16 May 2007 19:53:45 UTC