Re: [Json] Proposed rechartering for the JSON WG

Andrew Newton <andy@hxr.us> Sun, 09 February 2014 19:11 UTC

Return-Path: <andy@hxr.us>
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 CB44D1A03E6 for <json@ietfa.amsl.com>; Sun, 9 Feb 2014 11:11:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level:
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7] 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 qtCjbd7cJp3L for <json@ietfa.amsl.com>; Sun, 9 Feb 2014 11:11:10 -0800 (PST)
Received: from mail-pa0-f42.google.com (mail-pa0-f42.google.com [209.85.220.42]) by ietfa.amsl.com (Postfix) with ESMTP id 25FF81A050F for <json@ietf.org>; Sun, 9 Feb 2014 11:11:09 -0800 (PST)
Received: by mail-pa0-f42.google.com with SMTP id kl14so5278845pab.29 for <json@ietf.org>; Sun, 09 Feb 2014 11:11:09 -0800 (PST)
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:content-type; bh=I3NXPnrfY2SQnscwPRzyJ8/U/WtZNhKlC6Yjvdh168U=; b=aDWBwaUa4i4sMXmnNSdNEFhHudOqDqdd/Btx/4YgAXCMHb+KJnPLKg2X+FceKEjG4g WNjYSfeBA4GXzEd+/Lz+JUwQzO56fV9DddyuvryWf6AeBJgwWiljpe61hdAu0iX4klWd GO22AgWk0kLsCUj6t4h1BWMPtLWYwikU4qkmMiEF8vV10+A8XYBAwtqHeS/uw36jQnSI FY8UC2SYrhZunYaoRF1Mz0tPtFq2hWJzZoRngn5zSKWSv8l9iWYkjChLOOXyu8pQImHs uSERNc/5aTMc0nXX/lnFuXhiQ8Quv/xtK6ohFQF8y0Nq7MWwILuRdrqVSNXy1R5XV7I1 TLNA==
X-Gm-Message-State: ALoCoQn6sFM9G4QkOLqaaCI3wn/8+Bc9RTOKkbCHza0MBq4HLcz3DLTazVfOlNezzr5XUEaMwC21
MIME-Version: 1.0
X-Received: by 10.68.98.3 with SMTP id ee3mr33313811pbb.31.1391973069425; Sun, 09 Feb 2014 11:11:09 -0800 (PST)
Received: by 10.68.143.4 with HTTP; Sun, 9 Feb 2014 11:11:09 -0800 (PST)
X-Originating-IP: [108.45.162.177]
In-Reply-To: <85017697-48CF-420F-9935-B78193953493@tzi.org>
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> <7E1F7FE6-E7A9-4B7D-902C-A60D39B7B994@vpnc.org> <8AA70C014EEED3158A177F1C@cyrus.local> <85017697-48CF-420F-9935-B78193953493@tzi.org>
Date: Sun, 09 Feb 2014 14:11:09 -0500
Message-ID: <CAAQiQRfW2kX284QVtyeM3M1XV4svTVZSiS_Zp2zK32g-KZOehQ@mail.gmail.com>
From: Andrew Newton <andy@hxr.us>
To: Carsten Bormann <cabo@tzi.org>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: Cyrus Daboo <cyrus@daboo.name>, 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 19:11:12 -0000

On Sun, Feb 9, 2014 at 11:32 AM, Carsten Bormann <cabo@tzi.org> wrote:
> The important thing**) here is the 80-20 rule -- we don't need to make this thing powerful or perfect, because we can always fall back to English.
> But we shouldn't always have to, even for the most basic purposes.
>
> (draft-newton looks like an 85 % solution to me; maybe this can be even simpler.)

The intent of the draft was to find a way to document JSON. It
probably got too formal and could use some thoughtful reduction plus
use of english words instead of symbols to ease readability.

As for the backlash against schema languages, there are some lessons
to be learned. After all, DTDs and XSDs do not a standard make. The
sweet spot is probably not just a common notation or language to
describe the use of JSON in a standard but also some guidelines
regarding the other information necessary for a good specification.

-andy