- From: Aaron Bradley <aaranged@gmail.com>
- Date: Fri, 7 Feb 2014 12:23:17 -0800
- To: Dan Brickley <danbri@google.com>
- Cc: W3C Web Schemas Task Force <public-vocabs@w3.org>, Martin Hepp <martin.hepp@ebusiness-unibw.org>, Vicki Tardif Holland <vtardif@google.com>
- Message-ID: <CAMbipBvkmSHx4GWWRLXgPjOmPk3Auy+u+fA9yi_cJnK17aCKjw@mail.gmail.com>
These seem like sensible additions and modifications to me. However, as per Vicki's observation: "If I buy two coffee mugs, I should expect to pay twice the specified price." By expressly indicating that an Offer price means "unit price" and the addition of the totalPrice property this clears up any potential confusion about whether or not it is a unit or total price that an Offer refers. However, I don't believe that the acceptedOffer property of Order supports a declaration of quantity, even thought with this change price and totalPrice will be explicit. In other words, the proposed modifications will allow support marking up the price of 1 cup, and the total price of X cups, but not the value of X. The amountOfThisGood property is only expected for TypeAndQuantityNode, which indicates only the quality of goods in a *bundle* offer. Does it make sense for acceptedOffer to support a property that indicates the quantity of an item? Or am I just failing to recognize an extant method of expressing the quantity of a single item ordered in an acceptedOffer? It strikes me that schema.org now provides markup that supports an entire transaction as structured in Google Analytics [1] (between Order, Offer and Product - GA is obviously a much different data model), except for shipping, tax (both of these already addressed in the proposed clarifications) and quantity. [1] https://developers.google.com/analytics/devguides/collection/gajs/gaTrackingEcommerce#Example On Fri, Feb 7, 2014 at 11:10 AM, Dan Brickley <danbri@google.com> wrote: > I've just posted some proposed clarifications around schema.org price > markup to the wiki: > > https://www.w3.org/wiki/WebSchemas/PriceClarifications > > Basic idea is to allow an order to express the price paid, and to > clarify whether the existing property http://schema.org/price is for > unit versus total. Vicki's investigations into current usage suggested > the former, therefore the schema.org partners are proposing that we > add a http://schema.org/totalPrice property to meet the total price > use case for Order. > > Dan > >
Received on Friday, 7 February 2014 20:23:45 UTC