UBL Context Methodology Subcommittee

Use Cases

January 25, 2002

Introduction

As part of its work on developing a methodology for modification of document formats based on context, the UBL Context Methodology Subcommittee has compiled a preliminary set of use cases for the application of context. Special acknowledge is due to the members of the UBL Library Content subcommittee, whose input was invaluable in putting together this list.

This list is presented in raw form. Some of these examples may not be real use cases, and in other cases it is unclear how to handle a specific use case (e.g. what context driver or value to assign). The list will be extended and refined as the use cases are discussed, including adding new comments and examples to each valid use case and deleting non-use cases.

The applicability of the context methodology to real-world problems will benefit greatly from additional use cases, especially for context drivers not covered by the current list. Parties who have comments on the existing use cases or who are interested in submitting additional use cases should contact the UBL Context Methdology Subcommittee chair.

List of Use Cases

1.
Description: Cellphones in Switzerland must be sent to personal address.
Context Driver: Product Classification
Value: Cellphone

2.
Description: Currency must be included in price for cross border transactions.
Context Driver: Geopolitical
Value: Country of buyer and seller differ

3.
Description: Note of fiscal type is required in invoice header in Brazil
Context Driver: Geopolitical
Value: Brazil

3.
Description: Some rules are applied only to European interactions but not to interactions inside Europe that are specific to certain countries.
Context Driver: Geopolitical
Value: European (but not individual European countries)

4.
Description: In Australia every invoice has to contain an Australian business number of invoicing party
Context Driver: Geopolitical
Value: Australia

5.
Description: In automotive, the VIN number is part of product description. Some companies in manufacturing add GPS info to delivery information.
Context Driver: Industry Classification
Value: Automotive

6.
Description: For airlines, there is a carrier code, fare basis, flight number, originating city, destination city, number of stops, stopovers, service class, reservation number.
Context Driver: Industry Classification
Value: Air Travel

7.
Description: For lodging, there is a check-in date and check-out date, reservation number. For car rental there is check-out date, check-in date, number of miles driven, vehicle class, insurance, security deposit, vehicle registration number.
Context Driver: Industry Classification
Value: Lodging, Car Rental

8.
Description: Payment reference number required in invoice header in Scandinavia.
Context Driver: Geopolitical
Value: Scandinavia or individual Scandinavian countries

9.
Description: Tax exemption depends on project because some work is done for a public body and some work is done for a private company, so the tax information might not be required.
Context Driver: Official Constraints
Value:

10.
Description: The contents of the bill of lading or way bill depends on mode of transport.
Context Driver:
Value:

11.
Description: US government requires a government bill of lading in addition to the normal bill of lading.
Context Driver: Official Constraints
Value: US Government

12.
Description: When an order request becomes an order, you must put in a buyer request number (optional becomes required).
Context Driver: Business Process
Value: Ordering

13.
Description: Consolidating shipper consolidating on behalf of several forwarders, who are also shipping on behalf of several consonors, the info that is provided to the guy up the hierarchy has to be filtered from the info provided down the hierarchy. E.g.: cost of transport is provided to the supplier but not to the customer.
Context Driver:
Value:

14.
Description: When publishing catalog content, depending on whether you are the originator or the republisher, if you are a republisher, you need to include the manufacturer's part number as well as your own part number.
Context Driver: Business Process Role
Value: Originator or Republisher

15.
Description: In Australia, customs make a distinction at a line item level: when the item is composed of products from other countries, each item must be included in a separate line item (e.g. 25 bales of cotton, some from India, some from Bangladesh, you would need 2 line items).
Context Driver: Geopolitical
Value: Australia

16.
Description: In the Czech Republic, tax summary must be included with 0, 5 and 22 tax rates and amounts.
Context Driver: Geopolitical
Value: Czech Republic

17.
Description: For tax-reporting purposes you must report tax rate in EU.
Context Driver: Geopolitical
Value: Europe or an individual European country

18.
Description: In Singapore, the government generates all PO numbers (maybe for imported goods only).
Context Driver: Geopolitical
Value: Singapore

19.
Description: Certain items in PO line items (credit card name and address for UK and a number of EU countries) is private, has to be masked out when sent to a third party -- NEED FOR SOMETHING THAT'S THERE BUT MASKED
Context Driver: Geopolitical
Value: UK or some other EU countries

20.
Description: UK and ex-dominion countries, account name has superiority over number, in other countries the reverse is true (deciding which field is optional).
Context Driver: Geopolitical
Value: UK and ex-dominion countries

21.
Description: Host of examples around certifications (e.g. Bordeaux wine is actually Bordeaux), requirements vary by country.
Context Driver: Geopolitical
Value:

22.
Description: When shipping goods to countries that America doesn't like (some acronym), certificate of origin is required (several cases, like to Arabia from Israel, vice versa, etc.).
Context Driver: Geopolitical
Value:

23.
Description: Transport of hazard goods required additional fields: chemical constitution in addition to product name, contact information (many others) in line item at different points in the document.
Context Driver: Product Classification
Value:

24.
Description: Same for storage (but different set of fields), so relevant for inventory.
Context Driver: Product Classification
Value:

25.
Description: Some might apply only if its shipped at sea.
Context Driver:
Value: