W3C home > Mailing lists > Public > www-ws-desc@w3.org > June 2004

RE: Indicating element nodes that must be optimized with XOP

From: Ugo Corda <UCorda@SeeBeyond.com>
Date: Wed, 2 Jun 2004 09:35:25 -0700
Message-ID: <EDDE2977F3D216428E903370E3EBDDC903958D38@MAIL01.stc.com>
To: "Hugo Haas" <hugo@w3.org>
Cc: "Herve Ruellan" <herve.ruellan@crf.canon.fr>, <www-ws-desc@w3.org>

I assume your response only applies to case 2. For case 1, it would be
unreasonable for the service provider to expect the element to be
optimized.

Regards,
Ugo

> -----Original Message-----
> From: Hugo Haas [mailto:hugo@w3.org] 
> Sent: Wednesday, June 02, 2004 3:42 AM
> To: Ugo Corda
> Cc: Herve Ruellan; www-ws-desc@w3.org
> Subject: Re: Indicating element nodes that must be optimized with XOP
> 
> 
> * Ugo Corda <UCorda@SeeBeyond.com> [2004-06-01 10:25-0700]
> > Regarding your "XOP-optimization required" value, what would the 
> > behavior be in the following cases?
> > 
> > 1) The run-time value of the element is not in canonical lexical 
> > representation (so that, according to XOP, it cannot be optimized)
> > 
> > 2) The XOP machinery decides not to optimize the element 
> for its own 
> > reasons (which is consistent with the XOP Processing Model).
> 
> Well, that's a good question. I guess that if I am a service 
> provider and have decided for some reason to enforce the use 
> of XOP and the optimization of an element node transmission, 
> and for some reason a service requester agent cannot do it, 
> then maybe we just won't talk to one another, and I won't 
> process the request.
> 
> Regards,
> 
> Hugo
> 
> -- 
> Hugo Haas - W3C
> mailto:hugo@w3.org - http://www.w3.org/People/Hugo/
> 
Received on Wednesday, 2 June 2004 12:35:56 GMT

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