- From: Sandro Hawke <sandro@w3.org>
- Date: Mon, 12 Dec 2011 11:27:18 -0500
- To: Axel Polleres <axel.polleres@deri.org>
- Cc: Chime Ogbuji <chimezie@gmail.com>, Andy Seaborne <andy.seaborne@epimorphics.com>, SPARQL Working Group <public-rdf-dawg@w3.org>
On Mon, 2011-12-12 at 16:10 +0100, Axel Polleres wrote: > Dear Chime, Dear Andy, > > Apart from additional regrets from myself, can you please make sure to update us about the status of your documents? > > Are we in a position to vote on publications already? > If not what is missing and is there anything the group can contribute to get the docs to vote by next week? Unfortunately, we're not quite ready for Last Call on Graphstore Protocol. I started to surface some issues in my review, and they came up again much more strongly at last week's Enterprise Linked Data Workshop. At one level the problem is that the document could stand on its own, without any reference to SPARQL, but the users who want that will have a hard time finding and understand it because of all the SPARQL trappings. At another level, this design may conflict with some users doing just that. For example: Basic Profile Resources are created by HTTP POST (or PUT) to an existing resource, deleted by HTTP DELETE, updated by HTTP PUT or PATCH, and "fetched" using HTTP GET. -- http://www.ibm.com/developerworks/rational/library/basic-profile-linked-data/index.html I think that conflicts with our POST-to-Graph=APPEND rule. I think we need to sort this out before Last Call. It's pretty much my top priority -- I hope to have a proposal in the next day or two. -- Sandro > thanks a lot, > Axel > > On 12 Dec 2011, at 16:07, Chime Ogbuji wrote: > > > I will have to give my regrets for this teleconference > > > > -- > > Chime Ogbuji > > Sent with Sparrow > > On Monday, December 12, 2011 at 10:03 AM, Andy Seaborne wrote: > > > I'm "at risk" for this week's telecon. > > > > > > Andy > > > > > > > > > > > >
Received on Monday, 12 December 2011 16:27:32 UTC