- From: TAMIYA Keisuke <tamiya.keisuke@canon.co.jp>
- Date: Fri, 06 Mar 2009 14:32:04 +0900
- To: Daniel Peintner <daniel.peintner@gmail.com>
- Cc: public-exi-comments@w3.org, Efficient XML Interchange WG <member-exi-wg@w3.org>
Hello Daniel, Thank you for your answer. I understood that the mechanism to find Self-Contained Data from an EXI document is out of the specification. If possible, please show me some mechanism you and WG-members have discussed. Regards, Keisuke Tamiya On Thu, 26 Feb 2009 10:43:15 +0100 Daniel Peintner <daniel.peintner@gmail.com> wrote: > Hello Tamiya, > > thank you for interest in EXI. > > > EXI has Self-Contained option (ref. S.5.4). > > And the EXI parser can parse Self-Contained data without parsing other > > parts of the EXI document. > > But how does the EXI Parser find the position (ex. bytes offset) in the > > EXI data? > > If the EXI parser wants to parse Self-Contained data first, can it get > > a start position of Self-Contained data from the EXI documents? > > The EXI format itself offers only a hook to support selfContained > subtrees, meaning that an EXI processor may access such an independent > fragment without reading what came first. > > The working group expects many different use cases for this feature > and does not restrain its use to a specific mechanism which is likely > not be suitable for many environments. It is therefore up to an > application or system to make use of this feature and build an index > or any other solution on top of it. > > Hope this answers your question! > > Thanks, > > -- Daniel
Received on Friday, 6 March 2009 05:33:02 UTC