Cobalt Standards for dates in JSON

Does Cobalt have any standards for how dates should be represented in JSON data? I have a few options, I could go with the number of milliseconds since January 1 1970 UTC or ISO 8601, or something like that, but I’d like to be consistent with what the rest of Cobalt is doing if there is a standard.

Find more posts tagged with

json

refinitiv-internal

Accepted answers

Ryan Morlok

GRC never heard back an authoritative answer on this question and we decided to go with the number of milliseconds since Jan 1 1970 UTC because it was easy to work with it in Javascript.

**UPDATE:**

While we never got a formal response and we proceeded using the representation as described above, it looks like ISO 8601 seems to be one of the standards Cobalt Website expects. See JsonDotNetSerializer.cs, line 292:

[$/Cobalt Website/Development/App/Platform/Serialization/JsonDotNetSerializer.cs][1]

[1]: http://tfsnpt.int.thomson.com:8080/tfs/web/UI/Pages/Scc/ViewSource.aspx?path=$/Cobalt Website/Development/App/Platform/Serialization/JsonDotNetSerializer.cs&cs=184194&pguid=865373ee-51f3-4e25-a9fa-834796430ed2

All comments

Ryan Morlok

Michael Vellucci

Data Room and UDS have been using the ISO 8601 standard. If in Java, the Joda Time package is very useful for handling these conversions between Java Date and the ISO 8601 standard.

EXPLORE OUR SITES