Design Principle
Differentiate the aims of data processing, since different anonymization techniques allow proving data integrity or computational integrity.
01
Producer metadata and the represented concept document.
Concept identity
design-knowledge/yes-i-do-gdpr-dp3design-knowledge/yes-i-do-gdpr-dp3.mdDifferentiate the aims of data processing, since different anonymization techniques allow proving data integrity or computational integrity.
This design principle is proposed by Yes, I Do: Marrying Blockchain Applications with GDPR (Benjamin Schellinger, Fabiane Voelter, Nils Urbach, Johannes Sedlmeir, 2022).
02
Concepts connected by incoming or outgoing native Markdown links.
03
Directed links from Markdown. Heading context is displayed as derived metadata, not as a formal OKF predicate.
04
One-hop by default, with an optional bounded two-hop view. Nodes are concept files and arrows are Markdown links.
2 of 2 concepts · 2 directed relationships
05
The complete producer frontmatter, serialized without server paths or runtime data.
{
"type": "design-principle",
"title": "DP3 - Differentiate aims of data processing",
"description": "Differentiate the aims of data processing, since different anonymization techniques allow proving data integrity or computational integrity.",
"resource": "https://hdl.handle.net/10125/79900",
"source_paper": "Yes, I Do: Marrying Blockchain Applications with GDPR",
"label": "DP3",
"tags": [
"yes-i-do-gdpr",
"design-principle",
"gdpr-privacy",
"energy",
"compliance",
"framework"
]
}