W3C home > Mailing lists > Public > xml-dist-app@w3.org > April 2007

MTOM serialization policy assertion issues

From: Anish Karmarkar <Anish.Karmarkar@oracle.com>
Date: Fri, 27 Apr 2007 00:08:23 -0700
Message-ID: <4631A167.4010802@oracle.com>
To: "Xml-Dist-App@W3. Org" <xml-dist-app@w3.org>

1) The introduction and the abstract talks only about MTOM, but the spec 
is for an assertion that can be used for MTOM as well as the MTOMS11.

2) Required #2 in section 1.1: "Indicate the use of MTOM independent of 
transport"
how does one do that with this spec given that the policy subject is 
endpoint and portType is not allowed as the attachment point?

3) Text formating problems towards the end of section 1.2

4) Section 2.2, can we use a shorter more readable NS. For example:
http://w3.org/@@@/policy/mtom

5) section 2.4: since we don't define any wsdl in this spec, we can 
remove WSDL from the precedence rules.

6) Section 2: do we need this. We are defining terms that are already 
defined else where. Can we just point to it?

7) Section 3.2 needs to add a reference to [MTOMS11].

8) Section 3.2: do we need ignorable in the pseudo-schema as well as the 
schema in the appendix?

9) Sectoin 3.2: any reason not to make the assertion extensible via 
elements?

10) Bug http://www.w3.org/Bugs/Public/show_bug.cgi?id=4341 talks about 
message-level granularity. What about operation-level granularity?

11) In the case where MTOM assertion is included in the WSDL endpoint 
with wsp:Optional='true' and the client of a req-res operation does not 
use application/xop+xml media-type and wants to indicate that the 
service can send application/xop+xml media-type (bug 4341):
how about saying something along the lines of --
This spec does not define how to convey which policy alternative is 
selected or which feature is supported. Specific protocols may have an 
ability to convey such information. For example, Accept HTTP header may 
be used by the HTTP client to convey which media-types are acceptable 
for the response.

12) Need an example where req is application/soap+xml and response is 
application/xop+xml (and/or vice versa).

-Anish
--
Received on Friday, 27 April 2007 07:10:43 GMT

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