IETF Logo Mail Archive

Re: [Json] Fwd: JSON Content Rules

Pete Cordell <petejson@codalogic.com> Thu, 25 January 2018 09:15 UTC

Return-Path: <petejson@codalogic.com>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2697912E870 for <json@ietfa.amsl.com>; Thu, 25 Jan 2018 01:15:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 kVoa9LuP4rZC for <json@ietfa.amsl.com>; Thu, 25 Jan 2018 01:15:53 -0800 (PST)
Received: from ppsa-online.com (ppsa-online.com [217.199.162.192]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D46A512DA08 for <json@ietf.org>; Thu, 25 Jan 2018 01:15:52 -0800 (PST)
Received: (qmail 22137 invoked from network); 25 Jan 2018 09:06:07 +0000
Received: from host86-137-73-204.range86-137.btcentralplus.com (HELO ?192.168.1.72?) (86.137.73.204) by lvps217-199-162-217.vps.webfusion.co.uk with ESMTPSA (DHE-RSA-AES128-SHA encrypted, authenticated); 25 Jan 2018 09:06:07 +0000
To: Daniel P <danielaparker@gmail.com>, JSON WG <json@ietf.org>
References: <CA+mwktJU4xVHxRzgd=dcCKvUv3Om3qeBEhqTaW2sniLQ95+QDA@mail.gmail.com> <a36fc644-d3be-201e-b044-ed371fe7e52b@codalogic.com> <CA+mwktJ-YZBGExPeCTxCcwo6F1Ln5ZaDajRMOnm=RimUxnFqnQ@mail.gmail.com> <dbca1021-72ed-8c5f-7849-33f12bc420eb@codalogic.com> <CA+mwktL7zfs0BLjcgjwOBk9my75A958sJc_vzMTdfLp39Xe_rA@mail.gmail.com> <CA+mwktJo9pDou1Uk-E_qGTkp4z3Sy0zUy7iGzov14m2BJUTMUQ@mail.gmail.com>
From: Pete Cordell <petejson@codalogic.com>
Message-ID: <794516b0-4579-51f8-50c8-7356bb200ab9@codalogic.com>
Date: Thu, 25 Jan 2018 09:15:49 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <CA+mwktJo9pDou1Uk-E_qGTkp4z3Sy0zUy7iGzov14m2BJUTMUQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-GB
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/g8j7WG5dGVviz2xv1GiJRlgQCHg>
Subject: Re: [Json] Fwd: JSON Content Rules
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 25 Jan 2018 09:15:56 -0000

On 24/01/2018 17:51, Daniel P wrote:
> On Wed, Jan 24, 2018 at 11:09 AM, Pete Cordell <petejson@codalogic.com 
> <mailto:petejson@codalogic.com>> wrote:
> 
>  > JCR works in terms of rules ... JCR doesn't do macro substitution.
> 
> Of course, but the issue is whether the grammar needs to distinguish 
> between name rule specifications and
> value rule specifications. I don't think that it does, and I don't think 
> that that provides any meaningful benefit to
> the user, compared to the loss in simplicity of the syntax. That's just 
> my opinion, of course, but I would be
> interested to see what others on the list think.

I too am interested in the opinions of the group.  Maybe I'm being over 
cautious?

Pete.
http://www.xml2cpp.com

v2.23.0 | Report a Bug | By Email