Re: exi header document

Thanks Daniel, somehow I thought that SE(header) was implied, but I checked
the grammar spec again, indeed there should be two productions:

DocContent :
    SE (header) DocEnd 0
    SE (*) DocEnd               1

Best,
Mark

On Thu, Apr 9, 2015 at 7:03 AM, Peintner, Daniel (ext) <
daniel.peintner.ext@siemens.com> wrote:

> Hi Mark,
>
> > a0 = 10 | 1 | 0 0000 // distinguished bits, options present, Version
>
> This is correct.. the rest is as follows
>
> 48 = 0 | 10 | 01000 // 1bit indicates <header> in root, 2 bits are choice
> between lesscommon(00)/common(01)/strict(01)/EE(11), EXI Body stream
>
> The actual EXI Options <header><strict/></header> is encoded in three (3)
> bits. After Encoding <strict/> nothing else is expected and EndElements are
> implicit. Hence the EXI Body stream (the actual document) starts in
> bit-packed encoding with 01000.
>
> Hope this helps,
>
> -- Daniel
>
>
>
>
>
> External service provider at Siemens AG
> Corporate Technology
> Corporate Research and Technologies
> Embedded Networks and Service Infrastructure
> Otto-Hahn-Ring 6
> 81739 Munich, Germany
>
> Mobile: +39 (348) 7390349
> mailto:daniel.peintner.ext@siemens.com
>
> Important notice: This e-mail and any attachment thereof contain corporate
> proprietary information. If you have received it by mistake, please notify
> us immediately by reply e-mail and delete this e-mail and its attachments
> from your system. Thank you.
>