This space is effectively controlled by only three US platform/OS vendors. The interest among these parties creating a united web identity solution is NIL. The W3C should focus on things having a*/level playing field/* like XML structures. The standardization of <keygen> didn't work too well if it worked at all. Liberty Alliance Project tried for years creating browser-support and as far as I can see they got nowhere. If we are talking about web identity solutions that do not require browser upgrades there are already tons of other places where this is dealt with. The complete disconnect between browsers and tokens is beyond repair. Not even the requirements are possible to list without people getting hurt by IPR issues. Anders Bad guy On 2011-10-25 08:35, Henry Story wrote: > Dear Web Identity Groups, > > Since both the community forming around the Web Identity javascript cryptography work [1] and the WebID XG are working in the same space, I propose that the two groups work out how these projects can complement each other, so that the W3C can tell a unified identity story. There is a lot in common between them - usage of cryptography in the browser and certificates to prove identity online - and it seems quite clear to me that both the existing WebID solution [2] and the in development version known as BrowserId can complement each other, in fact should as much as possible do so. This could then form the basis for a future WG starting 2012, split hopefully into a number of small independent and closely interrelated parts. > > Henry > > > [1] http://www.w3.org/2011/08/webidentity-charter.html > [2] http://webid.info/spec/ > > Social Web Architect > http://bblfish.net/ > > >
Received on Tuesday, 25 October 2011 08:35:17 UTC