Overview  

Decentralized Data Governance for Data subject’s (data) rights

1. A key challenge, which is addressed with an International standards, is the lack of semantic harmonization for personal data control  which provides security for the portability and control of private information and is a required for people to be able to independently consent and control personal information.  This challenge, which was originally championed by  the Open Notice Initiative's Presentation and Paper @ the W3C DoNotTrack Conference in Berkeley California. 'Opening Up the Online Infrastructure' called for collaboration on the semantic standards to be developed. Ultimately realizing that intention data governance standards were needed, and international data governance policy was required to govern between jurisdictions, technical domains, and identity management systems.  It was also abundantly clear, the only legal, and human centric framework for this Internationally, is Notice & Consent.  Notice and Consent, after an exhaustive research campaign, Notice, and semantics are the only consistent legal, technical and socially required component, for all contexts dealing with personal information. 
2.  This turned into a Kantara Specification effort in 2014 and now, last year, ISO voted to fast track this to a standard 27560, to be used with ISO 29184 to address what was know by the  phrased of the Biggest Lie on the Internet, was a focus of a movie Terms and Condition's May Apply. With an international governance rule set, people can use independently of Terms and Conditions. 
3. With the success of this work as an international standard this Task Force aims to collaborate to provide the support an International data governance authority framework as an open resource for master data control of transparency over personal information (with standardized notice).
4. The objectives:
   1. Define the attributes needed for a privacy controller credential to extend ISO standards to SSI, 
   2. Use ANCR to specify notice semantics for specifying  Representatives of the controller
5. Develop a unifying approach for the notice semantics internationally with OCA
   1. Provide a common and simple contribution to a unified notice control language, putting together the semantics to include, legal schema, html schema, Jan-ld schema, for the governance and identity management technology,
   2.  Focus this on the use case to use OCA  for semantic harmonization and Notice and Consent receipts to determine which Data Subjects rights apply to any data processing context, linked to the  data controls as authorized by the Data Subject. 
   3. what's involved:
      1. use/finish the latest Operational Notice & Consent Receipt Specification -Kantara V1.2  that combines the ISO 29100 & 29184 and 27560 -standards comprised of the International privacy security framework (for Soverign data transfer) 
      2. start a generic - unified data control notice schema - mapped to the ISO 29100 framework - 
      3. map/generate a single international baseline overlay - ANCR WG-  ISO 27560 - Notice & Consent Receipt - Record Structure. (click the link for join info)
         

6. Key Points to consider:

   1.  sovereign identity, a data processing activity is based on a data subject’s explicit  or otherwise (human) consent (not internet service /cookie consent),

   2. an individual’s privacy rights need to be extended to proportional digital privacy rights, so an overlay extends the analogue privacy law with a standard digital control semantics with a unified notice control as the language for people to see, understand and control personal data

7. Gaps to cover 
   1. DGA - Architecture
   2. core schema base
   3. what missing in this base? 
      1. Verified Privacy Controller Credential 

   4. Digital Rights usage Challenge

      1. different legal justifications have different rights associated with them.  This makes it very difficult for people and orgs to know what rights apply in any given data control context  - a problem that the can be solved with the use of these standards - 

      2.  e.g. a notice for explicit consent - or legitimate interest?  when does a Data subjects have the right to data portability (Article 20) when is processing is based on consent. When not used on consent- people have  the right to object (Article 21)

      3. the right to withdraw consent may provide a different outcomes - - 

      4. Articles 16 to 20 of the GDPR indicate that (when data processing is based on consent), data subjects have the right to erasure when consent has been withdrawn and the rights to restriction, rectification and access.

Specification Outline

1. Overview of (OPN) Data Governance Authority Architecture:
   1. Intro
      1. This data governance authority architecture provides the international legal roles for  
   2. Data Governance Roles
      1. Policy Controller, Privacy (Data) Controller, Registration Authority, DGA - Registrar 
   3. Privacy Risk Assurance Levels 1-4
      1. Policy Controller, Privacy Controller, Data/Identity Governance Authority Operator (DGAO)
         1. Policy Controller ( or just Controller) - Tier 1 Assurance - Self Asserted Binding  -No Privacy Risk Assurance 
         2. Privacy Controller (or  Data Controller) - Tier 2 Assurance - Signed Binding for Legal Compliance - Mitigated Risk Assurance
         3. Data Governance Authority Operator - Tier 3 - Assurance - High Risk Assurance 
         4. Registrar - Tier 4 - Registrar Infrastructure - 
            1. Low Risk Personal Data Processing - 
               1. only personal information of Controller, and Company Operators
