Re:Hacker News API doesn't obey RFC 4627
by namecast on Wednesday October 08, 2014 @04:24PM
(#8429255)
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. The ambiguity is definitely removed in the updated version.)
Re:Hacker News API doesn't obey RFC 4627
by MalcolmDiggs on Wednesday October 08, 2014 @04:54PM
(#8429410)
If 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.
Re:Hacker News API doesn't obey RFC 4627
by sarciszewski on Thursday October 09, 2014 @09:13AM
(#8432121)
{"key": null}
vs
null
I'm pretty sure they're both valid.
per the RFC,
"JSON can represent four primitive types (strings, numbers, booleans, and null) and two structured types (objects and arrays)."
"An object is an unordered collection of zero or more name/value pairs, where a name is a string and a value is a string, number, boolean, null, object, or array."