W3C home > Mailing lists > Public > public-exi@w3.org > August 2009

Comments on restriced charset and whitespaces

From: FABLET Youenn <Youenn.Fablet@crf.canon.fr>
Date: Mon, 24 Aug 2009 16:52:00 +0200
To: "'public-exi@w3.org'" <public-exi@w3.org>
Message-ID: <C1797CB6A125334AB23C5A0A160944AD3609183C71@cressida.crf.canon.fr>
Dear all,

I have the following comment regarding the EXI specification.

The current regular expression generation mechanism does not seem to add automatically whitespaces in the character set.
This means that whitespaces (if not present in the regular expression) will not appear in the character set although they may actually appear in the string.
The solution seems to encode these whitespaces using the 'extended' symbol N + the actual whitespace symbol.
Another approach, used for built-in types in preserveLexical="true" is to add whitespaces within the character set, although these whitespaces could also be encoded using the previous strategy.

I am wondering whether that 'difference in behavior' is a conscious decision from the WG and whether there is a particular rationale behind this.

Received on Monday, 24 August 2009 14:52:41 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:52:43 UTC