About the Web Services Addressing 1.0 Core and SOAP Binding
Recommendations
The Web Services Addressing 1.0 Core and SOAP Binding Recommendations have
been produced by the W3C Web Services
Addressing Working Group as part of the Web
Services Activity of the W3C.
This document lists in reverse chronological order the
known errata to those two specifications. The errata are numbered,
classified as Substantive or Editorial, and listed in reverse
chronological order of their date of publication in each
category.
Each entry has the following
information:
- A unique entry number
- The date it was added to the errata page.
- The section referred to.
- A description of the problem and correction if applicable. Changes
to the text of the spec are indicated thus:
deleted text,
new text, modified text
.
- A rationale for making the change (not required for editorial errata).
Please send comments about this document to the public mailing list public-ws-addressing-comments@w3.org.
A public
archive is available.
Substantive corrections are proposed by the Web Services Addressing
Working Group, which has consensus that they are appropriate;
they are not to be considered normative until approved by a Call
for Review of Proposed Corrections or a Call
for Review of an Edited Recommendation.
Substantive errata
None at present
Editorial errata
E01
- Section 6.4.1 Invalid Addressing Header
-
Change the description of [Details] as follows:
[Details] either a <wsa:ProblemHeader> element
that conveys a copy of the offending header or a
<wsa:ProblemHeaderQName> element that conveys the
QName of the root element of the offending header.
- Section 6.4.1.6 wsa:ActionMismatch
-
Change the paragraph as follows:
Specifies that the [action] and SOAPAction for the
message did not match, [Details] MAY contain a
<wsa:ProblemAction> element in addition to the
<wsa:ProblemHeader> element or
<wsa:ProblemHeaderQName> element.
- Rationale
- The
<wsa:ProblemHeader> fault detail
element was removed during the Candidate Recommendation
phase.
Document maintained by the Web Services Addressing Working Group