hproduct-issues: Difference between revisions

From Microformats Wiki
Jump to navigation Jump to search
(adding template instructions)
(posting response to open issue)
Line 9: Line 9:
*# However, in the hProduct schema, we have the following fields:
*# However, in the hProduct schema, we have the following fields:
*#* "price. optional. floating point number. can be further refined by type (msrp, regular, sale, clearance)" => if the price is the retailer price, then it should be delegated to hListing. We could imagine it represents the "manufacturer" price (which could be different from the retailer price) ; in this case, it should clearly be explained in the schema definition.
*#* "price. optional. floating point number. can be further refined by type (msrp, regular, sale, clearance)" => if the price is the retailer price, then it should be delegated to hListing. We could imagine it represents the "manufacturer" price (which could be different from the retailer price) ; in this case, it should clearly be explained in the schema definition.
*#* I would say there is also ambiguity between the responsabilities of hProduct vs hListing for the following fields: quantity / shipping
*#* I would say there is also ambiguity between the responsibilities of hProduct vs hListing for the following fields: quantity / shipping
*#** Response <span class="summary vcard"><span class="dtstart">2008-02-16</span> raised by <span class="fn">Jay Myers</span></span>: I believe everyone agrees that we would borrow price from hListing for hProduct spec. I will explain the concept further in the schema.
*#** Response <span class="vcard">raised by <span class="fn">[[User:JayMyers|Jay Myers]]</span>, 2008-02-16</span>: I don't follow the quantity/ shipping issue. I don't see either of these on hListing, unless the concepts are somehow embedded in other attributes. Can you elaborate on what the ambiguity is?
</div>
</div>
</div>
</div>


== Template ==
== Template ==
{{issues-format}}
{{issues-format}}

Revision as of 15:41, 16 February 2009

2008-12-17 hProduct vs hListing regarding "price" / "quantity" / "shipping" fields

  • open issue! 2008-12-17 raised by NicolasLeroy
    1. In the "out of scope" section, it is explained: _"This microformat does not intend to replicate any of the content proposed within hListing and would defer all money/transactional matters to that microformat"_
    2. However, in the hProduct schema, we have the following fields:
      • "price. optional. floating point number. can be further refined by type (msrp, regular, sale, clearance)" => if the price is the retailer price, then it should be delegated to hListing. We could imagine it represents the "manufacturer" price (which could be different from the retailer price) ; in this case, it should clearly be explained in the schema definition.
      • I would say there is also ambiguity between the responsibilities of hProduct vs hListing for the following fields: quantity / shipping
        • Response 2008-02-16 raised by Jay Myers: I believe everyone agrees that we would borrow price from hListing for hProduct spec. I will explain the concept further in the schema.
        • Response raised by Jay Myers, 2008-02-16: I don't follow the quantity/ shipping issue. I don't see either of these on hListing, unless the concepts are somehow embedded in other attributes. Can you elaborate on what the ambiguity is?

Template

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.

<div class="hentry">
{{OpenIssue}} 
<span class="entry-summary author vcard">
 <span class="published">2011-MM-DD</span> 
 raised by <span class="fn">~~~</span>
</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
</div>
</div>