IETF Logo Mail Archive

Re: [Json] serializing sequences of JSON values

Tatu Saloranta <tsaloranta@gmail.com> Fri, 14 March 2014 19:31 UTC

Return-Path: <tsaloranta@gmail.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 944DE1A01A0 for <json@ietfa.amsl.com>; Fri, 14 Mar 2014 12:31:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 hr0r1KJwonOX for <json@ietfa.amsl.com>; Fri, 14 Mar 2014 12:30:58 -0700 (PDT)
Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) by ietfa.amsl.com (Postfix) with ESMTP id BA7C61A00A9 for <json@ietf.org>; Fri, 14 Mar 2014 12:30:57 -0700 (PDT)
Received: by mail-wi0-f170.google.com with SMTP id n15so1086490wiw.1 for <json@ietf.org>; Fri, 14 Mar 2014 12:30:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=gMpNHiYnEuxKALjACeb+YZGy6uLHBnBpvjW4grunFAI=; b=T/fzRp5W64vhnQ6t5EyBPQODoQIBbHfcNb3GhK9Yb6yWxpBtXbopf6amr72J/X5JnH +KLeYU8o1wyC0GdPIGDXFhUNX0RTxB2n39wVBH8jABf9ciRD41T2a17fk1hRqCffzir1 Lrg1hkNU6OCYZtJATnBfxJ23Ir/7LmsxAK0QKkH00byTMVtG4+WrMIcDU23B1uCS2DUb Q5CdaXk0Xw86V8sPSYStVJ3HUEGaRAQ4xty7fyv7v3chqV1vqhXJMjo0UhWx3Pak8BFg MIGHMMG52GxfgHBI0dHadLPd6JbWkQ2GJ6AzurGlqscO4qFiHiabcsdUoRrFeLOX1ODF to8A==
MIME-Version: 1.0
X-Received: by 10.194.21.193 with SMTP id x1mr7879119wje.33.1394825450353; Fri, 14 Mar 2014 12:30:50 -0700 (PDT)
Received: by 10.227.245.10 with HTTP; Fri, 14 Mar 2014 12:30:50 -0700 (PDT)
In-Reply-To: <CAK3OfOhYxRR1ii3=eezXAmUR1ArpZDmAzbjRdHL2ASQ7Y1deDw@mail.gmail.com>
References: <em2c025504-6532-4513-a339-3d71c4cdfbda@helsinki> <5FC8412F-30E5-4F80-AB63-6715B1053098@vpnc.org> <58a4b20f768b484c94a850c4eba71ec5@BL2PR02MB307.namprd02.prod.outlook.com> <53222FFC.8070204@cisco.com> <5322714F.6080508@it.aoyama.ac.jp> <CAGrxA26HRqa+R580qfEMXU_JGid-UDzwwmQigOkOW0OWuA9mpg@mail.gmail.com> <CAK3OfOier6uQ4nVuuCP+uWV+eRbYh8qqAi4FVdWqNLHOh94L+A@mail.gmail.com> <CAGrxA275TwvbUkAT7tp9NtgTDN1WwPNP33aKmAZdB7QJkSY0CA@mail.gmail.com> <CAK3OfOj3e7pqj5R-ggHhXfaN5p1CG+6djiLizaRE2nJnF1ivGA@mail.gmail.com> <CAK3OfOhYxRR1ii3=eezXAmUR1ArpZDmAzbjRdHL2ASQ7Y1deDw@mail.gmail.com>
Date: Fri, 14 Mar 2014 19:30:50 +0000
Message-ID: <CAGrxA270ARHz-XepgY-4PpTGqJG+4xGbFQ15kWYXPs_52vHtEg@mail.gmail.com>
From: Tatu Saloranta <tsaloranta@gmail.com>
To: Nico Williams <nico@cryptonector.com>
Content-Type: multipart/alternative; boundary="047d7b5d56107dfa5304f4961bec"
Archived-At: http://mailarchive.ietf.org/arch/msg/json/thCdBYPWzLYtqtuOGkxt1JSlwfY
Cc: Matt Miller <mamille2@cisco.com>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] serializing sequences of JSON values
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: Fri, 14 Mar 2014 19:31:06 -0000

On Fri, Mar 14, 2014 at 4:37 PM, Nico Williams <nico@cryptonector.com>wrote:

> The most interoperable form of JSON text sequence would be this:
> encoders MUST not use newlines in their JSON text encodings and MUST
> follow each JSON text with a newline.
>

And presumably this would include all linefeeds that JSON specification
supports? (\r, \n and \r\n).

-+ Tatu +-

v2.23.0 | Report a Bug | By Email