W3C home > Mailing lists > Public > www-ws-desc@w3.org > November 2005

Proposed Text for What Should Be Declared as a Fault in WSDL

From: Arthur Ryman <ryman@ca.ibm.com>
Date: Tue, 8 Nov 2005 09:24:41 -0500
To: www-ws-desc@w3.org
Message-ID: <OF2D6B0620.4F0213C8-ON852570B3.004C5A35-852570B3.004F27C7@ca.ibm.com>
As per my action item [1], here is the proposed text:

"The Interface component describes faults that have application level 
semantics, i.e. that the client or service is expected to handle, and 
potentially recover from, as part of the application processing logic. For 
example, an Interface component that accepts a credit card number may 
describe faults that indicate the credit card number is invalid, has been 
reported stolen, or has expired. The Interface component does not describe 
general system faults such as network failures, out of memory conditions, 
out of disk space conditions, invalid message formats, etc., although 
these faults may be generated as part of the message exchange. Such 
general system faults can reasonably be expected to occur in any message 
exchange and explicitly describing them in an Interface component is 
therefore redundant."


This should be added to Part 1, section 2.3.1 after the sentence 
beginning: "Note that faults other than the ones described in the 
Interface component can also be generated at run-time, i.e. faults are an 
open set."



[1] http://www.w3.org/2005/11/03-ws-desc-minutes.html#action02

Arthur Ryman,
IBM Software Group, Rational Division

blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca
Received on Tuesday, 8 November 2005 14:24:50 GMT

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