Issue 108348 - util::DateTime cannot represent XML-Schema P2 dateTime
Summary: util::DateTime cannot represent XML-Schema P2 dateTime
Status: CONFIRMED
Alias: None
Product: App Dev
Classification: Unclassified
Component: api (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: All All
: P3 Trivial
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-15 12:43 UTC by mst.ooo
Modified: 2017-05-20 11:28 UTC (History)
5 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description mst.ooo 2010-01-15 12:43:07 UTC
http://www.w3.org/TR/xmlschema-2/#dateTime

In the XML-Schema 2 specification, the datatype dateTime has several
aspects that our current UNO API css::util::DateTime struct cannot represent:

1. negative values
An XMLSchema-2 dateTime may have an "-" prefix to denote negative dates (BCE).
util::DateTime has all unsigned members, and no sign field.

2. fractional second precision
XMLSchema-2 specifies that fractional seconds must be supported with
at least 3 decimal digits of precision.
util::DateTime only has HundredthSeconds precision.

3. timezones
An XMLSchema-2 dateTime may contain a timezone offset.
util::DateTime has no timezone support.
It would be possible to convert all timezoned values to UTC on import;
however, timezoned values must sill be distinguishable from non-timezoned
values, which are specified to be in some unknown timezone, and thus are
not in general comparable with timezoned values.
Comment 1 Marcus 2017-05-20 11:28:06 UTC
Reset assigne to the default "issues@openoffice.apache.org".