I-JSON can mess with big numbers and we can't constrain the range.
We don't want to mandate bigint support on anyone. We don't want
to make non-JSON serializers/parsers have to worry about stringified
numbers - so modifying the CDDL directly seems off.
There's lots of ways that implementations can internally handle values,
we don't care much about that here. For interop, settle on allow JSON parsers
to write uint64 as strings if they want to. Make it clear that parsers
should expect that, unless they have some non-standard way of knowing.
Alternative to #359.
I-JSON can mess with big numbers and we can't constrain the range. We don't want to mandate bigint support on anyone. We don't want to make non-JSON serializers/parsers have to worry about stringified numbers - so modifying the CDDL directly seems off.
There's lots of ways that implementations can internally handle values, we don't care much about that here. For interop, settle on allow JSON parsers to write uint64 as strings if they want to. Make it clear that parsers should expect that, unless they have some non-standard way of knowing.
Fixes #229