To Do

Jump to: navigation, search


This page is for posting microformats related shared to do items. If you want to use this page for your microformats related to-do items, create a section with your name on it. The reason we are keeping these all on the same page is to make it easier to tell when people are working on similar things, and to make it more obvious when people help out with other people's tasks. In theory this probably won't scale, but let's first see how it does in practice. :) - Tantek

microformats2 updates

The following pages need to be updated to for microformats2 (typically code, examples, and any specific format advice)

wiki gardening

trim fixups

Search for all uses of "" for shortlinks and replace them with "" links that just use the pagename.

In particular, let's document old links and (unlinked) and where they used to link to so that if someone *searches* for URLs to figure out what happened to them, there's a chance they'll find the equivalent.

simplify pages

Review pages, from the Main Page on down and:

Examples of simplified pages:

Pages to simplify:

remove broken URLs

There's lots of links to sites that are now gone (see site-deaths on IWC for a full list).

It'd be useful if we replaced them where possible with links to or equivalent.

TODO (mark as done when done):

incorporate things expected to break

shortlink spec

The rel=shortlink spec:

is going to die soon as part of Google Code's shutdown.

1. We should copy that spec (along with FAQ for the first few valid questions/comments) to rel-shortlink, moving existing contents there to supplementary pages or purely historical record.

2. Get to redirect to rel-shortlink instead.

more documentation and research

extract from 1989 timbl proposal

microformats specific

Just some nice things, feel free to do any of these.

for all microformats



Add support to open source calendar projects

These are open source projects that could be potentially enhanced to support hCalendar.


hCalendar/hCard/hReview editor


WordPress patches for microformats

Yahoo Open Source Library Patches

Several of these could very much be improved with a little microformats markup. Do we just make patches and submit them? Contact Nate Koechley at Yahoo (see Tantek for contact info) to follow-up.

Drupal patches for microformats

Adding Microformats to Existing Pages

rel-tagging on Wikipedia

Somebody familiar with the "rel-tag" microformat might want to add details, and a link to the relevant page on this Wiki, to the Wikipedia page on tagging. Andy Mabbett 14:07, 3 Jan 2007 (PST)


Add to the glossary.

hAtom tutorial

Finish the hatom-tutorial.

wiki gardening


Per how-to-play: for English-language pages only: Find British spellings of common words and replace them with the US spellings per en-US. Mark such edits as "minor" with the comment: [[en-US]]. Please be careful to use and maintain proper native spelling of proper nouns (see how-to-play for details).

Here is a table of searches for some of the British-English spellings that have crept into English-language microformats wiki pages, along with their respective US-English spellings. If you find other British spellings, please feel free to add them to this table, with their US equivalent.

en-GB en-US
behaviour behavior
behaviours behaviors
centre center
colour color
colours colors
favour favor
flavour flavor
flavours flavors
flavoured flavored
minimise minimize
minimises minimizes
recognise recognize
recognised recognized

More American and British English spelling differences


This section is for folks to suggest to-do items for admins, in particular, having to do with suggestions for improvements to infrastructure such as the wiki. If you do add an item to this list, please sign your username with four tildes: ~~~~.

Admins check this "inbox" periodically and process and move items to admin-to-do.

Please check admin-to-do to see if there is already an ongoing task item relating to your request. Otherwise add the item below.

Website Improvements

Wiki improvements


I'm keeping microformats related to-do items here both for my own convenience, and for folks looking to help out. - Tantek.

overall priority ordering

  1. Protect the community from threats (wiki damage, mailing list pain or noise), repair damage, add measures to reduce future damage
  2. Update microformats2-parsing with resolved microformats2-parsing-issues
  3. Help implementers with established microformats
  4. Iterate on existing established microformats, resolve issues/feedback etc.
  5. Wiki cleanup/gardening for existing established microformats
  6. Site usability of top-down as an entry point
  7. Community dynamics, process and principles improvements to help guide new microformats developments
  8. Wrap up classic microformats documentation
  9. Document microformats history.
  10. Other

protect the community

update microformats2-parsing with resolved issues

Update microformats2-parsing with resolved microformats2-parsing-issues

help implementers

Update all these tasks for microformats2:

