Re: Context Link Header on PUT/POST?

On 3/5/15 8:13 PM, Gregg Kellogg wrote:
>  From Wikipedia [1], it seems that the Link header may just be valid for Response objects, not Request objects, but I confess that I can't really tell what Header fields (request or response) are defined for HTTP 2.0. Were it legal, then IMO supplying a Link to the context as part of a POST/PUT/PATCH would be reasonable, but why do it? The main intention of the Link header is to either provide a context for a document that can't otherwise be modified to include it inline, or when the client might not be able to handle anything other than application/json. Obviously, in the request case, both client and server must be JSON-LD aware, so placing it within the body makes the most sense (to me, anyway).

Gregg,

I brought this issue or "Link:" in request headers, as a basic HTTP 
pattern, up with Mark Nottingham last year [1]. We do need to be able to 
leverage relations as context providers in an HTTP request. This is 
vital to an overall web of extensible interactions that's driven by 
relations (comprehensible to both humans and machines).

[1] http://lists.w3.org/Archives/Public/public-webpayments/2014Jul/0112.html
[2] https://github.com/mnot/I-D/issues/61 -- latest state of affairs.

-- 
Regards,

Kingsley Idehen	
Founder & CEO
OpenLink Software
Company Web: http://www.openlinksw.com
Personal Weblog 1: http://kidehen.blogspot.com
Personal Weblog 2: http://www.openlinksw.com/blog/~kidehen
Twitter Profile: https://twitter.com/kidehen
Google+ Profile: https://plus.google.com/+KingsleyIdehen/about
LinkedIn Profile: http://www.linkedin.com/in/kidehen
Personal WebID: http://kingsley.idehen.net/dataspace/person/kidehen#this