Implementing UBL
Mark Crawford UBL Vice Chair XML 2003 9 December 2003 Why Are We Talking About UBL • UBL fulfils the promise of XML for business by defining a standard cross-industry vocabulary • UBL is the ebXML missing link • UBL plus ebXML enables the next generation of eBusiness exchanges – Cheaper, easier, Internet-ready – Extends benefits of EDI to small businesses – Fits existing legal and trade concepts – Allows re-use of data • UBL can provide the XML payload for a wide variety of other web-based business frameworks Overview 1 What and Why of UBL 2 The Design of UBL ebXML Core Components Naming and Design Rules Document Engineering Customizing UBL 3 The Content of UBL 1.0 What is Normative What is non-Normative Availability
4 Making UBL Happen
5 UBL Phase 2 6 Summary The promise of XML for e-business • Plug ‘n’ play electronic commerce – Spontaneous trade – No custom programming • Ubiquity on the Internet – Dirt-cheap tools – Complete platform independence – Enable true global market availability • Enable universal interoperability – Abandon existing EDI systems – Handle both "publication" document types and "transactional" documents Goals for Successful eBusiness Services
• Web-enable existing fax- and paper-based business practices • Allow businesses to upgrade at their own pace • Preserve the existing investment in electronic business exchanges • Integrate small and medium-size businesses into existing electronic data exchange-based supply chains The standardization of XML business documents is the easiest way to accomplish these goals. XML For Interoperability??? • anyML • anyML
Diff erenc infor es in matio nal co ntent Diff eren tags ces & m in ean ings
D iff ere nc p es os in itio ns
Different information elements Can’t We Just Do It?
OpenTag Markup W3C Specifications Documentation Metadata - PICS Document Definition Markup Language (DDML) T ext Encoding Initiative (T EI) MIX - Mediation of Information Using XML WEBDAV (IETF 'Extensions for Distributed Authoring and Versioning on the Web') Channel Definition Format, CDF (Based on XML) CDIF XML-Based Transfer Format DAV Searching and Locating (DASL) RDF Rich Site Summary (RSS) Synchronized Multimedia Integration Language (SMIL) Graphic Communications Association - GCA 'Paper' DT D Open Content Syndication (OCS) Precision Graphics Markup Language (PGML) DocBook XML DT D W3C Document Object Model (DOM), Level 1 Specification Vector Markup Language (VML) Tutorial Markup Language (T ML) Web Collections using XML WebBroker: Distributed Object Communication on the Web International Development Markup Language (IDML) Meta Content Framework Using XML (MCF) Web Interface Definition Language (WIDL) Call Processing Language (CPL) XML-Data XML/EDI - Electronic Data Interchange Call Policy Markup Language (CPML) Namespaces in XML XML/EDI Repository Working Group VoiceXML Forum (Voice Extensible Markup Language Forum) Resource Description Framework (RDF) European XML/EDI Pilot Project VoxML Markup Language Australia New Zealand Land Information Council (ANZLIC) - Metadata EEMA EDI/EC Work Group - XML/EDI Telephony Markup Language (T ML) Alexandria Digital Library Project ANSI ASC X12/XML and DISA SABLE: A Standard for T ext-to-Speech Synthesis Markup AT LA Serials Project (AT LAS) Information and Content Exchange (ICE) Java Speech Markup Language (JSML) XML Metadata Interchange Format (XMI)-Object Management Group (OMG) CommerceNet Industry Initiative SpeechML OMG Common Warehouse Metadata Interchange (CWMI) Specification eCo Interoperability Framework Specification TalkML Object Management Group XML/Value RFP BizT alk Framework XML and VRML (Virtual Reality Modeling Language) - X3D MDC Open Information Model (OIM) eCo Framework Project and Working Group XML for Workflow Management [NIST ] Educom Instructional Management Systems Project (IMS) Commerce XML (cXML) SWAP - Simple Workflow Access Protocol Metadata Specification RosettaNet XML-Based Process Management Standard: Wf-XML Structured Graph Format (SGF) Open Catalog Protocol (OCP) Theological Markup Language (T hML) Legal XML Working Group and UELP vCard Electronic Business Card LitML: A Liturgical Markup Language XML Court Interface (XCI) iCalendar XML DT D XML-F ('XML for FAX') Georgia State University Electronic Court Filing Project XML Encoded Form Values Extensible Forms Description Language (XFDL) Web Standards Project (WSP) Capability Card: An Attribute Certificate in XML XML Forms Architecture (XFA) HT ML T hreading - Use of HT ML in Email T elecommunications Interchange Markup (TIM, TCIF/IPI) Broadcast Hypertext Markup Language (BHT ML) Open Software Description Format (OSD) aecXML Working Group - Architecture, Engineering and Construction IEEE LTSC XML Ad Hoc Group XLF (Extensible Log Format) Initiative Product Data Markup Language (PDML) IEEE Standard DTD Apache XML Project Product Definition Exchange (PDX) Open Settlement Protocol (OSP) - ET SI/T IPHON WAP Wireless Markup Language Specification Electronic Component Information Exchange (ECIX) and Directory Services Markup Language (DSML) HT T P Distribution and Replication Protocol (DRP) Pinnacles Component Information Standard (PCIS) WDDX - Web Distributed Data Exchange Chemical Markup Language ECIX QuickData Specifications Business Rules Markup Language (BRML) Molecular Dynamics [Markup] Language (MoDL) ECIX Component Information Dictionary Standard (CIDS) Common Business Library (CBL) Bioinformatic Sequence Markup Language (BSML) ECIX Timing Diagram Markup Language (TDML) Open Applications Group - OAGIS BIOpolymer Markup Language (BIOML) Encoded Archival Description (EAD) Schema for Object-oriented XML (SOX) Virtual Hyperglossary (VHG) UML eXchange Format (UXF) XMLT P.Org - XML Transfer Protocol Weather Observation Definition Format (OMF) XML Data Binding Specification The XML Bookmark Exchange Language (XBEL) Open Financial Exchange (OFX/OFE) T ranslation Memory eXchange (T MX) Simple Object Definition Language (SODL) and XMOP Service Interactive Financial Exchange (IFX) P3P Syntax Specification Simple Object Access Protocol (SOAP) FinXML - 'T he Digital Language for Capital Markets' Scripting News in XML XML and Music Extensible Financial Reporting Markup Language (XFRML) InterX.org Initiative Clinical T rial Data Model Open T rading Protocol (OT P) NuDoc T echnology Human Resource Management Markup Language (HRMML) Financial Products Markup Language (FpML) Coins: Tightly Coupled JavaBeans and XML Elements HR-XML Consortium Mortgage Bankers Association of America XML Workgroup DMT F Common Information Model (CIM) XML-HR Initiative - Human Resources Digital Property Rights Language (DPRL) Universal Plug and Play Forum ECMData - Electronic Component Manufacturer Data Sheet Inventory Specification XML Digital Signature (Signed XML - IET F/W3C) Process Interchange Format XML (PIF-XML) Bean Markup Language (BML) Digital Receipt Infrastructure Initiative Ontology and Conceptual Knowledge Markup Languages The Koala Bean Markup Language (KBML) Digest Values for DOM (DOMHASH) XOL - XML-Based Ontology Exchange Language Jigsaw XML Format (JXML) Signed Document Markup Language (SDML) Procedural Markup Language (PML) Chinese XML Now! FIXML - A Markup Language for the FIX Application Message Layer QAML - T he Q&A Markup Language MOS-X (Media Object Server - XML) Bank Internet Payment System (BIPS) LACIT O Projet Archivage de données linguistiques FLBC (Formal Language for Business Communication) and KQML smartX ['SmartCard'] Markup Language (SML) sonores et textuelles [Linguistic Data Archiving Project] ISO 12083 XML DTDs Real Estate T ransaction Markup Language (RETML) Astronomical Markup Language Extensible User Interface Language (XUL) OpenMLS - Real Estate DT D Design Astronomical Instrument Markup Language (AIML) User Interface Markup Language (UIML) ACORD - XML for the Insurance Industry GedML: [GEDCOM] Genealogical Data in XML Process Specification Language (PSL) and XML Customer Profile Exchange (CPEX) Working Group Newspaper Association of America (NAA) - Standard for XML DTD for Phone Books Customer Support Consortium Classified Advertising Data 5.5 Using XML for RFCs XML for the Automotive Industry - SAE J2008 News Industry Text Format (NIT F) Schools Interoperability Framework (SIF) XML.ORG - T he XML Industry Portal XMLNews: XMLNews-Story and XMLNews-Meta Guideline XML (gXML) X-ACT - XML Active Content Technologies Council NewsML and IPT C2000 Extensible Protocol Electronic Business XML Initiative (ebXML) Notes Flat File Format (NFF) XML Belief Network File Format (Bayesian Networks) Portal Markup Language (PML) Java Help API Predictive Model Markup Language (PMML) EDGARspace Portal Cold Fusion Markup Language (CFML) The Data Documentation Initiative (DDI) DII Common Operating Environment (COE) XML Registry Document Content Description for XML (DCD) XML and CORBA Open eBook Initiative XSchema Mathematical Markup Language OpenMath Standard
The Role of a Hub Format Why UBL? • Leverages knowledge from existing EDI and XML B2B systems • Applies across all industry sectors and domains of electronic trade (80/20 rule) • Fully leverages XML • Provides the ebXML missing link: – XML Payload +ebXML CCTS +modelling methodology • Non-proprietary and committed to freedom from royalties • On track to become international standard for trade through ISO TC154 Overview
1 What and Why of UBL 2 The Design of UBL ebXML Core Components Naming and Design Rules Document Engineering Customizing UBL 3 The Content of UBL 1.0 What is Normative What is non-Normative Availability
4 Making UBL Happen
5 UBL Phase 2 6 Summary UBL and the ebWS stack
Message UBL Formatting Specs presentation
y UBL Context Methodology r Message UBL to i Context Methodology contextualization s o p e
R UBL Library
/ Standard } y messages tr Core Components s i g e
R Business ebXML CPPA agreements
XML Web b e ebXML BPSS Business Services processes ebMS Packaging/ transport } ebXML Core Components
•A set of the lowest common denominator that captures information about a real world (business) concept
•Core Components are neutral – in the notation for every kind of industry – in the syntax for every kind of business document standard or implementation ebXML Core Components
• Reusable pieces (objects) of contents that can be atomic or aggregate – Enables interoperability among different industry domains and areas – Are using common semantic units at any level consistent across context – Hold any related information together and avoiding fragmented semantic dispersal – Facilitate multilingual support • Accompanied by methodology for extensibility – Enable users to define meaningful business and process data – Ensure maximum interoperability The Core Components Specification Follows ISO 11179
Object class Address
Property 1: representation 1 Street: text Property 2: representation 2 Post code: text Property 3: representation 3 Town: text Property 4: representation 4 Country: identifier
ISO 11179 governs data dictionaries: defines the notions of object class, property, and representation term
• This is basic object-oriented “good stuff” The ebXML CCTS system
1 Without business Content semantics Component
Consists of 1-n Supplementary Component Consists of Core Component Type (CCT)
Specif ies restrictions on With known business semantics Data Type
Def ines set of v alues of
Basic Core Component
Association Core Component Prov ides a simple characteristic of and is aggregated in Prov ides a complex characteristic of and is aggregated in
Aggregate Core Component Applying Business Context Core Business C ore C omponent Type (CC T)
S pecifies rest rictions on
Further Data Type Data Type restricts
Def ines set Defines set of values of of values of
I s Basic C ore C omponent based Basic Business Information Entity on A
Associat ion g Association g
I s Business r
C ore e
based Informati on g C omponent on a
Entity t e d
i A s Property A s Property n A ggregated A ggregat ed in in
Qualifies the Aggregat e Busi ness Information Aggregate C ore C omponent Object Class Enti ty of
Assembly C omponent A ggregated in A dds extra information
Message A ssembly
Core Component Library Core Components vs. Business Information Entities
Core Component apply business context: Business Information (CC) business process Entity (BIE) product classification A building block for the industry classification A CC to which a business exchange of geopolitical region context has been applied semantically correct and official constraint meaningful information business process role supporting role system capabilitites • An address might be a generic CC • A U.S. address has (at least) the geopolitical region set as its business context, making it a BIE • UBL, by its nature, deals only in BIEs Overview
1 What and Why of UBL 2 The Design of UBL ebXML Core Components Naming and Design Rules Document Engineering Customizing UBL 3 The Content of UBL 1.0 What is Normative What is non-Normative Availability
4 Making UBL Happen
5 UBL Phase 2 6 Summary NDR Requirements
• Leverage XML technology, but keep it interoperable • Achieve semantic clarity through a binding to the Core Components model • Support contextualization (customization) and reuse • Selectively allow “outsourcing” to other standard schemas xsd:complexType
Core Component Type (CCT) As xsd:complexType Representation Term Specifies restrictions on
Data Type Further Data Type As (DT) restricts (DT) Representation Term
Defines a Defines a xsd:complexType xsd:element set set of values of of values of
Is Mapping Basic Core Component Basic Business Information xsd:element based (BCC) Entity (BBIE) on
Is CCTS to Association Core Component Association Business based (ASCC) Information Entity (ASBIE) on
Ass Ass XSD Property Property xsd:complexType xsd:element aggregated aggregated in in
Qualifies the Aggregate Core Component Aggregate Business Information Object Class (ACC) Entity (ABIE) of
Assembly Component Aggregated Aggregated in in
Adds extra information
Message Assembly
Core Component Library Some Major Design Rules
• The choice of normative schema language - XSD • Garden of Eden design approach – Named Types – Global Elements for all aggregate and leaf elements except: • Local Elements for Identifiers and Codes • Naming and construction of elements, attributes, and types • Modularity, namespaces, and versioning • Embedded schema documentation • Handling code lists (preliminary) A Taste Of The Naming Rules
• Dictionary entry names are fully qualified with object class names • But using these full names would result in hundreds of extra elements • We get reusability by allowing properties (elements) to “inherit” parent object classes (types), XPath-style – Delivery schedule IDs and order IDs could both be called
File W3C XML Schema Namespace 1 1 1 1
{In different namespace than ControlSchema}
ControlSchema SchemaModule
1 1
-included InternalSchemaModule ExternalSchemaModule 0..*
-imported 4..* Shaded area is {In same namespace The four required a "schema set". as ControlSchema} namespaces are (represented by their prefixes): dt, rt, cbc, cac. UBL – Building the Control Schema
ExternalSchemaModule
CBC CAC DT RT CTRT
1 -imports 0..* 1 1 1
-imports CodeList 0..* 1 CBC: Common Basic Components CAC: Common Aggregate Components CBC, CAC, DT, RT, and CodeList DT: DataTypes schema modules are imported by RT: RepresentationTerms (not CodeTypes) ControlSchema. CTRT is not. CTRT: CodeTypeRepresentationTerms urn:oasis:names:specification:ubl:schema:order:1:0
...:invoice:1:0
Order
Invoice
Reusing
...:commonbasiccomponents:1:0 Components Legend Common Basic Control Schema Across Components Internal Schema Module ...:commonaggregatecomponents:1:0
External Schema Module Control Common Aggregate import Components include
Schemas ...:commonaggregatecomponents:1:0 x:y:z namespace
Data Types
...:representationterms:1:0
Represent- ation Terms Code Lists
• UBL will seek to import external datatype definitions in conventional XSD form – Validation – Clarity • We are developing a schema for promotion as an international standard • We hope to promote a global code list marketplace Overview
1 What and Why of UBL 2 The Design of UBL ebXML Core Components Naming and Design Rules Document Engineering Customizing UBL 3 The Content of UBL 1.0 What is Normative What is non-Normative Availability
4 Making UBL Happen
5 UBL Phase 2 6 Summary Document Engineering
• A new discipline for designing electronic document structures • Applicable to Internet information exchange mechanisms to request or return the results of business processes (aka Web Services). • Consolidates document and data-centric perspectives • Provides analysis and design methods that yield formal models • UBL has developed these models for a common business process – procurement. Business Operations View UML and spreadsheets Conceptual models showing all possible associations
Functional
A Database
n XML Schema Schemas Service view a
l Libraries Schemas y Business s EDI Message i Document s Definitions Models The Real
11. Modeling E-business Documents and Processes
Copyright © 2002 Robert J. Glushko SIMS 290-4, 26 February 2002 1. Plan for Today's Class •What is a 'model'? •What is a 'metamodel'? •Why do modeling? World •Disciplines for modeling •Just enough UML •XML as a modeling notation
Functional
A Database
n XML Schema Schemas Service view a
l Libraries Schemas y Business s EDI Message Documents structures are i Document s Definitions Models assembled from 'network’ of components into document 11. Modeling E-business Documents and Processes
Copyright © 2002 Robert J. Glushko SIMS 290-4, 26 February 2002 1. Plan for Today's Class •What is a 'model'? •What is a 'metamodel'? models •Why do modeling? •Disciplines for modeling •Just enough UML •XML as a modeling notation
UML and spreadsheets I m
Design pl e m e n t
UBL script does a t i thFius naucttomionaatilc ally on
A Database
n XML Schema Schemas Service view a
l Libraries Schemas y Business s EDI Message i Document s Definitions Models The Real
11. Modeling E-business Documents and Processes
Copyright © 2002 Robert J. Glushko SIMS 290-4, 26 February 2002 1. Plan for Today's Class •What is a 'model'? •What is a 'metamodel'? •Why do modeling? World •Disciplines for modeling •Just enough UML Schema componentry •XML as a modeling notation
• Remove redundant and nearly • Remove the object class redundant words in the property name on properties, as the field (as in *. Identification. XML parent labels it Identifier) sufficiently • Remove periods, spaces, and • These are applied underscores automatically by the • When the representation term is schema generator “Text”, remove it Item. Details ItemType Item. Description. Text Description Item. Pack. Quantity PackQuantity Item. Buyers_ Item Identification Item. Sellers_ Item Identification BuyersItemIdentification SellersItemIdentification
A UBL Schema fragment Business Operations view
UML and spreadsheets I m
Design pl e m e n t a t i Functional on
A Database
n XML Schema Schemas Service view a
l Libraries FinaSlc hpermeassentation is application y Business s EDI Message i Document dependent (e.g. Stylesheet) s Definitions Models
The Real 11. Modeling E-business Documents and Processes Copyright © 2002 Robert J. Glushko SIMS 290-4, 26 February 2002 1. Plan for Today's Class 11. Modeling E-business Documents and Processes •What is a 'model'? Copyright © 2002 Robert J. Glushko •What is a 'metamodel'? SIMS 290-4, 26 February 2002 1. Plan for Today's Class •Why do modeling? •What is a 'model'? •Disciplines for modeling •What is a 'metamodel'? •Just enough UML •Why do modeling? World •XML as a modeling notation •Disciplines for modeling •Just enough UML •XML as a modeling notation
1 What and Why of UBL 2 The Design of UBL ebXML Core Components Naming and Design Rules Document Engineering Customizing UBL 3 The Content of UBL 1.0 What is Normative What is non-Normative Availability
4 Making UBL Happen
5 UBL Phase 2 6 Summary Customizing Means
• Applying a different context to the use of the schemas, e.g. – Adding Japanese accounting requirements to the UBL 'Payment' structure when used in Invoice. – Re-using UBL components
• Using UBL with other vocabularies, e.g. – RosettaNet, OAG – EDIFACT, ANSI X12 – Proprietary formats Levels of Interoperability • Schema compatibility • My schema for UBL Invoice still parses the Japanese one • UBL Context Methodology • Syntax compatibility • I need your schema but my application understands the structure used • We share the same NDRs for XML • Semantic compatibility • Whatever you call the component I can understand what it means and can map it to my application • We share ebXML “syntax-independent” core components Business Operations view
UML and spreadsheets I m
Design pl e m e n t a
Syntax Level t i Functional on
A Database
n XML Sch eSma eSmchemaasntiSce Lrveicvee vli ew a
l Libraries Schemas y Business s EDI Message i Document s Definitions Models The Real
11. Modeling E-business Documents and Processes
Copyright © 2002 Robert J. Glushko SIMS 290-4, 26 February 2002 1. Plan for Today's Class •What is a 'model'? •What is a 'metamodel'? •Why do modeling? World •Disciplines for modeling Schema Level •Just enough UML •XML as a modeling notation
1 What and Why of UBL 2 The Design of UBL ebXML Core Components Naming and Design Rules Document Engineering Customizing UBL 3 The Content of UBL 1.0 What is Normative What is non-Normative Availability
4 Making UBL Happen
5 UBL Phase 2 6 Summary Normative Schemas • W3C XML Schema (XSD) modules – Schema of re-usable Types • Party, Address, Item, Tax, etc – Schemas for ebXML Core Component Types • Core Component Types, Representation Terms and Data Types – Schemas for documents: • Order, Order Change, Order Cancellation, Order Response(simple), Order Response(complex), Despatch Advice, Receipt Advice, Invoice – Schemas for Code Lists(enumerations) • For each UBL code type • Currently all “placebo”s Release Schema Structure
The control document schema in... xsd/maindoc/UBL-Order-1.0-beta.xsd Refers to the common UBL Library in... xsd/common/UBL-Reusable-1.0-beta.xsd That uses data types defined in... xsd/common/UBL-RepresentationTerms-1.0-beta.xsd That extends data types defined in... xsd/common/UBL-CoreComponentTypes-1.0-beta.xsd Any of these may refer to a list of code values defined in... xsd/codelist/use/UBL-CodeList-DocumentStatusCode-Use-1.0-beta.xsd Normative Business Process • Tied to document types used in schemas – Basic Order-to-Invoice – Defines business rules/constraints for document use – 80/20 rule applies Non-Normative Data Models • Conceptual Model – UML (design format) – Party, Address, Item, Tax, etc... – "Candidate” ebXML Core Components • Document Models – Spreadsheets (maintenance format) – Assembled from conceptual model components (Re- usable Types) – Order, Order Change, Order Cancellation, Order Response(simple), Order Response(complex), Despatch Advice, Receipt Advice, Invoice – Apply UBL naming rules by formulae Other Non-Normative Deliverables
• Checklist of UBL naming and design rules • Tool(s) for generating the schemas • Additional modelling views: – Implementation view UML (actual schema structure) – ASN.1 schema – RELAX NG schema(?) • Forms presentation mappings for developing style sheets, etc. • Sample XML instances and outputs • Usage documentation Package Availability • HTML, PDF and OpenOffice document formats
Available at: http://www.oasis-open.org/committees/ubl/lcsc/UBLv1-beta Overview
1 What and Why of UBL 2 The Design of UBL ebXML Core Components Naming and Design Rules Document Engineering Customizing UBL 3 The Content of UBL 1.0 What is Normative What is non-Normative Availability
4 Making UBL Happen
5 UBL Phase 2 6 Summary UBL Status • November 2003 – UBL 1.0 beta (Committee Draft) for pilot implementation – Feedback essential to prove the specification • January 2004 – UBL NDR 1.0 Committee Draft • February 2004 – UBL 1.0 & UBL NDR 1.0 Committee Draft to OASIS for approval • March/April 2004 – UBL 1.0 & UBL NDR 1.0 become OASIS Technical Specification – UBL 1.0 and UBL NDR 1.0 Fast Tracked to ISO TC154 • UBL is at a watershed – 1.0 Library is complete(almost!) – Planning for UBL 2.0 starts now! – Customizing UBL for other contexts UBL Technical Subcommittees NDRSC CMSC CDSC Naming and Design Rules SC Context Methodology SC Context Drivers SC Develops guidelines for Develops a methodology Works on improvement normative-form schema and tools for applying and further development design, instance design, context. of the context drivers. and markup naming,
TTSC LCSC FPSC Tools Eavnadl uTaetcehsn ainqdu es SC Library Content SC Forms Presentation SC recommends the tools and Defines business Develops and documents techniques for documents and a library of formal technology- development, maintenance XML and ebXML CCTS agnostic Formatting and revision based building blocks Specifications
JPLSC CNLSC CLSC Japanese Localization SC Chinese Localization SC Code List SC Customization/ Customization/ Work with NDR/LC to Implementation of UBL in Implementation of UBL in finalize and institutionalize the Japanese market the Chinese market UBL Code List solution UBL Technical Subcommittees NDRSC CMSC CDSC Naming and Design Rules SC Context Methodology SC Context Drivers SC Develops guidelines for Develops a methodology Works on improvement normative-form schema and tools for applying and further development design, instance design, context. of the context drivers. and markup naming,
TTSC LCSC FPSC Tools Eavnadl uTaetcehsn ainqdu es SC Library Content SC Forms Presentation SC recommends the tools and Defines business Develops and documents techniques for documents and a library of formal technology- development, maintenance XML and ebXML CCTS agnostic Formatting and revision based building blocks Specifications
JPLSC CNLSC CLSC Japanese Localization SC Chinese Localization SC Liaison SC Customization/ Customization/ Work with NDR/LC to Implementation of UBL in Implementation of UBL in finalize and institutionalize the Japanese market the Chinese market UBL Code List solution UBL Technical Subcommittees
NDRSC CMSC CDSC Naming and Design Rules SC Context Methodology SC Context Drivers SC Develops guidelines for Develops a methodology Works on improvement normative-form schema and tools for applying and further development design, instance design, context. of the context drivers. and markup naming, Implementation SC
TTMSConitor UBL-Dev and cLoCoSCrdinate with other FPSC Tools Eavnadl uTtaeetcechshn ainqduic esa Sl CSC’s for rLeibsrparoy nCosnetent SC Forms Presentation SC recommends the tools and Defines business Develops and documents technCiquoelsl afotre issues didsoccuomveenrtse adn da an ldib rcaroyn ovf ey themfo rtmoa tl hteech nology- development, maintenance XML and ebXML CCTS agnostic Formatting and raepvipsiroon priate SC forb aascedti bounilding blocks Specifications
JPLSC CNLSC CLSC Japanese Localization SC Chinese Localization SC Liaison SC Customization/ Customization/ Work with NDR/LC to Implementation of UBL in Implementation of UBL in finalize and institutionalize the Japanese market the Chinese market UBL Code List solution UBL Administrative Subcommittees
ASC MSC LSC Administration SC Marketing SC Liaison SC Administrates and Does marketing and Organizes liaisons with coordinates the UBL promotion for the UBL other organizations. efforts effort Some UBL Participants APACS Northrup Grumman Boeing Oracle Commerce One PricewaterhouseCoopers Danish Bankers Association SAP France Telecom SeeBeyond General Electric Sterling Commerce Government of Hong Kong Sun Microsystems Government of Korea UCB Center for Document HP Engineering Intuit UK Cabinet Office KPMG United Parcel Service LMI U.S. GSA U.S. Navy Visa International The Value of J oining Forces
• As a non-profit cross-industry effort, UBL depends on expert domain input to “get it right” • We actively solicit industry and standards liaisons • Organizations appoint representatives to the UBL Liaison Subcommittee – If the organization is not an OASIS member, an individual representative joins at USD 250/year – Telcons are held frequently – Liaisons arrange for specification reviews Formal Liaisons (so far) • ACORD (insurance) • RosettaNet (information • ARTS (retail sales) technology) • ebXML Asia Committee • SWIFT (banking) (ebXML) • UIG (utilities) • e.centre (EAN UK) • VCA (optical supplies) • EIDX (electronics) • XBRL (accounting) • HL7 (healthcare) • ASC X12 COTG • Information Technology Standards Committee of • UN/CEFACT TBG Singapore • UN/CEFACT ATG • NACS (convenience stores) • OASIS eGov TC • Open Applications Group • OASIS CIQ TC Overview
1 What and Why of UBL 2 The Design of UBL ebXML Core Components Naming and Design Rules Document Engineering Customizing UBL 3 The Content of UBL 1.0 What is Normative What is non-Normative Availability
4 Making UBL Happen
5 UBL Phase 2 6 Summary Basic UBL Documents
• Procurement – Purchase Order, P.O. Response, P.O. Change • Materials management – Advance Ship Notice, Planning Schedule, Goods Receipt • Payment – Commercial Invoice, Remittance Advice • Transport/logistics – Consignment Status Request, Consignment Status Report, Bill of Lading • Catalogs – Price Catalog, Product Catalog • Statistical reports – Accounting Report Expand The Library
• Fill in basic list • Add new work areas – Tax – Customs – Government – Other Work the Customization Methodology
• Move forward with Context Methodology • Develop routines to automatically apply context and auto-generate UBL conformant contextualized schemas Overview
1 What and Why of UBL 2 The Design of UBL ebXML Core Components Naming and Design Rules Document Engineering Customizing UBL 3 The Content of UBL 1.0 What is Normative What is non-Normative Availability
4 Making UBL Happen
5 UBL Phase 2 6 Summary UBL Offers Important and Interesting Solutions • As a B2B standard: – It is user-driven, with deep experience and partnership resources to call on – It is committed to truly global trade and interoperability – Its process is open and transparent • As a Web Service interface: – It can be layered on existing standards – It is providing the 'missing link'; content • As an e-business vocabulary: – 80/20 plus customisation Where To Find More Information
• OASIS UBL TC – http://www.oasis-open.org – White papers, presentations, and specifications are available – All mailing list archives are open to public view • For ebXML: http://www.ebxml.org • For ebXML Core Components: