Theme of my presentation and discussion at today's gathering.
Problem: Unambiguous Verifiable Network Identity.
Q: How Does Linked Data Address This Problem?
A: It provides critical infrastructure for the WebID Protocol via a tweak of SSL/TLS.
Q: What about OpenID?
A: The WebID Protocol embraces and extends OpenID via the WebID + OpenID variant of the protocol (basic effect is that OpenID calls are re-routed to WebID aspect which simply removes Username and Password Authentication from the authentication challenge interaction).
1. X.509 Certificate and Private Key Generator
2. Structured Profile Document (e.g. a FOAF based Profile) published to an HTTP Network (e.g. World Wide Web) and accessible at an Address (URL)
3. An Agent Identifier aka. WebID (an HTTP Name Reference re. URI variant) that's the Subject of a Structured Profile Document (actually a Descriptor Resource)
4. Mechanism for persisting Public Key data from X.509 Certificate to Structured Profile Document and associating it with Subject WebID (e.g. SPARUL or other HTTP based methods)
5. Mechanism for de-referencing Public Key data associated with a WebID (from its Structured Profile Document) for comparison against Public Key data following successful standard SSL/TLS protocol handshake (e.g. via SPARQL Query).
-- WebID creation all the way to verification using OpenID across Stackoverflow.com & identi.ca as example data spaces on the Web .