Skip to content

handrews-*-01 bugfix for core & validation #555

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Mar 14, 2018
Merged

handrews-*-01 bugfix for core & validation #555

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
539187b
Add : to hanging list lables w short bodies
handrews Nov 28, 2017
066204c
Update "dependencies" CREF
handrews Mar 3, 2018
53b28fc
handrews-*-01 for core and validation, add commit log
handrews Mar 3, 2018
db67952
Fix error in older changelog
handrews Mar 4, 2018
f76226d
Crosslink annotations to implementation guidance.
handrews Mar 4, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
39 changes: 25 additions & 14 deletions jsonschema-core.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@
<?rfc rfcedstyle="yes"?>
<?rfc comments="yes"?>
<?rfc inline="yes" ?>
<rfc category="info" docName="draft-handrews-json-schema-00" ipr="trust200902">
<rfc category="info" docName="draft-handrews-json-schema-01" ipr="trust200902">
<front>
<title abbrev="JSON Schema">JSON Schema: A Media Type for Describing JSON Documents</title>

Expand Down Expand Up @@ -185,12 +185,12 @@
depending on the type:

<list style="hanging">
<t hangText="null">A JSON "null" production</t>
<t hangText="boolean">A "true" or "false" value, from the JSON "true" or "false" productions</t>
<t hangText="object">An unordered set of properties mapping a string to an instance, from the JSON "object" production</t>
<t hangText="array">An ordered list of instances, from the JSON "array" production</t>
<t hangText="number">An arbitrary-precision, base-10 decimal number value, from the JSON "number" production</t>
<t hangText="string">A string of Unicode code points, from the JSON "string" production</t>
<t hangText="null:">A JSON "null" production</t>
<t hangText="boolean:">A "true" or "false" value, from the JSON "true" or "false" productions</t>
<t hangText="object:">An unordered set of properties mapping a string to an instance, from the JSON "object" production</t>
<t hangText="array:">An ordered list of instances, from the JSON "array" production</t>
<t hangText="number:">An arbitrary-precision, base-10 decimal number value, from the JSON "number" production</t>
<t hangText="string:">A string of Unicode code points, from the JSON "string" production</t>
</list>
</t>
<t>
Expand Down Expand Up @@ -284,10 +284,10 @@
or schema keywords. Broadly speaking, keywords fall into one or both
of two categories:
<list style="hanging">
<t hangText="assertions">
<t hangText="assertions:">
produce a boolean result when applied to an instance
</t>
<t hangText="annotations">
<t hangText="annotations:">
attach information to an instance for application use
</t>
</list>
Expand All @@ -303,10 +303,10 @@
in terms of the validation vocabulary, boolean schemas are equivalent to
the following behaviors:
<list style="hanging">
<t hangText="true">
<t hangText="true:">
Always passes validation, as if the empty schema {}
</t>
<t hangText="false">
<t hangText="false:">
Always fails validation, as if the schema { "not":{} }
</t>
</list>
Expand Down Expand Up @@ -1045,7 +1045,7 @@ User-Agent: product-name/5.4.1 so-cool-json-schema/1.0.2 curl/7.43.0
<t>
Required parameters:
<list style="hanging">
<t hangText="schema">
<t hangText="schema:">
A non-empty list of space-separated URIs, each identifying
a JSON Schema resource. The instance SHOULD successfully
validate against at least one of these schemas.
Expand Down Expand Up @@ -1110,7 +1110,7 @@ User-Agent: product-name/5.4.1 so-cool-json-schema/1.0.2 curl/7.43.0
</author>
<date year="2017" month="November"/>
</front>
<seriesInfo name="Internet-Draft" value="draft-handrews-json-schema-validation-00" />
<seriesInfo name="Internet-Draft" value="draft-handrews-json-schema-validation-01" />
</reference>
<reference anchor="json-hyper-schema">
<front>
Expand All @@ -1123,7 +1123,7 @@ User-Agent: product-name/5.4.1 so-cool-json-schema/1.0.2 curl/7.43.0
</author>
<date year="2017" month="November"/>
</front>
<seriesInfo name="Internet-Draft" value="draft-handrews-json-schema-hyperschema-00" />
<seriesInfo name="Internet-Draft" value="draft-handrews-json-schema-hyperschema-01" />
</reference>
</references>

