- From: santhanakrishnan <santhana@huawei.com>
- Date: Tue, 27 May 2008 19:31:04 +0530
- To: 'Taki Kamiya' <tkamiya@us.fujitsu.com>, public-exi@w3.org
Hi Taki Sorry for the delayed follow up. As per this structure of channels we will have to go about more than one pass of the exi block to get the information present in one block. First pass can only read structure channel (event code and qnames). Only after this we will be able to read all the values. Then in one more pass we will be able to construct the XML stream for the content present in this block. Am I correct ? Regards Santhanakrishnan -----Original Message----- From: Taki Kamiya [mailto:tkamiya@us.fujitsu.com] Sent: Friday, May 02, 2008 4:44 AM To: santhana@huawei.com; public-exi@w3.org Subject: RE: [EXI] Precompression needs more clarity Hi Santhanakrishnan, The boundaries between channels are implicit. By reading the structure channel, one can know how many value channels there are in the block, in what order, which channels are combined in what order, as well as the number of values contained in each channels. Because you know the number of values in the channel, you can decode each value using its associated datatype. When you've finished decoding one channel, it's the start of next channel when there are more channels subsequently, otherwise it's the end of the block. Hope it helps, -taki ________________________________ From: public-exi-request@w3.org [mailto:public-exi-request@w3.org] On Behalf Of santhanakrishnan Sent: Wednesday, April 30, 2008 11:21 PM To: public-exi@w3.org Subject: [EXI] Precompression needs more clarity Hi I feel the pre-compression explained in the specification needs some clarity. It does not deal with the demarcation of different value channels that are combined together. Some example pre-compression steps would be useful in better understanding. Regards Santhanakrishnan
Received on Tuesday, 27 May 2008 14:01:55 UTC