Although SCORM is a detailed specification not all elements are mandatory. Furthermore, the Application Programming Interface (API) which facilitates interaction between LMS and your publication is presented in an html wrapper and your publication will be launched in a separate wrapper. There may be limitations of size because of the area made available to the SCO. There may be specific requirements for navigation.
This is particularly true where there is an LCMS involved as well as an LMS. Thus each "standard" can be implemented in a slightly different way so you will need to liaise with the LMS provider to understand things like:
The version of SCORM supported (and in particular which API is used)
The data models within that version which are supported
Any data transfer which is mandatory for their implementation.
Any limitations on size and format of the SCO
It must be remembered that most LMS providers also provide their own editing tools for creating resources and may be inclined to encourage your customer to use their tools. Some only provide limited import facilities for material created with third part applications.
This can cause problems with compatibility and/or getting specific functions to work correctly. This is not a problem specific to Opus – we have seen problems with Flash output and that from other competitors and compatibility can vary between LMS.
If you experience any problems getting your content to work in an LMS contact us. We are happy to work with you to get it working. We can even create custom templates for you to accommodate special requirements although there is usually a small charge for this.