<!– ============================================================= –> <!– MODULE: Journal Archiving DTD Customize Mixes Module –> <!– VERSION: 3.0 –> <!– DATE: Feb 2008 –> <!– –> <!– ============================================================= –>
<!– ============================================================= –> <!– PUBLIC DOCUMENT TYPE DEFINITION –> <!– TYPICAL INVOCATION –> <!– “-//NLM//DTD Journal Archiving with OASIS Tables Customize Mixes Module v3.0 20080202//EN” Delivered as file “archivecustom-mixes3.ent” –> <!– ============================================================= –>
<!– ============================================================= –> <!– SYSTEM: Journal Archiving and Interchange DTD of the –> <!– Archiving and Interchange DTD Suite –> <!– –> <!– PURPOSE: Declares over-ride values for the default element –> <!– mixes in the Suite. These over-rides are specific –> <!– to the Journal Archiving and Interchange DTD. –> <!– –> <!– Note: Since PEs must be declared before they –> <!– are used, this module must be called before the –> <!– default mixes modules (%default-mixes;) –> <!– –> <!– CONTAINS: 1) PEs that define the element mixes to be –> <!– over-ridden –> <!– –> <!– CREATED FOR: –> <!– Digital Archive of Journal Articles –> <!– National Center for Biotechnology Information –> <!– (NCBI) –> <!– National Library of Medicine (NLM) –> <!– –> <!– ORIGINAL CREATION DATE: –> <!– August 2004 –> <!– –> <!– CREATED BY: 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 3.0 (DAL/BTU) v3.0 (2007-10-31) Version 3.0 is the first non-backward-compatible release. In addition to the usual incremental changes, some elements and attributes have been renamed and/or remodeled to better meet user needs and to increase tag set consistency. All module change histories are available through the Tag Suite web site at http://dtd.nlm.nih.gov. Details on version 3.0 are available at http://dtd.nlm.nih.gov/3.0. 1. Updated public identifier to "v3.0 20080202//EN" ============================================================= (LAK) v3.0 (2008-12-2) 1. Updated PUBLIC identifier to indicate inclusion of OASIS table models. -->
<!– ============================================================= –> <!– ELEMENT MIXES FOR USE IN CONTENT MODELS –> <!– (MIXES ARE COMPOSED USING CLASSES) –> <!– ============================================================= –>
<!– ============================================================= –> <!– EXCEPTION: A MIX USED IN OTHER MIXES –> <!– ============================================================= –>
<!– ALL PHRASE-LEVEL ELEMENTS –> <!– This Parameter Entity contains all of the
phrase-level elements in the entire Archival Tag Set EXCEPT THE <break> element. MAINTENANCE NOTE: 1) Since this is used in other mixes, unlike all other mixes, all-phrase must be declared first in this module. 2) Since it acts like a class (is used in other mixes) it does not start with an OR bar, as all other inline mixes do -->
<!ENTITY % all-phrase “%address-link.class; | %article-link.class; |
%appearance.class; | %emphasis.class; | %inline-display.class; | %inline-math.class; | %math.class; | %phrase.class; | %simple-link.class; | %subsup.class; | %x.class;" >
<!– ============================================================= –> <!– TABLE ELEMENT MIXES –> <!– ============================================================= –>
<!– INSIDE TABLE CELL ELEMENTS –> <!– Mixed with #PCDATA inside a table cell, such
as a <td> or <th> element in the XHTML table model, the <entry> element in the OASIS CALS table model, etc. This PE will be used as the value of %Flow.mix;, %paracon;, etc. MAINTENANCE NOTE: Inside cell is an exception, an inline mix that does not start with an OR bar. This is because is used within the PE -%Flow.mix;, which is an inline mix defined in the course of the XHTML Table DTD, a DTD not under control of this DTD Suite. -->
<!ENTITY % inside-cell “%all-phrase; | %block-math.class; |
%break.class; | %chem-struct-wrap.class; | %citation.class; | %list.class; | %simple-display-noalt.class;" >
<!– ============================================================= –> <!– BACK MATTER ELEMENT MIXES(%backmatter.ent;)–> <!– ============================================================= –>
<!– DOCUMENT BACK MATTER ELEMENTS –> <!– Back Matter Elements used by a full document
such as a journal article. This is an element grouping rather than a class. These elements may also appear in the content models of structural elements, such as back matter. -->
<!ENTITY % doc-back-matter-mix
"%back.class; | %front-back.class; | %sec.class;" >
<!– ============================================================= –> <!– PARAGRAPH-LEVEL ELEMENT MIXES –> <!– ============================================================= –>
<!– PARAGRAPH-LEVEL ELEMENTS –> <!– Elements that may be used at the same
structural level as a paragraph, for example inside a Section Note: There a major overlap between this parameter entity and that for the elements that are at the same level as a paragraph. Inline elements appear only inside a paragraph, but block elements such as quotes and lists may appear either within a paragraph or at the same level as a paragraph. This serves a requirement in a repository DTD, since some incoming material will have restricted such elements to only inside a paragraph, some incoming material will have restricted them to only outside a paragraph and some may allow them in both places. Thus the DTD must allow for them to be in either or both. -->
<!ENTITY % para-level “%block-display.class; | %block-math.class; |
%just-para.class; | %list.class; | %math.class; | %related-article.class; | %rest-of-para.class; | %x.class;" >
<!– ============================================================= –> <!– INLINE ELEMENT MIXES –> <!– ============================================================= –>
<!– EMPHASIS MIX ELEMENTS –> <!– Elements that may be used inside most of the
emphasis class elements -->
<!ENTITY % emphasized-text
"| %all-phrase; | %break.class;" >
<!– JUST RENDITION –> <!– Only the simplest of the typographic
emphasis elements, as well as subscript and superscript. Usually used in a model that allows #PCDATA and this restricted mixture. This mix may be stripped down to only subscript and superscript by some, more restrictive DTDs. MAINTENANCE NOTE: This Parameter Entity and the related PE "rendition-plus" have been put in place to restrict the amount of variability that a person modifying the DTD through PE redefinition can achieve. Some elements have been set #PCDATA plus one PE and some have been set to #PCDATA plus the other in an effort to allow designers to modify entire groups of elements, but not to change similar models individually . -->
<!ENTITY % just-rendition
"| %all-phrase;" >
<!– RENDITION MARKUP PLUS –> <!– Only the simplest of the typographic
emphasis elements, as well as subscript and superscript. Usually used in a model that allows #PCDATA and this restricted mixture. This mix may be enhanced slightly in some more permissive DTDs, and should always contain at least typographic emphasis, subscript, and superscript. MAINTENANCE NOTE: This Parameter Entity and the related PE "just-rendition" have been put in place to restrict the amount of variability that a person modifying the DTD through PE redefinition can achieve. Some elements have been set #PCDATA plus one PE and some have been set to #PCDATA plus the other in an effort to allow designers to modify entire groups of elements, but not to individually change similar models. modify entire groups of elements, but not to change similar models individually . -->
<!ENTITY % rendition-plus
"| %all-phrase;" >
<!– SIMPLE PHRASE-LEVEL TEXTUAL ELEMENTS –> <!– Elements that may be used almost anywhere
text is used, for example, inside a title. Simple text plus inline display and math elements. -->
<!ENTITY % simple-phrase
"| %all-phrase;" >
<!– SIMPLE TEXTUAL CONTENT –> <!– Elements that may be used inside elements
that are really expected to be #PCDATA and not to contain any of these things. Note that in the original, this contained no math and no links, thus is was even simpler than %simple-phrase; (AS of v2 2004) the two are the same. -->
<!ENTITY % simple-text “| %all-phrase;” >
<!– ================== End Archiving DTD Mixes Customization ==== –>