Microformats Wiki - User contributions [en]

User:GeorgeBrock

2010-04-17T13:54:55Z

GeorgeBrock: Update old information and add public domain release.

<entry-title>George Brocklehurst (georgebrock)</entry-title>

<div class="vcard">
<span class="fn">George Brocklehurst</span>, works for <span class="org">Reevoo</span>.
More at <span class="url">http://georgebrock.com</span>
</div>

== Interests ==

Given that I now work for a product reviews company, I'm currently most interested in working on:

* [[hReview]] and [[hReview-aggregate]]
* [[hProduct]]

== Public Domain ==

{{cc-public-domain-release}}

hproduct-issues

2010-04-17T13:47:16Z

GeorgeBrock: /* HP8 - No clear way of including a valid hReview that refers back to the hProduct as its item */ Capture Toby's objections

__TOC__

== HP1 - hProduct vs hListing regarding "price" / "quantity" / "shipping" fields ==

<div class="vevent">
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-12-17</span> raised by <span class="fn">NicolasLeroy</span></span>
<div class="description">
*# In the "[[hproduct#Out_of_Scope|out of scope]]" section, it is explained: _"This microformat does not intend to replicate any of the content proposed within hListing and would defer all money/transactional matters to that microformat"_
*# However, in the hProduct schema, we have the following fields:
*#* "price. optional. floating point number. can be further refined by type (msrp, regular, sale, clearance)" => if the price is the retailer price, then it should be delegated to hListing. We could imagine it represents the "manufacturer" price (which could be different from the retailer price) ; in this case, it should clearly be explained in the schema definition.
*#* I would say there is also ambiguity between the responsibilities of hProduct vs hListing for the following fields: quantity / shipping
*#** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-02-16</span>: I believe everyone agrees that we would borrow price from hListing for hProduct spec. I will explain the concept further in the schema.
*#** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-02-16</span>: I don't follow the quantity/ shipping issue. I don't see either of these on hListing, unless the concepts are somehow embedded in other attributes. Can you elaborate on what the ambiguity is? ([[User:PaulLee|Paul Lee]]: If there's no objection here, may I suggest updating the price reference and keeping quantity and shipping as is?])
*#* +1 I agree with NicholasLeroy, anything price or transaction related should be left out of hProduct 0.1, and instead develop recipes / mark-up examples showing use of hListing with hProduct. We need to strongly resist and fight the tendency to include "just one more field" to individual formats and instead push to use formats as building blocks. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
*#** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2009-03-03</span>: If price should be left to hListing, should hAudio be modified not to include "price"?
*#* I am going to add price back into the hProduct spec. Price is an attribute of a product. We should be able to use microformats either standalone or as building blocks in combination with other formats. On price I'm thinking specifically of product manufacturer sites who may not be commerce enabled and are listing their products for informational purposes. In this case, they would not be using hListing, as there would be no transaction taking place. Leaving the price attribute out would ignore a major product attribute (in 99% of product sites, per hproduct examples analysis).
</div>
</div>

<div class="vevent">

== <span class="summary">HP2 - FN should be used instead of N for product title</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* Why is <b>n</b> used instead of <b>fn</b> for the title of the product? hCard and hAudio both use fn for the formatted name of the product. <b>n</b> is usually an optimization.
* +1 hProduct should use "fn" for the name of the product. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-03-03</span>: "n" will be changed to "fn" in the next version of the schema
* "fn" is hardly semantic, even though commonly deployed - surely "formatted-name" is truer to the principles of "humans-first, machines second" --[[User:Wowitim|Wowitim]] 12:59, 28 March 2009 (UTC)
</div>

<div class="vevent">

== <span class="summary">HP3 - BUY duplicates functionality of PAYMENT from hAudio</span> ==
* {{OpenIssue}} <span class="vcard">BUY duplicates functionality of PAYMENT from hAudio<span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* <b>buy</b> is duplicating the functionality of <b>payment</b> from hAudio.
** Response <span class="vcard">by <span class="fn">[[User:PaulLee|Paul Lee]]</span>, 2008-02-18</span>: From the payment page: "RelPayment is a microformat for making exchanges of support (be it financial or otherwise) possible. By adding rel="payment" to a hyperlink a page indicates that the destination of that hyperlink provides a way to show or give support for the current page. For example to give financial support to the owner of the current page. One of the goals with this microformat is to give content aggregators such as RSS readers a way to extract these support links and give them special attention (such as displaying a standard button along with the content)." First, this seems like a simple exercise for blogs, etc.; but the transaction process for shopping sites is typically considerably more complex. Usually, the actual payment URI is toward the end of the cart checkout process, the entry to which "buy" is intended to direct to the beginning of. Second, there is the potential for confusion when using payment, since "payment" in the shopping space often refers to payment methods, e.g., credit card, check, etc.
* +1 but in a different way. BUY/PAYMENT should both be out of scope for hProduct, and only be in hListing per issue HP1 above. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
*#* Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2009-03-03</span>: Should these be in scope for hAudio then?
</div>
</div>

<div class="vevent">

== <span class="summary">HP4 - Are all of the formats for PRICE in hProduct allowed</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* The way that <b>price</b> is used is iffy - do we allow anything but currency/amount in the compound statement?
* +1 PRICE should not be in hProduct per issue HP1. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
*#* Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2009-03-03</span>: Should other microformats (thinking hAudio) be modified not to include "price"?
</div>
</div>

<div class="vevent">

== <span class="summary">HP5 - The format for the contents of SHIPPING are vague</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* Seems like <b>shipping</b> could be abused quite a bit, resulting in a term that is fairly useless as time moves on.
* +1 agreed and I think SHIPPING belongs in hListing (not in hProduct) as it applies to a particular transaction/offering, and is not intrinsic to the product itself. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
</div>
</div>

<div class="vevent">
== <span class="summary">HP6 - P-V seems like a catch-all for hProduct</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* <b>p-v</b> seems like a catch-all, shoe-horn attempt at making the microformat infinitely scalable? Is this really useful?
** Response <span class="vcard">by <span class="fn">[[User:PaulLee|Paul Lee]]</span>, 2008-02-18</span>: IIUC, part of the reason why hproduct has been under discussion for quite awhile is b/c of the debate between p-v vs. more defined attributes. p-v is quite helpful b/c the attributes users care about change over time. Take cameras, for instance. Did anyone care about megapixels 10 years ago? etc.
* +1 I strongly oppose p-v as it is nothing more than a circumvention of the microformats [[process]] and 80/20 [[principle]] of formalizing only common properties. [[microformats]] are NOT designed to be infinitely extensible. p-v is simply another source of Tower of Babel problems. When attributes change over time, then the microformat can be iterated/extended to include them, *when* publishing behavior on the web for the *data* of such attributes exceeds the required 80/20 usage per microformats process. That being said, if you really must include arbitrary property-value data, there is already a microformat for that: [[xoxo]]. Modularly include a [[xoxo]] child and that way the extension is contained in a specific structure that can be ignored by implementations. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
</div>
</div>

<div class="vevent">

== <span class="summary">HP7 - Lots of vocabulary terms, does the data really back this up?</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* There seem to be a great deal of vocab terms and the terms seem to be fairly loosely defined... are they all justified? Is there a file that we can analyze (like via microformalyze)?
** Response <span class="vcard">by <span class="fn">[[User:PaulLee|Paul Lee]]</span>, 2008-02-18</span>:The examples aren't necessarily an accurate reflection of how frequently attributes/data is used by retailers. In practice, model/mpn is used much more frequently than dimensions, both for retailer websites as well as retailer submissions to search and shopping engines. Defer to those with more experience/other data on version.
* +1. If you cannot justify a property, or are unsure about including it, or don't think it is necessarily an accurate reflection of how frequently the data is used, then leave it out per microformats [[principles]]. A "version" property was added to [[hReview]] for largely theoretical concerns, but has never been needed/used. So in practice (per experience), leave out "version". [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-03-03</span>: I agree on both fronts here, I was surprised that model wasn't more prevalent in the research data, as it seems like an attribute that appears on nearly every product. Since "model" is often used as a type of identifier, it should be moved under the identifier attribute. "Version" will be taken out.
</div>
</div>

