Versioning is the ability to keep track of changes/updates made to SAIL content. At one meeting long long ago, we debated the merits of
- bushy versioning
- keeps new versions for every change made
- can be more automated
- its "bushy" because we expect there to be many branchpoints as people tailor content for their own uses (and don't integrate it back in).
- complicated
- it is probably necessary to have a detailed model of Learner Data - deprecated, esp. base types, for this to work
- sparse versioning
- more for manual control of new versions
- probably no branching information is kept, just linear versions. A branch starts a new version history...
- simple
This ucdiscovery grant might be useful:
- ''version support for XML document'': go here and search for the title. It is a UC thing, so should be available to us.
Versioning can also allow content that is no longer maintained to still run. When content depends on several shared libraries and those libraries are updated but the content can't be.
Doing this properly requires:
- a scheme to track which versions of libraries are backward compatible and which are not.
- tracking all dependancies of libraries and content. These dependencies need to be searched in both directions: from library to content and content to library.
- ability to serve two versions of the same file