[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: TimeZone issues
I haven’t gotten a chance to work on
the actual document. But I do have a list of issues I’d like to
make a decision on for Wed’s meeting. Previously we decided that
timezones would be defined via a facet with a value space of an zoneinfo/Olsen
database identifier – the Olsen database itself would define the timezone
and daylight saving times rules for a specific identifier. 1) Should the facet attribute name be “timezone”
or “tz”? 2) The Olsen database uses timezone
identifiers such as “America/New_York”. The continent portion
of the identifier is actually unnecessary and could be shorted to just such as “New_York”
– or put another way the city name itself is an unambiguous identifier (as
the database is currently defined). Do we wish to use the city name only
as the identifier? 3) Should we support any level of “timezone
inheritance”. Potentially options: a) no inheritance: all
abstime objects must declare a timezone facet (and what happens if not defined?) b) document level
inheritance: timezone facet is inherited from parent object within document
(unlike anything we do today) c) site level
inheritance: timezone facet is inherited from a property on the Lobby object Brian |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]