Microformats Wiki - User contributions [en]

accessibility

2008-01-28T01:31:26Z

JamesCraig: /* Advantages */ benefit of CSS, not uF

<h1>Accessibility</h1>

This page documents microformats and accessibility in general, in particular advantages that adopting microformats provide for accessibility, and for documenting techniques for making microformats more accessible.

We should all strive to make our published microformats, parser implementations, and this wiki, accessible to all users, regardless of their physical abilities and needs, within the limits of the time and resources of the microformats community. Readers are advised to follow the [http://www.w3.org/TR/WCAG10/ W3C's Web Content Accessibility Guidelines 1.0], to at least level 2. Further advice is available on the [http://www.accessifyforum.com/ Accessify Forums].

__TOC__

==Advantages==
Some microformats have potential accessibility advantages.

===hCard===
*<code>tel</code> in [[hcard|hCard]]: use <code>style="speak-numeral:digits"</code>, so that telephone numbers are read by aural browsers as, for example, "five-five-five one-two-three-four" and not "five-hundred and fifty-five, one-thousand, two-hundred and thirty-two".
**Note: This is not an advantage to Microformats. It is a CSS best practice and can be used with or without hCard. This should probably be moved to a [[css-best-practices|CSS Best Practices]] page. - [[User:JamesCraig|James Craig]]
***It is an advantage ''of'' microformats - [[User:AndyMabbett|Andy Mabbett]]
***It is not an advantage of microformats; it is just CSS that can be used on any class, whether or not it happens to be ''tel''. There is no documented AT implementation that recognizes Microformats classes automatically. This is just a benefit of CSS, with or without uF. [[User:JamesCraig|James Craig]]

==Disadvantages==
Some microformats have potential accessibility disadvantages.

===abbr-design-pattern===
*As mentioned on external sites (see:[[accessibility-issues]]) and on the microformats-discuss list, the abbr-design-pattern (used in [[hcard|hCard]], [[hcalendar|hCalendar]], [[geo|GEO]] and others) is in violation of WCAG1 and WCAG2, and has potentially harmful accessibility side-effects of reading machine data to screen reader users rendering human content inaccessible.

===anchor-include-pattern===
*As mentioned on [[accessibility-issues]], the anchor-include-pattern is in violation of WCAG1 and WCAG2, and has potentially harmful accessibility side effects due to the missing link text.

==External testimonials==
* [http://lists.w3.org/Archives/Public/w3c-wai-ig/2006JulSep/subject.html#msg133 hCard and hCalendar Formats] - 2006-08-03 in w3c-wai-ig. e.g. <blockquote><p>I think Microformats.org is doing rather well on it's own, and it isn't particularly something that the W3C would or should get involved in until it's settled down. (And then it would just be a ratification kind of thing.)</p><p>...</p><p>In fact, it is likely to be good for accessibility, as the tools for consuming microformats often require valid code.</p></blockquote>

== Challenges ==
* Andy Mabbett - How can we make them accessible to people with (for instance) visual disabilities?

==See also==
*[[accessibility-issues]] - note external criticisms on the accesibility issues page
*[[internationalization]]
*[[assistive-technology]]
*[[assistive-technology-abbr-results]]

assistive-technology-abbr-results

2008-01-06T06:08:34Z

JamesCraig: /* Markup Possibilities */ added note on title-trigger addition

<h1>abbr-design-pattern alternatives</h1>
This page is for document the precise results of using [[assistive-technology]] with real world examples in the wild of the abbr design pattern, as nearly always used by [[hcalendar|hCalendar]] (e.g. dtstart, dtend), often by [[hreview|hReview]] (e.g. dtreviewed, rating) and sometimes by [[hcard|hCard]] (e.g. bday, type subproperty) and by [[geo|Geo]].

__TOC__

Each [[assistive-technology]] listed here should link to a precise description of the tool/service on the [[assistive-technology]] page, including version number, when published, etc. Each test result listed for each assistive technology should link to the example that was tested.

== Test Cases ==
The [http://www.webstandards.org/action/atf/ WaSP Accessibility Task Force] has developed a set of ([http://cookiecrook.com/test/uf/testcases/ extended test cases]]) that cover the following data formats and markup formats.

===Data Formats===
* ISO 8601 date with punctuation (YYYY-MM-DD)
* ISO 8601 datetime with punctuation (YYYY-MM-DDTHH:MM:SS)
* ISO 8601 datetime with punctuation and no seconds (YYYY-MM-DDTHH:MM)
* ISO 8601 UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SSZ)
* ISO 8601 pre-UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SS+HH:MM)
* ISO 8601 pre-UTC datetime with punctuation and no timezone minutes (YYYY-MM-DDTHH:MM:SS+HH)
* ISO 8601 post-UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SS-HH:MM)
* ISO 8601 post-UTC datetime with punctuation and no timezone minutes (YYYY-MM-DDTHH:MM:SS-HH)
* ISO 8601 datetime with punctuation but w/o timezone punctuation. ''The hypothesis is that something like "eleven o'clock plus oh seven hundred" may be more understandable than "eleven o'clock plus seven o'clock" (similarly for the hyphen, read as "dash").''
** pre-UTC (YYYY-MM-DDTHH:MM:SS+HHMM)
** post-UTC (YYYY-MM-DDTHH:MM:SS-HHMM)
* GEO Latitude/Longitude coordinates.
* ISO 8601 durations
* ISO 8601 recurrences

=== Rejected Data formats ===
Dates without punctuation as they have proved unusable. Proof is premise for [[http://www.webstandards.org/2007/04/27/haccessibility/ hAccessibility]] article on the Web Standards Project Buzz blog. Window Eyes and JAWS read un-punctuated dates as single number. [[http://www.webstandards.org/files/atf_microformats/jaws.mp3 JAWS 8 on IE7 citation (MP3 Audio)]] of "twenty million seventy-thousand three-hundred twelve" is reason enough for rejection.
* ISO 8601 date without dashes (YYYYMMDD)
* ISO 8601 datetime without dashes and colons (YYYYMMDDTHHMMSS)
* ISO 8601 datetime without dashes and colons and no seconds (YYYYMMDDTHHMM)
* ISO 8601 UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ)
* ISO 8601 pre-UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ+HHMM)
* ISO 8601 pre-UTC datetime without dashes and colons and no timezone minutes (YYYYMMDDTHHMMSSZ+HH)
* ISO 8601 post-UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ-HHMM)
* ISO 8601 post-UTC datetime without dashes and colons and no timezone minutes (YYYYMMDDTHHMMSSZ-HH)

