Closed gjwgit closed 1 year ago
The current app encrypts fields within the ttl file.
This achieves a good level of privacy protection however adds complexity, in needing each field to be decrypted one by one.
A possibly more convenient approach could be to encrypt the whole ttl file. The whole file is loaded to app and then decrypted there.
This might put all surveys into a single file, or each survey is a separate encrypted file, though then the file names (timestamps) leak information.
So that we can use other tools to decrypt the file in one go, if the key is known, for convenience.
It might also be better for RDF validation more easily, which relies on the URIs for validation.
@onionoino to estimate effort required and then decide if to proceed.
Encrypted predicate and object might be the best approach, as you have it now. Let's go with that.
Description
The current app encrypts fields within the ttl file.
This achieves a good level of privacy protection however adds complexity, in needing each field to be decrypted one by one.
A possibly more convenient approach could be to encrypt the whole ttl file. The whole file is loaded to app and then decrypted there.
This might put all surveys into a single file, or each survey is a separate encrypted file, though then the file names (timestamps) leak information.
Why
So that we can use other tools to decrypt the file in one go, if the key is known, for convenience.
It might also be better for RDF validation more easily, which relies on the URIs for validation.
Close Criteria