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

« Previous Version 8 Next »

Notice & Consent for people relies on clear communication. 

Decentralized identity relies on legal semantics to express technical semantics that are mirrored to provide data governance that people expect.  Data governance referring explicitly to the transborder use of personal information and personal identifiers.

As there are no standardized legal semantics for Digital identity and personal Transborder data management presents a challenge.  This work aims to develop a Unified Notice Control Language, that utilizes the OCA and the W3C  Data Control Vocabulary ( mapped legal ontology) to harmonize decentralized legal semantics, utilizing the  International Kantara Notice & Consent Receipt specifications (now in WD2 ISO 27560) and ISO 27984. Online Privacy Notice and Consent standard. 

Notice & Consent Task Force 

Project owner:

Mark Lizar Salvatore D'Agostino

Team members:

Ken Adler


Status

ACTIVE 


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 International data governance framework as an open resource for master data control of personal information.
  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.

  8. Use Cases 
    1. Digital Immunisation Passport
      1. Holder, Verifier & Issuer
    2. Call for use cases.

Unified Notice Control Language for Semantic Harmonization 

For UNCL - 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 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) 

Requirements Privacy Controller Credential Specification

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 

Tier 1 -  Privacy Controller - 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 owners (required) 


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

  • Privacy - Transparency over legal entities, accountable people and beneficial - 
  • Legal Entity Identifier 
    • to identify the legal entity of the privacy controller 
    • beneficial owner of the legal entity 
  • Accuntable Person
    • 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 Actors

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



Data Governance Authority /


 Certification Providers on Regulator Approved Codes of Conduct  - very limited PII - data controller personal information and a linked reference to a data subjects identifier -

Privacy Stakeholders

ISO Definition


Regulator / 

PII Principal

PII Controller

PII Processor

3rd Party

    

Roles for CredentialsDescription 
Issuer 

Holder

Verifier 


Gov ToiP Role

UseCase Example 

Roles

Actors Privacy Stakeholders 

  • controller, processor, subject, 3rd Parties


Provides the schema - hospital issuer Privacy Controller 

Person - Requesting Information from - patient/traveller holderData 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 contactextend consent termination for a control point



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


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

  • No labels