<!– ============================================================= –> <!– MODULE: Journal Archiving DTD Customize Content and –> <!– Attributes Module –> <!– VERSION: 3.0.0 –> <!– DATE: Apr 2009 –> <!– –> <!– ============================================================= –>
<!– ============================================================= –> <!– PUBLIC DOCUMENT TYPE DEFINITION –> <!– TYPICAL INVOCATION –> <!– “-//Atypon//DTD Atypon Systems Archival NLM DTD Customize Content and Attributes Module v3.0.0 20090430//EN” Delivered as file “atypon-archivecustom-models3.ent” –> <!– ============================================================= –>
<!– ============================================================= –> <!– SYSTEM: Journal Archiving and Interchange DTD of the –> <!– Archiving and Interchange DTD Suite –> <!– –> <!– PURPOSE: To declare the Parameter Entities (PEs) used to –> <!– over-ride content models or parts of content –> <!– models when making a new DTD from the modules of –> <!– the Archiving and Interchange 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. –> <!– –> <!– CONTAINS: 1) PEs that define OR lists of elements to be –> <!– mixed with #PCDATA in element content models –> <!– (all PEs are named “yyy-elements”, where “yyy” –> <!– is the name of the primary element whose –> <!– content model will use the declared PE.) –> <!– 2) PEs that define complete content models. –> <!– (names ending in the suffix “-model”) –> <!– 3) PEs that define attribute list or attribute –> <!– value over-rides –> <!– –> <!– CREATED FOR: –> <!– Digital archives and publishers who wish to –> <!– create a custom XML DTD for original markup of –> <!– journal literature, books, and related material, –> <!– or for archiving and transferring such material –> <!– between archives. –> <!– –> <!– 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 Archiving and –> <!– Interchange 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 Archiving and Interchange DTD Suite.” –> <!– –> <!– 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 Archiving and Interchange DTD –> <!– Suite.” –> <!– –> <!– 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" -->
<!– ============================================================= –> <!– INLINE MIXES TO OVER-RIDE CONTENT MODELS –> <!– (ELEMENTS TO BE ADDED TO #PCDATA IN MODELS)–> <!– ============================================================= –>
<!– ABBREVIATION ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of the <abbrev> element -->
<!ENTITY % abbrev-elements
"| %all-phrase; | %def.class;" >
<!– ACCESS DATE ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of the Access Date <access-date> element -->
<!ENTITY % access-date-elements
"| %date-parts.class; | %x.class;" >
<!– AFFILIATION ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of the <aff> element -->
<!ENTITY % aff-elements “| %address.class; | %all-phrase; |
%break.class; | %label.class;" >
<!– ALT TEXT ELEMENTS –> <!– Elements to be mixed with data characters
inside the <alt-text> element -->
<!ENTITY % alt-text-elements
" %just-rendition;" >
<!– ANONYMOUS ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of an <anonymous> element -->
<!ENTITY % anonymous-elements
"| %all-phrase;" >
<!– ARTICLE TITLE ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of the <article-title> element. -->
<!ENTITY % article-title-elements
"| %all-phrase; | %break.class;" >
<!– CHEMICAL STRUCTURE ELEMENTS –> <!– Those elements that may mix with the data
characters inside a Chemical Structure <chem-struct> -->
<!ENTITY % chem-struct-elements
"| %access.class; | %all-phrase; | %break.class; | %id.class; | %label.class; | %list.class; | %simple-display-noalt.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
"%article-link.class; | %appearance.class; | %citation-additions.class; | %emphasis.class; | %inline-display.class; | %inline-math.class; | %label.class; | %math.class; | %phrase.class; | %references.class; | %simple-link.class; | %subsup.class; | %x.class; | bbox" >
<!– COLLABORATIVE (GROUP) AUTHOR ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of the <collab> element. This is essentially %all-phrase; plus contrib-info and break. All-phase is not used because of duplication clashes with the -contrib-info.class; -->
<!ENTITY % collab-elements
"| %article-link.class; | %address.class; | %appearance.class; | %break.class; | %contrib-group.class; | %contrib-info.class; | %emphasis.class; | %inline-display.class; | %inline-math.class; | %math.class; | %phrase.class; | %subsup.class; | %x.class;">
<!– COMPOUND KEYWORD PART ELEMENTS –> <!– Elements to be mixed with data characters
inside the <compound-kwd-part> element -->
<!ENTITY % compound-kwd-part-elements
"| %break.class; | %all-phrase;" >
<!– CONFERENCE MODEL –> <!– Content model for the <conference> element –> <!ENTITY % conference-model
"(%conference.class; | %x.class;)*" >
<!– CONFERENCE DATE ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of the <conf-date> element -->
<!ENTITY % conf-date-elements
"| %date-parts.class; | %x.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
"| %all-phrase;" >
<!– COPYRIGHT HOLDER ELEMENTS –> <!– Elements to be mixed with data characters
inside the content model for the <copyright-holder> element. -->
<!ENTITY % copyright-holder-elements
"| %subsup.class; | %x.class;" >
<!– COPYRIGHT STATEMENT ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of the <copyright-statement> -->
<!ENTITY % copyright-statement-elements
"| %all-phrase;" >
<!– 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; | %all-phrase; | %break.class; | %label.class;" >
<!– COUNTRY ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of the country element. -->
<!ENTITY % country-elements
"| %x.class;" >
<!– DATE IN CITATION ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of the Date Inside Citation <date-in-citation> element -->
<!ENTITY % date-in-citation-elements
"| %date-parts.class; | %emphasis.class; | %x.class;" >
<!– FORMULA, DISPLAY ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of the <disp-formula> -->
<!ENTITY % disp-formula-elements
"| %all-phrase; | %access.class; | %break.class; | %display-back-matter.class; | %label.class; | %simple-display-noalt.class;" >
<!– EMAIL ADDRESS ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of the <email> element -->
<!ENTITY % email-elements
"| %all-phrase;" >
<!– ET AL ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of an <etal> element -->
<!ENTITY % etal-elements
"| %all-phrase;" >
<!– EXTERNAL LINK ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of an <ext-link> -->
<!ENTITY % ext-link-elements
"| %all-phrase;" >
<!– FUNDING STATEMENT ELEMENTS –> <!– Model for the <funding-statement> element –> <!ENTITY % funding-statement-elements
"| %all-phrase; | %funding.class;" >
<!– HISTORY ELEMENTS –> <!– Elements that may be mixed with data
characters inside the model for <history> when <history> is modeled as a mixed content element. -->
<!ENTITY % history-elements
"| %all-phrase; | %break.class; | %date.class;" >
<!– FORMULA, INLINE ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of the <inline-formula> element. -->
<!ENTITY % inline-formula-elements
"| %all-phrase;" >
<!– INLINE SUPPLEMENTARY MATERIAL ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of the <inline-supplementary-material> element-->
<!ENTITY % inline-supplementary-material-elements
"| %access.class; | %all-phrase;" >
<!– INSTITUTION NAME ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of the <institution> element -->
<!ENTITY % institution-elements
"| %all-phrase; | %break.class;" >
<!– ISBN ELEMENTS –> <!– Elements for use with data characters inside
the model for the <isbn> element -->
<!ENTITY % isbn-elements
"| %x.class;" >
<!– ISSN ELEMENTS –> <!– Elements for use with data characters inside
the model for the <issn> element -->
<!ENTITY % issn-elements
"| %x.class;" >
<!– ISSUE TITLE ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of the <issue-title> element -->
<!ENTITY % issue-title-elements
"| %all-phrase;" >
<!– KEYWORD CONTENT ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of a keyword. -->
<!ENTITY % kwd-elements
"| %all-phrase; | %break.class;" >
<!– LABEL ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of the <label> element -->
<!ENTITY % label-elements
"| %all-phrase; | %break.class;" >
<!– LINK ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of linking element such as <xref>, <target>, and <ext-link> -->
<!ENTITY % link-elements
"| %all-phrase; | %break.class;" >
<!– LONG DESCRIPTION ELEMENTS –> <!– Elements to be mixed with data characters
inside the <long-desc> element -->
<!ENTITY % long-desc-elements
"| %x.class;" >
<!– METADATA DATA NAME ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of the <meta-name> element -->
<!ENTITY % meta-name-elements
"| %all-phrase;" >
<!– METADATA DATA VALUE ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of the <meta-value> element -->
<!ENTITY % meta-value-elements
"| %all-phrase;" >
<!– NAMED CONTENT ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of the <named-content> element -->
<!ENTITY % named-content-elements
"| %all-phrase; | %block-display-noalt.class; | %block-math.class; | %list.class; | %rest-of-para.class;" >
<!– PARAGRAPH ELEMENTS –> <!– Elements that may be used within a paragraph
in a mixed content model with #PCDATA. Design Note: There is a major overlap between this parameter entity and the mix for 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 % p-elements “| %all-phrase; |
%block-display-noalt.class; | %block-math.class; | %citation.class; | %funding.class; | %list.class; | %rest-of-para.class;" >
<!– PERSON GROUP ELEMENTS –> <!– Elements to be mixed with #PCDATA characters
within the Person Group element (name class include <string-name> in this tag set.-->
<!ENTITY % person-group-elements
"%name.class; | %person-group-info.class; | %x.class;" >
<!– 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; | %all-phrase; | %display-back-matter.class; " >
<!– PRODUCT ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of the <product> element (Note: all-phrase was replicated and not used directly because the article-link.class elements are repeated in -references.class and therefore cause duplication. -->
<!ENTITY % product-elements
"| %article-link.class; | %appearance.class; | %break.class; | %emphasis.class; | %inline-display.class; | %inline-math.class; | %label.class; | %math.class; | %phrase.class; | %price.class; | %references.class; | %simple-link.class; | %subsup.class; | %x.class;" >
<!– PUBLISHER'S LOCATION ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of the <publisher-loc> element -->
<!ENTITY % publisher-loc-elements
"| %address.class; | %all-phrase; | %break.class;" >
<!– RELATED ARTICLE ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of the <related-article> element. (Note: all-phrase was replicated and not used directly because the article-link.class elements are repeated in -references.class and therefore cause duplication.) -->
<!ENTITY % related-article-elements
" | %article-link.class; | %appearance.class; | %break.class; | %emphasis.class; | %inline-display.class; | %inline-math.class; | %journal-id.class; | %label.class; | %math.class; | %phrase.class; | %references.class; | %simple-link.class; | %subsup.class; | %x.class;" >
<!– RELATED OBJECT ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of the <related-object> element. (Note: all-phrase was replicated and not used directly because the article-link.class elements are repeated in -references.class and therefore cause duplication.) -->
<!ENTITY % related-object-elements
"| %article-link.class; | %appearance.class; | %break.class; | %emphasis.class; | %inline-display.class; | %inline-math.class; | %label.class; | %math.class; | %phrase.class; | %references.class; | %simple-link.class; | %subsup.class; | %x.class;" >
<!– 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
"| %all-phrase;" >
<!– TEXTUAL FORM ELEMENTS –> <!– Model for the <textual-form> element.
Added <label> -->
<!ENTITY % textual-form-elements
"%emphasis.class; | %inline-display-noalt.class; | %label.class; | %math.class; | %phrase-content.class; | %subsup.class;" >
<!– SELF-URI ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of the <self-uri> element -->
<!ENTITY % self-uri-elements
"| %all-phrase;" >
<!– SIGNATURE BLOCK ELEMENTS –> <!– Elements to be mixed with data characters
inside the content model for the <sig-block> element. -->
<!ENTITY % sig-block-elements
"| %all-phrase; | %break.class; | %contrib.class; | %just-base-display-noalt.class; | %person-group-info.class; | %sig.class;" >
<!– SIGNATURE ELEMENTS –> <!– Elements to be mixed with data characters
inside the content model for the <sig> element. -->
<!ENTITY % sig-elements “| %all-phrase; | %break.class; |
%just-base-display-noalt.class;" >
<!– SIZE ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of the size element. -->
<!ENTITY % size-elements
"| %x.class;" >
<!– SOURCE ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of the <source> element -->
<!ENTITY % source-elements
"| %all-phrase; | %break.class;" >
<!– SPEAKER ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of a speaker. -->
<!ENTITY % speaker-elements
"| %all-phrase; | %person-name.class;" >
<!– STRING DATE ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of the <string-date> element -->
<!ENTITY % string-date-elements
"| %all-phrase; | %date-parts.class;" >
<!– STRING NAME ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of the <string-name> element -->
<!ENTITY % string-name-elements
"| %all-phrase; | %person-name.class;" >
<!– STRUCTURAL TITLE ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of the <title> element -->
<!ENTITY % struct-title-elements
"| %all-phrase; | %break.class; | %citation.class;" >
<!– STYLED CONTENT ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of the <styled-content> element -->
<!ENTITY % styled-content-elements
"| %all-phrase; | %block-display-noalt.class;| %block-math.class; | %list.class; | %rest-of-para.class;" >
<!– SUBJECT GROUPING NAME ELEMENTS –> <!– Elements that may be used, along with data
characters inside the content model of the <subject> element -->
<!ENTITY % subject-elements
"| %all-phrase; | %break.class;" >
<!– DEFINITION LIST: TERM ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of a <term>. -->
<!ENTITY % term-elements
"| %all-phrase; | %block-math.class; | %chem-struct-wrap.class; | %simple-display-noalt.class;" >
<!– TIME STAMP ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of a <time-stamp>. -->
<!ENTITY % time-stamp-elements
"| %x.class; " >
<!– TITLE ELEMENTS –> <!– The elements that can be included along with
data characters inside the content model of title elements such as <title>, <subtitle>, <trans-title>, etc. -->
<!ENTITY % title-elements
"| %all-phrase; | %break.class;" >
<!– X ELEMENTS –> <!– Elements for use inside the <x> element –> <!ENTITY % x-elements “| %emphasis.class; | %phrase-content.class; |
%subsup.class; | %x.class;" >
<!– ============================================================= –> <!– DUPLICATES NEEDED FOR OVER-RIDES –> <!– (models unchanged from common.ent but –> <!– needed below) –> <!– ============================================================= –>
<!– MIGHT LINK XLINK ATTRIBUTES –> <!– Used for elements which may need to link to
external sources or other objects within the document, but may not necessarily act as a link at all. The attribute "xlink:href" identifies the object to which the link points. -->
<!ENTITY % might-link-atts
"xmlns:xlink CDATA #FIXED 'http://www.w3.org/1999/xlink' xlink:type (simple) #FIXED 'simple' 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" >
<!– 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
"(sec-meta?, label?, title?, (%para-level;)*, (%sec-level;)*, (%sec-back-matter-mix;)* )" >
<!– ============================================================= –> <!– OVER-RIDES OF CONTENT MODELS (FULL MODELS) –> <!– ============================================================= –>
<!– ALTERNATE TITLE TEXT FOR A FIGURE, ETC. –> <!– Short phrase used to display or pronounce
as an alternative to providing the full graphic for accessibility display or graphic-limited websites or devices. -->
<!ENTITY % alt-text-model “(#PCDATA %alt-text-elements;)*” >
<!– ARTICLE METADATA MODEL –> <!– Content model for the metadata that is
specific to the article. -->
<!ENTITY % article-meta-model
"(article-id*, article-categories?, title-group?, (contrib-group | aff | %x.class;)*, author-notes?, pub-date*, volume?, volume-id*, volume-series?, issue?, issue-id*, issue-sequence?, issue-title*, issue-sponsor*, issue-part?, isbn*, supplement?, ( ( (fpage, lpage?)?, page-range?) | elocation-id )?, (%address-link.class; | product | supplementary-material)*, history?, permissions?, self-uri*, related-article*, abstract*, trans-abstract*, kwd-group*, accreditation?, funding-group*, conference*, counts?, custom-meta-group?)" >
<!– ADDRESS MODEL –> <!– Content model for the <address> element –> <!ENTITY % address-model
"(%address.class; | %address-link.class; | %label.class; | %x.class;)*" >
<!– APPENDIX MODEL –> <!– Content model for the <app> element. The
section model already contains parentheses. Made initial <title> optional. -->
<!ENTITY % app-model “(%sec-opt-title-model;, permissions?)” >
<!– AUTHOR NOTES MODEL –> <!– Content model for an <author-notes> element.
-->
<!ENTITY % author-notes-model
"(label?, title?, (%corresp.class; | %fn-link.class; | %just-para.class; | %x.class;)+ )" >
<!– CONTRIBUTOR GROUP MODEL –> <!– Content model for the <title-group> element–> <!ENTITY % contrib-group-model
"(%contrib.class; | %contrib-info.class; | %x.class;)+" >
<!– CONTRIBUTOR MODEL –> <!– Content model for the <contrib> element –> <!ENTITY % contrib-model
"( (%name.class; | %degree.class; | %contrib-info.class; | %x.class;)* )" >
<!– DEFINITION LIST: DEFINITION ITEM MODEL –> <!– Content model of a <def-item> –> <!ENTITY % def-item-model
"(label?, term*, (%def.class; | %x.class;)* )" >
<!– DEFINITION LIST MODEL –> <!– Content model for the <def-list> element –> <!ENTITY % def-list-model
"(label?, title?, term-head?, def-head?, (def-item | %x.class;)*, def-list* )" >
<!– FOOTNOTE GROUP MODEL –> <!– Content model for the <fn-group> element
Added an <x> as alternative to <fn>. -->
<!ENTITY % fn-group-model
"(label?, title?, (%fn-link.class; | %x.class;)+ )" >
<!– HISTORY MODEL –> <!– Content model for the <history> element –> <!ENTITY % history-model
"(#PCDATA %history-elements;)*" >
<!– KEYWORD GROUP MODEL –> <!– Content model for a <kwd-group> element –> <!ENTITY % kwd-group-model
"(label?, title?, ((%kwd.class; | %x.class;)+ | unstructured-kwd-group ) )" >
<!– LIST MODEL –> <!– Content model for the <list> element –> <!ENTITY % list-model “(label?, title?,
(list-item | %x.class;)+ )" >
<!– PERSON GROUP MODEL –> <!– Content model for the Person Group element –> <!ENTITY % person-group-model
"(#PCDATA | %person-group-elements;)*" >
<!– PUBLICATION DATE MODEL –> <!– Content model for the element <pub-date> –> <!ENTITY % pub-date-model
"(day | month | year | season | string-date | x)*" >
<!– REFERENCE ITEM MODEL –> <!– Content model for the <ref> element –> <!ENTITY % ref-model “(label?, (%citation.class; | %note.class; |
%x.class;)+ )" >
<!– REFERENCE LIST MODEL –> <!– Content model for the <ref-list> element –> <!ENTITY % ref-list-model
"(label?, title?, (%para-level; | ref)*, (%ref-list.class;)* )" >
<!– CONTENT MODEL FOR A STRUCTURAL SECTION –> <!– The model for a Section <sec> –> <!ENTITY % sec-model “(sec-meta?, label?, title?,
(%para-level;)*, (%sec-level;)*, (%sec-back-matter-mix;)* )" >
<!– TABLE WRAP FOOTER MODEL –> <!– Content model for the <table-wrap-foot>
element -->
<!ENTITY % table-wrap-foot-model
"(label?, title?, (%just-para.class; | %fn-group.class; | %fn-link.class; | %display-back-matter.class; | %x.class;)+ )" >
<!– ============================================================= –> <!– OVER-RIDES OF ATTRIBUTE LISTS –> <!– ============================================================= –>
<!– ARTICLE IDENTIFIER ATTRIBUTES –> <!– Attributes for the <article-id> element –> <!ENTITY % article-id-atts
"pub-id-type CDATA #IMPLIED" >
<!– AWARD IDENTIFIER ATTRIBUTES –> <!– Attributes for the <award-group> element –> <!ENTITY % award-id-atts
"id ID #IMPLIED rid IDREFS #IMPLIED award-type CDATA #IMPLIED %might-link-atts;" >
<!– FUNDING STATEMENT ATTRIBUTES –> <!– Attributes for the <funding-source> element–> <!ENTITY % funding-statement-atts
"id ID #IMPLIED rid IDREFS #IMPLIED %might-link-atts;" >
<!– DATE (HISTORICAL) ATTRIBUTES –> <!ENTITY % date-atts
"date-type CDATA #IMPLIED" >
<!– NAME ATTRIBUTES –> <!– Attribute list for the <name> element –> <!ENTITY % name-atts
"content-type CDATA #IMPLIED name-style (western | eastern | islensk) 'western' xml:lang NMTOKEN #IMPLIED" >
<!– PUBLICATION IDENTIFIER ATTRIBUTES –> <!– Attributes for the <pub-id> element –> <!ENTITY % pub-id-atts
"pub-id-type CDATA #IMPLIED" >
<!– TRANSLATED TITLE GROUP ATTRIBUTES –> <!– Attribute list for the <trans-title-group>
Made xml:lang optional. -->
<!ENTITY % trans-title-group-atts
"id ID #IMPLIED content-type CDATA #IMPLIED xml:lang NMTOKEN #IMPLIED" >
<!– X(CROSS) REFERENCE ATTRIBUTES –> <!– Attribute list for cross references –> <!ENTITY % xref-atts
"id ID #IMPLIED ref-type CDATA #IMPLIED rid IDREFS #IMPLIED" >
<!– SUBJECT ATTRIBUTES –> <!– Attributes for the <subject> element –> <!ENTITY % subject-atts
"content-type CDATA #IMPLIED code CDATA #IMPLIED" >
<!– ================== End Archiving Content/ATT Over-rides ===== –>