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

Re: POSTing to a collection and GETing its index

From: Henry Story <henry.story@bblfish.net>
Date: Wed, 11 Apr 2012 23:57:19 +0200
Cc: public-rww@w3.org
Message-Id: <91BA428C-C59D-498B-9D03-66547597AD00@bblfish.net>
To: Olivier Berger <olivier.berger@it-sudparis.eu>

On 10 Apr 2012, at 13:11, Olivier Berger wrote:

> Hi.
> 
> On Mon, 9 Apr 2012 00:20:19 +0200, Henry Story <henry.story@bblfish.net> wrote:
>> 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.
>> 
> 
> SNIP
> 
> Have you had a look at "Linked Data Basic Profile 1.0" that was recently
> submitted [0] ?

Thanks for pointing me to this. This work looks like it is a very good starting
point for what we are doing. 
> 
> It seems to me that the "Basic Profile Container" are supposed to be
> handlinkg such cases...

Some remarks as I read through it:
 - I am surprised they don't allow xsd:hexBinary datatype. We find that useful in WebId.
 - they don't specify how PATCH should work. Sounds like using it with SPARQL update would be
  interesting...
 + They have an ontology for containers:

#    http://example.org/container1
	@prefix dcterms: <http://purl.org/dc/terms/>.
	@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#>.
	@prefix bp: <http://open-services.net/ns/basicProfile#>.

	<http://example.org/container1> a bp:Container;
   		dcterms:title "A very simple container";
   		refs:member <http://example.org/container1/member1>,
      			<http://example.org/container1/member2>,
      			<http://example.org/container1/member3>.

  POSTing to the container creates a new resource.
  That seems good. So we now have three methods to do this: the data.fm ontology, 
  using sioc:Container and this one.

 ? The o:asset membership property idea is interesting. I'll need to think
   about it more carefully.
 + the paging idea is interesting too...

I wonder where this is being discussed...

Thanks again for the pointer.

	Henry



> 
> Hope this helps.
> 
> Best regards,
> 
> [0]  http://www.w3.org/Submission/2012/02/
> -- 
> Olivier BERGER 
> http://www-public.it-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8
> Ingenieur Recherche - Dept INF
> Institut TELECOM, SudParis (http://www.it-sudparis.eu/), Evry (France)
> 

Social Web Architect
http://bblfish.net/
Received on Wednesday, 11 April 2012 21:57:55 UTC

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