Microformats Wiki - User contributions [en]

User:DerrickPallas

2007-07-17T06:58:39Z

DerrickPallas:

== Derrick Pallas ==

=== About me ===

I am a Software Engineer for [[http://www.alexa.com Alexa Internet]], a subsidiary of [[http://www.amazon.com Amazon]]. (Anything I say on this website is on my own behalf and is not the opinion or property of my company, nor should it be construed to represent such.)

I have an MS in CS from [[http://www.ucdavis.edu UCD]] where I [[http://wwwcsif.cs.ucdavis.edu/~pallas worked]] in the [[http://morpheus.cs.ucdavis.edu/ Center for Software Systems Reasearch]]. These days I just do cool tricks with Ruby and C++, advocating cool things like [[http://www.fastcgi.com FastCGI]] and [[http://microformats.org microformats]]. You probably saw me at [[http://barcamp.org/ BarCamp]] last year or the birthday party for microformats. You can often catch me at [[http://www.sfbeta.com/ SF Beta]].

Additionally, I used to write for [[http://www.thedailywtf.com The Daily WTF]]. You can find out more about me at [[http://derrick.pallas.us my own website]].

=== re: microformats ===

What I'm working on:

* working on examples for a software dependency / generic directed acyclic graph microformat
* telling everyone I know about how to embed an hCard in the web page they've already got
* I got a couple of fields added to the Alexa search engine, including "ClassTag" and "RelTag", which search for documents in which a class or rel appear. This is useful for queries against Alexa's "Million Search Results" service.
* Every month, I count the number of pages with microformats that show up in Alexa's archive.
** I don't show this number to Ben West any more, lest it end up in IRC attached to his name. (That really makes me furious.)

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

User:DerrickPallas

2007-07-17T06:57:56Z

DerrickPallas:

== Derrick Pallas ==

=== About me ===

I am a Software Engineer for [[http://www.alexa.com Alexa Internet]], a subsidiary of [[http://www.amazon.com Amazon]]. (Anything I say on this website is on my own behalf and is not the opinion or property of my company, nor should it be construed to represent such.)

I have an MS in CS from [[http://www.ucdavis.edu UCD]] where I [[http://wwwcsif.cs.ucdavis.edu/~pallas worked]] in the [[http://morpheus.cs.ucdavis.edu/ Center for Software Systems Reasearch]]. These days I just do cool tricks with Ruby and C++, advocating cool things like [[http://www.fastcgi.com FastCGI]] and [[http://microformats.org microformats]]. You probably saw me at [[http://barcamp.org/ BarCamp]] last year or the birthday party for microformats.

Additionally, I write for [[http://www.thedailywtf.com The Daily WTF]]. You can find out more about me at [[http://derrick.pallas.us my own website]].

=== re: microformats ===

What I'm working on:

* working on examples for a software dependency / generic directed acyclic graph microformat
* telling everyone I know about how to embed an hCard in the web page they've already got
* I got a couple of fields added to the Alexa search engine, including "ClassTag" and "RelTag", which search for documents in which a class or rel appear. This is useful for queries against Alexa's "Million Search Results" service.
* Every month, I count the number of pages with microformats that show up in Alexa's archive.
** I don't show this number to Ben West any more, lest it end up in IRC attached to his name. (That really makes me furious.)

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

error-message-examples

2007-07-14T16:31:32Z

DerrickPallas:

<h1> Error Message Examples </h1>

== Contributors ==

* [http://evan.prodromou.name/ Evan Prodromou]

== Introduction ==

Examples of error messages published as chunks of readable (X)HTML by Web applications.

== Table of Contents ==

__TOC__

== Examples ==

Note that many of these examples are failed logins; they're just the easiest kind of error to generate.

* [http://www.mediawiki.org/ MediaWiki] failed login

<pre><div class="errorbox">
<h2>Login error:</h2>
Incorrect password or confirmation code entered. Please try again.
</div></pre>

* [http://www.wordpress.com/ WordPress], failed to enter required fields in comment

<pre><p>Error: please fill the required fields (name, email).</p></pre>

* [http://www.paypal.com/ PayPal] , trying to send negative dollars.

<pre><div class="messageBox error">
<p>Some required information is missing or incomplete. Please correct your entries and try again.</p>
<ul><li>Please enter an amount greater than zero.</li></ul>
</div></pre>

* [http://www.google.com/ Google] apps login error

<pre><div class="errormsg" id="errormsg_0_Passwd">
Username and password do not match. (You provided XXXXXXXXXX)
</div></pre>

* [http://www.technorati.com/ Technorati] login error

<pre><p class="error">Sorry, the member name and password
you entered do not match. Please try again.</p></pre>

* [http://www.yahoo.com/ Yahoo] failed login

<pre><div class="yregertxt"><strong>Invalid ID or password.</strong><br> Please try again.</div></pre>

== Open Questions ==
* How is this significantly different than the plethora of HTTP status codes? Most of the examples currently on this page are just failed logins. [[User:DerrickPallas|DerrickPallas]] 09:31, 14 Jul 2007 (PDT)
** [http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.2 401 Unauthorized]
** [http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.3 402 Payment Required]
** [http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.4 403 Forbidden]
** ...

== See Also ==

* [[error-message-brainstorming|error message brainstorming]]

rel-faq

2007-02-23T18:54:31Z

DerrickPallas: /* FAQ: there were TWO links to rel-license in the same list */

<h1> "rel" attribute frequently asked questions </h1>

This document serves to answer and discuss frequently asked questions about the HTML4 "rel" and "rev" attributes, and their linktype values. Specifically this document explores a number of issues common to and exposed by the various [[microformats]] which extend the HTML4 rel attribute.

__TOC__

== Authors ==
* John Allsopp, [http://westciv.com Western Civilisation]
* [http://tantek.com Tantek Çelik], [http://technorati.com Technorati, Inc]
* [[User:AndyMabbett|Andy Mabbett]]

== FAQ ==

===What microformats use "rel"? ===
*[[rel-directory]]
*[[rel-license]]
*[[rel-nofollow]]
*[[rel-tag]]
*[[rel-payment]]
*[[vote-links]]
*[http://gmpg.org/xfn/ XFN]

=== What is the proper use of the 'rel' attribute? ===

First, you can use the [http://www.w3.org/TR/html4/types.html#type-links linktype] as specified in [http://www.w3.org/TR/html4/ HTML 4]. A well known example of this is rel="stylesheet". Second, you "can extend the rel attribute using a [http://www.w3.org/TR/html4/types.html#type-links profile"], but "[http://www.w3.org/TR/html4/types.html#idx-link_type-2 HTML doesn't specify/recommend a profile format]". XMDP can be used to formally define new rel values.

=== What does a rel value really mean? ===

The rel values in HTML follow a consistent pattern which at a minimum ''implies'' a deliberate design. rel describes the relationship of a hyperlink in terms of what the destination (href) is, to the source, or from the source's perspective. rel="stylesheet" is perhaps the easiest example to understand in this manner, because it is saying that this resource over there (indicated with the href) ''is'' a "stylesheet" for the current document. Similarly, rel="help" link states that the resource indicated by the href is "help" (e.g. a help file or FAQ) for the current document. All the rest of the values defined in HTML4 also follow this pattern of being a ''noun'' which labels the resource indicated by the href, from the perspective of the current document.

=== Then what does "rev" mean? ===

"rev" is the precise opposite (or "reverse") of the "rel" attribute. E.g. a rev="help" link indicates that ''the current document'' is "help" for the resource indicated by the href.

=== Is rel single or bi directional? ===

Though the HTML4 specification is not specific on this point, all the rel values in the HTML4 specification follow a very consistent pattern that indicate a specific directionality to the value of the rel attribute. The ''only'' exception to this is the value "alternate", which, is actually inherently symmetric, so rel="alternate" means pretty much the same thing as rev="alternate". I say pretty much because in theory (and in practice) one of a pair of alternates is likely to be more definitive, and thus one is more a primary resource, with the other being an alternative. In theory you could extend rel with a new value, e.g. "original" which could be used to point back the original version of a document. This could be used for example with translations, where translations of a document would point back to the original with rel="original".

=== Are "rel" attributes, and linktypes in general, just document to document? ===

The vast majority of the rel values defined in HTML4 are from a document to a document. rel="stylesheet" is a bit of an exception, as it from an HTML document to a style sheet, which is more like a set of styling rules and instructions than a "document" in the classical sense. Two notable exceptions are rel="copyright" and rel="bookmark" which describe the relationship from the current document to (potentially) only part of a document. The 'rev' attribute adds an interesting perspective on this question. Specifically, [http://www.w3.org/TR/html4/struct/links.html#rev-link 12.3.1 of HTML4] shows an example of two links one using rel and the other using rev which mean the same thing. Thus linktypes in general may be either from a whole document or part of a document to a whole document or a part of a document. For example, the RelTag specification introduces the rel="tag" value, and notes that it indicates a relation from a document or major portion thereof to a document. Finally, XFN probably stretches rel the farthest, as it uses rel to indicate a person to person relationship. This person to person scope was not introduced by XFN, but merely adopted. It was introduced by bloggers who have taken to linking to other bloggers by name and thus using people's blog URLs as proxies for people themselves.

=== Is/Was VoteLinks a proper use of rel? ===

No. The problem with using rel for VoteLinks is made apparent with the following example:

<pre><nowiki>
<a href="http://www2005.org" rel="vote-for">WWW2005 is a great conference</a>
</nowiki></pre>

Following the reasoning in the earlier answer to the question of what a rel value means, this link would mean:

The resource indicated by http://www2005.org is a "vote-for" the current document.

That clearly doesn't make any sense, and was certainly not the intent of VoteLinks. Ironically, the reverse makes a lot more sense:

The current document is a "vote-for" the resource indicated by http://www2005.org.

And generalizing to the same cultural usage links as XFN:

The current document, as a proxy for the person who wrote it (e.g. the blogger whose blog it is),
is a vote-for the resource indicated by http://www2005.org.

Fortunately the "rev" attribute captures this "reverse" relationship semantic, and thus the above example should be written like this:

<pre><nowiki>
<a href="http://www2005.org" rev="vote-for">WWW2005 is a great conference</a>
</nowiki></pre>

And thus VoteLinks has been changed to use "rev" instead of "rel", in order to keep the well known and easily understandable "vote-for", "vote-abstain", and "vote-against" values.

=== Should 'rev' even be used ===

Given that the 'rev' attribute has been more often misused by authors than properly used ([http://code.google.com/webstats/2005-12/linkrels.html Google Code: Web Authoring Statistics: Link Relationships]) is it even a good idea to use rev at all?

The short answer is unfortunately "no". Use of "rev" SHOULD be avoided.

However, VoteLinks, is being grandfathered since it was such an early use. No future microformats should be developed that use 'rev'.

=== When a 'rel' value refers to a relationship to or from a page or document, is it referring to just the page, or the contents of the page, or both? ===

The consensus (and convention) is that such rel values are referring to the page itself including its immediate contents, but not for example to embedded contents of like images, objects, frames etc.

== See Also ==

* [[rel-directory]]
* [[rel-license]]
* [[rel-payment]]
* [[rel-tag]], [[rel-tag-faq]]
* [[rel-design-pattern]]
* [[vote-links]]
* [http://gmpg.org/xfn/ XFN], [http://gmpg.org/xfn/faq XFN FAQ]

xfolk

2007-02-17T00:59:49Z

DerrickPallas: /* Many more examples */

<h1> xFolk (RC1) </h1>

'''xFolk''' is a simple and open format for publishing collections of bookmarks. It better enables services for improving user experience and sharing data in web-based bookmarking software. xFolk may be embedded in (X)HTML, Atom, RSS, and arbitrary XML. It is one of several open [[microformats|microformat]] standards.

__TOC__

== Draft Specification ==

=== Editor/Author ===
[http://thecommunityengine.com/ Bud Gibson], [http://thecommunityengine.com The Community Engine]

=== Copyright ===
{{MicroFormatCopyrightStatement2005}}

=== Patents ===
{{MicroFormatPatentStatement}}

=== Inspiration and Acknowledgments ===
Thanks to: [http://www.cnbc.cmu.edu/~plaut/ David Plaut] who introduced me to the idea that items may partially belong to many categories at once. More recently, thanks to: [http://tantek.com/ Tantek Çelik], [http://epeus.blogspot.com/ Kevin Marks], [http://steve.osdir.com/ Steve Mallet], [http://hybernaut.com/ Brian DelVecchio], and [http://blogmarks.net François Hodierne] who have contributed to the development of xFolk with thoughtful critiques and implementations.

== Introduction ==
Social bookmarking services let users save and tag bookmarks to share with other users. Over the past year, the number of these services has mushroomed to [http://en.wikipedia.org/wiki/Social_bookmarking over 20], with popular examples including: [http://del.icio.us del.icio.us], [http://furl.net furl], [http://de.lirio.us de.lirio.us], [http://jots.com jots], and [http://blogmarks.net blogmarks].

Lack of an open, interoperable data standard is a major issue in using social bookmarking services. An open standard would make it possible to easily collect social bookmark data and remix it to invent new services along the lines of [http://gataga.com gataga]'s experimental bookmark search engine. An open standard would also make it possible to write javascripts that work across services [http://johnvey.com/features/deliciousdirector/ as some currently do for del.icio.us], enabling across-the-board improvements in user experience.

xFolk is an open social bookmarking standard that aims to achieve both benefits. Social bookmarking services that adopt xFolk will continue to differentiate themselves with data services. But, the data itself will be easy to manipulate by third party scripts and easy to share. As a result, bookmarking services will be able to offer a wider array of options to their users at low cost and focus on what truly differentiates them. Individuals or groups operating standalone bookmark repositories will have access to a wider array of functionality than they can produce on their own.

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

== Format ==
Extensive analysis of social bookmarking services and linkblogs, reported on [http://thecommunityengine.com/home/archives/xfolk elsewhere], reveals that the data published by both bookmarking services and '''many''' different linkblogs are described by the following implied schema:

* A bookmarked or tagged link.
* A title for the entry.
* Tags for the link.
* An extended description or summary of the link.

As demonstrated in early iterations of the xFolk standard, this general schema can be translated into markup by:

# creating a container element for each entry of class <code>xfolkentry</code>,
# using an <a> element for the bookmarked or tagged link of class <code>taggedlink</code>,
# using title attribute for the tagged link <a> element, if it exists, as the entry title, otherwise using the element value,
# using [[rel-tag]] for the tags, and
# using a container element of class <code>description</code>, such as <p>, for any extended description or summary.

A given xFolk entry will always contain a tagged link including a title with all other elements optional. Entries may have more than one tag as well as more than one element of class <code>description</code>. Multiple elements of class <code>description</code> are ordered by default document order. Semantic elements within xFolk entries may be nested at arbitray depths.

Many social bookmarking systems exist, each with its own markup conventions. Further, many people are already publishing personal link blogs. xFolk is designed with ease of adapting to these current practices as a primary goal. Therefore, few assumptions are made as to the exact kinds of elements used for an xFolk entry. Rather, the work of defining semantics is left entirely to the class and rel (in the case of [[rel-tag]]) attribute values.

It is expected that developers will use [http://www.w3.org/TR/xpath XPath] or equivalent syntax in accessing xFolk entry elements. a requirement for XPath is that the (X)HTML document be well-formed but not necessarily valid. Thus, while not optimal, it is possible to serviceably use xFolk in an (X)HTML document that does not validate.

=== XMDP Profile ===

See the [[xfolk-profile|xFolk profile]] for the [http://gmpg.org/xmdp XMDP] profile of xFolk.

== Example ==
Here is a sample bookmark as displayed in [http://del.icio.us del.icio.us]'s standard markup. Lines where the value of elements' class attributes must change to conform to xFolk are marked with a comment at the end.
<pre><div class="post"> 
<div>
<a class="delLink" href="http://www.sifry.com/alerts/archives/000306.html"> 
Sifry's Alerts: Technorati launches Related Tags
</a>
</div>
<div class="extended"> 
Ever wanted to see what posts are related to other posts, what tags
are related to others? Now you can! Just check under the Tag
description on most tag pages, like this one, or this one, and you'll
see the patterns. Can you smell the emergence?
</div>
<div class="meta">
to
<a class="delNav" href="/fpgibson/folksonomy">folksonomy</a> 
<a class="delNav" href="/fpgibson/technorati">technorati</a> 
... <a class="delNav" href="/url/cbcabf7de070fdb46598ee679367be49">
and 1 other person
</a>
... on 2005-04-09
</div>
</div></pre>

The equivalent in xFolk is as follows. Comments are placed at the end of lines where class attribute changes were required.
<pre><nowiki>
<div class="xfolkentry"> 
<div>
<a class="taggedlink" href="http://www.sifry.com/alerts/archives/000306.html"> 
Sifry's Alerts: Technorati launches Related Tags
</a>
</div>
<div class="description"> 
Ever wanted to see what posts are related to other posts, what tags
are related to others? Now you can! Just check under the Tag
description on most tag pages, like this one, or this one, and you'll
see the patterns. Can you smell the emergence?
</div>
<div class="meta">
to
<a rel="tag" href="/fpgibson/folksonomy">folksonomy</a> 
<a rel="tag" href="/fpgibson/technorati">technorati</a> 
... <a class="delNav" href="/url/cbcabf7de070fdb46598ee679367be49">
and 1 other person
</a>
... on 2005-04-09
</div>
</div>
</nowiki></pre>

Converting markup to be conformant with xFolk is almost always this easy. The advantage of xFolk is that it provides one set of class attributes that can be reused across all services and link blogs, almost always with no loss of granularity. The next section presents several more examples to illustrate this point.

== Many more examples ==

We have numerous examples to help developers incorporate xFolk into their sites.

=== In the wild ===

These are real live examples of functioning systems that publish bookmarks in xFolk. These are a great place to start for anyone looking for examples "in the wild" to try parsing, indexing, organizing etc. If you publish using xFolk, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.

* [http://waferbaby.com/hussy waferbaby's Hussy] currently publishes links using xFolk.
* [http://smarking.com/ Smarking] currently publishes all shared links (including search results) using xFolk.
* [http://unalog.com unalog] currently publishes all shared links (including search results) using xFolk.
* [http://de.lirio.us de.lirio.us] currently publishes its bookmarks using xFolk (with the deprecated class attribute <code>extended</code> in place of <code>description</code>, see [[xfolk-profile | the XMDP]]).
* [http://dev.blogmarks.net/wiki/BlogSync blogmarks] currently exports bookmarks to blogs in xFolk (scroll down to the export example on the page; the deprecated class attribute <code>extended</code> is used in place of <code>description</code>, see [[xfolk-profile | the XMDP]]).
* [http://thecommunityengine.com The Community Engine] uses xFolk (with the deprecated class attribute <code>extended</code> in place of <code>description</code>, see [[xfolk-profile | the XMDP]]) for its [http://thecommunityengine.com/home main entries] and for its [http://thecommunityengine.com/webcites republished bookmarks].
* [http://groovymother.com/links/ Groovy Links] is a link blog which is marked up with xFolk.

=== Additional social bookmarking services ===

This example illustrates how xFolk may be applied to one additional service:

* [[xfolk-scuttle | scuttle]]

=== Link blogs ===

Social bookmarking services are only the most recent examples of people publishing links. Link blogs have been around almost since the beginning of blogging. They represent somewhat more of a challenge for xFolk because their markup tends to be less semantic from the outset. The following examples illustrate some particular challenges and how they can be overcome.

* [[xfolk-kottke | kottke]]
* [[xfolk-pollas | pollas]]
* [[xfolk-jacobian | jacobian]]
* [[xfolk-julian-bez | julian-bez]]

=== Spam ===
Some spammers are adding xFolk tags to their link farms. (It's probably a bad idea to actually link to these sites.) For example,
* phontron.info

== Implementations ==

The following implementations have been developed which generate or use xFolk. If you have an xFolk implementation, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.

* [http://buzka.com Buzka], a social bookmarking service, now supports xFolk
* [http://blip.tv Blip.tv], a video hosting site, now [http://blog.blip.tv/blog/2006/08/19/blip-supports-xfolk/ supports xFolk].
* [http://www.s9y.org/ Serendipity], a PHP-powered, flexible Blogging/CMS application, now has a [http://www.numblog.de/archives/241-Social-Bookmarks-Plugin-for-Serendipity.html social bookmarks plugin] that supports xFolk.
* [http://claimid.com claimID] has implemented xFolk for people's links.
* [http://ma.gnolia.com ma.gnolia] now supports xFolk.
* [http://smarking.com/ Smarking.com] (a social bookmarking service) marks up their tagged links with xFolk! Hat tip: [http://3spots.blogspot.com/2006/05/social-bookmarking-smarking.html 3spots: Social + bookMARKING = Smarking] which itself is an [[hreview|hReview]].
* [http://blog.codeeg.com/2006/03/20/flock-tails-flocktails/ Flocktails] - port of Tails extension for Flock 0.5.12 that looks for hCards, hCalendar, xFolk and hReview and tosses them into a handy topbar
* [http://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.
* Bud Gibson and Mike Migurski [http://thecommunityengine.com/home/archives/2005/09/vegomatic_an_al.html have written] [http://thecommunityengine.com/veg-o-matic veg-o-matic], an xFolk reblogging tool and service.
* [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 xFolk and [http://blog.davidjanes.com/mtarchives/2005_08.html#003379 provides a popup menu of actions]. ''This will work with FireFox 1.5+/GreaseMonkey 0.6.4+ now.''
* [http://www.midgard-project.org/midcom-permalink-6416db7e1f0e297b4cf3dcc285702a8d net.nemein.bookmarks], the bookmark manager in [http://www.midgard-project.org/ Midgard CMS] uses xFolk as the native output format, with added <code>abbr class=posted</code> for publication date and <code>abbr class=poster</code> for user who added the bookmark. See [http://bergie.iki.fi/links/ example]
* [http://de.lirio.us de.lirio.us] currently publishes its bookmarks using xFolk 0.4 (the class attribute <code>extended</code> is used in place of description).
* [http://dev.blogmarks.net/wiki/BlogSync blogmarks] currently exports bookmarks to blogs in xFolk 0.4 (scroll down to the export example on the page; the class attribute <code>extended</code> is used in place of <code>description</code>).
* [http://pokkari.com/microformat/javadoc/ Sivitols] is a Java library for microformats. Currently only the xFolk RC1 standard is implemented, but additional microformat support is planned. (adapted from [http://blog.blip.tv/blog/microformats/])

== References ==
=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [[rel-tag]]

=== Informative References ===
* [http://thecommunityengine.com/home/archives/xfolk articles about xFolk]
* [http://thecommunityengine.com/home/archives/tags/microformats articles about the business value of microformats]
* [http://gataga.com gataga social bookmark search engine]
* [http://johnvey.com/features/deliciousdirector/ an ajax based interface for del.icio.us]
* [http://en.wikipedia.org/wiki/Social_bookmarking social bookmarking defined at wikipedia]

=== Similar Work ===
* [[hreview | hReview]]

== Work in progress ==
Although this specification has recently begun to stabilize as indicated by the version RC1, it is still a work in progress. If warranted, I am prepared to go through multiple release candidates to achieve the narrow purpose of making bookmark entries more genrally accessible with as with as light weight a format as possible. All changes since the last iteration have been motivated by the implementation experience of developers attempting to achieve this narrow aim. Further changes will also most likely be motivated by implementation concerns. See "future directions" below for additional microformat possibilities.

=== Changes since xFolk 0.4 ===
The class attribute value <code>extended</code> was deprecated in favor <code>description</code> to better conform with other microformat usage and some requests during implementation. The other change has been to allow use of multiple elements of class <code>extended</code> based on some use cases discovered in implementation.

=== Future directions ===
There are several extensions one might imagine for xFolk. Frequently, these extensions are best achieved by combining xFolk with another microformat. For instance, one might want to indicate his or her evaluation of the bookmarked item. This might be achieved by using [[vote-links | Vote Links]] or [[hreview | hReview]] with xFolk.

One can also imagine extending xFolk to provide data conformant with various social bookmarking service APIs, for instance to provide all bookmarks by tag. These APIs are currently too fluid for specification in any kind of standard. The APIs and the functionality they provide represent one way social bookmarking services and meta services can differentiate themselves.

A companion format called "xFolk definition" is under development. xFolk definition will provide a means of explicitly defining the tags used in social bookmarks.

=== Brainstorming ===
* [[xfolk-brainstorming|xFolk brainstorming]]

== Discussions ==

=== Q&A ===
* If you have any questions about xFolk, check the [[xfolk-faq|xFolk FAQ]], and if you don't find answers, add your questions!

=== Issues ===
* Please add any issues with the specification to the separate [[xfolk-issues|xFolk issues]] document.

==Related pages==
{{template:xfolk-related-pages}}

Main Page

2007-02-17T00:55:21Z

DerrickPallas: /* Exploratory Discussions */

__NOTOC__
<h1>Microformats Wiki</h1>

'''Hello!''' Welcome to the microformats wiki. If this is your first visit, please see the [[introduction]] page.

Please read [[how-to-play]] before making any edits.

Please read [[process]] before proposing any new microformats.

__TOC__

==Getting Started==

[[what-are-microformats|What are microformats]]? [[what-can-you-do-with-microformats|What can you do with them]]?

The [http://microformats.org/about/ about page], [http://microformats.org/ latest news], plus recent [[press]], [[presentations]], [[podcasts]], and [[screencasts]] are also good places for some background information. Our [[cheatsheets]] are handy if you need a quick reminder about a particular microformat.

Frequently asked questions about the wiki and microformats in general are answered in the [[faq|FAQ]], and there is a [[glossary]].

Want to learn more in person? Check out [[events|microformats events]].

==Definition==

One popular definition from our [http://microformats.org/discuss/ mailing list] (see also: [[mailing-lists]]) is "simple conventions for embedding semantics in HTML to enable decentralized development." More precisely, microformats can be defined as:
:simple conventions
:for embedding semantic markup
::for a specific problem domain
:in human-readable (X)HTML/XML documents, Atom/RSS feeds, and "plain" XML
::that normalize existing content usage patterns
::using brief, descriptive class names
::often based on existing interoperable standards
:to enable decentralized development
::of resources, tools, and services

Simply put: "Microformats are a codification of convention." -- [http://easy-reader.net Aaron Gustafson]

"Or do you just use your browser to browse? That's so 20th century." -- [http://diveintomark.org Mark Pilgrim]

== How to contribute ==

Do you want to help take microformats to the next level? You can:

*Check out our open [[to-do|to do list]] for things to help get done.
*Join the [http://microformats.org/discuss mailing lists] and [[irc|IRC Channel]] to learn and help answer questions about microformats.
*[[advocacy|Advocate]] the use of microformats.
*help to [[Main_Page#microformats_wiki_in_other_languages|translate the microformats wiki into other languages]] to make microformats globally accessible.

== Specifications ==
[[microformats|Microformats]] open standards specifications (see also: [[implementations]], [[examples-in-the-wild]])
* [[hcalendar|hCalendar]] - [http://microformats.org/code/hcalendar/creator hcalendar creator]
* [[hcard|hCard]] - [http://microformats.org/code/hcard/creator hcard creator]
* [[rel-license]]
* [[rel-nofollow]]
* [[rel-tag]]
* [[vote-links|VoteLinks]]
* [http://gmpg.org/xfn/ XFN] (see also: [[xfn-implementations]])
* [http://gmpg.org/xmdp/ XMDP]
* [[xoxo|XOXO]]

== Drafts ==
* [[adr|adr]]
* [[geo|geo]]
* [[hatom|hAtom]]
* [[hresume|hResume]]
* [[hreview|hReview]] - [http://microformats.org/code/hreview/creator hreview creator]
* [[rel-directory]]
* [[rel-enclosure]]
* [[rel-home]]
* [[rel-payment]]
* [[robots-exclusion|Robots Exclusion]]
* [[xfolk|xFolk]]

== Design Patterns ==

{{design_patterns}} 

== Exploratory Discussions ==
Per the microformats [[process]]: research and analysis of real-world [[examples]], existing formats, and brainstorming to motivate the microformat. Please check [[rejected-formats]] before making additions.

* alternates [[alternates-brainstorming|alternates brainstorming]], [[alternates-examples|alternates examples]]
*[[attention]]
* blog description [[blog-description-examples|blog description examples]]
* blog info [[blog-info-examples|blog info examples]]
* blog post [[blog-post-examples|examples]], [[blog-post-formats|blog post formats]], and [[blog-post-brainstorming|blog post brainstorming]] (yielded the [[hatom|hAtom]] draft)
* book [[book-examples|book examples]], [[book-formats|book formats]], and [[book-brainstorming|book brainstorming]]
* chat [[chat-examples|chat examples]], [[chat-formats|chat formats]], and [[chat-brainstorming|chat brainstorming]]
* citation [[citation|citation effort]], [[citation-examples|citation examples]], [[citation-formats|citation formats]], [[citation-brainstorming|citation brainstorming]], and [[citation-faq|citation FAQ]]
* code [[code-examples| code examples]], [[code-brainstorming|code brainstorming]]{{NewMarker}}
* comment [[comment-problem|comment problem]], [[comment-examples|comment examples]], and [[comments-formats|comment formats]] (Some stuff needs to be extracted from [[comments-formats]])
* [[collection-description|collection description]] {{NewMarker}}
* [[course-catalog]]; [[course-catalog-examples]] {{NewMarker}}
* [[currency]]; [[currency-examples]]; [[currency-brainstorming]]; [[currency-proposal]]; [[currency-issues]]
* [[depend-examples]]: examples of dependency graphs, especially as they relate to software {{NewMarker}}
* [[digital-signatures]]: incorporation of digital signatures in Microformatted data; ([[digitalsignature-examples|digital-signature examples]], [[digitalsignature-brainstorming|digital-signatures brainstorming]]) {{NewMarker}}
* directions [[directions-examples|directions examples]] {{NewMarker}}
* directory inclusion [[directory-inclusion-examples|directory inclusion examples]], [[directory-inclusion-formats|directory inclusion formats]]. (see also [[rel-directory]])
* distributed conversation [[distributed-conversation|distributed conversation overview]], [[distributed-conversation-brainstorming|distributed conversation brainstorming]], [[distributed-conversation-examples|distributed conversation examples]], and [[distributed-conversation-formats|distributed conversation formats]]
* forms [[forms-examples|forms examples]]
* genealogy [[genealogy-formats|genealogy examples]]
* group [[group-brainstorming|group brainstorming]] and [[group-examples|group examples]]
* items [[items-brainstorming|items brainstorming]] and [[items-examples|items examples]
* hash [[hash-examples|hash examples]]
* job listing [[job-listing-examples|job listing examples]] and [[job-listing-brainstorming|job listing brainstorming]]
* last modified [[last-modified-examples|last modified examples]], [[last-modified-formats|last modified formats]], and [[last-modified-brainstorming|last modified brainstorming]]
* hListing [[hlisting-proposal|hListing proposal]], and [[hlisting-feedback|hListing feedback]]
** Also, listing [[listing-examples|examples]], [[listing-formats|formats]], and [[listing-brainstorming|brainstorming]]
* [[product|hProduct]] - [[product-brainstorming|hProduct brainstorming]] | [[product-examples|hProduct examples]]
* location [[location-formats|location formats]]. (see also [[adr]] and [[geo]])
* [[luna]] ([[geo]]-like co-ordinates, for places on The Moon) - see also [[geo-extension-strawman]] a possible implementation {{UpdateMarker}}
* [[mars]] ([[geo]]-like co-ordinates, for places on the planet Mars) - see also [[geo-extension-strawman]] a possible implementation {{UpdateMarker}}
* measures and measurement units [[measure]]
* [[media-info]] ([[media-info-examples|media-info examples]], [[media-info-formats|media-info formats]], [[media-info-brainstorming|media-info brainstorming]])
* meeting minutes [[meeting-minutes-examples|meeting minutes examples]], [[meeting-minutes-formats|meeting minutes formats]], and [[meeting-minutes-brainstorming|meeting minutes brainstorming]]
* metalink [[metalink-examples|metalink examples]] {{NewMarker}}
* microsummary [[microsummary-brainstorming|microsummary brainstorming]]
* [[mfo-examples|MFO examples]]
* music [[music-examples|music examples]]
* [[operating-hours]]: [[operating-hours-examples]] ..of stores, restaurants, etc. {{UpdateMarker}}
* [[payment]]
* photo note [[photo-note-examples|photo note examples]]
*[[question-answer]], [[question-answer-brainstorming]]; [[question-answer-examples]] {{NewMarker}}
* recipe [[recipe-examples|recipe examples]], [[recipe-brainstorming]] {{UpdateMarker}}
* rel-product [[rel-product-brainstorming|rel-product brainstorming]]
* requirements testing [[requirements-testing|requirements testing overview]], and [[requirements-testing-examples|requirements testing examples]]
* [[rest-examples|REST examples]]
* resume [[resume-brainstorming|resume brainstorming]], and [[resume-formats|resume formats]]
* review [[review-examples|review examples]], and [[review-formats|review formats]] (yielded the [[hreview|hReview]] draft)
* search results [[search-results-example|search results example]]
* show [[show-brainstorming|show brainstorming]]
* showroll [[showroll-brainstorming|brainstorming]]
* [[species]] - for the marking up of the scientific names of living things: [[species-examples]]; [[species-brainstorming]] {{UpdateMarker}}
* table [[table-examples|examples]]
* tagspeak [[tagspeak-examples|tagspeak examples]]
* tagcloud [[tagcloud-examples|tagcloud examples]], and [[tagcloud-brainstorming|tagcloud brainstorming]].
* [[thoughts-on-extending-the-geo-microformat|thoughts on extending the geo microformat]], [http://microformats.telemetry.gr examples] {{NewMarker}}
* transit table [[transit-table-examples|transit table examples]]
* [[uid]]
* widget [[widget-examples|widget examples]], and [[widget-brainstorming|widget brainstorming]]
* [[wiki-formats|wiki formats]]
* work of art [[work-of-art|work of art overview]], [[workofart-examples|work of art examples]], [[workofart-formats|work of art formats]], and [[workofart-brainstorming|work of art brainstorming]]
*[[xmdp-brainstorming|XMDP brainstorming]] (see also [[xmdp-faq]])

== Examples ==
* [[examples-in-the-wild]]
* [[implementations]]
* [[zen-garden]]

== Tools, Test Cases and Additional Research ==

The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting tools and services that need to process more than one microformat. This section is intended for editors, parsers, validators, test cases, and other information relevant across multiple microformats.

*[[accessibility]]
*[[faqs-for-rdf]]
*[[icalendar-implementations]]
*[[parsing-microformats]]
*[[selected-test-cases-from-the-web]]
*[http://hg.microformats.org/ Source code repository] -- [[mercurial-quick-start|HowTo: Download code from the repository]]
*[[vcard-implementations]], [[vcard-errata]], [[vcard-suggestions]]
*[[why-are-content-standards-hard]]
* [[profile-examples-in-wild|Profile examples, in the wild]]

== shared work areas ==
* [[buttons]]
* [[icons]] {{NewMarker}}
* [[spread-microformats]] {{NewMarker}}
* [[demo]] - a page with links for quickly demonstrating microformats working in practice.
* [[events]]
* [[to-do]]
* [[user-interface]]
* [[marked-for-deletion]]
* [[microformats-issues]] {{NewMarker}} - issues related to more than one microformat.

== microformats wiki in other languages ==

You may read and edit microformats articles in many other languages:

* languages with over 100 articles
** [[Main_Page-fr|Français (French)]] {{UpdateMarker-fr}}
* languages with over 10 articles
** [[Main_Page-pt-br| Português (Brazilian Portuguese)]] {{NewMarker-pt-br}}
** [[Main_Page-ja|日本語 (Japanese)]]
* languages with over 2 articles
** [[Main_Page-es|Español (Spanish)]]
** [[Main_Page-de|Deutsch (German)]]

==== microformats translations elsewhere ====
These are off-site pages/sites with translations about microformats. If you are working on one of these, please consider translating the main microformats website!
* [http://mikroformate.pbwiki.com/ Deutsch (German) mikroformate.pbwiki.com] {{NewMarker-de}}

=== Start a microformats wiki in another language ===

Don't see the language you want? Help translate the microformats wiki into another language!

We're still figuring this out.

For now, see the [http://en.wikipedia.org/wiki/Wikipedia:Multilingual_coordination Wikipedia page on Multilingual coordination], and [http://meta.wikimedia.org/wiki/How_to_start_a_new_Wikipedia How to start a new Wikipedia] for some good general tips, advice, and community conventions.

You may want to start with the list of [[stable-pages]], which are pages that are relatively stable, and have only minimal/editorial changes, which makes them much easier to keep in sync with the English versions, by using the [[Special:Watchlist|my watchlist]] feature (use it to watch the pages you've translated for changes).

Page naming: for the translated version of a page, use the same name for the page, and simply add the RFC 3066 language identifier code as a dash suffix. [http://google.con google] E.g. for the French version, [[Main_Page]] becomes [[Main_Page-fr]], and [[how-to-play]] becomes [[how-to-play-fr]].

==== more languages folks want to see ====

* Chinese: 微格式 (Microformats) (see [http://msittig.blogspot.com/2005/11/since-i-translated-schedule-of.html source of translation])
* Does somebody want to see a Dutch translation???

xhours

2007-02-04T17:57:29Z

DerrickPallas: /* Problems */

<h1>xHours</h1>

This page documents an effort to define a simple, open, and semantic format for marking up the operating hours of stores, restaurants, museums, offices, and other estabishments that have set hours and are open on a regular basis. xHours is closely based on the [[hCalendar]] microformat.

__TOC__
== Draft specification ==

=== Editor/Author ===
* [http://dragotown.com Nick Drago]

=== Process ===
This document's current status is an "exploratory discussion".

Per the microformats [[process]], these sections of this document are in development:
* examples
* formats
* brainstorming

Please feel free to help by contributing your thoughts and ideas.

== Introduction ==
This effort came about as a result of:

* the need for a human and machine readable markup format that can be used to define the operating hours of establishments
* the belief that the hCalendar format is not fully appropriate (not yet capable, etc.) for defining repeating events to the extent needed

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

This document proposes the introduction of a format which is a close subset of the [[hCalendar]] microformat, and thus the iCalendar standard, in semantic XHTML. Organizations and businesses can both embed their operating hours directly in their web pages and style them with CSS to make them appear as desired. In addition, this format would enable applications to retrieve such data directly from web pages without having to reference a separate file.

== Current example ==
The website of a national chain of retail stores (we'll call them Store XYZ) features a store locater, in which one enters their city and state and are provided with a listing of stores in their area. Below is an excerpt of one of the listings (slightly modified):
<pre>
<b>Store #5555</b><br>
Address, City, State, Zip <br>
<b>Hours:</b> Mon-Sat 10:00am-9:00pm<br>Sun 11:00am-7:00pm
<br><br>
<b>This store also features:</b><br>
- Mobile electronics installation <br>
</pre>

== Brainstorming ==
There are several main components to this listing:
* Location
** The establishment name
** The establishment address
* Hours
** Day of week
** Open time
** Close time

=== Using iCalendar ===
Using the current iCalendar standard, and using the date conventions defined in [http://en.wikipedia.org/wiki/ISO_8601#Time_interval ISO 8601], Store XYZ's store hours could be expressed as an interval:
<pre>
2007-01-01T10:00:00Z/2007-01-01T21:00:00Z
</pre>
Note that this defines the hours as an event occurring on January 1, 2007 from 10:00a.m. to 9:00p.m. (21:00).

Now, to make this event repeat, "R[n]/" is prefixed, with n being defined as 365:
<pre>
R365/2007-01-01T10:00:00Z/2007-01-01T21:00:00Z
</pre>
This would repeat this event 365 times, for the 365 days in a year. However, this is not appropriate, because Store XYZ is open during different hours during different days of the the week.

=== Using numbers for the weekday ===
The date could be marked up more simply by using an extension of [http://en.wikipedia.org/wiki/ISO_8601#Check_digit_.28weekday.29 ISO 8601]. ISO 8601 defines [http://en.wikipedia.org/wiki/ISO_8601#Week_dates weekday numbers] as:
<blockquote>
a digit [D] from 1 through 7, beginning with Monday and ending with Sunday
</blockquote>

xHours will use the digit (1 through 7, Monday through Sunday) to represent the day of the week.

== Format ==
The proposed method of marking up the date and time an establishment is open (using xHours) is the following:
<pre>
DTSTART:1-6-T10:00:00Z //this shows that Store XYZ opens Monday- Saturday (1-6) at 10:00
DTEND:1-6-T21:00:00Z// this shows that Store XYZ closes Monday- Saturday (1-6) at 21:00
</pre>

xHours markup (formatted similarly to hCalendar):

<pre><nowiki>
<div class="vevent">
<h3 class="summary">Store XYZ #5555</h3>
<p class="description">Store XYZ #5555's Hours</p>
<p>We will be open <abbr class="dtstart" title="1-6-T10:00:00Z">
Monday through Saturday from 10:00AM</abbr> until
<abbr class="dtend" title="1-6-T21:00:00Z">9:00PM</abbr></p>
<p>At our main location: <span class="location">Store #5555 in Anytown, USA</span></p>
</div>
</nowiki></pre>

== Problems ==
* How could multiple sets of hours be defined in the same paragraph? e.g. define Monday-Saturday's hours and Sunday's hours in the same vevent
* Are the weekday numbers (1-7) appropriate?
** No, it is not OK because of internationalization. In different cultures the week starts on different days.
**They are defined in ISO 8601, but this is an extension of that format.

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

=== Informative References ===
* [http://en.wikipedia.org/wiki/ISO_8601 Wikipedia article on ISO 8601]

rel-tag-faq

2007-02-03T20:04:57Z

DerrickPallas: in general, search engines do look at term relevance

= rel-tag frequently asked questions =

This document serves to answer and discuss frequently asked questions specifically about the [[rel-tag]] microformat. You may want to read the [[rel-faq]] first as it answers many common questions about the HTML4 “rel” and “rev” attributes, and their linktype values. If you have a new question to ask, first consider asking on the [http://microformats.org/mailman/listinfo/microformats-discuss/ microformats-discuss list].

== Q&A ==

# ''Where does a tagging link belong? Does the tagging link only need to appear in my Web feed (RSS / Atom)? Does the tagging link need to appear on the page where my specific blog entry lies? Does the tagging link need to appear everywhere that I can possibly imagine?''
#* In short, tagging links belong in all the places and formats in which you published tagged content. The Web page is the primary location where users read content and where search engines index. Thus the Web page is a place where you should absolutely include your [[rel-tag]] links. To tag your blog posts, put the [[rel-tag]] links inside them, visibly. The Web feeds are simply alternate ways of publishing your blog posts, and thus should include the full content of your blog posts, [[rel-tag]] links intact.
# ''Where shouldn't I use rel-tag?''
#* rel-tag expresses a particular relationship (a) between the page you are on and (b) the target of a link. If you're not asserting this relationship, don't use rel-tag. In particular:
#** don't use rel-tag in [http://en.wikipedia.org/wiki/Tag_cloud Tag Clouds]
#** don't use rel-tag to refer to the pages http://www.technorati.com/tag/xyz, http://del.icio.us/tag/xyz, http://www.flickr.com/photos/tags/xyz/ (and so forth) if you're not asserting "this page is tagged 'xyz'"
# ''The format specifies that the tag must “come after the last / in the path”. Will something like <code><nowiki>http://example.com/index.php/TAG</nowiki></code> work? Or does it have to be a “real” directory or [http://httpd.apache.org/docs/2.2/mod/mod_rewrite.html mod_rewrite]? -- [[User:Singpolyma|singpolyma]] 23:51, 24 Jan 2006 (PST)''
#* The key is the URL. Whether that URL is generated from a database or a directory does not matter. The URL matters.
#** My question, however, was about whether that URL form ( <code><nowiki>http://example.com/index.php/TAG</nowiki></code> ) would be valid, since there is the dot in “index.php”.
#*** Yes, the URL in the example is valid (or legal or conformant or whatever you want to call it to minimize confusion). The dot (period, full stop, U+002E) is free to appear in most places in a URL, even in the middle of a path-segment that is not the last path-segment. (The latest specification for URLs, “[http://gbiv.com/protocols/uri/rfc/rfc3986.html Uniform Resource Identifier (URI): Generic Syntax]”, is RFC 3986.)
# ''I’m developing a web application which uses tagging, and so of course I want to use [[rel-tag]]. For this application, I want nice, clean URLs. I was planning to use [http://httpd.apache.org/docs/2.2/mod/mod_rewrite.html mod_rewrite] to map a clean URL onto my underlying scripts. How do I use Apache’s [http://httpd.apache.org/docs/2.2/mod/mod_rewrite.html mod_rewrite] to map <code><nowiki>http://example.org/~user/app/tag/car</nowiki></code> to <code><nowiki>http://example.org/~user/app/script.php?tag=car</nowiki></code> ?''
#* One solution involves changing the script to inspect the path for the tag (via the variable “PATH_INFO”), rather than inspecting the query:
<pre><nowiki><Directory "/home/user/public_html/app/>
RewriteEngine On
RewriteRule ^tag/([^/]+)$ script.php/$1 [last]
</Directory></nowiki></pre>
#* For people who can edit the server’s main configuration file, the following untested configuration code may work. Corrections are welcome.
<pre><nowiki>RewriteEngine On
RewriteMap tag int:escape
RewriteRule ^/~user/app/tag/([^/]+)$ /~user/app/script.php?tag=${tag:$1} [last]</nowiki></pre>
#* The following configuration code, left over from a previous contribution to this document, does a poor job according to tests. The following code fails to enforce the [[rel-tag]] rules about the tag corresponding to the last non-empty path-segment. The following code fails to transcode the tag for safe use in the URL query. Consider that a request on <code><nowiki>http://example.org/~user/app/tag/</nowiki></code> would map internally to a request on <code><nowiki>http://example.org/~user/app/script.php?tag=</nowiki></code> . Consider that a request on <code><nowiki>http://example.org/~user/app/tag/not-a-tag/the-tag</nowiki></code> would map internally to a request on <code><nowiki>http://example.org/~user/app/script.php?tag=not-a-tag/the-tag</nowiki></code> . Consider that a request on <code><nowiki>http://example.org/~user/app/tag/the-tag/</nowiki></code> would map internally to a request on <code><nowiki>http://example.org/~user/app/script.php?tag=the-tag/</nowiki></code> . Consider that a request on <code><nowiki>http://example.org/~user/app/tag/attack&intent=destroy</nowiki></code> would map internally to a request on <code><nowiki>http://example.org/~user/app/script.php?tag=attack&intent=destroy</nowiki></code> .
<pre><nowiki><Directory "/home/user/public_html/app/>
RewriteEngine On
RewriteRule ^tag/(.*)$ script.php?tag=$1
</Directory></nowiki></pre>
<ol start="4">
<li>''Does a rel tag still have meaning if the link redirects? If the HTTP server returns a 302 status code, does the rel-tag have meaning? Is there a formal rule that indexers should follow the link to the final, resolved destination? Or is there a formal rule that a rel tag should be ignored if URL of its link does not return a status code of 200?''
* ..next answer
</li>
</ol>

===CSS selector===
*How do you write a CSS selector for rel-tag?
** <code>a[rel~="tag"] { color: green }</code>

===Are tags case sensitive?===
*Are tags case sensitive. Is "Dog" the same tag as "dog" and "DOG"?
**{{AwaitingAnswer}}

===Multi-word tags===
*How should a multi-word tag be made? For instance, if using Wikipedia as a name space, a page about a Black Redstart (a bird) would be tagged '''Black_Redstart''', with an underscore [http://en.wikipedia.org/wiki/Black_Redstart]. Is there any way of aliasing alternatives ("BlackRedstart", "Black-Redstart", etc.)? Is any particular format preferable?
**{{AwaitingAnswer}}

===Tags with file extensions===
*Is <code><a rel=tag href="http://example.com/cheese.htm">cheese</a></code> a valid tag, for "cheese"? Ditto <code>.asp</code> or <code>.php</code> variants? If not, why not?

No, you cannot use a tag URL with a file extension - unless you want the extension included in all of your tags. Explanation from Brian Suda on the microformats-discuss list:

--- the spec says:
... the last segment of the path portion of the URI (after the final
"/" character) contains the tag value.

What that string is, is irrelavant. It could be /file/my.pdf and the
tag would be "my.pdf" it could be /downloads/my.big.file.pdf and the
tag would be "my.big.file.pdf". A tag is everything after the last
slash (unless the last char is a slash). So if that is a file or a
folder, or a file that does not have an extention, or a folder that
has a '.' in it's name.

===What about Scope?===
Since rel-tag is a feature used in many other microformats, the question often arises: "What is the scope of the tag?" For instance, a rel-tag may appear inside of an [[xfolk xFolk]] entry and on first glance it may appear that the tag should only apply to that entry. However, current publishing practice seems to indicate anything appearing on a page is likely related to the content of the page. Therefore, the interpretation is that not only does the rel-tag apply its direct container but to all containers and to the document as a whole; it contains the xFolk entry. This is a departure from strict knowledge theory in favor of real-world usage.

As another example, you may link to your friend Joe with XFN and hCard, indicating in his categories that Joe is interested in swimming, which you loathe. Since the article is primarily about you and not about Joe's hobbies and because the rel-tag is inside an hCard, you may expect that the rel-tag does not apply to the document; however, the document does contain information about swimming, albeit tiny, namely that your friend likes it. In this way, rel-tag is binary: it indicates direction (yes or no) but not magnitude. This equivalent to a free-text search sans [[http://en.wikipedia.org/wiki/tf-idf tf-idf]]; i.e. without a notion of term relevance.

The upshot of this is that rel-tags can have downward scope but not upward scope.

==Related pages==
{{rel-tag-related-pages}}
**{{AwaitingAnswer}}

rel-tag-faq

2007-02-03T19:43:41Z

DerrickPallas: /* not everyone uses Apache */

= rel-tag frequently asked questions =

This document serves to answer and discuss frequently asked questions specifically about the [[rel-tag]] microformat. You may want to read the [[rel-faq]] first as it answers many common questions about the HTML4 “rel” and “rev” attributes, and their linktype values. If you have a new question to ask, first consider asking on the [http://microformats.org/mailman/listinfo/microformats-discuss/ microformats-discuss list].

== Q&A ==

# ''Where does a tagging link belong? Does the tagging link only need to appear in my Web feed (RSS / Atom)? Does the tagging link need to appear on the page where my specific blog entry lies? Does the tagging link need to appear everywhere that I can possibly imagine?''
#* In short, tagging links belong in all the places and formats in which you published tagged content. The Web page is the primary location where users read content and where search engines index. Thus the Web page is a place where you should absolutely include your [[rel-tag]] links. To tag your blog posts, put the [[rel-tag]] links inside them, visibly. The Web feeds are simply alternate ways of publishing your blog posts, and thus should include the full content of your blog posts, [[rel-tag]] links intact.
# ''Where shouldn't I use rel-tag?''
#* rel-tag expresses a particular relationship (a) between the page you are on and (b) the target of a link. If you're not asserting this relationship, don't use rel-tag. In particular:
#** don't use rel-tag in [http://en.wikipedia.org/wiki/Tag_cloud Tag Clouds]
#** don't use rel-tag to refer to the pages http://www.technorati.com/tag/xyz, http://del.icio.us/tag/xyz, http://www.flickr.com/photos/tags/xyz/ (and so forth) if you're not asserting "this page is tagged 'xyz'"
# ''The format specifies that the tag must “come after the last / in the path”. Will something like <code><nowiki>http://example.com/index.php/TAG</nowiki></code> work? Or does it have to be a “real” directory or [http://httpd.apache.org/docs/2.2/mod/mod_rewrite.html mod_rewrite]? -- [[User:Singpolyma|singpolyma]] 23:51, 24 Jan 2006 (PST)''
#* The key is the URL. Whether that URL is generated from a database or a directory does not matter. The URL matters.
#** My question, however, was about whether that URL form ( <code><nowiki>http://example.com/index.php/TAG</nowiki></code> ) would be valid, since there is the dot in “index.php”.
#*** Yes, the URL in the example is valid (or legal or conformant or whatever you want to call it to minimize confusion). The dot (period, full stop, U+002E) is free to appear in most places in a URL, even in the middle of a path-segment that is not the last path-segment. (The latest specification for URLs, “[http://gbiv.com/protocols/uri/rfc/rfc3986.html Uniform Resource Identifier (URI): Generic Syntax]”, is RFC 3986.)
# ''I’m developing a web application which uses tagging, and so of course I want to use [[rel-tag]]. For this application, I want nice, clean URLs. I was planning to use [http://httpd.apache.org/docs/2.2/mod/mod_rewrite.html mod_rewrite] to map a clean URL onto my underlying scripts. How do I use Apache’s [http://httpd.apache.org/docs/2.2/mod/mod_rewrite.html mod_rewrite] to map <code><nowiki>http://example.org/~user/app/tag/car</nowiki></code> to <code><nowiki>http://example.org/~user/app/script.php?tag=car</nowiki></code> ?''
#* One solution involves changing the script to inspect the path for the tag (via the variable “PATH_INFO”), rather than inspecting the query:
<pre><nowiki><Directory "/home/user/public_html/app/>
RewriteEngine On
RewriteRule ^tag/([^/]+)$ script.php/$1 [last]
</Directory></nowiki></pre>
#* For people who can edit the server’s main configuration file, the following untested configuration code may work. Corrections are welcome.
<pre><nowiki>RewriteEngine On
RewriteMap tag int:escape
RewriteRule ^/~user/app/tag/([^/]+)$ /~user/app/script.php?tag=${tag:$1} [last]</nowiki></pre>
#* The following configuration code, left over from a previous contribution to this document, does a poor job according to tests. The following code fails to enforce the [[rel-tag]] rules about the tag corresponding to the last non-empty path-segment. The following code fails to transcode the tag for safe use in the URL query. Consider that a request on <code><nowiki>http://example.org/~user/app/tag/</nowiki></code> would map internally to a request on <code><nowiki>http://example.org/~user/app/script.php?tag=</nowiki></code> . Consider that a request on <code><nowiki>http://example.org/~user/app/tag/not-a-tag/the-tag</nowiki></code> would map internally to a request on <code><nowiki>http://example.org/~user/app/script.php?tag=not-a-tag/the-tag</nowiki></code> . Consider that a request on <code><nowiki>http://example.org/~user/app/tag/the-tag/</nowiki></code> would map internally to a request on <code><nowiki>http://example.org/~user/app/script.php?tag=the-tag/</nowiki></code> . Consider that a request on <code><nowiki>http://example.org/~user/app/tag/attack&intent=destroy</nowiki></code> would map internally to a request on <code><nowiki>http://example.org/~user/app/script.php?tag=attack&intent=destroy</nowiki></code> .
<pre><nowiki><Directory "/home/user/public_html/app/>
RewriteEngine On
RewriteRule ^tag/(.*)$ script.php?tag=$1
</Directory></nowiki></pre>
<ol start="4">
<li>''Does a rel tag still have meaning if the link redirects? If the HTTP server returns a 302 status code, does the rel-tag have meaning? Is there a formal rule that indexers should follow the link to the final, resolved destination? Or is there a formal rule that a rel tag should be ignored if URL of its link does not return a status code of 200?''
* ..next answer
</li>
</ol>

===CSS selector===
*How do you write a CSS selector for rel-tag?
** <code>a[rel~="tag"] { color: green }</code>

===Are tags case sensitive?===
*Are tags case sensitive. Is "Dog" the same tag as "dog" and "DOG"?
**{{AwaitingAnswer}}

===Multi-word tags===
*How should a multi-word tag be made? For instance, if using Wikipedia as a name space, a page about a Black Redstart (a bird) would be tagged '''Black_Redstart''', with an underscore [http://en.wikipedia.org/wiki/Black_Redstart]. Is there any way of aliasing alternatives ("BlackRedstart", "Black-Redstart", etc.)? Is any particular format preferable?
**{{AwaitingAnswer}}

===Tags with file extensions===
*Is <code><a rel=tag href="http://example.com/cheese.htm">cheese</a></code> a valid tag, for "cheese"? Ditto <code>.asp</code> or <code>.php</code> variants? If not, why not?

No, you cannot use a tag URL with a file extension - unless you want the extension included in all of your tags. Explanation from Brian Suda on the microformats-discuss list:

--- the spec says:
... the last segment of the path portion of the URI (after the final
"/" character) contains the tag value.

What that string is, is irrelavant. It could be /file/my.pdf and the
tag would be "my.pdf" it could be /downloads/my.big.file.pdf and the
tag would be "my.big.file.pdf". A tag is everything after the last
slash (unless the last char is a slash). So if that is a file or a
folder, or a file that does not have an extention, or a folder that
has a '.' in it's name.

===What about Scope?===
Since rel-tag is a feature used in many other microformats, the question often arises: "What is the scope of the tag?" For instance, a rel-tag may appear inside of an [[xfolk xFolk]] entry and on first glance it may appear that the tag should only apply to that entry. However, current publishing practice seems to indicate anything appearing on a page is likely related to the content of the page. Therefore, the interpretation is that not only does the rel-tag apply its direct container but to all containers and to the document as a whole; it contains the xFolk entry. This is a departure from strict knowledge theory in favor of real-world usage.

As another example, you may link to your friend Joe with XFN and hCard, indicating in his categories that Joe is interested in swimming, which you loathe. Since the article is primarily about you and not about Joe's hobbies and because the rel-tag is inside an hCard, you may expect that the rel-tag does not apply to the document; however, the document does contain information about swimming, namely that your friend likes it. In this way, rel-tag is binary: it indicates direction (yes or no) but not magnitude. This is no different than a free-text search. When querying search engines for the term "swimming" the page about you loathing swimming would also be returned.

The upshot of this is that rel-tags can have downward scope but not upward scope.

==Related pages==
{{rel-tag-related-pages}}
**{{AwaitingAnswer}}

hcard-issues

2007-02-03T04:14:30Z

DerrickPallas: /* Issues: street-address is listed as not singular */

<h1> hCard issues </h1>

These are externally raised issues about [[hcard|hCard]] with broadly varying degrees of merit. Thus some issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the spec.

'''IMPORTANT''': Please read the [[hcard-faq|hCard FAQ]] ''before'' giving any feedback or raising any issues as your feedback/issues may already be resolved/answered.

Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — [http://tantek.com/log/ Tantek]

Please add new issues to the '''top''' of the list.

For matters relating to the vCard specification itself, see [[vcard-errata]] and [[vcard-suggestions]].

See also related [[hcalendar-issues]].

__TOC__

== Issues ==

* 2007-02-02 raised by [[User::DerrickPallas|Derrick Pallas]]
*# [[adr]] says that all of it's properties are singular; however, "street-address" is listed as zero-or-more.
* {{OpenIssue}} 2007-01-30 raised by [[User:AndyMabbett|Andy Mabbett]]
*# Many sites, not least Wikipedia, publish co-ordinates as degrees-minutes-seconds (e.g. [http://en.wikipedia.org/wiki/Birmingham]). Should [[geo]] be extended to allow for this, with parsers making the conversion to digital values?
* 2007-01-26 raised by James Craig on [[accessibility]] page.
*# ''Localization of RFC2426 'type' values. RFC2426 type values for adr, email, and tel were intended as machine-readable values. Used as real HTML content in the following example only works in English. The accessify forum discussion described on the [[accessibility]] page has asserted that reducing this problem to an abbr is not a valid, accessible solution.''<pre><nowiki>
<span class="tel" xml:lang="en">
<span class="type">Home</span> (<span class="type">pref</span>erred):
<span class="value">+1.415.555.1212</span>
</span>
</nowiki></pre> ''Use the the class attribute for qname prefixed type values (and others such as dtstart values), AKA meta classes.'' <pre><nowiki>
<span xml:lang="en">
Home (preferred): <span class="tel type:home type:pref">+1.415.555.1212</span>
</span>
<span xml:lang="es">
Casa (preferido): <span class="tel type:home type:pref">+1.415.555.1212</span>
</span>
</nowiki></pre>
*#* REJECTED DUPLICATE ETC. Class attributes for type values [http://microformats.org/wiki/hcard-parsing#ISSUE_2 was tried and rejected] and in addition, [[qnames-considered-harmful]].

* {{OpenIssue}} 2007-01-22 raised by [[User:Christina Hope|Christina Hope]].
*# ''What is the easiest way to display an hCard all on one line with spacing. Currently I am using this - but I know that there has to be an easier/ simpler way to do it. <br/>Examples: (1) <pre><nowiki><p>
<span class="vcard">
<span class="fn">Christina Hope</span>& nbsp;& nbsp;& nbsp;
<span class="department">Information Technology</span>& nbsp;& nbsp;& nbsp;
<span class="role">Website Coordinator</span>& nbsp;& nbsp;& nbsp;
<span display="none" class="region"></span>
<span class="tel"> x3408</span> & nbsp;& nbsp;& nbsp;
<span class="email"><a href="mailto:chope@example.com">chope@example.com</a></span>
</span></p></nowiki></pre>''

:: Try <pre><nowiki><p class="vcard">
<span class="fn">Christina Hope</span>
<span class="department">Information Technology</span>
<span class="role">Website Coordinator</span>
<abbr class="tel" title="+44123 456 7890 x 3408"> x3408</abbr>
<a class="email" href="mailto:chope@example.com">chope@example.com</a>
</p></nowiki></pre>

::Note: apply classes to existing elements; use abbr to give the phone number in full, in international format. Also, use CSS, not non- breaking spaces, for spacing.

::[[User:AndyMabbett|Andy Mabbett]] 08:34, 22 Jan 2007 (PST)

* {{OpenIssue}} 2006-12-15 raised ([http://microformats.org/discuss/mail/microformats-discuss/2006-December/007730.html on 2006-12-14, on the mailing list]) by Joe Andrieu.
*# (Paraphrased) By including organisations and places, as well as people, hCards have lost semantic specificity (see cited mailing list post for details).

* 2006-12-15 raised by [[User:WizardIsHungry|WizardIsHungry]]
*# ''[Moved from a user talk page] Hey, why is hiding semi-useful information using CSS bad? The Geo and Address stuff wouldn't be enough to contact me, but I would like there so bookmarklets, crawlers, greasemonkey etc can manipulate it. Is there a policy on using CSS hiding of fields? Thanks :)''
*#* I guess we can't rely that anything that consumes hCards is normalizing it to a particular format instead of just taking all the xml inside the hcard classed block and sticking it somewhere. If it does just store it as a string, then generating html from it will yield the same hidden fields. Perhaps hiding fields by applying a stylesheet to the relevant hcard styles is ok, but not hiding them using in-line CSS styling. Feedback? --[[User:WizardIsHungry|Jon Williams]] 10:28, 22 Dec 2006 (PST)
*#* Furthermore, [[hcard-example1-steps]] shows using inline CSS to hide fields. What gives? I still think this is an open issue; particularly the distinction between external stylesheet hiding and inline rules though. --[[User:WizardIsHungry|Jon Williams]] 13:33, 5 Jan 2007 (PST)
*#* Should this be on [[microformats-issues]]? --[[User:WizardIsHungry|Jon Williams]] 13:37, 5 Jan 2007 (PST)
*#** The example you cite is the first of several steps, which refine and improve the first step's suboptimal hCard.
*#*** The question is: ''why is this considered suboptimal if it is ok to hide the entire card?'''
*#**** REJECTED CLOSED TOO THEORETICAL. It is not OK to hide the entire card. Without further concrete examples with real world URLs on the web, this issue is closed.
*#***** Here are a number of examples of hiding the entire card, taken from [[hcard-examples-in-wild]]: [http://www.meryl.net/] [http://www.fberriman.com/] [http://www.fberriman.com/] [http://www.last.fm/user/Crok/?scrobbling=t1] -- Could someone link to where this was discussed and decided in the past, as it seems like this is being governed by fiat. Even if you don't care to have consensus, but could you at least justify this? This stonewalling is rather rude. --[[User:WizardIsHungry|Jon Williams]] 13:24, 9 Jan 2007 (PST)
*#* [[hcard-brainstorming#CSS_Styles]] explicitly permits this. I'm going with what they say.

* {{OpenIssue}} 2006-12-07 raised by RyanKing.
*# ''hCard org-fn matching should use organization-name, if given.''
*# originally [http://microformats.org/discuss/mail/microformats-discuss/2006-November/007337.html raised on uf-discuss] by David Janes.

* {{OpenIssue}} 2006-11-24 raised by [[User:AndyMabbett|Andy Mabbett]]
*# A suggested work-around for the lack of a gender property is to represent gender implicitly in the honorific-prefix field, e.g. Mr. for male, and Ms. for female. This approach does has the limitation that "Mr." and "Ms." (or "Miss"/ "Mrs.") conflicts with a higher-ranking, gender-neutral honorific, such as "Dr." or "Rev." for the person, as it is unusual (and sometimes, outside the USA, invalid) to refer to someone as "Mr. Dr." or "Mrs. Rev." for example. Note also that some cultures or religions regard such titles as offensive, or at least disdain them.

* 2006-11-23 raised by [[User:AndyMabbett|Andy Mabbett]]
*# The specification should be "stand alone", and not normally require reference to the vCard specification.
*#*A: ACCEPTED PARTIAL. Agreed that [[hcard|hCard]] should be usable by typical web authors without having to dig through the vCard specification. Precise implementation of parsing etc. hCard properties however will likely require programmers to reference the specifics/grammars in the vCard specification which we will NOT replicate in the hCard specification in order to avoid inevitable introduction of errors due to duplication. And that being said, ''informative'' explanations may be a good idea, while the vCard property/value definitions are kept as ''normative''.
*#** Yes; my meaning was with reference to hCard publishing, not parsing-into-vCards. [[User:AndyMabbett|Andy Mabbett]]
*# ''The specification should state that "telephone numbers SHOULD adhere to [http://en.wikipedia.org/wiki/E.123 ITU-T Recommendation E.123]" (or perhaps "MUST").''
*#* ACCEPTED PARTIAL. This makes sense as an informative reference and a MAY, but since vCard makes no such SHOULD statement for TEL values, neither should/will hCard. In addition, as a Wikipedia URL that is subject to drastic change, we cannot make that a normative reference.
*#** I take your point about Wikipedia - here's [http://www.itu.int/rec/T-REC-E.123-200102-I/en a more definitive ITU-E.123 URL]; but it's for a chargeable document. Using "SHOULD" or "MUST" in hCard will not affect compatibility with or conversion to vCard. [[User:AndyMabbett|Andy Mabbett]]

* 2006-11-16 raised by [[User:AndyMabbett|Andy Mabbett]]
*# ''The "type" for "tel" lacks a "textphone" option (for the devices used by, e.g., people who are deaf or have speech difficulties. Example: [http://www.birmingham.gov.uk/contact Birmingham City Council (303 1119)].''
*#*A: REJECTED. This is a vCard issue, as the "type" taxonomy for "tel" is determined by vCard. We are not presently extending hCard beyond the properties and values in vCard.
*#** ''I'm not clear how you can "reject" a provably factual statement. What's the process of suggesting an update to vCard? [[User:AndyMabbett|Andy Mabbett]]''
*#***A: ACCEPTED PARTIAL RESOLVED. Unfortunately it is not clear what the process is for updating vCard. However, we can at least capture suggestions for improvement to vCard from this community which may be helpful once the process for updating vCard is understood. I've created [[vcard-suggestions]] for this purpose and added this suggestion. - Tantek
*#**** The vCard spec is updated by RFC, for example [http://www.rfc-editor.org/rfc/rfc4770.txt RFC 4770]. [[User:AndyMabbett|Andy Mabbett]] 06:22, 12 Jan 2007 (PST)

* {{OpenIssue}} 2006-10-21 raised by [[User:AndyMabbett|Andy Mabbett]]
*# ''There should be some way to say that the URL of an hCard or hCalendar event is the URL of the page itself, without having to include a redundant, and accessibility-damaging link to that page, on the page itself.''

* 2005-06-21 raised by Hixie
*# ''Issue H-1: This specification is lacking a user agent conformance section. There's basically nothing that says how hCards must be parsed, how to handle errors, and so forth. Is it defined in terms of the DOM? Is it defined in terms of a serialisation? How do you handle unexpected content or missing content?
*#*A: ACCEPTED RESOLVED. See [[hcard-parsing]] for how hCards must be parsed. For errors/unexpected content/missing content, please provide specific examples.

* 2005-06-30 raised by Jack L. Wolfgang II. Please feel free to move these to the FAQs if they are better suited there.
*# ''Handling middle names and suffixes: How does one handle middle initials/names in the hCard format and suffixes that are not honorific suffixes (e.g. Jr., Sr., II, III, etc. as opposed to Ph.D., Esq., M.D., etc.)?''
*#*A: ACCEPTED FAQ. By [http://suda.co.uk Brian Suda] (2005-11-08 updated by [http://tantek.com/log/ Tantek]; 2006-11-16 updated by [[User:AndyMabbett|Andy Mabbett]]) hCard is based of the RFC2426 spec. I you want to use a middle initial it can be expanded using the abbr element. <code><abbr title="[MiddleName]" class="additional-name">M</abbr></code>. Honorific Suffixes in the RFC include Jr., Esq. and other inherited suffixes, so I would just use <code><abbr class="honorific-suffix" title="Junior">Jr.</abbr></code> etc.
*# ''Handling different types of addresses: How does one handle the TYPE (e.g. postal, work, etc.) specification for addresses as specified in RFC 2426 Section 3.2.1?''
*#*A: ACCEPTED FAQ. By [http://suda.co.uk Brian Suda] (2005-11-08 updated by [http://tantek.com/log/ Tantek]) If you want to add a type to certain elements, including address and telephone it may be done in the following manner:
<pre><nowiki>
<span class="adr">
<span class="type">work</span>:
...
</span>
</nowiki></pre>
<pre><nowiki>
<span class="tel">
<span class="type">work</span>:
<span class="value">123.456.7890</span>
</span>
</nowiki></pre>
the TYPE needs to be a sub-element of the property (adr, tel, etc) NOTE: EMAIL does NOT have many TYPE attributes, only INTERNET and X400

* {{OpenIssue}} 2006-04-10 raised by [[User:ScottReynen|Scott Reynen]].
*# ''When someone looks at the [[hcard|hCard]] pages, one sees no collection of real-world publishing of contact data nor discussion of the properties implied by such examples, I think it's far too easy to infer that microformats come from other formats more than actual behavior. There's nothing on the [[process]] nor the hcard pages explaining this discrepancy. I would argue that there should be an explanation, probably in both places.''

* 2006-04-06 raised by [[User:Evan|Evan]].
*# ''What is the relationship between the CATEGORY property and [[rel-tag]]? Can you add a tag to an hCard? How can you add a tag to a particular hcard on a page without tagging the other cards on a page?''
*#* ACCEPTED. Categories can optionally be represented as tags. The classname 'category' should always be used, but rel="tag" can optionally be used (in addition to the category classname). In the case that a rel-tag tag is used, the tag (as defined by [[rel-tag]]) is used for the category. Examples: (1) <code><nowiki><span class="category">food</span></nowiki></code> and (2) <code><nowiki><a class="category" rel="tag" href="http://example.com/food">Food!</a></nowiki></code>. --[[User:RyanKing|RyanKing]] 15:16, 13 Jun 2006 (PDT)

* {{OpenIssue}} 2006-03-07 raised by [http://tantek.com Tantek].
*# ''Issue 1: In 99% of the cases I am finding the need to explicitly do "n" markup, the person has a three word fn which is in the form "given-name additional-name(or initial) family-name". Should we make three word fn's into another shorthand notation to make this easier for authors?''

* 2006-02-23 raised by [http://www.thefutureoftheweb.com/ Jesse Skinner] and [http://www.thefutureoftheweb.com/blog/2006/1/hcard#comment1 Ben Buchanan].
*# ''Are multiple URLs allowed? The [http://microformats.org/wiki/hcard#Property_List Property List] suggests not, whereas email and tel have multiple type/value pairs. However, the [http://microformats.org/wiki/hcard-parsing#finding_hCard_properties parsing page] suggests multiple URLs are OK. Either way, it seems clear that a type cannot be associated with a URL. So how exactly does hCard deal with multiple URLs?''
*#* RESOLVED FAQ: Multiple URLs are allowed. Some consuming agents (Apple's AddressBook.app among them) don't have an interface for producing multiple URLs, but they are still valid in vCard and therefore hCard. --[[User:RyanKing|RyanKing]] 17:58, 12 Jun 2006 (PDT)

* 2006-02-19 raised by Miika Mäkinen.
*# ''Couldn't the types for tel numbers be specified in a class? Now, for a phone number one needs to add the type as "visible" text, which is not always preferred. For example, type "Work", many times more suitable label could be "Office" or similar and sometimes you might not want to display any type information at all.''
*#* REJECTED TRIED ALREADY. Using class names for the "type" of a tel or adr [http://microformats.org/wiki/hcard-parsing#ISSUE_2 was attempted], and failed in many situations. In addition, the "type" information is actual data, not just a property name, and thus deserves to be in the ''visible'' markup. Note that you can use abbreviations, e.g. <code><nowiki><abbr class="type" title="work">W:</abbr></nowiki></code> in order to present the type in a way that may better fit in with the rest of your presentation.

* 2006-02-13 raised by [http://microformats.org/wiki/User:Eron_Wright Eron Wright]
*# ''Few systems contemplate the altitude component of a coordinate, yet it exists. Altitude becomes important when working with 3D mapping software such as Google Earth. Indeed, the geocoding service that Google Earth uses returns a three-dimensional coordinate. I suggest that hCard provide explicit support for altitude.''
*#* REJECTED POSTPONED. Not in vCard. There is no "altitude" component in vCard (RFC 2426), and thus (certainly for now) there won't be any in hCard. If a new version of vCard were to come out with altitude, then we would add it to hCard. At some point we may also consider adding explicit extensions beyond vCard, but if we were to do so, we would capture them first on the [[hcard-brainstorming]] page.

*2006-02-03 raised by Brian
*# We can use the [[geo]] microformat in [[hatom]] to represent GeoRSS element

* {{OpenIssue}} 2006-01-28 raised by [http://rbach.priv.at/Microformats-IRC/2006-01-28#T075222 Tantek on #microformats]
*# ''Is hCard is really appropriate for a named phone bridge, or do we need something else for a named phone numbers that are neither people nor organizations (the current two precise semantics that can be defined by hCard). For example see the "Zakim" hCard on http://www.w3.org/2005/12/allgroupoverview.html''

* 2006-01-21 raised by [http://inspire.server101.com/ben/resume/ Ben Boyle].
*# ''Have run into issues trying to use definition lists with hCard, specifically around nesting requirements for tel where the DT element takes a class "type" (e.g. Telephone, Facsimile) and the DD element marks the value. It is invalid to place any other elements within a DL that wrap around the DT/DD pairs so there is no available element to assign the class "tel" to. XHTML2 proposes a DI element that will resolve this issue. I am hoping for an interim solution for those that wish to use definition lists, perhaps that "any class that would be placed on the DI parent (in XHTML2) must instead be placed on the first DT element". I realise this will cause headaches for those implementing hCard parsers. I'd also like to note this may affect other (current or future) microformats and relates to the general hassle of definition lists in current (X)HTML recommendations. For your consideration - thanks!''
*#* REJECTED WORKAROUND AVAILABLE. Either don't use definition lists in this manner (because the description of a definition should go completely in the DD element, and thus you should be able to put the class on that), or use separate DLs in the cases where you would otherwise have needed a DI element.

* 2005-12-08 raised by [http://www.heatonarts.com Kenny Heaton].
*# ''The specification gives no way to to declare a telephone extension, as in (800) 234-5678 ext. 101''
*#* ACCEPTED FAQ. What is the best way to declare a telephone extension in a "tel" property? (also seems like it would be a vCard FAQ).

* 2005-10-30 raised by [http://greenbytes.de/tech/webdav/ Julian Reschke].
*# ''Several implementations'' '''(Which ones? Please provide links.)''' ''seem to assume that any class attribute that contains the substring "vcard" indeed signals the presence of vcard information. Not so: there are examples'' '''(What examples? Please provide links.)''' ''of where a token in the class attribute indeed only ''starts with'' "vcard", in which it should be ignored. Implementations using XPath (such as XSLT or Greasemonkey scripts) should be advised to do a <code>contains(concat(@class,' '),'vcard ')</code>.
*#* REJECTED VAGUE. Which implementations? And which examples?
*#*''(Note: the code <code>contains(concat(@class,' '),'vcard ')</code> is broken see [[parsing-microformats#Parsing_class_values]] for a correct example --[[User:RobertBachmann|Robert Bachmann]])''

* 2005-08-12 raised by [http://home.alltel.net/jackwolfgang/contact/ Jack L. Wolfgang II]. Use of mailto transport functionality for the E-Mail address field.
*# ''As stated in the [[hcard-brainstorming]] document, mailto is abused by spammers. As a result, many organizations have moved to form-based contacts as opposed to mailtos. According to [http://www.ietf.org/rfc/rfc2426.txt RFC 2426], Section 3.3.2, "A non-standard value can also be specified." Does this refer to a non-standard e-mail address value or type value?''
*#* A: ACCEPTED FAQ. Type value.

* 2005-07-23 raised by DanConnolly
*# ''Are class names case sensitive or not? [[hcard]] says "If names in the source schema are case-insensitive, then use an all lowercase equivalent."''
*#* A: ACCEPTED FAQ. Class names are case sensitive per the HTML4 specification. Hence hCard explicitly specifies the case of class name to use for source schema names that are case-insensitive.
*# ''...but I find example data with class="Given-Name"''
*#* A: ACCEPTED RESOLVED. That is from an older preliminary version of the hCard spec which used mixed case class names. Such class names are no longer valid hCard. Please note which examples (URLs) are using the older class names and hopefully we can get them fixed.
*#** A: By [http://suda.co.uk Brian Suda] I have fixed all the references in the [[hcard-brainstorming]] page to reflect the lower-case style, this is a hold-over from the original design, X2V has been updated.
*# ''..and code that supports it [data with class="Given-Name"].''
*#* A: ACCEPTED RESOLVED. Any code supporting the older class name(s) is for backward compatibility only, and should be phased out. Any new hCard code SHOULD NOT support such mixed case class names.
*#** [http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html rfc2629xslt.html] uses Street-Address, Family-Name, etc.
*#*** A: By [http://greenbytes.de/tech/webdav/ Julian Reschke] Fixed rfc2629.xslt (2005-10-29)
*#** [http://suda.co.uk/projects/X2V/ X2V] Version 0.5.1 2005-07-08 supports Family-Name etc.
*#*** A: By [http://suda.co.uk Brian Suda] I agree that the upper-case class names can be removed from the code, this was a hold-over and will be trimmed.
*# ''The ul/ol stuff for multiple values of a property seems to be in the X2V code and in [[hcard-brainstorming]] but not in the [[hcard]] spec.''
*#* A. ACCEPTED RESOLVED. This needs to be added to the spec. 2005-11-08 Update: the way multiple values has been updated to work much better and not require ul/ol.
*# ''the [[hcard-profile]] says country-name but X2V and lots of the data I've seen says country''
*#* A. ACCEPTED RESOLVED. RFC 2426 clearly says "country name" in both the prose and the grammar, thus "country-name" is the correct class name to use. If X2V uses just "country", it needs to be fixed to use "country-name", and any such examples as well. Please note which examples (URLs) are using the class name "country" and hopefully we can get them fixed.
*#** A: By [http://suda.co.uk Brian Suda] I have fixed all the references in the [[hcard-brainstorming]] page to reflect the proper country-name, X2V will support this in the next iteration when i fix several bugs at once.

* 2005-07-22 raised by DanConnolly
*# ''...in my cellphone/sidekick address book, I have a number of entries for companies. I wrote [http://dev.w3.org/cvsweb/2001/palmagent/asHCard.xsl asHCard.xsl] to convert the data from RDF to hCard, but I don't know what to do with entries for companies, since FN is mandatory in hCard.''
*#*A: ACCEPTED FAQ. This should be an FAQ. "How do I write an hCard for a company?" The vCard specification is silent on this point (entries for companies). Thus there are two options as far as the hCard standard is concerned:
*#*# Set "fn" and "org" to the same value. E.g. <code><span class="fn org">W3C</span></code> (recommended)
*#*# Set "org" as usual, and set "fn" explicitly to empty. E.g. <code><span class="fn"></span><span class="org">W3C</span></code> or
*#*#* Simply have no "fn", and on the parsing side, if there is no "fn" present, but there is an "org" property, then duplicate the "org" value as "fn"
*#*The last two options are effectively the same and are both not explicit and easily confusable with a "missing data" condition. Thus option 1 is preferred. For converting applications (hCard to vCard), they ''may'' consider using proprietary extensions to make the distinction explicit in generated vCards, based on either case 1 or 2 above. E.g. Apple's Address Book application supports the property: <code>X-ABShowAs:COMPANY</code>
*#*We are looking for descriptions of how other vCard supporting applications treat "company" vCards differently from "person" vCards. Please provide descriptions here:
*#** Address Book / MacOSX.3:
*#*** Export (e.g. drag & drop to desktop, view in text editor)
*#**** Sets "FN" and "ORG" to the name of the company
*#**** Sets proprietary <code>X-ABShowAs:COMPANY</code>
*#*** Import (e.g. edit in text editor, drag & drop from desktop)
*#**** By setting "FN" and "ORG' to the same name (e.g. Banana Computers Inc.)
*#**** And removing any proprietary properties (e.g. X-ABShowAs)
*#**** Address Book user interface showed new vCard as a "company" contact rather an a person
*#** Address Book MacOSX.4:
*#*** same results as above -RyanKing
*#** The Danger Hiptop (aka T-Mobile Sidekick) address book:
*#*** Export (e.g. [http://lists.w3.org/Archives/Public/www-archive/2005Sep/0007.html email to a mailing list])
*#**** Sets "FN" to the empty string and puts the company name in "ORG".
*#*** Import - could not find a way to import a .vcf, by email, IM, or other means into the Sidekick.
*#** Contacts / Outlook 2003 Windows
*#*** Export (e.g. Highlight contact, File, Save As, vcard)
*#**** Sets "N" and "ORG to the name of the company
*#**** Sets "FN" to value in "File as:"
*#** Add another vCard app here.

=== Canonical/Authoritative Hcard ===

* {{OpenIssue}} 2006-01-23 raised by David Janes (?).
* ''Issue 1: Specifying Authoritative or Canonical or Official Hcard''
** Use of rel="me" only specifies an alternate version, not necessarily the canonical version
** Suggestion: use rel="me self". Adopt "self" semantics from Atom which means "the", or controversially "alternate, equivalent" version
*** The combined use of rel="me" and rel="self" may conflict with their definitions in the [http://www.gmpg.org/xfn/11#me XFN Profile] and RFC 4287 respectively. See [http://microformats.org/discuss/mail/microformats-discuss/2007-January/008443.html the mailing list discussion on rel="me self"] for more information. From [[User:RCanine|Ryan Cannon]].
** Suggestion: use rel="via". Per RFC 4287, via "signifies that the IRI in the value of the href attribute identifies a resource that is the source of the information provided in the containing element." from [[User:RCanine|Ryan Cannon]].
** Other suggestions? "authoritative", "canonical"?
** Problems with this suggestion?
** How does this relate to authentication/trust issues? Is this a different problem with a different scope?
*** (microformats-discuss list) Joe Andrieu: The concept behind an "authoritative" hCard rather than "definitive" or "canonical" one was that "authoritative" would explicitly be a ''claim'' by the author of the hCard regarding its authority in describing the subject of the hCard, i.e., use ''this'' hCard as the one true source of this individual's contact information.
*** To summarize: authentication/trust is a separate topic.
** What exactly is the scope of the problem to solve here?
*** (IRC) (10:47:44) sreynen: for example, all of the examples I've seen involve a single person publishing multiple hCards of himself
*** (IRC) (10:48:13) sreynen: yet many people are talking about 3rd parties publishing hCards and pointing back to the subject's own hCard
** rel="me" must be symmetrical, per the XFN spec. What exactly does this mean for this use?
** "me" (and, depending on usage, "self") are not appropriate for content referring to third- parties. [[User:AndyMabbett|Andy Mabbett]]
''TODO:'' please add appropriate context and history of this issue from the mailing list. Sign your name to your comments.

== Template ==

Please use this format (copy and paste this to the end of the list to add your issues):
* {{OpenIssue}} YYYY-MM-DD raised by [http://yourhomepage.example.com YOURNAME].
*# ''Issue 1: Here is the first issue I have.''
*# ''Issue 2: Here is the second issue I have.''

Note: large blocks of italic text are inaccessible to many readers, including people with types of visual impairment, dyslexia, etc. [http://www.intranet.man.ac.uk/accessibility/Disabilities/dyslexia.html], [https://tritonlink.ucsd.edu/portal/site/tritonlink-preview/menuitem.b4448692267a11256ec5e210514b01ca?storyID=20896]. [http://accessites.org/], [http://tlt.psu.edu/suggestions/accessibility/font.html], [http://www.wd4a.co.uk/Guidelines.htm]

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

hcard-examples-in-wild

2007-02-03T04:08:34Z

DerrickPallas: /* New Examples */

=hCard Examples in the wild=

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" 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]] markup. Examples added without a URL to a page with hCard markup 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 markup to your current contact page.

==New Examples==

Please add new examples to the '''top''' of this section.
* [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://www.last.fm Last FM] has hCards hidden on their profile pages e.g. [http://www.last.fm/user/Crok/?scrobbling=t1].
* [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.
* IBM is embracing microformats. The [http://www.ibm.com/contact/employees/ IBM Employee Directory] now returns hCards in its query results. Also see the [http://www.ibm.com/shortcuts/ Shortcuts Podcast].
* [http://dsingleton.co.uk/ David Singleton] has added a hCard to his blog.
* [http://krisswatt.co.uk/ Kriss Watt] has hidden an hCard his blog footer.
* [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.fberriman.com/ Frances Berriman] has a hidden vCard in the footers of her website.
* [http://www.candlescience.com/ CandleScience Candle Supply] added a hidden hcard sitewide.
* [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://alexander-mette.de amette] uses the hCard format in a module of his TikiWiki powered blog
* [http://staff.washington.edu/oren/weblog2/ Oren Sreebny] has an hcard on his blog main index template
* [http://www.cs.brandeis.edu/~zippy/ Patrick Tufts] has an hCard on his homepage.
* [http://ascii20.blogspot.com/ Mathias Kolehmainen and Jamie Taylor] have hCards on their weblog.
* [http://www.hoppsan.org/jamesb/blogger/ Barnaby James] has a hCard on his weblog.
* [http://esa-education.com/schools/map ESA Education] Uses hCards for their 100+ schools and each of the individual school sites.
* [http://www.thereisnocat.com/#vcard Ralph Brandi] has added an hCard to the sidebar of his weblog as a result of Tantek Çelik's portion of the Microformats presentation at SXSW 2006.
* [http://www.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.meryl.net/ Meryl K. Evans] has a hidden hCard on her homepage.
* [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.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.

== Examples ==
* [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.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://tantek.com/ Tantek's Thoughts] includes an inline author hCard at the bottom of the page.
* [http://technorati.com/ Technorati]'s [http://www.technorati.com/about/ About page] lists their '''Media Contact'''
* [http://www.deadringerart.com/ The Brothers McDowell] have hCards at their Contact page.
* [http://twinsparc.com/ Twinsparc] put an hCard in the header and footer of all their pages.
* [http://tantek.com/microformats/2005/web2/speakers.html Web 2.0 Conference speakers page marked up with hCard]
* [http://we05.com/ Web Essentials 05] marked up all their [http://we05.com/presenters.cfm presenters with hCard].
* [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]].
* The [http://technorati.com/about/ Technorati About page] has contact information marked up with hCard. By [[implementations#Technorati|Technorati]]
* The [http://technorati.com/press/ Technorati Press page] also has an hCard. By [[implementations#Technorati|Technorati]]
* The [http://technorati.com/about/staff.html Technorati Staff page] has many hCard. By [[implementations#Technorati|Technorati]]
* [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.

===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.
* [http://tantek.com/ Tantek's Thoughts] encodes Çelik as inline UTF8.

==Examples with some problems==

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

* [http://www.alexa.com Alexa Internet] marked up its [http://www.alexa.com/site/company/managers managers' page] with hCard.
**Person's job title within "fn". [[User:AndyMabbett|Andy Mabbett]]
* [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://www.matthewwest.co.uk Matthew West] has an hCard on his [http://www.matthewwest.co.uk/email contact] page.
**Flat- and building- number run on.
*[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)
* The good ship [http://styrheim.com/test/leonid.html Leonid Miloslavskiy] spotted in the North Atlantic
** INVALID --[[User:RyanKing|RyanKing]] 00:50, 27 Oct 2005 (PDT)
*** class="family" should probably be family-name
*** the "n" property is missing and the "n" optimization can't be applied
*** the first geo propery is empty, the second one is invalid (i.e., it doesn't contain lat/long)
* [http://landsbank.fo/#hCard Landsbanki Føroya]
** INVALID - using embedded RDF/XML invalidly
* [http://chrischerry.name/ Chris Cherry's contact page with his hCard]
** <strike>WARNING - uses class="cell" instead of <span class="type">cell</span></strike> Fixed -- [[User:Seriph|Chris Cherry]] 19:54, 15 Sep 2006 (PST)
* [http://www.bath.ac.uk/contact/ University of Bath] Person Finder results are encoded with hCards so you can easily create a vCard from any result.
** ERROR - attempt to use Implied-N optimization where that's not possible. --[[User:RyanKing|RyanKing]] 14:29, 5 Jan 2006 (PST)
** Error appears for external users only. Won't be fixed any time soon. -- [[User:PhilWilson|PhilWilson]] 00:03, 28 Jan 2006 (GMT)
* [http://richi.co.uk/blog/2005/12/structured-blogging.html Richi Jennings] has put up his attempt
** INVALID, missing "fn"--[[User:RyanKing|RyanKing]] 12:47, 5 Jan 2006 (PST)
* [http://www.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)

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

rel-tag-faq

2007-02-03T01:13:22Z

DerrickPallas: /* What about Scope? */

= rel-tag frequently asked questions =

This document serves to answer and discuss frequently asked questions specifically about the [[rel-tag]] microformat. You may want to read the [[rel-faq]] first as it answers many common questions about the HTML4 “rel” and “rev” attributes, and their linktype values. If you have a new question to ask, first consider asking on the [http://microformats.org/mailman/listinfo/microformats-discuss/ microformats-discuss list].

== Q&A ==

# ''Where does a tagging link belong? Does the tagging link only need to appear in my Web feed (RSS / Atom)? Does the tagging link need to appear on the page where my specific blog entry lies? Does the tagging link need to appear everywhere that I can possibly imagine?''
#* In short, tagging links belong in all the places and formats in which you published tagged content. The Web page is the primary location where users read content and where search engines index. Thus the Web page is a place where you should absolutely include your [[rel-tag]] links. To tag your blog posts, put the [[rel-tag]] links inside them, visibly. The Web feeds are simply alternate ways of publishing your blog posts, and thus should include the full content of your blog posts, [[rel-tag]] links intact.
# ''Where shouldn't I use rel-tag?''
#* rel-tag expresses a particular relationship (a) between the page you are on and (b) the target of a link. If you're not asserting this relationship, don't use rel-tag. In particular:
#** don't use rel-tag in [http://en.wikipedia.org/wiki/Tag_cloud Tag Clouds]
#** don't use rel-tag to refer to the pages http://www.technorati.com/tag/xyz, http://del.icio.us/tag/xyz, http://www.flickr.com/photos/tags/xyz/ (and so forth) if you're not asserting "this page is tagged 'xyz'"
# ''The format specifies that the tag must “come after the last / in the path”. Will something like <code><nowiki>http://example.com/index.php/TAG</nowiki></code> work? Or does it have to be a “real” directory or [http://httpd.apache.org/docs/2.2/mod/mod_rewrite.html mod_rewrite]? -- [[User:Singpolyma|singpolyma]] 23:51, 24 Jan 2006 (PST)''
#* The key is the URL. Whether that URL is generated from a database or a directory does not matter. The URL matters.
#** My question, however, was about whether that URL form ( <code><nowiki>http://example.com/index.php/TAG</nowiki></code> ) would be valid, since there is the dot in “index.php”.
#*** Yes, the URL in the example is valid (or legal or conformant or whatever you want to call it to minimize confusion). The dot (period, full stop, U+002E) is free to appear in most places in a URL, even in the middle of a path-segment that is not the last path-segment. (The latest specification for URLs, “[http://gbiv.com/protocols/uri/rfc/rfc3986.html Uniform Resource Identifier (URI): Generic Syntax]”, is RFC 3986.)
# ''I’m developing a web application which uses tagging, and so of course I want to use [[rel-tag]]. For this application, I want nice, clean URLs. I was planning to use [http://httpd.apache.org/docs/2.2/mod/mod_rewrite.html mod_rewrite] to map a clean URL onto my underlying scripts. How do I use Apache’s [http://httpd.apache.org/docs/2.2/mod/mod_rewrite.html mod_rewrite] to map <code><nowiki>http://example.org/~user/app/tag/car</nowiki></code> to <code><nowiki>http://example.org/~user/app/script.php?tag=car</nowiki></code> ?''
#* One solution involves changing the script to inspect the path for the tag (via the variable “PATH_INFO”), rather than inspecting the query:
<pre><nowiki><Directory "/home/user/public_html/app/>
RewriteEngine On
RewriteRule ^tag/([^/]+)$ script.php/$1 [last]
</Directory></nowiki></pre>
#* For people who can edit the server’s main configuration file, the following untested configuration code may work. Corrections are welcome.
<pre><nowiki>RewriteEngine On
RewriteMap tag int:escape
RewriteRule ^/~user/app/tag/([^/]+)$ /~user/app/script.php?tag=${tag:$1} [last]</nowiki></pre>
#* The following configuration code, left over from a previous contribution to this document, does a poor job according to tests. The following code fails to enforce the [[rel-tag]] rules about the tag corresponding to the last non-empty path-segment. The following code fails to transcode the tag for safe use in the URL query. Consider that a request on <code><nowiki>http://example.org/~user/app/tag/</nowiki></code> would map internally to a request on <code><nowiki>http://example.org/~user/app/script.php?tag=</nowiki></code> . Consider that a request on <code><nowiki>http://example.org/~user/app/tag/not-a-tag/the-tag</nowiki></code> would map internally to a request on <code><nowiki>http://example.org/~user/app/script.php?tag=not-a-tag/the-tag</nowiki></code> . Consider that a request on <code><nowiki>http://example.org/~user/app/tag/the-tag/</nowiki></code> would map internally to a request on <code><nowiki>http://example.org/~user/app/script.php?tag=the-tag/</nowiki></code> . Consider that a request on <code><nowiki>http://example.org/~user/app/tag/attack&intent=destroy</nowiki></code> would map internally to a request on <code><nowiki>http://example.org/~user/app/script.php?tag=attack&intent=destroy</nowiki></code> .
<pre><nowiki><Directory "/home/user/public_html/app/>
RewriteEngine On
RewriteRule ^tag/(.*)$ script.php?tag=$1
</Directory></nowiki></pre>
<ol start="4">
<li>''Does a rel tag still have meaning if the link redirects? If Apache returns a 302 status code, does the rel tag have meaning? Is there a formal rule that indexers should follow the link to the final, resolved destination? Or is there a formal rule that a rel tag should be ignored if URL of its link does not return a status code of 200?''
* ..next answer
</li>
</ol>

===CSS selector===
*How do you write a CSS selector for rel-tag?
** <code>a[rel~="tag"] { color: green }</code>

===Are tags case sensitive?===
*Are tags case sensitive. Is "Dog" the same tag as "dog" and "DOG"?
**{{AwaitingAnswer}}

===Multi-word tags===
*How should a multi-word tag be made? For instance, if using Wikipedia as a name space, a page about a Black Redstart (a bird) would be tagged '''Black_Redstart''', with an underscore [http://en.wikipedia.org/wiki/Black_Redstart]. Is there any way of aliasing alternatives ("BlackRedstart", "Black-Redstart", etc.)? Is any particular format preferable?
**{{AwaitingAnswer}}

===Tags with file extensions===
*Is <code><a rel=tag href="http://example.com/cheese.htm">cheese</a></code> a valid tag, for "cheese"? Ditto <code>.asp</code> or <code>.php</code> variants? If not, why not?
**{{AwaitingAnswer}}

===What about Scope?===
Since rel-tag is a feature used in many other microformats, the question often arises: "What is the scope of the tag?" For instance, a rel-tag may appear inside of an [[xfolk xFolk]] entry and on first glance it may appear that the tag should only apply to that entry. However, current publishing practice seems to indicate anything appearing on a page is likely related to the content of the page. Therefore, the interpretation is that not only does the rel-tag apply its direct container but to all containers and to the document as a whole; it contains the xFolk entry. This is a departure from strict knowledge theory in favor of real-world usage.

As another example, you may link to your friend Joe with XFN and hCard, indicating in his categories that Joe is interested in swimming, which you loathe. Since the article is primarily about you and not about Joe's hobbies and because the rel-tag is inside an hCard, you may expect that the rel-tag does not apply to the document; however, the document does contain information about swimming, namely that your friend likes it. In this way, rel-tag is binary: it indicates direction (yes or no) but not magnitude.

The upshot of this is that rel-tags can have downward scope but not upward scope.

==Related pages==
{{rel-tag-related-pages}}
**{{AwaitingAnswer}}

rel-tag-faq

2007-02-03T00:42:40Z

DerrickPallas: added section about scope being a red herring, as per tantek's request

= rel-tag frequently asked questions =

This document serves to answer and discuss frequently asked questions specifically about the [[rel-tag]] microformat. You may want to read the [[rel-faq]] first as it answers many common questions about the HTML4 “rel” and “rev” attributes, and their linktype values. If you have a new question to ask, first consider asking on the [http://microformats.org/mailman/listinfo/microformats-discuss/ microformats-discuss list].

== Q&A ==

# ''Where does a tagging link belong? Does the tagging link only need to appear in my Web feed (RSS / Atom)? Does the tagging link need to appear on the page where my specific blog entry lies? Does the tagging link need to appear everywhere that I can possibly imagine?''
#* In short, tagging links belong in all the places and formats in which you published tagged content. The Web page is the primary location where users read content and where search engines index. Thus the Web page is a place where you should absolutely include your [[rel-tag]] links. To tag your blog posts, put the [[rel-tag]] links inside them, visibly. The Web feeds are simply alternate ways of publishing your blog posts, and thus should include the full content of your blog posts, [[rel-tag]] links intact.
# ''Where shouldn't I use rel-tag?''
#* rel-tag expresses a particular relationship (a) between the page you are on and (b) the target of a link. If you're not asserting this relationship, don't use rel-tag. In particular:
#** don't use rel-tag in [http://en.wikipedia.org/wiki/Tag_cloud Tag Clouds]
#** don't use rel-tag to refer to the pages http://www.technorati.com/tag/xyz, http://del.icio.us/tag/xyz, http://www.flickr.com/photos/tags/xyz/ (and so forth) if you're not asserting "this page is tagged 'xyz'"
# ''The format specifies that the tag must “come after the last / in the path”. Will something like <code><nowiki>http://example.com/index.php/TAG</nowiki></code> work? Or does it have to be a “real” directory or [http://httpd.apache.org/docs/2.2/mod/mod_rewrite.html mod_rewrite]? -- [[User:Singpolyma|singpolyma]] 23:51, 24 Jan 2006 (PST)''
#* The key is the URL. Whether that URL is generated from a database or a directory does not matter. The URL matters.
#** My question, however, was about whether that URL form ( <code><nowiki>http://example.com/index.php/TAG</nowiki></code> ) would be valid, since there is the dot in “index.php”.
#*** Yes, the URL in the example is valid (or legal or conformant or whatever you want to call it to minimize confusion). The dot (period, full stop, U+002E) is free to appear in most places in a URL, even in the middle of a path-segment that is not the last path-segment. (The latest specification for URLs, “[http://gbiv.com/protocols/uri/rfc/rfc3986.html Uniform Resource Identifier (URI): Generic Syntax]”, is RFC 3986.)
# ''I’m developing a web application which uses tagging, and so of course I want to use [[rel-tag]]. For this application, I want nice, clean URLs. I was planning to use [http://httpd.apache.org/docs/2.2/mod/mod_rewrite.html mod_rewrite] to map a clean URL onto my underlying scripts. How do I use Apache’s [http://httpd.apache.org/docs/2.2/mod/mod_rewrite.html mod_rewrite] to map <code><nowiki>http://example.org/~user/app/tag/car</nowiki></code> to <code><nowiki>http://example.org/~user/app/script.php?tag=car</nowiki></code> ?''
#* One solution involves changing the script to inspect the path for the tag (via the variable “PATH_INFO”), rather than inspecting the query:
<pre><nowiki><Directory "/home/user/public_html/app/>
RewriteEngine On
RewriteRule ^tag/([^/]+)$ script.php/$1 [last]
</Directory></nowiki></pre>
#* For people who can edit the server’s main configuration file, the following untested configuration code may work. Corrections are welcome.
<pre><nowiki>RewriteEngine On
RewriteMap tag int:escape
RewriteRule ^/~user/app/tag/([^/]+)$ /~user/app/script.php?tag=${tag:$1} [last]</nowiki></pre>
#* The following configuration code, left over from a previous contribution to this document, does a poor job according to tests. The following code fails to enforce the [[rel-tag]] rules about the tag corresponding to the last non-empty path-segment. The following code fails to transcode the tag for safe use in the URL query. Consider that a request on <code><nowiki>http://example.org/~user/app/tag/</nowiki></code> would map internally to a request on <code><nowiki>http://example.org/~user/app/script.php?tag=</nowiki></code> . Consider that a request on <code><nowiki>http://example.org/~user/app/tag/not-a-tag/the-tag</nowiki></code> would map internally to a request on <code><nowiki>http://example.org/~user/app/script.php?tag=not-a-tag/the-tag</nowiki></code> . Consider that a request on <code><nowiki>http://example.org/~user/app/tag/the-tag/</nowiki></code> would map internally to a request on <code><nowiki>http://example.org/~user/app/script.php?tag=the-tag/</nowiki></code> . Consider that a request on <code><nowiki>http://example.org/~user/app/tag/attack&intent=destroy</nowiki></code> would map internally to a request on <code><nowiki>http://example.org/~user/app/script.php?tag=attack&intent=destroy</nowiki></code> .
<pre><nowiki><Directory "/home/user/public_html/app/>
RewriteEngine On
RewriteRule ^tag/(.*)$ script.php?tag=$1
</Directory></nowiki></pre>
<ol start="4">
<li>''Does a rel tag still have meaning if the link redirects? If Apache returns a 302 status code, does the rel tag have meaning? Is there a formal rule that indexers should follow the link to the final, resolved destination? Or is there a formal rule that a rel tag should be ignored if URL of its link does not return a status code of 200?''
* ..next answer
</li>
</ol>

===CSS selector===
*How do you write a CSS selector for rel-tag?
** <code>a[rel~="tag"] { color: green }</code>

===Are tags case sensitive?===
*Are tags case sensitive. Is "Dog" the same tag as "dog" and "DOG"?
**{{AwaitingAnswer}}

===Multi-word tags===
*How should a multi-word tag be made? For instance, if using Wikipedia as a name space, a page about a Black Redstart (a bird) would be tagged '''Black_Redstart''', with an underscore [http://en.wikipedia.org/wiki/Black_Redstart]. Is there any way of aliasing alternatives ("BlackRedstart", "Black-Redstart", etc.)? Is any particular format preferable?
**{{AwaitingAnswer}}

===Tags with file extensions===
*Is <code><a rel=tag href="http://example.com/cheese.htm">cheese</a></code> a valid tag, for "cheese"? Ditto <code>.asp</code> or <code>.php</code> variants? If not, why not?
**{{AwaitingAnswer}}

===What about Scope?===
Since rel-tag is a feature used in many other microformats, the question often arises: "What is the scope of the tag?" For instance, a rel-tag may appear inside of an [[xfolk xFolk]] entry and on first glance it may appear that the tag should only apply to that entry. However, current publishing practice seems to indicate anything appearing on a page is likely related to the content of the page. Therefore, the interpretation is that not only does the rel-tag apply its direct container but to all containers and to the document as a whole; it contains the xFolk entry. This is a departure from strict knowledge theory in favor of real-world usage.

As another example, you may link to your friend Joe with XFN and hCard, indicating in his categories that Joe is interested in swimming, which you loathe. Since the article is primarily about you and not about Joe's hobbies and because the rel-tag is inside an hCard, you may expect that the rel-tag does not apply to the document; however, the document does contain information about swimming, namely that your friend likes it. In this way, rel-tag is binary: it indicates direction (yes or no) but not magnitude.

==Related pages==
{{rel-tag-related-pages}}
**{{AwaitingAnswer}}

hcard-examples-in-wild

2007-02-02T04:12:50Z

DerrickPallas: /* New Examples */

=hCard Examples in the wild=

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" 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]] markup. Examples added without a URL to a page with hCard markup 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 markup to your current contact page.

==New Examples==

Please add new examples to the '''top''' of this section.
* [http://www.alexa.com Alexa Internet] marked up its [http://www.alexa.com/site/company/managers managers' page] with hCard.
* [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://www.last.fm Last FM] has hCards hidden on their profile pages e.g. [http://www.last.fm/user/Crok/?scrobbling=t1].
* [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.
* IBM is embracing microformats. The [http://www.ibm.com/contact/employees/ IBM Employee Directory] now returns hCards in its query results. Also see the [http://www.ibm.com/shortcuts/ Shortcuts Podcast].
* [http://dsingleton.co.uk/ David Singleton] has added a hCard to his blog.
* [http://krisswatt.co.uk/ Kriss Watt] has hidden an hCard his blog footer.
* [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.fberriman.com/ Frances Berriman] has a hidden vCard in the footers of her website.
* [http://www.candlescience.com/ CandleScience Candle Supply] added a hidden hcard sitewide.
* [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://alexander-mette.de amette] uses the hCard format in a module of his TikiWiki powered blog
* [http://staff.washington.edu/oren/weblog2/ Oren Sreebny] has an hcard on his blog main index template
* [http://www.cs.brandeis.edu/~zippy/ Patrick Tufts] has an hCard on his homepage.
* [http://ascii20.blogspot.com/ Mathias Kolehmainen and Jamie Taylor] have hCards on their weblog.
* [http://www.hoppsan.org/jamesb/blogger/ Barnaby James] has a hCard on his weblog.
* [http://esa-education.com/schools/map ESA Education] Uses hCards for their 100+ schools and each of the individual school sites.
* [http://www.thereisnocat.com/#vcard Ralph Brandi] has added an hCard to the sidebar of his weblog as a result of Tantek Çelik's portion of the Microformats presentation at SXSW 2006.
* [http://www.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.meryl.net/ Meryl K. Evans] has a hidden hCard on her homepage.
* [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.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.

== Examples ==
* [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.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://tantek.com/ Tantek's Thoughts] includes an inline author hCard at the bottom of the page.
* [http://technorati.com/ Technorati]'s [http://www.technorati.com/about/ About page] lists their '''Media Contact'''
* [http://www.deadringerart.com/ The Brothers McDowell] have hCards at their Contact page.
* [http://twinsparc.com/ Twinsparc] put an hCard in the header and footer of all their pages.
* [http://tantek.com/microformats/2005/web2/speakers.html Web 2.0 Conference speakers page marked up with hCard]
* [http://we05.com/ Web Essentials 05] marked up all their [http://we05.com/presenters.cfm presenters with hCard].
* [http://www.uoguelph.ca/directory/ The University of Guelph] includes hCard info in its directory.
* [http://www.child-care-index.net.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]].
* The [http://technorati.com/about/ Technorati About page] has contact information marked up with hCard. By [[implementations#Technorati|Technorati]]
* The [http://technorati.com/press/ Technorati Press page] also has an hCard. By [[implementations#Technorati|Technorati]]
* The [http://technorati.com/about/staff.html Technorati Staff page] has many hCard. By [[implementations#Technorati|Technorati]]
* [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.

===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.
* [http://tantek.com/ Tantek's Thoughts] encodes Çelik as inline UTF8.

==Examples with some problems==

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

* [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://www.matthewwest.co.uk Matthew West] has an hCard on his [http://www.matthewwest.co.uk/email contact] page.
**Flat- and building- number run on.
*[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)
* The good ship [http://styrheim.com/test/leonid.html Leonid Miloslavskiy] spotted in the North Atlantic
** INVALID --[[User:RyanKing|RyanKing]] 00:50, 27 Oct 2005 (PDT)
*** class="family" should probably be family-name
*** the "n" property is missing and the "n" optimization can't be applied
*** the first geo propery is empty, the second one is invalid (i.e., it doesn't contain lat/long)
* [http://landsbank.fo/#hCard Landsbanki Føroya]
** INVALID - using embedded RDF/XML invalidly
* [http://chrischerry.name/ Chris Cherry's contact page with his hCard]
** <strike>WARNING - uses class="cell" instead of <span class="type">cell</span></strike> Fixed -- [[User:Seriph|Chris Cherry]] 19:54, 15 Sep 2006 (PST)
* [http://www.bath.ac.uk/contact/ University of Bath] Person Finder results are encoded with hCards so you can easily create a vCard from any result.
** ERROR - attempt to use Implied-N optimization where that's not possible. --[[User:RyanKing|RyanKing]] 14:29, 5 Jan 2006 (PST)
** Error appears for external users only. Won't be fixed any time soon. -- [[User:PhilWilson|PhilWilson]] 00:03, 28 Jan 2006 (GMT)
* [http://richi.co.uk/blog/2005/12/structured-blogging.html Richi Jennings] has put up his attempt
** INVALID, missing "fn"--[[User:RyanKing|RyanKing]] 12:47, 5 Jan 2006 (PST)
* [http://www.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)

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

depend-examples

2007-02-01T03:33:04Z

DerrickPallas: /* Portage: dev-lang/erlang */

= depend examples =
== Overview ==
This page is dedicated to fleshing out examples of dependency (software and otherwise) on the Web-At-Large.
== Authors ==

* [[DerrickPallas|Derrick Pallas]]
* [[BenWest|Ben West]]

== Motivation ==
Right now, there many ways to install software; whether you're using
binaries (apt-get, yum, rpm) or source (emerge, srpm, *-src), you have
to go through a clearing house. Someone took the time to compile
binaries or repackage source trees and write down what needed what.

But the fact is all of this information is already on the homepage for
most software. Current aggregators rely on the author(s) submitting this
information manually. Furthermore, commercial packages don't normally
submit product information to sites like FreshMeat, SourceForge, or any
language-specific repository (CPAN, PEAR). (This includes things like drivers.)

Because the information (version, dependency, package URLs, bug alerts)
is already there (see below) it should be fairly straight-forward to
figure out what people already do and "semantic it up."

== Examples ==

=== Linux Kernel ===
http://kernel.org/
* uses <link> to provide RSS feed
* <div id="versions"> uses word "versions"
* uses links to deliverable with version string as anchor text
* uses a kind of "product/software id" (my made up term) <table
class="kver"> to identify the thing being described
* includes a description of the software
* includes the date published
* uses keywords as anchor text to perform operations or view
additional features. for example, V for view diff, changelog to see
the changelog, etc...

=== libPNG ===
http://libpng.org/pub/png/libpng.html
* <LINK REV="made" HREF="http://pobox.com/~newt/greg_contact.html">
Interesting. "made by "his guy" :-) . hcard would seem to be a
perfect fit here.
* <B>libpng</B> name of software in an element
* <A HREF=
"http://libpng.sourceforge.net/">http://libpng.sourceforge.net/</A>
link to homepage
* requires <B>zlib 1.0.4</B>
or later (<B>1.2.3</B> or <B>1.1.4</B> lossy markup of requirements
* The current public release, <B>libpng 1.2.15</B> again, lossy markup
* includes a description of the software
* <B>libpng 1.2.12</B> another mention of the software in it's own element
* the site contains links to test suites, documentation, and download links
* also includes a description of how to verify the contents
* lots of content about the software, but very little semantic markup.
good example: easy to see how some semantic techniques would help.
would marking this up using hatom help at all?

=== libvc ===
http://freshmeat.net/projects/libvc/
* uses <link> to an rss feed
* links to other project areas... issue tracking, forums etc...
* branch info published
* date added, created, modified all published
* description
* author
* "trove" categories
* might list dependencies, but there are none for this particular example
* stats listed: vitality, popularity, downloads, graphs...
* hits, subscribers
* other projects depending on this one are listed
* license published
* download links provided
* no semantic markup present.

=== Ruby FastCGI ===
http://raa.ruby-lang.org/project/fcgi/
* <link> and <meta> used to convey authorship, "made", author, and
some other attributes: search, index, home, glossary
* interesting, there is some semantic html...
<p class="caption">fcgi / 0.8.7</p>
<table class="entry">
* key value pairs (in a table) for: short description, category,
status, created, last update, owner, homepage, download, source
vieweing, license, dependency, versions as link text to the
deliverable with date published outside the link
* uses address to list contact for the document, and other uses of
semantic html such as class names "footer", "header", and "caption".
Shows a receptivity to semantic techniques as well as confirming the
list of properties published by software vendors.

=== Portage: dev-lang/erlang ===
http://www.gentoo-portage.com/dev-lang/erlang/Dep#ptabs
* <link> to rss feed
* <body id="gentoo-portage"> intended consumer published in markup
* links to other project areas
* <h2 id="packageid">dev-lang/erlang </h2> product name
* <h5> used for description
* <div id="website_list"><ul>...</ul></div> used to list project websites
* <div id="ebuild_list"><ul>... used for consumer-specific parameters
* "view" and "download" links.
* <h3>Runtime Dependencies</h3> dependencies published using <div
class="depbox with links.
* >= <a href="/dev-lang/perl">dev-lang/perl</a>-5.6.1
* the previous behaviour is used for each version of the published software
Lots of semantic html. Could be clues for possibles property names.

== See Also ==
* [[rel-tag]] (for language, etc.)
* [[rel-license]]
* [[hcard hCard]] (for authors)

* [[http://usefulinc.com/doap/ DOAP]] (similar in nature)

depend-examples

2007-02-01T03:31:37Z

DerrickPallas:

= depend examples =
== Overview ==
This page is dedicated to fleshing out examples of dependency (software and otherwise) on the Web-At-Large.
== Authors ==

* [[DerrickPallas|Derrick Pallas]]
* [[BenWest|Ben West]]

== Motivation ==
Right now, there many ways to install software; whether you're using
binaries (apt-get, yum, rpm) or source (emerge, srpm, *-src), you have
to go through a clearing house. Someone took the time to compile
binaries or repackage source trees and write down what needed what.

But the fact is all of this information is already on the homepage for
most software. Current aggregators rely on the author(s) submitting this
information manually. Furthermore, commercial packages don't normally
submit product information to sites like FreshMeat, SourceForge, or any
language-specific repository (CPAN, PEAR). (This includes things like drivers.)

Because the information (version, dependency, package URLs, bug alerts)
is already there (see below) it should be fairly straight-forward to
figure out what people already do and "semantic it up."

== Examples ==

=== Linux Kernel ===
http://kernel.org/
* uses <link> to provide RSS feed
* <div id="versions"> uses word "versions"
* uses links to deliverable with version string as anchor text
* uses a kind of "product/software id" (my made up term) <table
class="kver"> to identify the thing being described
* includes a description of the software
* includes the date published
* uses keywords as anchor text to perform operations or view
additional features. for example, V for view diff, changelog to see
the changelog, etc...

=== libPNG ===
http://libpng.org/pub/png/libpng.html
* <LINK REV="made" HREF="http://pobox.com/~newt/greg_contact.html">
Interesting. "made by "his guy" :-) . hcard would seem to be a
perfect fit here.
* <B>libpng</B> name of software in an element
* <A HREF=
"http://libpng.sourceforge.net/">http://libpng.sourceforge.net/</A>
link to homepage
* requires <B>zlib 1.0.4</B>
or later (<B>1.2.3</B> or <B>1.1.4</B> lossy markup of requirements
* The current public release, <B>libpng 1.2.15</B> again, lossy markup
* includes a description of the software
* <B>libpng 1.2.12</B> another mention of the software in it's own element
* the site contains links to test suites, documentation, and download links
* also includes a description of how to verify the contents
* lots of content about the software, but very little semantic markup.
good example: easy to see how some semantic techniques would help.
would marking this up using hatom help at all?

=== libvc ===
http://freshmeat.net/projects/libvc/
* uses <link> to an rss feed
* links to other project areas... issue tracking, forums etc...
* branch info published
* date added, created, modified all published
* description
* author
* "trove" categories
* might list dependencies, but there are none for this particular example
* stats listed: vitality, popularity, downloads, graphs...
* hits, subscribers
* other projects depending on this one are listed
* license published
* download links provided
* no semantic markup present.

=== Ruby FastCGI ===
http://raa.ruby-lang.org/project/fcgi/
* <link> and <meta> used to convey authorship, "made", author, and
some other attributes: search, index, home, glossary
* interesting, there is some semantic html...
<p class="caption">fcgi / 0.8.7</p>
<table class="entry">
* key value pairs (in a table) for: short description, category,
status, created, last update, owner, homepage, download, source
vieweing, license, dependency, versions as link text to the
deliverable with date published outside the link
* uses address to list contact for the document, and other uses of
semantic html such as class names "footer", "header", and "caption".
Shows a receptivity to semantic techniques as well as confirming the
list of properties published by software vendors.

=== Portage: dev-lang/erlang ===
http://www.gentoo-portage.com/dev-lang/erlang/Dep#ptabs
* <link> to rss feed
* <body id="gentoo-portage"> intended consumer published in markup
* links to other project areas
* <h2 id="packageid">dev-lang/erlang </h2> product name
* <h5> used for description
* <div id="website_list"><ul>...</ul></div> used to list project websites
* <div id="ebuild_list"><ul>... used for consumer-specific parameters
* "view" and "download" links.
* <h3>Runtime Dependencies</h3> dependencies published using <div
class="depbox with links.
* >=<a href="/dev-lang/perl">dev-lang/perl</a>-5.6.1
* the previous behaviour is used for each version of the published software
Lots of semantic html. Could be clues for possibles property names.

== See Also ==
* [[rel-tag]] (for language, etc.)
* [[rel-license]]
* [[hcard hCard]] (for authors)

* [[http://usefulinc.com/doap/ DOAP]] (similar in nature)

depend-examples

2007-02-01T03:31:12Z

DerrickPallas:

= depend examples =
== Overview ==
This page is dedicated to fleshing out examples of dependency (software and otherwise) on the Web-At-Large.
== Authors ==

* [[DerrickPallas|Derrick Pallas]]

== Motivation ==
Right now, there many ways to install software; whether you're using
binaries (apt-get, yum, rpm) or source (emerge, srpm, *-src), you have
to go through a clearing house. Someone took the time to compile
binaries or repackage source trees and write down what needed what.

But the fact is all of this information is already on the homepage for
most software. Current aggregators rely on the author(s) submitting this
information manually. Furthermore, commercial packages don't normally
submit product information to sites like FreshMeat, SourceForge, or any
language-specific repository (CPAN, PEAR). (This includes things like drivers.)

Because the information (version, dependency, package URLs, bug alerts)
is already there (see below) it should be fairly straight-forward to
figure out what people already do and "semantic it up."

== Examples ==

=== Linux Kernel ===
http://kernel.org/
* uses <link> to provide RSS feed
* <div id="versions"> uses word "versions"
* uses links to deliverable with version string as anchor text
* uses a kind of "product/software id" (my made up term) <table
class="kver"> to identify the thing being described
* includes a description of the software
* includes the date published
* uses keywords as anchor text to perform operations or view
additional features. for example, V for view diff, changelog to see
the changelog, etc...

=== libPNG ===
http://libpng.org/pub/png/libpng.html
* <LINK REV="made" HREF="http://pobox.com/~newt/greg_contact.html">
Interesting. "made by "his guy" :-) . hcard would seem to be a
perfect fit here.
* <B>libpng</B> name of software in an element
* <A HREF=
"http://libpng.sourceforge.net/">http://libpng.sourceforge.net/</A>
link to homepage
* requires <B>zlib 1.0.4</B>
or later (<B>1.2.3</B> or <B>1.1.4</B> lossy markup of requirements
* The current public release, <B>libpng 1.2.15</B> again, lossy markup
* includes a description of the software
* <B>libpng 1.2.12</B> another mention of the software in it's own element
* the site contains links to test suites, documentation, and download links
* also includes a description of how to verify the contents
* lots of content about the software, but very little semantic markup.
good example: easy to see how some semantic techniques would help.
would marking this up using hatom help at all?

=== libvc ===
http://freshmeat.net/projects/libvc/
* uses <link> to an rss feed
* links to other project areas... issue tracking, forums etc...
* branch info published
* date added, created, modified all published
* description
* author
* "trove" categories
* might list dependencies, but there are none for this particular example
* stats listed: vitality, popularity, downloads, graphs...
* hits, subscribers
* other projects depending on this one are listed
* license published
* download links provided
* no semantic markup present.

=== Ruby FastCGI ===
http://raa.ruby-lang.org/project/fcgi/
* <link> and <meta> used to convey authorship, "made", author, and
some other attributes: search, index, home, glossary
* interesting, there is some semantic html...
<p class="caption">fcgi / 0.8.7</p>
<table class="entry">
* key value pairs (in a table) for: short description, category,
status, created, last update, owner, homepage, download, source
vieweing, license, dependency, versions as link text to the
deliverable with date published outside the link
* uses address to list contact for the document, and other uses of
semantic html such as class names "footer", "header", and "caption".
Shows a receptivity to semantic techniques as well as confirming the
list of properties published by software vendors.

=== Portage: dev-lang/erlang ===
http://www.gentoo-portage.com/dev-lang/erlang/Dep#ptabs
* <link> to rss feed
* <body id="gentoo-portage"> intended consumer published in markup
* links to other project areas
* <h2 id="packageid">dev-lang/erlang </h2> product name
* <h5> used for description
* <div id="website_list"><ul>...</ul></div> used to list project websites
* <div id="ebuild_list"><ul>... used for consumer-specific parameters
* "view" and "download" links.
* <h3>Runtime Dependencies</h3> dependencies published using <div
class="depbox with links.
* >=<a href="/dev-lang/perl">dev-lang/perl</a>-5.6.1
* the previous behaviour is used for each version of the published software
Lots of semantic html. Could be clues for possibles property names.

== See Also ==
* [[rel-tag]] (for language, etc.)
* [[rel-license]]
* [[hcard hCard]] (for authors)

* [[http://usefulinc.com/doap/ DOAP]] (similar in nature)

include-pattern-feedback

2007-01-31T20:38:10Z

DerrickPallas: /* Concatenating values */

= Include Pattern Feedback =

Feedback about [[include-pattern]].

== Objects and Browser Behavior ==

Over at Yahoo! Local, we were using the object include pattern for all our [[hreview|hReviews]] on business detail pages and review listings. That is, until we realized that Safari and Internet Explorer both try to embed the entire page with every OBJECT call. (Firefox correctly recognizes that it's a local object and doesn't reload anything.)

On a page with 20+ reviews, this means a substantial increase in load time and memory consumption. As a result of this (bad) browser behavior, we removed the objects entirely.

Any suggestions for workarounds or modifications to the pattern?

-- AndyBaio 29 Jun 2006

Can you use the hyperlink option with DHMTL/Ajax to perform replacements in advanced browsers? (Simon Willison's <code>[http://simon.incutio.com/archive/2003/03/25/getElementsBySelector getElementsBySelector()]</code> may be helpful)
<a href="#id" class="include" title=""></a>
with something like:
//Works only for linked include-pattern definition at microformats.org
//Requires Simon Willison's getElementsBySelector()
// and normal IE workaround for addEventListener()
addEventListener( window, 'load', function() {
var myIncludes = document.getElementsBySelector( 'a[href].include' ), a, e;
for( var i=0; a=myIncludes[i]; i++ ) if (a.href.charAt(0)=='#') {
e = document.getElementsBySelector( a.href )[0].cloneNode( true );
a.parentNode.replaceChild( e, a );
}
})
--[[User:RichHall|RichHall]] 00:51, 23 Oct 2006 (PDT)

My hResume page [http://robert.o-rourke.org seen here] caused Safari <ins>2.0</ins> some major issues. The page was jumping between object elements when a link was hovered eventually causing the browser to crash. You can follow the thread on the [http://www.mail-archive.com/listdad%40webstandardsgroup.org/msg06078.html WSG mail archive].

It seems that while the object element may be more semantically appropriate it <del>is not</del> <ins>may not be</ins> usable in lieu of the issues raised in Safari.

--[[User:SanchoTheFat|Robert O'Rourke]] 12:08, 3 Nov 2006 (PST)

Which version of Safari? Please be specific as many Safari OBJECT bugs were fixed in Safari 2.x.

-- [[User:Tantek|Tantek]] 13:39, 3 Nov 2006 (PST)

== Hyperlink Include - Screen Reader Testing ==

Some [http://microformats.org/discuss/mail/microformats-discuss/2006-July/004693.html concerns have been raised] over the implications using empty hyperlinks may have on assistive devices such as screen readers. One concern is that an empty link may be read out, partially read out or result in some other confusing scenario for the user.

In response, a [http://allinthehead.com/demo/include.html test page] consisting of a number of empty hyperlinks in the style suggested by the pattern has been created. A 'good' result is that none of the links be read out.

=== Test Results: JAWS 7.0 with Firefox 1.5/Win ===

Tested by [[User:Phae|Frances Berriman]] 2006-07-21.

* 31 dash include dash Mozilla Firefox
* Page has no links
* 31 dash include

Conclusion: the hyperlink include pattern presented no usability issues for this screen reader.

=== Proprietary attribute ===
HTML tidy on the [http://allinthehead.com/demo/include.html test page] gives:
:Warning: <a> proprietary attribute "data"

The [http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fallinthehead.com%2Fdemo%2Finclude.html W3C validator is similarly unimpressed].

[[User:AndyMabbett|AndyMabbett]] 14:22, 22 Oct 2006 (PDT)

==== Use href ====
To clarify, links on the [http://allinthehead.com/demo/include.html test page] should be changed to use the <code>href</code> attribute as described at [[include-pattern]] (without <code>href</code> attributes, the elements probably won't register as hyperlinks, but anchors). Set <code>title=""</code> to fix empty link behavior for many assistive devices. --[[User:RichHall|RichHall]] 23:31, 22 Oct 2006 (PDT)

==== Test page corrected ====
2006-10-25: This error has been corrected on the [http://allinthehead.com/demo/include.html test page]. Any tests should probably be re-run in light of this.

== Unclear status ==

It's not clear, either from the main Wiki page or [[include-pattern]], whether this is an agreed standard, a draft, or just a proposal. [[User:AndyMabbett|AndyMabbett]] 03:14, 18 Oct 2006 (PDT)

* [[include-pattern]] is not its own proposal, draft, or spec. It is a design pattern, as listed on the [[Main_Page|wiki home page]] that is included in other proposals, drafts. and specs. ''Recommend for adding to the [[include-pattern-faq]].
**And that is not clear, either from the main Wiki page or [[include-pattern]]. [[User:AndyMabbett|AndyMabbett]] 16:40, 18 Oct 2006 (PDT)
***ACCEPTED. Will further clarify relationship between patterns and formats. [[User:Tantek|Tantek]] 16:48, 18 Oct 2006 (PDT)

==Parsing for include-pattern==

''Note: this issue is obsolete. On a [http://rbach.priv.at/Microformats-IRC/2007-01-03#T165528 IRC conversation 2007-01-03], Mike Kaply admitted that he figured this out, which is to apply all includes first into the parse tree before looking for any properties. -Tantek''

''To be more specific, what finally occurred to me is that the object pattern is simply about grabbing nodes from another vcard and using them in this vcard. So the implementor responsibility is just to clone the dom node from the other vcard and replace the object with the corresponding nodes. Works great. (of course I also had to clone the entire vcard since I can't manipulate the DOM like that without changing the page) -mkaply''

In an [http://rbach.priv.at/Microformats-IRC/2007-01-02#T205847 IRC discussion] with [http://www.kaply.com/weblog/ Mike Kaply] (author of the [https://addons.mozilla.org/firefox/4106/ Operator] extension for Firefox) we discussed the difficulty of parsing for an [[include-pattern]] in [[hresume|hResume]]. Mike asks:
<blockquote>I'm really wondering why the <code>object</code> stuff doesn't point back to the entire vCard. I don't understand why the spec has it point to individual items.</blockquote>
The problem was thought to be a weakness in the specification, which doesn't specify what part of the data is in the content that is pointed to by the <code>object</code>.

Currently, to overcome this a parser needs to follow this logic:
::IF I don't find an <code>fn</code>, look for an <code>object</code>. IF there is an <code>object</code>, do a <code>getelementbyid</code> on that <code>ID</code>, but yet there was nothing about that <code>object</code> that said that the content I was looking for in the other card was an <code>fn</code>

Two things may help in overcoming this difficulty:

# Change the spec to have the include-pattern reference the entire vCard, with the intent that any data not found in this vCard use the other vCard
# Include the element of the reference, where the class attribute on <code><object></code> has "include" plus the element that needs to be included. For example:
<pre><nowiki><object
class="include fn" data="#vcard-name">myname</object> </nowiki></pre>

Additionally, I pointed out that using the <code><object></code> element to contain the reference makes Microsoft's Internet Explorer throw an error "Your current security settings prohibit ActiveX controls on this page. As a result, the page may not display correctly." Of course, there is no ActiveX content on an include-pattern.

[[User:Bob Jonkman|Bob Jonkman]] 21:15, 2 Jan 2007 (PST)#

==Concatenating values==

I feel that there should be a way to "include" data from two places, in one microformat property. For instance:

<pre><nowiki><span id="summaryA" class="summary">Kidderminster Branch Indoor Meeting</span></nowiki></pre>
<pre><nowiki><span id="summaryB>Janaury</span></nowiki></pre>

and later

<pre><nowiki><object data="#summaryB+#summaryA" class="include"></object></nowiki></pre>

would give a summary of:

:'''January Kidderminster Branch Indoor Meeting'''

It may even be possible to include extra data:

<pre><nowiki><span id="summaryC>Fred Smith</span></nowiki></pre>

<pre><nowiki><object data="#summaryA+ with +#summaryC" class="include"></object></nowiki></pre>

to give:

:'''Kidderminster Branch Indoor Meeting with Fred Smith'''

[[User:AndyMabbett|Andy Mabbett]] 14:33, 8 Jan 2007 (PST)

Why not use

<pre><nowiki><span class="value"><object data="#summaryA" class="include"></object> with <object data="#summaryB" class="include"></object></span></nowiki></pre>

to build

:'''Kidderminster Branch Indoor Meeting with Fred Smith'''

[[User:DerrickPallas|Derrick Pallas]] 11:15, 31 Jan 2007 (PST)

:Neat solution! Can anyone say whether current parsers accept this? [[User:AndyMabbett|Andy Mabbett]] 12:18, 31 Jan 2007 (PST)

:Fully disclosure: My XSLT transformer supports this implicitly because it does include-pattern first, then pulls values. My only question would be what to do with nested @class="value" elements that could result from this. [[User:DerrickPallas|Derrick Pallas]] 12:35, 31 Jan 2007 (PST)

==Related Pages==
{{include-pattern-related-pages}}

include-pattern-feedback

2007-01-31T19:16:18Z

DerrickPallas: /* Concatenating values */

= Include Pattern Feedback =

Feedback about [[include-pattern]].

== Objects and Browser Behavior ==

Over at Yahoo! Local, we were using the object include pattern for all our [[hreview|hReviews]] on business detail pages and review listings. That is, until we realized that Safari and Internet Explorer both try to embed the entire page with every OBJECT call. (Firefox correctly recognizes that it's a local object and doesn't reload anything.)

On a page with 20+ reviews, this means a substantial increase in load time and memory consumption. As a result of this (bad) browser behavior, we removed the objects entirely.

Any suggestions for workarounds or modifications to the pattern?

-- AndyBaio 29 Jun 2006

Can you use the hyperlink option with DHMTL/Ajax to perform replacements in advanced browsers? (Simon Willison's <code>[http://simon.incutio.com/archive/2003/03/25/getElementsBySelector getElementsBySelector()]</code> may be helpful)
<a href="#id" class="include" title=""></a>
with something like:
//Works only for linked include-pattern definition at microformats.org
//Requires Simon Willison's getElementsBySelector()
// and normal IE workaround for addEventListener()
addEventListener( window, 'load', function() {
var myIncludes = document.getElementsBySelector( 'a[href].include' ), a, e;
for( var i=0; a=myIncludes[i]; i++ ) if (a.href.charAt(0)=='#') {
e = document.getElementsBySelector( a.href )[0].cloneNode( true );
a.parentNode.replaceChild( e, a );
}
})
--[[User:RichHall|RichHall]] 00:51, 23 Oct 2006 (PDT)

My hResume page [http://robert.o-rourke.org seen here] caused Safari <ins>2.0</ins> some major issues. The page was jumping between object elements when a link was hovered eventually causing the browser to crash. You can follow the thread on the [http://www.mail-archive.com/listdad%40webstandardsgroup.org/msg06078.html WSG mail archive].

It seems that while the object element may be more semantically appropriate it <del>is not</del> <ins>may not be</ins> usable in lieu of the issues raised in Safari.

--[[User:SanchoTheFat|Robert O'Rourke]] 12:08, 3 Nov 2006 (PST)

Which version of Safari? Please be specific as many Safari OBJECT bugs were fixed in Safari 2.x.

-- [[User:Tantek|Tantek]] 13:39, 3 Nov 2006 (PST)

== Hyperlink Include - Screen Reader Testing ==

Some [http://microformats.org/discuss/mail/microformats-discuss/2006-July/004693.html concerns have been raised] over the implications using empty hyperlinks may have on assistive devices such as screen readers. One concern is that an empty link may be read out, partially read out or result in some other confusing scenario for the user.

In response, a [http://allinthehead.com/demo/include.html test page] consisting of a number of empty hyperlinks in the style suggested by the pattern has been created. A 'good' result is that none of the links be read out.

=== Test Results: JAWS 7.0 with Firefox 1.5/Win ===

Tested by [[User:Phae|Frances Berriman]] 2006-07-21.

* 31 dash include dash Mozilla Firefox
* Page has no links
* 31 dash include

Conclusion: the hyperlink include pattern presented no usability issues for this screen reader.

=== Proprietary attribute ===
HTML tidy on the [http://allinthehead.com/demo/include.html test page] gives:
:Warning: <a> proprietary attribute "data"

The [http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fallinthehead.com%2Fdemo%2Finclude.html W3C validator is similarly unimpressed].

[[User:AndyMabbett|AndyMabbett]] 14:22, 22 Oct 2006 (PDT)

==== Use href ====
To clarify, links on the [http://allinthehead.com/demo/include.html test page] should be changed to use the <code>href</code> attribute as described at [[include-pattern]] (without <code>href</code> attributes, the elements probably won't register as hyperlinks, but anchors). Set <code>title=""</code> to fix empty link behavior for many assistive devices. --[[User:RichHall|RichHall]] 23:31, 22 Oct 2006 (PDT)

==== Test page corrected ====
2006-10-25: This error has been corrected on the [http://allinthehead.com/demo/include.html test page]. Any tests should probably be re-run in light of this.

== Unclear status ==

It's not clear, either from the main Wiki page or [[include-pattern]], whether this is an agreed standard, a draft, or just a proposal. [[User:AndyMabbett|AndyMabbett]] 03:14, 18 Oct 2006 (PDT)

* [[include-pattern]] is not its own proposal, draft, or spec. It is a design pattern, as listed on the [[Main_Page|wiki home page]] that is included in other proposals, drafts. and specs. ''Recommend for adding to the [[include-pattern-faq]].
**And that is not clear, either from the main Wiki page or [[include-pattern]]. [[User:AndyMabbett|AndyMabbett]] 16:40, 18 Oct 2006 (PDT)
***ACCEPTED. Will further clarify relationship between patterns and formats. [[User:Tantek|Tantek]] 16:48, 18 Oct 2006 (PDT)

==Parsing for include-pattern==

''Note: this issue is obsolete. On a [http://rbach.priv.at/Microformats-IRC/2007-01-03#T165528 IRC conversation 2007-01-03], Mike Kaply admitted that he figured this out, which is to apply all includes first into the parse tree before looking for any properties. -Tantek''

''To be more specific, what finally occurred to me is that the object pattern is simply about grabbing nodes from another vcard and using them in this vcard. So the implementor responsibility is just to clone the dom node from the other vcard and replace the object with the corresponding nodes. Works great. (of course I also had to clone the entire vcard since I can't manipulate the DOM like that without changing the page) -mkaply''

In an [http://rbach.priv.at/Microformats-IRC/2007-01-02#T205847 IRC discussion] with [http://www.kaply.com/weblog/ Mike Kaply] (author of the [https://addons.mozilla.org/firefox/4106/ Operator] extension for Firefox) we discussed the difficulty of parsing for an [[include-pattern]] in [[hresume|hResume]]. Mike asks:
<blockquote>I'm really wondering why the <code>object</code> stuff doesn't point back to the entire vCard. I don't understand why the spec has it point to individual items.</blockquote>
The problem was thought to be a weakness in the specification, which doesn't specify what part of the data is in the content that is pointed to by the <code>object</code>.

Currently, to overcome this a parser needs to follow this logic:
::IF I don't find an <code>fn</code>, look for an <code>object</code>. IF there is an <code>object</code>, do a <code>getelementbyid</code> on that <code>ID</code>, but yet there was nothing about that <code>object</code> that said that the content I was looking for in the other card was an <code>fn</code>

Two things may help in overcoming this difficulty:

# Change the spec to have the include-pattern reference the entire vCard, with the intent that any data not found in this vCard use the other vCard
# Include the element of the reference, where the class attribute on <code><object></code> has "include" plus the element that needs to be included. For example:
<pre><nowiki><object
class="include fn" data="#vcard-name">myname</object> </nowiki></pre>

Additionally, I pointed out that using the <code><object></code> element to contain the reference makes Microsoft's Internet Explorer throw an error "Your current security settings prohibit ActiveX controls on this page. As a result, the page may not display correctly." Of course, there is no ActiveX content on an include-pattern.

[[User:Bob Jonkman|Bob Jonkman]] 21:15, 2 Jan 2007 (PST)#

==Concatenating values==

I feel that there should be a way to "include" data from two places, in one microformat property. For instance:

<pre><nowiki><span id="summaryA" class="summary">Kidderminster Branch Indoor Meeting</span></nowiki></pre>
<pre><nowiki><span id="summaryB>Janaury</span></nowiki></pre>

and later

<pre><nowiki><object data="#summaryB+#summaryA" class="include"></object></nowiki></pre>

would give a summary of:

:'''January Kidderminster Branch Indoor Meeting'''

It may even be possible to include extra data:

<pre><nowiki><span id="summaryC>Fred Smith</span></nowiki></pre>

<pre><nowiki><object data="#summaryA+ with +#summaryC" class="include"></object></nowiki></pre>

to give:

:'''Kidderminster Branch Indoor Meeting with Fred Smith'''

[[User:AndyMabbett|Andy Mabbett]] 14:33, 8 Jan 2007 (PST)

Why not use

<pre><nowiki><span class="value"><object data="#summaryA" class="include"></object> with <object data="#summaryB" class="include"></object></span></nowiki></pre>

to build

:'''Kidderminster Branch Indoor Meeting with Fred Smith'''

[[User:DerrickPallas|Derrick Pallas]] 11:15, 31 Jan 2007 (PST)

==Related Pages==
{{include-pattern-related-pages}}

hcard

2007-01-30T00:43:55Z

DerrickPallas: that's what i get for not hitting preview

<h1>hCard</h1>

hCard is a simple, open, distributed format for representing people, companies, organizations, and places, using a 1:1 representation of the properties and values of the vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]) in [[semantic-xhtml|semantic XHTML]]. hCard is one of several open [[microformats|microformat]] standards suitable for embedding in (X)HTML, Atom, RSS, and arbitrary XML.

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

__TOC__

== Specification ==

=== Editor ===
[http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc.]

=== Authors ===
* [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc]
* [http://suda.co.uk/ Brian Suda]

=== Copyright ===
{{MicroFormatCopyrightStatement2004}}

=== Patents ===
{{MicroFormatPatentStatement}}

=== Inspiration and Acknowledgments ===
Thanks to: my good friend [http://vadim.com/ Vadim] who introduced me to vCard ''many'' years ago, and if I'd only paid more attention then, perhaps I could have helped a lot of people avoid wasting a lot of time reinventing various standards wheels.

== Introduction ==
The vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]), has been broadly interoperably implemented (e.g. Apple's "Address Book" application built into MacOSX).

In addition, many bloggers identify themselves by name and discuss their friends and family. With just a tad bit of structure, bloggers can discuss people in their blog(s) in such a way that spiders and other aggregators can retrieve this information, automatically convert them to vCards, and use them in any vCard application or service.

This specification introduces the '''hCard''' format, which uses a 1:1 representation of the properties and values of the aforementioned vCard standard, in semantic XHTML. Bloggers can both embed hCards directly in their web pages, and style them with CSS to make them appear as desired. In addition, hCard enables applications to retrieve information directly from web pages without having to reference a separate file.

Use the [http://microformats.org/code/hcard/creator hCard creator] and copy the HTML code it generates to your blog or website to publish your contact info.

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

== Format ==
=== In General ===
The vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]) forms the basis of hCard.

The basic format of hCard is to use vCard object/property names in lower-case for class names, and to map the nesting of vCard objects directly into nested XHTML elements.

=== More Semantic Equivalents ===
For some properties there are HTML elements which better match and convey their semantics. The following properties SHOULD be encoded with the following (X)HTML:
* <code>URL</code> in vCard becomes <code><a class="url" href="...">...</a></code> inside the element with <code>class="vcard"</code> in hCard.
* Similarly, <code>EMAIL</code> in vCard becomes <code><nowiki><a class="email" href="mailto:...">...</a></nowiki></code>
* <code>PHOTO</code> in vCard becomes <code><img class="photo" src="..." alt="Photo of ..." /></code> or <code><object class="photo" data="..." type="...">Photo of ...</object></code>
* <code>UID</code> in vCard simply becomes another semantic applied to a specific URL (or EMAIL) for an hCard.

=== Singular vs. Plural Properties ===
For properties which are singular (e.g. "N" and "FN"), the first descendant element with that class should take effect, any others being ignored.

For properties which can be plural (e.g. "TEL"), each class instance should create a instance of that property.

==== Singular properties ====

Singular properties: "FN", "N", "BDAY", "TZ", "GEO", "SORT-STRING", "UID", "CLASS".

All other properties are plural. This list has been derived by analyzing the semantics of the individual properties in vCard RFC2426 and determining logically that they MUST be singular per their semantics. See [[hcard-singular-properties]] for explanations.

==== Plural Properties Singularized ====

Since plural property names become their singular equivalents, even if the original plural property permitted only a single value with multiple components, those multiple components are represented each with their own singularly named property and the the property is effectively multivalued and subject to the above treatment of multivalued properties.

=== Human vs. Machine readable ===

If an <code><abbr></code> element is used for a property, then the '<code>title</code>' attribute of the <code><abbr></code> element is the value of the property, instead of the contents of the element, which instead provide a human presentable version of the value.

If an <code><a></code> element is used for one or more properties, it must be treated as follows:
# For the "PHOTO" property and any other property that takes a URL as its value, the <code>href="..."</code> attribute provides the property value.
# For other properties, the element's content is the value of the property.

If an <code><img></code> element is used for one or more properties, it must be treated as follows:
# For the "PHOTO" property and any other property that takes a URL as its value, the <code>src="..."</code> attribute provides the property value.
# For other properties, the <code><img></code> element's '<code>alt</code>' attribute is the value of the property.

If an <code><object></code> element is used for one or more properties, it must be treated as follows:
# For the "PHOTO" property and any other property that takes a URL as its value, the <code>data="..."</code> attribute provides the property value.
# For other properties, the element's content is the value of the property.

=== Value excerpting ===

Sometimes only part of an element which is the equivalent for a property should be used for the value of the property. This typically occurs when a property has a subtype, like TEL. For this purpose, the special class name "<code>value</code>" is introduced to excerpt out the subset of the element that is the value of the property. E.g. here is an hCard fragment for marking up a home phone number:<br />

vCard:
<pre><nowiki>
TEL;TYPE=HOME:+1.415.555.1212
</nowiki></pre>

hCard:
<pre><nowiki>
<span class="tel">
<span class="type">home</span>:
<span class="value">+1.415.555.1212</span>
</span>
</nowiki></pre>

This hCard fragment could be displayed as:

<div style="border: thin dashed black; width: 95%; padding: .5em 1em;">
<span class="tel">
<span class="type">home</span>:
<span class="value">+1.415.555.1212</span>
</span>
</div>

=== Property Exceptions ===

vCard has several properties which either do not make sense on, or are already implied within the context of a web page. This section explains what to (not) do with them.

# '''NAME''', '''PROFILE''', '''SOURCE''', '''PRODID''', '''VERSION''' properties as defined in Sections 2.1.2, 2.1.3, 2.1.4, 3.6.3, 3.6.9 of RFC 2426. Content publishers MUST NOT use these properties in their hCards, and as such, hCard consumers/parsers MUST IGNORE these properties if they are found within an hCard. Instead. hCard to vCard converters SHOULD use the title of the page where the hCard is found (e.g. the <code><title></code> element in (X)HTML documents) to construct the NAME property, MAY output a PROFILE value of "<code>VCARD</code>" per RFC 2426, SHOULD use the URL of the page where the hCard is found to construct the SOURCE property (e.g. perhaps as a parameter to a URL/service that converts hCards to vCards), for an output vCard stream (e.g. a .vcf file). Only services/applications that output actual vCards should write the PRODID property, with the product identifier for said service/application. Similarly only such services/applications should write the VERSION property, with the value "3.0" (without quotes) per RFC2426 Section 3.6.9.

=== Organization Contact Info ===

If the "FN" and "ORG" properties have the exact same value (typically because they are set on the same element, e.g. class="fn org"), then the hCard represents contact information for a company or organization and should be treated as such. In this case the author MUST also NOT set the "N" property, or set it (and any sub-properties) explicitly to the empty string "". Thus parsers should handle the missing "N" property in this case by implying empty values for all the "N" sub-properties.

=== Implied "n" Optimization ===

Although vCard requires that the "N" property be present, the authors of the vCard specification (RFC 2426) themselves do not include "N" properties in their vCards near the end of the spec (p.38). This apparent contradiction can be resolved by simply allowing the "FN" property to imply "N" property values in typical cases provided in the spec. We do so explicitly in hCard.

If "FN" and "ORG" are not the same (see previous section), and the value of the "FN" property is exactly two words (separated by whitespace), and there is no explicit "N" property, then the "N" property is inferred from the "FN" property. For "FN"s with either one word see below, and for three or more, the author MUST explicitly markup the "N", except for the organization contact info case, [http://microformats.org/wiki/hcard#Organization_Contact_Info see above] for that.

# The content of "FN" is broken into two "words" separated by whitespace.
# The ''first'' word of the "FN" is interpreted as the "given-name" for the "N" property.
# The ''second/last'' word of the "FN" is interpreted as the "family-name" for the "N" property.
# Exception: If the first word ends in a "," comma OR if the second word is a single character (optionally followed by a period "."), then the first word (minus the comma at the end if any) is interpreted as the "family-name" and the second word is interpreted as the "given-name".

This allows simplification in the typical case of people stating:
* given-name (space) family-name
* family-name (comma) given-name
* family-name (comma) given-name-first-initial
* family-name (space) given-name-first-initial (optional period)

=== Implied "nickname" Optimization ===

Due to the prevalence of the use of nicknames/handles/usernames on the Web in actual content published on the Web (e.g. authors of [[hReview|reviews]]), hCard also has an implied "nickname" optimization to handle this.

Similar to the implied "n" optimization, if "FN" and "ORG" are not the same, and the value of the "FN" property is exactly one word, and there is no explicit "N" property, then:

# The content of the "FN" is treated as a "nickname" property value.
# Parsers should handle the missing "N" property by implying empty values for all the "N" sub-properties.

Note: the hCard may have additional explicit "nickname" property values in addition to the implied nickname.

=== Implied "organization-name" Optimization ===

The "ORG" property has two subproperties, organization-name and organization-unit. Very often authors only publish the organization-name. Thus if an "ORG" property has no "organization-name" inside it, then its entire contents MUST be treated as the "organization-name".

=== Tags as Categories ===

Categories in hCard can optionally be represented by tags with [[rel-tag]]. When a category property is a rel-tag, the tag (as defined by rel-tag) is used for that category.

=== Root Class Name ===
The root class name for an hCard is "vcard".

=== Property List ===
This is the list of properties (and subproperties, in parentheses, like this) in hCard, taken from vCard:

* fn, n (family-name, given-name, additional-name, honorific-prefix, honorific-suffix), nickname, sort-string
* url, email (type, value), tel (type, value)
* adr (post-office-box, extended-address, street-address, locality, region, postal-code, country-name, type, value), label
* geo (latitude, longitude), tz
* photo, logo, sound, bday
* title, role, org (organization-name, organization-unit)
* category, note
* class, key, mailer, uid, rev

=== Property Notes ===
* tel - Authors MAY want to follow the E.123 standard for writing values of telephone numbers.

==== type subproperty values ====

The 'type' subproperty in particular takes different values depending on which property it is a subproperty of. These 'type' subproperty values are case-INSENSITIVE, meaning "Home" is the same as "home", as well as multivalued, e.g. a tel can be home and preferred:

vCard:
<pre><nowiki>
TEL;TYPE=HOME,PREF:+1.415.555.1212
</nowiki></pre>

hCard:
<pre><nowiki>
<span class="tel"><span class="type">Home</span> (<span class="type">pref</span>erred):
<span class="value">+1.415.555.1212</span>
</span>
</nowiki></pre>

This could be displayed as:

<div style="border: thin dashed black; width: 95%; padding: .5em 1em; ">
<span class="tel"><span class="type">Home</span> (<span class="type">pref</span>erred):
<span class="value">+1.415.555.1212</span>
</span>
</div>

The following lists are ''informative''. See RFC 2426 sections 3.2.1 ADR, 3.3.1 TEL, and 3.3.2 EMAIL respectively for normative type values. They are repeated here for convenience. Default type subproperty value(s) is(are) first in each list and indicated in ALL CAPS. types may be multivalued.

* adr type: INTL, POSTAL, PARCEL, WORK, dom, home, pref
* tel type: VOICE, home, msg, work, pref, fax, cell, video, pager, bbs, modem, [http://flickr.com/photos/tags/carcellphone/ car], isdn, pcs
* email type: INTERNET, x400, pref, "other IANA registered address types"

=== XMDP Profile ===

See [[hcard-profile]] for the [http://gmpg.org/xmdp XMDP] profile of hCard which contains the above complete list of properties, with references to their RFC 2426 definitions.

=== Parsing Details ===

See [[hcard-parsing|hCard parsing]].

== Examples ==

This section is informative.

=== Sample vCard ===

Here is a sample vCard:

<pre><nowiki>
BEGIN:VCARD
VERSION:3.0
N:Çelik;Tantek
FN:Tantek Çelik
URL:http://tantek.com/
ORG:Technorati
END:VCARD
</nowiki></pre>

and an equivalent in hCard with various elements optimized appropriately. See [[hcard-example1-steps| hCard Example 1]] for the derivation.

<pre><nowiki>
<div class="vcard">
<a class="url fn" href="http://tantek.com/">Tantek Çelik</a>
<div class="org">Technorati</div>
</div>
</nowiki></pre>

This hCard might be displayed as:
<div style="border: thin dashed black; width: 95%; padding: .5em 1em;">
[http://tantek.com/ Tantek Çelik]<br />
Technorati
</div>

Note: The version information is unnecessary in hCard markup directly since the version will be defined by the profile of hCard that is used/referred to in the 'profile' attribute of the <head> element.

=== More Examples ===
See [[hcard-examples|hCard examples]] for more examples, including all examples from vCard RFC 2426 converted into hCard.

== Examples in the wild ==
This section is '''informative'''. The number of hCard examples in the wild has expanded far beyond the capacity of being kept inline in this specification. They have been moved to a [[hcard-examples-in-wild|separate page]].

See [[hcard-examples-in-wild|hCard Examples in the wild]].

== Implementations ==
This section is '''informative'''. The number of hCard implementations has also expanded beyond the capacity of keeping them inline. They have been moved to a [[hcard-implementations|separate page]].

See [[hcard-implementations|hCard Implementations]].

== References ==
=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://www.ietf.org/rfc/rfc2426.txt vCard RFC2426]
* [http://www.itu.int/rec/T-REC-E.123-200102-I/en ITU recommendation E.123] format of telephone numbers (chargeable document)

=== Informative References ===
* Contributed from http://developers.technorati.com/wiki/hCard.
* [http://www.w3.org/2002/12/cal/rfc2426 HTML reformatted version of RFC2426]
* [http://w3.org/TR/REC-CSS1 CSS1]
* [http://tantek.com/log/2004/09.html#hcard hCard term introduced and defined on the Web, 20040930]
* [http://wiki.oreillynet.com/foocamp04/index.cgi?SimpleSemanticFormats FOO Camp 2004 Simple Semantic Formats presentation, 20040910]
* [http://www.w3.org/TR/xhtml11 XHTML 1.1]
* [http://en.wikipedia.org/wiki/E.123 Wikipedia summary of ITU-T Recommendation E.123] - for "TEL" values.
* [http://www.imc.org/pdi/ Internet Mail Consortium Personal Data Interchange vCard and vCalendar]

==== Specifications That Use hCard ====
* [[adr]]
* [[geo]]
* [[hcalendar|hCalendar]]
* [[hreview|hReview]]

==== Similar Work ====
* [http://www.intertwingly.net/wiki/pie/PaceBetterPersonElement Atom PaceBetterPersonElement]
* [http://www.jabber.org/jeps/jep-0054.html JEP-0054: vcard-temp]

== Further Reading ==
* [http://www.digital-web.com/articles/microformats_primer/ Digital Web Magazine: Microformats Primer] by Garrett Dimon has a good intro to hCard
* [http://24ways.org/advent/practical-microformats-with-hcard Practical Microformats with hCard] by Drew McLellan
* [http://www.naturalsearchblog.com/archives/2006/09/28/tips-for-local-search-engine-optimization-for-your-site/ Local Search Engine Optimization using Microformats] by Chris Silver Smith
* [http://thedredge.org/ Andrew D. Hume] has written a blog post on [http://usabletype.com/articles/2005/usable-microformats/ usable microformats] which discusses hCard
* [http://www.thefutureoftheweb.com/blog/2006/1/hcard Jesse Skinner's introduction to hCard]
* [http://blog.usweb.com/ Shaun Shull's] great post on [http://blog.usweb.com/archives/how-microformats-affect-search-engine-optimization-seo How Microformats Affect SEO], including his [[hcard|hCard]] as an example.
* [http://24ways.org/2006/styling-hcards-with-css 24 Ways: Styling hCards with CSS] A 24 Ways article - John Allsopp on styling hCard using CSS
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page] and the [http://technorati.com/tags/hcard hCard tag]
* [http://www.rfc-editor.org/rfc/rfc4770.txt RFC 4770 - Extensions for Instant Messaging]

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

hcard

2007-01-30T00:43:13Z

DerrickPallas: added link to rel-tag page

<h1>hCard</h1>

hCard is a simple, open, distributed format for representing people, companies, organizations, and places, using a 1:1 representation of the properties and values of the vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]) in [[semantic-xhtml|semantic XHTML]]. hCard is one of several open [[microformats|microformat]] standards suitable for embedding in (X)HTML, Atom, RSS, and arbitrary XML.

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

__TOC__

== Specification ==

=== Editor ===
[http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc.]

=== Authors ===
* [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc]
* [http://suda.co.uk/ Brian Suda]

=== Copyright ===
{{MicroFormatCopyrightStatement2004}}

=== Patents ===
{{MicroFormatPatentStatement}}

=== Inspiration and Acknowledgments ===
Thanks to: my good friend [http://vadim.com/ Vadim] who introduced me to vCard ''many'' years ago, and if I'd only paid more attention then, perhaps I could have helped a lot of people avoid wasting a lot of time reinventing various standards wheels.

== Introduction ==
The vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]), has been broadly interoperably implemented (e.g. Apple's "Address Book" application built into MacOSX).

In addition, many bloggers identify themselves by name and discuss their friends and family. With just a tad bit of structure, bloggers can discuss people in their blog(s) in such a way that spiders and other aggregators can retrieve this information, automatically convert them to vCards, and use them in any vCard application or service.

This specification introduces the '''hCard''' format, which uses a 1:1 representation of the properties and values of the aforementioned vCard standard, in semantic XHTML. Bloggers can both embed hCards directly in their web pages, and style them with CSS to make them appear as desired. In addition, hCard enables applications to retrieve information directly from web pages without having to reference a separate file.

Use the [http://microformats.org/code/hcard/creator hCard creator] and copy the HTML code it generates to your blog or website to publish your contact info.

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

== Format ==
=== In General ===
The vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]) forms the basis of hCard.

The basic format of hCard is to use vCard object/property names in lower-case for class names, and to map the nesting of vCard objects directly into nested XHTML elements.

=== More Semantic Equivalents ===
For some properties there are HTML elements which better match and convey their semantics. The following properties SHOULD be encoded with the following (X)HTML:
* <code>URL</code> in vCard becomes <code><a class="url" href="...">...</a></code> inside the element with <code>class="vcard"</code> in hCard.
* Similarly, <code>EMAIL</code> in vCard becomes <code><nowiki><a class="email" href="mailto:...">...</a></nowiki></code>
* <code>PHOTO</code> in vCard becomes <code><img class="photo" src="..." alt="Photo of ..." /></code> or <code><object class="photo" data="..." type="...">Photo of ...</object></code>
* <code>UID</code> in vCard simply becomes another semantic applied to a specific URL (or EMAIL) for an hCard.

=== Singular vs. Plural Properties ===
For properties which are singular (e.g. "N" and "FN"), the first descendant element with that class should take effect, any others being ignored.

For properties which can be plural (e.g. "TEL"), each class instance should create a instance of that property.

==== Singular properties ====

Singular properties: "FN", "N", "BDAY", "TZ", "GEO", "SORT-STRING", "UID", "CLASS".

All other properties are plural. This list has been derived by analyzing the semantics of the individual properties in vCard RFC2426 and determining logically that they MUST be singular per their semantics. See [[hcard-singular-properties]] for explanations.

==== Plural Properties Singularized ====

Since plural property names become their singular equivalents, even if the original plural property permitted only a single value with multiple components, those multiple components are represented each with their own singularly named property and the the property is effectively multivalued and subject to the above treatment of multivalued properties.

=== Human vs. Machine readable ===

If an <code><abbr></code> element is used for a property, then the '<code>title</code>' attribute of the <code><abbr></code> element is the value of the property, instead of the contents of the element, which instead provide a human presentable version of the value.

If an <code><a></code> element is used for one or more properties, it must be treated as follows:
# For the "PHOTO" property and any other property that takes a URL as its value, the <code>href="..."</code> attribute provides the property value.
# For other properties, the element's content is the value of the property.

If an <code><img></code> element is used for one or more properties, it must be treated as follows:
# For the "PHOTO" property and any other property that takes a URL as its value, the <code>src="..."</code> attribute provides the property value.
# For other properties, the <code><img></code> element's '<code>alt</code>' attribute is the value of the property.

If an <code><object></code> element is used for one or more properties, it must be treated as follows:
# For the "PHOTO" property and any other property that takes a URL as its value, the <code>data="..."</code> attribute provides the property value.
# For other properties, the element's content is the value of the property.

=== Value excerpting ===

Sometimes only part of an element which is the equivalent for a property should be used for the value of the property. This typically occurs when a property has a subtype, like TEL. For this purpose, the special class name "<code>value</code>" is introduced to excerpt out the subset of the element that is the value of the property. E.g. here is an hCard fragment for marking up a home phone number:<br />

vCard:
<pre><nowiki>
TEL;TYPE=HOME:+1.415.555.1212
</nowiki></pre>

hCard:
<pre><nowiki>
<span class="tel">
<span class="type">home</span>:
<span class="value">+1.415.555.1212</span>
</span>
</nowiki></pre>

This hCard fragment could be displayed as:

<div style="border: thin dashed black; width: 95%; padding: .5em 1em;">
<span class="tel">
<span class="type">home</span>:
<span class="value">+1.415.555.1212</span>
</span>
</div>

=== Property Exceptions ===

vCard has several properties which either do not make sense on, or are already implied within the context of a web page. This section explains what to (not) do with them.

# '''NAME''', '''PROFILE''', '''SOURCE''', '''PRODID''', '''VERSION''' properties as defined in Sections 2.1.2, 2.1.3, 2.1.4, 3.6.3, 3.6.9 of RFC 2426. Content publishers MUST NOT use these properties in their hCards, and as such, hCard consumers/parsers MUST IGNORE these properties if they are found within an hCard. Instead. hCard to vCard converters SHOULD use the title of the page where the hCard is found (e.g. the <code><title></code> element in (X)HTML documents) to construct the NAME property, MAY output a PROFILE value of "<code>VCARD</code>" per RFC 2426, SHOULD use the URL of the page where the hCard is found to construct the SOURCE property (e.g. perhaps as a parameter to a URL/service that converts hCards to vCards), for an output vCard stream (e.g. a .vcf file). Only services/applications that output actual vCards should write the PRODID property, with the product identifier for said service/application. Similarly only such services/applications should write the VERSION property, with the value "3.0" (without quotes) per RFC2426 Section 3.6.9.

=== Organization Contact Info ===

If the "FN" and "ORG" properties have the exact same value (typically because they are set on the same element, e.g. class="fn org"), then the hCard represents contact information for a company or organization and should be treated as such. In this case the author MUST also NOT set the "N" property, or set it (and any sub-properties) explicitly to the empty string "". Thus parsers should handle the missing "N" property in this case by implying empty values for all the "N" sub-properties.

=== Implied "n" Optimization ===

Although vCard requires that the "N" property be present, the authors of the vCard specification (RFC 2426) themselves do not include "N" properties in their vCards near the end of the spec (p.38). This apparent contradiction can be resolved by simply allowing the "FN" property to imply "N" property values in typical cases provided in the spec. We do so explicitly in hCard.

If "FN" and "ORG" are not the same (see previous section), and the value of the "FN" property is exactly two words (separated by whitespace), and there is no explicit "N" property, then the "N" property is inferred from the "FN" property. For "FN"s with either one word see below, and for three or more, the author MUST explicitly markup the "N", except for the organization contact info case, [http://microformats.org/wiki/hcard#Organization_Contact_Info see above] for that.

# The content of "FN" is broken into two "words" separated by whitespace.
# The ''first'' word of the "FN" is interpreted as the "given-name" for the "N" property.
# The ''second/last'' word of the "FN" is interpreted as the "family-name" for the "N" property.
# Exception: If the first word ends in a "," comma OR if the second word is a single character (optionally followed by a period "."), then the first word (minus the comma at the end if any) is interpreted as the "family-name" and the second word is interpreted as the "given-name".

This allows simplification in the typical case of people stating:
* given-name (space) family-name
* family-name (comma) given-name
* family-name (comma) given-name-first-initial
* family-name (space) given-name-first-initial (optional period)

=== Implied "nickname" Optimization ===

Due to the prevalence of the use of nicknames/handles/usernames on the Web in actual content published on the Web (e.g. authors of [[hReview|reviews]]), hCard also has an implied "nickname" optimization to handle this.

Similar to the implied "n" optimization, if "FN" and "ORG" are not the same, and the value of the "FN" property is exactly one word, and there is no explicit "N" property, then:

# The content of the "FN" is treated as a "nickname" property value.
# Parsers should handle the missing "N" property by implying empty values for all the "N" sub-properties.

Note: the hCard may have additional explicit "nickname" property values in addition to the implied nickname.

=== Implied "organization-name" Optimization ===

The "ORG" property has two subproperties, organization-name and organization-unit. Very often authors only publish the organization-name. Thus if an "ORG" property has no "organization-name" inside it, then its entire contents MUST be treated as the "organization-name".

=== Tags as Categories ===

Categories in hCard can optionally be represented by tags with [rel-tag]. When a category property is a rel-tag, the tag (as defined by rel-tag) is used for that category.

=== Root Class Name ===
The root class name for an hCard is "vcard".

=== Property List ===
This is the list of properties (and subproperties, in parentheses, like this) in hCard, taken from vCard:

* fn, n (family-name, given-name, additional-name, honorific-prefix, honorific-suffix), nickname, sort-string
* url, email (type, value), tel (type, value)
* adr (post-office-box, extended-address, street-address, locality, region, postal-code, country-name, type, value), label
* geo (latitude, longitude), tz
* photo, logo, sound, bday
* title, role, org (organization-name, organization-unit)
* category, note
* class, key, mailer, uid, rev

=== Property Notes ===
* tel - Authors MAY want to follow the E.123 standard for writing values of telephone numbers.

==== type subproperty values ====

The 'type' subproperty in particular takes different values depending on which property it is a subproperty of. These 'type' subproperty values are case-INSENSITIVE, meaning "Home" is the same as "home", as well as multivalued, e.g. a tel can be home and preferred:

vCard:
<pre><nowiki>
TEL;TYPE=HOME,PREF:+1.415.555.1212
</nowiki></pre>

hCard:
<pre><nowiki>
<span class="tel"><span class="type">Home</span> (<span class="type">pref</span>erred):
<span class="value">+1.415.555.1212</span>
</span>
</nowiki></pre>

This could be displayed as:

<div style="border: thin dashed black; width: 95%; padding: .5em 1em; ">
<span class="tel"><span class="type">Home</span> (<span class="type">pref</span>erred):
<span class="value">+1.415.555.1212</span>
</span>
</div>

The following lists are ''informative''. See RFC 2426 sections 3.2.1 ADR, 3.3.1 TEL, and 3.3.2 EMAIL respectively for normative type values. They are repeated here for convenience. Default type subproperty value(s) is(are) first in each list and indicated in ALL CAPS. types may be multivalued.

* adr type: INTL, POSTAL, PARCEL, WORK, dom, home, pref
* tel type: VOICE, home, msg, work, pref, fax, cell, video, pager, bbs, modem, [http://flickr.com/photos/tags/carcellphone/ car], isdn, pcs
* email type: INTERNET, x400, pref, "other IANA registered address types"

=== XMDP Profile ===

See [[hcard-profile]] for the [http://gmpg.org/xmdp XMDP] profile of hCard which contains the above complete list of properties, with references to their RFC 2426 definitions.

=== Parsing Details ===

See [[hcard-parsing|hCard parsing]].

== Examples ==

This section is informative.

=== Sample vCard ===

Here is a sample vCard:

<pre><nowiki>
BEGIN:VCARD
VERSION:3.0
N:Çelik;Tantek
FN:Tantek Çelik
URL:http://tantek.com/
ORG:Technorati
END:VCARD
</nowiki></pre>

and an equivalent in hCard with various elements optimized appropriately. See [[hcard-example1-steps| hCard Example 1]] for the derivation.

<pre><nowiki>
<div class="vcard">
<a class="url fn" href="http://tantek.com/">Tantek Çelik</a>
<div class="org">Technorati</div>
</div>
</nowiki></pre>

This hCard might be displayed as:
<div style="border: thin dashed black; width: 95%; padding: .5em 1em;">
[http://tantek.com/ Tantek Çelik]<br />
Technorati
</div>

Note: The version information is unnecessary in hCard markup directly since the version will be defined by the profile of hCard that is used/referred to in the 'profile' attribute of the <head> element.

=== More Examples ===
See [[hcard-examples|hCard examples]] for more examples, including all examples from vCard RFC 2426 converted into hCard.

== Examples in the wild ==
This section is '''informative'''. The number of hCard examples in the wild has expanded far beyond the capacity of being kept inline in this specification. They have been moved to a [[hcard-examples-in-wild|separate page]].

See [[hcard-examples-in-wild|hCard Examples in the wild]].

== Implementations ==
This section is '''informative'''. The number of hCard implementations has also expanded beyond the capacity of keeping them inline. They have been moved to a [[hcard-implementations|separate page]].

See [[hcard-implementations|hCard Implementations]].

== References ==
=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://www.ietf.org/rfc/rfc2426.txt vCard RFC2426]
* [http://www.itu.int/rec/T-REC-E.123-200102-I/en ITU recommendation E.123] format of telephone numbers (chargeable document)

=== Informative References ===
* Contributed from http://developers.technorati.com/wiki/hCard.
* [http://www.w3.org/2002/12/cal/rfc2426 HTML reformatted version of RFC2426]
* [http://w3.org/TR/REC-CSS1 CSS1]
* [http://tantek.com/log/2004/09.html#hcard hCard term introduced and defined on the Web, 20040930]
* [http://wiki.oreillynet.com/foocamp04/index.cgi?SimpleSemanticFormats FOO Camp 2004 Simple Semantic Formats presentation, 20040910]
* [http://www.w3.org/TR/xhtml11 XHTML 1.1]
* [http://en.wikipedia.org/wiki/E.123 Wikipedia summary of ITU-T Recommendation E.123] - for "TEL" values.
* [http://www.imc.org/pdi/ Internet Mail Consortium Personal Data Interchange vCard and vCalendar]

==== Specifications That Use hCard ====
* [[adr]]
* [[geo]]
* [[hcalendar|hCalendar]]
* [[hreview|hReview]]

==== Similar Work ====
* [http://www.intertwingly.net/wiki/pie/PaceBetterPersonElement Atom PaceBetterPersonElement]
* [http://www.jabber.org/jeps/jep-0054.html JEP-0054: vcard-temp]

== Further Reading ==
* [http://www.digital-web.com/articles/microformats_primer/ Digital Web Magazine: Microformats Primer] by Garrett Dimon has a good intro to hCard
* [http://24ways.org/advent/practical-microformats-with-hcard Practical Microformats with hCard] by Drew McLellan
* [http://www.naturalsearchblog.com/archives/2006/09/28/tips-for-local-search-engine-optimization-for-your-site/ Local Search Engine Optimization using Microformats] by Chris Silver Smith
* [http://thedredge.org/ Andrew D. Hume] has written a blog post on [http://usabletype.com/articles/2005/usable-microformats/ usable microformats] which discusses hCard
* [http://www.thefutureoftheweb.com/blog/2006/1/hcard Jesse Skinner's introduction to hCard]
* [http://blog.usweb.com/ Shaun Shull's] great post on [http://blog.usweb.com/archives/how-microformats-affect-search-engine-optimization-seo How Microformats Affect SEO], including his [[hcard|hCard]] as an example.
* [http://24ways.org/2006/styling-hcards-with-css 24 Ways: Styling hCards with CSS] A 24 Ways article - John Allsopp on styling hCard using CSS
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page] and the [http://technorati.com/tags/hcard hCard tag]
* [http://www.rfc-editor.org/rfc/rfc4770.txt RFC 4770 - Extensions for Instant Messaging]

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

User:DerrickPallas

2007-01-29T07:13:50Z

DerrickPallas: /* Derrick Pallas */

== Derrick Pallas ==

=== About me ===

I am a Software Engineer for [[http://www.alexa.com Alexa Internet]], a subsidiary of [[http://www.amazon.com Amazon]]. (Anything I say on this website is on my own behalf and is not the opinion or property of my company, nor should it be construed to represent such.)

I have an MS in CS from [[http://www.ucdavis.edu UCD]] where I [[http://wwwcsif.cs.ucdavis.edu/~pallas worked]] in the [[http://morpheus.cs.ucdavis.edu/ Center for Software Systems Reasearch]]. These days I just do cool tricks with Ruby and C++, advocating cool things like [[http://www.fastcgi.com FastCGI]] and [[http://microformats.org microformats]]. You probably saw me at [[http://barcamp.org/ BarCamp]] last year or the birthday party for microformats.

Additionally, I write for [[http://www.thedailywtf.com The Daily WTF]]. You can find out more about me at [[http://derrick.pallas.us my own website]].

=== re: microformats ===

What I'm working on:

* working on examples for a software dependency / generic directed acyclic graph microformat
* telling everyone I know about how to embed an hCard in the web page they've already got

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

User:DerrickPallas

2007-01-29T05:26:45Z

DerrickPallas: initial edit

mailing-lists-proposals

2007-01-27T20:22:18Z

DerrickPallas: /* Change nothing */

=Mailing Lists Proposals=

There is a proposal for creating a new [[mailing-lists|mailing list]] for discussing the research and creation of new microformats so that those discussions do not overwhelm microformats-discuss.

Some candidates for names with the thinking behind them. Feel free to add your name and opinion (+/- 1 or 0).

==microformats-new==
Focusing on discussing "new" microformats
* +1 Tantek - this name has the advantage of attracting the newbie that wants to do a "new" microformat.
* +1 ScottReynen
* -1 Lachlan Hunt
* +1 Joe Andrieu
* -1 Andy Mabbett
* +1 Bob Jonkman
* +1 Ben Ward
* +1 Ben O'Neill
* +1 Robert Bachmann
* +1 Colin Barrett - "new" is a shiny word, and will hopefully folks interested in shiny things off uf-discuss.
* +1 Spike

==microformats-research==
Focusing on the essential, and often overlooked by first-time proposers "research" phase(s) in the process
* -1 Tantek - agreed with Bob Jonkman's comment, research is only part of the process.
* +1 ScottReynen
* +1 cgriego
* +1 Phae
* +1 JustinThorp
* -1 Andy Mabbett
* -1 Joe Andrieu
* -1 Bob Jonkman (research is part of process, best documented on the Wiki)
* -1 Ben Ward (strikes me as dilution too far of µf-discuss and µf-new)
* 0 Lachlan Hunt

==microformats-process==
That's really what we're talking about with research of new microformats, isn't it?
* +1 ScottReynen
* +1 Lachlan Hunt
* +1 [[User:Singpolyma|singpolyma]]
* -1 Andy Mabbett
* -1 Joe Andrieu
* -1 cgriego (reminds me of parsing--processing--more so than even microformats-dev)
* -1 Bob Jonkman (Is this the process of creating a new microformat, or the some other process? Document it on the Wiki, I say)
* +0 Tantek - I think this is too vague and won't automatically attract the newbie that wants to propose new microformats. Still the semantic is roughly correct.
* -1 [[User:WizardIsHungry|Jon Williams]] 11:10, 26 Jan 2007 (PST)
* -1 Colin Barrett - A bit ambiguous, might be mistaken for a meta discuss list.

==microformats-propose==
* -1 Tantek - It misses the point of the process, and implies that there is a desire for microformats proposals - there isn't.
* -1 ScottReynen
* 0 Andy Mabbett
* -1 Bob Jonkman
* -1 Ben Ward

==microformats-suggest==
Similar to propose but milder ;)
* +1 ChrisMessina
* -1 Tantek - same comment as on microformats-propose
* -1 ScottReynen
* -1 Phae (I feel this is just -propose in disguise)
* -1 BenWest
* -1 Andy Mabbett
* -1 Bob Jonkman
* -1 Ben Ward (If µf-new or similar is created for active spec'ing and format development, uf-discuss would comfortably accomodate this as part of the course of discussion)

==microformats-work==
For working on microformats, new and old.
* +1 BenWest: I thought we are interested in a list that provides a venue for iterating through the process, and revising and refining microformats in general. discuss is for newbies, and dev is for implementing them.
* -1 Tantek: work could mean anything though, not just work on creating new microformats.

==microformats-wg==
WG is an abbreviation of Working Group
* +1 Lachlan Hunt
* -1 Tantek: "working group" means something quite specific in W3C terminology. Very little of that applies to the set of people that work on creating new microformats.
* -1 BenWard: As Tantek says, ‘working group’ means something that Microformats doesn't have and doesn't want. What's more, to an observer ‘Working Group’ implies exclusivity which isn't what µf development is about.

==microformats-tf==
TF is an abbreviation of Task Force
* 0 Lachlan Hunt
* -1 Tantek: Though less overloaded with specific meaning than "working group", "task force" still means something quite specific in W3C terminology as well as other standards organizations. Very little of that applies to the set of people that work on creating new microformats.
* -1 BenWard

==microformats-meta==
General-purpose "meta-discussion" about microformats.org process and policies
* +1 Ernest Prabhakar: captures all the things normal people don't want on uf-discuss. :-)
* -1 Tantek - this is outside the scope of the proposal for a list for new microformats.

==Change nothing==
e.g fix uf-dev (we have done that), do nothing else (for now)
* +1 RyanKing
* +1 Tim White
* +1 Andy Mabbett
* 0 Bob Jonkman
* 0 Ben Ward
* -1 BenWest
* -1 Tantek - we have opened uf-dev and I still strongly believe we need a new list for the discussion of new microformats, separate from microformats-discuss in order to avoid overwhelming new folks with details and minutiae of new and in development formats.
* -1 Robert Bachmann
* -1 Ernest Prabhakar: there's way too much "useful" noise that confuses new entrants (and me, sometimes)
* 0 Colin Barrett - I'm not convinced that doing nothing isn't an option, but momentum seems to be in the other direction, so I've registered my vote for uf-new
* -1 DerrickPallas It confused the heck out of me.

= General Comments=

==Andy Mabbett==
Why not create a new mailing list for each proposal, once it's reached a certain stage? Then , if the uF is created, or the proposal abandoned, the specific list would be closed, and the archive retained as a link from the "brainstorming" page, as a permanent, and discrete record of discussion on that topic.

Alternatively, the list could be retained for discussion of the implementation and development of that specific uF.

For example, several academic and professional taxonomists have told me in e-mail that they would be interested in the [[species]] proposal, (and one astronomer, likewise, for [[mars]]/ [[luna]]), but do not have the time to follow a general mailing list; indeed, a couple asked me specifically if I would set up a separate mailing list for the subject.

[[User:AndyMabbett|Andy Mabbett]] 04:44, 24 Oct 2006 (PDT)

*The biggest challenge with creating new microformats (especially for new comers) is with following the process. The same discussions are often had over and over for different formats, thus it makes sense for people developing different formats to at least see the discussions around the creation of other formats and hopefully learn from them and avoid repeating the same questions or mistakes. [[User:Tantek|Tantek]] 00:10, 25 Oct 2006 (PDT)
**Someone new to the mailing list won't see past discussion there anyway; they need to be referred to the archive. If busy people, whose expertise we need, choose not to see discussion of other, unrelated microformats, we can't force it on them - we either provide a more specifically-focussed forum, or they don't participate at all - which is best? [[User:AndyMabbett|Andy Mabbett]] 03:06, 25 Oct 2006 (PDT)
***Getting the *process/format/interop/reuse* aspects correct are more important than specific expertise in any vertical field. The point of the process is that we don't actually need the expertise of field experts - anyone can do research on the open web and find examples. In some ways, field experts may be a negative on the process in that they usually want to represent 100% of the possibilities for a format, rather than 80/20 of the *real world* use cases that are already in use on the Web. [[User:Tantek|Tantek]] 10:53, 26 Jan 2007 (PST)

*In addition, part of the [[microformats]] methodology/philosophy/principles is simplicity and minimalism - the fewer the better. This applies not only to microformats, microformats properties, and microformats values, but to microformats mailing lists as well. Thus since the beginning we have only created lists when absolutely necessary (i.e. when the traffic/topics crowded out one of the other lists), and then only one at a time. [[User:Tantek|Tantek]] 00:10, 25 Oct 2006 (PDT)
**I can see what has happened previously; I'm suggesting - with a stated justification - a variation on that. There is more than one opinion, as to what is "necessary". [[User:AndyMabbett|Andy Mabbett]] 03:06, 25 Oct 2006 (PDT)
***You don't know that more than one list will be necessary until you create the first one and use it. Let's base our actions here on real world experience with the creation of *a* new list, not the theoretical expectations of needing more than one list. In addition, the previous discussion shows why it would be a *negative* to have more than one list that created microformats.[[User:Tantek|Tantek]] 10:53, 26 Jan 2007 (PST)

irc-people

2007-01-27T20:13:15Z

DerrickPallas: added myself

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

* [[User:Adam Craven|AdamCraven]] (+0000)
* [[User:Amette|amette]] (+1000)
* [[User:Ashley|Ashley]] (+1000)
* [[User:B.K._DeLong|bkdelong]] (-0500/-0400)
* [[User:Tyler Roehmholdt|Baristo]] (-0800/-0700)
* [[User:Ben Ward|BenWard]] (+0000)
* [[User:BenjaminCarlyle|BenjaminCarlyle]] (+1000)
* [[User:HenriBergius|bergie]] (+0200/+0300)
* [[User:BenWest|bewest]] (-0800/-0700)
* [[User:BluesMoon|bluesmoon]] (+0530)
* [[User:Bob Jonkman|BobJonkman]] (-0500/-0400)
* [[User:Boneill|boneill]] (+0000)
* [[User:Brian|briansuda]] (+0000)
* [[User:Cgriego|cgriego]] (-0600/-0500)
* [[User:CharlesRoper|charles_r]] (0000/+0100)
* [[User:Charlvn|Charl]] (+0200/+0200)
* [[User:ChristopherStJohn|cks]] (-0600/-0500)
* [[User:Cloud|Cloud]] (+0000)
* [[User:Colin_Barrett|cbarrett]] (-1000)
* [[User:ColinDDevroe|cdevroe]] (-0500/-0600)
* [[User:Csarven|csarven]] (-0500/-0400)
* [[User:DerrickPallas|DerrickPallas]] (-0800/-0700)
* [[User:Dan Kubb|dkubb]] (-0800/-0700)
* [[User:DanC|DanC]] (-0600/-0500)
* [[User:DannyAyers|danja]] (+0100/+0200)
* [[User:Dave Cardwell|davecardwell]] (+0000)
* [[User:DeanEro|deanero]] (-0800/-0700)
* [[User:DiegoBudny|DiegoBudny]]
* [[User:DimitriGlazkov|dglazkov]] (-0600/-0500)
* [[User:DrewMcLellan|drewinthehead]] (+0000/+0100)
* [[User:DrewBell|droob]] (-0600/-0500)
* [[User:DimitriosZachariadis|dzach]] (+0200/+0300)
* [[User:Ed Summers|edsu]] (-0500/-0400)
* [[User:Enric|enric]] (-0800/-0700)
* [[User:Enric|Enric]] (-0800/-0700)
* [[User:Evan|evanpro]] (-0500)
* [[User:ChrisMessina|factoryjoe]] (-0800/-0700)
* [[User:Fil|Fil]] (+0200)
* [[User:MarkNormanFrancis|Mark Norman Francis]] (+0000/+0100)
* [[User:MarkoMrdjenovic|friedcell]] (+0100/+0200)
* [[User:Grantbow|Grantbow]] (-0800/-0700)
* [[User:Hlb|hlb]] (+0800-0700)
* [[User:IanHickson|Hixie]] (-0800/-0700)
* [[User:EdwardOConnor|hober]] (-0800/-0700)
* [[User:IwaiMasaharu|iwaim]] (+0900)
* [[User:Izo|IZO]]
* [[User:JamieKnight|jammie_]] (+1000/0000)
* [[User:WizardIsHungry|jcw9]] (-0500/-0400)
* [[User:Adactio|Jeremy Keith]] (+0000)
* [[User:JasonK|jkridner]] (-0600/-0500)
* [[User:JoeGregorio|jcgregorio]]
* [[User:Jonathan_Arkell|jonnay]] (-0700/0600)
* [[User:JulianStahnke|Julian Stahnke]] (+0000)
* [[User:Kapowaz|kapowaz]] (+0000/+0100)
* [[User:Keri Henare|kerihenare]] (+1200)
* [http://epeus.blogspot.com/ KevinMarks] (-0800/-0700)
* [[User:RyanKing|kingryan]] (-0800/-0700)
** [http://theryanking.com/blog/archives/2006/04/19/office-hours/ Office hours]: Wednesday, 21:00 UTC
* [[User:Lachlan Hunt|Lachy]] (+1000/+1100)
* [[User:Mark Mansour|Mark Mansour]] (+1100)
* [[User:CiaranMc|McNulty]] (+0000/+0100)
* [[mfbot]] - 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.
* [[User:MikeKaply|mkaply]] (-0600/-0500)
* [[User:SteveIvy|monkinetic/redmonk]] (-0700)
* [[User:neuro|neuro`]]
* [[User:NTollervey|ntoll]] (+0000/+0100)
* [[User:Phae|Phae]] (+0000/+0100)
* [[User:PriitLaes|plaes]] (+0200/+0300)
* [[User:ChrisCasciano|pnhChris]] (-0500/-0400)
* [[User:DavidOsolkowski|qid]] (-0500)
* [[User:Remi|Remi]] (-0500/-0400)
* [[User:RobertBachmann|RobertBachmann]] (+0100/+0200)
** Office hours: <del>Wednesday, 18:00-20:00 UTC</del> (Currently no office hours)
* [[User:Ronnos|Ron Kok]] (+0000)
* [[User:Dana Benson|Snowden]] (-0800/-0700)
* [[User:Smackman|Steve Farrell]] (-0800/-0700)
* [[User:Steve Ganz|SteveGanz]] (-0800/-0700)
* [[User:SuperPhly|SuperPhly]] (-600/-500)
* [[User:Tantek|Tantek]] (-0800/-0700)
* [[User:Trovster|trovster]] (-0800/-0700)
* [[User:Vant|vant]] (+0900)
* [[User:KrissWatt|VoodooChild]] (+0000/+0100)
* [[User:JacksonWilkinson|whafro]] (-0500/-0400)
* [[User:Richard Conyard|WhiskeyM]] (+0000)
* [[User:Veeliam|William Lawrence]] (-0800/-0700)
* [[User:Ianloic|yakk]] (-0800/-0700)

to-do

2007-01-27T18:44:41Z

DerrickPallas: /* Derrick Pallas */

<h1>To Do</h1>

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

__TOC__

== Lazyweb ==

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

=== for all microformats ===
* quick and easy "how to" pages for each microformat. [[use]] is a good overall start.
* brief summary statements for each microformat that explain why it matters, what does it accomplish for the publisher.
* write up [http://microformats.org/discuss/ mailing-list] questions and answers in the appropriate [[faq]] pages.
* validators. See the hReview section below as there has been a request for an hReview validator in particular. See [http://norman.walsh.name/2006/04/13/validatingMicroformats Norman Walsh's blog post "Validating microformats"] for some valuable analysis and validation pseudo-code (prose description), which are useful steps towards building microformat validators.
* Create a microformat (based on hCalendar?) for marking up the opening hours of stores and restaurants. Some people seem to believe hCalenders repeating event support isn't good enough for this and needs to be amended first.
* Add [http://verselogic.net/projects/wordpress/wordpress-openid-plugin/ OpenID] to Microformats Blog.

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

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

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

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

=== Yahoo Open Source Library Patches ===

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

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

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

=== Adding Microformats to Existing Pages ===

* See [[advocacy#Adding_Microformats_to_Existing_Sites|advocacy: Adding microformats to existing sites]].

===Geotagging on Wikipedia===
Somebody familiar with the "geo" microformat might want to add details, and a link to the relevant page on this Wiki, to the [http://en.wikipedia.org/wiki/Geotagging Wikipedia page on Geotagging]. [[User:AndyMabbett|Andy Mabbett]]

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

== Tantek ==

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

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

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

=== help publishers ===
* (: [[advocacy]] - add pages/sites that could use microformats, update them with sample markup, find contacts for those pages to get them updated, and send requests to update their sites with microformats including sample markup.

==== *-authoring microformats wiki pages ====
* Add some tips to [[hcard-authoring]]
** a tutorial on creating an hCard for your site
** specific instructions for common blogging platforms
** instructions for more properties (match at least the set that is in the [http://microformats.org/code/hcard/creator hCard creator])
* Create [[hreview-authoring]] - a tutorial on how to blog reviews so that they'll be aggregated.

* *-authoring for all microformats: [[hcalendar-authoring]], [[hreview-authoring]], [[xfolk-authoring]], [[hatom-authoring]]

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

=== help implementers ===
* wordpress improvements
** WP admin for new profiles
*** should simply read blog URL
*** look for hcards and parse them
* [http://gmpg.org/xfn/creator XFN Creator] localizations
** Get someone to verify the [http://gmpg.org/xfn/creator-ru XFN Creator Russian localization].
** Add it to the [http://gmpg.org/xfn/tools XFN Tools] page.
** Add rel="alternate" href="creator-ru" <link>s to the other XFN Creators.
* Conference Schedule Creator
** We need to ASAP build a simple conference schedule creator (and editor?) that builds upon the hCalendar creator. We should make it *trivial* for conference organizers to build/edit/publish an [[hcalendar|hCalendar]] schedule for their conference, including auto-generated "Subscribe..." link which produces the proper "webcal:..." link with X2V. Note: see the "axis" and "header" attributes in HTML4, specifically in the section on Tables. (Done. Feedback wanted. [http://dmitry.baranovskiy.com/work/csc/ Conference Schedule Creator])

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

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

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

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

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

* [[hcard-implementations]] - organize by same subsections as [[hcalendar-implementations]].

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

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

=== iterate on current microformats ===
==== [[hcard|hCard]] ====
* [[hcard-examples]]
** add examples of [[hcard|hCard]]s with work telephone, mailing address etc.
** add examples of marking up an organization vs. a person, then link to it from [http://microformats.org/wiki/hcard#Organization_Contact_Info hCard spec section on Organization Contact Info].
** add example of organization-name and organization-unit usage.
* [[hcard-examples-in-wild]]
** Group examples in the wild according to:
*** Individuals - one card per person, perhaps sort alphabetically
*** Organizations - one card per organization, alphabetical again
*** Institutions (which list more than one person), with a count estimating the # of hCards, e.g. 40k for Avon. Also indicate complexity of information supplied, eg. just name+number vs. complete details
*** Online Profiles (which host profiles for more than one person) with a count estimating the # of hCards, e.g. 3.5m for Flickr.com
*** Online Venues (which provide listings for businesses or organizations) with a count estimating the # of venues, e.g. ~10k for Upcoming.org
*** Speakers Listings (lists of speakers on conference sites) with a count estimating the # of speakers, e.g. ~300 for SXSW 2006.
** help dglazkov markup: http://glazkov.com/blog/archive/2003/12/17/147.aspx
* [[hcard-brainstorming]]
** need property for gender (see [[hcard-faq#How_is_gender_represented|proposal in hCard FAQ]] and discussion in [[hcard-issues]]) - use tags for now, add to hCard creator
** solve [[hcard-brainstorming#Auto-Discovery|autodiscovery]] of more canonical/thorough hCard

==== [[hcalendar|hCalendar]] ====
* re-add a list of properties per the [[hcard#Property_List|hCard property list]].
* formalize [http://microformats.org/wiki/hcalendar- brainstorming#Tabular_event_calendars]
* flesh out [[hcalendar-examples]] and do a once over on markup/presentation of what RFC2445 examples would look like
* need spec details and then [[hcalendar-examples]] of multi-instance [[hcalendar|hCalendar]] events
* need spec details and then [[hcalendar-examples]] of repeating events
* add explicit explanation and examples for LOCATION [[hcard|hCards]] and ATTENDEE [[hcard|hCards]], perhaps on a separate [[hcalendar-examples]] page.
* need to resolve all outstanding [[hcalendar-issues]] to-do items.
* create [[hcalendar-profile]] and have folks verify it. note that it will likely need reconciliation with the [[hcard-profile]], especially since [[hcalendar|hCalendar]] normatively depends on [[hcard|hCard]]. Probably makes sense to have a combined profile which hCalendar would use.

==== [[hreview|hReview]] ====
* Write hReview 0.3 XMDP profile, and reconcile with [[hcalendar-profile]] and [[hcard-profile]]. Makes sense to have a combined profile of all three for hReview, since hReview normatively depends on hCard and hCalendar.

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

==== parsing ====
* *-parsing for all microformats: [[hcalendar-parsing]], [[hreview-parsing]], [[xfolk-parsing]], [[hatom-parsing]]

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

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

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

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

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

=== emerging microformats ===
* [[citation]]
* [[hlisting|hListing]]
* [[media-info]]
* [[licensing]]

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

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

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

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

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

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

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

== Dimitri Glazkov ==

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

== Chris Messina ==

=== General ===

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

=== Campaigns ===

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

=== Wishlist ===

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

== Robert Bachmann ==

=== hAtom2Atom ===

Some ideas for features which could be implemented :

(If you are interested in one of this features, add "<i>+1 Your Name</i>")

<ul>
<li>
Join all hfeed's inside a page (or a fragment thereof) into one feed using [http://greenbytes.de/tech/webdav/rfc4287.html#element.source atom:source] semantics.
</li>
<li>
Extraction of <code>atom:content</code>, <code>atom:summary</code> and <code>atom:title</code>:
* <code>atom:content</code> and <code>atom:summary</code> as HTML
* <code>atom:content</code> and <code>atom:summary</code> as plain-text
* <code>atom:title</code> as XHTML
* <code>atom:title</code> as HTML
</li>
<li>Support for other XSLT engines:
* MSXML
* .Net System.Xml
* Sablotron
* Oracle XSLT
* XT
* hAtom2Atom written using XSL 2.0?
** Do you think this would be useful? I have created a barebones version, doesn't yet take in all the parsing rules yet, but I'd be happy to share. Moving to XSL 2.0 does make things a bit cleaner and more efficient. - Matt Dertinger.
</li>
<li>Support for other output formats: (hAtom2<i>xyz</i>.xsl)
* RSS 2.0 (meanwhile use hAtom2Atom.xsl and [http://atom.geekhood.net/ atom2rss.xsl]) -- <i>+1 Matt Dertinger</i>
* RSS 1.0 (meanwhile use hAtom2Atom.xsl and [http://cvs.4suite.org/viewcvs/uogbuji/atom2rss.xslt atom2rss.xslt]) -- <i>+1 Matt Dertinger</i>
* AtomOWL (meanwhile use hAtom2Atom.xsl and [http://dannyayers.com/2005/11/22/atomowl-xslt-progress/ atom2rdfxml.xsl])-- <i>+1 Matt Dertinger</i>
* JSON?
** Does it make sense to consider a canonical representation of microformats (either case by case, or in general) in JSON? E.g. so that a JSON API that returned contact information could return an hCard-equivalent chunk of JSON. - Tantek.
</li>
</ul>

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

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

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

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

== Mark Rickerby ==

=== Current Tasks ===

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

=== Wishlist ===

* hmmm

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

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

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

== Dan Connolly ==

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

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

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

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

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

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

== Chris Casciano ==

[[User:ChrisCasciano|ChrisCasciano]]

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

== Drew McLellan ==

[[User:DrewMcLellan|DrewMcLellan]]

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

== Christophe Ducamp (french localization) ==

[[Christophe Ducamp]]
* translate red links on [[Main_Page-fr]]
* localize a [http://www.elanceur.org/microformats/index.html french version] of the official website
** ask authorization to the authors
** migration could be done on any collaborative CMS
** test a cocomment system (based on local-wiki)
** complete with original links
* find experts for peer-reviewing
* update [http://fr.wikipedia.org/wiki/Microformats French-wikipedia:Microformats] via cowriting [http://fr.wikipedia.org/wiki/Discuter:Microformats on discussion page] (directly originated from the english article) + french examples to be found + local resources.

== Frances Berriman ==

[[User:Phae|Frances Berriman]]

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

== Ben West (bewest) ==

[[User:BenWest|bewest]]
* fight spam
* help tend wiki

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

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

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

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

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

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

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

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

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

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

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

These pages would be located respectively at

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

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

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

== Matt Dertinger (Thewhoo) ==

[[User:Thewhoo]]

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

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

== Henri Bergius ==

[[User:HenriBergius|Henri Bergius]]

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

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

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

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

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

== New Person 1 ==

etc.

to-do

2007-01-27T18:29:18Z

DerrickPallas: /* Mark Lentczner */

what-are-microformats

2007-01-21T00:38:50Z

DerrickPallas:

__NOTOC__

:If this is your first visit, please see the [[introduction]] page.

= What are microformats? =

__TOC__

== Launch Definition ==

The current definition on the [http://microformats.org home page] says:

<blockquote style="font-size:larger;font-style:italic">Designed for humans first and machines second, microformats are a set of simple, open data formats built upon existing and widely adopted standards.</blockquote>

originally written by Dan Cederholm with help from Tantek Çelik for the launch of [http://microformats.org microformats.org] on June 20th, 2005.

== From The Mailing List ==

<blockquote style="font-size:larger;font-style:italic">Microformats are simple conventions for embedding semantics in HTML to enable decentralized development.</blockquote>

from someone on the microformats-discuss mailing list. Please link/cite if you know the origin of this.

== More Specifically From The Mailing List ==

More precisely, microformats can be
defined as:

<blockquote style="font-size:larger;font-style:italic">
<pre>
simple conventions
for embedding semantic markup

for a specific problem domain

in human-readable (X)HTML/XML documents, Atom/RSS feeds, and "plain" XML

that normalize existing content usage patterns
using brief, descriptive class names
often based on existing interoperable standards

to enable decentralized development

of resources, tools, and services
</pre>
</blockquote>

from someone(s) on the microformats-discuss mailing list. Please link/cite if you know the origin of this.

(I'm pretty sure Ernie kicked off this particular definition, and I think helped a little, but I don't remember the specifics. -Tantek)

== Chris Messina ==

<blockquote style="font-size:larger;font-style:italic">
Microformats are simple codes that you can use to identify specific kinds of data, like people or events, in your webpages.
</blockquote>

== Tantek Çelik ==

<blockquote style="font-size:larger;font-style:italic"><p>Microformats are the way to publish and share information on <strong>the web with higher fidelity</strong>.</p><p>For example, if a company wanted their <strong>contact information</strong> to be easily found and shared, they would publish it with [[hcard|hCard]]. Similarly if an organization is planning a series of events and wants more people to know about them and add them to their calendars, then they would publish their <strong>events listing</strong> with [[hcalendar|hCalendar]]. For advocacy groups, whenever they take a position on some political leader, some piece of legislation etc., if they wanted their <strong>evaluations/reviews/ratings</strong> of those people/laws to be more easily found and passed around, they would publish such opinions with [[hreview|hReview]]. For all of these, to make it easier, publishers can use [[implementations|tools and services that support microformats]].</p><p>The key here is that microformats are simple/easy enough that the any organizations own <strong>web authors/designers can easily add them</strong> in themselves. Adding microformats is easier than publishing an RSS feed for example. You don't have to be a programmer. Anyone with decent (X)HTML+CSS authoring/writing skills can use microformats. Pretty much anyone who is literate can be taught how to author HTML+CSS, and thus microformats makes use of very widely available skill sets.</p></blockquote>

From an IRC conversation 2006-06-06 which helped "knowprose" grok microformats. Update 2006-06-07: knowprose's blog post [http://www.knowprose.com/node/15844 Making Sense of Microformats: Have Data, Will Find It].

<blockquote style="font-size:larger;font-style:italic"><p>microformats are carefully designed (X)HTML class names that extend the semantics of (X)HTML and enable authors to publish higher semantic fidelity content such as people, events, reviews, etc.</p></blockquote>

From an IRC conversation 2006-07-28 with tcaspers on irc.freenode.net/#wasp.

== Drew McLellan ==

<blockquote style="font-size:larger;font-style:italic">Microformats are a way of attaching extra meaning to the information published on a web page. This extra semantic richness works alongside the information already presented, and can be used for the benefit of people and computers. This is mostly done through adding special pre-defined names to the class attribute of existing XHTML markup.</blockquote>

from an IRC conversation

== Joe Andrieu ==

<blockquote style="font-size:larger;font-style:italic"><p>Designed for humans first and machines second, microformats are a set of simple, open data formats built upon (X)HTML and CSS.</p>

<p>The current blurb leaves me wondering "But <strong>what</strong> are they?". I remember this feeling from the first time reading through the microformats wiki. The [http://microformats.org/about/ about page] goes on from the opening blurb to state what microformats are, what microformats are not, and the microformats principles.</p>

<p>All great descriptions... Yet still leaving me wondering the most basic level of concreteness: <strong>What are they?</strong> Javascript libraries? An XML vocabulary? PHP tools? The most specific language is "data format standard." Is that like HTML? Is it just an RFC for the next web thing? </p>

<p>Of course, I know the answers to all of these things, now. But it took me a while to get there.</p>

<p>This suggestion attempts to concretize the "existing and widely adopted standards". It's a bit shorter and to my eye a bit clearer and more powerful.</p>
</blockquote>

== From The Wiki ==

There are unsettling faults with the definitions and explanations given. The writing seems to be a rallying cry for proponents - clever wording, impressive noun-phrases. But it explains nothing to those unfamiliar with microformats. Imagine giving this sort of explanation off-paper: "A Microformat? What do you mean?" one asks. "Well," the other replies, as he jumps onto the nearest table, his voice excited and booming, a crowd gathering around him:

<blockquote style="font-style:italic">
Designed for humans first and machines second, microformats are a set of simple, open data formats built upon existing and widely adopted standards. Instead of throwing away what works today, microformats intend to solve simpler problems first by adapting to current behaviors and usage patterns (e.g. XHTML, blogging). [...]
</blockquote>

Ah, I see now. So it's something for people to use. Something simple and intuitive, like a steering wheel. Something open, easily changed by anyone, like a wiki or linux. A data format, like rtf, xml, or pdf. It obeys unspecified standards, but is so much more! It's based on something that already works. It doesn't attempt to solve anything it doesn't need to. It dynamically changes to comply with how I'm behaving at the moment... Yes. Yes! This is what I need! My living text streaming-based DOM machine/user -interface will never be the same, now that I have Microformats! Er... right?

<blockquote style="font-size:larger;font-style:italic">
Microformats are conventions for marking up commonly-encountered data (such as links, contact information, and calendar events) in established languages such as HTML. By using standardized layouts, CSS classes, and attribute values, information becomes more accessible and useful to both humans and computers.
</blockquote>

I would appreciate if someone would copy this to the mailing list, since I don't wish to sign up, but would like this to be remedied. [[User:M|M]] 23:52, 23 Aug 2006 (PDT)

==Alok Jain==
<blockquote style="font-size:larger;font-style:italic">microformats are evolving frameworks for how to present commonly used data items. For e.g. hCard microformat provides framework to capture a person's details First, middle, last name,company, contact info etc.</blockquote>

In my view this is doing two things:
*a Bringing some amount of standardization to commonly used data sets, which can lead to several benefits towards data retreival
*a Bringing an implicit meta data structure which again can be used to fetch informaiton at more granular level. SO in above example one could fetch just the company name, even thought there is not meta data around company name

[http://www.iPrincipia.com Alok Jain]
== Dave Sanford ==

Chris asked me to contribute my 'definition,' although I refer to it as a distillation:

“Microformats are a way of identifying and labeling classes of commonly used data that make it easier for humans or computers to locate or distribute such information on websites.”

==Andy Mabbett==

Here's my re-write of the current opening blurb, from:

<blockquote style="font-size:larger">Designed for humans first and machines second, microformats are a set of simple, open data formats built upon existing and widely adopted standards.</blockquote>

to:

<blockquote style="font-size:larger;">Microformats are a way of adding simple markup to human-readable data items such as events, contact details or locations, on web pages, so that the information in them can be extracted by software and indexed, searched for, saved, cross-referenced or combined.</blockquote>

Which can be followed by:

<blockquote style="font-size:larger;">More technically, they are items of semantic markup, using just standard (X)HTML with a set of common class-names. They are open and available, freely, for anyone to use.</blockquote>

Principles:
*Start with "Microformats are"
*Mention web pages
*Say what purpose microformats serve
*Use plain language

Finally: don't use italics for whole paragraphs, it's harder for people (such as some with dyslexia or other cognitive disabilities) to read.

== Guillaume Lebleu ==

<blockquote style="font-size:larger;font-style:italic">Microformats are simple standardized annotations of content available on the Web that provide a practical solution today to more productive and decentralized Web-based information search and sharing. </blockquote>

<blockquote style="font-size:larger;font-style:italic">In other words, Microformats allow you today to copy/paste information from a Web page, for instance someone's contact information from their blog to your address book, instead of manually retyping it. Eventually, microformats will allow anyone to make the information they publish easily sharable and searchable (products, events, resume, etc.) without having to duplicate and maintain up-to-date their data in centralized databases.</blockquote>

== Richard Quick ==
This isn't a definition of microformats, it's more of an explanation of them...

<blockquote style="font-size:larger;">Every web page contains information. Most websites have a contact page, with a phone number, email address and possibly a street address. Others have reviews of products, books or CDs.</blockquote>

<blockquote style="font-size:larger;">Microformats are a way to label certain information, like contact details or reviews, so it can easily be extracted from your web page by a suitable computer program or web-based application.</blockquote>

<blockquote style="font-size:larger;">Although microformats exist to make it easier for computers to extract information from web pages, they’re designed to be easy to use by people. For example, many microformats simply involve adding certain class names to an HTML tag (others use rel attributes, for example).</blockquote>

<blockquote style="font-size:larger;">If a web page uses HTML on its own, it's very difficult (bordering on impossible in some cases) to write a computer program which can examine the web page, work out what kind of information is on the page, and extract that information.</blockquote>

<blockquote style="font-size:larger;">For example, look at the following address:

<pre>John Smith
1 Seaview Lane,
Mousehole,
Cornwall,
UK.</pre></blockquote>

<blockquote style="font-size:larger;">How can a computer program work out what kind of information the word "[http://en.wikipedia.org/wiki/Mousehole Mousehole]" is? Is it a town? Is it a country? Is it a hole where mice live?</blockquote>

<blockquote style="font-size:larger;">Obviously, it's going to be pretty difficult. However, using the '''[[hCard]]''' microformat, you can label each piece of information so that it's obvious to a computer what kind of information the word "Mousehole" is.

<pre><div class="vcard">
<span class="fn">John Smith</span>,
<div class="adr">
<div class="street-address">1 Seaview Lane</div>,
<span class="locality">Mousehole</span>,
<span class="region">Cornwall</span>,
<span class="country-name">UK</span>
</div>
</div></pre></blockquote>

<blockquote style="font-size:larger;">So is that all microformats are? A bunch of class names (and other similarly easy-to-use attributes)?</blockquote>

<blockquote style="font-size:larger;">Yes, that's basically all they are.</blockquote>

<blockquote style="font-size:larger;">They key is that everybody uses the same class names (and other attributes). In the example above, you can see that the div around word "Moushole", has "locality" as its class name. Of course, "city", "town" or "village" would all have been equally suitable class names to use, however by standardizing on one specific class name it makes it easy to write a computer program which can examine a web page, check for any microformats and then extract the information from that page.</blockquote>

<blockquote style="font-size:larger;">Also, in the above example you might have noticed the following code:

<pre><div class="vcard"></pre>

Why have we used "vcard" when the name of the microformat is hCard?</blockquote>

<blockquote style="font-size:larger;">Well, another important feature of microformats is that they don't try to reinvent the wheel. </blockquote>

<blockquote style="font-size:larger;">There was already an existing standard for labelling contact details on desktop computer, the [http://en.wikipedia.org/wiki/Vcard V Card]. V Cards are small files containing your contact information, which you can send to people you know. They can then import those contact details into any piece of software that supports the V Card format, for example Outlook Express.</blockquote>

<blockquote style="font-size:larger;">Rather than coming up with a whole new way of labelling contact information, the hCard microformat uses the same structure as V Cards. (the "h" in hCard stands for hypertext, by the way).</blockquote>

<blockquote style="font-size:larger;">And that's pretty much it. Microformats are a way of labelling information on web pages, so that it can be extracted by a computer program or web application. They're designed to be easy to use for people, and where possible, they are based in existing standards used elsewhere.</blockquote>

[[User:RichQuick|Richard Quick]]. Note: This text (with minor alterations) now appears in [http://ineasysteps.com/books/details/?1840783141 Web Design in easy steps]
*Superb plain-language intro! [[User:AndyMabbett|AndyMabbett]] 01:02, 26 Oct 2006 (PDT)

== BenWest ==

<blockquote style="font-size:larger;">
A microformat is a specific collection of names, values, and accompanying structure defined through rigorous market research intended to consider pervasive use of semantic html that increases data fidelity in HTML-borne data widely distributed on the web.

Microformats are more than one of these, eg "hcard and hcal are microformats."
</blockquote>

== DerrickPallas ==

<blockquote style="font-size:larger;">microformats are semantics with momentum, a codification of what everyone did anyway. They are what works, written down.</blockquote>

== Add Yours Here ==

<blockquote style="font-size:larger;">microformats are...</blockquote>

written by You.

== See Also ==

* [[what-can-you-do-with-microformats]]
* [[faq]]

== Translation ==
* [[what-are-microformats-fr|c'est quoi les microformats]] (fr)