YADIS as an abstraction layer

[Benjamin Yu]

Excellent.

I also want to emphasize what was implied by Martin's email.

Capabilities are returned in document form, not in the HTTP Headers.

I want to push for NOT returning capabilities in the HTTP headers. My main
argument for this is REST's rule of:

"self-descriptive messages; and, hypermedia as the engine of application
state."

The returned document is the resource's representation, not the headers.

-Ben

--- Martin Atkins <mart at degeneration.co.uk> wrote:
> I've made the following changes to YADIS as currently specced:
> * The capability document is (can be) just a static document on your
> website.
> * The endpoints for the declared services are configurable rather than
> assumed to be the same as the capability document.
> * The trick of requesting with ?meta=identity to as a hint to provide a
> capability document has been replaced with the use of the HTTP Accept
> header, which is less likely to conflict with existing applications at
> the identity URL and can be implemented using the content negotiation
> capabilities in Apache. The indirection through HTML is still provided
> for those who are unable to switch based on the Accept header.
> * The delegation functionality, which is pretty specific to OpenID
> anyway, is now in the capability file rather than in the HTML document.
> YADIS is acting as a delegation layer anyway, so there's no need for
> this as a core feature.
> * I'm ignoring all of the profile exchange stuff, since I don't think
> that has any place in YADIS. It is just another capability.
> 
> ---------------------------------------
> 
> How does that grab you all?
>