From Microformats Wiki
twiki /
Revision as of 08:21, 15 August 2009 by BenWard (talk | contribs) (Created TWiki implementation brainstorming page.)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search


TWiki is an enterprise-grade open-source Wiki platform, used internally by companies like BT, Disney and Yahoo.

They have a small amount of developer documentation from 2008 concerning support for microformats in TWiki, see [1].

This page documents ways TWiki can be enhanced using microformats:

Mark up articles with hAtom 0.1

The microformats wiki (—which runs MediaWiki with a custom skin that I developed—uses microformats in the mark-up of the page. Namely, each wiki page (article) is marked up using hAtom, providing common structure for titles, authors, content and so forth.

Provide ability to insert microformats into pages

That is, to mark-up an event, person, business and so forth as part of an article, is super-cumbersome. This is something no-one has solved yet, and requires an update to the wiki shorthand mark-up mechanism to allow people to add `class`, `rel` and `rev` attributes. Some attempts have made toward this: The Link Attributes extension for MediaWiki augments the link syntax to allow class, rel and rev.

I've also been working on a possible Markdown extension for the same purpose, that might look something like this, using braces for attributes:

[Ben Ward]({fn url, rel=me}

To produce:

<a class="fn url" rel="me">

TWiki could actually evolve in a similar way:

[[][Ben Ward][fn url, rel=me]]

It would also be necessary to allow adding class attributes to arbitrary blocks (p, div, spans etc.)

Automatically mark-up recurring data patterns in pages with microformats

You could go further with some common types of data. Mentions of and links to other TWiki users could be fully marked up as hCards.

Mark up TWiki user profile pages with hCard

TWiki profile pages, which already generate a certain amount of structured data for URLs, organizations, locations and so forth, should be marked up with hCard.

These are directions for development that come to mind straight away, I'm happy to help spec more specific implementation details.