If you want to play with the machine side of things, you can replace
the "html" extension with "js" for a JSON version, or "dump" for a Perl
Data::Dumper format. I don't expect anyone to write a client that uses
the Perl stuff, but it's useful for debugging and hey, if you want to
use it, I don't see a reason for it to go away. 

To be properly RESTful, Wirebird will need to actually pay attention to
the "Accepts" headers (technically it does but the extensions override
it for debugging purposes, which will be reversed for production). You
can test this by leaving off the extension and specifying Accepts... I
haven't yet, so if you do this let me know. 

Of course, I shouldn't actually post this until I have all the stuff
cleaned up and standardized. Right now, you'll be able to see some
RESTlessness in that I don't have all the links coming through
properly, things like that (because I originally assumed constructed
URLs, in the pre-REST days, but REST calls for explicitly passing
them). 

Also, trivia note: I got a hit here by someone from apple.com, using
Firefox on OS X, googling for "perl restful." Read into that what you
will.