Joseph, now that HP is in charge, Pre sales will soar. I predict you and I will be joined by a 3rd user within the month<br><br><span style="font-family:Prelude, Verdana, san-serif;"><br><br></span><span id="signature"><div style="font-family: arial, sans-serif; font-size: 12px;color: #999999;">-- Sent from my Palm Prē</div><br></span><span style="color:navy; font-family:Prelude, Verdana, san-serif; "><hr align="left" style="width:75%">On 10 May 2010 6:40 p.m., Joseph Smarr <jsmarr@gmail.com> wrote: <br><br>Yeah, I think at least specifying a way for IdPs to say "I consider this verified, so if you trust me, you can too" should be part of what the working group considers. <div><br></div><div>(And I'm not just agreeing because you sent this via a Palm Pre, which apparently makes you the only person besides me still proudly using one, heh!)</div>
<div><br></div><div>Thanks, js<br><br><div class="gmail_quote">On Mon, May 10, 2010 at 3:24 PM, Paul Madsen <span dir="ltr"><<a href="mailto:paulmadsen@rogers.com">paulmadsen@rogers.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
How about a goal of<br><br>Define how to describe if, and/or how, a given attribute was verified. Also, define how a RP can indicate its desires for verification of requested attributes<br><br><span style="font-family:Prelude, Verdana, san-serif">Paul<br>
<br></span><span><div style="font-family:arial, sans-serif;font-size:12px;color:#999999">-- Sent from my Palm Prē</div><br></span><span style="color:navy;font-family:Prelude, Verdana, san-serif"><hr align="left" style="width:75%">
<div><div></div><div class="h5">On 10 May 2010 4:07 p.m., Phillip Hallam-Baker <<a href="mailto:hallam@gmail.com" target="_blank">hallam@gmail.com</a>> wrote: <br><br>If by that you mean the administrative processes by which third
<br>parties verify the attributes, I think that should be completely out
<br>of scope for OpenID. Leave that to groups like WebTrust and CABForum.
<br>
<br>The only area where the group needs to address validation of
<br>attributes is to recognize the requirements for doing this. For
<br>example, a TTP acts in the same role as a notary: they do not certify
<br>the conclusion, they certify the process by which the conclusion was
<br>reached.
<br>
<br>On Mon, May 10, 2010 at 3:53 PM, Chris Obdam <<a href="mailto:chris.obdam@holder.nl" target="_blank">chris.obdam@holder.nl</a>> wrote:
<br>> I am missing the validation of attributes?
<br>> Op 10 mei 2010, om 20:09 heeft Joseph Smarr het volgende geschreven:
<br>>
<br>> Hey guys, I volunteered to drive the "attributes" working group for OpenID
<br>> v.Next, so here's a proposed charter, feedback welcome. Thanks to Mike Jones
<br>> for actually writing up the first draft and getting me to act on it! :) js
<br>>
<br>> (a) Charter.
<br>>
<br>> (i) WG name: OpenID v.Next Attributes
<br>>
<br>> (ii) Purpose: Produce attribute transmission
<br>> and schema specifications for OpenID v.Next that address the limitations and
<br>> drawbacks present in the OpenID 2.0 attribute facilities that
<br>> limit OpenID’s applicability, adoption, usability, and
<br>> interoperability. Sharing basic data about the user has become a common
<br>> enough requirement that OpenID needs to take a more hands-on role in
<br>> specifying common fields and also more tightly/actively working on how to
<br>> propose and accept new standard fields going forward. Specific goals are:
<br>>
<br>> · define how to ask for and get rich, consistent, common and extensible data
<br>> attributes,
<br>>
<br>> · define schemas for common attributes,
<br>>
<br>> · define a mechanism and process for using attributes not in this common
<br>> set,
<br>>
<br>> · enable user control over what attributes are released,
<br>>
<br>> · enable aggregation of attributes from multiple verifiable attribute
<br>> sources,
<br>>
<br>> · enable the use of attributes by non-browser applications
<br>>
<br>> · enable the use of attributes both with and without employing an active
<br>> client,
<br>>
<br>> · seamlessly integrate with and complement the other OpenID v.Next
<br>> specifications.
<br>>
<br>> Compatibility with OpenID 2.0 is an explicit non-goal
<br>> for this work.
<br>>
<br>> (iii) Scope: Produce a next generation
<br>> OpenID attribute specification or specifications, consistent with the
<br>> purpose statement.
<br>>
<br>> (iv) Proposed List of Specifications: OpenID v.Next Attribute
<br>> Transmission and Attribute Schema specifications and possibly
<br>> related specifications.
<br>>
<br>> (v) Anticipated audience or users of the work: Implementers of
<br>> OpenID Providers, Relying Parties, Active Clients, and non-browser
<br>> applications utilizing OpenID.
<br>>
<br>> (vi) Language in which the WG will conduct business: English.
<br>>
<br>> (vii) Method of work: E-mail discussions on the working group
<br>> mailing list, working group conference calls, and face-to-face
<br>> meetings at the Internet Identity Workshop and OpenID summits.
<br>>
<br>> (viii) Basis for determining when the work of the WG is
<br>> completed: Work will not be deemed to be complete until there is a
<br>> consensus that the resulting protocol specification or family of
<br>> specifications fulfills the working group goals. Additional proposed
<br>> changes beyond that initial consensus will be evaluated on the basis of
<br>> whether they increase or decrease consensus within the working group. The
<br>> work will be completed once it is apparent that maximal consensus on the
<br>> draft has been achieved, consistent with the purpose and scope.
<br>>
<br>> (b) Background Information.
<br>>
<br>> (i) Related work being done in other WGs or
<br>> organizations: OpenID Authentication 2.0 and related specifications,
<br>> including Attribute Exchange (AX) and Simple Registration (SReg). ICF
<br>> Schemas working group. Portable Contacts.
<br>>
<br>> (ii) Proposers:
<br>>
<br>> Joseph Smarr, <a href="mailto:jsmarr@google.com" target="_blank">jsmarr@google.com</a>, Google (chair)
<br>> Additional proposers to be added here
<br>>
<br>> (iii) Anticipated Contributions: None.
<br>>
<br>> _______________________________________________
<br>> specs mailing list
<br>> <a href="mailto:specs@lists.openid.net" target="_blank">specs@lists.openid.net</a>
<br>> <a href="http://lists.openid.net/mailman/listinfo/openid-specs" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs</a>
<br>>
<br>>
<br>> _______________________________________________
<br>> specs mailing list
<br>> <a href="mailto:specs@lists.openid.net" target="_blank">specs@lists.openid.net</a>
<br>> <a href="http://lists.openid.net/mailman/listinfo/openid-specs" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs</a>
<br>>
<br>>
<br>
<br>
<br>
<br>--
<br>Website: <a href="http://hallambaker.com/" target="_blank">http://hallambaker.com/</a>
<br></div></div>_______________________________________________
<br><div class="im">specs mailing list
<br><a href="mailto:specs@lists.openid.net" target="_blank">specs@lists.openid.net</a>
<br><a href="http://lists.openid.net/mailman/listinfo/openid-specs" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs</a>
<br></div></span>
</blockquote></div><br></div>
</span>