OASIS Open: Committees

Approve the WS-Reliable Messaging 1.1 Specification Set (WSRM, WSRMP, WSMC)

Shall the specification set listed below be approved as a Committee Specification by the OASIS Web Services Reliable Exchange (WS-RX) TC and submitted to TC Administration for OASIS Standard Vote?

This vote requires at least 2/3 of all WS-RX voting members to vote in the affirmative.

The candidate Committee Specification documents are located at:
(zip archive of specification set)
http://www.oasis-open.org/committees/download.php/22828/WSRX%20CD7.zip

WS-ReliableMessaging
http://www.oasis-open.org/committees/download.php/22825/wsrm-1.1-spec-cd-07.pdf
WS-ReliableMessaging Policy
http://www.oasis-open.org/committees/download.php/22826/wsrmp-1.1-spec-cd-07.pdf
WS-MakeConnection
http://www.oasis-open.org/committees/download.php/22827/wsmc-1.0-spec-cd-03.pdf

[ ]	Yes
[ ]	No
[ ]	Abstain

Opening:		Wednesday, 7 March 2007 @ 07:00 pm EST
Closing:		Thursday, 15 March 2007 @ 12:45 am EDT
Group:		OASIS Web Services Reliable Exchange (WS-RX) TC

Ballot has closed.

Voting Details

Voting Summary

Options with highest number of votes are bold

Option	# Votes	% of Total
Yes	26	72%
No	10	28%
Abstain	2

Eligible members who have voted:	36 of 39	92%
Eligible members who have abstained:	2 of 39	5%
Eligible members who have not voted:	1 of 39	3%

Voting Details

Voter	Company	Vote	Reference Document and/or Comment
Charlton Barreto	Adobe Systems	Yes
Dave Orchard	BEA Systems, Inc.	Yes
Gilbert Pilz	BEA Systems, Inc.	Yes
Lei Jin	BEA Systems, Inc.	Yes
Ian Jones	BTplc	Yes
Kazunori Iwasa	Fujitsu Limited	Abstain	I prefer TC to resolve interoperability issue how the Acknowledgement message should be returned on the underlying protocols. The spec or other TC document should mention underlying protocol binding o
Tom Rutt	Fujitsu Limited	No	both specs WS-ReliableMessaging Policy http://www.oasis-open.org/committees/download.php/22826/wsrmp-1.1-spec-cd-07.pdf WS-MakeConnection http://www.oasis-open.org/committees/download.php/22827/ws
Jacques Durand	Fujitsu Limited	No	We have discussed this further internally and decided for a NO vote: a better alternative would be for the TC to approve an amended version of the two specs with corrected namespace as CS for Member V
Eisaku Nishiyama	Hitachi, Ltd.	Yes
Nobuyuki Yamamoto	Hitachi, Ltd.	Yes
Robert Freund	Hitachi, Ltd.	Yes
Rich Salz	IBM	Yes
Christopher Ferris	IBM	Yes
Peter Niblett	IBM	Yes
Doug Davis	IBM	Yes
Matt Lovett	IBM	Yes
Charles Le Vay	IBM	Yes
Paul Cotton	Microsoft Corporation	No
Colleen Evans	Microsoft Corporation	No
Stefan Batres	Microsoft Corporation	No
Marc Goodner	Microsoft Corporation	No	There is an obvious error in the WS-Policy ns reference. We cancelled our last ballot for errors in the specification that were more minor than an incorrect namespace. Now the Policy CR we are referen
Doug Bunting	Microsoft Corporation	No	We cancelled our last ballot for errors in the specification that were more minor than an incorrect namespace. First, we learn the schema reference to the Policy namespace is incorrect. Now, the Polic
Chouthri Palanisamy	NEC Corporation	Yes
Paul Knight	Nortel Networks Limited	Yes
Lloyd Burch	Novell	Yes
Steve Carter	Novell	Yes
Martin Chapman	Oracle Corporation	Yes
jeff mischkinsky	Oracle Corporation	Yes
Eric Rajkovic	Oracle Corporation	Yes
Anish Karmarkar	Oracle Corporation	Yes
Ashok Malhotra	Oracle Corporation	Yes
Mark Little	Red Hat	Yes
Sanjay Patil	SAP AG	No	It would be prudent to get the remaining issues satisfactorily addressed before going out for OASIS member approval.
Mike Grogan	Sun Microsystems	No
Pete Wenzel	Sun Microsystems	No	As others have noted, the specification of the "wsp" namespace URI in WSRMP and WSMC is incorrect. This is a significant error that must be fixed prior to their advancement. (My preference would be
Shivajee Samdarshi	Tibco Software Inc.	--
Dan Leshchiner	Tibco Software Inc.	Yes
Paul Fremantle	WSO2	Abstain	I have changed my vote to abstain. While I do not take the same reading of the reference to Policy 1.5, I feel that an updated looser reference to both policy specs would more closely address the inte
Lily Liu	webMethods, Inc.	Yes