Jump to: navigation, search


70 bytes removed, 15:43, 11 March 2013
A. Mozilla Open Badge Infrastructure (OBI)
== A. Mozilla Open Badge Infrastructure (OBI) ==
NOTE: The documentation below is for general on-boarding. If you want the more technical documentation - , please see our [ github pages].
==== Why Are We Doing This? ====
* Learners Learning happens everywhere. Yet it's often difficult to be recognized for skills and achievements that are learning everywhere -- but most gained outside of that learning doesnschool. Mozilla't "count"* Skills assessment and communication s Open Badges project is limited in current systemworking to solve that problem by making it easy for anyone anywhere to issue, earn, eand display badges.g. GPAThe results: broad recognition of 21st century skills, GEDunlocking of career and educational opportunities, Bachelor or Master degrees, static resume* There are few alternatives and learners everywhere being able to the current accreditation/credentialing system* Learning doesn’t happen simply between K - 12 level up in their lives and university; learning happens over the course of a lifetime and frequently in informal settingswork.
==== Goals ====
* Develop badges as an a system for alternative accreditation/, credentialing system, and recognition;* Develop Help badges as a micro-accreditation/micro-credentialing system * Avoid silosexpand beyond siloed environments to be broadly shareable; ie badges stuck in one learning system* Truly support learners learning everywhere == Support badges issued from multiple issuers across the Web ;* Optimize the value of those badges == Make by allowing badges to be remixable and shareable with different audiences/sites ;* Develop a supporting infrastructure to standardize the process and support each learner collecting badges from multiple issuers and sharing sub-collections out across various displayers. ;* Create an infrastructure that is open and as decentralized as possible to give learners control and support of the entire ecosystem .
==== Description ====
Enabling learners to earn badges wherever they're learning across the web requires support for multiple individual badge issuers. Empowering learners to use their badges as legitimate credentials requires support for sharing of badges across many display sites. The Open Badges framework is designed to allow any learner to collect badges from multiple sites, tied to a single identity, and then share them out across various sites -- from their , including personal blog or website blogs to social networking profileschannels. It is critical for this infrastructure to be open to give learners control over their own learning and credentials, allow anyone to issue badges, and for each learner to carry the their badges with them across the web Web and other contexts.
=== II. TECH SPECS ===
==== Overview ====
* Issuer issues An issuing organization or individual makes a badge or series of badges available on their site, then website and prompts the Badge Earner their community to push earn them. The earner sends the badge into to their Backpack for portability.** Issuer does The badge becomes portable this through the [ Issuer API] which provides script to present the Badge Earner earner with a modal dialog that requests their consent to add the Issuerissuer's badge(s) to their Backpack.* Issuer can also push badges to the [ Mozilla Baking Service] where the assertion url URL representing JSON blobs is embedded into PNG files** n.b. Only This is only necessary if Issuer the issuer wants the Earner earner to have the ability to store badges outside of the OBI. Otherwise Badge Baking badge baking is handled through the [ Issuer API]. * Displayers pull unpacked badges (JSON) out of the Backpack based on earner action and privacy settings and Earner action. * Public badges are discoverable by Earner’s based on earner’s email address . * Earners can share their badges through the their Backpack, thus granting and grant permission for a particular site to display that set collection of badges . * Displayers authenticate badges with the Issuer using the [ Verification] check.

Navigation menu