Status Report of ebXML & UN/CEFACT Core Components Project Team Activities and Deliverables

1. Status Report of ebXML & UN/CEFACT Core Components Project Team Activities and Deliverables

2. eb XML Transport, Routing & Packaging and Registry & Repository Business Models and Core Components Syntax Neutral Semantics Standard XML Technical Framework

3. ebXML UN/CEFACT + OASIS Combining 30 yrs trade facilitation, 15 yrs of traditional EDI and 20 yrs of SGML electronic documentation standards to develop global business process choreographies and semantic definitions for e business

4. ebXML Vision Vision: A global electronic market place where enterprises of any sizeanywhere can: • Find each other electronically • Conduct business through the exchange of XML based messages • Using standard message structures • According to standard business process sequences • With clear business semantics • According to standard or mutually agreed trading partner agreements • Using off the shelf purchased business applications

5. Interoperable electronic business: ebXML Syntax Neutral Semantics Vision ebXML compliant syntax implementations XML UN/EDIFACT X.12 UN Layout Etc.

6. ‘Discovery’ and Analysis methodologies • Sample Catalog of Core Components • Naming Conventions & Rules • Sample Dictionary • Classification of Context • Describe ‘conditions of reuse’ rules for document assembly • Extension Methodology • Describe waysin which components are reused Scope of CC Project Team:

7. Standards Bodies • UN/CEFACT • TMWG,EWG, • BPAWG • OASIS, W3C & eCo • ANSI X.12 • ISO TC154 BSR • TC68 (Finance) • OMG • CEN/ISSS • XML/EDI Workshop • DAMSAD Industry Groups OTA & ATA (Air & Travel) MIST (European Trade & Transport) ACORD & GDV (Insurance) AIAG (Automotive) OAG (ERP) SWIFT (Finance) EAN.UCC & GCI (Retail) EDIFICAS (Accounting & Audit) BASDA (Accounting & ERP) EDIFICE & RosettaNet (Electronics) Biztalk

8. Technical Reports/White Papers approved : Concept document and overview of deliverables Core Component Discovery and Analysis Methodology Naming Conventions for core components Sample Catalog of core components Sample Data Dictionary Context & Re-Usability of Core Components Sample Catalog of Context Drivers Document Assembly & Context Rules ebXML CC Results as of Vienna May 2001

9. At stage 4 of the UN/CEFACT Open Development Process Revised Draft to be sent for Open Review Nov 2001 To be published in three sections - Core Components Technical . Working Process and Methodology for Business Users  . Technical Details- Core Components and Context . Technical Details -Storage and Metadata . Full Glossary of Terms Core Components Primer Catalogue of Discovered Core Components Status of UN/CEFACT CC TS Oct 2001

11. Dictionary Entries • Syntax neutral name format • Oxford English basis • Multi-level entries • Unique Global Identifier (UID) • Other countries can add their language equivalents • The Naming Conventions are designed to support • extensions toother languages • We expect in the short term, at least, • French • German • Japanese

12. UID CCT Dictionary Entry Name Definition Object Class CCT Components 000105 Amount. Type A number of monetary units specified in a currency where the unit of currency is explicit or implied. Amount ·Amount. Content (000106) ·Amount Currency. Identification. Code (000107) 000089 Code. Type A character string (letters, figures or symbols) that for brevity and/or language independence may be used to represent or replace a definitive value or text of an attribute together with relevant supplementary information. Code ·Code. Content (000091) ·Code List. Identifier (000092) ·Code List. Agency. Identifier (000093) ·Code List. Version. Identifier (000099) ·Code. Name (000100) ·Language. Code (000075) 000066 Date Time. Type A particular point in the progression of time together with relevant supplementary information. Date Time ·Date Time. Content (000067) ·Date Time. Format. Text (000068) 000180 Indicator. Type A list of two, and only two, values which indicate a condition such as on/off; true/false etc. (synonym: “Boolean”). Indicator ·Indicator. Content (000181) ·Indicator. Format.Text 000090 Text. Type A character string with or without a specified language. Text ·Text. Content (000094) ·Language. Code (000075)

13. UID Dictionary Entry Name Basic or Aggregate Definition Object Class Property Term Representation Term 000024 Address. Type. Code Basic The type of the address. Address Type Code 000147 Base Charge Price. Quantity Basic The base quantity of the charge/price unit amount. Base Charge Price Quantity* Quantity 000139 Base Currency. Identification. Code Basic The currency that is on the 'one unit' side of the rate of exchange. Base Currency Identification Code

