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

RE: CR123: Simultaneous presence of {http method} and {safe}

From: Rogers, Tony <Tony.Rogers@ca.com>
Date: Tue, 13 Feb 2007 08:01:27 +1100
Message-ID: <BEE2BD647C052D4FA59B42F5E2D946B317B7D9@AUSYMS12.ca.com>
To: "Jean-Jacques Moreau" <jean-jacques.moreau@crf.canon.fr>, "WSD Public" <www-ws-desc@w3.org>
My thought would be that {http method}, being the most specific, takes precedence over {safe}, but {safe} takes precedence over {http method default}.
 
Tony Rogers

________________________________

From: www-ws-desc-request@w3.org on behalf of Jean-Jacques Moreau
Sent: Tue 13-Feb-07 0:51
To: WSD Public
Subject: CR123: Simultaneous presence of {http method} and {safe}




I've implemented the current resolution for CR123.

However, I think we need to do a little more. Indeed, currently:
- if both {http method} (or, in its absence, {http method default}) and
{safe} are set, {http method} takes precendence, i.e. the value of the
{safe} property is ignored.

This could be an issue, for example if {http method}="POST" and
{safe}="true".

Two alternatives:
a. Indicate {http method} and {safe} cannot be present simultaneously.

b. {safe} takes precendence over {http method} (as {http method} already
takes precendence over {http method default}).

There's some appealing symmetry in b., but a. may be straigther.

JJ.
Received on Monday, 12 February 2007 21:02:41 GMT

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