Status Report of eb XML UNCEFACT Core Components

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

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

eb. XML 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 3

eb. XML Vision: A global electronic market place where enterprises of any size anywhere can: n Find each other electronically n Conduct business through the exchange of XML based messages – – – 4 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

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

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

Standards Bodies Industry Groups UN/CEFACT TMWG, EWG, BPAWG OTA & ATA (Air & Travel) OASIS, W 3 C & e. Co ACORD & GDV (Insurance) ANSI X. 12 7 MIST (European Trade & Transport) AIAG (Automotive) OAG (ERP) ISO TC 154 BSR TC 68 (Finance) SWIFT (Finance) OMG EDIFICAS (Accounting & Audit) CEN/ISSS XML/EDI Workshop DAMSAD BASDA (Accounting & ERP) EAN. UCC & GCI (Retail) EDIFICE & Rosetta. Net (Electronics) Biztalk

eb. XML CC Results as of Vienna May 2001 Technical Reports/White Papers approved : 8 § 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

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

10

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 to other languages • We expect in the short term, at least, French German Japanese 11

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 A character string with or without a specified language. Text 000090 12 Text. Type · Text. Content (000094) · Language. Code (000075)

UID Dictionary Entry Name Basic or Aggregat e Definition Object Class Property Term Representat ion 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 Identificat ion Code 13

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

Context drivers expressed as hierarchical classifications can define business process choreographies and refine core components. The classifications are: · 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. 15

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

X 12 & UN/EDIFACT Collaboration (JCC) Timetable Sep 2000 – EWG and X 12 leadership proposed collaborative CC effort and EWG formally agreed Oct 2000 – X 12 formally agreed Nov 2000 – eb. XML meeting in Tokyo Feb 2001 – X 12 meeting in Seattle & eb. XML meeting in Vancouver Mar 2001 – EWG meeting in Washington May 2001 – Final eb. XML meeting in Vienna Jun 2001 – X 12 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 – X 12 meeting in Miami Oct 2001 – eb. TWG meeting in San Francisco Next meetings: Feb 2002 – eb. TWG meeting in Seattle Feb 2002 – X 12 meeting in Seattle Mar 2002 - EWG in Barcelona March 2002 17

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

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

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

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

3. 3 e-Business Standards Development Management Business User Requirements 3. 4 All eb Repository 3. 9 Domain e-business Standards Work 3. 5 Business Standards Development Work 3. 6 BPM CCL new material BPM All CCL Technical Syntax Solutions 3. 8 EDIFACT 22 UBL? XML etc edocs 3. 10 Business User Implementation Functional Service View Syntax Solutions Cross-Domain Business Assessment, Harmonisation & Approval 3. 7 Business Operational View Business User External e-Business Standards Work 3. 11

3. 8 Technical 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: u UN/EDIFACT - this would consist of an instantiation of the CCL in the form of directories and UNSM (United Nation Standard Messages) u XML (UBL? ) - this would consist of an instantiation of the CCL in the form of a commonly accepted directory and document schemas 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. 23