OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

tc-announce message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Call for Participation: OASIS Business Document Exchange TC

To:  OASIS members & interested parties

   A new OASIS technical committee is being formed. The OASIS Business Document Exchange Technical Committee has been proposed by the members of OASIS listed below. The TC name, statement of purpose, scope, list of deliverables, audience, and language specified in the proposal will constitute the TC's official charter. Submissions of technology for consideration by the TC, and the beginning of technical discussions, may occur no sooner than the TC's first meeting.

   The eligibility requirements for becoming a participant in the TC at the first meeting are:

   (a) you must be an employee of an OASIS member organization or an individual member of OASIS, and
   (b) you must join the Technical Committee, which members may do by using the "Join this TC" button on the TC's home page at [a].

   To be considered a voting member at the first meeting, you must:
   (a) join the Technical Committee at least 7 days prior to the first meeting (12 January 2011); and
   (b) you must attend the first meeting of the TC, at the time and date fixed below (19 January 2011).

Of course, participants also may join the TC at a later time. OASIS and the TC welcomes all interested parties.

   Non-OASIS members who wish to participate may contact us about joining OASIS [b]. In addition, the public may access the information resources maintained for each TC: a mail list archive, document repository and public comments facility, which will be linked from the TC's public home page at [c].

   Please feel free to forward this announcement to any other appropriate lists. OASIS is an open standards organization; we encourage your participation.



Mary P McRae
Director, Standards Development
Technical Committee Administrator
OASIS: Advancing open standards for the information society
email: mary.mcrae@oasis-open.org 
web: www.oasis-open.org
twitter: @fiberartisan #oasisopen
phone: 1.603.232.9090

[a] [a] http://www.oasis-open.org/apps/org/workgroup/bdx
[b] See http://www.oasis-open.org/join/
[c] http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=bdx


OASIS Business Document Exchange TC

Name of the TC: 
OASIS Business Document Exchange Technical Committee

Statement of Purpose:
The purpose of the TC is to define specifications for a lightweight and federated messaging infrastructure supporting a 4-corner model(1) for the secure and reliable exchange of electronic documents. Wherever possible, the TC specifications will be  based on profiles of existing standards from OASIS and elsewhere.

The TC does not intend to replace existing messaging service standards. Instead, it will provide a simplified model for the exchange of documents, based on profiles of existing messaging service standards, plus some additional necessary infrastructure.

The foundation for the work will be the specifications developed as part of the PEPPOL(2) project, which provide the infrastructure for public eProcurement in Europe; however, the specifications will be designed for use with any business process. The TC intends to become the maintenance forum for interfaces implemented by the PEPPOL project and similar infrastructure initiatives. 

Scope of work of the TC: 
The primary objective of the TC is to specify an addressing mechanism that supports a 4-corner model. This addressing mechanism may be used with many transport protocols; however, initially the TC will focus on START/LIME and ebMS.

The specific objectives will be to:
1.    Establish specifications for a lightweight and federated document transport infrastructure supporting the secure and reliable exchange of electronic business documents.
2.    Profile and maintain a robust, secure and lightweight addressing mechanism (SMLP) capable of exposing metadata about endpoints (including supported business processes, content standards, transport protocols, and security requirements) and capable of being operated in a highly distributed environment.
3.    Support the dynamic creation of connections based on look-up of services at runtime. 
4.    a) Profile and maintain the START (Secure Trusted Asynchronous Reliable Transport) protocol. START is intended to be used as a transport profile between Service Providers in the 4-corner model.
4.    b) Profile and maintain the LIME (Lightweight Message Exchange) protocol, a secure and reliable lightweight messaging protocol. LIME is intended to be used as a transport profile between senders or receivers and their Service Providers in a 4-corner model.
5.    Profile and maintain the ebMS 3.0 protocol for use in the  4-corner model with SMLP.
6.    Give guidance on using other transports in a 4-corner model.
7.    Develop specifications that support service levels appropriate for large scale deployment.  

Out of scope:
The TC will not profile synchronous end-to-end messaging protocols, as they are not appropriate in a 4-corner model of network interconnections. Nevertheless, the addressing mechanism should be equally suitable for synchronous and asynchronous exchanges and can therefore be used in synchronous scenarios not covered by the 4-corner model. 

