- From: ashok malhotra <ashok.malhotra@oracle.com>
- Date: Fri, 10 Oct 2014 09:14:16 -0400
- To: public-ldp@w3.org
Let me add a couple of items to Henry's list: - Client directed paging - Ability to select the members of a collection to be returned -- equivalent to SQL WHERE clause - Access control Ashok On 10/10/2014 9:01 AM, henry.story@bblfish.net wrote: > In the last conf call Arnaud suggested we think about what wocouple ofbe useful for LDP-next. > > Here are some things I can think of: > > - uploading of multiple files > ( an easy answer would be to POST a tar with a special mime type that would create a resource > say ldpc/tarredir and which would untarred create all the hierarchy such as > ldpc/tarredir/file1 ldpc/tarredir/file2 ldpc/tarredir/subdir/other ) > > - in addition to PATCH allow for a SEARCH method ( perhaps QUERY would be better ) > This was allowed in early HTTP specs > http://www.w3.org/Protocols/HTTP/Methods.html > The advantage is that just with the knowledge of a URI one would be able to query that URI > directly. One could imagine a query on an LDPC allowing the query of the contents of the LDPC > too. > > - intuitive Containers, so that relative URLs work correctly all the way around > http://www.w3.org/2012/ldp/track/issues/50 > > - Web Access Control integration ( WebID? ) > > > Perhaps a wiki page for these would be useful, so that these ideas can be perused easily > without needing to run through the whole list. > > Henry > > Social Web Architect > http://bblfish.net/ > >
Received on Friday, 10 October 2014 13:14:48 UTC