<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Interview with Ian Hickson, editor of the HTML 5 specification.</title>
	<atom:link href="http://www.webstandards.org/2009/05/13/interview-with-ian-hickson-editor-of-the-html-5-specification/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.webstandards.org/2009/05/13/interview-with-ian-hickson-editor-of-the-html-5-specification/</link>
	<description>Working together for standards</description>
	<lastBuildDate>Wed, 27 Mar 2013 12:19:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Goyax</title>
		<link>http://www.webstandards.org/2009/05/13/interview-with-ian-hickson-editor-of-the-html-5-specification/comment-page-1/#comment-75767</link>
		<dc:creator>Goyax</dc:creator>
		<pubDate>Thu, 06 Aug 2009 11:05:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/?p=1726#comment-75767</guid>
		<description>It is very important that the new standard and the team behind it (for example the Microsoft employee sitting on one of the chairs of the W3C) is able to connect browser vendors more and involve them that far, so web-developpers are not forced anymore to keep an eye on every single browser implementation. The success of the www is that all applications in it (talking about applications means even a simple html-only-page) are usable on so many diffenrent devices and operating systems. Eliminating differences between the browser implementations will speed up the evolution of the www.</description>
		<content:encoded><![CDATA[<p>It is very important that the new standard and the team behind it (for example the Microsoft employee sitting on one of the chairs of the W3C) is able to connect browser vendors more and involve them that far, so web-developpers are not forced anymore to keep an eye on every single browser implementation. The success of the www is that all applications in it (talking about applications means even a simple html-only-page) are usable on so many diffenrent devices and operating systems. Eliminating differences between the browser implementations will speed up the evolution of the www.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Proxy</title>
		<link>http://www.webstandards.org/2009/05/13/interview-with-ian-hickson-editor-of-the-html-5-specification/comment-page-1/#comment-75710</link>
		<dc:creator>Proxy</dc:creator>
		<pubDate>Sat, 11 Jul 2009 21:54:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/?p=1726#comment-75710</guid>
		<description>Sounds useful, i´ll try the new specification. What about XHTML? Will core elements of XHTML get integrated into HTML 5 specs?</description>
		<content:encoded><![CDATA[<p>Sounds useful, i´ll try the new specification. What about XHTML? Will core elements of XHTML get integrated into HTML 5 specs?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bevan</title>
		<link>http://www.webstandards.org/2009/05/13/interview-with-ian-hickson-editor-of-the-html-5-specification/comment-page-1/#comment-75706</link>
		<dc:creator>Bevan</dc:creator>
		<pubDate>Fri, 10 Jul 2009 04:16:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/?p=1726#comment-75706</guid>
		<description>Nice Interview, great sharing about HTML

&lt;a href=&quot;http://www.bevanwistar.com&quot; rel=&quot;nofollow&quot;&gt;Bevanwistar&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Nice Interview, great sharing about HTML</p>
<p><a href="http://www.bevanwistar.com" rel="nofollow">Bevanwistar</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: joooc</title>
		<link>http://www.webstandards.org/2009/05/13/interview-with-ian-hickson-editor-of-the-html-5-specification/comment-page-1/#comment-75696</link>
		<dc:creator>joooc</dc:creator>
		<pubDate>Sat, 04 Jul 2009 16:59:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/?p=1726#comment-75696</guid>
		<description>I like the idea of non-version HTML standard. A lot of web apps doesn&#039;t use versions anymore (they just simply update on the run).

However I&#039;m scared about possible mess generated by various browsers and their implementation of the most recent rules ... on the other hand it should be less work to do it step by step so they can better react ... sounds interesting.

Looking forward for my first HTML 5 valid web page ;-)</description>
		<content:encoded><![CDATA[<p>I like the idea of non-version HTML standard. A lot of web apps doesn&#8217;t use versions anymore (they just simply update on the run).</p>
<p>However I&#8217;m scared about possible mess generated by various browsers and their implementation of the most recent rules &#8230; on the other hand it should be less work to do it step by step so they can better react &#8230; sounds interesting.</p>
<p>Looking forward for my first HTML 5 valid web page ;-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yazgunu</title>
		<link>http://www.webstandards.org/2009/05/13/interview-with-ian-hickson-editor-of-the-html-5-specification/comment-page-1/#comment-75684</link>
		<dc:creator>Yazgunu</dc:creator>
		<pubDate>Sun, 28 Jun 2009 13:18:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/?p=1726#comment-75684</guid>
		<description>I still hope to see the day the Flash dies.</description>
		<content:encoded><![CDATA[<p>I still hope to see the day the Flash dies.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christian</title>
		<link>http://www.webstandards.org/2009/05/13/interview-with-ian-hickson-editor-of-the-html-5-specification/comment-page-1/#comment-75681</link>
		<dc:creator>Christian</dc:creator>
		<pubDate>Sat, 27 Jun 2009 10:59:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/?p=1726#comment-75681</guid>
		<description>The main thing that I miss about HTML5 is extensibility. Everything is either baked in and bloats the main spec or has to rely on clumsy, underspecified class-attribute hacks.

XML may not be perfect and the convention of using URLs as namespace identifiers must have created confusion without end. But at least XHTML has an extension mechanism - only that Microsoft never started supporting it. Why is there no consideration to do something similar with non-XML HTML5? Is using divs with strange attributes really better than using additional vocabularies in HTML? (RDFa is also a hack in this respect IMO, but at least it can accomodate extension vocabularies in a decentralized and conflict-free fashion. Before tossing that out of the window, an attempt should be made of doing namespaces in a clearer fashion, if URNs are considered to be too complicated).

I really don&#039;t understand this whole aspect of HTML5. Yes, the W3C XHTML stuff was over-engineered and sometimes far away from reality. Yes, they put the bar a bit too high and so the transition never happened. 

But baking every possible use case into one core vocabulary won&#039;t do either.</description>
		<content:encoded><![CDATA[<p>The main thing that I miss about HTML5 is extensibility. Everything is either baked in and bloats the main spec or has to rely on clumsy, underspecified class-attribute hacks.</p>
<p>XML may not be perfect and the convention of using URLs as namespace identifiers must have created confusion without end. But at least XHTML has an extension mechanism &#8211; only that Microsoft never started supporting it. Why is there no consideration to do something similar with non-XML HTML5? Is using divs with strange attributes really better than using additional vocabularies in HTML? (RDFa is also a hack in this respect IMO, but at least it can accomodate extension vocabularies in a decentralized and conflict-free fashion. Before tossing that out of the window, an attempt should be made of doing namespaces in a clearer fashion, if URNs are considered to be too complicated).</p>
<p>I really don&#8217;t understand this whole aspect of HTML5. Yes, the W3C XHTML stuff was over-engineered and sometimes far away from reality. Yes, they put the bar a bit too high and so the transition never happened. </p>
<p>But baking every possible use case into one core vocabulary won&#8217;t do either.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Schoschie</title>
		<link>http://www.webstandards.org/2009/05/13/interview-with-ian-hickson-editor-of-the-html-5-specification/comment-page-1/#comment-75623</link>
		<dc:creator>Schoschie</dc:creator>
		<pubDate>Thu, 04 Jun 2009 13:49:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/?p=1726#comment-75623</guid>
		<description>Dammit, now you spoiled Fight Club for me.</description>
		<content:encoded><![CDATA[<p>Dammit, now you spoiled Fight Club for me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dominic Shiells</title>
		<link>http://www.webstandards.org/2009/05/13/interview-with-ian-hickson-editor-of-the-html-5-specification/comment-page-1/#comment-75605</link>
		<dc:creator>Dominic Shiells</dc:creator>
		<pubDate>Sat, 30 May 2009 22:27:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/?p=1726#comment-75605</guid>
		<description>With the spec is there any examples of the code to see how it is used in a practical format!
Dom</description>
		<content:encoded><![CDATA[<p>With the spec is there any examples of the code to see how it is used in a practical format!<br />
Dom</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sandra</title>
		<link>http://www.webstandards.org/2009/05/13/interview-with-ian-hickson-editor-of-the-html-5-specification/comment-page-1/#comment-75562</link>
		<dc:creator>Sandra</dc:creator>
		<pubDate>Wed, 27 May 2009 15:09:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/?p=1726#comment-75562</guid>
		<description>Flash is a &quot;common cross-browser extension&quot;? Sure, a common, non-free implementantation (with variants and ports between browsers and platform).

If Gnash or other non-Flash flash implementations were to take off, we&#039;d see the same slowdown as between browser implementors today.

I don&#039;t have Flash installed. I will install a good HTML 5 implementation.

I don&#039;t want to lock my works in a platform that&#039;s basically controlled by a single restricted-use, restricted-modification implementation. If Flash were DSFG-free, it&#039;d be back in the running.</description>
		<content:encoded><![CDATA[<p>Flash is a &#8220;common cross-browser extension&#8221;? Sure, a common, non-free implementantation (with variants and ports between browsers and platform).</p>
<p>If Gnash or other non-Flash flash implementations were to take off, we&#8217;d see the same slowdown as between browser implementors today.</p>
<p>I don&#8217;t have Flash installed. I will install a good HTML 5 implementation.</p>
<p>I don&#8217;t want to lock my works in a platform that&#8217;s basically controlled by a single restricted-use, restricted-modification implementation. If Flash were DSFG-free, it&#8217;d be back in the running.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hamranhansenhansen</title>
		<link>http://www.webstandards.org/2009/05/13/interview-with-ian-hickson-editor-of-the-html-5-specification/comment-page-1/#comment-75536</link>
		<dc:creator>Hamranhansenhansen</dc:creator>
		<pubDate>Tue, 26 May 2009 21:24:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/?p=1726#comment-75536</guid>
		<description>&gt; I think if we’re talking about conflating
&gt; structure and behaviour

Structure and behavior is already conflated in HTML 4. You can separate them as much as you like in your own applications. HTML 5 is not forcing your hand either way.

&gt; [Flash]

I started working with Flash in 1997 and it frustrates me that things I could do then easily in Flash are still either hard to do or basically impossible on the Web.

However, Flash is not now and has never been part of the World Wide Web. The Web is an application of the Internet, same as Flash. They&#039;re peers. The browser and Flash Player are 2 separate apps pretending to be one because Windows still doesn&#039;t have its own MPEG-4 player.

WebKit is just a few megabytes, and it runs on Intel, PowerPC, and ARM with industry-leading performance. And it&#039;s free and open source and used by Apple, Google, Nokia, Blackberry, Palm, and others. Mobiles have MPEG-4 decoder chips. There is no need for Flash on mobiles. If there was, it would already be there.</description>
		<content:encoded><![CDATA[<p>&gt; I think if we’re talking about conflating<br />
&gt; structure and behaviour</p>
<p>Structure and behavior is already conflated in HTML 4. You can separate them as much as you like in your own applications. HTML 5 is not forcing your hand either way.</p>
<p>&gt; [Flash]</p>
<p>I started working with Flash in 1997 and it frustrates me that things I could do then easily in Flash are still either hard to do or basically impossible on the Web.</p>
<p>However, Flash is not now and has never been part of the World Wide Web. The Web is an application of the Internet, same as Flash. They&#8217;re peers. The browser and Flash Player are 2 separate apps pretending to be one because Windows still doesn&#8217;t have its own MPEG-4 player.</p>
<p>WebKit is just a few megabytes, and it runs on Intel, PowerPC, and ARM with industry-leading performance. And it&#8217;s free and open source and used by Apple, Google, Nokia, Blackberry, Palm, and others. Mobiles have MPEG-4 decoder chips. There is no need for Flash on mobiles. If there was, it would already be there.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic page generated in 0.320 seconds. -->
<!-- Cached page generated by WP-Super-Cache on 2013-05-02 11:45:26 -->