244
edits
Badges/Onboarding-Issuer: Difference between revisions
Jump to navigation
Jump to search
→C. Badge
| Line 107: | Line 107: | ||
The core currency of exchange. A single credential demonstrating a skill, achievement, quality or affiliation. | The core currency of exchange. A single credential demonstrating a skill, achievement, quality or affiliation. | ||
* Representation - Chunks of JSON data embedded into a PNG file | * Representation - Chunks of JSON data embedded into a PNG file | ||
* Badge Assertion aka Badge Manifest - Earner identity information (<algorithm>$<hash(email + salt)>) plus badge information (JSON metadata) | * [https://github.com/mozilla/openbadges/wiki/Assertions Badge Assertion aka Badge Manifest] - Earner identity information (<algorithm>$<hash(email + salt)>) plus badge information (JSON metadata) | ||
* Verified Badge - Badges that have an assertion URL. OBI currently supports verification of badges through Hosted Assertions. i.e. When Issuer pushes badge to the OBI, metadata is pushed to a unique and persistent url aka assertion url. Issuer maintains Badge Assertion and Displayers can ping the assertion URL to confirm verification. | * Verified Badge - Badges that have an assertion URL. OBI currently supports verification of badges through Hosted Assertions. i.e. When Issuer pushes badge to the OBI, metadata is pushed to a unique and persistent url aka assertion url. Issuer maintains Badge Assertion and Displayers can ping the assertion URL to confirm verification. | ||
** n.b. Signed Assertion is on the development roadmap. | ** n.b. Signed Assertion is on the development roadmap. | ||