General Considerations

Subject matter review and content testing is not covered and is the responsibility of the developer.
If an implementation relies on tools and technology used by the content developer, it remains the content developer’s responsibility to make any necessary edits to the files for interoperability issues (after the tool generates that output). The developer must then submit the content for testing/validation.
Make good reuse of templates and share them with other developers. This provides a framework that can be tested once and used many times for maximum benefit.
Developers must decide how their course is played, to then modify the course's metadata (AICC files) to associate the course with a player.