Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Process in progress:

  1. Updated Jan 6
  2. [Proposed] Update to TF Objectives 
  3. Technical Discussion Points 
    1. Linking Records 
    2. Providence Fields
      1. Beneficial Owner
        1. Owner Agreement
  4. Discussion Papers
    1. Decentralized Data Governance 

Notice & Consent Task Force 

Project owner:

Mark Lizar 

Team members:

Salvatore DAgostino

Status

ACTIVE 


Spec Dev Link


Specification proposal:  to extend Decentralized Semantic Governance for a  

Define the assurance required to extend decentralized semantic governance for dynamic data controls ( DDC) to support privacy and trustworthy/regulated/surveillance architectures.   a:

  • Privacy Controller Credential 

...

This credential is comprised of the legal entity name and accountability profile as specified by regulation utilizing ISO/IEC 29100 Privacy & Security Techniques.  Which is an open  An open (no-fee, no barrier) and international standard in from ISO (International Standards the Internationational Organization for Standardization) and the IEC (International ElectroTechnical Commission).   The use of this standard for the creation of records and receipts is critical for scaleable and interoperable Decentralized Data Governance interoperability between technical domains and legal jurisdictions.

...

This specification is for the regulation and governance of surveillance and digital identity technology independently of any (including SSI) digital identity management (digital digital identifiers or trust frameworks).  The objective is for the this specification to work with and enhance digital surveillance assurances already provided by work in ToiP.  Used already to benchmark   The credentialling process benchmarks the privacy, security and compliance of digital identity technologies with international standards.

The aim of this task force outputs is to create a specification and by so doing implement ISO/IEC international standards to enable regulatory interoperability with human controls and transparency that scale for any authorized surveillance context.  To do this, this effort builds upon standards, incorporating additional technical specifications in order to support ToiP community efforts.  

Challenges being addressed with the PCC specification have been raised in the Kantara ANCR WG, W3C DPV CG, ISO/IEC 27560 Technical Committee's, CIO Council, DIACC Special Interest Group, IETF GNAP,  and VC's with DiD's.  The overarching objective is therefore to provide a specification  that supports these working community efforts.  

  1. The accountable person may or may not be an employee of the organization. 
  2. Different jurisdictions name/define and reference this role differently 
  3. Some jurisdictions, like the UK have a data controller registry (DCR), where this binding is public and legally required (benefit in this case, challenge where absent) and the name of the accountable person is publicly available in ICO DCR.  (using blinding identity taxonomy)
  4. Some jurisdictions, like the EU require an accountable data controller representative in the jurisdiction where a service is operating, in order to address legal data privacy and security issues that may arise. 
  5. 2 or more Controllers might be accountable for processing of personal data.
    1. Identify in context of service for any user the controller and accountable person.
  6. The privacy law in some jurisdictions, can itself break privacy law in other jurisdictions by requiring the accountable person information to be published publicly, 
  7. Specifies how to by axquire a VC (in this case the Privacy Controller Credential) for trust assurance for privacy assurance
  8. International Notice & Control protocol for  Unified Data Control & Portable Gap of an international notice & control protocol and semantics for governance interoperability between domain domains and jurisdictions.

Specification Objective

  1. Develop an extensible controller credential format.

The specification shall providprovide

  • a record format that MUST blind the identity of the accountable person,
  • be usable as a linked data in a notice of control receipt, which provides only the controller information required for the purpose of credential use. 
  • record , so as to and provide a profile of the bound controller credentials in a manner that can show the controlling person before, during and after the use of a decentralized digital identifier.
  • control providence that begins with the person making the assertion to the accountable role using laws and standards to bind privacy rights request to a legal entity.

...

Decentralized Data Governance is the focus of the first Discussion Paper, which aims to look at the overlaps of digital identity surveillance technology and regulator led (regulatory) data governance. This is import to specify why certain standards are This will present the overall architecture and the contribution of certain standards used in the credential, as well as how digital identity specifications and protocols can be deployed to implement decentralized data governance.

...