1. Name of the TC

   OASIS Advanced Message Queuing Protocol (AMQP) Bindings and Mappings (AMQP-BINDMAP) Technical Committee (TC)

2. Statement of Purpose

   The purpose of the AMQP Bindings and Mappings (AMQP-BINDMAP) TC is to define bindings of AMQP 1.0 core protocol [1] to underlying transports other than TCP, to define mappings of the AMQP 1.0 core protocol to existing well-known programming APIs, and to define representations of the AMQP 1.0 message format in existing well-known languages.

3. Scope of Work

   The TC will accept relevant proposals for defining bindings of AMQP 1.0 core protocol [1] to underlying transports other than TCP, mappings of the AMQP 1.0 core protocol [1] to existing well-known programming APIs, and representations of the AMQP 1.0 message format in existing well-known languages, and work to produce OASIS Standard specifications for them, including necessary XML renderings.

   Examples include, but are not limited to:

   • A mapping between the JMS API v1.1 and AMQP v1.0 which would:
     • Provide a standard mapping between JMS and AMQP types.
     • Provide a standard mapping between the JMS Message model and the AMQP message model.
     • Define which extensions capabilities (if any) to the core AMQP specification are necessary for an AMQP container to act as a full JMS Message Provider to any JMS client written in accordance with the AMQP JMS Mapping specification.
   • A binding of AMQP connection semantics to the WebSocket protocol which would:
     • Define the wire format for AMQP frames on a WebSocket connection.
     • Detail the relationship between the core AMQP security model and the authentication mechanisms associated with an HTTP session.

   Bindings of AMQP to alternative transports will preserve, the semantics associated with the performatives defined in the AMQP 1.0 core protocol [1], and the encoding of AMQP messages.

   Mappings of the AMQP 1.0 core protocol [1] to programming APIs will not rely on extensions to the AMQP 1.0 core protocol [1], except through the use of the defined extension capability registries. Any such extensions will be kept to a minimum, will be generally meaningful and not restricted to the use of any given API mapping.

   Any work not reasonably covered by the Scope of Work is deemed to be out of scope.

4. Deliverables

   The TC will produce OASIS Standard versions of such AMQP binding and mapping specifications, including representations of the AMQP 1.0 message format in existing well-known languages, and may advance those specifications to ISO/IEC JTC 1 through the JTC 1 PAS Transposition Process. The TC expects to produce the OASIS Standard version of some of those specifications within 18 months from its first meeting.

   The TC will maintain previously adopted deliverables and provide minor revisions of those deliverables, in order to clarify ambiguities, inconsistencies, and obvious errors.

5. IPR Mode

   This TC will operate under RF on RAND Terms IPR mode as defined in the OASIS Intellectual Property Rights (IPR) Policy effective 21 June 2012.

6. Anticipated Audience

   Anticipated audience for this work includes AMQP users and middleware implementers.

7. Language

   TC business will be conducted in English.

References

[1] OASIS AMQP Version 1.0 Specification
http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-complete-v1.0.pdf