Comments on: A List Apart #250 http://www.kashubeck.com/blog/2007/12/04/a-list-apart-250/ A blog about what I'm trying to cram into only 24 hours Tue, 06 Jan 2009 05:53:14 +0000 http://wordpress.org/?v=2.5.1 By: Nate Klaiber http://www.kashubeck.com/blog/2007/12/04/a-list-apart-250/#comment-43 Nate Klaiber Tue, 04 Dec 2007 20:46:56 +0000 http://www.kashubeck.com/blog/?p=28#comment-43 I tend to think about two things in regards to HTML5. 1), the actual timeframe where it will actually be rendered useful and the adoption rate is increased with vendors and users alike, and 2) backwards compatability. These are two very important things to consider. While I like the structural elements, would this mean that we should all go back and edit all of our markup to be in line with the new elements? Not against new elements - but think about the magnitude of this chance (think corporate and enterprise, think CMS's, think packaged web services). I think adoption rate will take a long time. This is why I like Microformats. They take what everyone else is already using, and adding semantic goodness to their elements. The benefit is two fold. The page is semantic, and they have hooks for their styling and JavaScript. A DIV simply represents a logical division. Where do you draw the line on all of the different possible divisions a user could potentially use? If you leave one out - then we are right back at square one where someone will have to modify accordingly to fit their specific needs (much like people do now). Just some more stuff to think about, I am still processing it all and I figured I would share it with you. I tend to think about two things in regards to HTML5. 1), the actual timeframe where it will actually be rendered useful and the adoption rate is increased with vendors and users alike, and 2) backwards compatability. These are two very important things to consider.

While I like the structural elements, would this mean that we should all go back and edit all of our markup to be in line with the new elements? Not against new elements - but think about the magnitude of this chance (think corporate and enterprise, think CMS’s, think packaged web services). I think adoption rate will take a long time. This is why I like Microformats. They take what everyone else is already using, and adding semantic goodness to their elements. The benefit is two fold. The page is semantic, and they have hooks for their styling and JavaScript.

A DIV simply represents a logical division. Where do you draw the line on all of the different possible divisions a user could potentially use? If you leave one out - then we are right back at square one where someone will have to modify accordingly to fit their specific needs (much like people do now).

Just some more stuff to think about, I am still processing it all and I figured I would share it with you.

]]>