Re: [apps-discuss] RFC 6570: what is the dot for in section 3?

Mark Nottingham <mnot@mnot.net> Tue, 19 March 2013 00:01 UTC

Return-Path: <mnot@mnot.net>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B70521F8AE8 for <apps-discuss@ietfa.amsl.com>; Mon, 18 Mar 2013 17:01:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=-4.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gqM3CbTzGRxt for <apps-discuss@ietfa.amsl.com>; Mon, 18 Mar 2013 17:01:22 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id 95D9721F8ADC for <apps-discuss@ietf.org>; Mon, 18 Mar 2013 17:01:22 -0700 (PDT)
Received: from [192.168.1.80] (unknown [118.209.42.8]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id DD779509B9; Mon, 18 Mar 2013 20:01:20 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <CALcybBA8naUpYfHdQXx7Lv-6-Y8+P+KLmahTjQDNxb2Rvtn3QA@mail.gmail.com>
Date: Tue, 19 Mar 2013 11:01:16 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <ACC4A53E-0B14-4693-86B2-79B9E20AD0F7@mnot.net>
References: <CALcybBA8naUpYfHdQXx7Lv-6-Y8+P+KLmahTjQDNxb2Rvtn3QA@mail.gmail.com>
To: Francis Galiegue <fgaliegue@gmail.com>
X-Mailer: Apple Mail (2.1499)
Cc: apps-discuss@ietf.org
Subject: Re: [apps-discuss] RFC 6570: what is the dot for in section 3?
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Mar 2013 00:01:23 -0000

It's there as a convenience to implementations, so they can model data structures (e.g., dictionaries) easily.


On 16/03/2013, at 12:23 AM, Francis Galiegue <fgaliegue@gmail.com> wrote:

> Hello,
> 
> The grammar for a variable name reads as such:
> 
>     varspec       =  varname [ modifier-level4 ]
>     varname       =  varchar *( ["."] varchar )
>     varchar       =  ALPHA / DIGIT / "_" / pct-encoded
> 
> I fail to see any mention of the dot anywhere else in the document
> when it appears in this context and I don't see any example either,
> not even in appendix A. And the "varchar" grammar token adds to the
> confusion since it seems to indicate the dot has a special role.
> 
> If, for example I have a variable foo defined as:
> 
> { "bar": 1, "baz": 2 }
> 
> what is "foo.bar"? Does it refer to another variable entirely, or is
> it value of key "bar" in associate array "foo"?
> 
> --
> Francis Galiegue, fgaliegue@gmail.com
> JSON Schema in Java: http://json-schema-validator.herokuapp.com
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss

--
Mark Nottingham   http://www.mnot.net/