Consider options for Path of side-loaded dictionaries

[pmeenan]

For dictionaries loaded from a Link: header, it could be useful for the request that triggers the dictionary fetch to either specify the scope of the dictionary or for the allowable path for the dictionary to include the path from the original request and from a document <link> tag to also provide other path options.

The path restrictions for dictionary use as they are currently written are for providing some level of ownership proof when setting the scope. The request that triggers the dictionary fetch and the document itself are also proof points and could allow for serving the dictionary from a different directory than the resources it is intended to be used with (still needs to be same-origin as the resources).

[pmeenan]

Closed this for now as setting the covered path outside of the dictionary response opens up more complexities and concerns than it solves. A 1:1 matching of dictionary is easier and cleaner, at least for now.