Jump to: navigation, search


1,019 bytes added, 16:56, 19 March 2014
Adding information about BadgeKit
* 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 [ Verification] check.
''BadgeKit, Mozilla's new set of badging tools, can significantly simplify the issuing process - [[Badges/badgekit|Read more about BadgeKit]].''
An organization or individual who “endorses” a badge by signing it with their private encryption key. Trusted third party signers may emerge.
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 ==
*** 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 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: [ Announcing Mozilla BadgeKit].
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 ===

Navigation menu