(So, what you could do is use the XML-encoding of ASN.1, and then use _that_ in the place of your (current) XML, and then simply allow eg DER encoded objects.)
If it's mostly consumed and edited by a machine/LLM, xml might actually be ok. Otherwise, I think something a bit less ceremonial. Obviously there's lots of options, and I imagine you may even miss much of the tooling of XML (schemas and such).
Kind of a drive-by comment, I admit, but it just struck me as a little surprising.
Also: it's been some 3 decades since I was playing with Ada ... very cool to see it getting some GUI love!
As happy user of qt desktop framework, not sure in what sense it’s dated.
Not sure how qwt relates to this tho? https://qwt.sourceforge.io/
Making coherent ux with it still seems much easier than in qml, it has the right constraints and visual editing it is reasonably lightweight, unlike qml studio. Of course it has its flaws too but UX wise it is still hard to find an equally mature cross platform toolkit.