Skip to content

Firefox 3 plans for microformats - no just speculation anymore

As you might know, the planning process for Firefox 3 has been and is quite transparent - to the extent that a draft of their requirements documentation is now online at mozilla.org

The planned release timeframe is q3/4 2007, with a goal of one major release per year.

Microformats get an extensive mention - here is what we can learn from the docs today

High Level Feature Plan

For Users

Information Management includes Bookmarks, History, Content Handling, Content Editing, Printing and Microformats

HIGHLY DESIRABLE Features

Microformat detection framework
FR: create document parsing framework for detecting microformats
FR: create API for developers to leverage this framework
Microformat handling
FR: display microformats in content area
FR: allow user to configure microformat handlers
FR: support hCard, hCal and geo
FR: provide API/data formats for adding additional microformat types
FR: allow web developers to override microformat display attributes
NFR: must not affect page load time

Firefox’s transparency is to be applauded - not just for keeping stakeholders like the community of developers and users in the loop, but also for openly committing to developments down the track. And for throwing down the gauntlet to other brower developers. What have Internet Explorer (who’ve made encouraging noises about microformats), but where are you Safari, and Opera?

[tags]microformats, firefox[/tags]

{ 1 } Trackback

  1. […] An article at the Microformatique blog has a nice summary of the planned features. Microformats are an attempt to allow applications to talk to each other with minimal human intervention.  One could envision that Firefox might support automatic transfer of microformatted data into your requested application. Currently, imbedded links on websites and custom plugins are the main ways to use microformats - technical hurdles that prevent all but the most techincally savvy from using them. […]

Post a Comment

Your email is never published nor shared. Required fields are marked *