Index: openacs-4/packages/imsld/www/doc/ch01s04.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/imsld/www/doc/ch01s04.html,v diff -u -r1.3 -r1.4 --- openacs-4/packages/imsld/www/doc/ch01s04.html 27 Jun 2005 11:34:37 -0000 1.3 +++ openacs-4/packages/imsld/www/doc/ch01s04.html 30 Jun 2005 10:31:51 -0000 1.4 @@ -1,3 +1,28 @@ -
- -There is some work done so far that we could use in the near future:
Alfanet.The people of Alfanet has already done some integration of IMS LD with OpenACS. At the time of writing this specification we were waiting to have access to their code in order to evaluate the possibility to make use of what they have already done, avoiding the waist of resources, but by the moment we don't know if this will be possible.
LAMS. At the time of writing this specification, we were plannig to do an integration with LAMS, which is a tool for designing, managing and delivering online collaborative learning activities. The LAMs project is already integrated with Moodle. We can take advantage of that integration experience, but we expect to write all the code at .LRN from scratch, and maybe later work on the integration.
RELOAD. It has an IMS LD editor wich is independent from any LMS. By means of this editor, you can generate an IMS LD for a concrete course. Also it has integrated the CopperCore player
CopperCore. It has an IMS LD editor wich is independent from any LMS. By means of this editor, you can generate an IMS LD for a concrete course. Also it has a player.
Our purporse is to be able to interpret the IMS LD generated by RELOAD, CopperCore and LAMS and whichever IMS LD that can be generated by other different authoring tools.
There is some work done so far that we could use in the near + future:
Alfanet.The + people of Alfanet has already done some integration of IMS-LD with + OpenACS. At the time of writing this specification we were waiting to + have access to their code in order to evaluate the possibility to make + use of what they have already done, avoiding the waist of resources, + but by the moment we don't know if this will be possible.
LAMS. At + the time of writing this specification, we were planing to do an + integration with LAMS, which is a tool for designing, managing and + delivering online collaborative learning activities. The LAMs project + is already integrated with Moodle. We can take advantage of + that integration experience, but we expect to write all the code at + .LRN from scratch, and maybe later work on the integration.
RELOAD. It has an + IMS-LD editor which is independent from any LMS. By means of this + editor, you can generate an IMS-LD for a concrete course. Also it has + integrated the CopperCore player
CopperCore. It has + an IMS-LD editor which is independent from any LMS. By means of this + editor, you can generate an IMS-LD for a concrete course. Also it has + a player.
Our purpose is to be able to interpret the IMS-LD generated by + RELOAD, CopperCore and LAMS and whichever IMS-LD that can be generated + by other different authoring tools.