RAML parser implement more features from the specification

[chriskapp]

Currently the RAML parser understands the most basic functionalities including traits and !include for request and response schemas. But there are some features which are missing from the spec. To be concrete this is:

• Currently !include is only supported for request and response schema definitions. Probably check for it in every value
• Nested resources are currently not supported we can define API paths only on the first level
• Add support for the "schemas" key at the root level which can be referenced in the request and response schema definitions

[chriskapp]

The 1.0.1 release implements the mentioned points