- From: Sanjiva Weerawarana <sanjiva@watson.ibm.com>
- Date: Thu, 6 Feb 2003 11:37:38 +0600
- To: "FABLET Youenn" <youenn.fablet@crf.canon.fr>, "Roberto Chinnici" <roberto.chinnici@sun.com>, <www-ws-desc@w3.org>
- Cc: "Jean-Jacques Moreau" <jean-jacques.moreau@crf.canon.fr>
"FABLET Youenn" youenn.fablet@crf.canon.fr writes: > > IMHO, we are searching for a construct quite similar to the xsd:element > but a little bit more constrained (fewer properties, no xml-schema > children in it) and with a sligthly different semantic. > Would it better to add another construct for the purpose of clarity, > readability and accuracy, the tradeoff being a (small ?) increase of the > complexity ? I am not sure of the answer... > Thoughts ? ;-) <wsdl:message> ;-) I am a bit surprised that the proposal I made for how to eliminate message is not interesting to more people. Basically what I proposed allows one to use a single XSD element or type for the 80% case and IF ONE WISHES to document more than one input or output element or type, then they can indicate it. That's a nice way to cleanly support the attachment stuff, for example (such as additional XML documents or GIF images people may want to send along with their SOAP envelope). It seems like a middle-ground that allows the people happy with just modeling the world with schema to do so, but allows others to life happily too. Sanjiva.
Received on Thursday, 6 February 2003 00:40:40 UTC