Projects One Pager

 


electronic business XML (ebXML)
Transport, Routing and Packaging Overview

31 July, 2000

Introduction
  The TRP group is working on specifications addressing the requirements specified by the ebXML Transport, Routing and Packaging Overview and Requirements Document.

Vision

  "The vision of the Transport and Packaging team is to produce a specification for a set of services and protocols that will let an e-commerce client request services from e-commerce servers over any application-level transport protocol, including SMTP, HTTP, FTP, and many others." -Rik Drummond, chair of the TRP group.

Scope/Key Issues

  1. To provide software practitioners with sufficient detail to develop software used in the packaging, exchange and processing of information following the ebXML specifications.

  2. To define the enveloping specifications used to represent ebXML messages and encapsulate ebXML message headers and digital payloads for transport over a data communication mechansim.
  3. To define the header information required to enable electronics documents to be transported between two services.
  Aspects to ebXML messaging not addressed by TRP include: Content and Semantics of Message Headers, payload structure, business processes, choreography of message exchanges and error handling. These are addressed in other ebXML specification documents.
Software practitioners are expected to use this document in combination with other ebXML specification documents when creating ebXML compliant software.

Objectives

  The objective of the TRP working group are:

  1.) to enable any party to carry out integrated eCommerce transaction with any other party anywhere in the world using their hardware and software vendor of choice

  2.) to persuade a wide variety of vendors to implement the approach

  3.) to not reinvent the wheel - re-use where possible

  4.) to enable existing "messaging" solutions to "bridge" to the ebXML solution

  5.) to scale from SMEs to large companies
  6.) to scale from low power to high end solutions

Requirements

 
  • No limitation is implied relative to processing mode, the structures defined in this specification can be used in one-way, broadcast, request/response (RPC) or full messaging mode communications between parties.
  • Enable parties to "package" very simple to very complex combinations of headers and payloads
  • Payload Neutral
  • Transport Neutral
  • Support corporate security policies and business practices

TRP Documents

 

ebXML TRP Overview and Requirements

  • Public release v0-96, 26 May 2000

ebXML TRP Message Envelope Specification

  • Public release v0-5, 26 July 2000
  • Internal: v0-6, 24 July 2000

ebXML TRP Strawman Message Header Specification

  • Public release v0-5 26 May 2000

ebXML Document Control and Index

  • Referred to in TRP Message Envelope Specification

Electronic Trading Partner

  • Internal: Martin Sachs & John Ibbotson, IBM
  • Internal Pre-submission Draft, v1.0.6

The role of TPAs within ebXML Transport

  • Internal: John Ibbotson, IBM, & Ian Jones, BT

EbXML Reliable Messaging Specification v0.06

  • Internal: 26 July 2000
    Kim Hughes & Masayoshi Shimamura, Fujitsu
 

A new approach is to develop a methodology for analysis of the existing data models currently used in e-business. The methodology is intended to:

  • be syntactically neutral,
  • aonform to ISO11179,
  • align with the Unified Modeling Methodology and
  • provide a mechanization for developing Core Components

 

Internal means it is still being reviewed inside TRP prior to release for general review



   

Please address questions or comments regarding this site to webmaster@ebxml.org