- From: Henry Story <henry.story@bblfish.net>
- Date: Fri, 19 Oct 2012 18:38:46 +0200
- To: ashok.malhotra@oracle.com
- Cc: public-ldp-wg@w3.org
- Message-Id: <21E8A6B7-BB4A-49E6-A361-E28934842754@bblfish.net>
On 19 Oct 2012, at 18:32, Ashok Malhotra <ashok.malhotra@oracle.com> wrote: > 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 it should be. you put <http://mydomain.com/foaf#me> a foaf:Person . to <http://data.fm/friends> then you would have <http://mydomain.com/foaf#me> a foaf:Person . in <http://data.fm/friends> if you PUT <#me> a foaf:Person to <http://data.fm/friends> Then you'll have that resources contain <http://data.fm/friends#me> a foaf:Person . > or would the conflation of > the container URI and resource URI prevent that? The new resource you PUT to, would now contain a metnion of the resource R. > Or would the URI of the resource in > the container just point to R which could have a different URI? The above should be the case. If it is not then one should open an issue. Henry > 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 Social Web Architect http://bblfish.net/
Attachments
- application/pkcs7-signature attachment: smime.p7s
Received on Friday, 19 October 2012 16:39:33 UTC