Edit comment LC-2715 for Efficient Extensible Interchange Working Group

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

Comment LC-2715

Comment Shortname:

Commenter: Rumen Kyusakov <rumen.kyusakov@ltu.se>

Message-id:

Section of the document concerned:

[Free text description]Document as a wholeAbstract Status of this Document 1. Introduction 2. Grammar Capping 2.1 Grammar Learning Disabling Mechanism 2.2 Grammar Learning Disabling Parameters 3. Local Value Capping 4. Parameters representation A References B Header Considerations (Non-Normative) C Prefix Workarounds (Non-Normative) D Name Table Workarounds (Non-Normative) D.1 Name Table Encoder Workarounds D.2 Name Table Decoder Workarounds E Grammar Restriction Considerations (Non-Normative) E.1 Grammar Restriction Encoder Considerations E.2 Grammar Restriction Decoder Considerations
or

Refinement of the section concerned:

Status:

open proposal pending resolved_yes resolved_no resolved_partial other assigned to Nobody Bournez, Carine Brutzman, Don Cokus, Michael Fernández, Javier D. Heuer, Joerg Käbisch, Sebastian Kamiya, Takuki Kuntschke, Richard Matsukura, Ryuichi McGregor, Don Peintner, Daniel Quin, Liam Shah, Grishma ZERGAOUI, Mohamed

Type: substantive editorial typo question general comment undefined

Resolution status:

Response drafted Resolution implemented Reply sent to commenter

Response status:

No response from Commenter yet Commenter approved disposition Commenter objected to disposition
Commenter's response (URI):

Comment:

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?

Related issues: LC-2706, LC-2714
(space separated ids)

WG Notes: DP drafted a response in: https://lists.w3.org/Archives/Member/member-exi-wg/2012Nov/0055.html The reviewed the draft during the telecon on 2012-12-05, and decided to send out the response.

Resolution: As alluded in my previous emails, the next updated version of the profile will introduce a "Guidelines" section. In regard to restricted devices, this new section is going to give advice for sensible default options for both, the EXI profile and the EXI1.0 baseline spec. However, we do not plan to prohibit users experimenting with the various options to best fit their needs. http://lists.w3.org/Archives/Public/public-exi-comments/2012Dec/0000.html

(Please make sure the resolution is adapted for public consumption)