@bascule @sergeybratus @maradydd I.e. if application uses the conventional "last key wins", infinite docs with same meaning.
-
-
Replying to @judsonlester
@judsonlester@sergeybratus@maradydd JSON keys should probably be represented as a list, and not as a hash. Latter enables hashDoS2 replies 0 retweets 1 like -
Replying to @bascule
@bascule@sergeybratus@maradydd Agreed, but a) spec is silent on field-name semantics and b) I know of no impl that does treat them as list2 replies 0 retweets 0 likes -
Replying to @judsonlester
@judsonlester@bascule@sergeybratus agreed, that is a spec bug in JSON.3 replies 0 retweets 1 like -
Replying to @maradydd
@maradydd@judsonlester@bascule Just the kind of a bug on the semantic "back end" API of an otherwise well-defined input language --1 reply 0 retweets 0 likes -
Replying to @sergeybratus
@sergeybratus@maradydd@bascule One thing that's been bugging me: if keys are req'd to be unique, no longer context-free, right?1 reply 0 retweets 0 likes -
Replying to @judsonlester
@judsonlester@maradydd@bascule I'd say, not when posed as a syntactic req. A recognizer would save this check till final semantic action.1 reply 0 retweets 0 likes -
Replying to @sergeybratus
@sergeybratus@maradydd@bascule Pedantically: "unique keys" makes the language at least context sensitive though, right?1 reply 0 retweets 0 likes -
Replying to @judsonlester
@judsonlester@maradydd@bascule So far as I can see, yes.1 reply 0 retweets 0 likes -
Replying to @sergeybratus
@sergeybratus@maradydd@bascule I ask because a langsec site recco'd JSON, which never sat right2 replies 0 retweets 0 likes
@judsonlester @sergeybratus @maradydd there are many places I use JSON in secure contexts today, like JOSE-JWT
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.