Re: [Json] JSON Content Rules -05

Andrew Newton <andy@hxr.us> Fri, 18 March 2016 14:50 UTC

Return-Path: <andy@hxr.us>
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 0DAB712D721 for <json@ietfa.amsl.com>; Fri, 18 Mar 2016 07:50:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hxr-us.20150623.gappssmtp.com
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 7rBGtrJZkLgI for <json@ietfa.amsl.com>; Fri, 18 Mar 2016 07:50:13 -0700 (PDT)
Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E50F12D64B for <json@ietf.org>; Fri, 18 Mar 2016 07:50:12 -0700 (PDT)
Received: by mail-wm0-x234.google.com with SMTP id p65so40788647wmp.0 for <json@ietf.org>; Fri, 18 Mar 2016 07:50:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hxr-us.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=ReMutNvIanJfI28SOoRh7jRHbWRlj8sdFGMzPtyZxV8=; b=W0BqkpcvlBnkVbcrnZeYVD+XF75SXGsjFTBolxoe2vPWqTgahsHMRXoCbu4oXnenMN piQd12w00UX1z2g+4COL2LHvWJE9C3yZTCdHlSnLbB/YewlCO2ETSfgng1nhocrrDG4M EgIB8+h9s++7uhcCdg9ZO5i/0TeQPKzJeG+cbr+A53+9oZJ9Jn0tsb8BGmbXEPEX6LLL mb7wjBDeBVc/hngIsexI8Ut2DZ93qee6d0FmHN9mfbpQSo+9M6qTel6RdmIdxkGeQakB Ofn50nOwHgj5rToRI6CBjFi7oi2XFnTxWA560SK9mnc4YEKYL4VNJ98Xxv1Hb/33fXHR 9ySg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=ReMutNvIanJfI28SOoRh7jRHbWRlj8sdFGMzPtyZxV8=; b=Fg92SBhO/aRc2sG0GMLlKizofevUZCHb/p+RjR2YywXcEzZ/fJR5n4CmTSbvPeBZTe u6FkIuFXN02o2H2A3qeJAO32GKZPjAXkdPZs1eEzZSFBWtzsE/P3gVnhB93as0AdjHW1 2cEfVhkHS3oFqEUYCPC5/zP0wRXiTjuYtpwQau5d5TWUWFRCZHmchiXyQfcFHZE0BjmZ i3aSMoCUGRVMYToC9m8mOcM1podErHJrYtngPUc3hKShibLYToOuATqfhKsnFqE2kI4N dfUU3vnMW9zbqMj7ZRviBxDQ4zyQQVkT+RnYAv4Hog9sHRU1L3iEGeRRXsnTIinvRmB+ I95Q==
X-Gm-Message-State: AD7BkJKI6V3gNF1+3ccYZK8kQdqYepxM4JRWpqIlmkIIYfVIJLQo6ZC0MOwDr9jfP/W3EgF4UjIPuxZDD5I5cA==
MIME-Version: 1.0
X-Received: by 10.194.121.194 with SMTP id lm2mr16417413wjb.71.1458312610702; Fri, 18 Mar 2016 07:50:10 -0700 (PDT)
Received: by 10.194.41.131 with HTTP; Fri, 18 Mar 2016 07:50:10 -0700 (PDT)
X-Originating-IP: [108.45.68.2]
In-Reply-To: <CA+mwktLxkDuGXGm083N4WK05mNVPg6R5SQ_5b5X5GckJR-mF2w@mail.gmail.com>
References: <CA+mwktLxkDuGXGm083N4WK05mNVPg6R5SQ_5b5X5GckJR-mF2w@mail.gmail.com>
Date: Fri, 18 Mar 2016 10:50:10 -0400
Message-ID: <CAAQiQRdajFBwcLP+HxAjKE5v+1qX3DC4kS0piRO5VqKaTm5pyQ@mail.gmail.com>
From: Andrew Newton <andy@hxr.us>
To: Daniel Parker <danielaparker@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/json/rguJgTwKlIHiWPvJEse_i25lHoU>
Cc: JSON WG <json@ietf.org>
Subject: Re: [Json] JSON Content Rules -05
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.17
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: Fri, 18 Mar 2016 14:50:15 -0000

Daniel,

Actually we realized that too. The -06 version, which should be out
soon, has an updated ABNF to allow the colon before object and array
rule definitions.

However, it is still needed for value rules so a parser can tell the
difference between a value rule and a rule name.

-andy

On Fri, Mar 18, 2016 at 10:29 AM, Daniel Parker <danielaparker@gmail.com> wrote:
> Regarding JCR - 05
>
> http://www.ietf.org/id/draft-newton-json-content-rules-05.txt
>
> Is there anything about the JCR grammar that requires the colon character to
> be used as a prefix to a value rule, as opposed to simply being a name-rule
> separator in an object rule?
>
> For example, to my eye, the example
>
> {
>
> "Image" {
>          width, height, "Title" :string,
>          "Thumbnail" { width, height, "Url" :uri },
>          "IDs" [ *:integer ]
>        }
> }
>
> width "Width" : 0..1280
> height "Height" : 0..1024
>
> would look more "JSON like" written as
>
> {
>
> "Image" {
>          width, height, "Title" :string,
>          "Thumbnail" : { width, height, "Url" :uri },
>          "IDs" [ *integer ]
>        }
> }
>
> width "Width" : 0..1280
> height "Height" : 0..1024
>
> and similarly
>
> the_bradys [ parents, children ]
>     children ( :"Greg", :"Marsha", :"Bobby", :"Jan" )
>
>        parents ( :"Mike", :"Carol" )
>
> would look more "JSON like" written as
>
> the_bradys [ parents, children ]
>       children ("Greg", "Marsha", "Bobby", "Jan" )
>        parents ( "Mike", "Carol" ).
>
> Thanks,
> Daniel
>
>
>
> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json
>