W3C home > Mailing lists > Public > xsl-editors@w3.org > October to December 2004

1.1 WD: Possible inconsistency between keywords and EnumerationTokens

From: Glen Mazza <grm7793@yahoo.com>
Date: Mon, 22 Nov 2004 19:11:30 -0500
Message-ID: <001601c4d0f0$fc56ec60$d20b24cc@PC07332>
To: <xsl-editors@w3.org>

I'd like to echo Thomas Haag's concern [1] about the usage of "keyword" and "enumeration token" in the XSL 1.1 WD, and have a few suggestions where the spec could be made clearer.

1.)  A global search in the 1.1 WD for the word "keyword" appears to suggest that it has two separate usages within the document:  (1) as a loose synonym for "enumeration token", and (2), in section 5.9.10 [2] as a special class of (enumeration?) tokens "that provide access to calculated values or other property values".  Definition #2 provides for only one keyword--"inherit".

This appears to create an inconsistency.  I don't see the need, however, for the second definition, because both 1.0 and 1.1 has only one keyword defined for it.  The second definition can be removed if the fourth tokenization rule in 5.9.11 is rewritten, if possible, from:

The Keyword values take precedence over EnumerationToken.


The "inherit" EnumerationToken take precedence over other EnumerationTokens.

Another reason for recommending this switch is that "keyword" appears too generic a word (i.e., too likely to be used as the first definition above) to be reserved as a special keyword as it currently is in 5.9.10.

2.)  However, if the Keyword definition remains in 5.9.10, I would like the spec to more clearly specify that a Keyword is a special type of EnumerationToken  (if it *is* a special type of EnumerationToken, I may be incorrect here as to your intent):

Change from:  "Keywords are special tokens in the grammar that provide access to calculated values or other property values."  to "Keywords are special EnumerationTokens [or enumeration tokens] ..."

Also, if a Keyword is an EnumerationToken, change the fourth tokenization rule in 5.9.11 to add "other" as follows:

The Keyword values take precedence over other EnumerationTokens.

3.)  Finally, in the table of section 5.9.12, Expression Value Conversions, perhaps best to switch from "Enumeration value, as defined..." to "Enumeration token, as defined..." to keep the naming consistent (a search on the WD will show that the latter is used elsewhere.)

Glen Mazza
Apache FOP Team

[1] http://lists.w3.org/Archives/Public/www-xsl-fo/2004Apr/0004.html
[2] http://www.w3.org/TR/2003/WD-xsl11-20031217/#d0e5427
Received on Tuesday, 23 November 2004 00:07:12 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:44:24 UTC