W3C home > Mailing lists > Public > public-exi@w3.org > December 2015

Call for opinions on how to represent empty elements in Canonical EXI

From: Takuki Kamiya <tkamiya@us.fujitsu.com>
Date: Mon, 21 Dec 2015 13:31:12 -0800
To: "public-exi@w3.org" <public-exi@w3.org>
Message-ID: <23204FACB677D84EBD57175AB7B5A71C03567577C345@FMSAMAIL.fmsa.local>
Hi,

There are two approaches proposed on how to define rules regarding 
the encoding of empty elements in schema-informed context.

Please provide any opinions as to which of those approaches you 
consider more appropriate to have as part of Canonical EXI.

The behavior of each approach is described below.

Approach A: This approach always first tries to encode empty elements 
(i.e. SE followed by EE, optionally AT, etc. in between) as a sequence of 
SE CH EE (optionally AT etc. between SE and CH) where CH is used for 
representing empty string, for elements defined to have simple-content,
as long as doing so is possible (i.e. unless the codec in effect does *not* 
permit to encode empty string "").

Approach B: This approach encodes empty elements (i.e. SE followed by EE, 
optionally AT, etc. in between) as a sequence of SE EE (optionally AT etc. 
in between). As an exception, for elements defined to have simple-content,
it is allowed to insert CH that represents empty string "" between SE and EE
only when doing so is necessary for representing an empty element there.

Note the approach B provides better efficiency, while approach B leads to 
generate the same sequence of events whether strict or non-strict mode.

Thank you,

Takuki Kamiya
Fujitsu Laboratories of America
Received on Monday, 21 December 2015 21:32:01 UTC

This archive was generated by hypermail 2.3.1 : Monday, 21 December 2015 21:32:02 UTC