UN/CEFACT Core Components: Semantic Interoperability of Data Elements and the Context Framework

1. UN/CEFACT Core ComponentsSemantic Interoperability of Data Elements and the Context FrameworkDuane Nickulldnickull@adobe.com

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.”

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.

4. 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. Problem • 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. Impact We can change it! • 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! Action Why do we need it?

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)

6. What are Core Components • 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

7. Core Component concepts BIE

8. Business Information Entities (BIE’s) Order.Date Name Name Date Company Company Line Item Phone # Phone # Address Address Party ID email email PO # Cost Party Invoice Data Elements build Business Messages at Design Time Core Components (CC’s) CONTEXT

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

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)

11. SMDG Togaf HR-XML EHD xCat UBL Rosettanet OTA IATA cXML E-construct CATXML PIDX Bolero XAML Opentrans xCBL HL7 Acord CIDX xBRL BSML agXML VICS SWIFT GCI UNeDoc GML Too many data standards All have different data elements!

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

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: Date Type: integer Mask: DDMMYY Data Element: Telephone Type: string Data Element: Name Type: string Data Element: Address Type: Aggregate

14. UN/CEFACT Core Components vision UN/CEFACT Core Component Library Reconciliation Of Data Elements 2007 2004 2002 1999 Existing Standards UBL XML X12 EDIFACT eGov SGML XML Etc.

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)

16. Who is working on Core Components • 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.

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)

18. Business Process are part of Country.Identifier Person.Family Name Context Core Component discovery process. Core Component Library Core Component Discovery Business Documents UNeDocs

19. Steps to identify Core Components

20. 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. <xml> <xs:schema> Using Core Components at Design Time New Business Process • Identify Core components to use for each Business Message Core Component Library has Business messages

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)

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…)

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)

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

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

26. 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 USAGE CONTEXT CORE COMPONENT 1. Example: YEAR BUSINESS INFORMATIONENTITY 2. Becomes: BEING.BIRTH.YEAR of Suspect Syntax Independent Syntax Bound SYNTAX BIE EXPRESSION 3.Is expressed in an XML schema fragment Demo Scenario explained English or French Text Document HTML XML Schema PDF eForms

27. XML Dictionary Data Elements (CC’s and BIE’s) Context of Use Transaction (Assembly Doc) References INPUT Assembler Utility Process Designers Calls to Registry May be placed into Registry OUTPUT XML Schema Form Template Applications to Support Design Time Registry/Repository DEMO!

28. Q & A • Thank you dnickull@adobe.com

29. UN/CEFACT SIMPLE, TRANSPARENT AND EFFECTIVE PROCESSES FOR GLOBAL BUSINESS.

30. Supplemental Technical Slides Illustrative - for Q & A

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)

32. Core Components concepts

33. Core Component Model

34. Data Element Methodology (*CCTS)

35. Context Declaration Mechanism

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