- From: Jean-Jacques Moreau <jean-jacques.moreau@crf.canon.fr>
- Date: Wed, 17 Mar 2004 12:01:45 +0100
- To: xmlp-comments@w3.org, Jacek Kopecky <jacek@systinet.com>
- Cc: chris@w3.org, Herve Ruellan <herve.ruellan@crf.canon.fr>
I am opposed to the resolution. The whole premice behind the split of MTOM into two separate specification was precisely so it could be used by other specification, in particular SVG. The decision to not address data: URIs attributes was made when MTOM was based on the XQuery data model. The data model made it difficult to support such attributes. The XMLP WG has recently decided to revert back to a simpler Infoset-based model. This change, I believe, now makes it much easier to support data: URI attributes. I also consider the Infoset change to be a significant change, and kindly ask that issue 452 be reopened and dealt with, possibly along the lines of [1]. Thank you, Jean-Jacques. [1] <http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2003Dec/0031.html> > Hi Chris, > > the XMLP WG has decided at its face-to-face meeting last week to close > issue 452 regarding optimizing data: URIs in attributes by declining to > add support for this in XOP. We don't consider data: URIs a good use > case to design our optimization mechanism for. > > Best regards, > > Jacek Kopecky > > Systinet Corporation > http://www.systinet.com/
Received on Wednesday, 17 March 2004 06:02:40 UTC