- From: John Schneider <john.schneider@agiledelta.com>
- Date: Wed, 22 Sep 2010 13:09:28 -0700
- To: "'FABLET Youenn'" <Youenn.Fablet@crf.canon.fr>, <public-exi-comments@w3.org>
Received on Wednesday, 22 September 2010 20:10:34 UTC
Dear Youenn, Thank you for you careful review and feedback of the EXI specification. You are correct that the phrase "has a schema-valid value" used in section 9.2.1 is inconsistent with other parts of the specification. In other cases, we intentionally avoided the term "schema-valid" so as not to give the false impression schema-validation is needed for EXI processing. We have reworded section 9.2.1 to more precisely specify the criteria that determines which xsi:nil values occur in the structure stream. Thank you again, John _____ From: public-exi-comments-request@w3.org [mailto:public-exi-comments-request@w3.org] On Behalf Of FABLET Youenn Sent: Friday, January 29, 2010 6:46 AM To: public-exi-comments@w3.org Subject: xs:nil feature in compression mode Dear all, This is feedback we have related to the EXI specification. The wording of @xsi:nil in section 9.2.1 seems slightly out of sync. The inclusion within or without the structure channel of the @xsi:nil value happens if @xsi:nil "has a schema-valid value". I would reword it so that we phrase in terms of the @xsi:nil values being encoded using the Boolean representation. This does not change the behavior and I find it clearer this way. Regards, Youenn
Received on Wednesday, 22 September 2010 20:10:34 UTC