[Cbor] CBOR Tooling breadth of use

[Steve Lasker <[e-mail]>]

Working with developers outside of IETF, adoption of CBOR has met resistance, ...due to a lack of tooling. There have been various libraries starting to surface, for using CBOR in code, however the lack of visualization, editing, debugging is a limitation. It's just too easy to open a json, yaml, (dare I say xml) files. To pass parameters, et.
One could argue it's still "early", and we need more time for adoption, and IETF is a forward-looking community.

However, sitting in various IETF meetings, I'm seeing "fellow community folks" also resist cbor, wait for it, ...due to a lack of tooling.

I'm familiar with https://cbor.io/. And while these are a start, they haven't yet met the bar for breadth usage.

To grow adoption of CBOR (and COSE) as a highly efficient, not subject to canonicalization general data formats, it really needs to be easier to use. We don't need "Yet Another Markup Language", we need great end to end tooling for a better protocol.

As a rough comparison, the photo or video industry didn't feel constrained to text files. You can't open a picture in your favorite text editor. You can "double click" pictures in various viewers and editors.

How much energy and acknowledgement is there around CBOR and COSE tooling? Does the CBOR community feel it's not intended as a general-purpose data format, and it's good enough? Or, is there a desire to make easier for more to use?