Melvin Loos

Any update on this? Would be a valuable improvement for the project I am working on right now.

Ah YAML **extension**, I now understand what you meant with it being on the YAML level in the comments above. Because I could not find it in the YAML spec...

@jstoiko thanks for the mention but as my company switched to swagger we are not currently working on RAML at the moment. I really liked working with RAML so its...

Just ran into this myself, I have been working on implementing this for a project at my work and when I wanted to validate the requests and responses against the...

@AnzeDspot I agree with @alecsammon redoing the entire library looks like a bit too much to me. Also, how much is the 1.0 spec breaking 0.8? As far as I...

Ok great then we are on the same page, just a misunderstanding. As @alecsammon suggested we should commit to a new v3.0 branch and update the documentation that v3.0 branch...

Sorry for the long radio silence. After re-evaluating the RAML type validation I determined that the reusing of the justinrainbow JSON validator wasn't a good enough choice. It seems that...

Hm ok it seems I am not able to create a new branch on the upstream (this) repo. @alecsammon , can you create a v3.0 branch? Then I can send...

@AnzeDspot while awaiting @alecsammon maybe you can already review my current work? [See my fork](https://github.com/InfopactMLoos/php-raml-parser/tree/v3.0). I have updated the README with a quick notice about a work-in-progress 1.0 specification and...

I have written all the validator class code last week, still need to clean up the code a bit before pushing to github. Sadly I have received little feedback on...