|
721 | 721 | <t> |
722 | 722 | When schemas are downloaded, |
723 | 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>. |
| 724 | + see <xref target="hypermedia">Usage for Hypermedia</xref>. |
725 | 725 | </t> |
726 | 726 | <t> |
727 | 727 | Implementations SHOULD be able to associate arbitrary URIs with an arbitrary |
|
835 | 835 | </t> |
836 | 836 | </section> |
837 | 837 |
|
838 | | - <section title="Usage for Hypermedia"> |
| 838 | + <section title="Usage for Hypermedia"anchor="hypermedia"> |
839 | 839 |
|
840 | 840 | <t> |
841 | 841 | JSON has been adopted widely by HTTP servers for automated APIs and robots. This |
@@ -936,7 +936,7 @@ Link: </alice>;rel="schema", </bob>;rel="schema" |
936 | 936 |
|
937 | 937 | </section> |
938 | 938 |
|
939 | | - <section title="Usage Over HTTP"anchor="http-usage"> |
| 939 | + <section title="Usage Over HTTP"> |
940 | 940 | <t> |
941 | 941 | When used for hypermedia systems over a network, |
942 | 942 | <xref target="RFC7231">HTTP</xref> is frequently the protocol of choice for |
|
0 commit comments