Draft notes from the Feb 10 2006 OASIS ebXML teleconference.

["Dale Moberg" <dmoberg@cyclonecommerce.com>]

February 10, 2006 OASIS ebXML Teleconference Notes

 

Attendance

 

Dale Moberg

Monica Martin

Pete Wenzel

Sacha Schlegel

Pim van der Eijk

 

Agenda is at http://lists.oasis-open.org/archives/ebxml-cppa/200602/msg00003.html

 

Consensus was that the draft schema changes for allowing perAction mshChannels for asynchronous msh signal delivery appeared OK.

 

A question was raised concerning the optional packageRef attribute that could be used to indicate the Packaging element relevant to the mshSignal. Issue is still open.

 

Discussion of ebMS 3.0 alignment was raised. Consensus favors that the TC explore including this in the 2.1 maintenance version scheduled for the middle of this year.

 

Dale conjectured that at least some Transport changes might be needed to accommodate the ebMS 3.0 mode of sending on the HTTP response. The sender needs to at least be allowed to configure an endpoint.

 

TimeToPerform discussions continued. Monica noted that the 2.0 version had a recommendation about closing the connection after the time to perform interval had elapsed. Dale is to retrieve the text for review at the next teleconference Feb. 24.

 

Dale also pointed out that a service level time to perform value might make sense when using BPSS 2.0 because the service identifier is associated with the toplevel BusinessCollaboration. So a BC TTP would be definable because a grouping beyond Action was describable. Whether these changes are in scope for 2.1 is not decided. If it is in scope

it should be considered whether the new BPSS use case for dynamic values for TTP should somehow be captured (possibly just as perMessage TTP agreed to).

 

The current draft does state in the extensibility chapter that

 

TimeToPerform

In [ebBP], the @timeToPerform attribute has been replaced by a TimeToPerform element that allows new means of specification of varying performance times for a BusinessTransaction. Therefore, the content model for both MessagingCharacteristics and BusinessTransactionCharacteristics has been generalized to allow extension by other namespace content.

 

Pim mentioned that there should be a warning to the implementer that if a synch reply mode is agreed upon (probably for the business response) that the connection should not be closed prior to the TTP interval elapsed.

 

Editor was given additional action items

 

1. Assemble the TTP contexts from the 2.1 draft for discussion
2. Study Transport schema changes for ebMS 3.0
3. and continue with a draft of specification language for perAction configurable msh signal endpoint (for asynchronous communication).

 

 

 

ebXML CPPA Teleconference Notes February 10 2006.doc