[OpenID] Is a URI Template really required for host-meta?

[Santosh Rajan]

One of the purposes of the host-meta is to map a given URI to its XRD
available on the server. Currently this is done by using a URITemplate.
<URITemplate>http://example.com/getxrd?q={uri}<URITemplate>

Instead can the host-meta define a resolver service on the host, that
returns an XRD given the Subject URI? eg. The host-meta can define a service
on the server that accepts a GET or POST request with a single parameter
passed whose key is "subject", and "value" is the subject URI to be
resolved. In this case we only need a URI to the service on the server and
can be written like this.

<link rel="http://ietf.org/service/resolve/xrd"
    type="application/xrd+xml"
    href="http://example.com/getxrd"/>

(the rel value is just an example)

Advantages of this being
1) No need for template and template mapping
2) The idea is consistent with the host-meta being an aggregator of the
XRD's available on the host.

Any reason this could be a bad idea?

-- 
http://hi.im/santosh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-general/attachments/20091114/015cf88e/attachment.htm>