W3C home > Mailing lists > Public > public-lod@w3.org > June 2010

Re: [foaf-protocols] Yet Another FOAF+SSL ACL Test: ACLs Baton Passing

From: Nathan <nathan@webr3.org>
Date: Sat, 19 Jun 2010 16:37:52 +0100
Message-ID: <4C1CE450.5010105@webr3.org>
To: mike amundsen <mca@amundsen.com>
CC: Kingsley Idehen <kidehen@openlinksw.com>, foaf-protocols <foaf-protocols@lists.foaf-project.org>, Linked Data community <public-lod@w3.org>
try: 
https://ods-qa.openlinksw.com/home/dav/Public/fao_to_sumo_mappings.txt,acl

note the ,acl

Nathan :)

mike amundsen wrote:
> Kingsley:
> 
> thanks for continuing to post examples/tests like this for us to work through.
> 
> When I attempt to deref the URI:
> https://ods-qa.openlinksw.com/home/dav/Public/fao_to_sumo_mappings.txt
> 
> I am asked for my cert (supplied) and I am presetned with the HTTP
> Auth challenge.
> 
> IOW, I'm not able to load the file and cannot continue.
> 
> mca
> http://amundsen.com/blog/
> http://mamund.com/foaf.rdf#me
> 
> 
> 
> 
> On Sat, Jun 19, 2010 at 09:58, Kingsley Idehen <kidehen@openlinksw.com> wrote:
>> All,
>>
>>
>> FOAF+SSL protected resource URL:
>> <https://ods-qa.openlinksw.com/home/dav/Public/fao_to_sumo_mappings.txt> .
>>
>> Step 1.
>>
>> If you are new to these test (I suspect most on the LOD list), you will
>> need to have a WebID in the ACL associated with the URL above. Thus,
>> failure to successfully de-reference the URL is success (i.e. you see a
>> WebDAV challenge due to your FOAF+SSL authentication challenge failure).
>>
>>
>> Step 2.
>>
>> I've given the added the following  FOAF+SSL crew members "write"
>> privileges on the ACL resource for
>> <https://ods-qa.openlinksw.com/home/dav/Public/fao_to_sumo_mappings.txt>
>> (the resource URL is discoverable via Link: response headers):
>>
>> 1. Nathan - <http://webr3.org/nathan#me>
>> 2. Henry - <http://bblfish.net/people/henry/card#me>
>> 3. Melvin - <http://foaf.me/melvincarvalho#me>
>> 4. Mike - <http://mamund.com/foaf.rdf#me>
>> 5. Michael Hausenblas - <http://sw-app.org/mic.xhtml#i> .
>>
>> Step 3.
>>
>> Each of the individuals above are in a position to extend the ACL
>> membership, courtesy of privileges assigned to their WebIDs, via a
>> WebDAV aware client (which includes all major operating systems these
>> days). Thus, via WebDAV you can simply edit the N3 representation of the
>> ACL resource.
>>
>> Once we get this process nailed, we will then up the ante with ping
>> based notices such that ACL membership changes are propagated via ping
>> based notifications to affected individuals (by sniffing their "ping
>> service endpoints" which should become part of the structured FOAF based
>> profiles associated with their WebIDs).
>>
>>
>> --
>>
>> Regards,
>>
>> Kingsley Idehen
>> President & CEO
>> OpenLink Software
>> Web: http://www.openlinksw.com
>> Weblog: http://www.openlinksw.com/blog/~kidehen
>> Twitter/Identi.ca: kidehen
>>
>>
>>
>>
>>
>> _______________________________________________
>> foaf-protocols mailing list
>> foaf-protocols@lists.foaf-project.org
>> http://lists.foaf-project.org/mailman/listinfo/foaf-protocols
>>
> 
> 
> 
Received on Saturday, 19 June 2010 15:39:12 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 31 March 2013 14:24:27 UTC