Microformats Wiki - User contributions [en]

user-interface

2007-06-29T06:59:13Z

Faaborg: /* Design Guidelines */

<h1> User Interface </h1>

Recently there have been many really good user interface ideas and suggestions for working with microformats. This page serves to collect and document them so that we may be inspired by and iterate on each others' works.

__TOC__

== Implementations ==

See [[implementations]], and document examples of good UI from there, here.
* [[Miffy]] inserts a green square into the document to represent the presence of microformat
* Some [[Greasemonkey]] scripts use a separate iFrame for microformat content
* Other [[Greasemonkey]] scripts insert an icon inline into the page
* [https://addons.mozilla.org/firefox/2240/ Tails Export] (Firefox extension) can display and export some microformats.

== Design Guidelines ==

These are some suggested design guidelines for Web designers and developers by [http://blog.mozilla.com/faaborg/ Alex Faaborg], a user experience designer at Mozilla:
*Design based on actions, not data. A button that says "Send to Calendar" is considerably more useable than a green button that simply says "hCalendar"
*Use iconic images instead of acronyms. In addition to being more descriptive, they localize better. Here are some I've been showing in various talks: [http://people.mozilla.com/~faaborg/files/20061213-fundamentalTypes/fundamentalTypesStatic.jpg_large.jpg microformat icons]. These are still very preliminary. Mozilla will likely release all of the source artwork for our microformat icons under a creative commons license around the launch of Firefox 3. This will enable Web designers to integrate the icons into their sites, and other Web browsers can consider using a similar set of icons.

== Challenges ==

* Chris Messina: "What kind of solutions can we come up with that are single click only?"
* Andy Mabbett - How can we make them [[accessibility|accessible]] to people with (for instance) visual disabilities?
* Alex Faaborg: Mozilla has had inquiries from reporters in the mainstream media (Wired and Business Week) who wanted to cover microformats in stories about the future of the Web browser, but they then later backed out because they felt the term "microformats" would only appeal to developers, and not the average reader. These types of mainstream stories need to focus on the user experience, and not the underlying technology, but what term should reporters use to describe the overall feature?

== Social Network Portability ==

Why is it that every single social network community site makes you:
* re-enter all your personal profile info (name, email, birthday, URL etc.)
* re-add all your friends
?

Instead, let's see some user interface suggestions for sites to simply ''import'' or, even better ''subscribe to'':
* your [[hcard|hCard]] from your URL (blog, profile from another service etc.)
* your list of [[xfn|XFN]] contacts, acquaintances, friends etc. again from your URL (blog, etc.)

Concrete discussion and suggestions:
* Jeremy Keith: [http://adactio.com/journal/1209/ Twittering]: <blockquote><p>Here’s what I want: when I go to the latest social networking fadsite, I want it to ask for my URL. Then it can go off and fetch my [[hcard|hCard]] and [[xfn|XFN]] list. A pre-filled form for my details and a pre-filled list of potential contacts can then be presented to me.</p></blockquote>
* Derek Featherstone: [http://www.boxofchocolates.ca/archives/2006/11/21/solving-problems-with-social-networking Solving problems with social networking]
* Jeremy Keith: [http://adactio.com/journal/1212/ More thoughts on portable social networks]
* Glenn Jones: [http://www.glennjones.net/Post/820/Microformatsandportablesocialnetwork.htm Microformats and portable social network]
* Velvetsarah has [http://www.velvet.id.au/2006/11/23/portable-social-networks/ posted a screenshot and brainstorm] about how a site could handle importing XFN enabled contacts.
[http://www.velvet.id.au/2006/11/23/portable-social-networks/ http://www.velvet.id.au/out/wp-content/uploads/2006/11/picture-9.png]
=== Social Network Portability FAQ ===
*''Doesn't [http://openid.net/ OpenID] address the re-enter all your personal profile info problem?''
** No it does not. OpenID is fundamentally about proving to one site that you own or control another particular URL. Nothing more. All the profile stuff is extra and even then the specific property set is unspecified in OpenID. That's where [[hcard|hCard]] comes in. hCard specifies a vocabulary of personal profile info (name, email, birthday, URL etc.) based on vCard. And in fact that's all you need to solve the "re-enter all your personal info" problem for public sites - no need to authenticate public URLs via OpenID, just read them and parse their hCard(s).

== Browser Integration ==

From screenshot brainstorms to working plugins, there is a lot going on with browser integration of microformats support.

=== Screen Shots ===
* [http://blog.mozilla.com/faaborg/2007/02/04/microformats-part-4-the-user-interface-of-microformat-detection/ Conceptual Mockups of Microformat Detection in Firefox 3]
* [http://www.hicksdesign.co.uk/journal/a-proposal-for-a-safari-microformats-plugin Jon Hicks: Proposal for a Safari Microformats plugin] <br /> [http://www.hicksdesign.co.uk/journal/a-proposal-for-a-safari-microformats-plugin http://www.hicksdesign.co.uk/images/txp/197t.png]
* [http://ben-ward.co.uk/journal/microformats-ui/ Ben Ward: Microformats in Web Browsers] <br /> [http://ben-ward.co.uk/journal/microformats-ui/ http://ben-ward.co.uk/res/posts/uf-web-browser/autodiscovery.png]
* [http://blog.wilsonet.com/archives/2006/04/30/microformats-in-flock/ Microformats in Flock] <br /> [http://blog.wilsonet.com/archives/2006/04/30/microformats-in-flock/ http://blog.wilsonet.com/mockups/Flock/Flock-PickContacts_thumbnail.png]

=== Plugins ===

* The microformat [[implementations]] page has some Greasemonkey scripts.
* http://greasemonkey.makedatamakesense.com/callto_tel/ by Scott Reynen
* [https://addons.mozilla.org/firefox/2240/ Tails Export] (Firefox extension) by Robert de Bruin.
* Jon Hicks has written [http://www.hicksdesign.co.uk/journal/highlight-microformats-with-css a user stylesheet for Mac browsers] that highlights hCard and hCalendar data.

=== Planning and Discussion ===

*[http://wiki.mozilla.org/Microformats Discussion of microformat detection in Firefox 3]
*[http://wiki.mozilla.org/Microformats/UE/ideas UI brainstorming on the Mozilla Wiki]
* The [http://wiki.caminobrowser.org/Development:Planning:Microformats Camino Wiki has a page] where future microformats support is being discussed and organized

== Simpler Markup Languages ==

There are plenty of [[wiki-formats]] that attempt to make it easier for more people author semantic markup, often with textually decorative punctuation.

As these simpler markup languages are something that *users* are expected to type, they are user interface.

=== Markdown extension for hCalendar ===

See [http://article.gmane.org/gmane.text.markdown.general/2027 Markdown and the hCal microformat] which proposes an extension to the Markdown text markup language to capture and represent hCalendar event semantics in a human editable form.

user-interface

2007-06-29T06:58:17Z

Faaborg: Added suggested design guidelines for Web designers

<h1> User Interface </h1>

Recently there have been many really good user interface ideas and suggestions for working with microformats. This page serves to collect and document them so that we may be inspired by and iterate on each others' works.

__TOC__

== Implementations ==

See [[implementations]], and document examples of good UI from there, here.
* [[Miffy]] inserts a green square into the document to represent the presence of microformat
* Some [[Greasemonkey]] scripts use a separate iFrame for microformat content
* Other [[Greasemonkey]] scripts insert an icon inline into the page
* [https://addons.mozilla.org/firefox/2240/ Tails Export] (Firefox extension) can display and export some microformats.

== Design Guidelines ==

These are some ''suggested'' design guidelines for Web designers and developers by Alex Faaborg, a user experience designer at Mozilla:
*Design based on actions, not data. A button that says "Send to Calendar" is considerably more useable than a green button that simply says "hCalendar"
*Use iconic images instead of acronyms. In addition to being more descriptive, they localize better. Here are some I've been showing in various talks: [http://people.mozilla.com/~faaborg/files/20061213-fundamentalTypes/fundamentalTypesStatic.jpg_large.jpg microformat icons]. These are still very preliminary. Mozilla will likely release all of the source artwork for our microformat icons under a creative commons license around the launch of Firefox 3. This will enable Web designers to integrate the icons into their sites, and other Web browsers can consider using a similar set of icons.

== Challenges ==

* Chris Messina: "What kind of solutions can we come up with that are single click only?"
* Andy Mabbett - How can we make them [[accessibility|accessible]] to people with (for instance) visual disabilities?
* Alex Faaborg: Mozilla has had inquiries from reporters in the mainstream media (Wired and Business Week) who wanted to cover microformats in stories about the future of the Web browser, but they then later backed out because they felt the term "microformats" would only appeal to developers, and not the average reader. These types of mainstream stories need to focus on the user experience, and not the underlying technology, but what term should reporters use to describe the overall feature?

== Social Network Portability ==

Why is it that every single social network community site makes you:
* re-enter all your personal profile info (name, email, birthday, URL etc.)
* re-add all your friends
?

Instead, let's see some user interface suggestions for sites to simply ''import'' or, even better ''subscribe to'':
* your [[hcard|hCard]] from your URL (blog, profile from another service etc.)
* your list of [[xfn|XFN]] contacts, acquaintances, friends etc. again from your URL (blog, etc.)

Concrete discussion and suggestions:
* Jeremy Keith: [http://adactio.com/journal/1209/ Twittering]: <blockquote><p>Here’s what I want: when I go to the latest social networking fadsite, I want it to ask for my URL. Then it can go off and fetch my [[hcard|hCard]] and [[xfn|XFN]] list. A pre-filled form for my details and a pre-filled list of potential contacts can then be presented to me.</p></blockquote>
* Derek Featherstone: [http://www.boxofchocolates.ca/archives/2006/11/21/solving-problems-with-social-networking Solving problems with social networking]
* Jeremy Keith: [http://adactio.com/journal/1212/ More thoughts on portable social networks]
* Glenn Jones: [http://www.glennjones.net/Post/820/Microformatsandportablesocialnetwork.htm Microformats and portable social network]
* Velvetsarah has [http://www.velvet.id.au/2006/11/23/portable-social-networks/ posted a screenshot and brainstorm] about how a site could handle importing XFN enabled contacts.
[http://www.velvet.id.au/2006/11/23/portable-social-networks/ http://www.velvet.id.au/out/wp-content/uploads/2006/11/picture-9.png]
=== Social Network Portability FAQ ===
*''Doesn't [http://openid.net/ OpenID] address the re-enter all your personal profile info problem?''
** No it does not. OpenID is fundamentally about proving to one site that you own or control another particular URL. Nothing more. All the profile stuff is extra and even then the specific property set is unspecified in OpenID. That's where [[hcard|hCard]] comes in. hCard specifies a vocabulary of personal profile info (name, email, birthday, URL etc.) based on vCard. And in fact that's all you need to solve the "re-enter all your personal info" problem for public sites - no need to authenticate public URLs via OpenID, just read them and parse their hCard(s).

== Browser Integration ==

From screenshot brainstorms to working plugins, there is a lot going on with browser integration of microformats support.

=== Screen Shots ===
* [http://blog.mozilla.com/faaborg/2007/02/04/microformats-part-4-the-user-interface-of-microformat-detection/ Conceptual Mockups of Microformat Detection in Firefox 3]
* [http://www.hicksdesign.co.uk/journal/a-proposal-for-a-safari-microformats-plugin Jon Hicks: Proposal for a Safari Microformats plugin] <br /> [http://www.hicksdesign.co.uk/journal/a-proposal-for-a-safari-microformats-plugin http://www.hicksdesign.co.uk/images/txp/197t.png]
* [http://ben-ward.co.uk/journal/microformats-ui/ Ben Ward: Microformats in Web Browsers] <br /> [http://ben-ward.co.uk/journal/microformats-ui/ http://ben-ward.co.uk/res/posts/uf-web-browser/autodiscovery.png]
* [http://blog.wilsonet.com/archives/2006/04/30/microformats-in-flock/ Microformats in Flock] <br /> [http://blog.wilsonet.com/archives/2006/04/30/microformats-in-flock/ http://blog.wilsonet.com/mockups/Flock/Flock-PickContacts_thumbnail.png]

=== Plugins ===

* The microformat [[implementations]] page has some Greasemonkey scripts.
* http://greasemonkey.makedatamakesense.com/callto_tel/ by Scott Reynen
* [https://addons.mozilla.org/firefox/2240/ Tails Export] (Firefox extension) by Robert de Bruin.
* Jon Hicks has written [http://www.hicksdesign.co.uk/journal/highlight-microformats-with-css a user stylesheet for Mac browsers] that highlights hCard and hCalendar data.

=== Planning and Discussion ===

*[http://wiki.mozilla.org/Microformats Discussion of microformat detection in Firefox 3]
*[http://wiki.mozilla.org/Microformats/UE/ideas UI brainstorming on the Mozilla Wiki]
* The [http://wiki.caminobrowser.org/Development:Planning:Microformats Camino Wiki has a page] where future microformats support is being discussed and organized

== Simpler Markup Languages ==

There are plenty of [[wiki-formats]] that attempt to make it easier for more people author semantic markup, often with textually decorative punctuation.

As these simpler markup languages are something that *users* are expected to type, they are user interface.

=== Markdown extension for hCalendar ===

See [http://article.gmane.org/gmane.text.markdown.general/2027 Markdown and the hCal microformat] which proposes an extension to the Markdown text markup language to capture and represent hCalendar event semantics in a human editable form.

user-interface

2007-06-29T06:41:06Z

Faaborg: /* Challenges */

<h1> User Interface </h1>

Recently there have been many really good user interface ideas and suggestions for working with microformats. This page serves to collect and document them so that we may be inspired by and iterate on each others' works.

__TOC__

== Implementations ==

See [[implementations]], and document examples of good UI from there, here.
* [[Miffy]] inserts a green square into the document to represent the presence of microformat
* Some [[Greasemonkey]] scripts use a separate iFrame for microformat content
* Other [[Greasemonkey]] scripts insert an icon inline into the page
* [https://addons.mozilla.org/firefox/2240/ Tails Export] (Firefox extension) can display and export some microformats.

== Challenges ==

* Chris Messina: "What kind of solutions can we come up with that are single click only?"
* Andy Mabbett - How can we make them [[accessibility|accessible]] to people with (for instance) visual disabilities?
* Alex Faaborg: Mozilla has had inquiries from reporters in the mainstream media (Wired and Business Week) who wanted to cover microformats in stories about the future of the Web browser, but they then later backed out because they felt the term "microformats" would only appeal to developers, and not the average reader. These types of mainstream stories need to focus on the user experience, and not the underlying technology, but what term should reporters use to describe the overall feature?

== Social Network Portability ==

Why is it that every single social network community site makes you:
* re-enter all your personal profile info (name, email, birthday, URL etc.)
* re-add all your friends
?

Instead, let's see some user interface suggestions for sites to simply ''import'' or, even better ''subscribe to'':
* your [[hcard|hCard]] from your URL (blog, profile from another service etc.)
* your list of [[xfn|XFN]] contacts, acquaintances, friends etc. again from your URL (blog, etc.)

Concrete discussion and suggestions:
* Jeremy Keith: [http://adactio.com/journal/1209/ Twittering]: <blockquote><p>Here’s what I want: when I go to the latest social networking fadsite, I want it to ask for my URL. Then it can go off and fetch my [[hcard|hCard]] and [[xfn|XFN]] list. A pre-filled form for my details and a pre-filled list of potential contacts can then be presented to me.</p></blockquote>
* Derek Featherstone: [http://www.boxofchocolates.ca/archives/2006/11/21/solving-problems-with-social-networking Solving problems with social networking]
* Jeremy Keith: [http://adactio.com/journal/1212/ More thoughts on portable social networks]
* Glenn Jones: [http://www.glennjones.net/Post/820/Microformatsandportablesocialnetwork.htm Microformats and portable social network]
* Velvetsarah has [http://www.velvet.id.au/2006/11/23/portable-social-networks/ posted a screenshot and brainstorm] about how a site could handle importing XFN enabled contacts.
[http://www.velvet.id.au/2006/11/23/portable-social-networks/ http://www.velvet.id.au/out/wp-content/uploads/2006/11/picture-9.png]
=== Social Network Portability FAQ ===
*''Doesn't [http://openid.net/ OpenID] address the re-enter all your personal profile info problem?''
** No it does not. OpenID is fundamentally about proving to one site that you own or control another particular URL. Nothing more. All the profile stuff is extra and even then the specific property set is unspecified in OpenID. That's where [[hcard|hCard]] comes in. hCard specifies a vocabulary of personal profile info (name, email, birthday, URL etc.) based on vCard. And in fact that's all you need to solve the "re-enter all your personal info" problem for public sites - no need to authenticate public URLs via OpenID, just read them and parse their hCard(s).

== Browser Integration ==

From screenshot brainstorms to working plugins, there is a lot going on with browser integration of microformats support.

=== Screen Shots ===
* [http://blog.mozilla.com/faaborg/2007/02/04/microformats-part-4-the-user-interface-of-microformat-detection/ Conceptual Mockups of Microformat Detection in Firefox 3]
* [http://www.hicksdesign.co.uk/journal/a-proposal-for-a-safari-microformats-plugin Jon Hicks: Proposal for a Safari Microformats plugin] <br /> [http://www.hicksdesign.co.uk/journal/a-proposal-for-a-safari-microformats-plugin http://www.hicksdesign.co.uk/images/txp/197t.png]
* [http://ben-ward.co.uk/journal/microformats-ui/ Ben Ward: Microformats in Web Browsers] <br /> [http://ben-ward.co.uk/journal/microformats-ui/ http://ben-ward.co.uk/res/posts/uf-web-browser/autodiscovery.png]
* [http://blog.wilsonet.com/archives/2006/04/30/microformats-in-flock/ Microformats in Flock] <br /> [http://blog.wilsonet.com/archives/2006/04/30/microformats-in-flock/ http://blog.wilsonet.com/mockups/Flock/Flock-PickContacts_thumbnail.png]

=== Plugins ===

* The microformat [[implementations]] page has some Greasemonkey scripts.
* http://greasemonkey.makedatamakesense.com/callto_tel/ by Scott Reynen
* [https://addons.mozilla.org/firefox/2240/ Tails Export] (Firefox extension) by Robert de Bruin.
* Jon Hicks has written [http://www.hicksdesign.co.uk/journal/highlight-microformats-with-css a user stylesheet for Mac browsers] that highlights hCard and hCalendar data.

=== Planning and Discussion ===

*[http://wiki.mozilla.org/Microformats Discussion of microformat detection in Firefox 3]
*[http://wiki.mozilla.org/Microformats/UE/ideas UI brainstorming on the Mozilla Wiki]
* The [http://wiki.caminobrowser.org/Development:Planning:Microformats Camino Wiki has a page] where future microformats support is being discussed and organized

== Simpler Markup Languages ==

There are plenty of [[wiki-formats]] that attempt to make it easier for more people author semantic markup, often with textually decorative punctuation.

As these simpler markup languages are something that *users* are expected to type, they are user interface.

=== Markdown extension for hCalendar ===

See [http://article.gmane.org/gmane.text.markdown.general/2027 Markdown and the hCal microformat] which proposes an extension to the Markdown text markup language to capture and represent hCalendar event semantics in a human editable form.

user-interface

2007-02-24T00:46:01Z

Faaborg:

<h1> User Interface </h1>

Recently there have been many really good user interface ideas and suggestions for working with microformats. This page serves to collect and document them so that we may be inspired by and iterate on each others' works.

__TOC__

== Implementations ==

See [[implementations]], and document examples of good UI from there, here.
* [[Miffy]] inserts a green square into the document to represent the presence of microformat
* Some [[Greasemonkey]] scripts use a separate iFrame for microformat content
* Other [[Greasemonkey]] scripts insert an icon inline into the page
* [https://addons.mozilla.org/firefox/2240/ Tails Export] (Firefox extension) can display and export some microformats.

== Challenges ==

* Chris Messina: "What kind of solutions can we come up with that are single click only?"
* Andy Mabbett - How can we make them accessible to people with (for instance) visual disabilities?

== Social Network Portability ==

Why is it that every single social network community site makes you:
* re-enter all your personal profile info (name, email, birthday, URL etc.)
* re-add all your friends
?

Instead, let's see some user interface suggestions for sites to simply ''import'' or, even better ''subscribe to'':
* your [[hcard|hCard]] from your URL (blog, profile from another service etc.)
* your list of [[xfn|XFN]] contacts, acquaintances, friends etc. again from your URL (blog, etc.)

Concrete discussion and suggestions:
* Jeremy Keith: [http://adactio.com/journal/1209/ Twittering]: <blockquote><p>Here’s what I want: when I go to the latest social networking fadsite, I want it to ask for my URL. Then it can go off and fetch my [[hcard|hCard]] and [[xfn|XFN]] list. A pre-filled form for my details and a pre-filled list of potential contacts can then be presented to me.</p></blockquote>
* Derek Featherstone: [http://www.boxofchocolates.ca/archives/2006/11/21/solving-problems-with-social-networking Solving problems with social networking]
* Jeremy Keith: [http://adactio.com/journal/1212/ More thoughts on portable social networks]
* Glenn Jones: [http://www.glennjones.net/Post/820/Microformatsandportablesocialnetwork.htm Microformats and portable social network]
* Velvetsarah has [http://www.velvet.id.au/2006/11/23/portable-social-networks/ posted a screenshot and brainstorm] about how a site could handle importing XFN enabled contacts.
[http://www.velvet.id.au/2006/11/23/portable-social-networks/ http://www.velvet.id.au/out/wp-content/uploads/2006/11/picture-9.png]
=== Social Network Portability FAQ ===
*''Doesn't [http://openid.net/ OpenID] address the re-enter all your personal profile info problem?''
** No it does not. OpenID is fundamentally about proving to one site that you own or control another particular URL. Nothing more. All the profile stuff is extra and even then the specific property set is unspecified in OpenID. That's where [[hcard|hCard]] comes in. hCard specifies a vocabulary of personal profile info (name, email, birthday, URL etc.) based on vCard. And in fact that's all you need to solve the "re-enter all your personal info" problem for public sites - no need to authenticate public URLs via OpenID, just read them and parse their hCard(s).

== Browser Integration ==

From screenshot brainstorms to working plugins, there is a lot going on with browser integration of microformats support.

=== Screen Shots ===
* [http://blog.mozilla.com/faaborg/2007/02/04/microformats-part-4-the-user-interface-of-microformat-detection/ Conceptual Mockups of Microformat Detection in Firefox 3]
* [http://www.hicksdesign.co.uk/journal/a-proposal-for-a-safari-microformats-plugin Jon Hicks: Proposal for a Safari Microformats plugin] <br /> [http://www.hicksdesign.co.uk/journal/a-proposal-for-a-safari-microformats-plugin http://www.hicksdesign.co.uk/images/txp/197t.png]
* [http://ben-ward.co.uk/journal/microformats-ui/ Ben Ward: Microformats in Web Browsers] <br /> [http://ben-ward.co.uk/journal/microformats-ui/ http://ben-ward.co.uk/res/posts/uf-web-browser/autodiscovery.png]
* [http://blog.wilsonet.com/archives/2006/04/30/microformats-in-flock/ Microformats in Flock] <br /> [http://blog.wilsonet.com/archives/2006/04/30/microformats-in-flock/ http://blog.wilsonet.com/mockups/Flock/Flock-PickContacts_thumbnail.png]

=== Plugins ===

* The microformat [[implementations]] page has some Greasemonkey scripts.
* http://greasemonkey.makedatamakesense.com/callto_tel/ by Scott Reynen
* [https://addons.mozilla.org/firefox/2240/ Tails Export] (Firefox extension) by Robert de Bruin.
* Jon Hicks has written [http://www.hicksdesign.co.uk/journal/highlight-microformats-with-css a user stylesheet for Mac browsers] that highlights hCard and hCalendar data.

=== Planning and Discussion ===

*[http://wiki.mozilla.org/Microformats Discussion of microformat detection in Firefox 3]
*[http://wiki.mozilla.org/Microformats/UE/ideas UI brainstorming on the Mozilla Wiki]
* The [http://wiki.caminobrowser.org/Development:Planning:Microformats Camino Wiki has a page] where future microformats support is being discussed and organized

== Simpler Markup Languages ==

There are plenty of [[wiki-formats]] that attempt to make it easier for more people author semantic markup, often with textually decorative punctuation.

As these simpler markup languages are something that *users* are expected to type, they are user interface.

=== Markdown extension for hCalendar ===

See [http://article.gmane.org/gmane.text.markdown.general/2027 Markdown and the hCal microformat] which proposes an extension to the Markdown text markup language to capture and represent hCalendar event semantics in a human editable form.

User:Faaborg

2007-02-24T00:40:34Z

Faaborg:

==Bio==
I'm a User Experience Designer at Mozilla working on [[Firefox3|Firefox 3]]. Here are some blog posts I've written about microformat detection in Firefox:

*[http://blog.mozilla.com/faaborg/2006/12/11/microformats-part-0-introduction Part 0: Introduction]
*[http://blog.mozilla.com/faaborg/2006/12/12/microformats-part-1-structured-data-chaos Part 1: Structured Data Chaos]
*[http://blog.mozilla.com/faaborg/2006/12/13/microformats-part-2-the-fundamental-types Part 2: The Fundamental Types]
*[http://blog.mozilla.com/faaborg/2006/12/16/microformats-part-3-introducing-operator Part 3: Introducing Operator]
*[http://blog.mozilla.com/faaborg/2007/02/04/microformats-part-4-the-user-interface-of-microformat-detection/ Part 4: The User Interface of Microformat Detection]

==Information about Microformats on the Mozilla Wiki==
*[http://wiki.mozilla.org/Microformats Main page]
*[http://wiki.mozilla.org/Microformats/UE/ideas UI Brainstorming]

==Contact Info==
http://people.mozilla.com/~faaborg/files/20061027/faaborgAtMozilla.jpg