W3C home > Mailing lists > Public > public-webapi@w3.org > April 2006

[comment] XMLHttpRequest Object - Conformance Model

From: Karl Dubost <karl@w3.org>
Date: Wed, 12 Apr 2006 15:45:27 +0900
Message-Id: <63158BD4-C561-48D7-A801-1DAF64994BE6@w3.org>
To: public-webapi@w3.org

Hi,

This is a QA Review comment for "The XMLHttpRequest Object"
http://www.w3.org/TR/2006/WD-XMLHttpRequest-20060405/
Wed, 05 Apr 2006 17:02:33 GMT
First WD

[[[
2. Conformance

This section is normative

The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,  
SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL in this document are to be  
interpreted as described in RFC 2119 [RFC2119].
]]]

-- The XMLHttpRequest Object
http://www.w3.org/TR/2006/WD-XMLHttpRequest-20060405/#conformance
Wed, 05 Apr 2006 17:02:33 GMT

Good there is a conformance section in your document but which is a  
bit dry, maybe once you have defined your class of products, you  
could define what does that mean to be conformant to XMLHttpRequest.

For example,
if one class of product is a "user agent with a scripting engine", to  
reach "basic conformance" would mean that all MUST have to be  
implemented, and for "full conformance", All MUST and SHOULD have to  
be implemented.

This is just an example, The WG would have to define its own  
conformance model.




-- 
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 Wednesday, 12 April 2006 06:45:43 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:54 GMT