Re: [Json] Comments on the proposed charter

Francis Galiegue <fgaliegue@gmail.com> Wed, 20 February 2013 03:04 UTC

Return-Path: <fgaliegue@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 BF57521F888B for <json@ietfa.amsl.com>; Tue, 19 Feb 2013 19:04:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.522
X-Spam-Level:
X-Spam-Status: No, score=-3.522 tagged_above=-999 required=5 tests=[AWL=0.077, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FHcDk8SviQgl for <json@ietfa.amsl.com>; Tue, 19 Feb 2013 19:04:23 -0800 (PST)
Received: from mail-ee0-f47.google.com (mail-ee0-f47.google.com [74.125.83.47]) by ietfa.amsl.com (Postfix) with ESMTP id 8B4F021F886B for <json@ietf.org>; Tue, 19 Feb 2013 19:04:22 -0800 (PST)
Received: by mail-ee0-f47.google.com with SMTP id e52so3691243eek.20 for <json@ietf.org>; Tue, 19 Feb 2013 19:04:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=oxJ+nT5YmVhNnsU65fQNbBioAoOVfl6qWiME8QsmQOw=; b=oRLhD9DbjQL7bZUWeBSZF1x6zeS4BGMW16RcUC1lWkPV03Aa8ghgN7pUtfxh2oj07z 3GXt2fpFYmoYhXY2sFBWJTxa4zMrN3Je8N/cthdhEU6JF5rPRL90j1YQuCTstFZa+9KM Kj2sC0fEleOReIiuC5BMEKwVKGlWxFmXhIvaXkOoyrmGdBLuDXGnDle7bNzYZ3xnBbKn Zi9ptMhdZVBEbKDP/xQnxbN+Oe9qquOTctoXuK5jOmpIhngqkWq18HrrKS6CM2GZdnLA ziDcpNevii7lQUX6SezZYrfj4Tb0pL+A1hkCgVUfn1Pg42slq7SuU9IvZLR//wNIGZtl b6+A==
MIME-Version: 1.0
X-Received: by 10.14.179.5 with SMTP id g5mr63905729eem.41.1361329461433; Tue, 19 Feb 2013 19:04:21 -0800 (PST)
Received: by 10.14.1.7 with HTTP; Tue, 19 Feb 2013 19:04:21 -0800 (PST)
In-Reply-To: <51243BC6.8080909@stpeter.im>
References: <E0597F3D-773C-4CDD-8087-09B99ADCF156@mnot.net> <CALcybBD-ksPe71YY9BY-NZ9VP0tNqToySn8zp+9swtM=P9MiCw@mail.gmail.com> <95501AA5-EA26-4D74-8C6B-187F0E52C524@mnot.net> <CALcybBA__74RTGwr6f0KV4=pw5jnRLGRs6Y9YtuYi=YBpyAYJA@mail.gmail.com> <51243BC6.8080909@stpeter.im>
Date: Wed, 20 Feb 2013 04:04:21 +0100
Message-ID: <CALcybBAKWQ+hH=LEXN-Rn90deGZN4tDtSgLV1dnnkjuLp-_+gw@mail.gmail.com>
From: Francis Galiegue <fgaliegue@gmail.com>
To: Peter Saint-Andre <stpeter@stpeter.im>
Content-Type: text/plain; charset=UTF-8
Cc: Mark Nottingham <mnot@mnot.net>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] Comments on the proposed charter
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion related to JavaScript Object Notation \(JSON\)." <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: Wed, 20 Feb 2013 03:04:23 -0000

On Wed, Feb 20, 2013 at 3:58 AM, Peter Saint-Andre <stpeter@stpeter.im> wrote:
[...]
>>
>> And that is what I said exactly. Your initial wording let the
>> impression that this working group SHOULD NOT care about the
>> existing, concrete uses of JSON.
>>
>> And this is where I disagree. They SHOULD care. Not steer, but
>> care.
>
> It's not about caring, it's about the working group's contract with
> the IESG and the IETF community at large. It's true that the
> individuals working on base specs in the JSON WG (if formed) will
> probably care about various uses of JSON. It does not follow that it's
> best to work on applications of JSON in the same venue as the base specs.
>

Yes, I agree with that too. My argument is that working on the base
specifications without an awareness of how these existing base
specifications are used is shortsighted.

I may have misinterpreted what Mark said, but this is the impression I
had when reading that part of his first answer.

-- 
Francis Galiegue, fgaliegue@gmail.com
Try out your JSON Schemas: http://json-schema-validator.herokuapp.com