It's only ill concieved to those who fail to grasp how SIMPLE they are... and I'm CONSTANTLY amazed at the people who cannot grasp what the specification is actually saying, and the sheer common sense of it. It's so moronically simple!
H1 is the heading under which all content and headings on the page are subsections of; H2's are the start of sections that are subsections of the h1. H3's are the start of subsections of the h2's. It fans out like a tree -- just like the auto-section navigation in Blazer gives you on pages that bother to use it properly; Just like the summary you can pull up with a user style in Lynx -- Just like the document outline in the FF web developer toolbar can create (If you are still using a version of Firefox prior to 3.6, since it's not been updated to work properly)
That's their meaning -- BECAUSE they use words like "importance" (which they mean in the structural sense) or rankings people have repeatedly taken the meanings incorrectly or out of context -- which I believe is why people CONSTANTLY screw up something so easy!
As opposed to just using a heading tag to say "This is the start of a section"... yeah, that's so much simpler; NOT.
Which of course precludes the use of accesskeys menus for most mobile browsers OTHER than webkit... IMHO the NAV element is simply being added to justify that extra pointless div people slap around their menu UL's for no good reason; They are just using accessibility as an excuse since I doubt we'll see many user agents be able to use it the way their explanation claims it will work.
Pretty much -- I wrote about many of my reasons on the blog I really need to post in more than once every six months...
People can barely manage to use any of the tags we already have correctly if they even know most of them, adding MORE tags to the specification isn't going to help matters; and is in fact undoing ALL of the progress STRICT offered us. You want evidence of idiocy, look no further than AUDIO, VIDEO, and making EMBED official... Since STRICT was supposed to be paving the way to replace APPLET, EMBED, IMG and BGSOUND with OBJECT. One tag... does the job, one tag is simpler than ten tags -- which we let this HTML5 train wreck through is basically what we are looking at!
CISC vs. RISC?
Keyword being buzz. Meaningless background noise spouted more as marketspeak than actual meaningful thought. ONE STEP removed from Web 2.0
Which I tried and got pissed with being constantly shot down over pointing out all the redundancies, undoing of the progress of the past ten years by making what is effectively "Transitional on Steroids", etc, etc... They don't want progress or cleaner code, they just want to keep bolting on new redundancies and pointless "gee ain't it neat" nonsense that does the end user no good and just wastes more bandwidth... It's one step removed from the dumbasses who slap jquery on a page just so they can change the color of an anchor.
Which makes it REALLY pathetic when they try to sell it as saving bandwidth or making things simpler. I suspect my definition of simpler differs from theirs.
But as my favorite apprentice said shortly before his unfortunate passing just over a year ago "The same people who made endless bloated nested tables today just make endless bloated nested div's." -- to which HTML 5 must be a dream come true with all the silly extra tags to justify those pointless wrapping elements by trying to sell us on them as semantic -- when they generally are so vague as to be meaningless. Hardly surprising since it seems most of the people working on the specification never actually embraced the concept of STRICT.
As it is I've stopped taking on new clients altogether and have been weening off my existing ones to the point they are self sustaining. My increasing disgust with the sleazeball crap out pages any old way industry has me ready to go on a shooting spree; As such I've taken a renewed interest carving, bicycle building, and busking on the EWI.
It just gets sleazier, sloppier and stupider every month...