Christian Heidenreich

Hi. This seems to look like a very cool project. Are you still working on it?

Use tables and links to specific section instead of text only

2

Currently, the spec has tables, text, and only few links. We want to improve the content by introducing a better table structure that basically contains the key name of a...

In the current version of the specification, the value of a `baseUri` node is described as follows: > The value of the baseUri node is a string that MUST conform...

Is the following a valid "baseUri"

4

Currently, the spec defines that the value of the `baseUri` node need to conform the RFC2396 specification (see [this issue](https://github.com/raml-org/raml-spec/issues/644) for updating it to RFC3986). Both specs RFC2396(old) and RFC3986(new)...

Question for validating union types

3

Assume we have the following type definitions: ```yaml types: EventType: type: object properties: eventTypeId: type: string eventTypeName: type: string eventTypeCategory: enum: [alert,notification,business,device,status] TemperatureSensorEvent: type: EventType properties: temperature: number unit: enum:...

Currently the spec states: --- There are only a few restrictions: - Validation of any XML or JSON instance against inner elements follows the same restrictions as the validation against...

At the moment, the specification is not clear about if you can leave the value of the `enum` facet completely empty or if it is allowed to define it as...

Would be nice to execute the converter from your CLI :)

I'd like to ask the mocking service which RAML document it currently mocks. It should use the mechanism described [here](https://github.com/raml-org/raml-spec/issues/556). One example of HTTP response for a hypothetical HTTP request:...

 As you can see in the image above; I am getting auto-completion inside a JSON schema type definition. Can we prevent that. It's kinda annoying since its comes out...