<?xml version="1.0"?>
<!-- edited with XML Spy v4.3 U (http://www.xmlspy.com) by Richard R. Liu (private) -->
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook V3.1//EN" "file:///D:/xmltools/docbook/docbkx412/docbookx.dtd" [
	<!ENTITY contributors "Martin Maier, Oliver Margraf">
]>
<book>
	<title>Questions and Answers on Document Construction with XML</title>
	<bookinfo>
		<releaseinfo revisionflag="added">Version 0.1</releaseinfo>
	</bookinfo>
	<preface>
		<title>Purpose of this Q and A type document</title>
		<para>
   The purpose of this list is to check and enhance the <emphasis>understanding</emphasis>
of XML use in the areas of publishing and industry schemas.</para>
		<para>Of course knowledge about specific XML technologies is needed as well, so the questions go from more complex ones which offer opportunities for design discussions to simpler ones which cover specific technologies.</para>
		<para>I would like to thank &contributors; for contributing to this list.</para>
	</preface>
	<chapter>
		<title>Markup Languages in General</title>
		<para></para>
		<section>
			<title>XML and HTML</title>
			<para>HTML, XHTML and XML are all so called markup languages. This raises some questions about general
concepts of markup languages as well as what makes them different.</para>
			<qandaset>
				<qandaentry lang="en">
					<question>
						<para>What makes markup languages different e.g. from the concept used by WYSIWYG editors 
