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


Help: OASIS Mailing Lists Help | MarkMail Help

bdx message

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

Subject: Re: [bdx] Proposal for a TC recharter

Hi Mike

Thanks for your comments, and I agree that it will be useful to start off the discussion by mail.

The original charter for the TC is a sort of one-off with a fixed schedule that accommodates for PEPPOL's project plan, and where the work of the TC stops once an initial set of specifications have been approved as OASIS standards.

With the new proposed charter it is our intention to not only broaden the scope of the TC but also to provide a more long term sustainable "home" for the specifications that we produce. It is the intention that the TC shall continue to maintain and produce specifications also after an initial set has been approved. With the broadening of the scope we are also broadening the the potential use cases for BDX and the amount of participants interested in moving the progress forward. I believe this will work to our advantage, also time wise, as the TC will get more resources who participates in the development.

Best regards,


From: Mike Edwards <mike_edwards@uk.ibm.com>
Date: Mon, 13 Feb 2012 09:21:16 +0000
To: Kenneth Bengtsson <kenneth@alfa1lab.com>
Cc: "bdx@lists.oasis-open.org" <bdx@lists.oasis-open.org>
Subject: Re: [bdx] Proposal for a TC recharter


This is a very interesting proposal.

I think that it would be very usefulto have a discussion of the proposal via the BDX TC email list ahead of the proposed meeting
on the 29th February, so that we can make more effective use of the time during that meeting.

I note that the proposed new charter for the TC appears to include a substantial broadening of the scope of the TC, which to me
implies more work and as a result a longer schedule for the TC.  In addition, the new charter is vague about the actual specifications
that will be produced by the TC, so that it is difficult to understand the amount of work that the TC will produce.  I note that progress
on the specifications currently agreed under the existing TC charter has not been swift - how is the new charter likely to affect
progress going forward?

Yours, Mike

Dr Mike Edwards Mail Point 137, Hursley Park
STSM Winchester, Hants SO21 2JN
SCA, Cloud Computing & Services Standards United Kingdom
Co-Chair OASIS SCA Assembly TC 
Chair UK ISO SC38 mirror committee (Cloud & SOA)  
PEPPOL eProcurement team member  
IBM Software Group 
Phone:+44-1962 818014 
Mobile:+44-7802-467431 (274097) 

From:Kenneth Bengtsson <kenneth@alfa1lab.com>
To:"bdx@lists.oasis-open.org" <bdx@lists.oasis-open.org>
Date:12/02/2012 16:47
Subject:[bdx] Proposal for a TC recharter
Sent by:<bdx@lists.oasis-open.org>


To move the work of the TC into a broader scope and to accommodate requirements raised by BDX adopters, some members of the TC have worked out a proposal for a rechartering of the OASIS Business Document Exchange TC. The proposal for the rechartering is submitted in accordance with the OASIS TC Process section 2.12:


The proposed new charter is being submitted by the following members of the TC:

Roger Bass, Traxian
Kenneth Bengtsson, Alfa1lab
Pim van der Eijk, Sonnenglanz Consulting
Klaus Vilstrup Pedersen, Difi-Agency for Public Management and eGovernment
Sven Rasmussen, Danish Ministry of Science, Technology and Innovation
Susanne Wigard, Land Nordrhein-Westfalen

We kindly request that the TC chairs arrange for a TC meeting the week of February 27 2012 to discuss the proposed new charter below. Depending on the outcome of these discussions we can proceedto formally adopt the changes using the process described in the OASIS TC Process.


Name of TC:
OASIS Business Document Exchange TC

Statement of Purpose:
The BDX standard will describe an architecture (or sets of reference architectures) where two entities exchange business documents in a secure and reliable way through the use of gateways (sometimes also referred to as access points), which is also known as the “four-corner model”.

The purpose of the TC is therefore to define the specifications of a federated messaging and trust infrastructure for data exchange and web services interoperability between domains. Here, a “domain” can be any community whose members (a) are connected through a shared system, and (b) may interact with others across domains.

Regardless of each domain’s internal workings, such interactions entail them each consuming and exposing to others over the Internet certain interfaces. These specifications should provide a framework for domains to interoperate securely and reliably (via Web Services), which can therefore be viewed as an Inter-cloud Web Services framework.

The TC specifications should be lightweight but, wherever and to the extent possible, based on profiles of existing standards from OASIS and elsewhere that are widely-used and proven, or otherwise seen to be generally applicable.  Approaches that are modular and agnostic about data content and implementation architectures will be preferred.

The TC will focus first on requirements for exchanges between groups of related domains around standardized processes/data. Requirements of cross-domain business documents exchange, with its corresponding use cases, and implied interoperability requirements will inform prioritization of the TC’s initial deliverables. The TC will specifically address requirements from the Large Scale Pilots (“LSPs”) in the area of e-government PEPPOL, e-CODEX and SPOCS.

In certain areas the work will therefore initially be centered on the work of these LSPs (notably on SMLP around identity and service discovery, addressing and profiling), and will also consider other approaches and related specifications (e.g. DNS, ebXML CPA, UDDI, ebXML RegRep, WS-Discovery), The TC may define or profile more than one such specification(s).

In other areas, published specifications today may be absent or have gaps.  In such cases the TC will attempt to identify relevant standards or work-in-progress at OASIS or other SDOs to establish liaisons with and provide requirements for such efforts, as needed.

Scope of work of the TC:
The specific objectives will be to define, specify and maintain the following:

1) Use cases and requirements, based on submissions;

2) Profiling / gap analysis of existing standards with reference to the use cases and requirements, potentially including:
  a) Addressing / Routing / Discovery (SML and related technologies)
  b) Service profiles/Capabilities (SMP, CPA and others)
  c) Identity/Authentication
  d) Trust Frameworks
  e) Transport / Reliable Messaging (e.g. AS4)

3) Unified architecture for all processes necessary and sufficient for the superset of supported use cases;

4) Specifications for SML/SMP will be developed within the TC;

5) PEPPOL specifications for the START and LIME protocols.

List of deliverables:
Technical specifications for protocols supporting distributed discovery of locations and e-business and technical capabilities of exchange partners.

Profiles of B2B messaging protocols for use in four-corner (or multi-corner) topologies.

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:

  - Enterprise procurement vendors and supplier networks
  - Software companies (e.g. providers of middleware and business applications)
  - Supplier information management providers
  - Public institutions
  - Financial institutions and payment networks
  - Large private companies

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

The initial list of liaisons that will be established includes: OASIS ebXML Technical Committees, ETSI ESI and OASIS Identity in the Cloud TC.

Other liaisons will be established in the course of the work.


Best regards,

Kenneth Bengtsson

Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

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