From: Peter C. <Pet...@me...> - 2005-05-27 16:42:24
|
I've just committed code that allows users with Manage permission to export an IMS content package version 1.1.4 from a webdocument. The exported CP can be loaded by Bodington - tested by doing a round-trip with Aggie's protein CP, and checking that the import from the round-trip is not distinguishable to the user from the originally-imported version. So I think we can release 2.6 with import many spec-compliant content packages. Bodington has never implemented some of the more obscure features of CPs, such as sub-manifests and xinclude; those features remain out of scope for this project, whose intention was to get CP import/export up to date. Still to do: Implement the notion that an installation-defined sequence of XSLT filters run on CPs before they are imported. This allows filtering of non-spec-compliant CPs to be at least minimally compliant, without having to recompile Bodington. Still to do: Amend the XML repository to be namespace-aware. I'm thinking about the best way to do this. Still to do: TEST! I have very few real-world CPs with which to test. If you have pointers to some, I'd still appreciate them. - Peter -- Peter Crowther, Director, Melandra Limited John Dalton House, 121 Deansgate, Manchester M3 2AB t: +44 (0)161 828 8736 f: +44 (0)161 832 5683 |