functionalities to import and export XML file, i would like to know
where i should start from
<p>This is good idea and it will save lot of time.
<p>We did similar work for Wimpy-Point and Glossary (PGSQL only) that can be found here : http://openacs.org/new-file-storage/one-file.tcl?file_id=434
<p>Currently ns_xml module can be used to export/import but I think there are efforts underway to replace it with TCLDOM etc, but for time being ns_xml should be ok.
IIRC, Jon Griffin has already started some work on this so you might want to cantact him. It's something that would be much more useful than 20 different ways to export/import depending on the package.
I realize that full "compliance" with these specs is probably well outside your scope, but if we all work towards IMS I think we can maximize code reuse and minimize duplication of effort.
OCW (ocw.mit.edu) announced at the EduCause conference that they intend to use these specifications to transfer data between the various MIT course management platforms and OCW. This means that eventually SloanSpace will implement a subsection IMS. OCW is still in the process of creating technical specs, so I do not yet know the time frame and I certainly can not guarantee that complete "compliance" will be in scope for Sloan either.
That said, my long term vision is that if indivdual dotLRN projects implement peices of IMS specifications to meet thier needs, that one of the OACS companies will find it in thier business interests to take it the remaining delta to compliance.
Michael Feldstein is another big IMS fan and a bit further up the learning curve on IMS then myself. I'm sure that he, as well as myself, will be happy to help you in interpreting how the specs can apply to FAQ.