End-to-end proof of delivery will not be covered by the TC, but proof of delivery between Service Providers is in scope.

Authentication mechanisms between senders or receivers and their Service Provider will not be covered by the TC.

List of deliverables:
The TC will produce an integrated set of Committee Specifications including a set of XML Schemas and an XML-based request/response protocol for the exchange of documents. 

Committee Specifications will cover: 
1.    BDEA (Business Document Exchange Architecture): A specification of a 4-corner model for the exchange of business documents.
2.    SMLP (Service Metadata Location and Publishing): A specification for a robust, secure, federated and lightweight addressing mechanism.
3.    START (Secure Trusted Asynchronous Reliable Transport): A profile of secure, trusted, asynchronous and reliable messaging. 
4.    LIME (Lightweight Message Exchange): A profile of a secure and reliable, lightweight messaging protocol. 
5.    A profile of ebMS (ebXML Message Service Specification) 3.0 for secure, trusted, asynchronous and reliable messaging with SMLP. 
6.    Test and conformance suites aiding the development of interoperable implementations of the profiles.

The first Committee Specifications will be based on the specifications made by the PEPPOL project (see 
This will be the main focus of the first nine months. These specifications will be contributed to the TC by the specifications' owner.

The TC intends that the Committee Specifications will become OASIS Standards.

It is estimated that the delivery of an initial set of specifications will take one to two years.

It is the goal that the first deliverables will be as follows:
-  March 2011: Committee Specification Drafts under OASIS namespaces based on PEPPOL specifications.
-  July 2011: Committee Specification Drafts for implementation by the PEPPOL project.
-  October 2011: Public review of Committee Specification Drafts
-  December 2011: Committee Specifications approved
-  March 2012: Committee Specifications become OASIS Standards

IPR Mode under which the TC will operate:
The TC will operate under the Non-Assertion Mode.

The anticipated audience or users of the work:
The initial target groups for the TC are
1.    Service providers and self-service providers (for example Value Added Network Operators, Banks, eProcurement solution providers etc). 
2.    Software companies (e.g. suppliers of middleware and software platforms)
3.    Public institutions
4.    Large private companies 

Language of the Technical Committee:
The business of the Technical Committee will be conducted in English.

Non-normative information regarding the startup of the TC: 

Similar or applicable work
A number of OASIS TCs and working groups at other standards organizations have covered and are covering subject areas similar to that of the TC. 
- UDDI: The Universal Description, Discovery, and Integration (UDDI) OASIS Standard forms the necessary technical foundation for publication and discovery of Web services implementations both within and between enterprises. UDDI was advanced by an OASIS TC that has completed its work.

- ebMS: The ebXML Messaging Services OASIS Standard defines the transport, routing and packaging of business transactions using standard Internet technologies. This work will foster consistency across specifications developed in other forums and carry forward the work started in the ebXML Transport, Routing and Packaging project team

- OASIS ebXML Registry: The OASIS ebXML Registry OASIS Standard defines specifications for achieving interoperable registries and repositories, with an interface that enables the submission, query and retrieval of contents in the registry and repository. 

- WS-I Basic Security Profile: This interoperability profile deals with transport security, SOAP messaging security and other Basic-Profile-oriented Web services security considerations.

- IETF Network Working Group: The MIME-Based Secure Peer-to-Peer Business Data Interchange Using HTTP, Applicability Statement 2 (AS2) describes how to exchange structured business data securely using the HTTP transfer protocol, instead of SMTP.  Structured business data may be XML; Electronic Data Interchange (EDI) in either the American National Standards Committee (ANSI) X12 format or the UN Electronic Data Interchange for Administration, Commerce, and Transport (UN/EDIFACT) format; or other structured data formats.  The data is packaged using standard MIME structures.  Authentication and data confidentiality are obtained by using Cryptographic Message Syntax with S/MIME security body parts.  Authenticated acknowledgements make use of multipart/signed Message Disposition Notification (MDN) responses to the original HTTP message.

- AMQP Working Group: The AMQP Working Group collaborate on specifications for messaging infrastructure that provides an facility for connecting messaging-dependent applications. AMQP's scope covers messaging within and between firms, with applicability to both business and infrastructure messaging.

The work of the TC does compete with the work of various groups mentioned above. A compliant infrastructure may be realized using software implementing one of these specifications.

First meeting:
The first meeting will be held on 19 January 2011 (at 17:00 CET) as a one-hour conference call. The meeting facility will be available at 
https://connect.forskningsnettet.dk/bdexchange/. Sign in as guest.

Meeting schedule:
The TC will hold weekly conference calls and in addition two face-to-face meetings a year (November and May). Face-to-face meetings will be sponsored by the members of the TC.

The names, electronic mail addresses, and membership affiliations of at least Minimum Membership who support this proposal:
Jens Jakob Andersen, jjan@itst.dk, Denmark Ministry of Science, Technology & Innovation
Mikkel Hippe Brun, mhb@tradeshift.com, Tradeshift Network Ltd.
Pim van der Eijk, pvde@sonnenglanz.net, Sonnenglanz
Tim McGrath, tim.mcgrath@documentengineeringservices.com, Document Engineering Services
Andrea Caccia, andrea.caccia@studiocaccia.com, AITI - Associazione Italiana dei Tesorieri d'Impresa
Thomas Gundel, tg@itcrew.dk
Paul Fremantle, paul@wso2.com, WSO2
Ken Holman, gkholman@CraneSoftwrights.com

Primary Representative statements of support:
Denmark Ministry of Science, Technology & Innovation
"The Danish National IT and Tele Agency (NITA) fully supports the idea of creating this TC within the framework of OASIS.
Denmark has developed and implemented both technical solutions, as well as legislation in this area, to create an effective and dynamic National ecommerce infrastructure, that generates substantial savings for both private and public sector.
We see a standardization within OASIS as the natural next step, to ensure that the knowhow is forwarded to the global community."
Jens Jakob Anderesen, jjan@itst.dk, Denmark Ministry of Science, Technology & Innovation

Tradeshift Network Ltd
"Tradeshift Network Ltd fully supports and intends to participate in the OASIS BusDox TC. Lowering barriers for SME's use of messaging infrastructures is of key importance in the coming years - especially in the fields of e-invoicing and supply chain connectivity. We believe that the BusDox TC will be an important enabler in this quest."
Mikkel Hippe Brun, mhb@tradeshift.com, Tradeshift Network Ltd.

Sonnenglanz Consulting
"As the primary representative of Sonnenglanz Consulting to OASIS, I officially inform you of our company's intention to participate in the OASIS Business Document Exchange TC."
Pim Van der Eijk , pvde@sonnenglanz.net, Sonnenglanz Consulting

Document Engineering Services
"Document Engineering Services supports and intends to participate in the OASIS Business Document Exchange TC."
Tim McGrath, tim.mcgrath@documentengineeringservices.com, Document Engineering Services

"I confirm that AITI - Associazione Italiana dei Tesorieri d'Impresa, Oasis member, is interested to participate to this new TC."
Gianfranco Tabasso,  AITI - Associazione Italiana dei Tesorieri d'Impresa (gianfranco.tabasso@fmsgroup.it)

"I, Paul Fremantle, as the Primary Representative to OASIS for WSO2, provide support to create the Business Document Exchange TC at OASIS"
Paul Fremantle, paul@wso2.com, WSO2

The Convenor will be Mikkel Hippe Brun (mhb@tradeshift.com).

The name of the Member Section with which the TC intends to affiliate, if any

A list of contributions of existing technical work that the proposers anticipate will be made to this TC

Optionally, a draft Frequently Asked Questions (FAQ) document

Optionally, a proposed working title and acronym for the specification(s) to be developed by the TC


(1) The 4-Corner Model

A document exchange process set-up whereby each Participant has contracted with one or several separate Service Providers, whereby the Service Providers ensure the correct interchange of documents between the Participants.

When senders and receivers of documents are supported by their own consolidator service provider (for the sender) and aggregator service provider (for the receiver), it is referred to as a 4-Corner model. A network usually based on open standards provides connectivity and the facilities for the secure trusted exchange of business documents. In the 4-Corner models, the consolidator and aggregator roles are often two different service providers.

Definition inspired from http://www.e-invoice-gateway.net/helpandsupport/glossary/

(2) The PEPPOL Project http://www.peppol.eu

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]