RE: Mapping ref attribute to {fault reference} - Type Mismatch

Thank you for considering my request.

Asir

-----Original Message-----
From: Jonathan Marsh [mailto:jmarsh@microsoft.com] 
Sent: Tuesday, September 21, 2004 2:42 PM
To: Asir Vedamuthu; public-ws-desc-comments@w3.org
Subject: RE: Mapping ref attribute to {fault reference} - Type Mismatch


Thanks for your comment.  The Working Group decided to fix this mismatch
by saying that the value is the component, and fixing the mapping
accordingly.

[See http://www.w3.org/2002/ws/desc/4/lc-issues/#LC14]

If you don't respond by October 1, we'll assume you accept this
resolution.

> -----Original Message-----
> From: public-ws-desc-comments-request@w3.org [mailto:public-ws-desc-
> comments-request@w3.org] On Behalf Of Asir Vedamuthu
> Sent: Monday, August 23, 2004 6:11 PM
> To: 'public-ws-desc-comments@w3.org'
> Subject: Mapping ref attribute to {fault reference} - Type Mismatch
> 
> 
> ref:
http://www.w3.org/TR/2004/WD-wsdl20-20040803/#FaultReference_Mapping
>
http://www.w3.org/TR/2004/WD-wsdl20-20040803/#FaultReference_details
> 
> Mapping,
> "{fault reference} = The actual value of the ref attribute information
> item"
> 
> Component description,
> "{fault reference} REQUIRED. An Interface Fault component in the
{faults}
> property of the parent Interface Operation component's parent
Interface
> component. Identifying the Interface Fault component therefore
indirectly
> defines the actual content or payload of the fault message."
> 
> Actual value is a QName. But, {fault reference} is a component. Hence,
the
> mismatch.
> 
> Regards,
> Asir S Vedamuthu
> asirv at webmethods dot com
> http://www.webmethods.com/

Received on Tuesday, 28 September 2004 19:33:21 UTC