Re: Question/idea: Self-contained WebID

I don’t know if it’s been covered, but if you sacrifice attribute exchange (or rely solely on attributes baked into the cert itself), you could do TLS-based “WebID” with a URI which is verifiable only using the public key in the cert.

For example, it’d be ugly (though who cares if your WebID URI is ugly if you never have to see/type it?), but you could do it with a URN containing your key algorithm and pubkey hash (e.g., urn:rsakey:<fingerprint>) — as an informal URN scheme it’d only take a couple of weeks to bring into life if somebody was really keen.

Server-side applications could even use that as a default URI for an agent as a matter of course, adding a resolveable URI as a preferred alias if one’s available.

M.

-- 
Mo McRoberts - Chief Technical Architect - Archives & Digital Public Space,
Zone 2.12, BBC Scotland, 40 Pacific Quay, Glasgow G51 1DA.

Inside the BBC? My movements this week: http://neva.li/where-is-mo

Received on Wednesday, 28 May 2014 17:52:40 UTC