W3C home > Mailing lists > Public > public-qt-comments@w3.org > December 2004

qt-2004Feb0362-24, Treatment of META element

From: Joanne Tong <joannet@ca.ibm.com>
Date: Wed, 8 Dec 2004 15:52:34 -0500
To: Martin Duerst <duerst@w3.org>
Cc: public-qt-comments@w3.org, w3c-i18n-ig@w3.org, w3c-dom-wg@w3.org, Scott Boag <scott_boag@us.ibm.com>
Message-ID: <OF5B10BD52.85629699-ON85256F62.005BD188-85256F64.0072AE6C@ca.ibm.com>
In [1], you submitted the following comment on the Last Call Working 
Draft of XSLT 2.0 and XQuery 1.0 Serialization on behalf of the I18N 
Working Group.

[31] Section 5 and Section 6: "If the data model includes a head element
   that has a meta element child, the processor should replace any
   content attribute of the meta element, or add such an attribute,
   with the value as described above, rather than output a new meta 
   This is written as if there would be only one <meta> element.
   Replacement should only take place if the <meta> element has a
   http-equiv attribute with value 'Content-Type'.

The XSL and XQuery working groups have accepted your comment.  It is 
related to an issue about having to explore the entire contents of the 
HEAD element before it decides whether to to add a new META element as the 

first child.  See [2].  We intend to resolve this by replacing the 
offending text with:

"If a META element has been added to the HEAD element as described above,
then any existing META element child of the HEAD element having an
http-equiv attribute with the value "Content-Type" MUST be discarded."

Please let us know if the resolution to this issue is acceptable.

Joanne Tong

[2] http://lists.w3.org/Archives/Member/w3c-xsl-wg/2004Aug/0088.html
Received on Wednesday, 8 December 2004 21:00:23 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:22 UTC