[whatwg] Small consistency issue with HTML5 nav element examples

[Nicholas Zakas]

Ah, I misinterpreted. With this in mind, I'm a bit unclear as to when <nav> should be used. If it's intended for primary navigation but secondary navigation can also be marked up with it, does that mean it's best to use <nav> whenever you have more than one link grouped together?

Thanks.

-Nicholas
 
______________________________________________
Commander Lock: "Dammit Morpheus, not everyone believes what you believe!"
Morpheus: "My beliefs do not require them to."

-----Original Message-----
From: Ian Hickson [mailto:ian at hixie.ch] 
Sent: Friday, January 14, 2011 3:58 PM
To: Nicholas Zakas
Cc: whatwg at whatwg.org
Subject: Re: [whatwg] Small consistency issue with HTML5 nav element examples

On Fri, 14 Jan 2011, Nicholas Zakas wrote:
>
> In section 4.4.5 (the aside element), an example is given that shows 
> <nav> being used within <footer>.
> 
> Section 4.4.3 (the nav element), explains that this would be an 
> inappropriate use of <nav> 
> (http://dev.w3.org/html5/spec/Overview.html#the-nav-element):
> 
> "Not all groups of links on a page need to be in a nav element - only 
> sections that consist of major navigation blocks are appropriate for the 
> nav element. In particular, it is common for footers to have a short 
> list of links to various pages of a site, such as the terms of service, 
> the home page, and a copyright page. The footer element alone is 
> sufficient for such cases, without a nav element."

It doesn't say it's inappropriate, such that it's not necessary. It's 
still fine to use it there. I'll try to clarify that.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'