Versions Compared

Old Version 8

changes.mady.by.user Former user

Saved on

compared with

New Version 9

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Note
titleWorking Draft

This page is a Working Draft subject to further revision and has not yet been approved by the Leadership Council.

Rev 0.71

(1) WG NAME (and any acronym or abbreviation of the name): The WG name, acronym and abbreviation must not include trademarks not owned by the Organization, or content that is infringing, harmful, or inappropriate.

Universal Login User Experience (ULX) Work Group

(2) PURPOSE: Please provide a clear statement of purpose and justification why the proposed WG is necessary.

The purpose of the Work Group is to uncover, through a structured process (design and testing of prototypes, authoring draft specifications, building reference implementations), an integrated user interface that best guides a person through the login lifecycle of a website. This includes first time registration and logging in during return visits as well as logging out. Assumed is a range of initial conditions, protocols, and relationships between the application and identity services. The Work Group will facilitate the development of visually consistent, interoperable implementations of these specifications.

The Work Group is necessary to expedite the process of gathering representatives from disparate communities each of which tends to focus on the user experience for a single protocol or approach. Key to success will be attracting participation from the communities developing formal standards (e.g. SAML, OpenID, and IMI Information Card), communities supporting de facto standards (e.g. Facebook Connect and Google Friend Connect), and communities involved in HTML username/password technology (e.g. browser developers). The output of the Work Group is a set of guidelines and draft specifications that embrace many different login technologies, along with reference applications that can be empirically demonstrated to be easy for people to learn and use. Specifically, this Work Group is responsible for:

  • Designing a methodology and set of metrics for empirically testing the effectiveness, efficiency, and overall usability of various approaches to implementing the website login lifecycle.
  • Developing a set of use cases and requirements that are specific enough to guide the specification design work
  • Developing prototype implementations of the user interface
  • Applying the testing methodology to these prototypes
  • Developing a set of modular draft specifications based on the outcome of the design/prototype/testing process that meet the identified use cases and requirements, influenced by contributions as appropriate
  • Developing and maintaining liaisons as appropriate with external bodies and other Kantara groups
  • Fostering the creation of multiple interoperable reference implementations, particularly in open source
  • Promoting progressive harmonization with existing specifications and protocols as appropriate
  • Developing educational materials in support of the overall Work Group effort
  • Overseeing the contribution of each resulting draft specification to a standards-setting organization

(3) SCOPE: Explain the scope and definition of the planned work.

The specifications must meet the following basic functional requirements, in addition to specific use cases and requirements later identified by this Work Group:

  • Support the notion of an integrated user interface such that one or more prototcol-specific implementations can fit within the overall visual interaction framework.
  • Allows the person to use a variable number of computers and/or mobile devices
  • Allows that the specific device being used may or may not have some kind of identity client software integrated into the browser or callable via an API from a local application
  • Supports a wide range of sizes of display surface for the interface.
  • Accommodates the fact that the Website (or local web-based application) supports one or more of the following interaction methods: username/password, OpenID, Facebook Connect, IMI Information Card, SAML, Google Friend Connect, Kerberos.
  • Accommodates the fact that the web-based identity client software, if present, supports one or more of the following login methods (that the person is capable of using): OpenID, Facebook Connect, IMI, SAML, Google Friend Connect, Kerberos.
  • Accommodates the fact that the person may be visually impaired or have other disabilities

