<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
My use case is here:
<a class="moz-txt-link-freetext" href="https://docs.google.com/a/google.com/Doc?docid=dc43mmng_2g6k9qzfb&hl=en">https://docs.google.com/a/google.com/Doc?docid=dc43mmng_2g6k9qzfb&hl=en</a><br>
<br>
<blockquote>
<h2 id="a-vh"> 5. Discovery
</h2>
A container declares what collection and features it supports, and
provides templates for discovering them, via a simple discovery
document. A client starts the discovery process at the container's
identifier URI (e.g., example.org). The full flow is available at
<a class="moz-txt-link-freetext" href="http://xrds-simple.net/core/1.0/">http://xrds-simple.net/core/1.0/</a>; in a nutshell:<br id="zl_a0">
<ol id="r6620">
<li id="r6621"> Client GETs {container-url} with Accept:
application/xrds+xml </li>
<li id="r6621"> Container responds with either an X-XRDS-Location:
header pointing to the discovery document, or the document itself. </li>
<li id="r6621"> If the client received an X-XRDS-Location: header,
follow it to get the discovery document. </li>
</ol>
<br id="u::e0">
The discovery document is an XML file in the same format used for
OpenID and OAuth discovery, defined at
<a class="moz-txt-link-freetext" href="http://xrds-simple.net/core/1.0/:">http://xrds-simple.net/core/1.0/:</a>
<blockquote id="ev1b0">
<pre id="by:f0"><XRDS xmlns="xri://$xrds">
<XRD xmlns:simple=<a class="moz-txt-link-rfc2396E" href="http://xrds-simple.net/core/1.0">"http://xrds-simple.net/core/1.0"</a> xmlns="xri://$XRD*($v*2.0)" xmlns:os=<a class="moz-txt-link-rfc2396E" href="http://ns.opensocial.org/">"http://ns.opensocial.org/"</a> version="2.0">
<Type>xri://$xrds*simple</Type>
<Service>
<Type><a class="moz-txt-link-freetext" href="http://ns.opensocial.org/people/0.8">http://ns.opensocial.org/people/0.8</a></Type>
<os:URI-Template><a class="moz-txt-link-freetext" href="http://api.example.org/people/">http://api.example.org/people/</a>{guid}/{selector}{-prefix|/|pid}</URI-Template>
</Service>
<Service>
<Type><a class="moz-txt-link-freetext" href="http://ns.opensocial.org/activities/0.8">http://ns.opensocial.org/activities/0.8</a></Type>
<os:URI-Template><a class="moz-txt-link-freetext" href="http://api.example.org/activities/">http://api.example.org/activities/</a>{guid}/{selector}</URI-Template>
</Service>
<Service>
<Type><a class="moz-txt-link-freetext" href="http://ns.opensocial.org/appdata/0.8">http://ns.opensocial.org/appdata/0.8</a></Type>
<os:URI-Template><a class="moz-txt-link-freetext" href="http://api.example.org/appdata/">http://api.example.org/appdata/</a>{guid}/{selector}</URI-Template>
</Service>
</XRD>
</XRDS></pre>
</blockquote>
<br id="kogv1">
Each Service advertises a service provided
by the container. Each container MUST support the service Types
documented below and MAY support others by advertising them in the
discovery document. Each service comprises a set of resources defined
by the given URI Template (or URI, if there is only a single
resource). Clients follow the URIs and instantiate the templates to
find and operate on specific resources. (URI Template syntax is
documented at
<a class="moz-txt-link-freetext" href="http://www.ietf.org/internet-drafts/draft-gregorio-uritemplate-03.txt">http://www.ietf.org/internet-drafts/draft-gregorio-uritemplate-03.txt</a>.)<br
id="soad0">
<br id="soad1">
The set of substitution variables is fixed for each service Type. The
core set of service Types and their substitution variables is
documented below. Extensions to OpenSocial SHOULD document their
substitution variables; note that a reasonable place to put human
readable documentation is at the namespace URI.</blockquote>
<br>
Andrew Arnott wrote:
<blockquote
cite="mid:216e54900805250934g77423329k3195c1ec798f4e90@mail.gmail.com"
type="cite">Forwarding to rest of the list.<br>
<br>
<div class="gmail_quote">---------- Forwarded message ----------<br>
From: <b class="gmail_sendername">Andrew Arnott</b> <<a
moz-do-not-send="true" href="mailto:andrewarnott@gmail.com">andrewarnott@gmail.com</a>><br>
Date: Sun, May 25, 2008 at 9:34 AM<br>
Subject: Re: [OpenID] XRDS RP discovery when dynamic pages allow logins?<br>
To: John <<a moz-do-not-send="true" href="mailto:jpanzer@acm.org">jpanzer@acm.org</a>><br>
<br>
<br>
Thanks, John.<br>
<br>
Can you (or anyone else) give or point to a simple example of an XRDS
document using this? And what does "Needs an extension" mean? That
it's not done as a spec in solving my problem, or that I need to
reference some extension namespace when I do this?<br>
<br>
Thanks again.
<div>
<div class="Wj3C7c"><br>
<br>
<div class="gmail_quote">On Sun, May 25, 2008 at 9:06 AM, John <<a
moz-do-not-send="true" href="mailto:jpanzer@acm.org" target="_blank">jpanzer@acm.org</a>>
wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Suggestion:
use uri templates (URI-Template element instead of URI). Needs an
extension.<br>
<br>
-John
<div><br>
<br>
On May 25, 2008, at 7:33 AM, "Andrew Arnott" <<a
moz-do-not-send="true" href="mailto:andrewarnott@gmail.com"
target="_blank">andrewarnott@gmail.com</a>> wrote:<br>
<br>
</div>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>According to the OpenID 2.0 spec (as I read it), the RP
discovery feature requires that the return_to URL be found in the XRDS
doc published by the RP at the realm URL. However, some sites, such as
blogs, allow logging in on virtually every page on the site
(thousands). How should this be handled in the XRDS document since it
can't be practical to include thousands of potential return_to URLs in
the XRDS doc?<br>
<br>
-- <br>
Andrew Arnott<br>
</div>
_______________________________________________<br>
general mailing list<br>
<a moz-do-not-send="true" href="mailto:general@openid.net"
target="_blank">general@openid.net</a><br>
<a moz-do-not-send="true"
href="http://openid.net/mailman/listinfo/general" target="_blank">http://openid.net/mailman/listinfo/general</a><br>
</blockquote>
</blockquote>
</div>
<br>
<br clear="all">
<br>
</div>
</div>
-- <br>
<font color="#888888">Andrew Arnott
</font></div>
<br>
<br clear="all">
<br>
-- <br>
Andrew Arnott
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
general mailing list
<a class="moz-txt-link-abbreviated" href="mailto:general@openid.net">general@openid.net</a>
<a class="moz-txt-link-freetext" href="http://openid.net/mailman/listinfo/general">http://openid.net/mailman/listinfo/general</a>
</pre>
</blockquote>
<br>
</body>
</html>