search

1EdTech / openbadges-specification

Specs related to Open Badges
186 stars 68 forks source link

Data Privacy for Learners #52

Open timothyfcook opened 9 years ago

timothyfcook commented 9 years ago

From @ottonomy on the Standards call on 8/18/2015

What happens to all published badge assertions? Do we want "megacorps" to be able to scoop up all this valuable de-anonymized information about learners and use it for nefarious purposes?

What privacy/security controls can be added to inhibit this?

@ottonomy has an idea here.

timothyfcook commented 8 years ago

@ottonomy says that we should do some discovery to get more information regarding exactly what ways this data might be exploited before we address these issues.

colomet commented 6 years ago

Do open badges specifications follows The EU General Data Protection Regulation (GDPR)?

justinpitcher commented 6 years ago

From my perspective, Open Badges are a specification for describing and encapsulating a standardized record of achievement. How a given platform uses and controls that data (relevant to GDPR) does not fall under the purview of the OB specification.

Or in other words, the specification only describes how to make and verify a badge. It does not say how to store, protect, and control the badge.

That said, the general discussion of best practices has come up within the community including debate as to who owns an assertion. For some of us, we believe the assertion is owned by the issuer as they're the ones making a claim with their name on it. And as such, the earner is not entitled to request it be forgotten, similar to other academic records. There's also the issue of public good and the persistence of credentials. It's an interesting debate to be sure, but GDPR is ultimately outside the scope of this specification.

colomet commented 6 years ago

why not to have a student confirmation about his name in the badge?