Badges/infrastructure-tech-docs: Difference between revisions

''Description'' <br>

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 personal blog or web site to social networking profiles. 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 badges with them across the web and other contexts.

'''TECH SPECS'''

* Badges are represented by JSON data blobs embedded in PNG files in the Backpack

* Identity management is handled by the Mozilla Verified Email ID specification

''DEFINITIONS'' <br>

** '''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).

'''WHAT MOZILLA IS BUILDING'''

''Diagram'' <br>

[[media:https://wiki.mozilla.org/images/a/aa/Open_Badges_--_tech-diagram-_2.2.jpg|https://wiki.mozilla.org/images/a/aa/Open_Badges_--_tech-diagram-_2.2.jpg]] <br>

'''Backpack + ''' <br>

* User can share badges through the Backpack, thus granting permission for a particular site to display that set of badges

* Displayers authenticate badges with the issuer using the Authentication Channel

'''METADATA SPEC'''

Used to test the sending of your JSON blobs to Mozilla <br>

http://brianlovesdata.github.com/openbadges/validator/

'''PNG FILES / BADGE BAKING''' <br>

* PNG files will be unpacked in the Backpack where each user can view, manage and organize their badges (and see all the metadata behind each badge)

* PNG files will be unpacked for the displayer API so that displayers will just have the raw data to work with on their end.

'''BADGE IMAGE STANDARDS'''

* When a badge is displayed, it will be loaded from the Mozilla cache to avoid extra burden on the issuer servers, also in case the issuer is not available or link is broken

* Note: this is under consideration. Since the JSON is now embedded in the PNG file, we might not need this cache

'''ISSUE REQUIREMENTS / WHY & HOW TO BECOME AN ISSUER''' <br>

NOTE: We have an example of issuer tech, built in python with the alpha version of the infrastructure in early July. This code is available for partners to explore/utilize for their own issuing: https://github.com/brianlovesdata/django-obi. We will also provide some assistance for beta partners if needed. This needs updating based on the new manifest changes - will be updated after 9/15

'''DISPLAY REQUIREMENTS / HOW TO BECOME A DISPLAY SITE'''

* Parchment - badges alongside formal education credentials

* LinkedIn - badges included on the career profile

'''IDENTITY''' <br>

* We will roll in future versions of Verified Email Identity as Mozilla Labs releases them

''Functional Flows'' <br>

#** Bad issuers may "copy" another badge but it will be easy to spot

#** Artifact contains FQDN.

'''USER BACKPACK CREATION/REGISTRATION''' <br>

''Backpack registration''

* Issuers do not need to register with the OBI - they simply push badges to the baking service

'''BADGE AUTHENTICATION''' <br>

# 2. Display site uses the Authentication Channel to communicate with the issuer to confirm that this badge was in fact issued to this user on this date, as well as if the badge has expired, needs updating, etc.

# 3. If authenticated, displayer shows the badge. If not authenticated, displayer should reject the badge.

'''BADGE ENDORSEMENT (SIGNING / VERIFICATION)''' <br>

# 5. If confirmed, Backpack accepts the badge. If unconfirmed, Backpack rejects badge.

'''DEVELOPMENT ROADMAP'''

* '''Beta''' - The beta version of the infrastructure will be launched early September 2011. The beta will be a fully functioning (critical feature) infrastructure, including all Backpack technology, launched with an initial set of partners. We are doing a closed beta launch to work closely with an initial group of issuers to fine tune the technology and ensure that we will have data and experience to evaluate the infrastructure.

* '''1.0 Public Spec''' - In January 2012 we will release the 1.0 version of the Open Badge Infrastructure with all necessary supporting documentation and tools to make it self-service

'''TEAM'''