Comments on Architecture of the Web

http://www.w3.org/2001/tag/2003/webarch-20030616

>Use URIs: All important resources SHOULD be identified by a URI. 2


How do you define important resources?

>Dan's client and the server engage in HTTP content negotiation, so 
>that Dan receives the best image format his client can handle.

or the image format he usually prefers.

>Attention to Error-Handling
>
>Specifications of data formats SHOULD be clear about behavior in the 
>presence of errors. It is reasonable to specify that errors should 
>be worked around, or should result in the termination of a 
>transaction or session. It is not acceptable for the behavior in the 
>face of errors to be left unspecified.

Does that mean for example that an invalid HTML file should be said 
invalid by the user agent to the user:
	- not displayed
	- warning?
	- etc.

But one could say if the resource is invalid, it is not anymore the 
data format which was intended.

Let say a flavour of an XHTML Company X, which is defined for a 
specific case, a user agent of a company Y don't understand the 
format, what the user agent should do in this case?

So how do you define in your data format, that you have errors or 
that you have done another flavour of the technology.

When it's not valid, it's not HTML (c) Masayasu.

>
>Final-form data formats are not designed to allow modification or 
>uses other than that intended by their designers.


I might be wrong, but I read the sentence as "Extension mechanisms in 
a data format are forbidden".


Two good resources for HTTP problems
	http://www.w3.org/TR/chips
	http://www.w3.org/TR/cuap

They are both in the process of being republished... we are 
reformating them to have the same presentation.
CUAP is in the process of being redesigned as an HTTP session between 
a server and a user agent, and identify the common issues.

Thanks for this wonderful piece of work.
Congrats to authors and editors.








-- 
Karl Dubost / W3C - Conformance Manager
           http://www.w3.org/QA/

      --- Be Strict To Be Cool! ---

Received on Thursday, 26 June 2003 17:46:33 UTC