3 ms·
It’s LocalDateTime AND geographic coordinates, not a name of a timezone. Maybe we need an ISO standard for universally accepted location/event identifiers or an
by ivan_gammel 3y ago
It’s LocalDateTime AND geographic coordinates, not a name of a timezone. Maybe we need an ISO standard for universally accepted location/event identifiers or an URI schema, eg:
event://de/Berlin/10557/Platz+der+Republic,+1/Bundestag#2030-08-30T18:00
- codetrotter 3y agoCountry borders can change, city divisions can change. Street names can change, and streets can disappear. Use GPS coordinates instead :D
- rini17 3y agoThat won't help if the Bundestag moves into another building. If country borders change, that is also likely to occur :D
- lxgr 3y agoNice idea in theory, but then you need to accommodate for continental drift as well :)
- ivan_gammel 3y agoI was expecting that comment and this would be my preferred answer.
- ivan_gammel 3y agoNot instead, but in addition to. Maybe 3rd element of the vector must be the moment when the identifier was created, so that knowing history of the location it could be possible to adjust it to the current coordinates.
- jameshart 3y agoYes the basic problem here is that people for some reason think that a time zone is a property of a time when in fact a time zone is a property of a place. It’s actually a mutable property of a place, to make things more complex.
- lmm 3y agoPlaces do not necessarily have a single agreed timezone - see Xinjiang (or indeed Crimea).
- jameshart 3y agoWell that’s more a case of there being more than one authority who claims to be the source of truth for answering the question ‘what is the time zone offset in that location at this point in time’… International disputes make it difficult to answer a lot of questions about specific locations without making choices about which authorities you’re willing to respect.