Judging by the comments and coverage a couple of recent posts on microformats have got, they’ve struck something of a nerve.
Kyle Neath wrote “I just don’t get this whole Microformats thing”.
The crux of Kyle’s argument is
I feel like the microformats crew are actively trying to make this an elitest club. I’m not very stupid (I don’t think) but when I first started researching microformats it took me ages to really understand it. It turned out to be dead simple.
Right now, the content at the wiki is largely specifications, and related documentation. And specifications are to some extent of their nature difficult - they are formal documents, whose role is to unambiguously, but completely, define a technology and its constituent elements.
Kyle’s frustration is definitely legitimate, but I’d like to observe that microformats are still, despite being increasingly widely known, in their infancy.
Unlike most standards development, the microformats process is “bottom up” - much more like open source software development than the kind of standards development you get out of the ISO of W3C.
It’s also worth keeping in mind that no one whatsoever gets paid or is officially employed in even a voluntary capacity in association with microformats. Some people might be lucky enough to have jobs that allow them to get involved during work time, but even that handful (at most) doubtless puts in a significant amount of after-hours effort. It really is a labor of love for all those involved.
If you went back a decade or so, you’d find very similar responses to CSS - there was little more than specifications out there - few if any books, few if any sites dedicated to CSS - if you wanted to get up to speed with CSS, then you needed to get to grips with the specification.
A lot of people expressed this level of frustration with CSS back then - in fact it sounds very familiar to me. And then as now, it was legitimate.
10 or so years ago it prompted me to write “Everything you ever wanted to know about style” (now the far more boringly titled Complete CSS Guide) and more generally, “The House of Style” a set of resources associated with CSS - tutorials, examples, articles, and other resources
I’m proud to say, it’s still around, literally tens of millions of page views and a decade later, and much updated too.
Others developed sites (quite a few predating ours) - css.nu being one of the first. People like Eric Meyer wrote wonderful books, and articles for development sites (sadly many of which are now defunct). Over a period of a couple of years, at least, an “ecosystem” of resources, software, training, guides, and so on, emerged around CSS. But it definitely took quite some time.
I have no doubt that the same is, and will continue to happen with microformats.
Right now, I’m doing a couple of things in that same vein as the stuff I started doing a decade or so ago with CSS.
Microformatique is a bog dedicated to what’s going on with microformats, and I’ve just started a new “Know your Microformats” series - each installment going into detail on one micrforomat, but staying practical and educational.
And I am doing something that despite a number of offers, I never did with CSS - I am writing a book on microfomats - one that’s actually pretty close to being finished. I hope that it will help those interested in and new to microformats get up to speed with the minimum of frustration.
And I’ll let you in on a little secret - I get frustrated sometimes with microformats - just as I did with CSS. But I see that (and this is my personal response) as a price for being associated with a technology in it’s infancy.


{ 5 } Comments
I agree with a lot of Kyle’s concerns. It seems like it is that way with any new technology. Early on it is often overly complicated by the leading group because they don’t know how to communicate it for mass appeal and the ideas are so new that no one knows how to articulate them properly. That is a serious barrier to entry. It is something that needs to be figured out.
I was recently at a conference on unicode and internationalization. It seemed the same way. There is some REALLY important stuff there. Its not that hard but I think a lot of it is over complicated so when people to adopt it they have to really work at figuring it out.
John, I really appreciate your work. When you have written about microformats, you have done it in an easy to understand way. You don’t over complicate it. Cheers!
John, I’ve got the same problem doing the same work like yours (for Russians). So I’m think that more clear examples and more easy language - the best way to spread microformats all over the world.
I think it’d be good to look towards the model that firefox uses to manage their user community. As I see it, they provide for 3 tiers of users: the “download and go” user (Getfirefox, popular addons page, mozillazine knowledge base links on support page, etc), the power user (MozillaWiki, mozillazine wiki, mozdev extension homepages, etc) and the developer/contributer (bugzilla, etc). Why not specifically structure the content for people who want to argue over DTDs and such from the people who just want to find browser plugins, hCard generators and such?
One interesting thing to notice about the stuff I mentioned as end-user content for firefox is that none of the pages linked from thetabs on the main firefox page is longer than 2 screen pages long and NONE have huge blocks of text.
BTW, one of the most clear articles: “Microformats: Understanding Elemental Microformats” (by Molly Holzschlag)
http://www.informit.com/guides/content.asp?g=webdesign&seqNum=293&rl=1
Down there towards the end of this post, I noticed the following statement:
“Microformatique is a bog.”
Now, I know it isn’t. And you know it isn’t. And it may just have been a ruse to get my attention. If so, it sure worked.
Happy bogging!
Post a Comment