[Python-ideas] Serialization of CSV vs. JSON

[Wes Turner]

JSON-LD supports datetimes (as e.g. IS8601 xsd:datetimes)
https://www.w3.org/TR/json-ld11/#typed-values

Jsonpickle (Python, JS, ) supports datetimes, numpy arrays, pandas
dataframes
https://github.com/jsonpickle/jsonpickle

JSON5 supports comments in JSON.
https://github.com/json5/json5/issues/3

... Some form of schema is necessary to avoid having to try parsing every
string value as a date time (and to specify precision: "2018" is not the
same as "2018 00:00:01")

On Friday, November 2, 2018, Chris Barker via Python-ideas <
python-ideas at python.org> wrote:

> On Fri, Nov 2, 2018 at 9:31 AM, M.-A. Lemburg <mal at egenix.com> wrote:
>
>> Serialization of those data types is not defined in the JSON standard:
>>
>> https://www.json.org/
>
>
> That being said, ISO 8601 is a standard for datetime stamps, and a defacto
> one for JSON
>
> So building encoding of datetime into Python's json encoder would be
> pretty useful.
>
> (I would not have any automatic decoding though -- as an ISO8601 string
> would still be just a string in JSON)
>
> Could we have a "pedantic" mode for "fully standard conforming" JSON, and
> then add some extensions to the standard?
>
> As another example, I would find it very handy if the json decoder would
> respect comments in JSON (I know that they are explicitly not part of the
> standard), but they are used in other applications, particularly when JSON
> is used as a configuration language.
>
> -CHB
>
>
> --
>
> Christopher Barker, Ph.D.
> Oceanographer
>
> Emergency Response Division
> NOAA/NOS/OR&R            (206) 526-6959   voice
> 7600 Sand Point Way NE   (206) 526-6329   fax
> Seattle, WA  98115       (206) 526-6317   main reception
>
> Chris.Barker at noaa.gov
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-ideas/attachments/20181102/37320412/attachment-0001.html>