- From: Taki Kamiya <tkamiya@us.fujitsu.com>
- Date: Tue, 8 Sep 2009 19:48:25 -0700
- To: "'FABLET Youenn'" <Youenn.Fablet@crf.canon.fr>, <public-exi@w3.org>
- Message-ID: <5603D368ACC64F3DBF1343AED47BAA96@homunculus>
Hi Youenn, Thanks for bringing the issue to our attention. You are right, and the "datatype" should mean to apply not only to the datatype itself but also to the datatypes derived from it by restriction. We will update the spec to clarify it in the next publication. Thanks again, -taki _____ From: public-exi-request@w3.org [mailto:public-exi-request@w3.org] On Behalf Of FABLET Youenn Sent: Monday, August 24, 2009 7:43 AM To: 'public-exi@w3.org' Subject: Clarification on datatype representation map Dear all, I have the following comment regarding section 7.4 of the EXI specification. According my reading of section 7.4, datatype representation map can be used to map a given type to a different encoding than the one defined by default in the EXI specification. >From other parts of the specification, I had the impression (but may this is just over-engineering ) that the actual intent of section 7.4 was to state that the mapping impacts both the type and its sub-types (except if a closer mapping is defined). Clearly, this adds more power at the expense of more implementation complexity. Anyway, if the latter interpretation is right, it may be good to actually state this in section 7.4. Regards, youenn
Received on Wednesday, 9 September 2009 02:49:18 UTC