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

Re: Issue 218 - Justify Interface Faults

From: Mark Nottingham <mark.nottingham@bea.com>
Date: Mon, 28 Jun 2004 08:41:36 -0700
Message-Id: <A38EEEA8-C919-11D8-A9BF-000A95BD86C0@bea.com>
Cc: <www-ws-desc@w3.org>
To: <paul.downey@bt.com>

On Jun 23, 2004, at 7:01 AM, <paul.downey@bt.com> wrote:

> --To--
> An Interface Fault component describes a fault that
> MAY occur during invocation of an operation of the interface.
> The Interface Fault component declares an abstract fault by naming
> it and indicating the contents of the fault message. When and how
> the fault message flows is indicated by the Interface Operation
> component 2.4 Interface Operation.
> The Interface Fault component provides a clear mechanism to name and
> describe the set of faults an interface may generate. Operations may
> 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.
> --00--


The second sentence in the second paragraph is a bit confusing, 
probably because of its use of 'may'. Suggest "This allows operations 
to easily identify..."

> I wonder if we need to say anything about faults which are not 
> described
> in the interface. i.e. that it is legal for an operation to generate a
> fault not described in WSDL.


Mark Nottingham   Principal Technologist
Office of the CTO   BEA Systems
Received on Monday, 28 June 2004 11:41:41 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:54:49 UTC