Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.
Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.
i could not agree with you more on all of that. well said.
random note: when i started getting attacked on twitter because my site doesn't validate, i knew i'd crossed a plateau. it was great.
I still think it is fine to go for the draft (or 'non-formalized') microformats. The slides may not have reflected it, but it is still part of my message. hRecipe, for example, is a draft and Google is using it to drive it's (super cool) recipe search app(? ... if you can call it that?). So just because a microformat is considered a draft (this terminology will be changing in microformats v2), doesn't mean it can't offer the structured data you are looking for. So, yes, go forth and use ... just make a point to stay up-to-date.
As for the mothereffin unquoted attributes ... I don't usually subscribe to 'movements.' They cause heavy sighs ... I recognize it is fantastic for informed folks to write and talk about different ways to approach what we do. And http://mathiasbynens.be/notes/unquoted-attribute-values seems relatively informed.
My beef is that uninformed (or lazy or don't-know-betters) will follow like lemmings, rather than taking the time to thoughtfully consider their projects, their work and their workflows. Those three points are always the key drivers of me 'following' anything. If it works for my needs then I will consider it and try. In my experience, that is a minority mentality... you can see it even in the standards world: validating for validation's sake.
For me, it's about being informed and I just feel sorry for the lemmings and their clients (or employers)
A few years ago @ CSS Summit, you said to go ahead and use the non-formalized microformats, as i took it, because in worse case scenario, should they not become part of a spec, the only harm done is maybe some classitus and/or random classes that nonPOSHers will never make sense of. i took that to heart and it's been a part of my workflow ever since. but i didn't see it in the slides above; is that because of microdata/rdfa in the mix?
regardless, great presentation, per usual.
random closing note - how do you feel about the mothereffin unquoted attribute value movement? thrilled, i am not.