{"id":68,"date":"2018-07-26T06:10:46","date_gmt":"2018-07-26T06:10:46","guid":{"rendered":"http:\/\/csp12.epgpbooks.inflibnet.ac.in\/?post_type=chapter&p=68"},"modified":"2022-01-06T12:03:57","modified_gmt":"2022-01-06T12:03:57","slug":"xmldtd","status":"publish","type":"chapter","link":"https:\/\/ebooks.inflibnet.ac.in\/csp12\/chapter\/xmldtd\/","title":{"rendered":"XMLDTD"},"content":{"raw":"
\r\n\r\n\u00a0 \u00a0 \u00a0Document Type Definitions<\/strong>\r\n\r\n \r\n

A DTD (Document Type Definition) describes the structure of one or more XML documents. Specifically, a DTD describes about Elements, Attributes and Entities defined in an XML document. An XML document is called a well-structured XML document if it follows certain simple syntactic rules and an XML document is called a valid XML document if it also specifies and conforms to a DTD.<\/p>\r\n \r\n\r\nThe need for DTDs<\/strong>\r\n\r\n \r\n

XML documents are designed to be processed by computer programs and if we can put just any<\/em> tags in an XML document, it\u2019s very hard to write a program that knows how to process the tags. A DTD specifies what tags may occur, when they may occur, and what attributes they may or must have. A DTD allows the XML document to be verified (shown to be legal) by the browser. A DTD that is shared across groups allows the groups to produce consistent XML documents.<\/p>\r\n\r\n<\/div>\r\n\u00a0 \u00a0 An XML example<\/strong>\r\n

\r\n\r\n \r\n\r\nFollowing is an simple example of an XML document.\r\n\r\n<nove l>\r\n\r\n<foreword>\r\n\r\n<paragraph>This is the great Indian novel.<\/ paragraph> <\/foreword>\r\n\r\n<chapter number=\"1\">\r\n\r\n<paragraph>It was a dark and stormy night.<\/paragraph> <paragraph>Suddenly, a shot rang out!\u00a0 \u00a0 \u00a0 <\/paragraph>\r\n\r\n<\/chapter>\r\n\r\n<\/novel>\r\n\r\n \r\n

This XML document contains elements and attributes and the DTD describes about the elements, such as <novel>, <foreword>, <chapter> and <paragraph>, consisting of tags<\/em> and content<\/em>. The element <novel> consists of elements <foreword> and <chapter>. The element <chapter> consists of attributes, such as number=\"1\", consisting of a name<\/em> and a value.<\/em><\/p>\r\nThis XML file is described with the following DTD,\r\n\r\n \r\n\r\nA DTD example<\/strong>\r\n\r\n \r\n\r\n<!DOCTYPE novel [\r\n\r\n<!ELEMENT novel (foreword, chapter+)>\r\n\r\n<!ELEMENT foreword (paragraph+)>\r\n\r\n<!ELEMENT chapter (paragraph+)>\r\n\r\n<!ELEMENT paragraph (#PCDATA)>\r\n\r\n<!ATTLIST chapter number CDATA #REQUIRED>\r\n\r\n]>\r\n\r\n \r\n

The DTD of an XML document starts with <!DOCTYPE root-element [ \u2026]> In this example we have defined as,<\/p>\r\n<!DOCTYPE novel [ \u2026]>\r\n\r\n \r\n

In an DTD the elements are described as<!ELEMENT\u2026> and attributes of the element are described as<\/p>\r\n<!ATTLIST \u2026.>.\r\n\r\n \r\n\r\nHere in this example, a novel consists of a foreword and one or more chapters, in that order. A foreword consists of one or more paragraphs. A chapter also consists of one or more paragraphs. A paragraph consists of parsed character data which means the text that cannot contain any other elements.\r\n\r\n \r\n\r\nEach chapter must have a number attribute given as \u201cREQUIRED\u201d.\r\n\r\n<\/div>\r\n\u00a0 \u00a0ELEMENT descriptions<\/strong>\r\n

\r\n\r\n \r\n

An element content can be another element or a list of child elements or it can be a text string or numeric value (character data).<\/p>\r\n \r\n

There are suffixes added to the element content where an element consists of zero, one or more occurences of the child elements. A (?) specifies optional or zero, (+) denotes one or more elements can occur and a (*) denotes zero or more of the elements can occur.<\/p>\r\n\r\n\r\n\r\n\r\n\r\n\r\n
?<\/td>\r\noptional<\/td>\r\nforeword?<\/td>\r\n<\/tr>\r\n
+<\/td>\r\none or more<\/td>\r\nchapter+<\/td>\r\n<\/tr>\r\n
*<\/td>\r\nzero or more<\/td>\r\nappendix*<\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\n

Seperators can also be added with the element declaration, that specifies the order of occurrence when the element has multiple number of child elements. There are two ways we can use to denote the order of occurrence. Using a comma (,) between the child elements specifies that the child elements will occur in the order given. Using a vertical line (|) means that either one or the other child element will occur.<\/p>\r\n

<\/p>\r\n\r\n<\/div>\r\n

\r\n\r\n\r\n\r\n\r\n
,<\/td>\r\nboth, in order<\/td>\r\nforeword?, chapter+<\/td>\r\n<\/tr>\r\n
|<\/td>\r\nor<\/td>\r\nsection|chapter<\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\nGrouping:<\/strong>\r\n\r\n \r\n

The elements can be grouped in the element content with parenthesis which can also be specified along with the order of occurrence or the number of occurrences of the child elements.<\/p>\r\n( ) grouping (section|chapter)+\r\n\r\n \r\n\r\nElements without children<\/strong>\r\n\r\n \r\n

Elements can be defined as empty or without children.<\/p>\r\n

<!ELEMENT name category><\/p>\r\n \r\n

The name<\/em> is the element name used in start and end tags and the category<\/em> may be given as EMPTY. In the DTD the <br> tag can be defined as : <!ELEMENT br EMPTY> In the XML the tag can be used as: <br><\/br> or just <br \/><\/p>\r\n \r\n

In the XML, an empty element may not have any content between the start tag and the end tag but an empty element may (and usually does) have attributes.<\/span><\/p>\r\n\r\n<\/div>\r\n

\r\n\r\n\u00a0<\/strong>\r\n\r\n Elements with unstructured children<\/strong>\r\n\r\n \r\n\r\nThe elements can be defined with unstructured children.\r\n\r\n<!ELEMENT name category>\r\n\r\nHere the category may be ANY.\r\n\r\n \r\n

This indicates that any<\/em> content character data, elements, even undeclared elements may be used. Since the whole point of using a DTD is to define the structure of a document, ANY should be avoided wherever possible.<\/p>\r\n \r\n

The category may be (#PCDATA), indicating that only character data may be used. Here the parentheses are required.<\/p>\r\n \r\n\r\nIn the DTD when an element is defined as (#PCDATA), the syntax is given as,\r\n\r\n<!ELEMENT paragraph (#PCDATA)>\r\n\r\n \r\n\r\nIn the XML file the element can contain text content\r\n\r\n<paragraph>A shot rang out!<\/paragraph>\r\n

Note:<\/em> In (#PCDATA), whitespace is kept exactly as entered. Elements may not <\/em>be used within parsed character data. Entities are character data, and may<\/em> be used.<\/p>\r\n \r\n\r\nElements with children<\/strong>\r\n\r\n \r\n

An element can contain one or more children.<\/p>\r\n

A category may describe one or more children as given in the syntax below,<\/p>\r\n

<!ELEMENT novel (foreword, chapter+)><\/p>\r\n \r\n

Here the parentheses are required, even if there is only one child, a space must precede the opening parenthesis. Commas (,) between elements mean that all<\/em> children must appear, and must be in the<\/em> order specified<\/em>. The \u201c|\u201d separators means any one child may be used. All child elements must themselves be declared. Children may have children and parentheses can be used for grouping.<\/p>\r\n \r\n\r\nAn complete example of the syntax we have seen so far is given in the following example .\r\n\r\n<!ELEMENT novel (foreword, (chapter+|section+))>\r\n\r\n<\/div>\r\n\u00a0 \u00a0 \u00a0Elements with mixed content<\/strong>\r\n

\r\n\r\n \r\n

Elements can also contain mixed content with text data or elements or both.Here #PCDATA describes elements with only character data and #PCDATA can be used in an \u201cor\u201d grouping also as follows,<\/p>\r\n \r\n\r\n<!ELEMENT note (#PCDATA|message)*>\r\n\r\nThis is called a mixed content\r\n\r\n \r\n\r\nBut certain and rather severe restrictions apply:\r\n\r\n \r\n\r\n\u2022\u00a0 #PCDATA must be first\r\n\r\n\u2022\u00a0 The separators must be \u201c|\u201d\r\n\r\n\u2022\u00a0 \u00a0The group must be starred (meaning zero or more)\r\n\r\n \r\n\r\nNames and namespaces<\/strong>\r\n\r\n \r\n

All names of elements, attributes, and entities, in both the DTD and the XML, are formed by following the rules given as below,<\/p>\r\n \r\n

\u2022 The name must begin with a letter or underscore.<\/p>\r\n

\u2022 The name may contain only letters, digits, dots, hyphens, underscores, and colons (and, for foreign languages, combining characters and extenders).<\/p>\r\n \r\n\r\nThe DTD doesn\u2019t know about namespaces as far as it knows, a colon is just part of a name\r\n\r\nThe following are different (and both legal),\r\n\r\n<!ELEMENT chapter (paragraph+)>\r\n\r\n<!ELEMENT myBook:chapter (myBook:paragraph+)>\r\n\r\nWe need to avoid colons in names, except to indicate namespaces.\r\n\r\n \r\n\r\nAn expanded DTD example<\/strong>\r\n\r\n \r\n\r\nAn example covering all those concepts we have seen so far is given now.\r\n\r\n<!DOCTYPE novel [\r\n\r\n<!ELEMENT novel\r\n\r\n(foreword, chapter+, biography?, criticalEssay*)> <!ELEMENT foreword (paragraph+)> <!ELEMENT chapter (section+|paragraph+)> <!ELEMENT section (paragraph+)> <!ELEMENT biography(paragraph+)>\r\n\r\n<!ELEMENT criticalEssay (section+)>\r\n\r\n<!ELEMENT paragraph (#PCDATA)><\/span>\r\n\r\n]><\/span>\r\n\r\n<\/div>\r\n

\r\n

\u00a0 \u00a0 \u00a0 The root element is the <novel> element. It consists of elements such as <foreword>, one or more <chapter> elements, zero or one <biography> elements and zero or more <criticalEssay> elements. The <foreword> elements consists of one or more <paragraph> elements. The <chapter> elements consists of one or more <section> or <paragraph> elements.The <section> element consists of one or more <paragraph> elements. The element <biography> consists of one or more <paragraph> elements. The element <criticalEssay> consists of one or more <section> elements. The element <paragraph> consists of #PCDATA.<\/p>\r\n \r\n\r\nAttributes and entities<\/strong>\r\n\r\n \r\n

In addition to elements, a DTD may declare attributes and entities. An attribute describes information that can be put within the start tag of an element.<\/p>\r\n \r\n\r\nIn the XML file we define the attributes as follows,\r\n\r\n<dog name=\"Spot\" age=\"3\"><\/dog>\r\n\r\n \r\n\r\nIn an DTD file the attribute is described as,\r\n\r\n<!ATTLIST dog\r\n\r\nname\u00a0 CDATA\u00a0 #REQUIRED\r\n\r\nage\u00a0\u00a0\u00a0\u00a0\u00a0 CDATA\u00a0 #IMPLIED >\r\n\r\n \r\n\r\nAn entity describes text to be substituted.\r\n\r\nIn an XML file an entity is defined as,\r\n\r\n&copyright;\r\n\r\n \r\n\r\nIn the DTD it is described as,\r\n\r\n<!ENTITY copyright \"Copyright Dr. Dave\">\r\n\r\n \r\n\r\nAttributes<\/strong>\r\n\r\n \r\n\r\nThe format of defining an attribute is,\r\n\r\n<!ATTLIST element-name<\/em>\r\n\r\nname\u00a0 type\u00a0 requirement<\/em>\r\n\r\nname\u00a0 type\u00a0 requirement<\/em>>\r\n\r\nwhere the name-type-requirement<\/em> may be repeated as many times as desired.\r\n\r\n \r\n

Note that only spaces separate the parts, so careful counting is essential. The element-name<\/em> tells which element may have these attributes.The <\/span>name<\/em> is the name of the attribute. Each element has a <\/span>type<\/em>, such as CDATA (character data).<\/span>The <\/span>requirement<\/em> may be defined as required, optional, or \u201cfixed\u201d. In the XML, attributes may occur in any order<\/span><\/p>\r\n\r\n<\/div>\r\n

\r\n\r\n\u00a0<\/strong>\r\n\r\n Important attribute types<\/strong>\r\n\r\n \r\n\r\nThere are ten attribute types and these are the most important ones:\r\n\r\n<\/div>\r\n\r\n\r\n\r\n\r\n\r\n\r\n
CDATA<\/td>\r\nThe value is character data<\/td>\r\n<\/tr>\r\n
(man|woman|child)<\/td>\r\nThe value is one from this list<\/td>\r\n<\/tr>\r\n
ID<\/td>\r\nThe value is a unique identifier. Note: ID values\r\nmust be legal XML names and must be unique within the\r\ndocument<\/td>\r\n<\/tr>\r\n
NMTOKEN<\/td>\r\nThe value is a legal XML name. This is sometimes\r\nused to disallow whitespace in the name. It also disallows\r\nnumbers, since an XML name cannot begin with a digit.<\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\n
\r\n\r\n \r\n\r\n \r\n\r\n \r\n\r\n \r\n\r\n \r\n\r\n \r\n\r\n \r\n\r\n \r\n\r\n\u00a0 \u00a0 Less important attribute types,<\/strong>\r\n\r\n<\/div>\r\n
\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n
IDREF<\/td>\r\nThe ID of another element<\/td>\r\n<\/tr>\r\n
IDREFS<\/td>\r\nA list of other IDs<\/td>\r\n<\/tr>\r\n
NMTOKENS<\/td>\r\nA list of valid XML names<\/td>\r\n<\/tr>\r\n
ENTITY<\/td>\r\nAn entity<\/td>\r\n<\/tr>\r\n
ENTITIES<\/td>\r\nA list of entities<\/td>\r\n<\/tr>\r\n
NOTATION<\/td>\r\nA notation<\/td>\r\n<\/tr>\r\n
xml:<\/td>\r\nA predefined XML value<\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\nRequirements<\/strong>\r\n\r\n \r\n\r\nRecall that an attribute has the form,\r\n\r\n<!ATTLIST element-name name\u00a0 type\u00a0 requirement<\/em>>\r\n\r\nThe requirement<\/em> is one of a default value, enclosed in quotes,\r\n\r\nExample: <!ATTLIST degree CDATA \"PhD\">\r\n\r\nThe requirement<\/em> can take different values such as #REQUIRED or #IMPLIED or #FIXED.\r\n\r\n<\/div>\r\n\u00a0 \u00a0 \u00a0\u2022\u00a0 \u00a0#REQUIRED means the attribute must be present.<\/span>\r\n\r\n\u00a0\u2022\u00a0 \u00a0#IMPLIED means the attribute is optional.<\/span>\r\n

\u00a0\u2022\u00a0 #FIXED \"value\" the attribute always has the given value. If specified in the XML, the same value must be used.<\/span><\/p>\r\n\r\n

\r\n\r\n\u00a0 <\/strong>\r\n\r\nEntities<\/strong>\r\n\r\n \r\n

Entities are Variables used to define shortcuts to common text. Entities should not be confused with character references, which are numerical values between & and #.There are exactly five predefined entities: &lt;, &gt;, &amp;, &quot;, and &apos;.Additional entities can be defined in the DTD by the following syntax,<\/p>\r\n

<!ENTITY copyright \"Copyright Dr. Dave\"><\/p>\r\n

Entities can be defined in another document by,<\/p>\r\n

<!ENTITY copyright SYSTEM \"MyURI\"><\/p>\r\n

An example of use in the XML as,<\/p>\r\n

This document is &copyright; 2002.<\/em><\/p>\r\n \r\n\r\nAnother example: XML<\/strong>\r\n\r\n \r\n\r\n<?xml version=\"1.0\"?>\r\n\r\n<!DOCTYPE weatherReport SYST EM \"http:\/\/www.mysite.com\/mydoc.dtd\"> <weatherReport>\r\n\r\n<date>05\/29\/2002<\/date>\r\n\r\n<location>\r\n\r\n<city>Chennai<\/city> <state>Tamilnadu<\/state> <country>INDIA<\/country>\r\n\r\n<\/location>\r\n\r\n<temperature -range>\r\n\r\n<high scale=\"F\">84<\/high>\r\n\r\n<low scale=\"F\">51<\/low>\r\n\r\n<\/temperature -range>\r\n\r\n<\/weatherReport>\r\n\r\n \r\n\r\nThe DTD for this example<\/strong>\r\n\r\n \r\n\r\n<!ELEMENT weatherReport (date, location, temperature -range)>\r\n\r\n<!ELEMENT date (#PCDATA)>\r\n\r\n<!ELEMENT location (city, state, country)>\r\n\r\n<!ELEMENT city (#PCDATA)>\r\n\r\n<!ELEMENT state (#PCDATA)><\/span>\r\n\r\n<!ELEMENT country (#PCDATA)><\/span>\r\n\r\n<!ELEMENT temperature -range ((low, high)|(high, low))> <!ELEMENT low (#PCDATA)> <!ELEMENT high (#PCDATA)><\/span>\r\n\r\n<!ATTLIST low scale (C|F) #REQUIRED><\/span>\r\n\r\n<!ATTLIST high scale (C|F) #REQUIRED><\/span>\r\n\r\n<\/div>\r\n

\r\n\r\n\u00a0 \u00a0<\/strong>\r\n\r\nInline DTDs<\/strong>\r\n\r\n \r\n

If a DTD is used only by a single XML document, it can be put directly in that document. An inline DTD can be used only by the document in which it occurs.<\/p>\r\n \r\n\r\n<?xml version=\"1.0\">\r\n\r\n<!DOCTYPE myRootElement [\r\n\r\n<!-- DTD content goes here -->\r\n\r\n]>\r\n\r\n<myRootElement>\r\n\r\n<!-- XML content goes here -->\r\n\r\n<\/myRootElement>\r\n\r\n \r\n\r\nInline DTDs - Example<\/strong>\r\n\r\n<\/div>\r\n\u00a0 \u00a0 <!DOCTYPE company [<\/span>\r\n\r\n< ! ELEMENT company<\/span>\r\n\r\n< ! ELEMENT person<\/span>\r\n\r\n< ! ELEMENT ssn<\/span>\r\n\r\n< ! ELEMENT name<\/span>\r\n\r\n< ! ELEMENT office<\/span>\r\n\r\n< ! ELEMENT phone<\/span>\r\n\r\n< ! ELEMENT product<\/span>\r\n\r\n< ! ELEMENT pi d<\/span>\r\n\r\n< ! ELEMENT description<\/span>\r\n\r\n( (person | product)*) ><\/span>\r\n\r\n( ssn, name, office, phone?) ><\/span>\r\n\r\n( # PCDATA) ><\/span>\r\n\r\n( # PCDATA) ><\/span>\r\n\r\n( # PCDATA) ><\/span>\r\n\r\n( # PCDATA) ><\/span>\r\n\r\n( pi d, name, description? ) ><\/span>\r\n\r\n( # PCDATA) ><\/span>\r\n\r\n( # PCDATA) ><\/span>\r\n\r\n]><\/span>\r\n\r\n<company><\/span>\r\n\r\n<person> <ssn> 12345678 < \/ssn><\/span>\r\n\r\n<name> John <\/name><\/span>\r\n\r\n<office> B432 <\/office><\/span>\r\n\r\n<phone> 1234 <\/phone><\/span>\r\n\r\n<\/person><\/span>\r\n\r\n<product> \u2026 <\/product><\/span>\r\n\r\n\u2026<\/span>\r\n\r\n<\/company><\/span>\r\n

\r\n\r\n \r\n\r\nExternal DTDs<\/strong>\r\n\r\n \r\n

An external DTD which is a DTD defined as a separate document is declared with a SYSTEM or a PUBLIC command. The syntax is given as follows,<!DOCTYPE myRootElement SYSTEM \"http:\/\/www.mysite.com\/mydoc.dtd\"><\/span><\/p>\r\n \r\n

The name that appears after DOCTYPE (in this example, myRootElement) must match the name of the XML document\u2019s root element. We will use SYSTEM for external DTDs that we define for ourself and we will use PUBLIC for official and published DTD's. External DTDs can only be referenced with a URL.<\/span><\/p>\r\n

The file extension for an external DTD is .dtd.<\/span><\/p>\r\n \r\n

External DTD's are almost always preferable to inline DTD's, since they can be used by more than one document.<\/span><\/p>\r\n\r\n<\/div>\r\n

\r\n\r\n\u00a0 <\/strong>\r\n\r\n\u00a0External DTDs - Example<\/strong>\r\n\r\n \r\n\r\n<!DOCTYPE company SYSTEM \u201ccom pany.dtd\u201d>\r\n\r\n<company>\r\n\r\n<person> <ssn> 12345678 < \/ssn>\r\n\r\n<name> John <\/name>\r\n\r\n<office> B432 <\/office>\r\n\r\n<phone> 1234 <\/phone>\r\n\r\n<\/person>\r\n\r\n<product> \u2026 <\/product>\r\n\r\n\u2026\r\n\r\n<\/company>\r\n\r\n \r\n\r\nIn this example the DTD is defined in a separate document called \u201ccompany.dtd\u201d and referred in the\r\n\r\nXML document after DOCTYPE.\r\n\r\nThe DTD can reside at a different URL, and then we refer to it as,\r\n\r\n<!DOCTYPE company SYSTEM \u201chttp:\/\/www.mydtd.com\/com pany.dtd\u201d>\r\n\r\nAn example of TV Schedule DTD<\/strong> is given,\r\n\r\n<!DOCTYPE TVSCHEDULE [\r\n\r\n<!ELEMENT TVSCHEDULE (CHANNEL+)>\r\n\r\n<!ELEMENT CHANNEL (BANNER, DAY+)>\r\n\r\n<!ELEMENT BANNER (#PCDATA)>\r\n\r\n<!ELEMENT DAY ((DAT E, HOLIDAY) | (DAT E, PROGRAMSLOT+))+> <!ELEMENT HOLIDAY (#PCDATA)>\u00a0 \u00a0 \u00a0 <!ELEMENT DAT E (#PCDATA)>\r\n\r\n<!ELEMENT PROGRAMSLOT (TIME, TITLE, DESCRIPTION?)> <!ELEMENT TIME (#PCDATA)> <!ELEMENT TITLE (#PCDATA)>\r\n\r\n<!ELEMENT DESCRIPTION (#PCDATA)>\r\n\r\n<!ATTLIST TVSCHEDULE NAME CDATA #REQUIRED> <!ATTLIST CHANNEL CHAN CDATA #REQUIRED> <!ATTLIST PROGRAMSLOT VTR CDATA #IMPLIED> <!ATTLIST TITLE RATING CDATA #IMPLIED> <!ATTLIST TITLE LANGUAGE CDATA #IMPLIED>\r\n\r\n]>\r\n\r\n<\/div>\r\nAnother Example for Newspaper Article DTD<\/strong> is also given for understanding,\r\n\r\n<!DOCTYPE NEWSPAPER [\r\n\r\n<!ELEMENT NEWSPAPER (ARTICLE+)>\r\n\r\n<!ELEMENT ARTICLE (HEADLINE, BYLINE, LEAD, BODY, NOT ES)> <!ELEMENT HEADLINE (#PCDATA)>\u00a0 \u00a0 \u00a0 <!ELEMENT BYLINE (#PCDATA)>\r\n\r\n<!ELEMENT LEAD (#PCDATA)>\r\n\r\n<!ELEMENT BODY (#PCDATA)>\r\n\r\n<!ELEMENT NOT ES (#PCDATA)>\r\n\r\n<!ATTLIST ARTICLE AUTHOR CDATA #REQUIRED> <!ATTLIST ARTICLE EDITOR CDATA #IMPLIED> <!ATTLIST ARTICLE DAT E CDATA #IMPLIED> <!ATTLIST ARTICLE EDITION CDATA #IMPLIED> <!ENTITY NEWSPAPER \"Vervet Logic Times\"> <!ENTITY PUBLISHER \"Vervet Logic Press\">\r\n\r\n<!ENTITY COPYRIGHT \"Copyright 1998 Vervet Logic Press\"> ]>\r\n\r\n \r\n\r\nLimitations of DTDs<\/strong>\r\n\r\n \r\n

DTDs are a very weak specification language and we can\u2019t put any restrictions on element contents. It is difficult to specify when all the children must occur, but may be in any order or this element must occur a certain number of times. There are only ten data types for attribute values.<\/p>\r\n \r\n

But most of all DTDs aren\u2019t written in XML. If we want to do any validation,we need one parser for the XML and<\/em> another for the DTD. This makes XML parsing harder than it needs to be. In order to support this, there is a newer and more powerful technology called XML Schemas. However, DTDs are still very much in use.<\/p>\r\n \r\n\r\nSummary<\/strong>\r\n\r\n \r\n

This module provides knowledge about XML DTD.The module identifies the purpose of DTD with few examples. The module also discusses about Inline and External D<\/p>\r\n \r\n\r\nWeb Links<\/strong>\r\n

    \r\n \t
  • www.w3schools.com\/xml<\/strong><\/em><\/li>\r\n \t
  • www.cis.upenn.edu\/~matuszek\/cit597-2003\/Lectures\/08-dtd<\/strong>.ppt<\/strong><\/em><\/li>\r\n \t
  • www.tutorialspoint.com\/xml<\/strong><\/em><\/li>\r\n<\/ul>","rendered":"
    \n

    \u00a0 \u00a0 \u00a0Document Type Definitions<\/strong><\/p>\n

     <\/p>\n

    A DTD (Document Type Definition) describes the structure of one or more XML documents. Specifically, a DTD describes about Elements, Attributes and Entities defined in an XML document. An XML document is called a well-structured XML document if it follows certain simple syntactic rules and an XML document is called a valid XML document if it also specifies and conforms to a DTD.<\/p>\n

     <\/p>\n

    The need for DTDs<\/strong><\/p>\n

     <\/p>\n

    XML documents are designed to be processed by computer programs and if we can put just any<\/em> tags in an XML document, it\u2019s very hard to write a program that knows how to process the tags. A DTD specifies what tags may occur, when they may occur, and what attributes they may or must have. A DTD allows the XML document to be verified (shown to be legal) by the browser. A DTD that is shared across groups allows the groups to produce consistent XML documents.<\/p>\n<\/div>\n

    \u00a0 \u00a0 An XML example<\/strong><\/p>\n

    \n

     <\/p>\n

    Following is an simple example of an XML document.<\/p>\n

    <nove l><\/p>\n

    <foreword><\/p>\n

    <paragraph>This is the great Indian novel.<\/ paragraph> <\/foreword><\/p>\n

    <chapter number=”1″><\/p>\n

    <paragraph>It was a dark and stormy night.<\/paragraph> <paragraph>Suddenly, a shot rang out!\u00a0 \u00a0 \u00a0 <\/paragraph><\/p>\n

    <\/chapter><\/p>\n

    <\/novel><\/p>\n

     <\/p>\n

    This XML document contains elements and attributes and the DTD describes about the elements, such as <novel>, <foreword>, <chapter> and <paragraph>, consisting of tags<\/em> and content<\/em>. The element <novel> consists of elements <foreword> and <chapter>. The element <chapter> consists of attributes, such as number=”1″, consisting of a name<\/em> and a value.<\/em><\/p>\n

    This XML file is described with the following DTD,<\/p>\n

     <\/p>\n

    A DTD example<\/strong><\/p>\n

     <\/p>\n

    <!DOCTYPE novel [<\/p>\n

    <!ELEMENT novel (foreword, chapter+)><\/p>\n

    <!ELEMENT foreword (paragraph+)><\/p>\n

    <!ELEMENT chapter (paragraph+)><\/p>\n

    <!ELEMENT paragraph (#PCDATA)><\/p>\n

    <!ATTLIST chapter number CDATA #REQUIRED><\/p>\n

    ]><\/p>\n

     <\/p>\n

    The DTD of an XML document starts with <!DOCTYPE root-element [ \u2026]> In this example we have defined as,<\/p>\n

    <!DOCTYPE novel [ \u2026]><\/p>\n

     <\/p>\n

    In an DTD the elements are described as<!ELEMENT\u2026> and attributes of the element are described as<\/p>\n

    <!ATTLIST \u2026.>.<\/p>\n

     <\/p>\n

    Here in this example, a novel consists of a foreword and one or more chapters, in that order. A foreword consists of one or more paragraphs. A chapter also consists of one or more paragraphs. A paragraph consists of parsed character data which means the text that cannot contain any other elements.<\/p>\n

     <\/p>\n

    Each chapter must have a number attribute given as \u201cREQUIRED\u201d.<\/p>\n<\/div>\n

    \u00a0 \u00a0ELEMENT descriptions<\/strong><\/p>\n

    \n

     <\/p>\n

    An element content can be another element or a list of child elements or it can be a text string or numeric value (character data).<\/p>\n

     <\/p>\n

    There are suffixes added to the element content where an element consists of zero, one or more occurences of the child elements. A (?) specifies optional or zero, (+) denotes one or more elements can occur and a (*) denotes zero or more of the elements can occur.<\/p>\n\n\n\n\n\n
    ?<\/td>\noptional<\/td>\nforeword?<\/td>\n<\/tr>\n
    +<\/td>\none or more<\/td>\nchapter+<\/td>\n<\/tr>\n
    *<\/td>\nzero or more<\/td>\nappendix*<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    Seperators can also be added with the element declaration, that specifies the order of occurrence when the element has multiple number of child elements. There are two ways we can use to denote the order of occurrence. Using a comma (,) between the child elements specifies that the child elements will occur in the order given. Using a vertical line (|) means that either one or the other child element will occur.<\/p>\n

    \n<\/div>\n

    \n\n\n\n\n
    ,<\/td>\nboth, in order<\/td>\nforeword?, chapter+<\/td>\n<\/tr>\n
    |<\/td>\nor<\/td>\nsection|chapter<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    Grouping:<\/strong><\/p>\n

     <\/p>\n

    The elements can be grouped in the element content with parenthesis which can also be specified along with the order of occurrence or the number of occurrences of the child elements.<\/p>\n

    ( ) grouping (section|chapter)+<\/p>\n

     <\/p>\n

    Elements without children<\/strong><\/p>\n

     <\/p>\n

    Elements can be defined as empty or without children.<\/p>\n

    <!ELEMENT name category><\/p>\n

     <\/p>\n

    The name<\/em> is the element name used in start and end tags and the category<\/em> may be given as EMPTY. In the DTD the <br> tag can be defined as : <!ELEMENT br EMPTY> In the XML the tag can be used as: <br><\/br> or just <br \/><\/p>\n

     <\/p>\n

    In the XML, an empty element may not have any content between the start tag and the end tag but an empty element may (and usually does) have attributes.<\/span><\/p>\n<\/div>\n

    \n

    \u00a0<\/strong><\/p>\n

    Elements with unstructured children<\/strong><\/p>\n

     <\/p>\n

    The elements can be defined with unstructured children.<\/p>\n

    <!ELEMENT name category><\/p>\n

    Here the category may be ANY.<\/p>\n

     <\/p>\n

    This indicates that any<\/em> content character data, elements, even undeclared elements may be used. Since the whole point of using a DTD is to define the structure of a document, ANY should be avoided wherever possible.<\/p>\n

     <\/p>\n

    The category may be (#PCDATA), indicating that only character data may be used. Here the parentheses are required.<\/p>\n

     <\/p>\n

    In the DTD when an element is defined as (#PCDATA), the syntax is given as,<\/p>\n

    <!ELEMENT paragraph (#PCDATA)><\/p>\n

     <\/p>\n

    In the XML file the element can contain text content<\/p>\n

    <paragraph>A shot rang out!<\/paragraph><\/p>\n

    Note:<\/em> In (#PCDATA), whitespace is kept exactly as entered. Elements may not <\/em>be used within parsed character data. Entities are character data, and may<\/em> be used.<\/p>\n

     <\/p>\n

    Elements with children<\/strong><\/p>\n

     <\/p>\n

    An element can contain one or more children.<\/p>\n

    A category may describe one or more children as given in the syntax below,<\/p>\n

    <!ELEMENT novel (foreword, chapter+)><\/p>\n

     <\/p>\n

    Here the parentheses are required, even if there is only one child, a space must precede the opening parenthesis. Commas (,) between elements mean that all<\/em> children must appear, and must be in the<\/em> order specified<\/em>. The \u201c|\u201d separators means any one child may be used. All child elements must themselves be declared. Children may have children and parentheses can be used for grouping.<\/p>\n

     <\/p>\n

    An complete example of the syntax we have seen so far is given in the following example .<\/p>\n

    <!ELEMENT novel (foreword, (chapter+|section+))><\/p>\n<\/div>\n

    \u00a0 \u00a0 \u00a0Elements with mixed content<\/strong><\/p>\n

    \n

     <\/p>\n

    Elements can also contain mixed content with text data or elements or both.Here #PCDATA describes elements with only character data and #PCDATA can be used in an \u201cor\u201d grouping also as follows,<\/p>\n

     <\/p>\n

    <!ELEMENT note (#PCDATA|message)*><\/p>\n

    This is called a mixed content<\/p>\n

     <\/p>\n

    But certain and rather severe restrictions apply:<\/p>\n

     <\/p>\n

    \u2022\u00a0 #PCDATA must be first<\/p>\n

    \u2022\u00a0 The separators must be \u201c|\u201d<\/p>\n

    \u2022\u00a0 \u00a0The group must be starred (meaning zero or more)<\/p>\n

     <\/p>\n

    Names and namespaces<\/strong><\/p>\n

     <\/p>\n

    All names of elements, attributes, and entities, in both the DTD and the XML, are formed by following the rules given as below,<\/p>\n

     <\/p>\n

    \u2022 The name must begin with a letter or underscore.<\/p>\n

    \u2022 The name may contain only letters, digits, dots, hyphens, underscores, and colons (and, for foreign languages, combining characters and extenders).<\/p>\n

     <\/p>\n

    The DTD doesn\u2019t know about namespaces as far as it knows, a colon is just part of a name<\/p>\n

    The following are different (and both legal),<\/p>\n

    <!ELEMENT chapter (paragraph+)><\/p>\n

    <!ELEMENT myBook:chapter (myBook:paragraph+)><\/p>\n

    We need to avoid colons in names, except to indicate namespaces.<\/p>\n

     <\/p>\n

    An expanded DTD example<\/strong><\/p>\n

     <\/p>\n

    An example covering all those concepts we have seen so far is given now.<\/p>\n

    <!DOCTYPE novel [<\/p>\n

    <!ELEMENT novel<\/p>\n

    (foreword, chapter+, biography?, criticalEssay*)> <!ELEMENT foreword (paragraph+)> <!ELEMENT chapter (section+|paragraph+)> <!ELEMENT section (paragraph+)> <!ELEMENT biography(paragraph+)><\/p>\n

    <!ELEMENT criticalEssay (section+)><\/p>\n

    <!ELEMENT paragraph (#PCDATA)><\/span><\/p>\n

    ]><\/span><\/p>\n<\/div>\n

    \n

    \u00a0 \u00a0 \u00a0 The root element is the <novel> element. It consists of elements such as <foreword>, one or more <chapter> elements, zero or one <biography> elements and zero or more <criticalEssay> elements. The <foreword> elements consists of one or more <paragraph> elements. The <chapter> elements consists of one or more <section> or <paragraph> elements.The <section> element consists of one or more <paragraph> elements. The element <biography> consists of one or more <paragraph> elements. The element <criticalEssay> consists of one or more <section> elements. The element <paragraph> consists of #PCDATA.<\/p>\n

     <\/p>\n

    Attributes and entities<\/strong><\/p>\n

     <\/p>\n

    In addition to elements, a DTD may declare attributes and entities. An attribute describes information that can be put within the start tag of an element.<\/p>\n

     <\/p>\n

    In the XML file we define the attributes as follows,<\/p>\n

    <dog name=”Spot” age=”3″><\/dog><\/p>\n

     <\/p>\n

    In an DTD file the attribute is described as,<\/p>\n

    <!ATTLIST dog<\/p>\n

    name\u00a0 CDATA\u00a0 #REQUIRED<\/p>\n

    age\u00a0\u00a0\u00a0\u00a0\u00a0 CDATA\u00a0 #IMPLIED ><\/p>\n

     <\/p>\n

    An entity describes text to be substituted.<\/p>\n

    In an XML file an entity is defined as,<\/p>\n

    &copyright;<\/p>\n

     <\/p>\n

    In the DTD it is described as,<\/p>\n

    <!ENTITY copyright “Copyright Dr. Dave”><\/p>\n

     <\/p>\n

    Attributes<\/strong><\/p>\n

     <\/p>\n

    The format of defining an attribute is,<\/p>\n

    <!ATTLIST element-name<\/em><\/p>\n

    name\u00a0 type\u00a0 requirement<\/em><\/p>\n

    name\u00a0 type\u00a0 requirement<\/em>><\/p>\n

    where the name-type-requirement<\/em> may be repeated as many times as desired.<\/p>\n

     <\/p>\n

    Note that only spaces separate the parts, so careful counting is essential. The element-name<\/em> tells which element may have these attributes.The <\/span>name<\/em> is the name of the attribute. Each element has a <\/span>type<\/em>, such as CDATA (character data).<\/span>The <\/span>requirement<\/em> may be defined as required, optional, or \u201cfixed\u201d. In the XML, attributes may occur in any order<\/span><\/p>\n<\/div>\n

    \n

    \u00a0<\/strong><\/p>\n

    Important attribute types<\/strong><\/p>\n

     <\/p>\n

    There are ten attribute types and these are the most important ones:<\/p>\n<\/div>\n\n\n\n\n\n\n
    CDATA<\/td>\nThe value is character data<\/td>\n<\/tr>\n
    (man|woman|child)<\/td>\nThe value is one from this list<\/td>\n<\/tr>\n
    ID<\/td>\nThe value is a unique identifier. Note: ID values
    \nmust be legal XML names and must be unique within the
    \ndocument<\/td>\n<\/tr>\n
    NMTOKEN<\/td>\nThe value is a legal XML name. This is sometimes
    \nused to disallow whitespace in the name. It also disallows
    \nnumbers, since an XML name cannot begin with a digit.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
    \n

     <\/p>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

    \u00a0 \u00a0 Less important attribute types,<\/strong><\/p>\n<\/div>\n

    \n\n\n\n\n\n\n\n\n\n
    IDREF<\/td>\nThe ID of another element<\/td>\n<\/tr>\n
    IDREFS<\/td>\nA list of other IDs<\/td>\n<\/tr>\n
    NMTOKENS<\/td>\nA list of valid XML names<\/td>\n<\/tr>\n
    ENTITY<\/td>\nAn entity<\/td>\n<\/tr>\n
    ENTITIES<\/td>\nA list of entities<\/td>\n<\/tr>\n
    NOTATION<\/td>\nA notation<\/td>\n<\/tr>\n
    xml:<\/td>\nA predefined XML value<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    Requirements<\/strong><\/p>\n

     <\/p>\n

    Recall that an attribute has the form,<\/p>\n

    <!ATTLIST element-name name\u00a0 type\u00a0 requirement<\/em>><\/p>\n

    The requirement<\/em> is one of a default value, enclosed in quotes,<\/p>\n

    Example: <!ATTLIST degree CDATA “PhD”><\/p>\n

    The requirement<\/em> can take different values such as #REQUIRED or #IMPLIED or #FIXED.<\/p>\n<\/div>\n

    \u00a0 \u00a0 \u00a0\u2022\u00a0 \u00a0#REQUIRED means the attribute must be present.<\/span><\/p>\n

    \u00a0\u2022\u00a0 \u00a0#IMPLIED means the attribute is optional.<\/span><\/p>\n

    \u00a0\u2022\u00a0 #FIXED “value” the attribute always has the given value. If specified in the XML, the same value must be used.<\/span><\/p>\n

    \n

    \u00a0 <\/strong><\/p>\n

    Entities<\/strong><\/p>\n

     <\/p>\n

    Entities are Variables used to define shortcuts to common text. Entities should not be confused with character references, which are numerical values between & and #.There are exactly five predefined entities: &lt;, &gt;, &amp;, &quot;, and &apos;.Additional entities can be defined in the DTD by the following syntax,<\/p>\n

    <!ENTITY copyright “Copyright Dr. Dave”><\/p>\n

    Entities can be defined in another document by,<\/p>\n

    <!ENTITY copyright SYSTEM “MyURI”><\/p>\n

    An example of use in the XML as,<\/p>\n

    This document is &copyright; 2002.<\/em><\/p>\n

     <\/p>\n

    Another example: XML<\/strong><\/p>\n

     <\/p>\n

    <?xml version=”1.0″?><\/p>\n

    <!DOCTYPE weatherReport SYST EM “http:\/\/www.mysite.com\/mydoc.dtd”> <weatherReport><\/p>\n

    <date>05\/29\/2002<\/date><\/p>\n

    <location><\/p>\n

    <city>Chennai<\/city> <state>Tamilnadu<\/state> <country>INDIA<\/country><\/p>\n

    <\/location><\/p>\n

    <temperature -range><\/p>\n

    <high scale=”F”>84<\/high><\/p>\n

    <low scale=”F”>51<\/low><\/p>\n

    <\/temperature -range><\/p>\n

    <\/weatherReport><\/p>\n

     <\/p>\n

    The DTD for this example<\/strong><\/p>\n

     <\/p>\n

    <!ELEMENT weatherReport (date, location, temperature -range)><\/p>\n

    <!ELEMENT date (#PCDATA)><\/p>\n

    <!ELEMENT location (city, state, country)><\/p>\n

    <!ELEMENT city (#PCDATA)><\/p>\n

    <!ELEMENT state (#PCDATA)><\/span><\/p>\n

    <!ELEMENT country (#PCDATA)><\/span><\/p>\n

    <!ELEMENT temperature -range ((low, high)|(high, low))> <!ELEMENT low (#PCDATA)> <!ELEMENT high (#PCDATA)><\/span><\/p>\n

    <!ATTLIST low scale (C|F) #REQUIRED><\/span><\/p>\n

    <!ATTLIST high scale (C|F) #REQUIRED><\/span><\/p>\n<\/div>\n

    \n

    \u00a0 \u00a0<\/strong><\/p>\n

    Inline DTDs<\/strong><\/p>\n

     <\/p>\n

    If a DTD is used only by a single XML document, it can be put directly in that document. An inline DTD can be used only by the document in which it occurs.<\/p>\n

     <\/p>\n

    <?xml version=”1.0″><\/p>\n

    <!DOCTYPE myRootElement [<\/p>\n

    <!– DTD content goes here –><\/p>\n

    ]><\/p>\n

    <myRootElement><\/p>\n

    <!– XML content goes here –><\/p>\n

    <\/myRootElement><\/p>\n

     <\/p>\n

    Inline DTDs – Example<\/strong><\/p>\n<\/div>\n

    \u00a0 \u00a0 <!DOCTYPE company [<\/span><\/p>\n

    < ! ELEMENT company<\/span><\/p>\n

    < ! ELEMENT person<\/span><\/p>\n

    < ! ELEMENT ssn<\/span><\/p>\n

    < ! ELEMENT name<\/span><\/p>\n

    < ! ELEMENT office<\/span><\/p>\n

    < ! ELEMENT phone<\/span><\/p>\n

    < ! ELEMENT product<\/span><\/p>\n

    < ! ELEMENT pi d<\/span><\/p>\n

    < ! ELEMENT description<\/span><\/p>\n

    ( (person | product)*) ><\/span><\/p>\n

    ( ssn, name, office, phone?) ><\/span><\/p>\n

    ( # PCDATA) ><\/span><\/p>\n

    ( # PCDATA) ><\/span><\/p>\n

    ( # PCDATA) ><\/span><\/p>\n

    ( # PCDATA) ><\/span><\/p>\n

    ( pi d, name, description? ) ><\/span><\/p>\n

    ( # PCDATA) ><\/span><\/p>\n

    ( # PCDATA) ><\/span><\/p>\n

    ]><\/span><\/p>\n

    <company><\/span><\/p>\n

    <person> <ssn> 12345678 < \/ssn><\/span><\/p>\n

    <name> John <\/name><\/span><\/p>\n

    <office> B432 <\/office><\/span><\/p>\n

    <phone> 1234 <\/phone><\/span><\/p>\n

    <\/person><\/span><\/p>\n

    <product> \u2026 <\/product><\/span><\/p>\n

    \u2026<\/span><\/p>\n

    <\/company><\/span><\/p>\n

    \n

     <\/p>\n

    External DTDs<\/strong><\/p>\n

     <\/p>\n

    An external DTD which is a DTD defined as a separate document is declared with a SYSTEM or a PUBLIC command. The syntax is given as follows,<!DOCTYPE myRootElement SYSTEM “http:\/\/www.mysite.com\/mydoc.dtd”><\/span><\/p>\n

     <\/p>\n

    The name that appears after DOCTYPE (in this example, myRootElement) must match the name of the XML document\u2019s root element. We will use SYSTEM for external DTDs that we define for ourself and we will use PUBLIC for official and published DTD’s. External DTDs can only be referenced with a URL.<\/span><\/p>\n

    The file extension for an external DTD is .dtd.<\/span><\/p>\n

     <\/p>\n

    External DTD’s are almost always preferable to inline DTD’s, since they can be used by more than one document.<\/span><\/p>\n<\/div>\n

    \n

    \u00a0 <\/strong><\/p>\n

    \u00a0External DTDs – Example<\/strong><\/p>\n

     <\/p>\n

    <!DOCTYPE company SYSTEM \u201ccom pany.dtd\u201d><\/p>\n

    <company><\/p>\n

    <person> <ssn> 12345678 < \/ssn><\/p>\n

    <name> John <\/name><\/p>\n

    <office> B432 <\/office><\/p>\n

    <phone> 1234 <\/phone><\/p>\n

    <\/person><\/p>\n

    <product> \u2026 <\/product><\/p>\n

    \u2026<\/p>\n

    <\/company><\/p>\n

     <\/p>\n

    In this example the DTD is defined in a separate document called \u201ccompany.dtd\u201d and referred in the<\/p>\n

    XML document after DOCTYPE.<\/p>\n

    The DTD can reside at a different URL, and then we refer to it as,<\/p>\n

    <!DOCTYPE company SYSTEM \u201chttp:\/\/www.mydtd.com\/com pany.dtd\u201d><\/p>\n

    An example of TV Schedule DTD<\/strong> is given,<\/p>\n

    <!DOCTYPE TVSCHEDULE [<\/p>\n

    <!ELEMENT TVSCHEDULE (CHANNEL+)><\/p>\n

    <!ELEMENT CHANNEL (BANNER, DAY+)><\/p>\n

    <!ELEMENT BANNER (#PCDATA)><\/p>\n

    <!ELEMENT DAY ((DAT E, HOLIDAY) | (DAT E, PROGRAMSLOT+))+> <!ELEMENT HOLIDAY (#PCDATA)>\u00a0 \u00a0 \u00a0 <!ELEMENT DAT E (#PCDATA)><\/p>\n

    <!ELEMENT PROGRAMSLOT (TIME, TITLE, DESCRIPTION?)> <!ELEMENT TIME (#PCDATA)> <!ELEMENT TITLE (#PCDATA)><\/p>\n

    <!ELEMENT DESCRIPTION (#PCDATA)><\/p>\n

    <!ATTLIST TVSCHEDULE NAME CDATA #REQUIRED> <!ATTLIST CHANNEL CHAN CDATA #REQUIRED> <!ATTLIST PROGRAMSLOT VTR CDATA #IMPLIED> <!ATTLIST TITLE RATING CDATA #IMPLIED> <!ATTLIST TITLE LANGUAGE CDATA #IMPLIED><\/p>\n

    ]><\/p>\n<\/div>\n

    Another Example for Newspaper Article DTD<\/strong> is also given for understanding,<\/p>\n

    <!DOCTYPE NEWSPAPER [<\/p>\n

    <!ELEMENT NEWSPAPER (ARTICLE+)><\/p>\n

    <!ELEMENT ARTICLE (HEADLINE, BYLINE, LEAD, BODY, NOT ES)> <!ELEMENT HEADLINE (#PCDATA)>\u00a0 \u00a0 \u00a0 <!ELEMENT BYLINE (#PCDATA)><\/p>\n

    <!ELEMENT LEAD (#PCDATA)><\/p>\n

    <!ELEMENT BODY (#PCDATA)><\/p>\n

    <!ELEMENT NOT ES (#PCDATA)><\/p>\n

    <!ATTLIST ARTICLE AUTHOR CDATA #REQUIRED> <!ATTLIST ARTICLE EDITOR CDATA #IMPLIED> <!ATTLIST ARTICLE DAT E CDATA #IMPLIED> <!ATTLIST ARTICLE EDITION CDATA #IMPLIED> <!ENTITY NEWSPAPER “Vervet Logic Times”> <!ENTITY PUBLISHER “Vervet Logic Press”><\/p>\n

    <!ENTITY COPYRIGHT “Copyright 1998 Vervet Logic Press”> ]><\/p>\n

     <\/p>\n

    Limitations of DTDs<\/strong><\/p>\n

     <\/p>\n

    DTDs are a very weak specification language and we can\u2019t put any restrictions on element contents. It is difficult to specify when all the children must occur, but may be in any order or this element must occur a certain number of times. There are only ten data types for attribute values.<\/p>\n

     <\/p>\n

    But most of all DTDs aren\u2019t written in XML. If we want to do any validation,we need one parser for the XML and<\/em> another for the DTD. This makes XML parsing harder than it needs to be. In order to support this, there is a newer and more powerful technology called XML Schemas. However, DTDs are still very much in use.<\/p>\n

     <\/p>\n

    Summary<\/strong><\/p>\n

     <\/p>\n

    This module provides knowledge about XML DTD.The module identifies the purpose of DTD with few examples. The module also discusses about Inline and External D<\/p>\n

     <\/p>\n

    Web Links<\/strong><\/p>\n

      \n
    • www.w3schools.com\/xml<\/strong><\/em><\/li>\n
    • www.cis.upenn.edu\/~matuszek\/cit597-2003\/Lectures\/08-dtd<\/strong>.ppt<\/strong><\/em><\/li>\n
    • www.tutorialspoint.com\/xml<\/strong><\/em><\/li>\n<\/ul>\n","protected":false},"author":4,"menu_order":8,"template":"","meta":{"pb_show_title":"on","pb_short_title":"","pb_subtitle":"","pb_authors":["dr-m-vijayalakshmi"],"pb_section_license":""},"chapter-type":[],"contributor":[58],"license":[],"class_list":["post-68","chapter","type-chapter","status-publish","hentry","contributor-dr-m-vijayalakshmi"],"part":3,"_links":{"self":[{"href":"https:\/\/ebooks.inflibnet.ac.in\/csp12\/wp-json\/pressbooks\/v2\/chapters\/68","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ebooks.inflibnet.ac.in\/csp12\/wp-json\/pressbooks\/v2\/chapters"}],"about":[{"href":"https:\/\/ebooks.inflibnet.ac.in\/csp12\/wp-json\/wp\/v2\/types\/chapter"}],"author":[{"embeddable":true,"href":"https:\/\/ebooks.inflibnet.ac.in\/csp12\/wp-json\/wp\/v2\/users\/4"}],"version-history":[{"count":21,"href":"https:\/\/ebooks.inflibnet.ac.in\/csp12\/wp-json\/pressbooks\/v2\/chapters\/68\/revisions"}],"predecessor-version":[{"id":628,"href":"https:\/\/ebooks.inflibnet.ac.in\/csp12\/wp-json\/pressbooks\/v2\/chapters\/68\/revisions\/628"}],"part":[{"href":"https:\/\/ebooks.inflibnet.ac.in\/csp12\/wp-json\/pressbooks\/v2\/parts\/3"}],"metadata":[{"href":"https:\/\/ebooks.inflibnet.ac.in\/csp12\/wp-json\/pressbooks\/v2\/chapters\/68\/metadata\/"}],"wp:attachment":[{"href":"https:\/\/ebooks.inflibnet.ac.in\/csp12\/wp-json\/wp\/v2\/media?parent=68"}],"wp:term":[{"taxonomy":"chapter-type","embeddable":true,"href":"https:\/\/ebooks.inflibnet.ac.in\/csp12\/wp-json\/pressbooks\/v2\/chapter-type?post=68"},{"taxonomy":"contributor","embeddable":true,"href":"https:\/\/ebooks.inflibnet.ac.in\/csp12\/wp-json\/wp\/v2\/contributor?post=68"},{"taxonomy":"license","embeddable":true,"href":"https:\/\/ebooks.inflibnet.ac.in\/csp12\/wp-json\/wp\/v2\/license?post=68"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}