<?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: Taking a peak at HTML 5</title>
	<atom:link href="http://ajaxian.com/archives/taking-a-peak-at-html-5/feed" rel="self" type="application/rss+xml" />
	<link>http://ajaxian.com/archives/taking-a-peak-at-html-5</link>
	<description>Cleaning up the web with Ajax</description>
	<lastBuildDate>Thu, 17 May 2012 07:43:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Vance  Dubberly</title>
		<link>http://ajaxian.com/archives/taking-a-peak-at-html-5/comment-page-1#comment-259870</link>
		<dc:creator>Vance  Dubberly</dc:creator>
		<pubDate>Tue, 11 Dec 2007 05:13:14 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3091#comment-259870</guid>
		<description>there are a lot of things I like in the HTML 5 and some things ( like article, aside, and domain specific stuff that just give me the creeps ) but it doesn&#039;t give my any hope. Microsoft will just screw it up and we&#039;ll end up with the worst tag soup we&#039;ve ever had.</description>
		<content:encoded><![CDATA[<p>there are a lot of things I like in the HTML 5 and some things ( like article, aside, and domain specific stuff that just give me the creeps ) but it doesn&#8217;t give my any hope. Microsoft will just screw it up and we&#8217;ll end up with the worst tag soup we&#8217;ve ever had.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Trevor</title>
		<link>http://ajaxian.com/archives/taking-a-peak-at-html-5/comment-page-1#comment-259839</link>
		<dc:creator>Trevor</dc:creator>
		<pubDate>Mon, 10 Dec 2007 06:48:04 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3091#comment-259839</guid>
		<description>zero:

Div and span should just about cover it, eh?

Ajaxian.com: please do something about the tag filtering so that typed tags that aren&#039;t supported as comment markup get converted to something readable. Thanks!</description>
		<content:encoded><![CDATA[<p>zero:</p>
<p>Div and span should just about cover it, eh?</p>
<p>Ajaxian.com: please do something about the tag filtering so that typed tags that aren&#8217;t supported as comment markup get converted to something readable. Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: zero</title>
		<link>http://ajaxian.com/archives/taking-a-peak-at-html-5/comment-page-1#comment-259837</link>
		<dc:creator>zero</dc:creator>
		<pubDate>Sun, 09 Dec 2007 19:20:16 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3091#comment-259837</guid>
		<description>this is a bad standardization practice.  this may be the structure of most of the current web, but it won&#039;t be soon.  specific tags like &quot;&quot; and even &quot;&quot; (although i admit i kinda like that one), solidify current practices in the standard, which means the stardard will stale quickly among other things.

with such a fast moving/changing such as the web and certainly a slow moving standards practice,  KEEP IT GENERAL.  &quot;&quot; is not hell &quot;&quot; is a general division on the page.  a division of a game, article, blog, etc.

the HTML standard will only benefit from less tags, not more.</description>
		<content:encoded><![CDATA[<p>this is a bad standardization practice.  this may be the structure of most of the current web, but it won&#8217;t be soon.  specific tags like &#8220;&#8221; and even &#8220;&#8221; (although i admit i kinda like that one), solidify current practices in the standard, which means the stardard will stale quickly among other things.</p>
<p>with such a fast moving/changing such as the web and certainly a slow moving standards practice,  KEEP IT GENERAL.  &#8220;&#8221; is not hell &#8220;&#8221; is a general division on the page.  a division of a game, article, blog, etc.</p>
<p>the HTML standard will only benefit from less tags, not more.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Trevor</title>
		<link>http://ajaxian.com/archives/taking-a-peak-at-html-5/comment-page-1#comment-259835</link>
		<dc:creator>Trevor</dc:creator>
		<pubDate>Sun, 09 Dec 2007 16:53:48 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3091#comment-259835</guid>
		<description>&quot;they should introduce columns and page/tab too!&quot;

I think those are semantically covered with section and h. Presentationally, I don&#039;t think it&#039;s realistic or reasonable to overload HTML with those concepts, as HTML isn&#039;t supposed to carry any style connotations at all. If you wanted, say, CSS attributes that corresponded to those ideas (display: column; display: tab; etc), I might find that more compelling.</description>
		<content:encoded><![CDATA[<p>&#8220;they should introduce columns and page/tab too!&#8221;</p>
<p>I think those are semantically covered with section and h. Presentationally, I don&#8217;t think it&#8217;s realistic or reasonable to overload HTML with those concepts, as HTML isn&#8217;t supposed to carry any style connotations at all. If you wanted, say, CSS attributes that corresponded to those ideas (display: column; display: tab; etc), I might find that more compelling.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Damir Secki</title>
		<link>http://ajaxian.com/archives/taking-a-peak-at-html-5/comment-page-1#comment-259834</link>
		<dc:creator>Damir Secki</dc:creator>
		<pubDate>Sun, 09 Dec 2007 06:18:40 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3091#comment-259834</guid>
		<description>This new tags as many of you mentioned will not change a lot. Is just the HTML code will be somehow more readable (comprehensive) and maybe search engines will benefit in small amount. As for the real usefulness I don&#039;t see a big improvement. I am of idea if we are to introduce new standard we should make sure we implement some more (read useful) features. Video and audio are some of them.

and if they are introducing elements like header, footer and article they should introduce columns and page/tab too!</description>
		<content:encoded><![CDATA[<p>This new tags as many of you mentioned will not change a lot. Is just the HTML code will be somehow more readable (comprehensive) and maybe search engines will benefit in small amount. As for the real usefulness I don&#8217;t see a big improvement. I am of idea if we are to introduce new standard we should make sure we implement some more (read useful) features. Video and audio are some of them.</p>
<p>and if they are introducing elements like header, footer and article they should introduce columns and page/tab too!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Trevor</title>
		<link>http://ajaxian.com/archives/taking-a-peak-at-html-5/comment-page-1#comment-259832</link>
		<dc:creator>Trevor</dc:creator>
		<pubDate>Sat, 08 Dec 2007 19:56:24 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3091#comment-259832</guid>
		<description>&quot;This is the layout of 90% of websites, and itâ€™s an absurd nightmare under CSS. Sure, CSS could be fixed, but Iâ€™m not holding my breath on that either.&quot;

You would still need CSS to render that layout. I&#039;m fairly sure with default styles each element in the example is a standard box-level element. CSS isn&#039;t in need of fixing (though some implementations need some work). It&#039;s already extremely powerful as is.</description>
		<content:encoded><![CDATA[<p>&#8220;This is the layout of 90% of websites, and itâ€™s an absurd nightmare under CSS. Sure, CSS could be fixed, but Iâ€™m not holding my breath on that either.&#8221;</p>
<p>You would still need CSS to render that layout. I&#8217;m fairly sure with default styles each element in the example is a standard box-level element. CSS isn&#8217;t in need of fixing (though some implementations need some work). It&#8217;s already extremely powerful as is.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin</title>
		<link>http://ajaxian.com/archives/taking-a-peak-at-html-5/comment-page-1#comment-259829</link>
		<dc:creator>Martin</dc:creator>
		<pubDate>Sat, 08 Dec 2007 14:03:15 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3091#comment-259829</guid>
		<description>An article tag will not help you styling the page any better than a div class=&quot;article&quot;.</description>
		<content:encoded><![CDATA[<p>An article tag will not help you styling the page any better than a div class=&#8221;article&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PixyMisa</title>
		<link>http://ajaxian.com/archives/taking-a-peak-at-html-5/comment-page-1#comment-259825</link>
		<dc:creator>PixyMisa</dc:creator>
		<pubDate>Sat, 08 Dec 2007 10:47:48 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3091#comment-259825</guid>
		<description>Gimme gimme gimme NOW!

This is the layout of 90% of websites, and it&#039;s an absurd nightmare under CSS.  Sure, CSS could be fixed, but I&#039;m not holding my breath on that either.</description>
		<content:encoded><![CDATA[<p>Gimme gimme gimme NOW!</p>
<p>This is the layout of 90% of websites, and it&#8217;s an absurd nightmare under CSS.  Sure, CSS could be fixed, but I&#8217;m not holding my breath on that either.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chad</title>
		<link>http://ajaxian.com/archives/taking-a-peak-at-html-5/comment-page-1#comment-259821</link>
		<dc:creator>Chad</dc:creator>
		<pubDate>Sat, 08 Dec 2007 07:30:43 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3091#comment-259821</guid>
		<description>What is html? j/k</description>
		<content:encoded><![CDATA[<p>What is html? j/k</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: eyelidlessness</title>
		<link>http://ajaxian.com/archives/taking-a-peak-at-html-5/comment-page-1#comment-259820</link>
		<dc:creator>eyelidlessness</dc:creator>
		<pubDate>Sat, 08 Dec 2007 04:34:59 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3091#comment-259820</guid>
		<description>I&#039;m sure everyone who objects to the new tags realizes that they aren&#039;t *required*. You can use generic section tags for anything that doesn&#039;t conform to one of the more specific tags. I can&#039;t imagine the harm in more descriptive tags unless there are simply too many of them. But all of the ones in the example are extraordinarily common in web documents today.

Whoever said that web documents are less common than web-application UIs is just wrong. Most of what I&#039;m seeing is that there is a lot of grey area between the two. But even web-app-like sites that are popular also present a lot of public data as documents.</description>
		<content:encoded><![CDATA[<p>I&#8217;m sure everyone who objects to the new tags realizes that they aren&#8217;t *required*. You can use generic section tags for anything that doesn&#8217;t conform to one of the more specific tags. I can&#8217;t imagine the harm in more descriptive tags unless there are simply too many of them. But all of the ones in the example are extraordinarily common in web documents today.</p>
<p>Whoever said that web documents are less common than web-application UIs is just wrong. Most of what I&#8217;m seeing is that there is a lot of grey area between the two. But even web-app-like sites that are popular also present a lot of public data as documents.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fretlessjazz</title>
		<link>http://ajaxian.com/archives/taking-a-peak-at-html-5/comment-page-1#comment-259818</link>
		<dc:creator>fretlessjazz</dc:creator>
		<pubDate>Sat, 08 Dec 2007 02:59:06 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3091#comment-259818</guid>
		<description>HTML 5 is sounding more like Perl 6 each time I read about it.  My guess on a deliverability date?  2015, minimum.  By then, the web will mean something completely different than it does today (compare 2007 to 1999).</description>
		<content:encoded><![CDATA[<p>HTML 5 is sounding more like Perl 6 each time I read about it.  My guess on a deliverability date?  2015, minimum.  By then, the web will mean something completely different than it does today (compare 2007 to 1999).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pwb</title>
		<link>http://ajaxian.com/archives/taking-a-peak-at-html-5/comment-page-1#comment-259814</link>
		<dc:creator>pwb</dc:creator>
		<pubDate>Fri, 07 Dec 2007 22:39:18 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3091#comment-259814</guid>
		<description>I think it&#039;s a horrible idea. HTML should not be suggesting page components like that? That&#039;s such a narrow view of the web.</description>
		<content:encoded><![CDATA[<p>I think it&#8217;s a horrible idea. HTML should not be suggesting page components like that? That&#8217;s such a narrow view of the web.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gsteff</title>
		<link>http://ajaxian.com/archives/taking-a-peak-at-html-5/comment-page-1#comment-259811</link>
		<dc:creator>gsteff</dc:creator>
		<pubDate>Fri, 07 Dec 2007 20:12:48 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3091#comment-259811</guid>
		<description>This is  a positive development, but it continues the fiction that HTML is a language for producing a semantic description of documents, instead of a language for describing application user interfaces, which is much closer to the truth nowadays.  A language revision focused on that would include ideas from web forms 2.0.  This will cut down on div-itis some, and help improve search engine results, but does diddly for the actual user experience.  Still, judged by its semantic intention, this is a welcome improvement (though I wish they&#039;d put tags in for form field errors and descriptions, like they have for labels).</description>
		<content:encoded><![CDATA[<p>This is  a positive development, but it continues the fiction that HTML is a language for producing a semantic description of documents, instead of a language for describing application user interfaces, which is much closer to the truth nowadays.  A language revision focused on that would include ideas from web forms 2.0.  This will cut down on div-itis some, and help improve search engine results, but does diddly for the actual user experience.  Still, judged by its semantic intention, this is a welcome improvement (though I wish they&#8217;d put tags in for form field errors and descriptions, like they have for labels).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: davidwalsh</title>
		<link>http://ajaxian.com/archives/taking-a-peak-at-html-5/comment-page-1#comment-259809</link>
		<dc:creator>davidwalsh</dc:creator>
		<pubDate>Fri, 07 Dec 2007 19:33:22 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3091#comment-259809</guid>
		<description>I don&#039;t understand why they&#039;re specifying tag names at all.  Why not simply let us create the tag name and style it using CSS ourselves?  Obviously a video tag has special capabilities, but I don&#039;t see why we need specified structure tags.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t understand why they&#8217;re specifying tag names at all.  Why not simply let us create the tag name and style it using CSS ourselves?  Obviously a video tag has special capabilities, but I don&#8217;t see why we need specified structure tags.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Kimber</title>
		<link>http://ajaxian.com/archives/taking-a-peak-at-html-5/comment-page-1#comment-259807</link>
		<dc:creator>Richard Kimber</dc:creator>
		<pubDate>Fri, 07 Dec 2007 18:09:20 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3091#comment-259807</guid>
		<description>I like the article, header and footer tags. Not convinced on the aside tag, maybe too descriptive?</description>
		<content:encoded><![CDATA[<p>I like the article, header and footer tags. Not convinced on the aside tag, maybe too descriptive?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric</title>
		<link>http://ajaxian.com/archives/taking-a-peak-at-html-5/comment-page-1#comment-259805</link>
		<dc:creator>Eric</dc:creator>
		<pubDate>Fri, 07 Dec 2007 17:40:23 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3091#comment-259805</guid>
		<description>Hmm, descriptive markup yes.  But, this doesn&#039;t seem like such a good idea - naming markup tags based on what you want them to contain.  Just like &#039;table&#039; was/is used for content that is not tabular these tags may become less descriptive because their too specific.  After all - header, footer, article, etc - they&#039;re all types of sections or divisions.  Isn&#039;t there a better way to describe them in a meaningful, robust, and flexible manner?  The article section of a web site should be in a  or  tag with some attribute signifying what type of section it is.</description>
		<content:encoded><![CDATA[<p>Hmm, descriptive markup yes.  But, this doesn&#8217;t seem like such a good idea &#8211; naming markup tags based on what you want them to contain.  Just like &#8216;table&#8217; was/is used for content that is not tabular these tags may become less descriptive because their too specific.  After all &#8211; header, footer, article, etc &#8211; they&#8217;re all types of sections or divisions.  Isn&#8217;t there a better way to describe them in a meaningful, robust, and flexible manner?  The article section of a web site should be in a  or  tag with some attribute signifying what type of section it is.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keith</title>
		<link>http://ajaxian.com/archives/taking-a-peak-at-html-5/comment-page-1#comment-259803</link>
		<dc:creator>Keith</dc:creator>
		<pubDate>Fri, 07 Dec 2007 17:21:01 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3091#comment-259803</guid>
		<description>And I was being nice, I didn&#039;t even point out that it&#039;s Jack O&#039;Neill. :D</description>
		<content:encoded><![CDATA[<p>And I was being nice, I didn&#8217;t even point out that it&#8217;s Jack O&#8217;Neill. :D</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keith</title>
		<link>http://ajaxian.com/archives/taking-a-peak-at-html-5/comment-page-1#comment-259802</link>
		<dc:creator>Keith</dc:creator>
		<pubDate>Fri, 07 Dec 2007 17:19:12 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3091#comment-259802</guid>
		<description>Cmon guys. Peak = pinnacle, top of a mountain. Peek = short look.

I&#039;m not a spelling and grammar nazi or anything, but at least try to get the headline right.  :)</description>
		<content:encoded><![CDATA[<p>Cmon guys. Peak = pinnacle, top of a mountain. Peek = short look.</p>
<p>I&#8217;m not a spelling and grammar nazi or anything, but at least try to get the headline right.  :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SZRimaging</title>
		<link>http://ajaxian.com/archives/taking-a-peak-at-html-5/comment-page-1#comment-259797</link>
		<dc:creator>SZRimaging</dc:creator>
		<pubDate>Fri, 07 Dec 2007 15:55:36 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3091#comment-259797</guid>
		<description>I have to agree with Will on this one. The Header/Footer markup seems like an excellent thing for markup. I find the &quot;aside&quot; a little...ummm...weird, but I can live with it. From the sounds of it, they aren&#039;t getting rid of the old tags, just adding new, more descriptive ones. I am really looking forward to the video tags and their solutions for those. Although, I think I could do without the audio tag.</description>
		<content:encoded><![CDATA[<p>I have to agree with Will on this one. The Header/Footer markup seems like an excellent thing for markup. I find the &#8220;aside&#8221; a little&#8230;ummm&#8230;weird, but I can live with it. From the sounds of it, they aren&#8217;t getting rid of the old tags, just adding new, more descriptive ones. I am really looking forward to the video tags and their solutions for those. Although, I think I could do without the audio tag.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Will Peavy</title>
		<link>http://ajaxian.com/archives/taking-a-peak-at-html-5/comment-page-1#comment-259796</link>
		<dc:creator>Will Peavy</dc:creator>
		<pubDate>Fri, 07 Dec 2007 15:35:39 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3091#comment-259796</guid>
		<description>HTML 5 looks like a move towards much more descriptive markup. I&#039;m 100% in favor of where the draft is heading</description>
		<content:encoded><![CDATA[<p>HTML 5 looks like a move towards much more descriptive markup. I&#8217;m 100% in favor of where the draft is heading</p>
]]></content:encoded>
	</item>
</channel>
</rss>

