<?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"
	>
<channel>
	<title>Comments on: New HTML Working Group</title>
	<atom:link href="http://theryanking.com/entries/2006/10/27/new-html-working-group/feed/" rel="self" type="application/rss+xml" />
	<link>http://theryanking.com/entries/2006/10/27/new-html-working-group/</link>
	<description>Music and Technology, but NO TECHNO!</description>
	<pubDate>Sat, 30 Aug 2008 06:35:39 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: The Web Standards Fluster Cuck - Alex Barnett blog</title>
		<link>http://theryanking.com/entries/2006/10/27/new-html-working-group/#comment-84762</link>
		<dc:creator>The Web Standards Fluster Cuck - Alex Barnett blog</dc:creator>
		<pubDate>Tue, 14 Aug 2007 02:45:27 +0000</pubDate>
		<guid isPermaLink="false">http://theryanking.com/blog/archives/2006/10/27/new-html-working-group/#comment-84762</guid>
		<description>[...] The Web Standards Fluster Cuck Clucking bell, Molly Holzshlag really has kicked the web standards&#160;beehive with&#160;a blog&#160;post expressing her great discontent with the W3C and WaSP. Now, before you head off and read the post and the 60+ comments, here's a bit of background on why I find this post of interest (and rather depressing): I've been following Molly's work for a while now. She first came on to my radar when after providing an update on the progress made between the Microsoft IE, VS and .NET teams and the Web Standards Project (WaSP). That was in 2005. Then in January 2007,&#160;I noted Molly's announcement that&#160;she had left WASP&#160;to join the IE team on a contract basis to work on standards and interoperability issues. I was pleased to see the IE team was making a real effort. Entirely seperately, but not entirely, in October of 2006 Tim Berners-Lee called for the reinvention of HTML. His call to action&#160;caused a bit of a hoo-ha at the time. What's that got to do with Molly? Well, as noted, some of the reactions to&#160;TBL's post varied from skepticism, to 'About time!'&#160;- and here's the connection with Molly's latest post&#160;- to&#160; what role the WHATWG&#160;will play in what presumably&#160;could&#160;be a competing effort to the HTML 5 (or XHTML5) spec in progress&#160;at the time.&#160;However, I was pleased to hear TBL's public calling for progress and hoped we might see some of&#160;this progrss&#160;after HTML's 8-year stagnation. Then in July 2007, we had the news that HTML5 was being considered by the W3C. Confused? You should be. So&#160;after&#160;my ridiculously inadequate backgrounder, you can now go ahead and read Molly's post, along with the contributions be&#160;the&#160;cast&#160;of&#160;characters (the commenters), some of whom are&#160;affiliated with various competing factions wrestling with the future of web&#160;standards and HTML, who&#160;somehow manage to converge&#160;the various threads&#160;(now including a Fear of Air, the Semantic Web, microformats, Silverlight, XML, community, accessibility, transparency&#160;and who-knows-what-else)&#160;into what looks like a complete political mess (read: fluster cuck). Yes, it is&#160;depressing,, but such is the business of web standards agreement.&#160;A messy business indeed...There's even a&#160;YouTube video covering the drama - HTML5 trailer - Find your Hero. - Thanks to Thomas Vander Wal for the link to Molly's post. &#160;  Posted: Aug 13 2007, 06:58 PM by alexbarnett &#124; with no comments Filed under: Web, microformats, Programming, VisualStudio, .NET, Internet, crap, semanticweb, XML, HTML, Adobe, IE, Apollo, community, silverlight, HTML5 [...]</description>
		<content:encoded><![CDATA[<p>[...] The Web Standards Fluster Cuck Clucking bell, Molly Holzshlag really has kicked the web standards&nbsp;beehive with&nbsp;a blog&nbsp;post expressing her great discontent with the W3C and WaSP. Now, before you head off and read the post and the 60+ comments, here&#8217;s a bit of background on why I find this post of interest (and rather depressing): I&#8217;ve been following Molly&#8217;s work for a while now. She first came on to my radar when after providing an update on the progress made between the Microsoft IE, VS and .NET teams and the Web Standards Project (WaSP). That was in 2005. Then in January 2007,&nbsp;I noted Molly&#8217;s announcement that&nbsp;she had left WASP&nbsp;to join the IE team on a contract basis to work on standards and interoperability issues. I was pleased to see the IE team was making a real effort. Entirely seperately, but not entirely, in October of 2006 Tim Berners-Lee called for the reinvention of HTML. His call to action&nbsp;caused a bit of a hoo-ha at the time. What&#8217;s that got to do with Molly? Well, as noted, some of the reactions to&nbsp;TBL&#8217;s post varied from skepticism, to &#8216;About time!&#8217;&nbsp;- and here&#8217;s the connection with Molly&#8217;s latest post&nbsp;- to&nbsp; what role the WHATWG&nbsp;will play in what presumably&nbsp;could&nbsp;be a competing effort to the HTML 5 (or XHTML5) spec in progress&nbsp;at the time.&nbsp;However, I was pleased to hear TBL&#8217;s public calling for progress and hoped we might see some of&nbsp;this progrss&nbsp;after HTML&#8217;s 8-year stagnation. Then in July 2007, we had the news that HTML5 was being considered by the W3C. Confused? You should be. So&nbsp;after&nbsp;my ridiculously inadequate backgrounder, you can now go ahead and read Molly&#8217;s post, along with the contributions be&nbsp;the&nbsp;cast&nbsp;of&nbsp;characters (the commenters), some of whom are&nbsp;affiliated with various competing factions wrestling with the future of web&nbsp;standards and HTML, who&nbsp;somehow manage to converge&nbsp;the various threads&nbsp;(now including a Fear of Air, the Semantic Web, microformats, Silverlight, XML, community, accessibility, transparency&nbsp;and who-knows-what-else)&nbsp;into what looks like a complete political mess (read: fluster cuck). Yes, it is&nbsp;depressing,, but such is the business of web standards agreement.&nbsp;A messy business indeed&#8230;There&#8217;s even a&nbsp;YouTube video covering the drama - HTML5 trailer - Find your Hero. - Thanks to Thomas Vander Wal for the link to Molly&#8217;s post. &nbsp;  Posted: Aug 13 2007, 06:58 PM by alexbarnett | with no comments Filed under: Web, microformats, Programming, VisualStudio, .NET, Internet, crap, semanticweb, XML, HTML, Adobe, IE, Apollo, community, silverlight, HTML5 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Boris</title>
		<link>http://theryanking.com/entries/2006/10/27/new-html-working-group/#comment-28198</link>
		<dc:creator>Boris</dc:creator>
		<pubDate>Tue, 31 Oct 2006 04:41:12 +0000</pubDate>
		<guid isPermaLink="false">http://theryanking.com/blog/archives/2006/10/27/new-html-working-group/#comment-28198</guid>
		<description>Joe, this line of questioning reminds me of &lt;a href="http://youtube.com/watch?v=I71ha4T4rUI" rel="nofollow"&gt;that Jon Stewart bit about how Fox and CNN use question marks to not really ask anything pertinent but rather spread misinformation&lt;/a&gt;.

(I'd leave a choice quote from it here but refrain out of respect... ;)</description>
		<content:encoded><![CDATA[<p>Joe, this line of questioning reminds me of <a href="http://youtube.com/watch?v=I71ha4T4rUI" rel="nofollow">that Jon Stewart bit about how Fox and CNN use question marks to not really ask anything pertinent but rather spread misinformation</a>.</p>
<p>(I&#8217;d leave a choice quote from it here but refrain out of respect&#8230; ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karl Dubost</title>
		<link>http://theryanking.com/entries/2006/10/27/new-html-working-group/#comment-28196</link>
		<dc:creator>Karl Dubost</dc:creator>
		<pubDate>Tue, 31 Oct 2006 04:23:44 +0000</pubDate>
		<guid isPermaLink="false">http://theryanking.com/blog/archives/2006/10/27/new-html-working-group/#comment-28196</guid>
		<description>Hi Joe,

The W3C can give you the reason that is announced in Tim's message. People and community asked for it. It doesn't come out of the hat. The next step is to have the charters reviewed, to maximize the participation, browser developers have been positively responsive so far with for sure comments, but that is part of the game. And something that everyone tend to forget, it is said "plan to charter", which means in plain English (far better than my usual broken prose) that it is not yet created.

About WHATWG, I can't speak for them. At least for some browser developers, they stated positive    position (look for example at www-html for public statements). Just something, we can notice. WHATWG has already transfered part of its work to W3C in the WebAPI WG for example.

There are also issues with IPs. Having a legal framework where you can guarantee that there will not be patents coming to bite you later on is important to have stability for the final developers and users. Yes that's not really fun, but we have to deal with this in our world.</description>
		<content:encoded><![CDATA[<p>Hi Joe,</p>
<p>The W3C can give you the reason that is announced in Tim&#8217;s message. People and community asked for it. It doesn&#8217;t come out of the hat. The next step is to have the charters reviewed, to maximize the participation, browser developers have been positively responsive so far with for sure comments, but that is part of the game. And something that everyone tend to forget, it is said &#8220;plan to charter&#8221;, which means in plain English (far better than my usual broken prose) that it is not yet created.</p>
<p>About WHATWG, I can&#8217;t speak for them. At least for some browser developers, they stated positive    position (look for example at www-html for public statements). Just something, we can notice. WHATWG has already transfered part of its work to W3C in the WebAPI WG for example.</p>
<p>There are also issues with IPs. Having a legal framework where you can guarantee that there will not be patents coming to bite you later on is important to have stability for the final developers and users. Yes that&#8217;s not really fun, but we have to deal with this in our world.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Clark</title>
		<link>http://theryanking.com/entries/2006/10/27/new-html-working-group/#comment-28156</link>
		<dc:creator>Joe Clark</dc:creator>
		<pubDate>Mon, 30 Oct 2006 22:51:48 +0000</pubDate>
		<guid isPermaLink="false">http://theryanking.com/blog/archives/2006/10/27/new-html-working-group/#comment-28156</guid>
		<description>If we shouldn’t have multiple versions of HTML (we already do: 3.2, 4.0, 4.01; Strict, Transtional, Frameset), then why should we have multiple new HTML working groups?

Can the W3C give us reasons not to believe the announcement is a response to the fact that someone *other* than the W3C has been plausibly writing a spec?

If WHAT WG weren't doing a plausible job, would this new group have been announced?

Was it announced because the W3C cannot bear the thought of anyone other than the W3C defining the specs for the Web?

Is this not another attempt to assert a monopoly position, one that is rather doomed to fail and actually undermine the stated goals of the group? After all, W3C HTML 5 and WHAT WG “HTML5” cannot both exist and be supported, can they? (Whatever happens when we get to elements and attributes with identical names in both specs but different definitions – dl/dt/dd, for example?)</description>
		<content:encoded><![CDATA[<p>If we shouldn’t have multiple versions of HTML (we already do: 3.2, 4.0, 4.01; Strict, Transtional, Frameset), then why should we have multiple new HTML working groups?</p>
<p>Can the W3C give us reasons not to believe the announcement is a response to the fact that someone *other* than the W3C has been plausibly writing a spec?</p>
<p>If WHAT WG weren&#8217;t doing a plausible job, would this new group have been announced?</p>
<p>Was it announced because the W3C cannot bear the thought of anyone other than the W3C defining the specs for the Web?</p>
<p>Is this not another attempt to assert a monopoly position, one that is rather doomed to fail and actually undermine the stated goals of the group? After all, W3C HTML 5 and WHAT WG “HTML5” cannot both exist and be supported, can they? (Whatever happens when we get to elements and attributes with identical names in both specs but different definitions – dl/dt/dd, for example?)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: HTML Reloaded, World Web War 2.0 &#171; FrogBSD Blog</title>
		<link>http://theryanking.com/entries/2006/10/27/new-html-working-group/#comment-27834</link>
		<dc:creator>HTML Reloaded, World Web War 2.0 &#171; FrogBSD Blog</dc:creator>
		<pubDate>Sat, 28 Oct 2006 10:24:49 +0000</pubDate>
		<guid isPermaLink="false">http://theryanking.com/blog/archives/2006/10/27/new-html-working-group/#comment-27834</guid>
		<description>[...] 有一組不隸屬 W3C 的人員另組的 WHATWG，制定 HTML5/XHTML5, Web Form 2.0 一段時間了，發言人 Ian Hickson 表示 W3C 並未知會他們。 [...]</description>
		<content:encoded><![CDATA[<p>[...] 有一組不隸屬 W3C 的人員另組的 WHATWG，制定 HTML5/XHTML5, Web Form 2.0 一段時間了，發言人 Ian Hickson 表示 W3C 並未知會他們。 [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
