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

RE: HTTP Location property definition

From: Jonathan Marsh <jonathan@wso2.com>
Date: Tue, 20 Feb 2007 15:30:09 -0800
To: "'youenn fablet'" <youenn.fablet@crf.canon.fr>
Cc: <public-ws-desc-comments@w3.org>
Message-ID: <01c501c75547$10c344a0$3501a8c0@DELLICIOUS>

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

The latest editor's draft [2] contains the central fixes, though others
appear in other sections, and even in part 1.

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#CR112

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 15, 2006 3:29 AM
> To: www-ws-desc@w3.org
> Subject: HTTP Location property definition
> Digging into the HTTP binding, I have the following comment, which is
> editorial IMHO.
> As per section 6.4.2, the HTTP location property is currently computed
> from the HTTP location attribute (if present) and the http endpoint
> address property, which does create some issues especially with bindings
> with no or multiple endpoints.
> I think we should change this part and have a direct @location to http
> location property mapping.
> If this change is agreed, we should check that every part of the
> specification making reference to the http location property is not
> broken.
> For instance, section checks that no question mark is present
> in the location property to add a question mark before the generated
> query string. This check should be applied to both the location property
> and endpoint address property.
>     Youenn
Received on Tuesday, 20 February 2007 23:30:07 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:31:06 UTC