|
4 | 4 | <!ENTITY rfc2046 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2046.xml">
|
5 | 5 | <!ENTITY rfc2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
|
6 | 6 | <!ENTITY rfc3986 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3986.xml">
|
7 |
| -<!ENTITY rfc4287 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4287.xml"> |
| 7 | +<!--<!ENTITY rfc4287 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4287.xml">--> |
8 | 8 | <!--<!ENTITY rfc5226 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5226.xml">-->
|
9 | 9 | <!ENTITY rfc5988 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5988.xml">
|
10 | 10 | <!ENTITY rfc6570 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6570.xml">
|
|
218 | 218 | </artwork>
|
219 | 219 | </figure>
|
220 | 220 | <figure>
|
221 |
| - <preamble>An example of a JSON instance using this schema to produce a rel="self" and rel="next" links</preamble> |
| 221 | + <preamble>An example of a JSON instance using this schema to produce rel="self" and rel="next" links</preamble> |
222 | 222 | <artwork>
|
223 | 223 | <![CDATA[
|
224 | 224 | {
|
|
510 | 510 |
|
511 | 511 | <section title="rel">
|
512 | 512 | <t>
|
513 |
| - The value of the "rel" property indicates the name of the relation to the target resource. |
| 513 | + The value of the "rel" property indicates the name of the relation to the target resource. The value MUST be a registered link relation from the <xref target="RFC5988">IANA Link Relation Type Registry established in RFC 5988</xref>, or a normalized URI following the <xref target="RFC3986">URI production of RFC 3986</xref>. |
514 | 514 | </t>
|
515 | 515 |
|
516 | 516 | <t>
|
517 |
| - The relation to the target SHOULD be interpreted as specifically from the instance object that the schema (or sub-schema) applies to, not just the top level resource that contains the object within its hierarchy. |
518 |
| - A link relation from the top level resource to a target MUST be indicated with the schema describing the top level JSON representation. |
| 517 | + The relation to the target is interpreted as from the instance that the schema (or sub-schema) applies to, not any larger document that the instance may have been found in. |
519 | 518 | </t>
|
520 | 519 |
|
521 | 520 | <t>
|
522 |
| - Relationship definitions SHOULD NOT be media type dependent, and users are encouraged to utilize existing accepted relation definitions, including those in existing relation registries (see <xref target="RFC4287">RFC 4287</xref>). |
| 521 | + Relationship definitions are not normally media type dependent, and users are encouraged to utilize existing accepted relation definitions. |
523 | 522 | </t>
|
524 | 523 |
|
525 | 524 | <figure>
|
@@ -851,7 +850,7 @@ GET /foo/
|
851 | 850 | &rfc2045;
|
852 | 851 | &rfc2119;
|
853 | 852 | &rfc3986;
|
854 |
| - &rfc4287; |
| 853 | + <!--&rfc4287;--> |
855 | 854 | &rfc6570;
|
856 | 855 | <reference anchor="json-schema">
|
857 | 856 | <front>
|
|
0 commit comments