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

John Cowan <cowan@ccil.org> Thu, 09 May 2019 23:16 UTC

Return-Path: <cowan@ccil.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 51EB11200EB for <json@ietfa.amsl.com>; Thu, 9 May 2019 16:16:47 -0700 (PDT)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ccil-org.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 qa3pljgaonE1 for <json@ietfa.amsl.com>; Thu, 9 May 2019 16:16:45 -0700 (PDT)
Received: from mail-wr1-x429.google.com (mail-wr1-x429.google.com [IPv6:2a00:1450:4864:20::429]) (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 4F7DF1200DF for <json@ietf.org>; Thu, 9 May 2019 16:16:45 -0700 (PDT)
Received: by mail-wr1-x429.google.com with SMTP id d12so5227347wrm.8 for <json@ietf.org>; Thu, 09 May 2019 16:16:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ccil-org.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+HtQqS+Gb5DEePil7eDy+a0QH4ph2EVFv+yVVSepBTY=; b=gSqvnWavJ0TYn35ofDze7WvmeptO6pVaLB9iUT657WhFQ4OwRxtHU2eN1BovFL/c9u qD8bjLquoLEpz/3iTHMJPsXYNTZanQbBiQwcHUKn2eYXjlvmD+Vk5PgRH7AIOLB0ESV2 saDo1uCGWJqHoTpoBEMBPT4dbh4P23mcyYKj0glEZ0LAtvGrT0QDEfgX12gDk6Hos2Hc DXCr7Q/Kbo/Fq47/JB8ub7gWU15vKHqvLxE+cHH7RvrXElcF7Rtr58NWl5eiNjZyp0xi mcQyqF0E4qyaOZOznepREaXmUEFdLpPp0vunnRjM2D+AU8VB3oYFqjnB1YHWr8SU8IFV yDBg==
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=+HtQqS+Gb5DEePil7eDy+a0QH4ph2EVFv+yVVSepBTY=; b=tjGNh8twc+HWnrK0X01x8naW2zHR01phzw2fyK5zzHAFDmDx53hrWTuVpchz0j3CgJ 2DeSpamc1GN/V/Qq1+0/6w9+Bg25GMgbLHFJXEzjpquWmpWx29Bk1lUR9Bnqc+9dvV/s MhgoPy5Jo4BHHVIq0u6C00LTJiM4LRcJvrjnYHB/oiVrgVEWLgQR7Ajvt8vYogKIbe6c DYBrzUlqq69/WAZ96kqGTFnK99Z2wJhB3i49e8sjFYPhzgnMXOOjII1eHEZZUz85NiKt 0Xal0sEsaV1BoMw9AYIEKDTpLlEnYBnWaxUgOKcaCfL6QzXr/FUbFKY3AFJx2qQL0o7V o3EA==
X-Gm-Message-State: APjAAAXzqJyM9QfntXOI2eIZMqqc8IZOwwnvcIbWUDILVA3JaBMlLpLi 1VeAc084WyD24ZJmP3K8siDyd2xq8/Dbgc+dcVhn1GDfOPs=
X-Google-Smtp-Source: APXvYqyeWCvM4JxFXJgYwF8j4iSRv2AUOa08TWVBvADy7kA7bMpn9nZuzXP7I1osjAsdsmKBVT6fZn3kUbrvglV8Ntc=
X-Received: by 2002:a05:6000:43:: with SMTP id k3mr5165242wrx.234.1557443803743; Thu, 09 May 2019 16:16:43 -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>
In-Reply-To: <CAMm+Lwi20mv1u0KpO0GWpxoCEOj_CERFieA0RuiJ1a4innAURg@mail.gmail.com>
From: John Cowan <cowan@ccil.org>
Date: Thu, 09 May 2019 19:16:32 -0400
Message-ID: <CAD2gp_TFjFLLVu=kBu6gmGBVx3xGBL_1sea8EmQ6x-jvpm7g_Q@mail.gmail.com>
To: Phillip Hallam-Baker <ietf@hallambaker.com>
Cc: Carsten Bormann <cabo@tzi.org>, Nico Williams <nico@cryptonector.com>, JSON WG <json@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ae1e7d05887ca449"
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/7LHJUyjg-1nbxe9er7qJZFlbNig>
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 23:16:48 -0000

On Thu, May 9, 2019 at 1:15 PM Phillip Hallam-Baker <ietf@hallambaker.com>
wrote:


> * Allow compact encoding of table data without having to specify tags for
> every data item.
>

If data is stored columnwise instead of row-wise, that's not a problem with
as-is JSON.  You could represent a table of observations like this:

{"elapsedTime":  [0, 5, 10, 15, 20, 25, 30, 35, 40, 45, 50],
 "waterTemperature": [25, 25, 33, 47, 60, 72, 88, 91, 100, 100, 100]}