Skip to content

Commit

Permalink
Remove broken references to other chapters
Browse files Browse the repository at this point in the history
Signed-off-by: George J Padayatti <[email protected]>
  • Loading branch information
georgepadayatti committed Jun 15, 2022
1 parent 19e5279 commit fbc9d2b
Show file tree
Hide file tree
Showing 2 changed files with 0 additions and 15 deletions.
10 changes: 0 additions & 10 deletions docs/data-agreement-specification.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,16 +32,6 @@ This specification describes how a Data Agreement between an organisation and in

In order to create the Data Agreement, and the resulting receipt as proof, a number of steps are required from different actors. This document describes these steps involved and is described as part of a Data Agreement lifecycle.

This specification is published together with an Interface Specification [1] and a DID Method Specification [2]. For details of the DID Method and Interface Specification please refer to these reference documents.The communication between the actors will be based on DIDComm.

This chapter provides an introduction to Data Agreement and elaborates on the concepts and terminology included in any kind of personal data usage by an organisation.

Chapter 2 provides a functional overview of Data Agreements. It also describes the interworking of various actors in the Data Agreement lifecycle.

Chapter 3 provides a list of references.

The Appendix provides additional details that includes Data Agreement Schema (Appendix A), how a DPIA report maps to a Data Agreement (Appendix B) and details on the various input standards used in the proposed Data Agreement Schema including the Kantara Consent Notice, ISO standards etc (Appendix C).

## Abbreviations

| Abbr | Expanded form |
Expand Down
5 changes: 0 additions & 5 deletions docs/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -73,11 +73,6 @@ <h2 id="abstract"><a class="toc-anchor" href="#abstract" >§</a> Abstract</h2>
<h1 id="introduction"><a class="toc-anchor" href="#introduction" >§</a> Introduction</h1>
<p>This specification describes how a Data Agreement between an organisation and individual is managed in order to capture, in a receipt, the conditions of processing of personal data. The receipt acts as evidence and demonstrates a higher level of accountability and is based on standard schemas. The accountability is further enhanced by directly integrating the Data Agreement with the input from a risk assessment, e.g. Data Protection Impact Assessment.</p>
<p>In order to create the Data Agreement, and the resulting receipt as proof, a number of steps are required from different actors. This document describes these steps involved and is described as part of a Data Agreement lifecycle.</p>
<p>This specification is published together with an Interface Specification [1] and a DID Method Specification [2]. For details of the DID Method and Interface Specification please refer to these reference documents.The communication between the actors will be based on DIDComm.</p>
<p>This chapter provides an introduction to Data Agreement and elaborates on the concepts and terminology included in any kind of personal data usage by an organisation.</p>
<p>Chapter 2 provides a functional overview of Data Agreements. It also describes the interworking of various actors in the Data Agreement lifecycle.</p>
<p>Chapter 3 provides a list of references.</p>
<p>The Appendix provides additional details that includes Data Agreement Schema (Appendix A), how a DPIA report maps to a Data Agreement (Appendix B) and details on the various input standards used in the proposed Data Agreement Schema including the Kantara Consent Notice, ISO standards etc (Appendix C).</p>
<h2 id="abbreviations"><a class="toc-anchor" href="#abbreviations" >§</a> Abbreviations</h2>
<table>
<thead>
Expand Down

0 comments on commit fbc9d2b

Please sign in to comment.