Microformats Wiki - User contributions [en]

admins

2021-01-21T21:09:32Z

Phae: /* contacting */ removing myself since I don't actually have full access anymore

{{DISPLAYTITLE:microformats admins}}
== admins ==
The following individuals are invited volunteer admins on the microformats [[IRC]] channel and [[Main_Page|wiki]]:
* [[User:Phae|Frances Berriman]]
* [[User:Tantek|Tantek Çelik]]
* [[User:ChristopheDucamp|Christophe Ducamp]] - primary editor/translator for [[Main_Page-fr]]. as of 2012-06-20
* [[User:Adactio|Jeremy Keith]]
* [[User:Rohit|Rohit Khare]] - also an ''ex officio'' observer of microformats admins, as the contact point for the servers, domain names, and [[:Category:public domain license#Point of Contact|legal issues]].
* [[User:GRegorLove|gRegor Morrill]] {{new}} as of 2018-06-20
* [[User:Kevin_Marks|Kevin Marks]]
* [[User:EricMeyer|Eric A. Meyer]]
* [[User:EdwardOConnor|Theresa O'Connor]] as of 2012-06-20
* [[User:Aaronpk|Aaron Parecki]] {{new}} as of 2018-06-20
* [[User:Brian|Brian Suda]]
* [[User:BenWard|Ben Ward]]

=== Wiki-only admins ===
* [[User:Sknebel|Sven Knebel]] {{new}} as of 2018-06-20
* [[User:TomMorris]]
* [[User:Zegnat|Martijn van der Ven]] {{new}} as of 2018-06-20
* [[User:Cnsupport]] - infrastructure only

For an automatically generated flat list of microformats wiki admins see: [[Special:Listadmins]].

== contacting ==
Contacting the admins can be done by either joining the microformats [[irc]] channel and stating "adminhelp" to alert an active moderator that you need their attention.

== admin emeriti ==
The following individuals are recognized as Admin Emeritus for their invaluable contributions to the microformats community, both in many cases with the founding thereof, and over the years. They've chosen to step down as active microformats admins but should they wish to, are always welcome to return to full active admin status.

* [[User:DanCederholm|Dan Cederholm]] (founding-2011)
* [[User:RyanKing|Ryan King]] - (founding-2011, [[mfbot]])

* [[User:RobertBachmann|Robert Bachmann]] (2006(?)-2011, [[mflogbot]])

* [[User:DimitriGlazkov|Dimitri Glazkov]] (2007(?)-2011)
* [[User:DrewMcLellan|Drew McLellan]] (2007(?)-2011)
* [[User:ScottReynen|Scott Reynen]] (2007(?)-2011)

== see also ==
* [[admin-faq]]
* [[admin-how-to]]
* [[admin-to-do]]
* [[community-robustness]]

to-do

2011-09-21T11:14:29Z

Phae: /* Frances Berriman */ note to add spec list to code and tools page

<entry-title>To Do</entry-title>
__TOC__
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. :) - [http://tantek.com Tantek]

== wiki gardening ==

=== trim fixups ===
Search for all uses of "tr.im" for shortlinks and replace them with "ufs.cc/w/" links that just use the pagename.

* [http://www.google.com/search?q=site%3Amicroformats.org+tr.im Google search for site:microformats.org tr.im]

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

* [[tr.im]]

== microformats specific ==

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

=== for all microformats ===
* We have added a new mailing list called microformats-new. There may be some confusion surrounding this change, so it would be helpful to:
** Draft a message to be added to the confirm message sent when someone subscribes to any list including a welcome message, ground rules, topic for the subscribed list, and the topics for nearby lists.
** Add a faq entry somewhere on why the new list was created.
** Double check the wiki pages to make sure advice on mailing lists is accurate.
* quick and easy "how to" pages for each microformat. [[get-started]] is a good overall start.
* brief summary statements for each microformat that explain why it matters, what does it accomplish for the publisher.
* write up [http://microformats.org/discuss/ mailing-list] questions and answers in the appropriate [[faq]] pages.
* validators. See the hReview section below as there has been a request for an hReview validator in particular. See [http://norman.walsh.name/2006/04/13/validatingMicroformats Norman Walsh's blog post "Validating microformats"] for some valuable analysis and validation pseudo-code (prose description), which are useful steps towards building microformat validators.
* Submit definitions of "microformat", and individual examples, to the [http://foldoc.org Free On-line Dictionary of Computing], acording to [http://foldoc.org/editing.html the Free On-line Dictionary of Computing guidelines]
* it would be nice to replace the -in-the-wild pages with a form that accepted URL entries that would both register the site and look for valid microformatted content and for those pages with problems, would set them aside in a queue to be reviewed by the community. Having such an interface would likely be more efficient for implementors looking to have their work reviewed, and would also add to a ready-database of microformats in the wild -- which would be a great way to feed pingerati.com. [[User:Chris_Messina Chris Messina]] on 2007 Aug 31.
* check with the group and then, assuming this is accepted, remove mention of the profile="" attribute from the wiki, since HTML5 removes the need for profiles to be declared

=== hCard ===
* microformatted versions of conference pages
** Wait for confirmation from O'Reilly webmaster on revision of the [http://conferences.oreillynet.com/etel2006/ ETel] [http://conferences.oreillynet.com/pub/w/44/speakers.html speaker's page] with all the speakers marked up with [[hcard|hCard]] and links to "Add hCards to Address Book" etc., similar to the [http://tantek.com/microformats/2005/web2/speakers.html Web 2.0 speakers page which Tantek did a revision of last fall].
* vcard to hcard converter
** would be nice to have a web upload UI that would take one or more vCards from apple's address book and give them back to you as hCards
** [[User:RobertBachmann | RobertBachmann]] suggests starting points:
*** For Ruby: http://vpim.rubyforge.org/
*** For C: http://freshmeat.net/projects/libvc/
*** For Python: http://www.nongnu.org/python-pdi/
*** For PHP: http://pear.php.net/package/Contact_Vcard_Parse/
** I (Andy Pemberton) started working on this at one point, but haven't touched it in a while: [http://www.andypemberton.com/sandbox/hcardconvert/ vCard-2-hCard]
* add export support for microformats to [http://www.turingart.com/abForWeb_lan__en.htm AB to Web]
* A mash-up with google maps that will take any url with a hcard (or hcard's) and map the location(s) on a map (similar to [http://austin.adactio.com/ austin.adactio.com])
* more test cases - add to [[hcard-examples]] to begin with, then hopefully create test cases for development to be checked in with mercurial to the repository
** include class="type" without explicit value test cases, based on [[hcard#type_with_unspecified_value|hCard type with unspecified value]].

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

* [http://www.k5n.us/webcalendar.php?topic=About WebCalendar]
* [http://phpicalendar.net/documentation/index.php?title=Main_Page PHP iCalendar]
* [http://www.vcalendar.org VCalendar]
* Investigation: [http://wiki.mozilla.org/Calendar_Talk:Lightning#hCalendar_publish_and_subscribe_support Mozilla Calendar / Lightning / Sunbird hCalendar support discussion]

=== hReview ===
* [[hreview|hReview]] support in Ecto (hey Adriaan!), requested by Andy Smith
* an [[hreview|hReview]] validator.
* a semantic, clean css star rating picker (e.g. a UI widget to rate from 1-5 stars)
** both [http://komodomedia.com/blog/index.php/2005/08/24/creating-a-star-rater-using-css/ this] and [http://factorycity.net/demos/drupal/rating/default.html this] have some flaws. Ask [[User:RyanKing|Ryan King]] for an explanation.

=== hCalendar/hCard/hReview editor ===
* onblur in the URL field (e.g. on hCalendar), goes out and tries to retrieve an object of same time (e.g. an hCalendar vevent) from that URL and uses it to autofill the form, same thing if the creator is loaded with that URL prefilled (e.g. due to a ?url=http://example.com/ in the URL that loads the creator).

=== hAtom ===
* [[hatom-issues]] needs sections for closed issues, resolved issues, and open issues sorted by year, similar to [[hcard-issues]].

=== WordPress patches for microformats ===
* submit patches for WordPress code/templates for microformats improvement
** <address class="vcard"> improvement in post author publication (e.g. home page of http://microformats.org/ )
* Wordpress plugin for microformats, specifically hReview and hCalendar
** See [http://www.surfarama.com/index.php?p=227 lazyweb request]

=== 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.

* [http://developer.yahoo.net/yui/ Yahoo! User Interface Library]
* [http://developer.yahoo.net/ypatterns/ Yahoo! Design Patterns Library]
* [http://www.yuiblog.com Yahoo! User Interface Blog]

=== Drupal patches for microformats ===
* [http://groups.drupal.org/microformats-in-drupal Microformat Module for Drupal] A group discussing ways to implement microformats in Drupal. Currently looking to support hAtom, hCard and hCalendar to start with. Contact digitalspaghetti at gmail dot com if you are interested in contributing to the project.

=== Adding Microformats to Existing Pages ===
* See [[advocacy#Adding_Microformats_to_Existing_Sites|advocacy: Adding microformats to existing sites]].

===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 [http://en.wikipedia.org/wiki/Tag_%28metadata%29 Wikipedia page on tagging]. [[User:AndyMabbett|Andy Mabbett]] 14:07, 3 Jan 2007 (PST)

===Glossary===
Add to the [[glossary]].

===hAtom tutorial===
Finish the [[hatom-tutorial]].

=== wiki gardening ===
* Find [[:Special:Lonelypages|orphaned]] pages, and add links to them.
* Use [[templates]] for boilerplate text and repeated lists of links
* Add keywords to the foot of pages (see [[vcard-suggestions]] for examples), so that they can be converted to tags, once this wiki allows the use of "rel" attributes. Keywords can also include synonyms to aid searching.

====Spelling====
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: <nowiki>[[en-US]]</nowiki>. 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.

{| border="1"
|+
! [[en-GB]] !! [[en-US]]
|-
| [http://microformats.org/wiki/Special:Search?search=behaviour&go=Go behaviour] || behavior
|-
| [http://microformats.org/wiki/Special:Search?search=behaviours&go=Go behaviours] || behaviors
|-
| [http://microformats.org/wiki/Special:Search?search=centre&go=Go centre] || center
|-
| [http://microformats.org/wiki/Special:Search?search=colour&go=Go colour] || color
|-
| [http://microformats.org/wiki/Special:Search?search=colours&go=Go colours] || colors
|-
| [http://microformats.org/wiki/Special:Search?search=favour&go=Go favour] || favor
|-
| [http://microformats.org/wiki/Special:Search?search=flavour&go=Go flavour] || flavor
|-
| [http://microformats.org/wiki/Special:Search?search=flavours&go=Go flavours] || flavors
|-
| [http://microformats.org/wiki/Special:Search?search=flavoured&go=Go flavoured] || flavored
|-
| [http://microformats.org/wiki/Special:Search?search=minimise&go=Go minimise] || minimize
|-
| [http://microformats.org/wiki/Special:Search?search=minimises&go=Go minimises] || minimizes
|-
| [http://microformats.org/wiki/Special:Search?search=recognise&go=Go recognise] || recognize
|-
| [http://microformats.org/wiki/Special:Search?search=recognised&go=Go recognised] || recognized
|-
|}

[http://en.wikipedia.org/wiki/American_and_British_English_spelling_differences More American and British English spelling differences]

== Admins ==
This section is for folks to suggest to-do items for [[admins]], in particular, having to do with suggestions for improvements to microformats.org infrastructure such as the wiki. If you do add an item to this list, please sign your username with four tildes: <nowiki>~~~~</nowiki>.

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 ===

* Something broken with the new MediaWiki microformats templates for date modified on delta/version pages? see: https://twitter.com/CogitoStudios/status/32227146466332672

* Want: Right-to-left (RTL) support in the theme for better translating to RTL languages. Per [https://www.facebook.com/permalink.php?story_fbid=10150109554926465&id=214611 this comment on the microformats page on Facebook 2011-02-13]: <blockquote><cite>Sina Cheraghi</cite> > Microformats "I want to contribute in Microformats wiki by translating it into Persian. But lack of RTL (right-to-left) languages (Persian, Arabic, Hebrew and ...) theme causes some problems for me and other contributors."</blockquote>

* New link styles for links to mailing list archive
** Lacking a more concrete suggestion for how to improve such links, I'm inclined to park this in "won't do". [[User:Tantek|Tantek]] 02:39, 10 September 2009 (UTC)

* Add proper styling to phrase elements
** Lacking a more concrete suggestion for how to improve styling of phrase elements, I'm inclined to park this in "won't do". [[User:Tantek|Tantek]] 02:39, 10 September 2009 (UTC)

* Make email addresses editable [[User:Singpolyma|Singpolyma]] 02:47, 26 July 2009 (UTC)
** How would this work and what's the purpose? [[User:Tantek|Tantek]] 02:39, 10 September 2009 (UTC)

== Tantek ==
I'm keeping a few microformats related to-do items here both for my own convenience, and for folks looking to help out with small tasks. If so, just create a new section with your name, and and maybe copy the item there, and put your name next to the item in my list. We'll figure this out as we go along. Thanks, [http://tantek.com Tantek].

=== overall priority ordering ===
# Protect the community from threats (wiki damage, mailing list pain or noise), repair damage, add measures to reduce future damage
# Help publishers with established microformats: [[hcard|hCard]], [[xfn]], [[rel-tag]], [[hcalendar|hCalendar]], [[hreview|hReview]], [[xfolk|xFolk]]
# Help implementers with established microformats
# Iterate on existing established microformats, resolve issues/feedback etc.
# Wiki cleanup/gardening for existing established microformats
# Site usability of microformats.org top-down as an entry point
# Community dynamics, [[process]] and [[principles]] improvements to help guide new microformats developments
# Emerging in-demand microformats: [[hresume|hResume]], [[hlisting|hListing]], [[citation]], [[media-info]] using abovementioned process and principles improvements.
# New microformat requests
# Document microformats [[history]].
# Other

=== protect the community ===
* Analyze [[Special:Recentchanges]] and [http://microformats.org/discuss mailing-lists] and:
** add to [[mailing-lists]] and [[how-to-play]] policies/guidelines accordingly.
** redirect and resolve threads accordingly per guidelines
** privately email violaters kindly asking them to improve their behavior
** work with admins on next steps for individuals negatively impacting the community
** recognize noisy/distracting threads on the email list, document responses/answers to such subjects on the appropriate page(s) on the wiki, and reply to those threads with the URLs to the documentation on the wiki. Putting the responses/answers on the wiki helps by hopefully providing preemptive answers to some who might reraise the subjects on the list in the future, and helps the community quickly terminate such threads by using the answers on the wiki.
** move exploratory discussions which are failing to follow the process to a separate page from that
** repair damage done to the wiki
*** identify damage done to the wiki - often in forms as simple as content changes that hurt usability (and thus accessibility)
*** document additional [[how-to-play]] guidelines to discourage and hopefully reduce such wiki damaging behavior in the future
*** repair/undo/reorganize page section division that hurt usability (and thus accessibility)
**** [[hcalendar-examples-in-wild]]
***** afterwards add some of the excellent conference schedule calendars that [[User:Adactio]] has been creating like:
****** http://adactio.com/extras/schedules/barcampbrighton3/
*** repair/undo/reorganize page splitting that hurt usability (and thus accessibility)
**** [[to-do]]

=== help publishers ===
==== solve problems blocking publishers ====
* [[value-class-pattern]]
** <del>drafted</del>
** <del>[[value-class-date-time-tests]] - finish writing date and time tests</del>
** <del>put out call for review, implementation,</del> and value-title tests

===== minor update current specifications =====
* draft hCard 1.0.1: [[hcard|hCard spec]] '''next-actions''':
** <del>resolve remaining [[hcard-issues|hCard issues]]</del>
** close remaining [[hcard-issues-resolved|hCard resolved issues]] by writing necessary [[hcard-faq|FAQ]] entries, updating [[hCard]], and adding to [[hcard-brainstorming]] for 1.0.1 and 1.1.
** draft [[hcard-1-0-1]] by starting with [[hcard-1-0]] and incorporating [[hcard-brainstorming]] targeted for 1.0.1.
** incorporate [[hcard-feedback]]
** continue updating the spec per the inline comment about property references
** add a brief descriptive sentence for each property, similar to what [[hreview|hReview]] has. just enough so that the casual reader can avoid having to reference and read the respective sections in [[RFC2426]]. add any non-trivial information about each property similar to what [[hreview|hReview]] has.
** iterate [[hcard-parsing]] with [[value-class-pattern]] as a required feature
** iterate [[hcard-parsing]] with sufficient table element special handling to do people equivalent of [http://microformats.org/wiki/hcalendar- brainstorming#Tabular_event_calendars]
** iterate [[hcard-parsing]] with how to handle new or different [[HTML5]] markup such as the <code><time></code> element, including at least one test case with the <code><time></code> element.
** [[hcard-brainstorming]] '''next-actions''': determine which brainstorms proposals to resolve for minor revision, and which later
** Update [[semantic-xhtml]] with lists of semantic [http://www.w3.org/TR/html401/index/elements.html elements] and [http://www.w3.org/TR/html401/index/attributes.html attributes].
** Update [[hcard-brainstorming]] on element specific parsing rules
** Update X2V, hKit, Operator accordingly
** Write test cases accordingly
** Update [[hcard-parsing]] accordingly
* draft hCalendar 1.0.1: [[hcalendar|hCalendar spec]] '''next-actions''':
** <del datetime="2009-10-03">resolve all outstanding [[hcalendar-issues]] into [[hcalendar-issues-resolved]]</del>
** close remaining [[hcalendar-issues-resolved|hCalendar resolved issues]] by writing necessary [[hcalendar-faq|FAQ]] entries, updating [[hCalendar]], and adding to [[hcalendar-brainstorming]] for 1.0.1 and 1.1.
** draft [[hcalendar-1-0-1]] by starting with [[hcalendar-1-0]] and incrementally incorporating [[hcalendar-brainstorming]] targeted for 1.0.1
** incorporate [[hcalendar-feedback]]
** itemize a complete property list similar to the [[hcard#Property_List|hCard property list]], drawing upon hCalendar experience, iCal-BASIC draft(s), ietf-calsify mailing list and other sources to derive the precise list. Separate common properties up front.
** add a brief descriptive sentence for each property, similar to what [[hreview|hReview]] has. just enough so that the casual reader can avoid having to reference and read the respective sections in [[RFC2445]]. add any non-trivial information about each property similar to what [[hreview|hReview]] has.
** significantly update and thoroughly specify [[hcalendar-parsing]] with [[value-class-pattern]] as a required feature
** formally document [http://microformats.org/wiki/hcalendar- brainstorming#Tabular_event_calendars]
** iterate [[hcalendar-parsing]] with how to handle new or different [[HTML5]] markup such as the <code><time></code> element, including at least one test case with the <code><time></code> element.
** [[hcalendar-examples]]
*** make sure all hCalendar examples that reference whole days use best international/accessible date format of YYYY-MM-DD
*** add explicit explanation and examples for LOCATION [[hcard|hCards]] and ATTENDEE [[hcard|hCards]], perhaps on a separate [[hcalendar-examples]] page.
** Write [[compound-parsing]] by abstracting commonalities between [[hcard-parsing]] and [[hcalendar-parsing]].
* draft hReview 0.4
* resolve hAtom issues
* co-edit hAtom per permission from David Janes
* draft [[hAtom]] 0.2
** Clarify that "published" property values may omit seconds, and that converters to Atom are expected to imply ":00" seconds.
* add sections for comments/opinion from community as well as issues subsection
* solicit feedback
* when sufficient consensus and issue resolution achieved, archive previous versions of specs, and update spec pages accordingly.

==== social network portability ====
Iterate on:
* [[social-network-portability]]
* [[hcard-supporting-user-profiles]]
* [[hcard-xfn-supporting-friends-lists]]

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:
* how to author/publish hCard user profiles - write this up in [[hcard-authoring]] first (see below) and then use that content.
* how to author/publish hCard+XFN friends lists - write this up in [[hcard-xfn-authoring]] (see below) and then use that content.
* how to parse/subscribe to hCard user profiles - write this up by updating: [[hcard-parsing]], and writing [[hcard-supporting-user-profile-parsing]] (collect this into parsing/developers tasks below)
* how to parse/subscribe to hCard+XFN friends lists - write this up by writing: [[xfn-parsing]], [[hcard-xfn-supporting-friends-list-parsing]] (collect these into parsing/developers tasks below)
** notes/thoughts on hCard+XFN supporting friends list parsing captured here for now:
*** do a full rel="me" bidirectional crawling within the domain - some sites' hCard supporting user profiles simply link to their hCard+XFN supporting friends lists with rel="me", and thus you will discover more pages with friends lists.
**** E.g. Flickr's /people/username pages have hCard for the user and link to their /people/username/contacts page with rel="me" (on the "More..." link, though they could also add rel="me" to the number inside "Your contacts (592)"). Need to get them to support hCard+XFN on the contacts themselves.
*** consider parsing within a friends list page, any links that are rel="next" and rel="prev" to iterate over the whole list.

==== foldup cheatsheet ====
'''next actions''':
* gather feedback on current foldup [[pocket-cheat-sheet|pocket cheatsheet]]
* document the [[pocket-cheat-sheet-feedback|feedback on the pocket cheatsheet]]
* provide printing recommendations for anyone to download and print their own
** Perhaps [http://www.visibone.com/ Visibone] can be of some use? I can recommend their current products. --[[User:Gazza|Gazza]] 06:41, 7 Apr 2007 (PDT)
* update cheatsheet to include new [[value-class-pattern]] uses
* give feedback to Erin or ask for volunteers to create a new cheatsheet, iterate, print more to have on hand, fold, distribute.
* discuss with [[User:Adactio]] and Hannah how to best create a UK/A4 version of the pocket cheatsheet
** preferably well in advance of dConstruct 2008 so that local cheatsheets can be printed.

==== *-authoring microformats wiki pages ====
* [[hcard-authoring]] - '''next-actions''': add tips/instructions noted below.
** instructions for each property that is in [http://microformats.org/code/hcard/creator hCard creator] to begin with
** instructions for all other hCard properties
** a tutorial on creating an hCard for your site
*** specific instructions for common blogging platforms
** reference [[hcard-examples]] for more specific uses, and add to them accordingly
*** add an extended example to [[hcard-examples#Authors_of_Pages_and_Posts|contact info for a page]] with postal address, phone numbers, email address.
* [[hcard-xfn-authoring]] - '''next-action''': draft by starting from hCard+XFN instructions in [[hcard-examples]].
* [[hreview-authoring]] - '''next-action''': create a first draft minimal tutorial on how to author hReviews (e.g. at least for common properties) to blog reviews so that they'll be aggregated.
* [[hcalendar-authoring]] - '''next-action''': add tips/instructions for each property that is in [http://microformats.org/code/hcalendar/creator hCalendar creator].
* *-authoring for other reasonably well established microformats:
** [[xfolk-authoring]], [[hatom-authoring]]

==== 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|hCalendar]] and [[hcard|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:
* Flickr.com (3.5m hCards)
* Upcoming.org (100k hCalendar events, 100k hCard venues)
** home page
* Eventful.com (100k hCalendar events, 100k hCard venues)
* Yahoo! Tech (300k products with hReviews)
* JudysBook.com (???k hReviews)
* ... lots more, get from "Implementations" and "Examples in the Wild" sections of specs.

==== advocacy for obvious sites ====
* [[advocacy]] - add pages/sites that obviously (no pun intended) could use microformats, update them with sample markup, find contacts for those pages to get them updated, and send requests to update their sites with microformats including sample markup. '''next-actions''': markup both twitter.com sample pages and dodgeball.com sample pages, post the changes publicly, and see which one is able to update first ;)
** dodgeball.com (hCard + XFN + hAtom for profiles, hCard + hReview for venues)
** write essay on [[open-data-more-important-than-open-source]] - and a shorthand URL too.
*** obviously doing both is ideal, however, open data is a higher priority and given limited resources, open data should be implemented before open source.
*** open data > open source
*** "open information" vs "open source"
*** i.e. please focus first on open data rather than open source, e.g. start with [[hcard|hCards]] for all organizations returned from http://wiserearth.org/organization
*** if the data is open you can always export it and consume it in any number of open source systems
*** that's why open data is MUCH more important than open source
*** adding open data (e.g. microformats) can be done by any HTML author (yes, you), whereas open sourcing requires programming expertise, resouces, support. do the simpler easier thing first (open data thru microformats) that will benefit more people sooner.
*** if the data was open, anyone could rebuild an accessible version
*** faqs / misconceptions:
**** eschipul: @tantek - creating microformats is easier. consuming microformats is unfortunately not easier.
***** A: If you think consuming microformats is not easier or hard etc., it may just be that you don't know how to do so easily, don't assume that you are an expert in something that you think is hard. Rather, if you think something is hard, then assume others may know easier methods, and ''ask'' the community how one can do it more easily. parsing in particular is something which is becoming easier and easier thanks to open source libraries like [[hkit|hKit]].
** write essay on [[open-data-more-important-than-open-apis]] - and a shorthand URL too
*** obviously doing both is ideal, however, open data is a higher priority and given limited resources, open data should be implemented before open APIs.
*** publishing/providing open data (e.g. microformats) can be done by any HTML author (yes, you), whereas providing/publishing open APIs requires programming expertise, resouces, and support. do the simpler easier thing first (open data thru microformats) that will benefit more people sooner.

=== help implementers ===
* wordpress improvements
** WP admin for new profiles
*** should simply read blog URL - '''next-action''': make sure a bug/feature request is filed with wordpress.org
*** look for hCards and parse them

* [http://gmpg.org/xfn/creator XFN Creator] localizations
** Get someone to verify the [http://gmpg.org/xfn/creator-ru XFN Creator Russian localization].
** Add it to the [http://gmpg.org/xfn/tools XFN Tools] page.
** Add rel="alternate" href="creator-ru" <link>s to the other XFN Creators.

* Conference Schedule Creator
** '''next-actions''': Review Dmitry Baranovskiy's [http://dmitry.baranovskiy.com/work/csc/ Conference Schedule Creator] and give him feedback per how well it:
*** Makes it *trivial* for conference organizers to build/edit/publish an [[hcalendar|hCalendar]] schedule for their conference, including auto-generated "Subscribe..." link which produces the proper "webcal:..." link with X2V. Note: see the "axis" and "header" attributes in HTML4, specifically in the section on Tables.

=== iterate on current microformats ===
==== in general ====
===== plain language intros =====
For [[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], [[xoxo|XOXO]] to start with, write up:
* brief plain-language intro at the top (say for example, something that a non-technical person like a member of the general media/press could read and understand), similar to or better than plain language intros on W3C specs.
* followed by links to more plain-language resources, e.g. *-intro pages.
In particular for [[xoxo|XOXO]], Angus McIntyre suggested:
* As well as a syntactic example, examples of use would be useful.
* when I might want to use XOXO.
* Some simple examples right upfront would probably do a lot to help users figure out whether a particular microformat is for them or not.
These suggestions could be incorporated into the other specs as well.
===== exploratory discussions =====
* update [[exploratory-discussions]] with critical microformats as "active"
===== CSS enhancements for =====
Analyze existing microformats for opportunities to enhance CSS and propose to W3C.
* e.g. CSS datetime presentation (need to add links to my earlier work in CSS working group)
* brainstorm additional possibilities for better presentation of content using existing microformats.
===== update affiliations =====
* Start a minimal draft/spec style guide using outline of most readable/accessible spec so far
* Reference http://www.w3.org/2001/06/manual/#Editors for how to manage affiliations
* Update affiliations on [[hcard]], [[hcalendar]], [[hreview]], etc. per http://www.w3.org/2001/06/manual/#Editors
===== profile URLs =====
* write-up and document [[profile-uris|profile URLs]] for all established microformats and perhaps for some drafts as well

==== [[hcard|hCard]] ====
Combined next-actions for iteration on [[hcard|hCard]], and derived/subsetted microformats [[adr]] and [[geo]]
* [[hcard-profile]] '''next-actions''':
** update property definitions with more detail using semantics from [[RFC2426]]
** link from brief sentence descriptions for each property in [[hCard]] to the respective more detailed definition in the [[hcard-profile]].
** link from definitions in the [[hcard-profile]] to the specific sections in the vCard spec
* [[hcard-examples]] '''next-actions''': update with examples described below
** add examples of [[hcard|hCard]]s with work telephone, mailing address etc.
** add examples of marking up an organization vs. a person, then link to it from [http://microformats.org/wiki/hcard#Organization_Contact_Info hCard spec section on Organization Contact Info].
** add example of organization-name and organization-unit usage.
* [[hcard-brainstorming]] '''next-actions''': explore brainstorms proposals for a 1.1 revision, e.g.
** need property for gender (see [[hcard-faq#How_is_gender_represented|proposal in hCard FAQ]] and discussion in [[hcard-issues]]) - use tags for now, add to hCard creator
** solve [[hcard-brainstorming#Auto-Discovery|autodiscovery]] of more canonical/thorough hCard
* [[hcard-examples-in-wild]]
** help dglazkov markup: http://glazkov.com/blog/archive/2003/12/17/147.aspx

* analyze [[hcard-cheatsheet]], [[adr-cheatsheet]], [[geo-cheatsheet]] for any assertions above and beyond what the specification itself says, take into account [[hcard-brainstorming]] along similar lines, and incorporate into the spec or remove as necessary and sync-up as a result. add clarification on the cheatsheets that they are '''informative''' and reference the specification for normative requirements.

==== [[hcalendar|hCalendar]] ====
'''Next-actions''':
* update [[hcalendar-examples]]
** add examples like [[hcard-examples]]
** flesh out and do a once over on markup/presentation of what RFC2445 examples would look like
** update all hcalendar-examples to use value-title from [[value-class-pattern]] where abbr doesn't make sense. e.g.
*** rrule
*** duration
*** ... etc.
* need spec details and then [[hcalendar-examples]] of multi-instance [[hcalendar|hCalendar]] events
* need spec details and then [[hcalendar-examples]] of repeating events
* have folks verify [[hcalendar-profile]]. Note that it will likely need reconciliation with the [[hcard-profile]], especially since [[hcalendar|hCalendar]] normatively depends on [[hcard|hCard]]. Probably makes sense to have a combined profile which hCalendar would use.
* analyze [[hcalendar-cheatsheet]] for any assertions above and beyond what the specification itself says, take into account [[hcalendar-brainstorming]] along similar lines, and incorporate into the spec or remove as necessary and sync-up as a result. add clarification on the cheatsheets that they are '''informative''' and reference the specification for normative requirements.

==== [[hreview|hReview]] ====
'''Next-actions''':
* reconcile [[hreview-profile|hReview 0.4 XMDP profile]] with [[hcalendar-profile]] and [[hcard-profile]]. Makes sense to have a combined profile of all three for hReview, since hReview normatively depends on hCard and hCalendar.
* Resolve all outstanding [[hreview-issues]] and [[hreview-feedback]] to-do items.

==== [[rel-tag]] ====
'''Next-actions''':
* send [[rel-tag]] XMDP profile ([[rel-tag-profile]]) to [http://dbaron.org/ David Baron].
* Resolve all outstanding [[rel-tag-issues]] and [[rel-tag-feedback]] to-do items.

==== [[rel-me]] ====
'''Next-actions''':
* move XFN and XMDP FAQs, tutorial, descriptions, spec etc. from gmpg.org to microformats.org
** and put redirects in place, notes about contribution
* update rel-me examples and document with examples the rel-me implict subdir rule

==== [[hatom|hAtom]] ====
'''Next-actions''':

==== summary Examples in the Wild page ====
* need to create a summary / overall [[examples-in-the-wild]] page
** parallel the summary/overall [[implementations]] page.
** use newly reorganized content from the above "reoganizing Examples in the Wild" task

==== parsing ====
'''Next-actions''':
* Draft *-parsing for all reasonably well adopted microformats: [[hreview-parsing]], [[xfolk-parsing]], [[hatom-parsing]]

=== wiki cleanup ===
==== for all microformat specs ====
'''Next-actions''':
* modularize any specs which are > 30K in order to avoid loss/corruption like [http://microformats.org/wiki?title=Special:Contributions&target=Evan Evan's 14 June edits] to [[hcard|hCard]], [[rel-tag]], and [[xoxo|XOXO]].
** [[hcard|hCard]] -
*** [[hcard-examples-in-the-wild]] group/sort by individuals, organizations, and hosting sites. Consider moving largest subsection to its own page as well.
** [[rel-tag]]
** [[xoxo]]

==== update specification section organization ====
'''Goal''': greater approachability/readability of microformats specs by a broader audience.

Reference:
* [[hresume|hResume]] has an experimental abbreviated intro/headers section, and links to more details further below, based on some ideas that Ryan King and I had for improving the readability of the microformats specifications.
* [[hreview|hReview]] has some similar improvements, but different.
* [[hcard|hCard]] has numerous improvements as well, again different from either hResume or hReview

'''Next-actions''':
# 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.
# figure out if the new intro/headers etc. structure/order in [[hcard|hCard]], [[hreview|hReview]], and [[hresume|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
# Design an iterative update to spec organization, in particular, the introduction/boilerplate/headers.
# Write up a template - make it self-documenting per the requirements
# Update existing specifications with the new intro/headers structure.
## [[hcard|hCard]]
## [[hcalendar|hCalendar]]
## [[hreview|hReview]]
# 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 ====
* sort implementations by authoring/creating/publishing, browsing/viewing, converting/importing, indexing/searching.

Hmmm... I like: '''A'''uthoring, '''B'''rowsing, '''C'''onverting, '''I'''ndexing, '''L'''ibraries (for developers), and '''P'''otential (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: [http://microformats.org/wiki/hcalendar#Implementations 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.

'''Next-actions''':
* [[hcard-implementations]] - re-organize by same subsections as [[hcalendar-implementations]].
* [[hreview-implementations]] - re-organize by same subsections as [[hcalendar-implementations]].
* [[hatom-implementations]] - re-organize by same subsections as [[hcalendar-implementations]].
* [[xfolk-implementations]] - re-organize by same subsections as [[hcalendar-implementations]].

==== reorg Examples in the Wild sections ====
Work with community to:
* include more *key* details per example, e.g. precise or estimates of counts for services
* collate/sort examples in the wild by
** hosting services - where users/people actively contribute to the growth (e.g. Flickr profile hCards)
** publishing services - where lots of data is published from some datasource/database (e.g. Yahoo! Local)
** companies/groups/organizations member pages (and their own) - pages for a group's site where they list members or employees (e.g. Technorati staff page)
** individiual companies/organizations contact info pages
** individual people's contact info pages
* of course at some point this won't scale, but that will be a very good problem to have, and by then I'm sure we'll have services to point to that provide queries and search results for all this data.

=== site usability ===
* figure out how to get wordpress to autopost blog posts to the microformats-announce list
** ideally use the from address of the author of the blog post
** maybe photomatt knows how to do this.

=== introduction / community ===
* microformats-discuss *
** introductory email template for new subscribers needs to direct people to [[process]] and [[how-to-play]]
* Need to add more to the [[naming-principles]], to cover in particular:
** avoid using the same name to mean two things
** avoid using two names to mean the same thing
** seek to keep the microformats vocabulary minimal, memorable, and usable.
* update and add details/simplifications to [[process]] given the past several months of experience. in particular:
** clarify requirement (MUST rather than SHOULD) of *-examples, *-formats, before any *-brainstorming.
** Add details of encouragement to experiment with simple semantic class names from *-brainstorming proposals to gain real world experience with real world content.
** note SHOULD prerequisite of use of all relevant microformats on real world web pages, along with documenting such use in respective "Examples in the Wild" sections, before proposing any new microformats.

==== posh improvement ====
* Create a page to answer the question "[[how-should-i-markup]]"
* consider creating a process/encouragement for collecting individual [[posh]] practices and examples, like a folksonomy of semantic HTML and semantic class names.

==== principles and process ====
Create the following pages and document/fill them with content from other pages, email lists, and [[presentations]].
* [[principles]] - mostly [[microformats#the_microformats_principles|documented in the microformats]] page.
* clearer statement of both copyright and patents both in specific specs and in general
* resolve [[process-issues]]

==== profiles ====
* update [[XMDP]] with new required features:
** ability for one profile to include/import another (rel="import" ?)
** ability to reference an XMDP via rel="profile" (similar to XHTML2 rel value by same name)
*** add rel="profile" to the [[xmdp-profile]].
** ability/suggestion to reference an XMDP using <a href> in addition to <link>

==== community mark ====
* Can we make "microformat" and "microformats" into [http://factoryjoe.com/blog/2006/01/14/the-case-for-community-marks/ Community Marks]?

==== document issue resolutions ====
* Prefixing has already been considered and rejected for microformats in general. Note [[naming-conventions]], limited vocabulary, and exceptions made for [[hatom|hAtom]] and how we went about doing so.

=== emerging microformats ===
* [[directions]]
* [[citation]]
* [[hlisting|hListing]]
* [[media-info]]
* [[licensing]]
'''Next-actions''' for each emerging microformat (one at a time)
* review all microformats-email on the new microformat
* determine where new microformats is "stuck" in the process
* brainstorm about how to improve process (or documentation thereof) to get the effort unstuck
* work with community to move the microformat forward through the process, iterating/clarifying the [[process]] as necessary

=== new microformat requests ===
* expense reports (really just a list of "expense" items), [http://flickr.com/photos/edyson/56774178/ requested by ED], should look at UBL as a pre-existing format
* photo-notes microformat
** clean up Subethaedit notes from working session with Greg Elin, Ryan King, Kevin Marks, Suw Charman and email to folks and figure out next steps
** iterate on [[photo-note-examples]] and start [[photo-note-formats]] and [[photo-note-brainstorming]].

=== document microformats history ===
Document microformats [[history]], including:
* dates and origins of microformats, names, terms
* examples and formats for established microformats like [[hcard|hCard]], [[hcalendar|hCalendar]], [[xfn]], [[rel-license]], [[xoxo]]

=== other ===
* Add XPath equivalents where appropriate in [[hcard-parsing]]

==Ryan==
=== wiki cleanup ===
* <s>possibly move dead proposals off of homepage?</s>

=== hCalendar/hCard/hReview creator improvements ===
* get all creators working in IE/Win, IE/Mac, Safari/OSX.3

=== other ===
* add an example of how to use DURATION in hcalendar see http://www.policyawareweb.org/2005/ftf2/paw-mtg#item15) -> verify http://svn.lifelint.com/hcalendar_tests/calendar-todo-multiple-attendees-and-alarm.xml

=== rel-payment ===
* update rel-payment to reference the IANA registry [http://www1.ietf.org/mail-archive/web/ietf-announce/current/msg02055.html]

=== hcalendar ===
* make sure we explicitly disallow 'vjournal'

== Dimitri Glazkov ==

* Figure out REST/Microformats thing
* Work on result set idea
* Implement h-creators using Web Forms 2.0

== Chris Messina ==

=== General ===

* Work on a microformat for play-lists (is it just a XOXO ordererd list of play-items?)
* Work on a microformat for play-item (take a look at [[media-info-examples]])
* Work on microformats tutorial for designers
* Add support for OpenID to micformats wiki
* <strike>Add support for [http://verselogic.net/projects/wordpress/wordpress-openid-plugin/ OpenID] to the microformats blog</strike>.
* <strike>Read GTD (at least the first two chapters)</strike>.

=== Campaigns ===

* <strike>Get Blogger to support hAtom and hCard</strike>
* <strike>Get LinkedIn to support hCard, hResume, hCalendar</strike> and XFN
* Get XING to support <strike>hCard</strike>, hCalendar, hResume and XFN
* Get <strike>Digg to support microformats</strike> (still need XFN).

=== Wishlist ===

* Microformat for "buyable items" (see [[listing-examples]] and related documents)
* Location MF -- right click "map this" (see [[geo]] and [[adr]])
* Better hCard support in the browser -- right click "IM this person...", "Add to contacts" (see [http://factoryjoe.com/blog/2006/03/20/flocktails-for-flock/ Flocktails])
* Better hCal support -- support many views of same hCal data on one page using XSLT
* We need something that a designer/web programmer can come to and leave w/ 2 examples of each microformat that they can apply right away... a "microformats styleguide for designers", if you will.
* invoicing microformat
* better microformats wiki theme
* Define flow for OpenID + XFN + hcard (see [http://diso-project.org DiSo Project])

Hey Chris.
Congrats on Microsyntax
([http://factoryjoe.com/blog/2009/05/26/stowe-boyd-launches-microsyntax-org/ "Stowe Boyd launches Microsyntax.org"]).
So ... do we need a page on this Microformats wiki describing the connection between microformats and microsyntax?
When the Microsyntax wiki goes online, please add a link to it on the Microformats [[WikiNode]] page.
--[[User:DavidCary|DavidCary]] 08:34, 4 June 2009 (UTC)

== Robert Bachmann ==
[[User:RobertBachmann|Robert Bachmann]]

=== XSLTs ===
<ul>
<li>Test scripts
<ul>
<li>Do some refactoring, split Perl code into smaller modules</li>
<li>Provide test results as HTML pages (similar to http://www.w3.org/2003/08/owl-systems/test-results-out)</li>
<li>Provide some documentation for using the test scripts</li>
</ul>
</li>
<li>hAtom2Atom
<ul>
<li>
Join all hfeed's inside a page (or a fragment thereof) into one feed using [http://greenbytes.de/tech/webdav/rfc4287.html#element.source atom:source] semantics.
</li>
<li>
Extraction of <code>atom:content</code>, <code>atom:summary</code> and <code>atom:title</code>:
* <code>atom:content</code> and <code>atom:summary</code> as HTML
* <code>atom:content</code> and <code>atom:summary</code> as plain-text
* <code>atom:title</code> as XHTML
* <code>atom:title</code> as HTML
</li>
<li>Support for other XSLT engines:
* .Net System.Xml
* hAtom2Atom written using XSL 2.0?
** Do you think this would be useful? I have created a barebones version, doesn't yet take in all the parsing rules yet, but I'd be happy to share. Moving to XSL 2.0 does make things a bit cleaner and more efficient. - Matt Dertinger.
</li>
<li>Support for other output formats: (hAtom2xyz.xsl)
* RSS 2.0 (meanwhile use hAtom2Atom.xsl and [http://atom.geekhood.net/ atom2rss.xsl]) -- +1 Matt Dertinger
* RSS 1.0 (meanwhile use hAtom2Atom.xsl and [http://cvs.4suite.org/viewcvs/uogbuji/atom2rss.xslt atom2rss.xslt]) -- +1 Matt Dertinger
** My opinion at the moment, I neither want to produce nor to consume RSS. Atom is nicer (and should be supported by most good feed readers available today), RSS should fade away. -- Robert Bachmann
* AtomOWL (meanwhile use hAtom2Atom.xsl and [http://dannyayers.com/2005/11/22/atomowl-xslt-progress/ atom2rdfxml.xsl])-- +1 Matt Dertinger
** Having the possibility of GRDDL-ing hAtom to AtomOWL seems definitly interessting. I realy should implement this some day. - Robert Bachmann
* JSON?
** Does it make sense to consider a canonical representation of microformats (either case by case, or in general) in JSON? E.g. so that a JSON API that returned contact information could return an hCard-equivalent chunk of JSON. - Tantek.
*** This could enable some nice JavaScript hacks. I should give hAtom2JSON a try. - Robert Bachmann
</li>
</ul>

([[User:Singpolyma|singpolyma]] 01:02, 9 May 2006 (PDT) -- Not XSLT, but see http://xoxotools.ning.com/hatom2rss.php for hatom to RSS2.0 conversion)
</li>
</ul>

== Brian Suda ==
=== Citation Microformats ===
* Add all my notes to the Wiki
* Start the process of naming the properties using existing names

=== X2V ===
Make changes and update site (almost stable)
Get ATTENDEE and other strange attributes working
==== WARNINGS and ERROR ====
work on the warnings and error output for the pre-check in X2V

=== FAQ ===
* clean-up the MF FAQs
* clean-up FAQs from the major microformats
* pull Questions from the mailing list and document them to the FAQs and example

=== Microformats History ===
* get early work from developer.technorati site
** issues with MoinMoin full history: http://moinmoin.wikiwikiweb.de/MoinMoinQuestions/UsingTheWiki#head-9d1b1d6beedde40b92cc6c13962b5a6f5b289d10

=== additions to the wiki ===

* better explain why NOT infinitely scaling is a good thing
* better explain why microformats do NOT use namespacing

== Mark Rickerby ==

=== Current Tasks ===

* Follow up on usability review
** Edits to homepage feature box text
** Draft of [[getting-started]] page
* Review content for new pages - [[start-simple]], [[modularity]], [[reuse]], [[humans-first]]
* xoxo datatype examples
** test case lists
** transmitting key/value lists
* practical feedback on hresume

=== Wishlist ===

* hmmm

== 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.

==== Goals ====
# Improve understanding of what needs to be done for Wiki
#* IMHO - this should be done here, in [[to-do]] incrementally. -Tantek
# 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
# Motivate community to have fun with otherwise tedious "housecleaning" chores

==== Agenda (Wishlist) ====
In parallel:
* Coalesce/prioritize existing To-Do items (above)
* Review/revise desired pathways for:
** New users learning about microformats
*** e.g., intro, about, explore, tutorials, etc.
*** cf. [http://www.rubyonrails.com/ Rails] front page
****Get Excited (Why, background, motivation)
****Get Started (What, downloads, getting started)
****Get Better (How, tutorials, )
****Get Involved (Who)
** Microformat lifecycle
*** e.g., research->brainstorm->proposal->spec->maintain
*** see http://theryanking.com/microformats/method.txt --[[User:RyanKing|RyanKing]] 15:35, 22 Feb 2006 (PST)
*** ensure information easy to find, follow, and up-to-date
* Review existing specs for completeness and consistency
* Identify areas of 'bitrot' or 'hole-filling'
* Do it!

== Dan Connolly ==

[[User:DanC|DanC]] hopes to sync up on these tasks in [[irc]] roughly
weekly, during Wednesday afternoon (Chicago time) "office hours". See also my [http://esw.w3.org/topic/DanConnolly esw todo list and someday pile].

* from SxSW in Austin
** build a combined hcalendar/hcard profile; resolve issues in [[profile-uris]].
*** with XSLT transformation to RDF
** finish [[hcard-tests]]
*** figure out [[include-pattern]] boundaries

* Medium term
** sync [[hcalendar-tests]] and [http://www.w3.org/2002/12/cal/ RDF calendar] tests and CALSIFY
*** reconsider RDF calendar naming conventions
** update my CV/resume using [[hResume]] and [[citation-formats]]
*** get an answer from the CALSIFY WG re [http://lists.w3.org/Archives/Public/www-rdf-calendar/2006Apr/0006.html dtstart and date vs datetime ] 21 Apr 2006
*** refine [[hatom]] so that it's suitable for the workflow around the W3C homepage.

* from WWW2006
** follow up on GRDDL as escape valve for microformats proposals, much like CSS was an escape valve for HTML tag proposals.

* Someday pile
** set up a timezone registry based on wikipedia and semantic mediawiki. As discussed in [[datetime-design-pattern]], iCalendar's by-value timezone passing is broken. see [http://lists.w3.org/Archives/Public/www-rdf-calendar/2006Apr/0002.html reconsidering timezones in light of hCalendar and CALSIFY] and [http://dig.csail.mit.edu/breadcrumbs/node/91 Toward Semantic Web data from Wikipedia]
** noodle on a playlist format and some of the media RSS stuff like [[media-info-brainstorming]], [[media-metadata-examples]] (re playlists: XSPF, SMIL, RDF, and microformats 9 Sep 2005)
** check out that hReview bug stuff...
** noodle on [[meeting-minutes-brainstorming]] and [http://esw.w3.org/topic/MeetingRecords MeetingRecords in the esw wiki].
** noodle on clipboard scenarios, esp how RDFa works in the general case but isn't as author-friendly as domain-specific syntaxes.

[[User:DanC|DanC]] 15:39, 31 May 2006 (PDT)

== Chris Casciano ==

[[User:ChrisCasciano|ChrisCasciano]]

* get around to updating [[hatom-issues]] with some multi feed rules/exceptions.
* <del>Update textpattern plugin with simple hreview support and get a new release out</del>
* Redesign placenamehere.com and include hatom
* Follow up with technorati folks on pingerati reviews getting lost (note: this will require publishing more reviews and theen watching them through the update process)
* <del>prototype a NetNewsWire microformat extractor (CSS+AppleScript)</del>

== Drew McLellan ==

[[User:DrewMcLellan|DrewMcLellan]]

* Build an hReview profile for [http://allinthehead.com/hkit/ hKit] and test
* Update the [http://www.webstandards.org/action/dwtf/microformats/ Dreamweaver extensions] to mirror recent changes in the online builders
* <del>Publish an hCard to JSON service on [http://tools.microformatic.com/ tools.microformatic.com] using hKit.</del>
* Further develop blog comment form hCard collection ideas.
* Version of hReview creator using hKit to import business details from an hCard

== Christophe Ducamp (french localization) ==

[[Christophe Ducamp]]
* seed "microformateurs group" and invite them to update http://microformateurs.org
** write a process for newbies in order to make them write [[posh-fr|CHIC]] posts on a public blog-governed-by-wiki ([http://socialsynergyweb.net/cgi-bin/wiki/MicroFormateurs/Blog]) before publication.
** find experts for peer-reviewing
** find french CSS gurus to setup a nice Sandbox-CSS template on Wordpress
* translating the wiki
** translate red links on [[Main_Page-fr]] and synchronize
** find out microformateurs at ease on "the-wiki-way-translation", and ready to help on semi-anonymous-synchro
* community-marketing -> pinko-marketing
** public-relations towards french journalists and complete [[advocacy-fr|advocacy]] (especially [[hcard-advocacy-fr]] towards organizations.
** help to build events, workshops like barcamps and explorcamps
** update [http://fr.wikipedia.org/wiki/Microformats French-wikipedia:Microformats] and subpages via cowriting [http://fr.wikipedia.org/wiki/Discuter:Microformats on discussion page] (directly originated from the english article) + french examples to be found + local resources.
** open discussion with french wikipediens about implementing some of the english existing templates
** small gifts: accessories and free gifts ? t-shirts, localized cheat-sheet, id-hcard-openid-providing, etc.
*** create hCard, hCalendar... and all red link pages on french wikipedia
* localize [[species-fr]] and related pages
* move all contents remaining on elanceur.org -> microformateurs.org
* wiki and uf:
** write and talk with "aboutus.org" to invite them to make experiences with uf -> talk with Mark Dilley
** maintain/update http://www.communitywiki.org/MicroFormats and talk with LionKimbro
** XWiki : awaiting beta-test of new platform
*** Follow-up LudovicDubost et LaurentLunati
* setup real-life links with european [[governance-fr|governance]] members ;) may be joining dconstruct-microformats-workshop - find solution (registering fees and travel expenses -> talk with Arnaud Fontaine or search french sponsors)

== Frances Berriman ==

[[User:Phae|Frances Berriman]]

* Clean up this todo list (meta!)
** Move alumni admin tasks out, and into a 'up for grabs' bucket (unless 100% specific to person).
*** Ping anyone with specific tasks / nag
* Proposal for page simplifications - notes, to expand to tasks later:
** Need a way to push active formats (those in the process) to the fore, and push back stagnating items.
** Process updates to blog?
** Activity overview updates on main site somewhere?
*** Code and Tools page on site: Currently it's mostly only tools. Need to add a list of actual specifications on the wiki.
** In general: less clutter, more structure, more focus.

== Ben West (bewest) ==

[[User:BenWest|bewest]]
* fight spam
* help tend wiki
* documentation of semantic authoring techniques
* researching the social problems relating to authorship and publishing on the web
* development of new microformats in response to failing to meet the needs of the second with the first.

=== 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?

=== Vocabulary ===
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:
* "boil the ocean" A huge task. "A phrase used in the industry to describe an attempt at something that is way too ambitious. For example, "They're trying to get their site launched by COMDEX. They could easier boil the ocean." from <http://www.netlingo.com/right.cfm?term=boil%20the%20ocean>
* microformats: more than one microformat
* microformat: see my definition on http://microformats.org/wiki/what-are-microformats#BenWest
* data fidelity: the extent to which a data format might be considered lossy. eg HTML is often seen as a lossy format because the information parsed out of a resource may not fully match the information orginally encoded. Non-lossy formats have a very high data fidelity, while lossy formats have low data fidelity. Microformats seek to increase data fidelity of html.
* market: the locus of economic forces

: See [[glossary]]. [[User:AndyMabbett|Andy Mabbett]] 13:57, 7 Dec 2006 (PST)

=== Creators ===
_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.
* <strike>Start hatom creator.</strike> http://dichotomize.com/uf/hatom/creator.html
* Code Reuse. These creators are downright handy, and I’ve reimplemented the vcard one on my own site. Instead, let’s make these widgetized. Let’s decide on a more or less canonical html structure and create some javascript that will create the desired microformat. Something as easy to use as new Microformat.hCard($('mycontainer')); would be awesome. Right now, if someone makes an improvement to the hCard creator, the other creators don’t get the benefit. Spec this out!
* About Section. Is there an official creator page? If so, let’s point to that. The about paragraph is getting longer and longer with phrases like “which is based on…” repeated over and over.
* Default all dates to “right now”. Provide an easy to use calendar type widget to change dates.
* hAtom creator: Add multiple. It’d be nice to add an arbitrary number of entries.
* hAtom creator: Optional feed enclosure. Check box to wrap the entry/entries in an hfeed.
* Edit URI: Allow someone to enter a URI and edit whatever microformat is found on the page.
* Optionals. If the format requires, say, a vcard, the creator can defer to an external URI or can trust the user to fill it in later.
* Common stylesheet. I suppose this goes with the reuseable code idea… we have many great coders, we should be reusing eachothers’ work.
* Use Amazon's ECS to pull in information about products when there is an ASIN in the item URI.

=== 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 http://simile.mit.edu/solvent/ with the big questions right out front:
* What Is This?
* What can I do here?
* Is there a demo?
* Where can I learn more?
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?
* About the Community
** Where to find information.
** Who are the stake holders?
** FAQs
* Web/Architectural Philosophy
** Community Principles
** Why are we doing this?
** XML and Namespaces
** Semantic XHTML
** Common Misconceptions
** Concession and Disposition of Criticism
** FAQs
* Specs
** Examples
** Discussion
** Exploration
** Use Cases
** Implementations
** The spec itself.

* Tips and Tricks for Authoring ([[User:BenWest|BenWest]] 15:00, 9 Dec 2006 (PST))
** how to author semantic html
** choosing class names
** using HTML's general extension mechanisms
** advocating use
** collaborating/reusing HTML
** debugging HTML: use pastebin, separate out the relevant bits.
** getting help from the community
** applying Microformats.

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:
* Belong to a microformat? (eg hcard-bestof)
* or to the global namespace? (eg /wiki/wisdom/foobar-format)
(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 -- [[User:Cgriego|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.
http://microformats.org/wiki/hcard) 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:

* Microformat
** Specification
** Tutorial
** Examples
** Use cases
** Reference
** Discussion
** Brainstorming (might be combined w/Discussion)
** Implementations
** Related Pages
** Further Reading
** All (Uses Mediawiki's "includes" to create a page including all sub pages; very useful for printing & reading offline)

These pages would be located respectively at

* http://microformats.org/wiki/hcard/
** http://microformats.org/wiki/hcard/Specification
** http://microformats.org/wiki/hcard/Tutorial
** http://microformats.org/wiki/hcard/Examples
** http://microformats.org/wiki/hcard/Use_cases
** http://microformats.org/wiki/hcard/Reference
** http://microformats.org/wiki/hcard/Discussion
** http://microformats.org/wiki/hcard/Brainstorming
** http://microformats.org/wiki/hcard/Implementations
** http://microformats.org/wiki/hcard/Related_Pages
** http://microformats.org/wiki/hcard/Further_Reading
** http://microformats.org/wiki/hcard/All

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) ==

[[User:Thewhoo]]

=== hAtom2Atom ===
<ul>
<li>Support for other XSLT engines:
* hAtom2Atom written using XSL 2.0
</li>
<li>Support for other output formats: (hAtom2xyz.xsl)
* RSS 2.0 (meanwhile use hAtom2Atom.xsl and [http://atom.geekhood.net/ atom2rss.xsl])
* RSS 1.0 (meanwhile use hAtom2Atom.xsl and [http://cvs.4suite.org/viewcvs/uogbuji/atom2rss.xslt atom2rss.xslt])
* AtomOWL (meanwhile use hAtom2Atom.xsl and [http://dannyayers.com/2005/11/22/atomowl-xslt-progress/ atom2rdfxml.xsl])
</li>
</ul>

=== Microformats Proposals ===

* rel="disclaimer":
** Purpose: to create a semantic linkage (relationship) between a foot-note or end-note marker and the actual location of the text that the marker refers to.
* rel="external":
** Purpose: to formalize what is already in existence in the wild. The use of rel="external" to refer to a document that is external or outside of the current domain.

== Henri Bergius ==

[[User:HenriBergius|Henri Bergius]]

* Add hKit support for automatically populating contact details into [http://www.openpsa.org/version2/openpsa/contacts.html OpenPsa Contacts] CRM
* Implement Tail scripts for adding things into Midgard

== Justin Thorp ==
* Start researching examples for a To-do microformat

== [[User:MarkLentczner|Mark Lentczner]] ==

* Get Second Life's event web pages to have proper event microformats data
** Add [[hcard|hCard]] to profile pages
** Add [[hcalendar|hCalendar]] to events listings
* Start pinging pingerati.net/ping/$url when pages are updated
* Collaborate on designing how to integrate microformats, metadata and objects in [http://secondlife.com/ Second Life].

== [[User:DerrickPallas|Derrick Pallas]] ==
=== microformat proposal: dependancy ===
* looking for examples of directed graphs on the web
* applications in
** software engineering
*** automatically build library dependency trees
*** distribute security alerts to people that link to your code
** any directed, acyclic graph
*** getting dressed in the morning
*** cooking
* orthogonal to xfn
** people don't have versions
*** libfoo requires libbar-2.0 or later
** people don't have optional relationships
*** ex: at build time, compile in SSL support if present
** people don't have exclusive-or relationships
*** ex: in Gentoo, syslog, syslog-ng, and metalog satisfy virtual/syslog
*** ex: the Ruby library RMagick requires ImageMagick xor GraphicsMagick

== [[User:PaulDowney|Paul Downey]] ==
* building a generic Javascript parser
* bundling parser as a [http://tiddlywiki.org TidlyWiki] plugin for hCards
* documenting how best to microformat TiddlyWiki pages

== [[User:RobManson | Rob Manson]] ==
* chase the admins to get some creation template extensions installed for wiki (see: http://meta.wikimedia.org/wiki/Inputbox or http://www.mediawiki.org/wiki/Extension:CreateBox or http://www.mediawiki.org/wiki/Extension:CreateArticle)

== [[User:ClayNewton | Clay Newton]] ==
* Work on getting others involved in [[trade-examples]]
** Need examples from major online banking sites
** Need examples from major ecommerce sites
* Continue working on: [[trade-brainstorming]]

== [[User:BenWard | Ben Ward]] ==

=== Recurring ===

* Delete Wiki Spam

=== Currently ===

* Gardening/updating key wiki pages.
** [[how-to-play]]
** XHTML Design Principals
* embed brainstorming
* Considering new welcome banner of µf.org to link to various µf resources, rather than being dominated by the infrequently updated blog.

=== Next Actions ===

* Conclude new hCalendar proposals from Yahoo TV Listings experience
* Resume work on hListing microformat
* Re-org the Microformats.org front-page content
** Work with [[User:Phae]] on refreshing the microformats frontpage content
** Build new events module for the blog using Upcoming.org, rather than hard coded event data (Matt Harris may have done this…)
** Build new wiki edits module for the blog
** Combine ‘list of microformats’ into the intro text? Make intro text more friendly.
* Build a microformats activity stream
** Replace front page blog with activity flow
*** Wiki Edits/New Pages
*** New Mailing List Threads
*** Interesting µf links
*** Blog posts
*** Upcoming events/event reminders
* Improve µf.org/blog OpenID support, find a good workflow for login/comment (current plug-in has an abysmal user experience)

== [[User:Spiritquest|Ketan Majmudar]] ==
=== Activites ===
* Work on developing the [[hlisting-brainstorming|hListing]] proposal
** Provide real world examples and apply this to the proposed specifications
* refine and keep up to date with [[hcard|hCard]] formats as used on existing sites [[http://www.ethical-junction.org| Ethical Junction CIC]]
* Understand / follow and evangalise existing patterns, especially the new [[value-class-pattern]]
* see where I can help the community
* look at using x2v or writing php parser classes for hcard -> vcard
* open source hCard class (php) used to format db fields

to-do

2011-09-21T10:32:13Z

Phae: /* Frances Berriman */ notes for me

<entry-title>To Do</entry-title>
__TOC__
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. :) - [http://tantek.com Tantek]

== wiki gardening ==

=== trim fixups ===
Search for all uses of "tr.im" for shortlinks and replace them with "ufs.cc/w/" links that just use the pagename.

* [http://www.google.com/search?q=site%3Amicroformats.org+tr.im Google search for site:microformats.org tr.im]

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

* [[tr.im]]

== microformats specific ==

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

=== for all microformats ===
* We have added a new mailing list called microformats-new. There may be some confusion surrounding this change, so it would be helpful to:
** Draft a message to be added to the confirm message sent when someone subscribes to any list including a welcome message, ground rules, topic for the subscribed list, and the topics for nearby lists.
** Add a faq entry somewhere on why the new list was created.
** Double check the wiki pages to make sure advice on mailing lists is accurate.
* quick and easy "how to" pages for each microformat. [[get-started]] is a good overall start.
* brief summary statements for each microformat that explain why it matters, what does it accomplish for the publisher.
* write up [http://microformats.org/discuss/ mailing-list] questions and answers in the appropriate [[faq]] pages.
* validators. See the hReview section below as there has been a request for an hReview validator in particular. See [http://norman.walsh.name/2006/04/13/validatingMicroformats Norman Walsh's blog post "Validating microformats"] for some valuable analysis and validation pseudo-code (prose description), which are useful steps towards building microformat validators.
* Submit definitions of "microformat", and individual examples, to the [http://foldoc.org Free On-line Dictionary of Computing], acording to [http://foldoc.org/editing.html the Free On-line Dictionary of Computing guidelines]
* it would be nice to replace the -in-the-wild pages with a form that accepted URL entries that would both register the site and look for valid microformatted content and for those pages with problems, would set them aside in a queue to be reviewed by the community. Having such an interface would likely be more efficient for implementors looking to have their work reviewed, and would also add to a ready-database of microformats in the wild -- which would be a great way to feed pingerati.com. [[User:Chris_Messina Chris Messina]] on 2007 Aug 31.
* check with the group and then, assuming this is accepted, remove mention of the profile="" attribute from the wiki, since HTML5 removes the need for profiles to be declared

=== hCard ===
* microformatted versions of conference pages
** Wait for confirmation from O'Reilly webmaster on revision of the [http://conferences.oreillynet.com/etel2006/ ETel] [http://conferences.oreillynet.com/pub/w/44/speakers.html speaker's page] with all the speakers marked up with [[hcard|hCard]] and links to "Add hCards to Address Book" etc., similar to the [http://tantek.com/microformats/2005/web2/speakers.html Web 2.0 speakers page which Tantek did a revision of last fall].
* vcard to hcard converter
** would be nice to have a web upload UI that would take one or more vCards from apple's address book and give them back to you as hCards
** [[User:RobertBachmann | RobertBachmann]] suggests starting points:
*** For Ruby: http://vpim.rubyforge.org/
*** For C: http://freshmeat.net/projects/libvc/
*** For Python: http://www.nongnu.org/python-pdi/
*** For PHP: http://pear.php.net/package/Contact_Vcard_Parse/
** I (Andy Pemberton) started working on this at one point, but haven't touched it in a while: [http://www.andypemberton.com/sandbox/hcardconvert/ vCard-2-hCard]
* add export support for microformats to [http://www.turingart.com/abForWeb_lan__en.htm AB to Web]
* A mash-up with google maps that will take any url with a hcard (or hcard's) and map the location(s) on a map (similar to [http://austin.adactio.com/ austin.adactio.com])
* more test cases - add to [[hcard-examples]] to begin with, then hopefully create test cases for development to be checked in with mercurial to the repository
** include class="type" without explicit value test cases, based on [[hcard#type_with_unspecified_value|hCard type with unspecified value]].

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

* [http://www.k5n.us/webcalendar.php?topic=About WebCalendar]
* [http://phpicalendar.net/documentation/index.php?title=Main_Page PHP iCalendar]
* [http://www.vcalendar.org VCalendar]
* Investigation: [http://wiki.mozilla.org/Calendar_Talk:Lightning#hCalendar_publish_and_subscribe_support Mozilla Calendar / Lightning / Sunbird hCalendar support discussion]

=== hReview ===
* [[hreview|hReview]] support in Ecto (hey Adriaan!), requested by Andy Smith
* an [[hreview|hReview]] validator.
* a semantic, clean css star rating picker (e.g. a UI widget to rate from 1-5 stars)
** both [http://komodomedia.com/blog/index.php/2005/08/24/creating-a-star-rater-using-css/ this] and [http://factorycity.net/demos/drupal/rating/default.html this] have some flaws. Ask [[User:RyanKing|Ryan King]] for an explanation.

=== hCalendar/hCard/hReview editor ===
* onblur in the URL field (e.g. on hCalendar), goes out and tries to retrieve an object of same time (e.g. an hCalendar vevent) from that URL and uses it to autofill the form, same thing if the creator is loaded with that URL prefilled (e.g. due to a ?url=http://example.com/ in the URL that loads the creator).

=== hAtom ===
* [[hatom-issues]] needs sections for closed issues, resolved issues, and open issues sorted by year, similar to [[hcard-issues]].

=== WordPress patches for microformats ===
* submit patches for WordPress code/templates for microformats improvement
** <address class="vcard"> improvement in post author publication (e.g. home page of http://microformats.org/ )
* Wordpress plugin for microformats, specifically hReview and hCalendar
** See [http://www.surfarama.com/index.php?p=227 lazyweb request]

=== 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.

* [http://developer.yahoo.net/yui/ Yahoo! User Interface Library]
* [http://developer.yahoo.net/ypatterns/ Yahoo! Design Patterns Library]
* [http://www.yuiblog.com Yahoo! User Interface Blog]

=== Drupal patches for microformats ===
* [http://groups.drupal.org/microformats-in-drupal Microformat Module for Drupal] A group discussing ways to implement microformats in Drupal. Currently looking to support hAtom, hCard and hCalendar to start with. Contact digitalspaghetti at gmail dot com if you are interested in contributing to the project.

=== Adding Microformats to Existing Pages ===
* See [[advocacy#Adding_Microformats_to_Existing_Sites|advocacy: Adding microformats to existing sites]].

===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 [http://en.wikipedia.org/wiki/Tag_%28metadata%29 Wikipedia page on tagging]. [[User:AndyMabbett|Andy Mabbett]] 14:07, 3 Jan 2007 (PST)

===Glossary===
Add to the [[glossary]].

===hAtom tutorial===
Finish the [[hatom-tutorial]].

=== wiki gardening ===
* Find [[:Special:Lonelypages|orphaned]] pages, and add links to them.
* Use [[templates]] for boilerplate text and repeated lists of links
* Add keywords to the foot of pages (see [[vcard-suggestions]] for examples), so that they can be converted to tags, once this wiki allows the use of "rel" attributes. Keywords can also include synonyms to aid searching.

====Spelling====
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: <nowiki>[[en-US]]</nowiki>. 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.

{| border="1"
|+
! [[en-GB]] !! [[en-US]]
|-
| [http://microformats.org/wiki/Special:Search?search=behaviour&go=Go behaviour] || behavior
|-
| [http://microformats.org/wiki/Special:Search?search=behaviours&go=Go behaviours] || behaviors
|-
| [http://microformats.org/wiki/Special:Search?search=centre&go=Go centre] || center
|-
| [http://microformats.org/wiki/Special:Search?search=colour&go=Go colour] || color
|-
| [http://microformats.org/wiki/Special:Search?search=colours&go=Go colours] || colors
|-
| [http://microformats.org/wiki/Special:Search?search=favour&go=Go favour] || favor
|-
| [http://microformats.org/wiki/Special:Search?search=flavour&go=Go flavour] || flavor
|-
| [http://microformats.org/wiki/Special:Search?search=flavours&go=Go flavours] || flavors
|-
| [http://microformats.org/wiki/Special:Search?search=flavoured&go=Go flavoured] || flavored
|-
| [http://microformats.org/wiki/Special:Search?search=minimise&go=Go minimise] || minimize
|-
| [http://microformats.org/wiki/Special:Search?search=minimises&go=Go minimises] || minimizes
|-
| [http://microformats.org/wiki/Special:Search?search=recognise&go=Go recognise] || recognize
|-
| [http://microformats.org/wiki/Special:Search?search=recognised&go=Go recognised] || recognized
|-
|}

[http://en.wikipedia.org/wiki/American_and_British_English_spelling_differences More American and British English spelling differences]

== Admins ==
This section is for folks to suggest to-do items for [[admins]], in particular, having to do with suggestions for improvements to microformats.org infrastructure such as the wiki. If you do add an item to this list, please sign your username with four tildes: <nowiki>~~~~</nowiki>.

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 ===

* Something broken with the new MediaWiki microformats templates for date modified on delta/version pages? see: https://twitter.com/CogitoStudios/status/32227146466332672

* Want: Right-to-left (RTL) support in the theme for better translating to RTL languages. Per [https://www.facebook.com/permalink.php?story_fbid=10150109554926465&id=214611 this comment on the microformats page on Facebook 2011-02-13]: <blockquote><cite>Sina Cheraghi</cite> > Microformats "I want to contribute in Microformats wiki by translating it into Persian. But lack of RTL (right-to-left) languages (Persian, Arabic, Hebrew and ...) theme causes some problems for me and other contributors."</blockquote>

* New link styles for links to mailing list archive
** Lacking a more concrete suggestion for how to improve such links, I'm inclined to park this in "won't do". [[User:Tantek|Tantek]] 02:39, 10 September 2009 (UTC)

* Add proper styling to phrase elements
** Lacking a more concrete suggestion for how to improve styling of phrase elements, I'm inclined to park this in "won't do". [[User:Tantek|Tantek]] 02:39, 10 September 2009 (UTC)

* Make email addresses editable [[User:Singpolyma|Singpolyma]] 02:47, 26 July 2009 (UTC)
** How would this work and what's the purpose? [[User:Tantek|Tantek]] 02:39, 10 September 2009 (UTC)

== Tantek ==
I'm keeping a few microformats related to-do items here both for my own convenience, and for folks looking to help out with small tasks. If so, just create a new section with your name, and and maybe copy the item there, and put your name next to the item in my list. We'll figure this out as we go along. Thanks, [http://tantek.com Tantek].

=== overall priority ordering ===
# Protect the community from threats (wiki damage, mailing list pain or noise), repair damage, add measures to reduce future damage
# Help publishers with established microformats: [[hcard|hCard]], [[xfn]], [[rel-tag]], [[hcalendar|hCalendar]], [[hreview|hReview]], [[xfolk|xFolk]]
# Help implementers with established microformats
# Iterate on existing established microformats, resolve issues/feedback etc.
# Wiki cleanup/gardening for existing established microformats
# Site usability of microformats.org top-down as an entry point
# Community dynamics, [[process]] and [[principles]] improvements to help guide new microformats developments
# Emerging in-demand microformats: [[hresume|hResume]], [[hlisting|hListing]], [[citation]], [[media-info]] using abovementioned process and principles improvements.
# New microformat requests
# Document microformats [[history]].
# Other

=== protect the community ===
* Analyze [[Special:Recentchanges]] and [http://microformats.org/discuss mailing-lists] and:
** add to [[mailing-lists]] and [[how-to-play]] policies/guidelines accordingly.
** redirect and resolve threads accordingly per guidelines
** privately email violaters kindly asking them to improve their behavior
** work with admins on next steps for individuals negatively impacting the community
** recognize noisy/distracting threads on the email list, document responses/answers to such subjects on the appropriate page(s) on the wiki, and reply to those threads with the URLs to the documentation on the wiki. Putting the responses/answers on the wiki helps by hopefully providing preemptive answers to some who might reraise the subjects on the list in the future, and helps the community quickly terminate such threads by using the answers on the wiki.
** move exploratory discussions which are failing to follow the process to a separate page from that
** repair damage done to the wiki
*** identify damage done to the wiki - often in forms as simple as content changes that hurt usability (and thus accessibility)
*** document additional [[how-to-play]] guidelines to discourage and hopefully reduce such wiki damaging behavior in the future
*** repair/undo/reorganize page section division that hurt usability (and thus accessibility)
**** [[hcalendar-examples-in-wild]]
***** afterwards add some of the excellent conference schedule calendars that [[User:Adactio]] has been creating like:
****** http://adactio.com/extras/schedules/barcampbrighton3/
*** repair/undo/reorganize page splitting that hurt usability (and thus accessibility)
**** [[to-do]]

=== help publishers ===
==== solve problems blocking publishers ====
* [[value-class-pattern]]
** <del>drafted</del>
** <del>[[value-class-date-time-tests]] - finish writing date and time tests</del>
** <del>put out call for review, implementation,</del> and value-title tests

===== minor update current specifications =====
* draft hCard 1.0.1: [[hcard|hCard spec]] '''next-actions''':
** <del>resolve remaining [[hcard-issues|hCard issues]]</del>
** close remaining [[hcard-issues-resolved|hCard resolved issues]] by writing necessary [[hcard-faq|FAQ]] entries, updating [[hCard]], and adding to [[hcard-brainstorming]] for 1.0.1 and 1.1.
** draft [[hcard-1-0-1]] by starting with [[hcard-1-0]] and incorporating [[hcard-brainstorming]] targeted for 1.0.1.
** incorporate [[hcard-feedback]]
** continue updating the spec per the inline comment about property references
** add a brief descriptive sentence for each property, similar to what [[hreview|hReview]] has. just enough so that the casual reader can avoid having to reference and read the respective sections in [[RFC2426]]. add any non-trivial information about each property similar to what [[hreview|hReview]] has.
** iterate [[hcard-parsing]] with [[value-class-pattern]] as a required feature
** iterate [[hcard-parsing]] with sufficient table element special handling to do people equivalent of [http://microformats.org/wiki/hcalendar- brainstorming#Tabular_event_calendars]
** iterate [[hcard-parsing]] with how to handle new or different [[HTML5]] markup such as the <code><time></code> element, including at least one test case with the <code><time></code> element.
** [[hcard-brainstorming]] '''next-actions''': determine which brainstorms proposals to resolve for minor revision, and which later
** Update [[semantic-xhtml]] with lists of semantic [http://www.w3.org/TR/html401/index/elements.html elements] and [http://www.w3.org/TR/html401/index/attributes.html attributes].
** Update [[hcard-brainstorming]] on element specific parsing rules
** Update X2V, hKit, Operator accordingly
** Write test cases accordingly
** Update [[hcard-parsing]] accordingly
* draft hCalendar 1.0.1: [[hcalendar|hCalendar spec]] '''next-actions''':
** <del datetime="2009-10-03">resolve all outstanding [[hcalendar-issues]] into [[hcalendar-issues-resolved]]</del>
** close remaining [[hcalendar-issues-resolved|hCalendar resolved issues]] by writing necessary [[hcalendar-faq|FAQ]] entries, updating [[hCalendar]], and adding to [[hcalendar-brainstorming]] for 1.0.1 and 1.1.
** draft [[hcalendar-1-0-1]] by starting with [[hcalendar-1-0]] and incrementally incorporating [[hcalendar-brainstorming]] targeted for 1.0.1
** incorporate [[hcalendar-feedback]]
** itemize a complete property list similar to the [[hcard#Property_List|hCard property list]], drawing upon hCalendar experience, iCal-BASIC draft(s), ietf-calsify mailing list and other sources to derive the precise list. Separate common properties up front.
** add a brief descriptive sentence for each property, similar to what [[hreview|hReview]] has. just enough so that the casual reader can avoid having to reference and read the respective sections in [[RFC2445]]. add any non-trivial information about each property similar to what [[hreview|hReview]] has.
** significantly update and thoroughly specify [[hcalendar-parsing]] with [[value-class-pattern]] as a required feature
** formally document [http://microformats.org/wiki/hcalendar- brainstorming#Tabular_event_calendars]
** iterate [[hcalendar-parsing]] with how to handle new or different [[HTML5]] markup such as the <code><time></code> element, including at least one test case with the <code><time></code> element.
** [[hcalendar-examples]]
*** make sure all hCalendar examples that reference whole days use best international/accessible date format of YYYY-MM-DD
*** add explicit explanation and examples for LOCATION [[hcard|hCards]] and ATTENDEE [[hcard|hCards]], perhaps on a separate [[hcalendar-examples]] page.
** Write [[compound-parsing]] by abstracting commonalities between [[hcard-parsing]] and [[hcalendar-parsing]].
* draft hReview 0.4
* resolve hAtom issues
* co-edit hAtom per permission from David Janes
* draft [[hAtom]] 0.2
** Clarify that "published" property values may omit seconds, and that converters to Atom are expected to imply ":00" seconds.
* add sections for comments/opinion from community as well as issues subsection
* solicit feedback
* when sufficient consensus and issue resolution achieved, archive previous versions of specs, and update spec pages accordingly.

==== social network portability ====
Iterate on:
* [[social-network-portability]]
* [[hcard-supporting-user-profiles]]
* [[hcard-xfn-supporting-friends-lists]]

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:
* how to author/publish hCard user profiles - write this up in [[hcard-authoring]] first (see below) and then use that content.
* how to author/publish hCard+XFN friends lists - write this up in [[hcard-xfn-authoring]] (see below) and then use that content.
* how to parse/subscribe to hCard user profiles - write this up by updating: [[hcard-parsing]], and writing [[hcard-supporting-user-profile-parsing]] (collect this into parsing/developers tasks below)
* how to parse/subscribe to hCard+XFN friends lists - write this up by writing: [[xfn-parsing]], [[hcard-xfn-supporting-friends-list-parsing]] (collect these into parsing/developers tasks below)
** notes/thoughts on hCard+XFN supporting friends list parsing captured here for now:
*** do a full rel="me" bidirectional crawling within the domain - some sites' hCard supporting user profiles simply link to their hCard+XFN supporting friends lists with rel="me", and thus you will discover more pages with friends lists.
**** E.g. Flickr's /people/username pages have hCard for the user and link to their /people/username/contacts page with rel="me" (on the "More..." link, though they could also add rel="me" to the number inside "Your contacts (592)"). Need to get them to support hCard+XFN on the contacts themselves.
*** consider parsing within a friends list page, any links that are rel="next" and rel="prev" to iterate over the whole list.

==== foldup cheatsheet ====
'''next actions''':
* gather feedback on current foldup [[pocket-cheat-sheet|pocket cheatsheet]]
* document the [[pocket-cheat-sheet-feedback|feedback on the pocket cheatsheet]]
* provide printing recommendations for anyone to download and print their own
** Perhaps [http://www.visibone.com/ Visibone] can be of some use? I can recommend their current products. --[[User:Gazza|Gazza]] 06:41, 7 Apr 2007 (PDT)
* update cheatsheet to include new [[value-class-pattern]] uses
* give feedback to Erin or ask for volunteers to create a new cheatsheet, iterate, print more to have on hand, fold, distribute.
* discuss with [[User:Adactio]] and Hannah how to best create a UK/A4 version of the pocket cheatsheet
** preferably well in advance of dConstruct 2008 so that local cheatsheets can be printed.

==== *-authoring microformats wiki pages ====
* [[hcard-authoring]] - '''next-actions''': add tips/instructions noted below.
** instructions for each property that is in [http://microformats.org/code/hcard/creator hCard creator] to begin with
** instructions for all other hCard properties
** a tutorial on creating an hCard for your site
*** specific instructions for common blogging platforms
** reference [[hcard-examples]] for more specific uses, and add to them accordingly
*** add an extended example to [[hcard-examples#Authors_of_Pages_and_Posts|contact info for a page]] with postal address, phone numbers, email address.
* [[hcard-xfn-authoring]] - '''next-action''': draft by starting from hCard+XFN instructions in [[hcard-examples]].
* [[hreview-authoring]] - '''next-action''': create a first draft minimal tutorial on how to author hReviews (e.g. at least for common properties) to blog reviews so that they'll be aggregated.
* [[hcalendar-authoring]] - '''next-action''': add tips/instructions for each property that is in [http://microformats.org/code/hcalendar/creator hCalendar creator].
* *-authoring for other reasonably well established microformats:
** [[xfolk-authoring]], [[hatom-authoring]]

==== 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|hCalendar]] and [[hcard|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:
* Flickr.com (3.5m hCards)
* Upcoming.org (100k hCalendar events, 100k hCard venues)
** home page
* Eventful.com (100k hCalendar events, 100k hCard venues)
* Yahoo! Tech (300k products with hReviews)
* JudysBook.com (???k hReviews)
* ... lots more, get from "Implementations" and "Examples in the Wild" sections of specs.

==== advocacy for obvious sites ====
* [[advocacy]] - add pages/sites that obviously (no pun intended) could use microformats, update them with sample markup, find contacts for those pages to get them updated, and send requests to update their sites with microformats including sample markup. '''next-actions''': markup both twitter.com sample pages and dodgeball.com sample pages, post the changes publicly, and see which one is able to update first ;)
** dodgeball.com (hCard + XFN + hAtom for profiles, hCard + hReview for venues)
** write essay on [[open-data-more-important-than-open-source]] - and a shorthand URL too.
*** obviously doing both is ideal, however, open data is a higher priority and given limited resources, open data should be implemented before open source.
*** open data > open source
*** "open information" vs "open source"
*** i.e. please focus first on open data rather than open source, e.g. start with [[hcard|hCards]] for all organizations returned from http://wiserearth.org/organization
*** if the data is open you can always export it and consume it in any number of open source systems
*** that's why open data is MUCH more important than open source
*** adding open data (e.g. microformats) can be done by any HTML author (yes, you), whereas open sourcing requires programming expertise, resouces, support. do the simpler easier thing first (open data thru microformats) that will benefit more people sooner.
*** if the data was open, anyone could rebuild an accessible version
*** faqs / misconceptions:
**** eschipul: @tantek - creating microformats is easier. consuming microformats is unfortunately not easier.
***** A: If you think consuming microformats is not easier or hard etc., it may just be that you don't know how to do so easily, don't assume that you are an expert in something that you think is hard. Rather, if you think something is hard, then assume others may know easier methods, and ''ask'' the community how one can do it more easily. parsing in particular is something which is becoming easier and easier thanks to open source libraries like [[hkit|hKit]].
** write essay on [[open-data-more-important-than-open-apis]] - and a shorthand URL too
*** obviously doing both is ideal, however, open data is a higher priority and given limited resources, open data should be implemented before open APIs.
*** publishing/providing open data (e.g. microformats) can be done by any HTML author (yes, you), whereas providing/publishing open APIs requires programming expertise, resouces, and support. do the simpler easier thing first (open data thru microformats) that will benefit more people sooner.

=== help implementers ===
* wordpress improvements
** WP admin for new profiles
*** should simply read blog URL - '''next-action''': make sure a bug/feature request is filed with wordpress.org
*** look for hCards and parse them

* [http://gmpg.org/xfn/creator XFN Creator] localizations
** Get someone to verify the [http://gmpg.org/xfn/creator-ru XFN Creator Russian localization].
** Add it to the [http://gmpg.org/xfn/tools XFN Tools] page.
** Add rel="alternate" href="creator-ru" <link>s to the other XFN Creators.

* Conference Schedule Creator
** '''next-actions''': Review Dmitry Baranovskiy's [http://dmitry.baranovskiy.com/work/csc/ Conference Schedule Creator] and give him feedback per how well it:
*** Makes it *trivial* for conference organizers to build/edit/publish an [[hcalendar|hCalendar]] schedule for their conference, including auto-generated "Subscribe..." link which produces the proper "webcal:..." link with X2V. Note: see the "axis" and "header" attributes in HTML4, specifically in the section on Tables.

=== iterate on current microformats ===
==== in general ====
===== plain language intros =====
For [[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], [[xoxo|XOXO]] to start with, write up:
* brief plain-language intro at the top (say for example, something that a non-technical person like a member of the general media/press could read and understand), similar to or better than plain language intros on W3C specs.
* followed by links to more plain-language resources, e.g. *-intro pages.
In particular for [[xoxo|XOXO]], Angus McIntyre suggested:
* As well as a syntactic example, examples of use would be useful.
* when I might want to use XOXO.
* Some simple examples right upfront would probably do a lot to help users figure out whether a particular microformat is for them or not.
These suggestions could be incorporated into the other specs as well.
===== exploratory discussions =====
* update [[exploratory-discussions]] with critical microformats as "active"
===== CSS enhancements for =====
Analyze existing microformats for opportunities to enhance CSS and propose to W3C.
* e.g. CSS datetime presentation (need to add links to my earlier work in CSS working group)
* brainstorm additional possibilities for better presentation of content using existing microformats.
===== update affiliations =====
* Start a minimal draft/spec style guide using outline of most readable/accessible spec so far
* Reference http://www.w3.org/2001/06/manual/#Editors for how to manage affiliations
* Update affiliations on [[hcard]], [[hcalendar]], [[hreview]], etc. per http://www.w3.org/2001/06/manual/#Editors
===== profile URLs =====
* write-up and document [[profile-uris|profile URLs]] for all established microformats and perhaps for some drafts as well

==== [[hcard|hCard]] ====
Combined next-actions for iteration on [[hcard|hCard]], and derived/subsetted microformats [[adr]] and [[geo]]
* [[hcard-profile]] '''next-actions''':
** update property definitions with more detail using semantics from [[RFC2426]]
** link from brief sentence descriptions for each property in [[hCard]] to the respective more detailed definition in the [[hcard-profile]].
** link from definitions in the [[hcard-profile]] to the specific sections in the vCard spec
* [[hcard-examples]] '''next-actions''': update with examples described below
** add examples of [[hcard|hCard]]s with work telephone, mailing address etc.
** add examples of marking up an organization vs. a person, then link to it from [http://microformats.org/wiki/hcard#Organization_Contact_Info hCard spec section on Organization Contact Info].
** add example of organization-name and organization-unit usage.
* [[hcard-brainstorming]] '''next-actions''': explore brainstorms proposals for a 1.1 revision, e.g.
** need property for gender (see [[hcard-faq#How_is_gender_represented|proposal in hCard FAQ]] and discussion in [[hcard-issues]]) - use tags for now, add to hCard creator
** solve [[hcard-brainstorming#Auto-Discovery|autodiscovery]] of more canonical/thorough hCard
* [[hcard-examples-in-wild]]
** help dglazkov markup: http://glazkov.com/blog/archive/2003/12/17/147.aspx

* analyze [[hcard-cheatsheet]], [[adr-cheatsheet]], [[geo-cheatsheet]] for any assertions above and beyond what the specification itself says, take into account [[hcard-brainstorming]] along similar lines, and incorporate into the spec or remove as necessary and sync-up as a result. add clarification on the cheatsheets that they are '''informative''' and reference the specification for normative requirements.

==== [[hcalendar|hCalendar]] ====
'''Next-actions''':
* update [[hcalendar-examples]]
** add examples like [[hcard-examples]]
** flesh out and do a once over on markup/presentation of what RFC2445 examples would look like
** update all hcalendar-examples to use value-title from [[value-class-pattern]] where abbr doesn't make sense. e.g.
*** rrule
*** duration
*** ... etc.
* need spec details and then [[hcalendar-examples]] of multi-instance [[hcalendar|hCalendar]] events
* need spec details and then [[hcalendar-examples]] of repeating events
* have folks verify [[hcalendar-profile]]. Note that it will likely need reconciliation with the [[hcard-profile]], especially since [[hcalendar|hCalendar]] normatively depends on [[hcard|hCard]]. Probably makes sense to have a combined profile which hCalendar would use.
* analyze [[hcalendar-cheatsheet]] for any assertions above and beyond what the specification itself says, take into account [[hcalendar-brainstorming]] along similar lines, and incorporate into the spec or remove as necessary and sync-up as a result. add clarification on the cheatsheets that they are '''informative''' and reference the specification for normative requirements.

==== [[hreview|hReview]] ====
'''Next-actions''':
* reconcile [[hreview-profile|hReview 0.4 XMDP profile]] with [[hcalendar-profile]] and [[hcard-profile]]. Makes sense to have a combined profile of all three for hReview, since hReview normatively depends on hCard and hCalendar.
* Resolve all outstanding [[hreview-issues]] and [[hreview-feedback]] to-do items.

==== [[rel-tag]] ====
'''Next-actions''':
* send [[rel-tag]] XMDP profile ([[rel-tag-profile]]) to [http://dbaron.org/ David Baron].
* Resolve all outstanding [[rel-tag-issues]] and [[rel-tag-feedback]] to-do items.

==== [[rel-me]] ====
'''Next-actions''':
* move XFN and XMDP FAQs, tutorial, descriptions, spec etc. from gmpg.org to microformats.org
** and put redirects in place, notes about contribution
* update rel-me examples and document with examples the rel-me implict subdir rule

==== [[hatom|hAtom]] ====
'''Next-actions''':

==== summary Examples in the Wild page ====
* need to create a summary / overall [[examples-in-the-wild]] page
** parallel the summary/overall [[implementations]] page.
** use newly reorganized content from the above "reoganizing Examples in the Wild" task

==== parsing ====
'''Next-actions''':
* Draft *-parsing for all reasonably well adopted microformats: [[hreview-parsing]], [[xfolk-parsing]], [[hatom-parsing]]

=== wiki cleanup ===
==== for all microformat specs ====
'''Next-actions''':
* modularize any specs which are > 30K in order to avoid loss/corruption like [http://microformats.org/wiki?title=Special:Contributions&target=Evan Evan's 14 June edits] to [[hcard|hCard]], [[rel-tag]], and [[xoxo|XOXO]].
** [[hcard|hCard]] -
*** [[hcard-examples-in-the-wild]] group/sort by individuals, organizations, and hosting sites. Consider moving largest subsection to its own page as well.
** [[rel-tag]]
** [[xoxo]]

==== update specification section organization ====
'''Goal''': greater approachability/readability of microformats specs by a broader audience.

Reference:
* [[hresume|hResume]] has an experimental abbreviated intro/headers section, and links to more details further below, based on some ideas that Ryan King and I had for improving the readability of the microformats specifications.
* [[hreview|hReview]] has some similar improvements, but different.
* [[hcard|hCard]] has numerous improvements as well, again different from either hResume or hReview

'''Next-actions''':
# 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.
# figure out if the new intro/headers etc. structure/order in [[hcard|hCard]], [[hreview|hReview]], and [[hresume|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
# Design an iterative update to spec organization, in particular, the introduction/boilerplate/headers.
# Write up a template - make it self-documenting per the requirements
# Update existing specifications with the new intro/headers structure.
## [[hcard|hCard]]
## [[hcalendar|hCalendar]]
## [[hreview|hReview]]
# 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 ====
* sort implementations by authoring/creating/publishing, browsing/viewing, converting/importing, indexing/searching.

Hmmm... I like: '''A'''uthoring, '''B'''rowsing, '''C'''onverting, '''I'''ndexing, '''L'''ibraries (for developers), and '''P'''otential (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: [http://microformats.org/wiki/hcalendar#Implementations 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.

'''Next-actions''':
* [[hcard-implementations]] - re-organize by same subsections as [[hcalendar-implementations]].
* [[hreview-implementations]] - re-organize by same subsections as [[hcalendar-implementations]].
* [[hatom-implementations]] - re-organize by same subsections as [[hcalendar-implementations]].
* [[xfolk-implementations]] - re-organize by same subsections as [[hcalendar-implementations]].

==== reorg Examples in the Wild sections ====
Work with community to:
* include more *key* details per example, e.g. precise or estimates of counts for services
* collate/sort examples in the wild by
** hosting services - where users/people actively contribute to the growth (e.g. Flickr profile hCards)
** publishing services - where lots of data is published from some datasource/database (e.g. Yahoo! Local)
** companies/groups/organizations member pages (and their own) - pages for a group's site where they list members or employees (e.g. Technorati staff page)
** individiual companies/organizations contact info pages
** individual people's contact info pages
* of course at some point this won't scale, but that will be a very good problem to have, and by then I'm sure we'll have services to point to that provide queries and search results for all this data.

=== site usability ===
* figure out how to get wordpress to autopost blog posts to the microformats-announce list
** ideally use the from address of the author of the blog post
** maybe photomatt knows how to do this.

=== introduction / community ===
* microformats-discuss *
** introductory email template for new subscribers needs to direct people to [[process]] and [[how-to-play]]
* Need to add more to the [[naming-principles]], to cover in particular:
** avoid using the same name to mean two things
** avoid using two names to mean the same thing
** seek to keep the microformats vocabulary minimal, memorable, and usable.
* update and add details/simplifications to [[process]] given the past several months of experience. in particular:
** clarify requirement (MUST rather than SHOULD) of *-examples, *-formats, before any *-brainstorming.
** Add details of encouragement to experiment with simple semantic class names from *-brainstorming proposals to gain real world experience with real world content.
** note SHOULD prerequisite of use of all relevant microformats on real world web pages, along with documenting such use in respective "Examples in the Wild" sections, before proposing any new microformats.

==== posh improvement ====
* Create a page to answer the question "[[how-should-i-markup]]"
* consider creating a process/encouragement for collecting individual [[posh]] practices and examples, like a folksonomy of semantic HTML and semantic class names.

==== principles and process ====
Create the following pages and document/fill them with content from other pages, email lists, and [[presentations]].
* [[principles]] - mostly [[microformats#the_microformats_principles|documented in the microformats]] page.
* clearer statement of both copyright and patents both in specific specs and in general
* resolve [[process-issues]]

==== profiles ====
* update [[XMDP]] with new required features:
** ability for one profile to include/import another (rel="import" ?)
** ability to reference an XMDP via rel="profile" (similar to XHTML2 rel value by same name)
*** add rel="profile" to the [[xmdp-profile]].
** ability/suggestion to reference an XMDP using <a href> in addition to <link>

==== community mark ====
* Can we make "microformat" and "microformats" into [http://factoryjoe.com/blog/2006/01/14/the-case-for-community-marks/ Community Marks]?

==== document issue resolutions ====
* Prefixing has already been considered and rejected for microformats in general. Note [[naming-conventions]], limited vocabulary, and exceptions made for [[hatom|hAtom]] and how we went about doing so.

=== emerging microformats ===
* [[directions]]
* [[citation]]
* [[hlisting|hListing]]
* [[media-info]]
* [[licensing]]
'''Next-actions''' for each emerging microformat (one at a time)
* review all microformats-email on the new microformat
* determine where new microformats is "stuck" in the process
* brainstorm about how to improve process (or documentation thereof) to get the effort unstuck
* work with community to move the microformat forward through the process, iterating/clarifying the [[process]] as necessary

=== new microformat requests ===
* expense reports (really just a list of "expense" items), [http://flickr.com/photos/edyson/56774178/ requested by ED], should look at UBL as a pre-existing format
* photo-notes microformat
** clean up Subethaedit notes from working session with Greg Elin, Ryan King, Kevin Marks, Suw Charman and email to folks and figure out next steps
** iterate on [[photo-note-examples]] and start [[photo-note-formats]] and [[photo-note-brainstorming]].

=== document microformats history ===
Document microformats [[history]], including:
* dates and origins of microformats, names, terms
* examples and formats for established microformats like [[hcard|hCard]], [[hcalendar|hCalendar]], [[xfn]], [[rel-license]], [[xoxo]]

=== other ===
* Add XPath equivalents where appropriate in [[hcard-parsing]]

==Ryan==
=== wiki cleanup ===
* <s>possibly move dead proposals off of homepage?</s>

=== hCalendar/hCard/hReview creator improvements ===
* get all creators working in IE/Win, IE/Mac, Safari/OSX.3

=== other ===
* add an example of how to use DURATION in hcalendar see http://www.policyawareweb.org/2005/ftf2/paw-mtg#item15) -> verify http://svn.lifelint.com/hcalendar_tests/calendar-todo-multiple-attendees-and-alarm.xml

=== rel-payment ===
* update rel-payment to reference the IANA registry [http://www1.ietf.org/mail-archive/web/ietf-announce/current/msg02055.html]

=== hcalendar ===
* make sure we explicitly disallow 'vjournal'

== Dimitri Glazkov ==

* Figure out REST/Microformats thing
* Work on result set idea
* Implement h-creators using Web Forms 2.0

== Chris Messina ==

=== General ===

* Work on a microformat for play-lists (is it just a XOXO ordererd list of play-items?)
* Work on a microformat for play-item (take a look at [[media-info-examples]])
* Work on microformats tutorial for designers
* Add support for OpenID to micformats wiki
* <strike>Add support for [http://verselogic.net/projects/wordpress/wordpress-openid-plugin/ OpenID] to the microformats blog</strike>.
* <strike>Read GTD (at least the first two chapters)</strike>.

=== Campaigns ===

* <strike>Get Blogger to support hAtom and hCard</strike>
* <strike>Get LinkedIn to support hCard, hResume, hCalendar</strike> and XFN
* Get XING to support <strike>hCard</strike>, hCalendar, hResume and XFN
* Get <strike>Digg to support microformats</strike> (still need XFN).

=== Wishlist ===

* Microformat for "buyable items" (see [[listing-examples]] and related documents)
* Location MF -- right click "map this" (see [[geo]] and [[adr]])
* Better hCard support in the browser -- right click "IM this person...", "Add to contacts" (see [http://factoryjoe.com/blog/2006/03/20/flocktails-for-flock/ Flocktails])
* Better hCal support -- support many views of same hCal data on one page using XSLT
* We need something that a designer/web programmer can come to and leave w/ 2 examples of each microformat that they can apply right away... a "microformats styleguide for designers", if you will.
* invoicing microformat
* better microformats wiki theme
* Define flow for OpenID + XFN + hcard (see [http://diso-project.org DiSo Project])

Hey Chris.
Congrats on Microsyntax
([http://factoryjoe.com/blog/2009/05/26/stowe-boyd-launches-microsyntax-org/ "Stowe Boyd launches Microsyntax.org"]).
So ... do we need a page on this Microformats wiki describing the connection between microformats and microsyntax?
When the Microsyntax wiki goes online, please add a link to it on the Microformats [[WikiNode]] page.
--[[User:DavidCary|DavidCary]] 08:34, 4 June 2009 (UTC)

== Robert Bachmann ==
[[User:RobertBachmann|Robert Bachmann]]

=== XSLTs ===
<ul>
<li>Test scripts
<ul>
<li>Do some refactoring, split Perl code into smaller modules</li>
<li>Provide test results as HTML pages (similar to http://www.w3.org/2003/08/owl-systems/test-results-out)</li>
<li>Provide some documentation for using the test scripts</li>
</ul>
</li>
<li>hAtom2Atom
<ul>
<li>
Join all hfeed's inside a page (or a fragment thereof) into one feed using [http://greenbytes.de/tech/webdav/rfc4287.html#element.source atom:source] semantics.
</li>
<li>
Extraction of <code>atom:content</code>, <code>atom:summary</code> and <code>atom:title</code>:
* <code>atom:content</code> and <code>atom:summary</code> as HTML
* <code>atom:content</code> and <code>atom:summary</code> as plain-text
* <code>atom:title</code> as XHTML
* <code>atom:title</code> as HTML
</li>
<li>Support for other XSLT engines:
* .Net System.Xml
* hAtom2Atom written using XSL 2.0?
** Do you think this would be useful? I have created a barebones version, doesn't yet take in all the parsing rules yet, but I'd be happy to share. Moving to XSL 2.0 does make things a bit cleaner and more efficient. - Matt Dertinger.
</li>
<li>Support for other output formats: (hAtom2xyz.xsl)
* RSS 2.0 (meanwhile use hAtom2Atom.xsl and [http://atom.geekhood.net/ atom2rss.xsl]) -- +1 Matt Dertinger
* RSS 1.0 (meanwhile use hAtom2Atom.xsl and [http://cvs.4suite.org/viewcvs/uogbuji/atom2rss.xslt atom2rss.xslt]) -- +1 Matt Dertinger
** My opinion at the moment, I neither want to produce nor to consume RSS. Atom is nicer (and should be supported by most good feed readers available today), RSS should fade away. -- Robert Bachmann
* AtomOWL (meanwhile use hAtom2Atom.xsl and [http://dannyayers.com/2005/11/22/atomowl-xslt-progress/ atom2rdfxml.xsl])-- +1 Matt Dertinger
** Having the possibility of GRDDL-ing hAtom to AtomOWL seems definitly interessting. I realy should implement this some day. - Robert Bachmann
* JSON?
** Does it make sense to consider a canonical representation of microformats (either case by case, or in general) in JSON? E.g. so that a JSON API that returned contact information could return an hCard-equivalent chunk of JSON. - Tantek.
*** This could enable some nice JavaScript hacks. I should give hAtom2JSON a try. - Robert Bachmann
</li>
</ul>

([[User:Singpolyma|singpolyma]] 01:02, 9 May 2006 (PDT) -- Not XSLT, but see http://xoxotools.ning.com/hatom2rss.php for hatom to RSS2.0 conversion)
</li>
</ul>

== Brian Suda ==
=== Citation Microformats ===
* Add all my notes to the Wiki
* Start the process of naming the properties using existing names

=== X2V ===
Make changes and update site (almost stable)
Get ATTENDEE and other strange attributes working
==== WARNINGS and ERROR ====
work on the warnings and error output for the pre-check in X2V

=== FAQ ===
* clean-up the MF FAQs
* clean-up FAQs from the major microformats
* pull Questions from the mailing list and document them to the FAQs and example

=== Microformats History ===
* get early work from developer.technorati site
** issues with MoinMoin full history: http://moinmoin.wikiwikiweb.de/MoinMoinQuestions/UsingTheWiki#head-9d1b1d6beedde40b92cc6c13962b5a6f5b289d10

=== additions to the wiki ===

* better explain why NOT infinitely scaling is a good thing
* better explain why microformats do NOT use namespacing

== Mark Rickerby ==

=== Current Tasks ===

* Follow up on usability review
** Edits to homepage feature box text
** Draft of [[getting-started]] page
* Review content for new pages - [[start-simple]], [[modularity]], [[reuse]], [[humans-first]]
* xoxo datatype examples
** test case lists
** transmitting key/value lists
* practical feedback on hresume

=== Wishlist ===

* hmmm

== 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.

==== Goals ====
# Improve understanding of what needs to be done for Wiki
#* IMHO - this should be done here, in [[to-do]] incrementally. -Tantek
# 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
# Motivate community to have fun with otherwise tedious "housecleaning" chores

==== Agenda (Wishlist) ====
In parallel:
* Coalesce/prioritize existing To-Do items (above)
* Review/revise desired pathways for:
** New users learning about microformats
*** e.g., intro, about, explore, tutorials, etc.
*** cf. [http://www.rubyonrails.com/ Rails] front page
****Get Excited (Why, background, motivation)
****Get Started (What, downloads, getting started)
****Get Better (How, tutorials, )
****Get Involved (Who)
** Microformat lifecycle
*** e.g., research->brainstorm->proposal->spec->maintain
*** see http://theryanking.com/microformats/method.txt --[[User:RyanKing|RyanKing]] 15:35, 22 Feb 2006 (PST)
*** ensure information easy to find, follow, and up-to-date
* Review existing specs for completeness and consistency
* Identify areas of 'bitrot' or 'hole-filling'
* Do it!

== Dan Connolly ==

[[User:DanC|DanC]] hopes to sync up on these tasks in [[irc]] roughly
weekly, during Wednesday afternoon (Chicago time) "office hours". See also my [http://esw.w3.org/topic/DanConnolly esw todo list and someday pile].

* from SxSW in Austin
** build a combined hcalendar/hcard profile; resolve issues in [[profile-uris]].
*** with XSLT transformation to RDF
** finish [[hcard-tests]]
*** figure out [[include-pattern]] boundaries

* Medium term
** sync [[hcalendar-tests]] and [http://www.w3.org/2002/12/cal/ RDF calendar] tests and CALSIFY
*** reconsider RDF calendar naming conventions
** update my CV/resume using [[hResume]] and [[citation-formats]]
*** get an answer from the CALSIFY WG re [http://lists.w3.org/Archives/Public/www-rdf-calendar/2006Apr/0006.html dtstart and date vs datetime ] 21 Apr 2006
*** refine [[hatom]] so that it's suitable for the workflow around the W3C homepage.

* from WWW2006
** follow up on GRDDL as escape valve for microformats proposals, much like CSS was an escape valve for HTML tag proposals.

* Someday pile
** set up a timezone registry based on wikipedia and semantic mediawiki. As discussed in [[datetime-design-pattern]], iCalendar's by-value timezone passing is broken. see [http://lists.w3.org/Archives/Public/www-rdf-calendar/2006Apr/0002.html reconsidering timezones in light of hCalendar and CALSIFY] and [http://dig.csail.mit.edu/breadcrumbs/node/91 Toward Semantic Web data from Wikipedia]
** noodle on a playlist format and some of the media RSS stuff like [[media-info-brainstorming]], [[media-metadata-examples]] (re playlists: XSPF, SMIL, RDF, and microformats 9 Sep 2005)
** check out that hReview bug stuff...
** noodle on [[meeting-minutes-brainstorming]] and [http://esw.w3.org/topic/MeetingRecords MeetingRecords in the esw wiki].
** noodle on clipboard scenarios, esp how RDFa works in the general case but isn't as author-friendly as domain-specific syntaxes.

[[User:DanC|DanC]] 15:39, 31 May 2006 (PDT)

== Chris Casciano ==

[[User:ChrisCasciano|ChrisCasciano]]

* get around to updating [[hatom-issues]] with some multi feed rules/exceptions.
* <del>Update textpattern plugin with simple hreview support and get a new release out</del>
* Redesign placenamehere.com and include hatom
* Follow up with technorati folks on pingerati reviews getting lost (note: this will require publishing more reviews and theen watching them through the update process)
* <del>prototype a NetNewsWire microformat extractor (CSS+AppleScript)</del>

== Drew McLellan ==

[[User:DrewMcLellan|DrewMcLellan]]

* Build an hReview profile for [http://allinthehead.com/hkit/ hKit] and test
* Update the [http://www.webstandards.org/action/dwtf/microformats/ Dreamweaver extensions] to mirror recent changes in the online builders
* <del>Publish an hCard to JSON service on [http://tools.microformatic.com/ tools.microformatic.com] using hKit.</del>
* Further develop blog comment form hCard collection ideas.
* Version of hReview creator using hKit to import business details from an hCard

== Christophe Ducamp (french localization) ==

[[Christophe Ducamp]]
* seed "microformateurs group" and invite them to update http://microformateurs.org
** write a process for newbies in order to make them write [[posh-fr|CHIC]] posts on a public blog-governed-by-wiki ([http://socialsynergyweb.net/cgi-bin/wiki/MicroFormateurs/Blog]) before publication.
** find experts for peer-reviewing
** find french CSS gurus to setup a nice Sandbox-CSS template on Wordpress
* translating the wiki
** translate red links on [[Main_Page-fr]] and synchronize
** find out microformateurs at ease on "the-wiki-way-translation", and ready to help on semi-anonymous-synchro
* community-marketing -> pinko-marketing
** public-relations towards french journalists and complete [[advocacy-fr|advocacy]] (especially [[hcard-advocacy-fr]] towards organizations.
** help to build events, workshops like barcamps and explorcamps
** update [http://fr.wikipedia.org/wiki/Microformats French-wikipedia:Microformats] and subpages via cowriting [http://fr.wikipedia.org/wiki/Discuter:Microformats on discussion page] (directly originated from the english article) + french examples to be found + local resources.
** open discussion with french wikipediens about implementing some of the english existing templates
** small gifts: accessories and free gifts ? t-shirts, localized cheat-sheet, id-hcard-openid-providing, etc.
*** create hCard, hCalendar... and all red link pages on french wikipedia
* localize [[species-fr]] and related pages
* move all contents remaining on elanceur.org -> microformateurs.org
* wiki and uf:
** write and talk with "aboutus.org" to invite them to make experiences with uf -> talk with Mark Dilley
** maintain/update http://www.communitywiki.org/MicroFormats and talk with LionKimbro
** XWiki : awaiting beta-test of new platform
*** Follow-up LudovicDubost et LaurentLunati
* setup real-life links with european [[governance-fr|governance]] members ;) may be joining dconstruct-microformats-workshop - find solution (registering fees and travel expenses -> talk with Arnaud Fontaine or search french sponsors)

== Frances Berriman ==

[[User:Phae|Frances Berriman]]

* Clean up this todo list (meta!)
** Move alumni admin tasks out, and into a 'up for grabs' bucket (unless 100% specific to person).
*** Ping anyone with specific tasks / nag
* Proposal for page simplifications - notes, to expand to tasks later:
** Need a way to push active formats (those in the process) to the fore, and push back stagnating items.
** Process updates to blog?
** Activity overview updates on main site somewhere?
** In general: less clutter, more structure, more focus.

== Ben West (bewest) ==

[[User:BenWest|bewest]]
* fight spam
* help tend wiki
* documentation of semantic authoring techniques
* researching the social problems relating to authorship and publishing on the web
* development of new microformats in response to failing to meet the needs of the second with the first.

=== 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?

=== Vocabulary ===
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:
* "boil the ocean" A huge task. "A phrase used in the industry to describe an attempt at something that is way too ambitious. For example, "They're trying to get their site launched by COMDEX. They could easier boil the ocean." from <http://www.netlingo.com/right.cfm?term=boil%20the%20ocean>
* microformats: more than one microformat
* microformat: see my definition on http://microformats.org/wiki/what-are-microformats#BenWest
* data fidelity: the extent to which a data format might be considered lossy. eg HTML is often seen as a lossy format because the information parsed out of a resource may not fully match the information orginally encoded. Non-lossy formats have a very high data fidelity, while lossy formats have low data fidelity. Microformats seek to increase data fidelity of html.
* market: the locus of economic forces

: See [[glossary]]. [[User:AndyMabbett|Andy Mabbett]] 13:57, 7 Dec 2006 (PST)

=== Creators ===
_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.
* <strike>Start hatom creator.</strike> http://dichotomize.com/uf/hatom/creator.html
* Code Reuse. These creators are downright handy, and I’ve reimplemented the vcard one on my own site. Instead, let’s make these widgetized. Let’s decide on a more or less canonical html structure and create some javascript that will create the desired microformat. Something as easy to use as new Microformat.hCard($('mycontainer')); would be awesome. Right now, if someone makes an improvement to the hCard creator, the other creators don’t get the benefit. Spec this out!
* About Section. Is there an official creator page? If so, let’s point to that. The about paragraph is getting longer and longer with phrases like “which is based on…” repeated over and over.
* Default all dates to “right now”. Provide an easy to use calendar type widget to change dates.
* hAtom creator: Add multiple. It’d be nice to add an arbitrary number of entries.
* hAtom creator: Optional feed enclosure. Check box to wrap the entry/entries in an hfeed.
* Edit URI: Allow someone to enter a URI and edit whatever microformat is found on the page.
* Optionals. If the format requires, say, a vcard, the creator can defer to an external URI or can trust the user to fill it in later.
* Common stylesheet. I suppose this goes with the reuseable code idea… we have many great coders, we should be reusing eachothers’ work.
* Use Amazon's ECS to pull in information about products when there is an ASIN in the item URI.

=== 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 http://simile.mit.edu/solvent/ with the big questions right out front:
* What Is This?
* What can I do here?
* Is there a demo?
* Where can I learn more?
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?
* About the Community
** Where to find information.
** Who are the stake holders?
** FAQs
* Web/Architectural Philosophy
** Community Principles
** Why are we doing this?
** XML and Namespaces
** Semantic XHTML
** Common Misconceptions
** Concession and Disposition of Criticism
** FAQs
* Specs
** Examples
** Discussion
** Exploration
** Use Cases
** Implementations
** The spec itself.

* Tips and Tricks for Authoring ([[User:BenWest|BenWest]] 15:00, 9 Dec 2006 (PST))
** how to author semantic html
** choosing class names
** using HTML's general extension mechanisms
** advocating use
** collaborating/reusing HTML
** debugging HTML: use pastebin, separate out the relevant bits.
** getting help from the community
** applying Microformats.

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:
* Belong to a microformat? (eg hcard-bestof)
* or to the global namespace? (eg /wiki/wisdom/foobar-format)
(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 -- [[User:Cgriego|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.
http://microformats.org/wiki/hcard) 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:

* Microformat
** Specification
** Tutorial
** Examples
** Use cases
** Reference
** Discussion
** Brainstorming (might be combined w/Discussion)
** Implementations
** Related Pages
** Further Reading
** All (Uses Mediawiki's "includes" to create a page including all sub pages; very useful for printing & reading offline)

These pages would be located respectively at

* http://microformats.org/wiki/hcard/
** http://microformats.org/wiki/hcard/Specification
** http://microformats.org/wiki/hcard/Tutorial
** http://microformats.org/wiki/hcard/Examples
** http://microformats.org/wiki/hcard/Use_cases
** http://microformats.org/wiki/hcard/Reference
** http://microformats.org/wiki/hcard/Discussion
** http://microformats.org/wiki/hcard/Brainstorming
** http://microformats.org/wiki/hcard/Implementations
** http://microformats.org/wiki/hcard/Related_Pages
** http://microformats.org/wiki/hcard/Further_Reading
** http://microformats.org/wiki/hcard/All

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) ==

[[User:Thewhoo]]

=== hAtom2Atom ===
<ul>
<li>Support for other XSLT engines:
* hAtom2Atom written using XSL 2.0
</li>
<li>Support for other output formats: (hAtom2xyz.xsl)
* RSS 2.0 (meanwhile use hAtom2Atom.xsl and [http://atom.geekhood.net/ atom2rss.xsl])
* RSS 1.0 (meanwhile use hAtom2Atom.xsl and [http://cvs.4suite.org/viewcvs/uogbuji/atom2rss.xslt atom2rss.xslt])
* AtomOWL (meanwhile use hAtom2Atom.xsl and [http://dannyayers.com/2005/11/22/atomowl-xslt-progress/ atom2rdfxml.xsl])
</li>
</ul>

=== Microformats Proposals ===

* rel="disclaimer":
** Purpose: to create a semantic linkage (relationship) between a foot-note or end-note marker and the actual location of the text that the marker refers to.
* rel="external":
** Purpose: to formalize what is already in existence in the wild. The use of rel="external" to refer to a document that is external or outside of the current domain.

== Henri Bergius ==

[[User:HenriBergius|Henri Bergius]]

* Add hKit support for automatically populating contact details into [http://www.openpsa.org/version2/openpsa/contacts.html OpenPsa Contacts] CRM
* Implement Tail scripts for adding things into Midgard

== Justin Thorp ==
* Start researching examples for a To-do microformat

== [[User:MarkLentczner|Mark Lentczner]] ==

* Get Second Life's event web pages to have proper event microformats data
** Add [[hcard|hCard]] to profile pages
** Add [[hcalendar|hCalendar]] to events listings
* Start pinging pingerati.net/ping/$url when pages are updated
* Collaborate on designing how to integrate microformats, metadata and objects in [http://secondlife.com/ Second Life].

== [[User:DerrickPallas|Derrick Pallas]] ==
=== microformat proposal: dependancy ===
* looking for examples of directed graphs on the web
* applications in
** software engineering
*** automatically build library dependency trees
*** distribute security alerts to people that link to your code
** any directed, acyclic graph
*** getting dressed in the morning
*** cooking
* orthogonal to xfn
** people don't have versions
*** libfoo requires libbar-2.0 or later
** people don't have optional relationships
*** ex: at build time, compile in SSL support if present
** people don't have exclusive-or relationships
*** ex: in Gentoo, syslog, syslog-ng, and metalog satisfy virtual/syslog
*** ex: the Ruby library RMagick requires ImageMagick xor GraphicsMagick

== [[User:PaulDowney|Paul Downey]] ==
* building a generic Javascript parser
* bundling parser as a [http://tiddlywiki.org TidlyWiki] plugin for hCards
* documenting how best to microformat TiddlyWiki pages

== [[User:RobManson | Rob Manson]] ==
* chase the admins to get some creation template extensions installed for wiki (see: http://meta.wikimedia.org/wiki/Inputbox or http://www.mediawiki.org/wiki/Extension:CreateBox or http://www.mediawiki.org/wiki/Extension:CreateArticle)

== [[User:ClayNewton | Clay Newton]] ==
* Work on getting others involved in [[trade-examples]]
** Need examples from major online banking sites
** Need examples from major ecommerce sites
* Continue working on: [[trade-brainstorming]]

== [[User:BenWard | Ben Ward]] ==

=== Recurring ===

* Delete Wiki Spam

=== Currently ===

* Gardening/updating key wiki pages.
** [[how-to-play]]
** XHTML Design Principals
* embed brainstorming
* Considering new welcome banner of µf.org to link to various µf resources, rather than being dominated by the infrequently updated blog.

=== Next Actions ===

* Conclude new hCalendar proposals from Yahoo TV Listings experience
* Resume work on hListing microformat
* Re-org the Microformats.org front-page content
** Work with [[User:Phae]] on refreshing the microformats frontpage content
** Build new events module for the blog using Upcoming.org, rather than hard coded event data (Matt Harris may have done this…)
** Build new wiki edits module for the blog
** Combine ‘list of microformats’ into the intro text? Make intro text more friendly.
* Build a microformats activity stream
** Replace front page blog with activity flow
*** Wiki Edits/New Pages
*** New Mailing List Threads
*** Interesting µf links
*** Blog posts
*** Upcoming events/event reminders
* Improve µf.org/blog OpenID support, find a good workflow for login/comment (current plug-in has an abysmal user experience)

== [[User:Spiritquest|Ketan Majmudar]] ==
=== Activites ===
* Work on developing the [[hlisting-brainstorming|hListing]] proposal
** Provide real world examples and apply this to the proposed specifications
* refine and keep up to date with [[hcard|hCard]] formats as used on existing sites [[http://www.ethical-junction.org| Ethical Junction CIC]]
* Understand / follow and evangalise existing patterns, especially the new [[value-class-pattern]]
* see where I can help the community
* look at using x2v or writing php parser classes for hcard -> vcard
* open source hCard class (php) used to format db fields

User:Phae

2011-09-21T09:52:47Z

Phae: fed up of updating my details. pointing to /about

Frances Berriman
*About: [http://fberriman.com/about http://fberriman.com/about]
*Contact at fberriman@gmail.com

*Main interests regarding microformats:
** Improvement of how-to, educational resources and explanations for new microformat users
** Implementing microformats where ever possible to provide test beds for developers (see my blog)
** Accessibility testing of microformats (ask me if you want me to do testing for you)
** Spreading microformats

--

{{cc-public-domain-release}}

process

2011-09-21T09:51:09Z

Phae: /* related issues questions regarding document stages */ added some further thoughts on standard reversal

If this is your first visit, please see the [[introduction]] page first.

<entry-title>The microformats process</entry-title>

'''So you wanna develop a new microformat?'''

'''Or just a new vocabulary?'''

'''Or create a new standard based on empirical research and scientific methods?'''

This document will help guide you through the steps to take towards achieving these goals.

The microformats process has been cited as inspiration for other standards groups and efforts such as the WHATWG and ActivityStreams.

;Editor
:[[User:Tantek|Tantek Çelik]]

{{TOC-right}}

== Get some experience first ==
Before even considering pursuing a new microformat, first:

# Make your site [[POSH]].
# Add existing microformats to your sites like [[hcard|hCard]] for your contact info etc., [[hcalendar|hCalendar]] for your events, [[hatom|hAtom]] for your episodic content (e.g. blogs). See [[get-started]] for more specific examples of adding microformats to your sites.

This will help familiarize you with how [[POSH]] and [[microformats]] currently work. Such "real world" experience will greatly help you with the development a new microformat. For more on this see [[why-using-existing-microformats-matters]].

Then, ask yourself:

==Why?==
There must be a problem to be solved (i.e. a real world use case). No problem, no microformat.

Once you've found your 'problem,' ask yourself: 'is there a simpler problem here?' If so, let's solve that problem first. We want to deal with the simplest problems first and only then build up to more complex problems.

Perhaps someone else is pursuing (or has pursued) a similar problem.

Check the [[exploratory-discussion]] page, and search around on the web. Chances are that someone else has encountered the same problem as you. There are very few truly new problems.

If you still believe that you have a new and unsolved problem, post something to the [[irc]] channel, and if no one is around, then the [http://microformats.org/mailman/listinfo/microformats-new/ microformats-new] mailing list. It's better to get the community involved in the discussion. Start the discussion '''before''' you start creating any pages on the wiki.

We're not using the wiki as a general "scratch pad". If you can't summarize the problem you are trying to solve in a short email, and feel like you need a long document, you're probably trying to solve too big of a problem - see previous point about 'is there a simpler problem here?' and simplify until you describe your problem and real world use case in a short paragraph.

== Check Exploratory Discussions For Previous Work ==
It may be possible that someone else has tried (or is trying to) solve the same real world problems as you.

Check the [[exploratory-discussions]] page ''before'' starting new pages for your effort to see if you can add to / iterate on an existing effort before creating a new one.

==Document Current Behavior==
Document examples of current human publishing behavior.

[[why-examples|Why examples first?]] Read that. It's important and gets to the core of what makes microformats efforts different than many/most previous/other format development efforts.

We're [http://ifindkarma.typepad.com/relax/2004/12/microformats.html paving the cowpaths]- before you do that you have to ''find'' the cowpaths.

By ''cowpaths'' here we mean ''real world publishing examples''. Your [[examples]] should be a collection of real world sites and pages which are publishing the kind of data you wish to structure with a microformat. From those pages and sites, you should extract markup examples and especially the schemas implied therein, and provide analysis.

This collection of examples should be public, preferably on the microformats wiki because it's unlikely you can do it by yourself (no matter how many of you there are), and having others even just check your work will help improve its quality.

The [[reviews-formats]] page is a good example of research done before the creation of a microformat. Before developing [[hreview|hReview]], the collaborators went out, documented current practices around reviews on web sites, and provided some analysis of the schemas implied therein.

Note: these examples are about the ''content'' (and schemas ''implied'' therein) not about formats, class names, pre-existing standards etc. That comes next.

Study the examples and determine the ''implied'' (not explicit) schema of data that is being published (the conceptual properties about the data - not literal class names). Sort these by frequency and determine which appear in roughly 80% of cases (per the 80/20 rule, Pareto [[principle]]).

If you can't find real world publishing examples of the type of data you want to represent using a microformat, then stop here. It doesn't need a microformat.

==Document Previous Efforts==
Once you've documented real world publishing examples of the kinds of data you want to represent, the next step is to research efforts at developing formats for those kinds of data.

There are almost always previous efforts at formats for whatever kind of data you want to represent using microformats.

Learning from previous format efforts is important, because it helps:
* minimize repeating mistakes by others
* explore why a previous format succeeded (or didn't)
* provide a source of vocabulary to express a new microformat

In particular, ask yourself: "are there any well established, interoperably implemented standards we can look at which address this problem?"

For example, hCard and hCalendar were built on top of the IETF standards for vCard and iCal, respectively, both of which are widely interoperably implemented, and dominant in their space (there were no competing formats with anywhere near the same levels of adoption).

The developers of those standards had already spent many years in standards committees arguing about and developing their schemas. Better to leverage all the hard work that others have done before you, than to go off as a solo cowboy inventor, and waste time repeating all their mistakes. It's also much easier to start from a well established schema, and map into into semantic HTML than to develop a new schema.

It's quite possible during this step that you'll find someone else who has dealt with the problem(s) you're addressing. Perhaps even solved it/them. Do your best to open a dialog with others who have encountered the same problem(s). We don't want to build walls between competing communities - we want people to work together to develop a good solution which will cover the majority of cases.

If you can't find previous efforts at formats for the data you want to microformat, ask in [[IRC]] and on the [[mailing-lists]].

==Brainstorm Proposals==
By now you've researched previous examples and previous formats and you're finally ready to write up brainstorms towards a new microformat.

Actually, don't!

There are other things to try before developing a microformat. First, ask yourself these questions:

# Is there a standard element in HTML that would work?
# Is there a compound of HTML elements that would work?

If so, document these on the brainstorming page, and stop. There is no need for a microformat.

Let's not unnecessarily reinvent what you can already do with HTML.

For more details on semantic HTML, examples of using HTML elements, and constructing HTML (and XHTML) compounds, see [http://tantek.com/presentations/2005/03/elementsofxhtml/ The Elements of Meaningful XHTML].

Otherwise, if you can clearly and confidently answer "no" to the above two questions, we can talk about a microformat.

Before you start your act of creation, familiarize yourself [[microformats#the_microformats_principles|the microformats principles]].

There's basically two steps to writing up a brainstorm proposal:

# Go back to that list of real world publishing examples that you researched, and collect the 80/20 of the implied conceptual schema from the examples.
# Give each of those concepts a property name, re-using from, in order:
## existing microformats
## previous formats
## simple but specific human readable English words and phrases

Congratulations, you've written up a brainstorm proposal with a list of class names for a possible microformat.

You may notice that we completely skipped ''naming'' the potential new microformat itself. This is not an accident, this is deliberate. Naming is tempting, and good naming is hard. Thus naming is discussed later.

The key is, the explicit schema of the microformat (what properties and hence class names are in it) is '''more important''' than the name.

Remember, microformats should be designed for humans first and machines second. Here are few questions that may help you decide if you really need a microformat for the problem you are trying to solve:

# If I looked at this microformat in a browser that didn't support CSS or had CSS turned off, would it still be human-readable?
# Are this format's elements stylable with CSS?

If the proposed format doesn't pass these two things, it's not likely to gain much acceptance. Remember: ''humans first, machines second''.

== Iterate ==
Now that you have a simple brainstorm proposal, what do you do?

Iterate. Iterate. Iterate.

In the process of developing a microformat, you'll likely get a lot of feedback from others interested in microformats. The effort needs to be iterated and adapted. Microformat development should be open, and preferably collaborative and community-based.

Here's an ASCII-art flow diagram of where you're going
<pre>
DIAGRAM:
problem statement---->research/discussion---->proposal/draft---->specification
^________________V ^___________________V ^______________V
</pre>

Note that each stage involves iteration. That iteration consists of discussion and feedback and may result in major changes. Do not be afraid to make major changes and please don't get too attached to any particular solutions.

Feel free to explore ''multiple'' proposals one after another on the brainstorming page. The goal here is to explore reasonable microformat solutions, including multiple possibilities, alternatives etc.

== Naming considerations ==
'''DO NOT''' start with even labeling your effort "hXYZ". This is a ''very'' common mistake.

Always start with the general problem area.

Thus name the problem area (*- pages below) generically and specifically avoid starting with code name / brand name like hNewCoolFormat.

Good: '''[[product-examples]]'''. Bad: '''hProduct-examples'''.

After you've iterated your research and brainstorming at least a bit, you've likely gained sufficient understanding of the problem-space that you're solving to start looking at naming considerations.

== Pages to create ==
After a specific problem area ('''*''') has been determined (principle 1), consider creating and filling out the following pages for it, and add the first to [[exploratory-discussions]]. If you're unable to come up with material for the pages, then you should probably reconsider whether or not the problem is worth (or ready for) solving.
# '''*-examples''' Find examples on today's web of the the type of content you think needs a microformat. Document them with URLs. Document the schemas implied by the content examples. This is the action that helps follow principle 3, design for humans first, machines second ... adapt to current behaviors and usage patterns. Start by cloning the [[examples]] page and filling it out.
# '''*-formats''' Find widely adopted interoperable current data formats and standards that attempt to or have attempted to solve the problem previously. Document their explicit schemas. This is necessary prerequisite for following through with principle 4, "reuse building blocks from widely adopted standards".
# '''*-brainstorming''' Use the current real-world web examples and their implicit schemas to determine an 80/20 as-simple-as-possible (principle 2) generic schema to represent their data. Yes, this means you will explicitly ''omit'' some features of some use cases, or perhaps entire use cases which are more edge-cases than representative of larger, aggregate/macro behaviors. See which existing microformats can be reused as building blocks (principle 5, modularity). Use those existing data formats and schemas as a [[existing-classes|source of names]] for the fields (principle 4). Consider how would you embed this microformat in other formats (also principle 5, embeddability). See the [[brainstorming]] page for a bit more info. With an 80/20 schema, and a source of field names, write up one or more straw proposals for a microformat in the *-brainstorming page. Make sure the straw proposals encourage the decentralized distribution of data (principle 6). Postpone the choice of root class name as it often overlaps with the naming of the microformat itself. Always keep close at hand the [[naming-principles|microformats naming principles]] when choosing names.Brainstorming about the substance of the microformat (its properties and values) should precede naming the microformat itself. Thus after proposals have been written up and are being discussed for the schema, create a naming section for the microformat itself and root class name, where various names can be considered.
# '''**''' When it seems like there is rough consensus around one of the brainstorm proposals for a microformat with a specific name('''**'''), write it up as a separate wiki page as a draft specification (see [[style-guide]]), and then start creating the following pages to track it.
# '''**-faq''' There will likely be common questions about the new microformat which can/should be answered in an FAQ page.
# '''**-issues''' Folks may also raise issues about the microformat which aren't immediately addressable. An issues document helps serves to capture these issues, who raised them, and when, so that folks working on the microformat can be sure to go through and thoroughly answer them.
# '''**-examples''' Eventually there may be too many real world examples of a microformat to document them in an informative section at the end of the specification, thus the list deserves its own page.
# '''**-implementations''' Eventually there may be too many implementations of a microformat to document them in an informative section at the end of the specification, thus the list deserves its own page.
# '''**-brainstorming''' Eventually there will be non-trivial proposals/suggestions/clarifications for changes in the microformats as part of iteration. Create such a format specific [[brainstorming]] page for such suggestions.

== Moving from Stage to Stage ==
These stages of development are mirrored on the main page where microformats are divided into "Exploratory Discussions", "Drafts", and "Specifications". Based on feedback we've added a new stage: "Standards".

How do microformats move from one stage to the other?

=== Exploratory Discussions ===
Document your problem area, existing research, and brainstorm proposals on the [[exploratory-discussions]] page.
You should do it on this wiki using current items under exploratory discussion as a guide.

Then send a note to the microformats-new list to get the attention of others who are interested in microformats. This is probably a good chance to pull in people from outside the current microformats community who may also be experiencing the same issue.

Feedback will probably range the gamut. Others may challenge your problem statement, the need for a microformat, concur, or add. All constructive feedback is good.

As a result of feedback, you may decide to abandon your microformat idea or substantially modify it or add more alternatives to brainstorm proposals to consider.

One thing you want to be sure to do at this stage is to avoid [[reinvented-wheels|reinventing the wheel]].

Are there elemental microformats you can reuse as building blocks? Doing this will save you effort and help you get implemented later because implementers will have less work to do.

=== Drafts ===
Once there seems to be rough consensus around a particular brainstorm proposal, including a specific schema and list or properties, write that brainstorm proposal into a draft.

Summary of what is a draft:

* '''draft''' - experimental new microformat
** '''preconditions:'''
*** rough consensus has been reached among the various *-brainstorming proposals
** '''actions:'''
*** determine a name for the new microformat (**)
*** write-up consensus brainstorm into a stand-alone draft
*** create **-issues page for collecting feedback
** '''means:'''
*** ready for publishers to start experimenting with on their public pages
*** ready for consumers to start experimenting with consuming such publishers
*** and both providing feedback for draft iteration accordingly
** '''stability:'''
*** major changes can still occur
*** e.g. add/drop/rename arbitrary features (per research/feedback from publishers/consumers)

Drafts are written up on the wiki using the draft template. Upon writing up a draft, send a note to the microformats-new mailing list to alert people that something new has happened. Continue encouraging feedback from relevant resources both inside and outside the community. Drafts need to include at least the following:

* Statements regarding the fact that you will not patent and are adopting appropriate copyright (preferably PUBLIC DOMAIN) as illustrated by current drafts.
* An XMDP stating explicit property and value names. You may want to place this on a separate wiki page and link to it. In that case use the naming convention *-profile, e.g. [[hcard-profile]].
* Examples from current practice that show how the microformat would be used. Keep an eye out for how the microformat is actually improving things. If it's not, that might be an indication that you either need to abandon or change a lot.
* Use of [[rfc-2119]] terms.
* References that back up your design decisions for the microformat. To the extent possible, you do not want to invent things from whole cloth. This should be relatively easy if you have followed the process so far with proper research.
* A list of implementations (if any).
* An issues section for people to feed back to you with detailed objections.

=== Specifications ===
You will usually need at least one iteration to get past the draft stage.

By the time something becomes a specification, it should be stable so that developers can pick it up and write to it. This in turn implies that there are at least a couple of implementations.

This in turn implies that there are at least a couple of sites/implementations that have shown interest beyond the creator/editors of the specification.

Summary of what is a specification:

* '''specification''' - a stable and mature draft
** '''preconditions:'''
*** all outstanding **-issues resolved (hit zero issues for a few weeks)
*** 1+ solid real world publisher(s) that
**** are not the editor(s) of the spec (demonstrates some breadth of interest)
**** benefit end users (i.e. not just artificial data published for data's sake)
*** 1+ solid real world consumer(s) that
**** are not the editor(s) of the spec (demonstrates some breadth of interest)
**** successfully consume the microformats published by the publisher(s).
**** provide real world end user benefits / solve use-cases
**** (libraries/opensource are nice as enablers but insufficient for this)
** '''actions:'''
*** update draft to use specification template
*** create **-examples-in-wild, **-implementations pages to collect them
** '''means:'''
*** ready for publishers to start depending on
*** ready for consumers to start depending on
** '''stability:'''
*** minor changes can still occur
*** e.g. dropping of properties and values (e.g. to reach "standard" - see below)
*** iteration based on real-world publisher/consumer experience
** '''actions:'''
*** encourage widespread adoption by all publishers and consumers
*** evaluate properties published by <2 publishers
*** evaluate properties consumed by <2 consumers
**** such properties block advancement from specification to standard.
**** drop such under-supported property(ies) - insufficient market support to keep them. properties which fail in the real world should be and get dropped (per the simplify [[principle]]). features may be reconsidered for future versions.
**** or wait for more additional publisher(s)/consumer(s) to support them. up to editor's preference.
** '''example microformats to advance:'''
*** [[hReview]] and [[hAtom]] can become "specifications" with a bit of work:
**** resolve issues, incorporate into spec updates (0.4, 0.2 respectively)
**** *-examples-in-wild *-implementations pages show publisher(s)/consumer(s) support

Before moving to the specifications section, you must have resolved all outstanding issues.

Then, drop a note to microformats-new noting that all issues have been resolved, and encourage discussion and major objections. Since this may elicit additional feedback, allow some time (editor discretion, 3 weeks suggested), for more issues, resolutions, fixes.

If none are forthcoming, suggest moving the microformat to the specifications area. If there is sufficient explicit positive support from the community to do so, then do so. If not, then leave as draft. The absence of feedback is not approval and should be noted instead as a lack of interest.

=== Standard ===

This is a new document stage to represent not only stability, but market acceptance.

Summary of what is a standard:

* '''standard''' - market proven microformat
** '''preconditions:'''
*** test suite with 1+ test per feature (e.g. property) (should be easy)
*** 2+ solid real world publishers as defined above for "specification"
*** 2+ solid real world consumers as defined above for "specification" that:
**** pass the test suite tests
**** interoperably consume microformats published by the publishers.
*** each property is published by 2+ of those publishers
*** each property is consumed by 2+ of those consumers
** '''actions:'''
*** bump the version # to 1.0 (if it isn't there already)
** '''means:'''
*** the market is interoperably publishing and consuming this microformat
** '''stability:'''
*** the microformat is considered stable
*** minor errata expected per real world publishing/consuming experience
** '''example microformats to advance:'''
*** [[hCard]] and [[hCalendar]] can become "standards" with a bit of work:
**** incorporate resolved issues into 1.0.1 releases (use 1.0.1 due to how long we left them a 1.0)
**** write up remaining missing test cases for a full property (not necessarily value) coverage test suite
**** drop insufficiently supported properties (e.g. "class", "key")

==== documenting implementation support ====
Ideally implementation support should be documented with '''test suite results''':
* '''implementation test suite report''': list all tests and whether an implementation passes them or not
** these can be added to entries for each implementation in the '''**-implementations''' wiki page
* '''test suite implementation summary report''': list all tests and implementations that pass each one
** see the [[value-class-date-time-tests#results|value class pattern date and time test results]] table for an example.

'''Claimed implementation''': it's also useful to document:
* '''what properties/values/features''' an implementation ''claims'' to support
** with links to supporting documentation from the implementer's site
** list properties/values an implementation claims to support on the implementation's entry in the '''**-implementations''' wiki page

=== related issues questions regarding document stages ===

<div class="discussion">
* '''if/when does it make sense to demote a microformat spec to a lower level?'''
** '''can a standard be undone?''' we haven't seen any examples of this, but it is certainly possible that a sufficient implementations/publishers of a ''standard'' could disappear until it no longer meets requirements, should (and when should) it be demoted to just a ''specification'' or perhaps even a ''draft''?
** '''from spec back to draft''' it's possible that implementations or publishers may disappear, and thus what used to qualify as a ''specification'' no longer meets the requirements, when should it be demoted explicitly back to a ''draft''?
*** Can we just mark these as "specification" but also "deprecated"? Possibly with a note that says something along the lines of "this draft is deprecated because of X, Y, Z reasons. Returning this specification to a standard requires A, B, C work". I imagine this situation is most likely to arise in the situation that a problem with the standard arose, preventing or reducing implementations, right? [[User:Phae|Phae]] 09:51, 21 September 2011 (UTC)
** '''undrafts''' e.g. there are plenty of drafts that never got any traction, should we have another category for "uninteresting-draft" that means no one other than the editor(s)/author(s) really cared for it, and thus it isn't a priority for the community. maybe we could call these "undrafts" - where drafts go when they don't make it to spec after some amount of time. From there it's probably best to simply use them for more brainstorming, and not encumber any future microformat effort with their legacy. This is likely important to keep the list of drafts as accurate/recent, and will also likely be challenging case-by-case judgment calls.
*** Perhaps rather than ‘undraft’, which is a slightly horrendous word, or ‘uninteresting’ which carries a subjective judgement, we could instead approach this with a kind of archiving strategy. After some period of non-progress/non-involvement/instability a draft becomes ‘Archived’ (or ‘Archived Draft’) to indicate the stagnation. It could become a regular draft again if someone finds it an interesting base. --[[User:BenWard|BenWard]] 00:48, 20 September 2011 (UTC)
**** I know this is super unimportant in the scheme of things, but in my mind, "archive" also tends to suggest old, if not also uninteresting. Couldn't they just be "Suggested draft" or something that suggests that they're not necessarily naff, they just don't have any friends/evidence/solidified paths yet, but could do if you went and had a look and got on-board with the effort for that draft? Should we have "rejected drafts" for those we really do mean to put down because they've been identified as out of scope etc. [[User:Phae|Phae]] 09:51, 21 September 2011 (UTC)
</div>

== Other Documents ==
=== Patterns ===
What about other types of pages on the wiki, like "patterns" (e.g. [[include-pattern]])?

How do those get created?

The short explanation is this:

The patterns are not formats at all. They do not stand on their own. They are merely documentation of pieces of other formats that are expected to (or are) being reused by other formats.

The real world examples for includes in particular were documented in the context of [[resume-examples]], [[resume-formats]], and [[resume-brainstorming]] (as noted at the very top of [[include-pattern|the document]]) "Initially developed as part of resume-brainstorming..." Later, real world examples for reviews were found to need the include pattern as well.

When real world examples for ''multiple'' microformats require the solution of the same or a similar problem, then it is worth exploring the creation of a pattern that solves the problem across microformats.

== Related ==
* [[process-faq]]
* [[process-issues]]
* [[process-brainstorming]]

events/2011-03-14-future-of-microformats

2011-03-13T22:52:38Z

Phae: hashtag reminder

<entry-title>The Future of Microformats - SXSW Interactive 2011</entry-title>
__TOC__
One of several microformats [[events]].

<div class="event-page vevent">
== Details ==
;When
:2011-03-14 from 15:30
;Where
:Austin Convention Center, 500 E Cesar Chavez Street, Austin, Texas 78701 USA
;What
:The Future of Microformats - SXSW Interactive Session
;Web
:http://upcoming.yahoo.com/event/7697872/
:http://www.facebook.com/event.php?eid=199322750085180
:http://plancast.com/p/3q33
:http://austin2011.sched.org/event/7fd1f13aec1a51466384a986cf6da1b3

'''[http://h2vx.com/ics/microformats.org/wiki/events/2011-03-14-future-of-microformats Add this event to your calendar]''' http://www.boogdesign.com/images/buttons/microformat_hcalendar.png

== Summary ==
<div class="description">Google, via its rich snippets, has reported that microformats has a 94% usage share (as compared with RDFa etc.). So how does the future look for microformats? In this session, we'll look closely at real problems with implementing microformats in [[HTML5]] and how this can be done, and whether there will be a continuing place for them. We'll also look at emerging technologies and techniques, such as [[RelMeAuth]] and discuss advanced user techniques.

== Tags ==
Use the following tags on related content (blog posts, photos, [http://twitter.com tweets]):

tags:
<kbd class="tags" style="display:block">
'''microformats-session'''
'''futuremf'''
microformats-meetup
microformats
austin
tx
texas
sxsw
sxswi
sxsw2011
sxswi2011
''microformats-session-2011-03-14''
''upcoming:event=7697872''
</kbd>

If you use Twitter, mention ''@microformats''' in tweets about the event, and track them on [http://search.twitter.com/search?q=microformats Twitter Search].

== Attendees ==
Add yourself alphabetically sorted by family name if you plan on attending or attended this event.

* [[User:Phae|Frances Berriman]]
* [[User:Tantek|Tantek Çelik]]
* [[User:YourName|You]]
* ...

== Notes ==

Topics Discussed:

* ...

== Q&A ==

Not going to be in the panel or too shy to step up to the mic? Add your question below by 2pm on the day, or email frances@fberriman.com, or tweet us using the hashtag #futuremf
* Question... From Your Name
* Q: What are the most creative and inspiring uses you've seen, from all this Webby data? (Sorry I can't be there to ask in person...) -- Dan Brickley
* Q: Nowadays, we have to choose the *format* in which they add semantics to our page or fall in a vortex of repetition. Microformats, rdfa, pure rdf and/or microdata. What will be microformat's (project, community) role in the near future? Be responsibile for the vocabularies used in microdata? Or be an alternative to microdata? -- andr3

== Photographs ==

* Search for photographs from this event on Flickr: [http://flickr.com/photos/tags/microformats-session-2011-03-14 Photographs tagged microformats-session-2011-03-14] or for [http://flickr.com/photos/tags/microformats-session all photographs from microformats sessions].

''Add a photograph from this event here''.

== Articles and Blog Posts ==
Articles and blog posts following up on the meetup. Add a link to your post in the list below:

* ...

Also, find posts on this meetup on [http://blogsearch.google.com/blogsearch?q=microformats-session-2011-03-14 Google Blog Search] or [http://technorati.com/search/microformats-session-2011-03-14 Technorati].

</div> 

== Related Pages==
{{events-related-pages}}

events/2011-03-14-future-of-microformats

2011-03-13T19:42:41Z

Phae: q&a section

<entry-title>The Future of Microformats - SXSW Interactive 2011</entry-title>
__TOC__
One of several microformats [[events]].

<div class="event-page vevent">
== Details ==
;When
:2011-03-14 from 15:30
;Where
:Austin Convention Center, 500 E Cesar Chavez Street, Austin, Texas 78701 USA
;What
:The Future of Microformats - SXSW Interactive Session
;Web
:http://upcoming.yahoo.com/event/7697872/
:http://www.facebook.com/event.php?eid=199322750085180
:http://plancast.com/p/3q33
:http://austin2011.sched.org/event/7fd1f13aec1a51466384a986cf6da1b3

'''[http://h2vx.com/ics/microformats.org/wiki/events/2011-03-14-future-of-microformats Add this event to your calendar]''' http://www.boogdesign.com/images/buttons/microformat_hcalendar.png

== Summary ==
<div class="description">Google, via its rich snippets, has reported that microformats has a 94% usage share (as compared with RDFa etc.). So how does the future look for microformats? In this session, we'll look closely at real problems with implementing microformats in [[HTML5]] and how this can be done, and whether there will be a continuing place for them. We'll also look at emerging technologies and techniques, such as [[RelMeAuth]] and discuss advanced user techniques.

== Tags ==
Use the following tags on related content (blog posts, photos, [http://twitter.com tweets]):

tags:
<kbd class="tags" style="display:block">
'''microformats-session'''
'''futuremf'''
microformats-meetup
microformats
austin
tx
texas
sxsw
sxswi
sxsw2011
sxswi2011
''microformats-session-2011-03-14''
''upcoming:event=7697872''
</kbd>

If you use Twitter, mention ''@microformats''' in tweets about the event, and track them on [http://search.twitter.com/search?q=microformats Twitter Search].

== Attendees ==
Add yourself alphabetically sorted by family name if you plan on attending or attended this event.

* [[User:Phae|Frances Berriman]]
* [[User:Tantek|Tantek Çelik]]
* [[User:YourName|You]]
* ...

== Notes ==

Topics Discussed:

* ...

== Q&A ==

Not going to be in the panel or too shy to step up to the mic? Add your question below by 2pm on the day, or email frances@fberriman.com
* Question... From Your Name
* ...

== Photographs ==

* Search for photographs from this event on Flickr: [http://flickr.com/photos/tags/microformats-session-2011-03-14 Photographs tagged microformats-session-2011-03-14] or for [http://flickr.com/photos/tags/microformats-session all photographs from microformats sessions].

''Add a photograph from this event here''.

== Articles and Blog Posts ==
Articles and blog posts following up on the meetup. Add a link to your post in the list below:

* ...

Also, find posts on this meetup on [http://blogsearch.google.com/blogsearch?q=microformats-session-2011-03-14 Google Blog Search] or [http://technorati.com/search/microformats-session-2011-03-14 Technorati].

</div> 

== Related Pages==
{{events-related-pages}}

events/2011-04-12-uk

2011-02-27T21:21:23Z

Phae: /* attendees */ added me

<entry-title>UK Meetup April 2011</entry-title>
__TOC__
One of several microformats [[events]].

== Idea ==
It has been a while since we had a microformats meet-up in the UK. The idea is for an event that is part social and part workshop to brainstorm the [[hcard-input-brainstorming|input micorformat]] ideas. As Tantek is in the UK between the 11-16 of April this would seem the best time to hold the event.

Please help us by adding your preferences to this page so we can organise the best time and place.

== what venue ==
These are venues we have used in the past, I am not sure if they still have the right layout or atmosphere for a meeting. Please add other venues that you think maybe good for the event. They need to be central and near good transport links?

<div class="discussion">
* London
** +1 If we hold the event in central London more people are likly to come along [[User:GlennJones|Glenn Jones]]
** +1 Possibly more venue choice, also. [[User:Phae|Phae]]
* Brighton
</div>

<div class="discussion">
* The Bricklayers Arms — 31 Gresse Street, London
* The Yorkshire Grey — 2 Theobald's Road, London
* Pitcher and Piano — 42 Kingsway, London
* Brew Wharf Yard — 2 Stoney Street, London
* The Princess — 76 Paul Street, London
* The Yorkshire Grey — 29-33 Grays Inn Road, London
** This is where we had the last vEvent (ages ago). They let us have the upstairs room for free. [[User:Phae|Phae]]
</div>

== what date ==
Which is the best date for the event?

<div class="discussion">
* Monday 11 April
* Tuesday 12 April
** +1 Held on a Tuesday night before [[User:GlennJones|Glenn Jones]]
** +1 London pubs are more easily bookable early in the week. [[User:Phae|Phae]]
* Wednesday 13 April
** -1 UX London is on this day
* Thursdays 14 April
** -1 Pub Standards is on this night [[User:GlennJones|Glenn Jones]]
** -1 UX London is on this day
* Friday 15 April
** -1 UX London is on this day
* Saturday 16 April
</div>

== attendees ==
Add yourself alphabetically sorted by family name if you plan on attending or attended.

* [[User:Phae|Frances Berriman]]
* [[User:Tantek|Tantek Çelik]]
* [[User:PaulDowney|Paul Downey (fn)]]
* [[User:SpikeUK|Chris Foote]]
* [[User:GlennJones|Glenn Jones (fn)]]
* ...

== photographs ==

* ...

== notes ==
Topics discussed, comments, and Q&A.

* …

== articles and blog posts ==
Articles and blog posts following up on the meetup. Add a link to your post in the list below. Newest first.

* ...

== related pages==
{{events-related-pages}}

events

2011-02-26T21:57:36Z

Phae: /* upcoming */ pretty url

<entry-title>Microformats events</entry-title>
Please add microformats related events (including events which have sessions on microformats) below.

Use the [[events-template|events template]] to create events pages, and list URLs, details, attendees, recommended tags, link to photos afterwards, etc. Add links to slides and other media to the [[presentations]], [[podcasts]] pages respectively.

Encourage the use of microformats on event sites' pages themselves, e.g. [[hCalendar]] and [[hCard]] for the schedule, sessions, speakers, and venues.

== Add events to your calendar ==
Subscribe to current and future microformats events:

iCal, Evolution:
* click to subscribe: http://h2vx.com/ics/sub/microformats.org/wiki/events
* set it to update (i.e. "<nowiki>[x]</nowiki> Refresh" or "Auto-refresh: Every day") and new events will appear automatically.

Zimbra:
* Choose the "'''Calendar'''" tab
* in the far left column, click the new calendar icon (little mini green calendar with a plus sign, top right corner of the column header), a "'''Create New Calendar'''" dialog box should appear
* enter "microformats events" into the '''Name''' field
* check the 2nd checkbox: '''<nowiki>[x]</nowiki> Synchronize appointments from remote calendar'''
* copy this URL: '''<code><nowiki>http://h2vx.com/ics/microformats.org/wiki/events</nowiki></code>'''
* paste it into the '''URL''' field and click '''<nowiki>[ OK ]</nowiki>'''

You may also download [http://h2vx.com/ics/microformats.org/wiki/events events on this page as an iCalendar file].

__TOC__

== regular ==
* regular [[meetup]] - community meetups. details inside.

== upcoming ==


*2011-03-09: [[events/2011-03-09-microformats-dinner|Microformats Dinner]] with special guest Frances Berriman at TBD, San Francisco, CA. http://microformats.org/wiki/events/2011-03-09-microformats-dinner

*2011-03-10..<abbr style="border:0" class="dtend" title="2011-03-15">15</abbr>: [[events/2011-03-sxsw|SXSW 2011]] at Austin, Texas. Lots of microformats related events happening at SXSW 2011 including a panel: "The Future of Microformats". http://microformats.org/events/2011-03-sxsw
**2011-03-13: SXSWi 2011 Activity Streams Meet-up at SXSW Interactive, Austin, Texas. http://plancast.com/p/38g9
**2011-03-14: [[events/2011-03-14-future-of-microformats|The Future of Microformats]] at SXSW Interactive, Austin, Texas. http://microformats.org/wiki/events/2011-03-14-future-of-microformats

*2011-04: Microformat UK meet-up with focused discussion on input format with Glenn Jones at TBD, Brighton or London. http://microformats.org/wiki/events/2011-04-uk

== recent ==


=== February 2011 ===
*2011-02-22: [[events/2011-02-22-microformats-dinner|Microformats Dinner & Drinks]] with special guest Edward O'Connor at Naan N' Chutney, 525 Haight st., San Francisco, CA. http://microformats.org/wiki/events/2011-02-22-microformats-dinner

*2011-02-10: ActivityStrea.ms Spec Meetup at Socialcast at 2 South Park St., San Francisco, CA 94107. http://plancast.com/p/3kng

*2011-02-01: [[events/2011-02-01-microformats-dinner|Microformats Dinner & Drinks]] at 21st Amendment, San Francisco, CA. http://microformats.org/wiki/events/2011-02-01-microformats-dinner

=== October 2010 ===
* Tantek Çelik on HTML5 at Front-Trends in Warsaw discussed microformats and [[HTML5]]

=== September 2010 ===
* Jeremy Keith workshop on HTML5+microformats at dConstruct 2010

=== August 2010 ===
*2010-08-19 at 19:00: [[events/2010-08-19-weekly-dinner-sf|Microformats + Activity Streams Meetup San Francisco]] at Westfield Food Court, San Francisco, California. http://microformats.org/wiki/events/2010-08-19-dinner-sf

=== July 2010 ===
* ... need to add talks by Tantek Çelik at CascadeSF on HTML5+CSS3+microformats, and at OpenWebCamp on HTML5+microformats+S5
* ... Federated Social Web summit - included discussions of hCard and identity

=== June 2010 ===
* ... need to add Voices That Matter talks on microformats by Emily Lewis and HTML5+microformats by Tantek Çelik

=== May 2010 ===
*2010-05-04 at 19:00: [[events/2010-05-04-weekly-dinner-sf|Microformats Dinner San Francisco]] at 21st Amendment, San Francisco, California. http://microformats.org/wiki/events/2010-05-04-weekly-dinner-sf

*2010-05-02: [[events/2010-05-02-microformats-2-0|microformats 2.0 discussion]] facilitated by [[User:Tantek|Tantek Çelik]] at Cambridge, MA. http://microformats.org/wiki/events/2010-05-02-microformats-2-0

=== April 2010 ===
*2010-04-23: [[events/2010-04-23-html5-workshop|HTML5 for Web Designers]] by Jeremy Keith at Brighton. http://workshopsfortheweb.com/html5/

=== March 2010 ===
*2010-03-12 to 2010-03-16: [[events/2010-03-12-sxsw|<abbr title="South by Southwest Interactive Festival">SXSWi</abbr>]] at Austin Convention Center, Austin.
** 2010-03-14 at 1:10pm: [[events/2010-03-14-sxsw-microformats-government|Microformats and Government]] at Room 9ABC, Austin Convention Center, Austin, <abbr title="Texas" class="region">TX</abbr>. http://microformats.org/wiki/events/2010-03-14-sxsw-microformats-government
** 2010-03-15 at 9:30am: [[events/2010-03-15-sxsw-open-science|Open Science: Create, Collaborate, Communicate]] at Room 10AB, Austin Convention Center, Austin, <abbr title="Texas" class="region">TX</abbr>. http://microformats.org/wiki/events/2010-03-15-sxsw-open-science

=== February 2010 ===
*2010-02-17 at 19:00: [[events/2010-02-17-webkit-html5-benkyokai|3rd Webkit/HTML5 Benkyokai (第3回Webkit/HTML5勉強会)]] at グリー株式会社（東京都港区六本木4-1-4 黒崎ビル5F (Tokyo, Japan)）. [http://oli.jp/ Oli Studholme] presenting on Microformats and Microdata (in Japanese). http://atnd.org/events/3058

*2010-02-02 at 18:30: [[events/2010-02-02-weekly-dinner-mv|Microformats Weekly Meetup Mountain View]] at Gyros House, Mountain View, California. http://microformats.org/wiki/events/2010-02-02-weekly-dinner-mv

=== January 2010 ===
*2010-01-19 at 19:00: [[events/2010-01-19-weekly-dinner-sf|Microformats Weekly Meetup San Francisco]] at Westfield Food Court, San Francisco, California. http://microformats.org/wiki/events/2010-01-19-weekly-dinner-sf

*2010-01-12 at 18:30: [[events/2010-01-12-weekly-dinner-sf|Microformats Dinner San Francisco]] at Pancho Villa Taqueria, San Francisco, California. http://microformats.org/wiki/events/2010-01-12-weekly-dinner-sf

*2010-01-05 at 18:30: [[events/2010-01-05-weekly-dinner-sf|Microformats Dinner San Francisco]] at 21st Amendment, San Francisco, California. http://microformats.org/wiki/events/2010-01-05-weekly-dinner-sf

== Previous events ==
Previous years' events can be found at the following:
* [[events-2009]]
* [[events-2008]]
* [[events-2007]]
* [[events-2006]]

== Other languages ==
* [[current_events-fr|événements en cours]] (fr)

== Quicktime Broadcaster Notes ==
See [[quicktime]]

==Related pages==
{{events-related-pages}}

events

2011-02-26T21:56:31Z

Phae: /* upcoming */ adding link thru to event page for april meetup

<entry-title>Microformats events</entry-title>
Please add microformats related events (including events which have sessions on microformats) below.

Use the [[events-template|events template]] to create events pages, and list URLs, details, attendees, recommended tags, link to photos afterwards, etc. Add links to slides and other media to the [[presentations]], [[podcasts]] pages respectively.

Encourage the use of microformats on event sites' pages themselves, e.g. [[hCalendar]] and [[hCard]] for the schedule, sessions, speakers, and venues.

== Add events to your calendar ==
Subscribe to current and future microformats events:

iCal, Evolution:
* click to subscribe: http://h2vx.com/ics/sub/microformats.org/wiki/events
* set it to update (i.e. "<nowiki>[x]</nowiki> Refresh" or "Auto-refresh: Every day") and new events will appear automatically.

Zimbra:
* Choose the "'''Calendar'''" tab
* in the far left column, click the new calendar icon (little mini green calendar with a plus sign, top right corner of the column header), a "'''Create New Calendar'''" dialog box should appear
* enter "microformats events" into the '''Name''' field
* check the 2nd checkbox: '''<nowiki>[x]</nowiki> Synchronize appointments from remote calendar'''
* copy this URL: '''<code><nowiki>http://h2vx.com/ics/microformats.org/wiki/events</nowiki></code>'''
* paste it into the '''URL''' field and click '''<nowiki>[ OK ]</nowiki>'''

You may also download [http://h2vx.com/ics/microformats.org/wiki/events events on this page as an iCalendar file].

__TOC__

== regular ==
* regular [[meetup]] - community meetups. details inside.

== upcoming ==


*2011-03-09: [[events/2011-03-09-microformats-dinner|Microformats Dinner]] with special guest Frances Berriman at TBD, San Francisco, CA. http://microformats.org/wiki/events/2011-03-09-microformats-dinner

*2011-03-10..<abbr style="border:0" class="dtend" title="2011-03-15">15</abbr>: [[events/2011-03-sxsw|SXSW 2011]] at Austin, Texas. Lots of microformats related events happening at SXSW 2011 including a panel: "The Future of Microformats". http://microformats.org/events/2011-03-sxsw
**2011-03-13: SXSWi 2011 Activity Streams Meet-up at SXSW Interactive, Austin, Texas. http://plancast.com/p/38g9
**2011-03-14: [[events/2011-03-14-future-of-microformats|The Future of Microformats]] at SXSW Interactive, Austin, Texas. http://microformats.org/wiki/events/2011-03-14-future-of-microformats

*2011-04: Microformat UK meet-up with focused discussion on input format with Glenn Jones at TBD, Brighton or London. http://microformats.org/wiki/index.php?title=events/2011-04-uk

== recent ==


=== February 2011 ===
*2011-02-22: [[events/2011-02-22-microformats-dinner|Microformats Dinner & Drinks]] with special guest Edward O'Connor at Naan N' Chutney, 525 Haight st., San Francisco, CA. http://microformats.org/wiki/events/2011-02-22-microformats-dinner

*2011-02-10: ActivityStrea.ms Spec Meetup at Socialcast at 2 South Park St., San Francisco, CA 94107. http://plancast.com/p/3kng

*2011-02-01: [[events/2011-02-01-microformats-dinner|Microformats Dinner & Drinks]] at 21st Amendment, San Francisco, CA. http://microformats.org/wiki/events/2011-02-01-microformats-dinner

=== October 2010 ===
* Tantek Çelik on HTML5 at Front-Trends in Warsaw discussed microformats and [[HTML5]]

=== September 2010 ===
* Jeremy Keith workshop on HTML5+microformats at dConstruct 2010

=== August 2010 ===
*2010-08-19 at 19:00: [[events/2010-08-19-weekly-dinner-sf|Microformats + Activity Streams Meetup San Francisco]] at Westfield Food Court, San Francisco, California. http://microformats.org/wiki/events/2010-08-19-dinner-sf

=== July 2010 ===
* ... need to add talks by Tantek Çelik at CascadeSF on HTML5+CSS3+microformats, and at OpenWebCamp on HTML5+microformats+S5
* ... Federated Social Web summit - included discussions of hCard and identity

=== June 2010 ===
* ... need to add Voices That Matter talks on microformats by Emily Lewis and HTML5+microformats by Tantek Çelik

=== May 2010 ===
*2010-05-04 at 19:00: [[events/2010-05-04-weekly-dinner-sf|Microformats Dinner San Francisco]] at 21st Amendment, San Francisco, California. http://microformats.org/wiki/events/2010-05-04-weekly-dinner-sf

*2010-05-02: [[events/2010-05-02-microformats-2-0|microformats 2.0 discussion]] facilitated by [[User:Tantek|Tantek Çelik]] at Cambridge, MA. http://microformats.org/wiki/events/2010-05-02-microformats-2-0

=== April 2010 ===
*2010-04-23: [[events/2010-04-23-html5-workshop|HTML5 for Web Designers]] by Jeremy Keith at Brighton. http://workshopsfortheweb.com/html5/

=== March 2010 ===
*2010-03-12 to 2010-03-16: [[events/2010-03-12-sxsw|<abbr title="South by Southwest Interactive Festival">SXSWi</abbr>]] at Austin Convention Center, Austin.
** 2010-03-14 at 1:10pm: [[events/2010-03-14-sxsw-microformats-government|Microformats and Government]] at Room 9ABC, Austin Convention Center, Austin, <abbr title="Texas" class="region">TX</abbr>. http://microformats.org/wiki/events/2010-03-14-sxsw-microformats-government
** 2010-03-15 at 9:30am: [[events/2010-03-15-sxsw-open-science|Open Science: Create, Collaborate, Communicate]] at Room 10AB, Austin Convention Center, Austin, <abbr title="Texas" class="region">TX</abbr>. http://microformats.org/wiki/events/2010-03-15-sxsw-open-science

=== February 2010 ===
*2010-02-17 at 19:00: [[events/2010-02-17-webkit-html5-benkyokai|3rd Webkit/HTML5 Benkyokai (第3回Webkit/HTML5勉強会)]] at グリー株式会社（東京都港区六本木4-1-4 黒崎ビル5F (Tokyo, Japan)）. [http://oli.jp/ Oli Studholme] presenting on Microformats and Microdata (in Japanese). http://atnd.org/events/3058

*2010-02-02 at 18:30: [[events/2010-02-02-weekly-dinner-mv|Microformats Weekly Meetup Mountain View]] at Gyros House, Mountain View, California. http://microformats.org/wiki/events/2010-02-02-weekly-dinner-mv

=== January 2010 ===
*2010-01-19 at 19:00: [[events/2010-01-19-weekly-dinner-sf|Microformats Weekly Meetup San Francisco]] at Westfield Food Court, San Francisco, California. http://microformats.org/wiki/events/2010-01-19-weekly-dinner-sf

*2010-01-12 at 18:30: [[events/2010-01-12-weekly-dinner-sf|Microformats Dinner San Francisco]] at Pancho Villa Taqueria, San Francisco, California. http://microformats.org/wiki/events/2010-01-12-weekly-dinner-sf

*2010-01-05 at 18:30: [[events/2010-01-05-weekly-dinner-sf|Microformats Dinner San Francisco]] at 21st Amendment, San Francisco, California. http://microformats.org/wiki/events/2010-01-05-weekly-dinner-sf

== Previous events ==
Previous years' events can be found at the following:
* [[events-2009]]
* [[events-2008]]
* [[events-2007]]
* [[events-2006]]

== Other languages ==
* [[current_events-fr|événements en cours]] (fr)

== Quicktime Broadcaster Notes ==
See [[quicktime]]

==Related pages==
{{events-related-pages}}

events/2011-04-12-uk

2011-02-26T21:52:03Z

Phae: /* what date */ more agrees

<entry-title>UK Meetup April 2011</entry-title>
__TOC__
One of several microformats [[events]].

== Idea ==
It has been a while since we had a microformats meet-up in the UK. The idea is for an event that is part social and part workshop to brainstorm the [[hcard-input-brainstorming|input micorformat]] ideas. As Tantek is in the UK between the 11-16 of April this would seem the best time to hold the event.

Please help us by adding your preferences to this page so we can organise the best time and place.

== what venue ==
These are venues we have used in the past, I am not sure if they still have the right layout or atmosphere for a meeting. Please add other venues that you think maybe good for the event. They need to be central and near good transport links?

<div class="discussion">
* London
** +1 If we hold the event in central London more people are likly to come along [[User:GlennJones|Glenn Jones]]
** +1 Possibly more venue choice, also. [[User:Phae|Phae]]
* Brighton
</div>

<div class="discussion">
* The Bricklayers Arms — 31 Gresse Street, London
* The Yorkshire Grey — 2 Theobald's Road, London
* Pitcher and Piano — 42 Kingsway, London
* Brew Wharf Yard — 2 Stoney Street, London
* The Princess — 76 Paul Street, London
* The Yorkshire Grey — 29-33 Grays Inn Road, London
** This is where we had the last vEvent (ages ago). They let us have the upstairs room for free. [[User:Phae|Phae]]
</div>

== what date ==
Which is the best date fro the event?

<div class="discussion">
* Monday 11 April
* Tuesday 12 April
** +1 Held on a Tuesday night before [[User:GlennJones|Glenn Jones]]
** +1 London pubs are more easily bookable early in the week. [[User:Phae|Phae]]
* Wednesday 13 April
* Thursdays 14 April
** -1 Pub Standards is on this night [[User:GlennJones|Glenn Jones]]
* Friday 15 April
* Saturday 16 April
</div>

== attendees ==
Add yourself alphabetically sorted by family name if you plan on attending or attended.

* [[User:GlennJones|Glenn Jones (fn)]]
* ...

== photographs ==

* ...

== notes ==
Topics discussed, comments, and Q&A.

* …

== articles and blog posts ==
Articles and blog posts following up on the meetup. Add a link to your post in the list below. Newest first.

* ...

== related pages==
{{events-related-pages}}

events/2011-04-12-uk

2011-02-26T21:50:04Z

Phae: /* what venue */ possible venue

<entry-title>UK Meetup April 2011</entry-title>
__TOC__
One of several microformats [[events]].

== Idea ==
It has been a while since we had a microformats meet-up in the UK. The idea is for an event that is part social and part workshop to brainstorm the [[hcard-input-brainstorming|input micorformat]] ideas. As Tantek is in the UK between the 11-16 of April this would seem the best time to hold the event.

Please help us by adding your preferences to this page so we can organise the best time and place.

== what venue ==
These are venues we have used in the past, I am not sure if they still have the right layout or atmosphere for a meeting. Please add other venues that you think maybe good for the event. They need to be central and near good transport links?

<div class="discussion">
* London
** +1 If we hold the event in central London more people are likly to come along [[User:GlennJones|Glenn Jones]]
** +1 Possibly more venue choice, also. [[User:Phae|Phae]]
* Brighton
</div>

<div class="discussion">
* The Bricklayers Arms — 31 Gresse Street, London
* The Yorkshire Grey — 2 Theobald's Road, London
* Pitcher and Piano — 42 Kingsway, London
* Brew Wharf Yard — 2 Stoney Street, London
* The Princess — 76 Paul Street, London
* The Yorkshire Grey — 29-33 Grays Inn Road, London
** This is where we had the last vEvent (ages ago). They let us have the upstairs room for free. [[User:Phae|Phae]]
</div>

== what date ==
Which is the best date fro the event?

<div class="discussion">
* Monday 11 April
* Tuesday 12 April
** +1 Held on a Tuesday night before [[User:GlennJones|Glenn Jones]]
* Wednesday 13 April
* Thursdays 14 April
** -1 Pub Standards is on this night [[User:GlennJones|Glenn Jones]]
* Friday 15 April
* Saturday 16 April
</div>

== attendees ==
Add yourself alphabetically sorted by family name if you plan on attending or attended.

* [[User:GlennJones|Glenn Jones (fn)]]
* ...

== photographs ==

* ...

== notes ==
Topics discussed, comments, and Q&A.

* …

== articles and blog posts ==
Articles and blog posts following up on the meetup. Add a link to your post in the list below. Newest first.

* ...

== related pages==
{{events-related-pages}}

events/2011-04-12-uk

2011-02-26T21:47:11Z

Phae: /* what venue */ approval

<entry-title>UK Meetup April 2011</entry-title>
__TOC__
One of several microformats [[events]].

== Idea ==
It has been a while since we had a microformats meet-up in the UK. The idea is for an event that is part social and part workshop to brainstorm the [[hcard-input-brainstorming|input micorformat]] ideas. As Tantek is in the UK between the 11-16 of April this would seem the best time to hold the event.

Please help us by adding your preferences to this page so we can organise the best time and place.

== what venue ==
These are venues we have used in the past, I am not sure if they still have the right layout or atmosphere for a meeting. Please add other venues that you think maybe good for the event. They need to be central and near good transport links?

<div class="discussion">
* London
** +1 If we hold the event in central London more people are likly to come along [[User:GlennJones|Glenn Jones]]
** +1 Possibly more venue choice, also. [[User:Phae|Phae]]
* Brighton
</div>

<div class="discussion">
* The Bricklayers Arms — 31 Gresse Street, London
* The Yorkshire Grey — 2 Theobald's Road, London
* Pitcher and Piano — 42 Kingsway, London
* Brew Wharf Yard — 2 Stoney Street, London
* The Princess — 76 Paul Street, London
</div>

== what date ==
Which is the best date fro the event?

<div class="discussion">
* Monday 11 April
* Tuesday 12 April
** +1 Held on a Tuesday night before [[User:GlennJones|Glenn Jones]]
* Wednesday 13 April
* Thursdays 14 April
** -1 Pub Standards is on this night [[User:GlennJones|Glenn Jones]]
* Friday 15 April
* Saturday 16 April
</div>

== attendees ==
Add yourself alphabetically sorted by family name if you plan on attending or attended.

* [[User:GlennJones|Glenn Jones (fn)]]
* ...

== photographs ==

* ...

== notes ==
Topics discussed, comments, and Q&A.

* …

== articles and blog posts ==
Articles and blog posts following up on the meetup. Add a link to your post in the list below. Newest first.

* ...

== related pages==
{{events-related-pages}}

events

2011-02-25T11:46:34Z

Phae: /* upcoming */ stub note for vEvent with Glenn Jones

<entry-title>Microformats events</entry-title>
Please add microformats related events (including events which have sessions on microformats) below.

Use the [[events-template|events template]] to create events pages, and list URLs, details, attendees, recommended tags, link to photos afterwards, etc. Add links to slides and other media to the [[presentations]], [[podcasts]] pages respectively.

Encourage the use of microformats on event sites' pages themselves, e.g. [[hCalendar]] and [[hCard]] for the schedule, sessions, speakers, and venues.

== Add events to your calendar ==
Subscribe to current and future microformats events:

iCal, Evolution:
* click to subscribe: http://h2vx.com/ics/sub/microformats.org/wiki/events
* set it to update (i.e. "<nowiki>[x]</nowiki> Refresh" or "Auto-refresh: Every day") and new events will appear automatically.

Zimbra:
* Choose the "'''Calendar'''" tab
* in the far left column, click the new calendar icon (little mini green calendar with a plus sign, top right corner of the column header), a "'''Create New Calendar'''" dialog box should appear
* enter "microformats events" into the '''Name''' field
* check the 2nd checkbox: '''<nowiki>[x]</nowiki> Synchronize appointments from remote calendar'''
* copy this URL: '''<code><nowiki>http://h2vx.com/ics/microformats.org/wiki/events</nowiki></code>'''
* paste it into the '''URL''' field and click '''<nowiki>[ OK ]</nowiki>'''

You may also download [http://h2vx.com/ics/microformats.org/wiki/events events on this page as an iCalendar file].

__TOC__

== regular ==
* regular [[meetup]] - community meetups. details inside.

== upcoming ==


*2011-03-09: [[events/2011-03-09-microformats-dinner|Microformats Dinner]] with special guest Frances Berriman at TBD, San Francisco, CA. http://microformats.org/wiki/events/2011-03-09-microformats-dinner

*2011-03-10..<abbr style="border:0" class="dtend" title="2011-03-15">15</abbr>: [[events/2011-03-sxsw|SXSW 2011]] at Austin, Texas. Lots of microformats related events happening at SXSW 2011 including a panel: "The Future of Microformats". http://microformats.org/events/2011-03-sxsw
**2011-03-13: SXSWi 2011 Activity Streams Meet-up at SXSW Interactive, Austin, Texas. http://plancast.com/p/38g9
**2011-03-14: [[events/2011-03-14-future-of-microformats|The Future of Microformats]] at SXSW Interactive, Austin, Texas. http://microformats.org/wiki/events/2011-03-14-future-of-microformats

*2011-04: Microformat vEvent with focused discussion on input format with Glenn Jones at TBD, Brighton or London. 

== recent ==


=== February 2011 ===
*2011-02-22: [[events/2011-02-22-microformats-dinner|Microformats Dinner & Drinks]] with special guest Edward O'Connor at Naan N' Chutney, 525 Haight st., San Francisco, CA. http://microformats.org/wiki/events/2011-02-22-microformats-dinner

*2011-02-10: ActivityStrea.ms Spec Meetup at Socialcast at 2 South Park St., San Francisco, CA 94107. http://plancast.com/p/3kng

*2011-02-01: [[events/2011-02-01-microformats-dinner|Microformats Dinner & Drinks]] at 21st Amendment, San Francisco, CA. http://microformats.org/wiki/events/2011-02-01-microformats-dinner

=== October 2010 ===
* Tantek Çelik on HTML5 at Front-Trends in Warsaw discussed microformats and [[HTML5]]

=== September 2010 ===
* Jeremy Keith workshop on HTML5+microformats at dConstruct 2010

=== August 2010 ===
*2010-08-19 at 19:00: [[events/2010-08-19-weekly-dinner-sf|Microformats + Activity Streams Meetup San Francisco]] at Westfield Food Court, San Francisco, California. http://microformats.org/wiki/events/2010-08-19-dinner-sf

=== July 2010 ===
* ... need to add talks by Tantek Çelik at CascadeSF on HTML5+CSS3+microformats, and at OpenWebCamp on HTML5+microformats+S5
* ... Federated Social Web summit - included discussions of hCard and identity

=== June 2010 ===
* ... need to add Voices That Matter talks on microformats by Emily Lewis and HTML5+microformats by Tantek Çelik

=== May 2010 ===
*2010-05-04 at 19:00: [[events/2010-05-04-weekly-dinner-sf|Microformats Dinner San Francisco]] at 21st Amendment, San Francisco, California. http://microformats.org/wiki/events/2010-05-04-weekly-dinner-sf

*2010-05-02: [[events/2010-05-02-microformats-2-0|microformats 2.0 discussion]] facilitated by [[User:Tantek|Tantek Çelik]] at Cambridge, MA. http://microformats.org/wiki/events/2010-05-02-microformats-2-0

=== April 2010 ===
*2010-04-23: [[events/2010-04-23-html5-workshop|HTML5 for Web Designers]] by Jeremy Keith at Brighton. http://workshopsfortheweb.com/html5/

=== March 2010 ===
*2010-03-12 to 2010-03-16: [[events/2010-03-12-sxsw|<abbr title="South by Southwest Interactive Festival">SXSWi</abbr>]] at Austin Convention Center, Austin.
** 2010-03-14 at 1:10pm: [[events/2010-03-14-sxsw-microformats-government|Microformats and Government]] at Room 9ABC, Austin Convention Center, Austin, <abbr title="Texas" class="region">TX</abbr>. http://microformats.org/wiki/events/2010-03-14-sxsw-microformats-government
** 2010-03-15 at 9:30am: [[events/2010-03-15-sxsw-open-science|Open Science: Create, Collaborate, Communicate]] at Room 10AB, Austin Convention Center, Austin, <abbr title="Texas" class="region">TX</abbr>. http://microformats.org/wiki/events/2010-03-15-sxsw-open-science

=== February 2010 ===
*2010-02-17 at 19:00: [[events/2010-02-17-webkit-html5-benkyokai|3rd Webkit/HTML5 Benkyokai (第3回Webkit/HTML5勉強会)]] at グリー株式会社（東京都港区六本木4-1-4 黒崎ビル5F (Tokyo, Japan)）. [http://oli.jp/ Oli Studholme] presenting on Microformats and Microdata (in Japanese). http://atnd.org/events/3058

*2010-02-02 at 18:30: [[events/2010-02-02-weekly-dinner-mv|Microformats Weekly Meetup Mountain View]] at Gyros House, Mountain View, California. http://microformats.org/wiki/events/2010-02-02-weekly-dinner-mv

=== January 2010 ===
*2010-01-19 at 19:00: [[events/2010-01-19-weekly-dinner-sf|Microformats Weekly Meetup San Francisco]] at Westfield Food Court, San Francisco, California. http://microformats.org/wiki/events/2010-01-19-weekly-dinner-sf

*2010-01-12 at 18:30: [[events/2010-01-12-weekly-dinner-sf|Microformats Dinner San Francisco]] at Pancho Villa Taqueria, San Francisco, California. http://microformats.org/wiki/events/2010-01-12-weekly-dinner-sf

*2010-01-05 at 18:30: [[events/2010-01-05-weekly-dinner-sf|Microformats Dinner San Francisco]] at 21st Amendment, San Francisco, California. http://microformats.org/wiki/events/2010-01-05-weekly-dinner-sf

== Previous events ==
Previous years' events can be found at the following:
* [[events-2009]]
* [[events-2008]]
* [[events-2007]]
* [[events-2006]]

== Other languages ==
* [[current_events-fr|événements en cours]] (fr)

== Quicktime Broadcaster Notes ==
See [[quicktime]]

==Related pages==
{{events-related-pages}}

events

2011-02-25T11:43:31Z

Phae: move past event

<entry-title>Microformats events</entry-title>
Please add microformats related events (including events which have sessions on microformats) below.

Use the [[events-template|events template]] to create events pages, and list URLs, details, attendees, recommended tags, link to photos afterwards, etc. Add links to slides and other media to the [[presentations]], [[podcasts]] pages respectively.

Encourage the use of microformats on event sites' pages themselves, e.g. [[hCalendar]] and [[hCard]] for the schedule, sessions, speakers, and venues.

== Add events to your calendar ==
Subscribe to current and future microformats events:

iCal, Evolution:
* click to subscribe: http://h2vx.com/ics/sub/microformats.org/wiki/events
* set it to update (i.e. "<nowiki>[x]</nowiki> Refresh" or "Auto-refresh: Every day") and new events will appear automatically.

Zimbra:
* Choose the "'''Calendar'''" tab
* in the far left column, click the new calendar icon (little mini green calendar with a plus sign, top right corner of the column header), a "'''Create New Calendar'''" dialog box should appear
* enter "microformats events" into the '''Name''' field
* check the 2nd checkbox: '''<nowiki>[x]</nowiki> Synchronize appointments from remote calendar'''
* copy this URL: '''<code><nowiki>http://h2vx.com/ics/microformats.org/wiki/events</nowiki></code>'''
* paste it into the '''URL''' field and click '''<nowiki>[ OK ]</nowiki>'''

You may also download [http://h2vx.com/ics/microformats.org/wiki/events events on this page as an iCalendar file].

__TOC__

== regular ==
* regular [[meetup]] - community meetups. details inside.

== upcoming ==


*2011-03-09: [[events/2011-03-09-microformats-dinner|Microformats Dinner]] with special guest Frances Berriman at TBD, San Francisco, CA. http://microformats.org/wiki/events/2011-03-09-microformats-dinner

*2011-03-10..<abbr style="border:0" class="dtend" title="2011-03-15">15</abbr>: [[events/2011-03-sxsw|SXSW 2011]] at Austin, Texas. Lots of microformats related events happening at SXSW 2011 including a panel: "The Future of Microformats". http://microformats.org/events/2011-03-sxsw
**2011-03-13: SXSWi 2011 Activity Streams Meet-up at SXSW Interactive, Austin, Texas. http://plancast.com/p/38g9
**2011-03-14: [[events/2011-03-14-future-of-microformats|The Future of Microformats]] at SXSW Interactive, Austin, Texas. http://microformats.org/wiki/events/2011-03-14-future-of-microformats

== recent ==


=== February 2011 ===
*2011-02-22: [[events/2011-02-22-microformats-dinner|Microformats Dinner & Drinks]] with special guest Edward O'Connor at Naan N' Chutney, 525 Haight st., San Francisco, CA. http://microformats.org/wiki/events/2011-02-22-microformats-dinner

*2011-02-10: ActivityStrea.ms Spec Meetup at Socialcast at 2 South Park St., San Francisco, CA 94107. http://plancast.com/p/3kng

*2011-02-01: [[events/2011-02-01-microformats-dinner|Microformats Dinner & Drinks]] at 21st Amendment, San Francisco, CA. http://microformats.org/wiki/events/2011-02-01-microformats-dinner

=== October 2010 ===
* Tantek Çelik on HTML5 at Front-Trends in Warsaw discussed microformats and [[HTML5]]

=== September 2010 ===
* Jeremy Keith workshop on HTML5+microformats at dConstruct 2010

=== August 2010 ===
*2010-08-19 at 19:00: [[events/2010-08-19-weekly-dinner-sf|Microformats + Activity Streams Meetup San Francisco]] at Westfield Food Court, San Francisco, California. http://microformats.org/wiki/events/2010-08-19-dinner-sf

=== July 2010 ===
* ... need to add talks by Tantek Çelik at CascadeSF on HTML5+CSS3+microformats, and at OpenWebCamp on HTML5+microformats+S5
* ... Federated Social Web summit - included discussions of hCard and identity

=== June 2010 ===
* ... need to add Voices That Matter talks on microformats by Emily Lewis and HTML5+microformats by Tantek Çelik

=== May 2010 ===
*2010-05-04 at 19:00: [[events/2010-05-04-weekly-dinner-sf|Microformats Dinner San Francisco]] at 21st Amendment, San Francisco, California. http://microformats.org/wiki/events/2010-05-04-weekly-dinner-sf

*2010-05-02: [[events/2010-05-02-microformats-2-0|microformats 2.0 discussion]] facilitated by [[User:Tantek|Tantek Çelik]] at Cambridge, MA. http://microformats.org/wiki/events/2010-05-02-microformats-2-0

=== April 2010 ===
*2010-04-23: [[events/2010-04-23-html5-workshop|HTML5 for Web Designers]] by Jeremy Keith at Brighton. http://workshopsfortheweb.com/html5/

=== March 2010 ===
*2010-03-12 to 2010-03-16: [[events/2010-03-12-sxsw|<abbr title="South by Southwest Interactive Festival">SXSWi</abbr>]] at Austin Convention Center, Austin.
** 2010-03-14 at 1:10pm: [[events/2010-03-14-sxsw-microformats-government|Microformats and Government]] at Room 9ABC, Austin Convention Center, Austin, <abbr title="Texas" class="region">TX</abbr>. http://microformats.org/wiki/events/2010-03-14-sxsw-microformats-government
** 2010-03-15 at 9:30am: [[events/2010-03-15-sxsw-open-science|Open Science: Create, Collaborate, Communicate]] at Room 10AB, Austin Convention Center, Austin, <abbr title="Texas" class="region">TX</abbr>. http://microformats.org/wiki/events/2010-03-15-sxsw-open-science

=== February 2010 ===
*2010-02-17 at 19:00: [[events/2010-02-17-webkit-html5-benkyokai|3rd Webkit/HTML5 Benkyokai (第3回Webkit/HTML5勉強会)]] at グリー株式会社（東京都港区六本木4-1-4 黒崎ビル5F (Tokyo, Japan)）. [http://oli.jp/ Oli Studholme] presenting on Microformats and Microdata (in Japanese). http://atnd.org/events/3058

*2010-02-02 at 18:30: [[events/2010-02-02-weekly-dinner-mv|Microformats Weekly Meetup Mountain View]] at Gyros House, Mountain View, California. http://microformats.org/wiki/events/2010-02-02-weekly-dinner-mv

=== January 2010 ===
*2010-01-19 at 19:00: [[events/2010-01-19-weekly-dinner-sf|Microformats Weekly Meetup San Francisco]] at Westfield Food Court, San Francisco, California. http://microformats.org/wiki/events/2010-01-19-weekly-dinner-sf

*2010-01-12 at 18:30: [[events/2010-01-12-weekly-dinner-sf|Microformats Dinner San Francisco]] at Pancho Villa Taqueria, San Francisco, California. http://microformats.org/wiki/events/2010-01-12-weekly-dinner-sf

*2010-01-05 at 18:30: [[events/2010-01-05-weekly-dinner-sf|Microformats Dinner San Francisco]] at 21st Amendment, San Francisco, California. http://microformats.org/wiki/events/2010-01-05-weekly-dinner-sf

== Previous events ==
Previous years' events can be found at the following:
* [[events-2009]]
* [[events-2008]]
* [[events-2007]]
* [[events-2006]]

== Other languages ==
* [[current_events-fr|événements en cours]] (fr)

== Quicktime Broadcaster Notes ==
See [[quicktime]]

==Related pages==
{{events-related-pages}}

hrecipe

2011-02-24T23:14:12Z

Phae: /* Authors */ removing incorrect association

<entry-title>hRecipe 0.22</entry-title>
{{Template:DraftSpecification}}
{{TOC-right}}
http://www.livingathome.de/test/recipe/hRecipe.png

[[recipe|hRecipe]] is a simple, open, distributed format, suitable for embedding information about recipes for cooking in (X)HTML, Atom, RSS, and arbitrary XML. hRecipe is one of several [[microformats]] open standards. This page and Microformat is in the public domain.

== hRecipe Microformat Draft Specification ==

=== Editor ===
* [[User:ThomasLoertsch | Thomas Lörtsch]]

=== Authors ===
* [[User:Phae|Frances Berriman]]
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]

=== Contributors===
[[User:AndyMabbett|Andy Mabbett]], [[User:Phae|Frances Berriman]], [[User:IamCam|Cameron Perry]], [[User:JohnLeMasney|John LeMasney]], [[User:Tantek|Tantek Çelik]], [[User:SudarshanP|SudarshanP]], [[User:CiaranMc|Ciaran McNulty]], [[User:LeeJordan|Lee Jordan]], [[User:RobertBachmann|Robert Bachmann]], [[User:JeffMcNeill|jeffmcneill]], [[User:ManuSporny|Manu Sporny]], [[User:RyanKing|Ryan King]], HollyMarieKoltz, Straup, [[User:ChristopheDucamp|Christophe Ducamp]], Mercman, [[User:Yde|Yde]], [[User:AmeerDawood|Ameer Dawood]], Scottk, [[User:Lee_Jordan|Lee Jordan]], MonroAlmon, EstevaoSamuel, [[User:Brian|Brian Suda]], SteveL, JohnLeMasney,

Microformats [[#Copyright]] and [[#Patents]] statements apply.

== Introduction ==

The hRecipe microformat is designed for the mark-up of instructions for creating meals, drinks or food-based items.

It is difficult for a browser to extract semantic information about a recipe described on a web page. Metadata such as author and name and details such as ingredients, method, preparation time etc provide relevant information about the recipe.

Having such information marked up can provide a number of benefits to the viewer. If a web browser understands that a particular web page contains a recipe with specific characteristics, it can produce richer interactions. For example, specific searches may be performed for ingredients or authors via general search services such as Google and Wikipedia. Additionally, classification by crawlers can become more accurate. If there are 20 recipes found on a page, and they all contain a certain ingredient, it can be assumed that the page is not only about cooking, but also about that particular ingredient.

In order to enable and encourage the sharing, distribution, syndication, and aggregation of recipes, the authors propose the hRecipe microformat, an open standard for distributed recipe metadata. The authors have researched both numerous [[recipe-examples]] in the wild and earlier attempts at [[recipe-formats]], and have designed hRecipe around a simple minimal schema for recipe content. Feedback is encouraged on the [[recipe-feedback|hRecipe feedback]] page.

=== Inspiration and Acknowledgments ===

Many thanks to the various individuals that did research and proposed ideas and discussion related to the hRecipe-format and recipes in general.

=== Scope ===

hRecipe is a format to annotate descriptions and lists of ingredients for the preparation of food and meals. Recipes consistently share several common properties. hRecipe has been based on this minimal common subset.

=== Out of scope ===

Recipes that are not for stuff that's meant to be eaten by humans are out of scope.

== Format ==

{{rfc-2119-intro}}

=== In General ===
The hRecipe format is based on a set of properties common to numerous recipe sites and formats in use today on the web. Where possible property names have been chosen based on those defined by related microformat standards. 
Some properties are marked ''experimental'' since they exceed the minimum set of properties needed to describe a recipe but still are very commonly used on the web. It's not sure if they are relevant enough for inclusion in the format. Implementation and general uptake of these properties will be observed and inform further decisions. So their use is not at all discouraged - but use them with care and be prepared for their eventual removal from the final spec.

=== Schema ===
The hRecipe schema consists of the following properties:

* '''hrecipe'''
** '''fn'''. required. text. the name of the recipe.
** '''ingredient'''. required. 1 or more. text with optional valid (x)HTML markup.
*** '''''value''''' and '''''type'''''. optional. [experimental]
** '''''yield'''''. optional. text.
** '''''instructions'''''. optional. text with optional valid (x)HTML markup.
** '''''duration'''''. optional. 1 or more. text.
** ''photo''. optional. 1 or more. using any element containing a URL, such as IMG. [experimental]
** ''summary''. optional. text. [experimental]
** ''author''. optional. 1 or more. [experimental]
** ''published''. optional. [experimental]
** ''nutrition''. optional. 1 or more. [experimental]
*** ''value'' and ''type''. optional. [experimental]
** ''tag''. optional. 1 or more. [experimental]

=== Property details ===

Property names <code>fn</code>, <code>photo</code>, <code>author</code>, <code>value</code> and <code>type</code> are reused from [[hCard]]. Property name <code>duration</code> is reused from [[hAudio]]. Property name <code>summary</code> is reused from [[hCalendar]]. Property name <code>published</code> is reused from [[hAtom]]. Property name <code>tag</code> is reused from [[rel-tag]].

The fields of the hRecipe schema represent the following:

==== hRecipe ====

A hRecipe is used to identify and describe values and metadata typically associated with a recipe.

* A hRecipe property is identified by the name <code>hrecipe</code>

==== fn ====

The title of a single recipe. A short textual description used to identify the work among interested parties. This can be the name of a meal or a short description regarding it's ingredients.

* The property is identified by the name <code>fn</code>.
* A Recipe {{must}} include a <code>fn</code>.
* The property {{must}} follow the conventions outlined in [[hCard]] e.g. by using only plain text.

==== ingredient ====

Describes one or more ingredients used in the recipe.

* The property is identified by the name <code>ingredient</code>.
* A Recipe {{must}} include one or more <code>ingredient</code>s.
* The property {{may}} include valid HTML markup (e.g. a list of ingredients).
* The property {{may}} include the properties <code>value</code> and <code>type</code> following the conventions outlined in [[hCard]], e.g. <source lang=html4strict>125ml milk</source>In this case each ingredient should be marked up with it's own <code>ingredient</code> property. These subproperties are considered ''experimental'' and may be removed from the final specification or replaced by 'num' and 'unit' from [[measure]].

==== yield ====

Specifies the quantity produced by the recipe, like how many persons it satisfyies or how many pieces can be made of it.

* The property is identified by the name <code>yield</code>.
* A Recipe {{may}} include a <code>yield</code>.

==== instructions ====

The method of the recipe.

* The property is identified by the name <code>instructions</code>.
* A Recipe {{may}} include a <code>instructions</code> property.
* The property {{may}} include valid HTML markup e.g. paragraphs or a list of steps.

==== duration ====

The time it takes to prepare the meal described by the recipe. Multiple duration properties can be used to denote e.g. time for preparing a dough, time needed for the dough to raise, time to bake the dough, time for decorating the cake etc.

* The property is identified by the name <code>duration</code>.
* A Recipe {{may}} include one or more <code>duration</code> properties.
* The property {{may}} encode the timespan as outlined in the [[value-class-pattern|value-class-pattern]]. A duration of 1 hour 30 minutes would translate to "PT1H30M" in ISO 8601 format and can be encoded as follows:<source lang=html4strict> 90 min</source>

==== photo ====

Accompanying image.

* The property is identified by the name <code>photo</code>.
* A Recipe {{may}} include one or more <code>photo</code> properties.
* The property {{should}} use an <img> element. It {{may}} use any other element that contains a URL, such as <a> or <object>, but it is not recommended. See [[hRecipe#Semantic_XHTML_Design_Principles | notes]] below.
* The property is considered ''experimental'' and may be removed from the final specification.

==== summary ====

The summary provides a short introduction to or an accompanying statement about the recipe.

* The property is identified by the name <code>summary</code>.
* A Recipe {{may}} include a <code>summary</code>.
* The property {{must}} follow the conventions outlined in [[hCalendar]]. Plain text fulfills these requirements.
* The property is considered ''experimental'' and may be removed from the final specification.

==== author ====

An author is the person who wrote the recipe.

* The property is identified by the name <code>author</code>.
* A Recipe {{may}} include one or more <code>author</code> properties.
* The contents of the element {{may}} be a plain text string in which case it defaults to a "vcard fn". Anything more elaborate {{must}} follow the conventions outlined in [[hCard]].
* The element is considered ''experimental'' and may be removed from the final specification.

==== published ====

The date the recipe was published.

* The property is identified by the name <code>published</code>.
* A Recipe {{may}} include a <code>published</code> date.
* The property {{may}} be encoded using the [[value-class-pattern|value-class-pattern]], e.g.:<source lang=html4strict>Published 14. Oct 2008</source>
* The property is considered ''experimental'' and may be removed from the final specification.

==== nutrition ====

Nutritional information like calories, fat, dietary fiber etc.

* The property is identified by name <code>nutrition</code>.
* A Recipe {{may}} include one or more <code>nutrition</code> properties.
* The property {{may}} include the properties <code>value</code> and <code>type</code> following the conventions outlined in [[hCard]]. In this case each nutritional information item should be marked up with it's own <code>nutrition</code> property. These subelement are considered ''experimental'' and may be replaced by 'num' and 'unit' from [[measure]].
* The property <code>nutrition</code> itself is also considered ''experimental'' and may be removed from the final specification.

==== tag ====

A keyword indicating a subject or an important aspect of the recipe like it's main ingredient, type of meal etc.

* The property is identified by the name <code>tag</code>.
* A Recipe {{may}} include one or more <code>tag</code>'s.
* The property {{must}} follow the conventions outlined in [[rel-tag]].
* The property is considered ''experimental'' and may be removed from the final specification.

=== Version history ===

* Version 0.22 changed the proposed formatting of time and date from the [[datetime-design-pattern|datetime-design-pattern]], which has [[datetime-design-pattern#Accessibility_issues|accessibility issues]], to the [[value-class-pattern|value-class-pattern]]. Also corrected some errors in the example especially with regard to the correct handling of vcard properties.
* Version 0.21 changed the status of ingredient/value and ingredient/type to ''experimental'', mentioning that there still is discussion if they should be replaced by 'num' and 'unit' from [[measure]] (which is still in brainstorming).
* Version 0.2: From [http://microformats.org/wiki/index.php?title=hrecipe&oldid=37357 Version 0.1] some elements have been renamed to strenghten re-use of established elements: '''fn''' for '''hRecipe-title''', '''summary''' for '''hRecipe-summary''', '''duration''' for '''preparation-time''', '''value''' and '''type''' for '''num''' and '''unit'''. Also some elements have been marked '''experimental''' because of concerns of element bloat. See the [[hrecipe-issues]] page for a more thorough discussion. Draft 0.1 was already a result of long lasting efforts. Nonetheless after publishing of it there has been a lively debate about some properties. Since they mostly could be resolved version 0.2 is considered fairly stable now, although of course you never know ;-)

=== Parser Processing Notes ===

* If the "author" property contains only a plain text string it should be regarded as of type "vcard fn".

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles}}

==== More Semantic Equivalents ====

For some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:

* For "photo", use <code><img class="photo" src="..." alt="" /></code>

==== Language ====

* To explicitly convey the natural language that an recipe is written in, use the standard (X)HTML 'lang' or 'xml:lang' attribute on the element with class="hrecipe"
**e.g. <code><nowiki>I like Kartoffelknödel best.</nowiki></code>
*If portions of an hRecipe (e.g. an ingredient name) are in a different language to the rest of the hRecipe, use the 'lang' or 'xml:lang' attribute on those portions.
* hRecipe parsers which need to handle the native language of hRecipe {{must}} process the standard (X)HTML 'lang' or 'xml:lang' attribute as specified.
* hRecipe parsers which need to handle native language {{may}} traverse up the DOM to discover the native language of the page and apply that to the hRecipe if no other language is specified on the hRecipe.

==== Human vs. Machine Readable ====

If an <code><abbr></code> element is used for a property, then its '<code>title</code>' attribute is used for the value of the property, instead of the contents of the element, which can then be used to provide a user-friendly alternate presentation of the value.

If an <code><a></code> element is used for one or more properties, it {{must}} be treated as follows:
# For the 'photo' property and any other property that takes a URL as its value, the <code>href="..."</code> attribute provides the property value.
# For other properties, the element's content is the value of the property.

If an <code><img></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>src="..."</code> attribute as property value.

If an <code><object></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>data="..."</code> attribute as property value.

=== Notes ===

This section is informative.

*Non so far.

== XMDP Profile ==

<source lang=html4strict>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>hrecipe</dt>
<dd>
Used to identify and describe metadata associated with instructions for creating meals, drinks or food-based items.
</dd>
<dt>fn</dt>
<dd>
The title of the recipe.
</dd>
<dt>ingredient</dt>
<dd>
Describes the ingredient(s) used in the recipe.
</dd>
<dt>yield</dt>
<dd>
Specifies the quantity produced by the recipe.
</dd>
<dt>instructions</dt>
<dd>
The method of the recipe.
</dd>
<dt>duration</dt>
<dd>
The time it takes to prepare the meal described by the recipe.
</dd>
<dt>photo</dt>
<dd>
Accompanying image.
</dd>
<dt>summary</dt>
<dd>
The summary provides a short introduction or an accompanying statement about the recipe.
</dd>
<dt>author</dt>
<dd>
The person who authored the recipe..
</dd>
<dt>published</dt>
<dd>
The date that the recipe was made available to the public.
</dd>
<dt>nutrition</dt>
<dd>
Nutritional information like calories, fat, dietary fiber etc.
</dd>
<dt>tag</dt>
<dd>
Keyword(s) describing the recipe.
</dd>
</dl>
</dd>
</dl>
</source>

== Examples ==

This section is informative.

Here '''will be''' a few examples of recipes, from real web sites, showing how they could be easily enhanced to use hRecipe. In the meantime the following contrieved example will have to do.

<source lang=html4strict><div class="hrecipe">
<h1 class="fn">Pommes Frites</h1>

Pommes frites originate in outer space. They are served hot. 
This recipe is only an example. Don't try this at home!


Contributed by CJ Tom and the
<a class="url fn" href="http://example.com">Cooky Gang</a>.

Published 14. Oct 2008
<img src="/img/pommes.png" class="photo" width="100" height="100" alt="Pommes Frites"/>
<h2>Ingredients</h2>
<ul>
<li class="ingredient">
500
gramme potatoes, hard cooking.
</li>
<li class="ingredient">
1 spoonful of salt
</li>
<li>
You may want to provide some
Ketchup and Mayonnaise
as well.
</li>
</ul>
<h2>Instructions</h2>
<ul class="instructions">
<li>First wash the potatoes.</li>
<li>Then slice and dice them and put them in boiling fat.</li>
<li>After a few minutes take them out again.</li>
</ul>
<h2>Further details</h2>
Enough for 12 children.
Preparation time is approximately
 90 min

Add half an hour to prepare your homemade Ketchup.
This recipe is <a href="http://www.example.com/tags/difficulty/easy" rel="tag">easy</a> and <a href="http://www.example.com/tags/tastyness/delicious" rel="tag">delicious</a>.


Pommes Frites have more than
1000
Joule
Energy,
while Ketchup and Mayonnaise have
0 vitamins.

</div>
</source>


== Examples in the wild ==

This section is '''informative'''.

Sites and pages that publish hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-examples-in-wild]].

* [http://www.epicurious.com/ Epicurious.com]'s [http://www.epicurious.com/recipesmenus/ recipes] have been marked up with hRecipe as of April 2010. (E.g., [http://www.epicurious.com/recipes/food/views/Chocolate-Almond-and-Banana-Parfaits-357369 Chocolate, Almond, and Banana Parfaits])
* [http://www.williams-sonoma.com/ Williams-Sonoma]'s [http://www.williams-sonoma.com/recipe/ recipes section], e.g. [http://www.williams-sonoma.com/recipe/cherry-almond-bundt-cake.html Cherry Almond Bundt Cake]
* http://foodnetwork.com/ has marked up all their recipes with hRecipe as of 2009-10, e.g. [http://www.foodnetwork.com/recipes/ina-garten/deep-dish-apple-pie-recipe2/index.html Deep-Dish Apple Pie recipe]
* [http://www.plantoeat.com/ Plan to Eat]'s [http://www.plantoeat.com/recipe_book recipe planner] is now in hRecipe format as of April 2010. (E.g., [http://www.plantoeat.com/recipes/4583/1fv1A5vFhjm Pasta With Smashed Peas])
* essen & trinken. As of spring 2009 [http://www.essen-und-trinken.de essen & trinken] publishes all recipes with hRecipe-conformant metadata encoded in RDF. See [[hrecipe-rdf]] for technical details.
* It's Ripe! As of January 2009, [http://itsripe.com/recipes/ http://itsripe.com] supports hRecipe for recipe pages and will soon add support in lists.
*'''Wild Mushroom, Pancetta & Truffle Risotto''' by Toby Inkster
** [http://tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Marked up as hRecipe] using the September 2007 draft format
** [http://srv.buzzword.org.uk/recipebook/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RecipeBook XML] output from Cognition.
** [http://srv.buzzword.org.uk/rdf-xml/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RDF/XML] and [http://srv.buzzword.org.uk/turtle/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Turtle] output from Cognition.
* allrecipes.com e.g. [http://allrecipes.com//Recipe/slow-cooker-chicken-and-dumplings/Detail.aspx Slow cooker chicken and dumplings]
* food.com e.g. [http://www.food.com/recipe/chicken-and-dumplings-72963 Chicken dumplings]
* tablespoon.com e.g. [http://www.tablespoon.com/recipes/old-fashioned-chicken-and-dumplings-recipe/1/ Chicken dumplings]

== Implementations ==
This section is '''informative'''.

Tools for generating and consuming hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-implementations]].

* Cognition. As of September 2008, [http://buzzword.org.uk/cognition/ Cognition] has experimental support for this format. ([http://buzzword.org.uk/cognition/uf-plus.html#hrecipe Details of support].) Recipes may be exported in [[recipe-formats#RecipeBook_XML|RecipeBook XML]] format or RDF.
* WordPress Plugin. There's a [http://wordpress.org/ WordPress ] [http://wordpress.org/extend/plugins/hrecipe/ hRecipe Plugin] available which makes adding hRecipe metadata to recipes very easy, practically effortless. Very nice!
* Google. Launched 24th February, 2011, [http://www.google.com/landing/recipes/ Recipe View] search results from Google are powered by hRecipe marked-up snippets.

== References ==

=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[abbr-design-pattern]]
* [[datetime-design-pattern]]

=== Informative References ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other recipe metadata efforts. See [[recipe-formats]].
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===

Per [[Microformats_Wiki:Copyrights]], hRecipe was placed into the public domain on 2008-11-14 by the authors. There are no usage, distribution, re-printing, or any other restrictions of any kind with regards to the text or content of this specification.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Public Domain Release ===

The authors and editors of this page due hereby relinquish their copyright on the document and release the text of this page into the public domain.

* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

== derivative works ==
* [[hrecipe-rdf|hRecipe in RDF]] - mapping of hRecipe into a RDF vocabulary called "aRecipe"

==related pages==
* [[hrecipe-issues|hRecipe issues]] - issues regarding the hRecipe draft
* [[hrecipe-feedback|hRecipe feedback]] - general feedback regarding hRecipe

Per the microformats [[process]], the [[recipe]] effort developed
* [[recipe-examples]]
* [[recipe-formats]]
* [[recipe-brainstorming]] (see also [[recipe-brainstorming-archive]])
* [[recipe-issues]]
towards the development of this draft.

[[Category:Draft Specifications]]

hrecipe

2011-02-24T23:07:29Z

Phae: /* Implementations */ adding the goog!

<entry-title>hRecipe 0.22</entry-title>
{{Template:DraftSpecification}}
{{TOC-right}}
http://www.livingathome.de/test/recipe/hRecipe.png

[[recipe|hRecipe]] is a simple, open, distributed format, suitable for embedding information about recipes for cooking in (X)HTML, Atom, RSS, and arbitrary XML. hRecipe is one of several [[microformats]] open standards. This page and Microformat is in the public domain.

== hRecipe Microformat Draft Specification ==

=== Editor ===
* [[User:ThomasLoertsch | Thomas Lörtsch]]

=== Authors ===
* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]

=== Contributors===
[[User:AndyMabbett|Andy Mabbett]], [[User:Phae|Frances Berriman]], [[User:IamCam|Cameron Perry]], [[User:JohnLeMasney|John LeMasney]], [[User:Tantek|Tantek Çelik]], [[User:SudarshanP|SudarshanP]], [[User:CiaranMc|Ciaran McNulty]], [[User:LeeJordan|Lee Jordan]], [[User:RobertBachmann|Robert Bachmann]], [[User:JeffMcNeill|jeffmcneill]], [[User:ManuSporny|Manu Sporny]], [[User:RyanKing|Ryan King]], HollyMarieKoltz, Straup, [[User:ChristopheDucamp|Christophe Ducamp]], Mercman, [[User:Yde|Yde]], [[User:AmeerDawood|Ameer Dawood]], Scottk, [[User:Lee_Jordan|Lee Jordan]], MonroAlmon, EstevaoSamuel, [[User:Brian|Brian Suda]], SteveL, JohnLeMasney,

Microformats [[#Copyright]] and [[#Patents]] statements apply.

== Introduction ==

The hRecipe microformat is designed for the mark-up of instructions for creating meals, drinks or food-based items.

It is difficult for a browser to extract semantic information about a recipe described on a web page. Metadata such as author and name and details such as ingredients, method, preparation time etc provide relevant information about the recipe.

Having such information marked up can provide a number of benefits to the viewer. If a web browser understands that a particular web page contains a recipe with specific characteristics, it can produce richer interactions. For example, specific searches may be performed for ingredients or authors via general search services such as Google and Wikipedia. Additionally, classification by crawlers can become more accurate. If there are 20 recipes found on a page, and they all contain a certain ingredient, it can be assumed that the page is not only about cooking, but also about that particular ingredient.

In order to enable and encourage the sharing, distribution, syndication, and aggregation of recipes, the authors propose the hRecipe microformat, an open standard for distributed recipe metadata. The authors have researched both numerous [[recipe-examples]] in the wild and earlier attempts at [[recipe-formats]], and have designed hRecipe around a simple minimal schema for recipe content. Feedback is encouraged on the [[recipe-feedback|hRecipe feedback]] page.

=== Inspiration and Acknowledgments ===

Many thanks to the various individuals that did research and proposed ideas and discussion related to the hRecipe-format and recipes in general.

=== Scope ===

hRecipe is a format to annotate descriptions and lists of ingredients for the preparation of food and meals. Recipes consistently share several common properties. hRecipe has been based on this minimal common subset.

=== Out of scope ===

Recipes that are not for stuff that's meant to be eaten by humans are out of scope.

== Format ==

{{rfc-2119-intro}}

=== In General ===
The hRecipe format is based on a set of properties common to numerous recipe sites and formats in use today on the web. Where possible property names have been chosen based on those defined by related microformat standards. 
Some properties are marked ''experimental'' since they exceed the minimum set of properties needed to describe a recipe but still are very commonly used on the web. It's not sure if they are relevant enough for inclusion in the format. Implementation and general uptake of these properties will be observed and inform further decisions. So their use is not at all discouraged - but use them with care and be prepared for their eventual removal from the final spec.

=== Schema ===
The hRecipe schema consists of the following properties:

* '''hrecipe'''
** '''fn'''. required. text. the name of the recipe.
** '''ingredient'''. required. 1 or more. text with optional valid (x)HTML markup.
*** '''''value''''' and '''''type'''''. optional. [experimental]
** '''''yield'''''. optional. text.
** '''''instructions'''''. optional. text with optional valid (x)HTML markup.
** '''''duration'''''. optional. 1 or more. text.
** ''photo''. optional. 1 or more. using any element containing a URL, such as IMG. [experimental]
** ''summary''. optional. text. [experimental]
** ''author''. optional. 1 or more. [experimental]
** ''published''. optional. [experimental]
** ''nutrition''. optional. 1 or more. [experimental]
*** ''value'' and ''type''. optional. [experimental]
** ''tag''. optional. 1 or more. [experimental]

=== Property details ===

Property names <code>fn</code>, <code>photo</code>, <code>author</code>, <code>value</code> and <code>type</code> are reused from [[hCard]]. Property name <code>duration</code> is reused from [[hAudio]]. Property name <code>summary</code> is reused from [[hCalendar]]. Property name <code>published</code> is reused from [[hAtom]]. Property name <code>tag</code> is reused from [[rel-tag]].

The fields of the hRecipe schema represent the following:

==== hRecipe ====

A hRecipe is used to identify and describe values and metadata typically associated with a recipe.

* A hRecipe property is identified by the name <code>hrecipe</code>

==== fn ====

The title of a single recipe. A short textual description used to identify the work among interested parties. This can be the name of a meal or a short description regarding it's ingredients.

* The property is identified by the name <code>fn</code>.
* A Recipe {{must}} include a <code>fn</code>.
* The property {{must}} follow the conventions outlined in [[hCard]] e.g. by using only plain text.

==== ingredient ====

Describes one or more ingredients used in the recipe.

* The property is identified by the name <code>ingredient</code>.
* A Recipe {{must}} include one or more <code>ingredient</code>s.
* The property {{may}} include valid HTML markup (e.g. a list of ingredients).
* The property {{may}} include the properties <code>value</code> and <code>type</code> following the conventions outlined in [[hCard]], e.g. <source lang=html4strict>125ml milk</source>In this case each ingredient should be marked up with it's own <code>ingredient</code> property. These subproperties are considered ''experimental'' and may be removed from the final specification or replaced by 'num' and 'unit' from [[measure]].

==== yield ====

Specifies the quantity produced by the recipe, like how many persons it satisfyies or how many pieces can be made of it.

* The property is identified by the name <code>yield</code>.
* A Recipe {{may}} include a <code>yield</code>.

==== instructions ====

The method of the recipe.

* The property is identified by the name <code>instructions</code>.
* A Recipe {{may}} include a <code>instructions</code> property.
* The property {{may}} include valid HTML markup e.g. paragraphs or a list of steps.

==== duration ====

The time it takes to prepare the meal described by the recipe. Multiple duration properties can be used to denote e.g. time for preparing a dough, time needed for the dough to raise, time to bake the dough, time for decorating the cake etc.

* The property is identified by the name <code>duration</code>.
* A Recipe {{may}} include one or more <code>duration</code> properties.
* The property {{may}} encode the timespan as outlined in the [[value-class-pattern|value-class-pattern]]. A duration of 1 hour 30 minutes would translate to "PT1H30M" in ISO 8601 format and can be encoded as follows:<source lang=html4strict> 90 min</source>

==== photo ====

Accompanying image.

* The property is identified by the name <code>photo</code>.
* A Recipe {{may}} include one or more <code>photo</code> properties.
* The property {{should}} use an <img> element. It {{may}} use any other element that contains a URL, such as <a> or <object>, but it is not recommended. See [[hRecipe#Semantic_XHTML_Design_Principles | notes]] below.
* The property is considered ''experimental'' and may be removed from the final specification.

==== summary ====

The summary provides a short introduction to or an accompanying statement about the recipe.

* The property is identified by the name <code>summary</code>.
* A Recipe {{may}} include a <code>summary</code>.
* The property {{must}} follow the conventions outlined in [[hCalendar]]. Plain text fulfills these requirements.
* The property is considered ''experimental'' and may be removed from the final specification.

==== author ====

An author is the person who wrote the recipe.

* The property is identified by the name <code>author</code>.
* A Recipe {{may}} include one or more <code>author</code> properties.
* The contents of the element {{may}} be a plain text string in which case it defaults to a "vcard fn". Anything more elaborate {{must}} follow the conventions outlined in [[hCard]].
* The element is considered ''experimental'' and may be removed from the final specification.

==== published ====

The date the recipe was published.

* The property is identified by the name <code>published</code>.
* A Recipe {{may}} include a <code>published</code> date.
* The property {{may}} be encoded using the [[value-class-pattern|value-class-pattern]], e.g.:<source lang=html4strict>Published 14. Oct 2008</source>
* The property is considered ''experimental'' and may be removed from the final specification.

==== nutrition ====

Nutritional information like calories, fat, dietary fiber etc.

* The property is identified by name <code>nutrition</code>.
* A Recipe {{may}} include one or more <code>nutrition</code> properties.
* The property {{may}} include the properties <code>value</code> and <code>type</code> following the conventions outlined in [[hCard]]. In this case each nutritional information item should be marked up with it's own <code>nutrition</code> property. These subelement are considered ''experimental'' and may be replaced by 'num' and 'unit' from [[measure]].
* The property <code>nutrition</code> itself is also considered ''experimental'' and may be removed from the final specification.

==== tag ====

A keyword indicating a subject or an important aspect of the recipe like it's main ingredient, type of meal etc.

* The property is identified by the name <code>tag</code>.
* A Recipe {{may}} include one or more <code>tag</code>'s.
* The property {{must}} follow the conventions outlined in [[rel-tag]].
* The property is considered ''experimental'' and may be removed from the final specification.

=== Version history ===

* Version 0.22 changed the proposed formatting of time and date from the [[datetime-design-pattern|datetime-design-pattern]], which has [[datetime-design-pattern#Accessibility_issues|accessibility issues]], to the [[value-class-pattern|value-class-pattern]]. Also corrected some errors in the example especially with regard to the correct handling of vcard properties.
* Version 0.21 changed the status of ingredient/value and ingredient/type to ''experimental'', mentioning that there still is discussion if they should be replaced by 'num' and 'unit' from [[measure]] (which is still in brainstorming).
* Version 0.2: From [http://microformats.org/wiki/index.php?title=hrecipe&oldid=37357 Version 0.1] some elements have been renamed to strenghten re-use of established elements: '''fn''' for '''hRecipe-title''', '''summary''' for '''hRecipe-summary''', '''duration''' for '''preparation-time''', '''value''' and '''type''' for '''num''' and '''unit'''. Also some elements have been marked '''experimental''' because of concerns of element bloat. See the [[hrecipe-issues]] page for a more thorough discussion. Draft 0.1 was already a result of long lasting efforts. Nonetheless after publishing of it there has been a lively debate about some properties. Since they mostly could be resolved version 0.2 is considered fairly stable now, although of course you never know ;-)

=== Parser Processing Notes ===

* If the "author" property contains only a plain text string it should be regarded as of type "vcard fn".

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles}}

==== More Semantic Equivalents ====

For some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:

* For "photo", use <code><img class="photo" src="..." alt="" /></code>

==== Language ====

* To explicitly convey the natural language that an recipe is written in, use the standard (X)HTML 'lang' or 'xml:lang' attribute on the element with class="hrecipe"
**e.g. <code><nowiki>I like Kartoffelknödel best.</nowiki></code>
*If portions of an hRecipe (e.g. an ingredient name) are in a different language to the rest of the hRecipe, use the 'lang' or 'xml:lang' attribute on those portions.
* hRecipe parsers which need to handle the native language of hRecipe {{must}} process the standard (X)HTML 'lang' or 'xml:lang' attribute as specified.
* hRecipe parsers which need to handle native language {{may}} traverse up the DOM to discover the native language of the page and apply that to the hRecipe if no other language is specified on the hRecipe.

==== Human vs. Machine Readable ====

If an <code><abbr></code> element is used for a property, then its '<code>title</code>' attribute is used for the value of the property, instead of the contents of the element, which can then be used to provide a user-friendly alternate presentation of the value.

If an <code><a></code> element is used for one or more properties, it {{must}} be treated as follows:
# For the 'photo' property and any other property that takes a URL as its value, the <code>href="..."</code> attribute provides the property value.
# For other properties, the element's content is the value of the property.

If an <code><img></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>src="..."</code> attribute as property value.

If an <code><object></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>data="..."</code> attribute as property value.

=== Notes ===

This section is informative.

*Non so far.

== XMDP Profile ==

<source lang=html4strict>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>hrecipe</dt>
<dd>
Used to identify and describe metadata associated with instructions for creating meals, drinks or food-based items.
</dd>
<dt>fn</dt>
<dd>
The title of the recipe.
</dd>
<dt>ingredient</dt>
<dd>
Describes the ingredient(s) used in the recipe.
</dd>
<dt>yield</dt>
<dd>
Specifies the quantity produced by the recipe.
</dd>
<dt>instructions</dt>
<dd>
The method of the recipe.
</dd>
<dt>duration</dt>
<dd>
The time it takes to prepare the meal described by the recipe.
</dd>
<dt>photo</dt>
<dd>
Accompanying image.
</dd>
<dt>summary</dt>
<dd>
The summary provides a short introduction or an accompanying statement about the recipe.
</dd>
<dt>author</dt>
<dd>
The person who authored the recipe..
</dd>
<dt>published</dt>
<dd>
The date that the recipe was made available to the public.
</dd>
<dt>nutrition</dt>
<dd>
Nutritional information like calories, fat, dietary fiber etc.
</dd>
<dt>tag</dt>
<dd>
Keyword(s) describing the recipe.
</dd>
</dl>
</dd>
</dl>
</source>

== Examples ==

This section is informative.

Here '''will be''' a few examples of recipes, from real web sites, showing how they could be easily enhanced to use hRecipe. In the meantime the following contrieved example will have to do.

<source lang=html4strict><div class="hrecipe">
<h1 class="fn">Pommes Frites</h1>

Pommes frites originate in outer space. They are served hot. 
This recipe is only an example. Don't try this at home!


Contributed by CJ Tom and the
<a class="url fn" href="http://example.com">Cooky Gang</a>.

Published 14. Oct 2008
<img src="/img/pommes.png" class="photo" width="100" height="100" alt="Pommes Frites"/>
<h2>Ingredients</h2>
<ul>
<li class="ingredient">
500
gramme potatoes, hard cooking.
</li>
<li class="ingredient">
1 spoonful of salt
</li>
<li>
You may want to provide some
Ketchup and Mayonnaise
as well.
</li>
</ul>
<h2>Instructions</h2>
<ul class="instructions">
<li>First wash the potatoes.</li>
<li>Then slice and dice them and put them in boiling fat.</li>
<li>After a few minutes take them out again.</li>
</ul>
<h2>Further details</h2>
Enough for 12 children.
Preparation time is approximately
 90 min

Add half an hour to prepare your homemade Ketchup.
This recipe is <a href="http://www.example.com/tags/difficulty/easy" rel="tag">easy</a> and <a href="http://www.example.com/tags/tastyness/delicious" rel="tag">delicious</a>.


Pommes Frites have more than
1000
Joule
Energy,
while Ketchup and Mayonnaise have
0 vitamins.

</div>
</source>


== Examples in the wild ==

This section is '''informative'''.

Sites and pages that publish hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-examples-in-wild]].

* [http://www.epicurious.com/ Epicurious.com]'s [http://www.epicurious.com/recipesmenus/ recipes] have been marked up with hRecipe as of April 2010. (E.g., [http://www.epicurious.com/recipes/food/views/Chocolate-Almond-and-Banana-Parfaits-357369 Chocolate, Almond, and Banana Parfaits])
* [http://www.williams-sonoma.com/ Williams-Sonoma]'s [http://www.williams-sonoma.com/recipe/ recipes section], e.g. [http://www.williams-sonoma.com/recipe/cherry-almond-bundt-cake.html Cherry Almond Bundt Cake]
* http://foodnetwork.com/ has marked up all their recipes with hRecipe as of 2009-10, e.g. [http://www.foodnetwork.com/recipes/ina-garten/deep-dish-apple-pie-recipe2/index.html Deep-Dish Apple Pie recipe]
* [http://www.plantoeat.com/ Plan to Eat]'s [http://www.plantoeat.com/recipe_book recipe planner] is now in hRecipe format as of April 2010. (E.g., [http://www.plantoeat.com/recipes/4583/1fv1A5vFhjm Pasta With Smashed Peas])
* essen & trinken. As of spring 2009 [http://www.essen-und-trinken.de essen & trinken] publishes all recipes with hRecipe-conformant metadata encoded in RDF. See [[hrecipe-rdf]] for technical details.
* It's Ripe! As of January 2009, [http://itsripe.com/recipes/ http://itsripe.com] supports hRecipe for recipe pages and will soon add support in lists.
*'''Wild Mushroom, Pancetta & Truffle Risotto''' by Toby Inkster
** [http://tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Marked up as hRecipe] using the September 2007 draft format
** [http://srv.buzzword.org.uk/recipebook/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RecipeBook XML] output from Cognition.
** [http://srv.buzzword.org.uk/rdf-xml/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RDF/XML] and [http://srv.buzzword.org.uk/turtle/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Turtle] output from Cognition.
* allrecipes.com e.g. [http://allrecipes.com//Recipe/slow-cooker-chicken-and-dumplings/Detail.aspx Slow cooker chicken and dumplings]
* food.com e.g. [http://www.food.com/recipe/chicken-and-dumplings-72963 Chicken dumplings]
* tablespoon.com e.g. [http://www.tablespoon.com/recipes/old-fashioned-chicken-and-dumplings-recipe/1/ Chicken dumplings]

== Implementations ==
This section is '''informative'''.

Tools for generating and consuming hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-implementations]].

* Cognition. As of September 2008, [http://buzzword.org.uk/cognition/ Cognition] has experimental support for this format. ([http://buzzword.org.uk/cognition/uf-plus.html#hrecipe Details of support].) Recipes may be exported in [[recipe-formats#RecipeBook_XML|RecipeBook XML]] format or RDF.
* WordPress Plugin. There's a [http://wordpress.org/ WordPress ] [http://wordpress.org/extend/plugins/hrecipe/ hRecipe Plugin] available which makes adding hRecipe metadata to recipes very easy, practically effortless. Very nice!
* Google. Launched 24th February, 2011, [http://www.google.com/landing/recipes/ Recipe View] search results from Google are powered by hRecipe marked-up snippets.

== References ==

=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[abbr-design-pattern]]
* [[datetime-design-pattern]]

=== Informative References ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other recipe metadata efforts. See [[recipe-formats]].
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===

Per [[Microformats_Wiki:Copyrights]], hRecipe was placed into the public domain on 2008-11-14 by the authors. There are no usage, distribution, re-printing, or any other restrictions of any kind with regards to the text or content of this specification.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Public Domain Release ===

The authors and editors of this page due hereby relinquish their copyright on the document and release the text of this page into the public domain.

* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

== derivative works ==
* [[hrecipe-rdf|hRecipe in RDF]] - mapping of hRecipe into a RDF vocabulary called "aRecipe"

==related pages==
* [[hrecipe-issues|hRecipe issues]] - issues regarding the hRecipe draft
* [[hrecipe-feedback|hRecipe feedback]] - general feedback regarding hRecipe

Per the microformats [[process]], the [[recipe]] effort developed
* [[recipe-examples]]
* [[recipe-formats]]
* [[recipe-brainstorming]] (see also [[recipe-brainstorming-archive]])
* [[recipe-issues]]
towards the development of this draft.

[[Category:Draft Specifications]]

hrecipe

2011-02-24T23:03:07Z

Phae: /* Examples in the wild */ a few more sites with hrecipe

<entry-title>hRecipe 0.22</entry-title>
{{Template:DraftSpecification}}
{{TOC-right}}
http://www.livingathome.de/test/recipe/hRecipe.png

[[recipe|hRecipe]] is a simple, open, distributed format, suitable for embedding information about recipes for cooking in (X)HTML, Atom, RSS, and arbitrary XML. hRecipe is one of several [[microformats]] open standards. This page and Microformat is in the public domain.

== hRecipe Microformat Draft Specification ==

=== Editor ===
* [[User:ThomasLoertsch | Thomas Lörtsch]]

=== Authors ===
* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]

=== Contributors===
[[User:AndyMabbett|Andy Mabbett]], [[User:Phae|Frances Berriman]], [[User:IamCam|Cameron Perry]], [[User:JohnLeMasney|John LeMasney]], [[User:Tantek|Tantek Çelik]], [[User:SudarshanP|SudarshanP]], [[User:CiaranMc|Ciaran McNulty]], [[User:LeeJordan|Lee Jordan]], [[User:RobertBachmann|Robert Bachmann]], [[User:JeffMcNeill|jeffmcneill]], [[User:ManuSporny|Manu Sporny]], [[User:RyanKing|Ryan King]], HollyMarieKoltz, Straup, [[User:ChristopheDucamp|Christophe Ducamp]], Mercman, [[User:Yde|Yde]], [[User:AmeerDawood|Ameer Dawood]], Scottk, [[User:Lee_Jordan|Lee Jordan]], MonroAlmon, EstevaoSamuel, [[User:Brian|Brian Suda]], SteveL, JohnLeMasney,

Microformats [[#Copyright]] and [[#Patents]] statements apply.

== Introduction ==

The hRecipe microformat is designed for the mark-up of instructions for creating meals, drinks or food-based items.

It is difficult for a browser to extract semantic information about a recipe described on a web page. Metadata such as author and name and details such as ingredients, method, preparation time etc provide relevant information about the recipe.

Having such information marked up can provide a number of benefits to the viewer. If a web browser understands that a particular web page contains a recipe with specific characteristics, it can produce richer interactions. For example, specific searches may be performed for ingredients or authors via general search services such as Google and Wikipedia. Additionally, classification by crawlers can become more accurate. If there are 20 recipes found on a page, and they all contain a certain ingredient, it can be assumed that the page is not only about cooking, but also about that particular ingredient.

In order to enable and encourage the sharing, distribution, syndication, and aggregation of recipes, the authors propose the hRecipe microformat, an open standard for distributed recipe metadata. The authors have researched both numerous [[recipe-examples]] in the wild and earlier attempts at [[recipe-formats]], and have designed hRecipe around a simple minimal schema for recipe content. Feedback is encouraged on the [[recipe-feedback|hRecipe feedback]] page.

=== Inspiration and Acknowledgments ===

Many thanks to the various individuals that did research and proposed ideas and discussion related to the hRecipe-format and recipes in general.

=== Scope ===

hRecipe is a format to annotate descriptions and lists of ingredients for the preparation of food and meals. Recipes consistently share several common properties. hRecipe has been based on this minimal common subset.

=== Out of scope ===

Recipes that are not for stuff that's meant to be eaten by humans are out of scope.

== Format ==

{{rfc-2119-intro}}

=== In General ===
The hRecipe format is based on a set of properties common to numerous recipe sites and formats in use today on the web. Where possible property names have been chosen based on those defined by related microformat standards. 
Some properties are marked ''experimental'' since they exceed the minimum set of properties needed to describe a recipe but still are very commonly used on the web. It's not sure if they are relevant enough for inclusion in the format. Implementation and general uptake of these properties will be observed and inform further decisions. So their use is not at all discouraged - but use them with care and be prepared for their eventual removal from the final spec.

=== Schema ===
The hRecipe schema consists of the following properties:

* '''hrecipe'''
** '''fn'''. required. text. the name of the recipe.
** '''ingredient'''. required. 1 or more. text with optional valid (x)HTML markup.
*** '''''value''''' and '''''type'''''. optional. [experimental]
** '''''yield'''''. optional. text.
** '''''instructions'''''. optional. text with optional valid (x)HTML markup.
** '''''duration'''''. optional. 1 or more. text.
** ''photo''. optional. 1 or more. using any element containing a URL, such as IMG. [experimental]
** ''summary''. optional. text. [experimental]
** ''author''. optional. 1 or more. [experimental]
** ''published''. optional. [experimental]
** ''nutrition''. optional. 1 or more. [experimental]
*** ''value'' and ''type''. optional. [experimental]
** ''tag''. optional. 1 or more. [experimental]

=== Property details ===

Property names <code>fn</code>, <code>photo</code>, <code>author</code>, <code>value</code> and <code>type</code> are reused from [[hCard]]. Property name <code>duration</code> is reused from [[hAudio]]. Property name <code>summary</code> is reused from [[hCalendar]]. Property name <code>published</code> is reused from [[hAtom]]. Property name <code>tag</code> is reused from [[rel-tag]].

The fields of the hRecipe schema represent the following:

==== hRecipe ====

A hRecipe is used to identify and describe values and metadata typically associated with a recipe.

* A hRecipe property is identified by the name <code>hrecipe</code>

==== fn ====

The title of a single recipe. A short textual description used to identify the work among interested parties. This can be the name of a meal or a short description regarding it's ingredients.

* The property is identified by the name <code>fn</code>.
* A Recipe {{must}} include a <code>fn</code>.
* The property {{must}} follow the conventions outlined in [[hCard]] e.g. by using only plain text.

==== ingredient ====

Describes one or more ingredients used in the recipe.

* The property is identified by the name <code>ingredient</code>.
* A Recipe {{must}} include one or more <code>ingredient</code>s.
* The property {{may}} include valid HTML markup (e.g. a list of ingredients).
* The property {{may}} include the properties <code>value</code> and <code>type</code> following the conventions outlined in [[hCard]], e.g. <source lang=html4strict>125ml milk</source>In this case each ingredient should be marked up with it's own <code>ingredient</code> property. These subproperties are considered ''experimental'' and may be removed from the final specification or replaced by 'num' and 'unit' from [[measure]].

==== yield ====

Specifies the quantity produced by the recipe, like how many persons it satisfyies or how many pieces can be made of it.

* The property is identified by the name <code>yield</code>.
* A Recipe {{may}} include a <code>yield</code>.

==== instructions ====

The method of the recipe.

* The property is identified by the name <code>instructions</code>.
* A Recipe {{may}} include a <code>instructions</code> property.
* The property {{may}} include valid HTML markup e.g. paragraphs or a list of steps.

==== duration ====

The time it takes to prepare the meal described by the recipe. Multiple duration properties can be used to denote e.g. time for preparing a dough, time needed for the dough to raise, time to bake the dough, time for decorating the cake etc.

* The property is identified by the name <code>duration</code>.
* A Recipe {{may}} include one or more <code>duration</code> properties.
* The property {{may}} encode the timespan as outlined in the [[value-class-pattern|value-class-pattern]]. A duration of 1 hour 30 minutes would translate to "PT1H30M" in ISO 8601 format and can be encoded as follows:<source lang=html4strict> 90 min</source>

==== photo ====

Accompanying image.

* The property is identified by the name <code>photo</code>.
* A Recipe {{may}} include one or more <code>photo</code> properties.
* The property {{should}} use an <img> element. It {{may}} use any other element that contains a URL, such as <a> or <object>, but it is not recommended. See [[hRecipe#Semantic_XHTML_Design_Principles | notes]] below.
* The property is considered ''experimental'' and may be removed from the final specification.

==== summary ====

The summary provides a short introduction to or an accompanying statement about the recipe.

* The property is identified by the name <code>summary</code>.
* A Recipe {{may}} include a <code>summary</code>.
* The property {{must}} follow the conventions outlined in [[hCalendar]]. Plain text fulfills these requirements.
* The property is considered ''experimental'' and may be removed from the final specification.

==== author ====

An author is the person who wrote the recipe.

* The property is identified by the name <code>author</code>.
* A Recipe {{may}} include one or more <code>author</code> properties.
* The contents of the element {{may}} be a plain text string in which case it defaults to a "vcard fn". Anything more elaborate {{must}} follow the conventions outlined in [[hCard]].
* The element is considered ''experimental'' and may be removed from the final specification.

==== published ====

The date the recipe was published.

* The property is identified by the name <code>published</code>.
* A Recipe {{may}} include a <code>published</code> date.
* The property {{may}} be encoded using the [[value-class-pattern|value-class-pattern]], e.g.:<source lang=html4strict>Published 14. Oct 2008</source>
* The property is considered ''experimental'' and may be removed from the final specification.

==== nutrition ====

Nutritional information like calories, fat, dietary fiber etc.

* The property is identified by name <code>nutrition</code>.
* A Recipe {{may}} include one or more <code>nutrition</code> properties.
* The property {{may}} include the properties <code>value</code> and <code>type</code> following the conventions outlined in [[hCard]]. In this case each nutritional information item should be marked up with it's own <code>nutrition</code> property. These subelement are considered ''experimental'' and may be replaced by 'num' and 'unit' from [[measure]].
* The property <code>nutrition</code> itself is also considered ''experimental'' and may be removed from the final specification.

==== tag ====

A keyword indicating a subject or an important aspect of the recipe like it's main ingredient, type of meal etc.

* The property is identified by the name <code>tag</code>.
* A Recipe {{may}} include one or more <code>tag</code>'s.
* The property {{must}} follow the conventions outlined in [[rel-tag]].
* The property is considered ''experimental'' and may be removed from the final specification.

=== Version history ===

* Version 0.22 changed the proposed formatting of time and date from the [[datetime-design-pattern|datetime-design-pattern]], which has [[datetime-design-pattern#Accessibility_issues|accessibility issues]], to the [[value-class-pattern|value-class-pattern]]. Also corrected some errors in the example especially with regard to the correct handling of vcard properties.
* Version 0.21 changed the status of ingredient/value and ingredient/type to ''experimental'', mentioning that there still is discussion if they should be replaced by 'num' and 'unit' from [[measure]] (which is still in brainstorming).
* Version 0.2: From [http://microformats.org/wiki/index.php?title=hrecipe&oldid=37357 Version 0.1] some elements have been renamed to strenghten re-use of established elements: '''fn''' for '''hRecipe-title''', '''summary''' for '''hRecipe-summary''', '''duration''' for '''preparation-time''', '''value''' and '''type''' for '''num''' and '''unit'''. Also some elements have been marked '''experimental''' because of concerns of element bloat. See the [[hrecipe-issues]] page for a more thorough discussion. Draft 0.1 was already a result of long lasting efforts. Nonetheless after publishing of it there has been a lively debate about some properties. Since they mostly could be resolved version 0.2 is considered fairly stable now, although of course you never know ;-)

=== Parser Processing Notes ===

* If the "author" property contains only a plain text string it should be regarded as of type "vcard fn".

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles}}

==== More Semantic Equivalents ====

For some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:

* For "photo", use <code><img class="photo" src="..." alt="" /></code>

==== Language ====

* To explicitly convey the natural language that an recipe is written in, use the standard (X)HTML 'lang' or 'xml:lang' attribute on the element with class="hrecipe"
**e.g. <code><nowiki>I like Kartoffelknödel best.</nowiki></code>
*If portions of an hRecipe (e.g. an ingredient name) are in a different language to the rest of the hRecipe, use the 'lang' or 'xml:lang' attribute on those portions.
* hRecipe parsers which need to handle the native language of hRecipe {{must}} process the standard (X)HTML 'lang' or 'xml:lang' attribute as specified.
* hRecipe parsers which need to handle native language {{may}} traverse up the DOM to discover the native language of the page and apply that to the hRecipe if no other language is specified on the hRecipe.

==== Human vs. Machine Readable ====

If an <code><abbr></code> element is used for a property, then its '<code>title</code>' attribute is used for the value of the property, instead of the contents of the element, which can then be used to provide a user-friendly alternate presentation of the value.

If an <code><a></code> element is used for one or more properties, it {{must}} be treated as follows:
# For the 'photo' property and any other property that takes a URL as its value, the <code>href="..."</code> attribute provides the property value.
# For other properties, the element's content is the value of the property.

If an <code><img></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>src="..."</code> attribute as property value.

If an <code><object></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>data="..."</code> attribute as property value.

=== Notes ===

This section is informative.

*Non so far.

== XMDP Profile ==

<source lang=html4strict>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>hrecipe</dt>
<dd>
Used to identify and describe metadata associated with instructions for creating meals, drinks or food-based items.
</dd>
<dt>fn</dt>
<dd>
The title of the recipe.
</dd>
<dt>ingredient</dt>
<dd>
Describes the ingredient(s) used in the recipe.
</dd>
<dt>yield</dt>
<dd>
Specifies the quantity produced by the recipe.
</dd>
<dt>instructions</dt>
<dd>
The method of the recipe.
</dd>
<dt>duration</dt>
<dd>
The time it takes to prepare the meal described by the recipe.
</dd>
<dt>photo</dt>
<dd>
Accompanying image.
</dd>
<dt>summary</dt>
<dd>
The summary provides a short introduction or an accompanying statement about the recipe.
</dd>
<dt>author</dt>
<dd>
The person who authored the recipe..
</dd>
<dt>published</dt>
<dd>
The date that the recipe was made available to the public.
</dd>
<dt>nutrition</dt>
<dd>
Nutritional information like calories, fat, dietary fiber etc.
</dd>
<dt>tag</dt>
<dd>
Keyword(s) describing the recipe.
</dd>
</dl>
</dd>
</dl>
</source>

== Examples ==

This section is informative.

Here '''will be''' a few examples of recipes, from real web sites, showing how they could be easily enhanced to use hRecipe. In the meantime the following contrieved example will have to do.

<source lang=html4strict><div class="hrecipe">
<h1 class="fn">Pommes Frites</h1>

Pommes frites originate in outer space. They are served hot. 
This recipe is only an example. Don't try this at home!


Contributed by CJ Tom and the
<a class="url fn" href="http://example.com">Cooky Gang</a>.

Published 14. Oct 2008
<img src="/img/pommes.png" class="photo" width="100" height="100" alt="Pommes Frites"/>
<h2>Ingredients</h2>
<ul>
<li class="ingredient">
500
gramme potatoes, hard cooking.
</li>
<li class="ingredient">
1 spoonful of salt
</li>
<li>
You may want to provide some
Ketchup and Mayonnaise
as well.
</li>
</ul>
<h2>Instructions</h2>
<ul class="instructions">
<li>First wash the potatoes.</li>
<li>Then slice and dice them and put them in boiling fat.</li>
<li>After a few minutes take them out again.</li>
</ul>
<h2>Further details</h2>
Enough for 12 children.
Preparation time is approximately
 90 min

Add half an hour to prepare your homemade Ketchup.
This recipe is <a href="http://www.example.com/tags/difficulty/easy" rel="tag">easy</a> and <a href="http://www.example.com/tags/tastyness/delicious" rel="tag">delicious</a>.


Pommes Frites have more than
1000
Joule
Energy,
while Ketchup and Mayonnaise have
0 vitamins.

</div>
</source>


== Examples in the wild ==

This section is '''informative'''.

Sites and pages that publish hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-examples-in-wild]].

* [http://www.epicurious.com/ Epicurious.com]'s [http://www.epicurious.com/recipesmenus/ recipes] have been marked up with hRecipe as of April 2010. (E.g., [http://www.epicurious.com/recipes/food/views/Chocolate-Almond-and-Banana-Parfaits-357369 Chocolate, Almond, and Banana Parfaits])
* [http://www.williams-sonoma.com/ Williams-Sonoma]'s [http://www.williams-sonoma.com/recipe/ recipes section], e.g. [http://www.williams-sonoma.com/recipe/cherry-almond-bundt-cake.html Cherry Almond Bundt Cake]
* http://foodnetwork.com/ has marked up all their recipes with hRecipe as of 2009-10, e.g. [http://www.foodnetwork.com/recipes/ina-garten/deep-dish-apple-pie-recipe2/index.html Deep-Dish Apple Pie recipe]
* [http://www.plantoeat.com/ Plan to Eat]'s [http://www.plantoeat.com/recipe_book recipe planner] is now in hRecipe format as of April 2010. (E.g., [http://www.plantoeat.com/recipes/4583/1fv1A5vFhjm Pasta With Smashed Peas])
* essen & trinken. As of spring 2009 [http://www.essen-und-trinken.de essen & trinken] publishes all recipes with hRecipe-conformant metadata encoded in RDF. See [[hrecipe-rdf]] for technical details.
* It's Ripe! As of January 2009, [http://itsripe.com/recipes/ http://itsripe.com] supports hRecipe for recipe pages and will soon add support in lists.
*'''Wild Mushroom, Pancetta & Truffle Risotto''' by Toby Inkster
** [http://tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Marked up as hRecipe] using the September 2007 draft format
** [http://srv.buzzword.org.uk/recipebook/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RecipeBook XML] output from Cognition.
** [http://srv.buzzword.org.uk/rdf-xml/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RDF/XML] and [http://srv.buzzword.org.uk/turtle/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Turtle] output from Cognition.
* allrecipes.com e.g. [http://allrecipes.com//Recipe/slow-cooker-chicken-and-dumplings/Detail.aspx Slow cooker chicken and dumplings]
* food.com e.g. [http://www.food.com/recipe/chicken-and-dumplings-72963 Chicken dumplings]
* tablespoon.com e.g. [http://www.tablespoon.com/recipes/old-fashioned-chicken-and-dumplings-recipe/1/ Chicken dumplings]

== Implementations ==
This section is '''informative'''.

Tools for generating and consuming hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-implementations]].

* Cognition. As of September 2008, [http://buzzword.org.uk/cognition/ Cognition] has experimental support for this format. ([http://buzzword.org.uk/cognition/uf-plus.html#hrecipe Details of support].) Recipes may be exported in [[recipe-formats#RecipeBook_XML|RecipeBook XML]] format or RDF.
* WordPress Plugin. There's a [http://wordpress.org/ WordPress ] [http://wordpress.org/extend/plugins/hrecipe/ hRecipe Plugin] available which makes adding hRecipe metadata to recipes very easy, practically effortless. Very nice!

== References ==

=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[abbr-design-pattern]]
* [[datetime-design-pattern]]

=== Informative References ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other recipe metadata efforts. See [[recipe-formats]].
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===

Per [[Microformats_Wiki:Copyrights]], hRecipe was placed into the public domain on 2008-11-14 by the authors. There are no usage, distribution, re-printing, or any other restrictions of any kind with regards to the text or content of this specification.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Public Domain Release ===

The authors and editors of this page due hereby relinquish their copyright on the document and release the text of this page into the public domain.

* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

== derivative works ==
* [[hrecipe-rdf|hRecipe in RDF]] - mapping of hRecipe into a RDF vocabulary called "aRecipe"

==related pages==
* [[hrecipe-issues|hRecipe issues]] - issues regarding the hRecipe draft
* [[hrecipe-feedback|hRecipe feedback]] - general feedback regarding hRecipe

Per the microformats [[process]], the [[recipe]] effort developed
* [[recipe-examples]]
* [[recipe-formats]]
* [[recipe-brainstorming]] (see also [[recipe-brainstorming-archive]])
* [[recipe-issues]]
towards the development of this draft.

[[Category:Draft Specifications]]

admins

2011-02-21T17:25:19Z

Phae: can't even spell my own name, apparently :)

<entry-title>microformats admins</entry-title>
== admins ==
The following individuals are invited volunteer admins on the microformats [[IRC]] channel, [[Main_Page|wiki]], and [[mailing-lists|mailing lists]]:
* [[User:RobertBachmann|Robert Bachmann]] - also maintains [[mflogbot]]
* [[User:Phae|Frances Berriman]]
* [[User:DanCederholm|Dan Cederholm]]
* [[User:Tantek|Tantek Çelik]]
* [[User:DimitriGlazkov|Dimitri Glazkov]]
* [[User:Adactio|Jeremy Keith]]
* [[User:Rohit|Rohit Khare]] - also an ''ex officio'' observer of microformats admins, as the contact point for the servers, domain names, and [[:Category:public domain license#Point of Contact|legal issues]].
* [[User:RyanKing|Ryan King]] - also maintains [[mfbot]]
* [[User:Kevin_Marks|Kevin Marks]]
* [[User:DrewMcLellan|Drew McLellan]]
* [[User:EricMeyer|Eric A. Meyer]]
* [[User:ScottReynen|Scott Reynen]]
* [[User:Brian|Brian Suda]]
* [[User:BenWard|Ben Ward]]
* [[User:BenWest|Benjamin West]]

=== Wiki-only admins ===
* [[User:ChristopheDucamp|Christophe Ducamp]] - primary editor/translator for [[Main_Page-fr]].
* [[User:Cnsupport]] - infrastructure only
* [[User:EdwardOConnor]] - for wiki spam fighting

For an automatically generated flat list of microformats wiki admins see: [[Special:Listadmins]].

== contacting ==
Contacting the admins can be done by either joining the microformats [[irc]] channel and stating "adminhelp" to alert an active moderator that you need their attention, or by using the following point of contact for the admins:

* [http://fberriman.com/ Frances Berriman] frances AT fberriman DOT com

''Please note that not all admins wish to act as points of contact, so please only use those listed.''

admins

2011-02-21T17:24:56Z

Phae: email update

<entry-title>microformats admins</entry-title>
== admins ==
The following individuals are invited volunteer admins on the microformats [[IRC]] channel, [[Main_Page|wiki]], and [[mailing-lists|mailing lists]]:
* [[User:RobertBachmann|Robert Bachmann]] - also maintains [[mflogbot]]
* [[User:Phae|Frances Berriman]]
* [[User:DanCederholm|Dan Cederholm]]
* [[User:Tantek|Tantek Çelik]]
* [[User:DimitriGlazkov|Dimitri Glazkov]]
* [[User:Adactio|Jeremy Keith]]
* [[User:Rohit|Rohit Khare]] - also an ''ex officio'' observer of microformats admins, as the contact point for the servers, domain names, and [[:Category:public domain license#Point of Contact|legal issues]].
* [[User:RyanKing|Ryan King]] - also maintains [[mfbot]]
* [[User:Kevin_Marks|Kevin Marks]]
* [[User:DrewMcLellan|Drew McLellan]]
* [[User:EricMeyer|Eric A. Meyer]]
* [[User:ScottReynen|Scott Reynen]]
* [[User:Brian|Brian Suda]]
* [[User:BenWard|Ben Ward]]
* [[User:BenWest|Benjamin West]]

=== Wiki-only admins ===
* [[User:ChristopheDucamp|Christophe Ducamp]] - primary editor/translator for [[Main_Page-fr]].
* [[User:Cnsupport]] - infrastructure only
* [[User:EdwardOConnor]] - for wiki spam fighting

For an automatically generated flat list of microformats wiki admins see: [[Special:Listadmins]].

== contacting ==
Contacting the admins can be done by either joining the microformats [[irc]] channel and stating "adminhelp" to alert an active moderator that you need their attention, or by using the following point of contact for the admins:

* [http://fberriman.com/ Frances Berriman] frances AT ferriman DOT com

''Please note that not all admins wish to act as points of contact, so please only use those listed.''

events/2011-03-14-future-of-microformats

2011-02-04T21:37:35Z

Phae: /* Tags */ added sxsw hashtag

<entry-title>The Future of Microformats - SXSW Interactive 2011</entry-title>
__TOC__
One of several microformats [[events]].

<div class="event-page vevent">
== Details ==
;When
:2011-03-14 from 15:30
;Where
:Austin Convention Center, 500 E Cesar Chavez Street, Austin, Texas 78701 USA
;What
:The Future of Microformats - SXSW Interactive Session
;Web
:http://upcoming.yahoo.com/event/7697872/
:http://www.facebook.com/event.php?eid=199322750085180
:http://plancast.com/p/3q33

'''[http://h2vx.com/ics/microformats.org/wiki/events/2011-03-14-future-of-microformats Add this event to your calendar]''' http://www.boogdesign.com/images/buttons/microformat_hcalendar.png

== Summary ==
<div class="description">Google, via its rich snippets, has reported that microformats has a 94% usage share (as compared with RDFa etc.). So how does the future look for microformats? In this session, we'll look closely at real problems with implementing microformats in [[HTML5]] and how this can be done, and whether there will be a continuing place for them. We'll also look at emerging technologies and techniques, such as [[RelMeAuth]] and discuss advanced user techniques.

== Tags ==
Use the following tags on related content (blog posts, photos, [http://twitter.com tweets]):

tags:
<kbd class="tags" style="display:block">
'''microformats-session'''
'''futuremf'''
microformats-meetup
microformats
austin
tx
texas
sxsw
sxswi
sxsw2011
sxswi2011
''microformats-session-2011-03-14''
''upcoming:event=7697872''
</kbd>

If you use Twitter, mention ''@microformats''' in tweets about the event, and track them on [http://search.twitter.com/search?q=microformats Twitter Search].

== Attendees ==
Add yourself alphabetically sorted by family name if you plan on attending or attended this event.

* [[User:Phae|Frances Berriman]]
* [[User:Tantek|Tantek Çelik]]
* [[User:YourName|You]]
* ...

== Notes ==

Topics Discussed:

* ...

== Photographs ==

* Search for photographs from this event on Flickr: [http://flickr.com/photos/tags/microformats-session-2011-03-14 Photographs tagged microformats-session-2011-03-14] or for [http://flickr.com/photos/tags/microformats-session all photographs from microformats sessions].

''Add a photograph from this event here''.

== Articles and Blog Posts ==
Articles and blog posts following up on the meetup. Add a link to your post in the list below:

* ...

Also, find posts on this meetup on [http://blogsearch.google.com/blogsearch?q=microformats-session-2011-03-14 Google Blog Search] or [http://technorati.com/search/microformats-session-2011-03-14 Technorati].

</div> 

== Related Pages==
{{events-related-pages}}

events/2011-03-sxsw

2011-02-04T21:36:35Z

Phae: /* Social media hashtag */ blah. formatting.

<entry-title>South By Southwest Interactive 2011</entry-title>

Microformats events, content and so forth at SXSWi.

==The Future of Microformats Panel==

Featuring:

* Frances Berriman
* Ben Ward
* Tantek Çelik
* Paul Tarjan

=== 140 Character Summary for SXSW documentation===

What is the future of structured data on the web? A look at new implementations, tools and hacks, plus updates on the microformats project.

=== Social media hashtag ===

hashtag: #futuremf

===Brainstorming the Panel===

Figure out the direction, content and general flow of the panel.

====Subjects to Cover====

<div class="discussion">
* Summarize the state of Microformats
** “Are microformats dead?” (not necessarily in those terms…)
*** I'm curious about the self-consciousness behind this question. Is it an actual concern? One you have heard? Or just an ironic opener? [[User:Tantek|Tantek]] 19:28, 30 January 2011 (UTC)
**** I've genuinely been asked if HTML 5 (various new elements) / Microdata replace microformats [[User:Phae|Phae]] 14:21, 31 January 2011 (UTC)
***** If the context is one of comparison, then let's handle that in comparison discussions (see below). - [[User:Tantek|Tantek]] 23:35, 31 January 2011 (UTC)
** Major implementations (to date)
*** Show an overview slide with logos of all the sites publishing microformats
*** Google search results - screenshots of rich snippets
*** [[RelMeAuth]]
*** Could demonstrate Twitter Tweet Button using <code>rel=me</code> to infer data from embedding pages
*** Glenn Jones has a few neat things too
**** Possibly demo each very quickly? Glenn was asking about doing a demo too.
** What microformats are there which are stable, ‘complete’?
*** This might be a good time to discuss potential thoughts about more formally defined microformats spec stages, e.g. draft (brainstorm consensus, ready for publishers), specification (stable multiple publisher support, implementations recommended), standard (multiple interoperable implementations) - I've brainstormed this a bit with Kevin Marks, perhaps worth further discussion at a dinner and capturing on its own wiki page).
* Cover structured data in general (perhaps briefly, just to clear up confusion)
** do a slide comparing microformats, microdata, RDFa (when you use it, which vocabs in use) - I think this might be a good lead in for the "Microformats 2.0" introduction.
** What's microdata? What's it for? Where is it supported?
** RDFa: Depending on further checking of the figures cited in Peter Mika's blog post (http://tripletalk.wordpress.com/2011/01/25/rdfa-deployment-across-the-web), what vocabularies are emerging in the RDFa space?
*** If the figures are wrong though, or there aren't any major vocabularies, then can probably skip over this. — Ben
**** Yeah, I'm a little tired of the deceptive marketing by the RDFa crowd (that article, and Ben's and Kevin Marks' trivial critiques (c.f. their twitters) are a prime example) and frankly in such a short session we shouldn't give such deceptions any time. However I *would* suggest a backup slide to debunk it (e.g. showing adoption of the class attribute or meta keyword in comparison to RDFa) when the inevitable one RDFa question comes up from the one RDFa person in the crowd. [[User:Tantek|Tantek]]
* What's happening this year?
** Any new vocabularies expected to be stable?
** vCard 4.0, and how that will tie into hCard
*** updates to hCard in general hCard 1.0.1, 1.1 - [[User:Tantek|Tantek]]
** HTML5, and how the time element affects hCalendar, hAtom, etc.
*** Good to mention X2V/H2VX update to support HTML5 and time/datetime here. - [[User:Tantek|Tantek]]
** “Microformats 2” (datatype prefixes, generic tree parsing.)
*** If this is mentioned at all, assuming Tantek is even continuing this work at all(?), I am firmly of the view that it needs to framed as an exploration around a use case, not an accepted progression of microformats as a whole. — Ben
**** Yes it is continuing :) I agree with the general thinking behind Ben's framing, that is, we need to stay practical. Direct use cases are one subset of real world problems (which is how microformats started) that microformats solve. What's driving Microformats 2.0 *is* the solving of specific real world problems that sufficient developers have encountered (i.e. not just hypothetical) that it's now finally worth spending the time to solve them. And yes, the goal would be to have Microformats 2.0 "ready to use/parse" for introduction at this session, possibly with some publisher/parser support already available (thinking Twitter, Facebook, X2V, Operator offhand). - [[User:Tantek|Tantek]]
** If we're covering individually led efforts though, Ben would like to frame up the concept of rich data containers and expanding parsing rules for those (<code>vcalendar</code> TV listings and the like.)
*** You know the drill, start an exploration wiki page on the subject :) - [[User:Tantek|Tantek]]
* Community Management? Being that this has been (is?) one of the larger challenges the microformats community has had, is it worth bringing up, lessons learned etc.?
** It's been on my mind a lot recently - particularly the reduction of traffic to mailing lists and potential stagnation of some proposals. I think we've got a tricky balance to strike. [[User:Phae|Phae]] 14:33, 31 January 2011 (UTC)
*** I think what essentially happened, to be blunt, is that the trolls "won". We had a sufficient # of trolls who overwhelmed the cognitive surplus of the admins (and the rest of the community, none of which were experienced with community management), that people (including myself) lost a lot of motivation and daily participation, IRC, etc. dropped off. I've been thinking a lot about this lately, and I think we actually have an opportunity to fix this, that is, to set up much stricter (and upfront) participation guidelines and consequences, and then act swiftly, and fairly merciless to ban those that are even minimally disruptive, because frankly, we don't have the staff to deal with educating (i.e. teaching better online manners etc.) those who are either new, immature, or just obsessive (i.e. can't help themselves from sending repeated emails to the lists, they're welcome to get such training on W3C lists where there are paid staff to deal with such folks). At that point, we can re-engage editors to step up activity, and then as admins very vigilantly patrol the lists and keep the clear of trolls. I would rather have higher quality traffic from a few productive folks, than noise from drive-by emailers. We need to act more like a meritocratic, hierarchical open source project (e.g. Mozilla) than the semi-free-for-all perceived flat "democracy" that so many standards lists (e.g. W3C) have. - [[User:Tantek|Tantek]] 23:35, 31 January 2011 (UTC)
* Accessibility? Since the value-class-pattern has solved these problems, is this worth mentioning at all?
** May be worth a mention, if only because I think the date-pattern debacle put a few souls off. [[User:Phae|Phae]] 14:33, 31 January 2011 (UTC)
*** Phae, that was 2 years ago - literally - we covered accessibility and the [[value-class-pattern]] at the SXSW 2009 session. What's left to do is debunk the out-of-date Wikipedia article on microformats and any other place the debate resurfaces. Not sure why it would be worth spending time on this at SXSW 2011 except in response to Q&A perhaps. - [[User:Tantek|Tantek]] 23:35, 31 January 2011 (UTC)
**** Fair enough, just thinking out loud :) [[User:Phae|Phae]]
</div>

====Subjects not to cover at all====
* meta keywords
* microdata on its own
* RDFa on its own
* ontology/ontologies (lose most the crowd just by mentioning the word)
* why invisible metadata fails (perhaps backup slides for Q&A response only)

events/2011-03-sxsw

2011-02-04T21:35:35Z

Phae: /* Social media hashtag */ futuremf

<entry-title>South By Southwest Interactive 2011</entry-title>

Microformats events, content and so forth at SXSWi.

==The Future of Microformats Panel==

Featuring:

* Frances Berriman
* Ben Ward
* Tantek Çelik
* Paul Tarjan

=== 140 Character Summary for SXSW documentation===

What is the future of structured data on the web? A look at new implementations, tools and hacks, plus updates on the microformats project.

=== Social media hashtag ===

#futuremf

===Brainstorming the Panel===

Figure out the direction, content and general flow of the panel.

====Subjects to Cover====

<div class="discussion">
* Summarize the state of Microformats
** “Are microformats dead?” (not necessarily in those terms…)
*** I'm curious about the self-consciousness behind this question. Is it an actual concern? One you have heard? Or just an ironic opener? [[User:Tantek|Tantek]] 19:28, 30 January 2011 (UTC)
**** I've genuinely been asked if HTML 5 (various new elements) / Microdata replace microformats [[User:Phae|Phae]] 14:21, 31 January 2011 (UTC)
***** If the context is one of comparison, then let's handle that in comparison discussions (see below). - [[User:Tantek|Tantek]] 23:35, 31 January 2011 (UTC)
** Major implementations (to date)
*** Show an overview slide with logos of all the sites publishing microformats
*** Google search results - screenshots of rich snippets
*** [[RelMeAuth]]
*** Could demonstrate Twitter Tweet Button using <code>rel=me</code> to infer data from embedding pages
*** Glenn Jones has a few neat things too
**** Possibly demo each very quickly? Glenn was asking about doing a demo too.
** What microformats are there which are stable, ‘complete’?
*** This might be a good time to discuss potential thoughts about more formally defined microformats spec stages, e.g. draft (brainstorm consensus, ready for publishers), specification (stable multiple publisher support, implementations recommended), standard (multiple interoperable implementations) - I've brainstormed this a bit with Kevin Marks, perhaps worth further discussion at a dinner and capturing on its own wiki page).
* Cover structured data in general (perhaps briefly, just to clear up confusion)
** do a slide comparing microformats, microdata, RDFa (when you use it, which vocabs in use) - I think this might be a good lead in for the "Microformats 2.0" introduction.
** What's microdata? What's it for? Where is it supported?
** RDFa: Depending on further checking of the figures cited in Peter Mika's blog post (http://tripletalk.wordpress.com/2011/01/25/rdfa-deployment-across-the-web), what vocabularies are emerging in the RDFa space?
*** If the figures are wrong though, or there aren't any major vocabularies, then can probably skip over this. — Ben
**** Yeah, I'm a little tired of the deceptive marketing by the RDFa crowd (that article, and Ben's and Kevin Marks' trivial critiques (c.f. their twitters) are a prime example) and frankly in such a short session we shouldn't give such deceptions any time. However I *would* suggest a backup slide to debunk it (e.g. showing adoption of the class attribute or meta keyword in comparison to RDFa) when the inevitable one RDFa question comes up from the one RDFa person in the crowd. [[User:Tantek|Tantek]]
* What's happening this year?
** Any new vocabularies expected to be stable?
** vCard 4.0, and how that will tie into hCard
*** updates to hCard in general hCard 1.0.1, 1.1 - [[User:Tantek|Tantek]]
** HTML5, and how the time element affects hCalendar, hAtom, etc.
*** Good to mention X2V/H2VX update to support HTML5 and time/datetime here. - [[User:Tantek|Tantek]]
** “Microformats 2” (datatype prefixes, generic tree parsing.)
*** If this is mentioned at all, assuming Tantek is even continuing this work at all(?), I am firmly of the view that it needs to framed as an exploration around a use case, not an accepted progression of microformats as a whole. — Ben
**** Yes it is continuing :) I agree with the general thinking behind Ben's framing, that is, we need to stay practical. Direct use cases are one subset of real world problems (which is how microformats started) that microformats solve. What's driving Microformats 2.0 *is* the solving of specific real world problems that sufficient developers have encountered (i.e. not just hypothetical) that it's now finally worth spending the time to solve them. And yes, the goal would be to have Microformats 2.0 "ready to use/parse" for introduction at this session, possibly with some publisher/parser support already available (thinking Twitter, Facebook, X2V, Operator offhand). - [[User:Tantek|Tantek]]
** If we're covering individually led efforts though, Ben would like to frame up the concept of rich data containers and expanding parsing rules for those (<code>vcalendar</code> TV listings and the like.)
*** You know the drill, start an exploration wiki page on the subject :) - [[User:Tantek|Tantek]]
* Community Management? Being that this has been (is?) one of the larger challenges the microformats community has had, is it worth bringing up, lessons learned etc.?
** It's been on my mind a lot recently - particularly the reduction of traffic to mailing lists and potential stagnation of some proposals. I think we've got a tricky balance to strike. [[User:Phae|Phae]] 14:33, 31 January 2011 (UTC)
*** I think what essentially happened, to be blunt, is that the trolls "won". We had a sufficient # of trolls who overwhelmed the cognitive surplus of the admins (and the rest of the community, none of which were experienced with community management), that people (including myself) lost a lot of motivation and daily participation, IRC, etc. dropped off. I've been thinking a lot about this lately, and I think we actually have an opportunity to fix this, that is, to set up much stricter (and upfront) participation guidelines and consequences, and then act swiftly, and fairly merciless to ban those that are even minimally disruptive, because frankly, we don't have the staff to deal with educating (i.e. teaching better online manners etc.) those who are either new, immature, or just obsessive (i.e. can't help themselves from sending repeated emails to the lists, they're welcome to get such training on W3C lists where there are paid staff to deal with such folks). At that point, we can re-engage editors to step up activity, and then as admins very vigilantly patrol the lists and keep the clear of trolls. I would rather have higher quality traffic from a few productive folks, than noise from drive-by emailers. We need to act more like a meritocratic, hierarchical open source project (e.g. Mozilla) than the semi-free-for-all perceived flat "democracy" that so many standards lists (e.g. W3C) have. - [[User:Tantek|Tantek]] 23:35, 31 January 2011 (UTC)
* Accessibility? Since the value-class-pattern has solved these problems, is this worth mentioning at all?
** May be worth a mention, if only because I think the date-pattern debacle put a few souls off. [[User:Phae|Phae]] 14:33, 31 January 2011 (UTC)
*** Phae, that was 2 years ago - literally - we covered accessibility and the [[value-class-pattern]] at the SXSW 2009 session. What's left to do is debunk the out-of-date Wikipedia article on microformats and any other place the debate resurfaces. Not sure why it would be worth spending time on this at SXSW 2011 except in response to Q&A perhaps. - [[User:Tantek|Tantek]] 23:35, 31 January 2011 (UTC)
**** Fair enough, just thinking out loud :) [[User:Phae|Phae]]
</div>

====Subjects not to cover at all====
* meta keywords
* microdata on its own
* RDFa on its own
* ontology/ontologies (lose most the crowd just by mentioning the word)
* why invisible metadata fails (perhaps backup slides for Q&A response only)

events/2011-03-sxsw

2011-02-04T21:34:15Z

Phae: /* 140 Character Summary for SXSW documentation */ ben's better version

<entry-title>South By Southwest Interactive 2011</entry-title>

Microformats events, content and so forth at SXSWi.

==The Future of Microformats Panel==

Featuring:

* Frances Berriman
* Ben Ward
* Tantek Çelik
* Paul Tarjan

=== 140 Character Summary for SXSW documentation===

What is the future of structured data on the web? A look at new implementations, tools and hacks, plus updates on the microformats project.

=== Social media hashtag ===

#futuremf or #sxswmf ?

===Brainstorming the Panel===

Figure out the direction, content and general flow of the panel.

====Subjects to Cover====

<div class="discussion">
* Summarize the state of Microformats
** “Are microformats dead?” (not necessarily in those terms…)
*** I'm curious about the self-consciousness behind this question. Is it an actual concern? One you have heard? Or just an ironic opener? [[User:Tantek|Tantek]] 19:28, 30 January 2011 (UTC)
**** I've genuinely been asked if HTML 5 (various new elements) / Microdata replace microformats [[User:Phae|Phae]] 14:21, 31 January 2011 (UTC)
***** If the context is one of comparison, then let's handle that in comparison discussions (see below). - [[User:Tantek|Tantek]] 23:35, 31 January 2011 (UTC)
** Major implementations (to date)
*** Show an overview slide with logos of all the sites publishing microformats
*** Google search results - screenshots of rich snippets
*** [[RelMeAuth]]
*** Could demonstrate Twitter Tweet Button using <code>rel=me</code> to infer data from embedding pages
*** Glenn Jones has a few neat things too
**** Possibly demo each very quickly? Glenn was asking about doing a demo too.
** What microformats are there which are stable, ‘complete’?
*** This might be a good time to discuss potential thoughts about more formally defined microformats spec stages, e.g. draft (brainstorm consensus, ready for publishers), specification (stable multiple publisher support, implementations recommended), standard (multiple interoperable implementations) - I've brainstormed this a bit with Kevin Marks, perhaps worth further discussion at a dinner and capturing on its own wiki page).
* Cover structured data in general (perhaps briefly, just to clear up confusion)
** do a slide comparing microformats, microdata, RDFa (when you use it, which vocabs in use) - I think this might be a good lead in for the "Microformats 2.0" introduction.
** What's microdata? What's it for? Where is it supported?
** RDFa: Depending on further checking of the figures cited in Peter Mika's blog post (http://tripletalk.wordpress.com/2011/01/25/rdfa-deployment-across-the-web), what vocabularies are emerging in the RDFa space?
*** If the figures are wrong though, or there aren't any major vocabularies, then can probably skip over this. — Ben
**** Yeah, I'm a little tired of the deceptive marketing by the RDFa crowd (that article, and Ben's and Kevin Marks' trivial critiques (c.f. their twitters) are a prime example) and frankly in such a short session we shouldn't give such deceptions any time. However I *would* suggest a backup slide to debunk it (e.g. showing adoption of the class attribute or meta keyword in comparison to RDFa) when the inevitable one RDFa question comes up from the one RDFa person in the crowd. [[User:Tantek|Tantek]]
* What's happening this year?
** Any new vocabularies expected to be stable?
** vCard 4.0, and how that will tie into hCard
*** updates to hCard in general hCard 1.0.1, 1.1 - [[User:Tantek|Tantek]]
** HTML5, and how the time element affects hCalendar, hAtom, etc.
*** Good to mention X2V/H2VX update to support HTML5 and time/datetime here. - [[User:Tantek|Tantek]]
** “Microformats 2” (datatype prefixes, generic tree parsing.)
*** If this is mentioned at all, assuming Tantek is even continuing this work at all(?), I am firmly of the view that it needs to framed as an exploration around a use case, not an accepted progression of microformats as a whole. — Ben
**** Yes it is continuing :) I agree with the general thinking behind Ben's framing, that is, we need to stay practical. Direct use cases are one subset of real world problems (which is how microformats started) that microformats solve. What's driving Microformats 2.0 *is* the solving of specific real world problems that sufficient developers have encountered (i.e. not just hypothetical) that it's now finally worth spending the time to solve them. And yes, the goal would be to have Microformats 2.0 "ready to use/parse" for introduction at this session, possibly with some publisher/parser support already available (thinking Twitter, Facebook, X2V, Operator offhand). - [[User:Tantek|Tantek]]
** If we're covering individually led efforts though, Ben would like to frame up the concept of rich data containers and expanding parsing rules for those (<code>vcalendar</code> TV listings and the like.)
*** You know the drill, start an exploration wiki page on the subject :) - [[User:Tantek|Tantek]]
* Community Management? Being that this has been (is?) one of the larger challenges the microformats community has had, is it worth bringing up, lessons learned etc.?
** It's been on my mind a lot recently - particularly the reduction of traffic to mailing lists and potential stagnation of some proposals. I think we've got a tricky balance to strike. [[User:Phae|Phae]] 14:33, 31 January 2011 (UTC)
*** I think what essentially happened, to be blunt, is that the trolls "won". We had a sufficient # of trolls who overwhelmed the cognitive surplus of the admins (and the rest of the community, none of which were experienced with community management), that people (including myself) lost a lot of motivation and daily participation, IRC, etc. dropped off. I've been thinking a lot about this lately, and I think we actually have an opportunity to fix this, that is, to set up much stricter (and upfront) participation guidelines and consequences, and then act swiftly, and fairly merciless to ban those that are even minimally disruptive, because frankly, we don't have the staff to deal with educating (i.e. teaching better online manners etc.) those who are either new, immature, or just obsessive (i.e. can't help themselves from sending repeated emails to the lists, they're welcome to get such training on W3C lists where there are paid staff to deal with such folks). At that point, we can re-engage editors to step up activity, and then as admins very vigilantly patrol the lists and keep the clear of trolls. I would rather have higher quality traffic from a few productive folks, than noise from drive-by emailers. We need to act more like a meritocratic, hierarchical open source project (e.g. Mozilla) than the semi-free-for-all perceived flat "democracy" that so many standards lists (e.g. W3C) have. - [[User:Tantek|Tantek]] 23:35, 31 January 2011 (UTC)
* Accessibility? Since the value-class-pattern has solved these problems, is this worth mentioning at all?
** May be worth a mention, if only because I think the date-pattern debacle put a few souls off. [[User:Phae|Phae]] 14:33, 31 January 2011 (UTC)
*** Phae, that was 2 years ago - literally - we covered accessibility and the [[value-class-pattern]] at the SXSW 2009 session. What's left to do is debunk the out-of-date Wikipedia article on microformats and any other place the debate resurfaces. Not sure why it would be worth spending time on this at SXSW 2011 except in response to Q&A perhaps. - [[User:Tantek|Tantek]] 23:35, 31 January 2011 (UTC)
**** Fair enough, just thinking out loud :) [[User:Phae|Phae]]
</div>

====Subjects not to cover at all====
* meta keywords
* microdata on its own
* RDFa on its own
* ontology/ontologies (lose most the crowd just by mentioning the word)
* why invisible metadata fails (perhaps backup slides for Q&A response only)

events/2011-03-14-future-of-microformats

2011-02-04T21:21:06Z

Phae: /* Attendees */ alphabetical

<entry-title>The Future of Microformats - SXSW Interactive 2011</entry-title>
__TOC__
One of several microformats [[events]].

<div class="event-page vevent">
== Details ==
;When
:2011-03-14 from 15:30
;Where
:Austin Convention Center, 500 E Cesar Chavez Street, Austin, Texas 78701 USA
;What
:The Future of Microformats - SXSW Interactive Session
;Web
:http://upcoming.yahoo.com/event/7697872/
:http://www.facebook.com/event.php?eid=199322750085180
:http://plancast.com/p/3q33

'''[http://h2vx.com/ics/microformats.org/wiki/events/2011-03-14-future-of-microformats Add this event to your calendar]''' http://www.boogdesign.com/images/buttons/microformat_hcalendar.png

== Summary ==
<div class="description">Google, via its rich snippets, has reported that microformats has a 94% usage share (as compared with RDFa etc.). So how does the future look for microformats? In this session, we'll look closely at real problems with implementing microformats in [[HTML5]] and how this can be done, and whether there will be a continuing place for them. We'll also look at emerging technologies and techniques, such as [[RelMeAuth]] and discuss advanced user techniques.

== Tags ==
Use the following tags on related content (blog posts, photos, [http://twitter.com tweets]):

tags:
<kbd class="tags" style="display:block">
'''microformats-session'''
microformats-meetup
microformats
austin
tx
texas
sxsw
sxswi
sxsw2011
sxswi2011
''microformats-session-2011-03-14''
''upcoming:event=7697872''
</kbd>

If you use Twitter, mention ''@microformats''' in tweets about the event, and track them on [http://search.twitter.com/search?q=microformats Twitter Search].

== Attendees ==
Add yourself alphabetically sorted by family name if you plan on attending or attended this event.

* [[User:Phae|Frances Berriman]]
* [[User:Tantek|Tantek Çelik]]
* [[User:YourName|You]]
* ...

== Notes ==

Topics Discussed:

* ...

== Photographs ==

* Search for photographs from this event on Flickr: [http://flickr.com/photos/tags/microformats-session-2011-03-14 Photographs tagged microformats-session-2011-03-14] or for [http://flickr.com/photos/tags/microformats-session all photographs from microformats sessions].

''Add a photograph from this event here''.

== Articles and Blog Posts ==
Articles and blog posts following up on the meetup. Add a link to your post in the list below:

* ...

Also, find posts on this meetup on [http://blogsearch.google.com/blogsearch?q=microformats-session-2011-03-14 Google Blog Search] or [http://technorati.com/search/microformats-session-2011-03-14 Technorati].

</div> 

== Related Pages==
{{events-related-pages}}

events/2011-03-14-future-of-microformats

2011-02-04T21:20:34Z

Phae: /* Attendees */ added me

<entry-title>The Future of Microformats - SXSW Interactive 2011</entry-title>
__TOC__
One of several microformats [[events]].

<div class="event-page vevent">
== Details ==
;When
:2011-03-14 from 15:30
;Where
:Austin Convention Center, 500 E Cesar Chavez Street, Austin, Texas 78701 USA
;What
:The Future of Microformats - SXSW Interactive Session
;Web
:http://upcoming.yahoo.com/event/7697872/
:http://www.facebook.com/event.php?eid=199322750085180
:http://plancast.com/p/3q33

'''[http://h2vx.com/ics/microformats.org/wiki/events/2011-03-14-future-of-microformats Add this event to your calendar]''' http://www.boogdesign.com/images/buttons/microformat_hcalendar.png

== Summary ==
<div class="description">Google, via its rich snippets, has reported that microformats has a 94% usage share (as compared with RDFa etc.). So how does the future look for microformats? In this session, we'll look closely at real problems with implementing microformats in [[HTML5]] and how this can be done, and whether there will be a continuing place for them. We'll also look at emerging technologies and techniques, such as [[RelMeAuth]] and discuss advanced user techniques.

== Tags ==
Use the following tags on related content (blog posts, photos, [http://twitter.com tweets]):

tags:
<kbd class="tags" style="display:block">
'''microformats-session'''
microformats-meetup
microformats
austin
tx
texas
sxsw
sxswi
sxsw2011
sxswi2011
''microformats-session-2011-03-14''
''upcoming:event=7697872''
</kbd>

If you use Twitter, mention ''@microformats''' in tweets about the event, and track them on [http://search.twitter.com/search?q=microformats Twitter Search].

== Attendees ==
Add yourself alphabetically sorted by family name if you plan on attending or attended this event.

* [[User:Tantek|Tantek Çelik]]
* [[User:Phae|Frances Berriman]]
* [[User:YourName|You]]
* ...

== Notes ==

Topics Discussed:

* ...

== Photographs ==

* Search for photographs from this event on Flickr: [http://flickr.com/photos/tags/microformats-session-2011-03-14 Photographs tagged microformats-session-2011-03-14] or for [http://flickr.com/photos/tags/microformats-session all photographs from microformats sessions].

''Add a photograph from this event here''.

== Articles and Blog Posts ==
Articles and blog posts following up on the meetup. Add a link to your post in the list below:

* ...

Also, find posts on this meetup on [http://blogsearch.google.com/blogsearch?q=microformats-session-2011-03-14 Google Blog Search] or [http://technorati.com/search/microformats-session-2011-03-14 Technorati].

</div> 

== Related Pages==
{{events-related-pages}}

events/2011-03-sxsw

2011-02-04T21:19:57Z

Phae: /* 140 Character Summary for SXSW documentation */ s

<entry-title>South By Southwest Interactive 2011</entry-title>

Microformats events, content and so forth at SXSWi.

==The Future of Microformats Panel==

Featuring:

* Frances Berriman
* Ben Ward
* Tantek Çelik
* Paul Tarjan

=== 140 Character Summary for SXSW documentation===

Discussing the future of microformats, implementations, new tools and techniques and the highs and lows of the project.

=== Social media hashtag ===

#futuremf or #sxswmf ?

===Brainstorming the Panel===

Figure out the direction, content and general flow of the panel.

====Subjects to Cover====

<div class="discussion">
* Summarize the state of Microformats
** “Are microformats dead?” (not necessarily in those terms…)
*** I'm curious about the self-consciousness behind this question. Is it an actual concern? One you have heard? Or just an ironic opener? [[User:Tantek|Tantek]] 19:28, 30 January 2011 (UTC)
**** I've genuinely been asked if HTML 5 (various new elements) / Microdata replace microformats [[User:Phae|Phae]] 14:21, 31 January 2011 (UTC)
***** If the context is one of comparison, then let's handle that in comparison discussions (see below). - [[User:Tantek|Tantek]] 23:35, 31 January 2011 (UTC)
** Major implementations (to date)
*** Show an overview slide with logos of all the sites publishing microformats
*** Google search results - screenshots of rich snippets
*** [[RelMeAuth]]
*** Could demonstrate Twitter Tweet Button using <code>rel=me</code> to infer data from embedding pages
*** Glenn Jones has a few neat things too
**** Possibly demo each very quickly? Glenn was asking about doing a demo too.
** What microformats are there which are stable, ‘complete’?
*** This might be a good time to discuss potential thoughts about more formally defined microformats spec stages, e.g. draft (brainstorm consensus, ready for publishers), specification (stable multiple publisher support, implementations recommended), standard (multiple interoperable implementations) - I've brainstormed this a bit with Kevin Marks, perhaps worth further discussion at a dinner and capturing on its own wiki page).
* Cover structured data in general (perhaps briefly, just to clear up confusion)
** do a slide comparing microformats, microdata, RDFa (when you use it, which vocabs in use) - I think this might be a good lead in for the "Microformats 2.0" introduction.
** What's microdata? What's it for? Where is it supported?
** RDFa: Depending on further checking of the figures cited in Peter Mika's blog post (http://tripletalk.wordpress.com/2011/01/25/rdfa-deployment-across-the-web), what vocabularies are emerging in the RDFa space?
*** If the figures are wrong though, or there aren't any major vocabularies, then can probably skip over this. — Ben
**** Yeah, I'm a little tired of the deceptive marketing by the RDFa crowd (that article, and Ben's and Kevin Marks' trivial critiques (c.f. their twitters) are a prime example) and frankly in such a short session we shouldn't give such deceptions any time. However I *would* suggest a backup slide to debunk it (e.g. showing adoption of the class attribute or meta keyword in comparison to RDFa) when the inevitable one RDFa question comes up from the one RDFa person in the crowd. [[User:Tantek|Tantek]]
* What's happening this year?
** Any new vocabularies expected to be stable?
** vCard 4.0, and how that will tie into hCard
*** updates to hCard in general hCard 1.0.1, 1.1 - [[User:Tantek|Tantek]]
** HTML5, and how the time element affects hCalendar, hAtom, etc.
*** Good to mention X2V/H2VX update to support HTML5 and time/datetime here. - [[User:Tantek|Tantek]]
** “Microformats 2” (datatype prefixes, generic tree parsing.)
*** If this is mentioned at all, assuming Tantek is even continuing this work at all(?), I am firmly of the view that it needs to framed as an exploration around a use case, not an accepted progression of microformats as a whole. — Ben
**** Yes it is continuing :) I agree with the general thinking behind Ben's framing, that is, we need to stay practical. Direct use cases are one subset of real world problems (which is how microformats started) that microformats solve. What's driving Microformats 2.0 *is* the solving of specific real world problems that sufficient developers have encountered (i.e. not just hypothetical) that it's now finally worth spending the time to solve them. And yes, the goal would be to have Microformats 2.0 "ready to use/parse" for introduction at this session, possibly with some publisher/parser support already available (thinking Twitter, Facebook, X2V, Operator offhand). - [[User:Tantek|Tantek]]
** If we're covering individually led efforts though, Ben would like to frame up the concept of rich data containers and expanding parsing rules for those (<code>vcalendar</code> TV listings and the like.)
*** You know the drill, start an exploration wiki page on the subject :) - [[User:Tantek|Tantek]]
* Community Management? Being that this has been (is?) one of the larger challenges the microformats community has had, is it worth bringing up, lessons learned etc.?
** It's been on my mind a lot recently - particularly the reduction of traffic to mailing lists and potential stagnation of some proposals. I think we've got a tricky balance to strike. [[User:Phae|Phae]] 14:33, 31 January 2011 (UTC)
*** I think what essentially happened, to be blunt, is that the trolls "won". We had a sufficient # of trolls who overwhelmed the cognitive surplus of the admins (and the rest of the community, none of which were experienced with community management), that people (including myself) lost a lot of motivation and daily participation, IRC, etc. dropped off. I've been thinking a lot about this lately, and I think we actually have an opportunity to fix this, that is, to set up much stricter (and upfront) participation guidelines and consequences, and then act swiftly, and fairly merciless to ban those that are even minimally disruptive, because frankly, we don't have the staff to deal with educating (i.e. teaching better online manners etc.) those who are either new, immature, or just obsessive (i.e. can't help themselves from sending repeated emails to the lists, they're welcome to get such training on W3C lists where there are paid staff to deal with such folks). At that point, we can re-engage editors to step up activity, and then as admins very vigilantly patrol the lists and keep the clear of trolls. I would rather have higher quality traffic from a few productive folks, than noise from drive-by emailers. We need to act more like a meritocratic, hierarchical open source project (e.g. Mozilla) than the semi-free-for-all perceived flat "democracy" that so many standards lists (e.g. W3C) have. - [[User:Tantek|Tantek]] 23:35, 31 January 2011 (UTC)
* Accessibility? Since the value-class-pattern has solved these problems, is this worth mentioning at all?
** May be worth a mention, if only because I think the date-pattern debacle put a few souls off. [[User:Phae|Phae]] 14:33, 31 January 2011 (UTC)
*** Phae, that was 2 years ago - literally - we covered accessibility and the [[value-class-pattern]] at the SXSW 2009 session. What's left to do is debunk the out-of-date Wikipedia article on microformats and any other place the debate resurfaces. Not sure why it would be worth spending time on this at SXSW 2011 except in response to Q&A perhaps. - [[User:Tantek|Tantek]] 23:35, 31 January 2011 (UTC)
**** Fair enough, just thinking out loud :) [[User:Phae|Phae]]
</div>

====Subjects not to cover at all====
* meta keywords
* microdata on its own
* RDFa on its own
* ontology/ontologies (lose most the crowd just by mentioning the word)
* why invisible metadata fails (perhaps backup slides for Q&A response only)

events/2011-03-sxsw

2011-02-04T21:17:12Z

Phae: /* Social media hashtag */ poss tags

<entry-title>South By Southwest Interactive 2011</entry-title>

Microformats events, content and so forth at SXSWi.

==The Future of Microformats Panel==

Featuring:

* Frances Berriman
* Ben Ward
* Tantek Çelik
* Paul Tarjan

=== 140 Character Summary for SXSW documentation===

Discussing the future of microformats, implementation, new tools and techniques and the highs and lows of the project.

=== Social media hashtag ===

#futuremf or #sxswmf ?

===Brainstorming the Panel===

Figure out the direction, content and general flow of the panel.

====Subjects to Cover====

<div class="discussion">
* Summarize the state of Microformats
** “Are microformats dead?” (not necessarily in those terms…)
*** I'm curious about the self-consciousness behind this question. Is it an actual concern? One you have heard? Or just an ironic opener? [[User:Tantek|Tantek]] 19:28, 30 January 2011 (UTC)
**** I've genuinely been asked if HTML 5 (various new elements) / Microdata replace microformats [[User:Phae|Phae]] 14:21, 31 January 2011 (UTC)
***** If the context is one of comparison, then let's handle that in comparison discussions (see below). - [[User:Tantek|Tantek]] 23:35, 31 January 2011 (UTC)
** Major implementations (to date)
*** Show an overview slide with logos of all the sites publishing microformats
*** Google search results - screenshots of rich snippets
*** [[RelMeAuth]]
*** Could demonstrate Twitter Tweet Button using <code>rel=me</code> to infer data from embedding pages
*** Glenn Jones has a few neat things too
**** Possibly demo each very quickly? Glenn was asking about doing a demo too.
** What microformats are there which are stable, ‘complete’?
*** This might be a good time to discuss potential thoughts about more formally defined microformats spec stages, e.g. draft (brainstorm consensus, ready for publishers), specification (stable multiple publisher support, implementations recommended), standard (multiple interoperable implementations) - I've brainstormed this a bit with Kevin Marks, perhaps worth further discussion at a dinner and capturing on its own wiki page).
* Cover structured data in general (perhaps briefly, just to clear up confusion)
** do a slide comparing microformats, microdata, RDFa (when you use it, which vocabs in use) - I think this might be a good lead in for the "Microformats 2.0" introduction.
** What's microdata? What's it for? Where is it supported?
** RDFa: Depending on further checking of the figures cited in Peter Mika's blog post (http://tripletalk.wordpress.com/2011/01/25/rdfa-deployment-across-the-web), what vocabularies are emerging in the RDFa space?
*** If the figures are wrong though, or there aren't any major vocabularies, then can probably skip over this. — Ben
**** Yeah, I'm a little tired of the deceptive marketing by the RDFa crowd (that article, and Ben's and Kevin Marks' trivial critiques (c.f. their twitters) are a prime example) and frankly in such a short session we shouldn't give such deceptions any time. However I *would* suggest a backup slide to debunk it (e.g. showing adoption of the class attribute or meta keyword in comparison to RDFa) when the inevitable one RDFa question comes up from the one RDFa person in the crowd. [[User:Tantek|Tantek]]
* What's happening this year?
** Any new vocabularies expected to be stable?
** vCard 4.0, and how that will tie into hCard
*** updates to hCard in general hCard 1.0.1, 1.1 - [[User:Tantek|Tantek]]
** HTML5, and how the time element affects hCalendar, hAtom, etc.
*** Good to mention X2V/H2VX update to support HTML5 and time/datetime here. - [[User:Tantek|Tantek]]
** “Microformats 2” (datatype prefixes, generic tree parsing.)
*** If this is mentioned at all, assuming Tantek is even continuing this work at all(?), I am firmly of the view that it needs to framed as an exploration around a use case, not an accepted progression of microformats as a whole. — Ben
**** Yes it is continuing :) I agree with the general thinking behind Ben's framing, that is, we need to stay practical. Direct use cases are one subset of real world problems (which is how microformats started) that microformats solve. What's driving Microformats 2.0 *is* the solving of specific real world problems that sufficient developers have encountered (i.e. not just hypothetical) that it's now finally worth spending the time to solve them. And yes, the goal would be to have Microformats 2.0 "ready to use/parse" for introduction at this session, possibly with some publisher/parser support already available (thinking Twitter, Facebook, X2V, Operator offhand). - [[User:Tantek|Tantek]]
** If we're covering individually led efforts though, Ben would like to frame up the concept of rich data containers and expanding parsing rules for those (<code>vcalendar</code> TV listings and the like.)
*** You know the drill, start an exploration wiki page on the subject :) - [[User:Tantek|Tantek]]
* Community Management? Being that this has been (is?) one of the larger challenges the microformats community has had, is it worth bringing up, lessons learned etc.?
** It's been on my mind a lot recently - particularly the reduction of traffic to mailing lists and potential stagnation of some proposals. I think we've got a tricky balance to strike. [[User:Phae|Phae]] 14:33, 31 January 2011 (UTC)
*** I think what essentially happened, to be blunt, is that the trolls "won". We had a sufficient # of trolls who overwhelmed the cognitive surplus of the admins (and the rest of the community, none of which were experienced with community management), that people (including myself) lost a lot of motivation and daily participation, IRC, etc. dropped off. I've been thinking a lot about this lately, and I think we actually have an opportunity to fix this, that is, to set up much stricter (and upfront) participation guidelines and consequences, and then act swiftly, and fairly merciless to ban those that are even minimally disruptive, because frankly, we don't have the staff to deal with educating (i.e. teaching better online manners etc.) those who are either new, immature, or just obsessive (i.e. can't help themselves from sending repeated emails to the lists, they're welcome to get such training on W3C lists where there are paid staff to deal with such folks). At that point, we can re-engage editors to step up activity, and then as admins very vigilantly patrol the lists and keep the clear of trolls. I would rather have higher quality traffic from a few productive folks, than noise from drive-by emailers. We need to act more like a meritocratic, hierarchical open source project (e.g. Mozilla) than the semi-free-for-all perceived flat "democracy" that so many standards lists (e.g. W3C) have. - [[User:Tantek|Tantek]] 23:35, 31 January 2011 (UTC)
* Accessibility? Since the value-class-pattern has solved these problems, is this worth mentioning at all?
** May be worth a mention, if only because I think the date-pattern debacle put a few souls off. [[User:Phae|Phae]] 14:33, 31 January 2011 (UTC)
*** Phae, that was 2 years ago - literally - we covered accessibility and the [[value-class-pattern]] at the SXSW 2009 session. What's left to do is debunk the out-of-date Wikipedia article on microformats and any other place the debate resurfaces. Not sure why it would be worth spending time on this at SXSW 2011 except in response to Q&A perhaps. - [[User:Tantek|Tantek]] 23:35, 31 January 2011 (UTC)
**** Fair enough, just thinking out loud :) [[User:Phae|Phae]]
</div>

====Subjects not to cover at all====
* meta keywords
* microdata on its own
* RDFa on its own
* ontology/ontologies (lose most the crowd just by mentioning the word)
* why invisible metadata fails (perhaps backup slides for Q&A response only)

events/2011-03-sxsw

2011-02-04T21:15:29Z

Phae: /* 140 Character Summary for SXSW documentation */ first pass

<entry-title>South By Southwest Interactive 2011</entry-title>

Microformats events, content and so forth at SXSWi.

==The Future of Microformats Panel==

Featuring:

* Frances Berriman
* Ben Ward
* Tantek Çelik
* Paul Tarjan

=== 140 Character Summary for SXSW documentation===

Discussing the future of microformats, implementation, new tools and techniques and the highs and lows of the project.

=== Social media hashtag ===

TBD

===Brainstorming the Panel===

Figure out the direction, content and general flow of the panel.

====Subjects to Cover====

<div class="discussion">
* Summarize the state of Microformats
** “Are microformats dead?” (not necessarily in those terms…)
*** I'm curious about the self-consciousness behind this question. Is it an actual concern? One you have heard? Or just an ironic opener? [[User:Tantek|Tantek]] 19:28, 30 January 2011 (UTC)
**** I've genuinely been asked if HTML 5 (various new elements) / Microdata replace microformats [[User:Phae|Phae]] 14:21, 31 January 2011 (UTC)
***** If the context is one of comparison, then let's handle that in comparison discussions (see below). - [[User:Tantek|Tantek]] 23:35, 31 January 2011 (UTC)
** Major implementations (to date)
*** Show an overview slide with logos of all the sites publishing microformats
*** Google search results - screenshots of rich snippets
*** [[RelMeAuth]]
*** Could demonstrate Twitter Tweet Button using <code>rel=me</code> to infer data from embedding pages
*** Glenn Jones has a few neat things too
**** Possibly demo each very quickly? Glenn was asking about doing a demo too.
** What microformats are there which are stable, ‘complete’?
*** This might be a good time to discuss potential thoughts about more formally defined microformats spec stages, e.g. draft (brainstorm consensus, ready for publishers), specification (stable multiple publisher support, implementations recommended), standard (multiple interoperable implementations) - I've brainstormed this a bit with Kevin Marks, perhaps worth further discussion at a dinner and capturing on its own wiki page).
* Cover structured data in general (perhaps briefly, just to clear up confusion)
** do a slide comparing microformats, microdata, RDFa (when you use it, which vocabs in use) - I think this might be a good lead in for the "Microformats 2.0" introduction.
** What's microdata? What's it for? Where is it supported?
** RDFa: Depending on further checking of the figures cited in Peter Mika's blog post (http://tripletalk.wordpress.com/2011/01/25/rdfa-deployment-across-the-web), what vocabularies are emerging in the RDFa space?
*** If the figures are wrong though, or there aren't any major vocabularies, then can probably skip over this. — Ben
**** Yeah, I'm a little tired of the deceptive marketing by the RDFa crowd (that article, and Ben's and Kevin Marks' trivial critiques (c.f. their twitters) are a prime example) and frankly in such a short session we shouldn't give such deceptions any time. However I *would* suggest a backup slide to debunk it (e.g. showing adoption of the class attribute or meta keyword in comparison to RDFa) when the inevitable one RDFa question comes up from the one RDFa person in the crowd. [[User:Tantek|Tantek]]
* What's happening this year?
** Any new vocabularies expected to be stable?
** vCard 4.0, and how that will tie into hCard
*** updates to hCard in general hCard 1.0.1, 1.1 - [[User:Tantek|Tantek]]
** HTML5, and how the time element affects hCalendar, hAtom, etc.
*** Good to mention X2V/H2VX update to support HTML5 and time/datetime here. - [[User:Tantek|Tantek]]
** “Microformats 2” (datatype prefixes, generic tree parsing.)
*** If this is mentioned at all, assuming Tantek is even continuing this work at all(?), I am firmly of the view that it needs to framed as an exploration around a use case, not an accepted progression of microformats as a whole. — Ben
**** Yes it is continuing :) I agree with the general thinking behind Ben's framing, that is, we need to stay practical. Direct use cases are one subset of real world problems (which is how microformats started) that microformats solve. What's driving Microformats 2.0 *is* the solving of specific real world problems that sufficient developers have encountered (i.e. not just hypothetical) that it's now finally worth spending the time to solve them. And yes, the goal would be to have Microformats 2.0 "ready to use/parse" for introduction at this session, possibly with some publisher/parser support already available (thinking Twitter, Facebook, X2V, Operator offhand). - [[User:Tantek|Tantek]]
** If we're covering individually led efforts though, Ben would like to frame up the concept of rich data containers and expanding parsing rules for those (<code>vcalendar</code> TV listings and the like.)
*** You know the drill, start an exploration wiki page on the subject :) - [[User:Tantek|Tantek]]
* Community Management? Being that this has been (is?) one of the larger challenges the microformats community has had, is it worth bringing up, lessons learned etc.?
** It's been on my mind a lot recently - particularly the reduction of traffic to mailing lists and potential stagnation of some proposals. I think we've got a tricky balance to strike. [[User:Phae|Phae]] 14:33, 31 January 2011 (UTC)
*** I think what essentially happened, to be blunt, is that the trolls "won". We had a sufficient # of trolls who overwhelmed the cognitive surplus of the admins (and the rest of the community, none of which were experienced with community management), that people (including myself) lost a lot of motivation and daily participation, IRC, etc. dropped off. I've been thinking a lot about this lately, and I think we actually have an opportunity to fix this, that is, to set up much stricter (and upfront) participation guidelines and consequences, and then act swiftly, and fairly merciless to ban those that are even minimally disruptive, because frankly, we don't have the staff to deal with educating (i.e. teaching better online manners etc.) those who are either new, immature, or just obsessive (i.e. can't help themselves from sending repeated emails to the lists, they're welcome to get such training on W3C lists where there are paid staff to deal with such folks). At that point, we can re-engage editors to step up activity, and then as admins very vigilantly patrol the lists and keep the clear of trolls. I would rather have higher quality traffic from a few productive folks, than noise from drive-by emailers. We need to act more like a meritocratic, hierarchical open source project (e.g. Mozilla) than the semi-free-for-all perceived flat "democracy" that so many standards lists (e.g. W3C) have. - [[User:Tantek|Tantek]] 23:35, 31 January 2011 (UTC)
* Accessibility? Since the value-class-pattern has solved these problems, is this worth mentioning at all?
** May be worth a mention, if only because I think the date-pattern debacle put a few souls off. [[User:Phae|Phae]] 14:33, 31 January 2011 (UTC)
*** Phae, that was 2 years ago - literally - we covered accessibility and the [[value-class-pattern]] at the SXSW 2009 session. What's left to do is debunk the out-of-date Wikipedia article on microformats and any other place the debate resurfaces. Not sure why it would be worth spending time on this at SXSW 2011 except in response to Q&A perhaps. - [[User:Tantek|Tantek]] 23:35, 31 January 2011 (UTC)
**** Fair enough, just thinking out loud :) [[User:Phae|Phae]]
</div>

====Subjects not to cover at all====
* meta keywords
* microdata on its own
* RDFa on its own
* ontology/ontologies (lose most the crowd just by mentioning the word)
* why invisible metadata fails (perhaps backup slides for Q&A response only)

events/2011-03-sxsw

2011-02-01T09:11:41Z

Phae: response

<entry-title>South By Southwest Interactive 2011</entry-title>

Microformats events, content and so forth at SXSWi.

==The Future of Microformats Panel==

Featuring:

* Frances Berriman
* Ben Ward
* Tantek Çelik
* Paul Tarjan

=== 140 Character Summary for SXSW documentation===

TBD

=== Social media hashtag ===

TBD

===Brainstorming the Panel===

Figure out the direction, content and general flow of the panel.

====Subjects to Cover====

<div class="discussion">
* Summarize the state of Microformats
** “Are microformats dead?” (not necessarily in those terms…)
*** I'm curious about the self-consciousness behind this question. Is it an actual concern? One you have heard? Or just an ironic opener? [[User:Tantek|Tantek]] 19:28, 30 January 2011 (UTC)
**** I've genuinely been asked if HTML 5 (various new elements) / Microdata replace microformats [[User:Phae|Phae]] 14:21, 31 January 2011 (UTC)
***** If the context is one of comparison, then let's handle that in comparison discussions (see below). - [[User:Tantek|Tantek]] 23:35, 31 January 2011 (UTC)
** Major implementations (to date)
*** Show an overview slide with logos of all the sites publishing microformats
*** Google search results - screenshots of rich snippets
*** [[RelMeAuth]]
*** Could demonstrate Twitter Tweet Button using <code>rel=me</code> to infer data from embedding pages
*** Glenn Jones has a few neat things too
**** Possibly demo each very quickly? Glenn was asking about doing a demo too.
** What microformats are there which are stable, ‘complete’?
*** This might be a good time to discuss potential thoughts about more formally defined microformats spec stages, e.g. draft (brainstorm consensus, ready for publishers), specification (stable multiple publisher support, implementations recommended), standard (multiple interoperable implementations) - I've brainstormed this a bit with Kevin Marks, perhaps worth further discussion at a dinner and capturing on its own wiki page).
* Cover structured data in general (perhaps briefly, just to clear up confusion)
** do a slide comparing microformats, microdata, RDFa (when you use it, which vocabs in use) - I think this might be a good lead in for the "Microformats 2.0" introduction.
** What's microdata? What's it for? Where is it supported?
** RDFa: Depending on further checking of the figures cited in Peter Mika's blog post (http://tripletalk.wordpress.com/2011/01/25/rdfa-deployment-across-the-web), what vocabularies are emerging in the RDFa space?
*** If the figures are wrong though, or there aren't any major vocabularies, then can probably skip over this. — Ben
**** Yeah, I'm a little tired of the deceptive marketing by the RDFa crowd (that article, and Ben's and Kevin Marks' trivial critiques (c.f. their twitters) are a prime example) and frankly in such a short session we shouldn't give such deceptions any time. However I *would* suggest a backup slide to debunk it (e.g. showing adoption of the class attribute or meta keyword in comparison to RDFa) when the inevitable one RDFa question comes up from the one RDFa person in the crowd. [[User:Tantek|Tantek]]
* What's happening this year?
** Any new vocabularies expected to be stable?
** vCard 4.0, and how that will tie into hCard
*** updates to hCard in general hCard 1.0.1, 1.1 - [[User:Tantek|Tantek]]
** HTML5, and how the time element affects hCalendar, hAtom, etc.
*** Good to mention X2V/H2VX update to support HTML5 and time/datetime here. - [[User:Tantek|Tantek]]
** “Microformats 2” (datatype prefixes, generic tree parsing.)
*** If this is mentioned at all, assuming Tantek is even continuing this work at all(?), I am firmly of the view that it needs to framed as an exploration around a use case, not an accepted progression of microformats as a whole. — Ben
**** Yes it is continuing :) I agree with the general thinking behind Ben's framing, that is, we need to stay practical. Direct use cases are one subset of real world problems (which is how microformats started) that microformats solve. What's driving Microformats 2.0 *is* the solving of specific real world problems that sufficient developers have encountered (i.e. not just hypothetical) that it's now finally worth spending the time to solve them. And yes, the goal would be to have Microformats 2.0 "ready to use/parse" for introduction at this session, possibly with some publisher/parser support already available (thinking Twitter, Facebook, X2V, Operator offhand). - [[User:Tantek|Tantek]]
** If we're covering individually led efforts though, Ben would like to frame up the concept of rich data containers and expanding parsing rules for those (<code>vcalendar</code> TV listings and the like.)
*** You know the drill, start an exploration wiki page on the subject :) - [[User:Tantek|Tantek]]
* Community Management? Being that this has been (is?) one of the larger challenges the microformats community has had, is it worth bringing up, lessons learned etc.?
** It's been on my mind a lot recently - particularly the reduction of traffic to mailing lists and potential stagnation of some proposals. I think we've got a tricky balance to strike. [[User:Phae|Phae]] 14:33, 31 January 2011 (UTC)
*** I think what essentially happened, to be blunt, is that the trolls "won". We had a sufficient # of trolls who overwhelmed the cognitive surplus of the admins (and the rest of the community, none of which were experienced with community management), that people (including myself) lost a lot of motivation and daily participation, IRC, etc. dropped off. I've been thinking a lot about this lately, and I think we actually have an opportunity to fix this, that is, to set up much stricter (and upfront) participation guidelines and consequences, and then act swiftly, and fairly merciless to ban those that are even minimally disruptive, because frankly, we don't have the staff to deal with educating (i.e. teaching better online manners etc.) those who are either new, immature, or just obsessive (i.e. can't help themselves from sending repeated emails to the lists, they're welcome to get such training on W3C lists where there are paid staff to deal with such folks). At that point, we can re-engage editors to step up activity, and then as admins very vigilantly patrol the lists and keep the clear of trolls. I would rather have higher quality traffic from a few productive folks, than noise from drive-by emailers. We need to act more like a meritocratic, hierarchical open source project (e.g. Mozilla) than the semi-free-for-all perceived flat "democracy" that so many standards lists (e.g. W3C) have. - [[User:Tantek|Tantek]] 23:35, 31 January 2011 (UTC)
* Accessibility? Since the value-class-pattern has solved these problems, is this worth mentioning at all?
** May be worth a mention, if only because I think the date-pattern debacle put a few souls off. [[User:Phae|Phae]] 14:33, 31 January 2011 (UTC)
*** Phae, that was 2 years ago - literally - we covered accessibility and the [[value-class-pattern]] at the SXSW 2009 session. What's left to do is debunk the out-of-date Wikipedia article on microformats and any other place the debate resurfaces. Not sure why it would be worth spending time on this at SXSW 2011 except in response to Q&A perhaps. - [[User:Tantek|Tantek]] 23:35, 31 January 2011 (UTC)
**** Fair enough, just thinking out loud :) [[User:Phae|Phae]]
</div>

====Subjects not to cover at all====
* meta keywords
* microdata on its own
* RDFa on its own
* ontology/ontologies (lose most the crowd just by mentioning the word)
* why invisible metadata fails (perhaps backup slides for Q&A response only)

events/2011-03-sxsw

2011-01-31T14:33:05Z

Phae: /* Subjects to Cover */ community

<entry-title>South By Southwest Interactive 2011</entry-title>

Microformats events, content and so forth at SXSWi.

==The Future of Microformats Panel==

Featuring:

* Frances Berriman
* Ben Ward
* Tantek Çelik
* Paul Tarjan

=== 140 Character Summary for SXSW documentation===

TBD

=== Social media hashtag ===

TBD

===Brainstorming the Panel===

Figure out the direction, content and general flow of the panel.

====Subjects to Cover====

<div class="discussion">
* Summarize the state of Microformats
** “Are microformats dead?” (not necessarily in those terms…)
*** I'm curious about the self-consciousness behind this question. Is it an actual concern? One you have heard? Or just an ironic opener? [[User:Tantek|Tantek]] 19:28, 30 January 2011 (UTC)
**** I've genuinely been asked if HTML 5 (various new elements) / Microdata replace microformats [[User:Phae|Phae]] 14:21, 31 January 2011 (UTC)
** Major implementations (to date)
*** Show an overview slide with logos of all the sites publishing microformats
*** Google search results - screenshots of rich snippets
*** [[RelMeAuth]]
*** Could demonstrate Twitter Tweet Button using <code>rel=me</code> to infer data from embedding pages
*** Glenn Jones has a few neat things too
**** Possibly demo each very quickly? Glenn was asking about doing a demo too.
** What microformats are there which are stable, ‘complete’?
*** This might be a good time to discuss potential thoughts about more formally defined microformats spec stages, e.g. draft (brainstorm consensus, ready for publishers), specification (stable multiple publisher support, implementations recommended), standard (multiple interoperable implementations) - I've brainstormed this a bit with Kevin Marks, perhaps worth further discussion at a dinner and capturing on its own wiki page).
* Cover structured data in general (perhaps briefly, just to clear up confusion)
** do a slide comparing microformats, microdata, RDFa (when you use it, which vocabs in use) - I think this might be a good lead in for the "Microformats 2.0" introduction.
** What's microdata? What's it for? Where is it supported?
** RDFa: Depending on further checking of the figures cited in Peter Mika's blog post (http://tripletalk.wordpress.com/2011/01/25/rdfa-deployment-across-the-web), what vocabularies are emerging in the RDFa space?
*** If the figures are wrong though, or there aren't any major vocabularies, then can probably skip over this. — Ben
**** Yeah, I'm a little tired of the deceptive marketing by the RDFa crowd (that article, and Ben's and Kevin Marks' trivial critiques (c.f. their twitters) are a prime example) and frankly in such a short session we shouldn't give such deceptions any time. However I *would* suggest a backup slide to debunk it (e.g. showing adoption of the class attribute or meta keyword in comparison to RDFa) when the inevitable one RDFa question comes up from the one RDFa person in the crowd. [[User:Tantek|Tantek]]
* What's happening this year?
** Any new vocabularies expected to be stable?
** vCard 4.0, and how that will tie into hCard
*** updates to hCard in general hCard 1.0.1, 1.1 - [[User:Tantek|Tantek]]
** HTML5, and how the time element affects hCalendar, hAtom, etc.
*** Good to mention X2V/H2VX update to support HTML5 and time/datetime here. - [[User:Tantek|Tantek]]
** “Microformats 2” (datatype prefixes, generic tree parsing.)
*** If this is mentioned at all, assuming Tantek is even continuing this work at all(?), I am firmly of the view that it needs to framed as an exploration around a use case, not an accepted progression of microformats as a whole. — Ben
**** Yes it is continuing :) I agree with the general thinking behind Ben's framing, that is, we need to stay practical. Direct use cases are one subset of real world problems (which is how microformats started) that microformats solve. What's driving Microformats 2.0 *is* the solving of specific real world problems that sufficient developers have encountered (i.e. not just hypothetical) that it's now finally worth spending the time to solve them. And yes, the goal would be to have Microformats 2.0 "ready to use/parse" for introduction at this session, possibly with some publisher/parser support already available (thinking Twitter, Facebook, X2V, Operator offhand). - [[User:Tantek|Tantek]]
** If we're covering individually led efforts though, Ben would like to frame up the concept of rich data containers and expanding parsing rules for those (<code>vcalendar</code> TV listings and the like.)
*** You know the drill, start an exploration wiki page on the subject :) - [[User:Tantek|Tantek]]
* Community Management? Being that this has been (is?) one of the larger challenges the microformats community has had, is it worth bringing up, lessons learned etc.?
** It's been on my mind a lot recently - particularly the reduction of traffic to mailing lists and potential stagnation of some proposals. I think we've got a tricky balance to strike. [[User:Phae|Phae]] 14:33, 31 January 2011 (UTC)
* Accessibility? Since the value-class-pattern has solved these problems, is this worth mentioning at all?
** May be worth a mention, if only because I think the date-pattern debacle put a few souls off. [[User:Phae|Phae]] 14:33, 31 January 2011 (UTC)
</div>

====Subjects not to cover at all====
* meta keywords
* microdata on its own
* RDFa on its own
* ontology/ontologies (lose most the crowd just by mentioning the word)
* why invisible metadata fails (perhaps backup slides for Q&A response only)

events/2011-03-sxsw

2011-01-31T14:22:49Z

Phae: we need to pick tags

events/2011-03-sxsw

2011-01-31T14:21:51Z

Phae: /* Subjects to Cover */ explicit

events/2011-03-sxsw

2011-01-31T14:21:05Z

Phae: response

introduction

2011-01-20T09:53:24Z

Phae: Reverted edits by BenjaminCadman (Talk) to last version by Tantek

<entry-title>Introduction to Microformats</entry-title>
__TOC__
== What are Microformats? ==

Microformats are a way of adding simple markup to human-readable data items such as events, contact details or locations, on web pages, so that the information in them can be extracted by software and indexed, searched for, saved, cross-referenced or combined.

More technically, they are items of semantic markup, using just standard "plain old semantic (X)HTML" (i.e. "[[POSH]]") with a set of common [[class-names]] and "[[rel]]" values. They are open and available, freely, for anyone to use.

== Why Microformats ==

Why did we come up with microformats?

In short, microformats are the convergence of a number of trends:
# a logical next step in the evolution of web design and information architecture
# a way for people and organisations to publish richer information themselves, without having to rely upon centralized services
# an acknowledgement that (outside of specialist areas) "traditional" metadata efforts have either failed or taken so long to garner any adoption, that a new approach was necessary
# a way to use [[(X)HTML]] for data.

== The Appeal to Simplicity ==

* Microformats are a simple effort which has appealed to many frustrated with previous complex efforts. One parallel that can be drawn is to REST in the web services world - for more on REST see [[suggested-reading#REST|suggested reading on REST]].
* See: [http://www.justinleavesley.com/journal/2005/7/28/web-services-and-the-innovators-dilemma.html Web Services and the Innovators Dilemma] by Justin Leavesley

==See also==
* A list of [[notable-users|some notable users]].
* Recent [[press]] interviews and [[articles]] are also a good introduction.
* See microformat [[presentations]] for more background and introductory material on [[microformats]].
* Listen to [[podcasts]] about microformats.
* Read the [[faq|FAQs]] for general microformat queries.
* More [[suggested-reading|suggested reading]]
* [[implement|So you want to implement microformats?]]
* [[presentations]]
* [[podcasts]]
* [[testimonials]]

== external ==
* Sitepoint has a nice introductory tutorial: [http://reference.sitepoint.com/html/microformats Microformats - Plugging the Gaps in HTML]
* Premasagar has written up [http://premasagar.com/microformats/compound/ some nice microformats examples with source].

== Translations ==
* [[introduction-pt-br]] (see also [[introduction-pt-br-2]])
* ...

Main Page

2011-01-20T09:52:01Z

Phae: Reverted edits by BenjaminCadman (Talk) to last version by WebOrganics

<entry-title>Welcome to the microformats wiki!</entry-title>
__TOC__
Please start with the [[introduction]] page and read [[how-to-play]] before making any edits.

==Introduction==
This wiki is the central resource of the microformats community. You'll find current versions of published microformat specifications, specification drafts and publishing patterns. The wiki also hosts development resources, such as brainstorming pages for new formats and issue tracking pages for all current and in-development microformats.

== Get Started==
To get started with microformats:

* First, be familiar writing your pages and applications with semantically rich, descriptive, ‘[[posh|<abbr title="Plain Old Semantic HTML">POSH</abbr>]]’ <abbr title="HyperText Mark-up Language">HTML</abbr>.
* Learn about microformats from the [http://microformats.org/about/ about page], [http://microformats.org/ blog], [[press]], [[presentations]], [[books]], [[podcasts]], & [[screencasts]] pages.
* Take a look at established specifications such as [[hcard|hCard]] and [[hcalendar|hCalendar]], and follow the [[hcard-examples|examples]] to start publishing microformats.
* Have questions? Read the [[faq|frequently asked questions]] and see the [[glossary]] for terms and definitions. You can also post to the {{MicroformatsMailingList}}.
* Want to learn more in person? Check out microformats [[events]].

==Definition==
Microformats are small patterns of HTML to represent commonly published things like [[hcard|people]], [[hcalendar|events]], [[hatom|blog posts]], [[hreview|reviews]] and [[rel-tag|tags]] in web pages.

Microformats enable the publishing of higher fidelity information on the Web; the fastest and simplest way to provide feeds and APIs for the information in your website.

* Read more explanations of [[what-are-microformats|what microformats are]], and [[what-can-you-do-with-microformats|what you can do with them]].

== How to contribute ==
Do you want to help take microformats to the next level? You can:

* [[get-started|Get started]] by adding microformats to your website, services, and products.
* [[advocacy|Advocate]] the use of microformats on other web sites, especially those you use.
* Write a [[testimonial]].
* Do something on the [[to-do|to do list]].
* Join the [[irc|IRC Channel]] and [[mail|mailing lists]] to learn and help answer questions (read the [[mailing-lists#General_guidelines|general guidelines]] before posting).
* [[Main_Page#microformats_wiki_translations|Translate this microformats wiki into other languages]] to make microformats more accessible to readers of languages around the world.
* Before proposing any new microformats, make sure your website is [[POSH]], [[get-started|uses existing microformats]], and then read the [[process]].

This wiki has a number of enhancements to assist development and contributions to microformats. Before you start editing, see the [[wiki-2|wiki introduction page]] for instructions.

== Specifications ==
The list of current, stable [[microformats|Microformats]] open standard specifications.

* [[hcalendar|hCalendar]] - [http://microformats.org/code/hcalendar/creator hCalendar creator]
* [[hcard|hCard]] - [http://microformats.org/code/hcard/creator hCard creator]
* [[rel-license]]
* [[rel-nofollow]]
* [[rel-tag]]
* [[vote-links|VoteLinks]]
* [[XFN]] - [http://gmpg.org/xfn/creator XFN creator]
* [[XMDP]]
* [[xoxo|XOXO]]

''If you're tempted to try your hand at writing a microformat please read '''[[process|the process]]''' page first!''

== Drafts ==
Drafts are newer microformats, for which the specifications haven't been completed yet. Drafts are somewhat mature in the development [[process]] (see [[exploratory-discussions]] for additional efforts that are not as far along in the process). The stability of these documents cannot be guaranteed, and implementers should be prepared to keep abreast of future developments and changes. Please watch the wiki pages for updates.

* [[adr|adr]] - for marking up address information
* [[geo|geo]] - for marking up [http://en.wikipedia.org/wiki/WGS84 WGS84] geographic coordinates (latitude; longitude)
* [[hatom|hAtom]] - syndicating episodic content (e.g. weblog postings)
* [[haudio|hAudio]]
* [[hlisting|hListing]] - open, distributed listings
* [[hmedia|hMedia]] - A single media publishing format that relates to Images, Video and Audio.
* [[hnews|hNews]]
* [[hproduct|hProduct]]
* [[hrecipe|hRecipe]] - for cooking+baking recipes
* [[hresume|hResume]] - for publishing resumes and CVs
* [[hreview|hReview]] - [http://microformats.org/code/hreview/creator hReview creator]
* [[rel-directory]] - to indicate that the destination of a hyperlink is a directory listing containing an entry for the current page
* [[rel-enclosure]] - for indicating attachments (e.g. files) to download and cache
* [[rel-home]] - indicate a hyperlink to the homepage of the site
* [[rel-payment]] - indicate a payment mechanism
* [[robots-exclusion|robots exclusion]]

* [[xfolk|xFolk]]

== Design Patterns ==
{{design_patterns}} 

== Exploratory Discussions ==
See: [[exploratory-discussions]] for details of research and analysis of real-world [[examples]], existing formats, and brainstorming of possible new microformats, per the microformats [[process]].

== Examples ==
* [[examples-in-the-wild]]
* [[implementations]]
* [[zen-garden]]

== Resources ==
See [[resources]].

== User centric development ==
*[[user-interface]]
*[[data-portability]]
*[[social-network-portability]]

== Shared work areas ==
* [[to-do]]
* [[templates]]
* [http://microformats.org/wiki/delete pages for deletion] 
* [[Special:Specialpages|"Special" wiki pages]]
* [[year-in-review]]

== Tools, test cases, additional research ==
The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting [[tools|tools and services]] that need to process more than one microformat. That section is intended for editors, [[parsers]], [[validators]], test cases, and other information relevant across multiple microformats.

== Microformats wiki translations ==
You may read and edit microformats articles in many other languages:

* languages with over 100 articles
** [[Main_Page-fr|Français (French)]] {{UpdateMarker-fr}}
* languages with over 10 articles
** [[Main_Page-pt-br|Português (Brazilian Portuguese)]]
** [[Main_Page-ja|日本語 (Japanese)]]
** [[Main_Page-ru|Русский (Russian)]]
* languages with over 2 articles
** [[Main_Page-cs|Česky (Czech)]] {{NewMarker}}
** [[Main_Page-de|Deutsch (German)]]
** [[Main_Page-es|Español (Spanish)]]
** [[Main_Page-gl|Galego (Galician)]] {{NewMarker}}
** [[Main_Page-pl|Polski (Polish)]]
** [[Main_Page-ro|Română (Romanian)]] {{NewMarker}}
** [[Main_Page-zh|汉语 (Chinese)]]
** [[Main_Page-id|Indonesia (Bahasa Indonesia)]] {{NewMarker}}
* languages just started
** [[Main_Page-fa|پارسی (Farsi)]] {{NewMarker}}
** [[Main_Page-ar|العربية (Arabic)]]
** [[Main_Page-th|ภาษาไทย (Thai)]]
** [[Main_Page-it|Italiano (Italian)]] {{NewMarker}}
** [[Main_Page-ko|한국어 (Korean)]] {{NewMarker}}
* elsewhere
**[http://en.wikipedia.org/wiki/Microformat Wikipedia's article on microformats] has been translated into a number of languages.

See also [[other-languages]], and [[how-to-start-new-translation|how-to-start-a-new-translation]].

Main Page

2010-10-02T15:52:03Z

Phae: Reverted edits by Spanishproperty01 (Talk) to last version by Tantek

User:Phae

2010-06-03T15:03:51Z

Phae: correcting for new job

Frances Berriman
*Front-end developer at [http://nature.com Nature Publishing Group], and previously at the [http://www.bbc.co.uk BBC].
*Blogs at [http://fberriman.com http://fberriman.com]
*Contact at fberriman@gmail.com

*Main interests regarding microformats:
** Improvement of how-to, educational resources and explanations for new microformat users
** Implementing microformats where ever possible to provide test beds for developers (see my blog)
** Accessibility testing of microformats (ask me if you want me to do testing for you)
** Spreading microformats

--

{{cc-public-domain-release}}

hrecipe-issues

2010-04-29T13:57:30Z

Phae: /* issues */ min/max durations query

== issues ==
Please add new issues to the '''bottom''' of this section by copy and pasting the [[hrecipe-issues#template|Template]]. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.

<div class="vevent">
* {{OpenIssue}} 2009-01-22 raised by [[User:ThomasLoertsch|ThomasLoertsch]]
<div class="description">
* '''"num" and "unit"'''. I only recently discovered the properties "type" and "value" from 'hCard'. I'll replace "num" and "unit" from the unfinished 'measure' with them.
** The decision to replace "num", "unit", and "item" with "type" and "value" needs further explanation. Was it due to the fact that measure is unfinished? If so I think leaving "ingredient" and "nutrition" as text strings until measure is finished would be a better idea. The transition from "type"/"value" to measure will be difficult at a later point and I believe measure is more appropriate than re-using hCard. [[User:Yde|Yde]] 11:46, 23 January 2009 (UTC)
*** The proposal to replace "num", "unit", and "item" with "type" and "value" has several reasons: first, i only recently thoroughly and systematically investgated other formats and that's when i found "type" and "value". They have a semantic advantage in that they may be more suitable for cases like value:"2"/type:"eggs" or value:"1/2"/type:"spoonfull" which are rather informal ways of putting measures, at least do not lend themselves easily to formal specification. Another reason is that these terms come from a comparably very stable vocabulary, while measure has not even draft status. It would be perfectly okay for measure to change attribute names, semantics or even the whole structure of the vocabulary. Although it doesn't look like that measure will (have to) do that I'd prefer to stay on the safe side, especially since we might even gain semantic advantage. [[User:ThomasLoertsch|ThomasLoertsch]] 19:43, 23 January 2009 (UTC)
**** I'm still not sure this is the right decision. 1) I don't think the semantic meaning of hCard's "type"/"value" is exactly equivalent to measure's "num"/"unit"/"item". From the [[hcard-profile]]: "Value: This class name is used to distinguish the actual *value* of a property from any other cruft that may be in the element representing the property." So what is the actual value of an ingredient? Is it the name of the ingredient or is the quantity? 2) This is ''exactly'' what [[measure]] is for. The advantage of being able to convert measures would IMO be one of the gratest advantages of hRecipe. I don't see why value:"2"/type:"eggs" is better than num:"2"/item:"eggs"? I agree that cases like value:"1/2"/type:"spoonfull" is problematic, but that's a [[measure]] issue. 3) Many [[recipe-formats]] use quantity/unit/item.
***** Measurements are rather informal in recipes and therefor the type/value pair seems quite appropriate to me. Automatic translation is out of scope. Anyway for a good enough machine translation of a recipe the markup of the ingredients won't be the main hurdle. Standardizing the informal quantities would be a requirement for such an effort. I made some suggestions for a vocabulary of most used "units" like cups, teespoonfulls etc a few months ago but no one reacted. So I dropped it.
***** But we're moving in circles. You are making valid points too. One reason I decided this way is that it's more inline with other decisions like reusing "fn". Since not all the shortcomings of microformats can be solved within hRecipe and since there has been no interest in discussing them here I decided to go the way of least resistance and stick with the customs of compactness, reuse and rather lax interpretation of semantic constraints. IMO hRecipe is now consistent with the genereal microformats approach and neither necessitates nor hinders a general redesign of microformats (which I think would be a good thing). --[[User:ThomasLoertsch|ThomasLoertsch]] 11:21, 18 February 2009 (UTC)
**** Proposed resolution: keep "ingredient" as a text string like "yield" - which would also benefit from a measure format - until such a format is ready. [[User:Yde|Yde]] 10:23, 15 February 2009 (UTC)
***** I opened this issue again and marked the subproperty 'value' and 'type' of ingredient as ''experimental''. This should leave enough room to discuss this issue further. --[[User:ThomasLoertsch|ThomasLoertsch]] 11:21, 18 February 2009 (UTC)
</div>
</div>

<div class="vevent">
* {{OpenIssue}} 2008-12-27 raised by [[User:Tantek|Tantek Çelik]]
<div class="description discussion issues">
# '''Too many properties.''' From reviewing the [[recipe-examples]], it does not appear that the schema implied by the examples justify the number of properties in hRecipe, especially for a first draft. microformats should start as small as possible (even smaller), and in this regard I believe several improvements could be made. There is one obvious example of recipe-title vs recipe-summary, but it looks like there may be more. Would appreciate feedback from folks who add hRecipe to the recipes on the web regarding which properties they ended up not using.
#* It is not necessarily helpful to constrain a vocabulary by all means. hCard and hCalender are examples for too large vocabularies (which mostly stems from the approach taken of converting an existing vocab 1:1) which are not as easily usable as one would wish. But to be useful a vocabluary should encompass 80:20 of the usecases, otherwise it may well not be worth the burden of implementation. We better try to hit that sweet spot right from the start - since otherwise, how should hRecipe get traction in the wild. All of the proposed properties are used on big recipe sites (many 'user generated content' sites among them) on the web. Please provide more arguments which properties you specifically think are superfluous. The only concrete example you give is to replace title by summary (which I think is a bad idea). [[User:ThomasLoertsch|ThomasLoertsch]]
#* Version 0.2 (and a little more so 0.21) has marked all but the most essential properties as ''experimental''. There use is not at all discouraged but implementors are warned that these properties may be removed from later version if they aren't used in real world applications. This uptake by implementors should be observed and studied before a final descision is made. A proposed timeframe would be at least a few months, maybe even a year or two, depending on how many implemetations surface in the meantime. --[[User:ThomasLoertsch|ThomasLoertsch]] 11:21, 18 February 2009 (UTC)
#* I checked the usage of the hRecipe format today and was delighted to see that Yahoo! searchmonkey lists 56.000 of them (search Yahoo for "searchmonkey:com.yahoo.page.uf.recipe"). The site I work for is responsible for about 12.000 of them but when i checked the first 70 results none of them was from our site :-) In fact they almost all came from personal sites, blogs and the like and this is really great! It was also very interesting to see that a lot of them came from WordPress Blogs which shows that the WordPress Plugin for hRecipe is very useful. But back to the issue: I checked the first 60 or so results and about 2/3 of them where really using hRecipe. 17 of them were from different sites(*) (**).

It's never bad to gather some empirical data to make an informed decision, so I took the burden to count element use. Actually this didn't take much more then an hour, so if somebody wants to check the results from 61 to ... feel free! Well, now, without futher ado, the results:
<pre>
16 fn
17 ingredient (3 value, 3 type)
3 yield
15 instructions
3 duration
4 photo
9 summary
4 author
3 published
1 nutrition (0 value, 0 type)
2 tag
</pre>
Of course this is not representative, but it gives a fairly good impression. If you add our site (or 20% of all published hRecipes ;) you can add +1 to all elements since we use everything...

Evaluation:

"fn", "ingredient" and "instructions" are no-brainers. Also "summary" is surprisingly strong and the intuition, that it's a strong part of how people communicate on recipes, seems to be right.

"author" and "published" probably didn't get so much used because on a blog they are provided anyway and most of the sites investigated were blogs. OTOH they aren't important for the functionality of a recipe and can be added by other means. So maybe they should be removed for the sake of terseness.

"photo" was definitely less used than there were photos added to recipes. And I know a lot of people who, when showed 2 recipes, one with and one without photo, almost certainly choose the one with photo. So IMHO it should stay.

"yield" was used surprisingly seldomly. Isn't it an essential addition to the ingredients list? Maybe the yield is often self-explanatory, maybe this reflects the fact, that also the value and type of ingredients wasn't marked up most of the time. 'Smallishness' would certainly suggest to omit all the three: "value", "type" and yield". People seem to feel that the "ingredient" field naturally holds information not only about the name of the ingredient but about type and value too and don't bother to mark these up explicitely. Again for big sites which generate their content from databases the cost-benefit ratio is totally different...

"duration" would be a candidate for removal as well. But still, remeber that this list only reflects usage of the elements. An information of duration was part of the recipe more often than it was marked up as such.

"tag" obviously didn't get used much and is maybe strong enough on it's own. People add tags no matter if they are part of a vocabulary, and the rel-tag pattern is certainly easy enough to grasp and straightforward to implement.
But the WordPress plugin added a tagging vocabulary on it's own (how dare they... ;-) which did get used most of the time. So tagging principally is strong. Well, I still don't have a clue on this one.

"nutrition" is definitely a candidate for removal, maybe into it's own vocabulary. OTOH, big commercially backed sites very often provide nutritional information and when provided it is a much more integral part of the information context than say the author. So maybe it should stay?
The full result-set, including URLs:
<pre>
fn ingredient v t yield instructions duration photo summary author published nutrition v t tag
http://nissasham.blog.com/
x x x x x x
http://reciperiot.blog.com/
x x x
http://www.greenworld365.com/twice-baked-buttermilk-potatoes/
x x
http://peachquilting.com/2009/04/beef-with-garlic-potatoes/ (wordpress plugin)
x x x x
http://fivepennynicole.com/blog/2008/10/29/world-series-caramel-corn/ (wordpress plugin)
x x x x x x x
http://www.theslowcook.com/2009/04/23/shrimp-stir-fry/ (wordpress plugin)
x x x
http://bitten.blogs.nytimes.com/2009/01/29/addictive-mac-and-cheese/ well ... very freestyle
x x x x
http://au.food.yahoo.com/recipes/recipe/-/5346170/baked-chicken-ravioli/
x x x x
http://humblegourmand.com/recipes/grovestand-lemon-cupcakes/
x x x x x x x
http://www.f00die.com/
x x x x
http://www.thebarkersworld.com/ (wordpress plugin)
x x x x
http://www.murraywilliams.com/cooking/souffle.html
x x x x
http://cookingwithbooze.org/beer/beer-brats/
x x x x
http://itsripe.com/recipes/11-kale-smoothie
x x x x x x x x x x
http://xavierroy.com/blog/chicken-legs-in-lemon-basil-mustard-sauce
x x x x x x x x x
http://www.f00die.com/2008/06/17/hobo-potatoes-w-arugula/
x x x x x
http://www.todayonpei.com/?p=5420
x x x
</pre>

(*) well, more of them, I skipped some WordPress Blogs since they all came from the same Plugin. But as the feature set of the Plugin continues to grow it doesn't make much sense to investigate them too thoroughly now unless you want to take into account which version of the plugin was used exactly etc etc - an undertaking I'm not really up to ;-)

(**) I felt quite bad when I saw that a lot of them used the pre-0.2 version with "title", "method" etc but I really don't know what I could do about it now (or then, too). I guess these decisions are made and the pain will diminish over time (cough).
--[[User:ThomasLoertsch|ThomasLoertsch]] 17:36, 17 June 2009 (UTC)
</div>
</div>

<div class="hentry">
{{OpenIssue}} 2009-07-01 raised by [[User:BenWard|BenWard]]
<div class="entry-content discussion issues">
* Reconsidering semantic of <code>published</code> over ‘<code>created</code>’. I think the reuse of <code>published</code> from [[hAtom]] may be incorrect. Given its use in hAtom, <code>published</code> represents the date and time that the content was originally published to the page. In the case of a recipe, it seems that you would instead want to represent the date that the recipe was authored/created, which is subtly different. The publication of a recipe on a web page is something that should be done with hAtom itself (publishing an <code>hEntry</code> that contains the recipe), but the recipe itself would contain the date that ''the recipe itself'' was created. e.g. <samp>I came up with this recipe for mashed potato in last summer</samp>. I'm totally open to ideas about this, but my feeling is that it's unnecessary to represent the publication date since that should be represented by a complete hAtom entry. Do we think that <code>created</code> as described here falls inside the 80:20?
** I agree with your interpretation of "published" versus "created". "published" is not used very often on it's own (see above) and I'm sure "created" would be used much less so - because it often is very difficult to determine when a recipe was created, when it was modified enough to count as newly created, from where (and when) it originated etc. IMO "published" MAY be out of the 80:20, but "created" certainly IS. You raise a point though that I'm thinking heavily about right now. I'm pondering if it would be wise to move most of the properties that are currently marked as "experimental" out of the draft and refer to them only (but explicitly) as possibly useful additions to a hRecipe. I would then add hReview as well and, from the 'experimental' properties, only leave "Nutrition" within the property set of hRecipe. But I need to think about that a little more. Anyway: I think your point is valid but should be part of a broader approach. --[[User:ThomasLoertsch|ThomasLoertsch]] 15:09, 2 July 2009 (UTC)
</div>
</div>

<div class="hentry">{{OpenIssue}}
2010-04-28 raised by [[User:Phae|Phae]]<div class="entry-content discussion issues">* Describing variable durations of preparation time..
BBC food has a problem whereby they'd like to show duration of preperation time with a minimum/maximum value. In plain english : "This recipe takes between 10 and 30 minutes to prepare". Google Rich Snippets provides a mechanism to show min/max in prepTime (although at the moment their visual preview is failing to accurately display these values) - how could we make it easier to specify min/max duration values in hRecipe? Reuse of duration is available, but is that sufficiant? ISO time has been recommended for use, but this kind of value is not an interval of time.

</div>
</div>

== resolved issues ==
<div class="vevent">
* {{ResolvedIssue}} 2008-12-27 raised by [[User:Tantek|Tantek Çelik]]
<div class="description">
*# '''author is re-used from hAtom not hCard'''. minor issue. the "author" property is actually re-used from [[hAtom]] rather than hCard - hCard has no such property.
*#* Yikes! Corrected... [[User:ThomasLoertsch|ThomasLoertsch]] 17:52, 6 January 2009 (UTC)
</div>
</div>

<div class="vevent">
* {{ResolvedIssue}}2008-01-17 raised by [[User:Yde|Yde]]
<div class="description">
* '''method'''. Would it make sense to [[reuse]] [[hreview|hReview's]] "description" instead of hRecipe's "method" or is this stretching the semantics too far?
** I just discovered that hCalender uses "method", and with totally different semantics. So I guess we MUST change it. I'm not very happy with "description" though - that's a very unspecific term. Maybe "instructions", or "steps", or "preparation" , or "procedure"? They are all 'available'. I like "instructions" most, but since I'm not a native speaker I'm hesitant. Maybe the semantics are too different? Maybe "preparation" is better since we already almost have it (or had it - see the discussion about "preparation-time" -> "duration" above)? [[User:ThomasLoertsch|ThomasLoertsch]] 12:24, 21 January 2009 (UTC)
** Since no further comments surfaced I'll change the property name to "instructions". I think it's a fairly unambiguous name which also can easily be reused in other formats. [[User:ThomasLoertsch|ThomasLoertsch]] 14:30, 2 Febuary 2009 (UTC)
</div>
</div>

<div class="vevent">
* {{ResolvedIssue}} 2008-12-27 raised by [[User:Tantek|Tantek Çelik]]
<div class="description discussion issues">
# '''Unnecessary recipe prefixing of summary property.''' Note: this is a re-opening of an issue from [[recipe-issues]]. The usage of summary in recipes appears to be very similar to that used for events. Rephrased, insufficient (if any?) evidence has been provided that summary means anything "special" enough (distinguishing it from the generic term "summary" as used in microformats) in the context of recipes to merit prefixing and thus a new property.
#* proposed resolution: Re-use generic "summary" property rather than introducing a recipe microformat scoped "recipe-summary" property.
#* I agree principally but there are different "summary"s around: The [[hReview]]-Draft specifies a summary as "This optional field serves as a title for the review itself" while the [[hCalendar]] Draft refers to RFC 2445 which defines summary as "This property defines a short summary or subject for the calendar component". I certainly agree more with the semantics from RFC 2445 but referring to either of the two doesn't make much sense right now. Since you are editor of both hReview and hCalendar maybe you can clarify the subject? If hReview would be aligned with RFC 2445 then I would promote dropping the prefix.[[User:ThomasLoertsch|ThomasLoertsch]] 17:52, 6 January 2009 (UTC)
#** Agreed, the definitions of "summary" across hCalendar and hReview could be better converged. Please add this as an issue to both [[hcalendar-issues]] and [[hreview-issues]] and I'll follow-up there accordingly. Given that is the path forward, let's fix this immediately in hRecipe now that the issue (and resolution) has been captured. [[User:Tantek|Tantek]] 20:54, 15 January 2009 (UTC)
#*** Will change "recipe-summary" to "summary" as defined in hCalender/RFC2445. [[User:ThomasLoertsch|ThomasLoertsch]] 15:00, 16 January 2009 (UTC)
</div>
</div>

<div class="vevent">
* {{ResolvedIssue}} 2008-12-27 raised by [[User:Tantek|Tantek Çelik]]
<div class="description discussion issues">
# '''preparation-time could re-use duration instead''' - it appears that the "preparation-time" semantic basically means the "duration" of the recipe, and thus could re-use that property from [[hCalendar]] rather than introducing a new property name.
#* proposed resolution: change "preparation-time" to "duration" and note re-use from [[hCalendar]] - or at least document how preparation-time is a different enough semantic from "duration" to justify the introduction of a new term.
#* One difference is that hCalendar ''duration'' is a singular property whereas hRecipe's ''preparation-time'' is plural. Also, ''preparation-time'' will often (typically) use value+note subproperties, while ''duration'' will usually be an ISO 8601 duration. [[User:TobyInk|TobyInk]] 20:32, 29 December 2008 (UTC)
#** Plurality is a contextual aspect and does not alter the semantic of the underlying property, thus is insufficient justification for introducing a new term. We do not use duplicates of each property in a singular and plural form. [[User:Tantek|Tantek]] 20:54, 15 January 2009 (UTC)
#** Syntax differences (value+note vs ISO 8601) are also insufficient to justify the introduction of a new property for the same semantic. Rather, it is better to expand the syntax of the existing property, e.g. perhaps using the [[value-excerption-pattern]] and to note that explicitly. [[User:Tantek|Tantek]] 20:54, 15 January 2009 (UTC)
#*** Semantically the reuse of "duration" is okay. RFC 2445 permits multiple duration values "if the property permits" so that should be fine too. If the syntactic differences can be worked out the way Tantek suggests above than it's okay with me to re-use "duration". I'm just not sure if it helps usability to overload properties in such a way but that ay be another discussion on it's own. [[User:ThomasLoertsch|ThomasLoertsch]] 15:00, 16 January 2009 (UTC)
#** The observation that preparation-time uses a nested "note" subproperty may actually reveal a problem with that approach itself, that is, perhaps instead of "preparation-time" with "value" and "note" subproperties, it may be better to refactor it as a "preparation" (an act thereof) with "duration" and "note" subproperties. [[User:Tantek|Tantek]] 20:54, 15 January 2009 (UTC)
#*** Removed the sub-property "note" from the v_0.2 draft format since I now agree that it looks a little overengineered. [[User:ThomasLoertsch|ThomasLoertsch]] 12:47, 22 January 2009 (UTC)
</div>
</div>

<div class="vevent">
* {{ResolvedIssue}} '''issues too long''' 2009-01-22 raised by [[User:ThomasLoertsch|ThomasLoertsch]]
<div class="description">
As threatened 2 weeks ago I heavily re-edited this page because discussions had become a little frayed (and heated at soem points). Have a look at the [http://microformats.org/wiki/index.php?title=hrecipe-issues&oldid=37788 previous version] for the full debate and feel free to re-edit this page if you find that I axed it too much. [[User:ThomasLoertsch|ThomasLoertsch]] 14:47, 2 February 2009 (UTC)
</div>
</div>

<div class="vevent">
* {{ResolvedIssue}} '''new draft'''2009-01-22 raised by [[User:ThomasLoertsch|ThomasLoertsch]]
<div class="description">
* The following is a proposal for draft 0.2, reflecting the issues discussed so far. "recipe-title" is replaced with "fn" from hCard (although I'm not convinced that this is a good idea), "recipe-summary" with "summary", "num" and "unit" from the unfinished 'measure' with "type" and "value" from 'hCard' (i only recently discovered them...), "method" (wihch is already used by [[hCalendar]] with "instructions", "preparation-time" with "duration". Two "note"s are deleted for brevity. "summary", "nutrition", "author", "published" and "photo" are marked as 'experimental', meaning that they may be removed from future drafts or the final specification, depending on experience and feedback from implementations :
</div>

=== '''hrecipe'''. Proposal for Draft 0.2 ===

* '''fn'''. the name of the recipe. required. text. re-used from [[hCard]]
* '''ingredient''' required. 1 or more. text with optional valid (x)HTML markup.
** '''value''' and '''type'''. optional. re-used from [[hCard]].
* '''yield'''. optional. text.
* '''instructions'''. optional. text with optional valid (x)HTML markup.
* '''duration'''. optional. 1 or more. text (see [[ISO-31-1]] duration brainstorming). re-used from [[hCalendar]].
* '''''summary'''''. optional. text. re-used from [[hCalendar]]. [ ''experimental'' ]
* '''''nutrition'''''. optional. 1 or more. [ ''experimental'' ].
** '''''value''''' and '''''type'''''. optional. re-used from [[hCard]]. [ ''experimental'' ].
* '''''author'''''. optional. 1 or more. re-used from [[hAtom]] using [[hCard]]. [ ''experimental'' ].
* '''''published'''''. optional. re-used from [[hAtom]]. [ ''experimental'' ].
* '''''photo'''''. optional. 1 or more. using any element containing a URL, such as IMG. re-used from [[hCard]]. [ ''experimental'' ].
* '''''tag'''''. optional. 1 or more. [ ''experimental'' ].
--[[User:ThomasLoertsch|ThomasLoertsch]] 11:01, 10 February 2009 (UTC)

** The above seems to use ''value'' very differently to other microformats. In other microformats it's used for [[value-class-pattern|value excerpting]] in most properties (i.e. the ''value'' class is used to indicate which text should be parsed with the rest being ignored); and in a handful of particular properties (e.g. hCard tel, email, adr, label) it's used in the ''value''+''type'' combination to indicate the main text that should be parsed while ''type'' refines the meaning of the property. In a recipe ingredient, the main idea to get across would be the ingredient itself (e.g. eggs, whisky, cardamom), so if ''value'' were to be used, you'd expect it to be more like this: <code><li class="ingredient">2 eggs, lightly whisked</li></code>. Wrapping <code>class=value</code> around the '2' is fairly at odds with how that class is used in other microformats. [[User:TobyInk|TobyInk]] 15:44, 25 March 2010 (UTC)
*** Suggestion: remove these subproperties from the ingredient and nutrition properties. [[User:TobyInk|TobyInk]] 15:44, 25 March 2010 (UTC)
</div>
**** +1 I concur with Toby's analysis and recommendation. [[User:Tantek|Tantek]] 17:30, 25 March 2010 (UTC)

== closed issues ==

<div class="vevent">
* {{ClosedIssue}} 2008-12-27 raised by [[User:Tantek|Tantek Çelik]] in the context of issue '''Too many properties'''
<div class="description discussion issues">
# '''Drop "recipe-title".''' In reviewing the examples, few (if any?) include *both* a title and a summary, and in practice the semantics of usage in the context of recipes appears to be virtually indistinguishable. Therefore we don't need both, and following in the pattern provided by [[hCalendar]] (which got it from [[RFC2445]]), we should keep the more generic concept of a "summary" and drop the concept of "title" from hRecipe.
#* I tend to agree. There are definitely use cases for both "recipe-title/title/fn" and "recipe-summary/summary" - e.g. "[http://www.simonwheatley.co.uk/2006/03/26/a-moroccan-ish-casserole/ A Moroccan-ish Casserole]" sounds more like a summary while "[http://blog.bumblepuppy.org.uk/2006/10/05/spaghetti-primavera/ Spaghetti primavera]" is the full name or the title of the recipe. But the problem is, they would serve the same purpose. [[User:Yde|Yde]] 10:07, 17 January 2009 (UTC)
#** Title and summary are different things and they are used differently in the real world. The examples you give are both names/titles/labels/headings, although more or less descriptive. They are short, memorable and make the thing adressable by humans. A summary can be (and mostly is) much longer and serves a different purpose: it describes essential properties of the object at hand, eg: "this is easy and fast to prepare, but still looks impressive", "easy, tasty, fast, vegan, good on cold days" or "the kids loved this last summer, but the ingredients can be hard to get" or "whenever i cook this i start to dream of ..." [[User:ThomasLoertsch|ThomasLoertsch]] 14:25, 20 January 2009 (UTC)
#*** Right, on second thought, I believe "title/name" and "summary" are different things. [[User:Yde|Yde]] 11:22, 23 January 2009 (UTC)
#* The term "title" has been so horribly overloaded across formats, vocabularies that it is nearly meaningless and for that reason should be avoided in any/all format efforts, preferring instead something more semantically specific such as "fn" (meaning full/formatted name of an item) or "summary" (when items are labeled more often with a short description/explanation rather than a name). [[User:Tantek|Tantek]] 20:54, 15 January 2009 (UTC)
#** Synonyms and homonyms are part of the real world - we have to cope with them. Also the word "title" is not horribly overloaded, you're exaggerating here. It just happened that hCard were the first to use it, and in a way that's empirically much less important then the use of "title" as the heading of a resource. Still the real problem is that Microformats have only one namespace and no resolution mechanism for conflicts like this, beside "first come first served". [[User:ThomasLoertsch|ThomasLoertsch]] 15:00, 16 January 2009 (UTC)
#** Maybe it would be better to make a clear cut with some of the sins of the past and deprecate some terms in hCard / hCalendar[[User:ThomasLoertsch|ThomasLoertsch]] 15:30, 3 February 2009 (UTC)
#* "fn" is [[existing-classes|defined]] as "the name of the object" which is pretty much what "recipe-title" means right now. So, whether we chose to keep this property, summary, or both, renaming "recipe-title" to "fn" would make sense. [[User:Yde|Yde]] 23:03, 16 January 2009 (UTC)
#** the definition of "fn" in [[existing-classes|existing classes]] is maybe a little too short. "fn" is defined in hCard which is a reformulation of RFC 2462, which says: "Type name:FN - Type purpose: To specify the formatted text corresponding to the name of the object the vCard represents. -Type special notes: This type is based on the semantics of the X.520 Common Name attribute. The property MUST be present in the vCard object. - Type example: 'FN:Mr. John Q. Public\, Esq.'" (http://www.ietf.org/rfc/rfc2426.txt, on page 8). That clearly means a name of a person or an institution. Institution equals a juristical person, so "fn" semantically boils down to 'name of a person'. I wouldn't use that for every object. [[User:ThomasLoertsch|ThomasLoertsch]] 14:03, 20 January 2009 (UTC)
#*** Thanks for the clarification. "fn" is definitely not a good idea. [[User:Yde|Yde]] 10:00, 23 January 2009 (UTC)
#*** <code>fn</code> is already reused more generically in hAudio, hReview and hListing (for items). The definition of use within microformats has already been adapted from the strict vcard interpretation in prior work. --[[User:BenWard|BenWard]] 23:04, 27 January 2009 (UTC)
#**** I see. I can't help but thinking: what a mess... What's the family name of a recipe, audio-recording or list-entry? What's the point of re-using a semantically totally void two-letter-acronym, when it doesn't even fit very well? What's the point of reusing an element when I have to lookup the meaning of it every time anyway? [[User:ThomasLoertsch|ThomasLoertsch]] 00:48, 28 January 2009 (UTC)
#***** <code>fn</code> is ''formatted''-name, not ‘family’. ‘Name as presented’, ‘display name’. I agree that <code>fn</code> takes a double glance when you're learning, but it's there and the reuse in other specs is consistent; there's a much stronger author benefit in building on common equivalent-semantic vocabulary than introducing synonyms, which I think will cause more confusion. Better to have a strong spec with common vocabulary than introduce duplication. I'll keep in mind that we should better emphasise the expansion of <code>fn</code> in all specs for benefit of new authors. I can see how ‘family name’ is a muddle too easily made in hCard. --[[User:BenWard|BenWard]] 07:01, 28 January 2009 (UTC)
#****** I was referring to the fact that a name of a natural or juridical person is semantically quite different to the name of an object. Other things like the opacity of the two-letter-code "fn" are indeed problematic too but not my main issue here. That vCard-legacy seems to be lurking around every corner. Why not make a clear cut and deprecate the problematic parts like "title" and "fn"? The approach to rather overload the semantics (and the property-constraints) just to keep element-count low only takes that far. In the end it hinders usability instead of improving it. I think [[reuse]] and [[naming-principles]] don't strike the right balance in that respect. [[User:ThomasLoertsch|ThomasLoertsch]] 11:45, 28 January 2009 (UTC)
#* why not define a property "name"?! From my understanding of the english language (I'm not a native speaker) "name" is semantically generic enough to serve as a substitute for "title". Defining it rather broadly as "designation or title or denominator or heading of an item" would make it easily reusable. Plus we would have to explicitely discourage it's use for naming real or juristical persons and point to "fn" instead. [[User:ThomasLoertsch|ThomasLoertsch]] 12:21, 21 January 2009 (UTC)
#** Hmmm. I would really like to get feedback on this... Again my argumentation:
#*** <code>title</code> would be the best solution but is already "taken". Depercating some of hCalenders sins would be the best solution but seems out of reach so far.
#*** <code>heading</code> would be a possible solution either but seems more suited for prose
#*** <code>name</code> gets the semantics quite well, especially in the case of recipes which are more a "thing" or abstract conceptualization than a work of literature/science/prose
#*** <code>fn</code> with it's subproperties is geared towards natural and juristical persons, which are quite different from things and concepts. Also semantics of the term "fn" are rather opaque, even misleading, which hinder it's usability.
#** Therefor I'd love "title", could live very well with "name", could live still well with "heading" and would sleep bad (but sleep) with "fn". [[User:ThomasLoertsch|ThomasLoertsch]] 16:30, 2 Febuary 2009 (UTC)
#** Okay, since there's no response I bow my head to "fn". But it speaks for itself that it's the only tag that has to be explained in the schema. [[User:ThomasLoertsch|ThomasLoertsch]] 11:15, 10 February 2009 (UTC)
</div>
</div>

===template===
{{issues-format}}

==related pages==
* [[hRecipe]]
* [[hrecipe-feedback|hRecipe feedback]] - general feedback regarding hRecipe

Per the microformats [[process]], the [[recipe]] effort developed
* [[recipe-examples]]
* [[recipe-formats]]
* [[recipe-brainstorming]] (see also [[recipe-brainstorming-archive]])
* [[recipe-issues]]
towards the development of this draft.

species

2010-04-26T10:48:23Z

Phae: /* Examples in the wild */ added bbc wildlife finder

=Species=

:'''For the latest ideas, and to make comments, please see [[species-brainstorming]].'''

:'''Note: the original name of the proposed microformat, "species", is likely to change, probably to "biota" or "taxon". The former has been retained here, to avoid having to make many repetitive and perhaps redundant edits'''

:'''The [http://www.kaply.com/weblog/2007/02/16/operator-07a-is-available/ beta of Operator] (0.7a) detects ''Species''. [http://www.westmidlandbirdclub.com/records/lists-2004.htm A test page is available]. Work on both continues!'''

==Introduction==

People use the vernacular AND taxonomic names of species in everyday speech and writing - just read or watch any populist gardening magazine or television programme.

*Consider this list: "'''Blackbird'''", "'''poodle'''", "'''T Rex'''", "'''potato'''", "'''French Marigold'''", "'''Wisteria'''", "'''E. Coli'''", "'''HIV'''", "'''Rubella'''" and "'''human being'''".

:"'''T Rex'''" is "''Tyrannosaurus rex''"; "'''E. Coli'''" is "''Escherichia coli''"; "'''HIV'''" is "''Human immunodeficiency virus''" and "'''Rubella'''" is "''Rubella virus''". All are the taxonomic (or scientific) names of unique species.

:"'''''Wisteria'''''" is a taxonomic genus.

:"'''Blackbird'''"; "'''poodle'''"; "'''potato'''"; "'''French Marigold'''" and "'''human being'''" (arguments about Neanderthals not withstanding) are vernacular (or common) names, but still refer to individual species.

*The scientific naming of organisms is a part of [http://www.calacademy.org/research/informatics/sblum/pub/biodiv_informatics.html biodiversity informatics] - "the application of information technology to the domain of biodiversity".

*The proposal aligns with [http://www.ted.com/tedprize/2007/wilson.cfm E.O Wilson's wish]:

<blockquote>...that we will work together to help create the key tool that we need to inspire preservation of Earth's biodiversity: the Encyclopedia of Life [...] an encyclopedia that lives on the Internet, with an ever-evolving page for every species [and which]
does not duplicate existing efforts, but instead incorporates them through linking [with a] search technology that can aggregate existing biological information and make it easily accessible.</blockquote>

*As long ago as April 1998 on [http://www.w3.org/MarkUp/future/papers/rothenburg-19980412.html Robert Rothenburg's paper on Dictionaries] (''Note 4'') said:

<blockquote>What is missing [from HTML] is an element for marking up "proper names" (names of people, geographic locations, institutions, or even '''scientific names such as genus/species''').</blockquote>

:It's interesting that microformats have given us the first three missing items - and we're now debating the fourth!

==Proposal==
Imagine viewing a web page with a reference to a species - and being able to use an add-on to you browser to be taken directly to information about that species, on, say, Wikipedia, or Wikispecies, or Google Images, or another site, such as in an academic database, of your choosing.

Your software would automatically know to search site A if the scientific name referred to a moth, site B for a bird, and site C for a plant - and you could set your preferences as to which sites those were to be, and in which order two or more were to be searched (e.g. for moths, try [http://ukmoths.org.uk/ UK Moths] first, if not found try [http://www.nhm.ac.uk/research-curation/projects/lepindex/index.html The Global Lepidoptera Names Index]).

Or supposing someone writes a long, chronologically-ordered web page about all the birds, insects, mammals and plants they saw on a wildlife safari, with lots of prose description about the paces where they saw them and the people they were with, but you want to extract a list of species, sorted into alphabetical order within taxonomic class (birds first, then insects then...) or in taxonomic order.

Those are just two of the things a "species" microformat might do for you.

Your software, or a search engine, would be able to differentiate between a pages discussing HMS Beagle, the ship, and a Beagle dog; or birds that fly as opposed to a slang term for women.

Another benefit would be that user-agents could be instructed to treat text marked up in this way as not being in the base language of the document or element in which they occur - pronunciation should be as for Latin, they should not be translated (e.g. where a component word happens also to be a valid word in that language, such as the genus '''''Colon''''', '''''Circus''' cyaneus'', ''Hesperia '''comma''''', or anything with ''major'' or ''minor'' on an English-language page) and should not be spell-checked, or be spell-checked with a specialised dictionary (a need identified in this [http://www.alvestrand.no/pipermail/ietf-languages/2003-February/000590.html 2003 ietf-languages discussion of language values for taxonomic names]).

A further benefit the species microformat would bring is in the enriching and enhancement of species checklists, which are commonly found on the web. Broadly speaking, a species checklist is a list of taxa, usually for a particular group of similar organisms such as birds or vascular plants, found within a particular geographical region (a country, [http://www.westmidlandbirdclub.com/records/lists.htm a region], a county, or a specific site, large or small). A typical example of a species checklist is the [http://www.coleopterist.org.uk/checklist.htm Checklist of Beetles of the British Isles] which, as the name suggests, lists beetles known to be found within the British Isles. A [http://www.google.com/search?q=species+checklist Google Search for "species checklist"] will reveal many other such examples. Species checklists are presented in a broadly consistent manner but are usually unable to be parsed and utilised by computers due to the lack of a common standard for marking them up in HTML. The species microformat would provide that common standard. A fully microformat enabled checklist would be parsable by computers and thus would provide developers with a means by which to aggregate and otherwise make use of this invaluable content beyond the current, rather limited, use of simple online viewing.

A specific example of checklist use might be in enabling [http://www.aditsite.co.uk/html/choosing_recording_software.html biological recording software] to parse and aggregate checklists in order to include them in their own species dictionaries. Typically there are waits of many months or even years while humans collate checklist changes manually for inclusion in recording software; automated checklist parsing and aggregation would greatly expedite and increase the efficiencies of this process.

==Existing taxonomies==
The proposal respects all existing biological taxonomies, and is not intended to change or supplant any of them - it is intended merely to provide webmasters (from personal hobby sites to major academic databases; from news outlets to retail organisations) with a method of either:

# marking-up a taxonomical name (or taxon-common name pair) in such a way that its components can be recognised by computers '''or'''
# marking up a common name, so as to associate with it a taxonomical name, in such a way that the latter's components can be recognised by computers.

==Embedding within other microformats==
The proposed [[plant]] microformat (with care regime, supplier, etc.), [[hlisting]], [[recipe]] or [[hReview]] (and possibly others) could contain a scientific name microformat, in the same way that an [[hCalendar]] can contain an [[hCard]].

See also: [[species-brainstorming#Future development]]

==References==

====General taxonomy====
* [http://en.wikipedia.org/wiki/Scientific_classification Wikipedia: Scientific classification]
**[http://en.wikipedia.org/wiki/Binomial_nomenclature Wikipedia: Binomial nomenclature]
**[http://en.wikipedia.org/wiki/Binomen Wikipedia: Binomen]
**[http://en.wikipedia.org/wiki/Trinomial_nomenclature Wikipedia: Trinomial nomenclature]
**[http://en.wikipedia.org/wiki/Trinomen Wikipedia: Trinomen]
**[http://en.wikipedia.org/wiki/Taxon Wikipedia: Taxon]
**[http://en.wikipedia.org/wiki/Rank_%28zoology%29 Wikipedia: Rank (zoology)]
**[http://en.wikipedia.org/wiki/Rank_%28botany%29 Wikipedia: Rank (botany)]
**[http://en.wikipedia.org/wiki/Cultivar Wikipedia: Cultivars]
**[http://en.wikipedia.org/wiki/Variety_%28biology%29 Wikipedia: Varieties]
**[http://en.wikipedia.org/wiki/Subvariety Wikipedia: Sub-varieties]
**[http://en.wikipedia.org/wiki/Form_%28botany%29 Wikipedia: forms]
**[http://en.wikipedia.org/wiki/Synonym_%28taxonomy%29 Wikipedia: Synonyms]
**[http://en.wikipedia.org/wiki/Wikipedia:How_to_read_a_taxobox How to read a taxobox]

====Taxonomic codes====
* [http://en.wikipedia.org/wiki/Nomenclature_Codes Wikipedia: Nomenclature Codes]
* [http://www.iczn.org/ http://www.iczn.org/ International Commission on Zoological Nomenclature] (ICZN)
** [http://en.wikipedia.org/wiki/International_Code_of_Zoological_Nomenclature Wikipedia: International Code of Zoological Nomenclature]
**[http://en.wikipedia.org/wiki/International_Commission_on_Zoological_Nomenclature Wikipedia: International Commission on Zoological Nomenclature]
* [http://ibot.sav.sk/icbn/main.htm International Code of Botanical Nomenclature] (ICBN)
** [http://en.wikipedia.org/wiki/International_Code_of_Botanical_Nomenclature Wikipedia: International Code of Botanical Nomenclature]
* [http://www.the-icsp.org/ International Committee on Systematics of Prokaryotes] (ICSP)
**[http://en.wikipedia.org/wiki/International_Code_of_Nomenclature_of_Bacteria Wikipedia: International Code of Nomenclature of Bacteria] (ICNB)
* [http://www.ictvonline.org/ International Committee on Taxonomy of Viruses]
**[http://en.wikipedia.org/wiki/International_Committee_on_Taxonomy_of_Viruses Wikipedia: International Committee on Taxonomy of Viruses]

====Other references====

*[http://www.rhs.org.uk/rhsplantfinder/plantnaming.asp RHS Plant Finder: The naming of plants]
*[http://www.ishs.org/sci/icracpco.htm International Code of Nomenclature for Cultivated Plants]
*[http://www.tdwg.org/index.html Taxonomic Databases Working Group]
*[http://www.hortax.org.uk/ Hortax] - The Names of Garden Plants
*[http://www.bgbm.fu-berlin.de/iapt/nomenclature/code/SaintLouis/0000St.Luistitle.htm www.bgbm.fu-berlin.de/iapt/nomenclature/code/SaintLouis/0000St.Luistitle.htm]
*[http://species.wikimedia.org/wiki/Main_Page WikiSpecies]
*[http://en.wiktionary.org/wiki/taxonomy Wiktionary: Taxonomy]
*[http://jbi.nhm.ku.edu/index.php/jbi/article/view/25 Biodiversity Informatics: Taxonomic names, metadata, and the Semantic Web]
*[http://en.wikipedia.org/wiki/Virus_classification Wikipedia: Virus classification]

==Contributors & Supporters==
*[[User:AndyMabbett|Andy Mabbett]] (proponent)
*[[User:RogerHyam|Roger Hyam]] (interested party?)
*[[User:SXBRC|Charles Roper]], [http://www.sxbrc.org.uk/ Sussex Biodiversity Record Centre] (proponent)
*[[User:SteveMcBill|Steve McWilliam]], [http://www.rECOrd-LRC.co.uk/ rECOrd - The Biodiversity Information System for the Cheshire region] (supporter)
*[[User:KierenPitts|Kieren Pitts]], [http://www.ilrt.bris.ac.uk/ ILRT - Institute for Learning and Research Technology] and the [http://www.amentsoc.org/ Amateur Entomologists' Society] (supporter)
*[[User:CyndyParr|Cyndy Parr]], [http://spire.umbc.edu Spire project] (interested party)
*[[User:AnimalDiversity|Animal Diversity Web]], [http://animaldiversity.org] (interested party)
*[[User:Christoph|Christoph Champ]], [http://www.christophchamp.com/] (supporter with a background in biochemistry, biophysics, and bioinformatics)
*[[User:David Stang|David Stang]], [http://ZipcodeZoo.com] (interested party)

==See also==
Here's some work-in-progress:
{{species}}
*[https://addons.mozilla.org/firefox/169/ Biobar] - A customisable Firefox Extension providing a toolbar and content menu options for browsing biological data and databases, which shows what a user-agent could do, with data extracted from a species microformat

==Examples in the wild==

* An example use of the species microformat on the [http://www.amentsoc.org/insects/fact-files/orders/hymenoptera-parasitica.html Amateur Entomologists' Society Web site].
*Social network for gardeners marking up plant names with microformats [http://www.growsonyou.com/plant/Cosmos_bipinnatus Grows on You].
*A "proof-of-concept" example, with binomial and sub-family, but no other ranks, has been added to the Wikispecies entry for [http://species.wikimedia.org/wiki/Glaucidium_sanchezi Glaucidium sanchezi]; and to its subfamily, [http://species.wikimedia.org/wiki/Surniinae Surniinae]. See [http://species.wikimedia.org/wiki/Wikispecies:Microformat Wikispecies:Microformat] for related discussion.
*The current "[[species-brainstorming#Straw man proposal|straw man]]" for the Species microformat has been deployed, in part, on Wikipedia. '''''All''''' Wikipedia articles with "[http://en.wikipedia.org/wiki/Template:Taxobox taxoboxes]" (information panels on living things; and there are '''37,140''' as at the time of posting) now emit a species microformat. For example [http://en.wikipedia.org/wiki/Southern_Tamandua Southern_Tamandua] (a species) and [http://en.wikipedia.org/wiki/Anteater Anteater] (a family of species).
* A [http://www.westmidlandbirdclub.com/records/lists-2004.htm West Midland Bird Club test page] is available.
* [http://www.bbc.co.uk/nature/family/Megapode BBC Wildlife Finder]

==Implementations==
*[https://addons.mozilla.org/firefox/4106/ Operator] has a user-script for parsing ''Species''.
*[http://buzzword.org.uk/cognition/ Cognition] has an [http://buzzword.org.uk/cognition/uf-plus.html#species experimental implementation].

===Implementations (pending)===
*[http://www.spacefornature.co.uk/biorec/taxoncheck.htm Taxon Checker] - a software tool which, given a common name, searches for the relevant taxonomic data and outputs the selected species' details as (among other options) an HTML fragment. It is intended to provide templates for outputting such fragments with "species" microformat markup, once this proposal is implemented.
*[http://en.wikipedia.org/wiki/User:Beastie_Bot Wikpedia's Beastie Bot] can be used to update the "taxoboxes" of articles about living things/

Main Page

2010-02-18T15:54:26Z

Phae: Reverted edits by Dogbreeds0 (Talk) to last version by Tantek

<entry-title>Welcome to the microformats wiki!</entry-title>
__TOC__
Please start with the [[introduction]] page and read [[how-to-play]] before making any edits.

==Introduction==
This wiki is the central resource of the microformats community. You'll find current versions of published microformat specifications, specification drafts and publishing patterns. The wiki also hosts development resources, such as brainstorming pages for new formats and issue tracking pages for all current and in-development microformats.

== Get Started==
To get started with microformats:

* First, be familiar writing your pages and applications with semantically rich, descriptive, ‘[[posh|<abbr title="Plain Old Semantic HTML">POSH</abbr>]]’ <abbr title="HyperText Mark-up Language">HTML</abbr>.
* Learn about microformats from the [http://microformats.org/about/ about page], [http://microformats.org/ blog], [[press]], [[presentations]], [[books]], [[podcasts]], & [[screencasts]] pages.
* Take a look at established specifications such as [[hcard|hCard]] and [[hcalendar|hCalendar]], and follow the [[hcard-examples|examples]] to start publishing microformats.
* Have questions? Read the [[faq|frequently asked questions]] and see the [[glossary]] for terms and definitions. You can also post to the {{MicroformatsMailingList}}.
* Want to learn more in person? Check out microformats [[events]].

==Definition==
Microformats are small patterns of HTML to represent commonly published things like [[hcard|people]], [[hcalendar|events]], [[hatom|blog posts]], [[hreview|reviews]] and [[rel-tag|tags]] in web pages.

Microformats enable the publishing of higher fidelity information on the Web; the fastest and simplest way to provide feeds and APIs for the information in your website.

* Read more explanations of [[what-are-microformats|what microformats are]], and [[what-can-you-do-with-microformats|what you can do with them]].

== How to contribute ==
Do you want to help take microformats to the next level? You can:

* [[get-started|Get started]] by adding microformats to your website, services, and products.
* [[advocacy|Advocate]] the use of microformats on other web sites, especially those you use.
* Write a [[testimonial]].
* Do something on the [[to-do|to do list]].
* Join the [[irc|IRC Channel]] and [[mail|mailing lists]] to learn and help answer questions (read the [[mailing-lists#General_guidelines|general guidelines]] before posting).
* [[Main_Page#microformats_wiki_translations|Translate this microformats wiki into other languages]] to make microformats more accessible to readers of languages around the world.
* Before proposing any new microformats, make sure your website is [[POSH]], [[get-started|uses existing microformats]], and then read the [[process]].

This wiki has a number of enhancements to assist development and contributions to microformats. Before you start editing, see the [[wiki-2|wiki introduction page]] for instructions.

== Specifications ==
The list of current, stable [[microformats|Microformats]] open standard specifications.

* [[hcalendar|hCalendar]] - [http://microformats.org/code/hcalendar/creator hCalendar creator]
* [[hcard|hCard]] - [http://microformats.org/code/hcard/creator hCard creator]
* [[rel-license]] - [http://www.rushessay.com/custom_essay.php Essay writing]
* [[rel-nofollow]]
* [[rel-tag]]
* [[vote-links|VoteLinks]]
* [[XFN]] - [http://gmpg.org/xfn/creator XFN creator]
* [[XMDP]]
* [[xoxo|XOXO]]

''If you're tempted to try your hand at writing a microformat please read '''[[process|the process]]''' page first!''

== Drafts ==
Drafts are newer microformats, for which the specifications haven't been completed yet. Drafts are somewhat mature in the development [[process]] (see [[exploratory-discussions]] for additional efforts that are not as far along in the process). The stability of these documents cannot be guaranteed, and implementers should be prepared to keep abreast of future developments and changes. Please watch the wiki pages for updates.

* [[adr|adr]] - for marking up address information
* [[geo|geo]] - for marking up [http://en.wikipedia.org/wiki/WGS84 WGS84] geographic coordinates (latitude; longitude)
* [[hatom|hAtom]] - syndicating episodic content (e.g. weblog postings)
* [[haudio|hAudio]]
* [[hlisting|hListing]] - open, distributed listings
* [[hmedia|hMedia]] - A single media publishing format that relates to Images, Video and Audio.
* [[hnews|hNews]]
* [[hproduct|hProduct]]
* [[hrecipe|hRecipe]] - for cooking+baking recipes
* [[hresume|hResume]] - for publishing resumes and CVs
* [[hreview|hReview]] - [http://microformats.org/code/hreview/creator hReview creator]
* [[rel-directory]] - to indicate that the destination of a hyperlink is a directory listing containing an entry for the current page
* [[rel-enclosure]] - for indicating attachments (e.g. files) to download and cache
* [[rel-home]] - indicate a hyperlink to the homepage of the site
* [[rel-payment]] - indicate a payment mechanism
* [[robots-exclusion|robots exclusion]]
* [[xfolk|xFolk]]

== Design Patterns ==
{{design_patterns}} 

== Exploratory Discussions ==
See: [[exploratory-discussions]] for details of research and analysis of real-world [[examples]], existing formats, and brainstorming of possible new microformats, per the microformats [[process]].

== Examples ==
* [[examples-in-the-wild]]
* [[implementations]]
* [[zen-garden]]

== Resources ==
See [[resources]].

== User centric development ==
*[[user-interface]]
*[[data-portability]]
*[[social-network-portability]]

== Shared work areas ==
* [[to-do]]
* [[templates]]
* [http://microformats.org/wiki/delete pages for deletion] 
* [[Special:Specialpages|"Special" wiki pages]]
* [[year-in-review]]

== Tools, test cases, additional research ==
The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting [[tools|tools and services]] that need to process more than one microformat. That section is intended for editors, [[parsers]], [[validators]], test cases, and other information relevant across multiple microformats.

== Microformats wiki translations ==
You may read and edit microformats articles in many other languages:

* languages with over 100 articles
** [[Main_Page-fr|Français (French)]] {{UpdateMarker-fr}}
* languages with over 10 articles
** [[Main_Page-pt-br|Português (Brazilian Portuguese)]]
** [[Main_Page-ja|日本語 (Japanese)]]
** [[Main_Page-ru|Русский (Russian)]]
* languages with over 2 articles
** [[Main_Page-cs|Česky (Czech)]] {{NewMarker}}
** [[Main_Page-de|Deutsch (German)]]
** [[Main_Page-es|Español (Spanish)]]
** [[Main_Page-gl|Galego (Galician)]] {{NewMarker}}
** [[Main_Page-pl|Polski (Polish)]]
** [[Main_Page-ro|Română (Romanian)]] {{NewMarker}}
** [[Main_Page-zh|汉语 (Chinese)]]
** [[Main_Page-id|Indonesia (Bahasa Indonesia)]] {{NewMarker}}
* languages just started
** [[Main_Page-ar|العربية (Arabic)]]
** [[Main_Page-th|ภาษาไทย (Thai)]]
** [[Main_Page-it|Italiano (Italian)]] {{NewMarker}}
** [[Main_Page-ko|한국어 (Korean)]] {{NewMarker}}
* elsewhere
**[http://en.wikipedia.org/wiki/Microformat Wikipedia's article on microformats] has been translated into a number of languages.

See also [[other-languages]], and [[how-to-start-new-translation|how-to-start-a-new-translation]].

microformateers

2009-09-28T15:23:00Z

Phae: added sig

<entry-title>Microformateers</entry-title>

[http://twitter.com/microformateers Microformateers] is a Twitter account providing quick answers to people's questions about microformats. Twitter is full of people with short queries about syntax, or remarking upon things they've read about microformats. Microformats.org already runs the [http://twitter.com/microformats @microformats] account for pushing news and announcements, but the microformateers effort is about responding.

==What is this?==

Microformateers is a single Twitter account, shared between a number of individual contributors. They monitor Twitter searches for mentions of microformats and related terms, and respond directly and publicly to people's lazy-web questions, ideally within 140 characters. Where longer code examples are required, code snippets areposted to [http://gist.github.com gist].

==Who are the microformateers?==

<div class="vcard">
Because of the mechanics of Twitter (a single account, shared with a single password) it is not possible for the Microformateers account to be open to all. '''The following agents are currently ‘on duty’''':

<div class="agent vcard">
===Frances Berriman (^FB)===

https://s3.amazonaws.com/twitter_production/profile_images/58225171/17464024_N00_normal_bigger.jpg

* http://twitter.com/phae
* [[User:Phae]]
</div>

<div class="agent vcard">
===Jeremy Keith (^??)===

https://s3.amazonaws.com/twitter_production/profile_images/65971001/avatar_bigger.jpg

* http://twitter.com/adactio
* [[User:Adactio]]
</div>

<div class="agent vcard">
===Drew McLellan (^??)===

https://s3.amazonaws.com/twitter_production/profile_images/124177936/peek_bigger.jpg

* http://twitter.com/drewm
* [[User:DrewMcLellan]]
</div>

<div class="agent vcard">
===Ben Ward (^BW)===

https://s3.amazonaws.com/twitter_production/profile_images/150824912/2009-200_bigger.jpg

* http://twitter.com/benward
* [[User:BenWard]]
</div>

</div> 

==Response Process==

* Microformateers is a single Twitter identity shared between an appropriate number of trusted individuals
* When you have a free moment or the mood takes you, monitor searches for microformats terms (there's one saved in the account already)
* When you find a question to be answered, respond using the [http://twitter.com/microformateers @microformateers account]
* If you need to provide code, stick it on [http://gist.github.com gist.github.com] (or similar pastebin service) and link to it. Gist is good though, as it ties into the Github community as well.
* When you answer someone's question, add the tweet to the [http://twitter.com/microformateers/favorites @microformateers’ favorites], that we avoid inundating questioners with duplicate answers. (Most quality Twitter clients, as well as the Twitter website itself, indicate which tweets you have ‘faved’ inline.)
* Where possible, save 3 characters to sign the tweet with a <kbd>^XX</kbd>, using your initials, so people can reference you personally as well. (e.g. ^BW, ^T, ^JK, ^FB… something identifiabley.) People can refer to this wiki page to look-up the individual. <code>^AB</code> is an existing convention on Twitter for this purpose, used by software such as Co-Tweet.

==Interested List==

If you're interested in becoming an agent for the microformateers, please add your name to the list below. There are a couple of constraints on this system: First is trust and security, simply because Twitter's account model requires sharing the same master password for the @microformateers account between all participants; we have to be conservative with proliferation. The second issue is meeting volume of demand. At present, we think that 4/5 agents is about the right number to be involved given the volume of questions and content that come through Twitter. But, as agents come and go, or as question demand increases we'll refer to this list. Thanks. (Technical solutions to make sharing Twitter accounts safer and accountable are also up for future consideration.) —[[User:BenWard|BenWard]] 21:31, 26 September 2009 (UTC)

* [[User:Pfefferle]] - http://twitter.com/pfefferle & http://twitter.com/mikroformate

events/2009-06-27-microforamts-vevent-london

2009-06-10T11:22:56Z

Phae: events/2009-06-27-microforamts-vevent-london moved to events/2009-06-27-microformats-vevent-london: spelt url wrong

#REDIRECT [[events/2009-06-27-microformats-vevent-london]]

events/2009-06-27-microformats-vevent-london

2009-06-10T11:22:56Z

Phae: events/2009-06-27-microforamts-vevent-london moved to events/2009-06-27-microformats-vevent-london: spelt url wrong

{{stub}}

This page is for organizing a vEvent in London in June. One of several microformats [[events]].

If you'd like to help out, please add your name!

== Attending ==
Add your name if you're definitely coming:
* [[User:Phae|Frances Berriman]]
...

== Interested ==
Add your name if you're interested in coming, but aren't sure yet:
*
...

== location ==
There are several possibilities for venue, let's figure out what makes the most sense:
* TBC

== date ==
* 27th June - evening. Probably for dinner after the standards.forward HTML5 event. TBC.

events

2009-06-10T11:22:28Z

Phae: /* upcoming */ plank. spelt microformats wrong :)

<entry-title>Microformats related events</entry-title>
Please add microformats events (including events which have sessions on microformats) below.

Use the [[events-template|events template]] to create events pages, and list URLs, details, attendees, recommended tags, link to photos afterwards, etc. Add links to slides and other media to the [[presentations]], [[podcasts]] pages respectively.

Encourage the use of microformats on event sites' pages themselves, e.g. [[hCalendar]] and [[hCard]] for the schedule, sessions, speakers, and venues.

== Add events to your calendar ==
Track current and future microformats events by subscribing to <kbd style="display:block;margin:1em 0">'''webcal://feeds.technorati.com/events/microformats.org/wiki/events'''</kbd> in your calendar app. Set it to update once a day and new events will appear automatically.

You may also download [http://technorati.com/events/microformats.org/wiki/events events on this page as a standalone iCalendar file].

__TOC__
== regular ==
* [[weekly-meetup]] - weekly community meetups. details inside.

== upcoming ==


*2009-06-09 at 18:30: [[events/2009-06-09-weekly-dinner-sf|Microformats Dinner San Francisco]] at Pizza Zone & Grill, San Francisco, California.http://upcoming.yahoo.com/event/2852506/

*2009-06-19...<abbr class="dtstart" title="2009-06-21">20</abbr>: [[events/2009-06-microformats-4th-bday|microformats 4th birthday party]] at location TBD. http://tbd.example.com

*2009-06-27 at 18:00: [[events/2009-06-27-microformats-vevent-london|London Microformats vEvent]] at TBC, London.

== recent ==


=== June 2009 ===
*2009-06-08: [[events/2009-06-08-london-web-standards|London Web Standards June: microformats]] at join http://www.meetup.com/londonwebstandards/ to see the location. http://www.meetup.com/londonwebstandards/calendar/10387218/

*2009-06-02 at 19:00: [[events/2009-06-02-weekly-dinner-sf|Microformats Dinner San Francisco]] at 21st Amendment, San Francisco, California.http://upcoming.yahoo.com/event/2801069/

=== May 2009 ===
*2009-05-20 at 20:00: [[events/2009-05-20-adr-geo-where20|geo/adr microformats BOF session at Where 2.0]] at Gold Room, 2nd floor, Fairmont San Jose, 170 South Market Street, San Jose, California 95113. Join us to discuss the all the recent buzz around [[geo]], [[adr]], and [[hCard]] microformats, support by [[google-search|Google in rich snippets]], and by [[yahoo-search|Yahoo in YQL and Y! Placemaker]]. http://upcoming.yahoo.com/event/2718033

*2009-05-19 at 19:00: [[events/2009-05-19-weekly-dinner-sf|Microformats Dinner San Francisco]] at Banana House, San Francisco, California. http://upcoming.yahoo.com/event/2656903

*2009-05-15 at 11:30: Twiist.be conference: Microformats and Transient Semantics. http://twiist.be/speakers/briansuda

*2009-05-12 at 19:00: [[events/2009-05-12-weekly-dinner-sf|Microformats Dinner San Francisco]] at Crepevine on Church st. in San Francisco, California. http://upcoming.yahoo.com/event/2656901

*2009-05-05: [[events/2009-05-05-weekly-dinner-sf|Microformats Dinner San Francisco]] at Chevy's on 3rd street in San Francisco, California. http://upcoming.yahoo.com/event/2568451

=== April 2009 ===
*2009-04-07: [[events/2009-04-07-weekly-dinner-sf|Microformats Dinner San Francisco]] at Crepes on Cole, San Francisco, California. http://upcoming.yahoo.com/event/2376470
*2009-04-14: [[events/2009-04-14-weekly-dinner-sf|Microformats Dinner San Francisco]] at Pancho Villa Taqueria, San Francisco, California. http://upcoming.yahoo.com/event/2376478
*2009-04-20: [http://www.w3qc.org/communiques/archives/invitation-a-la-soiree-conference-du-20-avril-2009/ Microformats presentation] at Laika, Montéral, Québec. http://upcoming.yahoo.com/event/2423142/
*2009-04-21: [[events/2009-04-21-weekly-dinner-sf|Microformats Dinner San Francisco]] at Taylor's Automatic Refresher, San Francisco, California. http://upcoming.yahoo.com/event/2376483
*2009-04-28: [[events/2009-04-28-weekly-dinner-sf|Microformats Dinner San Francisco]] at Third Street Grill, San Francisco, California. http://upcoming.yahoo.com/event/2376485

=== March 2009 ===
*2009-03-31: [[events/2009-03-31-weekly-dinner-sf|Microformats Dinner San Francisco]] at Metreon Food Court, San Francisco, California. http://upcoming.yahoo.com/event/2295743
*2009-03-24: [[events/2009-03-24-weekly-dinner-sf|Microformats Dinner San Francisco]] at Naan N' Chutney, San Francisco, California. http://upcoming.yahoo.com/event/2171301
*2009-03-14: [[events/2009-03-14-sxsw-revolution|Microformats: A Quiet Revolution]] at Room 10, Austin Convention Center, Austin, TX. http://upcoming.yahoo.com/event/1825864/
*2009-03-03: [[events/2009-03-03-weekly-dinner-sf|Microformats Dinner San Francisco]] at Flippers, San Francisco, California.http://upcoming.yahoo.com/event/1918295/

=== February 2009 ===
*2009-02-24: [[events/2009-02-24-weekly-dinner-sf|Microformats Dinner San Francisco]] at 21st Amendment, San Francisco, California.http://upcoming.yahoo.com/event/1900098/
*2009-02-17: [[events/2009-02-17-weekly-dinner-sf|Microformats Dinner San Francisco]] at Naan N' Chutney, San Francisco, California. http://upcoming.yahoo.com/event/1840841/
* 2009-02-10 at 7pm: [[events/2009-02-10-weekly-dinner-sf|Microformats Dinner San Francisco]] at California Pizza Kitchen, San Francisco, California. http://upcoming.yahoo.com/event/1765705/
* 2009-02-03 at 7pm: [[events/2009-02-03-weekly-dinner-sf|Microformats Dinner San Francisco]] at Taqueria Pancho Villa, San Francisco, California. http://upcoming.yahoo.com/event/1519710/

=== January 2009 ===
* 2009-01-27 at 7pm: [[events/2009-01-27-weekly-dinner-sf|Microformats Dinner San Francisco]] at Crepes on Cole, San Francisco, California. http://upcoming.yahoo.com/event/1519151/
* 2009-01-20 at 8pm: [[events/2009-01-20-weekly-dinner-sf|Microformats Dinner San Francisco]] at 21st Amendment, 2nd Street, San Francisco, California
* 2009-01-13 at 6:30pm: [[events/2009-01-13-weekly-dinner-sf|Microformats Dinner San Francisco]] at 21st Amendment, 2nd Street, San Francisco, California · http://upcoming.yahoo.com/event/1489360/
* 2009-01-06 at 6:30pm: [[events/2009-01-06-weekly-dinner-sf|Microformats Dinner San Francisco]] at Westfield Shopping Centre Food Court, 818 Mission Street, San Francisco, California · http://upcoming.yahoo.com/event/1467444/

== Previous events ==
Previous years' events can be found at the following:
* [[events-2008]]
* [[events-2007]]
* [[events-2006]]

== Other languages ==
* [[current_events-fr|événements en cours]] (fr)

== Quicktime Broadcaster Notes ==

See [[quicktime]]

==Related pages==
{{events-related-pages}}

events/2009-06-27-microformats-vevent-london

2009-06-10T11:14:17Z

Phae: /* date */ wrong format

events/2009-06-27-microformats-vevent-london

2009-06-10T11:13:42Z

Phae: left in some unnecessary copy

events/2009-06-27-microformats-vevent-london

2009-06-10T11:13:23Z

Phae: stub

{{stub}}

This page is for organizing a vEvent in London in June. One of several microformats [[events]].

If you'd like to help out, please add your name!

== Attending ==
Add your name if you're definitely coming:
* [[User:Phae|Frances Berriman]] - coordinating
...

== Interested ==
Add your name if you're interested in coming, but aren't sure yet:
*
...

== location ==
There are several possibilities for venue, let's figure out what makes the most sense:
* TBC

== date ==
* 27th June - evening. Probably for dinner after the standards.forward HTML5 event. TBC.

events

2009-06-10T11:10:10Z

Phae: /* upcoming */ add link for vevent in london

<entry-title>Microformats related events</entry-title>
Please add microformats events (including events which have sessions on microformats) below.

Use the [[events-template|events template]] to create events pages, and list URLs, details, attendees, recommended tags, link to photos afterwards, etc. Add links to slides and other media to the [[presentations]], [[podcasts]] pages respectively.

Encourage the use of microformats on event sites' pages themselves, e.g. [[hCalendar]] and [[hCard]] for the schedule, sessions, speakers, and venues.

== Add events to your calendar ==
Track current and future microformats events by subscribing to <kbd style="display:block;margin:1em 0">'''webcal://feeds.technorati.com/events/microformats.org/wiki/events'''</kbd> in your calendar app. Set it to update once a day and new events will appear automatically.

You may also download [http://technorati.com/events/microformats.org/wiki/events events on this page as a standalone iCalendar file].

__TOC__
== regular ==
* [[weekly-meetup]] - weekly community meetups. details inside.

== upcoming ==


*2009-06-09 at 18:30: [[events/2009-06-09-weekly-dinner-sf|Microformats Dinner San Francisco]] at Pizza Zone & Grill, San Francisco, California.http://upcoming.yahoo.com/event/2852506/

*2009-06-19...<abbr class="dtstart" title="2009-06-21">20</abbr>: [[events/2009-06-microformats-4th-bday|microformats 4th birthday party]] at location TBD. http://tbd.example.com

*2009-06-27 at 18:00: [[events/2009-06-27-microforamts-vevent-london|London Microformats vEvent]] at TBC, London.

== recent ==


=== June 2009 ===
*2009-06-08: [[events/2009-06-08-london-web-standards|London Web Standards June: microformats]] at join http://www.meetup.com/londonwebstandards/ to see the location. http://www.meetup.com/londonwebstandards/calendar/10387218/

*2009-06-02 at 19:00: [[events/2009-06-02-weekly-dinner-sf|Microformats Dinner San Francisco]] at 21st Amendment, San Francisco, California.http://upcoming.yahoo.com/event/2801069/

=== May 2009 ===
*2009-05-20 at 20:00: [[events/2009-05-20-adr-geo-where20|geo/adr microformats BOF session at Where 2.0]] at Gold Room, 2nd floor, Fairmont San Jose, 170 South Market Street, San Jose, California 95113. Join us to discuss the all the recent buzz around [[geo]], [[adr]], and [[hCard]] microformats, support by [[google-search|Google in rich snippets]], and by [[yahoo-search|Yahoo in YQL and Y! Placemaker]]. http://upcoming.yahoo.com/event/2718033

*2009-05-19 at 19:00: [[events/2009-05-19-weekly-dinner-sf|Microformats Dinner San Francisco]] at Banana House, San Francisco, California. http://upcoming.yahoo.com/event/2656903

*2009-05-15 at 11:30: Twiist.be conference: Microformats and Transient Semantics. http://twiist.be/speakers/briansuda

*2009-05-12 at 19:00: [[events/2009-05-12-weekly-dinner-sf|Microformats Dinner San Francisco]] at Crepevine on Church st. in San Francisco, California. http://upcoming.yahoo.com/event/2656901

*2009-05-05: [[events/2009-05-05-weekly-dinner-sf|Microformats Dinner San Francisco]] at Chevy's on 3rd street in San Francisco, California. http://upcoming.yahoo.com/event/2568451

=== April 2009 ===
*2009-04-07: [[events/2009-04-07-weekly-dinner-sf|Microformats Dinner San Francisco]] at Crepes on Cole, San Francisco, California. http://upcoming.yahoo.com/event/2376470
*2009-04-14: [[events/2009-04-14-weekly-dinner-sf|Microformats Dinner San Francisco]] at Pancho Villa Taqueria, San Francisco, California. http://upcoming.yahoo.com/event/2376478
*2009-04-20: [http://www.w3qc.org/communiques/archives/invitation-a-la-soiree-conference-du-20-avril-2009/ Microformats presentation] at Laika, Montéral, Québec. http://upcoming.yahoo.com/event/2423142/
*2009-04-21: [[events/2009-04-21-weekly-dinner-sf|Microformats Dinner San Francisco]] at Taylor's Automatic Refresher, San Francisco, California. http://upcoming.yahoo.com/event/2376483
*2009-04-28: [[events/2009-04-28-weekly-dinner-sf|Microformats Dinner San Francisco]] at Third Street Grill, San Francisco, California. http://upcoming.yahoo.com/event/2376485

=== March 2009 ===
*2009-03-31: [[events/2009-03-31-weekly-dinner-sf|Microformats Dinner San Francisco]] at Metreon Food Court, San Francisco, California. http://upcoming.yahoo.com/event/2295743
*2009-03-24: [[events/2009-03-24-weekly-dinner-sf|Microformats Dinner San Francisco]] at Naan N' Chutney, San Francisco, California. http://upcoming.yahoo.com/event/2171301
*2009-03-14: [[events/2009-03-14-sxsw-revolution|Microformats: A Quiet Revolution]] at Room 10, Austin Convention Center, Austin, TX. http://upcoming.yahoo.com/event/1825864/
*2009-03-03: [[events/2009-03-03-weekly-dinner-sf|Microformats Dinner San Francisco]] at Flippers, San Francisco, California.http://upcoming.yahoo.com/event/1918295/

=== February 2009 ===
*2009-02-24: [[events/2009-02-24-weekly-dinner-sf|Microformats Dinner San Francisco]] at 21st Amendment, San Francisco, California.http://upcoming.yahoo.com/event/1900098/
*2009-02-17: [[events/2009-02-17-weekly-dinner-sf|Microformats Dinner San Francisco]] at Naan N' Chutney, San Francisco, California. http://upcoming.yahoo.com/event/1840841/
* 2009-02-10 at 7pm: [[events/2009-02-10-weekly-dinner-sf|Microformats Dinner San Francisco]] at California Pizza Kitchen, San Francisco, California. http://upcoming.yahoo.com/event/1765705/
* 2009-02-03 at 7pm: [[events/2009-02-03-weekly-dinner-sf|Microformats Dinner San Francisco]] at Taqueria Pancho Villa, San Francisco, California. http://upcoming.yahoo.com/event/1519710/

=== January 2009 ===
* 2009-01-27 at 7pm: [[events/2009-01-27-weekly-dinner-sf|Microformats Dinner San Francisco]] at Crepes on Cole, San Francisco, California. http://upcoming.yahoo.com/event/1519151/
* 2009-01-20 at 8pm: [[events/2009-01-20-weekly-dinner-sf|Microformats Dinner San Francisco]] at 21st Amendment, 2nd Street, San Francisco, California
* 2009-01-13 at 6:30pm: [[events/2009-01-13-weekly-dinner-sf|Microformats Dinner San Francisco]] at 21st Amendment, 2nd Street, San Francisco, California · http://upcoming.yahoo.com/event/1489360/
* 2009-01-06 at 6:30pm: [[events/2009-01-06-weekly-dinner-sf|Microformats Dinner San Francisco]] at Westfield Shopping Centre Food Court, 818 Mission Street, San Francisco, California · http://upcoming.yahoo.com/event/1467444/

== Previous events ==
Previous years' events can be found at the following:
* [[events-2008]]
* [[events-2007]]
* [[events-2006]]

== Other languages ==
* [[current_events-fr|événements en cours]] (fr)

== Quicktime Broadcaster Notes ==

See [[quicktime]]

==Related pages==
{{events-related-pages}}

html5

2009-05-24T08:43:10Z

Phae: formatting

<h1>Microformats in HTML 5</h1>

''This page is to document '''future''' use of microformats in [http://www.w3.org/html/wg/html5 HTML 5]. None of the items documented are supported now, and may change upon proper development within the microformats community, or changes in the HTML 5 specification. This page is to track HTML5 enabled enhancements to microformats, and issues that HTML5 raises. It may be used to track issues which we need to push back into the HTML 5 development process.''

If there are things that Microformats would like to mark up that aren't handled by HTML5 explicitly, please let the WHATWG know, so we can improve HTML5. This is how <code>time</code> came to be, for instance.

==New features in HTML5==

* '''<code>time</code> element for representing date times'''. In HTML5, the machine form of datetimes can be represented natively. It should be possible to replace the date-time design pattern with native HTML.
* '''<code>data-</code> naming convention for tag attributes'''. the draft specification states that any attribute that starts with "data-" will be treated as a storage area for private data.
** Note that the data-* stuff is explicitly 'not' for Microformats, at least not Microformats that ever want to be handled natively by the browser. Those attributes are defined in such a way that browsers will never do anything special with them, ever. They are intended for script authors to have a space in which they can play without ever clashing with anything the browser does.
* '''Microdata'''. HTML5 provides a set of attributes and associated DOM APIs for extracting data from web pages.

== Current microformat compatibility ==
There seems to be no issue with current implementation of the following microformats in HTML 5:
* [[hcard]]
* [[xfn]]

== Requests ==
* microformats examples that use HTML5, e.g.
** hCalendar with the <code>time</code> element
* microformats parsing details that specify what to do (if anything special is required) with HTML5 elements
** how to parse the <code>time</code> element for dates and times for microformats
** if nothing special is required, then after performing the analysis, that should be noted as well, for the purpose of clarity.

==Issues==

* '''The <code>rev</code> attribute has been removed'''. In HTML5, <code>rel</code> and <code>rev</code> are no-longer paired, and the <code>rel</code> attribute nolonger describes the direction of a relationship. Microformats which use <code>rev</code> will need to use <code>rel</code> instead.
** Or something like data-rev="vote-for"
*** As above, <code>data-</code> attributes are for application-context functionality, ''not'' shared vocabularies. Further, the HTML5 specification makes <code>rel</code> the correct attribute to use, regardless of direction, through the changed specification. --[[User:BenWard|BenWard]] 17:53, 12 May 2009 (UTC)
* '''The <code>profile</code> attribute has been removed'''. In HTML, the <code>profile</code> attribute from the <code>head</code> has been removed, with no direct replacement. This causes issues for GRDDL support. It's been suggested that profile URLs be represented in <code>link</code> elements instead, or even as a custom HTTP header. See [[grddl]] and [[profile-uris]]
* '''Microdata <code>itemprop</code> duplicates <code>class</code> data'''. the new attribute itemprop is designed to hold some meaningful data about an element, but class already exists to hold this data. Unsure of reasons why itemprop required?