• Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
173
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
1
Comments
0
Likes
1

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 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/