I like the idea of the nav and the aside elements:
http://whatwg.org/specs/web-apps/current-work/#the-nav
http://whatwg.org/specs/web-apps/current-work/#the-aside
So instead of:
<html>
<head></head>
<body>
<div id="header"></div>
<div id="nav"></div>
<div id="content"></div>
<div id="sidebar"></div>
<div id="footer"></div>
</body>
</html>
We could have:
<html>
<head></head>
<body>
<header></header>
<nav></nav>
<article></article>
<aside></aside>
<footer></footer>
</body>
</html>
Which is cleaner and more semantic. But it would take years to get it
implemented by the browsers and to grow the installed base to the point where
we can actually use it. Better to just standardise the id and class names - the
web patterns / microformats approach.
cheers,
Geoff.
Brian Cummiskey wrote:
>
> I just stumbled upon this: http://code.google.com/webstats/index.html
>
> Based on commonly used classes and such, they are suggesting new html
> markup.
>
> For example, they mention that footer is used a lot, and are thus
> suggesting a <footer>tag</footer>.
>
> http://whatwg.org/specs/web-apps/current-work/#the-footer
>
> Thoughts?
>
******************************************************
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
******************************************************
