DR 09-0275 - BRM: serial date representation

[Horton, Gareth]

Chris,

We are also going to need prose, since 18.17.4 specifies ISO8601.  We need to spell out that "Each unique instant in SpreadsheetML time is stored as an ISO 8601-formatted string ..." does not apply to Part 4.

Also the discussion of dateCompatibility in 18.2.28 may need to addressed, since as far as I can see, a dateCompatibility value of 0 or false must not be supported if we are removing ISO8601 dates for compatibility purposes. Essentially we need to remove the 1900 date base system as well.  

In any case, we are intending to change the range for this date system for the ISO8601 changes we have planned, since it currently allows a base date of Jan 1 -9999.

There is also mention in 18.17.6.7 that we might want to explicitly point to, as regards deviating from it in Part 4.

Some other considerations:

DATE and other relevant functions - should disallow values enabled by 1900 date base here.

Gareth

-----Original Message-----
From: Chris Rae [mailto:Chris.Rae at microsoft.com] 
Sent: 28 April 2010 17:54
To: e-SC34-WG4 at ecma-international.org
Subject: DR 09-0275 - BRM: serial date representation

I volunteered back in Stockholm to write up the changes that would be required  in order to remove ISO 8601 dates from Transitional, and then we could work together to establish how these could be integrated into Part 4. Attached are the details of the changes that would need to be effected in Part 1 - we will now have to work out how best to word these alterations in Part 4. I believe the schemas are included in their entirety, so the easiest way to incorporate the prose changes is probably to make two mentions of the enumeration values to be removed and the sections they are mentioned in (something like "In section x, element x is removed"). It doesn't feel quite normative enough for me but I think it's a better option than copying and pasting the entire section and leaving it open for the texts to diverge.

Thoughts,

Chris