Charter of the SOAP-JMS Binding Working Group

The mission of the SOAP-JMS Binding Working Group, part of the Web Services Activity, is to produce a W3C Recommendation for how SOAP should bind to a transport that supports the Java™ Message Service (JMS) api by refining the “SOAP over Java™ Message Service 1.0” Member Submission. In the case of SOAP 1.2 this binding must use the SOAP Protocol Binding Framework defined by the XML Protocol Working Group.

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

End date	30 June 2012
Confidentiality	Proceedings are Public
Initial Chair	Roland Merrick (IBM)
Initial Team Contact (FTE %: 15)	Yves Lafon, Philippe Le Hégaret
Usual Meeting Schedule	Teleconferences: Weekly Face-to-face meetings will be held as needed.

Scope

The main purpose of this work is to ensure interoperability between the implementations of different Web services vendors. It must be possible to change the messaging layer that underpins the JMS api without affecting an application. It should also enable non-vendors to implement their own Web services for part of their infrastructure, and to have this interoperate with vendor provided Web services. It should enable implementers to write a SOAP-JMS implementation that will interoperate with other SOAP-JMS implementations, and that will not be dependent on any specific JMS implementation.

The Working Group is responsible for producing a W3C Recommendation for how SOAP should bind to a transport that supports the Java Message Service (JMS) api by refining the “SOAP over Java™ Message Service 1.0” Member Submission. The specification must describe a binding for both SOAP 1.1 and SOAP 1.2. In the case of SOAP 1.2 this binding must use the SOAP Protocol Binding Framework defined by the XML Protocol Working Group. In the case of SOAP 1.1 this binding must adopt the same basic approach as that taken for SOAP 1.2 even though SOAP 1.1 did not explicitly define a "Protocol Binding Framework".

The specification must describe how to construct and interpret the JMS messages used to transport the SOAP envelope.

The specification must describe how to deal the request/response and one-way WSDL 1.1 MEPs. It should also describe how to deal with WSDL 2.0 MEPs defined in section 2.3 of the WSDL 2.0 Adjuncts specification.

The Working Group must also describe how the binding may be used with WSDL 1.1 and WSDL 2.0.

The description of a JMS destination should also consider using the “IRI Scheme for Java(tm) Message Service 1.0” defined by the IETF.

Out of Scope

The following items are not within the scope of work of this Working Group:

It does NOT provide any mechanism for interoperation between two different messaging systems that both support the JMS api, i.e. it does NOT define any (wire) format for SOAP-JMS messages.
It does NOT define how the Web services themselves will be presented to the application programmer. For example, it does not describe how the programmer will characterise a one-way message.

Success Criteria

The success of the SOAP-JMS Binding Working Group will be judged on how well it fulfills the above objectives in terms of the deliverables and milestones set out below. It is expected to demonstrate interoperable implementations during the Call for Implementations step.

Deliverables

Technical Reports

The following deliverable will be created under the W3C Patent Policy:

A W3C Recommendation for SOAP-JMS Binding

Other Deliverables

The Working Group will maintain:

a test suite
an implementation report showing, for each tested product, the tests that are passed.

The Working Group may also:

Author additional non-normative material that describes how to use the SOAP-JMS Binding in conjuction with Web services standards including Web Services Reliable Messaging, Web Services Addressing and Security. This material may be in the form of a primer.
Author additional non-normative material that describes how to use JMS Topics with the SOAP-JMS Binding.

Milestones

Milestones
Specification	FPWD	LC	CR	PR	Rec
Note: The group will document significant changes from this initial schedule on the group home page.
SOAP-JMS Binding	June 2008	Sep 2008	Dec 2008	Mar 2009	Apr 2009

The Group will maintain the W3C Recommendation after April 2009 and until the end of December 2010. It is expected that there will be only teleconferences if needed after April 2009 to deal with issues related to the W3C Recommendation or the test suite.

Dependencies and Liaison

The following is a list of known dependencies and liaisons with other W3C groups at the time this charter was written. Liaison with other W3C groups can take advantage of a broad range of mechanisms such as cross membership, reviews of drafts produced by other groups, joint meetings etc., and whenever appropriate, the SOAP-JMS Binding Working Group will also coordinate with groups not listed here.

Dependencies

Liaisons

XML Protocol Working Group: The SOAP-JMS Binding Working Group will coordinate its work to ensure that it complies with the framework defined by the XML Protocol Working Group.

Relationship to External Groups

The SOAP-JMS Binding Working Group will coordinate with external groups on issues of mutual importance. At the time of writing the groups being coordinated with were:

The Internet Engineering Task Force (IETF): On the related topic of a JMS IRI Scheme.

About this Charter

This charter for the SOAP-JMS Binding Working Group has been created according to section 6.2 of the Process Document. In the event of a conflict between this document or the provisions of any charter and the W3C Process, the W3C Process shall take precedence.