El libro practical html5 projects de Adrian W. West cita
-------------------------------------------------------------------------------------------------------------------------------------------------
You may wonder why I have not used the <section> element in any example so far. When I wrote this
chapter, there was considerable confusion over the difference between <section> and <article>. This
arose because some manuals and web sites described the <section> element as being like a chapter in a
book. This suggested that it was like a wrapper containing chunks of content. As a result, one HTML5
manual and some HTML5 forums used <section> as a styled wrapper or container. This surrounded
several <article> elements. Another HTML5 manual used a <div>
for the container or wrapper; this
enclosed <article>
elements, which in turn enclosed <sections>.
Which practice is correct? I tried them all and they all worked because HTML5 is currently quite lax.
Even my favorite HTML5 gurus at HTML5 Doctor (http://html5doctor.com) discovered they had been using the <section> element incorrectly; their revised web site stated: “…we realize that we’ve been using the <section> element incorrectly all this time. Sorry, what we’ve been doing wrong is using <section> to wrap content in order to style it, or to demarcate the main content area from the <nav>, <header>, <footer> etc. These are jobs for <div>, not <section>.”
The
http://www.whatwg.org specification was revised as follows: “The <section> element is not a generic container element. When an element is needed for styling purposes…authors are encouraged touse the <div> element instead.”
See the full version of the W3C statement on this topic at
http://www.w3.org/TR/html5/sections.html#the-section-element ----------------------------------------------------------------------------------------------------------------------------------
por ello mi duda.