[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: [business-transaction] Email vote - Issue 66 - voting ends Tues May 30- REPLACES PREVIOUS ISSUE 66 BALLOT
The list of diagrams in the first ballot was incomplete. This is a call for an email vote on the proposed issue resolutions included below. The voting period is one week, seven days, commencing April 23, 2002 and closing at your local midnight on Tuesday April 30, 2002. To vote the voting member must send an email to the chair and the recording secretary. chair: zpope@pobox.com secretary: peter.furniss@choreology.com No need to include the text of this email. Just indicate: a) who is voting, b) each issue being voting on, and c) the vote for each issue (YES, NO, ABSTAIN). Feel free to add comments, especially for "NO" votes. Issue list URL ---------- http://www.oasis-open.org/committees/business-transactions/issues.html Issues Issue 66: Event diagram for termination protocol -------------------------------------------------------------------- Issue 66: Event diagram for termination protocol -------------------- Description For both Atom and Cohesion case, it might be helpful to add an event diagram that shows the type of messages sent in the 1st and 2nd phase in different scenarios. -------------------- Proposed Resolution Some of the existing diagrams, figure 9 and figure 16 (as numbered in 0.9.5.1), in the model section include the termination sequence, and figure 13 shows the state sequence for a Composer or Coordinator. Draft 0.9.5.1 contains three additional diagrams to those in 0.9.5, with explanatory paragraphs. The new figure 15 shows a termination sequence for a composer, figure 17 shows a termination sequence including a contradiction. The new figure 14 shows the state changes, and the triggering events for a Sub-coordinator and Sub-composer. -------------------- Supporting Material https://www.oasis-open.org/committees/business-transactions/documents/2002-04-22 .BTP_draft_0.9.5.1.pdf Pertinent Figures in 0.9.5.1 Figure 9 A conventional message sequence for a simple transaction Figure 14 Termination sequence for a composer Figure 15 State diagram for Sub-coordinator or Sub-composer Figure 16 A message sequence showing the "one-shot" optimisation Figure 17 Message sequence showing contradiction, reported with HAZARD ==================================================================== BT TC Voting Rules ------------------- Only eligible members of the TC can vote. Every member of a TC has a single vote. Organizations do not vote in TCs. Proxies are not allowed in TC voting. Votes on technical and editorial issues pass when a majority votes in favor. The majority is more than half of the members who vote on the issue, quorum is required. Abstention are recorded and count towards quorum. If a majority is not achieved the motion will be rejected. If quorum is not achieved it shall be as if the motion was not proposed and the vote did not happen. The chair may propose draft resolutions to the members of the TC for discussion by mail, to entertain friendly amendments to such draft resolutions and make such changes as shall seem most likely to gain general assent of the members of the TC, to put such resolutions as seem to have gained majority assent to the members of the TC for a vote by mail, and to conduct votes on such resolutions by mail. 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