Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Open Badges 2.0 #99
This is a preliminary pull request to merge the 2.0 draft (see on staging server here) into master to publish it as the final recommendation of the Badge Alliance to hand over to the IMS Global Open Badges Working Group in 2017.
The Badge Alliance has collected feedback and proposals from over two dozen stakeholder organizations and compiled a number of desired use cases in mid-2016.
These use cases were prioritized by organizations and individuals who wanted to contribute to standardizing solutions to them in the Open Badges Specification and advanced to issues on this repository.
I worked with members of the BA Standard Working Group to draft a recommendation containing minimal breaking changes and a robust set of new features, putting Open Badges on a firm foundation for years of improvements to implementations as well as clearing the way to a better ability to experiment with the vocabulary and providing the tools for future updates to avoid breaking changes for even major improvements. For issuers, it will take minimal effort to move from v1.1 Open Badges to v2.0, as almost every change is optional, leaving the previous option intact. Issuers may then take advantage of the large number of new features as they fit with internal development roadmaps.
Optional new features:
…ild" to create a build for local development and production. _config.yml adjusted for publishing of drafts on GitHub Pages.
…ocabulary: * Add reference to IMS Global taking over the spec (still in progress) * Update data classes * Improve ordering of document structure
…ress. We'll use gh-pages to accommodate automatic publishing on Github instead of the 2.0 branch.
…pts and terms. Not all references to v1 context have been removed at this time, because the semantic value of those extensions has not changed. Some further cleanup could be effected later.