Microformats Wiki - User contributions [en]

User:D4rr3ll

2006-09-20T07:56:12Z

D4rr3ll:

hello!

I'm basically interested in the hListing format in relation to one of my sites [http://www.dealtagger.com/ dealtagger].

hlisting-feedback

2006-09-20T07:39:25Z

D4rr3ll: /* Validator */

== Default Action ==
I think it's good form to have a default for every required field, since someone out there is going to drop any given requried field in the land of microformats. In that spirit, the default for listing type is offer, since wanted ads are << 10% in the real world. What I don't know is what the default action should be; the most neutral of them is ''announce'', which I am using in my parser.

-- Rohit

== Donations ==

Sell and Rent are obvious enough verbs; what does Trade mean, though? Barter? And what about one-sided gifts, like donations or "free to recycle"? Should we replace Trade and offer Donate in its place?

-- Rohit

== Desire to Inherit Context ==

When it comes to blog posting, I’d like to see us address the following:

1. '''Less is more'''. Or in reverse, people are lazy, and the less fields they need to fill in order to sell a couch or find a date, the more they'll use the plugin. So I'm trying to visualize how this plays in with the user interface and how we can keep it as simple as possible.

2. '''DRY'''. We want to capture as much information as possible from what is already available in the blog post. We already have summary (title), listing date/time (post date/time), permalink, author information, tags/categories.

3. '''Keep it simple'''. And here I'm talking about setup and being able to extend your blog's functionality without too much fuss. This one is a bit more tricky, so I'll go into details.

WordPress uses templates to render the blog post. The template then calls the WordPress API to render the title, a second call to render the content, and another call to render any additional metadata (e.g.
publish date, categories, author). These separate calls allow people to play with the formatting and apply any styling they like.

The way uPress works, is by processing the blog post before it goes back to the filter, creating the hEvent (to be: hListing) element around it, and adding any relevant fields into the blog post. So what you fill in the form, finds its way to the post content. As a result, setting up the plugin requires two steps: drop it to the plugins directory, and activate.

Unfortunately, I only get to process the content of the post. I can't easily include the title inside the hListing element, or any other metadata about the post, even though I have access to it. If I duplicate that information, the post stops being readable. And to wrap the entire post (not just body) inside a microformat element, I need to tweak the template. Except people use different templates, and I can't tweak all of them.

So the more context we use, the better the plugin becomes.

-- Assaf Arkin

== '''Make Info/Photo fields Optional''' ==

WordPress has a great WYSIWYG editor that lets you drag & drop images.
But the only semantic identification it uses is the HTML <img> element.
So how do we get a photo to be identified from all the images inside the description?

1. Manually edit the HTML that WordPress creates to add the class.
2. Add another UI doubling the one already used by WordPress, sans drag & drop, strictly for images designated as photos.
3. Tag every single image as photo.
4. Have the crawler interpret every single image as photo.

I'm not sure we want to push the complexity to the edge, that's like asking people to create only valid XHTML pages and not rendering anything that refuses to validate. This is about humans first, machines second. If complexity needs to exist, it should be not in the blog, but in the crawlers.

-- Assaf Arkin

== '''On hReview''' ==

This draft was heavily influenced by hReview. That's a good thing. We don’t want to duplicate efforts; are learning from the mistakes of others; and converging on a cohesive set of specifications. I want to eventually add hReview and hCard to my plugin. So this strategy of borrowing from existing microformats helps me get it done quicker. It took me all of five minutes to leverage address formatting from hEvent.

But we also need to recognize that hReview could also be more blogging friendly. The specification is great, but the implementations are lacking. I think the reason is that hReview was designed for greenfield applications that specifically deal with emitting reviews. The design did not take into consideration applications that already deal with content, but want to supplement it with reviews, listings, etc. There's no mention of such consideration in the spec.

We want to appeal to the wide populace of bloggers who just want to get stuff done. Rather than put the burden on millions of bloggers out there, we should place the burden on the few companies developing crawlers.

What would Tantek say? I think he'd ask us to focus on use cases, real examples. I'm presenting one such example. The use case involves a blogger who just wants to sell something on their blog, with the minimum amount of effort and cognitive friction. They want the listing to be discovered, aggregated and searched by others.

-- Assaf Arkin

== '''Neighborhood Name''' ==

With the exception of housing, most classified listings don’t contain a specific address (e.g., if I’m selling my couch, you don’t need to know where I live in the listing). Some location information, however, is important. In most suburban areas, the name of the town is sufficient. In cities, however, neighborhood is important and more contextually relevant than zipcode (simply a region defined by the post office).

This is a tough problem that needs to be solved but outside the context of this discussion. We think there are other cases the could benefit from it, including hReview and hEvent. We recommend that this debate be surface in the adr microformation discussion (e.g., perhaps extend the locality field (city) to optionally include a neighborhood)

-- Craig Donato & Assaf Arkin

== '''Listing Action, Listing Type, Item Type''' ==

We heavily debated how to classify a listing. Search engines or marketplaces typically need to understand what type of listing it is (e.g., personal ad, house for sale, music) to effectively reference or index a listing.

We initially considered proposing a single category field that contained tags (in addition to the tags field). Not only did this seem duplicative, it also seemed like too much of a good thing. In a previous project, Assaf managed to successfully overload everything into tags (including dates and locations), and run time-based and location-based searches, and ended up concluding it's a bad idea.

