News for hackers. Stuff that matters.

A comment on The I-JSON Message Format. Parent comment

Re:The I-JSON Message Format by tomchristie on Monday March 23, 2015 @01:13PM (#9252019)
> I-JSON doesn't appear to solve this problem

It's not within the scope of what I-JSON is intended to address. This is a more formally specified and slightly more constrained variation of the existing JSON spec. Adding new datatypes would mean that it would no longer be JSON.

[ Parent | on HN ]
Re:The I-JSON Message Format by thom_nic on Monday March 23, 2015 @01:42PM (#9252221)
I'll agree there aren't many ways this could be solved without breaking compatibility with JSON. Certainly something like {"created": Date("2013-12-1T12:00:00Z")} a la BSON seems elegant but is incompatible with JSON.

Maybe something like "String values that match (some computationally inexpensive ISO-8601-matching regex) shall be converted to Date instances by the JSON parser" could be possible without huge compatibility issues.

I guess I was mostly using this topic to voice what I'd imagine is a common point of frustration in an otherwise great data interchange format.

[ Parent | on HN ]
Re:The I-JSON Message Format by stouset on Monday March 23, 2015 @04:14PM (#9253103)
No, definitely don't do that. You're just trading one set of small annoyances for a huge set of unpredictable problems.
[ Parent | on HN ]