Schema's pointing to githubusercontent.com about schemastore

[madskristensen]

The best would be to host them all on schemastore.org so we can control the headers etc. The reason I haven't moved all of them is because I'm not sure where the best source of truth would be for some of these schemas. I have noticed that most projects don't keep their schemas up-to-date, so it might be better just to host them all on schemastore.org. That also gives users the advantage of the test suite we can maintain for them.

Do you want to move the 3 GitHub hosted schemas in with a pull request?

[madskristensen]

Actually, let me remove the Swagger 1.2 API schema reference, since 2.0 is out and taking over. That schema consist of a lot of files, so it will be more problematic to move anyway

[madskristensen]

It seems that both schemas for composer.json and contribute.json are actively maintained on their respective GitHub repos. Perhaps we should proxy the schemas through schemastore.org instead, so they can keep being maintained by their owners, but served correctly through the schemastore.org API

[madskristensen]

What if we download the latest source from the various remote repos in the Grunt build script. That way we host it on schemastore, but we always get the latest and greatest from the source. I'll get on that right now

[rhalff]

Sorry, you've been so fast I had not time to respond :-) Looks like a solid solution to me.