|
293 | 293 | </t>
|
294 | 294 | <t>
|
295 | 295 | As with all JSON Schema keywords, all keywords described in this section
|
296 |
| - are optional. The minimal valid JSON Hyper-schema is the blank object. |
| 296 | + are optional. The minimal valid JSON Hyper-schema is the blank object. |
297 | 297 | </t>
|
298 | 298 |
|
299 | 299 | <section title="base" anchor="base">
|
|
635 | 635 | This property provides a schema that is expected to describe
|
636 | 636 | the link target's representation. Depending on the protocol,
|
637 | 637 | the schema may or may not describe the request or response to
|
638 |
| - any particular operation performed with the link. See the |
| 638 | + any particular operation performed with the link. See the |
639 | 639 | <xref target="HTTP">JSON Hyper-Schema and HTTP</xref> section for
|
640 | 640 | an in-depth discussion of how this keyword is used with HTTP.
|
641 | 641 | </t>
|
|
784 | 784 | <t>
|
785 | 785 | In JSON Hyper-Schema, <xref target="targetSchema">"targetSchema"</xref>
|
786 | 786 | supplies a non-authoritative description of the target resource's
|
787 |
| - representation. A client can use "targetSchema" to structure input for |
| 787 | + representation. A client can use "targetSchema" to structure input for |
788 | 788 | replacing or modifying the representation, or as the base representation
|
789 | 789 | for building a patch document based on a patch media type.
|
790 | 790 | </t>
|
|
808 | 808 | The <xref target="submissionSchema">"submissionSchema"</xref> and
|
809 | 809 | <xref target="submissionMediaType">"submissionMediaType"</xref> keywords
|
810 | 810 | describe the ___domain of the processing function implemented by the target
|
811 |
| - resource. Otherwise, as noted above, the submission schema and media type |
| 811 | + resource. Otherwise, as noted above, the submission schema and media type |
812 | 812 | are ignored for operations to which they are not relevant.
|
813 | 813 | </t>
|
814 | 814 |
|
|
843 | 843 | describes the target information resource (including for replacing the
|
844 | 844 | contents of the resource in a PUT request), unlike "submissionSchema"
|
845 | 845 | which describes the user-submitted request data to be evaluated by the
|
846 |
| - resource. "submissionSchema" is intended for use with requests that |
| 846 | + resource. "submissionSchema" is intended for use with requests that |
847 | 847 | have payloads that are not necessarily defined in terms of the target
|
848 | 848 | representation.
|
849 | 849 | </t>
|
|
0 commit comments