- From: TAMIYA Keisuke <tamiya.keisuke@canon.co.jp>
- Date: Wed, 14 Jan 2009 09:51:51 +0900
- To: "Taki Kamiya" <tkamiya@us.fujitsu.com>, <public-exi-comments@w3.org>
- Cc: <youenn.fablet@crf.canon.fr>, <fujisawa.jun@canon.co.jp>
Hi Taki-san, and WG members, Thank you for your detailed response. On Wed, 7 Jan 2009 12:12:06 -0800 "Taki Kamiya" <tkamiya@us.fujitsu.com> wrote: > Yet, we understand that there are use cases where the use of a particular > version of XML is required when serializing infoset into XML. On such > occasions, it is the program that subsequently consumes the serialized XML > that calls for a particular XML version. We consider XML version as the > artifact of XML serialization, and therefore is the function of XML > serializer implementations, instead of being something that has to be > inherited from the source XML if any that was fed into the computing chain > as an input. Yes, I thought about this case, and I understand you. But I think you had better describe the reason if you drop a part of the XML Infomation Set. Because in section 1.1 and section 2 "Design Principles" in the draft, you describe compatibility with the XML Information Set . Regards, Keisuke Tamiya
Received on Wednesday, 14 January 2009 00:54:10 UTC