[QTI] Re: manifest file creation

[Michael Piotrowski]

"Linn van der Zanden" <reload_project at hotmail.co.uk> writes:

> Option 1: associating the metadata with the content package

[...]

> Option 2: associating the metadata with the files inside the content
> package

[...]

> The advantage of option 1 is that all of the mime types required for an item
> are together, and the content package is labelled with metadata
>
> The advantage of option 2 is individual files are labelled with metadata -
> which allows for multiple items to be bundled into a content package.

Which I'd consider decisive--what good is a content package when you
can't use it for packaging multiple items? ;-)

Seriously, I consider the <metadata> element in <manifest> to apply to
the whole package, while the <metadata> element in <resource> applies
only to that specific resource.

> Has anyone else implimented the CPing of QTI2 items?  How did you do it?  
> Which method would people recommend?

In LlsMultipleChoice <http://wwwai.cs.uni-magdeburg.de/sw/llsmc/>
we're using the different metadata elements as outlined above.  I can
send you an example CP produced by LlsMultipleChoice if you're
interested.

Greetings

-- 
Michael Piotrowski, M.A.                   <mxp at iws.cs.uni-magdeburg.de>
Otto von Guericke University, Magdeburg              WDOK Research Group