[Cbor] Re: EDN redux

Carsten Bormann <cabo@tzi.org> Wed, 07 August 2024 15:53 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5AD7C16942C for <cbor@ietfa.amsl.com>; Wed, 7 Aug 2024 08:53:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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
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 WsJaDehlKGXV for <cbor@ietfa.amsl.com>; Wed, 7 Aug 2024 08:53:26 -0700 (PDT)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 56038C15155A for <cbor@ietf.org>; Wed, 7 Aug 2024 08:53:24 -0700 (PDT)
Received: from clients-pool3-0220.vpn.uni-bremen.de (clients-pool3-0220.vpn.uni-bremen.de [134.102.69.220]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4WfF812QZGzDCfX; Wed, 7 Aug 2024 17:53:21 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAKoiRuYFzZKOubSN1hC=1DqMfv2jWar2zQ1i9d40RpW-5vm9vQ@mail.gmail.com>
Date: Wed, 07 Aug 2024 17:53:20 +0200
X-Mao-Original-Outgoing-Id: 744738800.606395-c02f13ef3dd1d8026cb10c811384d970
Content-Transfer-Encoding: quoted-printable
Message-Id: <B327B308-9DFA-4CED-8BF0-D55CCC4DB18C@tzi.org>
References: <7C93E178-2D2A-44E1-96A2-EB55048052DD@tzi.org> <CAKoiRuZebuHWhZ1AK6TPZDAdYgvQQBkM7Hdeyi7X=aFfFeQ3PQ@mail.gmail.com> <D7E13419-35FE-4ACC-BBE6-CDBAE83F4570@tzi.org> <CAKoiRubpwB6=JE=Bk5oh5o=wfxk0TGjA9_6MmcDRiXpRvVEVnQ@mail.gmail.com> <A6C5FBDD-E85E-4FEA-A784-B5F92BF6449B@tzi.org> <CAKoiRuYFzZKOubSN1hC=1DqMfv2jWar2zQ1i9d40RpW-5vm9vQ@mail.gmail.com>
To: Rohan Mahy <rohan.mahy@gmail.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Message-ID-Hash: IV6VWYAOV2U7YQYVZPKGXN4TM43DWH3T
X-Message-ID-Hash: IV6VWYAOV2U7YQYVZPKGXN4TM43DWH3T
X-MailFrom: cabo@tzi.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-cbor.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: CBOR <cbor@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Cbor] Re: EDN redux
List-Id: "Concise Binary Object Representation (CBOR)" <cbor.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/XWg4h2MXa1jcJS8eS87tkmHponw>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Owner: <mailto:cbor-owner@ietf.org>
List-Post: <mailto:cbor@ietf.org>
List-Subscribe: <mailto:cbor-join@ietf.org>
List-Unsubscribe: <mailto:cbor-leave@ietf.org>

On 2024-08-07, at 17:41, Rohan Mahy <rohan.mahy@gmail.com> wrote:
> 
> Hi Carsten, since you think so many people misunderstand what this document is for, maybe you could write your requirements so you're on the record. They certainly seem to have shifted at various points in this argument. 

The document sure did evolve: It started out as a brief description of the extension point.  Additional desirables were added over time, in particular the desirable for an ABNF definition of EDN, which in turn made it much easier to add support for somewhat relaxed, easier to use grammar (e.g., optional commas and an optional terminating comma that no longer fights with git).

> I think the most important value of EDN is to provide a well-specified, easy-to-use, JSON-like, human-readable and human-writable format that end-users can use to express CBOR instance documents, and can be converted in both directions. 

Yes.  
We wouldn’t need a new document for that, as RFC 8949 in conjunction with RFC 8610 already provides that.  
But we can still make it easier to use.  
E.g., time values can always be expressed as seconds since UNIX epoch, and had to be in 8949/8610 EDN.  
The current document adds an extension point that can be used for writing more readable expressions of CBOR data items, specifically via the dt’’ application-extension literal.

> Extending app-strings is pretty low on my list compared to any of the above, and certainly makes any machine-consumable conversion to/from CBOR instance docs more complicated.

Maybe this document is not really relevant for you then?

> To be clear, CBOR didn't define tag 999. This is yet another extra "feature" you've added to the EDN draft.

Tag 999 was defined out of experience of protocol evolution.
Enabling components of a system to tolerate the use of an extension point that they themselves do not support yet is desirable to sustain protocol evolution.  
Of course, this could be left out, making the deployability of the extension point much worse.  
You don’t care about the extension point, so that may seem trivial to you.

Grüße, Carsten