IETF Logo Mail Archive

Re: [Json] Parser and encoder options (Re: The names within an object SHOULD be unique.)

John Cowan <cowan@mercury.ccil.org> Thu, 06 June 2013 22:59 UTC

Return-Path: <cowan@ccil.org>
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 7BDC621F99FC for <json@ietfa.amsl.com>; Thu, 6 Jun 2013 15:59:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.101
X-Spam-Level:
X-Spam-Status: No, score=-3.101 tagged_above=-999 required=5 tests=[AWL=0.498, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 Y-yj5HieClVf for <json@ietfa.amsl.com>; Thu, 6 Jun 2013 15:59:08 -0700 (PDT)
Received: from earth.ccil.org (earth.ccil.org [192.190.237.11]) by ietfa.amsl.com (Postfix) with ESMTP id 10FDF21F99FB for <json@ietf.org>; Thu, 6 Jun 2013 15:59:08 -0700 (PDT)
Received: from cowan by earth.ccil.org with local (Exim 4.72) (envelope-from <cowan@ccil.org>) id 1Ukj98-000198-NN; Thu, 06 Jun 2013 18:59:06 -0400
Date: Thu, 06 Jun 2013 18:59:06 -0400
From: John Cowan <cowan@mercury.ccil.org>
To: Nico Williams <nico@cryptonector.com>
Message-ID: <20130606225906.GO3090@mercury.ccil.org>
References: <CAK3OfOieEdB0fQdc-iQ+Fpw6cB3L3=4kQ-WamCdxnh7VuZdFPw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAK3OfOieEdB0fQdc-iQ+Fpw6cB3L3=4kQ-WamCdxnh7VuZdFPw@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Sender: John Cowan <cowan@ccil.org>
Cc: Douglas Crockford <douglas@crockford.com>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] Parser and encoder options (Re: The names within an object SHOULD be unique.)
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 06 Jun 2013 22:59:14 -0000

Nico Williams scripsit:

> I think we should formalize the concept of options for parsers and encoders.
> 
> For example, it's common to have options for pretty printing JSON.
> And there's been talk of extensions, so why not have some useful
> extensions (like comments, or string join, like in C, for
> pretty-printing purposes)?
> 
> We should also have a taxonomy for describing an implementation.
> We've seen the need to distinguish between streaming and non-streaming
> parsers.  (For now that's my only contribution to such a taxonomy.)

While all these things are nice-to-haves, they are why specs balloon up
to dozens or even hundreds of pages, and become impossible for anyone
but large, well-funded organizations to implement.  I do most strongly
urge this group NOT to go there.

-- 
We call nothing profound                        cowan@ccil.org
that is not wittily expressed.                  John Cowan
        --Northrop Frye (improved)

v2.23.0 | Report a Bug | By Email