Best Practice Recipes for Publishing RDF Vocabularies - Default Behavior

Hi,
This is a QA Review comment for "Best Practice Recipes for Publishing
RDF Vocabularies"
http://www.w3.org/TR/2006/WD-swbp-vocab-pub-20060314/
Tue, 14 Mar 2006 12:48:26 GMT
1st WD


In the Content Negotiation section

[[[
Note that where the server is to be configured to perform content  
negotiation, a 'default behavior' must be specified. The server must  
be able to determine which response should be sent in the case where  
the client does not include an 'Accept:' field in the request message  
header (i.e. the client doesn't specify a preference), or where the  
values of the 'Accept:' field do not match any of the available  
content types (i.e. the client asks for something other than RDF/XML  
or HTML).
]]]

-- Best Practice Recipes for Publishing RDF Vocabularies
http://www.w3.org/TR/2006/WD-swbp-vocab-pub-20060314/#negotiation
Tue, 14 Mar 2006 12:48:26 GMT

The second sentence is too long and the paragraph difficult to read.

Suggestion:

	"The server must be configured with a “default behavior”
	to perform a content negotiation, because sometimes
	    1. the client does not send an 'Accept:' field in the
                request message header i.e. the client doesn't
                specify a preference)
	    2. the client send values of the 'Accept:' field which
                do not match any of the available content types
                (i.e. the client asks for something other than
                RDF/XML or HTML)."


Please, move the note about IE6, or comment about IE6 in a separated  
paragraph as an example of implementation problems. Did you test with  
other user agents (search engine bots, screen reader, voice reader,  
etc.)?



-- 
Karl Dubost - http://www.w3.org/People/karl/
W3C Conformance Manager, QA Activity Lead
   QA Weblog - http://www.w3.org/QA/
      *** Be Strict To Be Cool ***

Received on Monday, 15 May 2006 03:14:50 UTC