OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: [xml-dev] The XML 1.1 Candidate Recommendation is published

[ Lists Home | Date Index | Thread Index ]

>(Richard Tobin, can you give an example of the trick in question?)


 <!DOCTYPE foo [
 <!ENTITY a '<a&#xD;b="c"/>'>

This is well-formed XML 1.0 because the S production includes CR
(#xD).  The replacement text of the entity a contains a CR character,
and it gets parsed as whitespace.  This is of course the exception:
real CR characters in the document are translated on input and are
never matched against the productions.

The natural analogy would be to do the same for NEL (#x85), but this
would complicate life for (at least some) parsers greatly - they would
need a check in many places in order to tokenize differently depending
on the document version.  Since there are no existing well-formed
documents that rely on NEL being in S, and no good use cases for
examples like the one above, we decided it was not worth adding it.

So this will not be well-formed:

 <?xml version="1.1"?>
 <!DOCTYPE foo [
 <!ENTITY a '<a&#x85;b="c"/>'>

Similarly, we didn't add NEL to the characters normalized to space
in attributes.  And again, this only makes a difference if you use
a character reference.  In XML 1.0, this is valid:

 <!DOCTYPE foo [
 <!ENTITY b 'foo&#xD;bar'>
 <foo att="&b;"/>

but the corresponding document with &#x85; instead of &#xD; will
be invalid in 1.1.

We did consider the suggestion of removing CR from S in 1.1, but apart
from pointlessly breaking backward compatibility it would again mean
that parsers would have to test the version number when tokenizing.

-- Richard


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS