This document:Public document·View comments·Disposition of Comments·
Nearby:Efficient Extensible Interchange Working Group Other specs in this tool
Quick access to LC-2705 LC-2706 LC-2707 LC-2708 LC-2709 LC-2710 LC-2711 LC-2712 LC-2713 LC-2714 LC-2715
Previous: LC-2708 Next: LC-2714
Dear all, When reading up on the EXI specification section "7.3.3 Partitions Optimized for Frequent use of String Literals" last two paragraphs regarding the processing of value content items, I have one more issue to rise connected to the EXI Profile: In section "3. Local Value Capping" the parameter localValuePartitions is used to turn on or off the use of local value partitions. Note however that this same effect can be achieved by the use of the EXI parameter valuePartitionCapacity - it is not only used for the global value indexing. Setting valuePartitionCapacity to 0 effectively turns off both local and global value string tables. So the localValuePartitions parameter of the EXI profile has effect only when valuePartitionCapacity is greater than 0. However, the use of global value tables (valuePartitionCapacity > 0) while turning off only the local value tables (localValuePartitions = 0) is something that is highly unlikely to be useful in any scenario. So why having yet another parameter for something that is already available as option in the EXI specification?