Re: [dispatch] Request for feedback on draft-thomy-json-ntv-01
Philippe THOMY <philippe@loco-labs.io> Fri, 15 September 2023 21:31 UTC
Return-Path: <philippe@loco-labs.io>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 786D8C151072 for <dispatch@ietfa.amsl.com>; Fri, 15 Sep 2023 14:31:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=loco-labs-io.20230601.gappssmtp.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fP-RnPj7wFK2 for <dispatch@ietfa.amsl.com>; Fri, 15 Sep 2023 14:31:41 -0700 (PDT)
Received: from mail-oa1-x35.google.com (mail-oa1-x35.google.com [IPv6:2001:4860:4864:20::35]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A076BC14CE53 for <dispatch@ietf.org>; Fri, 15 Sep 2023 14:31:41 -0700 (PDT)
Received: by mail-oa1-x35.google.com with SMTP id 586e51a60fabf-1c0fcbf7ae4so1533161fac.0 for <dispatch@ietf.org>; Fri, 15 Sep 2023 14:31:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=loco-labs-io.20230601.gappssmtp.com; s=20230601; t=1694813501; x=1695418301; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=+VPKHwtWcG4cWMUA3eGj6xyuGCgtrItEmOjk2/2GxYo=; b=EwYhYmrE+k0XKQFG4PO4DdLVtporEsHNTEk4MaHYuSztZLDLa5dz/tnnz09fdzllTi bHOvnb/RcPd7OlnZInXa+OyUfmAsdbxPpef/Lu35ksxz0s3UkE7uwrT1xhSil2V2YMyR 9CR1ze27d7ga/htdPrXipIZFI2sWb2aKSz3XJcwewCCfCpzMIW4A9LCRyY84ZgfpEiWN Aw8wpiHSlOwOflDiCICORhTDHV7As6Z9Bq9QM9WT5SVMFCYFIs/j+ZvMPisVE2tHK+Zc miUMWtfnuamWorLCqHbvflmK0UY2E2elSbZvp3ylrVEIAOjoS1Dxl+x+1lqOhlei1Fvo ITvA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1694813501; x=1695418301; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=+VPKHwtWcG4cWMUA3eGj6xyuGCgtrItEmOjk2/2GxYo=; b=UDtXdF6Nhi+61zGQTpQ1+2Ra/yizrvgicDHGVdbe3EKgqUmaPsSoHfjDihz2vjqjL+ pMOD5D0qFm//7p/6ifbbotV9kE4Pq1iAz12iRbjCfqX1jK2BQlWHpNTNeMFdM1UOAtxN 70jwt0rfIfNPnYlbeIQLNsgX9Hr3krFcribgh98yusbu/e5rmdy0oqvPAB1xUCjzCsRh xlx8VzenedVJsS3hRzHQlwdHWusg8bHa7889RolWtkzGDaQpuZxtCglgjoCbwZYSAt61 TSTXr8uBFeZ3m+WaEPavxZCcDXoqZjiTW8DvdMTCSH0H6HrsVdJfhkfInUpkhrPM0rjk wcvA==
X-Gm-Message-State: AOJu0YzSrvJ1G7UdDM3N/lpUy7ODv05TZn1g4UMHwCzkxLordm4UF2fV +barJm6j9/ZtxQahalw1C3G9v3+g5v8Ki87gSdhZbNwQFt1C4k+ZzGc=
X-Google-Smtp-Source: AGHT+IEnV96YEVQe6G9kdazglsHXTJYWAHPXBvd9wXGE8MVKfYUnssS9mtMtvN5yWUMmPU0N4RGtLdv/JKOmjdq6U8A=
X-Received: by 2002:a05:6870:f10d:b0:1bb:c0ee:5536 with SMTP id k13-20020a056870f10d00b001bbc0ee5536mr3286425oac.47.1694813500784; Fri, 15 Sep 2023 14:31:40 -0700 (PDT)
MIME-Version: 1.0
References: <CAMsZS+T+ocd+AAvjr2xOi8zD15=T-NddrLFWwKHQp3RwkmcL-Q@mail.gmail.com> <87zg1nb95s.fsf@hobgoblin.ariadne.com>
In-Reply-To: <87zg1nb95s.fsf@hobgoblin.ariadne.com>
From: Philippe THOMY <philippe@loco-labs.io>
Date: Fri, 15 Sep 2023 23:31:29 +0200
Message-ID: <CAMsZS+TJ5u49OFuy61UX0VDP4v35kzmBWud2s71diw8n_0pdpA@mail.gmail.com>
To: "Dale R. Worley" <worley@ariadne.com>
Cc: dispatch@ietf.org
Content-Type: multipart/alternative; boundary="000000000000acda3306056c8439"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/ZumwmPczcLUeZH5faK58GzNN19c>
Subject: Re: [dispatch] Request for feedback on draft-thomy-json-ntv-01
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Sep 2023 21:31:42 -0000
On Fri, Sep 15, 2023 at 8:09 PM Dale R. Worley <worley@ariadne.com> wrote: > Philippe THOMY <philippe@loco-labs.io> writes: > > Two interpretations are possible: > > - JSON-NTV is not used enough in the IETF, so it will not be able to > evolve > > into RFC > > - JSON-NTV is not used enough in the IETF, it must therefore be used more > > in the IETF to evolve into RFC > > (I prefer the second interpretation !!) > > My meaning is a somewhat vague, but could be phrased "Why does the IETF > care?" Usually the answer to that is that various network operations > involve the concept in question, or would be improved by using the > concept in question. > You are right, the question is completely legitimate. Here are some partial answers: *General view:* The semantic level of shared JSON or CSV data remains low. It is often limited to the type of data defined in these exchange formats (strings for CSV formats; numbers, strings, arrays and objects for JSON formats). The reuse of data cannot therefore be automated without an external 'data schema' (e.g. if I have data [4.21, 41.234, 4.31, 41.5] I do not know what this array represents. In the JSON-NTV format, the type is integrated and the data will be {':box': [4.21, 41.234, 4.31, 41.5]}. 'box' is a standard type defined in GeoJSON and I can automatically transform it into a 'polygon' which can be visualized on a map). These automation (and quality) gains are found in several areas: IoT interface (for those who use JSON), database interface, BI/Dataviz interface, open-data, data analytics *Example of tabular data (application that I know best): * The majority of open-data sharing is carried out with the CSV format (RFC4180 - 2005). This format is obsolete and continues to exist (with non-standard extensions) only because there is no alternative format. The JSON-NTV format for tabular data (not yet described in an ID) is an optimized format (size) compared to the CSV format and explicitly addresses the question of column typing (and automation of reuse of tabular data ). This also makes it possible to have an identical file format and API format (facilitates the accessibility of open-data data). Furthermore, the module implemented with pandas shows that this makes it possible to have a reversible JSON format (lossless round trip) for all data structures supported by pandas (does not exist today). *Why IETF?* The IETF has managed the CSV format and manages the JSON format and its extensions (e.g. JSON-patch, JSON-pointer, JSON-path, GeoJSON, CBOR). Naively, it therefore seems 'logical' to me that this extension is supported by the IETF. > > - does the [JSON-NTV] notation refer to a possible WG? > > Actually, "[JSON-NTV]" is the reference tag the I-D uses for a document. > > Thanks, that’s clear. Dale >
- [dispatch] Request for feedback on draft-thomy-js… Philippe THOMY
- Re: [dispatch] Request for feedback on draft-thom… worley
- Re: [dispatch] Request for feedback on draft-thom… Philippe THOMY
- Re: [dispatch] Request for feedback on draft-thom… worley
- Re: [dispatch] Request for feedback on draft-thom… Philippe THOMY