- From: TAMIYA Keisuke <tamiya.keisuke@canon.co.jp>
- Date: Fri, 20 Feb 2009 14:41:46 +0900
- To: "Taki Kamiya" <tkamiya@us.fujitsu.com>
- Cc: <public-exi-comments@w3.org>, <youenn.fablet@crf.canon.fr>, <fujisawa.jun@canon.co.jp>
Hi Taki-san, Thank you for your reply. I understood your comment. And I think if you and WG-members share implementation report described in your reply, you can advise EXI users how to design the good data scheme in using an EXI parser. I hope such a guideline is written in the future. Regards, Keisuke Tamiya On Wed, 11 Feb 2009 11:40:21 -0800 "Taki Kamiya" <tkamiya@us.fujitsu.com> wrote: > We understand the concern you have raised over the issue grammar > learning behaviour may pose on the size of memory EXI processor > consumes and requires. > > While acknowledging it is a potential issue, we had stopped short of > adding a mechanism to restrain grammar learning at the time we dicussed > the feature a while back, based on implementation report of the feature > shared by the WG memebers, which suggested otherwise that the issue did > not surface in real deployments. > > One of the traits that documents for use in exchange in general is that > grammars are learned a lot up front at a pace close to linear rate, and > the learning becomes less and less frequent, eventually saturating to a > convergence. This observation helps explain why the issue is not very > likely to emerge in practice. > > Based on these observation and analysis, as well as the consideration of > the cost that would otherwise be incurred if a restraining mechanism was > introduced both in terms of compactness and runtime efficiency, we stay > cautious and may require further arguments involving specific use cases > before we consider a way to alleviate the potential issue.
Received on Friday, 20 February 2009 05:42:35 UTC