Call to Vote: Ballot for OASIS Standard - Advanced Message Queuing Protocol (AMQP) V1.0

The Advanced Message Queueing Protocol (AMQP) TC members [1] have approved submitting the following Candidate OASIS Standard to the OASIS membership for a membership vote for OASIS Standard:

OASIS Advanced Message Queueing Protocol (AMQP) Version 1.0
Candidate OASIS Standard 01
07 August 2012

This is a call to the primary or alternate representatives of OASIS Organizational Members to vote. This Committee Specification was approved by the Technical Committee and was submitted for the required 60-day public review. All requirements of the OASIS TC Process having been met, the Candidate OASIS Standard is now submitted to the voting representatives of OASIS organizational members.

-- Voting Details --

The ballot opens at 00:00 am U.S. Eastern time on 15 October 2012 and closes at 11:59 pm U.S. Eastern time on 29 October 2012. You can access the ballot to cast your vote at:

Internal OASIS link: https://www.oasis-open.org/apps/org/workgroup/voting/ballot.php?id=2300

Publicly visible link: https://www.oasis-open.org/committees/ballot.php?id=2300

The minimum number of affirmative votes required to approve this ballot is 48 (15% of 320).

Each OASIS organizational member has one vote. OASIS members should ensure that their organization's voting representative votes according to the organization's wishes. If you do not know the name of your organization's voting representative is, go to the My Account page at

http://www.oasis-open.org/members/user_tools

then click the link for your Company (at the top of the page) and review the list of users for the name designated as "Primary".

-- Information about the Candidate OASIS Standard and the Advanced Message Queueing Protocol (AMQP) TC --

AMQP (Advanced Message Queuing Protocol) 1.0 is an efficient, reliable, wire level messaging protocol supporting common middleware messaging interaction patterns: messaging, request/response, publish/subscribe, transactions, and store and forward. It allows middleware applications to communicate with each other without having to have the same infrastructure on both ends (i.e. it provides vendor neutral communications). Like all communication protocols, AMQP describes the message syntax and sequence for performing their different assigned tasks. AMQP is capable of being used in both synchronous (point-to-point) and asynchronous (broker based) architectures and is independent of any particular broker architecture. AMQP is of special importance in providing enterprise and cloud messaging services.

Reliance on private network infrastructures and/or proprietary messaging protocols is no longer able to meet the reliability and agility needed in the emergent "Business Social Enterprise" of today's global market place. What is required is an information exchange protocol that directly addresses these requirements and elevates business interactions above the technical details of managing byte stream flows to a level where business interactions are based on the unit of work, the message.

AMQP 1.0 offers organizations an easier, more secure approach to passing real-time data streams and business transactions. The goal of AMQP is to ensure information is safely and efficiently transported between applications, among organizations, across distributed cloud computing environments, and within mobile infrastructures. AMQP avoids proprietary technologies, offering the potential to lower the cost of enterprise middleware software integrations through open interoperability. By enabling a commoditized, multi-vendor ecosystem, AMQP seeks to create opportunities for transforming the way business is done in the Cloud and over the Internet.

AMQP 1.0 Committee Specification 01 was approved by the TC on 18 July 2012. The TC received five Statements of Use from IIT Software GmbH, INETCO Systems Ltd., Microsoft, Red Hat and StormMQ [2].

-- URIs --

The prose specification document and related files are available here. Please note that AMQP is a multi-part specification. The HTML document provides the overview and links to the other parts of the Candidate OASIS Standard. The PDF document is a complete copy containing all parts of the Candidate OASIS Standard:

XML (Authoritative):
http://docs.oasis-open.org/amqp/core/v1.0/cos01/amqp-core-overview-v1.0-...

HTML:
http://docs.oasis-open.org/amqp/core/v1.0/cos01/amqp-core-overview-v1.0-...

PDF:
http://docs.oasis-open.org/amqp/core/v1.0/cos01/amqp-core-complete-v1.0-...

ZIP distribution file (complete):

For your convenience, OASIS provides a complete package of the prose specification and related files in a ZIP distribution file. You can download the ZIP file here:

http://docs.oasis-open.org/amqp/core/v1.0/cos01/amqp-core-cos01.zip

-- Additional information --

[1] OASIS Advanced Message Queueing Protocol (AMQP) TC
http://www.oasis-open.org/committees/amqp/

TC Charter
https://www.oasis-open.org/committees/amqp/charter.php

[2] Statements of Use:
Links to Statements of Use
IIT Software GmbH: http://lists.oasis-open.org/archives/amqp/201207/msg00049.html
INETCO Systems Ltd.: http://lists.oasis-open.org/archives/amqp/201207/msg00054.html
Microsoft: http://lists.oasis-open.org/archives/amqp/201207/msg00053.html
Red Hat: http://lists.oasis-open.org/archives/amqp/201207/msg00060.html
StormMQ: http://lists.oasis-open.org/archives/amqp/201207/msg00044.html

Associated TC: 
Advanced Message Queuing Protocol (AMQP)
Associated MS: 
AMQP