Expand Down Expand Up @@ -1157,6 +1157,17 @@ User-Agent: product-name/5.4.1 so-cool-json-schema/1.0.2 curl/7.43.0
</t>
<t>
<list style="hanging">
<t hangText="draft-handrews-json-schema-01">
<list style="symbols">
<t>This draft is purely a clarification with no functional changes</t>
<t>Clarified $id by use cases</t>
<t>Exhaustive schema identification examples</t>
<t>Replaced "external referencing" with how and when an implementation might know of a schema from another doucment</t>
<t>Replaced "internal referencing" with how an implementation should recognized schema identifiers during parsing</t>
<t>Dereferencing the former "internal" or "external" references is always the same process</t>
<t>Minor formatting improvements</t>
</list>
</t>
<t hangText="draft-handrews-json-schema-00">
<list style="symbols">
<t>Make the concept of a schema keyword vocabulary more clear</t>
Expand Down
66 changes: 37 additions & 29 deletions jsonschema-validation.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@
<?rfc rfcedstyle="yes"?>
<?rfc comments="yes"?>
<?rfc inline="yes" ?>
<rfc category="info" docName="draft-handrews-json-schema-validation-00" ipr="trust200902">
<rfc category="info" docName="draft-handrews-json-schema-validation-01" ipr="trust200902">
<front>
<title abbrev="JSON Schema Validation">
JSON Schema Validation: A Vocabulary for Structural Validation of JSON
Expand Down Expand Up @@ -686,14 +686,14 @@
<section title="dependencies">
<t>
<cref>
Now that "if", "then", and "else" are keywords, it is not clear whether
there is any benefit in keeping the schema form of "dependencies".
It is frequently misunderstood, and having a form that takes a subschema
as well as a form that takes a primitive value is particularly
confusing. And it seems to be rarely used. Depending on feedback
with "if", "then", and "else", the schema form of this keyword may
well be removed in a future draft. Current thought is that the string
form (giving property names in an array) is a useful shortcut.
This keyword may be split into two, with the variation that uses
an array of property names rather than a subschema getting a new
name. The dual behavior is confusing and relatively difficult to
implement. In the previous draft, we proposed dropping the keyword
altogether, or dropping one of its forms, but we received feedback
in support of keeping it. See issues #442 and #528 at
&lt;https://github.com/json-schema-org/json-schema-spec/issues&gt;
for further discussion. Further feedback is encouraged.
</cref>
</t>
<t>
Expand Down Expand Up @@ -912,15 +912,15 @@
Implementations supporting formats SHOULD implement support for
the following attributes:
<list style="hanging">
<t hangText="date-time">
<t hangText="date-time:">
A string instance is valid against this attribute if it is
a valid representation according to the "date-time" production.
</t>
<t hangText="date">
<t hangText="date:">
A string instance is valid against this attribute if it is
a valid representation according to the "full-date" production.
</t>
<t hangText="time">
<t hangText="time:">
A string instance is valid against this attribute if it is
a valid representation according to the "full-time" production.
</t>
Expand Down Expand Up @@ -953,10 +953,10 @@
A string instance is valid against these attributes if it is a valid
Internet email address as follows:
<list style="hanging">
<t hangText="email">
<t hangText="email:">
As defined by <xref target="RFC5322">RFC 5322, section 3.4.1</xref>.
</t>
<t hangText="idn-email">
<t hangText="idn-email:">
As defined by <xref target="RFC6531">RFC 6531</xref>
</t>
</list>
Expand All @@ -972,12 +972,12 @@
A string instance is valid against these attributes if it is a valid
representation for an Internet hostname as follows:
<list style="hanging">
<t hangText="hostname">
<t hangText="hostname:">
As defined by <xref target="RFC1034">RFC 1034, section 3.1</xref>,
including host names produced using the Punycode algorithm
specified in <xref target="RFC5891">RFC 5891, section 4.4</xref>.
</t>
<t hangText="idn-hostname">
<t hangText="idn-hostname:">
As defined by either RFC 1034 as for hostname, or an
internationalized hostname as defined by
<xref target="RFC5890">RFC 5890, section 2.3.2.3</xref>.
Expand All @@ -996,12 +996,12 @@
A string instance is valid against these attributes if it is a valid
representation of an IP address as follows:
<list style="hanging">
<t hangText="ipv4">
<t hangText="ipv4:">
An IPv4 address according to the "dotted-quad" ABNF
syntax as defined in
<xref target="RFC2673">RFC 2673, section 3.2</xref>.
</t>
<t hangText="ipv6">
<t hangText="ipv6:">
An IPv6 address as defined in
<xref target="RFC4291">RFC 4291, section 2.2</xref>.
</t>
Expand All @@ -1015,20 +1015,20 @@
</t>
<t>
<list style="hanging">
<t hangText="uri">
<t hangText="uri:">
A string instance is valid against this attribute if it is
a valid URI, according to <xref target="RFC3986"/>.
</t>
<t hangText="uri-reference">
<t hangText="uri-reference:">
A string instance is valid against this attribute if it is a valid URI
Reference (either a URI or a relative-reference),
according to <xref target="RFC3986"/>.
</t>
<t hangText="iri">
<t hangText="iri:">
A string instance is valid against this attribute if it is
a valid IRI, according to <xref target="RFC3987"/>.
</t>
<t hangText="iri-reference">
<t hangText="iri-reference:">
A string instance is valid against this attribute if it is a valid IRI
Reference (either an IRI or a relative-reference),
according to <xref target="RFC3987"/>.
Expand Down Expand Up @@ -1059,12 +1059,12 @@
</t>
<t>
<list style="hanging">
<t hangText="json-pointer">
<t hangText="json-pointer:">
A string instance is valid against this attribute if it
is a valid JSON string representation of a JSON Pointer,
according to <xref target="RFC6901">RFC 6901, section 5</xref>.
</t>
<t hangText="relative-json-pointer">
<t hangText="relative-json-pointer:">
A string instance is valid against this attribute if it is a valid
<xref target="relative-json-pointer">Relative JSON Pointer</xref>.
</t>
Expand Down Expand Up @@ -1247,8 +1247,8 @@
<t>
Schema validation is a useful mechanism for annotating instance data
with additional information. The rules for determining when and how
annotations are associated with an instance are outlined in this specification's
overview.
annotations are associated with an instance are outlined in section
<xref target="annotations" format="counter"></xref>.
</t>
<t>
These general-purpose annotation keywords provide commonly used information
Expand Down Expand Up @@ -1425,7 +1425,7 @@
</author>
<date year="2017" month="November"/>
</front>
<seriesInfo name="Internet-Draft" value="draft-handrews-relative-json-pointer-00" />
<seriesInfo name="Internet-Draft" value="draft-handrews-relative-json-pointer-01" />
</reference>
<reference anchor="json-schema">
<front>
Expand All @@ -1438,7 +1438,7 @@
</author>
<date year="2017" month="November"/>
</front>
<seriesInfo name="Internet-Draft" value="draft-handrews-json-schema-00" />
<seriesInfo name="Internet-Draft" value="draft-handrews-json-schema-01" />
</reference>
</references>

Expand Down Expand Up @@ -1477,6 +1477,14 @@
</t>
<t>
<list style="hanging">
<t hangText="draft-handrews-json-schema-validation-01">
<list style="symbols">
<t>This draft is purely a clarification with no functional changes</t>
<t>Restored ommitted "if present" clause for "else" under "if"</t>
<t>Clarified that when "if" is absent, the results of "then" and "else" are ignored</t>
<t>Minor formatting and cross-referencing improvements</t>
</list>
</t>
<t hangText="draft-handrews-json-schema-validation-00">
<list style="symbols">
<t>Added "if"/"then"/"else"</t>
Expand All @@ -1497,7 +1505,7 @@
</t>
<t hangText="draft-wright-json-schema-validation-01">
<list style="symbols">
<t>Standardized on hyphenated format names ("uriref" becomes "uri-ref")</t>
<t>Standardized on hyphenated format names with full words ("uriref" becomes "uri-reference")</t>
<t>Add the formats "uri-template" and "json-pointer"</t>
<t>Changed "exclusiveMaximum"/"exclusiveMinimum" from boolean modifiers of "maximum"/"minimum" to independent numeric fields.</t>
<t>Split the additionalItems/items into two sections</t>
Expand Down