function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion

Datetime formats in JSON data



I'm getting datetime data back in my objects in the following format:




This is not quite the same as what is specified in the api spec at - which specifies a colon in the timezone offset.


My perl ISO 8601 parser doesn't accept this, and I've been advised that the although the ISO standard supports the use of colons in time separators, and supports missing them out, it doesn't support mixing the two in the same timestamp.


specifically: "Referring to ISO 8601:2004.  Clauses 2.3.3 and 2.3.4, defining "basic format" and "extended format", apply the concept to an entire date-and-time representation, rather than to segments of it, and doesn't mention any possibility of mixing the formats.  Clasue, defining how to represent local time together with UT offset, separately shows

basic and extended formats where separator usage matches, and doesn't give any explicit permission to mismatch them.  Clause 4.3, on combining date with time of day, behaves similarly."


Is this a small bug in the formatting? Currently I'm looking at having to write my own parser to work around this.








+1 ... causing issues with the standard .NET Framework Convert.ToDateTime()... replacing a "+" or ":" before the offset fixes it... but annoying...