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

Embed Size (px)

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 Presentation

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

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

  • Syntax Neutral SemanticsBusiness Models and Core ComponentsTransport, Routing & Packaging and Registry & RepositoryStandard XMLTechnicalFrameworkeb XML

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

  • ebXML Vision A global electronic market place where enterprises of any size anywhere can:Find each other electronicallyConduct business through the exchange of XML based messagesUsing standard message structures According to standard business process sequencesWith clear business semanticsAccording to standard or mutually agreed trading partner agreementsUsing off the shelf purchased business applicationsVision:

  • Interoperable electronic business:ebXML Syntax Neutral Semantics VisionXMLUN/EDIFACTX.12Etc.UN LayoutebXML compliant syntax implementations

  • Discovery and Analysis methodologiesSample Catalog of Core ComponentsNaming Conventions & RulesSample DictionaryClassification of Context Describe conditions of reuse rules for document assemblyExtension Methodology Describe ways in which components are reusedScope of CC Project Team:

  • Standards Bodies

    UN/CEFACTTMWG, EWG,BPAWG

    OASIS, W3C & eCo

    ANSI X.12

    ISO TC154 BSR TC68 (Finance)

    OMG

    CEN/ISSS XML/EDI WorkshopDAMSAD

    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

  • 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 RulesebXML CC Results as of Vienna May 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 -

    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

  • 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, FrenchGermanJapanese

  • DISCOVERYDomain 1Domain 2Domain NProcesses/ComponentsANALYSISCommon Processes/Core ComponentsDomain Processes/ComponentsRe-Used Processes/ComponentsSpecificDomainProcesses/ComponentsIssuesDISCUSSAGREEREGISTRY & REPOSITORYDiscovery & AnalysisMethodology

  • 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:Context

  • ebXML/X12/EWG to May 2001X12UN/CEFACTOASIS GOAL:GlobalStandard Business MessagesBased on Common Business Models and Common Core Components

  • X12 & UN/EDIFACT Collaboration (JCC) TimetableSep 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

  • Syntax Neutral SemanticsBusiness Models and Core ComponentsAfter ebXML?Transport, Routing & Packaging and Registry & RepositoryStandard XMLTechnicalFrameworkUN/CEFACT EWG, ebWG, ebTWG & BPAWG!OASIS

  • Interoperable electronic business:ebXML Syntax Neutral Semantics VisionXMLUN/EDIFACTX.12Etc.UN LayoutebXML compliant syntax implementations

  • 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?

  • The home of future CC work is currently unclear:UN/CEFACT EWG future under discussionUN/CEFACT ebWG under constructionUN/CEFACT ad hoc ebTWG in transitionUN/CEFACT TMWG hoveringWorking 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.

  • Cross-Domain Business Assessment, Harmonisation & ApprovalDomain e-business StandardsWorkebRepositoryTechnical Syntax SolutionsXMLEDIFACTedocsBusiness UserRequirementsBusiness Operational ViewFunctional Service ViewetcBusiness Standards Development WorkAllBPMAllCCLBusiness UserBusiness User ImplementationSyntaxSolutionse-Business Standards Development ManagementExternal e-BusinessStandards Work3.53.63.73.83.93.103.43.113.3-BPMnew materialBPMnew materialDomain e-business StandardsWorkebRepositoryTechnical Syntax SolutionsXMLEDIFACTedocsBusiness UserRequirementsBusiness Operational ViewFunctional Service ViewetcBusiness Standards Development WorkAllBPMAllCCLBusiness UserCCLnew materialCCLnew materialBusiness User ImplementationSyntaxSolutionse-Business Standards Development ManagementExternal e-BusinessStandards Work3.53.63.73.83.93.103.43.113.3UBL?

  • 3.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 schemasEach 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.