- From: Henry Story <henry.story@bblfish.net>
- Date: Tue, 11 Dec 2012 16:11:40 +0100
- To: public-webid Group <public-webid@w3.org>
- Cc: Read-Write-Web <public-rww@w3.org>
- Message-Id: <956E7C19-6B20-46C0-B5E1-F5E81298A278@bblfish.net>
To make some progress, I think we need a use cases and requirements document. At TPAC the main interest was to be able to work with the newly emerging Linked Data Platform group [1]. I don't think that LDP says anything about 303s so I don't think this is in fact necessarily relevant to the 303 vs hash debate. But it does give us a good reason to have HTTP URIs because we can then use that platform to do things like the following: Create an account ----------------- ( requires LDP + WebAccessControl ) 1. Find an a LD Collection that is publicly available and allows creation of containers 2. create a container that gives default access to the creator ( perhaps using hash id ) 3. creator can POST a WebID Profile to container with public key Restful Mail ------------ 1. Use the WebID profile to find a Collection for sending mail like content 2. POST a mail like entity there after authenticating with WebID ( now that gives us secure mail ) Pingback -------- similar to Restful Mail, but simpler Friend of a friend Access ------------------------- Allow friends of friends access to some resources So we have a page for this here which we started a few years back http://www.w3.org/2005/Incubator/webid/wiki/Use_Cases_and_Requirements I think it is time to work on that one again. Henry [1] http://www.w3.org/2012/ldp/hg/ldp.html Social Web Architect http://bblfish.net/
Attachments
- application/pkcs7-signature attachment: smime.p7s
Received on Tuesday, 11 December 2012 15:12:22 UTC