Skip to content
Snippets Groups Projects
Commit 53b5f032 authored by Goik Martin's avatar Goik Martin
Browse files

DTD --> Schema

parent 35c600e6
No related branches found
No related tags found
No related merge requests found
Hide whitespace changes
Inline Side-by-side
Showing
with 56 additions and 44 deletions
Sda1/sda1.xml
+ 56
− 44
View file @ 53b5f032
......@@ -3641,12 +3641,13 @@ INSERT INTO Customer (id, name) VALUES ('eve', 'Eve intruder')</computeroutput><
 
<itemizedlist>
<listitem>
<para>Some elements being central for a DTD may appear at
different places. For example a <tag class="starttag">title</tag>
element is likely to appear as a child of chapters, sections,
tables figures and so on. It may be sufficient to define a single
template with a <code>match="title"</code> attribute which
contains all rules being required.</para>
<para>Some elements may appear at different places of a given
document hierarchy. For example a <tag
class="starttag">title</tag> element is likely to appear as a
child of chapters, sections, tables figures and so on. It may be
sufficient to define a single template with a
<code>match="title"</code> attribute which contains all rules
being required.</para>
</listitem>
 
<listitem>
......@@ -4377,17 +4378,25 @@ you need some </emphasis>&lt;em&gt;time&lt;/em&gt;<emphasis role="bold">.</empha
<para>The <abbrev
xlink:href="http://www.w3.org/TR/xpath">XPath</abbrev>
expression <code>select="text()|emphasis|url"</code> corresponds
nicely to the content model definition in the DTD:</para>
<programlisting language="none">&lt;!ELEMENT content (#PCDATA|emphasis|url)*&gt;</programlisting>
nicely to the schema's content model definition:</para>
<programlisting language="none">&lt;xs:element name="content"&gt;
&lt;xs:complexType <emphasis role="bold">mixed="true"</emphasis>&gt;
&lt;xs:choice minOccurs="0" maxOccurs="unbounded"&gt;
&lt;xs:element <emphasis role="bold">ref="emphasis"</emphasis>/&gt;
&lt;xs:element <emphasis role="bold">ref="url"</emphasis>/&gt;
&lt;/xs:choice&gt;
...
&lt;/xs:complexType&gt;
&lt;/xs:element&gt;</programlisting>
</listitem>
 
<listitem>
<para>In most mixed content models <emphasis>all</emphasis> sub
elements of e.g. <tag class="starttag" role="">content</tag>
have to be formatted. During development some of the elements
defined in a DTD are likely to be omitted by accidence. For this
reason the <quote>typical</quote> <abbrev
defined in a schema are likely to be omitted by accidence. For
this reason the <quote>typical</quote> <abbrev
xlink:href="http://www.w3.org/TR/xpath">XPath</abbrev>
expression acting on mixed content models is defined to match
<emphasis>any</emphasis> sub element nodes:</para>
......@@ -4555,10 +4564,11 @@ you need some </emphasis>&lt;em&gt;time&lt;/em&gt;<emphasis role="bold">.</empha
<qandaentry>
<question>
<para>In <xref linkend="example_book.dtd_v5"/> we
constructed a DTD allowing itemized lists an mixed content
for <tag class="starttag">book</tag> instances. This DTD
also allowed to define <tag class="starttag">emphasis</tag>,
<tag class="starttag">table</tag> and <tag
constructed a schema allowing itemized lists and mixed
content for <tag class="starttag">book</tag> instances. This
schema also allowed to define <tag
class="starttag">emphasis</tag>, <tag
class="starttag">table</tag> and <tag
class="starttag">link</tag> elements being part of a mixed
content definition. Extend the current book2html.xsl to
account for these extensions.</para>
......@@ -4773,11 +4783,11 @@ you need some </emphasis>&lt;em&gt;time&lt;/em&gt;<emphasis role="bold">.</empha
 
<para>The call to <code>id(@linkend)</code> returns either a
<tag class="starttag">chapter</tag> or a <tag
class="starttag">para</tag> node since according to the DTD
attributes of type <code>ID</code> are only defined for
these two elements. Using this node as input to
<code>generate-id()</code> returns the desired identity
value for the generated Xhtml.</para>
class="starttag">para</tag> node since attributes of type
<code>ID</code> are only defined for these two elements.
Using this node as input to <code>generate-id()</code>
returns the desired identity value to be used in the
generated Xhtml.</para>
</answer>
</qandaentry>
</qandadiv>
......@@ -4790,8 +4800,8 @@ you need some </emphasis>&lt;em&gt;time&lt;/em&gt;<emphasis role="bold">.</empha
<para>XSL allows us to traverse a document instance's graph in
different directions. We start with a memo document instance:</para>
 
<programlisting language="none">&lt;!DOCTYPE memo SYSTEM "memo.dtd"&gt;
&lt;memo date="9.9.2099"&gt;
<programlisting language="none">&lt;memo xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="memo.xsd" date="9.9.2099"&gt;
&lt;from&gt;Joe&lt;/from&gt;
&lt;to&gt;Jack&lt;/to&gt;
&lt;to&gt;Eve&lt;/to&gt;
......@@ -5677,7 +5687,7 @@ Closing Document
 
<listitem>
<para>The parser will not validate a document instance against a
DTD being present.</para>
schema being present.</para>
</listitem>
</itemizedlist>
 
......@@ -6189,29 +6199,39 @@ public class MemoViewHandler extends DefaultHandler {
<figure xml:id="saxNotValid">
<title>An invalid XML document.</title>
 
<programlisting language="none">&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;!DOCTYPE catalog [
&lt;!ELEMENT catalog (item) &gt;
&lt;!ELEMENT item (#PCDATA) &gt;
&lt;!ATTLIST item orderNo NMTOKEN #REQUIRED &gt;
]&gt;
&lt;catalog&gt;
<programlisting language="none">&lt;xs:element name="catalog"&gt;
&lt;xs:complexType&gt;
&lt;xs:sequence&gt;
&lt;xs:element ref="item"/&gt;
&lt;/xs:sequence&gt;
&lt;/xs:complexType&gt;
&lt;/xs:element&gt;
&lt;xs:element name="item"&gt;
&lt;xs:complexType mixed="true"&gt;
&lt;xs:attribute name="orderNo" type="xs:int" use="required"/&gt;
&lt;/xs:complexType&gt;
&lt;/xs:element&gt;</programlisting>
<programlisting language="none">&lt;catalog&gt;
&lt;item orderNo="3218"&gt;Swinging headset&lt;/item&gt;
&lt;item orderNo="9921"&gt;200W Stereo Amplifier&lt;/item&gt;
&lt;item orderNo="9921"&gt;200W Stereo Amplifier&lt;/item&gt; <emphasis
role="bold">&lt;!-- second entry forbidden by schema --&gt;</emphasis>
&lt;/catalog&gt;</programlisting>
 
<caption>
<para>In contrast to <xref linkend="saxMissItem"/> this document
is well formed. But it is not <emphasis
role="bold">valid</emphasis> with respect to the DTD grammar since
more than one <tag class="starttag">item</tag> elements are
role="bold">valid</emphasis> with respect to the schema since more
than one <tag class="starttag">item</tag> elements are
present.</para>
</caption>
</figure>
 
<para>This document instance is well-formed but not valid. The parser
will not report any error or warning. In order to enable validation we
need to configure our parser:</para>
<para>This document instance is well-formed but not valid: Only one
element <tag class="starttag">item</tag> is allowed due to an
ill-defined schema. The parser will not report any error or warning.
In order to enable validation we need to configure our parser:</para>
 
<programlisting language="none">xmlReader.setFeature("http://xml.org/sax/features/validation", true);</programlisting>
 
......@@ -6243,14 +6263,6 @@ public class MemoViewHandler extends DefaultHandler {
</varlistentry>
</variablelist>
 
<para>Though not strictly required SAX validation may need DTD related
(Entity) resolving. Having just SYSTEM identifier pointing to remote
network addresses like <code>... SYSTEM
"http://www.w3.org/2002/04/xhtml-math-svg/xhtml-math-svg.dtd
..."</code> may take a long time for download or even fail completely.
So XML catalog files are in order for validation being based on
locally available schemes or DTDs.</para>
<para>The <productname
xlink:href="http://projects.apache.org/projects/xml_commons_resolver.html">xml-commons
resolver project </productname>offers an implementation being able to
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment