W3C

Efficient XML Interchange (EXI) Format 1.0 (Second Edition) Errata

01 September 2014


Abstract

This document records all known errors in the Efficient XML Interchange (EXI) Format 1.0 (Second Edition) (hereinafter, "the specification" or "the spec").

If you find errors in the specification that are not listed in this document, please report them to public-exi-comments@w3.org. Archives of the mailing list are available at public archive.

Table of Contents

1. Substantive Errata
2. Editorial Errata
3. Clarifications
A. Errata Changes


1. Substantive Errata

To be added upon receipt of errors.

2. Editorial Errata

To be added upon receipt of errors.

3. Clarifications

Section 5.4 EXI Options

01 September 2014

Insert the following clarification just before the sentence "Below is a brief description of each EXI option.":

Setting particular values to some of the EXI options may affect, or involve a trade-off among, the processing speed, the level of compactness and the amount of memory required during processing.

Add the following sentence after the end of the second sentence of the paragraph that starts with "[Definition:] The selfContained option....":

The use of self-contained elements results in EXI streams which require more runtime memory during processing compared to equivalent streams without selfContained elements.

The first sentence in the paragraph that starts with "[Definition:] The valueMaxLength option specifies ...." reads:

The valueMaxLength option specifies the maximum length of value content items to be considered for addition to the string table

Change that sentence to:

The valueMaxLength option specifies the maximum number of characters for value content items represented with 7.1.10 String to be considered for addition to the string table.

Add the following sentence at the end of the paragraph that starts with "[Definition:] The valueMaxLength option specifies ....":

Large or "unbounded" values of the valueMaxLength option can lead to higher memory consumption in exchange for smaller sized EXI streams as compared to equivalent streams with small values of the valueMaxLength option. Setting valueMaxLength to 0 disables the "local" and "global" value partitions of the string table which has the same effect as setting valuePartitionCapacity to 0.

Add the following at the end of the paragraph that starts with "[Definition:] The valuePartitionCapacity option ...."

Large or "unbounded" values of the valuePartitionCapacity option lead to higher memory consumption in exchange for smaller sized EXI streams as compared to equivalent streams with small values of the valuePartitionCapacity option. Setting valuePartitionCapacity to 0 disables the "local" and "global" value partitions of the string table which has two consequences: 1) lower memory usage during processing compared to "unbounded" valuePartitionCapacity case with difference in memory consumption proportional to the number and the size of the string value content items in the stream; 2) larger EXI stream compared to "unbounded" valuePartitionCapacity case with difference in size proportional to the number and the size of the repeating string value content items in the stream.

Section 5.4 EXI Options

01 September 2014

Add the following at the end of the paragraph that starts with "[Definition:] The blockSize option specifies ....":

The element "blockSize" SHOULD NOT appear in an EXI options document when the "compression" element is absent or the alignment option has value different from pre-compression.

A. Errata Changes (in reverse chronological order)