- From: <bugzilla@wiggum.w3.org>
- Date: Mon, 09 May 2005 10:05:37 +0000
- To: public-qt-comments@w3.org
- Cc:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=1309 ------- Additional Comments From davidc@nag.co.uk 2005-05-09 10:05 ------- > Is it possible to identify when these comments were previously made This current report is strongly related to http://www.w3.org/2005/04/data-model-issues.html#toc.qt-2003Dec0085-01 However the text that I commented about there has been largely removed/rewriten so most of the text of that comment is no longer relevant, the final comment lodged there is Norm's White space is now significant in all cases except element-only content where it is not significant. The draft has been clarified to reflect this. So the first of my comments in this bug report could be rephased as saying that: a) the clarification added at this point isn't correct as it uses the "Element Content" XML production which isn't necessarily available in an infoset which even if it was generated by parsing an XML document may not have the information. It will (or may) have the [element content whitespace] property reported though so this should be used as described in my message. b) If this clause isn't removed, the negative impact it has on XPath compatibility should be documented. The second of my comments that the reverse mapping should not always set the infoset property [element content whitespace] to "unknown", as it violates a constraint in the infoset spec, is new. David
Received on Monday, 9 May 2005 10:05:56 UTC