[
https://issues.apache.org/jira/browse/DAFFODIL-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Beckerle resolved DAFFODIL-1930.
----------------------------------------
Resolution: Fixed
Assignee: Dave Thompson (was: Michael Beckerle)
Fixed in 4522a82d9739a4e47cc3dd89af76e05f54abcd08
> DFDLGeneralFormat defines calendarTimeZone as UTC - should define as ""
> -----------------------------------------------------------------------
>
> Key: DAFFODIL-1930
> URL: https://issues.apache.org/jira/browse/DAFFODIL-1930
> Project: Daffodil
> Issue Type: Bug
> Components: Front End
> Affects Versions: 2.1.0
> Reporter: Michael Beckerle
> Assignee: Dave Thompson
> Priority: Major
> Fix For: 2.2.0
>
>
> Because DFDLGeneralFormat.dfdl.xsd defines calendarTimeZone="UTC" dates like
> "7/4/1999" come through in the infoset as 1999-07-04+00:00, that is, with the
> trailing time-zone specifier.
> The right definition for calendarTimeZone for a general purpose format is "",
> which means "time zone unknown".
> This avoids the need for all users of DFDLGeneralFormat who have dates to
> override calendarTimeZone themselves to "" value, and puts the burden on them
> to define it if they know and want a default time zone.
> Note: changing this will likely change the behavior of dateTime type as well
> as the date type, and we should not be taking time zone information or
> defaults from the local machine settings.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
