Commit fa911f7c authored by taco@waag.org's avatar taco@waag.org
Browse files

removed redundancy

parent 95e07a91
......@@ -9,7 +9,7 @@ Last year as participant of the [NGI-Ledger](https://www.ngi.eu/ngi-projects/led
This article is a reflection on things we learned during the development of the demonstrator that might apply for future Datacommons projects at Waag.
To begin we'll dive straight into the *use case* that we tried to tackle, because it will give insight into the complexity and sensitivity of many the things that can happen to your data in a very concrete way. This is followed by a reflection on the nature of *genetic data and ownership*. The underlying vision for a distributed *datacommons for genetic data* is laid out, and how the *verifiable credentials* technology could play a key role in this. We then zoom in on the idea of *dynamic informed consent*, and move on to how we fit everything together in *the Geneconsent demonstrator*. We end with a question about what we made with *do we really want this level of control?* and a summary of *future challenges*.
To begin we'll dive straight into the *use case* that we tried to tackle, because it will give insight into the complexity and sensitivity of many the things that can happen to your data in a very concrete way. This is followed by a reflection on the nature of *genetic data and ownership*. The underlying vision for a distributed *datacommons for genetic data* is laid out, and how the *verifiable credentials* technology could play a key role in this. We then zoom in on the idea of *dynamic informed consent*, and how we fit everything together in *the Geneconsent demonstrator*. We end with a question about what we made with *do we really want this level of control?* and a summary of *future challenges*.
## Use case
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment