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
One limitation of JSON is that it does not support any type of date. Dates can be encoded as a number containing a unix timestamp, or as a string containing an ISO Date string. Since using dates is such a common use case, it may be good to implement support for it.
Tabular-JSON can implement a part of the ISO 8601 standard for this. There are quite some variations of date/time/seconds/milliseconds/timezone due to a lot of optional parts, so we have to be careful on what to support exactly. The complexity can grow quite fast here. And the more complex the data format is, the more effort is needed to implement a parser for Tabular-JSON and to understand what it can/can't understand. We have to balance the pros/cons here.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
One limitation of JSON is that it does not support any type of date. Dates can be encoded as a number containing a unix timestamp, or as a string containing an ISO Date string. Since using dates is such a common use case, it may be good to implement support for it.
An example can look like:
Tabular-JSON can implement a part of the ISO 8601 standard for this. There are quite some variations of date/time/seconds/milliseconds/timezone due to a lot of optional parts, so we have to be careful on what to support exactly. The complexity can grow quite fast here. And the more complex the data format is, the more effort is needed to implement a parser for Tabular-JSON and to understand what it can/can't understand. We have to balance the pros/cons here.
Complexity: High
Added value: High
Beta Was this translation helpful? Give feedback.
All reactions