Issue 218 - Justify Interface Faults

there is already some text[1] currently in Part 1 to justify 
interface level faults. i suggest a slight rewording:

--From--
An Interface Fault component describes a fault that 
MAY be occur during execution of an operation of the interface. 
The Interface Fault component declares a fault by naming it and 
indicating the content or payload of the fault message. When and 
how the fault message flows is indicated by the Interface 
Operation component 2.4 Interface Operation.

The reason the Interface Fault component is a property of the 
Interface component is because that provides a convenient mechanism 
to declare a set of fault message types and then indicate which 
operations use those types, thus allowing one to easily indicate 
that the same fault message type can occur in multiple operations.
--00--


--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--


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. 

Paul

-- 
Paul Sumner Downey
Web Services Integration
BT Exact


[1] http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl20/wsdl20.html#InterfaceFault

Received on Wednesday, 23 June 2004 10:01:48 UTC