RE: Revised HTML/XML Task Force Report

Perhaps to “+1” (if I can still use that after Google's recent launch)  Larry’s comment, and restate:

 

When I read this I thought to myself, "what does it mean by 'limited applicability'?" Limited how? For example, if a high-volume Web site wanted to use such an XML tool chain producing and consuming HTML5, they could do so using Polyglot mark-up. Is that classed under "limited applicability"? I guess what I take issue with is the notion that for Polyglot to make any sense everyone has to adopt it – to me, that is not the point of polyglot.

 

Dan

 

From: www-tag-request@w3.org [mailto:www-tag-request@w3.org] On Behalf Of Larry Masinter
Sent: 12 July 2011 07:29
To: karld@opera.com
Cc: nrm@arcanedomain.com; www-tag@w3.org; ndw@nwalsh.com
Subject: Re: Revised HTML/XML Task Force Report

 

Maybe I'm asking too much, but I was hoping that the report from a task force set up to work through xml-html convergence issues might give a better idea of how serious the problems with various approaches might be, to help inform decisions. Html pages that cannot be made polyglot..... are they rare? Common? Only happens with pages that also have significant problems in ogher ways? 

While detailed data might be hard to come by, how about ONE example of a page "in the wild" with this property...

Connected by DROID on Verizon Wireless



-----Original message-----

From: Karl Dubost <karld@opera.com>
To: Larry Masinter <masinter@adobe.com>
Cc: Noah Mendelsohn <nrm@arcanedomain.com>, "www-tag@w3.org" <www-tag@w3.org>, Norm Walsh <ndw@nwalsh.com>
Sent: Tue, Jul 12, 2011 03:11:46 GMT+00:00
Subject: Re: Revised HTML/XML Task Force Report

Larry,

Le 11 juil. 2011 à 21:13, Larry Masinter a écrit :
> * How common are HTML documents that cannot be  reasonably represented in XML?

I'm not sure what you mean by common? Do you need global stats of the Web? Or patterns?
Global stats are difficult to draw.

For example, right now most of the documents which have an XHTML 1.0 doctype and are served as text/html are (unfortunately) not deliverable with application/xhtml+xml (My own site is only in application/xhtml+xml but I do not use scripting and many delicacies that most sites are using.)


> * What kinds of practical difficulties would arise for those documents (and how serious are those difficulties)?

These have been addressed a few times for a long time in different fora and is at the heart of all regular discussions between HTML and XML serializations. 

You can also check "How is the treatment of application/xhtml+xml documents different from the treatment of text/html documents?"
https://developer.mozilla.org/en/Mozilla_Web_Developer_FAQ#How_is_the_treatment_of_application.2fxhtml.2bxml_documents_different_from_the_treatment_of_text.2fhtml_documents.3f



-- 
Karl Dubost - http://dev.opera.com/

Developer Relations & Tools, Opera Software