Edit History since 0.90
Version 1.1 (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 and an enabling technical framework 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, required consents, as well as logging out. It encompasses the process of the selection of the user's Identity Provider as described in the Liberty Identity Provider Selector MRD [1]. Assumed is a range of initial conditions, protocols, and relationships between the application and identity services including identity providers and identity provider selection agents (ISAs). 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, OAuth and IMI Information Card), communities supporting de facto standards (e.g. OpenID, 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: (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: The specifications must meet the following basic design principles, in addition to any emergent design principles later identified by this Work Group: 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: 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) or OASIS for further work and completion: (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 (6) LEADERSHIP: Proposed WG Chair and Editor(s) (if any) subject to confirmation by a vote of the WG Participants. • Co-Chair: RL “Bob” Morgan, Internet2/University of Washington NOTE: For the purpose of formation, Paul Trevithick will act as the convener for the group and the initial primary point of contact. (7) AUDIENCE: Anticipated audience or users of the work. The anticipated audience for the documents produced by this Work Group includes developers, deployers, and designers of online services that act on behalf of individual users. The Work Group also anticipates gathering input from individual users of online services, in order to answer their needs and preferences to the extent possible. (8) DURATION: Objective criteria for determining when the work of the WG has been completed (or a statement that the WG is intended to be a standing WG to address work that is expected to be ongoing). This Work Group will target producing use cases and requirements including those of the Liberty Alliance Identity Provider Selector MRD [1] within 6 months of inception in order to guide its design effort, and will target 18-24 months to develop a V1.0 set of technical specifications and other auxiliary materials, facilitating the development of multiple independent reference implementations as appropriate during this time. The duration of this workgroup is intended to be indefinite, and charter may be amended from time to time, with changes approved by the Leadership Council. Kantara IPR Policy – Option Liberty [2] 10) RELATED WORK AND LIAISONS: Related work being done in other WGs or other organizations and any proposed liaison with those other WGs or organizations. This Work Group has a number of dependencies on, and shared goals with, the output of other efforts. Following are examples of other Kantara groups and external efforts with which this Work Group intends to liaise informally (absence from this list does not indicate a lack of interest in a liaison relationship): (11) CONTRIBUTIONS (optional): A list of contributions that the proposers anticipate will be made to the WG. None. (12) PROPOSERS: Names, email addresses, and any constituent affiliations of at least the minimum set of proposers required to support forming the WG. • Co-Chair: RL “Bob” Morgan, Internet2, University of Washington References |
Bookmarks
Is this site useful to you? Please share it! On This Page:
Pages in this Space:
|
Charter
Labels:
None