Registration Request for the respond-for HTTP preference

[irakli <[e-mail]>]

   o  Preference: respond-for

   o  Value: any alpha-numeric value. Dashes are also allowed.

   o  Optional Parameters: None

   o  Description: Expanded version of the "return" preference that 
allows clients to hint to the server the use-case for the response.
This allows batching response variations by common use-cases. The goal
is similar to GraphQL: letting client choose which data it needs, but
is significantly more light-weight and can allow all that client needs
in a very wide variety of cases, without resorting to heavier and 
potentially riskier GraphQL approach. For instance, for a blog post
a client may request "respond-for: teaser" or "respond-for: full-post"  

   o  Reference: https://www.freshblurbs.com/blog/2015/06/25/api-representations-prefer.html <https://www.freshblurbs.com/blog/2015/06/25/api-representations-prefer.html>

   o  Notes: We have used this approach successfully at a number of 
companies over the years but would like to standardize the preference
rather than using an unregistered preference, or using the "return" 
preference with values that are non-standard.


Thank you!

Irakli Nadareishvili