So I had mixed opinions on this subject when I started the XML.  That is why the first one had the path and the rest did not.  We DO NOT want to just make the first fully qualified and the rest different.  That was just an accident and addressing the path name issue is on my personal to-do list.

When I started this we weren't looking at DISA moving and maintaining the SVGs on GitHub.  So there was no assurance that the folder names would be standardized.  Therefore I decided not to include them.  Thus just the svg files names are included.  My feeling was that if the paths ever changed, or if an implementer using the XML chose to store his svgs in a different folder structure, dealing with hard coded path names in the XML would be problematic.

I believe the Graphic attributes should be kept short and simple and just include the file name.  I realize that Chris, you need full path names in CSV output.  My plan was and is to put the path strings inside the jmsml.config file that was always intended for this purpose, so paths could be changed by end users of the library.

Since I have yet (but am about to) produce you CSV output that has svg data in it, I was going to take care of this today and tomorrow.