Use Cases   

Data Governance: Data subject’s (data) rights

1. A key challenge and semantic at the core of self Soverign and privacy is that security and privacy is found in the lack of semantic harmonization for personal data control  which provides security for the portability of private information is required upfront.  If people are self-sovereign this information needs to be discoverable and useable by default  
   1. to address this issue a unified data control vocabulary extends the notice control language which can be used to address harmonisation of  the notice to indicate which Data Subjects rights to data controls that can be used for legal data controlsapply to which context, and which  data controls are authorized to be  used by the Data Subject. 
   2. whats 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 legal overlays for this core overlay to Create an OCA test schema framework. 

2. 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 the unified data control.  This requires a legal (computational law) use case to illustrate (action for Mark Lizar

   3. 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.

3. Gaps to cover 
   1. core schema base
   2. what missing in this base? 
      1. Verified Controller Credential 

Unified

...

Notice Control Language for Semantic (inputs)

For UNCL - the aim here  aim is to collect start a specification with the key roles specified for data control, transparency and accountability as the starting point for standards .  And to start with 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) For Example: 

Privacy Controller Credential 

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

ISO 29100 Actors

(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

...