Must have a receipt (with operational Privacy Controller Credential) to engage in the Dynamic Data Control Ecosystem from a privacy rights and self-soveign data control
Privacy Controller Credential is used to automate purpose driven online services, to enhance or even replace federated identity systems with self-sovering identity governance

ISO 29100 Privacy Stakeholders

Privacy Controller Credential Roles
Data Governance Authority Operator Role	Certification Providers on Regulator Approved Codes of Conduct - very limited PII - data controller personal information and a linked reference to a data subjects identifier -
Data Governance Registrar	`

Applying /mapping ToiP Governance Model to international framework:

Stakeholder	Privacy Controller Credential : Creating Credentials for a use Case	Description

	Issuer
	Holder
	Verifier

Gov ToiP Role

UseCase Example

Roles

Actors Privacy Stakeholders

Provides the schema - hospital

issuer

Privacy Controller

Person - Requesting Information from - patient/traveller

holder

Data Subject

3rd Party - border control

Verifier

Data Processor / 3rd Party

looking to make a process for what Legal Privacy Stakeholder has the Credential Role
- Steps to assign Stakeholder Roles
  - Test for checking if its a processors or a 3rd party?

Legal Semantic Element	semantic description	functional usage	fields Required
controller
controller_identity

controller address registered
controller address (mailing)

controller contact	extend consent termination for a control point

Delegated Role :

Space shortcuts