wiki cleanup

Update all these tasks for microformats2:

for all microformat specs


update specification section organization

Goal: greater approachability/readability of microformats specs by a broader audience.



  1. contact microformats community members who are content/tutorial authors, and/or have written (or are writing) technical books, and those who have made concrete helpful suggestions for reorganizing the information architecture / content-order / layout of specs.
  2. figure out if the new intro/headers etc. structure/order in hCard, hReview, and hResume is an improvement, and if it could be better. Document reasoning/requirements for intro/header and other sections.
    • Shorter tends to be better
    • Must be comprehensive enough to "print and read"
    • Must detail authorship/editorship
    • Must detail copyright/patent statements
  3. Design an iterative update to spec organization, in particular, the introduction/boilerplate/headers.
  4. Write up a template - make it self-documenting per the requirements
  5. Update existing specifications with the new intro/headers structure.
    1. hCard
    2. hCalendar
    3. hReview
  6. Write up methodology behind the section organization and note editors lessons learned into an editors-guide page (what other variants were done before, in which specs, and note problems/complaints with other variants).

reorganizing Implementations sections

Hmmm... I like: Authoring, Browsing, Converting, Indexing, Libraries (for developers), and Potential (for open source projects we want to add support to). Anybody have alternative suggestions for this vocabulary? I don't have a particularly strong preference so I'm going to go with these four until I find examples that don't fit, or someone suggests something better.

See: hCalendar Implementations for a first attempt at this. Assuming folks like that, we can go ahead with categorizing the implementations sections of other microformats specifications.


reorg Examples in the Wild sections

Work with community to:

site usability

Update all these tasks for microformats2:

introduction / community

Update all these tasks for microformats2:

posh improvement

principles and process

Create the following pages and document/fill them with content from other pages, email lists, and presentations.


community mark

document issue resolutions

emerging microformats

Update all these tasks for microformats2:

Next-actions for each emerging microformat (one at a time)

new microformat requests

Update all these tasks for microformats2:

wrap up classic microformats documentation

minor update current specifications

social network portability

Iterate on:

Brainstorm updates to the pocket-cheat-sheet to better enable social-network-portability, or perhaps design a new social network portability pocket cheat sheet that specifically documents:

foldup cheatsheet

next actions:

*-authoring microformats wiki pages

help with microformat examples in the wild

Using the above updated authoring pages, get the community to help go over all "common" pages (both logged out and logged in states) of the following sites which have some microformats already, and verify each page is as microformatted as it can be with high fidelity hCalendar and hCard etc. Document full support of each implementation's microformats on the implementations page (perhaps create a separate page for each implementation, e.g. flickr, upcoming, eventful etc.) Document any exceptions as needed. In no particular order:

advocacy for obvious sites

in general

plain language intros

For hCard, hCalendar, hReview, XOXO to start with, write up:

In particular for XOXO, Angus McIntyre suggested:

These suggestions could be incorporated into the other specs as well.

exploratory discussions
CSS enhancements for

Analyze existing microformats for opportunities to enhance CSS and propose to W3C.

update affiliations
profile URLs


Combined next-actions for iteration on hCard, and derived/subsetted microformats adr and geo











summary Examples in the Wild page



document microformats history

Document microformats history, including:



wiki cleanup

hCalendar/hCard/hReview creator improvements




Dimitri Glazkov

Chris Messina




Hey Chris. Congrats on Microsyntax ("Stowe Boyd launches"). So ... do we need a page on this Microformats wiki describing the connection between microformats and microsyntax?

Robert Bachmann

Robert Bachmann


Brian Suda

Citation Microformats


Make changes and update site (almost stable) Get ATTENDEE and other strange attributes working


work on the warnings and error output for the pre-check in X2V


Microformats History

additions to the wiki

Mark Rickerby

Current Tasks


Ernest Prabhakar

Wiki-Thon Proposal