2. Privacy Controller credential 
   1. Overview:  a Privacy Controller Credential is comprised of a bound relationship 
      1. Accountable Person + Legal Entity Identifier
         1. Legal Status of Accountable person and Legal Entity 
         2. Wether the Accountable person is employed by Legal Entity, or 3rd Party 
            1. if 3rd Party - Privacy Controller Credential of 3rd party is required
      2. Conditions of access and use
         1. the accountable person info should be masked unless required (not published as is required in some jurisdictions) 
3. Use Case(s) Use Cases 
   1. Digital Immunisation Passport
      1. Holder, Verifier & Issuer
   2. Call for use cases.

Unified Notice Control Language for Semantic Harmonization 

For UNCL:

Uses the definitions and terms specified in the ISO 29100 framework, Consent Receipt v1.2, specifying key roles - the  aim is to start a specification with the key roles specified for data control, transparency and accountability as the starting point.  And to start with the basis for a semantic data governance framework, in which the Privacy Controller Credential is used to extend the data controller role to a verifiable credential, usable as a legal credential for standardized data processing profile.  The Privacy Controller, the key authorizing stakeholder for data processing, and to represent this in the.  standards and references for legal governance, and to currate a list of proposed (new terms/elements to explore) 

At this time, a privacy controller credential written out in long form, might have multiple legal entities and Privacy Controller Credentials required, this would include address, public contact points and can be a very long document.  These elements which are found in a Public Privacy Profile can be represented with a single distributed identifier from the registrar, available via api and simplify each  DDE interaction. 

Privacy Risk Assurance ;

• refers to trustworthy transparency 
  • e.g does this organization use of standardized legal semantics for notice and consent to ease understanding

Requirements Privacy Controller Credential Specification (in Open Consent Groups' OPN Architecture)

Providence  chain starts with the person who is accountable bound to a legal entity. 

Legal Entity Accountability Levels according to Tiers of Privacy Risk

Tier 0 - is self asserted controller (not a verified privacy controller) even in the ICO Controller Registry - No-Risk Indicated :  Self Asserted Binding  with a privacy policy - providing minimum Privacy Risk Assurance (trustworthy Transparency)

Tier 1 -  Privacy Policy Controller - Low Risk - doesn't process personal data electronically, does not collect or process personal information, and for any personal identifier, this is minimized and secure, has internal security for data of employee's

Tier 2 -  Privacy (data) Controller - Does process personal data for commercial benefit and use with low risk services - (employee privacy ) Tier 2 - High Risk Privacy - identity management, any special/sensitive personal data category - (see personal data categories)

Tier 3 - Very High Risk - invisible public surveillance, surveillance of children /vulnerable people etc - .  Beneficial   Beneficial owners (required) 

Tier 4 - Controller Operator - Provides Registration services for Privacy Controller Credentials, Mitigates Privacy Risk with codes of conduct and certifications that accredit codes of practice.  Controller can then register to these codes of conduct and practice 

Use's of Credential Objective - for a credential  to provide a single identifier for a Privacy Controller, which links to all LEI's for beneficial ownership. 

• Simplify Transparency 
• Improve performance 
• Sign Receipts to create tokens
• Provides 
  • Privacy - Transparency over legal entities, accountable people and beneficial - 
  • Legal Entity
  Identifier 
  • Identifier Purpose and Sources
    • to identify the legal entity of the privacy controller 
    • beneficial owner of the legal entity 

• Accuntable Accountable Person Role
  • to identify the accountable person / role that is bound to the legal entity identifier (aka) organization. 
    • could be an employee
    • owner / director / officer 
    • data proaction officer 
    • 3rd. Party Company Representative 
      • accountable role - (for another 3rd Party) acting representative 
• Privacy Controller 
  • under what authority 
  • under what legal justification 

ISO 29100

...

Privacy Stakeholders

(Note: In progress - consulting with Steven on auto filling) 

...

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

Topic List

References

Reference Implementations

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]

...