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.
Decentralized Data Governance for Data subject’s (data) rights
Uses the definitions and terms specified in the ISO 29100 framework, Consent Receipt v1.2, for specifying key roles for data control, transparency and accountability. This international framework is the basis for extending semantic data governance to decentralized data economy. In this economy, the Privacy Controller Credential extended the Privacy Controller Public Profile for verified claims, decentralized identifiers, and Self Soverign applications. For this purpose, this specification is used to provide the best practices for the data controller to generate a verifiable credential, the considerations in using this as a legal credential for standardized data processing.
The Privacy Controller, the accountable, authorizing stakeholder for data processing is the key audience for this specification and language.
At this time, a high risk, high sensitivity data processing activity, has the responsibility to be transparent over the legal entities responsible for processing personal data, the beneficiaries of the data processing activity, in addition to any othe processors. This includes partners and data processing service providers, like Google or identity management service provider.
This privacy controller profile, printed out in long form would have multiple legal entities and Privacy Controller Credentials required, this would include all of their mailing addresses (by law) and , public contact point/addresses, and the details of any jurisdictional representative for privacy and data protection.
This specification, aims to tease out the language used for specifying these elements, which are legally required to be Public so that they can be represented with a single distributed identifier to simplify each DDE interaction.
Privacy Risk Assurance ;
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 1 - 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
Tier 3 - Very High Risk - invisible public surveillance, surveillance of children /vulnerable people etc 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 The PCC Credential - a single identifier for a Privacy Controller, which links to all LEI's for beneficial ownership.
|Privacy Controller Credential Roles|
|Data Governance Authority Operator Role||Certification Providers on Regulator Approved Codes of Conduct - very limited PII - data controller personal information and a linked reference to a data subjects identifier -|
|Data Governance Registrar||`|
|Stakeholder||Privacy Controller Credential : Creating Credentials for a use Case||Description|
Gov ToiP Role
Actors Privacy Stakeholders
|Provides the schema - hospital||issuer||Privacy Controller|
|Person - Requesting Information from - patient/traveller||holder||Data Subject|
|3rd Party - border control||Verifier||Data Processor / 3rd Party|
Legal Semantic Element
|controller address registered|
|controller address (mailing)|
|controller contact||extend consent termination for a control point|
Delegated Role :
Information technology — Security techniques — Privacy framework
ISO/IEC 29100:2011 provides a privacy framework which
|Status - Is publicly available - https://www.freestandardsdownload.com/iso-iec-29100-2011.html|
|ISO/IEC 29184:2020||Online 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.01||Data Privacy Vocabulary|
|Mapping Governance||Matching with ToiP Governance|
|Risks||Identity and Verifiable Credential Risks|
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]
OPN Privacy Profile URI
Link to the controller's profile in the OPN registry.
Type of Notice Receipt
Label Notice Receipt
A unique number for each Notice Receipt. SHOULD use UUID-4 [RFC 4122].
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).
The Controller’s profile public key. Used to sign notice icons, receipts and policies for higher assurance.
Language in which the consent was obtained. MUST use ISO 639-1:2002 [ISO 639] if this field is used. Default is 'EN'.
The identity (legal name) of the controller.
The jurisdiction(s) applicable to this notice
Contact name of the Controller. Contact could be a telephone number or an email address or a twitter handle.
Link to Notice
Link to the notice the receipt is for
Link to Policy
Method of notice presentation, sign, website pop-up etc
|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