- From: Kévin Dunglas <dunglas@gmail.com>
- Date: Tue, 28 Jan 2014 19:55:44 +0100
- To: Vicki Tardif Holland <vtardif@google.com>
- Cc: PublicVocabs <public-vocabs@w3.org>
Hi Vicki, Thank you for your answer, schema.org/ParcelDelivery is perfect for the shipmentDetail. What about the OrderItem type (the first part of my proposal)? In my opinion this is the best type to add the property pointing to ParcelDelivery 2014/1/27 Vicki Tardif Holland <vtardif@google.com>: > Hi Kevin, > > The schema.org/ParcelDelivery type has much of what you are looking for to > describe shipping details. However, there is no property from an Order to an > ParcelDelivery. (There is a property to get from a ParcelDelivery to an > order.) > > Would a reverse property from Order to ParcelDelivery satisfy your needs? > > - Vicki > > > Vicki Tardif Holland | Ontologist | vtardif@google.com > > > > On Sun, Jan 26, 2014 at 5:41 AM, Kévin Dunglas <dunglas@gmail.com> wrote: >> >> Hi, >> >> The new http://schema.org/Order type is great but, in my opinion, can >> be extended to be more useful and to match more existing models. >> The main drawback with this type is its support for multiple line items. >> >> * Many merchants such as Amazon, CDiscount or LaRedoute handle status >> at the order line level: one item can be "Processing" while another of >> the same order (ordered in the same time) is "In Transit". In the >> current vocable, the status is stored at the Order level, not at the >> Order item level, so it's impossible to represent case explained >> above. >> * In the current vocable, there is no notion of quantity for an order >> item. However, in almost all e-commerce platforms, a customer can >> order several times the same "Offer". (For instance, you can buy 3 >> t-shirts with SKU ABCDE). >> >> To fix this drawback, I propose to create a new type called OrderItem >> with the following properties: >> * quantity (Number): the number of acceptedOffer ordered >> * acceptedOffer (Offer): the accepted offer >> * orderItemStatus (OrderStatus): the order item status >> * orderItemNumber (Text): the order item number >> >> And to add a property orderItem to Order. >> >> Another thing that will be great to include in this vocable is shipment >> details. >> >> I propose to also add those properties to the new OrderItem type: >> * carrier (Carrier): the carrier >> * trackingNumber (Text): the tracking number >> * trackingUrl (URL): the tracking URL >> * shipmentDate (Date): the date of expedition >> >> And an extendable enumeration of carriers (Carrier) with values Like >> UPSCarrier, TNTCarrier... >> >> What do you think of that? >> -- >> Kévin Dunglas >> >> http://dunglas.fr >> >> > -- Kévin Dunglas http://dunglas.fr
Received on Tuesday, 28 January 2014 18:56:34 UTC