W3C home > Mailing lists > Public > public-rdf-wg@w3.org > December 2011

Re: Graph-State Resources (was Re: graphs and documents Re: [ALL] agenda telecon 14 Dec)

From: Sandro Hawke <sandro@w3.org>
Date: Thu, 15 Dec 2011 18:21:26 -0500
To: Pat Hayes <phayes@ihmc.us>
Cc: Richard Cyganiak <richard@cyganiak.de>, David Wood <david@3roundstones.com>, Tim Berners-Lee <timbl@w3.org>, Guus Schreiber <guus.schreiber@vu.nl>, RDF WG <public-rdf-wg@w3.org>
Message-ID: <1323991286.6252.1224.camel@waldron>
On Thu, 2011-12-15 at 17:15 -0600, Pat Hayes wrote:
> I see your reasoning, but these are all just too long and geeky, and unpronounceable. How about Thing Whose state Is a Graph, or TWIG. Then we can talk about RDF TWIGs, which trips off the tongue easily.

Not bad.    Keep tryin'  :-)

     - s

> Pat
> 
> On Dec 14, 2011, at 5:03 PM, Sandro Hawke wrote:
> 
> > On Wed, 2011-12-14 at 15:20 -0600, Pat Hayes wrote:
> >> On Dec 14, 2011, at 2:31 PM, Sandro Hawke wrote:
> >> 
> >>> 
> >>> Any ideas for a better term?
> >> 
> >> 
> >> My original suggestion for g-box was "RDF Resource". 
> > 
> > That was my first thought, on this problem, too, but I think the term is
> > too ambiguous.  To all the current RDF users, an RDF Resource is an
> > rdfs:Resource, aka anything.   So I think we need something more like
> > "RDF-Emiting Resource."   But in the REST terminology, the resources
> > don't emit something, they just have representations (serializations) of
> > their state transmitted.   The things are passive.   If, when prodded,
> > they emit an RDF serialization, then by REST, that means their state was
> > an RDF Graph.    So, Resources Whose State is an RDF Graph.   Or "RDF
> > Graph-State Resources".   Or just "Graph-State Resources" in a context
> > where RDF is implied....
> > 
> > That's my reasoning.
> > 
> >> I still think this most neatly captures the intention: a REST resource (a proddable Web thingie which emits representations of its state when prodded) whose representations are (parsable into) RDF graphs. If this is too gnomic, then "RDF Graph Resource" would do. It needs to have "RDF" in it somewhere. 
> >> 
> >> BTW, I have always thought of a g-box as something which emits graphs when prodded, rather than being restricted to a simple container. So +1 to this generalization, if it is a generalization. 
> > 
> > Yes, I resisted that, mostly because I didn't like REST.  I found a box
> > a much simpler concept.   But I've given up on that resistance, and am
> > finding the idea of
> > something-with-an-RDF-Graph-as-its-State-as-far-as-Web-Clients-are-concerned is pretty simple, too.
> > 
> >     -- Sandro
> >> Pat
> >> 
> >> ------------------------------------------------------------
> >> 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
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> > 
> > 
> > 
> > 
> 
> ------------------------------------------------------------
> 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, 15 December 2011 23:23:45 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 16:25:46 GMT