Wikidata:Property proposal/Equivalent Timezone
equivalent timezone[edit]
| Description | timezone with the same offset to UTC |
|---|---|
| Represents | time zone (Q12143) |
| Data type | Item |
| Domain | instance of (P31)time zone (Q12143) |
| Example | UTC+08:00 (Q6985) → Irkutsk Time (Q2347353), Macau Standard Time (Q996734), time in China (Q187189), China Standard Time (Q1143153); Irkutsk Time (Q2347353) → UTC+08:00 (Q6985) |
| See also | UTC timezone offset (P2907), located in time zone (P421), said to be the same as (P460) |
- Motivation
If we look at United States of America (Q30) and Russia (Q159) we see two completely different system for storing timezone information of geographical objects (see located in time zone (P421)). Either the country item links to UTC timezone items (instance of (P31)time zone named for a UTC offset (Q17272482), e.g. UTC+08:00 (Q6985)) or to more figurative items (e.g. Irkutsk Time (Q2347353)). I think both ways are legitimate. We should be able to use them equivalently. Therefore we need a standardized way to link a item like Irkutsk Time (Q2347353) with UTC+08:00 (Q6985) and backwards. This property would replace said to be the same as (P460) in those use cases, which is in my eyes not as meaningful.
This property is a Wikidata property for Wikivoyage (Q24262056). T.seppelt (talk) 05:59, 15 June 2016 (UTC)
- Discussion
@Jura1, Thryduulf, Matroc, LtPowers, WOSLinker: -- T.seppelt (talk) 05:59, 15 June 2016 (UTC)
Comment located in time zone (P421) is the inverse of this and is used on most of the named timezone items I looked at recently. I don't think said to be the same as (P460) is a good choice as named timezones can change relative to UTC and I don't think said to be the same as (P460) should take qualifiers - either something is the same as or it isn't. If we want the inverse of located in time zone (P421) as well I'd call it something like "timezone using this offset". Thryduulf (talk) 08:08, 15 June 2016 (UTC)
- @Thryduulf: have a look at this query. The only thing what we have at the moment is a mess. The constraints for located in time zone (P421) state that items should be P31/P297* of geographic location (Q2221906). Timezones don't fulfill this criteria. I think the proposed property should use itself as an inverse property. We should use located in time zone (P421) only on geographical objects. -- T.seppelt (talk) 09:01, 15 June 2016 (UTC)
Question Can't it determined by querying for items with the same UTC timezone offset (P2907) value? --Pasleim (talk) 13:03, 20 June 2016 (UTC)
- @Pasleim: UTC timezone offset (P2907) is only for instances of time zone named for a UTC offset (Q17272482) in accordance to the property proposal. Furthermore it's not possible to run such queries with the Lua Wikibase Client extension. We need some kind of link. --T.seppelt (talk) 05:28, 21 June 2016 (UTC)
Oppose I would rather propose to expend the timezone offset property. ChristianKl (talk) 14:17, 9 July 2016 (UTC)
- @ChristianKl: this would probably be useful for some use cases. It's not possible nonetheless to link between Irkutsk Time (Q2347353) and UTC+08:00 (Q6985) and backwards. We could increase the expressiveness of both items by having a new property as proposed. -- T.seppelt (talk) 14:21, 10 July 2016 (UTC)
Support My first thought was to use the "same as" property, but this might be overloaded.
--- Jura 22:51, 2 August 2016 (UTC)
Oppose per ChristianK and my earlier comments - we should change the constraints if needed. said to be the same as (P460) is the wrong property for this per my earlier comments. Thryduulf (talk) 21:09, 15 August 2016 (UTC)
@T.seppelt, Thryduulf, ChristianKl, Pasleim, Jura1: 
Not done, no consensus. Widening the constraints on UTC timezone offset (P2907) seems to be the preferred solution. --Srittau (talk) 11:54, 23 August 2016 (UTC)