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

Re: Indicating element nodes that must be optimized with XOP

From: Hugo Haas <hugo@w3.org>
Date: Thu, 3 Jun 2004 07:23:26 +0200
To: Ugo Corda <UCorda@SeeBeyond.com>
Cc: Herve Ruellan <herve.ruellan@crf.canon.fr>, www-ws-desc@w3.org
Message-ID: <20040603052326.GB4578@w3.org>
Hi Ugo.

* Ugo Corda <UCorda@SeeBeyond.com> [2004-06-02 09:35-0700]
> 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.

Maybe there is something I'm missing about case 1: can certain base64
blobs not be be serialized in canonical lexical form?

I had assumed that this limitation in XOP was only applying to
intermediaries: they may receive an element which is not in canonical
lexical representation; if their job was for example to XOP-optimize
the SOAP message, then they would not be able to.

However, for the message originator, I thought that it always had the
choice and therefore it was not a problem. If I am designing my
application and I have to use XOP, then I should be able to do so. If
I can't for some reason, then I should not use a service that requires
XOP-optimization of some things.

Am I missing something?

Regards,

Hugo

-- 
Hugo Haas - W3C
mailto:hugo@w3.org - http://www.w3.org/People/Hugo/

Received on Thursday, 3 June 2004 01:23:27 GMT

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