FWIW, RFC3339 allows timezones in the range +/- 23:59, with minutes in the
range 0-59. This was not, not my awareness, the result of any deep
consideration, but the way the syntax happens to come out.
[[
date-fullyear = 4DIGIT
date-month = 2DIGIT ; 01-12
date-mday = 2DIGIT ; 01-28, 01-29, 01-30, 01-31 based on
; month/year
time-hour = 2DIGIT ; 00-23
time-minute = 2DIGIT ; 00-59
time-second = 2DIGIT ; 00-58, 00-59, 00-60 based on leap second
; rules
time-secfrac = "." 1*DIGIT
time-numoffset = ("+" / "-") time-hour ":" time-minute
time-offset = "Z" / time-numoffset
partial-time = time-hour ":" time-minute ":" time-second
[time-secfrac]
full-date = date-fullyear "-" date-month "-" date-mday
full-time = partial-time time-offset
date-time = full-date "T" full-time
]]
#g
At 12:07 PM 9/14/02 -0400, Keith Moore wrote:
> I believe it suffices to require:
> 1. that the offset specified correspond to some established
> time zone in effect at the specified date-time, leaving
> the range subject as it is to the whims of politicians
> 2. that the "minutes" part be in the range 00 through 59
> (2822 seems to permit +9899, for example).
seems reasonable.
(has this actually been a problem in practice?)
Keith
-------------------
Graham Klyne
<GK(_at_)NineByNine(_dot_)org>