- From: Steve Speicher <sspeiche@gmail.com>
- Date: Tue, 14 Oct 2014 08:59:24 -0400
- To: "henry.story@bblfish.net" <henry.story@bblfish.net>
- Cc: public-ldp <public-ldp@w3.org>
- Message-ID: <CAOUJ7JrWhTu-FmoEFxquw4ypEJ8jHLqhsnG+fpRrx8bFm2y_+Q@mail.gmail.com>
On Fri, Oct 10, 2014 at 9:01 AM, henry.story@bblfish.net < henry.story@bblfish.net> wrote: > In the last conf call Arnaud suggested we think about what would be 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. > See http://www.w3.org/2012/ldp/wiki/LDPNext > Henry > > Social Web Architect > http://bblfish.net/ > > >
Received on Tuesday, 14 October 2014 12:59:51 UTC