[Json] Support for "\/" in ECMA versus I-JSON?

Anders Rundgren <anders.rundgren.net@gmail.com> Sat, 18 November 2017 15:54 UTC

Return-Path: <anders.rundgren.net@gmail.com>
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 2A6291274A5 for <json@ietfa.amsl.com>; Sat, 18 Nov 2017 07:54:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.8
X-Spam-Level:
X-Spam-Status: No, score=-0.8 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 SeYhrc_UPa85 for <json@ietfa.amsl.com>; Sat, 18 Nov 2017 07:54:23 -0800 (PST)
Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 843D512741D for <json@ietf.org>; Sat, 18 Nov 2017 07:54:23 -0800 (PST)
Received: by mail-wm0-x236.google.com with SMTP id 5so10365626wmk.1 for <json@ietf.org>; Sat, 18 Nov 2017 07:54:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=eXdkgj/vHPSiwHgheEE4yzeEjyC7wNQbuZQOXS2ORMU=; b=RJQNIMXG3XFwdFSLdR324rMvUv53H596eQZ8+0M2DJ66i/yxLq8NWKCX8xTxMWvSV0 DCWePMH59xfLJFUPY/admfeP8pJdNLUHc+5p8rIWB+mPsoM3xExLZdPrYrcv8Qiq1m80 rqLjPGw0pT/egYEV38ltxUCASG/r2n7gGStTOmz1QxEyMz7IKWd27Aa5pqQmnHazEUfc xuJgWa9MfGNlq9vT7PopwdgnM0/bMhY7GWGsQ+4ckwh57NxSoG0mOW0DGpixSMByJfJU IvzwBS+wo+SuUqE8/ddLQ5YWcGzU/JkuekZxZqwww+46XGMEt5mQ2EQBIs7B8V2Vv7oi k5Ew==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=eXdkgj/vHPSiwHgheEE4yzeEjyC7wNQbuZQOXS2ORMU=; b=rLeq/ZL3k+TXdLCA6vx93LWJEa5O0bAS05uhDetc0Bb82pTgaI5lQ8TKdDbS3eZX7Z KgmuO0iAJfCZtLEh54TJEiRbLqQ5TE/SX6P2rMWSOJ58RY3UJS40sMjibKEMVqedGk+H Y6lBNBiFhIv+Kh6aVEsXkJIlUXJh9IXedS88PHRE6tpiP+s04TzAn+3ukDUxr9W9Ll4N WavUyKRTfRMjBCwuo+4OzT9oegG6oXyMlJemDY17CSMOSqQw6NTdAyup6aysFfl6guo0 C8r8X2PPojc6gpcIhkwDqfudH36H7RVrYOsU4M0x44GY/PkzuUc8MnFNNKIubMrcrVEm fLSQ==
X-Gm-Message-State: AJaThX5piT6pYlmdfv8IKSDhX5+2B1LANzvLfhSJYADRDKPT2BZ9NRGj uLBAC0v3exkD+V0rypQkmrUQAw==
X-Google-Smtp-Source: AGs4zMYQ673omVCeMWbM2+nM0MfHOUpsNiqKSAx7qebVTLquS7NeAawrgz0Tme8t+ETKltQEB14Iwg==
X-Received: by 10.80.184.83 with SMTP id k19mr12549157ede.190.1511020461980; Sat, 18 Nov 2017 07:54:21 -0800 (PST)
Received: from [192.168.1.79] (25.131.146.77.rev.sfr.net. [77.146.131.25]) by smtp.googlemail.com with ESMTPSA id d9sm4337695edb.18.2017.11.18.07.54.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 18 Nov 2017 07:54:20 -0800 (PST)
To: json@ietf.org
Cc: Julian Reschke <julian.reschke@gmx.de>
References: <150047191184.7507.7143481683564082881@ietfa.amsl.com> <DB9BA7EA-D393-4079-B347-620A09280B26@isode.com> <CAC4RtVBYMrRCrUZ1qqD+_rH4M8N23GOgbbh=921fEYqH+gCm5Q@mail.gmail.com> <c06e583a-965e-9eaf-975f-e6876ac056ed@filament.com> <f1a6b553-c787-e248-67bd-74d68d98a845@gmx.de> <262E8314-263A-4443-B912-AFCF1A3277B2@tzi.org> <166957c4-26fc-90b5-a798-59280c91b466@filament.com> <8B60039F-96DD-4F72-8139-D80B6F11566C@tzi.org> <3760a157-5b88-e334-712c-03eecd675794@codalogic.com> <7a88952c-3e46-3f87-b3c2-2864f216c62d@gmail.com> <9cddf2e7-f987-3942-3580-05c3da6a4805@codalogic.com> <2892a0eb-0bd2-cd2e-87e7-aa2e29009b4b@filament.com>
From: Anders Rundgren <anders.rundgren.net@gmail.com>
Message-ID: <fb700d81-5ed9-c0aa-1ace-71554c516a69@gmail.com>
Date: Sat, 18 Nov 2017 16:54:18 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <2892a0eb-0bd2-cd2e-87e7-aa2e29009b4b@filament.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/QxyWdjX1LAqPatZd-4F7nhipxv8>
Subject: [Json] Support for "\/" in ECMA versus I-JSON?
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Sat, 18 Nov 2017 15:54:25 -0000

It is [quite] possible that I got lost in ECMA's gigantic spec but I can't find any support for the "\/" escape in there but it surely is in I-JSON.

WDYT?

Anders