Draft: draft-ietf-httpapi-deprecation-header

Commentary: yes , this one will have to be adjusted if we keep the draft . thanks . 
 thanks so much , those were a lot of changes !
For example, an API might not use Deprecation headers on all of its
resources, but only on designated resources such as the API's home
document.  This means that deprecation information is available, but
in order to get it, clients have to periodically inspect the home
document.  In this example, the extended context of the Deprecation
header would be all resources provided by the API, while the
visibility of the information would only be on the home document.
For example, an API might not use Deprecation header fields on all of
its resources, but only on designated resources such as the API's
home document.  This means that deprecation information is available,
but in order to get it, clients have to periodically inspect the home
document.  In this example, the extended context of the Deprecation
header field would be all resources provided by the API, while the
visibility of the information would only be on the home document.
In addition to the deprecation related information, if the resource
provider wants to convey to the client application that the
deprecated resource is expected to become unresponsive at a specific
point in time, the Sunset HTTP header field RFC8594 can be used in
addition to the "Deprecation" header.
In addition to the deprecation related information, if the resource
provider wants to convey to the client application that the
deprecated resource is expected to become unresponsive at a specific
point in time, the Sunset HTTP header field RFC8594 can be used in
addition to the "Deprecation" header field.
The "Deprecation" response header should be added to the permanent
registry of message header fields (see RFC3864).
The "Deprecation" response header field should be added to the
permanent registry of message header fields (see RFC3864).
Description: Deprecation header is recommended as the preferred
way to communicate API deprecation in Zalando API designs.
Description: Deprecation header field is recommended as the
preferred way to communicate API deprecation in Zalando API
designs.
Description: Deprecation header is incorporated in Hesperides, a
configuration management tool providing universal text file
templating and properties editing through a REST API or a webapp.
Description: Deprecation header field is incorporated in
Hesperides, a configuration management tool providing universal
text file templating and properties editing through a REST API or
a webapp.
Description: Core REST API of MediaWiki would use Deprecation
header for endpoints that have been deprecated because a new
endpoint provides the same or better functionality.
Description: Core REST API of MediaWiki would use Deprecation
header field for endpoints that have been deprecated because a new
endpoint provides the same or better functionality.
In cases where a "Link" header is used to provide documentation, one
should assume that the content of the "Link" header field may not be
secure, private or integrity-guaranteed, and due caution should be
exercised when using it.  Applications consuming the resource SHOULD
check the referred resource documentation to verify authenticity and
accuracy.
In cases where a "Link" header field is used to provide
documentation, one should assume that the content of the "Link"
header field may not be secure, private or integrity-guaranteed, and
due caution should be exercised when using it.  Applications
consuming the resource SHOULD check the referred resource
documentation to verify authenticity and accuracy.