Notice & Consent for people relies on clear communication.Decentralized identity relies on legal semantics to instruct the scope of technical semantics. Legal semantics for data control (that people can see and expect in person) are mirrored to provide data governance that people expect with the use of identifiers and claims online. Identity and traditionally data governance referring explicitly to control the flow of data in between domains and borders. Specification work Proposed for to extend international Decentralized Semantic Governance for the DDE.
| StatusACTIVE | |
Decentralized Data Governance for Data subject’s (data) rights. For people to find technology trustworthy, and to be able to use digital identity to control perosonal data in a way we trust, people need transparency over the security and privacy of the use of their identity and personal data after it is provided. They need to be able to see the privacy and security risks. In fact as a parent, this is legally required, in order to consent for them collection, use and surveillance of children's data and identifiers.
The lack of standardized legal semantics for Digital identity and personal (Transborder) data management presents a challenge for identity management technologies and protocols. This task force mission is to extend international identity governance standards to the SSI space with this specification for a privacy controller credential and the Unified Notice Control Language.
The Identity and Data Governance Stack of Specifications used to create this specification are designed to utilize OCA to overlay legal notice and consent schema's on to the existing ISO/IEC 29100 framework for jurisdictional privacy/surveillance notice profiles.
Then to enable identity governance interoperability by translating a local governance schema to the internationalized schema base for governance controls and privacy rights. Then, to overly the next schema for localized identity and data governance controls, which utilized the same surveillance and privacy semantic governance framework for identity and data control interoperability.
In this process the OCA utilizes this stack of standards and specifications to syncratically harmonize purpose driven interoperability for meta-data and identity governance (by extending International standards)
The Stack
UNCL:
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.
Key Problem>
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 0 - No-Risk Indicated : Self Asserted Binding with a privacy policy - providing minimum Privacy Risk Assurance (trustworthy Transparency)
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 Stakeholders | ISO Definition | |
---|---|---|
Regulator / | ||
PII Principal | ||
PII Controller | ||
PII Processor | ||
3rd Party |
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 | |
---|---|---|---|
Issuer | |||
Holder | |||
Verifier |
Gov ToiP Role | UseCase Example | Roles | 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 | semantic description | functional usage | fields Required | |
---|---|---|---|---|
controller | ||||
controller_identity | ||||
controller address registered | ||||
controller address (mailing) | ||||
controller contact | extend 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 |
Standard/Specifications | Title | Description | Resource Status |
---|---|---|---|
ISO 29100 | 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 |
|
|
Topic Title | ||
---|---|---|
Risks | ||
Mapping Governance | Matching with ToiP Governance | |
Topic | Link | |
---|---|---|
Risks | Identity and Verifiable Credential Risks | |
Implementer | |||
---|---|---|---|
Human Colossus | |||
OpenConsent | |||
I_Grant |
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 | 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