< Home | Return to Ballot listing

Ballot Details    TC Member Ballot View
JMS Mapping Version 1.0 effort JMS 1.1 and core AMQP only

Do you support limiting work on the first version of "Advanced Message Queuing Protocol (AMQP) JMS Mapping" to address JMS 1.1 and core AMQP capabilities, leaving JMS 2.0 and extended AMQP for later?

The scope of the current JMS Mapping effort in the OASIS AMQP Bindings and Mappings (BINDMAP) Technical Committee was under discussion during the TC meeting held Tuesday April 21, 2015. There was general consensus to limit work on the first version of the specification to address JMS 1.1 and core AMQP capabilities required. This would leave JMS 2.0 and extended AMQP capabilities (so-called "access all AMQP capabilities from JMS") work for possible follow-on efforts after the first version of the document is completed.

Because the TC meeting was not quorate, no vote on this could be taken. On Tuesday April 21, 2015 Bill Cox made a motion via the TC email list to move this question to an electronic ballot. Jakub Scholz seconded the motion on Thursday April 23.

 [ ]  Yes
 [ ]  No
 [ ]  Abstain
Opening:   Thursday, 23 April 2015 @ 10:00 am EDT
Closing:   Thursday, 30 April 2015 @ 10:00 am EDT
Group:   OASIS Advanced Message Queuing Protocol (AMQP) Bindings and Mappings (AMQP-BINDMAP) TC
Ballot has closed.

Referenced Items
Name Type Date Action

Voting Details

Voting Summary

Options with highest number of votes are bold

Option # Votes % of Total
Yes 8 100%
No 0 0%
Abstain 0
Eligible members who have voted: 8 of 8 100%
Eligible members who have abstained: 0 of 8 0%
Eligible members who have not voted: 0 of 8 0%

Voting Details

Voter Company VoteReference Document and/or Comment
Jakub Scholz
Deutsche Boerse AG
William Cox
Steve Huston
Rob Godfrey
JPMorgan Chase Bank, N.A.
Robert Gemmell
Red Hat
Timothy Bish
Red Hat
Alex Kritikos
Software AG, Inc.
Wolf Tombe
US Department of Homeland Security