W3C home > Mailing lists > Public > public-exi-comments@w3.org > February 2009

Re: Question about EXI Draft - Position of Self-Contained

From: Daniel Peintner <daniel.peintner@gmail.com>
Date: Thu, 26 Feb 2009 10:43:15 +0100
Message-ID: <abbf52e10902260143p15533365k2e03c43a38974c90@mail.gmail.com>
To: TAMIYA Keisuke <tamiya.keisuke@canon.co.jp>
Cc: public-exi-comments@w3.org, Efficient XML Interchange WG <member-exi-wg@w3.org>
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



On Fri, Nov 7, 2008 at 6:37 AM, TAMIYA Keisuke
<tamiya.keisuke@canon.co.jp> wrote:
>
> Dear W3C EXI WG members,
>
> I have a question about this draft specification.
>
> 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?
>
> Regards,
> Keisuke Tamiya (tamiya.keisuke@canon.co.jp)
>
>
>
>
Received on Thursday, 26 February 2009 09:43:57 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:45:28 UTC