IETF Logo Mail Archive

Re: [Json] Comments on the proposed charter

"Matt Miller (mamille2)" <mamille2@cisco.com> Wed, 20 February 2013 02:28 UTC

Return-Path: <mamille2@cisco.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 C4C2921F87BA for <json@ietfa.amsl.com>; Tue, 19 Feb 2013 18:28:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 pI8cb83xxF0f for <json@ietfa.amsl.com>; Tue, 19 Feb 2013 18:28:59 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 05F5221F87B6 for <json@ietf.org>; Tue, 19 Feb 2013 18:28:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1862; q=dns/txt; s=iport; t=1361327339; x=1362536939; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=Ou3pwIAUdUU6sr8S+Vi5vvyoIS8v/V40+USJpafgUaU=; b=hbaJv+nPJklgd1N3xvlYZVf7sK+ojEFQeQ2GoW1GIqdXOEG/Ig+WbSP8 z5yoXPx8UNlaCXcno+tXfxN3AUfXjhQQ3ZDatFvX3FKK8XDrEZr9M0WLg ZibNiI9Jr2GygkJ6wy3hrML0kRZslH+r3mrCdvqCzxFJwrupvmBR9LWtR o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAPsyJFGtJV2Z/2dsb2JhbABFwE2BDRZzgh8BAQEDAQEBATc0CwULAgEIDgoKFBAhBgslAgQBDQUIEYdnAwkGDLJRhCMNiVqMN4IkAjEHgl9hA5RQjR6FFYJ6DYFrJBg
X-IronPort-AV: E=Sophos;i="4.84,698,1355097600"; d="scan'208";a="175974485"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-9.cisco.com with ESMTP; 20 Feb 2013 02:28:58 +0000
Received: from xhc-aln-x01.cisco.com (xhc-aln-x01.cisco.com [173.36.12.75]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r1K2SwE6025327 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 20 Feb 2013 02:28:58 GMT
Received: from xmb-aln-x11.cisco.com ([169.254.6.203]) by xhc-aln-x01.cisco.com ([173.36.12.75]) with mapi id 14.02.0318.004; Tue, 19 Feb 2013 20:28:58 -0600
From: "Matt Miller (mamille2)" <mamille2@cisco.com>
To: Mark Nottingham <mnot@mnot.net>, "json@ietf.org" <json@ietf.org>
Thread-Topic: [Json] Comments on the proposed charter
Thread-Index: AQHODw0516g5UKYB5UGMEEY3kJQ8bZiCZc6AgAAARYCAAAR5gA==
Date: Wed, 20 Feb 2013 02:28:57 +0000
Message-ID: <BF7E36B9C495A6468E8EC573603ED9411513F4D4@xmb-aln-x11.cisco.com>
References: <E0597F3D-773C-4CDD-8087-09B99ADCF156@mnot.net> <CALcybBD-ksPe71YY9BY-NZ9VP0tNqToySn8zp+9swtM=P9MiCw@mail.gmail.com> <95501AA5-EA26-4D74-8C6B-187F0E52C524@mnot.net>
In-Reply-To: <95501AA5-EA26-4D74-8C6B-187F0E52C524@mnot.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.21.76.153]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <77323ADD8BC79E4D9A58D840815F3211@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Francis Galiegue <fgaliegue@gmail.com>
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 02:28:59 -0000

On Feb 19, 2013, at 7:12 PM, Mark Nottingham <mnot@mnot.net>
 wrote:

> There are ways to be aware of how JSON will be used without taking responsibility for defining those uses.
> 

THIS


- m&m

Matt Miller < mamille2@cisco.com >
Cisco Systems, Inc.

> On 20/02/2013, at 1:11 PM, Francis Galiegue <fgaliegue@gmail.com> wrote:
> 
>> On Wed, Feb 20, 2013 at 2:54 AM, Mark Nottingham <mnot@mnot.net> wrote:
>> [...]
>>> 
>>> This is a horrifically, monumentally bad idea.
>>> 
>>> Having a catch-all Working Group for anything that happens to use JSON is like having one for anything that happens to use ASCII or UTF-8. It's like shoving XML Schema, XLink, SOAP, Atom, DocBook and XHTML into the same Working Group.
>>> 
>> 
>> On the other hand, a working group focussing on JSON alone and only
>> JSON may fail to see the big picture of how JSON is actually _used_.
>> As far as I see it, this working group does not aim at standardizing
>> all of these, but it also needs to know how JSON is used in real life
>> situations. And as such, it needs to be aware of whatever idea has
>> been submitted as an I-D, or for that matter any other idea involving
>> JSON and not the IETF (JSON-RPC comes to mind, but so does SMD,
>> GeoJSON etc).
>> 
>> 
>> So, I disagree: this is not a bad idea. Awareness is needed. The most
>> clever people in the world, discussing a format, if clueless about
>> what happens "out there", have no value in steering a format.
>> 
>> -- 
>> Francis Galiegue, fgaliegue@gmail.com
>> Try out your JSON Schemas: http://json-schema-validator.herokuapp.com
> 
> --
> Mark Nottingham   http://www.mnot.net/
> 
> 
> 
> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json

v2.23.0 | Report a Bug | By Email