+1 to what DeWitt said as well.<div><br></div><div>The WG process should support the parallel development of v.Next and Connect. It is unclear that either is better at this point, and I think it's worth investigating each path to their logical conclusions.</div>
<div><br></div><div>As there has been much desire to see v.Next advance, and much frustration that scant results have been produced in the last six months, I think OpenID Connect provides a nice — as Don Thibeau would say — forcing function to help us make some real progress. Competition between two working groups would not be entirely a bad thing provided that they are both able to articulate clear goals that produce a sensible, implementable technology stack.</div>
<div><br></div><div>I see OpenID Connect as a product — which may and may not be able to form the basis of v.Next — but that should inform the work of the v.Next working group without dictating it.</div><div><br></div><div>
Chris<br><br><div class="gmail_quote">On Thu, May 20, 2010 at 10:46 AM, David Recordon <span dir="ltr"><<a href="mailto:recordond@gmail.com">recordond@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
+1 to what DeWitt said<div><div></div><div class="h5"><br><br><div class="gmail_quote">On Thu, May 20, 2010 at 10:45 AM, DeWitt Clinton <span dir="ltr"><<a href="mailto:dewitt@google.com" target="_blank">dewitt@google.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
>From where I'm sitting, I see them as mutually compatible and parallel goals, but not now the same technology, <i>and that's okay</i>.<div><br></div><div>Connect being "build on what the web is already doing and very much wants/needs <i>today</i>", and v.Next being "what could be done given the luxury of time to explore."</div>
<div><br></div><div>The OIDF could make an effort to wait for the latter to build the former, but honestly, the former isn't going to wait for the OIDF. Which is why I advocate a parallel approach if we hope to see the OIDF involved (and I do).<br>
<div><br></div><div>Please correct my understanding of the situation if I got the above wrong, as I'm only following the discussions from the edges and I'm (blissfully) out of the loop.</div><div><br><div>-DeWitt</div>
</div><br><div class="gmail_quote"><div>On Thu, May 20, 2010 at 10:36 AM, Brian Kissel <span dir="ltr"><<a href="mailto:bkissel@janrain.com" target="_blank">bkissel@janrain.com</a>></span> wrote:<br></div>
<div><div></div><div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
+1 to Nat's suggestion. While we know that both David and Joseph are very<br>
well qualified to lead this committee, if we do have differing<br>
perspectives on the future direction of the next iterations of OpenID, it<br>
would be good to have representatives from both perspectives involved in<br>
leading the process.<br>
<div><br>
Cheers,<br>
<br>
Brian<br>
___________<br>
<br>
Brian Kissel<br>
CEO - JanRain, Inc.<br>
<a href="mailto:bkissel@janrain.com" target="_blank">bkissel@janrain.com</a><br>
Mobile: 503.342.2668 | Fax: 503.296.5502<br>
519 SW 3rd Ave. Suite 600 Portland, OR 97204<br>
<br>
Increase registrations, engage users, and grow your brand with RPX. Learn<br>
more at <a href="http://www.rpxnow.com" target="_blank">www.rpxnow.com</a><br>
<br>
</div><div>-----Original Message-----<br>
From: <a href="mailto:openid-board-bounces@lists.openid.net" target="_blank">openid-board-bounces@lists.openid.net</a><br>
</div><div>[mailto:<a href="mailto:openid-board-bounces@lists.openid.net" target="_blank">openid-board-bounces@lists.openid.net</a>] On Behalf Of Nat Sakimura<br>
Sent: Thursday, May 20, 2010 12:09 AM<br>
To: <a href="mailto:openid-board@lists.openid.net" target="_blank">openid-board@lists.openid.net</a><br>
Subject: Re: [OpenID board] Technical Committee Chairs<br>
<br>
</div><div><div></div><div>I have a little concern here. It might be a healthy thing to have<br>
discussions, but in the end, I really want v.Next and Connect camp to<br>
unite. In that respect, both chair and co-chair coming from Connect<br>
camp bothers me.<br>
<br>
You say that Joseph was close to be a co-chair, but the situation<br>
surrounding it has changed since then. At the time, there was only<br>
v.Next. Now, it looks like there are v.Next and Connect camp.<br>
<br>
Do not you think it is better to first ask v.Next camp people to step up?<br>
<br>
Would not somebody form v.Next camp step up?<br>
<br>
=nat<br>
<br>
<br>
On Thu, May 20, 2010 at 3:23 PM, David Recordon <<a href="mailto:recordond@gmail.com" target="_blank">recordond@gmail.com</a>><br>
wrote:<br>
> The committee elects its own chairs. A few months ago we elected Dick as<br>
> chair and me as co-chair. Joseph was really close to being co-chair.<br>
><br>
> On Wed, May 19, 2010 at 11:22 PM, Nat Sakimura <<a href="mailto:sakimura@gmail.com" target="_blank">sakimura@gmail.com</a>><br>
wrote:<br>
>><br>
>> So, what is the process that chooses committee chairs?<br>
>><br>
>> On Thu, May 20, 2010 at 3:01 PM, David Recordon <<a href="mailto:recordond@gmail.com" target="_blank">recordond@gmail.com</a>><br>
>> wrote:<br>
>> > Today the Board passed a resolution directing the Executive Director,<br>
>> > Chair,<br>
>> > Technical Committee, and outside council to explore a contracting<br>
>> > relationship with Dick Hardt to move the v.Next work forward. Dick<br>
>> > brought<br>
>> > up how there could be a conflict during this process given that he is<br>
>> > the<br>
>> > chair of the Technical Committee. So for the time being I'll take on<br>
the<br>
>> > chair role with Joseph Smarr (who wasn't at the meeting but I spoke<br>
to a<br>
>> > few<br>
>> > hours ago) taking on the co-chair role.<br>
>> > Technical Committee, expect a followup email around starting to pull<br>
>> > together a set of deliverables and timeline over the next week. The<br>
>> > goal, as<br>
>> > I understand it, is to either have a contract in place or a<br>
>> > determination<br>
>> > that it is unfeasible by the end of the this month.<br>
>> ><br>
>> > Thanks,<br>
>> > --David<br>
>> > _______________________________________________<br>
>> > board mailing list<br>
>> > <a href="mailto:board@lists.openid.net" target="_blank">board@lists.openid.net</a><br>
>> > <a href="http://lists.openid.net/mailman/listinfo/openid-board" target="_blank">http://lists.openid.net/mailman/listinfo/openid-board</a><br>
>> ><br>
>> ><br>
>><br>
>><br>
>><br>
>> --<br>
>> Nat Sakimura (=nat)<br>
>> <a href="http://www.sakimura.org/en/" target="_blank">http://www.sakimura.org/en/</a><br>
>> <a href="http://twitter.com/_nat_en" target="_blank">http://twitter.com/_nat_en</a><br>
>> _______________________________________________<br>
>> board mailing list<br>
>> <a href="mailto:board@lists.openid.net" target="_blank">board@lists.openid.net</a><br>
>> <a href="http://lists.openid.net/mailman/listinfo/openid-board" target="_blank">http://lists.openid.net/mailman/listinfo/openid-board</a><br>
><br>
><br>
> _______________________________________________<br>
> board mailing list<br>
> <a href="mailto:board@lists.openid.net" target="_blank">board@lists.openid.net</a><br>
> <a href="http://lists.openid.net/mailman/listinfo/openid-board" target="_blank">http://lists.openid.net/mailman/listinfo/openid-board</a><br>
><br>
><br>
<br>
<br>
<br>
--<br>
Nat Sakimura (=nat)<br>
<a href="http://www.sakimura.org/en/" target="_blank">http://www.sakimura.org/en/</a><br>
<a href="http://twitter.com/_nat_en" target="_blank">http://twitter.com/_nat_en</a><br>
_______________________________________________<br>
board mailing list<br>
<a href="mailto:board@lists.openid.net" target="_blank">board@lists.openid.net</a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-board" target="_blank">http://lists.openid.net/mailman/listinfo/openid-board</a><br>
_______________________________________________<br>
board mailing list<br>
<a href="mailto:board@lists.openid.net" target="_blank">board@lists.openid.net</a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-board" target="_blank">http://lists.openid.net/mailman/listinfo/openid-board</a><br>
</div></div></blockquote></div></div></div><br></div>
<br>_______________________________________________<br>
board mailing list<br>
<a href="mailto:board@lists.openid.net" target="_blank">board@lists.openid.net</a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-board" target="_blank">http://lists.openid.net/mailman/listinfo/openid-board</a><br>
<br></blockquote></div><br>
</div></div><br>_______________________________________________<br>
board mailing list<br>
<a href="mailto:board@lists.openid.net">board@lists.openid.net</a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-board" target="_blank">http://lists.openid.net/mailman/listinfo/openid-board</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Chris Messina<br>Open Web Advocate, Google<br><br>Personal: <a href="http://factoryjoe.com">http://factoryjoe.com</a><br>Follow me on Buzz: <a href="http://buzz.google.com/chrismessina">http://buzz.google.com/chrismessina</a> <br>
...or Twitter: <a href="http://twitter.com/chrismessina">http://twitter.com/chrismessina</a> <br><br>This email is: [ ] shareable [X] ask first [ ] private<br>
</div>