I’d like to take this moment (and this incredibly long sentence) to announce that Buckle Down Publishing’s website has won The Association of Educational Publisher’s 2008 Beacon Award for Excellence in Website / E-Commerce. The name kinda lost me there at the end, but I’m pretty sure that this means that we, as the developers of this site, did something good. Good for Buckle Down Publishing as well for conceiving (and constantly revewing and improving) a clear and strong vision for how their site should look and function to best serve their customers. And for giving us money. Definately never a bad idea to give us money.
Applying semantics the “old school” way?
June 30th, 2008I was having an interesting conversation today regarding POSH with a colleague during the development of a back-end system. Over the years, we have both detached ourselves from the mind-set/methodology of using tables for layout in our markup (generally speaking – properly separating content from presentation). Although, towards the end of the conversation, we delved into the use of Microformats to further semantically markup items such as contact information and mailing addresses, and my colleague brought up an interesting assumption that he made regarding use of the class=”" on HTML markup to Microformat it. Essentially with this assumption, he concluded that applying CSS was the sole purpose of the class attribute and therefore applying classes to the markup only to get the data microformatted was the same as using the “table” tag to layout a page.
Now, I voluntarily teach a class covering semantic markup of HTML and applied CSS. A good number of the students traditionally in attendance are those that are still familiar with the “old school” markup techniques (and fresh out of college, no less). I have yet to have a student or another colleague have the same assumption, but I can clearly see now how that could be concluded without a proper education, so I am putting this out there educationally to help others with a similar assumption.
Here is what I quickly found on the topic to help him understand the “old school” way is not being duplicated again by “presentationally” applying classes to markup to solely “format” it. The first two seem a little light in their description though, so this has spurred my colleague to seek out what those “other” straight-forward uses of the class attribute are. What do you know of? Drop me a line and let me know.
- W3C – says
For general purpose processing by user agents
- Web Design Group says
An author could use
– so use for self-identification in programming or further development<code CLASS=Java>when giving Java code - Tantek’s Blog – some other things to note