<?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: Reservations about HTML5</title>
	<atom:link href="http://coffeeonthekeyboard.com/reservations-about-html5-271/feed/" rel="self" type="application/rss+xml" />
	<link>http://coffeeonthekeyboard.com/reservations-about-html5-271/</link>
	<description>by James Socol</description>
	<lastBuildDate>Mon, 08 Mar 2010 17:02:21 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: James</title>
		<link>http://coffeeonthekeyboard.com/reservations-about-html5-271/comment-page-1/#comment-3996</link>
		<dc:creator>James</dc:creator>
		<pubDate>Sun, 09 Aug 2009 16:16:42 +0000</pubDate>
		<guid isPermaLink="false">http://coffeeonthekeyboard.com/?p=271#comment-3996</guid>
		<description>From the same document you linked: &quot;For example, a blog post would be marked up using article, a chapter using section...&quot;

My point is that &lt;article&gt; and &lt;aside&gt; are only necessary for one type of document on the web, a blog post or magazine article, so adding a tag for that seems excessive, and shows &lt;em&gt;preference&lt;/em&gt; for those formats. While &lt;section&gt; is no more meaningful than &lt;div&gt;, so adding it is unnecessary.

I did try to give an example of an extensible method of semantically identifying page elements which would be meaningful to User Agents (browsers and search engines). While it&#039;s certainly not the best plan in the world, I do recognize the issue.</description>
		<content:encoded><![CDATA[<p>From the same document you linked: &#8220;For example, a blog post would be marked up using article, a chapter using section&#8230;&#8221;</p>
<p>My point is that &lt;article&gt; and &lt;aside&gt; are only necessary for one type of document on the web, a blog post or magazine article, so adding a tag for that seems excessive, and shows <em>preference</em> for those formats. While &lt;section&gt; is no more meaningful than &lt;div&gt;, so adding it is unnecessary.</p>
<p>I did try to give an example of an extensible method of semantically identifying page elements which would be meaningful to User Agents (browsers and search engines). While it&#8217;s certainly not the best plan in the world, I do recognize the issue.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Donovan van der Roest</title>
		<link>http://coffeeonthekeyboard.com/reservations-about-html5-271/comment-page-1/#comment-3993</link>
		<dc:creator>Donovan van der Roest</dc:creator>
		<pubDate>Sun, 09 Aug 2009 11:25:34 +0000</pubDate>
		<guid isPermaLink="false">http://coffeeonthekeyboard.com/?p=271#comment-3993</guid>
		<description>I am not sure I see your point here. HTML5 adds additional tags that give meaning to what we developers put unto it. These are additional elements on top of the still existing div (http://dev.w3.org/html5/spec/Overview.html#the-div-element)&quot; and span (http://dev.w3.org/html5/spec/Overview.html#the-span-element) elements.
So if you need something different, use those. 

Adding a way in which everybody can assign meaning to certain tags will create the opposite effect. Browsers will have no clue what it all means and search engines will not even bother trying to make sense of it because it will be impossible for them to do so. The HTML5 spec however creates a standard which can be followed by search engines and browsers without losing flexibility.</description>
		<content:encoded><![CDATA[<p>I am not sure I see your point here. HTML5 adds additional tags that give meaning to what we developers put unto it. These are additional elements on top of the still existing div (<a href="http://dev.w3.org/html5/spec/Overview.html#the-div-element)" rel="nofollow">http://dev.w3.org/html5/spec/Overview.html#the-div-element)</a>&#8221; and span (<a href="http://dev.w3.org/html5/spec/Overview.html#the-span-element" rel="nofollow">http://dev.w3.org/html5/spec/Overview.html#the-span-element</a>) elements.<br />
So if you need something different, use those. </p>
<p>Adding a way in which everybody can assign meaning to certain tags will create the opposite effect. Browsers will have no clue what it all means and search engines will not even bother trying to make sense of it because it will be impossible for them to do so. The HTML5 spec however creates a standard which can be followed by search engines and browsers without losing flexibility.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
