[foaf-protocols] Using @rel to broaden scope of what we currently call FOAF+SSL

Kingsley Idehen kidehen at openlinksw.com
Thu May 13 18:47:25 CEST 2010


Nathan wrote:
> Kingsley Idehen wrote:
>> Nathan wrote:
>>> Story Henry wrote:
>>>> Social Web Architect
>>>> http://bblfish.net/
>>>>
>>>> On 13 May 2010, at 16:55, Nathan wrote:
>>>>
>>>>> Story Henry wrote:
>>>>>> On 13 May 2010, at 16:42, Kingsley Idehen wrote:
>>>>>>> All,
>>>>>>>
>>>>>>> What's not to like about the following in <head/> of HTML docs 
>>>>>>> re. broadening scope of SSL based verifiable network identity ?
>>>>>>>
>>>>>>> <link rel="identity" 
>>>>>>> href="{verifiable-network-identity-card-url}" ../>
>>>>>>> <link rel="rsa:exponent" content="..." />
>>>>>>> <link rel="rsa:modulus"  content="..." />
>>>>>> You can only have one key per user, for one.
>>>>> surely you can have one key per cert, but multiple certs per user 
>>>>> (you Henry are one of the few people I've seen who have two - had 
>>>>> to update a few libs to handle more than one cert ;) and clear out 
>>>>> those non hex chars lol)
>>>>
>>>> The problem is that the above link relation would not allow you to 
>>>> have more than one
>>>> public key published.
>>>>
>>>
>>> gotcha, ty for clarifying (as per usual!)
>>
>> Is the composite key above such a problem?
>>
>> My credit card has a security code that I can't even change. At least 
>> here I can regenerate my key, and depending on my platform, get the 
>> HTML page in question re-generated etc..
>>
>> In a world of options, you move from basic to advanced. Typically, by 
>> opportunity costs palpable :-)
>
> I agree w/ you both and see both sides of it
>
> 1: great to have options and many will only need / use 1 key
>
> 2: many will also then need a second key and get frustrated at not 
> having support / will need to swap over.
>
> Important thing is getting more and more webids with foaf+ssl out 
> there, every +1 webid brings read write web one step closer.
>
> Other important thing is making sure you don't -1 by not doing things 
> properly and ensuring the options (and limitations of each / or 
> otherwise) are clear to all.
>
> i sit on both sides of the fence that isn't there - so I'm sitting on 
> the floor I guess.
>
> ps: who doesn't like <head/>!?

Activation Threshold Lowering is vital to any mass adoption of 
technology or best practices.

Make everyone embrace and extend your vision.

TimBL pulled off the above via HTTP and HTML re. the WWW; there is 
contemporary evidence that this pattern works :-)


Kingsley
>
> Best,
>
> Nathan
>
>
>


-- 

Regards,

Kingsley Idehen	      
President & CEO 
OpenLink Software     
Web: http://www.openlinksw.com
Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca: kidehen 







More information about the foaf-protocols mailing list