Re: [Json] Proposed rechartering for the JSON WG

Phillip Hallam-Baker <hallam@gmail.com> Sun, 09 February 2014 03:01 UTC

Return-Path: <hallam@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 476811A0673 for <json@ietfa.amsl.com>; Sat, 8 Feb 2014 19:01:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, SPF_PASS=-0.001] autolearn=ham
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 Qdhcg6f3F6vj for <json@ietfa.amsl.com>; Sat, 8 Feb 2014 19:01:02 -0800 (PST)
Received: from mail-lb0-x232.google.com (mail-lb0-x232.google.com [IPv6:2a00:1450:4010:c04::232]) by ietfa.amsl.com (Postfix) with ESMTP id 82DFD1A0678 for <json@ietf.org>; Sat, 8 Feb 2014 19:01:02 -0800 (PST)
Received: by mail-lb0-f178.google.com with SMTP id u14so3882344lbd.9 for <json@ietf.org>; Sat, 08 Feb 2014 19:01:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=06rdTVZUNoOYoju1zeNyB+Iwwa07nTlnNxLsHMb9CbU=; b=venOEnTLCGQneS8EDnxA6NvBo/qUXhA6w+OFzvY5LBN7Y2LeP6Q8udVOZWIbBgkaR7 0FlceiuYG5zaT/itMZBNnLK2Toy6bLnDKfBPXcf/tzi552A0/RuEJVYHcDqZpq+Xyt/0 /owUjrcaCVLHJ/CLXnqV7WWEhmSMShQQ1Xp7McD5ocIyHGQDnVp2rlwF7pdQkvN9iUN/ UEvdNs4MSOCAL5BGpGriUkxV70u4NiBXo8eRF/ci3lTgWTCfTUa8uHVuskQQEWgv9kRG 5A35m/8akmXZ4rYEqqXqfMC/UAnyjIhkVeMNS56QRUf1zYFvt+jngeoJSnJY79Q0/HPp f1MA==
MIME-Version: 1.0
X-Received: by 10.152.2.169 with SMTP id 9mr17388lav.48.1391914862203; Sat, 08 Feb 2014 19:01:02 -0800 (PST)
Received: by 10.112.37.168 with HTTP; Sat, 8 Feb 2014 19:01:02 -0800 (PST)
In-Reply-To: <C271F837-40FD-4E87-A56B-0F0357553923@mnot.net>
References: <52D9B39C.5020102@cisco.com> <1C1347D2-0D99-4D49-B4C1-199246167D23@vpnc.org> <CAMm+Lwj0phrmP563tBbZJKHeYw=Azh1as6GZOA6rANPpC6PJgA@mail.gmail.com> <CAHBU6iv+-9xQYAjZdfZk7+GeA6J+sjaV5era3L+PiJ9RoauBYg@mail.gmail.com> <CAMm+Lwh0O4+iuaJMUhYgj+0GS8e9b_nZtNNX91hOmjUypsgkTQ@mail.gmail.com> <CAK3OfOhu0GZY9CVQrqD4SyjHLVEoEg1DtYj_6imZbbHtzX2eEw@mail.gmail.com> <CAHBU6iuR0MPm9q483jBMqTRkGV1f2giGNhp+UciQ7rRnrvcEBA@mail.gmail.com> <C271F837-40FD-4E87-A56B-0F0357553923@mnot.net>
Date: Sat, 08 Feb 2014 22:01:02 -0500
Message-ID: <CAMm+LwjD0e_xgAbRN6+vF2J8YwLHB2m=n9mdJ_GHTOv4cenr-g@mail.gmail.com>
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Mark Nottingham <mnot@mnot.net>
Content-Type: multipart/alternative; boundary="047d7ba9719aeb57bd04f1f06ea4"
Cc: Nico Williams <nico@cryptonector.com>, Tim Bray <tbray@textuality.com>, Paul Hoffman <paul.hoffman@vpnc.org>, JSON WG <json@ietf.org>
Subject: Re: [Json] Proposed rechartering for the JSON WG
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: Sun, 09 Feb 2014 03:01:06 -0000

Me too.

I was asking if schema was in scope. I have no particular interest in
having a committee redesign a tool that works perfectly well as it is.


On Sat, Feb 8, 2014 at 9:37 PM, Mark Nottingham <mnot@mnot.net> wrote:

> +1
>
> I'd be more comfortable if the charter were more explicit about this;
> e.g., "A set of natural-language terms and/or phrases for use in future
> specifications that use JSON. This explicitly excludes schema languages and
> similar formalisms."
>
>
> On 8 Feb 2014, at 12:14 pm, Tim Bray <tbray@textuality.com> wrote:
>
> > I really want to stay away from the slippery schema slope. So I do not
> think we're trying to be ABNF for JSON, because that is in fact a simple
> lexical schema.  In a spec sentence like this:
> >
> > The value of the "size" member of the top level "buffer" item MUST be a
> non-negative integer.
> >
> > I think nomenclature means having a uniform standardised way to express
> the meaning of the words between "value of" and "MUST".  Perhaps something
> like XPath for JSON.
> >
> > Disclosure: I'm not convinced this is necessary or even useful.
> >
> > On 7 Feb 2014 20:03, "Nico Williams" <nico@cryptonector.com> wrote:
> > On Fri, Feb 7, 2014 at 6:57 PM, Phillip Hallam-Baker <hallam@gmail.com>
> wrote:
> > > On Fri, Feb 7, 2014 at 6:20 PM, Tim Bray <tbray@textuality.com> wrote:
> > >> On 7 Feb 2014 17:54, "Phillip Hallam-Baker" <hallam@gmail.com> wrote:
> > >> > Does a 'standardized nomenclature for JSON' mean formal languages
> are in
> > >> > or out of scope?
> > >>
> > >> Don't know what you mean by Formal Languages in this context, but
> schemas
> > >> are clearly out of scope.
> > >
> > > By formal language I mean a machine readable description of the data
> > > structure that specifies the tag names and the set of corresponding
> values.
> >
> > That's schema.  One (or more) schema representations for JSON would be
> > nice, yes.
> >
> > Note that ABNF is a formal language, but not what you're after, which
> > is why I would have asked the question Tim asked.
> >
> > Nico
> > --
> > _______________________________________________
> > json mailing list
> > json@ietf.org
> > https://www.ietf.org/mailman/listinfo/json
>
> --
> Mark Nottingham   http://www.mnot.net/
>
>
>
>


-- 
Website: http://hallambaker.com/