Hey Nick, Thanks for the patch. The way you did things all makes sense to me and I like the idea of pulling out the definitions to make things more compact in the main schema, the one thought I did have though was that it isn't immediately obvious in the main schema where these values are coming from. Because they just reference a $defs key that doesn't exist in this file, there is no reference to something like "hey, go look here for the definitions." Unfortunately, because it's JSON, you also can't just leave a comment, so I guess the best we can do is just make sure to document it well. I wonder if there is a way though that you can have the paths for the references reference other files. I'm sure you would have looked into that already, but that probably would fix the confusion problem, and it stops you from having to recombine manually.
<snip>
