I thought this was on the list somewhere but I couldn't find it, so I'll restate it here. One benefit we would lose from making wsa:ReplyTo optional is an indication in the message whether a reply is expected. An intermediary or proxy might use this information to, for example, keep a connection open without having a description of the message's MEP available. The information content of a specified wsa:ReplyTo and a default value is different. > -----Original Message----- > From: public-ws-addressing-request@w3.org [mailto:public-ws- > addressing-request@w3.org] On Behalf Of Mark Peel > Sent: Wednesday, March 02, 2005 12:08 PM > To: public-ws-addressing@w3.org > Subject: Re: Proposed resolution for Issue 50 (Misallignment of faut > to and reply to ) > > > > +1 to Dave's approach. But as for quoting Ockham's Razor as written, > I > feel we have enough cryptic language to deal with already... Latinum > est; non potest legi. > > Cheers, > > Mark Peel > Web Services Infrastructure > Novell, Inc. > > > >>> David Hull <dmh@tibco.com> 03/02/05 9:43 AM >>> > I think we're on the same page semantically. I believe the difference > > is between saying > > * missing => anonymous => binding-specified > > and > > * missing => binding specified > > For me the latter wins. /Entia non sunt multiplicanda praeter > necessitatem/. > >Received on Wednesday, 2 March 2005 20:30:40 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:35:04 GMT