[foaf-protocols] cert:fingerprint ?

Kingsley Idehen kidehen at openlinksw.com
Tue Nov 22 21:06:22 CET 2011

On 11/22/11 2:35 PM, Kingsley Idehen wrote:
>> 1. it is being pushed because of the use case of publishing on 
>> twitter and the lack of space of a tweet. But I don't believe in that 
>> use case
>>     - the use case does not contain a WebID: one has to assume there 
>> is a webid that twitter would give each user - but it is twitter that 
>> controls
> Of course it does [1].
>>       its name space
> It doesn't. It actually controls its data access address space.
>>     - it requires one to use the twitter json interface to go from 
>> imaginary webid to the hash, so the protocol ends up being completely 
>> twitter specific
> No it doesn't. 

I forgot to drop a link for [1].

1. http://id.myopenlink.net/about/id/entity/http/twitter.com/kidehen -- 
a proxy/wrapper Linked Data URI

-- same proxy URI via URI Debugger

-- Vapour Linked Data URI validation utility



Kingsley Idehen	
President&  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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1625 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.foaf-project.org/pipermail/foaf-protocols/attachments/20111122/3c5c77bf/attachment.bin 

More information about the foaf-protocols mailing list