Office-oriented formatting specification for UBL Order Response Simple example instance

Copyright © 2004 OASIS

$Date: 2004/09/05 15:14:03 $(UTC)

Table of Contents

1. Simple order response formatting specification
1.1. Status
1.2. Example rendering
1.3. Layout order and information
1.4. Namespaces
2. Miscellaneous information
2.1. Document header information
3. Header information
3.1. Purchase Order Number
3.2. Sales Order Number
3.3. Order Date
3.4. Response Date
3.5. To
3.6. From
3.7. Order Contact

1.  Simple order response formatting specification

This formatting specification describes a rendering of an instance of the UBL Order Response Simple 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.

1.1.  Status

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.

1.2.  Example rendering

The following is an example rendering that illustrates the position and decoration of the information items found in an instance of the document type:

1.3.  Layout order and information

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 stylesheets.

1.4.  Namespaces

The following namespaces are mapped to the prefixes in the expressions below:

  • cac = "urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-1.0"

    cbc = "urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-1.0"

    rs = "urn:oasis:names:specification:ubl:schema:xsd:OrderResponseSimple-1.0"

2.  Miscellaneous information

The following information is unrelated to the visible fields of the form.

2.1.  Document header information

Table 1. XPath information

XPath addresses
/​rs:OrderResponseSimple/​rs:ID
/​rs:OrderResponseSimple/​cbc: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.

3. Header information

Header information is associated with the form as a whole, not to the individual items of goods.

3.1. Purchase Order Number

Table 2. XPath information

XPath address
/​rs:OrderResponseSimple/​cac:OrderReference/​cac:BuyersID

3.2. Sales Order Number

Table 3. XPath information

XPath address
/​rs:OrderResponseSimple/​cac:OrderReference/​cac:SellersID

3.3. Order Date

Table 4. XPath information

XPath address
/​rs:OrderResponseSimple/​cac:OrderReference/​cbc:IssueDate

3.4. Response Date

Table 5. XPath information

XPath address
/​rs:OrderResponseSimple/​cbc:IssueDate

3.5. To

Table 6. XPath information

XPath address
/​rs:OrderResponseSimple/​cac:BuyerParty/​cac:Party/​cac:PartyName/​cbc:Name

3.6. From

Table 7. XPath information

XPath address
/​rs:OrderResponseSimple/​cac:SellerParty/​cac:Party/​cac:PartyName/​cbc:Name

3.7. Order Contact

Table 8. XPath information

XPath address
/​rs:OrderResponseSimple/​cac:SellerParty/​cac:OrderContact/​cbc:Name