• ExampleXrds
• EqualRegistry

Example XRDS File for the = Registry

1. Introduction

This page displays an example XRDS file that might be returned from the = registry as the resolution result for xri://=example.person.

2. XRDS File

<?xml version="1.0" encoding="UTF-8"?>
<XRDS ref="xri://=example.person">
    <XRD xmlns="xri://$xrd*($v*2.0)">
        <Query>*example.person</Query>
        <Status code="100"/>
        <Expires>2006-05-26T06:05:23.000Z</Expires>
        <ProviderID>xri://=</ProviderID>
        <CanonicalID>xri://=!1000.4dc2.89c0.a918</CanonicalID>
        <LocalID>!1000.4dc2.89c0.a918</LocalID>
        <Service>
            <Type>xri://$res*auth*($v*2.0)</Type>
            <ProviderID>xri://!!1003</ProviderID>
            <MediaType>application/xrds+xml</MediaType>
            <MediaType>application/xrds+xml;trust=https</MediaType>
            <URI>http://xri.example.com/=!1000.4dc2.89c0.a918/</URI>
            <URI>https://xri.example.com/=!1000.4dc2.89c0.a918/</URI>
        </Service>
        <Service>
            <ProviderID>xri://!!1000</ProviderID>
            <Type select="true">xri://+i-service*(+authn)*(+saml)*($v*1.0)</Type>
            <Path select="true">(+login)</Path>
            <URI append="qxri">http://authn.example.com/(+authn)*(+saml)*($v*1.0)/(=!1000.4dc2.89c0.a918)?xri=</URI>
            <URI append="qxri">https://authn.example.com/(+authn)*(+saml)*($v*1.0)/(=!1000.4dc2.89c0.a918)?xri=</URI>
        </Service>
        <Service priority="1">
            <ProviderID>xri://!!1000</ProviderID>
            <Type select="true">http://openid.net/signon/1.0</Type>
            <URI priority="1">https://openid.example.com/login</URI>
            <URI priority="2">http://openid.example.com/login</URI>
        </Service>
        <Service>
            <ProviderID>xri://!!1000!1234</ProviderID>
            <Type select="true">xri://+i-service*(+contact)*($v*1.0)</Type>
            <Type match="default"/>
            <MediaType>text/html</MediaType>
            <MediaType match="default"/>
            <Path select="true">(+contact)</Path>
            <Path match="null"/>
            <URI append="qxri">http://contact.example.com/(+contact)*($v*1.0)/(=!1000.4dc2.89c0.a918)?xri=</URI>
            <URI append="qxri">https://contact.example.com/(+contact)*($v*1.0)/(=!1000.4dc2.89c0.a918)?xri=</URI>
        </Service>
        <Service>
            <ProviderID>xri://!!1000</ProviderID>
            <Type select="true">xri://+i-service*(+forwarding)*($v*1.0)</Type>
            <Type match="null"/>
            <URI append="qxri">http://forwarding.example.com/(+forwarding)*($v*1.0)/(=!1000.4dc2.89c0.a918)/</URI>
            <URI append="qxri">https://forwarding.example.com/(+forwarding)*($v*1.0)/(=!1000.4dc2.89c0.a918)/</URI>
        </Service>
    </XRD>
</XRDS>

3. Notes

1. The first service endpoint is for an XRI authority resolution service for =example.name. This is the service endpoint that would resolve a community i-name assigned by the owner of =example.name, for example, =example.name*daughter. The values for this service endpoint element are specified by the XRI Resolution specification -- see [http://www.oasis-open.org/committees/xri/ OASIS XRI TC home page] for the current version.

2. Note that there is no service endpoint for SAML metadata as that service is only required for i-brokers or others sending or receiving SAML authentication requests.

3. The third service endpoint is for [http://www.openid.net OpenID] authentication.

4. The final service endpoints are for the three standard non-i-broker i-service endpoints defined by IserviceEndpointDefinitions.

5. Note that the contents of the URI elements shown above are only examples of what an i-broker might use. There are no absolute requirements for the contents of this element other than it must be a valid URI, IRI, or XRI. Also note that the effective URI that will be constructed depends on the value of the append attribute.