- From: Asir Vedamuthu <asirv@webmethods.com>
- Date: Mon, 23 Aug 2004 22:16:33 -0400
- To: "'public-ws-desc-comments@w3.org'" <public-ws-desc-comments@w3.org>
- Cc: "Christopher St. John" <cks@webmethods.com>
I am writing this issue on behalf of Christopher St. John, webMethods.
ref: http://www.w3.org/TR/2004/WD-wsdl20-20040803/#InterfaceFault
Today, fault components are scoped to an interface component, aka interface
component.{faults}
Similar to element declaration components in message reference
component.{element}, we would like to re-use fault components across
interfaces. This usage naturally maps to many programming languages.
We request the WG to elevate fault components as first class daughters of
definition components. This will also eliminate unnecessary best practice
statements such as,
"For the above reason, it is considered good practice to ensure, where
necessary, that the {name} property of Interface Fault components within a
namespace are unique, thus allowing such derivation to occur without
inadvertent error."
Regards,
Asir S Vedamuthu
asirv at webmethods dot com
http://www.webmethods.com/
Received on Tuesday, 24 August 2004 02:16:39 UTC