RAML 1.0 does not support repeatable keys

[sichvoge]

The example starting with line 102 is not correct as RAML does not support any repeatable keys. So there should be only one possible get.

[nogates]

Thanks for opening this issue @sichvoge.

Question related to this. What would it happen if instead of using an object to describe the methods, the resource defines an array? Like this:

/:
 - get: 
    200: 
      # rest of the first response
 - get: 
    200: 
      # rest of the second response

In this case, yaml would build an array of methods and the keys wouldn't be overridden. Still, I think this is not correct because using an array would mean that the resource object can't have no properties, only methods.

[sichvoge]

I would not prefer that, and maybe that is a discussion for #raml-org/raml-spec repo. IMHO, HTTP methods should be defined uniquely to remove anything that can be ambiguous around your API.