like word, wordperfect, Quark Express etc?</para>
					</question>
					<answer>
						<para></para>
					</answer>
				</qandaentry>
				<qandaentry lang="de">
					<question>
						<para>Was macht markup Sprachen anders im Vergleich zu WYSIWIG Editoren wie Word, Wordperfekt, Quark Express etc?</para>
					</question>
					<answer>
						<para></para>
					</answer>
				</qandaentry>
				<qandaentry lang="en">
					<question>
						<para>What is the advantage of a document written in XML compared to proprietary formats like Word, Quark Express etc.</para>
					</question>
					<answer>
						<para></para>
					</answer>
				</qandaentry>
				<qandaentry lang="de">
					<question>
						<para>Welchen Vorteil bringt ein XML Dokument im Vergleich zu propiet&auml;ren Formaten wie Word, Quark Express etc?</para>
					</question>
					<answer>
						<para></para>
					</answer>
				</qandaentry>
				<qandaentry>
					<question lang="en">
						<para>What are the main differences between XML and HTML?</para>
						<tip>
							<para>Could you e.g. express a database record well in HTML? Think about what kind of tags are available and what their main purpose is.</para>
						</tip>
					</question>
					<answer lang="en">
						<para></para>
					</answer>
				</qandaentry>
				<qandaentry>
					<question lang="de">
						<para>Nennen Sie die wesentlichen Unterschiede zwischen XML und HTML.</para>
						<tip>
							<para>K&ouml;nnten Sie einen Datanbank Rekord gut in HTML ausdr&uuml;cken? Was f&uuml;r Tags sind verf&uuml;gbar und welchem Zweck dienen sie in erster Linie?.</para>
						</tip>
					</question>
					<answer lang="de">
						<para></para>
					</answer>
				</qandaentry>
				<qandaentry>
					<question>
						<para>XML is said to be extensible and HTML not. Explain</para>
						<tip>
							<para>Think about who decides which tags are allowed?</para>
						</tip>
					</question>
					<answer>
						<para></para>
					</answer>
				</qandaentry>
				<qandaentry>
					<question>
						<para>In the above question, is the <quote>extensibility</quote> of XML something technical or something political/social?</para>
						<tip>
							<para>Can you extend <emphasis>every</emphasis> xml schema?</para>
						</tip>
					</question>
					<answer>
						<para></para>
					</answer>
				</qandaentry>
				<qandaentry lang="en">
					<question>
						<para>What is the advantage of using UNICODE compared to ASCII in XML documents?</para>
						<tip>
							<para>Think about WHERE xml will be used?</para>
						</tip>
					</question>
					<answer>
						<para></para>
					</answer>
				</qandaentry>
				<qandaentry lang="de">
					<question>
						<para>Was ist der Vorteil von XML Dokumenten in Unicode anstatt ASCII?</para>
						<tip>
							<para>Denken Sie daran wo XML &uuml;berall benutzt werden kann?</para>
						</tip>
					</question>
					<answer>
						<para></para>
					</answer>
				</qandaentry>
			</qandaset>
		</section>
	</chapter>
	<chapter>
		<title>Xtended Markup Language XML</title>
		<para></para>
		<section>
			<title>XML parts</title>
			<para>Here we take a look at the main parts of an XML file.</para>
			<qandaset>
				<qandaentry>
					<question>
						<para>What are the main ingredients of an xml instance that you will most likely need or encounter in documents?</para>
					</question>
					<answer>
						<para>XML declaration, element tags, attributes, comments, processing instructions, name space declarations and entities</para>
					</answer>
				</qandaentry>
				<qandaentry lang="en">
					<question>
						<para>Does an XML instance always need a DTD?</para>
					</question>
					<answer>
						<para></para>
					</answer>
				</qandaentry>
				<qandaentry lang="de">
					<question>
						<para>Braucht eine XML Instanz immer eine DTD?.</para>
					</question>
					<answer>
						<para></para>
					</answer>
				</qandaentry>
				<qandaentry lang="en">
					<question>
						<para>Explain the meaning of <markup>* + ?</markup> in einer DTD?</para>
					</question>
					<answer>
						<para>"*" means zero, one or many occurrences of an element in an XML instance are legal. "+" means that an element needs to be there at least once but possibly more often and "?" means that an element can be there or not.</para>
					</answer>
				</qandaentry>
				<qandaentry lang="de">
					<question>
						<para>Erkl&auml;ren Sie die Bedeutung von <markup>* + ?</markup> in einer DTD?.</para>
					</question>
					<answer>
						<para>"*" bedeutet keinmal, einmal oder beliebig oft kann ein Element in der XML Instanz vorkommen. "+" bedeutet mindestens einmal aber auch mehrmals und "?" bedeutet einmal oder keinmal ist legal.</para>
					</answer>
				</qandaentry>
				<qandaentry lang="en">
					<question>
						<para>Explain the meaning of <markup>#REQUIRED, #IMPLIED, #FIXED when used in the definition of attributes?</markup>
						</para>
						<tip>
							<para>What would you like to enforce about the use of attributes? What if the value of an attribute would always be the same?</para>
						</tip>
					</question>
					<answer>
						<para></para>
					</answer>
				</qandaentry>
				<qandaentry lang="de">
					<question>
						<para>Erkl&auml;ren Sie die Bedeutung von <markup>#REQUIRED, #IMPLIED, #FIXED bei der Definition eines Attributes?</markup>
						</para>
						<tip>
							<para>Was m&ouml;chten Sie bei Attributen eventuell erzwingen? Was ist wenn der Wert eines Attributes immer gleich ist?</para>
						</tip>
					</question>
					<answer>
						<para>.</para>
					</answer>
				</qandaentry>
				<qandaentry lang="en">
					<question>
						<para>A DTD defines a catalog element. Add an attribute "created" to this element.</para>
							<markup><![CDATA[ <!ELEMENT catalog (#PCDATA)> ]]></markup>
					</question>
					<answer>
						<para>.</para>
					</answer>
				</qandaentry>
				<qandaentry lang="de">
					<question>
						<para>Eine DTD definiert ein katalog Element. F&uuml;gen Sie ein Attribute "erstellt" hinzu.</para>
							<markup><![CDATA[ <!ELEMENT katalog (#PCDATA)> ]]></markup>
					</question>
					<answer>
						<para></para>
					</answer>
				</qandaentry>
				<qandaentry>
					<question>
						<para>What is the purpose of attributes in XML. Do you have to use them? Give some guiding rules for the use of attributes.</para>
						<tip>
							<para>Think about extensibility. How does this differ between attributes and elements? Think about your application and how it will react.</para>
						</tip>
					</question>
					<answer>
						<para></para>
					</answer>
				</qandaentry>
				<qandaentry lang="en">
					<question>
						<para>What happens in the following fragment of an instance when it is parsed?</para>
							<markup><![CDATA[ <!ENTITY bmw "Bayrische Motorenwerke" > <text>And the worlds best motorbikes come from &bmw; in Munich </text> ]]></markup>
					</question>
					<answer>
						<para></para>
					</answer>
				</qandaentry>
				<qandaentry lang="de">
					<question>
						<para>Was passiert wenn folgendes Fragment einer Instanz durch den Parser geht?</para>
							<markup><![CDATA[ <!ENTITY bmw "Bayrische Motorenwerke" > <text> Und die besten Motorr&auml;der der Welt kommen von &bmw; in M&uuml;chen </text> ]]></markup>
					</question>
					<answer>
						<para></para>
					</answer>
				</qandaentry>
				<qandaentry>
					<question>
						<para>What kind of definitions are used in DTDs?</para>
						<tip>
							<para>Think about the xml parts that show up in instances. How are they defined?</para>
						</tip>
					</question>
					<answer>
						<para></para>
					</answer>
				</qandaentry>
				<qandaentry>
					<question>
						<para>In the above question, is the <quote>extensibility</quote> of XML something technical or something political/social?</para>
						<tip>
							<para>Can you extend <emphasis>every</emphasis> xml schema?</para>
						</tip>
					</question>
					<answer>
						<para></para>
					</answer>
				</qandaentry>
			</qandaset>
		</section>
		<section>
			<title>Namespaces in XML</title>
			<para>This section covers namespace use in XML.</para>
			<qandaset>
				<qandaentry>
					<question>
						<para>The example below shows an XML fragment. What does it mean?</para>
						<markup>xml namespace decl and use goes here</markup>
					</question>
					<answer>
						<para></para>
					</answer>
				</qandaentry>
				<qandaentry>
					<question>
						<para>What are namespaces mainly used for in XML?</para>
						<tip>
							<para>
XML lets you define your own tags. Think about the consequences if everybody does define their own tags.</para>
						</tip>
					</question>
					<answer>
						<para>Eindeutigkeit 
               Kontext. 
               Namensraum wird verwendet um die XSL-Tags von anderen Tags zu unterscheiden ( ? ) </para>
					</answer>
				</qandaentry>
			</qandaset>
			<qandaset>
				<qandaentry>
					<question>
						<para>Geben Sie f&uuml;r jedes Element und Attribut des abgebildeten XML-Dokuments den zutreffenden Namensraum an. 
. </para>
						<para>
							<markup/>
						</para>
					</question>
					<answer>
						<para></para>
					</answer>
				</qandaentry>
			</qandaset>
		</section>
	</chapter>
	<chapter>
		<title>XML examples</title>
		<para></para>
		<section>
			<title>XML instances</title>
			<para>Here we take a look at some specific features of XML instances.</para>
			<qandaset>
				<qandaentry>
					<question>
						<para>The example below shows a xml segment. Can you explain what you see and what it might be?</para>
					</question>
					<answer>
						<para>Creating relations in XML documents</para>
					</answer>
				</qandaentry>
				<qandaentry>
					<question>
						<para>The example shows two different means of creating relatins within XML. One uses special XML features while the other one is made by the authors themselves. Explain both mechanisms and tell which one is application specific?</para>
						<tip>
							<para>a segment of JDF linking is shown.</para>
						</tip>
					</question>
					<answer>
						<para></para>
					</answer>
				</qandaentry>
				<qandaentry>
					<question>
						<para>In the above question, is the <quote>extensibility</quote> of XML something technical or something political/social?</para>
						<tip>
							<para>Can you extend <emphasis>every</emphasis> xml schema?</para>
						</tip>
					</question>
					<answer>
						<para></para>
					</answer>
				</qandaentry>
				<qandaentry lang="en">
					<question>
						<para>Given the following XML instance, write a proper DTD for it: </para>
							<markup><![CDATA[            <CD>

                         <artist>....................</artist>

                        <title>................................</title>

                        <price>...............................</price>

            </CD> ]]></markup>
					</question>
					<answer>
						<para></para>
					</answer>
				</qandaentry>
				<qandaentry lang="de">
					<question>
						<para>Schreiben Sie eine DTD f&uuml;r die folgende XML Instanz: </para>
							<markup><![CDATA[            <CD>

                         <Interpret>....................</Interpret>

                        <Title>................................</Title>

                        <Preis>...............................</Preis>

            </CD> ]]></markup>
					</question>
					<answer>
						<para></para>
					</answer>
				</qandaentry>
			</qandaset>
		</section>
	</chapter>
	<chapter>
		<title>Modelling XML information</title>
		<para>Modelling XML information (using DTDs or XML Schema or something else like Relax NG) is perhaps the most time consuming and important task. Only topped by the effort to create an industry-wide schema like JDF.</para>
		<section>
			<title>General questions about modelling</title>
			<para>This section covers questions about when to use what modelling construct (DTD, schema etc.).</para>
			<qandaset>
				<qandaentry lang="en">
					<question>
						<para>What is a Document Type Definition and what does it?</para>
						<tip>
							<para>Think about the advantages with respect to the correctness of a document</para>
						</tip>
					</question>
					<answer>
						<para></para>
					</answer>
				</qandaentry>
				<qandaentry lang="de">
					<question>
						<para>Welche Bedeutung hat eine DTD? Was wird darin definiert?</para>
						<tip>
							<para>Denken Sie an die Vorteile in Bezug auf die Korrektheit eines Dokuments. Korrekt gegen&uuml;ber was?</para>
						</tip>
					</question>
					<answer>
						<para></para>
					</answer>
				</qandaentry>
				<qandaentry>
					<question>
						<para>You and your friends are all heavy into lounge music from Paris and you decide to share information about CDs that you own or want to have. With ratings etc. Whhat would be the advantage of creating a DTD if you want to share this info?</para>
						<tip>
							<para>Think about what happened when we created instances of our catalog without a dtd first. We had some model, yes, but....</para>
						</tip>
					</question>
					<answer>
						<para></para>
					</answer>
				</qandaentry>
				<qandaentry lang="en">
					<question>
						<para>Some XML instances are called <phrase>well-formed</phrase> and others are called<phrase> valid</phrase>? What is the difference?</para>
						<tip>
							<para>Think about what you need for a document to be valid. Certain elements? Or just good looking tags?</para>
						</tip>
					</question>
					<answer>
						<para>.</para>
					</answer>
				</qandaentry>
				<qandaentry lang="de">
					<question>
						<para>Was ist ein g&uuml;ltiges und was ein wohlgeformtes XML-Dokument?</para>
						<tip>
							<para>Denken Sie daran was Sie brauchen damit ein Dokument valide sein kann. Gewisse Elemente oder nur Tags die gut aussehen?</para>
						</tip>
					</question>
					<answer>
						<para>Wohlgeformt: 
                    Tags stimmen &uuml;berein. Auf jedes &ouml;ffnende Tag gibt es auch ein schlie&szlig;endes Tag. 
                    es gibt eine Wurzel. G&uuml;ltig dann wenn es wohlgeformt ist, 
                    Dokument verweist auf eine DTD 
                    Dokument h&auml;lt die DTD auch ein  </para>
					</answer>
				</qandaentry>
				<qandaentry>
					<question>
						<para>Exactly what allows a Document Type Definition to be checked? The existence of certain elements? The order of elements? The proper text in elements? </para>
						<tip>
							<para>Think about creating a valid instance of xml that fits to a DTD. What can you type in without getting an error and where does the parser or editor tell you that it is wrong?</para>
						</tip>
					</question>
					<answer>
						<para>Order of elements, number of elements and types of attributes can be checked. There is no way to check whether an elements text is OK except if it has been declared as empty and contains text.</para>
					</answer>
				</qandaentry>
				<qandaentry>
					<question>
						<para>Look at the example XML instance and DTD below and say if the instance is a proper instance with respect to the DTD or if there are mistakes in the instance. Which mistakes would you fix where?</para>
						<tip>
							<para>The mistake can be in instance (e.g. if the DTD defines an element that the instance does not have) or it can be in the DTD because it does not correctly fit to our model that we need.</para>
						</tip>
						<para>
						<markup>Example of instance with missing element and dtd with wrong cardinality</markup>
            </para>
					</question>
					<answer>
						<para></para>
					</answer>
				</qandaentry>
				<qandaentry>
					<question>
						<para>Was ist der Unterschied zwischen einem DTD und XML-Schema ?

              </para>
					</question>
					<answer>
						<para>  beide beschreiben die Grammatik eines XML Dokus, aber: 
               XML-Schema ist in XML Syntax formuliert (???) 
               DTD hat nur beschr&auml;nkte Datentypen und Inhalte 
               XML-Format erm&ouml;glicht die Verwendung der XML-Techniken (XLink, XSL) sowie der bestehenden XML-Applikationen f&uuml;r XML-Schema</para>
					</answer>
				</qandaentry>
				<qandaentry lang="en">
					<question>
						<para>What is the alternative to a Document Type Definition (DTD) and when would you use it?</para>
						<tip>
							<para>DTDs where invented first and used a lot by authors and publishers. With XML more and more programmatic use has become popular e.g. to represent database records or programming language types in XML.</para>
						</tip>
					</question>
					<answer>
						<para></para>
					</answer>
				</qandaentry>
				<qandaentry lang="de">
					<question>
						<para>Was kann man alternativ zu einer DTD verwenden und wann tut man das in erster Linie?</para>
						<tip>
							<para>DTDs wurden zuerst erfunden und vor allem von Autoren viel genutzt. Durch XML ist auch die Nutzhung in Programmen stark vermehrt worden, z.B. um Datenbank Eintr&auml;ge oder Typen aus Programmiersprachen abzubilden in XML.</para>
						</tip>
					</question>
					<answer>
						<para></para>
					</answer>
				</qandaentry>
				<qandaentry>
					<question>
						<para>You have some very data oriented information that needs to get modelled. What construct: DTD or XML schema would you pick for the job and why?</para>
						<tip>
							<para>Think about what makes data <emphasis>correct</emphasis> and how you would express and check correctness.</para>
						</tip>
					</question>
					<answer>
						<para></para>
					</answer>
				</qandaentry>
				<qandaentry>
					<question>
						<para>You need to write a book or article and you want it transformed into html and pdf with little effort from your side. What modell for your text comes to mind?</para>
					</question>
					<answer>
						<para>If you decide to use docbook e.g., you will get a model that will certainly cover your needs with respect to publishing constructs (from book and authorinfo over references, mediaobjects, indexes and table of contents etc. And on top of it there exist free rendering stylesheets to produce various output formats</para>
					</answer>
				</qandaentry>
			</qandaset>
		</section>
		<section>
			<title>Practical modelling</title>
			<para>This section covers creating models for different subjects.</para>
			<qandaset>
				<qandaentry>
					<question>
						<para>You want to create a model for your CD collection. How would you structure this model? Just create a model first, don't use XML yet.</para>
						<tip>
							<para>Think about what you want to say about your collection and what it contains.</para>
						</tip>
					</question>
					<answer>
						<para></para>
					</answer>
				</qandaentry>
				<qandaentry>
					<question>
						<para>Create a DTD from your model of the CD-collection. Don't use fancy constructs. Keep it simple with elements and perhaps one or two attributes.</para>
					</question>
					<answer>
						<para></para>
					</answer>
				</qandaentry>
				<qandaentry>
					<question>
						<para>Create an XML instance of your CD-collection that fits to your DTD.</para>
					</question>
					<answer>
						<para></para>
					</answer>
				</qandaentry>
				<qandaentry>
					<question>
						<para>Create a tiny stylesheet for your xml instance.</para>
						<tip>
							<para>Use only the rule-based (or the fill in the blanks) pattern - no programming. use <markup> xsl:template match=""</markup> and <markup>xsl:value-of select=""</markup> and whatever HTML primitives you like.  </para>
						</tip>
					</question>
					<answer>
						<para></para>
					</answer>
				</qandaentry>
			</qandaset>
		</section>
	</chapter>
	<chapter>
		<title>XML tools</title>
		<para>Certain tasks nowadays require special tools like good xml editors and schema validators. An example of this is certainly the Job Definition Format with its complex schema. You want some good xml editor for that. But what makes an XML Editor different?</para>
		<section>
			<title>Editing XML</title>
			<qandaset>
				<qandaentry lang="en">
					<question>
						<para>Do you really need special software to create or edit XML documents? Please explain</para>
					</question>
					<answer>
						<para></para>
					</answer>
				</qandaentry>
				<qandaentry lang="de">
					<question>
						<para>Ben&ouml;tigen Sie zum Erstellen eines XML-Dokuments unbedingt eine spezielle Software? (Antwort mit Begr&uuml;ndung) </para>
					</question>
					<answer>
						<para></para>
					</answer>
				</qandaentry>
				<qandaentry>
					<question>
						<para>How can a XML editor help you creating and editing xml files that a normal text editor cannot do?</para>
					</question>
					<answer>
						<para></para>
					</answer>
				</qandaentry>
				<qandaentry>
					<question>
						<para>Does it make a difference for the xml editor if you have a DTD and what can it do with a DTD?</para>
					</question>
					<answer>
						<para></para>
					</answer>
				</qandaentry>
				<qandaentry>
					<question>
						<para>XML is said to leave the authors in control of their data or texts? Can you explain how this is meant? Why is this not so with other formats?</para>
						<tip>
							<para>
Think about changing to a different word processor with a large collection of documents in the format of your current processor. Is that switch easy? How does it look in the case with XML?</para>
						</tip>
					</question>
					<answer>
						<para></para>
					</answer>
				</qandaentry>
			</qandaset>
		</section>
	</chapter>
	<chapter>
		<title>XML Parsen</title>
		<para></para>
		<section>
			<title>XML Parser</title>
			<qandaset>
				<qandaentry lang="en">
					<question>
						<para>Two different types of XML parsers exist. Name them and explain the difference.</para>
						<tip>
							<para>Some parsers need to be extremely small and fast. And in some cases the user or application <emphasis>knows</emphasis> that the instance is already correct with respect to a DTD and all that is needed is to read in the XML instance and break it up into its parts.</para>
						</tip>
					</question>
					<answer>
						<para>Validating parsers always check the instance against the DTD. Non-validating parsers will only check if an instance is well-formed. They are of course a bit faster than validating parsers.</para>
					</answer>
				</qandaentry>
				<qandaentry lang="de">
					<question>
						<para>Es gibt zwei verschiedene Typen von XML Parsern. Nennen Sie die beiden Typen und erkl&auml;ren Sie den Unterschied.</para>
						<tip>
							<para>Einige Parser m&uuml;ssen extrem klein und schnell sein. Und in einigen F&auml;llen ist es der Applikation <emphasis>bekannt</emphasis> dass die Instanz korrekt bez&uuml;glich einer DTD ist und dass alles was n&ouml;tig ist das Einlesen der Instanz und das Aufbrechen in ihre Teile ist.</para>
						</tip>
					</question>
					<answer>
						<para>Validierende Parser pr&uuml;fen immer die Instanz gegen die DTD. Nicht-validierende Parser pr&uuml;fen nur dass die Instanz well-formed ist. Sie sind deshalb etwas kleiner und schneller als validierende Parser.</para>
					</answer>
				</qandaentry>
				<qandaentry lang="en">
					<question>
						<para>Two different types of XML parsing mechanisms exist. Name them and explain the difference.</para>
						<tip>
							<para>Think about how an application might want the results of the parsing process to be delivered to it. An editor application probably wants the parsing results in memory while a filter or search application only looks for one piece of a document and does not want to allocate a lot of memory for the whole document. This is also a problem with very large documents.</para>
						</tip>
					</question>
					<answer>
						<para>So called DOM (document object model) parser parse the instance and create an in memory representation of the whole document using node objects. The application gets the whole tree of nodes for further processing. They are good for editing etc. SAX parsers instead send only events about which element they have just found to the application and let the application decide what to do with it (allocate memory and store it or inspect the element and throw it away.</para>
					</answer>
				</qandaentry>
				<qandaentry lang="de">
					<question>
						<para>Zwei verschiedene XML Parsing Mechanismen existieren. Welche sind das und was ist der Unterschie?.</para>
						<tip>
							<para>Denken Sie daran wie Applikationen die Resultate des Parsing Prozesses zugestellt haben m&ouml; Ein Editor will wahrscheinlich das ganze Ergebnis im Speicher halten w&auml;hrend eine Filter oder Such-Applikation nur nach einem Teil des Dokuments sucht und nicht Memory f&uuml; das ganze Dokument allokieren m&ouml;chte. Das ist auch ein Problem bei sehr grossen Dokumenten.</para>
						</tip>
					</question>
					<answer>
						<para>Sogenannte DOM (Document Object Model) Parser parsen die ganze Instanz und erzeugen eine Darstellung des ganzen Dokuments in Form von Node Objekten im Speicher. Die Applikation bekommt den ganzen Baum aus Nodes zur weiteren Verarbeitung. Solche Parser sind gut f&uuml; Editor Applikationen. SAX Parser hingegen melden nur per Event an die Applikation welches Element sie gerade gefunden haben und lassen der Applikation entscheiden was damit passieren soll. Memory zum speichern allokieren oder nur anschauen und wegwerfen?.</para>
					</answer>
				</qandaentry>
			</qandaset>
		</section>
	</chapter>
	<chapter>
		<title>Transforming and rendering XML</title>
		<section>
			<title>Transforming</title>
			<para></para>
		</section>
		<section>
			<title>Rendering</title>
			<para>Here we dicuss how XML documents can be rendered into different output formats</para>
			<qandaset>
				<qandaentry lang="en">
					<question>
						<para>How is the mechanism called that allows rendering or transformation of XML documents?</para>
					</question>
					<answer>
						<para>Extended Style Sheet language XSL and XSLT processor</para>
					</answer>
				</qandaentry>
				<qandaentry lang="de">
					<question>
						<para>Welches Mittel verwenden Sie um XML in verschieden Ausgabeformaten darzustellen?</para>
					</question>
					<answer>
						<para>Extended Style Sheet language XSL und XSLT processor</para>
					</answer>
				</qandaentry>
			</qandaset>
			<qandaset>
				<qandaentry>
					<question>
						<para>Given the instance and stylesheet below and what would an xslt processor produce from it?</para>
						<markup></markup>
					</question>
					<answer>
						<para></para>
					</answer>
				</qandaentry>
			</qandaset>
		</section>
	</chapter>
	<chapter>
		<title>Special Industry Schemas</title>
		<para>A collection of important industry schemas is discussed here </para>
		<section>
			<title>Job Definition Format for the printing and media industry</title>
			<para></para>
			<qandaset>
				<qandaentry lang="en">
					<question>
						<para>What is the advantage of JDF compared to other job ticket formats like PPF, PJTF?</para>
					</question>
					<answer>
						<para></para>
					</answer>
				</qandaentry>
				<qandaentry lang="de">
					<question>
						<para>Welchen Vorteil bringt JDF gegen&uuml;ber anderen Jobtickets wie PPF, PJTF?</para>
					</question>
					<answer>
						<para></para>
					</answer>
				</qandaentry>
				<qandaentry lang="en">
					<question>
						<para>Give a short explanation of the following JDF components: Agent, Controller, Device, Engine</para>
					</question>
					<answer>
						<para></para>
					</answer>
				</qandaentry>
				<qandaentry lang="de">
					<question>
						<para>Erl&auml;utern Sie in Stichworten die Aufgaben folgender JDF-Komponenten: Agent, Controller, Ger&auml;t, Maschine?</para>
					</question>
					<answer>
						<para></para>
					</answer>
				</qandaentry>
				<qandaentry lang="en">
					<question>
						<para>Give a short explanation of the following JDF core elements: node and resource</para>
					</question>
					<answer>
						<para></para>
					</answer>
				</qandaentry>
				<qandaentry lang="de">
					<question>
						<para>Erl&auml;utern Sie in Stichworten die Aufgaben folgender JDF Kernelemente: Node und Resource</para>
					</question>
					<answer>
						<para></para>
					</answer>
				</qandaentry>
			</qandaset>
		</section>
	</chapter>
</book>
