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.<div><URITemplate><a href="http://example.com/getxrd?q={uri}">http://example.com/getxrd?q={uri}</a><URITemplate></div>
<div><br></div><div>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. </div>
<div><br></div><div><link rel="<a href="http://ietf.org/service/resolve/xrd">http://ietf.org/service/resolve/xrd</a>"</div><div> type="application/xrd+xml"</div><div> href="<a href="http://example.com/getxrd">http://example.com/getxrd</a>"/></div>
<div><br></div><div>(the rel value is just an example)<br clear="all"><br></div><div>Advantages of this being</div><div>1) No need for template and template mapping</div><div>2) The idea is consistent with the host-meta being an aggregator of the XRD's available on the host.</div>
<div><br></div><div>Any reason this could be a bad idea?</div><div><br>-- <br><a href="http://hi.im/santosh">http://hi.im/santosh</a><br><br><br>
</div>