UBL Mapping Committee

1. UBL Mapping Committee Plenary Report October 29th 2001

2. Terms of Reference • Review of xCBL 3.0 with respect to the Core Components initiative. • Produce a mapping of every xCBL construct into a corresponding CC construct and vice versa. • Develop a set of recommendations regarding the development of the UBL core library.

3. Participants • Jon Bosak (jon.bosak@sun.com • Brian Finale (bfinale@ups.com) • Lisa Seaburg (lisa.seaburg@commerceone.com) (impending Editor) • Arofan Gregory (arofan.gregory@commerceone.com) • Sue Probert (sue.probert@commerceone.com) • Gunther Stuhec (gunther.stuhec@sap.com) • Andy Cardy (acardy@ups.com) • Tim Thomasma (tthomasm@ford.com) • Tim McGrath (tmcgrath@portcomm.com.au) (Chair) • Debra Cimbala (debra.cimbala@remington.com) • Derek Coleman (RosettaNet)

4. Schedule • Team announced September 18th • Team List started September 28th • Draft discussion paper circulated October 5thth • Teleconferences on October 16th and October 23rd

5. Team Library • Mapping Strategy Recommendation Report • Draft Core Component Types to xCBL Datatypes Mapping Table • OAG Core Components Design Approach presentation (courtesy Tim Thomasma) • SAP Global Types and Entities proposal (courtesy Gunther Stuhec) These documents, together with correspondence within the team are available from the UBL Mapping Discussion List Archive at: http://lists.commerce.net/archives/bl-mapping logon: sandboxpassword: toys

6. Core Components and xCBL The relationship between the concepts of Core Components and xCBL are:  ·        Core Component (semantic model) + Context = Business Information Entity (semantic model). ·        Business Information Entities (semantic models, refined) + specific syntax binding = specific business vocabulary in XML (e.g. xCBL 3.0). - what will the CC library look like?

7. CONTEXT Business Business Information Entity Basic Core Component Aggregate Business Information Entity Aggregate Core Component Message/Document Core Component Library Core Core Component Type

8. Purchasing Core Business amount xCBL = UnitPrice pricing information for a basic unit of an item unit charge price.amount xCBL = OrderDetail common details for an ordered item item details xCBL = Order purchase order Core Component Library Example

9. Proposed Methodology – Step A • Map every simple and any obvious higher-level constructs of the current CC library to xCBL. Expect 20-50% alignment. • Identify the existence of "context-specific" structures ear-marked for the next step of the methodology.  • Identify constructs in xCBL based on assumptions about their use (e.g., assumed context drivers like Business Process and Industry). These mappings may be deferred until Phase II of UBL.

10. 000146 unit charge price. amount amount. type n/a The charge/price amount per unit. For example, for a charge of $5/day for 10 days, the charge unit amount is $5. Core Component Library definition Dictionary Entry Name xCBL 3.0 element UID Type Aggregate Definition Remarks • UnitPrice (Element) (Namespace: XCBL30) • Content: UnitPriceValue (Type: Decimal21_6) ,  Currency? ,  UnitOfMeasurement? • Description: TheUnitPrice element container element that holds the pricing information for a basic unit of an item. • UnitPriceValue  contains the value of the unit price. • Currency  contains the currency that UnitPriceValue is expressed in. • UnitOfMeasurement  contains the unit of measurement that the unit price is based on. Step A - UnitPrice example

11. Proposed Methodology – Step B Reverse-engineer the process, to: • Look for "in-context" matches between mapped items found in step A and establish the Business Information Entity and contexts involved. • Document syntax-binding rules to help in deciphering the rest of the Core Component library.

12. Step B - UnitPrice example UnitPrice appears in xCBL Order within a construct called BuyerExpectedUnitPrice… BuyerExpectedUnitPrice=> the pricing information for a basic unit of an item= context drivers, Business Process = “Purchasing”, Action= ‘Order Item”, Role = “Buyer” + the Core Component, unit charge price.amount

13. Core Business unit charge price.amount xCBL = BuyerExpectedUnitPrice Step B - BuyerExpectedUnitPrice Context Drivers are: Business Process = Purchasing Action = Order Item Role = Buyer pricing information for a basic unit of an item

14. Proposed Methodology – Step C Identify the xCBL structures that aren't yet mapped, and: • Determine constructs that can usefully be assembled from lower-level core components that already exist. Example: Are there any more amount.type components used in other xCBL structures, but in a different context?

15. Proposed Methodology – Step C • Identify structures that may be absent from the CC library - missing items submitted as candidate core components. Example: xCBL UnitPrice also contains, UnitOfMeasurement, the unit of measurement that the unit price is based on.

16. Proposed Methodology – Step C • Identify inconsistencies in the xCBL library –submitted for modification. • Example: The Core Component, charge.pricewouldalso relate to the xCBL element, ProductPrice, butProductPriceuses different xCBL pricing elements, creating duplicate xCBL definitions (e.g. UOMrather thanUnitOfMeasurement).

17. Proposed Methodology – Step D • Populate a data structure that contains xCBL elements, sets of context drivers and their values, and the Core Component(s) involved.

18. XCBL construct Mapped xCBL element Context 1 name/value Context 2 name/value Core Component BuyerExpectedUnitPrice UnitPrice ·UnitPriceValue ·Currency ·UnitOfMeasurement Business Process = Purchasing Role = Buyer unit charge price.amount (000146) Price amount.type(000105) ·    amount. content (000106) ·amount currency. identification. code (000107) BuyerExpectedUnitPrice Mapping

19. Work Items for this week • Step A applied to current 150 core components. • Steps B, C and D should be initially prototyped using a constrained set of xCBL structures (for example, the xCBL construct, ItemDetail).