- From: Takuki Kamiya <tkamiya@us.fujitsu.com>
- Date: Mon, 29 Feb 2016 15:02:36 -0800
- To: "Peintner, Daniel (ext)" <daniel.peintner.ext@siemens.com>, "public-exi@w3.org" <public-exi@w3.org>
Hi Daniel, Let's use as an example the following XML snippets, and assume in both cases the value is typed as xsd:int. 1. <A> 123 </A> 2. <A>123</A> In case #1, the data "123" is surrounded by whitespaces. When xml:space="preserve" is in effect, and the EXI grammar in use is *not* strict, the case #1 will be encoded using CH [untyped] production. On the other hand, case #2 will be encoded using CH [typed] production because it does not contain whitespaces around the number. When EXI grammar in use *is* strict, then the encoding #1 will fail as you mentioned in the document. Do you share the same understanding? Thank you, Takuki Kamiya Fujitsu Laboratories of America -----Original Message----- From: Peintner, Daniel (ext) [mailto:daniel.peintner.ext@siemens.com] Sent: Monday, January 11, 2016 9:27 AM To: Takuki Kamiya; public-exi@w3.org Subject: AW: Whitespace preservation mode All, I started to define whitespace handling rules in the spirit of the current TTFMS rules [1]. Please find a first draft here [2]. I think we could add advise for users * to use preserve.LexicalValue if encoding fails * to use xml:space="preserve" if canonicalization is expected to preserve as much whitespaces as possible Do you have any comment and/or feedback. Thanks, -- Daniel [1] https://lists.w3.org/Archives/Public/public-exi/2015Oct/0008.html [2] https://www.w3.org/XML/EXI/docs/canonical/canonical-exi.html#whitespaceHandling ________________________________ Von: Takuki Kamiya [tkamiya@us.fujitsu.com] Gesendet: Dienstag, 1. Dezember 2015 03:51 An: public-exi@w3.org Betreff: Whitespace preservation mode Hi, When there is a type associated with an element, content type information gives you an idea as to what to do with whitespaces during encoding. However, in schema-less situations, the best you can do is to guess what is expected to do, unless xml:space is specified. I am not very sure if this heuristics is always correct. I think we may need to provide a canonicalization mode where canonicalization is expected to preserve as much whitespaces as possible. Thank you, Takuki Kamiya Fujitsu Laboratories of America
Received on Monday, 29 February 2016 23:03:21 UTC