> So, we just use JSON, and our solution to this problem has been to pass 64 bit unix timestamps around. Passing an integer does not have the same semantics as

> So, we just use JSON, and our solution to this problem has been to pass 64 bit unix timestamps around. Passing an integer does not have the same semantics as passing a timestamp. Relying on out-of-band info to parse a document is a problem in the making. > but for most use cases it is more than enough practical range & precision to get the job done. Parsing s-expressions would also get the job done, even if it's a primitive s-expression that only supports cons cells and a string data type. However, people find value in enabling the parser to validate booleans, arrays, and objects. ION is just a logical next step. Timestamps are quite naturally a fundamental data type in comm between web services, particularly in binary form.