W3C home > Mailing lists > Public > www-html-editor@w3.org > April to June 2003

[XHTML2] Editorial comments on WD4

From: Ernest Cline <ernestcline@mindspring.com>
Date: Tue, 15 Apr 2003 22:36:32 -0400
To: www-html-editor@w3.org
Message-ID: <3E9C8970.17964.2B2C777@localhost>

Hopefully not too long, but here they are. There are no proposals here 
for a change to the working other draft other than to improve clarity 
of the existing proposal.

1) Section 3.2, User Agent Conformance
If the intent is that a specific set of user agent conformance 
requirements be required by XHTML2, then they should be included here 
instead of refrred to in another document.  If the intent is that the 
it should refer to the current version (as opposed to a a static 
version of [XHTMLMOD] then that reference should be changed from:
  http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410
to:
  http://www.w3.org/TR/xhtml-modularization/

2) Section 5.5 Attribute Types
In the second table the table head for the first column should be 
"Attribute Type" instead of "Data Type".

3) Section 5.5 Attribute Types
Datetime should either contain a reference to:
  http://www.w3.org/TR/NOTE-datetime
or if a different subset of ISO 8601 formats is to be used it should be 
  detailed here.

4) Section 5.5 Attribute Types
There is a Length type defined but it is not used for ant attrubutes in 
XHTML2. This type should be removed.

5) Section 7 XHTML Structure Module
In the minimal content model (MCM) table the body element has its MCM 
defined as:
 	(Heading | Block | List)*
despite the fact that Heading, Block, and List content sets are not 
definied in the Structure Module but in the Text Module and the List 
Module. This needs to either be changed to an empty MCM with the those 
modules expanding the MCM of the body element or this module should 
include an explicit reference to the those modules for this definition.

6) Section 7.1 The html element
Since metadata is not part of this module, it would seem to me that 
either the profile attribute should be moved from here to the XHTML 
Metainformation Module as an attribute that that module adds to the 
html element, or the Metainformation Module should be made part of the 
XHTML Structure Module instead of being a module of its own.

7) Section 7.2 The head element
Since only the title element is defined in the XHTML Structure Module, 
the description of this element should make no explicit mention of 
other uses such as metadata since in theory, an implementation might 
choose to not make use of another module that puts data into the head. 
A suggested rewording of the description is as follows:

The head element contains information about the current document, such 
as its title, that is not considered document content. The default 
presentation of the head is not to display it; however that can be 
overridden with a stylesheet for special purpose use. User agents may 
however make information in the head available to users through other 
mechanisms. Other modules may add additional elements besides title.

8) Section 8 XHTML Text Module
In the MCM table, the MCM of the blockquote element conatins the List 
content set which is not defined in this module. Either this module 
needs to reference the List Module or the List Module needs to be the 
one which adds List to the MCM of the blockquote element.

9) Section 8 XHTML Text Module
In the MCM table, the MCM of the p element contains the List content 
set and the table element which are not definined in this Module. 
Either this module needs to reference the those modules or those 
modules need to be the ones which add List and table to the MCM of the 
p element.

10) Section 8 XHTML Text Module
See comment 5 above about the placement of the information that the 
Heading and Block content sets are part of the MCM of the body element.

11) Section 8.3 The blockquote element
This could be an example of a URI that is a URN instead of a URL in the 
sepecification, by changing the cite attribute in the example to:
	cite="urn:ISBN:0-395-48933-4"

12) Section 8.13 The p element
Since lists and tables are not defined in this module, the description 
of the p element should be rewritten so that those are not referenced. 
A suggested rewording of the description is as follows:

The p element represents a paragraph.

In comparison with earlier versions of HTML, where a paragraph could 
only contain inline text, XHTML2's paragraphs represent the conceptual 
idea of a paragraph, and so may contain blockquote, and pre elementa as 
well as inline text. They may not, however, contain directly nested p 
elements. Other modules may add additional non-inline elements.

13) Section 10 XHTML List Module
See comment 5 above about the placement of the information that the 
List content set is part of the MCM of the body element.

14) Section 10 XHTML List Module
See comment 8 above about the placement of the information that the 
List content set is part of the MCM of the blockquote element.

15) Section 10 XHTML List Module
See comment 9 above about the placement of the information that the 
List content set is part of the MCM of the p element.

16) Section 11.2 The map element
Is there a reason why the class, id, and title elements are listed 
separately? It would seem to me that this description could be 
condensed down to the Core Attributes Colllection.

17) Section 11.2 The map element
With the embedding attributes now found in a wide range of elements, 
there appears to be no need to use object in XHTML 2 to achieve the 
structure given by the examples in this section. Changing all object 
references to p or other elements from the Text Module should be done.

18) Section 13 XHTML Metainformation Module
See comment 6 above about the placement of the information that the 
html element can possess the profile attribute.

19) Section 13 XHTML Metainformation Module
Is there a reason why the shorter and more commonly used term meta-data 
was not used instead of metainformation? (I am aware of the trademark 
that keeps the standard from using metadata with no hyphen or space.)

20) Section 14.1.3 Rules for processing objects
The examples for minimally coded object elements should contain a 
discussion of the fact that their functionality can be duplicated by 
the use of the Embedding Attribute Collection and then point out that 
object should be used in XHTML 2 for more complex embedding functions 
that the Embedding Attribute Collection cannot handle.

21) Section 17 XHTML Tables Module
See comment 9 above about the placement of the information that the 
table element is part of the MCM of the p element.
Received on Tuesday, 15 April 2003 22:36:25 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 18:17:44 GMT