Also adding Paul Trevithich (<a href="mailto:Paul@azigo.com">Paul@azigo.com</a>) as a co-proposer.<br><br><div class="gmail_quote">On Tue, May 25, 2010 at 11:15 AM, Joseph Smarr <span dir="ltr"><<a href="mailto:jsmarr@gmail.com">jsmarr@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">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<br>
<div><br></div><div><p class="MsoNormal"><b>(a)</b><b> <i><u>Charter</u></i>.</b></p>
<p class="MsoNormal" style="margin-top:0in;margin-right:0in;margin-bottom:2.0pt;margin-left:.5in"><b>(i)</b><span> </span><b>WG name:</b> OpenID
v.Next Attributes</p>
<p class="MsoNormal" style="margin-top:0in;margin-right:0in;margin-bottom:2.0pt;margin-left:.5in"><b>(ii)</b><span> </span><b>Purpose:</b> 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.<span> </span>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.<span>
</span>Specific goals are:</p>
<p style="margin-top:0in;margin-right:0in;margin-bottom:2.0pt;margin-left:45.0pt"><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">
</span></span></span>define how to ask for and get rich, consistent,
common and extensible data attributes,</p>
<p style="margin-top:0in;margin-right:0in;margin-bottom:2.0pt;margin-left:45.0pt"><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">
</span></span></span>define schemas for common attributes,</p>
<p style="margin-top:0in;margin-right:0in;margin-bottom:2.0pt;margin-left:45.0pt"><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">
</span></span></span>define a mechanism and process for using
attributes not in this common set,</p>
<p style="margin-top:0in;margin-right:0in;margin-bottom:2.0pt;margin-left:45.0pt"><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">
</span></span></span>enable user control over what attributes are
released,</p>
<p style="margin-top:0in;margin-right:0in;margin-bottom:2.0pt;margin-left:45.0pt"><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">
</span></span></span>enable aggregation of attributes from multiple attribute
sources,</p>
<p style="margin-top:0in;margin-right:0in;margin-bottom:2.0pt;margin-left:45.0pt"><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">
</span></span></span>enable attribute sources to provide verified
attributes,</p>
<p style="margin-top:0in;margin-right:0in;margin-bottom:2.0pt;margin-left:45.0pt"><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">
</span></span></span>enable the sources of attributes to be verified,</p>
<p style="margin-top:0in;margin-right:0in;margin-bottom:2.0pt;margin-left:45.0pt"><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">
</span></span></span>enable the use of attributes by non-browser
applications</p>
<p style="margin-top:0in;margin-right:0in;margin-bottom:2.0pt;margin-left:45.0pt"><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">
</span></span></span>enable the use of attributes both with and
without employing an active client,</p>
<p style="margin-top:0in;margin-right:0in;margin-bottom:2.0pt;margin-left:45.0pt"><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">
</span></span></span>seamlessly integrate with and complement the
other OpenID v.Next specifications.</p>
<p class="MsoNormal" style="margin-top:0in;margin-right:0in;margin-bottom:2.0pt;margin-left:.5in"><span><span> </span>Compatibility with OpenID 2.0 is an
explicit non-goal for this work.</span></p>
<p class="MsoNormal" style="margin-top:0in;margin-right:0in;margin-bottom:2.0pt;margin-left:.5in"><b>(iii)</b><span> </span><b>Scope:</b> Produce
a next generation OpenID attribute specification or specifications, consistent
with the purpose statement.</p>
<p class="MsoNormal" style="margin-top:0in;margin-right:0in;margin-bottom:2.0pt;margin-left:.5in"><b>(iv)</b><span> </span><b>Proposed List of
Specifications</b>: OpenID v.Next Attribute Transmission and Attribute
Schema specifications and possibly related specifications.</p>
<p class="MsoNormal" style="margin-top:0in;margin-right:0in;margin-bottom:2.0pt;margin-left:.5in"><b>(v)</b><span> </span><b>Anticipated audience or
users of the work:</b> Implementers of OpenID Providers, Relying Parties,
Active Clients, and non-browser applications utilizing OpenID.</p>
<p class="MsoNormal" style="margin-top:0in;margin-right:0in;margin-bottom:2.0pt;margin-left:.5in"><b>(vi)</b><span> </span><b>Language in which the WG
will conduct business</b>: English.</p>
<p class="MsoNormal" style="margin-top:0in;margin-right:0in;margin-bottom:2.0pt;margin-left:.5in"><b>(vii)</b><span> </span><b>Method of work: </b>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.</p>
<p class="MsoNormal" style="margin-top:0in;margin-right:0in;margin-bottom:2.0pt;margin-left:.5in"><b>(viii)</b><span> </span><b>Basis for determining when
the work of the WG is completed:</b> 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.<span> </span>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.</p>
<p class="MsoNormal"><b>(b)</b><b> <i><u>Background
Information</u></i>.</b></p>
<p class="MsoNormal" style="margin-top:0in;margin-right:0in;margin-bottom:2.0pt;margin-left:.5in"><b>(i)</b><span> </span><b>Related work being done
in other WGs or organizations</b>: OpenID Authentication 2.0 and related
specifications, including Attribute Exchange (AX) and Simple Registration
(SReg).<span> </span>ICF Schemas working group.<span> </span>Portable Contacts.<span> </span>Other OpenID v.Next working groups and the
OpenID Connect working group.</p>
<p class="MsoNormal" style="margin-top:0in;margin-right:0in;margin-bottom:2.0pt;margin-left:.5in"><b>(ii)</b><span> </span><b>Proposers:</b> </p>
<p class="MsoNormal" style="margin-left:.5in">Joseph Smarr, <a href="mailto:jsmarr@google.com" target="_blank">jsmarr@google.com</a>, Google (chair)</p>
<p class="MsoNormal" style="margin-left:.5in">Michael B. Jones, <a href="mailto:mbj@microsoft.com" target="_blank">mbj@microsoft.com</a>, Microsoft</p>
<p class="MsoNormal" style="margin-left:.5in">Dick Hardt, <a href="mailto:dick.hardt@gmail.com" target="_blank">dick.hardt@gmail.com</a>, independent</p>
<p class="MsoNormal" style="margin-left:.5in">Nat Sakimura <a href="mailto:n-sakimura@nri.co.jp" target="_blank">n-sakimura@nri.co.jp</a>, NRI</p>
<p class="MsoNormal" style="margin-left:.5in">John Bradley <a href="mailto:ve7jtb@ve7jtb.com" target="_blank">ve7jtb@ve7jtb.com</a>, independent</p>
<p class="MsoNormal" style="margin-left:.5in">Paul Madsen <a href="mailto:paulmadsen@rogers.com" target="_blank">paulmadsen@rogers.com</a>, individual</p>
<p class="MsoNormal" style="margin-top:0in;margin-right:0in;margin-bottom:2.0pt;margin-left:.5in"><b><span> </span>(iii)</b><span> </span><b>Anticipated Contributions</b>: None.</p>
<p class="MsoNormal"> </p></div>
</blockquote></div><br>