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

Re: Indicating element nodes that must be optimized with XOP

From: Herve Ruellan <herve.ruellan@crf.canon.fr>
Date: Tue, 01 Jun 2004 14:20:50 +0200
Message-ID: <40BC74A2.8000901@crf.canon.fr>
To: Hugo Haas <hugo@w3.org>
Cc: www-ws-desc@w3.org

Hugo,

Here are some answers for your questions (note that I speak for myself 
and not on behalf of the XMLP WG).

Hugo Haas wrote:
<snip/>
> The issue we have left as we discussed yesterday in our telcon is to
> identify which elements node to be optimized as per step 4 of the XOP
> processing model[7].

Note that saying nothing about how elements node to be optimized are 
identified is a deliberate choice of the XMLP WG. The purpose is to let 
applications free of choosing the mechanism best suited to them.

<snip/>

> An interesting thing I realized is that XOP itself is not a feature,
> i.e. the HTTP Transmission Optimization Feature uses XOP (which is
> only specific to SOAP despite its name) but doesn't say it's using the
> XOP feature, with a URI, etc.
> 
> It would be cool to have the HTTP Transmission Optimization Feature
> say that it uses the XOP feature, and then if somebody defines the XML
> over HTTP Transmission Optimization Mechanism feature as per my
> previous email[8], the feature could say that it uses the XOP feature
> and then it would be clear when the xop:optimize attribute becomes
> relevant.

XOP is not a SOAP feature, but a packaging mechanism that can be used by 
any XML language (there are some interests from SVG for using it).

However for the purpose of identifying a generic SOAP feature of which 
the HTTP Transmission Optimization Feature is a specialisation, MTOM 
defines the Abstract Transmission Optimization Feature [1] that is 
identified by a URI.

This does not solve however the problem of identifying the usage of XOP 
with the WSDL/HTTP binding that you raise in [8].

 > Hugo
 >
 >   6. http://lists.w3.org/Archives/Public/www-ws-desc/2004May/0077.html
 >   7. http://www.w3.org/TR/2004/WD-xop10-20040209/#xop_processing_model
 >   8. http://lists.w3.org/Archives/Public/www-ws-desc/2004May/0088.html

Regards,

Hervé.

[1] 
http://www.w3.org/2000/xp/Group/3/06/Attachments/OptimizationMechanism.html#feature
Received on Tuesday, 1 June 2004 08:21:30 GMT

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