image resize, xml well formed qandaset

Doc/course.xml

@@ -677,7 +677,7 @@ drwxr-xr-x 4 goik fb1prof 4096 Nov  8 22:04 ..
           </listitem>
           <listitem>
-            <para>sex, mandatory</para>
+            <para>sex (male/female), mandatory</para>
           </listitem>
           <listitem>
@@ -744,7 +744,8 @@ drwxr-xr-x 4 goik fb1prof 4096 Nov  8 22:04 ..
       </qandaset>
       <para>We may as well represent our current physical SQL model
-      graphically:</para>
+      graphically. The annotation <quote>(NN)</quote> denotes <quote>not
+      nullable</quote>:</para>
       <figure xml:id="fig_GraphModelEmployee">
         <title>Graphical representation of employees' model.</title>
@@ -756,6 +757,60 @@ drwxr-xr-x 4 goik fb1prof 4096 Nov  8 22:04 ..
         </mediaobject>
       </figure>
+      <para>We now turn to XML representation of data. Completely disregarding
+      integrity constraints we may use a so called <emphasis>well
+      formed</emphasis> XML file representation:</para>
+
+      <programlisting language="xml">&lt;?xml version="1.0" encoding="UTF-8"?&gt;
+&lt;employee&gt;
+    &lt;id&gt;21&lt;/id&gt;
+    &lt;givenName&gt;Bob&lt;/givenName&gt;
+    &lt;surname&gt;Hope&lt;/surname&gt;
+    &lt;birthday&gt;1982-07-22&lt;/birthday&gt;
+    &lt;sex&gt;m&lt;/sex&gt;
+    &lt;email&gt;hope@exploitation.com&lt;/email&gt;
+    &lt;phone&gt;1123-33244&lt;/phone&gt;
+&lt;/employee&gt;</programlisting>
+
+      <qandaset defaultlabel="qanda">
+        <title>Well-formed XML data questions</title>
+
+        <qandadiv>
+          <qandaentry>
+            <question>
+              <para>Explain the meaning of the <code
+              language="xml">version="1.0"</code> prologue attribute.</para>
+            </question>
+
+            <answer>
+              <para>The version attribute allows for an evolving XML standard.
+              This way XML Parsers are still able to parse XML documents
+              belonging to older versions.</para>
+
+              <para>For example XML documents adhering to the (unsuccessful)
+              <link xlink:href="http://www.w3.org/TR/xml11/#sec-xml11">XML
+              1.1</link> Standard may be analyzed by a parser accordingly by
+              reading the prologue to apply the respective rule set.</para>
+            </answer>
+          </qandaentry>
+
+          <qandaentry>
+            <question>
+              <para>Explain the meaning of <code
+              language="xml">encoding="UTF-8" prologue attribute. What about
+              other values</code> than <code>UTF-8</code> ?</para>
+            </question>
+
+            <answer>
+              <para>XML allows for choosing an encoding like <code
+              language="xml">encoding="US-ASCII"</code> or <code
+              language="xml">encoding="ISO-8859-1" for western European
+              countries</code>.</para>
+            </answer>
+          </qandaentry>
+        </qandadiv>
+      </qandaset>
+
       <para>Some SQL data types are quite appropriate. We may however add
       further restrictions to enhance data integrity. The attribute
       <code>SEX</code> for example may be restricted to allow only 'm' and