formal proposal for forming OpenID v.Next Attributes Working Group
Joseph Smarr
jsmarr at gmail.com
Tue May 25 18:38:03 UTC 2010
Also adding Paul Trevithich (Paul at azigo.com) as a co-proposer.
On Tue, May 25, 2010 at 11:15 AM, Joseph Smarr <jsmarr at gmail.com> wrote:
> Hi guys, thanks for your feedback, here is an updated proposal for forming
> the v.Next Attributes working group, which I now consider a formal request.
> Thanks again to Mike Jones for collecting the feedback and updating the
> charter text! js
>
> *(a)** Charter.*
>
> *(i)* *WG name:* OpenID v.Next Attributes
>
> *(ii)* *Purpose:* Produce attribute transmission and schema
> specifications for OpenID v.Next that address the limitations and drawbacks
> present in the OpenID 2.0 attribute facilities that limit OpenID’s
> applicability, adoption, usability, and interoperability. Sharing basic
> data about the user has become a common enough requirement that OpenID needs
> to take a more hands-on role in specifying common fields and also more
> tightly/actively working on how to propose and accept new standard fields
> going forward. Specific goals are:
>
> · define how to ask for and get rich, consistent, common and
> extensible data attributes,
>
> · define schemas for common attributes,
>
> · define a mechanism and process for using attributes not in this
> common set,
>
> · enable user control over what attributes are released,
>
> · enable aggregation of attributes from multiple attribute
> sources,
>
> · enable attribute sources to provide verified attributes,
>
> · enable the sources of attributes to be verified,
>
> · enable the use of attributes by non-browser applications
>
> · enable the use of attributes both with and without employing an
> active client,
>
> · seamlessly integrate with and complement the other OpenID v.Next
> specifications.
>
> Compatibility with OpenID 2.0 is an explicit non-goal for this
> work.
>
> *(iii)* *Scope:* Produce a next generation OpenID attribute
> specification or specifications, consistent with the purpose statement.
>
> *(iv)* *Proposed List of Specifications*: OpenID v.Next Attribute
> Transmission and Attribute Schema specifications and possibly related
> specifications.
>
> *(v)* *Anticipated audience or users of the work:* Implementers of
> OpenID Providers, Relying Parties, Active Clients, and non-browser
> applications utilizing OpenID.
>
> *(vi)* *Language in which the WG will conduct business*: English.
>
> *(vii)* *Method of work: *E-mail discussions on the working group
> mailing list, working group conference calls, and face-to-face meetings at
> the Internet Identity Workshop and OpenID summits.
>
> *(viii)* *Basis for determining when the work of the WG is completed:*
> Work will not be deemed to be complete until there is a consensus that the
> resulting protocol specification or family of specifications fulfills the
> working group goals. Additional proposed changes beyond that initial
> consensus will be evaluated on the basis of whether they increase or
> decrease consensus within the working group. The work will be completed
> once it is apparent that maximal consensus on the draft has been achieved,
> consistent with the purpose and scope.
>
> *(b)** Background Information.*
>
> *(i)* *Related work being done in other WGs or organizations*:
> OpenID Authentication 2.0 and related specifications, including Attribute
> Exchange (AX) and Simple Registration (SReg). ICF Schemas working group.
> Portable Contacts. Other OpenID v.Next working groups and the OpenID
> Connect working group.
>
> *(ii)* *Proposers:*
>
> Joseph Smarr, jsmarr at google.com, Google (chair)
>
> Michael B. Jones, mbj at microsoft.com, Microsoft
>
> Dick Hardt, dick.hardt at gmail.com, independent
>
> Nat Sakimura n-sakimura at nri.co.jp, NRI
>
> John Bradley ve7jtb at ve7jtb.com, independent
>
> Paul Madsen paulmadsen at rogers.com, individual
>
> * (iii)* *Anticipated Contributions*: None.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs/attachments/20100525/4887b5f7/attachment.html>
More information about the specs
mailing list