draft-ietf-httpapi-linkset-10.unpg.txt   draft-ietf-httpapi-linkset-latest.txt 
skipping to change at line 61 skipping to change at page 2, line 17
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Use Cases and Motivation 3. Use Cases and Motivation . . . . . . . . . . . . . . . . . . 3
3.1. Third-Party Links 3.1. Third-Party Links . . . . . . . . . . . . . . . . . . . . 4
3.2. Challenges Writing to HTTP Link Header Field 3.2. Challenges Writing to HTTP Link Header Field . . . . . . 5
3.3. Large Number of Links 3.3. Large Number of Links . . . . . . . . . . . . . . . . . . 5
4. Document Formats for Sets of Links 4. Document Formats for Sets of Links . . . . . . . . . . . . . 5
4.1. HTTP Link Document Format: application/linkset 4.1. HTTP Link Document Format: application/linkset . . . . . 7
4.2. JSON Document Format: application/linkset+json 4.2. JSON Document Format: application/linkset+json . . . . . 7
4.2.1. Set of Links 4.2.1. Set of Links . . . . . . . . . . . . . . . . . . . . 8
4.2.2. Link Context Object 4.2.2. Link Context Object . . . . . . . . . . . . . . . . . 8
4.2.3. Link Target Object 4.2.3. Link Target Object . . . . . . . . . . . . . . . . . 9
4.2.4. Link Target Attributes 4.2.4. Link Target Attributes . . . . . . . . . . . . . . . 10
4.2.5. JSON Extensibility 4.2.5. JSON Extensibility . . . . . . . . . . . . . . . . . 14
5. The "profile" parameter for media types to Represent Sets of 5. The "profile" parameter for media types to Represent Sets of
Links Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
6. The "linkset" Relation Type for Linking to a Set of Links 6. The "linkset" Relation Type for Linking to a Set of Links . . 15
7. Examples 7. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 16
7.1. Set of Links Provided as application/linkset 7.1. Set of Links Provided as application/linkset . . . . . . 16
7.2. Set of Links Provided as application/linkset+json 7.2. Set of Links Provided as application/linkset+json . . . . 18
7.3. Discovering a Link Set via the "linkset" Link Relation 7.3. Discovering a Link Set via the "linkset" Link Relation
Type Type . . . . . . . . . . . . . . . . . . . . . . . . . . 19
7.4. Link Set Profiles 7.4. Link Set Profiles . . . . . . . . . . . . . . . . . . . . 20
7.4.1. Using a "profile" Attribute with a "linkset" Link 7.4.1. Using a "profile" Attribute with a "linkset" Link . . 20
7.4.2. Using a "profile" Parameter with a Link Set Media 7.4.2. Using a "profile" Parameter with a Link Set Media
Type Type . . . . . . . . . . . . . . . . . . . . . . . . 21
7.4.3. Using a Link with a "profile" Link Relation Type 7.4.3. Using a Link with a "profile" Link Relation Type . . 21
8. IANA Considerations 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22
8.1. Link Relation Type: linkset 8.1. Link Relation Type: linkset . . . . . . . . . . . . . . . 22
8.2. Media Type: application/linkset 8.2. Media Type: application/linkset . . . . . . . . . . . . . 23
8.3. Media Type: application/linkset+json 8.3. Media Type: application/linkset+json . . . . . . . . . . 24
9. Security Considerations 9. Security Considerations . . . . . . . . . . . . . . . . . . . 25
10. References 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 26
10.1. Normative References 10.1. Normative References . . . . . . . . . . . . . . . . . . 26
10.2. Informative References 10.2. Informative References . . . . . . . . . . . . . . . . . 27
Appendix A. JSON-LD Context Appendix A. JSON-LD Context . . . . . . . . . . . . . . . . . . 28
Appendix B. Implementation Status Appendix B. Implementation Status . . . . . . . . . . . . . . . 33
B.1. GS1 B.1. GS1 . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
B.2. FAIR Signposting Profile B.2. FAIR Signposting Profile . . . . . . . . . . . . . . . . 34
B.3. Open Journal Systems (OJS) B.3. Open Journal Systems (OJS) . . . . . . . . . . . . . . . 34
Acknowledgements Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 34
Authors' Addresses Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 34
1. Introduction 1. Introduction
Resources on the Web often use typed Web Links [RFC8288], either Resources on the Web often use typed Web Links [RFC8288], either
embedded in resource representations, for example using the <link> embedded in resource representations, for example using the <link>
element for HTML documents, or conveyed in the HTTP "Link" header element for HTML documents, or conveyed in the HTTP "Link" header
field for documents of any media type. In some cases, however, field for documents of any media type. In some cases, however,
providing links in this manner is impractical or impossible and providing links in this manner is impractical or impossible and
delivering a set of links as a stand-alone document is preferable. delivering a set of links as a stand-alone document is preferable.
 End of changes. 4 change blocks. 
39 lines changed or deleted 39 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/