<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Peter,<div><br></div><div>XDI is a RDF data service that uses XRI for addressing data. Think SPARQL with security.</div><div><br></div><div>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.</div><div><br></div><div>We will be changing the 302 to a 303 in the next version of the spec to make it more AWWW friendly.</div><div><br></div><div>You may want to look at my XRDS =jbradley for some creative things using content negotiation and HXRI proxys.</div><div><br></div><div>It is possible to run your own XRI authority server to serve the XRDS documents as a community registry.</div><div><br></div><div>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.</div><div><br></div><div>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.</div><div><br></div><div>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.</div><div><br></div><div>None of this redirection applies to openID discovery directly. </div><div><br></div><div>Currently the URI rewriting rules are quite simple like appending the Query XRI etc.</div><div><br></div><div>The TC is looking at expanding URI construction rules in the new XRD spec. </div><div><br></div><div>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.</div><div><br></div><div>Feel free to email me directly.</div><div><br></div><div>Regards</div><div>=jbradley</div><div><br></div><div><br></div><div><br></div><div><div><div>On 29-Dec-08, at 3:11 PM, <a href="mailto:general-request@openid.net">general-request@openid.net</a> 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; ">Message: 1<br>Date: Mon, 29 Dec 2008 09:31:48 -0800<br>From: Peter Williams <<a href="mailto:pwilliams@rapattoni.com">pwilliams@rapattoni.com</a>><br>Subject: Re: [OpenID] XDI cross-references<br>To: "<a href="mailto:general@openid.net">general@openid.net</a>" <<a href="mailto:general@openid.net">general@openid.net</a>><br>Message-ID:<br><span class="Apple-tab-span" style="white-space: pre; "> </span><<a href="mailto:BFBC0F17A99938458360C863B716FE463981A70320@simmbox01.rapnt.com">BFBC0F17A99938458360C863B716FE463981A70320@simmbox01.rapnt.com</a>><br>Content-Type: text/plain; charset="us-ascii"<br><br>Concerning line ~219<span class="Apple-converted-space"> </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><br><br><br>Is there anywhere I can use an XDI-like service...to try out its integration with actual openid discovery clients (pbwiki, plaxo, blogspot, etc)?<br><br><br>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.<br><br>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:<br><br><br><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><br><br><br><br>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 class="Apple-converted-space"> </span><a href="https://xri.net/=example.personal.nickname/(+forwarding)">https://xri.net/=example.personal.nickname/(+forwarding)</a><br><br><br><br><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><br><br><br><br>is there an example forwarding service that is really capable of this (including the url encoding)?<br><br>(No...I cannot change the required form of the target URL, its set by the websso-switch vendor).<br><br><br></span></blockquote></div><br></div></body></html>