Re: [Json] [Asdf] Kicking off ASDF charter discussion

Carsten Bormann <cabo@tzi.org> Sat, 08 August 2020 07:45 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 C0F043A0E89; Sat, 8 Aug 2020 00:45:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, 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 c-UtKKD9c4Tp; Sat, 8 Aug 2020 00:45:35 -0700 (PDT)
Received: from gabriel-vm-2.zfn.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 84CA43A0B82; Sat, 8 Aug 2020 00:45:35 -0700 (PDT)
Received: from [172.16.42.101] (p5089ae91.dip0.t-ipconnect.de [80.137.174.145]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4BNvR21K57zyrT; Sat, 8 Aug 2020 09:45:34 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <2A11875E-43EA-4227-A6E7-A7F5A09831EC@tzi.org>
Date: Sat, 08 Aug 2020 09:45:33 +0200
Cc: asdf@ietf.org, json@ietf.org
X-Mao-Original-Outgoing-Id: 618565533.799698-6171c62f7c86e4dd60c9558d09dbb211
Content-Transfer-Encoding: quoted-printable
Message-Id: <B863207C-AEB4-4745-9902-64F41D166F36@tzi.org>
References: <5C210025-34B4-45BC-9A1D-66D9E92B339A@tzi.org> <3271.1596839115@localhost> <2A11875E-43EA-4227-A6E7-A7F5A09831EC@tzi.org>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.3608.120.23.2.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/KWdxLowU0mp-g3mcsEbCT-960Q4>
Subject: Re: [Json] [Asdf] Kicking off ASDF charter discussion
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: Sat, 08 Aug 2020 07:45:38 -0000

On 2020-08-08, at 09:25, Carsten Bormann <cabo@tzi.org> wrote:
> 
>> 2> It will also engage the still active mailing list of the
>> 2> dormant JSON WG.
>> 
>> Is this about json-path, and/or json-schema?
> 
> Probably more about json data definition (which includes the json-schema.org proposals that have been inspiring the SDF data definition components).

…and it is probably worth pointing out that, while SDF itself is notated in JSON (and thus benefits from CDDL), the data models that SDF describes cannot be limited just to the expressive gamut of JSON data.  So a JSON data definition format such as those proposed at json-schema.org can be an inspiration, but cannot on its own solve the entire problem.

Grüße, Carsten