<?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: Semantic navigation with the nav element</title>
	<atom:link href="http://html5doctor.com/nav-element/feed/" rel="self" type="application/rss+xml" />
	<link>http://html5doctor.com/nav-element/</link>
	<description>helping you implement HTML5 today</description>
	<lastBuildDate>Mon, 06 Feb 2012 20:26:52 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Carbonize</title>
		<link>http://html5doctor.com/nav-element/#comment-21051</link>
		<dc:creator>Carbonize</dc:creator>
		<pubDate>Fri, 23 Dec 2011 17:40:02 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=473#comment-21051</guid>
		<description>Slightly off topic but given that you are using HTML 5 on this fsite such as the doctype and nav element why are you still using the type attribute for the style and script tags? Neither of these is necessary in HTML 5 as the browser will treat them as CSS and JavaScript by default.</description>
		<content:encoded><![CDATA[<p>Slightly off topic but given that you are using HTML 5 on this fsite such as the doctype and nav element why are you still using the type attribute for the style and script tags? Neither of these is necessary in HTML 5 as the browser will treat them as CSS and JavaScript by default.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mandy</title>
		<link>http://html5doctor.com/nav-element/#comment-18399</link>
		<dc:creator>mandy</dc:creator>
		<pubDate>Wed, 09 Nov 2011 23:12:57 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=473#comment-18399</guid>
		<description>I had the same question regarding breadcrumbs as koder above, but I liked his second option so I&#039;m going to use that.</description>
		<content:encoded><![CDATA[<p>I had the same question regarding breadcrumbs as koder above, but I liked his second option so I&#8217;m going to use that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Toke Voltelen</title>
		<link>http://html5doctor.com/nav-element/#comment-18394</link>
		<dc:creator>Toke Voltelen</dc:creator>
		<pubDate>Wed, 09 Nov 2011 16:23:54 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=473#comment-18394</guid>
		<description>Well. The issue about having the &lt;nav&gt; element being an actual list, is that, in it&#039;s current state it is an area wherein navigational items are placed. No where is it said that the links needs to be in a list, but most developers do this for presentational reasons when there is no styles + accessibility.

I don&#039;t mind that the &lt;nav&gt; is an area-tag rather than a list-tag, as it makes sense to mark up an area that is related for navigation. But the definition of how to use the tag pretty vague. I don&#039;t understand why and bunch of links to key pages in a website in the footer, is less a navigation than the main menu in the header. It is still navigation to important places on the website.

In my oppinion the &lt;nav&gt; should be used for areas that allow the user navigate the site. Clusters of internal links along with descriptive texts and headers. Breadcrumb being an excellent example, as well as the footer links.</description>
		<content:encoded><![CDATA[<p>Well. The issue about having the &lt;nav&gt; element being an actual list, is that, in it&#8217;s current state it is an area wherein navigational items are placed. No where is it said that the links needs to be in a list, but most developers do this for presentational reasons when there is no styles + accessibility.</p>
<p>I don&#8217;t mind that the &lt;nav&gt; is an area-tag rather than a list-tag, as it makes sense to mark up an area that is related for navigation. But the definition of how to use the tag pretty vague. I don&#8217;t understand why and bunch of links to key pages in a website in the footer, is less a navigation than the main menu in the header. It is still navigation to important places on the website.</p>
<p>In my oppinion the &lt;nav&gt; should be used for areas that allow the user navigate the site. Clusters of internal links along with descriptive texts and headers. Breadcrumb being an excellent example, as well as the footer links.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hanamiti</title>
		<link>http://html5doctor.com/nav-element/#comment-18275</link>
		<dc:creator>Hanamiti</dc:creator>
		<pubDate>Tue, 01 Nov 2011 12:12:32 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=473#comment-18275</guid>
		<description>Man, thank you for the explanatory article :) I am slowly migrating from XHTML to HTML5 markup, and you were of real help! Cudos.</description>
		<content:encoded><![CDATA[<p>Man, thank you for the explanatory article <img src='http://html5doctor.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  I am slowly migrating from XHTML to HTML5 markup, and you were of real help! Cudos.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sandy Campbell</title>
		<link>http://html5doctor.com/nav-element/#comment-17817</link>
		<dc:creator>Sandy Campbell</dc:creator>
		<pubDate>Thu, 29 Sep 2011 03:03:06 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=473#comment-17817</guid>
		<description>Sorry, I didn&#039;t see the note about using brackets, so all my tags were stripped from my previous comment:

When I Googled “nav vs menu”, I didn’t realize how contentious an issue this is! But I actually prefer &#039;menu&#039; over &#039;nav&#039; because the markup for &#039;menu&#039; is simpler. The &#039;nav&#039; tag requires that your list items are wrapped with &#039;ul&#039;. It’s no different than using a &#039;div&#039; tag. But the &#039;menu&#039; tag accepts list items without needing a &#039;ul&#039; wrapper. In essence, &#039;menu&#039; replaces &#039;ul&#039; when you want to make a navigational list. It verifies and displays correctly as a list when CSS is disabled. Whatever styles you have now for &#039;ul&#039; will work for &#039;menu&#039;.</description>
		<content:encoded><![CDATA[<p>Sorry, I didn&#8217;t see the note about using brackets, so all my tags were stripped from my previous comment:</p>
<p>When I Googled “nav vs menu”, I didn’t realize how contentious an issue this is! But I actually prefer &#8216;menu&#8217; over &#8216;nav&#8217; because the markup for &#8216;menu&#8217; is simpler. The &#8216;nav&#8217; tag requires that your list items are wrapped with &#8216;ul&#8217;. It’s no different than using a &#8216;div&#8217; tag. But the &#8216;menu&#8217; tag accepts list items without needing a &#8216;ul&#8217; wrapper. In essence, &#8216;menu&#8217; replaces &#8216;ul&#8217; when you want to make a navigational list. It verifies and displays correctly as a list when CSS is disabled. Whatever styles you have now for &#8216;ul&#8217; will work for &#8216;menu&#8217;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sandy Campbell</title>
		<link>http://html5doctor.com/nav-element/#comment-17816</link>
		<dc:creator>Sandy Campbell</dc:creator>
		<pubDate>Thu, 29 Sep 2011 02:58:02 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=473#comment-17816</guid>
		<description>When I Googled &quot;nav vs menu&quot;, I didn&#039;t realize how contentious an issue this is! But I actually prefer  over  because the markup for  is simpler. The  tag requires that your  list items are wrapped with . It&#039;s no different than using a  tag. But the  tag accepts  list items without needing a  wrapper. In essence,  replaces  when you want to make a navigational list. It verifies and displays correctly as a list when CSS is disabled. Whatever styles you have now for  will work for .</description>
		<content:encoded><![CDATA[<p>When I Googled &#8220;nav vs menu&#8221;, I didn&#8217;t realize how contentious an issue this is! But I actually prefer  over  because the markup for  is simpler. The  tag requires that your  list items are wrapped with . It&#8217;s no different than using a  tag. But the  tag accepts  list items without needing a  wrapper. In essence,  replaces  when you want to make a navigational list. It verifies and displays correctly as a list when CSS is disabled. Whatever styles you have now for  will work for .</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Inkfree</title>
		<link>http://html5doctor.com/nav-element/#comment-17157</link>
		<dc:creator>Inkfree</dc:creator>
		<pubDate>Sat, 13 Aug 2011 15:12:19 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=473#comment-17157</guid>
		<description>the &quot;nav&quot; element can now accept &lt;i&gt;any&lt;/i&gt; form of content as i can see &lt;a href=&quot;http://www.w3schools.com/html5/tag_nav.asp&quot; rel=&quot;nofollow&quot;&gt;here&lt;/a&gt; and &lt;a href=&quot;http://dev.w3.org/html5/spec/Overview.html#the-nav-element&quot; rel=&quot;nofollow&quot;&gt;here&lt;/a&gt;. I always look for discussions here and would love to know what the doctor has to say :) thanks</description>
		<content:encoded><![CDATA[<p>the &#8220;nav&#8221; element can now accept <i>any</i> form of content as i can see <a href="http://www.w3schools.com/html5/tag_nav.asp" rel="nofollow">here</a> and <a href="http://dev.w3.org/html5/spec/Overview.html#the-nav-element" rel="nofollow">here</a>. I always look for discussions here and would love to know what the doctor has to say <img src='http://html5doctor.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Koder</title>
		<link>http://html5doctor.com/nav-element/#comment-15151</link>
		<dc:creator>Koder</dc:creator>
		<pubDate>Sun, 12 Jun 2011 10:51:33 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=473#comment-15151</guid>
		<description>I have a question about a breadcrumb that comes right after/under de primary navigation:

&lt;code&gt;
&lt;div&gt;
	&lt;!-- Main Navigation --&gt;
	&lt;nav&gt;
		&lt;ul&gt;
			&lt;li&gt;&lt;a href=&quot;#&quot;&gt;Main Page 1&lt;/a&gt;&lt;/li&gt;
			&lt;li&gt;&lt;a href=&quot;#&quot;&gt;Main Page 2&lt;/a&gt;&lt;/li&gt;
			&lt;li&gt;&lt;a href=&quot;#&quot;&gt;Main Page 3&lt;/a&gt;&lt;/li&gt;
		&lt;/ul&gt;
	&lt;/nav&gt;

	&lt;!-- Breadcrumb --&gt;			
	&lt;nav&gt;
		&lt;ul&gt;
			&lt;li&gt;&lt;a href=&quot;#&quot;&gt;Home&lt;/a&gt;&lt;/li&gt;
			&lt;li&gt;&lt;a href=&quot;#&quot;&gt;Main Page 2&lt;/a&gt;&lt;/li&gt;
			&lt;li&gt;&lt;a href=&quot;#&quot;&gt;Sub Page 2.1&lt;/a&gt;&lt;/li&gt;
			&lt;li&gt;&lt;a href=&quot;#&quot;&gt;Post title&lt;/a&gt;&lt;/li&gt;
		&lt;/ul&gt;	
	&lt;/nav&gt;
&lt;/div&gt;
&lt;/code&gt;

Or...

&lt;code&gt;
&lt;nav&gt;

	&lt;!-- Main Navigation --&gt;
	&lt;ul&gt;
		&lt;li&gt;&lt;a href=&quot;#&quot;&gt;Main Page 1&lt;/a&gt;&lt;/li&gt;
		&lt;li&gt;&lt;a href=&quot;#&quot;&gt;Main Page 2&lt;/a&gt;&lt;/li&gt;
		&lt;li&gt;&lt;a href=&quot;#&quot;&gt;Main Page 3&lt;/a&gt;&lt;/li&gt;
	&lt;/ul&gt;

	&lt;!-- Breadcrumb --&gt;
	&lt;ul&gt;
		&lt;li&gt;&lt;a href=&quot;#&quot;&gt;Home&lt;/a&gt;&lt;/li&gt;
			&lt;li&gt;&lt;a href=&quot;#&quot;&gt;Main Page 2&lt;/a&gt;&lt;/li&gt;
		&lt;li&gt;&lt;a href=&quot;#&quot;&gt;Sub Page 2.1&lt;/a&gt;&lt;/li&gt;
		&lt;li&gt;&lt;a href=&quot;#&quot;&gt;Post title&lt;/a&gt;&lt;/li&gt;
	&lt;/ul&gt;		
&lt;/nav&gt;
&lt;/code&gt;

I think the second one is correct, but I would like to know how you think about it.</description>
		<content:encoded><![CDATA[<p>I have a question about a breadcrumb that comes right after/under de primary navigation:</p>
<p><code><br />
&lt;div&gt;<br />
	&lt;!-- Main Navigation --&gt;<br />
	&lt;nav&gt;<br />
		&lt;ul&gt;<br />
			&lt;li&gt;&lt;a href="#"&gt;Main Page 1&lt;/a&gt;&lt;/li&gt;<br />
			&lt;li&gt;&lt;a href="#"&gt;Main Page 2&lt;/a&gt;&lt;/li&gt;<br />
			&lt;li&gt;&lt;a href="#"&gt;Main Page 3&lt;/a&gt;&lt;/li&gt;<br />
		&lt;/ul&gt;<br />
	&lt;/nav&gt;</code></p>
<p>	&lt;!-- Breadcrumb --&gt;<br />
	&lt;nav&gt;<br />
		&lt;ul&gt;<br />
			&lt;li&gt;&lt;a href="#"&gt;Home&lt;/a&gt;&lt;/li&gt;<br />
			&lt;li&gt;&lt;a href="#"&gt;Main Page 2&lt;/a&gt;&lt;/li&gt;<br />
			&lt;li&gt;&lt;a href="#"&gt;Sub Page 2.1&lt;/a&gt;&lt;/li&gt;<br />
			&lt;li&gt;&lt;a href="#"&gt;Post title&lt;/a&gt;&lt;/li&gt;<br />
		&lt;/ul&gt;<br />
	&lt;/nav&gt;<br />
&lt;/div&gt;<br />
</p>
<p>Or&#8230;</p>
<p><code><br />
&lt;nav&gt;</code></p>
<p>	&lt;!-- Main Navigation --&gt;<br />
	&lt;ul&gt;<br />
		&lt;li&gt;&lt;a href="#"&gt;Main Page 1&lt;/a&gt;&lt;/li&gt;<br />
		&lt;li&gt;&lt;a href="#"&gt;Main Page 2&lt;/a&gt;&lt;/li&gt;<br />
		&lt;li&gt;&lt;a href="#"&gt;Main Page 3&lt;/a&gt;&lt;/li&gt;<br />
	&lt;/ul&gt;</p>
<p>	&lt;!-- Breadcrumb --&gt;<br />
	&lt;ul&gt;<br />
		&lt;li&gt;&lt;a href="#"&gt;Home&lt;/a&gt;&lt;/li&gt;<br />
			&lt;li&gt;&lt;a href="#"&gt;Main Page 2&lt;/a&gt;&lt;/li&gt;<br />
		&lt;li&gt;&lt;a href="#"&gt;Sub Page 2.1&lt;/a&gt;&lt;/li&gt;<br />
		&lt;li&gt;&lt;a href="#"&gt;Post title&lt;/a&gt;&lt;/li&gt;<br />
	&lt;/ul&gt;<br />
&lt;/nav&gt;<br />
</p>
<p>I think the second one is correct, but I would like to know how you think about it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Terry</title>
		<link>http://html5doctor.com/nav-element/#comment-14986</link>
		<dc:creator>Terry</dc:creator>
		<pubDate>Tue, 10 May 2011 20:39:03 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=473#comment-14986</guid>
		<description>Again, because all the tags were deleted (smart comment function, really...):

Like others pointed out, it&#039;s idiotic having to write &quot;n a v&quot; followed by &quot;u l&quot; then &quot;l i&quot;. I don&#039;t know what the guys responsible for HTML5 were thinking. Probably nothing, like so much else in that new HTML version.

Inside a &quot;n a v&quot;, it should be possible to drop the &quot;u l&quot; because it just bloats the code. &quot;l i&quot; should stay though, as not every text listed should be part of a clickable link.</description>
		<content:encoded><![CDATA[<p>Again, because all the tags were deleted (smart comment function, really&#8230;):</p>
<p>Like others pointed out, it&#8217;s idiotic having to write &#8220;n a v&#8221; followed by &#8220;u l&#8221; then &#8220;l i&#8221;. I don&#8217;t know what the guys responsible for HTML5 were thinking. Probably nothing, like so much else in that new HTML version.</p>
<p>Inside a &#8220;n a v&#8221;, it should be possible to drop the &#8220;u l&#8221; because it just bloats the code. &#8220;l i&#8221; should stay though, as not every text listed should be part of a clickable link.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Terry</title>
		<link>http://html5doctor.com/nav-element/#comment-14985</link>
		<dc:creator>Terry</dc:creator>
		<pubDate>Tue, 10 May 2011 20:36:55 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=473#comment-14985</guid>
		<description>Like others pointed out, it&#039;s idiotic having to write  followed by  then . I don&#039;t know what the guys responsible for HTML5 were thinking. Probably nothing, like so much else in that new HTML version.

Inside a , it should be possible to drop the  because it just bloats the code.  should stay though, as not every text listed should be part of a clickable link.</description>
		<content:encoded><![CDATA[<p>Like others pointed out, it&#8217;s idiotic having to write  followed by  then . I don&#8217;t know what the guys responsible for HTML5 were thinking. Probably nothing, like so much else in that new HTML version.</p>
<p>Inside a , it should be possible to drop the  because it just bloats the code.  should stay though, as not every text listed should be part of a clickable link.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

