RE: {element declaration} for Interface Fault component

View: New views
1 Messages — Rating Filter:   Alert me  

Parent Message unknown RE: {element declaration} for Interface Fault component

by Jonathan Marsh-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Some parts of this message have been removed. Learn more about Nabble's security policy.

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

 


From: www-ws-desc-request@... [mailto:www-ws-desc-request@...] On Behalf Of Ramkumar Menon
Sent: Friday, January 05, 2007 3:05 PM
To: www-ws-desc@...
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