Re: [Json] draft-williams-json-text-sequence-00

"Manger, James" <> Mon, 17 March 2014 05:49 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id ACFF41A0396 for <>; Sun, 16 Mar 2014 22:49:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -0.202
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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id RPu3IBy0Yspg for <>; Sun, 16 Mar 2014 22:49:48 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id AD9FB1A0395 for <>; Sun, 16 Mar 2014 22:49:46 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.97,667,1389704400"; d="scan'208";a="192486425"
Received: from unknown (HELO ([]) by with ESMTP; 17 Mar 2014 16:49:37 +1100
X-IronPort-AV: E=McAfee;i="5400,1158,7379"; a="158810522"
Received: from ([]) by with ESMTP; 17 Mar 2014 16:49:18 +1100
Received: from ([]) by ([]) with mapi; Mon, 17 Mar 2014 16:49:18 +1100
From: "Manger, James" <>
To: Nico Williams <>, "" <>
Date: Mon, 17 Mar 2014 16:47:43 +1100
Thread-Topic: [Json] draft-williams-json-text-sequence-00
Thread-Index: Ac8/6bYRiW8mkPUST9m+Ixv0gMsWsQBtkp0g
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US, en-AU
Content-Language: en-US
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: Re: [Json] draft-williams-json-text-sequence-00
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: Mon, 17 Mar 2014 05:49:49 -0000

> Title:          JavaScript Object Notation (JSON) Text Sequences


Did you really mean to allow commas as separators (%2C in ABNF)?

I would be tempted to say:

  A JSON sequence is a concatenation of any number of JSON values,
  remembering that each value (matching <JSON-text> in [RFC7159])
  can be preceded and followed by insignificant whitespace.
  Whitespace MUST be present between two JSON values when both
  values are true, false, null, or a number. Whitespace between
  values is allowed, but not required, when either value is an
  object, array, or string.

  Concatenating JSON values, each terminated with a newline (U+000A),
  is a simple way to match the syntax rules.

  An empty text and texts consisting only of whitespace are both valid
  JSON sequences of zero JSON values.

  The media type "application/jsons" indentifies content that is
  a UTF-8-encoded JSON sequence.

James Manger