simplify the spec, as that could focus on headers only;
remove complex examples from the spec;
allow using different headers depending on the user requirements (eg. Digest has a very well defined
semantic that you may not want to use)
We can
remove Digest from examples;
remove from the scope of this spec the signature of the message body, as we can only sign a payload body, being the message subject to transfer coding;
clarify that we just want to sign headers;
clarify that you can sign the payload body OR a resource representation using other headers;
in an informative section, warn about digest semantic Digest usage in signatures
I expect
This spec to be disentangled from the
Digestone.This will:
We can
Digestfrom examples;message body, as we can only sign apayload body, being the message subject to transfer coding;Digest usage in signatures@dlangley @msporny @liamdennehy