W3C home > Mailing lists > Public > www-qa-wg@w3.org > January 2003

AI-2003-1-13-1 - Checkpoint 9.4 rewording - done

From: Karl Dubost <karl@w3.org>
Date: Mon, 20 Jan 2003 08:44:52 -0500
Message-Id: <a05200f09ba51a7b5b0a9@[24.202.71.17]>
To: www-qa-wg@w3.org

AI-2003-1-13-1  to draft new language for checkpoint 9.4
http://www.w3.org/QA/WG/ActionItems

Now
>Checkpoint 9.4. Use a standard mechanism to define the extension.
>[Priority 3]
>
>To fulfill this checkpoint, a specification MUST provide a standard
>way of defining the extension. It is not applicable if extensions
>are not allowed.
>
>This helps to ensure predictable handling of extensions, that is,
>its recognition as such and the appropriate actions (i.e., to
>ignore or to implement).
>
>Examples & Techniques for this checkpoint.

Proposition

Checkpoint 9.4. Define a abstract mechanism to create extension [Priority 3]

To fulfill this checkpoint a specification MUST provide a unique way 
of defining the extension, each time is it authorized by the 
specification. It is not applicable if extensions are not allowed.

This helps to ensure predictable handling of extensions, that is, its 
recognition as such and the appropriate actions (i.e., to ignore or 
to implement).

Examples & Techniques for this checkpoint.

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

      --- Be Strict To Be Cool! ---
Received on Monday, 20 January 2003 08:44:57 GMT

This archive was generated by hypermail 2.2.0 + w3c-0.30 : Thursday, 9 June 2005 12:13:12 GMT