Web Services Context Specification

(WS-Context) Version 1.0

Committee Specification 01

20 January 2006

Specification URIs:

This Version:

http://docs.oasis-open.org/ws-caf/ws-context/v1.0/CS01/wsctx.html

http://docs.oasis-open.org/ws-caf/ws-context/v1.0/CS01/wsctx.pdf

http://docs.oasis-open.org/ws-caf/ws-context/v1.0/CS01/wsctx.doc

Previous Version:

N/A

Latest Version:

http://docs.oasis-open.org/ws-caf/ws-context/v1.0/wsctx.html

http://docs.oasis-open.org/ws-caf/ws-context/v1.0/wsctx.pdf

http://docs.oasis-open.org/ws-caf/ws-context/v1.0/wsctx.doc

Technical Committee:

OASIS Web Services Composite Application Framework (WS-CAF) TC

Chair(s):

Eric Newcomer (eric.newcomer@iona.com)

Martin Chapman (martin.chapman@oracle.com)

Mark Little (mark.little@jboss.com)

 

Editor(s):

Mark Little (mark.little@jboss.com)

Eric Newcomer (eric.newcomer@iona.com)

Greg Pavlik (greg.pavlik@oracle.com)

 

Related work:

This specification is related to:

·       WS-Coordination Framework (part of OASIS WS-CAF)

·       WS-Transaction Management (part of OASIS WS-CAF)

Declared XML Namespace(s):

http://docs.oasis-open.org/ws-caf/2005/10/wsctx

Status

This document was last revised or approved by the OASIS Web Services Composite Application Framework (WS-CAF) TC on the above date. The level of approval is also listed above. Check the current location noted above for possible later revisions of this document. This document is updated periodically on no particular schedule.

Technical Committee members should send comments on this specification to the Technical Committee’s email list. Others should send comments to the Technical Committee by using the “Send A Comment” button on the Technical Committee’s web page at http://www.oasis-open.org/committees/ws-caf/.

For information on whether any patents have been disclosed that may be essential to implementing this specification, and any offers of patent licensing terms, please refer to the Intellectual Property Rights section of the Technical Committee web page (http://www.oasis-open.org/committees/ws-caf/ipr.php).

The non-normative errata page for this specification is located at http://www.oasis-open.org/committees/ws-caf/.

Abstract

Web services exchange XML documents with structured payloads. The processing semantics of an execution endpoint may be influenced by additional information that is defined at layers below the application protocol. When multiple Web services are used in combination, the ability to structure execution related data called context becomes important. This information is typically communicated via SOAP Headers. WS-Context provides a definition, a structuring mechanism, and service definitions for organizing and sharing context across multiple execution endpoints.

The ability to compose arbitrary units of work is a requirement in a variety of aspects of distributed applications such as workflow and business-to-business interactions. By composing work, we mean that it is possible for participants in an activity to be able to determine unambiguously whether or not they are participating in the same activity.

An activity is the execution of multiple Web services composed using some mechanism external to this specification, such as an orchestration or choreography. A common mechanism is needed to capture and manage contextual execution environment data shared, typically persistently, across execution instances.

 

Notices

OASIS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on OASIS's procedures with respect to rights in OASIS specifications can be found at the OASIS website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors or users of this specification, can be obtained from the OASIS Executive Director.

OASIS invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to implement this specification. Please address the information to the OASIS Executive Director.

Copyright © OASIS® 1993–2007. All Rights Reserved. OASIS trademark, IPR and other policies apply.

This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to OASIS, except as needed for the purpose of developing OASIS specifications, in which case the procedures for copyrights defined in the OASIS Intellectual Property Rights document must be followed, or as required to translate it into languages other than English.

The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.

This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

The names "OASIS", WS-Context and WS-CAF are trademarks of OASIS, the owner and developer of this specification, and should be used only to refer to the organization and its official outputs. OASIS welcomes reference to, and implementation and use of, specifications, while reserving the right to enforce its marks against misleading uses. Please see http://www.oasis-open.org/who/trademark.php for above guidance.


Table of contents

1    Note on terminology.................................................................................................................... 7

1.1 Namespace............................................................................................................................. 7

1.1.1 Prefix Namespace............................................................................................................ 7

1.2 Referencing Specifications...................................................................................................... 7

1.3 Precedence of schema and WSDL.......................................................................................... 7

2    Architecture................................................................................................................................. 8

2.1 Invocation of Service Operations............................................................................................. 8

2.2 Relationship to WSDL............................................................................................................. 9

2.3 Referencing and addressing conventions................................................................................ 9

3    Context..................................................................................................................................... 11

3.1 Activities................................................................................................................................ 12

3.2 Context information and SOAP............................................................................................. 13

4    Context Manager...................................................................................................................... 15

5    Context Service......................................................................................................................... 17

5.1 Status................................................................................................................................... 17

5.2 Context Service messages.................................................................................................... 17

begin...................................................................................................................................... 18

complete................................................................................................................................. 19

getStatus................................................................................................................................ 19

setTimeout.............................................................................................................................. 19