1 / 23

Future of ebXML Messaging: Evolution to Version 3.0

Explore the past, present, and future of ebXML Messaging from Version 1.0 to the upcoming Version 3.0. Understand the features, improvements, outstanding issues, and migration paths in this comprehensive overview. Stay informed and contribute to the development of this essential communication protocol.

currys
Download Presentation

Future of ebXML Messaging: Evolution to Version 3.0

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ebXML Messaging:The Future Ian Jones E-Commerce Engineer, BT Group plc. Chair ebXML Messaging Services TC ebXML Messaging: The future

  2. Outline • A brief history • Version 1.0 • Version 2.0 • Version 2.1 • Version 3 - The plan ebXML Messaging: The future

  3. (Organization for the Advancement of Structured Information Standards) United Nations Centre for the Facilitation of Procedures and Practices for Administration, Commerce and Transport A brief history ebXML Messaging: The future

  4. ebXML Messaging: The future

  5. 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 ebXML Messaging: The future

  6. Version 2.0 Improvements Simplification Element & Attribute rationalization Better alignment with CPP/A Modularization Changes Removal of TraceHeader element Removal of Via element ebXML Messaging: The future

  7. Outstanding Issues Changes requested None external - mostly issues internal What is being developed What is new or different Documentation Migration issues Version 2.1 ebXML Messaging: The future

  8. Lots of outstanding issues - no consensus for 2.0 Interoperability testing issues Multi-hop definition & implantation Version 2.1 - Issues ebXML Messaging: The future

  9. 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 Version 2.1 - Development ebXML Messaging: The future

  10. Version 2.1 is an interim release Preparation for version 3.0 Version 2.1 - Migration ebXML Messaging: The future

  11. Preview paper Requirements Use of other Web Services SOAP 1.2 WS-I Basic & other profiles New payload services Migration issues Version 3.0 ebXML Messaging: The future

  12. 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 Version 3.0 - Preview Paper ebXML Messaging: The future

  13. 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 Version 3.0 - Requirements ebXML Messaging: The future

  14. Reasons increase interoperability only invent the necessary WS Reliability / WS Reliable Messaging WS Security WS Composite Application Framework SAML Version 3.0 - Re-use of other Web Services ebXML Messaging: The future

  15. New “approved” version of SOAP Toolkits now support Modular - future proof design Issue packaging - still propose SWA method Version 3.0 - SOAP 1.2 ebXML Messaging: The future

  16. Investigate using the WS-I profiles Well known - interoperable definition Build on pre-tested combinations reduced software development costs Version 3.0 - WS-I profiles ebXML Messaging: The future

  17. 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 Version 3.0 - Changes ebXML Messaging: The future

  18. Compression Encryption Version 3.0 - New Payload Services ebXML Messaging: The future

  19. Query Version and Supported Functions Default – Basic CPA Language Neutral / Abstract Message Service API MSH Clustering Version 3.0 - New Features ebXML Messaging: The future

  20. Incompatibility SOAP 1.2 Version Attributes Support for previous versions An open topic - should version 3.0 MSH handle version 2, 2.1 messages? Version 3.0 - Migration ebXML Messaging: The future

  21. 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! ebXML Messaging: The future

  22. Questions ebXML Messaging: The future

  23. Thank You ebXML Messaging: The future

More Related