The NCBI Book Document Type Definition (hereafter NCBI Book DTD) and NCBI Book Collection Document Type Definition (hereafter NCBI Collection DTD) define elements and attributes that describe the content of books (such as pamphlets and monographs) and book collections, respectively. The NCBI Book DTD describes both the metadata for a book and the content of the book, but it can also describe only the metadata for both books and book parts, such “Chapters”. The NCBI Collection DTD describes a document that contains metadata for a grouping or “collection” of books, potentially followed by textual information about the books in the collection, and a listing of the books; the content of the books is not included. Although designed for biomedical books, the NCBI Book DTD should be sufficiently general to describe not only STM books but also technical books in any field.
This NCBI Book DTD and the NCBI Collection DTD comprise a handful of DTD-specific modules that set up Parameter Entity over-rides and use (by reference) the base modules of the NLM Journal Archiving and Interchange DTD Suite (hereafter Suite or base Suite). The modules of the Suite were developed as part of an effort to create XML applications through which materials on health-related disciplines could be shared and reused electronically. The Suite has been used to construct many DTDs in addition to this one. Although the full Suite was developed to support electronic journal production, the structures should be adequate to support book material and limited print production as well as electronic.
This Tag Library describes the NCBI Book DTD and NCBI Book Collection DTD, by providing:
The NCBI Book DTD provides the model for a single book, pamphlet, monograph, etc. It is possible to model an entire book, including its bibliographic metadata as well as its content or to model only the book metadata, to allow books to be modeled where the content is not in XML. A complete book typically contains metadata about itself; some textual front matter (such as a book preface or list of contributors); the book’s content (the text and graphical material that make up the body of the work); and possibly some ancillary back matter such as appendixes. Book components must appear in the following order:
The NCBI Collection DTD describes a group of books; the intent is to provide information about the collection, not to provide the contents of the books themselves. Accordingly, the top-level element, <collection>, serves as a wrapper element for metadata about the collection, any text discussing the collection as a whole, and a list of the books. The <collection> element contains the following elements, in order:
The NCBI Book DTD, the NCBI Collection DTD, and the full NLM Archiving and Interchange DTD Suite have been written as a set of XML DTD “modules”, each of which is a separate physical file. No module is an entire DTD by itself, but these modules can be combined into a number of different DTDs. Modules are primarily intended for maintenance and creation of new DTDs; all the elements of the same “type” (class) are stored together.
The NCBI Book DTD and NCBI Collection DTDs have been built from these modules, and both of these DTDs and individual modules from the Archival and Interchange DTD Suite will be described in this Tag Library.
The major disadvantage of a modular system is the longer learning curve, since it may not be immediately obvious where within the system to find a particular element or attribute cluster. To help with this, the description of each element in the Element Section of this documentation names the module in which that element is defined.
There are many advantages to such a modular approach. The smaller units are written once, maintained in one place, and used in many different DTDs. This makes it much easier to keep lower level structures consistent across document types, while allowing for any real differences that analysis identifies. A DTD for a new function (such as an authoring DTD) or a new publication type (such as a book) can be built quickly, since most of the necessary components will already be defined in the DTD Suite. Editorial and production personnel can bring the experience gained on one tagging project directly to the next with very little loss or retraining. Customized software (including authoring, typesetting, and electronic display tools) can be written once, shared among projects, and modified only for real distinctions.
|
Element |
Elements are nouns (such as “Speech”, “Book”, and “Speaker”) that represent the components of books, the book itself, and accompanying metadata about the book. |
|
Attribute |
Attributes hold facts about an element, such as which type of list (e.g., numbered, bulleted, or plain) is being requested when using the List <list> tag, or the name of a pointer to an external file that contains an image. Each attribute has both a name (e.g., list-type) and a value (e.g., “bulleted”). |
|
Metadata |
Data about the data, for example, bibliographic information. The distinction is between metadata elements which describe a book (such as the name of book’s publisher) versus elements which contain the textual and graphical content of the book. |
This Tag Library contains the following sections:
|
Introduction |
This introduction to the contents of this Tag Library, to the design philosophy and intended usage of the Journal Archiving and Interchange DTD Suite, and to the NCBI Book and NCBI Collection DTDs. |
|
Elements Section |
Descriptions of the elements used in the NCBI Book DTD, the NCBI Collection DTD, and most of the base Suite. The element descriptions are listed in alphabetical order by tag name. (Note: Each element has two names: a “tag name” (formally called an element-type name) that is used in tagged documents, the DTDs, and by the software, and an “element name” (usually longer) that provides a fuller, more descriptive name for the benefit of human readers. For example, a tag name might be <disp-quote> with the corresponding element name Quote, Displayed or a tag name might be <verse-group> with the corresponding element name Verse Form for Poetry. |
|
Attributes Section |
Descriptions of the attributes used in these DTDs. Like elements, attributes also have two names: the shorter machine-readable one and a (usually longer) human-readable one. Attributes are listed in order by the shorter machine-readable names, for example, the attribute short name “fig-type” instead of the more human-friendly (or at least more obvious)name “Type of Figure”. |
|
Parameter Entity Section (Implementors Only) |
Names, description, and contents of the Parameter Entities in these DTD modules. |
|
Context Table |
Listings of where each element may be used. All elements are given in a simple alphabetical list. There is a single table for the elements from all the Suite modules that are called from the DTDs. The Context Table is formatted in two columns. The first column lists an element’s tag name, and the second column lists the tag names of all the elements in which the first element may occur. For example, if the first column contains the book front matter element <book-front> and the second column contains only the element <book>, this means that the <book-front> (Book Front Matter) element may only be used inside an <book> (Book) element. Most elements may be used inside more than one other element. For example, the element <access-date> (Access Date for Cited Work) may be used inside the <citation> and <related-article> elements. Note: These Context Table listings (which list where an element may be used) are the inverse of the content definition that is given as a part of each element description, which lists what can be inside the named element. |
|
Book Hierarchy Diagrams |
Tree-like graphical representations of the content of many elements. This can be a fast visual way to determine the structure of an book (or book collection) or of any element within a book (or book collection). |
|
Index By Tag Name |
Index of element descriptions, alphabetically by tag name (element-type name) |
|
Index By Element Name |
Index of element descriptions, alphabetically by element name (the longer, more descriptive name) |
|
DTD Section |
Copies of the NCBI Book DTD, its four book-specific customization modules, its four book-specific element modules, the NCBI Collection DTD, and the modules of the Archiving and Interchange DTD Suite used by these two DTDs. |
| <alt-text> | The tag name of an element (Written in lower case monofont with the entire name surrounded by “< >”) |
| Alternate Title Text (For a Figure, Etc.) | The element name (long descriptive name of an element) or the descriptive name of an attribute (Written in title case, that is, with important words capitalized, and the words separated by spaces) |
| must not | Emphasis to stress a point |
Both the NCBI Book DTD and the NCBI Collection DTD are delivered as packages that include: a DTD file, the customization files needed for that DTD to over-ride the declarations in the Suite, any new modules that define DTD-specific elements, the modules that comprise the Suite, one or more tagged sample documents, and this documentation, as a set of linked HTML files.
How you use the documentation will depend on what you need to learn about the modules and the DTD.
If you want to learn about the elements and the attributes in the Suite, so that you can tag documents or read tagged documents, here is a good way to start.
If you want to learn about the DTD Suite in order to write a new DTD or to modify either of these DTDs:
New DTDs are created by writing, at a minimum, a new DTD module and new customization modules, so you might want to read (in order):
The NCBI Book DTD and NCBI Collection DTD were written as customizations of the NLM Archiving and Interchange DTD Suite. The basic Suite has module for defining tables, paragraphs, etc. The NCBI Book DTD (book.dtd) and its customization modules define the elements for a monograph or book and also calls in the Suite modules. In contrast, the NCBI Collection DTD bookcollection.dtd and its customization modules define a group of books, where the intent is to give information about the collection, and list its members, but not provide the actual content of any member book.
The NCBI Book DTD is comprised of the DTD module itself (book.dtd), the four book customization modules that are used to over-ride element and attribute declarations in the Suite (%bookcustom-modules.ent;, %bookcustom-classes.ent;, %bookcustom-mixes.ent;, %bookcustom-models.ent;), and the four modules that add new elements and attributes over and above what the Suite provides (%bookmeta.ent;, %bookpart.ent;, %bookimagemap.ent;, and %bookmultilink.ent;).
|
NCBI Book DTD |
(File name book.dtd) The top-level NCBI Book DTD Module that declares the document element (<book>) and the other top-level elements that define the primary components of a book (book metadata, book front matter, body, and back matter). The DTD invokes all the modules it uses, by reference, as external Parameter Entities: first the NCBI Book DTD Module of Modules is called to name all Book-specific customized modules, then the Suite Module of Modules is called to name all the potential modules from the Suite, then customized and default modules are called (for Parameter Entities naming element classes, mixes, and models), then the Common Module for shared elements and attribute lists is called, and finally all the other Suite element modules are called as needed, and the four new Book-specific element modules, %bookmeta.ent;, %bookpart.ent;, %bookimagemap.ent;, and %bookmultilink.ent;. |
The NCBI Book DTD customization modules over-ride the definitions in the modules of the Suite:
|
Book-Specific Module to Name Modules |
(Parameter Entity %bookcustom-modules.ent;) Defines all the external modules that are specific to the NCBI Collection DTD or NCBI Book DTD (except itself, which must be both named and called inside a DTD). A DTD can select from these modules by referencing the module names through external Parameter Entities. The entities are declared in this module, but referenced (actually called in) in the DTD proper. To include a set of elements (such as all the lists or all the MathML elements), a DTD references the external Parameter Entity of the module (defined in this module) that contains these declarations. Note: The NCBI Book DTD Module of Modules and the Suite Module of Modules need to be the first two external modules called by either the NCBI Collection DTD or the NCBI Book DTD. Customization modules for classes, mixes, and models will typically be called following the NCBI Book DTD Module of Modules and the Suite Module of Modules. |
|
Book-Specific Class Over-rides Module |
(Parameter Entity %bookcustom-classes.ent;) Sets up Parameter Entities that will be used to override the Suite’s default classes (those that are described in the %default-classes.ent; module) Note: This module must be called before %default-classes.ent; module (which this module overrides) and the %bookcustom-mixes.ent; and %bookcustom-models.ent; modules (which may build on classes defined in this module). |
|
Book-Specific Mix Over-rides Module |
(Parameter Entity %bookcustom-mixes.ent;) Sets up Parameter Entities that will be used to override default mixes (groupings made of “classes”) prescribed by the %default-mixes.ent; module Note: This module must be called after the Book Customize Classes Module (%bookcustom-classes.ent;) and the Default Classes Module (%default-classes.ent;) but before the %default-mixes.ent; module (which this module overrides) and the %bookcustom-models.ent; module (which may build on mixes defined in this module). |
|
Book-Specific Models/Attributes Over-rides Module |
(Parameter Entity %bookcustom-models.ent;) Sets up Parameter Entities that will be used to override default content model Parameter Entities set elsewhere in the Suite. Also defines customizable attribute Declared Values and attribute lists for the DTD being defined. Note: This module must be called after the NCBI Book DTD Customize Mixes Module (%bookcustom-mixes.ent;) and Default Mixes Module (%default-mixes.ent;) but before any “base” modules of the Suite. |
The new elements added just for the NCBI Book DTD are defined in the following modules:
|
Book DTD Metadata Module |
(Parameter Entity %bookmeta.ent;) Describes book-specific metadata elements that are not defined in the DTD Suite metadata module %articlemeta.ent; |
|
Book DTD Book Part Module |
(Parameter Entity %bookpart.ent;) Declares book-component-level metadata, such as chapter-specific or part-specific metadata elements |
|
Book DTD Image Map Module |
(Parameter Entity %bookimagemap.ent;) Declares the elements used to create client-side image maps, which make hot spots on graphics |
|
Book DTD Multilink Module |
(Parameter Entity %bookmultilink.ent;) Defines links to external resources (Note: The external and multiple external links defined in this module are used in the NCBI Book DTD for external links instead of the XLink mechanism. The XLink mechanism, although deprecated, is still specified in all of the DTD Suite modules.) |
The basic Suite modules over-ridden by the BOOK-specific customization modules just named include the following:
|
Suite Module to Name the Modules |
(Parameter Entity %modules.ent;) Defines all the external modules that are part of the modular Archiving and Interchange DTD Suite (except itself, which must be both named and called inside a DTD). A DTD selects from these modules by referencing the module names through external Parameter Entities. The entities are declared in the Suite Module of Modules (%modules.ent;), but referenced (or not) in the DTD proper. To include a set of elements (such as all the book metadata or all the display elements) a DTD references the external Parameter Entity of the module that contains these declarations. Note: The NCBI Book DTD Module of Modules and the Suite Module of Modules need to be the first two external modules called by either the NCBI Collection DTD or NCBI Book DTD. Customization modules for classes, mixes, and models will typically be called following the NCBI Book DTD Module of Modules and the Suite Module of Modules. |
|
Suite Default Element Classes Module |
(Parameter Entity %default-classes.ent;) Sets up the Parameter Entities that name the element members of each class that will be used to establish the content models Note: This module must be called before the Book Customize Mixes Module (%bookcustom-mixes.ent;) and the Default Element Mixes Module (%default-mixes.ent;), as well as the Book Customize Models Module, %bookcustom-models.ent; (which builds on those modules). |
|
Suite Default Element Mixes Module |
(Parameter Entity %default-mixes.ent;) Sets up the Parameter Entities that name mixes (groupings made of “classes”) that will be used to establish the content models Note: This module must be called before the Book Customize Models Module (%bookcustom-models.ent;) or any “base” module of the Interchange Suite. |
The NCBI Collection DTD models a collection list and description, is a small DTD that defines a few collection elements and uses all of the book and Suite modules.
|
NCBI Collection DTD |
(File name bookcollection.dtd) The top-level NCBI Collection DTD Module that declares the document element (<collection>) and the other top-level elements that define a grouping of related books (collection metadata, book front matter, body, and back matter). All elements but these few — and the elements needed to flesh out a collection’s metadata such as <collection-list> — are declared in the modules of the Suite. The DTD invokes all the other modules it uses, by reference, as external Parameter Entities: first the NCBI Book DTD Module of Modules is called to name all Book-specific customized modules, then the Suite Module of Modules is called to name all the potential modules from the Suite, then customized and default modules are called (for Parameter Entities naming element classes, mixes, and models), then the Common Module for shared elements and attribute lists is called, and finally all the other modules are called as needed, including the DTD-specific element modules, %bookmeta.ent;, %bookpart.ent;, %bookimagemap.ent;, and %bookmultilink.ent;. |
The modules comprising the rest of the DTD Suite that are used in both the NCBI Book DTD and the NCBI Collection DTD are the following:
|
Common (Shared) Elements Module |
(Parameter Entity %common.ent;) Declarations for elements, attributes, entities, and notations that are shared by more than one class module Note: This module must be called before any of the modules comprising the Interchange Suite. |
|
Article Metadata Elements Module |
(Parameter Entity %articlemeta.ent;) Declares the metadata elements (issue elements and article header elements) used to describe a journal article. This module has been incorporated in the NCBI Book DTD and NCBI Collection DTDs to include metadata elements that, although previously declared to model journal articles, are also used in the metadata of a book or book component such as a chapter. |
|
Back Matter Elements Module |
(Parameter Entity %backmatter.ent;) Declares elements that are not part of the main textual flow of a work, but are considered to be ancillary material such as appendices, glossaries, and bibliographic reference lists |
|
Display Class Elements Module |
(Parameter Entity %display.ent;) Declares the display-related elements, such as figures, graphics, math, chemical expressions and structures, tables, etc. |
|
Format Class Elements Module |
(Parameter Entity %format.ent;) Declares elements concerned with rendition of output, for example, printing on a page or display on a screen. This module includes the elements in the Appearance Class, the Break Class, and the Emphasis Class. |
|
Link Class Elements Module |
(Parameter Entity %link.ent;) Declares elements that are links (internal or external) by definition, such as URLs (<uri>) and internal cross references (<xref>) |
|
List Class Elements Module |
(Parameter Entity %list.ent;) Declares the elements in the List Class; these are all lists except the lists of bibliographic references (citations). Lists are considered to be composed of items. |
|
Math Class Elements Module |
(Parameter Entity %math.ent;) Declares the elements in the math classes such as display equations |
|
Paragraph-Like Elements Module |
(Parameter Entity %para.ent;) Declares structural, non-display elements that may appear in the same places as a paragraph. These elements are named in the various paragraph class Parameter Entities. |
|
Subject Phrase Class Elements Module |
(Parameter Entity %phrase.ent;) Declares the Phrase Class elements, that is, names the inline, subject-specific elements. At the time of this DTD’s creation, there were only two phrase-level elements. If more specific subject words (such as “gene”) are added to later versions of this DTD, they should be added to the %phrase.class; Parameter Entity and defined in this module or in the Common Module, %common.ent;. |
|
Bibliographic Reference (Citation) Class Elements Module |
(Parameter Entity %references.ent;) Declares the bibliographic reference elements |
|
Section Class Elements Module |
(Parameter Entity %section.ent;) Declares the elements of the Section Class, that is, declares all section-level elements in the NCBI Book DTD (or NCBI Collection DTD). When these DTDs were created, there is only one such element, Section (<sec>) itself, but future expansion to named sections (such as <methodology> or <materials>) or any new section-level structures would be added here. |
|
MathML Setup Module |
(Parameter Entity %mathmlsetup.ent;) Invokes the MathML modules DTD Creation Note: To include the MathML elements, a DTD must reference this module. This module sets up all Parameter Entities needed to use the MathML tagset and references (invokes) the MathML 2.0 DTD Module, which, in turn, invokes all the other MathML modules. |
|
MathML 2.0 DTD Module |
(Parameter Entity %mathml.dtd;) Mathematical Markup Language (MathML) 2.0, an XML application for describing mathematical notation and capturing both its structure and content |
|
MathML 2.0 Qualified Names 1.0 |
(Parameter Entity %mathml-qname.mod;) Declares Parameter Entities to support namespace-qualified names, namespace declarations, and name prefixing for MathML, as well as declares the Parameter Entities used to provide namespace-qualified names for all MathML element types |
|
Extra Entities for MathML 2.0 |
(Parameter Entity %ent-mmlextra;) Used for MathML processing |
|
Aliases for MathML 2.0 |
(Parameter Entity %ent-mmlalias;) Used for MathML processing |
|
XHTML Table Setup Module |
(Parameter Entity %XHTMLtablesetup.ent;) Sets all Parameter Entities needed by the HTML 4.0 (XHTML) table model, and then invokes the module containing that model DTD Creation Note: To include the XHTML table model, a DTD must reference this module. This module sets up all Parameter Entities needed to use the XHTML table model and references (invokes) the XHTML Table Model Module. |
|
XHTML Table Model Module |
(Parameter Entity %htmltable.dtd;) The public XML version of the HTML 4.0 (XHTML) table model. This module is invoked in %XHTMLtablesetup.ent;. |
|
XML Special Characters Module |
(Parameter Entity %xmlspecchars.ent;) Standard ISO XML special character entities used in this DTD |
|
Custom Special Characters Module |
(Parameter Entity %chars.ent;) Custom special character entities created specifically for use in this DTD |
|
Notation Declarations Module |
(Parameter Entity %notat.ent;) Container module for the Notation Declarations to be used with this DTD Suite. These notations have been placed in their own module for easy expansion or replacement. |
This DTD Suite has been written as a series of XML DTD modules that can be combined into a number of different DTDs. The modules are separate physical files that, taken together, define all element structures (such as tables, math, chemistry, paragraphs, sections, figures, footnotes, and reference elements), as well as attributes and entities in the Suite.
Modules in the Suite are primarily intended to group elements for maintenance. There are different kinds of modules. A module may either:
Parameter Entities are the major mechanism for customizing a DTD or creating a new DTD from the modules in the Suite. Individual DTDs will be constructed by 1) establishing element and attribute combinations and content models using Parameter Entities in one of the DTD-specific customizing modules and 2) choosing appropriate modules from the Suite that declare the elements needed. For example, if the base DTD contained 6 kinds of lists and 2 table models, a more specific DTD, such as an authoring DTD, might use a Customize Classes Module to redefine the List Class to name only 3 lists and redefine the Display Class to allow only one table model.
The standard modules to create a customized DTD are: the DTD itself, a module to name its components, and as many over-ride modules and new elements modules as necessary. Typical modules for a new DTD are:
Many of the elements in the NCBI Book DTD have been grouped into loose element classes. There is no hard and fast rule for what constitutes a class; each one is a design decision, a matter of judgment. These classes are designed to ease customization to meet the particular needs of new DTDs. Base classes for the Archiving and Interchange DTD Suite are defined in a separate Default Element Classes Module (%default-classes.ent;).
Content models are built using sequences of elements, and OR groups that are classes (typically) or mixes. As an example, the content model for a Paragraph element is declared to be an OR group (that is, a choice) of data characters and any of the elements named in the Paragraph Elements mix. The mix %p-elements; is declared to be a large OR group of many other element-defining classes: the Block Display Class Elements, the Mathematical Expressions Class Elements, the List Class Elements, the Citation Class Elements, et al.
These element classes can be viewed as building blocks that will be used to build larger Parameter Entities for element mixes. (Note: A mix describes a usage circumstance for a group of elements, such as all the paragraph-level elements, all the elements allowed inside a table cell, all the elements inside a paragraph, or all the inline elements). For example, to add another block display item to the Block Display Class Elements, you would edit the %block-display.class; entity declaration, and place the new declaration into the DTD-specific class over-ride module, thus establishing your definition ahead of the block display class of the Suite. Then create a new modules that defined the new element and call that modules form the DTD.
The basic idea for a new DTD is that all lower-level elements (paragraphs, lists, figures, etc.) will be defined in modules — either the modules of the base DTD Suite or in new DTD-specific modules rather than in the DTD itself. The new DTD will be fairly short and include only definitions of the topmost elements, at least the document element and maybe its children.
Modules are defined (declared) using External Parameter Entities in the Suite’s Module to Name the Modules or in the DTD-specific Module of Modules. Modules are called (referenced) in the DTD proper, in the order needed to define the Parameter Entities in sequence.
Version 2.1 of the NCBI Book DTD was written as an example of the new best-practice customization technique. A new variant DTD that follows this plan will probably consist of the following modules:
To illustrate the process just described, here is a series of specific instructions for making a new DTD, illustrated by showing how the NCBI Book DTD was created from the modules of the whole Suite.
The classes described here — with a few exceptions noted below — are defined in the Archiving and Interchange DTD Suite Default Element Classes Module (%default-classes.ent;) and have been used to divide the elements into physical modules. The documentation for the classes and their current default element contents are listed in the Parameter Entity Section toward the end of this Tag Library.
|
Accessibility Class |
(%access.class;) Elements added to make the processing of books more accessible to people with special needs and the devices that meet those needs, for example, the visually handicapped. Includes, for example, the element <alt-text> which is a short phrase name or description of an object, usually a graphical object, that can be used “behind the picture” on a website or pronounced in an audio system. |
|
Address Class |
(%address.class;) Potential element components of an address, such as <country> or <fax> |
|
Appearance Class |
(%appearance.class;) Formatting elements used primarily in tables, for example, a horizontal rule (usage discouraged) |
|
Appendix Class |
(%app.class;) A construct containing only the appendix for use in the back matter of a book or book component (e.g., chapter) |
|
Back Matter Class |
(%back.class;) Ancillary elements, typically used in the back matter of an book, part, chapter, etc. |
|
Book Part Class |
(%book-part.class;) Elements used in the body of a book to designate major segments such as parts or chapters [Defined in the %bookcustom-classes.ent; module] |
|
Break Class |
(%break.class;) Formatting element used to force a line break, primarily in tables and titles (usage discouraged) |
|
Citation Class |
(%citation.class;) Reference (a citation) to an external document as used within, for example, the text of a paragraph |
|
Contributor Information Class |
(%contrib-info.class;) Metadata about a contributor |
|
Corresponding Author Class |
(%corresp.class;) Elements associated with the corresponding author |
|
Custom Metadata Class |
(%custom-meta.class;) Construct for the wrapper element <custom-meta-wrap> used to contain additional metadata above and beyond what can be specified by the NCBI Book DTD [Defined in the %bookcustom-classes.ent; module] |
|
Date Class |
(%date.class;) Dates and other matters of history such as a Date as a String |
|
Date Parts Class |
(%date-parts.class;) The components of a date, such as <year> or <season> |
|
Definition Class |
(%def.class;) Definitions (<def>) and other elements to match with terms and abbreviations |
|
Degree Class |
(%degree.class;) The academic or professional degrees that accompany a person’s name |
|
Display Class |
(Several Parameter Entities: %caption.class;, %block-display.class;, %display-back-matter.class;, %fig-display.class;, %inline-display.class;, %just-base-display.class;, %simple-display.class;), %simple-intable-display.class;) Graphical or other display-related elements, including figures, chemical formulas, and images [%block-display.class; defined in the %bookcustom-classes.ent; module] |
|
Emphasis Class |
(%emphasis.class;, %subsup.class;) Used to produce rendering/typographical distinctions, such as superscript, subscript, or bold text |
|
Front and Front/Back Class |
(%front.class;, %front-back.class;) Ancillary elements, typically used in the front or back matter of a book (or book component) |
|
Identifier Class |
(%id.class;) DOIs and other identifiers used by publishers at many levels, for example, for an <abstract> or a <fig> |
|
Keyword Class |
(%kwd.class;) Keywords and other elements which name a subject term, critical expression, key phrase, etc. associated with an entire document and used for identification and indexing purposes |
|
Label Class |
(%label.class;) The label element, used to hold the number, prefix character, or prefix word or phrase of a labeled object such as a table, figure, or footnote |
|
Link Class |
(Several Parameter Entities: %address-link.class;, %article-link.class;, %simple-link.class;, %fn-link.class;) Elements that associate one location with another, including cross references, and URIs for links to the World Wide Web [%address-link.class; defined in the %bookcustom-classes.ent; module] |
|
List Class |
(%list.class;) The types of lists used in text, including numbered lists and bulleted lists |
|
Math Class |
(Several Parameter Entities: %math.class;, %block-math.class;, %inline-math.class;) The mathematical elements (<mml:math>, <tex-math>) and the elements that can contain them (such as <inline-formula> and <disp-formula>) |
|
Name Class |
(%name.class;) The elements used to name the personal names for individuals (such as <string-name>) or the collaboration names for groups (<collab>) for people who produce books or book components (such as chapters) |
|
Paragraph Class |
(Several Parameter Entities: %just-para.class;, %rest-of-para.class;, %intable-para.class;) Information for the reader that is at the same structural level as a paragraph, including both regular paragraphs and specially-named paragraphs that may have distinctive uses or different displays, such as dialogs and formal statements |
|
Personal Name Class |
(%person-name.class;) The element components of a person’s name (such as <surname>),which can be used, for example, inside the name of a contributor |
|
Phrase Class |
(%phrase.class;) Inline elements that surround a word or phrase in text because the subject (content) should be identified to support some kind of display, searching, or processing (such as <named-content> to identify a drug name, genus/species, product, etc.) |
|
Reference Class |
(%references.class;) The elements that may be included inside a <citation> (bibliographic reference) |
|
Reference List Class |
(%ref-list.class;) A construct containing only the reference list (defined in References Module) for use in the back matter of a book (or book component) |
|
Related Article Class |
(%related-article.class;) Journal articles that may be written concerning this work, summarizing this work, reviewing this work, etc. |
|
Section Back Matter Class |
(%sec-back.class;) Ancillary elements, typically used in the back matter of a section, etc. |
|
Section Class |
(%references.class;) The elements that are at the same hierarchical level as a section |
|
Table Class |
(Several Parameter Entities: %table.class;, %just-table.class;, %table-foot.class;, %tbody.class;) Elements that contain the rows and columns inside the Table Wrapper element (<table-wrap>). The following XHTML table model elements can be set up for inclusion: <table>. |
PARAMETER ENTITY: SAME FUNCTION, SAME NAME — The Suite modules and initial DTDs have used a series of Parameter Entity naming conventions consistently. While parsing software cannot enforce these Parameter Entity naming or usage conventions, these conventions can make it much easier for a person to know how the content models work and what must be modified to make a DTD change.
CLASSES — Classes are functional groupings of elements used together in an OR group. Each class is named with a Parameter Entity, and all class Parameter Entity names end in the suffix “.class”:
<!ENTITY % list.class "def-list | list">
A class, by definition, should never be made “empty”; the class should be removed from all models where you do not want the class elements included.
MIXES — Mixes are functional OR groups of classes; mixes should never contain element names directly. All mixes must be declared after all classes, since mixes are composed of classes. Mix names have no set suffix; for example, they may end in “-mix” or “-elements”. Content models and content model over-rides use mixes and classes for all OR groups. Only content model sequences are made up of element names directly.
MODEL OVER-RIDES — Parameter Entity mixes for over-riding a content model are of two styles: 1) inline mixes and 2) full content model replacements. These two groupings have been defined and named separately to preserve the mixed-content or element- content nature of the models in DTDs derived from the Suite.
The inline Parameter Entities to be intermingled with character data (#PCDATA) in a mixed content model are named with a suffix “-elements”. For example, “%institution-elements;” would be used in the content model for the element <institution>:
<!ENTITY % institution-elements "| %break.class; | %emphasis.class; | %subsup.class;" > <!ELEMENT institution (#PCDATA %institution-elements;)* >
All inline mixes begin with an OR bar, so that the mix can be removed leaving just character data (#PCDATA):
<!ENTITY % rendition-plus "| %emphasis.class; | %subsup.class;" >
The over-ride of a complete content model will be named with a suffix “-model” and should include the entire content model, including the enclosing parentheses:
<!ENTITY % kwd-group-model "(title?, (%kwd.class;)+ )" > <!ELEMENT kwd-group %kwd-group-model; >
Each DTD (a single module) has been given the suffix “.dtd” (delivered as the files book.dtd and bookcollection.dtd" respectively). Each of the book-specific modules (such as book customization modules and book element modules which are not part of the Suite) are called in by the DTD as External Parameter Entities and have been given the prefix “book-”.
Each DTD and module has been assigned a unique formal public identifier (fpi). File names are never referenced directly in the comments in the DTD; the file is referred to by the name of the external Parameter Entity, which names the fpi and a system name for the file. The external Parameter Entity has been set to the initial delivery filename.
The individual modules of both the Suite and the DTD (as delivered) have been given DOS/Windows 3-digit suffixes indicating their type:
|
*.dtd |
A module that can be used as the top level of an XML hierarchy. Used for the NCBI Book DTD top level (book.dtd) or the NCBI Collection DTD top level (bookcollection.dtd), but also taken unchanged for public DTD modules that have been included in this DTD such as the MathML DTD and the XHTML table model. |
|
*.ent |
A DTD fragment for incorporation into a full DTD. May contain element declarations, entity declarations, etc. |
|
*.mod |
A DTD fragment for incorporation into a full DTD. May contain element declarations, entity declarations, etc. This extension has the same meaning as *.ent and is only used to maintain the extension names dictated by the inclusion of PUBLIC DTD fragments, for example, mathml2-qname-1.mod. |
While the DTD cannot dictate graphic file names, best practice for naming graphic files in documents tagged according to this DTD Suite would be to limit the names and path names to these characters: letters (both upper and lower case), numbers, underscore, hyphen, and period. All such names will be assumed to be case sensitive. DOS-style file extensions may be used.
Modeling several structures and functions that might appropriately be part of a DTD using this Suite has been delayed until a later version of the Suite. Such components include: