Re: [Json] Proposal: JSON text sequence MIME type and Proposed Standard

"Manger, James" <James.H.Manger@team.telstra.com> Wed, 12 March 2014 03:13 UTC

Return-Path: <James.H.Manger@team.telstra.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 4AC441A08D3 for <json@ietfa.amsl.com>; Tue, 11 Mar 2014 20:13:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.202
X-Spam-Level:
X-Spam-Status: No, score=-0.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, RCVD_IN_DNSWL_NONE=-0.0001, RELAY_IS_203=0.994] autolearn=no
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 9hh8bG3G_rEG for <json@ietfa.amsl.com>; Tue, 11 Mar 2014 20:13:33 -0700 (PDT)
Received: from ipxano.tcif.telstra.com.au (ipxano.tcif.telstra.com.au [203.35.82.200]) by ietfa.amsl.com (Postfix) with ESMTP id BF5E01A08B4 for <json@ietf.org>; Tue, 11 Mar 2014 20:13:32 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.97,635,1389704400"; d="scan'208";a="191201256"
Received: from unknown (HELO ipcbni.tcif.telstra.com.au) ([10.97.216.204]) by ipoani.tcif.telstra.com.au with ESMTP; 12 Mar 2014 14:13:26 +1100
X-IronPort-AV: E=McAfee;i="5400,1158,7374"; a="206152884"
Received: from wsmsg3704.srv.dir.telstra.com ([172.49.40.197]) by ipcbni.tcif.telstra.com.au with ESMTP; 12 Mar 2014 14:12:21 +1100
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by WSMSG3704.srv.dir.telstra.com ([172.49.40.197]) with mapi; Wed, 12 Mar 2014 14:12:21 +1100
From: "Manger, James" <James.H.Manger@team.telstra.com>
To: Nico Williams <nico@cryptonector.com>
Date: Wed, 12 Mar 2014 14:12:19 +1100
Thread-Topic: [Json] Proposal: JSON text sequence MIME type and Proposed Standard
Thread-Index: Ac89flTq+71GEe1BRWeMeWxnieJKRgAIUFhA
Message-ID: <255B9BB34FB7D647A506DC292726F6E115401A0B02@WSMSG3153V.srv.dir.telstra.com>
References: <255B9BB34FB7D647A506DC292726F6E1153F8CA38B@WSMSG3153V.srv.dir.telstra.com> <CAK3OfOjZ4nDQ7OBpbF-0D9dK9+08MhXiRe9VxKvWTXwBosd-RA@mail.gmail.com>
In-Reply-To: <CAK3OfOjZ4nDQ7OBpbF-0D9dK9+08MhXiRe9VxKvWTXwBosd-RA@mail.gmail.com>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/json/fYUoW58i5JQe63vwoeTto7N2oRQ
Cc: "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] Proposal: JSON text sequence MIME type and Proposed Standard
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: Wed, 12 Mar 2014 03:13:35 -0000

> > I agree that a newline is the best separator for creators to include,
> and always including it is best.
> >
> > Some (most?) receivers will be more lenient and accept values
> separated by any whitespace, or with no separator (for objects, arrays,
> and/or strings). Perhaps it is best for interop to say receivers MUST
> be this lenient.

> Good point.  Sequence parsers MUST be able to handle newline text
> separators and SHOULD be able to handle other whitespace, as well as
> no separator in the unambiguous cases.  Sequence encoders SHOULD use a
> newline separator and MAY use other whitespace (with some guidance as
> to why newline is best); no need to mention when the separator may be
> omitted.

You don't quite guarantee interop with "encoders MAY use other whitespace" and "parsers SHOULD be able to handle other whitespace".

The spec needs to say: either "encoders MUST use a newline separator"; or "decoders MUST be able to handle any whitespace (including none in the unambiguous cases)".

--
James Manger