2. 2004 Adobe Systems Incorporated. All Rights Reserved. bcbc UN/CEFACT Core Components Semantic Interoperability of Data Elements and the Context Framework Duane Nickull dnickull@adobe.com dnickull@adobe.com

3. bcbc 2004 Adobe Systems Incorporated. All Rights Reserved.2 United Nations Centre for Trade Facilitation and Electronic Business (UN/CEFACT) “UN/CEFACT supports activities dedicated to improving the ability of business, trade and administrative organizations, from developed, developing and transitional economies, to exchange products and relevant services effectively.”

4. bcbc 2004 Adobe Systems Incorporated. All Rights Reserved.3 UN/CEFACT  Mission: Trade Facilitation and eBusiness. To improve the ability of business, trade and administrative organizations, from developed, developing and transitional economies, to exchange products and relevant services effectively - and so contribute to the growth of global commerce  Focus The worldwide facilitation of national AND international transactions, through the simplification and harmonization of procedures and information flows.

5. bcbc 2004 Adobe Systems Incorporated. All Rights Reserved.4 Why do we need it? Impact  Developing nations excluded from benefits of global trade.  The gap between the rich and poor continues to grow.  Social impact of trade in equality affects the entire population.  Economic discrimination hurts many, major social issues. We can change it! Action  Analyze, understand key elements of global business  Develop methods and processes including technologies.  Work with other standards development organizations (SDO’s)  Ensure we have one “FREE and OPEN” set of standards to use.  Encourage technology companies to behave responsibly.  Bridge the gap between paper and electronic commerce.  Educate and build capacity for fair global trade. What we must do! Problem  Cultural differences, trade regulations, sanctions.  Technology barriers to trade.  Need to balance global trade with global security.  Not all nations have basic infrastructures.  Models, technologies constantly changing. Where we are.

6. bcbc 2004 Adobe Systems Incorporated. All Rights Reserved.5 Agenda  What are Core Components  What problems do they solve  Who is working on Core Components  Core Component Methodology  What is the status  How can you use them today (scenario) Also…  Technical Slides (optional)

7. bcbc 2004 Adobe Systems Incorporated. All Rights Reserved.6  Core Components are building blocks of metadata.  Each Core Component captures and declares details about a real world business concept (example – “date”)  Designed to be re-used globally.  Design time artefacts. Could aid in building XML schemas, UNeDocs code lists etc.  May be specialized for use within a certain context (example – “date” becomes “OrderDate”) NOTE: “Core Component” is used herein to cover all CC terms including ACC, BCC, ABIE, BBIE What are Core Components

8. bcbc 2004 Adobe Systems Incorporated. All Rights Reserved.7 Core Component concepts BIE

9. bcbc 2004 Adobe Systems Incorporated. All Rights Reserved.8 Data Elements build Business Messages at Design Time Name AddressemailPhone #Company Phone # email Address NameParty Party ID Invoice PO #Line ItemCost CONTEXT DateOrder.Date Business Information Entities (BIE’s) Core Components (CC’s)

10. bcbc 2004 Adobe Systems Incorporated. All Rights Reserved.9 What items do we use to describe a CC Base Data  Unique definition  UUID (DCE 128 bit algorithm format)  Data Dictionary Name  Object Class Term  Property Term  Representation Term  Data Type Meta Data (from Registry)  Owner  Version  Status  Home Registry URI  Name  Associations  Classifications  Syntax Information

11. bcbc 2004 Adobe Systems Incorporated. All Rights Reserved.10 Agenda  What are Core Components  What problems do they solve  Who is working on Core Components  Core Component Methodology  What is the status  How can you use them today (scenario) Also…  Technical Slides (optional)

12. bcbc 2004 Adobe Systems Incorporated. All Rights Reserved.11 Too many data standards All have different data elements! HR- XML EHD xCat UBL Rosettanet OTAIATA cXML E- construct CAT XML SMDG PIDXGCIUNe Doc XAML Open trans GMLxCBL HL7 AcordCIDXxBRLBSMLagXMLVICSSWIFTTogaf Bolero

13. bcbc 2004 Adobe Systems Incorporated. All Rights Reserved.12 Problem: Inconsistent use of Data Elements  Nickull, Duane A.  Mr. Nickull  Duane Nickull  D. A. Nickull  Duane A. Nickull  Duane Allan Nickull  Nickull, Duane Allan  Mr. D. Nickull  Monsieur D.A. Nickull NAME OF PERSON

14. bcbc 2004 Adobe Systems Incorporated. All Rights Reserved.13 Solution: Data Dictionary “Incompatibility becomes incremental rather than wholesale, i.e. the detailed points of difference are noted, rather than a whole model being dismissed as incompatible.” Data Element: Name Type: string Data Element: Date Type: integer Mask: DDMMYY Data Element: Address Type: Aggregate Data Element: Telephone Type: string

15. bcbc 2004 Adobe Systems Incorporated. All Rights Reserved.14 UN/CEFACT Core Components vision UBL eGov XML SGML X12 XMLEtc. 1999 2002 2004 2007 Existing Standards Reconciliation Of Data Elements EDIFACT UN/CEFACT Core Component Library

16. bcbc 2004 Adobe Systems Incorporated. All Rights Reserved.15 Agenda  What are Core Components  What problems do they solve  Who is working on Core Components  Core Component Methodology  What is the status  How can you use them today (scenario) Also…  Technical Slides (optional)

17. bcbc 2004 Adobe Systems Incorporated. All Rights Reserved.16  Work started in ebXML – joint initiative between UN/CEFACT and OASIS in 1999.  After May 2001, work continued within UN/CEFACT.  UN/CEFACT TMG applied to ISO for ebXML Core Components TS v 2.01 to become fast tracked as ISO 15000 standard. Who is working on Core Components

