Both Tim Bray and Paul Prescod are talking about SVG, which is quite timely. Just last week I was doing SVG myself. I had large chunks of data from disparate systems that I needed to visualize. The nice part about SVG being an XML vocabulary is that it is just as easy to generate programmatically as it is with a content generation tool. It didn't take me long to put together a Python script that ran over the files and plotted them out in a unified SVG file. You won't see me doing the same with a Word document any time soon.
After getting some hands on experience I like SVG even more than before when I just liked it in theory. The format itself is clean, with good naming conventions for it's purpose. Note that I say that as a caveat. While SVG is mostly an attribute driven format, I like the element driven design that Atom is taking for it's vocabulary. The difference is in the intended audience. SVG can show up in-line in an HTML document, and the use of attributes vs. elements in SVG is tuned so that just the right stuff shows up in old browsers that don't understand SVG. On the other hand, Atom was never meant to be embedded into HTML and as such works much better with the majority of information in elements.
So the script was easy to put together, part of that being the cleanness of the Python language, and part being that Python is a scripting language. It is very easy to pop into the Python environment, try out a few things, building up code incrementally, then moving working pieces into a
.PY file. This is made even easier when you run Python right in the Emacs editor.
Speaking of content generation tools, the Draw program in OpenOffice can generate SVG, and that generation has improved dramatically in the 1.1 release. All in all I think that SVG does indeed have a bright future, given that as of today SVG is here, viewers are available, it's amenable to "view-source" and it just works. It also has the luxury of not being surrounded by a lot of hype and the associated unrealistic expectations, something that hurt VRML.
Posted by Adam Keys on 2003-07-19
Here is a pretty large list:
I would like to see someone do a review of the listed tools for price/performance/standards compliance.
Posted by joe on 2003-07-20
Posted by Paolo Marcucci on 2003-07-18