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

 


Help: OASIS Mailing Lists Help | MarkMail Help

bt-spec message

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


Subject: [bt-spec] Call for email vote: BT TC issue 54 - minor technical,HAZARD forms




This is a call for an email vote on the proposed resolution included
below for BT TC issue # 54
The voting period is one week, seven days, commencing Dec 3, 2001
and closing at your local midnight on Dec 10, 2001.

This email is sent to the 'bt spec' mail list.  Every voting member of
the TC must be on this list.  Voting members of the TC are asked to
vote by replying to this email and selecting one of
  ____ Yes
  ____ No
  ____ Abstain

and then sending their reply to the chair and the recording secretary.
The reply may also go to the 'bt spec' mail list or other destinations
at the voters discretion. 
  chair: zpope@pobox.com
  secretary: peter.furniss@choreology.com
  spec list: bt-spec@lists.oasis-open.org

Issue URL
----------
http://www.oasis-open.org/committees/business-transactions/issues.html#Issue54

Issue
------
Hazard forms
What are "forms" and how do they fit with the protocol and message
set? 

Draft 0.9, Page 48 talks about "hazard forms". Where do these
"forms" come in?  Are they only for discussing aspects of the
protocol, or do they occur in the message set?  It would be useful if 
this form of HAZARD information (mixes/possible) was in the message
set.


Proposed Resolution
--------------------

In abstract message section on HAZARD add row to HAZARD parameter list  

  "level, mixed/possible"

Add paragraph explaining 

  "'level' indicates, with value "mixed" that a mixed condition has
  definitely occurred; or, with value "possible" that it is unable to
  determine whether a mixed condition has occurred or not." 

In xml for hazard, add attribute 

  level="mixed|possible"


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