Databases Reference
In-Depth Information
<xsd:complexTypename="tOrder">
<xsd:sequence>
<xsd:elementname="
orderNo
"type="xsd:string"/>
<xsd:elementname="orderDesc"type="xsd:string"/>
<xsd:elementname="itemId"type="act:tItemId"/>
<xsd:elementname="sellerId"type="act:tUserId"/>
<xsd:elementname="buyerId"type="act:tUserId"/>
<xsd:elementname="orderDetail"type="act:tOrderDetail"/>
<xsd:elementname="
shipTo
"type="act:tShipTo"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexTypename="tOrderDetail">
<xsd:sequence>
<xsd:elementname="orderDate"type="xsd:date"/>
<xsd:elementname="
orderStatus
"type="xsd:string"/>
<xsd:elementname="quantity"type="xsd:int"/>
<xsd:elementname="itemPrice"type="xsd:decimal"/>
<xsd:elementname="subTotal"type="xsd:decimal"/>
<xsd:elementname="
shippingPrice
"type="xsd:decimal"/>
<xsd:elementname="totalPrice"type="xsd:decimal"/>
<xsd:elementname="lastUpdateDate"type="xsd:dateTime"/>
<xsd:elementname="nextAction"type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexTypename="tShipTo">
<xsd:sequence>
<xsd:elementname="shippingName"type="xsd:string"/>
<xsd:elementname="shippingAddress"type="act:tAddress"/>
<xsd:elementname="additionalInstructions"type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
Before we go any further, it's worth spending a moment to highlight some of the key
components of this:
•
OrderNo
: Potentially we could have multiple orders per auction
(for example, if oBay were to support a Dutch auction format at some
point in the future), so every order will need its own unique identifier.
As we have made the decision to have a single human task, we have a
one-to-one mapping between an order and an
OrderFulfillment
human
task, so will use the task number as our order number.
