Weaknesses
There’s a ton of relevant information on this page, but if you want the latest and the greatest, visit experienceapi.com.
The nature of adding new functionality to something as far-reaching as e-learning specifications inherently involves design trade-offs and compromises. Focusing on one area often necessarily involves compromising on other areas. We’re well aware of these weaknesses, and we have suggested solutions for most of them. Look through the list, check out our suggestions, and let us know what you think.
- Security/privacy complexity
- Activity definition agreement
- Verb variation
- Reporting complexity
- LRSs will have to store and manage more data
Pingback: Getting to Know Project Tin Can (Next Generation SCORM) | onehundredfortywords()
Pingback: Why SCORM 2004 failed & what that means for Tin Can | eFront Blog()