Well the first thing you can do is export your table in a simple XML format that maps the tables so clients can use it for whatever use, maybe feeding another DB, or filtering out some information, or adding some more, or presenting differently.

_you_ don't have to store the information in XML, but making it available in such a way makes it much more easy for others to re-use it. A time element is much easier to process than the second column of a table. Especially if (when) at some point in the future you change the structure of your table and you add an extra field in between the first 2. HTML processors will be all messed up while, if written properly XML clients will still work fine.

On the other hand of course you might not want clients to be able to re-create your data base and you might want to avoid exporting XML.

The nice thing about XML on the client side is that it is a slightly self-documented format, standard, stable, and that can be processed using a lot of different tools, form XSLT processors to Java libraries and to Perl modules.

And if you just _have_ to export XML because your boss told you so, then have a look at DBIx::XML_RDB which will do it painlessly and efficiently.