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

Phillip Hallam-Baker <ietf@hallambaker.com> Thu, 09 May 2019 20:04 UTC

Return-Path: <hallam@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 D26D61200FC for <json@ietfa.amsl.com>; Thu, 9 May 2019 13:04:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.649
X-Spam-Level:
X-Spam-Status: No, score=-1.649 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 B-BFWmvnMlol for <json@ietfa.amsl.com>; Thu, 9 May 2019 13:04:37 -0700 (PDT)
Received: from mail-oi1-f172.google.com (mail-oi1-f172.google.com [209.85.167.172]) (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 BD15D12006B for <json@ietf.org>; Thu, 9 May 2019 13:04:37 -0700 (PDT)
Received: by mail-oi1-f172.google.com with SMTP id l203so2900048oia.3 for <json@ietf.org>; Thu, 09 May 2019 13:04:37 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=M8uunREZ3gp85BP2WZ0gzocBwVgbcpYIMz9q5mdOl9A=; b=bLM+NMnt1WHyuYbsLuT+eVe4JEOdZ1vLwUsdQAUWEh5njP4VBtgZniUuATcEPHoE7v mfHztpnccQaHJDJYFhgtFbMcF8h//vqR+b/5JdP8x/frvBe6fUkuh+tR3ocYJm6K42/R nLsGuFDyRenvjjrSU1AK9r0zY9QCNJ2Ax0b7c1cjN/WrPhn5o5yZT3d5IvWrFhiVY6Vj D7GkQwUwon2E/jf+PbpHFxTRni5JBL/SS5zClAGRH/zNvhLl5XIweCrvpVMgNnk/RiFX snqISb65b/7Ad8qO9e9HIay56aN5pTseBwx9/drGHacWlvlfEwHszUiCiDAMSbIXIa52 4Tzg==
X-Gm-Message-State: APjAAAU3g0J/cmA7w46AQRudRwiX9UTcpqh0Koy0TTE1jTe4nBMgCGlN SfJ6QXPHRNC0EWz+7qMCMv7d3sthuDpuwCx2xjk=
X-Google-Smtp-Source: APXvYqzESkZ7wlpvwMMCtqvIaY3W6SSW2Lytno4F2qouwWj8CboZYs0zihJ3fxLrWVSviBzPwjUBQJBKyWl6zDG8NOY=
X-Received: by 2002:aca:43d5:: with SMTP id q204mr2803709oia.100.1557432276785; Thu, 09 May 2019 13:04:36 -0700 (PDT)
MIME-Version: 1.0
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> <A882918E-B02F-481B-9CDF-3D5C46D9F1C9@tzi.org>
In-Reply-To: <A882918E-B02F-481B-9CDF-3D5C46D9F1C9@tzi.org>
From: Phillip Hallam-Baker <ietf@hallambaker.com>
Date: Thu, 09 May 2019 16:04:26 -0400
Message-ID: <CAMm+LwgAVOMitgQ45ap4cAXqyMbVX2NLstt=n+O_4==WQK8=Tg@mail.gmail.com>
To: Carsten Bormann <cabo@tzi.org>
Cc: Nico Williams <nico@cryptonector.com>, JSON WG <json@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009eacfe058879f515"
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/q-xXKUhkZl1iF3CZ-6DGtIIaQqY>
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 20:04:39 -0000

On Thu, May 9, 2019 at 1:37 PM Carsten Bormann <cabo@tzi.org> wrote:

>
> > 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.
>

I was using temperatures as an example to illustrate the fact that the
general case for science data is that I have a bunch of information
describing the data set and a series of tables.

If I am using SciKit-Learn to analyze data, I am typically importing a
bunch of data files containing different tables and doing joins and merges
on them. A lot of the context for the process is lost because a CSV file
can only contain the table. So this morning I was looking at a ZIP file
that had the following file layout:

descrip.txt  # this file
dataset.json # the metadata
twitter.csv # Twitter persona data
facebook.csv # Facebook persona data
tweetlog.csv # Posts to twitter
fblog.csv # Posts to Facebook

Oh and they each have different layouts and syntax. I have to pull them
into Pandas, construct data frames, drop out features to SciKit and then
identify the fake news sources.

I think it would be actually quite easy to just dump out one file that has
everything in JSON and for this to be engineered so that the relevant
Pandas frames are constructed automagically.. But that is not where the
field is right now.