As written this function mandates an incorrect calculation for day of week for certain dates in the year 1900. An ISO standard should not be mandating incorrect values for the well-established Gregorian Calendar. To do so will only lead to confusion, poor interoperability and perpetuation of errors.

Proposed change: Remove the text that defines behavior that results in incorrect date calculations.

3.17.7.341 [p2818-2819]

te

Proposed Disposition of DIS 29500 Comment GB-0305 (Modified: 2008-01-02) Agreed; what was formerly the 1900 date base in SpreadsheetML - now called the 1900 backwards compatibility date base as a response to BR-0046, CH-0006 (and more) - that several functions dealing with dates and durations would incorrectly calculate those durations across February 28, 1900 and March 1, 1900. While that calculation bug must be maintained by these functions for compatibility with the existing corpus of binary documents, we do recognize the importance of fixing this calculation bug. As such, we have created a new date base as a response to BR-0046, CH-006 (and more) that both fixes the 1900 leap year bug and supports dates prior to the year 1900. When a SpreadsheetML document uses this new 1900 date base, functions such as WEEKDAY that deal with dates and durations should no longer display the buggy behaviour. Because the definitions of these functions already refer to §3.17.4.1 which describes the date base systems in SpreadsheetML, no update is necessary to §3.17.7.341 for this disposition. Similar Comments: CA-0071 , CL-0015 , CL-0172 , DE-0073 , FR-0352 , GR-0007 , IN-0062 , US-0134