|
528 | 528 | </section>
|
529 | 529 |
|
530 | 530 | <section title="Base URI and Dereferencing">
|
| 531 | + <t> |
| 532 | + To differentiate between schemas in a vast ecosystem, schemas are |
| 533 | + identified by URI, and can embed references to other schemas by specifying their URI. |
| 534 | + </t> |
| 535 | + |
531 | 536 | <section title="Initial Base URI">
|
532 | 537 | <t>
|
533 | 538 | <xref target="RFC3986">RFC3986 Section 5.1</xref> defines how to determine the
|
|
709 | 714 | </t>
|
710 | 715 | <section title="Loading a referenced schema">
|
711 | 716 | <t>
|
712 |
| - To differentiate between schemas in a vast ecosystem, schemas are |
713 |
| - identified by URI. As specified above, this does not necessarily mean |
714 |
| - anything is downloaded, but instead JSON Schema implementations SHOULD |
715 |
| - understand ahead of time which schemas they will be using, and the URIs that |
716 |
| - identify them. |
| 717 | + The use of URIs to identify remote schemas does not necessarily mean anything is downloaded, |
| 718 | + but instead JSON Schema implementations SHOULD understand ahead of time which schemas they will be using, |
| 719 | + and the URIs that identify them. |
| 720 | + </t> |
| 721 | + <t> |
| 722 | + When schemas are downloaded, |
| 723 | + for example by a generic user-agent that doesn't know until runtime which schemas to download, |
| 724 | + see <xref target="http-usage">Usage over HTTP</xref>. |
717 | 725 | </t>
|
718 | 726 | <t>
|
719 | 727 | Implementations SHOULD be able to associate arbitrary URIs with an arbitrary
|
@@ -928,7 +936,7 @@ Link: </alice>;rel="schema", </bob>;rel="schema"
|
928 | 936 |
|
929 | 937 | </section>
|
930 | 938 |
|
931 |
| - <section title="Usage Over HTTP"> |
| 939 | + <section title="Usage Over HTTP" anchor="http-usage"> |
932 | 940 | <t>
|
933 | 941 | When used for hypermedia systems over a network,
|
934 | 942 | <xref target="RFC7231">HTTP</xref> is frequently the protocol of choice for
|
|
0 commit comments