URI Scheme for Java(tm) Message Service 1.0
draft-merrick-jms-uri-12
Yes
(Alexey Melnikov)
No Objection
(Adrian Farrel)
(Dan Romascanu)
(Gonzalo Camarillo)
(Peter Saint-Andre)
(Robert Sparks)
(Ron Bonica)
(Russ Housley)
(Sean Turner)
(Stewart Bryant)
Note: This ballot was opened for revision 12 and is now closed.
Alexey Melnikov Former IESG member
(was Discuss, Yes)
Yes
Yes
()
Unknown
Adrian Farrel Former IESG member
No Objection
No Objection
()
Unknown
Dan Romascanu Former IESG member
No Objection
No Objection
()
Unknown
Gonzalo Camarillo Former IESG member
No Objection
No Objection
()
Unknown
Lars Eggert Former IESG member
No Objection
No Objection
(2011-01-17)
Unknown
INTRODUCTION, paragraph 4: > The syntax of this 'jms' URI is not compatible with any known current > vendor implementation, but the expressivity of the format should > permit all vendors to use it. So are there vendor implementations of 'jms' already? If yes, what it the value in publishing a specification that is not compatible with any of them? Or do we have an indication that the vendors will adopt this spec?
Peter Saint-Andre Former IESG member
No Objection
No Objection
()
Unknown
Robert Sparks Former IESG member
No Objection
No Objection
()
Unknown
Ron Bonica Former IESG member
No Objection
No Objection
()
Unknown
Russ Housley Former IESG member
No Objection
No Objection
()
Unknown
Sean Turner Former IESG member
No Objection
No Objection
()
Unknown
Stewart Bryant Former IESG member
No Objection
No Objection
()
Unknown