Author: G. Ken Holman
Date: $Date: 2003/02/10 22:11:56 $(UTC)
Copyright © 2003 OASIS
This formatting specification describes a rendering of the UBL Despatch Advice document model according to the United Nations Layout Key for Trade Documents guidelines for application for the 351 despatch advice form:
351 Despatch Advice: Document by means of which the seller or consignor informs the consignee about the despatch of goods.
For a list of all formatting specifications and an overview of the documentation conventions, please visit the formatting specification home page.
This specification has no formal status at this time. It should not be considered a reference interpretation of UBL documents. Feedback is sought from users of stylesheets that implement this formatting specification regarding suggestions for change for consideration by the OASIS UBL committees for incorporation into these formatting specifications.
Presentational semantics may never be formalized or normative in the UBL project due to differing international requirements and conventions for the presentation of information found in business documents. This document contains only examples from a few of what will probably be many available UBL stylesheet libraries.
Example renderings:
PDF printable format (A4 page size)
PDF printable format (US letter page size)
HTML browser format
Note the above examples are produced using Crane's XSLT and XSL-FO stylesheets. The HTML and XSL-FO are created by running the Saxon XSLT processor http://saxon.sourceforge.net/. The PDF is created by running the Antenna House XSL Formatter Version 2.3 http://www.AntennaHouse.com (with their gracious permission) to produce PostScript from XSL-FO and GhostScript AFPL http://www.GhostScript.com to distill PDF from the PostScript.
Example implementations:
These implementations must not be considered as reference implementations of UBL formatting specifications or as normative components of the UBL delivery; they are merely examples from what will probably be many available UBL stylesheet libraries.
XSLT and XSL-FO stylesheets in clear text from Crane Softwrights Ltd.:
release version: crane-ublss-20030214-0410.zip
latest version: http://www.CraneSoftwrights.com/links/res-ublo.htm
Java JAR standalone implementation of Crane's XSLT and XSL-FO stylesheets from Ambrosoft, Inc.:
release version: ambrosoft-crane-ublss-20030214-0420.zip
latest version: http://www.ambrosoft.com
Items in this formatting specification are ordered roughly from the laid out fields on the form in the order left-to-right, top to bottom.
Certain descriptions are verbatim quotes from the United Nations guidelines document.
Important: the rendering of a number of fields is very simplified, reflecting a Western European interpretation of a subset of fields (as in names and addresses). User requirements need to be better understood for the level of granularity in these stylesheets.
The following namespaces are mapped to the prefixes in the expressions below:
da = "urn:oasis:names:tc:ubl:DespatchAdvice:1.0:0.70"
cat = "urn:oasis:names:tc:ubl:CommonAggregateTypes:1.0:0.70"
The following information is unrelated to the visible fields of the form.
Path |
/da:DespatchAdvice/cat:ID |
/da:DespatchAdvice/cat:IssueDate |
This information shows up in the window-title bar of the HTML browser, and in the document title supported by some XSL-FO processors.
The information in the document header isn't revealed anywhere in the body of the form; is this acceptable? Should it be changed?
Header information is associated with the form as a whole, not to the individual items of goods.
Path |
/da:DespatchAdvice/cat:SellerParty/cat:PartyName/cat:Name |
/da:DespatchAdvice/cat:SellerParty/cat:Address/cat:Street |
/da:DespatchAdvice/cat:SellerParty/cat:Address/cat:CityName |
/da:DespatchAdvice/cat:SellerParty/cat:Address/cat:CountrySub-EntityCode |
/da:DespatchAdvice/cat:SellerParty/cat:Address/cat:Country/cat:Code |
This field is intended to show the name and address of the sender of goods or the originator of the documents, as the case may be.
Path |
/da:DespatchAdvice/cat:ReferencedOrder/cat:SellersOrderID |
reference for the goods
Path |
/da:DespatchAdvice/cat:ReferencedOrder/cat:BuyersOrderID |
reference for the goods
The field for the name and address of the consignee has been located in conformity with international postal specifications so as to allow the use of window envelopes.
The contents of this field is the same as the 3.5 Buyer field.
Path |
/da:DespatchAdvice/cat:BuyerParty/cat:PartyName/cat:Name |
/da:DespatchAdvice/cat:BuyerParty/cat:Address/cat:Street |
/da:DespatchAdvice/cat:BuyerParty/cat:Address/cat:CityName |
/da:DespatchAdvice/cat:BuyerParty/cat:Address/cat:CountrySub-EntityCode |
/da:DespatchAdvice/cat:BuyerParty/cat:Address/cat:Country/cat:Code |
The field for the name and address to which documents are sent (buyer).
Transportation fields that are header-like and applicable to the entire order.
Path |
/da:DespatchAdvice/cat:ActualShipment/cat:ShipmentStage/cat:TransportModeCode |
NB may be more than one
How should multiple mode of transport fields be formatted?
Path |
/da:DespatchAdvice/cat:ActualShipment/cat:ShipmentStage/cat:TransitPeriod/cat:StartDateTimeDate |
Use the earliest date (if more than one)
The "earliest" test hasn't yet been implemented.
Path |
/da:DespatchAdvice/cat:ActualShipment/cat:ShipmentStage/cat:TransportMeansTypeCode |
NB may be more than one
How should multiple means of transport fields be formatted?
Path |
/da:DespatchAdvice/cat:DeliveryRequirement/cat:SendFromAddress/cat:CityName |
/da:DespatchAdvice/cat:DeliveryRequirement/cat:SendFromAddress/cat:Country/cat:Code |
Despatch is the required place
Currently omitted from library (to be resolved)
Path |
/da:DespatchAdvice/cat:ActualShipment/cat:DeliveryRequirement/cat:SendFromAddress/cat:CityName |
/da:DespatchAdvice/cat:ActualShipment/cat:DeliveryRequirement/cat:SendFromToAddress/cat:Country/cat:Code |
Loading is the actual place
Path |
/da:DespatchAdvice/cat:ActualShipment/cat:DeliveryRequirement/cat:DeliverToAddress/cat:CityName |
/da:DespatchAdvice/cat:ActualShipment/cat:DeliveryRequirement/cat:DeliverToAddress/cat:Country/cat:Code |
Discharge is the actual place
Path |
/da:DespatchAdvice/cat:DeliveryRequirement/cat:DeliverToAddress/cat:CityName |
/da:DespatchAdvice/cat:DeliveryRequirement/cat:DeliverToAddress/cat:Country/cat:Code |
Delivery is the required place
Goods information is associated with the individual items of the goods in the shipment
Path |
/da:DespatchAdvice/cat:DespatchedTransportHandlingUnit/cat:ID |
This field is not clearly defined in the message
Path |
/da:DespatchAdvice/cat:ActualShipment/cat:TransportEquipment/cat:ID |
NB may be many of these
How should multiple container number fields be formatted?
Path |
/da:DespatchAdvice/cat:DespatchedTransportHandlingUnit/cat:TypeCode |
/da:DespatchAdvice/cat:ActualShipment/cat:DeliveryRequirement/cat:OrderLine/cat:Quantity |
/da:DespatchAdvice/cat:ActualShipment/cat:DeliveryRequirement/cat:OrderLine/cat:Item/cat:Description |
Path |
/da:DespatchAdvice/cat:ActualShipment/cat:GrossWeightMeasure |
The gross weight of the shipment
Summary information is associated with the form as a whole, not to the individual items of goods.
Path |
/da:DespatchAdvice/da:Notes |
How should multiple notes be formatted? Need they be enumerated? Any impact on "footnote"-like pointers?
Path |
/da:DespatchAdvice/cat:FreightForwarderParty/cat:PartyName/cat:Name |
/da:DespatchAdvice/cat:FreightForwarderParty/cat:Address/cat:Street |
/da:DespatchAdvice/cat:FreightForwarderParty/cat:Address/cat:CityName |
/da:DespatchAdvice/cat:FreightForwarderParty/cat:Address/cat:CountrySub-EntityCode |
/da:DespatchAdvice/cat:FreightForwarderParty/cat:Address/cat:Country/cat:Code |
Path |
/da:DespatchAdvice/cat:FreightForwarderParty/cat:Contact/cat:Name |
The information in the document header isn't revealed anywhere in the body of the form; is this acceptable? Should it be changed?
Note 2: 4.1 - Mode of transportHow should multiple mode of transport fields be formatted?
Note 3: 4.2 - Date of despatchThe "earliest" test hasn't yet been implemented.
Note 4: 4.3 - Means of transportHow should multiple means of transport fields be formatted?
Note 5: 5.2 - Container Nr.How should multiple container number fields be formatted?
Note 6: 6.1 - Documentary instructionsHow should multiple notes be formatted? Need they be enumerated? Any impact on "footnote"-like pointers?
UN layout formatting specification for UBL Despatch Advice instances
G. Ken Holman
Copyright © 2003 OASIS
$Date: 2003/02/10 22:11:56 $(UTC)