Re:RFC 3339 vs. ISO 8601
by ivan_gammel on Thursday August 31, 2023 @02:04PM
(#37341323)
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:
[ Parent
| on HN ]
Re:RFC 3339 vs. ISO 8601
by codetrotter on Thursday August 31, 2023 @02:09PM
(#37341404)
Country borders can change, city divisions can change. Street names can change, and streets can disappear.
Use GPS coordinates instead :D
That won't help if the Bundestag moves into another building. If country borders change, that is also likely to occur :D
Nice idea in theory, but then you need to accommodate for continental drift as well :)
Re:RFC 3339 vs. ISO 8601
by ivan_gammel on Thursday August 31, 2023 @06:30PM
(#37344462)
I was expecting that comment and this would be my preferred answer.
Re:RFC 3339 vs. ISO 8601
by ivan_gammel on Thursday August 31, 2023 @06:28PM
(#37344452)
Not 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.
Yes 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.
Places do not necessarily have a single agreed timezone - see Xinjiang (or indeed Crimea).
Well 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.