IETF Logo Mail Archive

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

Barry Leiba <barryleiba@computer.org> Thu, 20 February 2014 17:31 UTC

Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B9D81A025D for <json@ietfa.amsl.com>; Thu, 20 Feb 2014 09:31:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level:
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j-RmL-Br04_e for <json@ietfa.amsl.com>; Thu, 20 Feb 2014 09:31:10 -0800 (PST)
Received: from mail-vc0-x231.google.com (mail-vc0-x231.google.com [IPv6:2607:f8b0:400c:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id B96221A0252 for <json@ietf.org>; Thu, 20 Feb 2014 09:31:10 -0800 (PST)
Received: by mail-vc0-f177.google.com with SMTP id if11so2117560vcb.22 for <json@ietf.org>; Thu, 20 Feb 2014 09:31:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=XMwoBb9T//p5JCC8QwHKWPiKzxm6JSAHR69cLxNYLzA=; b=I6BsiHw3FD02efD4JJuTdos+Id69T1es+FZ/0uM2Cb8oT0UnhIj5yggcvHO0bM0V8H EJkf3zs5l6K9YDASK9VI1mqjy2MtCnDfY1Nu7GcWywQDAzY45/GiyTr0YnCyHEv0udIu WYoNlDLbGatVOxL/uxHMz/vXcvZE+lvqvcVpch+Xo9fc0uSWqbzB04sMopHHRKovClPY uadySGcHulI9kWh5kDxaZxtuRZrZv/M0zcgmJIz7K34/NMHRhGaQzBmLCVC+1du/8BEf wIOtSyCDfeSEJSApmpf6HrnR//TZY5Ry3XAHKtqyxZ+YHME15dUyShsnyMzPcVnrFove jJgg==
MIME-Version: 1.0
X-Received: by 10.52.246.227 with SMTP id xz3mr1391596vdc.95.1392917466977; Thu, 20 Feb 2014 09:31:06 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.58.19.104 with HTTP; Thu, 20 Feb 2014 09:31:06 -0800 (PST)
In-Reply-To: <CALcybBCTih9A6RL=r4WYrqf05rHsjgF4tEJP3cTY2FAmONRQaw@mail.gmail.com>
References: <CALcybBCTih9A6RL=r4WYrqf05rHsjgF4tEJP3cTY2FAmONRQaw@mail.gmail.com>
Date: Thu, 20 Feb 2014 12:31:06 -0500
X-Google-Sender-Auth: 5QcOXAWoLygQMyLq7v1s6zLUShk
Message-ID: <CAC4RtVD5J2oeTQGDNW5=M1oO4MuY_7i7z9G1Q=+icLr9su8aUQ@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Francis Galiegue <fgaliegue@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Archived-At: http://mailarchive.ietf.org/arch/msg/json/hfuqXQcFz0zu6KTGvujbv1b63b8
Cc: "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] RFC 4627bis vs RFC 6902 (JSON Patch)
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <json.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json>, <mailto:json-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/json/>
List-Post: <mailto:json@ietf.org>
List-Help: <mailto:json-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json>, <mailto:json-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Feb 2014 17:31:12 -0000

> 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.

Barry

v2.23.0 | Report a Bug | By Email