Re: [Json] Counterproposal #2 on work items

[Paul Hoffman <[e-mail]>]

On Feb 21, 2013, at 11:05 AM, Joe Hildebrand (jhildebr) <[e-mail]> wrote:

> On 2/20/13 10:15 PM, "Robert Sayre" <[e-mail]> wrote:
> 
>> There is a lack of interoperability, and this issue is one of the smaller
>> points. The larger point is that the JS implementations (and many smaller
>> ones) have no incentive to change their behavior, and what they do is
>> reasonable. Let's just
>> do that.
> 
> How about text like this for section 2.2:

Wrong thread. This thread is for "only product a best practices guide".

I bring this up because there is a huge difference between:
- Changing the requirements in the format specification
- Adding new processing rules, but allowing bad-idea data, in the format document
- Not touching the format specification and creating a best practices guide

Further, as we have discovered in many other areas of the IETF, there is a huge difference between:
- A format specification that is unclear on how to process illegal input
- A format specification that says processors must reject illegal input
- A format specification that says how processors handle legal-but-bad-idea input

--Paul Hoffman