| Re: Ocp Timezones [message #265 is a reply to message #263] |
Sat, 21 May 2011 12:44   |
Christian Rahmig
Messages: 151
Registered: January 2011
|
Senior Member |
|
|
Hello Tuomas (and everybody),
>> 2) The information is a "feature" of an ocp, however, it has to be
>> much more detailed in order to be valid in general for an
>> infrastructure item independent of any date. Subsequently it would
>> require to name start and end date/time of the daylight saving period
>> for each year as this may be subject to changes.
>
> These data are already collected and active maintained in the "tz
> database". [1] It also hosts the history of time zone/DST regulations
> for each region.
Regarding your comments I changed the timezone definition in
http://trac2.assembla.com/railML/changeset/394
Now, the tz database (Olson database) defines the format of the timezone
attribute, which is a simple string.
The entry, e.g. "Europe/Paris" or "America/New_York", does not refer to
a special UTC time offset, but a location. Thus, it is possible to
consider temporary time changes like DST within the timezone attribute
implicitly.
Best regards
Christian
> [1] http://en.wikipedia.org/wiki/Tz_database
---
Christian Rahmig
railML.infrastructure coordinator
|
|
|
|
Members
Search
Help
Login
Home
