Issue #507: clarify that "canonical" job result link should include query parameters

[soxofaan]

Issue #507: clarify that "canonical" job result link should include query parameters

[m-mohr]

Thinking a bit more about this, I think this was intentionally left out as implementations could either choose to include this parameter in the canonical link href or encode it implicitly in the signed URL. Depending on the implementation, it should or should not be part of the canonical href. Clients (which includes the aggregator) would basically just follow the link that was provided. If the href doesn't work as provided by the implementation, that's an implementation bug.

Makes sense, right? If yes, could you update the PR to clarify this?

[soxofaan]

implementations could either choose to include this parameter in the canonical link href or encode it implicitly in the signed URL.

That's what I actually meant here: query parameters should be preserved in the canonical URL: visibly in the URL with a trailing ?partial=true, or embedded in the opaque blob of the signed URL. How it's done doesn't matter, as long as the original parameter is preserved.
But that's apparently not clear from the current PR

[soxofaan]

did attempt to clarify the clarification