|
3 | 3 | <!ENTITY rfc2046 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2046.xml"> |
4 | 4 | <!ENTITY rfc2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml"> |
5 | 5 | <!ENTITY rfc3986 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3986.xml"> |
| 6 | +<!ENTITY rfc4151 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4151.xml"> |
6 | 7 | <!--<!ENTITY rfc4287 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4287.xml">--> |
7 | 8 | <!--<!ENTITY rfc5226 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5226.xml">--> |
8 | 9 | <!ENTITY rfc5789 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5789.xml"> |
|
766 | 767 | resource. The value MUST be a registered link relation from the |
767 | 768 | <xref target="RFC5988">IANA Link Relation Type Registry established in RFC 5988</xref>, |
768 | 769 | or a normalized URI following the <xref target="RFC3986">URI production of RFC 3986</xref>. |
| 770 | + This property is required. |
769 | 771 | </t> |
770 | 772 |
|
771 | 773 | <t> |
|
790 | 792 |
|
791 | 793 | <t> |
792 | 794 | Relationship definitions are not normally media type |
793 | | - dependent, and users are encouraged to utilize existing |
794 | | - accepted relation definitions. |
| 795 | + dependent, and users are encouraged to utilize the most |
| 796 | + suitable existing accepted relation definitions. |
795 | 797 | </t> |
796 | 798 |
|
| 799 | + <t> |
| 800 | + When no registered relation (aside from "related") applies, users are |
| 801 | + encouraged to mint their own extension relation types, as described in |
| 802 | + <xref target="RFC5988">section 4.2 of RFC 5988</xref>. The simplest |
| 803 | + approaches for choosing link relation type URIs are to either use |
| 804 | + a URI scheme that is already in use to identify the system's primary |
| 805 | + resources, or to use a human-readable, non-dereferenceable URI scheme |
| 806 | + such as <xref target="RFC4151">"tag", defined by RFC 4151</xref>. |
| 807 | + Extension relation type URIs need not be dereferenceable, even when |
| 808 | + using a scheme that allows it. |
| 809 | + </t> |
797 | 810 | <figure> |
798 | 811 | <preamble> |
799 | | - For example, if a hyper-schema is defined: |
| 812 | + As an example of registered relation types, if a hyper-schema is defined: |
800 | 813 | </preamble> |
801 | 814 | <artwork> |
802 | 815 | <![CDATA[{ |
@@ -1543,6 +1556,7 @@ GET /foo/ |
1543 | 1556 | <references title="Informative References"> |
1544 | 1557 | &rfc2046; |
1545 | 1558 | <!--&rfc5226;--> |
| 1559 | + &rfc4151; |
1546 | 1560 | &rfc5789; |
1547 | 1561 | &rfc5988; |
1548 | 1562 | &rfc7231; |
|
0 commit comments