|
220 | 220 | Some functionality that is useful for working with schemas is |
221 | 221 | defined by each media type, namely media type parameters and |
222 | 222 | URI fragment identifier syntax and semantics. These features are |
223 | | - useful in content negotiation and in caclulating URIs for specific |
| 223 | + useful in content negotiation and in calculating URIs for specific |
224 | 224 | locations within an instance, respectively. |
225 | 225 | </t> |
226 | 226 | <t> |
|
468 | 468 | allow tools to follow the correct behaviour. |
469 | 469 | </t> |
470 | 470 | <t> |
471 | | - Note that the recursive nature of meta-schemas requires re-definining |
| 471 | + Note that the recursive nature of meta-schemas requires re-defining |
472 | 472 | recursive keywords in the extended meta-schema, as can be seen in |
473 | 473 | the JSON Hyper-Schema meta-schema. |
474 | 474 | </t> |
|
581 | 581 | have one that is an empty string. |
582 | 582 | <!-- All of the standard meta-schemas use an empty fragment in their id/$id values. --> |
583 | 583 | <cref> |
584 | | - How should an "$id" URI reference containing a fragement with other components |
| 584 | + How should an "$id" URI reference containing a fragment with other components |
585 | 585 | be interpreted? There are two cases: when the other components match |
586 | 586 | the current base URI and when they change the base URI. |
587 | 587 | </cref> |
@@ -909,7 +909,7 @@ User-Agent: product-name/5.4.1 so-cool-json-schema/1.0.2 curl/7.43.0 |
909 | 909 | fail to strip them if such behavior is expected. |
910 | 910 | </t> |
911 | 911 | <t> |
912 | | - A malicous schema author could place executable code or other dangerous |
| 912 | + A malicious schema author could place executable code or other dangerous |
913 | 913 | material within a "$comment". Implementations MUST NOT parse or otherwise |
914 | 914 | take action based on "$comment" contents. |
915 | 915 | </t> |
|
0 commit comments