1. Tilak Kasturi, President E-Phase Software E-Phase.com
ebXML Initiative™
Tilak Kasturi, President
E-Phase Software
E-Phase.com
11/16/2018
e-Phase

2. Agenda History of ebXML initiative What is ebXML,Why it was formed.
Vision, Mission, Values
Strategies for the initiative
Individual teams and their mission, deliverables
11/16/2018
e-Phase

3. UN/CEFACT UN/CEFACT (www.uncefact.org) United Nations body
Worldwide policy and technical development in the area of trade facilitation and electronic business.
Headquartered in Geneva
UN/EDIFACT, the international EDI standard.
United Nations Center for the Facilitation of Procedures and Practices for Administration, Commerce and Transport (UN/CEFACT)
11/16/2018
e-Phase

4. OASIS OASIS (http://www.oasis-open.org)
Non-Profit, International consortium
Advance the open interchange of documents and structured information objects
SGML,XML
XML.org
Organization for the Advancement of Structured Information Standards (OASIS)
11/16/2018
e-Phase

5. History of ebXML Nov 9, 10 1999 Nov 17-19, 1999 Jan 31-Feb04, 2000
NATO meeting, The Hague
State-of-the-market presentation by OASIS
Nov 17-19, 1999
Inaugural meeting, San Jose, CA
140 participants from major companies, countries and organizations
Jan 31-Feb04, 2000
Project Team meetings, Orlando, FL
11/16/2018
e-Phase

6. What is ebXML Electronic business XML - ebXML
Joint effort of the United Nation/CEFACT and OASIS
“Create a Single Global XML Framework Solution”
18 month project
11/16/2018
e-Phase

7. Why ebXML? Sharing information and data worldwide
Make divergent global EDI interoperable
Unified global EDI standard
Lower the barrier of entry to eBusiness
Facilitate trade particularly with respect to small- and medium-sized enterprises (SMEs) and developing nations.
11/16/2018
e-Phase

8. Scope of ebXML Focus is to develop common framework
Cross-industry processes for message exchange
Specifications in public domain
Targeted towards
Large International Companies
Small and Medium Size enterprises (SME)
B2B, B2C (Business side)
11/16/2018
e-Phase

9. Project Teams ebXML requirements Business Process
Technical Architecture
Core Components
Transport/Routing and Packaging
Registry and Repository
Technical Coordination & support
Marketing/Awareness&Education
11/16/2018
e-Phase

10. ebXML Requirements Document and Validate Requirements
Serve as foundation for developing deliverables
Requirements of an ebXML compliant application, Interoperability
Based on W3C technical specifications
Provide for interoperability
Transition path
Will be submitted as a standard
11/16/2018
e-Phase

11. Business Process An ebXML-based business process integration
Create Meta-Model for Business Process Definition
Proof of Concept of the mappability using ebXML
Naming conventions
The vision of ebXML with respect to business processes is that organizations be able to express their business processes according to a specification to insure that they are understandable by other organizations thereby enabling integration of business processes
The Meta-model for Business Process Definition-ie the common terminology and constructs that defines/describes the business semantics (e.g. roles, interactions, messages and data)
Proof of Concept of the mappability between 2 existing industry frameworks -e.g.RosettaNet and OAG through ebXML.
Naming Conventions for instances of models and their components (eg. business service requests should consist of nouns and verbs: ‘cancelPO’
11/16/2018
e-Phase

12. Technical Architecture
Defines how ebXML represents business requirements
Reduce the need for expensive integration of business processes
Provide and support a library of common, standard intra-business processes
Define Common Business Processes, Common Semantics, Common Language (Vocabulary)
Reduce the need for collaborative business partners to have individual and expensive prior agreement on how to integrate business processes
11/16/2018
e-Phase

13. Core Components “The world does not need another P.O.!”
Identify a methodology for describing core components
Define core component content and structure
Support reuse and extensibility
Syntax Neutral
¨         Sample and recommend for XML and EDI instantiation
The Core Components Project Team may determine the need to develop core components. If that decision is made, then those core components will:
¨         Be syntax independent
[NOTE - Core components will not be specifically aligned with any existing syntax based semantics such as ANSI X12 or UN/EDIFACT]
¨         Be defined to insure separation of common "fundamental" versus "extra" specific
¨         Incorporate where appropriate ISO/IEC rules
¨         Use semantics solutions that accommodate currently defined accredited EDI semantics where they add value,
11/16/2018
e-Phase

14. Transport/Routing and Packing
Specify how to envelope business documents
Support platform independent interoperability
Meet security requirements
¨         Specify how to envelope business documents in regard to -
-          related messages in a collection, and
-          physical and/or logical addressing of destination for messages.
¨         Specify exchange at the application level
¨         Support common mapping techniques
¨         Identify messaging routing
¨         Meet security requirements
¨         Provide for audit trails
¨         Define and meet acceptable levels of quality of service
Support platform independent interoperability
11/16/2018
e-Phase

15. Registry and Repository
Develop detailed blueprints for an ebXML repository
Interface with other XML business standards repositories
accommodates versioning, metadata Registry
model interchange (UML XML Schema )
Collect mapping templates from Process owners
-          uses open management processes,
-          has open access,
-          has interfaces with other existing and planned XML business standards repositories,
-          accommodates versioning, metadata Registry, model interchange (e.g. UML - XML schemas)
  tool-to-tool queries and exchanges
   repository to repository queries and exchanges
   tool to repository queries and exchanges
repository to tool queries and exchanges
-    enables model integration (e.g., how to create an XML schema from a UML diagram and vice-versa without loss or gain),
-    supports Web access,
stores a legacy data model (e.g., IDEF-1X) and retrieves it back out as a UML class diagram
11/16/2018
e-Phase

16. Technical Coordination & Support
Project Team output consistency
A clear definition of ebXML compliance
¨         Project Team output consistency
¨         Research both internal and external XML concepts and technologies in support of executive committee and project team requirements
¨         Outreach requirements and recommendations
A clear definition of ebXML compliance
11/16/2018
e-Phase

17. Marketing/Awareness & Education
Marketing and promotion of ebXML
Awareness and education of ebXML technical specifications
11/16/2018
e-Phase

18. How do you participate?
ebXML initiative relies heavily on technical expert participation
Sign up at
Project Teams
Teleconference
Scheduled meetings
Listserv
Web site
11/16/2018
e-Phase

19. Meeting Schedules 8-12 May 2000, in Brussels, Belgium.
7-11 August in the United States
6-11 November in Tokyo, Japan.
11/16/2018
e-Phase

20. Specification Deliverables
May 8-12, Brussels meeting
ebXML Requirements
ebXML Conceptual Architecture
ebXML Message Structure and Headers
ebXML Core Components Specification
11/16/2018
e-Phase

21. Related Documents
Please Visit for archive of documents, meeting notes, team presentations
A copy of this presentation! – Please contact me.
11/16/2018
e-Phase

22. Participants Jan 31-Feb 04 Orlando Meeting Government Agencies
14 countries
83 companies
Government Agencies
National and International standards organizations
500 by virtual participation
11/16/2018
e-Phase

23. Participating Companies
IBM, Sun Microsystems, Commerce One, Dun & Bradstreet, Oracle, Visa International, General Motors
IETF/Internet Open Trading, Object Management Group (OMG), Data Interchange Standards Association (DISA), CommerceNet, Data Interchange Standards Association
Australia, Canada, France, Germany, Japan and United Kingdom, Netherlands, Finland, India
11/16/2018
e-Phase

24. Mission Statement “Create a Single Global XML Framework Solution”
11/16/2018
e-Phase

25. Q&A For Further Info Contact Tilak Kasturi tilak@e-phase.com
11/16/2018
e-Phase