Link Headers in POST Responses

I have a question to put to the group about requirements for Container
responses:

LDP 5.2.1.4[0] requires returning a Container Link header for *all
responses* to requests to containers.

The body of POST responses is undefined and a common implementation choice
is to return the newly created resource including any triples added by the
server. It seems desirable, in this case, to return headers associated with
the newly created resource (especially the ETag).

Should a server taking this approach strictly follow 5.2.1.4? If so, is it
acceptable to return the ETag for the created resource while returning Link
headers for the requested resource?

The examples in the spec vary. Example 11/12[1] shows the container header;
Example 15/16[2] do not. None of the examples in LDP Primer[3] show a
container header.

I have an open issue[4] for this in the Ruby implementation.

Best,

Tom Johnson
Metadata & Platform Architect
Digital Public Library of America

[0] https://www.w3.org/TR/ldp/#h-ldpc-linktypehdr
[1] https://www.w3.org/TR/ldp/#ldpc-ex-membership-add-new-liability-req
[2] https://www.w3.org/TR/ldp/#ldpc-ex-membership-add-new-advisor-req
[3] https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-primer/ldp-primer.html
[4] https://github.com/ruby-rdf/rdf-ldp/issues/48