<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:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" 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:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" 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:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" 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=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@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:12.0pt;
font-family:"Times New Roman","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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle19
{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='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>George,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>You’re right that there are two things. The question
is, do we wish to allow only OP advertisement via the host meta-data XRD
file? That would certainly work for me. But, would users prefer to
have a single email address (e.g., <a href="mailto:user@gmail.com">user@gmail.com</a>)
and still be able to associate that with a different OP through webfinger?<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>People could always have a different acct: URI. Is that
preferred over trying to support both host meta-data and user meta-data XRD
documents? <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Paul<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'>
<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'> George Fletcher
[mailto:gffletch@aol.com] <br>
<b>Sent:</b> Wednesday, January 27, 2010 3:11 PM<br>
<b>To:</b> Paul E. Jones<br>
<b>Cc:</b> 'Allen Tom'; arshad.khan@channel321.com; specs@openid.net<br>
<b>Subject:</b> Re: Email Address to URL Transformation<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-family:"Helvetica","sans-serif"'>I think
there are two different things being described... (1) meta data about the host
(host-meta) and (2) meta data about the acct: identifier (XRD returned from the
webfinger template URI endpoint).<br>
<br>
In this thread, that host-meta XRD only describes one service of the host...
webfinger. However, there is nothing stopping the host from also adding a
<Link> specifying that it is also an OpenID Provider. I agree with Allen
that this is valuable information. This doesn't preclude or supersede the XRD
returned for the user (based on the template URI endpoint).<br>
<br>
So, if an RP is looking to find the user's OP, then follow the webfinger
protocol. If the RP just wants to know if a domain supports OpenID it can just look
in the host-meta for that domain.<br>
<br>
I don't think they conflict.<br>
<br>
Thanks,<br>
George<br>
</span><br>
On 1/25/10 3:52 PM, Paul E. Jones wrote: <o:p></o:p></p>
<pre>Allen,<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Perhaps we're in agreement, but I wasn't clear.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>I think OpenID RPs should be able to use XRD documents in order to discover<o:p></o:p></pre><pre>the user's login service -- I like this. What I would *not* want is for<o:p></o:p></pre><pre>that to be defined in this document:<o:p></o:p></pre><pre><a
href="http://yahoo.com/.well-known/host-meta">http://yahoo.com/.well-known/host-meta</a><o:p></o:p></pre><pre><o:p> </o:p></pre><pre>The reason is that this document is not user-specific and blankets<o:p></o:p></pre><pre>everything under the yahoo.com domain.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Rather, I'd want that to be in this document:<o:p></o:p></pre><pre><a
href="http://webfinger.yahooapis.com/?id=">http://webfinger.yahooapis.com/?id=</a>{%id}<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Or other document that allows the user to provide details about himself.<o:p></o:p></pre><pre>So, if I enter <a
href="mailto:paulej@yahoo.com">paulej@yahoo.com</a>, RPs would still be directed to<o:p></o:p></pre><pre><a
href="http://openid.packetizer.com/paulej">http://openid.packetizer.com/paulej</a> by querying the above document (or other<o:p></o:p></pre><pre>document) and finding some pointer to my OP.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Paul<o:p></o:p></pre><pre><o:p> </o:p></pre><pre> <o:p></o:p></pre>
<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>-----Original Message-----<o:p></o:p></pre><pre>From: Allen Tom [<a
href="mailto:atom@yahoo-inc.com">mailto:atom@yahoo-inc.com</a>]<o:p></o:p></pre><pre>Sent: Monday, January 25, 2010 1:45 PM<o:p></o:p></pre><pre>To: Paul E. Jones<o:p></o:p></pre><pre>Cc: <a
href="mailto:arshad.khan@channel321.com">arshad.khan@channel321.com</a>; <a
href="mailto:specs@openid.net">specs@openid.net</a>; 'John Panzer'<o:p></o:p></pre><pre>Subject: Re: Email Address to URL Transformation<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Hi Paul -<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>This assumes that every user with a Gmail or Yahoo email account can<o:p></o:p></pre><pre>use<o:p></o:p></pre><pre>their account as an OpenID. Simply asking the user to enter their email<o:p></o:p></pre><pre>address to kickoff the sign-in process is a lot more scalable than the<o:p></o:p></pre><pre>NASCAR, and is probably a lot more usable then asking them to enter<o:p></o:p></pre><pre>their<o:p></o:p></pre><pre>OpenID URL.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Allen<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>On 1/24/10 7:12 PM, "Paul E. Jones" <a
href="mailto:paulej@packetizer.com"><paulej@packetizer.com></a> wrote:<o:p></o:p></pre><pre><o:p> </o:p></pre><pre> <o:p></o:p></pre>
<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre><o:p> </o:p></pre><pre>But, wouldn't that assume that every user who has a gmail.com or<o:p></o:p></pre><pre> <o:p></o:p></pre></blockquote>
<pre>yahoo.com<o:p></o:p></pre><pre> <o:p></o:p></pre>
<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>email address uses Google or Yahoo, respectively, for OpenID?<o:p></o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre> <o:p></o:p></pre></blockquote>
<pre><o:p> </o:p></pre><pre> <o:p></o:p></pre></blockquote>
<pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre>_______________________________________________<o:p></o:p></pre><pre>specs mailing list<o:p></o:p></pre><pre><a
href="mailto:specs@lists.openid.net">specs@lists.openid.net</a><o:p></o:p></pre><pre><a
href="http://lists.openid.net/mailman/listinfo/openid-specs">http://lists.openid.net/mailman/listinfo/openid-specs</a><o:p></o:p></pre><pre><o:p> </o:p></pre><pre> <o:p></o:p></pre></div>
</div>
</body>
</html>