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] SAX Topic 2004-0002: XML 1.1 support

[ Lists Home | Date Index | Thread Index ]

/ Elliotte Rusty Harold <elharo@metalab.unc.edu> was heard to say:
| At 9:27 AM -0500 2/22/04, David Megginson wrote:
|>- if a document is in XML 1.1, all of its entities must be as well;
|>   in that case, should getXMLVersion report XML 1.1 as the default
|>   even when an entity is explicity labelled as XML 1.0?
| I'm not quite sure what you mean here. An XML 1.1 document can include
| 1.0 external entities. According to the XML 1.1 spec:
| An XML 1.1 document may invoke XML 1.0 external entities, so that
| otherwise duplicated versions of external entities, particularly DTD
| external subsets, need not be maintained. However, in such a case the
| rules of XML 1.1 are applied to the entire document.
| I'm not sure what that last sentence means. Can anyone answer these questions?

I'll run these past the XML Core WG (though John, Richard, and others
may very well see them here), just to see if my understanding is
consistent with theirs.

Basically, I think the intent of that quoted paragraph is to allow the
parser to choose 1.0 behavior or 1.1 behavior at the start of the
document entity and apply those rules to the entire document. In other
words, if an external parsed entity has an XML declaration and its
version is "1.0" or "1.1" the version is effectively ignored.

| 1. What should a 1.1 aware parser do when from a 1.1 document it loads
| an external entity that uses an unescaped C1 control character?

That's a well-formedness error.

| 2. What should a 1.1 aware parser do when when it loads an entity
| labelled as 1.0 and which is malformed by virtue of using an escaped
| C0 control character?

It happily puts the C0 character into the information set.

| 3. What should a 1.1 aware parser do when it loads an invalid (but
| well-formed) external 1.0 entity which would be valid except for the
| use of NEL in white space in element content?

NEL is whitespace in element content in 1.1, so it just ignores it and
reports that the document is valid (assuming there are no other
validity or WF errors).

                                        Be seeing you,

Norman Walsh <ndw@nwalsh.com> | There is no such thing as an absolute
http://nwalsh.com/            | certainty, but there is assurance
                              | sufficient for the purposes of human
                              | life.--John Stuart Mill

PGP signature


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

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