Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Notice & Consent for people relies on clear communication. 

Decentralised identity relies on legal semantics to express technical semantics that mirror the same clarity. 

As there are no standardised semantics this presents a challenge.  This work is a call to action for a Unified Personal Data Control Semantics, that extend data control vocabulary ( mapped legal ontology) with decentralised legal semantics.  


Notice & Consent Task Force 

Project owner:

Mark Lizar Salvatore D'Agostino

Team members:


Status

ACTIVE 


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 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 Data Subjects rights to data controls that can be used for legal data controls
    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 Personal Data Control Vocabulary & Semantics (inputs)

the aim here is to collect the starting point for standards and references for legal governance, and to currate a list of proposed (new terms/elements to explore) 


For Example: 

Legal Semantic Element 

semantic description

functional usage

fields Required


controller 


    
controller_identity








controller address registered



controller address (mailing)








controller contactextend consent termination for a control point



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]


Field Name

Field Label

Format

Description 

Required/Optional

Schema Version

version

string

The version of specification used to which the receipt conforms. To refer to this version of the specification, the string "v1" or the IRI "https://w3id.org/OPN/v1" should be used.

Required

OPN Privacy Profile URI

profile

string

Link to the controller's profile in the OPN registry. 

Required

Type of Notice Receipt

Notice Receipt

string 

Label Notice Receipt 

Required

Receipt ID

id

string

A unique number for each Notice Receipt. SHOULD use UUID-4 [RFC 4122].

Required

Timestamp

timestamp

integer

Date and time of when the notice was generated and provided. The JSON value MUST be expressed as the number of seconds since 1970-01-01 00:00:00 GMT (Unix epoch).

Required

Signing Key

key

string

The Controller’s profile public key. Used to sign notice icons, receipts and policies for higher assurance.

Optional

Language

language

string

Language in which the consent was obtained. MUST use ISO 639-1:2002 [ISO 639] if this field is used. Default is 'EN'.

Optional

Controller Identity

controllerID

string

The identity (legal name) of the controller.

Required

Legal Jurisdiction

jurisdiction

string

The jurisdiction(s) applicable to this notice

Required

Controller Contact

controllerContact

string

Contact name of the Controller. Contact could be a telephone number or an email address or a twitter handle.

Required

Link to Notice

notice

string

Link to the notice the receipt is for 

Optional

Link to Policy

policy

string

Link to the policies relevant to this notice e.g. privacy policy active at the time notice was provided

Required

Context

context

string

Method of notice  presentation, sign, website pop-up etc

Optional

Receipt Type

The human understandable label for a record or receipt for data processing.  This is used to extend the schema with  profile for the type of legal processing - and is Used to identify data privacy rights and controls 

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) 

Privacy Stakeholders

ISO Definition


Regulator

PII Principal

PII Controller

PII Processor

3rd Party

    


Gov ToiP Role

Legal Receipt Type for action or event

Actors 



issuer 


holder


Verifier 


Delegated Role :




Delegated 

Regulator

Ombudsman
PII Principal

Guardian
PII Controller

Joint-Controller
PII Processor

Sub-Processor
3rd Party

turtles 

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

Standard/Specifications

Title

Description 

Resource Status

ISO 29100

Information technology — Security techniques — Privacy framework

ISO/IEC 29100:2011 provides a privacy framework which

  • specifies a common privacy terminology;
  • defines the actors and their roles in processing personally identifiable information (PII);
  • describes privacy safeguarding considerations; and
  • provides references to known privacy principles for information technology.
Status - Is publicly available - https://www.freestandardsdownload.com/iso-iec-29100-2011.html
ISO/IEC 29184:2020Online privacy notice and consent
(just published - not available to public - we are working on publishing a report/appendix for use with this group )
W3C DPV  0.01Data Privacy Vocabulary
  • legal ontology for technically breaking down and mapping legal ontology to a data legal ontology - 
  • the Notice +  CR V1.2 and W3C DPV, also use a common set of purpose categories. and the Kantara CR v1.1 for purpose specification
  • (note shared by initial FIHR approach - now much more evolved) 

Topic List

Topic Title 



Risks

Mapping Governance Matching with ToiP Governance 



References

Reference Implementations

Implementer




Human Colossus 


OpenConsent


I_Grant


  • No labels