RE: [SPAM] Issue with IgnoreUncidedEndpoint in LocationTemplate-1G

I don't think there's much practical difference between optional parameters
and nillable parameters - though we could debate the difference between
empty and null for months.

I'll expand my proposal for CR146 to include optional elements and
situations like this one:

  When serializing an HTTP request method that does not allow an HTTP 
  message body, and when {http location ignore uncited} is true, any 
  element not cited in the {http location} property MUST be defined in 
  the schema as nillable [[ or appear no less frequently than specified 
  by the minOccurs value. ]].

For this test case, I think instead of adding nillable="true" I should have
set minOccurs="1".  I'll go ahead and make that change.

Jonathan Marsh - http://www.wso2.com - http://auburnmarshes.spaces.live.com
 

> -----Original Message-----
> From: Youenn Fablet [mailto:[email protected]]
> Sent: Wednesday, January 31, 2007 1:31 AM
> To: keith chapman
> Cc: www-ws-desc; Jonathan Marsh
> Subject: Re: [SPAM] Issue with IgnoreUncidedEndpoint in LocationTemplate-
> 1G
> 
> I am then wondering how the nillable approach is better compared to the
> first, simpler, solution that comes to mind, i.e. stating that
> ignored parameters must be optional elements in the schema?
>     Youenn
> 
> keith chapman wrote:
> > Hi,
> >
> > The schema of LocationTemplate-1G states the following,
> >
> >       <xs:element name="time" type="xs:time" minOccurs="2"
> > maxOccurs="2" nillable="true"/>
> >
> > But in IgnoreUncidedEndpoint in LocationTemplate-1G,
> > whttp:location="datespace/{year}.html?start={time}". This is not
> > schema valid because there is only 1 time value. We can fix this by
> > changing the schema to minOccurs="1" or adding the end value to http
> > location.
> >
> > Thanks,
> > Keith.
> >
> > --
> > Keith Chapman
> > WSO2 Inc.
> > Oxygen for Web Services Developers.
> > http://wso2.org/