QTI: where are we and where are we going? Pierre Gorissen - SURFfoundation Steve Lay - Questionmark

QTI timeline Conceived in 1999, v1.0 released in 2000 Updated in 2001 (v1.1) and 2002 (v1.2) to improve and extend the model By 2003 it was clear that a major revision was necessary, a quick fix (1.2.1) was followed by a complete rewrite QTI v2.0 was published February 2005 QTI v2.1 (PD2) published June 2006 QTI v2.1 (PD2) – addendum published March 2008 QTI v2.1 (Final) expected ??

Conceived in 1999, v1.0 released in 2000

Updated in 2001 (v1.1) and 2002 (v1.2) to improve and extend the model

By 2003 it was clear that a major revision was necessary, a quick fix (1.2.1) was followed by a complete rewrite

QTI v2.0 was published February 2005

QTI v2.1 (PD2) published June 2006

QTI v2.1 (PD2) – addendum published March 2008

QTI v2.1 (Final) expected ??

QTI 2.1 Status Collected comments on Public Draft Released errata document Profiling discussion Still ongoing, some work done on CC K12 profile Interoperability demonstration Has not taken place yet Because of that – no date set for final release

Collected comments on Public Draft

Released errata document

Profiling discussion

Still ongoing, some work done on CC K12 profile

Interoperability demonstration

Has not taken place yet

Because of that – no date set for final release

Project team Meeting on monthly basis until December 2008 As of January 2009 Co-chair Steve Lay stepped down Co-chair Pierre Gorissen stepped down IMS are looking for a new chair, issues should be raised directly with: Kevin Riley, IMS Lisa Mattson, IMS Operations

Meeting on monthly basis until December 2008

As of January 2009

Co-chair Steve Lay stepped down

Co-chair Pierre Gorissen stepped down

IMS are looking for a new chair, issues should be raised directly with:

Kevin Riley, IMS

Lisa Mattson, IMS Operations

Changes in most recent update Esoteric backwards-compatible changes: Outcomes can also be substituted in Maths and Objects (not just template variables); minor schema change Minor changes to rules of substitution in MathML to support operator and variable name parameterization; no schema change Deprecation of special duration-based operators; no schema change Recommendation to allow extensions at ‘rule’ level within processing elements; more permissive schema extensions Other wording changes to provide clarity with no intended changes to meaning or schema These are only recommendations from this community – they are not agreed changes!

Esoteric backwards-compatible changes:

Outcomes can also be substituted in Maths and Objects (not just template variables); minor schema change

Minor changes to rules of substitution in MathML to support operator and variable name parameterization; no schema change

Deprecation of special duration-based operators; no schema change

Recommendation to allow extensions at ‘rule’ level within processing elements; more permissive schema extensions

Other wording changes to provide clarity with no intended changes to meaning or schema

These are only recommendations from this community – they are not agreed changes!

Questions…

Thank you for your attention…