microformats

2007-09-16T20:39:59Z

Atconys:

<h1> microformats </h1>

== What are microformats? ==
Author/Editor: '''Tantek Çelik'''

=== microformats are ===
* a way of thinking about data
* design principles for formats
* adapted to current behaviors and usage patterns ([http://ifindkarma.typepad.com/relax/2004/12/microformats.html "Pave the cow paths." - Adam Rifkin])
* highly correlated with semantic XHTML, AKA the [http://www.tantek.com/presentations/2004etech/realworldsemanticspres.html real world semantics, AKA lowercase semantic web], AKA [http://www.whump.com/moreLikeThis/link/04069 lossless XHTML]
* described by [http://tantek.com/log/2005/03.html#d13t1722 Tantek's recent presentation at SXSW: The Elements of Meaningful XHTML]
* a set of simple open data format standards that a diverse community of individuals and organizations are actively developing and implementing for more/better structured blogging and web microcontent publishing in general.
* [http://theryanking.com/blog/archives/2005/04/07/an-evolutionary-revolution/ "An evolutionary revolution" - Ryan King]
* all the above.

=== microformats are not ===
* a new language
* infinitely extensible and open-ended
* an attempt to get everyone to change their behavior and rewrite their tools
* a whole new approach that throws away what already works today
* a panacea for all taxonomies, ontologies, and other such abstractions
* defining the whole world, or even just boiling the ocean
* controlled by any individual or organization
* any of the above

== the microformats principles ==
See [[principles]].
== quotes ==
See also [[principles#quotes|quotes relating to the principles]].

== current microformats ==
See the [[Main_Page|main page]] for a list of current microformats specifications, drafts, and discussions.

== more thoughts on how microformats are different ==
There are plenty of existing formats that are ''nearly'' totally useless/ignored.

They're not ''totally'' useless though. They're useful in that they illustrate what at least someone thought might be useful, which unfortunately is typically a lone-inventor working a-priori without any domain expertise.

Or there is the other extreme. Lots of corporate inventors working with plenty of experience, over-designing a format for what ''might'' be needed some day. In particularly bad cases, the corporate vendors collude to prevent openness and/or adoptability by the open source community. Media standards [http://dannyayers.com/archives/2005/09/24/qotd-23/ often suffer from this kind of deliberate "strategic" positioning].

We seek to combat all of those problems with the microformat approach.

* We're not lone-inventors; we're a [http://microformats.org/discuss/ community].
* We don't work [http://en.wikipedia.org/wiki/A_priori a-priori] ("from reason alone"); we require documentation of existing examples, previous attempts at formats. See [[process]].
* When lacking domain expertise, we seek out the domain experts to provide it, and we immerse ourselves in examples and prior art from the domain (see previous point).
* We do our work in the [[Main_Page|open]] with [http://microformats.org/discuss/ open discussion forums].
* We're a diverse mix of corporate, independent, hobbyist, enthusiast.
* We don't over-design. We under-design, deliberately, and then only add things when they are absolutely necessary.
* We adopt very liberal copyright/licensing (CC,GMPG,IETF,W3C) and patent positions (RF,IETF,W3C).
* We ruthlessly self-criticize based on our [http://microformats.org/wiki/microformats#the_microformats_principles principles] in order to keep to the above.

Some ask what the purpose of the (intended) standards is.

Why do you need purpose? More often than not, premature focus on purpose tends to distort data formats towards a particular application which may not be all that relevant. Hence rather than focus on a-priori purpose, we focus on modeling existing behavior, with the knowledge that additional structure will yield plenty of interesting uses, most of which we will not be able to a-priori predict.

This is obviously a very different approach than traditional data format efforts.

Positive with iteration rather than negative with inaction.

Microformats tends to take a positive attitude of developing, [http://design.webgk.com designing] and using the best techniques we can come up with (and iterating upon them), rather than banning/blocking techniques for reasons of fear or cost and thus resulting in inaction. To scrap something, there must be a better alternative provided which addresses the same problem(s) at least as well, with lower costs.

Microformats Wiki - User contributions [en]

microformats