Microformats Wiki - User contributions [en]

value-class-pattern-brainstorming

2010-04-07T08:21:56Z

Spiritquest: /* feedback */ added support to the brainstorm / proposal

<entry-title>value excerption pattern brainstorming</entry-title>

''The [[value-excerption-pattern]] is derived from [[hCard#Value_excerpting|value-excerpting]] in hCard. The precise parsing behavior is not yet finalized, so the pattern should be used only with extreme caution.''

This brainstorming page is for exploring ideas related to specifying the value-excerption-pattern in more detail and ideas for special case handling of the value-excerption-pattern in combination with specific [[semantic HTML]] elements per those elements' particular semantics.

These are merely explorations for now, and should NOT be used in actual content publishing, nor implemented in any production code.

== details for handling specific elements ==
None currently.

== details for handling specific property types ==

=== duration ===
[[hCalendar]] has a duration property which takes the [http://en.wikipedia.org/wiki/ISO_8601#Durations ISO8601 duration format].

[[hAudio]] also has a duration property, based on the hCalendar property.

In both cases, the [[abbr-design-pattern]] is often used to move the less human friendly ISO8601 duration (e.g. "PT1H30M") into the title attribute, while displaying more human friendly text (e.g. "1hr 30mins"). Based on real world example:

<source lang=html4strict>
<abbr class="duration" title="PT1H30M">1hr 30mins</abbr>
</source>

http://www.stereoartist.com/sfl09/hcal1.html

Unfortunately the text "PT1H30M" is not very human-readable (e.g. in a tooltip) or listenable (e.g. when read by a screen reader), thus it probably shouldn't be in the title attribute.

In hAudio, durations of songs and albums more often provide minutes and seconds (see "length" in [[audio-info-examples]]), e.g. "2:46" meaning 2 minutes, 46 seconds.

==== ISO8601 alternate duration format ====
ISO8601 has the following alternate duration format:

* P[YYYY]-[MM]-[DD]T[hh]:[mm]:[ss]

Thus the example above:

<pre><code>PT1H30M</code></pre>

could instead be represented as

<pre><code>PT1:30:00</code></pre>

which is a bit more readable, and yet still likely to be confusing due to the "PT" prefix.

==== hours minutes seconds ====
Given the common use cases from hCalendar of hours and minutes, and from hAudio of minutes and seconds it makes sense to take the ISO8601 alternate duration format and simply permit it without the "PT" prefix, e.g.

<source lang=html4strict>
<span class="duration">
<abbr class="value" title="1:30:00">1hr 30mins</abbr>
</span>
</source>

'''Advantages.''' This new title attribute value has the advantages of
* more human readable. "1:30:00" is more human readable than "PT1:30:00" and certainly than "PT1H30M".
* more international. "1:30:00" is more internationally understandable than even the included text from the example of "1hr 30mins".

Thus the author could instead provide the following:

<source lang=html4strict>
<span class="duration">
<abbr class="value" title="1:30:00">1:30</abbr>
</span>
</source>

Where the more visible text "1:30" is understand by humans from the context of the site (a list of films) to be in the units of hours and minutes.

Thus the proposal would be to add a section to [[value-class-pattern]] accordingly (with heading levels adjusted accordingly)

===== Duration values =====

====== Summary ======
Some microformats properties expect an ISO8601 duration value, e.g. [[hCalendar]] and [[hAudio]]'s <code>duration</code> property.

Authors may use the value class pattern to specify duration in more human friendly format.

Example, this hCalendar 'duration' property with 'value' element:

<source lang=html4strict>
<p>The dinner will be
<span class="duration">
<abbr class="value" title="1:30:00">an hour and 30 minutes long</abbr>
</span>
</p>
</source>

produces the following 'duration' value:

<source lang=text>
1:30:00
</source>

and iCalendar converters produce the following DURATION:

<source lang=text>
DURATION:PT1H30M
</source>

====== Duration parsing ======
For all duration properties (as defined in their respective microformats specifications), the following rules apply in addition to (and in some cases replacing) the above value class pattern parsing rules.

When a "value" element is found, parse a value from the element as follows:
* if the element is an <code>img</code> or <code>area</code> element, then use the element's <code>alt</code> attribute value.
* if the element is an <code>abbr</code> element, then use the element's <code>title</code> attribute value.
* for any other element, use its inner-text.
* if the value has an hours minutes seconds duration, specifically, fits any of the following:
** HH:MM:SS
** :MM:SS
** HH is the optional number of "hours" in the duration. if omitted, infer 0.
** MM are the minutes from 00 to 59
** SS are the seconds from 00 to 59 (60 for a leap second).
** For the purposes of the value class pattern, the colons ":" separating the hour, minutes, seconds are required.
** ignore any further "value" elements that specify the duration.

====== format specific details ======
The following are format specific details and <span id="format_specific_optimizations">optimizations</span> that make use of the value-class-pattern.

====== iCalendar generators ======
microformats implementations which consume [[hCalendar]] and generate iCalendar {{must}} in addition:
# convert the duration to ISO8601 duration format

===== duration property incorporation =====
If this brainstorm proposal is accepted for the value class pattern, it would be even better if it was permitted directly on the "duration" property and incorporated as such into [[hCalendar]] (i.e. into v1.0.1), [[hAudio]], and any other microformats specifications that have a "duration" property ([[hRecipe]]?).

[[User:Tantek|Tantek]] 02:12, 7 April 2010 (UTC)

===== feedback =====
Please indicate your support/ambivalence/disapproval of this proposal with a +1/0/-1 followed by your name (use "<nowiki>~~~~</nowiki>") and optionally reasons for your opinion.

* +1 [[User:Tantek|Tantek]] 02:19, 7 April 2010 (UTC) (obviously, as the author :)
* +1 [[User:Spiritquest|Ketan]] [[User:Spiritquest|spiritquest]] 08:21, 7 April 2010 (UTC) (Quizzed Tantek about its use and the proposals above make sense.)

Please feel free to provide additional input as well!

* ...

Thanks, [[User:Tantek|Tantek]]

== Condensed <code>value-title</code> ==

It has been proposed that the [[value-class-pattern]] could be made less verbose by allowing the <code>value-title</code> element to be included on the same element as the property declaration. For example:

Currently, you can write this:

<source lang='html4strict'>
<p class='dtstart'><span class='value-title' title='2009-06-21'>Sunday</span></p>
</source>

Condensing would enable this:

<source lang='html4strict'>
<p class='dtstart value-title' title='2009-06-21'>Sunday</p>
</source>

It could also allow for non-visible data to be published less verbosely. e.g. in hReview:

<source lang='html4strict'>
<span class='best value-title' title='10'></span>
</source>

===Advantages===

<div class='discussion'>
* Publish less code.
* Answers unverified claims that element nesting confuses authors. Examples needed.
</div>

===Disadvantages===

<div class='discussion issues'>
* Adds an additional variant to a syntax, raising the barrier to entry and risking author confusion when different documentation uses different syntax. --[[User:BenWard|BenWard]] 02:38, 22 June 2009 (UTC)
</div>

==Implied <code>value-title</code>==

In some situations of using the value-title pattern to publish non-visible data (such as an implied <code>best</code> rating in [[hReview]], mark-up could be reduced. E.g rather than:

<source lang='html4strict'>
<span class='best'><span class='value-title' title='10'></span></span>
</source>

Optimize to:

<source lang='html4strict'>
<span class='best' title='10'></span>
</source>

There is no need to explicitly mention the <code>value-title</code>, instead it is implied by the element itself being empty (or containing a single collapsable white-space character).

===Advantages===

<div class=discussion>
* Publish less code.
* Answers unverified claims that element nesting confuses authors. Examples needed.
</div>

===Disadvantages===

<div class='discussion issues'>
* Adds an additional variant to a syntax, raising the barrier to entry and risking author confusion when different documentation uses different syntax. --[[User:BenWard|BenWard]] 02:38, 22 June 2009 (UTC)
* Is it more confusing to see this sort of optimization (which will only apply to certain properties) without an explicit class-name? The presence of <code>value-title</code> provides some self-documentation to the code. --[[User:BenWard|BenWard]] 02:38, 22 June 2009 (UTC)
</div>

== Accepted ==
The following brainstorm proposals have been accepted are written up more formally on the [[value-class-pattern]] page. They are included here merely for historical reference.

=== date and time separation ===
==== summary ====
By specifying a more precise parsing of the use of "value" excerption inside all datetime properties (e.g. dtstart, dtend, published, updated etc.), dates and times can be marked up separately, thus reducing/minimizing (and potentially eliminating) the readability issues that come with compound ISO8601 datetimes.

==== introductory example ====
The sentence:

<pre><nowiki>
The weekly dinner is tonight at 6:30pm.
</nowiki></pre>

would be marked up as:

<pre><nowiki>
The weekly dinner is <span class="dtstart"><abbr class="value" title="2008-06-24">tonight</abbr>
at <abbr class="value" title="18:30">6:30pm</abbr></span>.
</nowiki></pre>

==== advantages ====
* re-uses the readable [[abbr-date-pattern]]
* identifies a similarly readable abbr-time-pattern.
* minimizes DRY violation distance, keeps machine data on exactly the same element as the respective human data
** even better than [[abbr-datetime-pattern]] does, which, in practice from experience often required specifying the date in machine readable form on the human readable time (separate from the human readable date).
* introduces no new class names - [[principle]] of minimal invention
* introduces no new use of the class attribute - principle of minimal invention again
* introduces no new syntax ([[datetime-design-pattern#problems_with_strtime_proposal|see above]] about any publishing method that requires the author to think like a programmer being a non-starter, and introducing new syntax almost always requires authors to think like programmers).
* and most importantly, introduces no dark data.

==== issues ====
Some potential issues were raised in IRC, and it helps to document/resolve them so that they are not brought up repeatedly.
<div class="discussion issues">
* [http://rbach.priv.at/Microformats/IRC/2008-06-24#T163114 Does this sufficiently address the concerns raised with the current use of abbr-pattern?]
*# The [[abbr-date-pattern]], as documented and explained by [[User:Adactio|Jeremy Keith]] is just fine (in contrast to the [[abbr-datetime-pattern]]).
*# Similar to the [[abbr-date-pattern]], this proposal implies/introduces the abbr-time-pattern, which is similarly acceptable.
*# In addition, as long there is incremental improvement, we are making progress. It is more important to take small steps that we know will help some things, rather than try to take a big step that is more risky in the attempt to help more but may not actually do so (as most big changes don't), therefore "sufficiently" is a flawed way of evaluating incremental fixes.
* Exposes data through tooltips. Separating into 2008-06-07 and 18:03 improves the ability for humans to consume the data, but still exposes data through tooltips and speech in formats that the publisher did not choose to use. --[[User:BenWard|BenWard]] 04:52, 25 Jun 2008 (PDT)
*# This is a feature, not a bug. By making the duplicated data at least *somewhat* visible (rather than fully invisible), effective data quality is increased due to the fact that the probability of the ISO8601 and locale-specific data getting out-of-sync is reduced because of the increased visibility (and therefore the increased inspectability and more eye-balls looking at/for problems effect).
*# Workaround: if a site publisher wishes to customize the presentation of tooltips, they can do so with a nested span with title.
*#* That proposes extraneous mark-up maintain some publisher's wish not to have a tool-tip in the first place. I object to a microformat pattern requiring an immediate work-around to meet publisher's desires. It goes against ‘Humans first…’. --[[User:BenWard|BenWard]] 09:09, 30 Jun 2008 (PDT)
*#*# Additional markup has nothing to do with "Humans first".
*#*# Additional markup to work-around minor issues (e.g. CSS, cross-browser compatibility, etc.) is a well accepted modern web design practice. It's not ideal, but it is both accepted and widely practiced. With the use of <code><span></code> and <code><div></code> elements, it's also semantically neutral, therefore not a problem from that perspective either.
*#*# Finally, it should not be our goal to try to satisfy *every* publisher, for that would make every microformat beholden to every publisher and contort the design of microformats in really poor ways. We must accept that not all publishers will adopt all microformats and that is ok. Our goal to incrementally increase the number of publishers that adopt microformats, not to try to satisfy each and every one.
*#* You *have* to have a tooltip though. It’s not possible to *not* have a tooltip. Not great.--[[User:JulianStahnke|Julian Stahnke]] 12:58, 4 Sep 2008 (BST)
*#** If it is a requirement for the publisher that no tooltip whatsoever be displayed, then the publisher should consider using [[value-class-pattern#Using_value-title_to_publish_machine-data|value-title]] to publish the data in an empty first-child span as specified in the [[value-class-pattern#Using_value-title_to_publish_machine-data|value-title pattern]].
* Semantic misuses of ABBR. That ‘tonight’ is ever a textual, human abbreviation of ‘2008-06-24’ is not accepted.
*# Semantic stretch not misuse. It is a semantic abbreviation rather than a purely syntactical (character shortening) abbreviation, but it is an abbreviation in context nonetheless. Though this may stretch what may be commonly expected as an "abbreviation", the HTML4 spec does seem to allow some flexibility here ([http://www.w3.org/TR/html401/struct/text.html#h-9.2.1 HTML 4.01 9.2.1 Phrase elements]).
* Maintaining proper sentences with the expanded form. It is not always possible to use this mark-up and maintain proper sentences with the expanded form. e.g. <code>it's my <abbr class="bday" title="2005-06-20">birthday today</abbr>!</code> becomes ‘it's my 2005-06-20!’. And thus audio rendition of such titles can be nonsensical - "The weekly dinner is two thousand and eight dash zero six dash twenty four at eighteen thirty."
*# In some cases this can be addressed by improving authoring examples, and helping practices improve with experience.
*# Alternatively, for cases like these, the [[value-class-pattern#Using_value-title_to_publish_machine-data|value-title pattern]] can be used to include the precise ISO8601 date or datetime immediately adjacent to the informal date or datetime reference like "today" or "tonight".
* Publishing practices and desires show us that authors are not willing to compromise the semantics of abbr. [[User:Phae|Phae]] 04:30, 27 Jun 2008 (PDT)
*# Without specific citations of which authors and what specific issues they have, we are unable to address their issues.
*# See also above - not our goal to satisfy *every* publisher, but rather to incrementally satisfy more and more. We must accept that there may be some authors we are unable to satisfy in the immediate/short-term.
* [http://rbach.priv.at/Microformats/IRC/2008-06-24#T163435 That's getting pretty complicated]
** Much less complicated than inventing yet another syntax ( " { ... } " ???? ) that web authors would have to learn.
*** But it's all in one place, rather than spreading it out.
**** The spreading it out is what current content publishing practices do already! It is much more important to map the machine data as close to the existing publishing practice as possible, than to try to "put it all in one place". The "put it all in one place" way of thinking is why people ended up sticking so much invisible metadata in the head of the document, which we know fails.
</div>

==== content requirements ====
Some requirements which enhance both human readability, ''and'' machine parsability (best of both) :
* date value excerpts MUST use hyphen separators. E.g. 2008-06-24. Not ok:20080624.
* time value excerpts MUST use colon separators (seconds optional, implied :00 if absent). E.g. 18:30 or 18:30:00. Not ok:183000.
* timezone value excerpts MUST use leading plus or minus and NO colon separator. E.g. -0700. Not ok:-07:00.

==== derivation ====
It's important to document the derivation/background of a brainstorm/proposal as it allows others to see some of the thinking that went into it, and avoid having to rediscuss alternatives already considered, and helps provide understanding as to why aspects of the design are as they are.
===== example with datetime =====
Here is a short code example:
<pre><nowiki>
the weekly dinner is tonight at <span class="dtstart">2008-06-24T18:30</span>
</nowiki></pre>
===== example with abbr datetime =====
However that's not the easiest to read, nor do most people publish that as human visible text, so per the abbr-datetime pattern:
<pre><nowiki>
the weekly dinner is tonight at <abbr class="dtstart" title="2008-06-24T18:30">6:30pm</abbr>
</nowiki></pre>

which has raised two issues:
# When "2008-06-24T18:30" is inspected by a human reading a tooltip, or spoken by a screen reader, it's not the most understandable thing (precise citation needed, perhaps an mp3 with screen reader used version info).
# There is a non-local violation of DRY (which IMHO is a worse problem, as it leads to worse data quality -[[User:Tantek|Tantek]]). That is, the "date" information is now not only in the text twice (as it was before), but those two instances of the date information are not on the same element, which makes it worse. That is, "tonight" is in the prose, ''outside'' of the element with the precise date "2008-06-24".

In analysis of examples of event information on the web, the date and time are often published in separate elements, often for display purposes.

Thus it is this existing content publishing practice which leads to this brainstorm proposal, to essentially to introduce a date and time value excerption longhand.

(Initially [http://rbach.priv.at/Microformats/IRC/2008-06-21#T181634 Tantek's idea that he bounced off Jeremy Keith] ([http://rbach.priv.at/Microformats/IRC/2008-06-24#T124652 similar idea conceived by Drew independently]) was to [http://rbach.priv.at/Microformats/IRC/2008-06-24#T161819 introduce new classes "datevalue", "timevalue"] and "tzvalue" for this purpose, but [http://rbach.priv.at/Microformats/IRC/2008-06-24#T171603 Bob Jonkman pointed out] that HTML5's time parsing algorithm enables a single <nowiki><time></nowiki> element to contain dates or times (with or without timezone) without having to explicitly say whether the value contains dates or times (with or without timezone). [http://rbach.priv.at/Microformats/IRC/2008-06-24#T171723 Bob then proposed] that thus all was needed was a single new "datetime" class name. This was the key realization that allowed minimal invention. Tantek pointed out that since from the type of property we already know it is a datetime, [http://rbach.priv.at/Microformats/IRC/2008-06-24#T171835 there was no need for even one new class name], that we could simply re-use "value" excerption, and simply more precisely specify the semantics/parsing in the case of datetime properties.)

===== example with new date and time value excerpts =====
Thus we markup the date and time separately, as value excerpts, using the [[abbr-date-pattern]] and an implied parallel abbr-time-pattern:

<pre><nowiki>
The weekly dinner is <span class="dtstart"><abbr class="value" title="2008-06-24">tonight</abbr>
at <abbr class="value" title="18:30">6:30pm</abbr></span>.
</nowiki></pre>

===== separate subtrees =====
The proposal also allows setting the date and time in separate element subtrees as well, which may be necessary for some document structures:

<pre><nowiki>
the weekly dinner is <span class="dtstart"><abbr class="value" title="2008-06-24">tonight</abbr></span>
at <span class="dtstart"><abbr class="value" title="18:30">6:30pm</abbr></span>.
</nowiki></pre>

Note the two instances of dtstart, one of which sets the date for the dtstart, and the other of which sets the time.

The idea being, when a parser sees a datetime property (e.g. dtstart) with a value excerpt, that it only "set" the component of its full value that is specified by the value excerpt (e.g. the date), and that if lacking a complete datetime, it continue to parse additional instances of that datetime property for the remaining component(s) (e.g. the time).

Of course this only works for singular properties, but fortunately all instances of datetime properties so far are singular, so this works.

issue:
<div class="discussion">
* hCard's <code>rev</code> is plural. [[User:TobyInk|TobyInk]]
** can someone give a reference to this being the case? The RFC says "The value distinguishes the current revision of the information in this vCard for other renditions of the information." Does it make sense to have multiple REV dates in a single vCard?
*** The RFC is ambiguous as usual, but a contact card could conceivably have had several changes made to it, with a <code>rev</code> for each. ("Change logs" are fairly common on the web.) The [[hcard|hCard spec]] is fairly specific about which properties are [[hcard#Singular_vs._Plural_Properties|singular]] and which are not, and <code>rev</code> is not included in the list of singular properties.
**** ACCEPTED RESOLVED. The RFC states <blockquote><p>Type name: REV</p><p>Type purpose: To specify revision information about the current vCard.</p></blockquote> which thus implies the REV property applies to the entire vCard, not just portions thereof. I've updated the [[hcard#Singular_vs._Plural_Properties|hCard singular properties accordingly]], and note that the [[hcard-singular-properties#rev|explanation for why rev is singular]] was already updated - just added that same RFC text as quoted above. [[User:Tantek|Tantek]] 00:36, 2 May 2009 (UTC)
</div>

===== reusing date data for multiple datetime properties =====
This also provides a *very* convenient way to re-use the same date information for start and end, e.g. expanding the example:

<pre><nowiki>
the weekly dinner is <span class="dtstart dtend"><abbr class="value" title="2008-06-24">tonight</abbr></span>
from <span class="dtstart"><abbr class="value" title="18:30">6:30</abbr></span> -
<span class="dtend"><abbr class="value" title="20:30">8:30pm</abbr></span>.
</nowiki></pre>

Note what just happened. we just eliminated another duplication of date information by reusing the start *date* information for the end *date* information and *only* specifying the end *time* information separately for the two properties.

Reducing the duplication (or triplication) of such data helps to reduce the chances of (even inadvertent) data corruption/drift/divergence among any duplicates.

===== time zones =====
There are a few choices for timezones.
# Simply include the time zone information as part of the time "value". <br /> E.g. <code><nowiki><abbr class="value" title="18:30-0700">6:30pm</abbr></nowiki></code>
# Or use another value excerpt for the timezone (was: <del>introduce the class name "tzvalue"</del>) <br /> E.g. <code><nowiki><abbr class="value" title="18:30">6:30pm</abbr> <abbr class="value" title="-0700">PDT</abbr></nowiki></code>
# Or allow both and let web authors decide. This is the current leaning.
#* if web authors want to specify timezone as part of the time (first example above), they can,
#* or if web authors visibly publish the timezone separately (second example above), then they can mark that up.
#* or if web authors wish to omit timezone information, they can do so as well, as most do today. In practice this works fine, as it creates a "floating" time which works fine in far more than the 80/20.

Much of the above was derived from [http://rbach.priv.at/Microformats/IRC/2008-06-24#T161740 a lengthy discussion on IRC].

==== discussion ====
<div class="discussion">
* regarding the [[datetime-design-pattern#advantages|advantage]] of "and most importantly, introduces no dark data."
** "Dark data" is sometimes what publishers *want* to publish. To use the example of TV schedules which kick started the renewed discussion in this area, publishers will often not want to display the date. For instance, if a page entitled "Tomorrow's TV" and containing 300 different programmes marked up with <code>dtstart</code>, it is superfluous to explicitly display the date for each one. With this proposed solution the [[include|include pattern]] could be used to include the date into each vevent, but a visible link to the date on each programme would simply be confusing. Sometimes it just makes sense to hide some of the information you're publishing as a microformat - because the information you want to make explicit to parsers can be inferred from context by humans, or is more appropriately displayed at a different level of granularity for machines and humans. [[User:TobyInk|TobyInk]] 14:26, 24 Jun 2008 (PDT)
*** It doesn't matter whether publishers *want* to publish dark data or not. Invisible data always leads to poorer quality data. Publishers publish all kinds of invisible metadata in the heads of documents etc. because they want to, but their desire doesn't stop the data from becoming obsolete, diverging from the actual visible data etc. The quality of the data matters more than any publishers wish(es) of publishing in a specific format, or in a hidden way. In the example you gave, using the include pattern in that way would not result in any visible links, but merely empty include anchors. It never makes any sense to actually hide "some of the information you're publishing as a microformat", because historically that always results in some loss of data quality over time and thus the microformats [[principle]] of visible data instead of invisible metadata. [[User:Tantek|Tantek]] 14:32, 24 Jun 2008 (PDT)
**** All microformats hide ''some'' data. In the example <code><nowiki><span class="tel">01632 960123</span></nowiki></code>, the information that the long string of numbers represents a telephone number is invisible. And making it visible (<code><nowiki>Tel: <span class="tel">01632 960123</span></nowiki></code>) violates DRY. It's just a matter of where to draw the line.
***** That statement makes the mistake of conflating *type* data and *content* data. "tel" is not content data, just as <nowiki><p></nowiki> is not content data. It's markup, indicating the type of the data. Markup (type data) being invisible to the user has worked just fine. Content (content data) being invisible to the user is the problem of dark data. Or rather, if you think that everything is data, then you really should be spending time developing in a system that is built on that assumption, e.g. RDF, rather than microformats, which are built on HTML, and the clear separation of type of data (HTML elements, microformats properties) and content data (inner text, text attribute values).
****** My point is that there isn't a ''distinction'' between the two, but a ''continuum''. The choice of where to draw the line is never a clear one and always somewhat arbitrary. The vCard standard could quite easily have ended up with separate "TEL", "FAX" and "CELL" properties, in which case hCard would have ended up with <code><nowiki><foo class="tel"></nowiki></code>, <code><nowiki><bar class="fax"></nowiki></code> and <code><nowiki><baz class="cell"></nowiki></code>. Going the other way, they could have stored e-mail addresses as mailto: URLs, and then hCard would have <code><nowiki><a class="url" href="mailto:quux@example.com"></nowiki></code>. They chose the way they did, and as a result in hCard the distinction between a mailto: URI and an http: URI is largely invisible (in most circumstances only obvious by looking at the status bar when hovering), but the distinction between a telephone number and a fax number is visible. But that wasn't the only possible (nor the only reasonable) outcome.
******* REJECTED THEORETICAL AND TANGENT. There is a clear distinction between *type* data and *content* data in the concrete examples of both HTML and hCard (and vCard from which it derived its distinctions). The expression of a "continuum" and the hypothetical examples given to justify the expression are all purely theoretical (rather than real and pragmatic), and thus are not worthy of being the basis of an issue. In addition, such a theoretical continuation of discussion is tangential to the original issue raised (publishers wanting to publish dark data), and thus is rejected on that basis as well. [[User:Tantek|Tantek]] 00:51, 2 May 2009 (UTC)
</div>

==== date time separation test ====
In order to determine the feasibility of this pattern, it's useful to try a few test cases with various microformat examples:

* [[value-excerption-dt-separation-test]] (in progress)



== enabling more use of title attributes ==

===parsing <code>title</code> from empty <code>value</code> elements===

As a solution to the invisible data requirements sometimes presented by [[machine-data]] in microformats, a parsing rule is proposed where the <code>value</code> element is <em>empty</em> (contains no non-whitespace characters), the <code>title</code> attribute instead be parsed.

e.g. <code><span class="dtstart">Tuesday the 24th at 6pm <span class="value" title="20080624T180000+1000"></span>lt;/span></code>

Note that due to a quirk in parsers, this technique can already be used in some parsers where the empty <code>value</code> node is also an <code>abbr</code> element. That is semantically incorrect use of <code>abbr</code>, though.

====resolution notes====

* This is parsable, but needs to be specced precisely.
* Suggest restricting to instances where a single <code>value</code> element exists, e.g.
** Disallow concatenation of multiple non-visible embedded values
** Disallow embedded non-visible values from being appended to visible data.
* This pattern exists to solve the [[machine-data]] problem, and restricting it more will discourage it being mis-used for hiding other, useful data
** Restrict the value element to be the first-child (excluding white-space text-nodes) of a µf property element, forcing the data to be kept physically close to the µf property in code. Keeps data close, helps maintenance issues. Intends to alleviate some invisible data principal concerns.
** Require that only the machine-data value and its human form be contained within the microformat property; the µf property should not include arbitrary date
*** Include something to effect of ‘parsers may attempt to validate the human form against the machine form’ (PHP has a human date parsing function, for example)
** Restrict opt-in to specific properties. Do not allow it to be parsed globally. Fail parsers which implement it globally.
* Regarding accessibility, have confirmation that the empty element will be ignored (''Thank you'': James Craig, Gez Lemon, Bruce Lawson): “JAWS and Window-Eyes announce the title attribute for an empty abbr is used and verbosity is set to ‘expand abbreviations’, but neither read the title attribute on an empty span.”

====issues====
<div class="discussion issues">
* '''Violates the microformats [[principle]] of visible data.''' Numerous previous efforts (e.g. markup in comments etc.) have walked down that path of "dark data" and failed in practice. We must hold ourselves to higher standards than any XML/RDF solution. It's part of what sets microformats apart from so many other failed efforts at data representation on the web. We must not go down the path of dark data. IMHO that principle is inviolable for [[microformats]]. [[User:Tantek|Tantek]]
** The approach here is that we have ''exceptional'' situations where we are requiring data to be duplicated for machines. They are exceptions which have existed in microformats since hCard, and this is a pattern to handle those exceptions and '''only''' those exceptions in response to the problems people have publishing them. The specification for this could be written to make it a per-property opt-in device, only for those properties identified above. ''This is not a ‘generic data embedding’ device'' and in line with the cited principals, should not be allowed to become one. --[[User:BenWard|BenWard]] 05:17, 25 Jun 2008 (PDT)
** An alternative, I suppose, would be to recognise all of the above data format examples as being in violation of the microformats principal, since authors are hiding them in favour of their own content. Every instance of fixed data formats in microformats that force authors to break the invisible data principal would need to be eliminated in favour of accessible, i18n compatible replacements, including those in hCard which are 1:1 mappings from vCard. We _could_ undertake that, but previous discussions (people being advised to misuse ABBR for translation of the vCard telephone types, for example) have already suggested that supporting the visible publishing is too complex. --[[User:BenWard|BenWard]] 05:17, 25 Jun 2008 (PDT)
** Additionally, the use of terms such as ‘dark data’ is inappropriate for this discussion, which is focused on functional, practical solutions to the identified problem. The term is emotive, and aggressive toward other, completely unrelated technologies (such as RDF) which is irrelevant to this solving this issue. Precisely, the machine-data in this technique is ‘non-visible machine-data’, and is being approached with specific regard to the microformats principal of ''design for humans first''. --[[User:BenWard|BenWard]] 05:34, 26 Jun 2008 (PDT)
* '''Worsens the [[principles#related|DRY]] violation''' by separating the human visible version and machine readable version into separate elements. Duplicate data itself is bad, but at least by keeping the duplicates local on the same element (as the existing abbr-pattern does), the risk of drift/divergence is reduced. The greater the distance in content of the duplicates, the greater the risk of drift/divergence, and thus the lower the quality of data. This has been illustrated by the divergence of invisible metadata in the head of a document versus the content in the body, and even more so across documents.
**The machine-data form is kept as a sibling of the human form, and in distance in code, is not much further away than the data stored on a single elements <code>title</code> attribute. Further, the specification for this could demand the value element be placed as the _first child_ of the parent property, forcing it to be published immediately after the property element. --[[User:BenWard|BenWard]] 05:17, 25 Jun 2008 (PDT)
* '''Some parsers may strip empty inline elements''' (particularly those that run incoming HTML through [http://tidy.sf.net Tidy] to convert it into well-formed XML). A workaround may be to allow (or even require) hard white space (i.e. <code>&nbsp;</code>) within the element with class='value".
**It is, however, trivial to patch and build Tidy not to do this (keeping empty elements where that element also has a class attribute). Parser writers need to feed back on whether using a custom build is impossible to their solution, but since Tidy can be made to work, the problem can likely be alleviated. Ben Ward has put up an experimental build of Tidy with patched element-dropping behavior here: [http://ben-ward.co.uk/files/tidy-microformats.zip tidy-microformats.zip]
*** Tidy is not just used in parsers, but also by publishers, as part of CMSes, etc.
* '''WYSIWYG editors''' - this might present a problem in these editors in terms of allowing the user to change the value of the title of an empty span. Some of them allow editing title attributes of some elements, namely <A>, <IMG> and not much more. Needs to be properly researched, but is this an issue? Should we care about default WYSIWYG deployments? Or leave that for microformats-aware WYSIWYG versions, they would allow editing this span somehow... [User:Andr3|Andr3]] 04:38, 7 Nov 2008 (GMT)
</div>

=== ‘<code>value-title</code>’ ===
Numerous proposals over the years have advocated expanding the use of the title attribute beyond the abbr tag for storing microformat property values.

A more restrictive variant of the previous "parsing title from empty value elements" brainstorm is to introduce a new value excerption class name and some rules designed to reduce the negative impact of the disadvantages/issues noted above.

'''valuetitle''': before "normal" value excerption handling, first look (in the same manner as value-excerption) for the class name "valuetitle", if it is found, use the value of the title attribute on that element and do no further value excerption or other parsing for that property value.

E.g.

<code><nowiki>
<span class="type">
<span class="valuetitle" title="cell">mobile</span>
</span>
</nowiki></code>

In addition to first looking for "valuetitle" where a parser would look for "value", it seems reasonable to also allow "valuetitle" on the property element itself in order to minimize the markup necessary, e.g.:

<code><nowiki>
<span class="type" class="valuetitle" title="cell">mobile</span>
</nowiki></code>

Naming reasoning/methodology: by using the prefix "value-" it is clear that this is part of the value excerption pattern. By using the suffix "-title", it is clear that the "title" attribute is involved. Thus the name "valuetitle" is a good mnemonic for its functionality. See related [[naming-principles]].

This "valuetitle" variant was suggested on 2008-08-30 by [[User:Tantek|Tantek]] in a discussion with [[User:BenWard|Ben Ward]], derived from the previous brainstorm over parsing of title from empty elements — this pattern could also be used with empty elements.

When using an ''empty'' element with the "valuetitle" classname (e.g. to avoid tooltip/hover effects if that is desired), it must be the '''first child element''' of the property element. E.g. (whitespace added for illustrate nesting/hierarchy)

<code><nowiki>
<span class="type">
<span class="valuetitle" title="cell"></span>
mobile
</span>
</nowiki></code>

==== advantages ====
* Avoids confusing existing parser's use of the class="value" excerption pattern by introducing a new class name for this specific purpose.
* Reduces some of the DRY violation impact by encouraging the tight binding of the property element (the element with the property name class name, e.g. the <code>span class="type"</code> in the example) to the element containing the format-specific data while encouraging the adjacent proximity of the human readable duplicate.

==== value-title test ====
[[User:BenWard|Ben Ward]] has updated this brainstorm to use "value-title" per microformats [[naming-convention#Some_Details|naming principles for compound words]] and created some test cases:

* [[value-excerption-value-title-test]]

Please take a look and report your results on that page.

==== previous similar proposals ====
<div class=discussion>
* I believe there may have been a proposal for "usetitle"(link+citation needed) in the past that would function similarly. I think "valuetitle" is better than "usetitle" as "valuetitle" is more *descriptive*, i.e. meaning "the title is the value", as opposed to "usetitle", which is more *prescriptive*, i.e. "use the title". [[User:Tantek|Tantek]] 08:13, 1 Sep 2008 (PDT)
** Agreed. ‘Processing instruction’ classenames are ugly and undesirable. Class should always be descriptive of the content. --[[User:BenWard|BenWard]] 05:42, 14 January 2009 (UTC)
</div>

== Rejected ==
The following brainstorm proposals have been rejected for various reasons (included inline) and are included here to hopefully avoid going down the same paths again.

=== object param handling ===
2008-08-23 [[User:BenWard|Ben Ward]] and [[User:Tantek|Tantek Çelik]] brainstormed the following possible special case markup handling for the use of the [[value-excerption-pattern]] with the <nowiki><object></nowiki> element. Modified 2008-08-26.

The following markup example documents one way the [[hCard]] <code>tel</code> property's <code>type</code> subproperty could be specified with the enumerated value of "cell" while providing the UK English "mobile" as the human visible object text contents:

<pre><nowiki>
<object class="type" lang="en-GB">
<param name="value" value="cell" />
mobile
</object>
</nowiki></pre>

==== summary ====
* '''object element special case handling of value excerption'''. When a microformat (sub)property class name is specified on an object element, then value excerption handling is modified as follows:
* '''first param with name attribute value'''. if the first child of the object is a param element, and that param element has name attribute value of "value", then use the value attribute value for the value for the microformat (sub)property class name specified on the object.
* '''continue'''. if not, continue with existing value excerption handling, and microformat (sub)property parsing rules as currently best specified by [[hcard-parsing]].

==== notes ====
Note that the param element does not have a 'class' attribute and thus its 'name' attribute (which has a compatible semantic) is used instead to invoke the value excerption pattern.

===== advantages =====
* '''Greater semantic re-use.''' The use of the param element to specify a value for its object is in line with the param element's semantics. The semantic association between the object and the param element is defined in the HTML4 specification.
* '''Less invention.''' This use of object param is superior to the use of a nested empty span element. The association of an empty span with its parent is a new semantic not previously defined in the HTML4 specification. Thus this use of object param markup better follows the principle of minimum invention as compared to nested empty span markup.
===== neutral =====
* '''Similar violation of DRY to nested empty span.'''
===== disadvantages =====
* '''Less human visible than abbr DRY violation.''' The contents/values of param elements are not exposed to the user of a browser, unlike the title attribute of abbr which, since it is commonly available as a hover tooltip, is more human visible, thus verifiable, than param.
* '''DRY violation content divergence risk greater than abbr.''' With abbr, one element is used to express both a human visible string and the property value, thus tying these values closer together (thus reducing risk of divergence). With object param, two elements are used, and thus risk of divergence may be greater than the use of abbr. Possible mitigating techniques that would help keep the property value and the equivalent human visible string closer to each other, perhaps as close in the code as they are when using abbr:
*# require param be first child of object
*# require use of only one param child (allow other child elements)
*# require exclusive use of object for value excerption i.e. no using the same object for an actual replaced object and a value excerption
*# require "value" attribute be the last attribute specified on the param element
*# require equivalent human visible text be placed immediately (allowing for whitespace) following the param
===== criticisms =====
* '''Verbose''' - [[User:TobyInk|TobyInk]]

==== to do ====
* Browser testing. This code sample must be tested in various browsers to determine how they process and handle pages with such code
*# determine which browsers to test (based on popularity, deployment, etc.)
*# write a full sample test case using the above object param markup pattern and a complete hCard
*# write a more complex sample test case with multiple uses of the object param markup pattern
*# test do browsers properly display the UK English text "mobile"?
*# test do browsers generate multiple browser (e.g. Webkit, Trident etc.) controls as they would for embedded frames (nested HTML objects)?
*# determine any other tests
* Parser implementability. Determine approximately how much work it would be to implement this special case object param support.
** I've just added support for this. It took 19 bytes of code. [[User:TobyInk|TobyInk]] 01:24, 25 Aug 2008 (PDT)
* Document in more detail. Assuming browser tests of a simple example pass (proper visible text displayed, page efficiency not compromised by additional control creation), document how to handle/parse this pattern in more detail. Iterate.

==== Browser Testing ====
Using the following simple, HTML4 hcard:

<pre><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">

<title>&lt;object> value excerption pattern: hCard Telephone Type Test Case</title>

<body class="vcard">
<h1 class="fn"><a class="url" href="http://ben-ward.co.uk">Ben Ward</a></h1>
<p class="tel">
<object class="type">
<param name="value" value="cell">
Mobile:
</object>
<span class="value">415-123-567</span>
</p>
</body></pre>

===== Results =====
A pass is to display a heading level one ‘Ben Ward’ with hyperlink, followed by a paragraph displaying the text ‘Mobile: 415-123-567’
Browsers selected based on YUI Graded Browser Support (August 2008), plus some others.

* Opera 9.5 - Pass
* Firefox 2, 3 - Pass
* Microsoft Internet Explorer 5.2 (Mac) - Pass
* Microsoft Internet Explorer 6 - Partial Pass†
* Microsoft Internet Explorer 7 - Partial Pass†
* Microsoft Internet Explorer 8 (beta) - Partial Pass†
* Safari 3 - Pass
* Safari 2 - *Fail* ††

* † <span id="iewarningfail">Internet Explorer 6–8 on Windows XP renders the correct text, but triggers an ActiveX security warning bar on the page load.</span>
<div class="discussion">
* This is an error on behalf of IE/Windows. As the object has no type nor data attributes, it has nothing that would bind it to a specific ActiveX control, and therefore should not trigger a security warning bar. This bug should be reported, and the respective bug number referenced here. To do:
** report bug to Microsoft to fix in IE8 at a minimum (and since it is a security related false positive, perhaps patch it in IE6 and IE7 as well)
** ask Chris Wilson if there are any markup work-arounds to cause security alert to not happen for something that is not loading any ActiveX (2008-09-04 DONE. [[User:Tantek|Tantek]] direct messaged Chris, pointed him to this browser testing section, asked him about any markup work arounds.)
** try DECLARE attribute, e.g. <code><nowiki><object class="type" declare="declare">visible text</object></nowiki></code> to see if that makes IE/Windows not instantiate an ActiveX control and thus not trigger the warning.
*** IE6 and IE7 (as tested on virtual machines on [[User:BenWard|Ben Ward]]'s computer) still trigger the warning message, but do properly display "visible text". It appears this may happen for *any* inline markup use of the <code>object</code> element due to Microsoft's attempting to "[http://jritmeijer.spaces.live.com/blog/cns!8A48A27460FB898A!372.entry avoid paying patent whores such as Eolas hundreds of millions of dollars for something they did not invent in the first place.]" This would seem to imply that we cannot depend on any inline use of object for any markup solutions. We should still specify what happens with object for parsing purposes, and then document the current/past implementation/browser problems with object on another page like [[object-warnings]]. [[User:Tantek|Tantek]] 14:36, 23 Sep 2008 (PDT)
*** Safari 2 still puts an empty box in place of the object, and fails to display "visible text".
</div>
* †† Safari 2 renders a default-sized white box (as if embedding an external control). It breaks layout and does not display the desired content.

===== Safari 2 Tweak =====
The example is tweaked as follows to affect Safari 2 rendering:

<pre><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">

<title>&lt;object> value excerption pattern: hCard Telephone Type Test Case</title>

<body class="vcard">
<h1 class="fn"><a class="url" href="http://ben-ward.co.uk">Ben Ward</a></h1>
<p class="tel">
<object data="data://" class="type">
<param name="value" value="cell">
Mobile:
</object>
<span class="value">415-123-567</span>
</p>
</body></pre>

A <code>data="data://"</code> URL attribute is added to the <code>object</code> element.

====== Safari 2 Result ======
* Safari 2 - Partial Pass†

† Safari 2 renders the object correctly on first page load, *however*, upon using the browser ‘Refresh’ function, the <code>object</code> element reverts to the broken rendering described in the original test.

===== Current Conclusion =====
<div class="discussion issues">
* Safari 2 does not pass the test acceptably for this to be adopted as the only solution.
* Internet Explorer's security warnings are irritating, but justifiably unacceptable. --[[User:BenWard|BenWard]] 20:17, 26 Aug 2008 (PDT)
** I concur. And while we can report a bug against IE/Windows in the hopes that it is fixed eventually (perhaps even in IE8 before it ships), as this problem has been fixed in Safari 3, it is doubtful that a bug report against Safari 2 would be fixed in an intermediate version. --[[User:Tantek|Tantek]] 03:07, 27 Aug 2008 (PDT)
</div>

==== misconceptions ====
===== misunderstanding of authoring unfriendliness =====
* not very hand-authoring friendly, compared to other proposals like: [[datetime-design-pattern#Machine-data_in_class|Machine data in class]]: <code><nowiki><span class="type data-cell">Mobile:</span></nowiki></code>, and [http://microformats.org/discuss/mail/microformats-discuss/2008-February/011583.html data prefix in titles]: <code><nowiki><span class="type" title="data:cell">Mobile</span></nowiki></code> [[User:TobyInk|TobyInk]]
** It is even more hand-authoring unfriendly to introduce a new syntax, as "Machine data in class" does, and to some extent as "data prefix in titles does". Additional (especially new) syntax introduces far greater cognitive load to the author than a little bit more markup. [[User:Tantek|Tantek]]

==== previous iterations ====
===== 2008-08-23 =====
<pre><nowiki>
<object class="type" lang="en-GB">
<param class="value" name="value" value="cell" />
mobile
</object>
</nowiki></pre>
====== disadvantages ======
* '''Invalid (X)HTML''' - although this pattern does make sense, it is worth noting that <code><param></code> is one of just a handful of HTML elements for which the <code>class</code> attribute is [http://www.w3.org/TR/REC-html40/struct/objects.html#h-13.3.2 not defined]. Use of this pattern will break validation unless a custom DTD is employed.
====== advantages ======
None unique to this variant.
===== no previous iterations =====
==== inspiration ====
Ben Ward and Tantek Çelik decided to explore other markup possibilities beyond use of empty span elements in the hopes that more semantic alternatives could be found.

== related pages ==
* [[value-excerption-pattern]]
* [[value-excerption-pattern-issues]]
* [[value-excerption-dt-separation-test]]
* [[value-excerption-value-title-test]]
* [[hcard#Value_excerpting|hCard: Value Excepting]]

hlisting-brainstorming

2009-10-08T09:03:35Z

Spiritquest: /* Items changed: */ spelling correction

<entry-title>listing microformat brainstorming </entry-title>
This is brainstorming for a [[hlisting]] microformat per the [[process]].

== proposed schema revisions ==
=== Revised Base Schema Elements (proposed, revised by [[User:JayMyers|Jay Myers]] 16:55, 29 Jun 2009 (UTC)) ===

*hListing (hlisting)
** listing action. optional. one or more tags, suggested set: sell | rent | trade | meet | announce | offer | wanted | event | service
** '''lister.''' required. hCard | (fn || email || url || tel).
** dtlisted. optional. ISO8601 absolute date time.
** dtexpired. optional. ISO8601 absolute date time.
** price. optional. text. [should include a floating-point number with optional ISO currency codes] - see the currency proposal
** item info. optional. (fn || url || photo || geo || adr) | hCard (for person or business).
** summary. optional. text.
** '''description.''' required. text with optional valid XHTML markup.
** item tags. optional. keywords or phrases describing the item being offered, using rel-tag
** permalink. optional.
** availability. optional. text.
** condition. optional. text. examples: 'new', 'used', 'refurbished'.
** shipping. optional. text. text describing shipping and fulfillment

==== Notes ====

Please see [[hlisting-examples|hListing examples page]] for analysis of 80/20 use case for new attributes availability, condition and shipping. I believe condition should still be considered even though it misses the 80/20 use case mark (71.2% based on current analysis) as it is included in most product-specific data submission services (e.g., Yahoo Product Submit, Google Base).

----

=== Revised Base Schema Elements (proposed) ===

*hListing (hlisting)
** listing action. optional. one or more tags, suggested set: sell | rent | trade | meet | announce | offer | wanted | event | service
** lister. optional. hCard | (fn || email || url || tel).
** dtlisted. optional. ISO8601 absolute date time.
** dtexpired. optional. ISO8601 absolute date time.
** price. optional. text. [should include a floating-point number with optional ISO currency codes] - see the currency proposal
** item info. optional. (fn || url || photo || [[geo]] || [[adr]]) | [[hcard|hCard]] (for person or business).
** summary. optional. text.
** '''description'''. required. text with optional valid XHTML markup.
** item tags. optional. keywords or phrases describing the item being offered, using rel-tag
** permalink. optional.
** availability. optional. text.
** condition. optional. text. examples: 'new', 'used', 'refurbished'.
** shipping. optional. text. text describing shipping and fulfillment

==== Items removed ====
* version. optional. text.

<div class=discussion>
* +1 I'm tending to agree with the removal of version, as in practice it has not been necessary for either [[hReview]] or [[hListing]].[[User:Tantek|Tantek]] 17:45, 16 April 2009 (UTC)
</div>

* item info. optional. (fn || url || photo || geo || adr) | hCard (for person or business).

<div class=discussion>
* Removal of <code>item</code> seems to be a mistake, as that is used to indicate the item itself being listed. E.g., a nested <code>hProduct</code> would be <code><p class='item hproduct'></p></code>. Removal appears to leave no way to include ''what'' is being listed. --[[User:BenWard|BenWard]] 17:38, 16 April 2009 (UTC)
** +1 completely agreed with Ben Ward's point. Wide use of [[hReview]] in the [[hreview-examples-in-wild|wild]] has shown that having an explicit "item" is both necessary and works in practice. [[User:Tantek|Tantek]] 17:40, 16 April 2009 (UTC)
* Indeed it was a mistake... left it out of my edits. Replaced. [[User:JayMyers|JayMyers]] 21:04, 22 April 2009 (UTC)
</div>

==== Items added ====
<div class=discussion>
* Each of the following should cite the analysis made of real world examples that demonstrates the 80%+ use case need, otherwise, they should not be added. [[User:Tantek|Tantek]] 17:45, 16 April 2009 (UTC)
</div>

* availability. optional. text.
* condition. optional. text. examples: 'new', 'used', 'refurbished'.
* shipping. optional. text. text describing shipping and fulfillment

==== Items changed: ====
* listing action => optional. if omitted, action assumed to be sell
* lister => optional. if omitted, the buyer/seller is assumed to be the site where the microformat exists
<div class=discussion>
* In that case, an algorithm should be provided for how to determine the hCard for the lister, if no explicit lister is given. [[User:Tantek|Tantek]] 17:45, 16 April 2009 (UTC)
* Isn't the instruction above ("buyer/seller is assumed to be the site where the microformat exists" itself an algorithm? So, if Target.com has an item for sale and lister isn't specified, you use the domain of the web page containing the markup to identify the seller as "target.com" --Kavi, 6 July 2009
* Wouldn't it make sense for it remain compulsory? If you are stating that the value reverts to a default in the case of an omission - the requirement is still that the hlisting requires a URI as part of the lister - I feel it should stay so that aggregation of hlisting information is possible outside of the domain it was originally posted on. It therefore ''requires'' this information to exist. Maybe the required property should be the url value and the other properties can be optional. [[User:Spiritquest|Spiritquest]] 19:04, 30 September 2009 (UTC)
</div>

== payment ==
Use [[rel-payment]] or something similar to indicate payment method for hListing.

== additional transactional details ==
Per the discussions raised in the [[hproduct-issues|hProduct issues list]], consider provisions for providing transactional details like "shipping" or "buy/payment" attributes or similar for an iteration of hListing.

== see also ==
* [[hListing]]
* [[hlisting-issues]]
* [[hlisting-feedback]]

User:Spiritquest

2009-09-30T21:52:07Z

Spiritquest: username

Ketan Majmudar
Developer, Designer & Semantic Web Lover

my IRC nickanme is ethicaljunction

* Developing [http://www.ethical-junction.org Ethical Junction CIC] - all profiles use hCard
* Try to incorporate microformats as widely as possible
* Interested in exploring possibilities in using microformats in other areas
* hCard or alternative to capture social site usernames and share in an address card type of format
* eco labels
* exploring [[hlisting-brainstorming | hListing]] and its usage
* Am working on a project to explore the use of [[hrecipe | hRecipe]] as well

I seem to also have created another alias - which is [[User:Ket Majmudar]] - I'm going to try and consolidate my IRC / uf-usernames - not sure how I got into this mess, please bear with me.

User:Ket Majmudar

2009-09-30T21:50:00Z

Spiritquest:

My IRC username is ethicaljunction (atm)

I'm a web author, designer & developer

I've integrated hCard into [http://www.ethical-junction.org] - all the members profiles now have hCard markup and pars through technorati to download as vCard.

Interested in getting products and reviews into the site, also interested in the proposal of eco-labels microformat proposal.

I seem to also have created another alias - which is [[User:Spiritquest]] - I'm going to try and consolidate my IRC / uf-usernames - not sure how I got into this mess, please bear with me.

hlisting-brainstorming

2009-09-30T19:04:09Z

Spiritquest: /* Items changed: */ discussion

<entry-title>listing microformat brainstorming </entry-title>
This is brainstorming for a [[hlisting]] microformat per the [[process]].

== proposed schema revisions ==
=== Revised Base Schema Elements (proposed, revised by [[User:JayMyers|Jay Myers]] 16:55, 29 Jun 2009 (UTC)) ===

*hListing (hlisting)
** listing action. optional. one or more tags, suggested set: sell | rent | trade | meet | announce | offer | wanted | event | service
** '''lister.''' required. hCard | (fn || email || url || tel).
** dtlisted. optional. ISO8601 absolute date time.
** dtexpired. optional. ISO8601 absolute date time.
** price. optional. text. [should include a floating-point number with optional ISO currency codes] - see the currency proposal
** item info. optional. (fn || url || photo || geo || adr) | hCard (for person or business).
** summary. optional. text.
** '''description.''' required. text with optional valid XHTML markup.
** item tags. optional. keywords or phrases describing the item being offered, using rel-tag
** permalink. optional.
** availability. optional. text.
** condition. optional. text. examples: 'new', 'used', 'refurbished'.
** shipping. optional. text. text describing shipping and fulfillment

==== Notes ====

Please see [[hlisting-examples|hListing examples page]] for analysis of 80/20 use case for new attributes availability, condition and shipping. I believe condition should still be considered even though it misses the 80/20 use case mark (71.2% based on current analysis) as it is included in most product-specific data submission services (e.g., Yahoo Product Submit, Google Base).

----

=== Revised Base Schema Elements (proposed) ===

*hListing (hlisting)
** listing action. optional. one or more tags, suggested set: sell | rent | trade | meet | announce | offer | wanted | event | service
** lister. optional. hCard | (fn || email || url || tel).
** dtlisted. optional. ISO8601 absolute date time.
** dtexpired. optional. ISO8601 absolute date time.
** price. optional. text. [should include a floating-point number with optional ISO currency codes] - see the currency proposal
** item info. optional. (fn || url || photo || [[geo]] || [[adr]]) | [[hcard|hCard]] (for person or business).
** summary. optional. text.
** '''description'''. required. text with optional valid XHTML markup.
** item tags. optional. keywords or phrases describing the item being offered, using rel-tag
** permalink. optional.
** availability. optional. text.
** condition. optional. text. examples: 'new', 'used', 'refurbished'.
** shipping. optional. text. text describing shipping and fulfillment

==== Items removed ====
* version. optional. text.

<div class=discussion>
* +1 I'm tending to agree with the removal of version, as in practice it has not been necessary for either [[hReview]] or [[hListing]].[[User:Tantek|Tantek]] 17:45, 16 April 2009 (UTC)
</div>

* item info. optional. (fn || url || photo || geo || adr) | hCard (for person or business).

<div class=discussion>
* Removal of <code>item</code> seems to be a mistake, as that is used to indicate the item itself being listed. E.g., a nested <code>hProduct</code> would be <code><p class='item hproduct'></p></code>. Removal appears to leave no way to include ''what'' is being listed. --[[User:BenWard|BenWard]] 17:38, 16 April 2009 (UTC)
** +1 completely agreed with Ben Ward's point. Wide use of [[hReview]] in the [[hreview-examples-in-wild|wild]] has shown that having an explicit "item" is both necessary and works in practice. [[User:Tantek|Tantek]] 17:40, 16 April 2009 (UTC)
* Indeed it was a mistake... left it out of my edits. Replaced. [[User:JayMyers|JayMyers]] 21:04, 22 April 2009 (UTC)
</div>

==== Items added ====
<div class=discussion>
* Each of the following should cite the analysis made of real world examples that demonstrates the 80%+ use case need, otherwise, they should not be added. [[User:Tantek|Tantek]] 17:45, 16 April 2009 (UTC)
</div>

* availability. optional. text.
* condition. optional. text. examples: 'new', 'used', 'refurbished'.
* shipping. optional. text. text describing shipping and fulfillment

==== Items changed: ====
* listing action => optional. if omitted, action assumed to be sell
* lister => optional. if omitted, the buyer/seller is assumed to be the site where the microformat exists
<div class=discussion>
* In that case, an algorithm should be provided for how to determine the hCard for the lister, if no explicit lister is given. [[User:Tantek|Tantek]] 17:45, 16 April 2009 (UTC)
* Isn't the instruction above ("buyer/seller is assumed to be the site where the microformat exists" itself an algorithm? So, if Target.com has an item for sale and lister isn't specified, you use the domain of the web page containing the markup to identify the seller as "target.com" --Kavi, 6 July 2009
* Wouldn't it make sense for it remain compulsory? If you are stating that the value reverts to a default in teh case of an omission - the requirement is still that the hlisting requires a URI as part of the lister - I feel it should stay so that aggregation of hlisting information is possible outside of the domain it was originally posted on. It therefore ''requires'' this information to exist. Maybe the required property should be the url value and the other properties can be optional. [[User:Spiritquest|Spiritquest]] 19:04, 30 September 2009 (UTC)
</div>

== payment ==
Use [[rel-payment]] or something similar to indicate payment method for hListing.

== additional transactional details ==
Per the discussions raised in the [[hproduct-issues|hProduct issues list]], consider provisions for providing transactional details like "shipping" or "buy/payment" attributes or similar for an iteration of hListing.

== see also ==
* [[hListing]]
* [[hlisting-issues]]
* [[hlisting-feedback]]

User:Spiritquest

2009-09-30T18:22:14Z

Spiritquest:

Ketan Majmudar
Developer, Designer & Semantic Web Lover
* Developing [http://www.ethical-junction.org Ethical Junction CIC] - all profiles use hCard
* Try to incorporate microformats as widely as possible
* Interested in exploring possibilities in using microformats in other areas
* hCard or alternative to capture social site usernames and share in an address card type of format
* eco labels
* exploring [[hlisting-brainstorming | hListing]] and its usage

User:Spiritquest

2009-09-30T18:21:26Z

Spiritquest:

Ketan Majmudar
Developer, Designer & Semantic Web Lover
* Developing [[http://www.ethical-junction.org |Ethical Junction CIC]] - all profiles use hCard
* Try to incorporate microformats as widely as possible
* Interested in exploring possibilities in using microformats in other areas
* hCard or alternative to capture social site usernames and share in an address card type of format
* eco labels
* exploring [hlisting-brainstorming] and its usage

hcard-examples-in-wild

2009-09-30T18:18:27Z

Spiritquest: /* new and uncategorized examples */ Added website - Ethical Junction to a profile page

<entry-title>hCard Examples in the wild</entry-title>
<div style="height:7.5em;text-align:center;font-weight:bold;font-size:larger">
<span style="padding:3em 0;float:left;width:33%">[[hcard-examples-in-wild#examples_by_category|Want hCards]]</span><span style="padding:3em 0;float:left;width:33%">[[hcard-examples-in-wild#new_and_uncategorized_examples|Have hCards]]</span>
</div>

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

The following sites have published [[hcard|hCards]], and thus are a great place to start for anyone looking for examples "in the wild" for inspiration, or try parsing and indexing.

== new and uncategorized examples ==
'''Have hCard?''' If you have a site with hCard(s), add it to the top of this list. Include at least one URL to a page that includes actual [[hcard|hCard]] markup. Examples without direct links hCard(s) will be removed. Check back after a few days, to see if anyone has found any problems with the examples supplied. Note that examples may be categorized and moved to the grouped section below.

You may want to use these buttons on your pages with hCards. See [[buttons#hCard]] for any recent additions.
http://www.davidjanes.com/images/mf_hcard.png   http://www.boogdesign.com/images/buttons/microformat_hcard.png

*[http://www.ethical-junction.org/member/org-2012.html Ethical Junction CIC - Profile page] We use hCard for every organisation on their profile page
*[http://www.bowtietv.com Bow Tie Television] Uses hCard for contact information on every page and in the contacts section.
*[http://www.tauruslogistics.co.nz/about/contact Taurus Logistics] Uses hCard for contact information.
*[http://www.professdiamond.com/ professdiamond] encodes Thai as UTF8 in an inline hCard at the bottom of every page.
*[http://avonvalleylocalguide.iinet.net.au/ Avon Valley Local Guide] uses hCard for contact information of advertisers.
*[http://www.arizonafirstresponse.com/ Arizona First Response] uses an hCard on each page footer.
*[http://dillingham.me.uk/ Iain Dillingham] uses an hCard on each page footer, and has a styled example (with the microformats logo) on his [http://dillingham.me.uk/contact.html contact page].
*[http://www.pixeflips.com/ Pixelflips Web & Interface Design] hCard is used in the footer of all pages for easy access to contact information.
*[http://www.herminesperr.at/ Hermine Sperr, Qualified Practitionier of the Grinberg Method® in Wien/Austria] A hcard is used for contact information on every page on her website.
* [http://www.barnard.edu/ Barnard College] - College faculty profiles use hCard for contact info. Example: [http://www.barnard.edu/faculty/profiles/mehrling_p.html P. Mehrling's profile].
* [http://www.ivycat.com/ IvyCat Website Services] - Web design & hosting firm uses hCard for business contact info. Example: [http://www.ivycat.com/contact/ Contact Us].
* [http://www.modeltrainswithlarry.com/ ModelTrainsWithLarry] - Uses hCard for organization and business address. Example: [http://www.modeltrainswithlarry.com/index.php?listing=502 Choo Choo Barn].
* [http://www.gardeningwithlarry.com/ GardeningWithLarry] - Uses hCard for organization and business address. Example: [http://www.gardeningwithlarry.com/index.php?listing=2681 United States Botanic Garden].
* [http://abyrvalg.com/ Abyrvalg] - russian city community. Uses hCard to display local businesses address. Example: [http://moscow.abyrvalg.com/biz/faq-cafe FAQ cafe in Moscow].
* [http://www.jdclark.org/v1 Jordan Clark], from the Swansea area of Wales in the United Kingdom, uses [http://www.jdclark.org/card hcard for contact information].
* [http://whichtwitterapp.com/ WhichTwitterApp] provides [http://whichtwitterapp.com/reviews/iphone/tweetie reviews of twitter apps] using hCard, hReview, rel-tag and rel-home.
* [http://www.robinleysen.be/Robin.html Robin Leysen] has a hCard on a separate page. Tried to be as complete as possible. hCard validated with Optimus.
* [http://www.jay-photographics.de/ Jay Photographics] Photographer from Stuttgart, Germany. The hcard format is used on all pages for contact information.
* [http://www.uniquesite.co.uk/ UNIQUEsite] Website designer based in Brighton, UK. Uses the hcard format for contact information.
* [http://www.slideshare.net/ SlideShare] uses hcard to identify its users. see [http://hcard.geekhood.net/?url=http%3A%2F%2Fwww.slideshare.net%2Fkcmani#result Validated hcard] and [http://www.slideshare.net/kcmani Mani's SlideShare profile]
* [http://chrisruppel.com Chris Ruppel], a web developer in Dallas, TX, uses an hcard for contact information site-wide (as well as XFN)
* [http://greenspiritgardeners.com/ Green Spirit Gardeners] uses the hCard format throughout the site, including on the portfolio page for [http://greenspiritgardeners.com/portfolio/ commercial clients] and the [http://greenspiritgardeners.com/contact/ contact] page.
* [http://www.dorettebos.nl/ Dorette Bos Coaching & Training] uses hcard microformat on the [http://www.dorettebos.nl/contact.php contactpage]
* [http://volunteers.st/ Steffi & the volunteers] is an Austrian band and uses hcards for [http://volunteers.st/ band-contact in the footer] and on the page of the [http://volunteers.st/crew.html crew]
* [http://www.textundkonzept.at Bernhard Ulrich] an Austrian copywriter uses the hcard format [http://www.textundkonzept.at on all pages of his website] for his contact information
* [http://www.powerbrand.at/contact.html POWERBRAND] a brand name development agency uses a [http://www.powerbrand.at/contact.html hcard for contact information]
*[http://www.koerperarbeit.net/ Anita Braunsberger, Qualified Practitionier of the Grinberg Method® in Linz/Austria] A hcard is used for contact information on her website.
*[http://www.carpetscleansandiego.com Durbin's Carpet Care] displays a vCard for contact information and relevancy
*[http://www.nationalrural.org/organisation.aspx?id=96a3fc04-5c03-4d31-bb8a-2c55cc29aed4 National Rural Knowledge Exchange] uses an hCard with geo tags when displaying an organisations information
* [http://www.tinstar.co.uk/about-tinstar-design/contact-tinstar-design.html Tinstar Design] uses an hCard for company contact information.
* [http://www.interdixit.com/esp/contacto.php Interdixit] uses an hCard for his contact information.
* [http://www.sisnova.com/ Sisnova] uses hCard for his location pages.
* [http://www.fenoyarquitectura.com/esp/situacion.php Eduard Fenoy i Associats] uses an hCard.
* [http://www.deltronic.com/ Deltronic Corporation] of Santa Ana, CA has posted an hCard with geo tags on its [http://www.deltronic.com/contact.shtml Contact] page. Background image of a contact card reinforces content. For those without enabling browser extensions, both hCard "logo" and text link make vCard available via external parser.
* [http://transitionsmft.org/ Transitions Marriage and Family Therapy] has an hCard with geo tags in the footer of each page. There is also an hCard for each counselor on the [http://transitionsmft.org/about.php About] and [http://transitionsmft.org/contact.php Contact]pages.
* [http://ball.in.th/ ball.in.th] uses hCard to display all usernames.
* Italian business directory and community portal [http://www.cylex.it/ cylex.it] implements hCard for companies’ contact information with geo tags. Example: [http://www.cylex.it/azienda/computerland-10559319.html company profile]
* [http://jermy.musicremedy.com/ Jermy Leeuwis MSc] uses an hCard for his contact information.
* [http://idoinfotech.com Gary Eckstein] uses an hCard for [http://idoinfotech.com/contact contact information].
* [http://www.drsuarez.net/ Dr. Suarez] uses hCard on his [http://www.drsuarez.net/cvitae.html resume page]
* [http://sourceforge.net/projects/adx/ addressbook.xml] provides hCard support: [http://elektronengehirn.net/addressbook/addressbook.html adx live example]
* [http://aplawrence.com APlawrence.com] is using hCard for its [http://aplawrence.com/Links/consultants.html Unix and Linux Consultants Page]
* [http://www.afonsoduarte.com Afonso Duarte's Portfolio]. Uses an hCard for the contact information.
* [http://www.rafe.me Web development by Rafe Harwood]. Uses an hCard for the contact line in the footer of every page.
* [http://www.frogmeat.com Los Angeles Web Design]. Uses an hCard for contact information.
* [http://www.arbea.basilicata.it/ ARBEA - Agenzia della Regione Basilicata per le Erogazioni in Agricoltura]. hCard is used both for classic [http://www.arbea.basilicata.it/index.php?option=com_contact&view=contact&id=4&Itemid=101 Contact page] and for farms showcase ("Vetrina Aziende Agricole") available for registered users. I've embedded it modifying Joomla! 1.5 com_contact core component. Users of this CMS can [http://joomlacode.org/gf/project/hcardcontact/ download my patch].
* [http://trumps.net Los Angeles Search Engine Optimization] Uses hCard in the footer of all pages.
* [http://reaganvick.com Personal Portfolio of Lance Reagan Vick]. Includes examples of PGP and SSH public keys I have not seen used anywhere else. Hopefully someone finds it helpful!
* [http://www.fracturedstudios.com Los Angeles Search Engine Optimization] uses hCard to provide address information at bottom of page
* [http://www.csid.upt.ro/home.php The Distance Learning Center - CSID, "Politehnica" University Timisoara], Romania uses hCard, including geo information, in every page's footer for encoding the University address. hCard is also used for [http://www.csid.upt.ro/personal.php staff] and student contact information.
* [http://rehabpizza.co.uk Rehab Restaurant] London restaurant, see the sidebar for link to [http://rehabpizza.co.uk/rehab.hcard the hcard].
* [http://www.outdoorla.org/ Los Angeles Hiking Trails] at the bottom right, our contact information is marked up as an hcard.
* [http://c7.se Code7 Interactive] uses a hCard for Peter's [http://c7.se/contact contact details].
* The [http://www.austinartcollective.com Austin Art Collective] is a group dedicated to helping emerging artists sell their artwork online. There is space for users to submit [http://www.austinartcollective.com/gallery/Art-City-Austin.html art gallery reviews] as well, [http://www.austinartcollective.com/austin-galleries/Downtown.html organized by neighborhood] in Austin, TX USA.
* [http://www.squaremeal.co.uk/ Square Meal Restaurant Guide] uses hCards and hReviews for all restaurant listings and [http://www.squaremeal.co.uk/review/Ristorante_Semplice/1596 visitor reviews].
* [http://www.vegan-nottingham.co.uk/ Vegan Nottingham Guide] uses hcards, including geo information, for each entry in the guide.
* [http://www.cgtworld.com/ Cybernation Gamers Tournament] uses hCard in all users profiles like [http://www.cgtworld.com/profile/id-1/ Moonlext's Profile] and in the [http://www.cgtworld.com/about/press.html press page of CGT].
* [http://fcctlh.org First Christian Church of Tallahassee] Uses hCard in the footer of all pages.
* [http://www.pseps.com/vc-people/a.cfm The PSEPS Venture Capital and Private Equity Directory] Venture capital and private equity directory using microformats (both for professionals and firms).
* [http://www.koningskindkadootjes.nl koningskindkadootjes.nl] Hcard located at the bottom of the pages.
* [http://www.futurix.nl futurix.nl website and webshop development] At the bottom of the pages you'll find the hcard. With a link to technorati the hcard is used to get a vcard out of the hcard.
* [http://romjon.com/contact-us romjon.com website design & development] Contact Us page using hcard to markup address details. By using Operator, Google Maps and Yahoo! Maps can be made to open with the pointer, respectively, in pretty much and more or less exactly the right place.
* [http://www.thebeanmachine.nl/ The Bean Machine] at the bottom right, our contact information is marked up as a hcard
* [http://www.universalmedicalid.com/canada Universal Medical ID Canada] uses hCard to provide address information at bottom of page, as well as on a number of pages within the site.
* [http://web.mac.com/a.gibson/ Alex Gibson Web Developer] uses hCard for contact info on his homepage.
* [http://www.wardelldesign.com/html/contact/index.php Wardell Design] uses hCard for contact info with optional vCard download.
* [http://www.drfosterhealth.co.uk/hospital-guide/ Dr Foster Hospital Guide] uses hCard to mark up hospital addresses. See [http://www.drfosterhealth.co.uk/hospital-guide/hospital/nhs/Basingstoke-and-North-Hampshire-Hospital-366.aspx Basingstoke hospital page] for example.
* [http://www.drfosterhealth.co.uk/complementary-therapist-guide/ Dr Foster Complementary therapist guide] The [http://www.drfosterhealth.co.uk/complementary-therapist-guide/objectlist.aspx?w=32&p=8&obid=&sub=0 regulatory bodies page] uses hCard for contact details.
* [http://wayne.edu/ Wayne State University] uses hCard for University address and contact details in the global footer used on most web pages.
* [http://www.brakemeters.co.nz/ Portable Brake Meters N.Z. Ltd] uses hCard for business address and contact details.
* [http://www.tallpoppieshamilton.co.nz/ Tall Poppies Florist] uses hCard for business address and contact details.
* [http://www.livingcolour.co.nz/ Living Colour Florist] uses hCard for business address and contact details. See [http://www.livingcolour.co.nz/Information.aspx Information] page
* [http://www.dallasfamilyhomes.com/ DallasFamilyHomes.com] uses hCard for property addresses and geo latitude and longitude. See [http://www.dallasfamilyhomes.com/dallas-homes/ Dallas Homes] page for embedded hcards and property detail pages.
** Pretty good. An improvement might be to use <code>agent</code> to mark up the agent's contact details, and <code>note</code> to mark up the property descriptions. [[User:TobyInk|TobyInk]] 16:22, 4 December 2008 (UTC)
** Thanks for the suggestion Toby. Added the <code>note</code> for the description to the homes listings and home detail pages.
* [http://www.jabz.de/ Jabz | Internet Marketing Agentur] uses hCard for business address and contact details. See [http://www.jabz.de/kontakt/ Contact Page]
* [http://sixthirteendesign.com/ Six Thirteen Design] uses an embedded hCard along with other contact details on the footer of each page (http://sixthirteendesign.com/)
** ''Problems:'' page also includes class="vcard" used in a non-hCard context (for a VCARD download); types for telephone number and e-mail address are improper. [[User:TobyInk|TobyInk]] 16:22, 4 December 2008 (UTC)
* [http://www.locanto.com/ Locanto - Free Classifieds] uses hcards to geolocate their classified listings. Visit the ad pages for examples.
* [http://www.yalwa.com/ Yalwa - Local Directory] uses hcard on their directory listings. Example: [http://wiesbaden.yalwa.de/ID_102318221/Yalwa-GmbH.html Yalwa Address Listing]
* [http://www.fluendi.com/Contact Fluendi Consulting] uses hcard on their contact page (http://www.fluendi.com/Contact)
* [http://www.badbedbugs.com/ Bed Bugs] uses hcard for their site information. See the [http://www.badbedbugs.com/about-bad-bed-bugs/ about bed bugs] page.
* [http://www.lawyer-directory.net/ Lawyer Directory] uses hcard for addresses within the lawyer directory. Example [http://www.lawyer-directory.net/lawyer/Grand-Rapids-Bar-Association-Grand-Rapids-law434032.htm listing]
* [http://www.hanfmuseum.de/about About Hanf Museum Berlin] uses hcard for addresses and contact informations.
* [http://maps.google.com/ Google Maps] uses hCards for addresses. See [http://googlemapsapi.blogspot.com/2007/06/microformats-in-google-maps.html Microformats in Google Maps].
* [http://local.mapquest.com/ MapQuest Local] uses hCards for locations, hCalendar for events and supports the draft Geo format when lat/lng data is provided. See [http://blog.mapquest.com/2008/09/25/microformat-support-on-mapquest-local/ Microformat Support on MapQuest Local] for more information.
* [http://www.whitepoppy.com/ WhitePoppy.com] uses hCard for business address. See [http://www.whitepoppy.com/Contact.aspx Contact Page]
* [http://www.hightechcville.com/ HighTechCville] uses hcard to mark up people and organizations. See [http://www.hightechcville.com/people/72-eric-pugh Eric Pugh] for an example.
* [http://www.cleanertoday.com/ Cleaner Today] uses hcard to mark up contact details. (see [http://www.cleanertoday.com/Cleaner-Today-a/1.htm Contact Page])
* [http://www.aduk.org Audience Data UK] use hcard on their [http://www.aduk.org/contact.php contact page] and [http://www.aduk.org/directory.php directory of related organisations]
* [http://georgebrock.com georgebrock.com] used hcard for George's contact details
* [http://suggestionbox.com/ SuggestionBox] uses hcard for companies listed on its site. Example: [http://transfercar.suggestionbox.com/ Transfercar].
* [http://www.vcventerprise.com/wp/ Christopia] uses hcard to mark up contact details. (see [http://vcventerprise.com/wp/contact/])
* [http://www.rossirovetti.com/ Rossi & Rovetti Flowers in San Francisco] uses hcard to mark up company details in the about us page of the website. (see [http://www.rossirovetti.com/scripts/aboutus.asp example])
* [http://youtube.com YouTube] uses hcard to identify video contributors (see [http://www.flickr.com/photos/factoryjoe/2793731119/in/photostream/ screenshot]]
* [http://sewmyheadon.com/contact sewmyheadon.com] uses hcard to mark up contact details on contact and about pages.
* [http://www.kleinassoc.com/ Klein & Associates - Estate Planning] used hcard to mark up contact details on law firm's contact page.
* [http://www.markuspage.com/markus/en/contact Markus Kilås] uses hCard to mark up his contact details.
* [http://www.southsidewarriors.com/impressum.cfm Southside Warriors] uses hcard to mark up contact details on the imprint page.
* [http://applesold.com/ Apple Realty - Bristol Real Estate Company] uses hcard to mark up company details in the footer of website.
* [http://www.surfcom.co.uk/app/contact/ Surf Commission] uses hcard to mark up company contact details with option to download vcard.
* [http://www.k9yardpatch.com/contact-us/ K9YardPatch] uses hcard to markup company contact details with option to download.
* [http://www.ecovian.com Ecovian] uses hCard to mark up eco-friendly business contact details, see [http://www.ecovian.com/l/san-francisco-ca/jardiniere-restaurant example]
* [http://www.dischord.com/ Dischord Records] uses hCard to mark up company contact details in the footer of the home page.
* [http://www.thinkambient.co.uk/ ThinkAmbient] uses hCard to mark up company contact details.
* [http://proofile.org/ Proofile] extensive profiles with hCard, vCard, XFN and FOAF support.
* [http://www.ebycattle.com/horses/index.html Eby Ranch] uses hCard for the different branches of the company, with option to download the vCard.
* [http://www.clavex.com/contactus.aspx Clavex - A Latin America Financial Institution ] Uses hCard and geo for the contact information. Simple but effective.
* [http://www.dancefederation.co.uk Dance Federation Salsa Dancing & Jive Dancing Lessons and Events ] Directory for classes, lessons and events users hcard on its lessons and events -- region and url properties are empty. Is that an error?
* [http://mop.ardom.co.il/contact.php Southern Arava Research and Development Center] uses hCard for their contact details on their contact page and in sub pages with contact info. -- one card has two fn properties.
* [http://www.itma.org.uk/find-expert/London] - ITMA Trade Mark Attorney search presents results as hCards
* [http://interkonect.com Interkonect > Website Application Specialists] Office contact details marked up using vcard.
* [http://library.christchurch.org.nz/ContactUs/ Christchurch City Libraries (N.Z.)] contact page plus each of our libraries' individual pages linked from [http://library.christchurch.org.nz/Community/Libraries/ Library Locations map].
* [http://www.leftclick.com/about-us/ LeftClick] uses hcards for contact information.
* [http://ideas.veer.com/skinny Veer's Skinny Blog] implements hcard for comments and post authors.
* [http://wolpy.com/missha Wolpy] Uses hcards for contacts and [http://wolpy.com/missha/profile profile].
* [http://www.veganworldorder.com/index.php?m=vegguide Vegan World Order | Restaurants ] Uses hcards for restaurant listings.
* [http://mahalo.com Mahalo] per the announcement [http://www.seanpercival.com/blog/2008/04/23/mahalo-adds-microformats/]
* [http://www.buythatlocally.com BuyThatLocally ] uses hcards for local business information.
* [http://www.firmendb.de Firmendb] uses hCard for individual business contacts, e.g. [http://www.firmendb.de/firmen/15592.php]
* [http://autopendium.com Autopendium] has resources (e.g. suppliers, clubs) marked up with throughout the site, e.g. [http://autopendium.com/clubs/8-Volvo-Enthusiasts-Club]
* [http://display-block.co.uk Display-Block] uses hCard contacts for People and Companies on my personal Blog.
* [http://bergantinedesign.us Bergantine Design] has contact information marked up with hCard throughout the site
* [http://www.codesignville.com/ Codesignville] uses hCard for his contact details.
* [http://fan-expo.com/Contactez-nous,2 Forum des Acteurs du NumÃ©rique] (a French trade show and exhibition dedicated to content management) uses hCard for contact information (exhibition staff and exhibitors). It also makes use of hCalendar as well as rel-tag when relevant.
* [http://www.corewhisperer.com/ The Core Whisperer] (Paul Ransom) Geological Services uses hCard for contact information.
* [http://chairmanship.mfa.md/en/ The regional presidencies] of Republic of Moldova to the SEECP, CEI, MAG-RACVIAC, SEEHN, CEFTA uses hCard on [http://chairmanship.mfa.md/seecp-contacts/ contacts pages]
* [http://www.viget.com/about/team Viget Labs] - Team page and Individuals' Pages.
* [http://www.re3elstance.com RE3EL STANCE] - Entrepreneurship: Rebel Style.
* [http://www.worldeventsguide.com World Events Guide] - Events occuring around the world marked up with hCard.
* [http://www.amaliahotel.eu/en/contact.html Amalia Hotel Apartments] uses hCard in the contact-info page.
* [http://www.sslcertificaten.nl/contact.php Xolphin SSL Certificaten] uses hCard for their contact details
* [http://examples.tobyinkster.co.uk/hcard hCard + RDFa Example] - raising the bar for parsers...
* [http://competitiondiva.com/ Competition Diva] uses hCard in its page footer (and plans on it for the upcoming profile pages).
* [http://sanisoft.com/ SANIsoft] uses hCard in its page footer
* [http://www.bossalive.com BossaLive] uses [[hcard|hCard]] on user profile pages.
** Example: [http://www.bossalive.com/user/barry Barry's Profile]
** Also uses rel-tag microformat for tagging music. Publishes rel-tags for album, artist and genre.
* [http://hillhursthardware.com/ Hillhurst Hardware's] contact info w.logo uses hcard.
* Birmingham's [http://bigcityplan.org.uk/ Big City Plan] (England)
* Producer [http://www.sun-treader.com/contact.html Christopher Davis] uses hCard markup on his contact page.
* [http://www.tpexpress.co.uk/Liverpool08-Capital-of-Culture/ First TransPennine Express - Liverpool 08, Capital of Culture] - uses hCard to markup suggested venues.
* [http://anand.ws/ Anand's Musings] uses hCard to mark up authors for comments and posts.
* [http://www.onyomo.com/ OnYoMo] uses hCard markup for all addresses listed in their local search results.
* [http://www.dctalks.org/design/ DC Design Talks] used hCard to mark up the speakers for this one-day event.
* [http://www.entidi.it eNTiDi software] provides a basic hCard sample.
* [http://quickbase.intuit.com QuickBase] uses hCard markup on our contact us page.
* [http://www.pixsense.com/contact_us.html PixSense.com] uses hCard markup for addresses across the PixSense website.
* [http://www.areaguides.net areaguides.net] uses hCard markup for all addresses across the site.
** Examples: http://chicagoil.areaguides.net/ypcyellowpg/restaurants.html, http://newyorkny.areaguides.net/hotels.html
* [http://www.ll.georgetown.edu/ Georgetown University Law Library] in Washington, D.C. now uses hCard for our address on all pages. Also, library staff biography pages use hCard such as [http://www.ll.georgetown.edu/staff/bio.cfm?id_no=105 here] and [http://www.ll.georgetown.edu/staff/bio.cfm?id_no=32 here].
* [http://www.ll.georgetown.edu/ Georgetown University Law Library] in Washington, D.C. now uses hCard for our address on all pages. Also, library staff biography pages use hCard such as [http://www.ll.georgetown.edu/staff/bio.cfm?id_no=105 here] and [http://www.ll.georgetown.edu/staff/bio.cfm?id_no=32 here].

* [http://www.mtgd.gov.md/ Ministry of Transport and Road Industry] of Republic of Moldova. First Moldavian governmental site using hCards on [http://www.mtgd.gov.md/ministrul/ staff pages], [http://www.mtgd.gov.md/subdiviziunile-ministerului/ subdivisions page] and in the footer of each page (contact information)
**Only [http://www.mtgd.gov.md/ Romanian] and [http://www.mtgd.gov.md/ru/ Russian] versions available yet
* [http://www.auctionlink.com.au/ AuctionLink] uses hCard for Auctioneer records like [http://www.auctionlink.com.au/Auctioneers/Auctioneer/Cam_Brown_Auctions/ Cam Brown Auctions] (also uses hCalendar)
* [[User:WebOrganics|User WebOrganics]] The Microformats wiki has hcards on its user pages.
* [http://www.ontwerpkliniek.nl Ontwerpkliniek - Bureau voor Visuele Identiteit] uses the hCard contact information at the frontpage and the contact page.
* [http://www.instantdes.com L'instant des...] uses the hCard format for all photographers published on this collective photoblog.
* the mediadesigner groupblog [http://www.pixeltapete.de Pixeltapete] uses the hCard for the contactinformation of the authorpages of [http://www.pixeltapete.de/alex Alex] and [http://www.pixeltapete.de/carsten Carsten] and also for the [http://www.pixeltapete.de/kontakt imprint]. [http://www.pixeltapete.de Pixeltapete] uses its own [http://www.pixeltapete.de/2007/11/hcard-sidebarwidget-fuer-wordpress/ hcard widget] for wordpress sidebars.
* [http://www.thorsten-ott.de Thorsten Ott] uses hCard format for the contact section of his online resume.
* [http://rosebleed.net/ Rosebleed] supports [[hCard user profiles]] - your profile URL is <nowiki>http://rosebleed.net/users/profile.php/</nowiki> followed by your username, e.g. [http://rosebleed.net/users/profile.php/silvermoon82 silvermoon82].
**'''Fixed''' profiles now explicitly mark up 'n' where possible, otherwise omits it
* [http://www.whitepages.com WhitePages.com] Now WhitePages.com main implemented hCard on all its listings. Over 120 million hCards! Includes work information.
* [http://www.warmoth.com Warmoth Guitar Products] features hCard contact information in two places, [http://www.warmoth.com/customerservice/customer.cfm?fuseaction=order How To Order] and all of the [http://www.warmoth.com/catalog Warmoth E-Store]
* [http://www.bbc.co.uk/worldservice/bangladeshboat BBC World Service Bangladesh River Journey] a social network mashup, with hCard & other microformats. See [http://dharmafly.com/blog/bangladeshboat Dharmafly blog discussion].
* [http://www.amants-du-chocolat.net/ ACCP:Les Amants du Chocolat de la Couronne Parisienne] uses hCard on their contact page and in the chocolate maker they've reviewed.
* [http://www.accountviewsoftware.nl/ AccountviewSoftware.nl] makes use of hCards for the dealer directory [http://www.accountviewsoftware.nl/dir/ (directory)]
* [http://www.crystalvision.co.il/ CrystalVision] uses hCard on their contact page and in the footer throughout the site.
* [http://www.indigoclothing.com/ Indigo Clothing] a London based t-shirt company uses hCard with Technorati's Add to Address Book throughout the site in the footer
* [http://www.joshuamcginnis.com Joshua McGinnis] uses hCard to display his contact information to potential clients.
* [http://www.myaffordablemarketing.com/contact.php Affordable Marketing Solutions' contact page] uses hCard with Technorati "Add to Address Book".
* [http://www.bo.ingv.it/contents/INGV-Bologna/Staff.html INGV Bologna] implemented hCards for staff-members, marked-up as HTML table-rows ([[include-pattern]] also used to add organization-name and fax-number to each hCard).
* [http://www.lefora.com Lefora] is a free forum hosting site (using custom forum software). Every user's profile contains an hCard. (Example forum for testing: [http://funstuff.lefora.com funstuff.lefora.com])
* [http://www.handlairsystems.com H&L Air Systems] uses hCard with Technorati link Add to Address Book on all contact pages.
* [http://theultimates.whitepages.com WhitePages.com] A special version of whitepages.com has all its listings marked up in hCard.
* [http://piermontweb.com/contact/ Piermont Web Design] uses hCard on its contact page.
* [http://www.ie.asm.md/en/ The Institute of Power Engineering] of the Academy of Science of Moldova. First Moldavian site using hCards on staff pages, e.g [http://www.ie.asm.md/employees/oleschuk-valentin/]
**Also in Russian: [http://www.ie.asm.md/employees-ru/sit-michail-lvovich/] and Romanian: [http://www.ie.asm.md/angajati/chiorsac-mihail/]
* The good ship [http://styrheim.com/test/leonid.html Leonid Miloslavskiy] spotted in the North Atlantic
* [http://richi.co.uk/blog/2005/12/structured-blogging.html Richi Jennings] has put up his attempt
*[http://oberrycavanaugh.com O'Berry|Cavanaugh] has an organization hCard in the footer on every page as while as individual hCards on the [http://oberrycavanaugh.com/team.php Team] page.
* [http://fortisgc.com Fortis General Counsel], e. g. [http://fortisgc.com/joyce_lan_kim.html Joyce Kim's profile], uses hCard for profile and contact information.
* [http://peryplo.com Peryplo.com], e. g. [http://peryplo.com/personal/7e6786e711c6d051a39a1b7085f34955 Sample Page], uses hCard for Hotels, Gastronomy Places and services for tourists.
* [http://www.navitraveler.com/places/629/ NaviTraveler], e. g. [http://www.navitraveler.com/places/629/Lincoln_Memorial.html Lincoln Memorial], including [[geo|Geo]].
* [http://corewar.atspace.com/about.html sfghoul] has marked her contact info with [[hcard|hCard]]
* [http://www.zaadz.com Zaadz] uses [[hcard|hCard]] and [http://gmpg.org/xfn XFN] for friends on a user's profile page.
*[http://www.xoxiety.com/about.html Xoxiety] uses hCards on its about page, linking data from a within a block of text.
*[http://yedda.com Yedda] - Yedda provides hcard based identities on all of the people's profiles
*[http://openid.ne.jp OpenID.ne.jp] First OpenID provider service in Japan(æ¥æ¬èª). Each personal OpenID page (ex:[http://eouia.openid.ne.jp http://eouia.openid.ne.jp]) is marked up as his hCard. And there is a company hCard on every page, too.
* [http://www.goldenglovepromotions.com/ Golden Glove Promotions] used hcards on the footer of every page to store contact information.
* Australian national news sites The Australian and Australian IT use hCard on their contact pages: [http://www.theaustralian.com.au/contactus The Australian (contact us)] and [http://www.australianit.news.com.au/contactus Australian IT (contact us)]
* [http://www.thekiwiholiday.com/ The Kiwi Holiday] uses hCards for [http://www.thekiwiholiday.com/view-hostels New Zealand Hostels], [http://www.thekiwiholiday.com/view-restaurants New Zealand Restaurants], and [http://www.thekiwiholiday.com/view-activities New Zealand Activities]. Also provides hCard "download to address book" functionality on listing detail pages, e.g. [http://www.thekiwiholiday.com/restaurant/tonys-steak Tonys Steak Restaurant]
* [http://www.qcindustries.com/ QC Industries Conveyors] uses hcards to store contact information in the site footer and in their [http://www.qcindustries.com/news/press-releases/ press releases].
* [http://www.confuciusinstitute.ac.uk/ The Confucius Institute for Scotland at the University of Edinburgh] has their used a hcard to store contact information in the footer of the page.
* [http://admnj.com/ Affiliated Direct Mail] is a New Jersey based direct mail company that has their contact information and footer in hCard format.
* [http://www.golfdigest.com/ Golf Digest] now supports hCard in its [http://www.golfdigest.com/courses/places Course Finder] detail pages. [http://www.golfdigest.com/courses/places/2483 example]
* [http://dev.opera.com/authors/ Dev Opera] Opera's developer site uses hCards on the author details pages.
* [http://chrischerry.name/ Chris Cherry's contact page with his hCard]
* [http://www.kiteboarder.com.au/php/search.php www.kiteboarder.com.au] A new Australian kiteboarding portal. Microformats have been used so that users can export the shops <s>directly to outlook</s>. I was able to learn microformats through the Media 2007 conference in London. Author: Damien King
* [http://krevi.dk/ KREVI] A Danish research institute. Using hCard in the footer of each page and on staff list. This is the first known danish website from the public sector of Denmark using microformats.[http://krevi.dk/om-krevi/organisation/medarbejdere example staff list]
* [http://www.hss.ed.ac.uk/web-team/ College of Humanities and Social Science Web Team's site], University of Edinburgh uses a hCard in the footer of each page.
* [http://www.theglobeandmail.com/ globeandmail.com] Canada's National Newspaper uses an hCard for their contact information.
* [http://www.logisteam.pl/ Krzysztof Rucinski] uses an hCard for his contact details on [http://www.logisteam.pl/kontakt.html Logisteam keylogger contact] page.
* Creation design & marketing has hCards throughout the site, including the [http://www.creation.uk.com/contact/ contact page], the [http://www.creation.uk.com/company/leigh-scott/ company profile pages] and on the [http://www.creation.uk.com/news/2007/06/06/easy-money/#comments-view comments on articles]
*<s> Wikipedia now has a template, [http://en.wikipedia.org/wiki/Template:Hcard-geo hcard-geo], for in-line hCards with coordinates, such as that on [http://en.wikipedia.org/wiki/Engine_Arm Engine Arm]</s>
* [http://www.thomsonlocal.com/ ThomsonLocal.com], major UK business directory publisher, use hcard on the search results and company information pages.
* [http://www.corissia.com Corissia Group Hotels in Crete Greece] have included contact information as a hCard on the footer of every page of the website. There is a multilingual implementation as well.
* [http://zucchetti.co.uk/2007/03/06/simple-address-formatting-solution/ Laura Zucchetti] illustrates a simple address formatting solution as a hCard and marked up in a definition list.
* [http://www.feike.de/Kontakt.html Feike Contact] has a hCard on to top of the page.
* [http://www.londondrum.com/ London Drum] uses a whole host of microformats - there are hcards and geo's on the hotel pages, events are written up in hcalendar format on the cityguide page, and you can also find some hreviews as well (like on the [http://www.londondrum.com/hotels/athenaeum.php Athenaeum Hotel page])
* [http://www.regels-stadskanaal.nl/ Regelingenbank Stadskanaal] has a hCard on each page, containing Geo-information too.
* [http://www.tomstone.se Tom Stone - Trollkarl] has a hCard in the footer of each page of the site.
* [http://www.rolandinsh.lv/ Rolands Umbrovskis]'s home page has hCard in [http://www.rolandinsh.lv/?ro=contacts contact page] and all other pages with contact information.
* [http://www.epiphanysolutions.co.uk/ Epiphany Solutions Ltd] use a hCard on their contact us page. We intend to use the hCard on everypage if successfully implemented, along with a link to the Technorati vCard generator.
* [http://twitter.com Twitter] uses hCard for user information (along with [http://ihack.us/2007/05/14/twitter-gets-microformatted/ several other microformats])
* [http://www.bendodson.com/developer/ Ben Dodson] uses an hCard for his contact details on every page of his site as well as using hCards for any XFN relationships in his blogrolls.
*[http://www.pats.ua.ac.be/group PATS Group Members] uses hCard to mark up member contact information.
*[http://couchsurfing.com CouchSurfing] has limited information in hCard available on members' profiles (such as [http://www.couchsurfing.com/people/guaka Guaka's]).
*Wikipedia-UK (Ukranian)
**Starting to roll out on biographies e.g. [http://uk.wikipedia.org/wiki/%D0%93%D0%B5%D1%82%D1%8C%D0%BC%D0%B0%D0%BD_%D0%92%D0%B0%D0%B4%D0%B8%D0%BC_%D0%9F%D0%B5%D1%82%D1%80%D0%BE%D0%B2%D0%B8%D1%87 Vadym Hetman]
* [http://kpumuk.info Dmytro Shteflyuk] uses an hCard on his [http://kpumuk.info/contact/ contact] and [http://kpumuk.info/curriculum-vitae/ curriculum vitae] pages.
*Wikipedia-EN
**starting to roll-out on articles about people, for example [http://en.wikipedia.org/wiki/Albert_einstein Albert Einstein]. The nature of Wikipedia means that there are a large number of templates to update (Albert's is "infobox scientist; there's also "infobox military people", "infobox musician" and so on, almost ad infinitum). DoB is only included if it's entered using a birth-date template, not as raw text.
**starting to roll-out on articles about places, for example on UK Railway station template, e.g. [http://en.wikipedia.org/wiki/Birmingham_New_Street Birmingham New Street station] (includes Geo); and cities, for example [http://en.wikipedia.org/wiki/New_York_City New York]. See above for note on Wikipedia templates.
**Any Wikipedia editors willing to assist with updating templates should see [http://en.wikipedia.org/wiki/Wikipedia:WikiProject_Microformats Wikipedia's microformat project]; [http://en.wikipedia.org/wiki/Category:Templates_generating_hCards Wikipedia templates generating hCards]
**Unfortunately, [http://en.wikipedia.org/w/index.php?title=Template:Infobox_Protected_area&diff=prev&oldid=152308153 other editors are already breaking some of the implementations on Wikipedia]; e.g. [http://en.wikipedia.org/wiki/Grand_Canyon_National_Park Grand Canyon National Park]; [http://en.wikipedia.org/w/index.php?title=List_of_islands_of_Argentina&diff=prev&oldid=155590535 removal of "region" attributes]
* The [http://www.bayofislands.net/ Bay of Islands] site has implemented hCard on all listing pages, eg: [http://www.bayofislands.net/accommodation/backpackers/saltwater-lodge/ Saltwater Lodge]
* [http://people.cs.uchicago.edu/~mpschaef/index.html Merrick Schaefer] is psyched to use hCard on his homepage for his contact info.
* Christian Hess (from San JosÃ©, Costa Rica) has an hCard in his [http://www.hess-cr.com home page], [http://www.hess-cr.com/utilidades/correo.shtml#postal contact] and [http://www.hess-cr.com/secciones/curriculum/datos.shtml personal rÃ©sumÃ©] pages (all in Spanish). He also recommends using the [https://addons.mozilla.org/es-ES/firefox/addon/4106 Operator] extension in Firefox to check them out.
* [http://www.JamPlanet.com Jam Planet] uses hCard in Contact Us page; application can generate hCard for a contact.
* [http://www.anisfield-wolf.org/ The Anisfield-Wolf Book Awards], designated specifically to recognize works addressing issues of racism and diversity, uses hCard for the author bios of [http://www.anisfield-wolf.org/Winners/PastWinners/ past winners].
* [http://www.buy-our-honeymoon.com/ Buy Our Honeymoon], a [http://www.buy-our-honeymoon.com/registry honeymoon registry] service, uses hCard in their [http://www.buy-our-honeymoon.com/contact Contact Us] page.
* '''W3C webmaster''' [http://www.w3.org/People/Jean-Gui/ Jean-Guilhem Rouel] now has an hCard.
* [http://source.ibegin.com/ iBegin Source] - All 10.8+ million business listings have their information marked up in hCard. Example: [http://source.ibegin.com/california/adelanto/aeronautical-supplies/general-atomics-9779-yucca-rd-1.html General Atomics]
* [http://david.weekly.org/ David Weekly] has added an hCard to his home page for himself.
* [http://ficlets.com/stories/12 Ficlets] story page uses hCard for author bio.
* [http://redmonk.com/contact/ RedMonk Contact page] uses hCard for RedMonk firm as well as each analysts.
* [http://source.ibegin.com/ iBegin Source] uses hCard to identify business information for all 10.5+ million businesses listed.
* [http://cloudislands.com/contact.php Cloud Islands] uses hCard for our Contact Info.
* [http://www.international.unt.edu UNT International] uses hCard to mark up contact information sitewide (see esp. [http://www.international.unt.edu/offices/ieli/people/instructors/profiles the IELI instructor profile listing])
* [http://www.giraffo.de giraffo.de] has different hCards on every page (+ geo in "kontakt")
* [http://www.enap.com ENAP, Inc.] lists the HR Contact in hCard format on the [http://www.enap.com/career.aspx Career Opportunities] page.
* [http://sxsw07.conferenceer.com/people Conferenceer] lists panelists and participants to the 2007 South by Southwest interactive conference in hCard format
* [http://news.stanford.edu Stanford News] (Redesign) hCard in the footer on every page as well as markup for every staff member on the Staff page.
* [http://www.wikiservice.at/fractal/wikidev.cgi?FR/EveMoreau ValÃ©rie-Eve Moreau] has an hCard on her wiki-homepage.
* [http://en.wikipedia.org/wiki/St_George%27s_Minster%2C_Doncaster St George's Minster, Doncaster, on Wikipedia]
* AOL Journals publishes hCards for authors. [http://journals.aol.com/carowill/whats-happening Example]
* Ian McKellar's [http://ian.mckellar.org/ home page] is an hCard that's styled to look like a business card.
* [[Christophe Ducamp]]'s hCard based on [http://www.wikiservice.at/fractal/wikidev.cgi?FR/MicroFormats/ChristopheDucamp wiki personal page] of a wiki-branch which could be dedicated to seed a french group to support microformats. Thanks to Laurent Lunati for the CSS. You can [http://www.wikiservice.at/fractal/wikidev.cgi?action=edit&id=FR/MicroFormats/ChristopheDucamp edit it]. Any suggestions welcome.
* [http://www.matthewwest.co.uk Matthew West] has an hCard on his [http://www.matthewwest.co.uk/email contact] page.
*[http://www.webmaster.waw.pl PaweÅ Wrzosek] Freelance webdeveloper`s portfolio
*[http://www.stanford.edu/ Stanford.edu] hCard markup is included in the footer of the homepage and all subsequent pages within the /home directory.
*[http://openid.ne.jp OpenID.ne.jp] First OpenID provider service in Japan(æ¥æ¬èª). Each personal OpenID page (ex:[http://eouia.openid.ne.jp http://eouia.openid.ne.jp]) is marked up as his hCard. And there is a company hCard on every page, too.
* [http://www.qwertycars.co.uk/garages/mechanics-near-tadworth-kt20.aspx UK Car Garages] Address of car mechanics in the UK, in hCard format.
* [http://www.columbiaautomation.com/sub/contact.php Columbia Automation]'s About Us page every employee marked up as an hCard, as well as having a company hCard with geo information.
* [http://www.pointermix.com Pointermix Design] uses the hCard format.
* [http://eight6.com/contact/ eight6]'s contact page uses the hCard format.
* [http://www.raveaboutit.com.au Rave About It]'s business listings use the hCard format.
* [http://optics.org/cws/Contact/OurTeam.do optics.org]'s team page.
* [http://www.robcottingham.ca/contact Rob Cottingham]'s first foray into microformats is an hCard on the contact page of his personal blog. (He was inspired by Tantek Ãelik's presentation at Web Directions North 2007.)
* [http://redmonk.net/about-this-site Steve Ivy] - hcard about page, includes the usual suspects + XFN on 'url's, photo, amd geo.
* [http://seattleu.edu Seattle University] uses hCard on it's front page and most pages that share an official template.
* [http://www.josemarti.waw.pl Jose Marti XXII Secondary School in Warsaw] includes hCard on Contact and About Author sections
* [http://www.jaama.co.uk Jaama] have their company details as a vCard download on their [http://www.jaama.co.uk/Contact.aspx contact] page.
* [http://3amproductions.net 3AM Productions] has company details marked up as hCard all across the site and particularly for [http://3amproductions.net/jason.php Jason] and [http://3amproductions.net/gilbert.php Gilbert]
* [http://jc-development.co.uk/ JC's Development] has company contact details as hCard.
* [http://berlin.barwick.de/index.html Berlin Guide] is converting their address markup to hcard, e.g. [http://berlin.barwick.de/shopping/kadewe-kaufhaus-des-westens.html KaDeWe]
* [http://www.xlntads.com XLNTads] has their contact information marked up in hCard, as well as their development schedule/timeline in hCalendar
* [http://derrick.pallas.us Derrick Pallas] tells people to look for him here.
* [http://bluemonkcreative.com/contact/ Bill Turner] adds an hCard to the contact page of his freelance business' website.
* [http://www.oppenheim.com.au/ James Oppenheim's blog] includes an inline author hCard in the footer of each page and also on the contact page.
* [http://steinhardt.nyu.edu/ NYU Steinhardt] has [http://steinhardt.nyu.edu/faculty_bios/list/Faculty 240+ faculty bios marked up], e.g. [http://steinhardt.nyu.edu/faculty_bios/view/Susan_Murray].
* [http://www.boogdesign.com/aboutus.html boogdesign.com] has added hCard markup on the contact page.
* [http://www.gptg.org/ Great Places To Golf], hCards for golf clubs around the world, e.g. [http://www.gptg.org/club/12/]
*[http://www.travellerspoint.com/ The Travellerspoint Travel Community] has added hCards to all of their member profiles (e.g. [http://www.travellerspoint.com/member_profile.cfm?user=jax_07]). Details include name, photo, location, notes and url.
* The [http://www.westmidlandbirdclub.com/ West Midland Bird Club] in the English Midlands uses hCard on its [http://www.westmidlandbirdclub.com/ home page], [http://www.westmidlandbirdclub.com/diary/ events diary], [http://www.westmidlandbirdclub.com/club/contact.htm contact pages], [http://www.westmidlandbirdclub.com/site/links.htm links page], [http://www.westmidlandbirdclub.com/club/older.htm list of the world's oldest bird clubs] and in a page footer which is gradually being rolled out across the whole site. {{UpdateMarker}} Page-footer's hCard now has logo, using [[include-pattern]].
*[http://wizardishungry.com/blog/ wizardishungry/blog] has the author's hCard in the footer of every page with a link to X2V.
* [http://www.walkerfineart.com Walker Fine Art Gallery] Most pages contain an hCard in the footer.
* [http://www.brdatasystems.com.au/contact-us.html B&R Data Systems] is an organisation hCard. We have also used the technorati tool to download as a vCard, which I think is useful for a business.
* [http://chewbittel.com/contact.php Chew Bittel Assoc., Inc.] is an organization hCard. It's got abbr's in there, and a duplicate telephone field, and some hidden things. I'm really pushing things to the limit here. This should be a great test for your parser.
* [[User:Steve Ivy|Steve Ivy]]'s [http://redmonk.net/about-this-site/ about page] has his hcard, including a link to Technorati's contacts feed to let visitors download his contact information.
* Scott Allan Wallick's hCard is [[User:ScottWallick|his user page]] and on his blog, [http://www.plaintxt.org/about/2/ plaintxt.org]
* [[User:Bob_Jonkman|Bob Jonkman's hCard]] '''on this 'wiki''''
* [http://thetenwordreview.com The Ten Word Review] simply contains ten word long reviews. All reviews are marked up as [[hreview|hReviews]], and user information is marked up as hCards.
*OffshoreAgile.com, a subsite of Starsoft Development Labs, uses hCard in the [http://www.offshoreagile.com/company/contact/ Starsoft Contacts] and Media Inquiries sections
*T-Mobile uses hCard for the [http://t-mobilepressoffice.co.uk/press/contact-details/ T-Mobile UK Press Contact Details page], as well as for some of the latest press releases
* Psychology Press and Routledge's Behavioral Sciences' publishing division have implemented hCard on their contact pages on 17 of their websites (example on the contact page on their [http://www.clinicalpsychologyarena.com/contact/ Clinical Psychology Arena])
*[http://72ppi.us 72ppi], uses hCard in the footer.
*[http://www.csarven.ca Sarven Capadisli] uses hCard throughout the site (including user comments in articles).
* [https://www.urbanbody.com/information/contact-us Urban Body Men's Clothing] uses hCard for business locations and hCalendar for business hours.
* [http://www.iqair.us/ IQAir North America], uses hCard for contact information.
* [http://www.infoiasi.ro/ The website of the Faculty of Computer Science], "A. I. Cuza" University Iaşi, Romania uses hCard for each staff member.
* [http://www.finds.org.uk/ The Portable Antiquities Scheme at the British Museum] hCards added to footer of every page and to contacts section. Working on adding more and getting it right.
* In [http://www.ideasfornet.com/ IdeasForNet.com - the ideas repository] hCards were implemented partially in the footer of each page, and more comprehensively in the contact and about pages.
* The [http://www.cst.ed.ac.uk/ Centre of Canadian Studies] at the University of Edinburgh use hCards for contact information in the footer of their site.
* [http://www.theatrestudies.llc.ed.ac.uk/ Theatre Studies: European Theatre] at the University of Edinburgh use hCards for contact information on their home page
* [http://www.carolinemockett.com/design/about.aspx Caroline Mockett] has an hCard on her About Me page
* [http://wait-till-i.com Christian Heilmann] has a footer address using hCard
*[http://www.audience-response-rentals.com/ Audience Response System Rentals] uses hcard as a popup in the site accessibility area (lower right) for easy copy and paste of address by customers.
* [http://www.fischsolutions.com/ Fisch Internet Solutions] uses an embedded hCard and a vCard download to provide customers an easy way to contact them on their [http://fischsolutions.com/contactus.html Contact Us] section of the website.
* [http://www.micatholicconference.org/ Michigan Catholic Conference] uses hCard for contact information in the sidebar.
* [http://www.adambunn.co.uk/ Adam Bunn] provides contact details in the sidebar using hCard.
* [http://www.belkin.com/pressroom/releases/uploads/10_10_06NotebookExpansionDock.html Belkin Press Releases] are using hCards for PR contacts and corporate offices.
* [http://mybank.com myBank.com] uses hCard for its listings of every branch of every FDIC-insured bank in the United States.
* [http://leftlogic.com Left Logic] uses hCard for embedded contact information.
* [http://inga-art.co.uk/artist Inga Scholes] uses hCard for contact information in the sidebar.
* [http://www.lussumo.com/ Lussumo] uses hCards on user profile pages in its open-source [http://www.getvanilla.com/ Vanilla] Discussions Forum software.
* [http://www.creative-ways.nl/ Ron Kok] uses hCards to mark-up the names and URLs of commentors on his blog. He also uses hCards in combination with XFN in his blogposts to refer to friends, and has an hCard for himself on every page on his blog.
* [http://tagg.no Tagg Media] uses hCard for [http://heine.tagg.no/contact.php contact information] and provide link to vCard download in the contact section.
* The article about the fictitious Matrix character [http://en.wikipedia.org/wiki/Neo_%28The_Matrix%29 Thomas A Anderson in Wikipedia] is now marked up with hCard.
* [http://dconstruct06.madgex.com/ d.Construct 2006 Backnetwork] uses hCards for conference delegates (and provides the markup so that delegates can copy and paste cards into their own sites).
* [http://www.brown.edu Brown University] now uses hCard on the front page
* [http://www.wideblueyonderweb.co.uk Dunks at Wide Blue Yonder Web Design] has added hCard markup on his [http://www.wideblueyonderweb.co.uk/wbyw/pages/contact.htm contact page] and is looking to implement it on all past & future contact pages for clients.
* [http://southamptonrubberstamp.com Southampton Rubber Stamp Company] now has hCard markup with a vCard download link on every page.
* [http://barefoot-ceramics.com Barefoot Ceramics paint your own pottery studio] (in Newport, South Wales) has added hCard markup to its [http://barefoot-ceramics.com/find#address "Find"] page and other address instances. They hopes to implement hCalendar event lists as soon as an ics to hCalendar PHP class can be found or written.
* [http://dsingleton.co.uk/ David Singleton] has added a hCard to his blog.
* [http://www.thestreet.org.au The Street Theatre (Canberra, Australia)] has added hCard markup to its [http://www.thestreet.org.au/contact.htm Contact Us] page. hCalendar markup will soon be added for all of our performances.
* [http://www.informatik.uni-hamburg.de/SVS/personnel/henrich/index.php Henrich C. Pöhls] has marked up his about page using hcard, including his PGP-Key that is stored in an abbr title, using class=key.
* [http://www.yalf.de Yalf Webentwicklung] has [http://www.yalf.de/kontakt contact information] available as hCard (and vCard).
* [http://www.zeldman.com/about/ Jeffrey Zeldman]. Jeffrey Zeldman has marked up his about page using hcard.
* [http://WhereAreYouCamping.com Where Are You Camping]. hCards for all members and camps, employing the include pattern as well. AFAIK this is the first Burning Man related microformats implementation, not to mention addresses in Black Rock City.
* [http://www.clacksweb.org.uk Clackmannanshire Council ]. hCard is implemented for all contact details across the site, and for specific individuals such as elected members (Councillors).
* [http://www.webdirections.org Web Directions]. hCard is used as contact information for the conference, while speakers are marked up with hCard.
* [http://www.markthisdate.com/contactform.html MarkThisDate.com]. An hCard is implemented on our contact form. For our calendars hCalendars will follow as soon as possible.
* [http://www.msiinet.com/contact/ MSI Systems Integrators] has its "Contact MSI" page encoded with hCards.
* [http://www.coolblue.nl/ Corporate website of Coolblue BV]. hCards were implemented in both the footer of each page, and in the "News" section for press contact information.
* [http://www.besancon.fr/index.php?p=32 Official site of BesanÃ§on (France)] uses hCard for each page concerning the small towns surrounding BesanÃ§on.
* [http://2006.dconstruct.org/speakers/ d.Construct 2006 conference speakers list] is implemented using hCards.
* [http://local.yahoo.com Yahoo Local] now supports hCards for business and places in the search results
* [http://learningtheworld.eu/imprint/ Learning the World] has hcard information on the imprint, alas we didn't succeed to mark-up the work phone and fax numbers properly.
* The [http://www.fuckparade.org Fâparade] website uses hCard, though I didn't find a type to distinguish mobile and landline phone numbers.
**Use <code>cell</code> for mobiles.
* [http://www.miranet.nl/contact.htm Miranet Webdesign] have added a hcard to their [http://www.miranet.nl/contact.htm 'contact' page]
* [http://weblog.200ok.com.au/ Ben Buchanan] has added a vCard to the [http://weblog.200ok.com.au/about/ 'About' page on The 200ok Weblog]
* [http://www.radiantcore.com Radiant Core] has their contact information [http://www.radiantcore.com/contact/ available in hCard].
* [http://www.mikerumble.co.uk/ Mike Rumble] has [http://www.mikerumble.co.uk/contact.html uploaded his hCard].
* [http://www.saumag.edu/ Southern Arkansas University] has its contact footer encoded as hCard
* [http://main.uab.edu/ University of Alabama at Birmingham] has its contact footer encoded as hCard
* [http://www.capital.edu Capital University] has contact footer and bloggers' names encoded as hCard. Also, all page-specific contact information is encoded as hCards (see [http://www.capital.edu/Internet/Default.aspx?pid=67 Admissions] page for an example)
* [http://main.uab.edu/shrp/ UAB School of Health Professions] uses hCard in its contact footer
* [http://green.carisenda.com/ Stephen Stewart] has his hCard on the front page of his weblog ('You are here' section)
* [http://www.direction.es/ Direction] uses hCard for contact information.
* [http://audiobank.tryphon.org AudioBank] uses hCard to display member informations.
* [http://www.vivabit.com/atmedia2006/speakers/ @media speakers] are marked up with hCard (photos depend on BASE tag support which makes this a good test case)
* [http://www.dougransom.com Doug Ransom] uses hCard for his financial advisory practice.
* [http://rubyandrails.org/usergroups/newcastle/members.html ncl.rb] uses hCard for contact information.
* [http://www.snowinteractive.com/ Snow Interactive] uses hCard for contact information.
* [http://flickr.com Flickr] now supports [[hcard|hCard]] and [http://gmpg.org/xfn XFN] on profile pages. See [http://flickr.com/photos/factoryjoe/113866484/ screenshot of Flickr UI in Flock browser using Flocktails extension - March 17th 2006].
* [http://www.ndiyo.org/contact Contact information for the Ndiyo project]
* [http://www.pixelenvy.co.uk/ Pixel Envy] uses hCard for contact information on every page
* [http://stilbuero.de/contact/ Klaus Hartl] uses hCard in the sidebar for contact information (maybe easier to parse through delivering xhtml as xml).
* [http://charlvn.virafrikaans.com/contact Charl van Niekerk's hCard]
* [http://billy-girlardo.com/WP/ BillyBLOGirlardo] uses hCard for contact information.
* [http://www.hicksdesign.co.uk/ Hicksdesign] uses hCard for contact information.
* http://www.gr0w.com/articles/press/growsearch_launched_press_release/ - hCard in a press release for the press contact info
* http://www.redmonk.com/cote/archives/2006/03/testing_out_mic.html - hCard with explanation
* [http://andy.ciordia.info/ it's my island], personal blog, hcard on the ''[http://andy.ciordia.info/pages/about_me About the Writer]'' page. [[User:Ciordia9|Andy Ciordia]]
* [http://www.windowonwoking.org.uk/ Window on Woking], a local community site in the UK, uses hCard in the homepage of each member organisation and local Councillor.
* [http://ChunkySoup.net/ ChunkySoup.net] has redesigned using hAtom 0.1 and hCards on the entire site -- by [[User:ChrisCasciano|Chris Casciano]]
* [http://www.30boxes.com/ 30 Boxes],a social calendar application and digital lifestyle aggregator, automatically creates an hcard for you with your account. It is found under Settings > Syndication.
* [http://www.nearwhere.com/ Nearwhere.com] allow you to put an hcard on an interactive map.
* [http://www.brentozar.com/ Brent Ozar] added a [http://www.brentozar.com/contact.php contact] page hCard.
* [http://www.kerihenare.com/ Keri Henare] has rewritten his [http://www.kerihenare.com/contact/ contact] page hCard. Now using <code><object></code> instead of <code><img></code> for photo. (Thanks Brian Suda for updating the vCard converter)
* [http://michaelraichelson.com/contact/ Michael Raichelson] had an hCard on his contact page before SXSW, but never thought to add it here until Tantek requested it.
* [http://www.commoner.com/~lsimon/lindsey_simon_hcard.html Lindsey Simon] has added an hCard to his website as per Tantek's SXSW request for folks to try it
* [http://www.davidgagne.net/ David Gagne] has an hCard in his sidebar.
* [http://www.churchzip.com/map/ Churchzip.com/map] and [http://www.skiwhere.com/map/ Skiwhere.com/map], provide churches, hotels, and ski resorts on the same maps. Locations are formatted as hCards.
* All [http://www.iqdir.com/ IQ Directory Solutions] Yellow Pages web portals use [[hcard|hCard]] markup on listings. For example [http://www.yellowpages-cambodia.com/ Cambodia Yellow Pages] and [http://www.superpages.com.my/ Malaysia Super Pages]
* Ning's cloneable Group app uses fuzzy matching to map custom fields to [[hcard|hCard]] markup on its [http://group.ning.com/index.php?controller=person&action=view&content=JonathanAquino profile] pages.
* [http://claimid.com/factoryjoe Chris Messina' ClaimID hCard]
* [http://factoryjoe.com/ Chris Messina' homepage]
* [http://flock.com/about Flock About]
* [http://tantek.com/microformats/2006/03-01-TechPlenAgenda.html Agenda: W3C Technical Plenary Day, March 1 2006] has [[hcard|hCard]] and [[hcalendar|hCalendar]] markup. ([http://www.w3.org/2006/03/01-TechPlenAgenda.html original here]).
* [http://www.gr0w.com/articles/press/growsearch_launched_press_release/ GrowSearch Launched (Press Release)] uses an hCard to provide Press Contact Point.
* The [http://www.arborday.org/ National Arbor Day Foundation] has started using hCards for their [http://arborday.org/programs/conferences/communityforestry/index.cfm upcoming] [http://arborday.org/programs/conferences/hazardtrees-treeplanting/ conferences].
* [http://www.multipack.co.uk The Multipack] has numerous hCards, especially on the [http://www.multipack.co.uk/members/ members page], as well as the next meeting information.
* [http://deadringrancor.livejournal.com/ Justin McDowell] used an hCard when [http://deadringrancor.livejournal.com/221332.html referring to a person in his blog post]
* [http://davecardwell.co.uk/cv/ Dave Cardwell] has included his hCard in his Curriculum Vitae.
* [http://blog.usweb.com/ Shaun Shull] has written a great post on [http://blog.usweb.com/archives/how-microformats-affect-search-engine-optimization-seo How Microformats Affect SEO], and has included his [[hcard|hCard]] as one of the examples.
* [http://www.thefutureoftheweb.com/ Jesse Skinner] has written a simple [http://www.thefutureoftheweb.com/blog/2006/1/hcard tutorial with examples]
* [http://www.w3.org/2005/12/allgroupoverview.html 2006 W3C Technical Plenary Week] has marked up the venue, contacts, and program committee members all with hCard.
* [http://www.avf-nexus.co.uk AVF-Nexus] have a hCard on their [http://www.avf-nexus.co.uk/contact/ contact page] - (by [http://creation.uk.com Creation"])
* [http://www.thefantasticos.com/andrew/ Andrew White] posted [http://www.thefantasticos.com/andrew/index.php/my-hcard/ his hCard] and [http://www.thefantasticos.com/andrew/index.php/62/microformats-the-should-have-been-obvious-web-dev-tool/ blogged about it].
* [http://www.2sheds.ru Oleg "2sheds" Kourapov] in his [http://www.2sheds.ru/blog/ blog] ([http://suda.co.uk/projects/X2V/get-vcard.php?uri=http://www.2sheds.ru/blog X2V]) has turned personal profile into hCard ([http://suda.co.uk/projects/X2V/get-vcard.php?uri=http://www.2sheds.ru/blog/hcard.html X2V]) and his blogroll - into combination XFN/hCards ([http://suda.co.uk/projects/X2V/get-vcard.php?uri=http://www.2sheds.ru/blog/friends.html X2V])
* [http://www.approveddesign.co.uk Approved Design Consultancy] have a hCard on their [http://www.approveddesign.co.uk/about/contact/ contact page] as well as on their [http://www.approveddesign.co.uk/about/people/ people section] - (by [http://creation.uk.com Creation"])
* [http://weblog.200ok.com.au/ Ben Buchanan] and [http://www.griffith.edu.au/cgi-bin/phone_search.pl?string=colin+morris&format=search Colin Morris] have [http://weblog.200ok.com.au/2006/01/griffith-phonebook-adds-hcard-and.html implemented hCards and vCards] for the [http://www.griffith.edu.au Griffith University] [http://www.griffith.edu.au/find/content_phonebook.html online phone book]. Eg. [http://www.griffith.edu.au/cgi-bin/phone_search.pl?string=ben+buchanan&format=search Ben's vCard] and [http://www.griffith.edu.au/cgi-bin/phone_search.pl?string=colin+morris&format=search Colin's vCard]
* WWF-Australia [http://wwf.org.au/about/contactdetails/ contact details page]
* [http://rasterweb.net/raster/ Pete Prodoehl] used the hCard format on his [http://rasterweb.net/raster/contact.html Contact page] and his [http://rasterweb.net/portfolio/ Portfolio]
* [http://amette.eu amette] uses the hCard format in a module of his TikiWiki powered blog and a more complete hCard on his [http://amette.eu/contact contact page]
* [http://staff.washington.edu/oren/weblog2/ Oren Sreebny] has an hcard on his blog main index template
* [http://www.cs.brandeis.edu/~zippy/ Patrick Tufts] has an hCard on his homepage.
* [http://ascii20.blogspot.com/ Mathias Kolehmainen and Jamie Taylor] have hCards on their weblog.
* [http://www.hoppsan.org/jamesb/blogger/ Barnaby James] has a hCard on his weblog.
* [http://esa-education.com/schools/map ESA Education] Uses hCards for their 100+ schools and each of the individual school sites.
* [http://www.thereisnocat.com/#vcard Ralph Brandi] has added an hCard to the sidebar of his weblog as a result of Tantek Ãelik's portion of the Microformats presentation at SXSW 2006.
* [http://www.pierce.ctc.edu/ephone/ Pierce College] -- community college directory uses hCard on all individual directory entries.
* [http://www.ukoln.ac.uk/web-focus/events/workshops/webmaster-2006/ the Institutional Web Management Workshop 2006] have marked up all their [http://www.ukoln.ac.uk/web-focus/events/workshops/webmaster-2006/committee/ speakers with hCard].
* http://wikitravel.org/en/Singapore/Sentosa. Wikitravel is experimenting with hcard on its travel guides. This guide uses hcard for all its business listings. More info on http://wikitravel.org/en/Wikitravel_talk:Listings.
* [http://www.musik-erber.de/ Musik-Erber] uses to present contact information at the sidebar
* [http://cdevroe.com/about/#contact Colin D. Devroe] uses hCard to display his contact information on his about page
* The ECS (Scool of Electronics and Computer Science at the University of Southampton) [http://www.ecs.soton.ac.uk/people People Pages] use vCard. Contact cjg@ecs.soton.ac.uk if there's any bugs.
* [http://www.southwestern.edu/~ramseyp Pat Ramsey] has his contact information on his blog marked up with hCard. Contact [mailto:ramsey.pat@gmail.com ramsey.pat@gmail.com] if there are any bugs there.
* [http://www.vyre.com/company/contact-us/ VYRE] is a CMS development company with a "contact us" hCard
* [http://www.lefdal.cc/info.php Alf KÃ¥re Lefdal] uses hCard in the markup of his contact information
* [http://www.pignwhistle.com.au/ Pig N Whistle, a chain of pubs in Brisbane, Australia] is using hcard to mark up all the contact pages for its outlets and head office
* [http://kollitsch.de/ Patrick Kollitsch] has built his personal Profil as hCard
* [http://www.audiophile.pl/ Car Audio] uses the hCard in his contacts section.
* [http://www.hbs.edu/faculty/dspar/ Harvard Business School] has hCards on their faculty pages
* [http://openmikes.org/ openmikes.org] uses hCards for open mike venue addresses in its listing detail pages.
* [http://www.intertecnollc.com/ InterTecno, LCC] publishes an hCard on the home page and contact page.
* [http://canaltcm.com/ver/sobre-tcm Turner Classic Movies TCM Spanish website] has published contact details as a hCard
* [http://rejuvenation.com/ Rejuvenation] is now using hCard for contact information.
* [http://www.mattash.com/contact/ Matthew Ash] uses the hCard in his contacts section.
* [http://yarmouthguide.com/business.php Yarmouth Guide] uses hCard for each business details page.
* [http://www.merchantcircle.com MerchantCircle] has embedded an hCard in every one of their 15+ million US business listings.
* [http://citizenspace.us/citizens Citizen Space Citizens] is a list of tenants for a coworking space in San Francisco. The issue was raised that ''nicknames'' are usually located in the middle of ''fn'', which is not valid as per the [http://microformats.org/wiki/hcard-brainstorming#Implied_FN_from_N Implied_FN_from_N] rule. It seems that it should be possible, however, to include a ''nickname'' in the middle of an FN or even between a ''given-name'' and a ''family-name''.

* [http://www.brownbook.net The Brownbook - the open yellow pages] The Brownbook is a peer-produced (like a wiki, but not a using a wiki engine) local business search website. It Uses hCard to allow users to export local business contact details to Outlook or other desktop apps, plus for providing detailed maps from Google.
** Example of a search results page: [http://www.brownbook.net/business/search/?tag=hair+in+egham&x=21&y=4 Hairdressers in Egham]
*** '''suboptimal''': Adresses, e.g "2 Station Rd North, Egham, Surrey", are marked up as <code>street-address</code>
** Example of a single business's details [http://www.brownbook.net/business/view/122516 The Hair Emporium].
*** '''suboptimal''': Adresses, e.g "2 Station Rd North, Egham, Surrey", are marked up as <code>street-address</code>
* [http://www.Sylphen.com Sylphen] is a IT-solutions-provider and uses hCards on the [http://www.sylphen.com/content/kontakt/kontakt.htm Contact]
** '''invalid''' two of the three examples lack the required <code>fn</code> or <code>fn org</code> property
*[http://en.wikipedia.org/wiki/Category:Templates_generating_Geo Wikipedia templates generating Geo]
**'''hidden''' - for example [http://en.wikipedia.org/wiki/List_of_Minnesota_State_Parks List of Minnesota state parks]; [http://en.wikipedia.org/w/index.php?title=Alberta_Highway_60&diff=prev&oldid=157308650 Alberta Highway 60]
**NOte also removal of hCard properties, e.g. [http://en.wikipedia.org/w/index.php?title=List_of_Gaudi_Buildings&diff=prev&oldid=157704557 List_of_Gaudi_Buildings]
* [http://www.reefscape.net reefscape.net] Personal blog page that has a hidden hCard in the about section on every page. A vCard can be downloaded using the Technorati service.
**Hidden.
* [http://www.cosmotourist.com www.cosmotourist.com] and [http://www.cosmotourist.de www.cosmotourist.de] A new German and English portal around travel tips. Using hidden hCard for hotel listings, wherever address data is available.
**Hidden.
* [http://www.venncommunications.com/contact/ Venn] uses a hidden hCard on the contact page.
**Hidden.
* [http://www.last.fm Last FM] has hCards hidden on their profile pages e.g. [http://www.last.fm/user/Crok/?scrobbling=t1].
**Hidden.
* [http://krisswatt.co.uk/ Kriss Watt] has hidden an hCard his blog footer.
**Hidden.
* [http://www.fberriman.com/ Frances Berriman] has a hidden vCard in the footers of her website.
**Hidden.
* [http://www.candlescience.com/ CandleScience Candle Supply] added a hidden hcard sitewide.
**Hidden.
* [http://www.meryl.net/ Meryl K. Evans] has a hidden hCard on her homepage.
**Hidden.
* [http://www.highflyerscareers.com High Flyers Careers], India's first flight-crew placement agency uses microformats for their [http://www.highflyerscareers.com/corporate/ corporate information] page. Using standards couldn't be easier or better.
**Has honorific prefixes as part of "fn", rather than marked up separatley.
* Spotstor.com eg - [http://spotstor.com/] uses hCard on profile pages (where user has elected to show contact information).

* [http://www.naturalengland.org.uk/press/default.htm Natural England] (new UK government agency, formed 2006-10-01).
** No "fn" - which makes it invalid.
*[http://drop-off.co.uk G3:2] uses hCard with geo tags in the copyright and on the about me page
** Address data is hidden using CSS.
* [http://zdnet.co.uk/misc/contact/ ZDnet Contact Us Page] supports [[hcard|hCard]].
** by [http://www.subtleasafish.com/ James Myers] and [http://www.fromthefrontend.co.uk/2006/11/23/zdnet-uses-microformats/ David Long]
**Images and e-mail addresses are hidden; telephone numbers do not comply with [http://en.wikipedia.org/wiki/E.123 E.123]
* [http://gbraad.nl/ Gerard Braad] has published an example on his [http://gbraad.nl/site/?p=profile profile] page that is almost consistent with his original [http://gbraad.nl/files/gbraad.vcf vCard] file. Also progress is made for transforming his [http://files.gbraad.nl/foaf.rdf FoaF] file to a hCard encoded representation (also done for my spouse:[http://spouse.gbraad.nl/site/?p=profile Yong Yuan])
** (2005-09-27) PASSED, PASSED
** WARNINGS
*** uses 'n given-name' and 'n family-name' instead of nesting the given- and family- names inside the 'n'
*** has one 'tel' value with a bunch of values stuffed in
*** probably more problems --[[User:RyanKing|RyanKing]] 17:19, 5 Jan 2006 (PST)
* [http://kinrowan.net/ Cori Schlegel] [http://kinrowan.net/blog/wp/archives/2005/07/08/a-problem-with-the-structured-blogging-plug-in-for-wordpress/ discusses how he has updated] [http://kinrowan.net/blog/contact his contact page with hCard]
** INVALID - using 'prefix' instead of 'honorific-prefix' and type's in classnames (in both adr and tel) and has two photo's (the second could be 'logo') --[[User:RyanKing|RyanKing]] 15:15, 5 Jan 2006 (PST)
* [http://landsbank.fo/#hCard Landsbanki FÃ¸roya]
** INVALID - using embedded RDF/XML invalidly

* [http://www.yellowpencil.com/contact/ Yellow Pencil] Using microformats to present company contact information
** First hcard has empty "fn" and no "n". "fn" should be with "org" -- [[User: ScottReynen |ScottReynen]] 21:29, 19 Jun 2006 (CST)

* [http://www.art-switch.com/ArtSwitch/contactUs.html Art-Switch Exchange Limited] uses hCard for their contact details on their contact page.
* [http://onyomo.com/ OnYoMo] uses hCard markup for all addresses listed in their local search results.
* [http://vcardplus.info/show.asp?uid=Z9959-06323 Greg Bays], the author of vCardPlus! has made his sites vCard display page hCard complaint.
* [http://www.rosenblittdentistry.com/contact.php Dr. Jon Rosenblitt] uses hCard icon with '''Add to Address Book''' link.
* [http://www.nfwebsolutions.com/ New Frontier Web Solutions] uses hCard on their front page along with a link pointing to Brian Suda's [http://suda.co.uk/projects/X2V/get-vcard?uri=http://www.nfwebsolutions.com/ X2V].
* [http://shiftingpixel.com/about/the-artist shifting pixel photoblog] has published an hCard.
* [http://thoughtport.blogspot.com/ Aiden Kenny] hasn't published his hCard yet, but he has [http://thoughtport.blogspot.com/2005/07/elemental-particles-of-web.html published his hCard icon]: http://photos1.blogger.com/blogger/4224/444/320/AK-Hcard-icon.gif
* [http://thedredge.org Andy Hume] uses hCards to mark-up the names and URLs of commentors on his blog, e.g. his [http://thedredge.org/2005/06/using-hcards-in-your-blog/ blog post on "Using hCards in your blog"].
* [http://www.bidclix.com/ BidClix]'s [http://www.bidclix.com/AboutContact.html Contact BidClix] page has it's ''contact info'' marked up with an hCard.
* [http://suda.co.uk/ Brian Suda] has managed to embed a photo in [http://suda.co.uk/contact/ his hCard] through the [http://www.ietf.org/rfc/rfc2397.txt data URI scheme] by converting the image to BASE64 code. View the Source to see how this is accomplished. [http://suda.co.uk/projects/X2V/get-vcard.php?uri=http%3A//suda.co.uk/contact/ The X2V link] will extract the image and encode it for a vCard which will be displayed in some address book applications.
** Inspired by this I thought to try the same for SVG at [http://barefoot-ceramics.com/find Barefoot] ...
** <img class="photo" style="display:none;" src="data:image/svg+xml;text,<?xml version='1.0' encoding='UTF-8' standalone='no'?><svg xmlns:svg='http://www.w3.org/2000/svg' xmlns='http://www.w3.org/2000/svg' version='1.0' width='50' height='80' id='svg3957'><defs id='defs3959' /><path d='M 28.91433,...32.192802 z' style='fill:#cc4d00;fill-opacity:1;fill-rule:evenodd;stroke:none;stroke-width:0.625;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1' id='path9551' /></svg>" alt="Barefoot">
** Does it work?? Well it parses OK. Some automated tools replace the < with %3C (etc., e.g. Brian Suda's vCard form). Unfortunately Kontact (KDE contacts tool) doesn't handle SVG as a vCard photo or logo format - I don't know if this is a standard. It seems it could work and maybe even does somewhere. Maybe the text field needs to be Base64 encoded? ... see [http://slashdot.org/~pbhj/journal/142382 pbhj's slashdot journal] for a bit more on this.
* [http://cinematreasures.org Cinema Treasures] uses hCard to markup venue information for 10,000+ movie theaters.
* [http://www.w3.org/People/Connolly/events/ Dan Connolly's index of events and talks] has hCards for many of the people he has met at those events. In Mar 2006, he moved a bunch of hotel contact info from his PDA to this page; it's now up to 32 hCards.
* [http://doncrowley.blogspot.com/ Don Crowley] has published [http://www.crowley.nl/hcard.html his hCard] as well as a nifty hCard button: http://www.crowley.nl/images/hcard.png
* [http://loadaveragezero.com/hnav/contact.php Douglas W. Clifton] added all types of contact information
* [http://eventful.com Eventful] publishes all of its venue information pages with embedded hCards.
* [http://www.iowamilitaryveteransband.com/members/ Iowa Military Veterans Band Contacts] - 95 hCards [http://weblog.randomchaos.com/archive/2005/10/24/Microformats/ marked up by Scott Reynen]
* [http://JackWolfgang.blogspot.com Jack L. Wolfgang II] has [http://jack.randomata.com/resume/ converted the addresses in his resume to hCards].
* [http://www.efas.fupl.asso.fr/efas/_Mathieu-Drouet_.html Mathieu Drouet] and [http://www.efas.fupl.asso.fr/efas/_Annie-Leger_.html Annie Leger] both have hCards
* [http://www.oliverbrown.me.uk/ Oliver Brown] has published his hCard.
* [http://www.paradigmproductions.org/contact/ Paradigm Productions] published a vCard as a <code>ul</code> (marked up by [http://www.linkingarts.com/ Peter Jacobson])
* [http://www.splintered.co.uk/ Patrick H. Lauke] has marked up [http://www.splintered.co.uk/about/ his contact info with hCard].
* [http://blah Paul Schreiber has published his hCard on [http://paulschreiber.com/about/?contact his about page].
* [http://paulschreiber.com/blog/ Paul Schreiber]'s [http://concerts.shrub.ca/ Sunnyvale House Concerts] site publishes hCards for upcoming artists, as well as an hCard for the page itself. In addition the [http://concerts.shrub.ca/shows Past Shows] page contains hCards for all past artists.
* [http://www.paulmichaelsmith.com/blog/hcard.htm Paul Smith] has created an hCard page which is Human Readable, and a link to X2V passing the same hCard page to generate a vCard.
* [http://www.windley.com/archives/2005/07/hcards_trying_o.shtml Phil Windley has published] [http://phil.windley.org/hcard.html his hCard].
* [http://www.go-curiosity.com/about.htm Piercarlo Slavazza] has published an hCard.
* [http://zooibaai.nl/ Rob Mientjes] has published his hCard on [http://zooibaai.nl/about/ his about page].
* [http://rbach.priv.at/Contact Robert Bachmann] has published his hCard and [http://rbach.priv.at/Images/hcard a button].
* [http://blah Scott Reynen has published his hCard on [http://www.randomchaos.com/document.php?source=scott_reynen his profile page].
* [http://www.stackframe.com/ StackFrame, LLC] has published [http://www.stackframe.com/people/ employee] and [http://www.stackframe.com/contact/ general] contact information as hCards.
* [http://www.wolfsreign.com Steven Ametjan] has published his hCard on [http://www.wolfsreign.com/about/ his about page].
* [http://tantek.com/microformats/2005/syndicate/speakers-list.html Syndicate - Speaker List] as a set of hCards
* [http://tagcamp.org/index.cgi?ContactList TagCamp contact list]
* [http://www.deadringerart.com/ The Brothers McDowell] have hCards at their Contact page.
* [http://twinsparc.com/ Twinsparc] put an hCard in the header and footer of all their pages.
* [http://tantek.com/microformats/2005/web2/speakers.html Web 2.0 Conference speakers page marked up with hCard]
* [http://www.uoguelph.ca/directory/ The University of Guelph] includes hCard info in its directory.
* [http://www.echildcare.com.au/ The Australian Child Care Index] has over 3000 entries listing child care services across Australia - and every single one is marked up with an hCard!
* [http://www.cadforless.com/partners/ CADforless, Inc.] we listed our partners using hCard
* [http://avon.com/ Avon] - publishes all 40,000+ Avon representatives' contact info with hCard.
* [http://flock.com/about Flock About] page supports hCard microformat.
** by [[implementations#Flock|Flock]]
* [http://www.iowamilitaryveteransband.com/members/ Iowa Military Veterans Band]
* [http://www.nature.com/ Nature homepage], uses [[XOXO]].
** by [[implementations#Nature Publishing Group|Nature Publishing Group]]
* [http://concerts.shrub.ca/shows Sunnyvale House Concerts] supports hCard and [[hcalendar|hCalendar]].
* [http://www.bath.ac.uk/ University of Bath] [http://www.bath.ac.uk/contact/ Person Finder] supports hCard, e.g. see [http://www.bath.ac.uk/person/139897 Mr T Natt] page.
* [http://www.monster-prague.cz/ Monster Prague Openings] supports hCard, e.g. home page, contact list to come.
* [http://www.vogelelaw.com/contact.html Colette Vogele] has an hCard on her contact page with many types of name and contact information. (Marked up by [http://www.talkingtiger.net Naomi Raine]).
* [http://www.fixya.com/repair/cars/us/ca/san_francisco FixYa] (the troubleshooting site) has an hCard (vCard) in the repair directory displaying information about all kinds service providers.

== examples by category ==
'''Want hCard?''' Get started with writing an [[hcard|hCard]] using the [http://microformats.org/code/hcard/creator hCard creator] to write up some contact information, [[validators#hCard|validate]] and publish it, or following the [[hcard-authoring|hCard authoring tips]] to add hCard markup to your current site. Check out this section for similar examples of types of pages that benefit from hCard markup.

This section organizes examples into several rough categories as follows. If an example fits in more than one cateogry, use the *last* matching category in this list that matches the specific hCard example(s) in the wild that you are trying to categorize.
# '''[[hcard-examples-in-wild#Individuals|Individuals]]''' - one card per person, perhaps sort alphabetically by "family-name". People with their own hCards (typically) on their own site.
# '''[[hcard-examples-in-wild#Organizations|Organizations]]''' - one card per organization, alphabetical by "fn". Organizations with their own hCard(s) (typically) on their own site.
# '''[[hcard-examples-in-wild#Institutions|Institutions]]''' - which list more than one person, with a count estimating the # of hCards, e.g. 40k for Avon. Also indicate complexity of information supplied, eg. just name+number vs. complete details. Alphabetically sorted by "org" with perhaps a few individuals listed in a single sub-bullet, comma delimited, sorted by "family-name".
# '''[[hcard-supporting-user-profiles|Online Profiles]]''' - which host profiles for more than one person, with a count estimating the # of hCards, e.g. 10m+ for Flickr.com. Alphabetically sorted by company / service name.
# '''[[hcard-examples-in-wild#Online_Venues|Online Venues]]''' - which provide listings for businesses or organizations, with a count estimating the # of venues, e.g. ~10k for Upcoming.org. Alphabetically sorted by service/site name, with perhaps a few specific venues listed in a single sub-bullet, comma delimited, sorted by "fn".
# '''[[hcard-examples-in-wild#Speakers_Listings|Speakers Listings]]''' - event sites' speakers pages where the speakers are marked up with hCard. Sort by date, sub-grouped by year. Most recent first. Perhaps a few individuals listed in a single sub-bullet each event, comma delimited, sorted by "family-name".
# '''[[hcard-examples-in-wild#Group_Blogs|Group Blogs]]''' - blogs with multiple authors marked up with hCard
# '''[[hcard-examples-in-wild#Authors|Authors]]''' - pages about some other thing, such as books, perhaps reviews etc., which have marked up their authors with hCard
# '''[[hcard-examples-in-wild#Search_Results|Search Results]]''' - results pages from search engines (either generic or for people/organizations) that return people marked up with hCards.
# '''[[hcard-examples-in-wild#Listing_Contact|Listing Contact]]''' - contact information for a listing like a job posting, for sale offering, etc.

In addition there is a separate "[[hcard-examples-in-wild#UTF8_Examples|UTF8 Examples]]" section that can be used to put another link to any hCard examples in the wild which exercise various non-ASCII7 / non-english characters for various property values.

As each section itself become quite large (we might be there already, once we sort through the above "Reviewed Examples"), it will probably be moved to a separate page, leaving its heading here in place, and replacing its contents here with a link to the separate page and perhaps a stats summary.

=== Individuals ===
Groupings alphabetically by "family-name".

Nicely styled:
* [http://www.jaredhanson.net/ Jared Hanson]'s home page has a beautiful hCard with numerous ways of contacting him, and live updating of his online status on various messaging networks (uses javascript).
* [http://rogieking.com/#contact Rogie King]'s contact info is marked up with hCard and very nicely styled.
* [http://timvandamme.com/ Tim Van Damme]'s home page is a beautiful hCard.
** needs a few minor fixes: http://tr.im/hctvd (links to hCard validator results)

Simple web pages:
* [http://dbaron.org/ David Baron]'s home page is marked up with hCard.
* [http://abernier.name Antoine Bernier]'s UID hcard:
** Dynamic VCF download link (through [http://suda.co.uk/projects/microformats/hcard/get-contact.php?uri= hcard parser])
** Dynamic QRcode (through [http://microform.at/hcard2qrcode/ hcard2qrcode])
** Dynamic avatar (through [http://www.gravatar.com/ Gravatar])
** [http://wiki2008.openid.net/Delegation openID] ready
** [http://hcard.geekhood.net/?url=http%3A%2F%2Fabernier.name valid]
* [http://tantek.com/ Tantek Çelik]'s home page includes an inline author hCard at the bottom of the page.
* [http://christophertcressman.com/ Christopher T. Cressman] put his contact details on [http://christophertcressman.com/ Who is Chris Cressman?] and marked them up with hCard.

* [http://factoryjoe.com/hcard.html Chris Messina] has a page set aside with his contact details.
* [http://blog.roub.net/ Paul Roub] has an hCard for himself on his blog's home page.
* Patrick Trettenbrein is the operator of [http://skateboardspot.info/ skateboardspot.info] and uses hCard on its [http://skateboardspot.info/cat/about#operator "about" page] for his contact info.
* [http://blogs.msdn.com/cwilso/ Chris Wilson] has an hCard for himself on [http://blogs.msdn.com/cwilso/about.aspx his about page].
* ...

Hidden! Invisible data is strongly discouraged, these examples have been grouped here in the hopes that the authors will someday make their hCards visible:
* [http://ajbrown.org/ A.J. Brown]'s home page includes a hidden hCard at the bottom of the page.

Former. URLs that seem to have broken.
* <nowiki>http://tomleo.com/about.html</nowiki> Tom Leo's about page had an hCard. (missing as of 2009-08-23)

=== Organizations ===
* [http://www.michrome.com Michrome Marketing Lists (UK)] use hCard on all their search result data. For example, [http://michrome.com/free-leads/162-Bradford-BD9 Startup Companies in Bradford].
* [http://technorati.com Technorati] (3)
** [http://technorati.com/about/ about], [http://technorati.com/press/ press], and [http://technorati.com/about/contact.html contact] pages are marked up with hCard and have "Add to Address Book" links that use the [http://feed.technorati.com/contacts/ Technorati Contacts Feed service].
* [http://technorati.jp Technorati Japan] (1)
** [http://technorati.jp/about/contact.html contact] page is marked up with hCard.
* The imprint of [http://www.hsg-kl.de/impressum/index.php Hohenstaufen Gymnasium Kaiserslautern]
** '''suboptimal''': <code>adr</code> subproperties are not recognized due to lack of explicit "adr" property.

=== Institutions ===
* [http://conferences.oreillynet.com/contacts.csp O'Reilly's Conferences Team page] has hCards for their team (~14) with a link to "Download the below contact info in vcf format" that uses the [http://feeds.technorati.com/contacts/ Technorati contacts feed service] to convert the hCards into vCards.
** '''suboptimal''': The "org" shouldn't be hidden with "display:none". Instead, use the [[include-pattern]] to include the "org" from text elsewhere on the page (to avoid duplicating the text).
* [http://technorati.com/about/staff.html Technorati's Staff page] has hCards for its employees (~31)
** E.g. [http://technorati.com/about/staff.html?s=matthew_levine#matthew_levine Matthew Levine], [http://technorati.com/about/staff.html?s=ryan_king#ryan_king Ryan King], etc.
'''with some problems:'''
* The [http://www.ibm.com/contact/employees/ IBM Employee Directory] returns hCards in its query results
** E.g. [http://www.ibm.com/contact/employees/servlets/lookup?country=us&language=en&search_country=all&lastname=Kaply&firstname=Michael search for Michael Kaply],
** but with some problems:
*** '''invalid''': no "fn" (would be addressed by the [[hcard-brainstorming#Implied_FN_from_N|implied fn from n proposal]])
*** '''suboptimal''': adr has no children and thus is not providing any data (may be addressed by the [[hcard-brainstorming#implied_adr_subproperties|implied adr subproperties proposal]])
* [http://www.boltonmuseums.org.uk Bolton Museum and Archive Service] uses hCard on its
**[http://www.boltonmuseums.org.uk/about/contact/ Contacts] page
***'''invalid''': Several have no "fn"
**and on each of its visitor attractions pages e.g. on the [http://www.boltonmuseums.org.uk/visiting/findhallthwood/ Hall i' th' Wood location page].
***'''suboptimal''': "email" and "tel" properties mistakenly include "Email:" and "Telephone:" labels.
* [http://soap.stanford.edu/ Stanford Online Accessibility Program] has implemented hCard on every page
** '''suboptimal''': positioned off screen via CSS
* [http://www.belkin.com/pressroom/releases/uploads/10_09_06SportCommand.html Belkin Press Release] - All Belkin press releases since October 2006 use hCard and vCard for company contact info.
** '''invalid''': Example has 1 (out of 3) invalid hCard due to lack of "fn".
* [http://www.alexa.com Alexa Internet] marked up its [http://www.alexa.com/site/company/managers managers' page] with hCard.
** '''suboptimal''': job "title" is included inside within "fn" property.
* ...

=== Online Profiles ===
* See [[hcard-supporting-profiles]].

=== Online Venues ===
* [http://www.sydneydirectory.org/ Sydney Directory Wiki] supports hCard and geographical coordinates for locations, e.g. the [http://www.sydneydirectory.org/index.php/Opera_House Sydney Opera House].
* [http://www.airfix.com/stockists-and-distributors/ Airfix Stockists and Distributors], e.g. [http://www.airfix.com/stockists-and-distributors/?postcode=b1+1bb&root_rid=1&search.x=0&search.y=0&search=search]
**'''suboptimal''': <code>street-address</code> contains street address, locality and region (e.g. "99 Hobs Moat Rd, Solihull, W. Midlands")
**'''suboptimal''': <code>postal-code</code> and <code>country-name</code> include preprended commas
**'''suboptimal''': <code>fn</code> is used; should be <code>fn org</code>
* [http://www.easthampshire.org/ easthampshire.org] - hCard on events and events map - e.g. http://easthampshire.org/eventdetail/wine_society_evening/1372606 and http://easthampshire.org/eventmap/wine_society_evening/1372606 built by [http://www.callendercreates.com Callender Creates]

=== Speakers Listings ===
==== 2007 ====
[[to-do]]: check 2007 [[presentations]] as they likely contain links to conferences that marked up their speakers page(s) with hCard.
* 09: [http://2006.dconstruct.org/speakers/ d.Construct 2007 speakers]
==== 2006 ====
[[to-do]]: check 2006 [[presentations]] as they likely contain links to conferences that marked up their speakers page(s) with hCard.
* 09: [http://2006.dconstruct.org/speakers/ d.Construct 2006 speakers]
==== 2005 ====
[[to-do]]: check 2005 [[presentations]] as they likely contain links to conferences that marked up their speakers page(s) with hCard.
* 12: [http://tantek.com/microformats/2005/syndicate/speakers-list.html Syndicate - Speaker List] (hCarded version hosted at tantek.com)
* 10: [http://tantek.com/microformats/2005/web2/speakers.html Web 2.0 Conference 2005 -- Speakers] (hCarded version hosted at tantek.com)
* 09: [http://web.archive.org/web/20051102094339/we05.com/ Web Essentials 05] - [http://web.archive.org/web/20051102094339/we05.com/presenters.cfm The Presenters] <nowiki>original URL: http://we05.com/presenters.cfm</nowiki> (appears to have stopped working as of 2007-12-18, perhaps earlier). Web Essentials 2005 (we05) was the [http://tantek.com/log/2005/10.html#d06t1720 first conference to adopt hCard and hCalendar] on their website and marked up all their presenters with hCard.

=== Group Blogs ===
* The [http://www.ibm.com/shortcuts/ IBM Shortcuts Podcast] has authors marked up with hCard but has some problems:
** '''hidden''': The root hCard element as well as every property contained therein is made invisible through a style attribute containing "position:absolute; visibility:hidden".

=== Authors ===
* [http://lazylibrary.com LazyLibrary] uses author hCard's on every book page. Example: [http://lazylibrary.com/book/0751370576]
** '''suboptimal''' [http://lazylibrary.com/book/0751370576 Example] has an fn of "Dorling Kindersley, David West Reynolds" which should be split into two hCards! (site would also benefit from hReview).

=== Search Results ===
* [http://www.bath.ac.uk/contact/ University of Bath] Person Finder results are encoded with hCards so you can easily create a vCard from any result.
** '''invalid''': attempt to use Implied-N optimization where that's not possible,
** '''suboptimal''': honorific-prefix could be explicitly marked up
*** Error appears for external users only. Won't be fixed any time soon. -- [[User:PhilWilson|PhilWilson]] 00:03, 28 Jan 2006 (GMT)

=== Listing Contact ===
Contact information for listings, e.g. job postings, items for sale, etc.

* [http://seogadget.co.uk/search-marketing-executive-upto-30k-portsmouth/ search marketing executive] published by [http://seogadget.co.uk/ SEOgadget].
** '''invalid url property''' - href of the url property element lacks <nowiki>http://</nowiki>, thus being invalid and linking to a non-existent relative URL.
** '''invalid XHTML''' - W3C validator reports this page as [http://validator.w3.org/check?uri=http://seogadget.co.uk/search-marketing-executive-upto-30k-portsmouth/ XHTML 1.0 Transitional] (109 errors as of 2009-08-20).

===UTF8 Examples===
These examples all contain one or more characters in UTF8 that are outside the ASCII7 range and make for excellent test cases to make sure you are handling UTF8 properly throughout your hCard parsing and transforming. And especially if you are generating vCards, these test cases will help you make sure you are generating UTF8 vCards in such a way that can be recognized by UTF8 supporting vCard applications. Sorted roughly alphabetically (per Unicode).
* [http://sphinx.net.ru/author/ Dmitry Dzhus] embedded his UTF8 encoded hCard with Russian characters in Â«AuthorÂ» page of his website.
* [http://tantek.com/ Tantek's Thoughts] encodes Ãelik as inline UTF8.
* [http://technorati.jp/about/contact.html Technorati Japan contact information] encodes Japanese as inline UTF8.
* [http://uk.wikipedia.org/wiki/%D0%93%D0%B5%D1%82%D1%8C%D0%BC%D0%B0%D0%BD_%D0%92%D0%B0%D0%B4%D0%B8%D0%BC_%D0%9F%D0%B5%D1%82%D1%80%D0%BE%D0%B2%D0%B8%D1%87 Vadym Hetman] (Wikipedia-UK (Ukranian))
==== nickname only ====
These UTF8 examples only have UTF8 for the "nickname" property and are thus are a bit easier for testing than the previous examples.
* Various Wikipedia-EN articles, e.g. the "nickname" in: [http://en.wikipedia.org/wiki/Noyabrsk Noyabrsk] (Russian), [http://en.wikipedia.org/wiki/Thessaloniki Thessaloniki] (Greek), [http://en.wikipedia.org/wiki/Kyoto Kyoto] (Japanese) and [http://en.wikipedia.org/wiki/Beijing Beijing] (Chinese)

===non-HTML examples===
* [http://dannyayers.com/misc/microformats/hcard-svg Danny Ayers' SVG hCard demo]

=== missing ===
Examples that used to have one or more hCards but now don't seem to have any. If you do find one, please include direct links to at least two (assuming there are two or more) pages at the referenced site that have one or more hCards.
* [http://mapquest.com Mapquest] now supports hCards for business and places in the search results (e.g. [http://www.mapquest.com/maps/map.adp?searchtype=address&country=US&searchtab=home&formtype=address&cat=Whole+Foods&city=san+francisco&state=ca search for Whole Foods in San Francisco])
** appears to be missing hCards as of 2008-09-07

== related pages ==
{{hcard-related-pages}}

to-do

2009-09-30T18:06:09Z

Spiritquest: Added Ketan as User with To-Do

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

== Lazyweb ==

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

=== for all microformats ===
* We have added a new mailing list called microformats-new. There may be some confusion surrounding this change, so it would be helpful to:
** Draft a message to be added to the confirm message sent when someone subscribes to any list including a welcome message, ground rules, topic for the subscribed list, and the topics for nearby lists.
** Add a faq entry somewhere on why the new list was created.
** Double check the wiki pages to make sure advice on mailing lists is accurate.
* quick and easy "how to" pages for each microformat. [[get-started]] is a good overall start.
* brief summary statements for each microformat that explain why it matters, what does it accomplish for the publisher.
* write up [http://microformats.org/discuss/ mailing-list] questions and answers in the appropriate [[faq]] pages.
* validators. See the hReview section below as there has been a request for an hReview validator in particular. See [http://norman.walsh.name/2006/04/13/validatingMicroformats Norman Walsh's blog post "Validating microformats"] for some valuable analysis and validation pseudo-code (prose description), which are useful steps towards building microformat validators.
* Submit definitions of "microformat", and individual examples, to the [http://foldoc.org Free On-line Dictionary of Computing], acording to [http://foldoc.org/editing.html the Free On-line Dictionary of Computing guidelines]
* it would be nice to replace the -in-the-wild pages with a form that accepted URL entries that would both register the site and look for valid microformatted content and for those pages with problems, would set them aside in a queue to be reviewed by the community. Having such an interface would likely be more efficient for implementors looking to have their work reviewed, and would also add to a ready-database of microformats in the wild -- which would be a great way to feed pingerati.com. [[User:Chris_Messina Chris Messina]] on 2007 Aug 31.
* check with the group and then, assuming this is accepted, remove mention of the profile="" attribute from the wiki, since HTML5 removes the need for profiles to be declared

=== hCard ===
* microformatted versions of conference pages
** Wait for confirmation from O'Reilly webmaster on revision of the [http://conferences.oreillynet.com/etel2006/ ETel] [http://conferences.oreillynet.com/pub/w/44/speakers.html speaker's page] with all the speakers marked up with [[hcard|hCard]] and links to "Add hCards to Address Book" etc., similar to the [http://tantek.com/microformats/2005/web2/speakers.html Web 2.0 speakers page which Tantek did a revision of last fall].
* vcard to hcard converter
** would be nice to have a web upload UI that would take one or more vCards from apple's address book and give them back to you as hCards
** [[User:RobertBachmann | RobertBachmann]] suggests starting points:
*** For Ruby: http://vpim.rubyforge.org/
*** For C: http://freshmeat.net/projects/libvc/
*** For Python: http://www.nongnu.org/python-pdi/
*** For PHP: http://pear.php.net/package/Contact_Vcard_Parse/
** I (Andy Pemberton) started working on this at one point, but haven't touched it in a while: [http://www.andypemberton.com/sandbox/hcardconvert/ vCard-2-hCard]
* add export support for microformats to [http://www.turingart.com/abForWeb_lan__en.htm AB to Web]
* A mash-up with google maps that will take any url with a hcard (or hcard's) and map the location(s) on a map (similar to [http://austin.adactio.com/ austin.adactio.com])
* more test cases - add to [[hcard-examples]] to begin with, then hopefully create test cases for development to be checked in with mercurial to the repository
** include class="type" without explicit value test cases, based on [[hcard#type_with_unspecified_value|hCard type with unspecified value]].

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

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

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

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

=== hAtom ===
* [[hatom-issues]] needs sections for closed issues, resolved issues, and open issues sorted by year, similar to [[hcard-issues]].

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

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

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

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

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

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

===Glossary===
Add to the [[glossary]].

===hAtom tutorial===
Finish the [[hatom-tutorial]].

=== wiki gardening ===
* Find [[:Special:Lonelypages|orphaned]] pages, and add links to them.
* Use [[templates]] for boilerplate text and repeated lists of links
* Add keywords to the foot of pages (see [[vcard-suggestions]] for examples), so that they can be converted to tags, once this wiki allows the use of "rel" attributes. Keywords can also include synonyms to aid searching.

====Spelling====
Per [[how-to-play]]: for English-language pages only: Find British spellings of common words and replace them with the US spellings per [[en-US]]. Mark such edits as "minor" with the comment: <nowiki>[[en-US]]</nowiki>. Please be careful to use and maintain proper native spelling of proper nouns (see [[how-to-play]] for details).

Here is a table of searches for some of the British-English spellings that have crept into English-language microformats wiki pages, along with their respective US-English spellings. If you find other British spellings, please feel free to add them to this table, with their US equivalent.

{| border="1"
|+
! [[en-GB]] !! [[en-US]]
|-
| [http://microformats.org/wiki/Special:Search?search=behaviour&go=Go behaviour] || behavior
|-
| [http://microformats.org/wiki/Special:Search?search=behaviours&go=Go behaviours] || behaviors
|-
| [http://microformats.org/wiki/Special:Search?search=centre&go=Go centre] || center
|-
| [http://microformats.org/wiki/Special:Search?search=colour&go=Go colour] || color
|-
| [http://microformats.org/wiki/Special:Search?search=colours&go=Go colours] || colors
|-
| [http://microformats.org/wiki/Special:Search?search=favour&go=Go favour] || favor
|-
| [http://microformats.org/wiki/Special:Search?search=flavour&go=Go flavour] || flavor
|-
| [http://microformats.org/wiki/Special:Search?search=flavours&go=Go flavours] || flavors
|-
| [http://microformats.org/wiki/Special:Search?search=flavoured&go=Go flavoured] || flavored
|-
| [http://microformats.org/wiki/Special:Search?search=minimise&go=Go minimise] || minimize
|-
| [http://microformats.org/wiki/Special:Search?search=minimises&go=Go minimises] || minimizes
|-
| [http://microformats.org/wiki/Special:Search?search=recognise&go=Go recognise] || recognize
|-
| [http://microformats.org/wiki/Special:Search?search=recognised&go=Go recognised] || recognized
|-
|}

[http://en.wikipedia.org/wiki/American_and_British_English_spelling_differences More American and British English spelling differences]

== Admins ==
This section is for folks to suggest to-do items for [[admins]], in particular, having to do with suggestions for improvements to microformats.org infrastructure such as the wiki. If you do add an item to this list, please sign your username with four tildes: <nowiki>~~~~</nowiki>.

Admins check this "inbox" periodically and process and move items to [[admin-to-do]].

Please check [[admin-to-do]] to see if there is already an ongoing task item relating to your request. Otherwise add the item below.

=== Website Improvements ===
* ...

=== Wiki improvements ===

* New link styles for links to mailing list archive
** Lacking a more concrete suggestion for how to improve such links, I'm inclined to park this in "won't do". [[User:Tantek|Tantek]] 02:39, 10 September 2009 (UTC)

* Add proper styling to phrase elements
** Lacking a more concrete suggestion for how to improve styling of phrase elements, I'm inclined to park this in "won't do". [[User:Tantek|Tantek]] 02:39, 10 September 2009 (UTC)

* Make email addresses editable [[User:Singpolyma|Singpolyma]] 02:47, 26 July 2009 (UTC)
** How would this work and what's the purpose? [[User:Tantek|Tantek]] 02:39, 10 September 2009 (UTC)

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

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

=== protect the community ===
* Analyze [[Special:Recentchanges]] and [http://microformats.org/discuss mailing-lists] and:
** add to [[mailing-lists]] and [[how-to-play]] policies/guidelines accordingly.
** redirect and resolve threads accordingly per guidelines
** privately email violaters kindly asking them to improve their behavior
** work with admins on next steps for individuals negatively impacting the community
** recognize noisy/distracting threads on the email list, document responses/answers to such subjects on the appropriate page(s) on the wiki, and reply to those threads with the URLs to the documentation on the wiki. Putting the responses/answers on the wiki helps by hopefully providing preemptive answers to some who might reraise the subjects on the list in the future, and helps the community quickly terminate such threads by using the answers on the wiki.
** move exploratory discussions which are failing to follow the process to a separate page from that
** repair damage done to the wiki
*** identify damage done to the wiki - often in forms as simple as content changes that hurt usability (and thus accessibility)
*** document additional [[how-to-play]] guidelines to discourage and hopefully reduce such wiki damaging behavior in the future
*** repair/undo/reorganize page section division that hurt usability (and thus accessibility)
**** [[hcalendar-examples-in-wild]]
***** afterwards add some of the excellent conference schedule calendars that [[User:Adactio]] has been creating like:
****** http://adactio.com/extras/schedules/barcampbrighton3/
*** repair/undo/reorganize page splitting that hurt usability (and thus accessibility)
**** [[to-do]]

=== help publishers ===
==== solve problems blocking publishers ====
* [[value-class-pattern]]

===== minor update current specifications =====
* think about solving enumerated type issue (in [[hcard-issues]])
* draft hCard 1.0.1: [[hcard|hCard spec]] '''next-actions''':
** <del>resolve remaining [[hcard-issues|hCard issues]]</del>
** draft [[hcard-1-0-1]] by starting with [[hcard-1-0]] and incrementally incorporating [[hcard-issues-resolved|hCard issue resolutions]], moving them to [[hcard-issues-closed]] accordingly.
** incorporate [[hcard-feedback]]
** continue updating the spec per the inline comment about property references
** add a brief descriptive sentence for each property, similar to what [[hreview|hReview]] has. just enough so that the casual reader can avoid having to reference and read the respective sections in [[RFC2426]]. add any non-trivial information about each property similar to what [[hreview|hReview]] has.
** iterate [[hcard-parsing]] with [[value-class-pattern]] as a required feature
** iterate [[hcard-parsing]] with sufficient table element special handling to do people equivalent of [http://microformats.org/wiki/hcalendar- brainstorming#Tabular_event_calendars]
** [[hcard-brainstorming]] '''next-actions''': determine which brainstorms proposals to resolve for minor revision, and which later
** Update [[semantic-xhtml]] with lists of semantic [http://www.w3.org/TR/html401/index/elements.html elements] and [http://www.w3.org/TR/html401/index/attributes.html attributes].
** Update [[hcard-brainstorming]] on element specific parsing rules
** Update X2V, hKit, Operator accordingly
** Write test cases accordingly
** Update [[hcard-parsing]] accordingly
* draft hCalendar 1.0.1: [[hcalendar|hCalendar spec]] '''next-actions''':
** resolve all outstanding [[hcalendar-issues]] into [[hcalendar-issues-resolved]]
** draft [[hcalendar-1-0-1]] by starting with [[hcalendar-1-0]] and incrementally incorporating [[hcalendar-issues-resolved|hCalendar issue resolutions]], moving them to [[hcalendar-issues-closed]] accordingly.
** incorporate [[hcalendar-feedback]]
** itemize a complete property list similar to the [[hcard#Property_List|hCard property list]], drawing upon hCalendar experience, iCal-BASIC draft(s), ietf-calsify mailing list and other sources to derive the precise list. Separate common properties up front.
** add a brief descriptive sentence for each property, similar to what [[hreview|hReview]] has. just enough so that the casual reader can avoid having to reference and read the respective sections in [[RFC2445]]. add any non-trivial information about each property similar to what [[hreview|hReview]] has.
** significantly update and thoroughly specify [[hcalendar-parsing]] with [[value-class-pattern]] as a required feature
** formally document [http://microformats.org/wiki/hcalendar- brainstorming#Tabular_event_calendars]
** [[hcalendar-examples]]
*** make sure all hCalendar examples that reference whole days use best international/accessible date format of YYYY-MM-DD
*** add explicit explanation and examples for LOCATION [[hcard|hCards]] and ATTENDEE [[hcard|hCards]], perhaps on a separate [[hcalendar-examples]] page.
** Write [[compound-parsing]] by abstracting commonalities between [[hcard-parsing]] and [[hcalendar-parsing]].
* draft hReview 0.4
* resolve hAtom issues
* co-edit hAtom per permission from David Janes
* draft [[hAtom]] 0.2
** Clarify that "published" property values may omit seconds, and that converters to Atom are expected to imply ":00" seconds.
* add sections for comments/opinion from community as well as issues subsection
* solicit feedback
* when sufficient consensus and issue resolution achieved, archive previous versions of specs, and update spec pages accordingly.

==== social network portability ====
Iterate on:
* [[social-network-portability]]
* [[hcard-supporting-user-profiles]]
* [[hcard-xfn-supporting-friends-lists]]

Brainstorm updates to the [[pocket-cheat-sheet]] to better enable [[social-network-portability]], or perhaps design a new '''social network portability pocket cheat sheet''' that specifically documents:
* how to author/publish hCard user profiles - write this up in [[hcard-authoring]] first (see below) and then use that content.
* how to author/publish hCard+XFN friends lists - write this up in [[hcard-xfn-authoring]] (see below) and then use that content.
* how to parse/subscribe to hCard user profiles - write this up by updating: [[hcard-parsing]], and writing [[hcard-supporting-user-profile-parsing]] (collect this into parsing/developers tasks below)
* how to parse/subscribe to hCard+XFN friends lists - write this up by writing: [[xfn-parsing]], [[hcard-xfn-supporting-friends-list-parsing]] (collect these into parsing/developers tasks below)
** notes/thoughts on hCard+XFN supporting friends list parsing captured here for now:
*** do a full rel="me" bidirectional crawling within the domain - some sites' hCard supporting user profiles simply link to their hCard+XFN supporting friends lists with rel="me", and thus you will discover more pages with friends lists.
**** E.g. Flickr's /people/username pages have hCard for the user and link to their /people/username/contacts page with rel="me" (on the "More..." link, though they could also add rel="me" to the number inside "Your contacts (592)"). Need to get them to support hCard+XFN on the contacts themselves.
*** consider parsing within a friends list page, any links that are rel="next" and rel="prev" to iterate over the whole list.

==== foldup cheatsheet ====
'''next actions''':
* gather feedback on current foldup [[pocket-cheat-sheet|pocket cheatsheet]]
* document the [[pocket-cheat-sheet-feedback|feedback on the pocket cheatsheet]]
* provide printing recommendations for anyone to download and print their own
** Perhaps [http://www.visibone.com/ Visibone] can be of some use? I can recommend their current products. --[[User:Gazza|Gazza]] 06:41, 7 Apr 2007 (PDT)
* update cheatsheet to include new [[value-class-pattern]] uses
* give feedback to Erin or ask for volunteers to create a new cheatsheet, iterate, print more to have on hand, fold, distribute.
* discuss with [[User:Adactio]] and Hannah how to best create a UK/A4 version of the pocket cheatsheet
** preferably well in advance of dConstruct 2008 so that local cheatsheets can be printed.

==== *-authoring microformats wiki pages ====
* [[hcard-authoring]] - '''next-actions''': add tips/instructions noted below.
** instructions for each property that is in [http://microformats.org/code/hcard/creator hCard creator] to begin with
** instructions for all other hCard properties
** a tutorial on creating an hCard for your site
*** specific instructions for common blogging platforms
** reference [[hcard-examples]] for more specific uses, and add to them accordingly
*** add an extended example to [[hcard-examples#Authors_of_Pages_and_Posts|contact info for a page]] with postal address, phone numbers, email address.
* [[hcard-xfn-authoring]] - '''next-action''': draft by starting from hCard+XFN instructions in [[hcard-examples]].
* [[hreview-authoring]] - '''next-action''': create a first draft minimal tutorial on how to author hReviews (e.g. at least for common properties) to blog reviews so that they'll be aggregated.
* [[hcalendar-authoring]] - '''next-action''': add tips/instructions for each property that is in [http://microformats.org/code/hcalendar/creator hCalendar creator].
* *-authoring for other reasonably well established microformats:
** [[xfolk-authoring]], [[hatom-authoring]]

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

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

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

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

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

=== iterate on current microformats ===
==== in general ====
===== plain language intros =====
For [[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], [[xoxo|XOXO]] to start with, write up:
* brief plain-language intro at the top (say for example, something that a non-technical person like a member of the general media/press could read and understand), similar to or better than plain language intros on W3C specs.
* followed by links to more plain-language resources, e.g. *-intro pages.
In particular for [[xoxo|XOXO]], Angus McIntyre suggested:
* As well as a syntactic example, examples of use would be useful.
* when I might want to use XOXO.
* Some simple examples right upfront would probably do a lot to help users figure out whether a particular microformat is for them or not.
These suggestions could be incorporated into the other specs as well.
===== exploratory discussions =====
* update [[exploratory-discussions]] with critical microformats as "active"
===== CSS enhancements for =====
Analyze existing microformats for opportunities to enhance CSS and propose to W3C.
* e.g. CSS datetime presentation (need to add links to my earlier work in CSS working group)
* brainstorm additional possibilities for better presentation of content using existing microformats.
===== update affiliations =====
* Start a minimal draft/spec style guide using outline of most readable/accessible spec so far
* Reference http://www.w3.org/2001/06/manual/#Editors for how to manage affiliations
* Update affiliations on [[hcard]], [[hcalendar]], [[hreview]], etc. per http://www.w3.org/2001/06/manual/#Editors
===== profile URLs =====
* write-up and document [[profile-uris|profile URLs]] for all established microformats and perhaps for some drafts as well

==== [[hcard|hCard]] ====
Combined next-actions for iteration on [[hcard|hCard]], and derived/subsetted microformats [[adr]] and [[geo]]
* [[hcard-profile]] '''next-actions''':
** update property definitions with more detail using semantics from [[RFC2426]]
** link from brief sentence descriptions for each property in [[hCard]] to the respective more detailed definition in the [[hcard-profile]].
** link from definitions in the [[hcard-profile]] to the specific sections in the vCard spec
* [[hcard-examples]] '''next-actions''': update with examples described below
** add examples of [[hcard|hCard]]s with work telephone, mailing address etc.
** add examples of marking up an organization vs. a person, then link to it from [http://microformats.org/wiki/hcard#Organization_Contact_Info hCard spec section on Organization Contact Info].
** add example of organization-name and organization-unit usage.
* [[hcard-brainstorming]] '''next-actions''': explore brainstorms proposals for a 1.1 revision, e.g.
** need property for gender (see [[hcard-faq#How_is_gender_represented|proposal in hCard FAQ]] and discussion in [[hcard-issues]]) - use tags for now, add to hCard creator
** solve [[hcard-brainstorming#Auto-Discovery|autodiscovery]] of more canonical/thorough hCard
* [[hcard-examples-in-wild]]
** help dglazkov markup: http://glazkov.com/blog/archive/2003/12/17/147.aspx

* analyze [[hcard-cheatsheet]], [[adr-cheatsheet]], [[geo-cheatsheet]] for any assertions above and beyond what the specification itself says, take into account [[hcard-brainstorming]] along similar lines, and incorporate into the spec or remove as necessary and sync-up as a result. add clarification on the cheatsheets that they are '''informative''' and reference the specification for normative requirements.

==== [[hcalendar|hCalendar]] ====
'''Next-actions''':
* update [[hcalendar-examples]]
** add examples like [[hcard-examples]]
** flesh out and do a once over on markup/presentation of what RFC2445 examples would look like
** update all hcalendar-examples to use value-title from [[value-class-pattern]] where abbr doesn't make sense. e.g.
*** rrule
*** duration
*** ... etc.
* need spec details and then [[hcalendar-examples]] of multi-instance [[hcalendar|hCalendar]] events
* need spec details and then [[hcalendar-examples]] of repeating events
* create [[hcalendar-profile]] and have folks verify it. Note that it will likely need reconciliation with the [[hcard-profile]], especially since [[hcalendar|hCalendar]] normatively depends on [[hcard|hCard]]. Probably makes sense to have a combined profile which hCalendar would use.
* analyze [[hcalendar-cheatsheet]] for any assertions above and beyond what the specification itself says, take into account [[hcalendar-brainstorming]] along similar lines, and incorporate into the spec or remove as necessary and sync-up as a result. add clarification on the cheatsheets that they are '''informative''' and reference the specification for normative requirements.

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

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

==== [[rel-me]] ====
'''Next-actions''':
* move XFN and XMDP FAQs, tutorial, descriptions, spec etc. from gmpg.org to microformats.org
** and put redirects in place, notes about contribution
* update rel-me examples and document with examples the rel-me implict subdir rule

==== [[hatom|hAtom]] ====
'''Next-actions''':

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

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

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

==== update specification section organization ====
'''Goal''': greater approachability/readability of microformats specs by a broader audience.

Reference:
* [[hresume|hResume]] has an experimental abbreviated intro/headers section, and links to more details further below, based on some ideas that Ryan King and I had for improving the readability of the microformats specifications.
* [[hreview|hReview]] has some similar improvements, but different.
* [[hcard|hCard]] has numerous improvements as well, again different from either hResume or hReview

'''Next-actions''':
# contact microformats community members who are content/tutorial authors, and/or have written (or are writing) technical books, and those who have made concrete helpful suggestions for reorganizing the information architecture / content-order / layout of specs.
# figure out if the new intro/headers etc. structure/order in [[hcard|hCard]], [[hreview|hReview]], and [[hresume|hResume]] is an improvement, and if it could be better. Document reasoning/requirements for intro/header and other sections.
#* Shorter tends to be better
#* Must be comprehensive enough to "print and read"
#* Must detail authorship/editorship
#* Must detail copyright/patent statements
# Design an iterative update to spec organization, in particular, the introduction/boilerplate/headers.
# Write up a template - make it self-documenting per the requirements
# Update existing specifications with the new intro/headers structure.
## [[hcard|hCard]]
## [[hcalendar|hCalendar]]
## [[hreview|hReview]]
# Write up methodology behind the section organization and note editors lessons learned into an [[editors-guide]] page (what other variants were done before, in which specs, and note problems/complaints with other variants).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

==Ryan==
=== wiki cleanup ===
* <s>possibly move dead proposals off of homepage?</s>

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

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

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

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

== Dimitri Glazkov ==

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

== Chris Messina ==

=== General ===

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

=== Campaigns ===

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

=== Wishlist ===

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

Hey Chris.
Congrats on Microsyntax
([http://factoryjoe.com/blog/2009/05/26/stowe-boyd-launches-microsyntax-org/ "Stowe Boyd launches Microsyntax.org"]).
So ... do we need a page on this Microformats wiki describing the connection between microformats and microsyntax?
When the Microsyntax wiki goes online, please add a link to it on the Microformats [[WikiNode]] page.
--[[User:DavidCary|DavidCary]] 08:34, 4 June 2009 (UTC)

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

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

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

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

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

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

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

=== additions to the wiki ===

* better explain why NOT infinitely scaling is a good thing
* better explain why microformats do NOT use namespacing

== Mark Rickerby ==

=== Current Tasks ===

* Follow up on usability review
** Edits to homepage feature box text
** Draft of [[getting-started]] page
* Review content for new pages - [[start-simple]], [[modularity]], [[reuse]], [[humans-first]]
* xoxo datatype examples
** test case lists
** transmitting key/value lists
* practical feedback on hresume

=== Wishlist ===

* hmmm

== Ernest Prabhakar ==
=== Wiki-Thon Proposal ===
Set aside several hours (probably a Friday night US PST) for focused work on the Wiki, including both physical (e.g., a room in the Bay Area) and virtual (IRC/iChat) participants.

==== Goals ====
# Improve understanding of what needs to be done for Wiki
#* IMHO - this should be done here, in [[to-do]] incrementally. -Tantek
# Tackle larger projects (~1-2 hours) than people usually have time for
#* I'd like to see these projects *documented* first on [[to-do]] before we spend 1-2 hours of a bunch of folk's collective time to go through them. -Tantek
# Motivate community to have fun with otherwise tedious "housecleaning" chores

==== Agenda (Wishlist) ====
In parallel:
* Coalesce/prioritize existing To-Do items (above)
* Review/revise desired pathways for:
** New users learning about microformats
*** e.g., intro, about, explore, tutorials, etc.
*** cf. [http://www.rubyonrails.com/ Rails] front page
****Get Excited (Why, background, motivation)
****Get Started (What, downloads, getting started)
****Get Better (How, tutorials, )
****Get Involved (Who)
** Microformat lifecycle
*** e.g., research->brainstorm->proposal->spec->maintain
*** see http://theryanking.com/microformats/method.txt --[[User:RyanKing|RyanKing]] 15:35, 22 Feb 2006 (PST)
*** ensure information easy to find, follow, and up-to-date
* Review existing specs for completeness and consistency
* Identify areas of 'bitrot' or 'hole-filling'
* Do it!

== Dan Connolly ==

[[User:DanC|DanC]] hopes to sync up on these tasks in [[irc]] roughly
weekly, during Wednesday afternoon (Chicago time) "office hours". See also my [http://esw.w3.org/topic/DanConnolly esw todo list and someday pile].

* from SxSW in Austin
** build a combined hcalendar/hcard profile; resolve issues in [[profile-uris]].
*** with XSLT transformation to RDF
** finish [[hcard-tests]]
*** figure out [[include-pattern]] boundaries

* Medium term
** sync [[hcalendar-tests]] and [http://www.w3.org/2002/12/cal/ RDF calendar] tests and CALSIFY
*** reconsider RDF calendar naming conventions
** update my CV/resume using [[hResume]] and [[citation-formats]]
*** get an answer from the CALSIFY WG re [http://lists.w3.org/Archives/Public/www-rdf-calendar/2006Apr/0006.html dtstart and date vs datetime ] 21 Apr 2006
*** refine [[hatom]] so that it's suitable for the workflow around the W3C homepage.

* from WWW2006
** follow up on GRDDL as escape valve for microformats proposals, much like CSS was an escape valve for HTML tag proposals.

* Someday pile
** set up a timezone registry based on wikipedia and semantic mediawiki. As discussed in [[datetime-design-pattern]], iCalendar's by-value timezone passing is broken. see [http://lists.w3.org/Archives/Public/www-rdf-calendar/2006Apr/0002.html reconsidering timezones in light of hCalendar and CALSIFY] and [http://dig.csail.mit.edu/breadcrumbs/node/91 Toward Semantic Web data from Wikipedia]
** noodle on a playlist format and some of the media RSS stuff like [[media-info-brainstorming]], [[media-metadata-examples]] (re playlists: XSPF, SMIL, RDF, and microformats 9 Sep 2005)
** check out that hReview bug stuff...
** noodle on [[meeting-minutes-brainstorming]] and [http://esw.w3.org/topic/MeetingRecords MeetingRecords in the esw wiki].
** noodle on clipboard scenarios, esp how RDFa works in the general case but isn't as author-friendly as domain-specific syntaxes.

[[User:DanC|DanC]] 15:39, 31 May 2006 (PDT)

== Chris Casciano ==

[[User:ChrisCasciano|ChrisCasciano]]

* get around to updating [[hatom-issues]] with some multi feed rules/exceptions.
* <del>Update textpattern plugin with simple hreview support and get a new release out</del>
* Redesign placenamehere.com and include hatom
* Follow up with technorati folks on pingerati reviews getting lost (note: this will require publishing more reviews and theen watching them through the update process)
* <del>prototype a NetNewsWire microformat extractor (CSS+AppleScript)</del>

== Drew McLellan ==

[[User:DrewMcLellan|DrewMcLellan]]

* Build an hReview profile for [http://allinthehead.com/hkit/ hKit] and test
* Update the [http://www.webstandards.org/action/dwtf/microformats/ Dreamweaver extensions] to mirror recent changes in the online builders
* <del>Publish an hCard to JSON service on [http://tools.microformatic.com/ tools.microformatic.com] using hKit.</del>
* Further develop blog comment form hCard collection ideas.
* Version of hReview creator using hKit to import business details from an hCard

== Christophe Ducamp (french localization) ==

[[Christophe Ducamp]]
* seed "microformateurs group" and invite them to update http://microformateurs.org
** write a process for newbies in order to make them write [[posh-fr|CHIC]] posts on a public blog-governed-by-wiki ([http://socialsynergyweb.net/cgi-bin/wiki/MicroFormateurs/Blog]) before publication.
** find experts for peer-reviewing
** find french CSS gurus to setup a nice Sandbox-CSS template on Wordpress
* translating the wiki
** translate red links on [[Main_Page-fr]] and synchronize
** find out microformateurs at ease on "the-wiki-way-translation", and ready to help on semi-anonymous-synchro
* community-marketing -> pinko-marketing
** public-relations towards french journalists and complete [[advocacy-fr|advocacy]] (especially [[hcard-advocacy-fr]] towards organizations.
** help to build events, workshops like barcamps and explorcamps
** update [http://fr.wikipedia.org/wiki/Microformats French-wikipedia:Microformats] and subpages via cowriting [http://fr.wikipedia.org/wiki/Discuter:Microformats on discussion page] (directly originated from the english article) + french examples to be found + local resources.
** open discussion with french wikipediens about implementing some of the english existing templates
** small gifts: accessories and free gifts ? t-shirts, localized cheat-sheet, id-hcard-openid-providing, etc.
*** create hCard, hCalendar... and all red link pages on french wikipedia
* localize [[species-fr]] and related pages
* move all contents remaining on elanceur.org -> microformateurs.org
* wiki and uf:
** write and talk with "aboutus.org" to invite them to make experiences with uf -> talk with Mark Dilley
** maintain/update http://www.communitywiki.org/MicroFormats and talk with LionKimbro
** XWiki : awaiting beta-test of new platform
*** Follow-up LudovicDubost et LaurentLunati
* setup real-life links with european [[governance-fr|governance]] members ;) may be joining dconstruct-microformats-workshop - find solution (registering fees and travel expenses -> talk with Arnaud Fontaine or search french sponsors)

== Frances Berriman ==

[[User:Phae|Frances Berriman]]

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

== Ben West (bewest) ==

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

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

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

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

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

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

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

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

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

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

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

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

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

These pages would be located respectively at

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

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

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

== Matt Dertinger (Thewhoo) ==

[[User:Thewhoo]]

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

=== Microformats Proposals ===

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

== Henri Bergius ==

[[User:HenriBergius|Henri Bergius]]

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

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

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

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

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

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

== [[User:RobManson | Rob Manson]] ==
* chase the admins to get some creation template extensions installed for wiki (see: http://meta.wikimedia.org/wiki/Inputbox or http://www.mediawiki.org/wiki/Extension:CreateBox or http://www.mediawiki.org/wiki/Extension:CreateArticle)

== [[User:ClayNewton | Clay Newton]] ==
* Work on getting others involved in [[trade-examples]]
** Need examples from major online banking sites
** Need examples from major ecommerce sites
* Continue working on: [[trade-brainstorming]]

== [[User:BenWard | Ben Ward]] ==

=== Recurring ===

* Delete Wiki Spam

=== Currently ===

* Gardening/updating key wiki pages.
** [[how-to-play]]
** XHTML Design Principals
* embed brainstorming
* Considering new welcome banner of µf.org to link to various µf resources, rather than being dominated by the infrequently updated blog.

=== Next Actions ===

* Conclude new hCalendar proposals from Yahoo TV Listings experience
* Resume work on hListing microformat
* Re-org the Microformats.org front-page content
** Work with [[User:Phae]] on refreshing the microformats frontpage content
** Build new events module for the blog using Upcoming.org, rather than hard coded event data (Matt Harris may have done this…)
** Build new wiki edits module for the blog
** Combine ‘list of microformats’ into the intro text? Make intro text more friendly.
* Build a microformats activity stream
** Replace front page blog with activity flow
*** Wiki Edits/New Pages
*** New Mailing List Threads
*** Interesting µf links
*** Blog posts
*** Upcoming events/event reminders
* Improve µf.org/blog OpenID support, find a good workflow for login/comment (current plug-in has an abysmal user experience)

== [[User:Spiritquest|Ketan Majmudar]] ==
=== Activites ===
* Work on developing the [[hlisting-brainstorming|hListing]] proposal
** Provide real world examples and apply this to the proposed specifications
* refine and keep up to date with [[hcard|hCard]] formats as used on existing sites [[http://www.ethical-junction.org| Ethical Junction CIC]]
* Understand / follow and evangalise existing patterns, especially the new [[value-class-pattern]]
* see where I can help the community
* look at using x2v or writing php parser classes for hcard -> vcard
* open source hCard class (php) used to format db fields

ecolabel-brainstorming

2009-07-27T23:57:05Z

Spiritquest: moved content brainstorm page for research

=== rel="ecolabel" ===

Rel-Ecolabel is a simple, open, format for indicating ecolabelled items which is embedable in HTML or XHTML, Atom, RSS, and arbitrary XML.
Specification 2008-05-12

=== Author ===
Jacob Malthouse (http://bigroom.ca), formerly of ICANN (http://icann.org/)

=== Abstract ===
By adding rel="ecolabel" to a hyperlink, a page indicates that the destination of that hyperlink is the ecolabel for an ecolabelled item listed on the current page. E.g. with the following hyperlink:

<a href="http://ecolabelling.org/ecolabel/ecologo/" rel="ecolabel">ecologo</a>

NOTE: in the highlighted portion - is this where we would put an ecolabel code or readable URL for ecolabelling.org entry?

the author indicates that the product, company, or services has obtained an "ecologo" certification.

--[[User:Spiritquest|Spiritquest]] 23:06, 27 July 2009 (UTC)

It seems that it might work well with being linked to an hproduct / hCard - to identify a manufacturer - I've yet to explore hproduct in detail.

I don't know that pointing the URL of the ecolabel directly to www.ecolabelling.com would work.

If I ran a product site with ecolabelled products, I would want to point to either a source of information on the label internally within the site, or have it point to a list of all data tagged with similar ecolables.

<a href="http://myproductsite.org/ecolabel/ecologo/" rel="license">ecologo</a>

The destination would then show all '''ecologo''' tagged products within the catalogue of myproductsite.org

maybe microformat parsing tools could be created to send users or pull information from www.ecolabelling.org site as a source of authoritative info and background on the label.

rel-tag as an example can point to an internal site structure using a taxonomy but can also use microformat tools to extend data searches to sites like technorati.

=== Multiple Licenses ===

Multiple such rel="ecolabel" hyperlinks indicate that multiple items on the page are available under any of the referred licenses. E.g. the following hyperlinks could be used to declare that a page is available under either an ecologo or a certified carbon free ecolabel:

<a href="http://ecolabelling.org/ecolabel/ecologo/" rel="ecolabel">ecologo</a>
<a href="http://ecolabelling.org/ecolabel/certified-carbonfree/" rel="ecolabel">certified-carbon-free</a>

=== XMDP profile ===
unknown/in development

=== Implementations ===
none

=== List of Ecolabels ===
http://ecolabelling.org/ecolabel/
see also: about ecolabelling.org: http://ecolabelling.org/about/

=== References ===
See Also

rel-ecolabel

2009-07-27T23:55:59Z

Spiritquest: /* Brainstorming */

ecolabel-formats

2009-07-27T23:55:12Z

Spiritquest: mving content out

== previous formats ==

=== Similar Microformats ===

* [[rel-license]]

indicates a "that the destination of that hyperlink is a license for the current page." whereas rel-ecolabel would indicate that the destination of that hyperlink is an ecolabel for a product, company or service listed on the page.

In this case I am uncertain if rel-license defines an authoritative source for license information. The difference with rel-ecolabel is that we would define an authoritative source at www.ecolabelling.org. We'd do this because there are many ecolabels 300+ and very few display their information in a standardised way. That being said, we're not beholden to this approach.

* [[rel-tag]]

This would need to have the option / ability to point to the issuing labels site as well. Or if www.ecolabelling.org want to become the source, it should have a simple an quick method of adding labels into the system that aren't listed .. eg. a lot of UK based certified labels are currently not on the site. Would there be a conflict if I wanted to point the URL at the label associations website instead of www.ecolabelling.org (asked for discussion purposes)

Label example: Vegan Society Trademark: http://www.vegansociety.com/business/trademark/

=== Ecolabel Schema ===

ecolabel entry @ ecolabelling.org
eg: http://ecolabelling.org/ecolabel/energy-star/

ecolabel entry @ greenerchoices.org
eg: http://greenerchoices.org/eco-labels/label.cfm?LabelID=15&searchType=Label%20index&searchValue=&refpage=labelIndex&refqstr=

ecolabel ISO types
eg: http://www.gen.gr.jp/eco.html

=== conformsTo ===
The [http://dublincore.org/documents/dcmi-terms/#terms-conformsTo Dublin Core conformsTo] term appears to already solve a more general problem of indicating conforming to any external label etc, not just ecolabels.

Re-using conformsTo is also better than minting a new rel term. conformsTo can be used in a wider set of situations that "ecolabel" in that it can be used to indicate non-ecological conformance to standards too. e.g. a web page can conform to HTML 4.01 Strict, or software could conform to "Certified for Windows Vista" or a toy could conform to a particular child safety standard.

As a [[poshformat]] inside the product description, e.g. inside an [[hProduct]]:
<source lang=html4strict>
This product conforms to <a rel="conformsTo"
href="http://ecolabelling.org/ecolabel/certified-carbonfree/">certified-carbon-free</a>
</source>

using [http://www.w3.org/TR/rdfa-syntax RDFa]:
<pre><nowiki>
This product conforms to <a about="#product"
xmlns:dc="http://purl.org/dc/terms/" rel="dc:conformsTo"
href="http://ecolabelling.org/ecolabel/certified-carbonfree/">certified-carbon-free</a>
</nowiki></pre>

These claims could be verified by the authority being linked to (in the case above ecolabelling.org) by simply providing a link back from http://ecolabelling.org/ecolabel/certified-carbonfree/ to the product:

as a poshformat on the certified-carbonfree page:
<source lang=html4strict>
The <a href="http://foo.example.com/product" rev="conformsTo">Foo product conforms to certified carbonfree.</a>
</source>

as RDFa:
by linking to it using an about attribute, a namespace URL declaration, and labeling it with <tt>rev="dc:conformsTo"</tt>.

rel-ecolabel

2009-07-27T23:54:17Z

Spiritquest: /* previous formats */

ecolabel-examples

2009-07-27T23:51:56Z

Spiritquest: New page: Ecolabelled products appear on retailer and producer sites all over the web. There is currently no way of identifying them. Several examples are presented below: URL: http://www.amazon.co...

Ecolabelled products appear on retailer and producer sites all over the web. There is currently no way of identifying them. Several examples are presented below:

URL: http://www.amazon.com/Newmans-Own-Organics-California-15-Ounce/dp/B000FNJNO6/ref=tag_stp_st_edpp_url
SCHEMA: Oregon Tilth
ecolabel: http://ecolabelling.org/ecolabel/oregon-tilth/

URL: http://www.environmentalbychoice.com/prestigious_papers/enviro100ecofibre.php
SCHEMA: FSC
ecolabel: http://ecolabelling.org/ecolabel/fsc-forest-management-certification/

URL: http://www.bestbuy.com/site/olspage.jsp?skuId=7838995&type=product&productCategoryId=pcmcat108700050027&id=1142297396649
SCHEMA: Energy star
ecolabel: http://ecolabelling.org/ecolabel/energy-star/

rel-ecolabel

2009-07-27T23:51:29Z

Spiritquest: /* Examples */

'''This page was prematurely created and does not follow the microformats [[process]]. If you are the creator of this page, please join the discussion on the microformats [[irc]] channel, and ask for help with the microformats process. You may also request help on the microformats-new [http://microformats.org/discuss discussion list].'''

== Problem ==

It's difficult to authenticate eco-friendly goods and services online.

* The proposed solution below is not a solution to the above problem. The proposed solution offers a mechanism by which a service can ''claim'' an eco-friendly label, but no way of ''authenticating'' that claim.

== Proposed Solution ==

'''It is premature to propose any brainstormed solution without first at a minimum per the process creating pages to research and collect [[ecolabel-examples]] and [[ecolabel-formats]]. Only then should proposals be drafted on a [[ecolabel-brainstroming]] page.'''

We are interested in establishing "rel-ecolabel" as a way of identifying ecolabelled (and thus eco-friendly) items (where item = ecolabel certified unit including products, services, companies, land, or any other thing that can be certified eco-friendly) on the World Wide Web.

Definition of an ecolabel: http://ecolabelling.org/eco-labels/

== Examples ==

'''This section should be moved to a separate page like [[ecolabel-examples]].'''

== previous formats ==
'''This section should be moved to a separate page like [[ecolabel-formats]].'''

=== Similar Microformats ===

* [[rel-license]]

indicates a "that the destination of that hyperlink is a license for the current page." whereas rel-ecolabel would indicate that the destination of that hyperlink is an ecolabel for a product, company or service listed on the page.

In this case I am uncertain if rel-license defines an authoritative source for license information. The difference with rel-ecolabel is that we would define an authoritative source at www.ecolabelling.org. We'd do this because there are many ecolabels 300+ and very few display their information in a standardised way. That being said, we're not beholden to this approach.

* [[rel-tag]]

This would need to have the option / ability to point to the issuing labels site as well. Or if www.ecolabelling.org want to become the source, it should have a simple an quick method of adding labels into the system that aren't listed .. eg. a lot of UK based certified labels are currently not on the site. Would there be a conflict if I wanted to point the URL at the label associations website instead of www.ecolabelling.org (asked for discussion purposes)

Label example: Vegan Society Trademark: http://www.vegansociety.com/business/trademark/

=== Ecolabel Schema ===

ecolabel entry @ ecolabelling.org
eg: http://ecolabelling.org/ecolabel/energy-star/

ecolabel entry @ greenerchoices.org
eg: http://greenerchoices.org/eco-labels/label.cfm?LabelID=15&searchType=Label%20index&searchValue=&refpage=labelIndex&refqstr=

ecolabel ISO types
eg: http://www.gen.gr.jp/eco.html

=== conformsTo ===
The [http://dublincore.org/documents/dcmi-terms/#terms-conformsTo Dublin Core conformsTo] term appears to already solve a more general problem of indicating conforming to any external label etc, not just ecolabels.

Re-using conformsTo is also better than minting a new rel term. conformsTo can be used in a wider set of situations that "ecolabel" in that it can be used to indicate non-ecological conformance to standards too. e.g. a web page can conform to HTML 4.01 Strict, or software could conform to "Certified for Windows Vista" or a toy could conform to a particular child safety standard.

As a [[poshformat]] inside the product description, e.g. inside an [[hProduct]]:
<source lang=html4strict>
This product conforms to <a rel="conformsTo"
href="http://ecolabelling.org/ecolabel/certified-carbonfree/">certified-carbon-free</a>
</source>

using [http://www.w3.org/TR/rdfa-syntax RDFa]:
<pre><nowiki>
This product conforms to <a about="#product"
xmlns:dc="http://purl.org/dc/terms/" rel="dc:conformsTo"
href="http://ecolabelling.org/ecolabel/certified-carbonfree/">certified-carbon-free</a>
</nowiki></pre>

These claims could be verified by the authority being linked to (in the case above ecolabelling.org) by simply providing a link back from http://ecolabelling.org/ecolabel/certified-carbonfree/ to the product:

as a poshformat on the certified-carbonfree page:
<source lang=html4strict>
The <a href="http://foo.example.com/product" rev="conformsTo">Foo product conforms to certified carbonfree.</a>
</source>

as RDFa:
by linking to it using an about attribute, a namespace URL declaration, and labeling it with <tt>rev="dc:conformsTo"</tt>.

== Brainstorming ==
'''This section should be moved to a separate page like [[ecolabel-brainstorming]].'''

=== rel="ecolabel" ===

Rel-Ecolabel is a simple, open, format for indicating ecolabelled items which is embedable in HTML or XHTML, Atom, RSS, and arbitrary XML.
Specification 2008-05-12

=== Author ===
Jacob Malthouse (http://bigroom.ca), formerly of ICANN (http://icann.org/)

=== Abstract ===
By adding rel="ecolabel" to a hyperlink, a page indicates that the destination of that hyperlink is the ecolabel for an ecolabelled item listed on the current page. E.g. with the following hyperlink:

<a href="http://ecolabelling.org/ecolabel/ecologo/" rel="ecolabel">ecologo</a>

NOTE: in the highlighted portion - is this where we would put an ecolabel code or readable URL for ecolabelling.org entry?

the author indicates that the product, company, or services has obtained an "ecologo" certification.

--[[User:Spiritquest|Spiritquest]] 23:06, 27 July 2009 (UTC)

It seems that it might work well with being linked to an hproduct / hCard - to identify a manufacturer - I've yet to explore hproduct in detail.

I don't know that pointing the URL of the ecolabel directly to www.ecolabelling.com would work.

If I ran a product site with ecolabelled products, I would want to point to either a source of information on the label internally within the site, or have it point to a list of all data tagged with similar ecolables.

<a href="http://myproductsite.org/ecolabel/ecologo/" rel="license">ecologo</a>

The destination would then show all '''ecologo''' tagged products within the catalogue of myproductsite.org

maybe microformat parsing tools could be created to send users or pull information from www.ecolabelling.org site as a source of authoritative info and background on the label.

rel-tag as an example can point to an internal site structure using a taxonomy but can also use microformat tools to extend data searches to sites like technorati.

=== Multiple Licenses ===

Multiple such rel="ecolabel" hyperlinks indicate that multiple items on the page are available under any of the referred licenses. E.g. the following hyperlinks could be used to declare that a page is available under either an ecologo or a certified carbon free ecolabel:

<a href="http://ecolabelling.org/ecolabel/ecologo/" rel="ecolabel">ecologo</a>
<a href="http://ecolabelling.org/ecolabel/certified-carbonfree/" rel="ecolabel">certified-carbon-free</a>

=== XMDP profile ===
unknown/in development

=== Implementations ===
none

=== List of Ecolabels ===
http://ecolabelling.org/ecolabel/
see also: about ecolabelling.org: http://ecolabelling.org/about/

=== References ===
See Also

rel-ecolabel

2009-07-27T23:06:55Z

Spiritquest: /* Abstract */ - ideas on where the URL should point.

= Problem =

It's difficult to authenticate eco-friendly goods and services online.

* The proposed solution below is not a solution to the above problem. The proposed solution offers a mechanism by which a service can ''claim'' an eco-friendly label, but no way of ''authenticating'' that claim.

= Proposed Solution =

We are interested in establishing "rel-ecolabel" as a way of identifying ecolabelled (and thus eco-friendly) items (where item = ecolabel certified unit including products, services, companies, land, or any other thing that can be certified eco-friendly) on the World Wide Web.

Definition of an ecolabel: http://ecolabelling.org/eco-labels/

== Examples ==

Ecolabelled products appear on retailer and producer sites all over the web. There is currently no way of identifying them. Several examples are presented below:

URL: http://www.amazon.com/Newmans-Own-Organics-California-15-Ounce/dp/B000FNJNO6/ref=tag_stp_st_edpp_url
SCHEMA: Oregon Tilth
ecolabel: http://ecolabelling.org/ecolabel/oregon-tilth/

URL: http://www.environmentalbychoice.com/prestigious_papers/enviro100ecofibre.php
SCHEMA: FSC
ecolabel: http://ecolabelling.org/ecolabel/fsc-forest-management-certification/

URL: http://www.bestbuy.com/site/olspage.jsp?skuId=7838995&type=product&productCategoryId=pcmcat108700050027&id=1142297396649
SCHEMA: Energy star
ecolabel: http://ecolabelling.org/ecolabel/energy-star/

== Similar Microformats ==

rel-license: http://microformats.org/wiki/rel-license
indicates a "that the destination of that hyperlink is a license for the current page." whereas rel-ecolabel would indicate that the destination of that hyperlink is an ecolabel for a product, company or service listed on the page.

In this case I am uncertain if rel-license defines an authoritative source for license information. The difference with rel-ecolabel is that we would define an authoritative source at www.ecolabelling.org. We'd do this because there are many ecolabels 300+ and very few display their information in a standardised way. That being said, we're not beholden to this approach.

rel-tag: http://microformats.org/wiki/rel-tag

This would need to have the option / ability to point to the issuing labels site as well. Or if www.ecolabelling.org want to become the source, it should have a simple an quick method of adding labels into the system that aren't listed .. eg. a lot of UK based certified labels are currently not on the site. Would there be a conflict if I wanted to point the URL at the label associations website instead of www.ecolabelling.org (asked for discussion purposes)

Label example: Vegan Society Trademark: http://www.vegansociety.com/business/trademark/

== Ecolabel Schema ==

ecolabel entry @ ecolabelling.org
eg: http://ecolabelling.org/ecolabel/energy-star/

ecolabel entry @ greenerchoices.org
eg: http://greenerchoices.org/eco-labels/label.cfm?LabelID=15&searchType=Label%20index&searchValue=&refpage=labelIndex&refqstr=

ecolabel ISO types
eg: http://www.gen.gr.jp/eco.html

= Brainstorming =

== rel="ecolabel" ==

Rel-Ecolabel is a simple, open, format for indicating ecolabelled items which is embedable in HTML or XHTML, Atom, RSS, and arbitrary XML. Rel-Ecolabel is one of several microformat open standards.
Specification 2008-05-12

=== Author ===
Jacob Malthouse (http://bigroom.ca), formerly of ICANN (http://icann.org/)

=== Abstract ===
Rel-Ecolabel is one of several MicroFormats. By adding rel="ecolabel" to a hyperlink, a page indicates that the destination of that hyperlink is the ecolabel for an ecolabelled item listed on the current page. E.g. with the following hyperlink:

<a href="http://ecolabelling.org/ecolabel/ecologo/" rel="license">ecologo</a>

NOTE: in the highlighted portion - is this where we would put an ecolabel code or readable URL for ecolabelling.org entry?

the author indicates that the product, company, or services has obtained an "ecologo" certification.

--[[User:Spiritquest|Spiritquest]] 23:06, 27 July 2009 (UTC)

It seems that it might work well with being linked to an hproduct / hCard - to identify a manufacturer - I've yet to explore hproduct in detail.

I don't know that pointing the URL of the ecolabel directly to www.ecolabelling.com would work.

If I ran a product site with ecolabelled products, I would want to point to either a source of information on the label internally within the site, or have it point to a list of all data tagged with similar ecolables.

<a href="http://myproductsite.org/ecolabel/ecologo/" rel="license">ecologo</a>

The destination would then show all '''ecologo''' tagged products within the catalogue of myproductsite.org

maybe microformat parsing tools could be created to send users or pull information from www.ecolabelling.org site as a source of authoritative info and background on the label.

rel-tag as an example can point to an internal site structure using a taxonomy but can also use microformat tools to extend data searches to sites like technorati.

=== Multiple Licenses ===

Multiple such rel="ecolabel" hyperlinks indicate that multiple items on the page are available under any of the referred licenses. E.g. the following hyperlinks could be used to declare that a page is available under either an ecologo or a certified carbon free ecolabel:

<a href="http://ecolabelling.org/ecolabel/ecologo/" rel="ecolabel">ecologo</a>
<a href="http://ecolabelling.org/ecolabel/certified-carbonfree/" rel="ecolabel">certified-carbon-free</a>

=== XMDP profile ===
unknown/in development

=== Implementations ===
none

=== List of Ecolabels ===
http://ecolabelling.org/ecolabel/
see also: about ecolabelling.org: http://ecolabelling.org/about/

=== References ===
See Also

== RDFa ==

For contrast, the above rel=ecolabel proposal can already be implemented in [http://www.w3.org/TR/rdfa-syntax RDFa] using [http://dublincore.org/documents/dcmi-terms/ Dublin Core] very easily:

<pre><nowiki>
This product conforms to <a about="#product"
xmlns:dc="http://purl.org/dc/terms/" rel="dc:conformsTo"
href="http://ecolabelling.org/ecolabel/certified-carbonfree/">certified-carbon-free</a>
</nowiki></pre>

RDFa also allows these claims to be verified by the authority being linked to (in the case above ecolabelling.org) by simply providing an RDFa link back from http://ecolabelling.org/ecolabel/certified-carbonfree/ to our product page and labelling it with <tt>rev="dc:conformsTo"</tt>.

Re-using dc:conformsTo is also better than minting a new rel term. dc:conformsTo can be used in a wider set of situations that "ecolabel" in that it can be used to indicate non-ecological conformance to standards too. e.g. a web page can conform to HTML 4.01 Strict, or software could conform to "Certified for Windows Vista" or a toy could conform to a particular child safety standard.

{{cc-public-domain-release}}

rel-ecolabel

2009-07-27T22:45:18Z

Spiritquest: /* Similar Microformats */ alternatives pointing to source of label

= Problem =

It's difficult to authenticate eco-friendly goods and services online.

* The proposed solution below is not a solution to the above problem. The proposed solution offers a mechanism by which a service can ''claim'' an eco-friendly label, but no way of ''authenticating'' that claim.

= Proposed Solution =

We are interested in establishing "rel-ecolabel" as a way of identifying ecolabelled (and thus eco-friendly) items (where item = ecolabel certified unit including products, services, companies, land, or any other thing that can be certified eco-friendly) on the World Wide Web.

Definition of an ecolabel: http://ecolabelling.org/eco-labels/

== Examples ==

Ecolabelled products appear on retailer and producer sites all over the web. There is currently no way of identifying them. Several examples are presented below:

URL: http://www.amazon.com/Newmans-Own-Organics-California-15-Ounce/dp/B000FNJNO6/ref=tag_stp_st_edpp_url
SCHEMA: Oregon Tilth
ecolabel: http://ecolabelling.org/ecolabel/oregon-tilth/

URL: http://www.environmentalbychoice.com/prestigious_papers/enviro100ecofibre.php
SCHEMA: FSC
ecolabel: http://ecolabelling.org/ecolabel/fsc-forest-management-certification/

URL: http://www.bestbuy.com/site/olspage.jsp?skuId=7838995&type=product&productCategoryId=pcmcat108700050027&id=1142297396649
SCHEMA: Energy star
ecolabel: http://ecolabelling.org/ecolabel/energy-star/

== Similar Microformats ==

rel-license: http://microformats.org/wiki/rel-license
indicates a "that the destination of that hyperlink is a license for the current page." whereas rel-ecolabel would indicate that the destination of that hyperlink is an ecolabel for a product, company or service listed on the page.

In this case I am uncertain if rel-license defines an authoritative source for license information. The difference with rel-ecolabel is that we would define an authoritative source at www.ecolabelling.org. We'd do this because there are many ecolabels 300+ and very few display their information in a standardised way. That being said, we're not beholden to this approach.

rel-tag: http://microformats.org/wiki/rel-tag

This would need to have the option / ability to point to the issuing labels site as well. Or if www.ecolabelling.org want to become the source, it should have a simple an quick method of adding labels into the system that aren't listed .. eg. a lot of UK based certified labels are currently not on the site. Would there be a conflict if I wanted to point the URL at the label associations website instead of www.ecolabelling.org (asked for discussion purposes)

Label example: Vegan Society Trademark: http://www.vegansociety.com/business/trademark/

== Ecolabel Schema ==

ecolabel entry @ ecolabelling.org
eg: http://ecolabelling.org/ecolabel/energy-star/

ecolabel entry @ greenerchoices.org
eg: http://greenerchoices.org/eco-labels/label.cfm?LabelID=15&searchType=Label%20index&searchValue=&refpage=labelIndex&refqstr=

ecolabel ISO types
eg: http://www.gen.gr.jp/eco.html

= Brainstorming =

== rel="ecolabel" ==

Rel-Ecolabel is a simple, open, format for indicating ecolabelled items which is embedable in HTML or XHTML, Atom, RSS, and arbitrary XML. Rel-Ecolabel is one of several microformat open standards.
Specification 2008-05-12

=== Author ===
Jacob Malthouse (http://bigroom.ca), formerly of ICANN (http://icann.org/)

=== Abstract ===
Rel-Ecolabel is one of several MicroFormats. By adding rel="ecolabel" to a hyperlink, a page indicates that the destination of that hyperlink is the ecolabel for an ecolabelled item listed on the current page. E.g. with the following hyperlink:

<a href="http://ecolabelling.org/ecolabel/ecologo/" rel="license">ecologo</a>

NOTE: in the highlighted portion - is this where we would put an ecolabel code or readable URL for ecolabelling.org entry?

the author indicates that the product, company, or services has obtained an "ecologo" certification.

=== Multiple Licenses ===

Multiple such rel="ecolabel" hyperlinks indicate that multiple items on the page are available under any of the referred licenses. E.g. the following hyperlinks could be used to declare that a page is available under either an ecologo or a certified carbon free ecolabel:

<a href="http://ecolabelling.org/ecolabel/ecologo/" rel="ecolabel">ecologo</a>
<a href="http://ecolabelling.org/ecolabel/certified-carbonfree/" rel="ecolabel">certified-carbon-free</a>

=== XMDP profile ===
unknown/in development

=== Implementations ===
none

=== List of Ecolabels ===
http://ecolabelling.org/ecolabel/
see also: about ecolabelling.org: http://ecolabelling.org/about/

=== References ===
See Also

== RDFa ==

For contrast, the above rel=ecolabel proposal can already be implemented in [http://www.w3.org/TR/rdfa-syntax RDFa] using [http://dublincore.org/documents/dcmi-terms/ Dublin Core] very easily:

<pre><nowiki>
This product conforms to <a about="#product"
xmlns:dc="http://purl.org/dc/terms/" rel="dc:conformsTo"
href="http://ecolabelling.org/ecolabel/certified-carbonfree/">certified-carbon-free</a>
</nowiki></pre>

RDFa also allows these claims to be verified by the authority being linked to (in the case above ecolabelling.org) by simply providing an RDFa link back from http://ecolabelling.org/ecolabel/certified-carbonfree/ to our product page and labelling it with <tt>rev="dc:conformsTo"</tt>.

Re-using dc:conformsTo is also better than minting a new rel term. dc:conformsTo can be used in a wider set of situations that "ecolabel" in that it can be used to indicate non-ecological conformance to standards too. e.g. a web page can conform to HTML 4.01 Strict, or software could conform to "Certified for Windows Vista" or a toy could conform to a particular child safety standard.

{{cc-public-domain-release}}

User:Spiritquest

2009-07-27T10:51:17Z

Spiritquest: Expanded Profile

meetup

2009-07-27T10:44:55Z

Spiritquest: /* London */

<entry-title>Weekly Meetups & Dinners</entry-title>
{{TOC-right}}<div>http://farm4.static.flickr.com/3216/2836380076_9251390ded_m.jpg</div> A regular source of microformats [[events]].
== Weekly Meetup ==
The community and adoption have grown considerably over the last year, and news of adoptions (and once in a while challenges) come up frequently enough ([http://news.google.com/news?q=microformats&ie=UTF-8&scoring=n at least once a week]) that there are no shortage of new topics to discuss on a weekly basis. See [[weekly-meetup#purpose|purpose]] for more.

[[weekly-meetup#Organize_a_weekly_meetup|Organize a weekly meetup]]!

By making this a regular (every Tuesday) event, people know it is happening regularly and can thus come whichever ones are convenient for them, and not worry about missing any one in particular.

Cities where weekly meetup events are held, sorted alphabetically:

== London ==
In London, Tuesdays at 7:30pm worked well.

Interested in general for London:
* [[User:Phae|Frances]]
* [[User:GeorgeBrock|George Brocklehurst]]
* [http://twitter.com/ptg/statuses/906735728 Patrick Griffiths]
* [[User:Spiritquest|Ketan Majmudar ]]
* ...

Possible locations:
* ...

Past London venues:
* [http://www.squaremeal.co.uk/restaurants/london/view/81375/Wagamama Wagamama at New Oxford St. & Bloomsbury St.]: [[events/2008-09-02-london-meetup-dinner|2008-09-02]]
* [http://upcoming.yahoo.com/venue/213236/ The Princess at 76 Paul St.]: [[events/2008-09-09-london-meetup-dinner|2008-09-09]]

== San Francisco ==
From having informally asked a few folks in the SF area and on IRC it seems Tuesdays at 6:30pm work best, with a rotating venue to keep it interesting.

Additional suggested SF venues (suggester). Add your opinions and more suggestions:
* Osha Thai on 2nd st.
* Thirsty Bear
** +0 ok food, often too crowded for a group to actually get seating, though we did hold a [[events/2007-04-18-web-2-expo-dinner|microformats dinner there last year]] somehow. I think John Allsopp sweet talked the hostess. - [[User:Tantek|Tantek]]
* Mel's Diner
** +0 hard to order healthy here, but the food mostly tastes good, and can probably get seating for a decent crowd at 6:30pm - [[User:Tantek|Tantek]]
* Sugar Cafe
* Axis Cafe
* Naan & Curry on O'Farrell & Mason
* [http://www.yelp.com/biz/a-la-turca-restaurant-san-francisco A La Turca Restaurant]
* ...

=== past SF venues ===
Past SF venues. We'll reuse these at some point I'm sure.

'''This section needs updating with dinners that have occurred since 2008-10-28.'''

Please update the following list by looking at [[events-2008]] and more recent [[events]], and add links (even just one more would help!) to dinners starting from the "since" date above, and update that date accordingly so that other contributors know where to continue updating from. Thanks!

* Chaat Cafe: [[events/2008-06-24-weekly-meetup-dinner|2008-06-24]], [[events/2008-07-22-weekly-meetup-dinner|2008-07-22]]
* Crepes on Cole: [[events/2008-07-01-weekly-meetup-dinner|2008-07-01]]
* Westfield Food Court: [[events/2008-07-08-weekly-meetup-dinner|2008-07-08]], [[events/2008-08-19-weekly-meetup-dinner|2008-08-19]]
* South Park (lunch) : [[events/2008-07-15-weekly-meetup-lunch|2008-07-15]], [[events/2008-09-23-sf-weekly-meetup-lunch|2008-09-23]]
* Chevy's SOMA: [[events/2008-07-29-weekly-meetup-dinner|2008-07-29]]
* Brickhouse Cafe: [[events/2008-08-05-weekly-meetup-dinner|2008-08-05]]
* Pancho Villa: [[events/2008-08-12-weekly-meetup-dinner|2008-08-12]]
* 21st Amendment: [[events/2008-08-26-weekly-meetup-dinner|2008-08-26]], [[events/2008-09-16-sf-weekly-meetup-dinner|2008-09-16]], [[events/2008-10-28-sf-weekly-meetup-dinner|2008-10-28]]
* Blondie's Pizza on Powell st: [[events/2008-09-02-weekly-meetup-dinner|2008-09-02]]
* Metreon Food Court: [[events/2008-09-09-weekly-meetup-dinner|2008-09-09]]
* Naan & Chutney on Haight st.: [[events/2008-09-30-sf-weekly-meetup-dinner|2008-09-30]]
* Taylor's Automatic Refresher: [[events/2008-10-14-sf-weekly-meetup-dinner|2008-10-14]]
* Mehfil: [[events/2008-10-21-sf-weekly-meetup-dinner|2008-10-21]]
* 3rd Street Grill
* California Pizza Kitchen on 3rd
* Crepevine on Church

== Other Cities ==
Want a microformats meetup in your city? Organize one! Add your city and name to this list. Contact others from your city and [[weekly-meetup#Organize_a_weekly_meetup|organize a meetup]]. Once you do one, add another section for your city above this "Other Cities" section, and list suggested venues, past venues with links to meetup event pages etc.

There has been some interest expressed in organizing dinners in the following cities. Add yourself and/or contact the people listed and make it happen!
* Austin - [[irc]] Atamido
* Kansas City - [http://twitter.com/dckc/statuses/1116151301 Dan Connolly]
* Montreal - [[User:Csarven|Sarven Capadisli]]
* San Diego - [[User:EdwardOConnor]]
* San Jose (South Bay) - [[User:Kevin_Marks|Kevin Marks]], Rohit Khare
* Seattle, WA - [[User:jandrick|Jeremiah Andrick]], Colin Henry, Andy Woods

== Organize a weekly meetup ==
Anyone can organize a microformats weekly meetup or dinner!

At a minimum, all you need is:
# '''At least one other person''' that commits to go (so at least you know you'll have a good conversation about microformats with at least one person).
# '''A location'''

And organizing a weekly meetup requires you to at a minimum:
# '''Pick a location'''
# '''Announce it''' (location at 18:30, Tuesday) on various event sites and notification services like Twitter etc.

That's it. If you prefer a step-by-step list of instructions and details, to remove nearly all doubt, here you go:
# Pick a location
#* Ask folks on [[IRC]] if they have any suggested locations.
#* Consider locations that are easy for a variety of people to transit to.
#* Consider a new location to keep it interesting.
# Create the Events Pages
## Create specific event page on microformats.org wiki, follow the form <code>YYYY-MM-DD-weekly-dinner-CITYCODE</code> — e.g. <samp>2009-01-06-weekly-dinner-sf</samp> in San Francisco, or <samp>2009-01-06-weekly-dinner-ldn</samp> in London.
##* Copy the Weekly Dinner template code ([[weekly-meetup#Event_Template|below]]), and make the following edits:
##** Update dates and locations in the infobox at the top.
##** Update the tags list, adding the event specific tag for this event.
##** Update the URLs for Upcoming, Technorati, Google Blog Search and Flickr. These search on the event tag itself, so need to date portion updated.
##** Add yourself as an attendee
##** (For SF weekly meetup dinners, [[MatthewLevine|Matthew Levine]] has created a script to automatically generate wiki page source by parsing the [[hCalendar]] from the related [http://upcoming.org upcoming] event. To use this script, create an upcoming event '''first''', then visit <kbd>http://www.phusikos.com/event.php?upcoming_id=$upcoming_id</kbd>, e.g. [http://www.phusikos.com/event.php?upcoming_id=2656901 sample conversion link].)
## Create an [http://upcoming.org upcoming] event, summarizing the event and linking to the new wiki page you just created.
##* Just after creating the event, Upcoming gives you the option to "upload an official photo or image", click that link and upload <nowiki>http://farm4.static.flickr.com/3216/2836380076_9251390ded.jpg</nowiki>, making it the official photo for the event. Thanks to [http://www.flickr.com/photos/cindyli/2836380076 Cindy Li for the cool microformats meetup graphic!].
##* Add the event to the Microformats, Web2.0, Bay Area Web Geeks, Web Developers, Geek Dinners and Social Network Portability groups.
##* Update the wiki events page with Upcoming.org event tag (<samp>upcoming:event=00000000</samp>) you just created. You can copy and paste the previous meetup/dinner summary and change the relevant detail.
# '''Announce it'''
#* [http://twitter.com/ Tweet] the upcoming event
#* On the day of the event, post a reminder in the morning (to Twitter etc.), and again an hour before the event.
# At the event, take a photo and post it to BrightKite, Flickr etc.
# Afterwards
#* Post a thank you note thanking those that attended, invite them to add their content to the wiki.
#* Update the wiki event page with details of discussions, photographs, blog links and so forth.

===Event Template===

<source lang=html4strict><entry-title>Microformats Weekly Dinner, San Francisco</entry-title>
__TOC__
One of several microformats [[weekly-meetup]] [[events]].

<div class="event-page vevent">
== Details ==
;When
:<span class="dtstart">2009-MM-DDT18:30-0800</span> to <span class="dtend">2009-MM-DDT20:30-0800</span>
;Where
:<span class="location">TBA</span>
;What
:<span class="summary">Microformats Weekly Meetup Dinner, San Francisco</span>
;Web
:<span class="url">http://upcoming.yahoo.com/event/00000000/</span>

'''[http://feeds.technorati.com/events/referer Add this event to your calendar]''' http://www.boogdesign.com/images/buttons/microformat_hcalendar.png

== Weekly Meetup ==
<div class="description">The microformats community has grown and stablized over the past few years, news of adoptions, new ideas and challenges come up frequently enough that there are no shortage of new topics to discuss on a weekly basis.

Come along, meet up with the microformats community in San Francisco

In another city? Check out [[weekly-meetup#Other_Cities|Weekly Meetup: Other Cities]] and help organize one in your own city!</div>

== Tags ==
Use the following tags on related content (blog posts, photos, [http://twitter.com tweets]):

tags:
<kbd class="tags" style="display:block">
<span class="category">'''microformats-dinner'''</span>
<span class="category">microformats-meetup</span>
<span class="category">microformats</span>
<span class="category">san-francisco</span>
<span class="category">''microformats-dinner-2009-MM-DD''</span> 
<span class="category">''upcoming:event=00000000''</span> 
</kbd>

If you use Twitter, mention ''@microformats dinner''' in tweets about the event, and track them on [http://search.twitter.com/search?q=microformats+dinner Twitter Search].

== Attendees ==
Add yourself alphabetically sorted by family name if you plan on attending or attended this event.

* [[User:YourName|You]]
* …

== Notes ==

Topics Discussed:

* …

== Photographs ==


* Search for photographs from this event on Flickr: [http://flickr.com/photos/tags/microformats-dinner-2009-MM-DD Photographs tagged microformats-dinner-2009-MM-DD] or for [http://flickr.com/photos/tags/microformats-dinner all photographs from microformats dinners].

''Add a photograph from this event here''.

== Articles and Blog Posts ==
Articles and blog posts following up on the meetup. Add a link to your post in the list below:

* …


Also, find posts on this meetup on [http://blogsearch.google.co.uk/blogsearch?q=microformats-dinner-2009-MM-DD Google Blog Search] or [http://technorati.com/search/microformats-dinner-2009-MM-DD Technorati].

</div> 

== Related Pages==
{{events-related-pages}}</source>

== purpose ==
In addition to providing a convenient forum for community members to get together once in a while and talk about the [http://news.google.com/news?q=microformats&ie=UTF-8&scoring=n latest news about microformats], the weekly meetups serve many good ends.

Perhaps most importantly, weekly meetups really help communication and community. People that have met in person usually treat each other nicer online, thus very much help encourage everyone to [[mailing-list#Be_nice|be nice]] in IRC, mailing lists etc.

== FAQ ==
Perhaps move to [[weekly-meetup-faq]] if this section gets too big.

=== general talk ===
* Q: Do you just talk in general about microformats?
* A: As there's been new people at every microformat meetup, there's almost always at least some general talk about microformats.

=== newcomers vs detail ===
* Q: How do you handle newcomers and at the same time get into detailed stuff?
* A: Usually there are multiple conversations going, so there's almost always a good conversation to participate in. Also, it helps everyone to talk with newcomers and get fresh perspectives, as well as practiced at effectively communicating [[what-are-microformats|what microformats are]], [[benefits]], [[get-started|how to use]] etc.

=== existing issues ===
* Q: Do you try to solve some existing issues?
* A: We have discussed existing issues in some past meetups. Often divisive or controversial topics are much easier to discuss and understand multiple perspectives on in person. For example, [[User:BenWard|Ben Ward]] and [[User:Tantek|Tantek]] have made some good progress on understanding various perspectives on [[value-excerption-brainstorming]] and are optimistic about making progress on related issues.

=== notes ===
* Q: Do you take notes?
* A: Everyone is encouraged to take notes and contribute aspects of conversations, topics etc. on the wiki page for the meetup.

== related ==
* [[weekly-meetup-brainstorming]] to capture how to make the meet-up more exciting and give more practical use-cases
* [[events]]

User:Spiritquest

2009-07-26T19:27:34Z

Spiritquest: New page: Developer, Designer & Semantic Web Lover

Developer, Designer & Semantic Web Lover

User:Ket Majmudar

2009-07-25T21:57:23Z

Spiritquest:

User:Ket Majmudar

2009-07-25T19:12:41Z

Spiritquest: New page: My IRC username is ethicaljunction (atm) Interested and using microformats in my web development, interested in how it can help my organisation.

My IRC username is ethicaljunction (atm)

Interested and using microformats in my web development, interested in how it can help my organisation.

irc-people

2009-07-25T19:11:23Z

Spiritquest:

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

* {{irc user|Amodal1| amodal1|-0500/-0600}}
* {{irc user|Adam Ballai|AdamBallai|-700/-700}}
* {{irc user|Adam Craven|AdamCraven|+0000}}
* {{irc user|Alenonimo|Alenonimo|-0300}}
* {{irc user|Alexander Graf|AlexanderGraf|+0100}}
* {{irc user|Tomasino|aloneone|-0500}}
* {{irc user|AmanuelTewolde|Amanuel|-0500/-0400}}
* {{irc user|Amette|amette|+1000}}
* {{irc user|Amir Guindehi|AmirGuindehi|+1000}}
* {{irc user|Andr3|andr3|+0000}}
* {{irc user|Ajaswa|Andrew Jaswa|-0500}}
* {{irc user|AndrewDisley|AndrewDisley|+0000}}
* {{irc user|Andrii Ponomarov|Andrii|+0300}}
* {{irc user|AnselHalliburton|anselxyz|-0800/-0700}}
* {{irc user|Ashe Dryden|Ashe|-600}}
* {{irc user|Atamido|Atamido|-0600/-0500}}
* {{irc user|Barce|Barce|-0800/-0700}}
* {{irc user|Azathoth|Florian Beer|+1000}}
* {{irc user|Tyler Roehmholdt|Baristo|-0800/-0700}}
* {{irc user|Belling|Belling|-0800/-0700}}
* {{irc user|BenjaminCarlyle|BenjaminCarlyle|+1000}}
* {{irc user|HenriBergius|bergie|+0200/+0300}}
* {{irc user|Ben Ward|BenWard|-0800/-0700}}
* {{irc user|BenWest|bewest|-0800/-0700}}
* {{irc user|B.K._DeLong|bkdelong|-0500/-0400}}
* {{irc user|Robert|blueace|+0100}}
* {{irc user|Robert|blueace|+0100}}
* {{irc user|BluesMoon|bluesmoon|+0530}}
* {{irc user|BobChao|BobChao|+0800}}
* {{irc user|Bob Jonkman|BobJonkman|-0500/-0400}}
* {{irc user|Boneill|boneill|+0000}}
* {{irc user|Brian|briansuda|+0000}}
* {{irc user|TimT|bringo|-0800/-0700}}
* {{irc user|Briski|Briski|+0000}}
* {{irc user|BryanL|BryanL|-0500/-0400}}
* {{irc user|BryanRieger|Bryan Rieger|+0000}}
* {{irc user|Bug-E|Bug-E|+0200}}
* {{irc user|CarlaHufstedler|carlamagpie|-0500/-0400}}
* {{irc user|Colin_Barrett|cbarrett|-1000}}
* {{irc user|Cognizance|Cognizance|-0800/-0700}}
* {{irc user|ColinDDevroe|cdevroe|-0500/-0600}}
* {{irc user|Cgriego|cgriego|-0600/-0500}}
* {{irc user|Charlvn|Charl|+0200/+0200}}
* {{irc user|CharlesRoper|charles_r|0000/+0100}}
* {{irc user|Chris_Cressman|Chris Cressman|-0500/-0400}}
* {{irc user|ChristopherStJohn|cks|-0600/-0500}}
* {{irc user|JeremyBoggs|clioweb|-5000/-4000}}
* {{irc user|Cloud|Cloud|+0000}}
* {{irc user|Cruster|cruster|+0200}}
* {{irc user|Csarven|csarven|-0500/-0400}}
* {{irc user|ChrisBrentano|ctb|-0800/-0700}}
* {{irc user|DanC|DanC|-0600/-0500}}
* {{irc user|DanielBurka|DanielBurka|-0400}}
* {{irc user|DanielJohnLewis|danieljohnlewis|0000}}
* {{irc user|DannyAyers|danja|+0100/+0200}}
* {{irc user|Dave Cardwell|davecardwell|+0000}}
* {{irc user|DavidMead|DavidMead|-0400}}
* {{irc user|DavidRussell|davidrussell|-0600/-0500}}
* {{irc user|DBounds|Darren Bounds|-0500}}
* {{irc user|Ddonat|David Gratton|-0800/-700}}
* {{irc user|DenisDefreyne|ddfreyne|+0100/+0200}}
* {{irc user|DeanEro|deanero|-0800/-0700}}
* {{irc user|DeepText|Deep Text|-0800/-0700}}
* {{irc user|DerrickPallas|DerrickPallas|-0800/-0700}}
* {{irc user|DimitriGlazkov|dglazkov|-0600/-0500}}
* {{irc user|DiegoBudny|DiegoBudny|<small>-unspecified-</small>}}
* {{irc user|DKerzman|DKerzman|-0600}}
* {{irc user|Dan Kubb|dkubb|-0800/-0700}}
* {{irc user|DrErnie|DrErnie|-0800/-0700}}
* {{irc user|DrewMcLellan|drewinthehead|+0000/+0100}}
* {{irc user|DrewBell|droob|-0600/-0500}}
* {{irc user|DimitriosZachariadis|dzach|+0200/+0300}}
* {{irc user|DydimusTK|dydimustk|-0600}}
* {{irc user|Ed Summers|edsu|-0500/-0400}}
* {{irc user|Enric|Enric|-0800/-0700}} (alt sp "enric")
* {{irc user|Evan|evanpro|-0500}}
* {{irc user|Evan|e_s_p|-0500}}
* {{irc user|Ket Majmudar|ethicaljunction|+0100}}
* {{irc user|EdwardWelker|ewelker|-0500}}
* {{irc user|ChrisMessina|factoryjoe|-0800/-0700}}
* {{irc user|Fil|Fil|+0200}}
* {{irc user|CFinke|Finke|-0700/-0600}}
* {{irc user|MarkoMrdjenovic|friedcell|+0100/+0200}}
* {{irc user|GarethR|garethr|+0000/+0100}}
* {{irc user|GeorgeBrock|georgebrock|+0000/+0100}}
* {{irc user|Grantbow|Grantbow|-0800/-0700}}
* {{irc user|Griffin|Griffin|-0600/-0500}}
* {{irc user|Guillaume Lebleu|glebleu|-0800}}
* {{irc user|Aubergine10|Guy Fraser|+0100/+0000}}
* {{irc user|HenrichPoehls|HenrichP|+0100}}
* {{irc user|IanHickson|Hixie|-0800/-0700}}
* {{irc user|Hlb|hlb|+0800-0700}}
* {{irc user|EdwardOConnor|hober|-0800/-0700}}
* {{irc user|Ichigo|ichigo|+1000}}
* {{irc user|Alper|illustir|+0100}}
* {{irc user|Inkbase|inkbase|-0800/-0700}}
* {{irc user|IwaiMasaharu|iwaim|+0900}}
* {{irc user|Izo|IZO|<small>-unspecified-</small>}}
* {{irc user|Jabz|Jabz|+0000}}
* {{irc user|JamieKnight|JamieKnight|+1000/0000}}
* {{irc user|JayMyers|jaymyers|-0600/-0500}}
* {{irc user|JoeGregorio|jcgregorio|<small>-unspecified-</small>}}
* {{irc user|WizardIsHungry|jcw9|-0500/-0400}}
* {{irc user|Adactio|Jeremy Keith|+0000}}
* {{irc user|jrodgers|JesseRodgers|-0500}}
* {{irc user|JasonK|jkridner|-0600/-0500}}
* {{irc user|JeffMcNeill|jeffmcneill|-1000}}
* {{irc user|JimboJW|jimbojw|-0600/-0500}}
* {{irc user|Jonathan_Arkell|jonnay|-0700/0600}}
* {{irc user|JosephHolsten|josephholsten|-0600/-0500}}
* {{irc user|JulianStahnke|julianstahnke|+0000}}
* {{irc user|Kapowaz|kapowaz|+0000/+0100}}
* {{irc user|Keri Henare|kerihenare|+1200}}
* {{irc user|KevBurnsJr|kevburnsjr|-0800}}
* [http://epeus.blogspot.com/ KevinMarks] (-0800/-0700)
* {{irc user|RyanKing|kingryan|-0800/-0700}}
** [http://theryanking.com/blog/archives/2006/04/19/office-hours/ Office hours]: Wednesday, 21:00 UTC
* {{irc user|Lachlan Hunt|Lachy|+1000/+1100}}
* {{irc user|Levitation|levitation[A]|+0200/+0300}}
* {{irc user|Linmic|linmic|+0800-0700}}
* {{irc user|MarkNg|madness|+0000/+0100}}
* {{irc user|Mark Mansour|Mark Mansour|+1100}}
* {{irc user|MarkNormanFrancis|Mark Norman Francis|+0000/+0100}}
* {{irc user|Maddiin|Martin Czura|+0100}}
* {{irc user|MattBowen|Matt Bowen|-0500/-0400}}
* {{irc user|Groningen|Matthias Kluth|+0100}}
* {{irc user|MattisManzel|Mattis Manzel|+0100/+0200}}
* {{irc user|CiaranMc|McNulty|+0000/+0100}}
* <span class="vcard"><span class="fn org">[[mfbot]]</span> - a bot which logs all edits to this wiki. It appends a number with a '+' or '-' sign, to indicate the number of characters added or removed as a result of the edit.</span>
* {{irc user|Mike|Michael McCracken(mmc)|-0800/-0700}}
* {{irc user|MikeKaply|mkaply|-0600/-0500}}
* {{irc user|SteveIvy|monkinetic/redmonk|-0700}}
* {{irc user|MWTE|mwte|+0000/+0100}}
* {{irc user|RobManson|nambor|+1000}}
* {{irc user|Nelix|nelix|+1000}}
* {{irc user|neuro|neuro|<small>-unspecified-</small>}}
* {{irc user|Niekie|niekie|+0100/+0200}}
* {{irc user|NTollervey|ntoll|+0000/+0100}}
* {{irc user|Pawlik|pawlik|+0100/+0200}}
* {{irc user|Andy Pemberton|pembertona|-0500/-0400}}
* {{irc user|Phae|Phae|+0000/+0100}}
* {{irc user|pius|Pius Uzamere|+0500}}
* {{irc user|PriitLaes|plaes|+0200/+0300}}
* {{irc user|ChrisCasciano|pnhChris|-0500/-0400}}
* {{irc user|Hugopeixoto|Politoed|+0000/+0100}}
* {{irc user|PetarPopov|popov|-0800/-0700}}
* {{irc user|Pfefferle|pfefferle|+0100/+0200}}
* {{irc user|Lauren Scime|pseudowish|-0800/-700}}
* {{irc user|DavidOsolkowski|qid|-0500}}
* {{irc user|RCanine|RCanine|-0500/-0400}}
* {{irc user|Remi|Remi|-0500/-0400}}
* {{irc user|ZachCarter|riah|-0500/-0400}}
* {{irc user|RobertBachmann|RobertBachmann|+0100/+0200}}
** Office hours: <s>Wednesday, 18:00-20:00 UTC</s> (Currently no office hours}}
* {{irc user|RobLinton|RobLinton|-0800/-0700}}
* {{irc user|Ronnos|Ron Kok|+0000}}
* {{irc user|SamJohnston|samj|+0100/+0200}}
* {{irc user|SarahWorsham|sazbean|-0500/-0400}}
* {{irc user|ScottNelle|snelle|-0500/-0400}}
* {{irc user|ScottRozic|gravitas|-0500/+0100}}
* {{irc user|Dana Benson|Snowden|-0800/-0700}}
* {{irc user|SinDoc|SinDoc|+0100/+0200}}
* {{irc user|Savell Martin|Savell|+0000/+0000}}
* {{irc user|Smackman|Steve Farrell|-0800/-0700}}
* {{irc user|SpikeUK|SpikeUK|+0000/+0100}}
* {{irc user|Steve Ganz|SteveGanz|-0800/-0700}}
* {{irc user|Stii|Stii|+0200 GMT}}
* {{irc user|ReinierZ|surial|+0100 GMT}}
* {{irc user|SuperPhly|SuperPhly|-600/-500}}
* {{irc user|SyedSRahman|syedsrahman|+0530}}
* <span class="vcard"><span class="fn">sym[[User:LynX|lynX]]</span></span> or (better) [[User:LynX|lynX]] on [http://about.psyc.eu PSYC] (+0100}}
* {{irc user|DavidLehn|taaz|-0500/-0400}}
* {{irc user|Tantek|Tantek|-0800/-0700}}
* {{irc user|Wojciech|theanxy|+0100/+0200}}
* {{irc user|TheJbf|thejbf|+0100/+0200}}
* {{irc user|TobyInk|tobyink|+0000/+0100}}
* {{irc user|Trovster|trovster|-0800/-0700}}
* {{irc user|Vadania|vadania|-0600/-0700}}
* {{irc user|Vant|vant|+0900}}
* {{irc user|Victor|victor|+0100/+0200}}
* {{irc user|V-I-P|V-I-P|+0100/+0200}}
* {{irc user|KrissWatt|VoodooChild|+0000/+0100}}
* {{irc user|WebOrganics|weborganics|+0100}}
* {{irc user|JacksonWilkinson|whafro|-0500/-0400}}
* {{irc user|Richard Conyard|WhiskeyM|+0000}}
* {{irc user|Veeliam|William Lawrence|-0800/-0700}}
* {{irc user|StevenWoods|woodss|+0000 GMT}}
* {{irc user|Ianloic|yakk|-0800/-0700}}
* {{irc user|LarsStrojny|mastaYoda|+0100}}
* {{irc user|ZimbaTm|zimbatm|+0100}}
* {{irc user|FoundAtion|Foundation|-0800}}
* {{irc user|PJKix|pjkix|-0800/-700}}
* {{irc user| ChrisBroadfoot|broady|+1000}}
* {{irc user|Natalie Downe|NatBat|+0000}}
* {{irc user|Dotjay|dotjay|+0000}}
* {{irc user|PeterHellberg|zil|+0100}}
* {{irc user|Kiryl Zhybul|zkv|+0400}}
* {{irc user|ScottThorpe|Salve|-0800/-0700}}
* {{irc user|Dane|imdane|-0600/-0500}}
* {{irc user|ThomasLoertsch|tl|+0100/+0200}}
* {{irc user|Francisco Bernardo|frantic0|+0100/+0200}}
* {{irc user|Steven Osborn|steve918|-0700/-0800}}
* {{irc user|Trodrigues|trodrigues|+0000}}