[Json] JSON or I-JSON?
Pete Cordell <petejson@codalogic.com> Fri, 26 February 2021 11:02 UTC
Return-Path: <petejson@codalogic.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 3B5283A130F for <json@ietfa.amsl.com>; Fri, 26 Feb 2021 03:02:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 DwRoNMXvCKmq for <json@ietfa.amsl.com>; Fri, 26 Feb 2021 03:02:28 -0800 (PST)
Received: from ppsa-online.com (ppsa-online.com [217.199.162.192]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB2E93A130E for <json@ietf.org>; Fri, 26 Feb 2021 03:02:27 -0800 (PST)
Received: (qmail 20798 invoked from network); 26 Feb 2021 11:02:25 +0000
Received: from host31-49-16-155.range31-49.btcentralplus.com (HELO ?192.168.1.72?) (31.49.16.155) by lvps217-199-162-217.vps.webfusion.co.uk with ESMTPSA (AES128-SHA encrypted, authenticated); 26 Feb 2021 11:02:25 +0000
To: "json@ietf.org" <json@ietf.org>
From: Pete Cordell <petejson@codalogic.com>
Message-ID: <90cddfc3-c320-5ac0-210b-c77636383a6b@codalogic.com>
Date: Fri, 26 Feb 2021 11:02:24 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.8.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-GB
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/Sf01jGHgs6JA26usclNjq4dz7lE>
Subject: [Json] JSON or I-JSON?
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 26 Feb 2021 11:02:30 -0000
Quick question if I may... When defining new IETF standards that want to use JSON, are they referencing JSON (RFC8259) or I-JSON (RFC7493)? Thanks, Pete. -- --------------------------------------------------------------------- Pete Cordell Codalogic Ltd C++ tools for C++ programmers, http://codalogic.com Read & write XML in C++, http://www.xml2cpp.com ---------------------------------------------------------------------
- [Json] JSON or I-JSON? Pete Cordell
- Re: [Json] JSON or I-JSON? Anders Rundgren
- Re: [Json] JSON or I-JSON? Carsten Bormann
- Re: [Json] JSON or I-JSON? John Cowan
- Re: [Json] JSON or I-JSON? Pete Cordell
- Re: [Json] JSON or I-JSON? Pete Cordell
- Re: [Json] JSON or I-JSON? Tim Bray
- Re: [Json] JSON or I-JSON? David Kemp
- Re: [Json] JSON or I-JSON? John Cowan
- Re: [Json] JSON or I-JSON? Phillip Hallam-Baker