Microformats Wiki - User contributions [en]

User:RobertBachmann

2011-12-09T16:37:20Z

RobertBachmann:

= Robert Bachmann =

* Email: rbachm(AT)gmail.com
* Twitter: http://twitter.com/robertbachmann

<br style="maring-bottom: 4em"/>

== Public domain release ==
{{cc-public-domain-release}}

User:RobertBachmann

2009-07-28T15:47:28Z

RobertBachmann: /* Robert Bachmann */

= Robert Bachmann =

Contact: rbachm (AT) gmail (DOT) com
----

{{cc-public-domain-release}}

User:RobertBachmann

2008-08-24T11:30:46Z

RobertBachmann: cc-public-domain-release

= Robert Bachmann =

Contact: http://rbach.priv.at/Contact

Web: http://rbach.priv.at/

----

NOTE: rbach.priv.at is down because of technical problems. In the meanwhile you
can use my other email address to contact me: Robert.Bachmann (at) gmx.at

----

{{cc-public-domain-release}}

User:RobertBachmann

2008-08-24T11:29:46Z

RobertBachmann: /* Robert Bachmann */ email

irc

2008-08-24T11:27:14Z

RobertBachmann: /* logs status */

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

=== logs status ===
* ''DNS for rbach.priv.at seems to be down today. Anybody got a work-around?'' [[User:DanC|DanC]] 11:45, 22 Aug 2008 (PDT)
** Even if you could get onto the web server, the bot hasn't been logging properly for the last week or so. [[User:TobyInk|TobyInk]] 01:35, 24 Aug 2008 (PDT)
* The server where rbach.priv.at is hosted is down. I've already contacted the server's owner, but it I'm afraid that it will take some time to fix it. [[User:RobertBachmann|Robert Bachmann]] 04:27, 24 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]]

irc

2008-01-08T12:21:38Z

RobertBachmann:

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

== Logs ==

Logs are available here: http://rbach.priv.at/Microformats-IRC/

Atom feed of logs available here: http://microformat.makedatamakesense.com/log_feed/

== People on irc ==

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

=== Admins ===

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

== Greetings ==

To display a brief description of who you are each time you join the channel, you can 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]

==Bots==

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]

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

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

===Advanced===
...working on...

==Clients==

The following clients are recommended by #microformats participants:

===Windows===

* [http://pidgin.im/ Pidgin] - Popular open-source multi-protocol windows client, using libpurple
* [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://irssi.org/ Irssi] - Unix client, often run from a shell, sometimes [http://f0rked.com/articles/irssi in conjunction with 'screen'].
* [http://gaim.sourceforge.net/ Gaim] - Cross-platform multi-protocol instant messenger.
* [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]]

User:RobertBachmann

2008-01-08T12:19:53Z

RobertBachmann:

= Robert Bachmann =

Contact: http://rbach.priv.at/Contact

Web: http://rbach.priv.at/

----

{{public-domain-release}}

mercurial-quick-start

2007-08-09T19:31:21Z

RobertBachmann: /* Running the test */ corrected a mistake

__NOTOC__
= HowTo: Download code from the repository =

'''I had a little difficulty checking out code from the [http://hg.microformats.org repository], so I created this page to help those who are new to Mercurial and the Microformats repository.'''

== Introduction ==
Microformats.org uses [http://www.selenic.com/mercurial/wiki/index.cgi Mercurial] for source code management. You can find microformat generators, tests, and [http://suda.co.uk/projects/X2V/ Brian Suda's X2V] scripts in the repository at [http://hg.microformats.org]

== Mercurial ==
Mercurial offers binary packages and source code for Windows, Linux, and Mac OSX. You can read more about [http://www.selenic.com/mercurial/wiki/index.cgi/TutorialInstall how to install Mercurial] from their wiki.

== Checking out code ==
Once you have Mercurial installed, the quickest way to get started with the following recipe.

The first time you access a repository, you must first clone the repository on your local drive.

For example: to download the latest code for X2V, you would use the following:

<code>hg clone http://hg.microformats.org/x2v/</code>

Once you have cloned the repository, you can update your local code with the latest from the Microformats repository with:

<code>hg update http://hg.microformats.org/x2v/</code>

== Rake ==
For those of you with [http://rake.rubyforge.org/ Rake] installed on your machine you can take advantage of the Rakefile included with the Generators and X2V. The Rakefile makes two commands available:

# <code>rake hg:pull_update</code> -- Pull and update this repository. May fail if you need to merge
# <code>rake hg:push_update</code> -- Pushes this repository to microformats.org. Pulls and updates first

== Testing the XSLT scripts ==

The XSLT scripts in the mercurial repository are accompanied by Perl test scripts.
With these test scripts you can test the XSLT scripts against the tests from the tests repository using LibXSLT.
Various other XSLT engines are also supported: [http://4suite.org/ 4xslt], [http://saxon.sourceforge.net/ Saxon] (Java version), [http://xml.apache.org/xalan-j/ Xalan-J], [http://xml.apache.org/xalan-j/ Xalan-C].

=== Installing prerequisites ===

In order for the Perl scripts to work you'll need Perl 5.8
and the following additional modules: [http://cpan.uwinnipeg.ca/module/XML::LibXML XML::LibXML], [http://cpan.uwinnipeg.ca/module/XML::LibXSLT XML::LibXSLT],
[http://cpan.uwinnipeg.ca/module/Text::Diff Text::Diff].

==== MacOSX ====

Install [http://trac.macosforge.org/projects/macports/wiki/UsingMacPortsQuickStart MacPorts]
and then run <pre>sudo su
port install p5-xml-libxslt
port install p5-text-diff</pre>

===== *nix =====

Either use your distributions package management tool or
"<code>cpan install</code>" to install the Perl modules listed above.

===== Windows =====

Get ActivePerl 5.8 from http://www.activestate.com/Products/activeperl/.

Afterwards see http://theoryx5.uwinnipeg.ca/ppms/ for instructions on how to install the
additional modules.

You might also want to install [http://cpan.uwinnipeg.ca/module/Win32::Console::ANSI Win32::Console::ANSI].

=== Preparations ===
First you need to checkout both the tests and the XSLT repositories:

<pre>hg clone http://hg.microformats.org/x2v /home/johndoe/tests
hg clone http://hg.microformats.org/tests /home/johndoe/xslts</pre>

The test scripts are in the XSLT repositories, in order to tell them where
the test files are located you have to set the <code>MICROFORMATS_TESTS</code> environment variable.

On *nix and MacOSX (assumig you're using the bash shell): <pre>export MICROFORMATS_TESTS=/home/johndoe/tests</pre>
On Windows: <pre>set MICROFORMATS_TESTS=C:\path\to\tests</pre>

=== Running the test ===

First change to the directory where the XSLTs are located.
Afterwards you can start the test scripts with:
* <code>hcard/test.pl</code>
* <code>hcalendar/test-vcal.pl</code>
* <code>hatom/test.pl</code>

(On Windows: Use backslashes instead of forward slashes)

Here are some examples:

<pre>
./test.pl -x # Run all tests with libxslt
./test.pl -A 5 # Run test #5 with all Engines
./test.pl --saxon --4xslt 1-3 12 15 # Run test 1, 2, 3, 12, 15 with Saxon and 4XSLT
./test.pl --xalan-c 8-18 -e 12-14 # Run test 8-11 and 15-18 with Xalan-C
</pre>

=== Using additional XSLT engines ===

If you want to use any XSLT engines (besides LibXSLT) you have to install them and make
sure that the can be launched from the test script.

For Java based XSLT engines you need to add the the engine's .jar file (saxon8.jar and xalan.jar respectively) to your <code>CLASSPATH</code>
environment variable. Enter
<pre>java net.sf.saxon.Transform
java org.apache.xalan.xslt.Process</pre> to test if Xalan-J and Saxon can be called by the test scripts.

For all other XSLT engines add the path to their "bin" directories to your <code>PATH</code>
environment variable.

Enter
<pre>4xslt
Xalan
</pre> into the console to test if 4xslt and Xalan-C can be called by the test scripts.

mercurial-quick-start

2007-07-25T15:39:12Z

RobertBachmann: /* Running the test */ removed redundant word

__NOTOC__
= HowTo: Download code from the repository =

'''I had a little difficulty checking out code from the [http://hg.microformats.org repository], so I created this page to help those who are new to Mercurial and the Microformats repository.'''

== Introduction ==
Microformats.org uses [http://www.selenic.com/mercurial/wiki/index.cgi Mercurial] for source code management. You can find microformat generators, tests, and [http://suda.co.uk/projects/X2V/ Brian Suda's X2V] scripts in the repository at [http://hg.microformats.org]

== Mercurial ==
Mercurial offers binary packages and source code for Windows, Linux, and Mac OSX. You can read more about [http://www.selenic.com/mercurial/wiki/index.cgi/TutorialInstall how to install Mercurial] from their wiki.

== Checking out code ==
Once you have Mercurial installed, the quickest way to get started with the following recipe.

The first time you access a repository, you must first clone the repository on your local drive.

For example: to download the latest code for X2V, you would use the following:

<code>hg clone http://hg.microformats.org/x2v/</code>

Once you have cloned the repository, you can update your local code with the latest from the Microformats repository with:

<code>hg update http://hg.microformats.org/x2v/</code>

== Rake ==
For those of you with [http://rake.rubyforge.org/ Rake] installed on your machine you can take advantage of the Rakefile included with the Generators and X2V. The Rakefile makes two commands available:

# <code>rake hg:pull_update</code> -- Pull and update this repository. May fail if you need to merge
# <code>rake hg:push_update</code> -- Pushes this repository to microformats.org. Pulls and updates first

== Testing the XSLT scripts ==

The XSLT scripts in the mercurial repository are accompanied by Perl test scripts.
With these test scripts you can test the XSLT scripts against the tests from the tests repository using LibXSLT.
Various other XSLT engines are also supported: [http://4suite.org/ 4xslt], [http://saxon.sourceforge.net/ Saxon] (Java version), [http://xml.apache.org/xalan-j/ Xalan-J], [http://xml.apache.org/xalan-j/ Xalan-C].

=== Installing prerequisites ===

In order for the Perl scripts to work you'll need Perl 5.8
and the following additional modules: [http://cpan.uwinnipeg.ca/module/XML::LibXML XML::LibXML], [http://cpan.uwinnipeg.ca/module/XML::LibXSLT XML::LibXSLT],
[http://cpan.uwinnipeg.ca/module/Text::Diff Text::Diff].

==== MacOSX ====

Install [http://trac.macosforge.org/projects/macports/wiki/UsingMacPortsQuickStart MacPorts]
and then run <pre>sudo su
port install p5-xml-libxslt
port install p5-text-diff</pre>

===== *nix =====

Either use your distributions package management tool or
"<code>cpan install</code>" to install the Perl modules listed above.

===== Windows =====

Get ActivePerl 5.8 from http://www.activestate.com/Products/activeperl/.

Afterwards see http://theoryx5.uwinnipeg.ca/ppms/ for instructions on how to install the
additional modules.

You might also want to install [http://cpan.uwinnipeg.ca/module/Win32::Console::ANSI Win32::Console::ANSI].

=== Preparations ===
First you need to checkout both the tests and the XSLT repositories:

<pre>hg clone http://hg.microformats.org/x2v /home/johndoe/tests
hg clone http://hg.microformats.org/tests /home/johndoe/xslts</pre>

The test scripts are in the XSLT repositories, in order to tell them where
the test files are located you have to set the <code>MICROFORMATS_TESTS</code> environment variable.

On *nix and MacOSX (assumig you're using the bash shell): <pre>export MICROFORMATS_TESTS=/home/johndoe/tests</pre>
On Windows: <pre>set MICROFORMATS_TESTS=C:\path\to\tests</pre>

=== Running the test ===

First change to the directory where the XSLTs are located.
Afterwards you can start the test scripts with:
* <code>hcard/test.pl</code>
* <code>hcalendar/test-vcal.pl</code>
* <code>hatom/test.pl</code>

(On Windows: Use backslashes instead of forward slashes)

Here are some examples:

<pre>
./test.pl -x # Run all tests with libxslt
./test.pl -x 5 # Run tests 1 with all Engines
./test.pl --saxon --4xslt 1-3 12 15 # Run test 1, 2, 3, 12, 15 with Saxon and 4XSLT
./test.pl --xalan-c 8-18 -e 12-14 # Run test 8-11 and 15-18 with Xalan-C
</pre>

=== Using additional XSLT engines ===

If you want to use any XSLT engines (besides LibXSLT) you have to install them and make
sure that the can be launched from the test script.

For Java based XSLT engines you need to add the the engine's .jar file (saxon8.jar and xalan.jar respectively) to your <code>CLASSPATH</code>
environment variable. Enter
<pre>java net.sf.saxon.Transform
java org.apache.xalan.xslt.Process</pre> to test if Xalan-J and Saxon can be called by the test scripts.

For all other XSLT engines add the path to their "bin" directories to your <code>PATH</code>
environment variable.

Enter
<pre>4xslt
Xalan
</pre> into the console to test if 4xslt and Xalan-C can be called by the test scripts.

mercurial-quick-start

2007-07-25T15:37:32Z

RobertBachmann: /* Running Tests */

__NOTOC__
= HowTo: Download code from the repository =

'''I had a little difficulty checking out code from the [http://hg.microformats.org repository], so I created this page to help those who are new to Mercurial and the Microformats repository.'''

== Introduction ==
Microformats.org uses [http://www.selenic.com/mercurial/wiki/index.cgi Mercurial] for source code management. You can find microformat generators, tests, and [http://suda.co.uk/projects/X2V/ Brian Suda's X2V] scripts in the repository at [http://hg.microformats.org]

== Mercurial ==
Mercurial offers binary packages and source code for Windows, Linux, and Mac OSX. You can read more about [http://www.selenic.com/mercurial/wiki/index.cgi/TutorialInstall how to install Mercurial] from their wiki.

== Checking out code ==
Once you have Mercurial installed, the quickest way to get started with the following recipe.

The first time you access a repository, you must first clone the repository on your local drive.

For example: to download the latest code for X2V, you would use the following:

<code>hg clone http://hg.microformats.org/x2v/</code>

Once you have cloned the repository, you can update your local code with the latest from the Microformats repository with:

<code>hg update http://hg.microformats.org/x2v/</code>

== Rake ==
For those of you with [http://rake.rubyforge.org/ Rake] installed on your machine you can take advantage of the Rakefile included with the Generators and X2V. The Rakefile makes two commands available:

# <code>rake hg:pull_update</code> -- Pull and update this repository. May fail if you need to merge
# <code>rake hg:push_update</code> -- Pushes this repository to microformats.org. Pulls and updates first

== Testing the XSLT scripts ==

The XSLT scripts in the mercurial repository are accompanied by Perl test scripts.
With these test scripts you can test the XSLT scripts against the tests from the tests repository using LibXSLT.
Various other XSLT engines are also supported: [http://4suite.org/ 4xslt], [http://saxon.sourceforge.net/ Saxon] (Java version), [http://xml.apache.org/xalan-j/ Xalan-J], [http://xml.apache.org/xalan-j/ Xalan-C].

=== Installing prerequisites ===

In order for the Perl scripts to work you'll need Perl 5.8
and the following additional modules: [http://cpan.uwinnipeg.ca/module/XML::LibXML XML::LibXML], [http://cpan.uwinnipeg.ca/module/XML::LibXSLT XML::LibXSLT],
[http://cpan.uwinnipeg.ca/module/Text::Diff Text::Diff].

==== MacOSX ====

Install [http://trac.macosforge.org/projects/macports/wiki/UsingMacPortsQuickStart MacPorts]
and then run <pre>sudo su
port install p5-xml-libxslt
port install p5-text-diff</pre>

===== *nix =====

Either use your distributions package management tool or
"<code>cpan install</code>" to install the Perl modules listed above.

===== Windows =====

Get ActivePerl 5.8 from http://www.activestate.com/Products/activeperl/.

Afterwards see http://theoryx5.uwinnipeg.ca/ppms/ for instructions on how to install the
additional modules.

You might also want to install [http://cpan.uwinnipeg.ca/module/Win32::Console::ANSI Win32::Console::ANSI].

=== Preparations ===
First you need to checkout both the tests and the XSLT repositories:

<pre>hg clone http://hg.microformats.org/x2v /home/johndoe/tests
hg clone http://hg.microformats.org/tests /home/johndoe/xslts</pre>

The test scripts are in the XSLT repositories, in order to tell them where
the test files are located you have to set the <code>MICROFORMATS_TESTS</code> environment variable.

On *nix and MacOSX (assumig you're using the bash shell): <pre>export MICROFORMATS_TESTS=/home/johndoe/tests</pre>
On Windows: <pre>set MICROFORMATS_TESTS=C:\path\to\tests</pre>

=== Running the test ===

First change to the directory where the XSLTS XSLTs are located.
Afterwards you can start the test scripts with:
* <code>hcard/test.pl</code>
* <code>hcalendar/test-vcal.pl</code>
* <code>hatom/test.pl</code>

(On Windows: Use backslashes instead of forward slashes)

Here are some examples:

<pre>
./test.pl -x # Run all tests with libxslt
./test.pl -x 5 # Run tests 1 with all Engines
./test.pl --saxon --4xslt 1-3 12 15 # Run test 1, 2, 3, 12, 15 with Saxon and 4XSLT
./test.pl --xalan-c 8-18 -e 12-14 # Run test 8-11 and 15-18 with Xalan-C
</pre>

=== Using additional XSLT engines ===

If you want to use any XSLT engines (besides LibXSLT) you have to install them and make
sure that the can be launched from the test script.

For Java based XSLT engines you need to add the the engine's .jar file (saxon8.jar and xalan.jar respectively) to your <code>CLASSPATH</code>
environment variable. Enter
<pre>java net.sf.saxon.Transform
java org.apache.xalan.xslt.Process</pre> to test if Xalan-J and Saxon can be called by the test scripts.

For all other XSLT engines add the path to their "bin" directories to your <code>PATH</code>
environment variable.

Enter
<pre>4xslt
Xalan
</pre> into the console to test if 4xslt and Xalan-C can be called by the test scripts.

User:RobertBachmann

2007-07-23T14:31:20Z

RobertBachmann: pd

Robert Bachmann, http://rbach.priv.at/

{{public-domain-release}}

User:RobertBachmann

2007-07-23T14:28:52Z

RobertBachmann:

Robert Bachmann, http://rbach.priv.at/

to-do

2007-07-17T11:24:30Z

RobertBachmann: /* Robert Bachmann */ added to-do item

<h1>To Do</h1>

This page is for posting [[microformats]] related shared to do items. If you want to use this page for your microformats related to-do items, create a section with your name on it. The reason we are keeping these all on the same page is to make it easier to tell when people are working on similar things, and to make it more obvious when people help out with other people's tasks. In theory this probably won't scale, but let's first see how it does in practice. :) - [http://tantek.com Tantek]

__TOC__

== Lazyweb ==

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

=== for all microformats ===
* We have recently added a new mailing list called microformats-new. There may be some confusion surrounding this change, so it would be helpful to:
** Draft a message to be added to the confirm message sent when someone subscribes to any list including a welcome message, ground rules, topic for the subscribed list, and the topics for nearby lists.
** Add a faq entry somewhere on why the new list was created.
** Double check the wiki pages to make sure advice on mailing lists is accurate.
* quick and easy "how to" pages for each microformat. [[use]] is a good overall start.
* brief summary statements for each microformat that explain why it matters, what does it accomplish for the publisher.
* write up [http://microformats.org/discuss/ mailing-list] questions and answers in the appropriate [[faq]] pages.
* validators. See the hReview section below as there has been a request for an hReview validator in particular. See [http://norman.walsh.name/2006/04/13/validatingMicroformats Norman Walsh's blog post "Validating microformats"] for some valuable analysis and validation pseudo-code (prose description), which are useful steps towards building microformat validators.
* Add [http://verselogic.net/projects/wordpress/wordpress-openid-plugin/ OpenID] to Microformats Blog.
* Submit definitions of "mcroformat", and individual examples, to the [http://foldoc.org Free On-line Dictionary of Computing], acording to [http://foldoc.org/editing.html the Free On-line Dictionary of Computing guidelines]

=== hCard ===
* microformatted versions of conference pages
** Wait for confirmation from O'Reilly webmaster on revision of the [http://conferences.oreillynet.com/etel2006/ ETel] [http://conferences.oreillynet.com/pub/w/44/speakers.html speaker's page] with all the speakers marked up with [[hcard|hCard]] and links to "Add hCards to Address Book" etc., similar to the [http://tantek.com/microformats/2005/web2/speakers.html Web 2.0 speakers page which Tantek did a revision of last fall].
* vcard to hcard converter
** would be nice to have a web upload UI that would take one or more vCards from apple's address book and give them back to you as hCards
** [[User:RobertBachmann | RobertBachmann]] suggests starting points:
*** For Ruby: http://vpim.rubyforge.org/
*** For C: http://freshmeat.net/projects/libvc/
*** For Python: http://www.nongnu.org/python-pdi/
*** For PHP: http://pear.php.net/package/Contact_Vcard_Parse/
* add export support for microformats to [http://www.turingart.com/abForWeb_lan__en.htm AB to Web]
* A mash-up with google maps that will take any url with a hcard (or hcard's) and map the location(s) on a map (similar to [http://austin.adactio.com/ austin.adactio.com])

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

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

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

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

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

=== Yahoo Open Source Library Patches ===
Several of these could very much be improved with a little microformats markup. Do we just make patches and submit them? Contact Nate Koechley at Yahoo (see Tantek for contact info) to follow-up.

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

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

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

===rel-tagging on Wikipedia===
Somebody familiar with the "rel-tag" microformat might want to add details, and a link to the relevant page on this Wiki, to the [http://en.wikipedia.org/wiki/Tag_%28metadata%29 Wikipedia page on tagging]. [[User:AndyMabbett|Andy Mabbett]] 14:07, 3 Jan 2007 (PST)

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

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

=== protect the community ===
* Analyze [[Special:Recentchanges]] and [http://microformats.org/discuss mailing-lists] and:
** add to [[mailing-lists]] policies/guidelines accordingly.
** redirect and resolve threads accordingly per guidelines
** privately email violaters kindly asking them to improve their behavior
** work with admins on next steps for individuals negatively impacting the community
** recognize noisy/distracting threads on the email list, document responses/answers to such subjects on the appropriate page(s) on the wiki, and reply to those threads with the URLs to the documentation on the wiki. Putting the responses/answers on the wiki helps by hopefully providing preemptive answers to some who might reraise the subjects on the list in the future, and helps the community quickly terminate such threads by using the answers on the wiki.

=== help publishers ===
==== foldup cheatsheet ===
'''Next actions''': review all descriptions, property lists, examples in Erin's cheatsheet draft, give feedback back to Erin about her foldup cheatsheet, iterate, print, fold, distribute.

Help create a printable foldup cheatsheet of multiple microformats (ASAP, perhaps for [[events/2007-04-18-web-2-expo-dinner|Web 2.0 Expo Microformats dinner]]) that:
* prints onto both sides of a sheet of 8.5x11" paper (size chosen for US distribution, and because it folds nicely into 4ths sliced vertically, then 3rds sliced horizontally into a size approximating a business card, hoping to CC-by the whole thing so that others can do their own variants, perhaps for other paper sizes also)
* accordion folds first into 1/4 size along 3 vertical creases, then 1/3 size along 2 horizontal creases
* on each of the 8 vertical stripes (4 one side, 4 the other) of the sheet, info on each of the following microformats (it is assumed that [[hcard|hCard]] documentation will cover [[adr]], and [[geo]] also).
** people vs. other things
*** people-centric:
**** [[xfn|XFN]]
**** [[hcard|hCard]]([[adr]],[[geo]])
**** [[hcalendar|hCalendar]]
**** [[hresume|hResume]] + [[include-pattern]]
*** content-centric:
**** [[microformats]] list/overview
**** other common rels: [[rel-license]] [[rel-enclosure]] [[rel-tag]] [[rel-directory]]
**** [[hreview|hReview]] + [[xfolk|xFolk]]
**** [[hatom|hAtom]]
** original building blocks vs. newer
*** original:
**** [[microformats]] list/overview [[rel-license]] [[rel-tag]]
**** [[xfn|XFN]]
**** [[hcard|hCard]]([[adr]],[[geo]])
**** [[hcalendar|hCalendar]]
*** newer:
**** [[hreview|hReview]] + [[xfolk|xFolk]]
**** [[rel-directory]] [[rel-enclosure]]
**** [[hatom|hAtom]]
**** [[hresume|hResume]] + [[include-pattern]]
** other splits of 4 slices vs. 4 slices?
*** ...
*** ...
* each triple accordion fold section for a microformat should contain:
** property summary with required/optional singular/plural sub-properties (similar to current cheat sheet) + illustrative code sample with common properties
** list of properties, sub-properties with values and definitions of each
** URLs to spec, examples, implementations for more info.

Update: I made a folding cheat sheet to similar specifications. Not sure if it's 100% correct, it needs to be looked at for needed revisions. [http://erincaton.ca/media/cheatsheetHandout.pdf Cheat sheet PDF.] [[User:ErinCaton|ErinCaton]]

Perhaps [http://www.visibone.com/ Visibone] can be of some use? I can recommend their current products. --[[User:Gazza|Gazza]] 06:41, 7 Apr 2007 (PDT)

==== *-authoring microformats wiki pages ====
* [[hcard-authoring]] - '''next-actions''': add tips/instructions noted below.
** instructions for each property that is in [http://microformats.org/code/hcard/creator hCard creator] to begin with
** instructions for all other hCard properties
** a tutorial on creating an hCard for your site
*** specific instructions for common blogging platforms
** reference [[hcard-examples]] for more specific uses, and add to them accordingly
*** add an extended example to [[hcard-examples#Authors_of_Pages_and_Posts|contact info for a page]] with postal address, phone numbers, email address.

* [[hreview-authoring]] - '''next-action''': create a first draft minimal tutorial on how to author hReviews (e.g. at least for common properties) to blog reviews so that they'll be aggregated.

* [[hcalendar-authoring]] - '''next-action''': add tips/instructions for each property that is in [http://microformats.org/code/hcalendar/creator hCalendar creator].

* *-authoring for other reasonably well established microformats:
** [[xfolk-authoring]], [[hatom-authoring]]

==== help with microformat examples in the wild ====
Using the above updated [[authoring]] pages, get the community to help go over all "common" pages (both logged out and logged in states) of the following sites which have some microformats already, and verify each page is as microformatted as it can be with high fidelity [[hcalendar|hCalendar]] and [[hcard|hCard]] etc. Document full support of each implementation's microformats on the implementations page (perhaps create a separate page for each implementation, e.g. [[flickr]], [[upcoming]], [[eventful]] etc.) Document any exceptions as needed. In no particular order:
* Flickr.com (3.5m hCards)
* Upcoming.org (100k hCalendar events, 100k hCard venues)
** home page
* Eventful.com (100k hCalendar events, 100k hCard venues)
* Yahoo! Tech (300k products with hReviews)
* JudysBook.com (???k hReviews)
* ... lots more, get from "Implementations" and "Examples in the Wild" sections of specs.

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

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

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

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

=== iterate on current microformats ===
==== [[hcard|hCard]] ====
* [[hcard-examples]] '''next-actions''': update with examples described below
** add examples of [[hcard|hCard]]s with work telephone, mailing address etc.
** add examples of marking up an organization vs. a person, then link to it from [http://microformats.org/wiki/hcard#Organization_Contact_Info hCard spec section on Organization Contact Info].
** add example of organization-name and organization-unit usage.
* [[hcard-issues]] and [[hcard-feedback]]. '''next-actions''': resolve all issues and incorporate all feedback.
* [[hcard-brainstorming]] '''next-actions''': determine which brainstorms proposals to resolve in April, and which later
** need property for gender (see [[hcard-faq#How_is_gender_represented|proposal in hCard FAQ]] and discussion in [[hcard-issues]]) - use tags for now, add to hCard creator
** solve [[hcard-brainstorming#Auto-Discovery|autodiscovery]] of more canonical/thorough hCard
* [[hcard-examples-in-wild]]
** help dglazkov markup: http://glazkov.com/blog/archive/2003/12/17/147.aspx

==== [[hcalendar|hCalendar]] ====
'''Next-actions''':
* itemize a list of properties similar to the [[hcard#Property_List|hCard property list]], drawing upon hCalendar experience, iCal-BASIC draft(s), ietf-calsify mailing list and other sources to derive the precise list.
* formalize [http://microformats.org/wiki/hcalendar- brainstorming#Tabular_event_calendars]
* flesh out [[hcalendar-examples]] and do a once over on markup/presentation of what RFC2445 examples would look like
* need spec details and then [[hcalendar-examples]] of multi-instance [[hcalendar|hCalendar]] events
* need spec details and then [[hcalendar-examples]] of repeating events
* add explicit explanation and examples for LOCATION [[hcard|hCards]] and ATTENDEE [[hcard|hCards]], perhaps on a separate [[hcalendar-examples]] page.
* need to resolve all outstanding [[hcalendar-issues]] to-do items.
* create [[hcalendar-profile]] and have folks verify it. note that it will likely need reconciliation with the [[hcard-profile]], especially since [[hcalendar|hCalendar]] normatively depends on [[hcard|hCard]]. Probably makes sense to have a combined profile which hCalendar would use.

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

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

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

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

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

==== update specification section organization ====
'''Next-action''': work with Ryan, Ernie, Erin, and others who have made concrete helpful suggestions for reorganizing the information architecture / content-order / layout of specs for greater approachability/readability by a broader audience, to design an interative update to spec organizations, in particular, the introduction/boilerplate/headers. See below notes on hResume experiment in progress.

[[hresume|hResume]] has an experimental abbreviated intro/headers section, and links to more details further below, based on some ideas that Ryan King and I had for improving the readability of the microformats specifications. [[hreview|hReview]] has some similar improvements, but different. We need to:
# Figure out if the new intro/headers structure in [[hresume|hResume]] and/or [[hreview|hReview]] is an improvement, and if it could be better. Perhaps figure out the requirements for an intro/header section
#* Shorter tends to be better
#* Must be comprehensive enough to "print and read"
#* Must detail authorship/editorship
#* Must detail copyright/patent statements
# Write up a template - make it self-documenting per the requirements
# Update existing specifications with the new intro/headers structure.
## [[hcard|hCard]]
## [[hcalendar|hCalendar]]
## [[hreview|hReview]]

==== reorganizing Implementations sections ====
* sort implementations by authoring/creating/publishing, browsing/viewing, converting/importing, indexing/searching.

Hmmm... I like: '''A'''uthoring, '''B'''rowsing, '''C'''onverting, '''I'''ndexing, '''L'''ibraries (for developers), and '''P'''otential (for open source projects we want to add support to). Anybody have alternative suggestions for this vocabulary? I don't have a particularly strong preference so I'm going to go with these four until I find examples that don't fit, or someone suggests something better.

See: [http://microformats.org/wiki/hcalendar#Implementations hCalendar Implementations] for a first attempt at this. Assuming folks like that, we can go ahead with categorizing the implementations sections of other microformats specifications.

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

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

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

=== introduction / community ===

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

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

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

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

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

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

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

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

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

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

==Ryan==
=== wiki cleanup ===
* possibly move dead proposals off of homepage?

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

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

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

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

== Dimitri Glazkov ==

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

== Chris Messina ==

=== General ===

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

=== Campaigns ===

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

=== Wishlist ===

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

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

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

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

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

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

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

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

== 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 red links on [[Main_Page-fr]]
* localize a french version of the official website and migrate contents
** ask authorization to the authors
** migration could be done on any collaborative CMS
** test a cocomment system (based on local-wiki)
** complete with original links
* find experts for peer-reviewing
* update [http://fr.wikipedia.org/wiki/Microformats French-wikipedia:Microformats] via cowriting [http://fr.wikipedia.org/wiki/Discuter:Microformats on discussion page] (directly originated from the english article) + french examples to be found + local resources.
** create hCard, hCalendar... and all red link pages on french wikipedia
* find help and maintain http://www.communitywiki.org/MicroFormats
* localize [[species-fr]] and related pages
* clean all dead links pointing to elanceur.org

== Frances Berriman ==

[[User:Phae|Frances Berriman]]

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

== Ben West (bewest) ==

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

=== Expore Microformat Deployment Issues ===
How does who determine the status of work going through some stage of the process? When does a format move from draft to "full spec"? Who decides? What are the qualitative and quantitative features that characterize work in different stages, especially as a spec nears deployment as "full spec". What makes this pronouncement more than a mythical blessing? What quantitative analyses can be provided to validate deployment? Today, we have powerful agents capable of processing huge amounts of information on the web. Should we be using these to measure published marketshare? What role should tools and test suites play in deploying microformats?

=== Vocabulary ===
A lot of knowledge work is about maintaining sets of vocabulary. Now that the vocabulary is emerging, it may be time start making sure everyone is "on the same page," especially since some of the language is highly symbolic.
Terms:
* "boil the ocean" A huge task. "A phrase used in the industry to describe an attempt at something that is way too ambitious. For example, "They're trying to get their site launched by COMDEX. They could easier boil the ocean." from <http://www.netlingo.com/right.cfm?term=boil%20the%20ocean>
* microformats: more than one microformat
* microformat: see my definition on http://microformats.org/wiki/what-are-microformats#BenWest
* data fidelity: the extent to which a data format might be considered lossy. eg HTML is often seen as a lossy format because the information parsed out of a resource may not fully match the information orginally encoded. Non-lossy formats have a very high data fidelity, while lossy formats have low data fidelity. Microformats seek to increase data fidelity of html.
* market: the locus of economic forces

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

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

=== Information Architecture ===
'''Help Welcomed! Please leave your name'''
Add complaints to [[wiki-feedback]]!
Helping to make the wiki easier to use. I'd like to see the main page more towards a format like http://simile.mit.edu/solvent/ with the big questions right out front:
* What Is This?
* What can I do here?
* Is there a demo?
* Where can I learn more?
I'd like to change the front page to this kind of design.
==== Support Pages ====
There are several categories of things in the wiki. Can we enumerate them?
* About the Community
** Where to find information.
** Who are the stake holders?
** FAQs
* Web/Architectural Philosophy
** Community Principles
** Why are we doing this?
** XML and Namespaces
** Semantic XHTML
** Common Misconceptions
** Concession and Disposition of Criticism
** FAQs
* Specs
** Examples
** Discussion
** Exploration
** Use Cases
** Implementations
** The spec itself.

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

Can others agree and or refine this list? Should I take it to the -discuss list? How do we create consensus on how the wiki should be organized in order to make it more usable? And how can we turn that consensus into actionable changes?

The wiki should also capture wisdom that stems from discussions that don't produce microformats. For example, Chris Messina suggests a "Best Of" page suitable for capturing this kind of wisdom. I think we can think of a given microformat as being at a place in a spectrum that ranges from "not yet thought of", to "interesting but needs work," or even "rejected", and of course including all the stages familiar to the microformats processes (eg examples, brainstorming, etc...).
If there were such a page would it:
* Belong to a microformat? (eg hcard-bestof)
* or to the global namespace? (eg /wiki/wisdom/foobar-format)
(I think Chris Messina suggests that it belongs to a given microformat, but then how do we collect wisdom from non-microformats?)

Considering that the wiki page named with the microformat (i.e. /wiki/hcard) is the one that people will mostly likely look to first for learning about a particular format, I'd think it'd make more sense and create a more welcoming feel to convert these pages to an intro page introducing the format for the beginner and linking to resources like tutorials and creators. Spec pages would then be relocated to wiki/*-spec -- [[User:Cgriego|Cgriego]] 13:25, 16 Oct 2006 (PDT)

====Mike Schinkel's Comments====

My suggestion on the list was for us to use a convention that the entry page (i.e.
http://microformats.org/wiki/hcard) would be an index into a list of
(psuedo) standardized sub pages so that it would be very people to
find what is important to them. For example, is a list of potential sub pages:

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

These pages would be located respectively at

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

Please note I am suggesting an architecture not a specific list of sub pages. The list of sub pages should be defined by both reviewing existing information during site reorganization, and then via discussion on the list in an attempt to discover and extract which sub pages are needed for most/all microformats.

'''NOTE''': This differs from above in that the spec if not viewed as a top level structure but instead the microformat itself and the spec would be under the microformat. In this context "microformat" is a more abstract concept and "spec" is a more concrete thing. Another way to think about it would be that each microformat would have it's own mini home page and then things like "spec" are the pages listed on its home page.

== Matt Dertinger (Thewhoo) ==

[[User:Thewhoo]]

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

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

== Henri Bergius ==

[[User:HenriBergius|Henri Bergius]]

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

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

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

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

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

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

to-do

2007-07-17T11:10:11Z

RobertBachmann: /* Robert Bachmann */ updated 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 ===
* We have recently added a new mailing list called microformats-new. There may be some confusion surrounding this change, so it would be helpful to:
** Draft a message to be added to the confirm message sent when someone subscribes to any list including a welcome message, ground rules, topic for the subscribed list, and the topics for nearby lists.
** Add a faq entry somewhere on why the new list was created.
** Double check the wiki pages to make sure advice on mailing lists is accurate.
* quick and easy "how to" pages for each microformat. [[use]] is a good overall start.
* brief summary statements for each microformat that explain why it matters, what does it accomplish for the publisher.
* write up [http://microformats.org/discuss/ mailing-list] questions and answers in the appropriate [[faq]] pages.
* validators. See the hReview section below as there has been a request for an hReview validator in particular. See [http://norman.walsh.name/2006/04/13/validatingMicroformats Norman Walsh's blog post "Validating microformats"] for some valuable analysis and validation pseudo-code (prose description), which are useful steps towards building microformat validators.
* Add [http://verselogic.net/projects/wordpress/wordpress-openid-plugin/ OpenID] to Microformats Blog.
* Submit definitions of "mcroformat", and individual examples, to the [http://foldoc.org Free On-line Dictionary of Computing], acording to [http://foldoc.org/editing.html the Free On-line Dictionary of Computing guidelines]

=== hCard ===
* microformatted versions of conference pages
** Wait for confirmation from O'Reilly webmaster on revision of the [http://conferences.oreillynet.com/etel2006/ ETel] [http://conferences.oreillynet.com/pub/w/44/speakers.html speaker's page] with all the speakers marked up with [[hcard|hCard]] and links to "Add hCards to Address Book" etc., similar to the [http://tantek.com/microformats/2005/web2/speakers.html Web 2.0 speakers page which Tantek did a revision of last fall].
* vcard to hcard converter
** would be nice to have a web upload UI that would take one or more vCards from apple's address book and give them back to you as hCards
** [[User:RobertBachmann | RobertBachmann]] suggests starting points:
*** For Ruby: http://vpim.rubyforge.org/
*** For C: http://freshmeat.net/projects/libvc/
*** For Python: http://www.nongnu.org/python-pdi/
*** For PHP: http://pear.php.net/package/Contact_Vcard_Parse/
* add export support for microformats to [http://www.turingart.com/abForWeb_lan__en.htm AB to Web]
* A mash-up with google maps that will take any url with a hcard (or hcard's) and map the location(s) on a map (similar to [http://austin.adactio.com/ austin.adactio.com])

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

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

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

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

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

=== Yahoo Open Source Library Patches ===
Several of these could very much be improved with a little microformats markup. Do we just make patches and submit them? Contact Nate Koechley at Yahoo (see Tantek for contact info) to follow-up.

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

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

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

===rel-tagging on Wikipedia===
Somebody familiar with the "rel-tag" microformat might want to add details, and a link to the relevant page on this Wiki, to the [http://en.wikipedia.org/wiki/Tag_%28metadata%29 Wikipedia page on tagging]. [[User:AndyMabbett|Andy Mabbett]] 14:07, 3 Jan 2007 (PST)

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

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

=== protect the community ===
* Analyze [[Special:Recentchanges]] and [http://microformats.org/discuss mailing-lists] and:
** add to [[mailing-lists]] policies/guidelines accordingly.
** redirect and resolve threads accordingly per guidelines
** privately email violaters kindly asking them to improve their behavior
** work with admins on next steps for individuals negatively impacting the community
** recognize noisy/distracting threads on the email list, document responses/answers to such subjects on the appropriate page(s) on the wiki, and reply to those threads with the URLs to the documentation on the wiki. Putting the responses/answers on the wiki helps by hopefully providing preemptive answers to some who might reraise the subjects on the list in the future, and helps the community quickly terminate such threads by using the answers on the wiki.

=== help publishers ===
==== foldup cheatsheet ===
'''Next actions''': review all descriptions, property lists, examples in Erin's cheatsheet draft, give feedback back to Erin about her foldup cheatsheet, iterate, print, fold, distribute.

Help create a printable foldup cheatsheet of multiple microformats (ASAP, perhaps for [[events/2007-04-18-web-2-expo-dinner|Web 2.0 Expo Microformats dinner]]) that:
* prints onto both sides of a sheet of 8.5x11" paper (size chosen for US distribution, and because it folds nicely into 4ths sliced vertically, then 3rds sliced horizontally into a size approximating a business card, hoping to CC-by the whole thing so that others can do their own variants, perhaps for other paper sizes also)
* accordion folds first into 1/4 size along 3 vertical creases, then 1/3 size along 2 horizontal creases
* on each of the 8 vertical stripes (4 one side, 4 the other) of the sheet, info on each of the following microformats (it is assumed that [[hcard|hCard]] documentation will cover [[adr]], and [[geo]] also).
** people vs. other things
*** people-centric:
**** [[xfn|XFN]]
**** [[hcard|hCard]]([[adr]],[[geo]])
**** [[hcalendar|hCalendar]]
**** [[hresume|hResume]] + [[include-pattern]]
*** content-centric:
**** [[microformats]] list/overview
**** other common rels: [[rel-license]] [[rel-enclosure]] [[rel-tag]] [[rel-directory]]
**** [[hreview|hReview]] + [[xfolk|xFolk]]
**** [[hatom|hAtom]]
** original building blocks vs. newer
*** original:
**** [[microformats]] list/overview [[rel-license]] [[rel-tag]]
**** [[xfn|XFN]]
**** [[hcard|hCard]]([[adr]],[[geo]])
**** [[hcalendar|hCalendar]]
*** newer:
**** [[hreview|hReview]] + [[xfolk|xFolk]]
**** [[rel-directory]] [[rel-enclosure]]
**** [[hatom|hAtom]]
**** [[hresume|hResume]] + [[include-pattern]]
** other splits of 4 slices vs. 4 slices?
*** ...
*** ...
* each triple accordion fold section for a microformat should contain:
** property summary with required/optional singular/plural sub-properties (similar to current cheat sheet) + illustrative code sample with common properties
** list of properties, sub-properties with values and definitions of each
** URLs to spec, examples, implementations for more info.

Update: I made a folding cheat sheet to similar specifications. Not sure if it's 100% correct, it needs to be looked at for needed revisions. [http://erincaton.ca/media/cheatsheetHandout.pdf Cheat sheet PDF.] [[User:ErinCaton|ErinCaton]]

Perhaps [http://www.visibone.com/ Visibone] can be of some use? I can recommend their current products. --[[User:Gazza|Gazza]] 06:41, 7 Apr 2007 (PDT)

==== *-authoring microformats wiki pages ====
* [[hcard-authoring]] - '''next-actions''': add tips/instructions noted below.
** instructions for each property that is in [http://microformats.org/code/hcard/creator hCard creator] to begin with
** instructions for all other hCard properties
** a tutorial on creating an hCard for your site
*** specific instructions for common blogging platforms
** reference [[hcard-examples]] for more specific uses, and add to them accordingly
*** add an extended example to [[hcard-examples#Authors_of_Pages_and_Posts|contact info for a page]] with postal address, phone numbers, email address.

* [[hreview-authoring]] - '''next-action''': create a first draft minimal tutorial on how to author hReviews (e.g. at least for common properties) to blog reviews so that they'll be aggregated.

* [[hcalendar-authoring]] - '''next-action''': add tips/instructions for each property that is in [http://microformats.org/code/hcalendar/creator hCalendar creator].

* *-authoring for other reasonably well established microformats:
** [[xfolk-authoring]], [[hatom-authoring]]

==== help with microformat examples in the wild ====
Using the above updated [[authoring]] pages, get the community to help go over all "common" pages (both logged out and logged in states) of the following sites which have some microformats already, and verify each page is as microformatted as it can be with high fidelity [[hcalendar|hCalendar]] and [[hcard|hCard]] etc. Document full support of each implementation's microformats on the implementations page (perhaps create a separate page for each implementation, e.g. [[flickr]], [[upcoming]], [[eventful]] etc.) Document any exceptions as needed. In no particular order:
* Flickr.com (3.5m hCards)
* Upcoming.org (100k hCalendar events, 100k hCard venues)
** home page
* Eventful.com (100k hCalendar events, 100k hCard venues)
* Yahoo! Tech (300k products with hReviews)
* JudysBook.com (???k hReviews)
* ... lots more, get from "Implementations" and "Examples in the Wild" sections of specs.

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

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

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

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

=== iterate on current microformats ===
==== [[hcard|hCard]] ====
* [[hcard-examples]] '''next-actions''': update with examples described below
** add examples of [[hcard|hCard]]s with work telephone, mailing address etc.
** add examples of marking up an organization vs. a person, then link to it from [http://microformats.org/wiki/hcard#Organization_Contact_Info hCard spec section on Organization Contact Info].
** add example of organization-name and organization-unit usage.
* [[hcard-issues]] and [[hcard-feedback]]. '''next-actions''': resolve all issues and incorporate all feedback.
* [[hcard-brainstorming]] '''next-actions''': determine which brainstorms proposals to resolve in April, and which later
** need property for gender (see [[hcard-faq#How_is_gender_represented|proposal in hCard FAQ]] and discussion in [[hcard-issues]]) - use tags for now, add to hCard creator
** solve [[hcard-brainstorming#Auto-Discovery|autodiscovery]] of more canonical/thorough hCard
* [[hcard-examples-in-wild]]
** help dglazkov markup: http://glazkov.com/blog/archive/2003/12/17/147.aspx

==== [[hcalendar|hCalendar]] ====
'''Next-actions''':
* itemize a list of properties similar to the [[hcard#Property_List|hCard property list]], drawing upon hCalendar experience, iCal-BASIC draft(s), ietf-calsify mailing list and other sources to derive the precise list.
* formalize [http://microformats.org/wiki/hcalendar- brainstorming#Tabular_event_calendars]
* flesh out [[hcalendar-examples]] and do a once over on markup/presentation of what RFC2445 examples would look like
* need spec details and then [[hcalendar-examples]] of multi-instance [[hcalendar|hCalendar]] events
* need spec details and then [[hcalendar-examples]] of repeating events
* add explicit explanation and examples for LOCATION [[hcard|hCards]] and ATTENDEE [[hcard|hCards]], perhaps on a separate [[hcalendar-examples]] page.
* need to resolve all outstanding [[hcalendar-issues]] to-do items.
* create [[hcalendar-profile]] and have folks verify it. note that it will likely need reconciliation with the [[hcard-profile]], especially since [[hcalendar|hCalendar]] normatively depends on [[hcard|hCard]]. Probably makes sense to have a combined profile which hCalendar would use.

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

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

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

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

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

==== update specification section organization ====
'''Next-action''': work with Ryan, Ernie, Erin, and others who have made concrete helpful suggestions for reorganizing the information architecture / content-order / layout of specs for greater approachability/readability by a broader audience, to design an interative update to spec organizations, in particular, the introduction/boilerplate/headers. See below notes on hResume experiment in progress.

[[hresume|hResume]] has an experimental abbreviated intro/headers section, and links to more details further below, based on some ideas that Ryan King and I had for improving the readability of the microformats specifications. [[hreview|hReview]] has some similar improvements, but different. We need to:
# Figure out if the new intro/headers structure in [[hresume|hResume]] and/or [[hreview|hReview]] is an improvement, and if it could be better. Perhaps figure out the requirements for an intro/header section
#* Shorter tends to be better
#* Must be comprehensive enough to "print and read"
#* Must detail authorship/editorship
#* Must detail copyright/patent statements
# Write up a template - make it self-documenting per the requirements
# Update existing specifications with the new intro/headers structure.
## [[hcard|hCard]]
## [[hcalendar|hCalendar]]
## [[hreview|hReview]]

==== reorganizing Implementations sections ====
* sort implementations by authoring/creating/publishing, browsing/viewing, converting/importing, indexing/searching.

Hmmm... I like: '''A'''uthoring, '''B'''rowsing, '''C'''onverting, '''I'''ndexing, '''L'''ibraries (for developers), and '''P'''otential (for open source projects we want to add support to). Anybody have alternative suggestions for this vocabulary? I don't have a particularly strong preference so I'm going to go with these four until I find examples that don't fit, or someone suggests something better.

See: [http://microformats.org/wiki/hcalendar#Implementations hCalendar Implementations] for a first attempt at this. Assuming folks like that, we can go ahead with categorizing the implementations sections of other microformats specifications.

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

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

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

=== introduction / community ===

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

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

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

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

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

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

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

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

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

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

==Ryan==
=== wiki cleanup ===
* possibly move dead proposals off of homepage?

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

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

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

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

== Dimitri Glazkov ==

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

== Chris Messina ==

=== General ===

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

=== Campaigns ===

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

=== Wishlist ===

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

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

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

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

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

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

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

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

== 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 red links on [[Main_Page-fr]]
* localize a french version of the official website and migrate contents
** ask authorization to the authors
** migration could be done on any collaborative CMS
** test a cocomment system (based on local-wiki)
** complete with original links
* find experts for peer-reviewing
* update [http://fr.wikipedia.org/wiki/Microformats French-wikipedia:Microformats] via cowriting [http://fr.wikipedia.org/wiki/Discuter:Microformats on discussion page] (directly originated from the english article) + french examples to be found + local resources.
** create hCard, hCalendar... and all red link pages on french wikipedia
* find help and maintain http://www.communitywiki.org/MicroFormats
* localize [[species-fr]] and related pages
* clean all dead links pointing to elanceur.org

== Frances Berriman ==

[[User:Phae|Frances Berriman]]

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

== Ben West (bewest) ==

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

=== Expore Microformat Deployment Issues ===
How does who determine the status of work going through some stage of the process? When does a format move from draft to "full spec"? Who decides? What are the qualitative and quantitative features that characterize work in different stages, especially as a spec nears deployment as "full spec". What makes this pronouncement more than a mythical blessing? What quantitative analyses can be provided to validate deployment? Today, we have powerful agents capable of processing huge amounts of information on the web. Should we be using these to measure published marketshare? What role should tools and test suites play in deploying microformats?

=== Vocabulary ===
A lot of knowledge work is about maintaining sets of vocabulary. Now that the vocabulary is emerging, it may be time start making sure everyone is "on the same page," especially since some of the language is highly symbolic.
Terms:
* "boil the ocean" A huge task. "A phrase used in the industry to describe an attempt at something that is way too ambitious. For example, "They're trying to get their site launched by COMDEX. They could easier boil the ocean." from <http://www.netlingo.com/right.cfm?term=boil%20the%20ocean>
* microformats: more than one microformat
* microformat: see my definition on http://microformats.org/wiki/what-are-microformats#BenWest
* data fidelity: the extent to which a data format might be considered lossy. eg HTML is often seen as a lossy format because the information parsed out of a resource may not fully match the information orginally encoded. Non-lossy formats have a very high data fidelity, while lossy formats have low data fidelity. Microformats seek to increase data fidelity of html.
* market: the locus of economic forces

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

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

=== Information Architecture ===
'''Help Welcomed! Please leave your name'''
Add complaints to [[wiki-feedback]]!
Helping to make the wiki easier to use. I'd like to see the main page more towards a format like http://simile.mit.edu/solvent/ with the big questions right out front:
* What Is This?
* What can I do here?
* Is there a demo?
* Where can I learn more?
I'd like to change the front page to this kind of design.
==== Support Pages ====
There are several categories of things in the wiki. Can we enumerate them?
* About the Community
** Where to find information.
** Who are the stake holders?
** FAQs
* Web/Architectural Philosophy
** Community Principles
** Why are we doing this?
** XML and Namespaces
** Semantic XHTML
** Common Misconceptions
** Concession and Disposition of Criticism
** FAQs
* Specs
** Examples
** Discussion
** Exploration
** Use Cases
** Implementations
** The spec itself.

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

Can others agree and or refine this list? Should I take it to the -discuss list? How do we create consensus on how the wiki should be organized in order to make it more usable? And how can we turn that consensus into actionable changes?

The wiki should also capture wisdom that stems from discussions that don't produce microformats. For example, Chris Messina suggests a "Best Of" page suitable for capturing this kind of wisdom. I think we can think of a given microformat as being at a place in a spectrum that ranges from "not yet thought of", to "interesting but needs work," or even "rejected", and of course including all the stages familiar to the microformats processes (eg examples, brainstorming, etc...).
If there were such a page would it:
* Belong to a microformat? (eg hcard-bestof)
* or to the global namespace? (eg /wiki/wisdom/foobar-format)
(I think Chris Messina suggests that it belongs to a given microformat, but then how do we collect wisdom from non-microformats?)

Considering that the wiki page named with the microformat (i.e. /wiki/hcard) is the one that people will mostly likely look to first for learning about a particular format, I'd think it'd make more sense and create a more welcoming feel to convert these pages to an intro page introducing the format for the beginner and linking to resources like tutorials and creators. Spec pages would then be relocated to wiki/*-spec -- [[User:Cgriego|Cgriego]] 13:25, 16 Oct 2006 (PDT)

====Mike Schinkel's Comments====

My suggestion on the list was for us to use a convention that the entry page (i.e.
http://microformats.org/wiki/hcard) would be an index into a list of
(psuedo) standardized sub pages so that it would be very people to
find what is important to them. For example, is a list of potential sub pages:

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

These pages would be located respectively at

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

Please note I am suggesting an architecture not a specific list of sub pages. The list of sub pages should be defined by both reviewing existing information during site reorganization, and then via discussion on the list in an attempt to discover and extract which sub pages are needed for most/all microformats.

'''NOTE''': This differs from above in that the spec if not viewed as a top level structure but instead the microformat itself and the spec would be under the microformat. In this context "microformat" is a more abstract concept and "spec" is a more concrete thing. Another way to think about it would be that each microformat would have it's own mini home page and then things like "spec" are the pages listed on its home page.

== Matt Dertinger (Thewhoo) ==

[[User:Thewhoo]]

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

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

== Henri Bergius ==

[[User:HenriBergius|Henri Bergius]]

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

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

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

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

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

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

to-do

2007-07-17T10:58:24Z

RobertBachmann: /* hAtom2Atom */ Responses to comments

<h1>To Do</h1>

This page is for posting [[microformats]] related shared to do items. If you want to use this page for your microformats related to-do items, create a section with your name on it. The reason we are keeping these all on the same page is to make it easier to tell when people are working on similar things, and to make it more obvious when people help out with other people's tasks. In theory this probably won't scale, but let's first see how it does in practice. :) - [http://tantek.com Tantek]

__TOC__

== Lazyweb ==

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

=== for all microformats ===
* We have recently added a new mailing list called microformats-new. There may be some confusion surrounding this change, so it would be helpful to:
** Draft a message to be added to the confirm message sent when someone subscribes to any list including a welcome message, ground rules, topic for the subscribed list, and the topics for nearby lists.
** Add a faq entry somewhere on why the new list was created.
** Double check the wiki pages to make sure advice on mailing lists is accurate.
* quick and easy "how to" pages for each microformat. [[use]] is a good overall start.
* brief summary statements for each microformat that explain why it matters, what does it accomplish for the publisher.
* write up [http://microformats.org/discuss/ mailing-list] questions and answers in the appropriate [[faq]] pages.
* validators. See the hReview section below as there has been a request for an hReview validator in particular. See [http://norman.walsh.name/2006/04/13/validatingMicroformats Norman Walsh's blog post "Validating microformats"] for some valuable analysis and validation pseudo-code (prose description), which are useful steps towards building microformat validators.
* Add [http://verselogic.net/projects/wordpress/wordpress-openid-plugin/ OpenID] to Microformats Blog.
* Submit definitions of "mcroformat", and individual examples, to the [http://foldoc.org Free On-line Dictionary of Computing], acording to [http://foldoc.org/editing.html the Free On-line Dictionary of Computing guidelines]

=== hCard ===
* microformatted versions of conference pages
** Wait for confirmation from O'Reilly webmaster on revision of the [http://conferences.oreillynet.com/etel2006/ ETel] [http://conferences.oreillynet.com/pub/w/44/speakers.html speaker's page] with all the speakers marked up with [[hcard|hCard]] and links to "Add hCards to Address Book" etc., similar to the [http://tantek.com/microformats/2005/web2/speakers.html Web 2.0 speakers page which Tantek did a revision of last fall].
* vcard to hcard converter
** would be nice to have a web upload UI that would take one or more vCards from apple's address book and give them back to you as hCards
** [[User:RobertBachmann | RobertBachmann]] suggests starting points:
*** For Ruby: http://vpim.rubyforge.org/
*** For C: http://freshmeat.net/projects/libvc/
*** For Python: http://www.nongnu.org/python-pdi/
*** For PHP: http://pear.php.net/package/Contact_Vcard_Parse/
* add export support for microformats to [http://www.turingart.com/abForWeb_lan__en.htm AB to Web]
* A mash-up with google maps that will take any url with a hcard (or hcard's) and map the location(s) on a map (similar to [http://austin.adactio.com/ austin.adactio.com])

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

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

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

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

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

=== Yahoo Open Source Library Patches ===
Several of these could very much be improved with a little microformats markup. Do we just make patches and submit them? Contact Nate Koechley at Yahoo (see Tantek for contact info) to follow-up.

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

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

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

===rel-tagging on Wikipedia===
Somebody familiar with the "rel-tag" microformat might want to add details, and a link to the relevant page on this Wiki, to the [http://en.wikipedia.org/wiki/Tag_%28metadata%29 Wikipedia page on tagging]. [[User:AndyMabbett|Andy Mabbett]] 14:07, 3 Jan 2007 (PST)

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

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

=== protect the community ===
* Analyze [[Special:Recentchanges]] and [http://microformats.org/discuss mailing-lists] and:
** add to [[mailing-lists]] policies/guidelines accordingly.
** redirect and resolve threads accordingly per guidelines
** privately email violaters kindly asking them to improve their behavior
** work with admins on next steps for individuals negatively impacting the community
** recognize noisy/distracting threads on the email list, document responses/answers to such subjects on the appropriate page(s) on the wiki, and reply to those threads with the URLs to the documentation on the wiki. Putting the responses/answers on the wiki helps by hopefully providing preemptive answers to some who might reraise the subjects on the list in the future, and helps the community quickly terminate such threads by using the answers on the wiki.

=== help publishers ===
==== foldup cheatsheet ===
'''Next actions''': review all descriptions, property lists, examples in Erin's cheatsheet draft, give feedback back to Erin about her foldup cheatsheet, iterate, print, fold, distribute.

Help create a printable foldup cheatsheet of multiple microformats (ASAP, perhaps for [[events/2007-04-18-web-2-expo-dinner|Web 2.0 Expo Microformats dinner]]) that:
* prints onto both sides of a sheet of 8.5x11" paper (size chosen for US distribution, and because it folds nicely into 4ths sliced vertically, then 3rds sliced horizontally into a size approximating a business card, hoping to CC-by the whole thing so that others can do their own variants, perhaps for other paper sizes also)
* accordion folds first into 1/4 size along 3 vertical creases, then 1/3 size along 2 horizontal creases
* on each of the 8 vertical stripes (4 one side, 4 the other) of the sheet, info on each of the following microformats (it is assumed that [[hcard|hCard]] documentation will cover [[adr]], and [[geo]] also).
** people vs. other things
*** people-centric:
**** [[xfn|XFN]]
**** [[hcard|hCard]]([[adr]],[[geo]])
**** [[hcalendar|hCalendar]]
**** [[hresume|hResume]] + [[include-pattern]]
*** content-centric:
**** [[microformats]] list/overview
**** other common rels: [[rel-license]] [[rel-enclosure]] [[rel-tag]] [[rel-directory]]
**** [[hreview|hReview]] + [[xfolk|xFolk]]
**** [[hatom|hAtom]]
** original building blocks vs. newer
*** original:
**** [[microformats]] list/overview [[rel-license]] [[rel-tag]]
**** [[xfn|XFN]]
**** [[hcard|hCard]]([[adr]],[[geo]])
**** [[hcalendar|hCalendar]]
*** newer:
**** [[hreview|hReview]] + [[xfolk|xFolk]]
**** [[rel-directory]] [[rel-enclosure]]
**** [[hatom|hAtom]]
**** [[hresume|hResume]] + [[include-pattern]]
** other splits of 4 slices vs. 4 slices?
*** ...
*** ...
* each triple accordion fold section for a microformat should contain:
** property summary with required/optional singular/plural sub-properties (similar to current cheat sheet) + illustrative code sample with common properties
** list of properties, sub-properties with values and definitions of each
** URLs to spec, examples, implementations for more info.

Update: I made a folding cheat sheet to similar specifications. Not sure if it's 100% correct, it needs to be looked at for needed revisions. [http://erincaton.ca/media/cheatsheetHandout.pdf Cheat sheet PDF.] [[User:ErinCaton|ErinCaton]]

Perhaps [http://www.visibone.com/ Visibone] can be of some use? I can recommend their current products. --[[User:Gazza|Gazza]] 06:41, 7 Apr 2007 (PDT)

==== *-authoring microformats wiki pages ====
* [[hcard-authoring]] - '''next-actions''': add tips/instructions noted below.
** instructions for each property that is in [http://microformats.org/code/hcard/creator hCard creator] to begin with
** instructions for all other hCard properties
** a tutorial on creating an hCard for your site
*** specific instructions for common blogging platforms
** reference [[hcard-examples]] for more specific uses, and add to them accordingly
*** add an extended example to [[hcard-examples#Authors_of_Pages_and_Posts|contact info for a page]] with postal address, phone numbers, email address.

* [[hreview-authoring]] - '''next-action''': create a first draft minimal tutorial on how to author hReviews (e.g. at least for common properties) to blog reviews so that they'll be aggregated.

* [[hcalendar-authoring]] - '''next-action''': add tips/instructions for each property that is in [http://microformats.org/code/hcalendar/creator hCalendar creator].

* *-authoring for other reasonably well established microformats:
** [[xfolk-authoring]], [[hatom-authoring]]

==== help with microformat examples in the wild ====
Using the above updated [[authoring]] pages, get the community to help go over all "common" pages (both logged out and logged in states) of the following sites which have some microformats already, and verify each page is as microformatted as it can be with high fidelity [[hcalendar|hCalendar]] and [[hcard|hCard]] etc. Document full support of each implementation's microformats on the implementations page (perhaps create a separate page for each implementation, e.g. [[flickr]], [[upcoming]], [[eventful]] etc.) Document any exceptions as needed. In no particular order:
* Flickr.com (3.5m hCards)
* Upcoming.org (100k hCalendar events, 100k hCard venues)
** home page
* Eventful.com (100k hCalendar events, 100k hCard venues)
* Yahoo! Tech (300k products with hReviews)
* JudysBook.com (???k hReviews)
* ... lots more, get from "Implementations" and "Examples in the Wild" sections of specs.

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

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

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

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

=== iterate on current microformats ===
==== [[hcard|hCard]] ====
* [[hcard-examples]] '''next-actions''': update with examples described below
** add examples of [[hcard|hCard]]s with work telephone, mailing address etc.
** add examples of marking up an organization vs. a person, then link to it from [http://microformats.org/wiki/hcard#Organization_Contact_Info hCard spec section on Organization Contact Info].
** add example of organization-name and organization-unit usage.
* [[hcard-issues]] and [[hcard-feedback]]. '''next-actions''': resolve all issues and incorporate all feedback.
* [[hcard-brainstorming]] '''next-actions''': determine which brainstorms proposals to resolve in April, and which later
** need property for gender (see [[hcard-faq#How_is_gender_represented|proposal in hCard FAQ]] and discussion in [[hcard-issues]]) - use tags for now, add to hCard creator
** solve [[hcard-brainstorming#Auto-Discovery|autodiscovery]] of more canonical/thorough hCard
* [[hcard-examples-in-wild]]
** help dglazkov markup: http://glazkov.com/blog/archive/2003/12/17/147.aspx

==== [[hcalendar|hCalendar]] ====
'''Next-actions''':
* itemize a list of properties similar to the [[hcard#Property_List|hCard property list]], drawing upon hCalendar experience, iCal-BASIC draft(s), ietf-calsify mailing list and other sources to derive the precise list.
* formalize [http://microformats.org/wiki/hcalendar- brainstorming#Tabular_event_calendars]
* flesh out [[hcalendar-examples]] and do a once over on markup/presentation of what RFC2445 examples would look like
* need spec details and then [[hcalendar-examples]] of multi-instance [[hcalendar|hCalendar]] events
* need spec details and then [[hcalendar-examples]] of repeating events
* add explicit explanation and examples for LOCATION [[hcard|hCards]] and ATTENDEE [[hcard|hCards]], perhaps on a separate [[hcalendar-examples]] page.
* need to resolve all outstanding [[hcalendar-issues]] to-do items.
* create [[hcalendar-profile]] and have folks verify it. note that it will likely need reconciliation with the [[hcard-profile]], especially since [[hcalendar|hCalendar]] normatively depends on [[hcard|hCard]]. Probably makes sense to have a combined profile which hCalendar would use.

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

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

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

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

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

==== update specification section organization ====
'''Next-action''': work with Ryan, Ernie, Erin, and others who have made concrete helpful suggestions for reorganizing the information architecture / content-order / layout of specs for greater approachability/readability by a broader audience, to design an interative update to spec organizations, in particular, the introduction/boilerplate/headers. See below notes on hResume experiment in progress.

[[hresume|hResume]] has an experimental abbreviated intro/headers section, and links to more details further below, based on some ideas that Ryan King and I had for improving the readability of the microformats specifications. [[hreview|hReview]] has some similar improvements, but different. We need to:
# Figure out if the new intro/headers structure in [[hresume|hResume]] and/or [[hreview|hReview]] is an improvement, and if it could be better. Perhaps figure out the requirements for an intro/header section
#* Shorter tends to be better
#* Must be comprehensive enough to "print and read"
#* Must detail authorship/editorship
#* Must detail copyright/patent statements
# Write up a template - make it self-documenting per the requirements
# Update existing specifications with the new intro/headers structure.
## [[hcard|hCard]]
## [[hcalendar|hCalendar]]
## [[hreview|hReview]]

==== reorganizing Implementations sections ====
* sort implementations by authoring/creating/publishing, browsing/viewing, converting/importing, indexing/searching.

Hmmm... I like: '''A'''uthoring, '''B'''rowsing, '''C'''onverting, '''I'''ndexing, '''L'''ibraries (for developers), and '''P'''otential (for open source projects we want to add support to). Anybody have alternative suggestions for this vocabulary? I don't have a particularly strong preference so I'm going to go with these four until I find examples that don't fit, or someone suggests something better.

See: [http://microformats.org/wiki/hcalendar#Implementations hCalendar Implementations] for a first attempt at this. Assuming folks like that, we can go ahead with categorizing the implementations sections of other microformats specifications.

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

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

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

=== introduction / community ===

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

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

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

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

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

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

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

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

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

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

==Ryan==
=== wiki cleanup ===
* possibly move dead proposals off of homepage?

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

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

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

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

== Dimitri Glazkov ==

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

== Chris Messina ==

=== General ===

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

=== Campaigns ===

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

=== Wishlist ===

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

== Robert Bachmann ==

=== 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:
* .Net System.Xml
* hAtom2Atom written using XSL 2.0?
** Do you think this would be useful? I have created a barebones version, doesn't yet take in all the parsing rules yet, but I'd be happy to share. Moving to XSL 2.0 does make things a bit cleaner and more efficient. - Matt Dertinger.
</li>
<li>Support for other output formats: (hAtom2<i>xyz</i>.xsl)
* RSS 2.0 (meanwhile use hAtom2Atom.xsl and [http://atom.geekhood.net/ atom2rss.xsl]) -- <i>+1 Matt Dertinger</i>
* RSS 1.0 (meanwhile use hAtom2Atom.xsl and [http://cvs.4suite.org/viewcvs/uogbuji/atom2rss.xslt atom2rss.xslt]) -- <i>+1 Matt Dertinger</i>
** My opinion at the moment, I neither want to produce nor to consume RSS. Atom is nicer (and should be supported by most good feed readers available today), RSS should fade away. -- Robert Bachmann
* AtomOWL (meanwhile use hAtom2Atom.xsl and [http://dannyayers.com/2005/11/22/atomowl-xslt-progress/ atom2rdfxml.xsl])-- <i>+1 Matt Dertinger</i>
** Having the possibility of GRDDL-ing hAtom to AtomOWL seems definitly interessting. I realy should implement this some day. - Robert Bachmann
* JSON?
** Does it make sense to consider a canonical representation of microformats (either case by case, or in general) in JSON? E.g. so that a JSON API that returned contact information could return an hCard-equivalent chunk of JSON. - Tantek.
*** This could enable some nice JavaScript hacks. I should give hAtom2JSON a try. - Robert Bachmann
</li>
</ul>

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

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

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

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

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

== 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 red links on [[Main_Page-fr]]
* localize a french version of the official website and migrate contents
** ask authorization to the authors
** migration could be done on any collaborative CMS
** test a cocomment system (based on local-wiki)
** complete with original links
* find experts for peer-reviewing
* update [http://fr.wikipedia.org/wiki/Microformats French-wikipedia:Microformats] via cowriting [http://fr.wikipedia.org/wiki/Discuter:Microformats on discussion page] (directly originated from the english article) + french examples to be found + local resources.
** create hCard, hCalendar... and all red link pages on french wikipedia
* find help and maintain http://www.communitywiki.org/MicroFormats
* localize [[species-fr]] and related pages
* clean all dead links pointing to elanceur.org

== Frances Berriman ==

[[User:Phae|Frances Berriman]]

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

== Ben West (bewest) ==

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

=== Expore Microformat Deployment Issues ===
How does who determine the status of work going through some stage of the process? When does a format move from draft to "full spec"? Who decides? What are the qualitative and quantitative features that characterize work in different stages, especially as a spec nears deployment as "full spec". What makes this pronouncement more than a mythical blessing? What quantitative analyses can be provided to validate deployment? Today, we have powerful agents capable of processing huge amounts of information on the web. Should we be using these to measure published marketshare? What role should tools and test suites play in deploying microformats?

=== Vocabulary ===
A lot of knowledge work is about maintaining sets of vocabulary. Now that the vocabulary is emerging, it may be time start making sure everyone is "on the same page," especially since some of the language is highly symbolic.
Terms:
* "boil the ocean" A huge task. "A phrase used in the industry to describe an attempt at something that is way too ambitious. For example, "They're trying to get their site launched by COMDEX. They could easier boil the ocean." from <http://www.netlingo.com/right.cfm?term=boil%20the%20ocean>
* microformats: more than one microformat
* microformat: see my definition on http://microformats.org/wiki/what-are-microformats#BenWest
* data fidelity: the extent to which a data format might be considered lossy. eg HTML is often seen as a lossy format because the information parsed out of a resource may not fully match the information orginally encoded. Non-lossy formats have a very high data fidelity, while lossy formats have low data fidelity. Microformats seek to increase data fidelity of html.
* market: the locus of economic forces

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

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

=== Information Architecture ===
'''Help Welcomed! Please leave your name'''
Add complaints to [[wiki-feedback]]!
Helping to make the wiki easier to use. I'd like to see the main page more towards a format like http://simile.mit.edu/solvent/ with the big questions right out front:
* What Is This?
* What can I do here?
* Is there a demo?
* Where can I learn more?
I'd like to change the front page to this kind of design.
==== Support Pages ====
There are several categories of things in the wiki. Can we enumerate them?
* About the Community
** Where to find information.
** Who are the stake holders?
** FAQs
* Web/Architectural Philosophy
** Community Principles
** Why are we doing this?
** XML and Namespaces
** Semantic XHTML
** Common Misconceptions
** Concession and Disposition of Criticism
** FAQs
* Specs
** Examples
** Discussion
** Exploration
** Use Cases
** Implementations
** The spec itself.

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

Can others agree and or refine this list? Should I take it to the -discuss list? How do we create consensus on how the wiki should be organized in order to make it more usable? And how can we turn that consensus into actionable changes?

The wiki should also capture wisdom that stems from discussions that don't produce microformats. For example, Chris Messina suggests a "Best Of" page suitable for capturing this kind of wisdom. I think we can think of a given microformat as being at a place in a spectrum that ranges from "not yet thought of", to "interesting but needs work," or even "rejected", and of course including all the stages familiar to the microformats processes (eg examples, brainstorming, etc...).
If there were such a page would it:
* Belong to a microformat? (eg hcard-bestof)
* or to the global namespace? (eg /wiki/wisdom/foobar-format)
(I think Chris Messina suggests that it belongs to a given microformat, but then how do we collect wisdom from non-microformats?)

Considering that the wiki page named with the microformat (i.e. /wiki/hcard) is the one that people will mostly likely look to first for learning about a particular format, I'd think it'd make more sense and create a more welcoming feel to convert these pages to an intro page introducing the format for the beginner and linking to resources like tutorials and creators. Spec pages would then be relocated to wiki/*-spec -- [[User:Cgriego|Cgriego]] 13:25, 16 Oct 2006 (PDT)

====Mike Schinkel's Comments====

My suggestion on the list was for us to use a convention that the entry page (i.e.
http://microformats.org/wiki/hcard) would be an index into a list of
(psuedo) standardized sub pages so that it would be very people to
find what is important to them. For example, is a list of potential sub pages:

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

These pages would be located respectively at

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

Please note I am suggesting an architecture not a specific list of sub pages. The list of sub pages should be defined by both reviewing existing information during site reorganization, and then via discussion on the list in an attempt to discover and extract which sub pages are needed for most/all microformats.

'''NOTE''': This differs from above in that the spec if not viewed as a top level structure but instead the microformat itself and the spec would be under the microformat. In this context "microformat" is a more abstract concept and "spec" is a more concrete thing. Another way to think about it would be that each microformat would have it's own mini home page and then things like "spec" are the pages listed on its home page.

== Matt Dertinger (Thewhoo) ==

[[User:Thewhoo]]

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

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

== Henri Bergius ==

[[User:HenriBergius|Henri Bergius]]

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

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

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

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

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

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

to-do

2007-07-17T10:41:04Z

RobertBachmann: /* hAtom2Atom */ Removing legacy xslt engines

<h1>To Do</h1>

This page is for posting [[microformats]] related shared to do items. If you want to use this page for your microformats related to-do items, create a section with your name on it. The reason we are keeping these all on the same page is to make it easier to tell when people are working on similar things, and to make it more obvious when people help out with other people's tasks. In theory this probably won't scale, but let's first see how it does in practice. :) - [http://tantek.com Tantek]

__TOC__

== Lazyweb ==

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

=== for all microformats ===
* We have recently added a new mailing list called microformats-new. There may be some confusion surrounding this change, so it would be helpful to:
** Draft a message to be added to the confirm message sent when someone subscribes to any list including a welcome message, ground rules, topic for the subscribed list, and the topics for nearby lists.
** Add a faq entry somewhere on why the new list was created.
** Double check the wiki pages to make sure advice on mailing lists is accurate.
* quick and easy "how to" pages for each microformat. [[use]] is a good overall start.
* brief summary statements for each microformat that explain why it matters, what does it accomplish for the publisher.
* write up [http://microformats.org/discuss/ mailing-list] questions and answers in the appropriate [[faq]] pages.
* validators. See the hReview section below as there has been a request for an hReview validator in particular. See [http://norman.walsh.name/2006/04/13/validatingMicroformats Norman Walsh's blog post "Validating microformats"] for some valuable analysis and validation pseudo-code (prose description), which are useful steps towards building microformat validators.
* Add [http://verselogic.net/projects/wordpress/wordpress-openid-plugin/ OpenID] to Microformats Blog.
* Submit definitions of "mcroformat", and individual examples, to the [http://foldoc.org Free On-line Dictionary of Computing], acording to [http://foldoc.org/editing.html the Free On-line Dictionary of Computing guidelines]

=== hCard ===
* microformatted versions of conference pages
** Wait for confirmation from O'Reilly webmaster on revision of the [http://conferences.oreillynet.com/etel2006/ ETel] [http://conferences.oreillynet.com/pub/w/44/speakers.html speaker's page] with all the speakers marked up with [[hcard|hCard]] and links to "Add hCards to Address Book" etc., similar to the [http://tantek.com/microformats/2005/web2/speakers.html Web 2.0 speakers page which Tantek did a revision of last fall].
* vcard to hcard converter
** would be nice to have a web upload UI that would take one or more vCards from apple's address book and give them back to you as hCards
** [[User:RobertBachmann | RobertBachmann]] suggests starting points:
*** For Ruby: http://vpim.rubyforge.org/
*** For C: http://freshmeat.net/projects/libvc/
*** For Python: http://www.nongnu.org/python-pdi/
*** For PHP: http://pear.php.net/package/Contact_Vcard_Parse/
* add export support for microformats to [http://www.turingart.com/abForWeb_lan__en.htm AB to Web]
* A mash-up with google maps that will take any url with a hcard (or hcard's) and map the location(s) on a map (similar to [http://austin.adactio.com/ austin.adactio.com])

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

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

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

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

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

=== Yahoo Open Source Library Patches ===
Several of these could very much be improved with a little microformats markup. Do we just make patches and submit them? Contact Nate Koechley at Yahoo (see Tantek for contact info) to follow-up.

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

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

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

===rel-tagging on Wikipedia===
Somebody familiar with the "rel-tag" microformat might want to add details, and a link to the relevant page on this Wiki, to the [http://en.wikipedia.org/wiki/Tag_%28metadata%29 Wikipedia page on tagging]. [[User:AndyMabbett|Andy Mabbett]] 14:07, 3 Jan 2007 (PST)

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

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

=== protect the community ===
* Analyze [[Special:Recentchanges]] and [http://microformats.org/discuss mailing-lists] and:
** add to [[mailing-lists]] policies/guidelines accordingly.
** redirect and resolve threads accordingly per guidelines
** privately email violaters kindly asking them to improve their behavior
** work with admins on next steps for individuals negatively impacting the community
** recognize noisy/distracting threads on the email list, document responses/answers to such subjects on the appropriate page(s) on the wiki, and reply to those threads with the URLs to the documentation on the wiki. Putting the responses/answers on the wiki helps by hopefully providing preemptive answers to some who might reraise the subjects on the list in the future, and helps the community quickly terminate such threads by using the answers on the wiki.

=== help publishers ===
==== foldup cheatsheet ===
'''Next actions''': review all descriptions, property lists, examples in Erin's cheatsheet draft, give feedback back to Erin about her foldup cheatsheet, iterate, print, fold, distribute.

Help create a printable foldup cheatsheet of multiple microformats (ASAP, perhaps for [[events/2007-04-18-web-2-expo-dinner|Web 2.0 Expo Microformats dinner]]) that:
* prints onto both sides of a sheet of 8.5x11" paper (size chosen for US distribution, and because it folds nicely into 4ths sliced vertically, then 3rds sliced horizontally into a size approximating a business card, hoping to CC-by the whole thing so that others can do their own variants, perhaps for other paper sizes also)
* accordion folds first into 1/4 size along 3 vertical creases, then 1/3 size along 2 horizontal creases
* on each of the 8 vertical stripes (4 one side, 4 the other) of the sheet, info on each of the following microformats (it is assumed that [[hcard|hCard]] documentation will cover [[adr]], and [[geo]] also).
** people vs. other things
*** people-centric:
**** [[xfn|XFN]]
**** [[hcard|hCard]]([[adr]],[[geo]])
**** [[hcalendar|hCalendar]]
**** [[hresume|hResume]] + [[include-pattern]]
*** content-centric:
**** [[microformats]] list/overview
**** other common rels: [[rel-license]] [[rel-enclosure]] [[rel-tag]] [[rel-directory]]
**** [[hreview|hReview]] + [[xfolk|xFolk]]
**** [[hatom|hAtom]]
** original building blocks vs. newer
*** original:
**** [[microformats]] list/overview [[rel-license]] [[rel-tag]]
**** [[xfn|XFN]]
**** [[hcard|hCard]]([[adr]],[[geo]])
**** [[hcalendar|hCalendar]]
*** newer:
**** [[hreview|hReview]] + [[xfolk|xFolk]]
**** [[rel-directory]] [[rel-enclosure]]
**** [[hatom|hAtom]]
**** [[hresume|hResume]] + [[include-pattern]]
** other splits of 4 slices vs. 4 slices?
*** ...
*** ...
* each triple accordion fold section for a microformat should contain:
** property summary with required/optional singular/plural sub-properties (similar to current cheat sheet) + illustrative code sample with common properties
** list of properties, sub-properties with values and definitions of each
** URLs to spec, examples, implementations for more info.

Update: I made a folding cheat sheet to similar specifications. Not sure if it's 100% correct, it needs to be looked at for needed revisions. [http://erincaton.ca/media/cheatsheetHandout.pdf Cheat sheet PDF.] [[User:ErinCaton|ErinCaton]]

Perhaps [http://www.visibone.com/ Visibone] can be of some use? I can recommend their current products. --[[User:Gazza|Gazza]] 06:41, 7 Apr 2007 (PDT)

==== *-authoring microformats wiki pages ====
* [[hcard-authoring]] - '''next-actions''': add tips/instructions noted below.
** instructions for each property that is in [http://microformats.org/code/hcard/creator hCard creator] to begin with
** instructions for all other hCard properties
** a tutorial on creating an hCard for your site
*** specific instructions for common blogging platforms
** reference [[hcard-examples]] for more specific uses, and add to them accordingly
*** add an extended example to [[hcard-examples#Authors_of_Pages_and_Posts|contact info for a page]] with postal address, phone numbers, email address.

* [[hreview-authoring]] - '''next-action''': create a first draft minimal tutorial on how to author hReviews (e.g. at least for common properties) to blog reviews so that they'll be aggregated.

* [[hcalendar-authoring]] - '''next-action''': add tips/instructions for each property that is in [http://microformats.org/code/hcalendar/creator hCalendar creator].

* *-authoring for other reasonably well established microformats:
** [[xfolk-authoring]], [[hatom-authoring]]

==== help with microformat examples in the wild ====
Using the above updated [[authoring]] pages, get the community to help go over all "common" pages (both logged out and logged in states) of the following sites which have some microformats already, and verify each page is as microformatted as it can be with high fidelity [[hcalendar|hCalendar]] and [[hcard|hCard]] etc. Document full support of each implementation's microformats on the implementations page (perhaps create a separate page for each implementation, e.g. [[flickr]], [[upcoming]], [[eventful]] etc.) Document any exceptions as needed. In no particular order:
* Flickr.com (3.5m hCards)
* Upcoming.org (100k hCalendar events, 100k hCard venues)
** home page
* Eventful.com (100k hCalendar events, 100k hCard venues)
* Yahoo! Tech (300k products with hReviews)
* JudysBook.com (???k hReviews)
* ... lots more, get from "Implementations" and "Examples in the Wild" sections of specs.

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

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

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

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

=== iterate on current microformats ===
==== [[hcard|hCard]] ====
* [[hcard-examples]] '''next-actions''': update with examples described below
** add examples of [[hcard|hCard]]s with work telephone, mailing address etc.
** add examples of marking up an organization vs. a person, then link to it from [http://microformats.org/wiki/hcard#Organization_Contact_Info hCard spec section on Organization Contact Info].
** add example of organization-name and organization-unit usage.
* [[hcard-issues]] and [[hcard-feedback]]. '''next-actions''': resolve all issues and incorporate all feedback.
* [[hcard-brainstorming]] '''next-actions''': determine which brainstorms proposals to resolve in April, and which later
** need property for gender (see [[hcard-faq#How_is_gender_represented|proposal in hCard FAQ]] and discussion in [[hcard-issues]]) - use tags for now, add to hCard creator
** solve [[hcard-brainstorming#Auto-Discovery|autodiscovery]] of more canonical/thorough hCard
* [[hcard-examples-in-wild]]
** help dglazkov markup: http://glazkov.com/blog/archive/2003/12/17/147.aspx

==== [[hcalendar|hCalendar]] ====
'''Next-actions''':
* itemize a list of properties similar to the [[hcard#Property_List|hCard property list]], drawing upon hCalendar experience, iCal-BASIC draft(s), ietf-calsify mailing list and other sources to derive the precise list.
* formalize [http://microformats.org/wiki/hcalendar- brainstorming#Tabular_event_calendars]
* flesh out [[hcalendar-examples]] and do a once over on markup/presentation of what RFC2445 examples would look like
* need spec details and then [[hcalendar-examples]] of multi-instance [[hcalendar|hCalendar]] events
* need spec details and then [[hcalendar-examples]] of repeating events
* add explicit explanation and examples for LOCATION [[hcard|hCards]] and ATTENDEE [[hcard|hCards]], perhaps on a separate [[hcalendar-examples]] page.
* need to resolve all outstanding [[hcalendar-issues]] to-do items.
* create [[hcalendar-profile]] and have folks verify it. note that it will likely need reconciliation with the [[hcard-profile]], especially since [[hcalendar|hCalendar]] normatively depends on [[hcard|hCard]]. Probably makes sense to have a combined profile which hCalendar would use.

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

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

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

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

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

==== update specification section organization ====
'''Next-action''': work with Ryan, Ernie, Erin, and others who have made concrete helpful suggestions for reorganizing the information architecture / content-order / layout of specs for greater approachability/readability by a broader audience, to design an interative update to spec organizations, in particular, the introduction/boilerplate/headers. See below notes on hResume experiment in progress.

[[hresume|hResume]] has an experimental abbreviated intro/headers section, and links to more details further below, based on some ideas that Ryan King and I had for improving the readability of the microformats specifications. [[hreview|hReview]] has some similar improvements, but different. We need to:
# Figure out if the new intro/headers structure in [[hresume|hResume]] and/or [[hreview|hReview]] is an improvement, and if it could be better. Perhaps figure out the requirements for an intro/header section
#* Shorter tends to be better
#* Must be comprehensive enough to "print and read"
#* Must detail authorship/editorship
#* Must detail copyright/patent statements
# Write up a template - make it self-documenting per the requirements
# Update existing specifications with the new intro/headers structure.
## [[hcard|hCard]]
## [[hcalendar|hCalendar]]
## [[hreview|hReview]]

==== reorganizing Implementations sections ====
* sort implementations by authoring/creating/publishing, browsing/viewing, converting/importing, indexing/searching.

Hmmm... I like: '''A'''uthoring, '''B'''rowsing, '''C'''onverting, '''I'''ndexing, '''L'''ibraries (for developers), and '''P'''otential (for open source projects we want to add support to). Anybody have alternative suggestions for this vocabulary? I don't have a particularly strong preference so I'm going to go with these four until I find examples that don't fit, or someone suggests something better.

See: [http://microformats.org/wiki/hcalendar#Implementations hCalendar Implementations] for a first attempt at this. Assuming folks like that, we can go ahead with categorizing the implementations sections of other microformats specifications.

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

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

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

=== introduction / community ===

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

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

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

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

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

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

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

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

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

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

==Ryan==
=== wiki cleanup ===
* possibly move dead proposals off of homepage?

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

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

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

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

== Dimitri Glazkov ==

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

== Chris Messina ==

=== General ===

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

=== Campaigns ===

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

=== Wishlist ===

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

== Robert Bachmann ==

=== 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:
* .Net System.Xml
* hAtom2Atom written using XSL 2.0?
** Do you think this would be useful? I have created a barebones version, doesn't yet take in all the parsing rules yet, but I'd be happy to share. Moving to XSL 2.0 does make things a bit cleaner and more efficient. - Matt Dertinger.
</li>
<li>Support for other output formats: (hAtom2<i>xyz</i>.xsl)
* RSS 2.0 (meanwhile use hAtom2Atom.xsl and [http://atom.geekhood.net/ atom2rss.xsl]) -- <i>+1 Matt Dertinger</i>
* RSS 1.0 (meanwhile use hAtom2Atom.xsl and [http://cvs.4suite.org/viewcvs/uogbuji/atom2rss.xslt atom2rss.xslt]) -- <i>+1 Matt Dertinger</i>
* AtomOWL (meanwhile use hAtom2Atom.xsl and [http://dannyayers.com/2005/11/22/atomowl-xslt-progress/ atom2rdfxml.xsl])-- <i>+1 Matt Dertinger</i>
* JSON?
** Does it make sense to consider a canonical representation of microformats (either case by case, or in general) in JSON? E.g. so that a JSON API that returned contact information could return an hCard-equivalent chunk of JSON. - Tantek.
</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

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

== 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 red links on [[Main_Page-fr]]
* localize a french version of the official website and migrate contents
** ask authorization to the authors
** migration could be done on any collaborative CMS
** test a cocomment system (based on local-wiki)
** complete with original links
* find experts for peer-reviewing
* update [http://fr.wikipedia.org/wiki/Microformats French-wikipedia:Microformats] via cowriting [http://fr.wikipedia.org/wiki/Discuter:Microformats on discussion page] (directly originated from the english article) + french examples to be found + local resources.
** create hCard, hCalendar... and all red link pages on french wikipedia
* find help and maintain http://www.communitywiki.org/MicroFormats
* localize [[species-fr]] and related pages
* clean all dead links pointing to elanceur.org

== Frances Berriman ==

[[User:Phae|Frances Berriman]]

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

== Ben West (bewest) ==

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

=== Expore Microformat Deployment Issues ===
How does who determine the status of work going through some stage of the process? When does a format move from draft to "full spec"? Who decides? What are the qualitative and quantitative features that characterize work in different stages, especially as a spec nears deployment as "full spec". What makes this pronouncement more than a mythical blessing? What quantitative analyses can be provided to validate deployment? Today, we have powerful agents capable of processing huge amounts of information on the web. Should we be using these to measure published marketshare? What role should tools and test suites play in deploying microformats?

=== Vocabulary ===
A lot of knowledge work is about maintaining sets of vocabulary. Now that the vocabulary is emerging, it may be time start making sure everyone is "on the same page," especially since some of the language is highly symbolic.
Terms:
* "boil the ocean" A huge task. "A phrase used in the industry to describe an attempt at something that is way too ambitious. For example, "They're trying to get their site launched by COMDEX. They could easier boil the ocean." from <http://www.netlingo.com/right.cfm?term=boil%20the%20ocean>
* microformats: more than one microformat
* microformat: see my definition on http://microformats.org/wiki/what-are-microformats#BenWest
* data fidelity: the extent to which a data format might be considered lossy. eg HTML is often seen as a lossy format because the information parsed out of a resource may not fully match the information orginally encoded. Non-lossy formats have a very high data fidelity, while lossy formats have low data fidelity. Microformats seek to increase data fidelity of html.
* market: the locus of economic forces

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

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

=== Information Architecture ===
'''Help Welcomed! Please leave your name'''
Add complaints to [[wiki-feedback]]!
Helping to make the wiki easier to use. I'd like to see the main page more towards a format like http://simile.mit.edu/solvent/ with the big questions right out front:
* What Is This?
* What can I do here?
* Is there a demo?
* Where can I learn more?
I'd like to change the front page to this kind of design.
==== Support Pages ====
There are several categories of things in the wiki. Can we enumerate them?
* About the Community
** Where to find information.
** Who are the stake holders?
** FAQs
* Web/Architectural Philosophy
** Community Principles
** Why are we doing this?
** XML and Namespaces
** Semantic XHTML
** Common Misconceptions
** Concession and Disposition of Criticism
** FAQs
* Specs
** Examples
** Discussion
** Exploration
** Use Cases
** Implementations
** The spec itself.

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

Can others agree and or refine this list? Should I take it to the -discuss list? How do we create consensus on how the wiki should be organized in order to make it more usable? And how can we turn that consensus into actionable changes?

The wiki should also capture wisdom that stems from discussions that don't produce microformats. For example, Chris Messina suggests a "Best Of" page suitable for capturing this kind of wisdom. I think we can think of a given microformat as being at a place in a spectrum that ranges from "not yet thought of", to "interesting but needs work," or even "rejected", and of course including all the stages familiar to the microformats processes (eg examples, brainstorming, etc...).
If there were such a page would it:
* Belong to a microformat? (eg hcard-bestof)
* or to the global namespace? (eg /wiki/wisdom/foobar-format)
(I think Chris Messina suggests that it belongs to a given microformat, but then how do we collect wisdom from non-microformats?)

Considering that the wiki page named with the microformat (i.e. /wiki/hcard) is the one that people will mostly likely look to first for learning about a particular format, I'd think it'd make more sense and create a more welcoming feel to convert these pages to an intro page introducing the format for the beginner and linking to resources like tutorials and creators. Spec pages would then be relocated to wiki/*-spec -- [[User:Cgriego|Cgriego]] 13:25, 16 Oct 2006 (PDT)

====Mike Schinkel's Comments====

My suggestion on the list was for us to use a convention that the entry page (i.e.
http://microformats.org/wiki/hcard) would be an index into a list of
(psuedo) standardized sub pages so that it would be very people to
find what is important to them. For example, is a list of potential sub pages:

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

These pages would be located respectively at

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

Please note I am suggesting an architecture not a specific list of sub pages. The list of sub pages should be defined by both reviewing existing information during site reorganization, and then via discussion on the list in an attempt to discover and extract which sub pages are needed for most/all microformats.

'''NOTE''': This differs from above in that the spec if not viewed as a top level structure but instead the microformat itself and the spec would be under the microformat. In this context "microformat" is a more abstract concept and "spec" is a more concrete thing. Another way to think about it would be that each microformat would have it's own mini home page and then things like "spec" are the pages listed on its home page.

== Matt Dertinger (Thewhoo) ==

[[User:Thewhoo]]

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

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

== Henri Bergius ==

[[User:HenriBergius|Henri Bergius]]

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

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

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

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

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

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

posh-testimonials

2007-06-11T19:22:56Z

RobertBachmann: Reverted edit of NugNg2, changed back to last version by Tantek

<h1>POSH Testimonials</h1>

Do you like [[POSH]]? Blog a POSH Testimonial and link to it from here. Or if you prefer, you can also write one directly on this page.

== Blog Posts ==
* [http://blog.locusmeus.com/index.php?itemid=49 Posh Girl]: <blockquote><p>"At last! After microformats, AJAX, Web 2.0, XFN, JSON, XML-RPC (etc. etc.), they finally came up with a new fancy word that I can not only pronounce and remember, but actually understand as well! POSH - Plain Old Semantic HTML! Yup, I can do that :-)"</p></blockquote>
* [http://www.cvwdesign.com/txp/article/213/poshify-your-website CVW Web Design Blog]: <blockquote><p>"I intend to do what I can with my own code - and keep aware of the latest development in this area. I'd encourage all website authors to do the same."</p></blockquote>
* [http://www.unintentionallyblank.co.uk/2007/04/24/plain-old-semantic-html/ The Internet’s Upper Class Or Why Your Site Should Be POSH]:<blockquote><p>The idea is so simple it’s brilliant, get people to promote valid, semantic markup again.</p></blockquote>
* [http://shubox.net/blog/?p=11 pLAIN oLD sEMANTIC html]: <blockquote><p>"After reading the last few threads of the html5 specification mail-shots, and witnessing a serious discussion about why table tags should be allowed inside p tags (I read in disbelief!), I think more than ever good clean semantic mark-up needs promoting and a silly acronym might just be the way forward."</p></blockquote>
* ...

----
Return to the [[POSH]] home page.

operating-hours

2007-06-11T19:11:13Z

RobertBachmann: Reverted edit of GmxHxu, changed back to last version by Drago516

<h1>Operating Hours</h1>

This page documents a method that can be used to mark up the operating hours of stores, restaurants, museums, offices, and other estabishments that have set hours and are open on a regular basis. This is based on the [[hCalendar]] microformat.

__TOC__
== Discussion Participants ==
=== Authors ===
* [http://dragotown.com Nick Drago]
* [http://suda.co.uk/ Brian Suda]

=== Contributors ===

== Introduction ==
This effort came about as a result of the need for a human and machine readable markup format that can be used to define the operating hours of establishments.

Stores, businesses, etc. often provide their operating hours on their websites. With the addition of a small bit of markup, they are able to define their operating hours on their websites in such a way that spiders and other aggregators can retrieve such hours, automatically convert them to the iCalendar format, and use this data in any iCalendar application or service.

== Using RRULE in hCalendar ==
This was suggested [http://microformats.org/discuss/mail/microformats-discuss/2007-February/008562.html] by Brian. Is this the most appropriate method? --Nick

<pre>
// example definition of operating hours using RRULE in hCalendar

<h1>Pardon the Interruption</h1>
<p class="vevent">
<a class="url uid summary"
href="http://sports.espn.go.com/...">Pardon the Interruption</a>
is a <span class="category">TV</span> <span
class="category">sports</span> show.
<abbr class="dtstart" title="2001-10-22">It airs</abbr>
<span class="rrule">
<span class="freq">weekly</span>
<abbr class="byday" title="mo,tu,we,th,fr">Monday to
Friday</abbr> at <abbr class="byhour" title="5">5:30pm</abbr>
</span>


<abbr class="tzid" title="US-Eastern">ET</abbr> on ESPN.

The hosts of the show are longtime friends
<span class="hcard">
<span class="fn n">
<span class="given-name">Tony</span>
<span class="family-name">Kornheiser</span>
</span>
</span>
and ... (hCard for Michael Wilbon not shown)
<span class="description">They discuss - and frequently argue over
- the top stories of the
day in "sports... and other stuff".</span>
</p>
</pre>

== References ==
=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [[hcard]]
* [[hCalendar]]
* [http://www.ietf.org/rfc/rfc2445.txt iCalendar RFC2445]
* [http://www.iso.org/iso/en/prods-services/popstds/datesandtime.html ISO 8601]

=== Informative References ===
* [http://en.wikipedia.org/wiki/ISO_8601 Wikipedia article on ISO 8601]
* [http://www.xfront.com/microformats/hCalendar_part2.html Tutorial on recurring events in hCalendar]

=== Related ===
* [[operating-hours-examples]]
* [http://microformats.org/discuss/mail/microformats-discuss/2007-February/008562.html Corresponding thread from uf-discuss]

how-to-play-fr

2007-05-28T13:20:59Z

RobertBachmann: Reverted edit of XpkO5q, changed back to last version by ChristopheDucamp

Si c'est votre première visite, regardez svp la page d'[[introduction-fr|introduction]].

= Comment jouer ? =

Avant de commencer à contribuer au site, veuillez respecter svp ces instructions qui suivent :
# Vous devez vous créer un compte utilisateur (voir [http://fr.wikipedia.org/wiki/Wikip%C3%A9dia:Introduction%2C_compte_utilisateurWikipedia introduction compte utilisateur wikipédia]) avant d'éditer ou de créer des pages.
# Essayez d'abord l'une des [http://microformats.org/discuss listes de discussion] (et lisez la page [[mailing-lists-fr|liste de discussion]] avant de faire ainsi).
# Si vous écrivez un billet d'opinion, signez-le avec votre nom d'utilisateur.
# Ne créez SVP sur ce wiki que des pages directement en rapport avec les microformats. Toute autre page se verra très probablement effacée.
# Obéissez svp aux [[naming-conventions-fr|conventions de nomenclature]] des pages.
# N'utilisez pas les pages de discussion. voir #2.
# SVP essayez de vous assurez que vous produisez du XTHML valide.
# Quand vous collez du code, ajoutez quelques sauts de ligne avec une largeur raisonnable.
# SVP n'utilisez pas de "?" ou tout autre signe de poncturation dans les en-têtes - cela aide à maintenir des URLs plus courts et faciles à lire, et copier coller vers leurs identifiants fragments
# Les titres doivent être explicitement balisés avec des tags <h1> <h2> etc. Afin d'éviter qu'ils ne s'affichent / polluent les Tables des Matières. Si vous trouvez de tels titres dans une page, svp NE LES MODIFIEZ PAS dans les styles de titres "=" ou "==".
# Evitez de renommer/modifier les textes des titres, y compris même leurs mises en lettres capitales ou pour vous conformer aux règles ci-dessus qui s'appliquent aux titres. Les titres sont souvent utilisés comme des liens permanents, et les modifier briserait de tels permaliens qui auraient déjà été utilisés. Aussi, soyez prudents au moment de créer des titres. Vous pouvez changer un titre si vous êtes soigneux pour laisser un <code><nowiki><span id="vieuxtitreID"></span></nowiki></code> vide en face du titre avec l'ensemble du vieuxtitreID à la valeur nécessaire pour maintenir les permaliens de titre.
# Evitez les modifications / éditions éditoriales globales sur wiki (par ex. les mêmes éditions ou éditions similaires appliquées à plusieurs pages, disons, à plus dizaine ou plus de pages). Si vous avez une opinion sur la manière d'améliorer globalement quelque chose de façon stylistique ou éditorialement sur le wiki, ajoutez-la svp à votre section sur la page [[to-do]] et demandez peut-être ensite à la communauté utilisant la liste de discussion microformats-discuss ce qu'en pensent les gens. Interprétez l'absence de réponse(s) comme un désintérêt et de ce fait un rejet implicite. Les administrateurs peuvent de temps en temps faire des modifications globales sur le wiki pour retirer le spam, réparer les dégâts produits par d'autres éditions globales du wiki, etc.
# SVP évitez les réponses contradictoires simples comme "Non" pour les questions et problématiques. Au lieu de cela, fournissez une petite phrase avec une raison qui fournit un peu d'information allant au delà de ce qui est fourni dans la question ou problématique.
# Ne retirez pas les "liens rouges", ni ne créez des pages/emplacements vides "..." pour eux afin de faire qu'elles ne soient pas rouges. Les liens rouges communiquent utilement un besoin ou un désir pour cette page d'exister, et la personne exprimant ce désir peut ne pas être la même personne qi soit capable de prendre le temps, ou ait le talent/l'historique nécessaire pour ébaucher une telle page. Les liens vers les pages créés à cette heure servent de to-do liste efficace (et facile à exécuter). Retirer ces liens fait que c'est plus difficile et moins commode de faire ainsi. (Une exception à ce stade : les liens rouges vers des microformats non existants comme "hbib", devraient être déliés, parce qu'il est désirable pour lui d'être plus difficile/moins pratique pour créer de nouveaux microformats). Pour finir, parce que de tels liens fournissent de l'inforamtion, ils ne sont pas redondants.
# N'utilisez pas le mécanisme des "Catégories" de MediaWiki. Tout comme les pages "Talk" ou "Discussion", cette communauté n'utilise pas toutes les fonctionnalités de MediaWiki.
# Ne créez pas de nouveaux liens "User:" à la main. Les liens User: devraient être uniquement créés que comme un résultat des utilisateurs signant véritablement leurs éditions avec <nowiki>~~~</nowiki> ou <nowiki>~~~~</nowiki>. De cette manière chaque page User: correspondra à un véritable login, plutôt que de lier accidentellement vers une page qui ne représente pas n login. Si vous voyez un lien rouge qui apparaît comme cela, ce ''devrait'' être un lien User:, par ex. <nowiki>[[DavidJanes]]</nowiki>, plutôt que d'éditer le lien à la place, créez un lien de redirection vers la page personnelle User:.

== Nettoyage du Wiki ==

Voir [[spam-removal-fr|retrait spam]].

Si vous voyez quelque chose qui selon vous a beson d'un ménage massif sur le wiki, pointez-le svp aux admins sur le canal irc ou la liste microformats-discuss.

hcard-cheatsheet

2007-05-28T13:20:54Z

RobertBachmann: Reverted edit of JdnUri, changed back to last version by AndyMabbett

<h1>hCard cheetsheet</h1>

==Profile==
<nowiki><head profile="http://www.w3.org/2006/03/hcard"></nowiki>

==Properties (Class Names)==

*'''vcard''' {1}
**''[[adr]]''*
***type [work|home|pref|postal|dom|intl]?
***post-office-box?
***''street-address''*
***extended-address?
***region?
***locality?
***postal-code?
***country-name?
**''agent''*
**[[hcard-singular-properties#bday|bday]]? ''([[datetime-design-pattern |ISO date]])''
**[[hcard-singular-properties#class|class]]? ''confidentiality/access classification of the ''entire'' hCard''
**''category''*
**''email''*
***type?
***value?
**'''[[hcard-singular-properties#fn|fn]]''' {1}
**[[geo]]?
***latitude?
***longitude?
**''key''*
**''label''*
**''logo''*
**''mailer''*
**[[hcard-singular-properties#n|n]]?
***''honorific-prefix''*
***''given-name''*
***''additional-name''*
***''family-name''*
***''honorific-suffix''*
**''nickname''*
**''note''*
**''org''*
***organization-name?
***''organization-unit''*
**''photo''*
**[[hcard-singular-properties#rev|rev]]? ''datetime of the revision of the ''entire'' hCard''
**''role''*
**[[hcard-singular-properties#sort-string|sort-string]]?
**''sound''*
**''title''*
**''tel''* ''(Note [http://en.wikipedia.org/wiki/E.123 E.123] for formatting info.)''
***type [home|work|pref|fax|cell|pager]?
***value?
**[[hcard-singular-properties#tz|tz]]? ''timezone of the person''
**[[hcard-singular-properties#uid|uid]]? ''applies to the ''entire'' hCard''
**''url''*

{{cheatsheet-key}}
{| border="1" cellpadding="2"
| pref || preferred
|-
| dom || domestic
|-
| intl || international
|-
| cell || mobile
|}

===Notes===
*FAQ: [[hcard-faq#Should_I_use_ADDRESS_for_hCards|"why 'adr'?"]]
* <code>URL</code> in vCard becomes <code><a class="url" href=...>...</a></code> inside the element with class <code>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.
* If an adr-child (e.g ''street-address'') is present it will ONLY be considered part of the hCard data IF it is inside an ''adr''.

====Geo====
* If latitude is present, so MUST be longitude, and vice versa.
* Coordinates MAY be combined a single <abbr> element; then the latitude and longitude MUST be separated by a semicolon in the title attribute and latitude MUST be first:
:<code><nowiki><abbr class="geo" title="37.386013;-122.082932">home</abbr></nowiki></code>
* The same number of decimal places SHOULD be used in each value.
* Coordinates use the datum of [http://en.wikipedia.org/wiki/World_Geodetic_System WGS84].
* [http://wikitravel.org/en/Wikitravel:Geocoding#Sources_for_lat.2Flongs Sources for latitude/ longitude coordinates]

==Related pages==
{{hcard-related-pages}}
*{{cheatsheets}}

internationalization

2007-05-28T13:20:50Z

RobertBachmann: Reverted edit of UnoR2f, changed back to last version by AndyMabbett

=Internationalization=
(AKA '''internationalisation''', '''i18n'''.)

What can we do, to make microformats more easily usable, by people who are not publishing in (US) English?

==Background==
* Internet and web standards in general use US English terms and spelling (ref: W3C, IETF) for elements, attributes, properties and values.
** e.g. (X)HTML is defined in US English (e.g "color", "center").
* However such standards also strongly advocate the support of character sets such as UTF-8 for broader/better support of international content.

==Issues==
*<code>type</code> attributes, such as those for <code>tel</code> in [[hcard|hCard]], require either English-language content on the page, or English-language <code>abbr</code> titles.
**March 2007 discussion (ongoing) of [http://microformats.org/discuss/mail/microformats-discuss/2007-March/009000.html abbr title for non-English values]. Is <code><nowiki><abbr class="type" title="fax">Téléc</abbr></nowiki></code> acceptable?
*[[genealogy-brainstorming#Gender|Gender values in Genealogy]]

==Solutions==
* Use the [http://www.w3.org/TR/html4/struct/dirlang.html HTML <code>lang</code> and diretion (<code>dir</code>) attributes] wisely.
*For telephone numbers in hCard, use abbr and the [http://en.wikipedia.org/wiki/E.123 ITU E.123 standard] international format, for example:
:<code><nowiki><abbr class="tel" title="+44 1233 456 7890">01233 456 7890</abbr></nowiki></code>

==See also==
*[[faq#Q: How do microformats breach language barriers?|FAQ: How do microformats breach language barriers?]]
*[[hcard-examples-in-wild#UTF8_Examples|hCards using UTF8]]
*[[accessibility]]

==Microformats wiki in other languages==
See:
*[[other-languages|microformats wiki in other languages]]
*[[how-to-start-new-translation|how to start a new translation]]

==Internationalization/localization references==
*[http://www.w3.org/International/ WC3 Internationalization and Localization] - Lots of information in all areas.
*[http://en.wikipedia.org/wiki/Internationalization_and_localization Wikipedia's definition] - As well as further links to related articles.
*[http://www.lisa.org/ The Localization Industry Standards Association] - Some information requires site registration (like the primer), but not paid membership. Specific marketing details require paid membership.
*[http://www.useit.com/alertbox/9608.html Jakob Nielsen's Alertbox article on localization] - To remind this is actually for people first.

location-formats-fr

2007-05-28T13:20:43Z

RobertBachmann: Reverted edit of PmeKp3, changed back to last version by ChristopheDucamp

= Recherche sur 'Location'=
Ceci est une liste des efforts précedents sur les formats de données et protocoles de lieu / géographique ("Geo), sous forme d'une recherche de contexte pour développer un format lieu.
__TOC__

== Auteurs ==

* Tantek Çelik
* Bud Gibson
* Ryan King
* Eron Wright
* ...
* svp ajoutez-vous si vous avez aidé sur ce document.

(traduction en cours [[Christophe Ducamp]])

= Exemples de Lieu =

== Ce que les Personnes sont en train de Publier ==

* liens vers des services de cartes, URLs canoniques vers des services tiers comme :
** Google Maps
** Map Quest
** Yahoo Maps

* formats humain / nommés / juridiques
** endroits nommés, par exemple Westin St. Francis
** adresses, comprendant les codes postaux (zip)

* global/mathématique/géométrique
** Latitude / Longitude / Altitude
*** PRODUIT un bouton GeoURL
*** Geo en RSS. Veut dire qu'un billet spécifique de blog est associé avec une lat/log spécifique. Pas spécifique au sujet de savoir si cela signifie le lieu à partir duquel le billet a été produit ou l'endroit dont le billet traite.
*** La plupart des systèmes n'ont pas pour objectif ou ne supportent le composant altitude d'une coordonnée. Parce que la cartographie terrain en 3D crôit en popularité (Google Earth), on s'attend à ce que les systèmes de géocodage fournissent l'altitude.

= Formats de Lieu =

== vCard & hCard ==
vCard (RFC2426) et [[hcard-fr|hCard]] comprennent 'adr', un moyen de baliser les adresses. Elles ont aussi un champ appelé 'geo' pour lat/long.

== UPU S42 & OASIS xNAL ==
UPU S42 est un standard pour représenter les adresses postales. UPU, 'Universal Postal Union', est le consortium de toutes les postes nationales. Voir [http://xml.coverpages.org/ni2003-06-17-a.html UPU S42 Announcement]. xNAL, le nom XML
et langage de l'adresse, est une première tentative pour standardiser les composants des adresses développées par OASIS,
un consortium de petits processus-business. La distinction entre vCard/hCard et S42/xAL/xNAL viens pour savoir si les éléments de la ligne adresse en eux-mêmes sont décomposés. par exemple dans xNAL vous pouvez spécifier des composants comme numéro dans la voie, direction préfixe de la rue, nom de la rue, type de voie, direction rue postfix, type sous-adresse (Suite), numéro de sous-adresse.

Il n'est pas toujours possible de déterminer pour conclure ces composants à partir d'une ligne adresse, même aux USA où les adresses sont plus canoniques que d'autres."A 4TH ST W STE 10" est une ligne adresse légale aux USA. Le numéro de rue et le nom sont requis (aux USA), par conséquent, ce pourrait être canoniquemnet décomposé sous streetnumber="A", streetname="4TH", streettype="ST", postdirectional="W", subtype="STE", subtypenumber="10".

Les standards UPU S42 et OASIS xNAL sont probablement surdimensionnés pour taguer le contenu web général. Néanmoins, ce sont des standards importants qui devraient être considérés dans les webservices incluant à la fois le géocodage et le géocodate-inversé. Peut-être que les standards apparentés aux adresses décomposées sont quelque chose qui devraient être placés sur une autre page.

En outre, il devrait y avoir des pointeurs vers les standards nationaux des adresses.

USPS publie une liste complète d'abréviations canoniques pour à la fois les types de rues et les sous-types. Leurs publications sont cohérentes, mais il est facile d'inférer les correspondances correctes. Voir [http://www.usps.com/ncsc/lookups/usps_abbreviations.htm USPS Acronyms & Abbreviations]

La Nouvelle Zélande a adopté apparemment une variante de xNAL [http://www.e-government.govt.nz/docs/xnal-guidelines-1-0/index.html NZ xNAL Guidelines Release 1.0].

== ICBM ==
Une paire de lat/long séparés par une virgule <code><meta name="ICBM" content="XXX.XXXXX, XXX.XXXXX"></code>
[http://www.catb.org/~esr/jargon/html/I/ICBM-address.html]

== GeoUrl ==
* [http://geourl.org/ GeoURL]
** Ceci semble avoir une quantité décente d'adoption par les geeks, bien qu'il y ait beaucoup de problèmes typiques de métadonnées invisibles, de coordonnées inversées, positives au lieu de négatives, etc.
* [http://www.multimap.com/ Multimap.com] fournit une fonctionnalité similaire à GeoUrl, cherchant les sites web et weblog qui sont géotagués ou tagués ICBM, et les ajoute aux bases de données d'informations locales.

== Geotags Flickr ==
* [http://steeev.f2o.org/mt/2005/05/geotagging_flickr_with_google_maps_and_greasemonkey_part_2.html Flickr GeoTagging] Un script Greasemonkey pour ajouter des tags lat et long tags aux images flickr. Il utilise Google Maps pour avoir les lat et long. Les utilisateurs doivent entrer les termes de recherche (adresses, etc) et puis sélectionner un point sur la carte google. Les photos sont taguées avec "geo:lat=xx.xxxx", "geo:lon=xx.xxxx" et "geotagged" et agrégées sur [http://geobloggers.com/]
* [http://flickr.com/groups/geotagging/ Un groupe Flickr sur le sujet]
* [http://txfx.net/2005/05/17/flickr-google-maps-geobloggers/ Un parcours visuel de la technique.]
* A ce jour (2005-06-01), 14k photos ont été géotaguées sur Flickr.
* [http://mappr.com mappr], [http://brainoff.com/worldkit/flick mapping flickr] supportent aussi ces geotags.
* flickr supporte aussi [http://www.flickr.com/services/api/flickr.photos.getExif.html les en-têtes EXIF], qui peuvent être utilisés pour stocker des lieux.
* [http://beta.plazes.com plazes] permet aussi de taguer les photos flickr avec des geotags.

Ceci est quelque part un problème aussi, parce que des tags mécaniquement générés ne snot pas vraiment des tags. Inclure/régler les "Geotags" flickr pourrait être considéré comme de la pollution de texte vraiment saisi par l'utilisateur, parce que le texte des géotags est simplement un encodage pour un point sur une carte.

== Geotagging ==
* Geotagging a été employé dans d'autres services hébergés : [http://brainoff.com/worldkit/delicious/ delicious], [http://worldkit.typepad.com/ Typepad], [http://blog.360.yahoo.com/blog-yRZQpvY8cq2kWXBO5ZrxEmrwsg--?p=9 Yahoo 360], [http://www.zoto.com/users/geotags/ Zoto]

mais que signifient ces références vers "geotagging" ?

== RSS ==
Plusieurs personnes ont essayé de poser de l'information géographique dans RSS.
* [http://postneo.com/icbm/ Ce site] utilise les coordonnées icbm et a des plugins pour plusieurs packages de blogging.
* [http://www.blogmapper.com/ BlogMapper] - semble vouloir ajouter un espace-nom vers RSS.
* [http://www.feedmap.net/BlogMap/ BlogMap] - pioche l'extension RSS et les valeurs métatag.* [http://brainoff.com/worldkit/doc/rss.php worldKit RSS docs] - worldKit défend et comprend différents parfums de RSS géocodé ; particulièrement l'espace-nom "geo".
* [http://earthquake.usgs.gov/recenteqsww/rss.html USGS earthquake feed] - le fil RSS géocodé le plus largement utilisé
* [http://brainoff.com/worldkit/doc/polygon.php Polygones et lignes dans polygones] - Un format simple pour exprimer des polygones et lignes est défini pour worldKit
* [http://developer.yahoo.net/maps/ Yahoo Maps API] - utilise des espaces-nosm "geo" ( http://www.w3.org/2003/01/geo/wgs84_pos# ) et "ymaps" ( http://api.maps.yahoo.com/Maps/V1/AnnotatedMaps.xsd ) pour référencer spatialement RSS comme une section de son API, spécifiquement geo:lat, geo:long, ymaps:Address, ymaps:CityState, ymaps:Zip

== RDF ==
* [http://www.geosemantics.org/ Geosemantics Interest Group]
* [http://esw.w3.org/topic/GeoOnion GeoOnion] - un vocabulaire SW pour des items en rapport par la distance les uns des autres.
* [http://www.mapbureau.com/rdfmap1.0/index.html RDFMap]
* [http://esw.w3.org/topic/GeoRDF GeoRDF] effort similaire pour rassembler l'état de l'art, pour un effort dans l'interopérabilité entre les standards OGC et d'auters formats légérs géo.

== GML ==
[http://www.opengeospatial.org/docs/02-023r4.pdf Geographic Markup Language] fournit les descriptions XML les plus complètes de l'information géographique disponible. Heureuesment, c'est aussi un usage largement répandu, par conséquent un sous-ensemble communément utilisé de la spécification de 600 pages a vu le jour. GML est utilisé dans le payload OGC WFS décrit ci-dessous.

<blockquote style="background: white; border: 1px solid black; padding: 1em;">

== Open Geospatical Consortium - OGC ==
Since 1994, [http://www.opengeospatial.org/ Open Geospatial Consortium] has been developing open specifications to enable the exchange of geographic information between applications. While some GIS vendors opposed OGC initially, essentially all commercial GIS software companies have broken down their proprietary "stovepipes" by embracing OGC specifications. The recent groundswell of ajax mapping applications can benefit tremendously from using OGC specs.

=== WMS ===
The [http://portal.opengeospatial.org/files/?artifact_id=5316 OGC Web Map Service (WMS) specification] makes it easy to request map images from a map rendering engine, such as the [http://mapserver.gis.umn.edu/ UMN Map Server]. It is straightforward to build dynamic tiling ("slippy map") ajax applications that pull in OGC map tiles. At Where 2.0, [http://www.metacarta.com MetaCarta] demonstrated such an OGC-capable ajax GIS client. The portal map providers (yahoo/gmaps/msn/map quest) do not yet offer WMS interfaces, so someone should wrap their proprietary interfaces in a WMS wrapper to encourage them :-)

=== WCS ===

Web Coverage Service extends WMS to enable attribute information about large area overview maps.

=== WFS ===
The [https://portal.opengeospatial.org/files/?artifact_id=8339 OGC Web Feature Service (WFS) specification] is the best way to express geographic information about Web content. It is more complex than the <i>ad hoc</i> geoURL syntax, and for good reason: it can be loaded directly into any OGC-capable GIS even if the coordinate information is in a different projection/datum or is more complex than just a point.

WFS provides a robust means of querying for geographic entities, such as points, polygons, and more complex feature types. One can define new feature types simply by describing them. One can even specify the visual appearance of the geographic features using the [https://portal.opengeospatial.org/files/?artifact_id=1188 OGC Styled Layer Description (SLD) specification].

WFS is to vector map data, as WMS is to raster map data.

Geographic search results, such as the yellow page information from the portals, could be presented in WFS. John Battelle commented that RSS forces publishers to attach their business model to their content, instead of to the web site holding the content, so that they can make money no matter where their content flows. The search portals will probably be forced to do the same, e.g. putting click-through ads in the RSS search results or WFS yellow page results, so that even when you display them in your customized ajax mapping application, the portal publishing the search results can still make money.

</blockquote>

== Google ==
=== Google Earth XML ===
20050629 at Where 2.0 conference:
"Google Earth has an XML schema for describing a place on the earth. Will be releasing today or tomorrow."
- John Hanke of Google/Keyhole.
Official KML [http://www.keyhole.com/kml/kml_doc.html Docs] and [http://www.keyhole.com/kml/kml_tut.html Tutorial]

[http://bbs.keyhole.com/ubb/showthreaded.php/Cat/0/Number/16076/an/khGlobe/page/0#16076 Reverse-Engineered KML Schema] (deprecated now that KML 2.0 is officially released)

Note that KML supports the ''altitude'' component of a coordinate to support 3D terrain.

== NMEA ==

[http://www.gpsinformation.org/dale/nmea.htmhttp://www.gpsinformation.org/dale/nmea.htm Standard and Proprietary NMEA Sentances]

== Wikipedia ==

[http://en.wikipedia.org/wiki/Wikipedia:WikiProject_Geographical_coordinates Geo:Coordinates in Wikipedia Project]

== ISO6709 ==
[http://en.wikipedia.org/wiki/ISO_6709 : ISO6709 Alpha-numerical representation of Latitude,Longitude,(Altitude)]

== Autres Formats ==

* GPX = GPS XML format
* [http://en.wikipedia.org/wiki/Wikipedia:WikiProject_Geographical_coordinates Wikipedia markup styles]
* [http://openguides.org/ OpenGuides] and [http://b.evnt.org evnt] are both looking into real-world/folksonomic location name mappings

= Location APIs =

== Google Maps API ==
* [http://www.google.com/apis/maps/ Google Maps API documentation]

== Yahoo Maps API ==
* [http://developer.yahoo.net/maps/ Yahoo Maps API documentation]

= Location Data, Outils et Sites =

== Address2Coordinates ==
These systems are freely available sources of address to lat/long mappings (US only). The first few are based on US Census data, so they might be up to date.
* [http://www.census.gov/geo/www/tiger/ TIGER]
* [http://www.itl.nist.gov/fipspubs/55new/nav-top-fr.htm FIPS]
* [http://geocoder.us/ geocoder]
* You can get coordinates from UK post-codes from [http://www.streetmap.co.uk streetmap]
* Worldwide city level location data (over 4 million entries) is available from the [http://earth-info.nga.mil/gns/html/ GNS]. This is accessible as a REST service from the [http://brainoff.com/geocoder/ worldkit geocoder]
* [http://www.mysociety.org/?p=83 mysociety.org] is providing an interesting name-based location look-up services. The results are returned as a CSV file!   For instance, the query [http://gaze.mysociety.org/gaze-rest?f=find_places&country=US&state=CA&query=sunnyvale http://gaze.mysociety.org/gaze-rest?f=find_places&country=US&state=CA&query=sunnyvale] returns

<pre>
"Name","In","Near","Latitude","Longitude","State","Score"
"Sunnyvale","Santa Clara County","","37.36889","-122.03528","CA","100"
</pre>
but with a mime-type (text/csv) that browsers don't understand.

== A2B ==
[http://www.a2b.cc/ A2B] is a location based search engine. Lat and long only. Seems to pick stuff up from geo meta tags. Pages can either be manually entered or [http://www.a2b.cc/help-searching-addurl-blogping.a2b pinged]. They support lat/long and ICBM meta tags.

== Plazes ==
[http://plazes.com Plazes] is a system that does geo-info based on the network access point that the user's computer is connected to. They use tagging to identify locations.

== Sites Cartographie ==
* [http://www.multimap.com Multimap]
* [http://maps.google.com Google Maps]
* [http://www.mapquest.com MapQuest]
* [http://maps.yahoo.com Yahoo Maps]
* [http://www.mapblast.com MapBlast]
* [http://mapufacture.com mapufacture]

= Location Brainstorming =

Beaucoup de cela a été discuté et décrit à la conférence Where 2.0 d'O'Reilly sur le BOF Microformat.

Voir les notes [[geo-bof-2005-06-30]].

Une des idés qui est sortie du BOF était l'idée de [[location-tagging-fr|taguer le lieu]].

== Conclusions sur de nouveaux microformats ==

Les conclusions par consensus à partir du BOF Microformat GEO chez Where 2.0 fût de définir deux nouveaux microformats pour renvoyer les deux types de données géo les plus communément publiées.
* [[adr-fr|adr]] - pour représenter / baliser l'information du lieu de l'adresse. "adr" est simplement la propriété "adr" de [[hcard-fr|hCard]] et toutes ses sous-propriétés
* [[geo-fr|geo]] - pour représenter / baliser / publier l'information de lieu latitude et longitude. "geo" est simplement la propriété [[hcard-fr|hCard]] "geo" et toutes ses sous-propriétés, avec la donnée explicitement spécifiée de WGS84.

media-metadata-examples-fr

2007-05-28T13:20:17Z

RobertBachmann: Reverted edit of Zu9Cr6, changed back to last version by Tantek

Ceci est une page exploratoire à utiliser pour le stockage de différentes données multimédia et profils de métodonnées, formats et pratiques actuellement utilisés sur le web. Parce que c'est le tout tout début de l'exploration, nous devrions inclure autant de types de multimédia que possible dans la discussion ouverte - mais svp assurez-vous de déposer votre information dans la portion correcte de cette page.

= Objectif de cette exploration (ou : le Problème) =

L'objectif des études sur cette page est de déterminer la faisabilité et la demande pour un format sémantique de balisage flexible pour les paradigmes en rapport avec le multimédia.

Ceci couvre des choses comme :
<ul>
<li><p>Fournir des métdonnées associées à des fichiers liés multimédia.</p><p>Typiquement, la métadonnées multimédia est stockée dans le titre du fichier média lui-même - qui a des implications massives pour toute application où la métadonnée doit être indexée, cherchée ou rendue accessible à l'extérieur. Bien sûr, même si vous pourriez facilement accéder aux portions correctes d'un fichier média à distance, vous devriez encore coopérer avec une multitude de formats de métadonnées ouverts et propriétaires, chacun avec son ensemble de champs distinct, sa méthode de nomenclature et de stockage.
</p></li>
<li>Ce qui est appelé : Internet TV, IPTV, [http://newtube.org/ NewTube], vlogging, vidblogging, vidlogging, vodcasting, etc.</li>
<li>Ce qui est appelé : Podcasting, IPradio, etc.</li>
</ul>

Cette étude a pour but de produire un démarrage pour résoudre ce problème.

== Contributeurs ==

Ces types ont contribué à des exemples du vrai-monde et à la recherche dans ce document et sont intéressés pour aider à trouver une solution.

* Christopher Allen
* Dougal Campbell
* Dr. Ernie
* Rohit Khare
* Ryan King
* Kevin Marks
* Lisa Rein
* Dan Glegg
* Chris Messina
* [http://changelog.ca/ Charles Iliya Krempeaux]

Si vous contribuez sur de nouveaux exemples du vrai monde ou dans la recherche, et souhaitez aider à trouver une solution, ajoutez votre nom.

= Exemples sur le Web aujourd'hui =

Ci-dessous une liste de modèles de paille fondés sur des exemples du vrai monde. (les liens vers de véritables exemples ont été mis parce que beaucoup d'entre eux ont été trouvés sur des sites d'adultes, et il est admis que ce serait inapproprié de les lister ici. -- [[User:Charles|Charles]])

=== Show Strawman #1 ===
Clip simple avec une image de prévisualisation. Le clip est le show complet.
<nowiki>
<a href="clip.mpeg"><img src="preview.png" /></a>
</nowiki>

=== Show Strawman #2 ===
Clip simple avec une image de prévisualisation. Le clip est le teaser du show coplet. Et il y a un lien que vous pouvez suivre pour payer le show complet.
<nowiki>
<a href="teaser.mpeg"><img src="preview.png" /></a>

<a href="http://exemple.com/go">Payez pour Regarder</a>
</nowiki>

=== Show Strawman #3 ===
Un show divisé en plusieurs clips, chacun avec une image prévisualisation.
Ensemble les clips forment le show.
<nowiki>
<a href="clip-1.mpg"><img src="preview-1.png" /></a>

<a href="clip-2.mpg"><img src="preview-2.png" /></a>

<a href="clip-3.mpg"><img src="preview-3.png" /></a>
</nowiki>

=== Show Strawman #4 ===
Un ensemble de teasers pour un show. Ensemble il ne forment pas la totalité du show. et ils peuvent ou ne peuvent pas se chevaucher dans le temps. Il y a aussi un lien "Pay to
View".
<nowiki>
<a href="clip-blue.mpg"><img src="preview-blue.png" /></a>

<a href="clip-red.mpg"><img src="preview-red.png" /></a>

<a href="clip-green.mpg"><img src="preview-green.png" /></a>

<a href="http://example.com/go">Pay to View</a>
</nowiki>

=== Show Strawman #5 ===
Un clip unique qui arrive en différents formats. (Pourrait être un teaser, un clip, ou une émission complète.)
<nowiki>
<img src="preview.png" />
<a href="clip.mpg">MPEG</a>
<a href="clip.ogm">Ogg</a>
<a href="clip.avi">AVI</a>
</nowiki>

=== Show Strawman #6 ===
Une image de prévisualisation unique avec l'émission donnée dans deux méthodes différentes. La première est l'émission divisée en une série de morceaux (qui la rend plus facile à télécharger). Et la seconde est la totalité de l'émission en un fichier.
<nowiki>
<img src="preview.png" />

<a href="part-1.mpg">[1]</a>
<a href="part-2.mpg">[2]</a>
<a href="part-3.mpg">[3]</a>

<a href="full.mpg">full</a>
</nowiki>

=== Show Strawman #7 ===
Un clip unique avec une image de prévisualisation. Le titre de l'émission est donnée dans une image (et de ce fait le titre véritable lisible par une machine est le ''alt attribute'' de l'image) et est lié avec l'URL principale de l'émission. Il y a aussi un lien vers des épisodes plus anciens de l'émission.
<nowiki>
<a href="..."><img src="the-name-of-the-show-png" alt="The Name of the Show" /></a>

<a href="episode123-clip.mpeg"><img src="episode123-preview.png" /></a>

<a href="older-shows">older shows</a>
</nowiki>

=== Show Strawman #8 ===
Une série de clips avec des images de prévisualisation. Le titre du show est donnée avec une image (et de ce fait le titre véritable lisible par une machine est l'attribut alt de l'image) et est lié à l'url principale du show. Il y a aussi des liens vers les épisodes plus anciens et nouveaux du show.
<nowiki>
<a href="..."><img src="the-name-of-the-show-png" alt="The Name of the Show" /></a>

<a href="episode123-clip.mpeg"><img src="episode123-preview.png" /></a>
<a href="episode122-clip.mpeg"><img src="episode122-preview.png" /></a>
<a href="episode121-clip.mpeg"><img src="episode121-preview.png" /></a>
<a href="episode120-clip.mpeg"><img src="episode120-preview.png" /></a>

<a href="newer-shows">[next]</a>
<a href="older-shows">[previous]</a>
</nowiki>

=== Show Strawman #9 ===
Une série d'images de prévisualisation. Le titre du show est donné dans le texte. Un lien vers tous les fichiers de l'émission via un torrent. D'autres métadonnées sont aussi généralement incluses, en texte clair ; quelques-unes sont montrées ici. Aussi, parfois la métadonnée est placée dans la description.
<nowiki>
The Name of the Show

<img src="preview1.png" />
<img src="preview2.png" />

<a href="show.torrent">...</a>

Torrent Info Hash: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Description: blah blah blah .... here some URLs to previews...
blah blah blah .... this is 24 fps
blah blah blah

Content: tag1, tag2, tag3

Resolution: 320px x 240px

Run Time: 24mins 57secs

Size: 125.42 MB (131,509,108 bytes)

Type: Movie Clip

Published/Uploaded By: someone

<a href="...">Link to page with list of files in torrent</a>
<a href="...">Link to page with list of people on the torrent</a>
</nowiki>

= Standard Actuel / Précédent =

== Encore de l'image ==

* [http://www.exif.org/Exif2-2.PDF EXIF]
* [http://www.tasi.ac.uk/2000/09/rdfmeta/ RDF pour images auto-décrites]
* [http://archive.dstc.edu.au/RDU/staff/jane-hunter/PNG/paper.html Un système de requête et d'indexation pour les images en ligne basé sur le format PNG et les métadonnées embarquées]
* [http://www.w3.org/TR/photo-rdf/ Décrire et retrouver des photos en utilisant RDF et HTTP]
* [http://www.pheed.com/pheed/ Pheed extension RSS pour synidcation photo]

== Formats de Métadonnée Audio ==

* [http://www.id3.org/ ID3v2]

* iTunes
** Album : String
** Artist : String
** Beats Per Minute : Number
** Bit Rate : Number
** Comment : Blob
** Composer : String
** Genre : String or Foreign ID
** Disc Number : Number
** Kind : Proprietary - could be implimented as MIME type
** My Rating : Number < 5 (actually an integer from the range 0-100. 1-5 "stars" implemented by incrementing by 20)
** Sample Rate : Number
** Size : Number
** Time : Number
** Track Number : Number
** Year : Number
**Additional metadata used internally by the application : Date Added (Timestamp), Date Modified (Timestamp), Equalizer (foreign ID), Play Count (Number), Grouping (Internal)
**Noteable absences : Tags, [[rel-license|License]], Copyright year. Also note common complaints about [http://www.everything2.com/index.pl?node_id=1707402 ID3 and classical music].

* [http://www.xspf.org/ XSPF] (see also [http://gonze.com/playlists/playlist-format-survey.html A survey of playlist formats] and [http://www.xspf.org/xspf-v0.html The XSPF Playlist Format, version 0])
** album
** creator
** duration
** info
** title
** trackNum

== Podcasts ==

* '''iTunes podcast:''' http://phobos.apple.com/static/podcast_specifications.pdf
(version HTML de la spec : [http://labs.commerce.net/~rohit/How%20To%20Publish%20a%20Podcast%20on%20iTunes%20Music%20Store.html local archive], [http://labs.commerce.net/~rohit/iTunesRSS.html updated version from Apple Chapter Tool Beta docs], [http://phobos.apple.com/static/iTunesRSS.html online copy at Apple])

iTunes v. 4.9 a été largement proclamé comme une avance pour l'acceptation du podcasting par le plus grand nombre. Néanmoins, alors que quelques avocats résistent même au fragment d'un nom en marque déposé pour le phénomène, l'utilisation de "itunes": dans l'espace-nom est l'une des nombreuses décisions de design ans la spécification originale d'Apple devenu le principal objet du débat. Alors qu'Apple a une tradition de travailler tranquillement sur des fonctionnalités innovantes, ils se sont montrés ouverts aux inputs du public après sa version initiale. Beaucoup [http://daringfireball.net/2005/07/podcast_pocket d'autres blogueurs] ont [http://usefulinc.com/edd/blog/contents/2005/06/28-rss-apple-itunes/read chroniqué] [http://www.intertwingly.net/blog/2005/07/05/Insensitive-iTunes quelques-unes des réactions], tout comme quelques [http://tantek.com/log/2005/07.html#d10t0130 discussions en face à face].

Une liste de discussion pourrait bientôt venir...

* '''Media RSS :''' http://search.yahoo.com/mrss

Media RSS est [http://www.ysearchblog.com/archives/000111.html depuis longtemps dans le tube], mais n'a pas eu l'avantage de l'adoption de iTunes. Néanmoins, il a une ambition bien plus grande, y compris [http://www.ysearchblog.com/archives/000060.html la vidéo]; et une [http://groups.yahoo.com/group/rss-media/ communauté d'intérêt] bien plus grande.

=== Un Microformat Podcasting ? ===

Le meilleur point de départ pour comprendre ces deux propositions est [http://www.w3.org/2005/07/media-and-rss le tableau résumé du W3C dressé par Karl Dubost].

Il existe (au moins) deux chemins à considérer pour 'porter' ces propositions dans les Microformats :
# '''Standalone.''' What is the most straightforward rendering of each proposal into XHTML? This keeps the interests of the developers of ''consuming'' applications foremost: how can the migration be made as painless as possible?
# '''Refactored.''' Given the existing core of Microformats, what is the minimal (!) necessary to add on to RelLicense, RelTag, hReview, and so forth? This favors (we'd hope) content ''publishing'' applications: how can the marginal migration costs of adding media be made as painless as possible.

Mapping the existing specs requires understanding the data definitions set forth in each specification, and finding the optimal equivalents (where available). The following is a partial summary of one possible mapping:

==== Tableau Comparatif ====

<table border="1" cellpadding="5" cellspacing="0" style="border:1px solid grey;">
<tr>
<th>Aspect</th>
<th>Atom</th>
<th>iTunes RSS</th>
<th>Media RSS</th>
<th>M3U</td>
<th>RSS 2.0</th>
<th>Microformat?</th>
</tr>
<tr>
<td style="background-color:darkorange;color:black;font-weight:bold;">Authorship</td>
<td><ul><li><atom:author></li><li><atom:contributor></li></ul></td>
<td><ul><li><itunes:author></li><li><itunes:owner></li><li><itunes:name></li><li><itunes:email></li></ul></td>
<td><media:credit></td>
<td><em>nothing</em></td>
<td><copyright> <br /> <author> <br /> <source></td>
<td style="background-color:#eeeeee;color:black;"><ul><li><cite></li><li>[[hcard|hCard]]</li><li>[[rel-author]]</li><li>[[rev-author]]</li><li><address></li></ul><p>need a way of specifying the <em>role</em> of the <em>author</em> or <em>contributor</em>.</p></td>
</tr>
<tr>
<td style="background-color:darkorange;color:black;font-weight:bold;">Categorization</td>
<td><atom:category></td>
<td><itunes:category> <br /> <itunes:keywords></td>
<td><media:category></td>
<td><em>nothing</em></td>
<td><category></td>
<td style="background-color:#eeeeee;color:black;">[[rel-tag]] - requires a way to do sub categories?</td>
</tr>
<tr>
<td style="background-color:darkorange;color:black;font-weight:bold;">Description</td>
<td><atom:summary> <br /> <atom:content></td>
<td><itunes:subtitle> <br /> <itunes:summary></td>
<td><media:text></td>
<td><em>nothing</em></td>
<td><description></td>
<td style="background-color:#eeeeee;color:black;">XHTML (e.g. <nowiki><blockquote></nowiki> )</td>
</tr>
<tr>
<td style="background-color:darkorange;color:black;font-weight:bold;">Licensing</td>
<td><atom:copyright> <br /> <atom:rights></td>
<td><itunes:block> <br /> <copyright> <br /> <link></td>
<td>Not explicitly mentioned</td>
<td><em>nothing</em></td>
<td><ttl></td>
<td style="background-color:#eeeeee;color:black;">[[rel-license]]</td>
</tr>
<tr>
<td style="background-color:darkorange;color:black;font-weight:bold;">Metadata</td>
<td></td>
<td><itunes:duration> <br /> <itunes:image></td>
<td><media:thumbnail> <br /> <media:hash> <br /> <pre><media:content
url="http://www.example.com/movie.mov"
fileSize="12216320"
type="video/quicktime"
isDefault="true"
expression="full"
bitrate="128"
framerate="25"
duration="185"
height="200"
width="300"
/></pre></td>
<td><em>nothing</em></td>
<td></td>
<td style="background-color:#eeeeee;color:black;"><em>needs a new microformat</em> <br /> e.g., <dl><dt>proposal for duration</dt><dd><pre><abbr class="duration" title="00:27:35">
27 minutes, 35 seconds
</abbr></pre>
-- [[User:jkinberg|jkinberg]] 11:51, 19 Sept 2005 (PDT))
</dd></dl></td>
</tr>
<tr>
<td style="background-color:darkorange;color:black;font-weight:bold;">Preview</td>
<td><em>nothing</em></td>
<td><em>nothing</em></td>
<td><strong>For Video Media</strong>: <br /> <media:thumbnail> <br /><br /> <strong>For Audio Media</strong>: <br /> <em>nothing</em></td>
<td><em>nothing</em></td>
<td><em>nothing</em></td>
<td style="background-color:#eeeeee;color:black;"><em>need a new microformat for this</em>
<dl><dt>proposal for video preview</dt><dd><pre><img class="preview" src="..." /></pre>
-- [[User:Charles|Charles]]
</dd></dl></td>
</tr>
<tr>
<td style="background-color:darkorange;color:black;font-weight:bold;">Rating</td>
<td><em>nothing</em></td>
<td><itunes:explicit></td>
<td><s><media:adult></s> <media:rating></td>
<td><em>nothing</em></td>
<td><rating></td>
<td style="background-color:#eeeeee;color:black;">[[rel-tag]]</td>
</tr>
<tr>
<td style="background-color:darkorange;color:black;font-weight:bold;">Title</td>
<td><atom:title> <br /> <atom:subtitle></td>
<td><itunes:subtitle> <br /> <title></td>
<td><media:title> <br /> <title></td>
<td><em>nothing</em></td>
<td><title></td>
<td style="background-color:#eeeeee;color:black;">
<ul>
<li><h1>...</h1></li>
<li><h2>...<h2></li>
<li><h3>...</h3></li>
<li><h4>...</h4></li>
<li><h5>...</h5></li>
<li><h6>...</h6></li>
<li>title="..."</li>
<li>Microformats with class="title"</li>
</ul>
</td>
</tr>
<tr>
<td colspan="7"> </td>
</tr>
<tr>
<td style="background-color:darkorange;color:black;font-weight:bold;"><em>Show</em> Concept</td>
<td><ul><li><atom:feed></li><li><link rel="self" href="..." /></li></ul></td>
<td><ul><li><channel></li><li><link></li></ul></td>
<td><ul><li><channel></li><li><link></li></ul></td>
<td>A M3U file.</td>
<td><ul><li><channel></li><li><link></li></ul></td>
<td style="background-color:#eeeeee;color:black;"><em>need a new microformat</em></td>
</tr>
<tr>
<td style="background-color:darkorange;color:black;font-weight:bold;"><em>Episode</em> Concept</td>
<td><ul><li><atom:entry></li><li><link rel="alternate" href="..." /></li></ul></td>
<td><ul><li><item></li><li><link></li></ul></td>
<td><ul><li><item></li><li><link></li></ul></td>
<td>A single URL line.</td>
<td><ul><li><item></li><li><link></li></ul></td>
<td style="background-color:#eeeeee;color:black;"><em>need a new microformat</em></td>
</tr>
<tr>
<td style="background-color:darkorange;color:black;font-weight:bold;"><em>Media</em> Concept</td>
<td><ul><li><atom:link rel="enclosure" href="..." /></li><li>also... dependent on <em>type</em> of data embedded in or referenced from <atom:content></li></ul></td>
<td><enclosure></td>
<td><media:content></td>
<td>Simply the inclusion of a URL on a line.</td>
<td><enclosure></td>
<td style="background-color:#eeeeee;color:black;"><img> <br /> <a href=""> <br /> <object> <br /> <embed> </td>
</tr>
</table>

== Vidéo ==
* [http://www.exif.org/Exif2-2.PDF EXIF] - (Yes, the spec deals with video taken by still cameras. -- RyanKing)
* [http://www.chiariglione.org/mpeg/standards/mpeg-7/mpeg-7.htm MPEG-7] - MPEG-7, formally named "Multimedia Content Description Interface", is a standard for describing the multimedia content data that supports some degree of interpretation of the information meaning, which can be passed onto, or accessed by, a device or a computer code. (Very powerful, but you have to pay for documentation -- [[User:ChristopherA|ChristopherA]] 01:53, 29 Jun 2005 (PDT))
* [http://www.w3.org/AudioVideo/ SMIL] - Synchronized Multimedia Integration Language (SMIL, pronounced "smile") enables simple authoring of interactive audiovisual presentations. (Not exactly video, but has a lot of useful video-related features in it. -- [[User:ChristopherA|ChristopherA]] 01:55, 29 Jun 2005 (PDT))
* [[video-metadata-model| Video Metadata Model - un point de départ]]

== Interactive ==
* [http://www.w3.org/Graphics/SVG/ SVG]
* [http://www.w3.org/AudioVideo/ SMIL]
* QTVR ?

== Média Hors ligne ==
* [http://xspf.org XSPF] (media may be either offline or online)

=== Publications Imprimées (livres/magazines) ===
* [http://amazon.com/ Amazon]

=== Films ===
* [http://imdb.com/ IMDB]
* [http://amazon.com/ Amazon]

=== Musique ===
* [http://freedb.org/ FreeDB]
* [http://musicbrainz.org/ MusicBrainz]
* [http://amazon.com/ Amazon]

== Formats Conteneurs ==
The purpose of <strong>container formats</strong> is to allow the muxing of multiple codecs into a single file or stream. For example, if you want audio, video, and text (subtitles) combined into a single stream.

The purpose of the muxing is for synchronization and so that you can <em>stream</em> the file and <em>view it</em> without having to jump around -- seek -- in the file.

Container formats include:
* AVI
* MPEG
* Ogg
* QuickTime

=== Tableau de Comparaison de Format Conteneurs ===

<table border="1" cellpadding="5" cellspacing="0" style="border:1px solid grey;">
<tr>
<th>Aspect</th>
<th>AVI</th>
<th>MPEG</th>
<th>Ogg</td>
<th>QuickTime</th>
<th>Microformat?</th>
</tr>
<tr>
<td style="background-color:darkorange;color:black;font-weight:bold;">Allows Audio</td>
<td>Yes</td>
<td>Yes</td>
<td>Yes</td>
<td>Yes</td>
<td style="background-color:#eeeeee;color:black;"></td>
</tr>
<tr>
<td style="background-color:darkorange;color:black;font-weight:bold;">Allows Video</td>
<td>Yes</td>
<td>Yes</td>
<td>Yes</td>
<td>Yes</td>
<td style="background-color:#eeeeee;color:black;"></td>
</tr>
<tr>
<td style="background-color:darkorange;color:black;font-weight:bold;">Allows Text</td>
<td></td>
<td></td>
<td>Yes</td>
<td>Yes</td>
<td style="background-color:#eeeeee;color:black;"></td>
</tr>
<tr>
<td style="background-color:darkorange;color:black;font-weight:bold;">Error Detection</td>
<td></td>
<td></td>
<td>Yes</td>
<td></td>
<td style="background-color:#eeeeee;color:black;"></td>
</tr>
</table>

=== Notes pour les Microformats ===
One of the problems with container formats is that it is often difficult and sometimes impossible to know the disposition of what they contain ahead of time (without reading the file).

For example, Ogg files use the MIME type <em>application/ogg</em> and generally use the extension <em>.ogg</em>. With only these 2 pieces of information, you cannot tell whether such an Ogg file contains video data or not.

There is room for a microformat to help with this. Perhaps something like:
<div style="font-family:monospace;white-space:pre;padding:1.5em;background-color:black;color:white;"><a <strong style="background-color:yellow;color:black;">class="moving-image"</strong> type="application/ogg" href="my.ogg">...</a></div>
Although, this can be done in other ways too. For example, using [http://changelog.ca/log/2005/08/21/rss-disposition-hinting-proposal disposition hinting] one could do something like:
<div style="font-family:monospace;white-space:pre;padding:1.5em;background-color:black;color:white;"><a <strong style="background-color:yellow;color:black;">type="application/ogg;disposition-type:moving-image"</strong> href="my.ogg">...</a></div>

Anothing thing for any Microformat to consider is that it may be the case that the data files that are muxed in the container format may also be offered in non-muxed forms. This is important when <em>alternatives</em> are offered.

== Formats Audio ==

Audio formats include:
* AAC
* MP3
* PCM WAV
* Speex
* Vorbis
* WMA

=== Tableau de Comparaison de Formats Audio ===

<table border="1" cellpadding="5" cellspacing="0" style="border:1px solid grey;">
<tr>
<th>Aspect</th>
<th>AAC</th>
<th>MP3</th>
<th>PCM WAV</td>
<th>Speex</th>
<th>Vorbis</th>
<th>WMA</th>
<th>Microformat?</th>
</tr>
<tr>
<td style="background-color:darkorange;color:black;font-weight:bold;">Lossless</td>
<td>No</td>
<td>No</td>
<td>Yes</td>
<td>Yes</td>
<td>No</td>
<td></td>
<td style="background-color:#eeeeee;color:black;"></td>
</tr>
<tr>
<td style="background-color:darkorange;color:black;font-weight:bold;">Lossy</td>
<td>Yes</td>
<td>Yes</td>
<td>No</td>
<td>No</td>
<td>Yes</td>
<td>Yes</td>
<td style="background-color:#eeeeee;color:black;"></td>
</tr>
<tr>
<td style="background-color:darkorange;color:black;font-weight:bold;">Streamable</td>
<td>Yes</td>
<td>Yes</td>
<td></td>
<td>Yes</td>
<td>Yes</td>
<td>Yes</td>
<td style="background-color:#eeeeee;color:black;"></td>
</tr>
</table>

=== Notes pour les Microformats ===
* Knowing whether audio data is <em>streamable</em> or not can affect <em>pre-fetching</em>. And can be a metric used when alternatives of the <em>same file</em> is given.
* Having audio data marked as <em>lossy</em> or <em>lossless</em> can be useful when alternatives of the same file is made.

== Formats de Lecture ==
Playing formats include:
* ASX
* Atom
* Atom+SMIL
* Atomic RSS
* Atomic RSS+SMIL
* Extended M3U
* HTML+Time
* iTunes RSS
* KPL
* M3U
* MAGMA
* Media RSS
* PLS
* RAM
* RSS 2.0
* SMIL
* WAX
* WVX

=== Tableau Comparatif Format de Lecture ===
<table border="1" cellpadding="5" cellspacing="0" style="border:1px solid grey;">
<tr>
<th>Aspect</th>
<th>ASX</th>
<th>Atom</th>
<th>Atom+SMIL</th>
<th>Atomic RSS</th>
<th>Atomic RSS+SMIL</th>
<th>Extended M3U</th>
<th>HTML+Time</th>
<th>iTunes RSS</th>
<th>Media RSS</th>
<th>M3U</td>
<th>RSS 2.0</th>
<th>Microformat?</th>
</tr>
<tr>
<td style="background-color:darkorange;color:black;font-weight:bold;"><em>Alternatives</em> Playing</td>
<td></td>
<td><em>nothing</em></td>
<td></td>
<td></td>
<td><smil:switch></td>
<td></td>
<td></td>
<td><em>nothing</em></td>
<td><media:group></td>
<td><em>nothing</em></td>
<td><em>nothing</em></td>
<td style="background-color:#eeeeee;color:black;"><em>need a new microformat</em></td>
</tr>
<tr>
<td style="background-color:darkorange;color:black;font-weight:bold;"><em>Parallel</em> Playing</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td style="background-color:#eeeeee;color:black;"><em>need a new microformat</em></td>
</tr>
<tr>
<td style="background-color:darkorange;color:black;font-weight:bold;"><em>Sequence</em> Playing</td>
<td></td>
<td>if you consider the Atom file a <em>show</em>, then <em>nothing</em>. if you consider the Atom file an <em>episode</em>, then the list of <atom:entry>'s provides a sequence.</td>
<td></td>
<td></td>
<td><smil:seq></td>
<td></td>
<td></td>
<td>if you consider the RSS file a <em>show</em>, then <em>nothing</em>. if you consider the RSS file an <em>episode</em>, then the list of <item>'s provides a sequence.</td>
<td>if you consider the RSS file a <em>show</em>, then <em>nothing</em>. if you consider the RSS file an <em>episode</em>, then the list of <item>'s provides a sequence.</td>
<td>if you consider the M3U file a <em>show</em>, then <em>nothing</em>. if you consider the M3U file an <em>episode</em>, then the URL lines provide a sequence.</td>
<td>if you consider the RSS file a <em>show</em>, then <em>nothing</em>. if you consider the RSS file an <em>episode</em>, then the list of <item>'s provides a sequence.</td>
<td style="background-color:#eeeeee;color:black;"><em>need a new microformat</em></td>
</tr>
<tr>
<td style="background-color:darkorange;color:black;font-weight:bold;">Pre-Fetching</td>
<td></td>
<td><link rel="enclosure" href="..." /></td>
<td><ul><li style="white-space:pre;"><link rel="enclosure" href="..." /></li><li><smil:prefetch></li></ul></td>
<td><link rel="enclosure" href="..." /></td>
<td></td>
<td></td>
<td></td>
<td><enclosure></td>
<td><media:content></td>
<td>The M3U format is just list of URL's, with each URL on its own line. Pre-Fetching would be accomplished by just added a URL to the list.</td>
<td><enclosure></td>
<td style="background-color:#eeeeee;color:black;">[[rel-enclosure]]</td>
</tr>
</table>

== Formats Images Graphiques ==
Raster graphic formats include:
* GIF
* PNG
* JPEG

== Formats Vectoriels Graphiques ==
Vector graphic formats include:
* SVG

= Formats & Protocoles =

== AAC ==
<strong>AAC</strong> (<strong>Advanced Audio Coding</strong>) is a lossy audio format. Like MP3, AAC is part of the MPEG standard. Since April 2003, AAC has become an integral part of Apple's iPod and iTunes products. This association between AAC and Apple has become so strong among some that AAC is also sometimes call <em>Apple Audio Codec</em>.

Références:
* http://en.wikipedia.org/wiki/Advanced_Audio_Coding

== ASF ==
<strong>ASF</strong> is an Audio/Video format. ASF files that contain only audio data are typically called WMA files.

References:
* http://en.wikipedia.org/wiki/Advanced_Streaming_Format

== Atom ==
<strong>Atom</strong> is a XML-based syndication format that was developed by certain members of the RSS community.

Références :
* http://atomenabled.org/developers/syndication/
* [http://www.faqs.org/rfcs/rfc3339.html RFC 3339]

== Atom+SMIL ==
<strong>Atom+SMIL</strong> is Atom with SMIL used in the <atom:content>.

(This was originally used by [http://changelog.ca/ Charles Iliya Krempeaux] for "Internet TV". Also see <em>Atomic RSS+SMIL</em>)

== Atomic RSS ==
<strong>Atomic RSS</strong> is a syndication format that is RSS with Atom used as an extension module.

References:
* http://www.tbray.org/ongoing/When/200x/2005/07/27/Atomic-RSS

== Atomic RSS+SMIL ==
<strong>Atomic RSS+SMIL</strong> is Atomic RSS with SMIL use in the <atom:content>.

(This was originally used by [http://changelog.ca/ Charles Iliya Krempeaux] for "Internet TV".)

== AVI ==
<strong>AVI</strong> is a container format for Audio/Video formats.

References:
* http://en.wikipedia.org/wiki/AVI

== B4S ==
<strong>B4S</strong> is a playlist format.

References:
* http://gonze.com/playlists/playlist-format-survey.html#B4S

== BitTorrent ==
<strong>BitTorrent</strong> is a P2P protocol.

References:
* http://www.bittorrent.com/protocol.html
* http://en.wikipedia.org/wiki/Bittorrent
* http://wiki.theory.org/BitTorrentFAQ

== Creative Commons RDF ==

References:
* http://gonze.com/playlists/playlist-format-survey.html#Creative

== DAAP ==

References:
* http://gonze.com/playlists/playlist-format-survey.html#DAAP

== Extended M3U ==

References:
* http://gonze.com/playlists/playlist-format-survey.html#M3U
* http://hanna.pyxidis.org/tech/m3u.html
* http://en.wikipedia.org/wiki/M3U

== FLAC ==
Free Lossless Audio Codec (FLAC)
* http://flac.sourceforge.net/

== GIF ==
<strong>GIF</strong> is a raster graphics format and a movie format.

== HTML+Time ==

References:
* http://www.w3.org/TR/NOTE-HTMLplusTIME
* http://gonze.com/playlists/playlist-format-survey.html#HTML

== HTTP ==

References:
* http://www.w3.org/Protocols/

== iTunes Library ==

References:
* http://gonze.com/playlists/playlist-format-survey.html#iTunes

== iTunes RSS ==

References:
* http://www.apple.com/itunes/podcasts/techspecs.html

== JPEG ==
<strong>JPEG</strong> is a raster graphics format.

== Kapsule ==

References:
* http://gonze.com/playlists/playlist-format-survey.html#Kapsule

== KPL ==
<strong>KPL</strong> is a playlist format.

References:
* http://gonze.com/playlists/playlist-format-survey.html#KPL

== M3U ==
<strong>M3U</strong> is a playlist format.

References:
* http://gonze.com/playlists/playlist-format-survey.html#M3U

== MAGMA ==

References:
* http://gonze.com/playlists/playlist-format-survey.html#MAGMA

== Media RSS ==
<strong>Media RSS</strong> is a syndication format that is RSS with the addition of the <em>Media RSS Module</em>.

== MKV/MKA ==
Matroska <strong>MKV/MKA</strong> are video and audio containers, respectively.
* http://www.matroska.org/

== MNG ==
<strong>MNG</strong> is a Video format.

== MP3 ==
<strong>MP3</strong> is an Audio format.

== MPEG ==
<strong>ASF</strong> is an Audio/Video format.

== MusicBrainz ==

References:
* [http://www.MusicBrainz.org MusicBrainz.org]
* [http://wiki.musicbrainz.org MusicBrainz wiki]
* http://gonze.com/playlists/playlist-format-survey.html#musicbrainz

== Ogg ==
<strong>Ogg</strong> is a media container format.

References:
* http://xiph.org/ogg/
* http://en.wikipedia.org/wiki/Ogg
* [http://xiph.org/ogg/doc/rfc3533.txt RFC 3533] - The Ogg Encapsulation Format Version 0
* [http://xiph.org/ogg/doc/rfc3534.txt RFC 3534] - The application/ogg Media Type

== PLS ==
<strong>PLS</strong> is a playlist format.

References:
* http://gonze.com/playlists/playlist-format-survey.html#PLS
* http://en.wikipedia.org/wiki/PLS_(file_format)

== RAM ==
<strong>RAM</strong> is a playlist format.

References:
* http://gonze.com/playlists/playlist-format-survey.html#RAM

== RSS 2.0 ==
<strong>RSS 2.0</strong> is the defacto standard syndication format.

References:
* http://developer.mozilla.org/en/docs/RSS

== RTSP ==

References:
* http://www.rtsp.org/
* [http://www.ietf.org/rfc/rfc1889.txt RFC 1889]
* http://en.wikipedia.org/wiki/Real_Time_Streaming_Protocol

== SMIL ==

References:
* http://www.w3.org/AudioVideo/

== Speex ==

References:
* http://www.speex.org/

== SVG ==
<strong>SVG</strong> is a vector graphics format.

== Theora ==
<strong>Theora</strong> is an Audio/Video format/

References:
* http://www.theora.org/
* http://en.wikipedia.org/wiki/Theora

== Vorbis ==
<strong>Vorbis</strong> is an Audio format.

References:
* http://xiph.org/vorbis/
* http://vorbis.com/
* http://en.wikipedia.org/wiki/Vorbis

== WAX ==
<strong>WAX</strong> is an SGML-based playlist for that looks exactly like ASX and WVX, except that it can only reference to ASF or WMA, but NOT to WMV files.

References:
* http://gonze.com/playlists/playlist-format-survey.html#WAX

== WMA ==
<strong>WMA</strong> is an Audio format.

References:
* http://en.wikipedia.org/wiki/Windows_Media_Audio

== WMV ==
<strong>WMV</strong> is an Audio/Video format.

References:
* http://en.wikipedia.org/wiki/Windows_Media_Video

== WVX ==
<strong>WVX</strong> is an SGML-based playlist format that looks exactly like ASX and WAX, except that it can reference ASF, WMA, and WMV media files.

References:
* http://gonze.com/playlists/playlist-format-survey.html#WVX

= Commentaires =

* Voir le document séparé sur [[media-metadata-issues]]
** à traduire sur [[media-metadata-issues-fr]] -- [[Christophe Ducamp]]

= Voir aussi =

* [[video-metadata-models]]
** à traduire vers [[video-metadata-models-fr]]

hresume-faq

2007-05-28T13:20:11Z

RobertBachmann: Reverted edit of QadTrm, changed back to last version by Singpolyma

<h1> hResume FAQ </h1>

This page is for documenting Q&A about [[hresume|hResume]]. 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] mailing list. New questions and answers should be added to the end of the list. If you have a new question but not an answer, please add it to [[hresume-issues|hResume issues]].

<h2>Editing this Page</h2>
Please do not use "?" or other punctuation in the headers - it helps to keep the URLs to their fragment identifiers shorter and easier to read, copy/paste etc. See [[how-to-play]] for more wiki editing guidelines.

__TOC__

<h2> Q&A </h2>

=== Can contact information, or at least an address, be associated with an educational institution ===
-- [[User:Singpolyma|singpolyma]] 18:28, 29 Apr 2007 (PDT)

=== Was HR-XML considered ===
''Question: has any consideration for hr-xml (http://www.hr-xml.org) been given in the production of hResume microformat? I tried looking around the site but couldn't find anything specific. As someone working in the recruitment marketing industry I can see distinct benefits for the two formats converging. [[User:Strawbleu|Strawbleu]] 12:09, 15 Dec 2006 (GMT)'' (originally asked on [[hresume-feedback|hResume feeedback]] page.)
*Answer: Yes, [[resume-formats#HR-XML|HR-XML]] was documented as part of the research done into pre-existing resume formats as part of the microformats [[process]] in the development of a [[resume]] microformat. Since HR-XML was developed more a priori than a posteriori (see [[why-examples]]), it is likely to contain much that is not used by the 80% of resume publishers and thus it is unlikely that the two formats will ever converge. However, as more examples are found of new resume features, they are likely to be included in [[hresume|hResume]] over time, and HR-XML will be one of several formats that will be used as sources for vocabulary re-use.

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

picoformats-fr

2007-05-28T13:20:04Z

RobertBachmann: Reverted edit of MejP5y, changed back to last version by JeanChristopheCapelli

<h1> Picoformats </h1>

== Contributeurs ==
* [http://highearthorbit.com Andrew Turner]
* [http://factoryjoe.com/blog Chris Messina]
* Andy Stack de [http://mozes.com Mozes]

(traduction française en cours [[Christophe Ducamp]])

== Introduction ==

Les picoformats représentent un effort actuellement entrepris par [http://factoryjoe.com/blog Chris Messina] et Andy Stack de [http://mozes.com Mozes] pour codifier différents standards et poursuivre ouvertement une nomenclature et une syntaxe afin de communiquer et exécuter des commandes avec des terminaux mobiles via SMS.

Un exemple d'application est l'usage par [http://dodgeball.com Dodgeball] du symbole (@) pour exprimer un lieu.

Utiliser le processus des Microformats et les principes du design de construction de blocs, notre but est ouvertement de développer une syntaxe complète pour interagir avec différents services mobiles en utilisant les caractères disponibles sur la plupart des terminaux mobiles.

== Enoncé du Problème ==
# envoyer des messages à des utilisateurs de mobiles - via SMS, ou une petite application peut contenir de l'information comme des heures de rendez-vous, des lieux, des directions et une information de contact. Par exemple, rappeler aux utilisateurs quand ils ont besoin de partir pour se rendre à leurs rendez-vous, aussi le message peut ressembler à :

leave @ 4:35PM ~Dentist Office -> Detroit, MI

où le texte lui-même est simple et lisible, mais ce *peut* être un petit utilitaire qui parserait le symbole @ pour ajouter l'événement au calendrier, le ~ pour permettre à la personne de rappeler rapidement ce contact, ou le -> pour tirer les Cartes/directions vers l'endroit.

# permettre aux utilisateurs d'écrire des messages pour interroger une application - ceci est similaire à ce que Mozez a démarré avec les notes :

when2where: ?today --- quels rendez-vous ai-je aujourd'hui ?
new @ 4PM ~Olive Garden -> Novi --- ajouter un rendez-vous

En plus du domaine naturel des terminaux mobiles, je pense que les picoformats sont utilisables dans n'importe quel autre contexte où le "balisage" est trop lourd. Par exemple, j'assemble aussi cela dans un robot IRC, whereisbot, qui annonce les endroits de l'utilisateur au fur et à mesure qu'il signe dans un canal, ou permet aux personnes de faire :

.whereami, ou .whereis <nick> pour géolocaliser d'autres personnes dans un canal.

Je veux 'baliser' l'information, mais placer du véritable XHTML ou XML est ennuyeux, parce qu'IRC ne parse pas du tout l'information. Ainsi à cette heure, la réponse est :

ajturner: .whereami
whereisbot: ajturner is in Northville, MI, US [42.4365 x -83.4884]

Ainsi ensuite quelqu'un pourrait écrire un parseur Picoformat pour
X-Chat/Colloquy/autre qui parserait le [ #### x #### ] et fournirait un lien url Carte.

Utiliser les flèches pour indiquer l'heure et le lieu, est quelque chose d'habituel venant des magnétoscopes et autres terminaux.
Quelques idées : <past >future ^now (le chapeau est aussi mémonique pour Here + At) ou >5 (dans un délai de 5 jours) >>5 (dans un délai de 5 semaines) >>>5 (5 mois)

Meeting <Leeds went well. ^Home. See you >london
Sorry, saw them <<2 wanna go see film >3?

== Syntaxes Documentées ==

* [[textmarks-syntax-fr|Textmarks]]
* [[kiboze-syntax-fr|Kiboze]]
* [[twitter-syntax-fr| Twitter]]
* [[mixd-syntax-fr | Mixd]]
* [[tfl-syntax-fr | Transport for London]]
* [[plazes-syntax-fr | Plazes]]
* [[stikkit-syntax-fr | Stikkit]] http://stikkit.com/
* [[actiontastic-syntax-fr | Actiontastic]]
* [[facebook-syntax-fr | Facebook Mobile]]

== Références ==
* [http://www.kiboze.com/kiboze/CustWorks.aspx Kiboze How it Works]
* Flagr : [http://www.flagr.com/help/howto#mobile_creating_flag Créer des flags mobiles]
* [http://www.dodgeball.com/glossary Glossaire Dodgeball]
* [http://twttr.com/t/help/lingo Twttr lingo]
* [http://twitternanoformats.wikispaces.com/ Twttr nanoformats]
* [http://skobee.com/email_howto Syntaxe email de Skobee]
* [http://www.meetmoi.com/1/meetmoi?wicket:bookmarkablePage=:com.mdate.web.GettingStarted#11 Syntaxe MeetMoi]
* [https://www.billmonk.com/about/sms Syntaxe BillMonk]

podcasts-fr

2007-05-28T13:19:51Z

RobertBachmann: Reverted edit of Ee5Llv, changed back to last version by Tantek

<h1> microformats podcasts </h1>

Cette page liste différents podcasts et enregistrements audio (et/ou vidéo) qui ont fourni des explications et discussions tant pour les [[microformats-fr|microformats]] en général que les microformats spécifiques. Voir aussi les pages des microformats [[press-fr|presse]], [[presentations-fr|présentations]] et [[screencasts-fr|vidéos]]. Note : Les podcasts qui mentionnent simplement les microformats sans rentrer dans plus de discussions de détail des descriptions ou usages ne seront pas cités.

SVP, sentez-vous à l'aise pour ajouter des liens vers les podcasts qui discutent de microformats !

Les podcasts les plus récents sont listés en premier.
== 2007 ==
* 5 janvier [http://www.webdirections.org/podcasts/WD06/microformats.mp3 John Allsopp: "Microformats"] podcast à partir de [http://webdirections.org Web Directions South 2006-09-28]. Time ??:??.

== 2006 ==
* 5 novembre [http://www.flipclip.net/clips/siva001/692d23f566c59fa5059df18e4faf0a36 Fumi Yamazaki et Tantek Çelik sur les Microformats] (video [http://creativecommons.org/licenses/by-nc/2.1/jp/ CC-by-nc 2.1-jp]), en général, [[hcard-fr|hCard]], exemple d'ajout à un carnet d'adresses, [[hcalendar-fr|hCalendar]], Exemple d'abonnement à un Calendrier et démonstration. Fumi parle en japonais, Tantek parle en anglais et se périodiquement traduire en japonais.
* 11 octobre [http://media.libsyn.com/media/carsonsystems/Tantek_Celik.mp3 Tantek : "Microformats Practices"] podcast extrait de la session du 13 septembre 2006 [[events/2006-09-13-future-of-web-apps-microformats|The Future of Web Apps à San Francisco]]. Time ??:??.
* 25 Septembre [http://www.vivabit.com/atmedia2006/blog/index.php/tantek-celik-microformats-evolving-the-web-podcast/ Tantek: "Microformats: Evolving the Web] podcast extrait de la session du [[events/2006-06-16-atmedia-microformats|16 juin - @Media 2006]]. Time 1:00:12
* 11 septembre [http://www.boagworld.com/archives/2006/09/dconstruct_web_services.html Paul Boag parle à Jeremy Keith des microformats]. L'interview démarre à 8:10 et finit à 15:42.
* 5 septembre [http://www.beet.tv/2006/09/technorati_is_t.html Beet.tv interviewe Peter Hirshberg sur la vidéo et les microformats]
* 8 août [http://www.verkko2.com/2006/08/06/jakso-2-mikroformaatit/ Jakso 2: Mikroformaatit] (Finnois) ([http://www.zengestrom.com/blog/2006/08/verkko2_on_micr.html English]). Jyri Engeström a interviewé Tantek Çelik et Ryan King à propos de leur travail sur les microformats chez Technorati et à propos des microformats en général. Il y a une introduction en finnois, mais l'entretien est en anglais.
* 30 juin [http://www.weblogswork.com/2006/06/30/weblogs-worknotes-hresume/ Weblogs Worknotes: hResume]. "Alexander & moi ont donné à Tantek & Ryan une mise à jour des trucs hResume sur laquelle nous avons travaillée, et pendant que nous étions là, nous avons enregistré une discussion à propos de hResume et du succès des Microformats en général."
* 26 juin [http://www.boagworld.com/archives/2006/06/podcast_40_atmedia_mainstream_application.html atMedia - Applying the lessons learnt] de Boagworld.com (30Mb MP3). Paul Boag présente le concept des Microformats dans la section Technobuster du show (commence à 6:50), en réponse à la présentation de Tantek à @media 2006. Ciblé pour un public non technique.
* 11 avril 2006 [http://www.dustindiaz.com/episode-10/ Microformats, Drew, and lots of beer] (commence à la 42ème minute) Faute de meilleur titre, dans cet épisode Drew McLellan et moi ont eu la chance de discuter de la technologie des microformats avec quelques-uns de ses autres sites comme Dreamweaver Fever et 24ways. Autre que ça, nous avons discuté de quelques dernières actualités en cours sur le web comme le DOM Builder de Dan et le guide d'extension Firefox de William, et bien sûr joué à un autre jeu classique Pyramid 2.0 où j'ai échoué à nouveau misérablement.
* 5 avril : [http://pod-serve.com/audiofile/filename/949/Messina_on_Microformats.mp3 Weblogs Worknotes with Chris Messina (12 MB .mp3 ~ 20 min.] Dans la première partie de nos séries d'interviews sur les microformats, nous parlons avec Chris Messina.
* 5 avril : [http://www.web20show.com/articles/2006/04/04/web-2-0-show-episode-15-tantek-celik-ryan-king web2.0 show] Dans cet entretien SXSW, nous accrochons Tantek Celik et Ryan King de Technorati et des Microformats pour parler des choses sur lesquelles ils sont en train de travailler (besoin de la date de l'enregistrement)
* 31 mars : [http://blogs.msdn.com/alexbarn/archive/2006/03/31/566361.aspx Microformats Podcast] ([http://alexbarnett.audioblog.com/deluge/c6d4ccaa-b6e5-9604-a721-764467d8bc66.mp3 51 mins, .mp3, 12mb, CC-by-2.5]) avec Alex Barnett, Tantek Çelik, Dan Connolly et Rohit Khare.
* 23 mars : [http://www.technewsradio.com/2006/03/tech_news_radio_9.html TECH NEWS RADIO #273 | 060323| eTech 2006, Phil Windley, Digital Identity, Attention Economy, AOL, OpenAPI, Microformats] ([http://www.geekon.com/tnr/2006/03Mar/TNR_273_060323_Tech_News_Radio.mp3 6:55 mins, .mp3, 3.2mb, CC-by-sa-2.5])
** Sujets : Attention, Ray Ozzie's Cut and Paste for the Web, microformats, AOL
** Phil Windley : <blockquote>"In the last couple of years, microformats have kind of gone from this interesting idea, that people thought, 'ah yeah, that might be cool if you get can get anybody to do it', to dozens of companies that were here [at ETech] that had microformats built into their systems and were using them actively."</blockquote>
* 19 mars : [http://www.talkcrunch.com/2006/03/19/episode-2-social-networks-30/ TalkCrunch » Blog Archive » Episode 2: Social Networks 3.0] ([http://podcast.techcrunch.com/Techcrunch-Ep002-SocialNetworks.mp3 43:40min, .mp3, 10.2MB]) avec Michael Arrington, Nik Cubrilovic, Reid Hoffman et David Hornik.
** Thématiques : Réseaux sociaux, microformats, numéros de version
** Démarre à 17:55 minutes, Mike Arrington demande à Nik : ''"Comment définissez-vous un Web 2.0 ou un Social Network 3.0 ?"''
** Nik : <blockquote>"Je pense que ce qui est intéressant est ce que Reid a évoqué plus tôt avec LinkedIn fabriquant désormais des pages disponibles pour le public, probablement une grande étape dont nous devrions plus parler, et je pense que c'est tout ce qu'est le Social Networking 3.0, à savoir supporter pleinement je l'esprère les [[microformats-fr|microformats]], et ce que voulais demander à Reid à ce sujet comme [[hcard-fr|hCard]] et [http://gmpg.org/xfn XFN] mais nous nous sommes quittés. Selon moi Social Networking 3.0 est le fait de ne pas avoir un unique réseau social de destination, cela parle de publier votre profil sur le web, et de disposer de tous ces services supplémentaires aux alentours et de faire monter toute cette information pour la rendre disponible à n'importe qui d'autre. Parce que si vous pensez à la manière dont les réseaux sociaux fonctionnent dans la vraie vie, c'est que vous n'avez pas une énorme destination où tout le monde se regroupe mais bien des plus petits réseaux sociaux de 10, 15, 20 personnes. Ainsi si LinkedIn fait en sorte que ses pages soient publiques, ce que cela signifie est que je peux construire un réseau social, et je peux dire que ces 3 personnes venant de Linkedin et ces 8 personnes qui ont des blogs font toutes partie de ce réseau social. Le Social Networking 3.0 pour moi est de la <em>décentralisation</em> de réseaux sociaux, c'est le support de ces [[microformats-fr|microformats]], et le fait de pouvoir annoncer toute cette information ensemble en utilisant d'autres services."</blockquote>
* 16 février (enregistré le 7 février) : [http://www.release1-0.com/freshproduce/newideas_socialtime.cfm Discussing events online] inclut un petit segment de Tantek disctant de microformats et [[hcalendar-fr|hCalendar]] particulièrement à 4 minutes et 39 secondes. Video.

== 2005 ==
* September 30th [http://odeo.com/audio/270407/view Microformats: Evolving the Web (Incomplete)]

== Recherche ==
* [http://www.podcast.de podcasts] allemands sur [http://www.podcast.de/suche/nach/mikroformat*/in/ShowSearch micro formats]

metalink-examples

2007-05-28T13:19:46Z

RobertBachmann: Reverted edit of UihHlg, changed back to last version by Ant

'''Please incorporate this into [[alternates-examples]] as it is substantially the same problem. Thanks! Tantek'''

= Metalink Examples =
A microformat similar to the [http://www.metalinker.org Metalink] file format for aggregating the ways to get the same exact file.

== The Problem ==
For downloading some files, mirrors are listed without any way of being used automatically by programs that do segmented downloading (Web browsers or download managers). There are many different ways of downloading a file; we want people's clients to choose the best way and location, rather than them having to.

== Participants ==
* Gervase Markham
* Ant Bryan
== Real-World Examples ==

== Who offers Mirror downloads for software ==
This is only a small sampling.
*[http://sourceforge.net/index.php Sourceforge]

=== Example #1: [http://arklinux.org/index.php?option=com_content&task=view&id=5&Itemid=18 Ark Linux Download] ===
You can download Ark Linux Home 2006.1-rc2 from any of the following locations (you should typically pick one close to your location, unless it is overloaded):
Name

Location Protocols

North Carolina, USA FTP HTTP

Oregon, USA FTP HTTP

Kent, UK FTP HTTP

Amsterdam, The Netherlands FTP HTTP

Amsterdam, The Netherlands FTP HTTP

Dublin, Ireland FTP HTTP

Poland FTP

Thessaloniki, Greece FTP HTTP

The torrent file is here.

== Existing Practices ==
Most solutions are manual (wading through FTP sites on mirrors to find the exact file) or by searching against a filename & size.

== Proposal ==
A microformat for Mirrors could make them more usable. Web browsers or download managers could be modified to use them automatically.

<pre>
<div class="metalink">
<a href="http://www.foo.com/foo.zip!md5!FFEEE542543...">HTTP
download</a>
<a href="ftp://www.foo.com/foo.zip!md5!FFEEE542543...">HTTP
download</a>
<a href="http://www.foo2.com/foo.zip!md5!FFEEE542543...">HTTP
download</a>
<a href="http://www.foo.com/foo.torrent">Bittorrent download</a>
<a href="ed2k:/....">EDonkey download</a>
</div>
</pre>

It's pretty simple; the microformat states that all <a> links inside a
<sometag class="metalink"> are alternative ways of reaching the same
resource, and that when the UA sees a page like this it should
automatically pick the best one and begin downloading.

For legacy UAs, a stylesheet can hide the checksum spans if the author
wants to. No semantic information is present in the page text, which can
be freeform, in any language or whatever. The type of the link is
inferred from the scheme (in this case, http:) or the file extension
(e.g. .torrent) of the URL.

The microformat leverages [http://www.gerv.net/security/link-fingerprints/ Link Fingerprints] to embed the checksums where
required (BT, for example, has its own).

Alternatively, [[hash-examples]] could be used for checksums.

press-fr

2007-05-28T13:19:41Z

RobertBachmann: Reverted edit of Hm7Fq2, changed back to last version by ChristopheDucamp

<h1> Presse </h1>

__NOTOC__

Cette page documente les articles de presse sur les [[microformats-fr|microformats]].
Voir aussi les [[screencasts-fr|vidéos]], [[presentations-fr|présentations]], [[podcasts-fr|podcasts]], et les [[books-fr|livres]].

==Actuellement==
* [http://www.google.com/custom?domains=programmableweb.com&q=microformats&sitesearch=programmableweb.com Cherchez 'microformats' sur programmableweb.com]

== 2007 ==
=== Janvier 2007===
* [http://www.gcn.com/blogs/tech/42930.html ''Microformats get real''] dans ''Government Computer News'' (UK) (2007-01-15) par Joab Jackson
* [http://www.informationweek.com/blog/main/archives/2007/01/firefox_3_from.html Firefox 3: From HTML Renderer To Information Broker] par Mitch Wagner, Information Week. Discute des implications du support natif des microformats dans Fifefox (2007-01-03)
* [http://www.readwriteweb.com/archives/mozilla_does_microformats_firefox3.php Mozilla Does Microformats: Firefox 3 as Information Broker] - Read/ Write web, (2007-01-02)

== 2006 ==
=== Décembre ===
* [http://24ways.org/2006/styling-hcards-with-css 24 Ways: Styling hCards with CSS] Un article sur les 24 façons de styler hCard en utilisant CSS, John Allsopp (2006-12-14).

=== Novembre ===
* [http://accessify.com/news/2006/11/html-mastery/ Accessify.com announce ''HTML Mastery''] un nouveau livre de Paul Haine, avec un chapitre sur les microformats (2006-11-27).
* [http://www.netmag.co.uk .Net magazine (UK)], couverture décembre 2006, a un tutoriel sur les microformats, par Rachel Andrew (tutoriel non disponible en ligne)
* [http://www.ascii.co.jp/books/magazines/macpeople.shtml MacPeople], un magazine papier à propos du Macintosh au Japon, contenait un article à propos des microformats sur édition de 12/2006 écrit par [http://nobi.com/nobilog/ Nobuyuki Hayashi].
* Cover story in iX 11/2006 p. 62-65: [http://www.heise.de/ix/artikel/2006/11/062/ Mehrwert-Markup] (German: additional value markup)
* [http://www.architecturejournal.net/2006/issue8/F5_Patterns/default.aspx Patterns for High-Integrity Data Consumption and Composition], dans "The Architecture Journal", un journal en ligne d'architecture web publié par Microsoft, mentionne les microformats comme un moyen de maintenir un haute fidélité des données dans des systèmes vaguement joints et très fédérés. "The considerable variety of data these days includes an extensive array of XML-based formats, as well as increasingly widespread, lighter weight data formats such as the JavaScript Object Notation (JSON) and microformats."

=== Octobre ===
* [http://weblog.infoworld.com/techwatch/archives/008472.html INFOWORLD TECH WATCH: "Bloggers speak out on IE 7"] - publié le 20 octobre 2006. Mention/discussion des microformats par Tantek Çelik et Kristopher Tate.
* Practical Web Design, numéro d'Octobre 2006, article "Microformats" par Rachel Andrews
* W3C [http://www.w3.org/2006/10/grddl-pressrelease Communiqué de presse] Spec GRDDL

=== Septembre ===
* ...

=== Août ===
* [http://digital-web.com/articles/the_big_picture_on_microformats/ The Big Picture on microformats] - qui fait quoi avec les microformats à cette heure - par John Allsopp - Publié le 28 août 2006.
* [http://www.thinkvitamin.com/features/design/how-to-use-microformats Add microformats magic to your site] par John Allsopp - Publié le 25 août 2006.
=== Juillet ===
* [http://knowledge.wharton.upenn.edu/article.cfm?articleid=1526 Knowledge at Wharton: Tantek Çelik and Rohit Khare: The Progress and the Promise of Microformats] - Publié le 20 juillet 2006
=== Juin ===
* [http://devzone.zend.com/node/view/id/584 Microformats, PHP et hKit], venant de devzone.zend.com, une ressource développeurs PHP, 28 juin.
* [http://www.mercurytide.com/knowledge/white-papers/microformats Building a more semantic web with microformats], de Mercurytide, le 20 juin.
=== Mai ===
* [http://www.devsource.com/article2/0,1895,1961106,00.asp DevSource: An Developer's Introduction to Microformats by Phil Haack, May 11.].
** [http://www.elanceur.org/MicroFormats/IntroductionauxMicroForma.html Une traduction de cet article est en cours ici]... (attente autorisation de l'auteur)
** Voir aussi le [http://haacked.com/archive/2006/05/11/IntroductionToMicroformatsArticle.aspx billet de blog de Phil Haack à propos de l'article].

=== Avril ===
=== Mars ===
* (besoin de remplir ici - il y en a eu un paquet et je pense que nous avons simplement oublié de les ajouter dedans)
=== Février ===
* [http://book.mycom.co.jp/wd/ Web Designing], un magazine populaire pour l'industrie web au Japon, contenait un article à propos des microformats dans son article du mois de mars 2006.
* [http://www.release1-0.com/freshproduce/newideas_socialtime.cfm Release 1.0 / Ideas / New Ideas that Matter: Time as a social object], 16 février. Interviews Vidéo incluant un bout sur les microformats.
* [http://2006.sxsw.com/interactive/web_awards/finalists/ SXSW 2006 Web Awards Finalists], 3 février. [http://microformats.org microformats.org] est un finaliste dans la catégorie "Technical Achievement" pour "the sites that are re-inventing and re-defining the technical parameters of our online experience".
=== Janvier ===
* [http://code.google.com/webstats/index.html Google Web Authoring Statistics, 20 janvier]
*# La page d'accueil de l'étude "[http://code.google.com/webstats/index.html Web Authoring Statistics]" elle-même mentionne “microformats.org” et pointe vers http://microformats.org .
*# La page "[http://code.google.com/webstats/2005-12/pageheaders.html Page Headers]” remarque que [http://gmpg.org/xfn/ microformat XFN] est le profil de métadonnée le plus populaire : “…people do use the profile attribute, though. The three most-often used values are http://gmpg.org/xfn/1, http://dublincore.org/documents/dcq-html/, and http://gmpg.org/xfn/11. This makes XFN the most popular HTML metadata profile!”
*# La page “[http://code.google.com/webstats/2005-12/element-a.html a element]” a trouvé que trois des valeurs d'attributs ‘rel’ les plus populaires étaient des microformats : #1 [[rel-nofollow]], #2 [[rel-license]], #5 [[rel-tag]].
* [http://www.philoneist.com/50226711/interview_with_technorati_marketing_director_derek_gordon.php Philoneist: Interview With Technorati Marketing Director Derek Gordon by Jonathan G. Cohen, 11 janvier]
* [http://www.kbcafe.com/iBLOGthere4iM/?guid=20060101232742 #2 sur la liste des Best Web 2.0 Blogs, 2 janvier]

== 2005 ==
=== Décember ===
* [http://www.publish.com/article2/0,1759,1904359,00.asp Publish: Year in Review: CSS, Standards, Microformats and Flash, By Stephen Bryant, 21 décembre]
* [http://www.primezone.com/newsroom/news.html?d=91118 Newswire: Structured Blogging to support microformats, 13 décembre]
* [http://www.linuxjournal.com/article/8731 Linux Journal: Syndication and the Live Web Economy, de Doc Searls, 9 décembre]

=== Novembre ===
* [http://acmqueue.com/modules.php?name=Content&pa=showpage&pid=349&page=4 ACM Queue: A Conversation with Ray Ozzie, ACM Queue vol. 3, no. 9 novembre 2005]
* [http://www.digital-web.com/articles/microformats_primer/ Digital Web Magazine: Microformats Primer by Garrett Dimon, 14 novembre 2005]

=== Octobre ===
* [http://www.xml.com/pub/a/2005/10/19/microformats-and-web-2.0.html XML.com: Microformats and Web 2.0 de Micah Dubinko, 19 octobre 2005]
=== Septembre ===
* [http://channel9.msdn.com/Showpost.aspx?postid=118325 Channel 9: Interview at PDC] - Robert Scoble interviewe rapidement Tantek Çelik sur les standards Web, IE et les microformats.
=== Juillet ===
* [http://www.acm.org/technews/articles/2005-7/0722f.html#item12 ACM News Service - Volume 7, Issue 819: Friday, 22 juillet 2005]
* [http://lists.ssc.com/pipermail/suitwatch/2005-July/000090.html Linux Journal: SuitWatch -- 21 juillet-- par Doc Searls, Senior Editor of Linux Journal: Making More Sense of the Web]
* [http://knowledge.wharton.upenn.edu/index.cfm?fa=viewArticle&id=1247&specialId=38 Knowledge at Wharton: Supernova 2005: It's a Whole New, Connected World: What's the Next Big Thing on the Web? It May Be a Small, Simple Thing -- Microformats]
** Chinois simplifié : <http://knowledge2.wharton.com.cn//index.cfm?fa=article&articleid=1203&specialid=58&languageid=4>
** Chinois traditionnel :<http://knowledge2.wharton.com.cn//index.cfm?fa=article&articleid=1203&specialid=58&l=4&languageid=5>
** Version anglaise originale : <http://knowledge2.wharton.com.cn//index.cfm?fa=article&articleid=1203&specialid=58&languageid=1>

=== Juin ===
* [http://news.com.com/2030-12-5745034.html#microformats CNET News.com: Supernova 2005 blogcast] - David Weinberger interviewe Tantek Çelik et Rohit Khare à propos des microformats et de microformats [http://microformats.org/ microformats.org].
** [http://blog.blogcast2005.silkclips.com/clipView?http://silkblogs.com/FindResource/EC139870-22E5-F208-70FA-BC437BD64420/celik-khave-full.mov regardez l'interview avec Rohit Khare & Tantek Çelik (22:21 minutes)]
* Golem: [http://www.golem.de/0506/38831.html microformats.org - Formate für Menschen und Maschinen] (Allemand : microformats.org - Formats for humans and machines)

=== Mars ===
* [http://www.xml.com/pub/a/2005/03/23/deviant.html XML.com: What Are Microformats?]

operating-hours-examples

2007-05-28T13:19:36Z

RobertBachmann: Reverted edit of Wv1W7d, changed back to last version by Drago516

<h1>Operating Hours Examples</h1>

This page is for documenting real world examples of organizations (e.g. retail stores, restaurants, museums, offices) publishing operating hours. This page is a supplement to the [[operating-hours]] discussion.

__TOC__

= Discussion Participants =

== Editor ==
* [http://makedatamakesense.com/ Scott Reynen]

== Contributors ==
* [http://makedatamakesense.com/ Scott Reynen]
* [http://dragotown.com Nick Drago]

== Interested Folks ==

= Specific Examples from the Wild =

== Fry's Electronics ==

* [[http://www.frys-electronics-ads.com/frys-store-location.htm Website]]

<pre><nowiki>
<b><font size="4" face="Arial, Helvetica">Regular store hours for all Fry's Locations</font></b><br><br>
<font FACE="Arial,Helvetica" SIZE="2">Monday through Friday: <strong>8 AM - 9 PM</strong></font><br>
<font FACE="Arial,Helvetica" SIZE="2">Saturday: <strong>9 AM - 9 PM</strong><br>
Sunday: <strong>9 AM - 7 PM </strong></font></strong>
</nowiki></pre>

== Hobby Lobby ==

* [[http://www.hobbylobby.com/site3/store/hours.cfm Website]]

<pre><nowiki>
<tr><TD COLSPAN=3 WIDTH=303 align="center"> <H1>WEEK DAYS</H1> <B>MONDAY through SATURDAY</B> </TD></tr>
<tr>
<TD WIDTH=115 align="center"> <H3><FONT COLOR="#000066">WEEK DAY</FONT></H3> </TD>
<TD WIDTH=87 align="center"> <H3><FONT COLOR="#000066">OPEN</FONT></H3> </TD>
<TD WIDTH=101 align="center"> <H3><FONT COLOR="#000066">CLOSE</FONT></H3> </TD>
</tr>
<tr>
<Th align="left">Monday </Th>
<Th align="center">9:00 am </Th>
<Th align="center">8:00 pm </Th>
</tr>
<tr>
<Th align="left">Tuesday </Th>
<Th align="center">9:00 am </Th>
<Th align="center">8:00 pm </Th>
</tr>
<tr>
<Th align="left">Wednesday </Th>
<Th align="center">9:00 am </Th>
<Th align="center">8:00 pm </Th>
</tr>
<tr>
<Th align="left">Thursday </Th>
<Th align="center">9:00 am </Th>
<Th align="center">8:00 pm </Th>
</tr>
<tr>
<Th align="left">Friday </Th>
<Th align="center">9:00 am </Th>
<Th align="center">8:00 pm </Th>
</tr>
<tr>
<Th align="left">Saturday </Th>
<Th align="center">9:00 am </Th>
<Th align="center">8:00 pm </Th>
</tr>
<tr><td><br></td></tr>
<tr>
<TD COLSPAN=3 WIDTH=303 align="center"> <H3><FONT COLOR="#990000">ALL STORES CLOSED ON SUNDAY</FONT></H3> </TD>
</tr>
</nowiki></pre>

== US Embassy, Tokyo ==

* [[http://tokyo.usembassy.gov/fukuoka/wwwh2map.html Website]]

<pre><nowiki>
 Operating Hours: 9:00 a.m. - 4:00 p.m. Monday - Friday,
excluding <A HREF="http://japan.usembassy.gov/e/acs/tacs-holidays.html" TARGET="_blank" CLASS="new">Japanese and American holidays</A>. We are closed for lunch from
noon until 1:00 p.m.
<BR>
</nowiki></pre>

== Yale University Dining Services ==

* [[http://www.yale.edu/dining/options/hours.html Website]]

<pre><nowiki>
<p class="hdr-main" style="margin-top: 0;"><a name="commons"></a>Commons
Dining Room x 2-0455</p>
<ul type="square">
<li class="txt">Hot Breakfast: 7:45 am-11:00 am, <i>Monday
thru Friday</i></li>
<li class="txt">Lunch: 11:00 am-2:30pm, <i>Monday thru
Friday</i></li>
<li class="txt">Limited Lunch Menu: 2:30 pm-5:00 pm,
<i>Monday thru Thursday</i></li>
<li class="txt">Dinner: 5:00 pm-8:00 pm, <i>Monday thru
Thursday</i></li>
<li class="txt">Limited Dinner Menu: 8:00 pm-9:00 pm,
<i>Monday thru Thursday</i></li>
</ul>
</nowiki></pre>

== Best Buy Store Locater ==

* [[http://www.bestbuy.com/site/olspage.jsp?id=cat12092&type=page&_requestid=93763 Website]]

<pre><nowiki>
<script>titleCase('ITHACA NY')</script> (Store 384)</b></span><br>
<script>titleCase('40 CATHERWOOD RD')</script><br>
<script>titleCase('ITHACA')</script>, <script>titleCase('NY')</script> <script>titleCase('14850-1056')</script>
<br>
<b>Phone:</b> 607-257-6824<br>

<b>Hours:</b> Mon-Sat 10:00am-9:00pm<br>Sun 11:00am-7:00pm
<br><br>
<b>This store also features:</b><br>
</nowiki></pre>

= See also =
* [[operating-hours]]

measure-brainstorming

2007-05-28T13:19:25Z

RobertBachmann: Reverted edit of XleG3e, changed back to last version by Tantek

= Measure Microformat Brainstorming =

This page collects ideas on how to use semantic XHTML to represent unambiguously [[measure]]s.

== Guillaume Lebleu ==

Basic example with elementary unit using the abbr pattern and the UNECE code (see [[measure-formats]])

<pre>
<span class="length">5 <abbr class="unit" title="FOT">Feet</abbr></span>
</pre>

Optional "value" could be useful in some cases, for instance when the value is provided in plain text:

<pre>
<span class="length"><abbr class="value" title="5">Five</abbr> <abbr class="unit" title="FOT">Feet</abbr></span>
</pre>

==Andy Mabbett==

===Converter Extension===
This Firefox extension may be of interest. Note, though, that it's been criticised for having a "nag" screen: [https://addons.mozilla.org/firefox/2286/ Converter] [[User:AndyMabbett|AndyMabbett]] 15:32, 3 Oct 2006 (PDT)

:This is the author of that extension. I don't want to go much into this, but I just want to clarify this briefly. The part with the nag screen is wrong on two counts: (1) that dialog isn't there anymore, and (2) even if it was there, you only needed to read a paragraph and click a button to make it go away ''forever'' -- but you don't have to take my word for it, install it for yourselves and see. Andy's report is accurate however -- the extension '''''was''''' criticized for that dialog (that's what you get from your free extension's users when you ask for 15 seconds of their time in return for hundreds of hours of your time). --[[User:BogdanStancescu|BogdanStancescu]] 09:35, 9 Oct 2006 (PDT)

===HTML Entities===
*For squared and cubic values, the HTML entities <code>&sup2;</code> and <code>&sup3;</code> should be borne in mind.

*For temperatures and angels, the HTML entity <code>&deg;</code> exists.

*The following currency entities exist:
**<code>¤</code> - <code>&curren;</code> - currency
**<code>¢</code> - <code>&cent;</code> - cent
**<code>£</code> - <code>&pound;</code> - pound
**<code>¥</code> - <code>&yen;</code> - yen
**<code>€</code> - <code>&euro;</code> - Euro

==Bogdan Stăncescu==
Here are my findings related to automatic parsing of measurements on web pages while developing the [http://converter.mozdev.org Converter] extension. Please ask away if you want me to go into more detail on any of the topics -- I'm not sure which of my experiences are relevant to microformats, so I'm going to give you an overview of my conclusions.

By the way of an introduction, the Converter is a Firefox extension which tries to convert all measurements it finds in any web page to their Imperial or metric counterpart (e.g. Fahrenheit to Celsius, and Celsius to Fahrenheit; meters to feet and feet to meters). There are two steps to the conversion process: (1) identifying the measurements in the page, and (2) converting them. As expected, the conversion part is trivial, at least conceptually. The parsing is the tricky bit, and that's also where the Converter's challenges also become relevant for microformats.

Here are the main challenges I have encountered while writing the Converter:

;Presentation standardization: The first, biggest and most obvious challenge is lack of almost any ''de facto'' standardization in respect to data presentation. What I mean is that although the units themselves are more or less standardized (more on that later), they are ''presented'' in various ways within web pages. Take these examples: "50 foot monster", "50 ft monster", "50 feet monster", "50-foot monster", "50-feet monster" -- and my personal favorite, "fifty-foot monster" (more on this later);

:Note that using a microformat using in particular the [[abbr-design-pattern]] would make each of these examples less ambiguous if not unambiguous. See below --[[User:Guillaume_Lebleu|Guillaume_Lebleu]]:

<pre>
<span class="height"><span class="value">50</span><abbr class="unit" title="FOT">foot</abbr></span> monster
</pre>

<pre>
<span class="height"><span class="value">50</span><abbr class="unit" title="FOT">ft</abbr></span> monster
</pre>

<pre>
<span class="height"><span class="value">50</span>-<abbr class="unit" title="FOT">foot</abbr></span> monster
</pre>

<pre>
<span class="height"><span class="value">50</span><abbr class="unit" title="FOT">feet</abbr></span> monster
</pre>

<pre>
<span class="height"><abbr class="value" title="50">fifty</abbr><abbr class="unit" title="FOT">foot</abbr></span> monster
</pre>

:: Of course; as far as I could gather, that's actually the ''purpose'' of microformats -- bridging the gap between what humans and machines can understand, no? --[[User:BogdanStancescu|BogdanStancescu]] 00:30, 11 Oct 2006 (PDT)

;Unit standardization: I live in Europe, where I've always used the metric system. As such, this probably was a much bigger nasty surprise for me than it is for a user of the Imperial/U.S. Customary system: in the Imperial system, the units themselves vary depending on where you are -- miles, pints, and a whole lot of other units come in many different flavors, but they're all written the same in regular usage;

;Language: "1 meter" vs. "1 metre" is a reasonable difference -- but non-SI units are usually translated. Even some SI units have different plurals, depending on the language, although in theory SI units are actually denoted by ''symbols'', not "words", as to make them non-translatable, and truly international (hence the name of the SI). I haven't really given much thought to a solution towards parsing these, because I find it overwhelming for the time.

;The sheer number of units: surprisingly, most people don't realize just how many units we humans have invented. Just take a look here: [http://www.asknumbers.com/ asknumbers.com] -- see how many categories there are? Now click on Flow Rate -- a non-ubiquitous type of measurement. Three sub-categories only for flow rates! Now click on Volume Flow Rate and take a look at the number of units in those lists. Remember, those are just in one of the three categories for flow rate! The UNECE standard mentioned in the [[measure-formats#Measure_Formats|measure formats]] page is useful to define just that -- a ''standard'' set of units. But in practice there are a lot more being used out there.

:Do you have examples from the Web (a URL) of non-UNECE units. One possibility would be to provide the ability for a unit to be defined as a division of products of other units. This is consistent with the [[measure-formats#Systeme_International]], which defines 7 base units and all other units as derived units (of course some units, even though they are derived are much easily represented as simple ones). This is what XBRL has done for financial/accounting/reporting. See [[currency-formats#XBRL]] and theorical example (ampere acre per second) below --[[User:Guillaume_Lebleu|Guillaume_Lebleu]]:

::Unfortunately I don't have URLs -- almost at all -- with measurements, although I've been in the "business" for a while. The reason for this is that I collect URLs of pages I encounter which are not properly parsed by the Converter, and when I release a version which understands those, I delete the URLs. Also, I never intended to cover all units in the Converter myself, for a multitude of reasons -- therefore I was never interested in the more exotic ones.

<small>Guillaume Lebleu's example</small>
<pre>
<span class="unit">
<abbr class="unit" title="AMP">Ampere</abbr> <abbr class="unit" title="ACR">acre</abbr> <span class="divide">per</span> <abbr class="unit" title="SEC">second</abbr>
</span>
</pre>

::Regarding your idea of breaking down the units in base units, that's something I've also been toying with in my head for the Converter. For my particular application, it's technically more difficult to implement this breakdown. For microformats, it would be easier, but there still remains at least one potential problem: you end up with a huge mess in the page. If a standard is too complicated to follow, one tends to give up altogether.

::Consider a document which actually discusses some sort of current variation per farm, and therefore needs to repeatedly refer to ampere acres per second. For human use, they'd simply define the AAS somewhere at the top of the document, and then refer to AAS, KAAS or MAAS as needed. Maybe a similar approach should be considered for microformats as well:

<pre>
We define the
<span class="unit_definition">
<abbr class="unit_name">AAS</span>
as
<abbr class="unit" title="AMP">Ampere</abbr>
<abbr class="unit" title="ACR">acre</abbr>
<span class="divide">per</span>
<abbr class="unit" title="SEC">second</abbr>
</span>.
</pre>

::And then use the "AAS" throughout the document as any other pre-defined unit. How would you define (and use) the KAAS (1000 AAS) or MAAS (1,000,000 AAS) though? Is there any standard way already to use data multipliers in microformats? Or should we discuss that? Or is it out of scope? --[[User:BogdanStancescu|BogdanStancescu]] 00:30, 11 Oct 2006 (PDT)

That's all I can think of as major hurdles right now. If I remember anything else, I'll post here. Please do give me feedback here if you want to ask more about any of the topics I touched above, or if you have other questions I might be able to reply to. --[[User:BogdanStancescu|BogdanStancescu]] 12:08, 9 Oct 2006 (PDT)

==Discoleo==
=== Measurement Classification ===

Because it is easier to provide examples, I will first list examples.

==== Categorical vs Ordinal Data ====

Various measurements may produce '''NON-Numerical''' values:
* a pain scale: '''most severe''', '''very severe''', '''severe''', ...
* or the TNM tumour classification system: T0, Tx, T1, T2, T3, T4, N0, ...

There is even a more fundamental issue related to numbers themselves, e.g.:
* '''Lists''' or '''Years''' are sometimes written using '''Roman Numbers'''
** however, the strings corresponding to ''Roman Numbers'', when sorted alphabetically, do NOT retain the correct order
** i.e. C (100) preceds L (50), which preceds X (10)
* there are other numbering schemes

==== A Single Value / Data Point ====

This is the most simple data format and pretty straitforward to implement.

* the distance between 2 cities is '''40 km'''
* the velocity is '''62 mph'''
* most other simple entires (...)

==== An Interval Measurement ====

* time: the shop is open between '''6am - 18pm''' on every day of the week, exept Saturdays from '''9am - 16pm''' and Sundays from '''9am - 13pm'''
**[[hcalendar|hCalendar]]? [[User:AndyMabbett|Andy Mabbett]] 09:24, 22 Nov 2006 (PST)

This is more about an interval measurement. Every variable can have 2 (or more) values, e.g.:
* the levels of rain fall were between 25mm - 35mm
* the maximum velocity of various cars was 220 - 250 km/h

Should these values be stored as separate values? [e.g. low / high]
Or should the microformats be able to store an interval?

See also the examples for statistical summaries below.

*Mark up each as a separate measurement, and wrap them in a "range" microformat? [[User:AndyMabbett|Andy Mabbett]] 11:36, 22 Nov 2006 (PST)

==== Matrices ====

* the GPS coordinates are '''12°14' N and 25°55' E'''
**[[geo|Geo]]? [[User:AndyMabbett|Andy Mabbett]] 09:25, 22 Nov 2006 (PST)
* the dimension of the box is '''3m x 2m x 0.55m'''
**this is three separate, single measurements, surely? [[User:AndyMabbett|Andy Mabbett]] 09:21, 22 Nov 2006 (PST)
** 3 x 2 x 0.55 cubic meter, still 3 measurements, BUT given as cubic meter => ONE measurement?
***Who writes 3x2x0.55 cubic meter? You'd write "3.3m<sup>3</sup>" [[User:AndyMabbett|Andy Mabbett]] 11:36, 22 Nov 2006 (PST)
** the surface was 2 x 3 square feet ???
***Who writes 2x3 sq ft? You'd write "2ftx3ft" or "6ft<sup>2</sup>" [[User:AndyMabbett|Andy Mabbett]] 11:36, 22 Nov 2006 (PST)

* IF we write "3.3m<sup>3</sup>" or "6ft<sup>2</sup>", we '''loose information'''
* IF I want a surface, I would prefer the '''sqare feet''' unit, and NOT '''...feet x ...feet'''
* writing for every measure a markup, will '''bloat''' the code extensively
** data matrices would be very effective here
*** how would you make such a matrix? There are different ways how such information can be "compounded". (length per time = speed, length * length = area). Maybe a we can group those measurements by a surrounding information, what the context is. --Emil 02:50, 25 Dec 2006 (PST)

==== Statistical Measurements ====

Often, a group of data is summarized using a statistics:
* the mean length was 1.3m (SD 0.12m, group size 22)
* the median age was 42 years (interquartile range 95% 18 - 97)

==== Measurement Scales ====

===== Accuracy vs. Precision =====

'''QUESTIONS'''
* How detailed should a measurement be stored?
**Microformats aren't for storing measurements; they're for "labelling" the measurements that are already present. [[User:AndyMabbett|Andy Mabbett]] 09:23, 22 Nov 2006 (PST)
* If Accuracy and precision are relevant to the measurement, how do we store these?

===== Standardization of Measurement =====

* sometimes we may need to store the calibration information / calibration curves
* we may need to store the reference point the measurement is based on
* we may need to store the '''normal values'''
** biomedical measurements are often laboratory dependent, so it does NOT make sense to have the measurement without the corresponding normal values
** e.g. anti-Hepatitis B surface antigen antibody (anti-HBs) Titer: 32 MIU/ml
*** normal: 0 (non-infected, non-past infection, non-immunity)
*** protective immunity: >10 MIU/ml
*** interpretation is however more complex, depending on other tests as well

== Emil Thies ==

From my understanding, this microformat should concentrate on the notation of a measurement. So there will be some aspects, which has to be covered (elsewhere?) to improve the automatic use it or this microformat only uses some base informationens (units / dimensions) and derives all used from those base / build-in once.

=== Dimension vs. Unit vs. Scale vs. Measurement ===

A measurement is the combination of a number (value) and a unit (kind).
* 3km (3 Kilo Metre = 3.000 Metre)

A unit is a view for a measure of a dimension. There are two kinds how units can be different to each user:
* Units Differ by Scale (Prefix)
** 3km is the same as 3.000 meter or 300.000 cm (Its the same unit, with a different prefix, which works like a factor for the value, to lower the amount of symbols / numbers. The scale should be an own element and we can make use of the standard prefixes, like they are defined on [http://aurora.regenstrief.org/UCUM/ucum.html#section-Prefixes The Unified Code for Units of Measure] or [http://www.w3.org/TR/mathml-units/#SI-prefixes MathML]).
* Different units of the same dimension can be transferred into each other.
** Metre is a unit of the dimension length.
** Foot is a unit of the dimension length.

A Dimension is a base-dimension (see SI-System) or a compound dimension.
* length is a base dimension
* time is a base dimension
* speed is a compound dimension (length per time). There for a measurement of speed has one number and two unit by a math expression, which form their own unit. e.g. 10 m/s (10 Metre per second).

If we express a measurement in a microformat by the unit, the dimension is indirect provided by it. But a microformat, which uses measurement as a part, needs to define the dimension of it, to keep the use of the unit as an user choice. So, we could have a general measurement element, which allows all kinds of units to use. As a derived format, we can have sub-formats, which limit the list of units (or define an alternate list) by only allowing specific dimension(s).

E.G.
* [[currency-proposal]], with the money element which uses the same elements value (should then replace amount), scale (should be introduced), unit (should replace currency) which is limit to the ISO 4217 list.
* length, which only allows units which measures the dimension length, like FOT, MTR ...

=== Identification of Units ===

There are so many Units around - not only the existing one. There are deprecated ones like from Rome empire etc. For example "[http://en.wikipedia.org/wiki/Foot_(unit_of_length) Foot]" is not an unique identification of a unit. There is not only the British and U.S., there are for example same old German ones, before those areas joined the international metre convention in 1875:
* 25 cm in Hessen
* 28,935 cm in Bremen
* 29,641 cm in Oldenburg
* 29,1859 cm in Bayern
* 30,385 cm in Meiningen-Hildburghausen
* 31,385 cm in Preußen
* 31,608 cm in Wien/Österreich
* 32,61 cm in Bad Homburg vor der Höhe
* 33 1/3 cm in der Pfalz

So there is the need of a unique identification of those units. I found two approach right:

==== In MathML ====

MathML [http://www.w3.org/TR/mathml-units/#definitionURL defines] the construction of an URI like:

<nowiki>http://base/units/unit name[/context][/country][#prefix]</nowiki>

<pre>
http://.../units/foot/de
</pre>

But as you can see, there is right now no way to distinguish the different German foots based on the area inside Germany. Furthermore the context is so variable, that the same unit can be described by different URLs.

==== In OpenMath ====

OpenMath [http://www.openmath.org/cdgroups/units.html defines] the units inside of content directories:

<pre>
http://www.openmath.org/cd/units_us1.xhtml#foot_us_survey
</pre>

So there is a unique URLs for a Unit, but not every Unit is covered.

=== Transformation of Units ===

A real benefit is the automatic transformation of a unit, so that the write can write the measurement in his context (e.g. in the U.S. foot, or a quote from an antike text in Rome Empire foot) and the reader can get a transformation in his context (e.g. the value in metre). There fore there is the need of additional transformation information. And there are some different kinds of transformation:

==== units of same dimension ====

e.g. foot to metre

==== units of compound but same dimension ====

e.g. metre/s and mach-number

==== compound measurement context ====

<pre>This switch works up to 5 Ampere by 220 Volt</pre>

The reader might to now, which Watt device he can attach (1100 Watt would be the answer).

<pre>The dimension of the box is 3m x 2m x 0.55m</pre>

There might be some question like:
* volume (3,3 m³)
* surface (17,5 m²)

=== Approach ===

A general measurement should make use of the following informations:

value: a number, which represents the amount of the measurement. The number should follow one of the following representation:
* natural (positive and negative): e.g. -1, 0, 1
* decimal fraction (positive and negative): e.g. -2.5, 0.123
* natural fraction (positive and negative): e.g. -2/3, 3/7
scale: a factor used to lower the needed numbers of the value. The scale should be either
* a letter to refer a build-in factor, which is defined in [http://aurora.regenstrief.org/UCUM/ucum.html#section-Prefixes The Unified Code for Units of Measure] or [http://www.w3.org/TR/mathml-units/#SI-prefixes MathML]).
* a number like defined on value
unit: the unit used for the measurement. The unit should follow one of the following representation:
* build-in short-form like defined on [http://www.unece.org/etrades/units.htm Standards for Trade and Electronic Business] (or any other defined list which will be defined as the standard list for this format)
* a reference to a unit definition. (I think there is the need of a markup/language to define new units and/or the transformation between units).

<pre>
<span class="measurement"><abbr class="value" title="5">Five</abbr> <abbr class="scale" title="k">kilo</abbr> <abbr class="unit" title="MTR">metre</abbr></span>
</pre>

when we have a defined sub-measurement format for length, it could also be written:

<pre>
<span class="length"><abbr class="value" title="5">Five</abbr> <abbr class="scale" title="k">kilo</abbr> <abbr class="unit" title="MTR">metre</abbr></span>
</pre>

==== List of possible Sub-Formats ====

Here is a (first) list of possible keywords for sub-formats and their unit list or compound kind:

* money - unit limit to the ISO 4217 List
* '''length''' - unit limited to e.g. MTR (Metre), FOT (Foot) ....)
** '''area'''
*** Either a measurement with units like MTK (Square Metre), FTK (Square Foot)
*** or a compound format with elements (width:length, height:length)
** '''volume'''
*** Either a measurement with units like MTQ (Cubic Metre), FTQ (Cubic Foot), LTR (Litre) ...
*** or a compound format with elements (width:length, height:length, depth:length)
* time or duration or '''period''' - unit limited to e.g. sec (second), min (minute) ...
* mass or '''weight''' - unit limited to GRM (Gram), ...
* power or '''electricity''' - unit limited to AMP (Ampere), OHM (Ohm), ...

photo-note-examples

2007-05-28T13:19:19Z

RobertBachmann: Reverted edit of NhvRyf, changed back to last version by Tantek

= Photo Note Examples =

This is a concrete discussion of what exists right now in the specific problem area of annotating areas of photos with notes.

This is a very specific type of [[media-info]] that is not as generic as [[media-info-examples]] in general.

== Contributors ==

* Tantek Çelik
* Greg Elin

== Examples ==

* http://fotonotes.net
** http://fotonotes.net
** ordered list of notes, each note has unique ID
** each note has:
*** rectangle / boundingbox
*** unique id
*** title (thought of as human readable alias for unique id)
*** content - plain text
*** author of the note
*** date of annotation

* http://www.frankmanno.com/ideas/css-imagemap/
** CSS based image maps

* http://evan.nixsys.bz/note
** CSS based image maps

* http://bayareafreefi.com/city.php?city=San%20Francisco
** uses standard text formatting
** imagemaps with onmouseover events to load the text to display

* http://conflix.soe.umich.edu/photos/collections/KyleHelson/9/annotation/
** divs containing spans of plain text, very unexciting.

* http://flickr.com
** http://flickr.com/photos/tantek/64877881/
** ordered list of notes (there is an order because if they overlap, the latter one "wins" in terms of hover)
** each note has:
*** rectangle
*** content - hypertext markup
*** author of the note (left blank and implied for first-person notes)

* fotobuzz (has based their stuff on fotonotes, without attribution.)
** http://2entwine.com/screenshots/pic5.html (haven't found an editable one yet)
** http://fotobuzz.org/ displays an example containing multiple comments within one "note"
** plain text, although they display their data in flash
** rectangles.

semantic-xhtml-design-principles

2007-05-28T13:19:02Z

RobertBachmann: Reverted edit of AfsU77, changed back to last version by JamesCraig

=Semantic XHTML Design Principles=

__TOC__

XHTML is built on XML, and thus XHTML-based formats can be used not only for convenient display presentation, but also for general-purpose data exchange. In many ways, XHTML-based formats exemplify the best of both HTML and XML worlds. However, when building XHTML-based formats, it helps to have a guiding set of principles.

# Reuse the schema (names, objects, properties, values, types, hierarchies, constraints) as much as possible from pre-existing, established, well-supported standards by reference. Avoid restating constraints expressed in the source standard. Informative mentions are ok.
## For types with multiple components, use nested elements with class names equivalent to the names of the components.
## Plural components are made singular, and thus multiple nested elements are used to represent multiple text values that are comma-delimited.
# Use the most accurately precise semantic XHTML building block for each object etc.
# Otherwise use a generic structural element (e.g. <code><span></code> or <code><div></code>), or the appropriate contextual element (e.g. an <code><li></code> inside a <code><ul></code> or <code><ol></code>).
# Use class names based on names from the original schema, unless the [[semantic-xhtml|semantic XHTML]] building block precisely represents that part of the original schema. If names in the source schema are case-insensitive, then use an all lowercase equivalent. Components names implicit in prose (rather than explicit in the defined schema) should also use lowercase equivalents for ease of use. Spaces in component names become dash '-' characters.
# Finally, if the format of the data according to the original schema is too long and/or not human-friendly, use <code><abbr></code> instead of a generic structural element, and place the literal data into the 'title' attribute (where abbr expansions go), and the more brief and human-readable equivalent into the element itself. Further informative explanation of this use of <code><abbr></code>: [[abbr-design-pattern]], [http://tantek.com/log/2005/01.html#d26t0100 Human vs. ISO8601 dates problem solved], and [http://www.webstandards.org/2007/04/27/haccessibility/ hAccessibility] aka "abbr-design-pattern considered harmful."

==Semantic XHTML and Microformats==
(from Tantek Çelik on the [http://article.gmane.org/gmane.comp.web.microformats.general/6014 microformats-discuss mailing list])

Note that microformats use semantic XHTML, but not all use of semantic
XHTML are microformats.

Web designers and authors are using semantic XHTML everyday without using
microformats, and that's perfectly fine. They are not trying to create
standards and interoperably/automatically exchange data with each other.
They are simply expressing the semantics of their documents.

Whereas microformats follow a specific process and are intended to provide
a way for publishers worldwide to easily interoperably exchange simple
bits of data.

http://microformats.org/wiki/process

This distinction between "semantic XHTML" and "microformats" is very
important to understand and is often confused - I've even seen W3C staff
themselves call microformats "just using good class names", which is
incorrect. (Using good class names is simply one of the practices of
semantic XHTML).

voting-examples

2007-05-28T13:18:58Z

RobertBachmann: Reverted edit of EgjOtw, changed back to last version by AndyMabbett

= Voting Examples =

== The Problem ==

There has been a good bit of discussion relating to how to represent the intent of a link from one site to another as an endorsement of that site or not. See Kevin Marks on voting ([http://epeus.blogspot.com/2003/03/vote-links.html Vote Links]) for initial arguments for a way to represent this information.

This page serves to document the current list of voting examples from real world sites for the design of a simple voting [[microformat]]. - [[User:SteveIvy|Steve Ivy]]

__TOC__

== Participants ==
* Kevin Marks
* Tantek Çelik
* Steve Ivy

== Related Pages ==
* [[voting-brainstorming]]

== Discussion/Concepts ==
(This may belong on a page of its own)
* [http://www.ashbykuhlman.net/blog/2002/09/06/0546 When is a link an endorsement?] - Nathan Ashby-Kuhlman
* [http://epeus.blogspot.com/2003/03/anti-links-linking-to-things-you.html Anti-links - linking to things you disagree with and saying so] - Kevin Marks
* [http://epeus.blogspot.com/2003/03/vote-links.html Vote Links] - Kevin Marks
* [http://jeremy.zawodny.com/blog/archives/000751.html PageRank is Dead] - Jeremy Zawodny

== Real-World Examples ==

=== Centralized Implementations ===
* [http://digg.com Digg] - Digg is essentially a centralized voting system for links. Digg users can "digg" (vote-for) a link. Links with more diggs float to the top of the popular lists, hence getting more exposure and getting more diggs/votes for and against. Markup is plain html - links and images. However, the semantics of a digg are still unclear - links often get many diggs though the majority of commenters disagree with the content of the linked page. Comments on links can also be voted for or against - 'digg' or 'bury'.
** Link and descriptions
** # of votes ('for' votes)
** controls to vote ('digg')
** controls to vote on comments ('digg' or 'bury')

* [http://www.urbandictionary.com Urban Dictionary] - dictionary of colloquialisms where users can vote up or down (for/against) terms in the dictionary. Markup is plain html - tables and images.
** Term and Definition
** # of votes 'up' and 'down'
** controls to vote ('up' or 'down')

* Google's [http://en.wikipedia.org/wiki/PageRank#PageRank_uses_links_as_.22votes.22 PageRank] - "In essence, Google interprets a link from page A to page B as a vote, by page A, for page B." Issues with PageRank's "any link is a good link" model are a major impetus to standardizing on a format for link-intention.
* [http://yro.slashdot.org/yro/07/01/04/1544210.shtml Slashdot] - users can give comments a [http://slashdot.org/faq/com-mod.shtml#cm700 karma] score which affects what comments are seen (comments can be filtered based on the score)
* [http://del.icio.us del.icio.us], [http://ma.gnolia.com/ ma.gnolia], [http://technorati.com/ Technorati favorites] - bookmarking sites that more or less represent a "for" vote

=== Vote Links ===
There are a few implementations based on the [[vote-links|VoteLinks microformat]] combined with other technologies:
* [http://www.artweb-design.de/articles/2006/06/05/distributed-votings-using-microformats Distributed votings using microformats] from Artweb Design
* [http://24ways.org/2006/boost-your-hyperlink-power Boost Your Hyperlink Power] - Jeremy Keith, using CSS to surface vote information
* [http://redmonk.net/archives/2006/12/21/voteback/ VoteBack] - VoteLink discovery + pingback/trackback

=== Example: Vote Links ===
(from: [[vote-links|VoteLinks microformat]])
<pre><nowiki>
<a rev="vote-for" href="http://ragingcow.blogspot.com"
title="neat spoof">Raging Cow</a>
<a rev="vote-against" href="http://ragingcow.com"
title="nasty corn syrup drink">Raging Cow</a>
</nowiki></pre>

== Existing Practices ==
* Most example sites, including Digg, UrbanDictionary.com, and Slashdot all use plain text labels or images for marking up their voting features.

== See Also ==
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML SE]
* [[vote-links]]
* [http://dbpubs.stanford.edu:8090/pub/1999-66 Stanford paper describing an early version of PageRank]

press-ja

2007-05-28T13:17:36Z

RobertBachmann: Reverted edit of Iv2Lbl, changed back to last version by Tantek

__NOTOC__

<h1> Press </h1>

このページでは、[[microformats-ja|microformats]]が取り上げられたオンライン上の記事を紹介しています。他に[[screencasts]]、[[presentations-ja|プレゼンテーション]]、[[podcasts|ポッドキャスト]]、[[books-ja|書籍]]などのメディアでもmicroformatsが取り上げられています。

== 2006 ==

=== 8月 ===

* [http://digital-web.com/articles/the_big_picture_on_microformats/ The Big Picture on microformats] - who's doing what with microformats right now - by John Allsopp - Published August 28th, 2006.
* [http://www.thinkvitamin.com/features/design/how-to-use-microformats Add microformats magic to your site] by John Allsopp - Published August 25th, 2006.

=== 7月 ===
* [http://knowledge.wharton.upenn.edu/article.cfm?articleid=1526 Knowledge at Wharton: Tantek Çelik and Rohit Khare: The Progress and the Promise of Microformats] - 2006年7月20日に公開。

=== 6月 ===
* [http://devzone.zend.com/node/view/id/584 Microformats, PHP and hKit] PHP開発者の為の情報サイトdevzone.zend.comより。6月28日。
* [http://www.mercurytide.com/knowledge/white-papers/microformats Building a more semantic web with microformats] Mercurytideより。6月20日。

=== 5月 ===
* [http://www.devsource.com/article2/0,1895,1961106,00.asp DevSource: An Developer's Introduction to Microformats by Phil Haack, May 11.]
** 記事の著者Phil Haackによる[http://haacked.com/archive/2006/05/11/IntroductionToMicroformatsArticle.aspx 記事に関するblogポスト]も参照されたい。

=== 4月 ===
=== 3月 ===
* (need to backfill these - there were a bunch and I think we simply forgot to add them in)

=== 2月 ===
* [http://book.mycom.co.jp/wd/ Web Designing] [http://book.mycom.co.jp/wd/bn/200603.html 2006年3月号]にmicroformatsの紹介記事が載っています。
* [http://www.release1-0.com/freshproduce/newideas_socialtime.cfm Release 1.0 / Ideas / New Ideas that Matter: Time as a social object], February 16. Video interviews composite, including a bit on microformats.
* [http://2006.sxsw.com/interactive/web_awards/finalists/ SXSW 2006 Web Awards Finalists], February 3rd. [http://microformats.org microformats.org] is a finalist in the "Technical Achievement" category for "the sites that are re-inventing and re-defining the technical parameters of our online experience".

=== 1月 ===
* [http://code.google.com/webstats/index.html Google Web Authoring Statistics, January 20]
*# The home page of the study "[http://code.google.com/webstats/index.html Web Authoring Statistics]" itself both mentions “microformats.org” and links to http://microformats.org .
*# The "[http://code.google.com/webstats/2005-12/pageheaders.html Page Headers]” page notes that the [http://gmpg.org/xfn/ XFN] microformat is the most popular HTML metadata profile: “…people do use the profile attribute, though. The three most-often used values are http://gmpg.org/xfn/1, http://dublincore.org/documents/dcq-html/, and http://gmpg.org/xfn/11. This makes XFN the most popular HTML metadata profile!”
*# The “[http://code.google.com/webstats/2005-12/element-a.html a element]” page found that three of the most popular ‘rel’ attribute values were microformats: #1 [[rel-nofollow-ja|rel-nofollow]], #2 [[rel-license]], #5 [[rel-tag-ja|rel-tag]].
* [http://www.philoneist.com/50226711/interview_with_technorati_marketing_director_derek_gordon.php Philoneist: Interview With Technorati Marketing Director Derek Gordon by Jonathan G. Cohen, January 11]
* [http://www.kbcafe.com/iBLOGthere4iM/?guid=20060101232742 #2 on the list of Best Web 2.0 Blogs, January 2]

== 2005 ==

=== 12月 ===
* [http://www.publish.com/article2/0,1759,1904359,00.asp Publish: Year in Review: CSS, Standards, Microformats and Flash, By Stephen Bryant, December 21]
* [http://www.primezone.com/newsroom/news.html?d=91118 Newswire: Structured Blogging to support microformats, December 13th]
* [http://www.linuxjournal.com/article/8731 Linux Journal: Syndication and the Live Web Economy, By Doc Searls, December 9]

=== 11月 ===
* [http://acmqueue.com/modules.php?name=Content&pa=showpage&pid=349&page=4 ACM Queue: A Conversation with Ray Ozzie, ACM Queue vol. 3, no. 9 - November 2005]
* [http://www.digital-web.com/articles/microformats_primer/ Digital Web Magazine: Microformats Primer by Garrett Dimon, November 14, 2005]

=== 10月 ===
* [http://www.xml.com/pub/a/2005/10/19/microformats-and-web-2.0.html XML.com: Microformats and Web 2.0 by Micah Dubinko, October 19, 2005]

=== 9月 ===
* [http://channel9.msdn.com/Showpost.aspx?postid=118325 Channel 9: Interview at PDC] - Robert Scoble interviews Tantek Çelik briefly on web standards, IE, and microformats.

=== 7月 ===
* [http://www.acm.org/technews/articles/2005-7/0722f.html#item12 ACM News Service - Volume 7, Issue 819: Friday, July 22, 2005]
* [http://lists.ssc.com/pipermail/suitwatch/2005-July/000090.html Linux Journal: SuitWatch -- July 21 -- by Doc Searls, Senior Editor of Linux Journal: Making More Sense of the Web]
* [http://knowledge.wharton.upenn.edu/index.cfm?fa=viewArticle&id=1247&specialId=38 Knowledge at Wharton: Supernova 2005: It's a Whole New, Connected World: What's the Next Big Thing on the Web? It May Be a Small, Simple Thing -- Microformats]
** Simplified Chinese: <http://knowledge2.wharton.com.cn//index.cfm?fa=article&articleid=1203&specialid=58&languageid=4>
** Traditional Chinese: <http://knowledge2.wharton.com.cn//index.cfm?fa=article&articleid=1203&specialid=58&l=4&languageid=5>
** Original english version: <http://knowledge2.wharton.com.cn//index.cfm?fa=article&articleid=1203&specialid=58&languageid=1>

=== 6月 ===
* [http://news.com.com/2030-12-5745034.html#microformats CNET News.com: Supernova 2005 blogcast] - David Weinberger interviews Tantek Çelik and Rohit Khare about microformats and [http://microformats.org/ microformats.org].
** [http://blog.blogcast2005.silkclips.com/clipView?http://silkblogs.com/FindResource/EC139870-22E5-F208-70FA-BC437BD64420/celik-khave-full.mov Watch the full interview with Rohit Khare & Tantek Çelik (22:21 minutes)]
* Golem: [http://www.golem.de/0506/38831.html microformats.org - Formate für Menschen und Maschinen] (German: microformats.org - Formats for humans and machines)

=== 3月 ===
* [http://www.xml.com/pub/a/2005/03/23/deviant.html XML.com: What Are Microformats?]

podcasts

2007-05-28T13:16:32Z

RobertBachmann: Reverted edit of MyyOe4, changed back to last version by Adactio

<h1> microformats podcasts </h1>

This page lists various podcasts and audio (and/or video) recordings which have provided explanations and discussions of both [[microformats]] in general, and specific microformats. See also microformats [[press]], [[presentations]] and [[screencasts]]. Note: podcasts that simply mention microformats without going into more detail discussions of descriptions or uses are not inlcuded.

Please feel free to add links to additional podcasts that discuss microformats!

Most recent podcasts listed first.

== 2007 ==
* May 19th [http://adactio.com/journal/1294/ Microformats 1:01—Exporting microformats via bluetooth], a short video demo by Jeremy Keith. Time: 1:01min.
* March 23rd [http://www.podtech.net/home/technology/2477/microformats-guru-tantek-celik Microformats Guru Tantek Celik] interview on microformats, sxsw, vlogging. Time: 4:46min.
* January 29th [http://pod-serve.com/audiofile/filename/4668/Steve_Ganz.mp3 Edgework: Steve Ganz] 36 MB Steve Ganz, senior Web developer at LinkedIn, talks about how they republished 9 million public profiles using hResume. Time: ??:??
* January 17th [http://pod-serve.com/audiofile/filename/4499/Jeremy_Keith.mp3 Edgework: Jeremy Keith] 63 MB Jeremy Keith talks about Ajax and Microformats. Time ??:??
* January 17th [http://pod-serve.com/audiofile/filename/4331/Dan_Cederholm_Interview.mp3 Edgework: Dan Cederholm] 55 MB Dan Cederholm talks about Microformats in Corkd Time ??:??
* January 5th [http://www.webdirections.org/podcasts/WD06/microformats.mp3 John Allsopp: "Microformats"] podcast from [http://webdirections.org Web Directions South 2006-09-28]. Time ??:??.

== 2006 ==
* November 5th [http://www.flipclip.net/clips/siva001/692d23f566c59fa5059df18e4faf0a36 Fumi Yamazaki and Tantek Çelik on Microformats] (video [http://creativecommons.org/licenses/by-nc/2.1/jp/ CC-by-nc 2.1-jp]), in general, [[hcard|hCard]], Add to Address Book example and demonstration, [[hcalendar|hCalendar]], Subscribe to Calendar example and demonstration. Fumi speaks in Japanese, Tantek speaks in English, which is periodically translated into Japanese.
* October 11th [http://media.libsyn.com/media/carsonsystems/Tantek_Celik.mp3 Tantek: "Microformats Practices"] podcast from [[events/2006-09-13-future-of-web-apps-microformats|The Future of Web Apps 2006-09-13 session in San Francisco]]. Time ??:??.
* September 25th [http://www.vivabit.com/atmedia2006/blog/index.php/tantek-celik-microformats-evolving-the-web-podcast/ Tantek: "Microformats: Evolving the Web] podcast from [[events/2006-06-16-atmedia-microformats|@Media 2006 June 16th session]]. Time 1:00:12
* September 11th [http://www.boagworld.com/archives/2006/09/dconstruct_web_services.html Paul Boag talks to Jeremy Keith about microformats]. The interview starts at 8:10 and finishes at 15:42.
* September 5th [http://www.beet.tv/2006/09/technorati_is_t.html Beet.tv interviews Peter Hirshberg on video and microformats]
* August 8th [http://www.verkko2.com/2006/08/06/jakso-2-mikroformaatit/ Jakso 2: Mikroformaatit] (Finnish) ([http://www.zengestrom.com/blog/2006/08/verkko2_on_micr.html English]). Jyri Engeström interviewed Tantek Çelik and Ryan King about their work on microformats at Technorati and about microformats in general. There is a Finnish intro, but the interview is in English.
* June 30th [http://www.weblogswork.com/2006/06/30/weblogs-worknotes-hresume/ Weblogs Worknotes: hResume]. "Alexander & I gave Tantek & Ryan an update on the hResume stuff we’d been working on, and while we were there we recorded a discussion about hResume and the success of Microformats in general."
* June 26th [http://www.boagworld.com/archives/2006/06/podcast_40_atmedia_mainstream_application.html atMedia - Applying the lessons learnt] from Boagworld.com (30Mb MP3). Paul Boag introduces the concept of Microformats in the show's Technobuster section (starts 6:50), in response to Tantek's presentation at @media 2006. Aimed at a non-technical audience.
* June 22nd (recorded March 13th) [http://player.sxsw.com/2006/podcasts/SXSW06.INT.20060313.Microformats.mp3 Microformats: Evolving The Web (23.8MB, 51:58mins)] from South by SouthWest 2006. Tantek Çelik, Chris Messina, Jeremy Keith and Mark Norman Francis discuss microformats and demo tools and implementations. A transcript has been posted to [[events/2006-03-13-sxsw-microformats-transcript]].
* April 11th [http://www.dustindiaz.com/episode-10/ Microformats, Drew, and lots of beer] (starts 42nd minute) For a lack of a better title, in this episode Drew McLellan and I had the chance to discuss the evolving technology of microformats along with quite a few of his other sites like Dreamweaver Fever and 24ways. Other than that, we discussed some of the latest news going on around the web such as Dan’s DOM Builder and William’s Firefox extension guide, and of course played another classic game of Pryamid 2.0 where I failed miserably (again).
* April 5th: [http://pod-serve.com/audiofile/filename/949/Messina_on_Microformats.mp3 Weblogs Worknotes with Chris Messina (12 MB .mp3 ~ 20 min.] In the first of our series of casts on microformats, we talk with Chris Messina.
* April 5th: [http://www.web20show.com/articles/2006/04/04/web-2-0-show-episode-15-tantek-celik-ryan-king web2.0 show] In this SXSW interview, we snag Tantek Celik and Ryan King from Technorati and Microformats to talk about stuff they are working on… (need date of recording, not release date)
* March 31: [http://blogs.msdn.com/alexbarn/archive/2006/03/31/566361.aspx Microformats Podcast] ([http://alexbarnett.audioblog.com/deluge/c6d4ccaa-b6e5-9604-a721-764467d8bc66.mp3 51 mins, .mp3, 12mb, CC-by-2.5]) with Alex Barnett, Tantek Çelik, Dan Connolly, and Rohit Khare.
* March 23: [http://www.technewsradio.com/2006/03/tech_news_radio_9.html Tech News Radio #273 | 060323| eTech 2006, Phil Windley, Digital Identity, Attention Economy, AOL, OpenAPI, Microformats] ([http://www.geekon.com/tnr/2006/03Mar/TNR_273_060323_Tech_News_Radio.mp3 6:55 mins, .mp3, 3.2mb, CC-by-sa-2.5])
** Topics: Attention, Ray Ozzie's Cut and Paste for the Web, microformats, AOL
** Phil Windley: <blockquote>In the last couple of years, microformats have kind of gone from this interesting idea, that people thought, 'ah yeah, that might be cool if you get can get anybody to do it', to dozens of companies that were here [at ETech] that had microformats built into their systems and were using them actively.</blockquote>
* March 19: [http://www.talkcrunch.com/2006/03/19/episode-2-social-networks-30/ TalkCrunch » Blog Archive » Episode 2: Social Networks 3.0] ([http://podcast.techcrunch.com/Techcrunch-Ep002-SocialNetworks.mp3 43:40min, .mp3, 10.2MB]) with Michael Arrington, Nik Cubrilovic, Reid Hoffman, and David Hornik.
** Topics: Social networks, microformats, version numbers
** Starting at 17:55 minutes in, Mike Arrington asks Nik: ''"How do you define a Web 2.0 or Social Network 3.0?"''
** Nik: <blockquote>I think what's interesting is what Reid mentioned earlier with LinkedIn now making pages available to the public, probably a big step that we should talk about more, and I think this is what Social Networking 3.0 is all about, is having hopefully supporting [[microformats]] as well, which I wanted to ask Reid about but we'll leave 'til later, such as [[hcard|hCard]] and [http://gmpg.org/xfn XFN]. What I think Social Networking 3.0 is about is about not having a single destination social network, it's about publishing your profile on the Web, and having all these extra services that come around and scoop all this information up and make it available to anybody else. Because if you think about the way that social networks work in real life, is you don't have one big destination that everyone sort of groups around, smaller social networks, 10, 15, 20 people. So if LinkedIn makes these pages public, what that means is that I can set up a social network, and I can say that these 3 people from Linkedin and these 8 people who have blogs are all part of this social network. Social Networking 3.0 for me is about <em>decentralization</em> of social networks, it's about the support of these [[microformats]], and scooping all this information together using other services.</blockquote>
* February 16th (recorded on February 7th): [http://www.release1-0.com/freshproduce/newideas_socialtime.cfm Discussing events online] includes a little segment by Tantek talking about microformats and [[hcalendar|hCalendar]] in particular at 4 minutes 39 seconds. Video.

== 2005 ==
* September 30th [http://odeo.com/audio/270407/view Microformats: Evolving the Web (Incomplete)]

== Search ==
* German [http://www.podcast.de podcasts] on [http://www.podcast.de/suche/nach/mikroformat*/in/ShowSearch micro formats]

buttons

2007-03-28T13:14:01Z

RobertBachmann: /* Licensing */ cc-by 3.0 license for my buttons

<h1>Microformats Buttons</h1>

There have been requests for buttons for various microformats. Either badges, or buttons that do something with the specific microformats. This page keeps a list of buttons, and requests as well. - [http://tantek.com/log/ Tantek]

Added hosted buttons for all the microformats, including the draft ones, as well as instructions on how to make your own buttons. (14 May 2006) - [http://www.wackomenace.co.uk/ Ruben]

==Licensing==

If you add links to buttons you have designed, '''please also include a statement''' that you do one of the following:
*release them into the public domain
*hold copyright, but release all rights as to it use
*license them under a specified free license, e.g. consider using a [http://creativecommons.org/ Creative Commons] license, such as [http://creativecommons.org/licenses/by/3.0 cc-by-3.0].

Thank you.

* Images below hosted at boogdesign.com are available under [http://creativecommons.org/licenses/by/2.0/ CC Attribution 2.0 License], see [http://www.boogdesign.com/buttons.html my buttons page] for the Photoshop files if you need them. - Rob Crowther

* Images below hosted at rbach.priv.at are available under [http://creativecommons.org/licenses/by/3.0 cc-by-3.0 license]. - [[User:RobertBachmann|Robert Bachmann]]

__TOC__

== Buttons ==

=== Microformat Banner ===
I've made a banner for microformats. Since there are so many microformats and with more to come, just indicating support/ use of might be a good generic approach. The image is free to use. Please copy it to your own hosting account and not link to it.

http://www.crowley.nl/images/microformats.png

I already have a "I use
http://www.crowley.nl/images/microformats.png" on my blog: http://doncrowley.blogspot.com/

- Don Crowley

* http://www.boogdesign.com/images/buttons/microformat.png
* http://www.boogdesign.com/images/buttons/microformat_enabled.png
* http://www.boogdesign.com/images/buttons/emf_green.png
* http://www.boogdesign.com/images/buttons/mfe_green.png
* http://www.boogdesign.com/images/buttons/mwmf_green.png
* http://www.boogdesign.com/images/buttons/smf_green.png
* http://www.boogdesign.com/images/buttons/emf_white.png
* http://www.boogdesign.com/images/buttons/mfe_white.png
* http://www.boogdesign.com/images/buttons/mwmf_white.png
* http://www.boogdesign.com/images/buttons/smf_white.png

=== [[hcalendar|hCalendar]] ===
* http://rbach.priv.at/2006/buttons/hcal.png
* http://www.boogdesign.com/images/buttons/microformat_hcalendar.png
* CSS-powered button from [http://www.midgard-project.org/community/events/ Midgard CMS - Event calendar]:

<span class="badge" style="float: left; font: 9px Geneva, Verdana, sans-serif; padding: 0 1em 1px 0; border: 1px solid #000; background: #D1940C; color: #fff; text-decoration: none; text-align: center;"><span style="background: #000; border-right: 1px solid #000; color: #fff; padding: 1px 0.75em; margin-right: 0.1em;">›››</span> hCalendar</span>

Code (white space added for readability):

<pre><nowiki>
<span class="badge"
style="float: left; font: 9px Geneva, Verdana, sans-serif; padding: 0 1em 1px 0;
border: 1px solid #000; background: #D1940C; color: #fff; text-decoration: none;
text-align: center;">
<span style="background: #000; border-right: 1px solid #000; color: #fff; padding: 1px 0.75em;
margin-right: 0.1em;">
&#8250;&#8250;&#8250;
</span>
hCalendar
</span>
</nowiki></pre>

=== [[hcard|hCard]] ===
* http://www.crowley.nl/images/hcard.png (mirror: http://www.davidjanes.com/images/mf_hcard.png)
* http://rbach.priv.at/2006/buttons/hcard.png
* http://www.boogdesign.com/images/buttons/microformat_hcard.png
* CSS-powered button, as evidenced at [http://re-run.com/about/microformat-badges microformat badges @ re-run]

=== [[rel-license]] ===
* http://rbach.priv.at/2006/buttons/license.png
* http://www.boogdesign.com/images/buttons/microformat_rellicense.png

=== [[rel-nofollow]] ===
* http://rbach.priv.at/2006/buttons/nofollow.png
* http://www.boogdesign.com/images/buttons/microformat_relnofollow.png

=== [[rel-tag]] ===
* http://rbach.priv.at/2006/buttons/rel-tag.png
* http://rbach.priv.at/2006/buttons/tag.png
* http://www.boogdesign.com/images/buttons/microformat_reltag.png

=== [[vote-links|VoteLinks]] ===
* http://rbach.priv.at/2006/buttons/votelinks.png
* http://www.boogdesign.com/images/buttons/microformat_votelinks.png

=== [http://gmpg.org/xfn/ XFN] ===
* http://rbach.priv.at/2006/buttons/xfn.png
* http://www.boogdesign.com/images/buttons/microformat_xfn.png

=== [http://gmpg.org/xmdp/ XMDP] ===
* http://rbach.priv.at/2006/buttons/xmdp.png
* http://www.boogdesign.com/images/buttons/microformat_xmdp.png

=== [[xoxo|XOXO]] ===
* http://rbach.priv.at/2006/buttons/xoxo.png
* http://www.boogdesign.com/images/buttons/microformat_xoxo.png

== Buttons for draft formats ==

These may be subject to change if the names of the formats change when they are released.

=== [[adr]] ===
* http://rbach.priv.at/2006/buttons/adr.png

=== [[geo]] ===
* http://rbach.priv.at/2006/buttons/geo.png

=== [[hatom|hAtom]] ===
* http://rbach.priv.at/2006/buttons/hatom.png
* http://files.synaesthetic.net/common/images/buttons/hatom.png

=== [[hresume|hResume]] ===
* http://rbach.priv.at/2006/buttons/hresume.png
* http://www.boogdesign.com/images/buttons/microformat_hresume.png

=== [[hreview|hReview]] ===
* http://rbach.priv.at/2006/buttons/hreview.png

=== [[rel-directory]] ===
* http://rbach.priv.at/2006/buttons/directory.png

=== [[rel-enclosure]] ===
* http://rbach.priv.at/2006/buttons/enclosure.png

=== [[rel-home]] ===
* http://rbach.priv.at/2006/buttons/rel-home.png
* http://rbach.priv.at/2006/buttons/home.png

=== [[relpayment-research|rel-payment]] ===
* http://rbach.priv.at/2006/buttons/payment.png

=== [[robots-exclusion|Robots Exclusion]] ===
* http://rbach.priv.at/2006/buttons/robots.png

=== [[xfolk|xFolk]] ===
* http://rbach.priv.at/2006/buttons/xfolk.png

== Make your own buttons ==
=== Style 1 ===

Example: http://www.crowley.nl/images/hcard.png

Use the [http://kalsey.com/tools/buttonmaker/ Kalsey Button Maker] with the following settings:
* Outer border: #666666
* Inner border: #ffffff
* Bar position: 25 pixels from the left
* Left box text: >>>
* Left box background: #000000
* Left box text colour: #ffffff
* Left box text start: 7 pixels from the left
* Right box text: (The name of the microformat goes here)
* Right box background: #31757b
* Right box text colour: #ffffff
* Right box text start: 3 pixels from the bar

=== Style 2 ===

Example: http://rbach.priv.at/2006/buttons/hcal.png

# Get the font [http://www.kottke.org/plus/type/silkscreen/ Silkscreen]
# Install [http://www.imagemagick.org/ ImageMagick]
# Get the blank icon (http://rbach.priv.at/2006/buttons/blank.png)
# Type:
<pre>convert blank.png
-fill white
-font Silkscreen
-pointsize 8
+antialias
-draw "text 28,10 'button label'"
output.png
</pre>

=== Style 3 ===

Example: http://files.synaesthetic.net/common/images/buttons/hatom.png

# Get the font [http://www.kottke.org/plus/type/silkscreen/ Silkscreen]
# Install [http://www.imagemagick.org/ ImageMagick]
# Get the blank icon (http://files.synaesthetic.net/public/microformats/button2-blank.png)
# Type:
<pre>convert button2-blank.png
-fill white
-font Silkscreen
-pointsize 8
+antialias
-draw "text 20,10 'button label'"
output.png
</pre>

= Microformats Logos =
Rohit is a very poor CSS hacker, but gave it his best shot. He also [http://labs.commerce.net/~rohit/µf-logo.html rendered it at 72 and 18 points.]

http://microformats.org/img/logo.gif

<div style="position: relative; top:-46px; left:180px">
<div style="background-color:#679A06; width:30px; height: 30px; left:1px; top:10px; position:absolute; -moz-border-radius:5pt;"></div>

<div style="background-color:#85BC07; width:22px; height: 22px; left:11.5px; top:6px; position:absolute; border-left: 2px solid white;border-bottom: 2px solid white; -moz-border-radius:4pt;"></div>

<div style="background-color:#AEE219; width:14px; height: 14px; left:22.5px; top:4px; position:absolute; border-left: 2px solid white;border-bottom: 2px solid white;-moz-border-radius:2pt;"></div>

<div style="font-family:Arial Narrow,Arial,sans-serif;font-size:17.5pt;letter-spacing:0px;color:#676767; position: absolute; left:44px; top: -6px">
<span style="padding-left:9;color:#111111;vertical-align:40%">micro</span><span style="vertical-align:40%;padding-left:1pt">formats</span>
</div>
</div>

The above logo as a transparent PNG (linked here from my own server; if you use it, please copy it for yourself):

http://files.synaesthetic.net/public/microformats/microformats1.png

=Wiki buttons=
For use on this wiki.
*{{NewMarker}} - <nowiki>{{NewMarker}}</nowiki>
*{{SuccessMarker}} - <nowiki>{{SuccessMarker}}</nowiki>
*{{UpdateMarker}} - <nowiki>{{UpdateMarker}}</nowiki>

= Requests =

* Logos for all microformats

* When someone has time, these should be repeated on the page for each respective format.

to-do

2007-01-11T21:49:27Z

RobertBachmann: /* Robert Bachmann */ been there, done that ;-)

<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.
* Create a microformat (based on hCalendar?) for marking up the opening hours of stores and restaurants. Some people seem to believe hCalenders repeating event support isn't good enough for this and needs to be amended first.

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

=== Adding Microformats to Existing Pages ===

* See [[advocacy#Adding_Microformats_to_Existing_Sites|advocacy: Adding microformats to existing sites]].

===Geotagging on Wikipedia===
Somebody familiar with the "geo" microformat might want to add details, and a link to the relevant page on this Wiki, to the [http://en.wikipedia.org/wiki/Geotagging Wikipedia page on Geotagging]. [[User:AndyMabbett|Andy Mabbett]]

===rel-tagging on Wikipedia===
Somebody familiar with the "rel-tag" microformat might want to add details, and a link to the relevant page on this Wiki, to the [http://en.wikipedia.org/wiki/Tag_%28metadata%29 Wikipedia page on tagging]. [[User:AndyMabbett|Andy Mabbett]] 14:07, 3 Jan 2007 (PST)

== Tantek ==

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

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

=== protect the community ===
* Analyze [[Special:Recentchanges]] and [http://microformats.org/discuss mailing-lists] and:
** add to [[mailing-lists]] policies/guidelines accordingly.
** privately email violaters kindly asking them to improve their behavior
** work with admins on next steps for individuals negatively impacting the community
** recognize noisy/distracting threads on the email list, document responses/answers to such subjects on the appropriate page(s) on the wiki, and reply to those threads with the URLs to the documentation on the wiki. Putting the responses/answers on the wiki helps by hopefully providing preemptive answers to some who might reraise the subjects on the list in the future, and helps the community quickly terminate such threads by using the answers on the wiki.

=== help publishers ===
* (: [[advocacy]] - add pages/sites that could use microformats, update them with sample markup, find contacts for those pages to get them updated, and send requests to update their sites with microformats including sample markup.

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

* *-authoring for all microformats: [[hcalendar-authoring]], [[hreview-authoring]], [[xfolk-authoring]], [[hatom-authoring]]

==== 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 implementers ===
* 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. (Done. Feedback wanted. [http://dmitry.baranovskiy.com/work/csc/ Conference Schedule Creator])

=== wiki cleanup ===
==== 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]] -
*** [[hcard-examples-in-the-wild]] group/sort by individuals, organizations, and hosting sites. Consider moving largest subsection to its own page as well.
** [[rel-tag]]
** [[xoxo]]

==== update specification section organization ====
In particular, the introduction/boilerplate/headers. [[hresume|hResume]] has an experimental abbreviated intro/headers section, and links to more details further below, based on some ideas that Ryan King and I had for improving the readability of the microformats specifications. [[hreview|hReview]] has some similar improvements, but different. We need to:
# Figure out if the new intro/headers structure in [[hresume|hResume]] and/or [[hreview|hReview]] is an improvement, and if it could be better. Perhaps figure out the requirements for an intro/header section
#* Shorter tends to be better
#* Must be comprehensive enough to "print and read"
#* Must detail authorship/editorship
#* Must detail copyright/patent statements
# Write up a template - make it self-documenting per the requirements
# Update existing specifications with the new intro/headers structure.
## [[hcard|hCard]]
## [[hcalendar|hCalendar]]
## [[hreview|hReview]]

==== reorganizing Implementations sections ====
* sort implementations by authoring/creating/publishing, browsing/viewing, converting/importing, indexing/searching.

Hmmm... I like: '''A'''uthoring, '''B'''rowsing, '''C'''onverting, '''I'''ndexing, '''L'''ibraries (for developers), and '''P'''otential (for open source projects we want to add support to). Anybody have alternative suggestions for this vocabulary? I don't have a particularly strong preference so I'm going to go with these four until I find examples that don't fit, or someone suggests something better.

See: [http://microformats.org/wiki/hcalendar#Implementations hCalendar Implementations] for a first attempt at this. Assuming folks like that, we can go ahead with categorizing the implementations sections of other microformats specifications.

* [[hcard-implementations]] - organize by same subsections as [[hcalendar-implementations]].

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

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

=== iterate on current microformats ===
==== [[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. Also indicate complexity of information supplied, eg. just name+number vs. complete details
*** 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

==== [[hcalendar|hCalendar]] ====
* re-add a list of properties per the [[hcard#Property_List|hCard property list]].
* formalize [http://microformats.org/wiki/hcalendar- brainstorming#Tabular_event_calendars]
* flesh out [[hcalendar-examples]] and do a once over on markup/presentation of what RFC2445 examples would look like
* need spec details and then [[hcalendar-examples]] of multi-instance [[hcalendar|hCalendar]] events
* need spec details and then [[hcalendar-examples]] of repeating events
* add explicit explanation and examples for LOCATION [[hcard|hCards]] and ATTENDEE [[hcard|hCards]], perhaps on a separate [[hcalendar-examples]] page.
* need to resolve all outstanding [[hcalendar-issues]] to-do items.
* create [[hcalendar-profile]] and have folks verify it. note that it will likely need reconciliation with the [[hcard-profile]], especially since [[hcalendar|hCalendar]] normatively depends on [[hcard|hCard]]. Probably makes sense to have a combined profile which hCalendar would use.

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

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

==== parsing ====
* *-parsing for all microformats: [[hcalendar-parsing]], [[hreview-parsing]], [[xfolk-parsing]], [[hatom-parsing]]

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

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

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

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

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

=== emerging microformats ===
* [[citation]]
* [[hlisting|hListing]]
* [[media-info]]
* [[licensing]]

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

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

==Ryan==
=== wiki cleanup ===
* possibly move dead proposals off of homepage?

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

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

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

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

== Dimitri Glazkov ==

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

== Chris Messina ==

=== General ===

* Work on a microformat for play-lists (is it just a XOXO ordererd list of play-items?)
* Work on a microformat for play-item (take a look at [[media-info-examples]])
* Work on microformats tutorial for designers
* Add support for OpenID to micformats wiki

=== Campaigns ===

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

=== Wishlist ===

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

== Robert Bachmann ==

=== 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
* hAtom2Atom written using XSL 2.0?
** Do you think this would be useful? I have created a barebones version, doesn't yet take in all the parsing rules yet, but I'd be happy to share. Moving to XSL 2.0 does make things a bit cleaner and more efficient. - Matt Dertinger.
</li>
<li>Support for other output formats: (hAtom2<i>xyz</i>.xsl)
* RSS 2.0 (meanwhile use hAtom2Atom.xsl and [http://atom.geekhood.net/ atom2rss.xsl]) -- <i>+1 Matt Dertinger</i>
* RSS 1.0 (meanwhile use hAtom2Atom.xsl and [http://cvs.4suite.org/viewcvs/uogbuji/atom2rss.xslt atom2rss.xslt]) -- <i>+1 Matt Dertinger</i>
* AtomOWL (meanwhile use hAtom2Atom.xsl and [http://dannyayers.com/2005/11/22/atomowl-xslt-progress/ atom2rdfxml.xsl])-- <i>+1 Matt Dertinger</i>
* JSON?
** Does it make sense to consider a canonical representation of microformats (either case by case, or in general) in JSON? E.g. so that a JSON API that returned contact information could return an hCard-equivalent chunk of JSON. - Tantek.
</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 red links on [[Main_Page-fr]]
* localize a [http://www.elanceur.org/microformats/index.html french version] of the official website
** ask authorization to the authors
** migration could be done on any collaborative CMS
** test a cocomment system (based on local-wiki)
** complete with original links
* find experts for peer-reviewing
* update [http://fr.wikipedia.org/wiki/Microformats French-wikipedia:Microformats] via cowriting [http://fr.wikipedia.org/wiki/Discuter:Microformats on discussion page] (directly originated from the english article) + french examples to be found + local resources.

== Frances Berriman ==

[[User:Phae|Frances Berriman]]

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

== Ben West (bewest) ==

[[User:BenWest|bewest]]
* fight spam
* help tend wiki

=== Vocabulary ===
A lot of knowledge work is about maintaining sets of vocabulary. Now that the vocabulary is emerging, it may be time start making sure everyone is "on the same page," especially since some of the language is highly symbolic.
Terms:
* "boil the ocean" A huge task. "A phrase used in the industry to describe an attempt at something that is way too ambitious. For example, "They're trying to get their site launched by COMDEX. They could easier boil the ocean." from <http://www.netlingo.com/right.cfm?term=boil%20the%20ocean>
* microformats: more than one microformat
* microformat: see my definition on http://microformats.org/wiki/what-are-microformats#BenWest
* data fidelity: the extent to which a data format might be considered lossy. eg HTML is often seen as a lossy format because the information parsed out of a resource may not fully match the information orginally encoded. Non-lossy formats have a very high data fidelity, while lossy formats have low data fidelity. Microformats seek to increase data fidelity of html.
* market: the locus of economic forces

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

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

=== Information Architecture ===
'''Help Welcomed! Please leave your name'''
Add complaints to [[wiki-feedback]]!
Helping to make the wiki easier to use. I'd like to see the main page more towards a format like http://simile.mit.edu/solvent/ with the big questions right out front:
* What Is This?
* What can I do here?
* Is there a demo?
* Where can I learn more?
I'd like to change the front page to this kind of design.
==== Support Pages ====
There are several categories of things in the wiki. Can we enumerate them?
* About the Community
** Where to find information.
** Who are the stake holders?
** FAQs
* Web/Architectural Philosophy
** Community Principles
** Why are we doing this?
** XML and Namespaces
** Semantic XHTML
** Common Misconceptions
** Concession and Disposition of Criticism
** FAQs
* Specs
** Examples
** Discussion
** Exploration
** Use Cases
** Implementations
** The spec itself.

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

Can others agree and or refine this list? Should I take it to the -discuss list? How do we create consensus on how the wiki should be organized in order to make it more usable? And how can we turn that consensus into actionable changes?

The wiki should also capture wisdom that stems from discussions that don't produce microformats. For example, Chris Messina suggests a "Best Of" page suitable for capturing this kind of wisdom. I think we can think of a given microformat as being at a place in a spectrum that ranges from "not yet thought of", to "interesting but needs work," or even "rejected", and of course including all the stages familiar to the microformats processes (eg examples, brainstorming, etc...).
If there were such a page would it:
* Belong to a microformat? (eg hcard-bestof)
* or to the global namespace? (eg /wiki/wisdom/foobar-format)
(I think Chris Messina suggests that it belongs to a given microformat, but then how do we collect wisdom from non-microformats?)

Considering that the wiki page named with the microformat (i.e. /wiki/hcard) is the one that people will mostly likely look to first for learning about a particular format, I'd think it'd make more sense and create a more welcoming feel to convert these pages to an intro page introducing the format for the beginner and linking to resources like tutorials and creators. Spec pages would then be relocated to wiki/*-spec -- [[User:Cgriego|Cgriego]] 13:25, 16 Oct 2006 (PDT)

====Mike Schinkel's Comments====

My suggestion on the list was for us to use a convention that the entry page (i.e.
http://microformats.org/wiki/hcard) would be an index into a list of
(psuedo) standardized sub pages so that it would be very people to
find what is important to them. For example, is a list of potential sub pages:

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

These pages would be located respectively at

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

Please note I am suggesting an architecture not a specific list of sub pages. The list of sub pages should be defined by both reviewing existing information during site reorganization, and then via discussion on the list in an attempt to discover and extract which sub pages are needed for most/all microformats.

'''NOTE''': This differs from above in that the spec if not viewed as a top level structure but instead the microformat itself and the spec would be under the microformat. In this context "microformat" is a more abstract concept and "spec" is a more concrete thing. Another way to think about it would be that each microformat would have it's own mini home page and then things like "spec" are the pages listed on its home page.

== Matt Dertinger (Thewhoo) ==

[[User:Thewhoo]]

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

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

== Henri Bergius ==

[[User:HenriBergius|Henri Bergius]]

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

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

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

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

== New Person 1 ==

etc.

Main Page

2007-01-08T01:00:20Z

RobertBachmann: Reverted edit of Zaza, changed back to last version by NTollervey

__NOTOC__
<h1>Microformats Wiki</h1>

'''Hello!''' Welcome to the microformats wiki. If this is your first visit, please see the [[introduction]] page.

Please read [[how-to-play]] before making any edits.

Please read [[process]] before proposing any new microformats.

__TOC__

==Getting Started==

[[what-are-microformats|What are microformats]]? [[what-can-you-do-with-microformats|What can you do with them]]?

The [http://microformats.org/about/ about page], [http://microformats.org/ latest news], plus recent [[press]], [[presentations]], [[podcasts]], and [[screencasts]] are also good places for some background information. Our [[cheatsheets]] are handy if you need a quick reminder about a particular microformat.

Frequently asked questions about the wiki and microformats in general are answered in the [[faq|FAQ]], and there is a [[glossary]].

Want to learn more in person? Check out [[events|microformats events]].

==Definition==

One popular definition from our [http://microformats.org/discuss/ mailing list] (see also: [[mailing-lists]]) is "simple conventions for embedding semantics in HTML to enable decentralized development." More precisely, microformats can be defined as:
:simple conventions
:for embedding semantic markup
::for a specific problem domain
:in human-readable (X)HTML/XML documents, Atom/RSS feeds, and "plain" XML
::that normalize existing content usage patterns
::using brief, descriptive class names
::often based on existing interoperable standards
:to enable decentralized development
::of resources, tools, and services

Simply put: "Microformats are a codification of convention." -- [http://easy-reader.net Aaron Gustafson]

"Or do you just use your browser to browse? That's so 20th century." -- [http://diveintomark.org Mark Pilgrim]

== How to contribute ==

Do you want to help take microformats to the next level? You can:

*Check out our open [[to-do|to do list]] for things to help get done.
*Join the [http://microformats.org/discuss mailing lists] and [[irc|IRC Channel]] to learn and help answer questions about microformats.
*[[advocacy|Advocate]] the use of microformats.
*help to [[Main_Page#microformats_wiki_in_other_languages|translate the microformats wiki into other languages]] to make microformats globally accessible.

== Specifications ==
[[microformats|Microformats]] open standards specifications (see also: [[implementations]])
* [[hcalendar|hCalendar]] - [http://microformats.org/code/hcalendar/creator hcalendar creator]
* [[hcard|hCard]] - [http://microformats.org/code/hcard/creator hcard creator]
* [[rel-license]]
* [[rel-nofollow]]
* [[rel-tag]]
* [[vote-links|VoteLinks]]
* [http://gmpg.org/xfn/ XFN] (see also: [[xfn-implementations]])
* [http://gmpg.org/xmdp/ XMDP]
* [[xoxo|XOXO]]

== Drafts ==
* [[adr|adr]]
* [[geo|geo]]
* [[hatom|hAtom]]
* [[hresume|hResume]]
* [[hreview|hReview]] - [http://microformats.org/code/hreview/creator hreview creator]
* [[rel-directory]]
* [[rel-enclosure]]
* [[rel-home]]
* [[relpayment-research | rel-payment]]
* [[robots-exclusion|Robots Exclusion]]
* [[xfolk|xFolk]]

== Design Patterns ==

{{design_patterns}} 

== Exploratory Discussions ==
Research and analysis of real-world [[examples]], existing formats, and brainstorming to motivate the microformat. Please check [[rejected-formats]] before making additions.

*alternates [[alternates-brainstorming|alternates brainstorming]], [[alternates-examples|alternates examples]]
*[[attention]]
* blog description [[blog-description-examples|blog description examples]]
* blog info [[blog-info-examples|blog info examples]]
* blog post [[blog-post-examples|examples]], [[blog-post-formats|blog post formats]], and [[blog-post-brainstorming|blog post brainstorming]] (yielded the [[hatom|hAtom]] draft)
* book [[book-examples|book examples]], [[book-formats|book formats]], and [[book-brainstorming|book brainstorming]]
* chat [[chat-examples|chat examples]], [[chat-formats|chat formats]], and [[chat-brainstorming|chat brainstorming]]
* citation [[citation|citation effort]], [[citation-examples|citation examples]], [[citation-formats|citation formats]], [[citation-brainstorming|citation brainstorming]], and [[citation-faq|citation FAQ]]
* comment [[comment-problem|comment problem]], [[comment-examples|comment examples]], and [[comments-formats|comment formats]] (Some stuff needs to be extracted from [[comments-formats]])
* [[collection-description|collection description]] {{NewMarker}}
* [[course-catalog]]; [[course-catalog-examples]] {{NewMarker}}
* [[currency]]; [[currency-examples]]; [[currency-brainstorming]]; [[currency-proposal]]; [[currency-issues]]
* directions [[directions-examples|directions examples]] {{NewMarker}}
* directory inclusion [[directory-inclusion-examples|directory inclusion examples]], [[directory-inclusion-formats|directory inclusion formats]]. (see also [[rel-directory]])
* distributed conversation [[distributed-conversation|distributed conversation overview]], [[distributed-conversation-brainstorming|distributed conversation brainstorming]], [[distributed-conversation-examples|distributed conversation examples]], and [[distributed-conversation-formats|distributed conversation formats]]
* forms [[forms-examples|forms examples]]
* genealogy [[genealogy-formats|genealogy examples]]
* group [[group-brainstorming|group brainstorming]] and [[group-examples|group examples]]
* items [[items-brainstorming|items brainstorming]] and [[items-examples|items examples]
* hash [[hash-examples|hash examples]]
* job listing [[job-listing-examples|job listing examples]] and [[job-listing-brainstorming|job listing brainstorming]]
* last modified [[last-modified-examples|last modified examples]], [[last-modified-formats|last modified formats]], and [[last-modified-brainstorming|last modified brainstorming]]
* hListing [[hlisting-proposal|hListing proposal]], and [[hlisting-feedback|hListing feedback]]
** Also, listing [[listing-examples|examples]], [[listing-formats|formats]], and [[listing-brainstorming|brainstorming]]
* [[product|hProduct]] - [[product-brainstorming|hProduct brainstorming]] | [[product-examples|hProduct examples]]
* location [[location-formats|location formats]]. (see also [[adr]] and [[geo]])
* [[luna]] ([[geo]]-like co-ordinates, for places on The Moon) - see also [[geo-extension-strawman]] a possible implementation {{UpdateMarker}}
* [[mars]] ([[geo]]-like co-ordinates, for places on the planet Mars) - see also [[geo-extension-strawman]] a possible implementation {{UpdateMarker}}
* measures and measurement units [[measure]]
* [[media-info]] ([[media-info-examples|media-info examples]], [[media-info-formats|media-info formats]], [[media-info-brainstorming|media-info brainstorming]])
* meeting minutes [[meeting-minutes-examples|meeting minutes examples]], [[meeting-minutes-formats|meeting minutes formats]], and [[meeting-minutes-brainstorming|meeting minutes brainstorming]]
* metalink [[metalink-examples|metalink examples]] {{NewMarker}}
* microsummary [[microsummary-brainstorming|microsummary brainstorming]]
* [[mfo-examples|MFO examples]]
* music [[music-examples|music examples]]
* photo note [[photo-note-examples|photo note examples]]
*[[question-answer]], [[question-answer-brainstorming]]; [[question-answer-examples]] {{NewMarker}}
* recipe [[recipe-examples|recipe examples]], [[recipe-brainstorming]] {{UpdateMarker}}
* rel-product [[rel-product-brainstorming|rel-product brainstorming]]
* requirements testing [[requirements-testing|requirements testing overview]], and [[requirements-testing-examples|requirements testing examples]]
* [[rest-examples|REST examples]]
* resume [[resume-brainstorming|resume brainstorming]], and [[resume-formats|resume formats]]
* review [[review-examples|review examples]], and [[review-formats|review formats]] (yielded the [[hreview|hReview]] draft)
* search results [[search-results-example|search results example]]
* show [[show-brainstorming|show brainstorming]]
* showroll [[showroll-brainstorming|brainstorming]]
* [[species]] - for the marking up of the scientific names of living things: [[species-examples]]; [[species-brainstorming]] {{UpdateMarker}}
* table [[table-examples|examples]]
* tagspeak [[tagspeak-examples|tagspeak examples]]
* tagcloud [[tagcloud-examples|tagcloud examples]], and [[tagcloud-brainstorming|tagcloud brainstorming]].
* transit table [[transit-table-examples|transit table examples]]
* [[uid]]
* widget [[widget-examples|widget examples]], and [[widget-brainstorming|widget brainstorming]]
* [[wiki-formats|wiki formats]]
* work of art [[work-of-art|work of art overview]], [[workofart-examples|work of art examples]], [[workofart-formats|work of art formats]], and [[workofart-brainstorming|work of art brainstorming]]
*[[xmdp-brainstorming|XMDP brainstorming]] (see also [[xmdp-faq]])

== Examples ==
* [[examples]]
* [[zen-garden]]

== Tools, Test Cases and Additional Research ==

The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting tools and services that need to process more than one microformat. This section is intended for editors, parsers, validators, test cases, and other information relevant across multiple microformats.

*[[accessibility]]
*[[faqs-for-rdf]]
*[[icalendar-implementations]]
*[[parsing-microformats]]
*[[selected-test-cases-from-the-web]]
*[http://hg.microformats.org/ Source code repository] -- [[mercurial-quick-start|HowTo: Download code from the repository]]
*[[vcard-implementations]], [[vcard-errata]], [[vcard-suggestions]]
*[[why-are-content-standards-hard]]

== shared work areas ==
* [[buttons]]
* [[spread-microformats]] {{NewMarker}}
* [[demo]] - a page with links for quickly demonstrating microformats working in practice.
* [[events]]
* [[to-do]]
* [[user-interface]]
* [[marked-for-deletion]]
* [[microformats-issues]] {{NewMarker}} - issues related to more than one microformat.

== microformats wiki in other languages ==

You may read and edit microformats articles in many other languages:

* languages with over 50 articles
** [[Main_Page-fr|Français (French)]] {{UpdateMarker-fr}}
* languages with over 10 articles
** [[Main_Page-pt-br| Português (Brazilian Portuguese)]] {{NewMarker-pt-br}}
** [[Main_Page-ja|日本語 (Japanese)]]
* languages with over 2 articles
** [[Main_Page-es|Español (Spanish)]]
** [[Main_Page-de|Deutsch (German)]]

==== microformats translations elsewhere ====
These are off-site pages/sites with translations about microformats. If you are working on one of these, please consider translating the main microformats website!
* [http://mikroformate.pbwiki.com/ Deutsch (German) mikroformate.pbwiki.com] {{NewMarker-de}}

=== Start a microformats wiki in another language ===

Don't see the language you want? Help translate the microformats wiki into another language!

We're still figuring this out.

For now, see the [http://en.wikipedia.org/wiki/Wikipedia:Multilingual_coordination Wikipedia page on Multilingual coordination], and [http://meta.wikimedia.org/wiki/How_to_start_a_new_Wikipedia How to start a new Wikipedia] for some good general tips, advice, and community conventions.

You may want to start with the list of [[stable-pages]], which are pages that are relatively stable, and have only minimal/editorial changes, which makes them much easier to keep in sync with the English versions, by using the [[Special:Watchlist|my watchlist]] feature (use it to watch the pages you've translated for changes).

Page naming: for the translated version of a page, use the same name for the page, and simply add the RFC 3066 language identifier code as a dash suffix. E.g. for the French version, [[Main_Page]] becomes [[Main_Page-fr]], and [[how-to-play]] becomes [[how-to-play-fr]].

==== more languages folks want to see ====

* Chinese: 微格式 (Microformats) (see [http://msittig.blogspot.com/2005/11/since-i-translated-schedule-of.html source of translation])
* Does somebody want to see a Dutch translation???

Main Page

2007-01-04T20:42:41Z

RobertBachmann: Reverted edit of Zaza, changed back to last version by SteveIvy

plain-old-xml-considered-harmful

2006-11-25T14:42:29Z

RobertBachmann: Reverted edit of 1164465007, changed back to last version by DavidOsolkowski

= plain old xml considered harmful =

(This article is a stub, feel free to expand upon it)

The plain old xml approach has already been tried by *numerous* others
since 1998 and has failed on the Web.

http://blog.davidjanes.com/:entry:davidjanes-2005-10-04-0000/

OTOH, [[semantic-xhtml|XHTML]] + [[semantic-class-names]] has seen widespread adoption among the
web authoring/design/IA/publishing community. Microformats is leveraging
the approach that is both working better and frankly dominating in practice
on the Web.

http://microformats.org/blog/2006/01/09/tim-bray-on-creating-xml-dialects/

See also [[namespaces-considered-harmful]].

XML elements are limited to only one "name" and thus only one meaning, whereas the
class attribute is a space separated set of names and can thus capture
multiple meanings, providing a much more flexible semantic structure for
authors, and greatly aiding in following DRY.

There are 1000s more web authors/developers that write/understand (X)HTML
+ semantic class names + CSS as compared to the number of folks that
write/understand either plain or namespaced XML.

It's the publishers that matter, not the programmers. To put it
another way, programmers can solve problems once and share open source.
Publishers have to keep solving markup/publishing problems for content and
design numerous times continuously, and have much less chance of being able
to share their solutions. That, plus the fact that there are many more web
designers than programmers, plus simple economics, means the best solution is
to optimize for ease of publishing, and let iterative open source solve the
programming problems.

XML also has disadvantages in that an XML processor is required to abort when it encounters an error, so a single unescaped ampersand can cause an XML document to be entirely unreadable. This is hardly appropriate for an end-user application, so many people ignore this requirement and break the spec, so they're not actually using XML. Furthermore, serving XML over HTTP is difficult; there are all kinds of complicated issues dealing with character encodings; start with RFC 3023.

== See Also ==

* [[namespaces-considered-harmful]]
* [[microformats-easier-than-xml]]
* [[semantic-xhtml]]
* [[semantic-class-names]]

mailing-lists-proposals

2006-10-29T12:04:50Z

RobertBachmann: /* Change nothing */ vote: -1

=Mailing Lists Proposals=

There is a proposal for creating a new [[mailing-lists|mailing list]] for discussing the research and creation of new microformats so that those discussions do not overwhelm microformats-discuss.

Some candidates for names with the thinking behind them. Feel free to add your name and opinion (+/- 1 or 0).

==microformats-new==
Focusing on discussing "new" microformats
* +1 Tantek
* +1 ScottReynen
* -1 Lachlan Hunt
* +1 Joe Andrieu
* -1 Andy Mabbett
* +1 Bob Jonkman
* +1 Ben Ward
* +1 Ben O'Neill
* +1 Robert Bachmann

==microformats-research==
Focusing on the essential, and often overlooked by first-time proposers "research" phase(s) in the process
* +0 Tantek
* +1 ScottReynen
* +1 cgriego
* +1 Phae
* +1 JustinThorp
* -1 Andy Mabbett
* -1 Joe Andrieu
* -1 Bob Jonkman (research is part of process, best documented on the Wiki)
* -1 Ben Ward (strikes me as dilution too far of µf-discuss and µf-new)
* 0 Lachlan Hunt
==microformats-process==
That's really what we're talking about with research of new microformats, isn't it?
* +1 ScottReynen
* +1 Lachlan Hunt
* +1 [[User:Singpolyma|singpolyma]]
* -1 Andy Mabbett
* -1 Joe Andrieu
* -1 cgriego (reminds me of parsing--processing--more so than even microformats-dev)
* -1 Bob Jonkman (Is this the process of creating a new microformat, or the some other process? Document it on the Wiki, I say)
* +0 Tantek
==microformats-propose==
* -1 Tantek
* -1 ScottReynen
* 0 Andy Mabbett
* -1 Bob Jonkman
* -1 Ben Ward

Comment (possibly by Tantek?): It misses the point of the process, and implies that there is a desire for microformats proposals - there isn't.

==microformats-suggest==
Similar to propose but milder ;)
* +1 ChrisMessina
* -1 Tantek
* -1 ScottReynen
* -1 Phae (I feel this is just -propose in disguise)
* -1 BenWest
* -1 Andy Mabbett
* -1 Bob Jonkman
* -1 Ben Ward (If µf-new or similar is created for active spec'ing and format development, uf-discuss would comfortably accomodate this as part of the course of discussion)
==microformats-work==
For working on microformats, new and old.

* +1 BenWest: I thought we are interested in a list that provides a venue for iterating through the process, and revising and refining microformats in general. discuss is for newbies, and dev is for implementing them.
* -1 Tantek: work could mean anything though, not just work on creating new microformats.

==microformats-wg==
WG is an abbreviation of Working Group
* +1 Lachlan Hunt
* -1 Tantek: "working group" means something quite specific in W3C terminology. Very little of that applies to the set of people that work on creating new microformats.
* -1 BenWard: As Tantek says, ‘working group’ means something that Microformats doesn't have and doesn't want. What's more, to an observer ‘Working Group’ implies exclusivity which isn't what µf development is about.

==microformats-tf==
TF is an abbreviation of Task Force
* 0 Lachlan Hunt
* -1 Tantek: Though less overloaded with specific meaning than "working group", "task force" still means something quite specific in W3C terminology as well as other standards organizations. Very little of that applies to the set of people that work on creating new microformats.
* -1 BenWard

==Change nothing==
e.g fix uf-dev, do nothing else (for now)
* +1 RyanKing
* +1 Tim White
* +1 Andy Mabbett
* 0 Bob Jonkman
* 0 Ben Ward
* -1 BenWest
* -1 Tantek (we have opened uf-dev and I still strongly believe we need a new list for the discussion of new microformats, separate from microformats-discuss in order to avoid overwhelming new folks with details and minutiae of new and in development formats.)
* -1 Robert Bachmann

= General Comments=

==Andy Mabbett==
Why not create a new mailing list for each proposal, once it's reached a certain stage? Then , if the uF is created, or the proposal abandoned, the specific list would be closed, and the archive retained as a link from the "brainstorming" page, as a permanent, and discrete record of discussion on that topic.

Alternatively, the list could be retained for discussion of the implementation and development of that specific uF.

For example, several academic and professional taxonomists have told me in e-mail that they would be interested in the [[species]] proposal, (and one astronomer, likewise, for [[mars]]/ [[luna]]), but do not have the time to follow a general mailing list; indeed, a couple asked me specifically if I would set up a separate mailing list for the subject.

[[User:AndyMabbett|Andy Mabbett]] 04:44, 24 Oct 2006 (PDT)

*The biggest challenge with creating new microformats (especially for new comers) is with following the process. The same discussions are often had over and over for different formats, thus it makes sense for people developing different formats to at least see the discussions around the creation of other formats and hopefully learn from them and avoid repeating the same questions or mistakes. [[User:Tantek|Tantek]] 00:10, 25 Oct 2006 (PDT)
**Someone new to the mailing list won't see past discussion there anyway; they need to be referred to the archive. If busy people, whose expertise we need, choose not to see discussion of other, unrelated microformats, we can't force it on them - we either provide a more specifically-focussed forum, or they don't participate at all - which is best? [[User:AndyMabbett|Andy Mabbett]] 03:06, 25 Oct 2006 (PDT)

*In addition, part of the [[microformats]] methodology/philosophy/principles is simplicity and minimalism - the fewer the better. This applies not only to microformats, microformats properties, and microformats values, but to microformats mailing lists as well. Thus since the beginning we have only created lists when absolutely necessary (i.e. when the traffic/topics crowded out one of the other lists), and then only one at a time. [[User:Tantek|Tantek]] 00:10, 25 Oct 2006 (PDT)
**I can see what has happened previously; I'm suggesting - with a stated justification - a variation on that. There is more than one opinion, as to what is "necessary". [[User:AndyMabbett|Andy Mabbett]] 03:06, 25 Oct 2006 (PDT)

mailing-lists-proposals

2006-10-29T12:01:20Z

RobertBachmann: /* microformats-new */ vote: +1

=Mailing Lists Proposals=

There is a proposal for creating a new [[mailing-lists|mailing list]] for discussing the research and creation of new microformats so that those discussions do not overwhelm microformats-discuss.

Some candidates for names with the thinking behind them. Feel free to add your name and opinion (+/- 1 or 0).

==microformats-new==
Focusing on discussing "new" microformats
* +1 Tantek
* +1 ScottReynen
* -1 Lachlan Hunt
* +1 Joe Andrieu
* -1 Andy Mabbett
* +1 Bob Jonkman
* +1 Ben Ward
* +1 Ben O'Neill
* +1 Robert Bachmann

==microformats-research==
Focusing on the essential, and often overlooked by first-time proposers "research" phase(s) in the process
* +0 Tantek
* +1 ScottReynen
* +1 cgriego
* +1 Phae
* +1 JustinThorp
* -1 Andy Mabbett
* -1 Joe Andrieu
* -1 Bob Jonkman (research is part of process, best documented on the Wiki)
* -1 Ben Ward (strikes me as dilution too far of µf-discuss and µf-new)
* 0 Lachlan Hunt
==microformats-process==
That's really what we're talking about with research of new microformats, isn't it?
* +1 ScottReynen
* +1 Lachlan Hunt
* +1 [[User:Singpolyma|singpolyma]]
* -1 Andy Mabbett
* -1 Joe Andrieu
* -1 cgriego (reminds me of parsing--processing--more so than even microformats-dev)
* -1 Bob Jonkman (Is this the process of creating a new microformat, or the some other process? Document it on the Wiki, I say)
* +0 Tantek
==microformats-propose==
* -1 Tantek
* -1 ScottReynen
* 0 Andy Mabbett
* -1 Bob Jonkman
* -1 Ben Ward

Comment (possibly by Tantek?): It misses the point of the process, and implies that there is a desire for microformats proposals - there isn't.

==microformats-suggest==
Similar to propose but milder ;)
* +1 ChrisMessina
* -1 Tantek
* -1 ScottReynen
* -1 Phae (I feel this is just -propose in disguise)
* -1 BenWest
* -1 Andy Mabbett
* -1 Bob Jonkman
* -1 Ben Ward (If µf-new or similar is created for active spec'ing and format development, uf-discuss would comfortably accomodate this as part of the course of discussion)
==microformats-work==
For working on microformats, new and old.

* +1 BenWest: I thought we are interested in a list that provides a venue for iterating through the process, and revising and refining microformats in general. discuss is for newbies, and dev is for implementing them.
* -1 Tantek: work could mean anything though, not just work on creating new microformats.

==microformats-wg==
WG is an abbreviation of Working Group
* +1 Lachlan Hunt
* -1 Tantek: "working group" means something quite specific in W3C terminology. Very little of that applies to the set of people that work on creating new microformats.
* -1 BenWard: As Tantek says, ‘working group’ means something that Microformats doesn't have and doesn't want. What's more, to an observer ‘Working Group’ implies exclusivity which isn't what µf development is about.

==microformats-tf==
TF is an abbreviation of Task Force
* 0 Lachlan Hunt
* -1 Tantek: Though less overloaded with specific meaning than "working group", "task force" still means something quite specific in W3C terminology as well as other standards organizations. Very little of that applies to the set of people that work on creating new microformats.
* -1 BenWard

==Change nothing==
e.g fix uf-dev, do nothing else (for now)
* +1 RyanKing
* +1 Tim White
* +1 Andy Mabbett
* 0 Bob Jonkman
* 0 Ben Ward
* -1 BenWest
* -1 Tantek (we have opened uf-dev and I still strongly believe we need a new list for the discussion of new microformats, separate from microformats-discuss in order to avoid overwhelming new folks with details and minutiae of new and in development formats.)

= General Comments=

==Andy Mabbett==
Why not create a new mailing list for each proposal, once it's reached a certain stage? Then , if the uF is created, or the proposal abandoned, the specific list would be closed, and the archive retained as a link from the "brainstorming" page, as a permanent, and discrete record of discussion on that topic.

Alternatively, the list could be retained for discussion of the implementation and development of that specific uF.

For example, several academic and professional taxonomists have told me in e-mail that they would be interested in the [[species]] proposal, (and one astronomer, likewise, for [[mars]]/ [[luna]]), but do not have the time to follow a general mailing list; indeed, a couple asked me specifically if I would set up a separate mailing list for the subject.

[[User:AndyMabbett|Andy Mabbett]] 04:44, 24 Oct 2006 (PDT)

*The biggest challenge with creating new microformats (especially for new comers) is with following the process. The same discussions are often had over and over for different formats, thus it makes sense for people developing different formats to at least see the discussions around the creation of other formats and hopefully learn from them and avoid repeating the same questions or mistakes. [[User:Tantek|Tantek]] 00:10, 25 Oct 2006 (PDT)
**Someone new to the mailing list won't see past discussion there anyway; they need to be referred to the archive. If busy people, whose expertise we need, choose not to see discussion of other, unrelated microformats, we can't force it on them - we either provide a more specifically-focussed forum, or they don't participate at all - which is best? [[User:AndyMabbett|Andy Mabbett]] 03:06, 25 Oct 2006 (PDT)

*In addition, part of the [[microformats]] methodology/philosophy/principles is simplicity and minimalism - the fewer the better. This applies not only to microformats, microformats properties, and microformats values, but to microformats mailing lists as well. Thus since the beginning we have only created lists when absolutely necessary (i.e. when the traffic/topics crowded out one of the other lists), and then only one at a time. [[User:Tantek|Tantek]] 00:10, 25 Oct 2006 (PDT)
**I can see what has happened previously; I'm suggesting - with a stated justification - a variation on that. There is more than one opinion, as to what is "necessary". [[User:AndyMabbett|Andy Mabbett]] 03:06, 25 Oct 2006 (PDT)

press

2006-10-20T21:43:46Z

RobertBachmann: /* 2006 */ November: iX 11/2006 German

__NOTOC__
<h1> Press </h1>

This page documents the press that [[microformats]] has received. See also microformats [[screencasts]], [[presentations]], [[podcasts]], and [[books]].

== 2006 ==
=== November ===

* Cover story in iX 11/2006 p. 62-65: [http://www.heise.de/ix/artikel/2006/11/062/ Mehrwert-Markup] (German: additional value markup)

=== August ===
* [http://digital-web.com/articles/the_big_picture_on_microformats/ The Big Picture on microformats] - who's doing what with microformats right now - by John Allsopp - Published August 28th, 2006.
* [http://www.thinkvitamin.com/features/design/how-to-use-microformats Add microformats magic to your site] by John Allsopp - Published August 25th, 2006.

=== July ===
* [http://knowledge.wharton.upenn.edu/article.cfm?articleid=1526 Knowledge at Wharton: Tantek Çelik and Rohit Khare: The Progress and the Promise of Microformats] - Published: July 20, 2006
=== June ===
* [http://devzone.zend.com/node/view/id/584 Microformats, PHP and hKit], from devzone.zend.com, a PHP developer resource, 28th June.
* [http://www.mercurytide.com/knowledge/white-papers/microformats Building a more semantic web with microformats], from Mercurytide, 20th June.
=== May ===
* [http://www.devsource.com/article2/0,1895,1961106,00.asp DevSource: An Developer's Introduction to Microformats by Phil Haack, May 11.]
** See also Phil Haack's [http://haacked.com/archive/2006/05/11/IntroductionToMicroformatsArticle.aspx blog post about the article].
=== April ===
=== March ===
* (need to backfill these - there were a bunch and I think we simply forgot to add them in)
=== February ===
* [http://book.mycom.co.jp/wd/ Web Designing], a popular paper magazine for web industry in Japan, contained an article about microformats on its 03/2006 issue.
* [http://www.release1-0.com/freshproduce/newideas_socialtime.cfm Release 1.0 / Ideas / New Ideas that Matter: Time as a social object], February 16. Video interviews composite, including a bit on microformats.
* [http://2006.sxsw.com/interactive/web_awards/finalists/ SXSW 2006 Web Awards Finalists], February 3rd. [http://microformats.org microformats.org] is a finalist in the "Technical Achievement" category for "the sites that are re-inventing and re-defining the technical parameters of our online experience".
=== January ===
* [http://code.google.com/webstats/index.html Google Web Authoring Statistics, January 20]
*# The home page of the study "[http://code.google.com/webstats/index.html Web Authoring Statistics]" itself both mentions “microformats.org” and links to http://microformats.org .
*# The "[http://code.google.com/webstats/2005-12/pageheaders.html Page Headers]” page notes that the [http://gmpg.org/xfn/ XFN] microformat is the most popular HTML metadata profile: “…people do use the profile attribute, though. The three most-often used values are http://gmpg.org/xfn/1, http://dublincore.org/documents/dcq-html/, and http://gmpg.org/xfn/11. This makes XFN the most popular HTML metadata profile!”
*# The “[http://code.google.com/webstats/2005-12/element-a.html a element]” page found that three of the most popular ‘rel’ attribute values were microformats: #1 [[rel-nofollow]], #2 [[rel-license]], #5 [[rel-tag]].
* [http://www.philoneist.com/50226711/interview_with_technorati_marketing_director_derek_gordon.php Philoneist: Interview With Technorati Marketing Director Derek Gordon by Jonathan G. Cohen, January 11]
* [http://www.kbcafe.com/iBLOGthere4iM/?guid=20060101232742 #2 on the list of Best Web 2.0 Blogs, January 2]

== 2005 ==
=== December ===
* [http://www.publish.com/article2/0,1759,1904359,00.asp Publish: Year in Review: CSS, Standards, Microformats and Flash, By Stephen Bryant, December 21]
* [http://www.primezone.com/newsroom/news.html?d=91118 Newswire: Structured Blogging to support microformats, December 13th]
* [http://www.linuxjournal.com/article/8731 Linux Journal: Syndication and the Live Web Economy, By Doc Searls, December 9]
=== November ===
* [http://acmqueue.com/modules.php?name=Content&pa=showpage&pid=349&page=4 ACM Queue: A Conversation with Ray Ozzie, ACM Queue vol. 3, no. 9 - November 2005]
* [http://www.digital-web.com/articles/microformats_primer/ Digital Web Magazine: Microformats Primer by Garrett Dimon, November 14, 2005]
=== October ===
* [http://www.xml.com/pub/a/2005/10/19/microformats-and-web-2.0.html XML.com: Microformats and Web 2.0 by Micah Dubinko, October 19, 2005]
=== September ===
* [http://channel9.msdn.com/Showpost.aspx?postid=118325 Channel 9: Interview at PDC] - Robert Scoble interviews Tantek Çelik briefly on web standards, IE, and microformats.

=== July ===
* [http://www.acm.org/technews/articles/2005-7/0722f.html#item12 ACM News Service - Volume 7, Issue 819: Friday, July 22, 2005]
* [http://lists.ssc.com/pipermail/suitwatch/2005-July/000090.html Linux Journal: SuitWatch -- July 21 -- by Doc Searls, Senior Editor of Linux Journal: Making More Sense of the Web]
* [http://knowledge.wharton.upenn.edu/index.cfm?fa=viewArticle&id=1247&specialId=38 Knowledge at Wharton: Supernova 2005: It's a Whole New, Connected World: What's the Next Big Thing on the Web? It May Be a Small, Simple Thing -- Microformats]
** Simplified Chinese: <http://knowledge2.wharton.com.cn//index.cfm?fa=article&articleid=1203&specialid=58&languageid=4>
** Traditional Chinese: <http://knowledge2.wharton.com.cn//index.cfm?fa=article&articleid=1203&specialid=58&l=4&languageid=5>
** Original english version: <http://knowledge2.wharton.com.cn//index.cfm?fa=article&articleid=1203&specialid=58&languageid=1>
=== June ===
* [http://news.com.com/2030-12-5745034.html#microformats CNET News.com: Supernova 2005 blogcast] - David Weinberger interviews Tantek Çelik and Rohit Khare about microformats and [http://microformats.org/ microformats.org].
** [http://blog.blogcast2005.silkclips.com/clipView?http://silkblogs.com/FindResource/EC139870-22E5-F208-70FA-BC437BD64420/celik-khave-full.mov Watch the full interview with Rohit Khare & Tantek Çelik (22:21 minutes)]
* Golem: [http://www.golem.de/0506/38831.html microformats.org - Formate für Menschen und Maschinen] (German: microformats.org - Formats for humans and machines)

=== March ===
* [http://www.xml.com/pub/a/2005/03/23/deviant.html XML.com: What Are Microformats?]

Main Page

2006-10-07T15:17:44Z

RobertBachmann: /* shared work areas */ added spread microformats

__NOTOC__

<h1> Microformats Wiki </h1>

'''Hello!''' Welcome to the microformats wiki. If this is your first visit, please see the [[introduction]] page.

Please read [[how-to-play]] before making any edits.

Please read [[process]] before proposing any new microformats.

__TOC__

== Background==

[[what-are-microformats|What are microformats]]? [[what-can-you-do-with-microformats|What can you do with them]]?

The [http://microformats.org/about/ about page], plus recent [[press]], [[presentations]], [[podcasts]], and [[screencasts]] are also good places for some background information. Frequently asked questions are answered in the [[faq|FAQ]]. Want to learn more in person? Check out [[events|microformats events]].

==Definition==

One popular definition from our [http://microformats.org/discuss/ mailing list] (see also: [[mailing-lists]]) is "simple conventions for embedding semantics in HTML to enable decentralized development." More precisely, microformats can be defined as:
:simple conventions
:for embedding semantic markup
::for a specific problem domain
:in human-readable (X)HTML/XML documents, Atom/RSS feeds, and "plain" XML
::that normalize existing content usage patterns
::using brief, descriptive class names
::often based on existing interoperable standards
:to enable decentralized development
::of resources, tools, and services

"Or do you just use your browser to browse? That's so 20th century." -- [http://diveintomark.org Mark Pilgrim]

== How to contribute ==

Want to help take microformats to the next level?

Check out our open [[to-do|to do list]] for things to help get done. Join the [http://microformats.org/discuss mailing lists and irc channel] and learn and help answer questions about microformats.

Take a look at the [[Main_Page#microformats_wiki_in_other_languages| microformats wiki in other languages]] and help translate the microformats wiki to make microformats globally accessible.

== Specifications ==
[[microformats|Microformats]] open standards specifications (see also: [[implementations]])
* [[hcalendar|hCalendar]]
* [[hcard|hCard]]
* [[rel-license]]
* [[rel-nofollow]]
* [[rel-tag]]
* [[vote-links|VoteLinks]]
* [http://gmpg.org/xfn/ XFN] (see also: [[xfn-implementations]])
* [http://gmpg.org/xmdp/ XMDP]
* [[xoxo|XOXO]]

== Drafts ==
* [[adr|adr]]
* [[geo|geo]]
* [[hatom|hAtom]] {{NewMarker}}
* [[hresume|hResume]] {{NewMarker}}
* [[hreview|hReview]]
* [[rel-directory]]
* [[rel-enclosure]]
* [[rel-home]]
* [[relpayment-research | rel-payment]]
* [[robots-exclusion|Robots Exclusion]]
* [[xfolk|xFolk]]

== Design Patterns ==

{{design_patterns}} 

== Exploratory Discussions ==
Research and analysis of real-world [[examples]], existing formats, and brainstorming to motivate the microformat.
*alternates [[alternates-brainstorming|brainstorming]], [[alternates-examples|examples]]
*[[attention]]
* blog description [[blog-description-examples|examples]]
* blog info [[blog-info-examples|examples]]
* blog post [[blog-post-examples|examples]], [[blog-post-formats|formats]], and [[blog-post-brainstorming|brainstorming]] (yielded the [[hatom|hAtom]] draft)
* book [[book-examples|examples]], [[book-formats|formats]], and [[book-brainstorming|brainstorming]]
* chat [[chat-examples|examples]], [[chat-formats|formats]], and [[chat-brainstorming|brainstorming]]
* citation [[citation|effort]], [[citation-examples|examples]], [[citation-formats|formats]], [[citation-brainstorming|brainstorming]], and [[citation-faq|FAQ]]
* comment [[comment-problem|problem]], [[comment-examples|examples]], and [[comments-formats|formats]] (Some stuff needs to be extracted from [[comments-formats]])
* currency [[currency-examples|examples and brainstorming]] {{NewMarker}}
* directions [[directions-examples|examples]] {{NewMarker}}
* directory inclusion [[directory-inclusion-examples|examples]], [[directory-inclusion-formats|formats]]. (see also [[rel-directory]])
* distributed conversation [[distributed-conversation|overview]], [[distributed-conversation-brainstorming|brainstorming]], [[distributed-conversation-examples|examples]], and [[distributed-conversation-formats|formats]]
* forms [[forms-examples|examples]]
* genealogy [[genealogy-formats|examples]]
* group [[group-brainstorming|brainstorming]] and [[group-examples|examples]]
* hash [[hash-examples|examples]]
* job listing [[job-listing-examples|examples]] and [[job-listing-brainstorming|brainstorming]]
* last modified [[last-modified-examples|examples]], [[last-modified-formats|formats]], and [[last-modified-brainstorming|brainstorming]]
* hListing [[hlisting-proposal|proposal]], and [[hlisting-feedback|feedback]] {{NewMarker}}
** Also, listing [[listing-examples|examples]], [[listing-formats|formats]], and [[listing-brainstorming|brainstorming]]
* location [[location-formats|formats]]. (see also [[adr]] and [[geo]])
* [[luna]] ([[geo]]-like co-ordinates, for places on The Moon) {{NewMarker}}
* [[mars]] ([[geo]]-like co-ordinates, for places on the planet Mars) {{NewMarker}}
* measures and measurement units [[measure]]
* [[media-info]] ([[media-info-examples|examples]], [[media-info-formats|formats]], [[media-info-brainstorming|brainstorming]])
* meeting minutes [[meeting-minutes-examples|examples]], [[meeting-minutes-formats|formats]], and [[meeting-minutes-brainstorming|brainstorming]]
* metalink [[metalink-examples|examples]] {{NewMarker}}
* [[mfo-examples|MFO examples]]
* music [[music-examples|examples]]
* photo note [[photo-note-examples|examples]]
* recipe [[recipe-examples|examples]]
* rel-product [[rel-product-brainstorming|brainstorming]]
* requirements testing [[requirements-testing|overview]], and [[requirements-testing-examples|examples]]
* [[rest-examples|REST examples]]
* resume [[resume-brainstorming|brainstorming]], and [[resume-formats|formats]]
* review [[review-examples|examples]], and [[review-formats|formats]] (yielded the [[hreview|hReview]] draft)
* search results [[search-results-example|example]]
* show [[show-brainstorming|brainstorming]]
* showroll [[showroll-brainstorming|brainstorming]]
* [[species]] (or "''sci''"): for the marking up of the scientific names of living things. {{NewMarker}}
* table [[table-examples|examples]]
* tagspeak [[tagspeak-examples|examples]]
* tagcloud [[tagcloud-examples|examples]], and [[tagcloud-brainstorming | brainstorming]]. {{NewMarker}}
* transit table [[transit-table-examples|examples]]
* [[uid]]
* widget [[widget-examples|examples]], and [[widget-brainstorming|brainstorming]]
* [[wiki-formats|wiki formats]]
* work of art [[work-of-art|overview]], [[workofart-examples|examples]], [[workofart-formats|formats]], and [[workofart-brainstorming|brainstorming]] {{NewMarker}}
*[[xmdp-brainstorming|XMDP brainstorming]] (see also [[xmdp-faq]])

== Examples ==
* [[examples]]
* [[zen-garden]]

== Tools & Test Cases & Additional Research ==

The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting tools and services that need to process more than one microformat. This section is intended for editors, parsers, validators, test cases, and other information relevant across multiple microformats.

*[[accessibility]]
*[[faqs-for-rdf]]
*[[icalendar-implementations]]
*[[parsing-microformats]]
*[[selected-test-cases-from-the-web]]
*[http://hg.microformats.org/ Source code repository] -- [[mercurial-quick-start|HowTo: Download code from the repository]]
*[[vcard-implementations]], [[vcard-errata]]
*[[why-are-content-standards-hard]]

== shared work areas ==
* [[buttons]]
* [[spread-microformats]] {{NewMarker}}
* [[demo]] - a page with links for quickly demonstrating microformats working in practice.
* [[events]] {{NewMarker}}
* [[to-do]]
* [[user-interface]]
* [[marked-for-deletion]]

== microformats wiki in other languages ==

You may read and edit microformats articles in many other languages:

* languages with over 50 articles
** [[Main_Page-fr|Français (French)]] {{NewMarker-fr}}
* languages with over 2 articles
** [[Main_Page-ja|日本語 (Japanese)]]
** [[Main_Page-es|Español (Spanish)]]
* languages with 2 articles
** [[Main_Page-de|Deutsch (German)]]

==== microformats translations elsewhere ====
These are offsite pages/sites with translations about microformats. If you are working on one of these, please consider translating the main microformats website!
* [http://mikroformate.pbwiki.com/ Deutsch (German) mikroformate.pbwiki.com] {{NewMarker}}

=== Start a microformats wiki in another language ===

Don't see the language you want? Help translate the microformats wiki into another language!

We're still figuring this out.

For now, see the [http://en.wikipedia.org/wiki/Wikipedia:Multilingual_coordination Wikipedia page on Multilingual coordination], and [http://meta.wikimedia.org/wiki/How_to_start_a_new_Wikipedia How to start a new Wikipedia] for some good general tips, advice, and community conventions.

You may want to start with the list of [[stable-pages]], which are pages that are relatively stable, and have only minimal/editorial changes, which makes them much easier to keep in sync with the English versions, by using the [[Special:Watchlist|my watchlist]] feature (use it to watch the pages you've translated for changes).

Page naming: for the translated version of a page, use the same name for the page, and simply add the RFC 3066 language identifier code as a dash suffix. E.g. for the French version, [[Main_Page]] becomes [[Main_Page-fr]], and [[how-to-play]] becomes [[how-to-play-fr]].

==== more languages folks want to see ====

* Chinese: 微格式 (Microformats) (see [http://msittig.blogspot.com/2005/11/since-i-translated-schedule-of.html source of translation])

Main Page

2006-09-20T20:41:56Z

RobertBachmann: Reverted edit of Fox, changed back to last version by AndyMabbett

__NOTOC__
= Microformats Wiki =

'''Please read [[how-to-play]] before making any edits.'''

'''Please read [[process]] before proposing any new microformats.'''

== Introduction ==

[[what-are-microformats|What are microformats]]? And [[what-can-you-do-with-microformats|what can you do with them]]? See the [http://microformats.org/about/ about page] for an overview, and the [[introduction]] page for more info. Recent [[press]], [[presentations]], [[podcasts]], and [[screencasts]] are also a good place for some background reading/listening. Frequently asked questions are answered in the [[faq]]. Want something or want to contribute? Help with things [[to-do]]. Want to learn more in person? Check out microformats [[events]].

One popular definition from our [http://microformats.org/discuss/ mailing list] (see also: [[mailing-lists]]) is "simple conventions for embedding semantics in HTML to enable decentralized development." More precisely, microformats can be defined as:
:simple conventions
:for embedding semantic markup
::for a specific problem domain
:in human-readable (X)HTML/XML documents, Atom/RSS feeds, and "plain" XML
::that normalize existing content usage patterns
::using brief, descriptive class names
::often based on existing interoperable standards
:to enable decentralized development
::of resources, tools, and services

"Or do you just use your browser to browse? That's so 20th century." -- [http://diveintomark.org Mark Pilgrim]

== How to contribute ==

Want to help take microformats to the next level?

Check out our open [[to-do]] list for things to help get done. Join the [http://microformats.org/discuss mailing lists and irc channel] and learn and help answer questions about microformats.

Take a look at the [[Main_Page#microformats_wiki_in_other_languages| microformats wiki in other languages]] and help translate the microformats wiki to make microformats globally accessible.

== Specifications ==
[[microformats|Microformats]] open standards specifications (see also: [[implementations]])
* [[hcalendar|hCalendar]]
* [[hcard|hCard]]
* [[rel-license]]
* [[rel-nofollow]]
* [[rel-tag]]
* [[vote-links|VoteLinks]]
* [http://gmpg.org/xfn/ XFN] (see also: [[xfn-implementations]])
* [http://gmpg.org/xmdp/ XMDP]
* [[xoxo|XOXO]]

== Drafts ==
* [[adr|adr]]
* [[geo|geo]]
* [[hatom|hAtom]] {{NewMarker}}
* [[hresume|hResume]] {{NewMarker}}
* [[hreview|hReview]]
* [[rel-directory]]
* [[rel-enclosure]]
* [[rel-home]]
* [[relpayment-research | rel-payment]]
* [[robots-exclusion|Robots Exclusion]]
* [[xfolk|xFolk]]

== Design Patterns ==

{{design_patterns}} 

== Exploratory Discussions ==
Research and analysis of real-world [[examples]], existing formats, and brainstorming to motivate the microformat.
*[[attention]]
* blog description [[blog-description-examples|examples]]
* blog info [[blog-info-examples|examples]]
* blog post [[blog-post-examples|examples]], [[blog-post-formats|formats]], and [[blog-post-brainstorming|brainstorming]] (yielded the [[hatom|hAtom]] draft)
* book [[book-examples|examples]], [[book-formats|formats]], and [[book-brainstorming|brainstorming]]
* chat [[chat-examples|examples]], [[chat-formats|formats]], and [[chat-brainstorming|brainstorming]]
* citation [[citation|effort]], [[citation-examples|examples]], [[citation-formats|formats]], [[citation-brainstorming|brainstorming]], and [[citation-faq|FAQ]]
* comment [[comment-problem|problem]], [[comment-examples|examples]], and [[comments-formats|formats]] (Some stuff needs to be extracted from [[comments-formats]])
* currency [[currency-examples|examples and brainstorming]] {{NewMarker}}
* directions [[directions-examples|examples]] {{NewMarker}}
* directory inclusion [[directory-inclusion-examples|examples]], [[directory-inclusion-formats|formats]]. (see also [[rel-directory]])
* distributed conversation [[distributed-conversation|overview]], [[distributed-conversation-brainstorming|brainstorming]], [[distributed-conversation-examples|examples]], and [[distributed-conversation-formats|formats]]
* forms [[forms-examples|examples]]
* genealogy [[genealogy-formats|examples]]
* group [[group-brainstorming|brainstorming]] and [[group-examples|examples]]
* hash [[hash-examples|examples]]
* job listing [[job-listing-examples|examples]] and [[job-listing-brainstorming|brainstorming]]
* last modified [[last-modified-examples|examples]], [[last-modified-formats|formats]], and [[last-modified-brainstorming|brainstorming]]
* hListing [[hlisting-proposal|proposal]], and [[hlisting-feedback|feedback]] {{NewMarker}}
** Also, listing [[listing-examples|examples]], [[listing-formats|formats]], and [[listing-brainstorming|brainstorming]]
* location [[location-formats|formats]]. (see also [[adr]] and [[geo]])
* [[luna]] ([[geo]]-like co-ordinates, for places on The Moon) {{NewMarker}}
* [[mars]] ([[geo]]-like co-ordinates, for places on the planet Mars) {{NewMarker}}
* media info [[media-info-examples|examples]]
* meeting minutes [[meeting-minutes-examples|examples]], [[meeting-minutes-formats|formats]], and [[meeting-minutes-brainstorming|brainstorming]]
* metalink [[metalink-examples|examples]] {{NewMarker}}
* [[mfo-examples|MFO examples]]
* music [[music-examples|examples]]
* photo note [[photo-note-examples|examples]]
* recipe [[recipe-examples|examples]]
* rel-product [[rel-product-brainstorming|brainstorming]]
* requirements testing [[requirements-testing|overview]], and [[requirements-testing-examples|examples]]
* [[rest-examples|REST examples]]
* resume [[resume-brainstorming|brainstorming]], and [[resume-formats|formats]]
* review [[review-examples|examples]], and [[review-formats|formats]] (yielded the [[hreview|hReview]] draft)
* search results [[search-results-example|example]]
* show [[show-brainstorming|brainstorming]]
* showroll [[showroll-brainstorming|brainstorming]]
* [[species]] (or "''sci''"): for the marking up of the scientific names of living things. {{NewMarker}}
* table [[table-examples|examples]]
* tagspeak [[tagspeak-examples|examples]]
* transit table [[transit-table-examples|examples]]
* [[uid]]
* widget [[widget-examples|examples]], and [[widget-brainstorming|brainstorming]]
* [[wiki-formats|wiki formats]]
* work of art [[work-of-art|overview]], [[workofart-examples|examples]], [[workofart-formats|formats]], and [[workofart-brainstorming|brainstorming]] {{NewMarker}}
*[[xmdp-brainstorming|XMDP brainstorming]] (see also [[xmdp-faq]])

== Examples ==
* [[examples]]
* [[zen-garden]]

== Tools & Test Cases & Additional Research ==

The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting tools and services that need to process more than one microformat. This section is intended for editors, parsers, validators, test cases, and other information relevant across multiple microformats.

*[[accessibility]]
*[[faqs-for-rdf]]
*[[icalendar-implementations]]
*[[parsing-microformats]]
*[[selected-test-cases-from-the-web]]
*[http://hg.microformats.org/ Source code repository] -- [[mercurial-quick-start|HowTo: Download code from the repository]]
*[[vcard-implementations]], [[vcard-errata]]
*[[why-are-content-standards-hard]]

== shared work areas ==
* [[buttons]] {{NewMarker}}
* [[demo]] - a page with links for quickly demonstrating microformats working in practice.
* [[events]] {{NewMarker}}
* [[to-do]]
* [[user-interface]]
* [[marked-for-deletion]]

== microformats wiki in other languages ==

You may read and edit microformats articles in many other languages:

* languages with over 50 articles
** [[Main_Page-fr|Français (French)]] {{NewMarker-fr}}
* languages with over 2 articles
** [[Main_Page-ja|日本語 (Japanese)]]
** [[Main_Page-es|Español (Spanish)]]
* languages with 2 articles
** [[Main_Page-de|Deutsch (German)]]

==== microformats translations elsewhere ====
These are offsite pages/sites with translations about microformats. If you are working on one of these, please consider translating the main microformats website!
* [http://mikroformate.pbwiki.com/ Deutsch (German) mikroformate.pbwiki.com] {{NewMarker}}

=== Start a microformats wiki in another language ===

Don't see the language you want? Help translate the microformats wiki into another language!

We're still figuring this out.

For now, see the [http://en.wikipedia.org/wiki/Wikipedia:Multilingual_coordination Wikipedia page on Multilingual coordination], and [http://meta.wikimedia.org/wiki/How_to_start_a_new_Wikipedia How to start a new Wikipedia] for some good general tips, advice, and community conventions.

You may want to start with the list of [[stable-pages]], which are pages that are relatively stable, and have only minimal/editorial changes, which makes them much easier to keep in sync with the English versions, by using the [[Special:Watchlist|my watchlist]] feature (use it to watch the pages you've translated for changes).

Page naming: for the translated version of a page, use the same name for the page, and simply add the RFC 3066 language identifier code as a dash suffix. E.g. for the French version, [[Main_Page]] becomes [[Main_Page-fr]], and [[how-to-play]] becomes [[how-to-play-fr]].

==== more languages folks want to see ====

* Chinese: 微格式 (Microformats) (see [http://msittig.blogspot.com/2005/11/since-i-translated-schedule-of.html source of translation])

irc

2006-07-12T20:12:33Z

RobertBachmann: /* People on irc */

__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:Adam Craven|AdamCraven]] (+0000)
* [[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:DrewMcLellan|drewinthehead]] (+0000/+0100)
* [[User:EdwardOConnor|hober]] (-0800/-0700)
* [[User:Enric|enric]] (-0800/-0700)
* [[User:Evan|evanpro]] (-0500)
* [[User:Fil|Fil]] (+0200)
* [[User:Grantbow|Grantbow]] (-0800/-0700)
* [[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:Remi|Remi]] (-0500/-0400)
* [[User:RobertBachmann|RobertBachmann]] (+0100/+0200)
** Office hours: <del>Wednesday, 18:00-20:00 UTC</del> (Currently no office hours)
* [[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)
* [[User:Dan Kubb|dkubb]] (-0800/-0700)
* [[User:Ed Summers|edsu]] (-0500/-0400)
* [[User:Smackman|Steve Farrell]] (-0800/-0700)
* [[User:Enric|Enric]] (-0800/-0700)
* [[User:Charlvn|Charl]] (+0200/+0200)
* [[User:MarkoMrdjenovic|friedcell]] (+0100/+0200)

=== Greetings ===
To display a brief description of who you are each time you join the channel, you can 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.jdoewebsite.com</nowiki></code>

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

=== bots ===

* [[mfbot]]
* [[mflogbot]]
* [http://joiwiki.ito.com/joiwiki/index.cgi?jibot jibot]

== Logs ==

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

Atom feed of logs available here: http://microformat.makedatamakesense.com/log_feed/

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

zen-garden

2006-06-22T17:09:16Z

RobertBachmann: /* Open questions */ Project name

= Microformats Zen Garden =

A [http://www.csszengarden.com/ CSS Zen Garden] for microformats is essential for popular adoption. Getting something that "looks cool" for "free" should be a key attraction for convincing authors to "steal" microformatted data and cut'n'paste it into their own sites, and for that matter, to reuse style sheets for microformatted data as well.

Developers of microformat-savvy tools would also benefit from common idioms for presenting and editing microformatted data (for example, consider the impact of Apple's Address Book person-layout/edit view on many other Mac applications).

Unlike the original Zen Garden, Javascript may also prove essential to unlocking designers' flexibility: people have expressed interest in hooking hCards to maps, or [http://web.mit.edu/glasser/www/JSCalendar/ this example of a renderer for hCalendar] [http://web.mit.edu/glasser/www/JSCalendar/hcalendar.html grid views].

== Interested parties ==

People who would be willing to spend time on the garden.

* [[User:RobertBachmann|Robert Bachmann]]
** could act as a point person
** writing the sample document
** providing styles (but he's not a good designer)

* [[User:Scott Reynen|Scott Reynen]]
** could make the backend submission and switcher functionality

* Malarkey (Andy Clarke http://www.stuffandnonsense.co.uk)
** Designer
** I agreed to help by contributing design themes after talking with Kevin and Tantek

* [[User:PhilipAshlock|Philip Ashlock]] (http://www.philaestheta.com)
** Designer/Developer
** I agree to help by developing interface design - clean attractive implementations
** I have a server and domain names to contribute
** I have live data to implement with a university website and a record label website
** My university will essentially be paying me for development work
** Suggestions for where efforts should be focused are most appreciated

* [[User:ChrisMessina|Chris Messina]]
** Designer
** Drupal Theme developer
** I've done a few implementations in experimental Drupal and WordPress themes... would like to do more.

* [[User:Phae|Frances Berriman]]
** New Media Developer (CSS/XHTML primarily, but also an accessibility auditor)
** I offer to contribute time to ensuring development is accessible and adheres to WCAG.
** I offer to help develop initial CSS templates to kick-start the showcase.
** Will also be involved with any promotional or editorial aspects, if necessary.

== Planning ==
=== Open questions ===
* What license should be used? --[[User:RobertBachmann|Robert Bachmann]] 10:34, 21 Oct 2005 (PDT)
** My personal favorites are http://creativecommons.org/licenses/by/2.0/ and http://creativecommons.org/licenses/publicdomain/ --[[User:RobertBachmann|Robert Bachmann]] 14:03, 21 Oct 2005 (PDT)
* Should the example page contain examples for all microformats or should there be one example page per microformat? --[[User:RobertBachmann|Robert Bachmann]] 08:57, 24 Oct 2005 (PDT)
** I think the example pages should mirror real world examples as much as practical. In some cases, microformats will be mixed, and in others they will occur independently, and it would be nice to have an environment in which to test microformat applications on such a diversity of example data. On the other hand, I can see some benefit in keeping it simple to encourage use. --[[User:ScottReynen|Scott Reynen]] 12:44, 26 Oct 2005 (CST)
*** Unsure of status of this project (last edit 2005? Most interested though!) but think given recent development of [[hatom|hAtom]] and the constant growth and popularity of "blogs" as a whole, a blog page would be ideal. Perhaps a standard blog layout, containing author information (to utilise [[hcard|hCard]] and [[hcalendar|hCalendar]]) and many others as they are developed. It would also give the design plenty of space to write about what Microformats are all about, and show them in a really useful real world example that 99% of the viewers will find interesting (I hope). [[User:Phae|Frances Berriman]] 16 June 2006

* Discussion list: Use the microformats discussion list or use an extra list? (-[[User:RobertBachmann|Robert Bachmann]])
** I think a secondary list for this project would be beneficial. A digested version of current development work/status could be sent to the MF discussion lists periodically so that we can gain additional input from the MF group at large, without watering down the usual discussions that occur there. (-[[User:Phae|Frances Berriman]])

* Storing files: Subversion or Mercurial? (-[[User:RobertBachmann|Robert Bachmann]])

* Project name: Perhaps we need an other name? See <http://mezzoblue.com/archives/2006/02/22/homage_and_o/>. (-[[User:RobertBachmann|Robert Bachmann]])
** Having read that article, I think a new name would be beneficial. Perhaps we could discuss it with the Zen Garden creators first, and get their feedback? In the interim, it can be refered to as the MF Zen Garden, until a bright spark thinks of something better! (-[[User:Phae|Frances Berriman]])
** What about <em>Microformats Playground</em>? (suggested by Scott Reynen) (-[[User:RobertBachmann|Robert Bachmann]])
*** +1 [[User:RobertBachmann|Robert Bachmann]]

=== Back end prototype ===
Coded by Scott Reynen

* Demo: http://www.randomchaos.com/mfzen/
* Source: http://www.randomchaos.com/source/

zen-garden

2006-06-21T21:34:56Z

RobertBachmann: /* Planning */

= Microformats Zen Garden =

A [http://www.csszengarden.com/ CSS Zen Garden] for microformats is essential for popular adoption. Getting something that "looks cool" for "free" should be a key attraction for convincing authors to "steal" microformatted data and cut'n'paste it into their own sites, and for that matter, to reuse style sheets for microformatted data as well.

Developers of microformat-savvy tools would also benefit from common idioms for presenting and editing microformatted data (for example, consider the impact of Apple's Address Book person-layout/edit view on many other Mac applications).

Unlike the original Zen Garden, Javascript may also prove essential to unlocking designers' flexibility: people have expressed interest in hooking hCards to maps, or [http://web.mit.edu/glasser/www/JSCalendar/ this example of a renderer for hCalendar] [http://web.mit.edu/glasser/www/JSCalendar/hcalendar.html grid views].

== Interested parties ==

People who would be willing to spend time on the garden.

* [[User:RobertBachmann|Robert Bachmann]]
** could act as a point person
** writing the sample document
** providing styles (but he's not a good designer)

* [[User:Scott Reynen|Scott Reynen]]
** could make the backend submission and switcher functionality

* Malarkey (Andy Clarke http://www.stuffandnonsense.co.uk)
** Designer
** I agreed to help by contributing design themes after talking with Kevin and Tantek

* [[User:PhilipAshlock|Philip Ashlock]] (http://www.philaestheta.com)
** Designer/Developer
** I agree to help by developing interface design - clean attractive implementations
** I have a server and domain names to contribute
** I have live data to implement with a university website and a record label website
** My university will essentially be paying me for development work
** Suggestions for where efforts should be focused are most appreciated

* [[User:ChrisMessina|Chris Messina]]
** Designer
** Drupal Theme developer
** I've done a few implementations in experimental Drupal and WordPress themes... would like to do more.

* [[User:Phae|Frances Berriman]]
** New Media Developer (CSS/XHTML primarily, but also an accessibility auditor)
** I offer to contribute time to ensuring development is accessible and adheres to WCAG.
** I offer to help develop initial CSS templates to kick-start the showcase.
** Will also be involved with any promotional or editorial aspects, if necessary.

== Planning ==
=== Open questions ===
* What license should be used? --[[User:RobertBachmann|Robert Bachmann]] 10:34, 21 Oct 2005 (PDT)
** My personal favorites are http://creativecommons.org/licenses/by/2.0/ and http://creativecommons.org/licenses/publicdomain/ --[[User:RobertBachmann|Robert Bachmann]] 14:03, 21 Oct 2005 (PDT)
* Should the example page contain examples for all microformats or should there be one example page per microformat? --[[User:RobertBachmann|Robert Bachmann]] 08:57, 24 Oct 2005 (PDT)
** I think the example pages should mirror real world examples as much as practical. In some cases, microformats will be mixed, and in others they will occur independently, and it would be nice to have an environment in which to test microformat applications on such a diversity of example data. On the other hand, I can see some benefit in keeping it simple to encourage use. --[[User:ScottReynen|Scott Reynen]] 12:44, 26 Oct 2005 (CST)
*** Unsure of status of this project (last edit 2005? Most interested though!) but think given recent development of [[hatom|hAtom]] and the constant growth and popularity of "blogs" as a whole, a blog page would be ideal. Perhaps a standard blog layout, containing author information (to utilise [[hcard|hCard]] and [[hcalendar|hCalendar]]) and many others as they are developed. It would also give the design plenty of space to write about what Microformats are all about, and show them in a really useful real world example that 99% of the viewers will find interesting (I hope). [[User:Phae|Frances Berriman]] 16 June 2006

* Discussion list: Use the microformats discussion list or use an extra list? (-[[User:RobertBachmann|Robert Bachmann]])

* Storing files: Subversion or Mercurial? (-[[User:RobertBachmann|Robert Bachmann]])

* Project name: Perhaps we need an other name? See <http://mezzoblue.com/archives/2006/02/22/homage_and_o/>. (-[[User:RobertBachmann|Robert Bachmann]])

=== Back end prototype ===
Coded by Scott Reynen

* Demo: http://www.randomchaos.com/mfzen/
* Source: http://www.randomchaos.com/source/

hcard

2006-06-09T15:21:01Z

RobertBachmann: /* Implementations */ removed: "Proposed update: http://rbach.priv.at/2006/hcard-creator"

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

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

=== 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://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.yellowpencil.com/contact/ Yellow Pencil] Using microformats to present company contact information
* [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.

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

== 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.
* [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, 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://randomchaos.com/microformats/base/ Microformat Base] is an open-source PHP microformat aggregation crawler, currently recognizing hreview, hcalendar, and hcard.

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

faqs-for-rdf

2006-05-29T21:38:09Z

RobertBachmann: /* So how do I get the data out? */

= Microformat FAQs for RDF Fans =

__TOC__

==== What are Microformats? ====

Microformats are a set of simple, open data formats built upon existing and widely adopted standards, in particular XHTML used ''correctly''. The processes, principles, and practices of the (open) microformats group are what make microformats "microformats", but they centre on using XHTML as designed, as a semantic language (though they can also be implemented on other XML formats, e.g. Atom).

Although the microformats initiative puts human-readability first, with the help of the [http://www.w3.org/2004/01/rdxh/spec GRDDL] mechanism, it is possible to view microformats as domain-specific [http://www.w3.org/RDF/ RDF] serializations.

See also: [http://microformats.org/about/ About Microformats]

==== For example..? ====

This [http://microformats.org/wiki/hcard-example1-steps example] shows how the hCard microformat can be used to express vCard data.

==== But I do RDF, why should I be interested? ====

Microformats can lower the barrier to putting explicit data on the Web. This is entirely in line with the aims of the [http://www.w3.org/2001/sw/ Semantic Web].

Dan Connolly [http://lists.w3.org/Archives/Public/www-rdf-interest/2000Mar/0103 rdf-interest, March 2000]:
<blockquote>
I believe that one of the best ways to transition into RDF, if not a long-term deployment strategy for RDF, is to manage the information in human-consumable form (XHTML) annotated with just enough info to extract the RDF statements that the human info is intended to convey. In other words: using a relational database or some sort of native RDF data store, and spitting out HTML dynamically, is a lot of infrastructure to operate and probably not worth it for lots of interesting cases. We all know that we have to produce a human-readable version of the thing… why not use that as the primary source?
</blockquote>

==== I have an RDF vocabulary I would like to use as a microformat. How do I do it? ====

Before doing anything else, read the [http://microformats.org/wiki/process Process]. In general the microformat process is data-driven. It starts with material already being published, rather than an existing format, model or schema. You should also check the list of what has already been covered and the work-in-progress on the Wiki MainPage.

It may well be that what you have in mind isn't appropriate for use as a microformat, but it may still be a good idea to develop a (semantic) XHTML representation. Existing microformats demonstrate a standards-friendly way of doing this.

See also: [http://tantek.com/presentations/2005/03/elementsofxhtml/ The Elements of Meaningful XHTML]

==== So, this is about using CSS class values to add semantics? ====

No. XHTML already expresses semantics, the '''HTML''' <code>class</code> attribute is just one of several mechanisms. From the [http://www.w3.org/TR/REC-html40/ HTML 4 spec]:

<blockquote>
The class attribute, on the other hand, assigns one or more class names to an element; the element may be said to belong to these classes.
</blockquote>

See also: [http://www.microformats.org/blog/2005/10/19/more-than-styling/ Class attributes are about more than styling]

==== What about namespaces for the attributes, should I use "xxx:term"? ====

In general, microformats rejects the use of explicit namespace prefixes in
documents as unnecessary for solving the 80/20 of problems that microformats
seeks to solve. The general approach taken is not to attempt to generalise to the extent of [http://research.talis.com/2005/erdf/wiki/Main/RdfInHtml RDF-in-HTML], rather to define more domain-specific formats.

==== But won't there be naming clashes? ====

The social aspect of the microformats [http://microformats.org/wiki/process Process] is such that conflicts ought to be prevented. The goal is to keep things as simple as possible by only focusing on '''existing''' well-defined problems, rather than trying to "boil the ocean" (solve the hypothetical general case).

==== So how do I get the data out? ====

See [http://www.w3.org/TeamSubmission/grddl/ GRDDL]

See also: [http://www.w3.org/2006/05/08-htmltf-minutes.html#item03 hGRDDL proposal]

==== Isn't there a clash between the semantics of XFN and FOAF? ====

The use of the page URI in XFN to identify a person appears to conflict with FOAF's by-reference approach, and to mess up the potential for saying things about the page itself. However in practice this isn't a problem. It's possible to parse the document as XFN (using e.g. [http://www.w3.org/2003/12/rdf-in-xhtml-xslts/grokXFN.xsl grokXFN.xsl]) to extract the person-related statements, e.g.
<pre>
_:personA foaf:homepage <http://example.org/this-page> .
_:personA foaf:knows _:personB .
_:personB foaf:homepage <http://example.org/linked-page> .
</pre>
- and ''independently'' parse the document using other format mappings (e.g. [http://www.w3.org/2000/06/dc-extract/dc-extract.xsl dc-extract.xsl]) to obtain other statements, e.g.
<pre>
<http://example.org/this-page> dc:creator "The Creator" .
</pre>

See also: [http://www.w3.org/2003/g/td/xfn-workalike XFN on the GRDDL], [http://www.oreillynet.com/pub/wlg/8281 XFN Delusions of Grandeur], [http://www.microformats.org/blog/2005/11/02/xfn-grandeur/ XFN Grandeur], [http://dannyayers.com/archives/2005/11/03/xfn-vs-foaf/ XFN vs. FOAF]

==== What other work has been done with microformats and RDF? ====

* [http://www.w3.org/2003/g/td/xfn-workalike XFN on the GRDDL]
* [http://people.w3.org/~dom/archives/2005/05/grddl-specification-updated/ GRDDL specification updated works with Microformats]

==== Are there Schemas for Microformats? ====

Kind of. The primary specification is XHTML, but HTML4 provides a mechanism (the 'profile' attribute of the <head> element) to point to a meta data profile that defines properties and values. There is a (HTML-based) format specified for microformat profiles - [http://www.gmpg.org/xmdp/ XHTML Meta Data Profiles]. Note that XMDP's URLs for specifying terms is compatible with those used by RDF, with "#term" at the end.

==== What RDF vocabularies (and XSLT) corresponding to microformats is available? ====

See [http://esw.w3.org/topic/MicroModels MicroModels] (on ESW Wiki)

==== Isn't this just scraping? ====

No. Because microformats (should) include URI(s) for every profile used, and the profiles are clearly defined, the explicit data contained in a document can be extracted deterministically by parsing.

==== Who else is looking at RDF and microformats? ====

Lots of folks.
Including: [http://www.w3.org/People/Connolly/ Dan Connolly], [http://internetalchemy.org/ Ian Davis], [http://sw.deri.org/~jbreslin/ John Breslin], [http://dannyayers.com Danny Ayers]....

==== How do I get involved? ====

If you're using the Web, you already *are* involved! Next place to go is the [http://microformats.org/ microformats.org] site, and maybe sign up to some of the [http://microformats.org/discuss/ mailing lists] (in particular [http://microformats.org/mailman/listinfo/microformats-discuss/ microformats-discuss]). There's also an IRC channel [irc://irc.freenode.net#microformats #microformats on irc.freenode.net].