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


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
RE: [xml-dev] Support for XML 1.1?

IMHO I dont read "discouraged" == "depreciated"
Why add something then mark it as "depreciated" ... thats why "discouraged" was used (IMHO, I wasn't there just reading my crystal ball).

I am wondering what the advantage/disadvantage of allowing XML 1.1 in a processor (or DB) would be if it has largely 1.0 clients ?
What should a serialize do given a 1.1 data object but asked to serialize as XML 1.0 ?

David A. Lee

-----Original Message-----
From: Liam R E Quin [mailto:liam@w3.org] 
Sent: Monday, October 01, 2012 3:25 PM
To: Costello, Roger L.
Cc: xml-dev@lists.xml.org
Subject: Re: [xml-dev] Support for XML 1.1?

On Mon, 2012-10-01 at 16:06 +0000, Costello, Roger L. wrote:
> Hi Folks,

> It appears that using XML 1.1 is the best way to go for supporting all
> the US-ASCII characters.


XML 1.1 is based on Unicode, as is XML.

US ASCII contains 128 defined code points (it's a 7-bit standard, with
the 8th bit available, if present, for parity checking).

Of these, the "c0 controls" with the exception of tab, carriage return,
newline, are deprecated [[
Document authors are encouraged to avoid "compatibility characters", as
defined in Unicode [Unicode]. The characters defined in the following
ranges are also discouraged. They are either control characters or
permanently undefined Unicode characters:
and, like C1 controls, may only appear if escaped as character

In practice, the only feature from XML 1.1 that you miss in using XML
1.0 5e instead is actually namespaces 1.1 and the ability to remove the
association between a prefix and a URI. The other "significant" feature,
adding Unicode NEL to whitespace, was for sure a mistake, and I'm not
sure it's actually being used outside one or two organizations.

As others have said, 1.1 did not get industry traction.

One reason cited was that it could potentially change the meaning of
existing documents, because of NEL in attribute values turning into a
space during normalization, and another was that existing XML 1.0
documents that had been well-formed became non well-formed if they used
the C1 control characters without escaping them.

But the biggest problem was a revision to XML 1.0 that said a processor
should reject documents marked as being XML 1.1. So it's too risky to
send an XML 1.1 document over the net. We retracted that mistaken
assertion, but it was too late.


Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/
Pictures from old books: http://fromoldbooks.org/
Co-author: 5th edition of "Beginning XML", Wrox, July 2012


XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.

[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
subscribe: xml-dev-subscribe@lists.xml.org
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]

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

Copyright 1993-2007 XML.org. This site is hosted by OASIS