Table of contents

[Home] [W3C Specs]

1.1 Notational Conventions

2 Predefined Message Exchange Patterns

2.1 Fault Propagation Rules

2.1.1 Fault Replaces Message

2.1.2 Message Triggers Fault

2.1.3 No Faults

2.2 Message Exchange Patterns

2.2.1 In-Only

2.2.2 Robust In-Only

2.2.3 In-Out

2.2.4 In-Optional-Out

2.2.5 Out-Only

2.2.6 Robust Out-Only

2.2.7 Out-In

2.2.8 Out-Optional-In

3 Predefined Features

3.1 Application Data Feature

3.1.2 Operation

3.1.3 AD/data Property

3.1.4 Description

3.1.5 The ad:mustUnderstand Attribute

3.2 Application Data Module

3.2.1 Features Implemented

3.2.2 Operation

3.3 Application data serialization as HTTP headers

3.3.2 Features Implemented

3.3.3 Operation

4.1 Normative References

4.2 Informative References

Appendices

A Acknowledgements

B.1 Changes

1.1 Notational Conventions

Notational Conventions

The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].

[Next Chapter] [Home]