Re: [Cbor] Diagnostic Notation: Media Type?
Carsten Bormann <cabo@tzi.org> Mon, 20 March 2023 00:26 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 51A71C14F749 for <cbor@ietfa.amsl.com>; Sun, 19 Mar 2023 17:26:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.888
X-Spam-Level:
X-Spam-Status: No, score=-6.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=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 hPDgjiR7cala for <cbor@ietfa.amsl.com>; Sun, 19 Mar 2023 17:26:03 -0700 (PDT)
Received: from smtp.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 46BB9C1516F3 for <cbor@ietf.org>; Sun, 19 Mar 2023 17:26:01 -0700 (PDT)
Received: from smtpclient.apple (p548dc9a4.dip0.t-ipconnect.de [84.141.201.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.uni-bremen.de (Postfix) with ESMTPSA id 4PfwWT46mFzDCbJ; Mon, 20 Mar 2023 01:25:57 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.400.51.1.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <ZBeb1i5cwSr+nUr1@hephaistos.amsuess.com>
Date: Mon, 20 Mar 2023 01:25:47 +0100
Cc: cbor@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <2008F4AC-7339-4CCD-B079-4091618C5380@tzi.org>
References: <ZBeb1i5cwSr+nUr1@hephaistos.amsuess.com>
To: Christian Amsüss <christian@amsuess.com>
X-Mailer: Apple Mail (2.3731.400.51.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/1UfZtgeCarSBbz4M9dIanw3jbH8>
Subject: Re: [Cbor] Diagnostic Notation: Media Type?
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Mar 2023 00:26:09 -0000
On 20. Mar 2023, at 00:33, Christian Amsüss <christian@amsuess.com> wrote: > > For example, > given that all the mentioned uses are in a sense "local" environments, > would "text/x.cbor-diagnostic" make sense? I think registering a media type for CBOR diagnostic notation is one of that 10th birthday(*) presents that CBOR deserves. This should not be a text/something type, because it doesn’t describe text. Like JSON, CBOR, YAML, …, it should be an application/ type. So my vote would be for application/cbor-diagnostic. Now, which document do we piggy-back this on? We do have draft-bormann-cbor-edn-literals coming up, maybe we should put a lid on this, add the media type registration, and publish? Grüße, Carsten (*) Yes, that’s upcoming very soon.
- [Cbor] Diagnostic Notation: Media Type? Christian Amsüss
- Re: [Cbor] Diagnostic Notation: Media Type? Carsten Bormann
- Re: [Cbor] Diagnostic Notation: Media Type? Carsten Bormann