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

 


Help: OASIS Mailing Lists Help | MarkMail Help

business-transaction message

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


Subject: [business-transaction] BT TC con call - April 17 - details and agendaitems




BTP TC conference call for Wednesday April 17
=====================================================================
Call details, thanks to Choreology for hosting!

Date:  Wednesday, April 17, 2002
Time:  4:00 PM GMT
Duration:  2 Hours
Participants:  11
Title:  OASIS BTP meeting
Options:  Start recording call using control pad
Generate unique access codes for this call
Block use of the toll-free number

To join this conference:

For quick access, go to https://www.spiderphone.com/86211710
(This link will help connect both your browser and telephone to the call)

OR dial +1 (212) 812-2800 and enter 8621 1710

To see if your browser is configured to use the web-enhanced features of
your call,
go to http://www.spiderphone.com/BrowserCheck


=====================================================================
Agenda:
  - Greet, rustle, settle in (5 minutes)
  - Establish minute taker for this meeting
  - Call roll
  - Accept previous minutes
  - Set agenda
    Proposed items below and others from the TC
  - general meeting, discussion, votes
  - review outstanding action item

Items for Agenda:
- What's needed for committee draft?
  This item may simply be a forward reference to the issues listed
  below. 
- Schedule
  Committee draft out of Newcastle meeting?
- Face to Face in Newcastle
  - Who is attending?
- What issues are open and how are they to be dealt with?
  - Issue 87: Conformance
    The change to resolve this issue was voted down.  What's needed to
    resolve? 
  - Issue 89: J2EE Inter-operability - JMS short circuit.
    There is a proposed XML representation for BTP state.
  - Issue 108: Participant and service identification.
    The change to resolve this issue has been voted and agreed.  Is
    there more that needs to be done?
  "Model issues"
  - Issue 24: The apparent complexity of the model is too great
    State diagrams for hazard and termination protocol needed?
  - Issue 25: Conformance (depends on issue 87)
  - Issue 66: Event diagram for termination protocol
  - Issue 73: ACID relaxation in overview
    There is no explicit comparison to traditional ACID transactions
    in the draft 0.9.5 text.
  Editorial comments
  a) Tree composition is top down only
  b) Compensatable versus cancellable as a BTP requirement

Regards,
TC Chair

William Z Pope
zpope@pobox.com 


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


Powered by eList eXpress LLC