| Re: Ocp Timezones [message #263 is a reply to message #261] |
Wed, 18 May 2011 09:43   |
Susanne Wunsch railML
Messages: 0
Registered: January 2020
|
|
|
|
Hi,
Joerg von Lingen <coord(at)rollingstockrailmlorg> writes:
> 1) A simple flag (boolean) can only be used in timetable as it has a
> meaning only in relation to a certain date.
I would interprete the flag as "the ocp is located in an area, where
daylight saving is used". This is an geographical feature which is
independent from actual date and time.
It is a very political issue wether DST is used or not. Countries' time
offset to UTC do also change by some reasons.
> 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.
> But do we really need that information?
We already offer time zone dependent date and time tags in "timetable"
subschema.
You could fill the timetable with UTC values and the software transforms
it to the actual time according to the regional time zone specified in
ocp.
I think it's a proper enhancement which is worth implementing as
flexible and reliable as possible.
How about the W3C Guideline for "Working with time zones"? [2]
I hope it helps...
Susanne
[1] http://en.wikipedia.org/wiki/Tz_database
[2] http://www.w3.org/International/wiki/WorkingWithTimeZones
--
Susanne Wunsch
Schema Coordinator: railML.common
|
|
|
|
Members
Search
Help
Login
Home
