<!-- ============================================================= -->
<!--  MODULE:    Default Element Mixes Module                      -->
<!--  VERSION:   ANSI/NISO JATS Version 1.0 (Z39.96-2012)          -->
<!--  DATE:      March 2012                                        -->
<!--                                                               -->
<!-- ============================================================= -->

<!-- ============================================================= -->
<!--                    PUBLIC DOCUMENT TYPE DEFINITION            -->
<!--                        TYPICAL INVOCATION                     -->
<!--
"-//NLM//DTD JATS (Z39.96) Default Element Mixes Module v1.0 20120330//EN"
Delivered as file "JATS-default-mixes1.ent"                        -->
<!-- ============================================================= -->


<!-- ============================================================= -->
<!-- SYSTEM:     JATS DTD Suite                                    -->
<!--                                                               -->
<!-- PURPOSE:    Declares default values for all the element mixes -->
<!--             used in the content models of the DTD Suite       -->
<!--                                                               -->
<!--             Mixes are Or-groups of classes, used in many      -->
<!--             different content models. Mixes should not use    -->
<!--             element names directly, only through classes.     -->
<!--                                                               -->
<!--             Note: Since PEs must be declared before they      -->
<!--             are used, this module must be called after the    -->
<!--             customize mixes module (if any).                  -->
<!--                                                               -->
<!-- TAG SET SPONSOR                                               -->
<!--             National Center for Biotechnology                 -->
<!--                Information (NCBI)                             -->
<!--             National Library of Medicine (NLM)                -->
<!--                                                               -->
<!-- CREATED FOR:                                                  -->
<!--             This module was created for the JATS DTD Suite.   -->
<!--             Digital archives and publishers may use the       -->
<!--             DTD as is for markup of journal literature or     -->
<!--             related material for archiving and transferring   -->
<!--             such material between archives or create a        -->
<!--             custom XML DTD from the Suite for                 -->
<!--             these purposes.                                   -->
<!--                                                               -->
<!--             This DTD is in the public domain. An organization -->
<!--             that wishes to create its own DTD from the suite  -->
<!--             may do so without permission from NLM.            -->
<!--                                                               -->
<!--             The suite has been set up to be extended using a  -->
<!--             new DTD file and a new DTD-specific customization -->
<!--             module to redefine the many Parameter Entities.   -->
<!--             Do not modify the suite directly or redistribute  -->
<!--             modified versions of the suite.                   -->
<!--                                                               -->
<!--             In the interest of maintaining consistency and    -->
<!--             clarity for potential users, NLM requests:        -->
<!--                                                               -->
<!--             1. If you create a DTD from the JATS DTD Suite    -->
<!--                and intend to stay compatible with the suite,  -->
<!--                then please include the following statement    -->
<!--                as a comment in all of your DTD modules:       -->
<!--                   "Created from, and fully compatible with,   -->
<!--                    the ANSI/NISO Z39.96 Journal Article Tag   -->
<!--                    Suite (JATS)."                             -->
<!--                                                               -->
<!--             2. If you alter one or more modules of the suite, -->
<!--                then please rename your version and all its    -->
<!--                modules to avoid any confusion with the        -->
<!--                original suite. Also, please include the       -->
<!--                following statement as a comment in all your   -->
<!--                DTD modules:                                   -->
<!--                   "Based in part on, but not fully compatible -->
<!--                    with, the ANSI/NISO Z39.96 Journal Article -->
<!--                    Tag Suite (JATS)."                         -->
<!--                                                               -->
<!-- ORIGINAL CREATION DATE:                                       -->
<!--             August 2004                                       -->
<!--                                                               -->
<!-- CREATED BY: Mulberry Technologies, Inc. for the NISO Z39.96   -->
<!--             Working Group. Mulberry Technologies was          -->
<!--             supported by National Center for Biotechnology    -->
<!--             Information (NCBI), a center of the US National   -->
<!--             Library of Medicine (NLM).                        -->
<!--                                                               -->
<!--             This module is part of the JATS DTD Suite. The    -->
<!--             Suite is a continuation of work done by NCBI,     -->
<!--             Mulberry Technologies, and Inera, Inc. on the NLM -->
<!--             Journal Archiving and Interchange DTD Suite, which-->
<!--             was originally released in December, 2002.        -->
<!--                                                               -->
<!--             NLM thanks the Harvard University Libraries, both -->
<!--             for proposing that a draft archiving NLM DTD for  -->
<!--             life sciences journals be extended to accommodate -->
<!--             journals in all disciplines and for sponsoring    -->
<!--             Inera Inc.'s collaboration with other DTD         -->
<!--             authors in completing NLM Version 1.0. The        -->
<!--             Andrew W. Mellon Foundation provided support for  -->
<!--             these important contributions.                    -->
<!--                                                               -->
<!--             Suggestions for refinements and enhancements to   -->
<!--             this DTD should be sent in email to:              -->
<!--                 jats@ncbi.nlm.nih.gov                         -->
<!-- ============================================================= -->


<!-- ============================================================= -->
<!--                    DTD VERSION/CHANGE HISTORY                 -->
<!-- ============================================================= -->
<!--

