Microformats Wiki - User contributions [en]

hcard

2005-07-01T18:33:08Z

PatrickCrowley: /* Examples in the wild */

= hCard =

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

== Draft 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 is a 1:1 representation of the aforementioned vCard standard, in semantic XHTML. Bloggers can both embed vCards directly in their web pages, and style them with CSS to make them appear as desired. In addition, hCard enables applications to retrieve information about such vCards directly from web pages without having to reference a separate file.

== Semantic XHTML Design Principles ==
{{SemanticXHTMLDesignPrinciples}}

== 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 ===
However, for some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:
* <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>

=== 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. Plural properties with subtypes (e.g. TEL with WORK, HOME, CELL) can be optimized to share a common element for the property itself, with each instance of subtype being an appropriately classed descendant of the property element.

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

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

=== 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''' properties as defined in Sections 2.1.2, 2.1.3, 2.1.4, 3.6.3 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 URL that converts hCards to vCards), for an output vCard stream (e.g. a .vcf file).

=== 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 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 or three or more, then the author MUST explicitly markup the "N".

# 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 their firstname space lastname.

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

=== XMDP Profile ===

See [[hcard-profile]] for the [http://gmpg.org/xmdp XMDP] profile of hCard.

== Example ==
Here is a sample vCard:

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

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

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

This hCard might be displayed as::

[http://tantek.com/ Tantek Çelik]<br />
Technorati

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.

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

The following sites have published hCards, and thus are a great place to start for anyone looking for examples "in the wild" to try parsing, indexing, organizing etc. If you have an hCard on your own page, 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://cinematreasures.org Cinema Treasures] uses hCard to markup venue information for 10,000+ movie theaters.
* [http://thedredge.org Andy Hume] uses the hcard format to mark-up the names and URLs of commentors on his blog.
* [http://www.wolfsreign.com Steven Ametjan] has published his hCard on [http://www.wolfsreign.com/about/ his about page].
* [http://evdb.com EVDB], the Events and Venues Database, publishes all venue detail pages with embedded hCards.
* [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://zooibaai.nl/ Rob Mientjes] has published his hCard on [http://zooibaai.nl/about his about page].
* [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://technorati.com/ Technorati]'s [http://www.technorati.com/about/ About page] lists their '''Media Contact''', and their [http://www.technorati.com/about/news.html Press page] also lists their '''Press Contact''', both as inline hCards.
* [http://tantek.com/log Tantek's Thoughts] includes an inline author hCard at the bottom of the page.

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

The following implementations have been developed which either generate or parse hCards. If you have an hCard 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.

* The [http://tantek.com/microformats/hcard-creator.html hCard creator] is a very simple, yet illustrative, open source user interface / form / script which creates an hCard in real-time as you type in a set of contact information.
* [http://greenbytes.de/tech/webdav/rfc2629.xslt rfc2629.xslt] now attempts to generate hCard information ([http://ietf.org/rfc/rfc2629 RFC2629] is an XML format for authoring RFCs and Internet Drafts, see [http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html example document])
* [http://tantek.com/microformats/buddylist2hcards.html iChat buddy list to hCards] - Open source AppleScript to automatically convert one's buddy list in the MacOSX iChat AIM client into a valid XHTML 1.0 Strict list of hCards.
* [http://suda.co.uk/projects/X2V/ X2V] is a bookmarklet that parses hCard and produces a .vcf (vCard) stream. Note: needs to be updated as the spec is refined

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

=== Informative References ===
* [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]
* Contributed from http://developers.technorati.com/wiki/hCard.
* [http://www.w3.org/TR/xhtml11 XHTML 1.1]

=== Similar Work ===
* [[hcalendar]]
* [[XOXO]]
* [http://www.intertwingly.net/wiki/pie/PaceBetterPersonElement Atom PaceBetterPersonElement]

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. There is a separate document where we are keeping our brainstorms and other explorations relating to hCard:

* [[hcard-brainstorming|hCard Brainstorming]]

== Discussions ==

* See [http://www.technorati.com/cosmos/referer.html blogs discussing this page].

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

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

hcard

2005-06-30T21:53:41Z

PatrickCrowley: /* Examples in the wild */

= hCard =

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

== Draft 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 is a 1:1 representation of the aforementioned vCard standard, in semantic XHTML. Bloggers can both embed vCards directly in their web pages, and style them with CSS to make them appear as desired. In addition, hCard enables applications to retrieve information about such vCards directly from web pages without having to reference a separate file.

== Semantic XHTML Design Principles ==
{{SemanticXHTMLDesignPrinciples}}

== 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 ===
However, for some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:
* <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>

=== 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. Plural properties with subtypes (e.g. TEL with WORK, HOME, CELL) can be optimized to share a common element for the property itself, with each instance of subtype being an appropriately classed descendant of the property element.

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

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

=== 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''' properties as defined in Sections 2.1.2, 2.1.3, 2.1.4, 3.6.3 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 URL that converts hCards to vCards), for an output vCard stream (e.g. a .vcf file).

