Re: content negotiation for site-meta

[Eran Hammer-Lahav <eran@hueniverse.com>]

Title: Re: content negotiation for site-meta

I agree with your analysis. What makes me reconsider this is the lack of full overlap between /site-meta (text) and XRD. In my previous email you can see where I had to add another namespace to support <site-meta:scheme>. Since the text format will be required in any compliant implementation, maybe we should not support an XRD flavor of /site-meta.

EHL


On 12/15/08 12:18 PM, "Brian Eaton" <beaton@google.com> wrote:

> On Thu, Dec 11, 2008 at 11:40 PM, Eran Hammer-Lahav <eran@hueniverse.com> wrote:
> > At the /site-meta level, there will be a facility to describe URI mapping
> > via a URI template. /site-meta will have a canonical TEXT representation
> > (Mark will hopefully push it out soon) instead of the current XML. XRD will
> > define an XRD-based version of /site-meta so that a GET on /site-meta with
> > Accept: application/xrd+xml will produce an XRD version of the same content
> > (or just return the text format).
>
> I'm concerned that this approach will slow or stall deployment of
> site-meta because it relies on HTTP features that are not
> well-supported in current software.  There are three problematic parts
> of the architecture: the web servers, the intermediate caches, and the
> clients. =)
>
> I've done a bit of digging and written up my notes here:
> http://wiki.oasis-open.org/xri/XrdOne/ContentNegotiation
>
> Cheers,
> Brian