- From: <bugzilla@wiggum.w3.org>
- Date: Tue, 13 Dec 2005 15:07:11 +0000
- To: public-qt-comments@w3.org
- Cc:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=2474 ------- Additional Comments From davidc@nag.co.uk 2005-12-13 15:07 ------- > by reference to section 2.13 grr sorry about that, before posting I read that (but read the wrong bit of the xml spec by mistake) I know it's W3C house style, but the practice of linking to the reference list at the end of the current document rather than directly linking to the correct section of an external document is _so_ annoying/confusing. > I think we're only concerned with one parsed entity, as I say that depends just how far out of scope are references to parsed entities generated by character maps. The note in section 9 warning that character maps can result in non-wellformed documents could perhaps be extended to say that they can also make the resulting document not conform to whatever unicode normalisation form is specified. As far as 4 and 5 on the list, they are also a bit questionable, as list-typed content (eg IDREFS) is a white space list of Name tokens, so arguably they each need to be checked individually (although conversely, arguably the serialiser doesn't know that the element or attribute is so typed...) I don't mind either way, but I can't tell from the spec. I suspect that the answer is that the serialisation doesn't need to check individual tokens in a list, but that a validating parser which choses to warn of normalistion errors _will_ warn when reading the resulting document if tokens are not in normal form. David
Received on Tuesday, 13 December 2005 15:07:34 UTC