I find it very interesting that I’m running across this post right now since I am finishing up a custom window that will export tag defs in a predefined CSV and allow re-import of the CSV file or just an import of a brand new CSV file.
Now I realize that the dynamic nature of Ignition tags forces the use of XML and JSON but we just defined boundaries that all our tag definitions will follow which made a CSV file format possible.