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

Nico Williams <> Tue, 11 March 2014 23:05 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id A82871A088E for <>; Tue, 11 Mar 2014 16:05:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 1.753
X-Spam-Level: *
X-Spam-Status: No, score=1.753 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_COM=0.553, IP_NOT_FRIENDLY=0.334, RDNS_NONE=0.793] autolearn=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Kb5IAgRI3Xys for <>; Tue, 11 Mar 2014 16:05:01 -0700 (PDT)
Received: from (unknown []) by (Postfix) with ESMTP id B891C1A087F for <>; Tue, 11 Mar 2014 16:05:01 -0700 (PDT)
Received: from (localhost []) by (Postfix) with ESMTP id DD0C61DE060 for <>; Tue, 11 Mar 2014 16:04:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed;; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type;; bh=XZYVNGjs0V4A3+nP+x8/ XJyZF9U=; b=N33YGVIHIXdtTGpMHAS/w4ztUS3lHUZdj6FjsEOZNGq7fQa/L2Es 6b5hWyBBYj+8K/8rQu12rgNFD7y/sE3rneZOsmqITBNEP0E00vz64hbVEemo8jYe hoUA71nU+wWANKeOs2kTldH9aKaZ/7nSkCiQr2K9NEwNHJ7f0+1Xfhk=
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: by (Postfix) with ESMTPSA id 90E491DE005 for <>; Tue, 11 Mar 2014 16:04:55 -0700 (PDT)
Received: by with SMTP id l18so6447737wgh.7 for <>; Tue, 11 Mar 2014 16:04:54 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=OBNIna1ljwFTcX2HkpljxpIARdoifipQY3gjTa59umg=; b=WitZPndLaGnbhJb81kcXwfB0yH/KhW1/7bm7MsSNsooBTZ3XP2uq3fdRBpO4vR9NGr ebHpTawgxVuDwlKkv+Nut2i2ci4ztgtt3MVkeUAl7639ZedxIZJsg+V83EPqNMZvDdRt srRO0omJ+z2YElkc9oy1A298jGI7tCsE6ogkihHBOfgVgQAQkxhNQpQovDklTN7teL2j 5fSxD48Eh9XVRQGn8fGEaOFxeh87Fk0qN9u9UfIDvPj4g/HQ8pEHwNzesyJSc6q6+Pfx sfb60lAcfF+xYxzxm7RaZ9WsjbdoeRWKuIzEeOw6y6F6/S1VwbvOQ8L1u2atf+Xxnugi ob3A==
MIME-Version: 1.0
X-Received: by with SMTP id f11mr9793502wjz.47.1394579094386; Tue, 11 Mar 2014 16:04:54 -0700 (PDT)
Received: by with HTTP; Tue, 11 Mar 2014 16:04:54 -0700 (PDT)
In-Reply-To: <>
References: <>
Date: Tue, 11 Mar 2014 18:04:54 -0500
Message-ID: <>
From: Nico Williams <>
To: "Manger, James" <>
Content-Type: text/plain; charset=UTF-8
Cc: "" <>
Subject: Re: [Json] Proposal: JSON text sequence MIME type and Proposed Standard
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 11 Mar 2014 23:05:03 -0000

On Tue, Mar 11, 2014 at 6:01 PM, Manger, James
<> wrote:
> A short spec on JSON sequences is a good idea, Nico.

I'll submit an I-D soon.

> 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