The LabVIEW Tools Network has several implementations of XML, in addition to the one that ships with LabVIEW. I've had occasion (15 years ago) to experiment with two of them -- EasyXML (JKI) and NI GXML (NI Tools Network).
I ended up using GXML, but made some modifications that "enhanced" it for the purpose I needed. I wanted a flexible data format for recording "behavioral data", where there was a set of "header" information that you knew at the start of the study, a bunch of "time-series" data where you recorded "events" (usually represented by a cluster of entries describing the parameters of a stimulus and the parameters of a response), and a "trailer" section which may have nothing more than the time the study ended. At the time, the XML "model" didn't seem to support writing Array structure one entry at a time, but since GXML had fairly-understandable source code, I "enhanced" the Array structure to put off writing the "end Array" tag until I was done.
The key to using XML is to understand the "rules" for how the data are structured by XML What is the "Shape of your Data"? How do you want to "tag" your data elements for XML? Are you basically trying to read existing XML documents or, like my case, are you looking to structure and write existing (or evolving) LabVIEW Data to an XML document?
Give us an idea of the data structure you envision. If you can do it in XML, that's fine, but you can also simply be "descriptive". And if you have LabVIEW code that does or doesn't work, please attach it (in a LabVIEW Version, like 2021, that most of the experienced Forum users can open). [It's a peculiarity of LabVIEW that the most of the people on the Forum using the latest version are students learning LabVIEW].
Bob Schor
