Mozilla Open Badges 201

Click here to load reader

  • date post

  • Category


  • view

  • download


Embed Size (px)


Slides from @megcolek Mozilla Open Badges 201 Webinar, Nov. 13, 2013

Transcript of Mozilla Open Badges 201

  • 1.Mozilla Open Badges 201 Badge System Design & Technology ReviewMegan Cole Marketing Lead [email protected] @megcolek Sunny Lee Product Lead [email protected] @soleteleeThis work is licensed under the Creative Commons Attribution-ShareAlike 3.0 Unported License. To view a copy of this license, visit or send a letter to Creative Commons, 444 Castro Street, Suite 900, Mountain View, California, 94041, USA.

2. Welcome to our 201 Webinar Badge System Design Overview Technical Overview 7 Steps for Roadmapping Whats Next And more... 3. Adiffering opinionsAssessment Assessment Assessment Assessment Assessment Assessment Assessment Assessment Assessment 4. BSome folks say our educational system is 5. Cmany challenges seat time complicated metrics overcrowding remediation 6. Badges act as representations of achievements, learning, skills, interests, competencies 7. hard & soft skills, peer assessment, and stackable lifelong learning 8. Open Badges are a form of personal social currency you can share across the web 9. How are we getting there? 10. Through a shared infrastructure: a universal standard 11. Badge metadata spec + Issuer API (and in 2014 an Endorser API) 12. Badge name Badge URL (description) Badge criteria Badge image Issuer Issue date Recipient Alignment (standards) Expiration date Evidence URL 13. What does this mean in practice? 14. formal & informal learning pathways 15. Can I see an example? 16. Badge System Design 17. 18. Badge Team2. Badge Info3. Badge Tech4. Badge Design 19. 20. Homework exercise #1: write down your top 3 badge system goals (5 minutes) 21. Homework exercise #2: copy the spreadsheet & begin working through your rst badge (7 minutes) 22. Homework exercise #3: share your badge thinking with us at [email protected] (8 minutes) 23. 24. 25. Technology Overview 26. Mozillas Open Badge Infrastructure 27. Free and open source software Backpacks and APIs 28. 29. An application programming interface (API) that species how software components should interact with each other. 30. A small application with limited functionality that can be installed and executed within a web page by an end user. 31. 32. 33. 7 key points in roadmapping and resource management 34. 1. Funding 2. Partnerships 3. Research 4. Badge system design 5. Time management 6. Technical resources 7. Design resources 35. 1. Funding 36. How might you actively think about the personnel and required resources needed to build your best possible badge system? 37. 2. Partnerships 38. How might you freely imagine the system that you might be able to build with others? 39. 3. Research 40. How might you intentionally plan for the ways that badges may inuence you & your teams as well as your badge earners? 41. 4. Badge System 42. How might you consciously think about the genealogy of your system and its future growth? 43. 5. Timing 44. How might you deliberately plan for a full system life cycle? 45. 6. Technology Resources 46. How might you best architect your team to fail fast and maximize success? 47. 7. Design Resources 48. How might you dynamically explore the most compelling visual representation of your system? 49. 1. Funding 2. Partnerships 3. Research 4. Badge system design 5. Time management 6. Technical resources 7. Design resources 50. Whats Next? 51. Stay in Touch Join our weekly Community call Wednesdays at 9am PDT / 12pm EDT Post questions to our Google Group Stay up-to-date with our Blog Reach out to us for information [email protected] 52. THANK YOU! || @OpenBadges