21 ms·
Hrmm. Later on it is explained: 2.1. Values A JSON value MUST be an object, array, number, or string, or one of the following three literal names:
by namecast 12y ago
Hrmm. Later on it is explained:
2.1. Values
A JSON value MUST be an object, array, number, or string, or one of
the following three literal names:
false null true
... so what you're receiving is technically a valid JSON value according to the RFC, no?
(I am so sorry for being this pedantic - but that RFC is marked 'informational', it's not actually a standard so much as a suggestion, and even worse, RFC 7159 obsoletes it and is an IETF standards track document - check out http://tools.ietf.org/html/rfc7159 http://tools.ietf.org/html/rfc7159. The ambiguity is definitely removed in the updated version.)
- MalcolmDiggs 12y agoIf I'm reading it correctly: "null" would be a valid value, but a key/name would still need to be specified. So a blank document with the word "null" on it is invalid because the value of null has no key... but again, I may be reading it wrong.
- sarciszewski 12y ago{"key": null} vs null I'm pretty sure they're both valid.