Open Badges, Tin Can, LRMI can use InLOC as one cornerstone

From Simon Grant's blog:

There has been much discussion recently about Mozilla Open Badges, xAPI (Experience API, alias "Tin Can API") and LRMI, as new and interesting specifications to help bring standardisation particularly into the world of technology and resources involved with people and their learning. They have all reached their "version 1" this year, along with InLOC.
InLOC can quietly serve as a cornerstone of all three, providing a specification for one of the important things they may all want to refer to. InLOC allows documentation of the frameworks, of learning outcomes, competencies, abilities, whatever you call them, that describe what people need to know and be able to do.
Mozilla has been given, and devoted, plenty of resource to their OpenBadges effort, and as a result is it widely known about, though not so well known is the rapid and impressive development of the actual specification. The key part of the spec is how OpenBadges represents the "assertions" that someone has achieved something. The thing that people achieve (rather that its achievement) could well be represented in an InLOC framework.

Tin Can / Experience API (I'll use the customary abbreviation "xAPI") has also been talked about widely, as a successor to SCORM. The xAPI "makes it possible to collect the data about the wide range of experiences a person has (online and offline)". This clearly includes "experiences" such as completing a task or attaining a learning outcome. But xAPI does not deal with the relationships between these. If one greater learning outcome was composed of several lesser ones, it wouldn't be natural to represent that fact in xAPI itself. That is where InLOC naturally comes in.

LRMI ("Learning Resource Metadata Initiative") is, as one would expect, designed to help represent metadata about learning resources, in a way that is integrated with schema.org. What if many of those learning resources are designed to help a learner achieve an intended learning outcome? LRMI can naturally refer to such a learning outcome, but is not designed to represent the structures themselves. Again, InLOC can do that.

What would be chaotic would be if these three specifications, each one potentially very useful in its own way, all specified their own, possibly incompatible ways of representing the structures or frameworks that are often created to bring common ground and order to this whole area of life.

Please don't let that happen! Instead, I believe we should be using InLOC for what it is good at, leaving each other spec to handle its own area, and no one shamefully "reinventing the wheel".

Draft proposals [...]

Read the full article at: https://web.archive.org/web/20140401004010/http://blogs.cetis.ac.uk/asimong/2013/07/31/open-badges-tin-can-lrmi-can-use-inloc-as-one-cornerstone/