proposal for capabilities lookup

Drummond Reed drummond.reed at
Mon Nov 21 00:47:23 PST 2005

One minor correction to Peter's message below: in the XRI Resolution 2.0
Working Draft 09 spec, the official media type for XRD files was updated to
"application/xrd+xml", however in subsequent review, Gabe Wachob, XRI TC
co-chair, noted that due to the new separation of XML namespaces in the
spec, it will actually be:


Working Draft 10, which will contain numerous corrections such as the above
as XRI TC members complete their reviews, is due by Dec. 1.


-----Original Message-----
From: yadis-bounces at [mailto:yadis-bounces at]
On Behalf Of Peter Davis
Sent: Friday, November 18, 2005 2:18 PM
To: Martin Atkins; yadis at
Subject: Re: proposal for capabilities lookup

> I think two goals are most important for adoption:
> * Those using their own site as an identity URL must be able to add
> YADIS support without writing any code or greatly disturbing their
> existing site. (The HTML indirection case.) This implies a regular GET,
> as you mentioned.
> * In *that same request* consumers must somehow indicate that it's
> really capabilities that they are interested in, so that larger identity
> hosts like LiveJournal can remove the layer of indirection and just
> return the capabilities directly, without having to generate a rather
> costly journal page that's just going to be discarded. This is the
> purpose I was bending "Accept" for.

For those unaware, in content negotiation (Accept), A userAgent can specify
_multiple_ representations in weighted order:

HTTP_ACCEPT: application/xrid+xml;q=0.9,text/html;q=0.8,text/plain;q=0.7

Which informs the server, that the user agent wourl prefer
application/xrid+xml (this is the 'official' XRID media type, though IANA
registration is pending until the resolution spec is final).

Not sure this sways anyones thinking, but it is not a oft-used capability


More information about the yadis mailing list