- From: Don Brutzman <brutzman@nps.edu>
- Date: Mon, 11 Dec 2017 08:41:49 -0800
- To: "Peintner, Daniel" <daniel.peintner.ext@siemens.com>, 'Takuki Kamiya' <tkamiya@us.fujitsu.com>
- CC: 'Carine Bournez' <carine@w3.org>, "public-exi@w3.org" <public-exi@w3.org>
Summary based on preceding analysis and today's discussion: 1. First alternative, suggested changes for Canonical EXI: > 4. Recommended changes: > > "Hour is a value in the range 0-24" > to > "Hour is a value in the range 0-23" > > and > "seconds is a value in the range 0-60" > to > "seconds is a value in the range 0-59" and > WARNING > This approach does not account for uniquely representing the specific time values corresponding to leap seconds. Separate data representations may be necessary to account for such values. > [reference Wikipedia page or ITU] 2. Second alternative, suggested for least disruption with existing ecosystem, EXI Canonical might say: NOTE The approach allowed by XML Schema and EXI permits ambiguous values for times correct even-minute values. Canonical EXI documents should use a seconds value of 00 rather than 60 if strict comparability among different applications and documents is desired. EXAMPLE The preferred form for "one minute after midnight" is 00:01:00 and not 00:00:60. 3. The leap-seconds issue needs to be raised with XML Schema maintenance, at a minimum it is deserving of a note to document authors. 4. I think it is far preferable to have a single special case for leap seconds (intermittently and unpredictably, years apart) than have ambiguity and lack of comparable canonical representations every minute of every day. all the best, Don -- Don Brutzman Naval Postgraduate School, Code USW/Br brutzman@nps.edu Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149 X3D graphics, virtual worlds, navy robotics http://faculty.nps.edu/brutzman
Received on Monday, 11 December 2017 16:43:44 UTC