Re: [Json] JSON Content Rules -05

Daniel Parker <danielaparker@gmail.com> Fri, 18 March 2016 14:30 UTC

Return-Path: <danielaparker@gmail.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 9BC8C12D914 for <json@ietfa.amsl.com>; Fri, 18 Mar 2016 07:30:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 7xPTS-gSIU-l for <json@ietfa.amsl.com>; Fri, 18 Mar 2016 07:30:29 -0700 (PDT)
Received: from mail-yw0-x233.google.com (mail-yw0-x233.google.com [IPv6:2607:f8b0:4002:c05::233]) (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 E3F6012D8D4 for <json@ietf.org>; Fri, 18 Mar 2016 07:29:52 -0700 (PDT)
Received: by mail-yw0-x233.google.com with SMTP id m126so116846421ywd.0 for <json@ietf.org>; Fri, 18 Mar 2016 07:29:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to; bh=aNXjfDiU0zUgXtdK9sN0eNpXW1dK/4eDTFti4uycw0c=; b=LidcyrgsKdyym3DQG+pE2d4PUPytfWVpaJ1YfXNDd7O5DmsfoaOW+p+qqVfpRKNWKI ndWXaUbzdCtlgbpWP0dhI8u25WTW2zFRg3XSvVcvK4kalRfPpz8r/Vo87G3ewQ4ZhvaY 0Ff5Pk8hu2hYs3YTYTem/5UHYnKLdlzn69MnT4GO8eXj0InWLbT27d3TG766Fd81D2cI fVa6SP42MU96vrhF/ZJWko+HlrPTOUxNUnhIg8nt2C9cpb5h5XQEPS/OsL24PtSTaG6m lY3w2D05jBA3VKvNBtO5s1dcemlGK61m1dT0L73c9RNcZ3YXVFeNOzR8kwTE4HRSOKba eojA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=aNXjfDiU0zUgXtdK9sN0eNpXW1dK/4eDTFti4uycw0c=; b=mpRdQPNz+L2m+B5iDaYM4IgHPuIHVJSQaAZ/cBa0s52kI98bZRq5oFcm22F/5LyAVS PeKyw30YJZPh6+QaO0AtqWqIE5t+DxFxfrFgJ2+lR4smdF1Jl78urNpXY/zzvHmBRKa2 +TcGceTNVXv6yq+sfAcwgE9WZS2rVgffkJcwbPo2+aE6IiJy8vabMW7Y03OvfInyqGBZ Cicfw26HCsheoIGoIJOWj4hHJoT3K67Ho7YMBGbuMgxbUDBbObQ41NEevn0rC8YngJ8s f4evA8DGVXZv+DhnNwsLwCwAmv1ypbfAhzRD/P7xduNNTMYrgxusgjTcor3WdlwVWCjG DuMg==
X-Gm-Message-State: AD7BkJIjbFaeH3+wxoYj9MK9QVTGISqJmYjj2Zyss0UpeVaoHX4WB3EKlMyXXhpcJW28wHxXU8SwpRb3U49XBA==
MIME-Version: 1.0
X-Received: by 10.37.5.213 with SMTP id 204mr7338105ybf.19.1458311392142; Fri, 18 Mar 2016 07:29:52 -0700 (PDT)
Received: by 10.37.76.201 with HTTP; Fri, 18 Mar 2016 07:29:52 -0700 (PDT)
Date: Fri, 18 Mar 2016 10:29:52 -0400
Message-ID: <CA+mwktLxkDuGXGm083N4WK05mNVPg6R5SQ_5b5X5GckJR-mF2w@mail.gmail.com>
From: Daniel Parker <danielaparker@gmail.com>
To: json@ietf.org
Content-Type: multipart/alternative; boundary=001a11c001e28066f0052e539461
Archived-At: <http://mailarchive.ietf.org/arch/msg/json/fmT6Ls8vZU9qLSylwzwiBFwMzYs>
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:30:31 -0000

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