Single endpoint for all actions?

[jernst]

In 0.4, well-known data-rights.json enumerates actions, but the way I read it, does not permit the publication of different endpoints for different actions.

Proposal: allow the publication of N endpoints in the same JSON, each of which specifies different actions: "For Do Not Sell requests, push 3" :-) Chances are that some larger businesses will not be able to provide all actions at the same endpoint, because they will outsource some of the actions to a third party, and keep some in-house or such.

[rrix]

My intuition here was that the routing concerns should be "out of scope" of the agent app interactions -- the PIPi itself exists to enable this routing. even in the case where a CB is implementing it themselves around existing internal automation systems (for example an on-prem data or GRC product which doesn't adhere to DRP directly), there's an interface that understands DRP, and there's all the other data systems. I think there's value in coalescing all the things that "speak" the same technical language under the same semantic domain even if under the hood they're operated by different providers. Ultimately, though, I don't think there's a strong technical reason to go with the api_base method except that it makes the spec a bit easier to read ;)

I will bring this up in our technical implementors group though.