Hi guys, I am very new to RAML and looking on it mostly from the tool developer view.
When I am reading the spec it looks very promising comparing to RSDL or WADL, but as REST based tools developer I feel that I miss following features in the language.
Some times we need to provide some extra meta information about our REST methods, which may be used
by specialized tools to improve their understanding of REST API. For example one of my clients have a bunch of
REST API, some of them are highly specialized for using with Ext JS data binding framework and have specialized
inner language for query parameters, so our (internal) tooling needs to have additional information about this methods.
According to me it is possible to partially emulate this using traits, but this looks like not very natural way to do
Richer way to specify constraints
Another story from my customer. One of his requirements is to be able to semi automate unit and load test
generation for his REST services. To do it we need an ability to assign constraints to API parameters and ideally
some formal language to specify them. parameters and return values. Ability insert such constraints in formal API
descriptions can be enabler for much more smart automatic and semi automatic API QA tools such as test
generation and load testing tools.
Last thing that I am thinking about is an ability to add some description about how APIs may be batched.
Thanks in advance,