We have a micro services architecture and we are current using an osprey proxy as our gateway to our micro services. This approach forces us to use a single RAML file that contains all the definitions for our APIs for all our micro services. Naturally we would a API documentation and validation structure that reflects and supports the modularity of our architecture. A anyone had to solve this issue? If so how was this solved?