Microformat

From Wikipedia, the free encyclopedia

A microformat is a web-based^[1] approach to semantic markup that seeks to re-use existing XHTML and HTML tags to convey metadata^[2] and other attributes. This approach allows information intended for end-users (such as contact information, geographic coordinates, calendar events, and the like) to also be automatically processed by software.

Although the content of web pages is technically already capable of "automated processing," and has been since the inception of the web, such processing is difficult because the traditional markup tags used to display information on the web do not describe what the information means^[3]. Microformats are intended to bridge this gap by attaching semantics, and thereby obviate other, more complicated methods of automated processing, such as natural language processing or screen scraping. The use, adoption and processing of microformats enables data items to be indexed, searched for, saved or cross-referenced, so that information can be reused or combined^[3].

Current microformats allow the encoding and extraction of events, contact information, social relationships and so on. More are being developed. Version 3 of the Firefox browser^[4], as well as version 8 of Internet Explorer^[5] are expected to include native support for microformats.

[edit] Background

Microformats emerged as part of a grassroots movement to make recognizable data items (such as events, contact details or geographical locations) capable of automated processing by software, as well as directly readable by end-users^[3][6]. Link-based microformats emerged first. These include vote links that express opinions of the linked page, which can be tallied into instant polls by search engines^[7].

As the microformats community grew, CommerceNet, a nonprofit organization that promotes electronic commerce on the Internet, helped sponsor and promote the technology and support the microformats community in various ways.^[7] CommerceNet also helped co-found the Microformats.org community site^[7].

Neither CommerceNet nor Microformats.org is a standards body. The microformats community is an open wiki, mailing list, and Internet relay chat (IRC) channel^[7]. Most of the existing microformats were created at the Microformats.org wiki and associated mailing list, by a process of gathering examples of web publishing behaviour, then codifying it. Some other microformats (such as rel=nofollow and unAPI) have been proposed, or developed, elsewhere.

[edit] Technical overview

XHTML and HTML standards allow for semantics to be embedded and encoded within the attributes of markup tags. Microformats take advantage of these standards by indicating the presence of metadata using the following attributes:

For example, in the text "The birds roosted at 52.48,-1.89" is a pair of numbers which may be understood, from their context, to be a set of geographic coordinates. By wrapping them in spans (or other HTML elements) with specific class names (in this case geo, latitude and longitude, all part of the geo microformat specification):

The birds roosted at
   <span class="geo">
     <span class="latitude">52.48</span>,
     <span class="longitude">-1.89</span>
   </span>

machines can be told exactly what each value represents and can then perform a variety of tasks such as indexing it, looking it up on a map and exporting it to a GPS device.

[edit] Example

In this example, the contact information is presented as follows:

 <div>
   <div>Joe Doe</div>
   <div>The Example Company</div>
   <div></div>
   <a href="http://example.com/">http://example.com/</a>
 </div>
604-555-1234

With hCard microformat markup, that becomes:

 <div class="vcard">
   <div class="fn">Joe Doe</div>
   <div class="org">The Example Company</div>
   <div class="tel"></div>
   <a class="url" href="http://example.com/">http://example.com/</a>
 </div>
604-555-1234

Here, the formatted name (fn), organisation (org), telephone number (tel) and web address (url) have been identified using specific class names and the whole thing is wrapped in class="vcard", which indicates that the other classes form an hCard (short for "HTML vCard)") and are not merely coincidentally named. Other, optional, hCard classes also exist. It is now possible for software, such as browser plug-ins, to extract the information, and transfer it to other applications, such as an address book.

[edit] Specific microformats

Several microformats have been developed to enable semantic markup of particular types of information.

adr - for postal addresses geo - for geographical coordinates (latitude, longitude)

[edit] Proposed microformats

Among the many proposed microformats^[12], the following are undergoing active development:

[edit] Uses of microformats

Using microformats within HTML code provides additional formatting and semantic data that can be used by applications. These could be applications that collect data about on-line resources, such as web crawlers, or desktop applications such as e-mail clients or scheduling software. They can also be used to facilitate "mash ups" such as exporting all of the geographical locations on a web page into Google Maps, to visualize them spatially.

Several browser extensions, such as Operator, provide the ability to detect microformats within an HTML document and export them into formats compatible with contact management and calendar utilities, such as Microsoft Outlook.

Microsoft expressed a desire to incorporate Microformats into upcoming projects^[17]; as have other software companies.

In Wikipedia - and more generally in MediaWiki - microformats are used as part of templates like {{coord}}.

Alex Faaborg summarizes the arguments for putting the responsibility for microformat user interfaces in the web browser rather than makign more complicated HTML:^[18]

[edit] Evaluation of microformats

Various commentators have offered review and discussion on the design principles and practical aspects of microformats. Additionally, microformats have been compared to other approaches that seek to serve the same or similar purpose^[19]. From time to time, there is criticism of a single, or all, microformats^[19]. Documented efforts to advocate both the spread and use of microformats are known to exist as well^[20][21]. Opera Software CTO and CSS creator Håkon Wium Lie said in 2005 "We will also see a bunch of microformats being developed, and that’s how the semantic web will be built, I believe."^[22]. However, as of August 2008, Toby Inkster, author of the "Cognition" microformat parsing service pointed out that no new microformat specifications had been published for over three years^[23].

[edit] Design principles

Computer scientist and entrepreneur, Rohit Khare stated that reduce, reuse, and recycle is "shorthand for several design principles" that motivated the development and practices behind microformats^[7]:71-72 . These aspects can be summarized as follows:

[edit] Accessibility

Because some microformats make use of title attribute of HTML's abbr element to conceal machine-readable data (particularly date-times and geographical coordinates) in the "abbr design pattern", the plain text content of the element is inaccessible to those screen readers that expand abbreviations^[24]. In June 2008, the BBC announced that it would be dropping use of microformats using the abbr design pattern because of accessibility concerns^[25].

[edit] Alternative approaches

Microformats are not the only solution for providing "more intelligent data" on the web. Alternative approaches exist and are under development as well. For example, the use of XML markup and standards of the Semantic Web are cited as alternative approaches^[7]. Some contrast these with microformats in that they do not necessarily coincide with the design principles of "reduce, reuse, and recycle", at least not to the same extent^[7].

One advocate of microformats, Tantek Çelik, characterized a problem with alternative approaches:

For some applications the use of other approaches may be valid. If one wishes to use microformat-style embedding but the type of data one wishes to embed does not map to an existing microformat, one can use RDFa to embed arbitrary vocabularies into HTML. An example of this would be embedding domain-specific scientific data on the Web like zoological or chemical data, where no microformat for such data exists. Furthermore, standards such as W3C's GRDDL allow microformats to be converted into data compatible with the Semantic Web^[26].

Another advocate of microformats, Ryan King, put the compatibility of microformats with other approaches this way:

[edit] See also

[edit] Notes

[edit] References

[edit] Further reading

[edit] External links