ebXML Messaging:
The Future
Ian Jones
E-Commerce Engineer, BT Group plc.
Chair ebXML Messaging Services TC
27 April 2004
ebXML Messaging: The future
1
Outline
• A brief history
– Version 1.0
– Version 2.0
• Version 2.1
• Version 3 - The plan
27 April 2004
ebXML Messaging: The future
2
A brief history
United Nations Centre for the Facilitation of Procedures and Practices
for Administration, Commerce and Transport
27 April 2004
ebXML Messaging: The future
(Organization for the
Advancement of Structured
Information Standards)
3
27 April 2004
ebXML Messaging: The future
4
Version 1.0
• Features, Scope & Requirements
–
–
–
–
–
–
–
–
Envelope and headers for business documents
Reliable Messaging and Error Handling
Messaging Routing
Security
Audit
Quality of Service
Platform Independent Interoperability
Restart and Recovery
• Delivered a workable specification
27 April 2004
ebXML Messaging: The future
5
Version 2.0
• Improvements
–
–
–
–
Simplification
Element & Attribute rationalization
Better alignment with CPP/A
Modularization
• Changes
– Removal of TraceHeader element
– Removal of Via element
27 April 2004
ebXML Messaging: The future
6
Version 2.1
• Outstanding Issues
• Changes requested
– None external - mostly issues internal
• What is being developed
• What is new or different
– Documentation
• Migration issues
27 April 2004
ebXML Messaging: The future
7
Version 2.1 - Issues
• Lots of outstanding issues - no consensus
for 2.0
• Interoperability testing issues
• Multi-hop definition & implantation
27 April 2004
ebXML Messaging: The future
8
Version 2.1 - Development
• Revised specification in development
• Removal of superfluous elements, e.g.
RefToMsgId in unbundled Ack.
• Warning on features that may have
significant changes in version 3, e.g.
multi-hop
27 April 2004
ebXML Messaging: The future
9
Version 2.1 - Migration
• Version 2.1 is an interim release
• Preparation for version 3.0
27 April 2004
ebXML Messaging: The future
10
Version 3.0
•
•
•
•
•
•
•
Preview paper
Requirements
Use of other Web Services
SOAP 1.2
WS-I Basic & other profiles
New payload services
Migration issues
27 April 2004
ebXML Messaging: The future
11
Version 3.0 - Preview Paper
• Why did we produce it ?
–
–
–
–
To start discussion
To gather requirements
To inform others of what were thinking
Invite comments & input
• We still invite ideas & help
27 April 2004
ebXML Messaging: The future
12
Version 3.0 - Requirements
• More and better modularization - allow
easier integration of other Web Services and
related technologies.
• Re-evaluate need or process for multi-hop
processing
• Alignment other WS specifications and
newer ebXML specifications
27 April 2004
ebXML Messaging: The future
13
Version 3.0 - Re-use of other
Web Services
• Reasons
– increase interoperability
– only invent the necessary
•
•
•
•
WS Reliability / WS Reliable Messaging
WS Security
WS Composite Application Framework
SAML
27 April 2004
ebXML Messaging: The future
14
Version 3.0 - SOAP 1.2
•
•
•
•
New “approved” version of SOAP
Toolkits now support
Modular - future proof design
Issue packaging - still propose SWA method
27 April 2004
ebXML Messaging: The future
15
Version 3.0 - WS-I profiles
• Investigate using the WS-I profiles
– Well known - interoperable definition
– Build on pre-tested combinations
– reduced software development costs
27 April 2004
ebXML Messaging: The future
16
Version 3.0 - Changes
• Manifest - move to SOAP header
• Allow “payload” in SOAP body
• Investigate and redevelop use of Digital
Signatures now technology is more mature
• Synchronous reply - definition and handling
• Reliable messaging failure recovery
• Large attachments
• Conversational Semantics and BPSS Alignment
27 April 2004
ebXML Messaging: The future
17
Version 3.0 - New Payload
Services
• Compression
• Encryption
27 April 2004
ebXML Messaging: The future
18
Version 3.0 - New Features
• Query Version and Supported Functions
• Default – Basic CPA
• Language Neutral / Abstract Message
Service API
• MSH Clustering
27 April 2004
ebXML Messaging: The future
19
Version 3.0 - Migration
• Incompatibility
– SOAP 1.2
– Version Attributes
• Support for previous versions
– An open topic - should version 3.0 MSH handle
version 2, 2.1 messages?
27 April 2004
ebXML Messaging: The future
20
Summary
• Version 2.1 is a bug fix with some tidy to
prepare for version 3.0
• Version 3.0 is a major upgrade and we
invite comments, input and help
• Version 3.0 starts being built here
tomorrow!
27 April 2004
ebXML Messaging: The future
21
Questions
27 April 2004
ebXML Messaging: The future
22
Thank You
27 April 2004
ebXML Messaging: The future
23