[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: A Despatch Request Schema draft Re: [ubl-dev] Modelling internaldocuments with UBL v2.0
Sorry, the schema might be preserved by mail system better if I send as attachment (zipped as well just in case) -- Stephen D. Green Partner SystML, http://www.systml.co.uk Tel: +44 (0) 117 9541606 http://www.biblegateway.com/passage/?search=matthew+22:37 .. and voice Quoting stephen.green@systml.co.uk: > Although it would seem straightforward to use Despatch Advice > in reverse it starts to get a bit more complex than that when > you consider the document line requirements. DespatchLine isn't > appropriate (too many of its entities assume Despatch has already > happened). > > Also, since there are inappropriate definitions in the Despatch > Advice at document level (document definition and definitions > for IDs and dates which apply to issue by the Despatch Party), > along the need to use a different type of Line, it seems that > strictly speaking, if you want to be compliant with UBL, you > would need to create a new document schema. You can base most > of it on DespatchAdvice but perhaps call it DespatchRequest. > You probably need to create a new line element and type too > which means you probably need to create your own > CommonAggregateComponents schema as well; unless LineItem, say, > would be sufficient. > > It wouldn't be difficult though, just that you'd need to host it > and supply your own namespaces for the document and the line. If > it is for internal use that might be economically feasible for > your company (perhaps you've no need to persuade other companies > to use your schema). > > I tried a quick feasibility draft (using my SystML purl to create > a draft namespace) with LineItem as the line type. Maybe it would > be enough for you. Feel free to change the namespace of course. > Provided as is with no warranty of course. I think the copyright > notices are adequate (but UBL TC is checking what OASIS requires > for this at this moment). > ... > -- > Stephen D. Green > > Partner > SystML, http://www.systml.co.uk > Tel: +44 (0) 117 9541606 > > http://www.biblegateway.com/passage/?search=matthew+22:37 .. and voice > > > > Quoting Stephen Green <stephengreenubl@gmail.com>: > >> I would think a Request for Delivery is a Delivery Advice in reverse >> - sent from receiver to deliverer. In that case you might be able to >> use the Delivery Advice but with some care over how the ID works. >> The ID will then be the ID given it by the receiver, rather than the >> delivery party. (A parallel is with the use of Order as a Sales Order >> or with some punch-out when the order is produced by the seller.) >> >> On 01/02/2008, JAVEST <roberto@javest.com> wrote: >>> Hello Michael, >>> >>> I agree with the use of UBL Order for the Warehouse Requisition but I do >>> not understend perfectly the "Request for Delivery", can you please show >>> in a timeline when it is used exactly ? >>> >>> For a fast and easy evaluation and understanding of UBL Documents and >>> business entities I suggest you to use "UBL Swinger" software available >>> for free at www.javest.com >>> >>> This software show you on the right side the UBL documentation >>> dinamically (where sometime is available a sample for input data too). >>> >>> Hope this helps. >>> >>> Roberto Cisternino >>> >>> --- >>> >>> Michael Strasser ha scritto: >>>> I am new to UBL (but not to XML) and am looking to model five >>> documents to be generated by one of our systems that will be >>> converted into faxes to be sent both internally and externally. I >>> looked for standard XML vocabularies for such documents and >>> naturally found UBL. >>>> >>>> The documents are Purchase Order, Remittance Advice, Request for >>> Quotation, Warehouse Requesition and Request for Delivery >>> (expedite letters for ordered items outstanding). The first three >>> map directly to their UBL namesakes. >>>> >>>> The other two are not so simple. My instinct is that Warehouse >>> Requisition is really a type of order where the seller is another >>> part of our organisation. I'm not sure about Request for >>> Delivery. I suspect that UBL-Order may model it as well but I'm >>> don't know if these requests can refer to multiple previous >>> orders. Does this sound reasonable or have I missed a document >>> type? >>>> >>>> I may also ask questions about how to cope with UBL's complexity. >>> The range of choices appear overwhelming at first and I am looking >>> for some best-practice or common-practice advice in using >>> documents and common components. That advice may be from the list >>> or from resources you recommend. >>>> >>>> I really appreciate any help you can give on any of these matters. >>>> >>>> >>>> Regards >>>> >>>> Michael Strasser >>>> Enterprise ICT Architecture >>>> Brisbane City Council >>>> Brisbane, Australia >>>> >>>> >>>> >>>> ********************************************************************** >>>> This message has passed through an insecure network. >>>> Please direct all enquiries to the message author. >>>> ********************************************************************** >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: ubl-dev-unsubscribe@lists.oasis-open.org >>>> For additional commands, e-mail: ubl-dev-help@lists.oasis-open.org >>>> >>>> >>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: ubl-dev-unsubscribe@lists.oasis-open.org >>> For additional commands, e-mail: ubl-dev-help@lists.oasis-open.org >>> >>> >> >> >> -- >> Stephen D. Green >> >> Partner >> SystML, http://www.systml.co.uk >> Tel: +44 (0) 117 9541606 >> >> http://www.biblegateway.com/passage/?search=matthew+22:37 .. and voice >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: ubl-dev-unsubscribe@lists.oasis-open.org >> For additional commands, e-mail: ubl-dev-help@lists.oasis-open.org >> >> > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: ubl-dev-unsubscribe@lists.oasis-open.org > For additional commands, e-mail: ubl-dev-help@lists.oasis-open.org
<?xml version="1.0" encoding="UTF-8"?>
<!--
Document Type: DespatchRequest
Edited On: Fri Feb 01 18:17 P3 2008
-->
<!-- ===== xsd:schema Element With Namespaces Declarations ===== -->
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema";
targetNamespace="http://purl.oclc.org/NET/systml#draft:ubl:schema:xsd:DespatchRequest-2";
xmlns="http://purl.oclc.org/NET/systml#draft:ubl:schema:xsd:DespatchRequest-2";
xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2"
xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2"
xmlns:udt="urn:un:unece:uncefact:data:specification:UnqualifiedDataTypesSchemaModule:2"
xmlns:ccts="urn:un:unece:uncefact:documentation:2"
xmlns:ext="urn:oasis:names:specification:ubl:schema:xsd:CommonExtensionComponents-2"
xmlns:qdt="urn:oasis:names:specification:ubl:schema:xsd:QualifiedDatatypes-2"
elementFormDefault="qualified"
attributeFormDefault="unqualified"
version="2.0">
<!-- ===== Imports ===== -->
<xsd:import namespace="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2" schemaLocation="http://docs.oasis-open.org/ubl/os-UBL-2.0/xsd/common/UBL-CommonAggregateComponents-2.0.xsd"/>
<xsd:import namespace="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2" schemaLocation="http://docs.oasis-open.org/ubl/os-UBL-2.0/xsd/common/UBL-CommonBasicComponents-2.0.xsd"/>
<xsd:import namespace="urn:un:unece:uncefact:data:specification:UnqualifiedDataTypesSchemaModule:2" schemaLocation="http://docs.oasis-open.org/ubl/os-UBL-2.0/xsd/common/UnqualifiedDataTypeSchemaModule-2.0.xsd"/>
<xsd:import namespace="urn:oasis:names:specification:ubl:schema:xsd:CommonExtensionComponents-2" schemaLocation="http://docs.oasis-open.org/ubl/os-UBL-2.0/xsd/common/UBL-CommonExtensionComponents-2.0.xsd"/>
<xsd:import namespace="urn:oasis:names:specification:ubl:schema:xsd:QualifiedDatatypes-2" schemaLocation="http://docs.oasis-open.org/ubl/os-UBL-2.0/xsd/common/UBL-QualifiedDatatypes-2.0.xsd"/>
<!-- ===== Root Element ===== -->
<xsd:element name="DespatchRequest" type="DespatchRequestType">
<xsd:annotation>
<xsd:documentation>This element MUST be conveyed as the root element in any instance document based on this Schema expression</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="DespatchRequestType">
<xsd:annotation>
<xsd:documentation>
<ccts:Component>
<ccts:ComponentType>ABIE</ccts:ComponentType>
<ccts:DictionaryEntryName>Despatch Advice. Details</ccts:DictionaryEntryName>
<ccts:Definition>The document used to describe the despatch or delivery of goods and services.</ccts:Definition>
<ccts:ObjectClass>Despatch Request</ccts:ObjectClass>
<ccts:AlternativeBusinessTerms>Ship Note, Dispatch Advice, Consignment Note</ccts:AlternativeBusinessTerms>
</ccts:Component>
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element ref="ext:UBLExtensions" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>A container for all extensions present in the document.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element ref="cbc:UBLVersionID" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
<ccts:Component>
<ccts:ComponentType>BBIE</ccts:ComponentType>
<ccts:DictionaryEntryName>Despatch Request. UBL Version Identifier. Identifier</ccts:DictionaryEntryName>
<ccts:Definition>The earliest version of the UBL 2 schema for this document type that defines all of the elements that might be encountered in the current instance.</ccts:Definition>
<ccts:Cardinality>0..1</ccts:Cardinality>
<ccts:ObjectClass>Despatch Request</ccts:ObjectClass>
<ccts:PropertyTerm>UBL Version Identifier</ccts:PropertyTerm>
<ccts:RepresentationTerm>Identifier</ccts:RepresentationTerm>
<ccts:DataType>Identifier. Type</ccts:DataType>
<ccts:Examples>2.0.5</ccts:Examples>
</ccts:Component>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element ref="cbc:CustomizationID" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
<ccts:Component>
<ccts:ComponentType>BBIE</ccts:ComponentType>
<ccts:DictionaryEntryName>Despatch Request. Customization Identifier. Identifier</ccts:DictionaryEntryName>
<ccts:Definition>Identifies a user-defined customization of UBL for a specific use.</ccts:Definition>
<ccts:Cardinality>0..1</ccts:Cardinality>
<ccts:ObjectClass>Despatch Request</ccts:ObjectClass>
<ccts:PropertyTerm>Customization Identifier</ccts:PropertyTerm>
<ccts:RepresentationTerm>Identifier</ccts:RepresentationTerm>
<ccts:DataType>Identifier. Type</ccts:DataType>
<ccts:Examples>NES</ccts:Examples>
</ccts:Component>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element ref="cbc:ProfileID" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
<ccts:Component>
<ccts:ComponentType>BBIE</ccts:ComponentType>
<ccts:DictionaryEntryName>Despatch Request. Profile Identifier. Identifier</ccts:DictionaryEntryName>
<ccts:Definition>Identifies a user-defined profile of the customization of UBL being used.</ccts:Definition>
<ccts:Cardinality>0..1</ccts:Cardinality>
<ccts:ObjectClass>Despatch Request</ccts:ObjectClass>
<ccts:PropertyTerm>Profile Identifier</ccts:PropertyTerm>
<ccts:RepresentationTerm>Identifier</ccts:RepresentationTerm>
<ccts:DataType>Identifier. Type</ccts:DataType>
<ccts:Examples>BasicProcurementProcess</ccts:Examples>
</ccts:Component>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element ref="cbc:ID" minOccurs="1" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
<ccts:Component>
<ccts:ComponentType>BBIE</ccts:ComponentType>
<ccts:DictionaryEntryName>Despatch Request. Identifier</ccts:DictionaryEntryName>
<ccts:Definition>An identifier for the Despatch Request assigned by Delivery Customer (Party).</ccts:Definition>
<ccts:Cardinality>1</ccts:Cardinality>
<ccts:ObjectClass>Despatch Request</ccts:ObjectClass>
<ccts:PropertyTerm>Identifier</ccts:PropertyTerm>
<ccts:RepresentationTerm>Identifier</ccts:RepresentationTerm>
<ccts:DataType>Identifier. Type</ccts:DataType>
</ccts:Component>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element ref="cbc:CopyIndicator" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
<ccts:Component>
<ccts:ComponentType>BBIE</ccts:ComponentType>
<ccts:DictionaryEntryName>Despatch Request. Copy_ Indicator. Indicator</ccts:DictionaryEntryName>
<ccts:Definition>Indicates whether the Despatch Request is a copy (true) or not (false).</ccts:Definition>
<ccts:Cardinality>0..1</ccts:Cardinality>
<ccts:ObjectClass>Despatch Request</ccts:ObjectClass>
<ccts:PropertyTermQualifier>Copy</ccts:PropertyTermQualifier>
<ccts:PropertyTerm>Indicator</ccts:PropertyTerm>
<ccts:RepresentationTerm>Indicator</ccts:RepresentationTerm>
<ccts:DataType>Indicator. Type</ccts:DataType>
</ccts:Component>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element ref="cbc:UUID" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
<ccts:Component>
<ccts:ComponentType>BBIE</ccts:ComponentType>
<ccts:DictionaryEntryName>Despatch Request. UUID. Identifier</ccts:DictionaryEntryName>
<ccts:Definition>A universally unique identifier for an instance of this ABIE.</ccts:Definition>
<ccts:Cardinality>0..1</ccts:Cardinality>
<ccts:ObjectClass>Despatch Request</ccts:ObjectClass>
<ccts:PropertyTerm>UUID</ccts:PropertyTerm>
<ccts:RepresentationTerm>Identifier</ccts:RepresentationTerm>
<ccts:DataType>Identifier. Type</ccts:DataType>
</ccts:Component>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element ref="cbc:IssueDate" minOccurs="1" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
<ccts:Component>
<ccts:ComponentType>BBIE</ccts:ComponentType>
<ccts:DictionaryEntryName>Despatch Request. Issue Date. Date</ccts:DictionaryEntryName>
<ccts:Definition>The date assigned by Delivery Customer (Party) on which the Despatch Request was issued.</ccts:Definition>
<ccts:Cardinality>1</ccts:Cardinality>
<ccts:ObjectClass>Despatch Request</ccts:ObjectClass>
<ccts:PropertyTerm>Issue Date</ccts:PropertyTerm>
<ccts:RepresentationTerm>Date</ccts:RepresentationTerm>
<ccts:DataType>Date. Type</ccts:DataType>
</ccts:Component>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element ref="cbc:IssueTime" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
<ccts:Component>
<ccts:ComponentType>BBIE</ccts:ComponentType>
<ccts:DictionaryEntryName>Despatch Request. Issue Time. Time</ccts:DictionaryEntryName>
<ccts:Definition>The time assigned by Delivery Customer (Party) at which the Despatch Request was issued.</ccts:Definition>
<ccts:Cardinality>0..1</ccts:Cardinality>
<ccts:ObjectClass>Despatch Request</ccts:ObjectClass>
<ccts:PropertyTerm>Issue Time</ccts:PropertyTerm>
<ccts:RepresentationTerm>Time</ccts:RepresentationTerm>
<ccts:DataType>Time. Type</ccts:DataType>
</ccts:Component>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element ref="cbc:DocumentStatusCode" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
<ccts:Component>
<ccts:ComponentType>BBIE</ccts:ComponentType>
<ccts:DictionaryEntryName>Despatch Request. Document Status. Code</ccts:DictionaryEntryName>
<ccts:Definition>Identifies the status of the Despatch Request with respect to its original state. This may be used if the document precedes the event and is subsequently found to be incorrect and in need of cancelling or revising.</ccts:Definition>
<ccts:Cardinality>0..1</ccts:Cardinality>
<ccts:ObjectClass>Despatch Request</ccts:ObjectClass>
<ccts:PropertyTerm>Document Status</ccts:PropertyTerm>
<ccts:RepresentationTerm>Code</ccts:RepresentationTerm>
<ccts:DataType>Document Status_ Code. Type</ccts:DataType>
</ccts:Component>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element ref="cbc:Note" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
<ccts:Component>
<ccts:ComponentType>BBIE</ccts:ComponentType>
<ccts:DictionaryEntryName>Despatch Request. Note. Text</ccts:DictionaryEntryName>
<ccts:Definition>Free-form text applying to the Despatch Request. This element may contain notes or any other similar information that is not contained explicitly in another structure.</ccts:Definition>
<ccts:Cardinality>0..n</ccts:Cardinality>
<ccts:ObjectClass>Despatch Request</ccts:ObjectClass>
<ccts:PropertyTerm>Note</ccts:PropertyTerm>
<ccts:RepresentationTerm>Text</ccts:RepresentationTerm>
<ccts:DataType>Text. Type</ccts:DataType>
</ccts:Component>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element ref="cbc:LineCountNumeric" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
<ccts:Component>
<ccts:ComponentType>BBIE</ccts:ComponentType>
<ccts:DictionaryEntryName>Despatch Request. Line Count. Numeric</ccts:DictionaryEntryName>
<ccts:Definition>The number of lines in the document.</ccts:Definition>
<ccts:Cardinality>0..1</ccts:Cardinality>
<ccts:ObjectClass>Despatch Request</ccts:ObjectClass>
<ccts:PropertyTerm>Line Count</ccts:PropertyTerm>
<ccts:RepresentationTerm>Numeric</ccts:RepresentationTerm>
<ccts:DataType>Numeric. Type</ccts:DataType>
</ccts:Component>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element ref="cac:OrderReference" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
<ccts:Component>
<ccts:ComponentType>ASBIE</ccts:ComponentType>
<ccts:DictionaryEntryName>Despatch Request. Order Reference</ccts:DictionaryEntryName>
<ccts:Definition>An association to Order Reference.</ccts:Definition>
<ccts:Cardinality>0..n</ccts:Cardinality>
<ccts:ObjectClass>Despatch Request</ccts:ObjectClass>
<ccts:PropertyTerm>Order Reference</ccts:PropertyTerm>
<ccts:AssociatedObjectClass>Order Reference</ccts:AssociatedObjectClass>
</ccts:Component>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element ref="cac:AdditionalDocumentReference" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
<ccts:Component>
<ccts:ComponentType>ASBIE</ccts:ComponentType>
<ccts:DictionaryEntryName>Despatch Request. Additional_ Document Reference. Document Reference</ccts:DictionaryEntryName>
<ccts:Definition>An associative reference to Additional Document.</ccts:Definition>
<ccts:Cardinality>0..n</ccts:Cardinality>
<ccts:ObjectClass>Despatch Request</ccts:ObjectClass>
<ccts:PropertyTermQualifier>Additional</ccts:PropertyTermQualifier>
<ccts:PropertyTerm>Document Reference</ccts:PropertyTerm>
<ccts:AssociatedObjectClass>Document Reference</ccts:AssociatedObjectClass>
</ccts:Component>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element ref="cac:Signature" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
<ccts:Component>
<ccts:ComponentType>ASBIE</ccts:ComponentType>
<ccts:DictionaryEntryName>Despatch Request. Signature</ccts:DictionaryEntryName>
<ccts:Definition>An association to Signature.</ccts:Definition>
<ccts:Cardinality>0..n</ccts:Cardinality>
<ccts:ObjectClass>Despatch Request</ccts:ObjectClass>
<ccts:PropertyTerm>Signature</ccts:PropertyTerm>
<ccts:AssociatedObjectClass>Signature</ccts:AssociatedObjectClass>
</ccts:Component>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element ref="cac:DeliveryCustomerParty" minOccurs="1" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
<ccts:Component>
<ccts:ComponentType>ASBIE</ccts:ComponentType>
<ccts:DictionaryEntryName>Despatch Request. Delivery_ Customer Party. Customer Party</ccts:DictionaryEntryName>
<ccts:Definition>An association to the Delivery Party.</ccts:Definition>
<ccts:Cardinality>1</ccts:Cardinality>
<ccts:ObjectClass>Despatch Request</ccts:ObjectClass>
<ccts:PropertyTermQualifier>Delivery</ccts:PropertyTermQualifier>
<ccts:PropertyTerm>Customer Party</ccts:PropertyTerm>
<ccts:AssociatedObjectClass>Customer Party</ccts:AssociatedObjectClass>
</ccts:Component>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element ref="cac:DespatchSupplierParty" minOccurs="1" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
<ccts:Component>
<ccts:ComponentType>ASBIE</ccts:ComponentType>
<ccts:DictionaryEntryName>Despatch Request. Despatch_ Supplier Party. Supplier Party</ccts:DictionaryEntryName>
<ccts:Definition>An association to the Despatch Party.</ccts:Definition>
<ccts:Cardinality>1</ccts:Cardinality>
<ccts:ObjectClass>Despatch Request</ccts:ObjectClass>
<ccts:PropertyTermQualifier>Despatch</ccts:PropertyTermQualifier>
<ccts:PropertyTerm>Supplier Party</ccts:PropertyTerm>
<ccts:AssociatedObjectClass>Supplier Party</ccts:AssociatedObjectClass>
</ccts:Component>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element ref="cac:BuyerCustomerParty" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
<ccts:Component>
<ccts:ComponentType>ASBIE</ccts:ComponentType>
<ccts:DictionaryEntryName>Despatch Request. Buyer_ Customer Party. Customer Party</ccts:DictionaryEntryName>
<ccts:Definition>An association to the Buyer.</ccts:Definition>
<ccts:Cardinality>0..1</ccts:Cardinality>
<ccts:ObjectClass>Despatch Request</ccts:ObjectClass>
<ccts:PropertyTermQualifier>Buyer</ccts:PropertyTermQualifier>
<ccts:PropertyTerm>Customer Party</ccts:PropertyTerm>
<ccts:AssociatedObjectClass>Customer Party</ccts:AssociatedObjectClass>
</ccts:Component>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element ref="cac:SellerSupplierParty" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
<ccts:Component>
<ccts:ComponentType>ASBIE</ccts:ComponentType>
<ccts:DictionaryEntryName>Despatch Request. Seller_ Supplier Party. Supplier Party</ccts:DictionaryEntryName>
<ccts:Definition>An association to the Seller.</ccts:Definition>
<ccts:Cardinality>0..1</ccts:Cardinality>
<ccts:ObjectClass>Despatch Request</ccts:ObjectClass>
<ccts:PropertyTermQualifier>Seller</ccts:PropertyTermQualifier>
<ccts:PropertyTerm>Supplier Party</ccts:PropertyTerm>
<ccts:AssociatedObjectClass>Supplier Party</ccts:AssociatedObjectClass>
</ccts:Component>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element ref="cac:OriginatorCustomerParty" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
<ccts:Component>
<ccts:ComponentType>ASBIE</ccts:ComponentType>
<ccts:DictionaryEntryName>Despatch Request. Originator_ Customer Party. Customer Party</ccts:DictionaryEntryName>
<ccts:Definition>An association to the Originator (Party).</ccts:Definition>
<ccts:Cardinality>0..1</ccts:Cardinality>
<ccts:ObjectClass>Despatch Request</ccts:ObjectClass>
<ccts:PropertyTermQualifier>Originator</ccts:PropertyTermQualifier>
<ccts:PropertyTerm>Customer Party</ccts:PropertyTerm>
<ccts:AssociatedObjectClass>Customer Party</ccts:AssociatedObjectClass>
</ccts:Component>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element ref="cac:Shipment" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
<ccts:Component>
<ccts:ComponentType>ASBIE</ccts:ComponentType>
<ccts:DictionaryEntryName>Despatch Request. Shipment</ccts:DictionaryEntryName>
<ccts:Definition>An association to a Shipment detail.</ccts:Definition>
<ccts:Cardinality>0..1</ccts:Cardinality>
<ccts:ObjectClass>Despatch Request</ccts:ObjectClass>
<ccts:PropertyTerm>Shipment</ccts:PropertyTerm>
<ccts:AssociatedObjectClass>Shipment</ccts:AssociatedObjectClass>
</ccts:Component>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element ref="cac:LineItem" minOccurs="1" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
<ccts:Component>
<ccts:ComponentType>ASBIE</ccts:ComponentType>
<ccts:DictionaryEntryName>Despatch Request. Line Item</ccts:DictionaryEntryName>
<ccts:Definition>An association to one or more Line Items.</ccts:Definition>
<ccts:Cardinality>1..n</ccts:Cardinality>
<ccts:ObjectClass>Despatch Request</ccts:ObjectClass>
<ccts:PropertyTerm>Line Item</ccts:PropertyTerm>
<ccts:AssociatedObjectClass>Line Item</ccts:AssociatedObjectClass>
</ccts:Component>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<!-- ===== Element Declarations ===== -->
<!-- ===== Type Definitions ===== -->
<!-- ===== Basic Business Information Entity Type Definitions ===== -->
</xsd:schema>
<!-- ===== Copyright Notice ===== -->
<!--
OASIS takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to pertain
to the implementation or use of the technology described in this
document or the extent to which any license under such rights
might or might not be available; neither does it represent that it has
made any effort to identify any such rights. Information on OASIS's
procedures with respect to rights in OASIS specifications can be
found at the OASIS website. Copies of claims of rights made
available for publication and any assurances of licenses to be made
available, or the result of an attempt made to obtain a general
license or permission for the use of such proprietary rights by
implementors or users of this specification, can be obtained from
the OASIS Executive Director.
OASIS invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to
implement this specification. Please address the information to the
OASIS Executive Director.
Copyright (C) OASIS Open 2001-2006. All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain
it or assist in its implementation may be prepared, copied,
published and distributed, in whole or in part, without restriction of
any kind, provided that the above copyright notice and this
paragraph are included on all such copies and derivative works.
However, this document itself may not be modified in any way,
such as by removing the copyright notice or references to OASIS,
except as needed for the purpose of developing OASIS
specifications, in which case the procedures for copyrights defined
in the OASIS Intellectual Property Rights document must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by OASIS or its successors or assigns.
This document and the information contained herein is provided on
an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
WARRANTY THAT THE USE OF THE INFORMATION HEREIN
WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE.
-->
<!--
Copyright (C) SystML 2008. All Rights Reserved.
-->
UBL-SystML-DespatchRequest-2.0.zip
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]