OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

dita message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [dita] Proposal for 1.3 specification on lcQuestion


There looks to be an active QTI forum. Is it worth asking for clarification on the QTI side?

Sandra
On Jan 19, 2012, at 9:31 PM, Eliot Kimber wrote:

Also, looking at the definition of lcQuestionBase, it is specialized from
<p>, so it could not be changed to allow blocks. We would have to define a
new question base type (e.g, lcQuestionDivBase) and concrete type (e.g.,
lcQuestionDiv) allowed as an alternative to lcQuestion). This new element
type would need to specialize from figgroup I think.

I'm working currently with several textbook publishers using DITA for
textbooks and associated assessments. So this issue is important to me, but
so is IMS-QTI alignment as all my clients also publish their assessments to
SCORM- and IMS-based learning management systems.

I looked at the current IMS-QTI spec, which was last updated in 2006, and I
couldn't understand it well enough to figure out what the rules for
questions actually are--the standard is written in a particularly obtuse
way, at least to this unschooled reader.

Cheers,

E.


On 1/19/12 7:42 PM, "Eliot Kimber" <ekimber@reallysi.com> wrote:

The issue, as I understand it, is that IMS-QTI, which the learning
assessment markup tries to be consistent with as much as possible, does not
allow multiple paragraphs within the question prompt.

The way I've worked around this to date is to create a wrapper element,
e.g., <question>, that contains whatever block-level elements you want and
then any specialization of lcQuestionBase you want, e.g.:

<!ENTITY % question.content
 "(%RSuiteMetadata;,
  (p |
   image |
   table |
   simpletable |
   fig |
   ol |
   ul |
   lq)*,
  (%lcTrueFalse; |
   %lcSingleSelect; |
   %lcOpenQuestion;
   )*,
  (%lcFeedback;)*,
  q_meta?
 )
">

Whether or not the concern with IMS-QTI is still valid I don't know. If it's
not then I would agree with allowing blocks within lcQuestion as you
suggest.

Maybe John Hunt can provide more insight into the design?

Cheers,

E.

On 1/19/12 5:27 PM, "JoAnn Hackos" <joann.hackos@comtech-serv.com> wrote:

Hi All,
I would like to propose that we add to the list of elements available in the
L&T specialization of the assessment, namely lcQuestion.

lcQuestion needs to contain <p>, various lists, programming and software
elements, etc. At present, lcQuestion primarily contains highlighting
elements.

The relevant examples are below:

Regards,
JoAnn

JoAnn T. Hackos, PhD
President
Comtech Services Inc.
710 Kipling Street, Suite 400
Denver, CO 80215
joann.hackos@comtech-serv.com
skype joannhackos


Here is an example from our book:

We had to code the question as follows:
<lcQuestion>What is wrong with the following code?
<image href="">

We would have liked to have coded it:
<lcQuestion>What is wrong with the following code?
   <codeblock>&lt;property>
  &lt;prophead>
    &lt;proptypehd>Character graphic&lt;/proptypehd>
    &lt;propvaluehd>Code Point&lt;/propvaluehd>
    &lt;propdeschd>Description&lt;/propdeschd>
  &lt;/prophead>
  &lt;properties>
     &lt;proptype>A&lt;/proptype>
     &lt;propvalue>41&lt;/propvalue>
     &lt;propdesc>A capital&lt;/propdesc>
  &lt;/properties>
  &lt;properties>
     &lt;proptype>a&lt;/proptype>
     &lt;propvalue>61&lt;/propvalue>
     &lt;propdesc>a small&lt;/propdesc>
  &lt;/properties>
&lt;/property>  
     </codeblock></lcQuestion>

As another example, some questions might need a scenario set up where you
want
to have multiple paragraphs, which is also not allowed. For example,

Jane is taller than Bob.
Greg is shorter than Bob.
Bill is shorter than Jane, but taller than Bob.
Which of the following is true:
a)     Greg is taller than Jane.

b)     Bill is taller than Greg.

c)      Bob is the shortest person mentioned.


You could not code this question to format as we¹ve shown. It would have to
currently be one paragraph.

<lcQuestion> Jane is taller than Bob. Greg is shorter than Bob. Bill is
shorter than Jane, but taller than Bob. Which of the following is
true:</lcQuestion>

But we¹d rather be able to code:
<lcQuestion><p> Jane is taller than Bob.</p>
<p> Greg is shorter than Bob. </p>
<p>Bill is shorter than Jane, but taller than Bob. </p>
<p>Which of the following is true:<p></lcQuestion>


Or you might have a list within the question, like a logic problem. There¹s
no
way to include any type of list.
For example, how would you code the following without a list element in the
question?

Figure out the day of the week, first name, actor and cell phone for each
person using the clues given. Below are all categories and options used in
this puzzle.
1.      Kevin Bacon's cousin is not Conor.

2.      The person who arrived on Friday doesn't have a cell phone with
Verizon.

3.      The five individuals are the person who arrived on Wednesday, Conor,
the person who arrived on Friday, the person with the nTelos cell phone and
John Travolta's cousin.

4.      Kassidy arrived sometime before Danielle.

5.      The person with the nTelos cell phone is not Danielle.

6.      Neither Bruce Willis's cousin nor the person with the nTelos cell
phone is Felix.

7.      John Travolta's cousin arrived sometime before the person with the
Verizon cell phone.

8.      The person with the Cingular cell phone is not Felix.

9.      Kassidy arrived the day after Conor.

10.  Robert De Niro's cousin is not Kassidy.

11.  Conor has always used Nextel.

12.  Of Felix and Danny DeVito's cousin, one has always used nTelos and the
other arrived on Monday.

13.  The person who arrived on Tuesday isn't related to Robert De Niro.




--
Eliot Kimber
Senior Solutions Architect
"Bringing Strategy, Content, and Technology Together"
Main: 512.554.9368
www.reallysi.com
www.rsuitecms.com


---------------------------------------------------------------------
To unsubscribe, e-mail: dita-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: dita-help@lists.oasis-open.org


--
Eliot Kimber
Senior Solutions Architect
"Bringing Strategy, Content, and Technology Together"
Main: 512.554.9368
www.reallysi.com
www.rsuitecms.com


---------------------------------------------------------------------
To unsubscribe, e-mail: dita-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: dita-help@lists.oasis-open.org




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]