qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Huston <shus...@riverace.com>
Subject FW: [members] Call for Participation: AMQP Bindings and Mappings TC
Date Wed, 24 Oct 2012 18:23:10 GMT
FYI.

On 10/24/12 1:53 PM, "Chet Ensign" <chet.ensign@oasis-open.org> wrote:

>OASIS members & interested parties,
>
>A new OASIS technical committee is being formed. The OASIS Advanced
>Message Queuing Protocol Bindings and Mappings (AMQP-BindMap) Technical
>Committee has been proposed by the members of OASIS listed in the charter
>below. The TC name, statement of purpose, scope, list of deliverables,
>audience, IPR mode and language specified in the proposal will constitute
>the TC's official charter. Submissions of technology for consideration by
>the TC, and the beginning of technical discussions, may occur no sooner
>than the TC's first meeting.
>
>The eligibility requirements for becoming a participant in the TC at the
>first meeting are:
>
>(a) you must be an employee or designee of an OASIS member organization
>or an individual member of OASIS, and?
>(b) you must join the Technical Committee, which members may do by using
>the Roster "join group" link on the TC's web page at [a].
>
>To be considered a voting member at the first meeting:
>
>(a) you must join the Technical Committee at least 7 days prior to the
>first meeting (on or before 20 November 2012); and
>?(b) you must attend the first meeting of the TC, at the time and date
>fixed below (27 November 2012).
>
>Participants also may join the TC at a later time. OASIS and the TC
>welcomes all interested parties.
>
>Non-OASIS members who wish to participate may contact us about joining
>OASIS [b]. In addition, the public may access the information resources
>maintained for each TC: a mail list archive, document repository and
>public comments facility, which will be linked from the TC's public home
>page at [c].
>
>Please feel free to forward this announcement to any other appropriate
>lists. OASIS is an open standards organization; we encourage your
>participation.
>
>----------?
>[a] https://www.oasis-open.org/apps/org/workgroup/amqp-bindmap/ ?
>[b] See http://www.oasis-open.org/join/?
>[c] http://www.oasis-open.org/committees/amqp-bindmap/
>
>--- 
>
>(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:
>
>   - 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.
>
>(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 Director of Standards Architecture,
>VMware. Inc.
>
>Abbie Barbir, 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 CTO of 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.
>
>(f) TC Convener
>
>The TC Convener for the first meeting will be Laurie Bryson,
>laurie.m.bryson@jpmorgan.com, JPMorgan Chase.
> 
>(g) Affiliation to Member Section
>
>It is intended that this TC will be affiliated with the AMQP Member
>Section.
> 
>(h) List of anticipated contributions
>None
> 
>(i) Frequently Asked Questions (FAQ) relating to the planned scope of the
>TC
>None
> 
>(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
>
>
>
>
>
>
>---------------------------------------------------------------------
>
>This email list is used solely by OASIS for official consortium
>communications.
>
>Opt-out requests may be sent to member-services@oasis-open.org, however,
>all members are strongly encouraged to maintain a subscription to this
>list.
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org


Mime
View raw message