<entry-title> hListing Issues </entry-title>
These are externally raised issues about hListing with broadly varying degrees of merit. Thus some issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the spec.
IMPORTANT: Please read (or in this case create ;) ) the hListing FAQ before giving any feedback or raising any issues as your feedback/issues may already be resolved/answered.
Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well.
Please add new issues to the top of the list. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.
When this section gets too big, it can be moved to hlisting-issues-closed.
Issues that are resolved, with accepted resolutions (in some cases simply accepting the entire noted issue), and with completion of respective edits to the draft or related documents.
Issues that have been resolved but may have outstanding to-do items.
When this section gets too big, it can be moved to hlisting-issues-resolved.
- 2007-07-21 raised by User:RobManson
- The only discussion I could find relating to payment method for hListing was in the tag section. Wouldn't rel-payment be a natural fit with hListing?
- 2008-04-07 raised by User:Eazytiger
- When hListing is used for eCommerce products, is there any provision for product variations (eg. sizes) that will affect the price? I'm not aware of a precedent for variations in another microformat.
- ACCEPTED FAQ. A product variation that affects the price should be included in the description of the item, and perhaps as a tag on the item as well. This should be added to hlisting-faq Tantek 10:18, 5 August 2009 (UTC)
- 2008-08-26 raised by TobyInk
- The example given in the spec includes an invalid hCard 1.0. (Missing fn.)
- ACCEPTED. The example has been fixed to reference the "adr" directly for the location, which was the intent of the example. Tantek 10:18, 5 August 2009 (UTC)
- 2009-03-10 raised by JayMyers
- Per the discussions raised in the hProduct issues list, are there any provisions for providing transactional details like "shipping" or "buy/payment" attributes?
- ACCEPTED BRAINSTORMING. Consider adding transactional details like "shipping" or "buy/payment" attributes or something similar for an iteration of hListing, request added to listing microformat brainstorming. Tantek 10:18, 5 August 2009 (UTC)
- 2014-11-17 raised by Arthur
- One of the main obstacles for hListing usage is the lack of implementation examples on our end (real in-code implementation) for the 2-words properties. ex. "item info": tag which should encapsulate all the details like hCard | (fn || url || photo || geo || adr)? Should it be exactly class="item info" OR class="item-info"? This needs to be defined as it has to keep encapsulated within all the details of the item.
- 2014-11-17 raised by Tom Morris
- The version property should be deprecated. No other Microformat (classic or new) has used explicit versioning and it seems out of sync with the way we have thus far built microformats specifications.
raised by JulienChaumond
- Indicate that transaction has taken place.
hlisting tells the world that someone is selling something, but shouldn't there be a way to express that someone bought (or rented, etc.) something, i.e. transaction has indeed taken place? (Think Blippy, Swipely, Apple's Ping, etc.).
One way to go about it might be to add an optional datetime element specifying the transaction's date.
Consider using this format (copy and paste this to the end of the list to add your issues; replace ~~~ with an external link if preferred) to report issues or feedback, so that issues can show up in hAtom subscriptions of this issues page. If open issues lack this markup, please add it.
Please post one issue per entry, to make them easier to manage. Avoid combining multiple issues into single reports, as this can confuse or muddle feedback, and puts a burden of separating the discrete issues onto someone else who 1. may not have the time, and 2. may not understand the issue in the same way as the original reporter.
<span class="entry-summary author vcard">
raised by <span class="fn">~~~</span>
<div class="entry-content discussion issues">
* <strong class="entry-title">«Short title of issue»</strong>. «Description of Issue»
** Follow-up comment #1
** Follow-up comment #2