Executive Summary 

• The  privacy for surveillance controller credential is the digital version of an organization's privacy and surveillance notice and related default identification.
• Rather than analogue identification - company identity, company address, company phone number, the controller credential contains the digital version of this information and privacy contact point for exercising data control for privacy rights. 
  • The point where a valid state of consent can be assured with a proof of notice and a record of consent.
• The aim of this specification is to implement related standards and specification for different measure of privacy assurance in accordance with the principles of operational privacy and provides a data control risk impact assessement.
• At its core, the privacy controller credential is a security and rights record that among things can be used for indepent access to rights and controls in context of decentralized use of identifiers.

Introduction

In privacy regulations globally the notice and notification requirements in legislation are the most consistent across jurisdictions. In all regulations the identity of the PII Controller is required to be provided to the person before, at the time, or as soon as possible, when processing personal information. 

This specification uses ISO/IEC standard semantics to generate a controller notice receipt for each digital identifier based relationship, and in doing so implement privacy rights to control the use of the personal information related to the identifier(s). 

This specification also addresses security as a part of privacy (there won't be any "considerations" at the end). Current security approaches tend to look at privacy risk less wholistically. This specification addresses this key, no pun, security challenge - for example effectively KYC enhanced with a new authorization flow that that reflects - KYB - know your business from a human perspective (with whom does the identifier have a relationship).  Examples include:

• Verifying people for service use as security focus 
• Verfify their privacy controller credential and use privacy law for defining purpose specific services
• Using an open standards framework (an appendix to this specification, e.g. ISO 29100, Kantara Notice and Consent Receipts, W3C Vocabulary for Notice and Notifications ( text which fills the receipt fields).

• Operational Privacy (Identity and Security) (Engineering) Design Principles
  • Principal  of  "Transparency, Proportionality, and Control Reciprocity - Dynamic Data Controls"
  • Next steps toward this (outside this specification)

• Code of Conduct and Practice (Ethical Operation)
• Must have a receipt (with operational Privacy Controller Credential) to engage in the Dynamic Data Control ecosystem, aka dynamic data economy, from a privacy rights and self-soveign data control perspective.
• 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

Applying /mapping ToiP Governance Model to international framework: 

• 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? 

Delegated Role :

References for use for creating a Unified (generic) Data Control Vocabulary for OCA

Reference: OPN-Notice Schema

OPN: Open Notice  (+ Consent) Receipt Schema: Starters Guide to Unified Data Control Schema

Lizar, M. & Pandit, H.J., OPN: Open Notice Receipt Schema, 14th International Conference on Semantic Systems (SEMANTiCS 2019), Karlsruhe, Germany, 2019 [Published http://www.tara.tcd.ie/handle/2262/91576 [accessed July 1, 2020]

OCA schema specification: https://docs.google.com/spreadsheets/d/1KOdq8Yy3OXmuELyh7tpHMlhyMZPSZ3Ib/edit#gid=68769926