Shared publicly  - 
Explaining those WebID Tweets with SHA1 and MD5 hashes

Here is a collection of screenshots that covers the entire process of using our native (soon to be released) iOS5 based X.509 certificate generator. Basically, this is what leads to Tweets that take the form:

#X509Cert Fingerprint:2DE51E04E5E3FF8B12AC236A05F49ECC21DB9980 #SHA1 ; Subject Alt. Name: . #WebID

Important notes about the excerpt above:

1. each tweet includes an actual functional WebID;

2. each WebID resolves to a resource where format is negotiable by a WebID client;

3. Twitter acts as a key IdP component in the resulting Linked Data graph -- the minimal WebID spec requirement for Public Key components to be stored in an IdP space re. "mirrored claims" remains intact, since Linked Data is all about Webby graphs;

4. proxy URIs produced by Virtuoso or ODS include sophisticated cache invalidation schemes while also making Linked Data deployment utterly painless.

Click on the link in the Tweet excerpt above to experience what I explain above.

What does the Tweet above teach anyone about WebID?
It demonstrates the fact that WebID exploitation is more about structured data, URIs, PKI, Trust logic, and the architecture of the World Wide Web. Basically, nothing to do with a particular structured data representation format or syntax. It works for across all Web dimensions be it 1.0, 2.0, or 3.0.

1. -- creating an exploiting WebID from an iPad
2. -- iPhone and WebID .

#LinkedData #WebID #Identity #Nymwars #SemanticWeb #iPad #iPhone #iOS5 #PKI
Add a comment...