|
46 | 46 |
|
47 | 47 | <abstract> |
48 | 48 | <t> |
49 | | - JSON Schema defines the media type "application/schema+json", a JSONbased format |
| 49 | + JSON Schema defines the media type "application/schema+json", a JSON-based format |
50 | 50 | for describing the structure of JSON data. |
51 | 51 | JSON Schema asserts what a JSON document must look like, |
52 | 52 | ways to extract information from it, |
|
108 | 108 | This document proposes a new media type "application/schema+json" to identify a JSON |
109 | 109 | Schema for describing JSON data. |
110 | 110 | JSON Schemas are themselves JSON documents. |
111 | | - This, and related specifications, define keywords allowing authors describe JSON data in several ways. |
| 111 | + This, and related specifications, define keywords allowing authors to describe JSON data in several ways. |
112 | 112 | </t> |
113 | 113 |
|
114 | 114 | <section title="Validation"> |
|
373 | 373 | A schema MUST NOT be run into an infinite loop against a schema. For example, if two schemas "#alice" and "#bob" |
374 | 374 | both have an "allOf" property that refers to the other, a naive validator might get stuck in an infinite recursive |
375 | 375 | loop trying to validate the instance. |
376 | | - Schemas SHOULD NOT make use of infinite recursive nesting like this, the behavior is undefined. |
| 376 | + Schemas SHOULD NOT make use of infinite recursive nesting like this; the behavior is undefined. |
377 | 377 | </t> |
378 | 378 | </section> |
379 | 379 |
|
|
524 | 524 | <section title="Usage for hypermedia"> |
525 | 525 |
|
526 | 526 | <t> |
527 | | - One of the largest adopters of JSON has been HTTP servers for automated APIs and robots. |
| 527 | + JSON has been adopted widely by HTTP servers for automated APIs and robots. |
528 | 528 | This section describes how to enhance processing of JSON documents in a more RESTful manner |
529 | 529 | when used with protocols that support media types and <xref target="RFC5988">Web linking</xref>. |
530 | 530 | </t> |
@@ -604,7 +604,7 @@ Link: </alice>;rel="profile", </bob>;rel="profile" |
604 | 604 |
|
605 | 605 | <section title="Usage over HTTP"> |
606 | 606 | <t> |
607 | | - When used for hypermedia systems over a network, <xref target="RFC7231">HTTP</xref> is frequently the protocol of choice for distributing schemas. Misbehaved clients can pose problems for server maintainers if they pull a schema over the network more frequently than necessary, when it's instead possible to cache a schema for a long period of time. |
| 607 | + When used for hypermedia systems over a network, <xref target="RFC7231">HTTP</xref> is frequently the protocol of choice for distributing schemas. Misbehaving clients can pose problems for server maintainers if they pull a schema over the network more frequently than necessary, when it's instead possible to cache a schema for a long period of time. |
608 | 608 | </t> |
609 | 609 | <t> |
610 | 610 | HTTP servers SHOULD set long-lived caching headers on JSON Schemas. |
|
0 commit comments