W3C home > Mailing lists > Public > public-exi@w3.org > February 2016

AW: Header canonicalization

From: Peintner, Daniel (ext) <daniel.peintner.ext@siemens.com>
Date: Tue, 23 Feb 2016 13:59:10 +0000
To: Takuki Kamiya <tkamiya@us.fujitsu.com>, "public-exi@w3.org" <public-exi@w3.org>
Message-ID: <D94F68A44EB1954A91DE4AE9659C5A980FE540A9@DEFTHW99EH1MSX.ww902.siemens.net>
Hi Taki,

I think you are right with both comments.

The latest Editor's draft incorporates your feedback by simplifying rule #1 and adding Preserve.lexicalValues fidelity option to rule #5.


-- Daniel

[1] https://www.w3.org/XML/EXI/docs/canonical/canonical-exi.html#canonicalHeader

Von: Takuki Kamiya [tkamiya@us.fujitsu.com]
Gesendet: Dienstag, 23. Februar 2016 02:46
An: public-exi@w3.org
Betreff: Header canonicalization


Looking at header canonicalization section [1], I noticed one potential canonicalization
rule is not described yet.

When lexical preservation is on, DTRM should be omitted entirely.

Also, currently the section says:
"The options elements that change the default EXI option values
 (i.e. byte, pre-compress, selfContained, valueMaxLength, valuePartitionCapacity,
 dtd, prefixes, lexicalValues, comments, pis, blockSize, compression, fragment,
 schemaId, strict) MUST NOT be omitted (see EXI specification for default values)."

I am not sure if we need to mention it because they simply cannot be omitted
even if we don't mention that.

[1] https://www.w3.org/TR/2015/WD-exi-c14n-20150521/#canonicalHeader<&smime=>

Thank you,

Takuki Kamiya
Fujitsu Laboratories of America
Received on Tuesday, 23 February 2016 13:59:41 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 23 February 2016 13:59:41 UTC