The resource located at this URI MUST successfully describe itself.
It is RECOMMENDED that schema authors include this keyword in their schemas. We have done this and made this available at this URI: Don’t worry about that URI for now - we will return to Iglu and the proposed path structure in a future blog post.
Implementations SHOULD ignore keywords they do not support. This keyword MUST be located at the root of a JSON Schema.
The value of this keyword MUST be a URI [RFC3986] and a valid JSON Reference [json-reference]; this URI MUST be both absolute and normalized.
You then need a schema registry where you can look up the exact schema definition for a given version number." Kiji uses something we call protocol versioning to get around this issue.
Each record type that we intend to operate on has a field named version which is a string.
An instance is said to be described by one (or more) schema(s). Correlation by means of the "Content-Type" header It is RECOMMENDED that a MIME type parameter by the name of "profile" be appended to the "Content-Type" header of the instance being processed.
The Kiji Table Layout Desc Avro record (what your JSON table layout files interact with) includes a version field which today you should set to "layout-1.1".
In Kiji, a protocol version includes a protocol name and a version number in major.minor.revision format.
If it has not been submitted, skip the validation and display a blank form.
However, in the example above, all input fields are optional.