-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
In message <[email protected]>, Vittorio
<[email protected]> writes
>I should add that Richard has stated he will add text to the
>specification forbidding duplicate keys. That closes this particular
>vector and I think that is the right fix.
Real Soon Now
>My concern is the class rather
>than the instance: numeric type coercion
the JSON schema uses "integer" not "number" so I don't understand what
your concern might be
If someone turns up with an "integer" which is 5.50000000000001 and you
are worried that rounding may send it to 5 or to 6 then you should get
yourself some software that pays attention to what the schema says...
>and tolerated malformed input
if your JSON parser tolerates malformed input and someone gives you
malformed input then I agree that you might process an email rather than
rejecting it out of hand -- I don't think JSON is the issue here, if any
of your code doesn't do what it is supposed to you will have problems
- --
richard @ highwayman . com "Nothing seems the same
Still you never see the change from day to day
And no-one notices the customs slip away"
-----BEGIN PGP SIGNATURE-----
Version: PGPsdk version 1.7.1
iQA/AwUBaqryDWHfC/FfW545EQJHOgCbB/5WJlHQJfx8QWKbYKhdc4mjeeoAoLsH
iB/GAskD/SNZgIu2HZ+1lmmR
=4Z7x
-----END PGP SIGNATURE-----
_______________________________________________
Ietf-dkim mailing list -- [email protected]
To unsubscribe send an email to [email protected]
