Design Requirement
The prototype must be decentralized and may not rely on trustees.
01
Producer metadata and the represented concept document.
Concept identity
design-knowledge/forgetting-blockchain-gdpr-dr5design-knowledge/forgetting-blockchain-gdpr-dr5.mdThe prototype must be decentralized and may not rely on trustees.
This design requirement is proposed by Design of a forgetting blockchain: A possible way to accomplish GDPR compatibility (Simon Farshid, Andreas Reitz, Peter Roßbach, 2019).
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.
Derived heading context: Source paper
Derived heading context: Addresses
04
One-hop by default, with an optional bounded two-hop view. Nodes are concept files and arrows are Markdown links.
3 of 3 concepts · 5 directed relationships
05
The complete producer frontmatter, serialized without server paths or runtime data.
{
"type": "design-requirement",
"title": "DR5 - Decentralization without trustees",
"description": "The prototype must be decentralized and may not rely on trustees.",
"resource": "https://hdl.handle.net/10125/60145",
"source_paper": "Design of a forgetting blockchain: A possible way to accomplish GDPR compatibility",
"label": "DR5",
"tags": [
"forgetting-blockchain-gdpr",
"design-requirement",
"gdpr-privacy",
"blockchain-architecture",
"data-deletion",
"right-to-erasure"
]
}