Microformats Wiki - User contributions [en]

hcard

2006-01-16T15:18:29Z

Emiliano: /* Implementations */

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

Use the [http://microformats.org/code/hcard/creator hCard creator], 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 ===
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. Multivalued 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 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.

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.

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

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

home: +1.415.555.1212

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

=== 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", except for the organization contact info case, [http://microformats.org/wiki/hcard#Organization_Contact_Info see below] 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 their firstname space lastname, or lastname comma firstname, or lastname comma firstinitial, or lastname space firstinitial.

==== Organization Contact Info ====

Contact info for a company or organization is a special case of the implied "N" optimization.

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

=== Root Class Name ===

The root class name for an hCard is "vcard".

=== Property List ===

This is the list of properties (and subproperties, in parantheses, 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
==== 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:
<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>

The following lists are ''informative''. See RFC2426 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, 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:

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

=== More Examples ===

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

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

=== New Examples ===
Please add new examples to this section.

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

=== Examples ===
* [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 the hcard format to mark-up the names and URLs of commentors on his 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.
* [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.
* [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://evdb.com EVDB], the Events and Venues Database, publishes all venue detail 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.ndunn.com Neil Dunn] has published his rather [http://www.ndunn.com/2005/10/7/hCard good looking hCard]
* [http://www.oliverbrown.me.uk/ Oliver Brown] has published his hCard.
* [http://www.paradigmproductions.org/contact/ Paradigm Productions] published a vcard as a ul (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.wolfsreign.com Steven Ametjan] has published his hCard on [http://www.wolfsreign.com/about/ his about page].
* [http://tagcamp.org/index.cgi?ContactList TagCamp contact list]
* [http://tantek.com/log 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].

=== Examples with some problems ===
* [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://www.kerihenare.com/ Keri Henare] has marked up his [http://www.kerihenare.com/contact/ contact info page] with hCard.
** (2005-09-27) PASSED
** (2005-11-01) hCard completely rewritten
** WARNING - type subproperty in classname
* [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 (ie, it doesn't contain lat/long)
* [http://landsbank.fo/#hCard Landsbanki Føroya]
** INVALID - using embedded rdf/xml invalidly
* [http://chrischerry.name/blog/contact/ Chris Cherry's contact page with his hCard]
** WARNING - uses class="cell" instead of <span class="type">cell</span>
* [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)
** where? more detail and I will fix. -- [[User:PhilWilson|PhilWilson]] 23:22, 11 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.shiftingpixel.com/about/ shifting pixel photoblog] has published an hCard.
** "organization_name" should be "organization-name" (s/_/-/), otherwise good --[[User:RyanKing|RyanKing]] 14:01, 5 Jan 2006 (PST)

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

* There is [http://flickr.com/photos/factoryjoe/68755089/ evidence of built-in hCard support in the Konqueror browser]. Specifically, Konqueror 3.5, in KDE 3.5 (kubuntu Breezy w/ update).
* There is [http://tagcamp.org/index.cgi?ContactList evidence of a kwiki plugin for hCards]. Update: the [http://svn.kwiki.org/cwest/Kwiki-hCard/ hCard kwiki plugin svn repository]. See the [http://microwiki.caseywest.com/index.cgi?hCard documentation of the hCard kwiki plugin].
* [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
* [http://www.stripytshirt.co.uk Duncan Walker] has built [http://www.stripytshirt.co.uk/features/firefox/smartzilla a Firefox extension] that gets hCard data from a webpage, uses Brian Suda's XSL (locally) to transform it to vcard format and opens the resulting .vcf file.
* [http://george.hotelling.net/90percent/ George] has written a [http://george.hotelling.net/90percent/geekery/greasemonkey_and_microformats.php Greasemonkey user script] that detects hCards and allows users to easily add them to their address book application. Relies on the X2V web service to do the conversion.
* [http://blogmatrix.blogmatrix.com/ David Janes] has written a [[Greasemonkey]] [http://www.blogmatrix.com/include/microformat-find.user.js script] that finds many microformat elements, including hCards, and [http://blog.davidjanes.com/mtarchives/2005_08.html#003376 provides a popup menu of actions]. The hCard to vCard conversion is done internally within the script. ''This does not work with FireFox 1.5+/GreaseMonkey 0.6.4+.''
* [http://diveintomark.org/ Mark Pilgrim] has also written an [http://diveintomark.org/projects/greasemonkey/hcard/ hCard parser Greasemonkey user script]. It is self-contained and does not rely on the X2V web service.
* [http://www.oliverbrown.me.uk/2005/09/03/a-working-microformats-extension-to-simplexml/ Oliver Brown] has written an "extension" to [http://www.php.net/simplexml SimpleXML] that gives simple access to hCard information in PHP 5.
* [http://thedredge.org/ Andrew D. Hume] has built a system (Wordpress plugin?) for [http://thedredge.org/2005/06/using-hcards-in-your-blog/ using hcards in your blog] to represent people leaving comments on blog posts.
* 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://dev.w3.org/cvsweb/2001/palmagent/ palmagent] is a collection of palmpilot and sidekick tools. It includes X2V derivatives xhtml2hcard.xsl and toICal.xsl plus some [http://dev.w3.org/cvsweb/2001/palmagent/hcardTest.html hcardTest] materials
* [http://www.openpsa.org/ OpenPsa 2.x] CRM application uses hCard for all person listings. The widget is [http://www.midgard-project.org/midcom-permalink-922834501b71daad856f35ec593c7a6d reusable across Midgard CMS]
* [http://www.metonymie.com Emiliano Martínez Luque] has written an experimental [http://www.metonymie.com/hCard_extract/app.html hCard finder and structured search application] that finds hCards within a given set of URLs and returns the ones that match the specified search criteria.

== Additional Applications ==
This section is '''informative'''.

There are numerous potential additional uses and applications for hCards on the Web. The following are merely a few thoughts and possibilities that folks have come up with:

* As an open standard/format for [http://www.gravatar.com/ Gravatars].
* Marking up individual authors of blog posts on a group blog
* Marking up people's names and URLs in a blogroll
* Any reference to people in blog posts (e.g. when citing them, or referencing them, or describing them, by name).
* ...

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

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

== Related Pages And Further Reading ==
* [[hcard-profile|hCard profile]] - The XMDP profile for hCard

This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. These thoughts, issues, and questions are kept in separate pages.

* [[hcard-brainstorming|hCard Brainstorming]] - where we are keeping our brainstorms and other explorations relating to hCard
* [[hcard-tests|hCard tests]] - a wiki page with actual embedded hCards to try parsing.
* [[hcard-faq|hCard FAQ]] - If you have any questions about hCard, check here, and if you don't find answers, add your questions!
* [[hcard-issues|hCard issues]] - Please add any issues with the specification to the issues page.
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].

hcard

2006-01-16T15:17:02Z

Emiliano: /* Implementations */

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

Use the [http://microformats.org/code/hcard/creator hCard creator], 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 ===
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. Multivalued 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 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.

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.

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

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

home: +1.415.555.1212

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

=== 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", except for the organization contact info case, [http://microformats.org/wiki/hcard#Organization_Contact_Info see below] 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 their firstname space lastname, or lastname comma firstname, or lastname comma firstinitial, or lastname space firstinitial.

==== Organization Contact Info ====

Contact info for a company or organization is a special case of the implied "N" optimization.

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

=== Root Class Name ===

The root class name for an hCard is "vcard".

=== Property List ===

This is the list of properties (and subproperties, in parantheses, 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
==== 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:
<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>

The following lists are ''informative''. See RFC2426 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, 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:

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

=== More Examples ===

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

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

=== New Examples ===
Please add new examples to this section.

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

=== Examples ===
* [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 the hcard format to mark-up the names and URLs of commentors on his 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.
* [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.
* [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://evdb.com EVDB], the Events and Venues Database, publishes all venue detail 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.ndunn.com Neil Dunn] has published his rather [http://www.ndunn.com/2005/10/7/hCard good looking hCard]
* [http://www.oliverbrown.me.uk/ Oliver Brown] has published his hCard.
* [http://www.paradigmproductions.org/contact/ Paradigm Productions] published a vcard as a ul (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.wolfsreign.com Steven Ametjan] has published his hCard on [http://www.wolfsreign.com/about/ his about page].
* [http://tagcamp.org/index.cgi?ContactList TagCamp contact list]
* [http://tantek.com/log 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].

=== Examples with some problems ===
* [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://www.kerihenare.com/ Keri Henare] has marked up his [http://www.kerihenare.com/contact/ contact info page] with hCard.
** (2005-09-27) PASSED
** (2005-11-01) hCard completely rewritten
** WARNING - type subproperty in classname
* [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 (ie, it doesn't contain lat/long)
* [http://landsbank.fo/#hCard Landsbanki Føroya]
** INVALID - using embedded rdf/xml invalidly
* [http://chrischerry.name/blog/contact/ Chris Cherry's contact page with his hCard]
** WARNING - uses class="cell" instead of <span class="type">cell</span>
* [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)
** where? more detail and I will fix. -- [[User:PhilWilson|PhilWilson]] 23:22, 11 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.shiftingpixel.com/about/ shifting pixel photoblog] has published an hCard.
** "organization_name" should be "organization-name" (s/_/-/), otherwise good --[[User:RyanKing|RyanKing]] 14:01, 5 Jan 2006 (PST)

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

* There is [http://flickr.com/photos/factoryjoe/68755089/ evidence of built-in hCard support in the Konqueror browser]. Specifically, Konqueror 3.5, in KDE 3.5 (kubuntu Breezy w/ update).
* There is [http://tagcamp.org/index.cgi?ContactList evidence of a kwiki plugin for hCards]. Update: the [http://svn.kwiki.org/cwest/Kwiki-hCard/ hCard kwiki plugin svn repository]. See the [http://microwiki.caseywest.com/index.cgi?hCard documentation of the hCard kwiki plugin].
* [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
* [http://www.stripytshirt.co.uk Duncan Walker] has built [http://www.stripytshirt.co.uk/features/firefox/smartzilla a Firefox extension] that gets hCard data from a webpage, uses Brian Suda's XSL (locally) to transform it to vcard format and opens the resulting .vcf file.
* [http://george.hotelling.net/90percent/ George] has written a [http://george.hotelling.net/90percent/geekery/greasemonkey_and_microformats.php Greasemonkey user script] that detects hCards and allows users to easily add them to their address book application. Relies on the X2V web service to do the conversion.
* [http://blogmatrix.blogmatrix.com/ David Janes] has written a [[Greasemonkey]] [http://www.blogmatrix.com/include/microformat-find.user.js script] that finds many microformat elements, including hCards, and [http://blog.davidjanes.com/mtarchives/2005_08.html#003376 provides a popup menu of actions]. The hCard to vCard conversion is done internally within the script. ''This does not work with FireFox 1.5+/GreaseMonkey 0.6.4+.''
* [http://diveintomark.org/ Mark Pilgrim] has also written an [http://diveintomark.org/projects/greasemonkey/hcard/ hCard parser Greasemonkey user script]. It is self-contained and does not rely on the X2V web service.
* [http://www.oliverbrown.me.uk/2005/09/03/a-working-microformats-extension-to-simplexml/ Oliver Brown] has written an "extension" to [http://www.php.net/simplexml SimpleXML] that gives simple access to hCard information in PHP 5.
* [http://thedredge.org/ Andrew D. Hume] has built a system (Wordpress plugin?) for [http://thedredge.org/2005/06/using-hcards-in-your-blog/ using hcards in your blog] to represent people leaving comments on blog posts.
* 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://dev.w3.org/cvsweb/2001/palmagent/ palmagent] is a collection of palmpilot and sidekick tools. It includes X2V derivatives xhtml2hcard.xsl and toICal.xsl plus some [http://dev.w3.org/cvsweb/2001/palmagent/hcardTest.html hcardTest] materials
* [http://www.openpsa.org/ OpenPsa 2.x] CRM application uses hCard for all person listings. The widget is [http://www.midgard-project.org/midcom-permalink-922834501b71daad856f35ec593c7a6d reusable across Midgard CMS]
* [http://www.metonymie.com Emiliano Martínez Luque] has written an experimental [http://www.metonymie.com/hCard_extract/app.html hCard finder and structured search application] that finds hCards within a given set of URLs and returns the ones that match the specified criteria.

== Additional Applications ==
This section is '''informative'''.

There are numerous potential additional uses and applications for hCards on the Web. The following are merely a few thoughts and possibilities that folks have come up with:

* As an open standard/format for [http://www.gravatar.com/ Gravatars].
* Marking up individual authors of blog posts on a group blog
* Marking up people's names and URLs in a blogroll
* Any reference to people in blog posts (e.g. when citing them, or referencing them, or describing them, by name).
* ...

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

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

== Related Pages And Further Reading ==
* [[hcard-profile|hCard profile]] - The XMDP profile for hCard

This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. These thoughts, issues, and questions are kept in separate pages.

* [[hcard-brainstorming|hCard Brainstorming]] - where we are keeping our brainstorms and other explorations relating to hCard
* [[hcard-tests|hCard tests]] - a wiki page with actual embedded hCards to try parsing.
* [[hcard-faq|hCard FAQ]] - If you have any questions about hCard, check here, and if you don't find answers, add your questions!
* [[hcard-issues|hCard issues]] - Please add any issues with the specification to the issues page.
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].

hcard

2006-01-16T15:12:24Z

Emiliano: /* Implementations */

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

Use the [http://microformats.org/code/hcard/creator hCard creator], 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 ===
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. Multivalued 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 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.

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.

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

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

home: +1.415.555.1212

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

=== 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", except for the organization contact info case, [http://microformats.org/wiki/hcard#Organization_Contact_Info see below] 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 their firstname space lastname, or lastname comma firstname, or lastname comma firstinitial, or lastname space firstinitial.

==== Organization Contact Info ====

Contact info for a company or organization is a special case of the implied "N" optimization.

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

=== Root Class Name ===

The root class name for an hCard is "vcard".

=== Property List ===

This is the list of properties (and subproperties, in parantheses, 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
==== 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:
<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>

The following lists are ''informative''. See RFC2426 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, 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:

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

=== More Examples ===

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

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

=== New Examples ===
Please add new examples to this section.

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

=== Examples ===
* [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 the hcard format to mark-up the names and URLs of commentors on his 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.
* [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.
* [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://evdb.com EVDB], the Events and Venues Database, publishes all venue detail 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.ndunn.com Neil Dunn] has published his rather [http://www.ndunn.com/2005/10/7/hCard good looking hCard]
* [http://www.oliverbrown.me.uk/ Oliver Brown] has published his hCard.
* [http://www.paradigmproductions.org/contact/ Paradigm Productions] published a vcard as a ul (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.wolfsreign.com Steven Ametjan] has published his hCard on [http://www.wolfsreign.com/about/ his about page].
* [http://tagcamp.org/index.cgi?ContactList TagCamp contact list]
* [http://tantek.com/log 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].

=== Examples with some problems ===
* [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://www.kerihenare.com/ Keri Henare] has marked up his [http://www.kerihenare.com/contact/ contact info page] with hCard.
** (2005-09-27) PASSED
** (2005-11-01) hCard completely rewritten
** WARNING - type subproperty in classname
* [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 (ie, it doesn't contain lat/long)
* [http://landsbank.fo/#hCard Landsbanki Føroya]
** INVALID - using embedded rdf/xml invalidly
* [http://chrischerry.name/blog/contact/ Chris Cherry's contact page with his hCard]
** WARNING - uses class="cell" instead of <span class="type">cell</span>
* [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)
** where? more detail and I will fix. -- [[User:PhilWilson|PhilWilson]] 23:22, 11 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.shiftingpixel.com/about/ shifting pixel photoblog] has published an hCard.
** "organization_name" should be "organization-name" (s/_/-/), otherwise good --[[User:RyanKing|RyanKing]] 14:01, 5 Jan 2006 (PST)

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

* There is [http://flickr.com/photos/factoryjoe/68755089/ evidence of built-in hCard support in the Konqueror browser]. Specifically, Konqueror 3.5, in KDE 3.5 (kubuntu Breezy w/ update).
* There is [http://tagcamp.org/index.cgi?ContactList evidence of a kwiki plugin for hCards]. Update: the [http://svn.kwiki.org/cwest/Kwiki-hCard/ hCard kwiki plugin svn repository]. See the [http://microwiki.caseywest.com/index.cgi?hCard documentation of the hCard kwiki plugin].
* [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
* [http://www.stripytshirt.co.uk Duncan Walker] has built [http://www.stripytshirt.co.uk/features/firefox/smartzilla a Firefox extension] that gets hCard data from a webpage, uses Brian Suda's XSL (locally) to transform it to vcard format and opens the resulting .vcf file.
* [http://george.hotelling.net/90percent/ George] has written a [http://george.hotelling.net/90percent/geekery/greasemonkey_and_microformats.php Greasemonkey user script] that detects hCards and allows users to easily add them to their address book application. Relies on the X2V web service to do the conversion.
* [http://blogmatrix.blogmatrix.com/ David Janes] has written a [[Greasemonkey]] [http://www.blogmatrix.com/include/microformat-find.user.js script] that finds many microformat elements, including hCards, and [http://blog.davidjanes.com/mtarchives/2005_08.html#003376 provides a popup menu of actions]. The hCard to vCard conversion is done internally within the script. ''This does not work with FireFox 1.5+/GreaseMonkey 0.6.4+.''
* [http://diveintomark.org/ Mark Pilgrim] has also written an [http://diveintomark.org/projects/greasemonkey/hcard/ hCard parser Greasemonkey user script]. It is self-contained and does not rely on the X2V web service.
* [http://www.oliverbrown.me.uk/2005/09/03/a-working-microformats-extension-to-simplexml/ Oliver Brown] has written an "extension" to [http://www.php.net/simplexml SimpleXML] that gives simple access to hCard information in PHP 5.
* [http://thedredge.org/ Andrew D. Hume] has built a system (Wordpress plugin?) for [http://thedredge.org/2005/06/using-hcards-in-your-blog/ using hcards in your blog] to represent people leaving comments on blog posts.
* 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://dev.w3.org/cvsweb/2001/palmagent/ palmagent] is a collection of palmpilot and sidekick tools. It includes X2V derivatives xhtml2hcard.xsl and toICal.xsl plus some [http://dev.w3.org/cvsweb/2001/palmagent/hcardTest.html hcardTest] materials
* [http://www.openpsa.org/ OpenPsa 2.x] CRM application uses hCard for all person listings. The widget is [http://www.midgard-project.org/midcom-permalink-922834501b71daad856f35ec593c7a6d reusable across Midgard CMS]
* [http://www.metonymie.com Emiliano Martínez Luque] has written an experimental [http://www.metonymie.com/hCard_extract/app.html hCard finder and structured search application]

== Additional Applications ==
This section is '''informative'''.

There are numerous potential additional uses and applications for hCards on the Web. The following are merely a few thoughts and possibilities that folks have come up with:

* As an open standard/format for [http://www.gravatar.com/ Gravatars].
* Marking up individual authors of blog posts on a group blog
* Marking up people's names and URLs in a blogroll
* Any reference to people in blog posts (e.g. when citing them, or referencing them, or describing them, by name).
* ...

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

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

== Related Pages And Further Reading ==
* [[hcard-profile|hCard profile]] - The XMDP profile for hCard

This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. These thoughts, issues, and questions are kept in separate pages.

* [[hcard-brainstorming|hCard Brainstorming]] - where we are keeping our brainstorms and other explorations relating to hCard
* [[hcard-tests|hCard tests]] - a wiki page with actual embedded hCards to try parsing.
* [[hcard-faq|hCard FAQ]] - If you have any questions about hCard, check here, and if you don't find answers, add your questions!
* [[hcard-issues|hCard issues]] - Please add any issues with the specification to the issues page.
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].

Main Page

2005-09-06T00:27:00Z

Emiliano: /* Exploratory discussions */

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

But First:

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

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

== Introduction ==

What are microformats? See the [http://microformats.org/about/ about page] for an overview, and the [[introduction]] page for more info. Recent [[press]] and [[presentations]] are also a good place for some background reading as well.

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

== Drafts ==
* [[hreview|hReview]]
* [[rel-directory]]
* [[rel-enclosure]]
* [[relpayment-research | rel-payment]]
* [[robots-exclusion|Robots Exclusion]]
* [[xfolk]]

== Design Patterns ==

* [[datetime-design-pattern]]

== Exploratory discussions ==
*[[blog-description-format]]
*[[blog-post-formats]]
*[[blog-post-brainstorming]]
*[[citation-brainstorming]]
*[[cite|Planning pages for a citation microformat]]
*[[comments-formats]]
*[[directory-inclusion-examples]] (see also [[directory-inclusion-formats]])
*[[genealogy-formats]]
*[[last-modified-examples]]
*[[listing-examples]] (see also [[listing-formats]], [[listing-brainstorming]])
*[[location-formats]]
*[[media-metadata-examples]]
*[[other-formats]]
*[[requirements-testing]]
*[[resume-brainstorming]]
*[[resume-formats]]
*[[wiki-formats]]
*[[xmdp-brainstorming]] (see also [[xmdp-faq]])

== Tools & Test Cases ==

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.

*[[selected-test-cases-from-the-web]]
*[[microformats-viewers-and-editors]]

== shared work areas ==
* [[buttons]] (new!)
* [[to-do]]
* [[marked-for-deletion]]

listing-brainstorming

2005-09-06T00:24:51Z

Emiliano: /* Some initial thoughts */

=Listing Brainstorming=

==Some initial thoughts==
* The format should at is most basic be easily implemented by current listing sites without having to modify their existing setups (ie: tinkering with their SQL). For example: http://www.villagevoice.com/classifieds/index.php?page=ads&category=Employment&sort=1&database=0&a=0&class=4025 has a very simple data structure, one can imagine this simple data structure coming from an SQL database. If they need to alter their SQL to adapt to the microformat it will not be adopted (or at least not quickly). Ideally all it would took for current sites to adopt it is just a redesign.
* The format should be extendable enough to allow for specific data to be extracted from it so that specialized services ( format specific aggregators, social aggregators, collaborative filtering, discovery agents ) could be built on top of it.
* The format should be flexible enough to be easily added to current CMS and blogging systems.
* The format should be flexible enough to not interfeer with existing business models of stablished web based listing sites. For example a Job Listings site may get revenue from commissions on actual prospects found and contracted through their site. If the actual way of contacting the prospect is required in the format (rather than a link to the actual listing on their site), they might be weary of implementing the microformat (since it would take them out the loop, so to say). A similar argument could be made for other types of listings sites. However if they can implement a simple data structure that can then be traced to their sites, they would probably implement it since it would help in the discovery process of their listings (through aggregators or crawlers).

== A Basic Data Structure ==
* At it´s most basic web based listing schemas could be narrowed to:
** title
** description (Some sites don´t even seem to have Title)
** listing date
** contact info. (hCard might be used for this)
* Contextual or Implied Info.
** Regardless of the actual schemas that can be extracted from the html pages there is some information that is implied either contextually or by navigation in all of the examples found. For Example:
*** A listing on ebay.de implies ( contextually ) that the actual location of the listing in itself is in the country of Germany. Other examples: paris.craiglists.org, a classified ad on nytimes.com or (NY) globo.com.br (Brazil) or www.timeout.com (London).
*** A category or "Type" of the listing in itself is generally implied by navigation through the sites. For example: When accesing craiglist.org one chooses the type of listing one wants to see ( housing > housing wanted ). Some sites have specialized data structures depending on the type of listing (For example, it´s fairly common for Vehicles for sale to have a field for brand, model, year.)
** This suggests that location and type should be included in the base format. (Deciding on this may be quite tricky. Particullarly Types, since locations can be extracted from Contact. )

== Extending the Base Structure By Listing Type==
* Once a basic format is decided, it could be extended to more specific types of data structures.
** Type For Sale
*** Base
**** title could map to product name. (This mapping thing is just an idea, but it seems to be fairly common)
**** description could map to product description.
**** product category (may be part of the basic format category. No idea how to go with this.)
**** product condition (Used|New)
*** Optional
**** price ammount
**** price currency (currency is either specified or implied contextually when naming a Price. A price could be considered an specific ammount of an specific currency.)
**** photo (Optional, might be more than one *)
**** duration or expiry date of the offer.
**** availability (If there is more than one for sale, or even none.)
** Type For Sale, Product Category = vehicle (May extend for sale)
*** brand
*** model
*** year
** Type Wanted
*** title could map to product name.
*** description could map to product description.
*** duration or expiry date.
** Type Job Offer
*** title could map to job category (seems to be a common practice)
*** description could map to job description
*** requirements
*** contract type (part time| full time | temp)
*** contact could map to company or recruiter

* More extended types should be considered...

listing-brainstorming

2005-09-06T00:24:21Z

Emiliano: /* A Basic Data Structure */

=Listing Brainstorming=

==Some initial thoughts==
* The format should at is most basic be easily implemented by current listing sites without having to modify their existing setups (ie: tinkering with their SQL). For example: http://www.villagevoice.com/classifieds/index.php?page=ads&category=Employment&sort=1&database=0&a=0&class=4025 has a very simple data structure, one can imagine this simple data structure coming from an SQL database. If they need to alter their SQL to adapt to the microformat it will not be adopted (or at least not quickly). Ideally all it would took for current sites to adopt it is just a redesign.
* The format should be extendable enough to allow for specific data to be extracted from it so that specialized services ( format specific aggregators, social aggregators, collaborative filtering, discovery agents ) could be built on top of it.
* The format should be flexible enough to be easily added to current CMS and blogging systems.
* The format should be flexible enough to not interfeer with existing business models of stablished web based listing sites. For example a Job Listings site may get revenue from commissions on actual prospects found and contracted through their site. If the actual way of contacting the prospect is required in the format (rather than a link to the actual listing on their site), they might be weary of implementing the microformat (since it would take them out the loop, so to say). A similar argument could be made for other types of listings sites. However if they can implement a simple data structure that can then be traced to their sites, they would probably implement it since it would help in the discovery process of their listings (through aggregators or crawlers). <strong>--- This is just a thought ---</strong>

== A Basic Data Structure ==
* At it´s most basic web based listing schemas could be narrowed to:
** title
** description (Some sites don´t even seem to have Title)
** listing date
** contact info. (hCard might be used for this)
* Contextual or Implied Info.
** Regardless of the actual schemas that can be extracted from the html pages there is some information that is implied either contextually or by navigation in all of the examples found. For Example:
*** A listing on ebay.de implies ( contextually ) that the actual location of the listing in itself is in the country of Germany. Other examples: paris.craiglists.org, a classified ad on nytimes.com or (NY) globo.com.br (Brazil) or www.timeout.com (London).
*** A category or "Type" of the listing in itself is generally implied by navigation through the sites. For example: When accesing craiglist.org one chooses the type of listing one wants to see ( housing > housing wanted ). Some sites have specialized data structures depending on the type of listing (For example, it´s fairly common for Vehicles for sale to have a field for brand, model, year.)
** This suggests that location and type should be included in the base format. (Deciding on this may be quite tricky. Particullarly Types, since locations can be extracted from Contact. )

== Extending the Base Structure By Listing Type==
* Once a basic format is decided, it could be extended to more specific types of data structures.
** Type For Sale
*** Base
**** title could map to product name. (This mapping thing is just an idea, but it seems to be fairly common)
**** description could map to product description.
**** product category (may be part of the basic format category. No idea how to go with this.)
**** product condition (Used|New)
*** Optional
**** price ammount
**** price currency (currency is either specified or implied contextually when naming a Price. A price could be considered an specific ammount of an specific currency.)
**** photo (Optional, might be more than one *)
**** duration or expiry date of the offer.
**** availability (If there is more than one for sale, or even none.)
** Type For Sale, Product Category = vehicle (May extend for sale)
*** brand
*** model
*** year
** Type Wanted
*** title could map to product name.
*** description could map to product description.
*** duration or expiry date.
** Type Job Offer
*** title could map to job category (seems to be a common practice)
*** description could map to job description
*** requirements
*** contract type (part time| full time | temp)
*** contact could map to company or recruiter

* More extended types should be considered...

listing-brainstorming

2005-09-03T01:31:36Z

Emiliano: My initial ideas on this.

=Listing Brainstorming=

==Some initial thoughts==
* The format should at is most basic be easily implemented by current listing sites without having to modify their existing setups (ie: tinkering with their SQL). For example: http://www.villagevoice.com/classifieds/index.php?page=ads&category=Employment&sort=1&database=0&a=0&class=4025 has a very simple data structure, one can imagine this simple data structure coming from an SQL database. If they need to alter their SQL to adapt to the microformat it will not be adopted (or at least not quickly). Ideally all it would took for current sites to adopt it is just a redesign.
* The format should be extendable enough to allow for specific data to be extracted from it so that specialized services ( format specific aggregators, social aggregators, collaborative filtering, discovery agents ) could be built on top of it.
* The format should be flexible enough to be easily added to current CMS and blogging systems.
* The format should be flexible enough to not interfeer with existing business models of stablished web based listing sites. For example a Job Listings site may get revenue from commissions on actual prospects found and contracted through their site. If the actual way of contacting the prospect is required in the format (rather than a link to the actual listing on their site), they might be weary of implementing the microformat (since it would take them out the loop, so to say). A similar argument could be made for other types of listings sites. However if they can implement a simple data structure that can then be traced to their sites, they would probably implement it since it would help in the discovery process of their listings (through aggregators or crawlers). <strong>--- This is just a thought ---</strong>

== A Basic Data Structure ==
* At it´s most basic web based listing schemas could be narrowed to:
** title
** description (Some sites don´t even seem to have Title)
** listing date
** contact info. (hCard might be used for this)
* Contextual or Implied Info.
** Regardless of the actual schemas that can be extracted from the html pages there is some information that is implied either contextually or by navigation in all of the examples found. For Example:
*** A listing on ebay.de implies ( contextually ) that the actual location of the listing in itself is in the country of Germany. Other examples: paris.craiglists.org, a classified ad on nytimes.com or (NY) globo.com.br (Brazil) or www.timeout.com (London).
*** A category or "Type" of the listing in itself is generally implied by navigation through the sites. For example: When accesing craiglist.org one chooses the type of listing one wants to see ( housing > housing wanted ). Some sites have specialized data structures depending on the type of listing (For example, it´s fairly common for Vehicles for sale to have a field for brand, model, year.)
** This suggests that location and type should be included in the base format. (Deciding on this may be quite tricky.)

== Extending the Base Structure By Listing Type==
* Once a basic format is decided, it could be extended to more specific types of data structures.
** Type For Sale
*** Base
**** title could map to product name. (This mapping thing is just an idea, but it seems to be fairly common)
**** description could map to product description.
**** product category (may be part of the basic format category. No idea how to go with this.)
**** product condition (Used|New)
*** Optional
**** price ammount
**** price currency (currency is either specified or implied contextually when naming a Price. A price could be considered an specific ammount of an specific currency.)
**** photo (Optional, might be more than one *)
**** duration or expiry date of the offer.
**** availability (If there is more than one for sale, or even none.)
** Type For Sale, Product Category = vehicle (May extend for sale)
*** brand
*** model
*** year
** Type Wanted
*** title could map to product name.
*** description could map to product description.
*** duration or expiry date.
** Type Job Offer
*** title could map to job category (seems to be a common practice)
*** description could map to job description
*** requirements
*** contract type (part time| full time | temp)
*** contact could map to company or recruiter

* More extended types should be considered...

listing-examples

2005-08-31T02:02:54Z

Emiliano: /* Accomodation */

= Listing Examples =

This is an exploratory page to document listing (e.g. For Sale, Wanted) examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary feed formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed listings microformat.

== Authors ==

* Trevor O'Reilly
* Emiliano Martínez Luque

== Examples ==

=== For Sale ===

* Craigslist
** http://www.craigslist.org/sss/
** email
** duration (implied)
** date
** category
** title
** description
** location
** condition
** images
** price
** availability

* Amazon
** http://www.amazon.com/exec/obidos/ASIN/0735712018

* Powazek
** http://www.powazek.com/2005/01/000485.html
** email
** date
** title
** description
** image
** location
** condition
** price
** availability

* 37signals
** http://www.37signals.com/svn/archives2/for_sale_hp_laserjet_4000n_and_a_1ghz_powermac_g4_tower.php
** email
** date
** title
** description
** location
** condition
** price
** availability

* Mercado Libre
** http://www.mercadolibre.com.ar/jm/item?site=MLA&id=17910319
** http://www.mercadolibre.com.ar/jm/item?site=MLA&id=17902804
** price ammount
** price currency
** financing options (? may or may not exist)
** merchant/seller name
** merchant/seller rating (Within Mercado Libre)
** product condition (Used|New)
** location (Province)
** product category (Implied by Navigation)
** product name
** product photo
** product description
** offer ending date
** item# (MercadoLibre ID)

* Segunda Mano
** http://www.segundamano.com.ar/detalles/asp/informatica_y_comunicaciones/camaras_digitales/venta/13083319.htm
** http://www.segundamano.com.ar/detalles/asp/informatica_y_comunicaciones/camaras_digitales/venta/13084677.htm
** http://www.segundamano.com.ar/detalles/asp/automotores/motos/venta/13086663.htm
** price ammount
** price currency
** product category (Implied by Navigation)
** product description
** seller telephone
** listing date
** province (?)
** city (?)
** product specific data ( ie: Model, Year, Brand for Cars or Motorcycles. Varies by Product type. )

* Expats.cz
** http://www.expats.cz/prague/t-71854.html
** title
** price ammount
** price currency (might be CZK, USD, EUR)
** product description
** product condition
** email
** date

* Alibaba.com
** http://aux.en.alibaba.com/offerdetail/50425885/Sell_Split_Wall_Mounted_Air_Conditioner.html
** product name
** product photo
** product category
** description/features
** listing date
** expiry date
** company name
** contact person
** address
** zip
** telephone
** fax
** website

=== Wanted ===

* eBay
** http://www.wantitnow.ebay.com
** category
** item number
** buyer nickname
** feedback
** date
** duration
** title
** description
** location
** condition
** price

* Craigslist
** http://www.craigslist.org/wan/
** email
** duration
** date
** category
** title
** description
** location
** condition
** images
** price

* Alibaba.com
** http://www.alibaba.com/manufacturer/13083795/Buy_Air_Conditioner.html
** title
** description
** listing date
** expiry date
** contact info (implied, must login)

=== Real Estate ===

* Craigslist
** http://www.craigslist.org/hhh/
** category (rent, sale, temp)
** date
** duration (implied)
** contact info
** location
** title
** description
** size
*** bedrooms
** rent
** photos
** pet policy
** fee/no-fee
** broker/non-broker

* MetroRent.com
** http://www.rent.com
** contact info
** location
** title
** description
** photos
** size
*** bedrooms
*** bathrooms
** rent
** lease terms

* Rent.com
** http://www.rent.com
** contact info
** location
** title
** description
** photos
** size
*** bedrooms
*** bathrooms
*** square footage
** rent
** amenities
** lease terms

=== Jobs ===

* Craigslist
** http://www.craigslist.org/jjj/
** category
** contract terms
** date
** duration (implied)
** contact info
** location
** title
** description
** principals/recruiters

* Infojobs.net
** http://www.infojobs.net/visualizar_oferta.ij/of_codigo=25152424536981905650024953746
** offer title
*** offer date
*** offer reference
*** company name
**** company url
**** company number of workers
**** company headquarters
**** company description/filosophy
** location
*** location city
*** location country
*** location province/state
** job description
*** job title
*** job category
*** department
*** vacancies
*** job offer description
** requirements
*** minimal estudies
*** minimal experience
*** place of residency (where the candidate must live)
** contract
*** journal (full day| part time)

* InfoEmprego.com.br
** http://www.infoemprego.com.br/OfertaVisualizar.aspx?id=546853
** Offer title
** location (city - state - country)
** description
** company size
** company sector (of the job offer)
** company type
** offer description
*** sector
*** specialization
*** vacancies
** requirements
*** studies
*** professional experience
** Offering
*** salary (might not be shown it seems)
*** contract type

=== Accomodation ===

* Backpackers.com
** http://www.backpackers.com/Europe/Netherlands/Amsterdam/classifieds/rooms_&_shared/5718.html
** title
** listing date
** email
** city
** price ammount
** contact phone (Other contacting options)
** location (neighbourghood?)
** description (I'll add schema that seems to be inside the description)
*** number of rooms
*** rooms descriptions
*** from date
*** to date
** listing modified date
** ok for other to contact lister (boolean)

* Expatriates.com
** http://www.expatriates.com/cls/483203.html
** title
*** price ammount
*** term (per day, week, month)
*** number of rooms
*** room/apartment description
** email
** listing date
** category
** region
** description

== See Also ==

[[listing-formats]]

listing-examples

2005-08-31T02:00:45Z

Emiliano: /* Accomodation */ Added Expatriates.com

= Listing Examples =

This is an exploratory page to document listing (e.g. For Sale, Wanted) examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary feed formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed listings microformat.

== Authors ==

* Trevor O'Reilly
* Emiliano Martínez Luque

== Examples ==

=== For Sale ===

* Craigslist
** http://www.craigslist.org/sss/
** email
** duration (implied)
** date
** category
** title
** description
** location
** condition
** images
** price
** availability

* Amazon
** http://www.amazon.com/exec/obidos/ASIN/0735712018

* Powazek
** http://www.powazek.com/2005/01/000485.html
** email
** date
** title
** description
** image
** location
** condition
** price
** availability

* 37signals
** http://www.37signals.com/svn/archives2/for_sale_hp_laserjet_4000n_and_a_1ghz_powermac_g4_tower.php
** email
** date
** title
** description
** location
** condition
** price
** availability

* Mercado Libre
** http://www.mercadolibre.com.ar/jm/item?site=MLA&id=17910319
** http://www.mercadolibre.com.ar/jm/item?site=MLA&id=17902804
** price ammount
** price currency
** financing options (? may or may not exist)
** merchant/seller name
** merchant/seller rating (Within Mercado Libre)
** product condition (Used|New)
** location (Province)
** product category (Implied by Navigation)
** product name
** product photo
** product description
** offer ending date
** item# (MercadoLibre ID)

* Segunda Mano
** http://www.segundamano.com.ar/detalles/asp/informatica_y_comunicaciones/camaras_digitales/venta/13083319.htm
** http://www.segundamano.com.ar/detalles/asp/informatica_y_comunicaciones/camaras_digitales/venta/13084677.htm
** http://www.segundamano.com.ar/detalles/asp/automotores/motos/venta/13086663.htm
** price ammount
** price currency
** product category (Implied by Navigation)
** product description
** seller telephone
** listing date
** province (?)
** city (?)
** product specific data ( ie: Model, Year, Brand for Cars or Motorcycles. Varies by Product type. )

* Expats.cz
** http://www.expats.cz/prague/t-71854.html
** title
** price ammount
** price currency (might be CZK, USD, EUR)
** product description
** product condition
** email
** date

* Alibaba.com
** http://aux.en.alibaba.com/offerdetail/50425885/Sell_Split_Wall_Mounted_Air_Conditioner.html
** product name
** product photo
** product category
** description/features
** listing date
** expiry date
** company name
** contact person
** address
** zip
** telephone
** fax
** website

=== Wanted ===

* eBay
** http://www.wantitnow.ebay.com
** category
** item number
** buyer nickname
** feedback
** date
** duration
** title
** description
** location
** condition
** price

* Craigslist
** http://www.craigslist.org/wan/
** email
** duration
** date
** category
** title
** description
** location
** condition
** images
** price

* Alibaba.com
** http://www.alibaba.com/manufacturer/13083795/Buy_Air_Conditioner.html
** title
** description
** listing date
** expiry date
** contact info (implied, must login)

=== Real Estate ===

* Craigslist
** http://www.craigslist.org/hhh/
** category (rent, sale, temp)
** date
** duration (implied)
** contact info
** location
** title
** description
** size
*** bedrooms
** rent
** photos
** pet policy
** fee/no-fee
** broker/non-broker

* MetroRent.com
** http://www.rent.com
** contact info
** location
** title
** description
** photos
** size
*** bedrooms
*** bathrooms
** rent
** lease terms

* Rent.com
** http://www.rent.com
** contact info
** location
** title
** description
** photos
** size
*** bedrooms
*** bathrooms
*** square footage
** rent
** amenities
** lease terms

=== Jobs ===

* Craigslist
** http://www.craigslist.org/jjj/
** category
** contract terms
** date
** duration (implied)
** contact info
** location
** title
** description
** principals/recruiters

* Infojobs.net
** http://www.infojobs.net/visualizar_oferta.ij/of_codigo=25152424536981905650024953746
** offer title
*** offer date
*** offer reference
*** company name
**** company url
**** company number of workers
**** company headquarters
**** company description/filosophy
** location
*** location city
*** location country
*** location province/state
** job description
*** job title
*** job category
*** department
*** vacancies
*** job offer description
** requirements
*** minimal estudies
*** minimal experience
*** place of residency (where the candidate must live)
** contract
*** journal (full day| part time)

* InfoEmprego.com.br
** http://www.infoemprego.com.br/OfertaVisualizar.aspx?id=546853
** Offer title
** location (city - state - country)
** description
** company size
** company sector (of the job offer)
** company type
** offer description
*** sector
*** specialization
*** vacancies
** requirements
*** studies
*** professional experience
** Offering
*** salary (might not be shown it seems)
*** contract type

=== Accomodation ===

* Backpackers.com
** http://www.backpackers.com/Europe/Netherlands/Amsterdam/classifieds/rooms_&_shared/5718.html
** title
** listing date
** email
** city
** price ammount
** contact phone (Other contacting options)
** location (neighbourghood?)
** description (I'll add schema that seems to be inside the description)
*** number of rooms
*** rooms descriptions
*** from date
*** to date
** listing modified date
** ok for other to contact lister (boolean)

* Expatriates.com
** http://www.expatriates.com/cls/483203.html
** title
*** price ammount
*** price temporary term (per day, week, month)
*** number of rooms
*** room/apartment description
** email
** listing date
** category
** region
** description

== See Also ==

[[listing-formats]]

listing-examples

2005-08-31T01:39:15Z

Emiliano: /* Jobs */ Added infoemprego.com.br brazilian job site.

listing-examples

2005-08-31T01:18:55Z

Emiliano: /* Jobs */ Added infojobs.net (Spanish job listing´s site)

= Listing Examples =

This is an exploratory page to document listing (e.g. For Sale, Wanted) examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary feed formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed listings microformat.

== Authors ==

* Trevor O'Reilly
* Emiliano Martínez Luque

== Examples ==

=== For Sale ===

* Craigslist
** http://www.craigslist.org/sss/
** email
** duration (implied)
** date
** category
** title
** description
** location
** condition
** images
** price
** availability

* Amazon
** http://www.amazon.com/exec/obidos/ASIN/0735712018

* Powazek
** http://www.powazek.com/2005/01/000485.html
** email
** date
** title
** description
** image
** location
** condition
** price
** availability

* 37signals
** http://www.37signals.com/svn/archives2/for_sale_hp_laserjet_4000n_and_a_1ghz_powermac_g4_tower.php
** email
** date
** title
** description
** location
** condition
** price
** availability

* Mercado Libre
** http://www.mercadolibre.com.ar/jm/item?site=MLA&id=17910319
** http://www.mercadolibre.com.ar/jm/item?site=MLA&id=17902804
** price ammount
** price currency
** financing options (? may or may not exist)
** merchant/seller name
** merchant/seller rating (Within Mercado Libre)
** product condition (Used|New)
** location (Province)
** product category (Implied by Navigation)
** product name
** product photo
** product description
** offer ending date
** item# (MercadoLibre ID)

* Segunda Mano
** http://www.segundamano.com.ar/detalles/asp/informatica_y_comunicaciones/camaras_digitales/venta/13083319.htm
** http://www.segundamano.com.ar/detalles/asp/informatica_y_comunicaciones/camaras_digitales/venta/13084677.htm
** http://www.segundamano.com.ar/detalles/asp/automotores/motos/venta/13086663.htm
** price ammount
** price currency
** product category (Implied by Navigation)
** product description
** seller telephone
** listing date
** province (?)
** city (?)
** product specific data ( ie: Model, Year, Brand for Cars or Motorcycles. Varies by Product type. )

* Expats.cz
** http://www.expats.cz/prague/t-71854.html
** title
** price ammount
** price currency (might be CZK, USD, EUR)
** product description
** product condition
** email
** date

* Alibaba.com
** http://aux.en.alibaba.com/offerdetail/50425885/Sell_Split_Wall_Mounted_Air_Conditioner.html
** product name
** product photo
** product category
** description/features
** listing date
** expiry date
** company name
** contact person
** address
** zip
** telephone
** fax
** website

=== Wanted ===

* eBay
** http://www.wantitnow.ebay.com
** category
** item number
** buyer nickname
** feedback
** date
** duration
** title
** description
** location
** condition
** price

* Craigslist
** http://www.craigslist.org/wan/
** email
** duration
** date
** category
** title
** description
** location
** condition
** images
** price

* Alibaba.com
** http://www.alibaba.com/manufacturer/13083795/Buy_Air_Conditioner.html
** title
** description
** listing date
** expiry date
** contact info (implied, must login)

=== Real Estate ===

* Craigslist
** http://www.craigslist.org/hhh/
** category (rent, sale, temp)
** date
** duration (implied)
** contact info
** location
** title
** description
** size
*** bedrooms
** rent
** photos
** pet policy
** fee/no-fee
** broker/non-broker

* MetroRent.com
** http://www.rent.com
** contact info
** location
** title
** description
** photos
** size
*** bedrooms
*** bathrooms
** rent
** lease terms

* Rent.com
** http://www.rent.com
** contact info
** location
** title
** description
** photos
** size
*** bedrooms
*** bathrooms
*** square footage
** rent
** amenities
** lease terms

=== Jobs ===

* Craigslist
** http://www.craigslist.org/jjj/
** category
** contract terms
** date
** duration (implied)
** contact info
** location
** title
** description
** principals/recruiters

* Infojobs.net
** http://www.infojobs.net/visualizar_oferta.ij/of_codigo=25152424536981905650024953746
** offer title
*** offer date
*** offer reference
*** company name
**** company url
**** company number of workers
**** company headquarters
**** company description/filosophy
** location
*** location city
*** location country
*** location province/state
** job description
*** job title
*** job category
*** department
*** vacancies
*** job offer description
** requisites (is this the right term in english?)
*** minimal estudies
*** minimal experience
*** place of residency (where the candidate must live)
** contract
*** journal (full day| part time)

=== Accomodation ===

* Backpackers.com
** http://www.backpackers.com/Europe/Netherlands/Amsterdam/classifieds/rooms_&_shared/5718.html
** title
** listing date
** email
** city
** price ammount
** contact phone (Other contacting options)
** location (neighbourghood?)
** description (I'll add schema that seems to be inside the description)
*** number of rooms
*** rooms descriptions
*** from date
*** to date
** listing modified date
** ok for other to contact lister (boolean)

== See Also ==

[[listing-formats]]

listing-examples

2005-08-31T01:03:32Z

Emiliano: /* For Sale */ Took country out since they now have different hostnames for different countries

listing-examples

2005-08-31T01:00:58Z

Emiliano: Moved backpackers to Accomodation

listing-examples

2005-08-30T23:03:12Z

Emiliano: /* For Sale */

listing-examples

2005-08-29T19:13:44Z

Emiliano:

= Listing Examples =

This is an exploratory page to document listing (e.g. For Sale, Wanted) examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary feed formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed listings microformat.

== Contributors ==

* Trevor O'Reilly
* Emiliano Martínez Luque

== Examples in the Wild ==

=== For Sale ===

==== Craigslist ====
* http://www.craigslist.org/sss/
* email
* duration
* date
* category
* title
* description
* location
* condition
* images
* price
* availability

==== Amazon ====
* http://www.amazon.com/exec/obidos/ASIN/0735712018

==== Powazek ====
* http://www.powazek.com/2005/01/000485.html
* email
* date
* title
* description
* image
* location
* condition
* price
* availability

==== 37signals ====
* http://www.37signals.com/svn/archives2/for_sale_hp_laserjet_4000n_and_a_1ghz_powermac_g4_tower.php
* email
* date
* title
* description
* location
* condition
* price
* availability

==== Mercado Libre ====
* http://www.mercadolibre.com.ar/jm/item?site=MLA&id=17910319
* http://www.mercadolibre.com.ar/jm/item?site=MLA&id=17902804
* price ammount
* price currency
* financing options (? may or may not exist)
* merchant/seller name
* merchant/seller rating (Within Mercado Libre)
* product condition (Used|New)
* location (Province)
* country (Implied by Navigation. Country is selected when accesing mercadolibre.com)
* product name
* product photo
* product description
* offer ending date
* item# (MercadoLibre ID)

==== Segunda Mano ====
* http://www.segundamano.com.ar/detalles/asp/informatica_y_comunicaciones/cámaras_digitales/venta/13083319.htm
* http://www.segundamano.com.ar/detalles/asp/informatica_y_comunicaciones/cámaras_digitales/venta/13084677.htm
* http://www.segundamano.com.ar/detalles/asp/automotores/motos/venta/13086663.htm
* price ammount
* price currency
* product description
* seller telephone
* listing date
* province (?)
* city (?)
* country (Implied by Navigation. Country is selected when accesing segundamano.com)
* product specific data ( ie: Model, Year, Brand for Cars or Motorcycles. Varies by Product type. )

==== Expats.cz ====
* http://www.expats.cz/prague/t-71854.html
* price ammount
* price currency (might be CZK, USD, EUR)
* product description
* product condition
* email
* date

==== Alibaba.com ====
* http://aux.en.alibaba.com/offerdetail/50425885/Sell_Split_Wall_Mounted_Air_Conditioner.html
* product name
* product photo
* product category
* description/features
* listing date
* expiry date
* company name
* contact person
* address
* zip
* telephone
* fax
* website

=== Wanted ===

==== eBay ====
* http://www.wantitnow.ebay.com
* category
* item number
* buyer nickname
* feedback
* date
* duration
* title
* description
* location
* condition
* price

==== Craigslist ====
* http://www.craigslist.org/wan/
* email
* duration
* date
* category
* title
* description
* location
* condition
* images
* price

==== Alibaba.com ====
* http://www.alibaba.com/manufacturer/13083795/Buy_Air_Conditioner.html
* title
* description
* listing date
* expiry date
* contact info (implied, must login)

== Previous Schemas and Formats ==

==== eBay ====
* http://developer.ebay.com/DevZone/XML/docs/WSDL/index.htm
* http://pages.ebay.com/help/sell/export-structure.html

==== Amazon ====
* http://www.amazon.com/gp/aws/sdk/?v=2005%2d07%2d26&s=AWSEcommerceService
* http://www.amazon.com/gp/aws/sdk/main.html/103-0842473-2772652?s=AWSEcommerceService&v=2005-07-26&p=ApiReference/SmallResponseGroup
* http://www.amazon.com/gp/aws/sdk/main.html/103-0842473-2772652?s=AWSEcommerceService&v=2005-07-26&p=ApiReference/OfferFullResponseGroup

==== Micropayment Markup ====
* http://www.w3.org/TR/Micropayment-Markup/

==== FOAF-Shop ====
* http://rdfweb.org/people/danbri/rdfweb/danbri-foafshop.rdf

==== Froogle ====
* http://www.google.com/froogle/merchants/advanced_feed_instructions.html

==== Yahoo Shopping ====
* http://productsubmit.adcentral.yahoo.com/sspi/us/spec/

==== Become.com ====
* http://www.become.com/merchant/Product_Feed_Specification_5_05_05.pdf

==== MySimon ====
* http://shopper.cnet.com/html/partners/a_feed.html#guidelines

==== LinkShare Datafeeds ====
* http://www.linkshare.com/rc/sample_mfile.shtml (Example Feed)

== Related Initiatives ==

The following is a list of related e-business initiatives. While the scope of these projects is much larger than the problem addressed here, they may provide good reference points for property and process naming conventions. Included primarily for completeness.

* [http://www.w3.org/ECommerce/ W3C Electronic Commerce Interest Group] The role of W3C is to focus on core infrastructure technologies for Electronic Commerce and identify common infrastructure needed in this area.

* [http://www.commerce.net CommerceNet] CommerceNet is a non-profit membership organization meeting the evolving needs of companies doing electronic commerce.

* [http://www.ebxml.org ebXML] ebXML (Electronic Business using eXtensible Markup Language), is a modular suite of specifications that enables enterprises of any size and in any geographical location to conduct business over the Internet.

* [http://www.biztalk.org BizTalk] The BizTalk Framework is an XML framework for application integration and electronic commerce. It includes a design framework for implementing an XML schema and a set of XML tags used in messages sent between applications.

* [http://xml.coverpages.org/ecml.html ECML] The Electronic Commerce Modeling Language provides a simple set of guidelines for web merchants that will enable digital wallets from multiple vendors to automate the exchange of information between users and merchants.

* [http://www.iotp.org IOTP] The Open Trading Protocol was developed by a number of organizations, working cooperatively to make widespread Internet trading a convenient and secure reality.

* [http://www.udef.org UDEF] The Universal Data Element Framework is a cross-industry metadata identification strategy designed to facilitate convergence and interoperability among e-business and other standards.

* [http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ubl UBL] UBL, the Universal Business Language, is the product of an international effort to define a royalty-free library of standard electronic XML business documents such as purchase orders and invoices.

* [http://www.rosettanet.org RosettaNet] A self-funded, non-profit organization, RosettaNet is a consortium of major Computer and Consumer Electronics, Electronic Components, Semiconductor Manufacturing, Telecommunications and Logistics companies working to create and implement industry-wide, open e-business process standards. These standards form a common e-business language, aligning processes between supply chain partners on a global basis.

listing-examples

2005-08-29T19:09:41Z

Emiliano: /* alibaba.com */

= Listing Examples =

This is an exploratory page to document listing (e.g. For Sale, Wanted) examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary feed formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed listings microformat.

== Contributors ==

* Trevor O'Reilly
* Emiliano Martínez Luque

== Examples in the Wild ==

=== For Sale ===

==== Craigslist ====
* http://www.craigslist.org/sss/
* email
* duration
* date
* category
* title
* description
* location
* condition
* images
* price
* availability

==== Amazon ====
* http://www.amazon.com/exec/obidos/ASIN/0735712018

==== Powazek ====
* http://www.powazek.com/2005/01/000485.html
* email
* date
* title
* description
* image
* location
* condition
* price
* availability

==== 37signals ====
* http://www.37signals.com/svn/archives2/for_sale_hp_laserjet_4000n_and_a_1ghz_powermac_g4_tower.php
* email
* date
* title
* description
* location
* condition
* price
* availability

==== Mercado Libre ====
* http://www.mercadolibre.com.ar/jm/item?site=MLA&id=17910319
* http://www.mercadolibre.com.ar/jm/item?site=MLA&id=17902804
* price ammount
* price currency
* financing options (? may or may not exist)
* merchant/seller name
* merchant/seller rating (Within Mercado Libre)
* product condition (Used|New)
* location (Province)
* country (Implied by Navigation. Country is selected when accesing mercadolibre.com)
* product name
* product photo
* product description
* offer ending date
* item# (MercadoLibre ID)

==== Segunda Mano ====
* http://www.segundamano.com.ar/detalles/asp/informatica_y_comunicaciones/cámaras_digitales/venta/13083319.htm
* http://www.segundamano.com.ar/detalles/asp/informatica_y_comunicaciones/cámaras_digitales/venta/13084677.htm
* http://www.segundamano.com.ar/detalles/asp/automotores/motos/venta/13086663.htm
* price ammount
* price currency
* product description
* seller telephone
* publish date
* province (?)
* city (?)
* country (Implied by Navigation. Country is selected when accesing segundamano.com)
* product specific data ( ie: Model, Year, Brand for Cars or Motorcycles. Varies by Product type. )

==== Expats.cz ====
* http://www.expats.cz/prague/t-71854.html
* price ammount
* price currency (might be CZK, USD, EUR)
* product description
* product condition
* email
* date

==== Alibaba.com ====
* http://aux.en.alibaba.com/offerdetail/50425885/Sell_Split_Wall_Mounted_Air_Conditioner.html
* product name
* product photo
* product category
* description/features
* listing date
* expiry date
* company name
* contact person
* address
* zip
* telephone
* fax
* website

=== Wanted ===

==== eBay ====
* http://www.wantitnow.ebay.com
* category
* item number
* buyer nickname
* feedback
* date
* duration
* title
* description
* location
* condition
* price

==== Craigslist ====
* http://www.craigslist.org/wan/
* email
* duration
* date
* category
* title
* description
* location
* condition
* images
* price

== Previous Schemas and Formats ==

==== eBay ====
* http://developer.ebay.com/DevZone/XML/docs/WSDL/index.htm
* http://pages.ebay.com/help/sell/export-structure.html

==== Amazon ====
* http://www.amazon.com/gp/aws/sdk/?v=2005%2d07%2d26&s=AWSEcommerceService
* http://www.amazon.com/gp/aws/sdk/main.html/103-0842473-2772652?s=AWSEcommerceService&v=2005-07-26&p=ApiReference/SmallResponseGroup
* http://www.amazon.com/gp/aws/sdk/main.html/103-0842473-2772652?s=AWSEcommerceService&v=2005-07-26&p=ApiReference/OfferFullResponseGroup

==== Micropayment Markup ====
* http://www.w3.org/TR/Micropayment-Markup/

==== FOAF-Shop ====
* http://rdfweb.org/people/danbri/rdfweb/danbri-foafshop.rdf

==== Froogle ====
* http://www.google.com/froogle/merchants/advanced_feed_instructions.html

==== Yahoo Shopping ====
* http://productsubmit.adcentral.yahoo.com/sspi/us/spec/

==== Become.com ====
* http://www.become.com/merchant/Product_Feed_Specification_5_05_05.pdf

==== MySimon ====
* http://shopper.cnet.com/html/partners/a_feed.html#guidelines

==== LinkShare Datafeeds ====
* http://www.linkshare.com/rc/sample_mfile.shtml (Example Feed)

== Related Initiatives ==

The following is a list of related e-business initiatives. While the scope of these projects is much larger than the problem addressed here, they may provide good reference points for property and process naming conventions. Included primarily for completeness.

* [http://www.w3.org/ECommerce/ W3C Electronic Commerce Interest Group] The role of W3C is to focus on core infrastructure technologies for Electronic Commerce and identify common infrastructure needed in this area.

* [http://www.commerce.net CommerceNet] CommerceNet is a non-profit membership organization meeting the evolving needs of companies doing electronic commerce.

* [http://www.ebxml.org ebXML] ebXML (Electronic Business using eXtensible Markup Language), is a modular suite of specifications that enables enterprises of any size and in any geographical location to conduct business over the Internet.

* [http://www.biztalk.org BizTalk] The BizTalk Framework is an XML framework for application integration and electronic commerce. It includes a design framework for implementing an XML schema and a set of XML tags used in messages sent between applications.

* [http://xml.coverpages.org/ecml.html ECML] The Electronic Commerce Modeling Language provides a simple set of guidelines for web merchants that will enable digital wallets from multiple vendors to automate the exchange of information between users and merchants.

* [http://www.iotp.org IOTP] The Open Trading Protocol was developed by a number of organizations, working cooperatively to make widespread Internet trading a convenient and secure reality.

* [http://www.udef.org UDEF] The Universal Data Element Framework is a cross-industry metadata identification strategy designed to facilitate convergence and interoperability among e-business and other standards.

* [http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ubl UBL] UBL, the Universal Business Language, is the product of an international effort to define a royalty-free library of standard electronic XML business documents such as purchase orders and invoices.

* [http://www.rosettanet.org RosettaNet] A self-funded, non-profit organization, RosettaNet is a consortium of major Computer and Consumer Electronics, Electronic Components, Semiconductor Manufacturing, Telecommunications and Logistics companies working to create and implement industry-wide, open e-business process standards. These standards form a common e-business language, aligning processes between supply chain partners on a global basis.

listing-examples

2005-08-29T19:09:28Z

Emiliano: /* expats.cz */

= Listing Examples =

This is an exploratory page to document listing (e.g. For Sale, Wanted) examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary feed formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed listings microformat.

== Contributors ==

* Trevor O'Reilly
* Emiliano Martínez Luque

== Examples in the Wild ==

=== For Sale ===

==== Craigslist ====
* http://www.craigslist.org/sss/
* email
* duration
* date
* category
* title
* description
* location
* condition
* images
* price
* availability

==== Amazon ====
* http://www.amazon.com/exec/obidos/ASIN/0735712018

==== Powazek ====
* http://www.powazek.com/2005/01/000485.html
* email
* date
* title
* description
* image
* location
* condition
* price
* availability

==== 37signals ====
* http://www.37signals.com/svn/archives2/for_sale_hp_laserjet_4000n_and_a_1ghz_powermac_g4_tower.php
* email
* date
* title
* description
* location
* condition
* price
* availability

==== Mercado Libre ====
* http://www.mercadolibre.com.ar/jm/item?site=MLA&id=17910319
* http://www.mercadolibre.com.ar/jm/item?site=MLA&id=17902804
* price ammount
* price currency
* financing options (? may or may not exist)
* merchant/seller name
* merchant/seller rating (Within Mercado Libre)
* product condition (Used|New)
* location (Province)
* country (Implied by Navigation. Country is selected when accesing mercadolibre.com)
* product name
* product photo
* product description
* offer ending date
* item# (MercadoLibre ID)

==== Segunda Mano ====
* http://www.segundamano.com.ar/detalles/asp/informatica_y_comunicaciones/cámaras_digitales/venta/13083319.htm
* http://www.segundamano.com.ar/detalles/asp/informatica_y_comunicaciones/cámaras_digitales/venta/13084677.htm
* http://www.segundamano.com.ar/detalles/asp/automotores/motos/venta/13086663.htm
* price ammount
* price currency
* product description
* seller telephone
* publish date
* province (?)
* city (?)
* country (Implied by Navigation. Country is selected when accesing segundamano.com)
* product specific data ( ie: Model, Year, Brand for Cars or Motorcycles. Varies by Product type. )

==== Expats.cz ====
* http://www.expats.cz/prague/t-71854.html
* price ammount
* price currency (might be CZK, USD, EUR)
* product description
* product condition
* email
* date

==== alibaba.com ====
* http://aux.en.alibaba.com/offerdetail/50425885/Sell_Split_Wall_Mounted_Air_Conditioner.html
* product name
* product photo
* product category
* description/features
* listing date
* expiry date
* company name
* contact person
* address
* zip
* telephone
* fax
* website

=== Wanted ===

==== eBay ====
* http://www.wantitnow.ebay.com
* category
* item number
* buyer nickname
* feedback
* date
* duration
* title
* description
* location
* condition
* price

==== Craigslist ====
* http://www.craigslist.org/wan/
* email
* duration
* date
* category
* title
* description
* location
* condition
* images
* price

== Previous Schemas and Formats ==

==== eBay ====
* http://developer.ebay.com/DevZone/XML/docs/WSDL/index.htm
* http://pages.ebay.com/help/sell/export-structure.html

==== Amazon ====
* http://www.amazon.com/gp/aws/sdk/?v=2005%2d07%2d26&s=AWSEcommerceService
* http://www.amazon.com/gp/aws/sdk/main.html/103-0842473-2772652?s=AWSEcommerceService&v=2005-07-26&p=ApiReference/SmallResponseGroup
* http://www.amazon.com/gp/aws/sdk/main.html/103-0842473-2772652?s=AWSEcommerceService&v=2005-07-26&p=ApiReference/OfferFullResponseGroup

==== Micropayment Markup ====
* http://www.w3.org/TR/Micropayment-Markup/

==== FOAF-Shop ====
* http://rdfweb.org/people/danbri/rdfweb/danbri-foafshop.rdf

==== Froogle ====
* http://www.google.com/froogle/merchants/advanced_feed_instructions.html

==== Yahoo Shopping ====
* http://productsubmit.adcentral.yahoo.com/sspi/us/spec/

==== Become.com ====
* http://www.become.com/merchant/Product_Feed_Specification_5_05_05.pdf

==== MySimon ====
* http://shopper.cnet.com/html/partners/a_feed.html#guidelines

==== LinkShare Datafeeds ====
* http://www.linkshare.com/rc/sample_mfile.shtml (Example Feed)

== Related Initiatives ==

The following is a list of related e-business initiatives. While the scope of these projects is much larger than the problem addressed here, they may provide good reference points for property and process naming conventions. Included primarily for completeness.

* [http://www.w3.org/ECommerce/ W3C Electronic Commerce Interest Group] The role of W3C is to focus on core infrastructure technologies for Electronic Commerce and identify common infrastructure needed in this area.

* [http://www.commerce.net CommerceNet] CommerceNet is a non-profit membership organization meeting the evolving needs of companies doing electronic commerce.

* [http://www.ebxml.org ebXML] ebXML (Electronic Business using eXtensible Markup Language), is a modular suite of specifications that enables enterprises of any size and in any geographical location to conduct business over the Internet.

* [http://www.biztalk.org BizTalk] The BizTalk Framework is an XML framework for application integration and electronic commerce. It includes a design framework for implementing an XML schema and a set of XML tags used in messages sent between applications.

* [http://xml.coverpages.org/ecml.html ECML] The Electronic Commerce Modeling Language provides a simple set of guidelines for web merchants that will enable digital wallets from multiple vendors to automate the exchange of information between users and merchants.

* [http://www.iotp.org IOTP] The Open Trading Protocol was developed by a number of organizations, working cooperatively to make widespread Internet trading a convenient and secure reality.

* [http://www.udef.org UDEF] The Universal Data Element Framework is a cross-industry metadata identification strategy designed to facilitate convergence and interoperability among e-business and other standards.

* [http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ubl UBL] UBL, the Universal Business Language, is the product of an international effort to define a royalty-free library of standard electronic XML business documents such as purchase orders and invoices.

* [http://www.rosettanet.org RosettaNet] A self-funded, non-profit organization, RosettaNet is a consortium of major Computer and Consumer Electronics, Electronic Components, Semiconductor Manufacturing, Telecommunications and Logistics companies working to create and implement industry-wide, open e-business process standards. These standards form a common e-business language, aligning processes between supply chain partners on a global basis.

listing-examples

2005-08-29T19:09:10Z

Emiliano:

= Listing Examples =

This is an exploratory page to document listing (e.g. For Sale, Wanted) examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary feed formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed listings microformat.

== Contributors ==

* Trevor O'Reilly
* Emiliano Martínez Luque

== Examples in the Wild ==

=== For Sale ===

==== Craigslist ====
* http://www.craigslist.org/sss/
* email
* duration
* date
* category
* title
* description
* location
* condition
* images
* price
* availability

==== Amazon ====
* http://www.amazon.com/exec/obidos/ASIN/0735712018

==== Powazek ====
* http://www.powazek.com/2005/01/000485.html
* email
* date
* title
* description
* image
* location
* condition
* price
* availability

==== 37signals ====
* http://www.37signals.com/svn/archives2/for_sale_hp_laserjet_4000n_and_a_1ghz_powermac_g4_tower.php
* email
* date
* title
* description
* location
* condition
* price
* availability

==== Mercado Libre ====
* http://www.mercadolibre.com.ar/jm/item?site=MLA&id=17910319
* http://www.mercadolibre.com.ar/jm/item?site=MLA&id=17902804
* price ammount
* price currency
* financing options (? may or may not exist)
* merchant/seller name
* merchant/seller rating (Within Mercado Libre)
* product condition (Used|New)
* location (Province)
* country (Implied by Navigation. Country is selected when accesing mercadolibre.com)
* product name
* product photo
* product description
* offer ending date
* item# (MercadoLibre ID)

==== Segunda Mano ====
* http://www.segundamano.com.ar/detalles/asp/informatica_y_comunicaciones/cámaras_digitales/venta/13083319.htm
* http://www.segundamano.com.ar/detalles/asp/informatica_y_comunicaciones/cámaras_digitales/venta/13084677.htm
* http://www.segundamano.com.ar/detalles/asp/automotores/motos/venta/13086663.htm
* price ammount
* price currency
* product description
* seller telephone
* publish date
* province (?)
* city (?)
* country (Implied by Navigation. Country is selected when accesing segundamano.com)
* product specific data ( ie: Model, Year, Brand for Cars or Motorcycles. Varies by Product type. )

==== expats.cz ====
* http://www.expats.cz/prague/t-71854.html
* price ammount
* price currency (might be CZK, USD, EUR)
* product description
* product condition
* email
* date

==== alibaba.com ====
* http://aux.en.alibaba.com/offerdetail/50425885/Sell_Split_Wall_Mounted_Air_Conditioner.html
* product name
* product photo
* product category
* description/features
* listing date
* expiry date
* company name
* contact person
* address
* zip
* telephone
* fax
* website

=== Wanted ===

==== eBay ====
* http://www.wantitnow.ebay.com
* category
* item number
* buyer nickname
* feedback
* date
* duration
* title
* description
* location
* condition
* price

==== Craigslist ====
* http://www.craigslist.org/wan/
* email
* duration
* date
* category
* title
* description
* location
* condition
* images
* price

== Previous Schemas and Formats ==

==== eBay ====
* http://developer.ebay.com/DevZone/XML/docs/WSDL/index.htm
* http://pages.ebay.com/help/sell/export-structure.html

==== Amazon ====
* http://www.amazon.com/gp/aws/sdk/?v=2005%2d07%2d26&s=AWSEcommerceService
* http://www.amazon.com/gp/aws/sdk/main.html/103-0842473-2772652?s=AWSEcommerceService&v=2005-07-26&p=ApiReference/SmallResponseGroup
* http://www.amazon.com/gp/aws/sdk/main.html/103-0842473-2772652?s=AWSEcommerceService&v=2005-07-26&p=ApiReference/OfferFullResponseGroup

==== Micropayment Markup ====
* http://www.w3.org/TR/Micropayment-Markup/

==== FOAF-Shop ====
* http://rdfweb.org/people/danbri/rdfweb/danbri-foafshop.rdf

==== Froogle ====
* http://www.google.com/froogle/merchants/advanced_feed_instructions.html

==== Yahoo Shopping ====
* http://productsubmit.adcentral.yahoo.com/sspi/us/spec/

==== Become.com ====
* http://www.become.com/merchant/Product_Feed_Specification_5_05_05.pdf

==== MySimon ====
* http://shopper.cnet.com/html/partners/a_feed.html#guidelines

==== LinkShare Datafeeds ====
* http://www.linkshare.com/rc/sample_mfile.shtml (Example Feed)

== Related Initiatives ==

The following is a list of related e-business initiatives. While the scope of these projects is much larger than the problem addressed here, they may provide good reference points for property and process naming conventions. Included primarily for completeness.

* [http://www.w3.org/ECommerce/ W3C Electronic Commerce Interest Group] The role of W3C is to focus on core infrastructure technologies for Electronic Commerce and identify common infrastructure needed in this area.

* [http://www.commerce.net CommerceNet] CommerceNet is a non-profit membership organization meeting the evolving needs of companies doing electronic commerce.

* [http://www.ebxml.org ebXML] ebXML (Electronic Business using eXtensible Markup Language), is a modular suite of specifications that enables enterprises of any size and in any geographical location to conduct business over the Internet.

* [http://www.biztalk.org BizTalk] The BizTalk Framework is an XML framework for application integration and electronic commerce. It includes a design framework for implementing an XML schema and a set of XML tags used in messages sent between applications.

* [http://xml.coverpages.org/ecml.html ECML] The Electronic Commerce Modeling Language provides a simple set of guidelines for web merchants that will enable digital wallets from multiple vendors to automate the exchange of information between users and merchants.

* [http://www.iotp.org IOTP] The Open Trading Protocol was developed by a number of organizations, working cooperatively to make widespread Internet trading a convenient and secure reality.

* [http://www.udef.org UDEF] The Universal Data Element Framework is a cross-industry metadata identification strategy designed to facilitate convergence and interoperability among e-business and other standards.

* [http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ubl UBL] UBL, the Universal Business Language, is the product of an international effort to define a royalty-free library of standard electronic XML business documents such as purchase orders and invoices.

* [http://www.rosettanet.org RosettaNet] A self-funded, non-profit organization, RosettaNet is a consortium of major Computer and Consumer Electronics, Electronic Components, Semiconductor Manufacturing, Telecommunications and Logistics companies working to create and implement industry-wide, open e-business process standards. These standards form a common e-business language, aligning processes between supply chain partners on a global basis.

listing-examples

2005-08-29T17:29:25Z

Emiliano: /* expats.cz */

= Listing Examples =

This is an exploratory page to document listing (e.g. For Sale, Wanted) examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary feed formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed listings microformat.

== Contributors ==

* Trevor O'Reilly
* Emiliano Martínez Luque

== Examples in the Wild ==

=== For Sale ===

==== Craigslist ====
* http://www.craigslist.org/sss/
* email
* duration
* date
* category
* title
* description
* location
* condition
* images
* price
* availability

==== Amazon ====
* http://www.amazon.com/exec/obidos/ASIN/0735712018

==== Powazek ====
* http://www.powazek.com/2005/01/000485.html
* email
* date
* title
* description
* image
* location
* condition
* price
* availability

==== 37signals ====
* http://www.37signals.com/svn/archives2/for_sale_hp_laserjet_4000n_and_a_1ghz_powermac_g4_tower.php
* email
* date
* title
* description
* location
* condition
* price
* availability

==== Mercado Libre ====
* http://www.mercadolibre.com.ar/jm/item?site=MLA&id=17910319
* http://www.mercadolibre.com.ar/jm/item?site=MLA&id=17902804
* Price Ammount
* Price Currency
* Financing Options (? may or may not exist)
* Merchant/Seller Name
* Merchant/Seller Rating (Within Mercado Libre)
* Product Condition (Used|New)
* Location (Province)
* Country (Implied by Navigation. Country is selected when accesing mercadolibre.com)
* Product Name
* Product Photo
* Product Description
* Offer Ending Date
* Item# (MercadoLibre ID)

==== Segunda Mano ====
* http://www.segundamano.com.ar/detalles/asp/informatica_y_comunicaciones/cámaras_digitales/venta/13083319.htm
* http://www.segundamano.com.ar/detalles/asp/informatica_y_comunicaciones/cámaras_digitales/venta/13084677.htm
* http://www.segundamano.com.ar/detalles/asp/automotores/motos/venta/13086663.htm
* Price Ammount
* Price Currency
* Product Description
* Seller Telephone
* Publish Date
* Province (?)
* City (?)
* Country (Implied by Navigation. Country is selected when accesing segundamano.com)
* Product Specific Data ( ie: Model, Year, Brand for Cars or Motorcycles. Varies by Product type. )

==== expats.cz ====
* http://www.expats.cz/prague/t-71854.html
* Price Ammount
* Price Currency (might be CZK, USD, EUR)
* Product Description
* Product Condition
* Email
* Date

=== Wanted ===

==== eBay ====
* http://www.wantitnow.ebay.com
* category
* item number
* buyer nickname
* feedback
* date
* duration
* title
* description
* location
* condition
* price

==== Craigslist ====
* http://www.craigslist.org/wan/
* email
* duration
* date
* category
* title
* description
* location
* condition
* images
* price

== Previous Schemas and Formats ==

==== eBay ====
* http://developer.ebay.com/DevZone/XML/docs/WSDL/index.htm
* http://pages.ebay.com/help/sell/export-structure.html

==== Amazon ====
* http://www.amazon.com/gp/aws/sdk/?v=2005%2d07%2d26&s=AWSEcommerceService
* http://www.amazon.com/gp/aws/sdk/main.html/103-0842473-2772652?s=AWSEcommerceService&v=2005-07-26&p=ApiReference/SmallResponseGroup
* http://www.amazon.com/gp/aws/sdk/main.html/103-0842473-2772652?s=AWSEcommerceService&v=2005-07-26&p=ApiReference/OfferFullResponseGroup

==== Micropayment Markup ====
* http://www.w3.org/TR/Micropayment-Markup/

==== FOAF-Shop ====
* http://rdfweb.org/people/danbri/rdfweb/danbri-foafshop.rdf

==== Froogle ====
* http://www.google.com/froogle/merchants/advanced_feed_instructions.html

==== Yahoo Shopping ====
* http://productsubmit.adcentral.yahoo.com/sspi/us/spec/

==== Become.com ====
* http://www.become.com/merchant/Product_Feed_Specification_5_05_05.pdf

==== MySimon ====
* http://shopper.cnet.com/html/partners/a_feed.html#guidelines

==== LinkShare Datafeeds ====
* http://www.linkshare.com/rc/sample_mfile.shtml (Example Feed)

== Related Initiatives ==

The following is a list of related e-business initiatives. While the scope of these projects is much larger than the problem addressed here, they may provide good reference points for property and process naming conventions. Included primarily for completeness.

* [http://www.w3.org/ECommerce/ W3C Electronic Commerce Interest Group] The role of W3C is to focus on core infrastructure technologies for Electronic Commerce and identify common infrastructure needed in this area.

* [http://www.commerce.net CommerceNet] CommerceNet is a non-profit membership organization meeting the evolving needs of companies doing electronic commerce.

* [http://www.ebxml.org ebXML] ebXML (Electronic Business using eXtensible Markup Language), is a modular suite of specifications that enables enterprises of any size and in any geographical location to conduct business over the Internet.

* [http://www.biztalk.org BizTalk] The BizTalk Framework is an XML framework for application integration and electronic commerce. It includes a design framework for implementing an XML schema and a set of XML tags used in messages sent between applications.

* [http://xml.coverpages.org/ecml.html ECML] The Electronic Commerce Modeling Language provides a simple set of guidelines for web merchants that will enable digital wallets from multiple vendors to automate the exchange of information between users and merchants.

* [http://www.iotp.org IOTP] The Open Trading Protocol was developed by a number of organizations, working cooperatively to make widespread Internet trading a convenient and secure reality.

* [http://www.udef.org UDEF] The Universal Data Element Framework is a cross-industry metadata identification strategy designed to facilitate convergence and interoperability among e-business and other standards.

* [http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ubl UBL] UBL, the Universal Business Language, is the product of an international effort to define a royalty-free library of standard electronic XML business documents such as purchase orders and invoices.

* [http://www.rosettanet.org RosettaNet] A self-funded, non-profit organization, RosettaNet is a consortium of major Computer and Consumer Electronics, Electronic Components, Semiconductor Manufacturing, Telecommunications and Logistics companies working to create and implement industry-wide, open e-business process standards. These standards form a common e-business language, aligning processes between supply chain partners on a global basis.

listing-examples

2005-08-29T17:26:55Z

Emiliano: /* Previous Schemas and Formats */

= Listing Examples =

This is an exploratory page to document listing (e.g. For Sale, Wanted) examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary feed formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed listings microformat.

== Contributors ==

* Trevor O'Reilly
* Emiliano Martínez Luque

== Examples in the Wild ==

=== For Sale ===

==== Craigslist ====
* http://www.craigslist.org/sss/
* email
* duration
* date
* category
* title
* description
* location
* condition
* images
* price
* availability

==== Amazon ====
* http://www.amazon.com/exec/obidos/ASIN/0735712018

==== Powazek ====
* http://www.powazek.com/2005/01/000485.html
* email
* date
* title
* description
* image
* location
* condition
* price
* availability

==== 37signals ====
* http://www.37signals.com/svn/archives2/for_sale_hp_laserjet_4000n_and_a_1ghz_powermac_g4_tower.php
* email
* date
* title
* description
* location
* condition
* price
* availability

==== Mercado Libre ====
* http://www.mercadolibre.com.ar/jm/item?site=MLA&id=17910319
* http://www.mercadolibre.com.ar/jm/item?site=MLA&id=17902804
* Price Ammount
* Price Currency
* Financing Options (? may or may not exist)
* Merchant/Seller Name
* Merchant/Seller Rating (Within Mercado Libre)
* Product Condition (Used|New)
* Location (Province)
* Country (Implied by Navigation. Country is selected when accesing mercadolibre.com)
* Product Name
* Product Photo
* Product Description
* Offer Ending Date
* Item# (MercadoLibre ID)

==== Segunda Mano ====
* http://www.segundamano.com.ar/detalles/asp/informatica_y_comunicaciones/cámaras_digitales/venta/13083319.htm
* http://www.segundamano.com.ar/detalles/asp/informatica_y_comunicaciones/cámaras_digitales/venta/13084677.htm
* http://www.segundamano.com.ar/detalles/asp/automotores/motos/venta/13086663.htm
* Price Ammount
* Price Currency
* Product Description
* Seller Telephone
* Publish Date
* Province (?)
* City (?)
* Country (Implied by Navigation. Country is selected when accesing segundamano.com)
* Product Specific Data ( ie: Model, Year, Brand for Cars or Motorcycles. Varies by Product type. )

==== expats.cz ====
* http://www.expats.cz/prague/t-71854.html
* Price Ammount
* Price Currency (might be CZK, USD, EUR)
* Product Description
* Product Condition

=== Wanted ===

==== eBay ====
* http://www.wantitnow.ebay.com
* category
* item number
* buyer nickname
* feedback
* date
* duration
* title
* description
* location
* condition
* price

==== Craigslist ====
* http://www.craigslist.org/wan/
* email
* duration
* date
* category
* title
* description
* location
* condition
* images
* price

== Previous Schemas and Formats ==

==== eBay ====
* http://developer.ebay.com/DevZone/XML/docs/WSDL/index.htm
* http://pages.ebay.com/help/sell/export-structure.html

==== Amazon ====
* http://www.amazon.com/gp/aws/sdk/?v=2005%2d07%2d26&s=AWSEcommerceService
* http://www.amazon.com/gp/aws/sdk/main.html/103-0842473-2772652?s=AWSEcommerceService&v=2005-07-26&p=ApiReference/SmallResponseGroup
* http://www.amazon.com/gp/aws/sdk/main.html/103-0842473-2772652?s=AWSEcommerceService&v=2005-07-26&p=ApiReference/OfferFullResponseGroup

==== Micropayment Markup ====
* http://www.w3.org/TR/Micropayment-Markup/

==== FOAF-Shop ====
* http://rdfweb.org/people/danbri/rdfweb/danbri-foafshop.rdf

==== Froogle ====
* http://www.google.com/froogle/merchants/advanced_feed_instructions.html

==== Yahoo Shopping ====
* http://productsubmit.adcentral.yahoo.com/sspi/us/spec/

==== Become.com ====
* http://www.become.com/merchant/Product_Feed_Specification_5_05_05.pdf

==== MySimon ====
* http://shopper.cnet.com/html/partners/a_feed.html#guidelines

==== LinkShare Datafeeds ====
* http://www.linkshare.com/rc/sample_mfile.shtml (Example Feed)

== Related Initiatives ==

The following is a list of related e-business initiatives. While the scope of these projects is much larger than the problem addressed here, they may provide good reference points for property and process naming conventions. Included primarily for completeness.

* [http://www.w3.org/ECommerce/ W3C Electronic Commerce Interest Group] The role of W3C is to focus on core infrastructure technologies for Electronic Commerce and identify common infrastructure needed in this area.

* [http://www.commerce.net CommerceNet] CommerceNet is a non-profit membership organization meeting the evolving needs of companies doing electronic commerce.

* [http://www.ebxml.org ebXML] ebXML (Electronic Business using eXtensible Markup Language), is a modular suite of specifications that enables enterprises of any size and in any geographical location to conduct business over the Internet.

* [http://www.biztalk.org BizTalk] The BizTalk Framework is an XML framework for application integration and electronic commerce. It includes a design framework for implementing an XML schema and a set of XML tags used in messages sent between applications.

* [http://xml.coverpages.org/ecml.html ECML] The Electronic Commerce Modeling Language provides a simple set of guidelines for web merchants that will enable digital wallets from multiple vendors to automate the exchange of information between users and merchants.

* [http://www.iotp.org IOTP] The Open Trading Protocol was developed by a number of organizations, working cooperatively to make widespread Internet trading a convenient and secure reality.

* [http://www.udef.org UDEF] The Universal Data Element Framework is a cross-industry metadata identification strategy designed to facilitate convergence and interoperability among e-business and other standards.

* [http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ubl UBL] UBL, the Universal Business Language, is the product of an international effort to define a royalty-free library of standard electronic XML business documents such as purchase orders and invoices.

* [http://www.rosettanet.org RosettaNet] A self-funded, non-profit organization, RosettaNet is a consortium of major Computer and Consumer Electronics, Electronic Components, Semiconductor Manufacturing, Telecommunications and Logistics companies working to create and implement industry-wide, open e-business process standards. These standards form a common e-business language, aligning processes between supply chain partners on a global basis.

listing-examples

2005-08-29T17:24:21Z

Emiliano: /* Amazon */

= Listing Examples =

This is an exploratory page to document listing (e.g. For Sale, Wanted) examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary feed formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed listings microformat.

== Contributors ==

* Trevor O'Reilly
* Emiliano Martínez Luque

== Examples in the Wild ==

=== For Sale ===

==== Craigslist ====
* http://www.craigslist.org/sss/
* email
* duration
* date
* category
* title
* description
* location
* condition
* images
* price
* availability

==== Amazon ====
* http://www.amazon.com/exec/obidos/ASIN/0735712018

==== Powazek ====
* http://www.powazek.com/2005/01/000485.html
* email
* date
* title
* description
* image
* location
* condition
* price
* availability

==== 37signals ====
* http://www.37signals.com/svn/archives2/for_sale_hp_laserjet_4000n_and_a_1ghz_powermac_g4_tower.php
* email
* date
* title
* description
* location
* condition
* price
* availability

==== Mercado Libre ====
* http://www.mercadolibre.com.ar/jm/item?site=MLA&id=17910319
* http://www.mercadolibre.com.ar/jm/item?site=MLA&id=17902804
* Price Ammount
* Price Currency
* Financing Options (? may or may not exist)
* Merchant/Seller Name
* Merchant/Seller Rating (Within Mercado Libre)
* Product Condition (Used|New)
* Location (Province)
* Country (Implied by Navigation. Country is selected when accesing mercadolibre.com)
* Product Name
* Product Photo
* Product Description
* Offer Ending Date
* Item# (MercadoLibre ID)

==== Segunda Mano ====
* http://www.segundamano.com.ar/detalles/asp/informatica_y_comunicaciones/cámaras_digitales/venta/13083319.htm
* http://www.segundamano.com.ar/detalles/asp/informatica_y_comunicaciones/cámaras_digitales/venta/13084677.htm
* http://www.segundamano.com.ar/detalles/asp/automotores/motos/venta/13086663.htm
* Price Ammount
* Price Currency
* Product Description
* Seller Telephone
* Publish Date
* Province (?)
* City (?)
* Country (Implied by Navigation. Country is selected when accesing segundamano.com)
* Product Specific Data ( ie: Model, Year, Brand for Cars or Motorcycles. Varies by Product type. )

==== expats.cz ====
* http://www.expats.cz/prague/t-71854.html
* Price Ammount
* Price Currency (might be CZK, USD, EUR)
* Product Description
* Product Condition

=== Wanted ===

==== eBay ====
* http://www.wantitnow.ebay.com
* category
* item number
* buyer nickname
* feedback
* date
* duration
* title
* description
* location
* condition
* price

==== Craigslist ====
* http://www.craigslist.org/wan/
* email
* duration
* date
* category
* title
* description
* location
* condition
* images
* price

== Previous Schemas and Formats ==

==== eBay ====
* http://developer.ebay.com/DevZone/XML/docs/WSDL/index.htm
* http://pages.ebay.com/help/sell/export-structure.html

==== Amazon ====
* http://www.amazon.com/gp/aws/sdk/?v=2005%2d07%2d26&s=AWSEcommerceService
* http://www.amazon.com/gp/aws/sdk/main.html/103-0842473-2772652?s=AWSEcommerceService&v=2005-07-26&p=ApiReference/SmallResponseGroup
* http://www.amazon.com/gp/aws/sdk/main.html/103-0842473-2772652?s=AWSEcommerceService&v=2005-07-26&p=ApiReference/OfferFullResponseGroup

==== Micropayment Markup ====
* http://www.w3.org/TR/Micropayment-Markup/

==== FOAF-Shop ====
* http://rdfweb.org/people/danbri/rdfweb/danbri-foafshop.rdf

==== Froogle ====
* http://www.google.com/froogle/merchants/advanced_feed_instructions.html

==== Yahoo Shopping ====
* http://productsubmit.adcentral.yahoo.com/sspi/us/spec/

==== Become.com ====
* http://www.become.com/merchant/Product_Feed_Specification_5_05_05.pdf

==== MySimon ====
* http://shopper.cnet.com/html/partners/a_feed.html#guidelines

== Related Initiatives ==

The following is a list of related e-business initiatives. While the scope of these projects is much larger than the problem addressed here, they may provide good reference points for property and process naming conventions. Included primarily for completeness.

* [http://www.w3.org/ECommerce/ W3C Electronic Commerce Interest Group] The role of W3C is to focus on core infrastructure technologies for Electronic Commerce and identify common infrastructure needed in this area.

* [http://www.commerce.net CommerceNet] CommerceNet is a non-profit membership organization meeting the evolving needs of companies doing electronic commerce.

* [http://www.ebxml.org ebXML] ebXML (Electronic Business using eXtensible Markup Language), is a modular suite of specifications that enables enterprises of any size and in any geographical location to conduct business over the Internet.

* [http://www.biztalk.org BizTalk] The BizTalk Framework is an XML framework for application integration and electronic commerce. It includes a design framework for implementing an XML schema and a set of XML tags used in messages sent between applications.

* [http://xml.coverpages.org/ecml.html ECML] The Electronic Commerce Modeling Language provides a simple set of guidelines for web merchants that will enable digital wallets from multiple vendors to automate the exchange of information between users and merchants.

* [http://www.iotp.org IOTP] The Open Trading Protocol was developed by a number of organizations, working cooperatively to make widespread Internet trading a convenient and secure reality.

* [http://www.udef.org UDEF] The Universal Data Element Framework is a cross-industry metadata identification strategy designed to facilitate convergence and interoperability among e-business and other standards.

* [http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ubl UBL] UBL, the Universal Business Language, is the product of an international effort to define a royalty-free library of standard electronic XML business documents such as purchase orders and invoices.

* [http://www.rosettanet.org RosettaNet] A self-funded, non-profit organization, RosettaNet is a consortium of major Computer and Consumer Electronics, Electronic Components, Semiconductor Manufacturing, Telecommunications and Logistics companies working to create and implement industry-wide, open e-business process standards. These standards form a common e-business language, aligning processes between supply chain partners on a global basis.

listing-examples

2005-08-29T17:24:01Z

Emiliano: /* Amazon */

= Listing Examples =

This is an exploratory page to document listing (e.g. For Sale, Wanted) examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary feed formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed listings microformat.

== Contributors ==

* Trevor O'Reilly
* Emiliano Martínez Luque

== Examples in the Wild ==

=== For Sale ===

==== Craigslist ====
* http://www.craigslist.org/sss/
* email
* duration
* date
* category
* title
* description
* location
* condition
* images
* price
* availability

==== Amazon ====
* http://www.amazon.com/exec/obidos/ASIN/0735712018

==== Powazek ====
* http://www.powazek.com/2005/01/000485.html
* email
* date
* title
* description
* image
* location
* condition
* price
* availability

==== 37signals ====
* http://www.37signals.com/svn/archives2/for_sale_hp_laserjet_4000n_and_a_1ghz_powermac_g4_tower.php
* email
* date
* title
* description
* location
* condition
* price
* availability

==== Mercado Libre ====
* http://www.mercadolibre.com.ar/jm/item?site=MLA&id=17910319
* http://www.mercadolibre.com.ar/jm/item?site=MLA&id=17902804
* Price Ammount
* Price Currency
* Financing Options (? may or may not exist)
* Merchant/Seller Name
* Merchant/Seller Rating (Within Mercado Libre)
* Product Condition (Used|New)
* Location (Province)
* Country (Implied by Navigation. Country is selected when accesing mercadolibre.com)
* Product Name
* Product Photo
* Product Description
* Offer Ending Date
* Item# (MercadoLibre ID)

==== Segunda Mano ====
* http://www.segundamano.com.ar/detalles/asp/informatica_y_comunicaciones/cámaras_digitales/venta/13083319.htm
* http://www.segundamano.com.ar/detalles/asp/informatica_y_comunicaciones/cámaras_digitales/venta/13084677.htm
* http://www.segundamano.com.ar/detalles/asp/automotores/motos/venta/13086663.htm
* Price Ammount
* Price Currency
* Product Description
* Seller Telephone
* Publish Date
* Province (?)
* City (?)
* Country (Implied by Navigation. Country is selected when accesing segundamano.com)
* Product Specific Data ( ie: Model, Year, Brand for Cars or Motorcycles. Varies by Product type. )

==== expats.cz ====
* http://www.expats.cz/prague/t-71854.html
* Price Ammount
* Price Currency (might be CZK, USD, EUR)
* Product Description
* Product Condition

=== Wanted ===

==== eBay ====
* http://www.wantitnow.ebay.com
* category
* item number
* buyer nickname
* feedback
* date
* duration
* title
* description
* location
* condition
* price

==== Craigslist ====
* http://www.craigslist.org/wan/
* email
* duration
* date
* category
* title
* description
* location
* condition
* images
* price

== Previous Schemas and Formats ==

==== eBay ====
* http://developer.ebay.com/DevZone/XML/docs/WSDL/index.htm
* http://pages.ebay.com/help/sell/export-structure.html

==== Amazon ====
* http://www.amazon.com/gp/aws/sdk/?v=2005%2d07%2d26&s=AWSEcommerceService

==== Micropayment Markup ====
* http://www.w3.org/TR/Micropayment-Markup/

==== FOAF-Shop ====
* http://rdfweb.org/people/danbri/rdfweb/danbri-foafshop.rdf

==== Froogle ====
* http://www.google.com/froogle/merchants/advanced_feed_instructions.html

==== Yahoo Shopping ====
* http://productsubmit.adcentral.yahoo.com/sspi/us/spec/

==== Become.com ====
* http://www.become.com/merchant/Product_Feed_Specification_5_05_05.pdf

==== MySimon ====
* http://shopper.cnet.com/html/partners/a_feed.html#guidelines

== Related Initiatives ==

The following is a list of related e-business initiatives. While the scope of these projects is much larger than the problem addressed here, they may provide good reference points for property and process naming conventions. Included primarily for completeness.

* [http://www.w3.org/ECommerce/ W3C Electronic Commerce Interest Group] The role of W3C is to focus on core infrastructure technologies for Electronic Commerce and identify common infrastructure needed in this area.

* [http://www.commerce.net CommerceNet] CommerceNet is a non-profit membership organization meeting the evolving needs of companies doing electronic commerce.

* [http://www.ebxml.org ebXML] ebXML (Electronic Business using eXtensible Markup Language), is a modular suite of specifications that enables enterprises of any size and in any geographical location to conduct business over the Internet.

* [http://www.biztalk.org BizTalk] The BizTalk Framework is an XML framework for application integration and electronic commerce. It includes a design framework for implementing an XML schema and a set of XML tags used in messages sent between applications.

* [http://xml.coverpages.org/ecml.html ECML] The Electronic Commerce Modeling Language provides a simple set of guidelines for web merchants that will enable digital wallets from multiple vendors to automate the exchange of information between users and merchants.

* [http://www.iotp.org IOTP] The Open Trading Protocol was developed by a number of organizations, working cooperatively to make widespread Internet trading a convenient and secure reality.

* [http://www.udef.org UDEF] The Universal Data Element Framework is a cross-industry metadata identification strategy designed to facilitate convergence and interoperability among e-business and other standards.

* [http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ubl UBL] UBL, the Universal Business Language, is the product of an international effort to define a royalty-free library of standard electronic XML business documents such as purchase orders and invoices.

* [http://www.rosettanet.org RosettaNet] A self-funded, non-profit organization, RosettaNet is a consortium of major Computer and Consumer Electronics, Electronic Components, Semiconductor Manufacturing, Telecommunications and Logistics companies working to create and implement industry-wide, open e-business process standards. These standards form a common e-business language, aligning processes between supply chain partners on a global basis.

listing-examples

2005-08-29T17:17:33Z

Emiliano:

= Listing Examples =

This is an exploratory page to document listing (e.g. For Sale, Wanted) examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary feed formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed listings microformat.

== Contributors ==

* Trevor O'Reilly
* Emiliano Martínez Luque

== Examples in the Wild ==

=== For Sale ===

==== Craigslist ====
* http://www.craigslist.org/sss/
* email
* duration
* date
* category
* title
* description
* location
* condition
* images
* price
* availability

==== Amazon ====
* http://www.amazon.com/exec/obidos/ASIN/0735712018
* http://www.amazon.com/gp/aws/sdk/main.html/103-0842473-2772652?s=AWSEcommerceService&v=2005-07-26&p=ApiReference/SmallResponseGroup
* http://www.amazon.com/gp/aws/sdk/main.html/103-0842473-2772652?s=AWSEcommerceService&v=2005-07-26&p=ApiReference/OfferFullResponseGroup

==== Powazek ====
* http://www.powazek.com/2005/01/000485.html
* email
* date
* title
* description
* image
* location
* condition
* price
* availability

==== 37signals ====
* http://www.37signals.com/svn/archives2/for_sale_hp_laserjet_4000n_and_a_1ghz_powermac_g4_tower.php
* email
* date
* title
* description
* location
* condition
* price
* availability

==== Mercado Libre ====
* http://www.mercadolibre.com.ar/jm/item?site=MLA&id=17910319
* http://www.mercadolibre.com.ar/jm/item?site=MLA&id=17902804
* Price Ammount
* Price Currency
* Financing Options (? may or may not exist)
* Merchant/Seller Name
* Merchant/Seller Rating (Within Mercado Libre)
* Product Condition (Used|New)
* Location (Province)
* Country (Implied by Navigation. Country is selected when accesing mercadolibre.com)
* Product Name
* Product Photo
* Product Description
* Offer Ending Date
* Item# (MercadoLibre ID)

==== Segunda Mano ====
* http://www.segundamano.com.ar/detalles/asp/informatica_y_comunicaciones/cámaras_digitales/venta/13083319.htm
* http://www.segundamano.com.ar/detalles/asp/informatica_y_comunicaciones/cámaras_digitales/venta/13084677.htm
* http://www.segundamano.com.ar/detalles/asp/automotores/motos/venta/13086663.htm
* Price Ammount
* Price Currency
* Product Description
* Seller Telephone
* Publish Date
* Province (?)
* City (?)
* Country (Implied by Navigation. Country is selected when accesing segundamano.com)
* Product Specific Data ( ie: Model, Year, Brand for Cars or Motorcycles. Varies by Product type. )

==== expats.cz ====
* http://www.expats.cz/prague/t-71854.html
* Price Ammount
* Price Currency (might be CZK, USD, EUR)
* Product Description
* Product Condition

=== Wanted ===

==== eBay ====
* http://www.wantitnow.ebay.com
* category
* item number
* buyer nickname
* feedback
* date
* duration
* title
* description
* location
* condition
* price

==== Craigslist ====
* http://www.craigslist.org/wan/
* email
* duration
* date
* category
* title
* description
* location
* condition
* images
* price

== Previous Schemas and Formats ==

==== eBay ====
* http://developer.ebay.com/DevZone/XML/docs/WSDL/index.htm
* http://pages.ebay.com/help/sell/export-structure.html

==== Amazon ====
* http://www.amazon.com/gp/aws/sdk/?v=2005%2d07%2d26&s=AWSEcommerceService

==== Micropayment Markup ====
* http://www.w3.org/TR/Micropayment-Markup/

==== FOAF-Shop ====
* http://rdfweb.org/people/danbri/rdfweb/danbri-foafshop.rdf

==== Froogle ====
* http://www.google.com/froogle/merchants/advanced_feed_instructions.html

==== Yahoo Shopping ====
* http://productsubmit.adcentral.yahoo.com/sspi/us/spec/

==== Become.com ====
* http://www.become.com/merchant/Product_Feed_Specification_5_05_05.pdf

==== MySimon ====
* http://shopper.cnet.com/html/partners/a_feed.html#guidelines

== Related Initiatives ==

The following is a list of related e-business initiatives. While the scope of these projects is much larger than the problem addressed here, they may provide good reference points for property and process naming conventions. Included primarily for completeness.

* [http://www.w3.org/ECommerce/ W3C Electronic Commerce Interest Group] The role of W3C is to focus on core infrastructure technologies for Electronic Commerce and identify common infrastructure needed in this area.

* [http://www.commerce.net CommerceNet] CommerceNet is a non-profit membership organization meeting the evolving needs of companies doing electronic commerce.

* [http://www.ebxml.org ebXML] ebXML (Electronic Business using eXtensible Markup Language), is a modular suite of specifications that enables enterprises of any size and in any geographical location to conduct business over the Internet.

* [http://www.biztalk.org BizTalk] The BizTalk Framework is an XML framework for application integration and electronic commerce. It includes a design framework for implementing an XML schema and a set of XML tags used in messages sent between applications.

* [http://xml.coverpages.org/ecml.html ECML] The Electronic Commerce Modeling Language provides a simple set of guidelines for web merchants that will enable digital wallets from multiple vendors to automate the exchange of information between users and merchants.

* [http://www.iotp.org IOTP] The Open Trading Protocol was developed by a number of organizations, working cooperatively to make widespread Internet trading a convenient and secure reality.

* [http://www.udef.org UDEF] The Universal Data Element Framework is a cross-industry metadata identification strategy designed to facilitate convergence and interoperability among e-business and other standards.

* [http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ubl UBL] UBL, the Universal Business Language, is the product of an international effort to define a royalty-free library of standard electronic XML business documents such as purchase orders and invoices.

* [http://www.rosettanet.org RosettaNet] A self-funded, non-profit organization, RosettaNet is a consortium of major Computer and Consumer Electronics, Electronic Components, Semiconductor Manufacturing, Telecommunications and Logistics companies working to create and implement industry-wide, open e-business process standards. These standards form a common e-business language, aligning processes between supply chain partners on a global basis.

listing-examples

2005-08-29T17:17:03Z

Emiliano: Added expats.cz

= Listing Examples =

This is an exploratory page to document listing (e.g. For Sale, Wanted) examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary feed formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed listings microformat.

== Contributors ==

* Trevor O'Reilly
* Emiliano Martínez Luque

== Examples in the Wild ==

=== For Sale ===

==== Craigslist ====
* http://www.craigslist.org/sss/
* email
* duration
* date
* category
* title
* description
* location
* condition
* images
* price
* availability

==== Amazon ====
* http://www.amazon.com/exec/obidos/ASIN/0735712018
* http://www.amazon.com/gp/aws/sdk/main.html/103-0842473-2772652?s=AWSEcommerceService&v=2005-07-26&p=ApiReference/SmallResponseGroup
* http://www.amazon.com/gp/aws/sdk/main.html/103-0842473-2772652?s=AWSEcommerceService&v=2005-07-26&p=ApiReference/OfferFullResponseGroup

==== Powazek ====
* http://www.powazek.com/2005/01/000485.html
* email
* date
* title
* description
* image
* location
* condition
* price
* availability

==== 37signals ====
* http://www.37signals.com/svn/archives2/for_sale_hp_laserjet_4000n_and_a_1ghz_powermac_g4_tower.php
* email
* date
* title
* description
* location
* condition
* price
* availability

==== Mercado Libre ====
* http://www.mercadolibre.com.ar/jm/item?site=MLA&id=17910319
* http://www.mercadolibre.com.ar/jm/item?site=MLA&id=17902804
* Price Ammount
* Price Currency
* Financing Options (? may or may not exist)
* Merchant/Seller Name
* Merchant/Seller Rating (Within Mercado Libre)
* Product Condition (Used|New)
* Location (Province)
* Country (Implied by Navigation. Country is selected when accesing mercadolibre.com)
* Product Name
* Product Photo
* Product Description
* Offer Ending Date
* Item# (MercadoLibre ID)

==== Segunda Mano ====
* http://www.segundamano.com.ar/detalles/asp/informatica_y_comunicaciones/cámaras_digitales/venta/13083319.htm
* http://www.segundamano.com.ar/detalles/asp/informatica_y_comunicaciones/cámaras_digitales/venta/13084677.htm
* http://www.segundamano.com.ar/detalles/asp/automotores/motos/venta/13086663.htm
* Price Ammount
* Price Currency
* Product Description
* Seller Telephone
* Publish Date
* Province (?)
* City (?)
* Country (Implied by Navigation. Country is selected when accesing segundamano.com)
* Product Specific Data ( ie: Model, Year, Brand for Cars or Motorcycles. Varies by Product type. )

=== expats.cz ===
* http://www.expats.cz/prague/t-71854.html
* Price Ammount
* Price Currency (might be CZK, USD, EUR)
* Product Description
* Product Condition

=== Wanted ===

==== eBay ====
* http://www.wantitnow.ebay.com
* category
* item number
* buyer nickname
* feedback
* date
* duration
* title
* description
* location
* condition
* price

==== Craigslist ====
* http://www.craigslist.org/wan/
* email
* duration
* date
* category
* title
* description
* location
* condition
* images
* price

== Previous Schemas and Formats ==

==== eBay ====
* http://developer.ebay.com/DevZone/XML/docs/WSDL/index.htm
* http://pages.ebay.com/help/sell/export-structure.html

==== Amazon ====
* http://www.amazon.com/gp/aws/sdk/?v=2005%2d07%2d26&s=AWSEcommerceService

==== Micropayment Markup ====
* http://www.w3.org/TR/Micropayment-Markup/

==== FOAF-Shop ====
* http://rdfweb.org/people/danbri/rdfweb/danbri-foafshop.rdf

==== Froogle ====
* http://www.google.com/froogle/merchants/advanced_feed_instructions.html

==== Yahoo Shopping ====
* http://productsubmit.adcentral.yahoo.com/sspi/us/spec/

==== Become.com ====
* http://www.become.com/merchant/Product_Feed_Specification_5_05_05.pdf

==== MySimon ====
* http://shopper.cnet.com/html/partners/a_feed.html#guidelines

== Related Initiatives ==

The following is a list of related e-business initiatives. While the scope of these projects is much larger than the problem addressed here, they may provide good reference points for property and process naming conventions. Included primarily for completeness.

* [http://www.w3.org/ECommerce/ W3C Electronic Commerce Interest Group] The role of W3C is to focus on core infrastructure technologies for Electronic Commerce and identify common infrastructure needed in this area.

* [http://www.commerce.net CommerceNet] CommerceNet is a non-profit membership organization meeting the evolving needs of companies doing electronic commerce.

* [http://www.ebxml.org ebXML] ebXML (Electronic Business using eXtensible Markup Language), is a modular suite of specifications that enables enterprises of any size and in any geographical location to conduct business over the Internet.

* [http://www.biztalk.org BizTalk] The BizTalk Framework is an XML framework for application integration and electronic commerce. It includes a design framework for implementing an XML schema and a set of XML tags used in messages sent between applications.

* [http://xml.coverpages.org/ecml.html ECML] The Electronic Commerce Modeling Language provides a simple set of guidelines for web merchants that will enable digital wallets from multiple vendors to automate the exchange of information between users and merchants.

* [http://www.iotp.org IOTP] The Open Trading Protocol was developed by a number of organizations, working cooperatively to make widespread Internet trading a convenient and secure reality.

* [http://www.udef.org UDEF] The Universal Data Element Framework is a cross-industry metadata identification strategy designed to facilitate convergence and interoperability among e-business and other standards.

* [http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ubl UBL] UBL, the Universal Business Language, is the product of an international effort to define a royalty-free library of standard electronic XML business documents such as purchase orders and invoices.

* [http://www.rosettanet.org RosettaNet] A self-funded, non-profit organization, RosettaNet is a consortium of major Computer and Consumer Electronics, Electronic Components, Semiconductor Manufacturing, Telecommunications and Logistics companies working to create and implement industry-wide, open e-business process standards. These standards form a common e-business language, aligning processes between supply chain partners on a global basis.

listing-examples

2005-08-29T17:11:52Z

Emiliano: /* Mercado Libre */

= Listing Examples =

This is an exploratory page to document listing (e.g. For Sale, Wanted) examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary feed formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed listings microformat.

== Contributors ==

* Trevor O'Reilly
* Emiliano Martínez Luque

== Examples in the Wild ==

=== For Sale ===

==== Craigslist ====
* http://www.craigslist.org/sss/
* email
* duration
* date
* category
* title
* description
* location
* condition
* images
* price
* availability

==== Amazon ====
* http://www.amazon.com/exec/obidos/ASIN/0735712018
* http://www.amazon.com/gp/aws/sdk/main.html/103-0842473-2772652?s=AWSEcommerceService&v=2005-07-26&p=ApiReference/SmallResponseGroup
* http://www.amazon.com/gp/aws/sdk/main.html/103-0842473-2772652?s=AWSEcommerceService&v=2005-07-26&p=ApiReference/OfferFullResponseGroup

==== Powazek ====
* http://www.powazek.com/2005/01/000485.html
* email
* date
* title
* description
* image
* location
* condition
* price
* availability

==== 37signals ====
* http://www.37signals.com/svn/archives2/for_sale_hp_laserjet_4000n_and_a_1ghz_powermac_g4_tower.php
* email
* date
* title
* description
* location
* condition
* price
* availability

==== Mercado Libre ====
* http://www.mercadolibre.com.ar/jm/item?site=MLA&id=17910319
* http://www.mercadolibre.com.ar/jm/item?site=MLA&id=17902804
* Price Ammount
* Price Currency
* Financing Options (? may or may not exist)
* Merchant/Seller Name
* Merchant/Seller Rating (Within Mercado Libre)
* Product Condition (Used|New)
* Location (Province)
* Country (Implied by Navigation. Country is selected when accesing mercadolibre.com)
* Product Name
* Product Photo
* Product Description
* Offer Ending Date
* Item# (MercadoLibre ID)

==== Segunda Mano ====
* http://www.segundamano.com.ar/detalles/asp/informatica_y_comunicaciones/cámaras_digitales/venta/13083319.htm
* http://www.segundamano.com.ar/detalles/asp/informatica_y_comunicaciones/cámaras_digitales/venta/13084677.htm
* http://www.segundamano.com.ar/detalles/asp/automotores/motos/venta/13086663.htm
* Price Ammount
* Price Currency
* Product Description
* Seller Telephone
* Publish Date
* Province (?)
* City (?)
* Country (Implied by Navigation. Country is selected when accesing segundamano.com)
* Product Specific Data ( ie: Model, Year, Brand for Cars or Motorcycles. Varies by Product type. )

=== Wanted ===

==== eBay ====
* http://www.wantitnow.ebay.com
* category
* item number
* buyer nickname
* feedback
* date
* duration
* title
* description
* location
* condition
* price

==== Craigslist ====
* http://www.craigslist.org/wan/
* email
* duration
* date
* category
* title
* description
* location
* condition
* images
* price

== Previous Schemas and Formats ==

==== eBay ====
* http://developer.ebay.com/DevZone/XML/docs/WSDL/index.htm
* http://pages.ebay.com/help/sell/export-structure.html

==== Amazon ====
* http://www.amazon.com/gp/aws/sdk/?v=2005%2d07%2d26&s=AWSEcommerceService

==== Micropayment Markup ====
* http://www.w3.org/TR/Micropayment-Markup/

==== FOAF-Shop ====
* http://rdfweb.org/people/danbri/rdfweb/danbri-foafshop.rdf

==== Froogle ====
* http://www.google.com/froogle/merchants/advanced_feed_instructions.html

==== Yahoo Shopping ====
* http://productsubmit.adcentral.yahoo.com/sspi/us/spec/

==== Become.com ====
* http://www.become.com/merchant/Product_Feed_Specification_5_05_05.pdf

==== MySimon ====
* http://shopper.cnet.com/html/partners/a_feed.html#guidelines

== Related Initiatives ==

The following is a list of related e-business initiatives. While the scope of these projects is much larger than the problem addressed here, they may provide good reference points for property and process naming conventions. Included primarily for completeness.

* [http://www.w3.org/ECommerce/ W3C Electronic Commerce Interest Group] The role of W3C is to focus on core infrastructure technologies for Electronic Commerce and identify common infrastructure needed in this area.

* [http://www.commerce.net CommerceNet] CommerceNet is a non-profit membership organization meeting the evolving needs of companies doing electronic commerce.

* [http://www.ebxml.org ebXML] ebXML (Electronic Business using eXtensible Markup Language), is a modular suite of specifications that enables enterprises of any size and in any geographical location to conduct business over the Internet.

* [http://www.biztalk.org BizTalk] The BizTalk Framework is an XML framework for application integration and electronic commerce. It includes a design framework for implementing an XML schema and a set of XML tags used in messages sent between applications.

* [http://xml.coverpages.org/ecml.html ECML] The Electronic Commerce Modeling Language provides a simple set of guidelines for web merchants that will enable digital wallets from multiple vendors to automate the exchange of information between users and merchants.

* [http://www.iotp.org IOTP] The Open Trading Protocol was developed by a number of organizations, working cooperatively to make widespread Internet trading a convenient and secure reality.

* [http://www.udef.org UDEF] The Universal Data Element Framework is a cross-industry metadata identification strategy designed to facilitate convergence and interoperability among e-business and other standards.

* [http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ubl UBL] UBL, the Universal Business Language, is the product of an international effort to define a royalty-free library of standard electronic XML business documents such as purchase orders and invoices.

* [http://www.rosettanet.org RosettaNet] A self-funded, non-profit organization, RosettaNet is a consortium of major Computer and Consumer Electronics, Electronic Components, Semiconductor Manufacturing, Telecommunications and Logistics companies working to create and implement industry-wide, open e-business process standards. These standards form a common e-business language, aligning processes between supply chain partners on a global basis.

listing-examples

2005-08-29T17:08:00Z

Emiliano: /* Segunda Mano */

= Listing Examples =

This is an exploratory page to document listing (e.g. For Sale, Wanted) examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary feed formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed listings microformat.

== Contributors ==

* Trevor O'Reilly
* Emiliano Martínez Luque

== Examples in the Wild ==

=== For Sale ===

==== Craigslist ====
* http://www.craigslist.org/sss/
* email
* duration
* date
* category
* title
* description
* location
* condition
* images
* price
* availability

==== Amazon ====
* http://www.amazon.com/exec/obidos/ASIN/0735712018
* http://www.amazon.com/gp/aws/sdk/main.html/103-0842473-2772652?s=AWSEcommerceService&v=2005-07-26&p=ApiReference/SmallResponseGroup
* http://www.amazon.com/gp/aws/sdk/main.html/103-0842473-2772652?s=AWSEcommerceService&v=2005-07-26&p=ApiReference/OfferFullResponseGroup

==== Powazek ====
* http://www.powazek.com/2005/01/000485.html
* email
* date
* title
* description
* image
* location
* condition
* price
* availability

==== 37signals ====
* http://www.37signals.com/svn/archives2/for_sale_hp_laserjet_4000n_and_a_1ghz_powermac_g4_tower.php
* email
* date
* title
* description
* location
* condition
* price
* availability

==== Mercado Libre ====
* http://www.mercadolibre.com.ar/jm/item?site=MLA&id=17910319
* http://www.mercadolibre.com.ar/jm/item?site=MLA&id=17902804
* Price Ammount
* Price Currency
* Financing Options (? may or may not exist)
* Merchant/Seller Name
* Merchant/Seller Rating (Within Mercado Libre)
* Product Condition (Used|New)
* Location (Province)
* Country (Implied by Navigation. Country is selected when accesing mercadolibre.com)
* Product Name
* Product Photo
* Offer Ending Date
* Item# (MercadoLibre ID)

==== Segunda Mano ====
* http://www.segundamano.com.ar/detalles/asp/informatica_y_comunicaciones/cámaras_digitales/venta/13083319.htm
* http://www.segundamano.com.ar/detalles/asp/informatica_y_comunicaciones/cámaras_digitales/venta/13084677.htm
* http://www.segundamano.com.ar/detalles/asp/automotores/motos/venta/13086663.htm
* Price Ammount
* Price Currency
* Product Description
* Seller Telephone
* Publish Date
* Province (?)
* City (?)
* Country (Implied by Navigation. Country is selected when accesing segundamano.com)
* Product Specific Data ( ie: Model, Year, Brand for Cars or Motorcycles. Varies by Product type. )

=== Wanted ===

==== eBay ====
* http://www.wantitnow.ebay.com
* category
* item number
* buyer nickname
* feedback
* date
* duration
* title
* description
* location
* condition
* price

==== Craigslist ====
* http://www.craigslist.org/wan/
* email
* duration
* date
* category
* title
* description
* location
* condition
* images
* price

== Previous Schemas and Formats ==

==== eBay ====
* http://developer.ebay.com/DevZone/XML/docs/WSDL/index.htm
* http://pages.ebay.com/help/sell/export-structure.html

==== Amazon ====
* http://www.amazon.com/gp/aws/sdk/?v=2005%2d07%2d26&s=AWSEcommerceService

==== Micropayment Markup ====
* http://www.w3.org/TR/Micropayment-Markup/

==== FOAF-Shop ====
* http://rdfweb.org/people/danbri/rdfweb/danbri-foafshop.rdf

==== Froogle ====
* http://www.google.com/froogle/merchants/advanced_feed_instructions.html

==== Yahoo Shopping ====
* http://productsubmit.adcentral.yahoo.com/sspi/us/spec/

==== Become.com ====
* http://www.become.com/merchant/Product_Feed_Specification_5_05_05.pdf

==== MySimon ====
* http://shopper.cnet.com/html/partners/a_feed.html#guidelines

== Related Initiatives ==

The following is a list of related e-business initiatives. While the scope of these projects is much larger than the problem addressed here, they may provide good reference points for property and process naming conventions. Included primarily for completeness.

* [http://www.w3.org/ECommerce/ W3C Electronic Commerce Interest Group] The role of W3C is to focus on core infrastructure technologies for Electronic Commerce and identify common infrastructure needed in this area.

* [http://www.commerce.net CommerceNet] CommerceNet is a non-profit membership organization meeting the evolving needs of companies doing electronic commerce.

* [http://www.ebxml.org ebXML] ebXML (Electronic Business using eXtensible Markup Language), is a modular suite of specifications that enables enterprises of any size and in any geographical location to conduct business over the Internet.

* [http://www.biztalk.org BizTalk] The BizTalk Framework is an XML framework for application integration and electronic commerce. It includes a design framework for implementing an XML schema and a set of XML tags used in messages sent between applications.

* [http://xml.coverpages.org/ecml.html ECML] The Electronic Commerce Modeling Language provides a simple set of guidelines for web merchants that will enable digital wallets from multiple vendors to automate the exchange of information between users and merchants.

* [http://www.iotp.org IOTP] The Open Trading Protocol was developed by a number of organizations, working cooperatively to make widespread Internet trading a convenient and secure reality.

* [http://www.udef.org UDEF] The Universal Data Element Framework is a cross-industry metadata identification strategy designed to facilitate convergence and interoperability among e-business and other standards.

* [http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ubl UBL] UBL, the Universal Business Language, is the product of an international effort to define a royalty-free library of standard electronic XML business documents such as purchase orders and invoices.

* [http://www.rosettanet.org RosettaNet] A self-funded, non-profit organization, RosettaNet is a consortium of major Computer and Consumer Electronics, Electronic Components, Semiconductor Manufacturing, Telecommunications and Logistics companies working to create and implement industry-wide, open e-business process standards. These standards form a common e-business language, aligning processes between supply chain partners on a global basis.

listing-examples

2005-08-29T17:07:47Z

Emiliano: /* Segunda Mano */

= Listing Examples =

This is an exploratory page to document listing (e.g. For Sale, Wanted) examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary feed formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed listings microformat.

== Contributors ==

* Trevor O'Reilly
* Emiliano Martínez Luque

== Examples in the Wild ==

=== For Sale ===

==== Craigslist ====
* http://www.craigslist.org/sss/
* email
* duration
* date
* category
* title
* description
* location
* condition
* images
* price
* availability

==== Amazon ====
* http://www.amazon.com/exec/obidos/ASIN/0735712018
* http://www.amazon.com/gp/aws/sdk/main.html/103-0842473-2772652?s=AWSEcommerceService&v=2005-07-26&p=ApiReference/SmallResponseGroup
* http://www.amazon.com/gp/aws/sdk/main.html/103-0842473-2772652?s=AWSEcommerceService&v=2005-07-26&p=ApiReference/OfferFullResponseGroup

==== Powazek ====
* http://www.powazek.com/2005/01/000485.html
* email
* date
* title
* description
* image
* location
* condition
* price
* availability

==== 37signals ====
* http://www.37signals.com/svn/archives2/for_sale_hp_laserjet_4000n_and_a_1ghz_powermac_g4_tower.php
* email
* date
* title
* description
* location
* condition
* price
* availability

==== Mercado Libre ====
* http://www.mercadolibre.com.ar/jm/item?site=MLA&id=17910319
* http://www.mercadolibre.com.ar/jm/item?site=MLA&id=17902804
* Price Ammount
* Price Currency
* Financing Options (? may or may not exist)
* Merchant/Seller Name
* Merchant/Seller Rating (Within Mercado Libre)
* Product Condition (Used|New)
* Location (Province)
* Country (Implied by Navigation. Country is selected when accesing mercadolibre.com)
* Product Name
* Product Photo
* Offer Ending Date
* Item# (MercadoLibre ID)

==== Segunda Mano ====
* http://www.segundamano.com.ar/detalles/asp/informatica_y_comunicaciones/cámaras_digitales/venta/13083319.htm
* http://www.segundamano.com.ar/detalles/asp/informatica_y_comunicaciones/cámaras_digitales/venta/13084677.htm
* http://www.segundamano.com.ar/detalles/asp/automotores/motos/venta/13086663.htm
* Price Ammount
* Price Currency
* Product Description
* Seller Telephone
* Publish Date
* Province (?)
* City (?)
* Country (Implied by Navigation. Country is selected when accesing mercadolibre.com)
* Product Specific Data ( ie: Model, Year, Brand for Cars or Motorcycles. Varies by Product type. )

=== Wanted ===

==== eBay ====
* http://www.wantitnow.ebay.com
* category
* item number
* buyer nickname
* feedback
* date
* duration
* title
* description
* location
* condition
* price

==== Craigslist ====
* http://www.craigslist.org/wan/
* email
* duration
* date
* category
* title
* description
* location
* condition
* images
* price

== Previous Schemas and Formats ==

==== eBay ====
* http://developer.ebay.com/DevZone/XML/docs/WSDL/index.htm
* http://pages.ebay.com/help/sell/export-structure.html

==== Amazon ====
* http://www.amazon.com/gp/aws/sdk/?v=2005%2d07%2d26&s=AWSEcommerceService

==== Micropayment Markup ====
* http://www.w3.org/TR/Micropayment-Markup/

==== FOAF-Shop ====
* http://rdfweb.org/people/danbri/rdfweb/danbri-foafshop.rdf

==== Froogle ====
* http://www.google.com/froogle/merchants/advanced_feed_instructions.html

==== Yahoo Shopping ====
* http://productsubmit.adcentral.yahoo.com/sspi/us/spec/

==== Become.com ====
* http://www.become.com/merchant/Product_Feed_Specification_5_05_05.pdf

==== MySimon ====
* http://shopper.cnet.com/html/partners/a_feed.html#guidelines

== Related Initiatives ==

The following is a list of related e-business initiatives. While the scope of these projects is much larger than the problem addressed here, they may provide good reference points for property and process naming conventions. Included primarily for completeness.

* [http://www.w3.org/ECommerce/ W3C Electronic Commerce Interest Group] The role of W3C is to focus on core infrastructure technologies for Electronic Commerce and identify common infrastructure needed in this area.

* [http://www.commerce.net CommerceNet] CommerceNet is a non-profit membership organization meeting the evolving needs of companies doing electronic commerce.

* [http://www.ebxml.org ebXML] ebXML (Electronic Business using eXtensible Markup Language), is a modular suite of specifications that enables enterprises of any size and in any geographical location to conduct business over the Internet.

* [http://www.biztalk.org BizTalk] The BizTalk Framework is an XML framework for application integration and electronic commerce. It includes a design framework for implementing an XML schema and a set of XML tags used in messages sent between applications.

* [http://xml.coverpages.org/ecml.html ECML] The Electronic Commerce Modeling Language provides a simple set of guidelines for web merchants that will enable digital wallets from multiple vendors to automate the exchange of information between users and merchants.

* [http://www.iotp.org IOTP] The Open Trading Protocol was developed by a number of organizations, working cooperatively to make widespread Internet trading a convenient and secure reality.

* [http://www.udef.org UDEF] The Universal Data Element Framework is a cross-industry metadata identification strategy designed to facilitate convergence and interoperability among e-business and other standards.

* [http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ubl UBL] UBL, the Universal Business Language, is the product of an international effort to define a royalty-free library of standard electronic XML business documents such as purchase orders and invoices.

* [http://www.rosettanet.org RosettaNet] A self-funded, non-profit organization, RosettaNet is a consortium of major Computer and Consumer Electronics, Electronic Components, Semiconductor Manufacturing, Telecommunications and Logistics companies working to create and implement industry-wide, open e-business process standards. These standards form a common e-business language, aligning processes between supply chain partners on a global basis.

listing-examples

2005-08-29T17:07:25Z

Emiliano: /* Mercado Libre */

= Listing Examples =

This is an exploratory page to document listing (e.g. For Sale, Wanted) examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary feed formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed listings microformat.

== Contributors ==

* Trevor O'Reilly
* Emiliano Martínez Luque

== Examples in the Wild ==

=== For Sale ===

==== Craigslist ====
* http://www.craigslist.org/sss/
* email
* duration
* date
* category
* title
* description
* location
* condition
* images
* price
* availability

==== Amazon ====
* http://www.amazon.com/exec/obidos/ASIN/0735712018
* http://www.amazon.com/gp/aws/sdk/main.html/103-0842473-2772652?s=AWSEcommerceService&v=2005-07-26&p=ApiReference/SmallResponseGroup
* http://www.amazon.com/gp/aws/sdk/main.html/103-0842473-2772652?s=AWSEcommerceService&v=2005-07-26&p=ApiReference/OfferFullResponseGroup

==== Powazek ====
* http://www.powazek.com/2005/01/000485.html
* email
* date
* title
* description
* image
* location
* condition
* price
* availability

==== 37signals ====
* http://www.37signals.com/svn/archives2/for_sale_hp_laserjet_4000n_and_a_1ghz_powermac_g4_tower.php
* email
* date
* title
* description
* location
* condition
* price
* availability

==== Mercado Libre ====
* http://www.mercadolibre.com.ar/jm/item?site=MLA&id=17910319
* http://www.mercadolibre.com.ar/jm/item?site=MLA&id=17902804
* Price Ammount
* Price Currency
* Financing Options (? may or may not exist)
* Merchant/Seller Name
* Merchant/Seller Rating (Within Mercado Libre)
* Product Condition (Used|New)
* Location (Province)
* Country (Implied by Navigation. Country is selected when accesing mercadolibre.com)
* Product Name
* Product Photo
* Offer Ending Date
* Item# (MercadoLibre ID)

==== Segunda Mano ====
* http://www.segundamano.com.ar/detalles/asp/informatica_y_comunicaciones/cámaras_digitales/venta/13083319.htm
* http://www.segundamano.com.ar/detalles/asp/informatica_y_comunicaciones/cámaras_digitales/venta/13084677.htm
* http://www.segundamano.com.ar/detalles/asp/automotores/motos/venta/13086663.htm
* Price Ammount
* Price Currency
* Product Description
* Seller Telephone
* Publish Date
* Province (?)
* City (?)
* Product Specific Data ( ie: Model, Year, Brand for Cars or Motorcycles. Varies by Product type. )

=== Wanted ===

==== eBay ====
* http://www.wantitnow.ebay.com
* category
* item number
* buyer nickname
* feedback
* date
* duration
* title
* description
* location
* condition
* price

==== Craigslist ====
* http://www.craigslist.org/wan/
* email
* duration
* date
* category
* title
* description
* location
* condition
* images
* price

== Previous Schemas and Formats ==

==== eBay ====
* http://developer.ebay.com/DevZone/XML/docs/WSDL/index.htm
* http://pages.ebay.com/help/sell/export-structure.html

==== Amazon ====
* http://www.amazon.com/gp/aws/sdk/?v=2005%2d07%2d26&s=AWSEcommerceService

==== Micropayment Markup ====
* http://www.w3.org/TR/Micropayment-Markup/

==== FOAF-Shop ====
* http://rdfweb.org/people/danbri/rdfweb/danbri-foafshop.rdf

==== Froogle ====
* http://www.google.com/froogle/merchants/advanced_feed_instructions.html

==== Yahoo Shopping ====
* http://productsubmit.adcentral.yahoo.com/sspi/us/spec/

==== Become.com ====
* http://www.become.com/merchant/Product_Feed_Specification_5_05_05.pdf

==== MySimon ====
* http://shopper.cnet.com/html/partners/a_feed.html#guidelines

== Related Initiatives ==

The following is a list of related e-business initiatives. While the scope of these projects is much larger than the problem addressed here, they may provide good reference points for property and process naming conventions. Included primarily for completeness.

* [http://www.w3.org/ECommerce/ W3C Electronic Commerce Interest Group] The role of W3C is to focus on core infrastructure technologies for Electronic Commerce and identify common infrastructure needed in this area.

* [http://www.commerce.net CommerceNet] CommerceNet is a non-profit membership organization meeting the evolving needs of companies doing electronic commerce.

* [http://www.ebxml.org ebXML] ebXML (Electronic Business using eXtensible Markup Language), is a modular suite of specifications that enables enterprises of any size and in any geographical location to conduct business over the Internet.

* [http://www.biztalk.org BizTalk] The BizTalk Framework is an XML framework for application integration and electronic commerce. It includes a design framework for implementing an XML schema and a set of XML tags used in messages sent between applications.

* [http://xml.coverpages.org/ecml.html ECML] The Electronic Commerce Modeling Language provides a simple set of guidelines for web merchants that will enable digital wallets from multiple vendors to automate the exchange of information between users and merchants.

* [http://www.iotp.org IOTP] The Open Trading Protocol was developed by a number of organizations, working cooperatively to make widespread Internet trading a convenient and secure reality.

* [http://www.udef.org UDEF] The Universal Data Element Framework is a cross-industry metadata identification strategy designed to facilitate convergence and interoperability among e-business and other standards.

* [http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ubl UBL] UBL, the Universal Business Language, is the product of an international effort to define a royalty-free library of standard electronic XML business documents such as purchase orders and invoices.

* [http://www.rosettanet.org RosettaNet] A self-funded, non-profit organization, RosettaNet is a consortium of major Computer and Consumer Electronics, Electronic Components, Semiconductor Manufacturing, Telecommunications and Logistics companies working to create and implement industry-wide, open e-business process standards. These standards form a common e-business language, aligning processes between supply chain partners on a global basis.

listing-examples

2005-08-29T17:00:00Z

Emiliano: Added mercadolibre.com and segundamano.com Latinamerican listing sites and Amazon Web Services Api Responses for future reference

= Listing Examples =

This is an exploratory page to document listing (e.g. For Sale, Wanted) examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary feed formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed listings microformat.

== Contributors ==

* Trevor O'Reilly
* Emiliano Martínez Luque

== Examples in the Wild ==

=== For Sale ===

==== Craigslist ====
* http://www.craigslist.org/sss/
* email
* duration
* date
* category
* title
* description
* location
* condition
* images
* price
* availability

==== Amazon ====
* http://www.amazon.com/exec/obidos/ASIN/0735712018
* http://www.amazon.com/gp/aws/sdk/main.html/103-0842473-2772652?s=AWSEcommerceService&v=2005-07-26&p=ApiReference/SmallResponseGroup
* http://www.amazon.com/gp/aws/sdk/main.html/103-0842473-2772652?s=AWSEcommerceService&v=2005-07-26&p=ApiReference/OfferFullResponseGroup

==== Powazek ====
* http://www.powazek.com/2005/01/000485.html
* email
* date
* title
* description
* image
* location
* condition
* price
* availability

==== 37signals ====
* http://www.37signals.com/svn/archives2/for_sale_hp_laserjet_4000n_and_a_1ghz_powermac_g4_tower.php
* email
* date
* title
* description
* location
* condition
* price
* availability

==== Mercado Libre ====
* http://www.mercadolibre.com.ar/jm/item?site=MLA&id=17910319
* http://www.mercadolibre.com.ar/jm/item?site=MLA&id=17902804
* Price Ammount
* Price Currency
* Financing Options (? may or may not exist)
* Merchant/Seller Name
* Merchant/Seller Rating (Within Mercado Libre)
* Product Condition (Used|New)
* Location (Province)
* Product Name
* Product Photo
* Offer Ending Date
* Item# (MercadoLibre ID)

==== Segunda Mano ====
* http://www.segundamano.com.ar/detalles/asp/informatica_y_comunicaciones/cámaras_digitales/venta/13083319.htm
* http://www.segundamano.com.ar/detalles/asp/informatica_y_comunicaciones/cámaras_digitales/venta/13084677.htm
* http://www.segundamano.com.ar/detalles/asp/automotores/motos/venta/13086663.htm
* Price Ammount
* Price Currency
* Product Description
* Seller Telephone
* Publish Date
* Province (?)
* City (?)
* Product Specific Data ( ie: Model, Year, Brand for Cars or Motorcycles. Varies by Product type. )

=== Wanted ===

==== eBay ====
* http://www.wantitnow.ebay.com
* category
* item number
* buyer nickname
* feedback
* date
* duration
* title
* description
* location
* condition
* price

==== Craigslist ====
* http://www.craigslist.org/wan/
* email
* duration
* date
* category
* title
* description
* location
* condition
* images
* price

== Previous Schemas and Formats ==

==== eBay ====
* http://developer.ebay.com/DevZone/XML/docs/WSDL/index.htm
* http://pages.ebay.com/help/sell/export-structure.html

==== Amazon ====
* http://www.amazon.com/gp/aws/sdk/?v=2005%2d07%2d26&s=AWSEcommerceService

==== Micropayment Markup ====
* http://www.w3.org/TR/Micropayment-Markup/

==== FOAF-Shop ====
* http://rdfweb.org/people/danbri/rdfweb/danbri-foafshop.rdf

==== Froogle ====
* http://www.google.com/froogle/merchants/advanced_feed_instructions.html

==== Yahoo Shopping ====
* http://productsubmit.adcentral.yahoo.com/sspi/us/spec/

==== Become.com ====
* http://www.become.com/merchant/Product_Feed_Specification_5_05_05.pdf

==== MySimon ====
* http://shopper.cnet.com/html/partners/a_feed.html#guidelines

== Related Initiatives ==

The following is a list of related e-business initiatives. While the scope of these projects is much larger than the problem addressed here, they may provide good reference points for property and process naming conventions. Included primarily for completeness.

* [http://www.w3.org/ECommerce/ W3C Electronic Commerce Interest Group] The role of W3C is to focus on core infrastructure technologies for Electronic Commerce and identify common infrastructure needed in this area.

* [http://www.commerce.net CommerceNet] CommerceNet is a non-profit membership organization meeting the evolving needs of companies doing electronic commerce.

* [http://www.ebxml.org ebXML] ebXML (Electronic Business using eXtensible Markup Language), is a modular suite of specifications that enables enterprises of any size and in any geographical location to conduct business over the Internet.

* [http://www.biztalk.org BizTalk] The BizTalk Framework is an XML framework for application integration and electronic commerce. It includes a design framework for implementing an XML schema and a set of XML tags used in messages sent between applications.

* [http://xml.coverpages.org/ecml.html ECML] The Electronic Commerce Modeling Language provides a simple set of guidelines for web merchants that will enable digital wallets from multiple vendors to automate the exchange of information between users and merchants.

* [http://www.iotp.org IOTP] The Open Trading Protocol was developed by a number of organizations, working cooperatively to make widespread Internet trading a convenient and secure reality.

* [http://www.udef.org UDEF] The Universal Data Element Framework is a cross-industry metadata identification strategy designed to facilitate convergence and interoperability among e-business and other standards.

* [http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ubl UBL] UBL, the Universal Business Language, is the product of an international effort to define a royalty-free library of standard electronic XML business documents such as purchase orders and invoices.

* [http://www.rosettanet.org RosettaNet] A self-funded, non-profit organization, RosettaNet is a consortium of major Computer and Consumer Electronics, Electronic Components, Semiconductor Manufacturing, Telecommunications and Logistics companies working to create and implement industry-wide, open e-business process standards. These standards form a common e-business language, aligning processes between supply chain partners on a global basis.