<div class="vevent hentry">
== <span class="entry-title summary">HP8 - No clear way of including a valid hReview that refers back to the hProduct as its item</span> ==
* {{OpenIssue}} <span class="entry-summary author vcard"><span class="dtstart published">2010-03-05</span> raised by <span class="fn">[[User:GeorgeBrock|GeorgeBrock]]</span></span>
<div class="description entry-content discussion issues">
* An hProduct can include one or more hReviews. Each hReview requires an item, which should be the hProduct. The [[include-pattern]] prohibits references to an ancestor. Therefore it is not clear how to include a valid hReview in an hProduct.
** Suggested by [[User:Tantek|Tantek]] on [http://krijnhoetmer.nl/irc-logs/microformats/20100305#l-132 IRC]: The item-url property from [[item-license]] could be used to refer to the review's item without including it.
*** This suggestion "seems to introduce extra markup that's likely to be extraneous from an end-user point-of-view, and thus set to <code>display:none</code> by authors." — [[User:TobyInk|Toby Inkster]] on the [http://microformats.org/discuss/mail/microformats-discuss/2010-April/013242.html mailing list]
** The review property could be removed altogether, and instead multiple product reviews could be marked up using a more generic container mechanism (see [[container-brainstorming]]). This would give a us consistent method of marking up multiple hReviews that apply to the same item, instead of a special case that only applied to hProduct. — [[User:GeorgeBrock|GeorgeBrock]] 13:35, 17 April 2010 (UTC)
</div>
</div>

== Resolved Issues ==
<div class="vevent">
<div class="vevent">
== <span class="summary">HP1 - hProduct vs hListing regarding "price" / "quantity" / "shipping" fields</span> ==
* {{ResolvedIssue}} <span class="vcard"><span class="dtstart">2009-04-24</span> raised by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
<div class="description">
* "quantity" and "shipping" have been removed from hproduct and transitioned to a new [[hlisting]] proposal. "price" has been retained, with the caveat that if hproduct is being used alone (eg., a non-commerce site who provides product information), without combining it with a microformat like [[hlisting]], it is assumed that the price attribute represents the suggested manufacturers retail price. All transactional details (including transactional price) would be deferred to [[hlisting]].
</div>
</div>

<div class="vevent">
== <span class="summary">HP2 - FN should be used instead of N for product titles</span> ==
* {{ResolvedIssue}} <span class="vcard"><span class="dtstart">2009-04-24</span> raised by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
<div class="description">
* changed in draft spec 0.2
</div>
</div>

<div class="vevent">
== <span class="summary">HP3 - BUY duplicates functionality of PAYMENT from hAudio</span> ==
* {{ResolvedIssue}} <span class="vcard"><span class="dtstart">2009-04-24</span> raised by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
<div class="description">
* buy removed in draft spec 0.2
</div>
</div>

<div class="vevent">
== <span class="summary">HP5 - The format for the contents of SHIPPING are vague</span> ==
* {{ResolvedIssue}} <span class="vcard"><span class="dtstart">2009-04-24</span> raised by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
<div class="description">
* shipping removed in draft spec 0.2
</div>
</div>

<div class="vevent">
== <span class="summary">HP6 - P-V seems like a catch-all for hProduct</span> ==
* {{ResolvedIssue}} <span class="vcard"><span class="dtstart">2009-04-24</span> raised by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
<div class="description">
* p-v has been removed in draft spec 0.3 in favor of [[xoxo]]
</div>
</div>

<div class="vevent">
== <span class="summary">HP7 - Lots of vocabulary terms, does the data really back this up?</span> ==
* {{ResolvedIssue}} <span class="vcard"><span class="dtstart">2009-04-24</span> raised by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
<div class="description">
* many attributes have been removed in draft specs 0.2 and 0.3. We believe the current number of attributes accurately represents a product object while providing adequate opportunity to be combined with other microformats for better overall semantic solutions.
</div>
</div>

== Closed Issues ==

== Template ==
{{issues-format}}

hproduct-issues

2010-04-17T13:35:53Z

GeorgeBrock: /* HP8 - No clear way of including a valid hReview that refers back to the hProduct as its item */ Review property could be removed

__TOC__

== HP1 - hProduct vs hListing regarding "price" / "quantity" / "shipping" fields ==

<div class="vevent">
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-12-17</span> raised by <span class="fn">NicolasLeroy</span></span>
<div class="description">
*# In the "[[hproduct#Out_of_Scope|out of scope]]" section, it is explained: _"This microformat does not intend to replicate any of the content proposed within hListing and would defer all money/transactional matters to that microformat"_
*# However, in the hProduct schema, we have the following fields:
*#* "price. optional. floating point number. can be further refined by type (msrp, regular, sale, clearance)" => if the price is the retailer price, then it should be delegated to hListing. We could imagine it represents the "manufacturer" price (which could be different from the retailer price) ; in this case, it should clearly be explained in the schema definition.
*#* I would say there is also ambiguity between the responsibilities of hProduct vs hListing for the following fields: quantity / shipping
*#** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-02-16</span>: I believe everyone agrees that we would borrow price from hListing for hProduct spec. I will explain the concept further in the schema.
*#** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-02-16</span>: I don't follow the quantity/ shipping issue. I don't see either of these on hListing, unless the concepts are somehow embedded in other attributes. Can you elaborate on what the ambiguity is? ([[User:PaulLee|Paul Lee]]: If there's no objection here, may I suggest updating the price reference and keeping quantity and shipping as is?])
*#* +1 I agree with NicholasLeroy, anything price or transaction related should be left out of hProduct 0.1, and instead develop recipes / mark-up examples showing use of hListing with hProduct. We need to strongly resist and fight the tendency to include "just one more field" to individual formats and instead push to use formats as building blocks. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
*#** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2009-03-03</span>: If price should be left to hListing, should hAudio be modified not to include "price"?
*#* I am going to add price back into the hProduct spec. Price is an attribute of a product. We should be able to use microformats either standalone or as building blocks in combination with other formats. On price I'm thinking specifically of product manufacturer sites who may not be commerce enabled and are listing their products for informational purposes. In this case, they would not be using hListing, as there would be no transaction taking place. Leaving the price attribute out would ignore a major product attribute (in 99% of product sites, per hproduct examples analysis).
</div>
</div>

<div class="vevent">

== <span class="summary">HP2 - FN should be used instead of N for product title</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* Why is <b>n</b> used instead of <b>fn</b> for the title of the product? hCard and hAudio both use fn for the formatted name of the product. <b>n</b> is usually an optimization.
* +1 hProduct should use "fn" for the name of the product. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-03-03</span>: "n" will be changed to "fn" in the next version of the schema
* "fn" is hardly semantic, even though commonly deployed - surely "formatted-name" is truer to the principles of "humans-first, machines second" --[[User:Wowitim|Wowitim]] 12:59, 28 March 2009 (UTC)
</div>

<div class="vevent">

== <span class="summary">HP3 - BUY duplicates functionality of PAYMENT from hAudio</span> ==
* {{OpenIssue}} <span class="vcard">BUY duplicates functionality of PAYMENT from hAudio<span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* <b>buy</b> is duplicating the functionality of <b>payment</b> from hAudio.
** Response <span class="vcard">by <span class="fn">[[User:PaulLee|Paul Lee]]</span>, 2008-02-18</span>: From the payment page: "RelPayment is a microformat for making exchanges of support (be it financial or otherwise) possible. By adding rel="payment" to a hyperlink a page indicates that the destination of that hyperlink provides a way to show or give support for the current page. For example to give financial support to the owner of the current page. One of the goals with this microformat is to give content aggregators such as RSS readers a way to extract these support links and give them special attention (such as displaying a standard button along with the content)." First, this seems like a simple exercise for blogs, etc.; but the transaction process for shopping sites is typically considerably more complex. Usually, the actual payment URI is toward the end of the cart checkout process, the entry to which "buy" is intended to direct to the beginning of. Second, there is the potential for confusion when using payment, since "payment" in the shopping space often refers to payment methods, e.g., credit card, check, etc.
* +1 but in a different way. BUY/PAYMENT should both be out of scope for hProduct, and only be in hListing per issue HP1 above. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
*#* Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2009-03-03</span>: Should these be in scope for hAudio then?
</div>
</div>

<div class="vevent">

== <span class="summary">HP4 - Are all of the formats for PRICE in hProduct allowed</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* The way that <b>price</b> is used is iffy - do we allow anything but currency/amount in the compound statement?
* +1 PRICE should not be in hProduct per issue HP1. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
*#* Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2009-03-03</span>: Should other microformats (thinking hAudio) be modified not to include "price"?
</div>
</div>

<div class="vevent">

== <span class="summary">HP5 - The format for the contents of SHIPPING are vague</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* Seems like <b>shipping</b> could be abused quite a bit, resulting in a term that is fairly useless as time moves on.
* +1 agreed and I think SHIPPING belongs in hListing (not in hProduct) as it applies to a particular transaction/offering, and is not intrinsic to the product itself. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
</div>
</div>

<div class="vevent">
== <span class="summary">HP6 - P-V seems like a catch-all for hProduct</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* <b>p-v</b> seems like a catch-all, shoe-horn attempt at making the microformat infinitely scalable? Is this really useful?
** Response <span class="vcard">by <span class="fn">[[User:PaulLee|Paul Lee]]</span>, 2008-02-18</span>: IIUC, part of the reason why hproduct has been under discussion for quite awhile is b/c of the debate between p-v vs. more defined attributes. p-v is quite helpful b/c the attributes users care about change over time. Take cameras, for instance. Did anyone care about megapixels 10 years ago? etc.
* +1 I strongly oppose p-v as it is nothing more than a circumvention of the microformats [[process]] and 80/20 [[principle]] of formalizing only common properties. [[microformats]] are NOT designed to be infinitely extensible. p-v is simply another source of Tower of Babel problems. When attributes change over time, then the microformat can be iterated/extended to include them, *when* publishing behavior on the web for the *data* of such attributes exceeds the required 80/20 usage per microformats process. That being said, if you really must include arbitrary property-value data, there is already a microformat for that: [[xoxo]]. Modularly include a [[xoxo]] child and that way the extension is contained in a specific structure that can be ignored by implementations. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
</div>
</div>

<div class="vevent">

== <span class="summary">HP7 - Lots of vocabulary terms, does the data really back this up?</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* There seem to be a great deal of vocab terms and the terms seem to be fairly loosely defined... are they all justified? Is there a file that we can analyze (like via microformalyze)?
** Response <span class="vcard">by <span class="fn">[[User:PaulLee|Paul Lee]]</span>, 2008-02-18</span>:The examples aren't necessarily an accurate reflection of how frequently attributes/data is used by retailers. In practice, model/mpn is used much more frequently than dimensions, both for retailer websites as well as retailer submissions to search and shopping engines. Defer to those with more experience/other data on version.
* +1. If you cannot justify a property, or are unsure about including it, or don't think it is necessarily an accurate reflection of how frequently the data is used, then leave it out per microformats [[principles]]. A "version" property was added to [[hReview]] for largely theoretical concerns, but has never been needed/used. So in practice (per experience), leave out "version". [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-03-03</span>: I agree on both fronts here, I was surprised that model wasn't more prevalent in the research data, as it seems like an attribute that appears on nearly every product. Since "model" is often used as a type of identifier, it should be moved under the identifier attribute. "Version" will be taken out.
</div>
</div>

<div class="vevent hentry">
== <span class="entry-title summary">HP8 - No clear way of including a valid hReview that refers back to the hProduct as its item</span> ==
* {{OpenIssue}} <span class="entry-summary author vcard"><span class="dtstart published">2010-03-05</span> raised by <span class="fn">[[User:GeorgeBrock|GeorgeBrock]]</span></span>
<div class="description entry-content discussion issues">
* An hProduct can include one or more hReviews. Each hReview requires an item, which should be the hProduct. The [[include-pattern]] prohibits references to an ancestor. Therefore it is not clear how to include a valid hReview in an hProduct.
** Suggested by [[User:Tantek|Tantek]] on [http://krijnhoetmer.nl/irc-logs/microformats/20100305#l-132 IRC]: The item-url property from [[item-license]] could be used to refer to the review's item without including it.
** The review property could be removed altogether, and instead multiple product reviews could be marked up using a more generic container mechanism (see [[container-brainstorming]]). This would give a us consistent method of marking up multiple hReviews that apply to the same item, instead of a special case that only applied to hProduct. — [[User:GeorgeBrock|GeorgeBrock]] 13:35, 17 April 2010 (UTC)
</div>
</div>

== Resolved Issues ==
<div class="vevent">
<div class="vevent">
== <span class="summary">HP1 - hProduct vs hListing regarding "price" / "quantity" / "shipping" fields</span> ==
* {{ResolvedIssue}} <span class="vcard"><span class="dtstart">2009-04-24</span> raised by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
<div class="description">
* "quantity" and "shipping" have been removed from hproduct and transitioned to a new [[hlisting]] proposal. "price" has been retained, with the caveat that if hproduct is being used alone (eg., a non-commerce site who provides product information), without combining it with a microformat like [[hlisting]], it is assumed that the price attribute represents the suggested manufacturers retail price. All transactional details (including transactional price) would be deferred to [[hlisting]].
</div>
</div>

<div class="vevent">
== <span class="summary">HP2 - FN should be used instead of N for product titles</span> ==
* {{ResolvedIssue}} <span class="vcard"><span class="dtstart">2009-04-24</span> raised by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
<div class="description">
* changed in draft spec 0.2
</div>
</div>

<div class="vevent">
== <span class="summary">HP3 - BUY duplicates functionality of PAYMENT from hAudio</span> ==
* {{ResolvedIssue}} <span class="vcard"><span class="dtstart">2009-04-24</span> raised by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
<div class="description">
* buy removed in draft spec 0.2
</div>
</div>

<div class="vevent">
== <span class="summary">HP5 - The format for the contents of SHIPPING are vague</span> ==
* {{ResolvedIssue}} <span class="vcard"><span class="dtstart">2009-04-24</span> raised by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
<div class="description">
* shipping removed in draft spec 0.2
</div>
</div>

<div class="vevent">
== <span class="summary">HP6 - P-V seems like a catch-all for hProduct</span> ==
* {{ResolvedIssue}} <span class="vcard"><span class="dtstart">2009-04-24</span> raised by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
<div class="description">
* p-v has been removed in draft spec 0.3 in favor of [[xoxo]]
</div>
</div>

<div class="vevent">
== <span class="summary">HP7 - Lots of vocabulary terms, does the data really back this up?</span> ==
* {{ResolvedIssue}} <span class="vcard"><span class="dtstart">2009-04-24</span> raised by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
<div class="description">
* many attributes have been removed in draft specs 0.2 and 0.3. We believe the current number of attributes accurately represents a product object while providing adequate opportunity to be combined with other microformats for better overall semantic solutions.
</div>
</div>

== Closed Issues ==

== Template ==
{{issues-format}}

container-brainstorming

2010-04-17T13:07:08Z

GeorgeBrock: /* Markup proposals */ Proposed using prefixes to indicate shared properties

<entry-title>Containers</entry-title>

This page exists to brainstorm around the concept of ‘containers’ in microformats.

==What's a Container?==

A ‘container’ is a root element that contains multiple microformat items within it. It groups those items together, but could also be used to provide additional or shared semantics between those items.

Some microformats already define containers: <code>vcalendar</code> [[hCalendar]] is a container for events, the <code>hfeed</code> container in [[hAtom]] contains entries, [[hAudio]] has a concept whereby <code>haudio</code> concepts may be nested, and an [[hCard]] <code>vcard</code> may be a container for <code>agent vcard</code>s.

==Why is this being explored?==
There are a number of use cases for making better use of these container semantics, both in microformats like hCalendar that already have containers, and [[hReview]], where no current container concept exists.

== examples ==
As always it helps to start with examples of markup from actual websites that are already publishing container semantics. If this section gets too large, perhaps we can move it to [[container-examples]].

=== container of reviews ===
The following website(s) contain a list of reviews which could/would benefit from a way of marking up not just the reviews as hReviews, but also the set of them as reviewing the same item.
==== SustainLane ====
http://www.sustainlane.com/ has pages that show multiple reviews of the same item. e.g.

http://www.sustainlane.com/reviews/aziza/TVLWN4ZKQLKTOIKFLWKBWFQ17DN8

==== Yelp ====
http://yelp.com/ has pages that show multiple reviews of the same item. e.g.

http://www.yelp.com/biz/coffee-to-the-people-san-francisco

==Use cases==
Here are some example use cases for sharing properties from a container into multiple child microformats:

===Multiple reviews of the same item===
As demonstrated by the above real world examples, many sites publish a page for a single item, listing multiple reviews of that item (e.g. Amazon, Kelkoo, Yelp, Yahoo! Location etc.). The item appears once at the top of the page. The reviews follow. [[hReview]]'s current requirement is that the <code>item</code> be referenced from every review using the include-pattern. This requires duplicating some amount of content (most logically, the name of the reviewed item). This has raised objections by implementers, and usually imposes a CSS-dependency to hide the repeated content.

===Reviews and review aggregate of the same item===
Same as above, a single page includes a few reviews and a single reviews aggregate for a single business. In some implementations (yelp) the aggregate result number is contained inside the <code>hcard</code>. Reviews that use the include pattern to include the <code>hcard</code> of the business, are also including a second <code>rating</code> microformat, resulting in two ratings for the same <code>hreview</code>. Putting the reviews and review aggregates as siblings inside the same container, can solve this problem.

===Shared hCalendar Properties===
Yahoo! TV Listings marks up television programme listings using hCalendar. The <code>location</code> field of the event is the channel on which the show is broadcast: e.g. <code><span class='location'>BBC 1</span></code>.

* ‘BBC 1’ is the heading for that channels listing page. The information is published ''once'' in the page.
* Each scheduled programme on the page is a <code>vevent</code>
* Using current hCalendar semantics, the <code>location</code> must be included in every <code>vevent</code>

With the ‘BBC 1’ content at the top of the page, not part of the programme content, the content either has to be repeated and hidden in the presentation layer, or current microformats constructs such as the [[include-pattern]] need to be used to invisibly reference the original mention of ‘BBC 1’.

Repeating content is unacceptable, and the include-pattern is a messy, hacky mark-up pattern. Embracing the concept of the container would match the publishing pattern of the site, without repeating content or including invisible pointers.

'''ideally this markup proposal would be moved to the "markup proposals" section below, separate from the "Use Cases" section, so that multiple varying proposals could be grouped together to compare, rather than intermingling them with the list of use cases.'''

.e.g.

<source lang=html4strict>
<div class='vcalendar'>
<h1 class='location'>BBC 2</h1>

<ul>
<li class='vevent'>
<h2 class='summary'>Gardener's World</h2>
<p class='dtstart'><span class='value-title' title='2009-06-05T20:30:00+0100'> </span> 8:30pm</p>
</li>
<li class='vevent'>
<h2 class='summary'>Have I Got News For You</h2>
<p class='dtstart'><span class='value-title' title='2009-06-05T21:00:00+0100'> </span> 9:00pm</p>
</li>
</ul>
</div>
</source>

Here, the <code>location</code> is promoted to being a property of the <code>vcalendar</code>, and is the default location for all the contained events.

This could also apply to the <code>organizer</code>, <code>attendees</code>, and others. With further explanation and [[value-class-pattern|date-time separation]], you could event declare the day of the week the the <code>vcalendar</code> and the time-of-day in the <code>vevent</code>. The basic principal is illustrated, though.

Uses for this pattern:
* Broadcast listings for a single channel/station
* Concert listings at a single venue
* Concert listings for a single act (e.g. ‘Doves in Concert’ is the event <code>summary</code> for multiple events at different <code>locations</code>)

This of course, extends the use of an existing container.

===hAtom entries published together===

[[hAtom]] already has parsing rules to look for an <code>address</code> in the page for a shared author, a container-like concept. It already has an <code>hfeed</code> parent node, and this could be used to share other features of the format. For example, a photo album (for which explicit creation datetimes are either unavailable or irrelevant) may be published just as having been taken on a single day. As such, the date will appear once at the head of the page, and each photograph (<code>hentry</code>) will not contain a unique <code>updated</code> date.

==Shared Aspects of Containers==
If containers become a more strongly adopted concept in microformats, they should behave consistently across formats (hence documenting these two examples here, rather than just as separate issues for both hReview and hCalendar).

Things that should be consistent and predictable:

* Inheriting an property into a microformat item within the container
* Contained items ''overriding'' one or more inherited property
* Alternatively, siblings cannot override properties of other siblings. Example: hcard of reviewer inside hreview cannot override any property of the item hcard (a sibling of the hreview). When a sibling specifies a property of another sibling, it is ignored (Example: hreview contains availability, availability is ignored).

== markup proposals ==

===Existing container elements===

* <code>vcalendar</code> in [[hCalendar]]
* <code>hfeed</code> in [[hAtom]]
* <code>hresume</code> in [[hResume]] — hResume contains an hCard for the owner, which could indicate default properties (<code>fn</code>) for <code>experience</code> business cards.
* <code>hreview-aggregate</code> in [[hReview-aggregate]] can contain other hReviews, as such could be used as a container to share the <code>item</code> with each component <code>hreview</code>.
* <code>hproduct</code> in [[hProduct]] can contain one or more reviews ([[hReview]] or [[hReview-aggregate]]), this should allow the reviews to all use the containing <code>hproduct</code> as their <code>item</code>.

=== hreview-set ===
One solution to the problem of multiple reviews of the same item could be to wrap each <code>hReview</code> in a container (hypothetically, <code>hreview-set</code>. The <code>item</code> is a child of the set, and is inherited by each <code>hreview</code> contained within.

=== hCard as a container ===
<code>vcard</code> block can contain associated information like reviews and aggregates. <code>hreview</code>s inside an <code>vcard</code> do not need to specify item.
This also extends to other microformats that may contain reviews, such as hproduct.
Another option is that a vcard that contains other microformat must also specify additional tag, such as <code>hcontainer</code>, <code>item</code> or similar.
====Problems====
* <code>hreview</code> already contains child hCard. Since it can inherit aspects of hcard from its parent, there will be duplicate values. This makes the job of the parser more complex, and requires additional rules, such as "an hreview inside an hcard ignores all hCard properties that are not contained in it", etc.
* Include pattern from hreview to the container hCard can cause circular references, requiring more rules in the microformat specification and more rules for the parsers to follow.
* Generally it seems to me (Elli) that this pattern will require many parsing rules. Things are not "atomic". It also forces a rigid structure on the xhtml, which may defeat the purpose of containers.
<source lang=html4strict>
<div class="vcard">
<h1 class="fn">name</h1>
<div class="hreview-aggregate">
<div class="rating">
<span class="average">4.4</span>
</div>
<span class="count">1313</span> reviews
</div>
<div class="hreview"></div>
<div class="hreview"></div>
</div>
</source>

=== hcontainer===
A container microformat. Inside a container, a microformat that requires another microformat as a child (such as hreview requiring an item), can resolve this association by sibling relationship (as opposed to parent child relationship).
When a container includes <code>hreview</code> or <code>hreview-aggregate</code>, it also requires a child <code>item</code>. This is similar to <code>hreview-set</code> proposal, with specific handling of aggregates.

In the example below, the item is hcard, similar examples can be written for products and events.
<source lang=html4strict>

<div class="hcontainer">
<h1 class="item vcard fn">name</h1>
<div class="hreview-aggregate">
<div class="rating">
<span class="average">4.4</span>
</div>
<span class="count">1313</span> reviews
</div>
<div class="hreview">...</div>
<div class="hreview">...</div>
</div>

<div class="hcontainer">
<div class="hreview-aggregate">
<h1 class="item vcard fn">name</h1>
<div class="rating">
<span class="average">4.4</span>
</div>
<span class="count">1313</span> reviews
</div>
<div class="hreview">...</div>
<div class="hreview">...</div>
</div>
</source>

<div class='discussion'>
* Unconvinced by the generics here. Especially since a lot of microformats already have parent nodes (<code>vcalendar</code>, <code>hfeed</code>). Doesn't self-document. —[[User:BenWard|BenWard]] 06:27, 30 July 2009 (UTC)
* In this case, <code>hreview-aggregate</code> could itself have container behaviour; the <code>hreview-aggregate</code> is a container for other <code>hreveiw</code> items, and the <code>item</code> is shared. —[[User:BenWard|BenWard]] 06:27, 30 July 2009 (UTC)
</div>

=== item as a container ===
The <code>item</code> microformat is currently used inside <code>hreview</code>s. Use this existing micformat as a container as well. This makes the specification slightly more complicated, since <code>item</code> will be allowed as a parent of <code>hreview</code> as well as a child. This is basically the same proposal as above, but using the name <code>item</code> for the container, instead of a dedicated name.
====Problems====

* This defines two microformats that can be parent child of each other in both directions (<code>hreview</code> and <code>item</code>).
<source lang=html4strict>
<div class="item">
<h1 class="vcard fn">name</h1>
<div class="hreview-aggregate">
<div class="rating">
<span class="average">4.4</span>
</div>
<span class="count">1313</span> reviews
</div>
<div class="hreview"></div>
<div class="hreview"></div>
</div>
</source>

* I don't really see that <code>item</code> makes sense as a container here. An item is a singular thing, a collection is wrapping a collection of things. In hReview, or hListing, or anything you'd have <code>container</code> as a structural parent of <code>item</code>. Repurposing <code>item</code> seems very confusing. --[[User:BenWard|BenWard]] 06:21, 30 July 2009 (UTC)

=== hreview rating and hreview-aggregate rating use different names ===
Since the microformat <code>rating</code> is used for both, an <code>hreview</code> that includes an <code>hcard</code> which contains aggregates, effectively imports a second rating. This can be solved by having different names for hreview rating and hreview-aggregate rating. This is not really a container proposal, but it addresses issues of the hreview-aggregate which is currently a container for item.
====Problems====
* This may not be necessary for pages that can use a container microformat with minimal impact to the xhtml structure. Pages that cannot use container structure and use includes may still need a solution.
<source lang=html4strict>
<div class="vcard item" id="review_item">
<h1 class="fn">name</h1>

<span class="average-rating">5</span> stars
based on <span class="review-count">1313</span> reviews
<span class="type microformat_detail">business</span>
</div>
<div class="hreview">

<span class="rating">3</span> stars

<a class="item microformat_detail" href="#review_item">Aziza</a>
</div>
</source>

=== Prefixes to indicate shared properties ===

A generic <code>shared-</code> prefix could be used to indicate that certain properties should be applied to all component microformats within a container. For example, if a <code>vcard</code> did not have any descendant elements with the class <code>fn</code> it would take its formatted name from a sibling element with the class <code>shared-fn</code>.

Sharing a location between multiple <code>vevent</code>s within a <code>vcalendar</code>:

<source lang=html4strict>
<div class="vcalendar">
<h2 class="shared-location">The Music Venue</h2>
<p class="summary">This summary does not have the shared- prefix, so it is ignored by the events.</p>
<div class="vevent"> ... </div>
<div class="vevent"> ... </div>
</div>
</source>

If the container was itself a microformat then the prefix would be used to determine which properties belonged to the container, which belonged to the component microformats and which were shared by both.

For example, an [[hReview-aggregate]] may contain many [[hReview]]s. Within the root <code>hreview-aggregate</code> element:
* An element with class <code>item</code> would provide the item for the <code>hreview-aggregate</code>.
* An element with class <code>shared-item</code> would provide the item for the individual <code>hreview</code>s.
* An element with both classes (<code>item shared-item</code>) would provide the item for the <code>hreview-aggregate</code> and the individual <code>hreview</code>s.

<source lang=html4strict>
<div class="hreview-aggregate">
<h2 class="item shared-item vcard"><span class="fn org">A Restaurant</span></h2>
<div class="hreview"> ... </div>
<div class="hreview"> ... </div>
</div>
</source>

== see also ==
* [[hReview]]
* [[hCalendar]]
* [[hListing]]

container-brainstorming

2010-04-17T12:25:37Z

GeorgeBrock: /* Existing container elements */ Add hProduct contains hReviews example

<entry-title>Containers</entry-title>

This page exists to brainstorm around the concept of ‘containers’ in microformats.

==What's a Container?==

A ‘container’ is a root element that contains multiple microformat items within it. It groups those items together, but could also be used to provide additional or shared semantics between those items.

Some microformats already define containers: <code>vcalendar</code> [[hCalendar]] is a container for events, the <code>hfeed</code> container in [[hAtom]] contains entries, [[hAudio]] has a concept whereby <code>haudio</code> concepts may be nested, and an [[hCard]] <code>vcard</code> may be a container for <code>agent vcard</code>s.

==Why is this being explored?==
There are a number of use cases for making better use of these container semantics, both in microformats like hCalendar that already have containers, and [[hReview]], where no current container concept exists.

== examples ==
As always it helps to start with examples of markup from actual websites that are already publishing container semantics. If this section gets too large, perhaps we can move it to [[container-examples]].

=== container of reviews ===
The following website(s) contain a list of reviews which could/would benefit from a way of marking up not just the reviews as hReviews, but also the set of them as reviewing the same item.
==== SustainLane ====
http://www.sustainlane.com/ has pages that show multiple reviews of the same item. e.g.

http://www.sustainlane.com/reviews/aziza/TVLWN4ZKQLKTOIKFLWKBWFQ17DN8

==== Yelp ====
http://yelp.com/ has pages that show multiple reviews of the same item. e.g.

http://www.yelp.com/biz/coffee-to-the-people-san-francisco

==Use cases==
Here are some example use cases for sharing properties from a container into multiple child microformats:

===Multiple reviews of the same item===
As demonstrated by the above real world examples, many sites publish a page for a single item, listing multiple reviews of that item (e.g. Amazon, Kelkoo, Yelp, Yahoo! Location etc.). The item appears once at the top of the page. The reviews follow. [[hReview]]'s current requirement is that the <code>item</code> be referenced from every review using the include-pattern. This requires duplicating some amount of content (most logically, the name of the reviewed item). This has raised objections by implementers, and usually imposes a CSS-dependency to hide the repeated content.

===Reviews and review aggregate of the same item===
Same as above, a single page includes a few reviews and a single reviews aggregate for a single business. In some implementations (yelp) the aggregate result number is contained inside the <code>hcard</code>. Reviews that use the include pattern to include the <code>hcard</code> of the business, are also including a second <code>rating</code> microformat, resulting in two ratings for the same <code>hreview</code>. Putting the reviews and review aggregates as siblings inside the same container, can solve this problem.

===Shared hCalendar Properties===
Yahoo! TV Listings marks up television programme listings using hCalendar. The <code>location</code> field of the event is the channel on which the show is broadcast: e.g. <code><span class='location'>BBC 1</span></code>.

* ‘BBC 1’ is the heading for that channels listing page. The information is published ''once'' in the page.
* Each scheduled programme on the page is a <code>vevent</code>
* Using current hCalendar semantics, the <code>location</code> must be included in every <code>vevent</code>

With the ‘BBC 1’ content at the top of the page, not part of the programme content, the content either has to be repeated and hidden in the presentation layer, or current microformats constructs such as the [[include-pattern]] need to be used to invisibly reference the original mention of ‘BBC 1’.

Repeating content is unacceptable, and the include-pattern is a messy, hacky mark-up pattern. Embracing the concept of the container would match the publishing pattern of the site, without repeating content or including invisible pointers.

'''ideally this markup proposal would be moved to the "markup proposals" section below, separate from the "Use Cases" section, so that multiple varying proposals could be grouped together to compare, rather than intermingling them with the list of use cases.'''

.e.g.

<source lang=html4strict>
<div class='vcalendar'>
<h1 class='location'>BBC 2</h1>

<ul>
<li class='vevent'>
<h2 class='summary'>Gardener's World</h2>
<p class='dtstart'><span class='value-title' title='2009-06-05T20:30:00+0100'> </span> 8:30pm</p>
</li>
<li class='vevent'>
<h2 class='summary'>Have I Got News For You</h2>
<p class='dtstart'><span class='value-title' title='2009-06-05T21:00:00+0100'> </span> 9:00pm</p>
</li>
</ul>
</div>
</source>

Here, the <code>location</code> is promoted to being a property of the <code>vcalendar</code>, and is the default location for all the contained events.

This could also apply to the <code>organizer</code>, <code>attendees</code>, and others. With further explanation and [[value-class-pattern|date-time separation]], you could event declare the day of the week the the <code>vcalendar</code> and the time-of-day in the <code>vevent</code>. The basic principal is illustrated, though.

Uses for this pattern:
* Broadcast listings for a single channel/station
* Concert listings at a single venue
* Concert listings for a single act (e.g. ‘Doves in Concert’ is the event <code>summary</code> for multiple events at different <code>locations</code>)

This of course, extends the use of an existing container.

===hAtom entries published together===

[[hAtom]] already has parsing rules to look for an <code>address</code> in the page for a shared author, a container-like concept. It already has an <code>hfeed</code> parent node, and this could be used to share other features of the format. For example, a photo album (for which explicit creation datetimes are either unavailable or irrelevant) may be published just as having been taken on a single day. As such, the date will appear once at the head of the page, and each photograph (<code>hentry</code>) will not contain a unique <code>updated</code> date.

==Shared Aspects of Containers==
If containers become a more strongly adopted concept in microformats, they should behave consistently across formats (hence documenting these two examples here, rather than just as separate issues for both hReview and hCalendar).

Things that should be consistent and predictable:

* Inheriting an property into a microformat item within the container
* Contained items ''overriding'' one or more inherited property
* Alternatively, siblings cannot override properties of other siblings. Example: hcard of reviewer inside hreview cannot override any property of the item hcard (a sibling of the hreview). When a sibling specifies a property of another sibling, it is ignored (Example: hreview contains availability, availability is ignored).

== markup proposals ==

===Existing container elements===

* <code>vcalendar</code> in [[hCalendar]]
* <code>hfeed</code> in [[hAtom]]
* <code>hresume</code> in [[hResume]] — hResume contains an hCard for the owner, which could indicate default properties (<code>fn</code>) for <code>experience</code> business cards.
* <code>hreview-aggregate</code> in [[hReview-aggregate]] can contain other hReviews, as such could be used as a container to share the <code>item</code> with each component <code>hreview</code>.
* <code>hproduct</code> in [[hProduct]] can contain one or more reviews ([[hReview]] or [[hReview-aggregate]]), this should allow the reviews to all use the containing <code>hproduct</code> as their <code>item</code>.

=== hreview-set ===
One solution to the problem of multiple reviews of the same item could be to wrap each <code>hReview</code> in a container (hypothetically, <code>hreview-set</code>. The <code>item</code> is a child of the set, and is inherited by each <code>hreview</code> contained within.

=== hCard as a container ===
<code>vcard</code> block can contain associated information like reviews and aggregates. <code>hreview</code>s inside an <code>vcard</code> do not need to specify item.
This also extends to other microformats that may contain reviews, such as hproduct.
Another option is that a vcard that contains other microformat must also specify additional tag, such as <code>hcontainer</code>, <code>item</code> or similar.
====Problems====
* <code>hreview</code> already contains child hCard. Since it can inherit aspects of hcard from its parent, there will be duplicate values. This makes the job of the parser more complex, and requires additional rules, such as "an hreview inside an hcard ignores all hCard properties that are not contained in it", etc.
* Include pattern from hreview to the container hCard can cause circular references, requiring more rules in the microformat specification and more rules for the parsers to follow.
* Generally it seems to me (Elli) that this pattern will require many parsing rules. Things are not "atomic". It also forces a rigid structure on the xhtml, which may defeat the purpose of containers.
<source lang=html4strict>
<div class="vcard">
<h1 class="fn">name</h1>
<div class="hreview-aggregate">
<div class="rating">
<span class="average">4.4</span>
</div>
<span class="count">1313</span> reviews
</div>
<div class="hreview"></div>
<div class="hreview"></div>
</div>
</source>

=== hcontainer===
A container microformat. Inside a container, a microformat that requires another microformat as a child (such as hreview requiring an item), can resolve this association by sibling relationship (as opposed to parent child relationship).
When a container includes <code>hreview</code> or <code>hreview-aggregate</code>, it also requires a child <code>item</code>. This is similar to <code>hreview-set</code> proposal, with specific handling of aggregates.

In the example below, the item is hcard, similar examples can be written for products and events.
<source lang=html4strict>

<div class="hcontainer">
<h1 class="item vcard fn">name</h1>
<div class="hreview-aggregate">
<div class="rating">
<span class="average">4.4</span>
</div>
<span class="count">1313</span> reviews
</div>
<div class="hreview">...</div>
<div class="hreview">...</div>
</div>

<div class="hcontainer">
<div class="hreview-aggregate">
<h1 class="item vcard fn">name</h1>
<div class="rating">
<span class="average">4.4</span>
</div>
<span class="count">1313</span> reviews
</div>
<div class="hreview">...</div>
<div class="hreview">...</div>
</div>
</source>

<div class='discussion'>
* Unconvinced by the generics here. Especially since a lot of microformats already have parent nodes (<code>vcalendar</code>, <code>hfeed</code>). Doesn't self-document. —[[User:BenWard|BenWard]] 06:27, 30 July 2009 (UTC)
* In this case, <code>hreview-aggregate</code> could itself have container behaviour; the <code>hreview-aggregate</code> is a container for other <code>hreveiw</code> items, and the <code>item</code> is shared. —[[User:BenWard|BenWard]] 06:27, 30 July 2009 (UTC)
</div>

=== item as a container ===
The <code>item</code> microformat is currently used inside <code>hreview</code>s. Use this existing micformat as a container as well. This makes the specification slightly more complicated, since <code>item</code> will be allowed as a parent of <code>hreview</code> as well as a child. This is basically the same proposal as above, but using the name <code>item</code> for the container, instead of a dedicated name.
====Problems====

* This defines two microformats that can be parent child of each other in both directions (<code>hreview</code> and <code>item</code>).
<source lang=html4strict>
<div class="item">
<h1 class="vcard fn">name</h1>
<div class="hreview-aggregate">
<div class="rating">
<span class="average">4.4</span>
</div>
<span class="count">1313</span> reviews
</div>
<div class="hreview"></div>
<div class="hreview"></div>
</div>
</source>

* I don't really see that <code>item</code> makes sense as a container here. An item is a singular thing, a collection is wrapping a collection of things. In hReview, or hListing, or anything you'd have <code>container</code> as a structural parent of <code>item</code>. Repurposing <code>item</code> seems very confusing. --[[User:BenWard|BenWard]] 06:21, 30 July 2009 (UTC)

=== hreview rating and hreview-aggregate rating use different names ===
Since the microformat <code>rating</code> is used for both, an <code>hreview</code> that includes an <code>hcard</code> which contains aggregates, effectively imports a second rating. This can be solved by having different names for hreview rating and hreview-aggregate rating. This is not really a container proposal, but it addresses issues of the hreview-aggregate which is currently a container for item.
====Problems====
* This may not be necessary for pages that can use a container microformat with minimal impact to the xhtml structure. Pages that cannot use container structure and use includes may still need a solution.
<source lang=html4strict>
<div class="vcard item" id="review_item">
<h1 class="fn">name</h1>

<span class="average-rating">5</span> stars
based on <span class="review-count">1313</span> reviews
<span class="type microformat_detail">business</span>
</div>
<div class="hreview">

<span class="rating">3</span> stars

<a class="item microformat_detail" href="#review_item">Aziza</a>
</div>
</source>

== see also ==
* [[hReview]]
* [[hCalendar]]
* [[hListing]]

hproduct-issues

2010-03-05T18:33:36Z

GeorgeBrock: /* HP8 - No clear way of including a valid hReview that refers back to the hProduct as its item */ Added suggested solution from IRC

__TOC__

== HP1 - hProduct vs hListing regarding "price" / "quantity" / "shipping" fields ==

<div class="vevent">
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-12-17</span> raised by <span class="fn">NicolasLeroy</span></span>
<div class="description">
*# In the "[[hproduct#Out_of_Scope|out of scope]]" section, it is explained: _"This microformat does not intend to replicate any of the content proposed within hListing and would defer all money/transactional matters to that microformat"_
*# However, in the hProduct schema, we have the following fields:
*#* "price. optional. floating point number. can be further refined by type (msrp, regular, sale, clearance)" => if the price is the retailer price, then it should be delegated to hListing. We could imagine it represents the "manufacturer" price (which could be different from the retailer price) ; in this case, it should clearly be explained in the schema definition.
*#* I would say there is also ambiguity between the responsibilities of hProduct vs hListing for the following fields: quantity / shipping
*#** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-02-16</span>: I believe everyone agrees that we would borrow price from hListing for hProduct spec. I will explain the concept further in the schema.
*#** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-02-16</span>: I don't follow the quantity/ shipping issue. I don't see either of these on hListing, unless the concepts are somehow embedded in other attributes. Can you elaborate on what the ambiguity is? ([[User:PaulLee|Paul Lee]]: If there's no objection here, may I suggest updating the price reference and keeping quantity and shipping as is?])
*#* +1 I agree with NicholasLeroy, anything price or transaction related should be left out of hProduct 0.1, and instead develop recipes / mark-up examples showing use of hListing with hProduct. We need to strongly resist and fight the tendency to include "just one more field" to individual formats and instead push to use formats as building blocks. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
*#** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2009-03-03</span>: If price should be left to hListing, should hAudio be modified not to include "price"?
*#* I am going to add price back into the hProduct spec. Price is an attribute of a product. We should be able to use microformats either standalone or as building blocks in combination with other formats. On price I'm thinking specifically of product manufacturer sites who may not be commerce enabled and are listing their products for informational purposes. In this case, they would not be using hListing, as there would be no transaction taking place. Leaving the price attribute out would ignore a major product attribute (in 99% of product sites, per hproduct examples analysis).
</div>
</div>

<div class="vevent">

== <span class="summary">HP2 - FN should be used instead of N for product title</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* Why is <b>n</b> used instead of <b>fn</b> for the title of the product? hCard and hAudio both use fn for the formatted name of the product. <b>n</b> is usually an optimization.
* +1 hProduct should use "fn" for the name of the product. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-03-03</span>: "n" will be changed to "fn" in the next version of the schema
* "fn" is hardly semantic, even though commonly deployed - surely "formatted-name" is truer to the principles of "humans-first, machines second" --[[User:Wowitim|Wowitim]] 12:59, 28 March 2009 (UTC)
</div>

<div class="vevent">

== <span class="summary">HP3 - BUY duplicates functionality of PAYMENT from hAudio</span> ==
* {{OpenIssue}} <span class="vcard">BUY duplicates functionality of PAYMENT from hAudio<span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* <b>buy</b> is duplicating the functionality of <b>payment</b> from hAudio.
** Response <span class="vcard">by <span class="fn">[[User:PaulLee|Paul Lee]]</span>, 2008-02-18</span>: From the payment page: "RelPayment is a microformat for making exchanges of support (be it financial or otherwise) possible. By adding rel="payment" to a hyperlink a page indicates that the destination of that hyperlink provides a way to show or give support for the current page. For example to give financial support to the owner of the current page. One of the goals with this microformat is to give content aggregators such as RSS readers a way to extract these support links and give them special attention (such as displaying a standard button along with the content)." First, this seems like a simple exercise for blogs, etc.; but the transaction process for shopping sites is typically considerably more complex. Usually, the actual payment URI is toward the end of the cart checkout process, the entry to which "buy" is intended to direct to the beginning of. Second, there is the potential for confusion when using payment, since "payment" in the shopping space often refers to payment methods, e.g., credit card, check, etc.
* +1 but in a different way. BUY/PAYMENT should both be out of scope for hProduct, and only be in hListing per issue HP1 above. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
*#* Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2009-03-03</span>: Should these be in scope for hAudio then?
</div>
</div>

<div class="vevent">

== <span class="summary">HP4 - Are all of the formats for PRICE in hProduct allowed</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* The way that <b>price</b> is used is iffy - do we allow anything but currency/amount in the compound statement?
* +1 PRICE should not be in hProduct per issue HP1. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
*#* Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2009-03-03</span>: Should other microformats (thinking hAudio) be modified not to include "price"?
</div>
</div>

<div class="vevent">

== <span class="summary">HP5 - The format for the contents of SHIPPING are vague</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* Seems like <b>shipping</b> could be abused quite a bit, resulting in a term that is fairly useless as time moves on.
* +1 agreed and I think SHIPPING belongs in hListing (not in hProduct) as it applies to a particular transaction/offering, and is not intrinsic to the product itself. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
</div>
</div>

<div class="vevent">
== <span class="summary">HP6 - P-V seems like a catch-all for hProduct</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* <b>p-v</b> seems like a catch-all, shoe-horn attempt at making the microformat infinitely scalable? Is this really useful?
** Response <span class="vcard">by <span class="fn">[[User:PaulLee|Paul Lee]]</span>, 2008-02-18</span>: IIUC, part of the reason why hproduct has been under discussion for quite awhile is b/c of the debate between p-v vs. more defined attributes. p-v is quite helpful b/c the attributes users care about change over time. Take cameras, for instance. Did anyone care about megapixels 10 years ago? etc.
* +1 I strongly oppose p-v as it is nothing more than a circumvention of the microformats [[process]] and 80/20 [[principle]] of formalizing only common properties. [[microformats]] are NOT designed to be infinitely extensible. p-v is simply another source of Tower of Babel problems. When attributes change over time, then the microformat can be iterated/extended to include them, *when* publishing behavior on the web for the *data* of such attributes exceeds the required 80/20 usage per microformats process. That being said, if you really must include arbitrary property-value data, there is already a microformat for that: [[xoxo]]. Modularly include a [[xoxo]] child and that way the extension is contained in a specific structure that can be ignored by implementations. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
</div>
</div>

<div class="vevent">

== <span class="summary">HP7 - Lots of vocabulary terms, does the data really back this up?</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* There seem to be a great deal of vocab terms and the terms seem to be fairly loosely defined... are they all justified? Is there a file that we can analyze (like via microformalyze)?
** Response <span class="vcard">by <span class="fn">[[User:PaulLee|Paul Lee]]</span>, 2008-02-18</span>:The examples aren't necessarily an accurate reflection of how frequently attributes/data is used by retailers. In practice, model/mpn is used much more frequently than dimensions, both for retailer websites as well as retailer submissions to search and shopping engines. Defer to those with more experience/other data on version.
* +1. If you cannot justify a property, or are unsure about including it, or don't think it is necessarily an accurate reflection of how frequently the data is used, then leave it out per microformats [[principles]]. A "version" property was added to [[hReview]] for largely theoretical concerns, but has never been needed/used. So in practice (per experience), leave out "version". [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-03-03</span>: I agree on both fronts here, I was surprised that model wasn't more prevalent in the research data, as it seems like an attribute that appears on nearly every product. Since "model" is often used as a type of identifier, it should be moved under the identifier attribute. "Version" will be taken out.
</div>
</div>

<div class="vevent hentry">
== <span class="entry-title summary">HP8 - No clear way of including a valid hReview that refers back to the hProduct as its item</span> ==
* {{OpenIssue}} <span class="entry-summary author vcard"><span class="dtstart published">2010-03-05</span> raised by <span class="fn">[[User:GeorgeBrock|GeorgeBrock]]</span></span>
<div class="description entry-content discussion issues">
* An hProduct can include one or more hReviews. Each hReview requires an item, which should be the hProduct. The [[include-pattern]] prohibits references to an ancestor. Therefore it is not clear how to include a valid hReview in an hProduct.
** Suggested by [[User:Tantek|Tantek]] on [http://krijnhoetmer.nl/irc-logs/microformats/20100305#l-132 IRC]: The item-url property from [[item-license]] could be used to refer to the review's item without including it.
</div>
</div>

== Resolved Issues ==
<div class="vevent">
<div class="vevent">
== <span class="summary">HP1 - hProduct vs hListing regarding "price" / "quantity" / "shipping" fields</span> ==
* {{ResolvedIssue}} <span class="vcard"><span class="dtstart">2009-04-24</span> raised by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
<div class="description">
* "quantity" and "shipping" have been removed from hproduct and transitioned to a new [[hlisting]] proposal. "price" has been retained, with the caveat that if hproduct is being used alone (eg., a non-commerce site who provides product information), without combining it with a microformat like [[hlisting]], it is assumed that the price attribute represents the suggested manufacturers retail price. All transactional details (including transactional price) would be deferred to [[hlisting]].
</div>
</div>

<div class="vevent">
== <span class="summary">HP2 - FN should be used instead of N for product titles</span> ==
* {{ResolvedIssue}} <span class="vcard"><span class="dtstart">2009-04-24</span> raised by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
<div class="description">
* changed in draft spec 0.2
</div>
</div>

<div class="vevent">
== <span class="summary">HP3 - BUY duplicates functionality of PAYMENT from hAudio</span> ==
* {{ResolvedIssue}} <span class="vcard"><span class="dtstart">2009-04-24</span> raised by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
<div class="description">
* buy removed in draft spec 0.2
</div>
</div>

<div class="vevent">
== <span class="summary">HP5 - The format for the contents of SHIPPING are vague</span> ==
* {{ResolvedIssue}} <span class="vcard"><span class="dtstart">2009-04-24</span> raised by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
<div class="description">
* shipping removed in draft spec 0.2
</div>
</div>

<div class="vevent">
== <span class="summary">HP6 - P-V seems like a catch-all for hProduct</span> ==
* {{ResolvedIssue}} <span class="vcard"><span class="dtstart">2009-04-24</span> raised by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
<div class="description">
* p-v has been removed in draft spec 0.3 in favor of [[xoxo]]
</div>
</div>

<div class="vevent">
== <span class="summary">HP7 - Lots of vocabulary terms, does the data really back this up?</span> ==
* {{ResolvedIssue}} <span class="vcard"><span class="dtstart">2009-04-24</span> raised by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
<div class="description">
* many attributes have been removed in draft specs 0.2 and 0.3. We believe the current number of attributes accurately represents a product object while providing adequate opportunity to be combined with other microformats for better overall semantic solutions.
</div>
</div>

== Closed Issues ==

== Template ==
{{issues-format}}

hproduct-issues

2010-03-05T18:16:38Z

GeorgeBrock: /* HP8 - No clear way of including a valid hReview that refers back to the hProduct as its item */ fix typo

__TOC__

== HP1 - hProduct vs hListing regarding "price" / "quantity" / "shipping" fields ==

<div class="vevent">
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-12-17</span> raised by <span class="fn">NicolasLeroy</span></span>
<div class="description">
*# In the "[[hproduct#Out_of_Scope|out of scope]]" section, it is explained: _"This microformat does not intend to replicate any of the content proposed within hListing and would defer all money/transactional matters to that microformat"_
*# However, in the hProduct schema, we have the following fields:
*#* "price. optional. floating point number. can be further refined by type (msrp, regular, sale, clearance)" => if the price is the retailer price, then it should be delegated to hListing. We could imagine it represents the "manufacturer" price (which could be different from the retailer price) ; in this case, it should clearly be explained in the schema definition.
*#* I would say there is also ambiguity between the responsibilities of hProduct vs hListing for the following fields: quantity / shipping
*#** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-02-16</span>: I believe everyone agrees that we would borrow price from hListing for hProduct spec. I will explain the concept further in the schema.
*#** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-02-16</span>: I don't follow the quantity/ shipping issue. I don't see either of these on hListing, unless the concepts are somehow embedded in other attributes. Can you elaborate on what the ambiguity is? ([[User:PaulLee|Paul Lee]]: If there's no objection here, may I suggest updating the price reference and keeping quantity and shipping as is?])
*#* +1 I agree with NicholasLeroy, anything price or transaction related should be left out of hProduct 0.1, and instead develop recipes / mark-up examples showing use of hListing with hProduct. We need to strongly resist and fight the tendency to include "just one more field" to individual formats and instead push to use formats as building blocks. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
*#** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2009-03-03</span>: If price should be left to hListing, should hAudio be modified not to include "price"?
*#* I am going to add price back into the hProduct spec. Price is an attribute of a product. We should be able to use microformats either standalone or as building blocks in combination with other formats. On price I'm thinking specifically of product manufacturer sites who may not be commerce enabled and are listing their products for informational purposes. In this case, they would not be using hListing, as there would be no transaction taking place. Leaving the price attribute out would ignore a major product attribute (in 99% of product sites, per hproduct examples analysis).
</div>
</div>

<div class="vevent">

== <span class="summary">HP2 - FN should be used instead of N for product title</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* Why is <b>n</b> used instead of <b>fn</b> for the title of the product? hCard and hAudio both use fn for the formatted name of the product. <b>n</b> is usually an optimization.
* +1 hProduct should use "fn" for the name of the product. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-03-03</span>: "n" will be changed to "fn" in the next version of the schema
* "fn" is hardly semantic, even though commonly deployed - surely "formatted-name" is truer to the principles of "humans-first, machines second" --[[User:Wowitim|Wowitim]] 12:59, 28 March 2009 (UTC)
</div>

<div class="vevent">

== <span class="summary">HP3 - BUY duplicates functionality of PAYMENT from hAudio</span> ==
* {{OpenIssue}} <span class="vcard">BUY duplicates functionality of PAYMENT from hAudio<span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* <b>buy</b> is duplicating the functionality of <b>payment</b> from hAudio.
** Response <span class="vcard">by <span class="fn">[[User:PaulLee|Paul Lee]]</span>, 2008-02-18</span>: From the payment page: "RelPayment is a microformat for making exchanges of support (be it financial or otherwise) possible. By adding rel="payment" to a hyperlink a page indicates that the destination of that hyperlink provides a way to show or give support for the current page. For example to give financial support to the owner of the current page. One of the goals with this microformat is to give content aggregators such as RSS readers a way to extract these support links and give them special attention (such as displaying a standard button along with the content)." First, this seems like a simple exercise for blogs, etc.; but the transaction process for shopping sites is typically considerably more complex. Usually, the actual payment URI is toward the end of the cart checkout process, the entry to which "buy" is intended to direct to the beginning of. Second, there is the potential for confusion when using payment, since "payment" in the shopping space often refers to payment methods, e.g., credit card, check, etc.
* +1 but in a different way. BUY/PAYMENT should both be out of scope for hProduct, and only be in hListing per issue HP1 above. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
*#* Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2009-03-03</span>: Should these be in scope for hAudio then?
</div>
</div>

<div class="vevent">

== <span class="summary">HP4 - Are all of the formats for PRICE in hProduct allowed</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* The way that <b>price</b> is used is iffy - do we allow anything but currency/amount in the compound statement?
* +1 PRICE should not be in hProduct per issue HP1. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
*#* Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2009-03-03</span>: Should other microformats (thinking hAudio) be modified not to include "price"?
</div>
</div>

<div class="vevent">

== <span class="summary">HP5 - The format for the contents of SHIPPING are vague</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* Seems like <b>shipping</b> could be abused quite a bit, resulting in a term that is fairly useless as time moves on.
* +1 agreed and I think SHIPPING belongs in hListing (not in hProduct) as it applies to a particular transaction/offering, and is not intrinsic to the product itself. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
</div>
</div>

<div class="vevent">
== <span class="summary">HP6 - P-V seems like a catch-all for hProduct</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* <b>p-v</b> seems like a catch-all, shoe-horn attempt at making the microformat infinitely scalable? Is this really useful?
** Response <span class="vcard">by <span class="fn">[[User:PaulLee|Paul Lee]]</span>, 2008-02-18</span>: IIUC, part of the reason why hproduct has been under discussion for quite awhile is b/c of the debate between p-v vs. more defined attributes. p-v is quite helpful b/c the attributes users care about change over time. Take cameras, for instance. Did anyone care about megapixels 10 years ago? etc.
* +1 I strongly oppose p-v as it is nothing more than a circumvention of the microformats [[process]] and 80/20 [[principle]] of formalizing only common properties. [[microformats]] are NOT designed to be infinitely extensible. p-v is simply another source of Tower of Babel problems. When attributes change over time, then the microformat can be iterated/extended to include them, *when* publishing behavior on the web for the *data* of such attributes exceeds the required 80/20 usage per microformats process. That being said, if you really must include arbitrary property-value data, there is already a microformat for that: [[xoxo]]. Modularly include a [[xoxo]] child and that way the extension is contained in a specific structure that can be ignored by implementations. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
</div>
</div>

<div class="vevent">

== <span class="summary">HP7 - Lots of vocabulary terms, does the data really back this up?</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* There seem to be a great deal of vocab terms and the terms seem to be fairly loosely defined... are they all justified? Is there a file that we can analyze (like via microformalyze)?
** Response <span class="vcard">by <span class="fn">[[User:PaulLee|Paul Lee]]</span>, 2008-02-18</span>:The examples aren't necessarily an accurate reflection of how frequently attributes/data is used by retailers. In practice, model/mpn is used much more frequently than dimensions, both for retailer websites as well as retailer submissions to search and shopping engines. Defer to those with more experience/other data on version.
* +1. If you cannot justify a property, or are unsure about including it, or don't think it is necessarily an accurate reflection of how frequently the data is used, then leave it out per microformats [[principles]]. A "version" property was added to [[hReview]] for largely theoretical concerns, but has never been needed/used. So in practice (per experience), leave out "version". [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-03-03</span>: I agree on both fronts here, I was surprised that model wasn't more prevalent in the research data, as it seems like an attribute that appears on nearly every product. Since "model" is often used as a type of identifier, it should be moved under the identifier attribute. "Version" will be taken out.
</div>
</div>

<div class="vevent hentry">
== <span class="entry-title summary">HP8 - No clear way of including a valid hReview that refers back to the hProduct as its item</span> ==
* {{OpenIssue}} <span class="entry-summary author vcard"><span class="dtstart published">2010-03-05</span> raised by <span class="fn">[[User:GeorgeBrock|GeorgeBrock]]</span></span>
<div class="description entry-content discussion issues">
* An hProduct can include one or more hReviews. Each hReview requires an item, which should be the hProduct. The [[include-pattern]] prohibits references to an ancestor. Therefore it is not clear how to include a valid hReview in an hProduct.
</div>
</div>

== Resolved Issues ==
<div class="vevent">
<div class="vevent">
== <span class="summary">HP1 - hProduct vs hListing regarding "price" / "quantity" / "shipping" fields</span> ==
* {{ResolvedIssue}} <span class="vcard"><span class="dtstart">2009-04-24</span> raised by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
<div class="description">
* "quantity" and "shipping" have been removed from hproduct and transitioned to a new [[hlisting]] proposal. "price" has been retained, with the caveat that if hproduct is being used alone (eg., a non-commerce site who provides product information), without combining it with a microformat like [[hlisting]], it is assumed that the price attribute represents the suggested manufacturers retail price. All transactional details (including transactional price) would be deferred to [[hlisting]].
</div>
</div>

<div class="vevent">
== <span class="summary">HP2 - FN should be used instead of N for product titles</span> ==
* {{ResolvedIssue}} <span class="vcard"><span class="dtstart">2009-04-24</span> raised by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
<div class="description">
* changed in draft spec 0.2
</div>
</div>

<div class="vevent">
== <span class="summary">HP3 - BUY duplicates functionality of PAYMENT from hAudio</span> ==
* {{ResolvedIssue}} <span class="vcard"><span class="dtstart">2009-04-24</span> raised by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
<div class="description">
* buy removed in draft spec 0.2
</div>
</div>

<div class="vevent">
== <span class="summary">HP5 - The format for the contents of SHIPPING are vague</span> ==
* {{ResolvedIssue}} <span class="vcard"><span class="dtstart">2009-04-24</span> raised by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
<div class="description">
* shipping removed in draft spec 0.2
</div>
</div>

<div class="vevent">
== <span class="summary">HP6 - P-V seems like a catch-all for hProduct</span> ==
* {{ResolvedIssue}} <span class="vcard"><span class="dtstart">2009-04-24</span> raised by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
<div class="description">
* p-v has been removed in draft spec 0.3 in favor of [[xoxo]]
</div>
</div>

<div class="vevent">
== <span class="summary">HP7 - Lots of vocabulary terms, does the data really back this up?</span> ==
* {{ResolvedIssue}} <span class="vcard"><span class="dtstart">2009-04-24</span> raised by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
<div class="description">
* many attributes have been removed in draft specs 0.2 and 0.3. We believe the current number of attributes accurately represents a product object while providing adequate opportunity to be combined with other microformats for better overall semantic solutions.
</div>
</div>

== Closed Issues ==

== Template ==
{{issues-format}}

hproduct-issues

2010-03-05T18:15:20Z

GeorgeBrock: Added issue HP8 - No clear way of including a valid hReview that refers back to the hProduct as its item

__TOC__

== HP1 - hProduct vs hListing regarding "price" / "quantity" / "shipping" fields ==

<div class="vevent">
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-12-17</span> raised by <span class="fn">NicolasLeroy</span></span>
<div class="description">
*# In the "[[hproduct#Out_of_Scope|out of scope]]" section, it is explained: _"This microformat does not intend to replicate any of the content proposed within hListing and would defer all money/transactional matters to that microformat"_
*# However, in the hProduct schema, we have the following fields:
*#* "price. optional. floating point number. can be further refined by type (msrp, regular, sale, clearance)" => if the price is the retailer price, then it should be delegated to hListing. We could imagine it represents the "manufacturer" price (which could be different from the retailer price) ; in this case, it should clearly be explained in the schema definition.
*#* I would say there is also ambiguity between the responsibilities of hProduct vs hListing for the following fields: quantity / shipping
*#** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-02-16</span>: I believe everyone agrees that we would borrow price from hListing for hProduct spec. I will explain the concept further in the schema.
*#** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-02-16</span>: I don't follow the quantity/ shipping issue. I don't see either of these on hListing, unless the concepts are somehow embedded in other attributes. Can you elaborate on what the ambiguity is? ([[User:PaulLee|Paul Lee]]: If there's no objection here, may I suggest updating the price reference and keeping quantity and shipping as is?])
*#* +1 I agree with NicholasLeroy, anything price or transaction related should be left out of hProduct 0.1, and instead develop recipes / mark-up examples showing use of hListing with hProduct. We need to strongly resist and fight the tendency to include "just one more field" to individual formats and instead push to use formats as building blocks. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
*#** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2009-03-03</span>: If price should be left to hListing, should hAudio be modified not to include "price"?
*#* I am going to add price back into the hProduct spec. Price is an attribute of a product. We should be able to use microformats either standalone or as building blocks in combination with other formats. On price I'm thinking specifically of product manufacturer sites who may not be commerce enabled and are listing their products for informational purposes. In this case, they would not be using hListing, as there would be no transaction taking place. Leaving the price attribute out would ignore a major product attribute (in 99% of product sites, per hproduct examples analysis).
</div>
</div>

<div class="vevent">

== <span class="summary">HP2 - FN should be used instead of N for product title</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* Why is <b>n</b> used instead of <b>fn</b> for the title of the product? hCard and hAudio both use fn for the formatted name of the product. <b>n</b> is usually an optimization.
* +1 hProduct should use "fn" for the name of the product. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-03-03</span>: "n" will be changed to "fn" in the next version of the schema
* "fn" is hardly semantic, even though commonly deployed - surely "formatted-name" is truer to the principles of "humans-first, machines second" --[[User:Wowitim|Wowitim]] 12:59, 28 March 2009 (UTC)
</div>

<div class="vevent">

== <span class="summary">HP3 - BUY duplicates functionality of PAYMENT from hAudio</span> ==
* {{OpenIssue}} <span class="vcard">BUY duplicates functionality of PAYMENT from hAudio<span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* <b>buy</b> is duplicating the functionality of <b>payment</b> from hAudio.
** Response <span class="vcard">by <span class="fn">[[User:PaulLee|Paul Lee]]</span>, 2008-02-18</span>: From the payment page: "RelPayment is a microformat for making exchanges of support (be it financial or otherwise) possible. By adding rel="payment" to a hyperlink a page indicates that the destination of that hyperlink provides a way to show or give support for the current page. For example to give financial support to the owner of the current page. One of the goals with this microformat is to give content aggregators such as RSS readers a way to extract these support links and give them special attention (such as displaying a standard button along with the content)." First, this seems like a simple exercise for blogs, etc.; but the transaction process for shopping sites is typically considerably more complex. Usually, the actual payment URI is toward the end of the cart checkout process, the entry to which "buy" is intended to direct to the beginning of. Second, there is the potential for confusion when using payment, since "payment" in the shopping space often refers to payment methods, e.g., credit card, check, etc.
* +1 but in a different way. BUY/PAYMENT should both be out of scope for hProduct, and only be in hListing per issue HP1 above. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
*#* Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2009-03-03</span>: Should these be in scope for hAudio then?
</div>
</div>

<div class="vevent">

== <span class="summary">HP4 - Are all of the formats for PRICE in hProduct allowed</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* The way that <b>price</b> is used is iffy - do we allow anything but currency/amount in the compound statement?
* +1 PRICE should not be in hProduct per issue HP1. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
*#* Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2009-03-03</span>: Should other microformats (thinking hAudio) be modified not to include "price"?
</div>
</div>

<div class="vevent">

== <span class="summary">HP5 - The format for the contents of SHIPPING are vague</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* Seems like <b>shipping</b> could be abused quite a bit, resulting in a term that is fairly useless as time moves on.
* +1 agreed and I think SHIPPING belongs in hListing (not in hProduct) as it applies to a particular transaction/offering, and is not intrinsic to the product itself. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
</div>
</div>

<div class="vevent">
== <span class="summary">HP6 - P-V seems like a catch-all for hProduct</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* <b>p-v</b> seems like a catch-all, shoe-horn attempt at making the microformat infinitely scalable? Is this really useful?
** Response <span class="vcard">by <span class="fn">[[User:PaulLee|Paul Lee]]</span>, 2008-02-18</span>: IIUC, part of the reason why hproduct has been under discussion for quite awhile is b/c of the debate between p-v vs. more defined attributes. p-v is quite helpful b/c the attributes users care about change over time. Take cameras, for instance. Did anyone care about megapixels 10 years ago? etc.
* +1 I strongly oppose p-v as it is nothing more than a circumvention of the microformats [[process]] and 80/20 [[principle]] of formalizing only common properties. [[microformats]] are NOT designed to be infinitely extensible. p-v is simply another source of Tower of Babel problems. When attributes change over time, then the microformat can be iterated/extended to include them, *when* publishing behavior on the web for the *data* of such attributes exceeds the required 80/20 usage per microformats process. That being said, if you really must include arbitrary property-value data, there is already a microformat for that: [[xoxo]]. Modularly include a [[xoxo]] child and that way the extension is contained in a specific structure that can be ignored by implementations. [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
</div>
</div>

<div class="vevent">

== <span class="summary">HP7 - Lots of vocabulary terms, does the data really back this up?</span> ==
* {{OpenIssue}} <span class="vcard"><span class="dtstart">2009-02-17</span> raised by <span class="fn">[[User:ManuSporny|ManuSporny]]</span></span>
<div class="description">
* There seem to be a great deal of vocab terms and the terms seem to be fairly loosely defined... are they all justified? Is there a file that we can analyze (like via microformalyze)?
** Response <span class="vcard">by <span class="fn">[[User:PaulLee|Paul Lee]]</span>, 2008-02-18</span>:The examples aren't necessarily an accurate reflection of how frequently attributes/data is used by retailers. In practice, model/mpn is used much more frequently than dimensions, both for retailer websites as well as retailer submissions to search and shopping engines. Defer to those with more experience/other data on version.
* +1. If you cannot justify a property, or are unsure about including it, or don't think it is necessarily an accurate reflection of how frequently the data is used, then leave it out per microformats [[principles]]. A "version" property was added to [[hReview]] for largely theoretical concerns, but has never been needed/used. So in practice (per experience), leave out "version". [[User:Tantek|Tantek]] 23:41, 18 February 2009 (UTC)
** Response <span class="vcard">by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-03-03</span>: I agree on both fronts here, I was surprised that model wasn't more prevalent in the research data, as it seems like an attribute that appears on nearly every product. Since "model" is often used as a type of identifier, it should be moved under the identifier attribute. "Version" will be taken out.
</div>
</div>

<div class="vevent hentry">
== <span class="entry-title summary">HP8 - No clear way of including a valid hReview that refers back to the hProduct as its item</span> ==
* {{OpenIssue}} <span class="entry-summary author vcard"><span class="dtstart published">2010-03-05</span> raised by <span class="fn">[[User:GeorgeBrock|GeorgeBrock]]</span></span>
<div class="description entry-content discussion issues">
* An hProduct an include one or more hReviews. Each hReview requires an item, which should be the hProduct. The [[include-pattern]] prohibits references to an ancestor. Therefore it is not clear how to include a valid hReview in an hProduct.
</div>
</div>

== Resolved Issues ==
<div class="vevent">
<div class="vevent">
== <span class="summary">HP1 - hProduct vs hListing regarding "price" / "quantity" / "shipping" fields</span> ==
* {{ResolvedIssue}} <span class="vcard"><span class="dtstart">2009-04-24</span> raised by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
<div class="description">
* "quantity" and "shipping" have been removed from hproduct and transitioned to a new [[hlisting]] proposal. "price" has been retained, with the caveat that if hproduct is being used alone (eg., a non-commerce site who provides product information), without combining it with a microformat like [[hlisting]], it is assumed that the price attribute represents the suggested manufacturers retail price. All transactional details (including transactional price) would be deferred to [[hlisting]].
</div>
</div>

<div class="vevent">
== <span class="summary">HP2 - FN should be used instead of N for product titles</span> ==
* {{ResolvedIssue}} <span class="vcard"><span class="dtstart">2009-04-24</span> raised by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
<div class="description">
* changed in draft spec 0.2
</div>
</div>

<div class="vevent">
== <span class="summary">HP3 - BUY duplicates functionality of PAYMENT from hAudio</span> ==
* {{ResolvedIssue}} <span class="vcard"><span class="dtstart">2009-04-24</span> raised by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
<div class="description">
* buy removed in draft spec 0.2
</div>
</div>

<div class="vevent">
== <span class="summary">HP5 - The format for the contents of SHIPPING are vague</span> ==
* {{ResolvedIssue}} <span class="vcard"><span class="dtstart">2009-04-24</span> raised by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
<div class="description">
* shipping removed in draft spec 0.2
</div>
</div>

<div class="vevent">
== <span class="summary">HP6 - P-V seems like a catch-all for hProduct</span> ==
* {{ResolvedIssue}} <span class="vcard"><span class="dtstart">2009-04-24</span> raised by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
<div class="description">
* p-v has been removed in draft spec 0.3 in favor of [[xoxo]]
</div>
</div>

<div class="vevent">
== <span class="summary">HP7 - Lots of vocabulary terms, does the data really back this up?</span> ==
* {{ResolvedIssue}} <span class="vcard"><span class="dtstart">2009-04-24</span> raised by <span class="fn">[[User:JayMyers|JayMyers]]</span></span>
<div class="description">
* many attributes have been removed in draft specs 0.2 and 0.3. We believe the current number of attributes accurately represents a product object while providing adequate opportunity to be combined with other microformats for better overall semantic solutions.
</div>
</div>

== Closed Issues ==

== Template ==
{{issues-format}}

test-fixture-issues

2009-07-01T16:43:05Z

GeorgeBrock: Possible benefits of retaining a separate assertion method for dates

Issues against test-fixture. Note that this poshformat has not been through the microformats process and serves a funcational purpose for the [[test-suite]] work.

<div class="hentry">
{{OpenIssue}} <span class="entry-summary author vcard"><span class="published">2009-06-26</span> raised by <span class="fn">[[User:BenWard|BenWard]]</span></span>
<div class="entry-content discussion issues">
* <strong class="entry-title">Output type could be implied from <code>a/@type</code> rather than explicit?</strong>. Currently the output type is explicit in a <code>type</code> attribute, but either the output could just be taken from the anchor, or if it is duplicated visibly, perhaps it should match the MIME type rather than using strings? e.g. <code>&ltspan class="type">text/html</span></code>.
** …
</div>
</div>

<div class="hentry">
{{OpenIssue}} <span class="entry-summary author vcard"><span class="published">2009-06-26</span> raised by <span class="fn">[[User:BenWard|BenWard]]</span></span>
<div class="entry-content discussion issues">
* <strong class="entry-title">Represent history of changes using hAtom rather than hCalendar</strong>. It strikes me that [[hAtom]] would be a more appropriate format for a changelog than hCalendar.
** …
</div>
</div>

<div class="hentry">
{{OpenIssue}} <span class="entry-summary author vcard"><span class="published">2009-06-26</span> raised by <span class="fn">[[User:BenWard|BenWard]]</span></span>
<div class="entry-content discussion issues">
* <strong class="entry-title">Consider separating *Unit asserts from custom asserts</strong>. Although the normalisation of Geo and Dates is a very useful enhancement, they may not be essential (since ISO dates can be compared somewhat reliably as strings, and co-ordinates compared to the same precision as they appear in the source). This seems desirable for simple conversion into something like JUnit, without being dependent on additional functions.
** Some parsers discard the ISO string in favor of another date representation (e.g. [http://mofo.rubyforge.org/ MoFo], [http://github.com/danwrong/sumo/ Sumo]). When testing these parsers, equality assertions for dates would require some additional logic to compare the parsed value to the asserted value. For parsers that output dates as a generic data type (e.g. as an integer containing a UNIX timestamp) detecting when to apply this date-specific logic would be non-trivial and could require knowledge of which µf fields should contain dates, undermining the design goal of self contained tests. Keeping a separate equality assertion method for dates could therefore reduce complexity overall. - [[User:GeorgeBrock|GeorgeBrock]] 16:43, 1 July 2009 (UTC)
** …
</div>
</div>

test-suite-2009

2009-06-20T06:22:15Z

GeorgeBrock: /* Test Structure */ Fixed a broken link

<entry-title>Test Suites</entry-title>

So, you want to parse microformats in your app? Awesome. There are [[parsers]] in many languages.

A critical effort to assist in interoperability and completeness of microformat parsing is the Test Suite. This page documents the effort to produce test cases for each microformat and parsing pattern, so that you can verify the operations of your parser.

'''NB''': ''This page is new. There is a limited test suite available already for [[hCard]], [[hCalendar]], [[hReview]] and [[hAtom]]. It is somewhat outdated and unmaintained, but should give you a starting point. This effort hopes to produce something far more robust and extensive, as well as setting a precedent and framework for future microformats and test suites.''

This page will be expanded.

==Get the Tests==

; hCard
: ???
; hCalendar
: ???
; hAtom
: ???
; hReview
: ???
; Geo
: ???

==Goals of Test Suite Project==

We need to support specifications with better tests. There's no better way for parser writers to verify the correctness and completeness of their code without them. Microformats are getting adopted by big players, with large, stable implementations and are having bigger and bigger impact. It's critical that implementers don't reinvent the testing wheel for each new project.

We need to provide a suite to:

* Verify the correctness of microformats parsing
* Indicate the completeness of a parser implementation
* Ensure that global patterns like [[abbr-design-pattern]] and [[value-class-pattern]] are implemented accurately
* Provide a base set of tests for implementations to build their automated test scripts
* Encourage implementations to put their tests into this combined effort, rather than working alone

==Test Structure==

Each test takes the form of:

* Valid HTML 4 or XHTML 1.0 compatible file, containing the HTML mark-up for the test itself, along with the assertions used to validate the test.
* Assertions are described using a <code>test-fixture</code> mark-up pattern, invented by Glen Jones for his [http://www.ufxtract.com/testsuite/ µfextract tests]. ''This pattern needs to be documented here.''

This generic format has the following advantages:

* '''It is language implementation agnostic''', so never has to be ported into other languages (e.g. PHPUnit tests ported to JUnit ported to YUITest ported to…)
* '''The test case and assertions are contained in the same physical file'''. One file per test is easier to manage than multiple files associated in name.
* '''The test is self-documenting'''. Because the test is written in HTML, it can contain explanation alongside the assertions, can be verified easily by hand, as well as parsed by machines.
* The <code>test-fixture</code> format can be tested using itself.
* Dedicated automated test suites for languages (PHP, Python, JavaScript, Ruby, etc.) can be generated from the HTML using a single script. One new test case written using <code>test-fixture</code> can create tests for all languages.
* It's useful that all tests be in the same output format. Early tests for microformats returned native formats, such as <code>vcf</code> (vcard), <code>ics</code> (iCal) and Atom. These were useful in the context of early implementations, but parsers and consuming cases are now more sophisticated so providing assertions to verify against is more useful.

'''There is to be one test suite per format'''. In some cases, such as [[geo]] and [[adr]] with [[hCard]], the address and geo portions will be included in the geo and adr test suites and hCard parsers will be expected to run cases from all three suites.

Tests using global patterns, such as value-class and abbr-design-pattern should be included in tests for ''all'' vocabularies, where appropriate.

Each vocabulary suite is organized as follows

* <kbd>/stable</kbd> contains tests for the stable, specified aspects of each vocabulary.
** <kbd>/stable/new</kbd> is the initial location for a new test. Tests are checked into <kbd>new</kbd> first, pending peer-review. After review, the test is moved into <kbd>verified</kbd>.
** <kbd>/stable/verified</kbd> contains tests for stable aspects of a specification which have been sanity checked by at least one other. These tests will be presented as (and should be) 100% correct and reliable.
* <kbd>/experimental</kbd> is a repository for brainstorm tests, for experimental implementations. The tests will be filed under <kbd>/experimental/brainstorm-name</kbd>. This keeps them separate from the stable branch, but makes it easy to merge them in if a brainstorm is successful and results in an update to the spec.
* <kbd>/old</kbd> contains tests that don't match the proposed test suite format/criteria. They're useful and should be ported to the new form, but are filed separately.

==Establishment Tasks==

* Get the existing test cases from <code>hg.microformats.org</code> and into a Github repository.
** The collaboration functionality of Github is well suited to the development of new tests.
* Get the existing <code>test-fixture</code> tests integrated
** Needs Public Domain release from Glen Jones.
* Make people aware of it!
* Compile documentation for <code>test-fixture</code>
* Fill in all the blanks on this page.
* Rewrite the existing hCard, hCalendar and hAtom tests to transform into JSON rather than native formats
* Encourage production open source scripts to convert a <code>test-fixture</code> document into a runnable test case in major languages:
** PHP, Perl, Ruby, Python, .NET, Java
** Produce <code>test-fixture</code> test cases for <code>test-fixture</code> itself.

Later, thought should be given to how assertions can be used to test implied meanings in microformats. For example, we cannot test ‘hCard is an organisation’ using a simple assert, since that is not a field of hCard (but would be a data field in an implementation). Initially, these implied meanings should just be documented in the tests, and applicable implementations can take note.

==Related==

* [[parsers|Parsers]]
* [[debugging-tools|Debugging Tools]]
* [http://www.ufxtract.com/testsuite/ ufXtract test suite]

xfn-implementations

2009-06-11T21:59:27Z

GeorgeBrock: /* new implementations */ Added XFN profile discovery Greasemonkey script

<h1> XFN Implementations </h1>
{{TOC-right}}
In addition to the [http://gmpg.org/xfn/tools XFN Tools] page, this page contains more more recent implementations.

== new implementations ==
The following implementations have been developed which either generate or parse [http://gmpg.org/xfn XFN relationship links]. If you have an XFN implementation, feel free to add it to the '''top''' of this list.

* [http://blog.georgebrock.com/events/open-hack-london-xfn-profile-discovery XFN profile discovery] - A Greasemonkey script that follows rel="me" links from the current page to find a person's other sites and profiles.
* [http://afrigator.com Afrigator] by [[Stii|Stii Pretorius]] - use XFN data found on blog rolls to find friends on Afrigator.com (Screen cast - [http://www.vimeo.com/1110175 http://www.vimeo.com/1110175])
* [http://digg.com/ Digg] by [[SteveWilliams|Steve Williams]] (Example: [http://digg.com/users/sbwms Steve's Digg user profile].)
* [http://donpark.org:3301/ XFN friend finder] by Don Park ([http://www.donpark.org/blog/articles/2008/03/15/my-rss-reader-just-killed-friendfeed blog explanation]).
* [http://www.qmpeople.com/ qmpeople] - Generates XFN from address book properties of registered users - e.g. http://www.qmpeople.com/users/laserion
* [http://textcube.org TextCube] Blogging tool TextCube version 1.6 and later.
* [http://code.google.com/apis/socialgraph/ Google Social Graph API] uses XFN data from public Web sites as its main data source.

=== appear old or unverifiable ===
These sites appear to be too old, and or perhaps broken (like PHP error dump).
* [http://tagalag.com Tagalag] Tagalag [http://tagalag.com/tools.html#xfn supports] a partial XFN vocabulary.

== update streams and pingers ==
* [http://updates.elsewhere.im/ SixApart Relationship Update Stream] - launched 2007-10-19

== authoring publishing ==
The following tools, plugins, and extensions enable authors to eaily create and publish XFN links:
* [http://icite.net/develop/software.html#ll4blojsom LL4blojsom] is the LinkList plugin for the [http://blojsom.sf.net blojsom] blog engine. blojsom, written in Java, is the open source application behind the Tiger Weblog Server that is part of OS X server. The LL4blojsom plugin is used for creating XFN blogrolls.
* [http://www.zachinglis.com/projects/xfn-rel-creator/ XFN rel Creator] This script replaces any links within the designated tags and replaces them with a visual representation of the links. Default set as abbrevations but with CSS it is easy to replace them for images.
* [http://www.wordpress.org/ WordPress] has XFN support built-in to its Link Manager function, which is used for generating blogrolls. When in the administrative interface, choose the Links top-level menu item, then choose Add Link. The link form lets you choose which XFN properties you wish the link to have. When displaying the links on the site via any of the standard WordPress template tags, it will automatically format it with the appropriate tags in the rel attribute. (based on [http://gmpg.org/xfn/creator XFN Creator])
* [http://www.communityserver.org/ Community Server] has XFN support in its blog Link Lists. It allows you to select which XFN tag(s) to use for each link.
* [http://www.webstandards.org/action/dwtf/microformats/ Dreamweaver Extension suite] from the [http://webstandards.org/ Web Standards Project] enables the authoring of XFN links from within Dreamweaver 8.
* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding XFN and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].
* [http://www.zachinglis.com/projects/xfn-rel-creator/ XFN rel Creator] This script replaces any links within the designated tags and replaces them with a visual representation of the links. Default set as abbrevations but with CSS it is easy to replace them for images.
* [http://www.oddmuse.org/cgi-bin/oddmuse/xfn_Module OddMuse XFN Module] allows a wiki markup in OddMuse wikis for entering data about xfn relationships

== friends lists ==
Numerous services support both XFN friends lists, and even better XFN+[[hcard|hCard]] friends lists.
* See [[hcard-xfn-friends-lists|hCard+XFN friends lists]].

== rel me identity equivalency ==
* [http://wordpress.org/extend/plugins/yadis/ YADIS plugin] supports OpenID delegation links that are also compatible XFN rel-me links.
* [http://wink.com Wink] supports rel-me (see [http://wink.com/beach--profile])
** '''suboptimal''': uses "nofollow me" where it should just use "me". User entered profile information is first party, not 3rd party, and therefore should not be labeled with [[rel-nofollow]].

== validators ==
* [http://tools.microformatic.com/help/xhtml/rel-lint/ rel-lint] by [[User:DrewMcLellan|Drew McLellan]] will validate existence of XFN attributes.

== visualizers and browsers ==
* [http://manyeyes.alphaworks.ibm.com/manyeyes/visualizations/xhtml-friends-network-with-twitter XFN visualization] example at IBM's Many Eyes made with [http://sphinx.net.ru/hg/xfn-spider xfn-spider] — simple crawler extracting microformats with XSLT ([http://sphinx.net.ru/blog/entry/simple-microformat-xslt-extraction/ Original article in Russian] circa summer 2007) and exporting information to OPML feedlist, [http://manyeyes.alphaworks.ibm.com/manyeyes/visualizations/tags-from-a-bigger-xhtml-friend-netw tag cloud] etc.
* [http://xfngraph.sourceforge.net XFN Graph] — a multi-platform Java-based tool which creates spider diagrams of XFN relationships from any given starting URL.
* [http://xfnroll.new-bamboo.co.uk/people/popular XFNRoller] (to be lifestalker.com) XFN spider and browser focused on using blogs to represent individuals. Exports OPML of feeds for lists such as top 10 most popular people.

== search ==
* [http://xfnsearch.joshpeek.com/ XFN Search] (appears to require HTTP-authentication login)

== converters ==
* see [[xfn-to-foaf]]

== See Also ==
{{xfn-related-pages}}

events/2009-06-27-microformats-vevent-london

2009-06-10T19:19:09Z

GeorgeBrock: /* Attending */ Attending event and willing to help out

{{stub}}

This page is for organizing a vEvent in London in June. One of several microformats [[events]].

If you'd like to help out, please add your name!

== Attending ==
Add your name if you're definitely coming:
* [[User:Phae|Frances Berriman]]
* [[User:GeorgeBrock|George Brocklehurst]] (happy to help out before and/or at the event)
...

== Interested ==
Add your name if you're interested in coming, but aren't sure yet:
*
...

== location ==
There are several possibilities for venue, let's figure out what makes the most sense:
* TBC

== date ==
* 27th June - evening. Probably for dinner after the standards.forward HTML5 event. TBC.

debugging-tools

2009-06-01T22:12:37Z

GeorgeBrock: /* Rails assert microformats */ Name correction and link to user page

<entry-title>Microformats Debugging</entry-title>

Conformance checkers, validators, linting tools and debuggers.

__TOC__

== general microformats tools ==

===Optimus===
{{main|Optimus}}

[[Optimus]] is a microformats transformer and validator that supports numerous microformats including [[hCard]], [[hCalendar]], [[hReview]], [[hAtom]] (note: [[optimus-issues#hAtom_validation|hAtom validation issues]]).

Get the [http://tantek.com/favelets/#optimus-validator Optimus microformats validator favelet]. Blog post: [http://microformats.org/blog/2009/05/27/placemaker-optimus-validator/#optimus-favelet validator browser button].

Please add issues to the [[optimus-issues]] page.

===Operator Debugger===
{{main|Operator}}
* [https://addons.mozilla.org/firefox/4106/ https://addons.mozilla.org/firefox/4106/]

Operator does a good job of compliant parsing for microformats in general, and includes a debug mode that can help identify errors in the object structure.

=== rel-lint ===
* [http://tools.microformatic.com/help/xhtml/rel-lint/ http://tools.microformatic.com/help/xhtml/rel-lint/]

Rel-Lint provides linting and inspection of [[rel-tag|rel-tag]] and [[xfn|XFN]] (by [[implementors#Drew_McLellan|Drew McLellan]])

=== Rails assert microformats ===
* [[User:GeorgeBrock|George Brocklehurst]] has written open source code and a post explaining how to do [http://blog.georgebrock.com/projects/testing-microformats-in-rails-applications-with-assert-microformats testing microformats in Rails applications with assert-microformats].

== microformats specific tools ==
=== [[hCard]] ===

* http://hcard.geekhood.net/
* Also try the [http://feeds.technorati.com/contacts/ Technorati Contacts Feed service].
* The [http://srv.buzzword.org.uk Cognition web service] includes hCard error messages and warnings using [http://www.w3.org/TR/EARL10/ EARL] as part of the RDF output — hopefully other microformats will be covered in the near future.

=== [[hCalendar]] ===

* Try the [http://feeds.technorati.com/events/ Technorati Events Feed service].

== related ==
* [[implementations]]
* [[tests]]
* [[test-suite]]

value-class-pattern

2009-05-12T08:51:19Z

GeorgeBrock: /* Examples in the wild */ Added georgebrock.com and blog.georgebrock.com

<entry-title>Value Class Pattern</entry-title>
'''Document status: alpha.'''

The value class pattern is derived from [[hCard#Value_excerpting|value-excerpting]] in hCard. As such, it is already somewhat supported in parsers.

As of 2009-05-01, the editors believe the value-class-pattern to be "feature complete" and ready for use in markup and encourage implementers to update accordingly and provide [[value-class-pattern-feedback|feedback]]. '''However''', the precise parsing behavior is not quite finalized, and the documentation is a work in progress. The pattern should be used with some caution.''

__TOC__

; Editors
: <span class="vcard"><span class="fn">[[User:BenWard|Ben Ward]]</span></span>
: <span class="vcard"><span class="fn">[[User:Tantek|Tantek Çelik]]</span></span>

Sometimes, only a part of an element's content is to be used as the value of a microformat property. This may occur when a property has optional subproperties, such as <code>tel: type</code> and <code>tel: value</code> in [[hCard]]. Other times, the most appropriate structure for a property may include other content.

For these purposes, the special class name <code>value</code> is used to mark-up the relevant data excerpt from larger element content.

==Simple Examples==

Here is markup for a home phone number:

vCard fragment:

<source lang=text>TEL;TYPE=HOME:+1.415.555.1212</source>

hCard fragment:

<source lang=html4strict>
<span class="tel">
<span class="type">Home</span>:
<span class="value">+1.415.555.1212</span>
</span>
</source>

In this case, the <code>value</code> of <code>tel</code> is <code>+1.415.555.1212</code>, not <code>Home: +1.415.555.1212</code>.

Sometimes the value for a microformats property must be split into multiple pieces in the content of the element representing that property. Multiple elements with a class name of "value" (value elements) can be used to extract and concatenate these pieces into a single value for microformats properties which expect simple strings or tel values.

Another example, this time using a localized (British) telephone number:

<source lang=html4strict>
<span class="tel">
<span class="type">Home</span>:
<span class="value">+44</span> (0) <span class="value">1223 123 123</span>
</span>
</source>

In this case, the valid ''data'' for the telephone number is <samp>+441223123123</samp>, but the way in which phone number is presented in Britain will include the <samp>(0)</samp>, for local dialling. That is, from anywhere in the world you may dial <kbd>+441223123123</kbd>, or from within Britain you may dial <kbd>01223123123</kbd>. Common local publishing interferes with the data, since dialling <kbd>'''+440'''1223123123</kbd> is an invalid number.

In the mark-up, two <code>value</code> classes target the part of the telephone number string that makes an international, valid number, whilst allowing conventional presentation.

Another example, using <code>dtstart</code> in [[hCalendar]]:

<source lang=html4strict>
<span class="dtstart">
Friday 25th May, 6pm
[<span class="value">2008-05-25T18:00:00+0100</span>]
</span>
</source>

Whilst the entire string ‘Friday 25th May, 6pm <nowiki>[…]</nowiki>’ is date information, it's only the ISO 8601 encoded datetime which must be consumed by a microformats parser, so the <code>value</code> class isolates it.

Note that "dtstart" is a datetime property and thus subject to additional special value class pattern handling as described in the [[#Date_and_time_values|Date and time values]] section below.

==Basic Parsing==
# The value class pattern only applies to properties which are simple strings, enumerated values, telephone numbers, and datetimes. The value class pattern does not affect parsing of properties of type email, URL, URI, UID.
# Where an element with such a microformat property class name has a descendant with class name <code>value</code> (a "value" element), parsers should use the following portion of that element:
## if the value element is an <code>img</code> or <code>area</code> element, then use the element's <code>alt</code> attribute value.
## if the value 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.
# Where there are multiple descendants of a property with class name of <code>value</code> (multiple value elements)
## if the microformats property expects a simple string, enumerated value, or telephone number, then the values extracted from the value elements should be concatenated ''without'' inserting additional characters or white-space.
## if the microformats property expects a datetime value, see the [[#Date_and_time_parsing|Date Time Parsing]] section.
# Descendants with class of <code>value</code> must not be parsed deeper than one level. That is, where an element <code>foo</code> with class <code>value</code> has a <em>descendant</em> <code>bar</code> with class <code>value</code>, the content of <strong><code>foo</code></strong> is taken as the <code>value</code>. Nesting additional elements with class of <code>value</code> cannot be used to further isolate a property's value.

e.g.

<source lang=html4strict>
<p class="description">
<foo class="value">
<bar class="value">Puppies Rule!</bar>
<strong>But kittens are better!</strong>
</foo>
</p>
</source>

In this example, <code>description</code> has a child ‘<code>value</code>’, and that child has a ''grandchild'' ‘<code>value</code>’. However, the parsing of <code>value</code> classes stops at the first level, so the data for <code>description</code> is: <samp><code><bar class="value">Puppies Rule!</bar><strong>But kittens are better!</strong></code></samp>.

== Date and time values ==
Some microformats properties expect an ISO8601 datetime value, e.g. [[hCalendar]] <code>dtstart</code> and <code>dtend</code> or [[hAtom]] <code>published</code>.

Authors may use the value class pattern to separately specify the date and the time, which are then combined to specify a single datetime value.

Example:

<source lang=html4strict>
<p>The weekly dinner will be on
<span class="dtstart">
<abbr class="value" title="2008-06-24">this Tuesday</abbr>
at <span class="value">18:30</span>
</span>
</p>
</source>

Produces:

<source lang=text>
DTSTART:2008-06-24T18:30:00
</source>

The lack of a timezone indicates a "floating" datetime, that is a datetime independent of any particular timezone. Examples of floating datetimes could be an alarm clock you set to ring at 7am, or the common 9am-5pm workday.

=== Date and time parsing ===
For all date time 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 both a specific ISO8601 date and a specific time, use those and stop looking for "value" elements.
* if the value has *only* a specific date, specifically, fits the following ISO8601 date patterns (i.e. as documented in the [http://en.wikipedia.org/wiki/ISO_8601 Wikipedia summary of ISO8601])
** YYYY-MM-DD
** YYYY-DDD
** then use that as the date value. For the purposes of the value class pattern, the hyphens "-" separating the year, month, day and/or ordinal day are required.
** ignore any further "value" elements that specify the date.
* if the value has *only* a specific time (with or without timezone), parse it for a time value as follows
** HH:MM:SS-XX:YY
** HH:MM:SS+XX:YY
** HH:MM:SS-XXYY
** HH:MM:SS+XXYY
** HH:MM:SSZ
** HH:MM:SS
** HH:MM-XX:YY
** HH:MM+XX:YY
** HH:MM-XXYY
** HH:MM+XXYY
** HH:MMZ
** HH:MM
** HH is the 24 hour "hours" in the time, from 00 to 24, with optional leading 0 for values less than 10.
** MM are the minutes from 00 to 59
** SS are the optional seconds from 00 to 59 (60 for a leap second). If omitted, infer 00.
** XX is the time zone hours offset, from 00 to 12
** YY is the time zone minutes offset, from 00 to 59, though in practice only 00, 15, 30, 45 minute offsets are used in global timezones.
** Z is the literal 'Z' to indicate GMT.
** For the purposes of the value class pattern, the colons ":" separating the hour, minutes, seconds are required.
** However the colons ":" separating the hours and minutes of any timezone offset are ''optional'' and discouraged in order to make it less likely that a timezone offset will be confused for a time.
** (NOTE: consider a case insensitive { }"am"|{ }"a.m." suffix to treat an HH value of 12 as 00, or a case-insensitive { }"pm"|{ }"p.m." suffix to add 12 to HH value less than 12 - per [http://en.wikipedia.org/wiki/12-hour_clock Wikipedia article on the 12 hour clock])
** ignore any further "value" elements that specify the time.
* if the value has *only* a specific timezone, parse it as follows
** -XX:YY
** +XX:YY
** -XXYY
** +XXYY
** Z
** ignore any further "value" elements that specify the timezone.

If by parsing the "value" element(s), at least a specific date has been found, then the "value" is overall valid, and the parser assembles the overall datetime value by concatenating the specific date, "T" and specific time (if time was specified, with 00 seconds implied if no seconds are provided), and specific timezone (if timezone and a specific time was specified).
* YYYY-MM-DD - no time specified
* YYYY-MM-DDTHH:MM:SS - time specified but no timezone. This is a floating time.
* YYYY-MM-DDTHH:MM:SS-XXYY or
* YYYY-MM-DDTHH:MM:SSZ or
* YYYY-MM-DDTHH:MM:SS+XXYY - both time and timezone were specified.

=== derivation and tests ===
The handling of date and time values in the value class pattern was originally [[value-excerption-pattern-brainstorming#date_and_time_separation|brainstormed on the value-excerption-pattern-brainstorming]] page and derived from that analysis and feedback. For the curious, historical details may be found there, along with additional thoughts for extension.

Date and time separation and concatenation tests are available: [[value-excerption-dt-separation-test]]

==Parsing value from a <code>title</code> attribute==
The <code>value-title</code> class name allows the publisher to indicate the data value for a parent property is contained in the <code>title</code> attribute of an element, rather than the inner-text.

This can be used to provide a synonym within content, or used to quietly publish alternate forms of information for microformats parsing, without affecting the consumption of content.

For example, you can use casual localization with dates:

<source lang=html4strict>
<p>It was
<span class='dtstart'>
<span class='value-title' title='2008'>last year</span>
</span>
that I realised my addiction to cashew nuts would cost this country so dear.
</p>
</source>

Parsing rules for <code>value-title</code> are the same as for <code>value</code> above, with the following change:

* Where a microformats property has a child element with class name of <code>value-title</code>, the content of the <code>title</code> attribute of that element must be parsed, rather than the portion of the element that would be parsed for a class name of <code>value</code>.

===Using <code>value-title</code> to publish machine-data===

The initial usage of <code>value-title</code> is used to publish alternate, parsable forms of property values in a visible context without the use of the <code>abbr</code> element whose semantics already support interpretation of the 'title' attribute as an expanded, more precise form of the content.

Experience has found that there are some cases in microformats where a number of publishers want to include a precisely accurate and parsable value for a property but do not want it to be visible in their page, even as a tooltip.

For example, full [[ISO8601]] datetimes may be confusing to readers of the page (as a tooltip or when read aloud by a screen reader), and enumerated values such as the <code>type</code> subproperty of hCard's <code>tel</code> property use US-English terms, which are not part of pages in any other language.

Since both of those scenarios have shown to be obstacles for a number of publishers, for these cases, and these alone, there exists a further extension of value-excerption. This extension allows the parsable form of the property to be published ‘silently’ immediately adjacent with the respective local visible content.

Here is an example, with the required use of a first child element with class name <code>value-title</code>:

<source lang=html4strict>
<p class='tel' lang='en-gb'>
<span class='type'>
<span class='value-title' title='cell'> </span>
mobile
</span>
<span class='value'>+44 7773 000 000</span>
</p>
</source>

The <samp>cell</samp> value is parsed for the 'type' subproperty, but <samp>mobile</samp> is presented to the user.

In the case of dates:

<source lang=html4strict>
<p class='dtstart'>
<span class='value-title' title='2009-03-14T16:28-0600'> </span>
March 14th 2009, around half-past four
</p>
</source>

A microformats parser will read the ISO8601 format datetime <samp>2009-03-14T16:28-0600</samp>, but users will only see <samp>March 14th 2009, around half-past four</samp>. Testing has shown that the ISO8601 datetime above does not get exposed to any user at all.

===Parsing machine-data <code>value-title</code>===

Browsers collapse the <code>value-title</code> span down to a width of <code>0</code>, effectively providing no visual rendering, whilst keeping the element in the DOM. With no physical dimensions, there is no ‘hover’ state, so no tooltip is revealed. Furthermore, the empty element is not passed to assistive technology layers such as VoiceOver. Screen readers do not read the contents of the title attribute of an empty <code>span</code> element.

We conducted [[value-excerption-value-title-test|thorough testing]] of these parsing behaviors to ensure accessibility.

''Note: Whilst the <code>value-title</code> element is more gracefully written without whitespace inner-text (or as self-closing <code><foo /></code> element in XHTML), current tools such as WYSIWYG editors and HTML-Tidy will erroneously discard such elements, resulting in parsable data being thrown away by some tools. As such, <code><span class='value-title'> </span></code>, including a single whitespace character between the opening and closing tag, is the required pattern for authors, at this time.''

Parsing this final <code>value-title</code> extension imposes some stricter restrictions on usage. These restrictions exist to reduce the impact of <abbr title="Don't Repeat Yourself">DRY</abbr> violations, reduce the opportunity for sites to spoof data, and encourage best practice for maintaining both forms of data accurately.

Where an element with class <code>value-title</code> is to be parsed as data for a property, and that element also contains no non-whitespace content (hereafter referred to as ‘empty’), the following rules apply:

* The ‘empty’ value-title element must be the '''first, non-whitespace child''' of the property element. That is, it should follow immediately after the property is declared, before the human-readable form, and without any additional nesting.
* The ‘empty’ value-title element can only be used for specific properties. Microformat specifications must explicitly state which properties may be used with this extension of the value-class-pattern.
* Where an ‘empty’ value-title element is to be used as the single property value, it must be the ''only'' such <code>value</code> content. That is, the first instance of a conforming <code>value-title</code> element overrides all other <code>value</code> and <code>value-title</code> siblings and/or cousins.
* Tools written to perform Conformance Testing and/or Validation of microformats ''should'' attempt to compare the machine-data and human legible forms of the property data, and advise authors if the forms do not match.

=== limited use of value-title ===
Due to the fact that the value-title pattern hides some amount of data which tends to be a machine-specific duplicate of data that is provided in the human readable content, there are two microformats [[principles]] being compromised: '''visibility''' and '''<abbr title="Don't Repeat Yourself">DRY</abbr>'''. Thus the applicability of this pattern is deliberately restricted to properties that have demonstrated through experience a need for it, with no known better alternative.

In general authors should:

# First, try to directly specify microformats property values inline (the most visible, no duplication),
# Then consider using the value-class pattern
## Including multiple value elements for date and time properties
# and then only if those methods are insufficient, consider the value-title pattern.

This document post-dates other microformat specifications, such that they may not yet indicate which properties permit use of this pattern. In the interim, '''only''' the following types of properties should allow the value-title pattern.

* ISO8601 date, datetime, timezone, and duration values
* Enumerated values (such as the hCard tel/email/adr 'type' subproperties)
* Co-ordinates (such as the [[geo]] 'latitude' and 'longitude' properties)
* Telephone number properties (e.g. the hCard 'tel' property)

The [[machine-data]] page has documentation of some of the properties of some specs which experience has shown need a solution like the value-title pattern.

There are some simple reference examples and tests for this pattern on [[value-class-pattern-tests]].

In future use, ''specification authors'' may inherit use of <code>value-title</code> by use of ISO8601 date and time formats, or reuse of other microformats, but specifications should _avoid_ introducing new data structures that depend on or encourage this pattern. New specifications are themselves expected to adhere to the principals of visibile data and <abbr>DRY</abbr>.

=== <abbr title='Frequently Asked Questions'>FAQ</abbr>===
This section is '''informative'''.

Frequently asked questions about the value-class-pattern. Once this section grows too big, we'll make a separate wiki page (like [[value-class-faq]]).

<div class='discussion'>
* '''Why use an 'empty' element? Why not embed data in the class attribute?'''
** The class attribute is inappropriate for embedded data values, as per the HTML4 specification, which states <code>class</code> is for ‘general purposing processing’, which is defined as ‘e.g. for identifying fields when extracting data from HTML pages into a database, translating HTML documents into other formats, etc.’. ‘General purpose processing’ does not extend to data itself. Furthermore, this method avoids inventing a new string pattern for embedding data.
* '''Why use an 'empty' element? Why not make up a new attribute, like ‘data’?'''
** Microformats exist and function in valid HTML4 and XHTML1. Those are the current standards for web development, and microformats exist for use ''now''. In the future, perhaps future revisions of HTML will offer up another solution. For now, this method has been tested against browsers, and creates a consistant document structure (where machine-form and human-form data are siblings).
* '''The <code>title</code> attribute should only be used for content!'''
** The <code>title</code> attribute _is_ used for content and is read by microformats parsers. This exists for cases where data cannot be parsed with sufficient precision from just the commonly published, visible information. This pattern allows both forms of content to be included, whilst keeping it invisible to human consumers.
</div>

You can also refer to the general [[faq|Microformats FAQ]] and [[principles]].

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

The following sites and pages have started marking up content with the value-class-pattern, and are thus good places to go for examples with real world content to test with implementations (i.e. parsers). If you use the value-class-pattern in your content, feel free to add it to the '''top''' of this list. Once the list grows too big, we'll make a separate wiki page (like [[value-class-examples-in-wild]]).

* [http://georgebrock.com/ George Brocklehurst's activity stream] and [http://blog.georgebrock.com/ blog] use "value-title" for hAtom <code>published</code> property
* [http://ben-ward.co.uk/ Ben Ward's home page] uses:
** "value-title" for hCard <code>bday</code> property
** "value-title" for hAtom <code>updated</code> property
* [http://microformats.org/ microformats.org] uses:
** "value-title" for hAtom <code>updated</code> property in [[http://microformats.org/ microformats.org blog postss]]]
** date and time value separation for hCalendar <code>dtstart</code> property in [[events|microformats.org recent and upcoming events wiki page]]

''Add your site/page(s) that use the value-class-pattern here, along with a brief description of what value-class-pattern features you use, with which microformat(s) and which of its/their properties.''

== Implementations ==

This section is '''informative'''.

The following implementations have been developed which either generate or parse value-class-pattern property values. If you have an value-class-pattern implementation, feel free to add it to the '''top''' of this list. Once the list grows too big, we'll make a separate wiki page (like [[value-class-implementations]]).

* [[Operator]] has *some* implementation of the value-class-pattern according to Michael Kaply, but precisely how much is implemented, for which properties (property types) and which microformats is not currently known.
* ... add your implementation(s) that parse or generate the value-class-pattern here, along with which features you support (hopefully all!) and note any limitations if any.

==Related Pages==
This section is '''informative'''.

* [[value-excerption-pattern-issues]]
* [[hcard#Value_excerpting|hCard: Value Excepting]]
* [[value-excerption-pattern-brainstorming]]
* [[machine-data|Machine Data in Microformats]]

value-excerption-value-title-test

2009-02-01T14:06:27Z

GeorgeBrock: /* Successful Tests */ Added results (phase 1 and 2) for Camino 1.6.6

<entry-title>Value Excerption Pattern: Parsing 'value' from an empty element</entry-title>
'''This page is targetted at those already experienced with microformats.'''

''Please carefully note, this page is about a pre-draft, experimental and unfinished microformats proposal. You '''cannot''' use this pattern on your live pages, it is '''not supported''' by any stable parser and you should not assume that this pattern will be finalized as-is! We're just asking for help in testing this thoroughly. '''Thank you'''.''
__TOC__
This is a special page to introduce and gather results to widespread testing of a '''proposed''' extension to the value-excerption pattern. See [[value-excerption-pattern-brainstorming#.E2.80.98value-title.E2.80.99|value excerption pattern brainstorming: value-title]] for the specific proposal.

This pattern can be used to resolve some long standing issues with including [[machine-data|machine-data in microformats]]; it's imperative we test thoroughly before adding it to any pattern specification. Following are a number of example tests. ''Please try them out''.

The pattern we're testing looks a little something like this. Those experienced with microformats should immediately see what we're trying to do:

<source lang=html4strict>
<p class='tel'>
<span class='type'>
<span class='value-title' title='cell'></span>
mobile
</span>
<span class='value'>+44 7773 000 000</span>
</p>
</source>

<source lang=html4strict>
<p class='dtstart'>
<span class='value-title' title='2009-01-06T22:54:00-0800'></span>
January 6th, in the evening
</p>
</source>

It allows you to include machine-form data alongside the human form, without polluting visible formatted content with undesired machine form data.

This covers cases where a microformat uses a fixed format of data that is either inappropriate for visible inclusion in a page (such as a full date-time and timezone string), or where an American-English keyword is needed — such as <code>cell</code> instead of ‘mobile’ in a British English page, or any number of non-English translations.

This pattern is based on rendering behavior in browsers whereby an empty element — that is one containing no text-nodes or other child elements — remains in the DOM tree (for parsing) but is not rendered visibly to a page. This allows an element to be included in the document with a <code>title</code> attribute (as in the example), but ''without'' a tooltip being exposed to users, and without the data being read out by screen readers.

You can use <code>value-title</code> on non-empty elements as well; whatever makes most sense to your publishing scenario. This page is dedicated to the empty-element version though, since that offers up the consumption unknowns.

Based on everything we know up to this point, we believe this pattern will work. But, it's wide ranging and the web is broad, and we want to be sure. Please, help us out testing this pattern proposal. Examples tests are below, please push them or your own variants into publishing systems, content management systems, editor applications and tools. Check that it comes out the other side with the data intact, and exposed (or hidden) as expected: Render it in desktop browsers, mobile browers, screen readers, in braille… ''anything you can test, we want to know about''! We need to see any quirks, oddities and so on.

Also, by all means provide thoughts on the publishing flow for this. An empty element is an uncommon structure outside of forms and scripts, but the reasoning is as follows: ''‘Machine formatted data’ is not metadata, it is content. Therefore, it's structurally appropriate to have it as a sibling to the human-formatted content.''

'''Note that valid HTML is a cornerstone of microformats'''. ''Inventing new attributes, depending on unstable drafts of HTML5, using non-standard DOCTYPEs or XML extensions is not an applicable option''. We're trying to achieve something as gracefully as we can within the limitations of HTML4, and without harming user experience.

==The proposed parsing rules==

The current, likely incomplete, parsing rules and restrictions for this pattern are as follows:

* Only one <code>value-title</code> element may be included as a child of a property. No splitting or concatenation, no combining with other value-excerption elements.
* An empty <code>value-title</code> element '''must''' be the ''first''-child of the property (not including any preceding whitespace). To alleviate the [[value-excerption-pattern-brainstorming#issues_2|negative impact of non-visible data]], the value should be as near as possible to declaring the property.
* The machine-data value ''must'' represent the same data as the visible text; the parent property ''must not'' contain arbitrary data. Validator tools will be encouraged to verify this where possible (for example, some programming languages have access to powerful date parsing algorithms that can compare human dates to the ISO form).
* The empty element can be ''any element'', but a generic <code>span</code> is most appropriate. You could use <code>b</code> if you want to save bytes, or an <code>input type=hidden</code> if it makes sense to you. That choice will not matter to parsers. You are in complete control of that publishing decision. As per usual µf documentation, <code>span</code> will be used for generic examples.
* The <code>value-title</code> property does not have to be empty. If you ''do'' want a tool-tip to expose a useful data-form, you can. e.g. <code><span class='value-title' title='2008'>last year</span></code> is valid too.

==Example Tests==

The following snippets are example tests for the new pattern. You can use them as is, or use them as a base for your own tests with your own content. If you write your own tests, please document them under ‘additional test cases’ so that any failing tests can be checked for validity.

===hAtom#1: An hAtom <code>published</code>/<code>updated</code> Property===

<source lang=html4strict>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<title>Value Excerption Pattern Test hAtom#1</title>
</head>
<body>
<div class="hentry">
<h1 class="entry-title">An introduction to Microformats</h1>
<p>
Published on <span class="published updated">
<span class="value-title" title="2009-01-09T11:33:00-0800"></span>
January 9th, around lunchtime</span>
by <span class="author vcard">
<a class="url fn" href="http://example.com">
Joe Blogger</a></span>.
</p>
<p class="entry-content">Wow, microformats are really useful! You can
learn loads about them on the
<a href="http://microformats.org/wiki">microformats wiki</a>.
</p>
</div>
</body>
</html>
</source>

===hCal#1: An hCalendar <code>dtstart</code>===

<source lang=html4strict>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<title>Value Excerption Pattern Test hCal#1</title>
</head>
<body>
<div class="vevent">
<h1 class="summary">Value Exception Test Day!</h1>
<p class="description">Come help <span class="organizer vcard">
<a class="fn url org" href="http://microformats.org">microformats.org</a>
</span> test a new value-excerption pattern for sanity and
robustness!
</p>
<p>Help out by running some tests at
<span class="dtstart">
<span class="value-title" title="2009-01-12T12:00:00-0800"></span>
midday on Monday January 12th</span>.
</p>
<p>See <a class="url" href="http://microformats.org/wiki/value-excerption-pattern-issues/empty-value-element-test">the
wiki</a> for more details!
</p>
</div>
</body>
</html>
</source>

===hCard#1: An hCard <abbr title="birthday"><code>bday</code></abbr>===

<source lang=html4strict>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<title>Value Excerption Pattern Test hCard#1</title>
</head>
<body>

<div class="vcard">
<h1 class="fn">Ben Ward</h1>
<p>Ben Ward's birthday is
<span class="bday">
<span class="value-title" title="1984-02-09"></span>
February 9th
</span>.
You should throw him a party! Or call his <span class="tel">
<span class="type"><span class="value-title" title="cell"></span>mobile</span>
on <span class="value">415.123.123</span></span> to wish him well!
</p>
</div>

</body>
</html>
</source>

===hAudio#1: An hAudio <code>duration</code>===

<source lang=html4strict>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<title>Value Excerption Pattern Test hAudio#1</title>
</head>
<body>
<h1>Song of the year?</h1>

<p class="haudio">Did you hear ‘<span class="fn">Heavy Water</span>’ on
<span class="contributor">Foals</span>
‘<span class="album">Antidodes</span>’ record
<span class="published">
<span class="value-title" title="2008"></span>
last year
</span>? It's
<span class="duration">
<span class="value-title" title="PT04M32S"></span>
4 and a half minutes long
</span>, you should make time to hear it!</p>
</div>

</body>
</html>
</source>

''If you believe there is an error in any of these tests, or in any others that people contribute, please post on the {{MicroformatsMailingList}}.''

==Evil Tests==

If you want to give existing microformat parsers a good run out, construct ‘evil’ tests using nesting, combination and interpolation of different microformats.

===hAtom + hCalendar===

<source lang=html4strict>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<title>Value Excerption Pattern Test hAtomhCalEvil#1</title>
</head>
<body>
<div class="hentry vevent">
<h1 class="entry-title summary">An introduction to Microformats</h1>
<p>
Published on <span class="published updated">
<span class="value-title" title="2009-01-09T11:33:00-0800"></span>
January 11th, late afternoon</span>
by <span class="author organizer vcard">
<a class="url fn" href="http://example.com">
Joe Blogger</a></span>.
</p>
<p class="entry-content description">
<span class="dtstart">
<span class="value-title" title="2009-01-14T19:00:00"></span>
this coming Wednesday at 7
</span> is not the date of a completely fictional microformats
event. If it existed, it would promise to be informative and get
you up to speed on microformats.org for 2009! Now you've
learned to work with microformats a little, why not attend and
get involved! Why not? Because this event is a test case, not
for real.
</p>
</div>
</body>
</html>
</source>

==Second Phase Test==

Following the first wave of example tests (above), we had a handful of failures in publishing tools caused by the requirement of using the empty span element. Tools (including the widespread HTML-Tidy) drop the <code>span</code>, thus throwing away the data. Thus, we have a second test to claim confirmation on, please. This version includes a single whitespace (space) character in the <code>value-title</code> span. The result of this is that the publishing tools that failed in the above example pass. We now need to confirm that the single item of whitespace will also collapse (we believe it does). Here's a rewrite of the first hAtom test from above, with the whitespace variation:

<source lang=html4strict>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<title>Value Excerption Pattern Test hAtom#1</title>
</head>
<body>
<div class="hentry">
<h1 class="entry-title">An introduction to Microformats</h1>
<p>
Published on <span class="published updated">
<span class="value-title" title="2009-01-09T11:33:00-0800"> </span>
January 9th, around lunchtime</span>
by <span class="author vcard">
<a class="url fn" href="http://example.com">
Joe Blogger</a></span>.
</p>
<p class="entry-content">Wow, microformats are really useful! You can
learn loads about them on the
<a href="http://microformats.org/wiki">microformats wiki</a>.
</p>
</div>
</body>
</html>
</source>

The WYSIWYG editors can also publish the original pattern using the <code>input type=hidden</code> element rather than a <code>span</code>, but we're keen to avoid prescribing mark-up to any publisher (especially mark-up of ‘elaborate’ semantics).

A second column has been added to the results to confirm each item that also passes with the inclusion of whitespace. Failures should be documented in the same place, please.

This test is also hosted on Ben Ward's domain, so you can run it right in your browser by going to [http://ben-ward.co.uk/microformats/value-excerption-pattern/hAtom2.html http://ben-ward.co.uk/microformats/value-excerption-pattern/hAtom2.html].

==Verifying the tests==

To verified a successfully passing test, you need to check for the following:

===In consumers (browsers, screen readers, etc.)===

* The empty element should appear in the page <abbr title='Document Object Model'>DOM</abbr>
* When hovering over and near the visible data, a tooltip displaying the machine-form ''must not'' be displayed.
** You can doubly verify this by opening you browser's DOM Inspector and confirming that the <code>value-title</code> element has a width of <samp>0</samp> (or <samp>0 px</samp>).
* When rendered to speech using assistive technology, the machine-form data ''must not'' be read aloud.
** Any variance in this behaviour with different verbosity settings should be noted too, please.

===In publishing tools===

* The tool allows you to create an empty span element
** The tool allows you to add <kbd>value-title</kbd> to the <code>class</code> attribute of this empty element.
** The tool allows you to add corresponding date to the <code>attribute</code> attribute of this empty element.
* The element remains available in the editor whilst other edits are made
* When the content is ‘published’ to the web, the empty element is present in the page output, and therefore in the DOM for the document.

==Response==

* Don't like the empty element? Don't like the use of the title attribute? '''Please file general issues concerning the proposed pattern on the main [[value-excerption-pattern-brainstorming#enabling_more_use_of_title_attributes|value excerption brainstorming page]]''', or discuss them on the {{MicroformatsMailingList}}.
* Add results of tests and responses to these tests themselves on ''this page''.

Misplaced responses will be moved, and having to do so will make [[User:BenWard|Ben]] growly, so, y'know, please try to keep the wiki tidy.

=== Please Also Try ===
Please also try the [[value-excerption-dt-separation-test]]. This is not either or. Ideally both will work and can be carried forward.

===Successful Tests===

List successfully tested environments here. Add new environments as new list items, and expand existing list items with your name and platform variants to indicate verified successes.

{|
|+ Results of tests across various publishing/rendering environments
|-
! Product
! <abbr title="Publishing or Consuming?">P/C?</abbr>
! Platforms
! Test By
! Notes
! <abbr title='Test 2 with Whitespace'>T2</abbr>
|-
| MediaWiki/Linux
| Publishing
| Safari 3.2.1 (Mac OSX 10.5)
| [[User:BenWard]]
| The empty <code>span</code> elements are maintained in <abbr title="MediaWiki">MW</abbr> output. Note that <code>a</code> elements in the tests get escaped by this MediaWiki install.
|-
| TinyMCE 3.2.1.1
| Publishing
| Safari 3.2.1 (Mac OSX 10.5)
| [[User:BenWard]]
| Fails when trying to publish empty element (see below)
| Pass
|-
| FCKEditor 2.6.4 Beta
| Publishing
| Safari 3.2.1 (Mac OSX 10.5)
| [[User:BenWard]]
| Fails when trying to publish empty element (see below)
| Pass
|-
| Safari 2.0.4
| Consuming
| Mac OSX 10.5
| [[User:GeorgeBrock]]
| Empty-span reamins in DOM. No tooltip.
| Pass
|-
| Safari 3.0.3
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:EmilyLewis]]
| No tooltip
|-
| Safari 3.2.1
| Consuming
| Mac OSX 10.5,
| [[User:BenWard]], [[User:EmilyLewis]]
| Empty-span remains in DOM. Web Inspector reports the element has width and height of ‘0px’. No tooltip due to zero-dimensions.
| Pass
|-
| Firefox 2.0
| Consuming
| Mac OSX 10.5
| [[User:GeorgeBrock]], [[User:BenWard]]
| Empty-span remains in DOM. Firebug reports the element has width of '0px' and height of ‘16px’. No tooltip due to zero-width.
| Pass
|-
| Firefox 3.0.x
| Consuming
| Mac OSX 10.5,
| [[User:BenWard]], [[User:EmilyLewis]]
| Empty-span remains in DOM. Firebug reports the element has width of '0px' and height of ‘16px’. No tooltip due to zero-width.
| Pass
|-
| Firefox 3.0.x
| Consuming
| Windows XP SP3,
| [[User:EmilyLewis]]
| no tooltip
|-
| Firefox 3.1ß1
| Consuming
| Mac OSX 10.5,
| [[User:BenWard]]
| Empty-span remains in DOM. No tooltip.
|-
| Opera 9.6
| Consuming
| Mac OSX 10.5.6
| [[User:EmilyLewis]]
| No tooltip
|-
| Opera 9.62
| Consuming
| Mac OSX 10.5, Windows XP SP3
| [[User:BenWard]], [[User:EmilyLewis]]
| Empty-span remains in DOM. Dragonfly reports the element has width of '0px' and height of ‘0px’. No tooltip due to zero-dimensions.
| Pass
|-
| Opera 10 Alpha
| Consuming
| Mac OSX 10.5
| [[User:BenWard]]
| Empty-span remains in DOM. Dragonfly reports the element has width of '0px' and height of ‘0px’. No tooltip due to zero-dimensions.
| Pass
|-
| Internet Explorer 5.2
| Consuming
| Mac OSX 10.5,
| [[User:BenWard]]
| No tooltip.
| Pass
|-
| Internet Explorer 6.0
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:GeorgeBrock]], [[User:EmilyLewis]]
| Empty-span remains in DOM (visible to Web Developer Toolbar, accessible from Javascript). No tooltip.
| Pass
|-
| Internet Explorer 7.0
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:GeorgeBrock]], [[User:EmilyLewis]]
| Empty-span remains in DOM (visible to Web Developer Toolbar, accessible from Javascript). No tooltip.
| Pass
|-
| Internet Explorer 8.0 beta 2
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:GeorgeBrock]]
| Empty-span remains in DOM. Developer Tools (built in to <abbr title="Internet Explorer 8 beta 2">IE8b2</abbr>) report the element has width of '0px' and height of '19px'. No tooltip due to zero-width.
| Pass
|-
| Camino 1.6.5
| Consuming
| Mac OSX 10.5.6
| [[User:EmilyLewis]]
| No tooltip
|-
| Camino 1.6.6
| Consuming
| Mac OSX 10.5.6
| [[User:GeorgeBrock]]
| Empty-span remains in DOM. [http://getfirebug.com/lite.html Firebug Lite] reports width of '0px' and height of '16px'. No tooltip due to zero-width.
| Pass
|-
| Flock 2.0.2
| Consuming
| Mac OSX 10.5.6
| [[User:EmilyLewis]]
| No tooltip
|-
| Flock 2.0.2
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:EmilyLewis]]
| No tooltip
|-
| Chrome 1.0.154.43
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:EmilyLewis]]
| No tooltip
|-
| BlackBerry Browser
| Consuming
| BlackBerry Storm OS 4.0.7.85 (leaked, non-official OS build from Verizon)
| [[User:EmilyLewis]]
| Tested in ‘BlackBerry mode’. No tooltip
|-
| MobileSafari 2.2
| Consuming
| iPhone OS 2.2
| [[User:EmilyLewis]], [[User:BenWard]]
| No tooltip
| Pass
|-
| IE Mobile 7.11
| Consuming
| Sprint HTC Mogul, OS: Windows Mobile 6.1
| [[User:EmilyLewis]]
| No tooltip
|-
| JAWS 10.0.512 (demo mode)
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:EmilyLewis]]
| No voice
|-
| Fire Vox (Firefox 3.0.5)
| Consuming
| Mac OSX 10.5.6
| [[User:EmilyLewis]]
| No voice
|-
| WebbIE (Thunder 1.43)
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:EmilyLewis]]
| No voice
|-
| VoiceOver (Safari 3.2.1)
| Consuming
| Mac OSX 10.5.6
| [[User:EmilyLewis]], [[User:BenWard]]
| No voice. When interacting with elements, cannot focus on the empty-span.
| Pass
|-
|}

===Failed Tests===

For failures, please provide as much information as you can. The precise impact of the error, whether the behavior could be regarded as a bug in the software you're testing, whether it works in subsequent releases, whether you changed any settings in the software to produce the result, and if so, whether enabling/disabling that setting should be regarded a showstopper if this pattern were certified.

Since we want more detail, please expand failures into headed sections rather than cramming into a table.

For example, take this entirely plausible scenario as a template:

====Example: Fake Publisher 3.1ß====
; Platform
: Windows Vista
; Test By
: [[User:BenWard]]
; Description
: When trying to enter an empty span in my <abbr title="Hypertext Markup Language">HTML</abbr> editor, which I wrote myself whilst I was high, the application immediately crashes, performs <code>rm -rf /</code> on all UNIX boxes connected to my local network (which also appears to cause Android phones within Bluetooth range to do the same…), and then causes all attached peripherals to combust. I was not able to reproduce, as my house was now on fire. I think using a self closing XHTML tag instead might work-around the problem because as we know, it's been proved by Real Scienticians that XML is always better than HTML. Alternatively, it may be a bug in the beta software.
; Notes
: This is a beta release, and a bug has been filed.
: This product has a known history of flammability bugs.
: The user must explicitly enable the ‘Endanger My Life’ checkbox under the ‘Advanced Mislabelled Checkboxes’ tab of the ‘Complicated Preferences’ preferences pane.
: You get the idea.

====Browser <abbr title="What you see is what you get">WYSIWYG</abbr> editor: [http://tinymce.moxiecode.com/ TinyMCE 3.2.1.1]====
; Platform
: Firefox 3.0 on Mac OSX 10.5
; Test By
: [[User:GeorgeBrock]]
; Description
: Empty spans entered using TinyMCE's source editor are removed when switching back to the default WYSIWYG view.
: This is not a bug with TinyMCE, the editor is designed to remove empty instances of most elements by default. The handling of empty elements can be changed by modifying the [http://wiki.moxiecode.com/index.php/TinyMCE:Configuration/valid_elements valid-elements setting] (e.g. change <code>-span</code> to <code>span</code> and empty spans will no longer be removed), however settings can only be changed by modifying the source code of the page that contains the TinyMCE instance, so it is likely that some users will not be able to apply this fix.
; Notes
: This behaviour can be easily reproduced using the online [http://tinymce.moxiecode.com/examples/full.php TinyMCE examples].
: TinyMCE is the default WYSIWYG editor in WordPress[http://codex.wordpress.org/TinyMCE].
: With a single whitespace character (‘space’), the <code>span</code> is preserved, but yet still seems to collapse in Safari. Will write a follow-up test.--[[User:BenWard|BenWard]] 23:11, 20 January 2009 (UTC)
: You ''can'' publish this pattern using the <code>input type='hidden' class='value-title' title='2009-01-20'</code> hinted above. Semantically odd, although it's been suggested on µf lists before. Publishing workaround exists through element agnosticism. --[[User:BenWard|BenWard]] 23:11, 20 January 2009 (UTC)

====Browser <abbr title="What you see is what you get">WYSIWYG</abbr> editor: [http://www.fckeditor.net/ FCKEditor 2.6.4 Beta]====
; Platform
: Firefox 3.0 on Mac OSX 10.5
; Test By
: [[User:GeorgeBrock]]
; Description
: Empty spans entered using FCKEditor's source editor are removed when switching back to the default WYSIWYG view or submitting the form that contains the FCKEditor instance.
; Notes
: This behaviour can be easily reproduced using the online [http://www.fckeditor.net/demo FCKEditor demo].
: FCKEditor is used by various content management systems, frameworks and applications[http://www.fckeditor.net/whosusing].
: With a single whitespace character (‘space’), the <code>span</code> is preserved, but yet still seems to collapse in Safari. Will write a follow-up test.--[[User:BenWard|BenWard]] 23:12, 20 January 2009 (UTC)
: You ''can'' publish this pattern using the <code>input type='hidden' class='value-title' title='2009-01-20'</code> mentioned above. --[[User:BenWard|BenWard]] 23:12, 20 January 2009 (UTC)
: This issue does not effect FCKEditor instances that use the Placeholders plugin (this plugin comes with FCKEditor, enable it using <code>FCKConfig.Plugins.Add('placeholder')</code>). Examining the Placeholders plugin code may yield an easier work-around than including the plugin (I had a quick look but didn't see anything that was obviously responsible for allowing empty spans) -[[User:GeorgeBrock|GeorgeBrock]] 23:20, 20 January 2009 (UTC)



===General Test Feedback===
<div class='discussion'>
* Any general feedback you have on this test is most welcome. However, if you have issues with the pattern or alternate suggestions, please file them on the main [[value-excerption-pattern-issues]] page. Also, please remember to sign your comments with <nowiki>—~~~~</nowiki> —[[User:BenWard|BenWard]] 00:12, 9 January 2009 (UTC)
* … 
** … 
</div>

==Related Pages==
* [[value-excerption-pattern]]
* [[value-excerption-pattern-issues]]
* [[value-excerption-pattern-brainstorming]]
* [[value-excerption-dt-separation-test]]

value-excerption-value-title-test

2009-02-01T13:53:00Z

GeorgeBrock: /* Successful Tests */ 2nd phase test results for Safari 2 and IE6,7,8b2

<entry-title>Value Excerption Pattern: Parsing 'value' from an empty element</entry-title>
'''This page is targetted at those already experienced with microformats.'''

''Please carefully note, this page is about a pre-draft, experimental and unfinished microformats proposal. You '''cannot''' use this pattern on your live pages, it is '''not supported''' by any stable parser and you should not assume that this pattern will be finalized as-is! We're just asking for help in testing this thoroughly. '''Thank you'''.''
__TOC__
This is a special page to introduce and gather results to widespread testing of a '''proposed''' extension to the value-excerption pattern. See [[value-excerption-pattern-brainstorming#.E2.80.98value-title.E2.80.99|value excerption pattern brainstorming: value-title]] for the specific proposal.

This pattern can be used to resolve some long standing issues with including [[machine-data|machine-data in microformats]]; it's imperative we test thoroughly before adding it to any pattern specification. Following are a number of example tests. ''Please try them out''.

The pattern we're testing looks a little something like this. Those experienced with microformats should immediately see what we're trying to do:

<source lang=html4strict>
<p class='tel'>
<span class='type'>
<span class='value-title' title='cell'></span>
mobile
</span>
<span class='value'>+44 7773 000 000</span>
</p>
</source>

<source lang=html4strict>
<p class='dtstart'>
<span class='value-title' title='2009-01-06T22:54:00-0800'></span>
January 6th, in the evening
</p>
</source>

It allows you to include machine-form data alongside the human form, without polluting visible formatted content with undesired machine form data.

This covers cases where a microformat uses a fixed format of data that is either inappropriate for visible inclusion in a page (such as a full date-time and timezone string), or where an American-English keyword is needed — such as <code>cell</code> instead of ‘mobile’ in a British English page, or any number of non-English translations.

This pattern is based on rendering behavior in browsers whereby an empty element — that is one containing no text-nodes or other child elements — remains in the DOM tree (for parsing) but is not rendered visibly to a page. This allows an element to be included in the document with a <code>title</code> attribute (as in the example), but ''without'' a tooltip being exposed to users, and without the data being read out by screen readers.

You can use <code>value-title</code> on non-empty elements as well; whatever makes most sense to your publishing scenario. This page is dedicated to the empty-element version though, since that offers up the consumption unknowns.

Based on everything we know up to this point, we believe this pattern will work. But, it's wide ranging and the web is broad, and we want to be sure. Please, help us out testing this pattern proposal. Examples tests are below, please push them or your own variants into publishing systems, content management systems, editor applications and tools. Check that it comes out the other side with the data intact, and exposed (or hidden) as expected: Render it in desktop browsers, mobile browers, screen readers, in braille… ''anything you can test, we want to know about''! We need to see any quirks, oddities and so on.

Also, by all means provide thoughts on the publishing flow for this. An empty element is an uncommon structure outside of forms and scripts, but the reasoning is as follows: ''‘Machine formatted data’ is not metadata, it is content. Therefore, it's structurally appropriate to have it as a sibling to the human-formatted content.''

'''Note that valid HTML is a cornerstone of microformats'''. ''Inventing new attributes, depending on unstable drafts of HTML5, using non-standard DOCTYPEs or XML extensions is not an applicable option''. We're trying to achieve something as gracefully as we can within the limitations of HTML4, and without harming user experience.

==The proposed parsing rules==

The current, likely incomplete, parsing rules and restrictions for this pattern are as follows:

* Only one <code>value-title</code> element may be included as a child of a property. No splitting or concatenation, no combining with other value-excerption elements.
* An empty <code>value-title</code> element '''must''' be the ''first''-child of the property (not including any preceding whitespace). To alleviate the [[value-excerption-pattern-brainstorming#issues_2|negative impact of non-visible data]], the value should be as near as possible to declaring the property.
* The machine-data value ''must'' represent the same data as the visible text; the parent property ''must not'' contain arbitrary data. Validator tools will be encouraged to verify this where possible (for example, some programming languages have access to powerful date parsing algorithms that can compare human dates to the ISO form).
* The empty element can be ''any element'', but a generic <code>span</code> is most appropriate. You could use <code>b</code> if you want to save bytes, or an <code>input type=hidden</code> if it makes sense to you. That choice will not matter to parsers. You are in complete control of that publishing decision. As per usual µf documentation, <code>span</code> will be used for generic examples.
* The <code>value-title</code> property does not have to be empty. If you ''do'' want a tool-tip to expose a useful data-form, you can. e.g. <code><span class='value-title' title='2008'>last year</span></code> is valid too.

==Example Tests==

The following snippets are example tests for the new pattern. You can use them as is, or use them as a base for your own tests with your own content. If you write your own tests, please document them under ‘additional test cases’ so that any failing tests can be checked for validity.

===hAtom#1: An hAtom <code>published</code>/<code>updated</code> Property===

<source lang=html4strict>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<title>Value Excerption Pattern Test hAtom#1</title>
</head>
<body>
<div class="hentry">
<h1 class="entry-title">An introduction to Microformats</h1>
<p>
Published on <span class="published updated">
<span class="value-title" title="2009-01-09T11:33:00-0800"></span>
January 9th, around lunchtime</span>
by <span class="author vcard">
<a class="url fn" href="http://example.com">
Joe Blogger</a></span>.
</p>
<p class="entry-content">Wow, microformats are really useful! You can
learn loads about them on the
<a href="http://microformats.org/wiki">microformats wiki</a>.
</p>
</div>
</body>
</html>
</source>

===hCal#1: An hCalendar <code>dtstart</code>===

<source lang=html4strict>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<title>Value Excerption Pattern Test hCal#1</title>
</head>
<body>
<div class="vevent">
<h1 class="summary">Value Exception Test Day!</h1>
<p class="description">Come help <span class="organizer vcard">
<a class="fn url org" href="http://microformats.org">microformats.org</a>
</span> test a new value-excerption pattern for sanity and
robustness!
</p>
<p>Help out by running some tests at
<span class="dtstart">
<span class="value-title" title="2009-01-12T12:00:00-0800"></span>
midday on Monday January 12th</span>.
</p>
<p>See <a class="url" href="http://microformats.org/wiki/value-excerption-pattern-issues/empty-value-element-test">the
wiki</a> for more details!
</p>
</div>
</body>
</html>
</source>

===hCard#1: An hCard <abbr title="birthday"><code>bday</code></abbr>===

<source lang=html4strict>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<title>Value Excerption Pattern Test hCard#1</title>
</head>
<body>

<div class="vcard">
<h1 class="fn">Ben Ward</h1>
<p>Ben Ward's birthday is
<span class="bday">
<span class="value-title" title="1984-02-09"></span>
February 9th
</span>.
You should throw him a party! Or call his <span class="tel">
<span class="type"><span class="value-title" title="cell"></span>mobile</span>
on <span class="value">415.123.123</span></span> to wish him well!
</p>
</div>

</body>
</html>
</source>

===hAudio#1: An hAudio <code>duration</code>===

<source lang=html4strict>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<title>Value Excerption Pattern Test hAudio#1</title>
</head>
<body>
<h1>Song of the year?</h1>

<p class="haudio">Did you hear ‘<span class="fn">Heavy Water</span>’ on
<span class="contributor">Foals</span>
‘<span class="album">Antidodes</span>’ record
<span class="published">
<span class="value-title" title="2008"></span>
last year
</span>? It's
<span class="duration">
<span class="value-title" title="PT04M32S"></span>
4 and a half minutes long
</span>, you should make time to hear it!</p>
</div>

</body>
</html>
</source>

''If you believe there is an error in any of these tests, or in any others that people contribute, please post on the {{MicroformatsMailingList}}.''

==Evil Tests==

If you want to give existing microformat parsers a good run out, construct ‘evil’ tests using nesting, combination and interpolation of different microformats.

===hAtom + hCalendar===

<source lang=html4strict>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<title>Value Excerption Pattern Test hAtomhCalEvil#1</title>
</head>
<body>
<div class="hentry vevent">
<h1 class="entry-title summary">An introduction to Microformats</h1>
<p>
Published on <span class="published updated">
<span class="value-title" title="2009-01-09T11:33:00-0800"></span>
January 11th, late afternoon</span>
by <span class="author organizer vcard">
<a class="url fn" href="http://example.com">
Joe Blogger</a></span>.
</p>
<p class="entry-content description">
<span class="dtstart">
<span class="value-title" title="2009-01-14T19:00:00"></span>
this coming Wednesday at 7
</span> is not the date of a completely fictional microformats
event. If it existed, it would promise to be informative and get
you up to speed on microformats.org for 2009! Now you've
learned to work with microformats a little, why not attend and
get involved! Why not? Because this event is a test case, not
for real.
</p>
</div>
</body>
</html>
</source>

==Second Phase Test==

Following the first wave of example tests (above), we had a handful of failures in publishing tools caused by the requirement of using the empty span element. Tools (including the widespread HTML-Tidy) drop the <code>span</code>, thus throwing away the data. Thus, we have a second test to claim confirmation on, please. This version includes a single whitespace (space) character in the <code>value-title</code> span. The result of this is that the publishing tools that failed in the above example pass. We now need to confirm that the single item of whitespace will also collapse (we believe it does). Here's a rewrite of the first hAtom test from above, with the whitespace variation:

<source lang=html4strict>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<title>Value Excerption Pattern Test hAtom#1</title>
</head>
<body>
<div class="hentry">
<h1 class="entry-title">An introduction to Microformats</h1>
<p>
Published on <span class="published updated">
<span class="value-title" title="2009-01-09T11:33:00-0800"> </span>
January 9th, around lunchtime</span>
by <span class="author vcard">
<a class="url fn" href="http://example.com">
Joe Blogger</a></span>.
</p>
<p class="entry-content">Wow, microformats are really useful! You can
learn loads about them on the
<a href="http://microformats.org/wiki">microformats wiki</a>.
</p>
</div>
</body>
</html>
</source>

The WYSIWYG editors can also publish the original pattern using the <code>input type=hidden</code> element rather than a <code>span</code>, but we're keen to avoid prescribing mark-up to any publisher (especially mark-up of ‘elaborate’ semantics).

A second column has been added to the results to confirm each item that also passes with the inclusion of whitespace. Failures should be documented in the same place, please.

This test is also hosted on Ben Ward's domain, so you can run it right in your browser by going to [http://ben-ward.co.uk/microformats/value-excerption-pattern/hAtom2.html http://ben-ward.co.uk/microformats/value-excerption-pattern/hAtom2.html].

==Verifying the tests==

To verified a successfully passing test, you need to check for the following:

===In consumers (browsers, screen readers, etc.)===

* The empty element should appear in the page <abbr title='Document Object Model'>DOM</abbr>
* When hovering over and near the visible data, a tooltip displaying the machine-form ''must not'' be displayed.
** You can doubly verify this by opening you browser's DOM Inspector and confirming that the <code>value-title</code> element has a width of <samp>0</samp> (or <samp>0 px</samp>).
* When rendered to speech using assistive technology, the machine-form data ''must not'' be read aloud.
** Any variance in this behaviour with different verbosity settings should be noted too, please.

===In publishing tools===

* The tool allows you to create an empty span element
** The tool allows you to add <kbd>value-title</kbd> to the <code>class</code> attribute of this empty element.
** The tool allows you to add corresponding date to the <code>attribute</code> attribute of this empty element.
* The element remains available in the editor whilst other edits are made
* When the content is ‘published’ to the web, the empty element is present in the page output, and therefore in the DOM for the document.

==Response==

* Don't like the empty element? Don't like the use of the title attribute? '''Please file general issues concerning the proposed pattern on the main [[value-excerption-pattern-brainstorming#enabling_more_use_of_title_attributes|value excerption brainstorming page]]''', or discuss them on the {{MicroformatsMailingList}}.
* Add results of tests and responses to these tests themselves on ''this page''.

Misplaced responses will be moved, and having to do so will make [[User:BenWard|Ben]] growly, so, y'know, please try to keep the wiki tidy.

=== Please Also Try ===
Please also try the [[value-excerption-dt-separation-test]]. This is not either or. Ideally both will work and can be carried forward.

===Successful Tests===

List successfully tested environments here. Add new environments as new list items, and expand existing list items with your name and platform variants to indicate verified successes.

{|
|+ Results of tests across various publishing/rendering environments
|-
! Product
! <abbr title="Publishing or Consuming?">P/C?</abbr>
! Platforms
! Test By
! Notes
! <abbr title='Test 2 with Whitespace'>T2</abbr>
|-
| MediaWiki/Linux
| Publishing
| Safari 3.2.1 (Mac OSX 10.5)
| [[User:BenWard]]
| The empty <code>span</code> elements are maintained in <abbr title="MediaWiki">MW</abbr> output. Note that <code>a</code> elements in the tests get escaped by this MediaWiki install.
|-
| TinyMCE 3.2.1.1
| Publishing
| Safari 3.2.1 (Mac OSX 10.5)
| [[User:BenWard]]
| Fails when trying to publish empty element (see below)
| Pass
|-
| FCKEditor 2.6.4 Beta
| Publishing
| Safari 3.2.1 (Mac OSX 10.5)
| [[User:BenWard]]
| Fails when trying to publish empty element (see below)
| Pass
|-
| Safari 2.0.4
| Consuming
| Mac OSX 10.5
| [[User:GeorgeBrock]]
| Empty-span reamins in DOM. No tooltip.
| Pass
|-
| Safari 3.0.3
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:EmilyLewis]]
| No tooltip
|-
| Safari 3.2.1
| Consuming
| Mac OSX 10.5,
| [[User:BenWard]], [[User:EmilyLewis]]
| Empty-span remains in DOM. Web Inspector reports the element has width and height of ‘0px’. No tooltip due to zero-dimensions.
| Pass
|-
| Firefox 2.0
| Consuming
| Mac OSX 10.5
| [[User:GeorgeBrock]], [[User:BenWard]]
| Empty-span remains in DOM. Firebug reports the element has width of '0px' and height of ‘16px’. No tooltip due to zero-width.
| Pass
|-
| Firefox 3.0.x
| Consuming
| Mac OSX 10.5,
| [[User:BenWard]], [[User:EmilyLewis]]
| Empty-span remains in DOM. Firebug reports the element has width of '0px' and height of ‘16px’. No tooltip due to zero-width.
| Pass
|-
| Firefox 3.0.x
| Consuming
| Windows XP SP3,
| [[User:EmilyLewis]]
| no tooltip
|-
| Firefox 3.1ß1
| Consuming
| Mac OSX 10.5,
| [[User:BenWard]]
| Empty-span remains in DOM. No tooltip.
|-
| Opera 9.6
| Consuming
| Mac OSX 10.5.6
| [[User:EmilyLewis]]
| No tooltip
|-
| Opera 9.62
| Consuming
| Mac OSX 10.5, Windows XP SP3
| [[User:BenWard]], [[User:EmilyLewis]]
| Empty-span remains in DOM. Dragonfly reports the element has width of '0px' and height of ‘0px’. No tooltip due to zero-dimensions.
| Pass
|-
| Opera 10 Alpha
| Consuming
| Mac OSX 10.5
| [[User:BenWard]]
| Empty-span remains in DOM. Dragonfly reports the element has width of '0px' and height of ‘0px’. No tooltip due to zero-dimensions.
| Pass
|-
| Internet Explorer 5.2
| Consuming
| Mac OSX 10.5,
| [[User:BenWard]]
| No tooltip.
| Pass
|-
| Internet Explorer 6.0
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:GeorgeBrock]], [[User:EmilyLewis]]
| Empty-span remains in DOM (visible to Web Developer Toolbar, accessible from Javascript). No tooltip.
| Pass
|-
| Internet Explorer 7.0
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:GeorgeBrock]], [[User:EmilyLewis]]
| Empty-span remains in DOM (visible to Web Developer Toolbar, accessible from Javascript). No tooltip.
| Pass
|-
| Internet Explorer 8.0 beta 2
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:GeorgeBrock]]
| Empty-span remains in DOM. Developer Tools (built in to <abbr title="Internet Explorer 8 beta 2">IE8b2</abbr>) report the element has width of '0px' and height of '19px'. No tooltip due to zero-width.
| Pass
|-
| Camino 1.6.5
| Consuming
| Mac OSX 10.5.6
| [[User:EmilyLewis]]
| No tooltip
|-
| Flock 2.0.2
| Consuming
| Mac OSX 10.5.6
| [[User:EmilyLewis]]
| No tooltip
|-
| Flock 2.0.2
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:EmilyLewis]]
| No tooltip
|-
| Chrome 1.0.154.43
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:EmilyLewis]]
| No tooltip
|-
| BlackBerry Browser
| Consuming
| BlackBerry Storm OS 4.0.7.85 (leaked, non-official OS build from Verizon)
| [[User:EmilyLewis]]
| Tested in ‘BlackBerry mode’. No tooltip
|-
| MobileSafari 2.2
| Consuming
| iPhone OS 2.2
| [[User:EmilyLewis]], [[User:BenWard]]
| No tooltip
| Pass
|-
| IE Mobile 7.11
| Consuming
| Sprint HTC Mogul, OS: Windows Mobile 6.1
| [[User:EmilyLewis]]
| No tooltip
|-
| JAWS 10.0.512 (demo mode)
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:EmilyLewis]]
| No voice
|-
| Fire Vox (Firefox 3.0.5)
| Consuming
| Mac OSX 10.5.6
| [[User:EmilyLewis]]
| No voice
|-
| WebbIE (Thunder 1.43)
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:EmilyLewis]]
| No voice
|-
| VoiceOver (Safari 3.2.1)
| Consuming
| Mac OSX 10.5.6
| [[User:EmilyLewis]], [[User:BenWard]]
| No voice. When interacting with elements, cannot focus on the empty-span.
| Pass
|-
|}

===Failed Tests===

For failures, please provide as much information as you can. The precise impact of the error, whether the behavior could be regarded as a bug in the software you're testing, whether it works in subsequent releases, whether you changed any settings in the software to produce the result, and if so, whether enabling/disabling that setting should be regarded a showstopper if this pattern were certified.

Since we want more detail, please expand failures into headed sections rather than cramming into a table.

For example, take this entirely plausible scenario as a template:

====Example: Fake Publisher 3.1ß====
; Platform
: Windows Vista
; Test By
: [[User:BenWard]]
; Description
: When trying to enter an empty span in my <abbr title="Hypertext Markup Language">HTML</abbr> editor, which I wrote myself whilst I was high, the application immediately crashes, performs <code>rm -rf /</code> on all UNIX boxes connected to my local network (which also appears to cause Android phones within Bluetooth range to do the same…), and then causes all attached peripherals to combust. I was not able to reproduce, as my house was now on fire. I think using a self closing XHTML tag instead might work-around the problem because as we know, it's been proved by Real Scienticians that XML is always better than HTML. Alternatively, it may be a bug in the beta software.
; Notes
: This is a beta release, and a bug has been filed.
: This product has a known history of flammability bugs.
: The user must explicitly enable the ‘Endanger My Life’ checkbox under the ‘Advanced Mislabelled Checkboxes’ tab of the ‘Complicated Preferences’ preferences pane.
: You get the idea.

====Browser <abbr title="What you see is what you get">WYSIWYG</abbr> editor: [http://tinymce.moxiecode.com/ TinyMCE 3.2.1.1]====
; Platform
: Firefox 3.0 on Mac OSX 10.5
; Test By
: [[User:GeorgeBrock]]
; Description
: Empty spans entered using TinyMCE's source editor are removed when switching back to the default WYSIWYG view.
: This is not a bug with TinyMCE, the editor is designed to remove empty instances of most elements by default. The handling of empty elements can be changed by modifying the [http://wiki.moxiecode.com/index.php/TinyMCE:Configuration/valid_elements valid-elements setting] (e.g. change <code>-span</code> to <code>span</code> and empty spans will no longer be removed), however settings can only be changed by modifying the source code of the page that contains the TinyMCE instance, so it is likely that some users will not be able to apply this fix.
; Notes
: This behaviour can be easily reproduced using the online [http://tinymce.moxiecode.com/examples/full.php TinyMCE examples].
: TinyMCE is the default WYSIWYG editor in WordPress[http://codex.wordpress.org/TinyMCE].
: With a single whitespace character (‘space’), the <code>span</code> is preserved, but yet still seems to collapse in Safari. Will write a follow-up test.--[[User:BenWard|BenWard]] 23:11, 20 January 2009 (UTC)
: You ''can'' publish this pattern using the <code>input type='hidden' class='value-title' title='2009-01-20'</code> hinted above. Semantically odd, although it's been suggested on µf lists before. Publishing workaround exists through element agnosticism. --[[User:BenWard|BenWard]] 23:11, 20 January 2009 (UTC)

====Browser <abbr title="What you see is what you get">WYSIWYG</abbr> editor: [http://www.fckeditor.net/ FCKEditor 2.6.4 Beta]====
; Platform
: Firefox 3.0 on Mac OSX 10.5
; Test By
: [[User:GeorgeBrock]]
; Description
: Empty spans entered using FCKEditor's source editor are removed when switching back to the default WYSIWYG view or submitting the form that contains the FCKEditor instance.
; Notes
: This behaviour can be easily reproduced using the online [http://www.fckeditor.net/demo FCKEditor demo].
: FCKEditor is used by various content management systems, frameworks and applications[http://www.fckeditor.net/whosusing].
: With a single whitespace character (‘space’), the <code>span</code> is preserved, but yet still seems to collapse in Safari. Will write a follow-up test.--[[User:BenWard|BenWard]] 23:12, 20 January 2009 (UTC)
: You ''can'' publish this pattern using the <code>input type='hidden' class='value-title' title='2009-01-20'</code> mentioned above. --[[User:BenWard|BenWard]] 23:12, 20 January 2009 (UTC)
: This issue does not effect FCKEditor instances that use the Placeholders plugin (this plugin comes with FCKEditor, enable it using <code>FCKConfig.Plugins.Add('placeholder')</code>). Examining the Placeholders plugin code may yield an easier work-around than including the plugin (I had a quick look but didn't see anything that was obviously responsible for allowing empty spans) -[[User:GeorgeBrock|GeorgeBrock]] 23:20, 20 January 2009 (UTC)



===General Test Feedback===
<div class='discussion'>
* Any general feedback you have on this test is most welcome. However, if you have issues with the pattern or alternate suggestions, please file them on the main [[value-excerption-pattern-issues]] page. Also, please remember to sign your comments with <nowiki>—~~~~</nowiki> —[[User:BenWard|BenWard]] 00:12, 9 January 2009 (UTC)
* … 
** … 
</div>

==Related Pages==
* [[value-excerption-pattern]]
* [[value-excerption-pattern-issues]]
* [[value-excerption-pattern-brainstorming]]
* [[value-excerption-dt-separation-test]]

value-excerption-value-title-test

2009-01-20T23:20:57Z

GeorgeBrock: /* Browser WYSIWYG editor: FCKEditor 2.6.4 Beta */ Added work around for FCKEditor empty span issues

<entry-title>Value Excerption Pattern: Parsing 'value' from an empty element</entry-title>
'''This page is targetted at those already experienced with microformats.'''

''Please carefully note, this page is about a pre-draft, experimental and unfinished microformats proposal. You '''cannot''' use this pattern on your live pages, it is '''not supported''' by any stable parser and you should not assume that this pattern will be finalized as-is! We're just asking for help in testing this thoroughly. '''Thank you'''.''
__TOC__
This is a special page to introduce and gather results to widespread testing of a '''proposed''' extension to the value-excerption pattern.

This pattern can be used to resolve some long standing issues with including [[machine-data|machine-data in microformats]]; it's imperative we test thoroughly before adding it to any pattern specification. Following are a number of example tests. ''Please try them out''.

The pattern we're testing looks a little something like this. Those experienced with microformats should immediately see what we're trying to do:

<source lang=html4strict>
<p class='tel'>
<span class='type'>
<span class='value-title' title='cell'></span>
mobile
</span>
<span class='value'>+44 7773 000 000</span>
</p>
</source>

<source lang=html4strict>
<p class='dtstart'>
<span class='value-title' title='2009-01-06T22:54:00-0800'></span>
January 6th, in the evening
</p>
</source>

It allows you to include machine-form data alongside the human form, without polluting visible formatted content with undesired machine form data.

This covers cases where a microformat uses a fixed format of data that is either inappropriate for visible inclusion in a page (such as a full date-time and timezone string), or where an American-English keyword is needed — such as <code>cell</code> instead of ‘mobile’ in a British English page, or any number of non-English translations.

This pattern is based on rendering behavior in browsers whereby an empty element — that is one containing no text-nodes or other child elements — remains in the DOM tree (for parsing) but is not rendered visibly to a page. This allows an element to be included in the document with a <code>title</code> attribute (as in the example), but ''without'' a tooltip being exposed to users, and without the data being read out by screen readers.

You can use <code>value-title</code> on non-empty elements as well; whatever makes most sense to your publishing scenario. This page is dedicated to the empty-element version though, since that offers up the consumption unknowns.

Based on everything we know up to this point, we believe this pattern will work. But, it's wide ranging and the web is broad, and we want to be sure. Please, help us out testing this pattern proposal. Examples tests are below, please push them or your own variants into publishing systems, content management systems, editor applications and tools. Check that it comes out the other side with the data intact, and exposed (or hidden) as expected: Render it in desktop browsers, mobile browers, screen readers, in braille… ''anything you can test, we want to know about''! We need to see any quirks, oddities and so on.

Also, by all means provide thoughts on the publishing flow for this. An empty element is an uncommon structure outside of forms and scripts, but the reasoning is as follows: ''‘Machine formatted data’ is not metadata, it is content. Therefore, it's structurally appropriate to have it as a sibling to the human-formatted content.''

'''Note that valid HTML is a cornerstone of microformats'''. ''Inventing new attributes, depending on unstable drafts of HTML5, using non-standard DOCTYPEs or XML extensions is not an applicable option''. We're trying to achieve something as gracefully as we can within the limitations of HTML4, and without harming user experience.

==The proposed parsing rules==

The current, likely incomplete, parsing rules and restrictions for this pattern are as follows:

* Only one <code>value-title</code> element may be included as a child of a property. No splitting or concatenation, no combining with other value-excerption elements.
* An empty <code>value-title</code> element '''must''' be the ''first''-child of the property (not including any preceding whitespace). To alleviate the [[value-excerption-pattern-brainstorming#issues_2|negative impact of non-visible data]], the value should be as near as possible to declaring the property.
* The machine-data value ''must'' represent the same data as the visible text; the parent property ''must not'' contain arbitrary data. Validator tools will be encouraged to verify this where possible (for example, some programming languages have access to powerful date parsing algorithms that can compare human dates to the ISO form).
* The empty element can be ''any element'', but a generic <code>span</code> is most appropriate. You could use <code>b</code> if you want to save bytes, or an <code>input type=hidden</code> if it makes sense to you. That choice will not matter to parsers. You are in complete control of that publishing decision. As per usual µf documentation, <code>span</code> will be used for generic examples.
* The <code>value-title</code> property does not have to be empty. If you ''do'' want a tool-tip to expose a useful data-form, you can. e.g. <code><span class='value-title' title='2008'>last year</span></code> is valid too.

==Example Tests==

The following snippets are example tests for the new pattern. You can use them as is, or use them as a base for your own tests with your own content. If you write your own tests, please document them under ‘additional test cases’ so that any failing tests can be checked for validity.

===hAtom#1: An hAtom <code>published</code>/<code>updated</code> Property===

<source lang=html4strict>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<title>Value Excerption Pattern Test hAtom#1</title>
</head>
<body>
<div class="hentry">
<h1 class="entry-title">An introduction to Microformats</h1>
<p>
Published on <span class="published updated">
<span class="value-title" title="2009-01-09T11:33:00-0800"></span>
January 9th, around lunchtime</span>
by <span class="author vcard">
<a class="url fn" href="http://example.com">
Joe Blogger</a></span>.
</p>
<p class="entry-content">Wow, microformats are really useful! You can
learn loads about them on the
<a href="http://microformats.org/wiki">microformats wiki</a>.
</p>
</div>
</body>
</html>
</source>

===hCal#1: An hCalendar <code>dtstart</code>===

<source lang=html4strict>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<title>Value Excerption Pattern Test hCal#1</title>
</head>
<body>
<div class="vevent">
<h1 class="summary">Value Exception Test Day!</h1>
<p class="description">Come help <span class="organizer vcard">
<a class="fn url org" href="http://microformats.org">microformats.org</a>
</span> test a new value-excerption pattern for sanity and
robustness!
</p>
<p>Help out by running some tests at
<span class="dtstart">
<span class="value-title" title="2009-01-12T12:00:00-0800"></span>
midday on Monday January 12th</span>.
</p>
<p>See <a class="url" href="http://microformats.org/wiki/value-excerption-pattern-issues/empty-value-element-test">the
wiki</a> for more details!
</p>
</div>
</body>
</html>
</source>

===hCard#1: An hCard <abbr title="birthday"><code>bday</code></abbr>===

<source lang=html4strict>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<title>Value Excerption Pattern Test hCard#1</title>
</head>
<body>

<div class="vcard">
<h1 class="fn">Ben Ward</h1>
<p>Ben Ward's birthday is
<span class="bday">
<span class="value-title" title="1984-02-09"></span>
February 9th
</span>.
You should throw him a party! Or call his <span class="tel">
<span class="type"><span class="value-title" title="cell"></span>mobile</span>
on <span class="value">415.123.123</span></span> to wish him well!
</p>
</div>

</body>
</html>
</source>

===hAudio#1: An hAudio <code>duration</code>===

<source lang=html4strict>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<title>Value Excerption Pattern Test hAudio#1</title>
</head>
<body>
<h1>Song of the year?</h1>

<p class="haudio">Did you hear ‘<span class="fn">Heavy Water</span>’ on
<span class="contributor">Foals</span>
‘<span class="album">Antidodes</span>’ record
<span class="published">
<span class="value-title" title="2008"></span>
last year
</span>? It's
<span class="duration">
<span class="value-title" title="PT04M32S"></span>
4 and a half minutes long
</span>, you should make time to hear it!</p>
</div>

</body>
</html>
</source>

''If you believe there is an error in any of these tests, or in any others that people contribute, please post on the {{MicroformatsMailingList}}.''

==Evil Tests==

If you want to give existing microformat parsers a good run out, construct ‘evil’ tests using nesting, combination and interpolation of different microformats.

===hAtom + hCalendar===

<source lang=html4strict>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<title>Value Excerption Pattern Test hAtomhCalEvil#1</title>
</head>
<body>
<div class="hentry vevent">
<h1 class="entry-title summary">An introduction to Microformats</h1>
<p>
Published on <span class="published updated">
<span class="value-title" title="2009-01-09T11:33:00-0800"></span>
January 11th, late afternoon</span>
by <span class="author organizer vcard">
<a class="url fn" href="http://example.com">
Joe Blogger</a></span>.
</p>
<p class="entry-content description">
<span class="dtstart">
<span class="value-title" title="2009-01-14T19:00:00"></span>
this coming Wednesday at 7
</span> is not the date of a completely fictional microformats
event. If it existed, it would promise to be informative and get
you up to speed on microformats.org for 2009! Now you've
learned to work with microformats a little, why not attend and
get involved! Why not? Because this event is a test case, not
for real.
</p>
</div>
</body>
</html>
</source>

==Response==

* Don't like the empty element? Don't like the use of the title attribute? '''Please file general issues concerning the proposed pattern on the main [[value-excerption-pattern-brainstorming#enabling_more_use_of_title_attributes|value excerption brainstorming page]]''', or discuss them on the {{MicroformatsMailingList}}.
* Add results of tests and responses to these tests themselves on ''this page''.

Misplaced responses will be moved, and having to do so will make [[User:BenWard|Ben]] growly, so, y'know, please try to keep the wiki tidy.

===Successful Tests===

List successfully tested environments here. Add new environments as new list items, and expand existing list items with your name and platform variants to indicate verified successes.

{|
|+ Results of tests across various publishing/rendering environments
|-
! Product
! <abbr title="Publishing or Consuming?">P/C?</abbr>
! Platforms
! Test By
! Notes
|-
| MediaWiki/Linux
| Publishing
| Safari 3.2.1 (Mac OSX 10.5)
| [[User:BenWard]]
| The empty <code>span</code> elements are maintained in <abbr title="MediaWiki">MW</abbr> output. Note that <code>a</code> elements in the tests get escaped by this MediaWiki install.
|-
| Safari 2.0.4
| Consuming
| Mac OSX 10.5
| [[User:GeorgeBrock]]
| No tooltip.
|-
| Safari 3.2.1
| Consuming
| Mac OSX 10.5,
| [[User:BenWard]]
| Empty-span remains in DOM. Web Inspector reports the element has width and height of ‘0px’. No tooltip due to zero-dimensions.
|-
| Firefox 2.0
| Consuming
| Mac OSX 10.5
| [[User:GeorgeBrock]]
| Empty-span remains in DOM. Firebug reports the element has width of '0px' and height of ‘16px’. No tooltip due to zero-width.
|-
| Firefox 3.0
| Consuming
| Mac OSX 10.5,
| [[User:BenWard]]
| Empty-span remains in DOM. Firebug reports the element has width of '0px' and height of ‘16px’. No tooltip due to zero-width.
|-
| Firefox 3.1ß1
| Consuming
| Mac OSX 10.5,
| [[User:BenWard]]
| Empty-span remains in DOM. No tooltip.
|-
| Opera 9.62
| Consuming
| Mac OSX 10.5,
| [[User:BenWard]]
| Empty-span remains in DOM. Dragonfly reports the element has width of '0px' and height of ‘0px’. No tooltip due to zero-dimensions.
|-
| Internet Explorer 5.2
| Consuming
| Mac OSX 10.5,
| [[User:BenWard]]
| No tooltip.
|-
| Internet Explorer 6.0
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:GeorgeBrock]]
| Empty-span remains in DOM (visible to Web Developer Toolbar, accessible from Javascript). No tooltip.
|-
| Internet Explorer 7.0
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:GeorgeBrock]]
| Empty-span remains in DOM (visible to Web Developer Toolbar, accessible from Javascript). No tooltip.
|-
| Internet Explorer 8.0 beta 2
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:GeorgeBrock]]
| Empty-span remains in DOM. Developer Tools (built in to <abbr title="Internet Explorer 8 beta 2">IE8b2</abbr>) report the element has width of '0px' and height of '19px'. No tooltip due to zero-width.
|-
|}

===Failed Tests===

For failures, please provide as much information as you can. The precise impact of the error, whether the behavior could be regarded as a bug in the software you're testing, whether it works in subsequent releases, whether you changed any settings in the software to produce the result, and if so, whether enabling/disabling that setting should be regarded a showstopper if this pattern were certified.

Since we want more detail, please expand failures into headed sections rather than cramming into a table.

For example, take this entirely plausible scenario as a template:

====Example: Fake Publisher 3.1ß====
; Platform
: Windows Vista
; Test By
: [[User:BenWard]]
; Description
: When trying to enter an empty span in my <abbr title="Hypertext Markup Language">HTML</abbr> editor, which I wrote myself whilst I was high, the application immediately crashes, performs <code>rm -rf /</code> on all UNIX boxes connected to my local network (which also appears to cause Android phones within Bluetooth range to do the same…), and then causes all attached peripherals to combust. I was not able to reproduce, as my house was now on fire. I think using a self closing XHTML tag instead might work-around the problem because as we know, it's been proved by Real Scienticians that XML is always better than HTML. Alternatively, it may be a bug in the beta software.
; Notes
: This is a beta release, and a bug has been filed.
: This product has a known history of flammability bugs.
: The user must explicitly enable the ‘Endanger My Life’ checkbox under the ‘Advanced Mislabelled Checkboxes’ tab of the ‘Complicated Preferences’ preferences pane.
: You get the idea.

====Browser <abbr title="What you see is what you get">WYSIWYG</abbr> editor: [http://tinymce.moxiecode.com/ TinyMCE 3.2.1.1]====
; Platform
: Firefox 3.0 on Mac OSX 10.5
; Test By
: [[User:GeorgeBrock]]
; Description
: Empty spans entered using TinyMCE's source editor are removed when switching back to the default WYSIWYG view.
: This is not a bug with TinyMCE, the editor is designed to remove empty instances of most elements by default. The handling of empty elements can be changed by modifying the [http://wiki.moxiecode.com/index.php/TinyMCE:Configuration/valid_elements valid-elements setting] (e.g. change <code>-span</code> to <code>span</code> and empty spans will no longer be removed), however settings can only be changed by modifying the source code of the page that contains the TinyMCE instance, so it is likely that some users will not be able to apply this fix.
; Notes
: This behaviour can be easily reproduced using the online [http://tinymce.moxiecode.com/examples/full.php TinyMCE examples].
: TinyMCE is the default WYSIWYG editor in WordPress[http://codex.wordpress.org/TinyMCE].
: With a single whitespace character (‘space’), the <code>span</code> is preserved, but yet still seems to collapse in Safari. Will write a follow-up test.--[[User:BenWard|BenWard]] 23:11, 20 January 2009 (UTC)
: You ''can'' publish this pattern using the <code>input type='hidden' class='value-title' title='2009-01-20'</code> hinted above. Semantically odd, although it's been suggested on µf lists before. Publishing workaround exists through element agnosticism. --[[User:BenWard|BenWard]] 23:11, 20 January 2009 (UTC)

====Browser <abbr title="What you see is what you get">WYSIWYG</abbr> editor: [http://www.fckeditor.net/ FCKEditor 2.6.4 Beta]====
; Platform
: Firefox 3.0 on Mac OSX 10.5
; Test By
: [[User:GeorgeBrock]]
; Description
: Empty spans entered using FCKEditor's source editor are removed when switching back to the default WYSIWYG view or submitting the form that contains the FCKEditor instance.
; Notes
: This behaviour can be easily reproduced using the online [http://www.fckeditor.net/demo FCKEditor demo].
: FCKEditor is used by various content management systems, frameworks and applications[http://www.fckeditor.net/whosusing].
: With a single whitespace character (‘space’), the <code>span</code> is preserved, but yet still seems to collapse in Safari. Will write a follow-up test.--[[User:BenWard|BenWard]] 23:12, 20 January 2009 (UTC)
: You ''can'' publish this pattern using the <code>input type='hidden' class='value-title' title='2009-01-20'</code> mentioned above. --[[User:BenWard|BenWard]] 23:12, 20 January 2009 (UTC)
: This issue does not effect FCKEditor instances that use the Placeholders plugin (this plugin comes with FCKEditor, enable it using <code>FCKConfig.Plugins.Add('placeholder')</code>). Examining the Placeholders plugin code may yield an easier work-around than including the plugin (I had a quick look but didn't see anything that was obviously responsible for allowing empty spans) -[[User:GeorgeBrock|GeorgeBrock]] 23:20, 20 January 2009 (UTC)



===General Test Feedback===
<div class='discussion'>
* Any general feedback you have on this test is most welcome. However, if you have issues with the pattern or alternate suggestions, please file them on the main [[value-excerption-pattern-issues]] page. Also, please remember to sign your comments with <nowiki>—~~~~</nowiki> —[[User:BenWard|BenWard]] 00:12, 9 January 2009 (UTC)
* … 
** … 
</div>

==Related Pages==

* [[value-excerption-pattern]]
* [[value-excerption-pattern-issues]]
* [[value-excerption-pattern-brainstorming]]

value-excerption-value-title-test

2009-01-20T18:33:22Z

GeorgeBrock: /* Failed Tests */ Added test information for FCKEditor, improved test information for TinyMCE

value-excerption-value-title-test

2009-01-20T17:22:30Z

GeorgeBrock: Added failed test - TinyMCE

value-excerption-value-title-test

2009-01-20T12:55:12Z

GeorgeBrock: /* Successful Tests */ Added consuming test result for Firefox 2

value-excerption-value-title-test

2009-01-20T12:47:46Z

GeorgeBrock: /* Successful Tests */ Added consuming test result for Safari 2

value-excerption-value-title-test

2009-01-20T11:37:24Z

GeorgeBrock: /* Successful Tests */ Added consuming test results for IE6, 7 and 8b2

hcalendar-implementations

2008-11-21T14:57:50Z

GeorgeBrock: Added enhanced hCalendar download script

<h1>hCalendar Implementations</h1>
{{TOC-right}}
This page is an '''informative''' section of the [[hcalendar|hCalendar specification]].

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

==New Implementations==
Add new implementations here:

* [http://www.w3.org/People/Bos/HcalProxy/ Hcalproxy] runs as an HTTP server, either standalone or under inetd(8), and converts hCalendar to iCalendar.
* The calendar of [http://TikiWiki.org TikiWiki CMS/Groupware] uses hCalendar markup for events. It's a built-in feature (no need to download separate module/plugin/etc). You can see in action over at [http://wiki-translation.com wiki-translation.com]
* [http://code.google.com/p/schoorbs Schoorbs] has bookings flavored with hCalendar in view_entry.php since revision 175 (becoming 1.0-Alpha2).
* [http://buzzword.org/cognition/ Cognition] supports [[User:TobyInk/hcalendar-1.1|hcalendar 1.1]]
* ...

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

===Web-based Creators===
;hCalendar Creator : [http://microformats.org/code/hcalendar/creator hCalendar creator] ([[hcalendar-creator-feedback|hCalendar creator feedback]]) - create your own hCalendar events.
;Conference Schedule Creator : [http://dmitry.baranovskiy.com/work/csc/ Conference Schedule Creator] ([[hcalendar-schedule-creator-feedback|Conference Schedule Creator feedback]]) - create your conference schedule with hCalendar events.
;Permatime hCalendar vevent generator : [http://permatime.com/ Permatime] enables sharing of points in time as well as acting as a quick way to generate hcalendar vevents.

===Blogging and CMS tools===
;Midgard CMS : [http://www.midgard-project.org/documentation/net-nemein-calendar/ Midgard CMS - net.nemein.calendar] - as [http://bergie.iki.fi/blog/new-event-calendar-for-midcom.html blogged by Henri Bergius]

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

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

===Desktop Authoring Tools===
;Dreamweaver Extension : [http://www.webstandards.org/action/dwtf/microformats/ Extension suite] for Dreamweaver 8 from the [http://webstandards.org/ Web Standards Project].
;xfy :
In [https://www.xfytec.com/community/ xfy Community], there are some hCalendar implementations.
* [https://www.xfytec.com/community/modules/mydownloads/singlefile.php?cid=15&lid=25 hCalendar via RSS] parses an RSS feed, retrieves XHTML documents linked from that feed, and syndicates hCalendars into a calendar view.
* [https://www.xfytec.com/community/modules/mydownloads/singlefile.php?cid=19&lid=23 hCalendar Marker XVCD] helps to mark up an event information in XHTML document with hCalendar.
* [https://www.xfytec.com/community/modules/mydownloads/singlefile.php?cid=15&lid=17 Simple RDF Calendar XVCD] is a schedule tool which uses RDF Calendar format. It also converts RDF Calendar format to iCalendar and hCalendar format.
;Windows Live Writer :
* WLW's [http://gallery.live.com/liveItemDetail.aspx?li=9751e563-1408-4fc3-8028-bd4351edb1fb&l=8 Event Plugin] formats events in blog posts with hCalendar.

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

==Conversion and Import==
Implementations you can use to importing into a calendar application, typically by converting hCalendar to iCalendar/vCalendar.

===Web Services===
These return iCalendar (.ics) and other calendar formats for easy importing into typical calendar programs or other processing.
* [http://feeds.technorati.com/events Technorati Events Feed service] uses X2V library to parse hCalendar and return iCalendar (.ics).
**Note friendly URL, e.g. http://feeds.technorati.com/events/http%3A//microformats.org
**The [http://georgebrock.com/projects/enhanced-hcalendar-downloads/ enhanced-hcalendar-downloads] script detects links to this service and displays a menu when they are clicked containing the original Technorati link and links to add the event to Google, Yahoo! and 30boxes.
* [http://suda.co.uk/projects/X2V/ X2V] parses hCalendar and produces a .ics (iCalendar) stream.
**Note: needs to be updated to track changes in the specification as they occur.

* [http://spanningsalesforce.com/ Spanning Salesforce] produces hCalendar-enabled RSS feeds and .ics calendars from Salesforce.com.
* [http://makedatamakesense.com/myspace/event/ MySpace Events RSS Creator] creates RSS feeds of MySpace events with hCalendar markup.

===Firefox Greasemonkey Plugins===
* [http://george.hotelling.net/90percent/ George] has built a [http://george.hotelling.net/90percent/geekery/greasemonkey_and_microformats.php Greasemonkey user script that detects hCalendar events and allows users to easily add them to their calendar application(s)].
* [http://inside.glnetworks.de/ Martin Rehfeld] has updated the work of [http://blogmatrix.blogmatrix.com/ David Janes] and produced a [[Greasemonkey]] [http://inside.glnetworks.de/2006/06/05/microformats-have-arrived-in-firefox-15-greasemonkey-06/ script] that finds many microformat elements, including hCalendar events, and [http://blog.davidjanes.com/mtarchives/2005_08.html#003379 provides a popup menu of actions]. The hCalendar to vCalendar conversion is done internally within the script. ''This will work with FireFox 1.5+/GreaseMonkey 0.6.4+ now.''

===Aggregators===
* [http://placenamehere.com/mf/nnwextract/ Extract Microformats] is a script for NetNewsWire that supports extracting hCard and hCalendar data in blog posts (via Technorati service). Written by [[User:ChrisCasciano|Chris Casciano]]
* [http://kula.jp/software/endo/screenshots/ Endo], an OS X aggregator, supports discovering hCalendar and adding those events to iCal. Look at the last screenshot at the bottom of the page.

===Converters===
* [http://www.w3.org/People/Bos/HcalProxy/ Hcalproxy] runs as an HTTP server, either standalone or under inetd(8), and converts hCalendar to iCalendar. E.g., if Hcalproxy is running on localhost port 8000 and <nowiki>http://example.org/page.html</nowiki> points is an HTML page, then <nowiki>http://localhost:8000/http://example.org/page.html</nowiki> is an iCalendar document with the events from that page.

==Browsing==
Implementations that detect, display and otherwise highlight hCalendar events in pages.

* In [http://www.xfytec.com/community/ xfy Community], there are some hCalendar implementations. "hCalendar via RSS" parses an RSS feed, retrieves XHTML documents linked from that feed, and syndicates hCalendars into a calendar view.
* [http://code.google.com/p/js-hcalendar js-hcalendar] parses hCalendar and produces a displayable HTML table/CSS-based calendar (formerly called JSCalendar).
* [http://thebitterpill.com/07-2007/a-jquery-hcal-parser/ jqueryhcal] is a jQuery-based hCalendar parser that supports multi-day events, dtend, and other features.

===Firefox extension===
*[http://www.orch8.net/ AlchemyPoint] is a Firefox extension and proxy service that can detect microformats in HTML documents and display browsing/mashup suggestions based on their contents.
*[http://blog.codeeg.com/tails-firefox-extension/ Tails is a Firefox Extension] that will display the presence of microformats ([[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], [[xfolk|xFolk]]) on a webpage.
*[https://addons.mozilla.org/en-US/firefox/addon/4106 Operator] also displays the presence of microformats, is extensible, and allows you to add actions such as "Add hCalender to Yahoo! Calendar".

====Pending====
*[http://reminderfox.mozdev.org/ ReminderFox] have hCalendar import on their "to do " list.

===Flock extension===
*[http://www.orch8.net/ AlchemyPoint] is a Flock extension and proxy service that can detect microformats in HTML documents and display browsing/mashup suggestions based on their contents.
*[http://blog.codeeg.com/2006/03/20/flock-tails-flocktails/ Flocktails] - port of Tails extension for Flock 0.5.12 that looks for hCards, hCalendar, xFolk and hReview and tosses them into a handy topbar

==Libraries==
Open source libraries of hCalendar parsers and other related code for building hCalendar implementations. Note: it is very likely that some of the above implementations may be duplicated in this section. That's ok.
; Javascript :
* [http://virtuelvis.com/archives/2005/11/learn-to-love-microformats simple hCalendar parser] by [http://virtuelvis.com/ Arve Bersvendsen]
* [http://microformats.org/code/hcalendar/creator hCalendar creator] ([[hcalendar-creator-feedback|hCalendar creator feedback]])
; PHP :
*[http://randomchaos.com/microformats/base/ Microformat Base] is an open-source PHP microformat aggregation crawler, currently recognizing hreview, hcalendar, and hcard (Source code no longer available as of 6 Dec 06).
*[http://enarion.net/phpmicroformats/ phpMicroformats] is a PHP class library that generates microformats for calendar events (hCalendar) and vcards (hCard).
* [http://fresh.t-systems-sfr.com/unix/src/www/WebCalendar-devel-1.1.1.tar.gz:a/WebCalendar-1.1.1/includes/classes/hKit/hcal.profile.php hCalendar profile] for the [http://allinthehead.com/hkit/ hKit] parser.
; Ruby [http://rubyforge.org/projects/uformats/ uformats]: is a ruby library that can parse [[hCalendar]], [[hCard]], [[hReview]] and [[rel-tag]]
; XSLT :
* X2V is available as an XSLT library
* [http://dev.w3.org/cvsweb/2001/palmagent/ palmagent] by [[User:DanC]] includes toICal.xsl and test materials; it works much like xhtml2vcal.xsl in X2V. See also: [http://www.w3.org/2002/12/cal/ RDF Calendar workspace] with icalendar test materials.
; Python :
* [http://vobject.skyhouseconsulting.com/ vObject], part of the Chandler project, claims experimental hCalendar support.

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

activity-verb-examples

2008-10-24T00:08:56Z

GeorgeBrock: added examples of verbs from http://www.vimeo.com/#activity

<h1>activity verb examples</h1>
{{TOC-right}}
Part of the [[activity-streams]] effort. Per the microformats [[process]] this page is here to document existing real world web publishing examples of activity verbs (typically as part of activity streams).

== examples ==
In alphabetical order by site/service name:
=== Flickr ===
* [http://flickr.com/activity Flickr recent activity on your account]
** "newest contact" (of Flickr USER)
** "marked you as a contact too" (by Flickr USER)
** "comment since yours"
** "added this as favorite" (one of your photos)
** "said" (a comment on one of your photos)
** "added a tag" (tagname) (on one of your photos)
** "added a note" (on one of your photos)
** sent a Flickr mail (by Flickr USER)

Oddly/interestingly enough, the posting a photo itself does not show up in Flickr's activity streams.

=== FriendFeed ===
* [http://friendfeed.com FriendFeed]
** "posted" (message on Twitter, entry on Tumblr, photo on brightkite.com, message on brightkite.com, message on Jaiku, entry on BLOGNAME, link)
** "published" (photos on Flickr, videos on Vimeo)
** "dugg" (story on Digg)
** "checked in" (on brightkite.com)
** "bookmarked" (page on delicious)
** "loved" (song on Last.fm)
** "added" (event on Upcoming)

=== Vimeo ===
* [http://www.vimeo.com/#activity "All activity" on Vimeo]
** "uploaded" (a video)
** "likes" (a video)
** "commented on" (a video)
** "tagged" (a video with a tag)
** "joined" (a group)
** "created" (an album)
** "added" (a video to an album)

=== see also ===
For more examples, see also:
* [http://diso-project.org/wiki/activity-streams-examples DiSo wiki activity streams examples]
* [http://wiki.diso-project.org/activity-stream-verbs other DiSo wiki activity stream verbs]

== analysis of examples ==
Analyzing the above (and other) examples, one can deduce the following common verbs:

* posted
** FriendFeed - many specific types
** Flickr - a comment
* ...

More examples and analysis are necessary to expand this set. Some of this can be found by:

See also the analysis of [http://wiki.diso-project.org/activity-stream-verbs common activity stream verbs on the other DiSo wiki].

== see also ==
* [[activity-streams]]
* [[activity-verb-formats]]
* [[activity-verb-brainstorming]]

activity-verb-examples

2008-10-23T23:55:13Z

GeorgeBrock: added additional Friend Feed examples ("published" for Vimeo videos and "added" for Upcoming events)

hatom-examples-in-wild

2008-09-24T10:13:05Z

GeorgeBrock: added aduk.org to examples

=hAtom Examples in the Wild=

The following sites have implemented [[hatom|hAtom]], and thus are a great place to start for anyone looking for examples "in the wild" to try parsing, indexing, organizing etc. If your site marked up with hAtom, feel free to add it o the '''top''' of this list. Please check back after a few days, to see if anyone has found any problems with the examples supplied.

== 0.1 hAtom examples==

* [http://www.aduk.org/ ADUK] use hAtom to mark up news on their home page.
* [http://thetyee.ca/Blogs/TheHook/ The Hook] a Canadian political blog, uses hAtom for blog posts and list of blog posts, however also offers a feedburner RSS feed.
* [http://www.plaintxt.org/experiments/blog-summary/ Blog Summary] is a [[wordpress|WordPress]] plugin from plaintxt.org that generates a semantic list of recent entries in hAtom. By [[implementors#Scott_Allan_Wallick|Scott Allan Wallick]].
* [http://www.yigg.de YiGG (a german social-news community)] Marks up all there Pages with stories using hAtom.
* [http://www.dancefederation.co.uk Dance Federation Salsa Dancing & Jive Dancing Lessons and Events ] Directory for classes, lessons and events users hatom for its news page and generating rss.
* [http://blog.kakkoi.net/ Kakkoi] - combine hAtom (i.e., xFolk RC1, hreview, hAtom) for blog posts and comments.
* [http://www.vibereview.com/ VibeReview] uses hAtom for sex toy reviews and articles (no nudity, but still maybe NSFW). Two feeds can be found on the homepage.
* [http://www.linuxinfusion.com/ Linux Infusion] uses hAtom for blog posts and comments.
* Joseph Bergantine has used hAtom to mark up [http://bergantinedesign.us/blog/my-microwave-has-a-button-that-says-record blog posts], [http://bergantinedesign.us/blog/ article lists], and [http://bergantinedesign.us/blog/doneish#comment000068 comments]
* [http://microrevie.ws/ MicroReviews] marks up each review with [[hAtom]] so that every page can be a feed. See [http://microrevie.ws/ the home page] or [http://microrevie.ws/????? 5-Star Reviews]
* LocalHero (localhero dot biz) A local search which returns it search results in hatom (as well as other microformats).
* [http://blog.livedoor.jp/forestk/ forestk's blog] uses hAtom (note it is Japanese!)
* [http://www.niallkennedy.com/blog/ Niall Kennedy's Weblog] features hAtom on every page. includes comments.
* [http://weborganics.co.uk/ WebOrganics] - Has hAtom feeds on every page.
* [http://journal.redflavor.com/ Reprise] - A [http://redflavor.com/reprise.rb minimal blog] application which uses hAtom out of the box.
* [http://www.bbc.co.uk/worldservice/bangladeshboat BBC World Service Bangladesh River Journey] a social network mashup, with hAtom entries & other microformats. See [http://dharmafly.com/blog/bangladeshboat Dharmafly blog discussion].
* [http://www.people.com/people/news/ People Magazine] uses hAtom to markup the latest news stories.
* [http://www.bo.ingv.it/italiano/News.html Istituto Nazionale Geofisica e Vulcanologia, Bologna] implemented hAtom entries with embedded rel-tags for categories in its news-page (custom template for [http://www.modxcms.com MODx CMS]).
* [http://v1.itvp.pl/blog/przebojowanoc/i.tvp/idb/24/ ITVP] uses hAtom for entries. See [http://twitter.com/Wojtek/statuses/299700082 Wojtek's announcement 2007-09-28].
* [http://shiftingpixel.com Shifting Pixel] uses hAtom for blog posts and comments.
* [http://lazylibrary.com LazyLibrary] uses hAtom on book results pages.
* [http://findsubstance.com Find Substance Blog] uses hAtom for blog posts.
* [http://www.blogger.com Blogger]
** [http://groups.google.com/group/bloggerDev/browse_thread/thread/69344c5cc35b472e Announcement] on Blogger Dev that all new blogs will have hAtom classes
* AOL
**[http://news.aol.com AOL News], AOL News has implemented hAtom into their center column. This display will be used on other AOL channels as well
**[http://sports.aol.com AOL Sports], AOL Sports is the second AOL channel to use the hAtom display for its center column data
* [http://www.creation.uk.com Creation design & marketing] uses hAtom for a lot of the content as well as [http://www.creation.uk.com/news/2007/06/06/easy-money/ comments on articles].
* [http://www.sndbx.org/ The Sandbox Designs Competition] uses hAtom for all content, hCard for participant (the competition designers) and sponsor information, hCalendar for the competition schedule, XFN for links, and rel-license for licensing information. It's all GNU GPL.
* [http://guyleech.net guyleech.net] uses hAtom for blog posts, and uses hCard for contact information. There is also an [http://guyleech.net/technical/html/minimal-microformats article] on how to minimise hAtom, to save time and code.
* [http://kpumuk.info/ Dmytro Shteflyuk] uses hAtom for all blog posts.
* [http://blog.no-panic.at Florian Beer] uses hAtom to mark up all the blog posts. There is also a [http://blog.no-panic.at/2006/11/16/hatom-and-wordpress/ tutorial] on how to convert [[wordpress|WordPress]] themes to include hAtom.
* [http://ficlets.com/ Ficlets] uses hAtom on the [http://ficlets.com/stories main stories page] and on [http://ficlets.com/stories/12 individual story pages].
* [http://www.international.unt.edu UNT International] uses hAtom combined with hCard on news/announcement pages (e.g., [http://www.international.unt.edu/quick/news the main news page]) in addition to providing traditional Atom feeds
* [http://www.absalom.net.au Absalom Media] uses hAtom combined with hCard for articles.
* [http://www.joomlamug.com Joomla! Melbourne User Group] uses hAtom combined with hCard for articles.
* [http://www.volume.co.uk Volume] - Main news page is marked up as hAtom 0.1
* [http://yedda.com Yedda] - Yedda support hAtom on exploration of questions where there is also support for Atom and RSS feeds. ([http://yedda.com/questions/recent/ example])
* The [http://www.westmidlandbirdclub.com/ West Midland Bird Club's] frequently-updated [http://www.westmidlandbirdclub.com/new.htm What's New] page, [http://www.westmidlandbirdclub.com/ladywalk/latest.htm news from its Ladywalk Reserve] and [http://www.westmidlandbirdclub.com/worcs/grimley/latest.htm news from Grimley Pits] — comments welcome on my talk page [[User:AndyMabbett|Andy Mabbett]]
* [http://pixelsebi.com pixelsebi's repository] uses hAtom 0.1 for blog posts (and hCard, hCalendar, XFN, xFolk and many more) based on manual [[wordpress|WordPress]] template modifications
* [http://www.qmpeople.com/ qmpeople] uses hAtom combined with hCard for [http://www.qmpeople.com/blog/ blog].
* [http://www.geekinthepark.co.uk Geek in the Park] uses hAtom for the comments. -- by [[User:Trovster|trovster]]
* [http://www.csarven.ca Sarven Capadisli] uses hAtom for the articles and comments -- by [[User:Csarven|csarven]]
* [http://www.capital.edu Capital University] uses hAtom 0.1 to mark up the feed of latest posts by student bloggers on its home page.
* [http://blog.davidjanes.com Ranting and Roaring] (David Janes)
* [http://ChunkySoup.net/ ChunkySoup.net] has redesigned using hAtom 0.1 and hCards on the entire site — by [[User:ChrisCasciano|Chris Casciano]]
* [http://sedna.spip.org/sedna/ Sedna RSS] (a feed aggregator based on SPIP, by Fil, IZO and others; GPLd sources are available at [http://zone.spip.org/trac/spip-zone/browser/_squelettes_/sedna SPIP-Zone])
* [http://quotedprintable.com/pages/scribbish Scribbish] is a Typo theme which uses hAtom.
* [http://rbach.priv.at/hAtom2Atom/Changelog/ hAtom2Atom.xsl's Changelog] is published as hAtom and Atom.
* [http://federali.st/ federali.st]'s webbed Federalist Papers are each marked up in hAtom.
* [http://www.plaintxt.org/themes/sandbox/ Sandbox] is a theme for [[wordpress|WordPress]] that uses hAtom. By [[implementors#Scott_Allan_Wallick|Scott Allan Wallick]].
** The theme is also available to accounts on the [http://wordpress.com/ <username>.wordpress.com] hosting service. The [http://blog.coworking.info Coworking] and [http://barcamp.wordpress.com BarCamp] blogs are examples of custom Sandbox themes.
** Over 40 designs available for the Sandbox at the [http://www.sndbx.org/ Sandbox Designs Competition], which also uses hAtom
* [http://www.whump.com/dropbox/Strangelove.zip Strangelove] is a modification of the default WordPress theme (Kubrick) with hAtom support.
** It points to the hAtom2Atom proxy service as the link for syndication feeds.
* All [http://www.plaintxt.org/themes/ plaintxt.org themes] for [[wordpress|WordPress]] now use hAtom. The themes are also coded for hCard compliance. The themes, by name, are:
** [http://www.plaintxt.org/themes/barthelme/ Barthelme] (two-column, fluid), [http://www.plaintxt.org/themes/blogtxt/ blog.txt] (two- or three-column, elastic), [http://www.plaintxt.org/themes/plaintxtblog/ plaintxtBlog] (three-column, fluid), [http://www.plaintxt.org/themes/simplr/ Simplr] (one column, elastic), [http://www.plaintxt.org/themes/veryplaintxt/ veryplaintxt] (two column, fluid)
** By [[implementors#Scott_Allan_Wallick|Scott Allan Wallick]].
* [http://www.pats.ua.ac.be/courses PATS Courses], the PATS Research Group uses hAtom to mark up the latest course documents for some of their courses
* [http://mix.excite.co.uk Excite MIX], the Ajax Start Page from Excite Europe, uses hAtom 0.1 and hCard in the Feed Viewer to mark up feed entries and authors.
* [http://last.fm Last.FM], a social music sharing platform, uses hAtom markup for [http://blog.last.fm/2007/05/30/rss-your-shoutbox-and-you shoutbox], and recommends using [http://tools.microformatic.com microformatic]'s transcode tool
* [http://vlograzor.com/ Vlog Razor] - Contains multiple hAtom feeds on the same page.



==Examples with some problems==

Entries may be moved here if there's a problem with the way hAtom is used on the page concerned. If the page is yours, and you want to improve it, see the [[hatom-faq|hAtom FAQ]], or raise any queries on [[hatom-issues|hAtom Issues]] or [[mailing-lists#microformats-discuss|the mailing list]], where people will be happy to help you.

=== Pre 0.1 hAtom examples===
These pages conform to an older draft standard and need to be updated.

* [http://www.myelin.co.nz/post/ Second p0st] (Phil Pearson)

==See Also==
{{hatom-related-pages}}

web-agencies

2008-09-17T16:05:36Z

GeorgeBrock: added Doodledo to list of agencies using microformats

<h1>web agencies</h1>

More and more modern web design, development agencies/consultancies are supporting not only [[POSH]] but also microformats, both on their own sites and as a matter of standard practice on sites they build. This page is for documenting these modern web agencies.

== agencies ==
Alphabetical. MUST note [[hCard]] contact info URL. SHOULD also note URLs of client sites they've developed that support microformats.
* <span class="vcard"><span class="fn org">Doodledo</span> (<span class="adr"><span class="country-name">UK</span></span> based agency, contact info at <span class="url">http://www.doodledo.info</span>, <span class="note">recently built [http://www.aduk.org/contact.php ADUK.org] & [http://www.thinkambient.co.uk ThinkAmbient.co.uk]</span>)</span>
* [http://objectadjective.com Object Adjective] ([http://www.objectadjective.com/contact/ hCard contact info])

== advocacy ==
Getting more web design, development, etc. agencies and related efforts to adopt microformats also has the indirect benefit of them supporting microformats in the sites they build and develop. Suggest web agencies for [[advocacy]] on the [[web-agency-advocacy]] page.

== related ==
* [[advocacy]]

meetup

2008-09-11T13:11:00Z

GeorgeBrock: added self to "interested in london meetups"

<h1>microformats weekly meetup events</h1>
A regular source of microformats [[events]].
{{TOC-right}}
== 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.

By making this a regular (every week) 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.

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.

Cities where weekly meetup events are held, sorted alphabetically:

== London ==
Interested folks for [[events/2008-09-09-london-meetup-dinner|2008-09-09]]:
* [[User:Phae|Frances]]
* [http://georgebrock.com George Brocklehurst]
* [[User:Tantek|Tantek Çelik]]
* Hannah Donovan
* Drew McLellan
* ...
In general for London:
* [[User:Phae|Frances]]
* [[User:GeorgeBrock|George Brocklehurst]]
* [http://twitter.com/ptg/statuses/906735728 Patrick Griffiths]
* ...

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

== San Francisco ==
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]]
* Metreon Food Court
** +0 not the greatest, but it has lots of choices - [[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]]
* Naan & Chutney on Haight st. (Eran Globen)
* ...

Past SF venues. We'll reuse these at some point I'm sure.
* 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]]
* 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]]
* 21st Amendment: [[events/2008-08-26-weekly-meetup-dinner|2008-08-26]]

== Other Cities ==
I encourage folks to organize meetup dinners wherever there is sufficient local critical mass. Once you start 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
* San Diego - [[User:EdwardOConnor]]
* San Jose (South Bay) - [[User:Kevin_Marks]], Rohit Khare
* Montreal - [[User:Csarven]]

== Organize a weekly meetup ==
It's pretty easy to organize a weekly meetup, at a minimum, all you have to do is sometime beforehand (preferably at least a day in advance, like on Monday, for the Tuesday meetup).

In short:
# Pick a location
# Announce it (location at 18:30, Tuesday) on various event sites and notification services.

Details:
# 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 event pages
#* Create specific event page on microformats.org wiki.
#** Edit the [[events]] page and copy/paste the previous week's weekly meetup event, updating the date and location and commenting out the URLs.
#** Click on the previous weekly meetup event link, edit, select all, copy all the source, go back back.
#** Click on the (currently red) new weekly meetup event link, paste, and make the following edits:
#*** update all the URLs
#*** update all the dates
#*** comment out the ;Web section in details section
#*** clear out past attendees, photos, notes
#*** update the location specific tags, remove the previous upcoming event tag
#* Copy that specific event page URL and
#* Create a public [http://pownce.com Pownce] event with that wiki URL
#** what's happening? microformats weekly meetup dinner!
#** where? that location you chose
#** 6:30 PM on ....
#* Create an [http://upcoming.org upcoming] event with wiki + Pownce URLs
#* RSVP to the public Pownce event with "attending" and add the upcoming URL.
#* Update the microformats wiki event page with Pownce and upcoming URLs, and upcoming: event specific tag
#* Update the microformats wiki [[events]] page with the Pownce URL
# Announce it
#* [http://twitter.com/ Tweet] the Pownce event
#* Add the upcoming event to various groups, add tags to it.
#* On the day of the event, post a reminder in the morning (to Twitter etc.), and again an hour before the event.
#* Afterwards post a thank you note thanking those that attended.

== related ==
* [[events]]

benefits

2008-09-10T14:00:35Z

GeorgeBrock: added an h1 and a toc

<h1> Benefits of using Microformats </h1>
{{TOC-right}}

There are many benefits to using Microformats when publishing content on the web. This page provides a summary of some of those benefits.

==Don't repeat yourself==

With Microformats you can publish a <strong>single, human readable</strong> version of your information in HTML and then make it machine readable with the addition of a few standard class names.

A common example is contact details: If you wanted to publish human- and machine-readable versions without Microformats you would publish an HTML page containing your contact information and a separate machine-readable vCard file that people could automatically import into their address book software. Your information would be stored in two places making it harder to maintain and easier to get out of sync.

Using Microformats you only publish one version of the data, the human-readable HTML version with a few added class names defined by the [[hCard]] Microformat. You could also add a link to an online service to convert your hCard into a vCard file for users to download ([http://technorati.com/contacts/ Technorati] provides a service to do this). When it comes to maintaining your information not only do you only have one copy of it, it's also a copy that you can easily look at in a web browser to see if it's up to date or not.

==You already know HTML==

If you're publishing information online you already know HTML. Microformats allow you to make that your information machine readable without the need to learn a plethora of other languages.

There are Microformats to mark up [[hCard|contact information]], [[hCalendar|event information]] and [[hAtom|episodic web content]]. Without these Microformats you would need to learn three extra languages/vocabularies (vCard, iCalendar and Atom) to get the same benefits.

==Easy to add==

The Microformats design process is built around the idea of "paving the cow paths". That means we aim to support common patterns of behaviour so you probably won't have to change that much in your HTML, in most cases it's as easy as adding a few class names to existing elements and a few <span> elements here and there.

Here's a quick example of some contact details in a web page:

<pre><nowiki>
<p>
For more information call John Smith on 0207 123 123
or email <a href="mailto:john.smith@example.org">john.smith@example.org</a>
</p>
</nowiki></pre>

Then we add the [[hCard]] Microformat:

<pre><nowiki>
<p class="vcard">
For more information call <span class="fn">John Smith</span> on <span class="tel">0207 123 123</span>
or email <a class="email" href="mailto:john.smith@example.org">john.smith@example.org</a>
</p>
</nowiki></pre>

It's easy as that. This wiki even provides some helpful [[cheatsheets]] to help you remember the relevant class names.

hcard-examples-in-wild

2008-09-10T13:02:13Z

GeorgeBrock: /* new and uncategorized examples */

<h1>hCard Examples in the wild</h1>
<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>

{{TOC-right}}

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.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://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.serviceworksglobal.com/pages/contact-us.php Service Works Global] uses hcards on the contact us page and in the site footer
* [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/keylogger.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://christophertcressman.com Christopher T. Cressman] uses an hCard on the home page of his blog, [http://christophertcressman.com christopher t cressman].
* [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://www.lounews.com/ The Louisville News Company] uses hCard for site-wide contact information for the company and for the site developer.
* [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/blog/hcard Chris Messina' hCard]
* [http://flock.com/about Flock About]
* [http://tantek.com/microformats/2006/03-01-TechPlenAgenda.html Agenda: W3C Technical Plenary Day, March 1 2006] has [[hcard|hCard]] and [[hcalendar|hCalendar]] markup. ([http://www.w3.org/2006/03/01-TechPlenAgenda.html original here]).
* [http://www.gr0w.com/articles/press/growsearch_launched_press_release/ GrowSearch Launched (Press Release)] uses an hCard to provide Press Contact Point.
* The [http://www.arborday.org/ National Arbor Day Foundation] has started using hCards for their [http://arborday.org/programs/conferences/communityforestry/index.cfm upcoming] [http://arborday.org/programs/conferences/hazardtrees-treeplanting/ conferences].
* [http://www.multipack.co.uk The Multipack] has numerous hCards, especially on the [http://www.multipack.co.uk/members/ members page], as well as the next meeting information.
* [http://deadringrancor.livejournal.com/ Justin McDowell] used an hCard when [http://deadringrancor.livejournal.com/221332.html referring to a person in his blog post]
* [http://davecardwell.co.uk/cv/ Dave Cardwell] has included his hCard in his Curriculum Vitae.
* [http://blog.usweb.com/ Shaun Shull] has written a great post on [http://blog.usweb.com/archives/how-microformats-affect-search-engine-optimization-seo How Microformats Affect SEO], and has included his [[hcard|hCard]] as one of the examples.
* [http://www.thefutureoftheweb.com/ Jesse Skinner] has written a simple [http://www.thefutureoftheweb.com/blog/2006/1/hcard tutorial with examples]
* [http://www.w3.org/2005/12/allgroupoverview.html 2006 W3C Technical Plenary Week] has marked up the venue, contacts, and program committee members all with hCard.
* [http://www.avf-nexus.co.uk AVF-Nexus] have a hCard on their [http://www.avf-nexus.co.uk/contact/ contact page] - (by [http://creation.uk.com Creation"])
* [http://www.thefantasticos.com/andrew/ Andrew White] posted [http://www.thefantasticos.com/andrew/index.php/my-hcard/ his hCard] and [http://www.thefantasticos.com/andrew/index.php/62/microformats-the-should-have-been-obvious-web-dev-tool/ blogged about it].
* [http://www.2sheds.ru Oleg "2sheds" Kourapov] in his [http://www.2sheds.ru/blog/ blog] ([http://suda.co.uk/projects/X2V/get-vcard.php?uri=http://www.2sheds.ru/blog X2V]) has turned personal profile into hCard ([http://suda.co.uk/projects/X2V/get-vcard.php?uri=http://www.2sheds.ru/blog/hcard.html X2V]) and his blogroll - into combination XFN/hCards ([http://suda.co.uk/projects/X2V/get-vcard.php?uri=http://www.2sheds.ru/blog/friends.html X2V])
* [http://www.approveddesign.co.uk Approved Design Consultancy] have a hCard on their [http://www.approveddesign.co.uk/about/contact/ contact page] as well as on their [http://www.approveddesign.co.uk/about/people/ people section] - (by [http://creation.uk.com Creation"])
* [http://weblog.200ok.com.au/ Ben Buchanan] and [http://www.griffith.edu.au/cgi-bin/phone_search.pl?string=colin+morris&format=search Colin Morris] have [http://weblog.200ok.com.au/2006/01/griffith-phonebook-adds-hcard-and.html implemented hCards and vCards] for the [http://www.griffith.edu.au Griffith University] [http://www.griffith.edu.au/find/content_phonebook.html online phone book]. Eg. [http://www.griffith.edu.au/cgi-bin/phone_search.pl?string=ben+buchanan&format=search Ben's vCard] and [http://www.griffith.edu.au/cgi-bin/phone_search.pl?string=colin+morris&format=search Colin's vCard]
* WWF-Australia [http://wwf.org.au/about/contactdetails/ contact details page]
* [http://rasterweb.net/raster/ Pete Prodoehl] used the hCard format on his [http://rasterweb.net/raster/contact.html Contact page] 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://we05.com/ Web Essentials 05] marked up all their [http://we05.com/presenters.cfm presenters 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/760874 Mrs A Smith] 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]).

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

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 ===
Sort alphabetically by "family-name".
* [http://dbaron.org/ David Baron]'s home page is marked up with hCard.
* [http://tantek.com/ Tantek Çelik]'s home page includes an inline author hCard at the bottom of the page.
* [http://tomleo.com/about.html Tom Leo]'s about page has an hCard. Ya Microformats!
* [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].
* ...

=== Organizations ===
* [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>

=== 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: Web Essentials 2005 - The Presenters <nowiki>http://we05.com/presenters.cfm</nowiki> (appears to have stopped working as of 2007-12-18, perhaps earlier) mirror on tantek.com: [http://tantek.com/microformats/2005/we05/presenters.html Web Essentials 2005 - The Presenters]. Web Essentials 2005 (we05) was the [http://tantek.com/log/2005/10.html#d06t1720 first conference to adopt hCard and hCalendar] on their website.

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

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

benefits

2008-09-10T12:30:29Z

GeorgeBrock:

There are many benefits to using Microformats when publishing content on the web. This page provides a summary of some of those benefits.

==Don't repeat yourself==

With Microformats you can publish a <strong>single, human readable</strong> version of your information in HTML and then make it machine readable with the addition of a few standard class names.

A common example is contact details: If you wanted to publish human- and machine-readable versions without Microformats you would publish an HTML page containing your contact information and a separate machine-readable vCard file that people could automatically import into their address book software. Your information would be stored in two places making it harder to maintain and easier to get out of sync.

Using Microformats you only publish one version of the data, the human-readable HTML version with a few added class names defined by the [[hCard]] Microformat. You could also add a link to an online service to convert your hCard into a vCard file for users to download ([http://technorati.com/contacts/ Technorati] provides a service to do this). When it comes to maintaining your information not only do you only have one copy of it, it's also a copy that you can easily look at in a web browser to see if it's up to date or not.

==You already know HTML==

If you're publishing information online you already know HTML. Microformats allow you to make that your information machine readable without the need to learn a plethora of other languages.

There are Microformats to mark up [[hCard|contact information]], [[hCalendar|event information]] and [[hAtom|episodic web content]]. Without these Microformats you would need to learn three extra languages/vocabularies (vCard, iCalendar and Atom) to get the same benefits.

==Easy to add==

The Microformats design process is built around the idea of "paving the cow paths". That means we aim to support common patterns of behaviour so you probably won't have to change that much in your HTML, in most cases it's as easy as adding a few class names to existing elements and a few <span> elements here and there.

Here's a quick example of some contact details in a web page:

<pre><nowiki>
<p>
For more information call John Smith on 0207 123 123
or email <a href="mailto:john.smith@example.org">john.smith@example.org</a>
</p>
</nowiki></pre>

Then we add the [[hCard]] Microformat:

<pre><nowiki>
<p class="vcard">
For more information call <span class="fn">John Smith</span> on <span class="tel">0207 123 123</span>
or email <a class="email" href="mailto:john.smith@example.org">john.smith@example.org</a>
</p>
</nowiki></pre>

It's easy as that. This wiki even provides some helpful [[cheatsheets]] to help you remember the relevant class names.

irc-people

2008-09-10T11:34:26Z

GeorgeBrock: added self to IRC regulars

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|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|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|BenjaminCarlyle|BenjaminCarlyle|+1000}}
* {{irc user|HenriBergius|bergie|+0200/+0300}}
* {{irc user|Ben Ward|BenWard|+0000}}
* {{irc user|BenWest|bewest|-0800/-0700}}
* {{irc user|B.K._DeLong|bkdelong|-0500/-0400}}
* {{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|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|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|JamieKnight|JamieKnight|+1000/0000}}
* {{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}}
* [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|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|PetarPopov|popov|-0800/-0700}}
* {{irc user|Pfefferle|pfefferle|+0100/+0200}}
* {{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|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|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|Kiryl Zhybul|zkv|+0400}}
* {{irc user|ScottThorpe|Salve|-0800/-0700}}
* {{irc user|Dane|imdane|-0600/-0500}}

User:GeorgeBrock

2008-09-10T00:10:42Z

GeorgeBrock:

<div class="vcard"><span class="fn">George Brocklehurst</span>, a freelance web developer in London.
Links and a possible future blog at <span class="url">http://georgebrock.com</span>

User:GeorgeBrock

2008-09-10T00:09:27Z

GeorgeBrock:

<div class="vcard"><span class="fn">George Brocklehurst</span>, a freelance web developer in London.

He links to things and may one day blog at <a href="http://georgebrock.com" class="url">georgebrock.com</a></div>

User:GeorgeBrock

2008-09-10T00:07:59Z

GeorgeBrock:

GeorgeBrock is George Brocklehurst, a freelance web developer in London.

He links to things and may one day blog at http://georgebrock.com

events/2008-09-09-london-meetup-dinner

2008-09-10T00:06:39Z

GeorgeBrock: Added self to attendees

<h1>London microformats meetup dinner</h1>
{{TOC-right}}
One of several microformats [[weekly-meetup]] [[events]].

==Subscribe==
You can:
*Add this event to your Calendar: http://feeds.technorati.com/events/microformats.org/wiki/events/2008-09-09-london-meetup-dinner
*Subscribe to this event: webcal://feeds.technorati.com/events/microformats.org/wiki/events/2008-09-09-london-meetup-dinner

== details ==
<div class="vevent">
;When
:<span class="dtstart">2008-09-09T19:30+0100</span> to <span class="dtend">2008-09-09T21:00+0100</span>
;Where
:<span class="location vcard"><span class="fn org">The Princess</span>, <span class="adr"><span class="street-address">76 Paul Street</span>, <span class="postal-code">EC2A 4NE</span>, <span class="locality">London</span>, <span class="country-name">England</span></span>. <span class="url">http://upcoming.yahoo.com/venue/213236/</span></span>
:[http://maps.google.co.uk/maps?f=q&hl=en&geocode=&q=the+princess,+76-78+Paul+St&sll=51.534377,-0.09922&sspn=0.059797,0.109005&ie=UTF8&z=16&iwloc=addr Google Map] (see [http://upcoming.yahoo.com/venue/213236/ upcoming for directions]).
;What
:<span class="summary">London microformats meetup dinner</span>
;Web
:<span class="url">http://pownce.com/t/notes/3402832/</span>
:<span class="url">http://upcoming.yahoo.com/event/1080915/</span>
</div>

'''[http://technorati.com/events/microformats.org/wiki/events/2008-09-09-london-meetup-dinner Add this event to your diary or calendar program]''' http://www.boogdesign.com/images/buttons/microformat_hcalendar.png

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

By making this a regular (every week) 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.

From having informally asked a few folks in the London area it seems Tuesdays at 7:30pm work best, with a rotating venue to keep it interesting.

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

== tags ==
Please use ''all'' of the following tags when tagging related content (blog posts, photos):


tags: '''microformatsdinner20080909london microformatsdinner20080909 microformatsdinner microformatsmeetup microformats london paulstreet Princess ThePrincess upcoming:event=1080915'''

If you use Twitter [[twitter-syntax#Hash_tags|hash tags]], mention '''#microformatsdinner20080909london''' (with the "#") in tweets about the event.

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

* [[User:GeorgeBrock|George Brocklehurst]]
* [[User:Tantek|Tantek Çelik]]
* ...

== photographs ==
Please use ''all'' of the following tags when tagging related photos:

tags: '''microformatsdinner20080909london microformatsdinner20080909 microformatsdinner microformatsmeetup microformats london paulstreet Princess ThePrincess upcoming:event=1080915'''


* ...

== notes ==
Topics:
* ...
Session comments and Q&A.
* ...

== articles and blog posts ==
Articles and blog posts following up on the meetup. Newest first.

Please use ''all'' of the following tags when tagging related blog posts:

tags: '''microformatsdinner20080909london microformatsdinner20080909 microformatsdinner microformatsmeetup microformats london paulstreet Princess ThePrincess upcoming:event=1080915'''

* ...



== related pages==
{{events-related-pages}}

meetup

2008-09-08T16:18:55Z

GeorgeBrock: Added self to interested people for uF dinner in London

<h1>microformats weekly meetup events</h1>
A regular source of microformats [[events]].
{{TOC-right}}
== 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.

By making this a regular (every week) 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.

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.

Cities where weekly meetup events are held, sorted alphabetically:

== London ==
Interested folks for 2008-09-09:
* [[User:Phae|Frances]]
* [http://georgebrock.com George Brocklehurst]
* [[User:Tantek|Tantek Çelik]]
* Hannah Donovan
* Drew McLellan
* ...
In general for London:
* [[User:Phae|Frances]]
* [http://twitter.com/ptg/statuses/906735728 Patrick Griffiths]
* ...

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

== San Francisco ==
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]]
* Metreon Food Court
** +0 not the greatest, but it has lots of choices - [[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]]
* Naan & Chutney on Haight st. (Eran Globen)
* ...

Past SF venues. We'll reuse these at some point I'm sure.
* 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]]
* 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]]
* 21st Amendment: [[events/2008-08-26-weekly-meetup-dinner|2008-08-26]]

== Other Cities ==
I encourage folks to organize meetup dinners wherever there is sufficient local critical mass. Once you start 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
* San Diego - [[User:EdwardOConnor]]
* San Jose (South Bay) - [[User:Kevin_Marks]], Rohit Khare
* Montreal - [[User:Csarven]]

== Organize a weekly meetup ==
It's pretty easy to organize a weekly meetup, at a minimum, all you have to do is sometime beforehand (preferably at least a day in advance, like on Monday, for the Tuesday meetup).

In short:
# Pick a location
# Announce it (location at 18:30, Tuesday) on various event sites and notification services.

Details:
# 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 event pages
#* Create specific event page on microformats.org wiki.
#** Edit the [[events]] page and copy/paste the previous week's weekly meetup event, updating the date and location and commenting out the URLs.
#** Click on the previous weekly meetup event link, edit, select all, copy all the source, go back back.
#** Click on the (currently red) new weekly meetup event link, paste, and make the following edits:
#*** update all the URLs
#*** update all the dates
#*** comment out the ;Web section in details section
#*** clear out past attendees, photos, notes
#*** update the location specific tags, remove the previous upcoming event tag
#* Copy that specific event page URL and
#* Create a public [http://pownce.com Pownce] event with that wiki URL
#** what's happening? microformats weekly meetup dinner!
#** where? that location you chose
#** 6:30 PM on ....
#* Create an [http://upcoming.org upcoming] event with wiki + Pownce URLs
#* RSVP to the public Pownce event with "attending" and add the upcoming URL.
#* Update the microformats wiki event page with Pownce and upcoming URLs, and upcoming: event specific tag
#* Update the microformats wiki [[events]] page with the Pownce URL
# Announce it
#* [http://twitter.com/ Tweet] the Pownce event
#* Add the upcoming event to various groups, add tags to it.
#* On the day of the event, post a reminder in the morning (to Twitter etc.), and again an hour before the event.
#* Afterwards post a thank you note thanking those that attended.

== related ==
* [[events]]

hcard-examples-in-wild-pending

2008-07-14T14:06:40Z

GeorgeBrock: Added thinkambient.co.uk to list of hCard examples

<h1>hCard Examples in the wild, pending review</h1>
{{TOC-right}}

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

The following sites have published [[hcard|hCards]], but those hCards have not yet been reviewed. Once checked, they may be moved to [[hcard-examples-in-wild-reviewed]]; a great place to start for anyone looking for examples "in the wild" to try parsing, indexing, organizing etc.

If people or organizations on your site are marked up with hCard (even just your own contact information), feel free to add it to the '''top''' of this list. Please be sure to include at least one URL to a page on your site that includes actual [[hcard|hCard]] mark-up. Examples added without a URL to a page with hCard mark-up may be removed.

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

==New Examples==
Please add new examples to the '''top''' of this section so they can be reviewed! Please check back after a few days, to see if anyone has found any problems with the examples supplied.

===Added in 2008===
* [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://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].

===Added in 2007===
* [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]].
** Response in under 12 hours, to advocacy request - [[User:AndyMabbett|Andy Mabbett]]
* [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.serviceworksglobal.com/pages/contact-us.php Service Works Global] uses hcards on the contact us page and in the site footer
* [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/keylogger.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.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://christophertcressman.com Christopher T. Cressman] uses an hCard on the home page of his blog, [http://christophertcressman.com christopher t cressman].
* [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://www.lounews.com/ The Louisville News Company] uses hCard for site-wide contact information for the company and for the site developer.
* [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''''

===Added pre 2007===
* [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/blog/hcard Chris Messina' hCard]
* [http://flock.com/about Flock About]
* [http://tantek.com/microformats/2006/03-01-TechPlenAgenda.html Agenda: W3C Technical Plenary Day, March 1 2006] has [[hcard|hCard]] and [[hcalendar|hCalendar]] markup. ([http://www.w3.org/2006/03/01-TechPlenAgenda.html original here]).
* [http://www.gr0w.com/articles/press/growsearch_launched_press_release/ GrowSearch Launched (Press Release)] uses an hCard to provide Press Contact Point.
* The [http://www.arborday.org/ National Arbor Day Foundation] has started using hCards for their [http://arborday.org/programs/conferences/communityforestry/index.cfm upcoming] [http://arborday.org/programs/conferences/hazardtrees-treeplanting/ conferences].
* [http://www.multipack.co.uk The Multipack] has numerous hCards, especially on the [http://www.multipack.co.uk/members/ members page], as well as the next meeting information.
* [http://deadringrancor.livejournal.com/ Justin McDowell] used an hCard when [http://deadringrancor.livejournal.com/221332.html referring to a person in his blog post]
* [http://davecardwell.co.uk/cv/ Dave Cardwell] has included his hCard in his Curriculum Vitae.
* [http://blog.usweb.com/ Shaun Shull] has written a great post on [http://blog.usweb.com/archives/how-microformats-affect-search-engine-optimization-seo How Microformats Affect SEO], and has included his [[hcard|hCard]] as one of the examples.
* [http://www.thefutureoftheweb.com/ Jesse Skinner] has written a simple [http://www.thefutureoftheweb.com/blog/2006/1/hcard tutorial with examples]
* [http://www.w3.org/2005/12/allgroupoverview.html 2006 W3C Technical Plenary Week] has marked up the venue, contacts, and program committee members all with hCard.
* [http://www.avf-nexus.co.uk AVF-Nexus] have a hCard on their [http://www.avf-nexus.co.uk/contact/ contact page] - (by [http://creation.uk.com Creation"])
* [http://www.thefantasticos.com/andrew/ Andrew White] posted [http://www.thefantasticos.com/andrew/index.php/my-hcard/ his hCard] and [http://www.thefantasticos.com/andrew/index.php/62/microformats-the-should-have-been-obvious-web-dev-tool/ blogged about it].
* [http://www.2sheds.ru Oleg "2sheds" Kourapov] in his [http://www.2sheds.ru/blog/ blog] ([http://suda.co.uk/projects/X2V/get-vcard.php?uri=http://www.2sheds.ru/blog X2V]) has turned personal profile into hCard ([http://suda.co.uk/projects/X2V/get-vcard.php?uri=http://www.2sheds.ru/blog/hcard.html X2V]) and his blogroll - into combination XFN/hCards ([http://suda.co.uk/projects/X2V/get-vcard.php?uri=http://www.2sheds.ru/blog/friends.html X2V])
* [http://www.approveddesign.co.uk Approved Design Consultancy] have a hCard on their [http://www.approveddesign.co.uk/about/contact/ contact page] as well as on their [http://www.approveddesign.co.uk/about/people/ people section] - (by [http://creation.uk.com Creation"])
* [http://weblog.200ok.com.au/ Ben Buchanan] and [http://www.griffith.edu.au/cgi-bin/phone_search.pl?string=colin+morris&format=search Colin Morris] have [http://weblog.200ok.com.au/2006/01/griffith-phonebook-adds-hcard-and.html implemented hCards and vCards] for the [http://www.griffith.edu.au Griffith University] [http://www.griffith.edu.au/find/content_phonebook.html online phone book]. Eg. [http://www.griffith.edu.au/cgi-bin/phone_search.pl?string=ben+buchanan&format=search Ben's vCard] and [http://www.griffith.edu.au/cgi-bin/phone_search.pl?string=colin+morris&format=search Colin's vCard]
* WWF-Australia [http://wwf.org.au/about/contactdetails/ contact details page]
* [http://rasterweb.net/raster/ Pete Prodoehl] used the hCard format on his [http://rasterweb.net/raster/contact.html Contact page] 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''.
** use: <code><nowiki><span class="fn n"><span class="given-name">Andy</span> "<span class="nickname">Pigsonthewing</span>" <span class="family-name">Mabbett</span></span></nowiki></code>. [[User:AndyMabbett|Andy Mabbett]] 09:12, 16 Jan 2008 (PST) 

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