<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.1" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: The whimzical world of HTML 5</title>
	<link>http://www.webdevout.net/tidings/2007/04/23/the-whimzical-world-of-html-5/</link>
	<description>Updates on the march of progress. A weblog about web design, standards, web browsers, and the overall health of the Web.</description>
	<pubDate>Fri, 25 Jul 2008 02:32:16 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.1</generator>

	<item>
		<title>by: Jacques Distler</title>
		<link>http://www.webdevout.net/tidings/2007/04/23/the-whimzical-world-of-html-5/#comment-3961</link>
		<pubDate>Sat, 26 May 2007 04:43:01 +0000</pubDate>
		<guid>http://www.webdevout.net/tidings/2007/04/23/the-whimzical-world-of-html-5/#comment-3961</guid>
					<description>I don't know why you are so enamoured of DTDs. DTD-based validators &lt;a href=&quot;http://golem.ph.utexas.edu/~distler/blog/archives/001206.html&quot;&gt;suck&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t know why you are so enamoured of DTDs. <abbr title="Document Type Definition">DTD</abbr>-based validators <a href="http://golem.ph.utexas.edu/~distler/blog/archives/001206.html">suck</a>.</p>
<p class="postdetails"><em>Posted using (Not Specified) .</em></p>
]]></content:encoded>
				</item>
	<item>
		<title>by: greg</title>
		<link>http://www.webdevout.net/tidings/2007/04/23/the-whimzical-world-of-html-5/#comment-3957</link>
		<pubDate>Tue, 22 May 2007 20:20:06 +0000</pubDate>
		<guid>http://www.webdevout.net/tidings/2007/04/23/the-whimzical-world-of-html-5/#comment-3957</guid>
					<description>wait, so that Im clear - requiring bug mode means that in order to make a browser 10 years from now, you will need include every version of every browser's rendering engine from the last decade?

what a horrible idea.

FWIW - canvas doesn't sound like a bad idea.  semantics - &quot;visual stuff goes here.&quot;  Better than a semantically vacuous div.</description>
		<content:encoded><![CDATA[<p>wait, so that <abbr title="Instant Message">Im</abbr> clear - requiring bug mode means that in order to make a browser 10 years from now, you will need include every version of every browser&#8217;s rendering engine from the last decade?</p>
<p>what a horrible idea.</p>
<p>FWIW - canvas doesn&#8217;t sound like a bad idea.  semantics - &#8220;visual stuff goes here.&#8221;  Better than a semantically vacuous div.</p>
<p class="postdetails"><em>Posted using (Not Specified) .</em></p>
]]></content:encoded>
				</item>
	<item>
		<title>by: kalikiana</title>
		<link>http://www.webdevout.net/tidings/2007/04/23/the-whimzical-world-of-html-5/#comment-3954</link>
		<pubDate>Sat, 05 May 2007 21:48:48 +0000</pubDate>
		<guid>http://www.webdevout.net/tidings/2007/04/23/the-whimzical-world-of-html-5/#comment-3954</guid>
					<description>&amp;#62; Not only does Ian Hickson want to omit a DTD, but he doesn’t seem to think that a version indicator is even necessary.

Wow. I heard and read bad things about HTML5 before. I know that not everybody likes XHTML. But now I can hardly believe any more that this is coming from the W3C Group. They really ought to go order an internet connection.</description>
		<content:encoded><![CDATA[<p>&gt; Not only does Ian Hickson want to omit a <abbr title="Document Type Definition">DTD</abbr>, but he doesn’t seem to think that a version indicator is even necessary.</p>
<p>Wow. I heard and read bad things about HTML5 before. I know that not everybody likes <abbr title="eXtensible HyperText Markup Language">XHTML</abbr>. But now I can hardly believe any more that this is coming from the <abbr title="World Wide Web Consortium">W3C</abbr> Group. They really ought to go order an internet connection.</p>
<p class="postdetails"><em>Posted using (Not Specified) .</em></p>
]]></content:encoded>
				</item>
	<item>
		<title>by: mpt</title>
		<link>http://www.webdevout.net/tidings/2007/04/23/the-whimzical-world-of-html-5/#comment-3948</link>
		<pubDate>Sun, 29 Apr 2007 06:20:46 +0000</pubDate>
		<guid>http://www.webdevout.net/tidings/2007/04/23/the-whimzical-world-of-html-5/#comment-3948</guid>
					<description>* Yes, bugmode is a terrible idea, because it would make writing a new useful Web browser in 2030 prohibitively difficult. It's an anticompetitive move.

