Let's get JSON Schema registered with IANA

[cjaccino]

JSON Schema is important and useful today, yet a formal RFC seems like a long way off. It would benefit the community and boost legitimacy and awareness to have JSON Schema registered now.

The IETF's HTTP API working group now tracks a draft for YAML and OpenAPI spec registration. By the name, it's about REST APIs, and I think JSON Schema falls within that scope. YAML and Openapi non-IETF formats that deserve a media type. Would we consider either a similar, separate registration or adding JSON Schema to that document?

While we're at it, should we consider YAML as a viable format for JSON Schema? If so, do we need application/json-schema+yaml or similar?

That draft provides the following. Being able to formally use +yaml creates a dependency on that spec making it to RFC.

It provides:

• text/yaml
• application/yaml
• application/openapi+json
• application/openapi+yaml
• +yaml as a structured syntax suffix

If JSON Schema were to contribute these, I think the two efforts will have opened the door to much greater cohesion in the API tooling interoperability space, even as JSON Schema continues to evolve.

• application/schema+json
• application/schema-instance+json
• application/json-schema+yaml
• application/json-schema-instance+yaml <- would this be necessary for YAML if YAML supports JSON Pointer fragment styles in its registration?

Thanks!

[cjaccino]

@jdesrosiers it looks like you're way ahead of this. You've already submitted a pull request! Thank you. I'll take the application/json-schema+yaml to the other project.