RE: issue: optional parts in <message>?

XML Schema provides a rich, well-understood language for expressing
choices, sequences, optional, repeated, etc. constructs. It does not
seem like a good use of the WG time to re-invent such a mechanism.

Are there any interesting arguments against removing the message element
and making the operation within a port type point directly to an XML
Schema global element declaration?

--Jeff

-----Original Message-----
From: Sanjiva Weerawarana [mailto:sanjiva@watson.ibm.com] 
Sent: Wednesday, May 01, 2002 1:18 PM
To: WS-Desc WG (Public)
Subject: issue: optional parts in <message>?

<issue id="issue-message-parts">
  <head>Should the message part mechanism be extended to support
optional 
        parts etc.?</head>
  In WSDL 1.1, a message can only be defined to be a sequence of parts.
  It is not possible to indicate that certain parts may be optional,
  may occur multiple times, etc.? Should we do that? Overlapping with
  XML Schema's mechanisms is an obvious concern.
  <source>Sanjiva Weerawarana</source>
</issue>

Could we also start discussing this issue please?

Sanjiva.

Received on Wednesday, 1 May 2002 17:21:34 UTC