[00:05:10] <wm-bb>	 <Al> 🤔 Maybe the “comprehensive” list is too long… We might consider offset buckets, or just offsets? (re @u99of9: Yes, I am coming around to that idea too. Sorry, this should work. It looks like some on-wikidata work would be useful before ch...)
[00:09:47] <wm-bb>	 <u99of9> Many initial values will come from P421 statement values. The crucial question is how well we can then map them to canonical values or offsets. (re @Al: 🤔 Maybe the “comprehensive” list is too long… We might consider offset buckets, or just offsets?)
[00:16:22] <wm-bb>	 <u99of9> But the daylight savings issue means that it's still worth having options for a timezone (like mine) which switches between offsets. Then we need functions that can determine when to switch!
[08:26:54] <wm-bb>	 <Al> …and navigate the administrative territory hierarchy to get to the entity with the relevant P421 🥴 (re @u99of9: Many initial values will come from P421 statement values on administrative district items. The crucial question is how well we c...)
[10:39:42] <wm-bb>	 <u99of9> That's exactly why I threw this suggestion in! (re @u99of9: Is Qid1 a wdt:P279*/wdt:P31 of Qid2?)
[10:48:49] <wm-bb>	 <Al> Ah… it’s not clear to me that that is a solution, but I’m not saying it’s not! (re @u99of9: That's exactly why I threw this suggestion in!)
[10:53:04] <wm-bb>	 <u99of9> You are right, it's just a similar need that we use all the time on was, so I suggested it for Z30000 even though wdt:P131*/wdt:P421 is more immediately necessary. (re @Al: Ah… it’s not clear to me that that is a solution, but I’m not saying it’s not!)
[11:14:32] <wm-bb>	 <Al> It’s the nested indirection that troubles me. Perhaps we have a shortlist enumeration of countries with more than one time zone, so we can generally go via the P17? (re @u99of9: You are right, it's just a similar need that we use all the time on was, so I suggested it for Z30000 even though wdt:P131*/wdt:...)