W3C home > Mailing lists > Public > www-tag@w3.org > January 2013

Highlighting issue of XML support in DOM 4 (was: TAG Decision .....develop a polyglot guide)

From: Noah Mendelsohn <nrm@arcanedomain.com>
Date: Tue, 22 Jan 2013 09:11:05 -0500
Message-ID: <50FE9DF9.2050901@arcanedomain.com>
To: "www-tag@w3.org" <www-tag@w3.org>
CC: Daniel Glazman <daniel@glazman.org>, Norm Walsh <ndw@nwalsh.com>
I know you've all seen the long thread on polyglot. At the risk of adding 
further noise, I'm highlighting this note specifically to www-tag because 
it raises a significant issue that I don't think was discussed when we did 
our XML/HTML integration report. Quoting Daniel from the note below:

> Guys, I tried to make BlueGriffon output polyglot html5 for future
> 1.7 and I am hitting a serious issue: I am unable to do it for one
> single reason... Rendering engines are removing support for
> Document.xmlVersion, Document.xmlStandalone and Document.xmlEncoding
> that are deprecated in DOM 4. I have then *no way at all* of
> knowing if a document was parsed with an XML declaration or not
> from script, using the DOM.

Regardless of your position on polyglot and XML, the DOM 4 decision does 
seem significant, and I had not been aware of it. Worth any TAG discussion? 
Does it affect our recommendation on polyglot? Should we push on the DOM WG 
to change?

Thank you.

Noah



-------- Original Message --------
Subject: Re: TAG Decision on Rescinding the request to the HTML WG to 
develop  a polyglot guide
Resent-Date: Tue, 22 Jan 2013 07:51:55 +0000
Resent-From: www-tag@w3.org
Date: Tue, 22 Jan 2013 08:51:28 +0100
From: Daniel Glazman <daniel@glazman.org>
To: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
CC: Maciej Stachowiak <mjs@apple.com>, Henri Sivonen <hsivonen@iki.fi>, 
Sam Ruby <rubys@intertwingly.net>, Noah Mendelsohn <nrm@arcanedomain.com>, 
  "www-tag@w3.org List" <www-tag@w3.org>, "public-html@w3.org" 
<public-html@w3.org>,  Paul Cotton <Paul.Cotton@microsoft.com>, Anne van 
Kesteren <annevk@annevk.nl>, Aryeh Gregor <ayg@aryeh.name>,  Lachlan Hunt 
<lachlan.hunt@lachy.id.au>, Ms2ger <ms2ger@gmail.com>

(cc:ed to DOM 4 editors)

Guys, I tried to make BlueGriffon output polyglot html5 for future
1.7 and I am hitting a serious issue: I am unable to do it for one
single reason... Rendering engines are removing support for
Document.xmlVersion, Document.xmlStandalone and Document.xmlEncoding
that are deprecated in DOM 4. I have then *no way at all* of
knowing if a document was parsed with an XML declaration or not
from script, using the DOM.
The XML declaration is not reachable as a PI in the OM. Since an
editor like mine can edit all flavors of html, it still needs to
output the xml declaration for xhtml and for html5 if the polyglot
option is not chosen.

Because of that deprecation in DOM 4 (already removed in mozilla
central), Polyglot HTML5 is totally impossible to implement in an
application that is not Polyglot-HTML5 only... I guess this is an
architectural issue for the TAG, right?

</Daniel>
Received on Tuesday, 22 January 2013 14:11:33 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 22 January 2013 14:11:33 GMT