@Athaj wrote:
And how would the JSON respond to eventual changes in the data structure? Is there a similiar rigidity like with the XML?
It doesn't really matter.
Both XML and JSON, DB or whatever would have the same issues.
If you use the native LV JSON (un)flatten, the problems will be the same as with the native XML (un)flatten tools. If the data is the same, it will work. If it isn't, it won't work.
So if you want flexibility, you'll make tools to get individual elements, and store them to the individual LabVIEW elements. There are several ways to do this. All involve getting the values, and composing them into the LabVIEW object. No matter if DB, XML or JSON is the source, at some point you'll get a value. This value can be converted to LabVIEW by somehow unflattening ( XML, JSON, or string).
So you have source (whatever) -> text\binary -> binary\XML\JSON- > binary.