Skip to content
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

Verifying an entity corresponds to a specific Profile #79

Closed
ottonomy opened this issue Sep 7, 2016 · 1 comment

Comments

@ottonomy
Copy link
Contributor

commented Sep 7, 2016

Problem/challenge: Verifying that the entity presenting a badge to you is an entity referenced in the badge is a challenge. This can be done prior to issuing the badge (issuer checks the recipient) when receiving the badge (earner checks the issuer) and post issue (the consumer verifies the recipient and issuer).

Requirement: Profiles must contain properties that are possible to verify through interactive processes that scale. A consumer must be able to verify that a defined Profile corresponds to properties it can trust belongs to a particular entity, whether that is a logged in user, a person, or an organization.

Motivation: To enable a more expressive vocabulary for defining issuers and recipients of badges, the ability to verify different identifying properties of a profile on a broad scale becomes more important.

User Stories:

  1. As a badge consumer, earner, or issuer, I want to verify that a profile truly corresponds to its stated entity so that I can trust badge claims related to that profile.

@ottonomy ottonomy modified the milestone: 2.0 Prototypes Sep 7, 2016

ottonomy added a commit that referenced this issue Dec 31, 2016
Merge in description of endorsement, related examples. Deprecate old …
…endorsement extension #73 #76 #79. (and in my opinion also #83 and #88, though platform support would be required)
@ottonomy ottonomy referenced this issue Dec 31, 2016
@mgylling

This comment has been minimized.

Copy link
Contributor

commented Feb 1, 2017

Closing this issue, as it was resolved by the 2.0 Recommendation. This issue and all other issues resolved by 2.0 can be found via the 2.0 Release Candidate milestone and PR #99.

@mgylling mgylling closed this Feb 1, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
You can’t perform that action at this time.