Microformats Wiki - User contributions [en]

to-do

2007-08-12T17:20:05Z

WilleRaab: /* Wiki improvements */ << spelling is cool, gotta learn it...

<h1>To Do</h1>

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]

__TOC__

== Lazyweb ==

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

=== for all microformats ===
* We have recently 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. [[use]] 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.
* Add [http://verselogic.net/projects/wordpress/wordpress-openid-plugin/ OpenID] to Microformats Blog.
* Submit definitions of "mcroformat", 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]

=== 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/
* 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])

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

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

== Admins ==
This section is for any admins to keep track of current to-do items for admins and/or 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 tildas: <nowiki>~~~~</nowiki>.

=== Wiki improvements ===
* OpenID login, on behalf of a request a while ago from [[User:DanC]]. [[User:Tantek|Tantek]] 20:50, 20 Jul 2007 (PDT)
* Install creation template extension(s)(see: http://meta.wikimedia.org/wiki/Inputbox or http://www.mediawiki.org/wiki/Extension:CreateBox or http://www.mediawiki.org/wiki/Extension:CreateArticle) [[User:RobManson]] 14:00, 20 Jul 2007 (AEST)
* Encourage new users to use the preview feature to prevent a deluge of edit notifications from interrupting IRC discussions. [[User:SignpostMarv|SignpostMarv]] 09:28, 12 Aug 2007 (PDT)
* Some kind of [http://en.wikipedia.org/wiki/Spam_in_blogs anti-spam] (captcha? recaptcha? reverse turing tests? [http://unknowngenius.com/blog/wordpress/spam-karma/ Spam Karma?]) ~ [[User:WilleRaab|WilleRaab]] 09:43, 12 Aug 2007 (PDT)

== 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]] 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.
** remove noise from [[Main_Page|the wiki home page]] by simplifying/shortening it
*** move exploratory discussions to a separate page (think about what to name it)
*** move exploratory discussions which are failing to follow the process to a separate page from that

=== help publishers ===
==== 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]]
* give feedback to Erin, iterate, print more to have on hand, fold, distribute.
* 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)

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

