Structuring OpenBadges with InLOC
Download as PPT, PDF2 likes752 views
The presentation discusses how open badges can be structured using the InLOC specification to represent learning outcomes and competencies. InLOC allows learning outcomes and competencies to be represented in an interoperable format between tools and services. Badge classes can link to InLOC information through criteria URLs or alignments, reusing learning outcome definitions. Technical development of InLOC includes defining JSON bindings to work with open badges and other specifications using JSON formats.
Structuring OpenBadges with InLOC
- 1. Structuring OpenBadges with InLOC Simon Grant CETIS for OBSEG 2013-10-09, Glasgow
- 2. Outline ● The structure of a Badge ● What is InLOC? ● The Badge Class related to InLOC ● How are Badges structured? ● How can InLOC help? ● Developing InLOC technically
- 3. The structure of a Badge ● https://github.com/mozilla/openbadges/wiki/Assertio ● BadgeAssertion says something like – “this org awarded this badge to this person” – (and maybe) “here is some related evidence” – Badge image has metadata “baked” in ● BadgeClass – the generic badge (common to all awards of it) – has “criteria” – could be learning outcome(s) – also has “alignment” info
- 4. What is InLOC? ● “Integrating Learning Outcomes and Competences” ● Specification for representing information about – intended learning outcomes – competenc(i)es – structures or frameworks of definitions of them ● (Tech: originally XML; provisionally JSON) ● For communicating useful information – interoperably – between tools and services
- 5. BadgeClass and InLOC ● If criteria are learning outcomes (etc.) – criteria URL could point to InLOC info ● If criteria are not clear cut learning outcomes – criteria may or may not be suited to InLOC – alignments can point to InLOC definitions
- 6. How are Badges structured? ● Various ideas may be tried... – Lesser Badges could build up to greater ones – Could have pathways with prerequisites – Badges can be marked as equivalent or related – ... ● Examples from participants here? – (please bring them up in the question time)
- 7. How can InLOC help you? ● Can represent your information specifically about learning outcomes, competence ● Factors out your reusable LOC information from anything badge-specific ● Provides thread and glue for your badges ● Fills a need not satisfied by the Mozilla spec ● Your Badges point to your InLOC info
- 8. Developing InLOC technically ● XML binding is defined (in CEN Workshop) ● Probably JSON binding will be more useful – JSON used by OpenBadges, xAPI, etc. – by the way, how about JSON-LD? ● Please help us fix on a really useful JSON binding – all are welcome to join in ● Specially if you implement it at the same time!
- 9. Thanks! ● for your attention ● for your questions now ● for any future interest or later discussion: – asimong@gmail.com or @asimong This presentation “Structuring OpenBadges with InLOC” by Simon Grant of Cetis http://www.cetis.ac.uk/ is licensed under the Creative Commons Attribution 3.0 Unported Licence http://creativecommons.org/licenses/by/3.0/
- 10. Thanks! ● for your attention ● for your questions now ● for any future interest or later discussion: – asimong@gmail.com or @asimong This presentation “Structuring OpenBadges with InLOC” by Simon Grant of Cetis http://www.cetis.ac.uk/ is licensed under the Creative Commons Attribution 3.0 Unported Licence http://creativecommons.org/licenses/by/3.0/