<br><br><div><span class="gmail_quote">On 2/6/07, <b class="gmail_sendername">Chris Messina</b> <<a href="mailto:chris.messina@gmail.com">chris.messina@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I would argue that this only accelerates our need to come up with<br>documentation, use cases, interfaces-in-the-wild (which I continue to<br>collect: <a href="http://www.flickr.com/photos/factoryjoe/tags/loginform">http://www.flickr.com/photos/factoryjoe/tags/loginform
</a> and<br><a href="http://www.flickr.com/photos/factoryjoe/tags/openid">http://www.flickr.com/photos/factoryjoe/tags/openid</a>), alternative user<br>experiences and conceptual work to define the user-side experience of
<br>OpenID in all its potential, glorious forms.<br><br>I would also suggest that CardSpace as it exists today is a<br>Microsoft-developed solution -- and hasn't been kissed by the scrutiny<br>of the open source community.
</blockquote><div><br>The folks working on Higgins, Bandit and OSIS are working on actually building Open Source implementations of CardSpace. </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I would also suggest it is now up to us<br>to effectively reverse engineer, document and dissect the research and<br>thinking behind CardSpace -- and put it into a form that regular<br>OpenID implementors can digest and make use of (I've never been able
<br>to stomach the M$ docs system).<br><br>So, though they are blessed with billions to push into R&D, I would<br>conclude that this is simply one large contribution from an important<br>community member; we haven't committed anything -- and as the
<br>foundation charter should set out, you gain your seat at the table<br>based on merit, not on the size of your budget.<br><br>Chris<br><br>On 2/6/07, Johannes Ernst <<a href="mailto:jernst+openid.net@netmesh.us">jernst+openid.net@netmesh.us
</a>> wrote:<br>> So now that CardSpace (and its eventual equivalent on non-Windows<br>> platforms) is part of the OpenID picture, what does this do to the<br>> user-experience work on this list?<br>><br>> We could ...
<br>> 1. ignore it<br>> 2. say that usernames/passwords aren't a problem any more because<br>> CardSpace solves that for us at OPs,<br>> 3. broaden the use cases considered to allow OP authentication either
<br>> a. via username/password (traditional)<br>> b. via CardSpace<br>> c. via another OpenID authentication process.<br>><br>> Of course, I favor #3 or some variation on it. What does everybody
<br>> else think?<br>><br>> Cheers,<br>><br>><br>> Johannes.<br>><br>><br>><br>> Johannes Ernst<br>> NetMesh Inc.<br>><br>><br>><br>> <a href="http://netmesh.info/jernst">http://netmesh.info/jernst
</a><br>><br>><br>> _______________________________________________<br>> user-experience mailing list<br>> <a href="mailto:user-experience@openid.net">user-experience@openid.net</a><br>> <a href="http://openid.net/mailman/listinfo/user-experience">
http://openid.net/mailman/listinfo/user-experience</a><br>><br>><br>><br><br><br>--<br>Chris Messina<br>Citizen Provocateur &<br> Open Source Ambassador-at-Large<br>Work: <a href="http://citizenagency.com">http://citizenagency.com
</a><br>Blog: <a href="http://factoryjoe.com/blog">http://factoryjoe.com/blog</a><br>Cell: 412 225-1051<br>Skype: factoryjoe<br>This email is: [ ] bloggable [X] ask first [ ] private<br>_______________________________________________
<br>user-experience mailing list<br><a href="mailto:user-experience@openid.net">user-experience@openid.net</a><br><a href="http://openid.net/mailman/listinfo/user-experience">http://openid.net/mailman/listinfo/user-experience
</a><br></blockquote></div><br>