Re: REVISED Web Page Proposal - Version 2.0

On Thu, Nov 02, 2006 at 10:59:30PM +0100, Johannes Koch wrote:
 
> An HTTP response may vary e.g. with specific Accept* request headers, 
> authentication credentials (Authorization request header), cookies (Cookie or 
> Cookie2 request header), or the request message body (like parameters from an 
> HTML form with method="post"). Even CCPP-based protocols like UAProf can be 
> used to create a response adapted to the user agent's capabilities or user's 
> preferences.

Yes, and of course we don't want to limit ourselves to HTTP either.

Maybe the rule should be this:

Where two or more primary resources (together with any subsidiary resources
that may be rendered simultaneously with them) are obtainable from the same
URI, we partition the set of all such resources into equivalence classes. Two
resources are equivalent if they convey the same information or provide the
same functionality, concepts which are already employed elsewhere in the
guidelines.

The conformance requirement, then, is that at least one member of each
equivalence class must satisfy all success criteria at the specified
conformance level.

My purpose here is not to express the idea in the most elegant way possible,
as would need to be done if the proposal were developed further, but simply to
propose a potential solution to the problem at hand.

Received on Friday, 3 November 2006 01:16:48 UTC