pageoneresults - 4:25 pm on Feb 27, 2010 (gmt 0)
I've written before about what a huge challenge it is to do REAL sentiment analysis.
There's a language for that! ;)
Emotion Markup Language 1.0
but I think over-loading Class structures is typical of the abysmal quality and abuse of web programming languages in general.
This can be minimized by taking into consideration the class properties and then designing with those in mind. I understand where you're coming from but I don't see any abuse taking place. The overloading typically occurs from the developer standpoint. You can minimize the amount of markup involved by taking a look at the entire structure to see what can be nixed, to compensate for any additional class markup.
IMO, all quite a few of us have to do is change the name of the style applied to elements.
It really is as simple as that for many. For others, it is going to be constant whining and an ongoing battle to make things happen.
I'm already in the process of setting up default style sheets for all the confirmed and common properties. I will now start designing with those in mind and at the same time, begin retrofitting existing sites. I've already done a few. :)
I've spent the last two weeks engulfed in Microformats. I've read just about every topic Google have posted on the subject. I can tell you that this is not something new but it is now becoming a reality for many of us. So, what is new? For one, Google's documentation have been updated and contain many references to Microformats including their experimenting with hCard and hReview Microformats. Here are just a few you'll want to review and act upon if you haven't already. ;)