Re: Use cases updated w/ glossary and roles

On 08/01/2014 12:39 PM, Dave Longley wrote:
> So, solving this problem doesn't mean that a person wouldn't still be
> provided a UI with a set of identity providers to choose from. It 
> means that the *person* gets to choose that set and that the person 
> may put *any* identity provider that implements a standard protocol 
> into that list.

Also, it's important to note that the people that have asserted that the
use case requires a NASCAR solution to a problem are probably not
familiar with the technology that's being proposed to address each
NASCAR problem:

One of the outcomes of the almost-formed Credentials Community Group is
to address this NASCAR problem for login and payment provider
selection using a technology derived from the one discussed in
detail in the blog post above.

This isn't about preventing choice, it's about making choices easier on
everyone by only displaying the choices that are valid for you as an
individual. Why pop up buttons for all of the major payment providers if
you only use one of them? Why pop up buttons for all of the major login
providers if you only use two of them? The answer to both of these
questions is: You shouldn't.

When it comes to the NASCAR problem, the Identity Credentials spec is
primarily about only providing choices to the customer that make sense
for their particular situation.

-- manu

Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny)
Founder/CEO - Digital Bazaar, Inc.
blog: The Marathonic Dawn of Web Payments

Received on Saturday, 2 August 2014 20:03:59 UTC