In cleaning up the ULA source, I found that the schema enforces an ordering of #answer and #solution elements inside a #task. So the following is valid:
<task>
<answer> .. </answer>
<solution> .. </solution>
</task>
but
<task>
<solution> .. </solution>
<answer> .. </answer>
</task>
is not. It felt more natural to me to write solutions and then append shorter answers so I'm wondering if this is intentional. My assistant says the order doesn't affect processing. I can easily fix the 386 (!) violations, but I'm wondering about newer authors who may be confused since the validation report just says that 'element "answer" not allowed here.'
David