We eventually decided to propose the use three parametric field that when used together could define any type of listing independent of the words use to describe. These ended up being: listing-type (are you offering something or looking for something; listing-action (are you trying to sell, rent, or announce something); and item type (what item is referenced by the action such as a job opening, product, housing). By making small modifications to this vocabulary, users can specify an extremely wide range of potential transactions. This seemed more feasible given that the UI used to produce the hListing could abstract some of this from the user (as Assaf demonstrated in his demo plugin).

For example:

{|
!Desired Transaction
!Listing Type
!Listing Action
!Item Type
|-
|Merchandise For Sale
|Offer
|Sell
|Product
|-
|Looking to Buy Merchandise
|Wanted
|Sell
|Product
|-
|Selling Tickets
|Offer
|Sell
|Event
|-
|Apartment For Rent
|Offer
|Rent
|Housing
|-
|Looking for Apartment
|Wanted
|Rent
|Housing
|-
|Room for Rent (Roommate)
|Offer
|Rent
|Housing
|-
|Looking for a Date
|Offer||Wanted
|Announce, Meet
|-
|Job Opening
|Offer
|Announce
|Opening
|-
|Looking for a Job (Resume)
|Wanted
|Announce
|Opening
|-
|Music Lessons
|Offer
|Service
|Business
|-
|Trade Couch for TV
|Offer
|Trade
|Product
|-
|Pet for Adoption
|Offer
|Announce
|Animal?
|}
-- Craig Donato

== Eliminate Item Type ==

Can we eliminate item type and simply use tags? Or perhaps inferred item type from the item info?

== hClassified? ==

There are meanings of "listing" that wouldn't fit this format.. might not hClassified be a more descriptive name? It's not overconstraining... 'classifieds' being very broad in practice and the meaning very informally/functionally defined. Or has the 'listing' train left the station?

== What about retail? ==

Retail is out of scope for hListing, sure -- but what microformat should a retail seller of (e.g. mass-produced) goods use? hForSale? hProduct?

== Retail ==

Funnily enough, hProduct is always something that I've thought about.

I'd be bold enough to say that it will be one of the main uses of microformats in the future. Imagine the amount of shops, price comparison, product review and many more type of sites. It doesn't have to be for profit, it could just be someones product, on their site, that they are displaying.

I'd be willing to help and continue development of a spec for 'hProduct'.

Adam Craven

== Thubnail Class ==
Hello. I'm not sure I understand everything correctly, but from reading the hListing proposal it seems that one should put pictures of the listed subject into the "photo" class. I'm wondering if also we may wish to have a "thumnail" class or perhaps something like "photo-thumbnail" to denote thumbnail images.
-Andrew

== Validator ==
Perhaps to foster development of this type, someone (who knows a lot more about microformats than I) should put a validator type page out there. I realize that microformats, by their nature are a loose specification (it's not as strict as validating say an XML rss feed). But having something that I can use to at least verify that what I'm coding is actually recognized as an hListing by someone other than myself would be very helpful.
-Andrew

Blogmatrix have added hListing to their microformats parser [http://tools.blogmatrix.com/extract/ here]
-d4rr3ll

hlisting

2006-09-20T07:38:06Z

D4rr3ll: /* Examples in the Wild */

<h1> hListing Proposal </h1>

hListing is a proposal for an open, distributed listings (UK English: small-ads) format suitable for embedding in (X)HTML, Atom, RSS, and arbitrary XML. hListing would be one of several [[microformats]] open standards.

__TOC__

== Draft Proposal 2006-02-07 ==

===Editor===
* Rohit Khare, [http://commerce.net/ CommerceNet]

===Authors===
* Assaf Arkin, [http://blog.labnotes.org/ Labnotes]
* Craig Donato, [http://oodle.com/ Oodle]
* Rohit Khare, [http://commerce.net/ CommerceNet]

===Contributors===
* Tantek Çelik
* Ryan King

==Introduction==

Individuals and professionals are increasingly publishing their offerings online: whether as items for sale or rent (cars, homes, apartments), services for hire (music lessons, dog walker, plumber), openings (jobs, volunteers, extra spot in a book club) or personals (people looking for dates, companions, roommates). The goal of publishing (and promoting) these listings online is to seek out interested parties, often within a limited time period.

While descriptions of products and services are common on the Web, particularly on e-commerce sites, we are proposing an hListing microformat for sharing, searching, and syndicating the information that helps match up buyers and sellers. This proposal follows the common practices of trading sites such as Craigslist, eBay and newspaper classifieds.

If [[hreview|hReview]] is about an item and what you think of it, hListing is about an item and what you want to ''do'' with it.

=== Inspiration and Acknowledgments ===
Thanks to everyone who participated in the initial burst of hListing activity in August 2005, particularly Emiliano Martínez Luque and Trevor O'Reilly, for naming the effort and organizing the listing-{brainstorming, formats, examples} pages on the wiki. We would like to thank Tantek for an initial debate about whether to extend hReview or pursue an independent-though-similar hListing for our proposal.

=== Scope ===
Vibrant online marketplaces have been launched with little more than titles, prices, descriptions, and contact email addresses; we hope to kindle the same spirit of minimalism with this proposal to restart active discussion of what an hListing should be. Since we are venturing into a space that does not have “settled law” such as the vCard definitions hCard started with, we were inspired by hReview, another novel compound microformat that emerged from the microformats.org community process.

In particular, we note that both applications need a way to share informative descriptions of a product or service, including attribution of authorship and provenance of the item. if hReview is a microformat for one's opinion of a product or service, hListing helps share what one would like to ''do'' with it: sell it, rent it, trade it, perform that service, announce it, or, for people, to meet them. It can tell you how to contact the lister, and whether it is an item on offer or a wanted ad.

==== Out of Scope ====
We are focusing on providing "just enough" structure to enable matching, not to consummate transactions. This is distinct from the majority of formats described on the wiki under [[listing-examples]], which are specific enough to completely describe products for retail sale according to the idiosyncratic semantics of particular merchants and shopping engines. Instead of encoding retail-oriented fields such as UPCs, SKUs, and manufacturer part numbers, this proposal acknowledges that many listings are for "inventories of one" that may not have such precise abstractions.

Similarly, listings cannot aspire to describe prices and terms & conditions to the degree necessary to automate entire transactions or price comparisons. Some have terms beyond the pale of any B2B exchange protocols (e.g. "$50 ''obo''").

As in hReview, the concept of a “universal object identifier” is also out-of-scope for this effort. Unlike some of the “product feed” formats under [listing-examples], we avoided specifying any taxonomy for identifying or categorizing listings in favor of tags.

== Format ==
=== In General ===
The hListing format is based on a set of fields common to numerous listing sites and formats in use today on the web. Where possible field names have been chosen based on those defined by the related [[hreview|hReview]], [[hcard|hCard]], [[hcalendar|hCalendar]] standards.

=== Schema ===

An hListing schema should consist of the following:

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

==== Summary of Changes ====
By comparison to hReview:
* Item type and info have been preserved to describe the good, service, or person being offered.
* Item info expanded to take geo or adr for location of the item.
* Item description has become required, rather than item info or type. While reviews tend to apply to a range of products, listings "in the wild" can be ''sui generis,'' found with only a description and no other structured information.
* Rating has been removed.
* Lister, unlike Reviewer, can also have a telephone number -- but it must ''either'' be an hCard or the other fields.

Creating a listing requires adding transaction metadata:
* Type of transaction sought: whether the lister has or wants an item (sale or rent), a service, an opening, or a personal introduction.
* Dates of listing and expiry. Once taken, listings may be reposted with a modified dtexpired.
* Price has been called out specifically as an independent text field. It can include some terms & conditions.

==Field Details==
The fields of the hListing schema represent the following:

'''version''':: This optional field permits hListing publishers to specify a particular version of hListing that their content uses. By omitting this field, the publisher is stating that implementations may interpret the hListings according to any version of the hListing specification. The value for this proposal as of 6-Feb-2006 is "0.0," since it has no official standing yet.

===Transaction Metadata===
'''listing type''':: This required field indicates the desired matching: whether it’s about something that the lister has (offer) or wants (wanted). '''NOTE: This needs to be collapsed with listing action per the change made to the summary above.'''

'''listing action''':: This required field indicates the desired action for the listing: a permanent transfer (sale); transient use (rent); barter or donation (trade); to arrange an introduction (meet); publicize the existence of an event or vendor (announce); or to perform a service (service).

'''lister''':: The person or business who should be contacted about the listing, either in the form of an hCard or a shorthand notation of one or more formatted names (fn) and contact information (email, url, tel). Note that this is not necessarily the the same as the ''author'' of the listing.

'''dtlisted''':: This optional field MUST provide an ISO8601 absolute date time of when the listing was first made effective. This field SHOULD use UTC, but MAY use the time zone offset syntax. See [[datetime-design-pattern|datetime design pattern]].

'''dtexpired''':: This optional field MUST provide an ISO8601 absolute date time of when the listing will become ineffective. It MUST be later than dtlisted. This field SHOULD use UTC, but MAY use the time zone offset syntax. See [[datetime-design-pattern|datetime design pattern]].

<blockquote>
Note that this definition obviates the need for a “taken” listing action; when a listing is no longer valid, it can simply be deleted, or republished with an expiry date that has already passed. Republication may be desirable, to indicate that the listing is no longer available to forestall further inquiries. Keeping expiry orthogonal to listing-action permits archival use of web pages with hListings.
</blockquote>

'''location''':: This optional field contains the location of the item, which may be different than the location of the lister. This may be a full hCard with contact information, or a geolocation-specific microformat type.

<blockquote>
There is an separate discussion to be had about how either of these three microformats can best accommodate colloquial terminiology for “neighborhoods,” but this proposal does not break new ground by coining a new fields for that purpose.
</blockquote>

'''price''':: This optional text field describes the “advertised” price of the listing; it is not a binding offer, nor a complete transaction price. Floating point numbers found within this string may be extracted for sorting/indexing, as could adjacent currency symbols or ISO currency codes.

<blockquote>
Note that since price is such a general description, we have avoided promoting an additional “terms and conditions” field for elaborating on the price or terms of the deal (e.g. “dollars”, “best offer” “per month” “paypal only”). We suggest demoting it until proven that it needs to exist independently of either description (such as shipping rates) or price (which can just state “CAD$22/mo”).
</blockquote>

===Item Metadata===

'''item type''':: This optional field "type" provides the type of the item being ''listed'': one of the following: opening, housing, product, business, event, person, place, website, url.

<blockquote>
Note that the first two, housing and opening, are new and unique to hListing; the remainder are copied by reference from hReview. Similar to the note in hReview 0.2 for item types, the enumerated list of listing types is “under development and may be extended.”
</blockquote>

'''item info''':: This required field MUST have at a minimum the name ("fn" - the formatted text corresponding to the name) of the item , SHOULD provide at least one URI ("url") for the item, and MAY provide at least one URL to a photo or depiction ("photo") of the item. For items of type person or business, the item info (fn, url, photo) SHOULD be encapsulated in an hCard. Unique item IDs (e.g. ISBNs, UPCs) MAY be represented as a URN ("url") for the item.

===Content ===

'''summary''':: This optional text field serves as a title for listing.

'''description''':: This optional field contains the full text representing the written description of the item being listed. The field MAY include valid XHTML markup (e.g. paragraphs). User agents SHOULD preserve any markup.

'''tags''':: Tags are represented using a list of keywords or phrases (using the RelTag microformat for each individual keyword or phrase tag) that the reviewer associates with the item. The reviewer SHOULD provide tags relating to how they want the item categorized (e.g., “car, used, acura”, “job”, “real estate, 3BR”). The reviewer MAY also want to provide tags indicating payment terms (“dollars”, “paypal”).

'''permalink''':: This optional field is a URL for the hListing. In addition to using the <a href> tag for this field, the attribute rel="self bookmark" MUST be used to indicate that the hyperlink is a permalink for the review itself. If the hyperlink already contains a rel attribute, then the values self and bookmark MUST be included among the space-separated set of values in the attribute. Indexers MAY treat the permalink of a review as a unique ID in order to identify and collate the same listing from multiple sources (such as indexing a page multiple times). The permalink MAY also be used to indicate or imply the origin of the listing. Authors MAY use the classname of "permalink" on the element representing the permalink, but are not required to do so.

===Cross-cutting issues===
''Internationalization:'' Though there are many English-language tokens, they are only used as invisible class-names; user-visible listing information can be completely localized. N.b. that (X)HTML lang attribute rules still apply as usual, for multilingual aggregators of hListings.

The following field names have been reused from the [[hcard|hCard]] and [[hcalendar|hCalendar]] microformats: <code>version, summary, fn, url, email, photo, description, categories</code>. In addition, items and reviewers described by hCards MAY contain any hCard field. The rel value "self" has been reused from the [http://atompub.org/2005/07/11/draft-ietf-atompub-format-10.html Atom 1.0 specification].

==Contextual Defaults: A New Approach?==

Since listings may be embedded within blog postings, email, syndicated feeds, simple Web pages, or other microformats such as hAtom, to the degree possible, the following fields can be “inherited” from the context surrounding an hListing if absent:

* lister (author, contributor, From:)
* dtlisted (Date:)
* dtexpired (Expires:)
* summary (title)
* permalink (URI:, <base>)

By contrast, gazetteering is an example of ''ad hoc'' contextual defaulting that is '''not''' governed by this technique. Guessing that “Noe Valley” is in “San Francisco, CA” because the hCard of the blog author is in the same city is beyond the pale of the contextual defaulting proposed here. All we are suggesting is application of DRY (“Don’t Repeat Yourself”) for fields that have equivalent definitions elsewhere within the same XHTML document or its MIME headers.

See a related discussion on 2006-01-27 on [[hreview-feedback]].

==Examples (Preliminary)==

=== Simple Listing ===
Parking space for rent (2/2/06)
2 compact car spaces in a secure underground garage at:
1738 Elm St.
Somewhere, ED 34567 ISA
Available in April 2006 for $215/mo
Please contact John Broker at 110.555.1212 (C)

<pre><nowiki>
<div class="hlisting">
<p>
<span class="item fn">Parking space</span>
<span class="offer rent">for rent</span>
(<abbr class="dtlisted" title="20060202">2/2/06</abbr>)
</p>
<p class="description">
2 compact car spaces in a secure underground garage at:
<div class="location vcard adr">
<span class="street-address">1738 Elm St.</span>
<span class="locality">Somewhere</span>, <span class="region">ED</span>
<span class="postal-code">34567</span> <span class="country">ISA</span>
</div>
Available in <abbr class="dtexpired" title="20060401">April 2006</abbr>
for <span class="price">$215/qtr</span>
</p>
<div class="lister vcard">
Please contact <span class="fn">John Broker</span> at
<span class="tel"><span class="value">(110) 555-1212</span>
(<abbr class="type" title="cell">C</abbr>)</span>
</div>
</div></nowiki> </pre>

=== Extended Examples ===

See [[hlisting-extended-examples|hListing Extended Examples]] for real-world examples from Craigslist, eBay.com, and Match.com.

=== Challenge Problems ===

See [[hlisting-challenges|hListing Challenge Problems]] for some hypothetical examples that illustrate corners of the specification.

== Examples in the Wild ==
* [http://www.edgeio.com/ Edgeio] has started to produce output with hListings
* [http://www.dealtagger.com/ Dealtagger] supports hListing

Blogmatrix have a handy microformat parser which now supports hListing [http://tools.blogmatrix.com/extract/ here]

==Changes==

6 Feb 2006: clarified definitions of fields throughout.

5 Feb 2006: Reformatted into wiki-markup style.

4 Feb 2006: Folded the sense of “taken” into dtexpired, re-imported item type from hReview, and combined action and status. Added an example. Removed anonymous listings, since that is an unlikely use case (pseudonymous, perhaps, but not ''a''nonymous).

late Jan 2006: initial conversations started with the insight that hReview does a great job of describing items, and that we could shoehorn in listing semantics using a) magic tags to mean for-sale and b) mapping price onto dimensioned ratings. Tantek correctly nailed this as ''a-priori'' thinking, and encouraged us to start by designing the right spec for listings, and only sharing what was necessary.

== Discussions ==

* Feedback is encouraged on the [[hlisting-feedback]] page.
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].

hlisting

2006-09-01T14:00:36Z

D4rr3ll: /* Examples in the Wild */

=hListing Proposal=

hListing is a proposal for an open, distributed listings format suitable for embedding in (X)HTML, Atom, RSS, and arbitrary XML. hListing would be one of several [[microformats]] open standards.

__TOC__

== Draft Proposal 2006-02-07 ==

===Editor===
* Rohit Khare, [http://commerce.net/ CommerceNet]

===Authors===
* Assaf Arkin, [http://blog.labnotes.org/ Labnotes]
* Craig Donato, [http://oodle.com/ Oodle]
* Rohit Khare, [http://commerce.net/ CommerceNet]

===Contributors===
* Tantek Çelik
* Ryan King

==Introduction==

Individuals and professionals are increasingly publishing their offerings online: whether as items for sale or rent (cars, homes, apartments), services for hire (music lessons, dog walker, plumber), openings (jobs, volunteers, extra spot in a book club) or personals (people looking for dates, companions, roommates). The goal of publishing (and promoting) these listings online is to seek out interested parties, often within a limited time period.

While descriptions of products and services are common on the Web, particularly on e-commerce sites, we are proposing an hListing microformat for sharing, searching, and syndicating the information that helps match up buyers and sellers. This proposal follows the common practices of trading sites such as Craigslist, eBay and newspaper classifieds.

If [[hreview|hReview]] is about an item and what you think of it, hListing is about an item and what you want to ''do'' with it.

=== Inspiration and Acknowledgments ===
Thanks to everyone who participated in the initial burst of hListing activity in August 2005, particularly Emiliano Martínez Luque and Trevor O'Reilly, for naming the effort and organizing the listing-{brainstorming, formats, examples} pages on the wiki. We would like to thank Tantek for an initial debate about whether to extend hReview or pursue an independent-though-similar hListing for our proposal.

=== Scope ===
Vibrant online marketplaces have been launched with little more than titles, prices, descriptions, and contact email addresses; we hope to kindle the same spirit of minimalism with this proposal to restart active discussion of what an hListing should be. Since we are venturing into a space that does not have “settled law” such as the vCard definitions hCard started with, we were inspired by hReview, another novel compound microformat that emerged from the microformats.org community process.

In particular, we note that both applications need a way to share informative descriptions of a product or service, including attribution of authorship and provenance of the item. if hReview is a microformat for one's opinion of a product or service, hListing helps share what one would like to ''do'' with it: sell it, rent it, trade it, perform that service, announce it, or, for people, to meet them. It can tell you how to contact the lister, and whether it is an item on offer or a wanted ad.

==== Out of Scope ====
We are focusing on providing "just enough" structure to enable matching, not to consummate transactions. This is distinct from the majority of formats described on the wiki under [[listing-examples]], which are specific enough to completely describe products for retail sale according to the idiosyncratic semantics of particular merchants and shopping engines. Instead of encoding retail-oriented fields such as UPCs, SKUs, and manufacturer part numbers, this proposal acknowledges that many listings are for "inventories of one" that may not have such precise abstractions.

Similarly, listings cannot aspire to describe prices and terms & conditions to the degree necessary to automate entire transactions or price comparisons. Some have terms beyond the pale of any B2B exchange protocols (e.g. "$50 ''obo''").

As in hReview, the concept of a “universal object identifier” is also out-of-scope for this effort. Unlike some of the “product feed” formats under [listing-examples], we avoided specifying any taxonomy for identifying or categorizing listings in favor of tags.

== Format ==
=== In General ===
The hListing format is based on a set of fields common to numerous listing sites and formats in use today on the web. Where possible field names have been chosen based on those defined by the related [[hreview|hReview]], [[hcard|hCard]], [[hcalendar|hCalendar]] standards.

=== Schema ===

An hListing schema should consist of the following:

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

==== Summary of Changes ====
By comparison to hReview:
* Item type and info have been preserved to describe the good, service, or person being offered.
* Item info expanded to take geo or adr for location of the item.
* Item description has become required, rather than item info or type. While reviews tend to apply to a range of products, listings "in the wild" can be ''sui generis,'' found with only a description and no other structured information.
* Rating has been removed.
* Lister, unlike Reviewer, can also have a telephone number -- but it must ''either'' be an hCard or the other fields.

Creating a listing requires adding transaction metadata:
* Type of transaction sought: whether the lister has or wants an item (sale or rent), a service, an opening, or a personal introduction.
* Dates of listing and expiry. Once taken, listings may be reposted with a modified dtexpired.
* Price has been called out specifically as an independent text field. It can include some terms & conditions.

==Field Details==
The fields of the hListing schema represent the following:

'''version''':: This optional field permits hListing publishers to specify a particular version of hListing that their content uses. By omitting this field, the publisher is stating that implementations may interpret the hListings according to any version of the hListing specification. The value for this proposal as of 6-Feb-2006 is "0.0," since it has no official standing yet.

===Transaction Metadata===
'''listing type''':: This required field indicates the desired matching: whether it’s about something that the lister has (offer) or wants (wanted). '''NOTE: This needs to be collapsed with listing action per the change made to the summary above.'''

'''listing action''':: This required field indicates the desired action for the listing: a permanent transfer (sale); transient use (rent); barter or donation (trade); to arrange an introduction (meet); publicize the existence of an event or vendor (announce); or to perform a service (service).

'''lister''':: The person or business who should be contacted about the listing, either in the form of an hCard or a shorthand notation of one or more formatted names (fn) and contact information (email, url, tel). Note that this is not necessarily the the same as the ''author'' of the listing.

'''dtlisted''':: This optional field MUST provide an ISO8601 absolute date time of when the listing was first made effective. This field SHOULD use UTC, but MAY use the time zone offset syntax. See [[datetime-design-pattern|datetime design pattern]].

'''dtexpired''':: This optional field MUST provide an ISO8601 absolute date time of when the listing will become ineffective. It MUST be later than dtlisted. This field SHOULD use UTC, but MAY use the time zone offset syntax. See [[datetime-design-pattern|datetime design pattern]].

<blockquote>
Note that this definition obviates the need for a “taken” listing action; when a listing is no longer valid, it can simply be deleted, or republished with an expiry date that has already passed. Republication may be desirable, to indicate that the listing is no longer available to forestall further inquiries. Keeping expiry orthogonal to listing-action permits archival use of web pages with hListings.
</blockquote>

'''location''':: This optional field contains the location of the item, which may be different than the location of the lister. This may be a full hCard with contact information, or a geolocation-specific microformat type.

<blockquote>
There is an separate discussion to be had about how either of these three microformats can best accommodate colloquial terminiology for “neighborhoods,” but this proposal does not break new ground by coining a new fields for that purpose.
</blockquote>

'''price''':: This optional text field describes the “advertised” price of the listing; it is not a binding offer, nor a complete transaction price. Floating point numbers found within this string may be extracted for sorting/indexing, as could adjacent currency symbols or ISO currency codes.

<blockquote>
Note that since price is such a general description, we have avoided promoting an additional “terms and conditions” field for elaborating on the price or terms of the deal (e.g. “dollars”, “best offer” “per month” “paypal only”). We suggest demoting it until proven that it needs to exist independently of either description (such as shipping rates) or price (which can just state “CAD$22/mo”).
</blockquote>

===Item Metadata===

'''item type''':: This optional field "type" provides the type of the item being ''listed'': one of the following: opening, housing, product, business, event, person, place, website, url.

<blockquote>
Note that the first two, housing and opening, are new and unique to hListing; the remainder are copied by reference from hReview. Similar to the note in hReview 0.2 for item types, the enumerated list of listing types is “under development and may be extended.”
</blockquote>

'''item info''':: This required field MUST have at a minimum the name ("fn" - the formatted text corresponding to the name) of the item , SHOULD provide at least one URI ("url") for the item, and MAY provide at least one URL to a photo or depiction ("photo") of the item. For items of type person or business, the item info (fn, url, photo) SHOULD be encapsulated in an hCard. Unique item IDs (e.g. ISBNs, UPCs) MAY be represented as a URN ("url") for the item.

===Content ===

'''summary''':: This optional text field serves as a title for listing.

'''description''':: This optional field contains the full text representing the written description of the item being listed. The field MAY include valid XHTML markup (e.g. paragraphs). User agents SHOULD preserve any markup.

'''tags''':: Tags are represented using a list of keywords or phrases (using the RelTag microformat for each individual keyword or phrase tag) that the reviewer associates with the item. The reviewer SHOULD provide tags relating to how they want the item categorized (e.g., “car, used, acura”, “job”, “real estate, 3BR”). The reviewer MAY also want to provide tags indicating payment terms (“dollars”, “paypal”).

'''permalink''':: This optional field is a URL for the hListing. In addition to using the <a href> tag for this field, the attribute rel="self bookmark" MUST be used to indicate that the hyperlink is a permalink for the review itself. If the hyperlink already contains a rel attribute, then the values self and bookmark MUST be included among the space-separated set of values in the attribute. Indexers MAY treat the permalink of a review as a unique ID in order to identify and collate the same listing from multiple sources (such as indexing a page multiple times). The permalink MAY also be used to indicate or imply the origin of the listing. Authors MAY use the classname of "permalink" on the element representing the permalink, but are not required to do so.

===Cross-cutting issues===
''Internationalization:'' Though there are many English-language tokens, they are only used as invisible class-names; user-visible listing information can be completely localized. N.b. that (X)HTML lang attribute rules still apply as usual, for multilingual aggregators of hListings.

The following field names have been reused from the [[hcard|hCard]] and [[hcalendar|hCalendar]] microformats: <code>version, summary, fn, url, email, photo, description, categories</code>. In addition, items and reviewers described by hCards MAY contain any hCard field. The rel value "self" has been reused from the [http://atompub.org/2005/07/11/draft-ietf-atompub-format-10.html Atom 1.0 specification].

==Contextual Defaults: A New Approach?==

Since listings may be embedded within blog postings, email, syndicated feeds, simple Web pages, or other microformats such as hAtom, to the degree possible, the following fields can be “inherited” from the context surrounding an hListing if absent:

* lister (author, contributor, From:)
* dtlisted (Date:)
* dtexpired (Expires:)
* summary (title)
* permalink (URI:, <base>)

By contrast, gazetteering is an example of ''ad hoc'' contextual defaulting that is '''not''' governed by this technique. Guessing that “Noe Valley” is in “San Francisco, CA” because the hCard of the blog author is in the same city is beyond the pale of the contextual defaulting proposed here. All we are suggesting is application of DRY (“Don’t Repeat Yourself”) for fields that have equivalent definitions elsewhere within the same XHTML document or its MIME headers.

See a related discussion on 2006-01-27 on [[hreview-feedback]].

==Examples (Preliminary)==

=== Simple Listing ===
Parking space for rent (2/2/06)
2 compact car spaces in a secure underground garage at:
1738 Elm St.
Somewhere, ED 34567 ISA
Available in April 2006 for $215/mo
Please contact John Broker at 110.555.1212 (C)

<pre><nowiki>
<div class="hlisting">
<p>
<span class="item fn">Parking space</span>
<span class="offer rent">for rent</span>
(<abbr class="dtlisted" title="20060202">2/2/06</abbr>)
</p>
<p class="description">
2 compact car spaces in a secure underground garage at:
<div class="location vcard adr">
<span class="street-address">1738 Elm St.</span>
<span class="locality">Somewhere</span>, <span class="region">ED</span>
<span class="postal-code">34567</span> <span class="country">ISA</span>
</div>
Available in <abbr class="dtexpired" title="20060401">April 2006</abbr>
for <span class="price">$215/qtr</span>
</p>
<div class="lister vcard">
Please contact <span class="fn">John Broker</span> at
<span class="tel"><span class="value">(110) 555-1212</span>
(<abbr class="type" title="cell">C</abbr>)</span>
</div>
</div></nowiki> </pre>

=== Extended Examples ===

See [[hlisting-extended-examples|hListing Extended Examples]] for real-world examples from Craigslist, eBay.com, and Match.com.

=== Challenge Problems ===

See [[hlisting-challenges|hListing Challenge Problems]] for some hypothetical examples that illustrate corners of the specification.

== Examples in the Wild ==
* [http://www.edgeio.com/ Edgeio] has started to produce output with hListings
* [http://www.dealtagger.com/ Dealtagger] supports hListing

==Changes==

6 Feb 2006: clarified definitions of fields throughout.

5 Feb 2006: Reformatted into wiki-markup style.

4 Feb 2006: Folded the sense of “taken” into dtexpired, re-imported item type from hReview, and combined action and status. Added an example. Removed anonymous listings, since that is an unlikely use case (pseudonymous, perhaps, but not ''a''nonymous).

late Jan 2006: initial conversations started with the insight that hReview does a great job of describing items, and that we could shoehorn in listing semantics using a) magic tags to mean for-sale and b) mapping price onto dimensioned ratings. Tantek correctly nailed this as ''a-priori'' thinking, and encouraged us to start by designing the right spec for listings, and only sharing what was necessary.

== Discussions ==

* Feedback is encouraged on the [[hlisting-feedback]] page.
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].

hlisting-extended-examples

2006-08-31T18:18:50Z

D4rr3ll: /* hListing Extended Examples */

=hListing Extended Examples=

These are examples directly copied from then-current listings on public Websites by Craig Donato.

Note: the example markup on this page was produced by an early preview of Assaf Arkin's plugin for WordPress. It does not mean that the syntax here is final, or interoperable with, say, CommerceNet's parser (unfortunately!)

Note: some of the examples here show class="hlisting offer-sale", but according to [http://microformats.org/wiki/hcard-faq#nesting-properties this] that shouldn't be the case.

=== Housing / Craigslist ===
{|
|version
|
|-
|listing type
|offer
|-
|listing action
|rent
|-
|lister
|hous-131773022@craigslist.org
|-
|dtlisted
|2006-02-06, 3:48PM PST
|-
|dtexpired
|
|-
|price
|$1995
|-
|location
|1135 Sir Francis Drake Blvd, Kentfield, CA
|-
|item type
|housing
|-
|item info
photo
|http://b.im.craigslist.org/lI/kK/QS8vqLbrfj762txcg44ISQIThVta.jpg
http://b.im.craigslist.org/xg/h5/VIvHzirAmMtKj2bYMi81Cy4G318F.jpg
http://b.im.craigslist.org/LC/VV/wmQLa9DmuTJfPqqr8xVNwpVnJbUN.jpg
|-
|summary
|$1995 / 3br - Spacious townhouse private garage, lots of closets
|-
|description
|This is a spacious 3 bedroom 2 bath townhouse/apartment on the Ross border. Easy commute to San Francisco by bus or ferry. Close to bike & hike paths, College of Marin and public transportation. Located in the Kentfield School District.

3BR/2BA Fresh paint and very well maintained

First Floor:
* Living Room
* Dining Room
* Kitchen: Lots of counter space, dishwasher, refrigerator, stove, garbage disposal
* Full bathroom
* Bedroom with private balcony, overlooking creek and trees

Second Floor
* Two large bedrooms, each with walk-in closets
* Extra walk-in storage closet
* Full bathroom

EXTRAS
* Enclosed Parking Garage
* Cable Ready
* Shared Laundry Room
* Creekside deck for picnics
* Includes water and garbage pick-up

Address: 1135 Sir Francis Drake Blvd, Kentfield Please DO NOT disturb residents.

For more information, or to schedule an appointment to view, please contact (415) 454-2246
|-
|tags
|Apartments, Kentfield
|-
|permalink
|http://www.craigslist.org/nby/apa/131773022.html
|-
|}

<pre><nowiki>
<div class='hlisting offer-rent'>
<div class='description'><p><span style="font-size: 10pt">This is a
spacious 3 bedroom 2 bath townhouse/apartment on the Ross border. Easy
commute to San Francisco by bus or ferry. Close to bike & hike
paths, College of Marin and public transportation. Located in the
Kentfield School District.</span></p>
<p>3BR/2BA Fresh paint and very well maintained</p>
<p>First Floor:</p>
<ul>
<li>Living Room</li>
<li>Dining Room</li>
<li>Kitchen: Lots of counter space, dishwasher, refrigerator, stove,
garbage disposal</li>
<li>Full bathroom</li>
<li>Bedroom with private balcony, overlooking creek and trees</li>
</ul>
<p>Second Floor</p>
<ul>
<li>Two large bedrooms, each with walk-in closets</li>
<li>Extra walk-in storage closet</li>
<li>Full bathroom</li>
</ul>
<p>EXTRAS</p>
<ul>
<li>Enclosed Parking Garage</li>
<li>Cable Ready</li>
<li>Shared Laundry Room</li>
<li>Creekside deck for picnics</li>
<li>Includes water and garbage pick-up</li>
</ul>
<div class='tags'>Tagged: <a href="http://localhost/blog/tag/apartments"
rel="tag">Apartments</a>, <a href="http://localhost/blog/tag/housing"
rel="tag">housing</a>, <a href="http://localhost/blog/tag/kentfield"
rel="tag">Kentfield</a></div></div>
<p><strong>Price</strong>: <span class='price'>$1995</span></p>
<p class='location'><strong>Location</strong>: <div class='adr'><span
class='street-address'>1135 Sir Francis Drake Blvd</span><div
class='locality'>Kentfield</div><div><span class='region'>CA</state>
<span class='postal-code'></span></div></div></p>
<p class='contact'><strong>Contact me at</strong>: <span
class="hcard">(415) 454-2246</span></p>
</div></nowiki></pre>

Notes: @@.

Preview screenshot:

http://labs.commerce.net/~rohit/hlisting-housing-aa.png

=== Product / eBay ===

{|
|version
|
|-
|listing type
|offer
|-
|listing action
|sell
|-
|lister
|http://feedback.ebay.com/ws/eBayISAPI.dll?ViewFeedback&userid=manganos&iid=5863912155&frm=284
|-
|dtlisted
|Feb-07-06 14:28:35 PST
|-
|dtexpired
|Feb-13-06 15:28:35 PST
|-
|price
|$1
|-
|location
|Church Road, VA United States
|-
|item type
|product
|-
|item info
photo
|http://i8.ebayimg.com/02/i/06/32/24/5d_1.JPG
http://i10.ebayimg.com/05/i/06/31/1b/98_0.JPG
http://i2.ebayimg.com/02/i/06/33/81/34_0.JPG
|-
|summary
|BOUNTY HUNTER 840 *not garrett, minelab, whites*
|-
|description
|You are bidding on a Bounty Hunter 840 VLF/TR. I have never used this but I put batteries in it and it turned on. The unit is in goo cosmetic shape with no signs of wear. I do not know too much about this detector so do your research before bidding. It takes 2 - 9V batteries (not included). Find some treasure or coins in your own back yard. Good luck bidding on this NO RESERVE auction. Unit is sold as is as I have never used it. Thanks and good luck!
|-
|tags
|Used, Metal Detector
|-
|permalink
|http://cgi.ebay.com/BOUNTY-HUNTER-840-not-garrett-minelab-whites_W0QQitemZ5863912155QQcategoryZ67775QQrdZ1QQcmdZViewItem
|-
|}

<pre><nowiki>
<div class='hlisting offer-sale'>
<div class='summary'>BOUNTY HUNTER 840 *not garrett, minelab, whites*</div>
<div class='description'>
<p>You are bidding on a Bounty Hunter 840 VLF/TR. I have never used this
but I put batteries in it and it turned on. The unit is in goo cosmetic
shape with no signs of wear. I do not know too much about this detector
so do your research before bidding. It takes 2 - 9V batteries (not
included). Find some treasure or coins in your own back yard. Good luck
bidding on this NO RESERVE auction. Unit is sold as is as I have never
used it. Thanks and good luck!</p>
<p><img src="http://i8.ebayimg.com/02/i/06/32/24/5d_1.JPG" /></p>
<p><img src="http://i10.ebayimg.com/05/i/06/31/1b/98_0.JPG" /></p>
<p><img src="http://i2.ebayimg.com/02/i/06/33/81/34_0.JPG" /></p>
<div class='tags'>Tagged: <a
href="http://localhost/blog/tag/metal_detector" rel="tag">Metal
Detector</a>, <a href="http://localhost/blog/tag/used"
rel="tag">Used</a></div></div>
<p><strong>Price</strong>: <span class='price'>$1</span></p>
<p><strong>Listed</strong>: <abbr class='dtlisted'
title='20060702T142835-0800'>Feb-07-06 14:28:35 PST</abbr></p>
<p><strong>Expires</strong>: <abbr class='dtexpired'
title='20060213T152835-0800'>Feb-13-06 15:28:35 PST</abbr></p>
</div>
</div></nowiki></pre>

Notes: @@.

===Personal / Match.com===
{|
|-
|version
|
|-
|listing type
|wanted
|-
|listing action
|meet
|-
|lister
|http://www.match.com/doubleblind/emailform.aspx?lid=41&uid=AEMclhclaughal
|-
|dtlisted
|
|-
|dtexpired
|
|-
|price
|
|-
|location
|Burlingame, CA 94010 United States
|-
|item type
|person
|-
|item info
photo
|http://pictures.match.com/pictures/44/08/37954408A.jpeg
|-
|summary
|Let me show you the world in my eyes
|-
|description
|The only true way to get to know me is to chat with me.

I am looking for a guy who is honest and does not play games, takes care of himself, likes to laugh, can communicate, is confident, but not full of himself.

What do I like? I love spending time with my family, cooking, watching professional football and scuba diving.
|-
|tags
|WSM, blackhair, browneyes, confident, cooking, diving, family, football, honest, runner, running, scuba, walking, weights
|-
|permalink
|http://www.match.com/profile/showprofile.aspx?lid=18&RN=4&PI=1&TP=S&UID=HvAaOKJuTF4j9tqE%2bYDQoQ%3d%3d&Handle=puuikena&DO=2
|-
|
|-
|}

<pre><nowiki>
<div class='hlisting listing-meet'>
<div class='description'><p>The only true way to get to know me is to
chat with me.</p>
<p>I am looking for a guy who is honest and does not play games, takes
care of himself, likes to laugh, can communicate, is confident, but not
full of himself.</p>
<p>What do I like? I love spending time with my family, cooking,
watching professional football and scuba diving.</p>
<p><img src="http://pictures.match.com/pictures/44/08/37954408A.jpeg"
/></p></div>
<div class='tags'>Tagged: <a href="http://localhost/blog/tag/blackhair"
rel="tag">blackhair</a>, <a href="http://localhost/blog/tag/browneyes"
rel="tag">browneyes</a>, <a href="http://localhost/blog/tag/confident"
rel="tag">confident</a>, <a href="http://localhost/blog/tag/cooking"
rel="tag">cooking</a>, <a href="http://localhost/blog/tag/diving"
rel="tag">diving</a>, <a href="http://localhost/blog/tag/family"
rel="tag">family</a>, <a href="http://localhost/blog/tag/football"
rel="tag">football</a>, <a href="http://localhost/blog/tag/honest"
rel="tag">honest</a>, <a href="http://localhost/blog/tag/runner"
rel="tag">runner</a>, <a href="http://localhost/blog/tag/running"
rel="tag">running</a>, <a href="http://localhost/blog/tag/scuba"
rel="tag">scuba</a>, <a href="http://localhost/blog/tag/walking"
rel="tag">walking</a>, <a href="http://localhost/blog/tag/weights"
rel="tag">weights</a></div>
<p class='location'><strong>Location</strong>: Burlingame, CA 94010
United States</p>
</div></nowiki></pre>

Notes: missing permalink, additional adr structure for location, WSM tag.

Preview screenshot:

http://labs.commerce.net/~rohit/hlisting-personal-aa.png

hlisting-extended-examples

2006-08-31T18:17:58Z

D4rr3ll: /* hListing Extended Examples */

=hListing Extended Examples=

These are examples directly copied from then-current listings on public Websites by Craig Donato.

Note: the example markup on this page was produced by an early preview of Assaf Arkin's plugin for WordPress. It does not mean that the syntax here is final, or interoperable with, say, CommerceNet's parser (unfortunately!)

Note: some of the examples here show class="hlisting offer-sell", but according to [http://microformats.org/wiki/hcard-faq#nesting-properties this] that shouldn't be the case.

=== Housing / Craigslist ===
{|
|version
|
|-
|listing type
|offer
|-
|listing action
|rent
|-
|lister
|hous-131773022@craigslist.org
|-
|dtlisted
|2006-02-06, 3:48PM PST
|-
|dtexpired
|
|-
|price
|$1995
|-
|location
|1135 Sir Francis Drake Blvd, Kentfield, CA
|-
|item type
|housing
|-
|item info
photo
|http://b.im.craigslist.org/lI/kK/QS8vqLbrfj762txcg44ISQIThVta.jpg
http://b.im.craigslist.org/xg/h5/VIvHzirAmMtKj2bYMi81Cy4G318F.jpg
http://b.im.craigslist.org/LC/VV/wmQLa9DmuTJfPqqr8xVNwpVnJbUN.jpg
|-
|summary
|$1995 / 3br - Spacious townhouse private garage, lots of closets
|-
|description
|This is a spacious 3 bedroom 2 bath townhouse/apartment on the Ross border. Easy commute to San Francisco by bus or ferry. Close to bike & hike paths, College of Marin and public transportation. Located in the Kentfield School District.

3BR/2BA Fresh paint and very well maintained

First Floor:
* Living Room
* Dining Room
* Kitchen: Lots of counter space, dishwasher, refrigerator, stove, garbage disposal
* Full bathroom
* Bedroom with private balcony, overlooking creek and trees

Second Floor
* Two large bedrooms, each with walk-in closets
* Extra walk-in storage closet
* Full bathroom

EXTRAS
* Enclosed Parking Garage
* Cable Ready
* Shared Laundry Room
* Creekside deck for picnics
* Includes water and garbage pick-up

Address: 1135 Sir Francis Drake Blvd, Kentfield Please DO NOT disturb residents.

For more information, or to schedule an appointment to view, please contact (415) 454-2246
|-
|tags
|Apartments, Kentfield
|-
|permalink
|http://www.craigslist.org/nby/apa/131773022.html
|-
|}

<pre><nowiki>
<div class='hlisting offer-rent'>
<div class='description'><p><span style="font-size: 10pt">This is a
spacious 3 bedroom 2 bath townhouse/apartment on the Ross border. Easy
commute to San Francisco by bus or ferry. Close to bike & hike
paths, College of Marin and public transportation. Located in the
Kentfield School District.</span></p>
<p>3BR/2BA Fresh paint and very well maintained</p>
<p>First Floor:</p>
<ul>
<li>Living Room</li>
<li>Dining Room</li>
<li>Kitchen: Lots of counter space, dishwasher, refrigerator, stove,
garbage disposal</li>
<li>Full bathroom</li>
<li>Bedroom with private balcony, overlooking creek and trees</li>
</ul>
<p>Second Floor</p>
<ul>
<li>Two large bedrooms, each with walk-in closets</li>
<li>Extra walk-in storage closet</li>
<li>Full bathroom</li>
</ul>
<p>EXTRAS</p>
<ul>
<li>Enclosed Parking Garage</li>
<li>Cable Ready</li>
<li>Shared Laundry Room</li>
<li>Creekside deck for picnics</li>
<li>Includes water and garbage pick-up</li>
</ul>
<div class='tags'>Tagged: <a href="http://localhost/blog/tag/apartments"
rel="tag">Apartments</a>, <a href="http://localhost/blog/tag/housing"
rel="tag">housing</a>, <a href="http://localhost/blog/tag/kentfield"
rel="tag">Kentfield</a></div></div>
<p><strong>Price</strong>: <span class='price'>$1995</span></p>
<p class='location'><strong>Location</strong>: <div class='adr'><span
class='street-address'>1135 Sir Francis Drake Blvd</span><div
class='locality'>Kentfield</div><div><span class='region'>CA</state>
<span class='postal-code'></span></div></div></p>
<p class='contact'><strong>Contact me at</strong>: <span
class="hcard">(415) 454-2246</span></p>
</div></nowiki></pre>

Notes: @@.

Preview screenshot:

http://labs.commerce.net/~rohit/hlisting-housing-aa.png

=== Product / eBay ===

{|
|version
|
|-
|listing type
|offer
|-
|listing action
|sell
|-
|lister
|http://feedback.ebay.com/ws/eBayISAPI.dll?ViewFeedback&userid=manganos&iid=5863912155&frm=284
|-
|dtlisted
|Feb-07-06 14:28:35 PST
|-
|dtexpired
|Feb-13-06 15:28:35 PST
|-
|price
|$1
|-
|location
|Church Road, VA United States
|-
|item type
|product
|-
|item info
photo
|http://i8.ebayimg.com/02/i/06/32/24/5d_1.JPG
http://i10.ebayimg.com/05/i/06/31/1b/98_0.JPG
http://i2.ebayimg.com/02/i/06/33/81/34_0.JPG
|-
|summary
|BOUNTY HUNTER 840 *not garrett, minelab, whites*
|-
|description
|You are bidding on a Bounty Hunter 840 VLF/TR. I have never used this but I put batteries in it and it turned on. The unit is in goo cosmetic shape with no signs of wear. I do not know too much about this detector so do your research before bidding. It takes 2 - 9V batteries (not included). Find some treasure or coins in your own back yard. Good luck bidding on this NO RESERVE auction. Unit is sold as is as I have never used it. Thanks and good luck!
|-
|tags
|Used, Metal Detector
|-
|permalink
|http://cgi.ebay.com/BOUNTY-HUNTER-840-not-garrett-minelab-whites_W0QQitemZ5863912155QQcategoryZ67775QQrdZ1QQcmdZViewItem
|-
|}

<pre><nowiki>
<div class='hlisting offer-sale'>
<div class='summary'>BOUNTY HUNTER 840 *not garrett, minelab, whites*</div>
<div class='description'>
<p>You are bidding on a Bounty Hunter 840 VLF/TR. I have never used this
but I put batteries in it and it turned on. The unit is in goo cosmetic
shape with no signs of wear. I do not know too much about this detector
so do your research before bidding. It takes 2 - 9V batteries (not
included). Find some treasure or coins in your own back yard. Good luck
bidding on this NO RESERVE auction. Unit is sold as is as I have never
used it. Thanks and good luck!</p>
<p><img src="http://i8.ebayimg.com/02/i/06/32/24/5d_1.JPG" /></p>
<p><img src="http://i10.ebayimg.com/05/i/06/31/1b/98_0.JPG" /></p>
<p><img src="http://i2.ebayimg.com/02/i/06/33/81/34_0.JPG" /></p>
<div class='tags'>Tagged: <a
href="http://localhost/blog/tag/metal_detector" rel="tag">Metal
Detector</a>, <a href="http://localhost/blog/tag/used"
rel="tag">Used</a></div></div>
<p><strong>Price</strong>: <span class='price'>$1</span></p>
<p><strong>Listed</strong>: <abbr class='dtlisted'
title='20060702T142835-0800'>Feb-07-06 14:28:35 PST</abbr></p>
<p><strong>Expires</strong>: <abbr class='dtexpired'
title='20060213T152835-0800'>Feb-13-06 15:28:35 PST</abbr></p>
</div>
</div></nowiki></pre>

Notes: @@.

===Personal / Match.com===
{|
|-
|version
|
|-
|listing type
|wanted
|-
|listing action
|meet
|-
|lister
|http://www.match.com/doubleblind/emailform.aspx?lid=41&uid=AEMclhclaughal
|-
|dtlisted
|
|-
|dtexpired
|
|-
|price
|
|-
|location
|Burlingame, CA 94010 United States
|-
|item type
|person
|-
|item info
photo
|http://pictures.match.com/pictures/44/08/37954408A.jpeg
|-
|summary
|Let me show you the world in my eyes
|-
|description
|The only true way to get to know me is to chat with me.

I am looking for a guy who is honest and does not play games, takes care of himself, likes to laugh, can communicate, is confident, but not full of himself.

What do I like? I love spending time with my family, cooking, watching professional football and scuba diving.
|-
|tags
|WSM, blackhair, browneyes, confident, cooking, diving, family, football, honest, runner, running, scuba, walking, weights
|-
|permalink
|http://www.match.com/profile/showprofile.aspx?lid=18&RN=4&PI=1&TP=S&UID=HvAaOKJuTF4j9tqE%2bYDQoQ%3d%3d&Handle=puuikena&DO=2
|-
|
|-
|}

<pre><nowiki>
<div class='hlisting listing-meet'>
<div class='description'><p>The only true way to get to know me is to
chat with me.</p>
<p>I am looking for a guy who is honest and does not play games, takes
care of himself, likes to laugh, can communicate, is confident, but not
full of himself.</p>
<p>What do I like? I love spending time with my family, cooking,
watching professional football and scuba diving.</p>
<p><img src="http://pictures.match.com/pictures/44/08/37954408A.jpeg"
/></p></div>
<div class='tags'>Tagged: <a href="http://localhost/blog/tag/blackhair"
rel="tag">blackhair</a>, <a href="http://localhost/blog/tag/browneyes"
rel="tag">browneyes</a>, <a href="http://localhost/blog/tag/confident"
rel="tag">confident</a>, <a href="http://localhost/blog/tag/cooking"
rel="tag">cooking</a>, <a href="http://localhost/blog/tag/diving"
rel="tag">diving</a>, <a href="http://localhost/blog/tag/family"
rel="tag">family</a>, <a href="http://localhost/blog/tag/football"
rel="tag">football</a>, <a href="http://localhost/blog/tag/honest"
rel="tag">honest</a>, <a href="http://localhost/blog/tag/runner"
rel="tag">runner</a>, <a href="http://localhost/blog/tag/running"
rel="tag">running</a>, <a href="http://localhost/blog/tag/scuba"
rel="tag">scuba</a>, <a href="http://localhost/blog/tag/walking"
rel="tag">walking</a>, <a href="http://localhost/blog/tag/weights"
rel="tag">weights</a></div>
<p class='location'><strong>Location</strong>: Burlingame, CA 94010
United States</p>
</div></nowiki></pre>

Notes: missing permalink, additional adr structure for location, WSM tag.

Preview screenshot:

http://labs.commerce.net/~rohit/hlisting-personal-aa.png