Nils Goroll

@smatsson thank you, I have changed the wording based on your feedback. I have now specified the methods to send a `Content-Location` for, but actually I am not so sure...

Re @smatsson OK, I have reverted to basically ebf5701, but avoiding to talk about _permanent location_. Yes, I agree, this is merely a pointer to the appropriate place in the...

re @smatsson > In this proposal it seems that it's unknown for the client when the header can be received and it's unknown what to do with the header once...

re @Acconut force-pushing is a habit from other projects which works because gh keeps and logs previous commit hashes for PRs. But I will try to remember that this is...

@Acconut sorry for not responding earlier, please feel free

sure, that would work. But I wonder if the project should have a simple registry (need not be more than a file with hash name identifiers)?

I still think that a simple registry would leave the least amount of slack at very low overhead.

I don't disagree with naming rules. But they still leave room for interpretation. I just found the [iana hash function textual names registry](https://www.iana.org/assignments/hash-function-text-names/hash-function-text-names.xhtml#hash-function-text-names-1), which, unfortunately, does not have that many...

room for interpretation examples: `sha3-256` vs. `sha-3-256` vs `sha3_256` vs. `sha_3_256` etc.

re @Acconut HTTP does not use that strict a definition: https://httpwg.org/specs/rfc7231.html#header.content-type > The "Content-Type" header field indicates the media type of the associated representation: either the representation enclosed in the...