W3C home > Mailing lists > Public > public-rdf-dawg@w3.org > October to December 2009

RE: HTTP update : default graph

From: Seaborne, Andy <andy.seaborne@hp.com>
Date: Sun, 18 Oct 2009 14:05:01 +0000
To: Gregory Williams <greg@evilfunhouse.com>
CC: "public-rdf-dawg@w3.org Group" <public-rdf-dawg@w3.org>
Message-ID: <B6CF1054FDC8B845BF93A6645D19BEA3693FA225DB@GVW1118EXC.americas.hpqcorp.net>


> -----Original Message-----
> From: Gregory Williams [mailto:greg@evilfunhouse.com]
> Sent: 16 October 2009 19:08
> To: Seaborne, Andy
> Cc: public-rdf-dawg@w3.org Group
> Subject: Re: HTTP update : default graph
> 
> On Oct 14, 2009, at 1:14 PM, Seaborne, Andy wrote:
> 
> > We have talked about how to name a named graph for an update.  What
> > about the default graph?  The case of one graph in the store is
> > important.
> >
> > It could be http://example/store/default or
> http://example/store?graph=default

> > .
> >
> > It can't be http://example/store/ if that follows the style of being
> > the place to GET the service description.
> >
> > DELETE may be inappropriate on the default graph.
> >
> > And also for later: what's the service description for an update
> > service?
> 
> I'd assume it would be mostly the same as a query service, but with an
> appropriate sd:supportedLanguage property pointing to the IRI for
> Update 1.1. Is that what you were asking?

It was more something that occurred to me while thinking about update.  Be good to use the same framework and here will be a lot in common because of pattern matching.  Also, how to get the service description :  if this is "GET /service" (if that is the final outcome for query) then we have added GET to the things the update service needs to answer.

	Andy

> 
> .greg

Received on Sunday, 18 October 2009 14:06:09 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 16:15:40 GMT