W3C home > Mailing lists > Public > www-ws-desc@w3.org > May 2002

resolving issue-message-parts

From: Sanjiva Weerawarana <sanjiva@watson.ibm.com>
Date: Thu, 30 May 2002 22:28:31 +0600
Message-ID: <016901c207f7$2a363f70$0aaa7cca@lankabook2>
To: "WS-Desc WG \(Public\)" <www-ws-desc@w3.org>

Per our call today I've recorded the following:

<issue id="issue-message-parts" status="closed">
  <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>
  <resolution>We will consider this for WSDL 2.0 in conjunction
  with the resolution for issue "issue-eliminate-message." If 
  &lt;message&gt; is retained in WSDL 2.0, then this issue becomes
  interesting; otherwise its a non-issue.</resolution>

If anyone is concerned with this wording please let me know.

FYI, this is the status of issue-eliminate-message:

<issue id="issue-eliminate-message" status="closed">
  <head>Can we eliminate &lt;message&gt; in favor of a schema 
  Using the &lt;message&gt; mechanism to define the structure of
  a message makes the &lt;message&gt; syntax an alternate infoset
  defining syntax to XSD in some sense. It would be nice to be
  able to write message definitions just using XSD and eliminate
  the &lt;message&gt; mechanism altogether.
  <source>Keith Ballinger, Jeffrey Schlimmer, Others</source>
  <resolution>We will consider this for WSDL 2.0. For WSDL 1.2,
  we will not remove the &lt;message&gt; construct.</resolution>


Received on Thursday, 30 May 2002 12:30:35 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:06:23 UTC