Like Scott and Durand I’m all in favour of anything that can simplify the current IMS LD spec. However before we go ahead with the technical ins and outs I would really like to ensure that any development is based on real needs – what teachers and learners actually need and what we can really expect our systems to do effectively and efficiently.
So, before we start debating what we keep in/out of scope, I’d really like to see the development of a robust and real set of use-cases. Let’s use those to engage teachers and vendors alike and build tools that do what teachers really need them too. Let’s be realistic about who is actually going to take the time to create a fully fledged UoL to use IMS speak. Not every teacher/ learning designer will or necessarily needs to. Let’s look at what people really want to do and where there is a real gap. We have a wealth of designs now that we can draw on now. What are the key things people need to do but can’t just now, or could be done more effectively by some automatic processes for example grouping, populating classes? And instead of showing the XML, let’s start with what the user wants to do and work backwards from there.