[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsn] Issue: Pause/Resume subscription message types
That's assuming that we care about these elements being always empty! Not sure if we do. On the other hand, I always wondered if there are any real good reasons for the existence of these empty elements (other than making a SOAP processor happy by providing a required body element!). There are other simpler ways for signaling the operation intended by these empty elements (the non normative examples in the specs use wsa:Action). Thanks, Sanjay > -----Original Message----- > From: Samuel Meder [mailto:meder@mcs.anl.gov] > Sent: Tuesday, Jul 06, 2004 1:47 PM > To: wsn-oasis > Subject: [wsn] Issue: Pause/Resume subscription message types > > > The pause/resume subscription message types are currently declared as > > <xsd:element name="PauseSubscription" /> > <xsd:element name="PauseSubscriptionResponse" /> > <xsd:element name="ResumeSubscription" /> > <xsd:element name="ResumeSubscriptionResponse" /> > > They should be declared using a <complexType/> instead (other wise the > type defaults to anyType which is not quite what is intended). > > /Sam > -- > Sam Meder <meder@mcs.anl.gov> > The Globus Alliance - University of Chicago > 630-252-1752 > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]