RE: [xml-dev] Support for XML 1.1?

[Liam R E Quin <liam@w3.org>]

On Mon, 2012-10-01 at 19:33 +0000, David Lee wrote:
> IMHO I dont read "discouraged" == "depreciated"

You're right, I meant discouraged rather than deprecated.
We can't deprecate something only just introduced :-)

> 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 ?

Interoperability if someone sends you an XML 1.1 document?

> What should a serialize do given a 1.1 data object but asked to
> serialize as XML 1.0 ?
> 
As David Carlisle pointed out, it might be possible to write it out as
1.0 without problems.

The only real issue is when you get meaningless garbage control
characters such as ENQ or EOT. The most likely reason these get into
documents is from encoding errors - e.g. a database using a Windows 12xx
codepage or an old Apple encoding that used those codepoints for actual
characters rather than device control. In element content you can map
them to, e.g. <out-of-range-character codepoint="7" /> or <ascii:bel/>
or something.  Or write them out as entity references and have two
different DTDs.

Undeclaring namespace bindings is nice, but generally won't cause
breakage if you don't do it on output.

Liam

-- 
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, 2012