RE: {element declaration} for Interface Fault component

Thank you for this comment.  The Working Group this issue as a CR138 [1]. 

 

The latest editor's draft [2] makes faults the same as message references by
adding a {message content model} property, with the values #any, #other,
#element, #none.)

 

Unless you let us know otherwise within 2 weeks, we will assume you agree
with the resolution of this issue.

 

[1] http://www.w3.org/2002/ws/desc/5/cr-issues/issues.html#CR138

[2]
http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl20/wsdl20.html?content-
type=text/html;%20charset=utf-8#InterfaceFault

 

Jonathan Marsh -  <http://www.wso2.com> http://www.wso2.com -
<http://auburnmarshes.spaces.live.com> http://auburnmarshes.spaces.live.com

 

  _____  

From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org] On
Behalf Of Ramkumar Menon
Sent: Friday, January 05, 2007 3:05 PM
To: www-ws-desc@w3.org
Subject: {element declaration} for Interface Fault component

 

The XML Representation of the Interface Fault Component [section 2.3.2 -
Part 1] defines the {element declaration} property to be of type xs:QName.

This maybe changed to acommodate a union of xs:QName and xs:token.

 

-Ram

-- 
Shift to the left, shift to the right!
Pop up, push down, byte, byte, byte!

-Ramkumar Menon
A typical Macroprocessor