W3C home > Mailing lists > Public > public-ws-desc-comments@w3.org > February 2007

RE: {element declaration} for Interface Fault component

From: Jonathan Marsh <jonathan@wso2.com>
Date: Thu, 22 Feb 2007 12:32:34 -0800
To: "'Ramkumar Menon'" <ramkumar.menon@gmail.com>
Cc: <public-ws-desc-comments@w3.org>
Message-ID: <017801c756c0$97e7f820$1501010a@DELLICIOUS>
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



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.



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

-Ramkumar Menon
A typical Macroprocessor 
Received on Thursday, 22 February 2007 20:32:31 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:05:58 UTC