RE: [EXI] Local Table miss and Global table hit

Hi Santhanakrishnan,
 
Actually, your question was very clearly stated. In your example below, the
value "Hello" would be added to the global partition and the local partition
for the <product> element. It would *not* be added to the local partition
for the <material> element. While you are correct that placing the value
"Hello" in the local partition of each element where occurs would improve
compactness, this would also increase the space complexity (memory
requirements) of the algorithm. In addition, we are currently considering
algorithms for bounded string tables to give limited devices a way to bound
memory usage. Many of the algorithms under consideration require us to
replace older string table entries with newer string table entries. This
replacement process would be more complex, require more memory and be more
computationally expensive if the value being removed was in many tables. 
 
    Hope this helps!,
 
    John


  _____  

From: santhanakrishnan [mailto:santhana@huawei.com] 
Sent: Wednesday, May 28, 2008 10:59 PM
To: products@agiledelta.com; public-exi@w3.org
Subject: RE: [EXI] Local Table miss and Global table hit



Hi John,

    Thank you very much for your response. I guess I was not clear enough in
my question. Consider the below case.

<product>"Hello"<product/>

<material>"Hello"<material/>

....

<material>"Hello"<material/>

<material>"Hello"<material/>

<material>"Hello"<material/>

 

In this case while processing the <product> element we add "Hello" value to
Local Table of <product> and the global table. While processing <material>
element we hit the "Hello" value from the global table. This case of a value
hit from the global table and not present in the local table of the element
is not dealt anywhere in the standard. 

In this case if we add the value "Hello" to the Local Table of <material>
element then it would help indeed in processing efficiency. Supposing there
are more occurrences of <material> element subsequently then each time we
need not miss in the local table of <material> and hit in the global table.
Also it will help in encoding the compact id in lesser number of bits. 

Or inline with your response am I missing any other point where processing
efficiency is affected with this kind of approach?

 

Regards

Santhanakrishnan