Thoughts? (My question is: what can you do with a RAML-formatted API description once you have it? Is it just an exercise and sanity check of your API?) Topic: RAML stands for RESTful API Modeling Language. It's a way of describing practically-RESTful APIs in a way that's highly readable by both humans and computers. We say "practically RESTful" because in the real world, very few APIs today actually are. RAML isn't strict: in the end it is only describing HTTP with a few higher-level (optional) constructs. RAML is a non-proprietary, vendor-neutral open spec. The aim is to help our current API ecosystem and solve immediate problems, and then gently encourage ever-better API patterns. \ Links: http://raml.org/about.html https://github.com/raml-org/raml-spec Alan