From: santhanakrishnan <santhana@huawei.com>

Date: Wed, 09 Jul 2008 09:12:50 +0530

To: public-exi@w3.org

Message-id: <000001c8e175$dd0f74a0$4a18120a@china.huawei.com>

Date: Wed, 09 Jul 2008 09:12:50 +0530

To: public-exi@w3.org

Message-id: <000001c8e175$dd0f74a0$4a18120a@china.huawei.com>

Hi EXI Experts For the encoding of N-Bit Unsigned integer I feel the EXI specification has some contradictions. Especially when it is used for representing the Bounded Integer type from Schema. Perception 1: When in the bounded integer the range is within 4095 then the offset from mininclusive is encoded. When the range is greater than 4095 then Integer encoding is suggested for the same. For Integer encoding of positive number - 0(boolean) number(unsigned int) would be encoded For Integer encoding of negative number - 1(boolean) number(unsigned int) would be encoded Perception 2: This is from the Table 7-1. Built-in EXI Datatypes. Here it says * For integer without minInclusive or minExclusive facets, or with minInclusive or minExclusive facet of negative value(-ve Number) - Integer * For nonNegativeInteger or integer with minInclusive or minExclusive facet value of 0 or above(+ve number) - Unsigned Integer There is a contradiction for the encoding of positive number when the range is greater than 4095 in the above cases. The sign bit 0(boolean) is extra in case 1. Which approach has to be followed ? I observed that the prevalent EXI implementation Agile Delta is following case 2 for bounded integers when they are out of bounds and positive. Please clarify in this regard. regards SanthanakrishnanReceived on Wednesday, 9 July 2008 03:49:35 UTC

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