<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 18-Dec-08, at 10:27 AM, Brian Kissel wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0; "><div lang="EN-US" link="blue" vlink="purple" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div class="Section1"><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">I don’t know how much more clear I can be. I’m NOT advocating for RPX, I’m advocating for a better UX on the OIDF website. Rip out RPX today, that’s fine. Ask the community how we can improve OpenID login on the OIDF website, then get volunteers to implement it or pay Refresh or anyone else to implement it. But let’s make the OIDF website a showcase of the goodness of OpenID for users and RPs. Like it or not, the OIDF website is a showcase for the broader market, not just a tool for OIDF members. If we can improve UX and maintain neutrality, great. But let’s not sacrifice UX for neutrality if we know that the existing neutral UX is NOT intuitive. Would love to see some ideas on what we could be doing to improve intuitiveness rather than just saying a text box is neutral, so let’s just take the easy path and go that way.<o:p></o:p></span></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); "><o:p> </o:p></span></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">Would like to hear from some others on how we can improve intuitiveness and whether it’s important, not only on our website, but as a fundamental goal for the OIDF.</span></div></div></div></span></blockquote><br></div><div>That is more clear -- although your other comments indicate you are justifying why it is ok to use RPX.</div><div><br></div><div>OpenID UX is an issue. I do NOT think the OIDF website is the place to experiment, particularly during an election process.</div><div><br></div><div>This is a technical issue -- and the OIDF is there to facilitate resolving the problem -- the Foundation bylaws explicitly forbid the Foundation from directly resolving technical issues.</div><div><br></div><div>There is pretty active discussion on UX issues on the lists now. I think people are looking at how to solve it -- and there is NO clear solution that has gained consensus.</div><div><br></div><div>I think we are WAY off topic on this thread now.</div><div><br></div><div>-- Dick</div><br></body></html>