The top element in the schema definition includes the following xsd:annotation element:
Code Block | ||||
---|---|---|---|---|
| ||||
<xsd:annotation>
<xsd:documentation xml:lang="en">
<p>Schema for import and export of data in the Evaluation System. XML elements are
defined to encode sets and individual instances of these java classes: </p>
<ul>
<li>EvalScale</li>
<li>EvalItem</li>
<li>EvalItemGroup</li>
<li>EvalTemplate</li>
<li>EvalTemplateItem</li>
<li>EvalEmailTemplate</li>
<li>EvalEvaluation</li>
<li>EvalAssignGroup</li>
</ul>
<p>Note: Limits on length of strings are shown for fields that have limited length.
Other string properties are unbounded.</p>
<p> UMICH changes: </p>
<ul>
<li>Ensure that values are supplied for all integers, booleans, dates etc. Only
strings can be null.</li>
<li>Use lower-case names for all elements? Can we switch to camel-case to correspond
to the property names in the model classes?</li>
<li>Switch to date-time format for all dates. <a target="_blank"
href="http://www.w3.org/TR/xmlschema11-2/#dateTime"
>http://www.w3.org/TR/xmlschema11-2/#dateTime</a></li>
</ul>
</xsd:documentation>
<xsd:appinfo>
<jaxb:schemaBindings>
<jaxb:package name="org.sakaiproject.evaluation.model"/>
</jaxb:schemaBindings>
</xsd:appinfo>
</xsd:annotation>
|
It also contains definitions of the element EVAL_DATA, several complex types and five simple types:simple types. You will find links to the complex types and simple types in the page about EVAL_DATA and other pages linked from there.