<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:m="http://schemas.microsoft.com/office/2004/12/omml" 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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
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;}
span.apple-style-span
{mso-style-name:apple-style-span;}
span.apple-tab-span
{mso-style-name:apple-tab-span;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle20
{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 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>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>That was very useful. Thanks. Its puts a wholly new perspective
on XDI. Sparql-like - with the HXRI security model, a resolver query model,
and signed tokens that link the set of XRDs in the closure set.<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'>Ignore my previous jibberish. It was attempting to make sense of
an old document that was almost imprehensible, and apply it to openid discovery.
Basically, I just want the XRDS that comes back to have a Service element that
has a list of blog site synonyms (in addition to OP endpoints, delegations etc).
Viewing that synonym list as an ordered list, I wanted my consumer to check
that the set of 30x redirects my consumer had just gone through (to get to the
XRDS) was “consistent” with the order of the synonym list in the
XRDS.<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'>It’s not clear that the XDI forwarding service would even
preserve the original order of the synonyms, however.<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"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
general-bounces@openid.net [mailto:general-bounces@openid.net] <b>On Behalf Of </b>John
Bradley<br>
<b>Sent:</b> Monday, December 29, 2008 10:52 AM<br>
<b>To:</b> general@openid.net<br>
<b>Subject:</b> Re: [OpenID] general Digest, Vol 28, Issue 204<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Peter,<o:p></o:p></p>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>XDI is a RDF data service that uses XRI for addressing data.
Think SPARQL with security.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>XRI proxy servers will select a sep for
backwards compatibility with existing browsers and give you a 302
redirect to the URI element of the SEP. This is based on standard XRI
service selection criteria.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>We will be changing the 302 to a 303 in the next version of
the spec to make it more AWWW friendly.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>You may want to look at my XRDS =jbradley for some creative
things using content negotiation and HXRI proxys.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>It is possible to run your own XRI authority server to serve
the XRDS documents as a community registry.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>In the next version of XRI we intend to make it easier for
people to run there own XRI registries using a URI cross ref for the first
subsegment.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>iBrokers currently offer a service called a forwarding
service. This is separate from using the XRDS to do the forwarding.
The forwarding service is normally configured as the default service for
queries with a path component.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>The HXRI proxy uses URI construction to create a new URI
that is passed to the forwarding service. The forwarding service
then performs a redirect. The forwarding service itself is not
a part of XRI, rather it is a value add provided by iBrokers.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>None of this redirection applies to openID
discovery directly. <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>Currently the URI rewriting rules are quite simple like
appending the Query XRI etc.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>The TC is looking at expanding URI construction rules in the
new XRD spec. <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>I am not quite certain what you are trying to achieve,
but I suspect that XRI is probably not the best thing to use as a
URI rewriting and forwarding service. That really was only
intended as a backwards compatibility feature for existing web browsers.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>Feel free to email me directly.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>Regards<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>=jbradley<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<div>
<div>
<p class=MsoNormal>On 29-Dec-08, at 3:11 PM, <a
href="mailto:general-request@openid.net">general-request@openid.net</a> wrote:<o:p></o:p></p>
</div>
<p class=MsoNormal><br>
<br>
<o:p></o:p></p>
<p class=MsoNormal><span class=apple-style-span><span style='font-size:9.0pt;
font-family:"Helvetica","sans-serif";color:black'>Message: 1</span></span><span
style='font-size:9.0pt;font-family:"Helvetica","sans-serif";color:black'><br>
<span class=apple-style-span>Date: Mon, 29 Dec 2008 09:31:48 -0800</span><br>
<span class=apple-style-span>From: Peter Williams <<a
href="mailto:pwilliams@rapattoni.com">pwilliams@rapattoni.com</a>></span><br>
<span class=apple-style-span>Subject: Re: [OpenID] XDI cross-references</span><br>
<span class=apple-style-span>To: "<a href="mailto:general@openid.net">general@openid.net</a>"
<<a href="mailto:general@openid.net">general@openid.net</a>></span><br>
<span class=apple-style-span>Message-ID:</span><br>
<span class=apple-tab-span> </span><span
class=apple-style-span><<a
href="mailto:BFBC0F17A99938458360C863B716FE463981A70320@simmbox01.rapnt.com">BFBC0F17A99938458360C863B716FE463981A70320@simmbox01.rapnt.com</a>></span><br>
<span class=apple-style-span>Content-Type: text/plain; charset="us-ascii"</span><br>
<br>
<span class=apple-style-span>Concerning line ~219</span><span
class=apple-converted-space> </span><span class=apple-style-span><a
href="http://iss.xdi.org/moin.cgi/ForwardingService?action=AttachFile&do=get&target=iss-forwarding-v1.0-wd-03.pdf">http://iss.xdi.org/moin.cgi/ForwardingService?action=AttachFile&do=get&target=iss-forwarding-v1.0-wd-03.pdf</a></span><br>
<br>
<br>
<span class=apple-style-span>Is there anywhere I can use an XDI-like
service...to try out its integration with actual openid discovery clients
(pbwiki, plaxo, blogspot, etc)?</span><br>
<br>
<br>
<span class=apple-style-span>Am I right to think that the scheme is saying that
if I type in an HXRI invoking the forwarding service, a 3xx https response may
come back - whose URL form _can_ be another HXRI ...calling upon another
XDI-like forwarding network? That pattern of double discovery may be viable for
realty: use an i-broker governed forwarding service to locate a private
forwarding service that is not governed by i-broker vendor associations.
Some Realty MLSs would run their own XRI forwarding service, and others would
want to use the private-label services of Neustar, etc.</span><br>
<br>
<span class=apple-style-span>Ok less theory, more practice! We have a need to
let query-based openid discovery agents use their rule-rewriting expressions to
produce a websso-switch invocation URL of the form:</span><br>
<br>
<br>
<span class=apple-style-span><a
href="http://swmrsso.rapmlsstg.com/sp/startSSO.ping?PartnerIdpId=rapattoni:mlsstgswmichigan:entityId">http://swmrsso.rapmlsstg.com/sp/startSSO.ping?PartnerIdpId=rapattoni:mlsstgswmichigan:entityId</a></span><br>
<br>
<br>
<br>
<span class=apple-style-span>If I was to use i-names as the entity name for the
openid entity in PartnerIdpId (=example/seattle/sightseeing), I can see the
forwarding service producing for me, given the input</span><span
class=apple-converted-space> </span><span class=apple-style-span><a
href="https://xri.net/=example.personal.nickname/(+forwarding)">https://xri.net/=example.personal.nickname/(+forwarding)</a></span><br>
<br>
<br>
<br>
<span class=apple-style-span><a
href="http://swmrsso.rapmlsstg.com/sp/startSSO.ping?PartnerIdpId=%3dexample%2fseattle%2fsightseeing">http://swmrsso.rapmlsstg.com/sp/startSSO.ping?PartnerIdpId=%3dexample%2fseattle%2fsightseeing</a></span><br>
<br>
<br>
<br>
<span class=apple-style-span>is there an example forwarding service that is really
capable of this (including the url encoding)?</span><br>
<br>
<span class=apple-style-span>(No...I cannot change the required form of the
target URL, its set by the websso-switch vendor).</span><br>
<br>
<br>
<br>
</span><o:p></o:p></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>