Version  Reason/Occasion                   (who) vx.x (yyyy-mm-dd)
   
     =============================================================
     NISO JATS Version 1.0             (DAL/BTU) v1.0 (2012-xx-xx)
   
     ANSI/NISO Z39.96-2012 (Version 1.0) 

     Details concerning ANSI/NISO Z39.96-2012 JATS-based DTDs, XSDs, 
     RNGs and supporting documentation are available at
           http://jats.nlm.nih.gov/1.0/
   
  5. PARA-LEVEL PARAMETER ENTITY CONFLICT - Changed the parameter
     entity %para-level; to use the PE %nothing-but-para.class;,
     removing the similar PE "just-para.class;". It is possible to 
     add element(s) to %just-para.class;, so that the added element(s)
     may be used everywhere <p> is used. Such elements would also be
     named in %block-display.class;. This would lead to a conflict
     in %para-level; if both %just-para.class; and
     %block-display.class; named <p>. So %just-para; is replaced
     here in %para-level;. This is backward compatible for all XML
     documents. If a JATS customization has modified %just-para.class;
     they may need to change their customization to accommodate.
   
  4. Updated the DTD-version attribute to "1.0" and the formal
     public identifier to the date: "v1.0 20120330//EN".

     =============================================================
     Version 0.4                       (DAL/BTU) v0.4 (2011-01-31)
   
     This Tag Set is in the process of becoming a NISO standard.
     The version numbers are starting over from 0.4", as a Trial
     Use Draft, to be made into "Version 1.0" when the Tag Suite 
     becomes a NISO standard. Thus, the version number that would
     have been "NLM Version 3.1 Draft" has become NISO JATS
     "Version 0.4".

     Details on NISO Trial Use Draft Version 0.4 are available at
           http://jats.nlm.nih.gov/JATS-0.4.
   
  3. Updated the DTD-version attribute to "0.4" 
   
  2. Updated the public identifier to "v0.4 20110131", 
     modified the formal public identifier to include "JATS (Z39.96)",
     and the filename as delivered to include "JATS" and the
     new version number "0".
           http://jats.nlm.nih.gov/0.4.

     =============================================================
     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"              -->

<!-- ============================================================= -->
<!--                    ELEMENT MIXES FOR USE IN CONTENT MODELS    -->
<!--                    (MIXES ARE COMPOSED USING CLASSES)         -->
<!-- ============================================================= -->


<!--                    SECTION-LEVEL ELEMENTS                     -->
<!--                    Elements that may be used at the same
                        structural level as a Section for example
                        inside the Body <body>                     -->
<!ENTITY % sec-level    "%sec.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.
                        (Note: Technically this should have used
                        %sec.class;, but %sec-level; was used in an
                        earlier release and backwards compatibility
                        must be maintained.                        -->
<!ENTITY % doc-back-matter-mix
                        "%back.class; | %front-back.class; |
                         %sec.class;"                                >


<!--                    SECTION BACK MATTER ELEMENTS               -->
<!--                    Back matter elements used inside smaller
                        structures, such as sections and sidebars  -->
<!ENTITY % sec-back-matter-mix
                        "%front-back.class; | %sec-back.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; |
                         %list.class; | %math.class; | 
                         %nothing-but-para.class; | 
                         %related-article.class; |
                         %rest-of-para.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.
                        ### Usage Alert ###
                        Design 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  "%address-link.class; |  %appearance.class; |
                         %article-link.class; |
                         %block-math.class; | %break.class; |
                         %citation.class; | %emphasis.class; |
                         %inline-math.class; |
                         %list.class; | %math.class; |
                         %phrase.class; | %simple-display.class; |
                         %inline-display-noalt.class; |
                         %simple-link.class; | %subsup.class;"       >


<!--                    INSIDE TABLE WRAPPER ELEMENTS              -->
<!--                    Usually a Table Wrapper contains a table,
                        properly tagged with rows and columns, but
                        sometimes, a structure that is labeled as
                        a "table" is actually a list, or two
                        paragraphs.  This Parameter Entity names
                        all the alternatives to table that may
                        occur inside a table wrapper.              -->
<!ENTITY % inside-table-wrap
                        "%intable-para.class; | %list.class; |
                         %simple-intable-display.class;  |
                         %table.class;"                              >


<!-- ============================================================= -->
<!--                    INLINE ELEMENT MIXES                       -->
<!-- ============================================================= -->


<!--                    EMPHASIS MIX ELEMENTS                      -->
<!--                    Elements that may be used inside most of the
                        emphasis class elements
                        Design Note: Inline mixes begin with an
                        OR bar                                     -->
<!ENTITY % emphasized-text
                        "| %address-link.class; |
                         %article-link.class; | %emphasis.class;  |
                         %inline-display.class; |
                         %inline-math.class; | %math.class; |
                         %phrase.class; | %simple-link.class; |
                         %subsup.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 .
                        Design Note: Inline mixes begin with an
                        OR bar                                     -->
<!ENTITY % just-rendition
                        "| %emphasis.class;  | %subsup.class; |
                         %phrase-content.class;"                     >


<!--                    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 .
                        Design Note: Inline mixes begin with an
                        OR bar                                     -->
<!ENTITY % rendition-plus
                        "| %emphasis.class;  | %subsup.class; |
                         %phrase-content.class;"                     >


<!--                    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. In practice, This is the next step
                        up from "simple-text", adding the links.
                        Design Note: Inline mixes begin with an
                        OR bar                                     -->
<!ENTITY % simple-phrase
                        "| %address-link.class; |
                         %article-link.class; | %emphasis.class; |
                         %inline-display.class; |
                         %inline-math.class; | %math.class; |
                         %phrase.class; | %simple-link.class; |
                         %subsup.class;"                             >


<!--                    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 there is only inline math and no 
                        links.
                        Simpler even than %simple-phrase;
                        Design Note: Inline mixes begin with an
                        OR bar                                     -->
<!ENTITY % simple-text  "| %emphasis.class; | %inline-display.class; |
                         %inline-math.class; | %phrase.class; |
                         %subsup.class; "                            >


<!-- ================== End Archiving DTD Mixes Customization ==== -->
