A JSON Schema is a JSON Object that defines various attributes
(including usage and valid values) of a JSON value. JSON
Schema has recursive capabilities; there are a number of elements
in the structure that allow for nested JSON Schemas.
</t>
<figure>
<preamble>An example JSON Schema definition could look like:</preamble>
<artwork>
<![CDATA[
{
"description": "A person",
"type": "object",
"properties": {
"name": {
"type": "string"
},
"age": {
"type": "integer",
"maximum": 125
}
}
}
]]>
</artwork>
</figure>
<t>
A JSON Schema object may have any of the following properties, called schema
attributes (all attributes are optional):
</t>
<sectiontitle="type">
<t>
This attribute defines what the primitive type or the schema of the instance MUST be in order to validate.
This attribute can take one of two forms:
<liststyle="hanging">
<thangText="Simple Types">
A string indicating a primitive or simple type. The following are acceptable string values:
<liststyle="hanging">
<thangText="string">Value MUST be a string.</t>
<thangText="number">Value MUST be a number, floating point numbers are allowed. </t>
<thangText="integer">Value MUST be an integer, no floating point numbers are allowed. This is a subset of the number type.</t>
<thangText="boolean">Value MUST be a boolean. </t>
<thangText="object">Value MUST be an object.</t>
<thangText="array">Value MUST be an array.</t>
<thangText="null">Value MUST be null. Note this is mainly for purpose of being able use union types to define nullability. If this type is not included in a union, null values are not allowed (the primitives listed above do not allow nulls on their own).</t>
<thangText="any">Value MAY be of any type including null.</t>
</list>
If the property is not defined or is not in this list, then any type of value is acceptable.
Other type values MAY be used for custom purposes, but minimal validators of the specification
implementation can allow any instance value on unknown type values.
</t>
<thangText="Union Types">
An array of two or more simple type definitions. Each item in the array MUST be a simple type definition or a schema.
The instance value is valid if it is of the same type as one of the simple type definitions, or valid by one of the schemas, in the array.
</t>
</list>
</t>
<figure>
<preamble>For example, a schema that defines if an instance can be a string or a number would be:</preamble>
<artwork>
<![CDATA[
{
"type": ["string", "number"]
}
]]></artwork>
</figure>
</section>
<sectiontitle="properties"anchor="properties">
<t>This attribute is an object with property definitions that define the valid values of instance object property values. When the instance value is an object, the property values of the instance object MUST conform to the property definitions in this object. In this object, each property definition's value MUST be a schema, and the property's name MUST be the name of the instance property that it defines. The instance property value MUST be valid according to the schema from the property definition. Properties are considered unordered, the order of the instance properties MAY be in any order.</t>
</section>
<sectiontitle="patternProperties">
<t>This attribute is an object that defines the schema for a set of property names of an object instance. The name of each property of this attribute's object is a regular expression pattern in the ECMA 262/Perl 5 format, while the value is a schema. If the pattern matches the name of a property on the instance object, the value of the instance's property MUST be valid against the pattern name's schema value.</t>
<t>This attribute defines a schema for all properties that are not explicitly defined in an object type definition. If specified, the value MUST be a schema or a boolean. If false is provided, no additional properties are allowed beyond the properties defined in the schema. The default value is an empty schema which allows any value for additional properties.</t>
</section>
<sectiontitle="items">
<t>This attribute defines the allowed items in an instance array, and MUST be a schema or an array of schemas. The default value is an empty schema which allows any value for items in the instance array.</t>
<t>When this attribute value is a schema and the instance value is an array, then all the items in the array MUST be valid according to the schema.</t>
<t>When this attribute value is an array of schemas and the instance value is an array, each position in the instance array MUST conform to the schema in the corresponding position for this array. This called tuple typing. When tuple typing is used, additional items are allowed, disallowed, or constrained by the <xreftarget="additionalItems">"additionalItems"</xref> attribute using the same rules as <xreftarget="additionalProperties">"additionalProperties"</xref> for objects.</t>
<t>This provides a definition for additional items in an array instance when tuple definitions of the items is provided. This can be false to indicate additional items in the array are not allowed, or it can be a schema that defines the schema of the additional items.</t>
</section>
<sectiontitle="required">
<t>This attribute indicates if the instance must have a value, and not be undefined. This is false by default, making the instance optional.</t>
</section>
<sectiontitle="dependencies">
<t>This attribute is an object that defines the requirements of a property on an instance object. If an object instance has a property with the same name as a property in this attribute's object, then the instance must be valid against the attribute's property value (hereafter referred to as the "dependency value").</t>
<t>
The dependency value can take one of two forms:
<liststyle="hanging">
<thangText="Simple Dependency">
If the dependency value is a string, then the instance object MUST have a property with the same name as the dependency value.
If the dependency value is an array of strings, then the instance object MUST have a property with the same name as each string in the dependency value's array.
</t>
<thangText="Schema Dependency">
If the dependency value is a schema, then the instance object MUST be valid against the schema.
</t>
</list>
</t>
</section>
<sectiontitle="minimum">
<t>This attribute defines the minimum value of the instance property when the type of the instance value is a number.</t>
</section>
<sectiontitle="maximum">
<t>This attribute defines the maximum value of the instance property when the type of the instance value is a number.</t>
</section>
<sectiontitle="exclusiveMinimum">
<t>This attribute indicates if the value of the instance (if the instance is a number) can not equal the number defined by the "minimum" attribute. This is false by default, meaning the instance value can be greater then or equal to the minimum value.</t>
</section>
<sectiontitle="exclusiveMaximum">
<t>This attribute indicates if the value of the instance (if the instance is a number) can not equal the number defined by the "maximum" attribute. This is false by default, meaning the instance value can be less then or equal to the maximum value.</t>
</section>
<sectiontitle="minItems">
<t>This attribute defines the minimum number of values in an array when the array is the instance value.</t>
</section>
<sectiontitle="maxItems">
<t>This attribute defines the maximum number of values in an array when the array is the instance value.</t>
</section>
<sectiontitle="uniqueItems"anchor="uniqueItems">
<t>This attribute indicates that all items in an array instance MUST be unique (contains no two identical values).</t>
<t>
Two instance are consider equal if they are both of the same type and:
<list>
<t>are null; or</t>
<t>are booleans/numbers/strings and have the same value; or</t>
<t>are arrays, contains the same number of items, and each item in the array is equal to the corresponding item in the other array; or</t>
<t>are objects, contains the same property names, and each property in the object is equal to the corresponding property in the other object.</t>
</list>
</t>
</section>
<sectiontitle="pattern">
<t>When the instance value is a string, this provides a regular expression that a string instance MUST match in order to be valid. Regular expressions SHOULD follow the regular expression specification from ECMA 262/Perl 5</t>
</section>
<sectiontitle="minLength">
<t>When the instance value is a string, this defines the minimum length of the string.</t>
</section>
<sectiontitle="maxLength">
<t>When the instance value is a string, this defines the maximum length of the string.</t>
</section>
<sectiontitle="enum">
<t>This provides an enumeration of all possible values that are valid for the instance property. This MUST be an array, and each item in the array represents a possible value for the instance value. If this attribute is defined, the instance value MUST be one of the values in the array in order for the schema to be valid. Comparison of enum values uses the same algorithm as defined in <xreftarget="uniqueItems">"uniqueItems"</xref>.</t>
</section>
<sectiontitle="default">
<t>This attribute defines the default value of the instance when the instance is undefined.</t>
</section>
<sectiontitle="title">
<t>This attribute is a string that provides a short description of the instance property.</t>
</section>
<sectiontitle="description">
<t>This attribute is a string that provides a full description of the of purpose the instance property.</t>
</section>
<sectiontitle="format">
<t>This property defines the type of data, content type, or microformat to be expected in the instance property values. A format attribute MAY be one of the values listed below, and if so, SHOULD adhere to the semantics describing for the format. A format SHOULD only be used to give meaning to primitive types (string, integer, number, or boolean). Validators MAY (but are not required to) validate that the instance values conform to a format.</t>
<t>
The following formats are predefined:
<liststyle="hanging">
<thangText="date-time">This SHOULD be a date in ISO 8601 format of YYYY-MM-DDThh:mm:ssZ in UTC time. This is the recommended form of date/timestamp.</t>
<thangText="date">This SHOULD be a date in the format of YYYY-MM-DD. It is recommended that you use the "date-time" format instead of "date" unless you need to transfer only the date part.</t>
<thangText="time">This SHOULD be a time in the format of hh:mm:ss. It is recommended that you use the "date-time" format instead of "time" unless you need to transfer only the time part.</t>
<thangText="utc-millisec">This SHOULD be the difference, measured in milliseconds, between the specified time and midnight, 00:00 of January 1, 1970 UTC. The value SHOULD be a number (integer or float).</t>
<thangText="regex">A regular expression, following the regular expression specification from ECMA 262/Perl 5.</t>
<thangText="color">This is a CSS color (like "#FF0000" or "red"), based on <xreftarget="W3C.CR-CSS21-20070719">CSS 2.1</xref>.</t>
<thangText="style">This is a CSS style definition (like "color: red; background-color:#FFF"), based on <xreftarget="W3C.CR-CSS21-20070719">CSS 2.1</xref>.</t>
<thangText="phone">This SHOULD be a phone number (format MAY follow E.123).</t>
<thangText="uri">This value SHOULD be a URI.</t>
<thangText="email">This SHOULD be an email address.</t>
<thangText="ip-address">This SHOULD be an ip version 4 address.</t>
<thangText="ipv6">This SHOULD be an ip version 6 address.</t>
<thangText="host-name">This SHOULD be a host-name.</t>
</list>
</t>
<t>Additional custom formats MAY be created. These custom formats MAY be expressed as an URI, and this URI MAY reference a schema of that format.</t>
</section>
<sectiontitle="divisibleBy">
<t>This attribute defines what value the number instance must be divisible by with no remainder (the result of the division must be an integer.) The value of this attribute SHOULD NOT be 0.</t>
</section>
<sectiontitle="disallow">
<t>This attribute takes the same values as the "type" attribute, however if the instance matches the type or if this value is an array and the instance matches any type or schema in the array, then this instance is not valid.</t>
</section>
<sectiontitle="extends">
<t>The value of this property MUST be another schema which will provide a base schema which the current schema will inherit from. The inheritance rules are such that any instance that is valid according to the current schema MUST be valid according to the referenced schema. This MAY also be an array, in which case, the instance MUST be valid for all the schemas in the array. A schema that extends another schema MAY define additional attributes, constrain existing attributes, or add other constraints.</t>
<t>
Conceptually, the behavior of extends can be seen as validating an
instance against all constraints in the extending schema as well as
the extended schema(s). More optimized implementations that merge
schemas are possible, but are not required. Some examples of using "extends":
This attribute defines the current URI of this schema (this attribute is
effectively a "self" link). This URI MAY be relative or absolute. If
the URI is relative it is resolved against the current URI of the parent
schema it is contained in. If this schema is not contained in any
parent schema, the current URI of the parent schema is held to be the
URI under which this schema was addressed. If id is missing, the current URI of a schema is
defined to be that of the parent schema. The current URI of the schema
is also used to construct relative references such as for $ref.
</t>
</section>
<sectiontitle="$ref">
<t>
This attribute defines a URI of a schema that contains the full representation of this schema.
When a validator encounters this attribute, it SHOULD replace the current schema with the schema referenced by the value's URI (if known and available) and re-validate the instance.
This URI MAY be relative or absolute, and relative URIs SHOULD be resolved against the URI of the current schema.
</t>
</section>
<sectiontitle="$schema">
<t>
This attribute defines a URI of a JSON Schema that is the schema of the current schema.
When this attribute is defined, a validator SHOULD use the schema referenced by the value's URI (if known and available) when resolving <xreftarget="hyper-schema">Hyper Schema</xref><xreftarget="links">links</xref>.
</t>
<t>
A validator MAY use this attribute's value to determine which version of JSON Schema the current schema is written in, and provide the appropriate validation features and behavior.
Therefore, it is RECOMMENDED that all schema authors include this attribute in their schemas to prevent conflicts with future JSON Schema specification changes.
indicates the target URI of the related resource. The value
of the instance property SHOULD be resolved as a URI-Reference per <xreftarget="RFC3986">RFC 3986</xref>
and MAY be a relative URI. The base URI to be used for relative resolution
SHOULD be the URI used to retrieve the instance object (not the schema)
when used within a schema. Also, when links are used within a schema, the URI
SHOULD be parametrized by the property values of the instance
object, if property values exist for the corresponding variables
in the template (otherwise they MAY be provided from alternate sources, like user input).
</t>
<t>
Instance property values SHOULD be substituted into the URIs where
matching braces ('{', '}') are found surrounding zero or more characters,
creating an expanded URI. Instance property value substitutions are resolved
by using the text between the braces to denote the property name
from the instance to get the value to substitute.
<figure>
<preamble>For example, if an href value is defined:</preamble>
<artwork>
<![CDATA[
http://somesite.com/{id}
]]>
</artwork>
<postamble>Then it would be resolved by replace the value of the "id" property value from the instance object.</postamble>
</figure>
<figure>
<preamble>If the value of the "id" property was "45", the expanded URI would be:</preamble>
<artwork>
<![CDATA[
http://somesite.com/45
]]>
</artwork>
</figure>
If matching braces are found with the string "@" (no quotes) between the braces, then the
actual instance value SHOULD be used to replace the braces, rather than a property value.
This should only be used in situations where the instance is a scalar (string,
boolean, or number), and not for objects or arrays.
</t>
</section>
<sectiontitle="rel">
<t>
The value of the "rel" property indicates the name of the
relation to the target resource. The relation to the target SHOULD be interpreted as specifically from the instance object that the schema (or sub-schema) applies to, not just the top level resource that contains the object within its hierarchy. If a resource JSON representation contains a sub object with a property interpreted as a link, that sub-object holds the relation with the target. A relation to target from the top level resource MUST be indicated with the schema describing the top level JSON representation.
</t>
<t>
Relationship definitions SHOULD NOT be media type dependent, and users are encouraged to utilize existing accepted relation definitions, including those in existing relation registries (see <xreftarget="RFC4287">RFC 4287</xref>). However, we define these relations here for clarity of normative interpretation within the context of JSON hyper schema defined relations:
<liststyle="hanging">
<thangText="self">
If the relation value is "self", when this property is encountered in
the instance object, the object represents a resource and the instance object is
treated as a full representation of the target resource identified by
the specified URI.
</t>
<thangText="full">
This indicates that the target of the link is the full representation for the instance object. The object that contains this link possibly may not be the full representation.
</t>
<thangText="describedby">
This indicates the target of the link is the schema for the instance object. This MAY be used to specifically denote the schemas of objects within a JSON object hierarchy, facilitating polymorphic type data structures.
</t>
<thangText="root">
This relation indicates that the target of the link
SHOULD be treated as the root or the body of the representation for the
purposes of user agent interaction or fragment resolution. All other
properties of the instance objects can be regarded as meta-data
descriptions for the data.
</t>
</list>
</t>
<t>
The following relations are applicable for schemas (the schema as the "from" resource in the relation):
<liststyle="hanging">
<thangText="instances">This indicates the target resource that represents collection of instances of a schema.</t>
<thangText="create">This indicates a target to use for creating new instances of a schema. This link definition SHOULD be a submission link with a non-safe method (like POST).</t>
</list>
</t>
<t>
<figure>
<preamble>For example, if a schema is defined:</preamble>
<artwork>
<![CDATA[
{
"links": [{
"rel": "self",
"href": "{id}"
}, {
"rel": "up",
"href": "{upId}"
}, {
"rel": "children",
"href": "?upId={id}"
}]
}
]]>
</artwork>
</figure>
<figure>
<preamble>And if a collection of instance resource's JSON representation was retrieved:</preamble>
<artwork>
<![CDATA[
GET /Resource/
[{
"id": "thing",
"upId": "parent"
}, {
"id": "thing2",
"upId": "parent"
}]
]]>
</artwork>
</figure>
This would indicate that for the first item in the collection, its own
(self) URI would resolve to "/Resource/thing" and the first item's "up"
relation SHOULD be resolved to the resource at "/Resource/parent".
The "children" collection would be located at "/Resource/?upId=thing".
</t>
</section>
<sectiontitle="targetSchema">
<t>This property value is a schema that defines the expected structure of the JSON representation of the target of the link.</t>
</section>
<sectiontitle="Submission Link Properties">
<t>
The following properties also apply to link definition objects, and
provide functionality analogous to HTML forms, in providing a
means for submitting extra (often user supplied) information to send to a server.
</t>
<sectiontitle="method">
<t>
This attribute defines which method can be used to access the target resource.
In an HTTP environment, this would be "GET" or "POST" (other HTTP methods
such as "PUT" and "DELETE" have semantics that are clearly implied by
accessed resources, and do not need to be defined here).
This defaults to "GET".
</t>
</section>
<sectiontitle="enctype">
<t>
If present, this property indicates a query media type format that the server
supports for querying or posting to the collection of instances at the target
resource. The query can be
suffixed to the target URI to query the collection with
property-based constraints on the resources that SHOULD be returned from
the server or used to post data to the resource (depending on the method).
<figure>
<preamble>For example, with the following schema:</preamble>
<artwork>
<![CDATA[
{
"links": [{
"enctype": "application/x-www-form-urlencoded",
"method": "GET",
"href": "/Product/",
"properties": {
"name": {
"description": "name of the product"
}
}
}]
}
]]>
</artwork>
<postamble>This indicates that the client can query the server for instances that have a specific name.</postamble>
</figure>
<figure>
<preamble>For example:</preamble>
<artwork>
<![CDATA[
/Product/?name=Slinky
]]>
</artwork>
</figure>
If no enctype or method is specified, only the single URI specified by
the href property is defined. If the method is POST, "application/json" is
the default media type.
</t>
</section>
<sectiontitle="schema">
<t>
This attribute contains a schema which defines the acceptable structure of the submitted
request (for a GET request, this schema would define the properties for the query string
and for a POST request, this would define the body).
</t>
</section>
</section>
</section>
</section>
<sectiontitle="fragmentResolution">
<t>
This property indicates the fragment resolution protocol to use for
resolving fragment identifiers in URIs within the instance
representations. This applies to the instance object URIs and all
children of the instance object's URIs. The default fragment resolution
protocol is "slash-delimited", which is defined below. Other fragment
resolution protocols MAY be used, but are not defined in this document.
</t>
<t>
The fragment identifier is based on <xreftarget="RFC2396">RFC 2396, Sec 5</xref>, and defines the
mechanism for resolving references to entities within a document.
</t>
<sectiontitle="slash-delimited fragment resolution">
<t>
With the slash-delimited fragment resolution protocol, the fragment
identifier is interpreted as a series of property reference tokens that start with and
are delimited by the "/" character (\x2F). Each property reference token
is a series of unreserved or escaped URI characters. Each property
reference token SHOULD be interpreted, starting from the beginning of
the fragment identifier, as a path reference in the target JSON
structure. The final target value of the fragment can be determined by
starting with the root of the JSON structure from the representation of
the resource identified by the pre-fragment URI. If the target is a JSON
object, then the new target is the value of the property with the name
identified by the next property reference token in the fragment. If the
target is a JSON array, then the target is determined by finding the
item in array the array with the index defined by the next property
reference token (which MUST be a number). The target is successively
updated for each property reference token, until the entire fragment has
been traversed.
</t>
<t>
Property names SHOULD be URI-encoded. In particular, any "/" in a
property name MUST be encoded to avoid being interpreted as a property
delimiter.
</t>
<t>
<figure>
<preamble>For example, for the following JSON representation:</preamble>
<artwork>
<![CDATA[
{
"foo": {
"anArray": [{
"prop": 44
}],
"another prop": {
"baz": "A string"
}
}
}
]]>
</artwork>
</figure>
<figure>
<preamble>The following fragment identifiers would be resolved:</preamble>
<artwork>
<![CDATA[
fragment identifier resolution
------------------- ----------
# self, the root of the resource itself
#/foo the object referred to by the foo property
#/foo/another%20prop the object referred to by the "another prop"
property of the object referred to by the
"foo" property
#/foo/another%20prop/baz the string referred to by the value of "baz"
property of the "another prop" property of
the object referred to by the "foo" property
#/foo/anArray/0 the first object in the "anArray" array
]]>
</artwork>
</figure>
</t>
</section>
<sectiontitle="dot-delimited fragment resolution">
<t>
The dot-delimited fragment resolution protocol is the same as
slash-delimited fragment resolution protocol except that the "." character
(\x2E) is used as the delimiter between property names (instead of "/") and
the path does not need to start with a ".". For example, #.foo and #foo are a valid fragment
identifiers for referencing the value of the foo propery.
</t>
</section>
</section>
<sectiontitle="readonly">
<t>This attribute indicates that the instance property SHOULD NOT be changed. Attempts by a user agent to modify the value of this property are expected to be rejected by a server.</t>
</section>
<sectiontitle="contentEncoding">
<t>If the instance property value is a string, this attribute defines that the string SHOULD be interpreted as binary data and decoded using the encoding named by this schema property. <xreftarget="RFC2045">RFC 2045, Sec 6.1</xref> lists the possible values for this property.</t>
</section>
<sectiontitle="pathStart">
<t>
This attribute is a URI that defines what the instance's URI MUST start with in order to validate.
The value of the "pathStart" attribute MUST be resolved as per <xreftarget="RFC3986">RFC 3986, Sec 5</xref>,
and is relative to the instance's URI.
</t>
<t>
When multiple schemas have been referenced for an instance, the user agent
can determine if this schema is applicable for a particular instance by
determining if the URI of the instance begins with the the value of the "pathStart"
attribute. If the URI of the instance does not start with this URI,
or if another schema specifies a starting URI that is longer and also matches the
instance, this schema SHOULD NOT be applied to the instance. Any schema
that does not have a pathStart attribute SHOULD be considered applicable
to all the instances for which it is referenced.
</t>
</section>
<sectiontitle="mediaType">
<t>This attribute defines the media type of the instance representations that this schema is defining.</t>
</section>
</section>
<sectiontitle="Security Considerations">
<t>
This specification is a sub-type of the JSON format, and
consequently the security considerations are generally the same as <xreftarget="RFC4627">RFC 4627</xref>.
However, an additional issue is that when link relation of "self"
is used to denote a full representation of an object, the user agent
SHOULD NOT consider the representation to be the authoritative representation
of the resource denoted by the target URI if the target URI is not
equivalent to or a sub-path of the the URI used to request the resource
representation which contains the target URI with the "self" link.
<figure>
<preamble>For example, if a hyper schema was defined:</preamble>
<artwork>
<![CDATA[
{
"links": [{
"rel": "self",
"href": "{id}"
}]
}
]]>
</artwork>
</figure>
<figure>
<preamble>And a resource was requested from somesite.com:</preamble>
"name": "This representation can be safely treated \
as authoritative "
}, {
"id": "/baz",
"name": "This representation should not be treated as \
authoritative the user agent should make request the resource\
from '/baz' to ensure it has the authoritative representation"
}, {
"id": "http://othersite.com/something",
"name": "This representation\
should also not be treated as authoritative and the target\
resource representation should be retrieved for the\
authoritative representation"
}]
]]>
</artwork>
</figure>
</t>
</section>
<sectiontitle="IANA Considerations">
<t>The proposed MIME media type for JSON Schema is "application/schema+json".</t>
<t>Type name: application</t>
<t>Subtype name: schema+json</t>
<t>Required parameters: profile</t>
<t>
The value of the profile parameter SHOULD be a URI (relative or absolute) that
refers to the schema used to define the structure of this structure (the
meta-schema). Normally the value would be http://json-schema.org/draft-03/hyper-schema,
but it is allowable to use other schemas that extend the hyper schema's meta-
schema.
</t>
<t>Optional parameters: pretty</t>
<t>The value of the pretty parameter MAY be true or false to indicate if additional whitespace has been included to make the JSON representation easier to read.</t>
<sectiontitle="Registry of Link Relations">
<t>
This registry is maintained by IANA per <xreftarget="RFC4287">RFC 4287</xref> and this specification adds
four values: "full", "create", "instances", "root". New
assignments are subject to IESG Approval, as outlined in <xreftarget="RFC5226">RFC 5226</xref>.
Requests should be made by email to IANA, which will then forward the
request to the IESG, requesting approval.
</t>
</section>
</section>
</middle>
<back>
<!-- References Section -->
<referencestitle="Normative References">
&rfc2045;
&rfc2119;
&rfc2396;
&rfc3339;
&rfc3986;
&rfc4287;
</references>
<referencestitle="Informative References">
&rfc2616;
&rfc4627;
&rfc5226;
&iddiscovery;
&uritemplate;
&linkheader;
&html401;
&css21;
</references>
<sectiontitle="Change Log">
<t>
<liststyle="hanging">
<thangText="draft-03">
<liststyle="symbols">
<t>Added example and verbiage to "extends" attribute.</t>
<t>Defined slash-delimited to use a leading slash.</t>
<t>Made "root" a relation instead of an attribute.</t>
<t>Removed address values, and MIME media type from format to reduce confusion (mediaType already exists, so it can be used for MIME types).</t>
<t>Added more explanation of nullability.</t>
<t>Removed "alternate" attribute.</t>
<t>Upper cased many normative usages of must, may, and should.</t>
<t>Replaced the link submission "properties" attribute to "schema" attribute.</t>
<t>Replaced "optional" attribute with "required" attribute.</t>
<t>Replaced "maximumCanEqual" attribute with "exclusiveMaximum" attribute.</t>
<t>Replaced "minimumCanEqual" attribute with "exclusiveMinimum" attribute.</t>
<t>Replaced "requires" attribute with "dependencies" attribute.</t>
<t>Moved "contentEncoding" attribute to hyper schema.</t>
<t>Added "additionalItems" attribute.</t>
<t>Added "id" attribute.</t>
<t>Switched self-referencing variable substitution from "-this" to "@" to align with reserved characters in URI template.</t>
<t>Added "patternProperties" attribute.</t>
<t>Schema URIs are now namespace versioned.</t>
<t>Added "$ref" and "$schema" attributes.</t>
</list>
</t>
<thangText="draft-02">
<liststyle="symbols">
<t>Replaced "maxDecimal" attribute with "divisibleBy" attribute.</t>
<t>Added slash-delimited fragment resolution protocol and made it the default.</t>
<t>Added language about using links outside of schemas by referencing its normative URI.</t>
<t>Added "uniqueItems" attribute.</t>
<t>Added "targetSchema" attribute to link description object.</t>
</list>
</t>
<thangText="draft-01">
<liststyle="symbols">
<t>Fixed category and updates from template.</t>
</list>
</t>
<thangText="draft-00">
<liststyle="symbols">
<t>Initial draft.</t>
</list>
</t>
</list>
</t>
</section>
<sectiontitle="Open Issues">
<t>
<list>
<t>Should we give a preference to MIME headers over Link headers (or only use one)?</t>
<t>Should "root" be a MIME parameter?</t>
<t>Should "format" be renamed to "mediaType" or "contentType" to reflect the usage MIME media types that are allowed?</t>
