Comments on: IMS withdraw QTI v2.1 draft specification http://blogs.cetis.org.uk/rowin/2009/04/03/ims-withdraw-qti-v21-draft-specification/ Cetis Blog Thu, 29 Mar 2012 22:41:08 +0000 hourly 1 http://wordpress.org/?v=4.1.22 By: Wilbert’s work blog» Blog Archive » IMS QTI and the economics of interoperability http://blogs.cetis.org.uk/rowin/2009/04/03/ims-withdraw-qti-v21-draft-specification/#comment-83 Tue, 07 Apr 2009 12:42:25 +0000 http://blogs.cetis.org.uk/rowin/?p=115#comment-83 […] A brief overview of the current QTI 2.1 discussion […]

]]>
By: richard knights http://blogs.cetis.org.uk/rowin/2009/04/03/ims-withdraw-qti-v21-draft-specification/#comment-82 Sat, 04 Apr 2009 13:43:38 +0000 http://blogs.cetis.org.uk/rowin/?p=115#comment-82 WOW v2.1 is a far better format than v1.2, I’ve used both in big assessment projects. I think the issue however is not versions of specifications, its more that “standards” are increasingly irrelevent in the new digital world. The only one that still makes sense is IMS content packaging.

]]>
By: Structured Methods › links for 2009-04-03 http://blogs.cetis.org.uk/rowin/2009/04/03/ims-withdraw-qti-v21-draft-specification/#comment-81 Fri, 03 Apr 2009 18:04:15 +0000 http://blogs.cetis.org.uk/rowin/?p=115#comment-81 […] IMS withdraw QTI v2.1 draft specification Over the last few days a new notice has appeared on the IMS Question and Test Interoperability webpage in place of the QTI v2.1 draft specification: "The IMS QTIv2.1 draft specification has been removed from the IMS website. Adequate feedback on the specification has not been received, and therefore, the specification has been put back into the IMS project group process for further work." This was clearly completely unexpected, not only for us at CETIS but also amongst a number of commercial and academic developers who have been working with the specification as can be seen by posts to the technical discussion list hosted by UCLES. (tags: IMS QTI CETIS question_and_test_interoperability learning assessments) […]

]]>
By: Chuck Allen http://blogs.cetis.org.uk/rowin/2009/04/03/ims-withdraw-qti-v21-draft-specification/#comment-80 Fri, 03 Apr 2009 15:18:38 +0000 http://blogs.cetis.org.uk/rowin/?p=115#comment-80 Hopefully, this will be worked out within IMS to the satisfaction of
all stakeholders. But what if it is not? If you were a
stakeholder that had made significant contributions to 2.1 and then
made significant investments implementing it would you have painted yourself into a corner regarding on-going maintenance to the 2.1 work?

I saw Steve Lay’s post about his assumption that the license under which the draft was made available would still allow implementers to continue to use and distribute the 2.1 work. However, as I understand it, that license would prevent derivative works, so maintenance and additions to the 2.1 work independent of IMS would be blocked. Is that correct?

It occurs to me that many standards implementers and stakeholders don’t look at these “fine print” issues prospectively, but they should. I’ve made a couple recent posts to my blog about the need for more uniform, permissive licensing by consortia. As my posts point out, the number and variety open sources software licenses can be a source of much consternation. However, we’re approaching a point where there is more certainty regarding rights under OSS licenses than the licenses granted by consortia and standards orgs. The latter tend to be like snowflakes in that no two are the same.

]]>