<?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: HTML 5 and reserved class names</title>
	<atom:link href="http://www.broken-links.com/2007/12/03/html-5-and-reserved-class-names/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.broken-links.com/2007/12/03/html-5-and-reserved-class-names/</link>
	<description>Thoughts on web development and technologies by Peter Gasston</description>
	<lastBuildDate>Sun, 07 Mar 2010 16:33:42 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: DAZ</title>
		<link>http://www.broken-links.com/2007/12/03/html-5-and-reserved-class-names/comment-page-1/#comment-21448</link>
		<dc:creator>DAZ</dc:creator>
		<pubDate>Fri, 21 Nov 2008 17:42:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.broken-links.com/2007/12/03/html-5-and-reserved-class-names/#comment-21448</guid>
		<description>Good post. I think this is the way forward. I also think it would be good if there were some place that we could reach a consensus on some class-name-conventions, such as the use of &#039;search&#039;, &#039;button&#039;, &#039;price&#039;, etc. Then if these get used widely then maybe they will be considered for the html5 spec.

DAZ</description>
		<content:encoded><![CDATA[<p>Good post. I think this is the way forward. I also think it would be good if there were some place that we could reach a consensus on some class-name-conventions, such as the use of ‘search’, ‘button’, ‘price’, etc. Then if these get used widely then maybe they will be considered for the html5 spec.</p>
<p>DAZ</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arjan</title>
		<link>http://www.broken-links.com/2007/12/03/html-5-and-reserved-class-names/comment-page-1/#comment-5298</link>
		<dc:creator>Arjan</dc:creator>
		<pubDate>Mon, 03 Dec 2007 22:31:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.broken-links.com/2007/12/03/html-5-and-reserved-class-names/#comment-5298</guid>
		<description>I don&#039;t see why using the &lt;code&gt;class&lt;/code&gt;-names and &lt;code&gt;id&lt;/code&gt;-values... It isn&#039;t very strict (I can also use another &lt;code&gt;class&lt;/code&gt;-name, and my code is still 100% valid). Reserved &lt;code&gt;class&lt;/code&gt;-names and &lt;code&gt;id&lt;/code&gt;-values: ok, but not for very structural elements within the page.

For now, I really recommend using the element names from the future &lt;abbr title=&quot;Hypertext Markup Language version 5&quot;&gt;HTML5&lt;/abbr&gt; as a &lt;code&gt;class&lt;/code&gt;-name or &lt;code&gt;id&lt;/code&gt;-value (depending on what kind of element).</description>
		<content:encoded><![CDATA[<p>I don’t see why using the <code>class</code>–names and <code>id</code>–values… It isn’t very strict (I can also use another <code>class</code>–name, and my code is still 100% valid). Reserved <code>class</code>–names and <code>id</code>–values: ok, but not for very structural elements within the page.</p>
<p>For now, I really recommend using the element names from the future <abbr title="Hypertext Markup Language version 5">HTML5</abbr> as a <code>class</code>–name or <code>id</code>–value (depending on what kind of element).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