18. bcbc 2004 Adobe Systems Incorporated. All Rights Reserved.17 Agenda  What are Core Components  What problems do they solve  Who is working on Core Components  Core Component Methodology  What is the status  How can you use them today (scenario) Also…  Technical Slides (optional)

19. bcbc 2004 Adobe Systems Incorporated. All Rights Reserved.18 Core Component Discovery Business Documents Country.Identifier Person.Family Name Core Component discovery process. Core Component Library Business Process are part of Context UNeDocs

20. bcbc 2004 Adobe Systems Incorporated. All Rights Reserved.19 Steps to identify Core Components

21. bcbc 2004 Adobe Systems Incorporated. All Rights Reserved.20 Using Core Components at Design Time Core Component Library New Business Process has 1.Identify Core components to use for each Business Message Business messages 2. Aggregate CC’s for each new Business Message. 3. Use context to guide refinement of CC’s into BIE’s. Express as final metadata for Business Messages.

22. bcbc 2004 Adobe Systems Incorporated. All Rights Reserved.21 Agenda  What are Core Components  What problems do they solve  Who is working on Core Components  Core Component Methodology  What is the status  How can you use them today (scenario) Also…  Technical Slides (optional)

23. bcbc 2004 Adobe Systems Incorporated. All Rights Reserved.22 CCTS Status  CCTS v 2.01 done and submitted to ISO for fast tracking.  UN/CEFACT ATG has CC naming and Design Rules out for review.  CCTS getting a few reference implementations and PoC’s (US, Canadian Government, Adobe, others…)

24. bcbc 2004 Adobe Systems Incorporated. All Rights Reserved.23 Agenda  What are Core Components  What problems do they solve  Who is working on Core Components  Core Component Methodology  What is the status  How can you use them today and tomorrow (scenario) Also…  Technical Slides (optional)

25. bcbc 2004 Adobe Systems Incorporated. All Rights Reserved.24 Using Core Components Today  All new transaction instances use several pieces of information. Picked from CC dictionary.  Business Information Entities or BIE’s can be serialized inline using Context Methodology Framework.  Government of Canada has placed 353 Data Elements in ebXML Registry.  Data model XML rendition of UN/CEFACT Core Components  Uses them for building transactions  Work entering phase IV

26. bcbc 2004 Adobe Systems Incorporated. All Rights Reserved.25 Example: Context Affects “Human Being” depending on “Role”. CORE COMPONENT (BEING) Police Officer knows he is a WITNESS FRENCH ENGLISH Police Investigator thinks He is a SUSPECT NPB calls him a PAROLEE Corrections call him a INMATE / CRIMINAL Judge calls him a DEFENDANT L'officier de police sait qu'il est un TÉMOIN L'investigateur de police pense qu'il est un SUSPECT NPB l'appelle un LIBÉRÉ SUR PAROLE Les corrections l'appellent un DÉTENU/CRIMINEL Le juge l'appelle un DÉFENDEUR

27. bcbc 2004 Adobe Systems Incorporated. All Rights Reserved.26 Demo Scenario explained English or French Text Document HTML XML Schema PDF eForms CORE COMPONENT BUSINESS INFORMATION ENTITY SYNTAX BIE EXPRESSION USAGE CONTEXT Context Key: urn:uuid:4a593056-3509-0766-2e7b-4e154030423f Geo-Political Context: English or French Legislative Context: Narcotics Legistation Industry Context: NAICS 9221 Process Context: HC 3515 Process Role Context: Police Chief Supporting Role Context: RCMP Investigator Product Context: N/A Systems Capabilities Context: XML Schema 1. Example: YEAR Syntax Independent Syntax Bound 2. Becomes: BEING.BIRTH.YEAR of Suspect 3.Is expressed in an XML schema fragment

28. bcbc 2004 Adobe Systems Incorporated. All Rights Reserved.27 Applications to Support Design Time Registry/Repository XML Dictionary Data Elements (CC’s and BIE’s) References Assemble r Utility INPUT OUTPUT XML Schema Form Template May be placed into Registry Transaction (Assembly Doc) Process Designers Context of Use Calls to Registry

29. bcbc 2004 Adobe Systems Incorporated. All Rights Reserved.28 Q & A  Thank you dnickull@adobe.com

30. bcbc 2004 Adobe Systems Incorporated. All Rights Reserved.29 UN/CEFACT S IMPLE, T RANSPARENT AND E FFECTIVE P ROCESSES FOR G LOBAL B USINESS.

31. 2004 Adobe Systems Incorporated. All Rights Reserved. bcbc Supplemental Technical Slides  Illustrative - for Q & A

32. bcbc 2004 Adobe Systems Incorporated. All Rights Reserved.31 Agenda  What are Core Components  What problems do they solve  Who is working on Core Components  Core Components Methodology  What is the status  How can you use them today (scenario) Also…  Technical Slides (optional)

33. bcbc 2004 Adobe Systems Incorporated. All Rights Reserved.32 Core Components concepts

34. bcbc 2004 Adobe Systems Incorporated. All Rights Reserved.33 Core Component Model

35. bcbc 2004 Adobe Systems Incorporated. All Rights Reserved.34 Data Element Methodology (*CCTS)

36. bcbc 2004 Adobe Systems Incorporated. All Rights Reserved.35 Context Declaration Mechanism

37. bcbc 2004 Adobe Systems Incorporated. All Rights Reserved.36 Core component to BIE  Core Components are without context  After context – become Business Information Entities.  Most data elements in existing languages are ipso facto BIE’s  UMM Business Entities are BIE’s