Re: [apps-discuss] Sunset HTTP header field

[Erik Wilde <[e-mail]>]

hello james.

thanks a lot for your feedback!

On 2015-08-03 18:54 , James M Snell wrote:
> This is certainly interesting, but I'm not quite sure it goes far
> enough. In general, when a particular API is being deprecated, there
> is generally some form of replacement or alternative that developers
> are being pushed towards, and potentially some form of notice that
> should be displayed.

yes, those may be things that people want to advertise in well-known 
ways. i had listed both aspects as open issues:

https://tools.ietf.org/html/draft-wilde-sunset-header-00#section-8

my idea was to add optional qualifiers to the timestamp if people seem 
to want these features, but that's of course just one way of doing it.

> Considering that, a Link header might be an interesting possible approach:
> Link: </deprecation-notice.html>; rel="sunset"; title="This API will
> be sunset on 2015-12-12"; sunset=2015-12-12

i was considering the link relation type design option, but then 
concluded that at its core, the sunset timestamp is mostly a "unary 
link" and thus does not fit the link model very well. but i agree that 
pretty much anything can be modeled as links, and then it would fit into 
the link header as shown in your example.

thanks again and cheers,

dret.

-- 
erik wilde | mailto:[e-mail]  -  tel:[phone] |
            | UC Berkeley  -  School of Information (ISchool) |
            | http://dret.net/netdret http://twitter.com/dret |