- From: Kingsley Idehen <kidehen@openlinksw.com>
- Date: Mon, 02 Jul 2012 13:59:19 -0400
- To: Henry Story <henry.story@bblfish.net>
- CC: public-rww@w3.org
- Message-ID: <4FF1E177.90500@openlinksw.com>
On 7/2/12 1:48 PM, Henry Story wrote: > On 2 Jul 2012, at 19:41, Kingsley Idehen wrote: > >> On 7/2/12 11:37 AM, Henry Story wrote: >>> On 2 Jul 2012, at 16:58, Kingsley Idehen wrote: >>> >>>> All, >>>> >>>> I've now added Amazon Simple Storage System (S3) to the running demo [1] re., WebID ACLs applied to mounted folders via SaaS storage services. >>>> >>>> URL of the mounted resource collection (folder): <https://kingsley.idehen.net/DAV/home/kidehen/Public/AmazonS3/> . >>>> >>>> Let me know if it works for you, ditto if you would like your WebID added to my ACL. >>> Works. But I think more fun is if your Access control policy allowed friends of your friends, >>> and perhaps members and friends of the WebID and rww community groups (as specified by foaf files >>> to be written). >> Yes, but if I started there you would have requested something simpler. I am trying to take the simplest approach into a much more sophisticated realm. > I think too simple, makes it difficult to understand. "simple" is clearly subjective. > You need to give us some leverage to play with things, so that we can see how adding people to profiles or removing them changes things. Do you mean: go beyond the current demo which is focused (right now) on you presenting your WebID en route to resource access? > With foaf networks we could add friends to networks, see if they get access, remove them, etc... Then one can see the value of the foaf. > >>> That is when this starts becoming a lot more easy to understand. >> Hmm. >> >> As I said, that's easy. My goal was to start real simple: >> >> 1. mount a SaaS device >> 2. ACL protect access using a foaf:Group >> 3. share with the world >> 4. up the ante as folks engage. > Time to up the ante then... :-) Okay, but I do want feedback from a few more members. Right now I just have you, Melvin, and Juergen . My next step will be to expose the ACL resource so that seed members can expand access. After that, I show more complex rules and a UI for said rules. This is where the foaf:knows relationship comes into play as a basic example. The same UI will also allow you to make more sophisticated rules using SPARQL ASK. Kingsley > >> Kingsley >>> Henry >>> >>> >>>> Links: >>>> >>>> 1. http://bit.ly/NNOkNB -- original post which now has S3 added >>>> 2. https://kingsley.idehen.net/DAV/home/kidehen/Public/BoxNet/ -- Box.Net addition. >>>> >>>> -- >>>> >>>> Regards, >>>> >>>> Kingsley Idehen >>>> Founder & CEO >>>> OpenLink Software >>>> Company Web: http://www.openlinksw.com >>>> Personal Weblog: http://www.openlinksw.com/blog/~kidehen >>>> Twitter/Identi.ca handle: @kidehen >>>> Google+ Profile: https://plus.google.com/112399767740508618350/about >>>> LinkedIn Profile: http://www.linkedin.com/in/kidehen >>>> >>>> >>>> >>>> >>>> >>> Social Web Architect >>> http://bblfish.net/ >>> >>> >>> >> >> -- >> >> Regards, >> >> Kingsley Idehen >> Founder & CEO >> OpenLink Software >> Company Web: http://www.openlinksw.com >> Personal Weblog: http://www.openlinksw.com/blog/~kidehen >> Twitter/Identi.ca handle: @kidehen >> Google+ Profile: https://plus.google.com/112399767740508618350/about >> LinkedIn Profile: http://www.linkedin.com/in/kidehen >> >> >> >> >> > Social Web Architect > http://bblfish.net/ > > -- Regards, Kingsley Idehen Founder & CEO OpenLink Software Company Web: http://www.openlinksw.com Personal Weblog: http://www.openlinksw.com/blog/~kidehen Twitter/Identi.ca handle: @kidehen Google+ Profile: https://plus.google.com/112399767740508618350/about LinkedIn Profile: http://www.linkedin.com/in/kidehen
Attachments
- application/pkcs7-signature attachment: S/MIME Cryptographic Signature
Received on Monday, 2 July 2012 17:59:41 UTC