[OASIS Issue Tracker] Commented: (OFFICE-2343) 3.3.3 Date andDateTime - 1900 as leap year

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/OFFICE-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18134#action_18134 ] 

Michael Brauer commented on OFFICE-2343:
----------------------------------------

3.3.3 has been reformulated in CD01, and I have made the suggestion on the mailing list to rephrase the two portable notes in 3.3.3 to:

Note: Expression authors should consider that the epoch date may vary
between implementations. Expressions that assume a particular epoch
date may have different results depending on the implementation

and 

Conforming evaluators shall support positive serial numbers. They may
support negative serial numbers to represent dates before the epoch.

Note: Expression authors should consider that it is evaluator
specific whether 1900 is considered to be a leap year.

Note: It is recommended that evaluators that consider 1900 to be a
non leap year use the epoch date 1899-12-30 to compensate
for serial numbers originating from evaluators that consider 1900
to be a leap year and use the 1899-12-31 epoch date.

Is there anything left open, or can we set the issue to resolved?

> 3.3.3 Date and DateTime - 1900 as leap year 
> --------------------------------------------
>
>                 Key: OFFICE-2343
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-2343
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: OpenFormula
>    Affects Versions: ODF 1.2 Part 2 CD 1
>            Reporter: Patrick Durusau
>            Assignee: Dennis Hamilton
>            Priority: Blocker
>             Fix For: ODF 1.2 Part 2 CD 2
>
>
> Currently we say:
> ***
> Many applications cannot handle Date values before January 1, 1900. Some applications can handle dates for the years 1900 and on, but include a known defect: they incorrectly presume that 1900 was a leap year (1900 was not a leap year). Applications may reproduce the 1900-as-leap-year bug for compatibility purposes, but should not. 
> ***
> Rob Weir suggests that we should not make editorial comments about bugs, compatibility, etc. I think that is a good point. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira