status report of ebxml & un/cefact core components project team activities and deliverables
DESCRIPTION
Status Report of ebXML & UN/CEFACT Core Components Project Team Activities and Deliverables. eb XML. Transport, Routing & Packaging and Registry & Repository. Business Models and Core Components. Syntax Neutral Semantics. Standard XML Technical Framework. ebXML. - PowerPoint PPT PresentationTRANSCRIPT
UBL TC MeetingSan Francisco Oct 2001
Status Report of ebXML & UN/CEFACT Status Report of ebXML & UN/CEFACT Core Components Project Team Core Components Project Team Activities and Deliverables Activities and Deliverables
UBL TC MeetingSan Francisco Oct 2001
Syntax Neutral
Semantics
Business Models and
Core Components
Transport, Routing & Packaging
and Registry & Repository
Standard XMLTechnical
Framework
eb XML
UBL TC MeetingSan Francisco Oct 2001
ebXMLebXMLebXMLebXML
UN/CEFACT + OASISUN/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
UBL TC MeetingSan Francisco Oct 2001
ebXML Vision
A global electronic market place where enterprises of any size anywhere 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
Vision:
UBL TC MeetingSan Francisco Oct 2001
Interoperable electronic business:
ebXML Syntax Neutral
Semantics Vision
XML UN/EDIFACT X.12 Etc.UN Layout
ebXML compliant syntax implementations
UBL TC MeetingSan Francisco Oct 2001
‘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 ways in which components are reused
Scope of CC Project Team:
UBL TC MeetingSan Francisco Oct 2001
Standards BodiesStandards Bodies
UN/CEFACTTMWG, EWG,BPAWG
OASIS, W3C & eCo
ANSI X.12
ISO TC154 BSR TC68 (Finance)
OMG
CEN/ISSS XML/EDI WorkshopDAMSAD
Industry GroupsIndustry 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
UBL TC MeetingSan Francisco Oct 2001
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 2001ebXML CC Results as of Vienna May 2001
UBL TC MeetingSan Francisco Oct 2001
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 -
1. Core Components Technical2. . Working Process and Methodology for Business Users 3. . Technical Details - Core Components and Context4. . Technical Details - Storage and Metadata5. . Full Glossary of Terms
2. Core Components Primer
3. Catalogue of Discovered Core Components
Status of UN/CEFACT CC TS Oct 2001Status of UN/CEFACT CC TS Oct 2001
UBL TC MeetingSan Francisco Oct 2001
CoreComponent
Type
BasicCore Component
Basic BusinessInformation
Entity
AggregateCore
Component
AggregateBusiness Information
Entity
Message /Document
CORE BUSINESS
Data Dictionary Repository
Core Component Library
defines incontext
defines incontext
containscontains
contains
contains
is of type
UBL TC MeetingSan Francisco Oct 2001
Dictionary EntriesDictionary EntriesDictionary EntriesDictionary 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,
FrenchGermanJapanese
UBL TC MeetingSan Francisco Oct 2001
UID CCTDictionary 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)
UBL TC MeetingSan Francisco Oct 2001
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
UBL TC MeetingSan Francisco Oct 2001
DISCOVERY
Domain 1
Domain 2
Domain N
Processes/Components
ANALYSIS
Common Processes/
Core Components
Domain Processes/
Components
Re-Used Processes/
Components
SpecificDomain
Processes/Components
Issues
DISCUSS
AGREE
REGISTRY & REPOSITORY
Discovery & AnalysisMethodology
…
UBL TC MeetingSan Francisco Oct 2001
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:
ContextContext
UBL TC MeetingSan Francisco Oct 2001
ebXML/X12/EWGebXML/X12/EWG to May 2001 to May 2001ebXML/X12/EWGebXML/X12/EWG to May 2001 to May 2001
X12
UN/CEFACT OASIS
GOAL:GlobalStandard Business MessagesBased on Common Business Models and Common Core Components
Methodologies forBP Models andCore Components
ebXML
EWG(EDIFACT)
TMWG
UBL TC MeetingSan Francisco Oct 2001
X12 X12 && UN/UN/EEDIFACT Collaboration (JCC) TimetableDIFACT Collaboration (JCC) TimetableX12 X12 && UN/UN/EEDIFACT Collaboration (JCC) TimetableDIFACT Collaboration (JCC) Timetable
Sep 2000 – EWG and X12 leadership proposed collaborative CC effort and EWG formally agreed
Oct 2000 – X12 formally agreedNov 2000 – ebXML meeting in TokyoFeb 2001 – X12 meeting in Seattle & ebXML meeting in VancouverMar 2001 – EWG meeting in WashingtonMay 2001 – Final ebXML meeting in ViennaJun 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 continuesOct 2001 – X12 meeting in MiamiOct 2001 – ebTWG meeting in San Francisco
Next meetings:
Feb 2002 – ebTWG meeting in Seattle Feb 2002 – X12 meeting in SeattleMar 2002 - EWG in Barcelona March 2002
UBL TC MeetingSan Francisco Oct 2001
Syntax Neutral
Semantics
Business Models and
Core Components
After ebXML?
Transport, Routing & Packaging
and Registry & Repository
Standard XMLTechnical
Framework
UN/CEFACT EWG, ebWG,
ebTWG & BPAWG!
OASIS
UBL TC MeetingSan Francisco Oct 2001
Interoperable electronic business:
ebXML Syntax Neutral
Semantics Vision
XML UN/EDIFACT X.12 Etc.UN Layout
ebXML compliant syntax implementations
UBL TC MeetingSan Francisco Oct 2001
XML business document design rules, XML syntax core component structures and ebXML (UN/CEFACT) CC compliant XML document schemas
XML syntax implementation pieces are missing!
Where will this work be done and by whom – UBL?
UBL TC MeetingSan Francisco Oct 2001
The home of future CC work is currently unclear:
• 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.
UBL TC MeetingSan Francisco Oct 2001
Cross -Domain Business
Assessment, Harmonisation & Approval
BPMnew material
Domain e-business StandardsWork
eb Repository
Technical Syntax Solutions
XMLEDIFACT edocs
Business UserRequirements
Bu
sin
es
s O
pe
ratio
na
l Vie
wF
un
ctio
na
l Se
rvic
e V
iew
etc
Business Standards Development Work
AllBPM
AllCCL
Bu
sin
es
s U
se
r
CCLnew material
Business User Implementation
SyntaxSolutions
e-Business Standards Development Management
External e-BusinessStandards Work 3.5
3.6
3.7
3.8
3.9
3.10
3.4
3.11
3.3
-
BPMnew material
BPMnew material
Domain e-business StandardsWork
eb Repository
Technical Syntax Solutions
XMLEDIFACT edocs
Business UserRequirements
Bu
sin
es
s O
pe
ratio
na
l Vie
wF
un
ctio
na
l Se
rvic
e V
iew
etc
Business Standards Development Work
AllBPM
AllCCL
Bu
sin
es
s U
se
r
CCLnew material
CCLnew material
Business User Implementation
SyntaxSolutions
e-Business Standards Development Management
External e-BusinessStandards Work 3.5
3.6
3.7
3.8
3.9
3.10
3.4
3.11
3.3
UBL?
UBL TC MeetingSan Francisco Oct 2001
3.83.8 Technical syntax solutions3.83.8 Technical syntax solutions
Two technical solution areas have been identified:
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
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.
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.