I dunno, I've done a lot of work with SVG, and I find the verbosity to be quite useful. It really depends on how you decide to use it - for me, its an excellen

I dunno, I've done a lot of work with SVG, and I find the verbosity to be quite useful. It really depends on how you decide to use it - for me, its an excellent container format once you have coded a little controller-view abstraction. For example for a music-editing software project (internal, not publically released) I once used SVG as the primary User interface description language, with nodes named according to the verbs and objects in the UI paradigm, with the DOM structure being modified from a C++ application as needed depending on realtime input from the user. It works fabulously for this .. All I had to do was provide a dictionary of key node names to a UI designer, tell them "whatever you call a 'dial' has to have a 'needle', and then it will work for all controls that are using your dial skin", and hey-presto: instant UI appeal! Without any major coding changes it was possible to have very fresh, very appealing user interfaces built up by artists overnight .. and another thing I found interesting was that those artists I worked with that understood that the Node Editor was the primary interface to my program, were able to get really nice stuff done, fast, and with enthusiasm.. whereas those who complained that SVG wasn't Illustrator and that they were /never/ going to learn Inkscape to build the GUI and that I had to learn to use 'the real tools .. like Illustrator' .. well, that was just a waste of time. So my personal experience with SVG has been superb .. I really think its an excellent data form for design user interfaces and, given the appropriate strategy for how to lay out SVG nodes in a manner that makes sense (hint: group), it can be very fun for artistic/creative hats to participate directly in the skinning of an application ..