I would like to summarize my current thoughts about thefold next draft
of JSON specification:

- I will add support of JSON Sequence RFC 7464

- I am willing to drop json-tokens and json-generator because they are
too low level and specific about the actual JSON parsing algorithm

- I may add a limit on the count of characters just as reminder that
it possible to shoot yourself in the foot while reading some JSON text

- It seems to me, it possible to parse json objects into scheme
records with the current implementation of json-fold

- The depth limit is easier to setup than the characters limit, so I
want to keep it. I agree depending on the Scheme implementation,
+inf.0 may be too big, the actual value is implementation specific,
the specification suggest +inf.0

Also, most importantly, even if the sample implementation pass all the
tests, I found a bug while parsing JSON lines [0] so it might a good
thing to go through a JSON fuzzer but I did not find one yet. Fixing
the bug discovered with JSON lines, lead to a new implementation of
json-read (that use json-fold) and the specification should be
updated.

Also, I would be very glad to have more feedback on json-fold specification.

[0] https://github.com/amirouche/srfi-180/commit/7d69b70a01008ecaffb840a3d6bdd730889d3006