Thanks Jeff, that is a good point!
I think you read things right, if you by "public interface" mean "public TCL and/or SC API". (We obviously want a public UI for the Simple Sequencing package.) Ernie thinks a public API is absolutely necessary and we don't. The reasons why we reach these different conclusions is because we have different understandings of IMS SS and envision different end products.
Here's our (Polyxena's) partial interpretation of the main differences in opinion:
- We think that SS is specificly designed for traversal of sequences of learning activities.
- Ernie thinks that SS is a general service which could be used for many types of sequencing.
*
- To us, SS is about sequencing "learning activities" which map to learning objects and other content, such as a test, for instance.
- To Ernie, SS seems to be about sequencing the actual learning objects in LORSm themselves.
*
- We envision one central front-end for creating learning sequences throughout the toolkit.
- Ernie envisions many front-ends for creating learning sequences in many packages (among them LORSm).
*
- We think of LORSm as a filestorage (on steroids) for learning objects (a course library, if you will).
- Ernie thinks of LORSm as an LMS internally providing sequenced delivery of its learning objects.
*
- We want the whole learning sequence user experience to be server-side.
- Ernie wants the SCORM solution with client-side UI and an adapter demanding strictly defined content.
