- From: Ashok Malhotra <ashok.malhotra@oracle.com>
- Date: Fri, 19 Oct 2012 09:32:03 -0700
- To: public-ldp-wg@w3.org
Received on Friday, 19 October 2012 16:32:33 UTC
If I have another usecase. I have an, already created, resource R which has a URI and I want to put it in a container C. Is that possible or would the conflation of the container URI and resource URI prevent that? Or would the URI of the resource in the container just point to R which could have a different URI? All the best, Ashok On 10/19/2012 9:22 AM, Arnaud Le Hors wrote: > "Steve Battle" <steve.battle@sysemia.co.uk> wrote on 10/19/2012 08:44:36 AM: > > > It's my understanding that The Opacity Axiom > > <http://www.w3.org/DesignIssues/Axioms.html#opaque> applies only to clients > > attempting to pick apart a URI, rather than to the server. > > > > Indeed, but I'm not sure clients could live without knowing the magic involved in this scenario and even more so in the case of creating a resource using PUT. > -- > Arnaud Le Hors - Software Standards Architect - IBM Software Group
Received on Friday, 19 October 2012 16:32:33 UTC