The relationships field is a useful addition as some covered businesses have a very different set of relationships with data subjects. Ideally, however, the actions should be nested inside the relationships because they might vary. To give an example, we have multiple different types of erasure available to NYT subscribers, but that distinction will make no sense for the Store; or some relationships might have meaningful portability or DNS rights, whereas others don't. Most of these relationships also have completely different identifiers.
The relationships field is a useful addition as some covered businesses have a very different set of relationships with data subjects. Ideally, however, the actions should be nested inside the relationships because they might vary. To give an example, we have multiple different types of erasure available to NYT subscribers, but that distinction will make no sense for the Store; or some relationships might have meaningful portability or DNS rights, whereas others don't. Most of these relationships also have completely different identifiers.