[OASIS Issue Tracker] (COEL-165) Correcting data - GDPR review

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/COEL-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=67545#comment-67545 ] 

Paul Bruton commented on COEL-165:
----------------------------------

Suggested text is "...download all data for the Consumer, forget the old Consumer profile, add a new Consumer and upload the corrected data and Atoms."

It is not possible to create a new consumer with the same PseudonymousKey as the old one because the Service Provider has to submit a signed Pseudonymous Key to the Data Engine and the IDA will only create *new* signed PK, not sign old ones. New issue created: COEL-177

> Correcting data - GDPR review
> -----------------------------
>
>                 Key: COEL-165
>                 URL: https://issues.oasis-open.org/browse/COEL-165
>             Project: OASIS Classification of Everyday Living (COEL) TC
>          Issue Type: Improvement
>         Environment: MMI
>            Reporter: Joss Langford
>            Assignee: David Snelling
>
> GDPR requires the the ablity to correct data so I think privacy-by-design requires this to be baked into the standard. We discussed the ability to write a 100% certainty atom to make a correction but what if it is already 100% or we are correcting a correction?
> The other issue area is the segment data that cannot be added/changed after first registration. This is also an issue for people who move home countries.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)