W3C home > Mailing lists > Public > public-rww@w3.org > April 2012

POSTing to a collection and GETing its index

From: Henry Story <henry.story@bblfish.net>
Date: Mon, 9 Apr 2012 00:20:19 +0200
Message-Id: <B4765815-3B78-4D37-A16A-CDE64A053222@bblfish.net>
Cc: Alexandre Bertalis <bertails@w3.org>
To: Read-Write-Web <public-rww@w3.org>
Hi,

  As I understand POSTing a resource to a Collection should create a new resource.
We want to allow collections to be POST only so that unknown people can post into 
a collection without seeing the other resource in it. (whilst perhaps allowing the 
POSTer to edit the resources he created in that collection). We would like the owner 
of the collection to be able to know what is in the collection: so that he can for 
example find the new resources POSTed there.

  So some user should be able to 

POST /collection/ HTTP/1.1

thereby having the read-write-web server create the resource 

  /collection/r42

which he could later edit in case he made a mistake. But he would not be 
albe to find the elements of the collection by doing a 

GET /collection/

as that would be protected. He certainly could not edit what ends up being the
equivalent of /collection/index{.rdf} since he does not have access to that
file. It must therefore be up to the ReadWriteWeb server to do three things:

 1. create a name for the POSTed resource
 2. update/display the collection (sioc:Collection?) index retrieved when
    doing a GET /collection/
 3. Only show a subset of those elements of the collection that an agent
    has read access to

I think the scala read-write-web does not have POST on a collection (a directory
in unix terminology) create a new file currently. (It has a POST of a SPARQL update
on an rdf information resource change it.)

Does that sound right?

	Henry


Social Web Architect
http://bblfish.net/
Received on Sunday, 8 April 2012 22:20:50 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:10:25 UTC