Registration of media type application/schema+json

[Bjoern Hoehrmann]

* Kris Zyp wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
> 
>Type name:
>
>application
>
>   Subtype name:
>schema+json

As per RFC 4288 http://www.ietf.org/rfc/rfc4288.txt "Registrations in
the standards tree MUST be approved by the IESG and MUST correspond to
a formal publication by a recognized standards body." It seems this is
not the case here. You could, for example, follow the RFC process for
a suitable publication. Alternatively you could place the type into a
different tree, for example, application/vnd.json-schema.schema+json.

Also note that the use of "+type" is controversial, RFC 4288 notes:

  In accordance with the rules specified in [RFC3023], media subtypes
  that do not represent XML entities MUST NOT be given a name that ends
  with the "+xml" suffix.  More generally, "+suffix" constructs should
  be used with care, given the possibility of conflicts with future
  suffix definitions.

At the least, a proposal should include a rationale for using it.

>   Required parameters:
>
>   Optional parameters:
>schema
>schema.items

These lack a proper definition. 

>   Encoding considerations:
>Encoded in application/json format

This should probably refer to the application/json's encoding
considerations then. Generally, the field needs to have one of the
values "7bit", "8bit", "binary", "framed".

I hope this helps,
-- 
Björn Höhrmann · mailto:bjoern at hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/