Re: [Json] Two Documents

[Vinny A <[e-mail]>]

On Jun 17, 2013, at 7:14 PM, "Matt Miller (mamille2)" <[e-mail]> wrote:

> Hello Douglas,
> 
> In order for the WG to fully understand your proposal, we need a more definitive list of what to expect in each document.
> 
> As a starting point, can you describe which sections of the current RFC4627 would be in "JSON Data Interchange Format" and which would be in the JSON best practices document?  Clearly the latter will have many additions from the recent discussions, but it is less clear which portions of the current text goes into which document.


Obviously I'm not Douglas, but I'd like to make a proposal in this department.

The simplicity of the JSON standard has proven to be one of the many reasons why it's so popular. It would be a shame if we ended up bloating the official standard with miscellaneous nitpicks and advice. Clearly the standard needs some touch-up work (duplicate keys, for instance) - but it should be limited to just that, touch up work.

Everything else should be reserved for the best practices document; basically the rule of thumb would be that any new topics should be moved to best practices, while any current topics in the RFC should stay. Here's a short list of potential best practice topic candidates (additions/deletions welcome): 

- Unicode processing
- Runtime/Wire format recommendations
- Streaming parser recommendations
- Additional MIME types
- Comments
- String comparison
- Miscellaneous

-----------------
Vinny
www.jsontest.com