From 2a1bcdcd2ff664ab5efacc8b8ab78922447f912e Mon Sep 17 00:00:00 2001 From: Denis Laxalde Date: Thu, 16 Nov 2017 20:28:26 +0100 Subject: [PATCH 1/3] Fix typos in validation spec --- jsonschema-validation.xml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/jsonschema-validation.xml b/jsonschema-validation.xml index dc91e7c0..d1dacb76 100644 --- a/jsonschema-validation.xml +++ b/jsonschema-validation.xml @@ -122,7 +122,7 @@ and asserts constraints on the structure of the data at each location. An instance location that satisfies all asserted constraints is then annotated with any keywords that contain non-assertion information, - such as desciptive metadata and usage hints. If all locations within + such as descriptive metadata and usage hints. If all locations within the instance satisfy all asserted constraints, then the instance is said to be valid against the schema. @@ -246,7 +246,7 @@
Annotation keywords MUST be applied to all possible sub-instances. - even if such application can be short-circuited when only assertion + Even if such application can be short-circuited when only assertion evaluation is needed. For instance, the "contains" keyword need only be checked for assertions until at least one array item proves valid. However, when working with annotations, all items in the array must @@ -866,7 +866,7 @@ The "format" keyword functions as both an annotation () and as an assertion (). While no special effort is required to - implement it as an annotation convenying semantic meaning, implementing + implement it as an annotation conveying semantic meaning, implementing validation is non-trivial. @@ -1098,7 +1098,7 @@ The content keywords function as both annotations () and as assertions (). - While no special effort is required to implement them as annotations convenying + While no special effort is required to implement them as annotations conveying how applications can interpret the data in the string, implementing validation of conformance to the media type and encoding is non-trivial. From e055e91fe098a1f421bbc8b54af2afbf678fdb93 Mon Sep 17 00:00:00 2001 From: Denis Laxalde Date: Thu, 16 Nov 2017 20:39:00 +0100 Subject: [PATCH 2/3] Fix typos in core spec --- jsonschema-core.xml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/jsonschema-core.xml b/jsonschema-core.xml index ec03d656..127e6937 100644 --- a/jsonschema-core.xml +++ b/jsonschema-core.xml @@ -220,7 +220,7 @@ Some functionality that is useful for working with schemas is defined by each media type, namely media type parameters and URI fragment identifier syntax and semantics. These features are - useful in content negotiation and in caclulating URIs for specific + useful in content negotiation and in calculating URIs for specific locations within an instance, respectively. @@ -468,7 +468,7 @@ allow tools to follow the correct behaviour. - Note that the recursive nature of meta-schemas requires re-definining + Note that the recursive nature of meta-schemas requires re-defining recursive keywords in the extended meta-schema, as can be seen in the JSON Hyper-Schema meta-schema. @@ -581,7 +581,7 @@ have one that is an empty string. - How should an "$id" URI reference containing a fragement with other components + How should an "$id" URI reference containing a fragment with other components be interpreted? There are two cases: when the other components match the current base URI and when they change the base URI. @@ -909,7 +909,7 @@ User-Agent: product-name/5.4.1 so-cool-json-schema/1.0.2 curl/7.43.0 fail to strip them if such behavior is expected. - A malicous schema author could place executable code or other dangerous + A malicious schema author could place executable code or other dangerous material within a "$comment". Implementations MUST NOT parse or otherwise take action based on "$comment" contents. From 348bf0bae06ce827effaa9021341ee4ce779bf92 Mon Sep 17 00:00:00 2001 From: Denis Laxalde Date: Thu, 16 Nov 2017 20:39:27 +0100 Subject: [PATCH 3/3] Fix typos in hyperschema spec --- jsonschema-hyperschema.xml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/jsonschema-hyperschema.xml b/jsonschema-hyperschema.xml index b12fa4fb..44fdee29 100644 --- a/jsonschema-hyperschema.xml +++ b/jsonschema-hyperschema.xml @@ -368,7 +368,7 @@ application/json does not define a URI fragment resolution syntax, so properties or array elements within a plain JSON document cannot be fully identified by a URI. When it is not possible to produce a complete URI, - the position of the context SHOULD be conveyed by a the URI of the instance + the position of the context SHOULD be conveyed by the URI of the instance document, together with a separate plain-string JSON Pointer. @@ -621,7 +621,7 @@ For protocols supporting content-negotiation, implementations MAY choose to describe possible target media types using protocol-specific information in "headerSchema". If both - protocol-specific information and "targtMediaType" are present, then the + protocol-specific information and "targetMediaType" are present, then the value of "targetMediaType" MUST be compatible with the protocol-specific information, and SHOULD indicate the media type that will be returned in the absence of content negotiation. @@ -1068,7 +1068,7 @@ for varname in T: - Deterimine which variables can accept input + Determine which variables can accept input Pre-populate the input data set if the template resolution data @@ -1574,7 +1574,7 @@ Link: rel=describedBy - The attachment pointer is the root pointer (the only possiblity with + The attachment pointer is the root pointer (the only possibility with an empty object for the instance). The context URI is the default, which is the requested document. Since application/json does not allow for fragments, the context pointer is necessary to fully describe the @@ -1887,7 +1887,7 @@ Link: rev=up The following hyper-schema, applied to the instance in the response above, would produce the same "self" link and "up" link with "anchor". It also shows the use of a templated "base" URI, plus both absolute - and relative JSON Pointers in "tempaltePointers". + and relative JSON Pointers in "templatePointers".