<!– ============================================================= –> <!– MODULE: Article Authoring DTD Over-ride Content and –> <!– Attribute Module –> <!– VERSION: ANSI/NISO JATS Version 1.0 (Z39.96-2012) –> <!– DATE: Feb 2008 –> <!– –> <!– ============================================================= –>
<!– ============================================================= –> <!– PUBLIC DOCUMENT TYPE DEFINITION –> <!– TYPICAL INVOCATION –> <!– “-//NLM//DTD JATS (Z39.96) Article Authoring DTD Over-ride Content and Attribute Module v3.0 20080202//EN” Delivered as file “JATS-articleauthcustom-models1.ent” –> <!– ============================================================= –>
<!– ============================================================= –> <!– SYSTEM: Article Authoring DTD of the JATS DTD Suite –>
<!– –> <!– PURPOSE: To declare the Parameter Entities (PEs) used to –> <!– over-ride the content models, parts of content –> <!– models, or attribute lists of the JATS DTD Suite –> <!– –> <!– Or-groups within models should use mixes or –> <!– classes rather than name elements directly. –> <!– –> <!– Note: Since PEs must be declared before they –> <!– are used, this module must be called before the –> <!– content modules that declare elements. –> <!– –> <!– TAG SET SPONSOR –> <!– National Center for Biotechnology –> <!– Information (NCBI) –> <!– National Library of Medicine (NLM) –> <!– –> <!– CREATED FOR: –> <!– This DTD was created from the JATS DTD Suite. –> <!– Authors, 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: –> <!– June 2005 –> <!– –> <!– 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). –> <!– –> <!– The Article Authoring DTD is built from the –> <!– Archiving and Interchange DTD Suite. –> <!– –> <!– 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/ 13. RELATED OBJECT - Added <related-object> everywhere <related-article> was used, including inside <article-meta> using article-meta-model. 12. CONTRIBUTOR MODEL - Added "contrib-id.class" to the beginning at the <contrib> model, to hold identifiers for people, such as publishers-specific IDs, ORCIDs, and JST and NII identifiers. 11. STANDARDS ORGANIZATION - Added std-organization-elements to reduce what was allowed in the names of standards bodies. 10. PARAGRPH PARAMETER ENTITY SYNTAX CHANGE (no models changed) Fixed content models that were stated as "p*", "p+". and "sec*" to use the %just-para.class; and %sec.class; classes. Element models that were changed include: - abstract - ack - app-group - disp-quote-model - glossary - ref-list 9. Updated the public identifier to "v1.0 20120330//EN", modified the formal public identifier to include "JATS (Z39.96)", and the filename as delivered to include "JATS" and the new version number "1". ============================================================= 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. 8. Updated the DTD-version attribute to "0.4" 7. 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. 6. KEYWORD GROUP - Made <kwd-group> repeatable inside <article-meta> by modifying %article-meta-model; 5. MEDIA - In 3.0 <graphic> and <media> used the same model, defined by %graphic-model;. In 0.4, %media-model; was added to separate the redefinition possibilities. Since Authoring had redefined %graphic-model;, the same redefinition was necessary for <media> through %media-model;. 4. INITIALS - Removed the attribute over-ride for <surname> and <given-names> to allow the use of @initials. 3. PERSON-GROUP - Became a mixed-content model, so the parameter entity %person-group-model: was changed to %person-group-elements;, which will be mixed with #PCDATA as defined in references.ent. The PE person-group-model has been retained in references.ent for compatibility, but has been set to the mixed model using person-group-elements. 2. @SPECIFIC-USE and @XML:LANG - Added the @specific-use to the following over-rides: - fn through fn-atts (@specific-use only; @xml:lang already) - inline-graphic-atts through inline-graphic-atts (both) - list through list-atts (@xml:lang only; @specific-use already) - person-group through person-group-atts (both - underline through underline-atts (both) ============================================================= 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" -->
<!– ============================================================= –> <!– INLINE MIXES TO OVER-RIDE CONTENT MODELS –> <!– (ELEMENTS TO BE ADDED TO PCDATA IN MODELS)–> <!– ============================================================= –>
<!– ADDRESS LINE ELEMENTS –> <!– Elements for use in the <addr-line> element–> <!ENTITY % addr-line-elements
"%rendition-plus; | %address-line.class;" >
<!– AFFILIATION ELEMENTS –> <!– Elements for use in the <aff> element
Removed <label> -->
<!ENTITY % aff-elements “| %address.class; | %address-link.class; |
%break.class; | %emphasis.class; | %simple-link.class; | %subsup.class;" >
<!– AWARD-ID ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of the <award-id> -->
<!ENTITY % award-id-elements
"" >
<!– CHEMICAL STRUCTURE ELEMENTS –> <!– Those elements that may mix with the data
characters inside a Chemical Structure <chem-struct> -->
<!ENTITY % chem-struct-elements
"| %access.class; | %address-link.class; | %break.class; | %emphasis.class; | %id.class; | %list.class; | %simple-display.class; | %simple-link.class; | %subsup.class; " >
<!– CITATION ELEMENTS –> <!– Content for both types of citation. These
elements may be mixed with #PCDATA in the <mixed-citation> element (in which all punctuation and spacing are left intact), and they also constitute the choices that can be used to form the all-element-content of the <element-citation> element (in which punctuation and spacing are removed). Design Note: All inline mixes begin with an OR bar. -->
<!ENTITY % citation-elements
"%emphasis.class; | %inline-display.class; | %inline-math.class; | %phrase.class; | %references.class; | %subsup.class;" >
<!– COLLABORATIVE (GROUP) AUTHOR ELEMENTS –> <!– Elements for use in the <collab> element
Design Note: All inline mixes begin with an OR bar, but since %rendition-plus; is an inline mix, the OR bar is already there. -->
<!ENTITY % collab-elements
"%rendition-plus; | %address.class; | %contrib-info.class;" >
<!– COMMENT ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of the Comment in a Citation <comment> element. Design Note: All inline mixes begin with an OR bar, but since %simple-phrase; is an inline mix, the OR bar is already there. -->
<!ENTITY % comment-elements
"| %address-link.class; | %article-link.class; | %emphasis.class; | %inline-display.class; | %inline-math.class; | %phrase.class; | %subsup.class;" >
<!– CONFERENCE ACRONYM ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of the conference acronym. Design Note: All inline mixes begin with an OR bar, but since %simple-text; is an online mix, the OR bar is already there. -->
<!ENTITY % conf-acronym-elements
"" >
<!– CONFERENCE LOCATION ELEMENTS –> <!– Elements for use in the <conf-loc> element
Removed %simple-text; -->
<!ENTITY % conf-loc-elements
"" >
<!– CONFERENCE NAME ELEMENTS –> <!– Elements for use in the <conf-name> element.
Removed %simple-text; -->
<!ENTITY % conf-name-elements
"" >
<!– CONFERENCE NUMBER ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of the conference number. Design Note: All inline mixes begin with an OR bar, but since %simple-text; is an inline mix, the OR bar is already there. -->
<!ENTITY % conf-num-elements
"" >
<!– CONFERENCE SPONSOR ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of the conference sponsor. -->
<!ENTITY % conf-sponsor-elements
"" >
<!– CORRESPONDENCE INFORMATION ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of the correspondence information. -->
<!ENTITY % corresp-elements
"| %address.class; | %address-link.class; | %emphasis.class; | %subsup.class;" >
<!– DEGREE(S) ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of <degrees> -->
<!ENTITY % degrees-elements
"" >
<!– FORMULA, DISPLAY ELEMENTS –> <!– Elements for use mixed with PCDATA within
the <disp-formula> element -->
<!ENTITY % disp-formula-elements
"| %access.class; | %address-link.class; | %break.class; | %emphasis.class; | %display-back-matter.class; | %inline-display.class; | %inline-math.class; | %label.class; | %math.class; | %simple-display.class; | %subsup.class;" >
<!– EDITION ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of <edition> -->
<!ENTITY % edition-elements
"" >
<!– FAX NUMBER ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of a <fax> -->
<!ENTITY % fax-elements “” >
<!– FUNDING-SOURCE ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of the <funding-source> -->
<!ENTITY % funding-source-elements
"" >
<!– GIVEN (FIRST) NAMES ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of a <given-names> -->
<!ENTITY % given-names-elements
"" >
<!– INSTITUTION NAME ELEMENTS –> <!– Elements for use in the <institution>
element -->
<!ENTITY % institution-elements
"| %subsup.class;" >
<!– ISSUE TITLE ELEMENTS –> <!– Elements for use with data characters inside
the model for the <issue> element -->
<!ENTITY % issue-elements
"" >
<!– KEYWORD CONTENT ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of a keyword <kwd>. -->
<!ENTITY % kwd-elements “| %emphasis.class; | %phrase.class; |
%subsup.class;" >
<!– LABEL ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of the <label> element -->
<!ENTITY % label-elements
"" >
<!– PATENT NUMBER ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of <patent> -->
<!ENTITY % patent-elements
"" >
<!– PERSON GROUP MODEL –> <!– Content model for the <person-group> element
-->
<!ENTITY % person-group-elements
"| %name.class; | %person-group-info.class; | %string-name.class;" >
<!– PHONE NUMBER ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of a <phone number> -->
<!ENTITY % phone-elements
"" >
<!– PREFIX ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of a <prefix> -->
<!ENTITY % prefix-elements
"" >
<!– PREFORMATTED TEXT ELEMENTS –> <!– Elements that may be used, along with data
characters, inside the content model for the <preformat> element, in which white space, such as tabs, line feeds, and spaces will be preserved -->
<!ENTITY % preformat-elements
"| %access.class; | %address-link.class; | %display-back-matter.class; | %emphasis.class; | %phrase.class; | %subsup.class;" >
<!– PRODUCT ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of the <product> element -->
<!ENTITY % product-elements
"| %article-link.class; | %emphasis.class; | %inline-display.class; | %inline-math.class; | %phrase.class; | %price.class; | %references.class; | %simple-link.class; | %subsup.class;" >
<!– PUBLISHER’S LOCATION ELEMENTS –> <!– Elements for use in the Publisher Location
<publisher-loc> element -->
<!ENTITY % publisher-loc-elements
"" >
<!– PUBLISHER’S NAME ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of a <publisher-name> -->
<!ENTITY % publisher-name-elements
"" >
<!– ROLE ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of a <role> Design Note: All inline mixes begin with an OR bar; since %rendition-plus; is an inline mix, the OR bar is already there. -->
<!ENTITY % role-elements
"" >
<!– SUFFIX ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of a <suffix> -->
<!ENTITY % suffix-elements
"" >
<!– SOURCE ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of a <source>. -->
<!ENTITY % source-elements
"| %emphasis.class; | %address-link.class; | %subsup.class;" >
<!– STANDARDS ORGANIZATION ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of <std-organization>. Removed emphasis.class. -->
<!ENTITY % std-organization-elements
"| %subsup.class;" >
<!– SURNAME ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of a <surname> -->
<!ENTITY % surname-elements
"" >
<!– DEFINITION LIST: TERM ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of a <term>. Design Note: All inline mixes begin with an OR bar, but since %simple-phrase; is an inline mix, the OR bar is already there. -->
<!ENTITY % term-elements
"| %address-link.class; | %article-link.class; | %emphasis.class; | %inline-display.class; | %inline-math.class; | %phrase.class; | %simple-link.class; | %subsup.class;" >
<!– URI ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of a <uri> -->
<!ENTITY % uri-elements
"" >
<!– VOLUME NUMBER ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of a <volume> -->
<!ENTITY % volume-elements
"" >
<!– ============================================================= –> <!– OVER-RIDES USED IN SHARED CONTENT MODELS –> <!– ============================================================= –>
<!– DISPLAY ELEMENT BACK MATTER SEQUENCE –> <!– Miscellaneous stuff at the end of a display
element such as a figure or a boxed text element such as a sidebar -->
<!ENTITY % display-back-matter
"attrib?, permissions?" >
<!– ============================================================= –> <!– OVER-RIDES OF SHARED CONTENT MODELS (FULL) –> <!– ============================================================= –>
<!– CONTENT MODEL FOR A STRUCTURAL SECTION –> <!– The model for a section that requires that a
section title be present, used for elements such as Section and Appendix. -->
<!ENTITY % sec-model “(title, (%para-level;)*, (%sec-level;)* )” >
<!– CONTENT MODEL FOR AN UNTITLED SECTION –> <!– The model for a section-like structure that
may or may not have an initial title -->
<!ENTITY % sec-opt-title-model
"(title?, (%para-level;)*, (%sec-level;)* )" >
<!– ============================================================= –> <!– OVER-RIDES OF CONTENT MODELS (FULL MODELS) –> <!– ============================================================= –>
<!– ABSTRACT MODEL –> <!– Abstracts may contain one or more paragraphs
(as a typical abstract does) or titled sections, as is done in many physics articles. -->
<!ENTITY % abstract-model
"(title?, (%just-para.class;)*, %sec.class;*)" >
<!– ACKNOWLEDGMENTS MODEL –> <!– Content model for the <ack> element
Deleted optional sections and closing reference list -->
<!ENTITY % ack-model “(title?, (%just-para.class;)*)” >
<!– ANONYMOUS MODEL –> <!– Content model for the element <anonymous>.
When present, it is used to generate the text "anonymous" or "anon.", etc. -->
<!ENTITY % anonymous-model
"EMPTY" >
<!– ADDRESS MODEL –> <!– Content model for the <address> element –> <!ENTITY % address-model
"(institution?, addr-line*, country, phone*, fax*, email*, ext-link*, uri*)" >
<!– AFFILIATION MODEL –> <!– Content model for the <aff> element –> <!ENTITY % aff-model “(institution?, addr-line*, country, phone*,
fax*, email*, ext-link*, uri*)" >
<!– APPENDIX GROUP MODEL –> <!– Content model for the <app-group> element –> <!ENTITY % app-group-model
"(title?, (%just-para.class;)*, (%app.class;)* )" >
<!– ARTICLE METADATA MODEL –> <!– Full content model for the metadata that is
specific to the article. -->
<!ENTITY % article-meta-model
"(title-group, contrib-group, (product | supplementary-material)*, permissions?, self-uri*, (%related-article.class;)*, abstract+, kwd-group*, funding-group*, conference*)" >
<!– BOXED TEXT MODEL –> <!– Complete content model for the boxed text
element which is used for sidebars, marginalia, and other text that is outside the narrative flow. -->
<!ENTITY % boxed-text-model
"((%id.class;)*, caption?, (%para-level;)*, (%sec-level;)*, %display-back-matter; )" >
<!– CHEMICAL STRUCTURE WRAPPER MODEL –> <!– Content model for the Chemical Structure
Wrapper <chem-struct-wrap> element -->
<!ENTITY % chem-struct-wrap-model
"((%id.class;)*, (%caption.class;)?, (%access.class;)*, (%inside-chem-struct-wrap.class;)+, %display-back-matter;)" >
<!– CONFERENCE MODEL –> <!– The element components that describe
of a conference -->
<!ENTITY % conference-model
"(conf-date, (conf-name | conf-acronym )+, conf-num?, conf-loc?, conf-sponsor*, conf-theme?)" >
<!– CONTRIBUTOR MODEL –> <!– Content model for the <contrib> element –> <!ENTITY % contrib-model
"((%contrib-id.class;)*, (%name.class;)*, (%degree.class;)*, role?, on-behalf-of?, (%aff-alternatives.class;)*, address*, email*, ext-link*, uri*, bio?, author-comment?)" >
<!– CONTRIBUTOR GROUP MODEL –> <!– Content model for the <contrib-group>
element -->
<!ENTITY % contrib-group-model
"(%contrib.class;+)" >
<!– DATE ELEMENTS MODEL –> <!– The content models for elements that describe
dates, such as Publication Date <pub-date> and History Dates <date>. The <string-date> element holds dates for which months and years are not given, for example "first quarter", "spring", etc. -->
<!ENTITY % date-model
"(((day?, month?) | season)?, year)" >
<!– DEFINITION LIST MODEL –> <!– Content model for the <def-list> element –> <!ENTITY % def-list-model
"(title?, term-head?, def-head?, def-item+)" >
<!– DEFINITION LIST: DEFINITION ITEM ELEMENTS –> <!– The elements that can be included inside
the content model of a <def-item> -->
<!ENTITY % def-item-model
"(term, def*)" >
<!– QUOTE, DISPLAYED MODEL –> <!– Content model for the Display Quote element–> <!ENTITY % disp-quote-model
"(title?, (%just-para.class;)+, %display-back-matter; )" >
<!– FIGURE GROUP MODEL –> <!– Content model for a Figure Group element –> <!ENTITY % fig-group-model
"((%caption.class;)?, (%access.class; | %address-link.class;)*, (%fig-display.class; | %just-base-display.class;)* )" >
<!– FIGURE-LIKE CONTENT MODEL –> <!– Content model for the Figure element and any
similarly structured elements -->
<!ENTITY % fig-model “((%id.class;)*, (%caption.class;)?,
(%access.class;)*, (%block-math.class; | %chem-struct-wrap.class; | %intable-para.class; | %just-table.class; | %just-para.class; | %list.class; | %simple-display.class;)*, %display-back-matter; )" >
<!– FOOTNOTE GROUP MODEL –> <!– Content model for the <fn-group> element –> <!ENTITY % fn-group-model
"(title?, (%fn-link.class;)+ )" >
<!– FOOTNOTE MODEL –> <!– Content model for Footnote <fn> –> <!ENTITY % fn-model “((%just-para.class;)+ )” >
<!– GLOSSARY MODEL –> <!– Content model for the <glossary> element –> <!ENTITY % glossary-model
"(title?, (%just-para.class;)*, def-list*, glossary* )" >
<!– GRAPHIC MODEL –> <!– Content model for the <graphic> element –> <!ENTITY % graphic-model
"((%id.class;)?, (%access.class;)*, (%display-back-matter;)*) " >
<!– KEYWORD GROUP MODEL –> <!– Content model for a <kwd-group> element –> <!ENTITY % kwd-group-model
"(title?, (%kwd.class;)+ )" >
<!– LIST ITEM ELEMENTS –> <!– The elements that can be included inside
the content model of a <list-item> -->
<!ENTITY % list-item-model
"(%just-para.class;)+" >
<!– LIST MODEL –> <!– Content model for the <list> element –> <!ENTITY % list-model “(title?, list-item+)” >
<!– MEDIA MODEL –> <!– Content model for the <media> element –> <!ENTITY % media-model “((%id.class;)?, (%access.class;)*,
(%display-back-matter;)*) " >
<!– REFERENCE LIST MODEL –> <!– Content model for the <ref-list> element –> <!ENTITY % ref-list-model
"(title?, (%just-para.class;)*, ref+)" >
<!– REFERENCE ITEM MODEL
Model for the <ref> element -->
<!ENTITY % ref-model “(%citation.class;)+” >
<!– SUPPLEMENTARY MATERIAL MODEL –> <!– Content model for the
<supplementary-material> element -->
<!ENTITY % supplementary-material-model
"((%id.class;)*, (%caption.class;)?, (%access.class; | %address-link.class;)*, (%just-para.class;)*, %display-back-matter; )" >
<!– TABLE WRAPPER CONTENT MODEL –> <!– Content model for the container element that
surrounds the standard table models for row and columns. -->
<!ENTITY % table-wrap-model
"((%id.class;)*, (%caption.class;)?, (%access.class;)*, (%inside-table-wrap;)*, %table-foot.class;?, %display-back-matter; )" >
<!– TITLE GROUP MODEL –> <!– Content model for the <title-group> element–> <!ENTITY % title-group-model
"(article-title, subtitle?)" >
<!– TRANSLATED ABSTRACT MODEL –> <!– Content model for an <trans-abstract> element.
-->
<!ENTITY % trans-abstract-model
"(title?, (%just-para.class;)*, %sec.class;*)" >
<!– VERSE GROUP MODEL –> <!– Content model for the <verse-group> element–> <!ENTITY % verse-group-model
"(title?, subtitle?, verse-line+, %display-back-matter; ) " >
<!– ============================================================= –> <!– OVER-RIDES OF ATTRIBUTE VALUES –> <!– ============================================================= –>
<!– FOOTNOTE TYPE VALUES –> <!– Used to mark the semantics of the footnote,
what information does this footnote convey. -->
<!ENTITY % fn-types “abbr | com | con | conflict |
corresp | current-aff | deceased | edited-by | equal | financial-disclosure | on-leave | participating-researchers | presented-at | presented-by | present-address | previously-at | study-group-members | supplementary-material | supported-by | other" >
<!– LIST PREFIX TYPES –> <!– Used to request a specific style of prefix
characters for the items in lists and de-lists. Ordered is number or letters, bulleted is bullets or other non-ordered character, simple has no prefix at all. -->
<!ENTITY % list-types “bullet | order | simple” >
<!– CROSS(X)-REFERENCE TYPE VALUES –> <!– Used to say to what the reference is pointing.
May be used for type-specific processing or validation. Values are, for example: Affiliation "aff" and Figure "fig", and Bibliographic ref (to a citation. -->
<!ENTITY % ref-types “aff | app | bibr |
boxed-text | chem | contrib | corresp | disp-formula | fig | fn | kwd | list | plate | scheme | sec | statement | supplementary-material | table | table-fn | other" >
<!– ============================================================= –> <!– DUPLICATE ATTRIBUTE DECLARATIONS –> <!– (These are unchanged from the base Suite, –> <!– but are used in attribute over-rides below)–> <!– ============================================================= –>
<!– XLINK LINK ATTRIBUTES –> <!– Attributes for any element that must be a
link -->
<!ENTITY % link-atts
"xmlns:xlink CDATA #IMPLIED xlink:type (simple) #IMPLIED xlink:href CDATA #REQUIRED xlink:role CDATA #IMPLIED xlink:title CDATA #IMPLIED xlink:show (embed | new | none | other | replace) #IMPLIED xlink:actuate (none | onLoad | onRequest | other) #IMPLIED" >
<!– MIGHT LINK XLINK ATTRIBUTES –> <!– Attributes for any element that may be a link
but need not be one -->
<!ENTITY % might-link-atts
"xmlns:xlink CDATA #IMPLIED xlink:type (simple) #IMPLIED xlink:href CDATA #IMPLIED xlink:role CDATA #IMPLIED xlink:title CDATA #IMPLIED xlink:show (embed | new | none | other | replace) #IMPLIED xlink:actuate (none | onLoad | onRequest | other) #IMPLIED" >
<!– ============================================================= –> <!– OVER-RIDES OF ATTRIBUTE LISTS –> <!– ============================================================= –>
<!– FOOTNOTE ATTRIBUTES –> <!– Attribute list for Footnote element –> <!ENTITY % fn-atts
"id ID #IMPLIED fn-type (%fn-types;) #IMPLIED specific-use CDATA #IMPLIED xml:lang NMTOKEN #IMPLIED" >
<!– INLINE GRAPHIC ATTRIBUTES –> <!– Attributes for Inline Graphic
<inline-graphic> -->
<!ENTITY % inline-graphic-atts
"id ID #IMPLIED baseline-shift CDATA #IMPLIED mimetype CDATA #FIXED 'image' mime-subtype (cgm | gif | jpeg | png | tiff) #IMPLIED specific-use CDATA #IMPLIED xml:lang NMTOKEN #IMPLIED %link-atts;" >
<!– DEFAULT LIST CLASS ATTRIBUTES –> <!– Default attribute lists to be used for most
of the types of lists. Used for the <list> element and <def-list> element. -->
<!ENTITY % list-atts
"id ID #IMPLIED continued-from IDREF #IMPLIED list-type (%list-types;) #IMPLIED prefix-word CDATA #IMPLIED list-content CDATA #IMPLIED specific-use CDATA #IMPLIED xml:lang NMTOKEN #IMPLIED" >
<!– PERSON GROUP ATTRIBUTES –> <!– Attributes for the <person-group> element –> <!ENTITY % person-group-atts
"id ID #IMPLIED person-group-type (allauthors | assignee | author | compiler | director | editor | guest-editor | inventor | translator | transed) #IMPLIED specific-use CDATA #IMPLIED xml:lang NMTOKEN #IMPLIED" >
<!– SECTION ATTRIBUTES –> <!– Attributes for the <sec> element –> <!ENTITY % sec-atts
"id ID #IMPLIED sec-type CDATA #IMPLIED specific-use CDATA #IMPLIED xml:lang NMTOKEN #IMPLIED" >
<!– UNDERLINE ATTRIBUTES –> <!– Attributes for the <underline> element –> <!ENTITY % underline-atts
"specific-use CDATA #IMPLIED" >
<!– ================== End Authoring Over-ride Content/ATTLIST == –>