* It's &lt;em&gt;already&lt;/em&gt; impossible for an SGML parser to parse HTML4 as used in the real world, because the mass of humans who author the Web (and the computer programs written by those humans) will never be that perfect. The main change in HTML5 is the level of honesty.

* A DTD can represent only a small fraction of HTML5's conformance requirements. The judgement is that misleading authors, by providing DTD-based &quot;validation&quot; that tests only a small fraction of the requirements, does more harm than good.

* Backward compatibility is vital for the same reason bugmode is a bad idea: to make it feasible for programmers to write new useful Web browsers in decades to come. Making obsolete elements non-conforming does not contradict this goal: the specification will continue to describe how to render those things that are no longer conforming, as long as a non-trivial number of Web pages use them.

* As far as I know, &lt;code&gt;canvas&lt;/code&gt; and &lt;code&gt;embed&lt;/code&gt; both exist because browser vendors find it extremely difficult to implement generalized behavior (which is why &lt;code&gt;object&lt;/code&gt; is so patchily implemented, for example).

* The argument for &lt;code&gt;ping&lt;/code&gt; is pretty much exactly what you stated: that people who care will be able to disable it in their browser, whereas it's difficult or impossible to do the same with server-side tracking. I disagree on the grounds that browsers won't let you do this because the UI would be ridiculous. (&quot;Let Web sites track which links you click on: (*) Always ( ) Sometimes&quot;)</description>
		<content:encoded><![CDATA[<p>* Yes, bugmode is a terrible idea, because it would make writing a new useful Web browser in 2030 prohibitively difficult. It&#8217;s an anticompetitive move.</p>
<p>* It&#8217;s <em>already</em> impossible for an <abbr title="Standard Generalized Markup Language">SGML</abbr> parser to parse HTML4 as used in the real world, because the mass of humans who author the Web (and the computer programs written by those humans) will never be that perfect. The main change in HTML5 is the level of honesty.</p>
<p>* A <abbr title="Document Type Definition">DTD</abbr> can represent only a small fraction of HTML5&#8217;s conformance requirements. The judgement is that misleading authors, by providing DTD-based &#8220;validation&#8221; that tests only a small fraction of the requirements, does more harm than good.</p>
<p>* Backward compatibility is vital for the same reason bugmode is a bad idea: to make it feasible for programmers to write new useful Web browsers in decades to come. Making obsolete elements non-conforming does not contradict this goal: the specification will continue to describe how to render those things that are no longer conforming, as long as a non-trivial number of Web pages use them.</p>
<p>* As far as I know, <code>canvas</code> and <code>embed</code> both exist because browser vendors find it extremely difficult to implement generalized behavior (which is why <code>object</code> is so patchily implemented, for example).</p>
<p>* The argument for <code>ping</code> is pretty much exactly what you stated: that people who care will be able to disable it in their browser, whereas it&#8217;s difficult or impossible to do the same with server-side tracking. I disagree on the grounds that browsers won&#8217;t let you do this because the UI would be ridiculous. (&#8221;Let Web sites track which links you click on: (*) Always ( ) Sometimes&#8221;)</p>
<p class="postdetails"><em>Posted using (Not Specified) .</em></p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Chris Wilson</title>
		<link>http://www.webdevout.net/tidings/2007/04/23/the-whimzical-world-of-html-5/#comment-3947</link>
		<pubDate>Fri, 27 Apr 2007 20:38:34 +0000</pubDate>
		<guid>http://www.webdevout.net/tidings/2007/04/23/the-whimzical-world-of-html-5/#comment-3947</guid>
					<description>David, you missed the bit where they're considering putting the marquee element in HTML5.  :)</description>
		<content:encoded><![CDATA[<p>David, you missed the bit where they&#8217;re considering putting the marquee element in HTML5.  :)</p>
<p class="postdetails"><em>Posted using (Not Specified) .</em></p>
]]></content:encoded>
				</item>
</channel>
</rss>
