W3C home > Mailing lists > Public > public-ldp-wg@w3.org > January 2013

Re: ISSUE-36: Summary of ways of making containers

From: Roger Menday <Roger.Menday@uk.fujitsu.com>
Date: Thu, 24 Jan 2013 11:09:36 +0000
CC: "public-ldp-wg@w3.org" <public-ldp-wg@w3.org>
Message-ID: <75AB04E7-C83E-4F83-BAD7-E23778E6A8ED@uk.fujitsu.com>
To: Henry Story <henry.story@bblfish.net>

hi Henry, 

>> 
>> Henry, 
>> 
>> Let's say that LDP is the web for robots (i.e. HTML is replaced by RDF, hypermedia -> hyperdata). What is the application out there on the human web which requires container creation, which we also need to offer to our robotic clients ? 
> 
> Whenever you want to partition spaces to give access rights to different groups of users for example

In the wiki case, along with create folder (or whatever), access right management seems to be something also directed by the application flow. 

> Or if you want different interaction with the resources contained therein. 
> 

What is a scenario on the human web which shows this 'different interaction' as a clear example ? 

Roger

>> 
>> Roger
>> 
>> p.s. I don't think a wiki is an answer, because create container is part of the application. 
>> 
>> 
>> On 23 Jan 2013, at 09:41, Henry Story wrote:
>> 
>>> In summary here are the proposed ways of allowing applications to make
>>> containers:
>>> 
>>> 1. Using the MKCOL HTTP Method from WebDAV
>>> ------------------------------------------
>>> 
>>> - Works like GET/PUT/POST/DELETE . 
>>> - Implemented in 100s of millions of clients on MS-Windows, OSX, Linux, and other Unixes for WebDAV
>>> - RFC: http://tools.ietf.org/html/rfc4918#section-9.3
>>> 
>>> 2. POST + server looks at content of graph
>>> ------------------------------------------
>>> 
>>> if graph posted to ldp:Container </satellite/x4354/> contains the triple
>>> 
>>>    <> a ldp:Container .
>>> 
>>> the server makes a container.
>>> 
>>> 3. Link from LDPC to factory
>>> ----------------------------
>>> 
>>> The container </satellite/y500/> contains a link to a factory <makeAnotherContainer> .
>>> 
>>> <> a ldp:Container;
>>>    ldp:containerFactory <makeAnotherContainer> .
>>> 
>>> <makeAnotherContainer> would then be something else besides an LDPR or an LDPC. 
>>> It  would need to describe itself as a factory and tell you for which collection it was a 
>>> factory for. One can then POST something into the <makeAnotherContainer> factory in 
>>> order to create a collection inside the original </satellite/y500/> .
>>> 
>>> 4. Link from LDPC to home document that links to factory
>>> --------------------------------------------------------
>>> 
>>> The container contains a link to the home document
>>> 
>>> <> a ldp:Container;
>>>    ldp:homeDocument <http://nasa.gov/satellite/y500/homeSweetHome/> .
>>> 
>>> The home document contains a link to the containerFactory
>>> 
>>> <http://nasa.gov/satellite/y500/homeSweetHome/> a ldp:HomeDocument;
>>>    ldp:containerFactory <makeContainersFor> .
>>> 
>>> Sending a POST to the containerFactory can create a container, but requires 
>>> telling the container factory which container one wishes to create the container 
>>> in. The containerFactory needs to describe also which containers it can create 
>>> a factory for.
>>> 
>>> Henry  
>>> 
>>> Social Web Architect
>>> http://bblfish.net/
>>> 
>> 
> 
> Social Web Architect
> http://bblfish.net/
> 



Received on Thursday, 24 January 2013 11:10:46 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:11:44 UTC