Slide 1 Towards a Universal Business Language: Developing UBL as an international open standard for the conduct of XML-based electronic business Tim McGrath October

Slide 2 The OASIS Universal Business Language provides XML-based document models for e- commerce applications such as service oriented architectures and web services. As such it is an open standard for what is often the missing link for these services - the structures and semantics of the payload itself. This presentation will introduce the big ideas of UBL and discuss the successes and failures in achieving its goals.

Slide 3 Tim’s house Personal Introduction London

Slide 4 Tim’s house Crocodile hunter Everyone else

Slide 5 The Universal Business Language n International, royalty-free library of electronic business documents patterns. n Designed in an open and accountable vendor-neutral OASIS Technical Committee. n Fills the “payload” slot in B2B web services frameworks n Both human-readable and machine-readable n Designed for compatibility with existing EDI systems, existing legal frameworks, and existing patterns of trade n Intended for normative status under international law

Slide 6 UBL is a business vocabulary for XML HTTP + HTML = Web Publishing = Web Commerce ebXML/WS + UBL

Slide 7 UBL: the “Fifth Generation” B2B language n UBL represents over six years of continuous development in the creation of a standard XML business syntax. n G1 (1Q 1998): CBL 1.0 (Veo/NIST) n G2 (2Q 1999): CBL 2.0 (Commerce One) l plus over 20 years of EDI standards development n G3 (4Q 2000): xCBL 3.0 (Commerce One and SAP) n G4 (1Q 2003): UBL 0.7 (OASIS) n G5 (4Q 2004): UBL 1.0 (OASIS)

Slide 8 The Big Ideas of UBL “Words cannot convey the depth of language, and language cannot convey the depth of meaning.” Confucius ( BCE)

Slide 9 n A basic requirement for two businesses to conduct business is that their business systems interoperate. l The meaning of the information exchanged is understood as intended. n This has always been true, regardless of the technology used. n Interoperability requires: l that parties can exchange information and use the information they exchange. l that the information being exchanged is conceptually equivalent. n Easy to express but hard to achieve. l Variations in strategies, location, language, legacy applications, business processes, and terminology. l Different “contexts of use” Requirements for Document Exchange

Slide 10 Problems with Document Exchange n The names of components are only a small part of their meaning: l XML is not self-describing. l modelers will often choose different names for the same component. n Different document samples can lead to incompatible models. n All model expressions have technological limitations. l XML schemas cannot do everything. n So how do we solve this challenge?

Slide 11 Encouraging the use of Patterns n Patterns are models that are sufficiently general, adaptable, and worthy of imitation that we can use them over and over again. n Document exchanges for businesses follow common patterns. n Using patterns ensures applications and services are robust but adaptable when technology or business conditions change (as they inevitably will).

Slide 12 Sidenote on Standards n Standards are common patterns that have sanction and/or traction. n Sanction l de jure (ISO/UN/IEC, OASIS) n Traction l de facto (widely used) n History tells us traction is more important than sanction (HTML, TCP/IP, MS-Word, etc.. ) n Sanction is a means to achieve traction – not a goal in itself!

Slide 13 Interoperability requires all members of a trading community to understand the documents. This is facilitated when their syntax and semantics conform to common patterns. XML has become the preferred syntax for representing information in documents. Now we need to define common patterns for the semantics of business documents using XML syntax. - a “universal” business language Patterns Promote Interoperability

Slide 14 Making it real with UBL “ Technology neutral semantic alignment is unarguably a good thing, but only standardization on a single syntax will yield direct advantages.” Jon Bosak Chair, OASIS UBL TC

Slide 15 Example of a UBL Document <cbc:LineExtensionTotalAmount amountCurrencyCodeListVersionID="0.3" amountCurrencyID="USD"> Bills Microdevices Spring St 413 Elgin IL George Tirebiter

Slide 16 A UBL Implementation

Slide 17 UBL 1.0 Released May 1 st 2004 Basic Procurement Business Process Model Order to Invoice XML Schemas (W3C XSD) Order to Invoice Documents Re-usable Common Component Library XML (XSD) Naming and Design Rules Guidelines for schema customization. Pattern library of conceptual models. Forms Presentations and sample documents Download at :

Slide 18 Recent UBL Developments n UBL International Data Dictionary: l 600 elements translated into Chinese (Simplified and Traditional), Japanese, Korean, and Spanish. n UBL Naming and Design Rules (NDR) l adopted by chemical industry (CIDX), petroleum (PIDX), agriculture (RAPID), real estate (OSCRE/PISCES), U.S. Department of the Navy (DON), U.S. Taxation (IRS). n UBL Invoice used by the Danish Govt. l February to April 2005, more than one million invoices exchanged. l Estimated savings 94 million Euro annually. n UBL Invoice used by the Swedish Govt. l Announced October 2005 n Small Business Subset l Simple implementation guide for SMEs.

Slide 19 Work Plan for UBL 2.0 n Extended library. l Extended Procurement Process (Europe). l Transportation Process Documents (Asia). l Electronic Catalogue process (Europe). n Improved library. l Improve modelling l Clearer architecture. n Technology improvements l All types are global l Guidelines for validation of codes n Aligning with ISO and UN/CEFACT projects. l Core Component Type library. l UN/TDED. n Release Sept

Slide 20 Failures n Education and Support l Challenged by success n Documentation n Communication n Convergence l e.g. RosettaNet, OAG, UN/CEFACT l Liaison not equal to coordination n Customization approach l Too constrained l What is conformance and compliance? n We’re still here l Aren’t we there yet?

Slide 21 Successes n UBL is real l The first set of XML documents based on ebXML Core Components (ISO ) l A library of reusable data components n Stimulation for others l Libraries of ebXML Core Components l XML Naming and Design Rules n We’re still here! l 138 members (18 voting) l Project managing standards development …(and there’s more!)

Slide 22 Successes n Internationalization l Asia, Latin America, Scandanavia l Engagement and adoption n Adoption l Organic (viral) growth l Europe and Asia l North America (NDRs)

Slide 23 English514,000,000 Spanish425,000,000 Japanese120,000,000 Korean 60,000,000 Chinese (Mandarin) 1,075,000,000 The Meaning of Internationalization

Slide 24 The Value of Internationalization

Slide 25 The Value of Adoption

Slide 26 UBL Standard Needs Wider Use to Succeed 15 November 2004 Recommendations * Governments and other organizations should evaluate adopting UBL, but cannot anticipate widespread usage soon. UBL must gain broad adoption by 2008 if it is to have a significant impact. * A vocabulary-based approach is invaluable for e-commerce and can save enormous effort in XML data modeling. Use the extent of UBL's adoption by specific industries to measure whether it is living up to its promise. Analytical Sources: Rita Knox, Charles Abrams and Frank Kenney, Gartner Research The Next Challenge

Slide 27 Summary n The Universal Business Language is an international, royalty-free library of electronic business documents patterns. n UBL is addressing the challenge of supporting interoperable business services. n We are learning from our failures. n We are encouraged by our successes. n We are preparing for the challenge ahead.

Slide 28 Thank You … available from MIT Press