- From: Pat Hayes <phayes@ihmc.us>
- Date: Wed, 12 Oct 2011 20:55:05 -0500
- To: Sandro Hawke <sandro@w3.org>
- Cc: public-rdf-wg <public-rdf-wg@w3.org>
I like all of these, though the explicit time-talk in 3. still makes my hair stand on end. Pat On Oct 12, 2011, at 4:04 PM, Sandro Hawke wrote: > Some of us kept talking for a few more hours. Everyone was > more-or-less cool with these observations about dereference: > > 1. If a system successfully dereferences URL "L" and obtains a > representation of an RDF graph, then <L> is a GraphContainer. That > is, "L" denotes a GraphContainer. Logically, GraphContainer is > disjoint from foaf:Person (I think!!) so a document that includes "<> > a foaf:Person" is (by this proposal) logically inconsistent with it > being served on the Web. > > 2. So, owl:Ontology heavily overlaps GraphContainer. It might even be > a subclass of it. (Many OWL ontologies say "<> a owl:Ontology", where > the <> will be resolved to the address the ontologies is fetched from, > aka L.) > > 3. Some GraphContainers, "SerialGraphContainers" are functions mapping > from time to RDF Graphs. We can talk about next & previous & current > RDF Graphs in a SerialGraphContainer, but not about GraphContainers in > general. (cf facebook's api for fetching RDF data, which returns > different RDF data depending on your credentials). > > 4. A ConstantGraphContainer always holds the same RDF Graph. This can > be used for when you want to attach a dereferenceable URL to a g-snap. > You put it in a ConstantGraphContainer. > > > > > > ------------------------------------------------------------ IHMC (850)434 8903 or (650)494 3973 40 South Alcaniz St. (850)202 4416 office Pensacola (850)202 4440 fax FL 32502 (850)291 0667 mobile phayesAT-SIGNihmc.us http://www.ihmc.us/users/phayes
Received on Thursday, 13 October 2011 01:55:36 UTC