Edit comment LC-3042 for Efficient Extensible Interchange Working Group

Quick access to LC-3041 LC-3042 LC-3043 LC-3044 LC-3045 LC-3065 LC-3066 LC-3067 LC-3068 LC-3069 LC-3070 LC-3071 LC-3072 LC-3073 LC-3074 LC-3075 LC-3076 LC-3077 LC-3078

Comment LC-3042

Comment Shortname:

Commenter: timeless <timeless@gmail.com>

Message-id:

Section of the document concerned:

[Free text description]Document as a whole1. Introduction Canonical EXI Abstract 1.1 Notational Conventions and Terminology 1.2 Need of Canonical EXI 1.3 Applications 1.4 Limitations 2. Canonical EXI Stream 3. Canonical EXI Header 4. Canonical EXI Body 4.1 EXI Alignment Options and Streams 4.2 EXI Event Selection 4.2.1 Prune productions according to specific conventions 4.2.2 Prune productions for non applicable events with content values 4.2.3 Use the event with the most accurate event 4.3 EXI Stream Order 4.4 EXI Datatypes 4.4.1 Unsigned Integer 4.4.2 Enumeration 4.4.3 Decimal 4.4.4 Float 4.4.5 Date-Time 4.4.6 String and String Table 4.4.7 Restricted Character Sets 4.4.8 Datatype Representation Map A Design Decisions A.1 Relationship to XML Security A.2 No Unicode Normalization B Canonical EXI Examples B.1 EXI Event Selection Example B-1. Example productions with event codes B.2 EXI Stream Order Example B-2. Attribute and Namespace Declaration Sorting Figure C-1. Canonical EXI used in Signature B.3 EXI Floats Example B-3. Example algorithm for converting float values t... Example B-4. Canonicalized EXI Float values C Canonical EXI Applications C.1 Signature Processing Steps C.2 Exchange EXI Options (Best Practices "Work in Progress") C.2.1 Option 1 - XML Signature element C.2.2 Option 2 - Uri scheme fragment identifier C.2.3 Option 3 - EXI options within EXI stream D References
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:

> On the contrary, values that match the default value (i.e. <blockSize>1000000</blockSize>) MUST be omitted.

On the contrary => conversely

> When the alignment option compression is set, pre-compress MUST be used instead.

instead of ?

> Moreover, the EXI event sequence of each nested element MUST be SE followed by EE

would it hurt you to link "SE" and "EE" to some definition of "Start
Element" / "End Element" for readers less familiar w/ the jargon used
herein?

> The user defined meta-data MUST NOT be used unless it conveys a convention used by the application.

"user defined meta-data" is italicized, but it isn't linked, and the
use of "The" doesn't help me. If you dropped "The", I could almost
understand what you're saying. If the "The" is important, then this
italicized text SHOULD link to something defining it.

> The user defined meta-data conveys auxiliary information and does not alter or extend the EXI data format.
> Hence it deemed acceptable to omit this information.

it => it is | it was

> Elements that are necessary to structure the EXI options document according to the XML schema
> (i.e. lesscommon, uncommon, alignment, datatypeRepresentationMap, preserve and common)
> MUST be omitted unless there is at least one nested element according to the previous steps.

Ideally steps are in numbered form, or somehow called out beyond "by
the way, I hid steps somewhere before this point".

Related issues: (space separated ids)

WG Notes:

Resolution: > On the contrary => conversely Agree. > instead of ? The bullet list item has been changed to "When the alignment option compression is set, pre-compress MUST be used instead of compression." Further, references to all EXI options have been added. > would it hurt you to link "SE" and "EE" to some definition of "Start > Element" / "End Element" for readers less familiar w/ the jargon used > herein? Start Element (SE) and respectively End Element (EE) is used instead of the abbreviations. A link to EXI event types has been added also. > "user defined meta-data" is italicized, but it isn't linked, and the > use of "The" doesn't help me. If you dropped "The", I could almost > understand what you're saying. If the "The" is important, then this > italicized text SHOULD link to something defining it. "user defined meta-data" links now to the EXI specification. > it => it is | it was Changed to "it is". > Ideally steps are in numbered form, or somehow called out beyond "by > the way, I hid steps somewhere before this point". The bullet list has been changed to a numbered list.

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