Re: [Json] RFC 4627bis vs RFC 6902 (JSON Patch)

[Francis Galiegue <[e-mail]>]

On Thu, Feb 20, 2014 at 6:31 PM, Barry Leiba <[e-mail]> wrote:
>> The latter makes sense on the _producer_ of a patch operation;
>> however, on the parser side, should a parser receive a "malformed"
>> (f.e duplicated "op") operation, it seems to me that RFC 6902 expects
>> the parser to raise an error -- which RFC 4627bis does not mandate.
>
> What do you see as a conflict?
>
> The JSON spec gives general parameters for JSON, and allows duplicates.
>
> The JSON Patch spec gives specific parameters for a specific use of
> JSON.  For that use, duplicates are not allowed.
>
> That all looks just fine to me, and absolutely consistent.
>

Not to me. As I see it, 75+% of JSON parsers on the "market" just
cannot parse JSON Patch correctly because of the restrictions imposed
by RFC 6902. Note: parse, not emit (or "consume, not produce" -- or
whatever metaphor suits you).

IOW: I don't see "MUST have a unique member named 'foo'" and
"behaviour is unpredictable" as being consistent with one another.

-- 
Francis Galiegue, [e-mail]
JSON Schema in Java: http://json-schema-validator.herokuapp.com