===Markup Possibilities===
==== Valid HTML4 ====
* abbr-design-pattern (as currently recommended)
* SPAN element with title attribute (with or without [[title-trigger]] as it behaves no differently in any known screen reader).
* [[dfn-design-pattern|DFN element with title attribute.]]
* Non-linked anchor element with title attribute. (<code><nowiki><a class="dtstart" title="20070713">13th</a></nowiki></code>)
* Nested SPAN element.
* Nested ABBR element.
* Nested DFN element (See: [http://microformats.org/discuss/mail/microformats-new/2007-May/000335.html mailing list thread], verify at [http://alistapart.com/articles/hattrick ALA article]).
* Empty INS element with DATETIME attr (<code><nowiki><span class="dtstart">13th<ins datetime="20070713"></ins></span></nowiki></code>)
* Rarely used event handler. e.g. (<code><nowiki><span class="dtstart" onchange="void(20070713)">13th</span></nowiki></code>)
* Hidden INPUT element (undesirable as it requires FORM)
* Empty ABBR element (<code><nowiki><span class="dtstart">13th<abbr title="20070713"></abbr></span></nowiki></code>)

==== Invalid HTML4 ====
Markup possibilities that are invalid in HTML4/XHTML1 are noted here to be clear that they were considered and rejected. Since microformats build on [[posh]], any technique that is invalid semantic (X)HTML is unacceptable for a microformats solution. There is no need to bother testing these.
* SPAN with RDF dc:date attribute.
* SPAN with RDF geo:position attribute.
* Anchor element with name attr (<code><nowiki><a class="dtstart" name="iso8601:20070713">13th</a></nowiki></code>) *[name] does not need to be unique, but a[name] does. [http://www.w3.org/TR/html401/struct/links.html#h-12.2.1 HTML 4.01 Strict, 12.2.1]

==== Markup Rejections ====
* OBJECT with param value. (requires significant extra markup and CSS in order to *behave* correctly)
* OBJECT with in-page data attribute. (See [[include-pattern-feedback#Objects_and_Browser_Behavior]])

===Screenreader Language Pronunciations===
Localization is not the job of Microformats, so multiple human languages (English, Spanish, etc.) is irrelevant.

===Verbosity settings===

* Punctuation, speak none.
* Punctuation, speak some.
* Punctuation, speak all.
* Title attributes, speak none.
* Title attributes, speak some (abbr and acronym).
* Title attributes, speak all.

===Screenreaders===
* Freedom Scientific JAWS (multiple versions TBD)
* GW Micro Window Eyes (multiple versions TBD)
* Apple Voiceover (multiple versions TBD)
* Dolphin HAL (multiple versions TBD)

== Results ==

<s>Please provide hyperlinks to examples in the wild for each case that is to be tested. Test cases with example in the wild URLs merit more testing than those without.</s> The purpose of these test cases is to find the best solution, whether or not it is currently being used.

Results to be determined.

== See Also ==
* [[accessibility]]
* [[assistive-technology]]

dfn-design-pattern

2008-01-06T06:07:07Z

JamesCraig: /* Assistive Technology */

=Dfn design pattern=

<strong>Important</strong>: this is currently a proposal: it is <em>not</em> a finalised design pattern.

This page is intended for discussion and exploration of a design pattern to complement the [[abbr-design-pattern|abbr design pattern]] while addressing the [[abbr-design-pattern-issues|abbr design pattern issues]], particularly the [[accessibility-issues#abbr-design-pattern|accessibility issues]].

__TOC__

==Purpose==

The [[abbr-design-pattern|abbr design pattern]] is used in several microformats to enclose standardised data such as the [[datetime-design-pattern|datetime design pattern]] in the <code>title</code> attribute. However some [[assistive-technology|assistive technology]] will expose this data directly to the user, which is often undesirable.
See also [[assistive-technology-abbr-results|assistive technology abbr results]].

This problem arises because the <code>title</code> attribute has a different semantic meaning when it is attached to an <code>abbr</code> or <code>acronym</code> than it does on other elements. Usually [http://www.w3.org/TR/html4/struct/global.html#h-7.4.3 the <code>title</code> attribute] is used to provide provide advisory information. But for <code>abbr</code> or <code>acronym</code> the <code>title</code> is used to provide an expanded form of the text contained between the opening and closing tags. This is why the <code>abbr</code> element was chosen to contain datetime information: the ISO format is an expanded form of the human-readable text contained within the element. Because screen readers can be configured to treat <code>abbr</code> and <code>acronym</code> elements as special cases, the <code>title</code> attribute is sometimes read aloud.

==Proposal==

Rather than expand the [[abbr-design-pattern|abbr design pattern]] to any element (or to a semantically neutral element such as <code>span</code>), it would be better to use an element that has semantic value but which isn't treated as a special case by assistive technology.

===dfn===

The [http://www.w3.org/TR/html4/struct/text.html#h-9.2.1 dfn element] indicates the defining instance of the enclosed term. This element is not widely used but where it used, it is often used in a similar way to the <code>abbr</code> element. Although the <code>title</code> is not required for the <code>dfn</code> element, it is often used to provide expanded information.

The semantic meaning of <code>dfn</code>, as it is currently used, is potentially similar enough to <code>abbr</code> element to allow it to be used as an alternative:

<pre><nowiki>
<abbr class="dtstart" title="2007-08-16T22:00:00">10pm on August 16th</abbr>
<dfn class="dtstart" title="2007-08-16T22:00:00">10pm on August 16th</dfn>
</nowiki></pre>

==Issues==

===Semantics===

The <code>dfn</code> is <em>not</em> intended for definitions; it is intended for defining instances. Does this mean that it must always be used for the first instance of a term (such as a date)?

Is the <code>dfn</code> element equally appropriate as the <code>abbr</code> for information such as datetimes and geo or is this stretching the semantic meaning of the element beyond a reasonable limit?

====HTML5====
In HTML5, the [http://www.w3.org/html/wg/html5/#the-dfn|DFN element semantics] have completely changed and would be incompatable with this pattern.

===Parsers===

Existing microformats parsers (such as the Operator extension to Firefox) would need to be updated to handle this proposed alternative to the abbr design pattern. However, this is true of any proposed alternatives.

===Complexity===

Microformats are intended to be easy to publish. The number of design patterns should be kept to a minimum. Every new design pattern is potentially a new barrier to entry for publishers.

===Assistive Technology===

The proposed dfn design pattern assumes that screen readers don't treat <code>dfn</code> as a special case like <code>abbr</code> or <code>acronym</code>. Is this actually the case? Please note results of testing on that item in the [[assistive-technology-abbr-results|assistive technology results]] page.

===Usage in the wild===

This design pattern is built on the assumption that, although the <code>dfn</code> is not widely used, where it used, it is most often used in conjunction with the <code>title</code> attribute. Please document examples and references here:

* [http://juicystudio.com/article/jargon-busting-with-the-definition-element.php Juicy Studios: Jargon Busting with the Definition Element]
* [http://alistapart.com/articles/hattrick A List Apart: The Accessibility Hat Trick: Getting Abbreviations Right]
* ...

==Alternatives==
*[[title-trigger]]
*...

==See Also==

* [[abbr-design-pattern|abbr design pattern]]
* [[abbr-design-pattern-issues|abbr design pattern issues]]
* [[accessibility-issues#abbr-design-pattern|accessibility issues]]
* [[assistive-technology-abbr-results|assistive technology abbr results]]
* [[datetime-design-pattern|datetime design pattern]]

assistive-technology-abbr-results

2007-09-09T22:20:50Z

JamesCraig: /* Test Cases */ Finalizing

<h1>abbr-design-pattern alternatives</h1>
This page is for document the precise results of using [[assistive-technology]] with real world examples in the wild of the abbr design pattern, as nearly always used by [[hcalendar|hCalendar]] (e.g. dtstart, dtend), often by [[hreview|hReview]] (e.g. dtreviewed, rating) and sometimes by [[hcard|hCard]] (e.g. bday, type subproperty) and by [[geo|Geo]].

__TOC__

Each [[assistive-technology]] listed here should link to a precise description of the tool/service on the [[assistive-technology]] page, including version number, when published, etc. Each test result listed for each assistive technology should link to the example that was tested.

== Test Cases ==
The [http://www.webstandards.org/action/atf/ WaSP Accessibility Task Force] has developed a set of ([http://cookiecrook.com/test/uf/testcases/ extended test cases]]) that cover the following data formats and markup formats.

===Data Formats===
* ISO 8601 date with punctuation (YYYY-MM-DD)
* ISO 8601 datetime with punctuation (YYYY-MM-DDTHH:MM:SS)
* ISO 8601 datetime with punctuation and no seconds (YYYY-MM-DDTHH:MM)
* ISO 8601 UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SSZ)
* ISO 8601 pre-UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SS+HH:MM)
* ISO 8601 pre-UTC datetime with punctuation and no timezone minutes (YYYY-MM-DDTHH:MM:SS+HH)
* ISO 8601 post-UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SS-HH:MM)
* ISO 8601 post-UTC datetime with punctuation and no timezone minutes (YYYY-MM-DDTHH:MM:SS-HH)
* ISO 8601 datetime with punctuation but w/o timezone punctuation. ''The hypothesis is that something like "eleven o'clock plus oh seven hundred" may be more understandable than "eleven o'clock plus seven o'clock" (similarly for the hyphen, read as "dash").''
** pre-UTC (YYYY-MM-DDTHH:MM:SS+HHMM)
** post-UTC (YYYY-MM-DDTHH:MM:SS-HHMM)
* GEO Latitude/Longitude coordinates.
* ISO 8601 durations
* ISO 8601 recurrences

=== Rejected Data formats ===
Dates without punctuation as they have proved unusable. Proof is premise for [[http://www.webstandards.org/2007/04/27/haccessibility/ hAccessibility]] article on the Web Standards Project Buzz blog. Window Eyes and JAWS read un-punctuated dates as single number. [[http://www.webstandards.org/files/atf_microformats/jaws.mp3 JAWS 8 on IE7 citation (MP3 Audio)]] of "twenty million seventy-thousand three-hundred twelve" is reason enough for rejection.
* ISO 8601 date without dashes (YYYYMMDD)
* ISO 8601 datetime without dashes and colons (YYYYMMDDTHHMMSS)
* ISO 8601 datetime without dashes and colons and no seconds (YYYYMMDDTHHMM)
* ISO 8601 UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ)
* ISO 8601 pre-UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ+HHMM)
* ISO 8601 pre-UTC datetime without dashes and colons and no timezone minutes (YYYYMMDDTHHMMSSZ+HH)
* ISO 8601 post-UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ-HHMM)
* ISO 8601 post-UTC datetime without dashes and colons and no timezone minutes (YYYYMMDDTHHMMSSZ-HH)

===Markup Possibilities===
==== Valid HTML4 ====
* abbr-design-pattern (as currently recommended)
* SPAN element with title attribute.
* [[dfn-design-pattern|DFN element with title attribute.]]
* Non-linked anchor element with title attribute. (<code><nowiki><a class="dtstart" title="20070713">13th</a></nowiki></code>)
* Nested SPAN element.
* Nested ABBR element.
* Nested DFN element (See: [http://microformats.org/discuss/mail/microformats-new/2007-May/000335.html mailing list thread], verify at [http://alistapart.com/articles/hattrick ALA article]).
* Empty INS element with DATETIME attr (<code><nowiki><span class="dtstart">13th<ins datetime="20070713"></ins></span></nowiki></code>)
* Rarely used event handler. e.g. (<code><nowiki><span class="dtstart" onchange="void(20070713)">13th</span></nowiki></code>)
* Hidden INPUT element (undesirable as it requires FORM)
* Empty ABBR element (<code><nowiki><span class="dtstart">13th<abbr title="20070713"></abbr></span></nowiki></code>)

==== Invalid HTML4 ====
Markup possibilities that are invalid in HTML4/XHTML1 are noted here to be clear that they were considered and rejected. Since microformats build on [[posh]], any technique that is invalid semantic (X)HTML is unacceptable for a microformats solution. There is no need to bother testing these.
* SPAN with RDF dc:date attribute.
* SPAN with RDF geo:position attribute.
* Anchor element with name attr (<code><nowiki><a class="dtstart" name="iso8601:20070713">13th</a></nowiki></code>) *[name] does not need to be unique, but a[name] does. [http://www.w3.org/TR/html401/struct/links.html#h-12.2.1 HTML 4.01 Strict, 12.2.1]

==== Markup Rejections ====
* OBJECT with param value. (requires significant extra markup and CSS in order to *behave* correctly)
* OBJECT with in-page data attribute. (See [[include-pattern-feedback#Objects_and_Browser_Behavior]])

===Screenreader Language Pronunciations===
Localization is not the job of Microformats, so multiple human languages (English, Spanish, etc.) is irrelevant.

===Verbosity settings===

* Punctuation, speak none.
* Punctuation, speak some.
* Punctuation, speak all.
* Title attributes, speak none.
* Title attributes, speak some (abbr and acronym).
* Title attributes, speak all.

===Screenreaders===
* Freedom Scientific JAWS (multiple versions TBD)
* GW Micro Window Eyes (multiple versions TBD)
* Apple Voiceover (multiple versions TBD)
* Dolphin HAL (multiple versions TBD)

== Results ==

<s>Please provide hyperlinks to examples in the wild for each case that is to be tested. Test cases with example in the wild URLs merit more testing than those without.</s> The purpose of these test cases is to find the best solution, whether or not it is currently being used.

Results TBD.

== See Also ==
* [[accessibility]]
* [[assistive-technology]]

assistive-technology-abbr-results

2007-08-13T06:27:39Z

JamesCraig: /* Test Cases */ oops, wrong link

<h1>assistive technology abbr results</h1>
This page is for document the precise results of using [[assistive-technology]] with real world examples in the wild of the abbr design pattern, as nearly always used by [[hcalendar|hCalendar]] (e.g. dtstart, dtend), often by [[hreview|hReview]] (e.g. dtreviewed, rating) and sometimes by [[hcard|hCard]] (e.g. bday, type subproperty) and by [[geo|Geo]].

__TOC__

Each [[assistive-technology]] listed here should link to a precise description of the tool/service on the [[assistive-technology]] page, including version number, when published, etc. Each test result listed for each assistive technology should link to the example that was tested.

== Test Cases ==
The [http://www.webstandards.org/action/atf/ WaSP Accessibility Task Force] is working on a set of extended test cases ([http://cookiecrook.com/test/uf/testcases/ work-in-progress]]) that will cover the following data formats and markup formats. Please add to the list so we can create a comprehensive result set.

===Data Formats===
Please provide hyperlinks to examples in the wild for each case that is to be tested. Test cases with example in the wild URLs merit more testing than those without. However, the purpose of these test cases is to find the best solution, whether or not it is currently being used.
* ISO 8601 date with punctuation (YYYY-MM-DD)
* ISO 8601 datetime with punctuation (YYYY-MM-DDTHH:MM:SS)
* ISO 8601 datetime with punctuation and no seconds (YYYY-MM-DDTHH:MM)
* ISO 8601 UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SSZ)
* ISO 8601 pre-UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SS+HH:MM)
* ISO 8601 pre-UTC datetime with punctuation and no timezone minutes (YYYY-MM-DDTHH:MM:SS+HH)
* ISO 8601 post-UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SS-HH:MM)
* ISO 8601 post-UTC datetime with punctuation and no timezone minutes (YYYY-MM-DDTHH:MM:SS-HH)
* ISO 8601 datetime with punctuation but w/o timezone punctuation. ''The hypothesis is that something like "eleven o'clock plus oh seven hundred" may be more understandable than "eleven o'clock plus seven o'clock" (similarly for the hyphen, read as "dash").''
** pre-UTC (YYYY-MM-DDTHH:MM:SS+HHMM)
** post-UTC (YYYY-MM-DDTHH:MM:SS-HHMM)
* GEO Latitude/Longitude coordinates.
* ISO 8601 durations
* ISO 8601 recurrences

=== Rejected Data formats ===
Dates without punctuation as they have proved unusable. Proof is premise for [[http://www.webstandards.org/2007/04/27/haccessibility/ hAccessibility]] article on the Web Standards Project Buzz blog. Window Eyes and JAWS read un-punctuated dates as single number. [[http://www.webstandards.org/files/atf_microformats/jaws.mp3 JAWS 8 on IE7 citation (MP3 Audio)]] of "twenty million seventy-thousand three-hundred twelve" is reason enough for rejection.
* ISO 8601 date without dashes (YYYYMMDD)
* ISO 8601 datetime without dashes and colons (YYYYMMDDTHHMMSS)
* ISO 8601 datetime without dashes and colons and no seconds (YYYYMMDDTHHMM)
* ISO 8601 UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ)
* ISO 8601 pre-UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ+HHMM)
* ISO 8601 pre-UTC datetime without dashes and colons and no timezone minutes (YYYYMMDDTHHMMSSZ+HH)
* ISO 8601 post-UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ-HHMM)
* ISO 8601 post-UTC datetime without dashes and colons and no timezone minutes (YYYYMMDDTHHMMSSZ-HH)

===Markup Possibilities===
==== Valid HTML4 ====
* abbr-design-pattern (as currently recommended)
* SPAN element with title attribute.
* DFN element with title attribute.
* Non-linked anchor element with title attribute. (<code><nowiki><a class="dtstart" title="20070713">13th</a></nowiki></code>)
* Nested SPAN element.
* Nested ABBR element.
* Nested DFN element (See: [http://microformats.org/discuss/mail/microformats-new/2007-May/000335.html mailing list thread], verify at [http://alistapart.com/articles/hattrick ALA article]).
* Empty INS element with DATETIME attr (<code><nowiki><span class="dtstart">13th<ins datetime="20070713"></ins></span></nowiki></code>)
* Rarely used event handler. e.g. (<code><nowiki><span class="dtstart" onchange="void(20070713)">13th</span></nowiki></code>)
* Hidden INPUT element (undesirable as it requires FORM)
* Empty ABBR element (<code><nowiki><span class="dtstart">13th<abbr title="20070713"></abbr></span></nowiki></code>)

==== Invalid HTML4 ====
Markup possibilities that are invalid in HTML4/XHTML1 are noted here to be clear that they were considered and rejected. Since microformats build on [[posh]], any technique that is invalid semantic (X)HTML is unacceptable for a microformats solution. There is no need to bother testing these.
* SPAN with RDF dc:date attribute.
* SPAN with RDF geo:position attribute.
* Anchor element with name attr (<code><nowiki><a class="dtstart" name="iso8601:20070713">13th</a></nowiki></code>) *[name] does not need to be unique, but a[name] does. [http://www.w3.org/TR/html401/struct/links.html#h-12.2.1 HTML 4.01 Strict, 12.2.1]

==== Markup Rejections ====
* OBJECT with param value. (requires significant extra markup and CSS in order to *behave* correctly)
* OBJECT with in-page data attribute. (See [[include-pattern-feedback#Objects_and_Browser_Behavior]])

===Screenreader Language Pronunciations===
* English
* Spanish (need volunteer native Spanish speaker screen reader user)
* ?

===Verbosity settings===

* Punctuation, speak none.
* Punctuation, speak some.
* Punctuation, speak all.
* Title attributes, speak none.
* Title attributes, speak some (abbr and acronym).
* Title attributes, speak all.

===Screenreaders===
* Freedom Scientific JAWS (multiple versions TBD)
* GW Micro Window Eyes (multiple versions TBD)
* Apple Voiceover (multiple versions TBD)
* Dolphin HAL (multiple versions TBD)

== Results ==

To be determined.

== See Also ==
* [[accessibility]]
* [[assistive-technology]]

assistive-technology-abbr-results

2007-08-13T06:24:16Z

JamesCraig: /* Test Cases */ changed link to updated test cases

<h1>assistive technology abbr results</h1>
This page is for document the precise results of using [[assistive-technology]] with real world examples in the wild of the abbr design pattern, as nearly always used by [[hcalendar|hCalendar]] (e.g. dtstart, dtend), often by [[hreview|hReview]] (e.g. dtreviewed, rating) and sometimes by [[hcard|hCard]] (e.g. bday, type subproperty) and by [[geo|Geo]].

__TOC__

Each [[assistive-technology]] listed here should link to a precise description of the tool/service on the [[assistive-technology]] page, including version number, when published, etc. Each test result listed for each assistive technology should link to the example that was tested.

== Test Cases ==
The [http://www.webstandards.org/action/atf/ WaSP Accessibility Task Force] is working on a set of extended test cases ([http://cookiecrook.com/test/uf/ work-in-progress]]) that will cover the following data formats and markup formats. Please add to the list so we can create a comprehensive result set.

===Data Formats===
Please provide hyperlinks to examples in the wild for each case that is to be tested. Test cases with example in the wild URLs merit more testing than those without. However, the purpose of these test cases is to find the best solution, whether or not it is currently being used.
* ISO 8601 date with punctuation (YYYY-MM-DD)
* ISO 8601 datetime with punctuation (YYYY-MM-DDTHH:MM:SS)
* ISO 8601 datetime with punctuation and no seconds (YYYY-MM-DDTHH:MM)
* ISO 8601 UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SSZ)
* ISO 8601 pre-UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SS+HH:MM)
* ISO 8601 pre-UTC datetime with punctuation and no timezone minutes (YYYY-MM-DDTHH:MM:SS+HH)
* ISO 8601 post-UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SS-HH:MM)
* ISO 8601 post-UTC datetime with punctuation and no timezone minutes (YYYY-MM-DDTHH:MM:SS-HH)
* ISO 8601 datetime with punctuation but w/o timezone punctuation. ''The hypothesis is that something like "eleven o'clock plus oh seven hundred" may be more understandable than "eleven o'clock plus seven o'clock" (similarly for the hyphen, read as "dash").''
** pre-UTC (YYYY-MM-DDTHH:MM:SS+HHMM)
** post-UTC (YYYY-MM-DDTHH:MM:SS-HHMM)
* GEO Latitude/Longitude coordinates.
* ISO 8601 durations
* ISO 8601 recurrences

=== Rejected Data formats ===
Dates without punctuation as they have proved unusable. Proof is premise for [[http://www.webstandards.org/2007/04/27/haccessibility/ hAccessibility]] article on the Web Standards Project Buzz blog. Window Eyes and JAWS read un-punctuated dates as single number. [[http://www.webstandards.org/files/atf_microformats/jaws.mp3 JAWS 8 on IE7 citation (MP3 Audio)]] of "twenty million seventy-thousand three-hundred twelve" is reason enough for rejection.
* ISO 8601 date without dashes (YYYYMMDD)
* ISO 8601 datetime without dashes and colons (YYYYMMDDTHHMMSS)
* ISO 8601 datetime without dashes and colons and no seconds (YYYYMMDDTHHMM)
* ISO 8601 UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ)
* ISO 8601 pre-UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ+HHMM)
* ISO 8601 pre-UTC datetime without dashes and colons and no timezone minutes (YYYYMMDDTHHMMSSZ+HH)
* ISO 8601 post-UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ-HHMM)
* ISO 8601 post-UTC datetime without dashes and colons and no timezone minutes (YYYYMMDDTHHMMSSZ-HH)

===Markup Possibilities===
==== Valid HTML4 ====
* abbr-design-pattern (as currently recommended)
* SPAN element with title attribute.
* DFN element with title attribute.
* Non-linked anchor element with title attribute. (<code><nowiki><a class="dtstart" title="20070713">13th</a></nowiki></code>)
* Nested SPAN element.
* Nested ABBR element.
* Nested DFN element (See: [http://microformats.org/discuss/mail/microformats-new/2007-May/000335.html mailing list thread], verify at [http://alistapart.com/articles/hattrick ALA article]).
* Empty INS element with DATETIME attr (<code><nowiki><span class="dtstart">13th<ins datetime="20070713"></ins></span></nowiki></code>)
* Rarely used event handler. e.g. (<code><nowiki><span class="dtstart" onchange="void(20070713)">13th</span></nowiki></code>)
* Hidden INPUT element (undesirable as it requires FORM)
* Empty ABBR element (<code><nowiki><span class="dtstart">13th<abbr title="20070713"></abbr></span></nowiki></code>)

==== Invalid HTML4 ====
Markup possibilities that are invalid in HTML4/XHTML1 are noted here to be clear that they were considered and rejected. Since microformats build on [[posh]], any technique that is invalid semantic (X)HTML is unacceptable for a microformats solution. There is no need to bother testing these.
* SPAN with RDF dc:date attribute.
* SPAN with RDF geo:position attribute.
* Anchor element with name attr (<code><nowiki><a class="dtstart" name="iso8601:20070713">13th</a></nowiki></code>) *[name] does not need to be unique, but a[name] does. [http://www.w3.org/TR/html401/struct/links.html#h-12.2.1 HTML 4.01 Strict, 12.2.1]

==== Markup Rejections ====
* OBJECT with param value. (requires significant extra markup and CSS in order to *behave* correctly)
* OBJECT with in-page data attribute. (See [[include-pattern-feedback#Objects_and_Browser_Behavior]])

===Screenreader Language Pronunciations===
* English
* Spanish (need volunteer native Spanish speaker screen reader user)
* ?

===Verbosity settings===

* Punctuation, speak none.
* Punctuation, speak some.
* Punctuation, speak all.
* Title attributes, speak none.
* Title attributes, speak some (abbr and acronym).
* Title attributes, speak all.

===Screenreaders===
* Freedom Scientific JAWS (multiple versions TBD)
* GW Micro Window Eyes (multiple versions TBD)
* Apple Voiceover (multiple versions TBD)
* Dolphin HAL (multiple versions TBD)

== Results ==

To be determined.

== See Also ==
* [[accessibility]]
* [[assistive-technology]]

assistive-technology-abbr-results

2007-07-06T08:08:29Z

JamesCraig: /* Test Cases */ linked w.i.p. test case and changed a few instances of 'must' to 'should'

<h1>assistive technology abbr results</h1>
This page is for document the precise results of using [[assistive-technology]] with real world examples in the wild of the abbr design pattern, as nearly always used by [[hcalendar|hCalendar]] (e.g. dtstart, dtend), often by [[hreview|hReview]] (e.g. dtreviewed, rating) and sometimes by [[hcard|hCard]] (e.g. bday, type subproperty).

__TOC__

Each [[assistive-technology]] listed here should link to a precise description of the tool/service on the [[assistive-technology]] page, including version number, when published, etc. Each test result listed for each assistive technology should link to the example that was tested.

== Test Cases ==
The [http://www.webstandards.org/action/atf/ WaSP Accessibility Task Force] is working on a set of extended test cases ([http://cookiecrook.com/test/uf/patterns/ work-in-progress]]) that will cover the following data formats and markup formats. Please add to the list so we can create a comprehensive result set.

===Data Formats===
Please provide hyperlinks to examples in the wild for each case that is to be tested. Test cases with example in the wild URLs merit more testing than those without. However, the purpose of these test cases is to find the best solution, whether or not it is currently being used.
* ISO 8601 date with punctuation (YYYY-MM-DD)
* ISO 8601 datetime with punctuation (YYYY-MM-DDTHH:MM:SS)
* ISO 8601 datetime with punctuation and no seconds (YYYY-MM-DDTHH:MM)
* ISO 8601 UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SSZ)
* ISO 8601 pre-UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SS+HH:MM)
* ISO 8601 pre-UTC datetime with punctuation and no timezone minutes (YYYY-MM-DDTHH:MM:SS+HH)
* ISO 8601 post-UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SS-HH:MM)
* ISO 8601 post-UTC datetime with punctuation and no timezone minutes (YYYY-MM-DDTHH:MM:SS-HH)
* ISO 8601 datetime with punctuation but w/o timezone punctuation. ''The hypothesis is that something like "eleven o'clock plus oh seven hundred" may be more understandable than "eleven o'clock plus seven o'clock" (similarly for the hyphen, read as "dash").''
** pre-UTC (YYYY-MM-DDTHH:MM:SS+HHMM)
** post-UTC (YYYY-MM-DDTHH:MM:SS-HHMM)
* GEO Latitude/Longitude coordinates.
* ISO 8601 durations
* ISO 8601 recurrences

=== Rejected Data formats ===
Dates without punctuation as they have proved unusable. Proof is premise for [[http://www.webstandards.org/2007/04/27/haccessibility/ hAccessibility]] article on the Web Standards Project Buzz blog. Window Eyes and JAWS read un-punctuated dates as single number. [[http://www.webstandards.org/files/atf_microformats/jaws.mp3 JAWS 8 on IE7 citation (MP3 Audio)]] of "twenty million seventy-thousand three-hundred twelve" is reason enough for rejection.
* ISO 8601 date without dashes (YYYYMMDD)
* ISO 8601 datetime without dashes and colons (YYYYMMDDTHHMMSS)
* ISO 8601 datetime without dashes and colons and no seconds (YYYYMMDDTHHMM)
* ISO 8601 UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ)
* ISO 8601 pre-UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ+HHMM)
* ISO 8601 pre-UTC datetime without dashes and colons and no timezone minutes (YYYYMMDDTHHMMSSZ+HH)
* ISO 8601 post-UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ-HHMM)
* ISO 8601 post-UTC datetime without dashes and colons and no timezone minutes (YYYYMMDDTHHMMSSZ-HH)

===Markup Possibilities===
==== Valid HTML4 ====
* abbr-design-pattern (as currently recommended)
* SPAN element with title attribute.
* DFN element with title attribute.
* Non-linked anchor element with title attribute. (<code><nowiki><a class="dtstart" title="20070713">13th</a></nowiki></code>)
* Nested SPAN element.
* Nested ABBR element.
* Nested DFN element (See: [http://microformats.org/discuss/mail/microformats-new/2007-May/000335.html mailing list thread], verify at [http://alistapart.com/articles/hattrick ALA article]).
* Empty INS element with DATETIME attr (<code><nowiki><span class="dtstart">13th<ins datetime="20070713"></ins></span></nowiki></code>)
* Rarely used event handler. e.g. (<code><nowiki><span class="dtstart" onchange="void(20070713)">13th</span></nowiki></code>)
* Hidden INPUT element (undesirable as it requires FORM)
* Empty ABBR element (<code><nowiki><span class="dtstart">13th<abbr title="20070713"></abbr></span></nowiki></code>)

==== Invalid HTML4 ====
Markup possibilities that are invalid in HTML4/XHTML1 are noted here to be clear that they were considered and rejected. Since microformats build on [[posh]], any technique that is invalid semantic (X)HTML is unacceptable for a microformats solution. There is no need to bother testing these.
* SPAN with RDF dc:date attribute.
* SPAN with RDF geo:position attribute.
* Anchor element with name attr (<code><nowiki><a class="dtstart" name="iso8601:20070713">13th</a></nowiki></code>) *[name] does not need to be unique, but a[name] does. [http://www.w3.org/TR/html401/struct/links.html#h-12.2.1 HTML 4.01 Strict, 12.2.1]

==== Markup Rejections ====
* OBJECT with param value. (requires significant extra markup and CSS in order to *behave* correctly)
* OBJECT with in-page data attribute. (See [[include-pattern-feedback#Objects_and_Browser_Behavior]])

===Screenreader Language Pronunciations===
* English
* Spanish (need volunteer native Spanish speaker screen reader user)
* ?

===Verbosity settings===

* Punctuation, speak none.
* Punctuation, speak some.
* Punctuation, speak all.
* Title attributes, speak none.
* Title attributes, speak some (abbr and acronym).
* Title attributes, speak all.

===Screenreaders===
* Freedom Scientific JAWS (multiple versions TBD)
* GW Micro Window Eyes (multiple versions TBD)
* Apple Voiceover (multiple versions TBD)
* Dolphin HAL (multiple versions TBD)

== Results ==

To be determined.

== See Also ==
* [[accessibility]]
* [[assistive-technology]]

assistive-technology-abbr-results

2007-07-06T07:12:40Z

JamesCraig: /* Markup Possibilities */ rejecting one more format

<h1>assistive technology abbr results</h1>
This page is for document the precise results of using [[assistive-technology]] with real world examples in the wild of the abbr design pattern, as nearly always used by [[hcalendar|hCalendar]] (e.g. dtstart, dtend), often by [[hreview|hReview]] (e.g. dtreviewed, rating) and sometimes by [[hcard|hCard]] (e.g. bday, type subproperty).

__TOC__

Each [[assistive-technology]] listed here MUST link to a precise description of the tool/service on the [[assistive-technology]] page, including version number, when published, etc.

Each test result listed for each assistive technology MUST link to the real world example that was tested.

== Test Cases ==
The [http://www.webstandards.org/action/atf/ WasP Accessibility Task Force] is working on a set of extended test cases that will cover the following data formats and markup formats. Please add to the list so we can create a comprehensive result set.

===Data Formats===
Please provide hyperlinks to examples in the wild for each case that is to be tested. Test cases with example in the wild URLs merit more testing than those without. However, the purpose of these test cases is to find the best solution, whether or not it is currently being used.
* ISO 8601 date with punctuation (YYYY-MM-DD)
* ISO 8601 datetime with punctuation (YYYY-MM-DDTHH:MM:SS)
* ISO 8601 datetime with punctuation and no seconds (YYYY-MM-DDTHH:MM)
* ISO 8601 UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SSZ)
* ISO 8601 pre-UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SS+HH:MM)
* ISO 8601 pre-UTC datetime with punctuation and no timezone minutes (YYYY-MM-DDTHH:MM:SS+HH)
* ISO 8601 post-UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SS-HH:MM)
* ISO 8601 post-UTC datetime with punctuation and no timezone minutes (YYYY-MM-DDTHH:MM:SS-HH)
* ISO 8601 datetime with punctuation but w/o timezone punctuation. ''The hypothesis is that something like "eleven o'clock plus oh seven hundred" may be more understandable than "eleven o'clock plus seven o'clock" (similarly for the hyphen, read as "dash").''
** pre-UTC (YYYY-MM-DDTHH:MM:SS+HHMM)
** post-UTC (YYYY-MM-DDTHH:MM:SS-HHMM)
* GEO Latitude/Longitude coordinates.
* ISO 8601 durations
* ISO 8601 recurrences

=== Rejected Data formats ===
Dates without punctuation as they have proved unusable. Proof is premise for [[http://www.webstandards.org/2007/04/27/haccessibility/ hAccessibility]] article on the Web Standards Project Buzz blog. Window Eyes and JAWS read un-punctuated dates as single number. [[http://www.webstandards.org/files/atf_microformats/jaws.mp3 JAWS 8 on IE7 citation (MP3 Audio)]] of "twenty million seventy-thousand three-hundred twelve" is reason enough for rejection.
* ISO 8601 date without dashes (YYYYMMDD)
* ISO 8601 datetime without dashes and colons (YYYYMMDDTHHMMSS)
* ISO 8601 datetime without dashes and colons and no seconds (YYYYMMDDTHHMM)
* ISO 8601 UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ)
* ISO 8601 pre-UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ+HHMM)
* ISO 8601 pre-UTC datetime without dashes and colons and no timezone minutes (YYYYMMDDTHHMMSSZ+HH)
* ISO 8601 post-UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ-HHMM)
* ISO 8601 post-UTC datetime without dashes and colons and no timezone minutes (YYYYMMDDTHHMMSSZ-HH)

===Markup Possibilities===
==== Valid HTML4 ====
* abbr-design-pattern (as currently recommended)
* SPAN element with title attribute.
* DFN element with title attribute.
* Non-linked anchor element with title attribute. (<code><nowiki><a class="dtstart" title="20070713">13th</a></nowiki></code>)
* Nested SPAN element.
* Nested ABBR element.
* Nested DFN element (See: [http://microformats.org/discuss/mail/microformats-new/2007-May/000335.html mailing list thread], verify at [http://alistapart.com/articles/hattrick ALA article]).
* Empty INS element with DATETIME attr (<code><nowiki><span class="dtstart">13th<ins datetime="20070713"></ins></span></nowiki></code>)
* Rarely used event handler. e.g. (<code><nowiki><span class="dtstart" onchange="void(20070713)">13th</span></nowiki></code>)
* Hidden INPUT element (undesirable as it requires FORM)
* Empty ABBR element (<code><nowiki><span class="dtstart">13th<abbr title="20070713"></abbr></span></nowiki></code>)

==== Invalid HTML4 ====
Markup possibilities that are invalid in HTML4/XHTML1 are noted here to be clear that they were considered and rejected. Since microformats build on [[posh]], any technique that is invalid semantic (X)HTML is unacceptable for a microformats solution. There is no need to bother testing these.
* SPAN with RDF dc:date attribute.
* SPAN with RDF geo:position attribute.
* Anchor element with name attr (<code><nowiki><a class="dtstart" name="iso8601:20070713">13th</a></nowiki></code>) *[name] does not need to be unique, but a[name] does. [http://www.w3.org/TR/html401/struct/links.html#h-12.2.1 HTML 4.01 Strict, 12.2.1]

==== Markup Rejections ====
* OBJECT with param value. (requires significant extra markup and CSS in order to *behave* correctly)
* OBJECT with in-page data attribute. (See [[include-pattern-feedback#Objects_and_Browser_Behavior]])

===Screenreader Language Pronunciations===
* English
* Spanish (need volunteer native Spanish speaker screen reader user)
* ?

===Verbosity settings===

* Punctuation, speak none.
* Punctuation, speak some.
* Punctuation, speak all.
* Title attributes, speak none.
* Title attributes, speak some (abbr and acronym).
* Title attributes, speak all.

===Screenreaders===
* Freedom Scientific JAWS (multiple versions TBD)
* GW Micro Window Eyes (multiple versions TBD)
* Apple Voiceover (multiple versions TBD)
* Dolphin HAL (multiple versions TBD)

== Results ==

To be determined.

== See Also ==
* [[accessibility]]
* [[assistive-technology]]

assistive-technology-abbr-results

2007-07-06T06:57:06Z

JamesCraig: /* Markup Possibilities */ added non-linked anchor example

<h1>assistive technology abbr results</h1>
This page is for document the precise results of using [[assistive-technology]] with real world examples in the wild of the abbr design pattern, as nearly always used by [[hcalendar|hCalendar]] (e.g. dtstart, dtend), often by [[hreview|hReview]] (e.g. dtreviewed, rating) and sometimes by [[hcard|hCard]] (e.g. bday, type subproperty).

__TOC__

Each [[assistive-technology]] listed here MUST link to a precise description of the tool/service on the [[assistive-technology]] page, including version number, when published, etc.

Each test result listed for each assistive technology MUST link to the real world example that was tested.

== Test Cases ==
The [http://www.webstandards.org/action/atf/ WasP Accessibility Task Force] is working on a set of extended test cases that will cover the following data formats and markup formats. Please add to the list so we can create a comprehensive result set.

===Data Formats===
Please provide hyperlinks to examples in the wild for each case that is to be tested. Test cases with example in the wild URLs merit more testing than those without. However, the purpose of these test cases is to find the best solution, whether or not it is currently being used.
* ISO 8601 date with punctuation (YYYY-MM-DD)
* ISO 8601 datetime with punctuation (YYYY-MM-DDTHH:MM:SS)
* ISO 8601 datetime with punctuation and no seconds (YYYY-MM-DDTHH:MM)
* ISO 8601 UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SSZ)
* ISO 8601 pre-UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SS+HH:MM)
* ISO 8601 pre-UTC datetime with punctuation and no timezone minutes (YYYY-MM-DDTHH:MM:SS+HH)
* ISO 8601 post-UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SS-HH:MM)
* ISO 8601 post-UTC datetime with punctuation and no timezone minutes (YYYY-MM-DDTHH:MM:SS-HH)
* ISO 8601 datetime with punctuation but w/o timezone punctuation. ''The hypothesis is that something like "eleven o'clock plus oh seven hundred" may be more understandable than "eleven o'clock plus seven o'clock" (similarly for the hyphen, read as "dash").''
** pre-UTC (YYYY-MM-DDTHH:MM:SS+HHMM)
** post-UTC (YYYY-MM-DDTHH:MM:SS-HHMM)
* GEO Latitude/Longitude coordinates.
* ISO 8601 durations
* ISO 8601 recurrences

=== Rejected Data formats ===
Dates without punctuation as they have proved unusable. Proof is premise for [[http://www.webstandards.org/2007/04/27/haccessibility/ hAccessibility]] article on the Web Standards Project Buzz blog. Window Eyes and JAWS read un-punctuated dates as single number. [[http://www.webstandards.org/files/atf_microformats/jaws.mp3 JAWS 8 on IE7 citation (MP3 Audio)]] of "twenty million seventy-thousand three-hundred twelve" is reason enough for rejection.
* ISO 8601 date without dashes (YYYYMMDD)
* ISO 8601 datetime without dashes and colons (YYYYMMDDTHHMMSS)
* ISO 8601 datetime without dashes and colons and no seconds (YYYYMMDDTHHMM)
* ISO 8601 UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ)
* ISO 8601 pre-UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ+HHMM)
* ISO 8601 pre-UTC datetime without dashes and colons and no timezone minutes (YYYYMMDDTHHMMSSZ+HH)
* ISO 8601 post-UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ-HHMM)
* ISO 8601 post-UTC datetime without dashes and colons and no timezone minutes (YYYYMMDDTHHMMSSZ-HH)

===Markup Possibilities===
==== Valid HTML4 ====
* abbr-design-pattern (as currently recommended)
* OBJECT with param value.
* SPAN element with title attribute.
* DFN element with title attribute.
* Non-linked anchor element with title attribute. (<code><nowiki><a class="dtstart" title="20070713">13th</a></nowiki></code>)
* Nested SPAN element.
* Nested ABBR element.
* Nested DFN element (See: [http://microformats.org/discuss/mail/microformats-new/2007-May/000335.html mailing list thread], verify at [http://alistapart.com/articles/hattrick ALA article]).
* Empty INS element with DATETIME attr (<code><nowiki><span class="dtstart">13th<ins datetime="20070713"></ins></span></nowiki></code>)
* Rarely used event handler. e.g. (<code><nowiki><span class="dtstart" onchange="void(20070713)">13th</span></nowiki></code>)
* Hidden INPUT element (undesirable as it requires FORM)
* Empty ABBR element (<code><nowiki><span class="dtstart">13th<abbr title="20070713"></abbr></span></nowiki></code>)

==== Invalid HTML4 ====
Markup possibilities that are invalid in HTML4/XHTML1 are noted here to be clear that they were considered and rejected. Since microformats build on [[posh]], any technique that is invalid semantic (X)HTML is unacceptable for a microformats solution. There is no need to bother testing these.
* SPAN with RDF dc:date attribute.
* SPAN with RDF geo:position attribute.
* Anchor element with name attr (<code><nowiki><a class="dtstart" name="iso8601:20070713">13th</a></nowiki></code>) *[name] does not need to be unique, but a[name] does. [http://www.w3.org/TR/html401/struct/links.html#h-12.2.1 HTML 4.01 Strict, 12.2.1]

==== Markup Rejections ====
* OBJECT with in-page data attribute. (See [[include-pattern-feedback#Objects_and_Browser_Behavior]])

===Screenreader Language Pronunciations===
* English
* Spanish (need volunteer native Spanish speaker screen reader user)
* ?

===Verbosity settings===

* Punctuation, speak none.
* Punctuation, speak some.
* Punctuation, speak all.
* Title attributes, speak none.
* Title attributes, speak some (abbr and acronym).
* Title attributes, speak all.

===Screenreaders===
* Freedom Scientific JAWS (multiple versions TBD)
* GW Micro Window Eyes (multiple versions TBD)
* Apple Voiceover (multiple versions TBD)
* Dolphin HAL (multiple versions TBD)

== Results ==

To be determined.

== See Also ==
* [[accessibility]]
* [[assistive-technology]]

assistive-technology-abbr-results

2007-07-06T06:55:41Z

JamesCraig: /* Markup Possibilities */ using nowiki tags instead of char ents

<h1>assistive technology abbr results</h1>
This page is for document the precise results of using [[assistive-technology]] with real world examples in the wild of the abbr design pattern, as nearly always used by [[hcalendar|hCalendar]] (e.g. dtstart, dtend), often by [[hreview|hReview]] (e.g. dtreviewed, rating) and sometimes by [[hcard|hCard]] (e.g. bday, type subproperty).

__TOC__

Each [[assistive-technology]] listed here MUST link to a precise description of the tool/service on the [[assistive-technology]] page, including version number, when published, etc.

Each test result listed for each assistive technology MUST link to the real world example that was tested.

== Test Cases ==
The [http://www.webstandards.org/action/atf/ WasP Accessibility Task Force] is working on a set of extended test cases that will cover the following data formats and markup formats. Please add to the list so we can create a comprehensive result set.

===Data Formats===
Please provide hyperlinks to examples in the wild for each case that is to be tested. Test cases with example in the wild URLs merit more testing than those without. However, the purpose of these test cases is to find the best solution, whether or not it is currently being used.
* ISO 8601 date with punctuation (YYYY-MM-DD)
* ISO 8601 datetime with punctuation (YYYY-MM-DDTHH:MM:SS)
* ISO 8601 datetime with punctuation and no seconds (YYYY-MM-DDTHH:MM)
* ISO 8601 UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SSZ)
* ISO 8601 pre-UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SS+HH:MM)
* ISO 8601 pre-UTC datetime with punctuation and no timezone minutes (YYYY-MM-DDTHH:MM:SS+HH)
* ISO 8601 post-UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SS-HH:MM)
* ISO 8601 post-UTC datetime with punctuation and no timezone minutes (YYYY-MM-DDTHH:MM:SS-HH)
* ISO 8601 datetime with punctuation but w/o timezone punctuation. ''The hypothesis is that something like "eleven o'clock plus oh seven hundred" may be more understandable than "eleven o'clock plus seven o'clock" (similarly for the hyphen, read as "dash").''
** pre-UTC (YYYY-MM-DDTHH:MM:SS+HHMM)
** post-UTC (YYYY-MM-DDTHH:MM:SS-HHMM)
* GEO Latitude/Longitude coordinates.
* ISO 8601 durations
* ISO 8601 recurrences

=== Rejected Data formats ===
Dates without punctuation as they have proved unusable. Proof is premise for [[http://www.webstandards.org/2007/04/27/haccessibility/ hAccessibility]] article on the Web Standards Project Buzz blog. Window Eyes and JAWS read un-punctuated dates as single number. [[http://www.webstandards.org/files/atf_microformats/jaws.mp3 JAWS 8 on IE7 citation (MP3 Audio)]] of "twenty million seventy-thousand three-hundred twelve" is reason enough for rejection.
* ISO 8601 date without dashes (YYYYMMDD)
* ISO 8601 datetime without dashes and colons (YYYYMMDDTHHMMSS)
* ISO 8601 datetime without dashes and colons and no seconds (YYYYMMDDTHHMM)
* ISO 8601 UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ)
* ISO 8601 pre-UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ+HHMM)
* ISO 8601 pre-UTC datetime without dashes and colons and no timezone minutes (YYYYMMDDTHHMMSSZ+HH)
* ISO 8601 post-UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ-HHMM)
* ISO 8601 post-UTC datetime without dashes and colons and no timezone minutes (YYYYMMDDTHHMMSSZ-HH)

===Markup Possibilities===
==== Valid HTML4 ====
* abbr-design-pattern (as currently recommended)
* OBJECT with param value.
* SPAN element with title attribute.
* DFN element with title attribute.
* Non-linked anchor element with title attribute.
* Nested SPAN element.
* Nested ABBR element.
* Nested DFN element (See: [http://microformats.org/discuss/mail/microformats-new/2007-May/000335.html mailing list thread], verify at [http://alistapart.com/articles/hattrick ALA article]).
* Empty INS element with DATETIME attr (<code><nowiki><span class="dtstart">13th<ins datetime="20070713"></ins></span></nowiki></code>)
* Rarely used event handler. e.g. (<code><nowiki><span class="dtstart" onchange="void(20070713)">13th</span></nowiki></code>)
* Hidden INPUT element (undesirable as it requires FORM)
* Empty ABBR element (<code><nowiki><span class="dtstart">13th<abbr title="20070713"></abbr></span></nowiki></code>)

==== Invalid HTML4 ====
Markup possibilities that are invalid in HTML4/XHTML1 are noted here to be clear that they were considered and rejected. Since microformats build on [[posh]], any technique that is invalid semantic (X)HTML is unacceptable for a microformats solution. There is no need to bother testing these.
* SPAN with RDF dc:date attribute.
* SPAN with RDF geo:position attribute.
* Anchor element with name attr (<code><nowiki><a class="dtstart" name="iso8601:20070713">13th</a></nowiki></code>) *[name] does not need to be unique, but a[name] does. [http://www.w3.org/TR/html401/struct/links.html#h-12.2.1 HTML 4.01 Strict, 12.2.1]

==== Markup Rejections ====
* OBJECT with in-page data attribute. (See [[include-pattern-feedback#Objects_and_Browser_Behavior]])

===Screenreader Language Pronunciations===
* English
* Spanish (need volunteer native Spanish speaker screen reader user)
* ?

===Verbosity settings===

* Punctuation, speak none.
* Punctuation, speak some.
* Punctuation, speak all.
* Title attributes, speak none.
* Title attributes, speak some (abbr and acronym).
* Title attributes, speak all.

===Screenreaders===
* Freedom Scientific JAWS (multiple versions TBD)
* GW Micro Window Eyes (multiple versions TBD)
* Apple Voiceover (multiple versions TBD)
* Dolphin HAL (multiple versions TBD)

== Results ==

To be determined.

== See Also ==
* [[accessibility]]
* [[assistive-technology]]

assistive-technology-abbr-results

2007-07-06T06:35:51Z

JamesCraig: /* Markup Possibilities */ rejecting one format and other minor changes

<h1>assistive technology abbr results</h1>
This page is for document the precise results of using [[assistive-technology]] with real world examples in the wild of the abbr design pattern, as nearly always used by [[hcalendar|hCalendar]] (e.g. dtstart, dtend), often by [[hreview|hReview]] (e.g. dtreviewed, rating) and sometimes by [[hcard|hCard]] (e.g. bday, type subproperty).

__TOC__

Each [[assistive-technology]] listed here MUST link to a precise description of the tool/service on the [[assistive-technology]] page, including version number, when published, etc.

Each test result listed for each assistive technology MUST link to the real world example that was tested.

== Test Cases ==
The [http://www.webstandards.org/action/atf/ WasP Accessibility Task Force] is working on a set of extended test cases that will cover the following data formats and markup formats. Please add to the list so we can create a comprehensive result set.

===Data Formats===
Please provide hyperlinks to examples in the wild for each case that is to be tested. Test cases with example in the wild URLs merit more testing than those without. However, the purpose of these test cases is to find the best solution, whether or not it is currently being used.
* ISO 8601 date with punctuation (YYYY-MM-DD)
* ISO 8601 datetime with punctuation (YYYY-MM-DDTHH:MM:SS)
* ISO 8601 datetime with punctuation and no seconds (YYYY-MM-DDTHH:MM)
* ISO 8601 UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SSZ)
* ISO 8601 pre-UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SS+HH:MM)
* ISO 8601 pre-UTC datetime with punctuation and no timezone minutes (YYYY-MM-DDTHH:MM:SS+HH)
* ISO 8601 post-UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SS-HH:MM)
* ISO 8601 post-UTC datetime with punctuation and no timezone minutes (YYYY-MM-DDTHH:MM:SS-HH)
* ISO 8601 datetime with punctuation but w/o timezone punctuation. ''The hypothesis is that something like "eleven o'clock plus oh seven hundred" may be more understandable than "eleven o'clock plus seven o'clock" (similarly for the hyphen, read as "dash").''
** pre-UTC (YYYY-MM-DDTHH:MM:SS+HHMM)
** post-UTC (YYYY-MM-DDTHH:MM:SS-HHMM)
* GEO Latitude/Longitude coordinates.
* ISO 8601 durations
* ISO 8601 recurrences

=== Rejected Data formats ===
Dates without punctuation as they have proved unusable. Proof is premise for [[http://www.webstandards.org/2007/04/27/haccessibility/ hAccessibility]] article on the Web Standards Project Buzz blog. Window Eyes and JAWS read un-punctuated dates as single number. [[http://www.webstandards.org/files/atf_microformats/jaws.mp3 JAWS 8 on IE7 citation (MP3 Audio)]] of "twenty million seventy-thousand three-hundred twelve" is reason enough for rejection.
* ISO 8601 date without dashes (YYYYMMDD)
* ISO 8601 datetime without dashes and colons (YYYYMMDDTHHMMSS)
* ISO 8601 datetime without dashes and colons and no seconds (YYYYMMDDTHHMM)
* ISO 8601 UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ)
* ISO 8601 pre-UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ+HHMM)
* ISO 8601 pre-UTC datetime without dashes and colons and no timezone minutes (YYYYMMDDTHHMMSSZ+HH)
* ISO 8601 post-UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ-HHMM)
* ISO 8601 post-UTC datetime without dashes and colons and no timezone minutes (YYYYMMDDTHHMMSSZ-HH)

===Markup Possibilities===
==== Valid HTML4 ====
* abbr-design-pattern (as currently recommended)
* OBJECT with param value.
* SPAN element with title attribute.
* DFN element with title attribute.
* Nested SPAN element.
* Nested ABBR element.
* Nested DFN element (See: [http://microformats.org/discuss/mail/microformats-new/2007-May/000335.html mailing list thread], verify at [http://alistapart.com/articles/hattrick ALA article]).
* Empty INS element with DATETIME attr (<code><span class="dtstart">13th<ins datetime="20070713"></ins></span></code>)
* Rarely used event handler. e.g. (<code><span class="dtstart" onchange="void(20070713)">13th</span></code>)
* Hidden INPUT element (undesirable as it requires FORM)
* Empty ABBR element (<code><nowiki><span class="dtstart">13th<abbr title="20070713"></abbr></span></nowiki></code>)

==== Invalid HTML4 ====
Markup possibilities that are invalid in HTML4/XHTML1 are noted here to be clear that they were considered and rejected. Since microformats build on [[posh]], any technique that is invalid semantic (X)HTML is unacceptable for a microformats solution. There is no need to bother testing these.
* SPAN with RDF dc:date attribute.
* SPAN with RDF geo:position attribute.
* Anchor element with name attr (<code><a class="dtstart" name="iso8601:20070713">13th</a></code>) *[name] does not need to be unique, but a[name] does. [http://www.w3.org/TR/html401/struct/links.html#h-12.2.1 HTML 4.01 Strict, 12.2.1]

==== Markup Rejections ====
* OBJECT with in-page data attribute. (See [[include-pattern-feedback#Objects_and_Browser_Behavior]])

===Screenreader Language Pronunciations===
* English
* Spanish (need volunteer native Spanish speaker screen reader user)
* ?

===Verbosity settings===

* Punctuation, speak none.
* Punctuation, speak some.
* Punctuation, speak all.
* Title attributes, speak none.
* Title attributes, speak some (abbr and acronym).
* Title attributes, speak all.

===Screenreaders===
* Freedom Scientific JAWS (multiple versions TBD)
* GW Micro Window Eyes (multiple versions TBD)
* Apple Voiceover (multiple versions TBD)
* Dolphin HAL (multiple versions TBD)

== Results ==

To be determined.

== See Also ==
* [[accessibility]]
* [[assistive-technology]]

datetime-design-pattern

2007-07-05T23:00:56Z

JamesCraig: /* Discussion */ answering questions

'''This page is a draft.'''

= Datetime Design Pattern =
This is a page for exploring a datetime design pattern.

== Purpose ==
* Use the [[datetime-design-pattern]] to make datetimes that are human readable also formally machine readable.

== Practical Need ==
* This design pattern arose as a result of solving the practical need for human readable dates for [[hcalendar|hCalendar]].

== How to use it ==
* enclose the human-friendly datetime that you want to make machine readable with <code><abbr></code>
* as per the [[class-design-pattern]], add the appropriate <code>class</code> attribute to the <code>abbr</code> element
* add a <code>title</code> attribute to the <code>abbr</code> element with the machine readable ISO8601 datetime or date as the value

==Current uses==

The pattern, which is now available as part of [[hcalendar|hCalendar]], [[hcard|hCard]] and [[hreview|hReview]], is:

:<pre><abbr class="foo" title="YYYY-MM-DDTHH:MM:SS+ZZ:ZZ">Date Time</abbr></pre>

where foo is the semantic classname which is being applied to this date/time, the title of the <abbr> is an ISO 8601 date/time, with an appropriate level of specificity, and "Date Time" is a human-friendly representation of the same date/time.

An alternative, if you are using UTC-based timestamps, would be:

:<pre><abbr class="foo" title="YYYY-MM-DDTHH:MM:SSZ">Date Time</abbr></pre>

with a single "Z" as per [http://en.wikipedia.org/wiki/ISO_8601 ISO 8601]

== Profile of ISO8601 ==

We recommend that any [[microformat]] using the date-time-design pattern use a profile of ISO8601. There are currently two widely used profiles which SHOULD be reused.

* RFC 3339
* [http://www.w3.org/TR/NOTE-datetime W3C Note on Datetimes]

==Accessibility issues==

Note: There are some accessibility concerns with Datetime Design Pattern that being addressed as part of the [[abbr-design-pattern-issues]] discussion. Possible change recommendations may follow after the accessibility testing is complete.

== Discussion ==

This pattern is likely to be highly resuable.

--[[User:RyanKing]]

Can this not be viewed as a microformat in itself?

--[[User:DimitriGlazkov]]

It could, but inventing a microformat for the sake of inventing a microformat is against the microformat principles.
If there is a specific real world problem (and uses cases) that such an elemental microformat would solve, then it would be worth considering.

Until then it is best to keep the <abbr> datetime concept merely as a microformat design pattern, to be used in _actual_ microformats that have a demonstrated practical need.

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

Excerpt from #microformats Aug 18th. Please edit!

<pre>
Aug 18 15:16:14 <Tantek> DanC, what do you think of RFC3339?
Aug 18 15:17:14 <Tantek> ISO8601 subset
Aug 18 15:17:19 <DanC> Date and Time on the Internet: Timestamps http://www.ietf.org/rfc/rfc3339.txt
Aug 18 15:17:30 <DanC> Klyne is a good guy. I wonder if I talked with him about this.
Aug 18 15:17:32 <Tantek> compat with W3C-NOTE-DATETIME
Aug 18 15:17:50 <Tantek> compat with xsd:dateTime
Aug 18 15:17:57 <Tantek> it's a strict intersection subset
Aug 18 15:17:59 <DanC> I consider W3C-NOTE-DATETIME obsoleted by XML Schema datatype-- yeah.. xsd:dateTime
Aug 18 15:18:32 <Tantek> compare/contrast normatively using xsd:dateTime vs. RFC3339
Aug 18 15:18:41 <Tantek> note: Atom 1.0 chose RFC3339
Aug 18 15:18:50 <Tantek> i would like input from the microformats community on this
Aug 18 15:19:27 <DanC> in what context are you evaluating RFC 3339?
Aug 18 15:19:28 <jcgregorio> http://bitworking.org/news/Date_Constructs_in_the_Atom_Syndication_Format
Aug 18 15:21:24 <DanC> which microformat is the question coming from, Tantek ?
Aug 18 15:23:31 <DanC> " The grammar element time-second may have the value "60" at the end of
Aug 18 15:23:31 <DanC> months in which a leap second occurs" The XML Schema WG is in the 27th level of
leap-second-hell for the past few months, I gather.
Aug 18 15:24:21 <DanC> yeah... here's the scary bit: " Leap seconds cannot be predicted far into the
future. The
Aug 18 15:24:21 <DanC> International Earth Rotation Service publishes bulletins [IERS] that
Aug 18 15:24:21 <DanC> announce leap seconds with a few weeks' warning."
Aug 18 15:26:03 <Tantek> DanC, which microformats? any/all that use datetime fields.
Aug 18 15:26:36 <DanC> hard to give useful advice, then.
Aug 18 15:26:58 <DanC> I expect they'll use datetime fields for different things that have different
cost/benefit trade-offs
Aug 18 15:27:26 <DanC> do you know of any particular differences that matter to anybody?
Aug 18 15:56:43 <KragenSitaker> RFC3339 suggests -07:00, which seems like an improvement over -0700 anyway
Aug 18 15:56:49 <Tantek> Kragen, agreed
Aug 18 15:57:01 <Tantek> RFC3339 is certainly preferable to the ISO8601 subset in iCalendar
Aug 18 16:05:57 <DanC> Tantek's right, Kragen; iCalendar looks like it solves the local timezone
problem but doesn't.
Aug 18 16:06:14 <DanC> and it's true that there's no standard solution to the local timezone problem
Aug 18 16:06:39 <Tantek> so instead of appearing to solve the problem but not solving it, we chose to
provide the ability to *approximate* the local timezone using e.g. "-07:00"
Aug 18 16:06:49 <DanC> the simplest thing is to have people use Z time in hCalendar. But I gather
that's unacceptably unusable?
Aug 18 16:07:35 <Tantek> DanC, yes, the simplest thing is to have everyone use UTC Z
Aug 18 16:07:38 <Tantek> However
Aug 18 16:07:50 <Tantek> it is not *nearly* as usuable/verifiable
Aug 18 16:07:55 <Tantek> as -07:00 etc.
Aug 18 16:08:02 <Tantek> hence the decision to go with the latter
Aug 18 16:08:12 <Tantek> some degree of human verifiability is important here
Aug 18 16:14:21 <Tantek> DanC, my perception is that RFC3339 is a subset
Aug 18 16:17:00 <DanC> time-numoffset = ("+" / "-") time-hour ":" time-minute
Aug 18 16:17:34 <DanC> ok, then I can't see any differences. (modulo recent leap seconds issues that
may affect xsd:dateTime )
Aug 18 16:18:07 <Tantek> would be interesting to know why Atom 1.0 chose RFC3339 over xsd:dateTime
Aug 18 16:18:21 <Tantek> if there was a "real" reason or if it was arbitrary / coin-flip.
</pre>

Here's an exhaustive [http://www.imc.org/atom-syntax/mail-archive/msg13103.html comparison] from ndw. I think xsd:dateTime also allows unqualified local times, while RFC3339 allows only UTC with no known timezone (-00:00). In the end, Atompub followed the advice of [http://www.imc.org/atom-syntax/mail-archive/msg13244.html Sam Ruby] and [http://www.imc.org/atom-syntax/mail-archive/msg13248.html Scott Hollenbeck], our area director. Atom dates make some additional restrictions on RFC3339, such as uppercase T and Z characters for compatibility with xsd:dateTime, RFC3339, W3C-DTF, and ISO8601. --[http://franklinmint.fm Robert Sayre]

<pre>
Aug 18 16:18:43 <KragenSitaker> rfc3339 is pretty short.
Aug 18 16:19:36 <Tantek> DanC, BTW, which came first? REC for xsd:dateTime or RFC3339?
Aug 18 16:19:50 <DanC> RFC3339 is dated July 2002 ...
Aug 18 16:19:54 <KragenSitaker> Right --- and you might be able to understand xsd:dateTime without
reading all of xml schema, you wouldn't be confident of it
Aug 18 16:20:25 <DanC> W3C Recommendation 28 October 2004 ... but that's 2nd ed...
Aug 18 16:20:47 <DanC> W3C Recommendation 02 May 2001
Aug 18 16:22:10 <DanC> I don't see a BNF in http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/#dateTime ...
Aug 18 16:22:43 <KragenSitaker> yeah, appendix D of the current xml schema datatypes document seems
a little scanty, actually
Aug 18 16:23:28 <DanC> ah... 2nd ed of http://www.w3.org/TR/xmlschema-2/#date is much more
explicit about syntax.
Aug 18 16:23:30 <KragenSitaker> it's 1100 words but still doesn't give any examples
Aug 18 16:23:35 <DanC> still, it's given in prose and not BNF
Aug 18 16:24:17 <KragenSitaker> sections 3.2.9 through 3.2.14 seem to be the relevant ones around #date
Aug 18 16:24:29 <KragenSitaker> which is another 2200 words
Aug 18 16:24:42 <DanC> wow... they changed the canonical form of date from always-Z to
timezone-allowed between 1st edition and 2nd edition
Aug 18 16:25:01 <Tantek> Kragen, DanC, these are very good analyses
Aug 18 16:25:21 <Tantek> could I ask you to summarize the pros/cons for each in a new section at
end of http://microformats.org/wiki/datetime-design-pattern
Aug 18 16:25:22 <Tantek> ?
Aug 18 16:25:58 <KragenSitaker> rfc 3339 is 4000 words, excluding the last two pages of boilerplate.
Aug 18 16:26:31 <KragenSitaker> so it's actually longer than the datetime-relevant parts of XSD but it
seems much more rigorous and clear
Aug 18 16:28:37 <DanC> my advice is: normatively cite both, and claim they specify the same
syntax, and let anybody who discovers otherwise send you a bug report
with a test case
Aug 18 16:29:12 <KragenSitaker> danc: nice hack
</pre>

The RFC3339 has a mandatory TIME portion of the DATE-TIME. Some vCard/iCalendar DATE-TIME stamps can omit the TIME. For instance, DTSTART, if that is a full day event, then you can omit the time. BDAY in vCard can be respresented by only a DATE. I like the idea of restricting the possible date formats, but i think that TIME should be optional, which it isn't in RFC3339. - [http://suda.co.uk/ brian suda]

RFC 3339 allows lowercase 't' and 'z' while XSD doesn't. Specifying RFC 3339 plus 'T' and 'Z' MUST be caps will make them the same. - [http://bitworking.org Joe Gregorio]

---

A few questions: asked by [[User:CharlesBelov|CharlesBelov]] 16:57, 24 Apr 2007 (PDT), answered by [[User:JamesCraig|JamesCraig]] on 15:58, 5 Jul 2007 (PDT).

# Would it make more sense for documenting the alternative codings pitting the abbr tag vs. other tags to be on this page? ''Answer: That documentation should go on the [[assistive-technology-abbr-results]] page.''
# Would using the title attribute of the abbr tag to encode the machine-readable date in fact cause a failure of WCAG 2.0 Accessibility? What about USA Section 508? It does appear to violate Technique for WCAG 2.0 [http://www.w3.org/TR/WCAG20-TECHS/#H28 H28: Providing definitions for abbreviations by using the abbr and acronym elements], although that is a supporting document and does not have the force of a guideline. ''Answer: Yes, it appears that is in violation of WCAG, 508, et al, so alternatives are being discussed on the [[assistive-technology-abbr-results]] page.''
# In order to maintain accessibility, would it make sense to enclose the machine-readable date in a span with a style of "display:none" instead of using the abbr tag? ''Answer: please refer to and add any suggestions to [[assistive-technology-abbr-results]].''
# For that matter, wouldn't you want to style such an abbr tag with text-decoration:none to hide that an abbr tag was used? Otherwise, visitors might cursor over the time, see the machine time, and be annoyed that their time was wasted or else be confused. And I don't think you can suppress the title from coming up if the human-readable time was inadvertently hovered. ''Answer: Microformats should not rely on CSS in order to work properly, but again, that discussion can be found here: [[assistive-technology-abbr-results]].''

== Code ==
The following regular expression (parsed VERBOSE) should break apart a datetime and cover many lightly broken cases seen in the wild. This has been tested under Python.

<pre><nowiki>
^
(?P<year>\d\d\d\d)
([-])?(?P<month>\d\d)
([-])?(?P<day>\d\d)
(
(T|\s+)
(?P<hour>\d\d)
(
([:])?(?P<minute>\d\d)
(
([:])?(?P<second>\d\d)
(
([.])?(?P<fraction>\d+)
)?
)?
)?
)?
(
(?P<tzzulu>Z)
|
(?P<tzoffset>[-+])
(?P<tzhour>\d\d)
([:])?(?P<tzminute>\d\d)
)?
$
</nowiki></pre>

== See Also ==

* [[Main_Page#Design_Patterns|All microformat design patterns]]
* [[abbr-design-pattern]] is used by [[datetime-design-pattern]]
* HTML 4.01 definition of <code><[http://www.w3.org/TR/REC-html40/struct/text.html#edef-ABBR abbr]></code> element
* RFC [http://www.faqs.org/rfcs/rfc3339.html 3339]: Date and Time on the Internet: Timestamps
* W3C: [http://www.w3.org/TR/NOTE-datetime Note on Datetimes]
* Markus Kuhn: [http://www.cl.cam.ac.uk/~mgk25/iso-time.html A summary of the international standard date and time notation]
* Wikipedia: [http://en.wikipedia.org/wiki/ISO_8601 ISO 8601]

datetime-design-pattern

2007-07-05T22:50:12Z

JamesCraig: cleaning up FUD

'''This page is a draft.'''

= Datetime Design Pattern =
This is a page for exploring a datetime design pattern.

== Purpose ==
* Use the [[datetime-design-pattern]] to make datetimes that are human readable also formally machine readable.

== Practical Need ==
* This design pattern arose as a result of solving the practical need for human readable dates for [[hcalendar|hCalendar]].

== How to use it ==
* enclose the human-friendly datetime that you want to make machine readable with <code><abbr></code>
* as per the [[class-design-pattern]], add the appropriate <code>class</code> attribute to the <code>abbr</code> element
* add a <code>title</code> attribute to the <code>abbr</code> element with the machine readable ISO8601 datetime or date as the value

==Current uses==

The pattern, which is now available as part of [[hcalendar|hCalendar]], [[hcard|hCard]] and [[hreview|hReview]], is:

:<pre><abbr class="foo" title="YYYY-MM-DDTHH:MM:SS+ZZ:ZZ">Date Time</abbr></pre>

where foo is the semantic classname which is being applied to this date/time, the title of the <abbr> is an ISO 8601 date/time, with an appropriate level of specificity, and "Date Time" is a human-friendly representation of the same date/time.

An alternative, if you are using UTC-based timestamps, would be:

:<pre><abbr class="foo" title="YYYY-MM-DDTHH:MM:SSZ">Date Time</abbr></pre>

with a single "Z" as per [http://en.wikipedia.org/wiki/ISO_8601 ISO 8601]

== Profile of ISO8601 ==

We recommend that any [[microformat]] using the date-time-design pattern use a profile of ISO8601. There are currently two widely used profiles which SHOULD be reused.

* RFC 3339
* [http://www.w3.org/TR/NOTE-datetime W3C Note on Datetimes]

==Accessibility issues==

Note: There are some accessibility concerns with Datetime Design Pattern that being addressed as part of the [[abbr-design-pattern-issues]] discussion. Possible change recommendations may follow after the accessibility testing is complete.

== Discussion ==

This pattern is likely to be highly resuable.

--[[User:RyanKing]]

Can this not be viewed as a microformat in itself?

--[[User:DimitriGlazkov]]

It could, but inventing a microformat for the sake of inventing a microformat is against the microformat principles.
If there is a specific real world problem (and uses cases) that such an elemental microformat would solve, then it would be worth considering.

Until then it is best to keep the <abbr> datetime concept merely as a microformat design pattern, to be used in _actual_ microformats that have a demonstrated practical need.

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

Excerpt from #microformats Aug 18th. Please edit!

<pre>
Aug 18 15:16:14 <Tantek> DanC, what do you think of RFC3339?
Aug 18 15:17:14 <Tantek> ISO8601 subset
Aug 18 15:17:19 <DanC> Date and Time on the Internet: Timestamps http://www.ietf.org/rfc/rfc3339.txt
Aug 18 15:17:30 <DanC> Klyne is a good guy. I wonder if I talked with him about this.
Aug 18 15:17:32 <Tantek> compat with W3C-NOTE-DATETIME
Aug 18 15:17:50 <Tantek> compat with xsd:dateTime
Aug 18 15:17:57 <Tantek> it's a strict intersection subset
Aug 18 15:17:59 <DanC> I consider W3C-NOTE-DATETIME obsoleted by XML Schema datatype-- yeah.. xsd:dateTime
Aug 18 15:18:32 <Tantek> compare/contrast normatively using xsd:dateTime vs. RFC3339
Aug 18 15:18:41 <Tantek> note: Atom 1.0 chose RFC3339
Aug 18 15:18:50 <Tantek> i would like input from the microformats community on this
Aug 18 15:19:27 <DanC> in what context are you evaluating RFC 3339?
Aug 18 15:19:28 <jcgregorio> http://bitworking.org/news/Date_Constructs_in_the_Atom_Syndication_Format
Aug 18 15:21:24 <DanC> which microformat is the question coming from, Tantek ?
Aug 18 15:23:31 <DanC> " The grammar element time-second may have the value "60" at the end of
Aug 18 15:23:31 <DanC> months in which a leap second occurs" The XML Schema WG is in the 27th level of
leap-second-hell for the past few months, I gather.
Aug 18 15:24:21 <DanC> yeah... here's the scary bit: " Leap seconds cannot be predicted far into the
future. The
Aug 18 15:24:21 <DanC> International Earth Rotation Service publishes bulletins [IERS] that
Aug 18 15:24:21 <DanC> announce leap seconds with a few weeks' warning."
Aug 18 15:26:03 <Tantek> DanC, which microformats? any/all that use datetime fields.
Aug 18 15:26:36 <DanC> hard to give useful advice, then.
Aug 18 15:26:58 <DanC> I expect they'll use datetime fields for different things that have different
cost/benefit trade-offs
Aug 18 15:27:26 <DanC> do you know of any particular differences that matter to anybody?
Aug 18 15:56:43 <KragenSitaker> RFC3339 suggests -07:00, which seems like an improvement over -0700 anyway
Aug 18 15:56:49 <Tantek> Kragen, agreed
Aug 18 15:57:01 <Tantek> RFC3339 is certainly preferable to the ISO8601 subset in iCalendar
Aug 18 16:05:57 <DanC> Tantek's right, Kragen; iCalendar looks like it solves the local timezone
problem but doesn't.
Aug 18 16:06:14 <DanC> and it's true that there's no standard solution to the local timezone problem
Aug 18 16:06:39 <Tantek> so instead of appearing to solve the problem but not solving it, we chose to
provide the ability to *approximate* the local timezone using e.g. "-07:00"
Aug 18 16:06:49 <DanC> the simplest thing is to have people use Z time in hCalendar. But I gather
that's unacceptably unusable?
Aug 18 16:07:35 <Tantek> DanC, yes, the simplest thing is to have everyone use UTC Z
Aug 18 16:07:38 <Tantek> However
Aug 18 16:07:50 <Tantek> it is not *nearly* as usuable/verifiable
Aug 18 16:07:55 <Tantek> as -07:00 etc.
Aug 18 16:08:02 <Tantek> hence the decision to go with the latter
Aug 18 16:08:12 <Tantek> some degree of human verifiability is important here
Aug 18 16:14:21 <Tantek> DanC, my perception is that RFC3339 is a subset
Aug 18 16:17:00 <DanC> time-numoffset = ("+" / "-") time-hour ":" time-minute
Aug 18 16:17:34 <DanC> ok, then I can't see any differences. (modulo recent leap seconds issues that
may affect xsd:dateTime )
Aug 18 16:18:07 <Tantek> would be interesting to know why Atom 1.0 chose RFC3339 over xsd:dateTime
Aug 18 16:18:21 <Tantek> if there was a "real" reason or if it was arbitrary / coin-flip.
</pre>

Here's an exhaustive [http://www.imc.org/atom-syntax/mail-archive/msg13103.html comparison] from ndw. I think xsd:dateTime also allows unqualified local times, while RFC3339 allows only UTC with no known timezone (-00:00). In the end, Atompub followed the advice of [http://www.imc.org/atom-syntax/mail-archive/msg13244.html Sam Ruby] and [http://www.imc.org/atom-syntax/mail-archive/msg13248.html Scott Hollenbeck], our area director. Atom dates make some additional restrictions on RFC3339, such as uppercase T and Z characters for compatibility with xsd:dateTime, RFC3339, W3C-DTF, and ISO8601. --[http://franklinmint.fm Robert Sayre]

<pre>
Aug 18 16:18:43 <KragenSitaker> rfc3339 is pretty short.
Aug 18 16:19:36 <Tantek> DanC, BTW, which came first? REC for xsd:dateTime or RFC3339?
Aug 18 16:19:50 <DanC> RFC3339 is dated July 2002 ...
Aug 18 16:19:54 <KragenSitaker> Right --- and you might be able to understand xsd:dateTime without
reading all of xml schema, you wouldn't be confident of it
Aug 18 16:20:25 <DanC> W3C Recommendation 28 October 2004 ... but that's 2nd ed...
Aug 18 16:20:47 <DanC> W3C Recommendation 02 May 2001
Aug 18 16:22:10 <DanC> I don't see a BNF in http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/#dateTime ...
Aug 18 16:22:43 <KragenSitaker> yeah, appendix D of the current xml schema datatypes document seems
a little scanty, actually
Aug 18 16:23:28 <DanC> ah... 2nd ed of http://www.w3.org/TR/xmlschema-2/#date is much more
explicit about syntax.
Aug 18 16:23:30 <KragenSitaker> it's 1100 words but still doesn't give any examples
Aug 18 16:23:35 <DanC> still, it's given in prose and not BNF
Aug 18 16:24:17 <KragenSitaker> sections 3.2.9 through 3.2.14 seem to be the relevant ones around #date
Aug 18 16:24:29 <KragenSitaker> which is another 2200 words
Aug 18 16:24:42 <DanC> wow... they changed the canonical form of date from always-Z to
timezone-allowed between 1st edition and 2nd edition
Aug 18 16:25:01 <Tantek> Kragen, DanC, these are very good analyses
Aug 18 16:25:21 <Tantek> could I ask you to summarize the pros/cons for each in a new section at
end of http://microformats.org/wiki/datetime-design-pattern
Aug 18 16:25:22 <Tantek> ?
Aug 18 16:25:58 <KragenSitaker> rfc 3339 is 4000 words, excluding the last two pages of boilerplate.
Aug 18 16:26:31 <KragenSitaker> so it's actually longer than the datetime-relevant parts of XSD but it
seems much more rigorous and clear
Aug 18 16:28:37 <DanC> my advice is: normatively cite both, and claim they specify the same
syntax, and let anybody who discovers otherwise send you a bug report
with a test case
Aug 18 16:29:12 <KragenSitaker> danc: nice hack
</pre>

The RFC3339 has a mandatory TIME portion of the DATE-TIME. Some vCard/iCalendar DATE-TIME stamps can omit the TIME. For instance, DTSTART, if that is a full day event, then you can omit the time. BDAY in vCard can be respresented by only a DATE. I like the idea of restricting the possible date formats, but i think that TIME should be optional, which it isn't in RFC3339. - [http://suda.co.uk/ brian suda]

RFC 3339 allows lowercase 't' and 'z' while XSD doesn't. Specifying RFC 3339 plus 'T' and 'Z' MUST be caps will make them the same. - [http://bitworking.org Joe Gregorio]

---

A few questions:

1) Would it make more sense for documenting the alternative codings pitting the abbr tag vs. other tags to be on this page?

2) Would using the title attribute of the abbr tag to encode the machine-readable date in fact cause a failure of WCAG 2.0 Accessibility? What about USA Section 508? It does appear to violate Technique for WCAG 2.0 [http://www.w3.org/TR/WCAG20-TECHS/#H28 H28: Providing definitions for abbreviations by using the abbr and acronym elements], although that is a supporting document and does not have the force of a guideline.

3) In order to maintain accessibility, would it make sense to enclose the machine-readable date in a span with a style of "display:none" instead of using the abbr tag?

4) For that matter, wouldn't you want to style such an abbr tag with text-decoration:none to hide that an abbr tag was used? Otherwise, visitors might cursor over the time, see the machine time, and be annoyed that their time was wasted or else be confused. And I don't think you can suppress the title from coming up if the human-readable time was inadvertently hovered.

[[User:CharlesBelov|CharlesBelov]] 16:57, 24 Apr 2007 (PDT)

== Code ==
The following regular expression (parsed VERBOSE) should break apart a datetime and cover many lightly broken cases seen in the wild. This has been tested under Python.

<pre><nowiki>
^
(?P<year>\d\d\d\d)
([-])?(?P<month>\d\d)
([-])?(?P<day>\d\d)
(
(T|\s+)
(?P<hour>\d\d)
(
([:])?(?P<minute>\d\d)
(
([:])?(?P<second>\d\d)
(
([.])?(?P<fraction>\d+)
)?
)?
)?
)?
(
(?P<tzzulu>Z)
|
(?P<tzoffset>[-+])
(?P<tzhour>\d\d)
([:])?(?P<tzminute>\d\d)
)?
$
</nowiki></pre>

== See Also ==

* [[Main_Page#Design_Patterns|All microformat design patterns]]
* [[abbr-design-pattern]] is used by [[datetime-design-pattern]]
* HTML 4.01 definition of <code><[http://www.w3.org/TR/REC-html40/struct/text.html#edef-ABBR abbr]></code> element
* RFC [http://www.faqs.org/rfcs/rfc3339.html 3339]: Date and Time on the Internet: Timestamps
* W3C: [http://www.w3.org/TR/NOTE-datetime Note on Datetimes]
* Markus Kuhn: [http://www.cl.cam.ac.uk/~mgk25/iso-time.html A summary of the international standard date and time notation]
* Wikipedia: [http://en.wikipedia.org/wiki/ISO_8601 ISO 8601]

assistive-technology-abbr-results

2007-05-11T00:10:09Z

JamesCraig: /* Markup Possibilities */ added input[hidden]

<h1>assistive technology abbr results</h1>
This page is for document the precise results of using [[assistive-technology]] with real world examples in the wild of the abbr design pattern, as nearly always used by [[hcalendar|hCalendar]] (e.g. dtstart, dtend), often by [[hreview|hReview]] (e.g. dtreviewed, rating) and sometimes by [[hcard|hCard]] (e.g. bday, type subproperty).

__TOC__

Each [[assistive-technology]] listed here MUST link to a precise description of the tool/service on the [[assistive-technology]] page, including version number, when published, etc.

Each test result listed for each assistive technology MUST link to the real world example that was tested.

== Test Cases ==
The [http://www.webstandards.org/action/atf/ WasP Accessibility Task Force] is working on a set of extended test cases that will cover the following data formats and markup formats. Please add to the list so we can create a comprehensive result set.

===Data Formats===
Please provide hyperlinks to examples in the wild for each case that is to be tested. Test cases with example in the wild URLs merit more testing than those without. However, the purpose of these test cases is to find the best solution, whether or not it is currently being used.
* ISO 8601 date with punctuation (YYYY-MM-DD)
* ISO 8601 datetime with punctuation (YYYY-MM-DDTHH:MM:SS)
* ISO 8601 datetime with punctuation and no seconds (YYYY-MM-DDTHH:MM)
* ISO 8601 UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SSZ)
* ISO 8601 pre-UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SS+HH:MM)
* ISO 8601 pre-UTC datetime with punctuation and no timezone minutes (YYYY-MM-DDTHH:MM:SS+HH)
* ISO 8601 post-UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SS-HH:MM)
* ISO 8601 post-UTC datetime with punctuation and no timezone minutes (YYYY-MM-DDTHH:MM:SS-HH)
* ISO 8601 datetime with punctuation but w/o timezone punctuation. ''The hypothesis is that something like "eleven o'clock plus oh seven hundred" may be more understandable than "eleven o'clock plus seven o'clock" (similarly for the hyphen, read as "dash").''
** pre-UTC (YYYY-MM-DDTHH:MM:SS+HHMM)
** post-UTC (YYYY-MM-DDTHH:MM:SS-HHMM)
* GEO Latitude/Longitude coordinates.
* ISO 8601 durations
* ISO 8601 recurrences

=== Rejected Data formats ===
Dates without punctuation as they have proved unusable. Proof is premise for [[http://www.webstandards.org/2007/04/27/haccessibility/ hAccessibility]] article on the Web Standards Project Buzz blog. Window Eyes and JAWS read un-punctuated dates as single number. [[http://www.webstandards.org/files/atf_microformats/jaws.mp3 JAWS 8 on IE7 citation (MP3 Audio)]] of "twenty million seventy-thousand three-hundred twelve" is reason enough for rejection.
* ISO 8601 date without dashes (YYYYMMDD)
* ISO 8601 datetime without dashes and colons (YYYYMMDDTHHMMSS)
* ISO 8601 datetime without dashes and colons and no seconds (YYYYMMDDTHHMM)
* ISO 8601 UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ)
* ISO 8601 pre-UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ+HHMM)
* ISO 8601 pre-UTC datetime without dashes and colons and no timezone minutes (YYYYMMDDTHHMMSSZ+HH)
* ISO 8601 post-UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ-HHMM)
* ISO 8601 post-UTC datetime without dashes and colons and no timezone minutes (YYYYMMDDTHHMMSSZ-HH)

===Markup Possibilities===
==== Valid HTML4 ====
* abbr-design-pattern (as currently recommended)
* OBJECT with param value.
* OBJECT with in-page data attribute.
* SPAN element with title attribute.
* DFN element with title attribute.
* Nested SPAN element.
* Nested ABBR element.
* Nested DFN element (See: [http://microformats.org/discuss/mail/microformats-new/2007-May/000335.html mailing list thread], verify at [http://alistapart.com/articles/hattrick ALA article]).
* Empty INS element with DATETIME attr (<code><span class="dtstart">13th<ins datetime="20070713"></ins></span></code>)
* Rarely used event handler. e.g. (<code><span class="dtstart" onchange="void(20070713)">13th</span></code>)
* Hidden INPUT element (undesirable as it requires FORM)

==== Invalid HTML4 ====
Markup possibilities that are invalid in HTML4/XHTML1 are noted here to be clear that they were considered and rejected. Since microformats build on [[posh]], any technique that is invalid semantic (X)HTML is unacceptable for a microformats solution. There is no need to bother testing these.
* SPAN with RDF dc:date attribute.
* SPAN with RDF geo:position attribute.
* Anchor element with name attr (<code><a class="dtstart" name="iso8601:20070713">13th</a></code>) *[name] does not need to be unique, but a[name] does. [http://www.w3.org/TR/html401/struct/links.html#h-12.2.1 HTML 4.01 Strict, 12.2.1]

===Screenreader Language Pronunciations===
* English
* Spanish (need volunteer native Spanish speaker screen reader user)
* ?

===Verbosity settings===

* Punctuation, speak none.
* Punctuation, speak some.
* Punctuation, speak all.
* Title attributes, speak none.
* Title attributes, speak some (abbr and acronym).
* Title attributes, speak all.

===Screenreaders===
* Freedom Scientific JAWS (multiple versions TBD)
* GW Micro Window Eyes (multiple versions TBD)
* Apple Voiceover (multiple versions TBD)
* Dolphin HAL (multiple versions TBD)

== Results ==

To be determined.

== See Also ==
* [[accessibility]]
* [[assistive-technology]]

assistive-technology-abbr-results

2007-05-11T00:07:03Z

JamesCraig: /* Markup Possibilities */ moved a[name] to invalid

<h1>assistive technology abbr results</h1>
This page is for document the precise results of using [[assistive-technology]] with real world examples in the wild of the abbr design pattern, as nearly always used by [[hcalendar|hCalendar]] (e.g. dtstart, dtend), often by [[hreview|hReview]] (e.g. dtreviewed, rating) and sometimes by [[hcard|hCard]] (e.g. bday, type subproperty).

__TOC__

Each [[assistive-technology]] listed here MUST link to a precise description of the tool/service on the [[assistive-technology]] page, including version number, when published, etc.

Each test result listed for each assistive technology MUST link to the real world example that was tested.

== Test Cases ==
The [http://www.webstandards.org/action/atf/ WasP Accessibility Task Force] is working on a set of extended test cases that will cover the following data formats and markup formats. Please add to the list so we can create a comprehensive result set.

===Data Formats===
Please provide hyperlinks to examples in the wild for each case that is to be tested. Test cases with example in the wild URLs merit more testing than those without. However, the purpose of these test cases is to find the best solution, whether or not it is currently being used.
* ISO 8601 date with punctuation (YYYY-MM-DD)
* ISO 8601 datetime with punctuation (YYYY-MM-DDTHH:MM:SS)
* ISO 8601 datetime with punctuation and no seconds (YYYY-MM-DDTHH:MM)
* ISO 8601 UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SSZ)
* ISO 8601 pre-UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SS+HH:MM)
* ISO 8601 pre-UTC datetime with punctuation and no timezone minutes (YYYY-MM-DDTHH:MM:SS+HH)
* ISO 8601 post-UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SS-HH:MM)
* ISO 8601 post-UTC datetime with punctuation and no timezone minutes (YYYY-MM-DDTHH:MM:SS-HH)
* ISO 8601 datetime with punctuation but w/o timezone punctuation. ''The hypothesis is that something like "eleven o'clock plus oh seven hundred" may be more understandable than "eleven o'clock plus seven o'clock" (similarly for the hyphen, read as "dash").''
** pre-UTC (YYYY-MM-DDTHH:MM:SS+HHMM)
** post-UTC (YYYY-MM-DDTHH:MM:SS-HHMM)
* GEO Latitude/Longitude coordinates.
* ISO 8601 durations
* ISO 8601 recurrences

=== Rejected Data formats ===
Dates without punctuation as they have proved unusable. Proof is premise for [[http://www.webstandards.org/2007/04/27/haccessibility/ hAccessibility]] article on the Web Standards Project Buzz blog. Window Eyes and JAWS read un-punctuated dates as single number. [[http://www.webstandards.org/files/atf_microformats/jaws.mp3 JAWS 8 on IE7 citation (MP3 Audio)]] of "twenty million seventy-thousand three-hundred twelve" is reason enough for rejection.
* ISO 8601 date without dashes (YYYYMMDD)
* ISO 8601 datetime without dashes and colons (YYYYMMDDTHHMMSS)
* ISO 8601 datetime without dashes and colons and no seconds (YYYYMMDDTHHMM)
* ISO 8601 UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ)
* ISO 8601 pre-UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ+HHMM)
* ISO 8601 pre-UTC datetime without dashes and colons and no timezone minutes (YYYYMMDDTHHMMSSZ+HH)
* ISO 8601 post-UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ-HHMM)
* ISO 8601 post-UTC datetime without dashes and colons and no timezone minutes (YYYYMMDDTHHMMSSZ-HH)

===Markup Possibilities===
==== Valid HTML4 ====
* abbr-design-pattern (as currently recommended)
* OBJECT with param value.
* OBJECT with in-page data attribute.
* SPAN element with title attribute.
* DFN element with title attribute.
* Nested SPAN element.
* Nested ABBR element.
* Nested DFN element (See: [http://microformats.org/discuss/mail/microformats-new/2007-May/000335.html mailing list thread], verify at [http://alistapart.com/articles/hattrick ALA article]).
* Empty INS element with DATETIME attr (<code><span class="dtstart">13th<ins datetime="20070713"></ins></span></code>)
* Rarely used event handler. e.g. (<code><span class="dtstart" onchange="void(20070713)">13th</span></code>)

==== Invalid HTML4 ====
Markup possibilities that are invalid in HTML4/XHTML1 are noted here to be clear that they were considered and rejected. Since microformats build on [[posh]], any technique that is invalid semantic (X)HTML is unacceptable for a microformats solution. There is no need to bother testing these.
* SPAN with RDF dc:date attribute.
* SPAN with RDF geo:position attribute.
* Anchor element with name attr (<code><a class="dtstart" name="iso8601:20070713">13th</a></code>) *[name] does not need to be unique, but a[name] does. [http://www.w3.org/TR/html401/struct/links.html#h-12.2.1 HTML 4.01 Strict, 12.2.1]

===Screenreader Language Pronunciations===
* English
* Spanish (need volunteer native Spanish speaker screen reader user)
* ?

===Verbosity settings===

* Punctuation, speak none.
* Punctuation, speak some.
* Punctuation, speak all.
* Title attributes, speak none.
* Title attributes, speak some (abbr and acronym).
* Title attributes, speak all.

===Screenreaders===
* Freedom Scientific JAWS (multiple versions TBD)
* GW Micro Window Eyes (multiple versions TBD)
* Apple Voiceover (multiple versions TBD)
* Dolphin HAL (multiple versions TBD)

== Results ==

To be determined.

== See Also ==
* [[accessibility]]
* [[assistive-technology]]

assistive-technology-abbr-results

2007-05-10T20:33:16Z

JamesCraig: /* Markup Possibilities */ I really should use "preview" more often.

<h1>assistive technology abbr results</h1>
This page is for document the precise results of using [[assistive-technology]] with real world examples in the wild of the abbr design pattern, as nearly always used by [[hcalendar|hCalendar]] (e.g. dtstart, dtend), often by [[hreview|hReview]] (e.g. dtreviewed, rating) and sometimes by [[hcard|hCard]] (e.g. bday, type subproperty).

__TOC__

Each [[assistive-technology]] listed here MUST link to a precise description of the tool/service on the [[assistive-technology]] page, including version number, when published, etc.

Each test result listed for each assistive technology MUST link to the real world example that was tested.

== Test Cases ==
The [http://www.webstandards.org/action/atf/ WasP Accessibility Task Force] is working on a set of extended test cases that will cover the following data formats and markup formats. Please add to the list so we can create a comprehensive result set.

===Data Formats===
Please provide hyperlinks to examples in the wild for each case that is to be tested. Test cases with example in the wild URLs merit more testing than those without. However, the purpose of these test cases is to find the best solution, whether or not it is currently being used.
* ISO 8601 date with punctuation (YYYY-MM-DD)
* ISO 8601 datetime with punctuation (YYYY-MM-DDTHH:MM:SS)
* ISO 8601 datetime with punctuation and no seconds (YYYY-MM-DDTHH:MM)
* ISO 8601 UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SSZ)
* ISO 8601 pre-UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SS+HH:MM)
* ISO 8601 pre-UTC datetime with punctuation and no timezone minutes (YYYY-MM-DDTHH:MM:SS+HH)
* ISO 8601 post-UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SS-HH:MM)
* ISO 8601 post-UTC datetime with punctuation and no timezone minutes (YYYY-MM-DDTHH:MM:SS-HH)
* ISO 8601 datetime with punctuation but w/o timezone punctuation. ''The hypothesis is that something like "eleven o'clock plus oh seven hundred" may be more understandable than "eleven o'clock plus seven o'clock" (similarly for the hyphen, read as "dash").''
** pre-UTC (YYYY-MM-DDTHH:MM:SS+HHMM)
** post-UTC (YYYY-MM-DDTHH:MM:SS-HHMM)
* GEO Latitude/Longitude coordinates.
* ISO 8601 durations
* ISO 8601 recurrences

=== Rejected Data formats ===
Dates without punctuation as they have proved unusable. Proof is premise for [[http://www.webstandards.org/2007/04/27/haccessibility/ hAccessibility]] article on the Web Standards Project Buzz blog. Window Eyes and JAWS read un-punctuated dates as single number. [[http://www.webstandards.org/files/atf_microformats/jaws.mp3 JAWS 8 on IE7 citation (MP3 Audio)]] of "twenty million seventy-thousand three-hundred twelve" is reason enough for rejection.
* ISO 8601 date without dashes (YYYYMMDD)
* ISO 8601 datetime without dashes and colons (YYYYMMDDTHHMMSS)
* ISO 8601 datetime without dashes and colons and no seconds (YYYYMMDDTHHMM)
* ISO 8601 UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ)
* ISO 8601 pre-UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ+HHMM)
* ISO 8601 pre-UTC datetime without dashes and colons and no timezone minutes (YYYYMMDDTHHMMSSZ+HH)
* ISO 8601 post-UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ-HHMM)
* ISO 8601 post-UTC datetime without dashes and colons and no timezone minutes (YYYYMMDDTHHMMSSZ-HH)

===Markup Possibilities===
==== Valid HTML4 ====
* abbr-design-pattern (as currently recommended)
* OBJECT with param value.
* OBJECT with in-page data attribute.
* SPAN element with title attribute.
* DFN element with title attribute.
* Nested SPAN element.
* Nested ABBR element.
* Nested DFN element (See: [http://microformats.org/discuss/mail/microformats-new/2007-May/000335.html mailing list thread], verify at [http://alistapart.com/articles/hattrick ALA article]).
* Empty INS element with DATETIME attr (<code><span class="dtstart">13th<ins datetime="20070713"></ins></span></code>)
* Rarely used event handler. e.g. (<code><span class="dtstart" onchange="void(20070713)">13th</span></code>)
* Anchor element with name attr (<code><a class="dtstart" name="iso8601:20070713">13th</a></code>)

==== Invalid HTML4 ====
Markup possibilities that are invalid in HTML4/XHTML1 are noted here to be clear that they were considered and rejected. Since microformats build on [[posh]], any technique that is invalid semantic (X)HTML is unacceptable for a microformats solution. There is no need to bother testing these.
* SPAN with RDF dc:date attribute.
* SPAN with RDF geo:position attribute.

===Screenreader Language Pronunciations===
* English
* Spanish (need volunteer native Spanish speaker screen reader user)
* ?

===Verbosity settings===

* Punctuation, speak none.
* Punctuation, speak some.
* Punctuation, speak all.
* Title attributes, speak none.
* Title attributes, speak some (abbr and acronym).
* Title attributes, speak all.

===Screenreaders===
* Freedom Scientific JAWS (multiple versions TBD)
* GW Micro Window Eyes (multiple versions TBD)
* Apple Voiceover (multiple versions TBD)
* Dolphin HAL (multiple versions TBD)

== Results ==

To be determined.

== See Also ==
* [[accessibility]]
* [[assistive-technology]]

assistive-technology-abbr-results

2007-05-10T20:31:39Z

JamesCraig: /* Markup Possibilities */ oops.

<h1>assistive technology abbr results</h1>
This page is for document the precise results of using [[assistive-technology]] with real world examples in the wild of the abbr design pattern, as nearly always used by [[hcalendar|hCalendar]] (e.g. dtstart, dtend), often by [[hreview|hReview]] (e.g. dtreviewed, rating) and sometimes by [[hcard|hCard]] (e.g. bday, type subproperty).

__TOC__

Each [[assistive-technology]] listed here MUST link to a precise description of the tool/service on the [[assistive-technology]] page, including version number, when published, etc.

Each test result listed for each assistive technology MUST link to the real world example that was tested.

== Test Cases ==
The [http://www.webstandards.org/action/atf/ WasP Accessibility Task Force] is working on a set of extended test cases that will cover the following data formats and markup formats. Please add to the list so we can create a comprehensive result set.

===Data Formats===
Please provide hyperlinks to examples in the wild for each case that is to be tested. Test cases with example in the wild URLs merit more testing than those without. However, the purpose of these test cases is to find the best solution, whether or not it is currently being used.
* ISO 8601 date with punctuation (YYYY-MM-DD)
* ISO 8601 datetime with punctuation (YYYY-MM-DDTHH:MM:SS)
* ISO 8601 datetime with punctuation and no seconds (YYYY-MM-DDTHH:MM)
* ISO 8601 UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SSZ)
* ISO 8601 pre-UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SS+HH:MM)
* ISO 8601 pre-UTC datetime with punctuation and no timezone minutes (YYYY-MM-DDTHH:MM:SS+HH)
* ISO 8601 post-UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SS-HH:MM)
* ISO 8601 post-UTC datetime with punctuation and no timezone minutes (YYYY-MM-DDTHH:MM:SS-HH)
* ISO 8601 datetime with punctuation but w/o timezone punctuation. ''The hypothesis is that something like "eleven o'clock plus oh seven hundred" may be more understandable than "eleven o'clock plus seven o'clock" (similarly for the hyphen, read as "dash").''
** pre-UTC (YYYY-MM-DDTHH:MM:SS+HHMM)
** post-UTC (YYYY-MM-DDTHH:MM:SS-HHMM)
* GEO Latitude/Longitude coordinates.
* ISO 8601 durations
* ISO 8601 recurrences

=== Rejected Data formats ===
Dates without punctuation as they have proved unusable. Proof is premise for [[http://www.webstandards.org/2007/04/27/haccessibility/ hAccessibility]] article on the Web Standards Project Buzz blog. Window Eyes and JAWS read un-punctuated dates as single number. [[http://www.webstandards.org/files/atf_microformats/jaws.mp3 JAWS 8 on IE7 citation (MP3 Audio)]] of "twenty million seventy-thousand three-hundred twelve" is reason enough for rejection.
* ISO 8601 date without dashes (YYYYMMDD)
* ISO 8601 datetime without dashes and colons (YYYYMMDDTHHMMSS)
* ISO 8601 datetime without dashes and colons and no seconds (YYYYMMDDTHHMM)
* ISO 8601 UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ)
* ISO 8601 pre-UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ+HHMM)
* ISO 8601 pre-UTC datetime without dashes and colons and no timezone minutes (YYYYMMDDTHHMMSSZ+HH)
* ISO 8601 post-UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ-HHMM)
* ISO 8601 post-UTC datetime without dashes and colons and no timezone minutes (YYYYMMDDTHHMMSSZ-HH)

===Markup Possibilities===
==== Valid HTML4 ====
* abbr-design-pattern (as currently recommended)
* OBJECT with param value.
* OBJECT with in-page data attribute.
* SPAN element with title attribute.
* DFN element with title attribute.
* Nested SPAN element.
* Nested ABBR element.
* Nested DFN element (See: [http://microformats.org/discuss/mail/microformats-new/2007-May/000335.html mailing list thread], verify at [http://alistapart.com/articles/hattrick ALA article]).
* Empty INS element with DATETIME attr (<code><span class="dtstart">13th<ins datetime="20070713"></ins></span></code>)
* Rarely used event handler. e.g. (<code><span class="dtstart" onchange="void(20070713)">13th</span></code>)
* Element with name attr (<code><a class="dtstart" name="iso8601:20070713">13th</a></code>)

==== Invalid HTML4 ====
Markup possibilities that are invalid in HTML4/XHTML1 are noted here to be clear that they were considered and rejected. Since microformats build on [[posh]], any technique that is invalid semantic (X)HTML is unacceptable for a microformats solution. There is no need to bother testing these.
* SPAN with RDF dc:date attribute.
* SPAN with RDF geo:position attribute.

===Screenreader Language Pronunciations===
* English
* Spanish (need volunteer native Spanish speaker screen reader user)
* ?

===Verbosity settings===

* Punctuation, speak none.
* Punctuation, speak some.
* Punctuation, speak all.
* Title attributes, speak none.
* Title attributes, speak some (abbr and acronym).
* Title attributes, speak all.

===Screenreaders===
* Freedom Scientific JAWS (multiple versions TBD)
* GW Micro Window Eyes (multiple versions TBD)
* Apple Voiceover (multiple versions TBD)
* Dolphin HAL (multiple versions TBD)

== Results ==

To be determined.

== See Also ==
* [[accessibility]]
* [[assistive-technology]]

assistive-technology-abbr-results

2007-05-10T20:29:54Z

JamesCraig: /* Markup Possibilities */ Adding *[name] as markup possibility

<h1>assistive technology abbr results</h1>
This page is for document the precise results of using [[assistive-technology]] with real world examples in the wild of the abbr design pattern, as nearly always used by [[hcalendar|hCalendar]] (e.g. dtstart, dtend), often by [[hreview|hReview]] (e.g. dtreviewed, rating) and sometimes by [[hcard|hCard]] (e.g. bday, type subproperty).

__TOC__

Each [[assistive-technology]] listed here MUST link to a precise description of the tool/service on the [[assistive-technology]] page, including version number, when published, etc.

Each test result listed for each assistive technology MUST link to the real world example that was tested.

== Test Cases ==
The [http://www.webstandards.org/action/atf/ WasP Accessibility Task Force] is working on a set of extended test cases that will cover the following data formats and markup formats. Please add to the list so we can create a comprehensive result set.

===Data Formats===
Please provide hyperlinks to examples in the wild for each case that is to be tested. Test cases with example in the wild URLs merit more testing than those without. However, the purpose of these test cases is to find the best solution, whether or not it is currently being used.
* ISO 8601 date with punctuation (YYYY-MM-DD)
* ISO 8601 datetime with punctuation (YYYY-MM-DDTHH:MM:SS)
* ISO 8601 datetime with punctuation and no seconds (YYYY-MM-DDTHH:MM)
* ISO 8601 UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SSZ)
* ISO 8601 pre-UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SS+HH:MM)
* ISO 8601 pre-UTC datetime with punctuation and no timezone minutes (YYYY-MM-DDTHH:MM:SS+HH)
* ISO 8601 post-UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SS-HH:MM)
* ISO 8601 post-UTC datetime with punctuation and no timezone minutes (YYYY-MM-DDTHH:MM:SS-HH)
* ISO 8601 datetime with punctuation but w/o timezone punctuation. ''The hypothesis is that something like "eleven o'clock plus oh seven hundred" may be more understandable than "eleven o'clock plus seven o'clock" (similarly for the hyphen, read as "dash").''
** pre-UTC (YYYY-MM-DDTHH:MM:SS+HHMM)
** post-UTC (YYYY-MM-DDTHH:MM:SS-HHMM)
* GEO Latitude/Longitude coordinates.
* ISO 8601 durations
* ISO 8601 recurrences

=== Rejected Data formats ===
Dates without punctuation as they have proved unusable. Proof is premise for [[http://www.webstandards.org/2007/04/27/haccessibility/ hAccessibility]] article on the Web Standards Project Buzz blog. Window Eyes and JAWS read un-punctuated dates as single number. [[http://www.webstandards.org/files/atf_microformats/jaws.mp3 JAWS 8 on IE7 citation (MP3 Audio)]] of "twenty million seventy-thousand three-hundred twelve" is reason enough for rejection.
* ISO 8601 date without dashes (YYYYMMDD)
* ISO 8601 datetime without dashes and colons (YYYYMMDDTHHMMSS)
* ISO 8601 datetime without dashes and colons and no seconds (YYYYMMDDTHHMM)
* ISO 8601 UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ)
* ISO 8601 pre-UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ+HHMM)
* ISO 8601 pre-UTC datetime without dashes and colons and no timezone minutes (YYYYMMDDTHHMMSSZ+HH)
* ISO 8601 post-UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ-HHMM)
* ISO 8601 post-UTC datetime without dashes and colons and no timezone minutes (YYYYMMDDTHHMMSSZ-HH)

===Markup Possibilities===
==== Valid HTML4 ====
* abbr-design-pattern (as currently recommended)
* OBJECT with param value.
* OBJECT with in-page data attribute.
* SPAN element with title attribute.
* DFN element with title attribute.
* Nested SPAN element.
* Nested ABBR element.
* Nested DFN element (See: [http://microformats.org/discuss/mail/microformats-new/2007-May/000335.html mailing list thread], verify at [http://alistapart.com/articles/hattrick ALA article]).
* Empty INS element with DATETIME attr (<code><span class="dtstart">13th<ins datetime="20070713"></ins></span></code>)
* Rarely used event handler. e.g. (<code><span class="dtstart" onchange="void(20070713)">13th</span></code>)
* Element with name attr (<code><span class="dtstart" name="iso8601:20070713">13th</span></code>)

==== Invalid HTML4 ====
Markup possibilities that are invalid in HTML4/XHTML1 are noted here to be clear that they were considered and rejected. Since microformats build on [[posh]], any technique that is invalid semantic (X)HTML is unacceptable for a microformats solution. There is no need to bother testing these.
* SPAN with RDF dc:date attribute.
* SPAN with RDF geo:position attribute.

===Screenreader Language Pronunciations===
* English
* Spanish (need volunteer native Spanish speaker screen reader user)
* ?

===Verbosity settings===

* Punctuation, speak none.
* Punctuation, speak some.
* Punctuation, speak all.
* Title attributes, speak none.
* Title attributes, speak some (abbr and acronym).
* Title attributes, speak all.

===Screenreaders===
* Freedom Scientific JAWS (multiple versions TBD)
* GW Micro Window Eyes (multiple versions TBD)
* Apple Voiceover (multiple versions TBD)
* Dolphin HAL (multiple versions TBD)

== Results ==

To be determined.

== See Also ==
* [[accessibility]]
* [[assistive-technology]]

accessibility

2007-05-08T19:05:07Z

JamesCraig: /* Disadvantages */ reverting content already on (or linked from) accessibility-issues page

<h1>Accessibility</h1>

This page documents microformats and accessibility in general, in particular advantages that adopting microformats provide for accessibility, and for documenting techniques for making microformats more accessible.

We should all strive to make our published microformats, parser implementations, and this wiki, accessible to all users, regardless of their physical abilities and needs, within the limits of the time and resources of the microformats community. Readers are advised to follow the [http://www.w3.org/TR/WCAG10/ W3C's Web Content Accessibility Guidelines 1.0], to at least level 2. Further advice is available on the [http://www.accessifyforum.com/ Accessify Forums].

__TOC__

==Advantages==
Some microformats have potential accessibility advantages.

===hCard===
*<code>tel</code> in [[hcard|hCard]]: use <code>style="speak-numeral:digits"</code>, so that telephone numbers are read by aural browsers as, for example, "five-five-five one-two-three-four" and not "five-hundred and fifty-five, one-thousand, two-hundred and thirty-two". ''Note: This is not an advantage to Microformats. It is a CSS best practice and can be used with or without hCard. This should probably be moved to a [[css-best-practices|CSS Best Practices]] page. - JamesCraig''

==Disadvantages==
Some microformats have potential accessibility disadvantages.

===abbr-design-pattern===
*As mentioned on external sites (see:[[accessibility-issues]]) and on the microformats-discuss list, the abbr-design-pattern (used in [[hcard|hCard]], [[hcalendar|hCalendar]], [[geo|GEO]] and others) is in violation of WCAG1 and WCAG2, and has potentially harmful accessibility side-effects of reading machine data to screen reader users rendering human content inaccessible.

===anchor-include-pattern===
*As mentioned on [[accessibility-issues]], the anchor-include-pattern is in violation of WCAG1 and WCAG2, and has potentially harmful accessibility side effects due to the missing link text.

==External testimonials==
* [http://lists.w3.org/Archives/Public/w3c-wai-ig/2006JulSep/subject.html#msg133 hCard and hCalendar Formats] - 2006-08-03 in w3c-wai-ig. e.g. <blockquote><p>I think Microformats.org is doing rather well on it's own, and it isn't particularly something that the W3C would or should get involved in until it's settled down. (And then it would just be a ratification kind of thing.)</p><p>...</p><p>In fact, it is likely to be good for accessibility, as the tools for consuming microformats often require valid code.</p></blockquote>

==See also==
*[[accessibility-issues]] - note external criticisms on the accesibility issues page
*[[internationalization]]
*[[assistive-technology]]
*[[assistive-technology-abbr-results]]

assistive-technology-abbr-results

2007-05-07T21:15:50Z

JamesCraig: /* Markup Possibilities */ links

<h1>assistive technology abbr results</h1>
This page is for document the precise results of using [[assistive-technology]] with real world examples in the wild of the abbr design pattern, as nearly always used by [[hcalendar|hCalendar]] (e.g. dtstart, dtend), often by [[hreview|hReview]] (e.g. dtreviewed, rating) and sometimes by [[hcard|hCard]] (e.g. bday, type subproperty).

__TOC__

Each [[assistive-technology]] listed here MUST link to a precise description of the tool/service on the [[assistive-technology]] page, including version number, when published, etc.

Each test result listed for each assistive technology MUST link to the real world example that was tested.

== Test Cases ==
The [http://www.webstandards.org/action/atf/ WasP Accessibility Task Force] is working on a set of extended test cases that will cover the following data formats and markup formats. Please add to the list so we can create a comprehensive result set.

===Data Formats===
Please provide hyperlinks to examples in the wild for each case that is to be tested. Test cases with example in the wild URLs merit more testing than those without. However, the purpose of these test cases is to find the best solution, whether or not it is currently being used.
* ISO 8601 date with punctuation (YYYY-MM-DD)
* ISO 8601 datetime with punctuation (YYYY-MM-DDTHH:MM:SS)
* ISO 8601 datetime with punctuation and no seconds (YYYY-MM-DDTHH:MM)
* ISO 8601 UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SSZ)
* ISO 8601 pre-UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SS+HH:MM)
* ISO 8601 pre-UTC datetime with punctuation and no timezone minutes (YYYY-MM-DDTHH:MM:SS+HH)
* ISO 8601 post-UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SS-HH:MM)
* ISO 8601 post-UTC datetime with punctuation and no timezone minutes (YYYY-MM-DDTHH:MM:SS-HH)
* ISO 8601 datetime with punctuation but w/o timezone punctuation. ''The hypothesis is that something like "eleven o'clock plus oh seven hundred" may be more understandable than "eleven o'clock plus seven o'clock" (similarly for the hyphen, read as "dash").''
** pre-UTC (YYYY-MM-DDTHH:MM:SS+HHMM)
** post-UTC (YYYY-MM-DDTHH:MM:SS-HHMM)
* GEO Latitude/Longitude coordinates.
* ISO 8601 durations
* ISO 8601 recurrences

=== Rejected Data formats ===
Dates without punctuation as they have proved unusable. Proof is premise for [[http://www.webstandards.org/2007/04/27/haccessibility/ hAccessibility]] article on the Web Standards Project Buzz blog. Window Eyes and JAWS read un-punctuated dates as single number. [[http://www.webstandards.org/files/atf_microformats/jaws.mp3 JAWS 8 on IE7 citation (MP3 Audio)]] of "twenty million seventy-thousand three-hundred twelve" is reason enough for rejection.
* ISO 8601 date without dashes (YYYYMMDD)
* ISO 8601 datetime without dashes and colons (YYYYMMDDTHHMMSS)
* ISO 8601 datetime without dashes and colons and no seconds (YYYYMMDDTHHMM)
* ISO 8601 UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ)
* ISO 8601 pre-UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ+HHMM)
* ISO 8601 pre-UTC datetime without dashes and colons and no timezone minutes (YYYYMMDDTHHMMSSZ+HH)
* ISO 8601 post-UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ-HHMM)
* ISO 8601 post-UTC datetime without dashes and colons and no timezone minutes (YYYYMMDDTHHMMSSZ-HH)

===Markup Possibilities===
==== Valid HTML4 ====
* abbr-design-pattern (as currently recommended)
* OBJECT with param value.
* OBJECT with in-page data attribute.
* SPAN element with title attribute.
* DFN element with title attribute.
* Nested SPAN element.
* Nested ABBR element.
* Nested DFN element (See: [http://microformats.org/discuss/mail/microformats-new/2007-May/000335.html mailing list thread], verify at [http://alistapart.com/articles/hattrick ALA article]).
* Empty INS element with DATETIME attr (<code><span class="dtstart">13th<ins datetime="20070713"></ins></span></code>)
* Rarely used event handler. e.g. (<code><span class="dtstart" onchange="void(20070713)">13th</span></code>)

==== Invalid HTML4 ====
Markup possibilities that are invalid in HTML4/XHTML1 are noted here to be clear that they were considered and rejected. Since microformats build on [[posh]], any technique that is invalid semantic (X)HTML is unacceptable for a microformats solution. There is no need to bother testing these.
* SPAN with RDF dc:date attribute.
* SPAN with RDF geo:position attribute.

===Screenreader Language Pronunciations===
* English
* Spanish (need volunteer native Spanish speaker screen reader user)
* ?

===Verbosity settings===

* Punctuation, speak none.
* Punctuation, speak some.
* Punctuation, speak all.
* Title attributes, speak none.
* Title attributes, speak some (abbr and acronym).
* Title attributes, speak all.

===Screenreaders===
* Freedom Scientific JAWS (multiple versions TBD)
* GW Micro Window Eyes (multiple versions TBD)
* Apple Voiceover (multiple versions TBD)
* Dolphin HAL (multiple versions TBD)

== Results ==

To be determined.

== See Also ==
* [[accessibility]]
* [[assistive-technology]]

assistive-technology-abbr-results

2007-05-07T21:10:53Z

JamesCraig: /* Markup Possibilities */ added DFN, plus formatting

<h1>assistive technology abbr results</h1>
This page is for document the precise results of using [[assistive-technology]] with real world examples in the wild of the abbr design pattern, as nearly always used by [[hcalendar|hCalendar]] (e.g. dtstart, dtend), often by [[hreview|hReview]] (e.g. dtreviewed, rating) and sometimes by [[hcard|hCard]] (e.g. bday, type subproperty).

__TOC__

Each [[assistive-technology]] listed here MUST link to a precise description of the tool/service on the [[assistive-technology]] page, including version number, when published, etc.

Each test result listed for each assistive technology MUST link to the real world example that was tested.

== Test Cases ==
The [http://www.webstandards.org/action/atf/ WasP Accessibility Task Force] is working on a set of extended test cases that will cover the following data formats and markup formats. Please add to the list so we can create a comprehensive result set.

===Data Formats===
Please provide hyperlinks to examples in the wild for each case that is to be tested. Test cases with example in the wild URLs merit more testing than those without. However, the purpose of these test cases is to find the best solution, whether or not it is currently being used.
* ISO 8601 date with punctuation (YYYY-MM-DD)
* ISO 8601 datetime with punctuation (YYYY-MM-DDTHH:MM:SS)
* ISO 8601 datetime with punctuation and no seconds (YYYY-MM-DDTHH:MM)
* ISO 8601 UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SSZ)
* ISO 8601 pre-UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SS+HH:MM)
* ISO 8601 pre-UTC datetime with punctuation and no timezone minutes (YYYY-MM-DDTHH:MM:SS+HH)
* ISO 8601 post-UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SS-HH:MM)
* ISO 8601 post-UTC datetime with punctuation and no timezone minutes (YYYY-MM-DDTHH:MM:SS-HH)
* ISO 8601 datetime with punctuation but w/o timezone punctuation. ''The hypothesis is that something like "eleven o'clock plus oh seven hundred" may be more understandable than "eleven o'clock plus seven o'clock" (similarly for the hyphen, read as "dash").''
** pre-UTC (YYYY-MM-DDTHH:MM:SS+HHMM)
** post-UTC (YYYY-MM-DDTHH:MM:SS-HHMM)
* GEO Latitude/Longitude coordinates.
* ISO 8601 durations
* ISO 8601 recurrences

=== Rejected Data formats ===
Dates without punctuation as they have proved unusable. Proof is premise for [[http://www.webstandards.org/2007/04/27/haccessibility/ hAccessibility]] article on the Web Standards Project Buzz blog. Window Eyes and JAWS read un-punctuated dates as single number. [[http://www.webstandards.org/files/atf_microformats/jaws.mp3 JAWS 8 on IE7 citation (MP3 Audio)]] of "twenty million seventy-thousand three-hundred twelve" is reason enough for rejection.
* ISO 8601 date without dashes (YYYYMMDD)
* ISO 8601 datetime without dashes and colons (YYYYMMDDTHHMMSS)
* ISO 8601 datetime without dashes and colons and no seconds (YYYYMMDDTHHMM)
* ISO 8601 UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ)
* ISO 8601 pre-UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ+HHMM)
* ISO 8601 pre-UTC datetime without dashes and colons and no timezone minutes (YYYYMMDDTHHMMSSZ+HH)
* ISO 8601 post-UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ-HHMM)
* ISO 8601 post-UTC datetime without dashes and colons and no timezone minutes (YYYYMMDDTHHMMSSZ-HH)

===Markup Possibilities===
==== Valid HTML4 ====
* abbr-design-pattern (as currently recommended)
* OBJECT with param value.
* OBJECT with in-page data attribute.
* SPAN element with title attribute.
* DFN element with title attribute.
* Nested SPAN element.
* Nested ABBR element.
* Nested DFN element.
* Empty INS element with DATETIME attr (<code><span class="dtstart">13th<ins datetime="20070713"></ins></span></code>)
* Rarely used event handler. e.g. (<code><span class="dtstart" onchange="void(20070713)">13th</span></code>)

==== Invalid HTML4 ====
Markup possibilities that are invalid in HTML4/XHTML1 are noted here to be clear that they were considered and rejected. Since microformats build on [[posh]], any technique that is invalid semantic (X)HTML is unacceptable for a microformats solution. There is no need to bother testing these.
* SPAN with RDF dc:date attribute.
* SPAN with RDF geo:position attribute.

===Screenreader Language Pronunciations===
* English
* Spanish (need volunteer native Spanish speaker screen reader user)
* ?

===Verbosity settings===

* Punctuation, speak none.
* Punctuation, speak some.
* Punctuation, speak all.
* Title attributes, speak none.
* Title attributes, speak some (abbr and acronym).
* Title attributes, speak all.

===Screenreaders===
* Freedom Scientific JAWS (multiple versions TBD)
* GW Micro Window Eyes (multiple versions TBD)
* Apple Voiceover (multiple versions TBD)
* Dolphin HAL (multiple versions TBD)

== Results ==

To be determined.

== See Also ==
* [[accessibility]]
* [[assistive-technology]]

semantic-xhtml-design-principles

2007-05-07T18:09:34Z

JamesCraig: /* Semantic XHTML Design Principles */ adding links

=Semantic XHTML Design Principles=

__TOC__

XHTML is built on XML, and thus XHTML-based formats can be used not only for convenient display presentation, but also for general-purpose data exchange. In many ways, XHTML-based formats exemplify the best of both HTML and XML worlds. However, when building XHTML-based formats, it helps to have a guiding set of principles.

# Reuse the schema (names, objects, properties, values, types, hierarchies, constraints) as much as possible from pre-existing, established, well-supported standards by reference. Avoid restating constraints expressed in the source standard. Informative mentions are ok.
## For types with multiple components, use nested elements with class names equivalent to the names of the components.
## Plural components are made singular, and thus multiple nested elements are used to represent multiple text values that are comma-delimited.
# Use the most accurately precise semantic XHTML building block for each object etc.
# Otherwise use a generic structural element (e.g. <code><span></code> or <code><div></code>), or the appropriate contextual element (e.g. an <code><li></code> inside a <code><ul></code> or <code><ol></code>).
# Use class names based on names from the original schema, unless the [[semantic-xhtml|semantic XHTML]] building block precisely represents that part of the original schema. If names in the source schema are case-insensitive, then use an all lowercase equivalent. Components names implicit in prose (rather than explicit in the defined schema) should also use lowercase equivalents for ease of use. Spaces in component names become dash '-' characters.
# Finally, if the format of the data according to the original schema is too long and/or not human-friendly, use <code><abbr></code> instead of a generic structural element, and place the literal data into the 'title' attribute (where abbr expansions go), and the more brief and human-readable equivalent into the element itself. Further informative explanation of this use of <code><abbr></code>: [[abbr-design-pattern]], [http://tantek.com/log/2005/01.html#d26t0100 Human vs. ISO8601 dates problem solved], and [http://www.webstandards.org/2007/04/27/haccessibility/ hAccessibility] aka "abbr-design-pattern considered harmful."

==Semantic XHTML and Microformats==
(from Tantek Çelik on the [http://article.gmane.org/gmane.comp.web.microformats.general/6014 microformats-discuss mailing list])

Note that microformats use semantic XHTML, but not all use of semantic
XHTML are microformats.

Web designers and authors are using semantic XHTML everyday without using
microformats, and that's perfectly fine. They are not trying to create
standards and interoperably/automatically exchange data with each other.
They are simply expressing the semantics of their documents.

Whereas microformats follow a specific process and are intended to provide
a way for publishers worldwide to easily interoperably exchange simple
bits of data.

http://microformats.org/wiki/process

This distinction between "semantic XHTML" and "microformats" is very
important to understand and is often confused - I've even seen W3C staff
themselves call microformats "just using good class names", which is
incorrect. (Using good class names is simply one of the practices of
semantic XHTML).

assistive-technology-abbr-results

2007-05-07T17:59:20Z

JamesCraig: /* Test Cases */ durations/recurrences

<h1>assistive technology abbr results</h1>
This page is for document the precise results of using [[assistive-technology]] with real world examples in the wild of the abbr design pattern, as nearly always used by [[hcalendar|hCalendar]] (e.g. dtstart, dtend), often by [[hreview|hReview]] (e.g. dtreviewed, rating) and sometimes by [[hcard|hCard]] (e.g. bday, type subproperty).

__TOC__

Each [[assistive-technology]] listed here MUST link to a precise description of the tool/service on the [[assistive-technology]] page, including version number, when published, etc.

Each test result listed for each assistive technology MUST link to the real world example that was tested.

== Test Cases ==
The [http://www.webstandards.org/action/atf/ WasP Accessibility Task Force] is working on a set of extended test cases that will cover the following data formats and markup formats. Please add to the list so we can create a comprehensive result set.

===Data Formats===
Please provide hyperlinks to examples in the wild for each case that is to be tested. Test cases with example in the wild URLs merit more testing than those without. However, the purpose of these test cases is to find the best solution, whether or not it is currently being used.
* ISO 8601 date with punctuation (YYYY-MM-DD)
* ISO 8601 datetime with punctuation (YYYY-MM-DDTHH:MM:SS)
* ISO 8601 datetime with punctuation and no seconds (YYYY-MM-DDTHH:MM)
* ISO 8601 UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SSZ)
* ISO 8601 pre-UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SS+HH:MM)
* ISO 8601 pre-UTC datetime with punctuation and no timezone minutes (YYYY-MM-DDTHH:MM:SS+HH)
* ISO 8601 post-UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SS-HH:MM)
* ISO 8601 post-UTC datetime with punctuation and no timezone minutes (YYYY-MM-DDTHH:MM:SS-HH)
* ISO 8601 datetime with punctuation but w/o timezone punctuation. ''The hypothesis is that something like "eleven o'clock plus oh seven hundred" may be more understandable than "eleven o'clock plus seven o'clock" (similarly for the hyphen, read as "dash").''
** pre-UTC (YYYY-MM-DDTHH:MM:SS+HHMM)
** post-UTC (YYYY-MM-DDTHH:MM:SS-HHMM)
* GEO Latitude/Longitude coordinates.
* ISO 8601 durations
* ISO 8601 recurrences

=== Rejected Data formats ===
Dates without punctuation as they have proved unusable. Proof is premise for [[http://www.webstandards.org/2007/04/27/haccessibility/ hAccessibility]] article on the Web Standards Project Buzz blog. Window Eyes and JAWS read un-punctuated dates as single number. [[http://www.webstandards.org/files/atf_microformats/jaws.mp3 JAWS 8 on IE7 citation (MP3 Audio)]] of "twenty million seventy-thousand three-hundred twelve" is reason enough for rejection.
* ISO 8601 date without dashes (YYYYMMDD)
* ISO 8601 datetime without dashes and colons (YYYYMMDDTHHMMSS)
* ISO 8601 datetime without dashes and colons and no seconds (YYYYMMDDTHHMM)
* ISO 8601 UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ)
* ISO 8601 pre-UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ+HHMM)
* ISO 8601 pre-UTC datetime without dashes and colons and no timezone minutes (YYYYMMDDTHHMMSSZ+HH)
* ISO 8601 post-UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ-HHMM)
* ISO 8601 post-UTC datetime without dashes and colons and no timezone minutes (YYYYMMDDTHHMMSSZ-HH)

===Markup Possibilities===
==== Valid HTML4 ====
* abbr-design-pattern (as currently recommended)
* Object with param value.
* Object with in-page data attribute.
* Span with title property.
* Nested spans with child title set to null.
* Nested abbr with child title set to null.
* Empty ins element with datetime attr (<code><span class="dtstart">13th<ins datetime="20070713"></ins></span></code>)
* Rarely used event handler. e.g. (<code><span class="dtstart" onchange="void(20070713)">13th</span></code>)

==== Invalid HTML4 ====
Markup possibilities that are invalid in HTML4/XHTML1 are noted here to be clear that they were considered and rejected. Since microformats build on [[posh]], any technique that is invalid semantic (X)HTML is unacceptable for a microformats solution. There is no need to bother testing these.
* Span with RDF dc:date attribute.
* Span with RDF geo:position attribute.

===Screenreader Language Pronunciations===
* English
* Spanish (need volunteer native Spanish speaker screen reader user)
* ?

===Verbosity settings===

* Punctuation, speak none.
* Punctuation, speak some.
* Punctuation, speak all.
* Title attributes, speak none.
* Title attributes, speak some (abbr and acronym).
* Title attributes, speak all.

===Screenreaders===
* Freedom Scientific JAWS (multiple versions TBD)
* GW Micro Window Eyes (multiple versions TBD)
* Apple Voiceover (multiple versions TBD)
* Dolphin HAL (multiple versions TBD)

== Results ==

To be determined.

== See Also ==
* [[accessibility]]
* [[assistive-technology]]

accessibility

2007-05-07T17:56:55Z

JamesCraig: /* See also */ added assistive-technology-abbr-results

<h1>Accessibility</h1>

This page documents microformats and accessibility in general, in particular advantages that adopting microformats provide for accessibility, and for documenting techniques for making microformats more accessible.

We should all strive to make our published microformats, parser implementations, and this wiki, accessible to all users, regardless of their physical abilities and needs, within the limits of the time and resources of the microformats community. Readers are advised to follow the [http://www.w3.org/TR/WCAG10/ W3C's Web Content Accessibility Guidelines 1.0], to at least level 2. Further advice is available on the [http://www.accessifyforum.com/ Accessify Forums].

__TOC__

==Advantages==
Some microformats have potential accessibility advantages.

===hCard===
*<code>tel</code> in [[hcard|hCard]]: use <code>style="speak-numeral:digits"</code>, so that telephone numbers are read by aural browsers as, for example, "five-five-five one-two-three-four" and not "five-hundred and fifty-five, one-thousand, two-hundred and thirty-two". ''Note: This is not an advantage to Microformats. It is a CSS best practice and can be used with or without hCard. This should probably be moved to a [[css-best-practices|CSS Best Practices]] page. - JamesCraig''

==Disadvantages==
Some microformats have potential accessibility disadvantages.

===abbr-design-pattern===
*As mentioned on external sites (see:[[accessibility-issues]]) and on the microformats-discuss list, the abbr-design-pattern (used in [[hcard|hCard]], [[hcalendar|hCalendar]], [[geo|GEO]] and others) is in violation of WCAG1 and WCAG2, and has potentially harmful accessibility side-effects of reading machine data to screen reader users rendering human content inaccessible.

===anchor-include-pattern===
*As mentioned on [[accessibility-issues]], the anchor-include-pattern is in violation of WCAG1 and WCAG2, and has potentially harmful accessibility side effects due to the missing link text.

==External testimonials==
* [http://lists.w3.org/Archives/Public/w3c-wai-ig/2006JulSep/subject.html#msg133 hCard and hCalendar Formats] - 2006-08-03 in w3c-wai-ig. e.g. <blockquote><p>I think Microformats.org is doing rather well on it's own, and it isn't particularly something that the W3C would or should get involved in until it's settled down. (And then it would just be a ratification kind of thing.)</p><p>...</p><p>In fact, it is likely to be good for accessibility, as the tools for consuming microformats often require valid code.</p></blockquote>

==See also==
*[[accessibility-issues]] - note external criticisms on the accesibility issues page
*[[internationalization]]
*[[assistive-technology]]
*[[assistive-technology-abbr-results]]

advocacy

2007-05-07T17:38:43Z

JamesCraig: changed XXX to XYZ ;-)

<h1> Advocacy </h1>

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

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

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

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

== Adding Microformats to Existing Sites ==

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

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

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

=== hCard ===
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')
* Alexa.com has online profiles for domains with contact information. Would be great if they could add hCard to those. 2007-04-18 [[User:Tantek]] requested of [[User:BenWest]] e.g.:
** http://www.alexa.com/data/details?url=alexa.com/
** http://www.alexa.com/data/details?url=w3.org/
* [http://sunlightlabs.com/api/ SunlightLabs API] provides profiles for US Congresspeople. Their [http://sunlightlabs.com/api/masterref/megatable.php megatable] could easily be marked up with hCard, and their APIs could return hCards and hCard fields.
** [[User:Tantek|Tantek]] 12:30, 20 Apr 2007 (PDT) contacted them and requested that they add hCard to megatable, consider a GethCard API method, and potentially a GethResume API method for each person.
** {{SuccessMarker}} [[User:CarlAnderson|CarlAnderson]] 26 Apr 2007: http://sunlightlabs.com/api does now have a people.getHCard.php API method to get an hCard for every member of congress. See the documentation at http://sunlightlabs.com/api/people.getHCard.php. An example call: http://api.sunlightlabs.com/people.getHCard.php?id=fakeopenID1
** {{SuccessMarker}} [[User:CarlAnderson|CarlAnderson]] 30 Apr 2007: I created a page of hCards for every member of congress: http://sunlightlabs.com/api/hcards/index.php

==== 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] [[User:AndyMabbett|Andy Mabbett]] 13:10, 28 Jan 2007 (PST)
* See also [[persondata|discussion of Wikipedia's Persondata]], which aligns very closely with hCard, but has additional date and place of birth & death fields. [[User:AndyMabbett|Andy Mabbett]] 13:23, 28 Mar 2007 (PDT)

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

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

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

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

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

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

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

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

====Other hCard====
* [http://www.imdb.com/ Internet Movie Database] (IMDb) for people (real, not characters), e.g. [http://www.imdb.com/name/nm0000007/ Humphrey Bogart]. [[User:AndyMabbett|Andy Mabbett]] 02:49, 13 Nov 2006 (PST)
**Can't find contact info! [[User:AndyMabbett|Andy Mabbett]]
*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.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://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:
*[http://meta.wikimedia.org/wiki/WikiGPS WikiGPS]
**Under development; notified of Geo microformat 2007-03-23
*Collections of waypoints
**See also [[geo-waypoint-examples]]
*Upcoming
**Some events, e.g. [http://upcoming.org/event/128155/ Multipack February 2007] are tagged thus: <code>geo:lat=52.4784</code>, <code>geo:lon=-1.9096</code>. This could be rendered as a geo microformat. [[User:AndyMabbett|Andy Mabbett]]
**Requested on (now defunct) Upcoming wiki 2007-01-14
**[http://suggestions.yahoo.com/detail/?prop=upcoming&fid=14362 Repeated on new suggestion board]. 2007-03-30. '''Please vote for this suggestion''' [[User:AndyMabbett|Andy Mabbett]]
*[http://www.census.gov/cgi-bin/gazetteer U.S. Gazetteer] e.g. [http://www.census.gov/cgi-bin/gazetteer?city=Birmingham&state=&zip=]
*[http://www.world-gazetteer.com/ World Gazetteer] e.g. [http://www.world-gazetteer.com/wg.php?x=&men=gpro&lng=en&dat=32&geo=-81&srt=npan&col=aohdq&pt=c&va=&geo=512945809]
**Requested by e-mail, 2007-01-20 [[User:AndyMabbett|Andy Mabbett]]
*[http://www.genuki.org.uk/cgi-bin/places GENUKI Gazetteer] (UK & Ireland) e.g. [http://www.genuki.org.uk/cgi-bin/maplink?CCC=STS,GR=SP040940,PLACE=Great%20Barr]
**Requested via feedback form, 2007-01-20 [[User:AndyMabbett|Andy Mabbett]]
*[http://www.confluence.org/ The Degree Confluence Project]
**Requested by e-mail, 2007-03-26 [[User:AndyMabbett|Andy Mabbett]]
*[http://www.wikimapia.org/ WikiMapia]
**Requested by e-mail, 2007-03-27 [[User:AndyMabbett|Andy Mabbett]]
**Replied to say they're looking into it. 2007-03-29
*[http://www.jeeep.com/details/coord/translate.cgi?datum=83&lat=52.57265&lon=-1.911433&detail=1 Jeeep.com]
**Requested by e-mail, 2007-03-27 [[User:AndyMabbett|Andy Mabbett]]
**Advertised address bouncing, 2007-03-27
*[http://www.flagr.com/ Flagr]
**Using, but not (yet) displaying, coordinates
**Requested by e-mail, 2007-03-30; also suggested they display their coordinates, and mark them up as tags [[User:AndyMabbett|Andy Mabbett]]
**Replied same day to say they will "talk it over internally"
* Various [http://en.wikipedia.org/wiki/Geocaching#Geocache_listing_sites Geocache listing sites]

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

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

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

===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]]
*W3C
**{{SuccessMarker}} '''W3C webmaster''' [http://www.w3.org/People/Jean-Gui/ Jean-Guilhem Rouel] now has an hCard. [[User:AndyMabbett|Andy Mabbett]] 15:41, 4 Apr 2007 (PDT)
*{{SuccessMarker}}Wikipedia-EN - starting to roll-out
**UK Railway station template, e.g. [http://en.wikipedia.org/wiki/Birmingham_New_Street Birmingham New Street station] (includes Geo)

=== hCalendar Successes===

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

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

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

==Rejections==

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

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

== Comparisons With Alternative Approaches ==

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

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

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

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

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

advocacy

2007-05-07T17:37:13Z

JamesCraig: /* Comparisons With Alternative Approaches */ after some discussion with Brian, removed decontextualized opinions and instead just linked to the mailing list thread.

<h1> Advocacy </h1>

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

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

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

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

=== hCard ===
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')
* Alexa.com has online profiles for domains with contact information. Would be great if they could add hCard to those. 2007-04-18 [[User:Tantek]] requested of [[User:BenWest]] e.g.:
** http://www.alexa.com/data/details?url=alexa.com/
** http://www.alexa.com/data/details?url=w3.org/
* [http://sunlightlabs.com/api/ SunlightLabs API] provides profiles for US Congresspeople. Their [http://sunlightlabs.com/api/masterref/megatable.php megatable] could easily be marked up with hCard, and their APIs could return hCards and hCard fields.
** [[User:Tantek|Tantek]] 12:30, 20 Apr 2007 (PDT) contacted them and requested that they add hCard to megatable, consider a GethCard API method, and potentially a GethResume API method for each person.
** {{SuccessMarker}} [[User:CarlAnderson|CarlAnderson]] 26 Apr 2007: http://sunlightlabs.com/api does now have a people.getHCard.php API method to get an hCard for every member of congress. See the documentation at http://sunlightlabs.com/api/people.getHCard.php. An example call: http://api.sunlightlabs.com/people.getHCard.php?id=fakeopenID1
** {{SuccessMarker}} [[User:CarlAnderson|CarlAnderson]] 30 Apr 2007: I created a page of hCards for every member of congress: http://sunlightlabs.com/api/hcards/index.php

==== 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] [[User:AndyMabbett|Andy Mabbett]] 13:10, 28 Jan 2007 (PST)
* See also [[persondata|discussion of Wikipedia's Persondata]], which aligns very closely with hCard, but has additional date and place of birth & death fields. [[User:AndyMabbett|Andy Mabbett]] 13:23, 28 Mar 2007 (PDT)

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

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

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

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

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

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

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

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

====Other hCard====
* [http://www.imdb.com/ Internet Movie Database] (IMDb) for people (real, not characters), e.g. [http://www.imdb.com/name/nm0000007/ Humphrey Bogart]. [[User:AndyMabbett|Andy Mabbett]] 02:49, 13 Nov 2006 (PST)
**Can't find contact info! [[User:AndyMabbett|Andy Mabbett]]
*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.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://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:
*[http://meta.wikimedia.org/wiki/WikiGPS WikiGPS]
**Under development; notified of Geo microformat 2007-03-23
*Collections of waypoints
**See also [[geo-waypoint-examples]]
*Upcoming
**Some events, e.g. [http://upcoming.org/event/128155/ Multipack February 2007] are tagged thus: <code>geo:lat=52.4784</code>, <code>geo:lon=-1.9096</code>. This could be rendered as a geo microformat. [[User:AndyMabbett|Andy Mabbett]]
**Requested on (now defunct) Upcoming wiki 2007-01-14
**[http://suggestions.yahoo.com/detail/?prop=upcoming&fid=14362 Repeated on new suggestion board]. 2007-03-30. '''Please vote for this suggestion''' [[User:AndyMabbett|Andy Mabbett]]
*[http://www.census.gov/cgi-bin/gazetteer U.S. Gazetteer] e.g. [http://www.census.gov/cgi-bin/gazetteer?city=Birmingham&state=&zip=]
*[http://www.world-gazetteer.com/ World Gazetteer] e.g. [http://www.world-gazetteer.com/wg.php?x=&men=gpro&lng=en&dat=32&geo=-81&srt=npan&col=aohdq&pt=c&va=&geo=512945809]
**Requested by e-mail, 2007-01-20 [[User:AndyMabbett|Andy Mabbett]]
*[http://www.genuki.org.uk/cgi-bin/places GENUKI Gazetteer] (UK & Ireland) e.g. [http://www.genuki.org.uk/cgi-bin/maplink?CCC=STS,GR=SP040940,PLACE=Great%20Barr]
**Requested via feedback form, 2007-01-20 [[User:AndyMabbett|Andy Mabbett]]
*[http://www.confluence.org/ The Degree Confluence Project]
**Requested by e-mail, 2007-03-26 [[User:AndyMabbett|Andy Mabbett]]
*[http://www.wikimapia.org/ WikiMapia]
**Requested by e-mail, 2007-03-27 [[User:AndyMabbett|Andy Mabbett]]
**Replied to say they're looking into it. 2007-03-29
*[http://www.jeeep.com/details/coord/translate.cgi?datum=83&lat=52.57265&lon=-1.911433&detail=1 Jeeep.com]
**Requested by e-mail, 2007-03-27 [[User:AndyMabbett|Andy Mabbett]]
**Advertised address bouncing, 2007-03-27
*[http://www.flagr.com/ Flagr]
**Using, but not (yet) displaying, coordinates
**Requested by e-mail, 2007-03-30; also suggested they display their coordinates, and mark them up as tags [[User:AndyMabbett|Andy Mabbett]]
**Replied same day to say they will "talk it over internally"
* Various [http://en.wikipedia.org/wiki/Geocaching#Geocache_listing_sites Geocache listing sites]

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

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

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

===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]]
*W3C
**{{SuccessMarker}} '''W3C webmaster''' [http://www.w3.org/People/Jean-Gui/ Jean-Guilhem Rouel] now has an hCard. [[User:AndyMabbett|Andy Mabbett]] 15:41, 4 Apr 2007 (PDT)
*{{SuccessMarker}}Wikipedia-EN - starting to roll-out
**UK Railway station template, e.g. [http://en.wikipedia.org/wiki/Birmingham_New_Street Birmingham New Street station] (includes Geo)

=== hCalendar Successes===

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

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

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

==Rejections==

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

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

== Comparisons With Alternative Approaches ==

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

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

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

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

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

Talk:posh

2007-05-05T00:46:29Z

JamesCraig: bullets

== Misuse of microformats logo for ‘POSH’ bling ==

On 3rd May Ben Ward [http://www.mail-archive.com/microformats-discuss@microformats.org/msg07543.html objected] to the use of the microformats logo in graphics promoting ‘POSH’, on grounds that it creates confusing and undesirable ambiguity between the terms ‘microformat’ and ‘POSH’. We're at a point where people are wrongly interpreting ‘microformat’ as a general term for semantic class names. The endorsement of these graphics on our own Wiki is a massive hindrance to our efforts to discourage such misuse.

Please indicate a vote below on the removal of the microformats logo POSH buttons.

*+1 — Ben Ward
*+1 — James Craig

Talk:posh

2007-05-05T00:45:52Z

JamesCraig: /* Misuse of microformats logo for ‘POSH’ bling */ +1

advocacy

2007-05-03T23:44:49Z

JamesCraig: /* CalDAV */ radar number

<h1> Advocacy </h1>

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

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

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

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

=== hCard ===
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')
* Alexa.com has online profiles for domains with contact information. Would be great if they could add hCard to those. 2007-04-18 [[User:Tantek]] requested of [[User:BenWest]] e.g.:
** http://www.alexa.com/data/details?url=alexa.com/
** http://www.alexa.com/data/details?url=w3.org/
* [http://sunlightlabs.com/api/ SunlightLabs API] provides profiles for US Congresspeople. Their [http://sunlightlabs.com/api/masterref/megatable.php megatable] could easily be marked up with hCard, and their APIs could return hCards and hCard fields.
** [[User:Tantek|Tantek]] 12:30, 20 Apr 2007 (PDT) contacted them and requested that they add hCard to megatable, consider a GethCard API method, and potentially a GethResume API method for each person.
** {{SuccessMarker}} [[User:CarlAnderson|CarlAnderson]] 26 Apr 2007: http://sunlightlabs.com/api does now have a people.getHCard.php API method to get an hCard for every member of congress. See the documentation at http://sunlightlabs.com/api/people.getHCard.php. An example call: http://api.sunlightlabs.com/people.getHCard.php?id=fakeopenID1
** {{SuccessMarker}} [[User:CarlAnderson|CarlAnderson]] 30 Apr 2007: I created a page of hCards for every member of congress: http://sunlightlabs.com/api/hcards/index.php

==== 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] [[User:AndyMabbett|Andy Mabbett]] 13:10, 28 Jan 2007 (PST)
* See also [[persondata|discussion of Wikipedia's Persondata]], which aligns very closely with hCard, but has additional date and place of birth & death fields. [[User:AndyMabbett|Andy Mabbett]] 13:23, 28 Mar 2007 (PDT)

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

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

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

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

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

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

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

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

====Other hCard====
* [http://www.imdb.com/ Internet Movie Database] (IMDb) for people (real, not characters), e.g. [http://www.imdb.com/name/nm0000007/ Humphrey Bogart]. [[User:AndyMabbett|Andy Mabbett]] 02:49, 13 Nov 2006 (PST)
**Can't find contact info! [[User:AndyMabbett|Andy Mabbett]]
*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.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://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:
*[http://meta.wikimedia.org/wiki/WikiGPS WikiGPS]
**Under development; notified of Geo microformat 2007-03-23
*Collections of waypoints
**See also [[geo-waypoint-examples]]
*Upcoming
**Some events, e.g. [http://upcoming.org/event/128155/ Multipack February 2007] are tagged thus: <code>geo:lat=52.4784</code>, <code>geo:lon=-1.9096</code>. This could be rendered as a geo microformat. [[User:AndyMabbett|Andy Mabbett]]
**Requested on (now defunct) Upcoming wiki 2007-01-14
**[http://suggestions.yahoo.com/detail/?prop=upcoming&fid=14362 Repeated on new suggestion board]. 2007-03-30. '''Please vote for this suggestion''' [[User:AndyMabbett|Andy Mabbett]]
*[http://www.census.gov/cgi-bin/gazetteer U.S. Gazetteer] e.g. [http://www.census.gov/cgi-bin/gazetteer?city=Birmingham&state=&zip=]
*[http://www.world-gazetteer.com/ World Gazetteer] e.g. [http://www.world-gazetteer.com/wg.php?x=&men=gpro&lng=en&dat=32&geo=-81&srt=npan&col=aohdq&pt=c&va=&geo=512945809]
**Requested by e-mail, 2007-01-20 [[User:AndyMabbett|Andy Mabbett]]
*[http://www.genuki.org.uk/cgi-bin/places GENUKI Gazetteer] (UK & Ireland) e.g. [http://www.genuki.org.uk/cgi-bin/maplink?CCC=STS,GR=SP040940,PLACE=Great%20Barr]
**Requested via feedback form, 2007-01-20 [[User:AndyMabbett|Andy Mabbett]]
*[http://www.confluence.org/ The Degree Confluence Project]
**Requested by e-mail, 2007-03-26 [[User:AndyMabbett|Andy Mabbett]]
*[http://www.wikimapia.org/ WikiMapia]
**Requested by e-mail, 2007-03-27 [[User:AndyMabbett|Andy Mabbett]]
**Replied to say they're looking into it. 2007-03-29
*[http://www.jeeep.com/details/coord/translate.cgi?datum=83&lat=52.57265&lon=-1.911433&detail=1 Jeeep.com]
**Requested by e-mail, 2007-03-27 [[User:AndyMabbett|Andy Mabbett]]
**Advertised address bouncing, 2007-03-27
*[http://www.flagr.com/ Flagr]
**Using, but not (yet) displaying, coordinates
**Requested by e-mail, 2007-03-30; also suggested they display their coordinates, and mark them up as tags [[User:AndyMabbett|Andy Mabbett]]
**Replied same day to say they will "talk it over internally"
* Various [http://en.wikipedia.org/wiki/Geocaching#Geocache_listing_sites Geocache listing sites]

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

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

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

===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]]
*W3C
**{{SuccessMarker}} '''W3C webmaster''' [http://www.w3.org/People/Jean-Gui/ Jean-Guilhem Rouel] now has an hCard. [[User:AndyMabbett|Andy Mabbett]] 15:41, 4 Apr 2007 (PDT)
*{{SuccessMarker}}Wikipedia-EN - starting to roll-out
**UK Railway station template, e.g. [http://en.wikipedia.org/wiki/Birmingham_New_Street Birmingham New Street station] (includes Geo)

=== hCalendar Successes===

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

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

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

==Rejections==

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

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

== Comparisons With Alternative Approaches ==

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

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

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

====James Craig====
Brian, you seem to be under the opinion that CalDAV is a competitor to hCalendar. It is not. The two are not mutually exclusive. CalDAV data is as open as the owner wants to make it; the same as hCalendar data. The general public will have as much access to it as they do with any open source project, and your comments about ICS files are completely misinformed. Perhaps you could make (or link to) an informed comparison, rather than just guessing what CalDAV may or may not do. Your statements don't really add to the content of this page. Disclaimer: My employer has a vested interest in seeing CalDAV succeed. I have a vested interest in seeing that BOTH hCalendar and CalDAV succeed.

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

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

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

assistive-technology-abbr-results

2007-05-03T18:01:15Z

JamesCraig: /* Markup Possibilities */ extra space

<h1>assistive technology abbr results</h1>
This page is for document the precise results of using [[assistive-technology]] with real world examples in the wild of the abbr design pattern, as nearly always used by [[hcalendar|hCalendar]] (e.g. dtstart, dtend), often by [[hreview|hReview]] (e.g. dtreviewed, rating) and sometimes by [[hcard|hCard]] (e.g. bday, type subproperty).

__TOC__

Each [[assistive-technology]] listed here MUST link to a precise description of the tool/service on the [[assistive-technology]] page, including version number, when published, etc.

Each test result listed for each assistive technology MUST link to the real world example that was tested.

== Test Cases ==
The [http://www.webstandards.org/action/atf/ WasP Accessibility Task Force] is working on a set of extended test cases that will cover the following data formats and markup formats. Please add to the list so we can create a comprehensive result set.

===Data Formats===
Please provide hyperlinks to examples in the wild for each case that is to be tested. Test cases with example in the wild URLs merit more testing than those without. However, the purpose of these test cases is to find the best solution, whether or not it is currently being used.
* ISO 8601 date with punctuation (YYYY-MM-DD)
* ISO 8601 datetime with punctuation (YYYY-MM-DDTHH:MM:SS)
* ISO 8601 datetime with punctuation and no seconds (YYYY-MM-DDTHH:MM)
* ISO 8601 UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SSZ)
* ISO 8601 pre-UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SS+HH:MM)
* ISO 8601 pre-UTC datetime with punctuation and no timezone minutes (YYYY-MM-DDTHH:MM:SS+HH)
* ISO 8601 post-UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SS-HH:MM)
* ISO 8601 post-UTC datetime with punctuation and no timezone minutes (YYYY-MM-DDTHH:MM:SS-HH)
* ISO 8601 datetime with punctuation but w/o timezone punctuation. ''The hypothesis is that something like "eleven o'clock plus oh seven hundred" may be more understandable than "eleven o'clock plus seven o'clock" (similarly for the hyphen, read as "dash").''
** pre-UTC (YYYY-MM-DDTHH:MM:SS+HHMM)
** post-UTC (YYYY-MM-DDTHH:MM:SS-HHMM)
* GEO Latitude/Longitude coordinates.

=== Rejected Data formats ===
Dates without punctuation as they have proved unusable. Proof is premise for [[http://www.webstandards.org/2007/04/27/haccessibility/ hAccessibility]] article on the Web Standards Project Buzz blog. Window Eyes and JAWS read un-punctuated dates as single number. [[http://www.webstandards.org/files/atf_microformats/jaws.mp3 JAWS 8 on IE7 citation (MP3 Audio)]] of "twenty million seventy-thousand three-hundred twelve" is reason enough for rejection.
* ISO 8601 date without dashes (YYYYMMDD)
* ISO 8601 datetime without dashes and colons (YYYYMMDDTHHMMSS)
* ISO 8601 datetime without dashes and colons and no seconds (YYYYMMDDTHHMM)
* ISO 8601 UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ)
* ISO 8601 pre-UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ+HHMM)
* ISO 8601 pre-UTC datetime without dashes and colons and no timezone minutes (YYYYMMDDTHHMMSSZ+HH)
* ISO 8601 post-UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ-HHMM)
* ISO 8601 post-UTC datetime without dashes and colons and no timezone minutes (YYYYMMDDTHHMMSSZ-HH)

===Markup Possibilities===
==== Valid HTML4 ====
* abbr-design-pattern (as currently recommended)
* Object with param value.
* Object with in-page data attribute.
* Span with title property.
* Nested spans with child title set to null.
* Nested abbr with child title set to null.
* Empty ins element with datetime attr (<code><span class="dtstart">13th<ins datetime="20070713"></ins></span></code>)
* Rarely used event handler. e.g. (<code><span class="dtstart" onchange="void(20070713)">13th</span></code>)

==== Invalid HTML4 ====
Markup possibilities that are invalid in HTML4/XHTML1 are noted here to be clear that they were considered and rejected. Since microformats build on [[posh]], any technique that is invalid semantic (X)HTML is unacceptable for a microformats solution. There is no need to bother testing these.
* Span with RDF dc:date attribute.
* Span with RDF geo:position attribute.

===Screenreader Language Pronunciations===
* English
* Spanish (need volunteer native Spanish speaker screen reader user)
* ?

===Verbosity settings===

* Punctuation, speak none.
* Punctuation, speak some.
* Punctuation, speak all.
* Title attributes, speak none.
* Title attributes, speak some (abbr and acronym).
* Title attributes, speak all.

===Screenreaders===
* Freedom Scientific JAWS (multiple versions TBD)
* GW Micro Window Eyes (multiple versions TBD)
* Apple Voiceover (multiple versions TBD)

== Results ==

To be determined.

== See Also ==
* [[accessibility]]
* [[assistive-technology]]

assistive-technology-abbr-results

2007-05-03T17:10:19Z

JamesCraig: /* Markup Possibilities */ added two from Victor Jalencas on uf-discuss

<h1>assistive technology abbr results</h1>
This page is for document the precise results of using [[assistive-technology]] with real world examples in the wild of the abbr design pattern, as nearly always used by [[hcalendar|hCalendar]] (e.g. dtstart, dtend), often by [[hreview|hReview]] (e.g. dtreviewed, rating) and sometimes by [[hcard|hCard]] (e.g. bday, type subproperty).

__TOC__

Each [[assistive-technology]] listed here MUST link to a precise description of the tool/service on the [[assistive-technology]] page, including version number, when published, etc.

Each test result listed for each assistive technology MUST link to the real world example that was tested.

== Test Cases ==
The [http://www.webstandards.org/action/atf/ WasP Accessibility Task Force] is working on a set of extended test cases that will cover the following data formats and markup formats. Please add to the list so we can create a comprehensive result set.

===Data Formats===
Please provide hyperlinks to examples in the wild for each case that is to be tested. Test cases with example in the wild URLs merit more testing than those without. However, the purpose of these test cases is to find the best solution, whether or not it is currently being used.
* ISO 8601 date with punctuation (YYYY-MM-DD)
* ISO 8601 datetime with punctuation (YYYY-MM-DDTHH:MM:SS)
* ISO 8601 datetime with punctuation and no seconds (YYYY-MM-DDTHH:MM)
* ISO 8601 UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SSZ)
* ISO 8601 pre-UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SS+HH:MM)
* ISO 8601 pre-UTC datetime with punctuation and no timezone minutes (YYYY-MM-DDTHH:MM:SS+HH)
* ISO 8601 post-UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SS-HH:MM)
* ISO 8601 post-UTC datetime with punctuation and no timezone minutes (YYYY-MM-DDTHH:MM:SS-HH)
* ISO 8601 datetime with punctuation but w/o timezone punctuation. ''The hypothesis is that something like "eleven o'clock plus oh seven hundred" may be more understandable than "eleven o'clock plus seven o'clock" (similarly for the hyphen, read as "dash").''
** pre-UTC (YYYY-MM-DDTHH:MM:SS+HHMM)
** post-UTC (YYYY-MM-DDTHH:MM:SS-HHMM)
* GEO Latitude/Longitude coordinates.

=== Rejected Data formats ===
Dates without punctuation as they have proved unusable. Proof is premise for [[http://www.webstandards.org/2007/04/27/haccessibility/ hAccessibility]] article on the Web Standards Project Buzz blog. Window Eyes and JAWS read un-punctuated dates as single number. [[http://www.webstandards.org/files/atf_microformats/jaws.mp3 JAWS 8 on IE7 citation (MP3 Audio)]] of "twenty million seventy-thousand three-hundred twelve" is reason enough for rejection.
* ISO 8601 date without dashes (YYYYMMDD)
* ISO 8601 datetime without dashes and colons (YYYYMMDDTHHMMSS)
* ISO 8601 datetime without dashes and colons and no seconds (YYYYMMDDTHHMM)
* ISO 8601 UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ)
* ISO 8601 pre-UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ+HHMM)
* ISO 8601 pre-UTC datetime without dashes and colons and no timezone minutes (YYYYMMDDTHHMMSSZ+HH)
* ISO 8601 post-UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ-HHMM)
* ISO 8601 post-UTC datetime without dashes and colons and no timezone minutes (YYYYMMDDTHHMMSSZ-HH)

===Markup Possibilities===
==== Valid HTML4 ====
* abbr-design-pattern (as currently recommended)
* Object with param value.
* Object with in-page data attribute.
* Span with title property.
* Nested spans with child title set to null.
* Nested abbr with child title set to null.
* Empty ins element with datetime attr (<code><span class="dtstart">13th<ins datetime="20070713"></ins></span></code>)
* Rarely used event handler. e.g. (<code><span class="dtstart" onchange="void(20070713)">13th</span></code>)

==== Invalid HTML4 ====
Markup possibilities that are invalid in HTML4/XHTML1 are noted here to be clear that they were considered and rejected. Since microformats build on [[posh]], any technique that is invalid semantic (X)HTML is unacceptable for a microformats solution. There is no need to bother testing these.
* Span with RDF dc:date attribute.
* Span with RDF geo:position attribute.

===Screenreader Language Pronunciations===
* English
* Spanish (need volunteer native Spanish speaker screen reader user)
* ?

===Verbosity settings===

* Punctuation, speak none.
* Punctuation, speak some.
* Punctuation, speak all.
* Title attributes, speak none.
* Title attributes, speak some (abbr and acronym).
* Title attributes, speak all.

===Screenreaders===
* Freedom Scientific JAWS (multiple versions TBD)
* GW Micro Window Eyes (multiple versions TBD)
* Apple Voiceover (multiple versions TBD)

== Results ==

To be determined.

== See Also ==
* [[accessibility]]
* [[assistive-technology]]

assistive-technology-abbr-results

2007-05-02T19:23:03Z

JamesCraig: /* Test Cases */ removing leftovers

<h1>assistive technology abbr results</h1>
This page is for document the precise results of using [[assistive-technology]] with real world examples in the wild of the abbr design pattern, as nearly always used by [[hcalendar|hCalendar]] (e.g. dtstart, dtend), often by [[hreview|hReview]] (e.g. dtreviewed, rating) and sometimes by [[hcard|hCard]] (e.g. bday, type subproperty).

__TOC__

Each [[assistive-technology]] listed here MUST link to a precise description of the tool/service on the [[assistive-technology]] page, including version number, when published, etc.

Each test result listed for each assistive technology MUST link to the real world example that was tested.

== Test Cases ==
The [http://www.webstandards.org/action/atf/ WasP Accessibility Task Force] is working on a set of extended test cases that will cover the following data formats and markup formats. Please add to the list so we can create a comprehensive result set.

===Data Formats===
Please provide hyperlinks to examples in the wild for each case that is to be tested. Test cases with example in the wild URLs merit more testing than those without. However, the purpose of these test cases is to find the best solution, whether or not it is currently being used.
* ISO 8601 date with punctuation (YYYY-MM-DD)
* ISO 8601 datetime with punctuation (YYYY-MM-DDTHH:MM:SS)
* ISO 8601 datetime with punctuation and no seconds (YYYY-MM-DDTHH:MM)
* ISO 8601 UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SSZ)
* ISO 8601 pre-UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SS+HH:MM)
* ISO 8601 pre-UTC datetime with punctuation and no timezone minutes (YYYY-MM-DDTHH:MM:SS+HH)
* ISO 8601 post-UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SS-HH:MM)
* ISO 8601 post-UTC datetime with punctuation and no timezone minutes (YYYY-MM-DDTHH:MM:SS-HH)
* ISO 8601 datetime with punctuation but w/o timezone punctuation. ''The hypothesis is that something like "eleven o'clock plus oh seven hundred" may be more understandable than "eleven o'clock plus seven o'clock" (similarly for the hyphen, read as "dash").''
** pre-UTC (YYYY-MM-DDTHH:MM:SS+HHMM)
** post-UTC (YYYY-MM-DDTHH:MM:SS-HHMM)
* GEO Latitude/Longitude coordinates.

=== Rejected Data formats ===
Dates without punctuation as they have proved unusable. Proof is premise for [[http://www.webstandards.org/2007/04/27/haccessibility/ hAccessibility]] article on the Web Standards Project Buzz blog. Window Eyes and JAWS read un-punctuated dates as single number. [[http://www.webstandards.org/files/atf_microformats/jaws.mp3 JAWS 8 on IE7 citation (MP3 Audio)]] of "twenty million seventy-thousand three-hundred twelve" is reason enough for rejection.
* ISO 8601 date without dashes (YYYYMMDD)
* ISO 8601 datetime without dashes and colons (YYYYMMDDTHHMMSS)
* ISO 8601 datetime without dashes and colons and no seconds (YYYYMMDDTHHMM)
* ISO 8601 UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ)
* ISO 8601 pre-UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ+HHMM)
* ISO 8601 pre-UTC datetime without dashes and colons and no timezone minutes (YYYYMMDDTHHMMSSZ+HH)
* ISO 8601 post-UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ-HHMM)
* ISO 8601 post-UTC datetime without dashes and colons and no timezone minutes (YYYYMMDDTHHMMSSZ-HH)

===Markup Possibilities===
==== Valid HTML4 ====
* abbr-design-pattern (as currently recommended)
* Object with param value.
* Object with in-page data attribute.
* Span with title property.
* Nested spans with child title set to null.
* Nested abbr with child title set to null.

==== Invalid HTML4 ====
Markup possibilities that are invalid in HTML4/XHTML1 are noted here to be clear that they were considered and rejected. Since microformats build on [[posh]], any technique that is invalid semantic (X)HTML is unacceptable for a microformats solution. There is no need to bother testing these.
* Span with RDF dc:date attribute.
* Span with RDF geo:position attribute.

===Screenreader Language Pronunciations===
* English
* Spanish (need volunteer native Spanish speaker screen reader user)
* ?

===Verbosity settings===

* Punctuation, speak none.
* Punctuation, speak some.
* Punctuation, speak all.
* Title attributes, speak none.
* Title attributes, speak some (abbr and acronym).
* Title attributes, speak all.

===Screenreaders===
* Freedom Scientific JAWS (multiple versions TBD)
* GW Micro Window Eyes (multiple versions TBD)
* Apple Voiceover (multiple versions TBD)

== Results ==

To be determined.

== See Also ==
* [[accessibility]]
* [[assistive-technology]]

advocacy

2007-05-02T18:45:20Z

JamesCraig: /* Comparisons With Alternative Approaches */ adding facts and signed opinions

<h1> Advocacy </h1>

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

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

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

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

=== hCard ===
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')
* Alexa.com has online profiles for domains with contact information. Would be great if they could add hCard to those. 2007-04-18 [[User:Tantek]] requested of [[User:BenWest]] e.g.:
** http://www.alexa.com/data/details?url=alexa.com/
** http://www.alexa.com/data/details?url=w3.org/
* [http://sunlightlabs.com/api/ SunlightLabs API] provides profiles for US Congresspeople. Their [http://sunlightlabs.com/api/masterref/megatable.php megatable] could easily be marked up with hCard, and their APIs could return hCards and hCard fields.
** [[User:Tantek|Tantek]] 12:30, 20 Apr 2007 (PDT) contacted them and requested that they add hCard to megatable, consider a GethCard API method, and potentially a GethResume API method for each person.
** {{SuccessMarker}} [[User:CarlAnderson|CarlAnderson]] 26 Apr 2007: http://sunlightlabs.com/api does now have a people.getHCard.php API method to get an hCard for every member of congress. See the documentation at http://sunlightlabs.com/api/people.getHCard.php. An example call: http://api.sunlightlabs.com/people.getHCard.php?id=fakeopenID1
** {{SuccessMarker}} [[User:CarlAnderson|CarlAnderson]] 30 Apr 2007: I created a page of hCards for every member of congress: http://sunlightlabs.com/api/hcards/index.php

==== 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] [[User:AndyMabbett|Andy Mabbett]] 13:10, 28 Jan 2007 (PST)
* See also [[persondata|discussion of Wikipedia's Persondata]], which aligns very closely with hCard, but has additional date and place of birth & death fields. [[User:AndyMabbett|Andy Mabbett]] 13:23, 28 Mar 2007 (PDT)

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

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

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

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

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

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

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

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

====Other hCard====
* [http://www.imdb.com/ Internet Movie Database] (IMDb) for people (real, not characters), e.g. [http://www.imdb.com/name/nm0000007/ Humphrey Bogart]. [[User:AndyMabbett|Andy Mabbett]] 02:49, 13 Nov 2006 (PST)
**Can't find contact info! [[User:AndyMabbett|Andy Mabbett]]
*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.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://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:
*[http://meta.wikimedia.org/wiki/WikiGPS WikiGPS]
**Under development; notified of Geo microformat 2007-03-23
*Collections of waypoints
**See also [[geo-waypoint-examples]]
*Upcoming
**Some events, e.g. [http://upcoming.org/event/128155/ Multipack February 2007] are tagged thus: <code>geo:lat=52.4784</code>, <code>geo:lon=-1.9096</code>. This could be rendered as a geo microformat. [[User:AndyMabbett|Andy Mabbett]]
**Requested on (now defunct) Upcoming wiki 2007-01-14
**[http://suggestions.yahoo.com/detail/?prop=upcoming&fid=14362 Repeated on new suggestion board]. 2007-03-30. '''Please vote for this suggestion''' [[User:AndyMabbett|Andy Mabbett]]
*[http://www.census.gov/cgi-bin/gazetteer U.S. Gazetteer] e.g. [http://www.census.gov/cgi-bin/gazetteer?city=Birmingham&state=&zip=]
*[http://www.world-gazetteer.com/ World Gazetteer] e.g. [http://www.world-gazetteer.com/wg.php?x=&men=gpro&lng=en&dat=32&geo=-81&srt=npan&col=aohdq&pt=c&va=&geo=512945809]
**Requested by e-mail, 2007-01-20 [[User:AndyMabbett|Andy Mabbett]]
*[http://www.genuki.org.uk/cgi-bin/places GENUKI Gazetteer] (UK & Ireland) e.g. [http://www.genuki.org.uk/cgi-bin/maplink?CCC=STS,GR=SP040940,PLACE=Great%20Barr]
**Requested via feedback form, 2007-01-20 [[User:AndyMabbett|Andy Mabbett]]
*[http://www.confluence.org/ The Degree Confluence Project]
**Requested by e-mail, 2007-03-26 [[User:AndyMabbett|Andy Mabbett]]
*[http://www.wikimapia.org/ WikiMapia]
**Requested by e-mail, 2007-03-27 [[User:AndyMabbett|Andy Mabbett]]
**Replied to say they're looking into it. 2007-03-29
*[http://www.jeeep.com/details/coord/translate.cgi?datum=83&lat=52.57265&lon=-1.911433&detail=1 Jeeep.com]
**Requested by e-mail, 2007-03-27 [[User:AndyMabbett|Andy Mabbett]]
**Advertised address bouncing, 2007-03-27
*[http://www.flagr.com/ Flagr]
**Using, but not (yet) displaying, coordinates
**Requested by e-mail, 2007-03-30; also suggested they display their coordinates, and mark them up as tags [[User:AndyMabbett|Andy Mabbett]]
**Replied same day to say they will "talk it over internally"
* Various [http://en.wikipedia.org/wiki/Geocaching#Geocache_listing_sites Geocache listing sites]

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

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

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

===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]]
*W3C
**{{SuccessMarker}} '''W3C webmaster''' [http://www.w3.org/People/Jean-Gui/ Jean-Guilhem Rouel] now has an hCard. [[User:AndyMabbett|Andy Mabbett]] 15:41, 4 Apr 2007 (PDT)
*{{SuccessMarker}}Wikipedia-EN - starting to roll-out
**UK Railway station template, e.g. [http://en.wikipedia.org/wiki/Birmingham_New_Street Birmingham New Street station] (includes Geo)

=== hCalendar Successes===

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

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

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

==Rejections==

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

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

== Comparisons With Alternative Approaches ==

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

====Apple Support Tickets====
Calendar Server hCalendar input/output: http://trac.macosforge.org/projects/calendarserver/ticket/19
Wiki Server hCalendar output (internal RDAR ticket)

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

====James Craig====
Brian, you seem to be under the opinion that CalDAV is a competitor to hCalendar. It is not. The two are not mutually exclusive. CalDAV data is as open as the owner wants to make it; the same as hCalendar data. The general public will have as much access to it as they do with any open source project, and your comments about ICS files are completely misinformed. Perhaps you could make (or link to) an informed comparison, rather than just guessing what CalDAV may or may not do. Your statements don't really add to the content of this page. Disclaimer: My employer has a vested interest in seeing CalDAV succeed. I have a vested interest in seeing that BOTH hCalendar and CalDAV succeed.

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

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

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

haudio

2007-05-02T17:22:21Z

JamesCraig: /* Podcast Example */ updating example at manu's req (these, too)

<h1>hAudio 0.2</h1>

[[haudio|hAudio]] is a simple, open, distributed format, suitable for embedding information about audio recordings in (X)HTML, Atom, RSS, and arbitrary XML. hAudio is one of several [[microformats]] open standards.

== hAudio Microformat Draft Specification 2007-04-18 ==

; Editor: [[User:ManuSporny | Manu Sporny]], [http://www.bitmunk.com/ Bitmunk] - [http://blog.digitalbazaar.com Digital Bazaar], Inc.
; Authors: [[User:ManuSporny | Manu Sporny]], [http://www.bitmunk.com/ Bitmunk] - [http://blog.digitalbazaar.com Digital Bazaar], Inc.
: Martin McEvoy
: Alexandre Van De Sande
: Michael Johnson
: Dave Longley

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

__TOC__

== Introduction ==

It is difficult for a browser to extract semantic information about an audio recording described on a web page. Metadata such as speaker, musician, publisher, label, title of the work, release date, acquisition link, related image artwork and tags provide relevant context for the audio recording.

Having such information marked up can provide a number of benefits to the viewer. If a web browser understands that a particular web page contains a song performed by an artist, it can produce richer interactions. For example, specific searches may be performed for artists and songs via general search services such as Google and Wikipedia. Specific search services may also be queried such as MusicBrainz, The Internet Archive, FreeDB, or Bitmunk. Additionally, classification by crawlers can become more accurate. If there are 20 tracks found on a page done by the same artist, and that content consumes a significant portion of the page, it can be assumed that the page is not only about music, but also about a particular artist.

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

=== Inspiration and Acknowledgments ===

Many thanks to the various individuals that did research and proposed ideas and discussion related to media info and audio info in general. Among the many participants are [[RodBegbie]], Dean Hudson, [http://tantek.com/log/ Tantek Çelik], [http://napsterization.org/stories/ Mary Hodder], [http://joshkinberg.com/blog/ Joshua Kinberg], ChrisMessina, and [http://onlisareinsradar.com/ Lisa Rein].

=== Scope ===

Audio content consistently share several common fields. Where possible hAudio has been based on this minimal common subset.

==== Out of scope ====

Fields that are type-specific have been omitted from hAudio. It is important that hAudio 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 audio identifier, that is, how to identify the same audio album, song, speech, or podcast across different music and audio 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 hAudio format is based on a set of fields common to numerous audio content 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]] standards.

=== Schema ===

The hAudio schema consists of the following:

* hAudio ('''<code>haudio</code>''')
** '''work-title'''. required. text.
** '''contributor'''. optional. using [[hCard]].
*** suggested ''''role''''s: speaker, artist, composer, band, publisher
** '''published-date'''. optional. using [[datetime-design-pattern]].
** '''sample'''. optional. using [[rel-design-pattern]] with <code>sample</code> as the <code>mf-rel-value</code>.
** '''acquire'''. optional. using [[rel-design-pattern]] with <code>acquire</code> as the <code>mf-rel-value</code>.
** '''image-summary'''. optional. using HTML and XHTML tag <code>img</code>.
** '''genre'''. optional. text.
** '''length'''. optional. time in seconds using [[abbr-design-pattern]].
** '''price'''. optional. using [[currency-proposal]].

'''tracks''', '''songs''', and '''parts''' in general are specified by embedding hAudio's inside of hAudios and using the ideas put forth in [[grouping-brainstorming]] and [[grouping-proposal]]. Defining parts of an hAudio will not be complete without a complete grouping draft/specification.

=== Field details ===

The fields of the hAudio schema represent the following:

==== hAudio ====

An hAudio is used to identify and describe metadata associated with a particular audio recording.

* an hAudio element is identified by class name <code>haudio</code>
* hAudio content may contain other hAudios. This is most prevalent when describing Audio Albums. The outermost container is an hAudio describing an album, while the inner hAudios are the tracks in the album.

==== Work Title ====

A Work Title is a short textual description used to identify an audio recording among interested parties. This can be the title of a speech, album title, song title, or short description regarding a sound effect.

* The element is identified by the class name <code>work-title</code>.
* hAudio MUST have a Work Title.

==== Contributor ====

A Contributor is any entity that takes part in the creation and distribution of an audio recording. Examples include: artist, publisher, guitarist, vocalist, violinist, lead singer, backup singer, bassist, drummer, manager, and roadie.

* The element is identified by the class name <code>contributor</code>.
* hAudio MAY include one or more contributors.
* The contents of the element must include a valid [[hCard]] Microformat.
* The <code>role</code> field should be used to specify the Contributor's responsibility related to the audio recording.
* If multiple Contributors are specified without <code>role</code> specifications, it may be assumed that the first role mentioned is the creator.

==== Published Date ====

The Published Date specifies the date that the audio recording was made available to the public. Examples include: The airing date of a radio broadcast, the day a speech was given, or the day a music album was made available for sale.

* The element is identified by the class name <code>published-date</code>.
* hAudio MAY include one or more <code>published-date</code>s.
* The contents of the element must include a date format compliant with the [[datetime-design-pattern]].

==== Sample URL ====

A Sample URL specifies from where an excerpt of the audio recording may be retrieved.

* The element is identified by a URL fitting the [[rel-design-pattern]], the rel content being <code>sample</code>.
* hAudio MAY include one or more URL <code>sample</code>s.
* The URL SHOULD point to a directly accessible stream or file.
* The type of the sample MAY be specified by using the <code>type</code> specifier for a URL.

==== Acquire ====

An Acquire URL specifies from where the full version of an audio recording may be retrieved. The URL can point to a process required (such as purchasing) that must be completed to acquire the audio recording.

* The element is identified by a URL fitting the [[rel-design-pattern]], the rel content being <code>acquire</code>.
* hAudio MAY include one or more <code>acquire</code> URLs.
* The type of the file MAY be specified by using the <code>type</code> specifier for a URL.

==== Image Summary ====

An Image Summary specifies an image that should be used to summarize the audio recording. Examples include: the image of a speaker, an audio album cover image, and a picture from a concert.

* The element is identified by the class name <code>image-summary</code>.
* hAudio MAY include one or more <code>image-summary</code> images.
* The contents of the element must be wrapped in the <img> tag.

==== Genre ====

The Genre specifies the category used to classify the audio recording. Examples include: blues, rock, motivational, spoken word, or sound effect.

* The element is identified by the class name <code>genre</code>.
* hAudio MAY include one or more <code>genre</code>s.

==== Length ====

The Length specifies the length of the audio recording in seconds. Examples include: 104 seconds, 3:23, and 4 minutes.

* The element is identified by the class name <code>length</code>.
* hAudio MAY include one <code>length</code> element.
* The contents of the element SHOULD use the [[abbr-design-pattern]].

==== Price ====

The Price specifies the amount of currency that must be exchanged for acquisition of a full specimen of the audio recording. Examples include: One Dollar, $2, and £4.

* The element is identified by the class name <code>price</code>.
* hAudio MAY include one or more <code>price</code> elements.
* The contents of the element SHOULD use the [[currency-proposal]].

==== Grouping (Albums, Songs, and Tracks) ====

hAudio defines a method to specify albums, songs and tracks. The grouping and xoxo Microformats are used to provide the concept of sets, collections, groups and lists. Use of these two Microformats allow for the creation of Albums, Podcasts, Multi-part speeches, and relationships between audio recordings.

* A group is identified by using the grouping Microformat with the hAudio class.
* hAudio MAY encapsulate one or more <code>haudio</code> class tags.
* Grouping information between hAudio is specified using the grouping Microformat (and only the grouping Microformat).
* Sets that require a particular order (aka: Lists) must use the xoxo Microformat to define that order.

=== 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 'haudio' in hAudio.
* And for "image-summary", use <code><img class="image-summary" src="..." alt="Photo of ..." /></code>

==== Language ====

* To explicitly convey the natural language that an hAudio is written in, use the standard (X)HTML 'lang' attribute on the element with class="haudio", e.g. <code><div class="haudio" lang="en"> ... </div></code> If portions of an hAudio (e.g. the item name) are in a different language, use the 'lang' attribute on those portions.
* hAudio 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 "image-summary" 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.

=== Notes ===

This section is informative.

* By marking up audio content with the hAudio microformat, the expectation is communicated that information about the content MAY be indexed. This has no impact on the copyright of the content 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 hAudio 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.

== XMDP Profile ==

<pre>
<dl class="profile">
<dt>class</dt>
<dd><p>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>haudio</dt>
<dd>
Used to identify and describe metadata associated with a particular audio recording.
</dd>
<dt>work-title</dt>
<dd>
A short textual description used to identify an audio recording among interested parties.
</dd>
<dt>collaborator</dt>
<dd>
An entity that takes part in the creation and distribution of an audio recording.
</dd>
<dt>release-date</dt>
<dd>
The date that the audio recording was made available to the public.
</dd>
<dt>image-summary</dt>
<dd>
An image that should be used to summarize the audio recording.
</dd>
<dt>genre</dt>
<dd>
The category used to classify the audio recording.
</dd>
<dt>length</dt>
<dd>
The length of the audio recording in seconds.
</dd>
<dt>price</dt>
<dd>
The amount of currency that must be exchanged for acquisition of a full specimen of the audio recording.
</dd>
</dd>
</dl>
</pre>

== Examples ==
Here are a few examples of audio content from current web sites, and how they could be easily enhanced to support the hAudio audio metadata microformat.

Want to write valid [[haudio|hAudio]]? Use the [http://microformats.org/code/haudio/creator hAudio creator] (not implemented yet) to write about audio content and publish it on your blog.

=== Simple Song Example ===

Display:

Start Wearing Purple by Gogol Bordello

Microformatted XHTML:

<pre>
<div class="haudio">
<span class="work-title">Start Wearing Purple</span> by
<span class="collaborator hcard fn">Gogol Bordello</span>
</div>
</pre>

=== Speech Example ===

Display:

I Have a Dream, a speech by Martin Luther King Jr.

Microformatted XHTML:

<pre>
<div class="haudio">
<span class="work-title">I Have a Dream</span>, a
<span class="genre">speech</span> by
<span class="collaborator hcard fn">Martin Luther King Jr.</span>
</div>
</pre>

=== Audio Album Example ===

Display:

Black Horse and The Cherry Tree by KT Tunstall

# Black Horse & The Cherry Tree
# One Day [Live]

Microformatted XHTML:

<pre>
<div class="haudio grouping.ktsampler">
<span class="title">Black Horse and The Cherry Tree</span> by
<span class="collaborator hcard fn">KT Tunstall</span>
<ol class="xoxo">
<li>
<div class="haudio grouping.ktsampler.bh">
<span class="work-title">Black Horse & The Cherry Tree</span>
</div>
</li>
<li>
<div class="haudio grouping.ktsampler.od">
<span class="work-title">One Day [Live]</span>
</div>
</li>
</ol>
</div>
</pre>

=== Podcast Example ===

Display:

BBC Today Podcasts for Saturday, 28 April 2007.

* 8.10 Interview - Nottingham has become pivotal in the local elections.
** [http://downloads.bbc.co.uk/rmhttp/downloadtrial/radio4/today/today_20070428-0810_40_st.mp3 Download 8.10 Interview]
** [http://downloads.bbc.co.uk/rmhttp/downloadtrial/radio4/today/rss.xml Add to RSS]
* The Today Lead Interviews - The Today Programme morning briefing, ten to eight and half past eight interviews.
** [http://downloads.bbc.co.uk/rmhttp/downloadtrial/radio4/todayleadscombined/todayleadscombined_20070428-0900_40_st.mp3 Download the Today Lead Interviews]
** [http://downloads.bbc.co.uk/rmhttp/downloadtrial/radio4/today/rss.xml Add to RSS]
* BBC Radio NewsPod - Daily programme highlights from across BBC Radio News.
** [http://downloads.bbc.co.uk/rmhttp/downloadtrial/radionews/bbcradionewspod/bbcradionewspod_20070427-1800_40_st.mp3 Download BBC Radio NewsPod]
** [http://downloads.bbc.co.uk/rmhttp/downloadtrial/radio4/today/rss.xml Add to RSS]

Microformatted XHTML:

<pre>
<div class="haudio grouping.today-podcast">
<span class="work-title">BBC Today Podcasts</span> for
<abbr class="release-date" title="20070428">Saturday, 28 April 2007</span>.
</div>

<ul>
<li>
<div class="haudio grouping.today-podcast.810-interview">
<span class="work-title">8.10 Interview</span> -
Nottingham has become pivotal in the local elections.
<ul>
<li><a rel="acquire" href="http://downloads.bbc...-0810_40_st.mp3">Download 8.10 Interview</a></li>
<li><a href="http://downloads.bbc...today/rss.xml">Add to RSS</a>
</ul>
</div>
</li>
<li>
<div class="haudio grouping.today-podcast.the-today-lead-interviews">
<span class="work-title">The Today Lead Interviews</span> -
The Today Programme morning briefing, ten to eight and half past eight interviews.
<ul>
<li><a rel="acquire" href="http://downloads.bbc...-0900_40_st.mp3">Download the Today Lead Interviews</a></li>
<li><a href="http://downloads.bbc...today/rss.xml">Add to RSS</a>
</ul>
</div>
</li>
<li>
<div class="haudio grouping.today-podcast.bbc-radio-newspod">
<span class="work-title">BBC Radio NewsPod</span> -
Daily programme highlights from across BBC Radio News.
<ul>
<li><a rel="acquire" href="http://downloads.bbc...-1800_40_st.mp3">Download BBC Radio NewsPod</a></li>
<li><a href="http://downloads.bbc...today/rss.xml">Add to RSS</a>
</ul>
</div>
</li>
</ul>
</pre>

=== Complex hAudio Example ===

'''NEED AN EXAMPLE'''

== Examples in the wild ==

This section is '''informative'''.

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

See [[haudio-implementations|hAudio Implementations]].

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

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

==== Similar Work ====
* [[media-info-examples]]
* [[media-info-formats]]
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===
This document and specification is distributed under a [http://creativecommons.org/licenses/by/3.0/ Creative Commons Attribution 3.0 license]. It is licensed and can be used royalty-free for any purpose.

The authors intend to submit this specification to a standards body with a liberal copyright/licensing policy such as the GMPG (http://gmpg.org/), IETF (http://ietf.org/), and/or W3C (http://w3.org). Anyone wishing to contribute should read each organizations copyright principles, policies and licenses (e.g. the GMPG Principles (http://gmpg.org/principles)) and agree to them, including licensing of all contributions under all required licenses (e.g. CC-by 1.0 (http://creativecommons.org/licenses/by/1.0/) and later), before contributing.

=== Patents ===

The authors of this Microformat have not and will not apply for patents covering any invention covering this Microformat in part or as a whole. There are no claims to any patent in this document. Each author is required to report any known patent issues immediately under this section.

This document and specification is distributed under a royalty free patent policy, e.g. per the W3C Patent Policy (http://www.w3.org/Consortium/Patent-Policy-20040205/), and IETF RFC3667 (http://www.ietf.org/rfc/rfc3667.txt) & RFC3668 (http://www.ietf.org/rfc/rfc3668.txt).

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

== Further Reading ==

==See also==
*[[audio-info-brainstorming]]
*[[audio-info-examples]]

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

haudio

2007-05-02T17:14:50Z

JamesCraig: /* Podcast Example */ updating example at manu's req

<h1>hAudio 0.2</h1>

[[haudio|hAudio]] is a simple, open, distributed format, suitable for embedding information about audio recordings in (X)HTML, Atom, RSS, and arbitrary XML. hAudio is one of several [[microformats]] open standards.

== hAudio Microformat Draft Specification 2007-04-18 ==

; Editor: [[User:ManuSporny | Manu Sporny]], [http://www.bitmunk.com/ Bitmunk] - [http://blog.digitalbazaar.com Digital Bazaar], Inc.
; Authors: [[User:ManuSporny | Manu Sporny]], [http://www.bitmunk.com/ Bitmunk] - [http://blog.digitalbazaar.com Digital Bazaar], Inc.
: Martin McEvoy
: Alexandre Van De Sande
: Michael Johnson
: Dave Longley

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

__TOC__

== Introduction ==

It is difficult for a browser to extract semantic information about an audio recording described on a web page. Metadata such as speaker, musician, publisher, label, title of the work, release date, acquisition link, related image artwork and tags provide relevant context for the audio recording.

Having such information marked up can provide a number of benefits to the viewer. If a web browser understands that a particular web page contains a song performed by an artist, it can produce richer interactions. For example, specific searches may be performed for artists and songs via general search services such as Google and Wikipedia. Specific search services may also be queried such as MusicBrainz, The Internet Archive, FreeDB, or Bitmunk. Additionally, classification by crawlers can become more accurate. If there are 20 tracks found on a page done by the same artist, and that content consumes a significant portion of the page, it can be assumed that the page is not only about music, but also about a particular artist.

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

=== Inspiration and Acknowledgments ===

Many thanks to the various individuals that did research and proposed ideas and discussion related to media info and audio info in general. Among the many participants are [[RodBegbie]], Dean Hudson, [http://tantek.com/log/ Tantek Çelik], [http://napsterization.org/stories/ Mary Hodder], [http://joshkinberg.com/blog/ Joshua Kinberg], ChrisMessina, and [http://onlisareinsradar.com/ Lisa Rein].

=== Scope ===

Audio content consistently share several common fields. Where possible hAudio has been based on this minimal common subset.

==== Out of scope ====

Fields that are type-specific have been omitted from hAudio. It is important that hAudio 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 audio identifier, that is, how to identify the same audio album, song, speech, or podcast across different music and audio 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 hAudio format is based on a set of fields common to numerous audio content 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]] standards.

=== Schema ===

The hAudio schema consists of the following:

* hAudio ('''<code>haudio</code>''')
** '''work-title'''. required. text.
** '''contributor'''. optional. using [[hCard]].
*** suggested ''''role''''s: speaker, artist, composer, band, publisher
** '''published-date'''. optional. using [[datetime-design-pattern]].
** '''sample'''. optional. using [[rel-design-pattern]] with <code>sample</code> as the <code>mf-rel-value</code>.
** '''acquire'''. optional. using [[rel-design-pattern]] with <code>acquire</code> as the <code>mf-rel-value</code>.
** '''image-summary'''. optional. using HTML and XHTML tag <code>img</code>.
** '''genre'''. optional. text.
** '''length'''. optional. time in seconds using [[abbr-design-pattern]].
** '''price'''. optional. using [[currency-proposal]].

'''tracks''', '''songs''', and '''parts''' in general are specified by embedding hAudio's inside of hAudios and using the ideas put forth in [[grouping-brainstorming]] and [[grouping-proposal]]. Defining parts of an hAudio will not be complete without a complete grouping draft/specification.

=== Field details ===

The fields of the hAudio schema represent the following:

==== hAudio ====

An hAudio is used to identify and describe metadata associated with a particular audio recording.

* an hAudio element is identified by class name <code>haudio</code>
* hAudio content may contain other hAudios. This is most prevalent when describing Audio Albums. The outermost container is an hAudio describing an album, while the inner hAudios are the tracks in the album.

==== Work Title ====

A Work Title is a short textual description used to identify an audio recording among interested parties. This can be the title of a speech, album title, song title, or short description regarding a sound effect.

* The element is identified by the class name <code>work-title</code>.
* hAudio MUST have a Work Title.

==== Contributor ====

A Contributor is any entity that takes part in the creation and distribution of an audio recording. Examples include: artist, publisher, guitarist, vocalist, violinist, lead singer, backup singer, bassist, drummer, manager, and roadie.

* The element is identified by the class name <code>contributor</code>.
* hAudio MAY include one or more contributors.
* The contents of the element must include a valid [[hCard]] Microformat.
* The <code>role</code> field should be used to specify the Contributor's responsibility related to the audio recording.
* If multiple Contributors are specified without <code>role</code> specifications, it may be assumed that the first role mentioned is the creator.

==== Published Date ====

The Published Date specifies the date that the audio recording was made available to the public. Examples include: The airing date of a radio broadcast, the day a speech was given, or the day a music album was made available for sale.

* The element is identified by the class name <code>published-date</code>.
* hAudio MAY include one or more <code>published-date</code>s.
* The contents of the element must include a date format compliant with the [[datetime-design-pattern]].

==== Sample URL ====

A Sample URL specifies from where an excerpt of the audio recording may be retrieved.

* The element is identified by a URL fitting the [[rel-design-pattern]], the rel content being <code>sample</code>.
* hAudio MAY include one or more URL <code>sample</code>s.
* The URL SHOULD point to a directly accessible stream or file.
* The type of the sample MAY be specified by using the <code>type</code> specifier for a URL.

==== Acquire ====

An Acquire URL specifies from where the full version of an audio recording may be retrieved. The URL can point to a process required (such as purchasing) that must be completed to acquire the audio recording.

* The element is identified by a URL fitting the [[rel-design-pattern]], the rel content being <code>acquire</code>.
* hAudio MAY include one or more <code>acquire</code> URLs.
* The type of the file MAY be specified by using the <code>type</code> specifier for a URL.

==== Image Summary ====

An Image Summary specifies an image that should be used to summarize the audio recording. Examples include: the image of a speaker, an audio album cover image, and a picture from a concert.

* The element is identified by the class name <code>image-summary</code>.
* hAudio MAY include one or more <code>image-summary</code> images.
* The contents of the element must be wrapped in the <img> tag.

==== Genre ====

The Genre specifies the category used to classify the audio recording. Examples include: blues, rock, motivational, spoken word, or sound effect.

* The element is identified by the class name <code>genre</code>.
* hAudio MAY include one or more <code>genre</code>s.

==== Length ====

The Length specifies the length of the audio recording in seconds. Examples include: 104 seconds, 3:23, and 4 minutes.

* The element is identified by the class name <code>length</code>.
* hAudio MAY include one <code>length</code> element.
* The contents of the element SHOULD use the [[abbr-design-pattern]].

==== Price ====

The Price specifies the amount of currency that must be exchanged for acquisition of a full specimen of the audio recording. Examples include: One Dollar, $2, and £4.

* The element is identified by the class name <code>price</code>.
* hAudio MAY include one or more <code>price</code> elements.
* The contents of the element SHOULD use the [[currency-proposal]].

==== Grouping (Albums, Songs, and Tracks) ====

hAudio defines a method to specify albums, songs and tracks. The grouping and xoxo Microformats are used to provide the concept of sets, collections, groups and lists. Use of these two Microformats allow for the creation of Albums, Podcasts, Multi-part speeches, and relationships between audio recordings.

* A group is identified by using the grouping Microformat with the hAudio class.
* hAudio MAY encapsulate one or more <code>haudio</code> class tags.
* Grouping information between hAudio is specified using the grouping Microformat (and only the grouping Microformat).
* Sets that require a particular order (aka: Lists) must use the xoxo Microformat to define that order.

=== 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 'haudio' in hAudio.
* And for "image-summary", use <code><img class="image-summary" src="..." alt="Photo of ..." /></code>

==== Language ====

* To explicitly convey the natural language that an hAudio is written in, use the standard (X)HTML 'lang' attribute on the element with class="haudio", e.g. <code><div class="haudio" lang="en"> ... </div></code> If portions of an hAudio (e.g. the item name) are in a different language, use the 'lang' attribute on those portions.
* hAudio 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 "image-summary" 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.

=== Notes ===

This section is informative.

* By marking up audio content with the hAudio microformat, the expectation is communicated that information about the content MAY be indexed. This has no impact on the copyright of the content 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 hAudio 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.

== XMDP Profile ==

<pre>
<dl class="profile">
<dt>class</dt>
<dd><p>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>haudio</dt>
<dd>
Used to identify and describe metadata associated with a particular audio recording.
</dd>
<dt>work-title</dt>
<dd>
A short textual description used to identify an audio recording among interested parties.
</dd>
<dt>collaborator</dt>
<dd>
An entity that takes part in the creation and distribution of an audio recording.
</dd>
<dt>release-date</dt>
<dd>
The date that the audio recording was made available to the public.
</dd>
<dt>image-summary</dt>
<dd>
An image that should be used to summarize the audio recording.
</dd>
<dt>genre</dt>
<dd>
The category used to classify the audio recording.
</dd>
<dt>length</dt>
<dd>
The length of the audio recording in seconds.
</dd>
<dt>price</dt>
<dd>
The amount of currency that must be exchanged for acquisition of a full specimen of the audio recording.
</dd>
</dd>
</dl>
</pre>

== Examples ==
Here are a few examples of audio content from current web sites, and how they could be easily enhanced to support the hAudio audio metadata microformat.

Want to write valid [[haudio|hAudio]]? Use the [http://microformats.org/code/haudio/creator hAudio creator] (not implemented yet) to write about audio content and publish it on your blog.

=== Simple Song Example ===

Display:

Start Wearing Purple by Gogol Bordello

Microformatted XHTML:

<pre>
<div class="haudio">
<span class="work-title">Start Wearing Purple</span> by
<span class="collaborator hcard fn">Gogol Bordello</span>
</div>
</pre>

=== Speech Example ===

Display:

I Have a Dream, a speech by Martin Luther King Jr.

Microformatted XHTML:

<pre>
<div class="haudio">
<span class="work-title">I Have a Dream</span>, a
<span class="genre">speech</span> by
<span class="collaborator hcard fn">Martin Luther King Jr.</span>
</div>
</pre>

=== Audio Album Example ===

Display:

Black Horse and The Cherry Tree by KT Tunstall

# Black Horse & The Cherry Tree
# One Day [Live]

Microformatted XHTML:

<pre>
<div class="haudio grouping.ktsampler">
<span class="title">Black Horse and The Cherry Tree</span> by
<span class="collaborator hcard fn">KT Tunstall</span>
<ol class="xoxo">
<li>
<div class="haudio grouping.ktsampler.bh">
<span class="work-title">Black Horse & The Cherry Tree</span>
</div>
</li>
<li>
<div class="haudio grouping.ktsampler.od">
<span class="work-title">One Day [Live]</span>
</div>
</li>
</ol>
</div>
</pre>

=== Podcast Example ===

Display:

BBC Today Podcasts for Saturday, 28 April 2007.

* 8.10 Interview - Nottingham has become pivotal in the local elections.
** [http://downloads.bbc.co.uk/rmhttp/downloadtrial/radio4/today/today_20070428-0810_40_st.mp3 Download Now]
** [http://downloads.bbc.co.uk/rmhttp/downloadtrial/radio4/today/rss.xml Add to RSS]
* The Today Lead Interviews - The Today Programme morning briefing, ten to eight and half past eight interviews.
** [http://downloads.bbc.co.uk/rmhttp/downloadtrial/radio4/todayleadscombined/todayleadscombined_20070428-0900_40_st.mp3 Download Now]
** [http://downloads.bbc.co.uk/rmhttp/downloadtrial/radio4/today/rss.xml Add to RSS]
* BBC Radio NewsPod - Daily programme highlights from across BBC Radio News.
** [http://downloads.bbc.co.uk/rmhttp/downloadtrial/radionews/bbcradionewspod/bbcradionewspod_20070427-1800_40_st.mp3 Download Now]
** [http://downloads.bbc.co.uk/rmhttp/downloadtrial/radio4/today/rss.xml Add to RSS]

Microformatted XHTML:

<pre>
<div class="haudio grouping.today-podcast">
<span class="work-title">BBC Today Podcasts</span> for
<abbr class="release-date" title="20070428">Saturday, 28 April 2007</span>.
</div>

<ul>
<li>
<div class="haudio grouping.today-podcast.810-interview">
<span class="work-title">8.10 Interview</span> -
Nottingham has become pivotal in the local elections.
<ul>
<li><a rel="acquire" href="http://downloads.bbc...-0810_40_st.mp3">Download 8.10 Interview</a></li>
<li><a href="http://downloads.bbc...today/rss.xml">Add to RSS</a>
</ul>
</div>
</li>
<li>
<div class="haudio grouping.today-podcast.the-today-lead-interviews">
<span class="work-title">The Today Lead Interviews</span> -
The Today Programme morning briefing, ten to eight and half past eight interviews.
<ul>
<li><a rel="acquire" href="http://downloads.bbc...-0900_40_st.mp3">Download the Today Lead Interviews</a></li>
<li><a href="http://downloads.bbc...today/rss.xml">Add to RSS</a>
</ul>
</div>
</li>
<li>
<div class="haudio grouping.today-podcast.bbc-radio-newspod">
<span class="work-title">BBC Radio NewsPod</span> -
Daily programme highlights from across BBC Radio News.
<ul>
<li><a rel="acquire" href="http://downloads.bbc...-1800_40_st.mp3">Download BBC Radio NewsPod</a></li>
<li><a href="http://downloads.bbc...today/rss.xml">Add to RSS</a>
</ul>
</div>
</li>
</ul>
</pre>

=== Complex hAudio Example ===

'''NEED AN EXAMPLE'''

== Examples in the wild ==

This section is '''informative'''.

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

See [[haudio-implementations|hAudio Implementations]].

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

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

==== Similar Work ====
* [[media-info-examples]]
* [[media-info-formats]]
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===
This document and specification is distributed under a [http://creativecommons.org/licenses/by/3.0/ Creative Commons Attribution 3.0 license]. It is licensed and can be used royalty-free for any purpose.

The authors intend to submit this specification to a standards body with a liberal copyright/licensing policy such as the GMPG (http://gmpg.org/), IETF (http://ietf.org/), and/or W3C (http://w3.org). Anyone wishing to contribute should read each organizations copyright principles, policies and licenses (e.g. the GMPG Principles (http://gmpg.org/principles)) and agree to them, including licensing of all contributions under all required licenses (e.g. CC-by 1.0 (http://creativecommons.org/licenses/by/1.0/) and later), before contributing.

=== Patents ===

The authors of this Microformat have not and will not apply for patents covering any invention covering this Microformat in part or as a whole. There are no claims to any patent in this document. Each author is required to report any known patent issues immediately under this section.

This document and specification is distributed under a royalty free patent policy, e.g. per the W3C Patent Policy (http://www.w3.org/Consortium/Patent-Policy-20040205/), and IETF RFC3667 (http://www.ietf.org/rfc/rfc3667.txt) & RFC3668 (http://www.ietf.org/rfc/rfc3668.txt).

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

== Further Reading ==

==See also==
*[[audio-info-brainstorming]]
*[[audio-info-examples]]

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

accessibility

2007-05-02T00:57:10Z

JamesCraig: /* Advantages */ correcting WCAG1 link

<h1>Accessibility</h1>

This page documents microformats and accessibility in general, in particular advantages that adopting microformats provide for accessibility, and for documenting techniques for making microformats more accessible.

We should all strive to make our published microformats, parser implementations, and this wiki, accessible to all users, regardless of their physical abilities and needs, within the limits of the time and resources of the microformats community. Readers are advised to follow the [http://www.w3.org/TR/WCAG10/ W3C's Web Content Accessibility Guidelines 1.0], to at least level 2. Further advice is available on the [http://www.accessifyforum.com/ Accessify Forums].

__TOC__

==Advantages==
Some microformats have potential accessibility advantages.

===hCard===
*<code>tel</code> in [[hcard|hCard]]: use <code>style="speak-numeral:digits"</code>, so that telephone numbers are read by aural browsers as, for example, "five-five-five one-two-three-four" and not "five-hundred and fifty-five, one-thousand, two-hundred and thirty-two". ''Note: This is not an advantage to Microformats. It is a CSS best practice and can be used with or without hCard. This should probably be moved to a [[css-best-practices|CSS Best Practices]] page. - JamesCraig''

==Disadvantages==
Some microformats have potential accessibility disadvantages.

===abbr-design-pattern===
*As mentioned on external sites (see:[[accessibility-issues]]) and on the microformats-discuss list, the abbr-design-pattern (used in [[hcard|hCard]], [[hcalendar|hCalendar]], [[geo|GEO]] and others) is in violation of WCAG1 and WCAG2, and has potentially harmful accessibility side-effects of reading machine data to screen reader users rendering human content inaccessible.

===anchor-include-pattern===
*As mentioned on [[accessibility-issues]], the anchor-include-pattern is in violation of WCAG1 and WCAG2, and has potentially harmful accessibility side effects due to the missing link text.

==External testimonials==
* [http://lists.w3.org/Archives/Public/w3c-wai-ig/2006JulSep/subject.html#msg133 hCard and hCalendar Formats] - 2006-08-03 in w3c-wai-ig. e.g. <blockquote><p>I think Microformats.org is doing rather well on it's own, and it isn't particularly something that the W3C would or should get involved in until it's settled down. (And then it would just be a ratification kind of thing.)</p><p>...</p><p>In fact, it is likely to be good for accessibility, as the tools for consuming microformats often require valid code.</p></blockquote>

==See also==
*[[accessibility-issues]] - note external criticisms on the accesibility issues page
*[[internationalization]]
*[[assistive-technology]]

accessibility

2007-05-02T00:54:33Z

JamesCraig: /* Advantages */ noting this is off-topic

<h1>Accessibility</h1>

This page documents microformats and accessibility in general, in particular advantages that adopting microformats provide for accessibility, and for documenting techniques for making microformats more accessible.

We should all strive to make our published microformats, parser implementations, and this wiki, accessible to all users, regardless of their physical abilities and needs, within the limits of the time and resources of the microformats community. Readers are advised to follow the [http://www.w3.org/TR/WCAG10/full-checklist.html W3C's Web Content Accessibility Guidelines 1.0], to at least level 2. Further advice is available on the [http://www.accessifyforum.com/ Accessify Forums].

__TOC__

==Advantages==
Some microformats have potential accessibility advantages.

===hCard===
*<code>tel</code> in [[hcard|hCard]]: use <code>style="speak-numeral:digits"</code>, so that telephone numbers are read by aural browsers as, for example, "five-five-five one-two-three-four" and not "five-hundred and fifty-five, one-thousand, two-hundred and thirty-two". ''Note: This is not an advantage to Microformats. It is a CSS best practice and can be used with or without hCard. This should probably be moved to a [[css-best-practices|CSS Best Practices]] page. - JamesCraig''

==Disadvantages==
Some microformats have potential accessibility disadvantages.

===abbr-design-pattern===
*As mentioned on external sites (see:[[accessibility-issues]]) and on the microformats-discuss list, the abbr-design-pattern (used in [[hcard|hCard]], [[hcalendar|hCalendar]], [[geo|GEO]] and others) is in violation of WCAG1 and WCAG2, and has potentially harmful accessibility side-effects of reading machine data to screen reader users rendering human content inaccessible.

===anchor-include-pattern===
*As mentioned on [[accessibility-issues]], the anchor-include-pattern is in violation of WCAG1 and WCAG2, and has potentially harmful accessibility side effects due to the missing link text.

==External testimonials==
* [http://lists.w3.org/Archives/Public/w3c-wai-ig/2006JulSep/subject.html#msg133 hCard and hCalendar Formats] - 2006-08-03 in w3c-wai-ig. e.g. <blockquote><p>I think Microformats.org is doing rather well on it's own, and it isn't particularly something that the W3C would or should get involved in until it's settled down. (And then it would just be a ratification kind of thing.)</p><p>...</p><p>In fact, it is likely to be good for accessibility, as the tools for consuming microformats often require valid code.</p></blockquote>

==See also==
*[[accessibility-issues]] - note external criticisms on the accesibility issues page
*[[internationalization]]
*[[assistive-technology]]

accessibility

2007-05-02T00:50:55Z

JamesCraig: /* Disdvantages */ adding section

<h1>Accessibility</h1>

This page documents microformats and accessibility in general, in particular advantages that adopting microformats provide for accessibility, and for documenting techniques for making microformats more accessible.

We should all strive to make our published microformats, parser implementations, and this wiki, accessible to all users, regardless of their physical abilities and needs, within the limits of the time and resources of the microformats community. Readers are advised to follow the [http://www.w3.org/TR/WCAG10/full-checklist.html W3C's Web Content Accessibility Guidelines 1.0], to at least level 2. Further advice is available on the [http://www.accessifyforum.com/ Accessify Forums].

__TOC__

==Advantages==
Some microformats have potential accessibility advantages.

===hCard===
*<code>tel</code> in [[hcard|hCard]]: use <code>style="speak-numeral:digits"</code>, so that telephone numbers are read by aural browsers as, for example, "five-five-five one-two-three-four" and not "five-hundred and fifty-five, one-thousand, two-hundred and thirty-two".

==Disadvantages==
Some microformats have potential accessibility disadvantages.

===abbr-design-pattern===
*As mentioned on external sites (see:[[accessibility-issues]]) and on the microformats-discuss list, the abbr-design-pattern (used in [[hcard|hCard]], [[hcalendar|hCalendar]], [[geo|GEO]] and others) is in violation of WCAG1 and WCAG2, and has potentially harmful accessibility side-effects of reading machine data to screen reader users rendering human content inaccessible.

===anchor-include-pattern===
*As mentioned on [[accessibility-issues]], the anchor-include-pattern is in violation of WCAG1 and WCAG2, and has potentially harmful accessibility side effects due to the missing link text.

==External testimonials==
* [http://lists.w3.org/Archives/Public/w3c-wai-ig/2006JulSep/subject.html#msg133 hCard and hCalendar Formats] - 2006-08-03 in w3c-wai-ig. e.g. <blockquote><p>I think Microformats.org is doing rather well on it's own, and it isn't particularly something that the W3C would or should get involved in until it's settled down. (And then it would just be a ratification kind of thing.)</p><p>...</p><p>In fact, it is likely to be good for accessibility, as the tools for consuming microformats often require valid code.</p></blockquote>

==See also==
*[[accessibility-issues]] - note external criticisms on the accesibility issues page
*[[internationalization]]
*[[assistive-technology]]

accessibility-issues

2007-05-02T00:29:51Z

JamesCraig: /* abbr-design-pattern */ clarification

<h1>accessibility issues</h1>

These are externally raised issues about [[accessibility]] with broadly varying degrees of merit. Thus some issues may be 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 [[accessibility-faq|accessibility 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/ Tantek]

Please add new issues to the '''top''' of the list. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.

__TOC__

== Issues ==

*{{OpenIssue}} [http://lists.w3.org/Archives/Public/w3c-wai-ig/2006OctDec/0022.html 2006-10-06 raised by John Foliot in w3c-wai-ig]
*# ''<blockquote><p>What we don't need (IMHO) is a web where everything is simply a <div> with some extraneous Microformats style association added to it. </p></blockquote>''

*{{OpenIssue}} [http://www.accessifyforum.com/viewtopic.php?t=6167&postdays=0&postorder=asc&start=0 2006-09-20 raised by Andy Mabbett in accessifyforum]
*# ''Use of 'abbr' in microformats''

===hCalendar===
hCalendar specific accessibility issues. These are separated from the [[hcalendar-issues|hCalendar issues]] in general so that they are not lost among other non-accessibility related issues.

* {{OpenIssue}} 2007-01-20 raised by [[User:AndyMabbett|Andy Mabbett]]
*# ''Where <code>DTEND</code> is a date, and not a date-time, it is required to be the day after the end of the event, thus: <code><nowiki>
<abbr class="dtend" title="2007-04-30">29 April 2007</abbr></nowiki></code>. However, "29 April 2007" is '''''not''''' an abbreviation of 2007-04-30; it is an abbreviation of 2007-04-29. The markup as shown is semantically incorrect and likely to cause problems for users and user-agents which read the title attribute, and not the text value, of the <code>abbr</code> element.''

*{{OpenIssue}} 2006-12-11 raised by Andy Mabbett
*# ''The image in [[hcalendar-brainstorming#Photos and other attachments]] has inappropriate alt text, being just the file mname. [[User:AndyMabbett|Andy Mabbett]] 15:23, 6 Mar 2007 (PST)''

=== abbr-design-pattern ===
*{{OpenIssue}} 2007-04-27 raised by JamesCraig, BruceLawson.
*# ''Web Standards Project ATF article and discussion about why some instances of the [http://www.webstandards.org/2007/04/27/haccessibility/ abbr-design-pattern are bad for accessibility].'

=== include-design-pattern ===
*{{OpenIssue}} 2007-04-28 raised by [[User:PatrickLauke|PatrickLauke]]
*# although nominally empty, [http://microformats.org/wiki/include-pattern-feedback#Hyperlink_Include_-_issues_for_keyboard_users_.28including_Screen_Reader_users.29 hyperlink includes still present in tab cycle of major browsers], proving to be a problem for keyboard users (including users of screen readers)
*# [http://microformats.org/wiki/include-pattern-feedback#Test_Results:_JAWS_7.0_with_Firefox_1.5.2FWin JAWS 7.0] testing not conclusive to ascertain compatibility in other major screen readers.

===Accessibility of this wiki===
*{{OpenIssue}} 2006-11-26 raised by Andy Mabbett
*# ''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] [[User:AndyMabbett|Andy Mabbett]] 14:33, 26 Nov 2006 (PST)''

*{{OpenIssue}} 2006-12-11 raised by Andy Mabbett
*# ''[http://microformats.org/wiki?title=page-summary-formats&curid=2572&diff=0&oldid=11214&rcid=20591 Duplicating link text] breaches [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-meaningful-links WAI-WCAG 1 guideline 13.1 Clearly identify the target of each link] and is unhelpful to users of assistive technologies and other agents, which provide links in a stand-alone, out-of-context list. [[User:AndyMabbett|Andy Mabbett]] 10:29, 11 Dec 2006 (PST)''

== Template ==
Please use this format (copy and paste this to the beginning 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.''

== Resolved Issues ==
Issues that are resolved but may have outstanding [[to-do]] items.
* ...

== Closed Issues ==
Resolved issues that have no further actions to take.

*2006-11-26 raised by Andy Mabbett
*# ''Using emboldening and italics to differentiate types on, e.g. the cheatsheet pages [[hcard-cheatsheet]], is unhelpful to users of assistive technologies, text-only devices, etc. A number, letter or symbol should additionally be used. [[User:AndyMabbett|Andy Mabbett]] 14:33, 26 Nov 2006 (PST)''
*#*I think the emboldening is fine as it marks up the required properties. The italics are a bit of a problem but keep it simple at the moment. Additional characters can’t be used as they would break the class="property" template. Colours would be a way but are inaccessible to some users, so there is no real solution to that problem for now. [[User:JulianStahnke|Julian Stahnke]] 22:55, 26 Nov 2006 (GMT)
*#**"I think the emboldening is fine" - how would you understand emboldening in a text-only browser like Lynx, or in an aural browser? [[User:AndyMabbett|Andy Mabbett]] 15:17, 26 Nov 2006 (PST)
*#***Ups, I just assumed that it would use strong and em tags. Yeah, well, let’s think about it. [[User:JulianStahnke|Julian Stahnke]] 23:22, 26 Nov 2006 (GMT)
*#*Of course, one could add that stuff ''after'' the class="property" thing. That might look a little cluttered though. I’ll consider that for the next revision/next cheat sheet I do. [[User:JulianStahnke|Julian Stahnke]] 22:57, 26 Nov 2006 (GMT)
*#**All that's needed is:
::::<nowiki>* class="vcard" (1)</nowiki>
::instead of:
::::<nowiki>* class="vcard"</nowiki>
:::[[User:AndyMabbett|Andy Mabbett]] 15:24, 26 Nov 2006 (PST)
*#*'''Now resolved'''. Thanks to all who helped. [[User:AndyMabbett|Andy Mabbett]] 10:30, 11 Dec 2006 (PST)

== See Also ==
* [[accessibility]]
* [[microformats-issues]]

accessibility

2007-05-01T20:13:42Z

JamesCraig: /* External testimonials */ added ATF post

advocacy

2007-05-01T20:05:41Z

JamesCraig: /* Comparisons With Alternative Approaches */ removed non-neutral opinion statements

<h1> Advocacy </h1>

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

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

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

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

=== hCard ===
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')
* Alexa.com has online profiles for domains with contact information. Would be great if they could add hCard to those. 2007-04-18 [[User:Tantek]] requested of [[User:BenWest]] e.g.:
** http://www.alexa.com/data/details?url=alexa.com/
** http://www.alexa.com/data/details?url=w3.org/
* [http://sunlightlabs.com/api/ SunlightLabs API] provides profiles for US Congresspeople. Their [http://sunlightlabs.com/api/masterref/megatable.php megatable] could easily be marked up with hCard, and their APIs could return hCards and hCard fields.
** [[User:Tantek|Tantek]] 12:30, 20 Apr 2007 (PDT) contacted them and requested that they add hCard to megatable, consider a GethCard API method, and potentially a GethResume API method for each person.
** {{SuccessMarker}} [[User:CarlAnderson|CarlAnderson]] 26 Apr 2007: http://sunlightlabs.com/api does now have a people.getHCard.php API method to get an hCard for every member of congress. See the documentation at http://sunlightlabs.com/api/people.getHCard.php. An example call: http://api.sunlightlabs.com/people.getHCard.php?id=fakeopenID1
** {{SuccessMarker}} [[User:CarlAnderson|CarlAnderson]] 30 Apr 2007: I created a page of hCards for every member of congress: http://sunlightlabs.com/api/hcards/index.php

==== 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] [[User:AndyMabbett|Andy Mabbett]] 13:10, 28 Jan 2007 (PST)
* See also [[persondata|discussion of Wikipedia's Persondata]], which aligns very closely with hCard, but has additional date and place of birth & death fields. [[User:AndyMabbett|Andy Mabbett]] 13:23, 28 Mar 2007 (PDT)

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

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

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

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

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

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

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

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

====Other hCard====
* [http://www.imdb.com/ Internet Movie Database] (IMDb) for people (real, not characters), e.g. [http://www.imdb.com/name/nm0000007/ Humphrey Bogart]. [[User:AndyMabbett|Andy Mabbett]] 02:49, 13 Nov 2006 (PST)
**Can't find contact info! [[User:AndyMabbett|Andy Mabbett]]
*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.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://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:
*[http://meta.wikimedia.org/wiki/WikiGPS WikiGPS]
**Under development; notified of Geo microformat 2007-03-23
*Collections of waypoints
**See also [[geo-waypoint-examples]]
*Upcoming
**Some events, e.g. [http://upcoming.org/event/128155/ Multipack February 2007] are tagged thus: <code>geo:lat=52.4784</code>, <code>geo:lon=-1.9096</code>. This could be rendered as a geo microformat. [[User:AndyMabbett|Andy Mabbett]]
**Requested on (now defunct) Upcoming wiki 2007-01-14
**[http://suggestions.yahoo.com/detail/?prop=upcoming&fid=14362 Repeated on new suggestion board]. 2007-03-30. '''Please vote for this suggestion''' [[User:AndyMabbett|Andy Mabbett]]
*[http://www.census.gov/cgi-bin/gazetteer U.S. Gazetteer] e.g. [http://www.census.gov/cgi-bin/gazetteer?city=Birmingham&state=&zip=]
*[http://www.world-gazetteer.com/ World Gazetteer] e.g. [http://www.world-gazetteer.com/wg.php?x=&men=gpro&lng=en&dat=32&geo=-81&srt=npan&col=aohdq&pt=c&va=&geo=512945809]
**Requested by e-mail, 2007-01-20 [[User:AndyMabbett|Andy Mabbett]]
*[http://www.genuki.org.uk/cgi-bin/places GENUKI Gazetteer] (UK & Ireland) e.g. [http://www.genuki.org.uk/cgi-bin/maplink?CCC=STS,GR=SP040940,PLACE=Great%20Barr]
**Requested via feedback form, 2007-01-20 [[User:AndyMabbett|Andy Mabbett]]
*[http://www.confluence.org/ The Degree Confluence Project]
**Requested by e-mail, 2007-03-26 [[User:AndyMabbett|Andy Mabbett]]
*[http://www.wikimapia.org/ WikiMapia]
**Requested by e-mail, 2007-03-27 [[User:AndyMabbett|Andy Mabbett]]
**Replied to say they're looking into it. 2007-03-29
*[http://www.jeeep.com/details/coord/translate.cgi?datum=83&lat=52.57265&lon=-1.911433&detail=1 Jeeep.com]
**Requested by e-mail, 2007-03-27 [[User:AndyMabbett|Andy Mabbett]]
**Advertised address bouncing, 2007-03-27
*[http://www.flagr.com/ Flagr]
**Using, but not (yet) displaying, coordinates
**Requested by e-mail, 2007-03-30; also suggested they display their coordinates, and mark them up as tags [[User:AndyMabbett|Andy Mabbett]]
**Replied same day to say they will "talk it over internally"
* Various [http://en.wikipedia.org/wiki/Geocaching#Geocache_listing_sites Geocache listing sites]

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

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

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

===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]]
*W3C
**{{SuccessMarker}} '''W3C webmaster''' [http://www.w3.org/People/Jean-Gui/ Jean-Guilhem Rouel] now has an hCard. [[User:AndyMabbett|Andy Mabbett]] 15:41, 4 Apr 2007 (PDT)
*{{SuccessMarker}}Wikipedia-EN - starting to roll-out
**UK Railway station template, e.g. [http://en.wikipedia.org/wiki/Birmingham_New_Street Birmingham New Street station] (includes Geo)

=== hCalendar Successes===

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

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

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

==Rejections==

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

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

== Comparisons With Alternative Approaches ==

=== CalDAV ===

Kevin Marks spoke to Apple CalDAV developers about this, they have hCalendar support as a ticket in their database:
http://trac.macosforge.org/projects/calendarserver/ticket/19

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

assistive-technology-abbr-results

2007-05-01T19:58:48Z

JamesCraig: /* Rejected Data formats */ added test case proof

<h1>assistive technology abbr results</h1>
This page is for document the precise results of using [[assistive-technology]] with real world examples in the wild of the abbr design pattern, as nearly always used by [[hcalendar|hCalendar]] (e.g. dtstart, dtend), often by [[hreview|hReview]] (e.g. dtreviewed, rating) and sometimes by [[hcard|hCard]] (e.g. bday, type subproperty).

__TOC__

Each [[assistive-technology]] listed here MUST link to a precise description of the tool/service on the [[assistive-technology]] page, including version number, when published, etc.

Each test result listed for each assistive technology MUST link to the real world example that was tested.

== Test Cases ==
The [http://www.webstandards.org/action/atf/ WasP Accessibility Task Force] is working on a set of extended test cases that will cover the following data formats and markup formats. Please add to the list so we can create a comprehensive result set.

===Data Formats===
Please provide hyperlinks to examples in the wild for each case that is to be tested. Test cases with example in the wild URLs merit more testing than those without. However, the purpose of these test cases is to find the best solution, whether or not it is currently being used.
* ISO 8601 date with punctuation (YYYY-MM-DD)
* ISO 8601 datetime with punctuation (YYYY-MM-DDTHH:MM:SS)
* ISO 8601 datetime with punctuation and no seconds (YYYY-MM-DDTHH:MM)
* ISO 8601 UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SSZ)
* ISO 8601 pre-UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SS+HH:MM)
* ISO 8601 pre-UTC datetime with punctuation and no timezone minutes (YYYY-MM-DDTHH:MM:SS+HH)
* ISO 8601 post-UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SS-HH:MM)
* ISO 8601 post-UTC datetime with punctuation and no timezone minutes (YYYY-MM-DDTHH:MM:SS-HH)
* ISO 8601 pre-UTC datetime with punctuation but w/o timezone punctuation. ''The hypothesis is that something like "eleven o'clock plus oh seven hundred" may be more understandable than "eleven o'clock plus seven o'clock" (similarly for the hyphen, read as "dash").''
** pre-UTC (YYYY-MM-DDTHH:MM:SS+HHMM)
** post-UTC (YYYY-MM-DDTHH:MM:SS-HHMM)
* GEO Latitude/Longitude coordinates.

=== Rejected Data formats ===
Dates without punctuation as they have proved unusable. Proof is premise for [[http://www.webstandards.org/2007/04/27/haccessibility/ hAccessibility]] article on the Web Standards Project Buzz blog. Window Eyes and JAWS read un-punctuated dates as single number. [[http://www.webstandards.org/files/atf_microformats/jaws.mp3 JAWS 8 on IE7 citation (MP3 Audio)]] of "twenty million seventy-thousand three-hundred twelve" is reason enough for rejection.
* ISO 8601 date without dashes (YYYYMMDD)
* ISO 8601 datetime without dashes and colons (YYYYMMDDTHHMMSS)
* ISO 8601 datetime without dashes and colons and no seconds (YYYYMMDDTHHMM)
* ISO 8601 UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ)
* ISO 8601 pre-UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ+HHMM)
* ISO 8601 pre-UTC datetime without dashes and colons and no timezone minutes (YYYYMMDDTHHMMSSZ+HH)
* ISO 8601 post-UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ-HHMM)
* ISO 8601 post-UTC datetime without dashes and colons and no timezone minutes (YYYYMMDDTHHMMSSZ-HH)

===Markup Possibilities===
==== Valid HTML4 ====
* abbr-design-pattern (as currently recommended)
* Object with param value.
* Object with in-page data attribute.
* Span with title property.
* Nested spans with child title set to null.
* Nested abbr with child title set to null.

==== Invalid HTML4 ====
Markup possibilities that are invalid in HTML4/XHTML1 are noted here to be clear that they were considered and rejected. Since microformats build on [[posh]], any technique that is invalid semantic (X)HTML is unacceptable for a microformats solution. There is no need to bother testing these.
* Span with RDF dc:date attribute.
* Span with RDF geo:position attribute.

===Screenreader Language Pronunciations===
* English
* Spanish (need volunteer native Spanish speaker screen reader user)
* ?

===Verbosity settings===

* Punctuation, speak none.
* Punctuation, speak some.
* Punctuation, speak all.
* Title attributes, speak none.
* Title attributes, speak some (abbr and acronym).
* Title attributes, speak all.

===Screenreaders===
* Freedom Scientific JAWS (multiple versions TBD)
* GW Micro Window Eyes (multiple versions TBD)
* Apple Voiceover (multiple versions TBD)

== Results ==

To be determined.

== See Also ==
* [[accessibility]]
* [[assistive-technology]]

assistive-technology-abbr-results

2007-05-01T19:53:12Z

JamesCraig: /* Data Formats */ accepted timezone w/o punctuation format proposal

<h1>assistive technology abbr results</h1>
This page is for document the precise results of using [[assistive-technology]] with real world examples in the wild of the abbr design pattern, as nearly always used by [[hcalendar|hCalendar]] (e.g. dtstart, dtend), often by [[hreview|hReview]] (e.g. dtreviewed, rating) and sometimes by [[hcard|hCard]] (e.g. bday, type subproperty).

__TOC__

Each [[assistive-technology]] listed here MUST link to a precise description of the tool/service on the [[assistive-technology]] page, including version number, when published, etc.

Each test result listed for each assistive technology MUST link to the real world example that was tested.

== Test Cases ==
The [http://www.webstandards.org/action/atf/ WasP Accessibility Task Force] is working on a set of extended test cases that will cover the following data formats and markup formats. Please add to the list so we can create a comprehensive result set.

===Data Formats===
Please provide hyperlinks to examples in the wild for each case that is to be tested. Test cases with example in the wild URLs merit more testing than those without. However, the purpose of these test cases is to find the best solution, whether or not it is currently being used.
* ISO 8601 date with punctuation (YYYY-MM-DD)
* ISO 8601 datetime with punctuation (YYYY-MM-DDTHH:MM:SS)
* ISO 8601 datetime with punctuation and no seconds (YYYY-MM-DDTHH:MM)
* ISO 8601 UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SSZ)
* ISO 8601 pre-UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SS+HH:MM)
* ISO 8601 pre-UTC datetime with punctuation and no timezone minutes (YYYY-MM-DDTHH:MM:SS+HH)
* ISO 8601 post-UTC datetime with punctuation (YYYY-MM-DDTHH:MM:SS-HH:MM)
* ISO 8601 post-UTC datetime with punctuation and no timezone minutes (YYYY-MM-DDTHH:MM:SS-HH)
* ISO 8601 pre-UTC datetime with punctuation but w/o timezone punctuation. ''The hypothesis is that something like "eleven o'clock plus oh seven hundred" may be more understandable than "eleven o'clock plus seven o'clock" (similarly for the hyphen, read as "dash").''
** pre-UTC (YYYY-MM-DDTHH:MM:SS+HHMM)
** post-UTC (YYYY-MM-DDTHH:MM:SS-HHMM)
* GEO Latitude/Longitude coordinates.

=== Rejected Data formats ===
Dates without punctuation as they have "proved unusable" (please provide citation to tests and results).
* ISO 8601 date without dashes (YYYYMMDD)
* ISO 8601 datetime without dashes and colons (YYYYMMDDTHHMMSS)
* ISO 8601 datetime without dashes and colons and no seconds (YYYYMMDDTHHMM)
* ISO 8601 UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ)
* ISO 8601 pre-UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ+HHMM)
* ISO 8601 pre-UTC datetime without dashes and colons and no timezone minutes (YYYYMMDDTHHMMSSZ+HH)
* ISO 8601 post-UTC datetime without dashes and colons (YYYYMMDDTHHMMSSZ-HHMM)
* ISO 8601 post-UTC datetime without dashes and colons and no timezone minutes (YYYYMMDDTHHMMSSZ-HH)

===Markup Possibilities===
==== Valid HTML4 ====
* abbr-design-pattern (as currently recommended)
* Object with param value.
* Object with in-page data attribute.
* Span with title property.
* Nested spans with child title set to null.
* Nested abbr with child title set to null.

==== Invalid HTML4 ====
Markup possibilities that are invalid in HTML4/XHTML1 are noted here to be clear that they were considered and rejected. Since microformats build on [[posh]], any technique that is invalid semantic (X)HTML is unacceptable for a microformats solution. There is no need to bother testing these.
* Span with RDF dc:date attribute.
* Span with RDF geo:position attribute.

===Screenreader Language Pronunciations===
* English
* Spanish (need volunteer native Spanish speaker screen reader user)
* ?

===Verbosity settings===

* Punctuation, speak none.
* Punctuation, speak some.
* Punctuation, speak all.
* Title attributes, speak none.
* Title attributes, speak some (abbr and acronym).
* Title attributes, speak all.

===Screenreaders===
* Freedom Scientific JAWS (multiple versions TBD)
* GW Micro Window Eyes (multiple versions TBD)
* Apple Voiceover (multiple versions TBD)

== Results ==

To be determined.

== See Also ==
* [[accessibility]]
* [[assistive-technology]]

governance-issues

2007-05-01T19:28:14Z

JamesCraig: /* Abstract */ added voting/veto process

== Issue Summary 2007-02-28 ==
=== Editor ===
[http://www.opendarwin.org/~drernie/ Ernest Prabhakar]

=== Contributors ===
*[[User:AndyMabbett|Andy Mabbett]]
* Joe Andrieu
* Phae
* Ryan Cannon
* Colin Barrett
* ... Please add yourself.

== Preamble ==
Over the last year, a few people (AndyMabbett, JoeAndrieu, ErnestPrabhakar, JamesCraig) have raised issues about how the Microformats wiki, mailing list, and community are governed. This page is here to discuss ideas for documenting, formalizing, and/or improving our collective governance.

== Abstract ==
Governance has [http://www.phac-aspc.gc.ca/vs-sb/voluntarysector/glossary.html been defined] as "the traditions, institutions and processes that determine how power is exercised, how citizens are given a voice, and how decisions are made on issues of public concern." In the context of Microformats, it covers:
* Rules (both written and unwritten) expected of community members
* Formal process for change requests for known format problems (i.e. abbr-design-pattern) by voting, with leeway for admin vetoes.
* Who the various Admins are
* What powers Admins have
* Rules for how/when Admins can/should use those powers
* How to questioning/appealing a decision by an Admin
* How to become an Admin
* How to question/change any of these

While not all of these need to be explicitly spelled out, a healthy community our size requires a broad shared understanding of these facts -- as well as acceptance of them as "legitimate."

== Who Are Admins ==
* 2007-01-04 raised by [[User:DrErnie|DrErnie]] on [[microformats-issues]], before this page existed, and moved from there
*# ''As discussed in [http://microformats.org/discuss/mail/microformats-discuss/2007-January/008011.html], there exist various concerns about the lack of clarity regarding governance of the list, wiki, and the specifications themselves. While agree that there does need to be some form of strong leadership to preserve the integrity of the community, I agree with [http://microformats.org/discuss/mail/microformats-discuss/2007-January/008022.html Colin Barrett] when he said:''
:::"I think there should be bit more visible superstructure around just who is in this "cabal". It seems to me like the Editors/Authors of the various specs form the majority it of it, but perhaps that should be made a bit more apparent, and the "powers" of an editor (essentially, the ability to veto changes to the wiki, it seems) outlined a bit and some information about how to become an editor (AFIACT, make numerous, quality edits to the Wiki that the other editors approve of)."
:An entry has been added to the FAQ regarding [http://microformats.org/wiki/faq#Q:_Who_controls_microformats.3F Who controls microformats?].[[User:DrErnie|Dr. Ernie]] 08:48, 2 Feb 2007 (PST)

== Mailing List Unmoderation Discussion ==
Discussion from [[mailing-list-unmoderation]].

* 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)
* Agreed, Phae, Ernie is such a person and that is Tantek's point. But should one need to be a "friend of the court" to bring an action? That practice reinforces a culture of privilege that has historically proven antithetical to transparency and equality, both characteristics of good governance, IMO. It is great to see the powers-that-be responding to Ernie's request. It is also a bit frustrating that only those deemed meritorious by the peerage can call forth due process and that Andy's own efforts to speak on his behalf--referencing my previous request to do the same--were summarily dismissed by Tantek because they were "adversarial." Any robust governance should, IMO, work independent of privilege and be capable of addressing adversarial situations without arbitrary limits on the speech of those whose liberties are under challenge.--[[User:JoeAndrieu|JoeAndrieu]] 14:18, 19 Mar 2007 (PDT)
** Point taken and appreciated, but this is the first incident to come to this kind of a situation where someone else has felt the need to step in, and just happened to also involve someone that is felt to be a member of good standing. I'd like to hope that if another member of the community had felt a similar way and had chosen to bring it up, that it would also have been dealt with in this open manner (and I'm sure this incident will be brought up in the future). Hopefully this incident will be a good test case to better structure future interactions with administration. I can't personally comment on Andy's own appeals. [[User:Phae|Phae]] 14:45, 19 Mar 2007 (PDT)
**Agreed. The first efforts to work through a process like this are bound to be less than ideal. However, I'd like to get on the record two main points that appear problematic.
# [http://microformats.org/discuss/mail/microformats-discuss/2007-February/008490.html my previous request to do the same] was not, in fact, dealt with in this open manner. Rather it decayed into a defensive debate about governance generally, leaving poor Andy stuck in moderated censure. Perhaps I'm not the most diplomatic sort, but the issue on the table is not about me. It is about Andy's continuing moderation.
# The [[mailing-list-unmoderation|unmoderation wiki page]] for Andy is effectively a public hearing on Andy's standing and privileges in the community, especially with [http://microformats.org/discuss/mail/microformats-discuss/2007-March/009066.html Tantek's request] that no replies be sent to the email list on the topic. I find it particularly disturbing that Andy's efforts to contribute to that hearing have been [http://microformats.org/wiki?title=mailing-list-unmoderation&diff=14419&oldid=14416 repeatedly] [http://microformats.org/wiki?title=mailing-list-unmoderation&diff=14456&oldid=14454 dismissed] by Tantek (see the [http://microformats.org/wiki?title=mailing-list-unmoderation&action=history history] for a complete list). While It probably wasn't the best form for Andy to edit my comment directly, he should, IMO, have a way to voice his opinion on the matter. He's been threatened with a ban if he does so on the mailing list. Is there another venue that is more appropriate than the wiki page taking input and votes on his unmoderation?--[[User:JoeAndrieu|JoeAndrieu]] 20:19, 19 Mar 2007 (PDT)
* Shouldn't this point be moot? According to the terms of the moderation, it will be lifted "if he successfully sends only topical / positive / improving email to the lists for one week." Once the week passed, this moderation ought to have been lifted automatically, and should not require a vote, right? --[[User:RCanine|Ryan Cannon]]
** At least one message was rejected during that first week, thus moderation was left as is, with the attention of the admins etc. focused on other higher priority matters. Given the higher quality of messages *with* moderation (as compared to before), some have made the statement that moderation is "working" and thus should be kept. [[User:Tantek|Tantek]] 08:58, 22 Mar 2007 (PDT)
* I dislike moderation because I find it causes me to be hesitant with my own contributions in some cases. Since I don't often know how long a message has been queued its hard for me to judge if my reply would be helpful, or if the moderated poster has already moved along with the rest of the discussion so I err on the side of moving onto something else. doesn't hurt me, but I feel sometimes it might not help with the overall discussions depth or conclusion. . Thus, I think the burden should be heavy to continue moderation for any length of time without a decision to unmoderate or outright ban. [[User:ChrisCasciano|ChrisCasciano]] 11:40, 23 Mar 2007 (ET)

== Examples ==
''Note: This is not to take a position on whether or not any of these decisions were appropriate or inappropriate. Rather, the existence of these events demonstrates the need to document why and how such decisions were -- or should be -- made and/or appealed.''

* Labelling microformats schema discussions as [http://microformats.org/discuss/mail/microformats-discuss/2006-March/003551.html off-topic]
** Already covered by the [[microformats]] principles.
* Issue rejection [http://microformats.org/discuss/mail/microformats-discuss/2007-February/008864.html governance]
* Negative, PoV and derogatory edit summary content such as "[http://microformats.org/wiki?title=hcard-authoring&diff=13621&oldid=12276#Add_To_Address_Book_Links smelled of excessive political correctness worrying]" and "[http://microformats.org/wiki?title=to-do&curid=1110&diff=13989&oldid=13988&rcid=23801 removed non-productive comment]".
** Removal of negative content from the wiki is not a negative. The Admins use their best judgment.
*[[rejected-formats#Pavatar|listing of items as "rejected"]] when [http://microformats.org/discuss/mail/microformats-discuss/2007-January/008271.html requests for evidence of said rejection] reveal none.
** Not every email can be answered, nor should anyone expect them to be. In this case the rejection is in the mailing list archives.
* Despite an assurance that "all of the admins will be apropriately (sic) listed on the wiki page [http://microformats.org/discuss/mail/microformats-discuss/2007-February/008526.html]", the [http://microformats.org/wiki/faq#Q:_Who_controls_microformats.3F list given in FAQ] is prefaced with the qualifier "including".
** Reference for assurance? No such assurance should ever have been given.
* Removal of disputed edits / removal of negative content from the wiki
**[http://microformats.org/wiki?title=mailing-list-unmoderation&diff=next&oldid=14416 mailing-list-unmoderation (16:12, 19 Mar 2007)]
**[http://microformats.org/wiki?title=governance&curid=3084&diff=0&oldid=14390&rcid=24255 governance (12:50, 19 Mar 2007)]
** [http://microformats.org/wiki?title=governance-issues&diff=14401&oldid=14396 governance-issues (14:55, 19 Mar 2007)]
**[http://microformats.org/wiki?title=mailing-lists&curid=1297&diff=14391&oldid=14389&rcid=24254 mailing-lists (12:42, 19 Mar 2007)]

== Proposal ==

# Create a publicly-visible ''microformats-admin'' mailing list, for easily identifying and contacting all admins
# Document a forum/mechanism/process where individuals concerned about admin actions can legitimately raise their concerns, to ensure substantive issues are addressed
# Maintain a [[governance]] page that captures and describes
## the identity of current Admins
## how to contact them
## the process for becoming an Admin
## the specific kinds of behavior warranting Admin intervention
## how/when suspended/moderated individuals can return to "good standing"
## how to appeal an Admin decision/action

== Petition ==

We acknowledge that the microformats list and wiki is not a democracy, and that one of the key goals of microformats is to have as little process and structure as possible. However, at the same time we believe that the "dictatorship" needs to not merely ''be'', but ''be seen as'' "benevolent." This includes some minimal level of transparency and due process to ensure that there are legitimate ways for ordinary members to speak out if they feel (rightly or wrongly) that a particular administrative action was unwise or unfair. Whether that is similar to the '''[[#Proposal]]''' above, or a counter-proposal by the ''admin'' team, we believe that something is necessary.
:''Please add your vote here''
*+1 Ernest Prabhakar
*+1 Joe Andrieu
*+1 James Craig
*+1 Steve Robillard
*+1 Chris Messina

== Resources ==

* http://www.shirky.com/writings/group_enemy.html

governance-issues

2007-05-01T19:23:21Z

JamesCraig: /* Preamble */ added myself

== Issue Summary 2007-02-28 ==
=== Editor ===
[http://www.opendarwin.org/~drernie/ Ernest Prabhakar]

=== Contributors ===
*[[User:AndyMabbett|Andy Mabbett]]
* Joe Andrieu
* Phae
* Ryan Cannon
* Colin Barrett
* ... Please add yourself.

== Preamble ==
Over the last year, a few people (AndyMabbett, JoeAndrieu, ErnestPrabhakar, JamesCraig) have raised issues about how the Microformats wiki, mailing list, and community are governed. This page is here to discuss ideas for documenting, formalizing, and/or improving our collective governance.

== Abstract ==
Governance has [http://www.phac-aspc.gc.ca/vs-sb/voluntarysector/glossary.html been defined] as "the traditions, institutions and processes that determine how power is exercised, how citizens are given a voice, and how decisions are made on issues of public concern." In the context of Microformats, it covers:
* Rules (both written and unwritten) expected of community members
* Who the various Admins are
* What powers Admins have
* Rules for how/when Admins can/should use those powers
* How to questioning/appealing a decision by an Admin
* How to become an Admin
* How to question/change any of these

While not all of these need to be explicitly spelled out, a healthy community our size requires a broad shared understanding of these facts -- as well as acceptance of them as "legitimate."

== Who Are Admins ==
* 2007-01-04 raised by [[User:DrErnie|DrErnie]] on [[microformats-issues]], before this page existed, and moved from there
*# ''As discussed in [http://microformats.org/discuss/mail/microformats-discuss/2007-January/008011.html], there exist various concerns about the lack of clarity regarding governance of the list, wiki, and the specifications themselves. While agree that there does need to be some form of strong leadership to preserve the integrity of the community, I agree with [http://microformats.org/discuss/mail/microformats-discuss/2007-January/008022.html Colin Barrett] when he said:''
:::"I think there should be bit more visible superstructure around just who is in this "cabal". It seems to me like the Editors/Authors of the various specs form the majority it of it, but perhaps that should be made a bit more apparent, and the "powers" of an editor (essentially, the ability to veto changes to the wiki, it seems) outlined a bit and some information about how to become an editor (AFIACT, make numerous, quality edits to the Wiki that the other editors approve of)."
:An entry has been added to the FAQ regarding [http://microformats.org/wiki/faq#Q:_Who_controls_microformats.3F Who controls microformats?].[[User:DrErnie|Dr. Ernie]] 08:48, 2 Feb 2007 (PST)

== Mailing List Unmoderation Discussion ==
Discussion from [[mailing-list-unmoderation]].

* 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)
* Agreed, Phae, Ernie is such a person and that is Tantek's point. But should one need to be a "friend of the court" to bring an action? That practice reinforces a culture of privilege that has historically proven antithetical to transparency and equality, both characteristics of good governance, IMO. It is great to see the powers-that-be responding to Ernie's request. It is also a bit frustrating that only those deemed meritorious by the peerage can call forth due process and that Andy's own efforts to speak on his behalf--referencing my previous request to do the same--were summarily dismissed by Tantek because they were "adversarial." Any robust governance should, IMO, work independent of privilege and be capable of addressing adversarial situations without arbitrary limits on the speech of those whose liberties are under challenge.--[[User:JoeAndrieu|JoeAndrieu]] 14:18, 19 Mar 2007 (PDT)
** Point taken and appreciated, but this is the first incident to come to this kind of a situation where someone else has felt the need to step in, and just happened to also involve someone that is felt to be a member of good standing. I'd like to hope that if another member of the community had felt a similar way and had chosen to bring it up, that it would also have been dealt with in this open manner (and I'm sure this incident will be brought up in the future). Hopefully this incident will be a good test case to better structure future interactions with administration. I can't personally comment on Andy's own appeals. [[User:Phae|Phae]] 14:45, 19 Mar 2007 (PDT)
**Agreed. The first efforts to work through a process like this are bound to be less than ideal. However, I'd like to get on the record two main points that appear problematic.
# [http://microformats.org/discuss/mail/microformats-discuss/2007-February/008490.html my previous request to do the same] was not, in fact, dealt with in this open manner. Rather it decayed into a defensive debate about governance generally, leaving poor Andy stuck in moderated censure. Perhaps I'm not the most diplomatic sort, but the issue on the table is not about me. It is about Andy's continuing moderation.
# The [[mailing-list-unmoderation|unmoderation wiki page]] for Andy is effectively a public hearing on Andy's standing and privileges in the community, especially with [http://microformats.org/discuss/mail/microformats-discuss/2007-March/009066.html Tantek's request] that no replies be sent to the email list on the topic. I find it particularly disturbing that Andy's efforts to contribute to that hearing have been [http://microformats.org/wiki?title=mailing-list-unmoderation&diff=14419&oldid=14416 repeatedly] [http://microformats.org/wiki?title=mailing-list-unmoderation&diff=14456&oldid=14454 dismissed] by Tantek (see the [http://microformats.org/wiki?title=mailing-list-unmoderation&action=history history] for a complete list). While It probably wasn't the best form for Andy to edit my comment directly, he should, IMO, have a way to voice his opinion on the matter. He's been threatened with a ban if he does so on the mailing list. Is there another venue that is more appropriate than the wiki page taking input and votes on his unmoderation?--[[User:JoeAndrieu|JoeAndrieu]] 20:19, 19 Mar 2007 (PDT)
* Shouldn't this point be moot? According to the terms of the moderation, it will be lifted "if he successfully sends only topical / positive / improving email to the lists for one week." Once the week passed, this moderation ought to have been lifted automatically, and should not require a vote, right? --[[User:RCanine|Ryan Cannon]]
** At least one message was rejected during that first week, thus moderation was left as is, with the attention of the admins etc. focused on other higher priority matters. Given the higher quality of messages *with* moderation (as compared to before), some have made the statement that moderation is "working" and thus should be kept. [[User:Tantek|Tantek]] 08:58, 22 Mar 2007 (PDT)
* I dislike moderation because I find it causes me to be hesitant with my own contributions in some cases. Since I don't often know how long a message has been queued its hard for me to judge if my reply would be helpful, or if the moderated poster has already moved along with the rest of the discussion so I err on the side of moving onto something else. doesn't hurt me, but I feel sometimes it might not help with the overall discussions depth or conclusion. . Thus, I think the burden should be heavy to continue moderation for any length of time without a decision to unmoderate or outright ban. [[User:ChrisCasciano|ChrisCasciano]] 11:40, 23 Mar 2007 (ET)

== Examples ==
''Note: This is not to take a position on whether or not any of these decisions were appropriate or inappropriate. Rather, the existence of these events demonstrates the need to document why and how such decisions were -- or should be -- made and/or appealed.''

* Labelling microformats schema discussions as [http://microformats.org/discuss/mail/microformats-discuss/2006-March/003551.html off-topic]
** Already covered by the [[microformats]] principles.
* Issue rejection [http://microformats.org/discuss/mail/microformats-discuss/2007-February/008864.html governance]
* Negative, PoV and derogatory edit summary content such as "[http://microformats.org/wiki?title=hcard-authoring&diff=13621&oldid=12276#Add_To_Address_Book_Links smelled of excessive political correctness worrying]" and "[http://microformats.org/wiki?title=to-do&curid=1110&diff=13989&oldid=13988&rcid=23801 removed non-productive comment]".
** Removal of negative content from the wiki is not a negative. The Admins use their best judgment.
*[[rejected-formats#Pavatar|listing of items as "rejected"]] when [http://microformats.org/discuss/mail/microformats-discuss/2007-January/008271.html requests for evidence of said rejection] reveal none.
** Not every email can be answered, nor should anyone expect them to be. In this case the rejection is in the mailing list archives.
* Despite an assurance that "all of the admins will be apropriately (sic) listed on the wiki page [http://microformats.org/discuss/mail/microformats-discuss/2007-February/008526.html]", the [http://microformats.org/wiki/faq#Q:_Who_controls_microformats.3F list given in FAQ] is prefaced with the qualifier "including".
** Reference for assurance? No such assurance should ever have been given.
* Removal of disputed edits / removal of negative content from the wiki
**[http://microformats.org/wiki?title=mailing-list-unmoderation&diff=next&oldid=14416 mailing-list-unmoderation (16:12, 19 Mar 2007)]
**[http://microformats.org/wiki?title=governance&curid=3084&diff=0&oldid=14390&rcid=24255 governance (12:50, 19 Mar 2007)]
** [http://microformats.org/wiki?title=governance-issues&diff=14401&oldid=14396 governance-issues (14:55, 19 Mar 2007)]
**[http://microformats.org/wiki?title=mailing-lists&curid=1297&diff=14391&oldid=14389&rcid=24254 mailing-lists (12:42, 19 Mar 2007)]

== Proposal ==

# Create a publicly-visible ''microformats-admin'' mailing list, for easily identifying and contacting all admins
# Document a forum/mechanism/process where individuals concerned about admin actions can legitimately raise their concerns, to ensure substantive issues are addressed
# Maintain a [[governance]] page that captures and describes
## the identity of current Admins
## how to contact them
## the process for becoming an Admin
## the specific kinds of behavior warranting Admin intervention
## how/when suspended/moderated individuals can return to "good standing"
## how to appeal an Admin decision/action

== Petition ==

We acknowledge that the microformats list and wiki is not a democracy, and that one of the key goals of microformats is to have as little process and structure as possible. However, at the same time we believe that the "dictatorship" needs to not merely ''be'', but ''be seen as'' "benevolent." This includes some minimal level of transparency and due process to ensure that there are legitimate ways for ordinary members to speak out if they feel (rightly or wrongly) that a particular administrative action was unwise or unfair. Whether that is similar to the '''[[#Proposal]]''' above, or a counter-proposal by the ''admin'' team, we believe that something is necessary.
:''Please add your vote here''
*+1 Ernest Prabhakar
*+1 Joe Andrieu
*+1 James Craig
*+1 Steve Robillard
*+1 Chris Messina

== Resources ==

* http://www.shirky.com/writings/group_enemy.html

assistive-technology-abbr-results

2007-05-01T16:23:50Z

JamesCraig: /* Data Formats */ removing dates w/o punctuation as they have proved unusable before. Limiting test cases to viable options.

assistive-technology-abbr-results

2007-04-30T04:41:24Z

JamesCraig: /* Data Formats */ clarifying prioritization

assistive-technology-abbr-results

2007-04-30T00:00:36Z

JamesCraig: /* Markup Possibilities */ added geo:position

assistive-technology-abbr-results

2007-04-29T23:01:21Z

JamesCraig: /* Verbosity settings */ Add section

assistive-technology-abbr-results

2007-04-29T22:45:19Z

JamesCraig: /* Test Cases */ updated ATF link and added Screenreaders section