The specifications must meet the following basic design principles, in addition to any emergent design principles later identified by this Work Group:

  • Simple to understand, implement in an interoperable fashion, and deploy on an Internet-wide scale
  • Modular (e.g. incorporating other existing specifications by reference where appropriate, and breaking down this Work Group's draft specifications into multiple pieces where reuse by different communities is likely)
  • Generative (able to be combined and extended to support a variety of use cases and emerging application functionality)
  • Developed rapidly, in an "agile specification" process that can refactor for emerging needs

The following design solutions are initially out of scope for the first version of the group's output, though the group should avoid precluding such solutions, if possible, where they are analogous to in-scope solutions:

  • Other types of networked applications besides Web-based ones
  • Parties other than natural persons wishing to login

(4) DRAFT TECHNICAL SPECIFICATIONS: List Working Titles of draft Technical Specifications to be produced (if any), projected completion dates, and the Standards Setting Organization(s) to which they will be submitted upon approval by the Membership.

It is anticipated that the following technical specifications will be produced, with modular boundaries subject to change; they are anticipated to be submitted to the World Wide Web Consortium (W3C) for further work and completion:

  • Universal Login UX Specification
  • Login Metadata Discovery – A mechanism whereby an identity enabled client can discover the supported/preferred login method(s).

(5) OTHER DRAFT RECOMMENDATIONS: Other Draft Recommendations and projected completion dates for submission for All Member Ballot.

Universal Login UX Best Practices and Walkthrough Documentation

At the group's option, some of this material may be considered non-normative (equivalent to white papers).

(6) LEADERSHIP: Proposed WG Chair and Editor(s) (if any) subject to confirmation by a vote of the WG Participants.

...

Wiki Markup
{note:title=Working Draft}This page is a *Working Draft* subject to further revision and has not yet been approved by the Leadership Council.
{note}
Rev 0.90

*(1) WG NAME* _(and any acronym or abbreviation of the name): The WG name, acronym and abbreviation must not include trademarks not owned by the Organization, or content that is infringing, harmful, or inappropriate._

*{+}Universal Login User Experience (ULX) Work Group{+}*

*(2) PURPOSE:* _Please provide a clear statement of purpose and justification why the proposed WG is necessary._

<!--  /* Font Definitions */ @font-face 	{font-family:Times; 	panose-1:2 0 5 0 0 0 0 0 0 0; 	mso-font-charset:0; 	mso-generic-font-family:auto; 	mso-font-pitch:variable; 	mso-font-signature:3 0 0 0 1 0;} @font-face 	{font-family:Cambria; 	panose-1:2 4 5 3 5 4 6 3 2 4; 	mso-font-charset:0; 	mso-generic-font-family:auto; 	mso-font-pitch:variable; 	mso-font-signature:3 0 0 0 1 0;}  /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal 	{mso-style-parent:""; 	margin:0in; 	margin-bottom:.0001pt; 	mso-pagination:widow-orphan; 	font-size:12.0pt; 	font-family:"Times New Roman"; 	mso-ascii-font-family:Cambria; 	mso-ascii-theme-font:minor-latin; 	mso-fareast-font-family:Cambria; 	mso-fareast-theme-font:minor-latin; 	mso-hansi-font-family:Cambria; 	mso-hansi-theme-font:minor-latin; 	mso-bidi-font-family:"Times New Roman"; 	mso-bidi-theme-font:minor-bidi;} @page Section1 	{size:8.5in 11.0in; 	margin:1.0in 1.25in 1.0in 1.25in; 	mso-header-margin:.5in; 	mso-footer-margin:.5in; 	mso-paper-source:0;} div.Section1 	{page:Section1;} -->The purpose of the Work Group is to uncover, through a structured process (design and testing of prototypes, authoring draft specifications, building reference implementations), an integrated user interface that best guides a person through the login lifecycle of a website. This does not include first time registration, but does include logging in during return visits as well as logging out. Assumed is a range of initial conditions, protocols, and relationships between the application and identity services. The Work Group will facilitate the development of visually consistent, interoperable implementations of these specifications

<!--  /* Font Definitions */ @font-face 	{font-family:Times; 	panose-1:2 0 5 0 0 0 0 0 0 0; 	mso-font-charset:0; 	mso-generic-font-family:auto; 	mso-font-pitch:variable; 	mso-font-signature:3 0 0 0 1 0;} @font-face 	{font-family:Cambria; 	panose-1:2 4 5 3 5 4 6 3 2 4; 	mso-font-charset:0; 	mso-generic-font-family:auto; 	mso-font-pitch:variable; 	mso-font-signature:3 0 0 0 1 0;}  /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal 	{mso-style-parent:""; 	margin:0in; 	margin-bottom:.0001pt; 	mso-pagination:widow-orphan; 	font-size:12.0pt; 	font-family:"Times New Roman"; 	mso-ascii-font-family:Cambria; 	mso-ascii-theme-font:minor-latin; 	mso-fareast-font-family:Cambria; 	mso-fareast-theme-font:minor-latin; 	mso-hansi-font-family:Cambria; 	mso-hansi-theme-font:minor-latin; 	mso-bidi-font-family:"Times New Roman"; 	mso-bidi-theme-font:minor-bidi;} @page Section1 	{size:8.5in 11.0in; 	margin:1.0in 1.25in 1.0in 1.25in; 	mso-header-margin:.5in; 	mso-footer-margin:.5in; 	mso-paper-source:0;} div.Section1 	{page:Section1;} -->The Work Group is necessary to expedite the process of gathering representatives from disparate communities each of which tends to focus on the user experience for a single protocol or approach. Key to success will be attracting participation from the communities developing formal standards (e.g. SAML, OpenID, and IMI Information Card), communities supporting de facto standards (e.g. Facebook Connect and Google Friend Connect), and communities involved in HTML username/password technology (e.g. browser developers). The output of the Work Group is a set of guidelines and draft specifications that embrace many different login technologies, along with reference applications that can be empirically demonstrated to be easy for people to learn and use. Specifically, this Work Group is responsible for:



<!--  /* Font Definitions */ @font-face 	{font-family:"Courier New"; 	panose-1:2 7 3 9 2 2 5 2 4 4; 	mso-font-charset:0; 	mso-generic-font-family:auto; 	mso-font-pitch:variable; 	mso-font-signature:3 0 0 0 1 0;} @font-face 	{font-family:Times; 	panose-1:2 0 5 0 0 0 0 0 0 0; 	mso-font-charset:0; 	mso-generic-font-family:auto; 	mso-font-pitch:variable; 	mso-font-signature:3 0 0 0 1 0;} @font-face 	{font-family:Wingdings; 	panose-1:5 2 1 2 1 8 4 8 7 8; 	mso-font-charset:2; 	mso-generic-font-family:auto; 	mso-font-pitch:variable; 	mso-font-signature:0 0 65536 0 -2147483648 0;} @font-face 	{font-family:Cambria; 	panose-1:2 4 5 3 5 4 6 3 2 4; 	mso-font-charset:0; 	mso-generic-font-family:auto; 	mso-font-pitch:variable; 	mso-font-signature:3 0 0 0 1 0;}  /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal 	{mso-style-parent:""; 	margin:0in; 	margin-bottom:.0001pt; 	mso-pagination:widow-orphan; 	font-size:12.0pt; 	font-family:"Times New Roman"; 	mso-ascii-font-family:Cambria; 	mso-ascii-theme-font:minor-latin; 	mso-fareast-font-family:Cambria; 	mso-fareast-theme-font:minor-latin; 	mso-hansi-font-family:Cambria; 	mso-hansi-theme-font:minor-latin; 	mso-bidi-font-family:"Times New Roman"; 	mso-bidi-theme-font:minor-bidi;} @page Section1 	{size:8.5in 11.0in; 	margin:1.0in 1.25in 1.0in 1.25in; 	mso-header-margin:.5in; 	mso-footer-margin:.5in; 	mso-paper-source:0;} div.Section1 	{page:Section1;}  /* List Definitions */ @list l0 	{mso-list-id:1161697944; 	mso-list-template-ids:89825602;} @list l0:level1 	{mso-level-number-format:bullet; 	mso-level-text:?; 	mso-level-tab-stop:.5in; 	mso-level-number-position:left; 	text-indent:-.25in; 	mso-ansi-font-size:10.0pt; 	font-family:Symbol;} ol 	{margin-bottom:0in;} ul 	{margin-bottom:0in;} -->
* Designing a methodology and set      of metrics for empirically testing the effectiveness, efficiency, and      overall usability of various approaches to implementing the website login      lifecycle.
* Developing a set of use cases      and requirements that are specific enough to guide the specification      design work
* Developing prototype      implementations of the user interface
* Applying the testing      methodology to these prototypes
* Developing a set of modular      draft specifications based on the outcome of the design/prototype/testing      process that meet the identified use cases and requirements, influenced by      contributions as appropriate
* Developing and maintaining      liaisons as appropriate with external bodies and other Kantara groups
* Fostering the creation of      multiple interoperable reference implementations, particularly in open      source
* Promoting progressive      harmonization with existing specifications and protocols as appropriate
* Developing educational      materials in support of the overall Work Group effort
* Overseeing the contribution of      each resulting draft specification to a standards-setting organization



*(3) SCOPE:* _Explain the scope and definition of the planned work._

The specifications must meet the following basic functional requirements, in addition to specific use cases and requirements later identified by this Work Group:



<!--  /* Font Definitions */ @font-face 	{font-family:"Courier New"; 	panose-1:2 7 3 9 2 2 5 2 4 4; 	mso-font-charset:0; 	mso-generic-font-family:auto; 	mso-font-pitch:variable; 	mso-font-signature:3 0 0 0 1 0;} @font-face 	{font-family:Times; 	panose-1:2 0 5 0 0 0 0 0 0 0; 	mso-font-charset:0; 	mso-generic-font-family:auto; 	mso-font-pitch:variable; 	mso-font-signature:3 0 0 0 1 0;} @font-face 	{font-family:Wingdings; 	panose-1:5 2 1 2 1 8 4 8 7 8; 	mso-font-charset:2; 	mso-generic-font-family:auto; 	mso-font-pitch:variable; 	mso-font-signature:0 0 65536 0 -2147483648 0;} @font-face 	{font-family:Cambria; 	panose-1:2 4 5 3 5 4 6 3 2 4; 	mso-font-charset:0; 	mso-generic-font-family:auto; 	mso-font-pitch:variable; 	mso-font-signature:3 0 0 0 1 0;}  /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal 	{mso-style-parent:""; 	margin:0in; 	margin-bottom:.0001pt; 	mso-pagination:widow-orphan; 	font-size:12.0pt; 	font-family:"Times New Roman"; 	mso-ascii-font-family:Cambria; 	mso-ascii-theme-font:minor-latin; 	mso-fareast-font-family:Cambria; 	mso-fareast-theme-font:minor-latin; 	mso-hansi-font-family:Cambria; 	mso-hansi-theme-font:minor-latin; 	mso-bidi-font-family:"Times New Roman"; 	mso-bidi-theme-font:minor-bidi;} @page Section1 	{size:8.5in 11.0in; 	margin:1.0in 1.25in 1.0in 1.25in; 	mso-header-margin:.5in; 	mso-footer-margin:.5in; 	mso-paper-source:0;} div.Section1 	{page:Section1;}  /* List Definitions */ @list l0 	{mso-list-id:2000033213; 	mso-list-template-ids:1165763884;} @list l0:level1 	{mso-level-number-format:bullet; 	mso-level-text:?; 	mso-level-tab-stop:.5in; 	mso-level-number-position:left; 	text-indent:-.25in; 	mso-ansi-font-size:10.0pt; 	font-family:Symbol;} ol 	{margin-bottom:0in;} ul 	{margin-bottom:0in;} -->
* Support the notion of an      integrated user interface such that one or more protocol-specific      implementations can fit within the overall visual interaction framework.
* Allows the person to login and      to logout.
* Allows the person to use a      variable number of computers and/or mobile devices
* Allows that the specific device      being used may or may not have some kind of identity client software      integrated into the browser hereafter referred to as a _browser add-on_
* The user experience will be      optimized for the case where a browser add-on is present, but will still      function although with perhaps a less than ideal experience in the      browser-only case.
* Supports a wide range of sizes      of display surface for the interface.
* Accommodates the fact that the      Website (or local web-based application) supports one or more of the      following interaction methods: username/password, OpenID, Facebook      Connect, IMI Information Card, SAML, Google Friend Connect, Kerberos.
* Accommodates the fact that the browser      add-on, if present, supports one or more of the following login methods      (that the person is capable of using): OpenID, Facebook Connect, IMI,      SAML, Google Friend Connect, Kerberos.
* Accommodates the fact that the      person may be visually impaired or have other disabilities



The specifications must meet the following basic design principles, in addition to any emergent design principles later identified by this Work Group:



<!--  /* Font Definitions */ @font-face 	{font-family:"Courier New"; 	panose-1:2 7 3 9 2 2 5 2 4 4; 	mso-font-charset:0; 	mso-generic-font-family:auto; 	mso-font-pitch:variable; 	mso-font-signature:3 0 0 0 1 0;} @font-face 	{font-family:Times; 	panose-1:2 0 5 0 0 0 0 0 0 0; 	mso-font-charset:0; 	mso-generic-font-family:auto; 	mso-font-pitch:variable; 	mso-font-signature:3 0 0 0 1 0;} @font-face 	{font-family:Wingdings; 	panose-1:5 2 1 2 1 8 4 8 7 8; 	mso-font-charset:2; 	mso-generic-font-family:auto; 	mso-font-pitch:variable; 	mso-font-signature:0 0 65536 0 -2147483648 0;} @font-face 	{font-family:Cambria; 	panose-1:2 4 5 3 5 4 6 3 2 4; 	mso-font-charset:0; 	mso-generic-font-family:auto; 	mso-font-pitch:variable; 	mso-font-signature:3 0 0 0 1 0;}  /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal 	{mso-style-parent:""; 	margin:0in; 	margin-bottom:.0001pt; 	mso-pagination:widow-orphan; 	font-size:12.0pt; 	font-family:"Times New Roman"; 	mso-ascii-font-family:Cambria; 	mso-ascii-theme-font:minor-latin; 	mso-fareast-font-family:Cambria; 	mso-fareast-theme-font:minor-latin; 	mso-hansi-font-family:Cambria; 	mso-hansi-theme-font:minor-latin; 	mso-bidi-font-family:"Times New Roman"; 	mso-bidi-theme-font:minor-bidi;} @page Section1 	{size:8.5in 11.0in; 	margin:1.0in 1.25in 1.0in 1.25in; 	mso-header-margin:.5in; 	mso-footer-margin:.5in; 	mso-paper-source:0;} div.Section1 	{page:Section1;}  /* List Definitions */ @list l0 	{mso-list-id:1215242156; 	mso-list-template-ids:-1755021738;} @list l0:level1 	{mso-level-number-format:bullet; 	mso-level-text:?; 	mso-level-tab-stop:.5in; 	mso-level-number-position:left; 	text-indent:-.25in; 	mso-ansi-font-size:10.0pt; 	font-family:Symbol;} ol 	{margin-bottom:0in;} ul 	{margin-bottom:0in;} -->
* Simple to understand, implement      in an interoperable fashion, and deploy on an Internet-wide scale
* Modular (e.g. incorporating      other existing specifications by reference where appropriate, and breaking      down this Work Group's draft specifications into multiple pieces where      reuse by different communities is likely)
* Generative (able to be combined      and extended to support a variety of use cases and emerging application      functionality)
* Developed rapidly, in an      "agile specification" process that can refactor for emerging      needs



The following design solutions are initially out of scope for the first version of the group's output, though the group should avoid precluding such solutions, if possible, where they are analogous to in-scope solutions: <!--  /* Font Definitions */ @font-face 	{font-family:"Courier New"; 	panose-1:2 7 3 9 2 2 5 2 4 4; 	mso-font-charset:0; 	mso-generic-font-family:auto; 	mso-font-pitch:variable; 	mso-font-signature:3 0 0 0 1 0;} @font-face 	{font-family:Times; 	panose-1:2 0 5 0 0 0 0 0 0 0; 	mso-font-charset:0; 	mso-generic-font-family:auto; 	mso-font-pitch:variable; 	mso-font-signature:3 0 0 0 1 0;} @font-face 	{font-family:Wingdings; 	panose-1:5 2 1 2 1 8 4 8 7 8; 	mso-font-charset:2; 	mso-generic-font-family:auto; 	mso-font-pitch:variable; 	mso-font-signature:0 0 65536 0 -2147483648 0;} @font-face 	{font-family:Cambria; 	panose-1:2 4 5 3 5 4 6 3 2 4; 	mso-font-charset:0; 	mso-generic-font-family:auto; 	mso-font-pitch:variable; 	mso-font-signature:3 0 0 0 1 0;}  /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal 	{mso-style-parent:""; 	margin:0in; 	margin-bottom:.0001pt; 	mso-pagination:widow-orphan; 	font-size:12.0pt; 	font-family:"Times New Roman"; 	mso-ascii-font-family:Cambria; 	mso-ascii-theme-font:minor-latin; 	mso-fareast-font-family:Cambria; 	mso-fareast-theme-font:minor-latin; 	mso-hansi-font-family:Cambria; 	mso-hansi-theme-font:minor-latin; 	mso-bidi-font-family:"Times New Roman"; 	mso-bidi-theme-font:minor-bidi;} @page Section1 	{size:8.5in 11.0in; 	margin:1.0in 1.25in 1.0in 1.25in; 	mso-header-margin:.5in; 	mso-footer-margin:.5in; 	mso-paper-source:0;} div.Section1 	{page:Section1;}  /* List Definitions */ @list l0 	{mso-list-id:671957150; 	mso-list-template-ids:1113487554;} @list l0:level1 	{mso-level-number-format:bullet; 	mso-level-text:?; 	mso-level-tab-stop:.5in; 	mso-level-number-position:left; 	text-indent:-.25in; 	mso-ansi-font-size:10.0pt; 	font-family:Symbol;} ol 	{margin-bottom:0in;} ul 	{margin-bottom:0in;} -->* Other types of networked      applications besides Web-based ones
* Parties other than natural      persons wishing to login
* Non-login/lout interactions      including but not limited to account registration, password recovery, silent      authentication (e.g. of a computer to a network), digital signature      presentation, payment and credential presentation.<!--  /* Font Definitions */ @font-face 	{font-family:Times; 	panose-1:2 0 5 0 0 0 0 0 0 0; 	mso-font-charset:0; 	mso-generic-font-family:auto; 	mso-font-pitch:variable; 	mso-font-signature:3 0 0 0 1 0;} @font-face 	{font-family:Cambria; 	panose-1:2 4 5 3 5 4 6 3 2 4; 	mso-font-charset:0; 	mso-generic-font-family:auto; 	mso-font-pitch:variable; 	mso-font-signature:3 0 0 0 1 0;}  /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal 	{mso-style-parent:""; 	margin:0in; 	margin-bottom:.0001pt; 	mso-pagination:widow-orphan; 	font-size:12.0pt; 	font-family:"Times New Roman"; 	mso-ascii-font-family:Cambria; 	mso-ascii-theme-font:minor-latin; 	mso-fareast-font-family:Cambria; 	mso-fareast-theme-font:minor-latin; 	mso-hansi-font-family:Cambria; 	mso-hansi-theme-font:minor-latin; 	mso-bidi-font-family:"Times New Roman"; 	mso-bidi-theme-font:minor-bidi;} @page Section1 	{size:8.5in 11.0in; 	margin:1.0in 1.25in 1.0in 1.25in; 	mso-header-margin:.5in; 	mso-footer-margin:.5in; 	mso-paper-source:0;} div.Section1 	{page:Section1;} -->

The group will develop materials for workshops and conferences, and the coordinate speakers on ULX topics for such events.

*(4) DRAFT TECHNICAL SPECIFICATIONS:* _List Working Titles of draft Technical Specifications to be produced (if any), projected completion dates, and the Standards Setting Organization(s) to which they will be submitted upon approval by the Membership._

It is anticipated that the following technical specifications will be produced, with modular boundaries subject to change; they are anticipated to be submitted to the World Wide Web Consortium (W3C) for further work and completion:



<!--  /* Font Definitions */ @font-face 	{font-family:"Courier New"; 	panose-1:2 7 3 9 2 2 5 2 4 4; 	mso-font-charset:0; 	mso-generic-font-family:auto; 	mso-font-pitch:variable; 	mso-font-signature:3 0 0 0 1 0;} @font-face 	{font-family:Times; 	panose-1:2 0 5 0 0 0 0 0 0 0; 	mso-font-charset:0; 	mso-generic-font-family:auto; 	mso-font-pitch:variable; 	mso-font-signature:3 0 0 0 1 0;} @font-face 	{font-family:Wingdings; 	panose-1:5 2 1 2 1 8 4 8 7 8; 	mso-font-charset:2; 	mso-generic-font-family:auto; 	mso-font-pitch:variable; 	mso-font-signature:0 0 65536 0 -2147483648 0;} @font-face 	{font-family:Cambria; 	panose-1:2 4 5 3 5 4 6 3 2 4; 	mso-font-charset:0; 	mso-generic-font-family:auto; 	mso-font-pitch:variable; 	mso-font-signature:3 0 0 0 1 0;}  /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal 	{mso-style-parent:""; 	margin:0in; 	margin-bottom:.0001pt; 	mso-pagination:widow-orphan; 	font-size:12.0pt; 	font-family:"Times New Roman"; 	mso-ascii-font-family:Cambria; 	mso-ascii-theme-font:minor-latin; 	mso-fareast-font-family:Cambria; 	mso-fareast-theme-font:minor-latin; 	mso-hansi-font-family:Cambria; 	mso-hansi-theme-font:minor-latin; 	mso-bidi-font-family:"Times New Roman"; 	mso-bidi-theme-font:minor-bidi;} @page Section1 	{size:8.5in 11.0in; 	margin:1.0in 1.25in 1.0in 1.25in; 	mso-header-margin:.5in; 	mso-footer-margin:.5in; 	mso-paper-source:0;} div.Section1 	{page:Section1;}  /* List Definitions */ @list l0 	{mso-list-id:41641141; 	mso-list-template-ids:1679715028;} @list l0:level1 	{mso-level-number-format:bullet; 	mso-level-text:?; 	mso-level-tab-stop:.5in; 	mso-level-number-position:left; 	text-indent:-.25in; 	mso-ansi-font-size:10.0pt; 	font-family:Symbol;} ol 	{margin-bottom:0in;} ul 	{margin-bottom:0in;} -->
* Universal Login UX      Specification
* Login Metadata Discovery -- A      mechanism whereby a browser with an add-on can discover the      supported/preferred login method(s).



*(5) OTHER DRAFT RECOMMENDATIONS:* _Other Draft Recommendations and projected completion dates for submission for All Member Ballot._

Universal Login UX Best Practices and Walkthrough Documentation

At the group's option, some of this material may be considered non-normative (equivalent to white papers).

*(6) LEADERSHIP:* _Proposed WG Chair and Editor(s) (if any) subject to confirmation by a vote of the WG Participants._

* Co-Chair:  RL