Great work Allen! Exactly what the doctor ordered! <br><br><div class="gmail_quote">On Sat, May 22, 2010 at 9:10 PM, Nat <span dir="ltr"><<a href="mailto:sakimura@gmail.com">sakimura@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Yes. Let us go.<br><font color="#888888">
<br>
=nat @ Mountain View via iPhone</font><div><div></div><div class="h5"><br>
<br>
On 2010/05/22, at 14:11, John Bradley <<a href="mailto:ve7jtb@ve7jtb.com" target="_blank">ve7jtb@ve7jtb.com</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Agreed,<br>
<br>
Once the charter is approved lets get this party started.<br>
<br>
John B.<br>
On 2010-05-21, at 7:58 PM, Breno de Medeiros wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Agreed.<br>
<br>
While it's clear that other WGs might have to coordinate with the<br>
discovery WG, I think there's value in having a separate discovery WG<br>
for the reasons you mention.<br>
<br>
On Fri, May 21, 2010 at 19:28, Allen Tom <<a href="mailto:atom@yahoo-inc.com" target="_blank">atom@yahoo-inc.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi All,<br>
<br>
Regarding all the various WG proposals – at least with the Discovery WG, I<br>
think there’s universal consensus that the existing OpenID 2.0 discovery<br>
mechanism is very deficient and must be revised or even completely<br>
replaced. Yadis is obsolete and overly complex, and there’s been a lot of<br>
innovation in Discovery after OpenID 2.0 was finalized.<br>
<br>
The authors of the OpenID User Interface extension found several cases where<br>
OpenID discovery needed to be updated, yet extending the existing 2.0<br>
discovery did not quite work. (RP/OP Logos/Metadata, publishing which UI<br>
modes and display languages were supported, support for browser assistants,<br>
etc)<br>
<br>
The Discovery WG charter is well defined and focused – the output of the WG<br>
is expected to be usable for future iterations of OpenID. Given that the<br>
community wants to quickly advance OpenID, my hope is that the future<br>
discovery work can be developed in parallel and kept in sync with the other<br>
initiatives.<br>
<br>
Allen<br>
<br>
<br>
On 5/21/10 6:05 PM, "Allen Tom" <<a href="mailto:atom@yahoo-inc.com" target="_blank">atom@yahoo-inc.com</a>> wrote:<br>
<br>
Per the OpenID Foundation IPR policies and procedures, this note formally<br>
proposes the formation of a new OpenID working group. The charter and<br>
background information for the proposed group are as follows.<br>
<br>
(a) Charter.<br>
(i) WG name: OpenID v.Next Discovery.<br>
(ii) Purpose: Produce a discovery specification or family of discovery<br>
specifications for OpenID v.Next that address the limitations and drawbacks<br>
present in the OpenID 2.0 discovery facilities that limit OpenID’s<br>
applicability, adoption, usability, privacy, and security. Specific goals<br>
are:<br>
· enable discovery for and normalization of OpenID identifiers,<br>
including those utilizing e-mail address syntax and those that are URLs,<br>
<br>
· enable discovery of features supported by OpenID v.Next OpenID<br>
Providers and Relying Parties,<br>
<br>
· enable discovery of attributes about OpenID v.Next OPs and RPs,<br>
including, but not limited to visual logos and human-readable site names,<br>
<br>
· enable discovery supporting a spectrum of clients, including passive<br>
clients per current usage, thin active clients, and active clients with OP<br>
functionality,<br>
<br>
· enable discovery supporting authentication to and use of attributes by<br>
non-browser applications,<br>
<br>
· enable discovery of public keys,<br>
<br>
· enable potential mechanisms for discovering context-relevant OpenID<br>
providers,<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 for this<br>
work.<br>
(iii) Scope: Produce a next generation OpenID discovery specification or<br>
specifications, consistent with the purpose statement.<br>
(iv) Proposed List of Specifications: OpenID v.Next Discovery and<br>
possibly related specifications.<br>
(v) Anticipated audience or users of the work: Implementers of OpenID<br>
Providers, Relying Parties, Active Clients, and non-browser applications<br>
utilizing OpenID.<br>
(vi) Language in which the WG will conduct business: English.<br>
(vii) Method of work: E-mail discussions on the working group mailing<br>
list, working group conference calls, and face-to-face meetings at the<br>
Internet Identity Workshop and OpenID summits.<br>
(viii) Basis for determining when the work of the WG is completed: Work<br>
will not be deemed to be complete until there is a consensus that the<br>
resulting protocol specification or family of specifications fulfills the<br>
working group goals. Additional proposed changes beyond that initial<br>
consensus will be evaluated on the basis of whether they increase or<br>
decrease consensus within the working group. The work will be completed<br>
once it is apparent that maximal consensus on the draft has been achieved,<br>
consistent with the purpose and scope.<br>
(b) Background Information.<br>
(i) Related work being done in other WGs or organizations: OpenID<br>
Authentication 2.0 and related specifications, including Yadis 1.0. OAuth<br>
and OAuth 2.0. XRDS, XRD, host-meta, Web Linking, XAuth, LRDD, and<br>
WebFinger.<br>
(ii) Proposers:<br>
Allen Tom, <a href="mailto:atom@yahoo-inc.com" target="_blank">atom@yahoo-inc.com</a>, Yahoo! (co-chair)<br>
Michael B. Jones, <a href="mailto:mbj@microsoft.com" target="_blank">mbj@microsoft.com</a>, Microsoft (co-chair)<br>
John Bradley, <a href="mailto:ve7jtb@ve7jtb.com" target="_blank">ve7jtb@ve7jtb.com</a>, independent<br>
Dick Hardt, <a href="mailto:dick.hardt@gmail.com" target="_blank">dick.hardt@gmail.com</a>, independent<br>
<br>
<br>
</blockquote>
<br>
<br>
<br>
-- <br>
--Breno<br>
<br>
+1 (650) 214-1007 desk<br>
+1 (408) 212-0135 (Grand Central)<br>
MTV-41-3 : 383-A<br>
PST (GMT-8) / PDT(GMT-7)<br>
</blockquote>
<br>
</blockquote></div></div><div><div></div><div class="h5">
_______________________________________________<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>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><a href="http://hi.im/santosh">http://hi.im/santosh</a><br><br><br>