IETF Logo Mail Archive

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

Tim Bray <tbray@textuality.com> Sat, 18 November 2017 23:03 UTC

Return-Path: <tbray@textuality.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 24B5D124B17 for <json@ietfa.amsl.com>; Sat, 18 Nov 2017 15:03:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=textuality-com.20150623.gappssmtp.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 4rTT-JXHqL3f for <json@ietfa.amsl.com>; Sat, 18 Nov 2017 15:03:51 -0800 (PST)
Received: from mail-wm0-x22b.google.com (mail-wm0-x22b.google.com [IPv6:2a00:1450:400c:c09::22b]) (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 4AF8E1201F2 for <json@ietf.org>; Sat, 18 Nov 2017 15:03:51 -0800 (PST)
Received: by mail-wm0-x22b.google.com with SMTP id r68so12577203wmr.3 for <json@ietf.org>; Sat, 18 Nov 2017 15:03:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=textuality-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=RPOPOObfVH82SlCItWjFBHPxncXfMQBbW9KpiE8gVLc=; b=QlnyjBoTbuy51KOLx8cTcxhysVUJ/44reI+GrZFcEfWN+WtuqPI4hcko/oOPHMKZct dIP8vMRaqokAi6LXrcY4Ph93opS/XnzF5XKR88J5fAlfDHBGNTQTir93D6YGL3nivjia q4u+rMyMfrJQ67H2wPLXuWfdyYa3XpfG7IGGHdDzolNRJ1cWI9j/9t0RjHrMDfpsDHqA fbeKXYPTnJMRpqBUoGXjqCzDLGLzKRTavs3dBLyNlEP5lZXidYhjZPX4ALoG4nmbxJ8o Xes/dVjSc8PV8KxyQvAgGH2oLZXuduZ09u+Fcnvo/JXSAhaAfQN1KTjaEpjYPJSrebBj JC0A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=RPOPOObfVH82SlCItWjFBHPxncXfMQBbW9KpiE8gVLc=; b=MttloeJA0LnRjOnxuRv2DXHc1zlau88ZmTOPRKkgrqhoChIiqgO9JFBnb1mpBo0XFq UpMHfn5faK3/QF5ybUfgT9ytK9JOq2rZTVpln+qi89rnv/Dni+c+2d357u9jIVTYP7PZ mdcMEvstLtexmPa1Slpik7cMDomOyPCppOfm128W1HFmbb74LznhQBJrcm9M6gMfFQff IWjtdRI4g+5U1wCqKRLCreSNmuFij0s3am8wUyctzSqDZ+C+kbGsk872wDA8G1pWJRFv m5Rp7EnC5l7f3+kXzdDuNqjpeBtU7oHMMJrPdlLmsBHuQgfsfZ8IkQVJAmCX5oJUyI1r vdHw==
X-Gm-Message-State: AJaThX6/IwUVA3KdQDwHXNtq6zKYjd+QajxhSFW3GcOwnBjeayzvsWpZ DO/Sf66ZOc5bkdx9fvL+OoHX15Sbw1GTR1SY+A4InA==
X-Google-Smtp-Source: AGs4zMbWMyASSYto8hQVhOCN94mQE3Ht0pLgYPD1Tpp+MRUKEKK6xzsKfVhiANuEte03Anha85yY+OeOYf0VqGBYIYA=
X-Received: by 10.80.208.10 with SMTP id j10mr13161915edf.194.1511046229781; Sat, 18 Nov 2017 15:03:49 -0800 (PST)
MIME-Version: 1.0
Received: by 10.80.225.1 with HTTP; Sat, 18 Nov 2017 15:03:29 -0800 (PST)
X-Originating-IP: [174.6.224.108]
In-Reply-To: <fb700d81-5ed9-c0aa-1ace-71554c516a69@gmail.com>
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> <fb700d81-5ed9-c0aa-1ace-71554c516a69@gmail.com>
From: Tim Bray <tbray@textuality.com>
Date: Sat, 18 Nov 2017 23:03:29 +0000
Message-ID: <CAHBU6it7v=dgqQON8XZcamXkaV22Cm=68ObnHywkXT2ZZ8He-Q@mail.gmail.com>
To: Anders Rundgren <anders.rundgren.net@gmail.com>
Cc: "json@ietf.org" <json@ietf.org>, Julian Reschke <julian.reschke@gmx.de>
Content-Type: multipart/alternative; boundary="94eb2c1ccb9ec4035a055e49ddfd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/r4qjRprJEvoCgnvfdqsq9WpT8J0>
Subject: Re: [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 23:03:53 -0000

I can't imagine why you’d ever need \/ but it's blessed by RFC7159 - if
there's an inconsistency we should get it sorted out.

On Sat, Nov 18, 2017 at 3:54 PM, Anders Rundgren <
anders.rundgren.net@gmail.com> wrote:

> 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
>
> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json
>



-- 
- Tim Bray (If you’d like to send me a private message, see
https://keybase.io/timbray)

v2.23.0 | Report a Bug | By Email