Set aside several hours (probably a Friday night US PST) for focused work on the Wiki, including both physical (e.g., a room in the Bay Area) and virtual (IRC/iChat) participants.


  1. Improve understanding of what needs to be done for Wiki
    • IMHO - this should be done here, in to-do incrementally. -Tantek
  2. Tackle larger projects (~1-2 hours) than people usually have time for
    • I'd like to see these projects *documented* first on to-do before we spend 1-2 hours of a bunch of folk's collective time to go through them. -Tantek
  3. Motivate community to have fun with otherwise tedious "housecleaning" chores

Agenda (Wishlist)

In parallel:

Dan Connolly

DanC hopes to sync up on these tasks in irc roughly weekly, during Wednesday afternoon (Chicago time) "office hours". See also my esw todo list and someday pile.

DanC 15:39, 31 May 2006 (PDT)

Chris Casciano


Drew McLellan


Christophe Ducamp (french localization)

Christophe Ducamp

Frances Berriman

Frances Berriman

Ben West (bewest)


Expore Microformat Deployment Issues

How does who determine the status of work going through some stage of the process? When does a format move from draft to "full spec"? Who decides? What are the qualitative and quantitative features that characterize work in different stages, especially as a spec nears deployment as "full spec". What makes this pronouncement more than a mythical blessing? What quantitative analyses can be provided to validate deployment? Today, we have powerful agents capable of processing huge amounts of information on the web. Should we be using these to measure published marketshare? What role should tools and test suites play in deploying microformats?


A lot of knowledge work is about maintaining sets of vocabulary. Now that the vocabulary is emerging, it may be time start making sure everyone is "on the same page," especially since some of the language is highly symbolic. Terms:

See glossary. Andy Mabbett 13:57, 7 Dec 2006 (PST)


_Concession_: my plans involve reuse of code, which would involve non-compatible changes with the current inline model. This is a nice feature, so maybe I should be branching instead.

Information Architecture

Help Welcomed! Please leave your name Add complaints to wiki-feedback! Helping to make the wiki easier to use. I'd like to see the main page more towards a format like with the big questions right out front:

I'd like to change the front page to this kind of design.

Support Pages

There are several categories of things in the wiki. Can we enumerate them?

Can others agree and or refine this list? Should I take it to the -discuss list? How do we create consensus on how the wiki should be organized in order to make it more usable? And how can we turn that consensus into actionable changes?

The wiki should also capture wisdom that stems from discussions that don't produce microformats. For example, Chris Messina suggests a "Best Of" page suitable for capturing this kind of wisdom. I think we can think of a given microformat as being at a place in a spectrum that ranges from "not yet thought of", to "interesting but needs work," or even "rejected", and of course including all the stages familiar to the microformats processes (eg examples, brainstorming, etc...). If there were such a page would it:

(I think Chris Messina suggests that it belongs to a given microformat, but then how do we collect wisdom from non-microformats?)

Considering that the wiki page named with the microformat (i.e. /wiki/hcard) is the one that people will mostly likely look to first for learning about a particular format, I'd think it'd make more sense and create a more welcoming feel to convert these pages to an intro page introducing the format for the beginner and linking to resources like tutorials and creators. Spec pages would then be relocated to wiki/*-spec -- Cgriego 13:25, 16 Oct 2006 (PDT)

Mike Schinkel's Comments

My suggestion on the list was for us to use a convention that the entry page (i.e. would be an index into a list of (psuedo) standardized sub pages so that it would be very people to find what is important to them. For example, is a list of potential sub pages:

These pages would be located respectively at

Please note I am suggesting an architecture not a specific list of sub pages. The list of sub pages should be defined by both reviewing existing information during site reorganization, and then via discussion on the list in an attempt to discover and extract which sub pages are needed for most/all microformats.

NOTE: This differs from above in that the spec if not viewed as a top level structure but instead the microformat itself and the spec would be under the microformat. In this context "microformat" is a more abstract concept and "spec" is a more concrete thing. Another way to think about it would be that each microformat would have it's own mini home page and then things like "spec" are the pages listed on its home page.

Matt Dertinger (Thewhoo)



Microformats Proposals

Henri Bergius

Henri Bergius

Justin Thorp

Mark Lentczner

Derrick Pallas

microformat proposal: dependancy

Paul Downey

Rob Manson

Clay Newton

Ben Ward



Next Actions

Ketan Majmudar


To Do was last modified: Thursday, October 12th, 2017