Badges/infrastructure-tech-docs: Difference between revisions

** '''Badge Manifest''' - User identity information (email address) plus badge information (JSON metadata)

** '''Verified Badge''' - Badges that have been signed by a third party. The Backpack verifies the signature against the signers public key and if confirmed, accepts the badge as a verified badge. The verification information is represented with the badge as a layer of trust on the badges validity.

** '''Unverified Badge''' - A badge that has not been signed by a third party but is issued as flat JSON data. Unverified does not mean invalid, but simply that there is no additional information with the badge to establish an additional layer of trust. Most badges issued into the OBI will be unverified badges.

** '''''Hub''' - The core authorized data store. Each learner has his/her own hub where all badge data is stored. The Hub software will be open source so if a learner wants to install and manage their own hub, and thus completely control all of their credentials, they can. Mozilla will manage the hubs for users who do not install their own''.

** '''Badge Backpack''' - The core authorized data store and management interface. Each learner has his/her own Backpack where all their badge data is stored. Mozilla will host the reference Backpacks, but the infrastructure will allow for users to develop and host their own Backpacks. NOTE: the Hub and Backpack are being combined with new iterations of the development. Each user will have their own Backpack that holds all of their badges and gives them an interface to manage, control and share those badges.

** '''Metadata Spec''' - The definition of what makes up a badge. Each badge is a chunk of metadata that describes the badge, including title, description, issuer, issue date, evidence URL, image, etc. Each issuer will need to conform their badges to the metadata spec for the badges to be accepted into the Backpack. Beyond the technical requirements, the metadata spec is essential for standardizing badges to ensure that badges can be transferred/ported without losing critical information to understand and verify the badge. Beyond the core spec, the metadata is extensible.

** '''Badge Baking''' - Embedding the JSON blob into a PNG file to make a fully robust, portable badge (with all of the metadata embedded)

*** '''Badge Baking Service''' - tool/software to embed the JSON blob in a PNG. Mozilla will build the reference baking service for beta

** '''API''' - The interface specifications for pushing badges into the Backpack (issuers/users), as well as pulling them out (display sites/widgets).

** '''Authentication Channel''' - Communication channels and framework to support badge authentication (was this badge issued to this person on this date? Has it expired? etc.)  

** '''Verification/Endorsement Channel''' - Communication channels and framework to support badge endorsement (was this badge signed? is the signature valid?)

** '''Issuer''' - Organization, consortium or individual who issues badges into the OBI. The OBI is open and supports any independent issuer that conforms to the necessary badge and issuing specifications.

*** '''Issuer Tech''' - Software that supports issuing of badges into the OBI and/or to users directly. The issuer tech must generate the JSON data chunks for each badge, and communicate with the Backpack(s) to pass badge data and authenticate badges. Many issuers will build their own issuer tech, although open generic or technology-specific tools could be built to support a wide range of issuers.

** '''Displayer''' - Website, run by an organization, consortium or individual, that pulls badges from the OBI and displays them for a user. Displayers could range from social networking sites like Facebook or career social networks, to job search/application sites to personal blogs or sites. Each user manages which display sites can access their badges (and which subcollection of badges to display per display site) through the Backpack or directly on their own.

*** '''Widget''' - Software that supports the display of badges on a particular display site. Widgets will communicate with the Backpack to pull badges, as well as utilize the Authentication/Verification Framework to authenticate badges before displaying. For example, one could build a Facebook app that leverages both the OBI API to pull badge data, and the Facebook API to push badges into Facebook.   

** '''Signer/Endorser''' - An organization, consortium or individual who validates a badge by signing it with their private encryption key. Trusted third party signers may emerge.

*** '''Signing Authority''' - A third party that checks signed badges against the signers public encryption key and confirms or rejects verification. Backpack communicates with the signing authority to verify the badge if signing data is included with the badge (otherwise the badge is Unverified).