Microformats Wiki - User contributions [en]

mobile

2009-11-04T19:58:28Z

DanC: share my experience with the sidekick

<h1>mobile</h1>

'''This page is a stub and would benefit from your contributions!'''

{{TOC-right}}
Mobile and microformats make for a particularly powerful combination. Microformats help users complete more tasks with fewer steps, and requiring fewer steps is especially important in mobile applications. This page lists current known mobile support of microformats, and ideas/suggestions for mobile applications that could use microformats.

== mobile support ==
=== Treo ===
The Treo browser has good integration with the Treo address book and calendar.

* '''[[hCard]] support.''' Clicking on a "Add to Address Book" link (e.g. on [http://technorati.com/about/contact.html Technorati's contact page]) will prompt the user to add that [[hCard]] directly to their Treo address book.

* '''[[hCalendar]] support.''' Clicking on an "Add to Calendar" link (e.g. like on the [[events]] page) will prompt the user to add [[hCalendar]] events directly to their Treo calendar. (Note: the "Subscribe to" links that use <code>webcal:</code> do not appear to currently work on the Treo.)

=== Nokia ===
* The S60 3rd generation browser can handle vcards and icals (as those generated by X2V and technorati) extracted from hcards and vcards very well.

List of models: N80, N95, ''(please update)''.

=== Sony Ericsson ===
* The Sony Ericsson W810i can handle vCards generated by X2V (it also supports hCard to vCard to QR-Code (http://www.microform.at/hcard2qrcode/))

== mobile non support ==
Smartphones that should know better! I.e. they have a browser, they address books and/or calendar programs, and yet, they're not connected! They might even sync with a desktop that supports vCard and iCalendar (and maybe even hCard and hCalendar), but they lack built-in support.

=== BlackBerry ===
No support for hCard/vCard/hCalendar/iCalendar in BlackBerry 8700, 81xx, 88xx models. Anybody have experience either way with BlackBerry 9000?
* see [[mobile-advocacy]] for more.

=== iPhone ===
No support for hCard/vCard/hCalendar/iCalendar in first generation iPhone / Safari / Webkit.
No support on iPhone 3G software v2.0.2(5C1), clicking the "add to address book" link as above results in a message saying "Safari can't download this file".
This is particularly sad for the iPhone as the '''iPod''' has supported vCard and iCalendar for many years!
* see [[mobile-advocacy]] for more.

=== Sidekick ===

On a [http://en.wikipedia.org/wiki/Danger_Hiptop#T-Mobile_Sidekick_LX_.28Danger.2FSharp.29 Sidekick LX] (2008, I think; maybe 2007), it treats text/directory as text/plain; that is: if you use h2v to get data out of a page with hCard, you get some text back; text that's less readable and useful than the hCard. This is pretty disappointing, given that the sidekick can send contacts via email. Perhaps it's not all that surprising, though, since this sidekick doesn't do anything when *receiving* vcards.

== mobile application thoughts ==
If this section gets too big, we can move it to a separate page like [[mobile-user-interface]].

=== browser address book integration ===
Every mobile browser should auto-detect [[hCards]] and provide the user a simple/unobtrusive user interface to add them to their mobile address book.

Example: you are browsing a business site, or business listings (e.g. on Google Maps) which list business name, telephone number, address, URL etc. With a simple click or two, it should be possible to save those listings in your address book for future reference or navigation (see below).

=== browser calendar integration ===
Every mobile browser should auto-detect [[hCalendar]] events and provide the user a simple/unobtrusive user interface to add (or subscribe to) them to their mobile address book.

Example: you are browsing an event site (e.g. Upcoming.org), or event listings on a business site, and see event names, start/end times, locations, etc. With a simple click or two, it should be possible to save those events in your calendar for future reference / alarms etc.

=== mapping and navigation ===
[[adr]] and [[geo]] microformats are useful for mobile mapping and navigation applications. (from tweet: [http://twitter.com/microformats/statuses/916437155]).

The most obvious thing to do is extending support for [[geo]] so you can get directions to places from browsers, so you could, for example, get off the train, go to Upcoming.org on your mobile, click the address and have the mobile mapping applications walk you there. (from tweets [http://twitter.com/markng/statuses/916433126], [http://twitter.com/markng/statuses/916436304]).

=== url dialing ===
Most phones have a way of invoking a call from the browser or from applications built in the native languages (JavaME, Python etc.) - it'd be useful if you could have a really simple way of putting in a URI, and it finding the relevant hCard on the page and auto-dials it. I can remember "companyname.com" but not some long phone number. I'm thinking of building something broadly on this line using JavaME, backed by a web service to get the numbers and return them to the device (favouring hCards, but regexing for things that look like phone numbers if it doesn't find any). This came to me a while back when I was walking around London trying to find a shop - I knew their URL but had no idea of their phone number. --[[User:TomMorris|TomMorris]] 05:07, 12 Sep 2008 (PDT)

=== effortlessly add a contact to the address book ===
By using a bit of URL voodoo we can provide a [http://en.wikipedia.org/wiki/QR_Code QR Code] (here's a [http://reader.kaywa.com/ reader])so that the user can point their phone at the image and following the URL, a popup appears prompting them to add the contact to their address book. '''Downside:''' It requires internet access.

Example: [http://chart.apis.google.com/chart?chs=500x500&cht=qr&chl=http://suda.co.uk/projects/microformats/hcard/get-contact.php?uri=http://id.andr3.net] (Thank Brian Suda for X2V!) --[[User:Andr3|Andr3]] 01:19PM, 12 Sep 2008 (WEST)

== thanks ==
* [http://twitter.com/bryanrieger @bryanrieger] for [http://twitter.com/bryanrieger/statuses/916416344 asking the question] on Twitter.
* [http://twitter.com/markng @markng] for providing some ideas with user scenarios.

== see also ==
* [[advocacy]]
* [[mobile-advocacy]]
* [[user-interface]]
* [[operator-phone-tests]]

hcard-implementations

2009-04-28T04:31:34Z

DanC: vcardin.py converts .vcf to .html

<h1>hCard Implementations</h1>
{{TOC-right}}

This page is an '''informative''' section of the [[hcard|hCard specification]].

The following implementations have been developed which either generate or parse [[hcard|hCards]]. If you have such an hCard implementation, feel free to add it to '''the top''' of the New Implementations section. If you have a page or site which just ''publishes'' hCards, please use [[hcard-examples-in-wild]] instead.

== New Implementations ==
Add new implementations here for evaluation and classification into the below taxonomy of implementations.

* [http://www.w3.org/2002/12/cal/vcardin.py vcardin.py]: converts .vcf to .html based on a kid template; part of [http://www.w3.org/2002/12/cal/ the RDF Calendar workspace]
* [http://microform.at/hcard2qrcode/ hCard to QR-Code] -- Converts a published hCard to a vCard and displays the matching QR-Code.
* [http://code.google.com/p/verizon-contact-exporter/ Verizon Contact Exporter] -- adds hcards to a typical HTML page of contacts from someone's Verizon online address book so that they can be exported (say, if someone wants to leave Verizon)
* [http://hcard.geekhood.net/ hCard Validator] - finally!
* [http://www.cogmap.com/ Cogmap] - Cogmap has a bunch of org charts marked up with hcard. Desperately needs [[XPN]]!
* [http://www.tripit.com/ TripIt] - The TripIt contact list of your connections is marked up with hCard
* [[hAvatar]] - Wordpress plugin displaying avatars for commenters based on their hCard
* [[org.microformats.hCard]] - java hCard parser and creator.
* [http://mobileonlinebusiness.com.au/uf/vCard_to_hCard_converter.html Mobile Online Business' vCard to hCard converter]
*[http://www.jamplanet.com Jam] is an active address book extension for Firefox/Flock. Jam imports Vcard and various CSV formats, and can output contacts in Vcard and hCard format.
*The "[http://typo3.org/extensions/repository/view/tt_address/2.0.1/ tt_address]" extension for [http://www.typo3.com TYPO3] supports hCard since the latest release, v2.0.0
*[https://addons.mozilla.org/firefox/4106/ Operator] lets you combine pieces of information on Web sites with applications in ways that are useful. (Firefox-plugin)
*[http://rafaeloliveira.net/labs/hcard_creator.zip Wordpress hCard Creator] - I've made this simple plugin for wordpress. It adds the hCard Options submenu at Options menu, where you can create a simple hCard and put it on your blog using < ?php hcard_creator() ?> to show it. Also, it is possible to show an "export to vCard" link, which uses Brian Suda X2V. (Got send an e-mail to him regarding this)
*[http://leftlogic.com/lounge/articles/microformats_bookmarklet/ Microformats Bookmarklet] is a bookmarklet designed for IE6 and IE7, Firefox, Safari, Opera and Camino, that overlays on the current page to allow users to import individual hCards or hCalendars. Written by Remy Sharp.
*[http://domanske.de/2006/09/vcardexplorer-04/ vCardExplorer] is a Mac OS X Application, that displays VCF-Files and extracts hCards from Websites written by [http://vcardexplorer.corefault.de Daniel Kagemann].
* [http://placenamehere.com/mf/nnwextract/ Extract Microformats] is a script for NetNewsWire that supports extracting hCard and hCalendar data in blog posts (via technorati service). Written by [[User:ChrisCasciano|Chris Casciano]]
* [http://allinthehead.com/hkit/ hKit] is an open source PHP 5 parsing library with support for hCard.
* [http://kitchen.technorati.com/search Technorati Microformats Search] indexes [[hcard|hCard]], [[hcalendar|hCalendar]], and [[hreview|hReview]] as [http://tantek.com/log/2006/05.html#d31t1802 announced by Tantek].
** list of pages with indexing Issues so they can be looked into as to why data is not being extracted
** suda.co.uk/contact
** multipack.co.uk
* [http://www.webstandards.org/action/dwtf/microformats/ Dreamweaver Extension suite] from the [http://webstandards.org/ Web Standards Project] enables the authoring of hCards from within Dreamweaver 8.
* [http://scooch.gr0w.com/ Scooch] is a slide show and presentation creator that generates a [[hCard]] for individual slide show authors and comment authors with a CSS button to parse and download via [http://suda.co.uk/projects/X2V/ X2V]. Also uses [[hReview]] for slide ratings and [[rel-tag]] for categories.
* [http://blog.codeeg.com/2006/03/20/flock-tails-flocktails/ Flocktails] - port of Tails extension for Flock 0.5.12 that looks for hCards, hCalendar, xFolk and hReview and tosses them into a handy topbar
*[http://opensource.reevoo.com/2006/03/08/release-uformats-12/ uformats] is a ruby library that can parse [[hCalendar]], [[hCard]], [[hReview]] and [[rel-tag]]
* [http://blog.codeeg.com/tails-firefox-extension-03/ Tails] is a Firefox Extension that will display the presence and details of microformats ([[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], [[xfolk|xFolk]]) on a webpage. [https://addons.mozilla.org/firefox/2240/ Tails Export] is an extended version.
* [http://www.stripytshirt.co.uk/features/firefox/smartzilla Smartzilla is a Firefox Extension] that finds hCards on web pages and lets you add them to your addressbook.
* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding hCard and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].
* There is [http://flickr.com/photos/factoryjoe/68755089/ evidence of built-in hCard support in the Konqueror browser]. Specifically, Konqueror 3.5, in KDE 3.5 (kubuntu Breezy w/ update).
* There is [http://tagcamp.org/index.cgi?ContactList evidence of a kwiki plugin for hCards]. Update: the [http://svn.kwiki.org/cwest/Kwiki-hCard/ hCard kwiki plugin svn repository]. See the [http://microwiki.caseywest.com/index.cgi?hCard documentation of the hCard kwiki plugin].
* [http://suda.co.uk/projects/X2V/ X2V] is a bookmarklet that parses hCard and produces a .vcf (vCard) stream. Note: needs to be updated as the spec is refined.
* [http://www.stripytshirt.co.uk Duncan Walker] has built [http://www.stripytshirt.co.uk/features/firefox/smartzilla a Firefox extension] that gets hCard data from a webpage, uses Brian Suda's XSL (locally) to transform it to vcard format and opens the resulting .vcf file.
* [http://george.hotelling.net/90percent/ George] has written a [http://george.hotelling.net/90percent/geekery/greasemonkey_and_microformats.php Greasemonkey user script] that detects hCards and allows users to easily add them to their address book application. Relies on the X2V web service to do the conversion.
* [http://inside.glnetworks.de/ Martin Rehfeld] has updated the work of [http://blogmatrix.blogmatrix.com/ David Janes] and produced a [[Greasemonkey]] [http://inside.glnetworks.de/2006/06/05/microformats-have-arrived-in-firefox-15-greasemonkey-06/ script] that finds many microformat elements, including hCards, and [http://blog.davidjanes.com/mtarchives/2005_08.html#003379 provides a popup menu of actions]. The hCard to vCard conversion is done internally within the script. ''This will work with FireFox 1.5+/GreaseMonkey 0.6.4+ now.''
* [http://diveintomark.org/ Mark Pilgrim] has also written an [http://diveintomark.org/projects/greasemonkey/hcard/ hCard parser Greasemonkey user script]. It is self-contained and does not rely on the X2V web service.
* [http://www.oliverbrown.me.uk/2005/09/03/a-working-microformats-extension-to-simplexml/ Oliver Brown] has written an "extension" to [http://www.php.net/simplexml SimpleXML] that gives simple access to hCard information in PHP 5.
* [http://thedredge.org/ Andrew D. Hume] has built a system (Wordpress plugin?) for [http://thedredge.org/2005/06/using-hcards-in-your-blog/ using hCards in your blog] to represent people leaving comments on blog posts.
* [http://greenbytes.de/tech/webdav/rfc2629.xslt rfc2629.xslt] now attempts to generate hCard information ([http://ietf.org/rfc/rfc2629 RFC2629] is an XML format for authoring RFCs and Internet Drafts, see [http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html example document])
* [http://tantek.com/microformats/buddylist2hcards.html iChat buddy list to hCards] - Open source AppleScript to automatically convert one's buddy list in the MacOSX iChat AIM client into a valid XHTML 1.0 Strict list of hCards.
* [http://dev.w3.org/cvsweb/2001/palmagent/ palmagent] is a collection of palmpilot and sidekick tools. It includes X2V derivatives xhtml2hcard.xsl and toICal.xsl plus some [http://dev.w3.org/cvsweb/2001/palmagent/hcardTest.html hcardTest] materials
* [http://www.openpsa.org/ OpenPsa 2.x] CRM application uses hCard for all person listings. The widget is [http://www.midgard-project.org/midcom-permalink-922834501b71daad856f35ec593c7a6d reusable across Midgard CMS]
* [http://www.metonymie.com Emiliano Martínez Luque] has written an experimental [http://www.metonymie.com/hCard_extract/app.html hCard finder and structured search application] that finds hCards within a given set of URLs and returns the ones that match the specified search criteria.
* [http://www.milkcarton.be/apps/lustro Lustro] is a free and open source Mac OS X application that exports your Address Book contacts to CSV, tab delimited, Google Contacts and hCards off course. It creates a single XHMTL webpage with all your contacts as hCards.


==Authoring==
Implementations you can use to author, create, and publish hCards.

===Web-based Creators===
;[http://microformats.org/code/hcard/creator hCard creator]:Create your own hCards; also has a [http://www.wnas.nl/microformats/hcard/hcardCreator.html Dutch interface]. [[hcard-creator-feedback|hCard Give feedback.]]

===Blogging and CMS tools===
;[http://euphemize.net/blog/plugins/textpattern/jmc_event_manager/ Textpattern plug-in]:jmc_event_manager is a plugin for [http://textpattern.com/ Textpattern] that outputs locations and events in hCard (and hCalendar) formats. Written by [http://euphemize.net/ Joel Courtney].
;[http://wordpress.org/extend/plugins/addressbook/ Wordpress Addressbook plugin]:Display list of addresses from the blog owner's address book, each marked up as an hCard. Maintained by [http://samwilson.id.au Sam Wilson].

===Browser scripts and plug-ins===
Browser plugins that work with existing authoring tools:
; Any browser with javascript and a little bit of CSS : [http://microformats.org/code/hcard/creator microformats.org hCard creator] (see also [http://tantek.com/ Tantek]'s original [http://tantek.com/microformats/hcard-creator.html hCard creator on tantek.com].

===Desktop Authoring Tools===
* ...

==Search and Discovery==
* [http://kitchen.technorati.com/search Technorati Microformats Search] indexes [[hcard|hCard]], [[hcalendar|hCalendar]], and [[hreview|hReview]] as [http://tantek.com/log/2006/05.html#d31t1802 announced by Tantek].
* [http://leftlogic.com/info/articles/microformats_bookmarklet Microformats Bookmarklet] is a bookmarklet designed for Safari (works in Firefox and Camino) that overlays on the current page to allow users to import individual [[hcard|hCards]] or [[hcalendar|hCalendars]]. Written by [http://leftlogic.com Remy Sharp].



==Conversion and Import==
Implementations you can use to importing into an address book application, typically by converting hCard to vCard.

===Web Services===
These return vCard (.vcf) and other contact formats for easy importing into typical address book programs or other processing.
* [http://www.tomota.de www.tomota.de] Online address book that allows to import, export and convert hCard into vCard, ldif, csv and plain text.

* ...

===Firefox Greasemonkey Plugins===
* [http://userscripts.org/scripts/show/36879 Oomph for GreaseMonkey] - Injects the [http://www.visitmix.com/lab/oomph Oomph] javascript for Greasemonkey

===Aggregators===
* ...

===Forms===
* [http://lib.omnia-computing.de/hcardmapper hCard Mapper] maps hCards onto form fields (Javascript based)

==Browsing==
Implementations that detect, display and otherwise highlight hCards in pages.
* ...

===Firefox extension===

[http://www.kaply.com/weblog/operator Operator] - This extension is casual-user, advanced-user and developer friendly. Very customizable and unobstrusive.

===Internet Explorer extension===

[http://www.visitmix.com/lab/oomph Oomph] - This Add-In to Internet Explorer will light up on pages with hCards.

===Flock extension===
* ...

==Open Source==

Open source libraries of hCard parsers and other related code for building hCard implementations. Note: it is very likely that above implementations may be duplicated in this section. That's ok.

;Javascript
: The [http://microformats.org/code/hcard/creator hCard creator] ([[hcard-creator-feedback|hCard creator feedback]]) is a very simple, yet illustrative, open source user interface / form / script which creates an hCard in real-time as you type in a set of contact information.
;Perl
* [http://search.cpan.org/~ussjoin/Data-Microformat-0.01/lib/Data/Microformat/hCard.pm Data::Microformat] - CPAN module for both creating and parsing hCards
;PHP
* [[hKit]]
;Python:
* [http://tommorris.org/files/gmail2hcard-py.txt gmail2hcard-py.txt] - for converting Gmail CSV address book export to hCards
;Java:
* [[org.microformats.hCard]]
;Objective-C
* [http://www.milkcarton.be/apps/lustro Lustro] is a free and open source Mac OS X application that exports your Address Book contacts to CSV, tab delimited, Google Contacts and hCards off course. It creates a single XHMTL webpage with all your contacts as hCards.

== Additional Applications ==
This section should probably be incorporated into [[hcard-brainstorming]].

There are numerous potential additional uses and applications for hCards on the Web. The following are merely a few thoughts and possibilities that folks have come up with:

* As an open standard/format for [http://www.gravatar.com/ Gravatars].
** Like [http://alper.nl/cgi-bin/OpenAvatar.py?url=http://tantek.com this].
** Wordpress plugin with hCard based replacement for gravatar is in the make. [[User:Alper|Alper]] 12:59, 8 Aug 2007 (PDT)
* Marking up individual authors of blog posts on a group blog
* Marking up people's names and URLs in a blogroll
* Any reference to people in blog posts (e.g. when citing them, or referencing them, or describing them, by name).
* ...

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

irc

2008-08-22T18:45:26Z

DanC: trouble reaching the logs

<h1>#microformats on freenode</h1>
{{TOC-right}}

The microformats channel is hosted on the freenode.net server. See [[irc#Joining_a_server_and_channel|Joining a server and channel]] help for further information.

The idea of having IRC meetups (a set time for a meeting on IRC) has been suggested by [[User:RyanKing|Ryan King]], as it appears to work well for the WordPress community and may help us from time-to-time. As of yet, there are no plans to have meetups.

== Logs ==

[http://rbach.priv.at/Microformats-IRC/ IRC Logs] are available, as well as an [http://microformat.makedatamakesense.com/log_feed/ atom feed] to keep you up to date.

''DNS for rbach.priv.at seems to be down today. Anybody got a work-around?'' [[User:DanC|DanC]] 11:45, 22 Aug 2008 (PDT)

== People on IRC ==

See our [[irc-people|list of IRC regulars]] and their normal timezones.

Our channel has regular admins, who are also mailing list and wiki admins. If you want to get their attention, just say "adminhelp".

==Bots on IRC==

The IRC channel uses these bots:

* [[mfbot]] - logs all edits to this wiki.
* [[mflogbot]] - logs the irc channel itself to archives on the web. (Contact: [[User:RobertBachmann|Robert Bachmann]])
* [http://joiwiki.ito.com/joiwiki/index.cgi?jibot jibot]

=== Greeting Bot ===

To display a brief description of who you are each time you join the channel, you can use “JiBot” to create a definition for your username. To do so pass the <tt>?def</tt> command using something like the following convention (be brief):

<code>?def jdoe is John Doe and can be found online at <nowiki>http://www.example.com</nowiki></code>

More information about using JiBot commands can be found on the [http://joiwiki.ito.com/joiwiki/index.cgi?jibot jibot website]

= Getting started with IRC =

==Basic commands==
'''Please note:''' These directions relate specifically to the services that [http://freenode.net/ Freenode] offers. Other IRC servers may differ with the services they offer and how to operate them.

===Joining a server and channel===
Most clients will offer you a connection dialogue showing the required fields for connection. The details to connect to the server are:

*Server: <code>irc.freenode.net</code>
*Port: <code>6667</code> (usually default)

You should also fill in any fields to set your alias, real name and email address. If available, save these settings for later to speed up connecting in future.

More on setting a password protected alias can be [[irc#Creating_a_registered_nickname|read here]].

Once connected, you will most likely be presented with the "MOTD" (message of the day). For the first visit, it is advisable to read this to find out about the server's policies and other important pieces of news and help, otherwise it can be ignored and you can either [[irc#Creating_a_registered_nickname|authenticate your alias]] or join a channel.

Your client may display to you a listing of all available channels. Locate <code>#microformats</code> and select to join, or type <code>'''/join #microformats'''</code> into the command line available to you in your client (where you've just been shown your connection).

Assuming you've connected correctly, you should now find youself in the microformats channel!

More detailed, but general, advice can be [http://www.irchelp.org/irchelp/irctutorial.html#intro read here].

===Creating a registered nickname===
Registration means that a password becomes associated with your alias/nickname/sign-in name and from the point of registration authorisation is required to communicate using that alias.

Registration of a nickname is required for some channels, and should be done to protect your identity.

To register with [http://freenode.net Freenode], you must communicate with their service known as NickServ. The two basic command you will need to get started are:

For registration: <code>/msg nickserv register ''password''</code>

For authentication (login): <code>/msg nickserv identify ''password''</code>

With <code>''password''</code> being a value of your choice. You can also associate an email address with your nickname, which is optional, but advisable, should you want to request a password retrieval:

To add your email address: <code>/msg nickserv set email ''email''</code>

Where <code>''email''</code> is your email address.

Your client may offer you an option to set your alias and password, so that you will not have to manually enter this information on each join. Refer to your client's help files for more on this.

These commands can be typed directly into the server window upon join, or whilst in a channel, just as you would normally send a message.

More detailed user registration command information can be found in [http://freenode.net/faq.shtml#userregistration Freenode's FAQ]

===Communicating===

Sending a message to a channel may be as simple as joining the channel and typing into the window, just as you would with an Instant Messenger. You can refer to your client's help files for quicker/alternative methods of doing the following. For all clients the following commands are available (the parts in bold must be used, but are not seen by others):

'''Sending a message to the entire channel you are currently in:'''

Command: '''/msg''' ''Hello world!''

Result: '''<Bill> Hello world!'''

'''Sending an action/emotive/3rd person statement:'''

Command: <code>'''/me''' ''dances a code jig''</code>

Result: '''''Bill dances a code jig'''''

'''Sending a message to one person only (private chat):'''

Command: <code>'''/msg Bob''' ''Hi, would you like to code jig?''</code>

Result (for Bob only): '''<Bill> Hi, would you like to code jig?'''

==Clients==

The following clients are recommended by #microformats participants:

===Windows===

* [http://www.mirc.com/ mIRC] — Popular Windows client. Trial version only.
* [http://xchat.org/ X-Chat] — Popular cross-platform client. [http://www.silverex.org/download/ Free Windows version] available.
* [http://www.adiirc.com/ AdiIRC] — Simple C# based IRC client.
* [http://www.miranda-im.org/ Miranda] — Lightweight, muti-protocol instant messenger.

=== Mac ===

* [http://colloquy.info Colloquy] — open source, free
* [http://sourceforge.net/projects/fire Fire] — open source, free
* [http://www.snak.com/ Snak]
* [http://xchataqua.sourceforge.net/twiki/bin/view/Main/WebHome X-Chat Aqua] — X11 based IRC chat
** now has [http://www.portableapps.org PortableApps] version — [http://www.macupdate.com/info.php/id/21685/portable-x-chat-aqua MacUpdate link]
* [http://homepage.mac.com/philrobin/conversation/ Conversation]
* [http://www.chipersoft.com/minerva/ Minerva]
* [http://www.aquaticx.com/ Xirc]

===Cross-platform===
* [http://www.hacksrus.com/~ginda/chatzilla/ Chatzilla] — Cross-platform IRC extension for Firefox
* [http://pidgin.im/ Pidgin] — Popular open-source multi-protocol windows client, using libpurple
* [http://irssi.org/ Irssi] — Unix client, often run from a shell, sometimes [http://f0rked.com/articles/irssi in conjunction with 'screen'].
* [http://jirc.hick.org/jirc/ jIRCii]

=IRC and microformats=
== hCard ==
''How do we maintain info about ircing in our hCards (nick, network, fav-channels?)?''

== Related discussions ==

* chat [[chat-examples|chat examples]], [[chat-formats|chat formats]], and [[chat-brainstorming|chat brainstorming]]

==See also==
*[[irc-meetups]]
*[[discuss|Other discussion fora]]

press

2007-09-19T15:34:49Z

DanC: InternetNews.com on GRDDL and microformats

__NOTOC__
<h1> Press </h1>

This page documents the press that [[microformats]] has received. See also microformats [[screencasts]], [[presentations]], [[podcasts]], and [[books]]. Note that some of this press may be in response to [[press-faq|the press FAQ]].

Some sources of conventional press:

* [http://news.google.com/news?q=microformat+OR+microformats&scoring=n Google News search for "microformat(s)"]
* [http://www.google.com/alerts?hl=en&q=microformat+OR+microformats&ie=UTF8&t=1 Google alert (e-mail) for "microformat(s)"]

==Press enquiries==
If you are a journalist, wanting to write or broadcast about microformats, please ask on our [irc://irc.freenode.net#microformats #microformats IRC channel] or [[mail|microformats-discuss mailing list]].

== September 2007 ==
=== URLs of mentions ===

* InternetNews.com - Sep 11, 2007 [http://www.internetnews.com/dev-news/article.php/3699101&cid=0 Microformats Hop on Semantic Web 'Griddle']

* <span class="vevent"><span class="description"><span class="dtstart">2007-09-12</span> <span class="summary">"Microformats : vendre en ligne sans boutique" - Salon ecommerce Paris - Guide du Participant</span>: <span class="url">http://www.flickr.com/photos/christopheducamp/1405921949/</span></span></span>

== August 2007 ==
=== URLs of mentions ===
* <span class="vevent"><span class="description"><span class="dtstart">2007-08-06</span> <span class="summary">PC Magazine</span>: <span class="url">http://www.pcmag.com/article2/0,1895,2167604,00.asp</span></span></span>
* <span class="vevent"><span class="description"><span class="dtstart">2007-08-03</span> <span class="summary">SitePoint</span>: <span class="url">http://www.sitepoint.com/blogs/2007/08/03/have-microformats-finally-arrived</span></span></span>
* <span class="vevent"><span class="description"><span class="dtstart">2007-08-01</span> <span class="summary">WIRED</span>: <span class="url">http://blog.wired.com/monkeybites/2007/08/google-maps-tak.html</span></span></span>
* <span class="vevent"><span class="description"><span class="dtstart">2007-08-01</span> <span class="summary">CMSWire</span>: <span class="url">http://www.cmswire.com/cms/web-20/back-to-the-future-of-the-web-what-mattered-most-001526.php</span></span></span>

== July 2007 ==
=== URLs of mentions ===
* <span class="vevent"><span class="description"><span class="dtstart">2007-07-20</span> <span class="summary">CMSWire</span>: http://www.cmswire.com/cms/enterprise-20/openid-and-microformats-become-socially-acceptable-001494.php</span></span>
* <span class="vevent"><span class="description"><span class="dtstart">2007-07-10</span> <span class="summary">Wired</span>: http://blog.wired.com/monkeybites/2007/07/tim-berners-lee.html</span></span>
* <span class="vevent"><span class="description"><span class="dtstart">2007-07-02</span> <span class="summary">Seatle Times</span>: http://seattletimes.nwsource.com/html/businesstechnology/2003770628_techsocial02.html</span></span>
* <span class="vevent"><span class="description"><span class="dtstart">2007-07-02</span> <span class="summary">Web Worker Daily</span>: http://webworkerdaily.com/2007/07/02/powncing-on-the-twitter-bird-or-not/</span></span>

=== noted and quoted ===
Remove the above two level 3 headings when all URLs of mentions are noted and quoted here.

<ul>
<li class="vevent">
<span class="description"><span class="dtstart">2007-07-18</span> <span class="summary">Forbes article on Plaxo Pushes for ''Open Social Web'' references below microformats announcements</span> (<span class="url">http://www.forbes.com/businesswire/feeds/businesswire/2007/07/18/businesswire20070718005301r1.html</span>).</span>
</li>
<li class="vevent">
<span class="dtstart">2007-07-17</span> <span class="summary">Plaxo Pushes For "Open Social Web": Endorses and implements key open standards, OpenID and microformats</span> (<span class="url">http://www.plaxo.com/about/releases/release-20070718</span>) <blockquote class="description"><p>...the company has implemented the microformats hCard and hCal as part of the all-new Plaxo 3.0 making it even easier for members to share information and support more mashups in the future. Public profiles, a new feature of the service, now use the hCard format for contact info, giving users the ability use their profile information on any of the growing list of services that consume hCard data.</p></blockquote>
</li>
<li class="vevent">
<span class="dtstart">2007-07-03</span> <span class="summary">"What's next for the Internet" in "CNNMoney.com" syndication of an article from "Business 2.0 Magazine" by Michael V. Copeland.</span> (<span class="url">http://money.cnn.com/magazines/business2/business2_archive/2007/07/01/100117068/index.htm?postversion=2007070305</span>) <blockquote class="description"><p>"We've had the problem of overpromising in this industry; a lot of us who were working on semantic Web technologies early on saw the potential and got a little excited. It has taken much longer to realize than we thought. One thing Web 2.0 has taught everybody is that simpler is better. Find something useful and iterate on that." <nowiki>[- Nova Spivack]</nowiki></p><p>Tom Coates, whose day job at Yahoo involves working on just these issues, thinks the Web 2.0 crowd is already taking care of the problem. He points to tagging and [[microformats]] that add some of the same metadata to webpages that semantic technologies offer.</p><p>"I call it the dirty semantic Web," Coates says from his London office. "It may not be the pristine Berners-Lee view of the world, but it is headed in the right direction." </p></blockquote>
</li>
</ul>

== June 2007 ==

=== URLs of mentions ===

To be processed into the below noted and quoted format:
* <span class="vevent"><span class="description"><span class="dtstart">2007-06-26</span> <span class="summary">Web Worker Daily</span>: <span class="url">http://webworkerdaily.com/2007/06/26/location-location-location-get-the-best-out-of-3-presence-apps/</span></span></span>
* <span class="vevent"><span class="description"><span class="dtstart">2007-06-25</span> <span class="summary">Ars Technica</span>: <span class="url">http://arstechnica.com/journals/microsoft.ars/2007/06/25/rumor-internet-explorer-8-beta-coming-by-year-end</span></span></span>

=== noted and quoted ===

Remove the above two level 3 headings when all URLs of mentions are noted and quoted here.

<ul>
<li class="vevent">
<span class="dtstart">2007-06-29</span> <span class="summary">"The Tech Lab: Bradley Horowitz" in "BBC News, Technology"</span> (<span class="url">http://news.bbc.co.uk/1/hi/technology/6252716.stm</span>
<blockquote class="description"><p>Where we find people codifying big blocks of entities - whether in a movie database or books or restaurants, or business entities - I am comfortable taking a pragmatic approach so long as the companies contributing their respective intellectual property are committed to open standards and strategies.</p><p>It will happen through small pieces loosely joined, and it is emerging already. Different domain <span class="notspam">specia<span class="srsly"></span>lists</span> will grab different domain patches.</p><p>Once we begin to have this information we can then put it in [[microformats]] on the web, which are machine-readable. So then in an automated fashion crawlers can take advantage of that structure. </p><p>...</p><p>The web itself is sloppy, loose and unstructured - and these, by the way, are virtues!</p><p>But in making it easy to add [[microformats]], which are just machine-readable, coded bits of structure, we let machines talk to machines and ambiguity over which restaurant I am blogging about, or which film, or which person, will end.</p><p>This represents a huge step toward the vision of the semantic web, and will not only create entirely new applications, but will also solve problems that users today have come to accept as part of "life on the web."</p><p>This structure should be optional, not imposed. The onus is on us, the builders of the tools, to make it brain dead simple to add this structure.</p></blockquote>
</li>

<li class="vevent">
<span class="dtstart">2007-06-29</span> <span class="summary">'''"<span lang="fr">Les microformats donnent du sens aux pages web</span>"''' in "01 Informatique" - issue 1911 by Frederic Bordage</span>. [http://www.flickr.com/photos/christopheducamp/682883268/in/photostream/] with a french interview of Tantek Çelik [http://www.flickr.com/photos/christopheducamp/682882852/in/photostream/]<span style="float:right">[http://www.flickr.com/photos/christopheducamp/682882852 http://farm2.static.flickr.com/1348/682882852_15a6587a30_m.jpg]</span>
<blockquote class="description" lang="fr"><p>Web Sémantique. Ces formats transforment les pages web en bases de données structurées. L'indexation devient ainsi plus riche et plus pertinente. ''"Une approche du web sémantique pragmatique et simple à mettre en oeuvre"''. C'est ainsi que François Goube, PDG du moteur de recherche JobiJoba.com qualifie les microformats. (...)</p></blockquote>
</li>

<li class="vevent">
<span class="dtstart">2007-06-21</span> <span class="summary">"Microformats: People First, Machines Second" in "Electronic Design" by William Wong. ED Online ID #15742.</span> (<span class="url">http://www.elecdesign.com/Articles/ArticleID/15742/15742.html</span>
<blockquote class="description"><p>It's amazing what you can find bouncing around the Internet. I stumbled across microformats while looking for something else. Microformats are a way of embedding semantic information on a Web page. They're designed to augment human-readable versions so software can easily and accurately extract the same information. Also, they're based on a small set of open data formats built upon existing and widely adopted standards.</p></blockquote>
</li>
</ul>

== January 2007==

* <span class="vevent"><span class="description"><span class="dtstart">2007-01-15</span> <span class="summary">''Government Computer News'' (UK); Microformats get real by Joab Jackson</span>: <span class="url">http://www.gcn.com/blogs/tech/42930.html</span></span></span>
* <span class="vevent"><span class="description"><span class="dtstart">2007-01-03</span> <span class="summary">Information Week; Firefox 3: From HTML Renderer To Information Broker by Mitch Wagner</span>: <span class="url">http://www.informationweek.com/blog/main/archives/2007/01/firefox_3_from.html</span> Discusses the implications of native microformat support in Firefox.</span></span>
* <span class="vevent"><span class="description"><span class="dtstart">2007-01-02</span> <span class="summary">Read/ Write Web; Mozilla Does Microformats: Firefox 3 as Information Broker</span>: <span class="url">http://www.readwriteweb.com/archives/mozilla_does_microformats_firefox3.php</span></span></span>
* <span class="vevent"><span class="description"><span class="dtstart">2007-01-01 </span><span class="summary">''Linux Format Magazine'' (UK); What on earth... are Microformats?</span>: <span class="url">http://www.flickr.com/photos/christopheducamp/500478421/</span></span></span>

== Blog Mentions ==
While not conventionally thought of as press or news, mentions by blogs can often be significant and may superficially resemble press due to their reverse chronological, most recent post first organization.
* [http://s.technorati.com/microformat+OR+microformst Technorati search for "microformat(s)"]

== Related pages ==
<div id="2006"><div id="2005">
{{press-related pages}}
</div></div>

== See Also ==
* [[external-resources]] for external resources related to microformats.

User:DanC

2007-07-16T21:50:07Z

DanC: public domain release

My [http://microformats.org/discuss/mail/microformats-dev/2005-July/000010.html hcardTest materials, XHTML version of RFC2426, and fun with microformats] message is sort of my introduction to this community. I have since discovered the "personal intro" ritual in [http://microformats.org/discuss/mail/microformats-discuss/ microformats-discuss] and I may join that soonish.

Meanwhile, I'm working on [[hcard-tests]], [[hcard-issues]], [[to-do#Dan_Connolly|etc]].

I have written about 6 [http://dig.csail.mit.edu/breadcrumbs/taxonomy/term/26 blog posts tagged microformats] so far.

Ugh... yet another username/password out there. Oh for [http://www.openid.net/ OpenID]!

{{public-domain-release}}

directions-examples

2007-06-21T03:40:44Z

DanC: a couple year-in-flights examples

= directions examples =

Examples for a possible [[directions]] microformat.

Per the microformats [[process]], the first thing to do in the investigation/creation of a new microformat is to research existing examples of directions published on the Web.

__TOC__

== contributors ==

* JustinLilly
* TantekÇelik
* BretonSlivka
* KevinMarks
* AndyHume
* JeremyHuylebroeck
* RussNelson
*[[AndyMabbett|Andy Mabbett]]
==Examples==

Get examples from Google Maps, MSN Maps, Yahoo Maps, and note implicit schemas.

===Google Maps===

<pre>
Start address: 50 California St
San Francisco, CA 94111
End address: 10 Market St
San Francisco, CA 94111
Distance: 0.2 mi (about 24 secs)
Reverse directions

1. 1. Head east from California St - go 177 ft
2. 2. Turn right at Drumm St - go 149 ft
3. 3. Turn left at Market St - go 0.1 mi
</pre>

====source==== (via firefox's dom inspector)

<pre>
<table class="summary">
<tbody>
<tr onclick="openInfoWindow('start')" class="milestone">
<td class="name link">
<a onclick="this.blur()" href="javascript:void(0)">
Start address
</a>
:
</td>
<td class="value" id="panel_start">
50 California St
<br />
San Francisco, CA 94111
<br />
</td>
</tr>
<tr onclick="openInfoWindow('end')" class="milestone">
<td class="name">
<a onclick="this.blur()" href="javascript:void(0)">
End address
</a>
:
</td>
<td class="value" id="panel_end">
10 Market St
<br />
San Francisco, CA 94111
<br />
</td>
</tr>
<tr>
<td class="name">
Distance:
</td>
<td class="value">
0.2 mi (about 24 secs)
</td>
</tr>
</tbody>
</table>
<div class="reverse">
<a onclick="return loadUrl(this.href)" href="/maps?f=d&hl=en&sll=37.79449,-122.395015&sspn=0.048969,0.081711&saddr=10+market+st,+san+francisco&daddr=50+california+st,+san+francisco">
Reverse directions
</a>
</div>
<div class="printspacer noscreen">
 
</div>
<table class="steps">
<tbody>
<tr onclick="showPolylineBlowup('d', 0)">
<td class="num noprint">
<a href="javascript:void(0)">
1
</a>
.
</td>
<td class="num noscreen">
1.
</td>
<td id="panel_0" class="desc">
Head
<b>
east
</b>
from
<b>
California St
</b>
- go 
<b>
177 ft
</b>
</td>
</tr>
<tr onclick="showPolylineBlowup('d', 2)">
<td class="num noprint">
<a href="javascript:void(0)">
2
</a>
.
</td>
<td class="num noscreen">
2.
</td>
<td id="panel_2" class="desc">
Turn
<b>
right
</b>
at
<b>
Drumm St
</b>
- go 
<b>
149 ft
</b>
</td>
</tr>
<tr onclick="showPolylineBlowup('d', 4)">
<td class="num noprint">
<a href="javascript:void(0)">
3
</a>
.
</td>
<td class="num noscreen">
3.
</td>
<td id="panel_4" class="desc">
Turn
<b>
left
</b>
at
<b>
Market St
</b>
- go 
<b>
0.1 mi
</b>
</td>
</tr>
</tbody>
</table>

</pre>

====Google Maps route to GPX convertor====
[http://www.gnuite.com/nokia770/maemo-mapper Maemo-mapper] runs on the Nokia 770. It supports use with a bluetooth GPS receiver. It reformats Google Maps directions into a GPX file, and will display that route and announce turns as you approach them.

===MSN maps===

<pre>
Start: 1600 Pennsylvania Ave NW, Washington, DC 20006
End: 15th St NW & Constitution Ave NW, Washington, DC 20004
Total Distance: 0.6 Miles
Estimated Total Time: 4 minutes
Directions Miles
Start: Depart 1600 Pennsylvania Ave NW, Washington, DC 20006 on Local road(s) (East) < 0.1
1: Turn RIGHT (South) onto E Executive Ave NW 0.2
2: Turn LEFT (East) onto Alexander Hamilton Pl NW, then immediately turn RIGHT (South) onto 15th St NW 0.4

Map Image
End: Arrive 15th St NW & Constitution Ave NW, Washington, DC 20004
</pre>

====Source====

<pre>
<table class="NoBorder" border="0" width="100%">
<tr>
<td class="RTText">
<span class="RouteTableStartText">
Start:
</span>
Depart 1600 Pennsylvania Ave NW, Washington, DC 20006 on Local road(s) (East)
</td>
<td class="RTText" align="Right" width="40">
< 0.1
</td>
</tr>
<tr>
<td class="RTText">
<b>
1:
</b>
Turn RIGHT (South) onto E Executive Ave NW
</td>
<td class="RTText" align="Right" width="40">
0.2
</td>
</tr>
<tr>
<td class="RTText">
<b>
2:
</b>
Turn LEFT (East) onto Alexander Hamilton Pl NW, then immediately turn RIGHT (South) onto 15th St NW
</td>
<td class="RTText" align="Right" width="40">
0.4
</td>
</tr>
</table>
</td>
<td class="RTRow" align="Right" valign="Top" height="10">
 
</td>
</tr>
<tr>
<td class="RTRow">
 
<img style="border-color:#C7BCA2;" alt="Map Image" src="/I/spacer.gif" width="0" height="0" border="0" name="MapImg1">
</td>
</tr>
<tr>
<td class="RTRowDark" valign="Top" colspan="2" rowspan="2">
<table class="NoBorder" border="0" width="100%">
<tr>
<td class="RTText">
<span class="RouteTableEndText">
End:
</span>
Arrive 15th St NW & Constitution Ave NW, Washington, DC 20004
</td>
<td class="RTText" width="40">
 
</td>
</tr>
</table>
</pre>

=== Yahoo Maps ===

<pre>
Starting from: A 50 California St, San Francisco, CA, 94111-4624 Save Address
Arriving At: B 10 Market St, San Francisco, CA, 94111-4801 Save Address
Distance: 0.2 miles Approximate time: 1 min Get Reverse Directions

Map Image

Directions Show turn by turn maps
1. Start at 50 CALIFORNIA ST, SAN FRANCISCO - go < 0.1 mi
2. Turn R on DRUMM ST - go < 0.1 mi
3. Turn L on MARKET ST - go 0.1 mi
4. Arrive at 10 MARKET ST, SAN FRANCISCO, on the L
</pre>

==== Source ====

<pre>
<table border=0 cellspacing=0 cellpadding=2 id="ymaprt">
<tr>
<th align=right valign=top width="1%" nowrap class="ymaprtpts"><small><b>Starting from:</b></small></th>
<td colspan=4><img src="http://us.i1.yimg.com/us.yimg.com/i/us/mp/gr/mp16_a.gif" height=16 width=16 alt="1 "> 50 California St, San Francisco, CA 94111-4624
<small><a href="http://us.rd.yahoo.com/maps/ddresult/save_from;_ylt=AoqfcLOH0rfreiqhx67WzrQa3kcC/*-http://login.yahoo.com/config/set_yp?.src=mp&.page=p1&.cmd=n&.yn=&.st=50 California St&.zip=San Francisco, CA 94111-4624&.country=US&.done=http://maps.yahoo.com/dd_result?newaddr%3D50%2BCalifornia%2BSt%26taddr%3D10%2BMarket%2BSt%26csz%3DSan%2BFrancisco%252C%2BCA%2B94111%26country%3Dus%26tcsz%3DSan%2BFrancisco%252C%2BCA%2B94111%26tcountry%3Dus">Save Address</a></small></tr>
<tr>
<th align=right valign=top class="ymaprtpts"><small><b>Arriving at:</b></small></th>
<td colspan=4><img src="http://us.i1.yimg.com/us.yimg.com/i/us/mp/gr/mp16_b.gif" height=16 width=16 alt="2 "> 10 Market St, San Francisco, CA 94111-4801
<small><a href="http://us.rd.yahoo.com/maps/ddresult/save_to;_ylt=AiWgw9KytDi4XuzF4YWGFz0a3kcC/*-http://login.yahoo.com/config/set_yp?.src=mp&.page=p1&.cmd=n&.yn=&.st=10 Market St&.zip=San Francisco, CA 94111-4801&.country=US&.done=http://maps.yahoo.com/dd_result?newaddr%3D50%2BCalifornia%2BSt%26taddr%3D10%2BMarket%2BSt%26csz%3DSan%2BFrancisco%252C%2BCA%2B94111%26country%3Dus%26tcsz%3DSan%2BFrancisco%252C%2BCA%2B94111%26tcountry%3Dus">Save Address</a></small></tr>

<tr>
<th align=right class="ymaprtpts"><small><b>Distance:</b></small></th>
<td width="1%" nowrap>0.2 miles</td>
<th align=right width="1%" nowrap class="ymaprtpts"><small><b>Approximate Travel Time:</b></small></th>
<td>
1 min
</td>
<td align=right valign=bottom width="1%" nowrap>
<a href="http://us.rd.yahoo.com/maps/ddresult/reverseDD;_ylt=ArvjuCZ_I5Gc4JyrHRFQIaEa3kcC/*-http://maps.yahoo.com/dd_result?ed=_YaYzuV.winqVL64AzOmYypNBUy1fFVhwugBQs_Pogbl1WImEFx_H1JxBITyDts-&name=&csz=San+Francisco%2C+CA+94111-4801&country=US&desc=&tname=&tcsz=San+Francisco%2C+CA+94111-4624&tcountry=US&tdesc=&ds=g&tbt=0&trf=0&textonly=0&oerr=&terr=">
<small class="ygver">Get Reverse Directions</small>
</a>
</td>

</tr>
</table>

Links for sending the directions
MAP IMAGE

<div id="ymapdir">

<table width="100%" border=0 cellspacing=0 cellpadding=0 align=center><tr><th align=left><b class="ygver">Directions</b></th><th align=right><small><b>
<a href="http://us.rd.yahoo.com/maps/ddresult/tbt_on;_ylt=AtcdCayUHXlA8L0yvev28Jwa3kcC/*-http://maps.yahoo.com/dd_result?newaddr=50+California+St&taddr=10+Market+St&csz=San+Francisco%2C+CA+94111&country=us&tcsz=San+Francisco%2C+CA+94111&tcountry=us&tbt=1">Show Turn by Turn Maps</a></b></small></th></tr>
</table>
<table width="100%" border=0 cellspacing=0 cellpadding=0 align=center>
<tr><td>1.</td><td>Start at <b>50</b> <b>CALIFORNIA</b> <b>ST,</b> <b>SAN</b> <b>FRANCISCO</b> - go <b>< 0.1</b> mi</td></tr><tr><td>2.</td><td>Turn <img src="http://us.i1.yimg.com/us.yimg.com/i/us/mp/gr/mp22_r.gif" alt=Right align=absmiddle> on <b>DRUMM</b> <b>ST</b> - go <b>< 0.1</b> mi</td></tr><tr><td>3.</td><td>Turn <img src="http://us.i1.yimg.com/us.yimg.com/i/us/mp/gr/mp22_l.gif" alt=Left align=absmiddle> on <b>MARKET</b> <b>ST</b> - go <b>0.1</b> mi</td></tr><tr><td>4.</td><td>Arrive at <b>10</b> <b>MARKET</b> <b>ST,</b> <b>SAN</b> <b>FRANCISCO,</b> on the <img src="http://us.i1.yimg.com/us.yimg.com/i/us/mp/gr/mp22_l.gif" alt=Left align=absmiddle> </td></tr></table>

</div>
</pre>

===Yahoo Maps (Beta)===

<pre>
V GET MAP AND DIRECTIONS Clear

A 50 California St San Francisco, CA 94111 [x]
[] Make this my default Yahoo! location
1. Start at 50 CALIFORNIA ST, SAN FRANCISCO - go 0.0 mi
2. Turn Right on DRUMM ST - go 0.0 mi
3. Turn Left on MARKET ST - go 0.1 mi
4. Arrive at 10 MARKET ST, SAN FRANCISCO, on the Left

B 10 Market St San Francisco, CA 94111 [x]
C Address, City State [x]

Distance 0.2 mi Time: 1 mins (approx)
Reverse Directions | Roundtrip GO
</pre>

====Source====

Its all based on flash, and thus is not applicable.

===Multimap===

Multimap provides explicit start and finish times for the overall route, as well as individual timings for each step. There is also notification of specific toll roads or areas, such as the London congestion charge. [http://www.multimap.com/map/aproute.cgi?client=public&startx=531160&starty=181635&endx=531422&endy=181181&startrd=&starttown=&startpc=EC1N%202NS&startcountry=GB&endrd=Fleet%20Street&endtown=LONDON&endpc=EC4&endcountry=GB&rn=GB&qs=q&starttime=20:17&input_rt=aproute_pan&lang= Routing results page]

<pre>
Estimated duration:
0 hours, 1 minutes
Departure time:
20:17
Estimated arrival time:
20:18
Total distance:
0.6 miles (0.9 km)
Number of steps:
4

1 Depart on A40 High Holburn for 0.2 miles Map 0 miles (0 km) 20:17
2 At the roundabout, take the fifth exit onto A4 New Fetter Lane for 0.3 miles Map 0.2 miles (0.3 km) 20:17
3 Turn left onto Fleet Street for 0.1 miles Map 0.5 miles (0.8 km) 20:18
4 Arrive at your destination for 0 miles Map 0.6 miles (0.9 km) 20:18
</pre>

====Source====

<pre>
<dl>
<dt>Estimated duration:</dt>
<dd>0 hours, 1 minutes</dd>

<dt>Departure time:</dt>
<dd>20:17</dd>

<dt>Estimated arrival time:</dt>
<dd>20:18</dd>

<dt>Total distance:</dt>
<dd>
0.6 miles (0.9 km)
</dd>

<dt>Number of steps:</dt>
<dd>4</dd>
</dl>

<table>
<tr>
<th colspan="4">Instruction</th>
<th>Distance so far</th>
<th>Time</th>
</tr>

<tr><td colspan="7"><p style="text-align: center; font-weight: bold">You are entering the <a href="http://ad.uk.doubleclick.net/clk;9602607;9705200;e?http://www.cclondon.com">congestion charging zone</a>.<br />Applies Monday to Friday - 7am to 6.30pm.</p></td></tr>
<tr style="background-color: #ffecec">

<td>1</td>
<td>Depart on <strong>A40 High Holburn</strong></td>
<td>for <strong>0.2 miles</strong></td>
<td><a href="/map/aproute.cgi?qs=q&starttime=20:17&client=public&itineraryxylist=531160,181635;531422,181181&rn=GB&mapimg=step&stepbystep=1&lang=&startcountry=GB&endcountry=GB&startrd=&starttown=&startpc=EC1N 2NS&endrd=Fleet Street&endtown=LONDON&endpc=EC4&input_rt=aproute_pan" title="View map of this step">Map</a></td>
<td>0 miles (0 km)</td>
<td>20:17</td>
</tr>

<tr style="background-color: #fcc">
<td><a href="http://ad.uk.doubleclick.net/clk;9602607;9705200;e?http://www.cclondon.com" target="_blank"><img src="/images/ps/cc_logo.gif" border="0" alt="" /></a> 2</td>
<td>At the roundabout, take the fifth exit onto <strong>A4 New Fetter Lane</strong></td>
<td>for <strong>0.3 miles</strong></td>
<td><a href="/map/aproute.cgi?qs=q&starttime=20:17&client=public&itineraryxylist=531160,181635;531422,181181&rn=GB&mapimg=step&stepbystep=2&lang=&startcountry=GB&endcountry=GB&startrd=&starttown=&startpc=EC1N 2NS&endrd=Fleet Street&endtown=LONDON&endpc=EC4&input_rt=aproute_pan" title="View map of this step">Map</a></td>
<td>0.2 miles (0.3 km)</td>
<td>20:17</td>
</tr>

<tr style="background-color: #fcc">
<td><a href="http://ad.uk.doubleclick.net/clk;9602607;9705200;e?http://www.cclondon.com" target="_blank"><img src="/images/ps/cc_logo.gif" border="0" alt="" /></a> 3</td>
<td>Turn left onto <strong> Fleet Street</strong></td>
<td>for <strong>0.1 miles</strong></td>
<td><a href="/map/aproute.cgi?qs=q&starttime=20:17&client=public&itineraryxylist=531160,181635;531422,181181&rn=GB&mapimg=step&stepbystep=3&lang=&startcountry=GB&endcountry=GB&startrd=&starttown=&startpc=EC1N 2NS&endrd=Fleet Street&endtown=LONDON&endpc=EC4&input_rt=aproute_pan" title="View map of this step">Map</a></td>
<td>0.5 miles (0.8 km)</td>
<td>20:18</td>
</tr>

<tr style="background-color: #fcc">
<td><a href="http://ad.uk.doubleclick.net/clk;9602607;9705200;e?http://www.cclondon.com" target="_blank"><img src="/images/ps/cc_logo.gif" border="0" alt="" /></a> 4</td>
<td>Arrive at your destination <strong> </strong></td>
<td>for <strong>0 miles</strong></td>
<td><a href="/map/aproute.cgi?qs=q&starttime=20:17&client=public&itineraryxylist=531160,181635;531422,181181&rn=GB&mapimg=step&stepbystep=4&lang=&startcountry=GB&endcountry=GB&startrd=&starttown=&startpc=EC1N 2NS&endrd=Fleet Street&endtown=LONDON&endpc=EC4&input_rt=aproute_pan" title="View map of this step">Map</a></td>
<td>0.6 miles (0.9 km)</td>
<td>20:18</td>
</tr>
</table>
</pre>

===MapQuest===

<pre>
50 California St
San Francisco, CA 94111-4624, US Revise | New Directions

10 Market St
San Francisco, CA 94111-4801, US Revise | New Directions
Total Est. Time: 1 minute
Total Est. Distance: 0.18 miles
</pre>

<pre>
1: Start out going EAST on CALIFORNIA ST toward DRUMM ST. <0.1 miles Map
2: Turn RIGHT onto DRUMM ST. <0.1 miles Map
3: Turn SHARP LEFT onto MARKET ST. 0.1 miles Map
4: End at 10 Market St
San Francisco, CA 94111-4801, US Map
</pre>
Note: mapquest adds icons indiciating parts of a journey such as "Start" "left turn" "right turn" "end"

====Source====
<pre>
<div id="dirsummary" class="clear">
<div class="startend">
<div class="content clear">
<div id="mqaddress-start" class="addresssummary">
<div class="clear">
<img border="0" src="http://cdn.mapquest.com/mqsite/icon-dirs-start" width="32" height="17" alt="Start"/>
<p><span><b>50 California St</b><br />San Francisco, CA 94111-4624, US
</span><span class="screen"><a href="/directions/main.adp?do=nw&mo=ma&2si=navt&1gi=0&un=m&go=1&2gi=0&1a=50%20California%20St&1c=San%20Francisco&1g=F1vA%2bNzyt4iAl71AiHbU5Q%3d%3d&2a=10%20Market%20St&1l=rBXkKYPKi%2fM%3d&2c=San%20Francisco&1da=%2d1%2e000000&1rc=L1AAA&cl=EN&1n=SAN%20FRANCISCO%20COUNTY&2g=JF%2b%2bgQaqpCu8wB4zmqR0%2fw%3d%3d&qq=1ADqpk24ofCeTxpK%252f79e%252bAyK24xaIMHf9X7JhECKvl9XAwoRYTHRtvNigziQm6uUEJQ0Coge%252fbzANwMyr2Kx4bZM16XzMowN3yTnj0KzTJX6DCnZ3c11pDhSyQOR8KfFjA8LEPiDh414NP9IaMYlgrzYY1zx0jwDqifr862AG3q4kaKoc7v5cVDy4fxS94F1&1s=CA&2l=mK%2fUgh11ReQ%3d&ct=NA&1v=ADDRESS&2n=SAN%20FRANCISCO%20COUNTY&r=f&1y=US&1z=94111%2d4624&1si=navt&2s=CA&2da=%2d1%2e000000&2rc=L1AAA&2v=ADDRESS&did=1143928014&2y=US&2z=94111%2d4801&rsres=1&1sb=revise">Revise</a> | <a href="/directions/main.adp?do=nw">New Directions</a></span>
</p>
</div>
</div>
<div id="mqaddress-end" class="addresssummary end">
<div class="clear">
<img border="0" src="http://cdn.mapquest.com/mqsite/icon-dirs-end" width="32" height="17" alt="End"/>
<p><span><b>10 Market St</b><br />San Francisco, CA 94111-4801, US
</span><span class="screen"><a href="/directions/main.adp?do=nw&mo=ma&2si=navt&1gi=0&un=m&go=1&2gi=0&1a=50%20California%20St&1c=San%20Francisco&1g=F1vA%2bNzyt4iAl71AiHbU5Q%3d%3d&2a=10%20Market%20St&1l=rBXkKYPKi%2fM%3d&2c=San%20Francisco&1da=%2d1%2e000000&1rc=L1AAA&cl=EN&1n=SAN%20FRANCISCO%20COUNTY&2g=JF%2b%2bgQaqpCu8wB4zmqR0%2fw%3d%3d&qq=1ADqpk24ofCeTxpK%252f79e%252bAyK24xaIMHf9X7JhECKvl9XAwoRYTHRtvNigziQm6uUEJQ0Coge%252fbzANwMyr2Kx4bZM16XzMowN3yTnj0KzTJX6DCnZ3c11pDhSyQOR8KfFjA8LEPiDh414NP9IaMYlgrzYY1zx0jwDqifr862AG3q4kaKoc7v5cVDy4fxS94F1&1s=CA&2l=mK%2fUgh11ReQ%3d&ct=NA&1v=ADDRESS&2n=SAN%20FRANCISCO%20COUNTY&r=f&1y=US&1z=94111%2d4624&1si=navt&2s=CA&2da=%2d1%2e000000&2rc=L1AAA&2v=ADDRESS&did=1143928014&2y=US&2z=94111%2d4801&rsres=1&2sb=revise">Revise</a> | <a href="/directions/main.adp?do=nw">New Directions</a></span>
</p>
</div>
</div>
</div>
<div class="timedist clear">
<div class="time">
<p><b>Total Est. Time:</b> <span> 1 minute</span></p>
</div>
<div class="dist">
<p><b>Total Est. Distance:</b> <span>0.18 miles</span></p>
</div>
</div>
</div>
</pre>

<pre>
<table border="0" cellpadding="0" cellspacing="0" id="maneuvers">

<thead class="bga">
<tr>
<th colspan=3><b>Maneuvers</b></th>
<th class="textr">Distance</th>
<th class="textc"> Maps  </th>
</tr>
</thead>
<tbody>

<tr >

<td class="rs"><img border="0" src="http://cdn.mapquest.com/mqsite/icon-dirs-start" width="32" height="17"/></td>

<td class="num">1:</td>
<td>Start out going EAST on CALIFORNIA ST toward DRUMM ST.</td>
<td class="nowrap"><0.1 miles</td>

<td class="textc"><a name=ManAnchor0 href="javascript:showManMap('0','http://mq-mapgend.websys.aol.com:80/mqmapgend?MQMapGenRequest=FDR2dmwjDE%3byt2q%26FDT7w%7clztwly%24%2e90axhyz%3a%26%40%24%3a%26%40t5g6%245h6%24lu4%24HJQD%11T%26FDBBD%7clztwl4%24%2e90axhy1%3a%26%40%24%3a%26%40%24w9f2%3a%2aE%14QXO%2ax0z1xg%40%5fn10bwga%24%3a%26%40%24%3a%26%40z21%40%3aHO%1593bdWik1mf%3bNSC%12JDBJ%40ba0fbs%26%3d2l1a10h%402%3ag');">Map</a></td>
</tr>

<tr >
<td class="manmap" colspan=5 id="mmaprow0"><img id=mmIMG0 name=mmIMG0 style=display:none src=http://cdn.mapquest.com/mq/space_white height=0 width=0></img></td>
</tr>

<tr class="bgc">

<td class="rs"><img border="0" src="http://cdn.mapquest.com/mqsite/rs_right" width="32" height="32"/></td>

<td class="num">2:</td>
<td>Turn RIGHT onto DRUMM ST.</td>
<td class="nowrap"><0.1 miles</td>

<td class="textc"><a name=ManAnchor1 href="javascript:showManMap('1','http://mq-mapgend.websys.aol.com:80/mqmapgend?MQMapGenRequest=FDR2dmwjDE%3Byt2q%26FDT7w%7Clztwlw%24.90axhyb%3A%26%40%24%3A%26%40t5g6%245h6%24lu4%24HJQD%11T%26FDBBD%7Clztwly%24.90axhyb%3A%26%40%24%3A%26%40%240u0%24%3DTPWIK%2Cba0fbl%26%3D2l1a10l%40%24%3A%26%40%24%3A%26y7x%26%26FDEmvqjHqjwjg%7C%14D%13%13%17OHM%26atahaz%3A%29uallfzx%26%3Dr%3Au');">Map</a></td>
</tr>

<tr class="bgc">
<td class="manmap" colspan=5 id="mmaprow1"><img id=mmIMG1 name=mmIMG1 style=display:none src=http://cdn.mapquest.com/mq/space_white height=0 width=0></img></td>
</tr>

<tr >

<td class="rs"><img border="0" src="http://cdn.mapquest.com/mqsite/rs_sharp_left " width="32" height="32"/></td>

<td class="num">3:</td>
<td>Turn SHARP LEFT onto MARKET ST.</td>
<td class="nowrap">0.1 miles</td>

<td class="textc"><a name=ManAnchor2 href="javascript:showManMap('2','http://mq-mapgend.websys.aol.com:80/mqmapgend?MQMapGenRequest=FDR2dmwjDE%3byt2q%26FDT7w%7clztwlr%24%2e90axh4z%3a%26%40%24%3a%26%40t5g6%245h6%24lu4%24HJQD%11T%26FDBBD%7clztwl0%24%2e90axhyb%3a%26%40%24%3a%26%40%240ua%24%3dTPGp2hsQxolve%2cCMN%17MJAD%24x0z1x1%40%5fn10bwga%24s%26y%24a%26f%3aHOHQJ%3batahwr%3a%29uallfrg%26%40%24%3a%26%40%24%3ahu1l%26');">Map</a></td>
</tr>

<tr >
<td class="manmap" colspan=5 id="mmaprow2"><img id=mmIMG2 name=mmIMG2 style=display:none src=http://cdn.mapquest.com/mq/space_white height=0 width=0></img></td>
</tr>

<tr class="bgc">

<td class="rs"><img border="0" src="http://cdn.mapquest.com/mqsite/icon-dirs-end" width="32" height="17"/></td>

<td class="num">4:</td>
<td colspan="2">End at
<b>10 Market St</b><br />San Francisco, CA 94111-4801, US

</td>

<td class="textc"><a name=ManAnchor3 href="javascript:showManMap('3','http://mq-mapgend.websys.aol.com:80/mqmapgend?MQMapGenRequest=FDR2dmwjDE%3byt2q%26FDT7w%7clztwqw%24%2e90axhwy%3a%26%40%24%3a%26%40t5g6%245h6%24lu4%24HJQD%11T%26FDBBD%7clztwl0%24%2e90axhyb%3a%26%40%24%3a%26%40%240ua%24%3dTPGp2hsQxolve%2cCMN%17MJAD%24x0z1x1%40%5fn10bwga%24s%26y%24a%26f%3aHOHQJ%3batahwr%3a%29uallfrg%26%40%24%3a%26%40%24%3ahu1l%26');">Map</a></td>
</tr>
<tr class="bgc">
<td class="manmap" colspan=5 id="mmaprow3"><img id=mmIMG3 name=mmIMG3 style={display:none} src=http://cdn.mapquest.com/mq/space_white height=0 width=0></img></td>
</tr>

<tr >
<td colspan="5" class="totals"><b>Total Est. Time:</b> 1 minute     <b>Total Est. Distance:</b> 0.18 miles </td>
</tr>

</tbody>
</table>
</pre>

===Bus Trip Planners===

Trip planners exhibit many similar characteristics to Directions services. Here are some examples.

====transit.511.org====

<pre>
Trip Itinerary for Monday, leaving at 2:00pm.

Muni buses and F-line: Always ask for a transfer, even if you are not going to transfer to another line.

Depart: California St/park Presidio in San Francisco

Then:
Go to: S.W. Corner Of Geary Blvd & Park Presidio Blvd (Location map)

Board: SF Muni Bus #38l/Geary Ltd at 2:05 pm (next bus at 2:12 pm) (schedule detail)

Important! Important Announcements About This Route What is Important Announcement?

Fare: Pay $1.50

Get Off: Transbay Hump & La Playa St at 2:34 pm

Go to: 10 Market St. in San Francisco (Location map)

Total Travel Time: 40 min

Total Cash Fare: $1.50
</pre>

====source====

<pre>

<strong>Trip Itinerary for Monday, leaving at 2:00pm.</strong><br>

<br>

<table width="100%" border="0" cellpadding="4" cellspacing="0" bgcolor="#FFE3FF">

<tr valign="top">
<td width="100%">
<a href="http://www.sfmuni.com/pop" title="Muni buses and F-line: <b>Always ask for a transfer,</b> even if you are not going to transfer to another line.">Muni buses and F-line: <b>Always ask for a transfer,</b> even if you are not going to transfer to another line.</a>
</td>
</tr>

</table>
<br>

<table width="100%" border="0" cellpadding="4" cellspacing="0" bgcolor="#DCF3FF">
<tr valign="top">
<th><font color="#006699">Depart:</font></th>
<td width="100%">
California St/park Presidio in San Francisco
</td>

</tr>
</table>

<br><table width="100%" border="0" cellpadding="4" cellspacing="0" bgcolor="#DCF3FF">
<tr valign="top">
<th><font color="#006699">Then:</font></th>
<td><table width="100%" border="0" cellspacing="0" cellpadding="1">
<tr valign="top">
<th>Go to:</th>

<td>S.W. Corner Of Geary Blvd & Park Presidio Blvd (<a href="walkingmap.asp?al=California+St%2Fpark+Presidio+%28starting+location%29&ax=-15800&ay=-257&bl=Geary+Blvd+%26+Park+Presidio+Blvd&bx=-15799&by=-322" title="Location Map">Location map</a>)<br><br></td>
</tr>

<tr valign="top">
<th>Board:</th>
<td>
<a href="/providers/providerinfo.asp?cid=SF" title="Provider Info">SF Muni</a> Bus #38l/Geary Ltd at 2:05 pm (next bus at 2:12 pm)
(<a href="scheddetail.asp?scln=Sf+Muni+Bus+%2338l%2FGeary+Ltd&scrn=38L&scal=Geary+Blvd+%26+Park+Presidio+Blvd&scac=SW&scax=%2D15799&scay=%2D322&scar=1268&scas=17&scat=845&scbl=Transbay+Hump+%26+La+Playa+St&scbx=%2D14801&scby=%2D163&scbr=1268&scbs=34&scdy=2&sctm=L&fs=CALIFORNIA+ST%2FPARK+PRESIDIO&fc=SAN+FRANCISCO&fz=&ts=10+Market+St%2E&tc=San+Francisco&tz=&prfa=%2D15800%2C%2D257%2CCALIFORNIA+ST%2FPARK+PRESIDIO%2CSAN+FRANCISCO%2C&prta=%2D14781%2C%2D92%2C10+Market+St%2E%2CSan+Francisco%2C&td=2&tm=L&t1=2:00PM&t2=2:00PM&am1=PM&op=F&of=R&ow=120&sn=&rs=_&fx=-15800&fy=-257&fxy=%2D15800%2C%2D257%2CCALIFORNIA+ST%2FPARK+PRESIDIO%2C+SAN+FRANCISCO&tx=-14781&ty=-92" title="Schedule Detail">schedule detail</a>)

<br><br>

<img src="/images/warning.gif" alt="Important!" width="16" height="15">
<a href="/announcements/results.asp?rte=5616" title="Important Announcements About This Route">Important Announcements</a> About This Route
<a href="/utils/help.asp#annimpwhatis" title="What is Important Announcement?"><img src="/images/help.gif" alt="What is Important Announcement?" width="12" height="12" border="0"></a>
<br><br>

</td>
</tr>
<tr valign="top">
<th>Fare:</th>

<td>Pay $1.50<br><br></td>
</tr>
<tr valign="top">
<th>Get Off:</th>
<td>Transbay Hump & La Playa St at 2:34 pm</td>
</tr>
</table>

</pre>

====rtd-denver.com====

<pre>
From: W ALAMEDA AVE & S BROADWAY DENVER
To: E COLFAX AVE & PEARL ST DENVER
Arriving At: 500P
Best Itinerary
Go to Bus Stop At: S Lincoln St & Alameda Ave, DENVER
Get On Bus: #0 / 0 BROADWAY STN 0 DOWNTOWN at 4:37PM (Next Bus At 4:47PM)
Get Off the Bus At: Colfax Ave & Broadway, DENVER at 4:49PM

Go to Bus Stop At: Colfax Ave & Broadway, DENVER
Get On Bus: #15 / 15 CHAMBERS 15 via E COLFAX at 4:59PM (Next Bus At 5:07PM)
Get Off the Bus At: Colfax Ave & Sherman St, DENVER at 5:00PM

Travel Time : 23 minutes

Alternate Itinerary
Go to Bus Stop At: S Lincoln St & Alameda Ave, DENVER
Get On Bus: #0 / 0 DOWNTOWN 0 VIA BROADWAY at 4:32PM (Next Bus At 4:37PM)
Get Off the Bus At: Colfax Ave & Broadway, DENVER at 4:44PM

Go to Bus Stop At: Colfax Ave & Broadway, DENVER
Get On Bus: #15L / 15L AURORA MALL 15L E COLFAX at 4:51PM (Next Bus At 4:59PM)
Get Off the Bus At: Colfax Ave & Sherman St, DENVER at 4:53PM

Travel Time : 21 minutes

Alternate Itinerary
Go to Bus Stop At: S Lincoln St & Alameda Ave, DENVER
Get On Bus: #0 / 0 DOWNTOWN 0 VIA BROADWAY at 4:32PM (Next Bus At 4:37PM)
Get Off the Bus At: Colfax Ave & Broadway, DENVER at 4:44PM

Go to Bus Stop At: Colfax Ave & Broadway, DENVER
Get On Bus: #15 / 15 KRAMARIA 15 via E COLFAX at 4:52PM (Next Bus At 4:59PM)
Get Off the Bus At: Colfax Ave & Pearl St, DENVER at 4:55PM

Travel Time : 23 minutes

The Trip Planner is to be used as a guide to help plan bus itineraries.
You should always check bus schedules to verify route pickup times
and drop off times as well as any detours.
</pre>

====source====
(presentational markup removed for clarity; note unescaped ampersands and abuse of "br" tags)

<pre>
<table>
<tr>
<td>
From: W ALAMEDA AVE & S BROADWAY DENVER
<br>
To: E COLFAX AVE & PEARL ST DENVER
<br>
Arriving At: 500P
</td>
</tr>
<br>
<tr>
<td>
Best Itinerary
</td>
</tr>
<tr>
<td>
Go to Bus Stop At: S Lincoln St & Alameda Ave, DENVER
<br>
Get On Bus: #0 / 0 BROADWAY STN 0 DOWNTOWN at 4:37PM (Next Bus At 4:47PM)
<br>
Get Off the Bus At: Colfax Ave & Broadway, DENVER at 4:49PM
<br>
<br>
Go to Bus Stop At: Colfax Ave & Broadway, DENVER
<br>
Get On Bus: #15 / 15 CHAMBERS 15 via E COLFAX at 4:59PM (Next Bus At 5:07PM)
<br>
Get Off the Bus At: Colfax Ave & Sherman St, DENVER at 5:00PM
<br>
<br>
Travel Time : 23 minutes
<br>
<br>

</td>
</tr>
<tr>
<td>
Alternate Itinerary
</td>
</tr>
<tr>
<td>
Go to Bus Stop At: S Lincoln St & Alameda Ave, DENVER
<br>
Get On Bus: #0 / 0 DOWNTOWN 0 VIA BROADWAY at 4:32PM (Next Bus At 4:37PM)
<br>
Get Off the Bus At: Colfax Ave & Broadway, DENVER at 4:44PM
<br>
<br>
Go to Bus Stop At: Colfax Ave & Broadway, DENVER
<br>
Get On Bus: #15L / 15L AURORA MALL 15L E COLFAX at 4:51PM (Next Bus At 4:59PM)
<br>
Get Off the Bus At: Colfax Ave & Sherman St, DENVER at 4:53PM
<br>
<br>
Travel Time : 21 minutes
<br>
<br>

</td>
</tr>
<tr>
<td>
Alternate Itinerary
</td>
</tr>
<tr>
<td>
Go to Bus Stop At: S Lincoln St & Alameda Ave, DENVER
<br>
Get On Bus: #0 / 0 DOWNTOWN 0 VIA BROADWAY at 4:32PM (Next Bus At 4:37PM)
<br>
Get Off the Bus At: Colfax Ave & Broadway, DENVER at 4:44PM
<br>
<br>
Go to Bus Stop At: Colfax Ave & Broadway, DENVER
<br>
Get On Bus: #15 / 15 KRAMARIA 15 via E COLFAX at 4:52PM (Next Bus At 4:59PM)
<br>
Get Off the Bus At: Colfax Ave & Pearl St, DENVER at 4:55PM
<br>
<br>
Travel Time : 23 minutes
<br>
<br>

</td>
</tr>
<tr>
<td>
The Trip Planner is to be used as a guide to help plan bus itineraries.
<br>
You should always check bus schedules to verify route pickup times
<br>
and drop off times as well as any detours.
</td>
</tr>
</table>
</pre>

===GPX Planners===
[http://www.gnuite.com/nokia770/maemo-mapper Maemo-mapper] runs on the Nokia 770. It supports use with a bluetooth GPS receiver. It reformats Google Maps directions into a GPX file, and will display that route and announce turns as you approach them.

=== hand authored bike routes ===
May at [http://www.tikirobot.net/wp/category/cycling/ TikiRobot!] has been marking up her cycling routes. She uses photographs of landmarks, a map image, and a textual description, or textual directions. There is no implied schema, but would be a good candidate for adding address or geo info.

RussNelson at [http://russnelson.com/bicycling/ his blog] has been documenting his bike rides. A Garmin Foretrex 201 records the route, gpsbabel downloads it to his Linux desktop, maptracks.py uses Terraserver topo tiles to create a map from the track, and create-rides.py creates the structure of a blog entry using tracklength.py to calculate speed and distance. Photos get geolocated from the track, but only on demand. The resultant blog entry has a map which links to a Google Maps mashup displaying the track.

=== hand authored flight record ===
Jeremy Zawodny has [http://jeremy.zawodny.com/blog/archives/006655.html has narrated flights] He uses photographs of landmarks, a map image, and a textual description, with links to landmarks. There is no implied schema, but would be a good candidate for adding address or geo info.

=== Year in Flights ===

The [http://gc.kls2.com/faq.html great circle mapper] seems to inspire people to document
their trips a year at a time:

* [http://www.flickr.com/photos/ishida/323392479/ r12a in 2006: 140,718 km]
* [http://norman.walsh.name/2006/12/31/2006 ndw in 2006: 31,844 miles in 130 flights]

=== Directions to an office ===
====Microsoft in San Francisco====
http://www.microsoft.com/mscorp/info/usaoffices/northernca/sanfrancisco.mspx
<pre>
From the North Bay
Take US-101S over the Golden Gate Bridge to San Francisco. Exit right toward Lombard
Street/Downtown. Follow the street as it curves, and turn left onto Lombard Street.
Turn right onto Van Ness Avenue. Turn left onto Broadway. Turn right onto Battery Street.
Turn left onto Market Street. Go straight for five short blocks. The Landmark at One Market
is on the right.

From the East Bay
Take I-80W over the Bay Bridge. Pay toll ($5). Exit right at Fremont Street. Turn left
onto Fremont Street. Turn right onto Howard Street. Turn left onto Main Street. Turn
right onto Market Street. Go straight for two short blocks. The Landmark at One Market
is on the right.

From the South Bay or SFO Airport
Take US-101N San Francisco to Exit I-280N Port of San Francisco. Exit King Street. Turn
Left onto Third Street. Turn Right onto Folsom Street. Turn left onto Main Street. Turn
right onto Market Street. Go straight for two short blocks. The Landmark at One Market
is on the right.
</pre>

===Walking routes===
*[http://www.walkweb.org.uk/g05_information.htm (with GPS wayponts)]
*[http://www.cheshire.gov.uk/countryside/Walking/crewe_nantwich/nantwich_acton/nantwich_acton_directions.htm (without GPS wayponts)]

== related discussion ==

* [http://radar.oreilly.com/archives/2006/03/directions_microformat_leading.html Tim O'Reilly blog post: Directions Microformat -> Google for directions?]

==See also==
*[[events/2006-06-13-where-2-bof]]
*[[directions]]
*[[directions-formats]]
*[[directions-brainstorming]]

events/2007-03-12-sxsw-growth-evolution-of

2007-02-28T22:12:38Z

DanC: /* Would Like to Attend */

<h1>The Growth and Evolution of Microformats at SXSW 2007</h1>

One of several microformats [[events]].

__TOC__

== Summary ==
The Growth and Evolution of Microformats is a [http://2007.sxsw.com/interactive/programming/panels/ confirmed panel presentation] session to be held at the 2007 [http://2007.sxsw.com/ SXSW] Interactive Festival, on Monday, March 12th from 2:00-3:00pm in Austin, Texas.

== Tags ==
Please use ''all'' of the following tags when tagging content (blog posts, photos) published related to the microformats session at SXSW interactive 2007:

tags: '''microformats sxsw sxsw07 sxsw2007 sxswi sxswi07 sxswi2007 microformats-sxsw microformats-sxsw2007 microformats-sxswi microformats-sxswi2007'''

== Panelists ==
*[[User:Tantek|Tantek Çelik]] (moderator)
*[[User:Phae|Frances Berriman]]
*[[User:MikeKaply|Michael Kaply]]
*[http://www.glennjones.net/ Glenn Jones]

== Short Session Description ==
Was required to be 25 words or less:

Microformats.org has ushered in the rapid adoption of key formats for publishing and sharing [[rel-tag|tags]], [[rel-license|licenses]], [[hcard|contacts]], [[xfn|relationships]], [[hcalendar|events]] and [[hreview|reviews]]. What happens next?

== Longer Session Description ==

In its first year, microformats.org ushered in the rapid adoption of key formats for publishing and sharing [[rel-tag|tags]], [[rel-license|licenses]], [[hcard|contacts]], [[xfn|relationships]], [[hcalendar|events]] and [[hreview|reviews]] on the Web. See what new microformats are being developed for [[hresume|resumes]], [[hlisting|classified listings]], [[media-info|music, and media]], as well as how tens of millions of established microformats on web sites of individuals, companies, and organizations are driving innovations in desktop applications and advancing personal data portability.

== Attending ==
Please add your name here if you are attending this session, speaking or not.

*[[User:Tantek|Tantek Çelik]]
*[[User:Phae|Frances Berriman]]
*[[User:Veeliam|William Lawrence]]
*[[User:Adactio|Jeremy Keith]]
*[[User:RyanKing|Ryan King]]

== Would Like to Attend ==
Please add your name here if you might be around Austin and would like to attend.
* [[User:DanC|Dan Connolly]] (not likely)

== Session Comments and Q&A ==
* ...

== Photos ==
* ...

== Blog Posts ==
* ...

events/2007-03-12-sxsw-growth-evolution-of

2007-02-28T22:12:28Z

DanC: wishing

<h1>The Growth and Evolution of Microformats at SXSW 2007</h1>

One of several microformats [[events]].

__TOC__

== Summary ==
The Growth and Evolution of Microformats is a [http://2007.sxsw.com/interactive/programming/panels/ confirmed panel presentation] session to be held at the 2007 [http://2007.sxsw.com/ SXSW] Interactive Festival, on Monday, March 12th from 2:00-3:00pm in Austin, Texas.

== Tags ==
Please use ''all'' of the following tags when tagging content (blog posts, photos) published related to the microformats session at SXSW interactive 2007:

tags: '''microformats sxsw sxsw07 sxsw2007 sxswi sxswi07 sxswi2007 microformats-sxsw microformats-sxsw2007 microformats-sxswi microformats-sxswi2007'''

== Panelists ==
*[[User:Tantek|Tantek Çelik]] (moderator)
*[[User:Phae|Frances Berriman]]
*[[User:MikeKaply|Michael Kaply]]
*[http://www.glennjones.net/ Glenn Jones]

== Short Session Description ==
Was required to be 25 words or less:

Microformats.org has ushered in the rapid adoption of key formats for publishing and sharing [[rel-tag|tags]], [[rel-license|licenses]], [[hcard|contacts]], [[xfn|relationships]], [[hcalendar|events]] and [[hreview|reviews]]. What happens next?

== Longer Session Description ==

In its first year, microformats.org ushered in the rapid adoption of key formats for publishing and sharing [[rel-tag|tags]], [[rel-license|licenses]], [[hcard|contacts]], [[xfn|relationships]], [[hcalendar|events]] and [[hreview|reviews]] on the Web. See what new microformats are being developed for [[hresume|resumes]], [[hlisting|classified listings]], [[media-info|music, and media]], as well as how tens of millions of established microformats on web sites of individuals, companies, and organizations are driving innovations in desktop applications and advancing personal data portability.

== Attending ==
Please add your name here if you are attending this session, speaking or not.

*[[User:Tantek|Tantek Çelik]]
*[[User:Phae|Frances Berriman]]
*[[User:Veeliam|William Lawrence]]
*[[User:Adactio|Jeremy Keith]]
*[[User:RyanKing|Ryan King]]

== Would Like to Attend ==
Please add your name here if you might be around Austin and would like to attend.
* *[[User:DanC|Dan Connolly]] (not likely)

== Session Comments and Q&A ==
* ...

== Photos ==
* ...

== Blog Posts ==
* ...

events/2007-03-12-sxsw-growth-evolution-of

2007-02-28T22:12:16Z

DanC: oops

<h1>The Growth and Evolution of Microformats at SXSW 2007</h1>

One of several microformats [[events]].

__TOC__

== Summary ==
The Growth and Evolution of Microformats is a [http://2007.sxsw.com/interactive/programming/panels/ confirmed panel presentation] session to be held at the 2007 [http://2007.sxsw.com/ SXSW] Interactive Festival, on Monday, March 12th from 2:00-3:00pm in Austin, Texas.

== Tags ==
Please use ''all'' of the following tags when tagging content (blog posts, photos) published related to the microformats session at SXSW interactive 2007:

tags: '''microformats sxsw sxsw07 sxsw2007 sxswi sxswi07 sxswi2007 microformats-sxsw microformats-sxsw2007 microformats-sxswi microformats-sxswi2007'''

== Panelists ==
*[[User:Tantek|Tantek Çelik]] (moderator)
*[[User:Phae|Frances Berriman]]
*[[User:MikeKaply|Michael Kaply]]
*[http://www.glennjones.net/ Glenn Jones]

== Short Session Description ==
Was required to be 25 words or less:

Microformats.org has ushered in the rapid adoption of key formats for publishing and sharing [[rel-tag|tags]], [[rel-license|licenses]], [[hcard|contacts]], [[xfn|relationships]], [[hcalendar|events]] and [[hreview|reviews]]. What happens next?

== Longer Session Description ==

In its first year, microformats.org ushered in the rapid adoption of key formats for publishing and sharing [[rel-tag|tags]], [[rel-license|licenses]], [[hcard|contacts]], [[xfn|relationships]], [[hcalendar|events]] and [[hreview|reviews]] on the Web. See what new microformats are being developed for [[hresume|resumes]], [[hlisting|classified listings]], [[media-info|music, and media]], as well as how tens of millions of established microformats on web sites of individuals, companies, and organizations are driving innovations in desktop applications and advancing personal data portability.

== Attending ==
Please add your name here if you are attending this session, speaking or not.

*[[User:Tantek|Tantek Çelik]]
*[[User:Phae|Frances Berriman]]
*[[User:Veeliam|William Lawrence]]
*[[User:Adactio|Jeremy Keith]]
*[[User:RyanKing|Ryan King]]

== Would Like to Attend ==
Please add your name here if you might be around Austin and would like to attend.
* ...

== Session Comments and Q&A ==
* ...

== Photos ==
* ...

== Blog Posts ==
* ...

events/2007-03-12-sxsw-growth-evolution-of

2007-02-28T22:11:16Z

DanC: wishing

<h1>The Growth and Evolution of Microformats at SXSW 2007</h1>

One of several microformats [[events]].

__TOC__

== Summary ==
The Growth and Evolution of Microformats is a [http://2007.sxsw.com/interactive/programming/panels/ confirmed panel presentation] session to be held at the 2007 [http://2007.sxsw.com/ SXSW] Interactive Festival, on Monday, March 12th from 2:00-3:00pm in Austin, Texas.

== Tags ==
Please use ''all'' of the following tags when tagging content (blog posts, photos) published related to the microformats session at SXSW interactive 2007:

tags: '''microformats sxsw sxsw07 sxsw2007 sxswi sxswi07 sxswi2007 microformats-sxsw microformats-sxsw2007 microformats-sxswi microformats-sxswi2007'''

== Panelists ==
*[[User:Tantek|Tantek Çelik]] (moderator)
*[[User:Phae|Frances Berriman]]
*[[User:MikeKaply|Michael Kaply]]
*[http://www.glennjones.net/ Glenn Jones]

== Short Session Description ==
Was required to be 25 words or less:

Microformats.org has ushered in the rapid adoption of key formats for publishing and sharing [[rel-tag|tags]], [[rel-license|licenses]], [[hcard|contacts]], [[xfn|relationships]], [[hcalendar|events]] and [[hreview|reviews]]. What happens next?

== Longer Session Description ==

In its first year, microformats.org ushered in the rapid adoption of key formats for publishing and sharing [[rel-tag|tags]], [[rel-license|licenses]], [[hcard|contacts]], [[xfn|relationships]], [[hcalendar|events]] and [[hreview|reviews]] on the Web. See what new microformats are being developed for [[hresume|resumes]], [[hlisting|classified listings]], [[media-info|music, and media]], as well as how tens of millions of established microformats on web sites of individuals, companies, and organizations are driving innovations in desktop applications and advancing personal data portability.

== Attending ==
Please add your name here if you are attending this session, speaking or not.

*[[User:Tantek|Tantek Çelik]]
*[[User:Phae|Frances Berriman]]
*[[User:Veeliam|William Lawrence]]
*[[User:Adactio|Jeremy Keith]]
*[[User:RyanKing|Ryan King]]
*[[User:DanC|Dan Connolly]] (not likely)

== Would Like to Attend ==
Please add your name here if you might be around Austin and would like to attend.
* ...

== Session Comments and Q&A ==
* ...

== Photos ==
* ...

== Blog Posts ==
* ...

profile-uris

2007-02-28T20:37:41Z

DanC: un-resolve and clarify the combined profile issue

In [[hcalendar-issues]], it is ACCEPTED that each microformat should have a profile URI, like [[http://gmpg.org/xfn/11 the XFN profile]].

Some issues include:

* what domain to use? Candidates include:
** microformats.org
** www.w3.org
** xmdp.org
* what about versioning? how to keep in sync with the wiki and test materials?
* what profile URI to use for combinations, such as [[hcard]] and [[hcalendar]]?
** note [http://www.w3.org/TR/html401/struct/global.html#adef-profile HTML4.01] states "that one or more meta data profiles, [are] separated by white space." Though it's simpler for authors if they can just use one profile URI.
* More profiles are needed.

One proposal is: use www.w3.org, following [http://www.w3.org/1999/10/nsuri W3C namespace policy]. As to versioning, change the profile whenever the wiki changes (within some reasonable latency, say, a couple weeks or a month). For example: [http://www.w3.org/2006/03/hcard an hCard Profile at w3.org], and discussion: [http://microformats.org/discuss/mail/microformats-dev/2006-March/000068.html an hCard profile that seems to work with GRDDL].

See also:

* [[profile-examples-in-wild|Profile examples, in the wild]]
* [[faqs-for-rdf]] for discussion of connecting microformats to URIs.
* [[hcard-profile]].

irc-people

2007-01-11T16:02:40Z

DanC: not keep office hours any more

A list of [[irc|IRC]] regulars sorted by nick and their normal timezones (winter/summer).

* [[User:Adam Craven|AdamCraven]] (+0000)
* [[User:Amette|amette]] (+1000)
* [[User:Ashley|Ashley]] (+1000)
* [[User:B.K._DeLong|bkdelong]] (-0500/-0400)
* [[User:Ben Ward|BenWard]] (+0000)
* [[User:BenjaminCarlyle|BenjaminCarlyle]] (+1000)
* [[User:HenriBergius|bergie]] (+0200/+0300)
* [[User:BenWest|bewest]] (-0800/-0700)
* [[User:Bob Jonkman|BobJonkman]] (-0500/-0400)
* [[User:Boneill|boneill]] (+0000)
* [[User:Brian|briansuda]] (+0000)
* [[User:Cgriego|cgriego]] (-0600/-0500)
* [[User:CharlesRoper|charles_r]] (0000/+0100)
* [[User:Charlvn|Charl]] (+0200/+0200)
* [[User:ChristopherStJohn|cks]] (-0600/-0500)
* [[User:Cloud|Cloud]] (+0000)
* [[User:Colin_Barrett|cbarrett]] (-1000)
* [[User:ColinDDevroe|cdevroe]] (-0500/-0600)
* [[User:Csarven|csarven]] (-0500/-0400)
* [[User:Dan Kubb|dkubb]] (-0800/-0700)
* [[User:DanC|DanC]] (-0600/-0500)
* [[User:DannyAyers|danja]] (+0100/+0200)
* [[User:Dave Cardwell|davecardwell]] (+0000)
* [[User:DeanEro|deanero]] (-0800/-0700)
* [[User:DimitriGlazkov|dglazkov]] (-0600/-0500)
* [[User:DrewMcLellan|drewinthehead]] (+0000/+0100)
* [[User:Ed Summers|edsu]] (-0500/-0400)
* [[User:Enric|enric]] (-0800/-0700)
* [[User:Enric|Enric]] (-0800/-0700)
* [[User:Evan|evanpro]] (-0500)
* [[User:ChrisMessina|factoryjoe]] (-0800/-0700)
* [[User:Fil|Fil]] (+0200)
* [[User:MarkoMrdjenovic|friedcell]] (+0100/+0200)
* [[User:Grantbow|Grantbow]] (-0800/-0700)
* [[User:Hlb|hlb]] (+0800-0700)
* [[User:IanHickson|Hixie]] (-0800/-0700)
* [[User:EdwardOConnor|hober]] (-0800/-0700)
* [[User:IwaiMasaharu|iwaim]] (+0900)
* [[User:Izo|IZO]]
* [[User:JamieKnight|jammie_]] (+1000/0000)
* [[User:WizardIsHungry|jcw9]] (-0500/-0400)
* [[User:Adactio|Jeremy Keith]] (+0000)
* [[User:JasonK|jkridner]] (-0600/-0500)
* [[User:JoeGregorio|jcgregorio]]
* [[User:Jonathan_Arkell|jonnay]] (-0700/0600)
* [[User:JulianStahnke|Julian Stahnke]] (+0000)
* [[User:Kapowaz|kapowaz]] (+0000/+0100)
* [[User:Keri Henare|kerihenare]] (+1200)
* [http://epeus.blogspot.com/ KevinMarks] (-0800/-0700)
* [[User:RyanKing|kingryan]] (-0800/-0700)
** [http://theryanking.com/blog/archives/2006/04/19/office-hours/ Office hours]: Wednesday, 21:00 UTC
* [[User:Lachlan Hunt|Lachy]] (+1000/+1100)
* [[User:Mark Mansour|Mark Mansour]] (+1100)
* [[User:MarkNormanFrancis|Mark Norman Francis]] (+0000/+0100)
* [[User:CiaranMc|McNulty]] (+0000/+0100)
* [[User:MikeKaply|mkaply]] (-0600/-0500)
* [[User:SteveIvy|monkinetic/redmonk]] (-0700)
* [[User:neuro|neuro`]]
* [[User:NTollervey|ntoll]] (+0000/+0100)
* [[User:Phae|Phae]] (+0000/+0100)
* [[User:PriitLaes|plaes]] (+0200/+0300)
* [[User:ChrisCasciano|pnhChris]] (-0500/-0400)
* [[User:DavidOsolkowski|qid]] (-0500)
* [[User:Remi|Remi]] (-0500/-0400)
* [[User:RobertBachmann|RobertBachmann]] (+0100/+0200)
** Office hours: <del>Wednesday, 18:00-20:00 UTC</del> (Currently no office hours)
* [[User:Ronnos|Ron Kok]] (+0000)
* [[User:Dana Benson|Snowden]] (-0800/-0700)
* [[User:Smackman|Steve Farrell]] (-0800/-0700)
* [[User:Steve Ganz|SteveGanz]] (-0800/-0700)
* [[User:SuperPhly|SuperPhly]] (-600/-500)
* [[User:Tantek|Tantek]] (-0800/-0700)
* [[User:Trovster|trovster]] (-0800/-0700)
* [[User:Tyler|Tyler Roehmholdt]] (-0800/-0700)
* [[User:Vant|vant]] (+0900)
* [[User:KrissWatt|VoodooChild]] (+0000/+0100)
* [[User:JacksonWilkinson|whafro]] (-0500/-0400)
* [[User:Richard Conyard|WhiskeyM]] (+0000)
* [[User:Veeliam|William Lawrence]] (-0800/-0700)
* [[User:Ianloic|yakk]] (-0800/-0700)

x2v-issues

2006-12-20T15:57:41Z

DanC: see also hcard-issues etc.

x2v is one of the main microformats implementations.
The code is managed in an
[http://hg.microformats.org/x2v/ x2v hg repository].
BrianSuda and DanC are starting to track issues here.
See [http://rbach.priv.at/Microformats-IRC/2006-12-20#T154234 #microformats discussion 20 Dec].

See also: [[hcard-tests]], [[hcard-issues]], @@likewise for hCalendar, hAtom...

''Hmm... we'd like to give each issue a URI; how about using mediawiki's TOC support? What sort of issue names strike the best balance between convenience and durability?''

__TOC__

== issue2006-12-20content-encoding ==

X2V's php does not correctly check for content-encodings

== trailing_slash ==

X2V failed trailing slash in rel-tag (this is now fixed)

== FN ORG incomplete ==

FN == ORG (i don't think) is complete

x2v-issues

2006-12-20T15:56:36Z

DanC: a few concrete issues and some mechanics noodling

x2v is one of the main microformats implementations.
The code is managed in an
[http://hg.microformats.org/x2v/ x2v hg repository].
BrianSuda and DanC are starting to track issues here.
See [http://rbach.priv.at/Microformats-IRC/2006-12-20#T154234 #microformats discussion 20 Dec].

''Hmm... we'd like to give each issue a URI; how about using mediawiki's TOC support? What sort of issue names strike the best balance between convenience and durability?''

__TOC__

== issue2006-12-20content-encoding ==

X2V's php does not correctly check for content-encodings

== trailing_slash ==

X2V failed trailing slash in rel-tag (this is now fixed)

== FN ORG incomplete ==

FN == ORG (i don't think) is complete

hcard-tests

2006-12-20T15:48:45Z

DanC: note x2v hg repository and start x2v-issues page

The [http://microformats.org/tests/ hcard and hcalendar tests collection] was announced in a [http://microformats.org/discuss/mail/microformats-dev/2006-June/000102.html Jun 7 2006 message] from [[User:RyanKing]].

It's managed in [http://hg.microformats.org/tests/ an hg repository]. [http://www.selenic.com/mercurial/ hg/mercurial] is a distributed revision control system. It can be a little tricky to unlearn cvs habits; there are some good diagrams in [http://www.selenic.com/mercurial/wiki/index.cgi/Presentations?action=AttachFile&do=get&target=google.pdf slides from a 19 Jun talk that Bryan O'Sullivan gave at google]. The
[http://www.selenic.com/mercurial/wiki/index.cgi/Presentations mercurial presentations page] also has a link to a 50 minute video.

An [http://hg.microformats.org/x2v/ x2v hg repository] holds code that,
by design, passes the tests. [[x2v-issues]] is a place to track issues
in that code.

== External Tests ==

These are subsumed by the above tests, yes?

DanConnolly is working on [http://dev.w3.org/cvsweb/2001/palmagent/hcardTest.html hcardTest.html]; [http://dev.w3.org/cvsweb/~checkout~/2001/palmagent/hcardTest.html?rev=HEAD&content-type=text/html;%20charset=iso-8859-1 the current version] is always available. (I dunno why cvsweb uses the ordinary looing URL for the changelog rather than the current version.)

MarkPilgrim maintains a series of [http://diveintomark.org/projects/greasemonkey/hcard/tests/ hCard tests] for use with his [http://diveintomark.org/projects/greasemonkey/hcard/ hCard parser]

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

hcard-profile

2006-11-13T16:40:28Z

DanC: note a newer profile document in progress

= hCard Profile =

The following is an [http://gmpg.org/xmdp/ XMDP] profile for the [[hcard|hCard]] specification.

It's also available as [http://www.w3.org/2006/03/hcard http://www.w3.org/2006/03/hcard].
See [[profile-uris]] for more details.

http://www.w3.org/2006/vcard/ns has roughly the same information with a different editorial style.

== Profile ==
<pre>
<dl class="profile">
<dt>class</dt>
<dd><p>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
All values are defined according to the semantics defined in the
<a href="http://microformats.org/wiki/hcard">
hCard specification</a>
and thus in
<a href="http://www.ietf.org/rfc/rfc2426.txt">RFC 2426</a>.</p>
<dl>
<dt>vcard</dt>
<dd>A container for the rest of the class names defined in this XMDP profile.
See section 1. of RFC 2426.
</dd>

<dt>fn</dt>
<dd>See section 3.1.1 of RFC 2426.</dd>

<dt>n</dt>
<dd>See section 3.1.2 of RFC 2426. May be inferred per
Implied "N" Optimization.</dd>

<dt>family-name</dt>
<dd>See "Family Name" in section 3.1.2 of RFC 2426.</dd>

<dt>given-name</dt>
<dd>See "Given Name" in section 3.1.2 of RFC 2426.</dd>

<dt>additional-name</dt>
<dd>See "Additional Names" in section 3.1.2 of RFC 2426.</dd>

<dt>honorific-prefix</dt>
<dd>See "Honorific Prefixes" in section 3.1.2 of RFC 2426.</dd>

<dt>honorific-suffix</dt>
<dd>See "Honorific Suffixes" in section 3.1.2 of RFC 2426.</dd>

<dt>nickname</dt>
<dd>See section 3.1.3 of RFC 2426.</dd>

<dt>photo</dt>
<dd>See section 3.1.4 of RFC 2426. Typically used with an <img> tag.
Use the 'src' attribute for URI values. Use the 'data:' URI scheme for
binary values.</dd>

<dt>bday</dt>
<dd>See section 3.1.5 of RFC 2426. Typically used with an <abbr> tag
with the 'title' attribute for the date value, and a human readable date
inside the element.</dd>

<dt>adr</dt>
<dd>See section 3.2.1 of RFC 2426.</dd>

<dt>post-office-box</dt>
<dd>See "post office box" in section 3.2.1 of RFC 2426.</dd>

<dt>extended-address</dt>
<dd>See "extended address" in section 3.2.1 of RFC 2426.</dd>

<dt>street-address</dt>
<dd>See "street address" in section 3.2.1 of RFC 2426.</dd>

<dt>locality</dt>
<dd>See "locality" in section 3.2.1 of RFC 2426.</dd>

<dt>region</dt>
<dd>See "region" in section 3.2.1 of RFC 2426.</dd>

<dt>postal-code</dt>
<dd>See "postal code" in section 3.2.1 of RFC 2426.</dd>

<dt>country-name</dt>
<dd>See "country name" in section 3.2.1 of RFC 2426.</dd>

<dt>type</dt>
<dd>See "type" in the various sections of RFC 2426.</dd>

<dt>value</dt>
<dd>This class name is used to distinguish the actual *value*
of a property from any other cruft that may be in
the element representing the property.</dd>

<dt>label</dt>
<dd>See section 3.2.2 of RFC 2426.</dd>

<dt>tel</dt>
<dd>See section 3.3.1 of RFC 2426.</dd>

<dt>email</dt>
<dd>See section 3.3.2 of RFC 2426.</dd>

<dt>mailer</dt>
<dd>See section 3.3.3 of RFC 2426.</dd>

<dt>tz</dt>
<dd>See section 3.4.1 of RFC 2426. Typically used with an <abbr> tag
with the 'title' attribute for the tz value, and a human readable time zone
inside the element.</dd>

<dt>geo</dt>
<dd>See section 3.4.2 of RFC 2426.</dd>

<dt>latitude</dt>
<dd>See "latitude" in section 3.4.2 of RFC 2426.</dd>

<dt>longitude</dt>
<dd>See "longitude" in section 3.4.2 of RFC 2426.</dd>

<dt>title</dt>
<dd>See section 3.5.1 of RFC 2426.</dd>

<dt>role</dt>
<dd>See section 3.5.2 of RFC 2426.</dd>

<dt>logo</dt>
<dd>See section 3.5.3 of RFC 2426. Typically used with an <img> tag.
Use the 'src' attribute for URI values. Use the 'data:' URI scheme for
binary values.</dd>

<dt>agent</dt>
<dd>See section 3.5.4 of RFC 2426. If the value is a vCard, then
use a nest hCard. For simplicity in that case, the same element that
has the class name of "agent" should use the class name of "vcard".</dd>

<dt>org</dt>
<dd>See section 3.5.5 of RFC 2426.</dd>

<dt>organization-name</dt>
<dd>See "Organization Name" in section 3.5.5 of RFC 2426.
May be inferred per Implied "organization-name" Optimization.</dd>

<dt>organization-unit</dt>
<dd>See "Organization Unit" in section 3.5.5 of RFC 2426.</dd>

<dt>category</dt>
<dd>See section 3.6.1 of RFC 2426.</dd>

<dt>note</dt>
<dd>See section 3.6.2 of RFC 2426.</dd>

<dt>rev</dt>
<dd>See section 3.6.4 of RFC 2426. Typically used with an <abbr> tag
with the 'title' attribute for the date value, and a human readable date
inside the element.</dd>

<dt>sort-string</dt>
<dd>See section 3.6.5 of RFC 2426.</dd>

<dt>sound</dt>
<dd>See section 3.6.6 of RFC 2426. Typically used with either an <a>
or <object> tag. Use the 'data:' URI scheme for binary values.</dd>

<dt>uid</dt>
<dd>See section 3.6.7 of RFC 2426.</dd>

<dt>url</dt>
<dd>See section 3.6.8 of RFC 2426. Typically used with an <a> tag.
</dd>

<dt>class</dt>
<dd>See section 3.7.1 of RFC 2426.</dd>

<dt>key</dt>
<dd>See section 3.7.2 of RFC 2426. Typically used with an <abbr> tag
with the 'title' attribute for the key value, and a human readable key
equivalent inside the element.</dd>

</dl>
</dd>
</dl>
</pre>

== Deprecated ==

2005-09-16:

The following class names have been deprecated in favor of singular names and the use of the "type" sub-property rather than class names for all of its values. hCard publishers MUST NOT use them as a class name.
* plurals:
** additional-names, honorific-prefixes, honorific-suffixes, categories
* type values:
** dom, intl, postal, parcel, home, work, pref, msg, voice, fax, cell, video, pager, bbs, modem, car, isdn, pcs, internet, x400

hcard-faq

2006-08-30T22:11:56Z

DanC: if "breaking strict containment" were a known anti-pattern, a source should have been cited.

<h1> hCard FAQ </h1>

This page is for documenting Q&A about [[hcard|hCard]]. If you have a new question to ask, Please consider first asking your question on the [http://microformats.org/mailman/listinfo/microformats-discuss/ microformats-discuss] list.

<h2> Q&A </h2>

=== Should I use ADDRESS for hCards ===
''Should I use the more semantic <code><nowiki><address></nowiki></code> element for my hCards?''
* Yes the <code><nowiki><address></nowiki></code> element is more semantic, but it is ''too'' specifically semantic for most hCard uses. The poorly named <code><nowiki><address></nowiki></code> element really means <contact-info-for-this-web-page>. The [http://www.w3.org/TR/html401/struct/global.html#h-7.5.6 HTML4 definition of the ADDRESS element] says it is used "to supply contact information for a document or a major part of a document such as a form." Therefore <code><nowiki><address></nowiki></code> should be used for an hCard ONLY IF that hCard represents the contact information for the page or major part thereof. One example of such a usage is on [http://tantek.com/log/ Tantek's blog]. Another way of saying this is the following two statements: Every <address> on a page SHOULD be an hCard. But not every hCard should be an <code><nowiki><address></nowiki></code>. <br /> In short, '''DO NOT''' use <code><nowiki><address></nowiki></code> to markup addresses in general. Only use it to markup the contact information for the page (or major part thereof), and when doing so, use it to markup ''the entire'' contact information (via <address class="vcard">), not just the address of the contact.

=== Why is url property necessary ===
''Why is it necessary to put class name "url" on URL elements in the hCard when those hyperlinks already start with "http://", and that is enough to distinguish them from email links?''
* The classname "url" is necessary to explicitly distinguish hyperlinks that are URL elements for the hCard, from email hyperlinks, as well as hyperlinks to photos, or other random hyperlinks that happen to be inside the hCard.

=== How do I support an existing vCard URL ===
''I already have a vCard that I keep up-to-date. I don't want to change any references to it because it might break something else, what can I do?''
* You can use .HTACCESS to rewrite links to your vCard to a webservice that converts a page to the vCard dynamically, to do this you need to add something similar to your .htaccess file
<pre>
RewriteRule ^path/to/old.vcf http://suda.co.uk/projects/X2V/get-vcard.php\?uri=http://example.com/hCard_encoded.htm&filename=old.vcf
</pre>

Now you shouldn't have to do anything else, all links to the "old.vcf" are redirected to the webservice and will return a new vCard that is dynamially generated from your page.

I think that using 'Redirect' is better than using mod_rewrite (is not enabled on some hosts) --Robert Bachmann
<pre>
Redirect /path/to/old.vcf http://suda.co.uk/projects/X2V/get-vcard.php?uri=http://example.com/hCard_encoded.htm&filename=old.vcf
</pre>

=== What are plural hCard properties ===
''Is there a list of all hCard properties which can be plural?''<br />
''Is there a list of all the properties which can have multiple instances?''
* There is the [[hcard#Property_List|list of hCard properties]], and the list of [[hcard#Singular_properties|singular hCard properties]]. Everything that is not singular is plural. This list was presented explicitly (after much analysis of RFC2426) because it was too hard to read RFC2426 and reliably grok which properties were singular vs. plural.

Old previous answer:
* We have avoided *duplicating* (or providing a shortcut for) the "can this property occur multiple times or not" deliberately in order to avoid repeating a constraint from RFC 2426 vCard, and thus potentially getting it wrong. Here is the way to determine whether or not a particular property can occur multiple times (is a plural property / may have multiple instances or values).
* Check the [[hcard-profile|hCard XMDP profile]] for the property definition.
* If the property definition references a plural form in RFC 2426 (e.g. honorific-suffix references honorific suffixes), then the property is a plural property.
* Else go check the referenced section in RFC 2426 which should state explicitly whether or not the property is plural or singular.
* Else (if RFC 2426 is *not* explicit) then the property is plural.

=== What does FN stand for ===

''What does FN stand for?''
* FN stands for "Formatted Name." From Section 3.1.1 of the RFC:
<blockquote>Type purpose: To specify the formatted text corresponding to the name of the object the vCard represents.</blockquote>
* The reasoning behind this seems to be that, while N gives us a structured name, FN gives us the human-readable, formatted name which is assembled from its structured parts in a culturally dependant way.

=== How is gender represented ===
''How do you represent gender in hCard?''
* There is no GENDER property in [http://www.ietf.org/rfc/rfc2426.txt vCard RFC2426]. [[hcard|hCard]] is following the schema from vCard for interoperability reasons. If you want, it is possible to represent gender implicitly in the honorific-prefix field, e.g. Mr. for male, and Ms. for female:
<pre><nowiki>
<span class="honorific-prefix">Mr.</span>
</nowiki></pre>
or
<pre><nowiki>
<span class="honorific-prefix">Ms.</span>
</nowiki></pre>

Note that there is also a [http://msdn.microsoft.com/workshop/author/dhtml/reference/properties/vcard_name.asp page on MSDN that mentions vCard and "gender"]. Not sure what to make of that.

=== Can an hCard contains extra elements ===
''Is it OK for an hCard node to contain extra elements?''
* Yes, parsers will ignore anything they don't understand.

=== Can a GEO be inferred from an ADR in an hCard ===
''Can I automatically add GEO from an address when transfoming an hCard to vCard if it is not present?''
* No, an address represents a building which is a polygon, whereas a GEO only represents a single point

=== X2V does not convert email with name as plain text ===
''X2V doesn't convert my email address correctly, it is in the form href="FirstName LastName <Email@Address.com>"''
* While that form of email address works for some programs such as outlook, it is not a valid mailto: value (see [http://www.faqs.org/rfcs/rfc2368.html RFC2368]) the FirstName and LastName should be omitted.

=== What hCard properties are required ===
''What properties are required in an hCard?''
* The only required properties are 'fn' (the formatted name) and 'n' (the structured name), but 'n' can under certain circumstances be inferred from the <code>fn</code> property. See the [[hcard#Implied_.22n.22_Optimization|Implied N Optimization]] for details.

=== Does N property require all subproperties ===
''If I use the 'n' property, do I have to use ALL of the sub-properties?''
* No, You can use as many or as few as you need to mark-up the name, but at a minimum you should at least use the 'given-name' and 'family-name' sub-properties if at all possible. If all you have is a nickname/handle/userid, then consider simply marking it up as an 'fn' property and taking advantage of the [http://microformats.org/wiki/hcard#Implied_.22nickname.22_Optimization Implied "nickname" Optimization].

=== Do FN and N need to be on same element ===
''Do the 'fn' and 'n' properties have to be on the same element?''
* No, you can have two separate elements, for example:
<pre><nowiki>
<p class="vcard">My name is
<span class="n">
<span class="honorific-prefix">Mr.</span>
<span class="given-name">John</span>
<span class="additional-name">Q</span>
<span class="family-name">Public</span>
</span>
but you can just call me
<span class="fn">Johnny</span>
</p>
</nowiki></pre>

=== How do you convert a vCard to an hCard ===
''Is there a way to convert a vCard to an hCard?''
* There is no canonical conversion from a vCard to an hCard because you can construct an hCard in many different ways while expressing the same semantics. If you would like to recommend a suggested template hCard to use when displaying vCards in a browser, please propose it to the [http://microformats.org/discuss mailing list].

=== Are descendant elements recognized in a microformat ===
''Are descendants recognized in a microformat property?''
* Yes, for example:
<pre><nowiki>
<span class="country-name">United States <small>of</small> America</span>
</nowiki></pre>
The output would be "United States of America".

=== Do properties like TEL use all descendants ===
''Do properties like TEL use all descendants?'' e.g. <pre><nowiki><span class="tel"><span class="type">Home</span>:<span class="value">+1.234.567.8900</span></span></nowiki></pre><br>''Shouldn't that output be "TEL:Home: +1.234.567.8900"?''
* No. class="value" is used to denote a sub-element which is used for the value of the property. See [[hcard#Value_excerpting|Value excerpting]] for more details.

=== Can you have multiple value elements ===
''Can you have multiple class="value" elements inside a property and what happens to them?''
* Sure, for example:
<code><nowiki><span class="tel"><span class="type">Home</span>:<span class="value">+1</span>.<span class="value">234</span>.<span class="value">567</span>.<span class="value">8900</span></span>
</nowiki></code><br> would output: "+12345678900".

=== Can you mix properties and the root class name ===
''<span id="nesting-properties">Can you put properties on the same element as the root class for a microformat? E.g. class="vcard fn"?</span>''
* No, for several reasons:
** It breaks the simple contextual CSS selector rule for finding and styling property values: .rootname .propertyname which will make it more difficult to write scoped CSS for the properties. For more on why this is important see the [[faq#Class_interactions|microformats FAQ regarding class interactions]].
** It will result in more confusion for parsers which may be parsing nested microformats.

=== Can you mix a property and its subproperties ===
''Can singular sub-properties be mixed with parents?''
* No, all sub-properties MUST be on elements inside their parents.

=== Can you use query strings on email ===
''What happened to the Query String on my email address?''
* Query strings are removed from email addresses because they are not valid for importing to vCards

=== Are ADR and TEL types case sensitive ===
''Is the list of possible types for an ADR and TEL case sensitive?''
* No, enumerated values are case-INsensitive, therefore Home, home, HOME, etc. are all equivalent.

=== How does GEO work with ABBR ===
''What happens to the GEO sub-properties when GEO is used with ABBR?''
* The GEO property can be represented two different ways:
<pre>
<nowiki>
<span class="geo">
<span class="latitude">123.45</span>
<span class="longitude">67.89</span>
</span>

<abbr class="geo" title="123.45;67.89">My House</abbr>
</nowiki>
</pre>
When used with an <abbr> element the latitude and longitude are seperated by a semicolon.

=== Why is the root class name vcard ===
''Why is the root class="vcard" and not 'hcard'?''
* The reason is historical, hCard is based off of the vCard specification.

=== How do you markup a phone extension ===
''How do I mark-up a phone extension in hCard?''
There doesn't seem to be a way to declare a telephone extension in the vCard RFC2426 spec, the suggested way is currently:
<pre><nowiki>
<span class="tel">
<span class="type">cell</span>: <span class="value">800 555-1212 x 1234</span>
</span>
</nowiki></pre>

=== How do you encode IM accounts ===
''How do I encode my IM account in hCard?''
* see [[hcard-examples#New_Types_of_Contact_Info|hCard examples: New Types of Contact Info]]

=== Can you hCard the deceased ===
''How do you make an hCard for the deceased?''
* vCards were never designed to handle date-of-death, please refer to the biographical or [[genealogy-formats]] microformat

=== Any plans for xparams ===
''Are there plans to include x-parameters in future versions of hCard?''
* No. The problem is that each of these x-parameters are vendor specific and are not part of the RFC. Secondly, there is no way to be 100% sure that 'x-foobar' is not just a content-specific HTML class name that the publisher is using for CSS styling.

=== What is a word in implied optimizations ===
''What constitutes a "word" for the purpose of 'implied-n optimization'?''
* "N" can be implied from "FN" when the content of "FN" is broken into two "words" separated by whitespace. For this purpose, a "word" is any sequence of non-whitespace characters including but not limited to low- and high-range alphanumerics and punctuation. A "word" can be characterised by the following regular expression: <pre><nowiki>/\S+/</nowiki></pre>

=== How do you create non English tooltips ===
''My website is not in English and i want the tooltips to be in my native language''
* Properties such as class="type" require an enumerated list of English words. It is possible to use your native language for the displaying tooltip, but still use the English work for the class="type" without it being shown.
<pre><nowiki>
<abbr class="type" title="home">
<span title="[your native word for home here]">
to my home
</span>
</abbr>
</nowiki>
</pre>
Having an span with a title attribute inside the abbr element will only display the title on the span, where you have the text (your native word for home here).

events

2006-08-20T04:36:57Z

DanC: drupalcon in Brussels

<h1> Microformats related events </h1>

Please add any microformats related events (specifically, events where there will be talks on microformats) you find here, and we'll add them to the [[hcalendar|hCalendar]] on the [http://microformats.org home page]. Please also create a page for each specific event, where you can list URLs for the event, event details, create an "Attending" section, link to photos afterwards etc. (See [[events/2006-03-01-w3c-plenary-microformats|Microformats panel at W3C Plenary Day]] for a decent example to mimic). Thanks! -[http://tantek.com/ Tantek]

For presenations in particular, there's [[presentations|a separate wiki page]].

Patterns:
* YYYY-MM-DD: <nowiki>[[events/YYYY-MM-DD-event-session-title Event Session Title]]</nowiki>
* YYYY-MM-DD - YYYY-MM-DD: <nowiki>[[events/YYYY-MM-DD-event-session-title Event Session Title]]</nowiki>

== Upcoming ==
* 2006-08-17, 7:00-8:30PM: [[events/2006-08-17-refresh-dc-microformats|M. Jackson Wilkinson speaking on Microformats]] at [http://www.refresh-dc.org Refresh DC] in Washington, DC
* 2006-08-19, 10:00-10:40AM Brian Suda presents [http://conferences.oreillynet.com/cs/euos2006/view/e_sess/9508 Microformats: Web of Data] at Euro OS Con
* 2006-09-13 - 2006-09-14: Future of Web Apps - Microformats session
* 2006-09-29, 2:45-3:30PM John Allsopp speaking on Microformats at [http://www.webdirections.org Web Directions] in Sydney, Australia
* 2006-09-23 10:00 [http://drupalcon.org/node/36 Microformats and Drupal] at drupalcon in Brussels
* ...

== Recent ==
* 2006-08-05 5-6pm: Microformats at [http://wordcamp.org/ WordCamp], Swedish American Hall, second room, San Francisco, CA. Discussion led by Tantek Çelik, demos by Bill Humphries (Kubrick theme with [[hatom|hAtom]]) and Erica Douglass (Countdown Plugin with [[hcalendar|hCalendar]]).
* 2006-08-03 4-5:30PM: [http://events.commerce.net/?p=77 Server-side Microformats Parsing and MFML] at CommerceNet in Palo Alto
* 2006-07-27 8-9PM [[events/2006-07-27-oscon-microformats-bof|microformats BOF at O'Reilly OSCON]], Location: Room D137-138 in the OCC.
* 2006-07-13: ICWE panel: "Web 2.0" Engineering with Tantek Çelik
* 2006-07-11: [[events/2006-07-11-an-event-apart-microformats|An Event Apart: Microformats]]
* 2006-07-10: 9am-12:30pm [http://www.icwe2006.org/tutorials.htm#tutorial1 ICWE Tutorial on Microformats] by Ryan King @ <abbr title="Stanford Linear Accelerator Center">SLAC</abbr>
* 2006-06-21: [[events/2006-06-21-supernova-decentralizing-data|Supernova 2006 Decentralizing Data workshop]]
* 2006-06-20: Microformats.org [[events/anniversary/1|one year anniversary!]]
* 2006-06-15 - 2006-06-16: [[events/2006-06-16-atmedia-microformats|@media conference - microformats session]]
* 2006-06-13: [[events/2006-06-13-where-2-bof|Where 2.0 Microformats BOF II]] - developing a [[directions-examples|directions]] microformat.
* 2006-06-10: [http://barcamp.org/BarCampParisSiliconSentier BarCampParis]
* 2006-03-01: [[events/2006-03-01-w3c-plenary-microformats|Microformats panel at W3C Plenary Day]]
* 2006-03-02: [http://esw.w3.org/topic/SwigAtTp2006 Semantic Web Interest Group meeting at W3C Technical Plenary], specifically, 1.30-3.30pm Dan Connolly on using "GRDDL" to parse microformats
* 2006-03-07: [[events/2006-03-07-etech-microformats|Microformats at O'Reilly ETech]]
* 2006-03-13: [[events/2006-03-13-sxsw-microformats|Microformats at SXSW Interactive]]
* 2006-03-14: [[events/2006-03-14-sxsw-modulet|Convincing Your Company to Embrace Web Standards at SxSW Interactive]]
* 2006-03-20: [[events/2006-03-20-mix06-microformats|Mix06 Keynote with Tim O'Reilly and Bill Gates discussing microformats]]
* 2006-03-21: [[events/2006-03-21-mix06-microformats|Mix06 Microformats session discussions]]
* 2006-03-22: [[events/2006-03-22-mix06-microformats|Mix06 Microformats session discussions]]
* 2006-04-23 - 2006-04-24 [http://cmprofessionals.org/events/summit/#06spring CM Pros Summit] [http://www.nateaune.com Nate Aune] will be presenting a talk "Microformats and the Future of Syndication" from 16:30-17:30 at the Sheraton Palace Hotel in San Francisco.
* 2006-05-16 - 2006-05-19: [http://xtech.org/ XTech 2006 Conference]
** 2006-05-16 09:00-12:30: Half-day tutorial: [http://xtech06.usefulinc.com/content/tutorials#microformats Microformats from the Ground Up] at Volmer 3. [http://theryanking.com/presentations/2006/xtech/tutorial/ presentation slides].
** 2006-05-18 [http://xtech06.usefulinc.com/schedule#s2006-05-18-14:00 14:00-14:45]: [http://xtech06.usefulinc.com/schedule/detail/148 The Intelligent Design of Microformats]
* 2006-05-22: [http://refreshedinburgh.org/talks/introducing-microformats-your-web-site/ Refresh Edinburgh] Introducing microformats into your website, May 22nd 8pm-9pm.
* 2006-05-23 - 2006-05-26: [http://www2006.org/ www2006]
** 2006-05-23: [http://www.blogpulse.com/www2006-workshop/ WWE 2006 | 3rd Annual Workshop on the Weblogging Ecosystem] - call for papers is now open, and explicitly includes "microformats".
** 2006-05-24:
*** All day: "Microformats: a Pragmatic Path to the Semantic Web" poster (Poster ID 116, by Rohit Khare and Tantek Çelik) presentation at Strathblane Hall on Level 0 opposite the main entrance.
*** 14:00-15:30: Brian Suda will be presenting a microformats demo ([http://www2006.org/programme/item.php?id=d7 Microformats, converting XHTML to vCards and vCalendars]) in the NextWave developer track session. More information about the presentation is available at [[events/www2006]].
** 2006-05-25 10:30-13:30: Molly E. Holzschlag will be presenting a half-day "Practical Microformats" developer tutorial.
* 2006-06-08 [http://glazkov.com/resources/presentations/2006-06-08-microformats/ Microformats]. [[DimitriGlazkov|Dimitri Glazkov]] talks about microformats at [http://ipsaonline.com/ IPSA] monthly meeting.

== Quicktime Broadcaster Notes ==

For setting up a mac laptop with an iSight and QT Broadcaster in order to publish live audio/video from events.

# Make sure you have the necessary equipment and software installed
#* A Macintosh running OSX 10.3.9 or later
#* Quicktime 7 - get it from http://www.apple.com/quicktime/
#* Quicktime Broadcaster - get it from http://www.apple.com/quicktime/broadcaster/
#* An iSight or digital video camera with firewire connection
# Get a broadcast template document from someone (see KevinMarks for example)
# Open that, then change the info in the 'Network' pane that has his name etc in it.
# Check the video and audio panes are using your iSight
# Another tip is that the standalone thingy for the iSight can be more useful than the screen-top one if you have a desk, as that way it picks up less typing noise and wobbles
# I find plugging in headphones is a good idea, as you can then monitor and not get howlround

http://microformats.org/media/broadcast.mov

User:DanC

2006-07-25T20:47:21Z

DanC: link todo list

to-do

2006-07-25T20:46:22Z

DanC: review/revise playlist notes

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

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

=== hCard ===
* microformatted versions of conference pages
** Do a 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/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 ===
* submit patches for Drupal code/templates for microformats improvement
* Drupal modules for microformats, specifically hReview and hCalendar

=== Adding Markup to Existing Pages (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

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

=== *-authoring microformats wiki pages ===
* Add some tips to [[hcard-authoring]]
** a tutorial on creating an hCard for your site
** specific instructions for common blogging platforms
** instructions for more properties (match at least the set that is in the [http://microformats.org/code/hcard/creator hCard creator]
* Create [[hreview-authoring]] - a tutorial on how to blog reviews so that they'll be aggregated.

=== for all microformat specs ===
* 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]] - need to create new pages for [[hcard-examples-in-the-wild]] (perhaps grouped/ sorted by individuals, organizations, and hosting sites?), [[hcard-implementations]] at a minimum to separate out that content, and leave short summaries in their existing place inline in the [[hcard|hCard]] spec.
** [[rel-tag]]
** [[xoxo]]

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

=== iterate on current microformats ===
==== [[hreview|hReview]] ====
* 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.

==== [[hcalendar|hCalendar]] ====
* 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.

==== [[hcard|hCard]] ====
* [[hcard-examples]]
** 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.
* Examples in the wild - need to create a new page for them!
** Group examples in the wild according to:
*** Individuals - one card per person, perhaps sort alphabetically
*** Organizations - one card per organization, alphabetical again
*** Institutions (which list more than one person), with a count estimating the # of hCards, e.g. 40k for Avon
*** Online Profiles (which host profiles for more than one person) with a count estimating the # of hCards, e.g. 3.5m for Flickr.com
*** Online Venues (which provide listings for businesses or organizations) with a count estimating the # of venues, e.g. ~10k for Upcoming.org
*** Speakers Listings (lists of speakers on conference sites) with a count estimating the # of speakers, e.g. ~300 for SXSW 2006.
** help dglazkov markup: http://glazkov.com/blog/archive/2003/12/17/147.aspx

=== introduction / community ===
* microformats-discuss
** introductory email sent to 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.

=== 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)
** ability/suggestion to reference an XMDP using <a href> in addition to <link>

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

=== create microformats wiki pages for ===
* *-authoring for all microformats
* *-parsing for all microformats

=== improve usability and automation on the site ===
* 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.

=== help with microformat implementations ===
* wordpress improvements
** WP admin for new profiles
*** should simply read blog URL
*** 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
** We need to ASAP build a simple conference schedule creator (and editor?) that builds upon the hCalendar creator. We should make 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.

=== help with microformat examples in the wild ===
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.

=== help with 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]].

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

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

* 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

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

== Robert Bachmann ==

=== hCard Creator ===
* [http://microformats.org/code/hcard/creator hCard creator] - add features/fields
** aim / instant messaging contact info, using the techniques documented in [[hcard-examples#New_Types_of_Contact_Info|hCard Examples: New Types of Contact Info]]
*** consider a popup menu for the IM service (AIM|Yahoo|...), and a field next to it for the IM id.

=== hAtom2Atom ===

Some ideas for features which could be implemented :

(If you are interested in one of this features, add "<i>+1 Your Name</i>")

<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:
* MSXML
* .Net System.Xml
* Sablotron
* Oracle XSLT
* XT
</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])
* JSON?
</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)

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

== 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]]
* translate exploraty discussions (red links on [[to-do-fr]]
** find experts for peer-reviewing
* localize an french version of the official website
** find out the original versions of pictures (in SVG ?)
** find out french skills resources to adapt the original webdesign

== New Person 2 ==

etc.

User:DanC

2006-06-24T17:59:06Z

DanC: fix link to hcard-tests

My [http://microformats.org/discuss/mail/microformats-dev/2005-July/000010.html hcardTest materials, XHTML version of RFC2426, and fun with microformats] message is sort of my introduction to this community. I have since discovered the "personal intro" ritual in [http://microformats.org/discuss/mail/microformats-discuss/ microformats-discuss] and I may join that soonish.

Meanwhile, I'm working on [[hcard-tests]] and [[hcard-issues]] and such.

I have written about 6 [http://dig.csail.mit.edu/breadcrumbs/taxonomy/term/26 blog posts tagged microformats] so far.

Ugh... yet another username/password out there. Oh for [http://www.openid.net/ OpenID]!

hcard-tests

2006-06-24T17:58:47Z

DanC: note recent work on test repository, hg repository

The [http://microformats.org/tests/ hcard and hcalendar tests collection] was announced in a [http://microformats.org/discuss/mail/microformats-dev/2006-June/000102.html Jun 7 message] from [[User:RyanKing]].

It's managed in [http://hg.microformats.org/tests/ an hg repository]. [http://www.selenic.com/mercurial/ hg/mercurial] is a distributed revision control system. It can be a little tricky to unlearn cvs habits; there are some good diagrams in [http://www.selenic.com/mercurial/wiki/index.cgi/Presentations?action=AttachFile&do=get&target=google.pdf slides from a 19 Jun talk that Bryan O'Sullivan gave at google]. The
[http://www.selenic.com/mercurial/wiki/index.cgi/Presentations mercurial presentations page] also has a link to a 50 minute video.

== External Tests ==

These are subsumed by the above tests, yes?

DanConnolly is working on [http://dev.w3.org/cvsweb/2001/palmagent/hcardTest.html hcardTest.html]; [http://dev.w3.org/cvsweb/~checkout~/2001/palmagent/hcardTest.html?rev=HEAD&content-type=text/html;%20charset=iso-8859-1 the current version] is always available. (I dunno why cvsweb uses the ordinary looing URL for the changelog rather than the current version.)

MarkPilgrim maintains a series of [http://diveintomark.org/projects/greasemonkey/hcard/tests/ hCard tests] for use with his [http://diveintomark.org/projects/greasemonkey/hcard/ hCard parser]

hcard

2006-06-22T15:05:46Z

DanC: revert Tails link, but note extended version

<h1>hCard</h1>

hCard is a simple, open, distributed contact information format for people, companies, and organizations, which is suitable for embedding in (X)HTML, Atom, RSS, and arbitrary XML. hCard is a 1:1 representation of the vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]) in XHTML, one of several open [[microformats|microformat]] standards.

Want to get started with writing an [[hcard|hCard]]? Use the [http://microformats.org/code/hcard/creator hCard creator] to write up some contact information and publish it, or follow the [[hcard-authoring|hCard authoring tips]] to add hCard markup to your current contact page.

__TOC__

== Specification ==

=== Editor ===
[http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc.]

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

=== Copyright ===
{{MicroFormatCopyrightStatement2004}}

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

=== Inspiration and Acknowledgments ===
Thanks to: my good friend [http://vadim.com/ Vadim] who introduced me to vCard ''many'' years ago, and if I'd only paid more attention then, perhaps I could have helped a lot of people avoid wasting a lot of time reinventing various standards wheels.

== Introduction ==
The vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]), has been broadly interoperably implemented (e.g. Apple's "Address Book" application built into MacOSX).

In addition, many bloggers identify themselves by name and discuss their friends and family. With just a tad bit of structure, bloggers can discuss people in their blog(s) in such a way that spiders and other aggregators can retrieve this information, automatically convert them to vCards, and use them in any vCard application or service.

This specification introduces the '''hCard''' format, which is a 1:1 representation of the aforementioned vCard standard, in semantic XHTML. Bloggers can both embed vCards directly in their web pages, and style them with CSS to make them appear as desired. In addition, hCard enables applications to retrieve information about such vCards directly from web pages without having to reference a separate file.

Use the [http://microformats.org/code/hcard/creator hCard creator], copy the HTML code it generates to your blog or website to publish your contact info.

== Semantic XHTML Design Principles ==
{{semantic-xhtml-design-principles}}

== Format ==
=== In General ===
The vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]) forms the basis of hCard.

The basic format of hCard is to use vCard object/property names in lower-case for class names, and to map the nesting of vCard objects directly into nested XHTML elements.

=== More Semantic Equivalents ===
However, for some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:
* <code>URL</code> in vCard becomes <code><a class="url" href="...">...</a></code> inside the element with <code>class="vcard"</code> in hCard.
* Similarly, <code>EMAIL</code> in vCard becomes <code><nowiki><a class="email" href="mailto:...">...</a></nowiki></code>
* <code>PHOTO</code> in vCard becomes <code><img class="photo" src="..." alt="Photo of ..." /></code> or <code><object class="photo" data="..." type="...">Photo of ...</object></code>
* <code>UID</code> in vCard simply becomes another semantic applied to a specific URL (or EMAIL) for an hCard.

=== Singular vs. Plural Properties ===

For properties which are singular (e.g. "N" and "FN"), the first descendant element with that class should take effect, any others being ignored.

For properties which can be plural (e.g. "TEL"), each class instance should create a instance of that property. Plural properties with subtypes (e.g. TEL with WORK, HOME, CELL) can be optimized to share a common element for the property itself, with each instance of subtype being an appropriately classed descendant of the property element.

==== Plural Properties Singularized ====

Since plural property names become their singular equivalents, even if the original plural property permitted only a single value with multiple components, those multiple components are represented each with their own singularly named property and the the property is effectively multivalued and subject to the above treatment of multivalued properties.

=== Human vs. Machine readable ===

If an <code><abbr></code> element is used for a property, then the '<code>title</code>' attribute of the <code><abbr></code> element is the value of the property, instead of the contents of the element, which instead provide a human presentable version of the value.

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

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

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

=== Value excerpting ===

Sometimes only part of an element which is the equivalent for a property should be used for the value of the property. This typically occurs when a property has a subtype, like TEL. For this purpose, the special class name "<code>value</code>" is introduced to excerpt out the subset of the element that is the value of the property. E.g. here is an hCard fragment for marking up a home phone number:

<pre><nowiki>
<span class="tel">
<span class="type">home</span>:
<span class="value">+1.415.555.1212</span>
</span>
</nowiki></pre>

This hCard fragment could be displayed as:

home: +1.415.555.1212

=== Property Exceptions ===

vCard has several properties which either do not make sense on, or are already implied within the context of a web page. This section explains what to (not) do with them.

# '''NAME''', '''PROFILE''', '''SOURCE''', '''PRODID''', '''VERSION''' properties as defined in Sections 2.1.2, 2.1.3, 2.1.4, 3.6.3, 3.6.9 of RFC 2426. Content publishers MUST NOT use these properties in their hCards, and as such, hCard consumers/parsers MUST IGNORE these properties if they are found within an hCard. Instead. hCard to vCard converters SHOULD use the title of the page where the hCard is found (e.g. the <code><title></code> element in (X)HTML documents) to construct the NAME property, MAY output a PROFILE value of "<code>VCARD</code>" per RFC 2426, SHOULD use the URL of the page where the hCard is found to construct the SOURCE property (e.g. perhaps as a parameter to a URL/service that converts hCards to vCards), for an output vCard stream (e.g. a .vcf file). Only services/applications that output actual vCards should write the PRODID property, with the product identifier for said service/application. Similarly only such services/applications should write the VERSION property, with the value "3.0" (without quotes) per RFC2426 Section 3.6.9.

=== Organization Contact Info ===

If the "FN" and "ORG" properties have the exact same value (typically because they are set on the same element, e.g. class="fn org"), then the hCard represents contact information for a company or organization and should be treated as such. In this case the author MUST also NOT set the "N" property, or set it (and any sub-properties) explicitly to the empty string "". Thus parsers should handle the missing "N" property in this case by implying empty values for all the "N" sub-properties.

=== Implied "n" Optimization ===

Although vCard requires that the "N" property be present, the authors of the vCard specification (RFC 2426) themselves do not include "N" properties in their vCards near the end of the spec (p.38). This apparent contradiction can be resolved by simply allowing the "FN" property to imply "N" property values in typical cases provided in the spec. We do so explicitly in hCard.

If "FN" and "ORG" are not the same (see previous section), and the value of the "FN" property is exactly two words (separated by whitespace), and there is no explicit "N" property, then the "N" property is inferred from the "FN" property. For "FN"s with either one word see below, and for three or more, the author MUST explicitly markup the "N", except for the organization contact info case, [http://microformats.org/wiki/hcard#Organization_Contact_Info see above] for that.

# The content of "FN" is broken into two "words" separated by whitespace.
# The ''first'' word of the "FN" is interpreted as the "given-name" for the "N" property.
# The ''second/last'' word of the "FN" is interpreted as the "family-name" for the "N" property.
# Exception: If the first word ends in a "," comma OR if the second word is a single character (optionally followed by a period "."), then the first word (minus the comma at the end if any) is interpreted as the "family-name" and the second word is interpreted as the "given-name".

This allows simplification in the typical case of people stating:
* given-name (space) family-name
* family-name (comma) given-name
* family-name (comma) given-name-first-initial
* family-name (space) given-name-first-initial (optional period)

=== Implied "nickname" Optimization ===

Due to the prevalence of the use of nicknames/handles/usernames on the Web in actual content published on the Web (e.g. authors of [[hReview|reviews]]), hCard also has an implied "nickname" optimization to handle this.

Similar to the implied "n" optimization, if "FN" and "ORG" are not the same, and the value of the "FN" property is exactly one word, and there is no explicit "N" property, 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.

Note: the hCard may have additional explicit "nickname" property values in addition to the implied nickname.

=== Implied "organization-name" Optimization ===

The "ORG" property has two subproperties, organization-name and organization-unit. Very often authors only publish the organization-name. Thus if an "ORG" property has no "organization-name" inside it, then its entire contents MUST be treated as the "organization-name".

=== Tags as Categories ===

Categories in hCard can optionally be represented by tags with rel-tag. When a category property is a rel-tag, the tag (as defined by rel-tag) is used for that category.

=== Root Class Name ===

The root class name for an hCard is "vcard".

=== Property List ===

This is the list of properties (and subproperties, in parentheses, like this) in hCard, taken from vCard:

* fn, n (family-name, given-name, additional-name, honorific-prefix, honorific-suffix), nickname, sort-string
* url, email (type, value), tel (type, value)
* adr (post-office-box, extended-address, street-address, locality, region, postal-code, country-name, type, value), label
* geo (latitude, longitude), tz
* photo, logo, sound, bday
* title, role, org (organization-name, organization-unit)
* category, note
* class, key, mailer, uid, rev
==== type subproperty values ====

The 'type' subproperty in particular takes different values depending on which property it is a subproperty of. These 'type' subproperty values are case-INSENSITIVE, meaning "Home" is the same as "home", as well as multivalued, e.g. a tel can be home and preferred:
<pre><nowiki>
<span class="tel"><span class="type">Home</span> (<span class="type">pref</span>erred):
<span class="value">+1.415.555.1212</span>
</span>
</nowiki></pre>

The following lists are ''informative''. See RFC2426 sections 3.2.1 ADR, 3.3.1 TEL, and 3.3.2 EMAIL respectively for normative type values. They are repeated here for convenience. Default type subproperty value(s) is(are) first in each list and indicated in ALL CAPS. types may be multivalued.

* adr type: INTL, POSTAL, PARCEL, WORK, dom, home, pref
* tel type: VOICE, home, msg, work, pref, fax, cell, video, pager, bbs, modem, car, isdn, pcs
* email type: INTERNET, x400, pref, "other IANA registered address types"

=== XMDP Profile ===

See [[hcard-profile]] for the [http://gmpg.org/xmdp XMDP] profile of hCard which contains the above complete list of properties, with references to their RFC 2426 definitions.

=== Parsing Details ===

See [[hcard-parsing|hCard parsing]].

== Examples ==

This section is informative.

=== Sample vCard ===

Here is a sample vCard:

<pre><nowiki>
BEGIN:VCARD
VERSION:3.0
N:Çelik;Tantek
FN:Tantek Çelik
URL:http://tantek.com/
ORG:Technorati
END:VCARD
</nowiki></pre>

and an equivalent in hCard with various elements optimized appropriately. See [[hcard-example1-steps| hCard Example 1]] for the derivation.

<pre><nowiki>
<div class="vcard">
<a class="url fn" href="http://tantek.com/">Tantek Çelik</a>
<div class="org">Technorati</div>
</div>
</nowiki></pre>

This hCard might be displayed as:

[http://tantek.com/ Tantek Çelik]<br />
Technorati

Note: The version information is unnecessary in hCard markup directly since the version will be defined by the profile of hCard that is used/referred to in the 'profile' attribute of the <head> element.

=== More Examples ===

See [[hcard-examples]] for more examples, including all examples from vCard RFC 2426 converted into hCard.

== Examples in the wild ==
This section is '''informative'''.

The following sites have published hCards, and thus are a great place to start for anyone looking for examples "in the wild" to try parsing, indexing, organizing etc. If you have an hCard on your own page, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.

=== New Examples ===
Please add new examples to this section.
* [http://main.uab.edu/ University of Alabama at Birmingham] has its contact footer encoded as hCard
* [http://www.capital.edu Capital University] has contact footer and bloggers' names encoded as hCard. Also, all page-specific contact information is encoded as hCards (see [http://www.capital.edu/Internet/Default.aspx?pid=67 Admissions] page for an example)
* [http://main.uab.edu/shrp/ UAB School of Health Professions] uses hCard in its contact footer
* [http://green.carisenda.com/ Stephen Stewart] has his hCard on the front page of his weblog ('You are here' section)
* [http://www.fberriman.com/ Frances Berriman] has a hidden vCard in the footers of her website.
* [http://www.direction.es/ Direction] uses hCard for contact information.
* [http://www.vivabit.com/atmedia2006/speakers/ @media speakers] are marked up with hCard (photos depend on BASE tag support which makes this a good test case)
* [http://www.dougransom.com Doug Ransom] uses hCard for his financial advisory practice.
* [http://rubyandrails.org/usergroups/newcastle/members.html ncl.rb] uses hCard for contact information.
* [http://www.snowinteractive.com/ Snow Interactive] uses hCard for contact information.
* [http://flickr.com Flickr] now supports [[hcard|hCard]] and [http://gmpg.org/xfn XFN] on profile pages. See [http://flickr.com/photos/factoryjoe/113866484/ screenshot of Flickr UI in Flock browser using Flocktails extension - March 17th 2006].
* [http://www.ndiyo.org/contact Contact information for the Ndiyo project]
* [http://www.pixelenvy.co.uk/ Pixel Envy] uses hCard for contact information on every page
* [http://stilbuero.de/contact/ Klaus Hartl] uses hCard in the sidebar for contact information (maybe easier to parse through delivering xhtml as xml).
* [http://charlvn.virafrikaans.com/contact Charl van Niekerk's hCard]
* [http://billy-girlardo.com/WP/ BillyBLOGirlardo] uses hCard for contact information.
* [http://www.hicksdesign.co.uk/ Hicksdesign] uses hCard for contact information.
* http://www.gr0w.com/articles/press/growsearch_launched_press_release/ - hCard in a press release for the press contact info
* http://www.redmonk.com/cote/archives/2006/03/testing_out_mic.html - hCard with explanation
* [http://andy.ciordia.info/ it's my island], personal blog, hcard on the ''[http://andy.ciordia.info/pages/about_me About the Writer]'' page. [[User:Ciordia9|Andy Ciordia]]
* [http://www.windowonwoking.org.uk/ Window on Woking], a local community site in the UK, uses hCard in the homepage of each member organisation and local Councillor.
* [http://ChunkySoup.net/ ChunkySoup.net] has redesigned using hAtom 0.1 and hCards on the entire site -- by [[User:ChrisCasciano|Chris Casciano]]
* [http://www.30boxes.com/ 30 Boxes],a social calendar application and digital lifestyle aggregator, automatically creates an hcard for you with your account. It is found under Settings > Syndication.
* [http://www.nearwhere.com/ Nearwhere.com] allow you to put an hcard on an interactive map.
* [http://www.brentozar.com/ Brent Ozar] added a [http://www.brentozar.com/contact.php contact] page hCard.
* [http://www.kerihenare.com/ Keri Henare] has rewritten his [http://www.kerihenare.com/contact/ contact] page hCard. Now using <code><object></code> instead of <code><img></code> for photo. (Thanks Brian Suda for updating the vCard converter)
* [http://michaelraichelson.com/contact/ Michael Raichelson] had an hCard on his contact page before SXSW, but never thought to add it here until Tantek requested it.
* [http://www.commoner.com/~lsimon/lindsey_simon_hcard.html Lindsey Simon] has added an hCard to his website as per Tantek's SXSW request for folks to try it
* [http://www.davidgagne.net/ David Gagne] has an hCard in his sidebar.
* [http://www.churchzip.com/map/ Churchzip.com/map] and [http://www.skiwhere.com/map/ Skiwhere.com/map], provide churches, hotels, and ski resorts on the same maps. Locations are formatted as hcards.
* All [http://www.iqdir.com/ IQ Directory Solutions] Yellow Pages web portals use [[hcard|hCard]] markup on listings. For example [http://www.yellowpages-cambodia.com/ Cambodia Yellow Pages] and [http://www.superpages.com.my/ Malaysia Super Pages]
* Ning's cloneable Group app uses fuzzy matching to map custom fields to [[hcard|hCard]] markup on its [http://group.ning.com/index.php?controller=person&action=view&content=JonathanAquino profile] pages.
* [http://claimid.com/factoryjoe Chris Messina' ClaimID hCard]
* [http://factoryjoe.com/blog/hcard Chris Messina' hCard]
* [http://flock.com/about Flock About]
* [http://tantek.com/microformats/2006/03-01-TechPlenAgenda.html Agenda: W3C Technical Plenary Day, March 1 2006] has [[hcard|hCard]] and [[hcalendar|hCalendar]] markup. ([http://www.w3.org/2006/03/01-TechPlenAgenda.html original here]).
* [http://www.gr0w.com/articles/press/growsearch_launched_press_release/ GrowSearch Launched (Press Release)] uses an hCard to provide Press Contact Point.
* The [http://www.arborday.org/ National Arbor Day Foundation] has started using hCards for their [http://arborday.org/programs/conferences/communityforestry/index.cfm upcoming] [http://arborday.org/programs/conferences/hazardtrees-treeplanting/ conferences].
* [http://www.multipack.co.uk The Multipack] has numerous hCards, especially on the [http://www.multipack.co.uk/members/ members page], as well as the next meeting information.
* [http://deadringrancor.livejournal.com/ Justin McDowell] used an hCard when [http://deadringrancor.livejournal.com/221332.html referring to a person in his blog post]
* [http://davecardwell.co.uk/cv/ Dave Cardwell] has included his hCard in his Curriculum Vitae.
* [http://blog.usweb.com/ Shaun Shull] has written a great post on [http://blog.usweb.com/archives/how-microformats-affect-search-engine-optimization-seo How Microformats Affect SEO], and has included his [[hcard|hCard]] as one of the examples.
* [http://www.thefutureoftheweb.com/ Jesse Skinner] has written a simple [http://www.thefutureoftheweb.com/blog/2006/1/hcard tutorial with examples]
* [http://www.w3.org/2005/12/allgroupoverview.html 2006 W3C Technical Plenary Week] has marked up the venue, contacts, and program committee members all with hCard.
* [http://www.avf-nexus.co.uk AVF-Nexus] have a hCard on their [http://www.avf-nexus.co.uk/contact/ contact page] - (by [http://creation.uk.com Creation"])
* [http://www.thefantasticos.com/andrew/ Andrew White] posted [http://www.thefantasticos.com/andrew/index.php/my-hcard/ his hCard] and [http://www.thefantasticos.com/andrew/index.php/62/microformats-the-should-have-been-obvious-web-dev-tool/ blogged about it].
* [http://www.2sheds.ru Oleg "2sheds" Kourapov] in his [http://www.2sheds.ru/blog/ blog] ([http://suda.co.uk/projects/X2V/get-vcard.php?uri=http://www.2sheds.ru/blog X2V]) has turned personal profile into hCard ([http://suda.co.uk/projects/X2V/get-vcard.php?uri=http://www.2sheds.ru/blog/hcard.html X2V]) and his blogroll - into combination XFN/hCards ([http://suda.co.uk/projects/X2V/get-vcard.php?uri=http://www.2sheds.ru/blog/friends.html X2V])
* [http://www.approveddesign.co.uk Approved Design Consultancy] have a hCard on their [http://www.approveddesign.co.uk/about/contact/ contact page] as well as on their [http://www.approveddesign.co.uk/about/people/ people section] - (by [http://creation.uk.com Creation"])
* [http://weblog.200ok.com.au/ Ben Buchanan] and [http://www.griffith.edu.au/cgi-bin/phone_search.pl?string=colin+morris&format=search Colin Morris] have [http://weblog.200ok.com.au/2006/01/griffith-phonebook-adds-hcard-and.html implemented hCards and vCards] for the [http://www.griffith.edu.au Griffith University] [http://www.griffith.edu.au/find/content_phonebook.html online phone book]. Eg. [http://www.griffith.edu.au/cgi-bin/phone_search.pl?string=ben+buchanan&format=search Ben's vCard] and [http://www.griffith.edu.au/cgi-bin/phone_search.pl?string=colin+morris&format=search Colin's vCard]
* WWF-Australia [http://wwf.org.au/about/contactdetails/ contact details page]
* [http://rasterweb.net/raster/ Pete Prodoehl] used the hCard format on his [http://rasterweb.net/raster/contact.html Contact page]
* [http://alexander-mette.de amette] uses the hCard format in a module of his TikiWiki powered blog
* [http://staff.washington.edu/oren/weblog2/ Oren Sreebny] has an hcard on his blog main index template
* [http://www.cs.brandeis.edu/~zippy/ Patrick Tufts] has an hCard on his homepage.
* [http://ascii20.blogspot.com/ Mathias Kolehmainen and Jamie Taylor] have hCards on their weblog.
* [http://www.hoppsan.org/jamesb/blogger/ Barnaby James] has a hCard on his weblog.
* [http://esa-education.com/schools/map ESA Education] Uses hCards for their 100+ schools and each of the individual school sites.
* [http://www.thereisnocat.com/#vcard Ralph Brandi] has added an hCard to the sidebar of his weblog as a result of Tantek Çelik's portion of the Microformats presentation at SXSW 2006.
* [http://www.pierce.ctc.edu/ephone/ Pierce College] -- community college directory uses hCard on all individual directory entries.
* [http://www.ukoln.ac.uk/web-focus/events/workshops/webmaster-2006/ the Institutional Web Management Workshop 2006] have marked up all their [http://www.ukoln.ac.uk/web-focus/events/workshops/webmaster-2006/committee/ speakers with hCard].
* http://wikitravel.org/en/Singapore/Sentosa. Wikitravel is experimenting with hcard on its travel guides. This guide uses hcard for all its business listings. More info on http://wikitravel.org/en/Wikitravel_talk:Listings.
* [http://www.musik-erber.de/ Musik-Erber] uses to present contact information at the sidebar
* [http://cdevroe.com/about/#contact Colin D. Devroe] uses hCard to display his contact information on his about page
* The ECS (Scool of Electronics and Computer Science at the University of Southampton) [http://www.ecs.soton.ac.uk/people People Pages] use vCard. Contact cjg@ecs.soton.ac.uk if there's any bugs.
* [http://www.southwestern.edu/~ramseyp Pat Ramsey] has his contact information on his blog marked up with hCard. Contact [mailto:ramsey.pat@gmail.com ramsey.pat@gmail.com] if there are any bugs there.
* [http://www.meryl.net/ Meryl K. Evans] has a hidden hCard on her homepage.

=== Examples ===
* [http://thoughtport.blogspot.com/ Aiden Kenny] hasn't published his hCard yet, but he has [http://thoughtport.blogspot.com/2005/07/elemental-particles-of-web.html published his hCard icon]: http://photos1.blogger.com/blogger/4224/444/320/AK-Hcard-icon.gif
* [http://thedredge.org Andy Hume] uses hCards to mark-up the names and URLs of commentors on his blog, e.g. his [http://thedredge.org/2005/06/using-hcards-in-your-blog/ blog post on "Using hCards in your blog"].
* [http://www.bidclix.com/ BidClix]'s [http://www.bidclix.com/AboutContact.html Contact BidClix] page has it's ''contact info'' marked up with an hCard.
* [http://suda.co.uk/ Brian Suda] has managed to embed a photo in [http://suda.co.uk/contact/ his hCard] through the [http://www.ietf.org/rfc/rfc2397.txt data uri scheme] by converting the image to BASE64 code. View the Source to see how this is accomplished. [http://suda.co.uk/projects/X2V/get-vcard.php?uri=http%3A//suda.co.uk/contact/ The X2V link] will extract the image and encode it for a vCard which will be displayed in some address book applications.
* [http://cinematreasures.org Cinema Treasures] uses hCard to markup venue information for 10,000+ movie theaters.
* [http://www.w3.org/People/Connolly/events/ Dan Connolly's index of events and talks] has hCards for many of the people he has met at those events. In Mar 2006, he moved a bunch of hotel contact info from his PDA to this page; it's now up to 32 hCards.
* [http://doncrowley.blogspot.com/ Don Crowley] has published [http://www.crowley.nl/hcard.html his hCard] as well as a nifty hCard button: http://www.crowley.nl/images/hcard.png
* [http://loadaveragezero.com/hnav/contact.php Douglas W. Clifton] added all types of contact information
* [http://eventful.com Eventful] publishes all of its venue information pages with embedded hCards.
* [http://www.iowamilitaryveteransband.com/members/ Iowa Military Veterans Band Contacts] - 95 hCards [http://weblog.randomchaos.com/archive/2005/10/24/Microformats/ marked up by Scott Reynen]
* [http://JackWolfgang.blogspot.com Jack L. Wolfgang II] has [http://jack.randomata.com/resume/ converted the addresses in his resume to hCards].
* [http://www.efas.fupl.asso.fr/efas/_Mathieu-Drouet_.html Mathieu Drouet] and [http://www.efas.fupl.asso.fr/efas/_Annie-Leger_.html Annie Leger] both have hCards
* [http://www.ndunn.com Neil Dunn] has published his rather [http://www.ndunn.com/2005/10/7/hCard good looking hCard]
* [http://www.oliverbrown.me.uk/ Oliver Brown] has published his hCard.
* [http://www.paradigmproductions.org/contact/ Paradigm Productions] published a vcard as a ul (marked up by [http://www.linkingarts.com/ Peter Jacobson])
* [http://www.splintered.co.uk/ Patrick H. Lauke] has marked up [http://www.splintered.co.uk/about/ his contact info with hCard].
* [http://blah Paul Schreiber has published his hCard on [http://paulschreiber.com/about/?contact his about page].
* [http://paulschreiber.com/blog/ Paul Schreiber]'s [http://concerts.shrub.ca/ Sunnyvale House Concerts] site publishes hCards for upcoming artists, as well as an hCard for the page itself. In addition the [http://concerts.shrub.ca/shows Past Shows] page contains hCards for all past artists.
* [http://www.paulmichaelsmith.com/blog/hcard.htm Paul Smith] has created an hCard page which is Human Readable, and a link to X2V passing the same hCard page to generate a vCard.
* [http://www.windley.com/archives/2005/07/hcards_trying_o.shtml Phil Windley has published] [http://phil.windley.org/hcard.html his hCard].
* [http://www.go-curiosity.com/about.htm Piercarlo Slavazza] has published an hCard.
* [http://zooibaai.nl/ Rob Mientjes] has published his hCard on [http://zooibaai.nl/about/ his about page].
* [http://rbach.priv.at/Contact Robert Bachmann] has published his hCard and [http://rbach.priv.at/Images/hcard a button].
* [http://blah Scott Reynen has published his hCard on [http://www.randomchaos.com/document.php?source=scott_reynen his profile page].
* [http://www.stackframe.com/ StackFrame, LLC] has published [http://www.stackframe.com/people/ employee] and [http://www.stackframe.com/contact/ general] contact information as hCards.
* [http://www.wolfsreign.com Steven Ametjan] has published his hCard on [http://www.wolfsreign.com/about/ his about page].
* [http://tantek.com/microformats/2005/syndicate/speakers-list.html Syndicate - Speaker List] as a set of hCards
* [http://tagcamp.org/index.cgi?ContactList TagCamp contact list]
* [http://tantek.com/log Tantek's Thoughts] includes an inline author hCard at the bottom of the page.
* [http://technorati.com/ Technorati]'s [http://www.technorati.com/about/ About page] lists their '''Media Contact'''
* [http://www.deadringerart.com/ The Brothers McDowell] have hCards at their Contact page.
* [http://twinsparc.com/ Twinsparc] put an hCard in the header and footer of all their pages.
* [http://tantek.com/microformats/2005/web2/speakers.html Web 2.0 Conference speakers page marked up with hCard]
* [http://we05.com/ Web Essentials 05] marked up all their [http://we05.com/presenters.cfm presenters with hCard].

=== Examples with some problems ===

* [http://gbraad.nl/ Gerard Braad] has published an example on his [http://gbraad.nl/site/?p=profile profile] page that is almost consistent with his original [http://gbraad.nl/files/gbraad.vcf vCard] file. Also progress is made for transforming his [http://files.gbraad.nl/foaf.rdf FoaF] file to a hCard encoded representation. (also done for my spouse:[http://spouse.gbraad.nl/site/?p=profile Yong Yuan])
** (2005-09-27) PASSED, PASSED
** WARNINGS
*** uses 'n given-name' and 'n family-name' instead of nesting the given- and family- names inside the 'n'
*** has one 'tel' value with a bunch of values stuffed in
*** probably more problems --[[User:RyanKing|RyanKing]] 17:19, 5 Jan 2006 (PST)
* [http://kinrowan.net/ Cori Schlegel] [http://kinrowan.net/blog/wp/archives/2005/07/08/a-problem-with-the-structured-blogging-plug-in-for-wordpress/ discusses how he has updated] [http://kinrowan.net/blog/contact his contact page with hCard]
** INVALID - using 'prefix' instead of 'honorific-prefix' and type's in classnames (in both adr and tel) and has two photo's (the second could be 'logo') --[[User:RyanKing|RyanKing]] 15:15, 5 Jan 2006 (PST)
* The good ship [http://styrheim.com/test/leonid.html Leonid Miloslavskiy] spotted in the North Atlantic
** INVALID --[[User:RyanKing|RyanKing]] 00:50, 27 Oct 2005 (PDT)
*** class="family" should probably be family-name
*** the "n" property is missing and the "n" optimization can't be applied
*** the first geo propery is empty, the second one is invalid (ie, it doesn't contain lat/long)
* [http://landsbank.fo/#hCard Landsbanki Føroya]
** INVALID - using embedded rdf/xml invalidly
* [http://chrischerry.name/blog/contact/ Chris Cherry's contact page with his hCard]
** WARNING - uses class="cell" instead of <span class="type">cell</span>
* [http://www.bath.ac.uk/contact/ University of Bath] Person Finder results are encoded with hCards so you can easily create a vCard from any result.
** ERROR - attempt to use Implied-N optimization where that's not possible. --[[User:RyanKing|RyanKing]] 14:29, 5 Jan 2006 (PST)
** Error appears for external users only. Won't be fixed any time soon. -- [[User:PhilWilson|PhilWilson]] 00:03, 28 Jan 2006 (GMT)
* [http://richi.co.uk/blog/2005/12/structured-blogging.html Richi Jennings] has put up his attempt
** INVALID, missing FN --[[User:RyanKing|RyanKing]] 12:47, 5 Jan 2006 (PST)
* [http://www.shiftingpixel.com/about/ shifting pixel photoblog] has published an hCard.
** "organization_name" should be "organization-name" (s/_/-/), otherwise good --[[User:RyanKing|RyanKing]] 14:01, 5 Jan 2006 (PST)
* [http://www.yellowpencil.com/contact/ Yellow Pencil] Using microformats to present company contact information
** First hcard has empty "fn" and no "n". "fn" should be with "org" -- [[User: ScottReynen |ScottReynen]] 21:29, 19 Jun 2006 (CST)

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

The following implementations have been developed which either generate or parse hCards. If you have an hCard implementation, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.
* [http://kitchen.technorati.com/search Technorati Microformats Search] indexes [[hcard|hCard]], [[hcalendar|hCalendar]], and [[hreview|hReview]] as [http://tantek.com/log/2006/05.html#d31t1802 announced by Tantek].
** list of pages with indexing Issues so they can be looked into as to why data is not being extracted
** suda.co.uk/contact
** multipack.co.uk

* [http://www.webstandards.org/action/dwtf/microformats/ Dreamweaver Extension suite] from the [http://webstandards.org/ Web Standards Project] enables the authoring of hCards from within Dreamweaver 8.
* [http://scooch.gr0w.com/ Scooch] is a slide show and presentation creator that generates a [[hCard]] for individual slide show authors and comment authors with a CSS button to parse and download via [http://suda.co.uk/projects/X2V/ X2V]. Also uses [[hReview]] for slide ratings and [[rel-tag]] for categories.
* [http://blog.codeeg.com/2006/03/20/flock-tails-flocktails/ Flocktails] - port of Tails extension for Flock 0.5.12 that looks for hCards, hCalendar, xFolk and hReview and tosses them into a handy topbar
*[http://opensource.reevoo.com/2006/03/08/release-uformats-12/ uformats] is a ruby library that can parse [[hCalendar]], [[hCard]], [[hReview]] and [[rel-tag]]
* [http://blog.codeeg.com/tails-firefox-extension/ Tails] is a Firefox Extension that will display the presence and details of microformats ([[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], [[xfolk|xFolk]]) on a webpage. [https://addons.mozilla.org/firefox/2240/ Tails Export] is an extended version.
* [http://www.stripytshirt.co.uk/features/firefox/smartzilla Smartzilla is a Firefox Extension] that finds hCards on web pages and lets you add them to your addressbook.
* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding hCard and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].
* There is [http://flickr.com/photos/factoryjoe/68755089/ evidence of built-in hCard support in the Konqueror browser]. Specifically, Konqueror 3.5, in KDE 3.5 (kubuntu Breezy w/ update).
* There is [http://tagcamp.org/index.cgi?ContactList evidence of a kwiki plugin for hCards]. Update: the [http://svn.kwiki.org/cwest/Kwiki-hCard/ hCard kwiki plugin svn repository]. See the [http://microwiki.caseywest.com/index.cgi?hCard documentation of the hCard kwiki plugin].
* [http://suda.co.uk/projects/X2V/ X2V] is a bookmarklet that parses hCard and produces a .vcf (vCard) stream. Note: needs to be updated as the spec is refined
* [http://www.stripytshirt.co.uk Duncan Walker] has built [http://www.stripytshirt.co.uk/features/firefox/smartzilla a Firefox extension] that gets hCard data from a webpage, uses Brian Suda's XSL (locally) to transform it to vcard format and opens the resulting .vcf file.
* [http://george.hotelling.net/90percent/ George] has written a [http://george.hotelling.net/90percent/geekery/greasemonkey_and_microformats.php Greasemonkey user script] that detects hCards and allows users to easily add them to their address book application. Relies on the X2V web service to do the conversion.
* [http://inside.glnetworks.de/ Martin Rehfeld] has updated the work of [http://blogmatrix.blogmatrix.com/ David Janes] and produced a [[Greasemonkey]] [http://inside.glnetworks.de/2006/06/05/microformats-have-arrived-in-firefox-15-greasemonkey-06/ script] that finds many microformat elements, including hCards, and [http://blog.davidjanes.com/mtarchives/2005_08.html#003379 provides a popup menu of actions]. The hCard to vCard conversion is done internally within the script. ''This will work with FireFox 1.5+/GreaseMonkey 0.6.4+ now.''
* [http://diveintomark.org/ Mark Pilgrim] has also written an [http://diveintomark.org/projects/greasemonkey/hcard/ hCard parser Greasemonkey user script]. It is self-contained and does not rely on the X2V web service.
* [http://www.oliverbrown.me.uk/2005/09/03/a-working-microformats-extension-to-simplexml/ Oliver Brown] has written an "extension" to [http://www.php.net/simplexml SimpleXML] that gives simple access to hCard information in PHP 5.
* [http://thedredge.org/ Andrew D. Hume] has built a system (Wordpress plugin?) for [http://thedredge.org/2005/06/using-hcards-in-your-blog/ using hcards in your blog] to represent people leaving comments on blog posts.
* The [http://tantek.com/microformats/hcard-creator.html hCard creator] is a very simple, yet illustrative, open source user interface / form / script which creates an hCard in real-time as you type in a set of contact information.
* [http://greenbytes.de/tech/webdav/rfc2629.xslt rfc2629.xslt] now attempts to generate hCard information ([http://ietf.org/rfc/rfc2629 RFC2629] is an XML format for authoring RFCs and Internet Drafts,
* [http://greasemonkey.makedatamakesense.com/callto_tel/ callto: tel] is a Greasemonkey user script that finds usable "tel" values in hCards and wraps them in callto: links, for use in VOIP software.

hcard

2006-06-22T14:56:35Z

DanC: update Tails link

<h1>hCard</h1>

hCard is a simple, open, distributed contact information format for people, companies, and organizations, which is suitable for embedding in (X)HTML, Atom, RSS, and arbitrary XML. hCard is a 1:1 representation of the vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]) in XHTML, one of several open [[microformats|microformat]] standards.

Want to get started with writing an [[hcard|hCard]]? Use the [http://microformats.org/code/hcard/creator hCard creator] to write up some contact information and publish it, or follow the [[hcard-authoring|hCard authoring tips]] to add hCard markup to your current contact page.

__TOC__

== Specification ==

=== Editor ===
[http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc.]

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

=== Copyright ===
{{MicroFormatCopyrightStatement2004}}

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

=== Inspiration and Acknowledgments ===
Thanks to: my good friend [http://vadim.com/ Vadim] who introduced me to vCard ''many'' years ago, and if I'd only paid more attention then, perhaps I could have helped a lot of people avoid wasting a lot of time reinventing various standards wheels.

== Introduction ==
The vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]), has been broadly interoperably implemented (e.g. Apple's "Address Book" application built into MacOSX).

In addition, many bloggers identify themselves by name and discuss their friends and family. With just a tad bit of structure, bloggers can discuss people in their blog(s) in such a way that spiders and other aggregators can retrieve this information, automatically convert them to vCards, and use them in any vCard application or service.

This specification introduces the '''hCard''' format, which is a 1:1 representation of the aforementioned vCard standard, in semantic XHTML. Bloggers can both embed vCards directly in their web pages, and style them with CSS to make them appear as desired. In addition, hCard enables applications to retrieve information about such vCards directly from web pages without having to reference a separate file.

Use the [http://microformats.org/code/hcard/creator hCard creator], copy the HTML code it generates to your blog or website to publish your contact info.

== Semantic XHTML Design Principles ==
{{semantic-xhtml-design-principles}}

== Format ==
=== In General ===
The vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]) forms the basis of hCard.

The basic format of hCard is to use vCard object/property names in lower-case for class names, and to map the nesting of vCard objects directly into nested XHTML elements.

=== More Semantic Equivalents ===
However, for some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:
* <code>URL</code> in vCard becomes <code><a class="url" href="...">...</a></code> inside the element with <code>class="vcard"</code> in hCard.
* Similarly, <code>EMAIL</code> in vCard becomes <code><nowiki><a class="email" href="mailto:...">...</a></nowiki></code>
* <code>PHOTO</code> in vCard becomes <code><img class="photo" src="..." alt="Photo of ..." /></code> or <code><object class="photo" data="..." type="...">Photo of ...</object></code>
* <code>UID</code> in vCard simply becomes another semantic applied to a specific URL (or EMAIL) for an hCard.

=== Singular vs. Plural Properties ===

For properties which are singular (e.g. "N" and "FN"), the first descendant element with that class should take effect, any others being ignored.

For properties which can be plural (e.g. "TEL"), each class instance should create a instance of that property. Plural properties with subtypes (e.g. TEL with WORK, HOME, CELL) can be optimized to share a common element for the property itself, with each instance of subtype being an appropriately classed descendant of the property element.

==== Plural Properties Singularized ====

Since plural property names become their singular equivalents, even if the original plural property permitted only a single value with multiple components, those multiple components are represented each with their own singularly named property and the the property is effectively multivalued and subject to the above treatment of multivalued properties.

=== Human vs. Machine readable ===

If an <code><abbr></code> element is used for a property, then the '<code>title</code>' attribute of the <code><abbr></code> element is the value of the property, instead of the contents of the element, which instead provide a human presentable version of the value.

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

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

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

=== Value excerpting ===

Sometimes only part of an element which is the equivalent for a property should be used for the value of the property. This typically occurs when a property has a subtype, like TEL. For this purpose, the special class name "<code>value</code>" is introduced to excerpt out the subset of the element that is the value of the property. E.g. here is an hCard fragment for marking up a home phone number:

<pre><nowiki>
<span class="tel">
<span class="type">home</span>:
<span class="value">+1.415.555.1212</span>
</span>
</nowiki></pre>

This hCard fragment could be displayed as:

home: +1.415.555.1212

=== Property Exceptions ===

vCard has several properties which either do not make sense on, or are already implied within the context of a web page. This section explains what to (not) do with them.

# '''NAME''', '''PROFILE''', '''SOURCE''', '''PRODID''', '''VERSION''' properties as defined in Sections 2.1.2, 2.1.3, 2.1.4, 3.6.3, 3.6.9 of RFC 2426. Content publishers MUST NOT use these properties in their hCards, and as such, hCard consumers/parsers MUST IGNORE these properties if they are found within an hCard. Instead. hCard to vCard converters SHOULD use the title of the page where the hCard is found (e.g. the <code><title></code> element in (X)HTML documents) to construct the NAME property, MAY output a PROFILE value of "<code>VCARD</code>" per RFC 2426, SHOULD use the URL of the page where the hCard is found to construct the SOURCE property (e.g. perhaps as a parameter to a URL/service that converts hCards to vCards), for an output vCard stream (e.g. a .vcf file). Only services/applications that output actual vCards should write the PRODID property, with the product identifier for said service/application. Similarly only such services/applications should write the VERSION property, with the value "3.0" (without quotes) per RFC2426 Section 3.6.9.

=== Organization Contact Info ===

If the "FN" and "ORG" properties have the exact same value (typically because they are set on the same element, e.g. class="fn org"), then the hCard represents contact information for a company or organization and should be treated as such. In this case the author MUST also NOT set the "N" property, or set it (and any sub-properties) explicitly to the empty string "". Thus parsers should handle the missing "N" property in this case by implying empty values for all the "N" sub-properties.

=== Implied "n" Optimization ===

Although vCard requires that the "N" property be present, the authors of the vCard specification (RFC 2426) themselves do not include "N" properties in their vCards near the end of the spec (p.38). This apparent contradiction can be resolved by simply allowing the "FN" property to imply "N" property values in typical cases provided in the spec. We do so explicitly in hCard.

If "FN" and "ORG" are not the same (see previous section), and the value of the "FN" property is exactly two words (separated by whitespace), and there is no explicit "N" property, then the "N" property is inferred from the "FN" property. For "FN"s with either one word see below, and for three or more, the author MUST explicitly markup the "N", except for the organization contact info case, [http://microformats.org/wiki/hcard#Organization_Contact_Info see above] for that.

# The content of "FN" is broken into two "words" separated by whitespace.
# The ''first'' word of the "FN" is interpreted as the "given-name" for the "N" property.
# The ''second/last'' word of the "FN" is interpreted as the "family-name" for the "N" property.
# Exception: If the first word ends in a "," comma OR if the second word is a single character (optionally followed by a period "."), then the first word (minus the comma at the end if any) is interpreted as the "family-name" and the second word is interpreted as the "given-name".

This allows simplification in the typical case of people stating:
* given-name (space) family-name
* family-name (comma) given-name
* family-name (comma) given-name-first-initial
* family-name (space) given-name-first-initial (optional period)

=== Implied "nickname" Optimization ===

Due to the prevalence of the use of nicknames/handles/usernames on the Web in actual content published on the Web (e.g. authors of [[hReview|reviews]]), hCard also has an implied "nickname" optimization to handle this.

Similar to the implied "n" optimization, if "FN" and "ORG" are not the same, and the value of the "FN" property is exactly one word, and there is no explicit "N" property, 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.

Note: the hCard may have additional explicit "nickname" property values in addition to the implied nickname.

=== Implied "organization-name" Optimization ===

The "ORG" property has two subproperties, organization-name and organization-unit. Very often authors only publish the organization-name. Thus if an "ORG" property has no "organization-name" inside it, then its entire contents MUST be treated as the "organization-name".

=== Tags as Categories ===

Categories in hCard can optionally be represented by tags with rel-tag. When a category property is a rel-tag, the tag (as defined by rel-tag) is used for that category.

=== Root Class Name ===

The root class name for an hCard is "vcard".

=== Property List ===

This is the list of properties (and subproperties, in parentheses, like this) in hCard, taken from vCard:

* fn, n (family-name, given-name, additional-name, honorific-prefix, honorific-suffix), nickname, sort-string
* url, email (type, value), tel (type, value)
* adr (post-office-box, extended-address, street-address, locality, region, postal-code, country-name, type, value), label
* geo (latitude, longitude), tz
* photo, logo, sound, bday
* title, role, org (organization-name, organization-unit)
* category, note
* class, key, mailer, uid, rev
==== type subproperty values ====

The 'type' subproperty in particular takes different values depending on which property it is a subproperty of. These 'type' subproperty values are case-INSENSITIVE, meaning "Home" is the same as "home", as well as multivalued, e.g. a tel can be home and preferred:
<pre><nowiki>
<span class="tel"><span class="type">Home</span> (<span class="type">pref</span>erred):
<span class="value">+1.415.555.1212</span>
</span>
</nowiki></pre>

The following lists are ''informative''. See RFC2426 sections 3.2.1 ADR, 3.3.1 TEL, and 3.3.2 EMAIL respectively for normative type values. They are repeated here for convenience. Default type subproperty value(s) is(are) first in each list and indicated in ALL CAPS. types may be multivalued.

* adr type: INTL, POSTAL, PARCEL, WORK, dom, home, pref
* tel type: VOICE, home, msg, work, pref, fax, cell, video, pager, bbs, modem, car, isdn, pcs
* email type: INTERNET, x400, pref, "other IANA registered address types"

=== XMDP Profile ===

See [[hcard-profile]] for the [http://gmpg.org/xmdp XMDP] profile of hCard which contains the above complete list of properties, with references to their RFC 2426 definitions.

=== Parsing Details ===

See [[hcard-parsing|hCard parsing]].

== Examples ==

This section is informative.

=== Sample vCard ===

Here is a sample vCard:

<pre><nowiki>
BEGIN:VCARD
VERSION:3.0
N:Çelik;Tantek
FN:Tantek Çelik
URL:http://tantek.com/
ORG:Technorati
END:VCARD
</nowiki></pre>

and an equivalent in hCard with various elements optimized appropriately. See [[hcard-example1-steps| hCard Example 1]] for the derivation.

<pre><nowiki>
<div class="vcard">
<a class="url fn" href="http://tantek.com/">Tantek Çelik</a>
<div class="org">Technorati</div>
</div>
</nowiki></pre>

This hCard might be displayed as:

[http://tantek.com/ Tantek Çelik]<br />
Technorati

Note: The version information is unnecessary in hCard markup directly since the version will be defined by the profile of hCard that is used/referred to in the 'profile' attribute of the <head> element.

=== More Examples ===

See [[hcard-examples]] for more examples, including all examples from vCard RFC 2426 converted into hCard.

== Examples in the wild ==
This section is '''informative'''.

The following sites have published hCards, and thus are a great place to start for anyone looking for examples "in the wild" to try parsing, indexing, organizing etc. If you have an hCard on your own page, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.

=== New Examples ===
Please add new examples to this section.
* [http://main.uab.edu/ University of Alabama at Birmingham] has its contact footer encoded as hCard
* [http://www.capital.edu Capital University] has contact footer and bloggers' names encoded as hCard. Also, all page-specific contact information is encoded as hCards (see [http://www.capital.edu/Internet/Default.aspx?pid=67 Admissions] page for an example)
* [http://main.uab.edu/shrp/ UAB School of Health Professions] uses hCard in its contact footer
* [http://green.carisenda.com/ Stephen Stewart] has his hCard on the front page of his weblog ('You are here' section)
* [http://www.fberriman.com/ Frances Berriman] has a hidden vCard in the footers of her website.
* [http://www.direction.es/ Direction] uses hCard for contact information.
* [http://www.vivabit.com/atmedia2006/speakers/ @media speakers] are marked up with hCard (photos depend on BASE tag support which makes this a good test case)
* [http://www.dougransom.com Doug Ransom] uses hCard for his financial advisory practice.
* [http://rubyandrails.org/usergroups/newcastle/members.html ncl.rb] uses hCard for contact information.
* [http://www.snowinteractive.com/ Snow Interactive] uses hCard for contact information.
* [http://flickr.com Flickr] now supports [[hcard|hCard]] and [http://gmpg.org/xfn XFN] on profile pages. See [http://flickr.com/photos/factoryjoe/113866484/ screenshot of Flickr UI in Flock browser using Flocktails extension - March 17th 2006].
* [http://www.ndiyo.org/contact Contact information for the Ndiyo project]
* [http://www.pixelenvy.co.uk/ Pixel Envy] uses hCard for contact information on every page
* [http://stilbuero.de/contact/ Klaus Hartl] uses hCard in the sidebar for contact information (maybe easier to parse through delivering xhtml as xml).
* [http://charlvn.virafrikaans.com/contact Charl van Niekerk's hCard]
* [http://billy-girlardo.com/WP/ BillyBLOGirlardo] uses hCard for contact information.
* [http://www.hicksdesign.co.uk/ Hicksdesign] uses hCard for contact information.
* http://www.gr0w.com/articles/press/growsearch_launched_press_release/ - hCard in a press release for the press contact info
* http://www.redmonk.com/cote/archives/2006/03/testing_out_mic.html - hCard with explanation
* [http://andy.ciordia.info/ it's my island], personal blog, hcard on the ''[http://andy.ciordia.info/pages/about_me About the Writer]'' page. [[User:Ciordia9|Andy Ciordia]]
* [http://www.windowonwoking.org.uk/ Window on Woking], a local community site in the UK, uses hCard in the homepage of each member organisation and local Councillor.
* [http://ChunkySoup.net/ ChunkySoup.net] has redesigned using hAtom 0.1 and hCards on the entire site -- by [[User:ChrisCasciano|Chris Casciano]]
* [http://www.30boxes.com/ 30 Boxes],a social calendar application and digital lifestyle aggregator, automatically creates an hcard for you with your account. It is found under Settings > Syndication.
* [http://www.nearwhere.com/ Nearwhere.com] allow you to put an hcard on an interactive map.
* [http://www.brentozar.com/ Brent Ozar] added a [http://www.brentozar.com/contact.php contact] page hCard.
* [http://www.kerihenare.com/ Keri Henare] has rewritten his [http://www.kerihenare.com/contact/ contact] page hCard. Now using <code><object></code> instead of <code><img></code> for photo. (Thanks Brian Suda for updating the vCard converter)
* [http://michaelraichelson.com/contact/ Michael Raichelson] had an hCard on his contact page before SXSW, but never thought to add it here until Tantek requested it.
* [http://www.commoner.com/~lsimon/lindsey_simon_hcard.html Lindsey Simon] has added an hCard to his website as per Tantek's SXSW request for folks to try it
* [http://www.davidgagne.net/ David Gagne] has an hCard in his sidebar.
* [http://www.churchzip.com/map/ Churchzip.com/map] and [http://www.skiwhere.com/map/ Skiwhere.com/map], provide churches, hotels, and ski resorts on the same maps. Locations are formatted as hcards.
* All [http://www.iqdir.com/ IQ Directory Solutions] Yellow Pages web portals use [[hcard|hCard]] markup on listings. For example [http://www.yellowpages-cambodia.com/ Cambodia Yellow Pages] and [http://www.superpages.com.my/ Malaysia Super Pages]
* Ning's cloneable Group app uses fuzzy matching to map custom fields to [[hcard|hCard]] markup on its [http://group.ning.com/index.php?controller=person&action=view&content=JonathanAquino profile] pages.
* [http://claimid.com/factoryjoe Chris Messina' ClaimID hCard]
* [http://factoryjoe.com/blog/hcard Chris Messina' hCard]
* [http://flock.com/about Flock About]
* [http://tantek.com/microformats/2006/03-01-TechPlenAgenda.html Agenda: W3C Technical Plenary Day, March 1 2006] has [[hcard|hCard]] and [[hcalendar|hCalendar]] markup. ([http://www.w3.org/2006/03/01-TechPlenAgenda.html original here]).
* [http://www.gr0w.com/articles/press/growsearch_launched_press_release/ GrowSearch Launched (Press Release)] uses an hCard to provide Press Contact Point.
* The [http://www.arborday.org/ National Arbor Day Foundation] has started using hCards for their [http://arborday.org/programs/conferences/communityforestry/index.cfm upcoming] [http://arborday.org/programs/conferences/hazardtrees-treeplanting/ conferences].
* [http://www.multipack.co.uk The Multipack] has numerous hCards, especially on the [http://www.multipack.co.uk/members/ members page], as well as the next meeting information.
* [http://deadringrancor.livejournal.com/ Justin McDowell] used an hCard when [http://deadringrancor.livejournal.com/221332.html referring to a person in his blog post]
* [http://davecardwell.co.uk/cv/ Dave Cardwell] has included his hCard in his Curriculum Vitae.
* [http://blog.usweb.com/ Shaun Shull] has written a great post on [http://blog.usweb.com/archives/how-microformats-affect-search-engine-optimization-seo How Microformats Affect SEO], and has included his [[hcard|hCard]] as one of the examples.
* [http://www.thefutureoftheweb.com/ Jesse Skinner] has written a simple [http://www.thefutureoftheweb.com/blog/2006/1/hcard tutorial with examples]
* [http://www.w3.org/2005/12/allgroupoverview.html 2006 W3C Technical Plenary Week] has marked up the venue, contacts, and program committee members all with hCard.
* [http://www.avf-nexus.co.uk AVF-Nexus] have a hCard on their [http://www.avf-nexus.co.uk/contact/ contact page] - (by [http://creation.uk.com Creation"])
* [http://www.thefantasticos.com/andrew/ Andrew White] posted [http://www.thefantasticos.com/andrew/index.php/my-hcard/ his hCard] and [http://www.thefantasticos.com/andrew/index.php/62/microformats-the-should-have-been-obvious-web-dev-tool/ blogged about it].
* [http://www.2sheds.ru Oleg "2sheds" Kourapov] in his [http://www.2sheds.ru/blog/ blog] ([http://suda.co.uk/projects/X2V/get-vcard.php?uri=http://www.2sheds.ru/blog X2V]) has turned personal profile into hCard ([http://suda.co.uk/projects/X2V/get-vcard.php?uri=http://www.2sheds.ru/blog/hcard.html X2V]) and his blogroll - into combination XFN/hCards ([http://suda.co.uk/projects/X2V/get-vcard.php?uri=http://www.2sheds.ru/blog/friends.html X2V])
* [http://www.approveddesign.co.uk Approved Design Consultancy] have a hCard on their [http://www.approveddesign.co.uk/about/contact/ contact page] as well as on their [http://www.approveddesign.co.uk/about/people/ people section] - (by [http://creation.uk.com Creation"])
* [http://weblog.200ok.com.au/ Ben Buchanan] and [http://www.griffith.edu.au/cgi-bin/phone_search.pl?string=colin+morris&format=search Colin Morris] have [http://weblog.200ok.com.au/2006/01/griffith-phonebook-adds-hcard-and.html implemented hCards and vCards] for the [http://www.griffith.edu.au Griffith University] [http://www.griffith.edu.au/find/content_phonebook.html online phone book]. Eg. [http://www.griffith.edu.au/cgi-bin/phone_search.pl?string=ben+buchanan&format=search Ben's vCard] and [http://www.griffith.edu.au/cgi-bin/phone_search.pl?string=colin+morris&format=search Colin's vCard]
* WWF-Australia [http://wwf.org.au/about/contactdetails/ contact details page]
* [http://rasterweb.net/raster/ Pete Prodoehl] used the hCard format on his [http://rasterweb.net/raster/contact.html Contact page]
* [http://alexander-mette.de amette] uses the hCard format in a module of his TikiWiki powered blog
* [http://staff.washington.edu/oren/weblog2/ Oren Sreebny] has an hcard on his blog main index template
* [http://www.cs.brandeis.edu/~zippy/ Patrick Tufts] has an hCard on his homepage.
* [http://ascii20.blogspot.com/ Mathias Kolehmainen and Jamie Taylor] have hCards on their weblog.
* [http://www.hoppsan.org/jamesb/blogger/ Barnaby James] has a hCard on his weblog.
* [http://esa-education.com/schools/map ESA Education] Uses hCards for their 100+ schools and each of the individual school sites.
* [http://www.thereisnocat.com/#vcard Ralph Brandi] has added an hCard to the sidebar of his weblog as a result of Tantek Çelik's portion of the Microformats presentation at SXSW 2006.
* [http://www.pierce.ctc.edu/ephone/ Pierce College] -- community college directory uses hCard on all individual directory entries.
* [http://www.ukoln.ac.uk/web-focus/events/workshops/webmaster-2006/ the Institutional Web Management Workshop 2006] have marked up all their [http://www.ukoln.ac.uk/web-focus/events/workshops/webmaster-2006/committee/ speakers with hCard].
* http://wikitravel.org/en/Singapore/Sentosa. Wikitravel is experimenting with hcard on its travel guides. This guide uses hcard for all its business listings. More info on http://wikitravel.org/en/Wikitravel_talk:Listings.
* [http://www.musik-erber.de/ Musik-Erber] uses to present contact information at the sidebar
* [http://cdevroe.com/about/#contact Colin D. Devroe] uses hCard to display his contact information on his about page
* The ECS (Scool of Electronics and Computer Science at the University of Southampton) [http://www.ecs.soton.ac.uk/people People Pages] use vCard. Contact cjg@ecs.soton.ac.uk if there's any bugs.
* [http://www.southwestern.edu/~ramseyp Pat Ramsey] has his contact information on his blog marked up with hCard. Contact [mailto:ramsey.pat@gmail.com ramsey.pat@gmail.com] if there are any bugs there.
* [http://www.meryl.net/ Meryl K. Evans] has a hidden hCard on her homepage.

=== Examples ===
* [http://thoughtport.blogspot.com/ Aiden Kenny] hasn't published his hCard yet, but he has [http://thoughtport.blogspot.com/2005/07/elemental-particles-of-web.html published his hCard icon]: http://photos1.blogger.com/blogger/4224/444/320/AK-Hcard-icon.gif
* [http://thedredge.org Andy Hume] uses hCards to mark-up the names and URLs of commentors on his blog, e.g. his [http://thedredge.org/2005/06/using-hcards-in-your-blog/ blog post on "Using hCards in your blog"].
* [http://www.bidclix.com/ BidClix]'s [http://www.bidclix.com/AboutContact.html Contact BidClix] page has it's ''contact info'' marked up with an hCard.
* [http://suda.co.uk/ Brian Suda] has managed to embed a photo in [http://suda.co.uk/contact/ his hCard] through the [http://www.ietf.org/rfc/rfc2397.txt data uri scheme] by converting the image to BASE64 code. View the Source to see how this is accomplished. [http://suda.co.uk/projects/X2V/get-vcard.php?uri=http%3A//suda.co.uk/contact/ The X2V link] will extract the image and encode it for a vCard which will be displayed in some address book applications.
* [http://cinematreasures.org Cinema Treasures] uses hCard to markup venue information for 10,000+ movie theaters.
* [http://www.w3.org/People/Connolly/events/ Dan Connolly's index of events and talks] has hCards for many of the people he has met at those events. In Mar 2006, he moved a bunch of hotel contact info from his PDA to this page; it's now up to 32 hCards.
* [http://doncrowley.blogspot.com/ Don Crowley] has published [http://www.crowley.nl/hcard.html his hCard] as well as a nifty hCard button: http://www.crowley.nl/images/hcard.png
* [http://loadaveragezero.com/hnav/contact.php Douglas W. Clifton] added all types of contact information
* [http://eventful.com Eventful] publishes all of its venue information pages with embedded hCards.
* [http://www.iowamilitaryveteransband.com/members/ Iowa Military Veterans Band Contacts] - 95 hCards [http://weblog.randomchaos.com/archive/2005/10/24/Microformats/ marked up by Scott Reynen]
* [http://JackWolfgang.blogspot.com Jack L. Wolfgang II] has [http://jack.randomata.com/resume/ converted the addresses in his resume to hCards].
* [http://www.efas.fupl.asso.fr/efas/_Mathieu-Drouet_.html Mathieu Drouet] and [http://www.efas.fupl.asso.fr/efas/_Annie-Leger_.html Annie Leger] both have hCards
* [http://www.ndunn.com Neil Dunn] has published his rather [http://www.ndunn.com/2005/10/7/hCard good looking hCard]
* [http://www.oliverbrown.me.uk/ Oliver Brown] has published his hCard.
* [http://www.paradigmproductions.org/contact/ Paradigm Productions] published a vcard as a ul (marked up by [http://www.linkingarts.com/ Peter Jacobson])
* [http://www.splintered.co.uk/ Patrick H. Lauke] has marked up [http://www.splintered.co.uk/about/ his contact info with hCard].
* [http://blah Paul Schreiber has published his hCard on [http://paulschreiber.com/about/?contact his about page].
* [http://paulschreiber.com/blog/ Paul Schreiber]'s [http://concerts.shrub.ca/ Sunnyvale House Concerts] site publishes hCards for upcoming artists, as well as an hCard for the page itself. In addition the [http://concerts.shrub.ca/shows Past Shows] page contains hCards for all past artists.
* [http://www.paulmichaelsmith.com/blog/hcard.htm Paul Smith] has created an hCard page which is Human Readable, and a link to X2V passing the same hCard page to generate a vCard.
* [http://www.windley.com/archives/2005/07/hcards_trying_o.shtml Phil Windley has published] [http://phil.windley.org/hcard.html his hCard].
* [http://www.go-curiosity.com/about.htm Piercarlo Slavazza] has published an hCard.
* [http://zooibaai.nl/ Rob Mientjes] has published his hCard on [http://zooibaai.nl/about/ his about page].
* [http://rbach.priv.at/Contact Robert Bachmann] has published his hCard and [http://rbach.priv.at/Images/hcard a button].
* [http://blah Scott Reynen has published his hCard on [http://www.randomchaos.com/document.php?source=scott_reynen his profile page].
* [http://www.stackframe.com/ StackFrame, LLC] has published [http://www.stackframe.com/people/ employee] and [http://www.stackframe.com/contact/ general] contact information as hCards.
* [http://www.wolfsreign.com Steven Ametjan] has published his hCard on [http://www.wolfsreign.com/about/ his about page].
* [http://tantek.com/microformats/2005/syndicate/speakers-list.html Syndicate - Speaker List] as a set of hCards
* [http://tagcamp.org/index.cgi?ContactList TagCamp contact list]
* [http://tantek.com/log Tantek's Thoughts] includes an inline author hCard at the bottom of the page.
* [http://technorati.com/ Technorati]'s [http://www.technorati.com/about/ About page] lists their '''Media Contact'''
* [http://www.deadringerart.com/ The Brothers McDowell] have hCards at their Contact page.
* [http://twinsparc.com/ Twinsparc] put an hCard in the header and footer of all their pages.
* [http://tantek.com/microformats/2005/web2/speakers.html Web 2.0 Conference speakers page marked up with hCard]
* [http://we05.com/ Web Essentials 05] marked up all their [http://we05.com/presenters.cfm presenters with hCard].

=== Examples with some problems ===

* [http://gbraad.nl/ Gerard Braad] has published an example on his [http://gbraad.nl/site/?p=profile profile] page that is almost consistent with his original [http://gbraad.nl/files/gbraad.vcf vCard] file. Also progress is made for transforming his [http://files.gbraad.nl/foaf.rdf FoaF] file to a hCard encoded representation. (also done for my spouse:[http://spouse.gbraad.nl/site/?p=profile Yong Yuan])
** (2005-09-27) PASSED, PASSED
** WARNINGS
*** uses 'n given-name' and 'n family-name' instead of nesting the given- and family- names inside the 'n'
*** has one 'tel' value with a bunch of values stuffed in
*** probably more problems --[[User:RyanKing|RyanKing]] 17:19, 5 Jan 2006 (PST)
* [http://kinrowan.net/ Cori Schlegel] [http://kinrowan.net/blog/wp/archives/2005/07/08/a-problem-with-the-structured-blogging-plug-in-for-wordpress/ discusses how he has updated] [http://kinrowan.net/blog/contact his contact page with hCard]
** INVALID - using 'prefix' instead of 'honorific-prefix' and type's in classnames (in both adr and tel) and has two photo's (the second could be 'logo') --[[User:RyanKing|RyanKing]] 15:15, 5 Jan 2006 (PST)
* The good ship [http://styrheim.com/test/leonid.html Leonid Miloslavskiy] spotted in the North Atlantic
** INVALID --[[User:RyanKing|RyanKing]] 00:50, 27 Oct 2005 (PDT)
*** class="family" should probably be family-name
*** the "n" property is missing and the "n" optimization can't be applied
*** the first geo propery is empty, the second one is invalid (ie, it doesn't contain lat/long)
* [http://landsbank.fo/#hCard Landsbanki Føroya]
** INVALID - using embedded rdf/xml invalidly
* [http://chrischerry.name/blog/contact/ Chris Cherry's contact page with his hCard]
** WARNING - uses class="cell" instead of <span class="type">cell</span>
* [http://www.bath.ac.uk/contact/ University of Bath] Person Finder results are encoded with hCards so you can easily create a vCard from any result.
** ERROR - attempt to use Implied-N optimization where that's not possible. --[[User:RyanKing|RyanKing]] 14:29, 5 Jan 2006 (PST)
** Error appears for external users only. Won't be fixed any time soon. -- [[User:PhilWilson|PhilWilson]] 00:03, 28 Jan 2006 (GMT)
* [http://richi.co.uk/blog/2005/12/structured-blogging.html Richi Jennings] has put up his attempt
** INVALID, missing FN --[[User:RyanKing|RyanKing]] 12:47, 5 Jan 2006 (PST)
* [http://www.shiftingpixel.com/about/ shifting pixel photoblog] has published an hCard.
** "organization_name" should be "organization-name" (s/_/-/), otherwise good --[[User:RyanKing|RyanKing]] 14:01, 5 Jan 2006 (PST)
* [http://www.yellowpencil.com/contact/ Yellow Pencil] Using microformats to present company contact information
** First hcard has empty "fn" and no "n". "fn" should be with "org" -- [[User: ScottReynen |ScottReynen]] 21:29, 19 Jun 2006 (CST)

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

The following implementations have been developed which either generate or parse hCards. If you have an hCard implementation, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.
* [http://kitchen.technorati.com/search Technorati Microformats Search] indexes [[hcard|hCard]], [[hcalendar|hCalendar]], and [[hreview|hReview]] as [http://tantek.com/log/2006/05.html#d31t1802 announced by Tantek].
** list of pages with indexing Issues so they can be looked into as to why data is not being extracted
** suda.co.uk/contact
** multipack.co.uk

* [http://www.webstandards.org/action/dwtf/microformats/ Dreamweaver Extension suite] from the [http://webstandards.org/ Web Standards Project] enables the authoring of hCards from within Dreamweaver 8.
* [http://scooch.gr0w.com/ Scooch] is a slide show and presentation creator that generates a [[hCard]] for individual slide show authors and comment authors with a CSS button to parse and download via [http://suda.co.uk/projects/X2V/ X2V]. Also uses [[hReview]] for slide ratings and [[rel-tag]] for categories.
* [http://blog.codeeg.com/2006/03/20/flock-tails-flocktails/ Flocktails] - port of Tails extension for Flock 0.5.12 that looks for hCards, hCalendar, xFolk and hReview and tosses them into a handy topbar
*[http://opensource.reevoo.com/2006/03/08/release-uformats-12/ uformats] is a ruby library that can parse [[hCalendar]], [[hCard]], [[hReview]] and [[rel-tag]]
* [https://addons.mozilla.org/firefox/2240/ Tails is a Firefox Extension] that will display the presence and details of microformats ([[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], [[xfolk|xFolk]]) on a webpage. [http://blog.codeeg.com/tails-firefox-extension/
* [http://www.stripytshirt.co.uk/features/firefox/smartzilla Smartzilla is a Firefox Extension] that finds hCards on web pages and lets you add them to your addressbook.
* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding hCard and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].
* There is [http://flickr.com/photos/factoryjoe/68755089/ evidence of built-in hCard support in the Konqueror browser]. Specifically, Konqueror 3.5, in KDE 3.5 (kubuntu Breezy w/ update).
* There is [http://tagcamp.org/index.cgi?ContactList evidence of a kwiki plugin for hCards]. Update: the [http://svn.kwiki.org/cwest/Kwiki-hCard/ hCard kwiki plugin svn repository]. See the [http://microwiki.caseywest.com/index.cgi?hCard documentation of the hCard kwiki plugin].
* [http://suda.co.uk/projects/X2V/ X2V] is a bookmarklet that parses hCard and produces a .vcf (vCard) stream. Note: needs to be updated as the spec is refined
* [http://www.stripytshirt.co.uk Duncan Walker] has built [http://www.stripytshirt.co.uk/features/firefox/smartzilla a Firefox extension] that gets hCard data from a webpage, uses Brian Suda's XSL (locally) to transform it to vcard format and opens the resulting .vcf file.
* [http://george.hotelling.net/90percent/ George] has written a [http://george.hotelling.net/90percent/geekery/greasemonkey_and_microformats.php Greasemonkey user script] that detects hCards and allows users to easily add them to their address book application. Relies on the X2V web service to do the conversion.
* [http://inside.glnetworks.de/ Martin Rehfeld] has updated the work of [http://blogmatrix.blogmatrix.com/ David Janes] and produced a [[Greasemonkey]] [http://inside.glnetworks.de/2006/06/05/microformats-have-arrived-in-firefox-15-greasemonkey-06/ script] that finds many microformat elements, including hCards, and [http://blog.davidjanes.com/mtarchives/2005_08.html#003379 provides a popup menu of actions]. The hCard to vCard conversion is done internally within the script. ''This will work with FireFox 1.5+/GreaseMonkey 0.6.4+ now.''
* [http://diveintomark.org/ Mark Pilgrim] has also written an [http://diveintomark.org/projects/greasemonkey/hcard/ hCard parser Greasemonkey user script]. It is self-contained and does not rely on the X2V web service.
* [http://www.oliverbrown.me.uk/2005/09/03/a-working-microformats-extension-to-simplexml/ Oliver Brown] has written an "extension" to [http://www.php.net/simplexml SimpleXML] that gives simple access to hCard information in PHP 5.
* [http://thedredge.org/ Andrew D. Hume] has built a system (Wordpress plugin?) for [http://thedredge.org/2005/06/using-hcards-in-your-blog/ using hcards in your blog] to represent people leaving comments on blog posts.
* The [http://tantek.com/microformats/hcard-creator.html hCard creator] is a very simple, yet illustrative, open source user interface / form / script which creates an hCard in real-time as you type in a set of contact information.
* [http://greenbytes.de/tech/webdav/rfc2629.xslt rfc2629.xslt] now attempts to generate hCard information ([http://ietf.org/rfc/rfc2629 RFC2629] is an XML format for authoring RFCs and Internet Drafts,
* [http://greasemonkey.makedatamakesense.com/callto_tel/ callto: tel] is a Greasemonkey user script that finds usable "tel" values in hCards and wraps them in callto: links, for use in VOIP software.

to-do

2006-05-31T22:42:42Z

DanC: fix link markup

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

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

=== hCard ===
* microformatted versions of conference pages
** Do a 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/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 ===
* submit patches for Drupal code/templates for microformats improvement
* Drupal modules for microformats, specifically hReview and hCalendar

=== Adding Markup to Existing Pages (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

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

=== for all microformat specs ===
* 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.

=== iterate on current microformats ===
==== [[hreview|hReview]] ====
* 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.

==== [[hcalendar|hCalendar]] ====
* 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.

==== [[hcard|hCard]] ====
* [[hcard-examples]]
** 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.
* more examples in the wild
** help dglazkov markup: http://glazkov.com/blog/archive/2003/12/17/147.aspx

=== introduction / community ===
* microformats-discuss
** introductory email sent to 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.

=== 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)
** ability/suggestion to reference an XMDP using <a href> in addition to <link>

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

=== create microformats wiki pages for ===
* *-authoring for all microformats
* *-parsing for all microformats

=== improve usability and automation on the site ===
* 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.

=== help with microformat implementations ===
* wordpress improvements
** WP admin for new profiles
*** should simply read blog URL
*** 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
** We need to ASAP build a simple conference schedule creator (and editor?) that builds upon the hCalendar creator. We should make 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.

=== help with microformat examples in the wild ===
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.

=== help with 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]].

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

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

=== *-authoring microformats wiki pages ===
* Add some tips to [[hcard-authoring]] - a tutorial on creating an hCard for your site, blog (common platforms), etc.
* [[hcalendar-authoring]] - a tutorial on how to blog events so your friends can subscribe to them
* [[hreview-authoring]] - a tutorial on how to blog reviews so that they'll be aggregated.

=== 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 ===
* move tests from http://svn.lifelint.com/hcalendar_tests/ to subversion on microformats.org
* 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 ==

* 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

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

== Robert Bachmann ==

=== hCard Creator ===
* [http://microformats.org/code/hcard/creator hCard creator] - add features/fields
** aim / instant messaging contact info, using the techniques documented in [[hcard-examples#New_Types_of_Contact_Info|hCard Examples: New Types of Contact Info]]
*** consider a popup menu for the IM service (AIM|Yahoo|...), and a field next to it for the IM id.

=== hAtom2Atom ===

Some ideas for features which could be implemented :

(If you are interested in one of this features, add "<i>+1 Your Name</i>")

<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:
* MSXML
* .Net System.Xml
* Sablotron
* Oracle XSLT
* XT
</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])
* JSON?
</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)

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

== 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
*** 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]
** update my CV/resume using [[hResume]] and [[citation-formats]]
** noodle on a playlist format and some of the media RSS stuff like [[media-info-brainstorming]]
** 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)

== New Person 2 ==

etc.

to-do

2006-05-31T22:39:47Z

DanC: todo list dump

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

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

=== hCard ===
* microformatted versions of conference pages
** Do a 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/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 ===
* submit patches for Drupal code/templates for microformats improvement
* Drupal modules for microformats, specifically hReview and hCalendar

=== Adding Markup to Existing Pages (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

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

=== for all microformat specs ===
* 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.

=== iterate on current microformats ===
==== [[hreview|hReview]] ====
* 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.

==== [[hcalendar|hCalendar]] ====
* 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.

==== [[hcard|hCard]] ====
* [[hcard-examples]]
** 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.
* more examples in the wild
** help dglazkov markup: http://glazkov.com/blog/archive/2003/12/17/147.aspx

=== introduction / community ===
* microformats-discuss
** introductory email sent to 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.

=== 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)
** ability/suggestion to reference an XMDP using <a href> in addition to <link>

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

=== create microformats wiki pages for ===
* *-authoring for all microformats
* *-parsing for all microformats

=== improve usability and automation on the site ===
* 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.

=== help with microformat implementations ===
* wordpress improvements
** WP admin for new profiles
*** should simply read blog URL
*** 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
** We need to ASAP build a simple conference schedule creator (and editor?) that builds upon the hCalendar creator. We should make 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.

=== help with microformat examples in the wild ===
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.

=== help with 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]].

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

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

=== *-authoring microformats wiki pages ===
* Add some tips to [[hcard-authoring]] - a tutorial on creating an hCard for your site, blog (common platforms), etc.
* [[hcalendar-authoring]] - a tutorial on how to blog events so your friends can subscribe to them
* [[hreview-authoring]] - a tutorial on how to blog reviews so that they'll be aggregated.

=== 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 ===
* move tests from http://svn.lifelint.com/hcalendar_tests/ to subversion on microformats.org
* 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 ==

* 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

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

== Robert Bachmann ==

=== hCard Creator ===
* [http://microformats.org/code/hcard/creator hCard creator] - add features/fields
** aim / instant messaging contact info, using the techniques documented in [[hcard-examples#New_Types_of_Contact_Info|hCard Examples: New Types of Contact Info]]
*** consider a popup menu for the IM service (AIM|Yahoo|...), and a field next to it for the IM id.

=== hAtom2Atom ===

Some ideas for features which could be implemented :

(If you are interested in one of this features, add "<i>+1 Your Name</i>")

<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:
* MSXML
* .Net System.Xml
* Sablotron
* Oracle XSLT
* XT
</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])
* JSON?
</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)

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

== 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
*** 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]
** update my CV/resume using [[hResume]] and [[citation-formats]]
** noodle on a playlist format and some of the media RSS stuff like [[media-info-brainstorming]]
** 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)

== New Person 2 ==

etc.

to-do

2006-05-31T22:13:37Z

DanC: starting my todo list

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

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

=== hCard ===
* microformatted versions of conference pages
** Do a 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/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 ===
* submit patches for Drupal code/templates for microformats improvement
* Drupal modules for microformats, specifically hReview and hCalendar

=== Adding Markup to Existing Pages (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

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

=== for all microformat specs ===
* 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.

=== iterate on current microformats ===
==== [[hreview|hReview]] ====
* 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.

==== [[hcalendar|hCalendar]] ====
* 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.

==== [[hcard|hCard]] ====
* [[hcard-examples]]
** 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.
* more examples in the wild
** help dglazkov markup: http://glazkov.com/blog/archive/2003/12/17/147.aspx

=== introduction / community ===
* microformats-discuss
** introductory email sent to 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.

=== 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)
** ability/suggestion to reference an XMDP using <a href> in addition to <link>

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

=== create microformats wiki pages for ===
* *-authoring for all microformats
* *-parsing for all microformats

=== improve usability and automation on the site ===
* 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.

=== help with microformat implementations ===
* wordpress improvements
** WP admin for new profiles
*** should simply read blog URL
*** 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
** We need to ASAP build a simple conference schedule creator (and editor?) that builds upon the hCalendar creator. We should make 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.

=== help with microformat examples in the wild ===
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.

=== help with 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]].

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

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

=== *-authoring microformats wiki pages ===
* Add some tips to [[hcard-authoring]] - a tutorial on creating an hCard for your site, blog (common platforms), etc.
* [[hcalendar-authoring]] - a tutorial on how to blog events so your friends can subscribe to them
* [[hreview-authoring]] - a tutorial on how to blog reviews so that they'll be aggregated.

=== 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 ===
* move tests from http://svn.lifelint.com/hcalendar_tests/ to subversion on microformats.org
* 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 ==

* 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

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

== Robert Bachmann ==

=== hCard Creator ===
* [http://microformats.org/code/hcard/creator hCard creator] - add features/fields
** aim / instant messaging contact info, using the techniques documented in [[hcard-examples#New_Types_of_Contact_Info|hCard Examples: New Types of Contact Info]]
*** consider a popup menu for the IM service (AIM|Yahoo|...), and a field next to it for the IM id.

=== hAtom2Atom ===

Some ideas for features which could be implemented :

(If you are interested in one of this features, add "<i>+1 Your Name</i>")

<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:
* MSXML
* .Net System.Xml
* Sablotron
* Oracle XSLT
* XT
</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])
* JSON?
</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)

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

== 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]] 15:13, 31 May 2006 (PDT)

== New Person 2 ==

etc.

to-do

2006-05-19T15:20:07Z

DanC: asking the lazyweb to mark up the W3C track at WWW2006 with hCalendar

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

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

=== hCard ===
* microformatted versions of conference pages
** Do a 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/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 ===
* submit patches for Drupal code/templates for microformats improvement
* Drupal modules for microformats, specifically hReview and hCalendar

=== Adding Markup to Existing Pages (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

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

=== for all microformat specs ===
* 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.

=== iterate on current microformats ===
==== [[hreview|hReview]] ====
* 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.

==== [[hcalendar|hCalendar]] ====
* 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.

==== [[hcard|hCard]] ====
* [[hcard-examples]]
** 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.
* more examples in the wild
** help dglazkov markup: http://glazkov.com/blog/archive/2003/12/17/147.aspx

=== introduction / community ===
* microformats-discuss
** introductory email sent to 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.

=== 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)
** ability/suggestion to reference an XMDP using <a href> in addition to <link>

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

=== create microformats wiki pages for ===
* microformats [[history]]
** introduction of terms (when were microformats terms introduced, by whom, etc.)
** introduction of specs (when were microformats specifications first introduced)
*** use the history on Technorati's developer wiki for evidence of earliest dates.
*** use the [[presentations]] as a source as well.

=== improve usability and automation on the site ===
* 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.

=== help with microformat implementations ===
* wordpress improvements
** WP admin for new profiles
*** should simply read blog URL
*** 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
** We need to ASAP build a simple conference schedule creator (and editor?) that builds upon the hCalendar creator. We should make 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.

=== help with 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]].

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

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

=== *-authoring microformats wiki pages ===
* Add some tips to [[hcard-authoring]] - a tutorial on creating an hCard for your site, blog (common platforms), etc.
* [[hcalendar-authoring]] - a tutorial on how to blog events so your friends can subscribe to them
* [[hreview-authoring]] - a tutorial on how to blog reviews so that they'll be aggregated.

=== 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 ===
* move tests from http://svn.lifelint.com/hcalendar_tests/ to subversion on microformats.org
* 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 ==

* 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

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

== Robert Bachmann ==

=== hCard Creator ===
* [http://microformats.org/code/hcard/creator hCard creator] - add features/fields
** aim / instant messaging contact info, using the techniques documented in [[hcard-examples#New_Types_of_Contact_Info|hCard Examples: New Types of Contact Info]]
*** consider a popup menu for the IM service (AIM|Yahoo|...), and a field next to it for the IM id.

=== hAtom2Atom ===

Some ideas for features which could be implemented :

(If you are interested in one of this features, add "<i>+1 Your Name</i>")

<ul>
<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:
* MSXML
* .Net System.Xml
* Sablotron
* Oracle XSLT
* XT
</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])
* JSON?
</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)

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

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

== New Person 2 ==

etc.

meeting-minutes-examples

2006-05-04T22:56:44Z

DanC: W3C meeting minutes tools

= Meeting minutes =
They're typed, they look good, but all the meaning (participants, decisions, action items, etc.) is impossible to glean automatically. Enter hMinutes (or whatever)!

== The Problem ==
''Meeting notes provide a wealth of semantic content, invaluable to organizations. Meeting notes are routinely recorded in intranets, and (with public organizations) on the internet; however, without semantic content it is very difficult to extract the specific information, analyze it, distribute it, or search it effectively. This investigation seeks to document how meeting minutes on the web are structured, towards a lightweight suite of microformats and format extensions for markup.''
== Participants ==
* ''Brush''

== Real-World Examples ==
''These are fairly random, selected for variety of approach. Research is not yet in-depth. Room for more!''

=== [http://www.geneontology.org/minutes/20050408_Pasadena.txt Gene Ontology Consortium] ===
*Abbreviated organization name
*Dates
*Location (locality, region)
*Next meeting date/location (to be confirmed)
*Participants
**Listed by group-affiliation
**Names in comma-delimited parentheses
**Some groups not represented, still listed (like regrets)
*Nested outline of items (XOXO!)
*Major topic -> subsidiary topic
**Includes introduction, by named presenter(s)
**Discussion item list
***Detailed (but flat) following of arguments pro and con
***Identified conclusions (decisions? not formal?)
***Certain items or references id specific people
**Action items
***listed after each topic
***assigned to a person (or to "everyone")
***Also summarized at end of minutes
***Previous action items listed, with status:
****done
****unresolvable
****in progress
****almost done
****other details, etc.
**Brainstorm section
*Next meetings:
**Types
**Dates
**Locations

=== [http://www.stevenshealthcare.org/board_minutes_12.21.05.php Stevens Hospital Board] ===
*Organization, committee
*Date
*Time start/end
*Kind of meeting (ie. special meeting, as opposed to regular)
*Present, with roles:
**member/non-member
**President/Secretary
**organizational affiliations
**also plurally generic (ie. "Hospital Managers and citizens from the community, SEIU 1199NW delegation")
*Outline list (flat) of items
**"Call to order"
**"Oath of office" (ie. establishment of new official roles for individuals)
**Approval of previous minutes (special form of decision)
**Reports from managers/committees
**Authorizations for expenditures
**"Other business"
**Public comment
**Adjournment
*Decisions included in text of items
**motion made
**seconded
**approved unanimously
**included appointments to committees (changes in roles?)
*Items include one, sometimes more specifically referenced speakers

=== [http://www.php.net/~derick/meeting-notes.html PHP Developers Meeting] ===
*Includes relatively unhelpful presentation-oriented table-of-contents link outline markup (more detail?)
*Title
*Date
*Location
*Attendees
**Affiliation
*High-level item
**Includes one-sentence summary
*Second-level item
**Issue
**Discussion
**Conclusion(s)
***Not clear distinction between decisions and action items
***Some action items attached to specific people

=== [http://mail.gnome.org/archives/foundation-list/2004-April/msg00008.html GNOME/Mozilla Meeting] ===
*Title (included two participating organizations)
*Date
*(Email, so "date sent out" included implicitly)
*Attendance
**Organizational affiliation
**minutes
**chair
*Regrets
*Actions (list)
*Discussion (list tree, no titles)
**Specific items inside each discussion item refer to specific person(s)
**Follow pros and cons of arguments

=== [http://www.icann.org/minutes/minutes-10apr06.htm ICANN Executive Committee] ===
*Organization and committee
*form of meeting (ie. teleconference)
*Date
*Time start/end
*Attendance (noted that all were present throughout) with roles:
**member of committee
**member and chair
**non-member, board secretary
**non-member, general counsel
*XOXO-like outline of items
*"Resolved:" decisions for each item.
**vote count (ie. 4-0)
**who proposed
**who seconded
*Also included items deferred to later meetings

== Existing Practices ==
* ''Summary of common patterns discovered'': Anyone? Some things are fairly obvious...
* ''Other attempts to solve The Problem'': Does anyone have references to other schemae attempted to address this issue? How about a semantically marked up implementation!?
** All W3C meetings are recorded, as a matter of policy. There are zillions of teleconference and ftf meeting records. See [http://esw.w3.org/topic/MeetingRecords MeetingRecords in the ESW wiki] for notes, patterns, and tools, especially [http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm the scribe.perl tool], Zakim, and RRSAgent

== Proposal ==
* Early drafts
* ''Link to related pages as they become available''
** -brainstorming
** - proposal
** -microformat
== See Also ==
* ''Other microformats''
* ''Normative references for tags used''

meeting-minutes-examples

2006-05-04T22:55:22Z

DanC: /* Existing Practices */

= Meeting minutes =
They're typed, they look good, but all the meaning (participants, decisions, action items, etc.) is impossible to glean automatically. Enter hMinutes (or whatever)!

== The Problem ==
''Meeting notes provide a wealth of semantic content, invaluable to organizations. Meeting notes are routinely recorded in intranets, and (with public organizations) on the internet; however, without semantic content it is very difficult to extract the specific information, analyze it, distribute it, or search it effectively. This investigation seeks to document how meeting minutes on the web are structured, towards a lightweight suite of microformats and format extensions for markup.''
== Participants ==
* ''Brush''

== Real-World Examples ==
''These are fairly random, selected for variety of approach. Research is not yet in-depth. Room for more!''

=== [http://www.geneontology.org/minutes/20050408_Pasadena.txt Gene Ontology Consortium] ===
*Abbreviated organization name
*Dates
*Location (locality, region)
*Next meeting date/location (to be confirmed)
*Participants
**Listed by group-affiliation
**Names in comma-delimited parentheses
**Some groups not represented, still listed (like regrets)
*Nested outline of items (XOXO!)
*Major topic -> subsidiary topic
**Includes introduction, by named presenter(s)
**Discussion item list
***Detailed (but flat) following of arguments pro and con
***Identified conclusions (decisions? not formal?)
***Certain items or references id specific people
**Action items
***listed after each topic
***assigned to a person (or to "everyone")
***Also summarized at end of minutes
***Previous action items listed, with status:
****done
****unresolvable
****in progress
****almost done
****other details, etc.
**Brainstorm section
*Next meetings:
**Types
**Dates
**Locations

=== [http://www.stevenshealthcare.org/board_minutes_12.21.05.php Stevens Hospital Board] ===
*Organization, committee
*Date
*Time start/end
*Kind of meeting (ie. special meeting, as opposed to regular)
*Present, with roles:
**member/non-member
**President/Secretary
**organizational affiliations
**also plurally generic (ie. "Hospital Managers and citizens from the community, SEIU 1199NW delegation")
*Outline list (flat) of items
**"Call to order"
**"Oath of office" (ie. establishment of new official roles for individuals)
**Approval of previous minutes (special form of decision)
**Reports from managers/committees
**Authorizations for expenditures
**"Other business"
**Public comment
**Adjournment
*Decisions included in text of items
**motion made
**seconded
**approved unanimously
**included appointments to committees (changes in roles?)
*Items include one, sometimes more specifically referenced speakers

=== [http://www.php.net/~derick/meeting-notes.html PHP Developers Meeting] ===
*Includes relatively unhelpful presentation-oriented table-of-contents link outline markup (more detail?)
*Title
*Date
*Location
*Attendees
**Affiliation
*High-level item
**Includes one-sentence summary
*Second-level item
**Issue
**Discussion
**Conclusion(s)
***Not clear distinction between decisions and action items
***Some action items attached to specific people

=== [http://mail.gnome.org/archives/foundation-list/2004-April/msg00008.html GNOME/Mozilla Meeting] ===
*Title (included two participating organizations)
*Date
*(Email, so "date sent out" included implicitly)
*Attendance
**Organizational affiliation
**minutes
**chair
*Regrets
*Actions (list)
*Discussion (list tree, no titles)
**Specific items inside each discussion item refer to specific person(s)
**Follow pros and cons of arguments

=== [http://www.icann.org/minutes/minutes-10apr06.htm ICANN Executive Committee] ===
*Organization and committee
*form of meeting (ie. teleconference)
*Date
*Time start/end
*Attendance (noted that all were present throughout) with roles:
**member of committee
**member and chair
**non-member, board secretary
**non-member, general counsel
*XOXO-like outline of items
*"Resolved:" decisions for each item.
**vote count (ie. 4-0)
**who proposed
**who seconded
*Also included items deferred to later meetings

== Existing Practices ==
* ''Summary of common patterns discovered'': Anyone? Some things are fairly obvious...
* ''Other attempts to solve The Problem'': Does anyone have references to other schemae attempted to address this issue? How about a semantically marked up implementation!?
** All W3C meetings are recorded, as a matter of policy. There are zillions of teleconference and ftf meeting records. See [http://esw.w3.org/topic/MeetingRecords MeetingRecords in the ESW wiki] for notes, patterns, and tools.

== Proposal ==
* Early drafts
* ''Link to related pages as they become available''
** -brainstorming
** - proposal
** -microformat
== See Also ==
* ''Other microformats''
* ''Normative references for tags used''

hcalendar-tests

2006-04-21T17:53:32Z

DanC:

Many of the various sources of [[hcard-tests]] and [[hcalendar]] tests
have been collected into the
[http://hg.microformats.org/tests tests repository],
one of the [http://hg.microformats.org/ microformats hg repositories].
These get discussed in the
microformats-dev [http://microformats.org/discuss/ mailing list] and
pretty regularly on [[irc]].

See also:

* [http://dig.csail.mit.edu/breadcrumbs/node/127 DanC's 19 Apr post] with a screenshot of the version history tree
* [http://theryanking.com/blog/archives/2006/04/19/office-hours/ Ryan on "office hours"]

See also: [http://www.w3.org/2002/12/cal/ RDF Calendar workspace] with icalendar test materials.

hcalendar

2006-04-21T17:43:35Z

DanC: factoring out hcalendar-tests

<h1> hCalendar </h1>

hCalendar is a simple, open, distributed calendaring and events format, based on the iCalendar standard ([http://www.ietf.org/rfc/rfc2445.txt RFC2445]), suitable for embedding in (X)HTML, Atom, RSS, and arbitrary XML. hCalendar is one of several open [[microformats|microformat]] standards.

Want to get started with writing an [[hcalendar|hCalendar]] event? Use the [http://microformats.org/code/hcalendar/creator hCalendar creator] to write up an event and publish it.

__TOC__

== Draft Specification ==

; Editor : [http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc])
; Authors : [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc]
: [http://suda.co.uk/ Brian Suda]

=== Copyright ===
{{MicroFormatCopyrightStatement2004}}

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

=== Inspiration and Acknowledgments ===
Thanks to:
* Adam Bosworth for leading the [http://wiki.oreillynet.com/foocamp04/index.cgi?HTMLForCalendars FOO Camp 2004 HTML For Calendars presentation] which brought together a critical mass of interested parties.

== Introduction ==
The iCalendar standard ([http://www.ietf.org/rfc/rfc2445.txt RFC2445]), has been broadly interoperably implemented (e.g. Apple's "iCal" application built into MacOSX).

In addition, bloggers often discuss events on their blogs -- upcoming events, writeups of past events, etc. With just a tad bit of structure, bloggers can discuss events in their blog(s) in such a way that spiders and other aggregators can retrieve such events, automatically convert them to iCalendar, and use them in any iCalendar application or service.

This specification introduces the '''hCalendar''' format, which is a 1:1 representation of the aforementioned iCalendar standard, in semantic XHTML. Bloggers can both embed hCalendar events directly in their web pages, and style them with CSS to make them appear as desired. In addition, hCalendar enables applications to retrieve information about such events directly from web pages without having to reference a separate file.

== Semantic XHTML Design Principles ==

{{semantic-xhtml-design-principles}}

== Format ==

=== In General ===

The iCalendar standard ([http://www.ietf.org/rfc/rfc2445.txt RFC2445]) forms the basis of hCalendar.

Note: the editor and authors of this specification are tracking the [http://lists.osafoundation.org/pipermail/ietf-calsify/ "iCal-Basic" effort] and intend to base the core hCalendar profile on iCal-Basic. See references for a link to the current draft.

The basic format of hCalendar is to use iCalendar object/property names in lower-case for class names, and to map the nesting of iCalendar objects directly into nested XHTML.

=== More Semantic Equivalents ===

However, for some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:
* <code>URL</code> in iCalendar becomes <code><a class="url" href="...">...</a></code> inside the element with <code>class="vevent"</code> in hCalendar.
* <code>ATTENDEE</code>, <code>CONTACT</code>, and <code>ORGANIZER</code> in iCalendar may be represented by an [[hcard|hCard]] in hCalendar .
* A named <code>LOCATION</code> (potentially with an address and/or geo) in iCalendar may be represented by a nested [[hcard|hCard]] in hCalendar. Similarly, an address <code>LOCATION</code> may be represented by an [[adr]], and a geo (latitude and longitude) <code>LOCATION</code> may be represented by a [[geo]].
* <code>UID</code> in iCalendar simply becomes another semantic applied to a specific URL for an hCalendar event.

=== Singular vs. Multivalued Properties ===

For properties which are singular (e.g. "N" and "FN" from vCard), the first descendant element with that class should take effect, any others being ignored.

For properties which can be plural (e.g. "TEL" from vCard), each class instance should create a instance of that property. Plural properties with subtypes (e.g. TEL with WORK, HOME, CELL from vCard) can be optimized to share a common element for the property itself, with each instance of subtype being an appropriately classed descendant of the property element.

==== Plural Properties Singularized ====

Since plural property names become their singular equivalents, even if the original plural property permitted only a single value with multiple components, those multiple components are represented each with their own singularly named property and the the property is effectively multivalued and subject to the above treatment of multivalued properties.

=== Human vs. Machine readable ===
If an <code><nowiki><abbr></nowiki></code> element is used for a property, then the '<code>title</code>' attribute of the <code><nowiki><abbr></nowiki></code> element is the value of the property, instead of the contents of the element, which instead provide a human presentable version of the value. This specification recommends that such <code><nowiki><abbr></nowiki></code> elements be used for the following iCalendar properties:
* DTSTART, DTEND, DURATION, RDATE, RRULE

== Example ==

Here is a sample event in an iCalendar:
<pre><nowiki>
BEGIN:VCALENDAR
PRODID:-//XYZproduct//EN
VERSION:2.0
BEGIN:VEVENT
URL:http://www.web2con.com/
DTSTART:20051005
DTEND:20051008
SUMMARY:Web 2.0 Conference
LOCATION:Argent Hotel\, San Francisco\, CA
END:VEVENT
END:VCALENDAR
</nowiki></pre>
and an equivalent event in hCalendar format with various elements optimized appropriately. See [[hcalendar-example1-steps]] for the derivation.

<pre><nowiki>
<span class="vevent">
<a class="url" href="http://www.web2con.com/">
<span class="summary">Web 2.0 Conference</span>:
<abbr class="dtstart" title="2005-10-05">October 5</abbr>-
<abbr class="dtend" title="2005-10-08">7</abbr>,
at the <span class="location">Argent Hotel, San Francisco, CA</span>
</a>
</span>
</nowiki></pre>
which could be displayed as:

[http://www.web2con.com/ Web 2.0 Conference: October 5-7, at the Argent Hotel, San Francisco, CA]

Note 1: The product information is not necessary since hCalendar is an interchange format. When transforming hCalendar back into iCalendar, the transforming engine should add its own product ID.

Note 2: A surrounding <code><nowiki><span class="vcalendar"></nowiki></code> element is optional, and is left out as such. It is optional since the context of a vcalendar is implied when a vevent is encountered. The implied context/scope is that of the document. Authors may explicitly use elements with class="vcalendar" to wrap sets of vevents that all belong to the same calendar, e.g. when publishing multiple calendars on the same page.

Note 3: The version information is unnecessary in hCalendar markup directly since the version will be defined by the profile of hCalendar that is used/referred to in the 'profile' attribute of the <head> element.

Note 4: ISO8601 dates (required by iCalendar) are not very human friendly. In addition, the year is often understood implicitly by humans from the context. Thus <code><nowiki><abbr></nowiki></code> elements are used to simultaneously provide a human friendly date and/or time in the visible contents of the element, while placing the respective machine parsable comprehensive ISO8601 datetime in the 'title' attribute.
The notation YYYY-MM-DD should be used for better readability.

Note 5: The difference between the DTEND ISO8601 date (2005-10-08) and the human readable date (7) is NOT a mistake. [http://lists.osafoundation.org/pipermail/ietf-calsify/2005-September/000769.html DTEND is exclusive], meaning, that the event ends just before the DTEND. Thus for events which start on one day and end on another day, the DTEND date must be specified as the day after the day that a human would say is the last day of the event.

Note 6: The location in this example contains implicit structure (venue name, city, state) which could be marked up explicitly as an [[hcard|hCard]]. See [http://microformats.org/wiki/hcalendar-brainstorming#hCard_locations hCalendar brainstorming: hCard locations] for a informative explanation of how to do this.

See [[hcalendar-examples]] for more hCalendar examples

== Examples in the wild ==
This section is '''informative'''.

The following sites have implemented hCalendar, and thus are a great place to start for anyone looking for examples "in the wild" to try parsing, indexing, organizing etc. If events on your pages are marked up with hCalendar, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.

=== New Examples ===
Please add new examples to this section.
* [http://www.argolon.com/2006/04/17/web20-conference-in-dublin/ Web2.0 Conference in Dublin] hCalendar event
* [http://www.meetup.com/ Meetup.com] has marked up [http://www.meetup.com/cities/us/ny/new_york city event calendars], [http://photo.meetup.com/100/events/ group event lists], and [http://www.meetup.com/ signed-in homepages] with hCalendar.
* [http://ukwindsurfing.com/ ukwindsurfing.com] has marked upcoming events with hCalendar, and the [http://ukwindsurfing.com/events/ events page] in a table.
* [http://ocono.com/ ocono.com] has marked up it's "Upcoming Events" list with hCalendar.
* [http://www.austinbloggers.org/ Austin Bloggers] has marked up their "Upcoming Events" box with hCalendar ([http://www.austinbloggers.org/blog/a/001123.html announcement]).
* Ning's cloneable Group app has [[hcalendar|hCalendar]] markup on its [http://group.ning.com/index.php?controller=event&action=list event calendar] and [http://group.ning.com/index.php?controller=event&action=view&id=727220 event detail] pages.
* [http://tantek.com/microformats/2006/03-01-TechPlenAgenda.html Agenda: W3C Technical Plenary Day, March 1 2006] has [[hcard|hCard]] and [[hcalendar|hCalendar]] markup. ([http://www.w3.org/2006/03/01-TechPlenAgenda.html original here]).
* The National Arbor Day Foundation has started using hCalendars for their [http://arborday.org/programs/conferences/communityforestry/index.cfm upcoming] [http://arborday.org/programs/conferences/hazardtrees-treeplanting/ conferences].
* [http://www.multipack.co.uk The Multipack] features a vevent for the next meeting information.
* [http://www.stateofflux.com/ State of Flux street art site] has started adding events in hCalendar format
* The [http://barcamp.org/#BarCamps BarCamp home page lists upcoming BarCamps marked up with hCalendar] and even has a "Subscribe..." link.
* [http://www.w3.org/2005/12/allgroupoverview.html 2006 W3C Technical Plenary Week] has marked up the schedule and events for the week with hCalendar.
* [http://www.code4lib.org/2006/schedule code4lib Conference 2006 Schedule] is marked up with hCalendar as [http://www.code4lib.org/node/65 announced on their blog].
* [http://grouper.ieee.org/groups/754 IEEE 754 Working Group] - trying hCalendar for upcoming meetings.
* [http://www.pehuen.org/node/494 Elecciones 2005 Chile] - the first spanish language hCalendar event found in the wild.
* [http://www.codewitch.org/it/2005/11/17/no-creative-commons-no-party/ Giocolando » No Creative Commons? No Party!] is marked up with hCalendar
* [http://www.cmprofessionals.org/events/calendar.html CM Pros Events Calendar] by Bob Doyle
* [http://www.midgard-project.org/community/events/ Midgard CMS Event calendar] - as [http://bergie.iki.fi/blog/new-event-calendar-for-midcom.html blogged by Henri Bergius]
* [http://www.iowamilitaryveteransband.com/schedule/ Iowa Military Veterans Band Schedule] - hCalendar markup [http://weblog.randomchaos.com/archive/2005/10/24/Microformats/ added by Scott Reynen]
* [http://www.funfairgames.net/weblog/posts/00000011.html Upcoming events on Jason A.R. Moody Amusements Weblog] posted by Jason Moody on 15 Oct 2005. [http://www.funfairgames.net/weblog/index.html His weblog] in general has hCalendar events posted inside the blog posts.
* [http://tantek.com/microformats/2005/syndicate/tracks-sessions-schedule.html Syndicate - Tracks & Sessions]
* [http://tantek.com/microformats/2005/web2/program.html Web 2.0 Conference schedule page marked up with hCalendar]
* [http://www.thisiscmon.com/ C'MON] is a rock band from Canada, and their [http://www.thisiscmon.com/shows/ tour dates] have been marked up by [http://www.d2digitalmedia.com/ Ray Dickman] with hCalendar.
* [http://ifreebusy.com/ ifreebusy.com] will display freebusy information using hCalendar. See this [http://ifreebusy.com/neiljensen/freebusy/ example].
* [http://we05.com/ Web Essentials 05] has marked up their [http://we05.com/program.cfm program schedule table with hCalendar], using the 'axis' and 'headers' attributes.
* [http://www.asdvbonaparte.nl/ ASDV Bonaparte] is a Dutch debating society. Their events calendar has been marked up with the hCalendar conventions.
* [http://chocnvodka.blogware.com/blog Suw Charman] has marked up [http://suw.org.uk/archives/category/events/ her events] with hCalendar.
* [http://www.blogbusinesssummit.com/ Blog Business Summit] has published their [http://www.blogbusinesssummit.com/details.htm event details] marked up with hCalendar.
* [http://evdb.com EVDB], the Events and Venues database, publishes all events with hCalendar and venues with [[hcard|hCard]]. Took them only 15 minutes to implement both!
* [http://upcoming.org Upcoming.org] publishes all events and lists of events with hCalendar. Took them only an hour to add hCalendar support to the site.
* The [http://laughingsquid.com/squidlist/calendar/ Laughing Squid Calendar] events, [http://laughingsquid.com/squidlist/calendar/9949/2005/5/9 e.g. this party], now supports hCalendar.
* [http://paulschreiber.com/ Paul] Schreiber's [http://concerts.shrub.ca/ Sunnyvale House Concerts] site publishes hCalendar event information for upcoming concerts. In addition the [http://concerts.shrub.ca/shows Past Shows] page contains hCalendar events for all past concerts.
* [http://paulschreiber.com/ Paul] Schreiber's [http://iceoasis.shrub.ca/ unofficial schedule site] publishes hCalendar information for upcoming hockey games at [http://www.iceoasis.com/ Ice Oasis]
* [http://www.complexspiral.com/ Complex Spiral Consulting], both in the "Events" box on left side, and the separate [http://www.complexspiral.com/events/ Events page].
* [http://tantek.com/log Tantek's Thoughts], specifically the "Events" roll in the right-most column.
* [http://suda.co.uk/projects/holidays/ Lesser Known Holidays], a list of holidays on [http://suda.co.uk suda.co.uk] that can be imported via iCal and hCal so you can compare actual transformation versus intended.
* [http://norman.walsh.name/2005/itinerary/ Norm Walsh's travel schedule] use hCalendar as well as GRDDL.
* [http://www.policyawareweb.org/2005/ftf2/paw-mtg Policy Aware Web (PAW) Project Meeting] uses hCalendar to record date-related decisions, and uses a vtodo microformat to record action items.
* The [http://www.kiez-ev.de/ Kiez] is a small cinema and has published its [http://www.kiez-ev.de/programm.htm program] marked up with hCalendar.
* The [http://lufgi4.informatik.rwth-aachen.de Laboratory for Dependable Distributed Systems] publishes it's [http://lufgi4.informatik.rwth-aachen.de/cfps list of notable CfPs on dependability and security] with hCalendar-todo elements.
* The [http://laughingsquid.com/laughing-squid-10th-anniversary-party/ Laughing Squid 10th Anniversary Party] has an hcalendar page.
* SPRACI has hcalendar versions of its nightlife/clubbing/gigs/festivals listings for many cities worldwide - eg: [http://www.spraci.com/listhcalendar.php?parea=sydney&category=all Events in Sydney] (check the [http://www.spraci.com/api/ API] pages in the faq section of [http://www.spraci.com/ SPRACI] for more info about the area/city keywords and category tags to use to get data for your city/categories
* WWF-Australia events calendars: [http://wwf.org.au/act/events/ What's on], [http://wwf.org.au/act/volunteer/ Volunteer]
* [http://rubyholic.com rubyholic] uses hCalendar to publish calendars for ruby groups.

=== Examples with some problems ===
* [http://www.webanalyticsassociation.org/en/calendarevents/search.asp Web Analytics Association] - hCalendar microformat is in place on all Tendenci sites on the calendar events search page and consolidated list page.
** WARNINGS
*** has only dates where there should be datetime's
*** has abbr's with no title
*** should probably markup the description --[[User:RyanKing|RyanKing]] 16:04, 6 Jan 2006 (PST)
* [http://www.bokle.de/ s'Bokle] is a German music pub. Their events calendar has been marked up with hCalendar.
** improper use of rrule --[[User:RyanKing|RyanKing]] 16:04, 6 Jan 2006 (PST)

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

The following implementations have been developed which either generate or parse hCalendars. If you have an hCalendar implementation, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.

=== Authoring ===
Implementations you can use to author, create, and publish hCalendar events.
==== Blogging and CMS tools ====
;Midgard CMS : [http://www.midgard-project.org/documentation/net-nemein-calendar/ Midgard CMS - net.nemein.calendar] - as [http://bergie.iki.fi/blog/new-event-calendar-for-midcom.html blogged by Henri Bergius]

;Drupal module : [http://hybernaut.com/upcoming-hcal Drupal Upcoming.org syndication module emits hCalendar]
;MovableType and WordPress plug-ins : [http://structuredblogging.org/formats.php StructuredBlogging] is a set of plugins [http://structuredblogging.org/structuredblogging-wp-latest.zip for WordPress] and [http://structuredblogging.org/structuredblogging-wp-latest.zip for MovableType] that supports embedding hCalendar and other microformats in templates and blog posts.
;Textpattern plug-in : [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding hCalendar and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].

==== Browser scripts and plug-ins ====
Browser plugins that work with existing authoring tools:
; Any browser with javascript and a little bit of CSS : [http://microformats.org/code/hcalendar/creator microformats.org hCalendar creator] (see also original: [http://theryanking.com/ Ryan King] has an [http://theryanking.com/microformats/hcalendar-creator.html hCalendar creator]).
; Firefox Greasemonkey user script hCalendar creator : [http://www.decafbad.com/blog/2005/06/08/greasemonkey_magic magic_hcalendar Greasemonkey user script by Les Orchard] - allows easy form entry of an event into any textarea, e.g. into a blog post text area.
; Firefox Greasemonkey user script hCalendar to Google Calendar: [http://torrez.us Elias Torres] has created a [http://torrez.us/archives/2006/04/13/431/ simple script] that will parse hCalendar entries and create a link to add event to [http://www.google.com/calendar/ Google Calendar's] service. Based on [http://virtuelvis.com/archives/2005/11/learn-to-love-microformats George's] and [http://virtuelvis.com/archives/2005/11/learn-to-love-microformats Arve's] work.

==== Desktop Authoring Tools ====
;Dreamweaver Extension : [http://www.webstandards.org/action/dwtf/microformats/ Extension suite] for Dreamweaver 8 from the [http://webstandards.org/ Web Standards Project].
;xfy :
In [https://www.xfytec.com/community/ xfy Community], there are some hCalendar implementations.

* [https://www.xfytec.com/community/modules/mydownloads/singlefile.php?cid=15&lid=25 hCalendar via RSS] parses an RSS feed, retrieves XHTML documents linked from that feed, and syndicates hCalendars into a calendar view.
* [https://www.xfytec.com/community/modules/mydownloads/singlefile.php?cid=19&lid=23 hCalendar Marker XVCD] helps to mark up an event information in XHTML document with hCalendar.
* [https://www.xfytec.com/community/modules/mydownloads/singlefile.php?cid=15&lid=17 Simple RDF Calendar XVCD] is a schedule tool which uses RDF Calendar format. It also converts RDF Calendar format to iCalendar and hCalendar format.

=== Browsing ===
;Firefox extension: [http://blog.codeeg.com/tails-firefox-extension/ Tails is a Firefox Extension] that will display the presence of microformats ([[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], [[xfolk|xFolk]]) on a webpage.

;Flock extension: [http://blog.codeeg.com/2006/03/20/flock-tails-flocktails/ Flocktails] - port of Tails extension for Flock 0.5.12 that looks for hCards, hCalendar, xFolk and hReview and tosses them into a handy topbar

=== Conversion ===
Importing into a Calendar Application by converting hCalendar to iCalendar/vCalendar.
==== Server Based ====
These return iCalendar (.ics) and other calendar formats for easy importing into typical calendar programs or other processing.
* [http://feeds.technorati.com/events Technorati Events Feed service] uses X2V library to parse hCalendar and return iCalendar (.ics). Note friendly URL, e.g. http://feeds.technorati.com/events/http%3A//microformats.org
* [http://suda.co.uk/projects/X2V/ X2V] parses hCalendar and produces a .ics (iCalendar) stream. Note: needs to be updated to track changes in the specification as they occur.
* [http://lifelint.net/ Life Lint Parser] parses hCalendar and produces .ics, .rdf and debugging information and attempts to be more fully compliant to the iCal standard than previous implementations. It can be used in the same manner as X2V. Can output iCal (w optional Outlook 2002 compat), and RDF.
* In [http://www.xfytec.com/community/ xfy Community], there are some hCalendar implementations. "hCalendar via RSS" parses an RSS feed, retrieves XHTML documents linked from that feed, and syndicates hCalendars into a calendar view.
* [http://web.mit.edu/glasser/www/JSCalendar/ JSCalendar] parses hCalendar and produces a displayable HTML table/CSS-based calendar.
==== Firefox Browser Based ====
* [http://george.hotelling.net/90percent/ George] has built a [http://george.hotelling.net/90percent/geekery/greasemonkey_and_microformats.php Greasemonkey user script that detects hCalendar events and allows users to easily add them to their calendar application(s)].
* [http://blogmatrix.blogmatrix.com/ David Janes] has produced a [[Greasemonkey]] [http://www.blogmatrix.com/include/microformat-find.user.js script] that finds many microformat elements, including hCalendar events, and [http://blog.davidjanes.com/mtarchives/2005_08.html#003379 provides a popup menu of actions]. The hCalendar to vCalendar conversion is done internally within the script. ''This does not work with FireFox 1.5+/GreaseMonkey 0.6.4+.''

=== Libraries ===
; Javascript : [http://virtuelvis.com/archives/2005/11/learn-to-love-microformats simple hCalendar parser] by [http://virtuelvis.com/ Arve Bersvendsen]
; PHP : [http://randomchaos.com/microformats/base/ Microformat Base] is an open-source PHP microformat aggregation crawler, currently recognizing hreview, hcalendar, and hcard.
; Ruby : [http://opensource.reevoo.com/2006/03/08/release-uformats-12/ uformats] is a ruby library that can parse [[hCalendar]], [[hCard]], [[hReview]] and [[rel-tag]]
; XSLT :
* X2V is available as an XSLT library
* [http://dev.w3.org/cvsweb/2001/palmagent/ palmagent] by [[User:DanC]] includes toICal.xsl and test materials; it works much like xhtml2vcal.xsl in X2V. See also: [http://www.w3.org/2002/12/cal/ RDF Calendar workspace] with icalendar test materials.

=== Potential implementations ===

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]

== References ==
=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [[hcard|hCard]]
* [http://www.ietf.org/rfc/rfc2445.txt iCalendar RFC2445]

=== Informative References ===
* [http://w3.org/TR/REC-CSS1 CSS1]
* [http://tantek.com/log/2004/09.html#hcalendar hCalendar term introduced and defined on the Web, 20040930]
* [http://wiki.oreillynet.com/foocamp04/index.cgi?HTMLForCalendars FOO Camp 2004 HTML For Calendars presentation, 20040911]
* [http://wiki.oreillynet.com/foocamp04/index.cgi?SimpleSemanticFormats FOO Camp 2004 Simple Semantic Formats presentation, 20040910]
* [http://www.ietf.org/internet-drafts/draft-royer-ical-basic-04.txt iCal-Basic draft 04]
* Contributed from http://developers.technorati.com/wiki/hCalendar
* [http://www.w3.org/TR/xhtml11 XHTML 1.1]

==== Related ====
* [[icalendar-implementations|iCalendar implementations]]
* [[hcalendar-tests]]
* [http://lists.osafoundation.org/pipermail/ietf-calsify/ IETF-calsify archives]
* [http://www.livejournal.com/users/jwz/444651.html jwz - Hula] (required reading)
* [http://www.jwz.org/doc/groupware.html Groupware Bad by Jamie Zawinski] crystalizes the reason for hCalendar ('''emphasis''' added):
<blockquote>"Right now people can do that by publishing .ics files, but it's not trivial to do so, and it's work on the part of other people to look at them. '''If it's not HTML hanging off our friend's home page that can be viewed in any browser on a public terminal in a library, the bar to entry is too high and it's useless.'''"</blockquote>

* [http://muddybranch.thejkgroup.com/ Jason Klemow's blog]
* [http://www.softwarestudio.org/iCal/2445Issues.html RFC2445 Issues List]
* [http://ietf.webdav.org/calsify/ CALSIFY WG Links And Resources]

=== Similar Work ===
* [[XOXO]]

== Discussions ==

This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. There is a separate document where we are keeping our brainstorms and other explorations relating to hCalendar:

* [[hcalendar-brainstorming]]

* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].
** [http://weblog.infoworld.com/udell/2006/01/11.html#a1368 Moving forward with microformats] by [http://weblog.infoworld.com/udell Jon Udell] provides an hCalendar example and some discussion.

=== Q&A ===
* If you have any questions about hCalendar, check the [[hcalendar-faq]], and if you don't find answers, add your questions!

=== Issues ===
* Please add any issues with the specification to the separate [[hcalendar-issues]] document.

irc

2006-04-21T17:18:47Z

DanC: declare myself a regular

__NOTOC__
= Microformats IRC =

We have an IRC channel, [irc://irc.freenode.net#microformats #microformats on the freenode network].

There's typically someone there at any point during the day, though there isn't always active discussion. Sometimes, though this is the best place to discuss issues that need lots of back and forth discussion.

== People on irc ==
A list of IRC regulars and their normal timezones. (winter/summer)

* [[User:Amette|amette]] (+1000)
* [[User:B.K._DeLong|bkdelong]] (-0500/-0400)
* [[User:Ben Ward|BenWard]] (+0000)
* [[User:BenjaminCarlyle|BenjaminCarlyle]] (+1000)
* [[User:Boneill|boneill]] (+0000)
* [[User:Brian|briansuda]] (-0600/-0500)
* [[User:ColinDDevroe|cdevroe]] (-0500/-0600)
* [[User:Cgriego|cgriego]] (-0600/-0500)
* [[User:ChrisCasciano|pnhChris]] (-0500/-0400)
* [[User:ChrisMessina|factoryjoe]] (-0800/-0700)
* [[User:ChristopherStJohn|cks]] (-0600/-0500)
* [[User:DanC|DanC]] (-0600/-0500)
** office hours: Wednesday afternoons, America/Chicago time
* [[User:Dave Cardwell|davecardwell]] (+0000)
* [[User:DimitriGlazkov|dglazkov]] (-0600/-0500)
* [[User:EdwardOConnor|hober]] (-0800/-0700)
* [[User:Enric|enric]] (-0800/-0700)
* [[User:Evan|evanpro]] (-0500)
* [[User:Fil|Fil]] (+0200)
* [[User:Hlb|hlb]] (+0800-0700)
* [[User:IanHickson|Hixie]] (-0800/-0700)
* [[User:Izo|IZO]]
* [[User:JoeGregorio|jcgregorio]]
* [[User:Jonathan_Arkell|jonnay]] (-0700/0600)
* [[User:Keri Henare|kerihenare]] (+1200)
* [http://epeus.blogspot.com/ KevinMarks] (-0800/-0700)
* [[User:Mark Mansour|Mark Mansour]] (+1100)
* [[User:neuro|neuro`]]
* [[User:RobertBachmann|RobertBachmann]] (+0100/+0200)
** Office hours: Wednesday, 20:30-21:30 UTC
* [[User:RyanKing|kingryan]] (-0800/-0700)
** [http://theryanking.com/blog/archives/2006/04/19/office-hours/ Office hours]: Wednesday, 21:00 UTC
* [[User:Dana Benson|Snowden]] (-0800/-0700)
* [[User:Steve Ganz|SteveGanz]] (-0800/-0700)
* [[User:Tantek|Tantek]] (-0800/-0700)

=== bots ===

* [[mfbot]]
* [[mflogbot]]
* [http://joi.ito.com/joiwiki/JiBot jibot]

== Logs ==

Available here: http://rbach.priv.at/Microformats-IRC/

== IRC meetups ==

The idea of having IRC meetups (that is, a set time for meeting on IRC) has been suggested by [[User:RyanKing|Ryan King]], as it appears to work well for the WordPress community and may help us from time-to-time. As of yet, there are no plans to have meetups, though.

hcalendar-issues

2006-04-12T22:26:03Z

DanC: profile uris migrating from tantek's todo list

= hCalendar Issues =

These are externally raised issues about [[hcalendar|hCalendar]] with broadly varying degrees of merit. Thus some issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the spec. Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — [http://tantek.com/log/ Tantek]

See related [[hcard-issues]].

== Issues ==

Please use this format:
* YYYY-MM-DD raised by AUTHORNAME
*# ''Issue 1: Here is the first issue I have.''
*# ''Issue 2: Here is the second issue I have.''

And add new issues to the top of the list:

* 2006-03-07 raised by [[User:Ragdoll|Justin McDowell]]
*# ''Issue 1: I'd love to see a Property List, similar to what is seen in the hCard spec, that lists all the available properties and sub-properties in a nice, compact list. This saves a lot of time and is really useful for quickly and easily getting aquainted with the possibilities of vCalendar.''

* 2006-02-17 raised by [[User:Mark Mansour|Mark Mansour]] - notes are summarized [[hcalendar-irc-meetup-20060225|here]]
*# Should vcalendar be a class? Section 4.4 of RFC2445 says: "The Calendaring and Scheduling Core Object is a collection of calendaring and scheduling information. Typically, this information will consist of a single iCalendar object. However, multiple iCalendar objects can be sequentially grouped together." Also the vcalendar class would allow properties on the calendar itself such as METHOD and CALSCALE (I don't think VERSION and PRODID are particularly relevant).
*#* ACCEPTED SPECUPDATE/FAQ. Is this a case of fixing something that isn't broken? Note that "iCalendar object" != "vcalendar". This is a bit confusing so read RFC 2445 carefully in that regard. In addition, the [[hcalendar|hCalendar]] spec should say *precisely* how to generate VCALENDAR properties in their absence.
*# How are axis and headers going to be handled?
*#* ACCEPTED. This is documented in [[hcalendar-brainstorming]] but MUST be moved to [[hcalendar|hCalendar]] proper as the editors and implementers have all agreed on it (months ago). Add this as a [[to-do]] for Tantek.
*# There has been talk that table axis and headers should be used to capture calendar information in a more compact format, but no example are available. Does anyone have examples or should we try to invent some?
*#* REJECTED. Please RTFM. Searching the [[hcalendar|hCalendar]] spec for *either* "axis" or "headers" would have found the following example in the wild: [http://we05.com/ Web Essentials 05] has marked up their [http://we05.com/program.cfm program schedule table with hCalendar], using the 'axis' and 'headers' attributes.
*# Should embeded components be allowed? [[RyanKing]] has already noted that vJournal overlaps blog-posts (although not yet accepted), but should the components to-do, free/busy, timezone, alarms be allowed? They all considered as just as relevant by the ical spec as events are (my interpretation).
*#* ACCEPTED SPECUPDATE/FAQ. Another [[to-do]] for Tantek. Explicitly specify which additional iCalendar objects (in addition to VEVENT) are permitted in hCalendar. Current additional candidates: VTODO (many examples of this info on the web), VFREEBUSY (already at least one site publishing this info), VALARM (maybe, seems harmless enough, but without a compelling real world use case we should probably omit it). Currently dropping: VTIMEZONE (terrible construct), VJOURNAL (obsoleted by [[hatom|hAtom]]).
*# Validation of the hCalendar tests. The hCalendar tests have been available for a while now, but only Brian Suda and I have made contributions to their content. Does anyone else have thoughts and should we try to make these the beginning of 'official' hCalendar tests?
*#* ACCEPT PARTIAL. We probably need an hCalendar ''validator'' before we can declare any set of tests to be official.
*# The use of fragments is unclear. Fragment interpretation seems to be agent dependant. Fragments usually denote a heading or marker, like a goto statement for HTML. Unfortunately it may jump in the middle of elements (rather to the beginning of an element). How should this be handled. i.e.
<pre>
<a name="myfrag">heading</a>
<div class="vevent">
<div class="description">A nice event</div>
<abbr class="dtstart" title="2005-10-05">October 5</abbr>
</div>
</pre>
*#* ACCEPTED. We should clarify to converters how to interpret a fragement id. The interpretations are all consistent. It points to the element that is to be converted. If that element is empty then so is the conversion. There is no issue here other than a need for more documentation.
* 2006-02-01 raised by [[RyanKing]]
*# ''Issue 1: Given that now, or soon will have hAtom, should we disallow vJournal, so that we don't have 2 blog-post formats?''
*#* ACCEPTED. Yes, we should expliclty DROP "vjournal" from [[hcalendar|hCalendar]].
* 2006-01-04 raised by [[User:CGranade|CGranade]]
*# ''Interactions with strong namespacing. So far, it seems that hCalendar cannot be embedded into non-XHTML schemas that are also strongly namespaced (e.g.: RDF, Atom) without a resultant validation error, as the <code>class</code> attribute is ''not'' portable across schemas.''
*#* REJECTED. The class attribute is used on XHTML elements, which are XML, which can be embedded in any other XML. The issue as raised doesn't make sense.
*# ''All examples in XHTML. XHTML should not be the only host to microformats, and thus it should not be the only example host language. Rather, examples in Atom, RSS, RDF, etc. should also be provided.''
*#* ACCEPTED. This is definitely something to be added to *-examples pages for each microformat.
* 2005-10-14 raised by [[User:MarkoMrdjenovic|MarkoMrdjenovic]]
*# ''UID has to be present in iCal events if they want to be used in Microsoft Outlook. [Suggestion:] it should probably be added to the vevent tag as html attribute id. There is also the problem of converters - x2v has UID commented out. [http://www.ietf.org/rfc/rfc2445.txt RFC] recommends use of addr format for uids which is problematic in html id (does not validate). [[User:HenriBergius|HenriBergius]] pointed out some calendaring software crashes when @ is in the UID, so some other form of identification should be used - along the lines of dtstart-dtend-hash(title,summary)-sample-org''
*#* ACCEPTED-PARTIAL. Yes, it appears RFC2445 requires UID. However, typical mentions of events by web authors do not provide anything equivalent to a UID, nor should we require authors to do so. Thus we must come up with an algorithm for implied UID, similar to some of the other properties. We REJECT the use of the html 'id' attributre as a substitute for UID as they are of different scopes and thus such a translation will likely be problematic. As part of this algorithm, we MUST disallow "@" signs since the issue points out that such UIDs crash some calendaring software.
*# ''DTSTAMP also has to be present in iCal event for Microsoft Outlook. I think DTSTAMP should be user visible information so implementation with class="dtstamp" is fine. x2v already supports it so it should just be added to the standard and examples. The converters might also think of a way to force (create) dtstamp if it's not present.''
*#* ACCEPTED. We should come up with a way to encourage/synthesize/imply DTSTAMP property values.
*# ''Here is an example from Midgard CMS (which will be easy to change according to bergie on irc):''
*#* For more discussion of this, please see [http://microformats.org/wiki/hcalendar-brainstorming#UID_handling hCalendar brainstorming: UID handling]
<pre><nowiki>
<li class="vevent" id="2678c3f94af4a49f9ccbb69b92a82aba-midgardGuid">
<abbr class="dtstart" title="2005-10-20T14:34:45Z">Torstai 20. Lokakuu 17:34</abbr> -
<abbr class="dtend" title="2005-10-20T15:33:56Z">18:33</abbr>
<a class="url" href="/bergie/another-calendar/82457028ba83407451edd8aaeaa40622.html">
<span class="summary">From the other cal</span>
</a>
<abbr class="dtstamp" title="2005-10-14T12:16:45Z">Torstai 14. Lokakuu 12:16</abbr>
</li></nowiki></pre>
* 2005-09-29 raised by RyanKing
*# ''How does one use ATTENDEE?''
*#* ACCEPTED. Another [[to-do]] for Tantek - document how to use ATTENDEE with [[hcard|hCard]].
* 2005-07-27 raised by Paolo Massa
*# ''I tried to add a hcalendar event in my blog but it rendered orribly. The problem was I already have a 'class="summary' in my normal HTML (it is the title of the posts) and my CSS displays it bigger and bold. In this way the summary of the event was as big as the titles of the posts, destroying readability. The problem is Overloading of class attributes, it might be the case that a blogger already use, for example, class="summary" for different purposes. What can be a solution? Providing in every microformat wiki page a CSS file that users can download and insert in their blog as additional CSS. This CSS file will "shield" attribute "inside" microformats from being interpreted as "normal" attributes. For example for the hCalendar microformats the relative CSS could be something like:

.vevent .summary {

//remove all the previously set properties, for example:

text-decoration: none;

font-size: 100%;

...

}

Since the hCalendar microformat is the following,

<span class="vevent">

<a class="url" href="http://www.web2con.com/">

<span class="summary">Web 2.0 Conference</span>:

...

I hope to have been clear but I'm not so sure ;-)''

* 2005-07-21 raised by Neil Jensen
*# ''should we create a vfreebusy class for HTML representations of freebusy data? Discussion [http://microformats.org/wiki/hcalendar-brainstorming#Free.2FBusy_information on hCalendar brainstorming]. Additional background: [http://www.ifreebusy.com/cyclical/blog/calendar/3.html here].''

* 2005-07-11 raised by Kragen
*# ''The specification of class="url" as <a href="..."> should be a "should", not a "must". Other ways of referencing the event URL, such as <iframe src="..."> and <embed src="...">, shoul be mentioned. At present X2V doesn't appear to handle them. This came up in a discussion about [[xfolk|xFolk]].''
*#* REJECTED. Lack of use case. We should not add additional "ways of referencing the event URL" unless you can show a concrete real world example on the Web which requires it.

* 2005-06-21 raised by Hixie
*# ''Issue H-1: This specification is lacking a user agent conformance section. There's basically nothing that says how hCalendars must be parsed, how to handle errors, and so forth. Is it defined in terms of the DOM? Is it defined in terms of a serialisation? How do you handle unexpected content or missing content?
*#* ACCEPTED. Another [[to-do]] for Tantek, write-up [[hcalendar-parsing]] that documents precisely how user agents are to parse [[hcalendar|hCalendar]] markup.
* 2005-02-22 raised by Matt Raymond [http://listserver.dreamhost.com/pipermail/whatwg-whatwg.org/2005-February/003124.html on the whatwg list]:
*# ''There is no copyright statement and no patent statement.''
*#* ACCEPTED. I have updated [[hcalendar]] (and [[hcard]], and all other MicroFormats) with a standard copyright statement and patent statement.

* 2005-02-18 raised by Matt Raymond [http://listserver.dreamhost.com/pipermail/whatwg-whatwg.org/2005-February/003116.html on the whatwg list]:
*# ''There is no way for some reading the markup to tell if a class name is the name of an attribute or simply the name of a class used for styling.''
*#* REJECTED (strawman, poor assumption). There is no need to differentiate in the general case. In the specific case, a vocabulary is defined within a context.
*# ''As a result of the above, user agents would not be able to reliably allow users to access extension properties such as "x-mozilla-alarm-default-length" (which is an actual extension used in Sunbird).''
*#* REJECTED (out of scope). Extension properties are outside the current scope of hCalendar.
*# ''The use of <abbr> for dates is incorrect. "August 5th, 2004" is not the abbreviation of 2004-09-05. In fact, the opposite is closer to the truth.''
*#* REJECTED (false statement). This is simply a false statement. See this article for an explanation of this use of <abbr>: [http://tantek.com/log/2005/01.html#d26t0100 Human vs. ISO8601 dates problem solved]
*# ''You have to create a complex set of rules for all possible uses of legacy markup within <span class="vcalendar"> which can easily be implemented incorrectly.''
*#* REJECTED (false statements, strawman). There is no legacy markup. There is no need to create rules for all possible uses of legacy markup. There is no need to create a complex set of rules.
*# ''There are styling and tooltip issues that are unresolved.''
*#* REJECTED (empty statements). See the [[hcalendar-faq|hCalendar FAQ]] for answers to specific styling and tooltip questions. Otherwise, please raise specific issues here with clear valid examples.
*# ''hCalendar/hCard is more complicated for webmasters to read and understand and more complicated for developers to implement.''
*#* REJECTED (empty statements, invalid comparator). Please state specific examples which show the perceived complexity. The comparison "more complicated" requires two items, no second item was provided.
*# ''I dislike the entire system of using class names as markup. Class names should be reserved for user-defined semantics.''
*#* ACCEPT-PARTIAL. When specific elements are available, they should be used instead of class names, but even then class names work well to "subclass" specific elements. This is thoroughly discussed in the essay [http://tantek.com/log/2002/12.html#L20021216 A Touch of Class]. And yes, class names can and should be used for user-defined semantics. [[hcalendar|hCalendar]] is one such user, and it is reasonable for users to use each others class names.
*#* ''Would it be more in the spirit of HTML to define these classes in a [http://www.w3.org/TR/html401/struct/global.html#h-7.4.4.3 metadata profile], so that "User agents may... perform some activity based on known conventions for that profile"? Should this be a part of [[microformats]] specifications in general? (If not, why not?)''
*#** ACCEPTED. Yes, all [[microformats]] that introduce new classnames SHOULD include an [http://gmpg.org/xmdp/ XMDP] profile (which itself is a microformat for defining HTML metadata profiles) that defines those classnames.
*#*** ''Ok, but in order to refer to a profile, it needs a URI. Tantek writes in [http://microformats.org/discuss/mail/microformats-discuss/2005-July/000407.html a message of Jul 21] "This is precisely the reason that GMPG was founded and created, to provide permanent URLs/homes for microformat profiles." How does one cause GMPG to issue a profile URL?''
*#**** ACCEPTED. See [[profile-uris]]; this is moving from Tantek's [[to-do]] list, to both provide profiles and URLs (probably at gmpg.org) for those profiles for hCalendar etc.
* 2006-04-10 raised by [[User:ScottReynen|Scott Reynen]].
*# ''When someone looks at the [[hcalendar]] pages, one sees no collection of real-world publishing of event data nor discussion of the properties implied by such examples, I think it's far too easy to infer that microformats come from other formats more than actual behavior. There's nothing on the [[process]] nor the hcalendar pages explaining this discrepancy. I would argue that there should be an explanation, probably in both places.''

hcard-profile

2006-04-12T22:25:33Z

DanC: note profile at w3.org

= hCard Profile =

The following is an [http://gmpg.org/xmdp/ XMDP] profile for the [[hcard|hCard]] specification.

It's also available as [http://www.w3.org/2006/03/hcard http://www.w3.org/2006/03/hcard]; see [[profile-uris]] for more details.

== Profile ==
<pre>
<dl class="profile">
<dt>class</dt>
<dd><p>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
All values are defined according to the semantics defined in the
<a href="http://microformats.org/wiki/hcard">
hCard specification</a>
and thus in
<a href="http://www.ietf.org/rfc/rfc2426.txt">RFC 2426</a>.</p>
<dl>
<dt>vcard</dt>
<dd>A container for the rest of the class names defined in this XMDP profile.
See section 1. of RFC 2426.
</dd>

<dt>fn</dt>
<dd>See section 3.1.1 of RFC 2426.</dd>

<dt>n</dt>
<dd>See section 3.1.2 of RFC 2426. May be inferred per
Implied "N" Optimization.</dd>

<dt>family-name</dt>
<dd>See "Family Name" in section 3.1.2 of RFC 2426.</dd>

<dt>given-name</dt>
<dd>See "Given Name" in section 3.1.2 of RFC 2426.</dd>

<dt>additional-name</dt>
<dd>See "Additional Names" in section 3.1.2 of RFC 2426.</dd>

<dt>honorific-prefix</dt>
<dd>See "Honorific Prefixes" in section 3.1.2 of RFC 2426.</dd>

<dt>honorific-suffix</dt>
<dd>See "Honorific Suffixes" in section 3.1.2 of RFC 2426.</dd>

<dt>nickname</dt>
<dd>See section 3.1.3 of RFC 2426.</dd>

<dt>photo</dt>
<dd>See section 3.1.4 of RFC 2426. Typically used with an <img> tag.
Use the 'src' attribute for URI values. Use the 'data:' URI scheme for
binary values.</dd>

<dt>bday</dt>
<dd>See section 3.1.5 of RFC 2426. Typically used with an <abbr> tag
with the 'title' attribute for the date value, and a human readable date
inside the element.</dd>

<dt>adr</dt>
<dd>See section 3.2.1 of RFC 2426.</dd>

<dt>post-office-box</dt>
<dd>See "post office box" in section 3.2.1 of RFC 2426.</dd>

<dt>extended-address</dt>
<dd>See "extended address" in section 3.2.1 of RFC 2426.</dd>

<dt>street-address</dt>
<dd>See "street address" in section 3.2.1 of RFC 2426.</dd>

<dt>locality</dt>
<dd>See "locality" in section 3.2.1 of RFC 2426.</dd>

<dt>region</dt>
<dd>See "region" in section 3.2.1 of RFC 2426.</dd>

<dt>postal-code</dt>
<dd>See "postal code" in section 3.2.1 of RFC 2426.</dd>

<dt>country-name</dt>
<dd>See "country name" in section 3.2.1 of RFC 2426.</dd>

<dt>type</dt>
<dd>See "type" in the various sections of RFC 2426.</dd>

<dt>value</dt>
<dd>This class name is used to distinguish the actual *value*
of a property from any other cruft that may be in
the element representing the property.</dd>

<dt>label</dt>
<dd>See section 3.2.2 of RFC 2426.</dd>

<dt>tel</dt>
<dd>See section 3.3.1 of RFC 2426.</dd>

<dt>email</dt>
<dd>See section 3.3.2 of RFC 2426.</dd>

<dt>mailer</dt>
<dd>See section 3.3.3 of RFC 2426.</dd>

<dt>tz</dt>
<dd>See section 3.4.1 of RFC 2426. Typically used with an <abbr> tag
with the 'title' attribute for the tz value, and a human readable time zone
inside the element.</dd>

<dt>geo</dt>
<dd>See section 3.4.2 of RFC 2426.</dd>

<dt>latitude</dt>
<dd>See "latitude" in section 3.4.2 of RFC 2426.</dd>

<dt>longitude</dt>
<dd>See "longitude" in section 3.4.2 of RFC 2426.</dd>

<dt>title</dt>
<dd>See section 3.5.1 of RFC 2426.</dd>

<dt>role</dt>
<dd>See section 3.5.2 of RFC 2426.</dd>

<dt>logo</dt>
<dd>See section 3.5.3 of RFC 2426. Typically used with an <img> tag.
Use the 'src' attribute for URI values. Use the 'data:' URI scheme for
binary values.</dd>

<dt>agent</dt>
<dd>See section 3.5.4 of RFC 2426. If the value is a vCard, then
use a nest hCard. For simplicity in that case, the same element that
has the class name of "agent" should use the class name of "vcard".</dd>

<dt>org</dt>
<dd>See section 3.5.5 of RFC 2426.</dd>

<dt>organization-name</dt>
<dd>See "Organization Name" in section 3.5.5 of RFC 2426.
May be inferred per Implied "organization-name" Optimization.</dd>

<dt>organization-unit</dt>
<dd>See "Organization Unit" in section 3.5.5 of RFC 2426.</dd>

<dt>category</dt>
<dd>See section 3.6.1 of RFC 2426.</dd>

<dt>note</dt>
<dd>See section 3.6.2 of RFC 2426.</dd>

<dt>rev</dt>
<dd>See section 3.6.4 of RFC 2426. Typically used with an <abbr> tag
with the 'title' attribute for the date value, and a human readable date
inside the element.</dd>

<dt>sort-string</dt>
<dd>See section 3.6.5 of RFC 2426.</dd>

<dt>sound</dt>
<dd>See section 3.6.6 of RFC 2426. Typically used with either an <a>
or <object> tag. Use the 'data:' URI scheme for binary values.</dd>

<dt>uid</dt>
<dd>See section 3.6.7 of RFC 2426.</dd>

<dt>url</dt>
<dd>See section 3.6.8 of RFC 2426. Typically used with an <a> tag.
</dd>

<dt>class</dt>
<dd>See section 3.7.1 of RFC 2426.</dd>

<dt>key</dt>
<dd>See section 3.7.2 of RFC 2426. Typically used with an <abbr> tag
with the 'title' attribute for the key value, and a human readable key
equivalent inside the element.</dd>

</dl>
</dd>
</dl>
</pre>

== Deprecated ==

2005-09-16:

The following class names have been deprecated in favor of singular names and the use of the "type" sub-property rather than class names for all of its values. hCard publishers MUST NOT use them as a class name.
* plurals:
** additional-names, honorific-prefixes, honorific-suffixes, categories
* type values:
** dom, intl, postal, parcel, home, work, pref, msg, voice, fax, cell, video, pager, bbs, modem, car, isdn, pcs, internet, x400

profile-uris

2006-04-12T22:24:48Z

DanC: more on versioning

In [[hcalendar-issues]], it is ACCEPTED that each microformat should have a profile URI, like [[http://gmpg.org/xfn/11 the XFN profile]].

Some issues include:

* what domain to use? Candidates include:
** microformats.org
** www.w3.org
** xmdp.org
* what about versioning? how to keep in sync with the wiki and test materials?

* what profile URI to use for combinations, such as [[hcard]] and [[hcalendar]]?

One proposal is: use www.w3.org, following [http://www.w3.org/1999/10/nsuri W3C namespace policy]. As to versioning, change the profile whenever the wiki changes (within some reasonable latency, say, a couple weeks or a month). For example: [http://www.w3.org/2006/03/hcard an hCard Profile at w3.org], and discussion: [http://microformats.org/discuss/mail/microformats-dev/2006-March/000068.html an hCard profile that seems to work with GRDDL].

See also: [[faqs-for-rdf]] for discussion of connecting microformats to URIs.

And see also: [[hcard-profile]].

profile-uris

2006-04-12T22:21:01Z

DanC:

profile-uris

2006-04-12T22:20:04Z

DanC: based on SWSWi discussions

User:DanC

2006-03-26T07:28:26Z

DanC: linked microformats category in my blog

My [http://microformats.org/discuss/mail/microformats-dev/2005-July/000010.html hcardTest materials, XHTML version of RFC2426, and fun with microformats] message is sort of my introduction to this community. I have since discovered the "personal intro" ritual in [http://microformats.org/discuss/mail/microformats-discuss/ microformats-discuss] and I may join that soonish.

Meanwhile, I'm working on [[hcard-test]] and [[hcard-issues]] and such.

I have written about 6 [http://dig.csail.mit.edu/breadcrumbs/taxonomy/term/26 blog posts tagged microformats] so far.

Ugh... yet another username/password out there. Oh for [http://www.openid.net/ OpenID]!

hcard

2006-03-08T05:02:54Z

DanC: a bunch of hotel hCards on my event history page

<h1>hCard</h1>

hCard is a simple, open, distributed contact information format for people, companies, and organizations, which is suitable for embedding in (X)HTML, Atom, RSS, and arbitrary XML. hCard is a 1:1 representation of the vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]) in XHTML, one of several open [[microformats|microformat]] standards.

Want to get started with writing an [[hcard|hCard]]? Use the [http://microformats.org/code/hcard/creator hCard creator] to write up some contact information and publish it.

__TOC__

== Draft Specification ==

=== Editor ===
[http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc.]

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

=== Copyright ===
{{MicroFormatCopyrightStatement2004}}

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

=== Inspiration and Acknowledgments ===
Thanks to: my good friend [http://vadim.com/ Vadim] who introduced me to vCard ''many'' years ago, and if I'd only paid more attention then, perhaps I could have helped a lot of people avoid wasting a lot of time reinventing various standards wheels.

== Introduction ==
The vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]), has been broadly interoperably implemented (e.g. Apple's "Address Book" application built into MacOSX).

In addition, many bloggers identify themselves by name and discuss their friends and family. With just a tad bit of structure, bloggers can discuss people in their blog(s) in such a way that spiders and other aggregators can retrieve this information, automatically convert them to vCards, and use them in any vCard application or service.

This specification introduces the '''hCard''' format, which is a 1:1 representation of the aforementioned vCard standard, in semantic XHTML. Bloggers can both embed vCards directly in their web pages, and style them with CSS to make them appear as desired. In addition, hCard enables applications to retrieve information about such vCards directly from web pages without having to reference a separate file.

Use the [http://microformats.org/code/hcard/creator hCard creator], copy the HTML code it generates to your blog or website to publish your contact info.

== Semantic XHTML Design Principles ==
{{semantic-xhtml-design-principles}}

== Format ==
=== In General ===
The vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]) forms the basis of hCard.

The basic format of hCard is to use vCard object/property names in lower-case for class names, and to map the nesting of vCard objects directly into nested XHTML elements.

=== More Semantic Equivalents ===
However, for some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:
* <code>URL</code> in vCard becomes <code><a class="url" href="...">...</a></code> inside the element with <code>class="vcard"</code> in hCard.
* Similarly, <code>EMAIL</code> in vCard becomes <code><nowiki><a class="email" href="mailto:...">...</a></nowiki></code>
* <code>PHOTO</code> in vCard becomes <code><img class="photo" src="..." alt="Photo of ..." /></code>

=== Singular vs. Multivalued Properties ===

For properties which are singular (e.g. "N" and "FN"), the first descendant element with that class should take effect, any others being ignored.

For properties which can be plural (e.g. "TEL"), each class instance should create a instance of that property.

==== Plural Properties Singularized ====

Since plural property names become their singular equivalents, even if the original plural property permitted only a single value with multiple components, those multiple components are represented each with their own singularly named property and the the property is effectively multivalued and subject to the above treatment of multivalued properties.

=== Human vs. Machine readable ===

If an <code><abbr></code> element is used for a property, then the '<code>title</code>' attribute of the <code><abbr></code> element is the value of the property, instead of the contents of the element, which instead provide a human presentable version of the value.

Similarly, if an <code><img></code> element is used for one or more properties, it must be treated as follows:
# For the "PHOTO" property and any other property that takes a URL as its value, the <code>src="..."</code> attribute provides the property value.
# For other properties, the <code><img></code> element's '<code>alt</code>' attribute is the value of the property.

=== Value excerpting ===

Sometimes only part of an element which is the equivalent for a property should be used for the value of the property. This typically occurs when a property has a subtype, like TEL. For this purpose, the special class name "<code>value</code>" is introduced to excerpt out the subset of the element that is the value of the property. E.g. here is an hCard fragment for marking up a home phone number:

<pre><nowiki>
<span class="tel">
<span class="type">home</span>:
<span class="value">+1.415.555.1212</span>
</span>
</nowiki></pre>

This hCard fragment could be displayed as:

home: +1.415.555.1212

=== Property Exceptions ===

vCard has several properties which either do not make sense on, or are already implied within the context of a web page. This section explains what to (not) do with them.

# '''NAME''', '''PROFILE''', '''SOURCE''', '''PRODID''', '''VERSION''' properties as defined in Sections 2.1.2, 2.1.3, 2.1.4, 3.6.3, 3.6.9 of RFC 2426. Content publishers MUST NOT use these properties in their hCards, and as such, hCard consumers/parsers MUST IGNORE these properties if they are found within an hCard. Instead. hCard to vCard converters SHOULD use the title of the page where the hCard is found (e.g. the <code><title></code> element in (X)HTML documents) to construct the NAME property, MAY output a PROFILE value of "<code>VCARD</code>" per RFC 2426, SHOULD use the URL of the page where the hCard is found to construct the SOURCE property (e.g. perhaps as a parameter to a URL/service that converts hCards to vCards), for an output vCard stream (e.g. a .vcf file). Only services/applications that output actual vCards should write the PRODID property, with the product identifier for said service/application. Similarly only such services/applications should write the VERSION property, with the value "3.0" (without quotes) per RFC2426 Section 3.6.9.

=== Organization Contact Info ===

If the "FN" and "ORG" properties have the exact same value (typically because they are set on the same element, e.g. class="fn org"), then the hCard represents contact information for a company or organization and should be treated as such. In this case the author MUST also NOT set the "N" property, or set it (and any sub-properties) explicitly to the empty string "". Thus parsers should handle the missing "N" property in this case by implying empty values for all the "N" sub-properties.

=== Implied "n" Optimization ===

Although vCard requires that the "N" property be present, the authors of the vCard specification (RFC 2426) themselves do not include "N" properties in their vCards near the end of the spec (p.38). This apparent contradiction can be resolved by simply allowing the "FN" property to imply "N" property values in typical cases provided in the spec. We do so explicitly in hCard.

If "FN" and "ORG" are not the same (see previous section), and the value of the "FN" property is exactly two words (separated by whitespace), and there is no explicit "N" property, then the "N" property is inferred from the "FN" property. For "FN"s with either one word see below, and for three or more, the author MUST explicitly markup the "N", except for the organization contact info case, [http://microformats.org/wiki/hcard#Organization_Contact_Info see above] for that.

# The content of "FN" is broken into two "words" separated by whitespace.
# The ''first'' word of the "FN" is interpreted as the "given-name" for the "N" property.
# The ''second/last'' word of the "FN" is interpreted as the "family-name" for the "N" property.
# Exception: If the first word ends in a "," comma OR if the second word is a single character (optionally followed by a period "."), then the first word (minus the comma at the end if any) is interpreted as the "family-name" and the second word is interpreted as the "given-name".

This allows simplification in the typical case of people stating:
* given-name (space) family-name
* family-name (comma) given-name
* family-name (comma) given-name-first-initial
* family-name (space) given-name-first-initial (optional period)

=== Implied "nickname" Optimization ===

Due to the prevalence of the use of nicknames/handles/usernames on the Web in actual content published on the Web (e.g. authors of [[hReview|reviews]]), hCard also has an implied "nickname" optimization to handle this.

Similar to the implied "n" optimization, if "FN" and "ORG" are not the same, and the value of the "FN" property is exactly one word, and there is no explicit "N" property, 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.

Note: the hCard may have additional explicit "nickname" property values in addition to the implied nickname.

=== Implied "organization-name" Optimization ===

The "ORG" property has two subproperties, organization-name and organization-unit. Very often authors only publish the organization-name. Thus if an "ORG" property has no "organization-name" inside it, then its entire contents MUST be treated as the "organization-name".

=== Root Class Name ===

The root class name for an hCard is "vcard".

=== Property List ===

This is the list of properties (and subproperties, in parantheses, like this) in hCard, taken from vCard:

* fn, n (family-name, given-name, additional-name, honorific-prefix, honorific-suffix), nickname, sort-string
* url, email (type, value), tel (type, value)
* adr (post-office-box, extended-address, street-address, locality, region, postal-code, country-name, type, value), label
* geo (latitude, longitude), tz
* photo, logo, sound, bday
* title, role, org (organization-name, organization-unit)
* category, note
* class, key, mailer, uid, rev
==== type subproperty values ====

The 'type' subproperty in particular takes different values depending on which property it is a subproperty of. These 'type' subproperty values are case-INSENSITIVE, meaning "Home" is the same as "home", as well as multivalued, e.g. a tel can be home and preferred:
<pre><nowiki>
<span class="tel"><span class="type">Home</span> (<span class="type">pref</span>erred):
<span class="value">+1.415.555.1212</span>
</span>
</nowiki></pre>

The following lists are ''informative''. See RFC2426 sections 3.2.1 ADR, 3.3.1 TEL, and 3.3.2 EMAIL respectively for normative type values. They are repeated here for convenience. Default type subproperty value(s) is(are) first in each list and indicated in ALL CAPS. types may be multivalued.

* adr type: INTL, POSTAL, PARCEL, WORK, dom, home, pref
* tel type: VOICE, home, msg, work, pref, fax, cell, video, pager, bbs, modem, car, isdn, pcs
* email type: INTERNET, x400, pref, "other IANA registered address types"

=== XMDP Profile ===

See [[hcard-profile]] for the [http://gmpg.org/xmdp XMDP] profile of hCard which contains the above complete list of properties, with references to their RFC 2426 definitions.

=== Parsing Details ===

See [[hcard-parsing|hCard parsing]].

== Examples ==

This section is informative.

=== Sample vCard ===

Here is a sample vCard:

<pre><nowiki>
BEGIN:VCARD
VERSION:3.0
N:Çelik;Tantek
FN:Tantek Çelik
URL:http://tantek.com
ORG:Technorati
END:VCARD
</nowiki></pre>

and an equivalent in hCard with various elements optimized appropriately. See [[hcard-example1-steps| hCard Example 1]] for the derivation.

<pre><nowiki>
<div class="vcard">
<a class="url fn" href="http://tantek.com/">Tantek Çelik</a>
<div class="org">Technorati</div>
</div>
</nowiki></pre>

This hCard might be displayed as:

[http://tantek.com/ Tantek Çelik]<br />
Technorati

Note: The version information is unnecessary in hCard markup directly since the version will be defined by the profile of hCard that is used/referred to in the 'profile' attribute of the <head> element.

=== More Examples ===

See [[hcard-examples]] for more examples, including all examples from vCard RFC 2426 converted into hCard.

== Examples in the wild ==
This section is '''informative'''.

The following sites have published hCards, and thus are a great place to start for anyone looking for examples "in the wild" to try parsing, indexing, organizing etc. If you have an hCard on your own page, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.

=== New Examples ===
Please add new examples to this section.

* Ning's cloneable Group app uses fuzzy matching to map custom fields to [[hcard|hCard]] markup on its [http://group.ning.com/index.php?controller=person&action=view&content=JonathanAquino profile] pages.
* [http://claimid.com/factoryjoe Chris Messina' ClaimID hCard]
* [http://factoryjoe.com/blog/hcard Chris Messina' hCard]
* [http://flock.com/about Flock About]
* [http://tantek.com/microformats/2006/03-01-TechPlenAgenda.html Agenda: W3C Technical Plenary Day, March 1 2006] has [[hcard|hCard]] and [[hcalendar|hCalendar]] markup. ([http://www.w3.org/2006/03/01-TechPlenAgenda.html original here]).
* [http://www.gr0w.com/articles/press/growsearch_launched_press_release/ GrowSearch Launched (Press Release)] uses an hCard to provide Press Contact Point.
* The [http://www.arborday.org/ National Arbor Day Foundation] has started using hCards for their [http://arborday.org/programs/conferences/communityforestry/index.cfm upcoming] [http://arborday.org/programs/conferences/hazardtrees-treeplanting/ conferences].
* [http://www.multipack.co.uk The Multipack] has numerous hCards, especially on the [http://www.multipack.co.uk/members/ members page], as well as the next meeting information.
* [http://deadringrancor.livejournal.com/ Justin McDowell] used an hCard when [http://deadringrancor.livejournal.com/221332.html referring to a person in his blog post]
* [http://davecardwell.co.uk/cv/ Dave Cardwell] has included his hCard in his Curriculum Vitae.
* [http://blog.usweb.com/ Shaun Shull] has written a great post on [http://blog.usweb.com/archives/how-microformats-affect-search-engine-optimization-seo How Microformats Affect SEO], and has included his [[hcard|hCard]] as one of the examples.
* [http://www.thefutureoftheweb.com/ Jesse Skinner] has written a simple [http://www.thefutureoftheweb.com/blog/2006/1/hcard tutorial with examples]
* [http://www.w3.org/2005/12/allgroupoverview.html 2006 W3C Technical Plenary Week] has marked up the venue, contacts, and program committee members all with hCard.
* [http://www.avf-nexus.co.uk AVF-Nexus] have a hCard on their [http://www.avf-nexus.co.uk/contact/ contact page] - (by [http://creation.uk.com Creation"])
* [http://www.thefantasticos.com/andrew/ Andrew White] posted [http://www.thefantasticos.com/andrew/index.php/my-hcard/ his hCard] and [http://www.thefantasticos.com/andrew/index.php/62/microformats-the-should-have-been-obvious-web-dev-tool/ blogged about it].
* [http://www.2sheds.ru Oleg "2sheds" Kourapov] in his [http://www.2sheds.ru/blog/ blog] ([http://suda.co.uk/projects/X2V/get-vcard.php?uri=http://www.2sheds.ru/blog X2V]) has turned personal profile into hCard ([http://suda.co.uk/projects/X2V/get-vcard.php?uri=http://www.2sheds.ru/blog/hcard.html X2V]) and his blogroll - into combination XFN/hCards ([http://suda.co.uk/projects/X2V/get-vcard.php?uri=http://www.2sheds.ru/blog/friends.html X2V])
* [http://www.approveddesign.co.uk Approved Design Consultancy] have a hCard on their [http://www.approveddesign.co.uk/about/contact/ contact page] as well as on their [http://www.approveddesign.co.uk/about/people/ people section] - (by [http://creation.uk.com Creation"])
* [http://weblog.200ok.com.au/ Ben Buchanan] and [http://www.griffith.edu.au/cgi-bin/phone_search.pl?string=colin+morris&format=search Colin Morris] have [http://weblog.200ok.com.au/2006/01/griffith-phonebook-adds-hcard-and.html implemented hCards and vCards] for the [http://www.griffith.edu.au Griffith University] [http://www.griffith.edu.au/find/content_phonebook.html online phone book]. Eg. [http://www.griffith.edu.au/cgi-bin/phone_search.pl?string=ben+buchanan&format=search Ben's vCard] and [http://www.griffith.edu.au/cgi-bin/phone_search.pl?string=colin+morris&format=search Colin's vCard]
* WWF-Australia [http://wwf.org.au/about/contactdetails/ contact details page]
* [http://rasterweb.net/raster/ Pete Prodoehl] used the hCard format on his [http://rasterweb.net/raster/contact.html Contact page]
* [http://alexander-mette.de amette] uses the hCard format in a module of his TikiWiki powered blog

=== Examples ===
* [http://thoughtport.blogspot.com/ Aiden Kenny] hasn't published his hCard yet, but he has [http://thoughtport.blogspot.com/2005/07/elemental-particles-of-web.html published his hCard icon]: http://photos1.blogger.com/blogger/4224/444/320/AK-Hcard-icon.gif
* [http://thedredge.org Andy Hume] uses the hcard format to mark-up the names and URLs of commentors on his blog.
* [http://www.bidclix.com/ BidClix]'s [http://www.bidclix.com/AboutContact.html Contact BidClix] page has it's ''contact info'' marked up with an hCard.
* [http://suda.co.uk/ Brian Suda] has managed to embed a photo in [http://suda.co.uk/contact/ his hCard] through the [http://www.ietf.org/rfc/rfc2397.txt data uri scheme] by converting the image to BASE64 code. View the Source to see how this is accomplished. [http://suda.co.uk/projects/X2V/get-vcard.php?uri=http%3A//suda.co.uk/contact/ The X2V link] will extract the image and encode it for a vCard which will be displayed in some address book applications.
* [http://cinematreasures.org Cinema Treasures] uses hCard to markup venue information for 10,000+ movie theaters.
* [http://www.w3.org/People/Connolly/events/ Dan Connolly's index of events and talks] has hCards for many of the people he has met at those events. In Mar 2006, he moved a bunch of hotel contact info from his PDA to this page; it's now up to 32 hCards.
* [http://doncrowley.blogspot.com/ Don Crowley] has published [http://www.crowley.nl/hcard.html his hCard] as well as a nifty hCard button: http://www.crowley.nl/images/hcard.png
* [http://loadaveragezero.com/hnav/contact.php Douglas W. Clifton] added all types of contact information
* [http://evdb.com EVDB], the Events and Venues Database, publishes all venue detail pages with embedded hCards.
* [http://www.iowamilitaryveteransband.com/members/ Iowa Military Veterans Band Contacts] - 95 hCards [http://weblog.randomchaos.com/archive/2005/10/24/Microformats/ marked up by Scott Reynen]
* [http://JackWolfgang.blogspot.com Jack L. Wolfgang II] has [http://jack.randomata.com/resume/ converted the addresses in his resume to hCards].
* [http://www.efas.fupl.asso.fr/efas/_Mathieu-Drouet_.html Mathieu Drouet] and [http://www.efas.fupl.asso.fr/efas/_Annie-Leger_.html Annie Leger] both have hCards
* [http://www.ndunn.com Neil Dunn] has published his rather [http://www.ndunn.com/2005/10/7/hCard good looking hCard]
* [http://www.oliverbrown.me.uk/ Oliver Brown] has published his hCard.
* [http://www.paradigmproductions.org/contact/ Paradigm Productions] published a vcard as a ul (marked up by [http://www.linkingarts.com/ Peter Jacobson])
* [http://www.splintered.co.uk/ Patrick H. Lauke] has marked up [http://www.splintered.co.uk/about/ his contact info with hCard].
* [http://blah Paul Schreiber has published his hCard on [http://paulschreiber.com/about/?contact his about page].
* [http://paulschreiber.com/blog/ Paul Schreiber]'s [http://concerts.shrub.ca/ Sunnyvale House Concerts] site publishes hCards for upcoming artists, as well as an hCard for the page itself. In addition the [http://concerts.shrub.ca/shows Past Shows] page contains hCards for all past artists.
* [http://www.paulmichaelsmith.com/blog/hcard.htm Paul Smith] has created an hCard page which is Human Readable, and a link to X2V passing the same hCard page to generate a vCard.
* [http://www.windley.com/archives/2005/07/hcards_trying_o.shtml Phil Windley has published] [http://phil.windley.org/hcard.html his hCard].
* [http://www.go-curiosity.com/about.htm Piercarlo Slavazza] has published an hCard.
* [http://zooibaai.nl/ Rob Mientjes] has published his hCard on [http://zooibaai.nl/about/ his about page].
* [http://rbach.priv.at/Contact Robert Bachmann] has published his hCard and [http://rbach.priv.at/Images/hcard a button].
* [http://blah Scott Reynen has published his hCard on [http://www.randomchaos.com/document.php?source=scott_reynen his profile page].
* [http://www.stackframe.com/ StackFrame, LLC] has published [http://www.stackframe.com/people/ employee] and [http://www.stackframe.com/contact/ general] contact information as hCards.
* [http://www.wolfsreign.com Steven Ametjan] has published his hCard on [http://www.wolfsreign.com/about/ his about page].
* [http://tantek.com/microformats/2005/syndicate/speakers-list.html Syndicate - Speaker List] as a set of hCards
* [http://tagcamp.org/index.cgi?ContactList TagCamp contact list]
* [http://tantek.com/log Tantek's Thoughts] includes an inline author hCard at the bottom of the page.
* [http://technorati.com/ Technorati]'s [http://www.technorati.com/about/ About page] lists their '''Media Contact'''
* [http://www.deadringerart.com/ The Brothers McDowell] have hCards at their Contact page.
* [http://twinsparc.com/ Twinsparc] put an hCard in the header and footer of all their pages.
* [http://tantek.com/microformats/2005/web2/speakers.html Web 2.0 Conference speakers page marked up with hCard]
* [http://we05.com/ Web Essentials 05] marked up all their [http://we05.com/presenters.cfm presenters with hCard].

=== Examples with some problems ===
* [http://gbraad.nl/ Gerard Braad] has published an example on his [http://gbraad.nl/site/?p=profile profile] page that is almost consistent with his original [http://gbraad.nl/files/gbraad.vcf vCard] file. Also progress is made for transforming his [http://files.gbraad.nl/foaf.rdf FoaF] file to a hCard encoded representation. (also done for my spouse:[http://spouse.gbraad.nl/site/?p=profile Yong Yuan])
** (2005-09-27) PASSED, PASSED
** WARNINGS
*** uses 'n given-name' and 'n family-name' instead of nesting the given- and family- names inside the 'n'
*** has one 'tel' value with a bunch of values stuffed in
*** probably more problems --[[User:RyanKing|RyanKing]] 17:19, 5 Jan 2006 (PST)
* [http://www.kerihenare.com/ Keri Henare] has marked up his [http://www.kerihenare.com/contact/ contact info page] with hCard.
** (2005-09-27) PASSED
** (2005-11-01) hCard completely rewritten
** WARNING - type subproperty in classname
* [http://kinrowan.net/ Cori Schlegel] [http://kinrowan.net/blog/wp/archives/2005/07/08/a-problem-with-the-structured-blogging-plug-in-for-wordpress/ discusses how he has updated] [http://kinrowan.net/blog/contact his contact page with hCard]
** INVALID - using 'prefix' instead of 'honorific-prefix' and type's in classnames (in both adr and tel) and has two photo's (the second could be 'logo') --[[User:RyanKing|RyanKing]] 15:15, 5 Jan 2006 (PST)
* The good ship [http://styrheim.com/test/leonid.html Leonid Miloslavskiy] spotted in the North Atlantic
** INVALID --[[User:RyanKing|RyanKing]] 00:50, 27 Oct 2005 (PDT)
*** class="family" should probably be family-name
*** the "n" property is missing and the "n" optimization can't be applied
*** the first geo propery is empty, the second one is invalid (ie, it doesn't contain lat/long)
* [http://landsbank.fo/#hCard Landsbanki Føroya]
** INVALID - using embedded rdf/xml invalidly
* [http://chrischerry.name/blog/contact/ Chris Cherry's contact page with his hCard]
** WARNING - uses class="cell" instead of <span class="type">cell</span>
* [http://www.bath.ac.uk/contact/ University of Bath] Person Finder results are encoded with hCards so you can easily create a vCard from any result.
** ERROR - attempt to use Implied-N optimization where that's not possible. --[[User:RyanKing|RyanKing]] 14:29, 5 Jan 2006 (PST)
** Error appears for external users only. Won't be fixed any time soon. -- [[User:PhilWilson|PhilWilson]] 00:03, 28 Jan 2006 (GMT)
* [http://richi.co.uk/blog/2005/12/structured-blogging.html Richi Jennings] has put up his attempt
** INVALID, missing FN --[[User:RyanKing|RyanKing]] 12:47, 5 Jan 2006 (PST)
* [http://www.shiftingpixel.com/about/ shifting pixel photoblog] has published an hCard.
** "organization_name" should be "organization-name" (s/_/-/), otherwise good --[[User:RyanKing|RyanKing]] 14:01, 5 Jan 2006 (PST)

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

The following implementations have been developed which either generate or parse hCards. If you have an hCard implementation, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.

* [http://blog.codeeg.com/tails-firefox-extension/ Tails is a Firefox Extension] that will display the presence and details of microformats ([[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], [[xfolk|xFolk]]) on a webpage.
* [http://www.stripytshirt.co.uk/features/firefox/smartzilla Smartzilla is a Firefox Extension] that finds hCards on web pages and lets you add them to your addressbook.
* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding hCard and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].
* There is [http://flickr.com/photos/factoryjoe/68755089/ evidence of built-in hCard support in the Konqueror browser]. Specifically, Konqueror 3.5, in KDE 3.5 (kubuntu Breezy w/ update).
* There is [http://tagcamp.org/index.cgi?ContactList evidence of a kwiki plugin for hCards]. Update: the [http://svn.kwiki.org/cwest/Kwiki-hCard/ hCard kwiki plugin svn repository]. See the [http://microwiki.caseywest.com/index.cgi?hCard documentation of the hCard kwiki plugin].
* [http://suda.co.uk/projects/X2V/ X2V] is a bookmarklet that parses hCard and produces a .vcf (vCard) stream. Note: needs to be updated as the spec is refined
* [http://www.stripytshirt.co.uk Duncan Walker] has built [http://www.stripytshirt.co.uk/features/firefox/smartzilla a Firefox extension] that gets hCard data from a webpage, uses Brian Suda's XSL (locally) to transform it to vcard format and opens the resulting .vcf file.
* [http://george.hotelling.net/90percent/ George] has written a [http://george.hotelling.net/90percent/geekery/greasemonkey_and_microformats.php Greasemonkey user script] that detects hCards and allows users to easily add them to their address book application. Relies on the X2V web service to do the conversion.
* [http://blogmatrix.blogmatrix.com/ David Janes] has written a [[Greasemonkey]] [http://www.blogmatrix.com/include/microformat-find.user.js script] that finds many microformat elements, including hCards, and [http://blog.davidjanes.com/mtarchives/2005_08.html#003376 provides a popup menu of actions]. The hCard to vCard conversion is done internally within the script. ''This does not work with FireFox 1.5+/GreaseMonkey 0.6.4+.''
* [http://diveintomark.org/ Mark Pilgrim] has also written an [http://diveintomark.org/projects/greasemonkey/hcard/ hCard parser Greasemonkey user script]. It is self-contained and does not rely on the X2V web service.
* [http://www.oliverbrown.me.uk/2005/09/03/a-working-microformats-extension-to-simplexml/ Oliver Brown] has written an "extension" to [http://www.php.net/simplexml SimpleXML] that gives simple access to hCard information in PHP 5.
* [http://thedredge.org/ Andrew D. Hume] has built a system (Wordpress plugin?) for [http://thedredge.org/2005/06/using-hcards-in-your-blog/ using hcards in your blog] to represent people leaving comments on blog posts.
* The [http://tantek.com/microformats/hcard-creator.html hCard creator] is a very simple, yet illustrative, open source user interface / form / script which creates an hCard in real-time as you type in a set of contact information.
* [http://greenbytes.de/tech/webdav/rfc2629.xslt rfc2629.xslt] now attempts to generate hCard information ([http://ietf.org/rfc/rfc2629 RFC2629] is an XML format for authoring RFCs and Internet Drafts, see [http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html example document])
* [http://tantek.com/microformats/buddylist2hcards.html iChat buddy list to hCards] - Open source AppleScript to automatically convert one's buddy list in the MacOSX iChat AIM client into a valid XHTML 1.0 Strict list of hCards.
* [http://dev.w3.org/cvsweb/2001/palmagent/ palmagent] is a collection of palmpilot and sidekick tools. It includes X2V derivatives xhtml2hcard.xsl and toICal.xsl plus some [http://dev.w3.org/cvsweb/2001/palmagent/hcardTest.html hcardTest] materials
* [http://www.openpsa.org/ OpenPsa 2.x] CRM application uses hCard for all person listings. The widget is [http://www.midgard-project.org/midcom-permalink-922834501b71daad856f35ec593c7a6d reusable across Midgard CMS]
* [http://www.metonymie.com Emiliano Martínez Luque] has written an experimental [http://www.metonymie.com/hCard_extract/app.html hCard finder and structured search application] that finds hCards within a given set of URLs and returns the ones that match the specified search criteria.

== Additional Applications ==
This section is '''informative'''.

There are numerous potential additional uses and applications for hCards on the Web. The following are merely a few thoughts and possibilities that folks have come up with:

* As an open standard/format for [http://www.gravatar.com/ Gravatars].
* Marking up individual authors of blog posts on a group blog
* Marking up people's names and URLs in a blogroll
* Any reference to people in blog posts (e.g. when citing them, or referencing them, or describing them, by name).
* ...

== References ==
=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://www.ietf.org/rfc/rfc2426.txt vCard RFC2426]

=== Informative References ===
* [http://www.w3.org/2002/12/cal/rfc2426 HTML reformatted version of RFC2426]
* [http://w3.org/TR/REC-CSS1 CSS1]
* [http://tantek.com/log/2004/09.html#hcard hCard term introduced and defined on the Web, 20040930]
* [http://wiki.oreillynet.com/foocamp04/index.cgi?SimpleSemanticFormats FOO Camp 2004 Simple Semantic Formats presentation, 20040910]
* Contributed from http://developers.technorati.com/wiki/hCard.
* [http://www.w3.org/TR/xhtml11 XHTML 1.1]

==== Specifications That Use hCard ====
* [[adr]]
* [[geo]]
* [[hcalendar|hCalendar]]
* [[hreview|hReview]]

==== Similar Work ====
* [http://www.intertwingly.net/wiki/pie/PaceBetterPersonElement Atom PaceBetterPersonElement]
* [http://www.jabber.org/jeps/jep-0054.html JEP-0054: vcard-temp]

== Related Pages ==
* [[hcard-faq|hCard FAQ]] - If you have any questions about hCard, check here, and if you don't find answers, add your questions!
* [[hcard-parsing|hCard parsing]] - Normatively details of how to parse hCards.
* [[hcard-issues|hCard issues]] - Please add any issues with the specification to the issues page.
* [[hcard-profile|hCard profile]] - The XMDP profile for hCard

This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. These thoughts, issues, and questions are kept in separate pages.

* [[hcard-brainstorming|hCard Brainstorming]] - where we are keeping our brainstorms and other explorations relating to hCard
* [[hcard-tests|hCard tests]] - a wiki page with actual embedded hCards to try parsing.

== Further Reading ==
* [http://www.digital-web.com/articles/microformats_primer/ Digital Web Magazine: Microformats Primer] by Garrett Dimon has a good intro to hCard
* [http://24ways.org/advent/practical-microformats-with-hcard Practical Microformats with hCard] by Drew McLellan
* [http://thedredge.org/ Andrew D. Hume] has written a blog post on [http://usabletype.com/articles/2005/usable-microformats/ usable microformats] which discusses hCard
* [http://www.thefutureoftheweb.com/blog/2006/1/hcard Jesse Skinner's introduction to hCard]
* [http://blog.usweb.com/ Shaun Shull's] great post on [http://blog.usweb.com/archives/how-microformats-affect-search-engine-optimization-seo How Microformats Affect SEO], including his [[hcard|hCard]] as an example.
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page] and the [http://technorati.com/tags/hcard hCard tag]

events/2006-03-01-w3c-plenary-microformats

2006-02-25T07:41:14Z

DanC: linked my slides

<h1>Microformats panel at W3C Plenary Day</h1>

During the [http://www.w3.org/2006/03/01-TechPlenAgenda.html W3C Plenary Day] in the middle of the [http://www.w3.org/2005/12/allgroupoverview.html W3C All Group Meetings Week] in Mandelieu, FRANCE.

Presenters, please see To Do section.

__TOC__

== To Do ==

* ASAP: DanC, please add [[hcalendar|hCalendar]] and [[hcard|hCard]] markup to [http://www.w3.org/2006/03/01-TechPlenAgenda.html TP agenda]. ''I haven't found time. Anybody else got time to do the markup? I can probably install it.''

* All presenters should confirm that presentations are done and ready. Link to them from here as soon as possible (even drafts) so we can all review and see where everyone is at.
** Ian Hickson: started looking at some of the data Google didn't publish from our last billion-document run, to see if there's anything fun to show. I think I'll show the class names coloured based on how semantic they are, maybe.
** Tantek Çelik: not done yet
** Håkon Wium Lie: status unknown
** Rohit Khare: status unknown
** Dan Connolly: [http://www.w3.org/2003/g/talk62/slides slides] drafted

== Summary ==

This is the summary of the panel as sent to Steve Bratt as of 2006-02-17, and published at http://www.w3.org/2006/03/01-TechPlenAgenda.html :

Session 3: Microformats

Description: Leveraging the widespread adoption and understanding of CSS and semantic (X)HTML among web designers and publishers, microformats are a set of simple, practical, open data formats that are designed for humans first and machines second. Microformats are designed by researching and adapting to current human web publishing behaviors and usage patterns, and then reusing bits of existing widely adopted standards. This session will demonstrate the capabilities that have been quickly developed with microformats on today's Web, review current microformats, and open discussion on what microformats and related efforts mean for the future of the Web..

Moderators: Tantek Çelik (Technorati) and Don Connolly (W3C)

Presenters and Topics:

* Ian Hickson (Google) - "A billion documents and no semantics anywhere"
* Tantek Çelik (Technorati) - "What are microformats?"
* Håkon Wium Lie (Opera) - "Cascading Markup Languages — boom!"
* Rohit Khare (CommerceNet) - "Where Angle Brackets Fear to Tread"
* Dan Connolly (W3C) - "Microformats for practical Semantic Web deployment"

== Session Descriptions ==

These are session descriptions from each presenter.

Presenters, feel free to tweak/update your session descriptions.

=== Ian Hickson ===

"A billion documents and no semantics anywhere"

The "semantics" in the title refers to the "semantics" given to the Web by
HTML, as opposed to the "semantics" that are actually put in the Web by
the humans. Microformats can document existing practices (especially based
on the data from studies of existing documents) so that the existing
content can be given "official" "semantics".

Basically my talk will be something like "ooo look pretty shiny billion
documents lots of data that shows people use HTML not like it was intended
but we can reverse engineer microformats out of existing practices to
obtain useful information".

=== Tantek Çelik ===

"What are microformats?"

How did we get here? Picking up (hopefully) where the previous talk left off, a brief review of recent web authoring trends, a timeline of the ideas that formed microformats, and demonstrations how hCard and hCalendar are being put to good use today by publishers, browsers, and end users alike.

=== Håkon Wium Lie ===

"Cascading Markup Languages — boom!"

Cascading in CSS allows descigners to not have to provide the full presentation of a
document, they only need to supply the deltas from the html default
style sheet; cascading does the rest. In the same way, microformats
builds on the (admittantly shallow) semantics of HTML; you don't have
to create a new laguage to describe more semantics, you just provide
the deltas on top of HTML.

This is one of the design principles that CSS and microformat share,
others inlcude: simplicity, author-friendliness, an evolutionary
approach.

Boom will be provided as an example.

=== Rohit Khare ===

"Where Angle Brackets Fear to Tread"

XML has been a wild success almost everywhere in the information technology universe *except* for adding semantically-rich information to ordinary Web pages. Once upon a time, we were supposed to wish for <code><nowiki><price></nowiki></code> elements sprinkled about our HTML -- why is are we supposed to be so much more excited to see class="price" this time around? Dr. Khare will speak about his experiences with both xml and microformats in light of a recent project, hListing (for classified ads), and writing a parser and search engine for microformats in general.

=== Dan Connolly ===

"Microformats for practical Semantic Web deployment"

Microformats provide just enough structure to use semantic web technologies like RDF, OWL, and SPARQL on data in ordinary web pages. Dan will relate a few case studies and demonstrate some tools.

User:DanC

2006-02-17T16:12:06Z

DanC:

My [http://microformats.org/discuss/mail/microformats-dev/2005-July/000010.html hcardTest materials, XHTML version of RFC2426, and fun with microformats] message is sort of my introduction to this community. I have since discovered the "personal intro" ritual in [http://microformats.org/discuss/mail/microformats-discuss/ microformats-discuss] and I may join that soonish.

Meanwhile, I'm working on [[hcard-test]] and [[hcard-issues]] and such.

Ugh... yet another username/password out there. Oh for [http://www.openid.net/ OpenID]!

User:DanC

2006-02-17T16:11:27Z

DanC: oh for openID!

My [http://microformats.org/discuss/mail/microformats-dev/2005-July/000010.html hcardTest materials, XHTML version of RFC2426, and fun with microformats] message is sort of my introduction to this community. I have since discovered the "personal intro" ritual in [http://microformats.org/discuss/mail/microformats-discuss/ microformats-discuss] and I may join that soonish.

Meanwhile, I'm working on [[hcard-test]] and [[hcard-issues]] and such.

Ugh... yet another username/password out there. Oh for <a href="http://www.openid.net/">OpenID</a>!

hcalendar-brainstorming

2006-02-03T17:00:47Z

DanC: on workflow issues around hCalendar for big W3C meetings

= hCalendar Brainstorming =
__TOC__
== Authors ==
* [http://suda.co.uk/ Brian Suda]
* [http://tantek.com/log/ Tantek Çelik]

= BEST-PRACTICES =
Along with the four base properties, you can define addtional properties through the use of the x-prop property. For best-practices for hCal to iCal transformers, it would be helpful if the transforming application added the following x-* properties:

* X-FROM-URL. The value of this property would be the URL of the page where the iCal representation was generated.
<pre><nowiki>
X-FROM-URL:http://example.com/page-containing-hCal-encoding.html
</nowiki></pre>

* X-WR-CALNAME. iCal.app recognizes this property as the "calendar name" for subscribed calendars. Thus transforming applications *should* take the <code><title>...</title></code> from the page being parsed, optionally append " events", and use that value for the X-WR-CALNAME property in the resulting feed. E.g. if the page had <code><title>Example Home Page</title></code> then the .ics output should have as part of the vcalendar object:
<pre><nowiki>
X-WR-CALNAME:Example Home Page
</nowiki></pre>

= Examples =
This is a growing example case written in iCal format and transformed to the corresponding XHTML. These conversions are open to community input.

<pre><nowiki>
BEGIN:VEVENT
CATEGORIES:foo,bar
SUMMARY: Short Title
DESCRIPTION: Full Description
DTSTART;VALUE=DATE:20040101
DTEND:20040101T235959Z
RRULE:FREQ=YEARLY;UNTIL=20080102T000000Z
URL;WORK:http://example.com
ATTENDEE;ROLE=CHAIR:MAILTO:JohnDoe@example.com
GEO:37.386013;-122.082932
END:VEVENT
</nowiki></pre>
<pre><nowiki>
<p class="vevent">

Categories:
<ul class="categories">
<li>foo</li>
<li>bar</li>
</ul>
<a href="http://example.com" class="summary">Short Title</a>
<span class="description">description</span>
<span class="geo"><span class="Lat">37.386013</span> <span class="Lon">-122.082932</span></span>



Date: <em class="dtstart">20040101</em> - <em class="dtend">20040101T235959Z</em>




<a class="attendee chair" href="mailto:JohnDoe@example.com">John Doe</a>


<p class="rrule">The event will be held <span class="freq">yearly</span> until <span class=""until">20080102T000000Z</span>.</p>

</p>
</nowiki></pre>

@@-need to look at nested tag examples
<pre><nowiki>
XHTML
<span class="description"><span class="summary">Short Title</span> to a longer article</span>

vCal
SUMMARY:Short Title
DESCRIPTION:Short Title to a longer article
</nowiki></pre>

== Examples from RFC 2445 ==

* <del>Note: this subsection is worthy of being the start of a new page: [[hcalendar-examples]], similar to [[hcard-examples]] -[http://tantek.com/log/ Tantek]</del>
* These examples are now all available on [[hcalendar-examples]] -[[User:RyanKing]]

With the abbr's title attribute being used rather than the node value, the actual data could vary and still represent the same vcalendar.

<pre><nowiki>
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//hacksw/handcal//NONSGML v1.0//EN
BEGIN:VEVENT
DTSTART:19970714T170000Z
DTEND:19970715T035959Z
SUMMARY:Bastille Day Party
END:VEVENT
END:VCALENDAR
</nowiki></pre>

<pre><nowiki>
<span class="vcalendar">
<span class="vevent">
<abbr class="dtstart" title="19970714T170000Z">July 14th</abbr>
<abbr class="dtend" title="19970715T035959Z"></abbr>
<span class="summary">Bastille Day Party</span>
</span>
</span>
</nowiki></pre>

=== UID handling ===

The UID in iCal is represented in HTML as the id attribute in these examples. Any valid id in HTML is a valid UID in iCal, but not the contrapositive, a valid UID is NOT a valid HTML id. HTML ids can only start with a letter, not a number.

<pre><nowiki>
BEGIN:VEVENT
UID:19970901T130000Z-123401@host.com
DTSTAMP:19970901T1300Z
DTSTART:19970903T163000Z
DTEND:19970903T190000Z
SUMMARY:Annual Employee Review
CLASS:PRIVATE
CATEGORIES:BUSINESS,HUMAN RESOURCES
END:VEVENT
</nowiki></pre>

<pre><nowiki>
<span class="vcalendar">
<span class="vevent" id="19970901T130000Z-123402@host.com">
<abbr title="dtstamp" class="19970901T1300Z"></abbr>
<abbr title="dtstart" class="19970903T163000Z">September 3rd, 4:30pm</abbr>-
<abbr title="dtend" class="19970903T190000Z">7:00pm</abbr>
<span class="summary">Annual Employee Review</span>
<span class="class">private</span>
<ul class="categories">
<li>BUSINESS</li>
<li>HUMAN RESOURCES</li>
</ul>
</span>
</span>
</nowiki></pre>

<pre><nowiki>
BEGIN:VCALENDAR
BEGIN:VEVENT
UID:19970901T130000Z-123402@host.com
DTSTAMP:19970901T1300Z
DTSTART:19970401T163000Z
DTEND:19970402T010000Z
SUMMARY:Laurel is in sensitivity awareness class.
CLASS:PUBLIC
CATEGORIES:BUSINESS,HUMAN RESOURCES
TRANSP:TRANSPARENT
END:VEVENT
END:VCALENDAR
</nowiki></pre>
<pre><nowiki>
<span class="vcalendar">
<span class="vevent" id="19970901T130000Z-123402@host.com">
<abbr title="dtstamp" class="19970901T1300Z"></abbr>
<abbr title="dtstart" class="19970401T163000Z">April 1st 4:30pm</abbr>-
<abbr title="dtend" class="19970402T010000Z">1:00am</abbr>
<span class="summary">Laurel is in sensitivity awareness class.</span>
<span class="class">PUBLIC</span>
<ul class="categories">
<li>BUSINESS</li>
<li>HUMAN RESOURCES</li>
</ul>
<span class="transp">Transparent</span>
</span>
</span>
</nowiki></pre>

=== RRULE handling ===

The way RRULE is encoded should be discussed.

<pre><nowiki>
BEGIN:VEVENT
UID:19970901T130000Z-123403@host.com
DTSTAMP:19970901T1300Z
DTSTART:19971102
SUMMARY:Our Blissful Anniversary
CLASS:CONFIDENTIAL
CATEGORIES:ANNIVERSARY,PERSONAL,SPECIAL OCCASION
RRULE:FREQ=YEARLY
END:VEVENT
</nowiki></pre>
<pre><nowiki>
<span class="vcalendar">
<span class="vevent" id="19970901T130000Z-123403@host.com">
<abbr title="dtstart" class="19970901T1300Z"></abbr>
<abbr title="dtend" class="19971102">November 2nd</abbr>
<span class="summary">Our Blissful Anniversary</span>
<span class="class">CONFIDENTIAL</span>
<ul class="categories">
<li>ANNIVERSARY</li>
<li>PERSONAL</li>
<li>SPECIAL OCCASION</li>
</ul>
<span class="rrule"><span class="freq">YEARLY</span></span>
</span>
</span>
</nowiki></pre>

== Examples from real world event sites ==

=== W3C Meetings ===

I just got email announcing the dates of another W3C meeting. I don't think it's marked up with hCalendar. I could mark it up myself, like I did for [http://www.w3.org/2005/12/allgroupoverview.html the TP day/week schedule], but it might not stick. Somehow I got [http://www.w3.org/2000/08/w3c-synd/ our syndicated news markup] (precursor to [[hAtom]]) to stick, i.e. to become part of the norm in the W3C comm team. I wonder if I could pull that off for calendars.

My first thought is authoring tools, but I don't think I can wait that long.
Next thought is instant-feedback checking tools...
X2V is really handy, but can't be used for confidential pages (and many/most calendars I use are not public).
So.. how about some in-browser javascript "yes, you got it right!" or "hmm... that looks like a date; is there an event you didn't mark up?" feedback? I think I saw something like that in hCalendar implementations.

[[User:DanC|DanC]] 09:00, 3 Feb 2006 (PST)

=== Laughing Squid ===

Laughing Squid had the following [http://laughingsquid.com/squidlist/calendar/9584/2005/4/7 multiple occurence event example]:

Thu, Apr 7 : Tu/Wed: 12-4pm Th/Fr/Sat 12-7pm Sun 12-6pm

In addition, later on in the description, it says:

April 7-21, 2005

This is actually quite a non-trivial example, because the event lasts for different durations on different days (4 hours, 7 hours, 6 hours).

Because of the differing durations, the specification requires that *each* instance of this recurring event be explicitly specified.

But first we markup the starting date and time explicitly:
<pre>
<abbr class="dtstart" title="20050407T1200-0700">Thu, Apr 7</abbr> :
</pre>
Then we put in the quite lengthy explicit specification of every other time the event occurs, marked up around the human readable description.
<pre>
<abbr class="rdate" title="20050407T1200-0700/PT7H, 20050408T1200-0700/PT7H,
20050409T1200-0700/PT7H, 20050410T1200-0700/PT6H, 20050412T1200-0700/PT4H,
20050413T1200-0700/PT4H, 200504014T1200-0700/PT7H, 20050415T1200-0700/PT7H,
20050416T1200-0700/PT7H, 20050417T1200-0700/PT6H, 20050419T1200-0700/PT4H,
20050420T1200-0700/PT4H, 20050421T1200-0700/PT7H" >
Tu/Wed: 12-4pm Th/Fr/Sat 12-7pm Sun 12-6pm
</abbr>
</pre>

The RDATE "PERIOD" format is fairly straightforward. You simply list *each* occurrence of the event, separated by commas. Each occurrence consists of the ISO8601 datetime of the start of the event, followed by a slash "/", followed by *either* the duration of the event (e.g. 7 hours = PT7H), *or* a complete ISO8601 datetime of the end of the event. I chose to use the duration of the event for this example for reason of brevity.

Note that "value=period:" is unnecessary in the rdate value since the parser can infer "value=period:" from the presence of a "/" in the title attribute value.

With simpler repeating events, or perhaps events which only repeat a day or two, their hCalendar markup may be more illustrative of how to do this in a general way.

= CSS Styles =
Since the hCal properties are added in as CSS styles, you can style them along with any normal CSS style. You are free to style these properties in any fashion you want (see specific notes), but here are a few examples that you can use.

== Preserving White-space ==
If you are encoding data that requires tabs, returns, or other white-space to be perserved you can use the following CSS property to do so in HTML.
<pre><nowiki>
<span style="white-space: pre">
This white-space
will be
preserved
</span>
</nowiki></pre>
white-space can take one of three different parameters; normal, pre, and no-wrap.

== Not recommended ==

The following CSS styling techniques are not recommended:

=== Hiding Data ===
It is possible to encode additional data without it being displayed in the HTML, by using the CSS style property 'display'.
<pre><nowiki>
<span style="display:none">Hidden Data</span>
</nowiki></pre>
This data will be found by any transforming application and will be properly encoded into an iCal file.

'''You SHOULD NOT do this because it violates the visibility priniciple.'''

= Tutorials =
How to include hCal encodings into your favourite Blogging Software.

= Open Questions =
== General Questions ==
Q: Should Transforming applications purely extract the information and ignore validity? or should there be some checking, or should this be left to the importing application? (i.e. DTSTART;VALUE=DATE: This-Is-Not-a-proper-date)

A: The simpler the better. Other than checking for perhaps X(HT)ML validity, it should be a simple translator, because presumably the receiving iCalendar application has to have malformed .ics handling already. Let's avoid duplicating that. -- [http://tantek.com/ Tantek Çelik]

Q: What about multiple of the instances same vCal entity? (two instances of DTSTART) Is this left up to the importing application, or should the XSLT transformation fail?

A: Same as previous. Leave it up to the importing application to interpret it per the iCalendar spec, e.g. what does RFC2445 say about two instances of DTSTART? -- [http://tantek.com/ Tantek Çelik]

From RFC2445:
4.1.2 Multiple Values
Some properties defined in the iCalendar object can have multiple values. The general rule for encoding multi-valued items is to simply create a new content line for each value, including the property name. However, it should be noted that some properties support encoding multiple values in a single property by separating the values with a COMMA character (US-ASCII decimal 44). Individual property definitions should be consulted for determining whether a specific property allows multiple values and in which of these two forms.

Other than that, it does not mention what to do ABOUT invalid data, or which of the multiple entries takes precedence. The only mention of duplicate instances is in the RRULE and EXDATE rules where events exclusions/inclusions overlap. Then duplicate instances are ignore. If it is explicitly written for those items, but NOT for things like DTSTART, then it is difficult to assume duplicate instances are ignored for them as well.

Each of the Components (VEVENT, ...) define which properties can exisit and in what quantity. So multiple DTSTART properties are NOT allowed.
-- [http://suda.co.uk Brian Suda]

Q: Should vCal entitles be represented in XHTML in classes ONLY on block-level element? or should some like VEVENT be block-level and others be of any? does this impact the semantics at all?

A: I don't think the (X)HTML notion of "block-level" should have any bearing whatsoever on vCal entities. You should be able to say <span class="vevent"> or <div class="vevent"> and either should work.

Q: Should the transforming application add any additional information to the iCalendar representation other than what was encoded in the HTML? (i.e. UID, the unique identifier might not be present in the HTML code, but could be generated by the transforming application and added to the iCal file. Should this be allowed? or should the transforming app ONLY be allowed to add X-PROPERTY properties?) IF it was not explicitly encoded in the HTML should it be left out? What about default values?

Q: If we are looking at the most semantic way to encoding iCalendar data in HTML then several other attributes should be considered besides just 'class'. There are two other candidated, ID and REL. The ID tag MUST be unique within the XHTML file (this could be used for the UID property). The REL attribute can ONLY be applied to 'a' and 'link' tags, but might be helpful. Are namespac<ETH>H �n option? xml:lang, xml:base, are there any others that might be more semantically correct to encode this data?

Q: To help distinguish xparam values from other actual CSS styles, should we assume/mandate that all values in a class attribute within an encoded iCal component class attribute (<x class="vevent|vtodo|...">) be considered an xparam?

A: If you are using other CSS styles (e.g. "center", "bluebox", "greenline", etc.) nested within an iCal component, those should be avoided and the styles applied to the list of iCal properties instead/also?

<pre><nowiki>
.center, .vevent { text-align: center; }
</nowiki></pre>

Q: What about cases where the words "yesterday", "last year", or "last week" was used? How should we represent this? Is this overkill or not appropriate for hcard ? - [[User:B.K._DeLong]]

A: I took a stab at "yesterday" and just added a dtstart of the previous day. Not sure how to represent a single year or whole week - [[User:B.K._DeLong]]

<pre><nowiki>
<abbr class="dtstart" title="20050114">Yesterday's</abbr>
</nowiki></pre>

== Recurring Events ==

Recurring events are tricky. First, there's the question of whether to follow ''For types with multiple components, use nested elements with class names equivalent to the names of the components'' a la
<pre>
<nowiki><div class="rrule">every <em class="interval">1</em>
<em class="freq">WEEKLY</em> on <em class="byday">TU</em>
until <em class="until">2004-11-01</em></div></nowiki>
</pre>
... or ...
<pre>
<nowiki><abbr class="rrule" title="FREQ=WEEKLY;COUNT=17;INTERVAL=2;BYDAY=TH"> every other
Thursday for 34 weeks</abbr></nowiki>
</pre>
... as in [http://microformats.org/discuss/mail/microformats-discuss/2005-August/000516.html Tantek's 1 Aug msg].

[http://www.w3.org/People/Connolly/ DanC] has been experimenting with representing his PDA calendar in hCalendar:

* in [http://dev.w3.org/cvsweb/2001/palmagent/ palmagent], there's dangerSync.py which uses the XMLRPC interface and spits out RDF data. Then asHCal.xsl converts that to hCalendar
* then in [http://www.w3.org/2002/12/cal/ the RDF Calendar workspace], there's [http://www.w3.org/2002/12/cal/glean-hcal.xsl glean-hcal.xsl] that turns hCalendar into RDF Calendar, and finally,
* in [http://www.w3.org/2000/10/swap/ SWAP] there's [http://www.w3.org/2000/10/swap/pim/toIcal.py toIcal.py] that turns RDF Calendar to .ics format.

So I can go from my sidekick to .ics with one Makefile.

[http://dev.w3.org/cvsweb/2001/palmagent/event-test.html events-test.html] is a test file that has all the constructs from my PDA data, in hCalendar. In particular, it uses the nested element representation of recurring events. glean-hcal.xsl would be much less fun to write if it had to parse <nowiki>title="FREQ=WEEKLY;COUNT=17;INTERVAL=2;BYDAY=TH"</nowiki>.

Then there's the question of "every tuesday afternoon at 2pm Chicago time". This isn't expressible using [[datetime-design-pattern]]. There are some good reasons for that, but it leaves a rather large and uncomfortable gap in hCalendar.

== Encoding Questions ==
The way dates are encoded is not always the most user friendly. If i want to encode january 1st, 2005, that is <code><span class="dtstart">20050101</span></code>, which is displayed as 20050101. If we are marking-up comma seperated values, like FN, with each sub-element inside their own tag, then the date should be allowed the same.

(However, FN is in the RFC2426 spec and vCard schema, these individual date terms are not, therefore the reasoning in the last sentence is incorrect. -[http://tantek.com/log/ Tantek])

<pre><nowiki>
20050101
<span class="dtstart"><span class="Year">2005</span><span class="Month">01</span><span class="Day">01</span></span>
</nowiki></pre>
With this encoding, then YYYYMMDD schema can be rearranged for different cultures, DD-MM-YYYY for UK, MM-DD-YYYY for US, etc.
<pre><nowiki>
02-01-2005
<span class="dtstart"><span class="Month">02</span>-<span class="Day">01</span>-<span class="Year">2005</span></span>
01-02-2005
<span class="dtstart"><span class="Day" title="first">01</span>-<span class="Month" title="Feb">02</span>-<span class="Year">2005</span></span>
</nowiki></pre>
Both of the above encodings are equal, the '-' seperator is ignored by the transforming application. -- [http://suda.co.uk Brian Suda]

Agreed that the way dates are encoded is not always the most user friendly, but there is an easier solution to this, once you think of what is actually going on in the difference between ISO8601 dates, and dates the way humans use them. Humans typically use an abbrevation or shorthand for a date, like "tomorrow", or "Tuesday", or "the 4th", or perhaps "July 4th". Thus it makes sense to permit this in hCalendar, using the <code><abbr></code> tag which provides the ability to markup the human-familiar short form of some data or language, while preserving the long form in the 'title' attribute.

E.g. for the above example of a start date of January 1st, 2005, you could use this markup:

<pre><nowiki>
<abbr class="dtstart" title="20050101">January 1st, 2005</abbr>
</nowiki></pre>

Which would display as <code>January 1st, 2005</code> but would provide the respective ISO8601 date in the title attribute. - [http://tantek.com/log Tantek]

= TODO =
A HTML head profile needs creation and a home.

== Applications ==
A simple implementation of transforming/extracting vCal data from an XHTML file is available for testing. A bookmarklet is also available. The code will be updated as the spec is finalised.
http://suda.co.uk/projects/X2V/

== Parsing ==

Need to write up an [[hcalendar-parsing]] document, similar to [[hcard-parsing]].

=== Tabular Data ===

Many calendars are posted in tabular form, where the headings on the columns and rows have property values that apply to the cells which themselves are events.

(TODO: document "How To" for marking up tabular event listings)

To enable mark these up with [[hcalendar|hCalendar]], we must parse additional semantic attributes from HTML4.

When parsing, in addition to the special case rules documented in [[hcard-parsing]]:

* If the element is a table data cell <code><td></code>, then:
*# parse its "headers" attribute as a space separated set of local IDs
*# find the <code><td></code> and <code><th></code> elements referenced by those IDs (call them header cells) and consider them part of the element being parsed as follows:
*## Treat the header cells as children of the element, ordered by the order of ids in its "headers" attribute, immediately following the last child node (text or element) or the element. (The basic idea is that the content from those header cells is used to construct the VEVENT, but secondary to (AFTER) the content in the data cell itself, so that the data cell can customize/override part of the data in the header, e.g. if the header cell included both start time and location, and the event was being held at a different location).
*## Parse the "axis" attribute of a header cell as a comma-separated list of categories. These categories must be used in addition to (and before) any class names on that header cell for determining whether it is a property of the VEVENT.

== Relationships with other microformats ==

In a [http://www.technologyreview.com/articles/04/10/frauenfelder1004.asp Technology Review interview], TBL said "It would have the relationships between the event and the various people chairing it.".

We should have examples of how hCalendar events can indicate such relationships, both in the format and in the presentation.
E.g.:
* Would it just link to URLs for the various people? (e.g. to their homepages/blogs etc.)
* Would it include hCards for the various people?
* Would it link to hCards for various people?
* Perhaps allow all the above?

== Mime-Type ==
According to RFC2445, the proposed media type value is 'text/calendar'.

A standard vCalendar file has an extension of .vcs and MIME type of text/x-vCalendar. If you use iCalendar, the MIME type is "text/Calendar" and the extension is .ics.

Text/X-vCalendar Content Type
The vCalendar object can also be passed as a non-standard MIME media type. This would be useful in order to clearly identify the vCalendar object in an electronic mail message body part. A non-standard, vCalendar object should be identified as the MIME type/subtype "text/x-vCalendar".

@@ - i have to do some more investigation, but (i think) vCalendar is a subset of iCalendar, so many of the same encodings will work for both, but this document is dealing with iCalendar RFC2445 representation!

== Button ==

We need to come up with a nice <code>[ hCal | friendly ]</code> button to indicate that event info on a page/site is using hCalendar. - [http://tantek.com/log/ Tantek].

Possibilities:
* <code>[ hCal | friendly ]</code>
* <code>[ hCal | aware ]</code>
* <code>[ hCal | inside ]</code>
* <code>[ Valid | hCalendar ]</code> - though that would require writing an hCalendar validator which people could link to.
* <code>[ <icon> | hCalendar ]</code> where <icon> could be some generic calendar looking thing, or it could be a PHP generated image with the actual date in the icon, kind of like how the Apple iCal icon updates in the dock automatically.

And then we have to pick colors and all that stuff - [http://tantek.com/log/ Tantek].

Other ideas:
* <code>[ hCal | enabled ]</code>
* <code>[ hCal | available ]</code> - kind of an off-hand reference to being available for meetings, etc.

- [http://meyerweb.com/ Eric]

== Including More of iCalendar ==

=== Free/Busy information ===

See [http://www.ifreebusy.com/cyclical/blog/ Neil Jensen]'s [http://www.ifreebusy.com/cyclical/blog/calendar/3 analysis of how to represent the iCalendar VFREEBUSY object in hCalendar].

In order to show free/busy information, we could either use the existing vevent class (with empty location, summary, etc. properties) or create a new vfreebusy class. We should create a new vfreebusy class because it is consistent with the XHTML design principles, particularly point #4, "Use class names based on names from the original schema...".

In the iCalendar standard, the vfreebusy calendar component frequently has more than one freebusy property, and also may have a number of other properties such as organizer. For example:

<pre><nowiki>
BEGIN:VFREEBUSY
ORGANIZER:jsmith@host.com
DTSTART:19980313T141711Z
DTEND:19980410T141711Z
FREEBUSY:19980314T233000Z/19980315T003000Z
FREEBUSY:19980316T153000Z/19980316T163000Z
FREEBUSY:19980318T030000Z/19980318T040000Z
URL:http://www.host.com/calendar/busytime/jsmith.ifb
END:VFREEBUSY
</nowiki></pre>

So, our hCalendar representation should include separate elements for the vfreebusy calendar component (defined once) and the freebusy property (possibly defined many times):

<pre><nowiki>
<span class="vfreebusy">
<span class="freebusy">
<abbr class="dtstart" title="20050721T1000-0800">
July 21, 2005 - 10:00
</abbr> -
<abbr class="dtend" title="20050721T1100-0800">
11:00
</abbr>
</span><br/>
<span class="freebusy">
<abbr class="dtstart" title="20050722T1000-0800">
July 22, 2005 - 10:00
</abbr> -
<abbr class="dtend" title="20050722T1100-0800">
11:00
</abbr>
</span><br/>
</span>
</nowiki></pre>

According to RFC2445, "When publishing a "VFREEBUSY" calendar component, the property is used to specify the calendar that the published busy time came from." The property type is CAL-ADDRESS, and can include "non-standard, language, common name and directory entry reference" property parameters. CAL-ADDRESS is "...a URI as defined by [RFC 1738] or any other IANA registered form...".

From what I've seen, Microsoft Outlook typically populates this property with the email address of the calendar owner, which initially made me think of using hCard to specify the organizer. However, given that the property refers to the calendar and not necessarily the person who owns or has published it, I think we should use a new organizer element, as shown below:

<pre><nowiki>
BEGIN:VFREEBUSY
ORGANIZER:jsmith@host.com
FREEBUSY:20050314T133000Z/20050314T163000Z
END:VFREEBUSY
</nowiki></pre>

becomes

<pre><nowiki>
<span class="vfreebusy">
organizer: <span class="organizer">jsmith@host.com</span>
<span class="freebusy">
<abbr class="dtstart" title="20050314T133000Z">
March 14, 2005 - 13:30
</abbr> -
<abbr class="dtend" title="20050314T163000Z">
16:30
</abbr>
</span><br/>
</span>
</nowiki></pre>

Hmmm, this looks a little funny when the organizer is so obviously an email address, but at least it is semantically correct. The other problem that I can now see occurring is when the organizer property has parameters, for example (from the iCalendar spec):

<pre><nowiki>
ORGANIZER;CN=JohnSmith;DIR="ldap://host.com:6666/o=3DDC%20Associ
ates,c=3DUS??(cn=3DJohn%20Smith)":MAILTO:jsmith@host1.com
</nowiki></pre>

Perhaps it's best to use the same approach described in "Human vs. ISO8601 dates problem solved"; use the abbr element like so:

<pre><nowiki>
<span class="vfreebusy">
<span class="freebusy">
organizer: <abbr class="organizer" title="CN=JohnSmith;DIR=ldap://host.com:6666/o=3DDC%20Associ
ates,c=3DUS??(cn=3DJohn%20Smith):MAILTO:jsmith@host1.com">jsmith@host1.com</abbr>
<abbr class="dtstart" title="20050314T133000Z">
March 14, 2005 - 13:30
</abbr> -
<abbr class="dtend" title="20050314T163000Z">
16:30
</abbr>
</span>
</span>
</nowiki></pre>

=== To-Do information ===

The [http://www.policyawareweb.org/2005/ftf2/paw-mtg Policy Aware Web (PAW) Project Meeting - 23 Aug 2005] uses class="vtodo" to capture action items. Clearly recording action items from a meeting and publishing them as minutes is a good practical example use of the VTODO object on the web.

What's the scenario for usage though?

What kind of indexer/aggregator application would find these VTODO items and what would it do with them?

Perhaps with some way of figuring out who the to-do item is assigned to ("ATTENDEE"), who assigned it ("DELEGATED-FROM"), and a whitelisting of who, perhaps the "ORGANIZER" property, (and their domains/URLs) that a user would accept assignments from, a user could aggregate to-do items assigned from other folks. Then question remains how to update the status ("STATUS") (RFC 2445 4.8.1.11 Status) on that to-do item when it is (a) completed ("COMPLETED"), (b) abandoned/cut/rejected ("CANCELLED"), (c) some progress is made ("IN-PROCESS") etc. There certainly seems to be sufficient expressiveness in VTODO and its properties to do a decentralized to-do list / task distribution system. Could be very interesting for helping open source projects and other distributed teams do project management using the Web.

= References =
== Normative References ==
* [http://www.ietf.org/rfc/rfc2445.txt RFC 2445]
* [http://gmpg.org/xmdp/ XMDP]

== Informative References ==
* [http://wiki.oreillynet.com/foocamp04/index.cgi?HTMLForCalendars HTMLForCalendars (FOO camp)] - presented just a few days before this, hopefully these efforts can be combine

* [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.ietf.org/rfc/rfc2446.txt iTIP RFC2446]
* [http://www.ietf.org/rfc/rfc2447.txt iMIP RFC2447]
* [http://www.ietf.org/rfc/rfc3283.txt Guide to Internet Calendaring RFC3283]

== Other Implementations/Ideas ==
* [http://www.nehmer.net/~bergie/openpsa-calendar-horizontal.jpg OpenPSA calendar screenshot]
* [http://www.w3.org/2002/12/cal/ RDF Calendar Workspace] - some older work done with RDF, not really applicable to the simple XHTML case, but perhaps worthy of analysis for when and why they may have diverged from established iCalendar schemas.
* [http://planb.nicecupoftea.org/archives/000072.html 2003 RDF icalendar work, xCal references]

== Blogs About Calendaring ==
* http://staff.washington.edu/oren/weblog2/

rest/ahah

2005-11-29T05:04:22Z

DanC: friend/friendly typo

= AHAH: Asychronous HTML and HTTP =

AHAH is a very simple technique for dynamically updating web pages using [http://en.wikipedia.org/wiki/JavaScript JavaScript]. It involves using [http://en.wikipedia.org/wiki/XMLHTTP XMLHTTPRequest] to retrieve [http://en.wikipedia.org/wiki/HTML (X)HTML] fragments which are then inserted directly into the web page, whence they can be styled using [http://en.wikipedia.org/wiki/Cascading_Style_Sheets CSS].

== Contributors ==
* [http://www.loudthinking.com/ David Hansson]
* [http://epeus.blogspot.com/ Kevin Marks]
* [http://www.opendarwin.org/~drernie/ Ernest Prabhakar]

== Relation to AJAX ==

AHAH is intended to be a much simpler way to do [http://en.wikipedia.org/wiki/Web_development web development] than [http://en.wikipedia.org/wiki/Ajax_%28programming%29 AJAX]: "Asynchronous JavaScript and XML." Strictly speaking, AHAH can be considered a subset of AJAX, since (X)HTML is just a special kind of XML. However, it is a subset with some very specific and useful properties:
# The lack of custom XML schemas dramatically reduces design time
# AHAH can trivially reuse existing HTML pages, avoiding the need for a custom web service
# All data transport is done via browser-friendly HTML, easing debugging and testing
# The HTML is designed to be directly embedded in the page's DOM, eliminating the need for parsing
# As HTML, designers can format it using CSS, rather than programmers having to do XSLT transforms
# Processing is all done on the server, so the client-side programming is essentiall nil (moving opaque bits)

In fact, for any content that is destined to be viewed by the browser, it is virtually impossible to imagine any advantage to sending it as custom XML rather than structurally-correct HTML (with appropriate CSS-friendly class names, of course).

That said, many applications of AJAX are (at least in theory) targeteable at custom JavaScript code or desktop GUIs rather than mere browsers. For those cases, the advantages of HTML over custom XML are somewhat less. However, even here, it may well make sense to encode data using [[xoxo]] -- aka XHTML Property Lists -- which can be losslessly converted back and forth from standard data structures (lists and dictionaries) without the need for custom parsers.

== Source Code ==
Unlike the various libraries (e.g., [http://en.wikipedia.org/wiki/JSON JSON], [http://mochikit.com/ MochiKit]) important for AJAX, all of AHAH is contained in a single JavaScript file (also available as [http://www.opendarwin.org/~drernie/src/ahah.js ahah.js] and [http://homepage.mac.com/kevinmarks/jah.js jah.js]). In fact, this is little more than the canonical XMLHttpRequest example, and is simple enough for any modern web designer to embed within their existing web pages.

=== Send AHAH Request ===

function ahah(url,target) {
// native XMLHttpRequest object
document.getElementById(target).innerHTML = 'sending...';
if (window.XMLHttpRequest) {
req = new XMLHttpRequest();
req.onreadystatechange = function() {ahahDone(target);};
req.open("GET", url, true);
req.send(null);
// IE/Windows ActiveX version
} else if (window.ActiveXObject) {
req = new ActiveXObject("Microsoft.XMLHTTP");
if (req) {
req.onreadystatechange = function() {ahahDone(target);};
req.open("GET", url, true);
req.send();
}
}
}

Note the workaround needed for IE's ActiveX implementation. The current version hard-codes GET; there may be value in adding an extra parameter to allow POST, PUT, and DELETE.

=== Receive AHAH Request ===

function ahahDone(target) {
// only if req is "loaded"
if (req.readyState == 4) {
// only if "OK"
if (req.status == 200) {
results = req.responseText;
document.getElementById(target).innerHTML = results;
} else {
document.getElementById(target).innerHTML="ahah error:\n" +
req.statusText;
}
}
}

Other than error checking, the only real work done is:

document.getElementById(target).innerHTML = results;

Everything else (e.g., CSS-styling) is merely inherited from the parent webpage.

=== Executing Javascript ===

Since the browser won't execute <script> tags when changing innerHTML, you may want to apply the following function call on document.getElementById(target):

var bSaf = (navigator.userAgent.indexOf('Safari') != -1);
var bMoz = (navigator.appName == 'Netscape');
function execJS(node) {
var st = node.getElementsByTagName('script');
var strExec;
for(var i=0;i<st.length; i++) {
if (bSaf) {
strExec = st[i].innerHTML;
}
else if (bMoz) {
strExec = st[i].textContent;
}
else {
strExec = st[i].text;
}
try {
eval(strExec);
} catch(e) {
alert(e);
}
}
}

== History ==

"AHAH" as a formal technique appears to have been introduced by Kevin Marks on May 12, 2005 under the name [http://epeus.blogspot.com/2005_05_01_epeus_archive.html#111588374981985824 JAH]: "Just Asynchronous HTML", where it was also used in a [http://homepage.mac.com/kevinmarks/staticjah.html simple example]. The term "AHAH" was proposed by Ernest Prabhakar during the 2005 [http://www.web2con.com/ Web 2.0] conference, and later adopted as part of the REST-Enabled XHTML ([http://www.opendarwin.org/~drernie/C395201355/E20051019175947/index.html REX]) microformat for web services.

David Hansson had independently discovered the exact same concept, and in fact had already submitted an abstract about it for O'Reilly's 2006 [http://conferences.oreillynet.com/etech/ E-Tech] conference when he encountered the work done by Marks and Prabhakar. He had not however named the technique, and quickly agreed to adopt the AHAH moniker. The same concept has no doubt been independently discovered by others, but these three appear to be the first to make a sustained attempt to promote it as a formal technique.

== Implementations ==
* Sample [http://www.opendarwin.org/~drernie/src/ahah.js JavaScript code] available from Ernie Prabhakar, extending work by Kevin Marks.
* There is some talk of directly supporting AHAH in [http://www.rubyonrails.com/ Ruby on Rails] using [http://wiki.rubyonrails.com/rails/pages/UnderstandingPartials partials].

hcard

2005-11-11T00:27:55Z

DanC: DanC's list of events has hCards

= hCard =

hCard is a simple, open, distributed contact information format for people, companies, and organizations, which is suitable for embedding in (X)HTML, Atom, RSS, and arbitrary XML. hCard is a 1:1 representation of the vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]) in XHTML, one of several open [[microformats|microformat]] standards.
__TOC__

== Draft Specification ==

=== Editor ===
[http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc.]

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

=== Copyright ===
{{MicroFormatCopyrightStatement2004}}

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

=== Inspiration and Acknowledgments ===
Thanks to: my good friend [http://vadim.com/ Vadim] who introduced me to vCard ''many'' years ago, and if I'd only paid more attention then, perhaps I could have helped a lot of people avoid wasting a lot of time reinventing various standards wheels.

== Introduction ==
The vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]), has been broadly interoperably implemented (e.g. Apple's "Address Book" application built into MacOSX).

In addition, many bloggers identify themselves by name and discuss their friends and family. With just a tad bit of structure, bloggers can discuss people in their blog(s) in such a way that spiders and other aggregators can retrieve this information, automatically convert them to vCards, and use them in any vCard application or service.

This specification introduces the '''hCard''' format, which is a 1:1 representation of the aforementioned vCard standard, in semantic XHTML. Bloggers can both embed vCards directly in their web pages, and style them with CSS to make them appear as desired. In addition, hCard enables applications to retrieve information about such vCards directly from web pages without having to reference a separate file.

== Semantic XHTML Design Principles ==
{{semantic-xhtml-design-principles}}

== Format ==
=== In General ===
The vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]) forms the basis of hCard.

The basic format of hCard is to use vCard object/property names in lower-case for class names, and to map the nesting of vCard objects directly into nested XHTML elements.

=== More Semantic Equivalents ===
However, for some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:
* <code>URL</code> in vCard becomes <code><a class="url" href="...">...</a></code> inside the element with <code>class="vcard"</code> in hCard.
* Similarly, <code>EMAIL</code> in vCard becomes <code><nowiki><a class="email" href="mailto:...">...</a></nowiki></code>
* <code>PHOTO</code> in vCard becomes <code><img class="photo" src="..." alt="Photo of ..." /></code>

=== Singular vs. Multivalued Properties ===

For properties which are singular (e.g. "N" and "FN"), the first descendant element with that class should take effect, any others being ignored.

For properties which can be plural (e.g. "TEL"), each class instance should create a instance of that property.

==== Plural Properties Singularized ====

Since plural property names become their singular equivalents, even if the original plural property permitted only a single value with multiple components, those multiple components are represented each with their own singularly named property and the the property is effectively multivalued and subject to the above treatment of multivalued properties.

=== Human vs. Machine readable ===

If an <code><abbr></code> element is used for a property, then the '<code>title</code>' attribute of the <code><abbr></code> element is the value of the property, instead of the contents of the element, which instead provide a human presentable version of the value.

Similarly, if an <code><img></code> element is used for one or more properties, it must be treated as follows:
# For the "PHOTO" property and any other property that takes a URL as its value, the <code>src="..."</code> attribute provides the property value.
# For other properties, the <code><img></code> element's '<code>alt</code>' attribute is the value of the property.

=== Value excerpting ===

Sometimes only part of an element which is the equivalent for a property should be used for the value of the property. This typically occurs when a property has a subtype, like TEL. For this purpose, the special class name "<code>value</code>" is introduced to excerpt out the subset of the element that is the value of the property. E.g. here is an hCard fragment for marking up a home phone number:

<pre><nowiki>
<span class="tel">
<span class="type">home</span>:
<span class="value">+1.415.555.1212</span>
</span>
</nowiki></pre>

This hCard fragment could be displayed as:

home: +1.415.555.1212

=== Property Exceptions ===

vCard has several properties which either do not make sense on, or are already implied within the context of a web page. This section explains what to (not) do with them.

# '''NAME''', '''PROFILE''', '''SOURCE''', '''PRODID''', '''VERSION''' properties as defined in Sections 2.1.2, 2.1.3, 2.1.4, 3.6.3, 3.6.9 of RFC 2426. Content publishers MUST NOT use these properties in their hCards, and as such, hCard consumers/parsers MUST IGNORE these properties if they are found within an hCard. Instead. hCard to vCard converters SHOULD use the title of the page where the hCard is found (e.g. the <code><title></code> element in (X)HTML documents) to construct the NAME property, MAY output a PROFILE value of "<code>VCARD</code>" per RFC 2426, SHOULD use the URL of the page where the hCard is found to construct the SOURCE property (e.g. perhaps as a parameter to a URL/service that converts hCards to vCards), for an output vCard stream (e.g. a .vcf file). Only services/applications that output actual vCards should write the PRODID property, with the product identifier for said service/application. Similarly only such services/applications should write the VERSION property, with the value "3.0" (without quotes) per RFC2426 Section 3.6.9.

=== Implied "N" Optimization ===

Although vCard requires that the "N" property be present, the authors of the vCard specification (RFC 2426) themselves do not include "N" properties in their vCards near the end of the spec (p.38). This apparent contradiction can be resolved by simply allowing the "FN" property to imply "N" property values in typical cases provided in the spec. We do so explicitly in hCard.

If the value of the "FN" property is exactly two words (separated by whitespace.), and there is no explicit "N" property, then the "N" property is inferred from the "FN" property. For "FN"s with either one word or three or more, then the author MUST explicitly markup the "N", except for the organization contact info case, [http://microformats.org/wiki/hcard#Organization_Contact_Info see below] for that.

# The content of "FN" is broken into two "words" separated by whitespace.
# The ''first'' word of the "FN" is interpreted as the "Given Name" for the "N" property.
# The ''second/last'' word of the "FN" is interpreted as the "Family Name" for the "N" property.
# Exception: If the first word ends in a "," comma OR if the second word is a single character (optionally followed by a period "."), then the first word (minus the comma at the end if any) is interpreted as the "Family Name" and the second word is interpreted as the "Given Name".

This allows simplification in the typical case of people stating their firstname space lastname, or lastname comma firstname, or lastname comma firstinitial, or lastname space firstinitial.

==== Organization Contact Info ====

Contact info for a company or organization is a special case of the implied "N" optimization.

If the "FN" and "ORG" properties have the exact same value (typically because they are set on the same element, e.g. class="fn org"), then the hCard represents contact information for a company or organization and should be treated as such. In this case the author MUST also NOT set the "N" property, or set it (and any sub-properties) explicitly to the empty string "". Thus parsers should handle the missing "N" property in this case by implying empty values for all the "N" sub-properties.

=== Implied "organization-name" Optimization ===

The "ORG" property has two subproperties, organization-name and organization-unit. Very often authors only publish the organization-name. Thus if an "ORG" property has no "organization-name" inside it, then its entire contents MUST be treated as the "organization-name".

=== Root Class Name ===

The root class name for an hCard is "vcard".

=== Property List ===

This is the list of properties (and subproperties, in parantheses, like this) in hCard, taken from vCard:

* fn, n (family-name, given-name, additional-name, honorific-prefix, honorific-suffix, nickname), sort-string
* url, email (type), tel (type)
* adr (post-office-box, extended-address, street-address, locality, region, postal-code, country-name, type), label
* geo (latitude, longitude), tz
* photo, logo, sound, bday
* title, role, org (organization-name, organization-unit)
* category, note
* class, key, mailer, uid, rev

=== XMDP Profile ===

See [[hcard-profile]] for the [http://gmpg.org/xmdp XMDP] profile of hCard which contains the above complete list of properties, with references to their RFC 2426 definitions.

=== Parsing Details ===

See [[hcard-parsing|hCard parsing]].

== Examples ==

This section is informative.

=== Sample vCard ===

Here is a sample vCard:

<pre><nowiki>
BEGIN:VCARD
VERSION:3.0
N:Çelik;Tantek
FN:Tantek Çelik
URL:http://tantek.com
ORG:Technorati
END:VCARD
</nowiki></pre>

and an equivalent in hCard with various elements optimized appropriately. See [[hcard-example1-steps| hCard Example 1]] for the derivation.

<pre><nowiki>
<div class="vcard">
<a class="url fn" href="http://tantek.com/">
Tantek Çelik
</a>
<div class="org">Technorati</div>
</div>
</nowiki></pre>

This hCard might be displayed as::

[http://tantek.com/ Tantek Çelik]<br />
Technorati

Note: The version information is unnecessary in hCard markup directly since the version will be defined by the profile of hCard that is used/referred to in the 'profile' attribute of the <head> element.

=== More Examples ===

See [[hcard-examples]] for more examples, including all examples from vCard RFC 2426 converted into hCard.

== Examples in the wild ==
This section is '''informative'''.

The following sites have published hCards, and thus are a great place to start for anyone looking for examples "in the wild" to try parsing, indexing, organizing etc. If you have an hCard on your own page, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.

* [http://chrischerry.name/blog/contact/ Chris Cherry's contact page with his hCard]
* [http://tagcamp.org/index.cgi?ContactList TagCamp contact list]
* [http://landsbank.fo/#hCard Landsbanki Føroya]
* [http://www.iowamilitaryveteransband.com/members/ Iowa Military Veterans Band Contacts] - 95 hCards [http://weblog.randomchaos.com/archive/2005/10/24/Microformats/ marked up by Scott Reynen]
* [http://rbach.priv.at/Contact Robert Bachmann] has published his hCard and [http://rbach.priv.at/Images/hcard a button].
* The good ship [http://styrheim.com/test/leonid.html Leonid Miloslavskiy] spotted in the North Atlantic
** INVALID --[[User:RyanKing|RyanKing]] 00:50, 27 Oct 2005 (PDT)
*** class="family" should probably be family-name
*** the "n" property is missing and the "n" optimization can't be applied
*** the first geo propery is empty, the second one is invalid (ie, it doesn't contain lat/long)

* [http://tantek.com/microformats/2005/web2/speakers.html Web 2.0 Conference speakers page marked up with hCard]

* [http://www.ndunn.com Neil Dunn] has published his rather [http://www.ndunn.com/2005/10/7/hCard good looking hCard]

* [http://we05.com/ Web Essentials 05] marked up all their [http://we05.com/presenters.cfm presenters with hCard].
* [http://twinsparc.com/ Twinsparc] put an hCard in the header and footer of all their pages.
** (2005-09-27) No FN and no ORG properties
** (2005-10-07) Fixed

* [http://www.oliverbrown.me.uk/ Oliver Brown] has published his hCard.
** (2005-09-27) PASSED

* [http://suda.co.uk/ Brian Suda] has managed to embed a photo in his hCard through the [http://www.ietf.org/rfc/rfc2397.txt data uri scheme] by converting the image to BASE64 code. View the Source to see how this is accomplished. [http://suda.co.uk/projects/X2V/get-vcard.php?uri=http%3A//suda.co.uk/contact/ The X2V link] will extract the image and encode it for a vCard which will be displayed in some address book applications.

* [http://www.efas.fupl.asso.fr/efas/_Mathieu-Drouet_.html Mathieu Drouet] and [http://www.efas.fupl.asso.fr/efas/_Annie-Leger_.html Annie Leger] both have hCards
** (2005-09-27) PASSED, PASSED

* [http://www.paulmichaelsmith.com/blog/hcard.htm Paul Smith] has created an hCard page which is Human Readable, and a link to X2V passing the same hCard page to generate a vCard.
** (2005-09-27) PASSED

* [http://loadaveragezero.com/hnav/contact.php Douglas W. Clifton] added all types of contact information
** (2005-09-27) PASSED

* [http://kinrowan.net/ Cori Schlegel] [http://kinrowan.net/blog/wp/archives/2005/07/08/a-problem-with-the-structured-blogging-plug-in-for-wordpress/ discusses how he has updated] [http://kinrowan.net/blog/contact his contact page with hCard]
* [http://thoughtport.blogspot.com/ Aiden Kenny] hasn't published his hCard yet, but he has [http://thoughtport.blogspot.com/2005/07/elemental-particles-of-web.html published his hCard icon]: http://photos1.blogger.com/blogger/4224/444/320/AK-Hcard-icon.gif
* [http://home.alltel.net/jackwolfgang/blog/ Jack L. Wolfgang II] has [http://home.alltel.net/jackwolfgang/blog/2005/07/hcard-posts-corrected.html posted his hCard on his blog] and [http://home.alltel.net/jackwolfgang/resume/ converted the addresses in his resume to hCards].
** resume doesn't seem to be well-formed
** (2005-09-27) EMAIL and Additional-names problem

* [http://www.kerihenare.com/ Keri Henare] has marked up his [http://www.kerihenare.com/contact/ contact info page] with hCard.
** (2005-09-27) PASSED
** (2005-11-01) hCard completely rewritten

* [http://www.windley.com/archives/2005/07/hcards_trying_o.shtml Phil Windley has published] [http://phil.windley.org/hcard.html his hCard].
** (2005-09-27) PASSED

* Cori Schlegel has published a full hCard on his [http://kinrowan.net/contact contact page] and an abbreviated version (linked to the full version) in the sidebar of his [http://kinrowan.net blog].
* [http://cinematreasures.org Cinema Treasures] uses hCard to markup venue information for 10,000+ movie theaters.
* [http://thedredge.org Andy Hume] uses the hcard format to mark-up the names and URLs of commentors on his blog.
* [http://www.wolfsreign.com Steven Ametjan] has published his hCard on [http://www.wolfsreign.com/about/ his about page].
** (2005-09-27) PASSED

* [http://evdb.com EVDB], the Events and Venues Database, publishes all venue detail pages with embedded hCards.
* [http://paulschreiber.com/blog/ Paul Schreiber]'s [http://concerts.shrub.ca/ Sunnyvale House Concerts] site publishes hCards for upcoming artists, as well as an hCard for the page itself. In addition the [http://concerts.shrub.ca/shows Past Shows] page contains hCards for all past artists.
** (2005-09-27) PASSED

* [http://zooibaai.nl/ Rob Mientjes] has published his hCard on [http://zooibaai.nl/about/ his about page].
** (2005-09-27) PASSED

* [http://gbraad.nl/ Gerard Braad] has published an example on his [http://gbraad.nl/site/?p=profile profile] page that is almost consistent with his original [http://gbraad.nl/files/gbraad.vcf vCard] file. Also progress is made for transforming his [http://files.gbraad.nl/foaf.rdf FoaF] file to a hCard encoded representation. (also done for my spouse:[http://spouse.gbraad.nl/site/?p=profile Yong Yuan])
** (2005-09-27) PASSED, PASSED

* [http://doncrowley.blogspot.com/ Don Crowley] has published [http://www.crowley.nl/hcard.html his hCard] as well as a nifty hCard button: http://www.crowley.nl/images/hcard.png
** (2005-09-27) PASSED

* [http://technorati.com/ Technorati]'s [http://www.technorati.com/about/ About page] lists their '''Media Contact'''
** (2005-09-27) PASSED

* [http://tantek.com/log Tantek's Thoughts] includes an inline author hCard at the bottom of the page.

* Paul Schreiber has published his hCard on [http://paulschreiber.com/about/?contact his about page].
* Scott Reynen has published his hCard on [http://www.randomchaos.com/document.php?source=scott_reynen his profile page].
* [http://www.w3.org/People/Connolly/events/ Dan Connolly's index of events and talks] has hCards for many of the people he has met at those events.

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

The following implementations have been developed which either generate or parse hCards. If you have an hCard implementation, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.

* There is [http://tagcamp.org/index.cgi?ContactList evidence of a kwiki plugin for hCards].
* [http://suda.co.uk/projects/X2V/ X2V] is a bookmarklet that parses hCard and produces a .vcf (vCard) stream. Note: needs to be updated as the spec is refined
* [http://www.stripytshirt.co.uk Duncan Walker] has built [http://www.stripytshirt.co.uk/features/firefox/smartzilla a Firefox extension] that gets hCard data from a webpage, uses Brian Suda's XSL (locally) to transform it to vcard format and opens the resulting .vcf file.
* [http://george.hotelling.net/90percent/ George] has written a [http://george.hotelling.net/90percent/geekery/greasemonkey_and_microformats.php Greasemonkey user script] that detects hCards and allows users to easily add them to their address book application. Relies on the X2V web service to do the conversion.
* [http://blogmatrix.blogmatrix.com/ David Janes] has written a [[Greasemonkey]] [http://www.blogmatrix.com/include/microformat-find.user.js script] that finds many microformat elements, including hCards, and [http://blog.davidjanes.com/mtarchives/2005_08.html#003376 provides a popup menu of actions]. The hCard to vCard conversion is done internally within the script.
* [http://diveintomark.org/ Mark Pilgrim] has also written an [http://diveintomark.org/projects/greasemonkey/hcard/ hCard parser Greasemonkey user script]. It is self-contained and does not rely on the X2V web service.
* [http://www.oliverbrown.me.uk/2005/09/03/a-working-microformats-extension-to-simplexml/ Oliver Brown] has written an "extension" to [http://www.php.net/simplexml SimpleXML] that gives simple access to hCard information in PHP 5.
* [http://thedredge.org/ Andrew D. Hume] has built a system (Wordpress plugin?) for [http://thedredge.org/2005/06/using-hcards-in-your-blog/ using hcards in your blog] to represent people leaving comments on blog posts.
* The [http://tantek.com/microformats/hcard-creator.html hCard creator] is a very simple, yet illustrative, open source user interface / form / script which creates an hCard in real-time as you type in a set of contact information.
* [http://greenbytes.de/tech/webdav/rfc2629.xslt rfc2629.xslt] now attempts to generate hCard information ([http://ietf.org/rfc/rfc2629 RFC2629] is an XML format for authoring RFCs and Internet Drafts, see [http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html example document])
* [http://tantek.com/microformats/buddylist2hcards.html iChat buddy list to hCards] - Open source AppleScript to automatically convert one's buddy list in the MacOSX iChat AIM client into a valid XHTML 1.0 Strict list of hCards.
* [http://dev.w3.org/cvsweb/2001/palmagent/ palmagent] is a collection of palmpilot and sidekick tools. It includes X2V derivatives xhtml2hcard.xsl and toICal.xsl plus some [http://dev.w3.org/cvsweb/2001/palmagent/hcardTest.html hcardTest] materials
* [http://www.openpsa.org/ OpenPsa 2.x] CRM application uses hCard for all person listings. The widget is [http://www.midgard-project.org/midcom-permalink-922834501b71daad856f35ec593c7a6d reusable across Midgard CMS]

== References ==
=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://www.ietf.org/rfc/rfc2426.txt vCard RFC2426]

=== Informative References ===
* [http://www.w3.org/2002/12/cal/rfc2426 HTML reformatted version of RFC2426]
* [http://w3.org/TR/REC-CSS1 CSS1]
* [http://tantek.com/log/2004/09.html#hcard hCard term introduced and defined on the Web, 20040930]
* [http://wiki.oreillynet.com/foocamp04/index.cgi?SimpleSemanticFormats FOO Camp 2004 Simple Semantic Formats presentation, 20040910]
* Contributed from http://developers.technorati.com/wiki/hCard.
* [http://www.w3.org/TR/xhtml11 XHTML 1.1]

==== Specifications That Use hCard ====
* [[adr]]
* [[geo]]
* [[hcalendar|hCalendar]]
* [[hreview|hReview]]

==== Similar Work ====
* [http://www.intertwingly.net/wiki/pie/PaceBetterPersonElement Atom PaceBetterPersonElement]
* [http://www.jabber.org/jeps/jep-0054.html JEP-0054: vcard-temp]

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. There is a separate document where we are keeping our brainstorms and other explorations relating to hCard:

* [[hcard-brainstorming|hCard Brainstorming]]
* [[hcard-tests|hCard tests]]

== Discussions ==

* See [http://www.technorati.com/cosmos/referer.html blogs discussing this page].

=== Q&A ===
* If you have any questions about hCard, check the [[hcard-faq|hCard FAQ]], and if you don't find answers, add your questions!

=== Issues ===
* Please add any issues with the specification to the separate [[hcard-issues|hCard issues]] document.

hcalendar-examples

2005-11-10T23:51:30Z

DanC: attendee markup looks incomplete

= hCalendar examples =

Example [[hcalendar|hCalendars]].

== Authors ==
* [http://diveintomark.org/ Mark Pilgrim]
* [http://theryanking.com/ Ryan King]
* [http://tantek.com/log/ Tantek Çelik]

== RFC 2445 examples in hCalendar ==
These are 1:1 hCalendar examples for each example in RFC 2445.

Errata applied from [http://www.rfc-editor.org/cgi-bin/errata.pl#rfc2445 here].

=== 4.6.1 Event Component ===
The following is an example of the "VEVENT" calendar component used to represent a meeting that will also be opaque to searches for busy time:

<pre><nowiki>
BEGIN:VEVENT
UID:19970901T130000Z-123401@host.com
DTSTAMP:19970901T1300Z
DTSTART:19970903T163000Z
DTEND:19970903T190000Z
SUMMARY:Annual Employee Review
CLASS:PRIVATE
CATEGORIES:BUSINESS,HUMAN RESOURCES
END:VEVENT
</nowiki></pre>

This iCalendar event as an hCalendar:

<pre><nowiki>
<div class="vevent">
<h5 class="summary">Annual Employee Review</h5>
<div>posted on <abbr class="dtstamp" title="19970901T1300Z">September 1, 1997</abbr></div>
<div>UID: <span class="uid">19970901T130000Z-123401@host.com</span></div>
<div>Dates: <abbr class="dtstart" title="19970903T163000Z">Septempter 3, 1997, 16:30</abbr> -
<abbr class="dtend" title="19970903T190000Z">19:00 UTC</abbr></div>
<div>This meeting is <strong class="class">private</strong>.</div>
<div>Filed under:</div>
<ul>
<li class="category">Business</li>
<li class="category">Human Resources</li>
</ul>
</div>
</nowiki></pre>

This hCalendar could be displayed as:
<div class="vevent">

<h5 class="summary">Annual Employee Review</h5>
<div>posted on <abbr class="dtstamp" title="19970901T1300Z">September 1, 1997</abbr></div>
<div>UID: <span class="uid">19970901T130000Z-123401@host.com</span></div>
<div>Dates: <abbr class="dtstart" title="19970903T163000Z">Septempter 3, 1997, 16:30</abbr> - <abbr class="dtend" title="19970903T190000Z">19:00 UTC</abbr></div>
<div>This meeting is <strong class="class">Private</strong>.</div>
<div>Filed under:</div>
<ul>
<li class="category">Business</li>
<li class="category">Human Resources</li>
</ul>
</div>

==== Example 2 ====
The following is an example of the "VEVENT" calendar component used to represent a reminder that will not be opaque, but rather transparent, to searches for busy time:

<pre><nowiki>
BEGIN:VEVENT
UID:19970901T130000Z-123402@host.com
DTSTAMP:19970901T1300Z
DTSTART:19970401T163000Z
DTEND:19970402T010000Z
SUMMARY:Laurel is in sensitivity awareness class.
CLASS:PUBLIC
CATEGORIES:BUSINESS,HUMAN RESOURCES
TRANSP:TRANSPARENT
END:VEVENT
</nowiki></pre>

This iCalendar event as an hCalendar fragment:

<pre><nowiki>
<div class="vevent">
<h5 class="summary">Laurel is in sensitivity awareness class.</h5>
<div>Posted on: <abbr class="dtstamp" title="19970901T1300Z">September 1, 1997</abbr></div>
<div class="uid">19970901T130000Z-123402@host.com</div>
<div>Dates: <abbr class="dtstart" title="19970401T163000Z">April 1, 1997, 16:30 UTC</abbr>-
<abbr class="dtend" title="19970402T010000Z">April 2, 1997 01:00 UTC</abbr></div>
<div>This event is <span class="class">public</span> and <span class="transp">transparent</span> to free/busy scheduling.</div>
<div>Filed under:</div>
<ul>
<li class="category">Business</li>
<li class="category">Human Resources</li>
</ul>
</div>
</nowiki></pre>

This hCalendar could be displayed as:

<div class="vevent">
<h5 class="summary">Laurel is in sensitivity awareness class.</h5>
<div>Posted on: <abbr class="dtstamp" title="19970901T1300Z">September 1, 1997</abbr></div>
<div class="uid">19970901T130000Z-123402@host.com</div>
<div>Dates: <abbr class="dtstart" title="19970401T163000Z">April 1, 1997, 16:30 UTC</abbr>-<abbr class="dtend" title="19970402T010000Z">April 2, 1997 01:00 UTC</abbr></div>
<div>This event is <span class="class">public</span> and <span class="transp">transparent</span> to free/busy scheduling.</div>
<div>Filed under:</div>
<ul>
<li class="category">Business</li>
<li class="category">Human Resources</li>
</ul>
</div>

==== Example 3 ====

The following is an example of the "VEVENT" calendar component used to represent an anniversary that will occur annually. Since it takes up no time, it will not appear as opaque in a search for busy time; no matter what the value of the "TRANSP" property indicates:

<pre><nowiki>
BEGIN:VEVENT
UID:19970901T130000Z-123403@host.com
DTSTAMP:19970901T1300Z
DTSTART:19971102
SUMMARY:Our Blissful Anniversary
CLASS:CONFIDENTIAL
CATEGORIES:ANNIVERSARY,PERSONAL,SPECIAL OCCASION
RRULE:FREQ=YEARLY
END:VEVENT
</nowiki></pre>

This iCalendar event as an hCalendar fragment:

<pre><nowiki>
<div class="vevent">
<h5 class="summary">Our Blissful Anniversary</h5>
<div>Posted on: <abbr class="dtstamp" title="19970901T1300Z">September 1, 1997</abbr></div>
<div class="uid">19970901T130000Z-123403@host.com</div>
<div>Date: <abbr class="dtstart" title="19971102">November 2, 1997</abbr></div>
<div>This event is <strong class="class">confidential</stong>.</div>
<div>Filed under:</div>
<ul>
<li class="category">Anniversary</li>
<li class="category">PersonaL</li>
<li class="category">Special Occassion</li>
</ul>
<div class="rrule">Repeat <span class="freq">yearly</span>.</div>
</div>
</nowiki></pre>

ISSUES:
* We have a larger discusion about RRULE that needs to be resolved, hopefully these examples will help that. --RyanKing

This hCalendar could be displayed as:

<div class="vevent">
<h5 class="summary">Our Blissful Anniversary</h5>
<div>Posted on: <abbr class="dtstamp" title="19970901T1300Z">September 1, 1997</abbr></div>
<div class="uid">19970901T130000Z-123403@host.com</div>
<div>Date: <abbr class="dtstart" title="19971102">November 2, 1997</abbr></div>
<div>This event is <span class="class">confidential</span>.</div>
<div>Filed under:</div>
<ul>
<li class="category">Anniversary</li>
<li class="category">Personal</li>
<li class="category">Special Occassion</li>
</ul>
<div class="rrule">Repeat <span class="freq">yearly</span></div>
</div>

=== 5. iCalendar Object Examples ===

The following example specifies a three-day conference that begins at 8:00 AM EDT, September 18, 1996 and end at 6:00 PM EDT, September 20, 1996.

<pre><nowiki>
BEGIN:VEVENT
DTSTAMP:19960704T120000Z
UID:uid1@host.com
ORGANIZER:MAILTO:jsmith@host.com
DTSTART:19960918T143000Z
DTEND:19960920T220000Z
STATUS:CONFIRMED
CATEGORIES:CONFERENCE
SUMMARY:Networld+Interop Conference
DESCRIPTION:Networld+Interop Conference and Exhibit\nAtlanta World Congress Center\nAtlant\, Georgia
END:VEVENT
</nowiki></pre>

This iCalendar event as an hCalendar fragment: ''the attendee markup looks incomplete''

<pre><nowiki>
<div class="vevent">
<h5 class="summary">Networld+Interop Conference</h5>
<div class="description">Networld+Interop Conference and Exhibit Atlanta World Congress
Center Atlanta, Georgia</div>
<div>Posted on: <abbr class="dtstamp" title="19960704T120000Z">July 4, 1996</abbr></div>
<div class="uid">uid1@host.com</div>
<div>Organized by: <a class="organizer" href="mailto:jsmith@host.com">jsmith@host.com</a></div>
<div>Dates: <abbr class="dtstart" title="19960918T143000Z">September 18, 1996, 14:30 UTC</abbr> -
<abbr class="dtend" title="19960920T220000Z">September 20, 1996, 22:00 UTC</abbr></div>
<div>Status: <span class="status">CONFIRMED</span></div>
<div>Filed under:</div>
<ul class="categories">
<li>Conference</li>
</ul>
</div>
</nowiki></pre>

This hCalendar could be displayed as:

<div class="vevent">
<h5 class="summary">Networld+Interop Conference</h5>
<div class="description">Networld+Interop Conference and Exhibit Atlanta World Congress
Center Atlanta, Georgia</div>
<div>Posted on: <abbr class="dtstamp" title="19960704T120000Z">July 4, 1996</abbr></div>
<div class="uid">uid1@host.com</div>
<div>Organized by: [mailto:jsmith@host.com jsmith@host.com]</div>
<div>Dates: <abbr class="dtstart" title="19960918T143000Z">September 18, 1996, 14:30 UTC</abbr> -
<abbr class="dtend" title="19960920T220000Z">September 20, 1996, 22:00 UTC</abbr></div>
<div>Status: <span class="status">confirmed</span></div>
<div>Filed under:</div>
<ul class="categories">
<li>Conference</li>
</ul>
</div>

==== Example 2 ====
The following example specifies a group scheduled meeting that begin at 8:30 AM EST on March 12, 1998 and end at 9:30 AM EST on March 12, 1998. The "Organizer" has scheduled the meeting with one or more calendar users in a group. A time zone specification for Eastern United States has been specified.

<pre><nowiki>
BEGIN:VCALENDAR
PRODID:-//RDU Software//NONSGML HandCal//EN
VERSION:2.0
BEGIN:VTIMEZONE
TZID:US-Eastern
BEGIN:STANDARD
DTSTART:19981025T020000
RDATE:19981025T020000
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:19990404T020000
RDATE:19990404T020000
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
DTSTAMP:19980309T231000Z
UID:guid-1.host1.com
ORGANIZER;ROLE=CHAIR:MAILTO:mrbig@host.com
ATTENDEE;RSVP=TRUE;ROLE=REQ-PARTICIPANT;CUTYPE=GROUP:MAILTO:employee-A@host.com
DESCRIPTION:Project XYZ Review Meeting
CATEGORIES:MEETING
CLASS:PUBLIC
CREATED:19980309T130000Z
SUMMARY:XYZ Project Review
DTSTART;TZID=US-Eastern:19980312T083000
DTEND;TZID=US-Eastern:19980312T093000
LOCATION:1CP Conference Room 4350
END:VEVENT
END:VCALENDAR
</nowiki></pre>

This iCalendar as an hCalendar:

<pre><nowiki>
@TODO
</nowiki></pre>

This hCalendar could be displayed as:

@TODO

==== Example 3 ====
<pre><nowiki>
BEGIN:VCALENDAR
METHOD:xyz
VERSION:2.0
PRODID:-//ABC Corporation//NONSGML My Product//EN
BEGIN:VEVENT
DTSTAMP:19970324T1200Z
SEQUENCE:0
UID:uid3@host1.com
ORGANIZER:MAILTO:jdoe@host1.com
ATTENDEE;RSVP=TRUE:MAILTO:jsmith@host1.com
DTSTART:19970324T123000Z
DTEND:19970324T210000Z
CATEGORIES:MEETING,PROJECT
CLASS:PUBLIC
SUMMARY:Calendaring Interoperability Planning Meeting
DESCRIPTION:Discuss how we can test c&s interoperability\nusing iCalendar and other IETF standards.
LOCATION:LDB Lobby
ATTACH;FMTTYPE=application/postscript:ftp://xyzCorp.com/pub/conf/bkgrnd.ps
END:VEVENT
END:VCALENDAR
</nowiki></pre>

This iCalendar as an hCalendar:

<pre><nowiki>
<div class="vcalendar">
<div>Method: <span class="method">xyz</span></div>
<div class="vevent">
<div>Posted at: <span class="dtstamp">19970324T1200Z</span></div>
<div>Sequence: <span class="sequence">0</span></div>
<div>UID: <span class="uid">uid3@host1.com</span></div>
<div>Organzied by: <a class="organizer" href="mailto:jdoe@host1.com">jdoe@host1.com</a></div>
<div>Attending: <span class="attendee"><a class="value" href="mailto:jsmith@host1.com">jsmith@host1.com</a> RSVPed? <span class="rsvp">TRUE></span></span></div>
<div>Start Time: <abbr class="dtstart" title="19970324T123000Z">March 24, 1997 12:30 UTC</abbr></div>
<div>End Time: <abbr class="dtend" title="19970324T210000Z">March 24, 1997, 21:00 UTC</abbr></div>
<ul class="categories">
<li>Meeting</li>
<li>Project</li>
</ul>
<div>This event is <strong class="class">Public</strong></div>
<div class="summary">Calendaring Interoperability Planning Meeting</div>
<div class="description">Discuss how we can test c&s interoperability using iCalendar and other IETF standards.</div>
<div class="location">LDB Lobby</div>
<div>Attachment: <a class="attach" type="application/postscript" href="ftp://xyzCorp.com/pub/conf/bkgrnd.ps">ftp://xyzCorp.com/pub/conf/bkgrnd.ps</a></div>
</div>
</div>
</nowiki></pre>

This hCalendar could be displayed as:

<div class="vcalendar">
<div>Method: <span class="method">xyz</span></div>
<div class="vevent">
<div>Posted at: <span class="dtstamp">19970324T1200Z</span></div>
<div>Sequence: <span class="sequence">0</span></div>
<div>UID: <span class="uid">uid3@host1.com</span></div>
<div>Organzied by: [mailto:jdoe@host1.com jdoe@host1.com]</div>
<div>Attending: <span class="attendee">[mailto:jsmith@host1.com jsmith@host1.com], RSVPed? <span class="rsvp">TRUE></span></span></div>
<div>Start Time: <abbr class="dtstart" title="19970324T123000Z">March 24, 1997 12:30 UTC</abbr></div>
<div>End Time: <abbr class="dtend" title="19970324T210000Z">March 24, 1997, 21:00 UTC</abbr></div>
<ul class="categories">
<li>Meeting</li>
<li>Project</li>
</ul>
<div>This event is <strong class="class">Public</strong></div>
<div class="summary">Calendaring Interoperability Planning Meeting</div>
<div class="description">Discuss how we can test c&s interoperability using iCalendar and other IETF standards.</div>
<div class="location">LDB Lobby</div>
<div>Attachment: <a class="attach" type="application/postscript" href="ftp://xyzCorp.com/pub/conf/bkgrnd.ps">ftp://xyzCorp.com/pub/conf/bkgrnd.ps</a></div>
</div>
</div>

==== Example 4 ====

The following is an example of a to-do due on April 15, 1998. An audio alarm has been specified to remind the calendar user at noon, the day before the to-do is expected to be completed and repeat hourly, four additional times. The to-do definition has been modified twice since it was initially created.

<pre><nowiki>
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//ABC Corporation//NONSGML My Product//EN
BEGIN:VTODO
DTSTAMP:19980130T134500Z
SEQUENCE:2
UID:uid4@host1.com
ORGANIZER:MAILTO:unclesam@us.gov
ATTENDEE;PARTSTAT=ACCEPTED:MAILTO:jqpublic@host.com
DUE:19980415T235959
STATUS:NEEDS-ACTION
SUMMARY:Submit Income Taxes
BEGIN:VALARM
ACTION:AUDIO
TRIGGER:19980403T120000
ATTACH;FMTTYPE=audio/basic:http://host.com/pub/audio-files/ssbanner.aud
REPEAT:4
DURATION:PT1H
END:VALARM
END:VTODO
END:VCALENDAR
</nowiki></pre>

This iCalendar as an hCalendar:

<pre><nowiki>
<div class="vcalendar">
<div class="vtodo">
<div>Posted at: <span class="dtstamp">19980130T134500Z</span></div>
<div>Sequence <span class="sequence">2</span></div>
<div>UID: <span class="uid">uid4@host1.com</span></div>
<div>Organizer: [mailto:unclesam@us.gov unclesam@us.gov]</div>
<div>Attending: [mailto:jqpublic@host.com jqpublic@host.com], <span class="partstat">ACCEPTED</span></span></div>
<div>Due: <abbr class="due" title="19980415T235959">one minute before midnight on April 15, 1998</abbr></div>
<div>Status: <span class="status">needs-action</span></div>
<div class="summary">Submit Income Taxes</div>
<div class="valarm">
<div>Action: <span class="action">AUDIO</span></div>
<div>Trigger: <span class="trigger">19980403T120000</span></div>
<div>Attachment: <a class="attach" type="audio/basic" href="http://host.com/pub/audio-files/ssbanner.aud">http://host.com/pub/audio-files/ssbanner.aud</a></div>
<div>Repeat: <span class="repeat">4</span></div>
<div>Duration: <span class="duration">PT1H</span></div>
</div>
</div>
</div>
</nowiki></pre>

This hCalendar could be displayed as:

<div class="vcalendar">
<div class="vtodo">
<div>Posted at: <span class="dtstamp">19980130T134500Z</span></div>
<div>Sequence <span class="sequence">2</span></div>
<div>UID: <span class="uid">uid4@host1.com</span></div>
<div>Organizer: [mailto:unclesam@us.gov unclesam@us.gov]</div>
<div>Attending: [mailto:jqpublic@host.com jqpublic@host.com], <span class="partstat">ACCEPTED</span></span></div>
<div>Due: <abbr class="due" title="19980415T235959">one minute before midnight on April 15, 1998</abbr></div>
<div>Status: <span class="status">needs-action</span></div>
<div class="summary">Submit Income Taxes</div>
<div class="valarm">
<div>Action: <span class="action">AUDIO</span></div>
<div>Trigger: <span class="trigger">19980403T120000</span></div>
<div>Attachment: [http://host.com/pub/audio-files/ssbanner.aud http://host.com/pub/audio-files/ssbanner.aud]</div>
<div>Repeat: <span class="repeat">4</span></div>
<div>Duration: <span class="duration">PT1H</span></div>
</div>
</div>
</div>

==== Example 5: journal entry ====
The following is an example of a journal entry.

<pre><nowiki>
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//ABC Corporation//NONSGML My Product//EN
BEGIN:VJOURNAL
DTSTAMP:19970324T120000Z
UID:uid5@host1.com
ORGANIZER:MAILTO:jsmith@host.com
STATUS:DRAFT
CLASS:PUBLIC
CATEGORY:Project Report, XYZ, Weekly Meeting
DESCRIPTION:Project xyz Review Meeting Minutes\nAgenda\n
1. Review of project version 1.0 requirements.\n
2. Definition of project processes.\n
3. Review of project schedule.\nParticipants: John Smith, Jane Doe, Jim Dandy\n
-It was decided that the requirements need to be signed off by product marketing.\n
-Project processes were accepted.\n
-Project schedule needs to account for scheduled holidays and employee vacation time. Check with HR for specific dates.\n
-New schedule will be distributed by Friday.\n
-Next weeks meeting is cancelled. No meeting until 3/23.
END:VJOURNAL
END:VCALENDAR
</nowiki></pre>

(*note*: line-breaks have been added into the description, in reality it should be one line)

This iCalendar as an hCalendar:

<pre><nowiki>
<div class="vcalendar">
<div class="vjournal">
<div>Posted at: <abbr class="dtstamp" title="19970324T120000Z">March 24, 1997, 12:00 UTC</abbr></div>
<div class="uid">uid5@host1.com</div>
<div>Organizer: <a class="organizer" href="mailto:jsmith@host.com">jsmith@host.com</a></div>
<div>Status: <span class="status">Draft</span></div>
<div>This journal is<span class="class">Public</span>.</div>
<div>Filed under:</div>
<ul class="category">
<li>Project Report</li>
<li>xyz</li>
<li>Weekly Meeting</li>
</ul>
<div class="description">Project xyz Review Meeting Minutes<br />
Agenda<br />
1. Review of project version 1.0 requirements.<br />
2. Definition of project processes.<br />
3. Review of project schedule.<br />
Participants: John Smith, Jane Doe, Jim Dandy<br />
-It was decided that the requirements need to be signed off by product marketing.<br />
-Project processes were accepted.<br />
-Project schedule needs to account for scheduled holidays and employee vacation time. Check with HR for specific dates.<br />
-New schedule will be distributed by Friday.<br />
-Next weeks meeting is cancelled. No meeting until 3/23.
</div>
</div>
</div>
</nowiki></pre>

This hCalendar could be displayed as:

<div class="vcalendar">
<div class="vjournal">
<div>Posted at: <abbr class="dtstamp" title="19970324T120000Z">March 24, 1997, 12:00 UTC</abbr></div>
<div class="uid">uid5@host1.com</div>
<div>Organizer: [mailto:jsmith@host.com jsmith@host.com]</div>
<div>Status: <span class="status">Draft</span></div>
<div>This journal is<span class="class">Public</span>.</div>
<div>Filed under:</div>
<ul class="category">
<li>Project Report</li>
<li>xyz</li>
<li>Weekly Meeting</li>
</ul>
<div class="description">Project xyz Review Meeting Minutes<br />
Agenda<br />
1. Review of project version 1.0 requirements.<br />
2. Definition of project processes.<br />
3. Review of project schedule.<br />
Participants: John Smith, Jane Doe, Jim Dandy<br />
-It was decided that the requirements need to be signed off by product marketing.<br />
-Project processes were accepted.<br />
-Project schedule needs to account for scheduled holidays and employee vacation time. Check with HR for specific dates.<br />
-New schedule will be distributed by Friday.<br />
-Next weeks meeting is cancelled. No meeting until 3/23.
</div>
</div>
</div>

==== Example 6. Free/Busy time ====

The following is an example of published busy time information. The iCalendar object might be placed in the network resource www.host.com/calendar/busytime/jsmith.ifb.

<pre><nowiki>
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//RDU Software//NONSGML HandCal//EN
BEGIN:VFREEBUSY
ORGANIZER:MAILTO:jsmith@host.com
DTSTART:19980313T141711Z
DTEND:19980410T141711Z
FREEBUSY:19980314T233000Z/19980315T003000Z
FREEBUSY:19980316T153000Z/19980316T163000Z
FREEBUSY:19980318T030000Z/19980318T040000Z
URL:http://www.host.com/calendar/busytime/jsmith.ifb
END:VFREEBUSY
END:VCALENDAR
</nowiki></pre>

This iCalendar as an hCalendar:

<pre><nowiki>
<div class="vcalendar">
<div>Version: <span class="version">2.0</span></div>
<div>ProdID:<span class="prodid">-//RDU Software//NONSGML HandCal//EN</span></div>
<div class="vfreebusy">
<div>Organizer: <span class="organizer">:MAILTO:jsmith@host.com</span></div>
<div>Start Time: <abbr class="dtstart" title="19980313T141711Z">March 13, 1998 14:17:11 UTC</abbr></div>
<div>End time: <abbr class="dtend" title="19980410T141711Z">April 10, 1998 14:17:11 UTC</abbr></div>
<p>Busy times:</p> 
<ol>
<li class="freebusy"><abbr class="dtstart" title="19980314T233000Z">1998-03-14 23:30:00 UTC</abbr> - <abbr class="dtend" title="19980315T003000Z">1998-03-15- 00:30:00 UTC</abbr></li>
<li class="freebusy"><abbr class="dtstart" title="19980316T153000Z">1998-03-16 15:30:00 UTC</abbr> - <abbr class="dtend" title="19980316T163000Z">1998-03-16 16:30:00 UTC</abbr></li>
<li class="freebusy"><abbr class="dtstart" title="19980318T030000Z">1998-03-18 03:00:00 UTC</abbr> - <abbr class="dtend" title="19980318T040000Z">1998-03-18 04:00:00 UTC</abbr></li>
</ol>
<div>URL <a class="url" href="http://www.host.com/calendar/busytime/jsmith.ifb">http://www.host.com/calendar/busytime/jsmith.ifb</a></div>
</div>
</div>
</nowiki></pre>

This hCalendar could be displayed as:

@TODO

== Other ==

* See [[hcalendar-brainstorming]] for more examples (which may eventually be moved here) and analysis.

resume-examples

2005-11-10T21:12:45Z

DanC: joining the list

= Resume Examples =

== Experiments in microformatting ==
* [http://cs.usfca.edu/~rking/resume.html ryan king]
* [http://cs.usfca.edu/~rking/niall.html Niall Kennedy] (microformatted by RyanKing)
* [http://edward.oconnor.cx/resume/ Edward O'Connor]

== Resumes from the wild ==

* [http://tantek.com/projects/resume.html Tantek Çelik] (needs updating, this is about a year old)
* [http://www.w3.org/People/Connolly/misc/vita Dan Connolly] (needs elaboration for MIT purposes; has been GRDDL'd to some extent)

== See Also ==

* [[resume-formats]]
* [[resume-brainstorming]]

blog-post-formats

2005-10-25T21:21:39Z

DanC: /* An XHTML profile for RDF Site Summaries */

= Current Blog Formats =

There is a need for developing standard classes for blog posts (i.e. a microformat!).

This page serves to document the current list of individual blog post schemas, formats, and efforts as background for the design of a simple blog post MicroFormat.

== Discussion Participants ==

=== Editor ===
* [http://blog.factoryjoe.com/ Chris Messina], [http://flock.com Flock, Inc.]

=== Authors ===
* [http://blog.factoryjoe.com/ Chris Messina], [http://flock.com Flock, Inc.]
* [http://blogmatrix.blogmatrix.com/ David Janes], [http://www.blogmatrix BlogMatrix, Inc.]
* [http://www.geof.net/ Geof Glass]

=== Interested Folks ===
* [http://tantek.com/log/ Tantek Çelik], [http://technorati.com/ Technorati]
* [http://theryanking.com/blog/ Ryan King], [http://technorati.com/ Technorati]

== Tools ==

=== Blogger ===
* http://www.blogger.com/home

Blogger is one the earliest, best known and probably most widely used blogging platform. Blogger was bought by [http://www.google.com Google] in February of 2003. Blogger allows users to create and edit their own templates and also provides a large number of (more or less) attractive templates from which the user can select. Unfortunately, you must log into a blogger account to see the template selection.

Here are several Blogger templates, randomly selected from the presets. More recent templates seem to be converging on a vocabulary for identifying parts of posts. This may because they share an evolutionary history from a common template. I've included three examples here:

<pre><nowiki>
<body>
<div id="content">
<div id="main">
ENTRIES
</div>
</div>
</body>

<h2 class="date-header">POST DATE</h2>
<div class="post">
<a name="POST #"></a>
<h3 class="post-title">
<a href="POST URI" title="external link">POST TITLE</a>
</h3>
<p>POST CONTENT</p>
<p class="post-footer">
<em>posted by AUTHOR @ <a href="POST URI" title="permanent link">POST DATETIME</a></em>
</p>
</div>
</nowiki></pre>

<pre><nowiki>
<body>
<div id="main">
<div id="main2">
ENTRIES
</div>
</div>
</body>

<div class="post">
<a name="POST #"></a>
<h3 class="post-title">
<a href="sample_post.html" title="permanent link">POST TITLE</a>
</h3>
<div class="post-body">
POST CONTENT
</div>
<p class="post-footer">
<em>posted by AUTHOR @ <a href="POST URI" title="permanent link">POST TIME</a></em>
</p>
</div>
</nowiki></pre>

<pre><nowiki>
<body>
<div id="leftcontent">
ENTRIES
</div>
</body>

<div class="Post">
<a name="POST #"></a>
POST CONTENT
<span class="PostFooter">
<a href="POST URI">POST TIME</a>
</span>
</div>
</nowiki></pre>

==== Key CSS Elements ====
* newer templates seem to use "main" to identify a enclosure for all entries
* newer templates use "post" to identify a weblog entry
* newer templates use "post-title" to identify the entry's title
* beyond this there is little standardization

==== Template Concepts ====
* all posts
* an individual post
* post title
* post author
* post posting time
* post content
* post URI (permalink)

=== Blosxom===
* http://www.blosxom.com/
* http://pyblosxom.sourceforge.net/

=== Drupal ===
* http://drupal.org
* varies per theme

=== LiveJournal ===
* http://www.livejournal.com/

=== MovableType ===
* http://www.sixapart.com/movabletype/

MovableType is a perl-based blogging platform. Note that the MT is old and widely deployed and there are very many different variants on the templates in the wild.

The standard template for the weblog's main page (the "[http://www.sixapart.com/movabletype/default_templates#main_index main index]") has the following structure:

<pre><nowiki>
<body>
<div class="content">
<h2>DATE HEADER</h2>
<h3 id="a####">POST TITLE</h3>
POST CONTENT
[ OPTIONAL LINK TO MORE POST CONTENT ]
<p class="posted">Posted by AUTHOR at <a href="POST URI">POST DATE</a>
</div>
</div>

<div class="content">
<p align="right">
<h2>POST DATE</h2>
</p>
<h3>POST TITLE</h3>
POST CONTENT
<div id="more">
MORE POST CONTENT (optional)
</div>
<p class="posted">Posted by AUTHOR at DATE</p>
</div>
</nowiki></pre>

==== Key CSS Elements ====

* "content" can enclose an individual entry or all entries, depending on the context
* "h2" encloses the post date (literally: the time is not included)
* "h3" encloses the title
* there is no standard enclosure for all the content
* there is no clear identification of "here's all the entries"
* there is no clear identification of the post's author
* the permalink is not necessarily on the page anywhere

==== Template Concepts ====
* all posts
* an individual post
* post title
* post author
* post posting time
* post content, which includes the next two
* post content (first part)
* post content (expended part)
* post URI (permalink)

=== TypePad ===
* http://www.sixapart.com/typepad/

Typepad is a MovableType hosting service. It provides a list of [http://help.typepad.com/tags/default_templates.html default templates] and [ "template modules"] from which users can construct or modify their own templates. Looking at several Typepad blogs, most or all of them following the nomenclature and struct defined by these templates.

The standard structure is as follows:

<pre><nowiki>
<body class="layout-two-column-right">
<div id="container">
<div id="container-inner" class="pkg">
<div id="pagebody">
<div id="pagebody-inner" class="pkg">
<div id="alpha">
<div id="alpha-inner" class="pkg">
INDIVIDUAL ENTRY
</div>
</div>
</div>
</div>
</div>
</div>
</body>

<div class="entry" id="entry-#####">
<h3 class="entry-header">POST TITLE</h3>
<div class="entry-content">
<div class="entry-body">
POST CONTENT
</div>
<a id="more"></a>
<div class="entry-more">
MORE POST CONTENT
</div>
</div>
<p class="entry-footer">
POST FOOTER
</p>
</div>
</nowiki></pre>

I cannot seem to track down in the templates where the POST FOOTER is defined. However, we can see the results from a [http://www.bluedogbob.com/ sample blog]:

<pre><nowiki>
<span class="post-footers">Posted by AUTHOR_NAME in CATEGORY</span>
<span class="separator">|</span>
<a class="permalink" href="ENTRY_URI">Permalink</a>
| <a href="COMMENT_URI">Comments (2)</a>
| <a href="TRACKBACKS_URI">TrackBack (0)</a>
</nowiki></pre>

==== Key CSS Elements ====
* "entry" encloses all elements within an entry
* "entry-content" contains all the entry text, plus additional text saying "here's more"
* "entry-header" contains the title of the post
* "permalink" contains the post's URI
* there is no clear identification of "here's all the entries"
* there is no clear identification of the post's author

==== Template Concepts ====
* all posts
* an individual post
* post title
* post author
* post posting time
* post content, which includes the next two
* post content (first part)
* post content (expended part)
* post URI (permalink)

=== WordPress ===
* http://wordpress.org

WordPress is a popular GPLed blogging system based on PHP and MySQL. WordPress calls their templates "themes" -- [http://wordpress.org/extend/themes/ more information]. Wordpress does not have a standardized set of CSS elements for identifying parts of the weblog content. I've included a number of examples of what is seen in the wild (move to [[http://microformats.org/wiki/blog-post-examples examples]]?)

Example 1: [http://nokrev.com/older/ Fresh Bananas]

<pre><nowiki>
<body id="blog">
<div id="wrap">
<div id="content" class="two_column">
<div class="left">
ENTRIES
</div>
</div>
</div>
</body>

<h2>POST TITLE</h2>
POST CONTENT (PARTIAL)
<p>
<a href="POST URRI" title="Contiue reading this post">Continue reading</a>
</p>
</nowiki></pre>

Example 2: [http://www.vanillamist.com/blog/ VanillaMist]

<pre><nowiki>
<body>
<div id="main">
<div id="content">
ENTRIES
</div>
</div>
</body>

<div class="post">
<p class="post-date">Wed 6 Jul 2005
</p>
<div class="post-info">
<h2 class="post-title">
<a href="http://vanillamist.com/blog/?p=89" rel="bookmark" title="Permanent Link: Podcasts and a new version of Connections soon">Podcasts and a new version of Connections soon</a>
</h2>
Posted by AUTHOR under <a href="POST URI" title="View all posts in Blogs and Blogging" rel="category tag">CATEGORY</a>

<div class="post-content">
POST CONTENT
</div>

<div class="post-footer"> </div>
</div>
</div>
</nowiki></pre>

Example 3: [http://www.aamukaste.org/wpthemes/ Boredom]

<pre><nowiki>
<body>
<div id="content">
</div>
</body>

<div class="post">
<h2 id="post-5">
<a href="POST URI" rel="bookmark" title="Permanent Link to POST TITLE">POST TITLE</a>
</h2>
<small>POST DATE</small>
<div class="entry">
POST CONTENT
</div>
<p class="postmetadata">
</p>
</div>
</nowiki></pre>

==== Key CSS Elements ====
There is very little reuse amongst the various templates selected.

==== Template Concepts ====
* Post
* Title
* Author
* Date
* Content (partial)
* Content (full)

A list of all the template elemenents is [http://codex.wordpress.org/Template_Tags available here].

=== Xanga ===
* http://www.xanga.com/

== Syndication Feed Formats ==
All of the blogging tools above can produce syndication feeds from the same underlying content and thus prossibly worth discussing here.

[http://www.downes.ca/ Stephen Downes] postulates a [http://microformats.org/discuss/mail/microformats-discuss/2005-August/000670.html syndication/weblog equivalency rule], that RSS + XSLT = XHTML and XHTML + XSLT = RSS. In practice, this may not be exactly true due to syndication feeds often only provide summaries of the entry text and the definition of certain elements of syndications feeds may have ambiguous meaning or interpretation.

''This section may be moved elsewhere.''

=== Atom ===
* http://www.atomenabled.org/

Here is the basic structure of an Atom document, showing only required and recommended elements and the number of them that may appear (the rules are little more complicated than shown here, as some elements become optional or required depending on what else is included).

<pre><nowiki>
feed - 1
id - 1
title - 1; type "text"
updated - 1
link - 0-1 recommended; type "link"
author - 0-N recommended; type "person"
name - 1
email - 0-1 recommended
uri - 0-1 recommended
entry - 0-N
id - 1
title - 1; type "text"
updated - 1
published - 0-1
author - 0-N recommended; type "person"
content - 0-1 recommended; type "text";
"contains or links to the complete content of the entry"
link - 0-N recommended; type "link"
summary - 0-1 recommended; type "text"
</nowiki></pre>

A note about Atom types

* [http://www.atomenabled.org/developers/syndication/#person person] - describes a person, corporation, or similar entity
* [http://www.atomenabled.org/developers/syndication/#text text] - contains human-readable text; @text defines the encoding of the text itself: "text" (default), "html", "xhtml"
* [http://www.atomenabled.org/developers/syndication/#link link] - is patterned after html's [http://www.w3.org/TR/1999/REC-html401-19991224/struct/links.html#h-12.3 link element]; @href is required; @rel, @type, @hreflang, @title, and @length are optional.
* published and updated are datetimes

Here's an example Atom feed

<pre><nowiki>
<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">

<title>Example Feed</title>
<link href="http://example.org/"/>
<updated>2003-12-13T18:30:02Z</updated>
<author>
<name>John Doe</name>
</author>
<id>urn:uuid:60a76c80-d399-11d9-b93C-0003939e0af6</id>

<entry>
<title>Atom-Powered Robots Run Amok</title>
<link href="http://example.org/2003/12/13/atom03"/>
<id>urn:uuid:1225c695-cfb8-4ebb-aaaa-80da344efa6a</id>
<updated>2003-12-13T18:30:02Z</updated>
<summary>Some text.</summary>
</entry>

</feed>
</nowiki></pre>

=== RSS 2.0 ===
* http://blogs.law.harvard.edu/tech/rss

RSS 2.0 is not to be confused with [http://web.resource.org/rss/1.0/ RSS 1.0] is based on RDF. More about the various versions of RSS and the reason for their existance can be read on [http://en.wikipedia.org/w/index.php?title=RSS_%28protocol%29 Wikipedia]

Here is the basic structure of an RSS document, showing only required and recommended elements and the number of them that may appear:

<pre><nowiki>
</nowiki></pre>

Here's an example RSS 2.0 feed [''some editing needed internally to make entities show the correct way'']:

<pre><nowiki>
<?xml version="1.0"?>
<rss version="2.0">
<channel>
<title>Liftoff News</title>
<link>http://liftoff.msfc.nasa.gov/</link>
<description>Liftoff to Space Exploration.</description>
<language>en-us</language>
<pubDate>Tue, 10 Jun 2003 04:00:00 GMT</pubDate>
<item>

<title>Star City</title>
<link>http://liftoff.msfc.nasa.gov/news/2003/news-starcity.asp</link>
<description>How do Americans ...
<a href="http://howe.iki.rssi.ru/GCTC/gctc_e.htm">Star City</a>.
</description>
<pubDate>Tue, 03 Jun 2003 09:39:21 GMT</pubDate>
<guid>http://liftoff.msfc.nasa.gov/2003/06/03.html#item573</guid>

</item>
</channel>
</rss>
</nowiki></pre>

=== An XHTML profile for RDF Site Summaries ===
See [http://www.w3.org/2000/08/w3c-synd/ Site Summaries in XHTML], used in production for the W3C RSS feed for several years now.

== Discussion Forum / Bulletin Board Formats ==

Discussion forum posts are similar to blog posts, so may be relevant. Due to the complexity of table-based layouts, much of the mark-up in the following examples has been stripped. The mark-up and analysis also excludes controls (such as reply buttons).

=== Moodle ===
* http://moodle.org/

Moodle is an open source course management system used in education. It includes a discussion forum. The forum does not support templating.

<pre><nowiki>
<body class="mod-forum" id="mod-forum-discuss">
<div id="page">
<div id="header">
<div class="headermain">COURSE TITLE</div>
<div class="headermenu">(controls)</div>
</div>
<table class="navbar">
<tr>
<td>
<div class="breadcrumb">
<a href="BREADCRUMB LINK">BREADCRUMB TITLE</a>+
</div>
(controls)
</td>
</tr>
</table>
<div id="content">
(controls)
ENTRIES
</div>
</div>
</body>

<table class="forumpost">
<tr>
<td>
<img src="AVATAR"/>
</td>
<td class="topic>
<div class="subject">POST TITLE</div>
<div class="author">by <a>AUTHOR</a> - POST DATE</div>
</td>
</tr>
<tr>
<td class="content">
POST CONTENT
<div class="commands"><a>Show Parent</a> | <a>Reply</a></div>
</td>
</tr>
</table>
</nowiki></pre>

==== Key CSS Elements ====

* "headermain" identifies the course title
* "breadcrumb" identifies breadcrumbs
* "forumpost" identifies a post
* "subject" identifies the post subject
* "author" identifies the author, but also includes the date and other text
* "content" identifies the content area, but includes some controls also

==== Concepts ====

* course title
* breadcrumb titles and links
* post title
* post author
* post date
* post content
* original post (to which this is a reply)
* author avatar

=== phpBB ===
* http://www.phpbb.com/

phpBB is a popular GPL discussion forum system. This is based on the forum on the [http://www.phpbb.com/phpBB/ phpBB] website.

<pre><nowiki>
<body>
<table>
<tr>
<td class="bodyline" bgcolor="white">
<table width="100%" cellspacing="0" cellpadding="10" border="0">
<tr>
<td>
<table>
<tr>
<td>
<a class="maintitle" href="FORUM LINK">FORUM TITLE</a>
</td>
</tr>
</table>
<table width="100%" cellspacing="2" cellpadding="2" border="0">
<tr>
(controls)
<td align="left" valign="middle" width="100%">
<span class="nav"><a href="BREADCRUMB LINK" class="nav">BREADCRUMB TITLE</a>+</span>
</td>
</tr>
</table>

ENTRIES
(controls)
(repeat of controls and navigation)
...
</table>
</body>

<table class="forumline">
<tr>
<td class="catHead">(controls)</td>
</tr>
<tr>
<td class="row1">
<span class="name">
<a name="###"></a>
<b>AUTHOR</b>
</span>
<span class="postdetails">
AUTHOR STATUS (registered etc.)
<img src="AVATAR"/>
Joined: AUTHOR JOIN DATE
Posts: AUTHOR POST COUNT
Location: etc.
</span>
</td>
<td class="row1">
<table>
<tr>
<td>
<span class="postdetails">Posted: POST DATE Post subject: POST TITLE</span>
</td>
<td>(controls)</td>
</tr>
<tr>
<td>
<span class="postbody">
CONTENT
</span>
</td>
</tr>
</table>
</td>
</tr>
(controls)
</table>
</nowiki></pre>

==== Key CSS Elements ====

* "maintitle" identifies the forum title and link
* "nav" is used for breadcrumbs
* "forumline" encloses the post
* "name" identifies the author
* "postdetails" occurs twice, once providing information about the author, once enclosing the post date and title
* "postbody" identifies the post content

==== Concepts ====

* forum title and link
* breadcrumb titles and links
* post title
* post author
* post date
* post content
* author status
* author join date
* author avatar
* author post count
* author location

=== PunBB ===

* http://punbb.org/

PunBB is GPL forum software. This structure is from the [http://forums.punbb.org/ forum] on their web site.

<pre><nowiki>
<body>
<div id="punwrap">
<div id="punviewtopic" class="pun">
<div id="brdheader" class="block">
<div class="box">
<div id="brdtitle" class="inbox">
<h1><span>SITE SECTION TITLE</span></h1>
<p><span>SITE SECTION BYLINE</span></p>
</div>
(controls)
</div>
</div>
<div id="announce" class="block">
<h2><span>ANNOUNCEMENT TITLE</span></h2>
<div class="box">
<div class="inbox">
<div><span class="warntext">ANNOUNCEMENT CONTENT</span></div>
</div>
</div>
</div>
<div class="linkst">
<div class="inbox">
(controls)
<ul>
<li><a href="BREADCRUMB LINK">BREADCRUMB TITLE</a></li>+
</ul>
</div>
</div>
ENTRIES
</div>
</body>

<div id="HTML-ID" class="blockpost">
<h2>
<span class="conr">POST NUMBER</span>
<a href="PERMALINK">POST DATE</a></h2>
<div class="box">
<div class="inbox">
<div class="postleft">
<dl>
<dt><strong><a href="AUTHOR PROFILE LINK">AUTHOR NAME</a></strong></dt>
<dd class="usertitle"><strong>AUTHOR STATUS (e.g. Moderator)</strong></dd>
<dd class="postavatar"><img src="AVATAR"/></dd>
<dd>From: AUTHOR LOCATION</dd>
<dd>Registered: AUTHOR REGISTRATION DATE</dd>
<dd>Posts: AUTHOR POST COUNT</dd>
<dd class="usercontacts"><a href="AUTHOR URL">Website</a></dd>
</dl>
</div>
<div class="postright">
<h3>POST TITLE</h3>
<div class="postmsg">
POST CONTENT
</div>
<div class="postsignature">AUTHOR SIGNATURE</div>
</div>
<div class="clearer"></div>
<div class="postfootleft"><p>AUTHOR STATE (online, offline)</p></div>
<div class="postfootright"><div></div></div>
</div>
</div>
</div>
</nowiki></pre>

==== Key CSS Elements ====

* "blockpost" encloses a post; the element also has an HTML id
* "conr" is the post number within the discussion thread
* h1 indicates the site section title
* "announce" and "warntext" indicate the announcement title and content
* ul inside "linkst" identifies breadcrumbs
* h2 encloses the post number, post date, and permalink, distinguishable by HTML a and span elements
* h3 identifies the post title
* "postmsg" identifies the post content
* the author name and URL are in dl dt a
* additional author information is in dl dd
* "usertitle" identifies the author status
* "postavatar" indentifies the author's avatar
* "usercontacts" identifies author contact information

==== Concepts ====

* site section title and byline
* announcement title and content
* breadcrumb titles and links
* post title
* post author
* post date
* permalink
* post sequence number
* author status
* author avatar
* author location
* author registration date
* author post count
* author URL
* author profile link
* author signature
* author contact information (website)

=== YaBB ===
* http://www.yabbforum.com/

YaBB is a popular commercial/free forum system. This example is based on the [http://www.yabbforum.com/community/ forum] on the YaBB site. I have stripped some presentational class names.

<pre><nowiki>
<body>
<div class="container">
<div class="maincontent">
<div class="seperator">
<table>
(controls, login)
<tr>
<td>
<span id="fscroller">FORUM WELCOME</span>
(controls)
</td>
</tr>
</table>
</div>
<div class="navbarcontainer">
<table>
<tr>
<td>
<span>
<b><a href="BREADCRUMB LINK" class="nav">BREADCRUMB TITLE</a>+</b>
(Moderators: <a href="MODERATOR LINK">MODERATOR NAME</a>+)
<div class="seperator">
<table>
<tr>
<td>
<span>FORUM DESCRIPTION.</span>
</td>
</tr>
</table>
</div>
</span>
</td>
(controls)
</tr>
</table>
</div>
ENTRIES
</div>
(repeat of navigation)
</div>
</body>

<div class="displaycontainer">
<table>
<tr>
<td>
<a><b>POST TITLE</b></a>
AUTHOR STATUS (junior member, senior, etc.)<br />
<img src="AVATAR/>
AUTHOR BYLINE
Posts: ###
Gender: <img/>
</td>
<td>
<div>
<b>POST TITLE</b>
<span><b>Reply #nnn on:</b> POST DATE</span>
</div>
<div>
<span class="message">
CONTENT
</span>
</div>
</td>
</tr>
<tr>(controls)</tr>
</table>
</div>
</nowiki></pre>

==== Key CSS Elements ====

* "displaycontainer" encloses a post
* "message" identifies post content
* no other fields are identified by meaningful mark-up

==== Concepts ====

* forum welcome message
* forum description
* forum moderators (names and links)
* breadcrumbs (titles and links)
* post title
* post author
* post date
* post content
* original post (to which this is a reply)
* author status
* author byline
* author avatar
* author gender
* author post count

== Examples from the wild ==

* Early work on extending standardized nodes in Drupal: http://factorycity.net/demos/drupal/event_system/microformats/
* Microformat-style hooks in forum posts for Javascript annotation: http://www.geof.net/code/annotation/technical.html#microformats

=See Also=
* [[hatom|hAtom]] - the draft proposal based on this information
* [[blog-post-brainstorming]]
* [[blog-post-formats]]
* [[blog-post-examples]]
* [[blog-description-format]] - how to describe a blog (as opposed to the individual entries, which is what we're doing here)

blog-post-formats

2005-10-25T21:21:19Z

DanC: refine XHTML site summary blurb

= Current Blog Formats =

There is a need for developing standard classes for blog posts (i.e. a microformat!).

This page serves to document the current list of individual blog post schemas, formats, and efforts as background for the design of a simple blog post MicroFormat.

== Discussion Participants ==

=== Editor ===
* [http://blog.factoryjoe.com/ Chris Messina], [http://flock.com Flock, Inc.]

=== Authors ===
* [http://blog.factoryjoe.com/ Chris Messina], [http://flock.com Flock, Inc.]
* [http://blogmatrix.blogmatrix.com/ David Janes], [http://www.blogmatrix BlogMatrix, Inc.]
* [http://www.geof.net/ Geof Glass]

=== Interested Folks ===
* [http://tantek.com/log/ Tantek Çelik], [http://technorati.com/ Technorati]
* [http://theryanking.com/blog/ Ryan King], [http://technorati.com/ Technorati]

== Tools ==

=== Blogger ===
* http://www.blogger.com/home

Blogger is one the earliest, best known and probably most widely used blogging platform. Blogger was bought by [http://www.google.com Google] in February of 2003. Blogger allows users to create and edit their own templates and also provides a large number of (more or less) attractive templates from which the user can select. Unfortunately, you must log into a blogger account to see the template selection.

Here are several Blogger templates, randomly selected from the presets. More recent templates seem to be converging on a vocabulary for identifying parts of posts. This may because they share an evolutionary history from a common template. I've included three examples here:

<pre><nowiki>
<body>
<div id="content">
<div id="main">
ENTRIES
</div>
</div>
</body>

<h2 class="date-header">POST DATE</h2>
<div class="post">
<a name="POST #"></a>
<h3 class="post-title">
<a href="POST URI" title="external link">POST TITLE</a>
</h3>
<p>POST CONTENT</p>
<p class="post-footer">
<em>posted by AUTHOR @ <a href="POST URI" title="permanent link">POST DATETIME</a></em>
</p>
</div>
</nowiki></pre>

<pre><nowiki>
<body>
<div id="main">
<div id="main2">
ENTRIES
</div>
</div>
</body>

<div class="post">
<a name="POST #"></a>
<h3 class="post-title">
<a href="sample_post.html" title="permanent link">POST TITLE</a>
</h3>
<div class="post-body">
POST CONTENT
</div>
<p class="post-footer">
<em>posted by AUTHOR @ <a href="POST URI" title="permanent link">POST TIME</a></em>
</p>
</div>
</nowiki></pre>

<pre><nowiki>
<body>
<div id="leftcontent">
ENTRIES
</div>
</body>

<div class="Post">
<a name="POST #"></a>
POST CONTENT
<span class="PostFooter">
<a href="POST URI">POST TIME</a>
</span>
</div>
</nowiki></pre>

==== Key CSS Elements ====
* newer templates seem to use "main" to identify a enclosure for all entries
* newer templates use "post" to identify a weblog entry
* newer templates use "post-title" to identify the entry's title
* beyond this there is little standardization

==== Template Concepts ====
* all posts
* an individual post
* post title
* post author
* post posting time
* post content
* post URI (permalink)

=== Blosxom===
* http://www.blosxom.com/
* http://pyblosxom.sourceforge.net/

=== Drupal ===
* http://drupal.org
* varies per theme

=== LiveJournal ===
* http://www.livejournal.com/

=== MovableType ===
* http://www.sixapart.com/movabletype/

MovableType is a perl-based blogging platform. Note that the MT is old and widely deployed and there are very many different variants on the templates in the wild.

The standard template for the weblog's main page (the "[http://www.sixapart.com/movabletype/default_templates#main_index main index]") has the following structure:

<pre><nowiki>
<body>
<div class="content">
<h2>DATE HEADER</h2>
<h3 id="a####">POST TITLE</h3>
POST CONTENT
[ OPTIONAL LINK TO MORE POST CONTENT ]
<p class="posted">Posted by AUTHOR at <a href="POST URI">POST DATE</a>
</div>
</div>

<div class="content">
<p align="right">
<h2>POST DATE</h2>
</p>
<h3>POST TITLE</h3>
POST CONTENT
<div id="more">
MORE POST CONTENT (optional)
</div>
<p class="posted">Posted by AUTHOR at DATE</p>
</div>
</nowiki></pre>

==== Key CSS Elements ====

* "content" can enclose an individual entry or all entries, depending on the context
* "h2" encloses the post date (literally: the time is not included)
* "h3" encloses the title
* there is no standard enclosure for all the content
* there is no clear identification of "here's all the entries"
* there is no clear identification of the post's author
* the permalink is not necessarily on the page anywhere

==== Template Concepts ====
* all posts
* an individual post
* post title
* post author
* post posting time
* post content, which includes the next two
* post content (first part)
* post content (expended part)
* post URI (permalink)

=== TypePad ===
* http://www.sixapart.com/typepad/

Typepad is a MovableType hosting service. It provides a list of [http://help.typepad.com/tags/default_templates.html default templates] and [ "template modules"] from which users can construct or modify their own templates. Looking at several Typepad blogs, most or all of them following the nomenclature and struct defined by these templates.

The standard structure is as follows:

<pre><nowiki>
<body class="layout-two-column-right">
<div id="container">
<div id="container-inner" class="pkg">
<div id="pagebody">
<div id="pagebody-inner" class="pkg">
<div id="alpha">
<div id="alpha-inner" class="pkg">
INDIVIDUAL ENTRY
</div>
</div>
</div>
</div>
</div>
</div>
</body>

<div class="entry" id="entry-#####">
<h3 class="entry-header">POST TITLE</h3>
<div class="entry-content">
<div class="entry-body">
POST CONTENT
</div>
<a id="more"></a>
<div class="entry-more">
MORE POST CONTENT
</div>
</div>
<p class="entry-footer">
POST FOOTER
</p>
</div>
</nowiki></pre>

I cannot seem to track down in the templates where the POST FOOTER is defined. However, we can see the results from a [http://www.bluedogbob.com/ sample blog]:

<pre><nowiki>
<span class="post-footers">Posted by AUTHOR_NAME in CATEGORY</span>
<span class="separator">|</span>
<a class="permalink" href="ENTRY_URI">Permalink</a>
| <a href="COMMENT_URI">Comments (2)</a>
| <a href="TRACKBACKS_URI">TrackBack (0)</a>
</nowiki></pre>

==== Key CSS Elements ====
* "entry" encloses all elements within an entry
* "entry-content" contains all the entry text, plus additional text saying "here's more"
* "entry-header" contains the title of the post
* "permalink" contains the post's URI
* there is no clear identification of "here's all the entries"
* there is no clear identification of the post's author

==== Template Concepts ====
* all posts
* an individual post
* post title
* post author
* post posting time
* post content, which includes the next two
* post content (first part)
* post content (expended part)
* post URI (permalink)

=== WordPress ===
* http://wordpress.org

WordPress is a popular GPLed blogging system based on PHP and MySQL. WordPress calls their templates "themes" -- [http://wordpress.org/extend/themes/ more information]. Wordpress does not have a standardized set of CSS elements for identifying parts of the weblog content. I've included a number of examples of what is seen in the wild (move to [[http://microformats.org/wiki/blog-post-examples examples]]?)

Example 1: [http://nokrev.com/older/ Fresh Bananas]

<pre><nowiki>
<body id="blog">
<div id="wrap">
<div id="content" class="two_column">
<div class="left">
ENTRIES
</div>
</div>
</div>
</body>

<h2>POST TITLE</h2>
POST CONTENT (PARTIAL)
<p>
<a href="POST URRI" title="Contiue reading this post">Continue reading</a>
</p>
</nowiki></pre>

Example 2: [http://www.vanillamist.com/blog/ VanillaMist]

<pre><nowiki>
<body>
<div id="main">
<div id="content">
ENTRIES
</div>
</div>
</body>

<div class="post">
<p class="post-date">Wed 6 Jul 2005
</p>
<div class="post-info">
<h2 class="post-title">
<a href="http://vanillamist.com/blog/?p=89" rel="bookmark" title="Permanent Link: Podcasts and a new version of Connections soon">Podcasts and a new version of Connections soon</a>
</h2>
Posted by AUTHOR under <a href="POST URI" title="View all posts in Blogs and Blogging" rel="category tag">CATEGORY</a>

<div class="post-content">
POST CONTENT
</div>

<div class="post-footer"> </div>
</div>
</div>
</nowiki></pre>

Example 3: [http://www.aamukaste.org/wpthemes/ Boredom]

<pre><nowiki>
<body>
<div id="content">
</div>
</body>

<div class="post">
<h2 id="post-5">
<a href="POST URI" rel="bookmark" title="Permanent Link to POST TITLE">POST TITLE</a>
</h2>
<small>POST DATE</small>
<div class="entry">
POST CONTENT
</div>
<p class="postmetadata">
</p>
</div>
</nowiki></pre>

==== Key CSS Elements ====
There is very little reuse amongst the various templates selected.

==== Template Concepts ====
* Post
* Title
* Author
* Date
* Content (partial)
* Content (full)

A list of all the template elemenents is [http://codex.wordpress.org/Template_Tags available here].

=== Xanga ===
* http://www.xanga.com/

== Syndication Feed Formats ==
All of the blogging tools above can produce syndication feeds from the same underlying content and thus prossibly worth discussing here.

[http://www.downes.ca/ Stephen Downes] postulates a [http://microformats.org/discuss/mail/microformats-discuss/2005-August/000670.html syndication/weblog equivalency rule], that RSS + XSLT = XHTML and XHTML + XSLT = RSS. In practice, this may not be exactly true due to syndication feeds often only provide summaries of the entry text and the definition of certain elements of syndications feeds may have ambiguous meaning or interpretation.

''This section may be moved elsewhere.''

=== Atom ===
* http://www.atomenabled.org/

Here is the basic structure of an Atom document, showing only required and recommended elements and the number of them that may appear (the rules are little more complicated than shown here, as some elements become optional or required depending on what else is included).

<pre><nowiki>
feed - 1
id - 1
title - 1; type "text"
updated - 1
link - 0-1 recommended; type "link"
author - 0-N recommended; type "person"
name - 1
email - 0-1 recommended
uri - 0-1 recommended
entry - 0-N
id - 1
title - 1; type "text"
updated - 1
published - 0-1
author - 0-N recommended; type "person"
content - 0-1 recommended; type "text";
"contains or links to the complete content of the entry"
link - 0-N recommended; type "link"
summary - 0-1 recommended; type "text"
</nowiki></pre>

A note about Atom types

* [http://www.atomenabled.org/developers/syndication/#person person] - describes a person, corporation, or similar entity
* [http://www.atomenabled.org/developers/syndication/#text text] - contains human-readable text; @text defines the encoding of the text itself: "text" (default), "html", "xhtml"
* [http://www.atomenabled.org/developers/syndication/#link link] - is patterned after html's [http://www.w3.org/TR/1999/REC-html401-19991224/struct/links.html#h-12.3 link element]; @href is required; @rel, @type, @hreflang, @title, and @length are optional.
* published and updated are datetimes

Here's an example Atom feed

<pre><nowiki>
<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">

<title>Example Feed</title>
<link href="http://example.org/"/>
<updated>2003-12-13T18:30:02Z</updated>
<author>
<name>John Doe</name>
</author>
<id>urn:uuid:60a76c80-d399-11d9-b93C-0003939e0af6</id>

<entry>
<title>Atom-Powered Robots Run Amok</title>
<link href="http://example.org/2003/12/13/atom03"/>
<id>urn:uuid:1225c695-cfb8-4ebb-aaaa-80da344efa6a</id>
<updated>2003-12-13T18:30:02Z</updated>
<summary>Some text.</summary>
</entry>

</feed>
</nowiki></pre>

=== RSS 2.0 ===
* http://blogs.law.harvard.edu/tech/rss

RSS 2.0 is not to be confused with [http://web.resource.org/rss/1.0/ RSS 1.0] is based on RDF. More about the various versions of RSS and the reason for their existance can be read on [http://en.wikipedia.org/w/index.php?title=RSS_%28protocol%29 Wikipedia]

Here is the basic structure of an RSS document, showing only required and recommended elements and the number of them that may appear:

<pre><nowiki>
</nowiki></pre>

Here's an example RSS 2.0 feed [''some editing needed internally to make entities show the correct way'']:

<pre><nowiki>
<?xml version="1.0"?>
<rss version="2.0">
<channel>
<title>Liftoff News</title>
<link>http://liftoff.msfc.nasa.gov/</link>
<description>Liftoff to Space Exploration.</description>
<language>en-us</language>
<pubDate>Tue, 10 Jun 2003 04:00:00 GMT</pubDate>
<item>

<title>Star City</title>
<link>http://liftoff.msfc.nasa.gov/news/2003/news-starcity.asp</link>
<description>How do Americans ...
<a href="http://howe.iki.rssi.ru/GCTC/gctc_e.htm">Star City</a>.
</description>
<pubDate>Tue, 03 Jun 2003 09:39:21 GMT</pubDate>
<guid>http://liftoff.msfc.nasa.gov/2003/06/03.html#item573</guid>

</item>
</channel>
</rss>
</nowiki></pre>

=== An XHTML profile for RDF Site Summaries ===
See [[http://www.w3.org/2000/08/w3c-synd/ Site Summaries in XHTML]], used in production for the W3C RSS feed for several years now.

== Discussion Forum / Bulletin Board Formats ==

Discussion forum posts are similar to blog posts, so may be relevant. Due to the complexity of table-based layouts, much of the mark-up in the following examples has been stripped. The mark-up and analysis also excludes controls (such as reply buttons).

=== Moodle ===
* http://moodle.org/

Moodle is an open source course management system used in education. It includes a discussion forum. The forum does not support templating.

<pre><nowiki>
<body class="mod-forum" id="mod-forum-discuss">
<div id="page">
<div id="header">
<div class="headermain">COURSE TITLE</div>
<div class="headermenu">(controls)</div>
</div>
<table class="navbar">
<tr>
<td>
<div class="breadcrumb">
<a href="BREADCRUMB LINK">BREADCRUMB TITLE</a>+
</div>
(controls)
</td>
</tr>
</table>
<div id="content">
(controls)
ENTRIES
</div>
</div>
</body>

<table class="forumpost">
<tr>
<td>
<img src="AVATAR"/>
</td>
<td class="topic>
<div class="subject">POST TITLE</div>
<div class="author">by <a>AUTHOR</a> - POST DATE</div>
</td>
</tr>
<tr>
<td class="content">
POST CONTENT
<div class="commands"><a>Show Parent</a> | <a>Reply</a></div>
</td>
</tr>
</table>
</nowiki></pre>

==== Key CSS Elements ====

* "headermain" identifies the course title
* "breadcrumb" identifies breadcrumbs
* "forumpost" identifies a post
* "subject" identifies the post subject
* "author" identifies the author, but also includes the date and other text
* "content" identifies the content area, but includes some controls also

==== Concepts ====

* course title
* breadcrumb titles and links
* post title
* post author
* post date
* post content
* original post (to which this is a reply)
* author avatar

=== phpBB ===
* http://www.phpbb.com/

phpBB is a popular GPL discussion forum system. This is based on the forum on the [http://www.phpbb.com/phpBB/ phpBB] website.

<pre><nowiki>
<body>
<table>
<tr>
<td class="bodyline" bgcolor="white">
<table width="100%" cellspacing="0" cellpadding="10" border="0">
<tr>
<td>
<table>
<tr>
<td>
<a class="maintitle" href="FORUM LINK">FORUM TITLE</a>
</td>
</tr>
</table>
<table width="100%" cellspacing="2" cellpadding="2" border="0">
<tr>
(controls)
<td align="left" valign="middle" width="100%">
<span class="nav"><a href="BREADCRUMB LINK" class="nav">BREADCRUMB TITLE</a>+</span>
</td>
</tr>
</table>

ENTRIES
(controls)
(repeat of controls and navigation)
...
</table>
</body>

<table class="forumline">
<tr>
<td class="catHead">(controls)</td>
</tr>
<tr>
<td class="row1">
<span class="name">
<a name="###"></a>
<b>AUTHOR</b>
</span>
<span class="postdetails">
AUTHOR STATUS (registered etc.)
<img src="AVATAR"/>
Joined: AUTHOR JOIN DATE
Posts: AUTHOR POST COUNT
Location: etc.
</span>
</td>
<td class="row1">
<table>
<tr>
<td>
<span class="postdetails">Posted: POST DATE Post subject: POST TITLE</span>
</td>
<td>(controls)</td>
</tr>
<tr>
<td>
<span class="postbody">
CONTENT
</span>
</td>
</tr>
</table>
</td>
</tr>
(controls)
</table>
</nowiki></pre>

==== Key CSS Elements ====

* "maintitle" identifies the forum title and link
* "nav" is used for breadcrumbs
* "forumline" encloses the post
* "name" identifies the author
* "postdetails" occurs twice, once providing information about the author, once enclosing the post date and title
* "postbody" identifies the post content

==== Concepts ====

* forum title and link
* breadcrumb titles and links
* post title
* post author
* post date
* post content
* author status
* author join date
* author avatar
* author post count
* author location

=== PunBB ===

* http://punbb.org/

PunBB is GPL forum software. This structure is from the [http://forums.punbb.org/ forum] on their web site.

<pre><nowiki>
<body>
<div id="punwrap">
<div id="punviewtopic" class="pun">
<div id="brdheader" class="block">
<div class="box">
<div id="brdtitle" class="inbox">
<h1><span>SITE SECTION TITLE</span></h1>
<p><span>SITE SECTION BYLINE</span></p>
</div>
(controls)
</div>
</div>
<div id="announce" class="block">
<h2><span>ANNOUNCEMENT TITLE</span></h2>
<div class="box">
<div class="inbox">
<div><span class="warntext">ANNOUNCEMENT CONTENT</span></div>
</div>
</div>
</div>
<div class="linkst">
<div class="inbox">
(controls)
<ul>
<li><a href="BREADCRUMB LINK">BREADCRUMB TITLE</a></li>+
</ul>
</div>
</div>
ENTRIES
</div>
</body>

<div id="HTML-ID" class="blockpost">
<h2>
<span class="conr">POST NUMBER</span>
<a href="PERMALINK">POST DATE</a></h2>
<div class="box">
<div class="inbox">
<div class="postleft">
<dl>
<dt><strong><a href="AUTHOR PROFILE LINK">AUTHOR NAME</a></strong></dt>
<dd class="usertitle"><strong>AUTHOR STATUS (e.g. Moderator)</strong></dd>
<dd class="postavatar"><img src="AVATAR"/></dd>
<dd>From: AUTHOR LOCATION</dd>
<dd>Registered: AUTHOR REGISTRATION DATE</dd>
<dd>Posts: AUTHOR POST COUNT</dd>
<dd class="usercontacts"><a href="AUTHOR URL">Website</a></dd>
</dl>
</div>
<div class="postright">
<h3>POST TITLE</h3>
<div class="postmsg">
POST CONTENT
</div>
<div class="postsignature">AUTHOR SIGNATURE</div>
</div>
<div class="clearer"></div>
<div class="postfootleft"><p>AUTHOR STATE (online, offline)</p></div>
<div class="postfootright"><div></div></div>
</div>
</div>
</div>
</nowiki></pre>

==== Key CSS Elements ====

* "blockpost" encloses a post; the element also has an HTML id
* "conr" is the post number within the discussion thread
* h1 indicates the site section title
* "announce" and "warntext" indicate the announcement title and content
* ul inside "linkst" identifies breadcrumbs
* h2 encloses the post number, post date, and permalink, distinguishable by HTML a and span elements
* h3 identifies the post title
* "postmsg" identifies the post content
* the author name and URL are in dl dt a
* additional author information is in dl dd
* "usertitle" identifies the author status
* "postavatar" indentifies the author's avatar
* "usercontacts" identifies author contact information

==== Concepts ====

* site section title and byline
* announcement title and content
* breadcrumb titles and links
* post title
* post author
* post date
* permalink
* post sequence number
* author status
* author avatar
* author location
* author registration date
* author post count
* author URL
* author profile link
* author signature
* author contact information (website)

=== YaBB ===
* http://www.yabbforum.com/

YaBB is a popular commercial/free forum system. This example is based on the [http://www.yabbforum.com/community/ forum] on the YaBB site. I have stripped some presentational class names.

<pre><nowiki>
<body>
<div class="container">
<div class="maincontent">
<div class="seperator">
<table>
(controls, login)
<tr>
<td>
<span id="fscroller">FORUM WELCOME</span>
(controls)
</td>
</tr>
</table>
</div>
<div class="navbarcontainer">
<table>
<tr>
<td>
<span>
<b><a href="BREADCRUMB LINK" class="nav">BREADCRUMB TITLE</a>+</b>
(Moderators: <a href="MODERATOR LINK">MODERATOR NAME</a>+)
<div class="seperator">
<table>
<tr>
<td>
<span>FORUM DESCRIPTION.</span>
</td>
</tr>
</table>
</div>
</span>
</td>
(controls)
</tr>
</table>
</div>
ENTRIES
</div>
(repeat of navigation)
</div>
</body>

<div class="displaycontainer">
<table>
<tr>
<td>
<a><b>POST TITLE</b></a>
AUTHOR STATUS (junior member, senior, etc.)<br />
<img src="AVATAR/>
AUTHOR BYLINE
Posts: ###
Gender: <img/>
</td>
<td>
<div>
<b>POST TITLE</b>
<span><b>Reply #nnn on:</b> POST DATE</span>
</div>
<div>
<span class="message">
CONTENT
</span>
</div>
</td>
</tr>
<tr>(controls)</tr>
</table>
</div>
</nowiki></pre>

==== Key CSS Elements ====

* "displaycontainer" encloses a post
* "message" identifies post content
* no other fields are identified by meaningful mark-up

==== Concepts ====

* forum welcome message
* forum description
* forum moderators (names and links)
* breadcrumbs (titles and links)
* post title
* post author
* post date
* post content
* original post (to which this is a reply)
* author status
* author byline
* author avatar
* author gender
* author post count

== Examples from the wild ==

* Early work on extending standardized nodes in Drupal: http://factorycity.net/demos/drupal/event_system/microformats/
* Microformat-style hooks in forum posts for Javascript annotation: http://www.geof.net/code/annotation/technical.html#microformats

=See Also=
* [[hatom|hAtom]] - the draft proposal based on this information
* [[blog-post-brainstorming]]
* [[blog-post-formats]]
* [[blog-post-examples]]
* [[blog-description-format]] - how to describe a blog (as opposed to the individual entries, which is what we're doing here)