The Universal Business Language Uygar Donduran Uygar Donduran Alptekin Uzel

The promise of XML for e-business Plug and play electronic commerce Plug and play electronic commerce Spontaneous trade Spontaneous trade No custom programming No custom programming Ubiquity on the Internet Ubiquity on the Internet Complete platform independence Complete platform independence

WHY UBL ? XML is just a metalanguage XML is just a metalanguage Tag soup doesn’t give you interoperabilityTag soup doesn’t give you interoperability Seamless communication requires shared meaningSeamless communication requires shared meaning Shared meaning requires semantic standardization across whole industriesShared meaning requires semantic standardization across whole industries This is where UBL comes inThis is where UBL comes in

The Universal Business Language An XML-based business language standard-in-progress An XML-based business language standard-in-progress Applicable across all industry sectors and domains of electronic trade Applicable across all industry sectors and domains of electronic trade Actually modular, reusable, and extensible Actually modular, reusable, and extensible Non-proprietary and committed to freedom from royalties Non-proprietary and committed to freedom from royalties Intended to become a legal standard for international trade Intended to become a legal standard for international trade

ADVANTAGES OF UBL Lower cost of integration, both among and within enterprisesLower cost of integration, both among and within enterprises Lower cost of commercial softwareLower cost of commercial software Easier learning curveEasier learning curve Lower cost of entryLower cost of entry Quicker adoption by small and medium- size enterprises (SMEs)Quicker adoption by small and medium- size enterprises (SMEs) Standardized trainingStandardized training Universally available pool of skilled workersUniversally available pool of skilled workers

UBL PROVIDES THE FOLLOWING A library of XML schemas for reusable data components, such as “address”, “item”, and “payment”. Each such component is called Business Information Entity (BIE). A library of XML schemas for reusable data components, such as “address”, “item”, and “payment”. Each such component is called Business Information Entity (BIE). A small set of XML schemas that are composed from the BIEs are used. A small set of XML schemas that are composed from the BIEs are used. Guidelines for the extension of UBL in specific trading relationships. Guidelines for the extension of UBL in specific trading relationships.

UBL COMPONENT FOR “TAX”

Where UBL can fit into existing XML B2B Chemical Company C C’s industry partners CIDX Hospital B B’s industry partners HL7 Electronics Company A A’s industry partners RosettaNet

UBL’s relationship with ebXML UBL is not actually an “ebXML deliverable” UBL is not actually an “ebXML deliverable” UBL provides no particular messaging framework, but is built to support ebXML UBL provides no particular messaging framework, but is built to support ebXML But the combination will enable the “B2B web” But the combination will enable the “B2B web” HTTP + HTML = web publishingHTTP + HTML = web publishing ebXML + UBL = web commerceebXML + UBL = web commerce

Basic UBL Documents Order Order Response (simple) Order Response (complex) Order Change Despatch Advice (shipping notice) Receipt Advice Invoice

Order-to-Invoice Business Process

Some UBL participants APACS APACS Boeing Boeing Commerce One Commerce One France Telecom France Telecom General Electric General Electric HP HP Intuit Intuit KPMG KPMG LMI LMI Northrup Grumman Northrup Grumman OracleSAPSeeBeyond Sterling Commerce Sun Microsystems UK Cabinet Office United Parcel Service U.S. GSA U.S. Navy Visa International

Thanks!