ISSUE-122: DateTime Canonicalization should preserve seconds field
DateTime Canonicalization should preserve seconds field
- State:
- CLOSED
- Product:
- Canonical EXI
- Raised by:
- Takuki Kamiya
- Opened on:
- 2018-04-16
- Description:
- On 2017-11-28, Rich Rollman (AgileDelta) argued in email exchanges (not public)
that "the problem with using the algorithm [2] is that it destroys the
information contained in the dateTime. Taking the test case data as an example
with UTC normalization enabled, the two times 2012-06-30T23:59:60-06:00 and
2012-07-01T00:00:00-06:00 will result in the same digital signature which
should not be the case as these are two different times, the former one second
later than the latter."
[2] https://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#adding-durations-to-dateTimes - Related Actions Items:
- No related actions
- Related emails:
- AW: Draft request to publish Proposed Recommendation of the Canonical EXI (revised) (from daniel.peintner.ext@siemens.com on 2018-04-17)
- Draft request to publish Proposed Recommendation of the Canonical EXI (revised) (from tkamiya@us.fujitsu.com on 2018-04-16)
- ISSUE-122: DateTime Canonicalization should preserve seconds field [Canonical EXI] (from sysbot+tracker@w3.org on 2018-04-16)
Related notes:
The WG agreed with the argument [1], and clarified the way the WG
is going to make the specification clear on this aspect.
https://lists.w3.org/Archives/Public/public-exi/2017Dec/0005.html
Rich Rollman (AgileDelta) agreed with the proposed approach [1] in clarifying
the specification.
[1] https://lists.w3.org/Archives/Public/public-exi/2017Dec/0006.html
Display change log