UN/CEFACT Core Components

1. UN/CEFACT Core Components • Duane Nickull, CEFACT Plenary Bureau Vice-Chair, dnickull@adobe.com

2. United Nations Centre for Trade Facilitation and Electronic Business “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. Why do we need it?We Must Integrate the Information Ecosystem • 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

5. UN/CEFACT Structure STRATEGY TACTICAL VISION

6. Agenda • What are Core Components • What problems do they solve • Who is working on Core Components • Core Components explained • What is the status • How can you use them today (scenario) Also… • Technical Slides (optional)

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

8. Core Component concepts BIE

9. Data Elements build Business Messages at Design Time 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 CONTEXT

10. 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. Agenda • What are Core Components • What problems do they solve • Who is working on Core Components • Core Components explained • What is the status • How can you use them today (scenario) Also… • Technical Slides (optional)

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

13. 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 OFPERSON

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

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

16. Agenda • What are Core Components • What problems do they solve • Who is working on Core Components • Core Components explained • What is the status • How can you use them today (scenario) Also… • Technical Slides (optional)

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

18. Agenda • What are Core Components • What problems do they solve • Who is working on Core Components • Core Components explained • What is the status • How can you use them today (scenario) Also… • Technical Slides (optional)

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

20. Steps to identify Core Components

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

22. Agenda • What are Core Components • What problems do they solve • Who is working on Core Components • Core Components explained • What is the status • How can you use them today (scenario) Also… • Technical Slides (optional)

23. 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… see next page) • First 19 Core Components expected to be ratified by CEFACT in MacLean Virginia September 2004

24. Agenda • What are Core Components • What problems do they solve • Who is working on Core Components • Core Components explained • What is the status • How can you use them today and tomorrow (scenario) Also… • Technical Slides (optional)

25. Using Core Components Today • UNeDocs instances use several pieces of information. • These are specialized Core Components, also called Business Information Entities or BIE’s. • It is possible to place UN/CEFACT Core Components into a Registry/Repository and use them for building UNeDocs today and tomorrow. • Pilot Infrastructure would need to be built

26. UNeDocs use of Core Components? Update/change Requests Could be reflected real time in UN eDocs instances UN eDocs Example CC: Country.Identifier is associated with a list of values (UN LoCode) Core Component Library (Registry)

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

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

29. Supplemental Technical Slides Illustrative - for Q & A

30. Agenda • What are Core Components • What problems do they solve • Who is working on Core Components • Core Components explained • What is the status • How can you use them today (scenario) Also… • Technical Slides (optional)

31. Core Components concepts

32. Core Component Model

33. Data Element Methodology (*CCTS)

34. Context Declaration Mechanism

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