W3C home > Mailing lists > Public > www-ws-desc@w3.org > February 2003

RE: MEPs: Operation content model (was: Template for renaming discussion)

From: Martin Gudgin <mgudgin@microsoft.com>
Date: Fri, 28 Feb 2003 11:26:31 -0800
Message-ID: <92456F6B84D1324C943905BEEAE0278E02F44472@RED-MSG-10.redmond.corp.microsoft.com>
To: "Jonathan Marsh" <jmarsh@microsoft.com>, <www-ws-desc@w3.org>

Agreed. We still need to do some work on the binding portion of part 1. Essentially, the content model is the same as that for port type, and the component model is copied down from the port type referenced by the type attribute. This is already in the editors todo list.
 
Gudge

________________________________

From: Jonathan Marsh
Sent: Fri 28/02/2003 19:00
To: www-ws-desc@w3.org
Subject: MEPs: Operation content model (was: Template for renaming discussion)




I could not help noticing below that the content model for <operation>
is different depending on whether it appears in a <portType> or a
<binding>, according to the MEP proposal as I read it.

-----Original Message-----
From: Jonathan Marsh
Sent: Friday, February 28, 2003 10:58 AM
To: 'www-ws-desc@w3.org'
Subject: Template for renaming discussion

Here is a comprehensive list (I believe) of the Part 1 element and
attribute names including those suggested in the MEPs proposal [1].  My
hope is that having these all listed on a single page will facilitate
the Renaming discussion.  The (s) indicates places where the proposal
was unclear on whether the name is plural or not.  I propose dealing
with precise names for these new constructs under the "Renaming" agenda
item instead of the "MEPs" agenda item.

<definitions targetNamespace="...">
  <documentation/> <!-- not shown henceforth -->
  <include location="..."/>
  <import namespace="..." location="..."/>
  <types>
    <xs:import namespace="..." schemaLocation="..."/>
    <xs:schema targetNamespace="..."/>
  </types>
  <message name="...">
    <part name="..." element="..." type="..."/>
  </message>
  <portType name="..." extends="...">
    <operation name="..." mep="...">
      <input name="..." message="..."/>
      <output name="..." message="..."/>
      <infault(s) name="..." message(s)="..."/>
      <outfault(s) name="..." message(s)="..."/>
    </operation>
  </portType>
  <binding name="..." type="...">
    <operation name="...">
      <input name="..." message="..."/>
      <output name="..." message="..."/>
      <fault name="..." message="..."/>
    </operation>
  </binding>
  <service name="...">
    <port name="..." binding="...">
  </service>
  <some:ext wsdl:required="..."/>
</definitions>

[1]http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl12/wsdl12.xml?re
v=1.46.2.3&content-type=text/xml
Received on Friday, 28 February 2003 14:27:04 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:22 GMT