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 30D0DC14F5EF
	for <cbor@ietfa.amsl.com>; Thu, 25 Jul 2024 16:15:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.209
X-Spam-Level: 
X-Spam-Status: No, score=-4.209 tagged_above=-999 required=5
	tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3,
	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 ijYrnt_SlMPS for <cbor@ietfa.amsl.com>;
	Thu, 25 Jul 2024 16:15:12 -0700 (PDT)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [134.102.50.21])
	(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 4869FC14F5F4
	for <cbor@ietf.org>; Thu, 25 Jul 2024 16:15:12 -0700 (PDT)
Received: from smtpclient.apple (p5dc5d6c5.dip0.t-ipconnect.de
 [93.197.214.197])
	(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 4WVRYp2GtwzDCbK;
	Fri, 26 Jul 2024 01:15:10 +0200 (CEST)
Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.600.62\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: 
 <SJ0PR17MB433422441779AB52D3B3194ED2AB2@SJ0PR17MB4334.namprd17.prod.outlook.com>
Date: Fri, 26 Jul 2024 01:14:59 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <90467466-AD96-4B96-B936-315717F888B8@tzi.org>
References: 
 <SJ0PR17MB433422441779AB52D3B3194ED2AB2@SJ0PR17MB4334.namprd17.prod.outlook.com>
To: Steve Lasker <StevenLasker@hotmail.com>
X-Mailer: Apple Mail (2.3774.600.62)
Message-ID-Hash: BHACTIEVV4H3VHS4E6Y4DEMK6EFWVFOL
X-Message-ID-Hash: BHACTIEVV4H3VHS4E6Y4DEMK6EFWVFOL
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@ietf.org" <cbor@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: =?utf-8?q?=5BCbor=5D_Re=3A_CBOR_Tooling_breadth_of_use?=
List-Id: "Concise Binary Object Representation (CBOR)" <cbor.ietf.org>
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/cbor/yIGDXm3qQYjbozCJV-wByLHPrxM>
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>

Hi Steve,

> On 26. Jul 2024, at 00:52, Steve Lasker <StevenLasker@hotmail.com> =
wrote:
>=20
> How much energy and acknowledgement is there around CBOR and COSE =
tooling? Does the CBOR community feel it=E2=80=99s not intended as a =
general-purpose data format, and it=E2=80=99s good enough? Or, is there =
a desire to make easier for more to use?

I think that this is a great question.
The CBOR WG is not really set up to answer it, but its mailing list is a =
good way to get some coordination.

Most of the gaps I=E2=80=99m aware of are in the way of integration into =
existing tools.
Typically, this integration is best done by people who already know =
about the functioning and complex interfaces of those tools.
If we find some people who are interested in supporting CBOR, this list =
might be a good place to find the help they might need from the CBOR =
side.
I=E2=80=99m certainly offering my help (if people want to work with =
someone who doesn=E2=80=99t know much in the way of VSCode or what your =
tool of choice might be).

It would also be good to collect some information on how well tools work =
that already have CBOR support (e.g., Wireshark) and possibly organize =
some remedies.

A third activity might be to collect links to howtos or softwares in an =
accessible form.

(Oh, and the position of the author of simdcbor is still open :-)

Gr=C3=BC=C3=9Fe, Carsten

PS.: Here are a few lines for your .emacs, if you like to operate on =
CBOR in YAML form.
Substitute =E2=80=9Cdiag=E2=80=9D for =E2=80=9Cyaml=E2=80=9D to work in =
CBOR EDN (but this might need a few more options).

(add-to-list 'jka-compr-compression-info-list
             ["\\.cbor$"
              "converting YAML to CBOR"
              "yaml2cbor.rb"
              ()
              "converting CBOR to YAML"
              "cbor2yaml.rb"
              ()
              nil nil ""])

(jka-compr-update)

