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

Re: XOP/MTOM specs remaining problems

From: <noah_mendelsohn@us.ibm.com>
Date: Mon, 26 Apr 2004 12:54:32 -0400
To: "Herve Ruellan" <herve.ruellan@crf.canon.fr>
Cc: XMLP Dist App <xml-dist-app@w3.org>
Message-ID: <OF2EB05C65.6EE41407-ON85256E82.00626CFC@lotus.com>

> 4.2 Interpreting XOP Packages
> Issue: Nothing is said about what to do when the
> reconstruction of the XML Infoset fails, or if the XOP
> Package is incorrect while still allowing a
> reconstruction of the XML Infoset (e.g., xop:Include
> has a child element).
> Proposal: States that any failure is to be handled in
> an implementation dependant way.  States that any non
> fatal error may be ignored at the discretion of the
> implementation.

I have some concerns about this philosphically, in that I think it takes 
us closer than necessary to implying that we are specifying the behavior 
of processors as opposed to declaratively specifying an encoding. 

How about:

4.2:  Interpreting XOP Packages

This section specifies the means by which the original Infoset can be 
reconstructed from a XOP package that has been prepared according to the 
rules of 4.1 Creating XOP Packages. 

Note:  conventions or error reporting mechanisms to  be used in processing 
 multipart packages that incorrectly purport to be XOP Packages are beyond 
the scope of this specification. 

The essential difference here is that instead of normatively specifying 
that processors handle this in an implementation dependent way, we make 
clear that anything beyond the processing of correct XOP packages is 
beyond the scope of our specification.



Noah Mendelsohn 
IBM Corporation
One Rogers Street
Cambridge, MA 02142
Received on Monday, 26 April 2004 13:56:28 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 22:01:25 UTC