- From: Mark Nottingham <mark.nottingham@bea.com>
- Date: Mon, 28 Jun 2004 08:41:36 -0700
- To: <paul.downey@bt.com>
- Cc: <www-ws-desc@w3.org>
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-- +1 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. +1 -- Mark Nottingham Principal Technologist Office of the CTO BEA Systems
Received on Monday, 28 June 2004 11:41:41 UTC