You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following introduction of a LegalEntity asset to address PRiAM requirements, we need to either restrict relationship domains or ranges to LegalEntity assets where appropriate, or add modelling error threats that detect (and suggest how to resolve) situations where a non-legal entity is involved inappropriately in such a relationship.
This may form part of an update to the GDPR submodel, where the relationship specifying a data controller may need to be replaced by a new set of relationships that distinguish data controllers, data processors and their relationships.
The text was updated successfully, but these errors were encountered:
Following introduction of a LegalEntity asset to address PRiAM requirements, we need to either restrict relationship domains or ranges to LegalEntity assets where appropriate, or add modelling error threats that detect (and suggest how to resolve) situations where a non-legal entity is involved inappropriately in such a relationship.
This may form part of an update to the GDPR submodel, where the relationship specifying a data controller may need to be replaced by a new set of relationships that distinguish data controllers, data processors and their relationships.
The text was updated successfully, but these errors were encountered: