W3C home > Mailing lists > Public > www-ws-desc@w3.org > July 2004

RE: issue 235: definition of Fault

From: <paul.downey@bt.com>
Date: Thu, 15 Jul 2004 15:50:29 +0100
Message-ID: <2B7789AAED12954AAD214AEAC13ACCEF2709DA63@i2km02-ukbr.domain1.systemhost.net>
To: <sanjiva@watson.ibm.com>, <www-ws-desc@w3.org>

straw-man text:

"""
A fault is an event that occurs during the execution of a 
Message Exchange that disrupts* the normal flow of messages.
 
A fault is typically raised when a party is unable to 
communicate an error condition inside the normal message flow,
or a party wishes to terminate a message exchange. A fault 
message may be used to communicate out of band information such 
as the reason for the error, the origin of the fault, as well as 
other informal diagnostics such as a program stack trace. 
"""



-----Original Message-----
From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org]On
Behalf Of Sanjiva Weerawarana
Sent: 15 July 2004 15:27
To: www-ws-desc@w3.org
Subject: issue 235: definition of Fault



Issue 235 is asking for a "A short, formal definition of what a 
Fault is, in WSDL terms, may be useful (not necessarily in this
document, but somewhere)."

We already say in part1:

    <p>The Interface Fault component provides a clear mechanism
    to name and describe the set of faults an interface may 
    generate. This allows operations to easily identify the 
    individual faults they may generate by name. This mechanism
    allows the ready identification of the same fault occurring 
    across multiple operations and referenced in multiple bindings
    as well as reducing duplication of description for an 
    individual fault.</p>

Since we already assert that faults are clear ;-), can someone please
help figure out what additional wording would be necessary to
satisfy this issue?

Sanjiva.
Received on Thursday, 15 July 2004 10:51:17 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:32 GMT