Jason Desrosiers

Recently, we worked on formalizing the process for embedding schemas of different drafts than the parent schema. If the output format is changed, how would output for embedded schemas work?...

Not sure if I should be piling on here or creating another issue, but this seems like a good time to bring up something that bothers me about the output...

> In trying to pare down the list of nodes for the `detailed` and `basic` formats, I found that a lot of nodes were kept that may not be necessary....

> > If we trim the output results to improve one way of consuming the output, we might be limiting what can be done for other ways of consuming output....

> That your scenario requires an ID doesn't imply that every scenario will. The point is that the output format needs to be a common denominator for any application that...

Regarding false schemas ... In my implementation, validation is implemented as just another keyword. It therefore has a node in the validation output just like any other keyword. The top...

I suppose my solution is a middle ground. Every node in the output represents a keyword, but in the case of the pseudo-keyword "validate", the name of the keyword doesn't...

@gregsdennis I was working on something similar a while ago. I can't remember why, but I found trying to mimic the structure of the instance to be problematic. What I...

I don't mean to derail the conversation with my extensions. This was not a proposal. I'm just showing what I've done. Feel free to incorporate as little or as much...

I can see how this could work. It would work similarly to `additionalProperties` in that it would collect the property names declared by `properties` and use that to make its...