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

RE: Change to the RPC signature extension (Was: [revised] Proposed resolutions for issues 146 and 150)

From: Jonathan Marsh <jmarsh@microsoft.com>
Date: Mon, 15 Mar 2004 11:36:04 -0800
Message-ID: <DF1BAFBC28DF694A823C9A8400E71EA202E7D2BC@RED-MSG-30.redmond.corp.microsoft.com>
To: "Roberto Chinnici" <Roberto.Chinnici@Sun.COM>
Cc: "WS Description List" <www-ws-desc@w3.org>

It's my understanding that ## is necessary in schema to distinguish the
tokens from relative URIs.  That's not necessary in a union with QNames.
I'd suggest going ahead with the change, and I'll put your proposal on
the agenda just to get blessing recorded in the minutes :-).

> -----Original Message-----
> From: Roberto Chinnici [mailto:Roberto.Chinnici@Sun.COM]
> Sent: Monday, March 15, 2004 11:30 AM
> To: Jonathan Marsh
> Cc: WS Description List
> Subject: Change to the RPC signature extension (Was: [revised]
Proposed
> resolutions for issues 146 and 150)
> 
> Jonathan,
> 
> I see you're using #any and #empty as "special" tokens in your
> proposal. In the RPC signature extension I used ##in, ##out, etc.
> (i.e. two initial "#" characters). I think it'd be better
> to harmonize the two proposals -- I usually have trouble
> remembering when to use ##other and when #all in XML Schema.
> Or was it #other and ##all?  ;-)
> 
> Anyway, it seems that one "#" character is sufficient to distinguish
> tokens from QNames, so I'd like to amend the definition of the
> RPC signature extension to use the same convention:
> #in/#out/#inout/#return.
> 
> As a purely editorial change, unless I get any objections I'll update
> the spec accordingly.
> 
> Thanks,
> Roberto
> 
> 
> Jonathan Marsh wrote:
> > 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:36:37 GMT

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