Conceptual Diagram bis - aaronesilvers/xAPI-Badges GitHub Wiki

I use the same starting point as Aaron, with a little twist: the competency registry. Without a competency registry, it might be a impossible mission for a curriculum designer to go through hundred of badges to find whether there are matches for the different competencies/learning outcomes defined the the curriculum. And there is a simple way to bootstrap the process... ... harvesting metada from Open Badges. It won't be perfect; some curation will be required, but could be a quick and efficient bootstrap mechanism. In order to create a Badge, the starting point should be the addition of competency definitions in the repository (they should be distributed, but that doesn't change the main narrative) It is then possible to populate the Open Badges/ Activities registries. Activities are just "badges without a pretty picture": we still need the information about who/what has issued it in order to be assessed (by a machine or a human, whatever). When Jim 'pledges' for a Badge, the information must be retained somewhere, his own locker or the Badges registry. As Jim works towards his badge, his personal locker is collecting many xAPI statements. A webservice, the Badge Alert Service, regularly scans the lockers of those who have pledged for a badge and when all the criteria are being met, sends an alert to the badge issuer. The badge issuer, who can be a person (possibly representing an organisation) or an automaton delivers the badge to the client... which makes Jim very proud!