Hacker GitHub

← All repos

tjson/tjson-spec

View on GitHub ↗ ★ 64 HTML

IETF-style specification and test cases for TJSON

15 mentions on Hacker News by 2 people: 0 stories, 15 comments · first 2016-11-02 · latest 2017-04-26

Mentions per year 15 mentions · busiest year 2016 (13)
20082026
  1. …token, presumably repeated names in an object would be rejected by the parser. Correct: https://github.com/tjson/tjson-spec/blob/master/draft-tjson-... https://www.tjson.org/spec/#rfc.section.3.8
  2. …://www.w3.org/TR/xmlschema11-2/#built-in-datatypes I briefly considered adopting this work wholesale: https://github.com/tjson/tjson-spec/issues/37 If you'd like to see that happen, please make a note of it in the issue. Thanks! Also note:…
  3. …a concrete proposal for moving type signatures exclusively to a postfix tag on object keys here: https://github.com/tjson/tjson-spec/issues/30
  4. I've opened an issue about using tagged strings for floats here: https://github.com/tjson/tjson-spec/issues/32
  5. …of machine-readable examples which are intended to cover JSON's present underspecified edge cases: https://github.com/tjson/tjson-spec/blob/master/draft-tjson-...
  6. …"Unicode String", but moved to using "UTF-8 String", the rationale for which is given here: https://github.com/tjson/tjson-spec/issues/27 If your intent is to actually effect a change in the specification, that is the proper place to do…
  7. Please see this issue for homogenous typing of arrays: https://github.com/tjson/tjson-spec/issues/23 Also based on the feedback I've received, I'm putting together a full proposal for moving all type information to object keys, and fully…
  8. TBD: https://github.com/tjson/tjson-spec/issues/23
  9. …format, as opposed to all the binary formats named in the post, including CBOR. See also: https://github.com/tjson/tjson-spec/issues/26 TJSON could potentially provide non-lossy transcoding to/from the similarly tagged types in CBOR in…
  10. …of the same type. A better place to discuss ambiguities in the spec regarding this issue is here: https://github.com/tjson/tjson-spec/issues/27 The idea that different on-the-wire representations of an object correspond to the same typed…
  11. …expected failure in the boundary cases) is specified in the canonical test cases/examples file: https://github.com/tjson/tjson-spec/blob/master/draft-tjson-... 2) Please see https://github.com/tjson/tjson-spec/issues/27 3) Yes, these…
  12. …between data types (Unicode, rational numeric) and data representations (UTF-8, IEEE double). [1] https://github.com/tjson/tjson-spec/blob/master/draft-tjson-...
  13. …members in the names instead of the values, there's an open issue on the GitHub repo for the spec: https://github.com/tjson/tjson-spec/issues/28 Regarding MIME types, since the format is JSON-compatible I would prefer it remain…
  14. …for non-scalars is still an open issue, and is probably the best place to further discuss this: https://github.com/tjson/tjson-spec/issues/23 As an aesthetic note: I personally find "$" visually noisy as a sigil, and think it has generally…
  15. …of homogenous types, and objects were the only allowed nonterminal allowed by the root symbol. See: https://github.com/tjson/tjson-spec/issues/23