W3C home > Mailing lists > Public > xmlp-comments@w3.org > July 2002

SOAP 1.2 LC Issue: Clarification on Use of what SOAP Faults Mean when not Direct and Only Child of Body

From: Henrik Frystyk Nielsen <henrikn@microsoft.com>
Date: Fri, 19 Jul 2002 16:31:28 -0700
Message-ID: <79107D208BA38C45A4E45F62673A434D08515266@red-msg-07.redmond.corp.microsoft.com>
To: <xmlp-comments@w3.org>


This is IMO purely editorial--in the text from [1]:

"To be recognized as carrying SOAP error information, a SOAP message
MUST contain a single SOAP Fault element information item as the only
child of the SOAP Body .

When generating a fault, SOAP senders MUST NOT include additional
element information items in the SOAP Body . A message whose Body
contains a Fault plus additional element information items has no
SOAP-defined semantics.

A SOAP Fault element information item MAY appear within a SOAP header
block, or as a descendant of a child element information item of the
SOAP Body ; in such cases, the element has no SOAP-defined semantics."

I don't think the last sentence is correct. The question is not really
whether it has SOAP-defined semantics but whether it is the result of
the processing as defined in section 2.6 [2]. I suggest changing the
last sentence to:

"A SOAP Fault element information item MAY appear within a SOAP header
block, or as a descendant of a child element information item of the
SOAP Body; in such cases, the element is not indicating a failure in the
processing of that message as defined by the SOAP processing model
defined in [2]".

Henrik Frystyk Nielsen
mailto:henrikn@microsoft.com

[1] http://www.w3.org/TR/2002/WD-soap12-part1-20020626/#soapfault
[2] http://www.w3.org/TR/2002/WD-soap12-part1-20020626/#procsoapmsgs
Received on Friday, 19 July 2002 19:31:59 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 08:42:27 GMT