|
|
Line 1: |
Line 1: |
| <entry-title>listing microformat brainstorming </entry-title>
| | HOW THING THROUGH |
| This is brainstorming for a [[hlisting]] microformat per the [[process]].
| | HOW MAKE THING THROUGH |
| | | HOW THING BE THROUGH |
| == proposed schema revisions ==
| | HOW MAKE THING BE THROUGH |
| === Revised Base Schema Elements (proposed, revised by [[User:JayMyers|Jay Myers]] 16:55, 29 Jun 2009 (UTC)) ===
| | HOW ANYTHING THROUGH |
| | | HOW MAKE ANYTHING THROUGH |
| *hListing (hlisting)
| | HOW ANYTHING BE THROUGH |
| ** listing action. optional. one or more tags, suggested set: sell | rent | trade | meet | announce | offer | wanted | event | service
| | HOW MAKE ANYTHING BE THROUGH |
| ** '''lister.''' required. hCard | (fn || email || url || tel).
| | HOW EVERYTHING THROUGH |
| ** dtlisted. optional. ISO8601 absolute date time.
| | HOW MAKE EVERYTHING THROUGH |
| ** dtexpired. optional. ISO8601 absolute date time.
| | HOW EVERYTHING BE THROUGH |
| ** price. optional. text. [should include a floating-point number with optional ISO currency codes] - see the currency proposal
| | HOW MAKE EVERYTHING BE THROUGH |
| ** item info. optional. (fn || url || photo || geo || adr) | hCard (for person or business).
| | HOW UNIVERSE THROUGH |
| ** summary. optional. text.
| | HOW MAKE UNIVERSE THROUGH |
| ** '''description.''' required. text with optional valid XHTML markup.
| | HOW UNIVERSE BE THROUGH |
| ** item tags. optional. keywords or phrases describing the item being offered, using rel-tag
| | HOW MAKE UNIVERSE BE THROUGH |
| ** permalink. optional.
| | HOW THING OUT |
| ** availability. optional. text.
| | HOW MAKE THING OUT |
| ** condition. optional. text. examples: 'new', 'used', 'refurbished'.
| | HOW THING BE OUT |
| ** shipping. optional. text. text describing shipping and fulfillment
| | HOW MAKE THING BE OUT |
| | | HOW ANYTHING OUT |
| ==== Notes ====
| | HOW MAKE ANYTHING OUT |
| | | HOW ANYTHING BE OUT |
| Please see [[hlisting-examples|hListing examples page]] for analysis of 80/20 use case for new attributes availability, condition and shipping. I believe condition should still be considered even though it misses the 80/20 use case mark (71.2% based on current analysis) as it is included in most product-specific data submission services (e.g., Yahoo Product Submit, Google Base).
| | HOW MAKE ANYTHING BE OUT |
| | | HOW EVERYTHING OUT |
| ----
| | HOW MAKE EVERYTHING OUT |
| | | HOW EVERYTHING BE OUT |
| | | HOW MAKE EVERYTHING BE OUT |
| === Revised Base Schema Elements (proposed) ===
| | HOW UNIVERSE OUT |
| | | HOW MAKE UNIVERSE OUT |
| *hListing (hlisting)
| | HOW UNIVERSE BE OUT |
| ** listing action. optional. one or more tags, suggested set: sell | rent | trade | meet | announce | offer | wanted | event | service
| | HOW MAKE UNIVERSE BE OUT |
| ** lister. optional. hCard | (fn || email || url || tel).
| | HOW THING THROUGH |
| ** dtlisted. optional. ISO8601 absolute date time.
| | HOW MAKE THING THROUGH |
| ** dtexpired. optional. ISO8601 absolute date time.
| | HOW THING BE THROUGH |
| ** price. optional. text. [should include a floating-point number with optional ISO currency codes] - see the currency proposal
| | HOW MAKE THING BE THROUGH |
| ** item info. optional. (fn || url || photo || [[geo]] || [[adr]]) | [[hcard|hCard]] (for person or business).
| | HOW ANYTHING THROUGH |
| ** summary. optional. text.
| | HOW MAKE ANYTHING THROUGH |
| ** '''description'''. required. text with optional valid XHTML markup.
| | HOW ANYTHING BE THROUGH |
| ** item tags. optional. keywords or phrases describing the item being offered, using rel-tag
| | HOW MAKE ANYTHING BE THROUGH |
| ** permalink. optional.
| | HOW EVERYTHING THROUGH |
| ** availability. optional. text.
| | HOW MAKE EVERYTHING THROUGH |
| ** condition. optional. text. examples: 'new', 'used', 'refurbished'.
| | HOW EVERYTHING BE THROUGH |
| ** shipping. optional. text. text describing shipping and fulfillment
| | HOW MAKE EVERYTHING BE THROUGH |
| | | HOW UNIVERSE THROUGH |
| | | HOW MAKE UNIVERSE THROUGH |
| ==== Items removed ====
| | HOW UNIVERSE BE THROUGH |
| * version. optional. text.
| | HOW MAKE UNIVERSE BE THROUGH |
| | | HOW THING OUT |
| <div class=discussion>
| | HOW MAKE THING OUT |
| * +1 I'm tending to agree with the removal of version, as in practice it has not been necessary for either [[hReview]] or [[hListing]].[[User:Tantek|Tantek]] 17:45, 16 April 2009 (UTC)
| | HOW THING BE OUT |
| </div>
| | HOW MAKE THING BE OUT |
| | | HOW ANYTHING OUT |
| * item info. optional. (fn || url || photo || geo || adr) | hCard (for person or business).
| | HOW MAKE ANYTHING OUT |
| | | HOW ANYTHING BE OUT |
| <div class=discussion>
| | HOW MAKE ANYTHING BE OUT |
| * Removal of <code>item</code> seems to be a mistake, as that is used to indicate the item itself being listed. E.g., a nested <code>hProduct</code> would be <code><p class='item hproduct'></p></code>. Removal appears to leave no way to include ''what'' is being listed. --[[User:BenWard|BenWard]] 17:38, 16 April 2009 (UTC)
| | HOW EVERYTHING OUT |
| ** +1 completely agreed with Ben Ward's point. Wide use of [[hReview]] in the [[hreview-examples-in-wild|wild]] has shown that having an explicit "item" is both necessary and works in practice. [[User:Tantek|Tantek]] 17:40, 16 April 2009 (UTC)
| | HOW MAKE EVERYTHING OUT |
| * Indeed it was a mistake... left it out of my edits. Replaced. [[User:JayMyers|JayMyers]] 21:04, 22 April 2009 (UTC)
| | HOW EVERYTHING BE OUT |
| </div>
| | HOW MAKE EVERYTHING BE OUT |
| | | HOW UNIVERSE OUT |
| ==== Items added ====
| | HOW MAKE UNIVERSE OUT |
| <div class=discussion>
| | HOW UNIVERSE BE OUT |
| * Each of the following should cite the analysis made of real world examples that demonstrates the 80%+ use case need, otherwise, they should not be added. [[User:Tantek|Tantek]] 17:45, 16 April 2009 (UTC)
| | HOW MAKE UNIVERSE BE OUT |
| </div>
| |
| | |
| * availability. optional. text.
| |
| * condition. optional. text. examples: 'new', 'used', 'refurbished'.
| |
| * shipping. optional. text. text describing shipping and fulfillment
| |
| | |
| ==== Items changed: ====
| |
| * listing action => optional. if omitted, action assumed to be sell
| |
| * lister => optional. if omitted, the buyer/seller is assumed to be the site where the microformat exists
| |
| <div class=discussion>
| |
| * In that case, an algorithm should be provided for how to determine the hCard for the lister, if no explicit lister is given. [[User:Tantek|Tantek]] 17:45, 16 April 2009 (UTC)
| |
| * Isn't the instruction above ("buyer/seller is assumed to be the site where the microformat exists" itself an algorithm? So, if Target.com has an item for sale and lister isn't specified, you use the domain of the web page containing the markup to identify the seller as "target.com" --Kavi, 6 July 2009
| |
| * Wouldn't it make sense for it remain compulsory? If you are stating that the value reverts to a default in the case of an omission - the requirement is still that the hlisting requires a URI as part of the lister - I feel it should stay so that aggregation of hlisting information is possible outside of the domain it was originally posted on. It therefore ''requires'' this information to exist. Maybe the required property should be the url value and the other properties can be optional. [[User:Spiritquest|Spiritquest]] 19:04, 30 September 2009 (UTC)
| |
| </div>
| |
| | |
| == payment ==
| |
| Use [[rel-payment]] or something similar to indicate payment method for hListing.
| |
| | |
| == additional transactional details ==
| |
| Per the discussions raised in the [[hproduct-issues|hProduct issues list]], consider provisions for providing transactional details like "shipping" or "buy/payment" attributes or similar for an iteration of hListing.
| |
| | |
| == see also ==
| |
| * [[hListing]]
| |
| * [[hlisting-issues]]
| |
| * [[hlisting-feedback]]
| |