Closed barthanssens closed 3 years ago
Would the PO have a best practice for this context @costezki ? And hopefully you don't mind I drag you into these discussions, your input is very much appreciated!
If there is a way to recover the TZ from another part of the description, then fine, functionality can be set in place to update/correct the TZ where it is missing (relevant fields with timestamp, time and dateTimes datatype).
If the TZ information is not critical then I would rely on the fallback interpretation that then missing TZ is, in fact, the Coordinated Universal Time (or UTC).
Without knowing the context of the project, I would go for the latter, unless the former is a necessity.
when a document is digitally signed, the information of the time zone is mentioned. See for example
the same rational can be used here
The original question was about recovering the TZ in situations when the TZ is not explicitly mentioned. The case above shows that the TZ is available in the data.
Could be out of scope, and is probably obvious, but whenever a date / timestamp is provided, I assume the default timezone will be the local one, where the event happens, if no TZ is explicitly provided ?
I.e.: