Re: [Json] Adding integers to JSON (Re: JSON Schema Language)

Carsten Bormann <cabo@tzi.org> Thu, 09 May 2019 17:37 UTC

Return-Path: <cabo@tzi.org>
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 30FFC12003E for <json@ietfa.amsl.com>; Thu, 9 May 2019 10:37:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 h1ADhj6wHtbz for <json@ietfa.amsl.com>; Thu, 9 May 2019 10:37:03 -0700 (PDT)
Received: from smtp.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1903F1200C1 for <json@ietf.org>; Thu, 9 May 2019 10:37:03 -0700 (PDT)
Received: from [192.168.217.106] (p54A6CC75.dip0.t-ipconnect.de [84.166.204.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.uni-bremen.de (Postfix) with ESMTPSA id 450LBM5cGszyVN; Thu, 9 May 2019 19:36:59 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAMm+Lwi20mv1u0KpO0GWpxoCEOj_CERFieA0RuiJ1a4innAURg@mail.gmail.com>
Date: Thu, 09 May 2019 19:36:58 +0200
Cc: Nico Williams <nico@cryptonector.com>, JSON WG <json@ietf.org>
X-Mao-Original-Outgoing-Id: 579116216.983811-e119c885b56fca45e1322bb1d10a9276
Content-Transfer-Encoding: quoted-printable
Message-Id: <A882918E-B02F-481B-9CDF-3D5C46D9F1C9@tzi.org>
References: <CAHBU6itE8kub1qtdRoW8BqxaOmzMv=vUo1aDeuAr3HX141NUGg@mail.gmail.com> <77994bdb-a400-be90-5893-b846a8e13899@gmail.com> <20190507154201.GP21049@localhost> <CEF72901-5077-4305-BA68-60624DCE952D@bzfx.net> <69ea0c99-e983-5972-c0aa-824ddeecb7c4@dret.net> <CAMm+LwjyVjnJuWE4+a9Ea=_X1uuEGuK+O4KojzN3uVQ+s+HqUQ@mail.gmail.com> <058f58a3-dd27-998e-5f54-4874aff5f2f0@dret.net> <20190507221726.GR21049@localhost> <CAJK=1Rj7PBD-bbwvsqgjQQzp4Aoidb-W2q5Lj6asMHHDHaTVYQ@mail.gmail.com> <702ee54b-9465-7ca8-b521-2a88c1a47785@gmail.com> <20190508160740.GU21049@localhost> <ACD9A0A2-A75E-4B6E-9E9B-165DC222781B@tzi.org> <CAMm+Lwi20mv1u0KpO0GWpxoCEOj_CERFieA0RuiJ1a4innAURg@mail.gmail.com>
To: Phillip Hallam-Baker <ietf@hallambaker.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/Q8ltDPuNaM5kOyqd3auXKKBWCww>
Subject: Re: [Json] Adding integers to JSON (Re: JSON Schema Language)
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: Thu, 09 May 2019 17:37:05 -0000

> I would really like to see a JSON-like format emerge as an alternative to CSV because, I have spent too much time trying to analyze files that contain data separated from the context.

SenML, RFC 8428, was made for this.  Can be serialized in XML, EXI, JSON, CBOR.

> If I am doing science, I want files that look like this
> 
> { "TemperatureData" : {
>    "StartDate" : "2010-1-1",
>    "EndDate" : "2011-2-2",
>    "Location" : "Rome",
>    "Units" : "Centigrade",
>    "Channels" : [ "C1", "C2", "C3", "C4", 
>    "Readings" : [[ 20.2, 23.3, 44.3, 20.1 ... ] [34.3, 3.4 ...] ... ]
> 
> Not this
> 20.2, 23.3, 44.3, 20.1 ...
> 34.3, 3.4...
> …

SenML looks a bit different, but has the same kind of information content.
If you really want the arrays that are in your example, it would be an interesting exercise to extend SenML for that — up to now, the large organizations that use it have been happy with what we have.

Grüße, Carsten