W3C home > Mailing lists > Public > public-exi@w3.org > July 2007

Constraint on string tables

From: Stanley A. Klein <sklein@cpcug.org>
Date: Thu, 19 Jul 2007 12:22:01 -0400 (EDT)
Message-ID: <62771.>
To: public-exi@w3.org

Section 7.3 specifies that"

"The life cycle of a string table spans the processing of a single EXI
stream. String tables are not represented in an EXI stream or exchanged
between EXI processors. A string table cannot be reused across multiple
EXI streams; therefore, EXI processors MUST use a string table that is
equivalent to the one that would have been newly created and pre-populated
with initial values for processing each EXI stream."

Why is this constraint included?  It appears to imply that the string
table must be rebuilt for each message in a communications context.  If a
number of strings are known to occur repeatedly in a particular
communications context, why not allow the string table to be optionally
pre-populated for that context, just as schemas are permitted to be
optionally specified?

Stan Klein
Received on Thursday, 19 July 2007 19:14:02 UTC

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