<HTML dir=ltr><HEAD></HEAD>
<BODY>
<DIV id=idOWAReplyText85862 dir=ltr>
<DIV dir=ltr><FONT face=Arial size=2>Tom,</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV></DIV>
<DIV dir=ltr>
<DIV dir=ltr><FONT face=Arial size=2>
<DIV dir=ltr><FONT face=Arial size=2>Good luck on the counter blog campaign. I think you are targeting the opinions of the commentators, which makes it even harder to counter of course. Some possible talking points follow:-</FONT></DIV>
<DIV dir=ltr> </DIV>
<DIV dir=ltr> </DIV>OpenID initially marketed itself on UCI - the portability feature, that is. This is what got me hooked!</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>If OpenID is mostly actually about being in the business of "outsourced identity management' for partially closed communitys, then fine. The business of operating hub/spoke bureaus is well understood. Its just another private-lavel or extranet deployment model.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>If OpenID is about how the public and private issues intersect, then again its very interesting.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Im going to hazard a guess that its this "management model component" of the openess issue which is really under scrutiny, not which software set one may be using.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>The question wall street analysts will surely be having now will be concerning the state of the development of the new outsourcing id management market for both public and private communiteis - who is funding it, who is investing what amounts, who is endorsing ...not which bits lie on the wire or which software set makes them. Once a technology like OpenID has reached this point through the efforts of the investment Angels, the Evangelists and the early Adopters, there will surely be an explosion of implementations ...which will settle down to a couple of best "open source" references implementations, over a year or two. Topics like XRI resolution look tricky and quirky, so you will quickly see a fallout, especially if the mainstream outsourcers get to do their usual trick - and deliberately tweak each deployment per closed community - so each has different properties that only proprietary operational knowledge sets can address, at commercial grade. US Healthcare, US Insurance and even US realty outsourcing all suffer from these "closed" market dynamics - that transcend software.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>---------- </FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Speaking of actual openness, its time to start testing use of sreg for names written out in Hindi , particularly when locating land and other real property that only has local descriptions in the local language/script - being without formal street address in village life.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Lets see if the URI -> IRI -> XRI model works in practice for OpenIDs, as billed.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr>
<HR tabIndex=-1>
</DIV>
<DIV dir=ltr><FONT face=Tahoma size=2><B>From:</B> tom calthrop<BR><B>Sent:</B> Thu 3/27/2008 11:59 AM<BR><B>To:</B> Peter Williams<BR><B>Cc:</B> OpenID List<BR><B>Subject:</B> Re: [OpenID] Putting the "open" back into OpenID - a call to the FSOSS community<BR></FONT><BR></DIV></DIV>
<DIV><PRE style="WORD-WRAP: break-word">Hi Peter,
With all due respect Peter I think you completely missed my point. The
"fight" is with people commenting on blogs who question the "open" in
->Open<-ID and my point is that it is the FSOSS community that are best
placed to give a balanced argument as to why it is open and why FSOSS is
embracing OpenID.
</PRE></DIV></BODY></HTML>