244
edits
| Line 212: | Line 212: | ||
* Display of badges is where a significant part of the value lies - badges are not siloed or 'stuck' within one site but can be combined with badges from multiple Issuers and then shared out for different audiences/purposes | * Display of badges is where a significant part of the value lies - badges are not siloed or 'stuck' within one site but can be combined with badges from multiple Issuers and then shared out for different audiences/purposes | ||
* Earner will control where badges are displayed through the Backpack | * Earner will control where badges are displayed through the Backpack | ||
* Earner can create groups of badges and share through the Backpack to Displayers that have connected via the Displayer API | * Earner can create groups of badges and share through the Backpack to Displayers that have connected via the [https://github.com/mozilla/openbadges/wiki/Displayer-API Displayer API] | ||
* Earners can also make badges public - in that case, those badges would be discoverable by Displayers if they had the Earner’s email address | * Earners can also make badges public - in that case, those badges would be discoverable by Displayers if they had the Earner’s email address | ||
* At its most basic: if a site has an Earner's email address, they will be able to query the Backpack for all of Earner's public badges. They will get back JSON representation of the badges | * At its most basic: if a site has an Earner's email address, they will be able to query the Backpack for all of Earner's public badges. They will get back JSON representation of the badges | ||
== I. Identity == | == I. Identity == | ||
edits