Qti Update Jan 2009

339 views

Published on

Steve Lay of Questionmark and Pierre Gorissen of SURF discuss the current position of the IMS QTI specification and its possible future.

Published in: Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
339
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Qti Update Jan 2009

  1. 1. QTI: where are we and where are we going? Pierre Gorissen - SURFfoundation Steve Lay - Questionmark
  2. 2. QTI timeline <ul><li>Conceived in 1999, v1.0 released in 2000 </li></ul><ul><li>Updated in 2001 (v1.1) and 2002 (v1.2) to improve and extend the model </li></ul><ul><li>By 2003 it was clear that a major revision was necessary, a quick fix (1.2.1) was followed by a complete rewrite </li></ul><ul><li>QTI v2.0 was published February 2005 </li></ul><ul><li>QTI v2.1 (PD2) published June 2006 </li></ul><ul><li>QTI v2.1 (PD2) – addendum published March 2008 </li></ul><ul><li>QTI v2.1 (Final) expected ?? </li></ul>
  3. 3. QTI 2.1 Status <ul><li>Collected comments on Public Draft </li></ul><ul><ul><li>Released errata document </li></ul></ul><ul><li>Profiling discussion </li></ul><ul><ul><li>Still ongoing, some work done on CC K12 profile </li></ul></ul><ul><li>Interoperability demonstration </li></ul><ul><ul><li>Has not taken place yet </li></ul></ul><ul><li>Because of that – no date set for final release </li></ul>
  4. 4. Project team <ul><li>Meeting on monthly basis until December 2008 </li></ul><ul><li>As of January 2009 </li></ul><ul><ul><li>Co-chair Steve Lay stepped down </li></ul></ul><ul><ul><li>Co-chair Pierre Gorissen stepped down </li></ul></ul><ul><li>IMS are looking for a new chair, issues should be raised directly with: </li></ul><ul><ul><li>Kevin Riley, IMS </li></ul></ul><ul><ul><li>Lisa Mattson, IMS Operations </li></ul></ul>
  5. 5. Changes in most recent update <ul><li>Esoteric backwards-compatible changes: </li></ul><ul><ul><li>Outcomes can also be substituted in Maths and Objects (not just template variables); minor schema change </li></ul></ul><ul><ul><li>Minor changes to rules of substitution in MathML to support operator and variable name parameterization; no schema change </li></ul></ul><ul><ul><li>Deprecation of special duration-based operators; no schema change </li></ul></ul><ul><ul><li>Recommendation to allow extensions at ‘rule’ level within processing elements; more permissive schema extensions </li></ul></ul><ul><ul><li>Other wording changes to provide clarity with no intended changes to meaning or schema </li></ul></ul><ul><li>These are only recommendations from this community – they are not agreed changes! </li></ul>
  6. 6. Questions…
  7. 7. Thank you for your attention…

×