-
Notifications
You must be signed in to change notification settings - Fork 31
/
Copy pathdraft-ietf-httpapi-deprecation-header.xml
11 lines (11 loc) · 1.68 KB
/
draft-ietf-httpapi-deprecation-header.xml
1
2
3
4
5
6
7
8
9
10
11
<?xml version="1.0" encoding="UTF-8" ?>
<service primary="IETF" secondary="I-D" id="ietf-httpapi-deprecation-header">
<title>The Deprecation HTTP Header</title>
<documentation source="https://datatracker.ietf.org/doc/html/draft-ietf-httpapi-deprecation-header">The HTTP Deprecation response header field can be used to signal to consumers of a URI-identified resource that the use of the resource has been deprecated. Additionally, the deprecation link relation can be used to link to a resource that provides additional context for the deprecation, and possibly ways in which clients can find a replacement for the deprecated resource.</documentation>
<http-header def="Deprecation">
<documentation source="https://datatracker.ietf.org/doc/html/draft-ietf-httpapi-deprecation-header#section-2">The "Deprecation" HTTP response header field allows a server to communicate to a client that the URI-identified resource in context of the message is deprecated. It can also provide information that the resource is deprecated since which version.</documentation>
</http-header>
<link-relation def="deprecation">
<documentation source="https://datatracker.ietf.org/doc/html/draft-ietf-httpapi-deprecation-header#section-3">In addition to the Deprecation HTTP header field, the server can use links with the "deprecation" link relation type to communicate to the client where to find more information about deprecation of the context. This information can be in the form of documentation of the resource including details about the deprecation related aspects of the context or the deprecation policy of the context provider or both for example.</documentation>
</link-relation>
</service>