Charter submission for Account Chooser Working Group

Allen Tom allentomdude at gmail.com
Mon Aug 29 23:46:26 UTC 2011


Hi Eric,

Thanks for submitting the Account Chooser  WG proposal. As far as I know,
this is the first time a non protocol spec WG has been proposed.

Can you give us a idea as to what the content and format of the design spec
might look like? Will it be a set of wireframes? Mockups? Flowcharts? Will
it cover only the login form? Will it also cover account linking and account
recovery?

Thanks,
Allen


On Mon, Aug 29, 2011 at 10:46 AM, Eric Sachs <esachs at google.com> wrote:

> This is a formal submission to the OpenID Specs Council to approve the
> Account Chooser Working Group.  The draft charter is posted at
> https://sites.google.com/site/oauthgoog/workinggroupcharter and the
> current version has been copied below.  If possible, we would like to get a
> response from the Specifications Council before the September OpenID Summit
> so we can use that event for more discussions on this topic.
>
>
>
> *Name*
>
> OpenID Account Chooser Working Group
>
> *Background Information*
>
> The term "NASCAR UI" is used to refer to one of the most common user
> experiences on Relying Parties to enable users to login with an identity
> provider.  There are a number of known usability problems with that UI,
> especially in terms of supporting a large number of identity providers, and
> for offering users the ability to log in with either an identity provider or
> a traditional email/password.  The identity community has had discussions
> about building a “cloud based” identity selector to deal with some of those
> problems.  The idea has been to mix the user experience advantages of
> Information Cards, the popularity of consumer identity providers, and still
> support large numbers of identity providers as InCommon has done.  The end
> result is a user experience that is being called an Account Chooser.  For
> background, see accountchooser.com.
>
> The account chooser model can in some cases improve usability on a website
> even if it does not support identity providers, or a website that only
> supports identity providers, or a website that only supports a single
> identity provider.  The account chooser model can also allow a relying party
> to customize the set of buttons it shows during the "add account" flow based
> on IP geolocation of the user to help promote a larger number of identity
> providers around the world instead of just a small number of providers as is
> generally shown on a NASCAR UI.  The working group will discuss all of these
> use cases.
>
> *Statement of Purpose*
>
> This workgroup intends to produce user interface guidelines for how a
> relying party can implement an account chooser for both adding accounts, and
> selecting an account that was previously added.
>
> *Scope*
>
> Produce a specification for the account chooser user interface guidelines.
>
> *Out of Scope *
>
> The working group is not expected to define a protocol specification.
>
> *Specifications *
>
> OpenID Account Chooser User Interface 1.0.
>
> *Anticipated audience*
>
> All those interested in improving the usability of relying parties.
>
> *Language of business*
>
> English.
>
> *Method of work*
>
> Mailing list discussion. Posting of intermediate drafts in the OpenID Wiki.
> Virtual conferencing on an ad-hoc basis.
>
> *Basis for completion of the activity*
>
> The OpenID Account Chooser User Interface 1.0 final specification is
> completed.
>
> *Proposers*
>
> Basheer Tome, basheer at basheertome.com, independent
> John Bradley, jbradley at me.com, independent
> Nat Sakimura, sakimura at gmail.com, NRI
> Kevin Long, kevin at janrain.com, Janrain
> Pam Dingle, pdingle at pingidentity.com, Ping
> Eric Sachs, Esachs at google.com, Google
> Chuck Sievert, csievert at google.com, Google
> Wei Tu, weitu at google.com Google
> Andrew Dahley, andyd at google.com, Google
> Chris Messina, messina at google.com, Google
>
> *Initial Editors*
>
> Eric Sachs, Esachs at google.com>, Google
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs/attachments/20110829/5ecb55a9/attachment.html>


More information about the specs mailing list