W3C home > Mailing lists > Public > public-exi@w3.org > August 2008

Re: [EXI] SC fragment

From: Daniel Peintner <daniel.peintner@gmail.com>
Date: Fri, 8 Aug 2008 18:35:17 +0200
Message-ID: <abbf52e10808080935i54f9849bja48f66a8a97a6a69@mail.gmail.com>
To: santhana@huawei.com, public-exi@w3.org

Hello Santhanakrishnan,

Thank you very much for you continuing interest in EXI.

>         In the Built-in Element grammar definition, in the semantics for SC
> fragment step 6, it is mentioned that the sequence of events have to be
> processed according to a Fragment grammar. Here is mentions the sequence as
> (SD, SE(qname), content, ED). But I may also have NS, AT or directly CH
> events following this SC event in which case My Fragment
> or FragmentContent grammar has no means to process it. How this case will be
> handled ?
>     Also the sequence of events should also consider NS, AT, CH events and I
> will have a sequence like this (SD, [NS], [AT], [CH/SE(qname)], [content],
> ED).

Regarding the SC Fragment case there seems to be a misunderstanding.

Step 4 in the referred semantics section speaks about a preceding SE
qname. This qname is appearing once again in the SC fragment part. The
SC fragment itself is encoded as familiar EXI fragment with the qname
as the *root* element.

Let me give you a simple example where you have selfContained
fragments for each page in a document


   ... otherPages ...

The EXI events stream reads as follows:
SD SE(document) SE(page) SC SD SE(page) ...pageContent... EE ED  EE
...otherPages... EE ED

Hope this helps,

-- Daniel

> regards
> Santhanakrishnan
Received on Friday, 8 August 2008 16:35:54 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:52:43 UTC