[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Proposed Charter for AMQP Bindings and Mappings (AMQP-BINDMAP) TC
To OASIS Members: A draft TC charter has been submitted to establish the OASIS Advanced Message Queuing Protocol (AMQP) Bindings and Mappings (AMQP-BINDMAP) Technical Committee. In accordance with the OASIS TC Process Policy section 2.2: (https://www.oasis-open.org/policies-guidelines/tc-process#formation) the proposed charter is hereby submitted for comment. The comment period shall remain open until 11:45 pm ET on 15 October 2012. OASIS maintains a mailing list for the purpose of submitting comments on proposed charters. Any OASIS member may post to this list by sending email to: oasis-charter-discuss@lists.oasis-open.org. All messages will be publicly archived at: http://lists.oasis-open.org/archives/oasis-charter-discuss/. Members who wish to receive emails must join the group by selecting "join group" on the group home page: http://www.oasis-open.org/apps/org/workgroup/oasis-charter-discuss/. Employees of organizational members do not require primary representative approval to subscribe to the oasis-charter-discuss e-mail. A telephone conference will be held among the Convener, the OASIS TC Administrator, and those proposers who wish to attend within four days of the close of the comment period. The announcement and call-in information will be noted on the OASIS Charter Discuss Group Calendar. We encourage member comment and ask that you note the name of the proposed TC (AMQP-BINDMAP) in the subject line of your email message. --- (1) Charter of the Technical Committee (1)(a) Name of the TC OASIS Advanced Message Queuing Protocol (AMQP) Bindings and Mappings (AMQP-BINDMAP) Technical Committee (TC) (1)(b) 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. (1)(c) 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: o Provide a standard mapping between JMS and AMQP types. o Provide a standard mapping between the JMS Message model and the AMQP message model. o 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: o Define the wire format for AMQP frames on a WebSocket connection. o 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. (1)(d) 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. (1)(e) 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. (1)(f) Anticipated Audience Anticipated audience for this work includes AMQP users and middleware implementers. (1)(g) 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 (2) Non-normative information regarding the startup of the TC (2)(a) Similar Work There is no similar work being done in OASIS or to our knowledge in any other organizations. (2)(b) Date, Time, and Location of First Meeting The first meeting of the TC will be held by teleconference on November 27, 2012 during 8-9am PT. This meeting will be sponsored by Microsoft. (2)(c) On-Going Meeting Plans & Sponsors It is anticipated that the TC will meet weekly via teleconference and if needed meet face-to-face every 2-3 months at a time and location to be determined by the TC members. At its first meeting, the TC will setup an on-going meeting schedule and determine who will sponsor these meetings. (2)(d) Proposers of the TC Andreas Moravec, Andreas.Moravec@deutsche-boerse.com, Deutsche Boerse AG Mark Blair, mark.blair@credit-suisse.com, Credit Suisse Prasad Yendluri, prasad.yendluri@softwareag.com, Software AG Andreas Mueller, am@iit.de, IIT Software GmbH Winston Bumpus, wbumpus@vmware.com, VMware. Inc. Abbie Barbir, abbie.barbir@bankofamerica.com, Bank of America Mark Little, mlittle@redhat.com, Red Hat Ram Jeyaraman, Ram.Jeyaraman@microsoft.com, Microsoft Angus Telfer, art@inetco.com, INETCO Systems Limited. Allan Beck, allan.beck@jpmorgan.com, JPMorgan Chase Larry Neumann, Larry.Neumann@SolaceSystems.com, Solace Systems. (2)(e) Statement of Support Andreas Moravec, andreas.moravec@deutsche-boerse.com Deutsche Boerse AG: As the Primary Representative for Deutsche Boerse AG, I support the goals of the proposed OASIS AMQP Bindings and Mappings Technical Committee (AMQP-BINDMAP) as described in this Charter. Mark Blair, mark.blair@credit-suisse.com Credit Suisse: As the primary representative for Credit Suisse, I support the goals of the proposed OASIS Advanced Message Queuing Protocol (AMQP) Bindings and Mappings Technical Committee as described in this Charter. Prasad Yendluri, prasad.yendluri@softwareag.com Software AG: As the primary representative for Software AG, I support the goals of the proposed OASIS Advanced Message Queuing Protocol (AMQP) Bindings and Mappings Technical Committee as described in this Charter. Andreas Mueller, am@iit.de IIT Software GmbH: As the Primary Representative for IIT Software GmbH, I support the goals of the proposed OASIS Advanced Message Queuing Protocol (AMQP) Bindings and Mappings Technical Committee as described in this Charter. Winston Bumpus, wbumpus@vmware.com Director of Standards Architecture, VMware. Inc.: As the Primary Representative for VMware, Inc., I support the goals of the proposed OASIS Advanced Message Queuing Protocol (AMQP) Bindings and Mappings Technical Committee as described in this Charter. Abbie Barbir, abbie.barbir@bankofamerica.com Bank of America: As the primary representative for Bank of America, I support the goals of the proposed OASIS Advanced Message Queuing Protocol (AMQP) Bindings and Mappings Technical Committee as described in this Charter. Mark Little, mlittle@redhat.com Red Hat: As the Primary Representative for Red Hat, I support the goals of the proposed OASIS Advanced Message Queuing Protocol (AMQP) Bindings and Mappings Technical Committee as described in this Charter. Ram Jeyaraman, Ram.Jeyaraman@microsoft.com Microsoft: As the Primary Representative for Microsoft, I am pleased to offer our support for the creation of this Technical Committee. Angus Telfer, art@inetco.com CTO of INETCO Systems Limited: As the primary representative for INETCO Systems Limited, I support the goals of the proposed OASIS Advanced Message Queuing Protocol (AMQP) Bindings and Mappings Technical Committee as described in this Charter. Allan Beck, allan.beck@jpmorgan.com JPMorgan Chase: As the Primary Representative for JPMorgan Chase, I support the goals of the proposed OASIS Advanced Message Queuing Protocol (AMQP) Bindings and Mappings Technical Committee as described in the Charter. Larry Neumann, Larry.Neumann@SolaceSystems.com Solace Systems: As the Primary Representative for Solace, I support the goals of the proposed OASIS Advanced Message Queuing Protocol (AMQP) Bindings and Mappings Technical Committee as described in this Charter. (2)(f) TC Convener The TC Convener for the first meeting will be Laurie Bryson. (2)(g) Affiliation to Member Section It is intended that this TC will be affiliated with the AMQP Member Section. (2)(h) List of anticipated contributions None (2)(i) Frequently Asked Questions (FAQ) relating to the planned scope of the TC None (2)(j) Proposed working title and acronym for the specification(s) to be developed by the TC None /chet ---------------- Chet Ensign Director of Standards Development and TC Administration OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]