Microformats Wiki - User contributions [en]

stock-symbol-examples

2007-09-22T03:40:25Z

BenWest: /* Real-World Examples */ added an example from amazon.com

= Stock Symbols =

News services, financial sites, blogs are various other websites all refer to stocks on a regular basis. Some mentions are part of a news story while others give advice and review the stock or the company.

== The Problem ==

Formulate an unambiguous, machine parseable, representation that can be used when stocks are mentioned. This should work with hReview as it's just marking up the recommended example a bit more to make it easier for tools. (Also see # 9 in [http://microformats.org/wiki/hreview-faq hReview FAQ])

== Participants ==

* John Panzer
* Sujata Ramchandran

== Real-World Examples ==

* From Yahoo! stocks

Shares of Tractor Supply (TSCO:Nasdaq - commentary - research - Cramer's Take)

* MSN Money

The 2006 portfolio is up 12%, lead by Expeditors International of Washington (EXPD, news, msgs),
CSX (CSX, news, msgs) and Caterpillar (CAT, news, msgs), up 59%, 46% and 39%, respectively

* From Motley Fool

I made my top pick Quality Systems (Nasdaq: QSII)

* Wall Street Journal

Toyota Motor Corp. reported Wednesday a 39% rise in its fourth-quarter

* From Google Finance (the ".A" denotes class A shares)

Berkshire Hathaway Inc. (Public, NYSE:BRK.A)

* From a stock pick blog.

Today's pick is Time Warner.

* From a spam email

Golden Apple Oil and Gas, Inc. (GAPJ)
THIS ST OCK IS EXTREMELY UNDERVALUED!
GAPJ - is our NEXT HOT P ICK, which we feel is most undervalued
stock we have ever featured and should out perform all other picks.

* From a spam stock tracking site ([http://www.spamnation.info spamnation.info])

name symbol last date total
BackWeb Technologies Ltd BWEB 10.06.2006 6

* From [http://www.businessweek.com/bwdaily/dnflash/content/feb2007/db20070212_512678.htm?chan=top+news_top+news+index_businessweek+exclusives a Business Week article]

The results of each day's session ripple rapidly throughout the world economy. No sector
is untouched by energy prices: oil producers and refiners who invest billions to explore,
airlines nervous about jet-fuel prices, auto companies who must adjust models rapidly to
survive, and retailers like Wal-Mart Stores (WMT) keen to know how deeply its shoppers will
be dunned at the gas pump.

* From [http://boeing.com/companyoffices/financial/ boeing.com]
<pre><code><nowiki><h2>The Boeing Company</h2>
As of 4:07 PM ET on Sep 21
<table cellpadding="5" cellspacing="0" width="180">
<caption>Stock Quote</caption>
<tbody><tr>

<th class="brand bgltgray" scope="row" nowrap="nowrap">Last</th>
<td class="brand">102.59</td>
</tr>
<tr>
<th class="brand bgltgray" scope="row" nowrap="nowrap">Change</th>
<td class="brand">+ 1.34</td>
</tr>

<tr>
<th class="brand bgltgray" scope="row" nowrap="nowrap">% Change</th>
<td class="brand"><img src="http://www.shareholder.com/common/images/smup.gif"> 1.32</td>
</tr>
<tr>
<th class="brand bgltgray" scope="row" nowrap="nowrap">Prev. Close</th>
<td class="brand">101.25</td>

</tr>
<tr>
<th class="brand bgltgray" scope="row" nowrap="nowrap">Open</th>
<td class="brand">102.35</td>
</tr>
<tr>
<th class="brand bgltgray" scope="row" nowrap="nowrap">Volume</th>

<td class="brand">6,614,000</td>
</tr>
<tr>
<th class="brand bgltgray" scope="row" nowrap="nowrap">Exchange</th>
<td class="brand">NYSE</td>
</nowiki></code></pre>

* [http://phx.corporate-ir.net/phoenix.zhtml?c=97664&p=irol-irhome from amazon.com]
<code><pre><nowiki>
AMZN Amazon.com, Inc.

09/21/07 4:00 p.m. ET
Price $91.30

Change Stock is Up 1.65

% Change 1.84%

</nowiki></pre></code>and
<code><pre><nowiki>
<td align="left" nowrap="nowrap">
AMZN  
Amazon.com, Inc.
</td>
</nowiki></pre></code>

== Existing Practices ==
* ''Summary of common patterns discovered''
* ''Other attempts to solve The Problem''
== Proposal ==
* Early drafts
* ''Link to related pages as they become available''
** -brainstorming
** - proposal
** -microformat
== See Also ==
* ''Other microformats''
* ''Normative references for tags used''

stock-symbol-examples

2007-09-22T03:25:20Z

BenWest: /* Real-World Examples */ oops. small fix

= Stock Symbols =

News services, financial sites, blogs are various other websites all refer to stocks on a regular basis. Some mentions are part of a news story while others give advice and review the stock or the company.

== The Problem ==

Formulate an unambiguous, machine parseable, representation that can be used when stocks are mentioned. This should work with hReview as it's just marking up the recommended example a bit more to make it easier for tools. (Also see # 9 in [http://microformats.org/wiki/hreview-faq hReview FAQ])

== Participants ==

* John Panzer
* Sujata Ramchandran

== Real-World Examples ==

* From Yahoo! stocks

Shares of Tractor Supply (TSCO:Nasdaq - commentary - research - Cramer's Take)

* MSN Money

The 2006 portfolio is up 12%, lead by Expeditors International of Washington (EXPD, news, msgs),
CSX (CSX, news, msgs) and Caterpillar (CAT, news, msgs), up 59%, 46% and 39%, respectively

* From Motley Fool

I made my top pick Quality Systems (Nasdaq: QSII)

* Wall Street Journal

Toyota Motor Corp. reported Wednesday a 39% rise in its fourth-quarter

* From Google Finance (the ".A" denotes class A shares)

Berkshire Hathaway Inc. (Public, NYSE:BRK.A)

* From a stock pick blog.

Today's pick is Time Warner.

* From a spam email

Golden Apple Oil and Gas, Inc. (GAPJ)
THIS ST OCK IS EXTREMELY UNDERVALUED!
GAPJ - is our NEXT HOT P ICK, which we feel is most undervalued
stock we have ever featured and should out perform all other picks.

* From a spam stock tracking site ([http://www.spamnation.info spamnation.info])

name symbol last date total
BackWeb Technologies Ltd BWEB 10.06.2006 6

* From [http://www.businessweek.com/bwdaily/dnflash/content/feb2007/db20070212_512678.htm?chan=top+news_top+news+index_businessweek+exclusives a Business Week article]

The results of each day's session ripple rapidly throughout the world economy. No sector
is untouched by energy prices: oil producers and refiners who invest billions to explore,
airlines nervous about jet-fuel prices, auto companies who must adjust models rapidly to
survive, and retailers like Wal-Mart Stores (WMT) keen to know how deeply its shoppers will
be dunned at the gas pump.

* From [http://boeing.com/companyoffices/financial/ boeing.com]
<pre><code><nowiki><h2>The Boeing Company</h2>
As of 4:07 PM ET on Sep 21
<table cellpadding="5" cellspacing="0" width="180">
<caption>Stock Quote</caption>
<tbody><tr>

<th class="brand bgltgray" scope="row" nowrap="nowrap">Last</th>
<td class="brand">102.59</td>
</tr>
<tr>
<th class="brand bgltgray" scope="row" nowrap="nowrap">Change</th>
<td class="brand">+ 1.34</td>
</tr>

<tr>
<th class="brand bgltgray" scope="row" nowrap="nowrap">% Change</th>
<td class="brand"><img src="http://www.shareholder.com/common/images/smup.gif"> 1.32</td>
</tr>
<tr>
<th class="brand bgltgray" scope="row" nowrap="nowrap">Prev. Close</th>
<td class="brand">101.25</td>

</tr>
<tr>
<th class="brand bgltgray" scope="row" nowrap="nowrap">Open</th>
<td class="brand">102.35</td>
</tr>
<tr>
<th class="brand bgltgray" scope="row" nowrap="nowrap">Volume</th>

<td class="brand">6,614,000</td>
</tr>
<tr>
<th class="brand bgltgray" scope="row" nowrap="nowrap">Exchange</th>
<td class="brand">NYSE</td>
</nowiki></code></pre>

== Existing Practices ==
* ''Summary of common patterns discovered''
* ''Other attempts to solve The Problem''
== Proposal ==
* Early drafts
* ''Link to related pages as they become available''
** -brainstorming
** - proposal
** -microformat
== See Also ==
* ''Other microformats''
* ''Normative references for tags used''

stock-symbol-examples

2007-09-22T03:24:07Z

BenWest: /* Real-World Examples */ added an example from boeing.com

= Stock Symbols =

News services, financial sites, blogs are various other websites all refer to stocks on a regular basis. Some mentions are part of a news story while others give advice and review the stock or the company.

== The Problem ==

Formulate an unambiguous, machine parseable, representation that can be used when stocks are mentioned. This should work with hReview as it's just marking up the recommended example a bit more to make it easier for tools. (Also see # 9 in [http://microformats.org/wiki/hreview-faq hReview FAQ])

== Participants ==

* John Panzer
* Sujata Ramchandran

== Real-World Examples ==

* From Yahoo! stocks

Shares of Tractor Supply (TSCO:Nasdaq - commentary - research - Cramer's Take)

* MSN Money

The 2006 portfolio is up 12%, lead by Expeditors International of Washington (EXPD, news, msgs),
CSX (CSX, news, msgs) and Caterpillar (CAT, news, msgs), up 59%, 46% and 39%, respectively

* From Motley Fool

I made my top pick Quality Systems (Nasdaq: QSII)

* Wall Street Journal

Toyota Motor Corp. reported Wednesday a 39% rise in its fourth-quarter

* From Google Finance (the ".A" denotes class A shares)

Berkshire Hathaway Inc. (Public, NYSE:BRK.A)

* From a stock pick blog.

Today's pick is Time Warner.

* From a spam email

Golden Apple Oil and Gas, Inc. (GAPJ)
THIS ST OCK IS EXTREMELY UNDERVALUED!
GAPJ - is our NEXT HOT P ICK, which we feel is most undervalued
stock we have ever featured and should out perform all other picks.

* From a spam stock tracking site ([http://www.spamnation.info spamnation.info])

name symbol last date total
BackWeb Technologies Ltd BWEB 10.06.2006 6

* From [http://www.businessweek.com/bwdaily/dnflash/content/feb2007/db20070212_512678.htm?chan=top+news_top+news+index_businessweek+exclusives a Business Week article]

The results of each day's session ripple rapidly throughout the world economy. No sector
is untouched by energy prices: oil producers and refiners who invest billions to explore,
airlines nervous about jet-fuel prices, auto companies who must adjust models rapidly to
survive, and retailers like Wal-Mart Stores (WMT) keen to know how deeply its shoppers will
be dunned at the gas pump.

* From [http://boeing.com/companyoffices/financial/ boeing.com]
<pre><nowiki><code><h2>The Boeing Company</h2>
As of 4:07 PM ET on Sep 21
<table cellpadding="5" cellspacing="0" width="180">
<caption>Stock Quote</caption>
<tbody><tr>

<th class="brand bgltgray" scope="row" nowrap="nowrap">Last</th>
<td class="brand">102.59</td>
</tr>
<tr>
<th class="brand bgltgray" scope="row" nowrap="nowrap">Change</th>
<td class="brand">+ 1.34</td>
</tr>

<tr>
<th class="brand bgltgray" scope="row" nowrap="nowrap">% Change</th>
<td class="brand"><img src="http://www.shareholder.com/common/images/smup.gif"> 1.32</td>
</tr>
<tr>
<th class="brand bgltgray" scope="row" nowrap="nowrap">Prev. Close</th>
<td class="brand">101.25</td>

</tr>
<tr>
<th class="brand bgltgray" scope="row" nowrap="nowrap">Open</th>
<td class="brand">102.35</td>
</tr>
<tr>
<th class="brand bgltgray" scope="row" nowrap="nowrap">Volume</th>

<td class="brand">6,614,000</td>
</tr>
<tr>
<th class="brand bgltgray" scope="row" nowrap="nowrap">Exchange</th>
<td class="brand">NYSE</td>
</nowiki></pre>

== Existing Practices ==
* ''Summary of common patterns discovered''
* ''Other attempts to solve The Problem''
== Proposal ==
* Early drafts
* ''Link to related pages as they become available''
** -brainstorming
** - proposal
** -microformat
== See Also ==
* ''Other microformats''
* ''Normative references for tags used''

User:BenWest

2007-07-16T21:07:27Z

BenWest: adding public-domain-release.

=== What is this? ===
Ben West's uF page.

=== What can I do here? ===
Praise or flame me. Also add ideas.

* See if you can add hCard to the Alexa pages for "Related Info", e.g.
** http://www.alexa.com/data/details?url=alexa.com/
** http://www.alexa.com/data/details?url=w3.org/

=== What are you interested in? ===
Improving everything from creators, things I call deductive interfaces, sem web stuff, advocacy of microformats and its principles, and improvement of the wiki.

=== See Also ===
* [[to-do]]
* [[wiki-feedback]]

{{public-domain-release}}

xhtml-syndication

2007-06-18T21:12:06Z

BenWest: Reverted edit of Xk7X37, changed back to last version by RyanKing

= XHTML Syndication History =

The idea of using XHTML syndication is by no means new.

When the idea first started coming up on the [http://microformats.org/discuss/ microformats-discuss] list, it sounded like a new, novel idea. It's not. Of course, I ([[User:RyanKing|Ryan King]] wasn't a citizen of [http://en.wikipedia.org/wiki/Blogosphere Blogistan] when it had been discussed before, so I decided to do some research. Here's a brief history of the idea:

Mark Pilgrim accurately [http://diveintomark.org/archives/2002/11/26/syndication_is_not_publication asserts] that "Every few months, somebody floats the idea of doing away with RSS and replacing it with HTML or XHTML, 'because semantic markup is all we need'."

Apparently he was right, because the topic keeps coming up.

Mark also says:

<blockquote>
I’ve talked about application posture before; it seems to me that this latest movement adopts the wrong posture. The entire success of RSS is predicated on the principle that you can keep doing whatever messed up stuff you’ve always done on your web pages… oh, and do this other thing too. Look, it’s simple, you can code it up in an hour with a few print statements and an escape function. By contrast, this latest XHTML-as-syndication movement seems to be based on the principle that syndication is so incredibly important that you must immediately stop whatever you’re doing with your web pages, upgrade to XHTML, validate your markup, restructure your home page to include all and only the content you’re willing to syndicate, and by the way, would you please unlearn that ugly nasty presentational page layout language you’ve been using for years and learn this wonderful happy structured semantic markup language instead?
</blockquote>
In response, in seems that people are already *unlearning their crappy presentational markup shit.* Could it be that, given the move towards a separation of presentation and structure, we may now be able to create a syndication format in XHTML (at least for blogs)?

--[[User:RyanKing|RyanKing]] 14:34, 27 Oct 2005 (PDT)

== Work in Progress ==
This document is a work in progress. If you'd like to contribute, feel free to take one of the links from the Queue at the bottom of the page, analyze it, write a short summary of the proposal and record any issues in the "Issues Raised" section.

Reference: [http://diveintomark.org/archives/2002/11/26/syndication_is_not_publication]

== Issues Raised ==
This section is for documenting issues raised in earlier efforts at using XHTML as a syndication format.

* How do we represent dates in XHTML? (see above) [http://diveintomark.org/archives/2002/11/26/syndication_is_not_publication]
* Requiring specific structural elements doesn't make sense [http://www.scottandrew.com/blog/archives/2002/11/semantic_overloading.html]

== Proposed Profiles, etc ==
=== Site Summaries in XHTML ===
[http://w3.org/People/DanC Dan Connoly] of the [http://w3.org W3C] has a "Site Summaries in XHTML" to express RDF 1.0 channels in XHTML.

http://www.w3.org/2000/08/w3c-synd/

A boiled down, loose interpretation of the spec:

* the title of the channel is taken from the title of the page
* each <code><div class="item"></code> on the page indicates an RSS item
** each such div element should contain an h2 or h3 element; this serves as the item's title.
** it should also contain a p element that serves as the item's description.
**the p element should contain an <code><a rel="details" href="...ref...">...</a></code> which is taken as the URI of the item.
**the div should contain some element with <code>class="date"</code>; its content should be a date in DD Month YYYY format; this is taken as the Dublin Core date of the item.

=== XHTML Syndication Module ===
19 July 2002
Joe Gregorio published an XHTML Syndication Module.

<blockquote>
The motivation for this document is to do away with RSS as a seperate file format. If web publishers and CMSs want to participate in content syndication then they have to produce two versions of their front page, the HTML version and the RSS version. A careful inspection of XHTML and common web practice shows that most of the information need to do syndication already exists in web pages published today. What is needed is a little extra information to make syndication possible.
</blockquote>
Its done by way of an xml namespace which adds attributes to the XHTML. Example:

<blockquote><pre><nowiki>
<div class="singleItem" syn:item="">
<h4><a syn:title="" syn:link="href" href="http://bitworking.org/2002/07/18.html#a245"
class="weblogItemTitle">Bye-bye BurningBird</a></h4>

Hard to believe but <a href="http://weblog.burningbird.net/archives/000370.php">BurningBird</a>
is closing down her blog. Best of wishes Shelly.
<div class="singleItemFooter">
12:21:21 AM
<a href="2002/07/18.html#a245">#</a>
&nbsp;&nbsp;

</div>
</div>
</nowiki></pre></blockquote>
Reference: [http://bitworking.org/XHTML-Syndication-20020719.html]

=== RSS: XHTML Profile ===
Aaron Swartz has an XHTML profile. Description:

<blockquote>
* the value of the <title> is the title of your site
* (optional)the element with class="description" contains a short description
* each element with class="item" on your page is an item, inside which:
** the element with class="title" is the item's title
** everything else is the content of the item
** the link with rel="bookmark" is the URI of the item
** (optional) the element with class="date" is the date
</blockquote>

Reference: [http://www.aaronsw.com/2002/rssXP]

== Discussion ==
This section is for collecting links to stuff that discusses the idea of using XHTML for syndication. Personally, I'm most interested in proposals/ideas that *didn't* take off. I want to learn from previous mistakes. Feel free to add to this list, with a summary, if you'd like. --[[User:RyanKing|RyanKing]] 14:34, 27 Oct 2005 (PDT)

* http://www.dashes.com/anil/2002/11/22/syndication_for
* http://www.actsofvolition.com/archives/2002/march/blogmltheweblog
* http://weblog.burningbird.net/archives/2002/11/26/rss-push-back
* http://www.intertwingly.net/blog/977.html

= Queue =
Since this document is a work in progress, this section is simply a list of links which need to be covered.
* http://ln.hixie.ch/?start=1038263537&count=1
* http://www.aaronsw.com/weblog/000738
* http://www.kryogenix.org/days/2002/11/24/instead
* http://tantek.com/log/2002/11.html#L20021124t1454
* http://tantek.com/log/2002/11.html#L20021124t0620
* http://www.scottandrew.com/weblog/2002_11#a000469
* http://bitworking.org/2002/07/19.html#a251
* http://bitworking.org/2002/07/15.html#a244
* http://diveintomark.org/archives/2002/11/26/the_rebellion_will_be_syndicated
* http://diveintomark.org/archives/2002/11/26#syndication_is_not_publication
* http://www.yetanothercommunitysystem.com/yacs/articles/view.php/438
* http://diveintomark.org/archives/2002/11/26/syndication_is_not_publication
* http://www.dellah.com/orient/2002/11/26/the-xhtml-syndication-debate
* http://nilesh.org/weblog/2002/11/xhtml-syndication/
* http://dannyayers.com/archives/2003/04/30/xhtml-syndication-module/
* http://dannyayers.com/archives/2005/08/27/hatom-no-seriously/
* http://www.dashes.com/anil/2002/11/22/syndication_for

(tidy me ;-)
Dan Brickley, comment at http://dannyayers.com/archives/2005/11/26/history/ :
Eric van der Vlist had an implementation of this back in 2000 http://groups.yahoo.com/group/XHTML-L/message/683. We made a version available on the ILRT site http://www.ilrt.bris.ac.uk/discovery/2000/08/hss/sw.html, which fed into the more widely used W3C version http://www.w3.org/2000/08/w3c-synd/ of this idea. I still think this is the way to go, ultimately. The use cases just aren’t different enough to justify having completely different document formats, solely on basis of their dissemination mechanism. But I tried raising this in early Atom days and got told it was a silly idea. Maybe as the XML doc formats mature (XHTML2, CDF) it’ll be time to revisit again.

to-do

2007-04-09T21:41:32Z

BenWest: /* Ben West (bewest) */ add an interest in quantitative analysis wrt deployment issues

<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
# 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 ===
* (: [[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.

==== foldup cheatsheet ====

Help create a printable foldup cheatsheet of multiple microformats (hopefully in time for the [[events/2006-03-12-sxsw-growth-evolution-of|SXSW microformats session]]) 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 ====
* 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])

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

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

==== [[rel-tag]] ====
* Write [[rel-tag]] XMDP profile ([[rel-tag-profile]]) and send to [http://dbaron.org/ David Baron].

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

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

=== 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
* 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 "+1 Your Name")

<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: (hAtom2xyz.xsl)
* RSS 2.0 (meanwhile use hAtom2Atom.xsl and [http://atom.geekhood.net/ atom2rss.xsl]) -- +1 Matt Dertinger
* RSS 1.0 (meanwhile use hAtom2Atom.xsl and [http://cvs.4suite.org/viewcvs/uogbuji/atom2rss.xslt atom2rss.xslt]) -- +1 Matt Dertinger
* AtomOWL (meanwhile use hAtom2Atom.xsl and [http://dannyayers.com/2005/11/22/atomowl-xslt-progress/ atom2rdfxml.xsl])-- +1 Matt Dertinger
* 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 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: (hAtom2xyz.xsl)
* RSS 2.0 (meanwhile use hAtom2Atom.xsl and [http://atom.geekhood.net/ atom2rss.xsl])
* RSS 1.0 (meanwhile use hAtom2Atom.xsl and [http://cvs.4suite.org/viewcvs/uogbuji/atom2rss.xslt atom2rss.xslt])
* AtomOWL (meanwhile use hAtom2Atom.xsl and [http://dannyayers.com/2005/11/22/atomowl-xslt-progress/ atom2rdfxml.xsl])
</li>
</ul>

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

== Nick Drago (Drago516) ==

[[User:Drago516]]

* work on [[operating-hours]] and [[operating-hours-examples]]

citation

2007-04-09T00:34:23Z

BenWest: added link to issues page in see also section.

<h1> Citation microformat efforts </h1>

This wiki page outlines the overall effort to develop a citation microformat. We are documenting current examples of [http://en.wikipedia.org/wiki/Citation cites/citations] on the web today, their implicit/explicit schemas, and current cite/citation formats, with the intent of deriving a cite microformat from that research.

__TOC__

== Authors ==
* [http://tantek.com/ Tantek Çelik]
* [http://suda.co.uk/ Brian Suda]
* [http://www.inkdroid.org Ed Summers]

== Copyright ==
{{MicroFormatCopyrightStatement2004}}

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

== Example Citations ==
[[citation-examples|Citation Examples]] are citations found in the wild that could benefit from semantic mark-up. This is a growing list of examples from all sorts of places including W3C specifications, RFCs and others. These are the examples which will determine the schema for the citation microformat.

== Known Citation Formats ==
The [[citation-formats|Citation Formats Page]] will be a running tab of known formats for publishing citations.

Eventually, i would like to see a chart of how each value from the implicit schema determined by the [[citation-examples]] is represented in each format, and what formats have additional properties that do not map between them. (For example, Format1 calls 'author' 'author', in format2 'author' is called 'writer'. etc)

== Issues ==
The [[citation-issues]] page is intended to capture ongoing issues.

== To Do ==
* [[existing-classes|Using existing class names]] and creating new names, create property names for the profile
* Based on implicit schemas in [[citation-examples]], and terms from one or more [[citation-formats]], do some [[citation-brainstorming]] for a simple citation microformat.
* Create additional strawman proposals

== Modularity ==
My hope for this microformat is that it can be a sort of module that can be used in other microformats. Once this is developed and flushed out, citation references could easily be used for publications on a Resume/CV, therefore the citation microformat would be a module (subset) of all the possible Resume Values.

Other Microformats that could use the Citation Module
* [[hresume|hResume]]
* [[work-of-art]]

Other Microformats that the Citation Module will use
* [[hcard|hCard]] encodings for things like Author, Publisher (people and companies)
* [[hatom|hAtom]] encodings as a possible container, and author/date-time properties
* [[rel-tag]] encoding for keywords
* [[rel-license]] encoding for copyright

== References ==
=== Informative References ===
* [http://ocoins.info/ COinS]
* [http://xmlresume.sourceforge.net/ XMLResume]: if part of the drive for citations is for publications for a resume/CV then some of this information could be useful
* [http://www.citeulike.org/ CiteUlike] is a free service to help academics to share, store, and organise the academic papers they are reading
* [http://www.connotea.org/ Connotea] is a scientific bookmarking service from Nature.
* [http://www.ariadne.ac.uk/issue43/chudnov/ OpenURL] with Autodiscovery
* [http://cipolo.med.yale.edu/mailman/listinfo/gcs-pcs-list "Gather, Create, Share" and "Personal Collection Systems" memes, and systems implementing either or both]
* [http://www.loc.gov/standards/mods/ Metadata Object Description Schema] developed by the Library of Congress
* [http://www.dublincore.org/documents/dc-citation-guidelines/ Guidelines for Encoding Bibliographic Citation Information in Dublin Core Metadata]
* [http://www.ecst.csuchico.edu/~jacobsd/bib/formats/bibtex.html BibTeX reference] from Dana Jacobsen
* [http://www.refman.com/support/risformat_intro.asp RIS Format Specification] from Thomson ResearchSoft, makers of ReferenceManager
* [http://www.zotero.org/ Zotero] - "Firefox extension to help you collect, manage, and cite your research sources"
*[http://www.doi.org/ DOI] ([http://www.crossref.org/02publishers/guidelines.html CrossRef Guidelines] for use of DOIs in citations)
* [http://info-uri.info/ INFO URI] (URI scheme for representing legacy namespaces)
*[http://www.isbn-international.org/ ISBN] ([http://en.wikipedia.org/wiki/International_Standard_Book_Number ISBN on Wikipedia])
*[http://www.issn.org/ ISSN] ([http://en.wikipedia.org/wiki/International_Standard_Serial_Number ISSN on Wikipedia])
* [http://opcit.eprints.org/ Open Citation Project] - OpCit, a three year (1999-2002)R&D project funded by the Joint NSF - JISC International Digital Libraries Research Programme.

== See Also ==
* [[citation-examples]]
* [[citation-examples-markup]]
* [[citation-formats]]
* [[citation-brainstorming]]
* [[citation-faq]]
* [[citation-issues]]

citation-issues

2007-04-09T00:30:14Z

BenWest: added Brian Suda's outstanding issues from brainstorming page.

BenWest will start this by reorganizing material from http://microformats.org/wiki?title=citation-brainstorming&diff=0&oldid=15286.

__TOC__

== Issues ==

* Generally, use cases are used to flesh out requirements, but I don't see any on this page, so I've added a new section for this. Here are some suggested requirements. [[ThomasBreuel]]
*I've made these into issues. [[[[User:BenWest|BenWest]] 16:56, 8 Apr 2007 (PDT)]]

* {{OpenIssue}}
===Lossless Round-Trip Conversions===
'''Should citation support roundtrip conversions? Which formats should be supported?'''
One of the primary uses for a citation format is to permit people to put individual citations or entire bibliographies on the web. For that purpose, it's important that if someone puts up my bibliography on the web and someone else downloads it, they actually get back the citations correctly, and don't have to spend time fixing up the citations manually. Therefore, I suggest the following requirement.

''If X is one of the common citation formats (BibTeX, EndNote, etc.), then conversion of the form X -> hCitation -> X must not lose information and must not require manual fixing up of the result.''

Note that this has multiple components. First, for a format like BibTeX, it's important that the field names be preserved. Second, in general, markup (italics, math, chemical formulas, spacing, special characters) needs to be preserved.

* {{OpenIssue}}
===Citation Markup=== '''Should citations preserve presentation?'''
Citations may contain markup, such as italics, subscripts, superscripts, special characters, and chemical formulas. For a correct presentation of the citation format to the user, the format must permit even fairly complex markup. Note that this markup cannot easily be converted automatically between different bibliographic processors.

* {{OpenIssue}}
===Encapsulation of Non-Textual Content=== '''Should citations support non-textual content?'''
Systems like document image processors need to be able to represent semantic roles of parts of pages without actually giving a usable textual representation. For example, a system might segment citations into authors, titles, volumes, and years, but represent the actual content of those fields using image tokens rather than characters. Furthermore, no text to put into an ABBR tag may be available

* {{OpenIssue}}
===No New Semantics=== '''Should citations avoid introducing new semantics?'''
The proposals for a citation microformat, as they now stand, suggest creating a new format that differs from existing formats not just syntactically, but semantically (different choices of field types than other formats, different handling of proper names, different handling of publications that are part of collections, etc.). This has some serious consequences; in particular, it means that translation into any existing format is not just a simple syntactic transformation, it requires that an tools that deals with the citation microformat needs to be updated to handle new semantics, in addition to new syntax. An alternative is to define one or more microformats that are strictly a syntactic transformation of existing formats (e.g., encapsulated BibTeX, encapsulated Endnote).

So, a possible requirement to consider is that citation microformats introduce no new semantics, but are a strict syntactic encapsulation of existing citation formats.

* {{OpenIssue}}
===Convert citation formats===
'''Should a user agent provide retransmission of a citation in a new format? Which ones?'''
A user agent should be capable of reading a citation from a web page, in a given format, and converting it into a second format, for use elsewhere. For a list of such formats, and examples, see [http://en.wikipedia.org/wiki/Citation#Format_styles Wikipedia, Citation styles]. [[User:AndyMabbett|Andy Mabbett]] 11:05, 30 Mar 2007 (PDT)

== Outstanding Issues ==
Moved from [[citation-brainstorming]] by [[[[User:BenWest|BenWest]] 17:30, 8 Apr 2007 (PDT)]] available at http://microformats.org/wiki?title=citation-brainstorming&diff=0&oldid=15305

The 3 main points i (Brian) came across so far are:
1) IDENTIFIERS
2) FORMAT TYPES
3) NESTING

* {{OpenIssue}} '''How should different kinds of non-globally unique identifiers be represented?'''
1) In hCard/hCalendar there is a UID field. Added with URL it makes for a great unique identifier. There are loads of other identifers besides URL, ISBN, LOC call number, SKU, ISSN, etc. Many of these are unique in their domain, but not globally unique. So how to they get marked-up? Much like the hCard TEL/ADR properties, we can use something like:
<pre>
<nowiki>
<div class="uid">ISBN: 123456</div>
</nowiki>
</pre>
This makes the encoding the most extensible... if we start use class="isbn" then it is an enumerated list, with class="type" it is open ended.

* {{OpenIssue}} '''What vocabulary should be used to distinguish between medium (aka format) versus type of work. How do we resolve ambiguity between type of work and the publishing medium?'''
2) I keep mis-using "format", format is the medium - hardback, softback. The TYPE (there probably is a better word - container?) is book, article, conference, manifesto, etc. Much like the identifers we can make an enumerated list of values, class="book", class="article", but that boxes us in, whereas something like: <pre><nowiki>article</nowiki></pre> leaves things more open.

* {{OpenIssue}} '''Should citations support nesting?'''
3) Nesting citation data in a citation. The ability to nest the same microformat inside itself is something that other microformats don't explicitly handle.

The two options are:
i) Using class="book"
<pre>
<nowiki>
<div class="hcite">
<div class="book">
Book Title
<div class="chapter">
Chapter Title
</div>
</div>
</div>
</nowiki>
</pre>

This makes things easy to nest and to figure out exactly what is
associated with what, but the downside is that we have enumerated
lists of values for the class properties.

ii) using the TYPE for book
<pre>
<nowiki>
<div class="hcite">
<div class="type">book</div>
Book Title
<div class="type">chapter</div>
Chapter Title
</div>
</nowiki>
</pre>

now the class="fn" is not nested inside the class="book" or
class="chapter" so there would have to be some other mechanism to
associate the data with the type.

citation-brainstorming

2007-04-09T00:29:42Z

BenWest: /* Outstanding Issues */ moved brian suda's outstanding issues to the issues page.

<h1> Citation Brainstorming </h1>

== See also ==
* [[citation]]
* [[citation-examples]]
* [[citation-formats]]
* [[citation-faq]]
* [[citation-issues]]

__TOC__

== Contributors ==

* ...
* ... (a bunch of good folks!)
* Tantek Çelik
* Tim White
* Michael McCracken
* Brian Suda
* [[User:AndyMabbett|Andy Mabbett]]

== Use Cases ==

To focus the discussion, please add use cases below that will help show what problems the citation microformat will be solving.

I've included two, focusing on consuming information - I've assumed that use cases for generating microformatted content would just involve the desire to enable your content to be consumed better, but I'm interested to see if there's something I'm missing here -Mike

=== Acquiring reference information from the web ===

A user either finds an author's papers page, or is viewing the results of a search and would like to import the information about the displayed papers into their local reference database, for the purposes of cataloging things they've read, adding notes, and using the information to generate later citations, potentially in other forms, such as BibTeX or Docbook, for inclusion in a publication of their own.

Notes: In this case, it isn't important to the user what format the citation takes as displayed on the page where they find it. What *is* important is that it contains enough information to allow generation of the format they will ultimately re-publish it in. This implies that it may be worthwhile to err a little on the side of verbosity.

Also, links to downloadable full representations of the cited work are very important - e.g. a link to the PDF of a journal article, or to a music file.

=== Subscribing to reading lists, periodicals, etc ===

I would like to be able to leverage my news aggregator with hAtom to subscribe to a remote source for citation information, for example:

* a reading list for a seminar
* The publication list for a conference (e.g., subscribe to SIGGRAPH and see the updated conference proceedings every year)
* the issues of a journal
* a particular research group or researcher's publications
* Not just research: a popular author's publications (e.g., [http://www.gladwell.com/archive.html Malcolm Gladwell's Archive])

=== Aggregating reading lists and reviews ===

A citation microformat-specific aggregator could provide a decentralized version of [http://citeulike.org/ CiteULike]. Libraries, authors, research groups, and publishers could mark up their collections, while other people on weblogs or review sites could add tags and reviews.

At least, having a well-adopted microformat would make writing tools like CiteULike much better, since it relies in some cases on screen-scraping publisher web-sites.

=== Cut & Paste from web pages ===
Capturing/copying HTML from web pages for use in other applications (especially when those apps present HTML as output), such as pasting into Word, or a specialized application like [http://www.google.com/notebook Google Notebook], [http://onfolio.com Onfolio] or [http://www.kaboodle.com Kaboodle]. When such captures are made, it makes sense to keep track of the full citation data, including the date it was accessed, which may or may not be the date it was published.

=== Blogs quoting other resources, including blogs ===
Any blog that cites online content, whether a blog or news article, could use an hCitation to properly link to the cited reference. Such citations could include the access date when the blogger made the citation, because resources on the other side of those links can change without notice.

Instead, today we have simple formating with a link to the permaURL. The citation data is completely lacking. See [http://doc.weblogs.com Doc Searl's blog] for a style of referencing that could benefit from proper a citation uF.

Fascinating... after I added the last two use cases, I realized they focus on potentially marginal cases. The first because it is missing the "output" part of the cut & paste, where the uF would actually be used as part of the paste. The latter because bloggers have a working citation mechanism that is just a link to the URL (hopefully a permaURL). One could argue they wouldn't want a full hCitation. And in fact, until a tool exists that makes it easy, they probably won't. However, a tool that cuts & pastes from anywhere on the web into a blog with a full citation seems like a nice tool. But again, I'm not really paving the cowpaths with these ideas. -Joe Andrieu

===Finding in Library===
Find a copy of the cited work in a nearby library (as with [http://ocoins.info/ OpenCOinS]). [[User:AndyMabbett|AndyMabbett]] 04:55, 4 Nov 2006 (PST)

===Buy a copy===
Find the cited work on, for example, Amazon or [http://www.abebooks.com/ ABE]; or subscribe to a journal via its own website. [[User:AndyMabbett|AndyMabbett]] 04:55, 4 Nov 2006 (PST)

===Find reviews===
Find third-party reviews of the cited work. [[User:AndyMabbett|AndyMabbett]] 04:55, 4 Nov 2006 (PST)

===Give citation data for the page being visited===

Adding a class of, say, "self" to an attribute of the proposed strawman would allow users (or user agents) to extract the data required to cite the page being visited, when referring to it elsewhere. There would be the added advantage of allowing the citation to be ignored by any parser which might be building a "tree" of citations, and preventing the setting up of an infinite loop.

For evidence of published "self citation" data (albeit on a secondary page) see the "cite this article" link on any Wikipedia entry, e.g. [http://en.wikipedia.org/w/index.php?title=Special:Cite&page=West_Midland_Bird_Club&id=115894372] from [http://en.wikipedia.org/wiki/West_Midland_Bird_Club].

See also [http://en.wikipedia.org/wiki/Wikipedia_talk:Citing_Wikipedia#Citation_data_should_be_on_the_page_concerned Proposal to include on-page citation data in Wikipedia]

:[[User:AndyMabbett|Andy Mabbett]] 13:47, 20 Mar 2007 (PDT)

==Examples==
* (from a mailing list):
:<blockquote>if you want to cite a [biomedical journal] journal article on Wikipedia [...] you can export a correctly-formatted citation for Wikipedia from HubMed using unAPI... http://hublog.hubmed.org/archives/001408.html</blockquote>

*[http://www.zotero.org/ Zotero], a Firefox extension to help collect, manage, and cite research sources.
:[[User:AndyMabbett|Andy Mabbett]] 09:13, 21 Mar 2007 (PDT)

== Original hBib Discussion ==

During the WWW2005 Developer's Day [[microformats]] track, Rohit Khare gave a [[presentations|presentation]] where he discussed the microformats [[process]], and then did a quick demonstration wherein a bunch of us got on a shared Subethaedit document, and brainstormed some thoughts on what an "hBib" bibliography citation microformat would look like. Rohit placed the [http://cnlabs.commerce.net/~rohit/hBib%20Discussion.html document on his Commercenet site].

* http://cnlabs.commerce.net/~rohit/hBib%20Discussion.html

''An attempt to summarize and inline the linked document follows. -Mike''

Two major goals were outlined by the group:

* Avoid re-keying references
* Adapt to new journal styles by changing CSS

The fundamental problem was discussed in terms of display - the ability to transform XHTML+hBib into the many journal-specific formats. For example, how to display "et.al" when all authors are present in the source, and how to re-order the elements if a style defines a set order of elements that conflicts with the ordering in the source. Using hCard for authors was agreed on, and the beginnings of an example were shown.

== XHTML Structure ==
With my exprience working X2V and hCa* has taught me what elememts are easy to find and which are not. Since the Citation microformat is very new it is possible to not make a lot of the same errors twice and to make things easier for extracting application to find and imply certain properties.

* There should be some sort of 'root node' that implies all child elements are for the hCitation microformat.
* Since most people will have multiple citations there should be away to represent each hCitation object as a unqiue block independent of another. This is to keep the parse from finding 'author' and applying that to all citations. Each citation should be in a container (class="hcite") that is separated from others.
* Perhaps class="hcite" with <code><cite></code> recommended as the root element. E.g. <code><cite class="hcite"></code>

'''Note: This section was the original content of the document. Since then, class='hcite' has been agreed on as the root class name. See [http://microformats.org/wiki?title=citation-brainstorming#.27hcite.27_as_Root_Element_name explanation].'''

== Citation vs. [[media-info]] ==

What distinguishes a cite from say [[media-info]] (e.g. [[media-info-examples]]) is that a cite is a reference to something explicitly external to the current piece of content or document, whereas [[media-info]] describes information about content embedded or inline in the current document.

== Semantic Meaning ==
One of the guiding priniciple of Microformats is to use the most semantically rich element to describe each node (Point 2 of Semantic XHTML Design Principles: Use the most accurately precise semantic XHTML building block for each object etc). Since we are dealing with HTML and citations, several elements are candidates to be used to enrich the semantic meaning. [http://www.w3.org/TR/REC-html40/struct/text.html CITE, BLOCKQUOTE, Q, A], (are there more?)

The [[citation-brainstorming|Citation Brainstorming Page]] has a few development and ideas about how to give another person credit for a link. Some of the semantic ideas behind their choices of tags can be applied to a full bibliographic type reference. ''Does this sentence make sense only historically? -Mike''

== OCLC's WorldCat for titles ==
Question: what about using something like OCLC's [http://www.oclc.org/worldcat/open/isbnissnlinking/default.htm WorldCat] for linking titles? - Tim White

== This and That ==
After reading through alot of different citation encoding formats, i noticed that each format was being used in onw of two ways. It was either to describe the Current page (THIS.PAGE) or being used to encode references that point to external resources (THAT.PAGE)

The informatation being encoded was identical for both resources (author, date, name, etc) they just reference different things. For this microformat, i'm not sure if we want to try to solve both problems, or just one? The meta tags in the head element would be the ideal place for information about the THIS.PAGE, but that is not in following with the ideals of microformats where information is human-readable. The THAT.PAGE idea where a list of references is at the end of a document in the form of a bibliography is more inline with the ideals of a microformat where the data is human-readable. That doesn't mean that data about the current document shouldn't be human-readable, so some of the same properties used to reference extermal resources can be used for the current document (THIS.PAGE). To do this a different root item could be used and transforming applications could either extract the citation data about the current page, or information about this page's references.

This is open for discussion, but either way, i believe that the properties used to describe a page will be the same for both THIS and THAT. [http://suda.co.uk/ brian suda]

== More on This and That ==

Citation microformats are being explored as a possibility for citing genealogical information at [http://eatslikeahuman.blogspot.com Dan Lawyer's blog].

This is a case where frequently the citation would refer to (THIS.PAGE), but would have nested within it a reference to (THAT.PAGE), possibly a few levels deep. For instance, a web page might contain data extracted from a microfilm of a census. The citation would need to include information about the web page, information about the microfilm, and information about the census. Genealogical citations are expected to include the repository (where can this book or microfilm be found. Is this the same as ''venue''?). So, at each level the information should contain the repository of the referenced item. A nesting (recursive) mechanism for citation microformats would be useful in this case. Is this the function of the "container" element in the Straw Format?

== Date Formatting ==
Since microformats are all about re-use and the accepted way to encode Date-Time has been pretty much settled, then this is a good place to start when dealing with all the different date citation types.

These are all the different fields from various citation formats that are of temporal nature:
* Date (available | created | dateAccepted | dateCopyrighted | dateSubmitted | issued | modified | valid)
* originInfo/dateIssued
* originInfo/dateCreated
* originInfo/dateCaptured
* originInfo/dateOther
* month
* year
* Copyright Year
* Date - Generic
* Date of Confernce
* Date of Publication
* Date of update/revisou/issuance of database record
* Former Date
* Entry Date for Database Record
* Database Update
* Year of Publication

There are several common properties across several citation domains and will certainly be in the citation microformat, the unique instances will need further consideration, otherwise there could be no end to posiblities.

There are also several properties (year, month, Year of publication) that can be extracted from another source. Therefore, if you only encode a more specific property such as; Date of Publication, you can extract the 'year of publication' from that. Since the date-time format we are modeling after is the ISO date-time format, just the Year portion is an acceptable date. So if you ONLY know the year of publication, the you can form a valid 'Date of Publication' as a microformat (which inturn is a valid 'year of publication') - you milage may vary when it comes to importing into citation applications.

...

It seems to me that these can be collapsed to maybe one or two different date properties. As far as the specific human readable formatting of the date, that can be chosen per whatever the presentation style guide says, and the [[datetime-design-pattern]] used to simplify the markup. - Tantek

'''Important'''
Sometimes we need a date range and not simply a date (e.g. 4-6 May 2006). See ''Conference Citation'' examples later on this page. - Discoleo

'''Seasons'''
Some journals have seasonal issues (e.g. "Summer 2006 edition") instead of, or as well as, editions labelled by month or other calendar-date. [[User:AndyMabbett|AndyMabbett]] 05:05, 4 Nov 2006 (PST)

== Tags ==
Some of the citation formats has a place for 'keywords' or 'generic tags', etc. This might be a good place to re-use the [http://microformats.org/wiki/rel-tag RelTag microformat]. The downside would be that they are then forced to be links, which might be the correct way to mark-up these terms.

== MARC / MODS / Dublin Core ==

The MODS ([http://www.loc.gov/standards/marcxml/Sandburg/sandburgmods.xml example]) and Dublin Core ([http://www.loc.gov/standards/marcxml/Sandburg/sandburgdc.xml example]) transformations of MARC21 may contain some useful ideas.

Here's a first attempt at rewriting the linked examples in XHTML (written in response to a [http://microformats.org/discuss/mail/microformats-discuss/2005-December/002438.html mailing list query about encoding book information with microformats]):

<pre><nowiki>
<div class="book" lang="en">
<h3 class="fn">Arithmetic /</h3>
By Sandburg, Carl,
1878-1967,
and Rand, Ted
Publisher: Harcourt Brace Jovanovich,
San Diego
Published: 1993
A poem about numbers and their characteristics. Features
anamorphic, or distorted, drawings which can be restored to normal by viewing
from a particular angle or by viewing the image's reflection in the provided
Mylar cone.
One Mylar sheet included in pocket.
Subjects:
<ul>
<li class="subject">Arithmetic</li>
<li class="subject">Children's poetry, American.</li>
<li class="subject">Arithmetic</li>
<li class="subject">American poetry</li>
<li class="subject">Visual perception</li>
</ul>
</div>
</nowiki></pre>

== Basic Citation Stuctures ==
There are basic structures to any citation, this is an overview of some of the types
[http://www.users.muohio.edu/darcusb/misc/citations-spec.html http://www.users.muohio.edu/darcusb/misc/citations-spec.html]

== Concerns not addressed by existing formats ==

There are some aspects '''NOT adequately''' covered by existing formats. I have addressed this issue on the OpenOffice.org wiki page, too. [see http://wiki.services.openoffice.org/wiki/Bibliographic_Database for an extending discussion, the paragraph on ''Reference Types'']

These issues pertain mainly to '''Errata''', '''Comments and Authors Reply''' and '''Article Retractions'''.
* a bidirectional link could be necessary to implement these features (original article <=> eratum, reply, retraction letter)
* '''IMPORTANT: Errata'''
** Erata: one or more Corrections might be posted in various issues of the journal
** this is usually cited as: Orininal Article Citation Data (Correction available in ''Journal, Issue Nr, Year, Pages'') (repeat for more than one correction)
** it is possibly never cited alone
** there should be a link to the original article, while the original article should contain a link to this ''Errata''
* '''IMPORTANT: Commentary and Author Reply'''
** similar to Errata, there might be one or more Comments and Author Replys; this should be stored, too
** however, it is usually not included in the original citation
** it might be used however in a citation, but I do not know exaclty how to cite it optimally (original article should be provided as well)
* '''IMPORTANT: Article Retraction'''
** an article may be retracted because of plagiarism or some other flaw
** this should not be used any further in the research
** however, it might be used e.g. for an article on plagiarism or flawed research
** there should be therefore one field storing this information, too, and a link to:
** the published withdrawal letter (which explains why the article was retracted)

* this issue may need a time-controlled event
* '''IMPORTANT: electronic publishing ahead of print (EPUB)'''
** more and more articles are initially posted online, before the published article gets actually printed
** How should this be used/cited?
** Is this changed, after the print version becomes available?

== Outstanding Issues ==
Moved to [[citation-issues]] by [[[[User:BenWest|BenWest]] 17:29, 8 Apr 2007 (PDT)]].

== Brian's straw format ==

=== implied schema (examples) ===
+ publisher
+ language
+ description
+ title
+ creator
+ journal
+ volume
+ issue
+ page
+ edition
+ identifier
+ tags
+ format
+ date published
+ copyright
- audience

=== implied schema (formats) ===
+ publisher
+ language
+ description
+ title
+ creator
+ volume
+ pages
+ edition
+ issue
+ identifier
+ tags
+ format
+ date published
+ date copyrighted
- subtitle
- image
- excerpt
- index terms
- series title
- publication
- journal
- part (1 of X)

UNION of the two schemas
+ (PLUS) means common properties
- (MINUS) means unique to the schema

=== Working straw schema ===

This list records discussion about the common schema from above. The format is ''descriptive-name'' (''optional-recommended-element'' 'class-name') (''link to explanation'').

If there is no explanation link, that field should be considered either obvious or up for debate. If you're not sure which, it's up for debate.

* root element ('hcite') ([http://microformats.org/wiki?title=citation-brainstorming#.27hcite.27_as_Root_Element_name explanation])
** title ('title')
** Author / Editor etc. ('creator')
** Pages ('pages')
*** note: this can be any value
** container ('container hcite')
*** A nested hcite element that represents a containing item (like a book for a chapter) ([http://microformats.org/wiki?title=citation-brainstorming#Container discussion and link to mailing list thread])
** Volume Number ('volume')
** Edition ('edition')
** Issue number ('issue')
** Tags (href rel='tag')
** Format ('format')
*** Note - this is unclear at present - does format mean 'type', as in 'book' vs. 'article'? --[[User:Mike|Mike]] 22:53, 16 Jan 2007 (PST)
** date published ('date-published') ([http://microformats.org/wiki?title=citation-brainstorming#Date_Fields explanation])
** date accessed ('date-accessed') ([http://microformats.org/wiki?title=citation-brainstorming#Date_Fields explanation])
** publisher
** language
** Abstract / description ('description')
** URI (href class='uri') ([http://microformats.org/wiki?title=citation-brainstorming#The_URI_Element explanation])
** identifier
*** an (not necessarily globally unique) identifier, such as a cite-key, pubmed ID number, or simply the reference number or string within a publication ([1] or [CLRS2001])

==== Notes about missing / changed fields in the schema ====

This section lists fields that are intentionally ''not'' included in the straw schema, or are not represented directly, and links to discussion about each.

* date copyrighted ([http://microformats.org/wiki?title=citation-brainstorming#Date_Fields explanation])

=== Examples ===

Markup examples using the above format:

==== Book ====

This is Brian's original example

<pre>
<nowiki>
<ul class="bibliography">
<li class="hcite" xml:lang="en-gb">


<div class="creator vcard">
John Doe
...
</div>


Foobar!
World Class Book about foobar
1
1
1
1-10
article


12345678


<a class="keyword" rel="tag" href="/tags/foo">foo</a>
bar


Published <abbr class="date-published" title="20060101">January 1st 1006</abbr>
Copyright <abbr class="copyright" title="20060101">2006</abbr>
</li>
...
</ul>

Have you read <abbr title="book" class="format">Foo Bar</abbr>?
It was written by John Doe.
It only came out a <abbr class="dtpublished" title="20060101">few months ago</abbr>
</nowiki>
</pre>

Note: the "format" property above is incorrect. Format would refer more the physical characteristics of an item, rather than its type or genre (e.g. "article", "book", etc.). I'd rather have the main class for the li be "article" in this context, than the fairly meaningless "citation." Of course, one could have both, which would be fine too. -- bruce

Note: Could we use ROLE from hCard to identify editors, translators, authors, etc?
This was discussed on the mailing list and the idea was dropped [http://microformats.org/discuss/mail/microformats-discuss/2006-September/005694.html]

'''Comments''' : [[User:Singpolyma|singpolyma]] 08:03, 16 Jun 2006 (PDT) : keywords should be [[rel-tag]], and probably also [[XOXO]] (the same way the citation list is)

[[User:RCanine|RCanine]] 11:55, 18 Dec 2006 (EST) :

* Is there a reason not to re-use "published" from hAtom instead of inventing a new, basically equivalent term in "dtpublished"?
** note - date-published was decided on for the field, example changed to reflect it --[[User:Mike|Mike]] 10:12, 30 Mar 2007 (PDT)
* Missing a URL/URI/IRI/UID etc. field example (ISBN for Book).
* Does the "copyright" class conflict with [http://www.whatwg.org/specs/web-apps/current-work/#class WHATWG's definition]?
* WRT Bruce's comment, I'm currently using class="article citation" for my writing, as it has the most flexibility with CSS styles for titles (e.g. Book titles .citation>.fn must be italicized, while article titles must not, their container should).
* Speaking of containers, we need an "in" or "collection" field for journal articles or articles-in-books, or is that covered by "publisher"?

==== Citing Private Communication ====

Needs an example.

==== Citing Legal Cases ====
Needs an example.
see [http://microformats.org/wiki/citation-examples-markup#Wikipedia_Court_Case Wikipedia example] for inspiration.

==== Citing a Book ====

needs an example

==== Citing a journal article ====

From an old entry in PubMed - J Aersp Med. [http://www.ncbi.nlm.nih.gov/entrez/query.fcgi?db=pubmed&cmd=Retrieve&dopt=AbstractPlus&list_uids=4611181&query_hl=7&itool=pubmed_docsum link]

<pre><nowiki>

R R Burton,
S D Leverett, and
E D Michaelson

Man at high sustained +Gz acceleration: a review.
In 
<abbr class="type" title="Journal">J.</abbr><abbr class="title" title="Aerospace medicine">Aersp. Med.</abbr>
urn:issn:0001-9402
45
10
<abbr class="date-published" title="101974">Oct, 1974</abbr>
, pages 1115-36.



</nowiki></pre>

Note, I'm not entirely sure about the issn urn here.

==== Citing a magazine article ====

needs an example

==== Citing a Patent ====

Drawn from this [http://microformats.org/wiki/citation-examples#U.S._Patent example from Wikipedia]:

<pre><nowiki>
<li class="hcite"><a href="http://patft.uspto.gov/netacgi/nph-Parser?patentnumber=4,405,829" class="url"
title="http://patft.uspto.gov/netacgi/nph-Parser?patentnumber=4,405,829">
U.S. Patent 4,405,829</a>:
The <a href="/wiki/RSA" title="RSA">RSA</a> patent, a famous software patent on the ground-breaking
and highly unobvious algorithm for public key encryption, widely used for secure communications
in many industries nowdays
</li>
</nowiki></pre>

==== Citing a conference publication====

Based on the [http://microformats.org/wiki/citation-examples#ACM_Digital_Library_Search_Result_Examples conference publication reference example].

Changed Oct 06 to conform with [http://microformats.org/wiki/citation-brainstorming#Brian.27s_Straw_format Brian's format]. --[[User:Mike|Mike]] 18:09, 12 Oct 2006 (PDT)
(everything but the url class should be in line with that proposal)

L. Hochstein, J. Carver, F. Shull, S. Asgari, V. Basili, J. K. Hollingsworth, and M. Zelkowitz, “Hpc programmer productivity: A case study of novice hpc programmers,” in Proceedings of ACM/IEEE Supercomputing Conference, 2005.

<pre><nowiki>

Lorin Hochstein
 University of Maryland, College Park ,
 Jeff Carver 
 Mississippi State University ,
 Forrest Shull 
 Fraunhofer Center Maryland ,
 Sima Asgari
 University of Maryland, College Park ,
 Victor Basili
 Fraunhofer Center Maryland ,
 Jeffrey K. Hollingsworth
 University of Maryland, College Park , and
 Marv Zelkowitz
 University of Maryland, College Park ,

<a class="title url" href="http://dx.doi.org/10.1109/SC.2005.53">HPC Programmer Productivity: A Case Study of Novice HPC Programmers</a>.
(conference publication)

<a class="title url" href="...">Proceedings of ACM/IEEE Supercomputing Conference</a>
<abbr class="date-published" title="20051126T0000-0800">2005</abbr>

page 35

IEEE Computer Society


Washington,
DC


<a class="url eprint" href="http://portal.acm.org/...">PDF of full text from ACM</a>

DOI: <a class="url uid" href="http://dx.doi.org/10.1109/SC.2005.53">10.1109/SC.2005.53</a>
Tags:
<a class="keyword" rel="tag" href="results.cfm?query=genterm%3A%22Design%22 ...">Design</a>,
<a class="keyword" rel="tag" href="results.cfm?query=genterm%3A%22Experimentation%22 ....">Experimentation</a>,
<a class="keyword" rel="tag" href="results.cfm?query=genterm%3A%22Measurement%22...">Measurement</a>,
<a class="keyword" rel="tag" href="results.cfm?query=genterm%3A%22Performance%22 ...">Performance</a>

In developing High-Performance Computing (HPC) software, ....

</nowiki></pre>

'''Note''' (From [[Discoleo]], Sept. 06)
* sometimes, the citation must include '''Town/Country''' and '''Precise Date/Date Range''', e.g.
** ''Gillespie SH, Dickens A.'' Variation in mutation rate of quinolone resistance in Streptococcus pneumoniae [abstract P06-17A]. In: Abstracts of the 3rd International Symposium on Pneumococci and Pneumococcal Disease (Anchorage, 5-9 May 2002).Washington, DC: American Society of Microbiology, 2002.
** ''Bassetti, M.; Righi, E.; Rebesco, B.; Molinari, MP.; Costa, A.; Fasce, R.; Cruciani, M.; Bassetti, D.; Bobbio Pallavicini, F.'' 44th Annual Interscience Conference on Antimicrobial Agents and Chemotherapy (ICAAC). Washington, DC; 2004. Epidemiological trends in nosocomial candidemia in ICU: A five-year Italian perspective.
** ''Peacock JE, Wade JC, Lazarus HM, et al.'' Ciprofloxacin/piperacillin vs. tobramycin/piperacillin as empiric therapy for fever in neutropenic cancer patients, a randomized, double-blind trial [abstract 373]. In: Program and abstracts of the 37th Interscience Conference on Antimicrob Agents and Chemotherapy (Toronto). Washington, DC: American Society for Microbiology, 1997.

==== Citing an external website ====

This is based on a formal citation of a website in the references section of a research paper, but could also be used for in-line links that had added information. Here's the original:

[25] David Stern, "eprint Moderator Model", http://www.library.yale.edu/scilib/modmodexplain.html (version dated Jan 25, 1999)

<pre><nowiki>
<cite class="hcite">
<a class="fn url" href="http://www.library.yale.edu/scilib/modmodexplain.html">eprint Moderator Model</a>

<a href="http://pantheon.yale.edu/~dstern/dsbio.html" class="url fn">David Stern</a>

<abbr class="dtpublished" title="19990125T0000-0500">
Jan 25, 1999
</abbr>
</cite>
</nowiki></pre>

=== Discussion of Straw Format elements ===

This section is to provide explanations for posterity about the elements of the straw format, linking to discussions on the list and elsewhere if possible.

==== 'hcite' as Root Element name ====

This discussion took place in January of 2007, with [http://microformats.org/discuss/mail/microformats-discuss/2007-January/008098.html voting occurring on the mailing list].

It was decided to use 'hcite' as the root element's class-name for uniqueness and to reflect a trend in using 'h' to start microformat names.

==== The URI Element ====

It was decided to use URI for both http links to available copies or URNs.
This encompasses URLs that link directly to online copies as well as through resolvers using URIs such as urn:isbn: 0521890012

See the discussion from [http://microformats.org/discuss/mail/microformats-discuss/2006-November/007390.html November] and [http://microformats.org/discuss/mail/microformats-discuss/2006-December/007403.html December].

==== Date Fields ====

Brian's original straw format had three date fields, "accessed", "copyrighted", and "published".
After examining the examples of usage on the web, it was clear that 'copyrighted' was not used in the examples we have.
It was used once, but without a corresponding 'published' field (OCLC WorldCat), and it seems in that case to be used as
an equivalent to 'published'.

I updated the straw citation to include only 'accessed' and 'published' on January 31. --[[User:Mike|Mike]] 00:26, 31 Jan 2007 (PST)

I've mentioned more than once that "date-published" is misleadingly specific; too much for real world citations. Consider that many books are published in the year preceding their copyright date, which is in fact the date used for citation. I'd prefer just "date" and "date-accessed" as a first cut. --[[User:BDarcus|Bruce]] 3 Feb 2007

See the discussion from the [http://microformats.org/discuss/mail/microformats-discuss/2007-January/008175.html 'dates' thread on the list].

==== Container ====

Discussion about how to represent containing relationships is on the thread [http://microformats.org/discuss/mail/microformats-discuss/2007-March/thread.html 'nesting container elements']

== Old straw format discussion ==

Saved here so that I'm not just deleting people's comments.

=== Mike straw format suggestion (Deprecated) ===

In the interests of starting debate and having something concrete to fix, I suggest the following structure for a format. It is probably very incomplete and I claim no microformat expertise. I'm just trying to follow existing patterns. Comments and ridicule are both solicited. -Mike

'''NOTE:''' This format is here for historical reference. Because it was not based on existing examples, I've deprecated it and contributed examples to Brian's format. If you feel that any missing elements in here should be in the final format, find examples for them and contribute to Brian's schema. Thanks! --[[User:Mike|Mike]] 18:22, 12 Oct 2006 (PDT)

==== In General ====

The ''citation'' format is based on a set of fields common to many bibliographic data formats, which are often implied by standard citation display styles but not explicitly marked up in practice on the web.

==== Schema ====

The citation schema consists of the following:

* cite
** title: required, text (class = fn)
** subtitle: optional, text
** authors: optional, use hCard
** publication date: optional
** link(s) to instantiations, optional, url or use rel-enclosure? (class=url)
** UID, optional (for ISBN, DOI - use existing uid class) | permalink
** series (aka volume/issuenum) , optional (''not as sure how to handle these - suggestions?'')
** pages: startpage & endpage, optional, text
** venue, optional (hCard)
** publisher, optional (hCard)
** container: optional (nested hCite)
** abstract, optional (blockquote + class="abstract" ?)
** notes, optional (blockquote + class="notes" ?)
** keywords, optional (rel-tag)
** image, optional (for inclusion inline, unlike the url)
** copyright, optional (rel-license)
** ''what else am I missing?''
*** language, optional

''Looks good, but I question the use of hCard for names. Due to ambiguity issues, requring hCard would lead to extra markup in order to apply just a name, hence [http://microformats.org/discuss/mail/microformats-discuss/2006-March/003487.html the need for a root element]. We should extract the N optimization of hCard like we did with adr, in order to ease this problem.'' --[[User:RCanine|Ryan Cannon]]

Perhaps a Retrieved Date or Access Date would be appropriate for citing online resources. For example at http://www.crlt.umich.edu/publinks/facment_biblio.html
you see citations like this<nowiki>:</nowiki>
<blockquote>
Chief Academic Officers of the Big 12 Universities (2000). Big 12 Faculty Fellowship Program. Retrieved December 20, 2000 from the World Wide Web: http://www.k-state.edu/provost/academic/big12/big12guide.htm.
</blockquote>
--[[User:JoeAndrieu|Joe Andrieu]]

==== Discussion about citing legal cases ====

Here's some info I found about citing law:

I'm not a lawyer, so I'm relying on the published [http://www.legalbluebook.com "blue book" standard], at least the only part of it I can get without paying $25. I'd be happy to hear improvements from experts in the field - how do lawyers mark up references to case law in HTML now?

From groklaw.net and eff.org, I find mostly just links to PDFs with the name of the case as the link text. Or just this, from EFF:
<pre><nowiki>
<h1>The Betamax Case</h1>
<h2>Sony Corp. of America v. Universal City Studios, 464 U.S. 417 (1984)</h2>
</nowiki></pre>

From an example at the sample bluepages: http://www.legalbluebook.com/pdfs/bluepages.pdf
5 basic components:
*1 name of the case (citation title)
*2 published source in which case may be found (citation containing publication?)
*3 a parenthetical indicating the court and year of decision (citation venue?)
*4 other parenthetical information, if any (citation notes?)
*5 subsequent history of the case, if any (citation notes?)

Here's two examples from the bluebook. Note that there are very strict rules about abbreviations in that source!

Holland v. Donnelly, 216 F. Supp. 2d 227, 230 (S.D.N.Y. 2002), aff'd, 324 F.3d 99 (2d Cir. 2003).

Green v. Georgia, 442 U.S. 95, 97 (1979) (per curiam) (holding that exclusion of relevant evidence at sentencing hearing constitutes denial of due process).

== Examples in the wild ==
Pages which start to use the discussion above to create working examples in using hcite:
(This section could be used as a base for a page like "hcite-examples-in-wild" later).

Please add new examples to the top of this section.
* [http://www.demo.vorlagen.uni-erlangen.de/univis/mitarbeiter.shtml/georg-hager.shtml Example User Page] at the regional computer lab Erlangen, Germany, based on the universal information system UnivIS marked up with vcard, hcalender (optional, if user makes a lecture) and hcite.

== discussions ==
* [[citation-irc-notes-2006-04-09]]

citation-brainstorming

2007-04-09T00:12:25Z

BenWest: /* See also */ added a link to citation-issues

<h1> Citation Brainstorming </h1>

== See also ==
* [[citation]]
* [[citation-examples]]
* [[citation-formats]]
* [[citation-faq]]
* [[citation-issues]]

__TOC__

== Contributors ==

* ...
* ... (a bunch of good folks!)
* Tantek Çelik
* Tim White
* Michael McCracken
* Brian Suda
* [[User:AndyMabbett|Andy Mabbett]]

== Use Cases ==

To focus the discussion, please add use cases below that will help show what problems the citation microformat will be solving.

I've included two, focusing on consuming information - I've assumed that use cases for generating microformatted content would just involve the desire to enable your content to be consumed better, but I'm interested to see if there's something I'm missing here -Mike

=== Acquiring reference information from the web ===

A user either finds an author's papers page, or is viewing the results of a search and would like to import the information about the displayed papers into their local reference database, for the purposes of cataloging things they've read, adding notes, and using the information to generate later citations, potentially in other forms, such as BibTeX or Docbook, for inclusion in a publication of their own.

Notes: In this case, it isn't important to the user what format the citation takes as displayed on the page where they find it. What *is* important is that it contains enough information to allow generation of the format they will ultimately re-publish it in. This implies that it may be worthwhile to err a little on the side of verbosity.

Also, links to downloadable full representations of the cited work are very important - e.g. a link to the PDF of a journal article, or to a music file.

=== Subscribing to reading lists, periodicals, etc ===

I would like to be able to leverage my news aggregator with hAtom to subscribe to a remote source for citation information, for example:

* a reading list for a seminar
* The publication list for a conference (e.g., subscribe to SIGGRAPH and see the updated conference proceedings every year)
* the issues of a journal
* a particular research group or researcher's publications
* Not just research: a popular author's publications (e.g., [http://www.gladwell.com/archive.html Malcolm Gladwell's Archive])

=== Aggregating reading lists and reviews ===

A citation microformat-specific aggregator could provide a decentralized version of [http://citeulike.org/ CiteULike]. Libraries, authors, research groups, and publishers could mark up their collections, while other people on weblogs or review sites could add tags and reviews.

At least, having a well-adopted microformat would make writing tools like CiteULike much better, since it relies in some cases on screen-scraping publisher web-sites.

=== Cut & Paste from web pages ===
Capturing/copying HTML from web pages for use in other applications (especially when those apps present HTML as output), such as pasting into Word, or a specialized application like [http://www.google.com/notebook Google Notebook], [http://onfolio.com Onfolio] or [http://www.kaboodle.com Kaboodle]. When such captures are made, it makes sense to keep track of the full citation data, including the date it was accessed, which may or may not be the date it was published.

=== Blogs quoting other resources, including blogs ===
Any blog that cites online content, whether a blog or news article, could use an hCitation to properly link to the cited reference. Such citations could include the access date when the blogger made the citation, because resources on the other side of those links can change without notice.

Instead, today we have simple formating with a link to the permaURL. The citation data is completely lacking. See [http://doc.weblogs.com Doc Searl's blog] for a style of referencing that could benefit from proper a citation uF.

Fascinating... after I added the last two use cases, I realized they focus on potentially marginal cases. The first because it is missing the "output" part of the cut & paste, where the uF would actually be used as part of the paste. The latter because bloggers have a working citation mechanism that is just a link to the URL (hopefully a permaURL). One could argue they wouldn't want a full hCitation. And in fact, until a tool exists that makes it easy, they probably won't. However, a tool that cuts & pastes from anywhere on the web into a blog with a full citation seems like a nice tool. But again, I'm not really paving the cowpaths with these ideas. -Joe Andrieu

===Finding in Library===
Find a copy of the cited work in a nearby library (as with [http://ocoins.info/ OpenCOinS]). [[User:AndyMabbett|AndyMabbett]] 04:55, 4 Nov 2006 (PST)

===Buy a copy===
Find the cited work on, for example, Amazon or [http://www.abebooks.com/ ABE]; or subscribe to a journal via its own website. [[User:AndyMabbett|AndyMabbett]] 04:55, 4 Nov 2006 (PST)

===Find reviews===
Find third-party reviews of the cited work. [[User:AndyMabbett|AndyMabbett]] 04:55, 4 Nov 2006 (PST)

===Give citation data for the page being visited===

Adding a class of, say, "self" to an attribute of the proposed strawman would allow users (or user agents) to extract the data required to cite the page being visited, when referring to it elsewhere. There would be the added advantage of allowing the citation to be ignored by any parser which might be building a "tree" of citations, and preventing the setting up of an infinite loop.

For evidence of published "self citation" data (albeit on a secondary page) see the "cite this article" link on any Wikipedia entry, e.g. [http://en.wikipedia.org/w/index.php?title=Special:Cite&page=West_Midland_Bird_Club&id=115894372] from [http://en.wikipedia.org/wiki/West_Midland_Bird_Club].

See also [http://en.wikipedia.org/wiki/Wikipedia_talk:Citing_Wikipedia#Citation_data_should_be_on_the_page_concerned Proposal to include on-page citation data in Wikipedia]

:[[User:AndyMabbett|Andy Mabbett]] 13:47, 20 Mar 2007 (PDT)

==Examples==
* (from a mailing list):
:<blockquote>if you want to cite a [biomedical journal] journal article on Wikipedia [...] you can export a correctly-formatted citation for Wikipedia from HubMed using unAPI... http://hublog.hubmed.org/archives/001408.html</blockquote>

*[http://www.zotero.org/ Zotero], a Firefox extension to help collect, manage, and cite research sources.
:[[User:AndyMabbett|Andy Mabbett]] 09:13, 21 Mar 2007 (PDT)

== Original hBib Discussion ==

During the WWW2005 Developer's Day [[microformats]] track, Rohit Khare gave a [[presentations|presentation]] where he discussed the microformats [[process]], and then did a quick demonstration wherein a bunch of us got on a shared Subethaedit document, and brainstormed some thoughts on what an "hBib" bibliography citation microformat would look like. Rohit placed the [http://cnlabs.commerce.net/~rohit/hBib%20Discussion.html document on his Commercenet site].

* http://cnlabs.commerce.net/~rohit/hBib%20Discussion.html

''An attempt to summarize and inline the linked document follows. -Mike''

Two major goals were outlined by the group:

* Avoid re-keying references
* Adapt to new journal styles by changing CSS

The fundamental problem was discussed in terms of display - the ability to transform XHTML+hBib into the many journal-specific formats. For example, how to display "et.al" when all authors are present in the source, and how to re-order the elements if a style defines a set order of elements that conflicts with the ordering in the source. Using hCard for authors was agreed on, and the beginnings of an example were shown.

== XHTML Structure ==
With my exprience working X2V and hCa* has taught me what elememts are easy to find and which are not. Since the Citation microformat is very new it is possible to not make a lot of the same errors twice and to make things easier for extracting application to find and imply certain properties.

* There should be some sort of 'root node' that implies all child elements are for the hCitation microformat.
* Since most people will have multiple citations there should be away to represent each hCitation object as a unqiue block independent of another. This is to keep the parse from finding 'author' and applying that to all citations. Each citation should be in a container (class="hcite") that is separated from others.
* Perhaps class="hcite" with <code><cite></code> recommended as the root element. E.g. <code><cite class="hcite"></code>

'''Note: This section was the original content of the document. Since then, class='hcite' has been agreed on as the root class name. See [http://microformats.org/wiki?title=citation-brainstorming#.27hcite.27_as_Root_Element_name explanation].'''

== Citation vs. [[media-info]] ==

What distinguishes a cite from say [[media-info]] (e.g. [[media-info-examples]]) is that a cite is a reference to something explicitly external to the current piece of content or document, whereas [[media-info]] describes information about content embedded or inline in the current document.

== Semantic Meaning ==
One of the guiding priniciple of Microformats is to use the most semantically rich element to describe each node (Point 2 of Semantic XHTML Design Principles: Use the most accurately precise semantic XHTML building block for each object etc). Since we are dealing with HTML and citations, several elements are candidates to be used to enrich the semantic meaning. [http://www.w3.org/TR/REC-html40/struct/text.html CITE, BLOCKQUOTE, Q, A], (are there more?)

The [[citation-brainstorming|Citation Brainstorming Page]] has a few development and ideas about how to give another person credit for a link. Some of the semantic ideas behind their choices of tags can be applied to a full bibliographic type reference. ''Does this sentence make sense only historically? -Mike''

== OCLC's WorldCat for titles ==
Question: what about using something like OCLC's [http://www.oclc.org/worldcat/open/isbnissnlinking/default.htm WorldCat] for linking titles? - Tim White

== This and That ==
After reading through alot of different citation encoding formats, i noticed that each format was being used in onw of two ways. It was either to describe the Current page (THIS.PAGE) or being used to encode references that point to external resources (THAT.PAGE)

The informatation being encoded was identical for both resources (author, date, name, etc) they just reference different things. For this microformat, i'm not sure if we want to try to solve both problems, or just one? The meta tags in the head element would be the ideal place for information about the THIS.PAGE, but that is not in following with the ideals of microformats where information is human-readable. The THAT.PAGE idea where a list of references is at the end of a document in the form of a bibliography is more inline with the ideals of a microformat where the data is human-readable. That doesn't mean that data about the current document shouldn't be human-readable, so some of the same properties used to reference extermal resources can be used for the current document (THIS.PAGE). To do this a different root item could be used and transforming applications could either extract the citation data about the current page, or information about this page's references.

This is open for discussion, but either way, i believe that the properties used to describe a page will be the same for both THIS and THAT. [http://suda.co.uk/ brian suda]

== More on This and That ==

Citation microformats are being explored as a possibility for citing genealogical information at [http://eatslikeahuman.blogspot.com Dan Lawyer's blog].

This is a case where frequently the citation would refer to (THIS.PAGE), but would have nested within it a reference to (THAT.PAGE), possibly a few levels deep. For instance, a web page might contain data extracted from a microfilm of a census. The citation would need to include information about the web page, information about the microfilm, and information about the census. Genealogical citations are expected to include the repository (where can this book or microfilm be found. Is this the same as ''venue''?). So, at each level the information should contain the repository of the referenced item. A nesting (recursive) mechanism for citation microformats would be useful in this case. Is this the function of the "container" element in the Straw Format?

== Date Formatting ==
Since microformats are all about re-use and the accepted way to encode Date-Time has been pretty much settled, then this is a good place to start when dealing with all the different date citation types.

These are all the different fields from various citation formats that are of temporal nature:
* Date (available | created | dateAccepted | dateCopyrighted | dateSubmitted | issued | modified | valid)
* originInfo/dateIssued
* originInfo/dateCreated
* originInfo/dateCaptured
* originInfo/dateOther
* month
* year
* Copyright Year
* Date - Generic
* Date of Confernce
* Date of Publication
* Date of update/revisou/issuance of database record
* Former Date
* Entry Date for Database Record
* Database Update
* Year of Publication

There are several common properties across several citation domains and will certainly be in the citation microformat, the unique instances will need further consideration, otherwise there could be no end to posiblities.

There are also several properties (year, month, Year of publication) that can be extracted from another source. Therefore, if you only encode a more specific property such as; Date of Publication, you can extract the 'year of publication' from that. Since the date-time format we are modeling after is the ISO date-time format, just the Year portion is an acceptable date. So if you ONLY know the year of publication, the you can form a valid 'Date of Publication' as a microformat (which inturn is a valid 'year of publication') - you milage may vary when it comes to importing into citation applications.

...

It seems to me that these can be collapsed to maybe one or two different date properties. As far as the specific human readable formatting of the date, that can be chosen per whatever the presentation style guide says, and the [[datetime-design-pattern]] used to simplify the markup. - Tantek

'''Important'''
Sometimes we need a date range and not simply a date (e.g. 4-6 May 2006). See ''Conference Citation'' examples later on this page. - Discoleo

'''Seasons'''
Some journals have seasonal issues (e.g. "Summer 2006 edition") instead of, or as well as, editions labelled by month or other calendar-date. [[User:AndyMabbett|AndyMabbett]] 05:05, 4 Nov 2006 (PST)

== Tags ==
Some of the citation formats has a place for 'keywords' or 'generic tags', etc. This might be a good place to re-use the [http://microformats.org/wiki/rel-tag RelTag microformat]. The downside would be that they are then forced to be links, which might be the correct way to mark-up these terms.

== MARC / MODS / Dublin Core ==

The MODS ([http://www.loc.gov/standards/marcxml/Sandburg/sandburgmods.xml example]) and Dublin Core ([http://www.loc.gov/standards/marcxml/Sandburg/sandburgdc.xml example]) transformations of MARC21 may contain some useful ideas.

Here's a first attempt at rewriting the linked examples in XHTML (written in response to a [http://microformats.org/discuss/mail/microformats-discuss/2005-December/002438.html mailing list query about encoding book information with microformats]):

<pre><nowiki>
<div class="book" lang="en">
<h3 class="fn">Arithmetic /</h3>
By Sandburg, Carl,
1878-1967,
and Rand, Ted
Publisher: Harcourt Brace Jovanovich,
San Diego
Published: 1993
A poem about numbers and their characteristics. Features
anamorphic, or distorted, drawings which can be restored to normal by viewing
from a particular angle or by viewing the image's reflection in the provided
Mylar cone.
One Mylar sheet included in pocket.
Subjects:
<ul>
<li class="subject">Arithmetic</li>
<li class="subject">Children's poetry, American.</li>
<li class="subject">Arithmetic</li>
<li class="subject">American poetry</li>
<li class="subject">Visual perception</li>
</ul>
</div>
</nowiki></pre>

== Basic Citation Stuctures ==
There are basic structures to any citation, this is an overview of some of the types
[http://www.users.muohio.edu/darcusb/misc/citations-spec.html http://www.users.muohio.edu/darcusb/misc/citations-spec.html]

== Concerns not addressed by existing formats ==

There are some aspects '''NOT adequately''' covered by existing formats. I have addressed this issue on the OpenOffice.org wiki page, too. [see http://wiki.services.openoffice.org/wiki/Bibliographic_Database for an extending discussion, the paragraph on ''Reference Types'']

These issues pertain mainly to '''Errata''', '''Comments and Authors Reply''' and '''Article Retractions'''.
* a bidirectional link could be necessary to implement these features (original article <=> eratum, reply, retraction letter)
* '''IMPORTANT: Errata'''
** Erata: one or more Corrections might be posted in various issues of the journal
** this is usually cited as: Orininal Article Citation Data (Correction available in ''Journal, Issue Nr, Year, Pages'') (repeat for more than one correction)
** it is possibly never cited alone
** there should be a link to the original article, while the original article should contain a link to this ''Errata''
* '''IMPORTANT: Commentary and Author Reply'''
** similar to Errata, there might be one or more Comments and Author Replys; this should be stored, too
** however, it is usually not included in the original citation
** it might be used however in a citation, but I do not know exaclty how to cite it optimally (original article should be provided as well)
* '''IMPORTANT: Article Retraction'''
** an article may be retracted because of plagiarism or some other flaw
** this should not be used any further in the research
** however, it might be used e.g. for an article on plagiarism or flawed research
** there should be therefore one field storing this information, too, and a link to:
** the published withdrawal letter (which explains why the article was retracted)

* this issue may need a time-controlled event
* '''IMPORTANT: electronic publishing ahead of print (EPUB)'''
** more and more articles are initially posted online, before the published article gets actually printed
** How should this be used/cited?
** Is this changed, after the print version becomes available?

== Outstanding Issues ==
The 3 main points i (Brian) came across so far are:
1) IDENTIFIERS
2) FORMAT TYPES
3) NESTING

1) In hCard/hCalendar there is a UID field. Added with URL it makes for a great unique identifier. There are loads of other identifers besides URL, ISBN, LOC call number, SKU, ISSN, etc. Many of these are unique in their domain, but not globally unique. So how to they get marked-up? Much like the hCard TEL/ADR properties, we can use something like:
<pre>
<nowiki>
<div class="uid">ISBN: 123456</div>
</nowiki>
</pre>
This makes the encoding the most extensible... if we start use class="isbn" then it is an enumerated list, with class="type" it is open ended.

2) I keep mis-using "format", format is the medium - hardback, softback. The TYPE (there probably is a better word - container?) is book, article, conference, manifesto, etc. Much like the identifers we can make an enumerated list of values, class="book", class="article", but that boxes us in, whereas something like: <pre><nowiki>article</nowiki></pre> leaves things more open.

3) Nesting citation data in a citation. The ability to nest the same microformat inside itself is something that other microformats don't explicitly handle.

The two options are:
i) Using class="book"
<pre>
<nowiki>
<div class="hcite">
<div class="book">
Book Title
<div class="chapter">
Chapter Title
</div>
</div>
</div>
</nowiki>
</pre>

This makes things easy to nest and to figure out exactly what is
associated with what, but the downside is that we have enumerated
lists of values for the class properties.

ii) using the TYPE for book
<pre>
<nowiki>
<div class="hcite">
<div class="type">book</div>
Book Title
<div class="type">chapter</div>
Chapter Title
</div>
</nowiki>
</pre>

now the class="fn" is not nested inside the class="book" or
class="chapter" so there would have to be some other mechanism to
associate the data with the type.

== Brian's straw format ==

=== implied schema (examples) ===
+ publisher
+ language
+ description
+ title
+ creator
+ journal
+ volume
+ issue
+ page
+ edition
+ identifier
+ tags
+ format
+ date published
+ copyright
- audience

=== implied schema (formats) ===
+ publisher
+ language
+ description
+ title
+ creator
+ volume
+ pages
+ edition
+ issue
+ identifier
+ tags
+ format
+ date published
+ date copyrighted
- subtitle
- image
- excerpt
- index terms
- series title
- publication
- journal
- part (1 of X)

UNION of the two schemas
+ (PLUS) means common properties
- (MINUS) means unique to the schema

=== Working straw schema ===

This list records discussion about the common schema from above. The format is ''descriptive-name'' (''optional-recommended-element'' 'class-name') (''link to explanation'').

If there is no explanation link, that field should be considered either obvious or up for debate. If you're not sure which, it's up for debate.

* root element ('hcite') ([http://microformats.org/wiki?title=citation-brainstorming#.27hcite.27_as_Root_Element_name explanation])
** title ('title')
** Author / Editor etc. ('creator')
** Pages ('pages')
*** note: this can be any value
** container ('container hcite')
*** A nested hcite element that represents a containing item (like a book for a chapter) ([http://microformats.org/wiki?title=citation-brainstorming#Container discussion and link to mailing list thread])
** Volume Number ('volume')
** Edition ('edition')
** Issue number ('issue')
** Tags (href rel='tag')
** Format ('format')
*** Note - this is unclear at present - does format mean 'type', as in 'book' vs. 'article'? --[[User:Mike|Mike]] 22:53, 16 Jan 2007 (PST)
** date published ('date-published') ([http://microformats.org/wiki?title=citation-brainstorming#Date_Fields explanation])
** date accessed ('date-accessed') ([http://microformats.org/wiki?title=citation-brainstorming#Date_Fields explanation])
** publisher
** language
** Abstract / description ('description')
** URI (href class='uri') ([http://microformats.org/wiki?title=citation-brainstorming#The_URI_Element explanation])
** identifier
*** an (not necessarily globally unique) identifier, such as a cite-key, pubmed ID number, or simply the reference number or string within a publication ([1] or [CLRS2001])

==== Notes about missing / changed fields in the schema ====

This section lists fields that are intentionally ''not'' included in the straw schema, or are not represented directly, and links to discussion about each.

* date copyrighted ([http://microformats.org/wiki?title=citation-brainstorming#Date_Fields explanation])

=== Examples ===

Markup examples using the above format:

==== Book ====

This is Brian's original example

<pre>
<nowiki>
<ul class="bibliography">
<li class="hcite" xml:lang="en-gb">


<div class="creator vcard">
John Doe
...
</div>


Foobar!
World Class Book about foobar
1
1
1
1-10
article


12345678


<a class="keyword" rel="tag" href="/tags/foo">foo</a>
bar


Published <abbr class="date-published" title="20060101">January 1st 1006</abbr>
Copyright <abbr class="copyright" title="20060101">2006</abbr>
</li>
...
</ul>

Have you read <abbr title="book" class="format">Foo Bar</abbr>?
It was written by John Doe.
It only came out a <abbr class="dtpublished" title="20060101">few months ago</abbr>
</nowiki>
</pre>

Note: the "format" property above is incorrect. Format would refer more the physical characteristics of an item, rather than its type or genre (e.g. "article", "book", etc.). I'd rather have the main class for the li be "article" in this context, than the fairly meaningless "citation." Of course, one could have both, which would be fine too. -- bruce

Note: Could we use ROLE from hCard to identify editors, translators, authors, etc?
This was discussed on the mailing list and the idea was dropped [http://microformats.org/discuss/mail/microformats-discuss/2006-September/005694.html]

'''Comments''' : [[User:Singpolyma|singpolyma]] 08:03, 16 Jun 2006 (PDT) : keywords should be [[rel-tag]], and probably also [[XOXO]] (the same way the citation list is)

[[User:RCanine|RCanine]] 11:55, 18 Dec 2006 (EST) :

* Is there a reason not to re-use "published" from hAtom instead of inventing a new, basically equivalent term in "dtpublished"?
** note - date-published was decided on for the field, example changed to reflect it --[[User:Mike|Mike]] 10:12, 30 Mar 2007 (PDT)
* Missing a URL/URI/IRI/UID etc. field example (ISBN for Book).
* Does the "copyright" class conflict with [http://www.whatwg.org/specs/web-apps/current-work/#class WHATWG's definition]?
* WRT Bruce's comment, I'm currently using class="article citation" for my writing, as it has the most flexibility with CSS styles for titles (e.g. Book titles .citation>.fn must be italicized, while article titles must not, their container should).
* Speaking of containers, we need an "in" or "collection" field for journal articles or articles-in-books, or is that covered by "publisher"?

==== Citing Private Communication ====

Needs an example.

==== Citing Legal Cases ====
Needs an example.
see [http://microformats.org/wiki/citation-examples-markup#Wikipedia_Court_Case Wikipedia example] for inspiration.

==== Citing a Book ====

needs an example

==== Citing a journal article ====

From an old entry in PubMed - J Aersp Med. [http://www.ncbi.nlm.nih.gov/entrez/query.fcgi?db=pubmed&cmd=Retrieve&dopt=AbstractPlus&list_uids=4611181&query_hl=7&itool=pubmed_docsum link]

<pre><nowiki>

R R Burton,
S D Leverett, and
E D Michaelson

Man at high sustained +Gz acceleration: a review.
In 
<abbr class="type" title="Journal">J.</abbr><abbr class="title" title="Aerospace medicine">Aersp. Med.</abbr>
urn:issn:0001-9402
45
10
<abbr class="date-published" title="101974">Oct, 1974</abbr>
, pages 1115-36.



</nowiki></pre>

Note, I'm not entirely sure about the issn urn here.

==== Citing a magazine article ====

needs an example

==== Citing a Patent ====

Drawn from this [http://microformats.org/wiki/citation-examples#U.S._Patent example from Wikipedia]:

<pre><nowiki>
<li class="hcite"><a href="http://patft.uspto.gov/netacgi/nph-Parser?patentnumber=4,405,829" class="url"
title="http://patft.uspto.gov/netacgi/nph-Parser?patentnumber=4,405,829">
U.S. Patent 4,405,829</a>:
The <a href="/wiki/RSA" title="RSA">RSA</a> patent, a famous software patent on the ground-breaking
and highly unobvious algorithm for public key encryption, widely used for secure communications
in many industries nowdays
</li>
</nowiki></pre>

==== Citing a conference publication====

Based on the [http://microformats.org/wiki/citation-examples#ACM_Digital_Library_Search_Result_Examples conference publication reference example].

Changed Oct 06 to conform with [http://microformats.org/wiki/citation-brainstorming#Brian.27s_Straw_format Brian's format]. --[[User:Mike|Mike]] 18:09, 12 Oct 2006 (PDT)
(everything but the url class should be in line with that proposal)

L. Hochstein, J. Carver, F. Shull, S. Asgari, V. Basili, J. K. Hollingsworth, and M. Zelkowitz, “Hpc programmer productivity: A case study of novice hpc programmers,” in Proceedings of ACM/IEEE Supercomputing Conference, 2005.

<pre><nowiki>

Lorin Hochstein
 University of Maryland, College Park ,
 Jeff Carver 
 Mississippi State University ,
 Forrest Shull 
 Fraunhofer Center Maryland ,
 Sima Asgari
 University of Maryland, College Park ,
 Victor Basili
 Fraunhofer Center Maryland ,
 Jeffrey K. Hollingsworth
 University of Maryland, College Park , and
 Marv Zelkowitz
 University of Maryland, College Park ,

<a class="title url" href="http://dx.doi.org/10.1109/SC.2005.53">HPC Programmer Productivity: A Case Study of Novice HPC Programmers</a>.
(conference publication)

<a class="title url" href="...">Proceedings of ACM/IEEE Supercomputing Conference</a>
<abbr class="date-published" title="20051126T0000-0800">2005</abbr>

page 35

IEEE Computer Society


Washington,
DC


<a class="url eprint" href="http://portal.acm.org/...">PDF of full text from ACM</a>

DOI: <a class="url uid" href="http://dx.doi.org/10.1109/SC.2005.53">10.1109/SC.2005.53</a>
Tags:
<a class="keyword" rel="tag" href="results.cfm?query=genterm%3A%22Design%22 ...">Design</a>,
<a class="keyword" rel="tag" href="results.cfm?query=genterm%3A%22Experimentation%22 ....">Experimentation</a>,
<a class="keyword" rel="tag" href="results.cfm?query=genterm%3A%22Measurement%22...">Measurement</a>,
<a class="keyword" rel="tag" href="results.cfm?query=genterm%3A%22Performance%22 ...">Performance</a>

In developing High-Performance Computing (HPC) software, ....

</nowiki></pre>

'''Note''' (From [[Discoleo]], Sept. 06)
* sometimes, the citation must include '''Town/Country''' and '''Precise Date/Date Range''', e.g.
** ''Gillespie SH, Dickens A.'' Variation in mutation rate of quinolone resistance in Streptococcus pneumoniae [abstract P06-17A]. In: Abstracts of the 3rd International Symposium on Pneumococci and Pneumococcal Disease (Anchorage, 5-9 May 2002).Washington, DC: American Society of Microbiology, 2002.
** ''Bassetti, M.; Righi, E.; Rebesco, B.; Molinari, MP.; Costa, A.; Fasce, R.; Cruciani, M.; Bassetti, D.; Bobbio Pallavicini, F.'' 44th Annual Interscience Conference on Antimicrobial Agents and Chemotherapy (ICAAC). Washington, DC; 2004. Epidemiological trends in nosocomial candidemia in ICU: A five-year Italian perspective.
** ''Peacock JE, Wade JC, Lazarus HM, et al.'' Ciprofloxacin/piperacillin vs. tobramycin/piperacillin as empiric therapy for fever in neutropenic cancer patients, a randomized, double-blind trial [abstract 373]. In: Program and abstracts of the 37th Interscience Conference on Antimicrob Agents and Chemotherapy (Toronto). Washington, DC: American Society for Microbiology, 1997.

==== Citing an external website ====

This is based on a formal citation of a website in the references section of a research paper, but could also be used for in-line links that had added information. Here's the original:

[25] David Stern, "eprint Moderator Model", http://www.library.yale.edu/scilib/modmodexplain.html (version dated Jan 25, 1999)

<pre><nowiki>
<cite class="hcite">
<a class="fn url" href="http://www.library.yale.edu/scilib/modmodexplain.html">eprint Moderator Model</a>

<a href="http://pantheon.yale.edu/~dstern/dsbio.html" class="url fn">David Stern</a>

<abbr class="dtpublished" title="19990125T0000-0500">
Jan 25, 1999
</abbr>
</cite>
</nowiki></pre>

=== Discussion of Straw Format elements ===

This section is to provide explanations for posterity about the elements of the straw format, linking to discussions on the list and elsewhere if possible.

==== 'hcite' as Root Element name ====

This discussion took place in January of 2007, with [http://microformats.org/discuss/mail/microformats-discuss/2007-January/008098.html voting occurring on the mailing list].

It was decided to use 'hcite' as the root element's class-name for uniqueness and to reflect a trend in using 'h' to start microformat names.

==== The URI Element ====

It was decided to use URI for both http links to available copies or URNs.
This encompasses URLs that link directly to online copies as well as through resolvers using URIs such as urn:isbn: 0521890012

See the discussion from [http://microformats.org/discuss/mail/microformats-discuss/2006-November/007390.html November] and [http://microformats.org/discuss/mail/microformats-discuss/2006-December/007403.html December].

==== Date Fields ====

Brian's original straw format had three date fields, "accessed", "copyrighted", and "published".
After examining the examples of usage on the web, it was clear that 'copyrighted' was not used in the examples we have.
It was used once, but without a corresponding 'published' field (OCLC WorldCat), and it seems in that case to be used as
an equivalent to 'published'.

I updated the straw citation to include only 'accessed' and 'published' on January 31. --[[User:Mike|Mike]] 00:26, 31 Jan 2007 (PST)

I've mentioned more than once that "date-published" is misleadingly specific; too much for real world citations. Consider that many books are published in the year preceding their copyright date, which is in fact the date used for citation. I'd prefer just "date" and "date-accessed" as a first cut. --[[User:BDarcus|Bruce]] 3 Feb 2007

See the discussion from the [http://microformats.org/discuss/mail/microformats-discuss/2007-January/008175.html 'dates' thread on the list].

==== Container ====

Discussion about how to represent containing relationships is on the thread [http://microformats.org/discuss/mail/microformats-discuss/2007-March/thread.html 'nesting container elements']

== Old straw format discussion ==

Saved here so that I'm not just deleting people's comments.

=== Mike straw format suggestion (Deprecated) ===

In the interests of starting debate and having something concrete to fix, I suggest the following structure for a format. It is probably very incomplete and I claim no microformat expertise. I'm just trying to follow existing patterns. Comments and ridicule are both solicited. -Mike

'''NOTE:''' This format is here for historical reference. Because it was not based on existing examples, I've deprecated it and contributed examples to Brian's format. If you feel that any missing elements in here should be in the final format, find examples for them and contribute to Brian's schema. Thanks! --[[User:Mike|Mike]] 18:22, 12 Oct 2006 (PDT)

==== In General ====

The ''citation'' format is based on a set of fields common to many bibliographic data formats, which are often implied by standard citation display styles but not explicitly marked up in practice on the web.

==== Schema ====

The citation schema consists of the following:

* cite
** title: required, text (class = fn)
** subtitle: optional, text
** authors: optional, use hCard
** publication date: optional
** link(s) to instantiations, optional, url or use rel-enclosure? (class=url)
** UID, optional (for ISBN, DOI - use existing uid class) | permalink
** series (aka volume/issuenum) , optional (''not as sure how to handle these - suggestions?'')
** pages: startpage & endpage, optional, text
** venue, optional (hCard)
** publisher, optional (hCard)
** container: optional (nested hCite)
** abstract, optional (blockquote + class="abstract" ?)
** notes, optional (blockquote + class="notes" ?)
** keywords, optional (rel-tag)
** image, optional (for inclusion inline, unlike the url)
** copyright, optional (rel-license)
** ''what else am I missing?''
*** language, optional

''Looks good, but I question the use of hCard for names. Due to ambiguity issues, requring hCard would lead to extra markup in order to apply just a name, hence [http://microformats.org/discuss/mail/microformats-discuss/2006-March/003487.html the need for a root element]. We should extract the N optimization of hCard like we did with adr, in order to ease this problem.'' --[[User:RCanine|Ryan Cannon]]

Perhaps a Retrieved Date or Access Date would be appropriate for citing online resources. For example at http://www.crlt.umich.edu/publinks/facment_biblio.html
you see citations like this<nowiki>:</nowiki>
<blockquote>
Chief Academic Officers of the Big 12 Universities (2000). Big 12 Faculty Fellowship Program. Retrieved December 20, 2000 from the World Wide Web: http://www.k-state.edu/provost/academic/big12/big12guide.htm.
</blockquote>
--[[User:JoeAndrieu|Joe Andrieu]]

==== Discussion about citing legal cases ====

Here's some info I found about citing law:

I'm not a lawyer, so I'm relying on the published [http://www.legalbluebook.com "blue book" standard], at least the only part of it I can get without paying $25. I'd be happy to hear improvements from experts in the field - how do lawyers mark up references to case law in HTML now?

From groklaw.net and eff.org, I find mostly just links to PDFs with the name of the case as the link text. Or just this, from EFF:
<pre><nowiki>
<h1>The Betamax Case</h1>
<h2>Sony Corp. of America v. Universal City Studios, 464 U.S. 417 (1984)</h2>
</nowiki></pre>

From an example at the sample bluepages: http://www.legalbluebook.com/pdfs/bluepages.pdf
5 basic components:
*1 name of the case (citation title)
*2 published source in which case may be found (citation containing publication?)
*3 a parenthetical indicating the court and year of decision (citation venue?)
*4 other parenthetical information, if any (citation notes?)
*5 subsequent history of the case, if any (citation notes?)

Here's two examples from the bluebook. Note that there are very strict rules about abbreviations in that source!

Holland v. Donnelly, 216 F. Supp. 2d 227, 230 (S.D.N.Y. 2002), aff'd, 324 F.3d 99 (2d Cir. 2003).

Green v. Georgia, 442 U.S. 95, 97 (1979) (per curiam) (holding that exclusion of relevant evidence at sentencing hearing constitutes denial of due process).

== Examples in the wild ==
Pages which start to use the discussion above to create working examples in using hcite:
(This section could be used as a base for a page like "hcite-examples-in-wild" later).

Please add new examples to the top of this section.
* [http://www.demo.vorlagen.uni-erlangen.de/univis/mitarbeiter.shtml/georg-hager.shtml Example User Page] at the regional computer lab Erlangen, Germany, based on the universal information system UnivIS marked up with vcard, hcalender (optional, if user makes a lecture) and hcite.

== discussions ==
* [[citation-irc-notes-2006-04-09]]

citation-brainstorming

2007-04-09T00:11:35Z

BenWest: /* Convert citation formats */ moving andy's comment to the issues page. hope he doesn't mind.

<h1> Citation Brainstorming </h1>

== See also ==
* [[citation]]
* [[citation-examples]]
* [[citation-formats]]
* [[citation-faq]]

__TOC__

== Contributors ==

* ...
* ... (a bunch of good folks!)
* Tantek Çelik
* Tim White
* Michael McCracken
* Brian Suda
* [[User:AndyMabbett|Andy Mabbett]]

== Use Cases ==

To focus the discussion, please add use cases below that will help show what problems the citation microformat will be solving.

I've included two, focusing on consuming information - I've assumed that use cases for generating microformatted content would just involve the desire to enable your content to be consumed better, but I'm interested to see if there's something I'm missing here -Mike

=== Acquiring reference information from the web ===

A user either finds an author's papers page, or is viewing the results of a search and would like to import the information about the displayed papers into their local reference database, for the purposes of cataloging things they've read, adding notes, and using the information to generate later citations, potentially in other forms, such as BibTeX or Docbook, for inclusion in a publication of their own.

Notes: In this case, it isn't important to the user what format the citation takes as displayed on the page where they find it. What *is* important is that it contains enough information to allow generation of the format they will ultimately re-publish it in. This implies that it may be worthwhile to err a little on the side of verbosity.

Also, links to downloadable full representations of the cited work are very important - e.g. a link to the PDF of a journal article, or to a music file.

=== Subscribing to reading lists, periodicals, etc ===

I would like to be able to leverage my news aggregator with hAtom to subscribe to a remote source for citation information, for example:

* a reading list for a seminar
* The publication list for a conference (e.g., subscribe to SIGGRAPH and see the updated conference proceedings every year)
* the issues of a journal
* a particular research group or researcher's publications
* Not just research: a popular author's publications (e.g., [http://www.gladwell.com/archive.html Malcolm Gladwell's Archive])

=== Aggregating reading lists and reviews ===

A citation microformat-specific aggregator could provide a decentralized version of [http://citeulike.org/ CiteULike]. Libraries, authors, research groups, and publishers could mark up their collections, while other people on weblogs or review sites could add tags and reviews.

At least, having a well-adopted microformat would make writing tools like CiteULike much better, since it relies in some cases on screen-scraping publisher web-sites.

=== Cut & Paste from web pages ===
Capturing/copying HTML from web pages for use in other applications (especially when those apps present HTML as output), such as pasting into Word, or a specialized application like [http://www.google.com/notebook Google Notebook], [http://onfolio.com Onfolio] or [http://www.kaboodle.com Kaboodle]. When such captures are made, it makes sense to keep track of the full citation data, including the date it was accessed, which may or may not be the date it was published.

=== Blogs quoting other resources, including blogs ===
Any blog that cites online content, whether a blog or news article, could use an hCitation to properly link to the cited reference. Such citations could include the access date when the blogger made the citation, because resources on the other side of those links can change without notice.

Instead, today we have simple formating with a link to the permaURL. The citation data is completely lacking. See [http://doc.weblogs.com Doc Searl's blog] for a style of referencing that could benefit from proper a citation uF.

Fascinating... after I added the last two use cases, I realized they focus on potentially marginal cases. The first because it is missing the "output" part of the cut & paste, where the uF would actually be used as part of the paste. The latter because bloggers have a working citation mechanism that is just a link to the URL (hopefully a permaURL). One could argue they wouldn't want a full hCitation. And in fact, until a tool exists that makes it easy, they probably won't. However, a tool that cuts & pastes from anywhere on the web into a blog with a full citation seems like a nice tool. But again, I'm not really paving the cowpaths with these ideas. -Joe Andrieu

===Finding in Library===
Find a copy of the cited work in a nearby library (as with [http://ocoins.info/ OpenCOinS]). [[User:AndyMabbett|AndyMabbett]] 04:55, 4 Nov 2006 (PST)

===Buy a copy===
Find the cited work on, for example, Amazon or [http://www.abebooks.com/ ABE]; or subscribe to a journal via its own website. [[User:AndyMabbett|AndyMabbett]] 04:55, 4 Nov 2006 (PST)

===Find reviews===
Find third-party reviews of the cited work. [[User:AndyMabbett|AndyMabbett]] 04:55, 4 Nov 2006 (PST)

===Give citation data for the page being visited===

Adding a class of, say, "self" to an attribute of the proposed strawman would allow users (or user agents) to extract the data required to cite the page being visited, when referring to it elsewhere. There would be the added advantage of allowing the citation to be ignored by any parser which might be building a "tree" of citations, and preventing the setting up of an infinite loop.

For evidence of published "self citation" data (albeit on a secondary page) see the "cite this article" link on any Wikipedia entry, e.g. [http://en.wikipedia.org/w/index.php?title=Special:Cite&page=West_Midland_Bird_Club&id=115894372] from [http://en.wikipedia.org/wiki/West_Midland_Bird_Club].

See also [http://en.wikipedia.org/wiki/Wikipedia_talk:Citing_Wikipedia#Citation_data_should_be_on_the_page_concerned Proposal to include on-page citation data in Wikipedia]

:[[User:AndyMabbett|Andy Mabbett]] 13:47, 20 Mar 2007 (PDT)

==Examples==
* (from a mailing list):
:<blockquote>if you want to cite a [biomedical journal] journal article on Wikipedia [...] you can export a correctly-formatted citation for Wikipedia from HubMed using unAPI... http://hublog.hubmed.org/archives/001408.html</blockquote>

*[http://www.zotero.org/ Zotero], a Firefox extension to help collect, manage, and cite research sources.
:[[User:AndyMabbett|Andy Mabbett]] 09:13, 21 Mar 2007 (PDT)

== Original hBib Discussion ==

During the WWW2005 Developer's Day [[microformats]] track, Rohit Khare gave a [[presentations|presentation]] where he discussed the microformats [[process]], and then did a quick demonstration wherein a bunch of us got on a shared Subethaedit document, and brainstormed some thoughts on what an "hBib" bibliography citation microformat would look like. Rohit placed the [http://cnlabs.commerce.net/~rohit/hBib%20Discussion.html document on his Commercenet site].

* http://cnlabs.commerce.net/~rohit/hBib%20Discussion.html

''An attempt to summarize and inline the linked document follows. -Mike''

Two major goals were outlined by the group:

* Avoid re-keying references
* Adapt to new journal styles by changing CSS

The fundamental problem was discussed in terms of display - the ability to transform XHTML+hBib into the many journal-specific formats. For example, how to display "et.al" when all authors are present in the source, and how to re-order the elements if a style defines a set order of elements that conflicts with the ordering in the source. Using hCard for authors was agreed on, and the beginnings of an example were shown.

== XHTML Structure ==
With my exprience working X2V and hCa* has taught me what elememts are easy to find and which are not. Since the Citation microformat is very new it is possible to not make a lot of the same errors twice and to make things easier for extracting application to find and imply certain properties.

* There should be some sort of 'root node' that implies all child elements are for the hCitation microformat.
* Since most people will have multiple citations there should be away to represent each hCitation object as a unqiue block independent of another. This is to keep the parse from finding 'author' and applying that to all citations. Each citation should be in a container (class="hcite") that is separated from others.
* Perhaps class="hcite" with <code><cite></code> recommended as the root element. E.g. <code><cite class="hcite"></code>

'''Note: This section was the original content of the document. Since then, class='hcite' has been agreed on as the root class name. See [http://microformats.org/wiki?title=citation-brainstorming#.27hcite.27_as_Root_Element_name explanation].'''

== Citation vs. [[media-info]] ==

What distinguishes a cite from say [[media-info]] (e.g. [[media-info-examples]]) is that a cite is a reference to something explicitly external to the current piece of content or document, whereas [[media-info]] describes information about content embedded or inline in the current document.

== Semantic Meaning ==
One of the guiding priniciple of Microformats is to use the most semantically rich element to describe each node (Point 2 of Semantic XHTML Design Principles: Use the most accurately precise semantic XHTML building block for each object etc). Since we are dealing with HTML and citations, several elements are candidates to be used to enrich the semantic meaning. [http://www.w3.org/TR/REC-html40/struct/text.html CITE, BLOCKQUOTE, Q, A], (are there more?)

The [[citation-brainstorming|Citation Brainstorming Page]] has a few development and ideas about how to give another person credit for a link. Some of the semantic ideas behind their choices of tags can be applied to a full bibliographic type reference. ''Does this sentence make sense only historically? -Mike''

== OCLC's WorldCat for titles ==
Question: what about using something like OCLC's [http://www.oclc.org/worldcat/open/isbnissnlinking/default.htm WorldCat] for linking titles? - Tim White

== This and That ==
After reading through alot of different citation encoding formats, i noticed that each format was being used in onw of two ways. It was either to describe the Current page (THIS.PAGE) or being used to encode references that point to external resources (THAT.PAGE)

The informatation being encoded was identical for both resources (author, date, name, etc) they just reference different things. For this microformat, i'm not sure if we want to try to solve both problems, or just one? The meta tags in the head element would be the ideal place for information about the THIS.PAGE, but that is not in following with the ideals of microformats where information is human-readable. The THAT.PAGE idea where a list of references is at the end of a document in the form of a bibliography is more inline with the ideals of a microformat where the data is human-readable. That doesn't mean that data about the current document shouldn't be human-readable, so some of the same properties used to reference extermal resources can be used for the current document (THIS.PAGE). To do this a different root item could be used and transforming applications could either extract the citation data about the current page, or information about this page's references.

This is open for discussion, but either way, i believe that the properties used to describe a page will be the same for both THIS and THAT. [http://suda.co.uk/ brian suda]

== More on This and That ==

Citation microformats are being explored as a possibility for citing genealogical information at [http://eatslikeahuman.blogspot.com Dan Lawyer's blog].

This is a case where frequently the citation would refer to (THIS.PAGE), but would have nested within it a reference to (THAT.PAGE), possibly a few levels deep. For instance, a web page might contain data extracted from a microfilm of a census. The citation would need to include information about the web page, information about the microfilm, and information about the census. Genealogical citations are expected to include the repository (where can this book or microfilm be found. Is this the same as ''venue''?). So, at each level the information should contain the repository of the referenced item. A nesting (recursive) mechanism for citation microformats would be useful in this case. Is this the function of the "container" element in the Straw Format?

== Date Formatting ==
Since microformats are all about re-use and the accepted way to encode Date-Time has been pretty much settled, then this is a good place to start when dealing with all the different date citation types.

These are all the different fields from various citation formats that are of temporal nature:
* Date (available | created | dateAccepted | dateCopyrighted | dateSubmitted | issued | modified | valid)
* originInfo/dateIssued
* originInfo/dateCreated
* originInfo/dateCaptured
* originInfo/dateOther
* month
* year
* Copyright Year
* Date - Generic
* Date of Confernce
* Date of Publication
* Date of update/revisou/issuance of database record
* Former Date
* Entry Date for Database Record
* Database Update
* Year of Publication

There are several common properties across several citation domains and will certainly be in the citation microformat, the unique instances will need further consideration, otherwise there could be no end to posiblities.

There are also several properties (year, month, Year of publication) that can be extracted from another source. Therefore, if you only encode a more specific property such as; Date of Publication, you can extract the 'year of publication' from that. Since the date-time format we are modeling after is the ISO date-time format, just the Year portion is an acceptable date. So if you ONLY know the year of publication, the you can form a valid 'Date of Publication' as a microformat (which inturn is a valid 'year of publication') - you milage may vary when it comes to importing into citation applications.

...

It seems to me that these can be collapsed to maybe one or two different date properties. As far as the specific human readable formatting of the date, that can be chosen per whatever the presentation style guide says, and the [[datetime-design-pattern]] used to simplify the markup. - Tantek

'''Important'''
Sometimes we need a date range and not simply a date (e.g. 4-6 May 2006). See ''Conference Citation'' examples later on this page. - Discoleo

'''Seasons'''
Some journals have seasonal issues (e.g. "Summer 2006 edition") instead of, or as well as, editions labelled by month or other calendar-date. [[User:AndyMabbett|AndyMabbett]] 05:05, 4 Nov 2006 (PST)

== Tags ==
Some of the citation formats has a place for 'keywords' or 'generic tags', etc. This might be a good place to re-use the [http://microformats.org/wiki/rel-tag RelTag microformat]. The downside would be that they are then forced to be links, which might be the correct way to mark-up these terms.

== MARC / MODS / Dublin Core ==

The MODS ([http://www.loc.gov/standards/marcxml/Sandburg/sandburgmods.xml example]) and Dublin Core ([http://www.loc.gov/standards/marcxml/Sandburg/sandburgdc.xml example]) transformations of MARC21 may contain some useful ideas.

Here's a first attempt at rewriting the linked examples in XHTML (written in response to a [http://microformats.org/discuss/mail/microformats-discuss/2005-December/002438.html mailing list query about encoding book information with microformats]):

<pre><nowiki>
<div class="book" lang="en">
<h3 class="fn">Arithmetic /</h3>
By Sandburg, Carl,
1878-1967,
and Rand, Ted
Publisher: Harcourt Brace Jovanovich,
San Diego
Published: 1993
A poem about numbers and their characteristics. Features
anamorphic, or distorted, drawings which can be restored to normal by viewing
from a particular angle or by viewing the image's reflection in the provided
Mylar cone.
One Mylar sheet included in pocket.
Subjects:
<ul>
<li class="subject">Arithmetic</li>
<li class="subject">Children's poetry, American.</li>
<li class="subject">Arithmetic</li>
<li class="subject">American poetry</li>
<li class="subject">Visual perception</li>
</ul>
</div>
</nowiki></pre>

== Basic Citation Stuctures ==
There are basic structures to any citation, this is an overview of some of the types
[http://www.users.muohio.edu/darcusb/misc/citations-spec.html http://www.users.muohio.edu/darcusb/misc/citations-spec.html]

== Concerns not addressed by existing formats ==

There are some aspects '''NOT adequately''' covered by existing formats. I have addressed this issue on the OpenOffice.org wiki page, too. [see http://wiki.services.openoffice.org/wiki/Bibliographic_Database for an extending discussion, the paragraph on ''Reference Types'']

These issues pertain mainly to '''Errata''', '''Comments and Authors Reply''' and '''Article Retractions'''.
* a bidirectional link could be necessary to implement these features (original article <=> eratum, reply, retraction letter)
* '''IMPORTANT: Errata'''
** Erata: one or more Corrections might be posted in various issues of the journal
** this is usually cited as: Orininal Article Citation Data (Correction available in ''Journal, Issue Nr, Year, Pages'') (repeat for more than one correction)
** it is possibly never cited alone
** there should be a link to the original article, while the original article should contain a link to this ''Errata''
* '''IMPORTANT: Commentary and Author Reply'''
** similar to Errata, there might be one or more Comments and Author Replys; this should be stored, too
** however, it is usually not included in the original citation
** it might be used however in a citation, but I do not know exaclty how to cite it optimally (original article should be provided as well)
* '''IMPORTANT: Article Retraction'''
** an article may be retracted because of plagiarism or some other flaw
** this should not be used any further in the research
** however, it might be used e.g. for an article on plagiarism or flawed research
** there should be therefore one field storing this information, too, and a link to:
** the published withdrawal letter (which explains why the article was retracted)

* this issue may need a time-controlled event
* '''IMPORTANT: electronic publishing ahead of print (EPUB)'''
** more and more articles are initially posted online, before the published article gets actually printed
** How should this be used/cited?
** Is this changed, after the print version becomes available?

== Outstanding Issues ==
The 3 main points i (Brian) came across so far are:
1) IDENTIFIERS
2) FORMAT TYPES
3) NESTING

1) In hCard/hCalendar there is a UID field. Added with URL it makes for a great unique identifier. There are loads of other identifers besides URL, ISBN, LOC call number, SKU, ISSN, etc. Many of these are unique in their domain, but not globally unique. So how to they get marked-up? Much like the hCard TEL/ADR properties, we can use something like:
<pre>
<nowiki>
<div class="uid">ISBN: 123456</div>
</nowiki>
</pre>
This makes the encoding the most extensible... if we start use class="isbn" then it is an enumerated list, with class="type" it is open ended.

2) I keep mis-using "format", format is the medium - hardback, softback. The TYPE (there probably is a better word - container?) is book, article, conference, manifesto, etc. Much like the identifers we can make an enumerated list of values, class="book", class="article", but that boxes us in, whereas something like: <pre><nowiki>article</nowiki></pre> leaves things more open.

3) Nesting citation data in a citation. The ability to nest the same microformat inside itself is something that other microformats don't explicitly handle.

The two options are:
i) Using class="book"
<pre>
<nowiki>
<div class="hcite">
<div class="book">
Book Title
<div class="chapter">
Chapter Title
</div>
</div>
</div>
</nowiki>
</pre>

This makes things easy to nest and to figure out exactly what is
associated with what, but the downside is that we have enumerated
lists of values for the class properties.

ii) using the TYPE for book
<pre>
<nowiki>
<div class="hcite">
<div class="type">book</div>
Book Title
<div class="type">chapter</div>
Chapter Title
</div>
</nowiki>
</pre>

now the class="fn" is not nested inside the class="book" or
class="chapter" so there would have to be some other mechanism to
associate the data with the type.

== Brian's straw format ==

=== implied schema (examples) ===
+ publisher
+ language
+ description
+ title
+ creator
+ journal
+ volume
+ issue
+ page
+ edition
+ identifier
+ tags
+ format
+ date published
+ copyright
- audience

=== implied schema (formats) ===
+ publisher
+ language
+ description
+ title
+ creator
+ volume
+ pages
+ edition
+ issue
+ identifier
+ tags
+ format
+ date published
+ date copyrighted
- subtitle
- image
- excerpt
- index terms
- series title
- publication
- journal
- part (1 of X)

UNION of the two schemas
+ (PLUS) means common properties
- (MINUS) means unique to the schema

=== Working straw schema ===

This list records discussion about the common schema from above. The format is ''descriptive-name'' (''optional-recommended-element'' 'class-name') (''link to explanation'').

If there is no explanation link, that field should be considered either obvious or up for debate. If you're not sure which, it's up for debate.

* root element ('hcite') ([http://microformats.org/wiki?title=citation-brainstorming#.27hcite.27_as_Root_Element_name explanation])
** title ('title')
** Author / Editor etc. ('creator')
** Pages ('pages')
*** note: this can be any value
** container ('container hcite')
*** A nested hcite element that represents a containing item (like a book for a chapter) ([http://microformats.org/wiki?title=citation-brainstorming#Container discussion and link to mailing list thread])
** Volume Number ('volume')
** Edition ('edition')
** Issue number ('issue')
** Tags (href rel='tag')
** Format ('format')
*** Note - this is unclear at present - does format mean 'type', as in 'book' vs. 'article'? --[[User:Mike|Mike]] 22:53, 16 Jan 2007 (PST)
** date published ('date-published') ([http://microformats.org/wiki?title=citation-brainstorming#Date_Fields explanation])
** date accessed ('date-accessed') ([http://microformats.org/wiki?title=citation-brainstorming#Date_Fields explanation])
** publisher
** language
** Abstract / description ('description')
** URI (href class='uri') ([http://microformats.org/wiki?title=citation-brainstorming#The_URI_Element explanation])
** identifier
*** an (not necessarily globally unique) identifier, such as a cite-key, pubmed ID number, or simply the reference number or string within a publication ([1] or [CLRS2001])

==== Notes about missing / changed fields in the schema ====

This section lists fields that are intentionally ''not'' included in the straw schema, or are not represented directly, and links to discussion about each.

* date copyrighted ([http://microformats.org/wiki?title=citation-brainstorming#Date_Fields explanation])

=== Examples ===

Markup examples using the above format:

==== Book ====

This is Brian's original example

<pre>
<nowiki>
<ul class="bibliography">
<li class="hcite" xml:lang="en-gb">


<div class="creator vcard">
John Doe
...
</div>


Foobar!
World Class Book about foobar
1
1
1
1-10
article


12345678


<a class="keyword" rel="tag" href="/tags/foo">foo</a>
bar


Published <abbr class="date-published" title="20060101">January 1st 1006</abbr>
Copyright <abbr class="copyright" title="20060101">2006</abbr>
</li>
...
</ul>

Have you read <abbr title="book" class="format">Foo Bar</abbr>?
It was written by John Doe.
It only came out a <abbr class="dtpublished" title="20060101">few months ago</abbr>
</nowiki>
</pre>

Note: the "format" property above is incorrect. Format would refer more the physical characteristics of an item, rather than its type or genre (e.g. "article", "book", etc.). I'd rather have the main class for the li be "article" in this context, than the fairly meaningless "citation." Of course, one could have both, which would be fine too. -- bruce

Note: Could we use ROLE from hCard to identify editors, translators, authors, etc?
This was discussed on the mailing list and the idea was dropped [http://microformats.org/discuss/mail/microformats-discuss/2006-September/005694.html]

'''Comments''' : [[User:Singpolyma|singpolyma]] 08:03, 16 Jun 2006 (PDT) : keywords should be [[rel-tag]], and probably also [[XOXO]] (the same way the citation list is)

[[User:RCanine|RCanine]] 11:55, 18 Dec 2006 (EST) :

* Is there a reason not to re-use "published" from hAtom instead of inventing a new, basically equivalent term in "dtpublished"?
** note - date-published was decided on for the field, example changed to reflect it --[[User:Mike|Mike]] 10:12, 30 Mar 2007 (PDT)
* Missing a URL/URI/IRI/UID etc. field example (ISBN for Book).
* Does the "copyright" class conflict with [http://www.whatwg.org/specs/web-apps/current-work/#class WHATWG's definition]?
* WRT Bruce's comment, I'm currently using class="article citation" for my writing, as it has the most flexibility with CSS styles for titles (e.g. Book titles .citation>.fn must be italicized, while article titles must not, their container should).
* Speaking of containers, we need an "in" or "collection" field for journal articles or articles-in-books, or is that covered by "publisher"?

==== Citing Private Communication ====

Needs an example.

==== Citing Legal Cases ====
Needs an example.
see [http://microformats.org/wiki/citation-examples-markup#Wikipedia_Court_Case Wikipedia example] for inspiration.

==== Citing a Book ====

needs an example

==== Citing a journal article ====

From an old entry in PubMed - J Aersp Med. [http://www.ncbi.nlm.nih.gov/entrez/query.fcgi?db=pubmed&cmd=Retrieve&dopt=AbstractPlus&list_uids=4611181&query_hl=7&itool=pubmed_docsum link]

<pre><nowiki>

R R Burton,
S D Leverett, and
E D Michaelson

Man at high sustained +Gz acceleration: a review.
In 
<abbr class="type" title="Journal">J.</abbr><abbr class="title" title="Aerospace medicine">Aersp. Med.</abbr>
urn:issn:0001-9402
45
10
<abbr class="date-published" title="101974">Oct, 1974</abbr>
, pages 1115-36.



</nowiki></pre>

Note, I'm not entirely sure about the issn urn here.

==== Citing a magazine article ====

needs an example

==== Citing a Patent ====

Drawn from this [http://microformats.org/wiki/citation-examples#U.S._Patent example from Wikipedia]:

<pre><nowiki>
<li class="hcite"><a href="http://patft.uspto.gov/netacgi/nph-Parser?patentnumber=4,405,829" class="url"
title="http://patft.uspto.gov/netacgi/nph-Parser?patentnumber=4,405,829">
U.S. Patent 4,405,829</a>:
The <a href="/wiki/RSA" title="RSA">RSA</a> patent, a famous software patent on the ground-breaking
and highly unobvious algorithm for public key encryption, widely used for secure communications
in many industries nowdays
</li>
</nowiki></pre>

==== Citing a conference publication====

Based on the [http://microformats.org/wiki/citation-examples#ACM_Digital_Library_Search_Result_Examples conference publication reference example].

Changed Oct 06 to conform with [http://microformats.org/wiki/citation-brainstorming#Brian.27s_Straw_format Brian's format]. --[[User:Mike|Mike]] 18:09, 12 Oct 2006 (PDT)
(everything but the url class should be in line with that proposal)

L. Hochstein, J. Carver, F. Shull, S. Asgari, V. Basili, J. K. Hollingsworth, and M. Zelkowitz, “Hpc programmer productivity: A case study of novice hpc programmers,” in Proceedings of ACM/IEEE Supercomputing Conference, 2005.

<pre><nowiki>

Lorin Hochstein
 University of Maryland, College Park ,
 Jeff Carver 
 Mississippi State University ,
 Forrest Shull 
 Fraunhofer Center Maryland ,
 Sima Asgari
 University of Maryland, College Park ,
 Victor Basili
 Fraunhofer Center Maryland ,
 Jeffrey K. Hollingsworth
 University of Maryland, College Park , and
 Marv Zelkowitz
 University of Maryland, College Park ,

<a class="title url" href="http://dx.doi.org/10.1109/SC.2005.53">HPC Programmer Productivity: A Case Study of Novice HPC Programmers</a>.
(conference publication)

<a class="title url" href="...">Proceedings of ACM/IEEE Supercomputing Conference</a>
<abbr class="date-published" title="20051126T0000-0800">2005</abbr>

page 35

IEEE Computer Society


Washington,
DC


<a class="url eprint" href="http://portal.acm.org/...">PDF of full text from ACM</a>

DOI: <a class="url uid" href="http://dx.doi.org/10.1109/SC.2005.53">10.1109/SC.2005.53</a>
Tags:
<a class="keyword" rel="tag" href="results.cfm?query=genterm%3A%22Design%22 ...">Design</a>,
<a class="keyword" rel="tag" href="results.cfm?query=genterm%3A%22Experimentation%22 ....">Experimentation</a>,
<a class="keyword" rel="tag" href="results.cfm?query=genterm%3A%22Measurement%22...">Measurement</a>,
<a class="keyword" rel="tag" href="results.cfm?query=genterm%3A%22Performance%22 ...">Performance</a>

In developing High-Performance Computing (HPC) software, ....

</nowiki></pre>

'''Note''' (From [[Discoleo]], Sept. 06)
* sometimes, the citation must include '''Town/Country''' and '''Precise Date/Date Range''', e.g.
** ''Gillespie SH, Dickens A.'' Variation in mutation rate of quinolone resistance in Streptococcus pneumoniae [abstract P06-17A]. In: Abstracts of the 3rd International Symposium on Pneumococci and Pneumococcal Disease (Anchorage, 5-9 May 2002).Washington, DC: American Society of Microbiology, 2002.
** ''Bassetti, M.; Righi, E.; Rebesco, B.; Molinari, MP.; Costa, A.; Fasce, R.; Cruciani, M.; Bassetti, D.; Bobbio Pallavicini, F.'' 44th Annual Interscience Conference on Antimicrobial Agents and Chemotherapy (ICAAC). Washington, DC; 2004. Epidemiological trends in nosocomial candidemia in ICU: A five-year Italian perspective.
** ''Peacock JE, Wade JC, Lazarus HM, et al.'' Ciprofloxacin/piperacillin vs. tobramycin/piperacillin as empiric therapy for fever in neutropenic cancer patients, a randomized, double-blind trial [abstract 373]. In: Program and abstracts of the 37th Interscience Conference on Antimicrob Agents and Chemotherapy (Toronto). Washington, DC: American Society for Microbiology, 1997.

==== Citing an external website ====

This is based on a formal citation of a website in the references section of a research paper, but could also be used for in-line links that had added information. Here's the original:

[25] David Stern, "eprint Moderator Model", http://www.library.yale.edu/scilib/modmodexplain.html (version dated Jan 25, 1999)

<pre><nowiki>
<cite class="hcite">
<a class="fn url" href="http://www.library.yale.edu/scilib/modmodexplain.html">eprint Moderator Model</a>

<a href="http://pantheon.yale.edu/~dstern/dsbio.html" class="url fn">David Stern</a>

<abbr class="dtpublished" title="19990125T0000-0500">
Jan 25, 1999
</abbr>
</cite>
</nowiki></pre>

=== Discussion of Straw Format elements ===

This section is to provide explanations for posterity about the elements of the straw format, linking to discussions on the list and elsewhere if possible.

==== 'hcite' as Root Element name ====

This discussion took place in January of 2007, with [http://microformats.org/discuss/mail/microformats-discuss/2007-January/008098.html voting occurring on the mailing list].

It was decided to use 'hcite' as the root element's class-name for uniqueness and to reflect a trend in using 'h' to start microformat names.

==== The URI Element ====

It was decided to use URI for both http links to available copies or URNs.
This encompasses URLs that link directly to online copies as well as through resolvers using URIs such as urn:isbn: 0521890012

See the discussion from [http://microformats.org/discuss/mail/microformats-discuss/2006-November/007390.html November] and [http://microformats.org/discuss/mail/microformats-discuss/2006-December/007403.html December].

==== Date Fields ====

Brian's original straw format had three date fields, "accessed", "copyrighted", and "published".
After examining the examples of usage on the web, it was clear that 'copyrighted' was not used in the examples we have.
It was used once, but without a corresponding 'published' field (OCLC WorldCat), and it seems in that case to be used as
an equivalent to 'published'.

I updated the straw citation to include only 'accessed' and 'published' on January 31. --[[User:Mike|Mike]] 00:26, 31 Jan 2007 (PST)

I've mentioned more than once that "date-published" is misleadingly specific; too much for real world citations. Consider that many books are published in the year preceding their copyright date, which is in fact the date used for citation. I'd prefer just "date" and "date-accessed" as a first cut. --[[User:BDarcus|Bruce]] 3 Feb 2007

See the discussion from the [http://microformats.org/discuss/mail/microformats-discuss/2007-January/008175.html 'dates' thread on the list].

==== Container ====

Discussion about how to represent containing relationships is on the thread [http://microformats.org/discuss/mail/microformats-discuss/2007-March/thread.html 'nesting container elements']

== Old straw format discussion ==

Saved here so that I'm not just deleting people's comments.

=== Mike straw format suggestion (Deprecated) ===

In the interests of starting debate and having something concrete to fix, I suggest the following structure for a format. It is probably very incomplete and I claim no microformat expertise. I'm just trying to follow existing patterns. Comments and ridicule are both solicited. -Mike

'''NOTE:''' This format is here for historical reference. Because it was not based on existing examples, I've deprecated it and contributed examples to Brian's format. If you feel that any missing elements in here should be in the final format, find examples for them and contribute to Brian's schema. Thanks! --[[User:Mike|Mike]] 18:22, 12 Oct 2006 (PDT)

==== In General ====

The ''citation'' format is based on a set of fields common to many bibliographic data formats, which are often implied by standard citation display styles but not explicitly marked up in practice on the web.

==== Schema ====

The citation schema consists of the following:

* cite
** title: required, text (class = fn)
** subtitle: optional, text
** authors: optional, use hCard
** publication date: optional
** link(s) to instantiations, optional, url or use rel-enclosure? (class=url)
** UID, optional (for ISBN, DOI - use existing uid class) | permalink
** series (aka volume/issuenum) , optional (''not as sure how to handle these - suggestions?'')
** pages: startpage & endpage, optional, text
** venue, optional (hCard)
** publisher, optional (hCard)
** container: optional (nested hCite)
** abstract, optional (blockquote + class="abstract" ?)
** notes, optional (blockquote + class="notes" ?)
** keywords, optional (rel-tag)
** image, optional (for inclusion inline, unlike the url)
** copyright, optional (rel-license)
** ''what else am I missing?''
*** language, optional

''Looks good, but I question the use of hCard for names. Due to ambiguity issues, requring hCard would lead to extra markup in order to apply just a name, hence [http://microformats.org/discuss/mail/microformats-discuss/2006-March/003487.html the need for a root element]. We should extract the N optimization of hCard like we did with adr, in order to ease this problem.'' --[[User:RCanine|Ryan Cannon]]

Perhaps a Retrieved Date or Access Date would be appropriate for citing online resources. For example at http://www.crlt.umich.edu/publinks/facment_biblio.html
you see citations like this<nowiki>:</nowiki>
<blockquote>
Chief Academic Officers of the Big 12 Universities (2000). Big 12 Faculty Fellowship Program. Retrieved December 20, 2000 from the World Wide Web: http://www.k-state.edu/provost/academic/big12/big12guide.htm.
</blockquote>
--[[User:JoeAndrieu|Joe Andrieu]]

==== Discussion about citing legal cases ====

Here's some info I found about citing law:

I'm not a lawyer, so I'm relying on the published [http://www.legalbluebook.com "blue book" standard], at least the only part of it I can get without paying $25. I'd be happy to hear improvements from experts in the field - how do lawyers mark up references to case law in HTML now?

From groklaw.net and eff.org, I find mostly just links to PDFs with the name of the case as the link text. Or just this, from EFF:
<pre><nowiki>
<h1>The Betamax Case</h1>
<h2>Sony Corp. of America v. Universal City Studios, 464 U.S. 417 (1984)</h2>
</nowiki></pre>

From an example at the sample bluepages: http://www.legalbluebook.com/pdfs/bluepages.pdf
5 basic components:
*1 name of the case (citation title)
*2 published source in which case may be found (citation containing publication?)
*3 a parenthetical indicating the court and year of decision (citation venue?)
*4 other parenthetical information, if any (citation notes?)
*5 subsequent history of the case, if any (citation notes?)

Here's two examples from the bluebook. Note that there are very strict rules about abbreviations in that source!

Holland v. Donnelly, 216 F. Supp. 2d 227, 230 (S.D.N.Y. 2002), aff'd, 324 F.3d 99 (2d Cir. 2003).

Green v. Georgia, 442 U.S. 95, 97 (1979) (per curiam) (holding that exclusion of relevant evidence at sentencing hearing constitutes denial of due process).

== Examples in the wild ==
Pages which start to use the discussion above to create working examples in using hcite:
(This section could be used as a base for a page like "hcite-examples-in-wild" later).

Please add new examples to the top of this section.
* [http://www.demo.vorlagen.uni-erlangen.de/univis/mitarbeiter.shtml/georg-hager.shtml Example User Page] at the regional computer lab Erlangen, Germany, based on the universal information system UnivIS marked up with vcard, hcalender (optional, if user makes a lecture) and hcite.

== discussions ==
* [[citation-irc-notes-2006-04-09]]

citation-issues

2007-04-09T00:11:27Z

BenWest: added andy's comment about citation format conversion.

citation-brainstorming

2007-04-08T23:58:09Z

BenWest: moved ThomasBreuel's requirements into an issue page... about to move more issues there as well.

<h1> Citation Brainstorming </h1>

== See also ==
* [[citation]]
* [[citation-examples]]
* [[citation-formats]]
* [[citation-faq]]

__TOC__

== Contributors ==

* ...
* ... (a bunch of good folks!)
* Tantek Çelik
* Tim White
* Michael McCracken
* Brian Suda
* [[User:AndyMabbett|Andy Mabbett]]

== Use Cases ==

To focus the discussion, please add use cases below that will help show what problems the citation microformat will be solving.

I've included two, focusing on consuming information - I've assumed that use cases for generating microformatted content would just involve the desire to enable your content to be consumed better, but I'm interested to see if there's something I'm missing here -Mike

=== Acquiring reference information from the web ===

A user either finds an author's papers page, or is viewing the results of a search and would like to import the information about the displayed papers into their local reference database, for the purposes of cataloging things they've read, adding notes, and using the information to generate later citations, potentially in other forms, such as BibTeX or Docbook, for inclusion in a publication of their own.

Notes: In this case, it isn't important to the user what format the citation takes as displayed on the page where they find it. What *is* important is that it contains enough information to allow generation of the format they will ultimately re-publish it in. This implies that it may be worthwhile to err a little on the side of verbosity.

Also, links to downloadable full representations of the cited work are very important - e.g. a link to the PDF of a journal article, or to a music file.

=== Subscribing to reading lists, periodicals, etc ===

I would like to be able to leverage my news aggregator with hAtom to subscribe to a remote source for citation information, for example:

* a reading list for a seminar
* The publication list for a conference (e.g., subscribe to SIGGRAPH and see the updated conference proceedings every year)
* the issues of a journal
* a particular research group or researcher's publications
* Not just research: a popular author's publications (e.g., [http://www.gladwell.com/archive.html Malcolm Gladwell's Archive])

=== Aggregating reading lists and reviews ===

A citation microformat-specific aggregator could provide a decentralized version of [http://citeulike.org/ CiteULike]. Libraries, authors, research groups, and publishers could mark up their collections, while other people on weblogs or review sites could add tags and reviews.

At least, having a well-adopted microformat would make writing tools like CiteULike much better, since it relies in some cases on screen-scraping publisher web-sites.

=== Cut & Paste from web pages ===
Capturing/copying HTML from web pages for use in other applications (especially when those apps present HTML as output), such as pasting into Word, or a specialized application like [http://www.google.com/notebook Google Notebook], [http://onfolio.com Onfolio] or [http://www.kaboodle.com Kaboodle]. When such captures are made, it makes sense to keep track of the full citation data, including the date it was accessed, which may or may not be the date it was published.

=== Blogs quoting other resources, including blogs ===
Any blog that cites online content, whether a blog or news article, could use an hCitation to properly link to the cited reference. Such citations could include the access date when the blogger made the citation, because resources on the other side of those links can change without notice.

Instead, today we have simple formating with a link to the permaURL. The citation data is completely lacking. See [http://doc.weblogs.com Doc Searl's blog] for a style of referencing that could benefit from proper a citation uF.

Fascinating... after I added the last two use cases, I realized they focus on potentially marginal cases. The first because it is missing the "output" part of the cut & paste, where the uF would actually be used as part of the paste. The latter because bloggers have a working citation mechanism that is just a link to the URL (hopefully a permaURL). One could argue they wouldn't want a full hCitation. And in fact, until a tool exists that makes it easy, they probably won't. However, a tool that cuts & pastes from anywhere on the web into a blog with a full citation seems like a nice tool. But again, I'm not really paving the cowpaths with these ideas. -Joe Andrieu

===Finding in Library===
Find a copy of the cited work in a nearby library (as with [http://ocoins.info/ OpenCOinS]). [[User:AndyMabbett|AndyMabbett]] 04:55, 4 Nov 2006 (PST)

===Buy a copy===
Find the cited work on, for example, Amazon or [http://www.abebooks.com/ ABE]; or subscribe to a journal via its own website. [[User:AndyMabbett|AndyMabbett]] 04:55, 4 Nov 2006 (PST)

===Find reviews===
Find third-party reviews of the cited work. [[User:AndyMabbett|AndyMabbett]] 04:55, 4 Nov 2006 (PST)

===Give citation data for the page being visited===

Adding a class of, say, "self" to an attribute of the proposed strawman would allow users (or user agents) to extract the data required to cite the page being visited, when referring to it elsewhere. There would be the added advantage of allowing the citation to be ignored by any parser which might be building a "tree" of citations, and preventing the setting up of an infinite loop.

For evidence of published "self citation" data (albeit on a secondary page) see the "cite this article" link on any Wikipedia entry, e.g. [http://en.wikipedia.org/w/index.php?title=Special:Cite&page=West_Midland_Bird_Club&id=115894372] from [http://en.wikipedia.org/wiki/West_Midland_Bird_Club].

See also [http://en.wikipedia.org/wiki/Wikipedia_talk:Citing_Wikipedia#Citation_data_should_be_on_the_page_concerned Proposal to include on-page citation data in Wikipedia]

:[[User:AndyMabbett|Andy Mabbett]] 13:47, 20 Mar 2007 (PDT)

===Convert citation formats===
A user agent should be capable of reading a citation from a web page, in a given format, and converting it into a second format, for use elsewhere. For a list of such formats, and examples, see [http://en.wikipedia.org/wiki/Citation#Format_styles Wikipedia, Citation styles]. [[User:AndyMabbett|Andy Mabbett]] 11:05, 30 Mar 2007 (PDT)

==Examples==
* (from a mailing list):
:<blockquote>if you want to cite a [biomedical journal] journal article on Wikipedia [...] you can export a correctly-formatted citation for Wikipedia from HubMed using unAPI... http://hublog.hubmed.org/archives/001408.html</blockquote>

*[http://www.zotero.org/ Zotero], a Firefox extension to help collect, manage, and cite research sources.
:[[User:AndyMabbett|Andy Mabbett]] 09:13, 21 Mar 2007 (PDT)

== Original hBib Discussion ==

During the WWW2005 Developer's Day [[microformats]] track, Rohit Khare gave a [[presentations|presentation]] where he discussed the microformats [[process]], and then did a quick demonstration wherein a bunch of us got on a shared Subethaedit document, and brainstormed some thoughts on what an "hBib" bibliography citation microformat would look like. Rohit placed the [http://cnlabs.commerce.net/~rohit/hBib%20Discussion.html document on his Commercenet site].

* http://cnlabs.commerce.net/~rohit/hBib%20Discussion.html

''An attempt to summarize and inline the linked document follows. -Mike''

Two major goals were outlined by the group:

* Avoid re-keying references
* Adapt to new journal styles by changing CSS

The fundamental problem was discussed in terms of display - the ability to transform XHTML+hBib into the many journal-specific formats. For example, how to display "et.al" when all authors are present in the source, and how to re-order the elements if a style defines a set order of elements that conflicts with the ordering in the source. Using hCard for authors was agreed on, and the beginnings of an example were shown.

== XHTML Structure ==
With my exprience working X2V and hCa* has taught me what elememts are easy to find and which are not. Since the Citation microformat is very new it is possible to not make a lot of the same errors twice and to make things easier for extracting application to find and imply certain properties.

* There should be some sort of 'root node' that implies all child elements are for the hCitation microformat.
* Since most people will have multiple citations there should be away to represent each hCitation object as a unqiue block independent of another. This is to keep the parse from finding 'author' and applying that to all citations. Each citation should be in a container (class="hcite") that is separated from others.
* Perhaps class="hcite" with <code><cite></code> recommended as the root element. E.g. <code><cite class="hcite"></code>

'''Note: This section was the original content of the document. Since then, class='hcite' has been agreed on as the root class name. See [http://microformats.org/wiki?title=citation-brainstorming#.27hcite.27_as_Root_Element_name explanation].'''

== Citation vs. [[media-info]] ==

What distinguishes a cite from say [[media-info]] (e.g. [[media-info-examples]]) is that a cite is a reference to something explicitly external to the current piece of content or document, whereas [[media-info]] describes information about content embedded or inline in the current document.

== Semantic Meaning ==
One of the guiding priniciple of Microformats is to use the most semantically rich element to describe each node (Point 2 of Semantic XHTML Design Principles: Use the most accurately precise semantic XHTML building block for each object etc). Since we are dealing with HTML and citations, several elements are candidates to be used to enrich the semantic meaning. [http://www.w3.org/TR/REC-html40/struct/text.html CITE, BLOCKQUOTE, Q, A], (are there more?)

The [[citation-brainstorming|Citation Brainstorming Page]] has a few development and ideas about how to give another person credit for a link. Some of the semantic ideas behind their choices of tags can be applied to a full bibliographic type reference. ''Does this sentence make sense only historically? -Mike''

== OCLC's WorldCat for titles ==
Question: what about using something like OCLC's [http://www.oclc.org/worldcat/open/isbnissnlinking/default.htm WorldCat] for linking titles? - Tim White

== This and That ==
After reading through alot of different citation encoding formats, i noticed that each format was being used in onw of two ways. It was either to describe the Current page (THIS.PAGE) or being used to encode references that point to external resources (THAT.PAGE)

The informatation being encoded was identical for both resources (author, date, name, etc) they just reference different things. For this microformat, i'm not sure if we want to try to solve both problems, or just one? The meta tags in the head element would be the ideal place for information about the THIS.PAGE, but that is not in following with the ideals of microformats where information is human-readable. The THAT.PAGE idea where a list of references is at the end of a document in the form of a bibliography is more inline with the ideals of a microformat where the data is human-readable. That doesn't mean that data about the current document shouldn't be human-readable, so some of the same properties used to reference extermal resources can be used for the current document (THIS.PAGE). To do this a different root item could be used and transforming applications could either extract the citation data about the current page, or information about this page's references.

This is open for discussion, but either way, i believe that the properties used to describe a page will be the same for both THIS and THAT. [http://suda.co.uk/ brian suda]

== More on This and That ==

Citation microformats are being explored as a possibility for citing genealogical information at [http://eatslikeahuman.blogspot.com Dan Lawyer's blog].

This is a case where frequently the citation would refer to (THIS.PAGE), but would have nested within it a reference to (THAT.PAGE), possibly a few levels deep. For instance, a web page might contain data extracted from a microfilm of a census. The citation would need to include information about the web page, information about the microfilm, and information about the census. Genealogical citations are expected to include the repository (where can this book or microfilm be found. Is this the same as ''venue''?). So, at each level the information should contain the repository of the referenced item. A nesting (recursive) mechanism for citation microformats would be useful in this case. Is this the function of the "container" element in the Straw Format?

== Date Formatting ==
Since microformats are all about re-use and the accepted way to encode Date-Time has been pretty much settled, then this is a good place to start when dealing with all the different date citation types.

These are all the different fields from various citation formats that are of temporal nature:
* Date (available | created | dateAccepted | dateCopyrighted | dateSubmitted | issued | modified | valid)
* originInfo/dateIssued
* originInfo/dateCreated
* originInfo/dateCaptured
* originInfo/dateOther
* month
* year
* Copyright Year
* Date - Generic
* Date of Confernce
* Date of Publication
* Date of update/revisou/issuance of database record
* Former Date
* Entry Date for Database Record
* Database Update
* Year of Publication

There are several common properties across several citation domains and will certainly be in the citation microformat, the unique instances will need further consideration, otherwise there could be no end to posiblities.

There are also several properties (year, month, Year of publication) that can be extracted from another source. Therefore, if you only encode a more specific property such as; Date of Publication, you can extract the 'year of publication' from that. Since the date-time format we are modeling after is the ISO date-time format, just the Year portion is an acceptable date. So if you ONLY know the year of publication, the you can form a valid 'Date of Publication' as a microformat (which inturn is a valid 'year of publication') - you milage may vary when it comes to importing into citation applications.

...

It seems to me that these can be collapsed to maybe one or two different date properties. As far as the specific human readable formatting of the date, that can be chosen per whatever the presentation style guide says, and the [[datetime-design-pattern]] used to simplify the markup. - Tantek

'''Important'''
Sometimes we need a date range and not simply a date (e.g. 4-6 May 2006). See ''Conference Citation'' examples later on this page. - Discoleo

'''Seasons'''
Some journals have seasonal issues (e.g. "Summer 2006 edition") instead of, or as well as, editions labelled by month or other calendar-date. [[User:AndyMabbett|AndyMabbett]] 05:05, 4 Nov 2006 (PST)

== Tags ==
Some of the citation formats has a place for 'keywords' or 'generic tags', etc. This might be a good place to re-use the [http://microformats.org/wiki/rel-tag RelTag microformat]. The downside would be that they are then forced to be links, which might be the correct way to mark-up these terms.

== MARC / MODS / Dublin Core ==

The MODS ([http://www.loc.gov/standards/marcxml/Sandburg/sandburgmods.xml example]) and Dublin Core ([http://www.loc.gov/standards/marcxml/Sandburg/sandburgdc.xml example]) transformations of MARC21 may contain some useful ideas.

Here's a first attempt at rewriting the linked examples in XHTML (written in response to a [http://microformats.org/discuss/mail/microformats-discuss/2005-December/002438.html mailing list query about encoding book information with microformats]):

<pre><nowiki>
<div class="book" lang="en">
<h3 class="fn">Arithmetic /</h3>
By Sandburg, Carl,
1878-1967,
and Rand, Ted
Publisher: Harcourt Brace Jovanovich,
San Diego
Published: 1993
A poem about numbers and their characteristics. Features
anamorphic, or distorted, drawings which can be restored to normal by viewing
from a particular angle or by viewing the image's reflection in the provided
Mylar cone.
One Mylar sheet included in pocket.
Subjects:
<ul>
<li class="subject">Arithmetic</li>
<li class="subject">Children's poetry, American.</li>
<li class="subject">Arithmetic</li>
<li class="subject">American poetry</li>
<li class="subject">Visual perception</li>
</ul>
</div>
</nowiki></pre>

== Basic Citation Stuctures ==
There are basic structures to any citation, this is an overview of some of the types
[http://www.users.muohio.edu/darcusb/misc/citations-spec.html http://www.users.muohio.edu/darcusb/misc/citations-spec.html]

== Concerns not addressed by existing formats ==

There are some aspects '''NOT adequately''' covered by existing formats. I have addressed this issue on the OpenOffice.org wiki page, too. [see http://wiki.services.openoffice.org/wiki/Bibliographic_Database for an extending discussion, the paragraph on ''Reference Types'']

These issues pertain mainly to '''Errata''', '''Comments and Authors Reply''' and '''Article Retractions'''.
* a bidirectional link could be necessary to implement these features (original article <=> eratum, reply, retraction letter)
* '''IMPORTANT: Errata'''
** Erata: one or more Corrections might be posted in various issues of the journal
** this is usually cited as: Orininal Article Citation Data (Correction available in ''Journal, Issue Nr, Year, Pages'') (repeat for more than one correction)
** it is possibly never cited alone
** there should be a link to the original article, while the original article should contain a link to this ''Errata''
* '''IMPORTANT: Commentary and Author Reply'''
** similar to Errata, there might be one or more Comments and Author Replys; this should be stored, too
** however, it is usually not included in the original citation
** it might be used however in a citation, but I do not know exaclty how to cite it optimally (original article should be provided as well)
* '''IMPORTANT: Article Retraction'''
** an article may be retracted because of plagiarism or some other flaw
** this should not be used any further in the research
** however, it might be used e.g. for an article on plagiarism or flawed research
** there should be therefore one field storing this information, too, and a link to:
** the published withdrawal letter (which explains why the article was retracted)

* this issue may need a time-controlled event
* '''IMPORTANT: electronic publishing ahead of print (EPUB)'''
** more and more articles are initially posted online, before the published article gets actually printed
** How should this be used/cited?
** Is this changed, after the print version becomes available?

== Outstanding Issues ==
The 3 main points i (Brian) came across so far are:
1) IDENTIFIERS
2) FORMAT TYPES
3) NESTING

1) In hCard/hCalendar there is a UID field. Added with URL it makes for a great unique identifier. There are loads of other identifers besides URL, ISBN, LOC call number, SKU, ISSN, etc. Many of these are unique in their domain, but not globally unique. So how to they get marked-up? Much like the hCard TEL/ADR properties, we can use something like:
<pre>
<nowiki>
<div class="uid">ISBN: 123456</div>
</nowiki>
</pre>
This makes the encoding the most extensible... if we start use class="isbn" then it is an enumerated list, with class="type" it is open ended.

2) I keep mis-using "format", format is the medium - hardback, softback. The TYPE (there probably is a better word - container?) is book, article, conference, manifesto, etc. Much like the identifers we can make an enumerated list of values, class="book", class="article", but that boxes us in, whereas something like: <pre><nowiki>article</nowiki></pre> leaves things more open.

3) Nesting citation data in a citation. The ability to nest the same microformat inside itself is something that other microformats don't explicitly handle.

The two options are:
i) Using class="book"
<pre>
<nowiki>
<div class="hcite">
<div class="book">
Book Title
<div class="chapter">
Chapter Title
</div>
</div>
</div>
</nowiki>
</pre>

This makes things easy to nest and to figure out exactly what is
associated with what, but the downside is that we have enumerated
lists of values for the class properties.

ii) using the TYPE for book
<pre>
<nowiki>
<div class="hcite">
<div class="type">book</div>
Book Title
<div class="type">chapter</div>
Chapter Title
</div>
</nowiki>
</pre>

now the class="fn" is not nested inside the class="book" or
class="chapter" so there would have to be some other mechanism to
associate the data with the type.

== Brian's straw format ==

=== implied schema (examples) ===
+ publisher
+ language
+ description
+ title
+ creator
+ journal
+ volume
+ issue
+ page
+ edition
+ identifier
+ tags
+ format
+ date published
+ copyright
- audience

=== implied schema (formats) ===
+ publisher
+ language
+ description
+ title
+ creator
+ volume
+ pages
+ edition
+ issue
+ identifier
+ tags
+ format
+ date published
+ date copyrighted
- subtitle
- image
- excerpt
- index terms
- series title
- publication
- journal
- part (1 of X)

UNION of the two schemas
+ (PLUS) means common properties
- (MINUS) means unique to the schema

=== Working straw schema ===

This list records discussion about the common schema from above. The format is ''descriptive-name'' (''optional-recommended-element'' 'class-name') (''link to explanation'').

If there is no explanation link, that field should be considered either obvious or up for debate. If you're not sure which, it's up for debate.

* root element ('hcite') ([http://microformats.org/wiki?title=citation-brainstorming#.27hcite.27_as_Root_Element_name explanation])
** title ('title')
** Author / Editor etc. ('creator')
** Pages ('pages')
*** note: this can be any value
** container ('container hcite')
*** A nested hcite element that represents a containing item (like a book for a chapter) ([http://microformats.org/wiki?title=citation-brainstorming#Container discussion and link to mailing list thread])
** Volume Number ('volume')
** Edition ('edition')
** Issue number ('issue')
** Tags (href rel='tag')
** Format ('format')
*** Note - this is unclear at present - does format mean 'type', as in 'book' vs. 'article'? --[[User:Mike|Mike]] 22:53, 16 Jan 2007 (PST)
** date published ('date-published') ([http://microformats.org/wiki?title=citation-brainstorming#Date_Fields explanation])
** date accessed ('date-accessed') ([http://microformats.org/wiki?title=citation-brainstorming#Date_Fields explanation])
** publisher
** language
** Abstract / description ('description')
** URI (href class='uri') ([http://microformats.org/wiki?title=citation-brainstorming#The_URI_Element explanation])
** identifier
*** an (not necessarily globally unique) identifier, such as a cite-key, pubmed ID number, or simply the reference number or string within a publication ([1] or [CLRS2001])

==== Notes about missing / changed fields in the schema ====

This section lists fields that are intentionally ''not'' included in the straw schema, or are not represented directly, and links to discussion about each.

* date copyrighted ([http://microformats.org/wiki?title=citation-brainstorming#Date_Fields explanation])

=== Examples ===

Markup examples using the above format:

==== Book ====

This is Brian's original example

<pre>
<nowiki>
<ul class="bibliography">
<li class="hcite" xml:lang="en-gb">


<div class="creator vcard">
John Doe
...
</div>


Foobar!
World Class Book about foobar
1
1
1
1-10
article


12345678


<a class="keyword" rel="tag" href="/tags/foo">foo</a>
bar


Published <abbr class="date-published" title="20060101">January 1st 1006</abbr>
Copyright <abbr class="copyright" title="20060101">2006</abbr>
</li>
...
</ul>

Have you read <abbr title="book" class="format">Foo Bar</abbr>?
It was written by John Doe.
It only came out a <abbr class="dtpublished" title="20060101">few months ago</abbr>
</nowiki>
</pre>

Note: the "format" property above is incorrect. Format would refer more the physical characteristics of an item, rather than its type or genre (e.g. "article", "book", etc.). I'd rather have the main class for the li be "article" in this context, than the fairly meaningless "citation." Of course, one could have both, which would be fine too. -- bruce

Note: Could we use ROLE from hCard to identify editors, translators, authors, etc?
This was discussed on the mailing list and the idea was dropped [http://microformats.org/discuss/mail/microformats-discuss/2006-September/005694.html]

'''Comments''' : [[User:Singpolyma|singpolyma]] 08:03, 16 Jun 2006 (PDT) : keywords should be [[rel-tag]], and probably also [[XOXO]] (the same way the citation list is)

[[User:RCanine|RCanine]] 11:55, 18 Dec 2006 (EST) :

* Is there a reason not to re-use "published" from hAtom instead of inventing a new, basically equivalent term in "dtpublished"?
** note - date-published was decided on for the field, example changed to reflect it --[[User:Mike|Mike]] 10:12, 30 Mar 2007 (PDT)
* Missing a URL/URI/IRI/UID etc. field example (ISBN for Book).
* Does the "copyright" class conflict with [http://www.whatwg.org/specs/web-apps/current-work/#class WHATWG's definition]?
* WRT Bruce's comment, I'm currently using class="article citation" for my writing, as it has the most flexibility with CSS styles for titles (e.g. Book titles .citation>.fn must be italicized, while article titles must not, their container should).
* Speaking of containers, we need an "in" or "collection" field for journal articles or articles-in-books, or is that covered by "publisher"?

==== Citing Private Communication ====

Needs an example.

==== Citing Legal Cases ====
Needs an example.
see [http://microformats.org/wiki/citation-examples-markup#Wikipedia_Court_Case Wikipedia example] for inspiration.

==== Citing a Book ====

needs an example

==== Citing a journal article ====

From an old entry in PubMed - J Aersp Med. [http://www.ncbi.nlm.nih.gov/entrez/query.fcgi?db=pubmed&cmd=Retrieve&dopt=AbstractPlus&list_uids=4611181&query_hl=7&itool=pubmed_docsum link]

<pre><nowiki>

R R Burton,
S D Leverett, and
E D Michaelson

Man at high sustained +Gz acceleration: a review.
In 
<abbr class="type" title="Journal">J.</abbr><abbr class="title" title="Aerospace medicine">Aersp. Med.</abbr>
urn:issn:0001-9402
45
10
<abbr class="date-published" title="101974">Oct, 1974</abbr>
, pages 1115-36.



</nowiki></pre>

Note, I'm not entirely sure about the issn urn here.

==== Citing a magazine article ====

needs an example

==== Citing a Patent ====

Drawn from this [http://microformats.org/wiki/citation-examples#U.S._Patent example from Wikipedia]:

<pre><nowiki>
<li class="hcite"><a href="http://patft.uspto.gov/netacgi/nph-Parser?patentnumber=4,405,829" class="url"
title="http://patft.uspto.gov/netacgi/nph-Parser?patentnumber=4,405,829">
U.S. Patent 4,405,829</a>:
The <a href="/wiki/RSA" title="RSA">RSA</a> patent, a famous software patent on the ground-breaking
and highly unobvious algorithm for public key encryption, widely used for secure communications
in many industries nowdays
</li>
</nowiki></pre>

==== Citing a conference publication====

Based on the [http://microformats.org/wiki/citation-examples#ACM_Digital_Library_Search_Result_Examples conference publication reference example].

Changed Oct 06 to conform with [http://microformats.org/wiki/citation-brainstorming#Brian.27s_Straw_format Brian's format]. --[[User:Mike|Mike]] 18:09, 12 Oct 2006 (PDT)
(everything but the url class should be in line with that proposal)

L. Hochstein, J. Carver, F. Shull, S. Asgari, V. Basili, J. K. Hollingsworth, and M. Zelkowitz, “Hpc programmer productivity: A case study of novice hpc programmers,” in Proceedings of ACM/IEEE Supercomputing Conference, 2005.

<pre><nowiki>

Lorin Hochstein
 University of Maryland, College Park ,
 Jeff Carver 
 Mississippi State University ,
 Forrest Shull 
 Fraunhofer Center Maryland ,
 Sima Asgari
 University of Maryland, College Park ,
 Victor Basili
 Fraunhofer Center Maryland ,
 Jeffrey K. Hollingsworth
 University of Maryland, College Park , and
 Marv Zelkowitz
 University of Maryland, College Park ,

<a class="title url" href="http://dx.doi.org/10.1109/SC.2005.53">HPC Programmer Productivity: A Case Study of Novice HPC Programmers</a>.
(conference publication)

<a class="title url" href="...">Proceedings of ACM/IEEE Supercomputing Conference</a>
<abbr class="date-published" title="20051126T0000-0800">2005</abbr>

page 35

IEEE Computer Society


Washington,
DC


<a class="url eprint" href="http://portal.acm.org/...">PDF of full text from ACM</a>

DOI: <a class="url uid" href="http://dx.doi.org/10.1109/SC.2005.53">10.1109/SC.2005.53</a>
Tags:
<a class="keyword" rel="tag" href="results.cfm?query=genterm%3A%22Design%22 ...">Design</a>,
<a class="keyword" rel="tag" href="results.cfm?query=genterm%3A%22Experimentation%22 ....">Experimentation</a>,
<a class="keyword" rel="tag" href="results.cfm?query=genterm%3A%22Measurement%22...">Measurement</a>,
<a class="keyword" rel="tag" href="results.cfm?query=genterm%3A%22Performance%22 ...">Performance</a>

In developing High-Performance Computing (HPC) software, ....

</nowiki></pre>

'''Note''' (From [[Discoleo]], Sept. 06)
* sometimes, the citation must include '''Town/Country''' and '''Precise Date/Date Range''', e.g.
** ''Gillespie SH, Dickens A.'' Variation in mutation rate of quinolone resistance in Streptococcus pneumoniae [abstract P06-17A]. In: Abstracts of the 3rd International Symposium on Pneumococci and Pneumococcal Disease (Anchorage, 5-9 May 2002).Washington, DC: American Society of Microbiology, 2002.
** ''Bassetti, M.; Righi, E.; Rebesco, B.; Molinari, MP.; Costa, A.; Fasce, R.; Cruciani, M.; Bassetti, D.; Bobbio Pallavicini, F.'' 44th Annual Interscience Conference on Antimicrobial Agents and Chemotherapy (ICAAC). Washington, DC; 2004. Epidemiological trends in nosocomial candidemia in ICU: A five-year Italian perspective.
** ''Peacock JE, Wade JC, Lazarus HM, et al.'' Ciprofloxacin/piperacillin vs. tobramycin/piperacillin as empiric therapy for fever in neutropenic cancer patients, a randomized, double-blind trial [abstract 373]. In: Program and abstracts of the 37th Interscience Conference on Antimicrob Agents and Chemotherapy (Toronto). Washington, DC: American Society for Microbiology, 1997.

==== Citing an external website ====

This is based on a formal citation of a website in the references section of a research paper, but could also be used for in-line links that had added information. Here's the original:

[25] David Stern, "eprint Moderator Model", http://www.library.yale.edu/scilib/modmodexplain.html (version dated Jan 25, 1999)

<pre><nowiki>
<cite class="hcite">
<a class="fn url" href="http://www.library.yale.edu/scilib/modmodexplain.html">eprint Moderator Model</a>

<a href="http://pantheon.yale.edu/~dstern/dsbio.html" class="url fn">David Stern</a>

<abbr class="dtpublished" title="19990125T0000-0500">
Jan 25, 1999
</abbr>
</cite>
</nowiki></pre>

=== Discussion of Straw Format elements ===

This section is to provide explanations for posterity about the elements of the straw format, linking to discussions on the list and elsewhere if possible.

==== 'hcite' as Root Element name ====

This discussion took place in January of 2007, with [http://microformats.org/discuss/mail/microformats-discuss/2007-January/008098.html voting occurring on the mailing list].

It was decided to use 'hcite' as the root element's class-name for uniqueness and to reflect a trend in using 'h' to start microformat names.

==== The URI Element ====

It was decided to use URI for both http links to available copies or URNs.
This encompasses URLs that link directly to online copies as well as through resolvers using URIs such as urn:isbn: 0521890012

See the discussion from [http://microformats.org/discuss/mail/microformats-discuss/2006-November/007390.html November] and [http://microformats.org/discuss/mail/microformats-discuss/2006-December/007403.html December].

==== Date Fields ====

Brian's original straw format had three date fields, "accessed", "copyrighted", and "published".
After examining the examples of usage on the web, it was clear that 'copyrighted' was not used in the examples we have.
It was used once, but without a corresponding 'published' field (OCLC WorldCat), and it seems in that case to be used as
an equivalent to 'published'.

I updated the straw citation to include only 'accessed' and 'published' on January 31. --[[User:Mike|Mike]] 00:26, 31 Jan 2007 (PST)

I've mentioned more than once that "date-published" is misleadingly specific; too much for real world citations. Consider that many books are published in the year preceding their copyright date, which is in fact the date used for citation. I'd prefer just "date" and "date-accessed" as a first cut. --[[User:BDarcus|Bruce]] 3 Feb 2007

See the discussion from the [http://microformats.org/discuss/mail/microformats-discuss/2007-January/008175.html 'dates' thread on the list].

==== Container ====

Discussion about how to represent containing relationships is on the thread [http://microformats.org/discuss/mail/microformats-discuss/2007-March/thread.html 'nesting container elements']

== Old straw format discussion ==

Saved here so that I'm not just deleting people's comments.

=== Mike straw format suggestion (Deprecated) ===

In the interests of starting debate and having something concrete to fix, I suggest the following structure for a format. It is probably very incomplete and I claim no microformat expertise. I'm just trying to follow existing patterns. Comments and ridicule are both solicited. -Mike

'''NOTE:''' This format is here for historical reference. Because it was not based on existing examples, I've deprecated it and contributed examples to Brian's format. If you feel that any missing elements in here should be in the final format, find examples for them and contribute to Brian's schema. Thanks! --[[User:Mike|Mike]] 18:22, 12 Oct 2006 (PDT)

==== In General ====

The ''citation'' format is based on a set of fields common to many bibliographic data formats, which are often implied by standard citation display styles but not explicitly marked up in practice on the web.

==== Schema ====

The citation schema consists of the following:

* cite
** title: required, text (class = fn)
** subtitle: optional, text
** authors: optional, use hCard
** publication date: optional
** link(s) to instantiations, optional, url or use rel-enclosure? (class=url)
** UID, optional (for ISBN, DOI - use existing uid class) | permalink
** series (aka volume/issuenum) , optional (''not as sure how to handle these - suggestions?'')
** pages: startpage & endpage, optional, text
** venue, optional (hCard)
** publisher, optional (hCard)
** container: optional (nested hCite)
** abstract, optional (blockquote + class="abstract" ?)
** notes, optional (blockquote + class="notes" ?)
** keywords, optional (rel-tag)
** image, optional (for inclusion inline, unlike the url)
** copyright, optional (rel-license)
** ''what else am I missing?''
*** language, optional

''Looks good, but I question the use of hCard for names. Due to ambiguity issues, requring hCard would lead to extra markup in order to apply just a name, hence [http://microformats.org/discuss/mail/microformats-discuss/2006-March/003487.html the need for a root element]. We should extract the N optimization of hCard like we did with adr, in order to ease this problem.'' --[[User:RCanine|Ryan Cannon]]

Perhaps a Retrieved Date or Access Date would be appropriate for citing online resources. For example at http://www.crlt.umich.edu/publinks/facment_biblio.html
you see citations like this<nowiki>:</nowiki>
<blockquote>
Chief Academic Officers of the Big 12 Universities (2000). Big 12 Faculty Fellowship Program. Retrieved December 20, 2000 from the World Wide Web: http://www.k-state.edu/provost/academic/big12/big12guide.htm.
</blockquote>
--[[User:JoeAndrieu|Joe Andrieu]]

==== Discussion about citing legal cases ====

Here's some info I found about citing law:

I'm not a lawyer, so I'm relying on the published [http://www.legalbluebook.com "blue book" standard], at least the only part of it I can get without paying $25. I'd be happy to hear improvements from experts in the field - how do lawyers mark up references to case law in HTML now?

From groklaw.net and eff.org, I find mostly just links to PDFs with the name of the case as the link text. Or just this, from EFF:
<pre><nowiki>
<h1>The Betamax Case</h1>
<h2>Sony Corp. of America v. Universal City Studios, 464 U.S. 417 (1984)</h2>
</nowiki></pre>

From an example at the sample bluepages: http://www.legalbluebook.com/pdfs/bluepages.pdf
5 basic components:
*1 name of the case (citation title)
*2 published source in which case may be found (citation containing publication?)
*3 a parenthetical indicating the court and year of decision (citation venue?)
*4 other parenthetical information, if any (citation notes?)
*5 subsequent history of the case, if any (citation notes?)

Here's two examples from the bluebook. Note that there are very strict rules about abbreviations in that source!

Holland v. Donnelly, 216 F. Supp. 2d 227, 230 (S.D.N.Y. 2002), aff'd, 324 F.3d 99 (2d Cir. 2003).

Green v. Georgia, 442 U.S. 95, 97 (1979) (per curiam) (holding that exclusion of relevant evidence at sentencing hearing constitutes denial of due process).

== Examples in the wild ==
Pages which start to use the discussion above to create working examples in using hcite:
(This section could be used as a base for a page like "hcite-examples-in-wild" later).

Please add new examples to the top of this section.
* [http://www.demo.vorlagen.uni-erlangen.de/univis/mitarbeiter.shtml/georg-hager.shtml Example User Page] at the regional computer lab Erlangen, Germany, based on the universal information system UnivIS marked up with vcard, hcalender (optional, if user makes a lecture) and hcite.

== discussions ==
* [[citation-irc-notes-2006-04-09]]

citation-issues

2007-04-08T23:56:58Z

BenWest: moving "requirements" from brainstorming to issues.

citation

2007-04-08T23:39:21Z

BenWest: Create link to citation-issues

priorities

2007-03-28T21:40:17Z

BenWest: BenWest's opinions... stubbed out 3 priorities.

Microformateers are successful when pursuing:
* 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.

mailing-list-unmoderation

2007-03-19T19:43:28Z

BenWest: +1 from BenWest

Andy Mabbett was [http://rbach.priv.at/Microformats-IRC/2007-01-04#T011730 moderated (rather than banned for a week) on 2007-01-04] on the microformats mailing lists at the time for both his frequent/excessive off-topic posts, and his ignoring of several warnings from admins to please stop doing so (see microformats-discuss archives for details). Ernie P. (a longstanding overwhelmingly positive contributor to the community) has [http://microformats.org/discuss/mail/microformats-discuss/2007-March/009063.html proposed unmoderating Andy at this point, 2007-03-19]. Please add your opinion at the end:
* +1 Ernie P.
* +1 David Janes
* +1 Nic James Ferrier
* +1 Tantek
* +1 Scott Reynen
* +1 Steve Ganz
* +1 Joe Andrieu
* +1 M. Jackson Wilkinson
* +1 BenWest
* ... add your opinion (+1 unmoderate, 0 no opinion, -1 keep moderated) and your name

===Discussion===
I'm glad to see this issue getting traction. However, I'm curious why Ernie's standing in the community is relevant to the issue of unmoderating Andy. Tantek, could you explain why that has been presented as an integral part of this decision making process?

Clearly, personal clout always shapes one's ability to influence the community; however, I doubt it should be officially incorporated in these "proceedings". Shouldn't every member of the community have an equal hearing under whatever governance procedures we use?
--[[User:JoeAndrieu|JoeAndrieu]] 09:38, 19 Mar 2007 (PDT)--

:[http://microformats.org/discuss/mail/microformats-discuss/2007-March/009066.html Tantek also said]: "''Ernie, as someone who has made overwhelmingly positive contributions to the microformats community, IMHO the occasional OT post is reasonable'".
* I believe the statement was added to give context to the appealing member of the community. i.e. Ernie is a long standing, good contributor, as opposed to someone new who has no experience with this particular community or someone who has had little or no interaction with the community until now, and also negates it being a personal statement (rather he is interested in community as a whole, instead of being a friend of the Andy and having a personal goal, for example). Basically, he is a person with a certain amount of credibility and trustworthiness. [[User:Phae|Phae]] 10:25, 19 Mar 2007 (PDT)

advocacy

2007-03-18T03:22:03Z

BenWest: /* hAtom */ added the use case where hatom can be used for log files.

= Advocacy =

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

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

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

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

== Adding Microformats to Existing Sites ==

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

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

==== Online Profiles ====
Nearly every website that has a login has a page representing the public profile of the user that other users can see and interact with. Many such sites already [[hcard-implementations|support hCard]] (e.g. ClaimID.com, Flickr.com, Technorati.com, Zooomr.com). Here are some that I think would benefit from the addition of hCard to their profile / user pages. Feel free to add more such sites that have a social network profile-like component and I'll see what I can do. [[User:Tantek|Tantek]] 17:44, 13 Dec 2006 (PST)
* [http://jpgmag.com/ JPG magazine] - have sent email to their web developer with sample marked up member profile with [[hcard|hCard]] and [[xfn]] [[rel-me|rel="me"]]. [[User:Tantek|Tantek]] 23:48, 21 Feb 2007 (PST)
* Twitter.com - working on it [[User:Tantek|Tantek]] 17:44, 13 Dec 2006 (PST)
* Consumating.com - working on it [[User:Tantek|Tantek]] 17:44, 13 Dec 2006 (PST)
* Wikimedia - including this site, Wikipedia (See [http://en.wikipedia.org/wiki/Wikipedia:WikiProject_Microformats WikiProject Microformats]), Wikitravel, etc.
**It would be nice if <nowiki>[[User:YOURNAME]]</nowiki> links generated proper (mini)hCards. ([http://microformats.org/wiki?title=to-do&diff=12177&oldid=12173#Lazyweb per SteveIvy]; moved from 'to-do')

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

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

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

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

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

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

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

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

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

====Other hCard====
* [http://www.imdb.com/ Internet Movie Database] (IMDb) for people (real, not characters), e.g. [http://www.imdb.com/name/nm0000007/ Humphrey Bogart]. [[User:AndyMabbett|Andy Mabbett]] 02:49, 13 Nov 2006 (PST)
**Can't find contact info! [[User:AndyMabbett|Andy Mabbett]]
*Wikitravel
**e.g. [http://wikitravel.org/en/Birmingham_%28England%29 Wikitravel - Birmingham]
***[http://microformats.org/wiki?title=User_talk:MarkJaroski&curid=2699&diff=0&oldid=10663&rcid=19955 Wikitravel is about to hugely roll out hCard] Mark Jaroski
***See also [http://wikitravel.org/en/Wikitravel:Microformats Wikitravel:Microformats]
*[http://orlabs.oclc.org/Identities/ WorldCat Identities]
**The recently prototyped WorldCat Identities provides pages for 20 million 'identities', mainly authors and people who are the subjects of published titles.
**Requested by feedback form, 2007-03-09 [[User:AndyMabbett|Andy Mabbett]]

===hCalendar===

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

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

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

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

====Government hCalendar====
=====UK Gov. hCalendar=====
*[http://www.dti.gov.uk/employment/bank-public-holidays/index.html DTI: Bank Holidays] (not Scotland)
** Requested by e-mail, 2006-11-13 [[User:AndyMabbett|Andy Mabbett]]
***Response: "At the moment we have no plans to use hCalendar or hCard coding due to unresolved concerns about accessibility issues (especially text-to-speech readers), however, we thank you for your suggestion."
***Request for clarification of concerns unanswered.
*[http://petitions.pm.gov.uk/ E-petitions] (in draft, and asking for suggested improvements}
** Requested by e-mail, 2006-12-01 [[User:AndyMabbett|Andy Mabbett]] 11:47, 1 Dec 2006 (PST)
*** reply: "I've added it to our list of ideas." 2006-12-04 [[User:AndyMabbett|Andy Mabbett]] 11:07, 4 Dec 2006 (PST)
*[http://www.scotland.gov.uk/Publications/2005/01/bankholidays Scottish Executive Bank Holidays]
** Requested by [http://www.scotland.gov.uk/About/HaveYourSay/WebsiteFdbck Scottish Executive feedback form], 2006-11-13 [[User:AndyMabbett|Andy Mabbett]]

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

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

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

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

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

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

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

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

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

=== Geo ===
Adding "[[geo|Geo]]" markup to these sites would make them even more useful:
*Wikipedia
**All articles on places, e.g. [http://en.wikipedia.org/wiki/Birmingham Wikipedia - Birmingham] (note co-ordinates already present in infobox)
**See also [http://en.wikipedia.org/wiki/Wikipedia:WikiProject_Microformats WikiProject Microformats]
*Upcoming
**Some events, e.g. [http://upcoming.org/event/128155/ Multipack February 2007] are tagged thus: <code>geo:lat=52.4784</code>, <code>geo:lon=-1.9096</code>. This could be rendered as a geo microformat. [[User:AndyMabbett|Andy Mabbett]]
**[http://community.upcoming.org/w/index.php/Suggestion_Box#Coordinates Geo requested on Upcoming wiki] 2007-01-14
*[http://www.census.gov/cgi-bin/gazetteer U.S. Gazetteer] e.g. [http://www.census.gov/cgi-bin/gazetteer?city=Birmingham&state=&zip=]
*[http://www.world-gazetteer.com/ World Gazetteer] e.g. [http://www.world-gazetteer.com/wg.php?x=&men=gpro&lng=en&dat=32&geo=-81&srt=npan&col=aohdq&pt=c&va=&geo=512945809]
**Requested by e-mail, 2007-01-20 [[User:AndyMabbett|Andy Mabbett]]
*[http://www.genuki.org.uk/cgi-bin/places GENUKI Gazetteer] (UK & Ireland) e.g. [http://www.genuki.org.uk/cgi-bin/maplink?CCC=STS,GR=SP040940,PLACE=Great%20Barr]
**Requested via feedback form, 2007-01-20 [[User:AndyMabbett|Andy Mabbett]]

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

=== VoteLinks ===
* I've added a request for vote-link support in [http://ma.gnolia.com Ma.gnolia]'s link rating system: [http://wiki.ma.gnolia.com/Feature_Suggestions Feature Suggestions on wiki.ma.gnolia.com]

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

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

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

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

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

== Adding Microformats to Applications ==

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

===Browsers===

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

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

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

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

====Opera====
* First reference to "microformats" in the [http://my.opera.com/community/forums/topic.dml?id=169975&t=1166045417&page=1#comment1851680 Opera forums]. 2006-12-13 [[User:AndyMabbett|Andy Mabbett]]
*[http://www.operamini.com/ Opera Mini] (and other browsers on telephones) could especially benefit from recognising the "tel" attributes of hCard, and allowing users to dial numbers found on-line.
**[http://my.opera.com/community/forums/topic.dml?id=169978 Proposed on forum] 2006-12-13 [[User:AndyMabbett|Andy Mabbett]]

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

===Publishing Platforms===

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

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

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

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

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

== Adding Microformats to Web Services ==

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

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

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

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

== Successes ==

=== hCard Successes ===

*Details of hCard should be added to the [http://www.imc.org/pdi/ Internet Mail Consortium's vCard page]
**Requested by e-mail, 2006-11-24 [[User:AndyMabbett|Andy Mabbett]]
**'''Success''' achieved 2006-11-25. [[User:AndyMabbett|Andy Mabbett]]

=== hCalendar Successes===

*Details of hCalendar should be added to the [http://www.imc.org/pdi/ Internet Mail Consortium's vCalendar page]
**Requested by e-mail, 2006-11-24 [[User:AndyMabbett|Andy Mabbett]]
**'''Success''' achieved 2006-11-27. [[User:AndyMabbett|Andy Mabbett]]

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

===Geo Successes===
*Wikitravel
**All articles on places, e.g. [http://wikitravel.org/en/Birmingham_%28England%29 Wikitravel guide to Birmingham, England]
**See also [http://wikitravel.org/en/Wikitravel:Microformats Wikitravel:Microformats]
** '''Success''' achieved 2006-12-13, per [http://wikitravel.org/shared/Tech:Add_SpecialMap_using_Mapstraction_link_for_geo-tagged_pages_and_for_single_listings] see, for example, [http://wikitravel.org/en/Birmingham_%28England%29 Wikitravel guide to Birmingham, England] [[User:AndyMabbett|Andy Mabbett]]

== Comparisons With Alternative Approaches ==

=== CalDAV ===

====Brian Suda====
The other great thing about exposing your data as microformats, is that the data becomes Open Data. Will the general public have access to the CalDAV? (probably not) and even if they did, it will probably only serve-up .ics files... what if i don't want ICS? i need to then hack that around to get it into the format that i want... if the data were in the HTML to begin with, then i could EASILY convert that to any format i wanted. Also, sites like http://pingerati.net/ will happily take in hCalendar data and aggregate it, make your data more valuable and easily slurped up by other providers - i don't see that happening as easily with a CalDAV.

====Kevin Marks====
With respect to CalDAV: I spoke to the CalDAV chaps at Apple about this, they have hCalendar support as a ticket in their db:
http://trac.macosforge.org/projects/calendarserver/ticket/19

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

hreview

2007-03-05T19:11:19Z

BenWest: Reverted edit of Adminis, changed back to last version by RyanKing

<h1> hReview 0.3 </h1>

[[hreview|hReview]] is a simple, open, distributed format, suitable for embedding reviews (of products, services, businesses, events, etc.) in (X)HTML, Atom, RSS, and arbitrary XML. hReview is one of several [[microformats]] open standards.

Want to get started with writing an [[hreview|hReview]]? Use the [http://microformats.org/code/hreview/creator hReview creator] to write a review and publish it.

== Microformats Draft Specification 2006-02-22 ==

; Editor: [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc.]
; Authors: [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc.]
: [http://360.yahoo.com/alidiabali Ali Diab],[http://yahoo.com Yahoo! Inc.]
: [http://spaces.msn.com/members/ianmcallister/ Ian McAllister], [http://microsoft.com/ Microsoft Corporation]
: [http://journals.aol.com/panzerjohn/abstractioneer John Panzer], [http://www.aol.com America Online, Inc.]
: [http://ifindkarma.com/blog Adam Rifkin], [http://labs.commerce.net/ CommerceNet Labs]
: [http://sippey.typepad.com/ Michael Sippey], [http://sixapart.com Six Apart, Ltd]

Microformats [http://microformats.org/wiki/hreview#Copyright copyright] and [http://microformats.org/wiki/hreview#Patents patents] statements apply.

__TOC__

== Introduction ==
Numerous web sites publish reviews using a broad variety of schema for all sorts of things from products (movies, music, books), to businesses (restaurants, hotels, stores), to events (concerts, theatre), to people (artists, leaders, celebrities), to places (landmarks, parks), to online resources (web pages, files), to reviews of reviews themselves.

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

=== Inspiration and Acknowledgments ===
Thanks to everyone who responded to the open call for implementor participation for hReview. The authors in particular wish to thank the following individuals for their constructive input and feedback: [http://www.richardault.com/ Richard Ault], [http://dannyayers.com Danny Ayers], [http://www.vertexdev.com/~jeff/ Jeffrey Barr],[http://adriancuthbert.blogspot.com/ Adrian Cuthbert],[http://jason.defillippo.com/ Jason DeFillippo], [http://www.hybernaut.com/bdv Brian Del Vecchio], Scott Derringer, [http://budgibson.com/home/ Bud Gibson], [http://joi.ito.com/ Joi Ito], [http://www.kanai.net/weblog/ Gen Kanai],[http://niallkennedy.com/ Niall Kennedy], [http://labs.commerce.net/wiki/index.php/Rohit_Khare Rohit Khare], [http://theryanking.com/ Ryan King], [http://www.jluster.org/ Jonas Luster], [http://epeus.blogspot.com/ Kevin Marks], Mark Nottingham, [http://www.powazek.com/ Derek Powazek], [http://www.judysbook.com/ Jeff Rodenburg], [http://sifry.com/alerts/ David Sifry], [http://jystewart.net/ James Stewart], [http://kung-foo.tv/ Adriaan Tijsseling], [http://www.flashenabled.com/ Phillip Torrone], Thai Tran, [http://w6daily.winn.com/ Phillip Winn], [http://yohei-y.blogspot.com YAMAMOTO Yohei].

=== Scope ===
Reviews consistently share several common fields. Where possible hReview has been based on this minimal common subset.

==== Out of scope ====
Fields that are type-specific have been omitted from hReview. It is important that hReview be kept simple and minimal from the start. Additional features can be added as deemed necessary by practical implementation experience.

The concept of a "universal object identifier", that is, how to identify the same object/item/product across different shopping sites, though something very useful to have, is outside the scope of this format.

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

== Format ==
=== In General ===
The hReview format is based on a set of fields common to numerous review sites and formats in use today on the web. Where possible field names have been chosen based on those defined by the related [[hcard|hCard]] and [[hcalendar|hCalendar]] standards.

=== Schema ===
The hReview schema consists of the following:

* hReview ('''<code>hreview</code>''')
** '''<code>version</code>'''. optional. text.
** '''<code>summary</code>'''. optional. text.
** item '''<code>type</code>'''. optional. product | business | event | person | place | website | url.
** '''<code>item</code>''' info. required. '''<code>fn</code>''' ('''<code>url</code>''' || '''<code>photo</code>''' ) | '''[[hcard|hCard]]''' (for person or business) | '''[[hcalendar|hCalendar]]''' (for event)
** '''<code>reviewer</code>'''. optional. '''[[hcard|hCard]]'''.
** '''<code>dtreviewed</code>'''. optional. ISO8601 absolute date time.
** '''<code>rating</code>'''. optional. fixed point integer [1.0-5.0], with optional alternate '''<code>worst</code>''' (default:1.0) and/or '''<code>best</code>''' (default:5.0), also fixed point integers, and explicit '''<code>value</code>'''.
** '''<code>description</code>'''. optional. text with optional valid XHTML markup.
** tags. optional. keywords or phrases, using '''[[rel-tag]]''', each with optional rating.
** permalink. optional, using '''[[rel-bookmark]]''' and '''[[rel-self]]'''.
** license. optional, using '''[[rel-license]]'''.

=== Field details ===
The fields of the hReview schema represent the following:

'''version''':: This optional field permits hReview publishers to specify a particular version of hReview that their content uses. By omitting this field, the publisher is stating that implementations may interpret the hReviews according to any version of the hReview specification v0.2 or later. In practice the authors of this specification are comitted to maintaining backward compatibility with content produced using earlier versions of the specification. This field is syntax compatible with, and thus reuses the semantics of "VERSION" as defined in vCard RFC2426 section "3.6.9 VERSION Type Definition". The value of this field for this specification is "0.3".

'''summary''':: This optional field serves as a title for the review itself.

'''item type''':: This optional field "type" provides the type of the item being reviewed, one of the following: product, business, event, person, place, website, url. If omitted, then in some cases the item type may be inferred. If the item is also an [[hcard|hCard]], then the item type is a "business" or a "person" based upon which of those the hCard represents. If the item is also an [[hcalendar|hCalendar]] event, then the item type is an "event".

'''item info''':: This required field MUST have at a minimum the name ("fn" - the formatted text corresponding to the name) of ''the'' item (an hReview describes only one item), SHOULD provide at least one URI ("url") for the item, and MAY provide at least one URL to a photo or depiction ("photo") of the item. For items of type person or business, the item info (fn, url, photo) MUST be encapsulated in an [[hcard|hCard]]. For items of type event, the item info SHOULD be encapsulated in an [[hcalendar|hCalendar]] "vevent". Unique item IDs (e.g. ISBNs, UPCs) MAY be represented as a URN ("url") for the item. Encapsulated microformats (e.g. [[hcard|hCard]] and [[hcalendar|hCalendar]] events for now) may be set on the item itself (e.g. class="item vcard"). However, when using item info subproperties ("fn", "url", "photo"), they MUST be nested inside the item element.

'''reviewer''':: The optional field specifies the person who authored the review. If the reviewer is specified, an hCard representing the reviewer MUST be provided. For anonymous reviews, use "anonymous" (without quotes) for the full name of the reviewer. If no "reviewer" is found inside the hReview, parsers should look outside the hReview, in the context of the page, for the "reviewer". If there is no "reviewer" outside either, then parsers should use the author defined by the containing document language, e.g. for (X)HTML documents, the <code><nowiki><address></nowiki></code> contact info for the page (which is ideally marked up as an [[hcard|hCard]] as well), for Atom 1.0 the <code><nowiki><entry></nowiki></code> <code><nowiki><author></nowiki></code> if present and if not the <code><nowiki><feed></nowiki></code> <code><nowiki><author></nowiki></code>, for RSS the <code><nowiki><author></nowiki></code> inside the containing <code><nowiki><item></nowiki></code> element.

'''dtreviewed''':: This optional field when present MUST provide an ISO8601 absolute date time of when the review was written or otherwise authored. This field SHOULD use UTC, but MAY use the time zone offset syntax. If dtreviewed is absent from the hReview, then look outside the hReview, in the surrounding context. If the context is an [[hatom|hAtom]] entry, use its "published" (or "updated" if that is missing) datetime as the dtreviewed, if not present on the entry, use the "published" (or "updated" if that is missing) of the feed. Otherwise use the creation date (or modified date if that is missing) information according to the containing document language (e.g. "published"/"updated" similarly for Atom feeds), then protocol (e.g. HTTP Last-Modified, or file system last modified datetime) as the dtreviewed.

'''rating''':: The rating is a fixed point integer (one decimal point of precision) from 1.0 to 5.0 inclusive indicating a rating for the item, higher indicating a better rating by default. Optionally a different integral "worst" value and/or "best" value MAY be specified to indicate a different range (e.g. 6 from 0-10). The "best" value may be numerically smaller than the "worst" value.

'''description''':: This optional field contains the full text representing the written opinion of the reviewer. The field MAY include valid XHTML markup (e.g. paragraphs). User agents SHOULD preserve any markup. Multiple descriptions or section descriptions (e.g. pros and cons, plusses and minusses) SHOULD be included in the description field.

'''tags''':: Tags are represented using a list of keywords or phrases (using the [[rel-tag]] microformat for each individual keyword or phrase tag) that the reviewer associates with the item. The reviewer MAY optionally provide a tag-specific rating inside each [[rel-tag]], e.g. ambience:5. Tag-specific ratings by default use the same range as an overall rating for the item if present, and MAY also have a custom worst...best range specified. Authors MAY also invert this structure for the same semantic if it is more convenient for their markup, that is, place the [[rel-tag]] inside a rating to indicate a rated tag. Note: rated tags should ideally use a tag space that explains what the ratings for that tag mean. E.g. Food:18/30 should link to a tags space for Food that explains what an 18 out of 30 means for the Food tag.

'''permalink''':: This optional field is a URL for the hReview. In addition to using the <code><a href></code> tag for this field, the attribute <code>rel="self bookmark"</code> MUST be used to indicate that the hyperlink is a permalink for the review itself. If the hyperlink already contains a <code>rel</code> attribute, then the values <code>self</code> and <code>bookmark</code> MUST be included among the space-separated set of values in the attribute. Indexers MAY treat the permalink of a review as a unique ID in order to identify and collate the same review from multiple sources (such as indexing a page multiple times). The permalink MAY also be used to indicate or imply the origin of the review. Authors MAY use the classname of "permalink" on the element representing the permalink, but are not required to do so.

'''license''':: This optional field links to the license under which the contents of the hReview itself is licensed, using the '''[[rel-license]]''' microformat.

The following field names have been reused from the [[hcard|hCard]] and [[hcalendar|hCalendar]] microformats: <code>version, summary, fn, url, photo, description</code>. In addition, items and reviewers described by hCards MAY contain any hCard field. The rel value "self" has been reused from the [http://atompub.org/2005/07/11/draft-ietf-atompub-format-10.html Atom 1.0 specification].

=== More Semantic Equivalents ===

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

* For any "url", use <code><a class="url" href="...">...</a></code> inside the element with the class name 'hreview' in hReview.
* And for "photo", use <code><img class="photo" src="..." alt="Photo of ..." /></code>

* Ratings are often presented either as a set of images or characters, e.g. "***". For these, the <code><abbr></code> element is particularly useful, as such characters are an abbreviation for the precise rating, e.g. <code><abbr class="rating" title="3.0">***</abbr></code>. This is further explored in the next section.

==== Language ====
* To explicitly convey the natural language that an hReview is written in, use the standard (X)HTML 'lang' attribute on the element with class="hreview", e.g. <code><div class="hreview" lang="en"> ... </div></code> If portions of an hReview (e.g. the item name) are in a different language, use the 'lang' attribute on those portions.
* hReview processors which need to handle the language of reviews MUST process the standard (X)HTML 'lang' attribute as specified.

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

Similarly, if an <code><img /></code> element is used for one or more properties, it MUST be treated as follows:

# For the "photo" property and any other property that takes a URL as its value, the <code>src="..."</code> attribute provides the property value.
# For other properties, the <code><img /></code> element's '<code>alt</code>' attribute is the value of the property.

=== Object Includes ===

hReview 0.3 includes support for the object [[include-pattern]].

Often a single page lists an item, and then several reviews for that item. In order to avoid having to repeat the item info for each review of the item, the first review should be marked up as an hReview, with a unique "id" attribute on the item info, and then following reviews should use the object [[include-pattern]] to include the item info from the first review.

=== Notes ===
This section is informative.

* By marking up a review with the hReview microformat, the expectation is communicated that the review MAY be indexed. This has no impact on the copyright of the review itself which the publisher may explicitly specify using [[rel-license]] as specified above.
* The enumerated list of item types is under development and may be extended.
* Each type may have custom hReview fields that follow the common set.
* Additional details about a particular item should be specified with the rest of the item's info at the URL provided for the item.
* Most rating systems use the range 1.0 to 5.0, and most of those represent the rating as a number (and possibly half) of stars. Sites may use whatever graphic they wish to represent the rating.

== Examples ==
Here are a few examples of reviews from current web sites, and how they could be easily enhanced to support the hReview structured review microformat.

Want to get started with writing an [[hreview|hReview]]? Use the [http://microformats.org/code/hreview/creator hReview creator] to write a review and publish it on your blog.

=== Restaurant reviews ===

Here is an example of a simple online restaurant review:

<pre><nowiki>
<div>
5 stars out of 5 stars
<h4>Crepes on Cole is awesome</h4>
Reviewer: Tantek - April 18, 2005
<blockquote>
Crepes on Cole is one of the best little creperies in San Francisco.
Excellent food and service. Plenty of tables in a variety of sizes
for parties large and small. Window seating makes for excellent
people watching to/from the N-Judah which stops right outside.
I've had many fun social gatherings here, as well as gotten
plenty of work done thanks to neighborhood WiFi.
</blockquote>
Visit date: April 2005
Food eaten: Florentine crepe
</div>
</nowiki></pre>

Adding hReview to this review is quite simple:

<pre><nowiki>
<div class="hreview">
5 out of 5 stars
<h4 class="summary">Crepes on Cole is awesome</h4>
Reviewer: Tantek -
<abbr class="dtreviewed" title="20050418T2300-0700">April 18, 2005</abbr>
<div class="description item vcard">
Crepes on Cole is one of the best little
creperies in San Francisco.
Excellent food and service. Plenty of tables in a variety of sizes
for parties large and small. Window seating makes for excellent
people watching to/from the N-Judah which stops right outside.
I've had many fun social gatherings here, as well as gotten
plenty of work done thanks to neighborhood WiFi.
</div>
Visit date: April 2005
Food eaten: Florentine crepe
</div>
</nowiki></pre>

Note that some of the properties of this sample review are not captured by hReview (visit date, food eaten). This is deliberate per the scope of keeping hReview minimal and simple.

This sample hReview could be rendered like this:

5 stars out of 5 stars 
'''Crepes on Cole is awesome''' 
Reviewer: Tantek - April 18, 2005 

Crepes on Cole is one of the best little creperies in San Francisco. Excellent food and service. Plenty of tables in a variety of sizes for parties large and small. Window seating makes for excellent people watching to/from the N-Judah which stops right outside. I've had many fun social gatherings here, as well as gotten plenty of work done thanks to neighborhood wifi.

Visit date: April 2005 
Food eaten: Florentine crepe 

==== Multidimensional Restaurant Review ====
Some restaurant reviews indicate ratings for different aspects of the restaurant. Such details are represented in hReview using tagged ratings. In addition, note the inline tags inside the description of this review.

Here is one such review in text format:

Cafe Borrone

1010 El Camino Real, Menlo Park, CA 94025, +1-650-327-0830;
cafeborrone.com

Food: 18/30; Ambience: 19/30; Service: 15/30; Price: $$...

This cafe is a welcoming oasis on the Peninsula. It even has a fountain
outside which cloaks the nearby sounds of El Camino traffic. Next door to a
superb indy bookstore, Cafe Borrone is an ideal spot to grab a coffee or a
snack to accompany a newly purchased book or imported periodical. Soups and
sandwich specials rotate daily. The corn chowder with croutons and big
chunks of cheese goes especially well with a freshly toasted mini-baguette.
Evenings are often crowded and may require sharing a table with a perfect
stranger. Espresso afficionados will appreciate the Illy coffee. Noise
levels can vary from peaceful in the late mornings to nearly overwhelming on
jazz band nights.

As an hReview:

<pre><nowiki>
<div class="hreview">
<div class="item vcard">
<div class="fn org summary">Cafe Borrone</div>

1010 El Camino Real,
Menlo Park,
CA
94025,

+1-650-327-0830;
<a class="url" href="http://cafeborrone.com">cafeborrone.com</a>
</div>
<ul>
<li class="rating"><a href="http://en.wikipedia.org/wiki/Food" rel="tag">
Food: 18/30</a>;</li>
<li class="rating"><a href="http://flickr.com/photos/tags/Ambience" rel="tag">
Ambience: 19/30</a>;</li>
<li class="rating"><a href="http://en.wikipedia.org/wiki/Service" rel="tag">
Service: 15/30</a>;</li>
<li class="rating"><a href="http://en.wikipedia.org/wiki/Price" rel="tag">
Price: <abbr class="value" title="2">$$</abbr>...</a></li>
</ul>
<div class="description">
This <abbr class="type" title="business">
<a href="http://en.wikipedia.org/wiki/cafe" rel="tag">cafe</a></abbr>
is a welcoming oasis on the Peninsula.
It even has a fountain outside which nearly eliminates
the sounds of El Camino traffic. Next door to a superb indy bookstore,
Cafe Borrone is an ideal spot to grab a
<a href="http://en.wikipedia.org/wiki/coffee" rel="tag">coffee</a>
or a meal to accompany a newly purchased book or imported periodical.
<a href="http://technorati.com/tag/soup" rel="tag">Soups</a> and
<a href="http://technorati.com/tag/sandwich" rel="tag">sandwich</a>
specials rotate daily. The corn chowder with croutons and big chunks of cheese
goes especially well with a freshly toasted mini-baguette. Evenings are
often crowded and may require sharing a table with a perfect stranger.
<a href="http://flickr.com/photos/tags/espresso" rel="tag">Espresso</a>
afficionados will appreciate the
<a href="http://en.wikipedia.org/wiki/Illy" rel="tag">Illy</a> coffee.
Noise levels can vary from peaceful in the late mornings to nearly overwhelming on
<a href="http://en.wikipedia.org/wiki/jazz" rel="tag">jazz</a> band nights.
</div>
Review (<a href="http://microformats.org/wiki/hreview">
hReview v0.3</a>)
by anonymous,
<abbr class="dtreviewed" title="20050428T2130-0700">April 28th, 2005</abbr>.
</div>
</nowiki></pre>

With an accompanying CSS style sheet like:

<pre><nowiki>
a.url { display:block }
ul { margin:1em 0; padding:0 }
ul li { display:inline }
</nowiki></pre>

This hReview could be presented similar to the original text:

Cafe Borrone 
1010 El Camino Real, Menlo Park, CA 94025, +1-650-327-0830; 
[http://cafeborrone.com/ cafeborrone.com] 
 
[http://en.wikipedia.org/wiki/Food Food: 18/30];
[http://flickr.com/photos/tags/Ambience Ambience: 19/30];
[http://en.wikipedia.org/wiki/Service Service: 15/30];
[http://en.wikipedia.org/wiki/Price Price: $$...] 

This [http://en.wikipedia.org/wiki/cafe cafe] is a welcoming oasis on the Peninsula. It even has a fountain outside which cloaks the nearby sounds of El Camino traffic. Next door to a superb indy bookstore, Cafe Borrone is an ideal spot to grab a [http://en.wikipedia.org/wiki/coffee coffee] or a snack to accompany a newly purchased book or imported periodical. [http://technorati.com/tag/soup Soups] and [http://technorati.com/tag/sandwich sandwich] specials rotate daily. The corn chowder with croutons and big chunks of cheese goes especially well with a freshly toasted mini-baguette. Evenings are often crowded and may require sharing a table with a perfect stranger. [http://flickr.com/photos/tags/espresso Espresso] afficionados will appreciate the [http://en.wikipedia.org/wiki/Illy Illy] coffee. Noise levels can vary from peaceful in the late mornings to nearly overwhelming on [http://en.wikipedia.org/wiki/jazz jazz] band nights.

Review ([http://microformats.org/wiki/hreview hReview v0.3]) by anonymous, April 28th, 2005.

=== Product review ===
Here is an example of a product review:

<pre><nowiki>
<div>
<a href="http://www.amazon.com/exec/obidos/ASIN/B000089CJI/">
<img src="http://images.amazon.com/images/P/B000089CJI.01._SCTHUMBZZZ_.jpg"
alt="Album cover photo: The Postal Service: Give Up." />
The Postal Service: Give Up</a>
<blockquote>
"The people thought they were just being rewarded for treating others
as they like to be treated, for obeying stop signs and curing diseases,
for mailing letters with the address of the sender... Don't wake me,
I plan on sleeping in..."

"Nothing Better" is a great track on this album, too...
</blockquote>
(*****)
</div>
</nowiki></pre>

Adding hReview to this review is also quite simple, but in this case requires a few more elements for the rating and reviewer which are required by hReview:

<pre><nowiki>
<div class="hreview">
<a class="url fn" href="http://www.amazon.com/exec/obidos/ASIN/B000089CJI/">
<img src="http://images.amazon.com/images/P/B000089CJI.01._SCTHUMBZZZ_.jpg"
alt="Album cover photo: The Postal Service: Give Up. "
class="photo" />
The Postal Service: Give Up</a>
<div class="description">
"The people thought they were just being rewarded for treating others
as they like to be treated, for obeying stop signs and curing diseases,
for mailing letters with the address of the sender... Don't wake me,
I plan on sleeping in..."

"Nothing Better" is a great track on this album, too...
</div>
(<abbr class="rating" title="5">*****</abbr>)
Review by
<a class="url fn" href="http://ifindkarma.com/blog/">Adam Rifkin</a>,
<abbr class="dtreviewed" title="200502">February 2005</abbr>

</div>
</nowiki></pre>

And this hReview might be presented like this:

[Album cover photo: ]
[The Postal Service:]
[ Give Up ]

The Postal Service: Give Up

"The people thought they were just being rewarded for treating others as they like to be treated, for obeying stop signs and curing diseases, for mailing letters with the address of the sender... Don't wake me, I plan on sleeping in..."

"Nothing Better" is a great track on this album, too...

(*****)

Review by Adam Rifkin, February 2005.

=== Movie Review ===
Finally, here is an example of a movie review.

<pre><nowiki>
<div>
anonymous, April 18th, 2005
<div>
<a lang="zh" href="http://www.imdb.com/title/tt0299977/">
Ying Xiong (HERO)
</a>
</div>
<div>Rating: 4 out of 5</div>
<blockquote>
This movie has great visuals and music.
</blockquote>
</div>
</nowiki></pre>

With hReview:

<pre><nowiki>
<div class="hreview">

anonymous,
<abbr class="dtreviewed" title="20050418">April 18th, 2005</abbr>

<div class="item">
<a lang="zh" class="url fn" href="http://www.imdb.com/title/tt0299977/">
Ying Xiong (HERO)
</a>
</div>
<div>Rating: 4 out of 5</div>
<div class="description">
This movie has great music and visuals.
</div>
</div>
</nowiki></pre>

Which could be presented like this:

anonymous, April 18th, 2005 
Ying Xiong (HERO) 
Rating: 4 out of 5 

This movie has great music and visuals.

== Examples in the wild ==
This section is '''informative'''. The number of hReview examples in the wild has expanded far beyond the capacity of being kept inline in this specification. They have been moved to a [[hreview-examples-in-wild|separate page]].

See [[hreview-examples-in-wild|hReview Examples in the wild]].

== Implementations ==
This section is '''informative'''. The number of hReview implementations has also expanded beyond the capacity of keeping them inline. They have been moved to a [[hreview-implementations|separate page]].

See [[hreview-implementations|hReview Implementations]].

== References ==
=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[hcalendar|hCalendar]]
* [[rel-tag]]
* [http://www.ietf.org/rfc/rfc2119.txt RFC2119]
* [http://www.ietf.org/rfc/rfc3986.txt RFC3986]
* [http://www.ietf.org/rfc/rfc4287.txt RFC4287] (Atom 1.0)

=== Informative References ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.ietf.org/rfc/rfc3667.txt RFC3667]
* [http://www.ietf.org/rfc/rfc3668.txt RFC3668]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* [http://local.yahoo.com/details?id=21359628 Crepes on Cole reviews on Yahoo! Local]
* Other reviews efforts. See [[reviews-formats]].
* Contributed from http://developers.technorati.com/wiki/hReview.

==== Similar Work ====
* [[hlisting-proposal|hListing]]
* [[xoxo|XOXO]]

=== Copyright ===
{{MicroformatCopyrightStatement2005}}

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

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

=== Changes from v0.2 ===
The following changes have been made in hReview v0.3 over [[hreview-v0.2|hReview v0.2]]:

Normative changes:
# MUST (instead of SHOULD) use [[hcard|hCard]] for the item description of a business or person
# "reviewer" changes
## Made reviewer *optional* per feedback from Ryan King and Mark Nottingham
## If reviewer is absent from the hReview, then look outside the hReview, in the context of the page, for the reviewer. If there is no "reviewer" outside either, then use the author information according to the containing document language (e.g. <code><nowiki><address></nowiki></code> for (X)HTML pages) as the reviewer.
## MUST (instead of SHOULD) use [[hcard|hCard]] to represent reviewer information
# "dtreviewed" changes
## Made dtreviewed *optional* per feedback from Ryan King and Mark Nottingham
## If dtreviewed is absent from the hReview, then look outside the hReview, in the surrounding context. If the context is an [[hatom|hAtom]] entry, use its "published" (or "updated" if that is missing) datetime as the dtreviewed, if not present on the entry, use the "published" (or "updated" if that is missing) of the feed. Otherwise use the information according to the containing document language (e.g. "published"/"updated" similarly for Atom feeds), then protocol (e.g. HTTP Last-Modified, or file system last modified datetime).
# SHOULD use [[hcalendar|hCalendar]] to represent an item of 'type' 'event'
# Added one decimal digit of precision to ratings' numerical values based on publisher experience.
# Use [http://microformats.org/wiki/hcard#Value_excerpting the "value" construct from hCard] (as it is used in "tel" properties for example) to more explicitly markup the rating value when also providing (marking up) the best/worst of a rating.
# Added [[rel-license]] to indicate the license of the hReview as a whole.
# Permit tags inside ratings to denote rated tags, the same as ratings inside tags per suggestion from Eran Globen.
# Add [[include-pattern]] support to allow multiple reviews for the same item to not repeat the item info.

Informative changes (several, but in particular):
# Note that scalar/rated tags would ideally use a tag space that explain the ratings for that tag. E.g. to explain what Food:18/30 means.
# Updated examples accordingly.

== Further Reading ==
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].

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

to-do

2007-02-08T22:53:14Z

BenWest: /* Lazyweb */ add some todo items regarding the creation of the new 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.

=== 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
** 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/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
# 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.
* [[hcard-examples-in-wild]]
** 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
* [[hcard-brainstorming]]
** 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

==== [[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
* 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 "+1 Your Name")

<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: (hAtom2xyz.xsl)
* RSS 2.0 (meanwhile use hAtom2Atom.xsl and [http://atom.geekhood.net/ atom2rss.xsl]) -- +1 Matt Dertinger
* RSS 1.0 (meanwhile use hAtom2Atom.xsl and [http://cvs.4suite.org/viewcvs/uogbuji/atom2rss.xslt atom2rss.xslt]) -- +1 Matt Dertinger
* AtomOWL (meanwhile use hAtom2Atom.xsl and [http://dannyayers.com/2005/11/22/atomowl-xslt-progress/ atom2rdfxml.xsl])-- +1 Matt Dertinger
* 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: (hAtom2xyz.xsl)
* RSS 2.0 (meanwhile use hAtom2Atom.xsl and [http://atom.geekhood.net/ atom2rss.xsl])
* RSS 1.0 (meanwhile use hAtom2Atom.xsl and [http://cvs.4suite.org/viewcvs/uogbuji/atom2rss.xslt atom2rss.xslt])
* AtomOWL (meanwhile use hAtom2Atom.xsl and [http://dannyayers.com/2005/11/22/atomowl-xslt-progress/ atom2rdfxml.xsl])
</li>
</ul>

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

== Nick Drago (Drago516) ==

[[User:Drago516]]

* work on [[operating-hours]] and [[operating-hours-examples]]

hcard-issues

2007-01-31T19:19:20Z

BenWest: /* Issues */ added to TOC for canonical/authoritative issue. fixed some formatting

<h1> hCard issues </h1>

These are externally raised issues about [[hcard|hCard]] with broadly varying degrees of merit. Thus some issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the spec.

'''IMPORTANT''': Please read the [[hcard-faq|hCard FAQ]] ''before'' giving any feedback or raising any issues as your feedback/issues may already be resolved/answered.

Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — [http://tantek.com/log/ Tantek]

Please add new issues to the '''top''' of the list.

For matters relating to the vCard specification itself, see [[vcard-errata]] and [[vcard-suggestions]].

See also related [[hcalendar-issues]].

__TOC__

== Issues ==

* {{OpenIssue}} 2007-01-30 raised by [[User:AndyMabbett|Andy Mabbett]]
*# Many sites, not least Wikipedia, publish co-ordinates as degrees-minutes-seconds (e.g. [http://en.wikipedia.org/wiki/Birmingham]). Should [[geo]] be extended to allow for this, with parsers making the conversion to digital values?
* 2007-01-26 raised by James Craig on [[accessibility]] page.
*# ''Localization of RFC2426 'type' values. RFC2426 type values for adr, email, and tel were intended as machine-readable values. Used as real HTML content in the following example only works in English. The accessify forum discussion described on the [[accessibility]] page has asserted that reducing this problem to an abbr is not a valid, accessible solution.''<pre><nowiki>

Home (preferred):
+1.415.555.1212

</nowiki></pre> ''Use the the class attribute for qname prefixed type values (and others such as dtstart values), AKA meta classes.'' <pre><nowiki>

Home (preferred): +1.415.555.1212


Casa (preferido): +1.415.555.1212

</nowiki></pre>
*#* REJECTED DUPLICATE ETC. Class attributes for type values [http://microformats.org/wiki/hcard-parsing#ISSUE_2 was tried and rejected] and in addition, [[qnames-considered-harmful]].

* {{OpenIssue}} 2007-01-22 raised by [[User:Christina Hope|Christina Hope]].
*# ''What is the easiest way to display an hCard all on one line with spacing. Currently I am using this - but I know that there has to be an easier/ simpler way to do it. Examples: (1) <pre><nowiki>

Christina Hope& nbsp;& nbsp;& nbsp;
Information Technology& nbsp;& nbsp;& nbsp;
Website Coordinator& nbsp;& nbsp;& nbsp;

 x3408 & nbsp;& nbsp;& nbsp;
<a href="mailto:chope@example.com">chope@example.com</a>
</nowiki></pre>''

:: Try <pre><nowiki>
Christina Hope
Information Technology
Website Coordinator
<abbr class="tel" title="+44123 456 7890 x 3408"> x3408</abbr>
<a class="email" href="mailto:chope@example.com">chope@example.com</a>
</nowiki></pre>

::Note: apply classes to existing elements; use abbr to give the phone number in full, in international format. Also, use CSS, not non- breaking spaces, for spacing.

::[[User:AndyMabbett|Andy Mabbett]] 08:34, 22 Jan 2007 (PST)

* {{OpenIssue}} 2006-12-15 raised ([http://microformats.org/discuss/mail/microformats-discuss/2006-December/007730.html on 2006-12-14, on the mailing list]) by Joe Andrieu.
*# (Paraphrased) By including organisations and places, as well as people, hCards have lost semantic specificity (see cited mailing list post for details).

* 2006-12-15 raised by [[User:WizardIsHungry|WizardIsHungry]]
*# ''[Moved from a user talk page] Hey, why is hiding semi-useful information using CSS bad? The Geo and Address stuff wouldn't be enough to contact me, but I would like there so bookmarklets, crawlers, greasemonkey etc can manipulate it. Is there a policy on using CSS hiding of fields? Thanks :)''
*#* I guess we can't rely that anything that consumes hCards is normalizing it to a particular format instead of just taking all the xml inside the hcard classed block and sticking it somewhere. If it does just store it as a string, then generating html from it will yield the same hidden fields. Perhaps hiding fields by applying a stylesheet to the relevant hcard styles is ok, but not hiding them using in-line CSS styling. Feedback? --[[User:WizardIsHungry|Jon Williams]] 10:28, 22 Dec 2006 (PST)
*#* Furthermore, [[hcard-example1-steps]] shows using inline CSS to hide fields. What gives? I still think this is an open issue; particularly the distinction between external stylesheet hiding and inline rules though. --[[User:WizardIsHungry|Jon Williams]] 13:33, 5 Jan 2007 (PST)
*#* Should this be on [[microformats-issues]]? --[[User:WizardIsHungry|Jon Williams]] 13:37, 5 Jan 2007 (PST)
*#** The example you cite is the first of several steps, which refine and improve the first step's suboptimal hCard.
*#*** The question is: ''why is this considered suboptimal if it is ok to hide the entire card?'''
*#**** REJECTED CLOSED TOO THEORETICAL. It is not OK to hide the entire card. Without further concrete examples with real world URLs on the web, this issue is closed.
*#***** Here are a number of examples of hiding the entire card, taken from [[hcard-examples-in-wild]]: [http://www.meryl.net/] [http://www.fberriman.com/] [http://www.fberriman.com/] [http://www.last.fm/user/Crok/?scrobbling=t1] -- Could someone link to where this was discussed and decided in the past, as it seems like this is being governed by fiat. Even if you don't care to have consensus, but could you at least justify this? This stonewalling is rather rude. --[[User:WizardIsHungry|Jon Williams]] 13:24, 9 Jan 2007 (PST)
*#* [[hcard-brainstorming#CSS_Styles]] explicitly permits this. I'm going with what they say.

* {{OpenIssue}} 2006-12-07 raised by RyanKing.
*# ''hCard org-fn matching should use organization-name, if given.''
*# originally [http://microformats.org/discuss/mail/microformats-discuss/2006-November/007337.html raised on uf-discuss] by David Janes.

* {{OpenIssue}} 2006-11-24 raised by [[User:AndyMabbett|Andy Mabbett]]
*# A suggested work-around for the lack of a gender property is to represent gender implicitly in the honorific-prefix field, e.g. Mr. for male, and Ms. for female. This approach does has the limitation that "Mr." and "Ms." (or "Miss"/ "Mrs.") conflicts with a higher-ranking, gender-neutral honorific, such as "Dr." or "Rev." for the person, as it is unusual (and sometimes, outside the USA, invalid) to refer to someone as "Mr. Dr." or "Mrs. Rev." for example. Note also that some cultures or religions regard such titles as offensive, or at least disdain them.

* 2006-11-23 raised by [[User:AndyMabbett|Andy Mabbett]]
*# The specification should be "stand alone", and not normally require reference to the vCard specification.
*#*A: ACCEPTED PARTIAL. Agreed that [[hcard|hCard]] should be usable by typical web authors without having to dig through the vCard specification. Precise implementation of parsing etc. hCard properties however will likely require programmers to reference the specifics/grammars in the vCard specification which we will NOT replicate in the hCard specification in order to avoid inevitable introduction of errors due to duplication. And that being said, ''informative'' explanations may be a good idea, while the vCard property/value definitions are kept as ''normative''.
*#** Yes; my meaning was with reference to hCard publishing, not parsing-into-vCards. [[User:AndyMabbett|Andy Mabbett]]
*# ''The specification should state that "telephone numbers SHOULD adhere to [http://en.wikipedia.org/wiki/E.123 ITU-T Recommendation E.123]" (or perhaps "MUST").''
*#* ACCEPTED PARTIAL. This makes sense as an informative reference and a MAY, but since vCard makes no such SHOULD statement for TEL values, neither should/will hCard. In addition, as a Wikipedia URL that is subject to drastic change, we cannot make that a normative reference.
*#** I take your point about Wikipedia - here's [http://www.itu.int/rec/T-REC-E.123-200102-I/en a more definitive ITU-E.123 URL]; but it's for a chargeable document. Using "SHOULD" or "MUST" in hCard will not affect compatibility with or conversion to vCard. [[User:AndyMabbett|Andy Mabbett]]

* 2006-11-16 raised by [[User:AndyMabbett|Andy Mabbett]]
*# ''The "type" for "tel" lacks a "textphone" option (for the devices used by, e.g., people who are deaf or have speech difficulties. Example: [http://www.birmingham.gov.uk/contact Birmingham City Council (303 1119)].''
*#*A: REJECTED. This is a vCard issue, as the "type" taxonomy for "tel" is determined by vCard. We are not presently extending hCard beyond the properties and values in vCard.
*#** ''I'm not clear how you can "reject" a provably factual statement. What's the process of suggesting an update to vCard? [[User:AndyMabbett|Andy Mabbett]]''
*#***A: ACCEPTED PARTIAL RESOLVED. Unfortunately it is not clear what the process is for updating vCard. However, we can at least capture suggestions for improvement to vCard from this community which may be helpful once the process for updating vCard is understood. I've created [[vcard-suggestions]] for this purpose and added this suggestion. - Tantek
*#**** The vCard spec is updated by RFC, for example [http://www.rfc-editor.org/rfc/rfc4770.txt RFC 4770]. [[User:AndyMabbett|Andy Mabbett]] 06:22, 12 Jan 2007 (PST)

* {{OpenIssue}} 2006-10-21 raised by [[User:AndyMabbett|Andy Mabbett]]
*# ''There should be some way to say that the URL of an hCard or hCalendar event is the URL of the page itself, without having to include a redundant, and accessibility-damaging link to that page, on the page itself.''

* 2005-06-21 raised by Hixie
*# ''Issue H-1: This specification is lacking a user agent conformance section. There's basically nothing that says how hCards must be parsed, how to handle errors, and so forth. Is it defined in terms of the DOM? Is it defined in terms of a serialisation? How do you handle unexpected content or missing content?
*#*A: ACCEPTED RESOLVED. See [[hcard-parsing]] for how hCards must be parsed. For errors/unexpected content/missing content, please provide specific examples.

* 2005-06-30 raised by Jack L. Wolfgang II. Please feel free to move these to the FAQs if they are better suited there.
*# ''Handling middle names and suffixes: How does one handle middle initials/names in the hCard format and suffixes that are not honorific suffixes (e.g. Jr., Sr., II, III, etc. as opposed to Ph.D., Esq., M.D., etc.)?''
*#*A: ACCEPTED FAQ. By [http://suda.co.uk Brian Suda] (2005-11-08 updated by [http://tantek.com/log/ Tantek]; 2006-11-16 updated by [[User:AndyMabbett|Andy Mabbett]]) hCard is based of the RFC2426 spec. I you want to use a middle initial it can be expanded using the abbr element. <code><abbr title="[MiddleName]" class="additional-name">M</abbr></code>. Honorific Suffixes in the RFC include Jr., Esq. and other inherited suffixes, so I would just use <code><abbr class="honorific-suffix" title="Junior">Jr.</abbr></code> etc.
*# ''Handling different types of addresses: How does one handle the TYPE (e.g. postal, work, etc.) specification for addresses as specified in RFC 2426 Section 3.2.1?''
*#*A: ACCEPTED FAQ. By [http://suda.co.uk Brian Suda] (2005-11-08 updated by [http://tantek.com/log/ Tantek]) If you want to add a type to certain elements, including address and telephone it may be done in the following manner:
<pre><nowiki>

work:
...

</nowiki></pre>
<pre><nowiki>

work:
123.456.7890

</nowiki></pre>
the TYPE needs to be a sub-element of the property (adr, tel, etc) NOTE: EMAIL does NOT have many TYPE attributes, only INTERNET and X400

* {{OpenIssue}} 2006-04-10 raised by [[User:ScottReynen|Scott Reynen]].
*# ''When someone looks at the [[hcard|hCard]] pages, one sees no collection of real-world publishing of contact data nor discussion of the properties implied by such examples, I think it's far too easy to infer that microformats come from other formats more than actual behavior. There's nothing on the [[process]] nor the hcard pages explaining this discrepancy. I would argue that there should be an explanation, probably in both places.''

* 2006-04-06 raised by [[User:Evan|Evan]].
*# ''What is the relationship between the CATEGORY property and [[rel-tag]]? Can you add a tag to an hCard? How can you add a tag to a particular hcard on a page without tagging the other cards on a page?''
*#* ACCEPTED. Categories can optionally be represented as tags. The classname 'category' should always be used, but rel="tag" can optionally be used (in addition to the category classname). In the case that a rel-tag tag is used, the tag (as defined by [[rel-tag]]) is used for the category. Examples: (1) <code><nowiki>food</nowiki></code> and (2) <code><nowiki><a class="category" rel="tag" href="http://example.com/food">Food!</a></nowiki></code>. --[[User:RyanKing|RyanKing]] 15:16, 13 Jun 2006 (PDT)

* {{OpenIssue}} 2006-03-07 raised by [http://tantek.com Tantek].
*# ''Issue 1: In 99% of the cases I am finding the need to explicitly do "n" markup, the person has a three word fn which is in the form "given-name additional-name(or initial) family-name". Should we make three word fn's into another shorthand notation to make this easier for authors?''

* 2006-02-23 raised by [http://www.thefutureoftheweb.com/ Jesse Skinner] and [http://www.thefutureoftheweb.com/blog/2006/1/hcard#comment1 Ben Buchanan].
*# ''Are multiple URLs allowed? The [http://microformats.org/wiki/hcard#Property_List Property List] suggests not, whereas email and tel have multiple type/value pairs. However, the [http://microformats.org/wiki/hcard-parsing#finding_hCard_properties parsing page] suggests multiple URLs are OK. Either way, it seems clear that a type cannot be associated with a URL. So how exactly does hCard deal with multiple URLs?''
*#* RESOLVED FAQ: Multiple URLs are allowed. Some consuming agents (Apple's AddressBook.app among them) don't have an interface for producing multiple URLs, but they are still valid in vCard and therefore hCard. --[[User:RyanKing|RyanKing]] 17:58, 12 Jun 2006 (PDT)

* 2006-02-19 raised by Miika Mäkinen.
*# ''Couldn't the types for tel numbers be specified in a class? Now, for a phone number one needs to add the type as "visible" text, which is not always preferred. For example, type "Work", many times more suitable label could be "Office" or similar and sometimes you might not want to display any type information at all.''
*#* REJECTED TRIED ALREADY. Using class names for the "type" of a tel or adr [http://microformats.org/wiki/hcard-parsing#ISSUE_2 was attempted], and failed in many situations. In addition, the "type" information is actual data, not just a property name, and thus deserves to be in the ''visible'' markup. Note that you can use abbreviations, e.g. <code><nowiki><abbr class="type" title="work">W:</abbr></nowiki></code> in order to present the type in a way that may better fit in with the rest of your presentation.

* 2006-02-13 raised by [http://microformats.org/wiki/User:Eron_Wright Eron Wright]
*# ''Few systems contemplate the altitude component of a coordinate, yet it exists. Altitude becomes important when working with 3D mapping software such as Google Earth. Indeed, the geocoding service that Google Earth uses returns a three-dimensional coordinate. I suggest that hCard provide explicit support for altitude.''
*#* REJECTED POSTPONED. Not in vCard. There is no "altitude" component in vCard (RFC 2426), and thus (certainly for now) there won't be any in hCard. If a new version of vCard were to come out with altitude, then we would add it to hCard. At some point we may also consider adding explicit extensions beyond vCard, but if we were to do so, we would capture them first on the [[hcard-brainstorming]] page.

*2006-02-03 raised by Brian
*# We can use the [[geo]] microformat in [[hatom]] to represent GeoRSS element

* {{OpenIssue}} 2006-01-28 raised by [http://rbach.priv.at/Microformats-IRC/2006-01-28#T075222 Tantek on #microformats]
*# ''Is hCard is really appropriate for a named phone bridge, or do we need something else for a named phone numbers that are neither people nor organizations (the current two precise semantics that can be defined by hCard). For example see the "Zakim" hCard on http://www.w3.org/2005/12/allgroupoverview.html''

* 2006-01-21 raised by [http://inspire.server101.com/ben/resume/ Ben Boyle].
*# ''Have run into issues trying to use definition lists with hCard, specifically around nesting requirements for tel where the DT element takes a class "type" (e.g. Telephone, Facsimile) and the DD element marks the value. It is invalid to place any other elements within a DL that wrap around the DT/DD pairs so there is no available element to assign the class "tel" to. XHTML2 proposes a DI element that will resolve this issue. I am hoping for an interim solution for those that wish to use definition lists, perhaps that "any class that would be placed on the DI parent (in XHTML2) must instead be placed on the first DT element". I realise this will cause headaches for those implementing hCard parsers. I'd also like to note this may affect other (current or future) microformats and relates to the general hassle of definition lists in current (X)HTML recommendations. For your consideration - thanks!''
*#* REJECTED WORKAROUND AVAILABLE. Either don't use definition lists in this manner (because the description of a definition should go completely in the DD element, and thus you should be able to put the class on that), or use separate DLs in the cases where you would otherwise have needed a DI element.

* 2005-12-08 raised by [http://www.heatonarts.com Kenny Heaton].
*# ''The specification gives no way to to declare a telephone extension, as in (800) 234-5678 ext. 101''
*#* ACCEPTED FAQ. What is the best way to declare a telephone extension in a "tel" property? (also seems like it would be a vCard FAQ).

* 2005-10-30 raised by [http://greenbytes.de/tech/webdav/ Julian Reschke].
*# ''Several implementations'' '''(Which ones? Please provide links.)''' ''seem to assume that any class attribute that contains the substring "vcard" indeed signals the presence of vcard information. Not so: there are examples'' '''(What examples? Please provide links.)''' ''of where a token in the class attribute indeed only ''starts with'' "vcard", in which it should be ignored. Implementations using XPath (such as XSLT or Greasemonkey scripts) should be advised to do a <code>contains(concat(@class,' '),'vcard ')</code>.
*#* REJECTED VAGUE. Which implementations? And which examples?
*#*''(Note: the code <code>contains(concat(@class,' '),'vcard ')</code> is broken see [[parsing-microformats#Parsing_class_values]] for a correct example --[[User:RobertBachmann|Robert Bachmann]])''

* 2005-08-12 raised by [http://home.alltel.net/jackwolfgang/contact/ Jack L. Wolfgang II]. Use of mailto transport functionality for the E-Mail address field.
*# ''As stated in the [[hcard-brainstorming]] document, mailto is abused by spammers. As a result, many organizations have moved to form-based contacts as opposed to mailtos. According to [http://www.ietf.org/rfc/rfc2426.txt RFC 2426], Section 3.3.2, "A non-standard value can also be specified." Does this refer to a non-standard e-mail address value or type value?''
*#* A: ACCEPTED FAQ. Type value.

* 2005-07-23 raised by DanConnolly
*# ''Are class names case sensitive or not? [[hcard]] says "If names in the source schema are case-insensitive, then use an all lowercase equivalent."''
*#* A: ACCEPTED FAQ. Class names are case sensitive per the HTML4 specification. Hence hCard explicitly specifies the case of class name to use for source schema names that are case-insensitive.
*# ''...but I find example data with class="Given-Name"''
*#* A: ACCEPTED RESOLVED. That is from an older preliminary version of the hCard spec which used mixed case class names. Such class names are no longer valid hCard. Please note which examples (URLs) are using the older class names and hopefully we can get them fixed.
*#** A: By [http://suda.co.uk Brian Suda] I have fixed all the references in the [[hcard-brainstorming]] page to reflect the lower-case style, this is a hold-over from the original design, X2V has been updated.
*# ''..and code that supports it [data with class="Given-Name"].''
*#* A: ACCEPTED RESOLVED. Any code supporting the older class name(s) is for backward compatibility only, and should be phased out. Any new hCard code SHOULD NOT support such mixed case class names.
*#** [http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html rfc2629xslt.html] uses Street-Address, Family-Name, etc.
*#*** A: By [http://greenbytes.de/tech/webdav/ Julian Reschke] Fixed rfc2629.xslt (2005-10-29)
*#** [http://suda.co.uk/projects/X2V/ X2V] Version 0.5.1 2005-07-08 supports Family-Name etc.
*#*** A: By [http://suda.co.uk Brian Suda] I agree that the upper-case class names can be removed from the code, this was a hold-over and will be trimmed.
*# ''The ul/ol stuff for multiple values of a property seems to be in the X2V code and in [[hcard-brainstorming]] but not in the [[hcard]] spec.''
*#* A. ACCEPTED RESOLVED. This needs to be added to the spec. 2005-11-08 Update: the way multiple values has been updated to work much better and not require ul/ol.
*# ''the [[hcard-profile]] says country-name but X2V and lots of the data I've seen says country''
*#* A. ACCEPTED RESOLVED. RFC 2426 clearly says "country name" in both the prose and the grammar, thus "country-name" is the correct class name to use. If X2V uses just "country", it needs to be fixed to use "country-name", and any such examples as well. Please note which examples (URLs) are using the class name "country" and hopefully we can get them fixed.
*#** A: By [http://suda.co.uk Brian Suda] I have fixed all the references in the [[hcard-brainstorming]] page to reflect the proper country-name, X2V will support this in the next iteration when i fix several bugs at once.

* 2005-07-22 raised by DanConnolly
*# ''...in my cellphone/sidekick address book, I have a number of entries for companies. I wrote [http://dev.w3.org/cvsweb/2001/palmagent/asHCard.xsl asHCard.xsl] to convert the data from RDF to hCard, but I don't know what to do with entries for companies, since FN is mandatory in hCard.''
*#*A: ACCEPTED FAQ. This should be an FAQ. "How do I write an hCard for a company?" The vCard specification is silent on this point (entries for companies). Thus there are two options as far as the hCard standard is concerned:
*#*# Set "fn" and "org" to the same value. E.g. <code>W3C</code> (recommended)
*#*# Set "org" as usual, and set "fn" explicitly to empty. E.g. <code>W3C</code> or
*#*#* Simply have no "fn", and on the parsing side, if there is no "fn" present, but there is an "org" property, then duplicate the "org" value as "fn"
*#*The last two options are effectively the same and are both not explicit and easily confusable with a "missing data" condition. Thus option 1 is preferred. For converting applications (hCard to vCard), they ''may'' consider using proprietary extensions to make the distinction explicit in generated vCards, based on either case 1 or 2 above. E.g. Apple's Address Book application supports the property: <code>X-ABShowAs:COMPANY</code>
*#*We are looking for descriptions of how other vCard supporting applications treat "company" vCards differently from "person" vCards. Please provide descriptions here:
*#** Address Book / MacOSX.3:
*#*** Export (e.g. drag & drop to desktop, view in text editor)
*#**** Sets "FN" and "ORG" to the name of the company
*#**** Sets proprietary <code>X-ABShowAs:COMPANY</code>
*#*** Import (e.g. edit in text editor, drag & drop from desktop)
*#**** By setting "FN" and "ORG' to the same name (e.g. Banana Computers Inc.)
*#**** And removing any proprietary properties (e.g. X-ABShowAs)
*#**** Address Book user interface showed new vCard as a "company" contact rather an a person
*#** Address Book MacOSX.4:
*#*** same results as above -RyanKing
*#** The Danger Hiptop (aka T-Mobile Sidekick) address book:
*#*** Export (e.g. [http://lists.w3.org/Archives/Public/www-archive/2005Sep/0007.html email to a mailing list])
*#**** Sets "FN" to the empty string and puts the company name in "ORG".
*#*** Import - could not find a way to import a .vcf, by email, IM, or other means into the Sidekick.
*#** Contacts / Outlook 2003 Windows
*#*** Export (e.g. Highlight contact, File, Save As, vcard)
*#**** Sets "N" and "ORG to the name of the company
*#**** Sets "FN" to value in "File as:"
*#** Add another vCard app here.

=== Canonical/Authoritative Hcard ===
* {{OpenIssue}} 2006-01-31 raised by ??.
* ''Issue 1: Specifying Authoritative or Canonical or Official Hcard''
** Use of rel="me" only specifies an alternate version, not necessarily the canonical version
** Suggestion: use rel="me self". Adopt "self" semantics from Atom which means "the", or controversially "alternate, equivalent" version
** Other suggestions? "via", "authoritative", "canonical"?
** Problems with this suggestion?
** How does this relate to authentication/trust issues? Is this a different problem with a different scope?
** (10:47:44) sreynen: for example, all of the examples i've seen involve a single person publishing multiple hCards of himself
(10:48:13) sreynen: yet many people are talking about 3rd parties publishing hCards and pointing back to the subject's own hCard

''TODO:'' please add apropriate context and history of this issue from the mailing list. Sign your name to your comments.

== Template ==

Please use this format (copy and paste this to the end of the list to add your issues):
* {{OpenIssue}} YYYY-MM-DD raised by [http://yourhomepage.example.com YOURNAME].
*# ''Issue 1: Here is the first issue I have.''
*# ''Issue 2: Here is the second issue I have.''

Note: large blocks of italic text are inaccessible to many readers, including people with types of visual impairment, dyslexia, etc. [http://www.intranet.man.ac.uk/accessibility/Disabilities/dyslexia.html], [https://tritonlink.ucsd.edu/portal/site/tritonlink-preview/menuitem.b4448692267a11256ec5e210514b01ca?storyID=20896]. [http://accessites.org/], [http://tlt.psu.edu/suggestions/accessibility/font.html], [http://www.wd4a.co.uk/Guidelines.htm]

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

hcard-issues

2007-01-31T19:16:51Z

BenWest: /* Template */ attempt to add the rel="me self" issue. please add to this.

<h1> hCard issues </h1>

These are externally raised issues about [[hcard|hCard]] with broadly varying degrees of merit. Thus some issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the spec.

'''IMPORTANT''': Please read the [[hcard-faq|hCard FAQ]] ''before'' giving any feedback or raising any issues as your feedback/issues may already be resolved/answered.

Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — [http://tantek.com/log/ Tantek]

Please add new issues to the '''top''' of the list.

For matters relating to the vCard specification itself, see [[vcard-errata]] and [[vcard-suggestions]].

See also related [[hcalendar-issues]].

__TOC__

== Issues ==

* {{OpenIssue}} 2007-01-30 raised by [[User:AndyMabbett|Andy Mabbett]]
*# Many sites, not least Wikipedia, publish co-ordinates as degrees-minutes-seconds (e.g. [http://en.wikipedia.org/wiki/Birmingham]). Should [[geo]] be extended to allow for this, with parsers making the conversion to digital values?
* 2007-01-26 raised by James Craig on [[accessibility]] page.
*# ''Localization of RFC2426 'type' values. RFC2426 type values for adr, email, and tel were intended as machine-readable values. Used as real HTML content in the following example only works in English. The accessify forum discussion described on the [[accessibility]] page has asserted that reducing this problem to an abbr is not a valid, accessible solution.''<pre><nowiki>

Home (preferred):
+1.415.555.1212

</nowiki></pre> ''Use the the class attribute for qname prefixed type values (and others such as dtstart values), AKA meta classes.'' <pre><nowiki>

Home (preferred): +1.415.555.1212


Casa (preferido): +1.415.555.1212

</nowiki></pre>
*#* REJECTED DUPLICATE ETC. Class attributes for type values [http://microformats.org/wiki/hcard-parsing#ISSUE_2 was tried and rejected] and in addition, [[qnames-considered-harmful]].

* {{OpenIssue}} 2007-01-22 raised by [[User:Christina Hope|Christina Hope]].
*# ''What is the easiest way to display an hCard all on one line with spacing. Currently I am using this - but I know that there has to be an easier/ simpler way to do it. Examples: (1) <pre><nowiki>

Christina Hope& nbsp;& nbsp;& nbsp;
Information Technology& nbsp;& nbsp;& nbsp;
Website Coordinator& nbsp;& nbsp;& nbsp;

 x3408 & nbsp;& nbsp;& nbsp;
<a href="mailto:chope@example.com">chope@example.com</a>
</nowiki></pre>''

:: Try <pre><nowiki>
Christina Hope
Information Technology
Website Coordinator
<abbr class="tel" title="+44123 456 7890 x 3408"> x3408</abbr>
<a class="email" href="mailto:chope@example.com">chope@example.com</a>
</nowiki></pre>

::Note: apply classes to existing elements; use abbr to give the phone number in full, in international format. Also, use CSS, not non- breaking spaces, for spacing.

::[[User:AndyMabbett|Andy Mabbett]] 08:34, 22 Jan 2007 (PST)

* {{OpenIssue}} 2006-12-15 raised ([http://microformats.org/discuss/mail/microformats-discuss/2006-December/007730.html on 2006-12-14, on the mailing list]) by Joe Andrieu.
*# (Paraphrased) By including organisations and places, as well as people, hCards have lost semantic specificity (see cited mailing list post for details).

* 2006-12-15 raised by [[User:WizardIsHungry|WizardIsHungry]]
*# ''[Moved from a user talk page] Hey, why is hiding semi-useful information using CSS bad? The Geo and Address stuff wouldn't be enough to contact me, but I would like there so bookmarklets, crawlers, greasemonkey etc can manipulate it. Is there a policy on using CSS hiding of fields? Thanks :)''
*#* I guess we can't rely that anything that consumes hCards is normalizing it to a particular format instead of just taking all the xml inside the hcard classed block and sticking it somewhere. If it does just store it as a string, then generating html from it will yield the same hidden fields. Perhaps hiding fields by applying a stylesheet to the relevant hcard styles is ok, but not hiding them using in-line CSS styling. Feedback? --[[User:WizardIsHungry|Jon Williams]] 10:28, 22 Dec 2006 (PST)
*#* Furthermore, [[hcard-example1-steps]] shows using inline CSS to hide fields. What gives? I still think this is an open issue; particularly the distinction between external stylesheet hiding and inline rules though. --[[User:WizardIsHungry|Jon Williams]] 13:33, 5 Jan 2007 (PST)
*#* Should this be on [[microformats-issues]]? --[[User:WizardIsHungry|Jon Williams]] 13:37, 5 Jan 2007 (PST)
*#** The example you cite is the first of several steps, which refine and improve the first step's suboptimal hCard.
*#*** The question is: ''why is this considered suboptimal if it is ok to hide the entire card?'''
*#**** REJECTED CLOSED TOO THEORETICAL. It is not OK to hide the entire card. Without further concrete examples with real world URLs on the web, this issue is closed.
*#***** Here are a number of examples of hiding the entire card, taken from [[hcard-examples-in-wild]]: [http://www.meryl.net/] [http://www.fberriman.com/] [http://www.fberriman.com/] [http://www.last.fm/user/Crok/?scrobbling=t1] -- Could someone link to where this was discussed and decided in the past, as it seems like this is being governed by fiat. Even if you don't care to have consensus, but could you at least justify this? This stonewalling is rather rude. --[[User:WizardIsHungry|Jon Williams]] 13:24, 9 Jan 2007 (PST)
*#* [[hcard-brainstorming#CSS_Styles]] explicitly permits this. I'm going with what they say.

* {{OpenIssue}} 2006-12-07 raised by RyanKing.
*# ''hCard org-fn matching should use organization-name, if given.''
*# originally [http://microformats.org/discuss/mail/microformats-discuss/2006-November/007337.html raised on uf-discuss] by David Janes.

* {{OpenIssue}} 2006-11-24 raised by [[User:AndyMabbett|Andy Mabbett]]
*# A suggested work-around for the lack of a gender property is to represent gender implicitly in the honorific-prefix field, e.g. Mr. for male, and Ms. for female. This approach does has the limitation that "Mr." and "Ms." (or "Miss"/ "Mrs.") conflicts with a higher-ranking, gender-neutral honorific, such as "Dr." or "Rev." for the person, as it is unusual (and sometimes, outside the USA, invalid) to refer to someone as "Mr. Dr." or "Mrs. Rev." for example. Note also that some cultures or religions regard such titles as offensive, or at least disdain them.

* 2006-11-23 raised by [[User:AndyMabbett|Andy Mabbett]]
*# The specification should be "stand alone", and not normally require reference to the vCard specification.
*#*A: ACCEPTED PARTIAL. Agreed that [[hcard|hCard]] should be usable by typical web authors without having to dig through the vCard specification. Precise implementation of parsing etc. hCard properties however will likely require programmers to reference the specifics/grammars in the vCard specification which we will NOT replicate in the hCard specification in order to avoid inevitable introduction of errors due to duplication. And that being said, ''informative'' explanations may be a good idea, while the vCard property/value definitions are kept as ''normative''.
*#** Yes; my meaning was with reference to hCard publishing, not parsing-into-vCards. [[User:AndyMabbett|Andy Mabbett]]
*# ''The specification should state that "telephone numbers SHOULD adhere to [http://en.wikipedia.org/wiki/E.123 ITU-T Recommendation E.123]" (or perhaps "MUST").''
*#* ACCEPTED PARTIAL. This makes sense as an informative reference and a MAY, but since vCard makes no such SHOULD statement for TEL values, neither should/will hCard. In addition, as a Wikipedia URL that is subject to drastic change, we cannot make that a normative reference.
*#** I take your point about Wikipedia - here's [http://www.itu.int/rec/T-REC-E.123-200102-I/en a more definitive ITU-E.123 URL]; but it's for a chargeable document. Using "SHOULD" or "MUST" in hCard will not affect compatibility with or conversion to vCard. [[User:AndyMabbett|Andy Mabbett]]

* 2006-11-16 raised by [[User:AndyMabbett|Andy Mabbett]]
*# ''The "type" for "tel" lacks a "textphone" option (for the devices used by, e.g., people who are deaf or have speech difficulties. Example: [http://www.birmingham.gov.uk/contact Birmingham City Council (303 1119)].''
*#*A: REJECTED. This is a vCard issue, as the "type" taxonomy for "tel" is determined by vCard. We are not presently extending hCard beyond the properties and values in vCard.
*#** ''I'm not clear how you can "reject" a provably factual statement. What's the process of suggesting an update to vCard? [[User:AndyMabbett|Andy Mabbett]]''
*#***A: ACCEPTED PARTIAL RESOLVED. Unfortunately it is not clear what the process is for updating vCard. However, we can at least capture suggestions for improvement to vCard from this community which may be helpful once the process for updating vCard is understood. I've created [[vcard-suggestions]] for this purpose and added this suggestion. - Tantek
*#**** The vCard spec is updated by RFC, for example [http://www.rfc-editor.org/rfc/rfc4770.txt RFC 4770]. [[User:AndyMabbett|Andy Mabbett]] 06:22, 12 Jan 2007 (PST)

* {{OpenIssue}} 2006-10-21 raised by [[User:AndyMabbett|Andy Mabbett]]
*# ''There should be some way to say that the URL of an hCard or hCalendar event is the URL of the page itself, without having to include a redundant, and accessibility-damaging link to that page, on the page itself.''

* 2005-06-21 raised by Hixie
*# ''Issue H-1: This specification is lacking a user agent conformance section. There's basically nothing that says how hCards must be parsed, how to handle errors, and so forth. Is it defined in terms of the DOM? Is it defined in terms of a serialisation? How do you handle unexpected content or missing content?
*#*A: ACCEPTED RESOLVED. See [[hcard-parsing]] for how hCards must be parsed. For errors/unexpected content/missing content, please provide specific examples.

* 2005-06-30 raised by Jack L. Wolfgang II. Please feel free to move these to the FAQs if they are better suited there.
*# ''Handling middle names and suffixes: How does one handle middle initials/names in the hCard format and suffixes that are not honorific suffixes (e.g. Jr., Sr., II, III, etc. as opposed to Ph.D., Esq., M.D., etc.)?''
*#*A: ACCEPTED FAQ. By [http://suda.co.uk Brian Suda] (2005-11-08 updated by [http://tantek.com/log/ Tantek]; 2006-11-16 updated by [[User:AndyMabbett|Andy Mabbett]]) hCard is based of the RFC2426 spec. I you want to use a middle initial it can be expanded using the abbr element. <code><abbr title="[MiddleName]" class="additional-name">M</abbr></code>. Honorific Suffixes in the RFC include Jr., Esq. and other inherited suffixes, so I would just use <code><abbr class="honorific-suffix" title="Junior">Jr.</abbr></code> etc.
*# ''Handling different types of addresses: How does one handle the TYPE (e.g. postal, work, etc.) specification for addresses as specified in RFC 2426 Section 3.2.1?''
*#*A: ACCEPTED FAQ. By [http://suda.co.uk Brian Suda] (2005-11-08 updated by [http://tantek.com/log/ Tantek]) If you want to add a type to certain elements, including address and telephone it may be done in the following manner:
<pre><nowiki>

work:
...

</nowiki></pre>
<pre><nowiki>

work:
123.456.7890

</nowiki></pre>
the TYPE needs to be a sub-element of the property (adr, tel, etc) NOTE: EMAIL does NOT have many TYPE attributes, only INTERNET and X400

* {{OpenIssue}} 2006-04-10 raised by [[User:ScottReynen|Scott Reynen]].
*# ''When someone looks at the [[hcard|hCard]] pages, one sees no collection of real-world publishing of contact data nor discussion of the properties implied by such examples, I think it's far too easy to infer that microformats come from other formats more than actual behavior. There's nothing on the [[process]] nor the hcard pages explaining this discrepancy. I would argue that there should be an explanation, probably in both places.''

* 2006-04-06 raised by [[User:Evan|Evan]].
*# ''What is the relationship between the CATEGORY property and [[rel-tag]]? Can you add a tag to an hCard? How can you add a tag to a particular hcard on a page without tagging the other cards on a page?''
*#* ACCEPTED. Categories can optionally be represented as tags. The classname 'category' should always be used, but rel="tag" can optionally be used (in addition to the category classname). In the case that a rel-tag tag is used, the tag (as defined by [[rel-tag]]) is used for the category. Examples: (1) <code><nowiki>food</nowiki></code> and (2) <code><nowiki><a class="category" rel="tag" href="http://example.com/food">Food!</a></nowiki></code>. --[[User:RyanKing|RyanKing]] 15:16, 13 Jun 2006 (PDT)

* {{OpenIssue}} 2006-03-07 raised by [http://tantek.com Tantek].
*# ''Issue 1: In 99% of the cases I am finding the need to explicitly do "n" markup, the person has a three word fn which is in the form "given-name additional-name(or initial) family-name". Should we make three word fn's into another shorthand notation to make this easier for authors?''

* 2006-02-23 raised by [http://www.thefutureoftheweb.com/ Jesse Skinner] and [http://www.thefutureoftheweb.com/blog/2006/1/hcard#comment1 Ben Buchanan].
*# ''Are multiple URLs allowed? The [http://microformats.org/wiki/hcard#Property_List Property List] suggests not, whereas email and tel have multiple type/value pairs. However, the [http://microformats.org/wiki/hcard-parsing#finding_hCard_properties parsing page] suggests multiple URLs are OK. Either way, it seems clear that a type cannot be associated with a URL. So how exactly does hCard deal with multiple URLs?''
*#* RESOLVED FAQ: Multiple URLs are allowed. Some consuming agents (Apple's AddressBook.app among them) don't have an interface for producing multiple URLs, but they are still valid in vCard and therefore hCard. --[[User:RyanKing|RyanKing]] 17:58, 12 Jun 2006 (PDT)

* 2006-02-19 raised by Miika Mäkinen.
*# ''Couldn't the types for tel numbers be specified in a class? Now, for a phone number one needs to add the type as "visible" text, which is not always preferred. For example, type "Work", many times more suitable label could be "Office" or similar and sometimes you might not want to display any type information at all.''
*#* REJECTED TRIED ALREADY. Using class names for the "type" of a tel or adr [http://microformats.org/wiki/hcard-parsing#ISSUE_2 was attempted], and failed in many situations. In addition, the "type" information is actual data, not just a property name, and thus deserves to be in the ''visible'' markup. Note that you can use abbreviations, e.g. <code><nowiki><abbr class="type" title="work">W:</abbr></nowiki></code> in order to present the type in a way that may better fit in with the rest of your presentation.

* 2006-02-13 raised by [http://microformats.org/wiki/User:Eron_Wright Eron Wright]
*# ''Few systems contemplate the altitude component of a coordinate, yet it exists. Altitude becomes important when working with 3D mapping software such as Google Earth. Indeed, the geocoding service that Google Earth uses returns a three-dimensional coordinate. I suggest that hCard provide explicit support for altitude.''
*#* REJECTED POSTPONED. Not in vCard. There is no "altitude" component in vCard (RFC 2426), and thus (certainly for now) there won't be any in hCard. If a new version of vCard were to come out with altitude, then we would add it to hCard. At some point we may also consider adding explicit extensions beyond vCard, but if we were to do so, we would capture them first on the [[hcard-brainstorming]] page.

*2006-02-03 raised by Brian
*# We can use the [[geo]] microformat in [[hatom]] to represent GeoRSS element

* {{OpenIssue}} 2006-01-28 raised by [http://rbach.priv.at/Microformats-IRC/2006-01-28#T075222 Tantek on #microformats]
*# ''Is hCard is really appropriate for a named phone bridge, or do we need something else for a named phone numbers that are neither people nor organizations (the current two precise semantics that can be defined by hCard). For example see the "Zakim" hCard on http://www.w3.org/2005/12/allgroupoverview.html''

* 2006-01-21 raised by [http://inspire.server101.com/ben/resume/ Ben Boyle].
*# ''Have run into issues trying to use definition lists with hCard, specifically around nesting requirements for tel where the DT element takes a class "type" (e.g. Telephone, Facsimile) and the DD element marks the value. It is invalid to place any other elements within a DL that wrap around the DT/DD pairs so there is no available element to assign the class "tel" to. XHTML2 proposes a DI element that will resolve this issue. I am hoping for an interim solution for those that wish to use definition lists, perhaps that "any class that would be placed on the DI parent (in XHTML2) must instead be placed on the first DT element". I realise this will cause headaches for those implementing hCard parsers. I'd also like to note this may affect other (current or future) microformats and relates to the general hassle of definition lists in current (X)HTML recommendations. For your consideration - thanks!''
*#* REJECTED WORKAROUND AVAILABLE. Either don't use definition lists in this manner (because the description of a definition should go completely in the DD element, and thus you should be able to put the class on that), or use separate DLs in the cases where you would otherwise have needed a DI element.

* 2005-12-08 raised by [http://www.heatonarts.com Kenny Heaton].
*# ''The specification gives no way to to declare a telephone extension, as in (800) 234-5678 ext. 101''
*#* ACCEPTED FAQ. What is the best way to declare a telephone extension in a "tel" property? (also seems like it would be a vCard FAQ).

* 2005-10-30 raised by [http://greenbytes.de/tech/webdav/ Julian Reschke].
*# ''Several implementations'' '''(Which ones? Please provide links.)''' ''seem to assume that any class attribute that contains the substring "vcard" indeed signals the presence of vcard information. Not so: there are examples'' '''(What examples? Please provide links.)''' ''of where a token in the class attribute indeed only ''starts with'' "vcard", in which it should be ignored. Implementations using XPath (such as XSLT or Greasemonkey scripts) should be advised to do a <code>contains(concat(@class,' '),'vcard ')</code>.
*#* REJECTED VAGUE. Which implementations? And which examples?
*#*''(Note: the code <code>contains(concat(@class,' '),'vcard ')</code> is broken see [[parsing-microformats#Parsing_class_values]] for a correct example --[[User:RobertBachmann|Robert Bachmann]])''

* 2005-08-12 raised by [http://home.alltel.net/jackwolfgang/contact/ Jack L. Wolfgang II]. Use of mailto transport functionality for the E-Mail address field.
*# ''As stated in the [[hcard-brainstorming]] document, mailto is abused by spammers. As a result, many organizations have moved to form-based contacts as opposed to mailtos. According to [http://www.ietf.org/rfc/rfc2426.txt RFC 2426], Section 3.3.2, "A non-standard value can also be specified." Does this refer to a non-standard e-mail address value or type value?''
*#* A: ACCEPTED FAQ. Type value.

* 2005-07-23 raised by DanConnolly
*# ''Are class names case sensitive or not? [[hcard]] says "If names in the source schema are case-insensitive, then use an all lowercase equivalent."''
*#* A: ACCEPTED FAQ. Class names are case sensitive per the HTML4 specification. Hence hCard explicitly specifies the case of class name to use for source schema names that are case-insensitive.
*# ''...but I find example data with class="Given-Name"''
*#* A: ACCEPTED RESOLVED. That is from an older preliminary version of the hCard spec which used mixed case class names. Such class names are no longer valid hCard. Please note which examples (URLs) are using the older class names and hopefully we can get them fixed.
*#** A: By [http://suda.co.uk Brian Suda] I have fixed all the references in the [[hcard-brainstorming]] page to reflect the lower-case style, this is a hold-over from the original design, X2V has been updated.
*# ''..and code that supports it [data with class="Given-Name"].''
*#* A: ACCEPTED RESOLVED. Any code supporting the older class name(s) is for backward compatibility only, and should be phased out. Any new hCard code SHOULD NOT support such mixed case class names.
*#** [http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html rfc2629xslt.html] uses Street-Address, Family-Name, etc.
*#*** A: By [http://greenbytes.de/tech/webdav/ Julian Reschke] Fixed rfc2629.xslt (2005-10-29)
*#** [http://suda.co.uk/projects/X2V/ X2V] Version 0.5.1 2005-07-08 supports Family-Name etc.
*#*** A: By [http://suda.co.uk Brian Suda] I agree that the upper-case class names can be removed from the code, this was a hold-over and will be trimmed.
*# ''The ul/ol stuff for multiple values of a property seems to be in the X2V code and in [[hcard-brainstorming]] but not in the [[hcard]] spec.''
*#* A. ACCEPTED RESOLVED. This needs to be added to the spec. 2005-11-08 Update: the way multiple values has been updated to work much better and not require ul/ol.
*# ''the [[hcard-profile]] says country-name but X2V and lots of the data I've seen says country''
*#* A. ACCEPTED RESOLVED. RFC 2426 clearly says "country name" in both the prose and the grammar, thus "country-name" is the correct class name to use. If X2V uses just "country", it needs to be fixed to use "country-name", and any such examples as well. Please note which examples (URLs) are using the class name "country" and hopefully we can get them fixed.
*#** A: By [http://suda.co.uk Brian Suda] I have fixed all the references in the [[hcard-brainstorming]] page to reflect the proper country-name, X2V will support this in the next iteration when i fix several bugs at once.

* 2005-07-22 raised by DanConnolly
*# ''...in my cellphone/sidekick address book, I have a number of entries for companies. I wrote [http://dev.w3.org/cvsweb/2001/palmagent/asHCard.xsl asHCard.xsl] to convert the data from RDF to hCard, but I don't know what to do with entries for companies, since FN is mandatory in hCard.''
*#*A: ACCEPTED FAQ. This should be an FAQ. "How do I write an hCard for a company?" The vCard specification is silent on this point (entries for companies). Thus there are two options as far as the hCard standard is concerned:
*#*# Set "fn" and "org" to the same value. E.g. <code>W3C</code> (recommended)
*#*# Set "org" as usual, and set "fn" explicitly to empty. E.g. <code>W3C</code> or
*#*#* Simply have no "fn", and on the parsing side, if there is no "fn" present, but there is an "org" property, then duplicate the "org" value as "fn"
*#*The last two options are effectively the same and are both not explicit and easily confusable with a "missing data" condition. Thus option 1 is preferred. For converting applications (hCard to vCard), they ''may'' consider using proprietary extensions to make the distinction explicit in generated vCards, based on either case 1 or 2 above. E.g. Apple's Address Book application supports the property: <code>X-ABShowAs:COMPANY</code>
*#*We are looking for descriptions of how other vCard supporting applications treat "company" vCards differently from "person" vCards. Please provide descriptions here:
*#** Address Book / MacOSX.3:
*#*** Export (e.g. drag & drop to desktop, view in text editor)
*#**** Sets "FN" and "ORG" to the name of the company
*#**** Sets proprietary <code>X-ABShowAs:COMPANY</code>
*#*** Import (e.g. edit in text editor, drag & drop from desktop)
*#**** By setting "FN" and "ORG' to the same name (e.g. Banana Computers Inc.)
*#**** And removing any proprietary properties (e.g. X-ABShowAs)
*#**** Address Book user interface showed new vCard as a "company" contact rather an a person
*#** Address Book MacOSX.4:
*#*** same results as above -RyanKing
*#** The Danger Hiptop (aka T-Mobile Sidekick) address book:
*#*** Export (e.g. [http://lists.w3.org/Archives/Public/www-archive/2005Sep/0007.html email to a mailing list])
*#**** Sets "FN" to the empty string and puts the company name in "ORG".
*#*** Import - could not find a way to import a .vcf, by email, IM, or other means into the Sidekick.
*#** Contacts / Outlook 2003 Windows
*#*** Export (e.g. Highlight contact, File, Save As, vcard)
*#**** Sets "N" and "ORG to the name of the company
*#**** Sets "FN" to value in "File as:"
*#** Add another vCard app here.

* {{OpenIssue}} 2006-01-31 raised by ??.
*# ''Issue 1: Specifying Authoritative or Canonical or Official Hcard''
* Use of rel="me" only specifies an alternate version, not necessarily the canonical version
* Suggestion: use rel="me self". Adopt "self" semantics from Atom which means "the", or controversially "alternate, equivalent" version
* Other suggestions? "via", "authoritative", "canonical"?
* Problems with this suggestion?
* How does this relate to authentication/trust issues? Is this a different problem with a different scope?
* (10:47:44) sreynen: for example, all of the examples i've seen involve a single person publishing multiple hCards of himself
(10:48:13) sreynen: yet many people are talking about 3rd parties publishing hCards and pointing back to the subject's own hCard

''TODO:'' please add apropriate context and history of this issue from the mailing list. Sign your name to your comments.

== Template ==

Please use this format (copy and paste this to the end of the list to add your issues):
* {{OpenIssue}} YYYY-MM-DD raised by [http://yourhomepage.example.com YOURNAME].
*# ''Issue 1: Here is the first issue I have.''
*# ''Issue 2: Here is the second issue I have.''

Note: large blocks of italic text are inaccessible to many readers, including people with types of visual impairment, dyslexia, etc. [http://www.intranet.man.ac.uk/accessibility/Disabilities/dyslexia.html], [https://tritonlink.ucsd.edu/portal/site/tritonlink-preview/menuitem.b4448692267a11256ec5e210514b01ca?storyID=20896]. [http://accessites.org/], [http://tlt.psu.edu/suggestions/accessibility/font.html], [http://www.wd4a.co.uk/Guidelines.htm]

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

events/2007-01-18-sf-microformats-dinner

2007-01-18T21:50:13Z

BenWest: /* San Francisco January 2007 Microformats Dinner */

= San Francisco January 2007 Microformats Dinner =

One of several microformats [[events]].

Where: Current candidate: Nova. TBD - likely somewhere in SOMA/SouthPark area, cafe style, with wifi, not too noisy
* Possibilities:
** Nova. 555 Second St San Francisco, CA 94107. (415) 543-2282. has wifi. can handle perhaps up to about 15 people.
** 21st Amendment (has wifi, too noisy)
** ...

When: Thursday January 18th, 6pm-...

Who (food prefs). Please RSVP so that we can make sure the venue can accomodate the group.

* Tantek Çelik (vegetarian or fish options)
* Ryan King
* Eric Meyer (not spicy)
* Matthew Mullenweg
* William Lawrence (vegetarian) - ''tentative''
* Kevin Marks (eats anything)
* Ben West
* Derrick Pallas
* Nicole Hanusek
* Steve Cohen
* ...

events/2007-01-18-sf-microformats-dinner

2007-01-18T21:49:34Z

BenWest: /* San Francisco January 2007 Microformats Dinner */

rel-tag-issues

2007-01-03T22:39:34Z

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

= relTag Issues =

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

== Issues ==

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

* 2005-06-21 raised by Hixie
*# ''Issue H-1: This specification is lacking a user agent conformance section. Does the UA simply crawl the DOM looking for all <html:a> elements with a "rel" attribute that contains a "tag" keyword (after space-separated splitting) and then grab the href="" value? How about relative links? Must they implement xml:base? <html:base>? Other things?
*# ''Issue H-2: What's the point? Isn't free-text search more effective than relying on people to remember to put a particular tag?

* 2006-01-10 raised by Adam Willard
*# ''Issue 1: Somewhat confused. Please either fix or elaborate the difference in the URLs in the Tag Spaces area -> is it /tag/ or /tags/ or /wiki/. Is this URI changeable or is this just showing other implementations. If this is the case I am confused on the implementation. Should /wiki/ only show tagged content of wiki? Should URIs be constructed as /definition/ /blog/ etc... to return those items? Or is it just returning pages and the webmaster just decided on /wiki/ or /tag/ or /applicationdir/?''
*#* ACCEPTED FAQ - We need to make this an FAQ entry. --[[User:RyanKing|RyanKing]] 14:46, 25 Jan 2006 (PST) (@TODO)
*# ''Issue 2: More information on actually implementing a tag space would be helpful. I wrote a tagging system on our intranet and we run IIS. So I had to install URLrewrite (ISAPI) to create the URI /tag/tagname. We horrible Microsoft people are't as lucky to have Mod Rewrite.''
*#* REJECTED IRRELEVANT - Implementing a tagspace is well outside the bounds of the rel-tag specification. --[[User:RyanKing|RyanKing]] 14:46, 25 Jan 2006 (PST)

* 2006-02-09 raised by JonathanFeinberg
*# ''Issue 1: It's bizarre to have the tag be denoted by the URL. The content of the '''a''' tag is a perfectly suitable place to '''contain''' the tag.''
*#* REJECTED, IGNORES ESTABLISHED PRACTICE. Flickr and del.icio.us and other tagging sites established the defacto standard of having the tag term be denoted by the last segment in the URL. [[rel-tag]] was designed to leverage that existing behavior. Theoretical arguments about suitability are irrelevant in the fact of overwhelming existing practice.
*# ''Issue 2: There's no way to distinguish between an individual user's notion of a tag and a global tag (i.e., Fred's java tag versus all things tagged with java.''
*#* REJECTED UNTRUE. ACCEPTED FAQ. Tag spaces (see [[rel-tag]] specification) are used for distinguishing, e.g. Flickr does this with photos from one user with a tag, vs. photos from all users with a tag. [[to-do]] - add this to the the [[rel-tag-faq]].
*# ''Issue 3: It's not reasonable to restrict the host's REST implementation according to this spec's rather limited idea of a "good" tag URL. The idea of tags as query parameters is rejected without justification, for example. Query parameters are a perfectly legitimate means of denoting state.''
*#* REJECTED, IGNORES ESTABLISHED PRACTICE. Flickr and del.icio.us and other tagging sites established the defacto standard of having the tag term be denoted by the last segment in the URL and thus defined what makes a "good" tag URL. [[rel-tag]] has codified this good practice.

* 2006-02-09 raised by Robert Yates
*# ''Issue 1: So I work alongside Jonathan at Lotus / IBM and we have several systems in development each with their own tag implementations. All of them have their own pages that are dedicated to listing the things within them that have been tagged by a given tag. Some of these systems use a url notation that ends in /tag but many (the majority) do not. We are looking to have a standard way that these systems can sematically tag their tags and relTag looked very promising. However, given that some of the systems produce tag urls that do not end in /tag we are a little stuck. It would be extremely hard and somewhat impracticle to get all these groups to ensure that their tag urls end in /tag. Are you at all considering another approach. We'd love to use relTag within our products, but at the moment we can't. Looking for some help / guidance.''
*#* Clarification: By '/tag' do you mean '/<tag-name>'? --[[User:RyanKing|RyanKing]] 15:21, 9 Feb 2006 (PST)
*#*:* yes -- rob yates 18:56, 9 Feb 2006 (EST)
*#* I wanted to do a quick survey to see how many other sites would struggle to easily adopt this format, due to the fact that they don't currently end their tag urls '/<tag-name>'. While I definately agree that ending with '/<tag-name>' is a best practice, I do feel that their needs to be an option for sites that don't do this, but still want to semantically tag their tags. Here's some sites that I found that cannot easily adopt reltag without reworking server side logic. There's some pretty big names on this list.
*#*:* O'Reilly.com. See the tags at this url http://www.xml.com/pub/a/2004/11/10/delicious.html
*#*:* Dodgeball. http://boston.dodgeball.com/tags.php
*#*:* Any typepad blog. See for instance the categories here http://ideasinfood.typepad.com/ideas_in_food/
*#*:* Eventful. http://eventful.com/
*#*:* WordPress blogs, default permalink structure (http://example.com/?cat=N). Pretty permalinks (http://example.com/category/<tagname>) are supported through various methods, but cannot be enabled by default due to technical variances in web servers and setups. The rigidity of the spec has set a high technical barrier to entry. Even if the category name were put into the URL, it would have to be in the querystring for default WordPress setups, which isn't supported in the spec. A querystring fallback (?tag=<tagname>) would enable many more systems to use rel-tag. --[[User:MarkJaquith|MarkJaquith]] 15:39, 20 Oct 2006 (PDT)

* 2006-04-06 raised by [[User:Evan|Evan]]
*# ''The scope says 'rel="tag" is specifically designed for "tagging" content, typically web pages (or portions thereof, like blog posts).', but it's not clear how to associate a tag with one portion of a web page and not another. Some common use cases: image galleries, blog posts, yellow-pages directories, hcard directories, del.icio.us-style lists of bookmarks. Does the tag apply to the <a> element's immediate containing element? All containing elements? One possibility I suggest: the tag applies to the '''most immediately enclosing element with an "id" attribute''' (addressable, at least in XHTML, as #idval), or to the entire page if there is no such element. Another possibility is having a '''tagtarget''' class, so that the parent with that class is the object being tagged.''

* 2006-11-24 raised by [[User:AndyMabbett|Andy Mabbett]]
*# Why not ''also'' allow tagging on within-page links (i.e. after "#" as well as after "/")? Then, if I have a page with sub-sections, each of those could be a tag, according to their ID:

<pre><nowiki>
<ul class="navbar">
<li><a href="#whisky" rel="tag">Whisky</a></li>
<li><a href="#wine" rel="tag">Wine</a></li>
</ul>
[...]
<h2 id="whisky">"Whisky</h2>
[...]
<h2 id="wine">"Wine</h2>
[...]
</nowiki></pre>

* 2006-11-25 raised by [[User:AndyMabbett|Andy Mabbett]]
*#Caution should be advised when recommending Wikipedia as a name-space. For example, an article about Birmingham, Alabama, tagged with a link to http://en.wikipedia.org/wiki/Birmingham would link to an article about Birmingham, England. Similarly, a tag using http://wikitravel.org/en/Newcastle will link to a disambiguation page.

* 2006-11-26 raised by [[User:AndyMabbett|Andy Mabbett]]
*#There is a danger of encouraging users to breach [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-meaningful-links WCAG 1.0 priority 2 guideline 13.6] "'''Clearly identify the target of each link'''". If a page has a link thus <code><a href="http://www.bbc.co.uk">BBC</a></code>, tagging it with a link thus <code><a href="http://www.example.com/BBC" rel="tag">BBC</a></code> will result in two links on the page, both labelled "BBC", with different targets.

*2007-01-01 raised Jan 2006 by Ben Buchanan as [http://weblog.200ok.com.au/2006/01/limitations-of-rel-microformat.html limitations of rel="tag" microformat]
*#Summary: Under the current draft, tags and relevant tagspaces are potentially hard to create; and it's still easy to abuse the system. Humans can still be tricked and so can the machines. It's a great spec if you happen to have a compliant directory structure, but if your site doesn't match then you either recreate your entire system... or, more likely, you sadly advise the client that tags aren't happening.

== Need reformatting ==

These issues were mistakenly added to the [[rel-tag-faq]] and should have been put here in the first place. They need to be reformatted as issues.

===Are tags case sensitive?===
*Are tags case sensitive. Is "Dog" the same tag as "dog" and "DOG"?

===Multi-word tags===
*How should a multi-word tag be made? For instance, if using Wikipedia as a name space, a page about a Black Redstart (a bird) would be tagged '''Black_Redstart''', with an underscore [http://en.wikipedia.org/wiki/Black_Redstart]. Is there any way of aliasing alternatives ("BlackRedstart", "Black-Redstart", etc.)? Is any particular format preferable?

==Related pages==
{{rel-tag-related-pages}}

rel-tag-issues

2007-01-03T22:36:12Z

BenWest: Reverted edit of AndyMabbett, changed back to last version by Tantek

to-do

2006-12-10T20:19:20Z

BenWest: /* Creators */ s/dichotmize/dichotomize

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

== 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 ===
# Improve community dynamics
# Tasks for helping publishers with existing established microformats: [[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], [[xfolk|xFolk]]
# Wiki cleanup/gardening for existing established microformats
# Iterate on existing established microformats, resolve issues/feedback etc.
# [[process]] improvements to help guide new microformats developments

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

=== for all microformat specs ===
* modularize any specs which are > 30K in order to avoid loss/corruption like [http://microformats.org/wiki?title=Special:Contributions&target=Evan Evan's 14 June edits] to [[hcard|hCard]], [[rel-tag]], and [[xoxo|XOXO]].
** [[hcard|hCard]] -
*** [[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.

=== iterate on current microformats ===
==== [[hreview|hReview]] ====
* Write hReview 0.3 XMDP profile, and reconcile with [[hcalendar-profile]] and [[hcard-profile]]. Makes sense to have a combined profile of all three for hReview, since hReview normatively depends on hCard and hCalendar.

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

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

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

=== 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.
* [[advocacy]] - add more pages/sites that could use microformats and find contacts for those pages to get them updated.

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>

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

=== create microformats wiki pages for ===
Need to create and complete pages for authoring and parsing.
* *-authoring for all microformats: [[hcalendar-authoring]], [[hreview-authoring]], [[xfolk-authoring]], [[hatom-authoring]]
* *-parsing for all microformats: [[hcalendar-parsing]], [[hreview-parsing]], [[xfolk-parsing]], [[hatom-parsing]]

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

=== help with microformat implementations ===
* wordpress improvements
** WP admin for new profiles
*** should simply read blog URL
*** look for hcards and parse them
* [http://gmpg.org/xfn/creator XFN Creator] localizations
** Get someone to verify the [http://gmpg.org/xfn/creator-ru XFN Creator Russian localization].
** Add it to the [http://gmpg.org/xfn/tools XFN Tools] page.
** Add rel="alternate" href="creator-ru" <link>s to the other XFN Creators.
* Conference Schedule Creator
** We need to ASAP build a simple conference schedule creator (and editor?) that builds upon the hCalendar creator. We should make it *trivial* for conference organizers to build/edit/publish an [[hcalendar|hCalendar]] schedule for their conference, including auto-generated "Subscribe..." link which produces the proper "webcal:..." link with X2V. Note: see the "axis" and "header" attributes in HTML4, specifically in the section on Tables.

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

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

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

=== random collection of other items ===
* 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 ==

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

=== hAtom2Atom ===

Some ideas for features which could be implemented :

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

<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: (hAtom2xyz.xsl)
* RSS 2.0 (meanwhile use hAtom2Atom.xsl and [http://atom.geekhood.net/ atom2rss.xsl]) -- +1 Matt Dertinger
* RSS 1.0 (meanwhile use hAtom2Atom.xsl and [http://cvs.4suite.org/viewcvs/uogbuji/atom2rss.xslt atom2rss.xslt]) -- +1 Matt Dertinger
* AtomOWL (meanwhile use hAtom2Atom.xsl and [http://dannyayers.com/2005/11/22/atomowl-xslt-progress/ atom2rdfxml.xsl])-- +1 Matt Dertinger
* 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 exploraty discussions (red links on [[to-do-fr]]
** find experts for peer-reviewing
* localize an french version of the official website
** find out the original versions of pictures (in SVG ?)
** find out french skills resources to adapt the original webdesign

== 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: (hAtom2xyz.xsl)
* RSS 2.0 (meanwhile use hAtom2Atom.xsl and [http://atom.geekhood.net/ atom2rss.xsl])
* RSS 1.0 (meanwhile use hAtom2Atom.xsl and [http://cvs.4suite.org/viewcvs/uogbuji/atom2rss.xslt atom2rss.xslt])
* AtomOWL (meanwhile use hAtom2Atom.xsl and [http://dannyayers.com/2005/11/22/atomowl-xslt-progress/ atom2rdfxml.xsl])
</li>
</ul>

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

to-do

2006-12-09T23:00:05Z

BenWest: /* Ben West (bewest) */ update my todo list with new responsibilities and incorporate tips and tricks for authoring in IA section

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

== 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 ===
# Improve community dynamics
# Tasks for helping publishers with existing established microformats: [[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], [[xfolk|xFolk]]
# Wiki cleanup/gardening for existing established microformats
# Iterate on existing established microformats, resolve issues/feedback etc.
# [[process]] improvements to help guide new microformats developments

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

=== for all microformat specs ===
* modularize any specs which are > 30K in order to avoid loss/corruption like [http://microformats.org/wiki?title=Special:Contributions&target=Evan Evan's 14 June edits] to [[hcard|hCard]], [[rel-tag]], and [[xoxo|XOXO]].
** [[hcard|hCard]] -
*** [[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.

=== iterate on current microformats ===
==== [[hreview|hReview]] ====
* Write hReview 0.3 XMDP profile, and reconcile with [[hcalendar-profile]] and [[hcard-profile]]. Makes sense to have a combined profile of all three for hReview, since hReview normatively depends on hCard and hCalendar.

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

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

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

=== 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.
* [[advocacy]] - add more pages/sites that could use microformats and find contacts for those pages to get them updated.

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>

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

=== create microformats wiki pages for ===
Need to create and complete pages for authoring and parsing.
* *-authoring for all microformats: [[hcalendar-authoring]], [[hreview-authoring]], [[xfolk-authoring]], [[hatom-authoring]]
* *-parsing for all microformats: [[hcalendar-parsing]], [[hreview-parsing]], [[xfolk-parsing]], [[hatom-parsing]]

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

=== help with microformat implementations ===
* wordpress improvements
** WP admin for new profiles
*** should simply read blog URL
*** look for hcards and parse them
* [http://gmpg.org/xfn/creator XFN Creator] localizations
** Get someone to verify the [http://gmpg.org/xfn/creator-ru XFN Creator Russian localization].
** Add it to the [http://gmpg.org/xfn/tools XFN Tools] page.
** Add rel="alternate" href="creator-ru" <link>s to the other XFN Creators.
* Conference Schedule Creator
** We need to ASAP build a simple conference schedule creator (and editor?) that builds upon the hCalendar creator. We should make it *trivial* for conference organizers to build/edit/publish an [[hcalendar|hCalendar]] schedule for their conference, including auto-generated "Subscribe..." link which produces the proper "webcal:..." link with X2V. Note: see the "axis" and "header" attributes in HTML4, specifically in the section on Tables.

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

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

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

=== random collection of other items ===
* 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 ==

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

=== hAtom2Atom ===

Some ideas for features which could be implemented :

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

<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: (hAtom2xyz.xsl)
* RSS 2.0 (meanwhile use hAtom2Atom.xsl and [http://atom.geekhood.net/ atom2rss.xsl]) -- +1 Matt Dertinger
* RSS 1.0 (meanwhile use hAtom2Atom.xsl and [http://cvs.4suite.org/viewcvs/uogbuji/atom2rss.xslt atom2rss.xslt]) -- +1 Matt Dertinger
* AtomOWL (meanwhile use hAtom2Atom.xsl and [http://dannyayers.com/2005/11/22/atomowl-xslt-progress/ atom2rdfxml.xsl])-- +1 Matt Dertinger
* 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 exploraty discussions (red links on [[to-do-fr]]
** find experts for peer-reviewing
* localize an french version of the official website
** find out the original versions of pictures (in SVG ?)
** find out french skills resources to adapt the original webdesign

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

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

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

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

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

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

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

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

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

These pages would be located respectively at

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

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

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

== Matt Dertinger (Thewhoo) ==

[[User:Thewhoo]]

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

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

to-do

2006-12-09T21:13:41Z

BenWest: /* Vocabulary */ link and quote from netlingo for boiling the ocean

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

== 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 ===
# Improve community dynamics
# Tasks for helping publishers with existing established microformats: [[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], [[xfolk|xFolk]]
# Wiki cleanup/gardening for existing established microformats
# Iterate on existing established microformats, resolve issues/feedback etc.
# [[process]] improvements to help guide new microformats developments

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

=== for all microformat specs ===
* modularize any specs which are > 30K in order to avoid loss/corruption like [http://microformats.org/wiki?title=Special:Contributions&target=Evan Evan's 14 June edits] to [[hcard|hCard]], [[rel-tag]], and [[xoxo|XOXO]].
** [[hcard|hCard]] -
*** [[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.

=== iterate on current microformats ===
==== [[hreview|hReview]] ====
* Write hReview 0.3 XMDP profile, and reconcile with [[hcalendar-profile]] and [[hcard-profile]]. Makes sense to have a combined profile of all three for hReview, since hReview normatively depends on hCard and hCalendar.

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

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

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

=== 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.
* [[advocacy]] - add more pages/sites that could use microformats and find contacts for those pages to get them updated.

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>

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

=== create microformats wiki pages for ===
Need to create and complete pages for authoring and parsing.
* *-authoring for all microformats: [[hcalendar-authoring]], [[hreview-authoring]], [[xfolk-authoring]], [[hatom-authoring]]
* *-parsing for all microformats: [[hcalendar-parsing]], [[hreview-parsing]], [[xfolk-parsing]], [[hatom-parsing]]

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

=== help with microformat implementations ===
* wordpress improvements
** WP admin for new profiles
*** should simply read blog URL
*** look for hcards and parse them
* [http://gmpg.org/xfn/creator XFN Creator] localizations
** Get someone to verify the [http://gmpg.org/xfn/creator-ru XFN Creator Russian localization].
** Add it to the [http://gmpg.org/xfn/tools XFN Tools] page.
** Add rel="alternate" href="creator-ru" <link>s to the other XFN Creators.
* Conference Schedule Creator
** We need to ASAP build a simple conference schedule creator (and editor?) that builds upon the hCalendar creator. We should make it *trivial* for conference organizers to build/edit/publish an [[hcalendar|hCalendar]] schedule for their conference, including auto-generated "Subscribe..." link which produces the proper "webcal:..." link with X2V. Note: see the "axis" and "header" attributes in HTML4, specifically in the section on Tables.

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

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

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

=== random collection of other items ===
* 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 ==

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

=== hAtom2Atom ===

Some ideas for features which could be implemented :

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

<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: (hAtom2xyz.xsl)
* RSS 2.0 (meanwhile use hAtom2Atom.xsl and [http://atom.geekhood.net/ atom2rss.xsl]) -- +1 Matt Dertinger
* RSS 1.0 (meanwhile use hAtom2Atom.xsl and [http://cvs.4suite.org/viewcvs/uogbuji/atom2rss.xslt atom2rss.xslt]) -- +1 Matt Dertinger
* AtomOWL (meanwhile use hAtom2Atom.xsl and [http://dannyayers.com/2005/11/22/atomowl-xslt-progress/ atom2rdfxml.xsl])-- +1 Matt Dertinger
* 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 exploraty discussions (red links on [[to-do-fr]]
** find experts for peer-reviewing
* localize an french version of the official website
** find out the original versions of pictures (in SVG ?)
** find out french skills resources to adapt the original webdesign

== 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]]
=== 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://dichtomize.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.

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

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

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

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

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

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

These pages would be located respectively at

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

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

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

== Matt Dertinger (Thewhoo) ==

[[User:Thewhoo]]

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

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

to-do

2006-12-07T18:54:53Z

BenWest: /* Ben West (bewest) */ todo: start a dictionary (added: boil the ocean, microformats, microformat, data fidelity, market)

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

== Tantek ==

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

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

=== for all microformat specs ===
* modularize any specs which are > 30K in order to avoid loss/corruption like [http://microformats.org/wiki?title=Special:Contributions&target=Evan Evan's 14 June edits] to [[hcard|hCard]], [[rel-tag]], and [[xoxo|XOXO]].
** [[hcard|hCard]] -
*** [[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.

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

=== iterate on current microformats ===
==== [[hreview|hReview]] ====
* Write hReview 0.3 XMDP profile, and reconcile with [[hcalendar-profile]] and [[hcard-profile]]. Makes sense to have a combined profile of all three for hReview, since hReview normatively depends on hCard and hCalendar.

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

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

=== 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.
* [[advocacy]] - add more pages/sites that could use microformats and find contacts for those pages to get them updated.

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.

=== profiles ===

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

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

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

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

=== help with microformat implementations ===
* wordpress improvements
** WP admin for new profiles
*** should simply read blog URL
*** look for hcards and parse them
* [http://gmpg.org/xfn/creator XFN Creator] localizations
** Get someone to verify the [http://gmpg.org/xfn/creator-ru XFN Creator Russian localization].
** Add it to the [http://gmpg.org/xfn/tools XFN Tools] page.
** Add rel="alternate" href="creator-ru" <link>s to the other XFN Creators.
* Conference Schedule Creator
** We need to ASAP build a simple conference schedule creator (and editor?) that builds upon the hCalendar creator. We should make it *trivial* for conference organizers to build/edit/publish an [[hcalendar|hCalendar]] schedule for their conference, including auto-generated "Subscribe..." link which produces the proper "webcal:..." link with X2V. Note: see the "axis" and "header" attributes in HTML4, specifically in the section on Tables.

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

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

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

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

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

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

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

== Dimitri Glazkov ==

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

== Chris Messina ==

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

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

=== hAtom2Atom ===

Some ideas for features which could be implemented :

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

<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: (hAtom2xyz.xsl)
* RSS 2.0 (meanwhile use hAtom2Atom.xsl and [http://atom.geekhood.net/ atom2rss.xsl]) -- +1 Matt Dertinger
* RSS 1.0 (meanwhile use hAtom2Atom.xsl and [http://cvs.4suite.org/viewcvs/uogbuji/atom2rss.xslt atom2rss.xslt]) -- +1 Matt Dertinger
* AtomOWL (meanwhile use hAtom2Atom.xsl and [http://dannyayers.com/2005/11/22/atomowl-xslt-progress/ atom2rdfxml.xsl])-- +1 Matt Dertinger
* 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 exploraty discussions (red links on [[to-do-fr]]
** find experts for peer-reviewing
* localize an french version of the official website
** find out the original versions of pictures (in SVG ?)
** find out french skills resources to adapt the original webdesign

== 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]]
=== 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. One of the technorati guys can give the history.
* 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

=== 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://dichtomize.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.

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

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

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

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

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

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

These pages would be located respectively at

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

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

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

== Matt Dertinger (Thewhoo) ==

[[User:Thewhoo]]

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

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

what-are-microformats

2006-12-07T00:04:25Z

BenWest: /* BenWest */ brone -> borne

__NOTOC__

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

= What are microformats? =

__TOC__

== Launch Definition ==

The current definition on the [http://microformats.org home page] says:

<blockquote style="font-size:larger;font-style:italic">Designed for humans first and machines second, microformats are a set of simple, open data formats built upon existing and widely adopted standards.</blockquote>

originally written by Dan Cederholm with help from Tantek Çelik for the launch of [http://microformats.org microformats.org] on June 20th, 2005.

== From The Mailing List ==

<blockquote style="font-size:larger;font-style:italic">Microformats are simple conventions for embedding semantics in HTML to enable decentralized development.</blockquote>

from someone on the microformats-discuss mailing list. Please link/cite if you know the origin of this.

== More Specifically From The Mailing List ==

More precisely, microformats can be
defined as:

<blockquote style="font-size:larger;font-style:italic">
<pre>
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
</pre>
</blockquote>

from someone(s) on the microformats-discuss mailing list. Please link/cite if you know the origin of this.

(I'm pretty sure Ernie kicked off this particular definition, and I think helped a little, but I don't remember the specifics. -Tantek)

== Chris Messina ==

<blockquote style="font-size:larger;font-style:italic">
Microformats are simple codes that you can use to identify specific kinds of data, like people or events, in your webpages.
</blockquote>

== Tantek Çelik ==

<blockquote style="font-size:larger;font-style:italic">Microformats are the way to publish and share information on the web with higher fidelity.For example, if a company wanted their contact information to be easily found and shared, they would publish it with [[hcard|hCard]]. Similarly if an organization is planning a series of events and wants more people to know about them and add them to their calendars, then they would publish their events listing with [[hcalendar|hCalendar]]. For advocacy groups, whenever they take a position on some political leader, some piece of legislation etc., if they wanted their evaluations/reviews/ratings of those people/laws to be more easily found and passed around, they would publish such opinions with [[hreview|hReview]]. For all of these, to make it easier, publishers can use [[implementations|tools and services that support microformats]].The key here is that microformats are simple/easy enough that the any organizations own web authors/designers can easily add them in themselves. Adding microformats is easier than publishing an RSS feed for example. You don't have to be a programmer. Anyone with decent (X)HTML+CSS authoring/writing skills can use microformats. Pretty much anyone who is literate can be taught how to author HTML+CSS, and thus microformats makes use of very widely available skill sets.</blockquote>

From an IRC conversation 2006-06-06 which helped "knowprose" grok microformats. Update 2006-06-07: knowprose's blog post [http://www.knowprose.com/node/15844 Making Sense of Microformats: Have Data, Will Find It].

<blockquote style="font-size:larger;font-style:italic">microformats are carefully designed (X)HTML class names that extend the semantics of (X)HTML and enable authors to publish higher semantic fidelity content such as people, events, reviews, etc.</blockquote>

From an IRC conversation 2006-07-28 with tcaspers on irc.freenode.net/#wasp.

== Drew McLellan ==

<blockquote style="font-size:larger;font-style:italic">Microformats are a way of attaching extra meaning to the information published on a web page. This extra semantic richness works alongside the information already presented, and can be used for the benefit of people and computers. This is mostly done through adding special pre-defined names to the class attribute of existing XHTML markup.</blockquote>

from an IRC conversation

== Joe Andrieu ==

<blockquote style="font-size:larger;font-style:italic">Designed for humans first and machines second, microformats are a set of simple, open data formats built upon (X)HTML and CSS.

The current blurb leaves me wondering "But what are they?". I remember this feeling from the first time reading through the microformats wiki. The [http://microformats.org/about/ about page] goes on from the opening blurb to state what microformats are, what microformats are not, and the microformats principles.

All great descriptions... Yet still leaving me wondering the most basic level of concreteness: What are they? Javascript libraries? An XML vocabulary? PHP tools? The most specific language is "data format standard." Is that like HTML? Is it just an RFC for the next web thing? 

Of course, I know the answers to all of these things, now. But it took me a while to get there.

This suggestion attempts to concretize the "existing and widely adopted standards". It's a bit shorter and to my eye a bit clearer and more powerful.
</blockquote>

== From The Wiki ==

There are unsettling faults with the definitions and explanations given. The writing seems to be a rallying cry for proponents - clever wording, impressive noun-phrases. But it explains nothing to those unfamiliar with microformats. Imagine giving this sort of explanation off-paper: "A Microformat? What do you mean?" one asks. "Well," the other replies, as he jumps onto the nearest table, his voice excited and booming, a crowd gathering around him:

<blockquote style="font-style:italic">
Designed for humans first and machines second, microformats are a set of simple, open data formats built upon existing and widely adopted standards. Instead of throwing away what works today, microformats intend to solve simpler problems first by adapting to current behaviors and usage patterns (e.g. XHTML, blogging). [...]
</blockquote>

Ah, I see now. So it's something for people to use. Something simple and intuitive, like a steering wheel. Something open, easily changed by anyone, like a wiki or linux. A data format, like rtf, xml, or pdf. It obeys unspecified standards, but is so much more! It's based on something that already works. It doesn't attempt to solve anything it doesn't need to. It dynamically changes to comply with how I'm behaving at the moment... Yes. Yes! This is what I need! My living text streaming-based DOM machine/user -interface will never be the same, now that I have Microformats! Er... right?

<blockquote style="font-size:larger;font-style:italic">
Microformats are conventions for marking up commonly-encountered data (such as links, contact information, and calendar events) in established languages such as HTML. By using standardized layouts, CSS classes, and attribute values, information becomes more accessible and useful to both humans and computers.
</blockquote>

I would appreciate if someone would copy this to the mailing list, since I don't wish to sign up, but would like this to be remedied. [[User:M|M]] 23:52, 23 Aug 2006 (PDT)

==Alok Jain==
<blockquote style="font-size:larger;font-style:italic">microformats are evolving frameworks for how to present commonly used data items. For e.g. hCard microformat provides framework to capture a person's details First, middle, last name,company, contact info etc.</blockquote>

In my view this is doing two things:
*a Bringing some amount of standardization to commonly used data sets, which can lead to several benefits towards data retreival
*a Bringing an implicit meta data structure which again can be used to fetch informaiton at more granular level. SO in above example one could fetch just the company name, even thought there is not meta data around company name

[http://www.iPrincipia.com Alok Jain]
== Dave Sanford ==

Chris asked me to contribute my 'definition,' although I refer to it as a distillation:

“Microformats are a way of identifying and labeling classes of commonly used data that make it easier for humans or computers to locate or distribute such information on websites.”

==Andy Mabbett==

Here's my re-write of the current opening blurb, from:

<blockquote style="font-size:larger">Designed for humans first and machines second, microformats are a set of simple, open data formats built upon existing and widely adopted standards.</blockquote>

to:

<blockquote style="font-size:larger;">Microformats are a way of adding simple markup to human-readable data items such as events, contact details or locations, on web pages, so that the information in them can be extracted by software and indexed, searched for, saved, cross-referenced or combined.</blockquote>

Which can be followed by:

<blockquote style="font-size:larger;">More technically, they are items of semantic markup, using just standard (X)HTML with a set of common class-names. They are open and available, freely, for anyone to use.</blockquote>

Principles:
*Start with "Microformats are"
*Mention web pages
*Say what purpose microformats serve
*Use plain language

Finally: don't use italics for whole paragraphs, it's harder for people (such as some with dyslexia or other cognitive disabilities) to read.

== Guillaume Lebleu ==

<blockquote style="font-size:larger;font-style:italic">Microformats are simple standardized annotations of content available on the Web that provide a practical solution today to more productive and decentralized Web-based information search and sharing. </blockquote>

<blockquote style="font-size:larger;font-style:italic">In other words, Microformats allow you today to copy/paste information from a Web page, for instance someone's contact information from their blog to your address book, instead of manually retyping it. Eventually, microformats will allow anyone to make the information they publish easily sharable and searchable (products, events, resume, etc.) without having to duplicate and maintain up-to-date their data in centralized databases.</blockquote>

== Richard Quick ==
This isn't a definition of microformats, it's more of an explanation of them...

<blockquote style="font-size:larger;">Every web page contains information. Most websites have a contact page, with a phone number, email address and possibly a street address. Others have reviews of products, books or CDs.</blockquote>

<blockquote style="font-size:larger;">Microformats are a way to label certain information, like contact details or reviews, so it can easily be extracted from your web page by a suitable computer program or web-based application.</blockquote>

<blockquote style="font-size:larger;">Although microformats exist to make it easier for computers to extract information from web pages, they’re designed to be easy to use by people. For example, many microformats simply involve adding certain class names to an HTML tag (others use rel attributes, for example).</blockquote>

<blockquote style="font-size:larger;">If a web page uses HTML on its own, it's very difficult (bordering on impossible in some cases) to write a computer program which can examine the web page, work out what kind of information is on the page, and extract that information.</blockquote>

<blockquote style="font-size:larger;">For example, look at the following address:

<pre>John Smith
1 Seaview Lane,
Mousehole,
Cornwall,
UK.</pre></blockquote>

<blockquote style="font-size:larger;">How can a computer program work out what kind of information the word "[http://en.wikipedia.org/wiki/Mousehole Mousehole]" is? Is it a town? Is it a country? Is it a hole where mice live?</blockquote>

<blockquote style="font-size:larger;">Obviously, it's going to be pretty difficult. However, using the '''[[hCard]]''' microformat, you can label each piece of information so that it's obvious to a computer what kind of information the word "Mousehole" is.

<pre><div class="vcard">
John Smith,
<div class="adr">
<div class="street-address">1 Seaview Lane</div>,
Mousehole,
Cornwall,
UK
</div>
</div></pre></blockquote>

<blockquote style="font-size:larger;">So is that all microformats are? A bunch of class names (and other similarly easy-to-use attributes)?</blockquote>

<blockquote style="font-size:larger;">Yes, that's basically all they are.</blockquote>

<blockquote style="font-size:larger;">They key is that everybody uses the same class names (and other attributes). In the example above, you can see that the div around word "Moushole", has "locality" as its class name. Of course, "city", "town" or "village" would all have been equally suitable class names to use, however by standardizing on one specific class name it makes it easy to write a computer program which can examine a web page, check for any microformats and then extract the information from that page.</blockquote>

<blockquote style="font-size:larger;">Also, in the above example you might have noticed the following code:

<pre><div class="vcard"></pre>

Why have we used "vcard" when the name of the microformat is hCard?</blockquote>

<blockquote style="font-size:larger;">Well, another important feature of microformats is that they don't try to reinvent the wheel. </blockquote>

<blockquote style="font-size:larger;">There was already an existing standard for labelling contact details on desktop computer, the [http://en.wikipedia.org/wiki/Vcard V Card]. V Cards are small files containing your contact information, which you can send to people you know. They can then import those contact details into any piece of software that supports the V Card format, for example Outlook Express.</blockquote>

<blockquote style="font-size:larger;">Rather than coming up with a whole new way of labelling contact information, the hCard microformat uses the same structure as V Cards. (the "h" in hCard stands for hypertext, by the way).</blockquote>

<blockquote style="font-size:larger;">And that's pretty much it. Microformats are a way of labelling information on web pages, so that it can be extracted by a computer program or web application. They're designed to be easy to use for people, and where possible, they are based in existing standards used elsewhere.</blockquote>

[http://www.richardquickdesign.com RQ]
*Superb plain-language intro! [[User:AndyMabbett|AndyMabbett]] 01:02, 26 Oct 2006 (PDT)

== BenWest ==

<blockquote style="font-size:larger;">
A microformat is a specific collection of names, values, and accompanying structure defined through rigorous market research intended to consider pervasive use of semantic html that increases data fidelity in HTML-borne data widely distributed on the web.

Microformats are more than one of these, eg "hcard and hcal are microformats."
</blockquote>

== Add Yours Here ==

<blockquote style="font-size:larger;">microformats are...</blockquote>

written by You.

== See Also ==

* [[what-can-you-do-with-microformats]]
* [[faq]]

== Translation ==
* [[what-are-microformats-fr|c'est quoi les microformats]] (fr)

what-are-microformats

2006-12-07T00:03:32Z

BenWest: dense definition

__NOTOC__

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

= What are microformats? =

__TOC__

== Launch Definition ==

The current definition on the [http://microformats.org home page] says:

<blockquote style="font-size:larger;font-style:italic">Designed for humans first and machines second, microformats are a set of simple, open data formats built upon existing and widely adopted standards.</blockquote>

originally written by Dan Cederholm with help from Tantek Çelik for the launch of [http://microformats.org microformats.org] on June 20th, 2005.

== From The Mailing List ==

<blockquote style="font-size:larger;font-style:italic">Microformats are simple conventions for embedding semantics in HTML to enable decentralized development.</blockquote>

from someone on the microformats-discuss mailing list. Please link/cite if you know the origin of this.

== More Specifically From The Mailing List ==

More precisely, microformats can be
defined as:

<blockquote style="font-size:larger;font-style:italic">
<pre>
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
</pre>
</blockquote>

from someone(s) on the microformats-discuss mailing list. Please link/cite if you know the origin of this.

(I'm pretty sure Ernie kicked off this particular definition, and I think helped a little, but I don't remember the specifics. -Tantek)

== Chris Messina ==

<blockquote style="font-size:larger;font-style:italic">
Microformats are simple codes that you can use to identify specific kinds of data, like people or events, in your webpages.
</blockquote>

== Tantek Çelik ==

<blockquote style="font-size:larger;font-style:italic">Microformats are the way to publish and share information on the web with higher fidelity.For example, if a company wanted their contact information to be easily found and shared, they would publish it with [[hcard|hCard]]. Similarly if an organization is planning a series of events and wants more people to know about them and add them to their calendars, then they would publish their events listing with [[hcalendar|hCalendar]]. For advocacy groups, whenever they take a position on some political leader, some piece of legislation etc., if they wanted their evaluations/reviews/ratings of those people/laws to be more easily found and passed around, they would publish such opinions with [[hreview|hReview]]. For all of these, to make it easier, publishers can use [[implementations|tools and services that support microformats]].The key here is that microformats are simple/easy enough that the any organizations own web authors/designers can easily add them in themselves. Adding microformats is easier than publishing an RSS feed for example. You don't have to be a programmer. Anyone with decent (X)HTML+CSS authoring/writing skills can use microformats. Pretty much anyone who is literate can be taught how to author HTML+CSS, and thus microformats makes use of very widely available skill sets.</blockquote>

From an IRC conversation 2006-06-06 which helped "knowprose" grok microformats. Update 2006-06-07: knowprose's blog post [http://www.knowprose.com/node/15844 Making Sense of Microformats: Have Data, Will Find It].

<blockquote style="font-size:larger;font-style:italic">microformats are carefully designed (X)HTML class names that extend the semantics of (X)HTML and enable authors to publish higher semantic fidelity content such as people, events, reviews, etc.</blockquote>

From an IRC conversation 2006-07-28 with tcaspers on irc.freenode.net/#wasp.

== Drew McLellan ==

<blockquote style="font-size:larger;font-style:italic">Microformats are a way of attaching extra meaning to the information published on a web page. This extra semantic richness works alongside the information already presented, and can be used for the benefit of people and computers. This is mostly done through adding special pre-defined names to the class attribute of existing XHTML markup.</blockquote>

from an IRC conversation

== Joe Andrieu ==

<blockquote style="font-size:larger;font-style:italic">Designed for humans first and machines second, microformats are a set of simple, open data formats built upon (X)HTML and CSS.

The current blurb leaves me wondering "But what are they?". I remember this feeling from the first time reading through the microformats wiki. The [http://microformats.org/about/ about page] goes on from the opening blurb to state what microformats are, what microformats are not, and the microformats principles.

All great descriptions... Yet still leaving me wondering the most basic level of concreteness: What are they? Javascript libraries? An XML vocabulary? PHP tools? The most specific language is "data format standard." Is that like HTML? Is it just an RFC for the next web thing? 

Of course, I know the answers to all of these things, now. But it took me a while to get there.

This suggestion attempts to concretize the "existing and widely adopted standards". It's a bit shorter and to my eye a bit clearer and more powerful.
</blockquote>

== From The Wiki ==

There are unsettling faults with the definitions and explanations given. The writing seems to be a rallying cry for proponents - clever wording, impressive noun-phrases. But it explains nothing to those unfamiliar with microformats. Imagine giving this sort of explanation off-paper: "A Microformat? What do you mean?" one asks. "Well," the other replies, as he jumps onto the nearest table, his voice excited and booming, a crowd gathering around him:

<blockquote style="font-style:italic">
Designed for humans first and machines second, microformats are a set of simple, open data formats built upon existing and widely adopted standards. Instead of throwing away what works today, microformats intend to solve simpler problems first by adapting to current behaviors and usage patterns (e.g. XHTML, blogging). [...]
</blockquote>

Ah, I see now. So it's something for people to use. Something simple and intuitive, like a steering wheel. Something open, easily changed by anyone, like a wiki or linux. A data format, like rtf, xml, or pdf. It obeys unspecified standards, but is so much more! It's based on something that already works. It doesn't attempt to solve anything it doesn't need to. It dynamically changes to comply with how I'm behaving at the moment... Yes. Yes! This is what I need! My living text streaming-based DOM machine/user -interface will never be the same, now that I have Microformats! Er... right?

<blockquote style="font-size:larger;font-style:italic">
Microformats are conventions for marking up commonly-encountered data (such as links, contact information, and calendar events) in established languages such as HTML. By using standardized layouts, CSS classes, and attribute values, information becomes more accessible and useful to both humans and computers.
</blockquote>

I would appreciate if someone would copy this to the mailing list, since I don't wish to sign up, but would like this to be remedied. [[User:M|M]] 23:52, 23 Aug 2006 (PDT)

==Alok Jain==
<blockquote style="font-size:larger;font-style:italic">microformats are evolving frameworks for how to present commonly used data items. For e.g. hCard microformat provides framework to capture a person's details First, middle, last name,company, contact info etc.</blockquote>

In my view this is doing two things:
*a Bringing some amount of standardization to commonly used data sets, which can lead to several benefits towards data retreival
*a Bringing an implicit meta data structure which again can be used to fetch informaiton at more granular level. SO in above example one could fetch just the company name, even thought there is not meta data around company name

[http://www.iPrincipia.com Alok Jain]
== Dave Sanford ==

Chris asked me to contribute my 'definition,' although I refer to it as a distillation:

“Microformats are a way of identifying and labeling classes of commonly used data that make it easier for humans or computers to locate or distribute such information on websites.”

==Andy Mabbett==

Here's my re-write of the current opening blurb, from:

<blockquote style="font-size:larger">Designed for humans first and machines second, microformats are a set of simple, open data formats built upon existing and widely adopted standards.</blockquote>

to:

<blockquote style="font-size:larger;">Microformats are a way of adding simple markup to human-readable data items such as events, contact details or locations, on web pages, so that the information in them can be extracted by software and indexed, searched for, saved, cross-referenced or combined.</blockquote>

Which can be followed by:

<blockquote style="font-size:larger;">More technically, they are items of semantic markup, using just standard (X)HTML with a set of common class-names. They are open and available, freely, for anyone to use.</blockquote>

Principles:
*Start with "Microformats are"
*Mention web pages
*Say what purpose microformats serve
*Use plain language

Finally: don't use italics for whole paragraphs, it's harder for people (such as some with dyslexia or other cognitive disabilities) to read.

== Guillaume Lebleu ==

<blockquote style="font-size:larger;font-style:italic">Microformats are simple standardized annotations of content available on the Web that provide a practical solution today to more productive and decentralized Web-based information search and sharing. </blockquote>

<blockquote style="font-size:larger;font-style:italic">In other words, Microformats allow you today to copy/paste information from a Web page, for instance someone's contact information from their blog to your address book, instead of manually retyping it. Eventually, microformats will allow anyone to make the information they publish easily sharable and searchable (products, events, resume, etc.) without having to duplicate and maintain up-to-date their data in centralized databases.</blockquote>

== Richard Quick ==
This isn't a definition of microformats, it's more of an explanation of them...

<blockquote style="font-size:larger;">Every web page contains information. Most websites have a contact page, with a phone number, email address and possibly a street address. Others have reviews of products, books or CDs.</blockquote>

<blockquote style="font-size:larger;">Microformats are a way to label certain information, like contact details or reviews, so it can easily be extracted from your web page by a suitable computer program or web-based application.</blockquote>

<blockquote style="font-size:larger;">Although microformats exist to make it easier for computers to extract information from web pages, they’re designed to be easy to use by people. For example, many microformats simply involve adding certain class names to an HTML tag (others use rel attributes, for example).</blockquote>

<blockquote style="font-size:larger;">If a web page uses HTML on its own, it's very difficult (bordering on impossible in some cases) to write a computer program which can examine the web page, work out what kind of information is on the page, and extract that information.</blockquote>

<blockquote style="font-size:larger;">For example, look at the following address:

<pre>John Smith
1 Seaview Lane,
Mousehole,
Cornwall,
UK.</pre></blockquote>

<blockquote style="font-size:larger;">How can a computer program work out what kind of information the word "[http://en.wikipedia.org/wiki/Mousehole Mousehole]" is? Is it a town? Is it a country? Is it a hole where mice live?</blockquote>

<blockquote style="font-size:larger;">Obviously, it's going to be pretty difficult. However, using the '''[[hCard]]''' microformat, you can label each piece of information so that it's obvious to a computer what kind of information the word "Mousehole" is.

<pre><div class="vcard">
John Smith,
<div class="adr">
<div class="street-address">1 Seaview Lane</div>,
Mousehole,
Cornwall,
UK
</div>
</div></pre></blockquote>

<blockquote style="font-size:larger;">So is that all microformats are? A bunch of class names (and other similarly easy-to-use attributes)?</blockquote>

<blockquote style="font-size:larger;">Yes, that's basically all they are.</blockquote>

<blockquote style="font-size:larger;">They key is that everybody uses the same class names (and other attributes). In the example above, you can see that the div around word "Moushole", has "locality" as its class name. Of course, "city", "town" or "village" would all have been equally suitable class names to use, however by standardizing on one specific class name it makes it easy to write a computer program which can examine a web page, check for any microformats and then extract the information from that page.</blockquote>

<blockquote style="font-size:larger;">Also, in the above example you might have noticed the following code:

<pre><div class="vcard"></pre>

Why have we used "vcard" when the name of the microformat is hCard?</blockquote>

<blockquote style="font-size:larger;">Well, another important feature of microformats is that they don't try to reinvent the wheel. </blockquote>

<blockquote style="font-size:larger;">There was already an existing standard for labelling contact details on desktop computer, the [http://en.wikipedia.org/wiki/Vcard V Card]. V Cards are small files containing your contact information, which you can send to people you know. They can then import those contact details into any piece of software that supports the V Card format, for example Outlook Express.</blockquote>

<blockquote style="font-size:larger;">Rather than coming up with a whole new way of labelling contact information, the hCard microformat uses the same structure as V Cards. (the "h" in hCard stands for hypertext, by the way).</blockquote>

<blockquote style="font-size:larger;">And that's pretty much it. Microformats are a way of labelling information on web pages, so that it can be extracted by a computer program or web application. They're designed to be easy to use for people, and where possible, they are based in existing standards used elsewhere.</blockquote>

[http://www.richardquickdesign.com RQ]
*Superb plain-language intro! [[User:AndyMabbett|AndyMabbett]] 01:02, 26 Oct 2006 (PDT)

== BenWest ==

<blockquote style="font-size:larger;">
A microformat is a specific collection of names, values, and accompanying structure defined through rigorous market research intended to consider pervasive use of semantic html that increases data fidelity in HTML-brone data widely distributed on the web.

Microformats are more than one of these, eg "hcard and hcal are microformats."
</blockquote>

== Add Yours Here ==

<blockquote style="font-size:larger;">microformats are...</blockquote>

written by You.

== See Also ==

* [[what-can-you-do-with-microformats]]
* [[faq]]

== Translation ==
* [[what-are-microformats-fr|c'est quoi les microformats]] (fr)

press

2006-11-17T00:49:11Z

BenWest: /* 2006 */ added mention of microformats as a way to maintain data fidelity in Architecture Journal, an MS publication

__NOTOC__
<h1> Press </h1>

This page documents the press that [[microformats]] has received. See also microformats [[screencasts]], [[presentations]], [[podcasts]], and [[books]].

== 2006 ==
=== November ===
* [http://www.ascii.co.jp/books/magazines/macpeople.shtml MacPeople], a paper magazine about Macintosh in Japan, contained an article about microformats on its 12/2006 issue, written by [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], in "The Architecture Journal", an online journal of web architecture published by Microsoft, mentions microformats as a way to maintain high data fidelity in loosely coupled, highly federated systems. "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."

=== October ===
* [http://weblog.infoworld.com/techwatch/archives/008472.html INFOWORLD TECH WATCH: "Bloggers speak out on IE 7"] - published: October 20, 2006. Mention/discussion of microformats by Tantek Çelik and Kristopher Tate.
* Practical Web Design, October 2006 issue, "Microformats" article by Rachel Andrews
* W3C [http://www.w3.org/2006/10/grddl-pressrelease Press Release] GRDDL Spec

=== September ===
* ...

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

attention-examples

2006-10-23T21:29:43Z

BenWest: /* Implicit Attention */ added link to attention trust and their xml spec.

= Attention Examples =

This page documents examples on the Web of published attention information.

This is part of an open standards community effort to update (even rethink and rewrite) the [http://developers.technorati.com/wiki/attentionxml Attention.xml] format on a strong foundation of research of existing examples and formats, as well as leveraging the Attention.XML implementation experience from [http://attensa.com Attensa], [http://commerce.net CommerceNet], [http://technorati.com Technorati], and any other interested Attention developers.

== Authors ==

* Tim Brown
* Tantek Çelik
* Eric Hayes
* Rohit Khare
* Kevin Marks
* Greg Elin

== Attention Examples ==

=== Implicit Attention ===
* what I've listened to - Last.FM, and other scripts that do that
** KevinMarks will contribute more here
** eg http://www.seabury.edu/faculty/akma/2002_09_22_blogarch.html#e82241126
* ?? email rules files
* [http://wiki.attentiontrust.org/index.php/Attention-related_Software_and_Services AttentionTrust's Related section] has a list of nearby software and services that collect attention data.
** [http://www.attentiontrust.org/extension/spec AttentionTrust's attention xml] is recorded by their firefox plugin and can be sent to a chosen provider.

=== Explicit Attention ===

* blogrolls, friendrolls (e.g. LiveJournal, XFN) - what/who I'm reading
* linkblogs / delicious feeds - how I have tagged sites I've read
* playlists of what songs I like - e.g. on MSN Spaces
* favorites.html files - yes, people actually publish these on the web
** http://style.cleverchimp.com/misc/favorites.html
* [http://pyxml.sourceforge.net/topics/xbel/ xbel] xml format for bookmarks TODO: Should there be a more general bookmark topic? [[User:BenWest|BenWest]] 14:23, 23 Oct 2006 (PDT)
* Chats and chat logs
* The AttentionStream from ETech05: http://attentionstream.com

== Inattention Examples ==

* killfiles
* email blacklists

== See Also ==
* [[attention-formats]]
* [[attention-brainstorming]]

attention-examples

2006-10-23T21:23:20Z

BenWest: /* Explicit Attention */ added xbel, a bookmark xml format by the python community

= Attention Examples =

This page documents examples on the Web of published attention information.

This is part of an open standards community effort to update (even rethink and rewrite) the [http://developers.technorati.com/wiki/attentionxml Attention.xml] format on a strong foundation of research of existing examples and formats, as well as leveraging the Attention.XML implementation experience from [http://attensa.com Attensa], [http://commerce.net CommerceNet], [http://technorati.com Technorati], and any other interested Attention developers.

== Authors ==

* Tim Brown
* Tantek Çelik
* Eric Hayes
* Rohit Khare
* Kevin Marks
* Greg Elin

== Attention Examples ==

=== Implicit Attention ===
* what I've listened to - Last.FM, and other scripts that do that
** KevinMarks will contribute more here
** eg http://www.seabury.edu/faculty/akma/2002_09_22_blogarch.html#e82241126
* ?? email rules files

=== Explicit Attention ===

* blogrolls, friendrolls (e.g. LiveJournal, XFN) - what/who I'm reading
* linkblogs / delicious feeds - how I have tagged sites I've read
* playlists of what songs I like - e.g. on MSN Spaces
* favorites.html files - yes, people actually publish these on the web
** http://style.cleverchimp.com/misc/favorites.html
* [http://pyxml.sourceforge.net/topics/xbel/ xbel] xml format for bookmarks TODO: Should there be a more general bookmark topic? [[User:BenWest|BenWest]] 14:23, 23 Oct 2006 (PDT)
* Chats and chat logs
* The AttentionStream from ETech05: http://attentionstream.com

== Inattention Examples ==

* killfiles
* email blacklists

== See Also ==
* [[attention-formats]]
* [[attention-brainstorming]]

to-do

2006-10-23T01:35:21Z

BenWest: /* Information Architecture */ added Chris M.'s idea re: "best of"

<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 ===
* submit patches for Drupal code/templates for microformats improvement
* Drupal modules for microformats, specifically hReview and hCalendar

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

== Tantek ==

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

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

=== for all microformat specs ===
* modularize any specs which are > 30K in order to avoid loss/corruption like [http://microformats.org/wiki?title=Special:Contributions&target=Evan Evan's 14 June edits] to [[hcard|hCard]], [[rel-tag]], and [[xoxo|XOXO]].
** [[hcard|hCard]] - need to create new pages for [[hcard-examples-in-the-wild]] (perhaps grouped/ sorted by individuals, organizations, and hosting sites?), [[hcard-implementations]] at a minimum to separate out that content, and leave short summaries in their existing place inline in the [[hcard|hCard]] spec.
** [[rel-tag]]
** [[xoxo]]

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

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

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

=== iterate on current microformats ===
==== [[hreview|hReview]] ====
* Write hReview 0.3 XMDP profile, and reconcile with [[hcalendar-profile]] and [[hcard-profile]]. Makes sense to have a combined profile of all three for hReview, since hReview normatively depends on hCard and hCalendar.

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

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

=== introduction / community ===
* microformats-discuss
** introductory email sent to new subscribers needs to direct people to [[process]] and [[how-to-play]]
* Need to add more to the [[naming-principles]], to cover in particular:
** avoid using the same name to mean two things
** avoid using two names to mean the same thing
** seek to keep the microformats vocabulary minimal, memorable, and usable.
* 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.

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.

=== profiles ===

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

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

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

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

=== help with microformat implementations ===
* wordpress improvements
** WP admin for new profiles
*** should simply read blog URL
*** look for hcards and parse them
* [http://gmpg.org/xfn/creator XFN Creator] localizations
** Get someone to verify the [http://gmpg.org/xfn/creator-ru XFN Creator Russian localization].
** Add it to the [http://gmpg.org/xfn/tools XFN Tools] page.
** Add rel="alternate" href="creator-ru" <link>s to the other XFN Creators.
* Conference Schedule Creator
** We need to ASAP build a simple conference schedule creator (and editor?) that builds upon the hCalendar creator. We should make it *trivial* for conference organizers to build/edit/publish an [[hcalendar|hCalendar]] schedule for their conference, including auto-generated "Subscribe..." link which produces the proper "webcal:..." link with X2V. Note: see the "axis" and "header" attributes in HTML4, specifically in the section on Tables.

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

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

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

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

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

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

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

== Dimitri Glazkov ==

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

== Chris Messina ==

* Work on a microformat for play-lists (is it just a XOXO ordererd list of play-items?)
* Work on a microformat for play-item (take a look at [[media-info-examples]])
* Work on microformats tutorial for designers

=== Wishlist ===

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

== Robert Bachmann ==

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

=== hAtom2Atom ===

Some ideas for features which could be implemented :

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

<ul>
<li>
Join all hfeed's inside a page (or a fragment thereof) into one feed using [http://greenbytes.de/tech/webdav/rfc4287.html#element.source atom:source] semantics.
</li>
<li>
Extraction of <code>atom:content</code>, <code>atom:summary</code> and <code>atom:title</code>:
* <code>atom:content</code> and <code>atom:summary</code> as HTML
* <code>atom:content</code> and <code>atom:summary</code> as plain-text
* <code>atom:title</code> as XHTML
* <code>atom:title</code> as HTML
</li>
<li>Support for other XSLT engines:
* MSXML
* .Net System.Xml
* Sablotron
* Oracle XSLT
* XT
</li>
<li>Support for other output formats: (hAtom2xyz.xsl)
* RSS 2.0 (meanwhile use hAtom2Atom.xsl and [http://atom.geekhood.net/ atom2rss.xsl])
* RSS 1.0 (meanwhile use hAtom2Atom.xsl and [http://cvs.4suite.org/viewcvs/uogbuji/atom2rss.xslt atom2rss.xslt])
* AtomOWL (meanwhile use hAtom2Atom.xsl and [http://dannyayers.com/2005/11/22/atomowl-xslt-progress/ atom2rdfxml.xsl])
* 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 exploraty discussions (red links on [[to-do-fr]]
** find experts for peer-reviewing
* localize an french version of the official website
** find out the original versions of pictures (in SVG ?)
** find out french skills resources to adapt the original webdesign

== 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]]
=== Creators ===
* <strike>Start hatom creator.</strike> http://dichtomize.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.

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.

== New Person 1 ==

etc.

species-examples

2006-10-22T05:20:38Z

BenWest: /* Grouped By Publisher */ saved my work for the night.

=Species Examples=

Examples of common and scientific names of living things, which could be marked up with a "'''[[species]]'''" (or similar) microformat. Note use of matching pairs of examples, where possible.

__TOC__

==binominals==

===Birds===

'''Black-tailed Godwit''' on [http://www.westmidlandbirdclub.com/ladywalk/latest.htm West Midland Bird Club's Ladywalk reserve latest news page]

<pre><nowiki>Black-tailed Godwit</nowiki></pre>

'''''Limosa limosa''''' on [http://www.westmidlandbirdclub.com/records/lists.htm West Midland Bird Club's county lists']

<pre><nowiki><td>Limosa limosa</td></nowiki></pre>

===Mammal===
'''Wolf''' on [http://www.wolf.org/wolves/index.asp International Wolf Center]

===Fish===
'''Northern pike''' on [http://www.dnr.state.mn.us/fish/northern/index.html Minnesota Department of Natural Resources]

'''''Esox lucius''''' on [http://www.pikezander.co.uk/pike.htm Pike & Zander]

===Insect===
'''Death’s Head Hawkmoth''' on [http://funkman.org/animal/insect/deathheadmoth.html Animal Teachers]

'''''Acherontia atropos''''' on [http://ukmoths.org.uk/show.php?id=2540 UK Moths]

'''Migrant Hawker''' (''Aeshna mixta'') on [http://www.sxbrc.org.uk/news/friston-forest-recording-day Sussex Biodiversity Record Centre]

===Arachnid===
'''''Araneus angulatus''''' on [http://www.sxbrc.org.uk/news/friston-forest-recording-day Sussex Biodiversity Record Centre] (this is a duplicate. [[User:BenWest|BenWest]] 21:56, 21 Oct 2006 (PDT))

===Plant===
'''Bog Pimpernel''' on [http://www.map-reading.co.uk/wildflowers/HTML%20files/f0219.htm Map Reading's Wildflower Images]

'''''Anagallis tenella''''' on [http://www.bioimages.org.uk/HTML/T47624.HTM BioImages]

'''''Persicaria campanulatum''''' on [http://www.record-lrc.co.uk/?Mod=Forum&Do=ViewThread&ForumID=6&ThreadID=75 rECOrd - The Biodiversity Information Centre for the Cheshire region]

===Fungi===

'''''Amanita muscaria''''' on [http://www.mykoweb.com/CAF/species/Amanita_muscaria.html California Fungi]
* as '''''Amanita muscaria'' (L. per Fr.) Hooker'''
* as '''''Amanita muscaria var. flavivolvata'''''

'''Fly Agaric''' on [http://www.treesforlife.org.uk/forest/mythfolk/flyagaric.html Trees for Life]

'''''Rhodocollybia maculata'' (Albertini & Schweinitz: Fries) Singer''' on [http://www.ilmyco.gen.chicago.il.us/Taxa/Rhodomacul540.html]
*also written as '''''Rhodocollybia maculata'' (Albertini & Schweinitz ex Fries) Singer'''
*(This is where a post-Linnean author is given special rights (because his descriptions were comparatively complete - i.e. recognisable) so his interpretation of earlier names is taken as the sense meant by the original author. Think these used to be "apud" and are now "ex" although a colon has also been used. There are only a few sanctioning authors, the main one being Elias Fries.(Fr.) )

==More than binominals==

===Authority===
'''''Pica pica'' Linnaeus, (1758)''' on [http://en.wikipedia.org/wiki/European_Magpie Wikipedia: European Magpie]
:(i.e. named by Linnaeus in 1758)

===Unspecified species===
'''''Podiceps sp.''''' on [http://www.birdlife.org/datazone/species/index.html?action=SpcHTMDetails.asp&sid=3644&m=0 Bird Life] <pre><nowiki>Podiceps sp.</nowiki></pre>

'''Psyllid plant hopper''' [http://ramblingsofanaturalist.blogspot.com/2006/07/bay-sucker-gall-trioza-alacris.html on Ramblings of a Naturalist blog]

===Sub-species===

====Animal====
'''''Larus glaucoides kumlieni''' on [http://www.birdguides.com/html/vidlib/species/Larus_glaucoides_kumlieni.htm BirdGuides]

'''Kumlien's Gull''' on [http://www.birdsireland.com/pages/rare_bird_news/2005/january_photos.html Birds Ireland]

====Plant====
'''''Pisum sativum L. subsp. sativum''''' on [http://www.plantnames.unimelb.edu.au/Sorting/Pisum.html] (also has other examples; note lack of required italics)
<pre><nowiki>Pisum sativum L. subsp. sativum</nowiki></pre>

===Cultivars (plant)===
'''''Chamaecyparis lawsoniana 'Aureomarginata'''''' on [http://en.wikipedia.org/wiki/Cultivar Wikipedia: Cultivar]

<pre><nowiki><dd>Chamaecyparis lawsoniana 'Aureomarginata'</dd></nowiki></pre>

'''''Chamaecyparis lawsoniana'' 'Golden Wonder'''' on [http://www.plantago.nl/plantindex/c/Chamaecyparis/Chamaecyparis_4.htm plantago.nl]

====Cultivar groups (plant)====
'''''Brassica oleracea'' Botrytis Group''' on [http://en.wikipedia.org/wiki/Cultivar Wikipedia: Cultivar]

===Trade names (plant)===

'''''Rosa'' Peace''' on [http://en.wikipedia.org/wiki/Cultivar Wikipedia: Cultivar]
:("Peace" is a trade designation or "selling name" for the cultivar R. 'Madame A. Meilland' and should therefore be printed in a different typeface from the rest of the name, without any quote marks)

'''Sunflower 'Giant Single'''' on [http://cgi.www.johnsons-seeds.com/cgi-bin/www.johnsons-seeds.com/detail/azlist/S-1 Johnsons Seeds]

'''Sunflower 'Infrared' F1''' on [http://cgi.www.johnsons-seeds.com/cgi-bin/www.johnsons-seeds.com/detail/azlist/S-1 Johnsons Seeds]
:(Note "F1" cross designation)

===Variety (plant)===
'''''Pisum sativum var. macrocarpon''''' on [http://davesgarden.com/pf/go/8/index.html Dave's Garden]

====Sub-variety (plant)====

'''''Betula ermani var. genuina subvar. brevidentata''''' on [http://www.nccpg.com/gloucestershire/wilson1.html National Council for the Conservation of Plants and Gardens, Gloucestershire Group] (plus many other examples)

===Form (plant)===

'''''Acanthocalycium spiniflorum f. klimpelianum''''' on [http://en.wikipedia.org/wiki/Form_%28botany%29 Wikipedia: form (botany)]
*aka '''''Acanthocalycium spiniflorum forma klimpelianum'''''

===Sense (plant)===
'''''Ranunculus aquatilis s.l.''''' and '''''R. aquatilis s.s'''''; on [http://www.westmidlandbirdclub.com/blithfield/plants20060815.htm Blithfield Reservoir: Survey of Flowering Plants...] (see also footnotes on that page)

===Cross (plant)===
'''''Digitalis x mertonensis''''' on [http://www.hortax.org.uk/gardenplantsnames.html Hortax]
:The hybrid name for all plants derived from the cross between '''D. purpurea''' and '''D. grandiflora'''. The "x" indicates the hybrid status.

'''''× Fatshedera lizei''''' on [http://oregonstate.edu/dept/ldplants/sci-names.htm Scientific Plant Names, Oregon State Univ., Landscape Plants]

===Strain (bacteria)===
'''''Escherichia coli O157:H7''''' on [http://www.cfsan.fda.gov/~mow/chap15.html FDA.gov]

'''''E.Coli''''' on [http://news.bbc.co.uk/1/hi/england/southern_counties/5346842.stm BBC news]

==Misc==
===Superseded names===
'''''Tringa bartramia''''' superseded by '''''Bartramia longicauda''''' on [http://www.westmidlandbirdclub.com/firsts/UPLSA.htm West Midland Bird Club's Upland Sandpiper article]

===GUID===
'''NBN Taxon Key''' for European Otter, ''Lutra lutra'', on [http://nbn.nhm.ac.uk/nhm/bin/nbntaxa.dll/taxon_details?taxon_key=NBNSYS0000005133 NBN Species Dictionary]: '''NBNSYS0000005133'''

'''LSID ([http://lsid.sourceforge.net/#whatislsid Life Science Indicator])''' for ''Popillia japonica'' on [http://names.ubio.org/browser/details2.php?names=on&authors=on&sci=on&vern=on&conceptID=&expand=&namebankID=3377001 uBio]: '''urn:lsid:ubio.org:namebank:3377001'''

===Wikipedia===
'''Black-tailed Godwit''' on [http://en.wikipedia.org/wiki/Black-tailed_Godwit Wikipedia: Black-tailed Godwit]

Wikipedia uses several sets of markup, e.g. (in-line styles and links, plus some other markup, removed, for clarity):

<pre><nowiki>The Black-tailed Godwit, Limosa limosa</nowiki></pre>

and:

<pre><nowiki>
<tr>
<td>Kingdom:</td>
<td>Animalia</td>
</tr>
<tr>
<td>Phylum:</td>
<td>Chordata</td>
</tr>
<tr>
<td>Class:</td>
<td>Aves</td>
</tr>
<tr>
<td>Order:</td>
<td>Charadriiformes</td>
</tr>
<tr>
<td>Family:</td>
<td>Scolopacidae</td>
</tr>
<tr>
<td>Genus:</td>
<td>Limosa</td>
</tr>
<tr>
<td>Species:</td>
<td>L. limosa</td>
</tr>

<tr>
<th>binominal name</th>
</tr>
<tr>
<td>Limosa limosa
<td>(Linnaeus, 1758)</td>
</tr>
</nowiki></pre>

==Quantitative evidence==

For evidence of quantitative, rather than qualitative, use of species' and other taxonomic names, see [http://microformats.org/discuss/mail/microformats-discuss/2006-September/005790.html] and [http://microformats.org/discuss/mail/microformats-discuss/2006-September/005791.html]. Furthermore:

*Wikipedia:
** '''All''' species articles, e.g. [http://en.wikipedia.org/wiki/Little_Ringed_Plover Little Ringed Plover] (see [[species-examples#Wikipedia|above]])
** '''All''' genera articles, e.g. [http://en.wikipedia.org/wiki/Plover Charadrius (Plover)]
** '''All''' higher classes, e.g. [http://en.wikipedia.org/wiki/Charadriidae Charadriidae]
** '''All''' regional lists, e.g. [http://en.wikipedia.org/wiki/List_of_British_birds:_non-passerines List of British birds]
** '''All''' dedicatees, e.g. [http://en.wikipedia.org/wiki/Alexander_Wilson Alexander Wilson]
** '''All''' authorities, e.g. [http://en.wikipedia.org/wiki/Giovanni_Antonio_Scopoli Giovanni Antonio Scopoli]
** '''All''' images of living things, e.g. [http://en.wikipedia.org/wiki/Image:Charadrius_dubius_4_%28Marek_Szczepanek%29.jpg Charadrius dubius 4 (Marek Szczepanek).jpg]
** Many reserves, lakes, and other places of interest, e.g. [http://en.wikipedia.org/wiki/Belvide Belvide]
** Many biological authors and illustrators, e.g. [http://en.wikipedia.org/wiki/John_Audubon John Audubon]; [http://en.wikipedia.org/wiki/Gilbert_White Gilbert White]
** Random articles on other topics, e.g. [http://en.wikipedia.org/wiki/Balancing_lake Balancing lake}]
** '''All the above, again''', for each alternative language e.g. [http://cy.wikipedia.org/wiki/Cwtiad_Torchog_Bach Welsh]; [http://fr.wikipedia.org/wiki/Petit_gravelot French]; [http://zh.wikipedia.org/wiki/%E9%87%91%E7%9C%B6%E9%B8%BB Chinese]

*Wikimedia Commons
** '''All''' species indexes, e.g. [http://commons.wikimedia.org/wiki/Charadrius_dubius Charadrius dubius]
** '''Each individual''' image, e.g. [http://commons.wikimedia.org/wiki/Image:Charadrius_dubius_1_%28Marek_Szczepanek%29.jpg Charadrius dubius 1 (Marek Szczepanek).jpg]
** '''Each family''' list [http://commons.wikimedia.org/wiki/Charadriidae Charadriidae]

*Wiktionary
** '''All''' species articles, e.g. [http://en.wiktionary.org/wiki/american_golden_plover American Golden Plover]
** '''All''' family articles, e.g. [http://en.wiktionary.org/wiki/plover Plover]
** '''Many of the above, in other langauges''' e.g. [http://en.wiktionary.org/wiki/aquila_reale Italian]; [http://en.wiktionary.org/wiki/%D0%B1%D0%B5%D1%80%D0%BA%D1%83%D1%82 Russian]

*Wikispecies
** '''Every''' speices, e.g. [http://species.wikimedia.org/wiki/Charadrius_dubius Charadrius dubius]
** '''Every''' genus, e.g. [http://species.wikimedia.org/wiki/Charadrius Charadrius]
** '''Every''' sub-family, e.g. [http://species.wikimedia.org/wiki/Charadriinae Charadriinae]
** '''Every''' family, e.g. [http://species.wikimedia.org/wiki/Charadriidae Charadriidae]
** and so on, for '''every other rank'''
** '''Every''' image (e.g. [http://species.wikimedia.org/wiki/Image:Charadrius_hiaticula_He.jpg Charadrius hiaticula He.jpg]

*Google
**[http://www.google.co.uk/search?hl=en&hs=dBU&client=firefox-a&rls=org.mozilla:en-US:official&sa=X&oi=spell&resnum=0&ct=result&cd=1&q=%22E+coli%22&spell=1 Google finds about '''37,600,000''' for "E coli"].
***[http://www.google.co.uk/search?hs=Apo&hl=en&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&q=%22Escherichia+coli%22&btnG=Search&meta= Google finds about '''19,500,000''' for "Escherichia coli"]
***[http://www.google.co.uk/search?hs=zqo&hl=en&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&q=%22Ecoli%22&btnG=Search&meta= Google finds about '''722,000''' for "Ecoli"].
**[http://www.google.co.uk/search?hs=vWC&hl=en&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&q=%22Homo+sapiens%22&btnG=Search&meta= Google finds about '''14,200,000''' for "Homo sapiens"]
***[http://www.google.co.uk/search?hs=vWC&hl=en&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&q=%22Homo+sapien%22+-sapiens&btnG=Search&meta= Google finds about '''273,000''' for the mis-spelling "Homo sapien" -sapiens.]
**[http://www.google.co.uk/search?q=%22%22Homo+erectus%22%22&start=0&ie=utf-8&oe=utf-8&client=firefox-a&rls=org.mozilla:en-US:official Google finds about '''1,260,000''' for ""Homo erectus"]
**[http://www.google.com/search?svnum=10&as_scoring=r&hl=en&edition=us&as_drrb=q&as_qdr=&as_mind=1&as_minm=9&as_maxd=1&as_maxm=10&q=%22Clostridium+difficile%22&ie=UTF-8&sa=N&tab=nw Google finds about '''1,380,000''' for "Clostridium difficile"].
**[http://www.google.com/search?hl=en&lr=&edition=us&q=%22Passer+domesticus%22&btnG=Search Google finds about '''841,000''' for "Passer domesticus"].
***[http://images.google.com/images?hl=en&lr=&edition=us&q=%22Passer%20domesticus%22&btnG=Search&sa=N&tab=wi Google images finds about '''3,140''' for "Passer domesticus"].
**[http://www.google.co.uk/search?hl=en&hs=oEU&client=firefox-a&rls=org.mozilla:en-US:official&sa=X&oi=spell&resnum=0&ct=result&cd=1&q=%22Acer+palmatum%22&spell=1 Google finds about '''602,000''' for "Acer palmatum"]
** At the time of writing, '''every single one''' of the first 20 [http://www.google.com/search?q=%22Noctule+bat%22 Google results for "Noctule Bat"] also includes the scientific name ''Nyctalus noctula''.

*[http://www.arkive.org/ ARKive] - '''2000''' species ("It is ARKive's current aim to compile audio-visual records, where such media exists, for the 15,000-plus species currently threatened with extinction, according to the World Conservation Union's (IUCN) Red List of Threatened Species.")

*[http://www.rhs.org.uk/rhsplantfinder/plantfinder.asp Royal Horticultural Society - RHS Plant Finder] - '''70,000''' plants

*[http://www.bacterio.net List of Prokaryotic Names (formerly List of Bacterial Names)] - 2,032 *files*; '''10,268''' published names (to 2006-09-07)

*[http://nbn.nhm.ac.uk/nhm/ UK National Biodiversity Network's Species Dictionary]

*[http://www.searchnbn.net/ UK National Biodiversity Network Gateway] - '''20 million+''' species records

*[http://www.sp2000.org/ Species 2000] - '''450,000 species'''

*[http://www.bioimages.org.uk/index.html BioImages - Virtual Fieldguide] - '''53,000''' images depicting 4,600 species (see [[species-brainstorming#Malcolm_Storey|Wiki comments from site owner]])

*[http://animaldiversity.ummz.umich.edu/ Animal Diversity Web] - "'''Thousands''' of species accounts ['''plus'''] descriptions of levels of organization above the species level, especially phyla, classes, and in some cases, orders and families. Hundreds of hyperlinked pages and images illustrate the traits and general biology of these groups"

* [http://www.ubio.org/index.php?pagename=home uBio]
**NameBank is a repository of '''millions''' of recorded biological names and facts that link those names together.
**ClassificationBank stores multiple classifications and taxonomic concepts that are the result of expert opinions. It extends the functionality of NameBank.

*[http://www.birdlife.org/datazone/species/ BirdLife International] - all birds of the world (~'''10,000''')

*[http://bugguide.net/ Bug Guide] - all insects, spiders, and allies, of the USA and Canada (most with more than one page).
** e.g. [http://bugguide.net/node/view/70875 Arge pectoralis - Birch Sawfly]

*[http://www.bto.org/birdtrack/ BirdTrack]
**[http://blx1.bto.org/bt-dailyresults/results/s171-20-06.html Lapwing]

*[http://www.discoverlife.org/ Discover Life] - "contains '''306,553''' species. The Polistes Foundation and its scientific partners plan to add high-quality identification guides, maps, images, and text for '''a million species''' by 2012. [...] Each month Discover Life serves approximately 3 million pages and images to 70,000 IP addresses"

*[http://www.record-lrc.co.uk/ rECOrd] (the Local Biological Records Centre serving the Cheshire region of England) - '''1.6 million''' species records available online for the public to search and map

===Planned sites===
*[http://herbariaunited.org/atHome/ Herbaria United] (part of The website of the Botanical Collection Managers Group (BCMG), a specialist group of the Linnean Society of London) - "The UK has the world's largest and oldest collections of herbarium specimens held in trust by museums and universities. A new project is just getting underway to put all this online."

==Notable websites==
These high-profile websites use species names

*Amazon
**[http://www.amazon.co.uk/s/?url=search-alias%3Daps&field-keywords=%22house+sparrow%22 search for "House Sparrow"]

*BBC News
**[http://news.bbc.co.uk/1/hi/uk/4835208.stm Fewer birds spotted in UK gardens]
**[http://news.bbc.co.uk/1/hi/england/london/4743250.stm Study to solve sparrow's decline riddle]

*Encyclopaedia Britannica - all species, e.g.
**[http://concise.britannica.com/ebc/article-9379473/starling Starling]

*Flickr
**[http://www.flickr.com/photos/tags/citheronia/ Tag for moth genera 'citheronia']
***[http://www.flickr.com/photos/30268343@N00/152101772/ Sample result from that search]
**[http://www.flickr.com/groups/birdguide/ Field Guide: Birds of the World] 23,073 tagged photos, as at 2006-10-21

*CNN
**[http://archives.cnn.com/2001/NATURE/01/24/dying.eagles/ Disease threatens bald eagle population]

*eBay
**[http://search.ebay.com/house-sparrow search for "House Sparrow"]

*The Guardian
**[http://environment.guardian.co.uk/conservation/story/0,,1878956,00.html The call of the wildlife]
**[http://education.guardian.co.uk/higher/news/story/0,,1665396,00.html Sparrow joins 'raped' duck in Dutch museum] (note improper capitalisation "''passer domesticus''")

*London Zoo
**[http://www.zsl.org/london-zoo/animals/birds/tawny-frogmouth,99,AN.html Tawny frogmouth]

*Microsoft
**[http://www.microsoft.com/games/zootycoon/zoo2/zoo2_ymi_animals1.asp Zoo Tycoon]

*MSN-Encarta - all species, e.g.
**[http://encarta.msn.com/encnet/refpages/search.aspx?q=vulgaris&Submit2=Go Search for "vulgaris"]

*MySpace
**[http://blog.myspace.com/index.cfm?fuseaction=blog.view&friendID=47134278&blogID=79591637]

*Nature
**[http://www.nature.com/nature/focus/avianflu/index.html Avian flu web focus]

*Nature Network, Boston
**[http://network.nature.com/boston/news/archive/2006/06/13/the-student-and-the-squid The student and the squid] '''N.B.''' site already supports rel-tag, hCard for user profiles and hCalendar for marking up events across the site.

*NASA
**[http://history.nasa.gov/SP-401/ch3.htm SP-401 Skylab, Classroom in Space. Part II - Student Experiments] ("The common Cross spider (Araneus diadematus)")

*New York Times
**[http://query.nytimes.com/gst/fullpage.html?sec=travel&res=9D04E4DE1131F93BA25751C0A9669C8B63 Where the Eagles Fly: Seeing the National Symbol]

*Snopes (Urban Legends Reference Pages)
**[http://www.snopes.com/photos/animals/fishfly.asp Fish Fly]

*United Kingdom Government
**[http://www.defra.gov.uk/wildlife-countryside/vertebrates/gen-licence.htm DEFRA: General licences under the Wildlife & Countryside Act 1981]

*United States of America Government
**ITIS, e.g. [http://www.itis.usda.gov/servlet/SingleRpt/SingleRpt?search_topic=TSN&search_value=179628 Passer Domesticus] - "authoritative taxonomic information on plants, animals, fungi, and microbes of North America and the world"

*W3C
**[http://dev.w3.org/cvsweb/2000/10/swap/test/ferrell/biology.n3?rev=1.4 An Ontology of Biology]
**[http://esw.w3.org/topic/HCLSIG_BioRDF_Subgroup/Tasks/Reagents/Status_Reports/2006-05-04 BioRDF Sub-group Status Report, 4 May 2006]

*Yahoo Groups
**[http://tech.groups.yahoo.com/group/passerdomesticus/ passerdomesticus] species as group name!

==Breaking news==
*[http://news.bbc.co.uk/1/shared/spl/hi/pop_ups/06/sci_nat_orchid_spectacular/html/1.stm BBC News: Stunning new orchids from Asia's rainforest] - 2006-10-16
*[http://news.bbc.co.uk/1/hi/sci/tech/6045802.stm BBC News: Winter home find cheers twitchers] (winter home of the northern bald ibis found) - 2006-10-13
*[http://news.bbc.co.uk/1/hi/sci/tech/6043648.stm BBC News: New mouse find is 'living fossil'] - 2006-10-12
*[http://news.bbc.co.uk/1/hi/sci/tech/6035113.stm BBC News: Giant camel fossil found in Syria] - 2006-10-10
*[http://news.bbc.co.uk/1/hi/sci/tech/5414410.stm BBC News: Sharks swim into political waters] - 2006-10-06
*[http://news.bbc.co.uk/1/hi/sci/tech/5403570.stm BBC News: 'Monster' fossil find in Arctic] - 2006-10-05

==Use in blogs==
*[http://technorati.com/search/%22passer%20domesticus%22 Technorati search for "Passer domesticus"] (367 found, as at 2006-09-25)
*[http://technorati.com/search/%22acer%20palmatum%22 Technorati search for "Acer palmatum"] (682 found, as at 2006-09-25)
*[http://technorati.com/search/%22Homo%20sapiens%22 Technorati search for "Homo sapiens"] (40,932 found, as at 2006-09-25)
*[http://technorati.com/search/birding Technorati search for "birding"] (26,472 found, as at 2006-09-25)
*[http://ramblingsofanaturalist.blogspot.com/ Ramblings of a Naturalist]
*[http://squaremetre1.blogspot.com/ The Square Metre]
*[http://windowboxwildlife.blogspot.com/index.html Windowbox Wildlife]
*[http://www.rxwildlife.org.uk/ RXWildlife]

==And finally...==
Gary Larson, in his book ''The Far Side Gallery'' (Warner Books, 1980, ISBN 0751502367) has a cartoon, showing two entomologists sitting down to eat dinner in a jungle. One says to the other "Hey! What's this ''Drosophila melanogaster'' doing in my soup?"

----
== Grouped By Publisher ==

=== West Midland Bird Club ===
* [http://www.westmidlandbirdclub.com/ladywalk/latest.htm Black-tailed Godwit]
<pre><nowiki>Black-tailed Godwit</nowiki></pre>

* [http://www.westmidlandbirdclub.com/records/lists.htm Limosa limosa ]
<pre><nowiki><td>Limosa limosa</td></nowiki></pre>

=== species.mediawiki.org ===
[http://species.wikimedia.org/wiki/Charadrius_dubius species.mediawiki.org media bird ] .
<pre><nowiki>
<dd>Regnum: <a href="/wiki/Animalia" title="Animalia">Animalia</a> (Metazoa)
<dl>
<dd>Subregnum: <a href="/wiki/Eumetazoa" title="Eumetazoa">Eumetazoa</a>
<dl>
<dd>Superphylum: Bilateria: <a href="/wiki/Deuterostomia" title="Deuterostomia">Deuterostomia</a>
<dl>
<dd>Phylum: <a href="/wiki/Chordata" title="Chordata">Chordata</a>
<dl>

<dd>Subphylum: <a href="/wiki/Vertebrata" title="Vertebrata">Vertebrata</a>
<dl>
<dd>Classis: <a href="/wiki/Aves" title="Aves">Aves</a>
<dl>
<dd>Subclassis: <a href="/wiki/Neognathae" title="Neognathae">Neognathae</a>
<dl>
<dd>Ordo: <a href="/wiki/Charadriiformes" title="Charadriiformes">Charadriiformes</a>
<dl>
<dd>Subordo: <a href="/wiki/Charadrii" title="Charadrii">Charadrii</a>

<dl>
<dd>Familia: <a href="/wiki/Charadriidae" title="Charadriidae">Charadriidae</a>
<dl>
<dd>Subfamily: <a href="/wiki/Charadriinae" title="Charadriinae">Charadriinae</a>
<dl>
<dd>Genus: <a href="/wiki/Charadrius" title="Charadrius">Charadrius</a>
<dl>
<dd>Species: Charadrius dubius
<dl>

<dd>Subspecies: <a href="/w/index.php?title=Charadrius_dubius_curonicus&action=edit" class="new" title="Charadrius dubius curonicus">C. d. curonicus</a> - <a href="/w/index.php?title=Charadrius_dubius_dubius&action=edit" class="new" title="Charadrius dubius dubius">C. d. dubius</a> - <a href="/w/index.php?title=Charadrius_dubius_jerdoni&action=edit" class="new" title="Charadrius dubius jerdoni">C. d. jerdoni</a> - <a href="/w/index.php?title=Charadrius_dubius_papuanus&action=edit" class="new" title="Charadrius dubius papuanus">C. d. papuanus</a></dd>

...
</nowiki>
</pre>

* Comments
** This feels similar to tagging to me. This particular example has a resolves the whole heirarchy, correct? [[User:BenWest|BenWest]] 17:57, 21 Oct 2006 (PDT)

=== International Wolf Center ===

[http://www.wolf.org/wolves/index.asp Wolf Example]
* Comments
** The word "wolf" appears all over, a brief look only revealed "delist
wolves" as more resolution in some free text. Is this a good example of how
species data is marked up on the web? [[User:BenWest|BenWest]] 22:20, 21 Oct 2006 (PDT)

=== Minnesota Department of Natural Resources ===
[http://www.dnr.state.mn.us/fish/northern/index.html Northern Pike Example]

<pre><nowiki>
<h1 class="last">Northern pike</h1>
</nowiki></pre>

=== Pike & Zander ===

[http://www.pikezander.co.uk/pike.htm Pike & Zander]
<pre><nowiki>
The Pike is known worldwide, a species of the family Esocidae...
</nowiki>
</pre>
<pre><nowiki>
In Europe and Asia, Esox lucius had to...
</nowiki></pre>
* Comments
** Free text, in paragraph elements.

=== funkman.org ===
[http://funkman.org/animal/insect/deathheadmoth.html Death's Head Hawkmoth Example]
Free text in paragraph elements.

=== UK Moths ===
[http://ukmoths.org.uk/show.php?id=2540 Acherontia atropos]
<pre><nowiki>
Acherontia atropos
</nowiki></pre>
<pre><nowiki>
<div id="title">Sphingidae: Sphinginae</div>
</nowiki></pre>
<pre><nowiki>
(Solanum tuberosum)
</nowiki></pre>

[http://ukmoths.org.uk/cirsiumkey.php Cirsium arvense Key]
<pre><nowiki>
Key to leaf-feeding micro-moth larvae on creeping thistle (Cirsium arvense)
</nowiki></pre>

<pre><nowiki>
1076 <a href="show.php?bf=1076">Celypha lacunana</a>. A very common polyphage, but too many varieties to include.
</nowiki></pre>
<pre><nowiki>
1380 <a href="show.php?bf=1380">Phlyctaenia perlucidalis</a>. No larval description or photographs available Feb. 2004. 
</nowiki></pre>
<pre><nowiki>
</nowiki></pre>
<pre><nowiki>
814a Scrobipalpa pauperella. No larval description or photographs available Feb. 2004.
</nowiki></pre>

* Comments
** Use of to italicize. Use of scientific names and latin. [[User:BenWest|BenWest]] 22:20, 21 Oct 2006 (PDT)
** Again, two next to last examples look like tagging. [[User:BenWest|BenWest]] 22:20, 21 Oct 2006 (PDT)

=== Sussex Biodiversity Record Centre ===

[http://www.sxbrc.org.uk/news/friston-forest-recording-day Migrant Hawker (''Aeshna mixta'')]
<pre><nowiki>
include a White Admiral (Limenitis camilla), an <a href="http://www.britishspiders.org.uk/html/nbn.php?spn=375">Araneus angulatus</a>,
</nowiki></pre>

All common names are in strong elements, the species is in an italic element,
with resolution as link text, which turns out to be a fairly consistent
convention on this particular site.

* Comments
** Again, some part of the resolution is the link text to a resource presumably
considered authoritative. Resembles tagging. This particular site also puts
common names in a strong tag, with the species in an italic tag.

TODO: remove, or at least
coalesce free text examples. create a commonalities section. [[User:BenWest|BenWest]] 22:20, 21 Oct 2006 (PDT)
TODO:
I've been working down the examples list, item by item to
reorganize by publisher, like the other *-examples pages have done. So far,
I've gone from the top of binominals to the top of the Plant section. It's a
Saturday night and time to have some fun so.... If someone continues this work
before I get a chance to continue, please note where you left off. [[User:BenWest|BenWest]] 22:20, 21 Oct 2006 (PDT)

== Alternative Grouping By Strategy ==
I'd like to regroup these examples... perhaps by publishing strategy instead of a list of what is being published. Should this be available as an alternate grouping section? In the mean time, a grouping by publisher would help analysis go smoother. [[User:BenWest|BenWest]] 17:57, 21 Oct 2006 (PDT)

I looked at several examples. Several of them feel like tagging to me. Should we attempt to note what level or resolution is available in each example?

=== Tagging ===
The [[http://species.wikimedia.org/wiki/Charadrius_dubius wiki media bird example]] is particularly interesting.
<pre><nowiki>
<dd>Regnum: <a href="/wiki/Animalia" title="Animalia">Animalia</a> (Metazoa)
<dl>
<dd>Subregnum: <a href="/wiki/Eumetazoa" title="Eumetazoa">Eumetazoa</a>
<dl>
<dd>Superphylum: Bilateria: <a href="/wiki/Deuterostomia" title="Deuterostomia">Deuterostomia</a>
<dl>
<dd>Phylum: <a href="/wiki/Chordata" title="Chordata">Chordata</a>
<dl>

<dd>Subphylum: <a href="/wiki/Vertebrata" title="Vertebrata">Vertebrata</a>
<dl>
<dd>Classis: <a href="/wiki/Aves" title="Aves">Aves</a>
<dl>
<dd>Subclassis: <a href="/wiki/Neognathae" title="Neognathae">Neognathae</a>
<dl>
<dd>Ordo: <a href="/wiki/Charadriiformes" title="Charadriiformes">Charadriiformes</a>
<dl>
<dd>Subordo: <a href="/wiki/Charadrii" title="Charadrii">Charadrii</a>

<dl>
<dd>Familia: <a href="/wiki/Charadriidae" title="Charadriidae">Charadriidae</a>
<dl>
<dd>Subfamily: <a href="/wiki/Charadriinae" title="Charadriinae">Charadriinae</a>
<dl>
<dd>Genus: <a href="/wiki/Charadrius" title="Charadrius">Charadrius</a>
<dl>
<dd>Species: Charadrius dubius
<dl>

<dd>Subspecies: <a href="/w/index.php?title=Charadrius_dubius_curonicus&action=edit" class="new" title="Charadrius dubius curonicus">C. d. curonicus</a> - <a href="/w/index.php?title=Charadrius_dubius_dubius&action=edit" class="new" title="Charadrius dubius dubius">C. d. dubius</a> - <a href="/w/index.php?title=Charadrius_dubius_jerdoni&action=edit" class="new" title="Charadrius dubius jerdoni">C. d. jerdoni</a> - <a href="/w/index.php?title=Charadrius_dubius_papuanus&action=edit" class="new" title="Charadrius dubius papuanus">C. d. papuanus</a></dd>

...
</nowiki>
</pre>
This feels similar to tagging to me. This particular example has a resolves the whole heirarchy, correct? [[User:BenWest|BenWest]] 17:57, 21 Oct 2006 (PDT)

----

==Contributors==
*[[User:AndyMabbett|Andy Mabbett]] (proponent)
*Malcolm Storey (per e-mail)
*[[User:SXBRC|Charles Roper]], [http://www.sxbrc.org.uk/ Sussex Biodiversity Record Centre] (proponent)
*[[User:SteveMcBill|Steve McWilliam]], [http://www.rECOrd-LRC.co.uk/ rECOrd - The Biodiversity Information System for the Cheshire region] (proponent)

==See also==
[[species-brainstorming]]

species-examples

2006-10-22T05:19:45Z

BenWest: moved my sections to the bottom

=Species Examples=

Examples of common and scientific names of living things, which could be marked up with a "'''[[species]]'''" (or similar) microformat. Note use of matching pairs of examples, where possible.

__TOC__

==binominals==

===Birds===

'''Black-tailed Godwit''' on [http://www.westmidlandbirdclub.com/ladywalk/latest.htm West Midland Bird Club's Ladywalk reserve latest news page]

<pre><nowiki>Black-tailed Godwit</nowiki></pre>

'''''Limosa limosa''''' on [http://www.westmidlandbirdclub.com/records/lists.htm West Midland Bird Club's county lists']

<pre><nowiki><td>Limosa limosa</td></nowiki></pre>

===Mammal===
'''Wolf''' on [http://www.wolf.org/wolves/index.asp International Wolf Center]

===Fish===
'''Northern pike''' on [http://www.dnr.state.mn.us/fish/northern/index.html Minnesota Department of Natural Resources]

'''''Esox lucius''''' on [http://www.pikezander.co.uk/pike.htm Pike & Zander]

===Insect===
'''Death’s Head Hawkmoth''' on [http://funkman.org/animal/insect/deathheadmoth.html Animal Teachers]

'''''Acherontia atropos''''' on [http://ukmoths.org.uk/show.php?id=2540 UK Moths]

'''Migrant Hawker''' (''Aeshna mixta'') on [http://www.sxbrc.org.uk/news/friston-forest-recording-day Sussex Biodiversity Record Centre]

===Arachnid===
'''''Araneus angulatus''''' on [http://www.sxbrc.org.uk/news/friston-forest-recording-day Sussex Biodiversity Record Centre] (this is a duplicate. [[User:BenWest|BenWest]] 21:56, 21 Oct 2006 (PDT))

===Plant===
'''Bog Pimpernel''' on [http://www.map-reading.co.uk/wildflowers/HTML%20files/f0219.htm Map Reading's Wildflower Images]

'''''Anagallis tenella''''' on [http://www.bioimages.org.uk/HTML/T47624.HTM BioImages]

'''''Persicaria campanulatum''''' on [http://www.record-lrc.co.uk/?Mod=Forum&Do=ViewThread&ForumID=6&ThreadID=75 rECOrd - The Biodiversity Information Centre for the Cheshire region]

===Fungi===

'''''Amanita muscaria''''' on [http://www.mykoweb.com/CAF/species/Amanita_muscaria.html California Fungi]
* as '''''Amanita muscaria'' (L. per Fr.) Hooker'''
* as '''''Amanita muscaria var. flavivolvata'''''

'''Fly Agaric''' on [http://www.treesforlife.org.uk/forest/mythfolk/flyagaric.html Trees for Life]

'''''Rhodocollybia maculata'' (Albertini & Schweinitz: Fries) Singer''' on [http://www.ilmyco.gen.chicago.il.us/Taxa/Rhodomacul540.html]
*also written as '''''Rhodocollybia maculata'' (Albertini & Schweinitz ex Fries) Singer'''
*(This is where a post-Linnean author is given special rights (because his descriptions were comparatively complete - i.e. recognisable) so his interpretation of earlier names is taken as the sense meant by the original author. Think these used to be "apud" and are now "ex" although a colon has also been used. There are only a few sanctioning authors, the main one being Elias Fries.(Fr.) )

==More than binominals==

===Authority===
'''''Pica pica'' Linnaeus, (1758)''' on [http://en.wikipedia.org/wiki/European_Magpie Wikipedia: European Magpie]
:(i.e. named by Linnaeus in 1758)

===Unspecified species===
'''''Podiceps sp.''''' on [http://www.birdlife.org/datazone/species/index.html?action=SpcHTMDetails.asp&sid=3644&m=0 Bird Life] <pre><nowiki>Podiceps sp.</nowiki></pre>

'''Psyllid plant hopper''' [http://ramblingsofanaturalist.blogspot.com/2006/07/bay-sucker-gall-trioza-alacris.html on Ramblings of a Naturalist blog]

===Sub-species===

====Animal====
'''''Larus glaucoides kumlieni''' on [http://www.birdguides.com/html/vidlib/species/Larus_glaucoides_kumlieni.htm BirdGuides]

'''Kumlien's Gull''' on [http://www.birdsireland.com/pages/rare_bird_news/2005/january_photos.html Birds Ireland]

====Plant====
'''''Pisum sativum L. subsp. sativum''''' on [http://www.plantnames.unimelb.edu.au/Sorting/Pisum.html] (also has other examples; note lack of required italics)
<pre><nowiki>Pisum sativum L. subsp. sativum</nowiki></pre>

===Cultivars (plant)===
'''''Chamaecyparis lawsoniana 'Aureomarginata'''''' on [http://en.wikipedia.org/wiki/Cultivar Wikipedia: Cultivar]

<pre><nowiki><dd>Chamaecyparis lawsoniana 'Aureomarginata'</dd></nowiki></pre>

'''''Chamaecyparis lawsoniana'' 'Golden Wonder'''' on [http://www.plantago.nl/plantindex/c/Chamaecyparis/Chamaecyparis_4.htm plantago.nl]

====Cultivar groups (plant)====
'''''Brassica oleracea'' Botrytis Group''' on [http://en.wikipedia.org/wiki/Cultivar Wikipedia: Cultivar]

===Trade names (plant)===

'''''Rosa'' Peace''' on [http://en.wikipedia.org/wiki/Cultivar Wikipedia: Cultivar]
:("Peace" is a trade designation or "selling name" for the cultivar R. 'Madame A. Meilland' and should therefore be printed in a different typeface from the rest of the name, without any quote marks)

'''Sunflower 'Giant Single'''' on [http://cgi.www.johnsons-seeds.com/cgi-bin/www.johnsons-seeds.com/detail/azlist/S-1 Johnsons Seeds]

'''Sunflower 'Infrared' F1''' on [http://cgi.www.johnsons-seeds.com/cgi-bin/www.johnsons-seeds.com/detail/azlist/S-1 Johnsons Seeds]
:(Note "F1" cross designation)

===Variety (plant)===
'''''Pisum sativum var. macrocarpon''''' on [http://davesgarden.com/pf/go/8/index.html Dave's Garden]

====Sub-variety (plant)====

'''''Betula ermani var. genuina subvar. brevidentata''''' on [http://www.nccpg.com/gloucestershire/wilson1.html National Council for the Conservation of Plants and Gardens, Gloucestershire Group] (plus many other examples)

===Form (plant)===

'''''Acanthocalycium spiniflorum f. klimpelianum''''' on [http://en.wikipedia.org/wiki/Form_%28botany%29 Wikipedia: form (botany)]
*aka '''''Acanthocalycium spiniflorum forma klimpelianum'''''

===Sense (plant)===
'''''Ranunculus aquatilis s.l.''''' and '''''R. aquatilis s.s'''''; on [http://www.westmidlandbirdclub.com/blithfield/plants20060815.htm Blithfield Reservoir: Survey of Flowering Plants...] (see also footnotes on that page)

===Cross (plant)===
'''''Digitalis x mertonensis''''' on [http://www.hortax.org.uk/gardenplantsnames.html Hortax]
:The hybrid name for all plants derived from the cross between '''D. purpurea''' and '''D. grandiflora'''. The "x" indicates the hybrid status.

'''''× Fatshedera lizei''''' on [http://oregonstate.edu/dept/ldplants/sci-names.htm Scientific Plant Names, Oregon State Univ., Landscape Plants]

===Strain (bacteria)===
'''''Escherichia coli O157:H7''''' on [http://www.cfsan.fda.gov/~mow/chap15.html FDA.gov]

'''''E.Coli''''' on [http://news.bbc.co.uk/1/hi/england/southern_counties/5346842.stm BBC news]

==Misc==
===Superseded names===
'''''Tringa bartramia''''' superseded by '''''Bartramia longicauda''''' on [http://www.westmidlandbirdclub.com/firsts/UPLSA.htm West Midland Bird Club's Upland Sandpiper article]

===GUID===
'''NBN Taxon Key''' for European Otter, ''Lutra lutra'', on [http://nbn.nhm.ac.uk/nhm/bin/nbntaxa.dll/taxon_details?taxon_key=NBNSYS0000005133 NBN Species Dictionary]: '''NBNSYS0000005133'''

'''LSID ([http://lsid.sourceforge.net/#whatislsid Life Science Indicator])''' for ''Popillia japonica'' on [http://names.ubio.org/browser/details2.php?names=on&authors=on&sci=on&vern=on&conceptID=&expand=&namebankID=3377001 uBio]: '''urn:lsid:ubio.org:namebank:3377001'''

===Wikipedia===
'''Black-tailed Godwit''' on [http://en.wikipedia.org/wiki/Black-tailed_Godwit Wikipedia: Black-tailed Godwit]

Wikipedia uses several sets of markup, e.g. (in-line styles and links, plus some other markup, removed, for clarity):

<pre><nowiki>The Black-tailed Godwit, Limosa limosa</nowiki></pre>

and:

<pre><nowiki>
<tr>
<td>Kingdom:</td>
<td>Animalia</td>
</tr>
<tr>
<td>Phylum:</td>
<td>Chordata</td>
</tr>
<tr>
<td>Class:</td>
<td>Aves</td>
</tr>
<tr>
<td>Order:</td>
<td>Charadriiformes</td>
</tr>
<tr>
<td>Family:</td>
<td>Scolopacidae</td>
</tr>
<tr>
<td>Genus:</td>
<td>Limosa</td>
</tr>
<tr>
<td>Species:</td>
<td>L. limosa</td>
</tr>

<tr>
<th>binominal name</th>
</tr>
<tr>
<td>Limosa limosa
<td>(Linnaeus, 1758)</td>
</tr>
</nowiki></pre>

==Quantitative evidence==

For evidence of quantitative, rather than qualitative, use of species' and other taxonomic names, see [http://microformats.org/discuss/mail/microformats-discuss/2006-September/005790.html] and [http://microformats.org/discuss/mail/microformats-discuss/2006-September/005791.html]. Furthermore:

*Wikipedia:
** '''All''' species articles, e.g. [http://en.wikipedia.org/wiki/Little_Ringed_Plover Little Ringed Plover] (see [[species-examples#Wikipedia|above]])
** '''All''' genera articles, e.g. [http://en.wikipedia.org/wiki/Plover Charadrius (Plover)]
** '''All''' higher classes, e.g. [http://en.wikipedia.org/wiki/Charadriidae Charadriidae]
** '''All''' regional lists, e.g. [http://en.wikipedia.org/wiki/List_of_British_birds:_non-passerines List of British birds]
** '''All''' dedicatees, e.g. [http://en.wikipedia.org/wiki/Alexander_Wilson Alexander Wilson]
** '''All''' authorities, e.g. [http://en.wikipedia.org/wiki/Giovanni_Antonio_Scopoli Giovanni Antonio Scopoli]
** '''All''' images of living things, e.g. [http://en.wikipedia.org/wiki/Image:Charadrius_dubius_4_%28Marek_Szczepanek%29.jpg Charadrius dubius 4 (Marek Szczepanek).jpg]
** Many reserves, lakes, and other places of interest, e.g. [http://en.wikipedia.org/wiki/Belvide Belvide]
** Many biological authors and illustrators, e.g. [http://en.wikipedia.org/wiki/John_Audubon John Audubon]; [http://en.wikipedia.org/wiki/Gilbert_White Gilbert White]
** Random articles on other topics, e.g. [http://en.wikipedia.org/wiki/Balancing_lake Balancing lake}]
** '''All the above, again''', for each alternative language e.g. [http://cy.wikipedia.org/wiki/Cwtiad_Torchog_Bach Welsh]; [http://fr.wikipedia.org/wiki/Petit_gravelot French]; [http://zh.wikipedia.org/wiki/%E9%87%91%E7%9C%B6%E9%B8%BB Chinese]

*Wikimedia Commons
** '''All''' species indexes, e.g. [http://commons.wikimedia.org/wiki/Charadrius_dubius Charadrius dubius]
** '''Each individual''' image, e.g. [http://commons.wikimedia.org/wiki/Image:Charadrius_dubius_1_%28Marek_Szczepanek%29.jpg Charadrius dubius 1 (Marek Szczepanek).jpg]
** '''Each family''' list [http://commons.wikimedia.org/wiki/Charadriidae Charadriidae]

*Wiktionary
** '''All''' species articles, e.g. [http://en.wiktionary.org/wiki/american_golden_plover American Golden Plover]
** '''All''' family articles, e.g. [http://en.wiktionary.org/wiki/plover Plover]
** '''Many of the above, in other langauges''' e.g. [http://en.wiktionary.org/wiki/aquila_reale Italian]; [http://en.wiktionary.org/wiki/%D0%B1%D0%B5%D1%80%D0%BA%D1%83%D1%82 Russian]

*Wikispecies
** '''Every''' speices, e.g. [http://species.wikimedia.org/wiki/Charadrius_dubius Charadrius dubius]
** '''Every''' genus, e.g. [http://species.wikimedia.org/wiki/Charadrius Charadrius]
** '''Every''' sub-family, e.g. [http://species.wikimedia.org/wiki/Charadriinae Charadriinae]
** '''Every''' family, e.g. [http://species.wikimedia.org/wiki/Charadriidae Charadriidae]
** and so on, for '''every other rank'''
** '''Every''' image (e.g. [http://species.wikimedia.org/wiki/Image:Charadrius_hiaticula_He.jpg Charadrius hiaticula He.jpg]

*Google
**[http://www.google.co.uk/search?hl=en&hs=dBU&client=firefox-a&rls=org.mozilla:en-US:official&sa=X&oi=spell&resnum=0&ct=result&cd=1&q=%22E+coli%22&spell=1 Google finds about '''37,600,000''' for "E coli"].
***[http://www.google.co.uk/search?hs=Apo&hl=en&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&q=%22Escherichia+coli%22&btnG=Search&meta= Google finds about '''19,500,000''' for "Escherichia coli"]
***[http://www.google.co.uk/search?hs=zqo&hl=en&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&q=%22Ecoli%22&btnG=Search&meta= Google finds about '''722,000''' for "Ecoli"].
**[http://www.google.co.uk/search?hs=vWC&hl=en&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&q=%22Homo+sapiens%22&btnG=Search&meta= Google finds about '''14,200,000''' for "Homo sapiens"]
***[http://www.google.co.uk/search?hs=vWC&hl=en&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&q=%22Homo+sapien%22+-sapiens&btnG=Search&meta= Google finds about '''273,000''' for the mis-spelling "Homo sapien" -sapiens.]
**[http://www.google.co.uk/search?q=%22%22Homo+erectus%22%22&start=0&ie=utf-8&oe=utf-8&client=firefox-a&rls=org.mozilla:en-US:official Google finds about '''1,260,000''' for ""Homo erectus"]
**[http://www.google.com/search?svnum=10&as_scoring=r&hl=en&edition=us&as_drrb=q&as_qdr=&as_mind=1&as_minm=9&as_maxd=1&as_maxm=10&q=%22Clostridium+difficile%22&ie=UTF-8&sa=N&tab=nw Google finds about '''1,380,000''' for "Clostridium difficile"].
**[http://www.google.com/search?hl=en&lr=&edition=us&q=%22Passer+domesticus%22&btnG=Search Google finds about '''841,000''' for "Passer domesticus"].
***[http://images.google.com/images?hl=en&lr=&edition=us&q=%22Passer%20domesticus%22&btnG=Search&sa=N&tab=wi Google images finds about '''3,140''' for "Passer domesticus"].
**[http://www.google.co.uk/search?hl=en&hs=oEU&client=firefox-a&rls=org.mozilla:en-US:official&sa=X&oi=spell&resnum=0&ct=result&cd=1&q=%22Acer+palmatum%22&spell=1 Google finds about '''602,000''' for "Acer palmatum"]
** At the time of writing, '''every single one''' of the first 20 [http://www.google.com/search?q=%22Noctule+bat%22 Google results for "Noctule Bat"] also includes the scientific name ''Nyctalus noctula''.

*[http://www.arkive.org/ ARKive] - '''2000''' species ("It is ARKive's current aim to compile audio-visual records, where such media exists, for the 15,000-plus species currently threatened with extinction, according to the World Conservation Union's (IUCN) Red List of Threatened Species.")

*[http://www.rhs.org.uk/rhsplantfinder/plantfinder.asp Royal Horticultural Society - RHS Plant Finder] - '''70,000''' plants

*[http://www.bacterio.net List of Prokaryotic Names (formerly List of Bacterial Names)] - 2,032 *files*; '''10,268''' published names (to 2006-09-07)

*[http://nbn.nhm.ac.uk/nhm/ UK National Biodiversity Network's Species Dictionary]

*[http://www.searchnbn.net/ UK National Biodiversity Network Gateway] - '''20 million+''' species records

*[http://www.sp2000.org/ Species 2000] - '''450,000 species'''

*[http://www.bioimages.org.uk/index.html BioImages - Virtual Fieldguide] - '''53,000''' images depicting 4,600 species (see [[species-brainstorming#Malcolm_Storey|Wiki comments from site owner]])

*[http://animaldiversity.ummz.umich.edu/ Animal Diversity Web] - "'''Thousands''' of species accounts ['''plus'''] descriptions of levels of organization above the species level, especially phyla, classes, and in some cases, orders and families. Hundreds of hyperlinked pages and images illustrate the traits and general biology of these groups"

* [http://www.ubio.org/index.php?pagename=home uBio]
**NameBank is a repository of '''millions''' of recorded biological names and facts that link those names together.
**ClassificationBank stores multiple classifications and taxonomic concepts that are the result of expert opinions. It extends the functionality of NameBank.

*[http://www.birdlife.org/datazone/species/ BirdLife International] - all birds of the world (~'''10,000''')

*[http://bugguide.net/ Bug Guide] - all insects, spiders, and allies, of the USA and Canada (most with more than one page).
** e.g. [http://bugguide.net/node/view/70875 Arge pectoralis - Birch Sawfly]

*[http://www.bto.org/birdtrack/ BirdTrack]
**[http://blx1.bto.org/bt-dailyresults/results/s171-20-06.html Lapwing]

*[http://www.discoverlife.org/ Discover Life] - "contains '''306,553''' species. The Polistes Foundation and its scientific partners plan to add high-quality identification guides, maps, images, and text for '''a million species''' by 2012. [...] Each month Discover Life serves approximately 3 million pages and images to 70,000 IP addresses"

*[http://www.record-lrc.co.uk/ rECOrd] (the Local Biological Records Centre serving the Cheshire region of England) - '''1.6 million''' species records available online for the public to search and map

===Planned sites===
*[http://herbariaunited.org/atHome/ Herbaria United] (part of The website of the Botanical Collection Managers Group (BCMG), a specialist group of the Linnean Society of London) - "The UK has the world's largest and oldest collections of herbarium specimens held in trust by museums and universities. A new project is just getting underway to put all this online."

==Notable websites==
These high-profile websites use species names

*Amazon
**[http://www.amazon.co.uk/s/?url=search-alias%3Daps&field-keywords=%22house+sparrow%22 search for "House Sparrow"]

*BBC News
**[http://news.bbc.co.uk/1/hi/uk/4835208.stm Fewer birds spotted in UK gardens]
**[http://news.bbc.co.uk/1/hi/england/london/4743250.stm Study to solve sparrow's decline riddle]

*Encyclopaedia Britannica - all species, e.g.
**[http://concise.britannica.com/ebc/article-9379473/starling Starling]

*Flickr
**[http://www.flickr.com/photos/tags/citheronia/ Tag for moth genera 'citheronia']
***[http://www.flickr.com/photos/30268343@N00/152101772/ Sample result from that search]
**[http://www.flickr.com/groups/birdguide/ Field Guide: Birds of the World] 23,073 tagged photos, as at 2006-10-21

*CNN
**[http://archives.cnn.com/2001/NATURE/01/24/dying.eagles/ Disease threatens bald eagle population]

*eBay
**[http://search.ebay.com/house-sparrow search for "House Sparrow"]

*The Guardian
**[http://environment.guardian.co.uk/conservation/story/0,,1878956,00.html The call of the wildlife]
**[http://education.guardian.co.uk/higher/news/story/0,,1665396,00.html Sparrow joins 'raped' duck in Dutch museum] (note improper capitalisation "''passer domesticus''")

*London Zoo
**[http://www.zsl.org/london-zoo/animals/birds/tawny-frogmouth,99,AN.html Tawny frogmouth]

*Microsoft
**[http://www.microsoft.com/games/zootycoon/zoo2/zoo2_ymi_animals1.asp Zoo Tycoon]

*MSN-Encarta - all species, e.g.
**[http://encarta.msn.com/encnet/refpages/search.aspx?q=vulgaris&Submit2=Go Search for "vulgaris"]

*MySpace
**[http://blog.myspace.com/index.cfm?fuseaction=blog.view&friendID=47134278&blogID=79591637]

*Nature
**[http://www.nature.com/nature/focus/avianflu/index.html Avian flu web focus]

*Nature Network, Boston
**[http://network.nature.com/boston/news/archive/2006/06/13/the-student-and-the-squid The student and the squid] '''N.B.''' site already supports rel-tag, hCard for user profiles and hCalendar for marking up events across the site.

*NASA
**[http://history.nasa.gov/SP-401/ch3.htm SP-401 Skylab, Classroom in Space. Part II - Student Experiments] ("The common Cross spider (Araneus diadematus)")

*New York Times
**[http://query.nytimes.com/gst/fullpage.html?sec=travel&res=9D04E4DE1131F93BA25751C0A9669C8B63 Where the Eagles Fly: Seeing the National Symbol]

*Snopes (Urban Legends Reference Pages)
**[http://www.snopes.com/photos/animals/fishfly.asp Fish Fly]

*United Kingdom Government
**[http://www.defra.gov.uk/wildlife-countryside/vertebrates/gen-licence.htm DEFRA: General licences under the Wildlife & Countryside Act 1981]

*United States of America Government
**ITIS, e.g. [http://www.itis.usda.gov/servlet/SingleRpt/SingleRpt?search_topic=TSN&search_value=179628 Passer Domesticus] - "authoritative taxonomic information on plants, animals, fungi, and microbes of North America and the world"

*W3C
**[http://dev.w3.org/cvsweb/2000/10/swap/test/ferrell/biology.n3?rev=1.4 An Ontology of Biology]
**[http://esw.w3.org/topic/HCLSIG_BioRDF_Subgroup/Tasks/Reagents/Status_Reports/2006-05-04 BioRDF Sub-group Status Report, 4 May 2006]

*Yahoo Groups
**[http://tech.groups.yahoo.com/group/passerdomesticus/ passerdomesticus] species as group name!

==Breaking news==
*[http://news.bbc.co.uk/1/shared/spl/hi/pop_ups/06/sci_nat_orchid_spectacular/html/1.stm BBC News: Stunning new orchids from Asia's rainforest] - 2006-10-16
*[http://news.bbc.co.uk/1/hi/sci/tech/6045802.stm BBC News: Winter home find cheers twitchers] (winter home of the northern bald ibis found) - 2006-10-13
*[http://news.bbc.co.uk/1/hi/sci/tech/6043648.stm BBC News: New mouse find is 'living fossil'] - 2006-10-12
*[http://news.bbc.co.uk/1/hi/sci/tech/6035113.stm BBC News: Giant camel fossil found in Syria] - 2006-10-10
*[http://news.bbc.co.uk/1/hi/sci/tech/5414410.stm BBC News: Sharks swim into political waters] - 2006-10-06
*[http://news.bbc.co.uk/1/hi/sci/tech/5403570.stm BBC News: 'Monster' fossil find in Arctic] - 2006-10-05

==Use in blogs==
*[http://technorati.com/search/%22passer%20domesticus%22 Technorati search for "Passer domesticus"] (367 found, as at 2006-09-25)
*[http://technorati.com/search/%22acer%20palmatum%22 Technorati search for "Acer palmatum"] (682 found, as at 2006-09-25)
*[http://technorati.com/search/%22Homo%20sapiens%22 Technorati search for "Homo sapiens"] (40,932 found, as at 2006-09-25)
*[http://technorati.com/search/birding Technorati search for "birding"] (26,472 found, as at 2006-09-25)
*[http://ramblingsofanaturalist.blogspot.com/ Ramblings of a Naturalist]
*[http://squaremetre1.blogspot.com/ The Square Metre]
*[http://windowboxwildlife.blogspot.com/index.html Windowbox Wildlife]
*[http://www.rxwildlife.org.uk/ RXWildlife]

==And finally...==
Gary Larson, in his book ''The Far Side Gallery'' (Warner Books, 1980, ISBN 0751502367) has a cartoon, showing two entomologists sitting down to eat dinner in a jungle. One says to the other "Hey! What's this ''Drosophila melanogaster'' doing in my soup?"

----
== Grouped By Publisher ==

=== West Midland Bird Club ===
* [http://www.westmidlandbirdclub.com/ladywalk/latest.htm Black-tailed Godwit]
<pre><nowiki>Black-tailed Godwit</nowiki></pre>

* [http://www.westmidlandbirdclub.com/records/lists.htm Limosa limosa ]
<pre><nowiki><td>Limosa limosa</td></nowiki></pre>

=== species.mediawiki.org ===
[http://species.wikimedia.org/wiki/Charadrius_dubius species.mediawiki.org media bird ] .
<pre><nowiki>
<dd>Regnum: <a href="/wiki/Animalia" title="Animalia">Animalia</a> (Metazoa)
<dl>
<dd>Subregnum: <a href="/wiki/Eumetazoa" title="Eumetazoa">Eumetazoa</a>
<dl>
<dd>Superphylum: Bilateria: <a href="/wiki/Deuterostomia" title="Deuterostomia">Deuterostomia</a>
<dl>
<dd>Phylum: <a href="/wiki/Chordata" title="Chordata">Chordata</a>
<dl>

<dd>Subphylum: <a href="/wiki/Vertebrata" title="Vertebrata">Vertebrata</a>
<dl>
<dd>Classis: <a href="/wiki/Aves" title="Aves">Aves</a>
<dl>
<dd>Subclassis: <a href="/wiki/Neognathae" title="Neognathae">Neognathae</a>
<dl>
<dd>Ordo: <a href="/wiki/Charadriiformes" title="Charadriiformes">Charadriiformes</a>
<dl>
<dd>Subordo: <a href="/wiki/Charadrii" title="Charadrii">Charadrii</a>

<dl>
<dd>Familia: <a href="/wiki/Charadriidae" title="Charadriidae">Charadriidae</a>
<dl>
<dd>Subfamily: <a href="/wiki/Charadriinae" title="Charadriinae">Charadriinae</a>
<dl>
<dd>Genus: <a href="/wiki/Charadrius" title="Charadrius">Charadrius</a>
<dl>
<dd>Species: Charadrius dubius
<dl>

<dd>Subspecies: <a href="/w/index.php?title=Charadrius_dubius_curonicus&action=edit" class="new" title="Charadrius dubius curonicus">C. d. curonicus</a> - <a href="/w/index.php?title=Charadrius_dubius_dubius&action=edit" class="new" title="Charadrius dubius dubius">C. d. dubius</a> - <a href="/w/index.php?title=Charadrius_dubius_jerdoni&action=edit" class="new" title="Charadrius dubius jerdoni">C. d. jerdoni</a> - <a href="/w/index.php?title=Charadrius_dubius_papuanus&action=edit" class="new" title="Charadrius dubius papuanus">C. d. papuanus</a></dd>

...
</nowiki>
</pre>

* Comments
** This feels similar to tagging to me. This particular example has a resolves the whole heirarchy, correct? [[User:BenWest|BenWest]] 17:57, 21 Oct 2006 (PDT)

== Alternative Grouping By Strategy ==
I'd like to regroup these examples... perhaps by publishing strategy instead of a list of what is being published. Should this be available as an alternate grouping section? In the mean time, a grouping by publisher would help analysis go smoother. [[User:BenWest|BenWest]] 17:57, 21 Oct 2006 (PDT)

I looked at several examples. Several of them feel like tagging to me. Should we attempt to note what level or resolution is available in each example?

=== Tagging ===
The [[http://species.wikimedia.org/wiki/Charadrius_dubius wiki media bird example]] is particularly interesting.
<pre><nowiki>
<dd>Regnum: <a href="/wiki/Animalia" title="Animalia">Animalia</a> (Metazoa)
<dl>
<dd>Subregnum: <a href="/wiki/Eumetazoa" title="Eumetazoa">Eumetazoa</a>
<dl>
<dd>Superphylum: Bilateria: <a href="/wiki/Deuterostomia" title="Deuterostomia">Deuterostomia</a>
<dl>
<dd>Phylum: <a href="/wiki/Chordata" title="Chordata">Chordata</a>
<dl>

<dd>Subphylum: <a href="/wiki/Vertebrata" title="Vertebrata">Vertebrata</a>
<dl>
<dd>Classis: <a href="/wiki/Aves" title="Aves">Aves</a>
<dl>
<dd>Subclassis: <a href="/wiki/Neognathae" title="Neognathae">Neognathae</a>
<dl>
<dd>Ordo: <a href="/wiki/Charadriiformes" title="Charadriiformes">Charadriiformes</a>
<dl>
<dd>Subordo: <a href="/wiki/Charadrii" title="Charadrii">Charadrii</a>

<dl>
<dd>Familia: <a href="/wiki/Charadriidae" title="Charadriidae">Charadriidae</a>
<dl>
<dd>Subfamily: <a href="/wiki/Charadriinae" title="Charadriinae">Charadriinae</a>
<dl>
<dd>Genus: <a href="/wiki/Charadrius" title="Charadrius">Charadrius</a>
<dl>
<dd>Species: Charadrius dubius
<dl>

<dd>Subspecies: <a href="/w/index.php?title=Charadrius_dubius_curonicus&action=edit" class="new" title="Charadrius dubius curonicus">C. d. curonicus</a> - <a href="/w/index.php?title=Charadrius_dubius_dubius&action=edit" class="new" title="Charadrius dubius dubius">C. d. dubius</a> - <a href="/w/index.php?title=Charadrius_dubius_jerdoni&action=edit" class="new" title="Charadrius dubius jerdoni">C. d. jerdoni</a> - <a href="/w/index.php?title=Charadrius_dubius_papuanus&action=edit" class="new" title="Charadrius dubius papuanus">C. d. papuanus</a></dd>

...
</nowiki>
</pre>
This feels similar to tagging to me. This particular example has a resolves the whole heirarchy, correct? [[User:BenWest|BenWest]] 17:57, 21 Oct 2006 (PDT)

----

==Contributors==
*[[User:AndyMabbett|Andy Mabbett]] (proponent)
*Malcolm Storey (per e-mail)
*[[User:SXBRC|Charles Roper]], [http://www.sxbrc.org.uk/ Sussex Biodiversity Record Centre] (proponent)
*[[User:SteveMcBill|Steve McWilliam]], [http://www.rECOrd-LRC.co.uk/ rECOrd - The Biodiversity Information System for the Cheshire region] (proponent)

==See also==
[[species-brainstorming]]

species-examples

2006-10-22T04:56:43Z

BenWest: /* Arachnid */ added a note that this is a duplicate already listed.

=Species Examples=

Examples of common and scientific names of living things, which could be marked up with a "'''[[species]]'''" (or similar) microformat. Note use of matching pairs of examples, where possible.

__TOC__

== Grouped By Publisher ==

=== West Midland Bird Club ===
* [http://www.westmidlandbirdclub.com/ladywalk/latest.htm Black-tailed Godwit]
<pre><nowiki>Black-tailed Godwit</nowiki></pre>

* [http://www.westmidlandbirdclub.com/records/lists.htm Limosa limosa ]
<pre><nowiki><td>Limosa limosa</td></nowiki></pre>

=== species.mediawiki.org ===
[http://species.wikimedia.org/wiki/Charadrius_dubius species.mediawiki.org media bird ] .
<pre><nowiki>
<dd>Regnum: <a href="/wiki/Animalia" title="Animalia">Animalia</a> (Metazoa)
<dl>
<dd>Subregnum: <a href="/wiki/Eumetazoa" title="Eumetazoa">Eumetazoa</a>
<dl>
<dd>Superphylum: Bilateria: <a href="/wiki/Deuterostomia" title="Deuterostomia">Deuterostomia</a>
<dl>
<dd>Phylum: <a href="/wiki/Chordata" title="Chordata">Chordata</a>
<dl>

<dd>Subphylum: <a href="/wiki/Vertebrata" title="Vertebrata">Vertebrata</a>
<dl>
<dd>Classis: <a href="/wiki/Aves" title="Aves">Aves</a>
<dl>
<dd>Subclassis: <a href="/wiki/Neognathae" title="Neognathae">Neognathae</a>
<dl>
<dd>Ordo: <a href="/wiki/Charadriiformes" title="Charadriiformes">Charadriiformes</a>
<dl>
<dd>Subordo: <a href="/wiki/Charadrii" title="Charadrii">Charadrii</a>

<dl>
<dd>Familia: <a href="/wiki/Charadriidae" title="Charadriidae">Charadriidae</a>
<dl>
<dd>Subfamily: <a href="/wiki/Charadriinae" title="Charadriinae">Charadriinae</a>
<dl>
<dd>Genus: <a href="/wiki/Charadrius" title="Charadrius">Charadrius</a>
<dl>
<dd>Species: Charadrius dubius
<dl>

<dd>Subspecies: <a href="/w/index.php?title=Charadrius_dubius_curonicus&action=edit" class="new" title="Charadrius dubius curonicus">C. d. curonicus</a> - <a href="/w/index.php?title=Charadrius_dubius_dubius&action=edit" class="new" title="Charadrius dubius dubius">C. d. dubius</a> - <a href="/w/index.php?title=Charadrius_dubius_jerdoni&action=edit" class="new" title="Charadrius dubius jerdoni">C. d. jerdoni</a> - <a href="/w/index.php?title=Charadrius_dubius_papuanus&action=edit" class="new" title="Charadrius dubius papuanus">C. d. papuanus</a></dd>

...
</nowiki>
</pre>

* Comments
** This feels similar to tagging to me. This particular example has a resolves the whole heirarchy, correct? [[User:BenWest|BenWest]] 17:57, 21 Oct 2006 (PDT)

== Alternative Grouping By Strategy ==
I'd like to regroup these examples... perhaps by publishing strategy instead of a list of what is being published. Should this be available as an alternate grouping section? In the mean time, a grouping by publisher would help analysis go smoother. [[User:BenWest|BenWest]] 17:57, 21 Oct 2006 (PDT)

I looked at several examples. Several of them feel like tagging to me. Should we attempt to note what level or resolution is available in each example?

=== Tagging ===
The [[http://species.wikimedia.org/wiki/Charadrius_dubius wiki media bird example]] is particularly interesting.
<pre><nowiki>
<dd>Regnum: <a href="/wiki/Animalia" title="Animalia">Animalia</a> (Metazoa)
<dl>
<dd>Subregnum: <a href="/wiki/Eumetazoa" title="Eumetazoa">Eumetazoa</a>
<dl>
<dd>Superphylum: Bilateria: <a href="/wiki/Deuterostomia" title="Deuterostomia">Deuterostomia</a>
<dl>
<dd>Phylum: <a href="/wiki/Chordata" title="Chordata">Chordata</a>
<dl>

<dd>Subphylum: <a href="/wiki/Vertebrata" title="Vertebrata">Vertebrata</a>
<dl>
<dd>Classis: <a href="/wiki/Aves" title="Aves">Aves</a>
<dl>
<dd>Subclassis: <a href="/wiki/Neognathae" title="Neognathae">Neognathae</a>
<dl>
<dd>Ordo: <a href="/wiki/Charadriiformes" title="Charadriiformes">Charadriiformes</a>
<dl>
<dd>Subordo: <a href="/wiki/Charadrii" title="Charadrii">Charadrii</a>

<dl>
<dd>Familia: <a href="/wiki/Charadriidae" title="Charadriidae">Charadriidae</a>
<dl>
<dd>Subfamily: <a href="/wiki/Charadriinae" title="Charadriinae">Charadriinae</a>
<dl>
<dd>Genus: <a href="/wiki/Charadrius" title="Charadrius">Charadrius</a>
<dl>
<dd>Species: Charadrius dubius
<dl>

<dd>Subspecies: <a href="/w/index.php?title=Charadrius_dubius_curonicus&action=edit" class="new" title="Charadrius dubius curonicus">C. d. curonicus</a> - <a href="/w/index.php?title=Charadrius_dubius_dubius&action=edit" class="new" title="Charadrius dubius dubius">C. d. dubius</a> - <a href="/w/index.php?title=Charadrius_dubius_jerdoni&action=edit" class="new" title="Charadrius dubius jerdoni">C. d. jerdoni</a> - <a href="/w/index.php?title=Charadrius_dubius_papuanus&action=edit" class="new" title="Charadrius dubius papuanus">C. d. papuanus</a></dd>

...
</nowiki>
</pre>
This feels similar to tagging to me. This particular example has a resolves the whole heirarchy, correct? [[User:BenWest|BenWest]] 17:57, 21 Oct 2006 (PDT)

==binominals==

===Birds===

'''Black-tailed Godwit''' on [http://www.westmidlandbirdclub.com/ladywalk/latest.htm West Midland Bird Club's Ladywalk reserve latest news page]

<pre><nowiki>Black-tailed Godwit</nowiki></pre>

'''''Limosa limosa''''' on [http://www.westmidlandbirdclub.com/records/lists.htm West Midland Bird Club's county lists']

<pre><nowiki><td>Limosa limosa</td></nowiki></pre>

===Mammal===
'''Wolf''' on [http://www.wolf.org/wolves/index.asp International Wolf Center]

===Fish===
'''Northern pike''' on [http://www.dnr.state.mn.us/fish/northern/index.html Minnesota Department of Natural Resources]

'''''Esox lucius''''' on [http://www.pikezander.co.uk/pike.htm Pike & Zander]

===Insect===
'''Death’s Head Hawkmoth''' on [http://funkman.org/animal/insect/deathheadmoth.html Animal Teachers]

'''''Acherontia atropos''''' on [http://ukmoths.org.uk/show.php?id=2540 UK Moths]

'''Migrant Hawker''' (''Aeshna mixta'') on [http://www.sxbrc.org.uk/news/friston-forest-recording-day Sussex Biodiversity Record Centre]

===Arachnid===
'''''Araneus angulatus''''' on [http://www.sxbrc.org.uk/news/friston-forest-recording-day Sussex Biodiversity Record Centre] (this is a duplicate. [[User:BenWest|BenWest]] 21:56, 21 Oct 2006 (PDT))

===Plant===
'''Bog Pimpernel''' on [http://www.map-reading.co.uk/wildflowers/HTML%20files/f0219.htm Map Reading's Wildflower Images]

'''''Anagallis tenella''''' on [http://www.bioimages.org.uk/HTML/T47624.HTM BioImages]

'''''Persicaria campanulatum''''' on [http://www.record-lrc.co.uk/?Mod=Forum&Do=ViewThread&ForumID=6&ThreadID=75 rECOrd - The Biodiversity Information Centre for the Cheshire region]

===Fungi===

'''''Amanita muscaria''''' on [http://www.mykoweb.com/CAF/species/Amanita_muscaria.html California Fungi]
* as '''''Amanita muscaria'' (L. per Fr.) Hooker'''
* as '''''Amanita muscaria var. flavivolvata'''''

'''Fly Agaric''' on [http://www.treesforlife.org.uk/forest/mythfolk/flyagaric.html Trees for Life]

'''''Rhodocollybia maculata'' (Albertini & Schweinitz: Fries) Singer''' on [http://www.ilmyco.gen.chicago.il.us/Taxa/Rhodomacul540.html]
*also written as '''''Rhodocollybia maculata'' (Albertini & Schweinitz ex Fries) Singer'''
*(This is where a post-Linnean author is given special rights (because his descriptions were comparatively complete - i.e. recognisable) so his interpretation of earlier names is taken as the sense meant by the original author. Think these used to be "apud" and are now "ex" although a colon has also been used. There are only a few sanctioning authors, the main one being Elias Fries.(Fr.) )

==More than binominals==

===Authority===
'''''Pica pica'' Linnaeus, (1758)''' on [http://en.wikipedia.org/wiki/European_Magpie Wikipedia: European Magpie]
:(i.e. named by Linnaeus in 1758)

===Unspecified species===
'''''Podiceps sp.''''' on [http://www.birdlife.org/datazone/species/index.html?action=SpcHTMDetails.asp&sid=3644&m=0 Bird Life] <pre><nowiki>Podiceps sp.</nowiki></pre>

'''Psyllid plant hopper''' [http://ramblingsofanaturalist.blogspot.com/2006/07/bay-sucker-gall-trioza-alacris.html on Ramblings of a Naturalist blog]

===Sub-species===

====Animal====
'''''Larus glaucoides kumlieni''' on [http://www.birdguides.com/html/vidlib/species/Larus_glaucoides_kumlieni.htm BirdGuides]

'''Kumlien's Gull''' on [http://www.birdsireland.com/pages/rare_bird_news/2005/january_photos.html Birds Ireland]

====Plant====
'''''Pisum sativum L. subsp. sativum''''' on [http://www.plantnames.unimelb.edu.au/Sorting/Pisum.html] (also has other examples; note lack of required italics)
<pre><nowiki>Pisum sativum L. subsp. sativum</nowiki></pre>

===Cultivars (plant)===
'''''Chamaecyparis lawsoniana 'Aureomarginata'''''' on [http://en.wikipedia.org/wiki/Cultivar Wikipedia: Cultivar]

<pre><nowiki><dd>Chamaecyparis lawsoniana 'Aureomarginata'</dd></nowiki></pre>

'''''Chamaecyparis lawsoniana'' 'Golden Wonder'''' on [http://www.plantago.nl/plantindex/c/Chamaecyparis/Chamaecyparis_4.htm plantago.nl]

====Cultivar groups (plant)====
'''''Brassica oleracea'' Botrytis Group''' on [http://en.wikipedia.org/wiki/Cultivar Wikipedia: Cultivar]

===Trade names (plant)===

'''''Rosa'' Peace''' on [http://en.wikipedia.org/wiki/Cultivar Wikipedia: Cultivar]
:("Peace" is a trade designation or "selling name" for the cultivar R. 'Madame A. Meilland' and should therefore be printed in a different typeface from the rest of the name, without any quote marks)

'''Sunflower 'Giant Single'''' on [http://cgi.www.johnsons-seeds.com/cgi-bin/www.johnsons-seeds.com/detail/azlist/S-1 Johnsons Seeds]

'''Sunflower 'Infrared' F1''' on [http://cgi.www.johnsons-seeds.com/cgi-bin/www.johnsons-seeds.com/detail/azlist/S-1 Johnsons Seeds]
:(Note "F1" cross designation)

===Variety (plant)===
'''''Pisum sativum var. macrocarpon''''' on [http://davesgarden.com/pf/go/8/index.html Dave's Garden]

====Sub-variety (plant)====

'''''Betula ermani var. genuina subvar. brevidentata''''' on [http://www.nccpg.com/gloucestershire/wilson1.html National Council for the Conservation of Plants and Gardens, Gloucestershire Group] (plus many other examples)

===Form (plant)===

'''''Acanthocalycium spiniflorum f. klimpelianum''''' on [http://en.wikipedia.org/wiki/Form_%28botany%29 Wikipedia: form (botany)]
*aka '''''Acanthocalycium spiniflorum forma klimpelianum'''''

===Sense (plant)===
'''''Ranunculus aquatilis s.l.''''' and '''''R. aquatilis s.s'''''; on [http://www.westmidlandbirdclub.com/blithfield/plants20060815.htm Blithfield Reservoir: Survey of Flowering Plants...] (see also footnotes on that page)

===Cross (plant)===
'''''Digitalis x mertonensis''''' on [http://www.hortax.org.uk/gardenplantsnames.html Hortax]
:The hybrid name for all plants derived from the cross between '''D. purpurea''' and '''D. grandiflora'''. The "x" indicates the hybrid status.

'''''× Fatshedera lizei''''' on [http://oregonstate.edu/dept/ldplants/sci-names.htm Scientific Plant Names, Oregon State Univ., Landscape Plants]

===Strain (bacteria)===
'''''Escherichia coli O157:H7''''' on [http://www.cfsan.fda.gov/~mow/chap15.html FDA.gov]

'''''E.Coli''''' on [http://news.bbc.co.uk/1/hi/england/southern_counties/5346842.stm BBC news]

==Misc==
===Superseded names===
'''''Tringa bartramia''''' superseded by '''''Bartramia longicauda''''' on [http://www.westmidlandbirdclub.com/firsts/UPLSA.htm West Midland Bird Club's Upland Sandpiper article]

===GUID===
'''NBN Taxon Key''' for European Otter, ''Lutra lutra'', on [http://nbn.nhm.ac.uk/nhm/bin/nbntaxa.dll/taxon_details?taxon_key=NBNSYS0000005133 NBN Species Dictionary]: '''NBNSYS0000005133'''

'''LSID ([http://lsid.sourceforge.net/#whatislsid Life Science Indicator])''' for ''Popillia japonica'' on [http://names.ubio.org/browser/details2.php?names=on&authors=on&sci=on&vern=on&conceptID=&expand=&namebankID=3377001 uBio]: '''urn:lsid:ubio.org:namebank:3377001'''

===Wikipedia===
'''Black-tailed Godwit''' on [http://en.wikipedia.org/wiki/Black-tailed_Godwit Wikipedia: Black-tailed Godwit]

Wikipedia uses several sets of markup, e.g. (in-line styles and links, plus some other markup, removed, for clarity):

<pre><nowiki>The Black-tailed Godwit, Limosa limosa</nowiki></pre>

and:

<pre><nowiki>
<tr>
<td>Kingdom:</td>
<td>Animalia</td>
</tr>
<tr>
<td>Phylum:</td>
<td>Chordata</td>
</tr>
<tr>
<td>Class:</td>
<td>Aves</td>
</tr>
<tr>
<td>Order:</td>
<td>Charadriiformes</td>
</tr>
<tr>
<td>Family:</td>
<td>Scolopacidae</td>
</tr>
<tr>
<td>Genus:</td>
<td>Limosa</td>
</tr>
<tr>
<td>Species:</td>
<td>L. limosa</td>
</tr>

<tr>
<th>binominal name</th>
</tr>
<tr>
<td>Limosa limosa
<td>(Linnaeus, 1758)</td>
</tr>
</nowiki></pre>

==Quantitative evidence==

For evidence of quantitative, rather than qualitative, use of species' and other taxonomic names, see [http://microformats.org/discuss/mail/microformats-discuss/2006-September/005790.html] and [http://microformats.org/discuss/mail/microformats-discuss/2006-September/005791.html]. Furthermore:

*Wikipedia:
** '''All''' species articles, e.g. [http://en.wikipedia.org/wiki/Little_Ringed_Plover Little Ringed Plover] (see [[species-examples#Wikipedia|above]])
** '''All''' genera articles, e.g. [http://en.wikipedia.org/wiki/Plover Charadrius (Plover)]
** '''All''' higher classes, e.g. [http://en.wikipedia.org/wiki/Charadriidae Charadriidae]
** '''All''' regional lists, e.g. [http://en.wikipedia.org/wiki/List_of_British_birds:_non-passerines List of British birds]
** '''All''' dedicatees, e.g. [http://en.wikipedia.org/wiki/Alexander_Wilson Alexander Wilson]
** '''All''' authorities, e.g. [http://en.wikipedia.org/wiki/Giovanni_Antonio_Scopoli Giovanni Antonio Scopoli]
** '''All''' images of living things, e.g. [http://en.wikipedia.org/wiki/Image:Charadrius_dubius_4_%28Marek_Szczepanek%29.jpg Charadrius dubius 4 (Marek Szczepanek).jpg]
** Many reserves, lakes, and other places of interest, e.g. [http://en.wikipedia.org/wiki/Belvide Belvide]
** Many biological authors and illustrators, e.g. [http://en.wikipedia.org/wiki/John_Audubon John Audubon]; [http://en.wikipedia.org/wiki/Gilbert_White Gilbert White]
** Random articles on other topics, e.g. [http://en.wikipedia.org/wiki/Balancing_lake Balancing lake}]
** '''All the above, again''', for each alternative language e.g. [http://cy.wikipedia.org/wiki/Cwtiad_Torchog_Bach Welsh]; [http://fr.wikipedia.org/wiki/Petit_gravelot French]; [http://zh.wikipedia.org/wiki/%E9%87%91%E7%9C%B6%E9%B8%BB Chinese]

*Wikimedia Commons
** '''All''' species indexes, e.g. [http://commons.wikimedia.org/wiki/Charadrius_dubius Charadrius dubius]
** '''Each individual''' image, e.g. [http://commons.wikimedia.org/wiki/Image:Charadrius_dubius_1_%28Marek_Szczepanek%29.jpg Charadrius dubius 1 (Marek Szczepanek).jpg]
** '''Each family''' list [http://commons.wikimedia.org/wiki/Charadriidae Charadriidae]

*Wiktionary
** '''All''' species articles, e.g. [http://en.wiktionary.org/wiki/american_golden_plover American Golden Plover]
** '''All''' family articles, e.g. [http://en.wiktionary.org/wiki/plover Plover]
** '''Many of the above, in other langauges''' e.g. [http://en.wiktionary.org/wiki/aquila_reale Italian]; [http://en.wiktionary.org/wiki/%D0%B1%D0%B5%D1%80%D0%BA%D1%83%D1%82 Russian]

*Wikispecies
** '''Every''' speices, e.g. [http://species.wikimedia.org/wiki/Charadrius_dubius Charadrius dubius]
** '''Every''' genus, e.g. [http://species.wikimedia.org/wiki/Charadrius Charadrius]
** '''Every''' sub-family, e.g. [http://species.wikimedia.org/wiki/Charadriinae Charadriinae]
** '''Every''' family, e.g. [http://species.wikimedia.org/wiki/Charadriidae Charadriidae]
** and so on, for '''every other rank'''
** '''Every''' image (e.g. [http://species.wikimedia.org/wiki/Image:Charadrius_hiaticula_He.jpg Charadrius hiaticula He.jpg]

*Google
**[http://www.google.co.uk/search?hl=en&hs=dBU&client=firefox-a&rls=org.mozilla:en-US:official&sa=X&oi=spell&resnum=0&ct=result&cd=1&q=%22E+coli%22&spell=1 Google finds about '''37,600,000''' for "E coli"].
***[http://www.google.co.uk/search?hs=Apo&hl=en&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&q=%22Escherichia+coli%22&btnG=Search&meta= Google finds about '''19,500,000''' for "Escherichia coli"]
***[http://www.google.co.uk/search?hs=zqo&hl=en&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&q=%22Ecoli%22&btnG=Search&meta= Google finds about '''722,000''' for "Ecoli"].
**[http://www.google.co.uk/search?hs=vWC&hl=en&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&q=%22Homo+sapiens%22&btnG=Search&meta= Google finds about '''14,200,000''' for "Homo sapiens"]
***[http://www.google.co.uk/search?hs=vWC&hl=en&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&q=%22Homo+sapien%22+-sapiens&btnG=Search&meta= Google finds about '''273,000''' for the mis-spelling "Homo sapien" -sapiens.]
**[http://www.google.co.uk/search?q=%22%22Homo+erectus%22%22&start=0&ie=utf-8&oe=utf-8&client=firefox-a&rls=org.mozilla:en-US:official Google finds about '''1,260,000''' for ""Homo erectus"]
**[http://www.google.com/search?svnum=10&as_scoring=r&hl=en&edition=us&as_drrb=q&as_qdr=&as_mind=1&as_minm=9&as_maxd=1&as_maxm=10&q=%22Clostridium+difficile%22&ie=UTF-8&sa=N&tab=nw Google finds about '''1,380,000''' for "Clostridium difficile"].
**[http://www.google.com/search?hl=en&lr=&edition=us&q=%22Passer+domesticus%22&btnG=Search Google finds about '''841,000''' for "Passer domesticus"].
***[http://images.google.com/images?hl=en&lr=&edition=us&q=%22Passer%20domesticus%22&btnG=Search&sa=N&tab=wi Google images finds about '''3,140''' for "Passer domesticus"].
**[http://www.google.co.uk/search?hl=en&hs=oEU&client=firefox-a&rls=org.mozilla:en-US:official&sa=X&oi=spell&resnum=0&ct=result&cd=1&q=%22Acer+palmatum%22&spell=1 Google finds about '''602,000''' for "Acer palmatum"]
** At the time of writing, '''every single one''' of the first 20 [http://www.google.com/search?q=%22Noctule+bat%22 Google results for "Noctule Bat"] also includes the scientific name ''Nyctalus noctula''.

*[http://www.arkive.org/ ARKive] - '''2000''' species ("It is ARKive's current aim to compile audio-visual records, where such media exists, for the 15,000-plus species currently threatened with extinction, according to the World Conservation Union's (IUCN) Red List of Threatened Species.")

*[http://www.rhs.org.uk/rhsplantfinder/plantfinder.asp Royal Horticultural Society - RHS Plant Finder] - '''70,000''' plants

*[http://www.bacterio.net List of Prokaryotic Names (formerly List of Bacterial Names)] - 2,032 *files*; '''10,268''' published names (to 2006-09-07)

*[http://nbn.nhm.ac.uk/nhm/ UK National Biodiversity Network's Species Dictionary]

*[http://www.searchnbn.net/ UK National Biodiversity Network Gateway] - '''20 million+''' species records

*[http://www.sp2000.org/ Species 2000] - '''450,000 species'''

*[http://www.bioimages.org.uk/index.html BioImages - Virtual Fieldguide] - '''53,000''' images depicting 4,600 species (see [[species-brainstorming#Malcolm_Storey|Wiki comments from site owner]])

*[http://animaldiversity.ummz.umich.edu/ Animal Diversity Web] - "'''Thousands''' of species accounts ['''plus'''] descriptions of levels of organization above the species level, especially phyla, classes, and in some cases, orders and families. Hundreds of hyperlinked pages and images illustrate the traits and general biology of these groups"

* [http://www.ubio.org/index.php?pagename=home uBio]
**NameBank is a repository of '''millions''' of recorded biological names and facts that link those names together.
**ClassificationBank stores multiple classifications and taxonomic concepts that are the result of expert opinions. It extends the functionality of NameBank.

*[http://www.birdlife.org/datazone/species/ BirdLife International] - all birds of the world (~'''10,000''')

*[http://bugguide.net/ Bug Guide] - all insects, spiders, and allies, of the USA and Canada (most with more than one page).
** e.g. [http://bugguide.net/node/view/70875 Arge pectoralis - Birch Sawfly]

*[http://www.bto.org/birdtrack/ BirdTrack]
**[http://blx1.bto.org/bt-dailyresults/results/s171-20-06.html Lapwing]

*[http://www.discoverlife.org/ Discover Life] - "contains '''306,553''' species. The Polistes Foundation and its scientific partners plan to add high-quality identification guides, maps, images, and text for '''a million species''' by 2012. [...] Each month Discover Life serves approximately 3 million pages and images to 70,000 IP addresses"

*[http://www.record-lrc.co.uk/ rECOrd] (the Local Biological Records Centre serving the Cheshire region of England) - '''1.6 million''' species records available online for the public to search and map

===Planned sites===
*[http://herbariaunited.org/atHome/ Herbaria United] (part of The website of the Botanical Collection Managers Group (BCMG), a specialist group of the Linnean Society of London) - "The UK has the world's largest and oldest collections of herbarium specimens held in trust by museums and universities. A new project is just getting underway to put all this online."

==Notable websites==
These high-profile websites use species names

*Amazon
**[http://www.amazon.co.uk/s/?url=search-alias%3Daps&field-keywords=%22house+sparrow%22 search for "House Sparrow"]

*BBC News
**[http://news.bbc.co.uk/1/hi/uk/4835208.stm Fewer birds spotted in UK gardens]
**[http://news.bbc.co.uk/1/hi/england/london/4743250.stm Study to solve sparrow's decline riddle]

*Encyclopaedia Britannica - all species, e.g.
**[http://concise.britannica.com/ebc/article-9379473/starling Starling]

*Flickr
**[http://www.flickr.com/photos/tags/citheronia/ Tag for moth genera 'citheronia']
***[http://www.flickr.com/photos/30268343@N00/152101772/ Sample result from that search]
**[http://www.flickr.com/groups/birdguide/ Field Guide: Birds of the World] 23,073 tagged photos, as at 2006-10-21

*CNN
**[http://archives.cnn.com/2001/NATURE/01/24/dying.eagles/ Disease threatens bald eagle population]

*eBay
**[http://search.ebay.com/house-sparrow search for "House Sparrow"]

*The Guardian
**[http://environment.guardian.co.uk/conservation/story/0,,1878956,00.html The call of the wildlife]
**[http://education.guardian.co.uk/higher/news/story/0,,1665396,00.html Sparrow joins 'raped' duck in Dutch museum] (note improper capitalisation "''passer domesticus''")

*London Zoo
**[http://www.zsl.org/london-zoo/animals/birds/tawny-frogmouth,99,AN.html Tawny frogmouth]

*Microsoft
**[http://www.microsoft.com/games/zootycoon/zoo2/zoo2_ymi_animals1.asp Zoo Tycoon]

*MSN-Encarta - all species, e.g.
**[http://encarta.msn.com/encnet/refpages/search.aspx?q=vulgaris&Submit2=Go Search for "vulgaris"]

*MySpace
**[http://blog.myspace.com/index.cfm?fuseaction=blog.view&friendID=47134278&blogID=79591637]

*Nature
**[http://www.nature.com/nature/focus/avianflu/index.html Avian flu web focus]

*Nature Network, Boston
**[http://network.nature.com/boston/news/archive/2006/06/13/the-student-and-the-squid The student and the squid] '''N.B.''' site already supports rel-tag, hCard for user profiles and hCalendar for marking up events across the site.

*NASA
**[http://history.nasa.gov/SP-401/ch3.htm SP-401 Skylab, Classroom in Space. Part II - Student Experiments] ("The common Cross spider (Araneus diadematus)")

*New York Times
**[http://query.nytimes.com/gst/fullpage.html?sec=travel&res=9D04E4DE1131F93BA25751C0A9669C8B63 Where the Eagles Fly: Seeing the National Symbol]

*Snopes (Urban Legends Reference Pages)
**[http://www.snopes.com/photos/animals/fishfly.asp Fish Fly]

*United Kingdom Government
**[http://www.defra.gov.uk/wildlife-countryside/vertebrates/gen-licence.htm DEFRA: General licences under the Wildlife & Countryside Act 1981]

*United States of America Government
**ITIS, e.g. [http://www.itis.usda.gov/servlet/SingleRpt/SingleRpt?search_topic=TSN&search_value=179628 Passer Domesticus] - "authoritative taxonomic information on plants, animals, fungi, and microbes of North America and the world"

*W3C
**[http://dev.w3.org/cvsweb/2000/10/swap/test/ferrell/biology.n3?rev=1.4 An Ontology of Biology]
**[http://esw.w3.org/topic/HCLSIG_BioRDF_Subgroup/Tasks/Reagents/Status_Reports/2006-05-04 BioRDF Sub-group Status Report, 4 May 2006]

*Yahoo Groups
**[http://tech.groups.yahoo.com/group/passerdomesticus/ passerdomesticus] species as group name!

==Breaking news==
*[http://news.bbc.co.uk/1/shared/spl/hi/pop_ups/06/sci_nat_orchid_spectacular/html/1.stm BBC News: Stunning new orchids from Asia's rainforest] - 2006-10-16
*[http://news.bbc.co.uk/1/hi/sci/tech/6045802.stm BBC News: Winter home find cheers twitchers] (winter home of the northern bald ibis found) - 2006-10-13
*[http://news.bbc.co.uk/1/hi/sci/tech/6043648.stm BBC News: New mouse find is 'living fossil'] - 2006-10-12
*[http://news.bbc.co.uk/1/hi/sci/tech/6035113.stm BBC News: Giant camel fossil found in Syria] - 2006-10-10
*[http://news.bbc.co.uk/1/hi/sci/tech/5414410.stm BBC News: Sharks swim into political waters] - 2006-10-06
*[http://news.bbc.co.uk/1/hi/sci/tech/5403570.stm BBC News: 'Monster' fossil find in Arctic] - 2006-10-05

==Use in blogs==
*[http://technorati.com/search/%22passer%20domesticus%22 Technorati search for "Passer domesticus"] (367 found, as at 2006-09-25)
*[http://technorati.com/search/%22acer%20palmatum%22 Technorati search for "Acer palmatum"] (682 found, as at 2006-09-25)
*[http://technorati.com/search/%22Homo%20sapiens%22 Technorati search for "Homo sapiens"] (40,932 found, as at 2006-09-25)
*[http://technorati.com/search/birding Technorati search for "birding"] (26,472 found, as at 2006-09-25)
*[http://ramblingsofanaturalist.blogspot.com/ Ramblings of a Naturalist]
*[http://squaremetre1.blogspot.com/ The Square Metre]
*[http://windowboxwildlife.blogspot.com/index.html Windowbox Wildlife]
*[http://www.rxwildlife.org.uk/ RXWildlife]

==And finally...==
Gary Larson, in his book ''The Far Side Gallery'' (Warner Books, 1980, ISBN 0751502367) has a cartoon, showing two entomologists sitting down to eat dinner in a jungle. One says to the other "Hey! What's this ''Drosophila melanogaster'' doing in my soup?"

==Contributors==
*[[User:AndyMabbett|Andy Mabbett]] (proponent)
*Malcolm Storey (per e-mail)
*[[User:SXBRC|Charles Roper]], [http://www.sxbrc.org.uk/ Sussex Biodiversity Record Centre] (proponent)
*[[User:SteveMcBill|Steve McWilliam]], [http://www.rECOrd-LRC.co.uk/ rECOrd - The Biodiversity Information System for the Cheshire region] (proponent)

==See also==
[[species-brainstorming]]

species-examples

2006-10-22T04:55:31Z

BenWest: /* Arachnid */ removed duplicate link requiring premium subscription.

=Species Examples=

Examples of common and scientific names of living things, which could be marked up with a "'''[[species]]'''" (or similar) microformat. Note use of matching pairs of examples, where possible.

__TOC__

== Grouped By Publisher ==

=== West Midland Bird Club ===
* [http://www.westmidlandbirdclub.com/ladywalk/latest.htm Black-tailed Godwit]
<pre><nowiki>Black-tailed Godwit</nowiki></pre>

* [http://www.westmidlandbirdclub.com/records/lists.htm Limosa limosa ]
<pre><nowiki><td>Limosa limosa</td></nowiki></pre>

=== species.mediawiki.org ===
[http://species.wikimedia.org/wiki/Charadrius_dubius species.mediawiki.org media bird ] .
<pre><nowiki>
<dd>Regnum: <a href="/wiki/Animalia" title="Animalia">Animalia</a> (Metazoa)
<dl>
<dd>Subregnum: <a href="/wiki/Eumetazoa" title="Eumetazoa">Eumetazoa</a>
<dl>
<dd>Superphylum: Bilateria: <a href="/wiki/Deuterostomia" title="Deuterostomia">Deuterostomia</a>
<dl>
<dd>Phylum: <a href="/wiki/Chordata" title="Chordata">Chordata</a>
<dl>

<dd>Subphylum: <a href="/wiki/Vertebrata" title="Vertebrata">Vertebrata</a>
<dl>
<dd>Classis: <a href="/wiki/Aves" title="Aves">Aves</a>
<dl>
<dd>Subclassis: <a href="/wiki/Neognathae" title="Neognathae">Neognathae</a>
<dl>
<dd>Ordo: <a href="/wiki/Charadriiformes" title="Charadriiformes">Charadriiformes</a>
<dl>
<dd>Subordo: <a href="/wiki/Charadrii" title="Charadrii">Charadrii</a>

<dl>
<dd>Familia: <a href="/wiki/Charadriidae" title="Charadriidae">Charadriidae</a>
<dl>
<dd>Subfamily: <a href="/wiki/Charadriinae" title="Charadriinae">Charadriinae</a>
<dl>
<dd>Genus: <a href="/wiki/Charadrius" title="Charadrius">Charadrius</a>
<dl>
<dd>Species: Charadrius dubius
<dl>

<dd>Subspecies: <a href="/w/index.php?title=Charadrius_dubius_curonicus&action=edit" class="new" title="Charadrius dubius curonicus">C. d. curonicus</a> - <a href="/w/index.php?title=Charadrius_dubius_dubius&action=edit" class="new" title="Charadrius dubius dubius">C. d. dubius</a> - <a href="/w/index.php?title=Charadrius_dubius_jerdoni&action=edit" class="new" title="Charadrius dubius jerdoni">C. d. jerdoni</a> - <a href="/w/index.php?title=Charadrius_dubius_papuanus&action=edit" class="new" title="Charadrius dubius papuanus">C. d. papuanus</a></dd>

...
</nowiki>
</pre>

* Comments
** This feels similar to tagging to me. This particular example has a resolves the whole heirarchy, correct? [[User:BenWest|BenWest]] 17:57, 21 Oct 2006 (PDT)

== Alternative Grouping By Strategy ==
I'd like to regroup these examples... perhaps by publishing strategy instead of a list of what is being published. Should this be available as an alternate grouping section? In the mean time, a grouping by publisher would help analysis go smoother. [[User:BenWest|BenWest]] 17:57, 21 Oct 2006 (PDT)

I looked at several examples. Several of them feel like tagging to me. Should we attempt to note what level or resolution is available in each example?

=== Tagging ===
The [[http://species.wikimedia.org/wiki/Charadrius_dubius wiki media bird example]] is particularly interesting.
<pre><nowiki>
<dd>Regnum: <a href="/wiki/Animalia" title="Animalia">Animalia</a> (Metazoa)
<dl>
<dd>Subregnum: <a href="/wiki/Eumetazoa" title="Eumetazoa">Eumetazoa</a>
<dl>
<dd>Superphylum: Bilateria: <a href="/wiki/Deuterostomia" title="Deuterostomia">Deuterostomia</a>
<dl>
<dd>Phylum: <a href="/wiki/Chordata" title="Chordata">Chordata</a>
<dl>

<dd>Subphylum: <a href="/wiki/Vertebrata" title="Vertebrata">Vertebrata</a>
<dl>
<dd>Classis: <a href="/wiki/Aves" title="Aves">Aves</a>
<dl>
<dd>Subclassis: <a href="/wiki/Neognathae" title="Neognathae">Neognathae</a>
<dl>
<dd>Ordo: <a href="/wiki/Charadriiformes" title="Charadriiformes">Charadriiformes</a>
<dl>
<dd>Subordo: <a href="/wiki/Charadrii" title="Charadrii">Charadrii</a>

<dl>
<dd>Familia: <a href="/wiki/Charadriidae" title="Charadriidae">Charadriidae</a>
<dl>
<dd>Subfamily: <a href="/wiki/Charadriinae" title="Charadriinae">Charadriinae</a>
<dl>
<dd>Genus: <a href="/wiki/Charadrius" title="Charadrius">Charadrius</a>
<dl>
<dd>Species: Charadrius dubius
<dl>

<dd>Subspecies: <a href="/w/index.php?title=Charadrius_dubius_curonicus&action=edit" class="new" title="Charadrius dubius curonicus">C. d. curonicus</a> - <a href="/w/index.php?title=Charadrius_dubius_dubius&action=edit" class="new" title="Charadrius dubius dubius">C. d. dubius</a> - <a href="/w/index.php?title=Charadrius_dubius_jerdoni&action=edit" class="new" title="Charadrius dubius jerdoni">C. d. jerdoni</a> - <a href="/w/index.php?title=Charadrius_dubius_papuanus&action=edit" class="new" title="Charadrius dubius papuanus">C. d. papuanus</a></dd>

...
</nowiki>
</pre>
This feels similar to tagging to me. This particular example has a resolves the whole heirarchy, correct? [[User:BenWest|BenWest]] 17:57, 21 Oct 2006 (PDT)

==binominals==

===Birds===

'''Black-tailed Godwit''' on [http://www.westmidlandbirdclub.com/ladywalk/latest.htm West Midland Bird Club's Ladywalk reserve latest news page]

<pre><nowiki>Black-tailed Godwit</nowiki></pre>

'''''Limosa limosa''''' on [http://www.westmidlandbirdclub.com/records/lists.htm West Midland Bird Club's county lists']

<pre><nowiki><td>Limosa limosa</td></nowiki></pre>

===Mammal===
'''Wolf''' on [http://www.wolf.org/wolves/index.asp International Wolf Center]

===Fish===
'''Northern pike''' on [http://www.dnr.state.mn.us/fish/northern/index.html Minnesota Department of Natural Resources]

'''''Esox lucius''''' on [http://www.pikezander.co.uk/pike.htm Pike & Zander]

===Insect===
'''Death’s Head Hawkmoth''' on [http://funkman.org/animal/insect/deathheadmoth.html Animal Teachers]

'''''Acherontia atropos''''' on [http://ukmoths.org.uk/show.php?id=2540 UK Moths]

'''Migrant Hawker''' (''Aeshna mixta'') on [http://www.sxbrc.org.uk/news/friston-forest-recording-day Sussex Biodiversity Record Centre]

===Arachnid===
'''''Araneus angulatus''''' on [http://www.sxbrc.org.uk/news/friston-forest-recording-day Sussex Biodiversity Record Centre]

===Plant===
'''Bog Pimpernel''' on [http://www.map-reading.co.uk/wildflowers/HTML%20files/f0219.htm Map Reading's Wildflower Images]

'''''Anagallis tenella''''' on [http://www.bioimages.org.uk/HTML/T47624.HTM BioImages]

'''''Persicaria campanulatum''''' on [http://www.record-lrc.co.uk/?Mod=Forum&Do=ViewThread&ForumID=6&ThreadID=75 rECOrd - The Biodiversity Information Centre for the Cheshire region]

===Fungi===

'''''Amanita muscaria''''' on [http://www.mykoweb.com/CAF/species/Amanita_muscaria.html California Fungi]
* as '''''Amanita muscaria'' (L. per Fr.) Hooker'''
* as '''''Amanita muscaria var. flavivolvata'''''

'''Fly Agaric''' on [http://www.treesforlife.org.uk/forest/mythfolk/flyagaric.html Trees for Life]

'''''Rhodocollybia maculata'' (Albertini & Schweinitz: Fries) Singer''' on [http://www.ilmyco.gen.chicago.il.us/Taxa/Rhodomacul540.html]
*also written as '''''Rhodocollybia maculata'' (Albertini & Schweinitz ex Fries) Singer'''
*(This is where a post-Linnean author is given special rights (because his descriptions were comparatively complete - i.e. recognisable) so his interpretation of earlier names is taken as the sense meant by the original author. Think these used to be "apud" and are now "ex" although a colon has also been used. There are only a few sanctioning authors, the main one being Elias Fries.(Fr.) )

==More than binominals==

===Authority===
'''''Pica pica'' Linnaeus, (1758)''' on [http://en.wikipedia.org/wiki/European_Magpie Wikipedia: European Magpie]
:(i.e. named by Linnaeus in 1758)

===Unspecified species===
'''''Podiceps sp.''''' on [http://www.birdlife.org/datazone/species/index.html?action=SpcHTMDetails.asp&sid=3644&m=0 Bird Life] <pre><nowiki>Podiceps sp.</nowiki></pre>

'''Psyllid plant hopper''' [http://ramblingsofanaturalist.blogspot.com/2006/07/bay-sucker-gall-trioza-alacris.html on Ramblings of a Naturalist blog]

===Sub-species===

====Animal====
'''''Larus glaucoides kumlieni''' on [http://www.birdguides.com/html/vidlib/species/Larus_glaucoides_kumlieni.htm BirdGuides]

'''Kumlien's Gull''' on [http://www.birdsireland.com/pages/rare_bird_news/2005/january_photos.html Birds Ireland]

====Plant====
'''''Pisum sativum L. subsp. sativum''''' on [http://www.plantnames.unimelb.edu.au/Sorting/Pisum.html] (also has other examples; note lack of required italics)
<pre><nowiki>Pisum sativum L. subsp. sativum</nowiki></pre>

===Cultivars (plant)===
'''''Chamaecyparis lawsoniana 'Aureomarginata'''''' on [http://en.wikipedia.org/wiki/Cultivar Wikipedia: Cultivar]

<pre><nowiki><dd>Chamaecyparis lawsoniana 'Aureomarginata'</dd></nowiki></pre>

'''''Chamaecyparis lawsoniana'' 'Golden Wonder'''' on [http://www.plantago.nl/plantindex/c/Chamaecyparis/Chamaecyparis_4.htm plantago.nl]

====Cultivar groups (plant)====
'''''Brassica oleracea'' Botrytis Group''' on [http://en.wikipedia.org/wiki/Cultivar Wikipedia: Cultivar]

===Trade names (plant)===

'''''Rosa'' Peace''' on [http://en.wikipedia.org/wiki/Cultivar Wikipedia: Cultivar]
:("Peace" is a trade designation or "selling name" for the cultivar R. 'Madame A. Meilland' and should therefore be printed in a different typeface from the rest of the name, without any quote marks)

'''Sunflower 'Giant Single'''' on [http://cgi.www.johnsons-seeds.com/cgi-bin/www.johnsons-seeds.com/detail/azlist/S-1 Johnsons Seeds]

'''Sunflower 'Infrared' F1''' on [http://cgi.www.johnsons-seeds.com/cgi-bin/www.johnsons-seeds.com/detail/azlist/S-1 Johnsons Seeds]
:(Note "F1" cross designation)

===Variety (plant)===
'''''Pisum sativum var. macrocarpon''''' on [http://davesgarden.com/pf/go/8/index.html Dave's Garden]

====Sub-variety (plant)====

'''''Betula ermani var. genuina subvar. brevidentata''''' on [http://www.nccpg.com/gloucestershire/wilson1.html National Council for the Conservation of Plants and Gardens, Gloucestershire Group] (plus many other examples)

===Form (plant)===

'''''Acanthocalycium spiniflorum f. klimpelianum''''' on [http://en.wikipedia.org/wiki/Form_%28botany%29 Wikipedia: form (botany)]
*aka '''''Acanthocalycium spiniflorum forma klimpelianum'''''

===Sense (plant)===
'''''Ranunculus aquatilis s.l.''''' and '''''R. aquatilis s.s'''''; on [http://www.westmidlandbirdclub.com/blithfield/plants20060815.htm Blithfield Reservoir: Survey of Flowering Plants...] (see also footnotes on that page)

===Cross (plant)===
'''''Digitalis x mertonensis''''' on [http://www.hortax.org.uk/gardenplantsnames.html Hortax]
:The hybrid name for all plants derived from the cross between '''D. purpurea''' and '''D. grandiflora'''. The "x" indicates the hybrid status.

'''''× Fatshedera lizei''''' on [http://oregonstate.edu/dept/ldplants/sci-names.htm Scientific Plant Names, Oregon State Univ., Landscape Plants]

===Strain (bacteria)===
'''''Escherichia coli O157:H7''''' on [http://www.cfsan.fda.gov/~mow/chap15.html FDA.gov]

'''''E.Coli''''' on [http://news.bbc.co.uk/1/hi/england/southern_counties/5346842.stm BBC news]

==Misc==
===Superseded names===
'''''Tringa bartramia''''' superseded by '''''Bartramia longicauda''''' on [http://www.westmidlandbirdclub.com/firsts/UPLSA.htm West Midland Bird Club's Upland Sandpiper article]

===GUID===
'''NBN Taxon Key''' for European Otter, ''Lutra lutra'', on [http://nbn.nhm.ac.uk/nhm/bin/nbntaxa.dll/taxon_details?taxon_key=NBNSYS0000005133 NBN Species Dictionary]: '''NBNSYS0000005133'''

'''LSID ([http://lsid.sourceforge.net/#whatislsid Life Science Indicator])''' for ''Popillia japonica'' on [http://names.ubio.org/browser/details2.php?names=on&authors=on&sci=on&vern=on&conceptID=&expand=&namebankID=3377001 uBio]: '''urn:lsid:ubio.org:namebank:3377001'''

===Wikipedia===
'''Black-tailed Godwit''' on [http://en.wikipedia.org/wiki/Black-tailed_Godwit Wikipedia: Black-tailed Godwit]

Wikipedia uses several sets of markup, e.g. (in-line styles and links, plus some other markup, removed, for clarity):

<pre><nowiki>The Black-tailed Godwit, Limosa limosa</nowiki></pre>

and:

<pre><nowiki>
<tr>
<td>Kingdom:</td>
<td>Animalia</td>
</tr>
<tr>
<td>Phylum:</td>
<td>Chordata</td>
</tr>
<tr>
<td>Class:</td>
<td>Aves</td>
</tr>
<tr>
<td>Order:</td>
<td>Charadriiformes</td>
</tr>
<tr>
<td>Family:</td>
<td>Scolopacidae</td>
</tr>
<tr>
<td>Genus:</td>
<td>Limosa</td>
</tr>
<tr>
<td>Species:</td>
<td>L. limosa</td>
</tr>

<tr>
<th>binominal name</th>
</tr>
<tr>
<td>Limosa limosa
<td>(Linnaeus, 1758)</td>
</tr>
</nowiki></pre>

==Quantitative evidence==

For evidence of quantitative, rather than qualitative, use of species' and other taxonomic names, see [http://microformats.org/discuss/mail/microformats-discuss/2006-September/005790.html] and [http://microformats.org/discuss/mail/microformats-discuss/2006-September/005791.html]. Furthermore:

*Wikipedia:
** '''All''' species articles, e.g. [http://en.wikipedia.org/wiki/Little_Ringed_Plover Little Ringed Plover] (see [[species-examples#Wikipedia|above]])
** '''All''' genera articles, e.g. [http://en.wikipedia.org/wiki/Plover Charadrius (Plover)]
** '''All''' higher classes, e.g. [http://en.wikipedia.org/wiki/Charadriidae Charadriidae]
** '''All''' regional lists, e.g. [http://en.wikipedia.org/wiki/List_of_British_birds:_non-passerines List of British birds]
** '''All''' dedicatees, e.g. [http://en.wikipedia.org/wiki/Alexander_Wilson Alexander Wilson]
** '''All''' authorities, e.g. [http://en.wikipedia.org/wiki/Giovanni_Antonio_Scopoli Giovanni Antonio Scopoli]
** '''All''' images of living things, e.g. [http://en.wikipedia.org/wiki/Image:Charadrius_dubius_4_%28Marek_Szczepanek%29.jpg Charadrius dubius 4 (Marek Szczepanek).jpg]
** Many reserves, lakes, and other places of interest, e.g. [http://en.wikipedia.org/wiki/Belvide Belvide]
** Many biological authors and illustrators, e.g. [http://en.wikipedia.org/wiki/John_Audubon John Audubon]; [http://en.wikipedia.org/wiki/Gilbert_White Gilbert White]
** Random articles on other topics, e.g. [http://en.wikipedia.org/wiki/Balancing_lake Balancing lake}]
** '''All the above, again''', for each alternative language e.g. [http://cy.wikipedia.org/wiki/Cwtiad_Torchog_Bach Welsh]; [http://fr.wikipedia.org/wiki/Petit_gravelot French]; [http://zh.wikipedia.org/wiki/%E9%87%91%E7%9C%B6%E9%B8%BB Chinese]

*Wikimedia Commons
** '''All''' species indexes, e.g. [http://commons.wikimedia.org/wiki/Charadrius_dubius Charadrius dubius]
** '''Each individual''' image, e.g. [http://commons.wikimedia.org/wiki/Image:Charadrius_dubius_1_%28Marek_Szczepanek%29.jpg Charadrius dubius 1 (Marek Szczepanek).jpg]
** '''Each family''' list [http://commons.wikimedia.org/wiki/Charadriidae Charadriidae]

*Wiktionary
** '''All''' species articles, e.g. [http://en.wiktionary.org/wiki/american_golden_plover American Golden Plover]
** '''All''' family articles, e.g. [http://en.wiktionary.org/wiki/plover Plover]
** '''Many of the above, in other langauges''' e.g. [http://en.wiktionary.org/wiki/aquila_reale Italian]; [http://en.wiktionary.org/wiki/%D0%B1%D0%B5%D1%80%D0%BA%D1%83%D1%82 Russian]

*Wikispecies
** '''Every''' speices, e.g. [http://species.wikimedia.org/wiki/Charadrius_dubius Charadrius dubius]
** '''Every''' genus, e.g. [http://species.wikimedia.org/wiki/Charadrius Charadrius]
** '''Every''' sub-family, e.g. [http://species.wikimedia.org/wiki/Charadriinae Charadriinae]
** '''Every''' family, e.g. [http://species.wikimedia.org/wiki/Charadriidae Charadriidae]
** and so on, for '''every other rank'''
** '''Every''' image (e.g. [http://species.wikimedia.org/wiki/Image:Charadrius_hiaticula_He.jpg Charadrius hiaticula He.jpg]

*Google
**[http://www.google.co.uk/search?hl=en&hs=dBU&client=firefox-a&rls=org.mozilla:en-US:official&sa=X&oi=spell&resnum=0&ct=result&cd=1&q=%22E+coli%22&spell=1 Google finds about '''37,600,000''' for "E coli"].
***[http://www.google.co.uk/search?hs=Apo&hl=en&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&q=%22Escherichia+coli%22&btnG=Search&meta= Google finds about '''19,500,000''' for "Escherichia coli"]
***[http://www.google.co.uk/search?hs=zqo&hl=en&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&q=%22Ecoli%22&btnG=Search&meta= Google finds about '''722,000''' for "Ecoli"].
**[http://www.google.co.uk/search?hs=vWC&hl=en&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&q=%22Homo+sapiens%22&btnG=Search&meta= Google finds about '''14,200,000''' for "Homo sapiens"]
***[http://www.google.co.uk/search?hs=vWC&hl=en&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&q=%22Homo+sapien%22+-sapiens&btnG=Search&meta= Google finds about '''273,000''' for the mis-spelling "Homo sapien" -sapiens.]
**[http://www.google.co.uk/search?q=%22%22Homo+erectus%22%22&start=0&ie=utf-8&oe=utf-8&client=firefox-a&rls=org.mozilla:en-US:official Google finds about '''1,260,000''' for ""Homo erectus"]
**[http://www.google.com/search?svnum=10&as_scoring=r&hl=en&edition=us&as_drrb=q&as_qdr=&as_mind=1&as_minm=9&as_maxd=1&as_maxm=10&q=%22Clostridium+difficile%22&ie=UTF-8&sa=N&tab=nw Google finds about '''1,380,000''' for "Clostridium difficile"].
**[http://www.google.com/search?hl=en&lr=&edition=us&q=%22Passer+domesticus%22&btnG=Search Google finds about '''841,000''' for "Passer domesticus"].
***[http://images.google.com/images?hl=en&lr=&edition=us&q=%22Passer%20domesticus%22&btnG=Search&sa=N&tab=wi Google images finds about '''3,140''' for "Passer domesticus"].
**[http://www.google.co.uk/search?hl=en&hs=oEU&client=firefox-a&rls=org.mozilla:en-US:official&sa=X&oi=spell&resnum=0&ct=result&cd=1&q=%22Acer+palmatum%22&spell=1 Google finds about '''602,000''' for "Acer palmatum"]
** At the time of writing, '''every single one''' of the first 20 [http://www.google.com/search?q=%22Noctule+bat%22 Google results for "Noctule Bat"] also includes the scientific name ''Nyctalus noctula''.

*[http://www.arkive.org/ ARKive] - '''2000''' species ("It is ARKive's current aim to compile audio-visual records, where such media exists, for the 15,000-plus species currently threatened with extinction, according to the World Conservation Union's (IUCN) Red List of Threatened Species.")

*[http://www.rhs.org.uk/rhsplantfinder/plantfinder.asp Royal Horticultural Society - RHS Plant Finder] - '''70,000''' plants

*[http://www.bacterio.net List of Prokaryotic Names (formerly List of Bacterial Names)] - 2,032 *files*; '''10,268''' published names (to 2006-09-07)

*[http://nbn.nhm.ac.uk/nhm/ UK National Biodiversity Network's Species Dictionary]

*[http://www.searchnbn.net/ UK National Biodiversity Network Gateway] - '''20 million+''' species records

*[http://www.sp2000.org/ Species 2000] - '''450,000 species'''

*[http://www.bioimages.org.uk/index.html BioImages - Virtual Fieldguide] - '''53,000''' images depicting 4,600 species (see [[species-brainstorming#Malcolm_Storey|Wiki comments from site owner]])

*[http://animaldiversity.ummz.umich.edu/ Animal Diversity Web] - "'''Thousands''' of species accounts ['''plus'''] descriptions of levels of organization above the species level, especially phyla, classes, and in some cases, orders and families. Hundreds of hyperlinked pages and images illustrate the traits and general biology of these groups"

* [http://www.ubio.org/index.php?pagename=home uBio]
**NameBank is a repository of '''millions''' of recorded biological names and facts that link those names together.
**ClassificationBank stores multiple classifications and taxonomic concepts that are the result of expert opinions. It extends the functionality of NameBank.

*[http://www.birdlife.org/datazone/species/ BirdLife International] - all birds of the world (~'''10,000''')

*[http://bugguide.net/ Bug Guide] - all insects, spiders, and allies, of the USA and Canada (most with more than one page).
** e.g. [http://bugguide.net/node/view/70875 Arge pectoralis - Birch Sawfly]

*[http://www.bto.org/birdtrack/ BirdTrack]
**[http://blx1.bto.org/bt-dailyresults/results/s171-20-06.html Lapwing]

*[http://www.discoverlife.org/ Discover Life] - "contains '''306,553''' species. The Polistes Foundation and its scientific partners plan to add high-quality identification guides, maps, images, and text for '''a million species''' by 2012. [...] Each month Discover Life serves approximately 3 million pages and images to 70,000 IP addresses"

*[http://www.record-lrc.co.uk/ rECOrd] (the Local Biological Records Centre serving the Cheshire region of England) - '''1.6 million''' species records available online for the public to search and map

===Planned sites===
*[http://herbariaunited.org/atHome/ Herbaria United] (part of The website of the Botanical Collection Managers Group (BCMG), a specialist group of the Linnean Society of London) - "The UK has the world's largest and oldest collections of herbarium specimens held in trust by museums and universities. A new project is just getting underway to put all this online."

==Notable websites==
These high-profile websites use species names

*Amazon
**[http://www.amazon.co.uk/s/?url=search-alias%3Daps&field-keywords=%22house+sparrow%22 search for "House Sparrow"]

*BBC News
**[http://news.bbc.co.uk/1/hi/uk/4835208.stm Fewer birds spotted in UK gardens]
**[http://news.bbc.co.uk/1/hi/england/london/4743250.stm Study to solve sparrow's decline riddle]

*Encyclopaedia Britannica - all species, e.g.
**[http://concise.britannica.com/ebc/article-9379473/starling Starling]

*Flickr
**[http://www.flickr.com/photos/tags/citheronia/ Tag for moth genera 'citheronia']
***[http://www.flickr.com/photos/30268343@N00/152101772/ Sample result from that search]
**[http://www.flickr.com/groups/birdguide/ Field Guide: Birds of the World] 23,073 tagged photos, as at 2006-10-21

*CNN
**[http://archives.cnn.com/2001/NATURE/01/24/dying.eagles/ Disease threatens bald eagle population]

*eBay
**[http://search.ebay.com/house-sparrow search for "House Sparrow"]

*The Guardian
**[http://environment.guardian.co.uk/conservation/story/0,,1878956,00.html The call of the wildlife]
**[http://education.guardian.co.uk/higher/news/story/0,,1665396,00.html Sparrow joins 'raped' duck in Dutch museum] (note improper capitalisation "''passer domesticus''")

*London Zoo
**[http://www.zsl.org/london-zoo/animals/birds/tawny-frogmouth,99,AN.html Tawny frogmouth]

*Microsoft
**[http://www.microsoft.com/games/zootycoon/zoo2/zoo2_ymi_animals1.asp Zoo Tycoon]

*MSN-Encarta - all species, e.g.
**[http://encarta.msn.com/encnet/refpages/search.aspx?q=vulgaris&Submit2=Go Search for "vulgaris"]

*MySpace
**[http://blog.myspace.com/index.cfm?fuseaction=blog.view&friendID=47134278&blogID=79591637]

*Nature
**[http://www.nature.com/nature/focus/avianflu/index.html Avian flu web focus]

*Nature Network, Boston
**[http://network.nature.com/boston/news/archive/2006/06/13/the-student-and-the-squid The student and the squid] '''N.B.''' site already supports rel-tag, hCard for user profiles and hCalendar for marking up events across the site.

*NASA
**[http://history.nasa.gov/SP-401/ch3.htm SP-401 Skylab, Classroom in Space. Part II - Student Experiments] ("The common Cross spider (Araneus diadematus)")

*New York Times
**[http://query.nytimes.com/gst/fullpage.html?sec=travel&res=9D04E4DE1131F93BA25751C0A9669C8B63 Where the Eagles Fly: Seeing the National Symbol]

*Snopes (Urban Legends Reference Pages)
**[http://www.snopes.com/photos/animals/fishfly.asp Fish Fly]

*United Kingdom Government
**[http://www.defra.gov.uk/wildlife-countryside/vertebrates/gen-licence.htm DEFRA: General licences under the Wildlife & Countryside Act 1981]

*United States of America Government
**ITIS, e.g. [http://www.itis.usda.gov/servlet/SingleRpt/SingleRpt?search_topic=TSN&search_value=179628 Passer Domesticus] - "authoritative taxonomic information on plants, animals, fungi, and microbes of North America and the world"

*W3C
**[http://dev.w3.org/cvsweb/2000/10/swap/test/ferrell/biology.n3?rev=1.4 An Ontology of Biology]
**[http://esw.w3.org/topic/HCLSIG_BioRDF_Subgroup/Tasks/Reagents/Status_Reports/2006-05-04 BioRDF Sub-group Status Report, 4 May 2006]

*Yahoo Groups
**[http://tech.groups.yahoo.com/group/passerdomesticus/ passerdomesticus] species as group name!

==Breaking news==
*[http://news.bbc.co.uk/1/shared/spl/hi/pop_ups/06/sci_nat_orchid_spectacular/html/1.stm BBC News: Stunning new orchids from Asia's rainforest] - 2006-10-16
*[http://news.bbc.co.uk/1/hi/sci/tech/6045802.stm BBC News: Winter home find cheers twitchers] (winter home of the northern bald ibis found) - 2006-10-13
*[http://news.bbc.co.uk/1/hi/sci/tech/6043648.stm BBC News: New mouse find is 'living fossil'] - 2006-10-12
*[http://news.bbc.co.uk/1/hi/sci/tech/6035113.stm BBC News: Giant camel fossil found in Syria] - 2006-10-10
*[http://news.bbc.co.uk/1/hi/sci/tech/5414410.stm BBC News: Sharks swim into political waters] - 2006-10-06
*[http://news.bbc.co.uk/1/hi/sci/tech/5403570.stm BBC News: 'Monster' fossil find in Arctic] - 2006-10-05

==Use in blogs==
*[http://technorati.com/search/%22passer%20domesticus%22 Technorati search for "Passer domesticus"] (367 found, as at 2006-09-25)
*[http://technorati.com/search/%22acer%20palmatum%22 Technorati search for "Acer palmatum"] (682 found, as at 2006-09-25)
*[http://technorati.com/search/%22Homo%20sapiens%22 Technorati search for "Homo sapiens"] (40,932 found, as at 2006-09-25)
*[http://technorati.com/search/birding Technorati search for "birding"] (26,472 found, as at 2006-09-25)
*[http://ramblingsofanaturalist.blogspot.com/ Ramblings of a Naturalist]
*[http://squaremetre1.blogspot.com/ The Square Metre]
*[http://windowboxwildlife.blogspot.com/index.html Windowbox Wildlife]
*[http://www.rxwildlife.org.uk/ RXWildlife]

==And finally...==
Gary Larson, in his book ''The Far Side Gallery'' (Warner Books, 1980, ISBN 0751502367) has a cartoon, showing two entomologists sitting down to eat dinner in a jungle. One says to the other "Hey! What's this ''Drosophila melanogaster'' doing in my soup?"

==Contributors==
*[[User:AndyMabbett|Andy Mabbett]] (proponent)
*Malcolm Storey (per e-mail)
*[[User:SXBRC|Charles Roper]], [http://www.sxbrc.org.uk/ Sussex Biodiversity Record Centre] (proponent)
*[[User:SteveMcBill|Steve McWilliam]], [http://www.rECOrd-LRC.co.uk/ rECOrd - The Biodiversity Information System for the Cheshire region] (proponent)

==See also==
[[species-brainstorming]]

species-examples

2006-10-22T04:52:57Z

BenWest: /* Arachnid */ nature.com link requires premium subscription. removed

=Species Examples=

Examples of common and scientific names of living things, which could be marked up with a "'''[[species]]'''" (or similar) microformat. Note use of matching pairs of examples, where possible.

__TOC__

== Grouped By Publisher ==

=== West Midland Bird Club ===
* [http://www.westmidlandbirdclub.com/ladywalk/latest.htm Black-tailed Godwit]
<pre><nowiki>Black-tailed Godwit</nowiki></pre>

* [http://www.westmidlandbirdclub.com/records/lists.htm Limosa limosa ]
<pre><nowiki><td>Limosa limosa</td></nowiki></pre>

=== species.mediawiki.org ===
[http://species.wikimedia.org/wiki/Charadrius_dubius species.mediawiki.org media bird ] .
<pre><nowiki>
<dd>Regnum: <a href="/wiki/Animalia" title="Animalia">Animalia</a> (Metazoa)
<dl>
<dd>Subregnum: <a href="/wiki/Eumetazoa" title="Eumetazoa">Eumetazoa</a>
<dl>
<dd>Superphylum: Bilateria: <a href="/wiki/Deuterostomia" title="Deuterostomia">Deuterostomia</a>
<dl>
<dd>Phylum: <a href="/wiki/Chordata" title="Chordata">Chordata</a>
<dl>

<dd>Subphylum: <a href="/wiki/Vertebrata" title="Vertebrata">Vertebrata</a>
<dl>
<dd>Classis: <a href="/wiki/Aves" title="Aves">Aves</a>
<dl>
<dd>Subclassis: <a href="/wiki/Neognathae" title="Neognathae">Neognathae</a>
<dl>
<dd>Ordo: <a href="/wiki/Charadriiformes" title="Charadriiformes">Charadriiformes</a>
<dl>
<dd>Subordo: <a href="/wiki/Charadrii" title="Charadrii">Charadrii</a>

<dl>
<dd>Familia: <a href="/wiki/Charadriidae" title="Charadriidae">Charadriidae</a>
<dl>
<dd>Subfamily: <a href="/wiki/Charadriinae" title="Charadriinae">Charadriinae</a>
<dl>
<dd>Genus: <a href="/wiki/Charadrius" title="Charadrius">Charadrius</a>
<dl>
<dd>Species: Charadrius dubius
<dl>

<dd>Subspecies: <a href="/w/index.php?title=Charadrius_dubius_curonicus&action=edit" class="new" title="Charadrius dubius curonicus">C. d. curonicus</a> - <a href="/w/index.php?title=Charadrius_dubius_dubius&action=edit" class="new" title="Charadrius dubius dubius">C. d. dubius</a> - <a href="/w/index.php?title=Charadrius_dubius_jerdoni&action=edit" class="new" title="Charadrius dubius jerdoni">C. d. jerdoni</a> - <a href="/w/index.php?title=Charadrius_dubius_papuanus&action=edit" class="new" title="Charadrius dubius papuanus">C. d. papuanus</a></dd>

...
</nowiki>
</pre>

* Comments
** This feels similar to tagging to me. This particular example has a resolves the whole heirarchy, correct? [[User:BenWest|BenWest]] 17:57, 21 Oct 2006 (PDT)

== Alternative Grouping By Strategy ==
I'd like to regroup these examples... perhaps by publishing strategy instead of a list of what is being published. Should this be available as an alternate grouping section? In the mean time, a grouping by publisher would help analysis go smoother. [[User:BenWest|BenWest]] 17:57, 21 Oct 2006 (PDT)

I looked at several examples. Several of them feel like tagging to me. Should we attempt to note what level or resolution is available in each example?

=== Tagging ===
The [[http://species.wikimedia.org/wiki/Charadrius_dubius wiki media bird example]] is particularly interesting.
<pre><nowiki>
<dd>Regnum: <a href="/wiki/Animalia" title="Animalia">Animalia</a> (Metazoa)
<dl>
<dd>Subregnum: <a href="/wiki/Eumetazoa" title="Eumetazoa">Eumetazoa</a>
<dl>
<dd>Superphylum: Bilateria: <a href="/wiki/Deuterostomia" title="Deuterostomia">Deuterostomia</a>
<dl>
<dd>Phylum: <a href="/wiki/Chordata" title="Chordata">Chordata</a>
<dl>

<dd>Subphylum: <a href="/wiki/Vertebrata" title="Vertebrata">Vertebrata</a>
<dl>
<dd>Classis: <a href="/wiki/Aves" title="Aves">Aves</a>
<dl>
<dd>Subclassis: <a href="/wiki/Neognathae" title="Neognathae">Neognathae</a>
<dl>
<dd>Ordo: <a href="/wiki/Charadriiformes" title="Charadriiformes">Charadriiformes</a>
<dl>
<dd>Subordo: <a href="/wiki/Charadrii" title="Charadrii">Charadrii</a>

<dl>
<dd>Familia: <a href="/wiki/Charadriidae" title="Charadriidae">Charadriidae</a>
<dl>
<dd>Subfamily: <a href="/wiki/Charadriinae" title="Charadriinae">Charadriinae</a>
<dl>
<dd>Genus: <a href="/wiki/Charadrius" title="Charadrius">Charadrius</a>
<dl>
<dd>Species: Charadrius dubius
<dl>

<dd>Subspecies: <a href="/w/index.php?title=Charadrius_dubius_curonicus&action=edit" class="new" title="Charadrius dubius curonicus">C. d. curonicus</a> - <a href="/w/index.php?title=Charadrius_dubius_dubius&action=edit" class="new" title="Charadrius dubius dubius">C. d. dubius</a> - <a href="/w/index.php?title=Charadrius_dubius_jerdoni&action=edit" class="new" title="Charadrius dubius jerdoni">C. d. jerdoni</a> - <a href="/w/index.php?title=Charadrius_dubius_papuanus&action=edit" class="new" title="Charadrius dubius papuanus">C. d. papuanus</a></dd>

...
</nowiki>
</pre>
This feels similar to tagging to me. This particular example has a resolves the whole heirarchy, correct? [[User:BenWest|BenWest]] 17:57, 21 Oct 2006 (PDT)

==binominals==

===Birds===

'''Black-tailed Godwit''' on [http://www.westmidlandbirdclub.com/ladywalk/latest.htm West Midland Bird Club's Ladywalk reserve latest news page]

<pre><nowiki>Black-tailed Godwit</nowiki></pre>

'''''Limosa limosa''''' on [http://www.westmidlandbirdclub.com/records/lists.htm West Midland Bird Club's county lists']

<pre><nowiki><td>Limosa limosa</td></nowiki></pre>

===Mammal===
'''Wolf''' on [http://www.wolf.org/wolves/index.asp International Wolf Center]

===Fish===
'''Northern pike''' on [http://www.dnr.state.mn.us/fish/northern/index.html Minnesota Department of Natural Resources]

'''''Esox lucius''''' on [http://www.pikezander.co.uk/pike.htm Pike & Zander]

===Insect===
'''Death’s Head Hawkmoth''' on [http://funkman.org/animal/insect/deathheadmoth.html Animal Teachers]

'''''Acherontia atropos''''' on [http://ukmoths.org.uk/show.php?id=2540 UK Moths]

'''Migrant Hawker''' (''Aeshna mixta'') on [http://www.sxbrc.org.uk/news/friston-forest-recording-day Sussex Biodiversity Record Centre]

===Arachnid===
'''Costa Rican zebra tarantula''' (''Aphonopelma seemanni'') on [http://www.nature.com/news/2006/060925/full/060925-6.html Nature.com]

'''''Araneus angulatus''''' on [http://www.sxbrc.org.uk/news/friston-forest-recording-day Sussex Biodiversity Record Centre]

===Plant===
'''Bog Pimpernel''' on [http://www.map-reading.co.uk/wildflowers/HTML%20files/f0219.htm Map Reading's Wildflower Images]

'''''Anagallis tenella''''' on [http://www.bioimages.org.uk/HTML/T47624.HTM BioImages]

'''''Persicaria campanulatum''''' on [http://www.record-lrc.co.uk/?Mod=Forum&Do=ViewThread&ForumID=6&ThreadID=75 rECOrd - The Biodiversity Information Centre for the Cheshire region]

===Fungi===

'''''Amanita muscaria''''' on [http://www.mykoweb.com/CAF/species/Amanita_muscaria.html California Fungi]
* as '''''Amanita muscaria'' (L. per Fr.) Hooker'''
* as '''''Amanita muscaria var. flavivolvata'''''

'''Fly Agaric''' on [http://www.treesforlife.org.uk/forest/mythfolk/flyagaric.html Trees for Life]

'''''Rhodocollybia maculata'' (Albertini & Schweinitz: Fries) Singer''' on [http://www.ilmyco.gen.chicago.il.us/Taxa/Rhodomacul540.html]
*also written as '''''Rhodocollybia maculata'' (Albertini & Schweinitz ex Fries) Singer'''
*(This is where a post-Linnean author is given special rights (because his descriptions were comparatively complete - i.e. recognisable) so his interpretation of earlier names is taken as the sense meant by the original author. Think these used to be "apud" and are now "ex" although a colon has also been used. There are only a few sanctioning authors, the main one being Elias Fries.(Fr.) )

==More than binominals==

===Authority===
'''''Pica pica'' Linnaeus, (1758)''' on [http://en.wikipedia.org/wiki/European_Magpie Wikipedia: European Magpie]
:(i.e. named by Linnaeus in 1758)

===Unspecified species===
'''''Podiceps sp.''''' on [http://www.birdlife.org/datazone/species/index.html?action=SpcHTMDetails.asp&sid=3644&m=0 Bird Life] <pre><nowiki>Podiceps sp.</nowiki></pre>

'''Psyllid plant hopper''' [http://ramblingsofanaturalist.blogspot.com/2006/07/bay-sucker-gall-trioza-alacris.html on Ramblings of a Naturalist blog]

===Sub-species===

====Animal====
'''''Larus glaucoides kumlieni''' on [http://www.birdguides.com/html/vidlib/species/Larus_glaucoides_kumlieni.htm BirdGuides]

'''Kumlien's Gull''' on [http://www.birdsireland.com/pages/rare_bird_news/2005/january_photos.html Birds Ireland]

====Plant====
'''''Pisum sativum L. subsp. sativum''''' on [http://www.plantnames.unimelb.edu.au/Sorting/Pisum.html] (also has other examples; note lack of required italics)
<pre><nowiki>Pisum sativum L. subsp. sativum</nowiki></pre>

===Cultivars (plant)===
'''''Chamaecyparis lawsoniana 'Aureomarginata'''''' on [http://en.wikipedia.org/wiki/Cultivar Wikipedia: Cultivar]

<pre><nowiki><dd>Chamaecyparis lawsoniana 'Aureomarginata'</dd></nowiki></pre>

'''''Chamaecyparis lawsoniana'' 'Golden Wonder'''' on [http://www.plantago.nl/plantindex/c/Chamaecyparis/Chamaecyparis_4.htm plantago.nl]

====Cultivar groups (plant)====
'''''Brassica oleracea'' Botrytis Group''' on [http://en.wikipedia.org/wiki/Cultivar Wikipedia: Cultivar]

===Trade names (plant)===

'''''Rosa'' Peace''' on [http://en.wikipedia.org/wiki/Cultivar Wikipedia: Cultivar]
:("Peace" is a trade designation or "selling name" for the cultivar R. 'Madame A. Meilland' and should therefore be printed in a different typeface from the rest of the name, without any quote marks)

'''Sunflower 'Giant Single'''' on [http://cgi.www.johnsons-seeds.com/cgi-bin/www.johnsons-seeds.com/detail/azlist/S-1 Johnsons Seeds]

'''Sunflower 'Infrared' F1''' on [http://cgi.www.johnsons-seeds.com/cgi-bin/www.johnsons-seeds.com/detail/azlist/S-1 Johnsons Seeds]
:(Note "F1" cross designation)

===Variety (plant)===
'''''Pisum sativum var. macrocarpon''''' on [http://davesgarden.com/pf/go/8/index.html Dave's Garden]

====Sub-variety (plant)====

'''''Betula ermani var. genuina subvar. brevidentata''''' on [http://www.nccpg.com/gloucestershire/wilson1.html National Council for the Conservation of Plants and Gardens, Gloucestershire Group] (plus many other examples)

===Form (plant)===

'''''Acanthocalycium spiniflorum f. klimpelianum''''' on [http://en.wikipedia.org/wiki/Form_%28botany%29 Wikipedia: form (botany)]
*aka '''''Acanthocalycium spiniflorum forma klimpelianum'''''

===Sense (plant)===
'''''Ranunculus aquatilis s.l.''''' and '''''R. aquatilis s.s'''''; on [http://www.westmidlandbirdclub.com/blithfield/plants20060815.htm Blithfield Reservoir: Survey of Flowering Plants...] (see also footnotes on that page)

===Cross (plant)===
'''''Digitalis x mertonensis''''' on [http://www.hortax.org.uk/gardenplantsnames.html Hortax]
:The hybrid name for all plants derived from the cross between '''D. purpurea''' and '''D. grandiflora'''. The "x" indicates the hybrid status.

'''''× Fatshedera lizei''''' on [http://oregonstate.edu/dept/ldplants/sci-names.htm Scientific Plant Names, Oregon State Univ., Landscape Plants]

===Strain (bacteria)===
'''''Escherichia coli O157:H7''''' on [http://www.cfsan.fda.gov/~mow/chap15.html FDA.gov]

'''''E.Coli''''' on [http://news.bbc.co.uk/1/hi/england/southern_counties/5346842.stm BBC news]

==Misc==
===Superseded names===
'''''Tringa bartramia''''' superseded by '''''Bartramia longicauda''''' on [http://www.westmidlandbirdclub.com/firsts/UPLSA.htm West Midland Bird Club's Upland Sandpiper article]

===GUID===
'''NBN Taxon Key''' for European Otter, ''Lutra lutra'', on [http://nbn.nhm.ac.uk/nhm/bin/nbntaxa.dll/taxon_details?taxon_key=NBNSYS0000005133 NBN Species Dictionary]: '''NBNSYS0000005133'''

'''LSID ([http://lsid.sourceforge.net/#whatislsid Life Science Indicator])''' for ''Popillia japonica'' on [http://names.ubio.org/browser/details2.php?names=on&authors=on&sci=on&vern=on&conceptID=&expand=&namebankID=3377001 uBio]: '''urn:lsid:ubio.org:namebank:3377001'''

===Wikipedia===
'''Black-tailed Godwit''' on [http://en.wikipedia.org/wiki/Black-tailed_Godwit Wikipedia: Black-tailed Godwit]

Wikipedia uses several sets of markup, e.g. (in-line styles and links, plus some other markup, removed, for clarity):

<pre><nowiki>The Black-tailed Godwit, Limosa limosa</nowiki></pre>

and:

<pre><nowiki>
<tr>
<td>Kingdom:</td>
<td>Animalia</td>
</tr>
<tr>
<td>Phylum:</td>
<td>Chordata</td>
</tr>
<tr>
<td>Class:</td>
<td>Aves</td>
</tr>
<tr>
<td>Order:</td>
<td>Charadriiformes</td>
</tr>
<tr>
<td>Family:</td>
<td>Scolopacidae</td>
</tr>
<tr>
<td>Genus:</td>
<td>Limosa</td>
</tr>
<tr>
<td>Species:</td>
<td>L. limosa</td>
</tr>

<tr>
<th>binominal name</th>
</tr>
<tr>
<td>Limosa limosa
<td>(Linnaeus, 1758)</td>
</tr>
</nowiki></pre>

==Quantitative evidence==

For evidence of quantitative, rather than qualitative, use of species' and other taxonomic names, see [http://microformats.org/discuss/mail/microformats-discuss/2006-September/005790.html] and [http://microformats.org/discuss/mail/microformats-discuss/2006-September/005791.html]. Furthermore:

*Wikipedia:
** '''All''' species articles, e.g. [http://en.wikipedia.org/wiki/Little_Ringed_Plover Little Ringed Plover] (see [[species-examples#Wikipedia|above]])
** '''All''' genera articles, e.g. [http://en.wikipedia.org/wiki/Plover Charadrius (Plover)]
** '''All''' higher classes, e.g. [http://en.wikipedia.org/wiki/Charadriidae Charadriidae]
** '''All''' regional lists, e.g. [http://en.wikipedia.org/wiki/List_of_British_birds:_non-passerines List of British birds]
** '''All''' dedicatees, e.g. [http://en.wikipedia.org/wiki/Alexander_Wilson Alexander Wilson]
** '''All''' authorities, e.g. [http://en.wikipedia.org/wiki/Giovanni_Antonio_Scopoli Giovanni Antonio Scopoli]
** '''All''' images of living things, e.g. [http://en.wikipedia.org/wiki/Image:Charadrius_dubius_4_%28Marek_Szczepanek%29.jpg Charadrius dubius 4 (Marek Szczepanek).jpg]
** Many reserves, lakes, and other places of interest, e.g. [http://en.wikipedia.org/wiki/Belvide Belvide]
** Many biological authors and illustrators, e.g. [http://en.wikipedia.org/wiki/John_Audubon John Audubon]; [http://en.wikipedia.org/wiki/Gilbert_White Gilbert White]
** Random articles on other topics, e.g. [http://en.wikipedia.org/wiki/Balancing_lake Balancing lake}]
** '''All the above, again''', for each alternative language e.g. [http://cy.wikipedia.org/wiki/Cwtiad_Torchog_Bach Welsh]; [http://fr.wikipedia.org/wiki/Petit_gravelot French]; [http://zh.wikipedia.org/wiki/%E9%87%91%E7%9C%B6%E9%B8%BB Chinese]

*Wikimedia Commons
** '''All''' species indexes, e.g. [http://commons.wikimedia.org/wiki/Charadrius_dubius Charadrius dubius]
** '''Each individual''' image, e.g. [http://commons.wikimedia.org/wiki/Image:Charadrius_dubius_1_%28Marek_Szczepanek%29.jpg Charadrius dubius 1 (Marek Szczepanek).jpg]
** '''Each family''' list [http://commons.wikimedia.org/wiki/Charadriidae Charadriidae]

*Wiktionary
** '''All''' species articles, e.g. [http://en.wiktionary.org/wiki/american_golden_plover American Golden Plover]
** '''All''' family articles, e.g. [http://en.wiktionary.org/wiki/plover Plover]
** '''Many of the above, in other langauges''' e.g. [http://en.wiktionary.org/wiki/aquila_reale Italian]; [http://en.wiktionary.org/wiki/%D0%B1%D0%B5%D1%80%D0%BA%D1%83%D1%82 Russian]

*Wikispecies
** '''Every''' speices, e.g. [http://species.wikimedia.org/wiki/Charadrius_dubius Charadrius dubius]
** '''Every''' genus, e.g. [http://species.wikimedia.org/wiki/Charadrius Charadrius]
** '''Every''' sub-family, e.g. [http://species.wikimedia.org/wiki/Charadriinae Charadriinae]
** '''Every''' family, e.g. [http://species.wikimedia.org/wiki/Charadriidae Charadriidae]
** and so on, for '''every other rank'''
** '''Every''' image (e.g. [http://species.wikimedia.org/wiki/Image:Charadrius_hiaticula_He.jpg Charadrius hiaticula He.jpg]

*Google
**[http://www.google.co.uk/search?hl=en&hs=dBU&client=firefox-a&rls=org.mozilla:en-US:official&sa=X&oi=spell&resnum=0&ct=result&cd=1&q=%22E+coli%22&spell=1 Google finds about '''37,600,000''' for "E coli"].
***[http://www.google.co.uk/search?hs=Apo&hl=en&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&q=%22Escherichia+coli%22&btnG=Search&meta= Google finds about '''19,500,000''' for "Escherichia coli"]
***[http://www.google.co.uk/search?hs=zqo&hl=en&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&q=%22Ecoli%22&btnG=Search&meta= Google finds about '''722,000''' for "Ecoli"].
**[http://www.google.co.uk/search?hs=vWC&hl=en&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&q=%22Homo+sapiens%22&btnG=Search&meta= Google finds about '''14,200,000''' for "Homo sapiens"]
***[http://www.google.co.uk/search?hs=vWC&hl=en&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&q=%22Homo+sapien%22+-sapiens&btnG=Search&meta= Google finds about '''273,000''' for the mis-spelling "Homo sapien" -sapiens.]
**[http://www.google.co.uk/search?q=%22%22Homo+erectus%22%22&start=0&ie=utf-8&oe=utf-8&client=firefox-a&rls=org.mozilla:en-US:official Google finds about '''1,260,000''' for ""Homo erectus"]
**[http://www.google.com/search?svnum=10&as_scoring=r&hl=en&edition=us&as_drrb=q&as_qdr=&as_mind=1&as_minm=9&as_maxd=1&as_maxm=10&q=%22Clostridium+difficile%22&ie=UTF-8&sa=N&tab=nw Google finds about '''1,380,000''' for "Clostridium difficile"].
**[http://www.google.com/search?hl=en&lr=&edition=us&q=%22Passer+domesticus%22&btnG=Search Google finds about '''841,000''' for "Passer domesticus"].
***[http://images.google.com/images?hl=en&lr=&edition=us&q=%22Passer%20domesticus%22&btnG=Search&sa=N&tab=wi Google images finds about '''3,140''' for "Passer domesticus"].
**[http://www.google.co.uk/search?hl=en&hs=oEU&client=firefox-a&rls=org.mozilla:en-US:official&sa=X&oi=spell&resnum=0&ct=result&cd=1&q=%22Acer+palmatum%22&spell=1 Google finds about '''602,000''' for "Acer palmatum"]
** At the time of writing, '''every single one''' of the first 20 [http://www.google.com/search?q=%22Noctule+bat%22 Google results for "Noctule Bat"] also includes the scientific name ''Nyctalus noctula''.

*[http://www.arkive.org/ ARKive] - '''2000''' species ("It is ARKive's current aim to compile audio-visual records, where such media exists, for the 15,000-plus species currently threatened with extinction, according to the World Conservation Union's (IUCN) Red List of Threatened Species.")

*[http://www.rhs.org.uk/rhsplantfinder/plantfinder.asp Royal Horticultural Society - RHS Plant Finder] - '''70,000''' plants

*[http://www.bacterio.net List of Prokaryotic Names (formerly List of Bacterial Names)] - 2,032 *files*; '''10,268''' published names (to 2006-09-07)

*[http://nbn.nhm.ac.uk/nhm/ UK National Biodiversity Network's Species Dictionary]

*[http://www.searchnbn.net/ UK National Biodiversity Network Gateway] - '''20 million+''' species records

*[http://www.sp2000.org/ Species 2000] - '''450,000 species'''

*[http://www.bioimages.org.uk/index.html BioImages - Virtual Fieldguide] - '''53,000''' images depicting 4,600 species (see [[species-brainstorming#Malcolm_Storey|Wiki comments from site owner]])

*[http://animaldiversity.ummz.umich.edu/ Animal Diversity Web] - "'''Thousands''' of species accounts ['''plus'''] descriptions of levels of organization above the species level, especially phyla, classes, and in some cases, orders and families. Hundreds of hyperlinked pages and images illustrate the traits and general biology of these groups"

* [http://www.ubio.org/index.php?pagename=home uBio]
**NameBank is a repository of '''millions''' of recorded biological names and facts that link those names together.
**ClassificationBank stores multiple classifications and taxonomic concepts that are the result of expert opinions. It extends the functionality of NameBank.

*[http://www.birdlife.org/datazone/species/ BirdLife International] - all birds of the world (~'''10,000''')

*[http://bugguide.net/ Bug Guide] - all insects, spiders, and allies, of the USA and Canada (most with more than one page).
** e.g. [http://bugguide.net/node/view/70875 Arge pectoralis - Birch Sawfly]

*[http://www.bto.org/birdtrack/ BirdTrack]
**[http://blx1.bto.org/bt-dailyresults/results/s171-20-06.html Lapwing]

*[http://www.discoverlife.org/ Discover Life] - "contains '''306,553''' species. The Polistes Foundation and its scientific partners plan to add high-quality identification guides, maps, images, and text for '''a million species''' by 2012. [...] Each month Discover Life serves approximately 3 million pages and images to 70,000 IP addresses"

*[http://www.record-lrc.co.uk/ rECOrd] (the Local Biological Records Centre serving the Cheshire region of England) - '''1.6 million''' species records available online for the public to search and map

===Planned sites===
*[http://herbariaunited.org/atHome/ Herbaria United] (part of The website of the Botanical Collection Managers Group (BCMG), a specialist group of the Linnean Society of London) - "The UK has the world's largest and oldest collections of herbarium specimens held in trust by museums and universities. A new project is just getting underway to put all this online."

==Notable websites==
These high-profile websites use species names

*Amazon
**[http://www.amazon.co.uk/s/?url=search-alias%3Daps&field-keywords=%22house+sparrow%22 search for "House Sparrow"]

*BBC News
**[http://news.bbc.co.uk/1/hi/uk/4835208.stm Fewer birds spotted in UK gardens]
**[http://news.bbc.co.uk/1/hi/england/london/4743250.stm Study to solve sparrow's decline riddle]

*Encyclopaedia Britannica - all species, e.g.
**[http://concise.britannica.com/ebc/article-9379473/starling Starling]

*Flickr
**[http://www.flickr.com/photos/tags/citheronia/ Tag for moth genera 'citheronia']
***[http://www.flickr.com/photos/30268343@N00/152101772/ Sample result from that search]
**[http://www.flickr.com/groups/birdguide/ Field Guide: Birds of the World] 23,073 tagged photos, as at 2006-10-21

*CNN
**[http://archives.cnn.com/2001/NATURE/01/24/dying.eagles/ Disease threatens bald eagle population]

*eBay
**[http://search.ebay.com/house-sparrow search for "House Sparrow"]

*The Guardian
**[http://environment.guardian.co.uk/conservation/story/0,,1878956,00.html The call of the wildlife]
**[http://education.guardian.co.uk/higher/news/story/0,,1665396,00.html Sparrow joins 'raped' duck in Dutch museum] (note improper capitalisation "''passer domesticus''")

*London Zoo
**[http://www.zsl.org/london-zoo/animals/birds/tawny-frogmouth,99,AN.html Tawny frogmouth]

*Microsoft
**[http://www.microsoft.com/games/zootycoon/zoo2/zoo2_ymi_animals1.asp Zoo Tycoon]

*MSN-Encarta - all species, e.g.
**[http://encarta.msn.com/encnet/refpages/search.aspx?q=vulgaris&Submit2=Go Search for "vulgaris"]

*MySpace
**[http://blog.myspace.com/index.cfm?fuseaction=blog.view&friendID=47134278&blogID=79591637]

*Nature
**[http://www.nature.com/nature/focus/avianflu/index.html Avian flu web focus]

*Nature Network, Boston
**[http://network.nature.com/boston/news/archive/2006/06/13/the-student-and-the-squid The student and the squid] '''N.B.''' site already supports rel-tag, hCard for user profiles and hCalendar for marking up events across the site.

*NASA
**[http://history.nasa.gov/SP-401/ch3.htm SP-401 Skylab, Classroom in Space. Part II - Student Experiments] ("The common Cross spider (Araneus diadematus)")

*New York Times
**[http://query.nytimes.com/gst/fullpage.html?sec=travel&res=9D04E4DE1131F93BA25751C0A9669C8B63 Where the Eagles Fly: Seeing the National Symbol]

*Snopes (Urban Legends Reference Pages)
**[http://www.snopes.com/photos/animals/fishfly.asp Fish Fly]

*United Kingdom Government
**[http://www.defra.gov.uk/wildlife-countryside/vertebrates/gen-licence.htm DEFRA: General licences under the Wildlife & Countryside Act 1981]

*United States of America Government
**ITIS, e.g. [http://www.itis.usda.gov/servlet/SingleRpt/SingleRpt?search_topic=TSN&search_value=179628 Passer Domesticus] - "authoritative taxonomic information on plants, animals, fungi, and microbes of North America and the world"

*W3C
**[http://dev.w3.org/cvsweb/2000/10/swap/test/ferrell/biology.n3?rev=1.4 An Ontology of Biology]
**[http://esw.w3.org/topic/HCLSIG_BioRDF_Subgroup/Tasks/Reagents/Status_Reports/2006-05-04 BioRDF Sub-group Status Report, 4 May 2006]

*Yahoo Groups
**[http://tech.groups.yahoo.com/group/passerdomesticus/ passerdomesticus] species as group name!

==Breaking news==
*[http://news.bbc.co.uk/1/shared/spl/hi/pop_ups/06/sci_nat_orchid_spectacular/html/1.stm BBC News: Stunning new orchids from Asia's rainforest] - 2006-10-16
*[http://news.bbc.co.uk/1/hi/sci/tech/6045802.stm BBC News: Winter home find cheers twitchers] (winter home of the northern bald ibis found) - 2006-10-13
*[http://news.bbc.co.uk/1/hi/sci/tech/6043648.stm BBC News: New mouse find is 'living fossil'] - 2006-10-12
*[http://news.bbc.co.uk/1/hi/sci/tech/6035113.stm BBC News: Giant camel fossil found in Syria] - 2006-10-10
*[http://news.bbc.co.uk/1/hi/sci/tech/5414410.stm BBC News: Sharks swim into political waters] - 2006-10-06
*[http://news.bbc.co.uk/1/hi/sci/tech/5403570.stm BBC News: 'Monster' fossil find in Arctic] - 2006-10-05

==Use in blogs==
*[http://technorati.com/search/%22passer%20domesticus%22 Technorati search for "Passer domesticus"] (367 found, as at 2006-09-25)
*[http://technorati.com/search/%22acer%20palmatum%22 Technorati search for "Acer palmatum"] (682 found, as at 2006-09-25)
*[http://technorati.com/search/%22Homo%20sapiens%22 Technorati search for "Homo sapiens"] (40,932 found, as at 2006-09-25)
*[http://technorati.com/search/birding Technorati search for "birding"] (26,472 found, as at 2006-09-25)
*[http://ramblingsofanaturalist.blogspot.com/ Ramblings of a Naturalist]
*[http://squaremetre1.blogspot.com/ The Square Metre]
*[http://windowboxwildlife.blogspot.com/index.html Windowbox Wildlife]
*[http://www.rxwildlife.org.uk/ RXWildlife]

==And finally...==
Gary Larson, in his book ''The Far Side Gallery'' (Warner Books, 1980, ISBN 0751502367) has a cartoon, showing two entomologists sitting down to eat dinner in a jungle. One says to the other "Hey! What's this ''Drosophila melanogaster'' doing in my soup?"

==Contributors==
*[[User:AndyMabbett|Andy Mabbett]] (proponent)
*Malcolm Storey (per e-mail)
*[[User:SXBRC|Charles Roper]], [http://www.sxbrc.org.uk/ Sussex Biodiversity Record Centre] (proponent)
*[[User:SteveMcBill|Steve McWilliam]], [http://www.rECOrd-LRC.co.uk/ rECOrd - The Biodiversity Information System for the Cheshire region] (proponent)

==See also==
[[species-brainstorming]]

species-examples

2006-10-22T04:45:10Z

BenWest: /* Insect */ removed the sloe bug link (404)

=Species Examples=

Examples of common and scientific names of living things, which could be marked up with a "'''[[species]]'''" (or similar) microformat. Note use of matching pairs of examples, where possible.

__TOC__

== Grouped By Publisher ==

=== West Midland Bird Club ===
* [http://www.westmidlandbirdclub.com/ladywalk/latest.htm Black-tailed Godwit]
<pre><nowiki>Black-tailed Godwit</nowiki></pre>

* [http://www.westmidlandbirdclub.com/records/lists.htm Limosa limosa ]
<pre><nowiki><td>Limosa limosa</td></nowiki></pre>

=== species.mediawiki.org ===
[http://species.wikimedia.org/wiki/Charadrius_dubius species.mediawiki.org media bird ] .
<pre><nowiki>
<dd>Regnum: <a href="/wiki/Animalia" title="Animalia">Animalia</a> (Metazoa)
<dl>
<dd>Subregnum: <a href="/wiki/Eumetazoa" title="Eumetazoa">Eumetazoa</a>
<dl>
<dd>Superphylum: Bilateria: <a href="/wiki/Deuterostomia" title="Deuterostomia">Deuterostomia</a>
<dl>
<dd>Phylum: <a href="/wiki/Chordata" title="Chordata">Chordata</a>
<dl>

<dd>Subphylum: <a href="/wiki/Vertebrata" title="Vertebrata">Vertebrata</a>
<dl>
<dd>Classis: <a href="/wiki/Aves" title="Aves">Aves</a>
<dl>
<dd>Subclassis: <a href="/wiki/Neognathae" title="Neognathae">Neognathae</a>
<dl>
<dd>Ordo: <a href="/wiki/Charadriiformes" title="Charadriiformes">Charadriiformes</a>
<dl>
<dd>Subordo: <a href="/wiki/Charadrii" title="Charadrii">Charadrii</a>

<dl>
<dd>Familia: <a href="/wiki/Charadriidae" title="Charadriidae">Charadriidae</a>
<dl>
<dd>Subfamily: <a href="/wiki/Charadriinae" title="Charadriinae">Charadriinae</a>
<dl>
<dd>Genus: <a href="/wiki/Charadrius" title="Charadrius">Charadrius</a>
<dl>
<dd>Species: Charadrius dubius
<dl>

<dd>Subspecies: <a href="/w/index.php?title=Charadrius_dubius_curonicus&action=edit" class="new" title="Charadrius dubius curonicus">C. d. curonicus</a> - <a href="/w/index.php?title=Charadrius_dubius_dubius&action=edit" class="new" title="Charadrius dubius dubius">C. d. dubius</a> - <a href="/w/index.php?title=Charadrius_dubius_jerdoni&action=edit" class="new" title="Charadrius dubius jerdoni">C. d. jerdoni</a> - <a href="/w/index.php?title=Charadrius_dubius_papuanus&action=edit" class="new" title="Charadrius dubius papuanus">C. d. papuanus</a></dd>

...
</nowiki>
</pre>

* Comments
** This feels similar to tagging to me. This particular example has a resolves the whole heirarchy, correct? [[User:BenWest|BenWest]] 17:57, 21 Oct 2006 (PDT)

== Alternative Grouping By Strategy ==
I'd like to regroup these examples... perhaps by publishing strategy instead of a list of what is being published. Should this be available as an alternate grouping section? In the mean time, a grouping by publisher would help analysis go smoother. [[User:BenWest|BenWest]] 17:57, 21 Oct 2006 (PDT)

I looked at several examples. Several of them feel like tagging to me. Should we attempt to note what level or resolution is available in each example?

=== Tagging ===
The [[http://species.wikimedia.org/wiki/Charadrius_dubius wiki media bird example]] is particularly interesting.
<pre><nowiki>
<dd>Regnum: <a href="/wiki/Animalia" title="Animalia">Animalia</a> (Metazoa)
<dl>
<dd>Subregnum: <a href="/wiki/Eumetazoa" title="Eumetazoa">Eumetazoa</a>
<dl>
<dd>Superphylum: Bilateria: <a href="/wiki/Deuterostomia" title="Deuterostomia">Deuterostomia</a>
<dl>
<dd>Phylum: <a href="/wiki/Chordata" title="Chordata">Chordata</a>
<dl>

<dd>Subphylum: <a href="/wiki/Vertebrata" title="Vertebrata">Vertebrata</a>
<dl>
<dd>Classis: <a href="/wiki/Aves" title="Aves">Aves</a>
<dl>
<dd>Subclassis: <a href="/wiki/Neognathae" title="Neognathae">Neognathae</a>
<dl>
<dd>Ordo: <a href="/wiki/Charadriiformes" title="Charadriiformes">Charadriiformes</a>
<dl>
<dd>Subordo: <a href="/wiki/Charadrii" title="Charadrii">Charadrii</a>

<dl>
<dd>Familia: <a href="/wiki/Charadriidae" title="Charadriidae">Charadriidae</a>
<dl>
<dd>Subfamily: <a href="/wiki/Charadriinae" title="Charadriinae">Charadriinae</a>
<dl>
<dd>Genus: <a href="/wiki/Charadrius" title="Charadrius">Charadrius</a>
<dl>
<dd>Species: Charadrius dubius
<dl>

<dd>Subspecies: <a href="/w/index.php?title=Charadrius_dubius_curonicus&action=edit" class="new" title="Charadrius dubius curonicus">C. d. curonicus</a> - <a href="/w/index.php?title=Charadrius_dubius_dubius&action=edit" class="new" title="Charadrius dubius dubius">C. d. dubius</a> - <a href="/w/index.php?title=Charadrius_dubius_jerdoni&action=edit" class="new" title="Charadrius dubius jerdoni">C. d. jerdoni</a> - <a href="/w/index.php?title=Charadrius_dubius_papuanus&action=edit" class="new" title="Charadrius dubius papuanus">C. d. papuanus</a></dd>

...
</nowiki>
</pre>
This feels similar to tagging to me. This particular example has a resolves the whole heirarchy, correct? [[User:BenWest|BenWest]] 17:57, 21 Oct 2006 (PDT)

==binominals==

===Birds===

'''Black-tailed Godwit''' on [http://www.westmidlandbirdclub.com/ladywalk/latest.htm West Midland Bird Club's Ladywalk reserve latest news page]

<pre><nowiki>Black-tailed Godwit</nowiki></pre>

'''''Limosa limosa''''' on [http://www.westmidlandbirdclub.com/records/lists.htm West Midland Bird Club's county lists']

<pre><nowiki><td>Limosa limosa</td></nowiki></pre>

===Mammal===
'''Wolf''' on [http://www.wolf.org/wolves/index.asp International Wolf Center]

===Fish===
'''Northern pike''' on [http://www.dnr.state.mn.us/fish/northern/index.html Minnesota Department of Natural Resources]

'''''Esox lucius''''' on [http://www.pikezander.co.uk/pike.htm Pike & Zander]

===Insect===
'''Death’s Head Hawkmoth''' on [http://funkman.org/animal/insect/deathheadmoth.html Animal Teachers]

'''''Acherontia atropos''''' on [http://ukmoths.org.uk/show.php?id=2540 UK Moths]

'''Migrant Hawker''' (''Aeshna mixta'') on [http://www.sxbrc.org.uk/news/friston-forest-recording-day Sussex Biodiversity Record Centre]

===Arachnid===
'''Tarantulas''' on [http://www.nature.com/news/2006/060925/full/060925-6.html Nature.com]

'''Costa Rican zebra tarantula''' (''Aphonopelma seemanni'') on [http://www.nature.com/news/2006/060925/full/060925-6.html Nature.com]

'''''Araneus angulatus''''' on [http://www.sxbrc.org.uk/news/friston-forest-recording-day Sussex Biodiversity Record Centre]

===Plant===
'''Bog Pimpernel''' on [http://www.map-reading.co.uk/wildflowers/HTML%20files/f0219.htm Map Reading's Wildflower Images]

'''''Anagallis tenella''''' on [http://www.bioimages.org.uk/HTML/T47624.HTM BioImages]

'''''Persicaria campanulatum''''' on [http://www.record-lrc.co.uk/?Mod=Forum&Do=ViewThread&ForumID=6&ThreadID=75 rECOrd - The Biodiversity Information Centre for the Cheshire region]

===Fungi===

'''''Amanita muscaria''''' on [http://www.mykoweb.com/CAF/species/Amanita_muscaria.html California Fungi]
* as '''''Amanita muscaria'' (L. per Fr.) Hooker'''
* as '''''Amanita muscaria var. flavivolvata'''''

'''Fly Agaric''' on [http://www.treesforlife.org.uk/forest/mythfolk/flyagaric.html Trees for Life]

'''''Rhodocollybia maculata'' (Albertini & Schweinitz: Fries) Singer''' on [http://www.ilmyco.gen.chicago.il.us/Taxa/Rhodomacul540.html]
*also written as '''''Rhodocollybia maculata'' (Albertini & Schweinitz ex Fries) Singer'''
*(This is where a post-Linnean author is given special rights (because his descriptions were comparatively complete - i.e. recognisable) so his interpretation of earlier names is taken as the sense meant by the original author. Think these used to be "apud" and are now "ex" although a colon has also been used. There are only a few sanctioning authors, the main one being Elias Fries.(Fr.) )

==More than binominals==

===Authority===
'''''Pica pica'' Linnaeus, (1758)''' on [http://en.wikipedia.org/wiki/European_Magpie Wikipedia: European Magpie]
:(i.e. named by Linnaeus in 1758)

===Unspecified species===
'''''Podiceps sp.''''' on [http://www.birdlife.org/datazone/species/index.html?action=SpcHTMDetails.asp&sid=3644&m=0 Bird Life] <pre><nowiki>Podiceps sp.</nowiki></pre>

'''Psyllid plant hopper''' [http://ramblingsofanaturalist.blogspot.com/2006/07/bay-sucker-gall-trioza-alacris.html on Ramblings of a Naturalist blog]

===Sub-species===

====Animal====
'''''Larus glaucoides kumlieni''' on [http://www.birdguides.com/html/vidlib/species/Larus_glaucoides_kumlieni.htm BirdGuides]

'''Kumlien's Gull''' on [http://www.birdsireland.com/pages/rare_bird_news/2005/january_photos.html Birds Ireland]

====Plant====
'''''Pisum sativum L. subsp. sativum''''' on [http://www.plantnames.unimelb.edu.au/Sorting/Pisum.html] (also has other examples; note lack of required italics)
<pre><nowiki>Pisum sativum L. subsp. sativum</nowiki></pre>

===Cultivars (plant)===
'''''Chamaecyparis lawsoniana 'Aureomarginata'''''' on [http://en.wikipedia.org/wiki/Cultivar Wikipedia: Cultivar]

<pre><nowiki><dd>Chamaecyparis lawsoniana 'Aureomarginata'</dd></nowiki></pre>

'''''Chamaecyparis lawsoniana'' 'Golden Wonder'''' on [http://www.plantago.nl/plantindex/c/Chamaecyparis/Chamaecyparis_4.htm plantago.nl]

====Cultivar groups (plant)====
'''''Brassica oleracea'' Botrytis Group''' on [http://en.wikipedia.org/wiki/Cultivar Wikipedia: Cultivar]

===Trade names (plant)===

'''''Rosa'' Peace''' on [http://en.wikipedia.org/wiki/Cultivar Wikipedia: Cultivar]
:("Peace" is a trade designation or "selling name" for the cultivar R. 'Madame A. Meilland' and should therefore be printed in a different typeface from the rest of the name, without any quote marks)

'''Sunflower 'Giant Single'''' on [http://cgi.www.johnsons-seeds.com/cgi-bin/www.johnsons-seeds.com/detail/azlist/S-1 Johnsons Seeds]

'''Sunflower 'Infrared' F1''' on [http://cgi.www.johnsons-seeds.com/cgi-bin/www.johnsons-seeds.com/detail/azlist/S-1 Johnsons Seeds]
:(Note "F1" cross designation)

===Variety (plant)===
'''''Pisum sativum var. macrocarpon''''' on [http://davesgarden.com/pf/go/8/index.html Dave's Garden]

====Sub-variety (plant)====

'''''Betula ermani var. genuina subvar. brevidentata''''' on [http://www.nccpg.com/gloucestershire/wilson1.html National Council for the Conservation of Plants and Gardens, Gloucestershire Group] (plus many other examples)

===Form (plant)===

'''''Acanthocalycium spiniflorum f. klimpelianum''''' on [http://en.wikipedia.org/wiki/Form_%28botany%29 Wikipedia: form (botany)]
*aka '''''Acanthocalycium spiniflorum forma klimpelianum'''''

===Sense (plant)===
'''''Ranunculus aquatilis s.l.''''' and '''''R. aquatilis s.s'''''; on [http://www.westmidlandbirdclub.com/blithfield/plants20060815.htm Blithfield Reservoir: Survey of Flowering Plants...] (see also footnotes on that page)

===Cross (plant)===
'''''Digitalis x mertonensis''''' on [http://www.hortax.org.uk/gardenplantsnames.html Hortax]
:The hybrid name for all plants derived from the cross between '''D. purpurea''' and '''D. grandiflora'''. The "x" indicates the hybrid status.

'''''× Fatshedera lizei''''' on [http://oregonstate.edu/dept/ldplants/sci-names.htm Scientific Plant Names, Oregon State Univ., Landscape Plants]

===Strain (bacteria)===
'''''Escherichia coli O157:H7''''' on [http://www.cfsan.fda.gov/~mow/chap15.html FDA.gov]

'''''E.Coli''''' on [http://news.bbc.co.uk/1/hi/england/southern_counties/5346842.stm BBC news]

==Misc==
===Superseded names===
'''''Tringa bartramia''''' superseded by '''''Bartramia longicauda''''' on [http://www.westmidlandbirdclub.com/firsts/UPLSA.htm West Midland Bird Club's Upland Sandpiper article]

===GUID===
'''NBN Taxon Key''' for European Otter, ''Lutra lutra'', on [http://nbn.nhm.ac.uk/nhm/bin/nbntaxa.dll/taxon_details?taxon_key=NBNSYS0000005133 NBN Species Dictionary]: '''NBNSYS0000005133'''

'''LSID ([http://lsid.sourceforge.net/#whatislsid Life Science Indicator])''' for ''Popillia japonica'' on [http://names.ubio.org/browser/details2.php?names=on&authors=on&sci=on&vern=on&conceptID=&expand=&namebankID=3377001 uBio]: '''urn:lsid:ubio.org:namebank:3377001'''

===Wikipedia===
'''Black-tailed Godwit''' on [http://en.wikipedia.org/wiki/Black-tailed_Godwit Wikipedia: Black-tailed Godwit]

Wikipedia uses several sets of markup, e.g. (in-line styles and links, plus some other markup, removed, for clarity):

<pre><nowiki>The Black-tailed Godwit, Limosa limosa</nowiki></pre>

and:

<pre><nowiki>
<tr>
<td>Kingdom:</td>
<td>Animalia</td>
</tr>
<tr>
<td>Phylum:</td>
<td>Chordata</td>
</tr>
<tr>
<td>Class:</td>
<td>Aves</td>
</tr>
<tr>
<td>Order:</td>
<td>Charadriiformes</td>
</tr>
<tr>
<td>Family:</td>
<td>Scolopacidae</td>
</tr>
<tr>
<td>Genus:</td>
<td>Limosa</td>
</tr>
<tr>
<td>Species:</td>
<td>L. limosa</td>
</tr>

<tr>
<th>binominal name</th>
</tr>
<tr>
<td>Limosa limosa
<td>(Linnaeus, 1758)</td>
</tr>
</nowiki></pre>

==Quantitative evidence==

For evidence of quantitative, rather than qualitative, use of species' and other taxonomic names, see [http://microformats.org/discuss/mail/microformats-discuss/2006-September/005790.html] and [http://microformats.org/discuss/mail/microformats-discuss/2006-September/005791.html]. Furthermore:

*Wikipedia:
** '''All''' species articles, e.g. [http://en.wikipedia.org/wiki/Little_Ringed_Plover Little Ringed Plover] (see [[species-examples#Wikipedia|above]])
** '''All''' genera articles, e.g. [http://en.wikipedia.org/wiki/Plover Charadrius (Plover)]
** '''All''' higher classes, e.g. [http://en.wikipedia.org/wiki/Charadriidae Charadriidae]
** '''All''' regional lists, e.g. [http://en.wikipedia.org/wiki/List_of_British_birds:_non-passerines List of British birds]
** '''All''' dedicatees, e.g. [http://en.wikipedia.org/wiki/Alexander_Wilson Alexander Wilson]
** '''All''' authorities, e.g. [http://en.wikipedia.org/wiki/Giovanni_Antonio_Scopoli Giovanni Antonio Scopoli]
** '''All''' images of living things, e.g. [http://en.wikipedia.org/wiki/Image:Charadrius_dubius_4_%28Marek_Szczepanek%29.jpg Charadrius dubius 4 (Marek Szczepanek).jpg]
** Many reserves, lakes, and other places of interest, e.g. [http://en.wikipedia.org/wiki/Belvide Belvide]
** Many biological authors and illustrators, e.g. [http://en.wikipedia.org/wiki/John_Audubon John Audubon]; [http://en.wikipedia.org/wiki/Gilbert_White Gilbert White]
** Random articles on other topics, e.g. [http://en.wikipedia.org/wiki/Balancing_lake Balancing lake}]
** '''All the above, again''', for each alternative language e.g. [http://cy.wikipedia.org/wiki/Cwtiad_Torchog_Bach Welsh]; [http://fr.wikipedia.org/wiki/Petit_gravelot French]; [http://zh.wikipedia.org/wiki/%E9%87%91%E7%9C%B6%E9%B8%BB Chinese]

*Wikimedia Commons
** '''All''' species indexes, e.g. [http://commons.wikimedia.org/wiki/Charadrius_dubius Charadrius dubius]
** '''Each individual''' image, e.g. [http://commons.wikimedia.org/wiki/Image:Charadrius_dubius_1_%28Marek_Szczepanek%29.jpg Charadrius dubius 1 (Marek Szczepanek).jpg]
** '''Each family''' list [http://commons.wikimedia.org/wiki/Charadriidae Charadriidae]

*Wiktionary
** '''All''' species articles, e.g. [http://en.wiktionary.org/wiki/american_golden_plover American Golden Plover]
** '''All''' family articles, e.g. [http://en.wiktionary.org/wiki/plover Plover]
** '''Many of the above, in other langauges''' e.g. [http://en.wiktionary.org/wiki/aquila_reale Italian]; [http://en.wiktionary.org/wiki/%D0%B1%D0%B5%D1%80%D0%BA%D1%83%D1%82 Russian]

*Wikispecies
** '''Every''' speices, e.g. [http://species.wikimedia.org/wiki/Charadrius_dubius Charadrius dubius]
** '''Every''' genus, e.g. [http://species.wikimedia.org/wiki/Charadrius Charadrius]
** '''Every''' sub-family, e.g. [http://species.wikimedia.org/wiki/Charadriinae Charadriinae]
** '''Every''' family, e.g. [http://species.wikimedia.org/wiki/Charadriidae Charadriidae]
** and so on, for '''every other rank'''
** '''Every''' image (e.g. [http://species.wikimedia.org/wiki/Image:Charadrius_hiaticula_He.jpg Charadrius hiaticula He.jpg]

*Google
**[http://www.google.co.uk/search?hl=en&hs=dBU&client=firefox-a&rls=org.mozilla:en-US:official&sa=X&oi=spell&resnum=0&ct=result&cd=1&q=%22E+coli%22&spell=1 Google finds about '''37,600,000''' for "E coli"].
***[http://www.google.co.uk/search?hs=Apo&hl=en&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&q=%22Escherichia+coli%22&btnG=Search&meta= Google finds about '''19,500,000''' for "Escherichia coli"]
***[http://www.google.co.uk/search?hs=zqo&hl=en&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&q=%22Ecoli%22&btnG=Search&meta= Google finds about '''722,000''' for "Ecoli"].
**[http://www.google.co.uk/search?hs=vWC&hl=en&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&q=%22Homo+sapiens%22&btnG=Search&meta= Google finds about '''14,200,000''' for "Homo sapiens"]
***[http://www.google.co.uk/search?hs=vWC&hl=en&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&q=%22Homo+sapien%22+-sapiens&btnG=Search&meta= Google finds about '''273,000''' for the mis-spelling "Homo sapien" -sapiens.]
**[http://www.google.co.uk/search?q=%22%22Homo+erectus%22%22&start=0&ie=utf-8&oe=utf-8&client=firefox-a&rls=org.mozilla:en-US:official Google finds about '''1,260,000''' for ""Homo erectus"]
**[http://www.google.com/search?svnum=10&as_scoring=r&hl=en&edition=us&as_drrb=q&as_qdr=&as_mind=1&as_minm=9&as_maxd=1&as_maxm=10&q=%22Clostridium+difficile%22&ie=UTF-8&sa=N&tab=nw Google finds about '''1,380,000''' for "Clostridium difficile"].
**[http://www.google.com/search?hl=en&lr=&edition=us&q=%22Passer+domesticus%22&btnG=Search Google finds about '''841,000''' for "Passer domesticus"].
***[http://images.google.com/images?hl=en&lr=&edition=us&q=%22Passer%20domesticus%22&btnG=Search&sa=N&tab=wi Google images finds about '''3,140''' for "Passer domesticus"].
**[http://www.google.co.uk/search?hl=en&hs=oEU&client=firefox-a&rls=org.mozilla:en-US:official&sa=X&oi=spell&resnum=0&ct=result&cd=1&q=%22Acer+palmatum%22&spell=1 Google finds about '''602,000''' for "Acer palmatum"]
** At the time of writing, '''every single one''' of the first 20 [http://www.google.com/search?q=%22Noctule+bat%22 Google results for "Noctule Bat"] also includes the scientific name ''Nyctalus noctula''.

*[http://www.arkive.org/ ARKive] - '''2000''' species ("It is ARKive's current aim to compile audio-visual records, where such media exists, for the 15,000-plus species currently threatened with extinction, according to the World Conservation Union's (IUCN) Red List of Threatened Species.")

*[http://www.rhs.org.uk/rhsplantfinder/plantfinder.asp Royal Horticultural Society - RHS Plant Finder] - '''70,000''' plants

*[http://www.bacterio.net List of Prokaryotic Names (formerly List of Bacterial Names)] - 2,032 *files*; '''10,268''' published names (to 2006-09-07)

*[http://nbn.nhm.ac.uk/nhm/ UK National Biodiversity Network's Species Dictionary]

*[http://www.searchnbn.net/ UK National Biodiversity Network Gateway] - '''20 million+''' species records

*[http://www.sp2000.org/ Species 2000] - '''450,000 species'''

*[http://www.bioimages.org.uk/index.html BioImages - Virtual Fieldguide] - '''53,000''' images depicting 4,600 species (see [[species-brainstorming#Malcolm_Storey|Wiki comments from site owner]])

*[http://animaldiversity.ummz.umich.edu/ Animal Diversity Web] - "'''Thousands''' of species accounts ['''plus'''] descriptions of levels of organization above the species level, especially phyla, classes, and in some cases, orders and families. Hundreds of hyperlinked pages and images illustrate the traits and general biology of these groups"

* [http://www.ubio.org/index.php?pagename=home uBio]
**NameBank is a repository of '''millions''' of recorded biological names and facts that link those names together.
**ClassificationBank stores multiple classifications and taxonomic concepts that are the result of expert opinions. It extends the functionality of NameBank.

*[http://www.birdlife.org/datazone/species/ BirdLife International] - all birds of the world (~'''10,000''')

*[http://bugguide.net/ Bug Guide] - all insects, spiders, and allies, of the USA and Canada (most with more than one page).
** e.g. [http://bugguide.net/node/view/70875 Arge pectoralis - Birch Sawfly]

*[http://www.bto.org/birdtrack/ BirdTrack]
**[http://blx1.bto.org/bt-dailyresults/results/s171-20-06.html Lapwing]

*[http://www.discoverlife.org/ Discover Life] - "contains '''306,553''' species. The Polistes Foundation and its scientific partners plan to add high-quality identification guides, maps, images, and text for '''a million species''' by 2012. [...] Each month Discover Life serves approximately 3 million pages and images to 70,000 IP addresses"

*[http://www.record-lrc.co.uk/ rECOrd] (the Local Biological Records Centre serving the Cheshire region of England) - '''1.6 million''' species records available online for the public to search and map

===Planned sites===
*[http://herbariaunited.org/atHome/ Herbaria United] (part of The website of the Botanical Collection Managers Group (BCMG), a specialist group of the Linnean Society of London) - "The UK has the world's largest and oldest collections of herbarium specimens held in trust by museums and universities. A new project is just getting underway to put all this online."

==Notable websites==
These high-profile websites use species names

*Amazon
**[http://www.amazon.co.uk/s/?url=search-alias%3Daps&field-keywords=%22house+sparrow%22 search for "House Sparrow"]

*BBC News
**[http://news.bbc.co.uk/1/hi/uk/4835208.stm Fewer birds spotted in UK gardens]
**[http://news.bbc.co.uk/1/hi/england/london/4743250.stm Study to solve sparrow's decline riddle]

*Encyclopaedia Britannica - all species, e.g.
**[http://concise.britannica.com/ebc/article-9379473/starling Starling]

*Flickr
**[http://www.flickr.com/photos/tags/citheronia/ Tag for moth genera 'citheronia']
***[http://www.flickr.com/photos/30268343@N00/152101772/ Sample result from that search]
**[http://www.flickr.com/groups/birdguide/ Field Guide: Birds of the World] 23,073 tagged photos, as at 2006-10-21

*CNN
**[http://archives.cnn.com/2001/NATURE/01/24/dying.eagles/ Disease threatens bald eagle population]

*eBay
**[http://search.ebay.com/house-sparrow search for "House Sparrow"]

*The Guardian
**[http://environment.guardian.co.uk/conservation/story/0,,1878956,00.html The call of the wildlife]
**[http://education.guardian.co.uk/higher/news/story/0,,1665396,00.html Sparrow joins 'raped' duck in Dutch museum] (note improper capitalisation "''passer domesticus''")

*London Zoo
**[http://www.zsl.org/london-zoo/animals/birds/tawny-frogmouth,99,AN.html Tawny frogmouth]

*Microsoft
**[http://www.microsoft.com/games/zootycoon/zoo2/zoo2_ymi_animals1.asp Zoo Tycoon]

*MSN-Encarta - all species, e.g.
**[http://encarta.msn.com/encnet/refpages/search.aspx?q=vulgaris&Submit2=Go Search for "vulgaris"]

*MySpace
**[http://blog.myspace.com/index.cfm?fuseaction=blog.view&friendID=47134278&blogID=79591637]

*Nature
**[http://www.nature.com/nature/focus/avianflu/index.html Avian flu web focus]

*Nature Network, Boston
**[http://network.nature.com/boston/news/archive/2006/06/13/the-student-and-the-squid The student and the squid] '''N.B.''' site already supports rel-tag, hCard for user profiles and hCalendar for marking up events across the site.

*NASA
**[http://history.nasa.gov/SP-401/ch3.htm SP-401 Skylab, Classroom in Space. Part II - Student Experiments] ("The common Cross spider (Araneus diadematus)")

*New York Times
**[http://query.nytimes.com/gst/fullpage.html?sec=travel&res=9D04E4DE1131F93BA25751C0A9669C8B63 Where the Eagles Fly: Seeing the National Symbol]

*Snopes (Urban Legends Reference Pages)
**[http://www.snopes.com/photos/animals/fishfly.asp Fish Fly]

*United Kingdom Government
**[http://www.defra.gov.uk/wildlife-countryside/vertebrates/gen-licence.htm DEFRA: General licences under the Wildlife & Countryside Act 1981]

*United States of America Government
**ITIS, e.g. [http://www.itis.usda.gov/servlet/SingleRpt/SingleRpt?search_topic=TSN&search_value=179628 Passer Domesticus] - "authoritative taxonomic information on plants, animals, fungi, and microbes of North America and the world"

*W3C
**[http://dev.w3.org/cvsweb/2000/10/swap/test/ferrell/biology.n3?rev=1.4 An Ontology of Biology]
**[http://esw.w3.org/topic/HCLSIG_BioRDF_Subgroup/Tasks/Reagents/Status_Reports/2006-05-04 BioRDF Sub-group Status Report, 4 May 2006]

*Yahoo Groups
**[http://tech.groups.yahoo.com/group/passerdomesticus/ passerdomesticus] species as group name!

==Breaking news==
*[http://news.bbc.co.uk/1/shared/spl/hi/pop_ups/06/sci_nat_orchid_spectacular/html/1.stm BBC News: Stunning new orchids from Asia's rainforest] - 2006-10-16
*[http://news.bbc.co.uk/1/hi/sci/tech/6045802.stm BBC News: Winter home find cheers twitchers] (winter home of the northern bald ibis found) - 2006-10-13
*[http://news.bbc.co.uk/1/hi/sci/tech/6043648.stm BBC News: New mouse find is 'living fossil'] - 2006-10-12
*[http://news.bbc.co.uk/1/hi/sci/tech/6035113.stm BBC News: Giant camel fossil found in Syria] - 2006-10-10
*[http://news.bbc.co.uk/1/hi/sci/tech/5414410.stm BBC News: Sharks swim into political waters] - 2006-10-06
*[http://news.bbc.co.uk/1/hi/sci/tech/5403570.stm BBC News: 'Monster' fossil find in Arctic] - 2006-10-05

==Use in blogs==
*[http://technorati.com/search/%22passer%20domesticus%22 Technorati search for "Passer domesticus"] (367 found, as at 2006-09-25)
*[http://technorati.com/search/%22acer%20palmatum%22 Technorati search for "Acer palmatum"] (682 found, as at 2006-09-25)
*[http://technorati.com/search/%22Homo%20sapiens%22 Technorati search for "Homo sapiens"] (40,932 found, as at 2006-09-25)
*[http://technorati.com/search/birding Technorati search for "birding"] (26,472 found, as at 2006-09-25)
*[http://ramblingsofanaturalist.blogspot.com/ Ramblings of a Naturalist]
*[http://squaremetre1.blogspot.com/ The Square Metre]
*[http://windowboxwildlife.blogspot.com/index.html Windowbox Wildlife]
*[http://www.rxwildlife.org.uk/ RXWildlife]

==And finally...==
Gary Larson, in his book ''The Far Side Gallery'' (Warner Books, 1980, ISBN 0751502367) has a cartoon, showing two entomologists sitting down to eat dinner in a jungle. One says to the other "Hey! What's this ''Drosophila melanogaster'' doing in my soup?"

==Contributors==
*[[User:AndyMabbett|Andy Mabbett]] (proponent)
*Malcolm Storey (per e-mail)
*[[User:SXBRC|Charles Roper]], [http://www.sxbrc.org.uk/ Sussex Biodiversity Record Centre] (proponent)
*[[User:SteveMcBill|Steve McWilliam]], [http://www.rECOrd-LRC.co.uk/ rECOrd - The Biodiversity Information System for the Cheshire region] (proponent)

==See also==
[[species-brainstorming]]

species-examples

2006-10-22T04:10:35Z

BenWest: started group by publishers section

=Species Examples=

Examples of common and scientific names of living things, which could be marked up with a "'''[[species]]'''" (or similar) microformat. Note use of matching pairs of examples, where possible.

__TOC__

== Grouped By Publisher ==

=== West Midland Bird Club ===
* [http://www.westmidlandbirdclub.com/ladywalk/latest.htm Black-tailed Godwit]
<pre><nowiki>Black-tailed Godwit</nowiki></pre>

* [http://www.westmidlandbirdclub.com/records/lists.htm Limosa limosa ]
<pre><nowiki><td>Limosa limosa</td></nowiki></pre>

=== species.mediawiki.org ===
[http://species.wikimedia.org/wiki/Charadrius_dubius species.mediawiki.org media bird ] .
<pre><nowiki>
<dd>Regnum: <a href="/wiki/Animalia" title="Animalia">Animalia</a> (Metazoa)
<dl>
<dd>Subregnum: <a href="/wiki/Eumetazoa" title="Eumetazoa">Eumetazoa</a>
<dl>
<dd>Superphylum: Bilateria: <a href="/wiki/Deuterostomia" title="Deuterostomia">Deuterostomia</a>
<dl>
<dd>Phylum: <a href="/wiki/Chordata" title="Chordata">Chordata</a>
<dl>

<dd>Subphylum: <a href="/wiki/Vertebrata" title="Vertebrata">Vertebrata</a>
<dl>
<dd>Classis: <a href="/wiki/Aves" title="Aves">Aves</a>
<dl>
<dd>Subclassis: <a href="/wiki/Neognathae" title="Neognathae">Neognathae</a>
<dl>
<dd>Ordo: <a href="/wiki/Charadriiformes" title="Charadriiformes">Charadriiformes</a>
<dl>
<dd>Subordo: <a href="/wiki/Charadrii" title="Charadrii">Charadrii</a>

<dl>
<dd>Familia: <a href="/wiki/Charadriidae" title="Charadriidae">Charadriidae</a>
<dl>
<dd>Subfamily: <a href="/wiki/Charadriinae" title="Charadriinae">Charadriinae</a>
<dl>
<dd>Genus: <a href="/wiki/Charadrius" title="Charadrius">Charadrius</a>
<dl>
<dd>Species: Charadrius dubius
<dl>

<dd>Subspecies: <a href="/w/index.php?title=Charadrius_dubius_curonicus&action=edit" class="new" title="Charadrius dubius curonicus">C. d. curonicus</a> - <a href="/w/index.php?title=Charadrius_dubius_dubius&action=edit" class="new" title="Charadrius dubius dubius">C. d. dubius</a> - <a href="/w/index.php?title=Charadrius_dubius_jerdoni&action=edit" class="new" title="Charadrius dubius jerdoni">C. d. jerdoni</a> - <a href="/w/index.php?title=Charadrius_dubius_papuanus&action=edit" class="new" title="Charadrius dubius papuanus">C. d. papuanus</a></dd>

...
</nowiki>
</pre>

* Comments
** This feels similar to tagging to me. This particular example has a resolves the whole heirarchy, correct? [[User:BenWest|BenWest]] 17:57, 21 Oct 2006 (PDT)

== Alternative Grouping By Strategy ==
I'd like to regroup these examples... perhaps by publishing strategy instead of a list of what is being published. Should this be available as an alternate grouping section? In the mean time, a grouping by publisher would help analysis go smoother. [[User:BenWest|BenWest]] 17:57, 21 Oct 2006 (PDT)

I looked at several examples. Several of them feel like tagging to me. Should we attempt to note what level or resolution is available in each example?

=== Tagging ===
The [[http://species.wikimedia.org/wiki/Charadrius_dubius wiki media bird example]] is particularly interesting.
<pre><nowiki>
<dd>Regnum: <a href="/wiki/Animalia" title="Animalia">Animalia</a> (Metazoa)
<dl>
<dd>Subregnum: <a href="/wiki/Eumetazoa" title="Eumetazoa">Eumetazoa</a>
<dl>
<dd>Superphylum: Bilateria: <a href="/wiki/Deuterostomia" title="Deuterostomia">Deuterostomia</a>
<dl>
<dd>Phylum: <a href="/wiki/Chordata" title="Chordata">Chordata</a>
<dl>

<dd>Subphylum: <a href="/wiki/Vertebrata" title="Vertebrata">Vertebrata</a>
<dl>
<dd>Classis: <a href="/wiki/Aves" title="Aves">Aves</a>
<dl>
<dd>Subclassis: <a href="/wiki/Neognathae" title="Neognathae">Neognathae</a>
<dl>
<dd>Ordo: <a href="/wiki/Charadriiformes" title="Charadriiformes">Charadriiformes</a>
<dl>
<dd>Subordo: <a href="/wiki/Charadrii" title="Charadrii">Charadrii</a>

<dl>
<dd>Familia: <a href="/wiki/Charadriidae" title="Charadriidae">Charadriidae</a>
<dl>
<dd>Subfamily: <a href="/wiki/Charadriinae" title="Charadriinae">Charadriinae</a>
<dl>
<dd>Genus: <a href="/wiki/Charadrius" title="Charadrius">Charadrius</a>
<dl>
<dd>Species: Charadrius dubius
<dl>

<dd>Subspecies: <a href="/w/index.php?title=Charadrius_dubius_curonicus&action=edit" class="new" title="Charadrius dubius curonicus">C. d. curonicus</a> - <a href="/w/index.php?title=Charadrius_dubius_dubius&action=edit" class="new" title="Charadrius dubius dubius">C. d. dubius</a> - <a href="/w/index.php?title=Charadrius_dubius_jerdoni&action=edit" class="new" title="Charadrius dubius jerdoni">C. d. jerdoni</a> - <a href="/w/index.php?title=Charadrius_dubius_papuanus&action=edit" class="new" title="Charadrius dubius papuanus">C. d. papuanus</a></dd>

...
</nowiki>
</pre>
This feels similar to tagging to me. This particular example has a resolves the whole heirarchy, correct? [[User:BenWest|BenWest]] 17:57, 21 Oct 2006 (PDT)

==binominals==

===Birds===

'''Black-tailed Godwit''' on [http://www.westmidlandbirdclub.com/ladywalk/latest.htm West Midland Bird Club's Ladywalk reserve latest news page]

<pre><nowiki>Black-tailed Godwit</nowiki></pre>

'''''Limosa limosa''''' on [http://www.westmidlandbirdclub.com/records/lists.htm West Midland Bird Club's county lists']

<pre><nowiki><td>Limosa limosa</td></nowiki></pre>

===Mammal===
'''Wolf''' on [http://www.wolf.org/wolves/index.asp International Wolf Center]

===Fish===
'''Northern pike''' on [http://www.dnr.state.mn.us/fish/northern/index.html Minnesota Department of Natural Resources]

'''''Esox lucius''''' on [http://www.pikezander.co.uk/pike.htm Pike & Zander]

===Insect===
'''Death’s Head Hawkmoth''' on [http://funkman.org/animal/insect/deathheadmoth.html Animal Teachers]

'''''Acherontia atropos''''' on [http://ukmoths.org.uk/show.php?id=2540 UK Moths]

'''Migrant Hawker''' (''Aeshna mixta'') on [http://www.sxbrc.org.uk/news/friston-forest-recording-day Sussex Biodiversity Record Centre]

'''Sloe Bug''' (''Dolycoris baccarum'') on [http://www.record-lrc.co.uk/?Mod=Forum&Do=ViewThread&ForumID=31&ThreadID=101 rECOrd - The Biodiversity Information Centre for the Cheshire region]

===Arachnid===
'''Tarantulas''' on [http://www.nature.com/news/2006/060925/full/060925-6.html Nature.com]

'''Costa Rican zebra tarantula''' (''Aphonopelma seemanni'') on [http://www.nature.com/news/2006/060925/full/060925-6.html Nature.com]

'''''Araneus angulatus''''' on [http://www.sxbrc.org.uk/news/friston-forest-recording-day Sussex Biodiversity Record Centre]

===Plant===
'''Bog Pimpernel''' on [http://www.map-reading.co.uk/wildflowers/HTML%20files/f0219.htm Map Reading's Wildflower Images]

'''''Anagallis tenella''''' on [http://www.bioimages.org.uk/HTML/T47624.HTM BioImages]

'''''Persicaria campanulatum''''' on [http://www.record-lrc.co.uk/?Mod=Forum&Do=ViewThread&ForumID=6&ThreadID=75 rECOrd - The Biodiversity Information Centre for the Cheshire region]

===Fungi===

'''''Amanita muscaria''''' on [http://www.mykoweb.com/CAF/species/Amanita_muscaria.html California Fungi]
* as '''''Amanita muscaria'' (L. per Fr.) Hooker'''
* as '''''Amanita muscaria var. flavivolvata'''''

'''Fly Agaric''' on [http://www.treesforlife.org.uk/forest/mythfolk/flyagaric.html Trees for Life]

'''''Rhodocollybia maculata'' (Albertini & Schweinitz: Fries) Singer''' on [http://www.ilmyco.gen.chicago.il.us/Taxa/Rhodomacul540.html]
*also written as '''''Rhodocollybia maculata'' (Albertini & Schweinitz ex Fries) Singer'''
*(This is where a post-Linnean author is given special rights (because his descriptions were comparatively complete - i.e. recognisable) so his interpretation of earlier names is taken as the sense meant by the original author. Think these used to be "apud" and are now "ex" although a colon has also been used. There are only a few sanctioning authors, the main one being Elias Fries.(Fr.) )

==More than binominals==

===Authority===
'''''Pica pica'' Linnaeus, (1758)''' on [http://en.wikipedia.org/wiki/European_Magpie Wikipedia: European Magpie]
:(i.e. named by Linnaeus in 1758)

===Unspecified species===
'''''Podiceps sp.''''' on [http://www.birdlife.org/datazone/species/index.html?action=SpcHTMDetails.asp&sid=3644&m=0 Bird Life] <pre><nowiki>Podiceps sp.</nowiki></pre>

'''Psyllid plant hopper''' [http://ramblingsofanaturalist.blogspot.com/2006/07/bay-sucker-gall-trioza-alacris.html on Ramblings of a Naturalist blog]

===Sub-species===

====Animal====
'''''Larus glaucoides kumlieni''' on [http://www.birdguides.com/html/vidlib/species/Larus_glaucoides_kumlieni.htm BirdGuides]

'''Kumlien's Gull''' on [http://www.birdsireland.com/pages/rare_bird_news/2005/january_photos.html Birds Ireland]

====Plant====
'''''Pisum sativum L. subsp. sativum''''' on [http://www.plantnames.unimelb.edu.au/Sorting/Pisum.html] (also has other examples; note lack of required italics)
<pre><nowiki>Pisum sativum L. subsp. sativum</nowiki></pre>

===Cultivars (plant)===
'''''Chamaecyparis lawsoniana 'Aureomarginata'''''' on [http://en.wikipedia.org/wiki/Cultivar Wikipedia: Cultivar]

<pre><nowiki><dd>Chamaecyparis lawsoniana 'Aureomarginata'</dd></nowiki></pre>

'''''Chamaecyparis lawsoniana'' 'Golden Wonder'''' on [http://www.plantago.nl/plantindex/c/Chamaecyparis/Chamaecyparis_4.htm plantago.nl]

====Cultivar groups (plant)====
'''''Brassica oleracea'' Botrytis Group''' on [http://en.wikipedia.org/wiki/Cultivar Wikipedia: Cultivar]

===Trade names (plant)===

'''''Rosa'' Peace''' on [http://en.wikipedia.org/wiki/Cultivar Wikipedia: Cultivar]
:("Peace" is a trade designation or "selling name" for the cultivar R. 'Madame A. Meilland' and should therefore be printed in a different typeface from the rest of the name, without any quote marks)

'''Sunflower 'Giant Single'''' on [http://cgi.www.johnsons-seeds.com/cgi-bin/www.johnsons-seeds.com/detail/azlist/S-1 Johnsons Seeds]

'''Sunflower 'Infrared' F1''' on [http://cgi.www.johnsons-seeds.com/cgi-bin/www.johnsons-seeds.com/detail/azlist/S-1 Johnsons Seeds]
:(Note "F1" cross designation)

===Variety (plant)===
'''''Pisum sativum var. macrocarpon''''' on [http://davesgarden.com/pf/go/8/index.html Dave's Garden]

====Sub-variety (plant)====

'''''Betula ermani var. genuina subvar. brevidentata''''' on [http://www.nccpg.com/gloucestershire/wilson1.html National Council for the Conservation of Plants and Gardens, Gloucestershire Group] (plus many other examples)

===Form (plant)===

'''''Acanthocalycium spiniflorum f. klimpelianum''''' on [http://en.wikipedia.org/wiki/Form_%28botany%29 Wikipedia: form (botany)]
*aka '''''Acanthocalycium spiniflorum forma klimpelianum'''''

===Sense (plant)===
'''''Ranunculus aquatilis s.l.''''' and '''''R. aquatilis s.s'''''; on [http://www.westmidlandbirdclub.com/blithfield/plants20060815.htm Blithfield Reservoir: Survey of Flowering Plants...] (see also footnotes on that page)

===Cross (plant)===
'''''Digitalis x mertonensis''''' on [http://www.hortax.org.uk/gardenplantsnames.html Hortax]
:The hybrid name for all plants derived from the cross between '''D. purpurea''' and '''D. grandiflora'''. The "x" indicates the hybrid status.

'''''× Fatshedera lizei''''' on [http://oregonstate.edu/dept/ldplants/sci-names.htm Scientific Plant Names, Oregon State Univ., Landscape Plants]

===Strain (bacteria)===
'''''Escherichia coli O157:H7''''' on [http://www.cfsan.fda.gov/~mow/chap15.html FDA.gov]

'''''E.Coli''''' on [http://news.bbc.co.uk/1/hi/england/southern_counties/5346842.stm BBC news]

==Misc==
===Superseded names===
'''''Tringa bartramia''''' superseded by '''''Bartramia longicauda''''' on [http://www.westmidlandbirdclub.com/firsts/UPLSA.htm West Midland Bird Club's Upland Sandpiper article]

===GUID===
'''NBN Taxon Key''' for European Otter, ''Lutra lutra'', on [http://nbn.nhm.ac.uk/nhm/bin/nbntaxa.dll/taxon_details?taxon_key=NBNSYS0000005133 NBN Species Dictionary]: '''NBNSYS0000005133'''

'''LSID ([http://lsid.sourceforge.net/#whatislsid Life Science Indicator])''' for ''Popillia japonica'' on [http://names.ubio.org/browser/details2.php?names=on&authors=on&sci=on&vern=on&conceptID=&expand=&namebankID=3377001 uBio]: '''urn:lsid:ubio.org:namebank:3377001'''

===Wikipedia===
'''Black-tailed Godwit''' on [http://en.wikipedia.org/wiki/Black-tailed_Godwit Wikipedia: Black-tailed Godwit]

Wikipedia uses several sets of markup, e.g. (in-line styles and links, plus some other markup, removed, for clarity):

<pre><nowiki>The Black-tailed Godwit, Limosa limosa</nowiki></pre>

and:

<pre><nowiki>
<tr>
<td>Kingdom:</td>
<td>Animalia</td>
</tr>
<tr>
<td>Phylum:</td>
<td>Chordata</td>
</tr>
<tr>
<td>Class:</td>
<td>Aves</td>
</tr>
<tr>
<td>Order:</td>
<td>Charadriiformes</td>
</tr>
<tr>
<td>Family:</td>
<td>Scolopacidae</td>
</tr>
<tr>
<td>Genus:</td>
<td>Limosa</td>
</tr>
<tr>
<td>Species:</td>
<td>L. limosa</td>
</tr>

<tr>
<th>binominal name</th>
</tr>
<tr>
<td>Limosa limosa
<td>(Linnaeus, 1758)</td>
</tr>
</nowiki></pre>

==Quantitative evidence==

For evidence of quantitative, rather than qualitative, use of species' and other taxonomic names, see [http://microformats.org/discuss/mail/microformats-discuss/2006-September/005790.html] and [http://microformats.org/discuss/mail/microformats-discuss/2006-September/005791.html]. Furthermore:

*Wikipedia:
** '''All''' species articles, e.g. [http://en.wikipedia.org/wiki/Little_Ringed_Plover Little Ringed Plover] (see [[species-examples#Wikipedia|above]])
** '''All''' genera articles, e.g. [http://en.wikipedia.org/wiki/Plover Charadrius (Plover)]
** '''All''' higher classes, e.g. [http://en.wikipedia.org/wiki/Charadriidae Charadriidae]
** '''All''' regional lists, e.g. [http://en.wikipedia.org/wiki/List_of_British_birds:_non-passerines List of British birds]
** '''All''' dedicatees, e.g. [http://en.wikipedia.org/wiki/Alexander_Wilson Alexander Wilson]
** '''All''' authorities, e.g. [http://en.wikipedia.org/wiki/Giovanni_Antonio_Scopoli Giovanni Antonio Scopoli]
** '''All''' images of living things, e.g. [http://en.wikipedia.org/wiki/Image:Charadrius_dubius_4_%28Marek_Szczepanek%29.jpg Charadrius dubius 4 (Marek Szczepanek).jpg]
** Many reserves, lakes, and other places of interest, e.g. [http://en.wikipedia.org/wiki/Belvide Belvide]
** Many biological authors and illustrators, e.g. [http://en.wikipedia.org/wiki/John_Audubon John Audubon]; [http://en.wikipedia.org/wiki/Gilbert_White Gilbert White]
** Random articles on other topics, e.g. [http://en.wikipedia.org/wiki/Balancing_lake Balancing lake}]
** '''All the above, again''', for each alternative language e.g. [http://cy.wikipedia.org/wiki/Cwtiad_Torchog_Bach Welsh]; [http://fr.wikipedia.org/wiki/Petit_gravelot French]; [http://zh.wikipedia.org/wiki/%E9%87%91%E7%9C%B6%E9%B8%BB Chinese]

*Wikimedia Commons
** '''All''' species indexes, e.g. [http://commons.wikimedia.org/wiki/Charadrius_dubius Charadrius dubius]
** '''Each individual''' image, e.g. [http://commons.wikimedia.org/wiki/Image:Charadrius_dubius_1_%28Marek_Szczepanek%29.jpg Charadrius dubius 1 (Marek Szczepanek).jpg]
** '''Each family''' list [http://commons.wikimedia.org/wiki/Charadriidae Charadriidae]

*Wiktionary
** '''All''' species articles, e.g. [http://en.wiktionary.org/wiki/american_golden_plover American Golden Plover]
** '''All''' family articles, e.g. [http://en.wiktionary.org/wiki/plover Plover]
** '''Many of the above, in other langauges''' e.g. [http://en.wiktionary.org/wiki/aquila_reale Italian]; [http://en.wiktionary.org/wiki/%D0%B1%D0%B5%D1%80%D0%BA%D1%83%D1%82 Russian]

*Wikispecies
** '''Every''' speices, e.g. [http://species.wikimedia.org/wiki/Charadrius_dubius Charadrius dubius]
** '''Every''' genus, e.g. [http://species.wikimedia.org/wiki/Charadrius Charadrius]
** '''Every''' sub-family, e.g. [http://species.wikimedia.org/wiki/Charadriinae Charadriinae]
** '''Every''' family, e.g. [http://species.wikimedia.org/wiki/Charadriidae Charadriidae]
** and so on, for '''every other rank'''
** '''Every''' image (e.g. [http://species.wikimedia.org/wiki/Image:Charadrius_hiaticula_He.jpg Charadrius hiaticula He.jpg]

*Google
**[http://www.google.co.uk/search?hl=en&hs=dBU&client=firefox-a&rls=org.mozilla:en-US:official&sa=X&oi=spell&resnum=0&ct=result&cd=1&q=%22E+coli%22&spell=1 Google finds about '''37,600,000''' for "E coli"].
***[http://www.google.co.uk/search?hs=Apo&hl=en&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&q=%22Escherichia+coli%22&btnG=Search&meta= Google finds about '''19,500,000''' for "Escherichia coli"]
***[http://www.google.co.uk/search?hs=zqo&hl=en&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&q=%22Ecoli%22&btnG=Search&meta= Google finds about '''722,000''' for "Ecoli"].
**[http://www.google.co.uk/search?hs=vWC&hl=en&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&q=%22Homo+sapiens%22&btnG=Search&meta= Google finds about '''14,200,000''' for "Homo sapiens"]
***[http://www.google.co.uk/search?hs=vWC&hl=en&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&q=%22Homo+sapien%22+-sapiens&btnG=Search&meta= Google finds about '''273,000''' for the mis-spelling "Homo sapien" -sapiens.]
**[http://www.google.co.uk/search?q=%22%22Homo+erectus%22%22&start=0&ie=utf-8&oe=utf-8&client=firefox-a&rls=org.mozilla:en-US:official Google finds about '''1,260,000''' for ""Homo erectus"]
**[http://www.google.com/search?svnum=10&as_scoring=r&hl=en&edition=us&as_drrb=q&as_qdr=&as_mind=1&as_minm=9&as_maxd=1&as_maxm=10&q=%22Clostridium+difficile%22&ie=UTF-8&sa=N&tab=nw Google finds about '''1,380,000''' for "Clostridium difficile"].
**[http://www.google.com/search?hl=en&lr=&edition=us&q=%22Passer+domesticus%22&btnG=Search Google finds about '''841,000''' for "Passer domesticus"].
***[http://images.google.com/images?hl=en&lr=&edition=us&q=%22Passer%20domesticus%22&btnG=Search&sa=N&tab=wi Google images finds about '''3,140''' for "Passer domesticus"].
**[http://www.google.co.uk/search?hl=en&hs=oEU&client=firefox-a&rls=org.mozilla:en-US:official&sa=X&oi=spell&resnum=0&ct=result&cd=1&q=%22Acer+palmatum%22&spell=1 Google finds about '''602,000''' for "Acer palmatum"]
** At the time of writing, '''every single one''' of the first 20 [http://www.google.com/search?q=%22Noctule+bat%22 Google results for "Noctule Bat"] also includes the scientific name ''Nyctalus noctula''.

*[http://www.arkive.org/ ARKive] - '''2000''' species ("It is ARKive's current aim to compile audio-visual records, where such media exists, for the 15,000-plus species currently threatened with extinction, according to the World Conservation Union's (IUCN) Red List of Threatened Species.")

*[http://www.rhs.org.uk/rhsplantfinder/plantfinder.asp Royal Horticultural Society - RHS Plant Finder] - '''70,000''' plants

*[http://www.bacterio.net List of Prokaryotic Names (formerly List of Bacterial Names)] - 2,032 *files*; '''10,268''' published names (to 2006-09-07)

*[http://nbn.nhm.ac.uk/nhm/ UK National Biodiversity Network's Species Dictionary]

*[http://www.searchnbn.net/ UK National Biodiversity Network Gateway] - '''20 million+''' species records

*[http://www.sp2000.org/ Species 2000] - '''450,000 species'''

*[http://www.bioimages.org.uk/index.html BioImages - Virtual Fieldguide] - '''53,000''' images depicting 4,600 species (see [[species-brainstorming#Malcolm_Storey|Wiki comments from site owner]])

*[http://animaldiversity.ummz.umich.edu/ Animal Diversity Web] - "'''Thousands''' of species accounts ['''plus'''] descriptions of levels of organization above the species level, especially phyla, classes, and in some cases, orders and families. Hundreds of hyperlinked pages and images illustrate the traits and general biology of these groups"

* [http://www.ubio.org/index.php?pagename=home uBio]
**NameBank is a repository of '''millions''' of recorded biological names and facts that link those names together.
**ClassificationBank stores multiple classifications and taxonomic concepts that are the result of expert opinions. It extends the functionality of NameBank.

*[http://www.birdlife.org/datazone/species/ BirdLife International] - all birds of the world (~'''10,000''')

*[http://bugguide.net/ Bug Guide] - all insects, spiders, and allies, of the USA and Canada (most with more than one page).
** e.g. [http://bugguide.net/node/view/70875 Arge pectoralis - Birch Sawfly]

*[http://www.bto.org/birdtrack/ BirdTrack]
**[http://blx1.bto.org/bt-dailyresults/results/s171-20-06.html Lapwing]

*[http://www.discoverlife.org/ Discover Life] - "contains '''306,553''' species. The Polistes Foundation and its scientific partners plan to add high-quality identification guides, maps, images, and text for '''a million species''' by 2012. [...] Each month Discover Life serves approximately 3 million pages and images to 70,000 IP addresses"

*[http://www.record-lrc.co.uk/ rECOrd] (the Local Biological Records Centre serving the Cheshire region of England) - '''1.6 million''' species records available online for the public to search and map

===Planned sites===
*[http://herbariaunited.org/atHome/ Herbaria United] (part of The website of the Botanical Collection Managers Group (BCMG), a specialist group of the Linnean Society of London) - "The UK has the world's largest and oldest collections of herbarium specimens held in trust by museums and universities. A new project is just getting underway to put all this online."

==Notable websites==
These high-profile websites use species names

*Amazon
**[http://www.amazon.co.uk/s/?url=search-alias%3Daps&field-keywords=%22house+sparrow%22 search for "House Sparrow"]

*BBC News
**[http://news.bbc.co.uk/1/hi/uk/4835208.stm Fewer birds spotted in UK gardens]
**[http://news.bbc.co.uk/1/hi/england/london/4743250.stm Study to solve sparrow's decline riddle]

*Encyclopaedia Britannica - all species, e.g.
**[http://concise.britannica.com/ebc/article-9379473/starling Starling]

*Flickr
**[http://www.flickr.com/photos/tags/citheronia/ Tag for moth genera 'citheronia']
***[http://www.flickr.com/photos/30268343@N00/152101772/ Sample result from that search]
**[http://www.flickr.com/groups/birdguide/ Field Guide: Birds of the World] 23,073 tagged photos, as at 2006-10-21

*CNN
**[http://archives.cnn.com/2001/NATURE/01/24/dying.eagles/ Disease threatens bald eagle population]

*eBay
**[http://search.ebay.com/house-sparrow search for "House Sparrow"]

*The Guardian
**[http://environment.guardian.co.uk/conservation/story/0,,1878956,00.html The call of the wildlife]
**[http://education.guardian.co.uk/higher/news/story/0,,1665396,00.html Sparrow joins 'raped' duck in Dutch museum] (note improper capitalisation "''passer domesticus''")

*London Zoo
**[http://www.zsl.org/london-zoo/animals/birds/tawny-frogmouth,99,AN.html Tawny frogmouth]

*Microsoft
**[http://www.microsoft.com/games/zootycoon/zoo2/zoo2_ymi_animals1.asp Zoo Tycoon]

*MSN-Encarta - all species, e.g.
**[http://encarta.msn.com/encnet/refpages/search.aspx?q=vulgaris&Submit2=Go Search for "vulgaris"]

*MySpace
**[http://blog.myspace.com/index.cfm?fuseaction=blog.view&friendID=47134278&blogID=79591637]

*Nature
**[http://www.nature.com/nature/focus/avianflu/index.html Avian flu web focus]

*Nature Network, Boston
**[http://network.nature.com/boston/news/archive/2006/06/13/the-student-and-the-squid The student and the squid] '''N.B.''' site already supports rel-tag, hCard for user profiles and hCalendar for marking up events across the site.

*NASA
**[http://history.nasa.gov/SP-401/ch3.htm SP-401 Skylab, Classroom in Space. Part II - Student Experiments] ("The common Cross spider (Araneus diadematus)")

*New York Times
**[http://query.nytimes.com/gst/fullpage.html?sec=travel&res=9D04E4DE1131F93BA25751C0A9669C8B63 Where the Eagles Fly: Seeing the National Symbol]

*Snopes (Urban Legends Reference Pages)
**[http://www.snopes.com/photos/animals/fishfly.asp Fish Fly]

*United Kingdom Government
**[http://www.defra.gov.uk/wildlife-countryside/vertebrates/gen-licence.htm DEFRA: General licences under the Wildlife & Countryside Act 1981]

*United States of America Government
**ITIS, e.g. [http://www.itis.usda.gov/servlet/SingleRpt/SingleRpt?search_topic=TSN&search_value=179628 Passer Domesticus] - "authoritative taxonomic information on plants, animals, fungi, and microbes of North America and the world"

*W3C
**[http://dev.w3.org/cvsweb/2000/10/swap/test/ferrell/biology.n3?rev=1.4 An Ontology of Biology]
**[http://esw.w3.org/topic/HCLSIG_BioRDF_Subgroup/Tasks/Reagents/Status_Reports/2006-05-04 BioRDF Sub-group Status Report, 4 May 2006]

*Yahoo Groups
**[http://tech.groups.yahoo.com/group/passerdomesticus/ passerdomesticus] species as group name!

==Breaking news==
*[http://news.bbc.co.uk/1/shared/spl/hi/pop_ups/06/sci_nat_orchid_spectacular/html/1.stm BBC News: Stunning new orchids from Asia's rainforest] - 2006-10-16
*[http://news.bbc.co.uk/1/hi/sci/tech/6045802.stm BBC News: Winter home find cheers twitchers] (winter home of the northern bald ibis found) - 2006-10-13
*[http://news.bbc.co.uk/1/hi/sci/tech/6043648.stm BBC News: New mouse find is 'living fossil'] - 2006-10-12
*[http://news.bbc.co.uk/1/hi/sci/tech/6035113.stm BBC News: Giant camel fossil found in Syria] - 2006-10-10
*[http://news.bbc.co.uk/1/hi/sci/tech/5414410.stm BBC News: Sharks swim into political waters] - 2006-10-06
*[http://news.bbc.co.uk/1/hi/sci/tech/5403570.stm BBC News: 'Monster' fossil find in Arctic] - 2006-10-05

==Use in blogs==
*[http://technorati.com/search/%22passer%20domesticus%22 Technorati search for "Passer domesticus"] (367 found, as at 2006-09-25)
*[http://technorati.com/search/%22acer%20palmatum%22 Technorati search for "Acer palmatum"] (682 found, as at 2006-09-25)
*[http://technorati.com/search/%22Homo%20sapiens%22 Technorati search for "Homo sapiens"] (40,932 found, as at 2006-09-25)
*[http://technorati.com/search/birding Technorati search for "birding"] (26,472 found, as at 2006-09-25)
*[http://ramblingsofanaturalist.blogspot.com/ Ramblings of a Naturalist]
*[http://squaremetre1.blogspot.com/ The Square Metre]
*[http://windowboxwildlife.blogspot.com/index.html Windowbox Wildlife]
*[http://www.rxwildlife.org.uk/ RXWildlife]

==And finally...==
Gary Larson, in his book ''The Far Side Gallery'' (Warner Books, 1980, ISBN 0751502367) has a cartoon, showing two entomologists sitting down to eat dinner in a jungle. One says to the other "Hey! What's this ''Drosophila melanogaster'' doing in my soup?"

==Contributors==
*[[User:AndyMabbett|Andy Mabbett]] (proponent)
*Malcolm Storey (per e-mail)
*[[User:SXBRC|Charles Roper]], [http://www.sxbrc.org.uk/ Sussex Biodiversity Record Centre] (proponent)
*[[User:SteveMcBill|Steve McWilliam]], [http://www.rECOrd-LRC.co.uk/ rECOrd - The Biodiversity Information System for the Cheshire region] (proponent)

==See also==
[[species-brainstorming]]

species-examples

2006-10-22T00:57:47Z

BenWest: suggested an alternative grouping by publish strategy (eventually) and by publisher, also added analysis for species.wikimedia.org

=Species Examples=

Examples of common and scientific names of living things, which could be marked up with a "'''[[species]]'''" (or similar) microformat. Note use of matching pairs of examples, where possible.

__TOC__

== Alternative Grouping By Strategy ==
I'd like to regroup these examples... perhaps by publishing strategy instead of a list of what is being published. Should this be available as an alternate grouping section? In the mean time, a grouping by publisher would help analysis go smoother. [[User:BenWest|BenWest]] 17:57, 21 Oct 2006 (PDT)

I looked at several examples. Several of them feel like tagging to me. Should we attempt to note what level or resolution is available in each example?

=== Tagging ===
The [[http://species.wikimedia.org/wiki/Charadrius_dubius wiki media bird example]] is particularly interesting.
<pre><nowiki>
<dd>Regnum: <a href="/wiki/Animalia" title="Animalia">Animalia</a> (Metazoa)
<dl>
<dd>Subregnum: <a href="/wiki/Eumetazoa" title="Eumetazoa">Eumetazoa</a>
<dl>
<dd>Superphylum: Bilateria: <a href="/wiki/Deuterostomia" title="Deuterostomia">Deuterostomia</a>
<dl>
<dd>Phylum: <a href="/wiki/Chordata" title="Chordata">Chordata</a>
<dl>

<dd>Subphylum: <a href="/wiki/Vertebrata" title="Vertebrata">Vertebrata</a>
<dl>
<dd>Classis: <a href="/wiki/Aves" title="Aves">Aves</a>
<dl>
<dd>Subclassis: <a href="/wiki/Neognathae" title="Neognathae">Neognathae</a>
<dl>
<dd>Ordo: <a href="/wiki/Charadriiformes" title="Charadriiformes">Charadriiformes</a>
<dl>
<dd>Subordo: <a href="/wiki/Charadrii" title="Charadrii">Charadrii</a>

<dl>
<dd>Familia: <a href="/wiki/Charadriidae" title="Charadriidae">Charadriidae</a>
<dl>
<dd>Subfamily: <a href="/wiki/Charadriinae" title="Charadriinae">Charadriinae</a>
<dl>
<dd>Genus: <a href="/wiki/Charadrius" title="Charadrius">Charadrius</a>
<dl>
<dd>Species: Charadrius dubius
<dl>

<dd>Subspecies: <a href="/w/index.php?title=Charadrius_dubius_curonicus&action=edit" class="new" title="Charadrius dubius curonicus">C. d. curonicus</a> - <a href="/w/index.php?title=Charadrius_dubius_dubius&action=edit" class="new" title="Charadrius dubius dubius">C. d. dubius</a> - <a href="/w/index.php?title=Charadrius_dubius_jerdoni&action=edit" class="new" title="Charadrius dubius jerdoni">C. d. jerdoni</a> - <a href="/w/index.php?title=Charadrius_dubius_papuanus&action=edit" class="new" title="Charadrius dubius papuanus">C. d. papuanus</a></dd>

...
</nowiki>
</pre>
This feels similar to tagging to me. This particular example has a resolves the whole heirarchy, correct? [[User:BenWest|BenWest]] 17:57, 21 Oct 2006 (PDT)

==binominals==

===Birds===

'''Black-tailed Godwit''' on [http://www.westmidlandbirdclub.com/ladywalk/latest.htm West Midland Bird Club's Ladywalk reserve latest news page]

<pre><nowiki>Black-tailed Godwit</nowiki></pre>

'''''Limosa limosa''''' on [http://www.westmidlandbirdclub.com/records/lists.htm West Midland Bird Club's county lists']

<pre><nowiki><td>Limosa limosa</td></nowiki></pre>

===Mammal===
'''Wolf''' on [http://www.wolf.org/wolves/index.asp International Wolf Center]

===Fish===
'''Northern pike''' on [http://www.dnr.state.mn.us/fish/northern/index.html Minnesota Department of Natural Resources]

'''''Esox lucius''''' on [http://www.pikezander.co.uk/pike.htm Pike & Zander]

===Insect===
'''Death’s Head Hawkmoth''' on [http://funkman.org/animal/insect/deathheadmoth.html Animal Teachers]

'''''Acherontia atropos''''' on [http://ukmoths.org.uk/show.php?id=2540 UK Moths]

'''Migrant Hawker''' (''Aeshna mixta'') on [http://www.sxbrc.org.uk/news/friston-forest-recording-day Sussex Biodiversity Record Centre]

'''Sloe Bug''' (''Dolycoris baccarum'') on [http://www.record-lrc.co.uk/?Mod=Forum&Do=ViewThread&ForumID=31&ThreadID=101 rECOrd - The Biodiversity Information Centre for the Cheshire region]

===Arachnid===
'''Tarantulas''' on [http://www.nature.com/news/2006/060925/full/060925-6.html Nature.com]

'''Costa Rican zebra tarantula''' (''Aphonopelma seemanni'') on [http://www.nature.com/news/2006/060925/full/060925-6.html Nature.com]

'''''Araneus angulatus''''' on [http://www.sxbrc.org.uk/news/friston-forest-recording-day Sussex Biodiversity Record Centre]

===Plant===
'''Bog Pimpernel''' on [http://www.map-reading.co.uk/wildflowers/HTML%20files/f0219.htm Map Reading's Wildflower Images]

'''''Anagallis tenella''''' on [http://www.bioimages.org.uk/HTML/T47624.HTM BioImages]

'''''Persicaria campanulatum''''' on [http://www.record-lrc.co.uk/?Mod=Forum&Do=ViewThread&ForumID=6&ThreadID=75 rECOrd - The Biodiversity Information Centre for the Cheshire region]

===Fungi===

'''''Amanita muscaria''''' on [http://www.mykoweb.com/CAF/species/Amanita_muscaria.html California Fungi]
* as '''''Amanita muscaria'' (L. per Fr.) Hooker'''
* as '''''Amanita muscaria var. flavivolvata'''''

'''Fly Agaric''' on [http://www.treesforlife.org.uk/forest/mythfolk/flyagaric.html Trees for Life]

'''''Rhodocollybia maculata'' (Albertini & Schweinitz: Fries) Singer''' on [http://www.ilmyco.gen.chicago.il.us/Taxa/Rhodomacul540.html]
*also written as '''''Rhodocollybia maculata'' (Albertini & Schweinitz ex Fries) Singer'''
*(This is where a post-Linnean author is given special rights (because his descriptions were comparatively complete - i.e. recognisable) so his interpretation of earlier names is taken as the sense meant by the original author. Think these used to be "apud" and are now "ex" although a colon has also been used. There are only a few sanctioning authors, the main one being Elias Fries.(Fr.) )

==More than binominals==

===Authority===
'''''Pica pica'' Linnaeus, (1758)''' on [http://en.wikipedia.org/wiki/European_Magpie Wikipedia: European Magpie]
:(i.e. named by Linnaeus in 1758)

===Unspecified species===
'''''Podiceps sp.''''' on [http://www.birdlife.org/datazone/species/index.html?action=SpcHTMDetails.asp&sid=3644&m=0 Bird Life] <pre><nowiki>Podiceps sp.</nowiki></pre>

'''Psyllid plant hopper''' [http://ramblingsofanaturalist.blogspot.com/2006/07/bay-sucker-gall-trioza-alacris.html on Ramblings of a Naturalist blog]

===Sub-species===

====Animal====
'''''Larus glaucoides kumlieni''' on [http://www.birdguides.com/html/vidlib/species/Larus_glaucoides_kumlieni.htm BirdGuides]

'''Kumlien's Gull''' on [http://www.birdsireland.com/pages/rare_bird_news/2005/january_photos.html Birds Ireland]

====Plant====
'''''Pisum sativum L. subsp. sativum''''' on [http://www.plantnames.unimelb.edu.au/Sorting/Pisum.html] (also has other examples; note lack of required italics)
<pre><nowiki>Pisum sativum L. subsp. sativum</nowiki></pre>

===Cultivars (plant)===
'''''Chamaecyparis lawsoniana 'Aureomarginata'''''' on [http://en.wikipedia.org/wiki/Cultivar Wikipedia: Cultivar]

<pre><nowiki><dd>Chamaecyparis lawsoniana 'Aureomarginata'</dd></nowiki></pre>

'''''Chamaecyparis lawsoniana'' 'Golden Wonder'''' on [http://www.plantago.nl/plantindex/c/Chamaecyparis/Chamaecyparis_4.htm plantago.nl]

====Cultivar groups (plant)====
'''''Brassica oleracea'' Botrytis Group''' on [http://en.wikipedia.org/wiki/Cultivar Wikipedia: Cultivar]

===Trade names (plant)===

'''''Rosa'' Peace''' on [http://en.wikipedia.org/wiki/Cultivar Wikipedia: Cultivar]
:("Peace" is a trade designation or "selling name" for the cultivar R. 'Madame A. Meilland' and should therefore be printed in a different typeface from the rest of the name, without any quote marks)

'''Sunflower 'Giant Single'''' on [http://cgi.www.johnsons-seeds.com/cgi-bin/www.johnsons-seeds.com/detail/azlist/S-1 Johnsons Seeds]

'''Sunflower 'Infrared' F1''' on [http://cgi.www.johnsons-seeds.com/cgi-bin/www.johnsons-seeds.com/detail/azlist/S-1 Johnsons Seeds]
:(Note "F1" cross designation)

===Variety (plant)===
'''''Pisum sativum var. macrocarpon''''' on [http://davesgarden.com/pf/go/8/index.html Dave's Garden]

====Sub-variety (plant)====

'''''Betula ermani var. genuina subvar. brevidentata''''' on [http://www.nccpg.com/gloucestershire/wilson1.html National Council for the Conservation of Plants and Gardens, Gloucestershire Group] (plus many other examples)

===Form (plant)===

'''''Acanthocalycium spiniflorum f. klimpelianum''''' on [http://en.wikipedia.org/wiki/Form_%28botany%29 Wikipedia: form (botany)]
*aka '''''Acanthocalycium spiniflorum forma klimpelianum'''''

===Sense (plant)===
'''''Ranunculus aquatilis s.l.''''' and '''''R. aquatilis s.s'''''; on [http://www.westmidlandbirdclub.com/blithfield/plants20060815.htm Blithfield Reservoir: Survey of Flowering Plants...] (see also footnotes on that page)

===Cross (plant)===
'''''Digitalis x mertonensis''''' on [http://www.hortax.org.uk/gardenplantsnames.html Hortax]
:The hybrid name for all plants derived from the cross between '''D. purpurea''' and '''D. grandiflora'''. The "x" indicates the hybrid status.

'''''× Fatshedera lizei''''' on [http://oregonstate.edu/dept/ldplants/sci-names.htm Scientific Plant Names, Oregon State Univ., Landscape Plants]

===Strain (bacteria)===
'''''Escherichia coli O157:H7''''' on [http://www.cfsan.fda.gov/~mow/chap15.html FDA.gov]

'''''E.Coli''''' on [http://news.bbc.co.uk/1/hi/england/southern_counties/5346842.stm BBC news]

==Misc==
===Superseded names===
'''''Tringa bartramia''''' superseded by '''''Bartramia longicauda''''' on [http://www.westmidlandbirdclub.com/firsts/UPLSA.htm West Midland Bird Club's Upland Sandpiper article]

===GUID===
'''NBN Taxon Key''' for European Otter, ''Lutra lutra'', on [http://nbn.nhm.ac.uk/nhm/bin/nbntaxa.dll/taxon_details?taxon_key=NBNSYS0000005133 NBN Species Dictionary]: '''NBNSYS0000005133'''

'''LSID ([http://lsid.sourceforge.net/#whatislsid Life Science Indicator])''' for ''Popillia japonica'' on [http://names.ubio.org/browser/details2.php?names=on&authors=on&sci=on&vern=on&conceptID=&expand=&namebankID=3377001 uBio]: '''urn:lsid:ubio.org:namebank:3377001'''

===Wikipedia===
'''Black-tailed Godwit''' on [http://en.wikipedia.org/wiki/Black-tailed_Godwit Wikipedia: Black-tailed Godwit]

Wikipedia uses several sets of markup, e.g. (in-line styles and links, plus some other markup, removed, for clarity):

<pre><nowiki>The Black-tailed Godwit, Limosa limosa</nowiki></pre>

and:

<pre><nowiki>
<tr>
<td>Kingdom:</td>
<td>Animalia</td>
</tr>
<tr>
<td>Phylum:</td>
<td>Chordata</td>
</tr>
<tr>
<td>Class:</td>
<td>Aves</td>
</tr>
<tr>
<td>Order:</td>
<td>Charadriiformes</td>
</tr>
<tr>
<td>Family:</td>
<td>Scolopacidae</td>
</tr>
<tr>
<td>Genus:</td>
<td>Limosa</td>
</tr>
<tr>
<td>Species:</td>
<td>L. limosa</td>
</tr>

<tr>
<th>binominal name</th>
</tr>
<tr>
<td>Limosa limosa
<td>(Linnaeus, 1758)</td>
</tr>
</nowiki></pre>

==Quantitative evidence==

For evidence of quantitative, rather than qualitative, use of species' and other taxonomic names, see [http://microformats.org/discuss/mail/microformats-discuss/2006-September/005790.html] and [http://microformats.org/discuss/mail/microformats-discuss/2006-September/005791.html]. Furthermore:

*Wikipedia:
** '''All''' species articles, e.g. [http://en.wikipedia.org/wiki/Little_Ringed_Plover Little Ringed Plover] (see [[species-examples#Wikipedia|above]])
** '''All''' genera articles, e.g. [http://en.wikipedia.org/wiki/Plover Charadrius (Plover)]
** '''All''' higher classes, e.g. [http://en.wikipedia.org/wiki/Charadriidae Charadriidae]
** '''All''' regional lists, e.g. [http://en.wikipedia.org/wiki/List_of_British_birds:_non-passerines List of British birds]
** '''All''' dedicatees, e.g. [http://en.wikipedia.org/wiki/Alexander_Wilson Alexander Wilson]
** '''All''' authorities, e.g. [http://en.wikipedia.org/wiki/Giovanni_Antonio_Scopoli Giovanni Antonio Scopoli]
** '''All''' images of living things, e.g. [http://en.wikipedia.org/wiki/Image:Charadrius_dubius_4_%28Marek_Szczepanek%29.jpg Charadrius dubius 4 (Marek Szczepanek).jpg]
** Many reserves, lakes, and other places of interest, e.g. [http://en.wikipedia.org/wiki/Belvide Belvide]
** Many biological authors and illustrators, e.g. [http://en.wikipedia.org/wiki/John_Audubon John Audubon]; [http://en.wikipedia.org/wiki/Gilbert_White Gilbert White]
** Random articles on other topics, e.g. [http://en.wikipedia.org/wiki/Balancing_lake Balancing lake}]
** '''All the above, again''', for each alternative language e.g. [http://cy.wikipedia.org/wiki/Cwtiad_Torchog_Bach Welsh]; [http://fr.wikipedia.org/wiki/Petit_gravelot French]; [http://zh.wikipedia.org/wiki/%E9%87%91%E7%9C%B6%E9%B8%BB Chinese]

*Wikimedia Commons
** '''All''' species indexes, e.g. [http://commons.wikimedia.org/wiki/Charadrius_dubius Charadrius dubius]
** '''Each individual''' image, e.g. [http://commons.wikimedia.org/wiki/Image:Charadrius_dubius_1_%28Marek_Szczepanek%29.jpg Charadrius dubius 1 (Marek Szczepanek).jpg]
** '''Each family''' list [http://commons.wikimedia.org/wiki/Charadriidae Charadriidae]

*Wiktionary
** '''All''' species articles, e.g. [http://en.wiktionary.org/wiki/american_golden_plover American Golden Plover]
** '''All''' family articles, e.g. [http://en.wiktionary.org/wiki/plover Plover]
** '''Many of the above, in other langauges''' e.g. [http://en.wiktionary.org/wiki/aquila_reale Italian]; [http://en.wiktionary.org/wiki/%D0%B1%D0%B5%D1%80%D0%BA%D1%83%D1%82 Russian]

*Wikispecies
** '''Every''' speices, e.g. [http://species.wikimedia.org/wiki/Charadrius_dubius Charadrius dubius]
** '''Every''' genus, e.g. [http://species.wikimedia.org/wiki/Charadrius Charadrius]
** '''Every''' sub-family, e.g. [http://species.wikimedia.org/wiki/Charadriinae Charadriinae]
** '''Every''' family, e.g. [http://species.wikimedia.org/wiki/Charadriidae Charadriidae]
** and so on, for '''every other rank'''
** '''Every''' image (e.g. [http://species.wikimedia.org/wiki/Image:Charadrius_hiaticula_He.jpg Charadrius hiaticula He.jpg]

*Google
**[http://www.google.co.uk/search?hl=en&hs=dBU&client=firefox-a&rls=org.mozilla:en-US:official&sa=X&oi=spell&resnum=0&ct=result&cd=1&q=%22E+coli%22&spell=1 Google finds about '''37,600,000''' for "E coli"].
***[http://www.google.co.uk/search?hs=Apo&hl=en&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&q=%22Escherichia+coli%22&btnG=Search&meta= Google finds about '''19,500,000''' for "Escherichia coli"]
***[http://www.google.co.uk/search?hs=zqo&hl=en&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&q=%22Ecoli%22&btnG=Search&meta= Google finds about '''722,000''' for "Ecoli"].
**[http://www.google.co.uk/search?hs=vWC&hl=en&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&q=%22Homo+sapiens%22&btnG=Search&meta= Google finds about '''14,200,000''' for "Homo sapiens"]
***[http://www.google.co.uk/search?hs=vWC&hl=en&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&q=%22Homo+sapien%22+-sapiens&btnG=Search&meta= Google finds about '''273,000''' for the mis-spelling "Homo sapien" -sapiens.]
**[http://www.google.co.uk/search?q=%22%22Homo+erectus%22%22&start=0&ie=utf-8&oe=utf-8&client=firefox-a&rls=org.mozilla:en-US:official Google finds about '''1,260,000''' for ""Homo erectus"]
**[http://www.google.com/search?svnum=10&as_scoring=r&hl=en&edition=us&as_drrb=q&as_qdr=&as_mind=1&as_minm=9&as_maxd=1&as_maxm=10&q=%22Clostridium+difficile%22&ie=UTF-8&sa=N&tab=nw Google finds about '''1,380,000''' for "Clostridium difficile"].
**[http://www.google.com/search?hl=en&lr=&edition=us&q=%22Passer+domesticus%22&btnG=Search Google finds about '''841,000''' for "Passer domesticus"].
***[http://images.google.com/images?hl=en&lr=&edition=us&q=%22Passer%20domesticus%22&btnG=Search&sa=N&tab=wi Google images finds about '''3,140''' for "Passer domesticus"].
**[http://www.google.co.uk/search?hl=en&hs=oEU&client=firefox-a&rls=org.mozilla:en-US:official&sa=X&oi=spell&resnum=0&ct=result&cd=1&q=%22Acer+palmatum%22&spell=1 Google finds about '''602,000''' for "Acer palmatum"]
** At the time of writing, '''every single one''' of the first 20 [http://www.google.com/search?q=%22Noctule+bat%22 Google results for "Noctule Bat"] also includes the scientific name ''Nyctalus noctula''.

*[http://www.arkive.org/ ARKive] - '''2000''' species ("It is ARKive's current aim to compile audio-visual records, where such media exists, for the 15,000-plus species currently threatened with extinction, according to the World Conservation Union's (IUCN) Red List of Threatened Species.")

*[http://www.rhs.org.uk/rhsplantfinder/plantfinder.asp Royal Horticultural Society - RHS Plant Finder] - '''70,000''' plants

*[http://www.bacterio.net List of Prokaryotic Names (formerly List of Bacterial Names)] - 2,032 *files*; '''10,268''' published names (to 2006-09-07)

*[http://nbn.nhm.ac.uk/nhm/ UK National Biodiversity Network's Species Dictionary]

*[http://www.searchnbn.net/ UK National Biodiversity Network Gateway] - '''20 million+''' species records

*[http://www.sp2000.org/ Species 2000] - '''450,000 species'''

*[http://www.bioimages.org.uk/index.html BioImages - Virtual Fieldguide] - '''53,000''' images depicting 4,600 species (see [[species-brainstorming#Malcolm_Storey|Wiki comments from site owner]])

*[http://animaldiversity.ummz.umich.edu/ Animal Diversity Web] - "'''Thousands''' of species accounts ['''plus'''] descriptions of levels of organization above the species level, especially phyla, classes, and in some cases, orders and families. Hundreds of hyperlinked pages and images illustrate the traits and general biology of these groups"

* [http://www.ubio.org/index.php?pagename=home uBio]
**NameBank is a repository of '''millions''' of recorded biological names and facts that link those names together.
**ClassificationBank stores multiple classifications and taxonomic concepts that are the result of expert opinions. It extends the functionality of NameBank.

*[http://www.birdlife.org/datazone/species/ BirdLife International] - all birds of the world (~'''10,000''')

*[http://bugguide.net/ Bug Guide] - all insects, spiders, and allies, of the USA and Canada (most with more than one page).
** e.g. [http://bugguide.net/node/view/70875 Arge pectoralis - Birch Sawfly]

*[http://www.bto.org/birdtrack/ BirdTrack]
**[http://blx1.bto.org/bt-dailyresults/results/s171-20-06.html Lapwing]

*[http://www.discoverlife.org/ Discover Life] - "contains '''306,553''' species. The Polistes Foundation and its scientific partners plan to add high-quality identification guides, maps, images, and text for '''a million species''' by 2012. [...] Each month Discover Life serves approximately 3 million pages and images to 70,000 IP addresses"

*[http://www.record-lrc.co.uk/ rECOrd] (the Local Biological Records Centre serving the Cheshire region of England) - '''1.6 million''' species records available online for the public to search and map

===Planned sites===
*[http://herbariaunited.org/atHome/ Herbaria United] (part of The website of the Botanical Collection Managers Group (BCMG), a specialist group of the Linnean Society of London) - "The UK has the world's largest and oldest collections of herbarium specimens held in trust by museums and universities. A new project is just getting underway to put all this online."

==Notable websites==
These high-profile websites use species names

*Amazon
**[http://www.amazon.co.uk/s/?url=search-alias%3Daps&field-keywords=%22house+sparrow%22 search for "House Sparrow"]

*BBC News
**[http://news.bbc.co.uk/1/hi/uk/4835208.stm Fewer birds spotted in UK gardens]
**[http://news.bbc.co.uk/1/hi/england/london/4743250.stm Study to solve sparrow's decline riddle]

*Encyclopaedia Britannica - all species, e.g.
**[http://concise.britannica.com/ebc/article-9379473/starling Starling]

*Flickr
**[http://www.flickr.com/photos/tags/citheronia/ Tag for moth genera 'citheronia']
***[http://www.flickr.com/photos/30268343@N00/152101772/ Sample result from that search]
**[http://www.flickr.com/groups/birdguide/ Field Guide: Birds of the World] 23,073 tagged photos, as at 2006-10-21

*CNN
**[http://archives.cnn.com/2001/NATURE/01/24/dying.eagles/ Disease threatens bald eagle population]

*eBay
**[http://search.ebay.com/house-sparrow search for "House Sparrow"]

*The Guardian
**[http://environment.guardian.co.uk/conservation/story/0,,1878956,00.html The call of the wildlife]
**[http://education.guardian.co.uk/higher/news/story/0,,1665396,00.html Sparrow joins 'raped' duck in Dutch museum] (note improper capitalisation "''passer domesticus''")

*London Zoo
**[http://www.zsl.org/london-zoo/animals/birds/tawny-frogmouth,99,AN.html Tawny frogmouth]

*Microsoft
**[http://www.microsoft.com/games/zootycoon/zoo2/zoo2_ymi_animals1.asp Zoo Tycoon]

*MSN-Encarta - all species, e.g.
**[http://encarta.msn.com/encnet/refpages/search.aspx?q=vulgaris&Submit2=Go Search for "vulgaris"]

*MySpace
**[http://blog.myspace.com/index.cfm?fuseaction=blog.view&friendID=47134278&blogID=79591637]

*Nature
**[http://www.nature.com/nature/focus/avianflu/index.html Avian flu web focus]

*Nature Network, Boston
**[http://network.nature.com/boston/news/archive/2006/06/13/the-student-and-the-squid The student and the squid] '''N.B.''' site already supports rel-tag, hCard for user profiles and hCalendar for marking up events across the site.

*NASA
**[http://history.nasa.gov/SP-401/ch3.htm SP-401 Skylab, Classroom in Space. Part II - Student Experiments] ("The common Cross spider (Araneus diadematus)")

*New York Times
**[http://query.nytimes.com/gst/fullpage.html?sec=travel&res=9D04E4DE1131F93BA25751C0A9669C8B63 Where the Eagles Fly: Seeing the National Symbol]

*Snopes (Urban Legends Reference Pages)
**[http://www.snopes.com/photos/animals/fishfly.asp Fish Fly]

*United Kingdom Government
**[http://www.defra.gov.uk/wildlife-countryside/vertebrates/gen-licence.htm DEFRA: General licences under the Wildlife & Countryside Act 1981]

*United States of America Government
**ITIS, e.g. [http://www.itis.usda.gov/servlet/SingleRpt/SingleRpt?search_topic=TSN&search_value=179628 Passer Domesticus] - "authoritative taxonomic information on plants, animals, fungi, and microbes of North America and the world"

*W3C
**[http://dev.w3.org/cvsweb/2000/10/swap/test/ferrell/biology.n3?rev=1.4 An Ontology of Biology]
**[http://esw.w3.org/topic/HCLSIG_BioRDF_Subgroup/Tasks/Reagents/Status_Reports/2006-05-04 BioRDF Sub-group Status Report, 4 May 2006]

*Yahoo Groups
**[http://tech.groups.yahoo.com/group/passerdomesticus/ passerdomesticus] species as group name!

==Breaking news==
*[http://news.bbc.co.uk/1/shared/spl/hi/pop_ups/06/sci_nat_orchid_spectacular/html/1.stm BBC News: Stunning new orchids from Asia's rainforest] - 2006-10-16
*[http://news.bbc.co.uk/1/hi/sci/tech/6045802.stm BBC News: Winter home find cheers twitchers] (winter home of the northern bald ibis found) - 2006-10-13
*[http://news.bbc.co.uk/1/hi/sci/tech/6043648.stm BBC News: New mouse find is 'living fossil'] - 2006-10-12
*[http://news.bbc.co.uk/1/hi/sci/tech/6035113.stm BBC News: Giant camel fossil found in Syria] - 2006-10-10
*[http://news.bbc.co.uk/1/hi/sci/tech/5414410.stm BBC News: Sharks swim into political waters] - 2006-10-06
*[http://news.bbc.co.uk/1/hi/sci/tech/5403570.stm BBC News: 'Monster' fossil find in Arctic] - 2006-10-05

==Use in blogs==
*[http://technorati.com/search/%22passer%20domesticus%22 Technorati search for "Passer domesticus"] (367 found, as at 2006-09-25)
*[http://technorati.com/search/%22acer%20palmatum%22 Technorati search for "Acer palmatum"] (682 found, as at 2006-09-25)
*[http://technorati.com/search/%22Homo%20sapiens%22 Technorati search for "Homo sapiens"] (40,932 found, as at 2006-09-25)
*[http://technorati.com/search/birding Technorati search for "birding"] (26,472 found, as at 2006-09-25)
*[http://ramblingsofanaturalist.blogspot.com/ Ramblings of a Naturalist]
*[http://squaremetre1.blogspot.com/ The Square Metre]
*[http://windowboxwildlife.blogspot.com/index.html Windowbox Wildlife]
*[http://www.rxwildlife.org.uk/ RXWildlife]

==And finally...==
Gary Larson, in his book ''The Far Side Gallery'' (Warner Books, 1980, ISBN 0751502367) has a cartoon, showing two entomologists sitting down to eat dinner in a jungle. One says to the other "Hey! What's this ''Drosophila melanogaster'' doing in my soup?"

==Contributors==
*[[User:AndyMabbett|Andy Mabbett]] (proponent)
*Malcolm Storey (per e-mail)
*[[User:SXBRC|Charles Roper]], [http://www.sxbrc.org.uk/ Sussex Biodiversity Record Centre] (proponent)
*[[User:SteveMcBill|Steve McWilliam]], [http://www.rECOrd-LRC.co.uk/ rECOrd - The Biodiversity Information System for the Cheshire region] (proponent)

==See also==
[[species-brainstorming]]

species-examples

2006-10-22T00:24:39Z

BenWest: /* Mammal */ removed nps.gov (404'd)

=Species Examples=

Examples of common and scientific names of living things, which could be marked up with a "'''[[species]]'''" (or similar) microformat. Note use of matching pairs of examples, where possible.

__TOC__

==binominals==

===Birds===

'''Black-tailed Godwit''' on [http://www.westmidlandbirdclub.com/ladywalk/latest.htm West Midland Bird Club's Ladywalk reserve latest news page]

<pre><nowiki>Black-tailed Godwit</nowiki></pre>

'''''Limosa limosa''''' on [http://www.westmidlandbirdclub.com/records/lists.htm West Midland Bird Club's county lists']

<pre><nowiki><td>Limosa limosa</td></nowiki></pre>

===Mammal===
'''Wolf''' on [http://www.wolf.org/wolves/index.asp International Wolf Center]

===Fish===
'''Northern pike''' on [http://www.dnr.state.mn.us/fish/northern/index.html Minnesota Department of Natural Resources]

'''''Esox lucius''''' on [http://www.pikezander.co.uk/pike.htm Pike & Zander]

===Insect===
'''Death’s Head Hawkmoth''' on [http://funkman.org/animal/insect/deathheadmoth.html Animal Teachers]

'''''Acherontia atropos''''' on [http://ukmoths.org.uk/show.php?id=2540 UK Moths]

'''Migrant Hawker''' (''Aeshna mixta'') on [http://www.sxbrc.org.uk/news/friston-forest-recording-day Sussex Biodiversity Record Centre]

'''Sloe Bug''' (''Dolycoris baccarum'') on [http://www.record-lrc.co.uk/?Mod=Forum&Do=ViewThread&ForumID=31&ThreadID=101 rECOrd - The Biodiversity Information Centre for the Cheshire region]

===Arachnid===
'''Tarantulas''' on [http://www.nature.com/news/2006/060925/full/060925-6.html Nature.com]

'''Costa Rican zebra tarantula''' (''Aphonopelma seemanni'') on [http://www.nature.com/news/2006/060925/full/060925-6.html Nature.com]

'''''Araneus angulatus''''' on [http://www.sxbrc.org.uk/news/friston-forest-recording-day Sussex Biodiversity Record Centre]

===Plant===
'''Bog Pimpernel''' on [http://www.map-reading.co.uk/wildflowers/HTML%20files/f0219.htm Map Reading's Wildflower Images]

'''''Anagallis tenella''''' on [http://www.bioimages.org.uk/HTML/T47624.HTM BioImages]

'''''Persicaria campanulatum''''' on [http://www.record-lrc.co.uk/?Mod=Forum&Do=ViewThread&ForumID=6&ThreadID=75 rECOrd - The Biodiversity Information Centre for the Cheshire region]

===Fungi===

'''''Amanita muscaria''''' on [http://www.mykoweb.com/CAF/species/Amanita_muscaria.html California Fungi]
* as '''''Amanita muscaria'' (L. per Fr.) Hooker'''
* as '''''Amanita muscaria var. flavivolvata'''''

'''Fly Agaric''' on [http://www.treesforlife.org.uk/forest/mythfolk/flyagaric.html Trees for Life]

'''''Rhodocollybia maculata'' (Albertini & Schweinitz: Fries) Singer''' on [http://www.ilmyco.gen.chicago.il.us/Taxa/Rhodomacul540.html]
*also written as '''''Rhodocollybia maculata'' (Albertini & Schweinitz ex Fries) Singer'''
*(This is where a post-Linnean author is given special rights (because his descriptions were comparatively complete - i.e. recognisable) so his interpretation of earlier names is taken as the sense meant by the original author. Think these used to be "apud" and are now "ex" although a colon has also been used. There are only a few sanctioning authors, the main one being Elias Fries.(Fr.) )

==More than binominals==

===Authority===
'''''Pica pica'' Linnaeus, (1758)''' on [http://en.wikipedia.org/wiki/European_Magpie Wikipedia: European Magpie]
:(i.e. named by Linnaeus in 1758)

===Unspecified species===
'''''Podiceps sp.''''' on [http://www.birdlife.org/datazone/species/index.html?action=SpcHTMDetails.asp&sid=3644&m=0 Bird Life] <pre><nowiki>Podiceps sp.</nowiki></pre>

'''Psyllid plant hopper''' [http://ramblingsofanaturalist.blogspot.com/2006/07/bay-sucker-gall-trioza-alacris.html on Ramblings of a Naturalist blog]

===Sub-species===

====Animal====
'''''Larus glaucoides kumlieni''' on [http://www.birdguides.com/html/vidlib/species/Larus_glaucoides_kumlieni.htm BirdGuides]

'''Kumlien's Gull''' on [http://www.birdsireland.com/pages/rare_bird_news/2005/january_photos.html Birds Ireland]

====Plant====
'''''Pisum sativum L. subsp. sativum''''' on [http://www.plantnames.unimelb.edu.au/Sorting/Pisum.html] (also has other examples; note lack of required italics)
<pre><nowiki>Pisum sativum L. subsp. sativum</nowiki></pre>

===Cultivars (plant)===
'''''Chamaecyparis lawsoniana 'Aureomarginata'''''' on [http://en.wikipedia.org/wiki/Cultivar Wikipedia: Cultivar]

<pre><nowiki><dd>Chamaecyparis lawsoniana 'Aureomarginata'</dd></nowiki></pre>

'''''Chamaecyparis lawsoniana'' 'Golden Wonder'''' on [http://www.plantago.nl/plantindex/c/Chamaecyparis/Chamaecyparis_4.htm plantago.nl]

====Cultivar groups (plant)====
'''''Brassica oleracea'' Botrytis Group''' on [http://en.wikipedia.org/wiki/Cultivar Wikipedia: Cultivar]

===Trade names (plant)===

'''''Rosa'' Peace''' on [http://en.wikipedia.org/wiki/Cultivar Wikipedia: Cultivar]
:("Peace" is a trade designation or "selling name" for the cultivar R. 'Madame A. Meilland' and should therefore be printed in a different typeface from the rest of the name, without any quote marks)

'''Sunflower 'Giant Single'''' on [http://cgi.www.johnsons-seeds.com/cgi-bin/www.johnsons-seeds.com/detail/azlist/S-1 Johnsons Seeds]

'''Sunflower 'Infrared' F1''' on [http://cgi.www.johnsons-seeds.com/cgi-bin/www.johnsons-seeds.com/detail/azlist/S-1 Johnsons Seeds]
:(Note "F1" cross designation)

===Variety (plant)===
'''''Pisum sativum var. macrocarpon''''' on [http://davesgarden.com/pf/go/8/index.html Dave's Garden]

====Sub-variety (plant)====

'''''Betula ermani var. genuina subvar. brevidentata''''' on [http://www.nccpg.com/gloucestershire/wilson1.html National Council for the Conservation of Plants and Gardens, Gloucestershire Group] (plus many other examples)

===Form (plant)===

'''''Acanthocalycium spiniflorum f. klimpelianum''''' on [http://en.wikipedia.org/wiki/Form_%28botany%29 Wikipedia: form (botany)]
*aka '''''Acanthocalycium spiniflorum forma klimpelianum'''''

===Sense (plant)===
'''''Ranunculus aquatilis s.l.''''' and '''''R. aquatilis s.s'''''; on [http://www.westmidlandbirdclub.com/blithfield/plants20060815.htm Blithfield Reservoir: Survey of Flowering Plants...] (see also footnotes on that page)

===Cross (plant)===
'''''Digitalis x mertonensis''''' on [http://www.hortax.org.uk/gardenplantsnames.html Hortax]
:The hybrid name for all plants derived from the cross between '''D. purpurea''' and '''D. grandiflora'''. The "x" indicates the hybrid status.

'''''× Fatshedera lizei''''' on [http://oregonstate.edu/dept/ldplants/sci-names.htm Scientific Plant Names, Oregon State Univ., Landscape Plants]

===Strain (bacteria)===
'''''Escherichia coli O157:H7''''' on [http://www.cfsan.fda.gov/~mow/chap15.html FDA.gov]

'''''E.Coli''''' on [http://news.bbc.co.uk/1/hi/england/southern_counties/5346842.stm BBC news]

==Misc==
===Superseded names===
'''''Tringa bartramia''''' superseded by '''''Bartramia longicauda''''' on [http://www.westmidlandbirdclub.com/firsts/UPLSA.htm West Midland Bird Club's Upland Sandpiper article]

===GUID===
'''NBN Taxon Key''' for European Otter, ''Lutra lutra'', on [http://nbn.nhm.ac.uk/nhm/bin/nbntaxa.dll/taxon_details?taxon_key=NBNSYS0000005133 NBN Species Dictionary]: '''NBNSYS0000005133'''

'''LSID ([http://lsid.sourceforge.net/#whatislsid Life Science Indicator])''' for ''Popillia japonica'' on [http://names.ubio.org/browser/details2.php?names=on&authors=on&sci=on&vern=on&conceptID=&expand=&namebankID=3377001 uBio]: '''urn:lsid:ubio.org:namebank:3377001'''

===Wikipedia===
'''Black-tailed Godwit''' on [http://en.wikipedia.org/wiki/Black-tailed_Godwit Wikipedia: Black-tailed Godwit]

Wikipedia uses several sets of markup, e.g. (in-line styles and links, plus some other markup, removed, for clarity):

<pre><nowiki>The Black-tailed Godwit, Limosa limosa</nowiki></pre>

and:

<pre><nowiki>
<tr>
<td>Kingdom:</td>
<td>Animalia</td>
</tr>
<tr>
<td>Phylum:</td>
<td>Chordata</td>
</tr>
<tr>
<td>Class:</td>
<td>Aves</td>
</tr>
<tr>
<td>Order:</td>
<td>Charadriiformes</td>
</tr>
<tr>
<td>Family:</td>
<td>Scolopacidae</td>
</tr>
<tr>
<td>Genus:</td>
<td>Limosa</td>
</tr>
<tr>
<td>Species:</td>
<td>L. limosa</td>
</tr>

<tr>
<th>binominal name</th>
</tr>
<tr>
<td>Limosa limosa
<td>(Linnaeus, 1758)</td>
</tr>
</nowiki></pre>

==Quantitative evidence==

For evidence of quantitative, rather than qualitative, use of species' and other taxonomic names, see [http://microformats.org/discuss/mail/microformats-discuss/2006-September/005790.html] and [http://microformats.org/discuss/mail/microformats-discuss/2006-September/005791.html]. Furthermore:

*Wikipedia:
** '''All''' species articles, e.g. [http://en.wikipedia.org/wiki/Little_Ringed_Plover Little Ringed Plover] (see [[species-examples#Wikipedia|above]])
** '''All''' genera articles, e.g. [http://en.wikipedia.org/wiki/Plover Charadrius (Plover)]
** '''All''' higher classes, e.g. [http://en.wikipedia.org/wiki/Charadriidae Charadriidae]
** '''All''' regional lists, e.g. [http://en.wikipedia.org/wiki/List_of_British_birds:_non-passerines List of British birds]
** '''All''' dedicatees, e.g. [http://en.wikipedia.org/wiki/Alexander_Wilson Alexander Wilson]
** '''All''' authorities, e.g. [http://en.wikipedia.org/wiki/Giovanni_Antonio_Scopoli Giovanni Antonio Scopoli]
** '''All''' images of living things, e.g. [http://en.wikipedia.org/wiki/Image:Charadrius_dubius_4_%28Marek_Szczepanek%29.jpg Charadrius dubius 4 (Marek Szczepanek).jpg]
** Many reserves, lakes, and other places of interest, e.g. [http://en.wikipedia.org/wiki/Belvide Belvide]
** Many biological authors and illustrators, e.g. [http://en.wikipedia.org/wiki/John_Audubon John Audubon]; [http://en.wikipedia.org/wiki/Gilbert_White Gilbert White]
** Random articles on other topics, e.g. [http://en.wikipedia.org/wiki/Balancing_lake Balancing lake}]
** '''All the above, again''', for each alternative language e.g. [http://cy.wikipedia.org/wiki/Cwtiad_Torchog_Bach Welsh]; [http://fr.wikipedia.org/wiki/Petit_gravelot French]; [http://zh.wikipedia.org/wiki/%E9%87%91%E7%9C%B6%E9%B8%BB Chinese]

*Wikimedia Commons
** '''All''' species indexes, e.g. [http://commons.wikimedia.org/wiki/Charadrius_dubius Charadrius dubius]
** '''Each individual''' image, e.g. [http://commons.wikimedia.org/wiki/Image:Charadrius_dubius_1_%28Marek_Szczepanek%29.jpg Charadrius dubius 1 (Marek Szczepanek).jpg]
** '''Each family''' list [http://commons.wikimedia.org/wiki/Charadriidae Charadriidae]

*Wiktionary
** '''All''' species articles, e.g. [http://en.wiktionary.org/wiki/american_golden_plover American Golden Plover]
** '''All''' family articles, e.g. [http://en.wiktionary.org/wiki/plover Plover]
** '''Many of the above, in other langauges''' e.g. [http://en.wiktionary.org/wiki/aquila_reale Italian]; [http://en.wiktionary.org/wiki/%D0%B1%D0%B5%D1%80%D0%BA%D1%83%D1%82 Russian]

*Wikispecies
** '''Every''' speices, e.g. [http://species.wikimedia.org/wiki/Charadrius_dubius Charadrius dubius]
** '''Every''' genus, e.g. [http://species.wikimedia.org/wiki/Charadrius Charadrius]
** '''Every''' sub-family, e.g. [http://species.wikimedia.org/wiki/Charadriinae Charadriinae]
** '''Every''' family, e.g. [http://species.wikimedia.org/wiki/Charadriidae Charadriidae]
** and so on, for '''every other rank'''
** '''Every''' image (e.g. [http://species.wikimedia.org/wiki/Image:Charadrius_hiaticula_He.jpg Charadrius hiaticula He.jpg]

*Google
**[http://www.google.co.uk/search?hl=en&hs=dBU&client=firefox-a&rls=org.mozilla:en-US:official&sa=X&oi=spell&resnum=0&ct=result&cd=1&q=%22E+coli%22&spell=1 Google finds about '''37,600,000''' for "E coli"].
***[http://www.google.co.uk/search?hs=Apo&hl=en&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&q=%22Escherichia+coli%22&btnG=Search&meta= Google finds about '''19,500,000''' for "Escherichia coli"]
***[http://www.google.co.uk/search?hs=zqo&hl=en&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&q=%22Ecoli%22&btnG=Search&meta= Google finds about '''722,000''' for "Ecoli"].
**[http://www.google.co.uk/search?hs=vWC&hl=en&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&q=%22Homo+sapiens%22&btnG=Search&meta= Google finds about '''14,200,000''' for "Homo sapiens"]
***[http://www.google.co.uk/search?hs=vWC&hl=en&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&q=%22Homo+sapien%22+-sapiens&btnG=Search&meta= Google finds about '''273,000''' for the mis-spelling "Homo sapien" -sapiens.]
**[http://www.google.co.uk/search?q=%22%22Homo+erectus%22%22&start=0&ie=utf-8&oe=utf-8&client=firefox-a&rls=org.mozilla:en-US:official Google finds about '''1,260,000''' for ""Homo erectus"]
**[http://www.google.com/search?svnum=10&as_scoring=r&hl=en&edition=us&as_drrb=q&as_qdr=&as_mind=1&as_minm=9&as_maxd=1&as_maxm=10&q=%22Clostridium+difficile%22&ie=UTF-8&sa=N&tab=nw Google finds about '''1,380,000''' for "Clostridium difficile"].
**[http://www.google.com/search?hl=en&lr=&edition=us&q=%22Passer+domesticus%22&btnG=Search Google finds about '''841,000''' for "Passer domesticus"].
***[http://images.google.com/images?hl=en&lr=&edition=us&q=%22Passer%20domesticus%22&btnG=Search&sa=N&tab=wi Google images finds about '''3,140''' for "Passer domesticus"].
**[http://www.google.co.uk/search?hl=en&hs=oEU&client=firefox-a&rls=org.mozilla:en-US:official&sa=X&oi=spell&resnum=0&ct=result&cd=1&q=%22Acer+palmatum%22&spell=1 Google finds about '''602,000''' for "Acer palmatum"]
** At the time of writing, '''every single one''' of the first 20 [http://www.google.com/search?q=%22Noctule+bat%22 Google results for "Noctule Bat"] also includes the scientific name ''Nyctalus noctula''.

*[http://www.arkive.org/ ARKive] - '''2000''' species ("It is ARKive's current aim to compile audio-visual records, where such media exists, for the 15,000-plus species currently threatened with extinction, according to the World Conservation Union's (IUCN) Red List of Threatened Species.")

*[http://www.rhs.org.uk/rhsplantfinder/plantfinder.asp Royal Horticultural Society - RHS Plant Finder] - '''70,000''' plants

*[http://www.bacterio.net List of Prokaryotic Names (formerly List of Bacterial Names)] - 2,032 *files*; '''10,268''' published names (to 2006-09-07)

*[http://nbn.nhm.ac.uk/nhm/ UK National Biodiversity Network's Species Dictionary]

*[http://www.searchnbn.net/ UK National Biodiversity Network Gateway] - '''20 million+''' species records

*[http://www.sp2000.org/ Species 2000] - '''450,000 species'''

*[http://www.bioimages.org.uk/index.html BioImages - Virtual Fieldguide] - '''53,000''' images depicting 4,600 species (see [[species-brainstorming#Malcolm_Storey|Wiki comments from site owner]])

*[http://animaldiversity.ummz.umich.edu/ Animal Diversity Web] - "'''Thousands''' of species accounts ['''plus'''] descriptions of levels of organization above the species level, especially phyla, classes, and in some cases, orders and families. Hundreds of hyperlinked pages and images illustrate the traits and general biology of these groups"

* [http://www.ubio.org/index.php?pagename=home uBio]
**NameBank is a repository of '''millions''' of recorded biological names and facts that link those names together.
**ClassificationBank stores multiple classifications and taxonomic concepts that are the result of expert opinions. It extends the functionality of NameBank.

*[http://www.birdlife.org/datazone/species/ BirdLife International] - all birds of the world (~'''10,000''')

*[http://bugguide.net/ Bug Guide] - all insects, spiders, and allies, of the USA and Canada (most with more than one page).
** e.g. [http://bugguide.net/node/view/70875 Arge pectoralis - Birch Sawfly]

*[http://www.bto.org/birdtrack/ BirdTrack]
**[http://blx1.bto.org/bt-dailyresults/results/s171-20-06.html Lapwing]

*[http://www.discoverlife.org/ Discover Life] - "contains '''306,553''' species. The Polistes Foundation and its scientific partners plan to add high-quality identification guides, maps, images, and text for '''a million species''' by 2012. [...] Each month Discover Life serves approximately 3 million pages and images to 70,000 IP addresses"

*[http://www.record-lrc.co.uk/ rECOrd] (the Local Biological Records Centre serving the Cheshire region of England) - '''1.6 million''' species records available online for the public to search and map

===Planned sites===
*[http://herbariaunited.org/atHome/ Herbaria United] (part of The website of the Botanical Collection Managers Group (BCMG), a specialist group of the Linnean Society of London) - "The UK has the world's largest and oldest collections of herbarium specimens held in trust by museums and universities. A new project is just getting underway to put all this online."

==Notable websites==
These high-profile websites use species names

*Amazon
**[http://www.amazon.co.uk/s/?url=search-alias%3Daps&field-keywords=%22house+sparrow%22 search for "House Sparrow"]

*BBC News
**[http://news.bbc.co.uk/1/hi/uk/4835208.stm Fewer birds spotted in UK gardens]
**[http://news.bbc.co.uk/1/hi/england/london/4743250.stm Study to solve sparrow's decline riddle]

*Encyclopaedia Britannica - all species, e.g.
**[http://concise.britannica.com/ebc/article-9379473/starling Starling]

*Flickr
**[http://www.flickr.com/photos/tags/citheronia/ Tag for moth genera 'citheronia']
***[http://www.flickr.com/photos/30268343@N00/152101772/ Sample result from that search]
**[http://www.flickr.com/groups/birdguide/ Field Guide: Birds of the World] 23,073 tagged photos, as at 2006-10-21

*CNN
**[http://archives.cnn.com/2001/NATURE/01/24/dying.eagles/ Disease threatens bald eagle population]

*eBay
**[http://search.ebay.com/house-sparrow search for "House Sparrow"]

*The Guardian
**[http://environment.guardian.co.uk/conservation/story/0,,1878956,00.html The call of the wildlife]
**[http://education.guardian.co.uk/higher/news/story/0,,1665396,00.html Sparrow joins 'raped' duck in Dutch museum] (note improper capitalisation "''passer domesticus''")

*London Zoo
**[http://www.zsl.org/london-zoo/animals/birds/tawny-frogmouth,99,AN.html Tawny frogmouth]

*Microsoft
**[http://www.microsoft.com/games/zootycoon/zoo2/zoo2_ymi_animals1.asp Zoo Tycoon]

*MSN-Encarta - all species, e.g.
**[http://encarta.msn.com/encnet/refpages/search.aspx?q=vulgaris&Submit2=Go Search for "vulgaris"]

*MySpace
**[http://blog.myspace.com/index.cfm?fuseaction=blog.view&friendID=47134278&blogID=79591637]

*Nature
**[http://www.nature.com/nature/focus/avianflu/index.html Avian flu web focus]

*Nature Network, Boston
**[http://network.nature.com/boston/news/archive/2006/06/13/the-student-and-the-squid The student and the squid] '''N.B.''' site already supports rel-tag, hCard for user profiles and hCalendar for marking up events across the site.

*NASA
**[http://history.nasa.gov/SP-401/ch3.htm SP-401 Skylab, Classroom in Space. Part II - Student Experiments] ("The common Cross spider (Araneus diadematus)")

*New York Times
**[http://query.nytimes.com/gst/fullpage.html?sec=travel&res=9D04E4DE1131F93BA25751C0A9669C8B63 Where the Eagles Fly: Seeing the National Symbol]

*Snopes (Urban Legends Reference Pages)
**[http://www.snopes.com/photos/animals/fishfly.asp Fish Fly]

*United Kingdom Government
**[http://www.defra.gov.uk/wildlife-countryside/vertebrates/gen-licence.htm DEFRA: General licences under the Wildlife & Countryside Act 1981]

*United States of America Government
**ITIS, e.g. [http://www.itis.usda.gov/servlet/SingleRpt/SingleRpt?search_topic=TSN&search_value=179628 Passer Domesticus] - "authoritative taxonomic information on plants, animals, fungi, and microbes of North America and the world"

*W3C
**[http://dev.w3.org/cvsweb/2000/10/swap/test/ferrell/biology.n3?rev=1.4 An Ontology of Biology]
**[http://esw.w3.org/topic/HCLSIG_BioRDF_Subgroup/Tasks/Reagents/Status_Reports/2006-05-04 BioRDF Sub-group Status Report, 4 May 2006]

*Yahoo Groups
**[http://tech.groups.yahoo.com/group/passerdomesticus/ passerdomesticus] species as group name!

==Breaking news==
*[http://news.bbc.co.uk/1/shared/spl/hi/pop_ups/06/sci_nat_orchid_spectacular/html/1.stm BBC News: Stunning new orchids from Asia's rainforest] - 2006-10-16
*[http://news.bbc.co.uk/1/hi/sci/tech/6045802.stm BBC News: Winter home find cheers twitchers] (winter home of the northern bald ibis found) - 2006-10-13
*[http://news.bbc.co.uk/1/hi/sci/tech/6043648.stm BBC News: New mouse find is 'living fossil'] - 2006-10-12
*[http://news.bbc.co.uk/1/hi/sci/tech/6035113.stm BBC News: Giant camel fossil found in Syria] - 2006-10-10
*[http://news.bbc.co.uk/1/hi/sci/tech/5414410.stm BBC News: Sharks swim into political waters] - 2006-10-06
*[http://news.bbc.co.uk/1/hi/sci/tech/5403570.stm BBC News: 'Monster' fossil find in Arctic] - 2006-10-05

==Use in blogs==
*[http://technorati.com/search/%22passer%20domesticus%22 Technorati search for "Passer domesticus"] (367 found, as at 2006-09-25)
*[http://technorati.com/search/%22acer%20palmatum%22 Technorati search for "Acer palmatum"] (682 found, as at 2006-09-25)
*[http://technorati.com/search/%22Homo%20sapiens%22 Technorati search for "Homo sapiens"] (40,932 found, as at 2006-09-25)
*[http://technorati.com/search/birding Technorati search for "birding"] (26,472 found, as at 2006-09-25)
*[http://ramblingsofanaturalist.blogspot.com/ Ramblings of a Naturalist]
*[http://squaremetre1.blogspot.com/ The Square Metre]
*[http://windowboxwildlife.blogspot.com/index.html Windowbox Wildlife]
*[http://www.rxwildlife.org.uk/ RXWildlife]

==And finally...==
Gary Larson, in his book ''The Far Side Gallery'' (Warner Books, 1980, ISBN 0751502367) has a cartoon, showing two entomologists sitting down to eat dinner in a jungle. One says to the other "Hey! What's this ''Drosophila melanogaster'' doing in my soup?"

==Contributors==
*[[User:AndyMabbett|Andy Mabbett]] (proponent)
*Malcolm Storey (per e-mail)
*[[User:SXBRC|Charles Roper]], [http://www.sxbrc.org.uk/ Sussex Biodiversity Record Centre] (proponent)
*[[User:SteveMcBill|Steve McWilliam]], [http://www.rECOrd-LRC.co.uk/ rECOrd - The Biodiversity Information System for the Cheshire region] (proponent)

==See also==
[[species-brainstorming]]

mailing-lists

2006-10-21T23:09:35Z

BenWest: changed my vote away from "nothing"; added microformats-work as a suggestion for the purpose of working on microformats new and old.

<h1> Mailing Lists </h1>

Read the [http://microformats.org/discuss/ microformats discuss page] first.

Then read the [http://microformats.org/mailinglists-policies/ mailing list policies].

Ok, now here are some additional notes of scope and topics for each list.

__TOC__

== microformats-discuss ==
A mailing list for general discussion of microformats, with a strong leaning towards:

* starting out with microformats
* real-world content authoring

=== good topics for discussion ===
Here is a list (certainly not definitive) of good topics which are appropriate for the microformats-discuss mailing list:

* general thoughts on the design and use of semantic XHTML markup
* how to use and write microformats in content
* how to use microformat design patterns in content

=== good topics that belong somewhere else ===
* see [http://microformats.org/wiki/mailing-lists#good_topics_for_discussion_2 microformats-dev good topics for discussion]

=== bad topics for discussion ===

AKA topics better discussed elsewhere (somewhere other than microformats.org).

Here is a list (also not definitive) of topics which are undesired and inappopriate for the microformats-discuss mailing list. In fact, they're not even worth the time to bother discussing, so please do not bring them up on the microformats-discuss mailing list. We'll add more topics as people come up with more off-topic or out-of-scope or rathole topics.

# '''How to make a "general purpose" (micro)format.''' Go read [http://microformats.org/wiki/microformats#microformats_are_not what microformats are not], actually, go read the entire [[microformats|principles]] page. Sometimes this may masquerade as a "format of formats". Either way, it is one of those boil the ocean ratholes which are far outside the focus of microformats. If you really want to work on such subjects, teach yourself DTD (SGML, XML), XML Schema, Relax NG, RDF Schema, and find the communities working on those technologies.
# '''Using namespaces and namespace prefixes.''' In short, namespaces are neither necessary (the Internet ran just fine without them for decades, go read some RFCs), nor desirable (prefixes make formats far uglier and more difficult to hand-code). See also [[namespaces-considered-harmful]].
# '''Using non-English names for properties'''. This was briefly discussed on the microformats-discuss list most recently as "Language Maps" but has been raised before that. Some folks have raised the issue that microformats use English names for properties, and they would like alternate (non-English) names in other (natural) languages, and perhaps try to establish a mapping between them. As microformats property names are based on existing standards (see [[process]], and [[naming-principles]]), this is another problem that is far outside the scope of microformats. As Ryan King put it, this is a pre-existing (unsolved) "problem" with English-based HTML, the English-based CSS, the English-based HTTP and so on. Note that this is NOT about the internationalization (i18n) of the content and data itself - which is of course an excellent goal, advocated and promoted by microformats and the standards they are based on (e.g. W3C, IETF). This is purely about the names of the properties (and enumerated values) in the formats.

== microformats-dev ==
For discussion of microformats development, with a leaning towards:

* anything that involves writing code
* abstractions / models (in contrast to actual content)

=== good topics for discussion ===
These tend to be topics that belong in microformats-dev instead of microformats-discuss. This list is also not definitive, but illustrates the general areas:

* microformat parsing
* microformat "(auto)-discovery"
* comparisons of microformats with other data abstractions or data representations (e.g. XML, RDF)
* compatibility/interoperability of microformats with other data abstractions or data representations

Formerly, the membership to this list was moderated and limited to people who had demonstrated public implementations of microformats. We've since relaxed this requirement, yet maintain the same expectations that people involved in the discussion are focused on concrete and pragmatic topics related to writing code using microformats.

== microformats-rest ==
For discussion of use of microformats with [http://en.wikipedia.org/wiki/Representational_State_Transfer REST], in protocols, services, APIs etc.

== how to search the mailing list archives ==
If your post to the list starts off "I'm new to the list and microformats so I don't know if you've discussed this already" READ THROUGH THE [http://microformats.org/discuss/mail/microformats-discuss/ ARCHIVES]!

The archives are getting larger, so here are a few simple ways you can search them. Most popular search engines imploy some sort of site based results filtering. Google does this in your initial search. Type "site:http://microformats.org/discuss/ <search terms here>" to limit the search results to only our discussion list. This will help you from asking a question that has already been posted, debated, and possibly resolved. It saves everyone time and energy!

== new list proposal ==

There is a proposal for creating a new 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
* microformats-research (focusing on the essential, and often overlooked by first-time proposers "research" phase(s) in the process)
** +1 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)
* microformats-process (That's really what we're talking about with research of new microformats, isn't it?)
** +1 ScottReynen
** +1 Lachlan Hunt
** -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)
* microformats-propose (it misses the point of the process, and implies that there is a desire for microformats proposals - there isn't)
** -1 tantek
** -1 ScottReynen
** 0 Andy Mabbett
** -1 Bob Jonkman
** -1 Ben Ward
* microformats-suggest (similar to propose but milder ;)
** +1 ChrisMessina
** 0 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)
* nothing (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.)
* 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.

faq

2006-10-18T19:25:36Z

BenWest: /* Q. ''How will microformat class names impact page size?'' */ test todo's

<h1> Microformats FAQ </h1>

This page document frequently asked questions about microformats. For frequently asked questions from the [[press]], see [[press-faq]].

__TOC__

== Wiki specific questions ==
===Q: ''How do I create a username? Why won't it let me use my preferred username?''===

A: First, read this: http://en.wikipedia.org/wiki/Wikipedia:Username . Second, real names are preferred to pseudonyms/handles etc. Real names encourage better transparency and accountability. Third, the most common problem creating a user name is forgetting to caplitalize the first letter of the user name. Try using a WikiCase version of your full name as username, e.g. RyanKing.

== Email list ==
===Q: ''I've joined the discussion mailing list but am not seeing my replies anywhere. Why?''===

A: There is no moderation on microformats-discuss, but it only accepts posts from subscribers. You MUST post to microformats-discuss using the email address you used to subscribe.

== Basic Microformat Questions ==
===Q: ''When should I use a microformat? What are they for?"===

A: You are writing some HTML that contains useful human-readable information (such as a piece of contact information). You say to yourself: I would like to mark this up with some classes now for styling. You look up the relevant microformat, and you
pull in the standard names. You don't have to make your own up, and now your page is machine-readable too. Bonus!

Microformats are designed to make the data you already publish for humans available to machines. It allows applications as simple as cut-and-paste or as complex as a seach engine to use your data effectively.

===Q: ''Are microformats dependent upon (X)HTML?''===

A: Microformats are made to be embeddable. They can be embedded in (X)HTML, RSS, Atom or anywhere (X)HTML is allowed.

===Q: ''Microformats sound great. How can I help?''===

A: Take a look at http://microformats.org/discuss to see some ways to join the conversations about microformats, and the [[to-do]] list for things to help out with.

===Q: ''I'd like to make a donation to the microformat cause. How can I do this?''===

A: Thank you for your willingness to support microformats. We've only recently started this site and have decided that while we are figuring out exactly how to accept donations, we will be passing along donations to other good causes. Please consider donating to another cause like Red Cross, perhaps directed to help victims of recent natural disasters.

===Q: ''Which microformats have been implemented?'' ===

A: See the [[implementations]] page.

===Q: ''Which microformats should I implement?''===

A: Chances are you that your website already has data very similar to several microformats. For example, you probably have people and/or their contact information somewhere. That information could be marked up with [[hcard|hCard]], see the [[hcard-authoring|hCard authoring]] page for step by step instructions. If you are publishing press releases, try using [[hatom|hAtom]].

===Q: ''Do you have any link badges I can add to my website/blog?''===

A: There are some [[buttons]] but we can certainly use more! Please contribute what you come up with!

===Q. ''Are there any tools that support microformats?''===

A. Yes...tons... [[implementations]].

===Q. Is there a way to indicate that a given web page contains markup that conforms to one or more microformats? ===

A. The HTML HEAD element's '<code>profile</code>' attribute alerts applications to the potential presence of microformats. The [http://www.w3.org/TR/1999/REC-html401-19991224/struct/global.html#h-7.4.4.3 W3C HTML Specification] describes more about the profile attribute, and the [http://gmpg.org/xmdp/description XMDP description] documents how it is used.

===Q. ''What about using new URI schemes instead of class names, e.g. for geo information?''===

A. In general, it is more work, and less content-publisher friendly, to ask publishers to use URI schemes instead of class names.

Authors aren't publishing links to geo information.

They're publishing *visible text* of [[geo]] information.

So the easiest thing to do, for the author, is to leave it as visible text.

Thus, it makes the most sense to do the simple thing of just wrapping that
visible text with a little bit of markup, rather than asking the author to
move (or copy) it into an attribute, which may or may not require a
reformatting of the data as well.

It would make sense from a usability persepective to hyperlink geo information to a maps page or something, so that clicking it actually does something. If you forced them to use a hypothetical "geo:" protocol instead, then that would interfere, since you can only hyperlink something to one destination.

===Q: ''Who controls microformats?''===

A: An open community. Microformats are open standards licensed under Creative Commons Attribution. Much of the work here was begun on [[http://developers.technorati.com/wiki Technorati's Developer Wiki]], but Technorati has since divested control of these microformat standards to the open community here. The microformats.org domain is registered to Rohit Khare, CommerceNet is graciously hosting the servers, but claims no control over microformat standards. Anyone may follow the established [[process]] and contribute towards the development of microformat standards.

===Q: ''Who is the registrar for microformats?''===

A: There is no central registry. Microformats are registered in a distributed manner using profiles. For more information on profiles see http://microformats.org/wiki/profile-uris and http://gmpg.org/xmdp/

Conflicts and interoperability are managed through social processes rather than a formal registry. Current microformat profiles can be found at http://gmpg.org, http://w3.org, and http://microformats.org.

===Q: ''So multiple microformats with the same name can be valid?''===

A: Yes. The community at microformats.org can hopefully play a role in determining which is preferred by bringing interested folks together in one place and helping them resolve that question. As long as each microformat maintains a valid profile, each can be used effectively.

===Q: ''How do I validate my microformated content?''===

A: Currently there is not an automatic general-purpose validator for microformats (See [[to-do]]). There are however some microformat specific tools listed on the [[implementations]] page.

== Creating and Suggesting New Microformats ==

===Q. ''I would like to author a new microformats open standards specification for my site/business. How do I get started?''===

A. The first thing to do before attempting a new microformat open standard is to make as much use of existing [[microformats]] open standards as possible in whatever site you are looking to markup with your new microformat, as a way of learning what is left to be done. That is, at a minimum first:
* Markup all people and organizations as [[hcard|hCards]].
* Markup all events and time based things as [[hcalendar|hCalendar]] events.
* Markup all reviews as [[hreview|hReviews]].
* etc.
Then join the microformats [http://microformats.org/discuss discuss list], and ask folks what they think of your use of the microformats and if it can be improved.

From that experience you will then be able to figure out what is left to be specified. Otherwise it is too hard to approach the "whole problem".

Once you have completed that, take a look at the microformats [[process]] for how to walk through the steps of creating a new microformat, and note the specific problem you are trying to solve to the microformats-discuss list. This will help you find more people to help you solve the problems you are trying to solve.

===''Q How do I know if an idea for a Microformat has already been suggested in the past?''===

A. Check the list of proposed and rejected microformats.
* [[rejected-formats]]

== Specific Microformat Questions ==
If you have a question regarding a specific microformat, you may want to check the FAQ specific to that microformat.
* [[hatom-faq]]
* [[hcalendar-faq]]
* [[hcard-faq]]
* [[hreview-faq]]
* [[rel-faq]]
* [[rel-tag-faq]]
* [http://gmpg.org/xfn/faq xfn-faq]
* [[xfolk-faq]]
* [[xmdp-faq]]
* [[xoxo-faq]]

== Class interactions ==

===Q. ''Are there issues with page styling when specific class values are used?''===

A. There might be. However, any such issues can be easily (trivially) worked around by using contextual selectors.

===Q. ''How does the use of class values for semantics interact with the use of class values for attaching CSS styles?''===

A. The class attribute takes a space separated set of class names [http://www.w3.org/TR/REC-html40/struct/global.html#h-7.5.2 HTML4 reference]. Thus both author and microformat defined class names may be used in the same class attribute. In addition, microformat class names provide the author with a consistent set of class names to use for styling. If the author is already using using specific class names, they can continue to do so, and include microformat class names. If the author is already using a class name that happens to also be a microformat class name, then the author may want to consider using contextual CSS class selectors to make sure that avoid any unintentional styling effects.

See also:
* [http://tantek.com/log/2002/12.html#L20021216 A Touch Of Class]
* [http://tantek.com/log/2004/07.html#classmeaningnotshow Class For Meaning Not For Show]
* [http://www.meyerweb.com/eric/thoughts/2004/07/18/competent-classing Competant Classing], by Eric Meyer for discussion of choosing class names in (X)HTML
* [http://www.microformats.org/blog/2005/10/19/more-than-styling/ Class attributes are about more than styling] - Ryan King dispells common misconceptions about the ''HTML'' class attribute.

== <code><div></code> and <code></code> semantics ==

===''Q. Is it semantically meaningless to use divs?'' ===

A. Yes, both <code><div></code> and <code></code> have nearly no semantics. <code><div></code> can be used to represent a "division" of the page content. Similarly <code></code> can be used to reperesent that that "span" of text has some meaning, but the specifics of what that meaning is undefined by the <code></code>.

===''Q. Does the use of <code><div></code> and <code></code> elements add any semantics to web pages?''===

A. According to the [http://www.w3.org/TR/REC-html40/struct/global.html#h-7.5.4 spec], <code><div></code> and <code></code> "offer a generic mechanism for adding structure to documents." Their only meaning is in dividing documents into sections, and as such, their presence implies that the content within has a specific, but undefined by the element markup, semantic. Thus they are nearly semantic-free.

===''Q. Why do the examples on the wiki use <code class="element"></code> and <code class="element"><div></code> for nearly everything?''===

A. <code class="element"></code> and <code class="element"><div></code> are generic elements in HTML. When you use microformats, you should pick the most specific semantic element available for the semantics you are trying to express.

== Class semantics ==

===Q. ''How will microformat class names impact page size?''===

A. You probably won't notice any impact on page size when authoring with microformats. Our experience is that people use comparably sized class names, and semantic class names are now considered an industry best practice. Some sites are successfully publishing millions of microformats, and we haven't heard any complaints yet. You are more likely to gain space savings by more fully adopting the principles of microformats Add link to microformats principles., and eliminating tables for layout.
Consider creating a new section for web authoring tips? Or at least linking to another site that advocates good authorship.

===Q. ''Can an element have more than one class''===

A. Yes, the class attribute can contain a space delimited list of classes. For example:
Write high quality and simple software.
Add link to w3c.

===Q. ''Do (X)HTML class names have semantics?''===

A. The HTML4 specification does not define any particular class values [http://www.w3.org/TR/REC-html40/struct/global.html#h-7.5.2 REF], nor does it define any particular semantic for class values [http://www.w3.org/TR/REC-html40/struct/global.html#h-7.5.2 REF], except that they "may be used for general user agent processing" [http://www.w3.org/TR/REC-html40/struct/global.html#h-7.5.2 REF]. However, the [http://www.w3.org/TR/WD-htmllink-970328#profile" draft of "Hypertext Links in HTML"], allows for a "profile" to define meanings for those classes. [http://gmpg.org/xmdp/ XMDP] is a format for defining meta data profiles for (X)HTML, and thus an XMDP profile can be used to define the meanings of class names.

See also:
* [http://tantek.com/log/2002/12.html#L20021216 A Touch Of Class]
* [http://www.w3.org/TR/WD-htmllink-970328 Hypertext Links in HTML]

===Q. ''I thought one of the main goals of CSS was to separate data from presentation. Isn’t this sneaking presentation back into data?''===

A. This is a quite commonly expressed objection to the way microformats uses class, but it's based on a misunderstanding of the way the class attribute in HTML was designed. Yes, class is very commonly,and appropriately used by web designers in conjunction with CSS to style pages, and in truth, it is often overused for that, but despite this, class, according to the HTML specification "has several roles in HTML", including [http://www.w3.org/TR/html4/struct/global.html#h-7.5.2 "for general purpose processing by user agents"].

Microformats utilize this second aspect of the class (and id) attribute, and do so legitimately. It is not an abuse of the class or id attribute to use it to add semantic context to a document. Nor is the use of class in and of itself presentational - in fact, it is an important mechanism for separating presentation from structured content.

For some more on using class semantically, here are some articles

* [http://meyerweb.com/eric/thoughts/2004/07/18/competent-classing Competent Classing by Eric Meyer]
* [http://www.w3.org/QA/Tips/goodclassnames Use class with semantics in mind, W3C]
* [http://tantek.com/log/2004/07.html#d20t2359 More about the class attribute, Tantek Çelik]

== Microformats and Spam ==
===''Q. Given that Google now looks at hidden content as potential spam, will invisible microformats be considered spam?''===

A. It is advisable not to hide information in your site, regardless of whether it is microformated or not. Microformats provide a mechanism for marking up ''visible'' content. Any mechanism for embedding ''invisible'' or hidden content risks being considered spam due to the fact that invisible (meta)data inevitably ends up being abused. Avoid invisible (meta)data. Publish visible data.

== Design Patterns with Abbr & Title ==
===''Q. Why is ABBR being used when the title attribute is available on all HTML elements?''===

In the datetime design pattern the title attribute is used for the value of the property and the node value is used as the display value. <abbr title="value-here">Display-Here</abbr>.

A. The short answer is that <abbr> has the correct semantics.

The longer answer is that the value is often an abbreviated version of the formal value. Of course, if you don't want to use an <abbr>, you can use another element like this:

<abbr title="2006-12-31T12:59:59Z" class="dtstamp">New Year</abbr>

2006-12-31T12:59:59Z

In addition, microformats encourage the content to be visible and thus prefer the text of an element rather than using the 'title' attribute or any other less visible alternative. The exception is made for datetimes and abbr due to the fact that microformats are for humans first, machines second. Thus the content of the abbr element is used to provide human visible content and the machine equivalent is placed in the less visible (but still easily verifiable) 'title' attribute.

== Nesting of elements ==
===''Q. It seems that ... should work. Why is this incorrect?''===

A. See [http://microformats.org/wiki/hcard-faq#nesting-properties]

faq

2006-10-18T18:57:05Z

BenWest: /* Class semantics */

<h1> Microformats FAQ </h1>

This page document frequently asked questions about microformats. For frequently asked questions from the [[press]], see [[press-faq]].

__TOC__

== Wiki specific questions ==
===Q: ''How do I create a username? Why won't it let me use my preferred username?''===

A: First, read this: http://en.wikipedia.org/wiki/Wikipedia:Username . Second, real names are preferred to pseudonyms/handles etc. Real names encourage better transparency and accountability. Third, the most common problem creating a user name is forgetting to caplitalize the first letter of the user name. Try using a WikiCase version of your full name as username, e.g. RyanKing.

== Email list ==
===Q: ''I've joined the discussion mailing list but am not seeing my replies anywhere. Why?''===

A: There is no moderation on microformats-discuss, but it only accepts posts from subscribers. You MUST post to microformats-discuss using the email address you used to subscribe.

== Basic Microformat Questions ==
===Q: ''When should I use a microformat? What are they for?"===

A: You are writing some HTML that contains useful human-readable information (such as a piece of contact information). You say to yourself: I would like to mark this up with some classes now for styling. You look up the relevant microformat, and you
pull in the standard names. You don't have to make your own up, and now your page is machine-readable too. Bonus!

Microformats are designed to make the data you already publish for humans available to machines. It allows applications as simple as cut-and-paste or as complex as a seach engine to use your data effectively.

===Q: ''Are microformats dependent upon (X)HTML?''===

A: Microformats are made to be embeddable. They can be embedded in (X)HTML, RSS, Atom or anywhere (X)HTML is allowed.

===Q: ''Microformats sound great. How can I help?''===

A: Take a look at http://microformats.org/discuss to see some ways to join the conversations about microformats, and the [[to-do]] list for things to help out with.

===Q: ''I'd like to make a donation to the microformat cause. How can I do this?''===

A: Thank you for your willingness to support microformats. We've only recently started this site and have decided that while we are figuring out exactly how to accept donations, we will be passing along donations to other good causes. Please consider donating to another cause like Red Cross, perhaps directed to help victims of recent natural disasters.

===Q: ''Which microformats have been implemented?'' ===

A: See the [[implementations]] page.

===Q: ''Which microformats should I implement?''===

A: Chances are you that your website already has data very similar to several microformats. For example, you probably have people and/or their contact information somewhere. That information could be marked up with [[hcard|hCard]], see the [[hcard-authoring|hCard authoring]] page for step by step instructions. If you are publishing press releases, try using [[hatom|hAtom]].

===Q: ''Do you have any link badges I can add to my website/blog?''===

A: There are some [[buttons]] but we can certainly use more! Please contribute what you come up with!

===Q. ''Are there any tools that support microformats?''===

A. Yes...tons... [[implementations]].

===Q. Is there a way to indicate that a given web page contains markup that conforms to one or more microformats? ===

A. The HTML HEAD element's '<code>profile</code>' attribute alerts applications to the potential presence of microformats. The [http://www.w3.org/TR/1999/REC-html401-19991224/struct/global.html#h-7.4.4.3 W3C HTML Specification] describes more about the profile attribute, and the [http://gmpg.org/xmdp/description XMDP description] documents how it is used.

===Q. ''What about using new URI schemes instead of class names, e.g. for geo information?''===

A. In general, it is more work, and less content-publisher friendly, to ask publishers to use URI schemes instead of class names.

Authors aren't publishing links to geo information.

They're publishing *visible text* of [[geo]] information.

So the easiest thing to do, for the author, is to leave it as visible text.

Thus, it makes the most sense to do the simple thing of just wrapping that
visible text with a little bit of markup, rather than asking the author to
move (or copy) it into an attribute, which may or may not require a
reformatting of the data as well.

It would make sense from a usability persepective to hyperlink geo information to a maps page or something, so that clicking it actually does something. If you forced them to use a hypothetical "geo:" protocol instead, then that would interfere, since you can only hyperlink something to one destination.

===Q: ''Who controls microformats?''===

A: An open community. Microformats are open standards licensed under Creative Commons Attribution. Much of the work here was begun on [[http://developers.technorati.com/wiki Technorati's Developer Wiki]], but Technorati has since divested control of these microformat standards to the open community here. The microformats.org domain is registered to Rohit Khare, CommerceNet is graciously hosting the servers, but claims no control over microformat standards. Anyone may follow the established [[process]] and contribute towards the development of microformat standards.

===Q: ''Who is the registrar for microformats?''===

A: There is no central registry. Microformats are registered in a distributed manner using profiles. For more information on profiles see http://microformats.org/wiki/profile-uris and http://gmpg.org/xmdp/

Conflicts and interoperability are managed through social processes rather than a formal registry. Current microformat profiles can be found at http://gmpg.org, http://w3.org, and http://microformats.org.

===Q: ''So multiple microformats with the same name can be valid?''===

A: Yes. The community at microformats.org can hopefully play a role in determining which is preferred by bringing interested folks together in one place and helping them resolve that question. As long as each microformat maintains a valid profile, each can be used effectively.

===Q: ''How do I validate my microformated content?''===

A: Currently there is not an automatic general-purpose validator for microformats (See [[to-do]]). There are however some microformat specific tools listed on the [[implementations]] page.

== Creating and Suggesting New Microformats ==

===Q. ''I would like to author a new microformats open standards specification for my site/business. How do I get started?''===

A. The first thing to do before attempting a new microformat open standard is to make as much use of existing [[microformats]] open standards as possible in whatever site you are looking to markup with your new microformat, as a way of learning what is left to be done. That is, at a minimum first:
* Markup all people and organizations as [[hcard|hCards]].
* Markup all events and time based things as [[hcalendar|hCalendar]] events.
* Markup all reviews as [[hreview|hReviews]].
* etc.
Then join the microformats [http://microformats.org/discuss discuss list], and ask folks what they think of your use of the microformats and if it can be improved.

From that experience you will then be able to figure out what is left to be specified. Otherwise it is too hard to approach the "whole problem".

Once you have completed that, take a look at the microformats [[process]] for how to walk through the steps of creating a new microformat, and note the specific problem you are trying to solve to the microformats-discuss list. This will help you find more people to help you solve the problems you are trying to solve.

===''Q How do I know if an idea for a Microformat has already been suggested in the past?''===

A. Check the list of proposed and rejected microformats.
* [[rejected-formats]]

== Specific Microformat Questions ==
If you have a question regarding a specific microformat, you may want to check the FAQ specific to that microformat.
* [[hatom-faq]]
* [[hcalendar-faq]]
* [[hcard-faq]]
* [[hreview-faq]]
* [[rel-faq]]
* [[rel-tag-faq]]
* [http://gmpg.org/xfn/faq xfn-faq]
* [[xfolk-faq]]
* [[xmdp-faq]]
* [[xoxo-faq]]

== Class interactions ==

===Q. ''Are there issues with page styling when specific class values are used?''===

A. There might be. However, any such issues can be easily (trivially) worked around by using contextual selectors.

===Q. ''How does the use of class values for semantics interact with the use of class values for attaching CSS styles?''===

A. The class attribute takes a space separated set of class names [http://www.w3.org/TR/REC-html40/struct/global.html#h-7.5.2 HTML4 reference]. Thus both author and microformat defined class names may be used in the same class attribute. In addition, microformat class names provide the author with a consistent set of class names to use for styling. If the author is already using using specific class names, they can continue to do so, and include microformat class names. If the author is already using a class name that happens to also be a microformat class name, then the author may want to consider using contextual CSS class selectors to make sure that avoid any unintentional styling effects.

See also:
* [http://tantek.com/log/2002/12.html#L20021216 A Touch Of Class]
* [http://tantek.com/log/2004/07.html#classmeaningnotshow Class For Meaning Not For Show]
* [http://www.meyerweb.com/eric/thoughts/2004/07/18/competent-classing Competant Classing], by Eric Meyer for discussion of choosing class names in (X)HTML
* [http://www.microformats.org/blog/2005/10/19/more-than-styling/ Class attributes are about more than styling] - Ryan King dispells common misconceptions about the ''HTML'' class attribute.

== <code><div></code> and <code></code> semantics ==

===''Q. Is it semantically meaningless to use divs?'' ===

A. Yes, both <code><div></code> and <code></code> have nearly no semantics. <code><div></code> can be used to represent a "division" of the page content. Similarly <code></code> can be used to reperesent that that "span" of text has some meaning, but the specifics of what that meaning is undefined by the <code></code>.

===''Q. Does the use of <code><div></code> and <code></code> elements add any semantics to web pages?''===

A. According to the [http://www.w3.org/TR/REC-html40/struct/global.html#h-7.5.4 spec], <code><div></code> and <code></code> "offer a generic mechanism for adding structure to documents." Their only meaning is in dividing documents into sections, and as such, their presence implies that the content within has a specific, but undefined by the element markup, semantic. Thus they are nearly semantic-free.

===''Q. Why do the examples on the wiki use <code class="element"></code> and <code class="element"><div></code> for nearly everything?''===

A. <code class="element"></code> and <code class="element"><div></code> are generic elements in HTML. When you use microformats, you should pick the most specific semantic element available for the semantics you are trying to express.

== Class semantics ==

===Q. ''How will microformat class names impact page size?''===

A. You probably won't notice any impact on page size when authoring with microformats. Our experience is that people use comparably sized class names, and semantic class names are now considered an industry best practice. Some sites are successfully publishing millions of microformats, and we haven't heard any complaints yet. You are more likely to gain space savings by more fully adopting the principles of microformats Add link to microformats principles., and eliminating tables for layout.
Consider creating a new section for web authoring tips? Or at least linking to another site that advocates good authorship.

===Q. ''Can an element have more than one class''===

A. Yes, the class attribute can contain a space delimited list of classes. For example:
Write high quality and simple software.
Add link to w3c.

===Q. ''Do (X)HTML class names have semantics?''===

A. The HTML4 specification does not define any particular class values [http://www.w3.org/TR/REC-html40/struct/global.html#h-7.5.2 REF], nor does it define any particular semantic for class values [http://www.w3.org/TR/REC-html40/struct/global.html#h-7.5.2 REF], except that they "may be used for general user agent processing" [http://www.w3.org/TR/REC-html40/struct/global.html#h-7.5.2 REF]. However, the [http://www.w3.org/TR/WD-htmllink-970328#profile" draft of "Hypertext Links in HTML"], allows for a "profile" to define meanings for those classes. [http://gmpg.org/xmdp/ XMDP] is a format for defining meta data profiles for (X)HTML, and thus an XMDP profile can be used to define the meanings of class names.

See also:
* [http://tantek.com/log/2002/12.html#L20021216 A Touch Of Class]
* [http://www.w3.org/TR/WD-htmllink-970328 Hypertext Links in HTML]

===Q. ''I thought one of the main goals of CSS was to separate data from presentation. Isn’t this sneaking presentation back into data?''===

A. This is a quite commonly expressed objection to the way microformats uses class, but it's based on a misunderstanding of the way the class attribute in HTML was designed. Yes, class is very commonly,and appropriately used by web designers in conjunction with CSS to style pages, and in truth, it is often overused for that, but despite this, class, according to the HTML specification "has several roles in HTML", including [http://www.w3.org/TR/html4/struct/global.html#h-7.5.2 "for general purpose processing by user agents"].

Microformats utilize this second aspect of the class (and id) attribute, and do so legitimately. It is not an abuse of the class or id attribute to use it to add semantic context to a document. Nor is the use of class in and of itself presentational - in fact, it is an important mechanism for separating presentation from structured content.

For some more on using class semantically, here are some articles

* [http://meyerweb.com/eric/thoughts/2004/07/18/competent-classing Competent Classing by Eric Meyer]
* [http://www.w3.org/QA/Tips/goodclassnames Use class with semantics in mind, W3C]
* [http://tantek.com/log/2004/07.html#d20t2359 More about the class attribute, Tantek Çelik]

== Microformats and Spam ==
===''Q. Given that Google now looks at hidden content as potential spam, will invisible microformats be considered spam?''===

A. It is advisable not to hide information in your site, regardless of whether it is microformated or not. Microformats provide a mechanism for marking up ''visible'' content. Any mechanism for embedding ''invisible'' or hidden content risks being considered spam due to the fact that invisible (meta)data inevitably ends up being abused. Avoid invisible (meta)data. Publish visible data.

== Design Patterns with Abbr & Title ==
===''Q. Why is ABBR being used when the title attribute is available on all HTML elements?''===

In the datetime design pattern the title attribute is used for the value of the property and the node value is used as the display value. <abbr title="value-here">Display-Here</abbr>.

A. The short answer is that <abbr> has the correct semantics.

The longer answer is that the value is often an abbreviated version of the formal value. Of course, if you don't want to use an <abbr>, you can use another element like this:

<abbr title="2006-12-31T12:59:59Z" class="dtstamp">New Year</abbr>

2006-12-31T12:59:59Z

In addition, microformats encourage the content to be visible and thus prefer the text of an element rather than using the 'title' attribute or any other less visible alternative. The exception is made for datetimes and abbr due to the fact that microformats are for humans first, machines second. Thus the content of the abbr element is used to provide human visible content and the machine equivalent is placed in the less visible (but still easily verifiable) 'title' attribute.

== Nesting of elements ==
===''Q. It seems that ... should work. Why is this incorrect?''===

A. See [http://microformats.org/wiki/hcard-faq#nesting-properties]

faq

2006-10-18T18:44:59Z

BenWest: /* Class semantics */ fixed an example regarding multiple classnames. there are still todo's left in this faq

<h1> Microformats FAQ </h1>

This page document frequently asked questions about microformats. For frequently asked questions from the [[press]], see [[press-faq]].

__TOC__

== Wiki specific questions ==
===Q: ''How do I create a username? Why won't it let me use my preferred username?''===

A: First, read this: http://en.wikipedia.org/wiki/Wikipedia:Username . Second, real names are preferred to pseudonyms/handles etc. Real names encourage better transparency and accountability. Third, the most common problem creating a user name is forgetting to caplitalize the first letter of the user name. Try using a WikiCase version of your full name as username, e.g. RyanKing.

== Email list ==
===Q: ''I've joined the discussion mailing list but am not seeing my replies anywhere. Why?''===

A: There is no moderation on microformats-discuss, but it only accepts posts from subscribers. You MUST post to microformats-discuss using the email address you used to subscribe.

== Basic Microformat Questions ==
===Q: ''When should I use a microformat? What are they for?"===

A: You are writing some HTML that contains useful human-readable information (such as a piece of contact information). You say to yourself: I would like to mark this up with some classes now for styling. You look up the relevant microformat, and you
pull in the standard names. You don't have to make your own up, and now your page is machine-readable too. Bonus!

Microformats are designed to make the data you already publish for humans available to machines. It allows applications as simple as cut-and-paste or as complex as a seach engine to use your data effectively.

===Q: ''Are microformats dependent upon (X)HTML?''===

A: Microformats are made to be embeddable. They can be embedded in (X)HTML, RSS, Atom or anywhere (X)HTML is allowed.

===Q: ''Microformats sound great. How can I help?''===

A: Take a look at http://microformats.org/discuss to see some ways to join the conversations about microformats, and the [[to-do]] list for things to help out with.

===Q: ''I'd like to make a donation to the microformat cause. How can I do this?''===

A: Thank you for your willingness to support microformats. We've only recently started this site and have decided that while we are figuring out exactly how to accept donations, we will be passing along donations to other good causes. Please consider donating to another cause like Red Cross, perhaps directed to help victims of recent natural disasters.

===Q: ''Which microformats have been implemented?'' ===

A: See the [[implementations]] page.

===Q: ''Which microformats should I implement?''===

A: Chances are you that your website already has data very similar to several microformats. For example, you probably have people and/or their contact information somewhere. That information could be marked up with [[hcard|hCard]], see the [[hcard-authoring|hCard authoring]] page for step by step instructions. If you are publishing press releases, try using [[hatom|hAtom]].

===Q: ''Do you have any link badges I can add to my website/blog?''===

A: There are some [[buttons]] but we can certainly use more! Please contribute what you come up with!

===Q. ''Are there any tools that support microformats?''===

A. Yes...tons... [[implementations]].

===Q. Is there a way to indicate that a given web page contains markup that conforms to one or more microformats? ===

A. The HTML HEAD element's '<code>profile</code>' attribute alerts applications to the potential presence of microformats. The [http://www.w3.org/TR/1999/REC-html401-19991224/struct/global.html#h-7.4.4.3 W3C HTML Specification] describes more about the profile attribute, and the [http://gmpg.org/xmdp/description XMDP description] documents how it is used.

===Q. ''What about using new URI schemes instead of class names, e.g. for geo information?''===

A. In general, it is more work, and less content-publisher friendly, to ask publishers to use URI schemes instead of class names.

Authors aren't publishing links to geo information.

They're publishing *visible text* of [[geo]] information.

So the easiest thing to do, for the author, is to leave it as visible text.

Thus, it makes the most sense to do the simple thing of just wrapping that
visible text with a little bit of markup, rather than asking the author to
move (or copy) it into an attribute, which may or may not require a
reformatting of the data as well.

It would make sense from a usability persepective to hyperlink geo information to a maps page or something, so that clicking it actually does something. If you forced them to use a hypothetical "geo:" protocol instead, then that would interfere, since you can only hyperlink something to one destination.

===Q: ''Who controls microformats?''===

A: An open community. Microformats are open standards licensed under Creative Commons Attribution. Much of the work here was begun on [[http://developers.technorati.com/wiki Technorati's Developer Wiki]], but Technorati has since divested control of these microformat standards to the open community here. The microformats.org domain is registered to Rohit Khare, CommerceNet is graciously hosting the servers, but claims no control over microformat standards. Anyone may follow the established [[process]] and contribute towards the development of microformat standards.

===Q: ''Who is the registrar for microformats?''===

A: There is no central registry. Microformats are registered in a distributed manner using profiles. For more information on profiles see http://microformats.org/wiki/profile-uris and http://gmpg.org/xmdp/

Conflicts and interoperability are managed through social processes rather than a formal registry. Current microformat profiles can be found at http://gmpg.org, http://w3.org, and http://microformats.org.

===Q: ''So multiple microformats with the same name can be valid?''===

A: Yes. The community at microformats.org can hopefully play a role in determining which is preferred by bringing interested folks together in one place and helping them resolve that question. As long as each microformat maintains a valid profile, each can be used effectively.

===Q: ''How do I validate my microformated content?''===

A: Currently there is not an automatic general-purpose validator for microformats (See [[to-do]]). There are however some microformat specific tools listed on the [[implementations]] page.

== Creating and Suggesting New Microformats ==

===Q. ''I would like to author a new microformats open standards specification for my site/business. How do I get started?''===

A. The first thing to do before attempting a new microformat open standard is to make as much use of existing [[microformats]] open standards as possible in whatever site you are looking to markup with your new microformat, as a way of learning what is left to be done. That is, at a minimum first:
* Markup all people and organizations as [[hcard|hCards]].
* Markup all events and time based things as [[hcalendar|hCalendar]] events.
* Markup all reviews as [[hreview|hReviews]].
* etc.
Then join the microformats [http://microformats.org/discuss discuss list], and ask folks what they think of your use of the microformats and if it can be improved.

From that experience you will then be able to figure out what is left to be specified. Otherwise it is too hard to approach the "whole problem".

Once you have completed that, take a look at the microformats [[process]] for how to walk through the steps of creating a new microformat, and note the specific problem you are trying to solve to the microformats-discuss list. This will help you find more people to help you solve the problems you are trying to solve.

===''Q How do I know if an idea for a Microformat has already been suggested in the past?''===

A. Check the list of proposed and rejected microformats.
* [[rejected-formats]]

== Specific Microformat Questions ==
If you have a question regarding a specific microformat, you may want to check the FAQ specific to that microformat.
* [[hatom-faq]]
* [[hcalendar-faq]]
* [[hcard-faq]]
* [[hreview-faq]]
* [[rel-faq]]
* [[rel-tag-faq]]
* [http://gmpg.org/xfn/faq xfn-faq]
* [[xfolk-faq]]
* [[xmdp-faq]]
* [[xoxo-faq]]

== Class interactions ==

===Q. ''Are there issues with page styling when specific class values are used?''===

A. There might be. However, any such issues can be easily (trivially) worked around by using contextual selectors.

===Q. ''How does the use of class values for semantics interact with the use of class values for attaching CSS styles?''===

A. The class attribute takes a space separated set of class names [http://www.w3.org/TR/REC-html40/struct/global.html#h-7.5.2 HTML4 reference]. Thus both author and microformat defined class names may be used in the same class attribute. In addition, microformat class names provide the author with a consistent set of class names to use for styling. If the author is already using using specific class names, they can continue to do so, and include microformat class names. If the author is already using a class name that happens to also be a microformat class name, then the author may want to consider using contextual CSS class selectors to make sure that avoid any unintentional styling effects.

See also:
* [http://tantek.com/log/2002/12.html#L20021216 A Touch Of Class]
* [http://tantek.com/log/2004/07.html#classmeaningnotshow Class For Meaning Not For Show]
* [http://www.meyerweb.com/eric/thoughts/2004/07/18/competent-classing Competant Classing], by Eric Meyer for discussion of choosing class names in (X)HTML
* [http://www.microformats.org/blog/2005/10/19/more-than-styling/ Class attributes are about more than styling] - Ryan King dispells common misconceptions about the ''HTML'' class attribute.

== <code><div></code> and <code></code> semantics ==

===''Q. Is it semantically meaningless to use divs?'' ===

A. Yes, both <code><div></code> and <code></code> have nearly no semantics. <code><div></code> can be used to represent a "division" of the page content. Similarly <code></code> can be used to reperesent that that "span" of text has some meaning, but the specifics of what that meaning is undefined by the <code></code>.

===''Q. Does the use of <code><div></code> and <code></code> elements add any semantics to web pages?''===

A. According to the [http://www.w3.org/TR/REC-html40/struct/global.html#h-7.5.4 spec], <code><div></code> and <code></code> "offer a generic mechanism for adding structure to documents." Their only meaning is in dividing documents into sections, and as such, their presence implies that the content within has a specific, but undefined by the element markup, semantic. Thus they are nearly semantic-free.

===''Q. Why do the examples on the wiki use <code class="element"></code> and <code class="element"><div></code> for nearly everything?''===

A. <code class="element"></code> and <code class="element"><div></code> are generic elements in HTML. When you use microformats, you should pick the most specific semantic element available for the semantics you are trying to express.

== Class semantics ==

===Q. ''Can an element have more than one class''===

A. Yes, the class attribute can contain a space delimited list of classes. For example:
Write high quality and simple software.
TODO: Add link to w3c.

===Q. ''Do (X)HTML class names have semantics?''===

A. The HTML4 specification does not define any particular class values [http://www.w3.org/TR/REC-html40/struct/global.html#h-7.5.2 REF], nor does it define any particular semantic for class values [http://www.w3.org/TR/REC-html40/struct/global.html#h-7.5.2 REF], except that they "may be used for general user agent processing" [http://www.w3.org/TR/REC-html40/struct/global.html#h-7.5.2 REF]. However, the [http://www.w3.org/TR/WD-htmllink-970328#profile" draft of "Hypertext Links in HTML"], allows for a "profile" to define meanings for those classes. [http://gmpg.org/xmdp/ XMDP] is a format for defining meta data profiles for (X)HTML, and thus an XMDP profile can be used to define the meanings of class names.

See also:
* [http://tantek.com/log/2002/12.html#L20021216 A Touch Of Class]
* [http://www.w3.org/TR/WD-htmllink-970328 Hypertext Links in HTML]

===Q. ''I thought one of the main goals of CSS was to separate data from presentation. Isn’t this sneaking presentation back into data?''===

A. This is a quite commonly expressed objection to the way microformats uses class, but it's based on a misunderstanding of the way the class attribute in HTML was designed. Yes, class is very commonly,and appropriately used by web designers in conjunction with CSS to style pages, and in truth, it is often overused for that, but despite this, class, according to the HTML specification "has several roles in HTML", including [http://www.w3.org/TR/html4/struct/global.html#h-7.5.2 "for general purpose processing by user agents"].

Microformats utilize this second aspect of the class (and id) attribute, and do so legitimately. It is not an abuse of the class or id attribute to use it to add semantic context to a document. Nor is the use of class in and of itself presentational - in fact, it is an important mechanism for separating presentation from structured content.

For some more on using class semantically, here are some articles

* [http://meyerweb.com/eric/thoughts/2004/07/18/competent-classing Competent Classing by Eric Meyer]
* [http://www.w3.org/QA/Tips/goodclassnames Use class with semantics in mind, W3C]
* [http://tantek.com/log/2004/07.html#d20t2359 More about the class attribute, Tantek Çelik]

== Microformats and Spam ==
===''Q. Given that Google now looks at hidden content as potential spam, will invisible microformats be considered spam?''===

A. It is advisable not to hide information in your site, regardless of whether it is microformated or not. Microformats provide a mechanism for marking up ''visible'' content. Any mechanism for embedding ''invisible'' or hidden content risks being considered spam due to the fact that invisible (meta)data inevitably ends up being abused. Avoid invisible (meta)data. Publish visible data.

== Design Patterns with Abbr & Title ==
===''Q. Why is ABBR being used when the title attribute is available on all HTML elements?''===

In the datetime design pattern the title attribute is used for the value of the property and the node value is used as the display value. <abbr title="value-here">Display-Here</abbr>.

A. The short answer is that <abbr> has the correct semantics.

The longer answer is that the value is often an abbreviated version of the formal value. Of course, if you don't want to use an <abbr>, you can use another element like this:

<abbr title="2006-12-31T12:59:59Z" class="dtstamp">New Year</abbr>

2006-12-31T12:59:59Z

In addition, microformats encourage the content to be visible and thus prefer the text of an element rather than using the 'title' attribute or any other less visible alternative. The exception is made for datetimes and abbr due to the fact that microformats are for humans first, machines second. Thus the content of the abbr element is used to provide human visible content and the machine equivalent is placed in the less visible (but still easily verifiable) 'title' attribute.

== Nesting of elements ==
===''Q. It seems that ... should work. Why is this incorrect?''===

A. See [http://microformats.org/wiki/hcard-faq#nesting-properties]

wiki-feedback

2006-10-17T04:44:15Z

BenWest: /* Complaints: */ signed my name on a comment

== What is This? ==
We collect feedback on usability and organization of the wiki here.

== What can I do here? ==
* Complain about how hard the wiki is to use. (Make it a story, if possible.)
* Add suggestions regarding content, organization, and usability to [http://microformats.org/wiki/to-do#Information_Architecture the IA todo list]. (Add your own area if necessary).
* Concur that you also had a problem finding something on the wiki.
* Search through the [http://microformats.org/discuss/mail/microformats-discuss/ Mailing List Archives] for
** [http://www.google.com/search?&q=site%3Ahttp%3A%2F%2Fmicroformats.org%2Fdiscuss%2Fmail%2Fmicroformats-discuss%2F+confused confused]
** [http://www.google.com/search?&q=site%3Ahttp%3A%2F%2Fmicroformats.org%2Fdiscuss%2Fmail%2Fmicroformats-discuss%2F+trouble trouble]
** [http://www.google.com/search?&q=site%3Ahttp%3A%2F%2Fmicroformats.org%2Fdiscuss%2Fmail%2Fmicroformats-discuss%2F+confusion confusion]
** [http://www.google.com/search?&q=site%3Ahttp%3A%2F%2Fmicroformats.org%2Fdiscuss%2Fmail%2Fmicroformats-discuss%2F+help help]
and post your results here.

== Complaints: ==
* Roger was wondering how fn and org work together, and didn't see the relevant section in the [[hcard|hCard]] spec.
** See [[hcard#Organization_Contact_Info|Organization Contact Info]] in the spec, and [[hcard-authoring#The_Importance_of_Names|The Importance of Names]] in [[hcard-authoring]]. I recommend this be added to [[hcard-faq]]. [[User:Tantek|Tantek]] 17:54, 16 Oct 2006 (PDT)
** Once I pointed out the first reference, he wondered why he missed it. Nonetheless, missed it he did. How should we highlight recommendations/suggestions? [[User:BenWest|BenWest]] 21:44, 16 Oct 2006 (PDT)
* Justin says: I didn't even see that there was a page on authoring within the pages and pages of specification. Even with it at the top of the page. I glanced right over it. It seems like most tutorials on hCard or [[hcalendar|hCalendar]] point people to the spec to get more information. Should we be encouraging people to point to the authoring page? I think a newbie would be very very very intimidated being pointed right to the spec.
:I agree with this. Perhaps a more friendly intro page could be constructed to introduce hCard and link to the various resources. [[User:Ashley|Ashley]] 14:31, 16 Oct 2006 (PDT)
* I can't find any useful information about marking up a key in the wiki. Perhaps someone could include some examples? [[User:Ashley|Ashley]] 14:31, 16 Oct 2006 (PDT)
** Ashley, what do you mean by a "key"? [[User:Tantek|Tantek]] 17:54, 16 Oct 2006 (PDT)
* Andy tells of his coworker: She was baffled; not lest because, though the page had a treatise on "Semantic XHTML Design Principles", it didn't list the hCalendar fields, let alone say which are mandatory and which are optional! (ed: RE: hCalendar) [[User:BenWest|BenWest]] 15:11, 16 Oct 2006 (PDT)
** Agreed that hCalendar needs to list the properties/sub-properties. Added to my [[to-do]] list. [[User:Tantek|Tantek]] 17:54, 16 Oct 2006 (PDT)
* This suggestion http://microformats.org/discuss/mail/microformats-discuss/2006-October/006101.html and many other proposals like it aren't being captured on the wiki. This means we are doomed to discuss rejected microformats again and again. Maybe we can have a gallery of ideas and their status (both ongoing and dead)... [[User:BenWest|BenWest]] 15:11, 16 Oct 2006 (PDT)
* Mike Schinkel says in a recent email to the list: -- (Nothing I could find on Microformats.org is explicit in defining "goals") -- (If would be good if there were a consensus, or at least if we were all aware.) [[User:BenWest|BenWest]] 21:19, 16 Oct 2006 (PDT)

== How Does This Work? ==
List accounts of complaints above. After they are addressed and confirmed, we can strike through them, and after some time when it is clear they have been addressed we can remove them completely. Perhaps if there is a suggestion it should be colored (perhaps highlighted yellow) and we should take care to make sure it gets moved to the [[to-do]] list.