So, any attempt to improve agility is the right way to go, we all know that a wiki offers more flexibility than just HTML editing.
Yeah, but none of that flexibility fits into the IMS notion of what a course is, which is a set of resources and sequencing information, nothing more. The only thing that makes sense in that context is to be able to edit an existing resource.
If there is interest from the community to extend this list with xowiki/imsd or whatever, maybe the dotlrn consortium will got for it.
We're in the last round of adopting accessibility requirements. Meeting those accessibility requirements is a prerequisite for considering xowiki for inclusion in .LRN.
For an iframe, i would recommend to provide a custom adp file with an appropriate HTML head etc., such that e.g. page specific css files will continue to work.
IMS resources including HTML files should be standalone, so they can be created using standard course creation tools. The bare-naked HTML - including the HTML, HEAD and BODY tags included within - has to be returned directly with no wrapping by the LMS.
