Copyright © 2003 OASIS
$Date: 2003/11/18 15:40:30 $(UTC)
Table of Contents
This formatting specification describes a rendering of an instance of the UBL Order document model according to a conceptual office-oriented layout.
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)
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.
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 formatting specifications.
The following information is unrelated to the visible fields of the form.
Header information is associated with the form as a whole, not to the individual items of goods.
The reference number is a number or designation preferably common throughout each set of documents.
If not otherwise specified, "date" means the date of issue of the document in which it appears.
Table 4. XPath information
| XPath addresses |
| /po:Order/cat:SellerParty/cat:Party/cat:PartyName/cat:Name |
| /po:Order/cat:SellerParty/cat:Party/cat:Address/cat:StreetName |
| /po:Order/cat:SellerParty/cat:Party/cat:Address/cat:CityName |
| /po:Order/cat:SellerParty/cat:Party/cat:Address/cat:PostalZone |
| /po:Order/cat:SellerParty/cat:Party/cat:Address/cat:CountrySubentityCode |
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.
Table 5. XPath information
| XPath addresses |
| /po:Order/cat:BuyerParty/cat:Party/cat:PartyName/cat:Name |
| /po:Order/cat:BuyerParty/cat:Party/cat:Address/cat:StreetName |
| /po:Order/cat:BuyerParty/cat:Party/cat:Address/cat:CityName |
| /po:Order/cat:BuyerParty/cat:Party/cat:Address/cat:PostalZone |
| /po:Order/cat:BuyerParty/cat:Party/cat:Address/cat:CountrySubentityCode |
The field for the name and address to which documents are sent (buyer).
The buyer's contact for the order
Table 7. XPath information
| XPath addresses |
| /po:Order/cat:Delivery/cat:DeliverToAddress/cat:StreetName |
| /po:Order/cat:Delivery/cat:DeliverToAddress/cat:CityName |
| /po:Order/cat:Delivery/cat:DeliverToAddress/cat:PostalZone |
| /po:Order/cat:Delivery/cat:DeliverToAddress/cat:CountrySubentityCode |
The address where the order is being delivered.
Line item information is associated with the individual items of the goods in the order.
This is the reference to the Order line.
Table 12. XPath information
| XPath address |
| /po:Order/cat:OrderLine/cat:LineItem/cat:Item/cat:Description |
One of these exists for each Line item.
Table 13. XPath information
| XPath addresses |
| /po:Order/cat:OrderLine/cat:LineItem/cat:Quantity |
| /po:Order/cat:OrderLine/cat:LineItem/cat:Quantity/@unitCode |
One of these exists for each line item.
Summary information is associated with the form as a whole, not to the individual items of goods.