Re: Mozilla Persona, lessons learned

On 02/16/2014 06:22 AM, Melvin Carvalho wrote:
> IMHO, the problem with persona is that they overloaded email to do
> too many things.  It's
> 
> 1. A memorable identifier 2. A primary key for identity 3. A message
> delivery service
> 
> This design decision has advantages for usability, but disadvantages
> for scalability.
> 
> It excludes essentially "The Web" and linked data based systems such
> as web payments which use URLs.  Additionally they dont use URIs to
> name things which is the first axiom of web architecture.  This
> creates a silo monoculture where you have to evangelize your system
> to a large audience (something mozilla is good at), however a more
> universal system like the one described in the web payments spec has
> a focus on interoperability and should be able to stitch different
> identity eco systems together.

Based on this feedback, a section has been added to the Web Identity spec:

https://web-payments.org/specs/source/web-identity/#compatability-with-other-identity-mechanisms

In theory, the Web Identity spec could be used stand-alone to provide
Login, could be combined w/ Persona w/ a few modifications to Persona,
and can theoretically be paired with OpenID Connect. The trick is to do
all of this w/o severely complicating the spec. :)

-- manu

-- 
Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny)
Founder/CEO - Digital Bazaar, Inc.
blog: The Worlds First Web Payments Workshop
http://www.w3.org/2013/10/payments/

Received on Friday, 21 February 2014 12:23:52 UTC