=== 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 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 or three or more, then the author MUST explicitly markup the "N".

# 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 their firstname space lastname.

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

=== XMDP Profile ===

See [[hcard-profile]] for the [http://gmpg.org/xmdp XMDP] profile of hCard.

== Example ==
Here is a sample vCard:

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

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

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

This hCard might be displayed as::

[http://tantek.com/ Tantek Çelik]<br />
Technorati

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.

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

The following sites have published hCards, and thus are a great place to start for anyone looking for examples "in the wild" to try parsing, indexing, organizing etc. If you have an hCard on your own page, 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://cinematreasures.org Cinema Treasures] uses hCard to provide venue information for 10,000+ movie theaters.
* [http://thedredge.org Andy Hume] uses the hcard format to mark-up the names and URLs of commentors on his blog.
* [http://www.wolfsreign.com Steven Ametjan] has published his hCard on [http://www.wolfsreign.com/about/ his about page].
* [http://evdb.com EVDB], the Events and Venues Database, publishes all venue detail pages with embedded hCards.
* [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://zooibaai.nl/ Rob Mientjes] has published his hCard on [http://zooibaai.nl/about his about page].
* [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://technorati.com/ Technorati]'s [http://www.technorati.com/about/ About page] lists their '''Media Contact''', and their [http://www.technorati.com/about/news.html Press page] also lists their '''Press Contact''', both as inline hCards.
* [http://tantek.com/log Tantek's Thoughts] includes an inline author hCard at the bottom of the page.

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

The following implementations have been developed which either generate or parse hCards. If you have an hCard 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.

* The [http://tantek.com/microformats/hcard-creator.html hCard creator] is a very simple, yet illustrative, open source user interface / form / script which creates an hCard in real-time as you type in a set of contact information.
* [http://greenbytes.de/tech/webdav/rfc2629.xslt rfc2629.xslt] now attempts to generate hCard information ([http://ietf.org/rfc/rfc2629 RFC2629] is an XML format for authoring RFCs and Internet Drafts, see [http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html example document])
* [http://tantek.com/microformats/buddylist2hcards.html iChat buddy list to hCards] - Open source AppleScript to automatically convert one's buddy list in the MacOSX iChat AIM client into a valid XHTML 1.0 Strict list of hCards.
* [http://suda.co.uk/projects/X2V/ X2V] is a bookmarklet that parses hCard and produces a .vcf (vCard) stream. Note: needs to be updated as the spec is refined

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

=== Informative References ===
* [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]
* Contributed from http://developers.technorati.com/wiki/hCard.
* [http://www.w3.org/TR/xhtml11 XHTML 1.1]

=== Similar Work ===
* [[hcalendar]]
* [[XOXO]]
* [http://www.intertwingly.net/wiki/pie/PaceBetterPersonElement Atom PaceBetterPersonElement]

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. There is a separate document where we are keeping our brainstorms and other explorations relating to hCard:

* [[hcard-brainstorming|hCard Brainstorming]]

== Discussions ==

* See [http://www.technorati.com/cosmos/referer.html blogs discussing this page].

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

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

hcard

2005-06-30T21:50:08Z

PatrickCrowley: /* Examples in the wild */

= hCard =

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

== Draft 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 is a 1:1 representation of the aforementioned vCard standard, in semantic XHTML. Bloggers can both embed vCards directly in their web pages, and style them with CSS to make them appear as desired. In addition, hCard enables applications to retrieve information about such vCards directly from web pages without having to reference a separate file.

== Semantic XHTML Design Principles ==
{{SemanticXHTMLDesignPrinciples}}

== 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 ===
However, for some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:
* <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>

=== 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. Plural properties with subtypes (e.g. TEL with WORK, HOME, CELL) can be optimized to share a common element for the property itself, with each instance of subtype being an appropriately classed descendant of the property element.

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

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

=== 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''' properties as defined in Sections 2.1.2, 2.1.3, 2.1.4, 3.6.3 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 URL that converts hCards to vCards), for an output vCard stream (e.g. a .vcf file).

=== 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 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 or three or more, then the author MUST explicitly markup the "N".

# 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 their firstname space lastname.

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

=== XMDP Profile ===

See [[hcard-profile]] for the [http://gmpg.org/xmdp XMDP] profile of hCard.

== Example ==
Here is a sample vCard:

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

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

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

This hCard might be displayed as::

[http://tantek.com/ Tantek Çelik]<br />
Technorati

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.

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

The following sites have published hCards, and thus are a great place to start for anyone looking for examples "in the wild" to try parsing, indexing, organizing etc. If you have an hCard on your own page, 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://cinematreasures.org Cinema Treasures] uses hCard to provide venue information for 10,000+ movie theaters
* [http://thedredge.org Andy Hume] uses the hcard format to mark-up the names and URLs of commentors on his blog.
* [http://www.wolfsreign.com Steven Ametjan] has published his hCard on [http://www.wolfsreign.com/about/ his about page].
* [http://evdb.com EVDB], the Events and Venues Database, publishes all venue detail pages with embedded hCards.
* [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://zooibaai.nl/ Rob Mientjes] has published his hCard on [http://zooibaai.nl/about his about page].
* [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://technorati.com/ Technorati]'s [http://www.technorati.com/about/ About page] lists their '''Media Contact''', and their [http://www.technorati.com/about/news.html Press page] also lists their '''Press Contact''', both as inline hCards.
* [http://tantek.com/log Tantek's Thoughts] includes an inline author hCard at the bottom of the page.

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

The following implementations have been developed which either generate or parse hCards. If you have an hCard 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.

* The [http://tantek.com/microformats/hcard-creator.html hCard creator] is a very simple, yet illustrative, open source user interface / form / script which creates an hCard in real-time as you type in a set of contact information.
* [http://greenbytes.de/tech/webdav/rfc2629.xslt rfc2629.xslt] now attempts to generate hCard information ([http://ietf.org/rfc/rfc2629 RFC2629] is an XML format for authoring RFCs and Internet Drafts, see [http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html example document])
* [http://tantek.com/microformats/buddylist2hcards.html iChat buddy list to hCards] - Open source AppleScript to automatically convert one's buddy list in the MacOSX iChat AIM client into a valid XHTML 1.0 Strict list of hCards.
* [http://suda.co.uk/projects/X2V/ X2V] is a bookmarklet that parses hCard and produces a .vcf (vCard) stream. Note: needs to be updated as the spec is refined

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

=== Informative References ===
* [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]
* Contributed from http://developers.technorati.com/wiki/hCard.
* [http://www.w3.org/TR/xhtml11 XHTML 1.1]

=== Similar Work ===
* [[hcalendar]]
* [[XOXO]]
* [http://www.intertwingly.net/wiki/pie/PaceBetterPersonElement Atom PaceBetterPersonElement]

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. There is a separate document where we are keeping our brainstorms and other explorations relating to hCard:

* [[hcard-brainstorming|hCard Brainstorming]]

== Discussions ==

* See [http://www.technorati.com/cosmos/referer.html blogs discussing this page].

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

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

location-formats

2005-06-30T02:26:18Z

PatrickCrowley: /* Location Formats */

= Location Formats =
__TOC__
This is a list of previous efforts at location / geographic ("Geo") data formats and protocols, as background research for developing a location format.

== vCard & hCard ==
vCard (RFC2426) and [[hcard]] includes 'adr', a way to markup addresses. There is also a field called 'geo' for lat/long.

== ICBM ==
Comma seperated list of lat/long <code><meta name="ICBM" content="XXX.XXXXX, XXX.XXXXX"></code>
[http://www.catb.org/~esr/jargon/html/I/ICBM-address.html]

== GeoUrl ==
* [http://geourl.org/ GeoURL]

== Flickr Geotags ==
* [http://steeev.f2o.org/mt/2005/05/geotagging_flickr_with_google_maps_and_greasemonkey_part_2.html Flickr GeoTagging] A Greasemonkey script for adding lat and long tags to flick pictures. He uses Google Maps to get the lat and long. Users have to enter search terms (address, etc) and then select a point on the google map. Photos are tagged with "geo:lat=xx.xxxx", "geo:lon=xx.xxxx" and "geotagged" and aggregated at [http://geobloggers.com/]
* [http://flickr.com/groups/geotagging/ A Flickr Group related to the topic]
* [http://txfx.net/2005/05/17/flickr-google-maps-geobloggers/ A visual walkthrough of the technique.]
* As of today (2005-06-01), 14k photos have been geotagged on Flickr.
* [http://mappr.com mappr], [http://brainoff.com/worldkit/flick mapping flickr] also support these geotags.
* flickr also supports [http://www.flickr.com/services/api/flickr.photos.getExif.html EXIF headers], which can be used for storing location.

== Geotagging ==
* Geotagging has been employed in other hosted services: [http://brainoff.com/worldkit/delicious/ delicious], [http://worldkit.typepad.com/ Typepad], [http://blog.360.yahoo.com/blog-yRZQpvY8cq2kWXBO5ZrxEmrwsg--?p=9 Yahoo 360]

== A2B ==
[http://www.a2b.cc/ A2B] is a location based search engine. Lat and long only. Seems to pick stuff up from geo meta tags. Pages can either be manually entered or [http://www.a2b.cc/help-searching-addurl-blogping.a2b pinged]. They support lat/long and ICBM meta tags.

== RSS ==
Several people have tried putting geographic information into RSS.
* [http://postneo.com/icbm/ This site] uses icbm coordinates and has plugins for several blogging packages.
* [http://www.blogmapper.com/ BlogMapper] - appears to be adding a namespace to RSS.
* [http://www.feedmap.net/BlogMap/ BlogMap] - picks up RSS extension and meta tag values
* [http://brainoff.com/worldkit/doc/rss.php worldKit RSS docs] - worldKit advocates and understands various flavors of geocoded RSS; particularly the "geo" namespace.
* [http://earthquake.usgs.gov/recenteqsww/rss.html USGS earthquake feed] - most widely used geocoded RSS feed
* [http://brainoff.com/worldkit/doc/polygon.php Polygons and lines in polygons] - A simple format for expressing polygons and lines is defined for worldKit

== Address2Coordinates ==
Both of these systems are freely available sources of address to lat/long mappings (US only). I think they're based on US Census data, so they might be up to date.
* [http://www.census.gov/geo/www/tiger/ TIGER]
* [http://www.itl.nist.gov/fipspubs/55new/nav-top-fr.htm FIPS]
* [http://geocoder.us/ geocoder]
* You can get coordinates from UK post-codes from [http://www.streetmap.co.uk streetmap]
* Worldwide city level location data (over 4 million entries) is available from the [http://earth-info.nga.mil/gns/html/ GNS]. This is accessible as a REST service from the [http://brainoff.com/geocoder/ worldkit geocoder]

== Plazes ==
[http://plazes.com Plazes] is a system that does geo-info based on the network access point that the user's computer is connected to. They use tagging to identify locations.

== Mapping Sites ==
* [http://www.multimap.com Multimap]
* [http://maps.google.com Google Maps]
* [http://www.mapquest.com MapQuest]
* [http://maps.yahoo.com Yahoo Maps]
* [http://www.mapblast.com MapBlast]
* [http://mapufacture.com mapufacture]

== Semantic Web ==
* [http://www.geosemantics.org/ Geosemantics Interest Group]
* [http://www.opengeospatial.org/ Open GeoSpatial Consortium]
* [http://esw.w3.org/topic/GeoOnion GeoOnion] - a SW vocuabulary for relating items by distance from each other.
* [http://www.mapbureau.com/rdfmap1.0/index.html RDFMap]
* [http://esw.w3.org/topic/GeoRDF GeoRDF] similar effort to collect prior art, for an effort in interoperability between OGC standards and various lightweight geo formats.

== GML ==
[http://www.opengeospatial.org/docs/02-023r4.pdf Geographic Markup Language] - a "600 page standard"

== Google Earth XML ==
20050629 at Where 2.0 conference:
"Google Earth has an XML schema for describing a place on the earth. Will be releasing today or tomorrow."
- John Hanke of Google/Keyhole.

== Yahoo Maps API ==
* [http://developer.yahoo.net/maps/ Yahoo Maps API documentation]

== Google Maps API ==
* [http://www.google.com/apis/maps/ Google Maps API documentation]

== OGC ==

== WCS ==

Main Page

2005-06-23T19:55:23Z

PatrickCrowley: /* Exploratory discussions */

Welcome to the new microformats wiki. There's a lot going on around here, but feel free to jump in and offer your assistance.

== Standards ==
[[microformats|Microformats]] open standards specifications:
* [[hcalendar|hCalendar]]
* [[hcard|hCard]]
* [[rel-license|RelLicense]]
* [[rel-nofollow|RelNoFollow]]
* [[rel-tag|RelTag]]
* [[vote-links|VoteLinks]]
* [[xoxo|XOXO]]

== Drafts ==
* [[hreview|hReview]]
* [[robots-exclusion|Robots Exclusion]]
* [[rel-enclosure]]

== Proposals ==
*[[hcomment|hComment]]
* [[mfcomment|mfComment]]

== Exploratory discussions ==

*[[comments-formats|comments-formats]]
*[[media-metadata-examples|media-metadata-examples]]
*[[reviews-formats| reviews-formats]]

Main Page

2005-06-23T19:54:26Z

PatrickCrowley: /* Exploratory discussions */

Welcome to the new microformats wiki. There's a lot going on around here, but feel free to jump in and offer your assistance.

== Standards ==
[[microformats|Microformats]] open standards specifications:
* [[hcalendar|hCalendar]]
* [[hcard|hCard]]
* [[rel-license|RelLicense]]
* [[rel-nofollow|RelNoFollow]]
* [[rel-tag|RelTag]]
* [[vote-links|VoteLinks]]
* [[xoxo|XOXO]]

== Drafts ==
* [[hreview|hReview]]
* [[robots-exclusion|Robots Exclusion]]
* [[rel-enclosure]]

== Proposals ==
*[[hcomment|hComment]]
* [[mfcomment|mfComment]]

== Exploratory discussions ==

*[[media-metadata-examples|media-metadata-examples]]
*[[comments-formats|comments-formats]]

comments-formats

2005-06-23T19:09:56Z

PatrickCrowley: /* Examples from the wild */

= Current Comments Formats =
There have been several efforts to define data formats for posting "comments" on the Web.

This page serves to document the current list of comment schemas, formats, and efforts as background for the design of a simple comments MicroFormat.

== Centralized Implementations ==

=== WordPress ===
* http://wordpress.org

** comment_ID
** comment_author
** comment_author_IP
** comment_author_email
** comment_author_link
** comment_type
** comment_text
** comment_excerpt
** comment_date
** comment_time

=== pMachine ===
* http://pmachine.com

** body
** date
** name
** location
** url
** email
** profile_link
** member_total_comments

=== Expression Engine ===
* http://pmachine.com

** {author_id}
** {comment}
** {comment_id}
** {ip_address}
** {name}
** {permalink}
** {url}
** {url_or_email}

Expression Engine includes many additional comments templates tags. This list excludes the following tags: tags used to display user data (instant message handles, location, occupation, etc.), tags which are used for navigation within EE-based blogs or websites, tags which deal with comment presentation (alternating background colors between comments), and custom member tags (which are defined by individual sites.)

== Examples from the wild ==

* brianstorms (movable type) (from http://www.brianstorms.com/archives/000580.html)
<pre><code><nowiki>
<div class="comments-body">
<p>Congratulations! Any list that includes Molly Holzschlag and Wil Wheaton is certainly something...
and that's just the Honorable Mentions.</p>

<p>Now to scrape the links of all the rest of those "people you may not know but probably should"...</p>
<span class="comments-post">Posted by:
<a href="http://www.brianstorms.com/mt/mt-comments.cgi?__mode=red&id=3826">Chris</a>
at June 21, 2005 08:53 PM</span>
</div>
</nowiki></code></pre>

* mfComment "small" example:
<pre><nowiki>
<div class="mfcomment">
<a class="url" rel="target" href="http://an9.org/blog/2005/06/07/super-sekret-project/">Super Sekret Project</a>
<span class="commenter">anonymous</span>
<abbr class="dtcommented" title="20050612T21:30-0700">June 12th, 2005</abbr>
<div class="description">
<p>Gosh, this is neat.</p>
</div>
<a class="url" rel="self bookmark" href="http://sxore.com/comment/view/14">link to this comment</a>
</div>
</nowiki></pre>

comments-formats

2005-06-23T19:00:46Z

PatrickCrowley: /* Expression Engine */

comments-formats

2005-06-23T18:59:57Z

PatrickCrowley: /* Blogging software comment fields */

= Current Comments Formats =
There have been several efforts to define data formats for posting "comments" on the Web.

This page serves to document the current list of comment schemas, formats, and efforts as background for the design of a simple comments MicroFormat.

== Centralized Implementations ==

=== WordPress ===
* http://wordpress.org

** comment_ID
** comment_author
** comment_author_IP
** comment_author_email
** comment_author_link
** comment_type
** comment_text
** comment_excerpt
** comment_date
** comment_time

=== pMachine ===
* http://pmachine.com

** body
** date
** name
** location
** url
** email
** profile_link
** member_total_comments

=== Expression Engine ===
* http://pmachine.com

** {author_id}
** {comment}
** {comment_id}
** {interests}
** {ip_address}
** {location}
** {member_search_path}
** {occupation}
** {name}
** {permalink}
** {url}
** {url_or_email}

Expression Engine includes many additional comments templates tags. This list excludes the following tags: tags used to display user data (instant message handles, etc.), tags which are used for navigation within EE-based blogs or websites, tags which deal with comment presentation (alternating background colors between comments), and custom member tags (which are defined by individual sites.)

== Examples from the wild ==

* brianstorms (movable type) (from http://www.brianstorms.com/archives/000580.html)
<pre><code><nowiki>
<div class="comments-body">
<p>Congratulations! Any list that includes Molly Holzschlag and Wil Wheaton is certainly something...
and that's just the Honorable Mentions.</p>

<p>Now to scrape the links of all the rest of those "people you may not know but probably should"...</p>
<span class="comments-post">Posted by:
<a href="http://www.brianstorms.com/mt/mt-comments.cgi?__mode=red&id=3826">Chris</a>
at June 21, 2005 08:53 PM</span>
</div>
</nowiki></code></pre>

comments-formats

2005-06-23T18:58:41Z

PatrickCrowley: /* Examples from the wild */

= Current Comments Formats =
There have been several efforts to define data formats for posting "comments" on the Web.

This page serves to document the current list of comment schemas, formats, and efforts as background for the design of a simple comments MicroFormat.

== Blogging software comment fields ==

=== WordPress ===
* http://wordpress.org

** comment_ID
** comment_author
** comment_author_IP
** comment_author_email
** comment_author_link
** comment_type
** comment_text
** comment_excerpt
** comment_date
** comment_time

=== pMachine ===
* http://pmachine.com

** body
** date
** name
** location
** url
** email
** profile_link
** member_total_comments

=== Expression Engine ===
* http://pmachine.com

** {author_id}
** {comment}
** {comment_id}
** {interests}
** {ip_address}
** {location}
** {member_search_path}
** {occupation}
** {name}
** {permalink}
** {url}
** {url_or_email}

Expression Engine includes many additional comments templates tags. This list excludes the following tags: tags used to display user data (instant message handles, etc.), tags which are used for navigation within EE-based blogs or websites, tags which deal with comment presentation (alternating background colors between comments), and custom member tags (which are defined by individual sites.)

== Examples from the wild ==

* brianstorms (movable type) (from http://www.brianstorms.com/archives/000580.html)
<pre><code><nowiki>
<div class="comments-body">
<p>Congratulations! Any list that includes Molly Holzschlag and Wil Wheaton is certainly something...
and that's just the Honorable Mentions.</p>

<p>Now to scrape the links of all the rest of those "people you may not know but probably should"...</p>
<span class="comments-post">Posted by:
<a href="http://www.brianstorms.com/mt/mt-comments.cgi?__mode=red&id=3826">Chris</a>
at June 21, 2005 08:53 PM</span>
</div>
</nowiki></code></pre>

comments-formats

2005-06-23T18:57:38Z

PatrickCrowley: /* Expression Engine */

= Current Comments Formats =
There have been several efforts to define data formats for posting "comments" on the Web.

This page serves to document the current list of comment schemas, formats, and efforts as background for the design of a simple comments MicroFormat.

== Blogging software comment fields ==

=== WordPress ===
* http://wordpress.org

** comment_ID
** comment_author
** comment_author_IP
** comment_author_email
** comment_author_link
** comment_type
** comment_text
** comment_excerpt
** comment_date
** comment_time

=== pMachine ===
* http://pmachine.com

** body
** date
** name
** location
** url
** email
** profile_link
** member_total_comments

=== Expression Engine ===
* http://pmachine.com

** {author_id}
** {comment}
** {comment_id}
** {interests}
** {ip_address}
** {location}
** {member_search_path}
** {occupation}
** {name}
** {permalink}
** {url}
** {url_or_email}

Expression Engine includes many additional comments templates tags. This list excludes the following tags: tags used to display user data (instant message handles, etc.), tags which are used for navigation within EE-based blogs or websites, tags which deal with comment presentation (alternating background colors between comments), and custom member tags (which are defined by individual sites.)

== Examples from the wild ==

* brianstorms (movable type) (from http://www.brianstorms.com/archives/000580.html)
<pre><code><nowiki>
<div class="comments-body">
<p>Congratulations! Any list that includes Molly Holzschlag and Wil Wheaton is certainly something... and that's just the Honorable Mentions.</p>

<p>Now to scrape the links of all the rest of those "people you may not know but probably should"...</p>
<span class="comments-post">Posted by: <a href="http://www.brianstorms.com/mt/mt-comments.cgi?__mode=red&id=3826">Chris</a> at June 21, 2005 08:53 PM</span>
</div>
</nowiki></code></pre>

comments-formats

2005-06-23T18:56:32Z

PatrickCrowley: /* Expression Engine */

= Current Comments Formats =
There have been several efforts to define data formats for posting "comments" on the Web.

This page serves to document the current list of comment schemas, formats, and efforts as background for the design of a simple comments MicroFormat.

== Blogging software comment fields ==

=== WordPress ===
* http://wordpress.org

** comment_ID
** comment_author
** comment_author_IP
** comment_author_email
** comment_author_link
** comment_type
** comment_text
** comment_excerpt
** comment_date
** comment_time

=== pMachine ===
* http://pmachine.com

** body
** date
** name
** location
** url
** email
** profile_link
** member_total_comments

=== Expression Engine ===
* http://pmachine.com

** {author_id}
** {comment}
** {comment_id}
** {interests}
** {ip_address}
** {location}
** {member_search_path}
** {occupation}
** {name}
** {permalink}
** {url}
** {url_or_email}
** {url_or_email_as_author}
** {url_or_email_as_link}
** {url_title_path=weblog/comments}

Expression Engine includes many additional comments templates tags. This list excludes the following tags: tags used to display user data (instant message handles, etc.), tags which are used for navigation within EE-based blogs or websites, tags which deal with comment presentation (alternating background colors between comments), and custom member tags (which are defined by individual sites.)

== Examples from the wild ==

* brianstorms (movable type) (from http://www.brianstorms.com/archives/000580.html)
<pre><code><nowiki>
<div class="comments-body">
<p>Congratulations! Any list that includes Molly Holzschlag and Wil Wheaton is certainly something... and that's just the Honorable Mentions.</p>

<p>Now to scrape the links of all the rest of those "people you may not know but probably should"...</p>
<span class="comments-post">Posted by: <a href="http://www.brianstorms.com/mt/mt-comments.cgi?__mode=red&id=3826">Chris</a> at June 21, 2005 08:53 PM</span>
</div>
</nowiki></code></pre>

comments-formats

2005-06-23T18:55:03Z

PatrickCrowley: /* Blogging software comment fields */

= Current Comments Formats =
There have been several efforts to define data formats for posting "comments" on the Web.

This page serves to document the current list of comment schemas, formats, and efforts as background for the design of a simple comments MicroFormat.

== Blogging software comment fields ==

=== WordPress ===
* http://wordpress.org

** comment_ID
** comment_author
** comment_author_IP
** comment_author_email
** comment_author_link
** comment_type
** comment_text
** comment_excerpt
** comment_date
** comment_time

=== pMachine ===
* http://pmachine.com

** body
** date
** name
** location
** url
** email
** profile_link
** member_total_comments

=== Expression Engine ===
* http://pmachine.com

** {author_id}
** {comment}
** {comment_id}
** {interests}
** {ip_address}
** {location}
** {member_search_path}
** {occupation}
** {name}
** {permalink}
** {url}
** {url_or_email}
** {url_or_email_as_author}
** {url_or_email_as_link}
** {url_title_path=weblog/comments}

Expression Engine includes many additional comments templates tags, but I have excluded these tags: tags used to display user data (instant message handles, etc.), tags which are used for navigation within EE-based blogs or websites, tags which deal with comment presentation (alternating background colors between comments), and custom member tags (which are defined by individual sites.)

== Examples from the wild ==

* brianstorms (movable type) (from http://www.brianstorms.com/archives/000580.html)
<pre><code><nowiki>
<div class="comments-body">
<p>Congratulations! Any list that includes Molly Holzschlag and Wil Wheaton is certainly something... and that's just the Honorable Mentions.</p>

<p>Now to scrape the links of all the rest of those "people you may not know but probably should"...</p>
<span class="comments-post">Posted by: <a href="http://www.brianstorms.com/mt/mt-comments.cgi?__mode=red&id=3826">Chris</a> at June 21, 2005 08:53 PM</span>
</div>
</nowiki></code></pre>

comments-formats

2005-06-23T18:38:15Z

PatrickCrowley: /* Blogging software comment fields */

User:PatrickCrowley

2005-06-21T17:47:52Z

PatrickCrowley:

= Patrick Crowley =

* I work for http://evdb.com
* I'm the creator of http://icalshare.com

User:PatrickCrowley

2005-06-21T17:47:32Z

PatrickCrowley:

* I work for http://evdb.com
* I'm the creator of http://icalshare.com