You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the current XSD, times are just defined as xsd:datetime.
While in many local stationXML documents, fdsn/station responses, no time zone is given and seismologists may implicitly assume that times are in UTC, the XMLSchema standard actually says on the data type xsd:datetime:
"If no time zone value is present, it is considered unknown; it is not assumed to be UTC." - times with unknown timezones are not very useful for the user.
Moreover: The character strings allowed in xsd:datatimes (e.g. 2004-04-12T13:20:00) look like ISO 8601-formatted time strings. However, ISO 8601 says: "If no UTC relation information is given with a time representation, the time is assumed to be in local time." - if a client interprets such a time without time zone e.g. using the standard java implementation of ISO 8601 time parsing, (s)he will get a time object with the time zone according to the locale of his machine.
To avoid these ambiguities I would suggest that all times should be given in UTC explicitly, and hence all time stamps have a respective zone mark ("...Z")
The text was updated successfully, but these errors were encountered:
kaestli
changed the title
Require times to be in UTC (...Z)
Require DateTimes to be in UTC (...Z)
Dec 16, 2021
In the current XSD, times are just defined as xsd:datetime.
While in many local stationXML documents, fdsn/station responses, no time zone is given and seismologists may implicitly assume that times are in UTC, the XMLSchema standard actually says on the data type xsd:datetime:
"If no time zone value is present, it is considered unknown; it is not assumed to be UTC." - times with unknown timezones are not very useful for the user.
Moreover: The character strings allowed in xsd:datatimes (e.g. 2004-04-12T13:20:00) look like ISO 8601-formatted time strings. However, ISO 8601 says: "If no UTC relation information is given with a time representation, the time is assumed to be in local time." - if a client interprets such a time without time zone e.g. using the standard java implementation of ISO 8601 time parsing, (s)he will get a time object with the time zone according to the locale of his machine.
To avoid these ambiguities I would suggest that all times should be given in UTC explicitly, and hence all time stamps have a respective zone mark ("...Z")
The text was updated successfully, but these errors were encountered: