- From: Andy Seaborne <andy.seaborne@epimorphics.com>
- Date: Thu, 13 Dec 2012 13:30:01 +0000
- To: public-ldp-wg@w3.org
On 13/12/12 12:29, Roger Menday wrote: >>>> >>>>>> - Can collections contain collections i.e. are collections hierarchical? >>>>>>> (we may decide, no) >>>>> this is a very important point. >>>> I agree. Let's see what other members of the WG feel about this issue. >>>> For example, suppose for a minute that the content was RDF. Does a hierarchical >>>> collection structure map gracefully to the RDF model? >>> >>> An important point indeed! >>> >>> Hierarchies of containers are necessary in my opinion, but I can't see a good reason not to allow (MAY) a graph structure that would map cleanly to the RDF model. >>> >>> URIs are hierarchical, and so are file systems, but links work in both systems, making graphs. >>> >>> Does anyone have a good argument against containers within containers (I hope not). >> >> I'll go further - I don't think it is possible to ban them. >> >> A link in a container is a link - it can be a link to anything >> (including outside of this LDP platform, or outside of any LDP >> platform). So it can be a link to a container. >> > > I see a difference between 'container contained by container' and 'container linked to container' (both should be supported in LDP) ... If a client links a container to another container it is just linkage, and not necessarily containment. Containment is something directed/decided by the server, often through creation. That relates to the creation and management of the container, which are important. But from just the link to the container, you can't tell? A container entry is just a link? Andy > > Roger > >> Andy >> >>> >>> Regards, >>> Dave >>> >>> >>>> >>>> Ashok >>>> >>> >> > > ______________________________________________________________________ > > Fujitsu Laboratories of Europe Limited > Hayes Park Central, Hayes End Road, Hayes, Middlesex, UB4 8FE > Registered No. 4153469 > > This e-mail and any attachments are for the sole use of addressee(s) and > may contain information which is privileged and confidential. Unauthorised > use or copying for disclosure is strictly prohibited. The fact that this > e-mail has been scanned by Trendmicro Interscan does not guarantee that > it has not been intercepted or amended nor that it is virus-free. > >
Received on Thursday, 13 December 2012 13:30:34 UTC