<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:D="DAV:" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=utf-8">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:Consolas;
        panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif";
        color:black;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
        {mso-style-priority:99;
        mso-style-link:"Plain Text Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:10.5pt;
        font-family:Consolas;
        color:black;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
        {mso-style-priority:99;
        mso-style-link:"Balloon Text Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:8.0pt;
        font-family:"Tahoma","sans-serif";
        color:black;}
span.PlainTextChar
        {mso-style-name:"Plain Text Char";
        mso-style-priority:99;
        mso-style-link:"Plain Text";
        font-family:Consolas;}
span.BalloonTextChar
        {mso-style-name:"Balloon Text Char";
        mso-style-priority:99;
        mso-style-link:"Balloon Text";
        font-family:"Tahoma","sans-serif";}
span.EmailStyle21
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page Section1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
        {page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor=white lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='color:#1F497D'>I’m not insisting on anything.
What I am questioning is whether we can find a way, any way, to make the UX on
OIDF more intuitive. If Google, Yahoo, AOL, Verisign, Vidoop, or the OIDF
membership community can come up with a more intuitive way to log into our
website, I think that’s a win and we should consider those options. For those
who haven’t talked to hundreds of mainstream RPs (not blogging sites with tech savvy
users), typing in a URL is not intuitive for the masses. Maybe someday it will
be, but today it isn’t – period. So it’s all well and good to be “neutral” but
if we want to drive adoption and usage, we need to respond to what the market
wants, or at least offer them options that are more compelling than what they’ve
told us so far is clearly not.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>When we talked with the former
ED of the Bluetooth SIG, he gave an example about demonstrating Bluetooth for
press and analysts. The initial demos he gave were using a Toshiba laptop and
mouse because Toshiba was one of the founding members of the SIG. But the user
experience at that time was pretty bad with Toshiba, so it didn’t serve the
purpose of getting press and analysts excited about the reliability and ease of
use of Bluetooth. He then switched to doing demos with an Apple laptop and
mouse (even though Apple wasn’t yet a member of the SIG), and the demos were a
smashing success and resulted in much more favorable press and analysts
coverage.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>All I’m saying is that we can’t
be dogmatic, we need to think about what our mission is, then make sure we’ve
evaluated the best ways to achieve our mission. If we can drive adoption and
usage equally well with a “neutral” approach to everything we do on our
website, with press & analysts, etc. that’s great. But I think we’ll find
over time that we need to be pragmatic and make tradeoffs. We recently moved
our wiki to PB Wiki which is provided by a vendor, presumably because it gave
us the functionality we needed at a reasonable cost. We didn’t write our own
wiki software. Many of the committees are using Google docs for collaboration,
and that’s OK.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>We have a lot of creative
members of the OIDF, why don’t we ask them how to improve the UX of the OIDF
website login in a way that will be intuitive for the masses that we ultimately
hope to serve? If we’re going to spend $2K, I’d advocate spending it on
implementing that UX.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<div>
<p class=MsoNormal><span style='color:navy'>Cheers,</span><span
style='color:navy'><o:p></o:p></span></p>
<p class=MsoNormal><span style='color:navy'><br>
Brian<o:p></o:p></span></p>
<p class=MsoNormal><b><span style='color:navy'>==============<o:p></o:p></span></b></p>
<p class=MsoNormal><b><span style='color:navy'>Brian Kissel<o:p></o:p></span></b></p>
<p class=MsoNormal><b><span style='color:navy'>Cell: 503.866.4424<o:p></o:p></span></b></p>
<p class=MsoNormal><b><span style='color:navy'>Fax: 503.296.5502<o:p></o:p></span></b></p>
</div>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:windowtext'>From:</span></b><span style='font-size:10.0pt;font-family:
"Tahoma","sans-serif";color:windowtext'> board-bounces@openid.net
[mailto:board-bounces@openid.net] <b>On Behalf Of </b>Eddy Nigg (StartCom Ltd.)<br>
<b>Sent:</b> Thursday, December 18, 2008 9:15 AM<br>
<b>To:</b> board@openid.net<br>
<b>Subject:</b> Re: [OpenID board] BOARD VOTE: Motion to update Rails plugin
andOpenID.net ...<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>On 12/18/2008 06:59 PM, Brian Kissel: <o:p></o:p></p>
<p class=MsoPlainText>Agreed there is no consensus on the UX for OpenID
;-) Not sure there ever will be. And to be clear, I was not
requesting nor advocating paying anything to JanRain, only offering that we
could do that for free if requested. Seems like the simplest, quickest,
cheapest thing would be to have Refresh Media put the text box on the front of
RPX. If AOL were willing to modify their UX at MapQuest to include the
top X (10, 15, 20?) commercial OPs, would that be a better UX? <o:p></o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:12.0pt;
font-family:"Times New Roman","serif"'><br>
Nooooo! Why are you insisting on it? We want an OpenID <b>vendor neutral</b>
interface. I really don't understand, is this a promotional circus for
commercial providers or is this the OpenID Foundation? My provider would be
most likely within the top ten or twenty, this isn't the point, it's about what
a foundation is and represents.<br>
<br>
<o:p></o:p></span></p>
<div>
<table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0>
<tr>
<td colspan=2 style='padding:0in 0in 0in 0in'>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'>Regards <o:p></o:p></span></p>
</td>
</tr>
<tr>
<td colspan=2 style='padding:0in 0in 0in 0in'>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'> <o:p></o:p></span></p>
</td>
</tr>
<tr>
<td style='padding:0in 0in 0in 0in'>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'>Signer: <o:p></o:p></span></p>
</td>
<td style='padding:0in 0in 0in 0in'>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'>Eddy
Nigg, <a href="http://www.startcom.org">StartCom Ltd.</a><o:p></o:p></span></p>
</td>
</tr>
<tr>
<td style='padding:0in 0in 0in 0in'>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'>Jabber: <o:p></o:p></span></p>
</td>
<td style='padding:0in 0in 0in 0in'>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><a
href="xmpp:startcom@startcom.org">startcom@startcom.org</a><o:p></o:p></span></p>
</td>
</tr>
<tr>
<td style='padding:0in 0in 0in 0in'>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'>Blog: <o:p></o:p></span></p>
</td>
<td style='padding:0in 0in 0in 0in'>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><a
href="http://blog.startcom.org">Join the Revolution!</a><o:p></o:p></span></p>
</td>
</tr>
<tr>
<td style='padding:0in 0in 0in 0in'>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'>Phone: <o:p></o:p></span></p>
</td>
<td style='padding:0in 0in 0in 0in'>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'>+1.213.341.0390<o:p></o:p></span></p>
</td>
</tr>
<tr>
<td colspan=2 style='padding:0in 0in 0in 0in'>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'> <o:p></o:p></span></p>
</td>
</tr>
</table>
</div>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><br>
<br>
<br>
__________ Information from ESET NOD32 Antivirus, version of virus signature
database 3703 (20081218) __________<br>
<br>
The message was checked by ESET NOD32 Antivirus.<br>
<br>
<a href="http://www.eset.com">http://www.eset.com</a><o:p></o:p></span></p>
</div>
</body>
</html>