On Tue, Sep 22, 2009 at 4:49 PM, Breno de Medeiros <> wrote:
Sorry, but the Googlers finally got together to do some fine-print
reading of the XRI spec.
I will start several threads on separate topics. The subject of this
topic is "URITemplate"
Questions:
1. Do we need URITemplate support in XRD, or could this be a host-meta
extension?
To explain a little more where we're coming from here:
If I perform discovery on http://foo.com/bar, but for whatever reason first have to fetch foo.com's host-meta-XRD (perhaps because I'm following an LRDD-like discovery flow), then the following makes sense:
<Host>foo.com</Host>
<Link>
<Rel>describedby</Rel>
<URITemplate>http://foo.com/xrd?uri={%uri}</URITemplate>
</Link>
It means that the meta-data for http://foo.com/bar is available at http://foo.com/xrd?uri=http://foo.com/bar.
If, however, I am already looking at the XRD for a certain resource (like http://foo.com/bar), wouldn't we simply say:
<Subject>http://foo.com/bar</Subject>
<Link>
<Rel>describedby</Rel>
<URI>http://foo.com/xrd?uri=http://foo.com/bar<URI>
</Link>
?
What sense would it possibly make to have a URITemplate in such an XRD? What URI am I supposed to apply to such a URITemplate? It can't be http://foo.com/bar, because I'm already staring at the XRD for that resource, so there is no need to resolve it any further. Ar there other use cases (other than host-meta) that need URITemplate?
Dirk.
2. If we need URITemplate, do we need extensible vocabularies? (That
is what the spec calls for).
3. Do we need to specify the processing order for URI vs. URITemplate?
Presumably the discovery is for either the subject or some other
resource related to the subject, but not both. Should not this be a
client prerrogative?
--
--Breno
+1 (650) 214-1007 desk
+1 (408) 212-0135 (Grand Central)
MTV-41-3 : 383-A
PST (GMT-8) / PDT(GMT-7)
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