==== [[hcard|hCard]] ====
Combined next-actions for iteration on [[hcard|hCard]], and derived/subsetted microformats [[adr]] and [[geo]]
* [[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-issues]] and [[hcard-feedback]]. '''next-actions''': resolve all issues and incorporate all feedback.
* [[hcard-brainstorming]] '''next-actions''': determine which brainstorms proposals to resolve in April, and which later
** 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''':
* itemize a list of properties 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.
* formalize [http://microformats.org/wiki/hcalendar- brainstorming#Tabular_event_calendars]
* flesh out [[hcalendar-examples]] and do a once over on markup/presentation of what RFC2445 examples would look like
* need spec details and then [[hcalendar-examples]] of multi-instance [[hcalendar|hCalendar]] events
* need spec details and then [[hcalendar-examples]] of repeating events
* add explicit explanation and examples for LOCATION [[hcard|hCards]] and ATTENDEE [[hcard|hCards]], perhaps on a separate [[hcalendar-examples]] page.
* need to resolve all outstanding [[hcalendar-issues]] to-do items.
* create [[hcalendar-profile]] and have folks verify it. 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''':
* Write hReview 0.3 XMDP profile, and reconcile 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''':
* Write [[rel-tag]] XMDP profile ([[rel-tag-profile]]) and send to [http://dbaron.org/ David Baron].
* Resolve all outstanding [[rel-tag-issues]] and [[rel-tag-feedback]] to-do items.

==== 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 reoganized content from the above "reoganizing Examples in the Wild" task

==== parsing ====
'''Next-actions''':
* Draft *-parsing for all reasonably well adopted microformats: [[hcalendar-parsing]], [[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 ====
'''Next-action''': work with Ryan, Ernie, Erin, and others who have made concrete helpful suggestions for reorganizing the information architecture / content-order / layout of specs for greater approachability/readability by a broader audience, to design an interative update to spec organizations, in particular, the introduction/boilerplate/headers. See below notes on hResume experiment in progress.

[[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. We need to:
# Figure out if the new intro/headers structure in [[hresume|hResume]] and/or [[hreview|hReview]] is an improvement, and if it could be better. Perhaps figure out the requirements for an intro/header section
#* Shorter tends to be better
#* Must be comprehensive enough to "print and read"
#* Must detail authorship/editorship
#* Must detail copyright/patent statements
# 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]]

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

==== 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 ===
* possibly move dead proposals off of homepage?

=== 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
* Add support for [http://verselogic.net/projects/wordpress/wordpress-openid-plugin/ OpenID] to the microformats blog.
* Read GTD (at least the first two chapters).

=== Campaigns ===

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

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

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

=== XSLTs ===
<ul>
<li><strong>Test scripts</strong>
<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><strong>hAtom2Atom</strong>
<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: (hAtom2<i>xyz</i>.xsl)
* RSS 2.0 (meanwhile use hAtom2Atom.xsl and [http://atom.geekhood.net/ atom2rss.xsl]) -- <i>+1 Matt Dertinger</i>
* RSS 1.0 (meanwhile use hAtom2Atom.xsl and [http://cvs.4suite.org/viewcvs/uogbuji/atom2rss.xslt atom2rss.xslt]) -- <i>+1 Matt Dertinger</i>
** 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])-- <i>+1 Matt Dertinger</i>
** 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]]

* Work on styles for [[zen-garden]] project.
* Style HTML cheatsheet to match Brian Suda's PDF.
* Write simplified help/implementation documents (how tos) for all finalised Microformats.
* Re-organise general FAQ and simplify
** (Feel free to add suggested tasks to my list below:)
*** Help converge on organization efforts ~bewest :-)

== 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: (hAtom2<i>xyz</i>.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 ===
<ul>
<li>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.</li>
<li>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.</li>
</ul>

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

to-do

2007-08-12T16:43:07Z

WilleRaab: /* Wiki improvements */ < + spam-prevention

<h1>To Do</h1>

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]

__TOC__

== Lazyweb ==

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

=== for all microformats ===
* We have recently 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. [[use]] 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.
* Add [http://verselogic.net/projects/wordpress/wordpress-openid-plugin/ OpenID] to Microformats Blog.
* Submit definitions of "mcroformat", 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]

=== 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/
* 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])

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

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

== Admins ==
This section is for any admins to keep track of current to-do items for admins and/or 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 tildas: <nowiki>~~~~</nowiki>.

=== Wiki improvements ===
* OpenID login, on behalf of a request a while ago from [[User:DanC]]. [[User:Tantek|Tantek]] 20:50, 20 Jul 2007 (PDT)
* Install creation template extension(s)(see: http://meta.wikimedia.org/wiki/Inputbox or http://www.mediawiki.org/wiki/Extension:CreateBox or http://www.mediawiki.org/wiki/Extension:CreateArticle) [[User:RobManson]] 14:00, 20 Jul 2007 (AEST)
* Encourage new users to use the preview feature to prevent a deluge of edit notifications from interrupting IRC discussions. [[User:SignpostMarv|SignpostMarv]] 09:28, 12 Aug 2007 (PDT)
* Some kind of [http://en.wikipedia.org/wiki/Spam_in_blogs anti-spam] (capatcha? recapatcha? reverse turing tests? [http://unknowngenius.com/blog/wordpress/spam-karma/ Spam Karma?]) ~ [[User:WilleRaab|WilleRaab]] 09:43, 12 Aug 2007 (PDT)

== 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]] 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.
** remove noise from [[Main_Page|the wiki home page]] by simplifying/shortening it
*** move exploratory discussions to a separate page (think about what to name it)
*** move exploratory discussions which are failing to follow the process to a separate page from that

=== help publishers ===
==== 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]]
* give feedback to Erin, iterate, print more to have on hand, fold, distribute.
* 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)

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

==== [[hcard|hCard]] ====
Combined next-actions for iteration on [[hcard|hCard]], and derived/subsetted microformats [[adr]] and [[geo]]
* [[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-issues]] and [[hcard-feedback]]. '''next-actions''': resolve all issues and incorporate all feedback.
* [[hcard-brainstorming]] '''next-actions''': determine which brainstorms proposals to resolve in April, and which later
** 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''':
* itemize a list of properties 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.
* formalize [http://microformats.org/wiki/hcalendar- brainstorming#Tabular_event_calendars]
* flesh out [[hcalendar-examples]] and do a once over on markup/presentation of what RFC2445 examples would look like
* need spec details and then [[hcalendar-examples]] of multi-instance [[hcalendar|hCalendar]] events
* need spec details and then [[hcalendar-examples]] of repeating events
* add explicit explanation and examples for LOCATION [[hcard|hCards]] and ATTENDEE [[hcard|hCards]], perhaps on a separate [[hcalendar-examples]] page.
* need to resolve all outstanding [[hcalendar-issues]] to-do items.
* create [[hcalendar-profile]] and have folks verify it. 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''':
* Write hReview 0.3 XMDP profile, and reconcile 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''':
* Write [[rel-tag]] XMDP profile ([[rel-tag-profile]]) and send to [http://dbaron.org/ David Baron].
* Resolve all outstanding [[rel-tag-issues]] and [[rel-tag-feedback]] to-do items.

==== 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 reoganized content from the above "reoganizing Examples in the Wild" task

==== parsing ====
'''Next-actions''':
* Draft *-parsing for all reasonably well adopted microformats: [[hcalendar-parsing]], [[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 ====
'''Next-action''': work with Ryan, Ernie, Erin, and others who have made concrete helpful suggestions for reorganizing the information architecture / content-order / layout of specs for greater approachability/readability by a broader audience, to design an interative update to spec organizations, in particular, the introduction/boilerplate/headers. See below notes on hResume experiment in progress.

[[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. We need to:
# Figure out if the new intro/headers structure in [[hresume|hResume]] and/or [[hreview|hReview]] is an improvement, and if it could be better. Perhaps figure out the requirements for an intro/header section
#* Shorter tends to be better
#* Must be comprehensive enough to "print and read"
#* Must detail authorship/editorship
#* Must detail copyright/patent statements
# 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]]

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

==== 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 ===
* possibly move dead proposals off of homepage?

=== 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
* Add support for [http://verselogic.net/projects/wordpress/wordpress-openid-plugin/ OpenID] to the microformats blog.
* Read GTD (at least the first two chapters).

=== Campaigns ===

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

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

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

=== XSLTs ===
<ul>
<li><strong>Test scripts</strong>
<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><strong>hAtom2Atom</strong>
<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: (hAtom2<i>xyz</i>.xsl)
* RSS 2.0 (meanwhile use hAtom2Atom.xsl and [http://atom.geekhood.net/ atom2rss.xsl]) -- <i>+1 Matt Dertinger</i>
* RSS 1.0 (meanwhile use hAtom2Atom.xsl and [http://cvs.4suite.org/viewcvs/uogbuji/atom2rss.xslt atom2rss.xslt]) -- <i>+1 Matt Dertinger</i>
** 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])-- <i>+1 Matt Dertinger</i>
** 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]]

* Work on styles for [[zen-garden]] project.
* Style HTML cheatsheet to match Brian Suda's PDF.
* Write simplified help/implementation documents (how tos) for all finalised Microformats.
* Re-organise general FAQ and simplify
** (Feel free to add suggested tasks to my list below:)
*** Help converge on organization efforts ~bewest :-)

== 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: (hAtom2<i>xyz</i>.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 ===
<ul>
<li>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.</li>
<li>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.</li>
</ul>

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

plazes-syntax

2007-07-25T15:32:23Z

WilleRaab: /* Numbers */ Broken link, added suggestion for change...

<h1>Plazes SMS Service Syntax</h1>

Retrieved from the [http://beta.plazes.com/locate/sms_detailed.php Plazes SMS Service page].
:'''Link broken. Perhaps this one could replace it - I'll let someone else be the judge: http://beta.plazes.com/the/help#faq-12 [[User:WilleRaab|WilleRaab]] 08:32, 25 Jul 2007 (PDT)'''

Once activated, you can send these commands to one of the following numbers and interact with Plazes on your mobile phone.

==Numbers==

<div class="vcard"><span class ="fn org">Plazes USA</span>: <span class="tel">+1 (718) 407-9566 </span></div>
<div class="vcard"><span class ="fn org">Plazes International</span>: <span class="tel">+49 176 888 111 33</span> (German number and charged accordingly)</div>

== Commands ==

=== Set Your Current Location ===

* '''at <plazename>''': set your location to an existing Plaze which is in the same city as your last visited Plaze (no matter if it was visited via SMS, Mobile Plazer or Plazer for Mac/PC).
** examples:
*** <code>at bar 25</code>
*** <code>at centre pompidou in paris</code>
*** <code>at sony center in berlin</code>
* '''in <city>''': to your text message if you have recently changed cities. You can also send in <city> as a single command to just locate yourself within a city.
** examples:
*** <code>in münchen</code>
*** <code>in roma</code>
*** <code>in palo alto</code>
* '''on <address>''': Add on <address> to your text message if you know you are visiting a new Plaze. You may also send on <address> if you want to locate yourself just at an address. Remember to send in <city> if you are in a new city.
** examples:
*** <code>on alexanderplatz</code>
*** <code>on mariahilfer strasse 43 in wien</code>
*** <code>on 11 market street in San Francisco</code>

Note that you can freely combine the at, in and on commands.

Examples:
* '''at''' soy luck club '''on''' 115 greenwich avenue '''in''' new york city
* '''at''' centraal station '''on''' stationsplein '''in''' amsterdam
* '''at''' hotel new koyo '''on''' 2-26-13 NIHONZUTSUMI TAITO-KU '''in''' tokyo

=== Finding Your Contacts ===

* '''contacts?''': Send '''contacts?''' to see where your friends are. Plazes SMS will return a list of your contacts, their current location and if possible, distance and direction from where you are.

=== Invite Others while on the Go ===

* '''invite <name of friend> <mobile number of friend>''': to invite someone while on the go. Your friend will get an SMS text message with your current location. Your friend will then get added to your contact list as soon as he/she replies.<br /> <br />The easy way to invite friends is to forward the contact right out of your phone's address book. If your phone supports sending business cards or vCards via SMS, just send the Plazes SMS the vCard of the friend you would like to invite.
** examples:
*** <code>invite tanya 0049 173 12345678</code>
*** <code>invite john_doe +1 555 123-4567</code>

=== Help on the Go ===

* '''help''': Send '''help''' to receive a text message with the basic commands for Plazes SMS.

==See also==
*[[picoformats]]

xoxo-faq

2007-07-25T01:54:36Z

WilleRaab: Fixed typo.

= XOXO FAQ =

This page documents questions and answers regarding the [[xoxo]] (Extensible Open XHTML Outlines) format.

== I don't understand what benefits xoxo provides ==
Color me dense, but I can't for the life of me figure out what XOXO offers. I read about syntax on this wiki, but not about use cases or benefits. Please help me understand! Thanks in advance. [[User:MikeSchinkel|MikeSchinkel]] 21:30, 11 Oct 2006 (PDT)

I also do not quite understand the dividing line between a bog-standard HTML list and a xoxo list. What is the defining difference? [[User:Premasagar|Premasagar]]

== the 'compact' attribute ==

''Q: why is compact/expanded expressed via a new attribute and not by a style class? Wouldn't it be more compatible to simply use a style class?''

A: The 'compact' attribute is not a new attribute. It is defined in XHTML Modularization, and has been in HTML (4, 3.2, 2) since [http://www.w3.org/MarkUp/HTMLPlus/htmlplus_31.html HTML Plus]. Whenever possible it is better to reuse an existing HTML attribute for semantics, instead of a style class. The essay [http://tantek.com/log/2002/12.html#L20021216 A Touch of Class] discusses such semantic nuances in more detail.

''Q: Follow-up: wouldn't a style class ''applied to the sub-outline's parent <code><li></code> element'' allow control over the rendering of the outline and its subject (e.g. adding an expand/collapse widget as a bullet-point)?''

A:See previous A: it is better to reuse an existing HTML attribute for semantics, rather than a style class. A style rule can be written to utilize the "compact" attribute just as easily as the "class" attribute, and then allow control over rendering of the outline and its subject.

''Q: Follow-up: Is 'compact' supposed to remove borders and spacing around a list?''
A: No. Please RTFM. [http://www.w3.org/TR/html401/struct/lists.html#adef-compact HTML 4.01 on the 'compact' attribute]: "When set, this boolean attribute gives a hint to visual user agents to render the list in a more compact way." And rendering the list in a more compact way (in particular, fully compacted) is exactly what [[xoxo]] specifies for the 'compact' attribute.

''Q: Why isn't the XForms "appearance" attribute used instead of "compact"?''

A: Why should the XForms "appearance" attribute be used? There is no need for it, nor is there any need for a second namespace to make simple things more complicated than they need to be.

''Q: Why is the 'compact' attribute, which was deprecated in the HTML4 specification, used in the XOXO format? Isn't it better not to use any deprecated elements or attributes?''

A: The 'compact' attribute as specified in HTML4 is purely presentational and as such was deprecated. Since this attribute has been little used, we have repurposed it as a semantic attribute in XOXO that actually preserves the state of whether or not the ''user'' has twiddled an outline item and all its children in the open state vs. the closed state. We recycled the 'compact' attribute instead of making a new attribute to minimize reinvention, and to make an otherwise useless attribute useful again.

== class="xoxo" ==

''Q: Why don't MarkP's examples use <code><ol class="xoxo"></code> ?''

A: The use of <code>class="xoxo"</code> is optional for XOXO authors and user agents.

== other markup in xoxo ==

''Q: MarkP uses <code><p></code> in some of his examples. Is that allowed? If yes, shouldn't <code><p></code> then be added to the description of XOXO's "document type" (see above)?''

A: Yes, additional elements and/or attributes are allowed per XHTML Modularization, and no, all such possible additions (e.g. <code><p></code>) don't need to be added to the XOXO document type since XOXO user agents may simply treat them according to the XHTML Modularization user agent conformance requirements (4-6):
1. ...
2. ...
3. ...
4. If a user agent encounters an element it does not recognize, it must continue to process the children of that element. If the content is text, the text must be presented to the user.
5. If a user agent encounters an attribute it does not recognize, it must ignore the entire attribute specification (i.e., the attribute and its value).
6. If a user agent encounters an attribute value it doesn't recognize, it must use the default attribute value.

== xoxo properties and values ==

''Q: Can an XOXO item have a multi-valued property, or a property with multiple values?''

A: Yes. Here is how you would do that:
<pre><nowiki>
<ol class='xoxo'>
<li>item 1
<dl>
<dt>multivalproperty1</dt>
<dd><ul>
<li>value-a</li>
<li>value-b</li>
</ul></dd>
</dl>
</li>
</ol>
</nowiki></pre>

semantic-html

2007-07-24T14:19:52Z

WilleRaab: /* Semantic Elements */ Added object (>map > area)

<h1> Semantic (X)HTML </h1>

Semantic (X)HTML refers to:
# The semantic elements and attributes of (X)HTML (as opposed to the [[presentational-html|presentational HTML]] elements and attributes)
# (X)HTML documents that are written using semantic (X)HTML.
# The practice of writing semantic (X)HTML
# [[posh|plain old semantic HTML]]

__TOC__

== Contributors ==
* [http://tantek.com/ Tantek]
* [[User:AndyMabbett|Andy Mabbett]]
* [[User:RobManson|Rob Manson]]

== Semantic Elements ==

(This list is incomplete, please add!)

* a
* abbr
* acronym
* address
* blockquote
* button
* caption
* cite
* code
* del
* dfn
* dl
** dt
** dd
* em
* fieldset
** legend
* form
* h1,h2,h3,h4,h5,h6
* input
* ins
* img
** map
*** area
* kbd
* li
* link
* label
* legend
* object
** map
*** area
* ol
* p
* pre
* q
* samp
* select
** optgroup
** option
* strong
* sub
* sup
* table (when used for tabular data, not layout)
** tbody
** td
** tfoot
** th
** thead
** tr
* textarea
* tt
* ul
* var

== Semantic Attributes ==

(This list is incomplete, please add!)

* caption
* class
* data
* href
* hreflang
* id
* lang
* rel
* rev
* scope
* summary
* type

== Presentations ==
See [[posh#POSH_Presentations|POSH Presentations]].

== See also ==
* [[semantic-xhtml-design-principles]]
* [[semantic-class-names]]

== References ==
* [http://w3.org/TR/xhtml1 XHTML 1.0]
* [http://w3.org/TR/html401 HTML 4.01]

hcard-brainstorming

2007-07-23T23:55:34Z

WilleRaab: Noted invalid link and added another link.

<h1> hCard Brainstorming </h1>
This page is for brainstorming about various uses and details of [[hcard|hCard]].

__TOC__

== Authors ==
* [http://suda.co.uk/ Brian Suda]
* [http://tantek.com/ Tantek Çelik] (formerly of [http://technorati.com Technorati, Inc])

== Contributors ==
* [[User:Atamido|Atamido]]
* [[User:ChrisMessina|ChrisMessina]]
* [[User:DimitriGlazkov|DimitriGlazkov]]
* [[User:AndyMabbett|Andy Mabbett]]
* ...
* ... and many others

== Problems Being Solved ==

Some of the problems that [[hcard|hCard]] helps to solve:

* having to enter business cards that go out of date (subscribe to someone's syndicated [[hcard|hCard]] instead).
* annoying "update your contact info" email from various centralized contact info services

== FN Nickname semantic ==

There are many sites (e.g. [http://flickr.com Flickr], [http://consumating.com/ Consumating]) which permit the user to '''both''' have a multi-word login/handle/alias, '''and''' not show their ''real'' name (fn, n, given-name, family-name etc.).

For the people represented by the profile pages of these sites, the best we can do is mark-up their login/handle/alias as their "nickname". Originally, we had thought that such handles etc. were single words only, and thus we created the [[hcard#Implied_.22nickname.22_Optimization|Implied nickname optimization]] accordingly, where you can markup the handle as an "fn", and have it automatically set a "nickname" property value, and empty values for all the "n" sub-values.

In order to deal with multi-word handles, similar to the [[hcard#Organization_Contact_Info|hCard Organization contact info]] method, the following is proposed:

=== "fn" and "nickname" combination ===

Due to the use of potentially multi-word nicknames/handles/usernames in content published on the Web, (e.g. on sites like [http://flickr.com Flickr] and [http://consumating.com/ Consumating]), hCard has a mechanism for specifying a multi-word "fn" that is also a "nickname" without affecting any "n" sub-properties that are otherwise specified, and explicitly implying empty defaults for "n" sub-properties.

Similar to the [[hcard#Implied_.22nickname.22_Optimization|implied "nickname" optimization]], if the "fn" property and a "nickname" property have the exact same value (typically because they are set on the same element, e.g. <code>class="fn nickname"</code>), then

# The content of the "fn" is treated as a "nickname" property value.
# Parsers should handle the missing "n" property by implying empty values for all the "n" sub-properties.

== Examples ==

* See [[hcard-examples]], which provides several illustrative instructive examples, as well as 1:1 hCard examples for each example in [http://www.ietf.org/rfc/rfc2426.txt RFC 2426].

=== Using RFC2806 with hCard ===

[http://www.ietf.org/rfc/rfc2806.txt RFC 2806] defines the telephone scheme "tel:", "fax:" and "modem:" to handle phone communications with URIs in the same way, "mailto:" is defined for email. It's part of the list or registered schemes by IANA : [http://www.iana.org/assignments/uri-schemes Uniform Resource Identifier (URI) SCHEMES]

<pre><nowiki>
tel telephone [RFC2806]
fax fax [RFC2806]
modem modem [RFC2806]
</nowiki></pre>

It is practical to write your tel number like this.

<pre><nowiki>
<a class="tel" href="tel:+1-919-555-7878">+1-919-555-7878</a>
</nowiki></pre>

or even

<pre><nowiki>
<a class="tel" href="tel:+1-919-555-7878">Mr Smith's phone</a>
</nowiki></pre>

You can add support for "tel:" to your desktop and to your browser

* For Gnome, edit ~/.gnome/Gnome and add something to the URL Handlers section. (Dan Connolly uses this to get galeon to launch telnum from [http://dev.w3.org/cvsweb/2001/telagent/ telagent sources] for tel URIs)
* In Mozilla, [http://dizzy.mozdev.org/ Dizzy]
* In Internet Explorer, [http://msdn.microsoft.com/workshop/networking/pluggable/overview/overview.asp Asynchronous Pluggable Protocols]

On the CSS front… You could for example add automagically an icon. I have put the property !important for those who wants to add it to their own stylesheet in their browsers, so they know type of links when browsing.

<pre><nowiki>
a[href^="tel:"]:before {
content: '\260f ' !important;
padding-left: 20px !important; }

a[href^="mailto:"]:before {
content: '\2709 ' !important;
padding-left: 20px !important; }
</nowiki></pre>

== Encoding "modern" attributes ==

Since vCard was first established, various interactive communication technologies and addressing schemes have been widely adopted. Although there aren't specific properties for these technologies / addressing schemes, they can be captured as URLs or email addresses.

This has now been written up for the most part. See:

http://microformats.org/wiki/hcard-examples#New_Types_of_Contact_Info

Still to be addressed:

* iChat mac.com addresses, simply store "@mac.com" email addresses, e.g.
** <code><nowiki><a class="email" href="mailto:steve@mac.com">...</nowiki></code>
* MSN Instant Messenger, you can simple store "@hotmail.com" or "@msn.com" or "@passport.com" email addresses.
* Internet Relay Chat (IRC), use "irc:" URLs.

== Auto-Discovery ==

=== Representative hCard discovery ===
Ways to auto discover the representative hCard for a page, that is the hCard that means the person/owner of the page.

Applications for auto-discovery of the representative hCard for the page
* vCard auto extraction from the page
* profile icon discovery (e.g. what people use gravatar for and have proposed pavatar for).

The preferred option is to use only visible semantic HTML ([[POSH]]).

Here is a scenario that outlines the proposed auto-discovery process:

# I (as user) give the URL of my homepage or hCard or other profile URL, to a site that wants a profile icon
# That site goes and gets it (e.g. using hKit), and then:
## checks to see if there is an <nowiki><address></nowiki> hCard, and uses it if it finds it
## otherwise uses the first hCard it finds (which in cases of profile URLs which have a single hCard like on [http://flickr.com Flickr], [http://zooomr.com Zooomr], and [http://technorati.com/ Technorati], will work as expected).
# The site looks in the hCard for a "logo" property and uses the first one if it finds any.
# Otherwise it looks for a "photo" property and uses the first one if it finds any.
# Otherwise the site uses a default icon, but subscribes to the URL with the hCard and checks it for a "logo" or "photo", say, once a day.

=== vCard link rel auto-discovery ===

A similar possibility is an auto discovery link in the head of the document could point to a URL (perhaps with transform) to a vCard version of the representative hCard.

On the page with the hCard encoding, the best link would be as follows:
<code><nowiki> <link rel="alternate" type="text/directory" href="..." /> </nowiki></code>
this HTML page is an alternate view of the vCard.

The [http://www.iana.org/assignments/media-types/text/ registered and appropriate type] for vCard entities is “text/directory”, as defined in Internet RFC 2425, “[http://www.rfc-editor.org/rfc/rfc2425.txt A MIME Content-Type for Directory Information]”. RFC 2426, “[http://www.rfc-editor.org/rfc/rfc2425.txt vCard MIME Directory Profile]”, specifies the vCard profile for “text/directory” entities, which profile the MIME/HTTP header field “Content-Type” would indicate with a “profile” parameter whose value is “VCARD”.

It is unclear whether the HTML/XHTML “type” attribute allows values with parameters. On 2004-05-23, [http://bjoern.hoehrmann.de/ Björn Höhrmann] sent to the [http://www.w3.org/2002/05/html/charter HTML Working Group] a [http://www.w3.org/mid/40ccdc4d.97400945@smtp.bjoern.hoehrmann.de request for clarification] on the issue.

When on a different page, referencing that encoded page in the href would ''not'' be an alternate view of the current page. Therefore rel="alternate" may not be appropriate. The problem of what rel value to use is bigger than links to vCards.

=== hCard to hCard relationships ===

There are several types of hCard to hCard relationships, that is, one hCard hyperlinking to another hCard which would beneift from the explicit rel values that described the specific relationship.

==== mini hCard to expanded hCard ====

Perhaps the most common type of hCard to hCard link is a mini hCard, e.g. from a personal home page or blog to the person's contact/about page, perhaps consisting of only a name and URL, that links to an expanded hCard. Examples in the wild:

In this instance, possible rel values might include:
* rel="expanded"
* rel="definitive" - the problem with this is that the expanded hCard is not necessarily a definitive version.
* rel="canonical" - similarly, the expanded hCard is not necessarily at a canonical URL. It may simply be *an* expanded version, not *the* expanded version.

The following rel values have been suggested, but are not really a good idea due to the fact that they imply a dependence to add a new rel value for any new microformat which might have a mini-version linking to a more expanded version:
* rel="author"
* rel='contact'
* rel="contactinfo"
* rel='hcard'
* rel='person'

Here are some more generic values that have been suggested which perhaps make even less sense:
* rel='microformat' - this doesn't make any sense when you imagine a world where nearly every web page contains microformats.
* rel='about' - what does "about" have to do with a person or even authorship?
* rel="profile" - should be reserved for meaning here is an [[xmdp|XMDP]] profile for the current page.
* rel='PIM' - not sure about how this makes any sense either.

==== mini hCard to remote site ====
Per the instructions in [[hcard-examples]] for [[hcard-examples#References_to_People_in_Blogrolls|marking up people in blogrolls]], you might have an hCard of your site for another person which then links to that other person's website. Should there be a rel value that indicates this "mini-hCard" to "person" relationship?

==== mini hCards and nearby expanded hCard links ====
Some authors include mini-hCards on their pages of themselves (e.g. in their blog posts), and yet those mini-hCards don't actually point to more expanded versions. However, sometimes they have a separate but nearby link on the same page like "about" or "contact" that does link to an expanded hCard.

E.g. on [http://factoryjoe.com/blog/ FactoryCity], blog posts have mini-hCards for "published by", e.g. (white space added for readability):
<pre><nowiki>
Published by
<span class="vcard author">
<a href="http://factoryjoe.com/blog/author/factoryjoe/" class="url fn">
Chris Messina
</a>
</span>
</nowiki></pre>

On those same blog pages, there is a link labeled "Contact Information" that links to http://factoryjoe.com/blog/hcard/ which has an hCard with more information like phone number, birthday etc.

=== Auto-Discovery for XFN ===

An author will typically their XFN information on a specific page, rather than all pages. In particular, a specific page separate from the home page of their blog, and thus it would be useful to have an explicit rel value to assist in auto-discovery of XFN information.

This was suggested by Jens Alfke on 20050606 at the WWDC blogger's dinner.

== geo improvements ==
''See [[geo-brainstorming]]''

== Other use cases ==
*calculate and display the subject's age "as of today".
*calculate and display the subject's age at death (if a Date of Death is available)
*Generate an recurring iCal for a living subject's birthday
*Generate an recurring iCal for a dead subject's "anniversary of birth" (if a Date of Death is available)

== Issues with vCard Applications ==
See [[vcard-implementations]].

== Open Questions ==

Q: since many of the components would be using CSS classes for encoding data, it is possible to MIX two different profiles. (e.g. hCard and XFN) There are no real constraints on where/how to enforce class names, these are based on the html profile, since it is difficult to associate the text within the attribute to a specific profile.

<pre><nowiki>
...
<a href="mailto:joe.smith@example.com" class="fn" rel="met">Joe Smith</a>
...
</nowiki></pre>

-- [http://suda.co.uk/ Brian Suda]

Q: Preserving White space? Should the transforming applications preserve extra white space characters? For example:
<pre><nowiki>
<a href="http://mywebsite.com/" class="fn n">
<span class="given-name">John</span>
<span class="other-names">Q.</span>
<span class="family-name">Public</span>
</a>
</nowiki></pre>

When transformed into a vCard, the N property will pick apart the span tags and create the value for N correctly seperated by colons. The FN property will take a string and simply display it. There are two possible renderings for FN:
<pre><nowiki>
John Q. Public

John
Q.
Public
</nowiki></pre>

Either the white-space is preserved or it is not. Which should the transforming applications render?

-- [http://suda.co.uk/ Brian Suda]

A: The parsing application should follow the white space collapsing rules of the mime type it retrieves. I.e. if it retrieves a "text/html" document, it should do HTML white space collapsing.

-- [http://tantek.com/log/ Tantek]

Many of the Questions and Answers are relevant to both ["hCal"] and hCard.

Q: Would it be appropriate to wrap the name of the vCard owner with <dfn/>? This may give the hCard some added semantic value in the XHTML document.
<pre><nowiki>
<span class="agent">
<span class="vcard">
<span class="email">
<a class="internet" href="mailto:jfriday@host.com">
<dfn>
<span class="fn">Joe Friday</span>
</dfn>
</a>
</span>
<span class="tel">+1-919-555-7878</span>
<span class="title">Area Administrator, Assistant</span>
</span>
</span>
</nowiki></pre>
-- [http://www.ben-ward.co.uk/ Ben Ward]
* If the answer to the above Q is "yes", why not use the following?
<pre><nowiki>
<dfn class="fn">Joe Friday</dfn>
</nowiki></pre>
or
<pre><nowiki>
<span class="agent">
<dfn class="vcard">
<span class="email">
<a class="internet" href="mailto:jfriday@host.com">
<span class="fn">Joe Friday</span>
</a>
</span>
<span class="tel">+1-919-555-7878</span>
<span class="title">Area Administrator, Assistant</span>
</dfn>
</span>
</nowiki></pre>
This would mark the entire hcard as the "defining instance".

[[User:Bob Jonkman|Bob Jonkman]] 10:07, 13 Jul 2007 (PDT)

== Applications ==
Applications that are hCard aware or can convert hCard to vCard formats.

=== Copy hCards favelet(s) ===
* I think a Favelet would work nicely here. When you find a page that is hCard friendly, you click the favlet and you get yourself a vCard. This is done! See X2V in the implementations section of the [[hcard|hCard]] spec.

=== Distributed Commentor Icons ===

''The URL reffered to in this section is no longer available. The thoughts on using icons are however still relevant.'' [[User:WilleRaab|WilleRaab]] 16:55, 23 Jul 2007 (PDT)

* See [http://thedredge.org/2005/06/using-hcards-in-your-blog/ using hCards in your blog] for an example of hCards used for comment authors (commentors). The system used there, "Gravatars", is a centralized site that serves commentor icons that requires login etc.

What if we gave each commentor the option of hosting their own icon?

A distributed commentor icon implementation could work like this:

# Given the URL of a commentor, look for an <code><address></code> element with classname of "vcard" at the commentor's URL. The <code><address></code> element is supposed to be the contact information for the page (see [[hcard-faq|hCard FAQ]] for more info), so this makes sense.
# Next, look for the first element inside that hcard that has a classname of "logo".
# Hopefully that element is an <code><img></code>, and if so, use its src to get the commentor's icon.
# Presto. You've got distributed commentor icons!

== Spam prevention ==
hCard uses <code>mailto:</code> links, and therefore
it automatically "inherits" the disadvantage of <code>mailto:</code> links:
These links can be easily detected by emails spiders (used by spammers).

Email addresses are picked up like any other link crawled by a search engine and trustworthy crawlers may be deterred from adding emphasis while indexing these links by including rel="nofollow" (See [[rel-nofollow]]). However, email addresses used for spam are crawled by email spiders which will likely ignore this attribute.

There are ways to prevent email address detection by simple email spiders, while
still retaining full compatibility with (X)HTML applications.
One common way is to "encode" the the "m" of "mail" and "@" with character entities, yet it's unwise to follow a convention of only encoding specific characters because the email spiders can pick up on this too:

Example of the original link:
<pre><nowiki>
<a class="email" href="mailto:john.smith@example.com">john.smith@example.com</a>
</nowiki></pre>

Example of the "encoded" link (with rel-nofollow added):
<pre><nowiki>
<a class="e&#109;ail" rel="nofollow" href="&#109;ailto:john.smith&#064;example.com">john.smith&#064;example.com</a>
</nowiki></pre>

Simple email spiders which do not do character entity decoding will therefore not be able to find your email address.

''Note:'' Perhaps there are or will be email spiders which can decode entities, so the this technique will only help with some (cheap) email spiders.
(See also: http://rbach.priv.at/Misc/2005/EmailSpiderTest)

=== Other prevention methods to consider ===
* Using server-side code to implement character entities randomly
* Displaying the address in a way thought to be only human readable (thus breaking the link):
** Using an image instead of text (could still be machine readable using OCR)
** Using human readable text that conveys the need for editing before use (eg PLEASE-NO-SPAM_name@example_NO-SPAM.com)
* Using javascript for client-side decryption of an encrypted address (requires javascript to be enabled)
* Pointing to an email form or other URL instead of an email address

== Tutorials ==
* How to hCard encode entries in Popular blog software.
* Good reasons to publish your hCard
** as a business, get people to put you in their address book so they'll find you later
** as a business with an email list, get people to add you (with email address) to their address book so that your email list works via whitelisting via the address book.

* [http://24ways.org/2006/styling-hcards-with-css Styling hCards with CSS] is a text on how to use CSS to make an improved presentation of an hCards contents.

== Parsing ==
See separate [[hcard-parsing|hCard parsing]] page for current hCard parsing rules.

Add thoughts/proposals to improve/add to hCard parsing here in this section in hCard brainstorming, and be sure to include URLs to examples of hCards in the wild which could benefit from parsing rule changes.

* Multiple Type parsing / Type Optimization: The spec allows for, and the [[hcard-authoring#Phone_Numbers|hcard-authoring]] demonstrate the use of multiple type designations for a single value of tel. The syntax used in the authoring examples where each seems like it could become cumbersome. As these type designations are all single 'word' strings it may be possible to implement additional parsing rules to allow for multiple types inside the same HTML element. Handling delimiters may be an issue [space, comma, etc?], and some in-the-wild usage of multiple types would need to be located and examined before considering additional parsing rules along these lines [ [[User:ChrisCasciano|ChrisCasciano]] 10:21, 16 Apr 2007 (PDT) ]
*Parsers could calculate the current age of hCard subjects, from the DoB. [[User:AndyMabbett|Andy Mabbett]] 07:47, 20 Apr 2007 (PDT)
*for hCards with DoB, parsers could generate and export a recurring hCalendar. [[User:AndyMabbett|Andy Mabbett]] 08:06, 20 Apr 2007 (PDT)
**If/ when date-of-death is added to hCard, parsers could instead generate a recurring "death-anniversary" hCalendar. [[User:AndyMabbett|Andy Mabbett]] 08:08, 20 Apr 2007 (PDT)
* ...

=== fax and modem hyperlink parsing ===
For the "tel" property in particular, when the element is:
* <code><a href="fax:..."></code> OR <code><area href="fax:..."></code> : parse the value of the 'href' attribute, omitting the "fax:" prefix and any "?" query suffix (if present), in the attribute. For details on the "fax:" URL scheme, see RFC 2806. In addition, treat this 'tel' property instance as having subproperty type "fax" in addition to any explicit subproperty type specified on the 'tel' property.
* <code><a href="modem:..."></code> OR <code><area href="modem:..."></code> : parse the value of the 'href' attribute, omitting the "modem:" prefix and any "?" query suffix (if present), in the attribute. For details on the "modem:" URL scheme, see RFC 2806. In addition, treat this 'tel' property instance as having subproperty type "modem" in addition to any explicit subproperty type specified on the 'tel' property.

=== Ambiguous name components ===

When automatically publishing hCards from pre-existing data, it's not necessarily possible to tell which words in a name map to which hCard properties. When the structure of a name is unknown, it is hard to ensure an automatically published hCard remains valid.

There's currently no easy answer to this.

One implementation suggestion is a 'best-guess' algorithm, something along the lines of:

# If the name is one word, attempt [[hcard#Implied_.22nickname.22_Optimization|implied nickname optimization]]
# If the name is two words, attempt [[hcard#Implied_.22n.22_Optimization|implied n optimization]]
# For three or more words
## Perform a lookup against known sub-name combinations (e.g. 'Sarah Jane', 'Vander Wal')
## Apply the grammar "given-name additional-name(s) family-name"

The principal behind this suggestion is that it's better to make a good guess and potentially miscategorize an ambiguous name component than to generate an invalid hCard.

===ADR with no children===
Parsers (Operator, Tails, Almost Universal Microformat Parser) currently expect <code>adr</code> to have one or more sub-properties. It is not clear from the hCard spec that that's mandatory (though the vCard RFC requires it); nor is it always possible for an address field in a templated (or CMS) web site to be defined with such granularity.

Consider Wikipedia, whose templates often have a "locale" or "place" field, used, for example, on these articles about railway stations:

*[http://en.wikipedia.org/wiki/Old_Street_station Old Street]
**"Place" ("locale" in the template) is a '''street'''
*[http://en.wikipedia.org/wiki/Hamstead_railway_station Hamstead]
**"Place" is a '''local district'''
*[http://en.wikipedia.org/wiki/Inverness_railway_station Inverness]
**"Place" is a '''city'''

Likewise, the Wikipedia template for organisations, in which a "headquarters" address (for a business, for example) may contain a full or partial postal address, or just a city/county or city/country pair:

*[http://en.wikipedia.org/wiki/Tesco Tesco]
*[http://en.wikipedia.org/wiki/BP BP]
*[http://en.wikipedia.org/wiki/Google Google]
*[http://en.wikipedia.org/wiki/Blue_Coat_Systems Blue Coat Systems]

I propose that, where <code>adr</code> has content, but no explicit sub-properties, there should be a default sub-property to which that content is allocated, in order that it is captured by user agents, and can later be manually tweaked (in, say, an address book programme) by users if so desired. This would satisfy the vCard requirement for child-of-adr, and adhere to the general principle to "[[be-strict|be strict in what you send but generous in what you receive]]".
*Note that there may be other reasons to consider this suggestion, such as "ease of authoring". Another way of looking at this suggestion is as a "adr/extended-address shorthand". [[User:Tantek|Tantek]] 08:28, 26 Mar 2007 (PDT)

* there is also a LABEL property which is NOT structured data, but purely a text string to be used when labeling. LABEL purpose: To specify the formatted text corresponding to delivery address of the object the vCard represents. [[User:Brian|Brian]] 13:18, 30 Mar 2007 (UTC)
**On re-reading this, it seems that none of the adressess given in my examples meet the criteria of being "''formatted text corresponding to delivery address''". [[User:AndyMabbett|Andy Mabbett]] 03:35, 17 Apr 2007 (PDT)

Of the available sub-property options:

*street-address
*extended-address
*region
*locality

I suggest that "extended-address" is the most sensible sub-property to use, for this purpose. [[User:AndyMabbett|Andy Mabbett]] 03:57, 26 Mar 2007 (PDT)

=== INPUT element handling ===

In [[hcard-parsing]], I've defined special-case handling for several elements according to [[hcard-parsing#more_semantic_exceptions|more semantic exceptions]], e.g. textual properties on the IMG element use the 'alt' attribute.

One element I forgot at the time was the INPUT element, specifically, <nowiki><input type="text"></nowiki>. Another I forgot was the TEXTAREA element.

The simple suggestion is to add the following to [[hcard-parsing]], specifically to the [[hcard-parsing#all_properties|all properties]] sub-section:

* <code><input type="text" value="..."></code>: use the value of the 'value' attribute. If there is no 'value' attribute then treat the value as empty. Interactive useragents MUST use the [http://www.w3.org/TR/html4/interact/forms.html#current-value current value] of the element.
** consider other input types also (e.g. checkbox, radio, hidden) and specify how to parse them as well.
* <code><textarea></code>: use the text contents of the element. Interactive useragents MUST use the [http://www.w3.org/TR/html4/interact/forms.html#current-value current value] of the element.

[[User:Tantek|Tantek]]

==== forms auto-fill ====
If you go to a site that needs your contact info for something, say an ecommerce site for checkout, and if the form fields are marked up with hCard semantics per the above, then perhaps we could consider having that mean "insert hCard here".

Interactive useragents (e.g. [[operator]] on [[firefox]]) could detect such "insert hCard here" semantics in forms on pages, and let you "pre-fill" with *your* hCard info, and then all of a sudden we have a standard for forms auto-fill, rather than all the hacks that have gone into browsers since 1999 (starting with IE4.5/Mac which I'm pretty sure was the first to do forms auto-fill of an entire form with a single button press - not just auto-complete of each form field individually).

Obviously this would make sense to build into *existing* forms auto-fill features in [[Firefox]] and [[IE]], and any other browsers that support it.

This way new sites could simply conform to the standard, rather than depend on hacks which parse label values etc. and imply things and get them wrong sometimes.

'''[[i18n]]''' advantages: hCard annotated form inputs would also be more international, thus avoiding the need for each browser to guess what is the "name" and "telephone" field in every language, so they can do forms auto-fill on any site regardless of language, not just English.

[[User:Tantek|Tantek]] 16:24, 23 Jul 2007 (PDT)

==== Background discussion: ====

Key threads:
* http://microformats.org/discuss/mail/microformats-discuss/2006-September/005951.html
* http://microformats.org/discuss/mail/microformats-discuss/2006-October/006132.html
* http://microformats.org/discuss/mail/microformats-discuss/2007-January/008312.html

Somewhat related:
* http://microformats.org/wiki/rest/forms-brainstorming
* http://microformats.org/wiki/rest/forms-examples

One key summary:
* http://microformats.org/discuss/mail/microformats-discuss/2006-October/006172.html

The options discussed in a hypothetical hCard input system so far appear to be:

1) create a new root class other than vcard to indicate a form that's
fillable with hCard data.

Proposed markup:

<pre><nowiki>
<form class="vcard-input" ...>
<fieldset class="fn">
<input type="text" class="given-name" name="first_name" />
<input type="text" class="family-name" name="last_name" />
</fieldset>
...
</form>
</nowiki></pre>

Benefits:
Doesn't overcomplicate hCard with new parsing rules,
doesn't require rewrite of existing parsers to ignore 'unparsable' data.
Drawbacks:
Requires completely new parsers to be written.
Existing parsers would ignore data even if a valid hCard could be extracted.

2) extend hCard's parsing rules to cover form elements and relying on
the FORM/INPUT semantics to indicate that stuff is inputtable.

Proposed markup:

<pre><nowiki>
<form ...>
<div class="vcard">
<fieldset class="fn">
<input type="text" class="given-name" name="first_name" value="Rob" />
<input type="text" class="family-name" name="last_name" value="Manson" />
</fieldset>
...
</div>
<div class="vcard">
<fieldset class="fn">
<input type="text" class="given-name" name="first_name" value="Scott" />
<input type="text" class="family-name" name="last_name" value="Reynen" />
</fieldset>
...
</div>
</form>
</nowiki></pre>

Benefits:
Small addition to existing format rather than new one.
Semantics of an input form and the eventual display format are the same.
Drawbacks:
Existing parsers would/could parse forms as invalid hCards, would need re-writing.

Broader question:
* http://microformats.org/discuss/mail/microformats-discuss/2005-September/001059.html
Should this be extended beyond just hCard?

==== Key Issues/discussion points ====
* Extending parsing rules to extract value attributes from <input type="text|hidden"> fields
- ''Negative'' : this require re-coding the existing parsers
- ''Positive'' : this could help to enable uf based auto form filling
- ''Negative'' : this could help to enable uf based auto form filling (e.g. spam automation)
* Existing server side and client side scripts use non-hCard field names so class is the most seamless extension point
- ''Positive'' : this is in line with the current parsing model
* Many parsers (e.g. operator) parse the loaded html not the dynamic DOM
- ''Negative'' : parser doesn't pickup any updated form data after the page has loaded
- e.g. even though textarea appears to parse ok - it's only ever the initially loaded value that can be exported
* Forms may contain more than one hCard so using <FORM class="vcard"> should not be required
- ''Positive'' : this minimises the changes to current parsing rules
* Empty values should be ignored when extracting hCards
* hCards with all empty values should be ignored when listing/extracting hCards
* Which form elements should be supported beyond input fields
- ''Examples''
- title select that lists mr/mrs/ms/dr/etc.
- checkboxes to choose which addresses to use
- ''Option'' : simplify extension to only support input fields and recommend that select's, radio buttons and checkboxes update related hidden input fields with simple javascript (e.g. onChange/Click="this.form.elements[this.className].value = this.value")
- ''Positive'' : this would simplify parsing and server side form processing as only single input fields for each value need to be used/validated
- ''Negative'' : hCard forms then require javascript if they use form elements other than basic <input type="text|hidden">
- ''Comment'' : either way any auto form filling will be more complex beyond simple <input type="text|hidden"> fields

[[User:RobManson|RobManson]]

== Post vCard additions ==

Keeping hCard properties and values as a 1:1 representation of vCard properties and values has numerous benefits such as simplicity, stability, interoperability with the vast number of existing vCard applications etc.

However some have found vCard to be limiting in terms of the data/properties/fields they want to express in contact information. Some implementations use vCard extensions to express such information [citation needed].

This section is for documentation of such suggested additions. Empirical evidence of actual *real world* examples on the Web of people publishing this information would be a good step towards considering any such additions/extensions.

* '''altitude'''. From [[hcard-issues]].
**See [[geo-elevation-examples]]
* '''vat-number''' : for VAT numbers of companies, which are used a lot in Europe and they need to be published on Belgian publications (including websites).
* '''gender'''
**most social network sites (see [[profile-examples]]) publish the gender of the individual
**Many pages publish implicit gender information, not easily machine parsable - using names (Andrew, Andrea), titles (Mr, Mrs, Miss), relationships (husband, brother), pronouns (he, she), etc. See also [[genealogy-brainstorming]]
* '''date-of-death'''
**Used by Wikipedia e.g. [http://en.wikipedia.org/wiki/John_Bonham John Bonham]
**Used in obituaries, e.g [http://www.westmidlandbirdclub.com/obituaries/norris.htm Tony Norris (WMBC)]; [http://www.guardian.co.uk/obituaries/story/0,,1725211,00.html Ivor Cutler (Guardian)]; [http://www.britarch.ac.uk/BA/ba8/ba8obit.html Grahame Clark (British Archaeology)]
**Used in grave indices e.g. [http://www.findagrave.com/cgi-bin/fg.cgi?page=gr&GRid=676 Chico Marx]
**Used on war memorial pages [http://tinyurl.com/2ddlvq Captain Ronald Wilkinson]
**Used in biographies e.g. [http://www.oxforddnb.com/public/lotw/6.html Oxford National Dictionary of Biography]
Of course if vCard were extended itself, that may provide impetus to add such extensions to hCard in order to maintain the 1:1 representation of properties/values.

Thus see (and add to): [[vcard-suggestions]]

Another path to consider is the development of another microformat which includes an hCard and then extends it with additional properties for a particular domain. In many ways [[hresume|hResume]] has already done this. Other related efforts:
* [[genealogy]]
* [[profile]]

Using hCard as a stable building block for additional microformats may seem more desirable than incrementally growing hCard itself.

==Wikipedia's Persondata==
Wikipedia's [http://en.wikipedia.org/wiki/Wikipedia:Persondata Persondata] aligns very closely with hCard, but has additional date and place of birth & death fields. [[User:AndyMabbett|Andy Mabbett]] 13:02, 28 Jan 2007 (PST)

== TODO ==

* The [[hcard-profile]] needs verification and perhaps a URL for retrieving the actual XMDP, rather than as <pre> text on a wiki page.
* Complete translating the examples from the vCard spec into hCard, and place them on a separate hCard examples page.
* Create a "rich" but realistic hCard example, say for example for a salesperson, who wants to put a whole bunch of contact information on their website in order to be found/contacted easily.
* Provide examples of how to encode instant messaging (IM) accounts. Figure out what would the mailto: or aim: URL in hCard look like in vCard. And take a look at what vCard applications do today with IM addresses.

== CSS Styles ==
Not only can you create semantics with the hCard values, but you can add CSS styles to them as well. You are free to style the terms in any way you want, but here we can list a few ideas for how to style terms.

If you want to encode hCard data, but do NOT want to display it in the HTML code (WARNING: This is very much recommended AGAINST, and in general against the microformat principle of marking up visible data), then you can hide that tag in CSS with the following code:
<pre><nowiki>
<span style="display: none">Hidden Data</span>
</nowiki></pre>
Transforming applications will still find the data and use it when converting hCards to vCards.

== Other Implementations/Ideas ==
* [http://www.w3.org/TR/2001/NOTE-vcard-rdf-20010222/ Representing vCard Objects in RDF/XML] This could allow conversion of vCard data from XHTML to RDF and from RDF to XHTML
* It would also be possible to convert XFN and hCard to FoaF.

== Accepted Suggestions ==

=== Encoding Company data as a Business Card (proposal) ===

( Accepted: http://microformats.org/wiki/hcard#Organization_Contact_Info )

In the wild there are several hCards that do not currently validate because they are businesses that have omitted the "fn" property in favor of the "org" property.

Proposal: hCards representing a business or organization MUST set fn AND org to the same value. Parsers may then use this equivalence, if detected, to treat an hCard as the contact info for a business or organization rather than an individual.

Note that [http://microformats.org/wiki/vcard-implementations#organization_vs._individual Apple Address Book supports this semantic when importing vCards].

See the [http://technorati.com/about/contact.html Technorati Contact Info] for an example.

=== Implied "FN and N" Optimization (proposal) ===

Right now a parser first looks for an "n" element.

And then if no "n" is present, look for an "fn" element to use to imply an "n" element per the "implied n property" rules in the spec.

BACKGROUND:

Due to the prevalence of the use of "nicknames" or "handles" on the Web, in actual content published on the Web (e.g. authors of reviews), there has been a discussion about adding a "fn" shortcut to the "n" shortcut that used the "nickname" as a fallback.

PROPOSAL:

We should consider adding one more implied optimization after the steps documented above and that is:

If no "fn" is present either, then look for a "nickname" element to use to imply both the "fn", and the "n/given-name", leaving the "n/family-name" as empty.

This would enable "nickname" only hCards for denoting and individual on a website, which is quite common on blogs and reviews published on the Web.
* +1 [[User:Atamido|Atamido]]
* +1 [[User:ChrisMessina|ChrisMessina]] - note: multiple alternate nicknames should also be allowed
* +1 [[User:DimitriGlazkov|DimitriGlazkov]]

== Rejected Suggestions ==

Suggestion: ''The use of class="url" on an <a> tag to represent an hCard URL property is redundant. By virtue of the <a> tag you know this is a URL.''

Rejected. This is a bad suggestion because although it appears to reduce redunancy and keep things cleaner, it also creates a few problems. Without explicitly noting that this is a URL then any <a> tags within a 'vcard' would be considered a URL, for example:
<pre><nowiki>
<span class="vcard">
...
<ul class="categories">
<li><a href="http://w3c.org">W3C</a></li>
</ul>
...
</span>
</nowiki></pre>

There is no way to "turn-off" the encoding of the W3C URL, whereas if "url" needed to be explicitly listed in the class attribute list, then by NOT listing it you could effectively turn it off.

== References ==
=== Normative References ===
* [http://www.ietf.org/rfc/rfc2426.txt RFC 2426] vCard RFC
* [http://www.ietf.org/rfc/rfc2397 RFC 2397] data URI RFC
* [http://gmpg.org/xmdp/ XMDP]
=== Informative References ===
* [http://www.imc.org/pdi/ Personal Data Interchange (PDI) at the Internet Mail Consortium]
* [http://tantek.com/log/2004/07.html#d27t1049 Markup language design notes]
* [http://tantek.com/log/2002/12.html#L20021216t2238 A Touch of Class]
* [http://www.icao.int/mrtd/download/technical.cfm ICAO - Machine Readable Travel Documents format]

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

recipe-brainstorming

2007-07-20T23:57:43Z

WilleRaab: /* Additional Suggestions */ A few suggestions.

= recipe brainstorming =

Towards a [[recipe]] microformat. Please read [[process]] before editing this page.

This page is currently a rough draft formed after surveying the [[recipe-examples]] and other related formats such as RecipeML and existing microformats. '''RecipeML MUST be documented in [[recipe-formats]], otherwise the reference is meaningless.'''

'''This page is currently premature, as there first needs to be a [[recipe-formats]] page where pre-existing recipe formats are documented (e.g. RecipeML), BEFORE brainstorming, per the [[process]]'''

==Suggested fields for inclusion==
Excerpted from [http://conoroneill.com/2006/03/21/what-if-i-suggest-a-structured-recipe-format-and-you-critique-it/ Conor Bandon's Blog entry] and derived from The RecipeML Spec:
*Recipe_Title
*Summary Description (one liner)
*Measurement System (U.S., Imperial etc)
*Ingredients (each one a separate "item" rather than block text with count/amount/range/unit broken out too)
**Some (e.g. meats, vegetables) could optionally be marked up with (elements of) the proposed [[species]] microformat. [[User:AndyMabbett|Andy Mabbett]] 06:41, 16 Nov 2006 (PST)
** Ingredient importance (e.g. Main, Required, Optional) should be listed as an attribute of each entry. [[User:AlexanderShusta|α]]
**Units need separate microformat: see [[measure]]
**Ingredient Preparation: such as diced, chopped, sliced, grated, minced, etc. [[User:SteveL|Steve Lewis]] 18:55, 11 Feb 2007 (PST)
*Preparation Time (overall time)
*Yield Quantity and Unit (4 pancakes or 5 servings)
**Calories per serving [[User:JohnLeMasney| John LeMasney]]
**Calories per ounce [[User:JohnLeMasney| John LeMasney]]
*Background Information - Optional section to encapsulate information that is useful but not necessarily required for a successful recipe. [[User:AlexanderShusta|α]]
**Author (Person) ([[hcard]]?)
**Submitter (Person) ([[hcard]]?)
**Source (Book Title etc)
*** could use the proposed [[citation]] microformat. [[User:AndyMabbett|Andy Mabbett]] 06:43, 16 Nov 2006 (PST)
**Date (Of Creation or Publication)
**Rights (Copyright or other)
**Meal Category (Starter, entree, dessert )
**Cuisine Category (Italian etc)
*Instructions (text, but can contain:)
**Steps (optional)
***Should be an ordered list [[User:AndyMabbett|Andy Mabbett]] 14:46, 16 Nov 2006 (PST)
***Another vote for an ordered list, perhaps in the [[XOXO]] format. [[User:AlexanderShusta|α]]
*Photo (optional) [[User:IamCam|Cameron Perry]]
**Could be one per dish, or one for each (or for some of the) step(s). [[User:AndyMabbett|Andy Mabbett]]

== Additional Suggestions ==

*Difficulty/Notes - Perhaps incorporation of [[hreview|hReview]] to describe difficulty (using rating) and general comments (review), as an optional field. [[User:Phae|Frances Berriman]]
*Suitability (e.g. vegetarian, vegan, wheat-free, etc.). Possibly [[rel-tag]]. [[User:AndyMabbett|Andy Mabbett]] 14:57, 16 Nov 2006 (PST)
*Ingredient Grouping - In baking you need to differentiate wet from dry ingredients. See also an [[recipe-examples|example recipe]] from [http://www.extratasty.com/recipe/46/cuba_libre extratasty.com] for useful grouping in cocktail mixing. [[SteveL|Steve Lewis]] 19:10, 11 Feb 2007
* Number of dishes or similary - often it's mentioned how many dishes (or breads in baking, etc) the ingredients are for. [[User:WilleRaab|WilleRaab]] 16:57, 20 Jul 2007 (PDT)
* Suitable for occations - what occations are the dish suitable for? [[User:WilleRaab|WilleRaab]] 16:57, 20 Jul 2007 (PDT)
* Category - many sites categorize their recipes. [[User:WilleRaab|WilleRaab]] 16:57, 20 Jul 2007 (PDT)

Note: Comments added ''"[[User:WilleRaab|WilleRaab]] 16:57, 20 Jul 2007 (PDT)"'' are added after looking at http://tasteline.com, example: [http://www.tasteline.com/default.ns?strItemID=showRecipe&intChannelID=&lngRID=8045&tlfo=0 here].

== Cookcamp brainstorming ==

At [http://barcamp.org/CookCamp CookCamp] in February 2007, Tantek moderated a fairly free form discussion of how to publish/share recipes. Here is a [http://flickr.com/photos/tantek/422072573/ photo of the whiteboard]:

[http://flickr.com/photos/tantek/422072573/ http://farm1.static.flickr.com/162/422072573_9956d93f61.jpg]

'''To Do''': OCR this and enter rough notes here...

==Issues==
===Scope===
*Is this intended for only food recipes, or also recipes for, say, glue, paint, dyes and other chemicals? [[User:AndyMabbett|Andy Mabbett]] 14:53, 16 Nov 2006 (PST)
** +1 Wondered the same. I'd like to see this extended as a general recipe for anything that can be created in a defined way/order, rather than just edible food.[[User:Phae|Frances Berriman]]
** Agreed. This format could apply to a set of methods and materials, including cooking, science experiments, craft making, building, etc. - essentially any how-to or tutorial. [[User:IamCam|Cameron Perry]]
** However, now I view my addition of 'calories per serving' as suspect, ;) though I guess it could still apply, since it's just a unit of energy. [[User:JohnLeMasney|John LeMasney]]
***Recipe for Nitroglycerine (not recommended by Weight Watchers) ? [[User:AndyMabbett|Andy Mabbett]] 10:43, 1 Feb 2007 (PST)
** The scope is determined by the [[recipe-examples]] research that is done, other musings are purely theoretical and thus discouraged. So far this means recipes means only food recipes. In addition, "recipe" in common vernacular applies primarily to food. Other uses are certainly outside the common 80/20 (note that 80/20 does note mean there are no non-food cases, merely that they are outside the 80). If you want to pursue other types of recipes, e.g. "chemical-recipes" - start that as a separate research effort per the [[process]]. [[User:Tantek|Tantek]] 07:39, 15 Mar 2007 (PDT)
*Is it possible to have special structure for the details of the operations in the cooking. For Eg. I invite you to have a look at the following Page [http://www.anthus.com/Recipes/CompCook.html]. Should it be possible to have special markup for the operations? Or is that going too far? Maybe we could keep this open ended so that it could be included when sites would actually be interested in including the same... Anyway the article makes for some interesting reading though it is from 1985 ;-) [[User:SudarshanP|SudarshanP]] 06:46, 26 Jun 2007 (PDT)

== See Also ==
* [[recipe]]
* [[recipe-examples]]
* [[recipe-formats]]

User:WilleRaab

2007-07-20T23:29:06Z

WilleRaab: public domain stuff..

<div id="hcard-Wilhelm-Raab" class="vcard">

<div style="float: left; margin: 0; padding: 0 23px 0 0">
http://www2.gnallspik.net/avatars/203634437944a80b9594562.gif
</div>

<div style="float: left; margin: 10px 0 0 0; padding: 0px 23px 0 0; vertical-align: top; ">
<div class="fn" style="font-weight: bold">Wilhelm Raab</div>
<div class="email">raab@home.se</div>
<div class="url">http://blog.gnallspik.net</div>
<div class="tel">+46-736-462427</div>
</div>

<div style="float: left; margin: 10px 0 0 0; padding: 0 23px 0 0; vertical-align: top; " class="adr">
<span class="street-address">Storgatan 56</span><br />
<span class="postal-code">S-17152</span>, <span class="locality">Solna</span><br />
<span class="country-name">Sweden</span><br />
</div>

</div>

<br style="clear: left">
<br />
<strong>Things that might be of interest:</strong>
* A very simple [http://www.greasespot.net Greasemonkey] script for parsing [[vote-links]] [[http://wille.sassur.net/lekstuga/vote-links.user.js script]|[http://wille.sassur.net/lekstuga/vote-links.html testpage]]

<div id="publicdomainrelease" cellspacing="1" cellpadding="1" style="background: #f7f8ff; border: 1px solid #88a; padding: 5px; font-size: 80%;"><span style="float:left;margin:.8em 0">http://upload.wikimedia.org/wikipedia/commons/thumb/6/62/PD-icon.svg/64px-PD-icon.svg.png</span><span style="float:right;margin:.8em 0">http://upload.wikimedia.org/wikipedia/commons/thumb/6/62/PD-icon.svg/64px-PD-icon.svg.png</span>
<div style="background:#fff;margin:0 68px;padding:2px"><div style="text-align: center; background: #ccf;">'''Released into public domain'''</div>
I agree to release my text and image contributions, unless otherwise stated, into the [http://en.wikipedia.org/wiki/public_domain public domain]. Please be aware that other contributors might not do the same, so if you want to use pages with my contributions under public domain terms, please check the other contributors' user pages.</div></div>
[[Category:public domain license|{{PAGENAME}}]]

advocacy

2007-07-20T23:27:08Z

WilleRaab: /* hCalendar */ New section (event-sites) + three links in this section.

<h1> Advocacy </h1>

A lot can be done to help advocate the use of microformats. Often, simply by taking an existing site, and adding the suggested microformatting to a few of its pages as examples is all that is necessary to help the developers of the site add the microformats to the site itself. Applications, such as browsers, could also use some guidance on how to best support microformats.

Sometimes advocacy requires comparison and analysis of alternative technologies or approaches. As [[User:MikeSchinkel|Mike Schinkel]] pointed out, we need good answers to comments like "No, we're going to use XYZ instead...".

The goal for this page is to include pointers for how to advocate microformats on new sites and on existing sites that are considering or using alternative approaches, as well as applications that can benefit from supporting microformats.

For general resources for marketing microformats, see [[spread-microformats]].

== Adding Microformats to Existing Sites ==

Add sites here that you think would benefit from the addition of microformats. For now they are grouped by the microformat which would primarily benefit the site. Feel free to take a look at some of the sites on this list, document sample pages to be microformatted, add microformats to them, and then add the before/after of the key sections of mark-up to another wiki page for that site.

Successes are also noted; the most recent are flagged as {{SuccessMarker}}.

If your successes resulted from emails that you sent to site owners/developers, please consider sharing your successful advocacy emails on the [[advocacy-email-samples]] page, and along with each email sample, list the sites which responded positively to your email. This way others in the community can learn from your success and hopefully use your email samples to contact additional sites and get them to adopt microformats.

===hCard===

;See [[hcard-advocacy]]

===hCalendar===

[[hcalendar|hCalendar]] could be used on these sites:

==== W3C track at WWW2006 ====
* DanC offers a 150 point bounty to anybody who takes [http://www.w3.org/2006/05/w3c-track the W3C track at WWW2006] and adds hCalendar markup and sends it to connolly@w3.org,www-archive@w3.org

====Television listings====
*A major coup would be to get one of the major players (the BBC, Sky, or PBS, say), to mark up their TV or radio listings with hCalendar - does anyone have contacts in such an organisation? [[User:AndyMabbett|Andy Mabbett]] 10:53, 21 Oct 2006 (PDT)
**Does anyone have URLs to the TV or radio listings of the major players? Getting those URLs would be the next step, and then doing the markup ourselves would be the next step after that. [[User:Tantek|Tantek]] 13:02, 21 Oct 2006 (PDT)

e.g. (please add other examples!):
*[http://www.tvtimes.co.uk/ TV Times] (UK)
** Requested by e-mail 2006-11-13 [[User:AndyMabbett|Andy Mabbett]]
*BBC main listings (e.g. [http://www.bbc.co.uk/bbcone/listings/index.shtml?service_id=4223 BBC One])
** Requested by [http://www.bbc.co.uk/feedback/bbci_comment.shtml BBC Feedback Form] 2006-11-13 [[User:AndyMabbett|Andy Mabbett]]
** [http://microformats.org/discuss/mail/microformats-discuss/2007-January/008129.html "We're currently looking at using the event microformat on the redesigned radio 4 schedule page (and possibly throughout bbc.co.uk/radio4"] 2007-01-14 per email.
* MTV Europe
**Requested at [[User talk:AndySmith]], 2007-06-11. [[User:AndyMabbett|Andy Mabbett]] 07:59, 11 Jun 2007 (PDT)

====Government hCalendar====
=====UK Gov. hCalendar=====
*[http://petitions.pm.gov.uk/ E-petitions] (in draft, and asking for suggested improvements}
** Requested by e-mail, 2006-12-01 [[User:AndyMabbett|Andy Mabbett]] 11:47, 1 Dec 2006 (PST)
*** reply: "I've added it to our list of ideas." 2006-12-04 [[User:AndyMabbett|Andy Mabbett]] 11:07, 4 Dec 2006 (PST)
*[http://www.scotland.gov.uk/Publications/2005/01/bankholidays Scottish Executive Bank Holidays]
** Requested by [http://www.scotland.gov.uk/About/HaveYourSay/WebsiteFdbck Scottish Executive feedback form], 2006-11-13 [[User:AndyMabbett|Andy Mabbett]]

====Sports Fixtures====
e.g. (please add other examples!):
*PremiumTV (UK, Soccer, has a page for each team)
**[http://www.avfc.premiumtv.co.uk/page/Fixtures/ Aston Villa]
**[http://www.wba.premiumtv.co.uk/page/Fixtures/ West Bromwich Albion]
*** Requested by e-mail, 2006-11-13 [[User:AndyMabbett|Andy Mabbett]]
****"webmaster@" bounced. [[User:AndyMabbett|Andy Mabbett]]

====Concert/ Theatre Listings====
e.g. (please add other examples!):
*[http://www.birmingham-alive.com/ Birmingham Alive!] (UK)
**Requested in person; now on "to do" list

====Travel Industry====
any travel site is based on calender type data!
Airlines, Hotels etc.
Sure it will be nice to get your reservation confirmation, but what about suppliers "syndicating" their product details that are calendar based? This would allow any other to mash-up supplier offerings.
Sorry no examples... but I hope this will stimulate others to add some if the know them or just to make others think about possibilities.

====iCal Share====
*[http://www.icalshare.com/ iCal share]
**Requested by e-mail. 2007-01-14

==== Event-sites ====
Sites that host online calendars of different sorts, containing information from many different areas. (These could also make use of hCard, since they often contain contant information to a lot of different places.)
* http://alltomstockholm.se A (Swedish) site that hosts information about concerts, pubs, movies, theater, etc in Stockholm (Swedens capital).
* http://www.alltomgoteborg.se A (Swedish) site that hosts information about concerts, pubs, movies, theater, etc in Gothenburg (Swedens second largest city).
* http://www.alltommalmo.se A (Swedish) site that hosts information about concerts, pubs, movies, theater, etc in Malmö (Swedens third largest city).

=== hReview ===
[[hreview|hReview]] could be used on these sites:

====Government hReview====
=====UK Gov. hReview=====
*[http://petitions.pm.gov.uk/ E-petitions] (in draft, and asking for suggested improvements}
** Requested by e-mail, 2006-12-01 [[User:AndyMabbett|Andy Mabbett]] 11:48, 1 Dec 2006 (PST)
*** reply: "I've added it to our list of ideas." 2006-12-04 [[User:AndyMabbett|Andy Mabbett]] 11:08, 4 Dec 2006 (PST)

====Other hReview====
* [http://www.imdb.com/ Internet Movie Database] (IMDb) for film reviews, e.g. [http://www.imdb.com/title/tt0049291/ The Harder They Fall ]. [[User:AndyMabbett|AndyMabbett]] 02:49, 13 Nov 2006 (PST)
**Can't find contact info! [[User:AndyMabbett|Andy Mabbett]]
**See also example, below.
* [http://www.dpreview.com/ Digital Photography Review]
** Requested by feedback form, 2007-01-18. [[User:AndyMabbett|Andy Mabbett]]
* [http://www.steves-digicams.com/ Steve's Digicams]
** Requested by e-mail, 2007-01-18. [[User:AndyMabbett|Andy Mabbett]]
* [http://www.librarything.com/ LibraryThing]
** e.g. [http://www.librarything.com/catalog.php?view=trealawboy]
* [http://www.summize.com/ Summize]
* [http://www.listal.com/ Listal] for all reviews including [http://www.listal.com/reviews/books/1/books books].
** Requested by e-mail, 2007-05-29. [[User:DavidMead|David Mead]]

===hAtom===
[[hatom|hAtom]] could be used on these sites:

====Government hAtom====
=====UK Gov. hAtom=====
*[http://petitions.pm.gov.uk/ E-petitions] (in draft, and asking for suggested improvements}
** Requested by e-mail, 2006-12-01 [[User:AndyMabbett|Andy Mabbett]] 11:49, 1 Dec 2006 (PST)
*** reply: "I've added it to our list of ideas." 2006-12-04 [[User:AndyMabbett|Andy Mabbett]] 11:07, 4 Dec 2006 (PST)

====Other hAtom====
* TV Listings (see hCalendar, above)
*[http://rbach.priv.at/Microformats-IRC/2006-11-13 IRC logs]
**E-mailed. [[User:AndyMabbett|Andy Mabbett]] 10:29, 5 Dec 2006 (PST)
* hatom can be used to markup log files. Basically log information is a feed of events. For more details, see the [http://microformats.org/discuss/mail/microformats-discuss/2007-March/009038.html logging technique] discussed in on [http://microformats.org/discuss/mail/microformats-discuss/2007-March/009038.html microformats-discuss].

=== Geo ===
Adding "[[geo|Geo]]" markup to these sites would make them even more useful:
*[http://meta.wikimedia.org/wiki/WikiGPS WikiGPS]
**Under development; notified of Geo microformat 2007-03-23
*Collections of waypoints
**See also [[geo-waypoint-examples]]
*Upcoming
**Some events, e.g. [http://upcoming.org/event/128155/ Multipack February 2007] are tagged thus: <code>geo:lat=52.4784</code>, <code>geo:lon=-1.9096</code>. This could be rendered as a geo microformat. [[User:AndyMabbett|Andy Mabbett]]
**Requested on (now defunct) Upcoming wiki 2007-01-14
**[http://suggestions.yahoo.com/detail/?prop=upcoming&fid=14362 Repeated on new suggestion board]. 2007-03-30. '''Please vote for this suggestion''' [[User:AndyMabbett|Andy Mabbett]]
*[http://www.census.gov/cgi-bin/gazetteer U.S. Gazetteer] e.g. [http://www.census.gov/cgi-bin/gazetteer?city=Birmingham&state=&zip=]
*[http://www.world-gazetteer.com/ World Gazetteer] e.g. [http://www.world-gazetteer.com/wg.php?x=&men=gpro&lng=en&dat=32&geo=-81&srt=npan&col=aohdq&pt=c&va=&geo=512945809]
**Requested by e-mail, 2007-01-20 [[User:AndyMabbett|Andy Mabbett]]
*[http://www.genuki.org.uk/cgi-bin/places GENUKI Gazetteer] (UK & Ireland) e.g. [http://www.genuki.org.uk/cgi-bin/maplink?CCC=STS,GR=SP040940,PLACE=Great%20Barr]
**Requested via feedback form, 2007-01-20 [[User:AndyMabbett|Andy Mabbett]]
*[http://www.confluence.org/ The Degree Confluence Project]
**Requested by e-mail, 2007-03-26 [[User:AndyMabbett|Andy Mabbett]]
*[http://www.wikimapia.org/ WikiMapia]
**Requested by e-mail, 2007-03-27 [[User:AndyMabbett|Andy Mabbett]]
**Replied to say they're looking into it. 2007-03-29
*[http://www.jeeep.com/details/coord/translate.cgi?datum=83&lat=52.57265&lon=-1.911433&detail=1 Jeeep.com]
**Requested by e-mail, 2007-03-27 [[User:AndyMabbett|Andy Mabbett]]
**Advertised address bouncing, 2007-03-27
*[http://www.flagr.com/ Flagr]
**Using, but not (yet) displaying, coordinates
**Requested by e-mail, 2007-03-30; also suggested they display their coordinates, and mark them up as tags [[User:AndyMabbett|Andy Mabbett]]
**Replied same day to say they will "talk it over internally"
*http://opencaching.de/
**Requires German speaker

Also:
* Various [http://en.wikipedia.org/wiki/Geocaching#Geocache_listing_sites Geocache listing sites]

=== Adr ===
Adding "[[adr|Adr]]" markup to these sites would make them even more useful:
*Various postcode <--> address lookup sites
** e.g. [http://www.royalmail.com/portal/rm/addressfinder Royal Mail (UK)] - enter a valid postcode (e.g. "B13 9PW").

===rel-tag===
====Google as rel-tag namespace====
A Google search for 'sparrow' resolves to http://www.google.com/search?&q=sparrow, if not the unwieldy http://www.google.com/search?hs=TUz&hl=en&lr=&client=firefox-a&rls=org.mozilla%3Aen-GB%3Aofficial&q=sparrow&btnG=Search - likewise http://www.google.com/search?&q=%22black+redstart%22 for ' "black redstart" '. If Google can be persuaded to also accept, say, '''<nowiki>http://www.google.com/search/sparrow</nowiki>''' and '''<nowiki>http://www.google.com/search/black_redstart</nowiki>''' as being equivalent (and assuming that the latter term searches for ' "black redstart" ', with the quote marks), then Google would become a namespace for rel-tag. [[User:AndyMabbett|Andy Mabbett]] 00:15, 29 Nov 2006 (PST)

=== VoteLinks ===
*[http://ma.gnolia.com Ma.gnolia]'s link rating system
**Requested: [http://wiki.ma.gnolia.com/Feature_Suggestions Feature Suggestions on wiki.ma.gnolia.com]

=== Multiple microformats ===
The following site(s) could benefit greatly from having multiple microformats added to their pages:
* IMDB, e.g. http://www.imdb.com/title/tt0413267/
** hReview for all the review data
** hCard for all the people
** tags for film/plot/other tags
** [http://tantek.com/microformats/2007/imdb-title-tt0413267uf.html title/tt0413267 with microformats] - hReview for the whole page for the item with overall rating, name, photo, tags. hCards for the directors/actors. [[User:Tantek|Tantek]] 19:20, 21 May 2007 (PDT)
***Could also use tag on year (also on Sound Mix, Certification and actor-names if URLs allowed this). [[User:AndyMabbett|Andy Mabbett]] 02:23, 22 May 2007 (PDT)
** [[media-info]] microformat once there is one.

===Various===
*eBay (.com and localised versions)
** '''hCard''' - Buyer and seller address details.
** '''hCalendar''' - Auction end date/times.
** '''hReview''' - Feedback.
** '''hAtom''' - Recent purchases/ won/ lost/ watching etc.
**Requested by feedback form, 2006-12-05. [[User:AndyMabbett|Andy Mabbett]]
**[http://microformats.org/discuss/mail/microformats-discuss/2006-December/007531.html eBay response of 2006-12-08]

====IT News sites====
There is obviously a great deal of publicity to be gained, by having microformats used on sites about IT developments, which are likely to be read by people in a position to have microformats used, and microformat tools implemented, in their organisations. Please add to this list!
*[http://www.theregister.co.uk/ The Register] (UK)
**Requested by e-mail, 2006-12-14. [[User:AndyMabbett|Andy Mabbett]]
*[http://www.ziffdavis.com/ Ziff-Davis] media sites, e.g:
**[http://www.microsoft-watch.com/ Microsoft Watch]
**[http://www.linux-watch.com/ Linux Watch]
**[http://www.extremetech.com/ Extreme Tech]
**[http://www.webbuyersguide.com/ Web Buyer's Guide]
**Requested at corporate level, 2006-12-14. [[User:AndyMabbett|Andy Mabbett]]
* [http://www.netmag.co.uk .Net magazine (UK)] (issue dated December 2006, has tutorial on microformats, by Rachel Andrew)
**Requested by e-mail, 2006-12-14. [[User:AndyMabbett|Andy Mabbett]]
* ...

====Other high-profile IT sites====
*[http://www.useit.com/ Jakob Nielsen's 'Use It'] and his [http://www.nngroup.com/ Nielsen Norman Group]
**Requested by e-mail, 2007-01-06. [[User:AndyMabbett|Andy Mabbett]]
*[http://www.vivabit.com/atmedia2007/ AtMedia2007]
**Requested via feedback form, 2007-01-18. [[User:AndyMabbett|Andy Mabbett]]
**Are using hCard, but will not use hCalendar, saying: "There are aspects of hCalendar that we are not happy using in this situation [...] It surrounds the use of the abbr element, particularly surrounding times in a table cell (the schedule will be slotted into a table once it is ready)." 2007-01-20. [[User:AndyMabbett|Andy Mabbett]]
* ...

====Science + Technology====
*[http://www.eurekalert.org/ Eurekalert]
**Requested via e-mail, 2007-01-20. [[User:AndyMabbett|Andy Mabbett]]

====Miscellany====
*[http://www.wikioutdoors.com/ WikiOutdoors]
**Could use hCard, Geo, and others
**Requested, 2007-03-14
**[http://www.wikioutdoors.com/forums/viewtopic.php?p=80#80 Considering] [[User:AndyMabbett|Andy Mabbett]] 04:17, 15 Mar 2007 (PDT)

== Adding Microformats to Applications ==

User-agents (browsers, etc.) should support microformats natively. For instance, a user should not need to use a third party application or web service to add address details or events from a microformat-using web page to their address book or calendar programme.

===Browsers===

In addition to the following, third-party developers should be encouraged to make their relevant browser add-ons microforamt aware; or to create new add-ons with microformat capabilities.

====Firefox====
===== Firefox developments =====
*Mozilla are "brainstorming" developments for Firefox 3.0 and beyond, and have a page on microformat handling at http://wiki.mozilla.org/Firefox/Feature_Brainstorming:Microformat_Handling

=====ReminderFox=====
*The makers of the [http://reminderfox.mozdev.org/ ReminderFox] extension have put hCalendar support on their [http://reminderfox.mozdev.org/userrequests.html ReminderFox "to do" list].

=====LinkAlert=====
*The [http://conlan89.googlepages.com/linkalert LinkAlert] extension could signal when a link is marked as a tag (likewise for other "rel" attributes). [[User:AndyMabbett|Andy Mabbett]]
**Requested by e-mail 2006-12-29. [[User:AndyMabbett|Andy Mabbett]]
**Response 2007-01-07: "Thank you for your feedback, I will consider adding [...] rel in a future update."

====Opera====
* First reference to "microformats" in the [http://my.opera.com/community/forums/topic.dml?id=169975&t=1166045417&page=1#comment1851680 Opera forums]. 2006-12-13 [[User:AndyMabbett|Andy Mabbett]]
*[http://www.operamini.com/ Opera Mini] (and other browsers on telephones) could especially benefit from recognising the "tel" attributes of hCard, and allowing users to dial numbers found on-line.
**[http://my.opera.com/community/forums/topic.dml?id=169978 Proposed on forum] 2006-12-13 [[User:AndyMabbett|Andy Mabbett]]
* We've been looking into Microformats for a while, and we are in the process of rolling out Microformats support on [http://my.opera.com/ My Opera] and [http://dev.opera.com/ Dev Opera]. Feel free to contact me with any additional suggestions of what you'd like to see. - [[User:DStorey|David Storey]]

===Screenreaders===
*Screenreaders (e.g [http://www.freedomscientific.com/fs_products/software_jaws.asp Jaws]) could recognise telephone number components of hCards, to differentiate them from other strings of digits. [[User:AndyMabbett|Andy Mabbett]] 13:02, 9 Dec 2006 (PST)
** Additional to this, I believe that screen reader users would benefit from being able to recognise any of the microformats. For example, there is value in being verbally notified that a page contains "1 contact and 3 events", or being able to seek out rel attributes with help values. [[User:Phae|Frances Berriman]]

===Publishing Platforms===

====Blogger====
* Chris Messina is [http://factoryjoe.com/blog/2006/09/02/on-open-letter-to-blogger/ advocating more support in Blogger]

====Drupal====
*There's a Drupal group for discussing/advocating/implementing [http://groups.drupal.org/microformats-in-drupal microformats in Drupal]

====MediaWiki====
*[http://www.mediawiki.org/wiki/MediaWiki MediaWiki]
** See above references to Wikipedia, which runs on MediaWiki (as does this wiki)

====Plone====
*[http://plone.org/ Plone] is an Open Source Content Management System ([http://en.wikipedia.org/wiki/Plone_(content_management_system) Plone on Wikipedia]).
**See this [http://plone.org/events/sprints/past-sprints/calsprint/SprintTopics/?searchterm=microformats 2005 Plone user comment]
**[http://dev.plone.org/plone/ticket/5351 Plone feature request for rel-tag]
**[http://dev.plone.org/plone/ticket/6050 Plone feature request for microformats], submitted 2007-01-06 [[User:AndyMabbett|Andy Mabbett]]

====Semantic MediaWiki====
*[http://wiki.ontoworld.org/wiki/Semantic_MediaWiki]
** A semantic version of MediaWiki

== Adding Microformats to Web Services ==

===30Boxes===
*[http://30boxes.com/ 30Boxes] could accept a URL, parse the page for hCalendar microformats, then present a list to the user. These could be selected (via check-boxes) and uploaded. [[User:AndyMabbett|Andy Mabbett]] 13:41, 14 Jan 2007 (PST)
**[http://30boxes.com/forum/viewtopic.php?p=8289#8289 Upload of hCalendars requested on 30Boxes forum] 2007-01-14

===ClearForest===
*[http://sws.clearforest.com/ ClearForest Semantic Web Services ] - uses natural language processing tools to recognise people, organisations, places, events and CVs (resumes) in web pages. Would benefit from recognising hCard, hResume, hCalendar, Geo, Adr, etc. Could also use them in its output. [[User:AndyMabbett|Andy Mabbett]] 05:09, 6 Dec 2006 (PST)

===ma.gnolia===
*[http://wiki.ma.gnolia.com/Microformat_Feature_Requests Microformat Feature Requests on ma.gnolia wiki]

===Upcoming===
*[http://upcoming.org/ Upcoming] could accept a URL, parse the page for hCalendar microformats, then present a list to the user. These could be selected (via check-boxes) and uploaded. [[User:AndyMabbett|Andy Mabbett]]
**[http://community.upcoming.org/w/index.php/Suggestion_Box#Upload_events_from_microformatted_pages Upload of hCalendars requested on Upcoming wiki] 2007-01-14

== Successes ==

For successes on Wikipedia, see the list of [http://en.wikipedia.org/wiki/Category:Templates_generating_microformats Wikipedia templates generating microformats].

=== hCard Successes ===

:See [[hcard-advocacy#Successes]]

=== hCalendar Successes===

*Details of hCalendar should be added to the [http://www.imc.org/pdi/ Internet Mail Consortium's vCalendar page]
**Requested by e-mail, 2006-11-24 [[User:AndyMabbett|Andy Mabbett]]
**'''Success''' achieved 2006-11-27. [[User:AndyMabbett|Andy Mabbett]]
*[http://www.radiotimes.com/ Radio Times] (BBC, UK)
** Requested by e-mail [[User:AndyMabbett|Andy Mabbett]]
** {{SuccessMarker}} 2007-03

=== hReview successes ===
*[http://www.birderslibrary.com/ The Birder's Library]
**[http://www.birdforum.net/showthread.php?p=779886#post779886 Requested]; confirmed under development, 2006-12-18.
** '''Success''' e.g. [http://www.birderslibrary.com/reviews/dvd/audubon_video_guide.htm Audubon VideoGuide to 505 Birds of North America]. Apparently from 2007-01-18 [[User:AndyMabbett|Andy Mabbett]]

===Geo Successes===
*Wikitravel
**All articles on places, e.g. [http://wikitravel.org/en/Birmingham_%28England%29 Wikitravel guide to Birmingham, England]
**See also [http://wikitravel.org/en/Wikitravel:Microformats Wikitravel:Microformats]
**achieved 2006-12-13, per [http://wikitravel.org/shared/Tech:Add_SpecialMap_using_Mapstraction_link_for_geo-tagged_pages_and_for_single_listings] see, for example, [http://wikitravel.org/en/Birmingham_%28England%29 Wikitravel guide to Birmingham, England] [[User:AndyMabbett|Andy Mabbett]]
*[http://www.poi66.com/ POI66]
**Requested by e-mail, 2007-03-23 [[User:AndyMabbett|Andy Mabbett]]
**over '''58,500''' waypoints geo-formatted, in under 4 hours from initial contact!
*[http://www.geograph.org.uk Geograph British Isles]
**Requested by feedback form, 2007-03-26 [[User:AndyMabbett|Andy Mabbett]]
** over '''370,000''' examples, within 30 minutes of request being submitted!
*[http://www.addressfix.com/ AddressFix]
**Requested via feedback form, 2007-01-26 [[User:AndyMabbett|Andy Mabbett]]
**valid postal addresses/ places converted, within one day of request being submitted.
*Wikipedia
**Wikipedia-EN
***Articles on places, e.g. [http://en.wikipedia.org/wiki/Great_Barr Wikipedia - Great Barr] (roll-out ongoing) 2007-03
***'''All''' map link pages linked to from the same, e.g. [http://tools.wikimedia.de/~magnus/geo/geohack.php?params=52.548_N_1.932_W_ maps for Wikipedia-EN article on Great Barr] 2007-03
***See also [http://en.wikipedia.org/wiki/Wikipedia:WikiProject_Microformats WikiProject Microformats]
**Wikipedia-DE
***'''All''' map link pages e.g. [http://tools.wikimedia.de/~magnus/geo/geohack.php?language=de&params=52_28_47_N_1_53_51_W_type:city_region:GB maps for Wikipedia-DE article on Birmingham]
**Wikipedia-NL
***'''All''' map link pages e.g. [http://www.nsesoftware.nl/wiki/maps.asp?params=52_28_47_N_1_53_51_W_type:city_region:GB&src=Birmingham_%28Engeland%29 maps for Wikipedia-NL article on Birmingham]
**GIS-Wiki's "[http://www.giswiki.org/hjl_get_CoorE.htm hjl_getCoor]" now outputs Geo markup, from a Google Maps API.
*[http://gc.kls2.com/ Great Circle Mapper] ("GCM"; e.g. [http://tinyurl.com/yugscj sample GCM trip], [http://gc.kls2.com/airport/BHX BHX on GCM])
**Requested by e-mail, 2007-06-21 [[User:AndyMabbett|Andy Mabbett]]
**{{SuccessMarker}} Confirmed in use, 2007-06-23

==Rejections==

===hCalendar rejections===
*[http://www.dti.gov.uk/employment/bank-public-holidays/index.html DTI: Bank Holidays] (not Scotland)
** Requested by e-mail, 2006-11-13 [[User:AndyMabbett|Andy Mabbett]]
***Response: "At the moment we have no plans to use hCalendar or hCard coding due to unresolved concerns about accessibility issues (especially text-to-speech readers), however, we thank you for your suggestion."
***Request for clarification of concerns unanswered.

===Geo rejections===
*[http://www.geocaching.com/ geocaching.com]
**Requested via feedback form, 2007-01-27 [[User:AndyMabbett|Andy Mabbett]]
**"The true benefit of this appears to be allowing sharing between sites [this] is something that GC specifically guards against so would be a major detriment. And most importantly when discussing a site or piece of software that is running smoothly, if it ain't broke, don't fix it. There just does not seem to be a benefit to GC's current plans." 2007-04-02

== Comparisons With Alternative Approaches ==

=== CalDAV ===
The CalDAV protocol should not be considered an 'alternative' approach as the two are not mutually exclusive. For more information, see:
*http://ietf.osafoundation.org/caldav/
*http://trac.calendarserver.org/projects/calendarserver

====Apple Support Tickets====
* Calendar Server hCalendar input/output: http://trac.macosforge.org/projects/calendarserver/ticket/19
* Wiki Server hCalendar output (internal RADAR ticket [rdar://5180875/])

====Mailing List Threads====
* [http://microformats.org/discuss/mail/microformats-discuss/2006-October/006584.html Microformats vs. CalDAV?] October 2006

=== Microsoft Exchange Server ===
Exchnage Server info to be added.

== See Also ==
* [[buttons]]
* [[podcasts]]
* [[presentations]]
* [[press]]
* [[spread-microformats]]

vote-links

2007-07-20T22:03:43Z

WilleRaab: /* Implementations */ Added link to vote-links-script for greasemonkey.

= Vote Links =
__TOC__
== Specification 2005 ==
=== Editor ===
* [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc.] (formerly of [http://microsoft.com/ Microsoft Corporation])

=== Concept ===
* [http://epeus.blogspot.com/ Kevin Marks], [http://technorati.com Technorati, Inc.]

=== Authors ===
* [http://epeus.blogspot.com/ Kevin Marks], [http://technorati.com Technorati, Inc]
* [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc]

=== Copyright ===
{{MicroFormatCopyrightStatement2004}}
* [[User:Tantek|Tantek]]: I release all my contributions to this specification into the public domain and I encourage the other authors to do so as well.

=== Patents ===
{{MicroFormatPatentStatement}}

=== Inspiration and Acknowledgments ===
Thanks to everyone who has given feedback on VoteLinks. Thanks especially to EtanWexler, who provided the first really good documentation that VoteLinks should be using 'rev' instead of 'rel' (see [[VoteLinksFAQ]]), and John Allsopp who similarly challenged the use of 'rel', and helped co-author the [[RelFAQ]] exploring questions and issues about the use of the HTML4 'rel', 'rev' attributes and linktypes in general.

== Introduction ==
Indexing and tracking applications treat all links as endorsements, or expressions of support. This is a problem, as we need to link to those we disagree with as well, to discuss why.

== Specification ==
VoteLinks is an [[elemental-microformat|elemental microformat]], one of several [[microformats|microformat]] open standards.
We propose a set of three new values for the rev attribute of the <a> (hyperlink) tag in HTML.

The new values are "vote-for" "vote-abstain" or "vote-against", which are mutually exclusive, and represent agreement, abstention or indifference, and disagreement respectively.

A link without an explicit vote 'rev' value is deemed to have value "vote-for" or "vote-abstain", depending on the application.

Additional human-readable commentary can be added using the existing 'title' attribute, which most browsers show as a rollover.

Examples:
<pre><nowiki>
<a rev="vote-for" href="http://ragingcow.blogspot.com"
title="neat spoof">Raging Cow</a>
<a rev="vote-against" href="http://ragingcow.com"
title="nasty corn syrup drink">Raging Cow</a>
</nowiki></pre>

=== Deprecated: Using 'rel' for VoteLinks ===
A previous draft of the specification used the 'rel' value instead of the 'rev' attribute. Analysis and feedback has demonstrated this to have been inappropriate use of the 'rel' attribute, when the 'rev' attribute was much more important. See the [[RelFAQ]] for more details.

Implementations MAY support links with the VoteLinks values in the 'rel' attribute for backward compatibility with any existing VoteLinks content.

Authors MUST NOT use 'rel' for VoteLinks values.

== XMDP profile ==
<pre><nowiki>
<dl class="profile">
<dt id="rev">rev</dt>
<dd><p><a rel="help" href="http://www.w3.org/TR/html401/struct/links.html#adef-rev">
HTML4 definition of the 'rev' attribute.</a>
Here are some additional values.</p>
<dl>
<dt id="vote-for">vote-for</dt>
<dd>Indicates agreement with or recommendation for the referred resource.</dd>
<dt id="vote-abstain">vote-abstain</dt>
<dd>Indicates abstention or indifference for the referred resource.</dd>
<dt id="vote-against">vote-against</dt>
<dd>Indicates disagreement with or recommendation against the referred resource.</dd>
</dl>
</dd>
</dl>
</nowiki></pre>

== Implementations ==
This section is '''informative'''.
* Following a [http://jyte.com/cl/jyte-should-integrate-microformats-votelinks vote-links claim] [http://jyte.com/profile/brianellin.com Brian Ellin] implemented vote-links on [http://jyte.com Jyte] within less than 30 minutes.
* [http://moloko.itc.it/paoloblog/ Paolo Massa] created [http://moloko.itc.it/paoloblog/semantic_links/ SemanticLinks], a small Firefox extension that shows vote-for, vote-against links information. (Note the download links for SemanticLinks have been removed by the author.)
* Wordpress VoteBack (vote-link aware pingback and trackback) plugin is in testing at [http://redmonk.net/archives/2006/12/21/voteback/ VoteBack] ([[User:SteveIvy|Steve Ivy]]) - looking for testers!
* [[User:WilleRaab|I've]] created a small and ''very'' simple [http://www.greasespot.net Greasemonkey] script for parsing [[vote-links]] [[http://wille.sassur.net/lekstuga/vote-links.user.js script]|[http://wille.sassur.net/lekstuga/vote-links.html testpage]]

== Normative References ==
* [http://gmpg.org/xmdp/ XMDP]

== Related Work ==
* [[xoxo]]
* [http://gmpg.org/xfn/ XFN]
* [http://developers.technorati.com/wiki/attentionxml Attention.xml]
* [[rellicense]]
* [[reltag]]
* [[relnofollow]]

== FAQ ==
* See [[vote-links-faq]] and the broader [[rel-faq]].
* See also [[vote-links-issues]] for issues which have been raised with the votelinks [[microformat]].

User:WilleRaab

2007-07-20T21:40:57Z

WilleRaab:

User:WilleRaab

2007-07-20T17:51:19Z

WilleRaab: Added link to greasmonkey script for vote-links.

User:WilleRaab

2007-07-20T14:30:44Z

WilleRaab:

hresume-authoring

2007-07-19T02:23:27Z

WilleRaab: /* Creating a new hResume */ changing the link to hresume-examples-in-wild....

<h1>hResume authoring</h1>

This page contains useful tips and guidelines for how to author an [[hresume|hResume]], either from scratch, or by adding markup to existing content.

'''Goal:''' The goal of this document is to provide some good intuitive guidelines that should make it as easy and as quick as possible for any web author to create hResumes or add hResume markup to existing content.

'''Audience:''' Web authors and designers. This document is written for easy consumption and understanding by any web designer who knows at least enough (X)HTML and CSS to use HTML class names on elements and write CSS selectors that apply styles to those class names. Please help with clarifying/simplifying this document accordingly.

'''Author(s):''' Tantek Çelik

__TOC__

== Creating a new hResume ==
Start with the [http://hresume.weblogswork.com/hresumecreator/ hResume creator], and for additional fields and properties, see the [[hresume-examples-in-wild|hResume examples]] page.

== Adding hCard markup to existing content ==

* To be filled in.

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

hresume-authoring

2007-07-19T02:19:55Z

WilleRaab: /* Creating a new hResume */ link-change hresume-examples to resume-examples

<h1>hResume authoring</h1>

This page contains useful tips and guidelines for how to author an [[hresume|hResume]], either from scratch, or by adding markup to existing content.

'''Goal:''' The goal of this document is to provide some good intuitive guidelines that should make it as easy and as quick as possible for any web author to create hResumes or add hResume markup to existing content.

'''Audience:''' Web authors and designers. This document is written for easy consumption and understanding by any web designer who knows at least enough (X)HTML and CSS to use HTML class names on elements and write CSS selectors that apply styles to those class names. Please help with clarifying/simplifying this document accordingly.

'''Author(s):''' Tantek Çelik

__TOC__

== Creating a new hResume ==
Start with the [http://hresume.weblogswork.com/hresumecreator/ hResume creator], and for additional fields and properties, see the [[resume-examples|hResume examples]] page.

== Adding hCard markup to existing content ==

* To be filled in.

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

how-to-play

2007-07-19T01:33:49Z

WilleRaab: Fixing invalid reference... (I hope. ;-) )

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

= How to Play =

Before contributing please observe these guidelines:

# You have to create an account (see [http://en.wikipedia.org/wiki/Wikipedia:Username Wikipedia Username guidelines]) before editing/creating pages.
# Read about microformats.org [http://microformats.org/wiki/Category:public_domain_license Voluntary Public Domain Declarations] and please consider adding the [[Template:public-domain-release]] to your User page accordingly to release your contributions to microformats.org into the public domain.
# Try the [http://microformats.org/discuss irc channel (preferable) or mailing lists] first (and read the [[mailing-lists]] page before doing so).
# If you write something opinionated, sign it with your username - you can easily do so with a datetimestamp in MediaWiki with four ~s, e.g.: <nowiki>~~~~</nowiki>.
# Please only create pages directly relating to microformats on this wiki. Other pages will likely be deleted.
# Please obey the [[naming-conventions| naming conventions]] for pages.
# Don't use talk pages. See #3.
# Please try to ensure that you produce valid XHTML.
# When you paste code, add some line breaks at a reasonable width.
# Please do not use "?" or other punctuation in the headings - it helps to keep the URLs to their fragment identifiers shorter and easier to read, copy/paste etc.
# Headings may be explicitly marked up with <h1> <h2> tags etc. in order to avoid having them show up / pollute the Table of Contents. If you find such headings in a page, please DO NOT change them to "=" or "==" style headings.
# Avoid renaming/changing heading text, including even just their capitalization or to comply with above rules that apply to headings. Headings are often used as permalinks, and changing the heading breaks such permalinks that have already been used. Thus be careful when creating headings. You may change a heading if you are careful to leave an empty <code><nowiki><span id="oldheadingID"></span></nowiki></code> in front of the heading with oldHeadingID set to the necessary value to maintain heading permalinks.
# Avoid global editorial wiki changes / edits (e.g. the same or similar edits applied to numerous pages, say, more than a dozen or so pages). If you have an opinion on how to globally improve something stylistically or editorially on the wiki, please add it to your section on the [[to-do]] page, and then perhaps ask the community using the microformats-discuss mailing list what folks think of it. Interpret absence of response(s) as disinterest and thus implicit rejection. Admins may from time to time do global wiki changes to remove spam, repair damage done by other global wiki edits etc.
# Please avoid simple contradictory responses such as "No" to questions and issues. Instead provide at least a short sentence with a reason which provides information beyond what is provided in the question or issue.
# Do not remove "red links", nor create empty / placeholder "..." pages for them just to make them not red. The red links usefully communicate a need or a desire for that page to exist, and the person expressing that desire may not be the same person that is able to take the time, or has the necessary skill/background to draft such a page. The links to pages not yet created often serve as an effective (and easy to execute) "to do" list. Removing those links makes it harder, less convenient to do so. (One exception noted so far: red links to non-existent microformats e.g. "hbib", should be delinked, as it is desirable for it to be harder/less convenient to create new microformats). Finally, as such links do provide information, they are not redundant.
# Do not use the MediaWiki "Categories" mechanism. As with "Talk" pages, this community does not use all the features of MediaWiki.
# Do not create new "User:" links by hand. User: links should only created as a result of users actually signing their edits with <nowiki>~~~</nowiki> or <nowiki>~~~~</nowiki>. That way each User: page will correspond to an actual login, rather than accidentally linking to a page which doesn't represent a login. If you see a red link which appears like it ''should'' be a User: link, e.g. <nowiki>[[DavidJanes]]</nowiki>, rather than editing the link in place, create a redirect at the destination of the link to the person's User: page.

== Wiki Cleaning ==

See [[spam-removal]].

If you see something which you think needs massive cleanup on the wiki, please point it out to admins on the irc channel or microformats-discuss list.

== Related ==

See [[mediawiki-customization]] for brief notes on how the microformats wiki is different from a "typical" MediaWiki install, in many ways to help with [[how-to-play]] and [[naming-conventions]].

hcard-advocacy

2007-07-18T17:46:21Z

WilleRaab: /* Online Profiles */ -> added some urls

= hCard advocacy =
Adding [[hcard|hCard]] to these sites would make them quite handy for their users and for being indexed:

== Online Profiles ==
Nearly every website that has a login has a page representing the public profile of the user that other users can see and interact with. Many such sites already [[hcard-implementations|support hCard]] (e.g. ClaimID.com, Flickr.com, Technorati.com, Zooomr.com). Here are some that I think would benefit from the addition of hCard to their profile / user pages. Feel free to add more such sites that have a social network profile-like component and I'll see what I can do. [[User:Tantek|Tantek]] 17:44, 13 Dec 2006 (PST)
* Wikimedia - including this site, Wikipedia (See [http://en.wikipedia.org/wiki/Wikipedia:WikiProject_Microformats WikiProject Microformats]), Wikitravel, etc.
**It would be nice if <nowiki>[[User:YOURNAME]]</nowiki> links generated proper (mini)hCards. ([http://microformats.org/wiki?title=to-do&diff=12177&oldid=12173#Lazyweb per SteveIvy]; moved from 'to-do')
* Alexa.com has online profiles for domains with contact information. Would be great if they could add hCard to those. 2007-04-18 [[User:Tantek]] requested of [[User:BenWest]] e.g.:
** http://www.alexa.com/data/details?url=alexa.com/
** http://www.alexa.com/data/details?url=w3.org/
* [http://dodgeball.com/ Dodgeball] profiles and venues need [[hcard|hCard]] for people and organizations
** [http://www.dodgeball.com/user?uid=30209 a profile]
** [http://www.dodgeball.com/venue?vid=23551 a venue] - could also use [[hreview|hReview]] for the user reviews listed there for the venue
* [http://idubyou.com/ i dub you]
* [http://www.icq.com/people ICQ, where they show ppls profiles and have a few ways of contacting and/or connection to ppl.]
* http://youtube.com The very popular youtube have profiles that do include some information that might use [[hcard|hCard]].
* [http://www.facebook.com Facebook] is a very popular (over 13 miljon members) community.

== Online Venues ==
There are many sites that offer pages that represent organizations and venues that could benefit from being marked up with hCard. [http://local.yahoo.com/ Yahoo Local] venues are marked up with hCards for example. Here are some more sites that have venues that would benefit from hCard markup.
* Yelp.com

== Plugins for and modifications of web-applications ==
Many web-applications use plugin-systems to change their behaviour and content. Most notable is probably web-forums and blogs. Many of these have a community of coders that develop plugins or code to modify the default behaviour of these web-applications. Here are some sites where it might be interesting to develop hcard-related plugins/mods.

* forum-software
** http://www.phpbb.com
* blog-software
** http://b2evolution.net

==Wikpedia hCard==
*Infobox Templates for people to add [[hcard|hCard]] to their generated markup
** [http://en.wikipedia.org/w/index.php?title=Template:Infobox_Biography&action=edit Infobox_Biography]
** [http://en.wikipedia.org/w/index.php?title=Template:Infobox_actor&action=edit Infobox_actor] which should result in actor pages, e.g. [http://en.wikipedia.org/wiki/Humphrey_Bogart Humphrey Bogart]'s page, being properly hCarded.
*Addressable buildings e.g. [http://en.wikipedia.org/wiki/The_Old_Crown%2C_Birmingham The Old Crown, Birmingham]
*Tourist attractions, e.g. [http://en.wikipedia.org/wiki/Cadbury_World Cadbury World]
*Companies, e.g. [http://en.wikipedia.org/wiki/Tesco Tesco] (note headquarters address in infobox)
*Motorway service stations, e.g. [http://en.wikipedia.org/wiki/Watford_Gap_service_station Watford Gap]
*Railway Stations, e.g. [http://en.wikipedia.org/wiki/Perry_Barr_railway_station Perry Barr]
*etc.
*See also [http://en.wikipedia.org/wiki/Wikipedia:WikiProject_Microformats WikiProject Microformats] [[User:AndyMabbett|Andy Mabbett]] 13:10, 28 Jan 2007 (PST)
* See also [[persondata|discussion of Wikipedia's Persondata]], which aligns very closely with hCard, but has additional date and place of birth & death fields. [[User:AndyMabbett|Andy Mabbett]] 13:23, 28 Mar 2007 (PDT)

==Telephone Directory Listings==
Telephone Directory Listings could usefully apply hCard to their results pages. [[User:AndyMabbett|Andy Mabbett]] 03:10, 13 Nov 2006 (PST)

e.g. (please add other examples!):
*[http://www.thephonebook.bt.com/ BT]
**Requested via [http://tinyurl.com/yhtdjy BT feedback form], 2006-11-13 [[User:AndyMabbett|Andy Mabbett]]
**BT confirm that they will consider this at their next re-build. 2006-12 [[User:AndyMabbett|Andy Mabbett]]
*[http://118118.com 118118.com]
**Requested via e-mail, 2006-11-13. [[User:AndyMabbett|Andy Mabbett]]
*[http://192.com/ 192.com]
**Requested via [http://www.192.com/support/feedback.cfm 192.com feedback form], 2007-03-07 [[User:AndyMabbett|Andy Mabbett]]
*[http://www.skype.com/intl/en-gb/download/features/skypefind/ SkypeFind]
**Requested via [http://support.skype.com/?_a=tickets&_m=submit Skype feedback form], 2007-03-16 [[User:AndyMabbett|Andy Mabbett]]
*[http://www.whitepages.com/ White Pages (USA/ Canada)]
*[http://www.whitepages.com.au/ White Pages (Australia)]
*[http://www.switchboard.com/ Stitchboard (USA)]]
*[http://people.yahoo.com/ Yahoo! People Search (USA)]
*[http://www.whowhere.com/ Lycos People Search (USA)]
*[http://www.bsnl.co.in/map.htm BSNL (India)]

==Postal (ZIP) code Finders==
Postal code Finders could usefully apply hCard to their results pages. [[User:AndyMabbett|Andy Mabbett]] 12:09, 13 Nov 2006 (PST)

e.g. (please add other examples!):
*[http://pol.royalmail.com/dda/txt/pf.asp Royal Mail] (UK)
**Requested via [http://tinyurl.com/ya4hzu Royal Mail feedback form], 2006-11-13 [[User:AndyMabbett|Andy Mabbett]]
**Acknowledged 2006-11-30. [[User:AndyMabbett|Andy Mabbett]]

==Government hCard==
===UK Gov. hCard===
* Parliament: [http://www.parliament.uk/directories/hciolists/alms.cfm Alphabetical List of Members of Parliament] (see also [http://www.parliament.uk/directories/directories.cfm other lists of MPs and Lords]). [[User:AndyMabbett|Andy Mabbett]]

===Europe Gov. hCard===
* e.g. [http://www.europarl.org.uk/uk_meps/westmidlands.asp UK MEPs]

=== MAPLight ===
http://maplight.org/ can use a bunch of hCard markup, e.g.
* individual politicians, like [http://www.maplight.org/map/us/legislator/408/individuals Nancy Pelosi]
* mentions of politicians on interest pages like [http://www.maplight.org/map/us/interest/L1300 Teachers unions]
* their contact info of course: http://www.maplight.org/contact
Requested by [[User:Tantek|Tantek]] 12:13, 30 May 2007 (PDT) in person at the NetSquared2007 conference.

== Organization Contacts ==
Many companies and organizations have about or contact pages that could benefit from being marked up with hCard. [http://technorati.com/about/contact.html Technorati's contact page] for example is both marked up with hCard and has a convenient "Add to Address Book" hCard to vCard converter link. The following company sites could benefit from similar markup (and, until user agents support hCards natively, "Add to Address Book" links). [[User:Tantek|Tantek]] 17:44, 13 Dec 2006 (PST)
*Adobe
**[http://www.adobe.com/aboutadobe/offices.html Adobe offices]
***Requested using contact form, 2006-12-14. [[User:AndyMabbett|Andy Mabbett]]
*Google
**Contacts, e.g.
*** [http://www.google.com/intl/en/contact/index.html Google.com contact page]
**** Requested by asking Google Employee KevinMarks via instant messaging to add hCard to that page along with a "Add to Address Book" link [[User:Tantek|Tantek]] 11:32, 10 Apr 2007 (PDT) and RyanKing in IRC
*** [http://www.google.co.uk/intl/en/contact/index.html Google UK], etc.
*[http://www.mozilla.com/ Mozilla]
**[http://www.mozilla.com/en-US/about/legal.html Mozilla legal notices]
*Opera
**People, e.g. [http://people.opera.com/howcome/ Håkon Wium Lie]; could also be hResume
*W3C
**[http://www.w3.org/Consortium/contact W3C contact]
**[http://www.w3.org/People/all W3C Staff listing] and individual pages, e.g. [http://www.w3.org/People/Berners-Lee/ Tim Berners-Lee]
***Requested by e-mail. [[User:AndyMabbett|Andy Mabbett]]

== Individual hCards ==
Getting these sites to at least add hCard to their home page or contact info page and then [http://pingerati.net/ping/ ping Pingerati] would be an excellent start with getting them some experience with microformats and thinking about adding microformats to other places in their sites that make sense:
* [http://metaweb.com/ Metaweb Technologies]
** [http://www.freebase.com/ Freebase ]

==Other hCard==
* [http://www.imdb.com/ Internet Movie Database] (IMDb) for people (real, not characters), e.g. [http://www.imdb.com/name/nm0000007/ Humphrey Bogart]. [[User:AndyMabbett|Andy Mabbett]] 02:49, 13 Nov 2006 (PST)
**Can't find contact info! [[User:AndyMabbett|Andy Mabbett]]
**See also example, below.
*Wikitravel
**e.g. [http://wikitravel.org/en/Birmingham_%28England%29 Wikitravel - Birmingham]
***[http://microformats.org/wiki?title=User_talk:MarkJaroski&curid=2699&diff=0&oldid=10663&rcid=19955 Wikitravel is about to hugely roll out hCard] Mark Jaroski
***See also [http://wikitravel.org/en/Wikitravel:Microformats Wikitravel:Microformats]
*[http://orlabs.oclc.org/Identities/ WorldCat Identities]
**The recently prototyped WorldCat Identities provides pages for 20 million 'identities', mainly authors and people who are the subjects of published titles.
**Requested by feedback form, 2007-03-09 [[User:AndyMabbett|Andy Mabbett]]
** No reply, as of 02:02, 13 Jun 2007 (PDT)
*[http://geonames.org GeoNames]
**Requested by e-mail, 2007-06-07 [[User:AndyMabbett|Andy Mabbett]]
**Reply confirms that they will deploy hCard and Geo
*[http://www.oup.com/oxforddnb/info/ Oxford Dictionary of National Biography] (ODNB); subscription based, but [http://www.oxforddnb.com/public/lotw/ some ODNB articles available free]. All 56,000+ entries have Date of Death.
*[http://www.findagrave.com/ Find-a-Grave] e.g. [http://www.findagrave.com/cgi-bin/fg.cgi?page=gr&GRid=680 Karl Marx]. Most entries have Date of Death.

== Successes ==

*Details of hCard should be added to the [http://www.imc.org/pdi/ Internet Mail Consortium's vCard page]
**Requested by e-mail, 2006-11-24 [[User:AndyMabbett|Andy Mabbett]]
**'''Success''' achieved 2006-11-25. [[User:AndyMabbett|Andy Mabbett]]
*W3C
**'''W3C webmaster''' [http://www.w3.org/People/Jean-Gui/ Jean-Guilhem Rouel] now has an hCard. [[User:AndyMabbett|Andy Mabbett]] 15:41, 4 Apr 2007 (PDT)
*Wikipedia-EN - starting to roll-out
**UK Railway station template, e.g. [http://en.wikipedia.org/wiki/Birmingham_New_Street Birmingham New Street station] (includes Geo)
* [http://jpgmag.com/ JPG magazine] - have sent email to their web developer with sample marked up member profile with [[hcard|hCard]] and [[xfn]] [[rel-me|rel="me"]]. [[User:Tantek|Tantek]] 23:48, 21 Feb 2007 (PST)
** [[hcard|hCard]]+[[xfn]] [[rel-me|rel="me"]] support as of March 2007.
* Twitter.com - working on it [[User:Tantek|Tantek]] 17:44, 13 Dec 2006 (PST).
** Completed [[hcard|hCard]]+[[xfn]]+[[hatom|hAtom]] support last week with help from Chris Messina. [[User:Tantek|Tantek]] 12:01, 16 May 2007 (PDT)
* Consumating.com - working on it [[User:Tantek|Tantek]] 17:44, 13 Dec 2006 (PST)
** [[hcard|hCard]] profiles, [[hcalendar|hCalendar]] events as of March 2007.
* [http://sunlightlabs.com/api/ SunlightLabs API] provides profiles for US Congresspeople. Their [http://sunlightlabs.com/api/masterref/megatable.php megatable] could easily be marked up with hCard, and their APIs could return hCards and hCard fields.
** [[User:Tantek|Tantek]] 12:30, 20 Apr 2007 (PDT) contacted them and requested that they add hCard to megatable, consider a GethCard API method, and potentially a GethResume API method for each person.
** [[User:CarlAnderson|CarlAnderson]] 26 Apr 2007: http://sunlightlabs.com/api does now have a people.getHCard.php API method to get an hCard for every member of congress. See the documentation at http://sunlightlabs.com/api/people.getHCard.php. An example call: http://api.sunlightlabs.com/people.getHCard.php?id=fakeopenID1
** [[User:CarlAnderson|CarlAnderson]] 30 Apr 2007: I created a page of hCards for every member of congress: http://sunlightlabs.com/api/hcards/index.php

==See also==
{{hcard-related-pages}}
*[[advocacy]]

hcard-advocacy

2007-07-18T17:42:50Z

WilleRaab: New section: Plugins for and modifications of web-applications

= hCard advocacy =
Adding [[hcard|hCard]] to these sites would make them quite handy for their users and for being indexed:

== Online Profiles ==
Nearly every website that has a login has a page representing the public profile of the user that other users can see and interact with. Many such sites already [[hcard-implementations|support hCard]] (e.g. ClaimID.com, Flickr.com, Technorati.com, Zooomr.com). Here are some that I think would benefit from the addition of hCard to their profile / user pages. Feel free to add more such sites that have a social network profile-like component and I'll see what I can do. [[User:Tantek|Tantek]] 17:44, 13 Dec 2006 (PST)
* Wikimedia - including this site, Wikipedia (See [http://en.wikipedia.org/wiki/Wikipedia:WikiProject_Microformats WikiProject Microformats]), Wikitravel, etc.
**It would be nice if <nowiki>[[User:YOURNAME]]</nowiki> links generated proper (mini)hCards. ([http://microformats.org/wiki?title=to-do&diff=12177&oldid=12173#Lazyweb per SteveIvy]; moved from 'to-do')
* Alexa.com has online profiles for domains with contact information. Would be great if they could add hCard to those. 2007-04-18 [[User:Tantek]] requested of [[User:BenWest]] e.g.:
** http://www.alexa.com/data/details?url=alexa.com/
** http://www.alexa.com/data/details?url=w3.org/
* [http://dodgeball.com/ Dodgeball] profiles and venues need [[hcard|hCard]] for people and organizations
** [http://www.dodgeball.com/user?uid=30209 a profile]
** [http://www.dodgeball.com/venue?vid=23551 a venue] - could also use [[hreview|hReview]] for the user reviews listed there for the venue
* [http://idubyou.com/ i dub you]
* [http://www.icq.com/people ICQ, where they show ppls profiles and have a few ways of contacting and/or connection to ppl.]

== Online Venues ==
There are many sites that offer pages that represent organizations and venues that could benefit from being marked up with hCard. [http://local.yahoo.com/ Yahoo Local] venues are marked up with hCards for example. Here are some more sites that have venues that would benefit from hCard markup.
* Yelp.com

== Plugins for and modifications of web-applications ==
Many web-applications use plugin-systems to change their behaviour and content. Most notable is probably web-forums and blogs. Many of these have a community of coders that develop plugins or code to modify the default behaviour of these web-applications. Here are some sites where it might be interesting to develop hcard-related plugins/mods.

* forum-software
** http://www.phpbb.com
* blog-software
** http://b2evolution.net

==Wikpedia hCard==
*Infobox Templates for people to add [[hcard|hCard]] to their generated markup
** [http://en.wikipedia.org/w/index.php?title=Template:Infobox_Biography&action=edit Infobox_Biography]
** [http://en.wikipedia.org/w/index.php?title=Template:Infobox_actor&action=edit Infobox_actor] which should result in actor pages, e.g. [http://en.wikipedia.org/wiki/Humphrey_Bogart Humphrey Bogart]'s page, being properly hCarded.
*Addressable buildings e.g. [http://en.wikipedia.org/wiki/The_Old_Crown%2C_Birmingham The Old Crown, Birmingham]
*Tourist attractions, e.g. [http://en.wikipedia.org/wiki/Cadbury_World Cadbury World]
*Companies, e.g. [http://en.wikipedia.org/wiki/Tesco Tesco] (note headquarters address in infobox)
*Motorway service stations, e.g. [http://en.wikipedia.org/wiki/Watford_Gap_service_station Watford Gap]
*Railway Stations, e.g. [http://en.wikipedia.org/wiki/Perry_Barr_railway_station Perry Barr]
*etc.
*See also [http://en.wikipedia.org/wiki/Wikipedia:WikiProject_Microformats WikiProject Microformats] [[User:AndyMabbett|Andy Mabbett]] 13:10, 28 Jan 2007 (PST)
* See also [[persondata|discussion of Wikipedia's Persondata]], which aligns very closely with hCard, but has additional date and place of birth & death fields. [[User:AndyMabbett|Andy Mabbett]] 13:23, 28 Mar 2007 (PDT)

==Telephone Directory Listings==
Telephone Directory Listings could usefully apply hCard to their results pages. [[User:AndyMabbett|Andy Mabbett]] 03:10, 13 Nov 2006 (PST)

e.g. (please add other examples!):
*[http://www.thephonebook.bt.com/ BT]
**Requested via [http://tinyurl.com/yhtdjy BT feedback form], 2006-11-13 [[User:AndyMabbett|Andy Mabbett]]
**BT confirm that they will consider this at their next re-build. 2006-12 [[User:AndyMabbett|Andy Mabbett]]
*[http://118118.com 118118.com]
**Requested via e-mail, 2006-11-13. [[User:AndyMabbett|Andy Mabbett]]
*[http://192.com/ 192.com]
**Requested via [http://www.192.com/support/feedback.cfm 192.com feedback form], 2007-03-07 [[User:AndyMabbett|Andy Mabbett]]
*[http://www.skype.com/intl/en-gb/download/features/skypefind/ SkypeFind]
**Requested via [http://support.skype.com/?_a=tickets&_m=submit Skype feedback form], 2007-03-16 [[User:AndyMabbett|Andy Mabbett]]
*[http://www.whitepages.com/ White Pages (USA/ Canada)]
*[http://www.whitepages.com.au/ White Pages (Australia)]
*[http://www.switchboard.com/ Stitchboard (USA)]]
*[http://people.yahoo.com/ Yahoo! People Search (USA)]
*[http://www.whowhere.com/ Lycos People Search (USA)]
*[http://www.bsnl.co.in/map.htm BSNL (India)]

==Postal (ZIP) code Finders==
Postal code Finders could usefully apply hCard to their results pages. [[User:AndyMabbett|Andy Mabbett]] 12:09, 13 Nov 2006 (PST)

e.g. (please add other examples!):
*[http://pol.royalmail.com/dda/txt/pf.asp Royal Mail] (UK)
**Requested via [http://tinyurl.com/ya4hzu Royal Mail feedback form], 2006-11-13 [[User:AndyMabbett|Andy Mabbett]]
**Acknowledged 2006-11-30. [[User:AndyMabbett|Andy Mabbett]]

==Government hCard==
===UK Gov. hCard===
* Parliament: [http://www.parliament.uk/directories/hciolists/alms.cfm Alphabetical List of Members of Parliament] (see also [http://www.parliament.uk/directories/directories.cfm other lists of MPs and Lords]). [[User:AndyMabbett|Andy Mabbett]]

===Europe Gov. hCard===
* e.g. [http://www.europarl.org.uk/uk_meps/westmidlands.asp UK MEPs]

=== MAPLight ===
http://maplight.org/ can use a bunch of hCard markup, e.g.
* individual politicians, like [http://www.maplight.org/map/us/legislator/408/individuals Nancy Pelosi]
* mentions of politicians on interest pages like [http://www.maplight.org/map/us/interest/L1300 Teachers unions]
* their contact info of course: http://www.maplight.org/contact
Requested by [[User:Tantek|Tantek]] 12:13, 30 May 2007 (PDT) in person at the NetSquared2007 conference.

== Organization Contacts ==
Many companies and organizations have about or contact pages that could benefit from being marked up with hCard. [http://technorati.com/about/contact.html Technorati's contact page] for example is both marked up with hCard and has a convenient "Add to Address Book" hCard to vCard converter link. The following company sites could benefit from similar markup (and, until user agents support hCards natively, "Add to Address Book" links). [[User:Tantek|Tantek]] 17:44, 13 Dec 2006 (PST)
*Adobe
**[http://www.adobe.com/aboutadobe/offices.html Adobe offices]
***Requested using contact form, 2006-12-14. [[User:AndyMabbett|Andy Mabbett]]
*Google
**Contacts, e.g.
*** [http://www.google.com/intl/en/contact/index.html Google.com contact page]
**** Requested by asking Google Employee KevinMarks via instant messaging to add hCard to that page along with a "Add to Address Book" link [[User:Tantek|Tantek]] 11:32, 10 Apr 2007 (PDT) and RyanKing in IRC
*** [http://www.google.co.uk/intl/en/contact/index.html Google UK], etc.
*[http://www.mozilla.com/ Mozilla]
**[http://www.mozilla.com/en-US/about/legal.html Mozilla legal notices]
*Opera
**People, e.g. [http://people.opera.com/howcome/ Håkon Wium Lie]; could also be hResume
*W3C
**[http://www.w3.org/Consortium/contact W3C contact]
**[http://www.w3.org/People/all W3C Staff listing] and individual pages, e.g. [http://www.w3.org/People/Berners-Lee/ Tim Berners-Lee]
***Requested by e-mail. [[User:AndyMabbett|Andy Mabbett]]

== Individual hCards ==
Getting these sites to at least add hCard to their home page or contact info page and then [http://pingerati.net/ping/ ping Pingerati] would be an excellent start with getting them some experience with microformats and thinking about adding microformats to other places in their sites that make sense:
* [http://metaweb.com/ Metaweb Technologies]
** [http://www.freebase.com/ Freebase ]

==Other hCard==
* [http://www.imdb.com/ Internet Movie Database] (IMDb) for people (real, not characters), e.g. [http://www.imdb.com/name/nm0000007/ Humphrey Bogart]. [[User:AndyMabbett|Andy Mabbett]] 02:49, 13 Nov 2006 (PST)
**Can't find contact info! [[User:AndyMabbett|Andy Mabbett]]
**See also example, below.
*Wikitravel
**e.g. [http://wikitravel.org/en/Birmingham_%28England%29 Wikitravel - Birmingham]
***[http://microformats.org/wiki?title=User_talk:MarkJaroski&curid=2699&diff=0&oldid=10663&rcid=19955 Wikitravel is about to hugely roll out hCard] Mark Jaroski
***See also [http://wikitravel.org/en/Wikitravel:Microformats Wikitravel:Microformats]
*[http://orlabs.oclc.org/Identities/ WorldCat Identities]
**The recently prototyped WorldCat Identities provides pages for 20 million 'identities', mainly authors and people who are the subjects of published titles.
**Requested by feedback form, 2007-03-09 [[User:AndyMabbett|Andy Mabbett]]
** No reply, as of 02:02, 13 Jun 2007 (PDT)
*[http://geonames.org GeoNames]
**Requested by e-mail, 2007-06-07 [[User:AndyMabbett|Andy Mabbett]]
**Reply confirms that they will deploy hCard and Geo
*[http://www.oup.com/oxforddnb/info/ Oxford Dictionary of National Biography] (ODNB); subscription based, but [http://www.oxforddnb.com/public/lotw/ some ODNB articles available free]. All 56,000+ entries have Date of Death.
*[http://www.findagrave.com/ Find-a-Grave] e.g. [http://www.findagrave.com/cgi-bin/fg.cgi?page=gr&GRid=680 Karl Marx]. Most entries have Date of Death.

== Successes ==

*Details of hCard should be added to the [http://www.imc.org/pdi/ Internet Mail Consortium's vCard page]
**Requested by e-mail, 2006-11-24 [[User:AndyMabbett|Andy Mabbett]]
**'''Success''' achieved 2006-11-25. [[User:AndyMabbett|Andy Mabbett]]
*W3C
**'''W3C webmaster''' [http://www.w3.org/People/Jean-Gui/ Jean-Guilhem Rouel] now has an hCard. [[User:AndyMabbett|Andy Mabbett]] 15:41, 4 Apr 2007 (PDT)
*Wikipedia-EN - starting to roll-out
**UK Railway station template, e.g. [http://en.wikipedia.org/wiki/Birmingham_New_Street Birmingham New Street station] (includes Geo)
* [http://jpgmag.com/ JPG magazine] - have sent email to their web developer with sample marked up member profile with [[hcard|hCard]] and [[xfn]] [[rel-me|rel="me"]]. [[User:Tantek|Tantek]] 23:48, 21 Feb 2007 (PST)
** [[hcard|hCard]]+[[xfn]] [[rel-me|rel="me"]] support as of March 2007.
* Twitter.com - working on it [[User:Tantek|Tantek]] 17:44, 13 Dec 2006 (PST).
** Completed [[hcard|hCard]]+[[xfn]]+[[hatom|hAtom]] support last week with help from Chris Messina. [[User:Tantek|Tantek]] 12:01, 16 May 2007 (PDT)
* Consumating.com - working on it [[User:Tantek|Tantek]] 17:44, 13 Dec 2006 (PST)
** [[hcard|hCard]] profiles, [[hcalendar|hCalendar]] events as of March 2007.
* [http://sunlightlabs.com/api/ SunlightLabs API] provides profiles for US Congresspeople. Their [http://sunlightlabs.com/api/masterref/megatable.php megatable] could easily be marked up with hCard, and their APIs could return hCards and hCard fields.
** [[User:Tantek|Tantek]] 12:30, 20 Apr 2007 (PDT) contacted them and requested that they add hCard to megatable, consider a GethCard API method, and potentially a GethResume API method for each person.
** [[User:CarlAnderson|CarlAnderson]] 26 Apr 2007: http://sunlightlabs.com/api does now have a people.getHCard.php API method to get an hCard for every member of congress. See the documentation at http://sunlightlabs.com/api/people.getHCard.php. An example call: http://api.sunlightlabs.com/people.getHCard.php?id=fakeopenID1
** [[User:CarlAnderson|CarlAnderson]] 30 Apr 2007: I created a page of hCards for every member of congress: http://sunlightlabs.com/api/hcards/index.php

==See also==
{{hcard-related-pages}}
*[[advocacy]]

User:WilleRaab

2007-07-18T17:35:46Z

WilleRaab:

hcard-advocacy

2007-07-18T17:01:46Z

WilleRaab: /* Online Profiles */ --> added ICQ

= hCard advocacy =
Adding [[hcard|hCard]] to these sites would make them quite handy for their users and for being indexed:

== Online Profiles ==
Nearly every website that has a login has a page representing the public profile of the user that other users can see and interact with. Many such sites already [[hcard-implementations|support hCard]] (e.g. ClaimID.com, Flickr.com, Technorati.com, Zooomr.com). Here are some that I think would benefit from the addition of hCard to their profile / user pages. Feel free to add more such sites that have a social network profile-like component and I'll see what I can do. [[User:Tantek|Tantek]] 17:44, 13 Dec 2006 (PST)
* Wikimedia - including this site, Wikipedia (See [http://en.wikipedia.org/wiki/Wikipedia:WikiProject_Microformats WikiProject Microformats]), Wikitravel, etc.
**It would be nice if <nowiki>[[User:YOURNAME]]</nowiki> links generated proper (mini)hCards. ([http://microformats.org/wiki?title=to-do&diff=12177&oldid=12173#Lazyweb per SteveIvy]; moved from 'to-do')
* Alexa.com has online profiles for domains with contact information. Would be great if they could add hCard to those. 2007-04-18 [[User:Tantek]] requested of [[User:BenWest]] e.g.:
** http://www.alexa.com/data/details?url=alexa.com/
** http://www.alexa.com/data/details?url=w3.org/
* [http://dodgeball.com/ Dodgeball] profiles and venues need [[hcard|hCard]] for people and organizations
** [http://www.dodgeball.com/user?uid=30209 a profile]
** [http://www.dodgeball.com/venue?vid=23551 a venue] - could also use [[hreview|hReview]] for the user reviews listed there for the venue
* [http://idubyou.com/ i dub you]
* [http://www.icq.com/people ICQ, where they show ppls profiles and have a few ways of contacting and/or connection to ppl.]

== Online Venues ==
There are many sites that offer pages that represent organizations and venues that could benefit from being marked up with hCard. [http://local.yahoo.com/ Yahoo Local] venues are marked up with hCards for example. Here are some more sites that have venues that would benefit from hCard markup.
* Yelp.com

==Wikpedia hCard==
*Infobox Templates for people to add [[hcard|hCard]] to their generated markup
** [http://en.wikipedia.org/w/index.php?title=Template:Infobox_Biography&action=edit Infobox_Biography]
** [http://en.wikipedia.org/w/index.php?title=Template:Infobox_actor&action=edit Infobox_actor] which should result in actor pages, e.g. [http://en.wikipedia.org/wiki/Humphrey_Bogart Humphrey Bogart]'s page, being properly hCarded.
*Addressable buildings e.g. [http://en.wikipedia.org/wiki/The_Old_Crown%2C_Birmingham The Old Crown, Birmingham]
*Tourist attractions, e.g. [http://en.wikipedia.org/wiki/Cadbury_World Cadbury World]
*Companies, e.g. [http://en.wikipedia.org/wiki/Tesco Tesco] (note headquarters address in infobox)
*Motorway service stations, e.g. [http://en.wikipedia.org/wiki/Watford_Gap_service_station Watford Gap]
*Railway Stations, e.g. [http://en.wikipedia.org/wiki/Perry_Barr_railway_station Perry Barr]
*etc.
*See also [http://en.wikipedia.org/wiki/Wikipedia:WikiProject_Microformats WikiProject Microformats] [[User:AndyMabbett|Andy Mabbett]] 13:10, 28 Jan 2007 (PST)
* See also [[persondata|discussion of Wikipedia's Persondata]], which aligns very closely with hCard, but has additional date and place of birth & death fields. [[User:AndyMabbett|Andy Mabbett]] 13:23, 28 Mar 2007 (PDT)

==Telephone Directory Listings==
Telephone Directory Listings could usefully apply hCard to their results pages. [[User:AndyMabbett|Andy Mabbett]] 03:10, 13 Nov 2006 (PST)

e.g. (please add other examples!):
*[http://www.thephonebook.bt.com/ BT]
**Requested via [http://tinyurl.com/yhtdjy BT feedback form], 2006-11-13 [[User:AndyMabbett|Andy Mabbett]]
**BT confirm that they will consider this at their next re-build. 2006-12 [[User:AndyMabbett|Andy Mabbett]]
*[http://118118.com 118118.com]
**Requested via e-mail, 2006-11-13. [[User:AndyMabbett|Andy Mabbett]]
*[http://192.com/ 192.com]
**Requested via [http://www.192.com/support/feedback.cfm 192.com feedback form], 2007-03-07 [[User:AndyMabbett|Andy Mabbett]]
*[http://www.skype.com/intl/en-gb/download/features/skypefind/ SkypeFind]
**Requested via [http://support.skype.com/?_a=tickets&_m=submit Skype feedback form], 2007-03-16 [[User:AndyMabbett|Andy Mabbett]]
*[http://www.whitepages.com/ White Pages (USA/ Canada)]
*[http://www.whitepages.com.au/ White Pages (Australia)]
*[http://www.switchboard.com/ Stitchboard (USA)]]
*[http://people.yahoo.com/ Yahoo! People Search (USA)]
*[http://www.whowhere.com/ Lycos People Search (USA)]
*[http://www.bsnl.co.in/map.htm BSNL (India)]

==Postal (ZIP) code Finders==
Postal code Finders could usefully apply hCard to their results pages. [[User:AndyMabbett|Andy Mabbett]] 12:09, 13 Nov 2006 (PST)

e.g. (please add other examples!):
*[http://pol.royalmail.com/dda/txt/pf.asp Royal Mail] (UK)
**Requested via [http://tinyurl.com/ya4hzu Royal Mail feedback form], 2006-11-13 [[User:AndyMabbett|Andy Mabbett]]
**Acknowledged 2006-11-30. [[User:AndyMabbett|Andy Mabbett]]

==Government hCard==
===UK Gov. hCard===
* Parliament: [http://www.parliament.uk/directories/hciolists/alms.cfm Alphabetical List of Members of Parliament] (see also [http://www.parliament.uk/directories/directories.cfm other lists of MPs and Lords]). [[User:AndyMabbett|Andy Mabbett]]

===Europe Gov. hCard===
* e.g. [http://www.europarl.org.uk/uk_meps/westmidlands.asp UK MEPs]

=== MAPLight ===
http://maplight.org/ can use a bunch of hCard markup, e.g.
* individual politicians, like [http://www.maplight.org/map/us/legislator/408/individuals Nancy Pelosi]
* mentions of politicians on interest pages like [http://www.maplight.org/map/us/interest/L1300 Teachers unions]
* their contact info of course: http://www.maplight.org/contact
Requested by [[User:Tantek|Tantek]] 12:13, 30 May 2007 (PDT) in person at the NetSquared2007 conference.

== Organization Contacts ==
Many companies and organizations have about or contact pages that could benefit from being marked up with hCard. [http://technorati.com/about/contact.html Technorati's contact page] for example is both marked up with hCard and has a convenient "Add to Address Book" hCard to vCard converter link. The following company sites could benefit from similar markup (and, until user agents support hCards natively, "Add to Address Book" links). [[User:Tantek|Tantek]] 17:44, 13 Dec 2006 (PST)
*Adobe
**[http://www.adobe.com/aboutadobe/offices.html Adobe offices]
***Requested using contact form, 2006-12-14. [[User:AndyMabbett|Andy Mabbett]]
*Google
**Contacts, e.g.
*** [http://www.google.com/intl/en/contact/index.html Google.com contact page]
**** Requested by asking Google Employee KevinMarks via instant messaging to add hCard to that page along with a "Add to Address Book" link [[User:Tantek|Tantek]] 11:32, 10 Apr 2007 (PDT) and RyanKing in IRC
*** [http://www.google.co.uk/intl/en/contact/index.html Google UK], etc.
*[http://www.mozilla.com/ Mozilla]
**[http://www.mozilla.com/en-US/about/legal.html Mozilla legal notices]
*Opera
**People, e.g. [http://people.opera.com/howcome/ Håkon Wium Lie]; could also be hResume
*W3C
**[http://www.w3.org/Consortium/contact W3C contact]
**[http://www.w3.org/People/all W3C Staff listing] and individual pages, e.g. [http://www.w3.org/People/Berners-Lee/ Tim Berners-Lee]
***Requested by e-mail. [[User:AndyMabbett|Andy Mabbett]]

== Individual hCards ==
Getting these sites to at least add hCard to their home page or contact info page and then [http://pingerati.net/ping/ ping Pingerati] would be an excellent start with getting them some experience with microformats and thinking about adding microformats to other places in their sites that make sense:
* [http://metaweb.com/ Metaweb Technologies]
** [http://www.freebase.com/ Freebase ]

==Other hCard==
* [http://www.imdb.com/ Internet Movie Database] (IMDb) for people (real, not characters), e.g. [http://www.imdb.com/name/nm0000007/ Humphrey Bogart]. [[User:AndyMabbett|Andy Mabbett]] 02:49, 13 Nov 2006 (PST)
**Can't find contact info! [[User:AndyMabbett|Andy Mabbett]]
**See also example, below.
*Wikitravel
**e.g. [http://wikitravel.org/en/Birmingham_%28England%29 Wikitravel - Birmingham]
***[http://microformats.org/wiki?title=User_talk:MarkJaroski&curid=2699&diff=0&oldid=10663&rcid=19955 Wikitravel is about to hugely roll out hCard] Mark Jaroski
***See also [http://wikitravel.org/en/Wikitravel:Microformats Wikitravel:Microformats]
*[http://orlabs.oclc.org/Identities/ WorldCat Identities]
**The recently prototyped WorldCat Identities provides pages for 20 million 'identities', mainly authors and people who are the subjects of published titles.
**Requested by feedback form, 2007-03-09 [[User:AndyMabbett|Andy Mabbett]]
** No reply, as of 02:02, 13 Jun 2007 (PDT)
*[http://geonames.org GeoNames]
**Requested by e-mail, 2007-06-07 [[User:AndyMabbett|Andy Mabbett]]
**Reply confirms that they will deploy hCard and Geo
*[http://www.oup.com/oxforddnb/info/ Oxford Dictionary of National Biography] (ODNB); subscription based, but [http://www.oxforddnb.com/public/lotw/ some ODNB articles available free]. All 56,000+ entries have Date of Death.
*[http://www.findagrave.com/ Find-a-Grave] e.g. [http://www.findagrave.com/cgi-bin/fg.cgi?page=gr&GRid=680 Karl Marx]. Most entries have Date of Death.

== Successes ==

*Details of hCard should be added to the [http://www.imc.org/pdi/ Internet Mail Consortium's vCard page]
**Requested by e-mail, 2006-11-24 [[User:AndyMabbett|Andy Mabbett]]
**'''Success''' achieved 2006-11-25. [[User:AndyMabbett|Andy Mabbett]]
*W3C
**'''W3C webmaster''' [http://www.w3.org/People/Jean-Gui/ Jean-Guilhem Rouel] now has an hCard. [[User:AndyMabbett|Andy Mabbett]] 15:41, 4 Apr 2007 (PDT)
*Wikipedia-EN - starting to roll-out
**UK Railway station template, e.g. [http://en.wikipedia.org/wiki/Birmingham_New_Street Birmingham New Street station] (includes Geo)
* [http://jpgmag.com/ JPG magazine] - have sent email to their web developer with sample marked up member profile with [[hcard|hCard]] and [[xfn]] [[rel-me|rel="me"]]. [[User:Tantek|Tantek]] 23:48, 21 Feb 2007 (PST)
** [[hcard|hCard]]+[[xfn]] [[rel-me|rel="me"]] support as of March 2007.
* Twitter.com - working on it [[User:Tantek|Tantek]] 17:44, 13 Dec 2006 (PST).
** Completed [[hcard|hCard]]+[[xfn]]+[[hatom|hAtom]] support last week with help from Chris Messina. [[User:Tantek|Tantek]] 12:01, 16 May 2007 (PDT)
* Consumating.com - working on it [[User:Tantek|Tantek]] 17:44, 13 Dec 2006 (PST)
** [[hcard|hCard]] profiles, [[hcalendar|hCalendar]] events as of March 2007.
* [http://sunlightlabs.com/api/ SunlightLabs API] provides profiles for US Congresspeople. Their [http://sunlightlabs.com/api/masterref/megatable.php megatable] could easily be marked up with hCard, and their APIs could return hCards and hCard fields.
** [[User:Tantek|Tantek]] 12:30, 20 Apr 2007 (PDT) contacted them and requested that they add hCard to megatable, consider a GethCard API method, and potentially a GethResume API method for each person.
** [[User:CarlAnderson|CarlAnderson]] 26 Apr 2007: http://sunlightlabs.com/api does now have a people.getHCard.php API method to get an hCard for every member of congress. See the documentation at http://sunlightlabs.com/api/people.getHCard.php. An example call: http://api.sunlightlabs.com/people.getHCard.php?id=fakeopenID1
** [[User:CarlAnderson|CarlAnderson]] 30 Apr 2007: I created a page of hCards for every member of congress: http://sunlightlabs.com/api/hcards/index.php

==See also==
{{hcard-related-pages}}
*[[advocacy]]