- From: Karl Dubost <karl@w3.org>
- Date: Mon, 14 Apr 2008 10:06:47 +0900
- To: Al Gilman <Alfred.S.Gilman@IEEE.org>
- Cc: Ian Hickson <ian@hixie.ch>, Steven Faulkner <faulkner.steve@gmail.com>, HTML WG <public-html@w3.org>, wai-xtech@w3.org
Le 14 avr. 2008 à 00:01, Al Gilman a écrit :
> The HTML *specification* should be about the markup.
I don't think it is true. It is not only about the *document* class
of products
For example, in the user agent class of product a requirement of HTML
4.01:
"For reasons of accessibility, user agents must
always make the content of the TITLE element
available to users (including TITLE elements
that occur in frames).
-- http://www.w3.org/TR/html4/struct/global.html#edef-TITLE
What is important is to clearly define the class of products. See
* 2.2.2 What needs to conform? [1]
* 3. Classes of products and specification category [2]
The following is a list of the most common classes of products for W3C
specifications:
* Content (of type, meaning, and format as defined in the
specification)
* Producer of content (may be divided into initiators and
modifiers)
* Player (read-only consumer, conveys content in non- XML way)
* Consumer in a one-way pipeline
* Responding agent (e.g., server) of API (consumer and producer)
* Processor (consumer of its vocabulary/instructions)
* Module that hosts the processor
* Producer of instructions/commands to processor
* Profile derived from the specification's Rules for Profiles
* Specification (guidelines)
[1]: http://www.w3.org/TR/qaframe-spec/#what-conform
[2]: http://www.w3.org/TR/spec-variability/#spec-cat-cop
--
Karl Dubost - W3C
http://www.w3.org/QA/
Be Strict To Be Cool
Received on Monday, 14 April 2008 01:07:27 UTC