Error in reflection of Issue 030 into WS-AT?

[Alastair Green <alastair.green@choreology.com>]

I believe that the following lines from WS-AT WD 10 should not be there, and contradict the final resolution of Issue 030:

ll. 507 - 509.

Fault messages

·         MUST include a [relationship] header, specifying the MessageID from the Notification message that generated the fault condition.

Minus change markings, the final resolution of 030 reads:

Both terminal and non-terminal notification messages

·         MUST include a [reply endpoint] property whose [address] property is set to 'http://www.w3.org/2005/08/addressing/none’

Notification messages are addressed by both coordinators and participants using the Endpoint References initially obtained during the Register-RegisterResponse exchange. If a [source endpoint] property is present in a notification message, it MAY be used by the recipient. For example, in cases where a Coordinator or Participant has forgotten a transaction that is completed and needs to respond to a resent protocol message, the [source endpoint] property should be used as described in section 3.3 of [WS-Addressing Core]. Permanent loss of connectivity between a coordinator and a participant in an in-doubt state can result in data corruption.

Protocol faults raised by a Coordinator or Participant during the processing of a notification message are terminal notifications and MUST be composed using the same mechanisms as other terminal notification messages.

The two lines cited are shown as deleted by the purple change markings, along with all other references to message ids etc.

Alastair