Office-oriented formatting specification for UBL Order instances

Author: G. Ken Holman
Date: $Date: 2003/02/10 21:27:44 $(UTC)

Copyright © 2003 OASIS

Table of contents

1: Purchase order formatting specification

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.

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 renderings and implementations

Example renderings:

• PDF printable format (A4 page size)

  • OfficeOrder.OfficeOrderInstance1.pdf

• PDF printable format (US letter page size)

  • OfficeOrder.OfficeOrderInstance1-us.pdf

• HTML browser format

  • OfficeOrder.OfficeOrderInstance1.html

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

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:

• po = "urn:oasis:names:tc:ubl:Order:1.0:0.70"

• cat = "urn:oasis:names:tc:ubl:CommonAggregateTypes:1.0:0.70"

2: Miscellaneous information

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

2.1: Document header information

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: Order No.

The reference number is a number or designation preferably common throughout each set of documents.

3.2: Issue Date

If not otherwise specified, "date" means the date of issue of the document in which it appears.

3.3: Seller

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.

3.4: Buyer

The field for the name and address to which documents are sent (buyer).

3.5: Contact

The buyer's contact for the order

3.6: Order Contact

This field is not filled in at this time

3.7: Delivery address

The address where the order is being delivered.

3.8: Requested Delivery Date

4: Line item information

Line item information is associated with the individual items of the goods in the order.

4.1: Line no.

This is the reference to the Order line.

4.2: Part number

4.3: Description

One of these exists for each Line item.

4.4: Quantity U/M

One of these exists for each line item.

4.5: Unit price

One of these exists for each line item.

4.6: Amount

This is not calculated - it is transmitted

5: Summary information

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

5.1: Total amount

Two data fields populate this one form field: the currency and the total amount.

Office-oriented formatting specification for UBL Order instances
G. Ken Holman
Copyright © 2003 OASIS
$Date: 2003/02/10 21:27:44 $(UTC)