-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add trait: GDPR compliance #14
Comments
@fabianekc are there specific features that make a DID method GDPR compliant? The right to be forgotten comes to mind. |
Example definition: {
"gdpr-compliant": {
"type": "boolean",
"title": "GDPR-compliant",
"description": "A DID method's ability to fully adhere to the European Union's General Data Protection Regulation (GDPR) requirements, ensuring comprehensive protection of personal data and individual privacy rights."
}
} |
- cryptography_privacy_preserving: decentralized-identity#16 - cryptography_government-approved: decentralized-identity#15 - gdpr-compliant: decentralized-identity#14
The trait has been added. It's up to the method author to provide detailed information on the compliance. |
In today's call, we concluded that this trait is too difficult to express in a simple boolean value and not technical enough. Therefore, the trait will be removed. |
Yes agreed. As we discussed compliance with data protection can even be altered depending in how the did method is implemented in specific instance. |
In some use cases it is relevant to ensure GDPR compliance for the identifiers used. Therefore, I propose to discuss if this trait makes sense and might be added.
The text was updated successfully, but these errors were encountered: