<!-- ============================================================= -->
<!-- MODULE: NCBI Book DTD Over-ride Classes Module -->
<!-- VERSION: 2.3 -->
<!-- DATE: February 2007 -->
<!-- -->
<!-- ============================================================= -->
<!-- ============================================================= -->
<!-- PUBLIC DOCUMENT TYPE DEFINITION -->
<!-- TYPICAL INVOCATION -->
<!--
"-//NLM//DTD NCBI Book DTD Over-ride Classes Module v2.3 20070202//EN"
Delivered as file "bookcustom-classes.ent" -->
<!-- ============================================================= -->
<!-- ============================================================= -->
<!-- SYSTEM: NCBI Book DTD of the -->
<!-- Archiving and Interchange DTD Suite -->
<!-- -->
<!-- PURPOSE: To declare the Parameter Entities (PEs) used to -->
<!-- over-ride the named element classes -->
<!-- -->
<!-- Note: Since PEs must be declared before they -->
<!-- are used, this module must be called before the -->
<!-- content modules that declare elements, and before -->
<!-- the default classes module. -->
<!-- -->
<!-- CONTAINS: 1) PEs for changing the contents of the default -->
<!-- element classes -->
<!-- -->
<!-- CREATED FOR: -->
<!-- Digital Archive of Journal Articles -->
<!-- National Center for Biotechnology Information -->
<!-- (NCBI) -->
<!-- National Library of Medicine (NLM) -->
<!-- -->
<!-- ORIGINAL CREATION DATE: -->
<!-- October 2004 -->
<!-- -->
<!-- CREATED BY: Bart Trawick (NCBI) -->
<!-- Jeff Beck (NCBI) -->
<!-- Deborah Lapeyre (Mulberry Technologies, Inc.) -->
<!-- B. Tommie Usdin (Mulberry Technologies, Inc.) -->
<!-- -->
<!-- Suggestions for refinements and enhancements to -->
<!-- this DTD should be sent in email to: -->
<!-- archive-dtd@ncbi.nlm.nih.gov -->
<!-- ============================================================= -->
<!-- ============================================================= -->
<!-- DTD VERSION/CHANGE HISTORY -->
<!-- ============================================================= -->
<!--
Version Reason/Occasion (who) vx.x (yyyy-mm-dd)
=============================================================
Version 2.3 (DAL/BTU/Beck) v2.3 (2007-02-02)
Enhancement Release (2.3) following the Working Group meetings
of Oct-Nov/2006-Jan/2007. No backward-incompatible changes.
Archiving loosened even more. New structures for all the DTDs.
10. SIMPLE LINK CLASS - Added new element to the
simple-link.class:
- <related-object>
9. EMPHASIS CLASS - Added new element to the emphasis.class:
- <sans-serif>
8. MILESTONES - Added <milestone-start> and <milestone-end>
to -%phrase.class;
7. NLM CITATION - Added <nlm-citation> as an alternative to
unstructured <citation>s by adding <nlm-citation>
to %citation.class;. This changed the models for:
- <ref>, which uses %citation.class; inside %ref-model;
6. Updated public identifier to "v2.3 20070202//EN"
=============================================================
Version 2.2 (DAL/BTU) v2.2 (2006-10-13)
Backwards-compatible changes to meet operational needs.
Typical changes include adding attribute values and making
required elements optional.
5. SIGNATURE BLOCK- Added <sig-block> to the end of section
<sec> by redefining -%sec-back.class;
4. Updated public identifier to "v2.3 20070202//EN"
=============================================================
Version 2.1 (DAL/BTU) v2.1 (2005-06-30)
Changed to MathML 2.0 and MathML 2.0 Character Sets
Added new material requested by the online list
3. PREFORMAT - Book needed to be able to use <named-content>
inside <preformat>, which Historical could already do, because
Historical mixes <named-content> into the emphasis.class.
So the same was done with book and the emphasis override was
created in this module to include <named-content>. Now both Book
and Historical can treat <named-content> as one of the emphasis
elements, and use it almost anywhere. Historical uses it for
yellow highlighting, underlining, etc. (Note that Historical
cannot use the SAME override, because Historical also adds
<annotation> to the emphasis class.)
Since <named-content> had to be removed from the
phrase.class to avoid clashes (as the emhasis.class is more
inclusive), phrase.class was also redefined to remove
<name-content>.
2. Updated public identifier to "v2.3 20070202"
=============================================================
Version 2.0 (DAL/BTU/TRG) v2.0 (2005-01-25)
1. Comments for this module were cleaned up as part of the delivery
of the NCBI Historical DTD. Since only comments were changed,
this was not even considered to be a dot release and the
formal public identifier remained unchanged. -->
<!-- ============================================================= -->
<!-- PARAMETER ENTITIES FOR CLASS OVER-RIDES -->
<!-- ============================================================= -->
<!-- ADDRESS LINK CLASS ELEMENTS -->
<!-- Link elements that can be used inside
addresses. This is essentially the three
generic external links.
(Note: in earlier releases, this Parameter
Entity was named %address-elements;,
although it functioned as a class.) -->
<!ENTITY % address-link.class
"email | ext-link | multi-link | uri" >
<!-- DISPLAY CLASS ELEMENTS -->
<!-- Graphical or other image-related elements.
The display elements may occur within
the text of a table cell or paragraph
although they are typically at the same
hierarchical level as a paragraph.
Added <map-group> -->
<!ENTITY % block-display.class
"array | boxed-text | chem-struct |
chem-struct-wrapper | fig | fig-group |
graphic | map-group | media | preformat |
supplementary-material | table-wrap |
table-wrap-group" >
<!-- BOOK PART CLASS -->
<!-- Those elements that are very like a book
part, where a book part is defined as a
chapter, part, module, unit, etc. -->
<!ENTITY % book-part.class
"book-part" >
<!-- CITATION CLASS ELEMENTS -->
<!-- Reference to an external document, as used
within, for example, the text of a
paragraph -->
<!ENTITY % citation.class
"citation | nlm-citation" >
<!-- CUSTOM METADATA WRAPPER CLASS -->
<!-- Hold the <custom-meta-wrap> element for use
in book-specific models -->
<!ENTITY % custom-meta.class
"custom-meta-wrap" >
<!-- EMPHASIS/RENDITION ELEMENTS -->
<!-- Elements concerning with marking the location
of typographical emphasis (highlighting)
DTD Design Note: There are no emphasis
elements for <fractur>, <openface> (black
board), <script>, etc. because this DTD
recommends the use of the STIX extensions
to accomplish this, as soon as they are
available.
Added <page-start>, this milestone element
marks the start of a physical page in the
printed edition of a historical work. It
is a type of typographic effect, as are the
emphasis elements and should be allowed
anywhere text is allowed, as they are, thus
being excluded from very few elements: all the
identifiers, some elements only used inside
inside references, and metadata elements.
Added <named-content> (and removed it
from %phrase.class;) because it will be
used to mark historical emphasis, such as
pencil underlining, ink circled words, or
highlighting using a yellow highlighter.
Added <annotation>, which is only slightly
over-loading this element. An inline
<annotation> element is used for inline
commentary, which may not typographical
emphasis, but which may be rhetorical
emphasis and, in any case, needs to be
used anywhere real emphasis is allowed. -->
<!ENTITY % emphasis.class
"bold | italic | monospace | named-content |
overline | overline-start | overline-end |
sans-serif | sc | strike | underline |
underline-start | underline-end " >
<!-- SECTION BACK MATTER CLASS -->
<!-- Ancillary elements, typically used in the
back matter of a section, etc. -->
<!ENTITY % sec-back.class
"fn-group | glossary | ref-list |
sig-block" >
<!-- PHRASE CLASS ELEMENTS -->
<!-- Small inline elements, that surround a word
or phrase in the text because the subject
(content) should be identified as something
special or different
Added <alt-term>.
Removed <named-content> because it was
promoted to the even more ubiquitous mix,
%emphasis.class; -->
<!ENTITY % phrase.class "abbrev | milestone-end | milestone-start" >
<!-- SIMPLE LINKS/CROSS-REFERENCES CLASS -->
<!-- The smaller and simpler linking elements
that might be inside, for example, a
Keyword <kwd>. Adds <related-object> to
the base Suite. -->
<!ENTITY % simple-link.class
"fn | target | xref | related-object" >
<!-- ================== End NCBI Book DTD Over-ride Classes ====== -->