I think writing a converter from WADL to this format would be better.

You might ask, Why I am sticking with this format? It's because this format is easier to write in for users with as few requirements as possible which are the ones I needed to generate client libraries.

A converter is nice but I was thinking more along the lines of pre-existing RESTful web services. I can see a use case for developers that want to generate client libraries and not want to convert to a new format. Additionally WADL is automatically generated (at least when using a framework like Jersey it is).

Would the converter be an option added to alpaca or better suited as a separate tool?

More like an option so that people wont have a problem with converting.

Sounds good. I'll see if I can carve out some time to add this feature in. I don't know Go but I'm sure it has a decent XML DOM parser. If you have any recommendations let me know.

Definitely. I would appreciate your help. :)

One simple Go code generator from WADL documents: https://github.com/katco-/wadl2go
@katco-