disable output escaping for CDATA html elements
include short answer prompts in the resultset view
use "prompt" xpath that matches current QTI serialization
use regular hyperlink to viewing question (item) details - nested form elements were causing grief after being included with ajax calls.
detokenize
add handling for qti metadata in resultset view
adjust xpaths to match changes to edml/qti output by FirstMorpho
render multiple mattext elements if they exist...
get the ajax-specific first skins organized with some better naming.these essentially provide a pointer to custom resultset style sheets so that we can just use Ajax.Updater from prototype and inject the returned html.they do rely on the first skin (which makes it nice for changing the look and feel - not a bunch of css files lying around messing things up, etc...).