introduction-ja

Microformatsの手引き

関連: プレス, プレゼンテーション, 参考図書, 証言

Microformatsとは?

Microformatsとは、XHTML semantic contentの"辞書"です。Microformatsを使っておけば、リッチな情報をもつHTML文書からsemanticな意味を機械的に抽出できるようになります。つまり、Microformatsは、最も簡単にWeb上でデータ(もしくはデータフォーマット)を再利用するためのものなのです。

何故Microformatsなのか

何故Microformatsに注目するのか?

簡単に言えば、Microformatsにはいくつかの追い風があるのです。

1. Webデザインや情報構造の進化の中での論理的な次のステップである
2. 中央集権的なサービスを信頼せずとも、リッチな情報を公開する人自身で使える方法である
3. "従来の"メタデータの試みは失敗したり広く導入されるまでにとても長い時間がかかることが判明したので新しいアプローチが必要とされていた
4. データのための(X)HTMLを使うことができる

Webデザインの進化

はじめに1990年のことを話そう。HTMLというものがあった。それは良いものだった。シンプルで、小さい仕様で、(テキスト)データを論理的な意味をマークアップすることができた。そして、World Wide Web上でそれを共有することができた。

それからブラウザ戦争(1994-1999)が勃発した。主要なブラウザ開発会社は、典型的なWebサイトの作成者/デザイナが求めていたWebページの見ためを制御するための"革新的な"タグを導入しはじめた。結果、HTML 3.2は流行していた見ためのためのタグを"標準化"してしまった。

CSS1 (1996)と論理表現に主眼を置いたHTML4 (1998)が現れ、かすかな希望をもたらした。しかし、WebデザイナがWebページにCSSを実戦投入するのは、CSS1/HTML4を完全に(もしくはほとんどを)実装したWebブラウザ(IE5/Mac, IE6/Windows, Netscape 6)がリリースされる(2000-2001)のを待たねばならなかった。コミュニティの先導者たちは、(い く つ かのハックを使いつつとはいえ)CSSを精力的に採用し、推進しはじめた。そして、マークアップからプレゼンテーションを分離することは、効率の良さと高い生産性をもたらしたのであった。しかし、その事実を声高に主張しつつも依然として少数派でしかなかった。

The introduction of the Wired News redesign in 100% CSS, and the beautiful CSS Zen Garden (2002-2003) was CSS's tipping point. With the clear and obvious presentation of visual beauty and broad creativity, designers world-wide "got it" and realized that this was the future of web design. The presentational markup of <FONT>, <TABLE>, and spacer.gif were tossed aside by any and all self-respecting web designers, who discovered the near infinite flexibility of <div>, <span>, and the 'class' attribute. A few in the community even began adopting some of the more semantic elements in HTML: <p>, <h1>...<h6>, <ol>, <ul>, <li>, <em>, <strong>. Leaders in the community exercised the semantic limits of strict HTML4 (experimented with XHTML) and documented best practices.

As the community followed rapidly in the footpaths they had worn, the leaders began to run into the limits of semantic (X)HTML. Other subcultures were attempting to rewrite the world in their own language(s) (RDF, "plain" XML, SVG), yet not having much of an impact on the World Wide Web, which required human presentable data, compatible with the browsers people already used. Social Software and Blogs, written by this new generation of web designers and programmers, began to take off.

Natural patterns emerged from the way people used blogging systems, putting things into lists, for example lists of other bloggers (known as blogrolls), and annotating them with information representing relationships such has having met, friends, family, etc. The first microformat, XFN, was designed to match these behaviors, and introduced to the blogging community (2003-2004), who adopted it within weeks. The GMPG was formed as a home for XFN, and documented a few key design principles later adopted for microformats. The key notion, that semantic (X)HTML could be extended, had been introduced and accepted by the community.

By understanding, using, and combining semantic (X)HTML building blocks, as well as determining that semantic (X)HTML could be validly extended via new rel, meta name, and class values, defined in (X)HTML profiles in the XMDP format, the community began to design and develop many more microformats (2004-2005). More patterns emerged from the blogging community, and each aggregate human behavior drove the design of simple, adaptive microformats to meet its needs. Creative Commons licensing became popular and rel-license was proposed. Outlines and lists: XOXO. Contact info: hCard. Calendars and events hCalendar.

Using these new found building blocks, the web design and information architecture communities were no longer limited by the predefined semantics of HTML4 (nor did they have to compromise human presentation and ease of authoring which other attempts sorely lacked). 2005 may well be the year that microformats became the next step in the evolution of the web.

The Appeal to Simplicity

• Microformats are a simple effort which has appealed to many frustrated with previous complex efforts. One parallel that can be drawn is to REST in the web services world, i.e. see this comparison of microformats and REST. See the REST wiki for more about REST. Related microformats and microprotocols.
• See also: Web Services and the Innovators Dilemma by Justin Leavesley

関連ページ

• 最近のプレスのインタビューや記事もよい手引きとなります。
• microformats-jaにあるプレゼンテーションも背景を更に知ったり、導入のための資料となるでしょう。
• microformatsについてのポッドキャストを聴いてください。
• suggested readingもあります。
• microformatsを実装したいですか?

Articles

• Digital Web Magazine: Microformats Primer by Garrett Dimon
• An Extra SIDE to Web Standards Based Design - How Semantic Information Design Ethics (SIDE) and a few readily available techniques can help heal the Web, by Jon Tan. See also his CSS Zen Garden "Leggo my ego" entry.
• Andrew D. Hume has written a blog post introducing microformats and another one on usable microformats.
• Practical Microformats with hCard by Drew McLellan
• Jesse Skinner's introduction to hCard
• Shaun Shull's great post on How Microformats Affect Seearch Engine Optimization
• Blog Business Summit: Microformats in Plain English: the Promise of Simple Business to Business Data Exchange by Steve Broback

Miscellaneous Reference

These are various intro-related links/articles which I haven't figured out yet how to incorporate. You may find them of interest. - Tantek

• Data First vs. Structure First
  • Tantek says: In many ways it is actually *far* worse than that post conveys. The "typical" programmer literally loves spending far more time worrying about and designing the structure for structure's sake, than data, and even less so, "real world" data (current behaviors etc.). Hence we have taken the directly opposite tack with microformats when looking to solve a problem.
    • Zeroeth, define the real-world problem. If you can't do this, then stop.
    • First, look at real-world usage (data).
    • Second, what previous standards are people actually using today? If there is more than one, then lean towards those with the better adoption.
    • And only after those first two do we bother to pay attention to theoretical standards, those that have been invented (whether by individuals, committees), but haven't seen much if any actual adoption.
• 2000-03-21 Dan Connolly on human-consumable information: (strong emphasis added)
  • I believe that one of the best ways to transition into RDF, if not a long-term deployment strategy for RDF, is to manage the information in human-consumable form (XHTML) annotated with just enough info to extract the RDF statements that the human info is intended to convey. In other words: using a relational database or some sort of native RDF data store, and spitting out HTML dynamically, is a lot of infrastructure to operate and probably not worth it for lots of interesting cases. We all know that we have to produce a human-readable version of the thing... why not use that as the primary source?