14. Domain 1 Domain 2 DISCOVERY … Discovery & Analysis Methodology Domain N Processes/ Components DISCUSS AGREE Issues ANALYSIS Domain Processes/ Components Common Processes/ Core Components Specific Domain Processes/ Components Re-Used Processes/ Components REGISTRY & REPOSITORY

15. Context ·  Product Classification Context –the goods or services concerned ·  Industry Classification Context –the relevant trading partner industry ·  Geopolitical Context– where the business process is to be conducted ·  Official Constraints Context – Any legal restrictions or requirements ·  Business Process Role Context –the role of the sender or receiver ·  Supporting Role Context– the role of any other relevant party ·  System Capabilities Context –any major restrictions derived from the type of system e.g. legacy requirements etc. Context drivers expressed as hierarchical classifications can define business process choreographies and refine core components. The classifications are:

16. EWG (EDIFACT) TMWG ebXML Methodologies for BP Models and Core Components ebXML/X12/EWG to May 2001 UN/CEFACT OASIS X12 GOAL: Global Standard Business Messages Based on Common Business Models and Common Core Components

17. X12 &UN/EDIFACT Collaboration (JCC) Timetable Sep 2000– EWG and X12 leadership proposed collaborative CC effort and EWG formally agreed Oct 2000 – X12 formally agreed Nov 2000 – ebXML meeting in Tokyo Feb 2001 –X12 meeting in Seattle & ebXML meeting in Vancouver Mar 2001 – EWG meeting in Washington May 2001 – Final ebXML meeting in Vienna Jun 2001 – X12 meeting in St Louis Sep 2001 – EWG meeting in Rotterdam where JCC as a title for this continuing collaborative effort ceased but work continues Oct 2001 – X12 meeting in Miami Oct 2001 – ebTWG meeting in San Francisco Next meetings: Feb 2002 – ebTWG meeting in Seattle Feb 2002 – X12 meeting in Seattle Mar 2002- EWG in Barcelona March 2002

18. After ebXML? Transport, Routing & Packaging and Registry & Repository Business Models and Core Components UN/CEFACT EWG, ebWG, ebTWG & BPAWG! OASIS Syntax Neutral Semantics Standard XML Technical Framework

19. Interoperable electronic business: ebXML Syntax Neutral Semantics Vision ebXML compliant syntax implementations XML UN/EDIFACT X.12 UN Layout Etc.

20. XML syntax implementation pieces are missing! XML business document design rules, XML syntax core component structures and ebXML (UN/CEFACT) CC compliant XML document schemas Where will this work be done and by whom – UBL?

21. UN/CEFACT EWG future under discussion UN/CEFACT ebWG under construction UN/CEFACT ad hoc ebTWG in transition UN/CEFACT TMWG hovering Working members must be representative of business and vendor interests i.e. from OASIS and EDIFACT/X12 business domain groups plus other XML initiatives OAGI, Rosettanet, xBRL etc. etc. The home of future CC work is currently unclear:

22. BPM CCL new material new material 3.3 3.3 e e - - Business Standards Development Management Business Standards Development Management External e External e - - Business Business Domain e Domain e - - business Standards business Standards 3.11 3.11 3.5 3.5 Standards Work Standards Work Work Work Business User Business User Business User Business User 3.4 3.4 Requirements Requirements 3.6 3.6 Business Standards Development Work Business Standards Development Work Business Operational View Business Operational View BPM BPM CCL CCL All All new material new material new material new material BPM BPM 3.9 3.9 eb eb Repository Repository All All CCL CCL Cross Domain Business - - 3.7 3.7 Assessment, Harmonisation & Approval Syntax Syntax Solutions Solutions 3.8 3.8 Technical Syntax Solutions Technical Syntax Solutions Functional Service View Functional Service View etc etc XML XML EDIFACT EDIFACT edocs edocs UBL? 3.10 3.10 Business User Implementation Business User Implementation

23. UN/EDIFACT - this would consist of an instantiation of the CCL in the form of directories and UNSM (United Nation Standard Messages) XML (UBL?) - this would consist of an instantiation of the CCL in the form of a commonly accepted directory and document schemas 3.8Technical syntax solutions Each of these will take the duly assessed, harmonised and approved business requirements and process specifications and develop the required syntax solution(s), using existing library content, and ultimately adding new solutions into the library. Two technical solution areas have been identified: Each specific syntax implementations will require their own infrastructure, which will include at least technical assessment, document design/generation, syntax rules, architecture and maintenance within each.