W3C home > Mailing lists > Public > public-ws-desc-comments@w3.org > February 2007

RE: 6.7.1.1 Construction of the request IRI using the http location

From: Jonathan Marsh <jonathan@wso2.com>
Date: Thu, 15 Feb 2007 16:01:10 -0800
To: "'Youenn Fablet'" <youenn.fablet@crf.canon.fr>, "'Philippe Le Hegaret'" <plh@w3.org>
Cc: <public-ws-desc-comments@w3.org>
Message-ID: <032b01c7515d$920d44e0$3501a8c0@DELLICIOUS>

Thank you for this comment.  The Working Group this issue as a CR117 [1]. 

The latest editor's draft [2] includes a provision for describing when and
how to %-encode data inserted into a template.  There is no provision that a
transform from XML into the http location template be unambiguously
reversible.

Unless you let us know otherwise within 2 weeks, we will assume you agree
with the resolution of this issue.

[1] http://www.w3.org/2002/ws/desc/5/cr-issues/issues.html#CR117
[2]
http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl20/wsdl20-adjuncts.html
?content-type=text/html;%20charset=utf-8#_http_operation_location_cited_ser


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

> -----Original Message-----
> From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org] On
> Behalf Of Youenn Fablet
> Sent: Wednesday, November 22, 2006 7:52 AM
> To: Philippe Le Hegaret
> Cc: www-ws-desc
> Subject: Re: 6.7.1.1 Construction of the request IRI using the http
> location
> 
> 
> Following on philippe's message, there are also ambiguous cases that
> might happen.
> Given this schema:
> <element name=root>
>     <sequence>
>         <element name=person type=string minOccurs=0/>
>         <element name=address type=string minOccurs=0/>
>         <element name=surname type=string minOccurs=0/>
>     </sequence>
> </element>
> Given this instance data:
> <root>
>     <person>foo</person>
>     <address>/</address>
>     <surname>foo</surname>
> </root>
> with http:location="foo/{person}/{address}/{surname}
> we will obtain foo/foo///foo, which leads to ambiguous parsing on the
> server side (as address='' and surname='/foo' will also lead to the same
> uri-encoded data).
> Should we prevent this case and escape the '/' character in url path
> encoded data?
> 
> There is also the case of the '?' special character that may lead to
> issues in determining when begins the query string.
> Should we prevent this case and escape the '?' character in url path
> encoded data?
>     Youenn
> 
> 
> 
> Philippe Le Hegaret wrote:
> > Given this instance data:
> >  <root>
> >    <foo>1</foo>
> >    <foo>2</foo>
> >  </root>
> >
> > With http:location="t"
> > we should obtain "t?foo=1&foo=2"
> >
> > With http:location="t/{foo}"
> > we should obtain "t/1?foo=2"
> >
> > With http:location="t/{foo}/{foo}"
> > we should obtain "t/1/2"
> >
> > With http:location="t/{foo}/{foo}/{foo}"
> > should we obtain an error (we don't have 3 foo elements in the instance
> > data) or, should we obtain "t/1/2/1" or "t/1/2/2" ?
> >
> > As a side comment, using element names in the http:location adds an
> > additional message schema constraint, in addition to the ones already
> > defined the IRI style: those element names shouldn't be optional. If one
> > of those http:location element names is defined as optional in the
> > schema, not including it in the instance data could result in a runtime
> > error.
> >
> > Philippe
> >
> >
> >
> >
Received on Friday, 16 February 2007 00:01:13 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:20:33 GMT