This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
6.7.3, content Why is the construction of text nodes consisting only of whitespace in element content not described in terms of the [element content whitespace] property? Also note that only validating parsers are required to return this information. And it should be mentioned that this is a big change from XPath 1.0, which did not remove element content whitespace.
The accessors of the data model The accessors sometimes rely on the data type xs:anyURI, i.e. baseURI (5.2), document-uri (5.4), unparsed-entity-system-id (5.16). xs:anyURI itself in its latest version is defined in terms of IRI. I would be good if you could refer to IRI itself, in addition to anyURI. Based on Martin's review, comment [20]
Comment #1 is a cut-and-paste error, ignore it.
The WG has discussed this comment: http://lists.w3.org/Archives/Member/w3c-xsl-query/2005May/0069.html and declines to make any changes. Please let us know if you accept this resolution.
(In reply to comment #3) We still find it surprising that, for example, an XSLT 2 identity transform will strip element-content whitespace from a document. But assuming you do not change this, we still believe that section 6.7.3 should be reworded to use infoset terminology (i.e. refer to the [element content whitespace] property instead of referring to text nodes occurring in element content). The PSVI wording in 6.7.4 would need to be changed to match.
With respect to We still find it surprising that, for example, an XSLT 2 identity transform will strip element-content whitespace from a document. See bug #1309. With respect to the rest of your comment, we agree and will make appropriate editorial changes.
(In reply to comment #5) See our reply to bug #1309. We accept your decision to request CR comments on this issue.