Confirmed users
20
edits
Badges/Onboarding-Issuer: Difference between revisions
Jump to navigation
Jump to search
→Adding information about BadgeKit
Jadeforester (talk | contribs) |
|||
| Line 39: | Line 39: | ||
* Earners can share their badges through their Backpack and grant permission for a particular site to display that collection of badges. | * Earners can share their badges through their Backpack and grant permission for a particular site to display that collection of badges. | ||
* Displayers authenticate badges with the Issuer using the [https://wiki.mozilla.org/Badges/Onboarding-Issuer#G._Verification Verification] check. | * Displayers authenticate badges with the Issuer using the [https://wiki.mozilla.org/Badges/Onboarding-Issuer#G._Verification Verification] check. | ||
''BadgeKit, Mozilla's new set of badging tools, can significantly simplify the issuing process - [[Badges/badgekit|Read more about BadgeKit]].'' | |||
=== IV. DEFINITIONS/KEY TERMS === | === IV. DEFINITIONS/KEY TERMS === | ||
| Line 68: | Line 70: | ||
;Endorser | ;Endorser | ||
An organization or individual who “endorses” a badge by signing it with their private encryption key. Trusted third party signers may emerge. | An organization or individual who “endorses” a badge by signing it with their private encryption key. Trusted third party signers may emerge. | ||
;[[Badges/badgekit|BadgeKit]] | |||
A new set of tools to simplify badging for issuers - provides an interface for creating and managing badges/ assessing badge applications. The BadgeKit API lets issuers control interaction with their own community of badge earners. | |||
== B. Issuer == | == B. Issuer == | ||
| Line 91: | Line 95: | ||
*** Issuers must generate public/private key pair and maintain the hosted public key. | *** Issuers must generate public/private key pair and maintain the hosted public key. | ||
*** Issuers must sign the badges themselves, sign the whole package, and push badges to earner backpacks through the Issuer Javascript API. | *** Issuers must sign the badges themselves, sign the whole package, and push badges to earner backpacks through the Issuer Javascript API. | ||
* Issuers looking to use [[Badges/badgekit|BadgeKit]] have a specific range of options and requirements regarding hosting and technical provision - see the following blog post for more information: [http://openbadges.tumblr.com/post/78764181250/announcing-mozilla-badgekit Announcing Mozilla BadgeKit]. | |||
=== III. BADGE CREATION FLOW === | === III. BADGE CREATION FLOW === | ||
| Line 100: | Line 105: | ||
The Issuer API is a script that can be dropped into any badge issuer's website to provide a way for earners to add an issuer's badges to their Backpack or federated backpacks. There's no need to bake the badges independently as the API takes care of this. | The Issuer API is a script that can be dropped into any badge issuer's website to provide a way for earners to add an issuer's badges to their Backpack or federated backpacks. There's no need to bake the badges independently as the API takes care of this. | ||
''The badge creation flow varies significantly for issuers using [[Badges/badgekit|BadgeKit]]. Issuer admins can design and define the data for a badge within the BadgeKit Web app, with BadgeKit handling badge assertions. Issuers can then present available badges to their earners using the BadgeKit API.'' | |||
=== IV. OPEN BADGES Related Widgets created by the community === | === IV. OPEN BADGES Related Widgets created by the community === | ||