W3C home > Mailing lists > Public > www-ws-desc@w3.org > March 2004

RE: [revised] Proposed resolutions for issues 146 and 150

From: Jonathan Marsh <jmarsh@microsoft.com>
Date: Mon, 15 Mar 2004 11:09:51 -0800
Message-ID: <DF1BAFBC28DF694A823C9A8400E71EA202E7D225@RED-MSG-30.redmond.corp.microsoft.com>
To: "Asir Vedamuthu" <asirv@webmethods.com>, "WS Description List" <www-ws-desc@w3.org>

See, I had to put a schema bug in there just to see who would notice
:-).

I assume if there's no element attribute the {content model} property
would have no value (the default is empty).  That's why I introduced an
explicit #element value at the component model level, to distinguish
between the absence of the element attribute, and the presence of the
attribute with a Qname.

> -----Original Message-----
> From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org]
On
> Behalf Of Asir Vedamuthu
> Sent: Sunday, March 14, 2004 4:42 AM
> To: Jonathan Marsh; WS Description List
> Subject: RE: [revised] Proposed resolutions for issues 146 and 150
> 
> 
> Minor corrections (see line 2 and 3) to simple type 'elementReference'
> syntax,
> 
> 1  <xs:simpleType name="elementReference">
> 2   <xs:union memberTypes="xs:QName">
> 3    <xs:simpleType>
> 4     <xs:restriction base="xs:token">
> 5      <xs:enumeration value="#any"/>
> 6      <xs:enumeration value="#empty"/>
> 7     </xs:restriction>
> 8    </xs:simpleType>
> 9   </xs:union>
> 10 </xs:simpleType>
> 
> > <xs:attribute name="element" type="elementReference" use="optional"
/>
> 
> If this attribute is absent, is there any default value for {message
> content
> model} property?
> 
> Asir
> 
> -----Original Message-----
> From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org]
On
> Behalf Of Jonathan Marsh
> Sent: Thursday, March 11, 2004 7:35 PM
> To: WS Description List
> Subject: [revised] Proposed resolutions for issues 146 and 150
> 
> 
> 
> Here's an update to my proposal [.0] for issues 146 [.1] "Should WSDL
be
> able to describe an operation with *anything* in the message?" and 150
> [.2] "Indicating empty bodies".
> 
> When using XML Schemas, the element attribute points to a QName of a
> GED, preventing either empty bodies, or unconstrained content.
Special
> values of the element attribute could indicate these conditions.
> 
> Status quo:
>   <xs:attribute name="element" type="xs:QName" use="optional" />
> 
> Proposal:
>   <xs:attribute name="element" type="elementReference" use="optional"
/>
> 
>   <xs:simpleType name="elementReference">
>     <xs:union>
>       <xs:simpleType memberTypes="xs:QName">
>         <xs:restriction base="xs:token">
>           <xs:enumeration value="#any"/>
>           <xs:enumeration value="#empty"/>
>         </xs:restriction>
>       </xs:simpleType>
>     </xs:union>
>   </xs:simpleType>
> 
> {message content model} A token with one of the values '#any',
'#empty',
> or '#element'.  A value of #any indicates that there are no
restrictions
> on the message structure.  A value of empty indicates there is no
> message content.  A value of element indicates that the message
consists
> of a single element described by the global element declaration
> reference by the {element} property.
> 
> {element} A reference to an XML element declaration in the {element
> declarations} property of 2.1.1 The Definitions Component. This
element
> represents the content or "payload" of the message.  When the {message
> content model} property has the value #any or #empty the element
> property is empty.
> 
> The mapping from XML into these properties should be fairly obvious.
> 
> [.0] http://lists.w3.org/Archives/Public/www-ws-desc/2004Mar/0058.html
> [.1] http://www.w3.org/2002/ws/desc/2/06/issues.html#x146
> [.2] http://www.w3.org/2002/ws/desc/2/06/issues.html#x150
Received on Monday, 15 March 2004 14:10:24 GMT

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