<!-- ============================================================= -->
<!-- MODULE: Journal Publishing DTD -->
<!-- VERSION: 3.0 -->
<!-- DATE: Feb 2008 -->
<!-- -->
<!-- ============================================================= -->
<!-- ============================================================= -->
<!-- PUBLIC DOCUMENT TYPE DEFINITION -->
<!-- TYPICAL INVOCATION -->
<!--
"-//NLM//DTD Journal Publishing DTD v3.0 20080202//EN"
Delivered as file "journalpublishing3.dtd" -->
<!-- ============================================================= -->
<!-- ============================================================= -->
<!-- SYSTEM: Journal Publishing DTD of the -->
<!-- Archiving and Interchange DTD Suite -->
<!-- -->
<!-- PURPOSE: DTD for creation of new journal articles -->
<!-- -->
<!-- This subset of the Journal Archiving and -->
<!-- Interchange DTD is optimized for the authoring -->
<!-- (or initial XML tagging) of journal articles and -->
<!-- some non-article material such as product and -->
<!-- book reviews. It describes both the metadata for -->
<!-- a journal article and the full content of the -->
<!-- article. -->
<!-- This DTD was constructed using the modules in the -->
<!-- Archiving and Interchange DTD Suite. -->
<!-- -->
<!-- CONTAINS: 1) Declare and invoke the Publishing (Blue) DTD- -->
<!-- specific module of modules, that names any -->
<!-- modules created expressly for this DTD. -->
<!-- (%journalpubcustom-modules.ent;) -->
<!-- 2) Declare and invoke the DTD Suite module of -->
<!-- modules (%modules.ent;), the Archiving and -->
<!-- Interchange Suite module that names all the -->
<!-- Suite modules this DTD might invoke -->
<!-- 3) Invoke DTD-specific classes over-ride module -->
<!-- (%journalpub-classes.ent;) -->
<!-- 4) Invoke Suite default classes -->
<!-- (%default-classes.ent;) -->
<!-- 5) Invoke DTD-specific mixes over-ride module -->
<!-- (%journalpubcustom-mixes.ent;) -->
<!-- 6) Invoke Suite default mixes -->
<!-- (%default-mixes.ent;) -->
<!-- 7) Invoke DTD-specific content model over-ride -->
<!-- module (%journalpubcustom-models.ent;) -->
<!-- 8) Invoke the Common Element Module (from Suite) -->
<!-- 9) Invoke all the Class Modules (from Suite) as -->
<!-- well as any DTD-specific element modules -->
<!-- 10) Parameter Entities for attribute values used -->
<!-- in this module (DTD-specific definitions) -->
<!-- 11) Define document element (Article <article>) -->
<!-- 12) Define Front Matter <front> -->
<!-- 13) Define Body Matter <body> -->
<!-- 14) Define Back Matter <back> -->
<!-- -->
<!-- TAG SET SPONSOR -->
<!-- Digital Archive of Journal Articles -->
<!-- National Center for Biotechnology Information -->
<!-- (NCBI) -->
<!-- National Library of Medicine (NLM) -->
<!-- -->
<!-- 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: -->
<!-- February 2003 -->
<!-- -->
<!-- CREATED BY: Jeff Beck (NCBI) -->
<!-- B. Tommie Usdin (Mulberry Technologies, Inc.) -->
<!-- -->
<!-- The Journal Publishing DTD is built from the -->
<!-- Archiving and Interchange DTD Suite. -->
<!-- -->
<!-- Suggestions for refinements and enhancements to -->
<!-- this DTD should be sent in email to: -->
<!-- publishing-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.
2. Changed default @xml:lang from "EN" from "en" to match latest
RFC 4646/W3C/IANA Subtag Registry recommendations
1. Updated public identifier to "v3.0 20080202//EN" -->
<!-- ============================================================= -->
<!-- DESIGN CONSIDERATIONS -->
<!-- ============================================================= -->
<!-- MODULAR DTD LIBRARY
A set of journal archiving and interchange
DTD modules was written as the basis for
publishing, interchange, and repository
DTDs, with the intention that DTDs for
specific purposes, such as this Publishing
DTD, would be developed based on them.
This publishing DTD has been optimized for
the creation of new journal articles. This
means that it is far smaller (fewer elements,
and fewer choices in many contexts) than was
the interchange DTD. Where in the interchange
DTD there may have been several ways to
express the same information, only one is
provided for authoring. It was not the
intention to limit the expressive power
licensed by the DTD, but rather to limit the
meaningless choices needed in a full
archiving and interchange DTD that make
conversion from a wide variety of formats as
easy as possible.
This Publishing DTD has been developed from
the Archiving and Interchange DTD Suite
modules, in the approved manner, making
changes to the declarations in those modules
by overriding Parameter Entity defined in
the over-rise (customization) modules:
%journalpubcustom-classes.ent;
%journalpubcustom-mixes.ent;
%journalpubcustom-models.ent;
which are all declared in the module:
%journalpubcustom-modules.ent;
Additional Publishing-DTD-Specific material
is defined in the module(s):
%nlmcitation.ent;
No changes to any of the original Archiving
and Interchange Suite modules are required
in order to use this DTD. -->
<!-- ============================================================= -->
<!-- MODULES OF MODULES INVOKED -->
<!-- ============================================================= -->
<!-- MODULE TO NAME DTD-SPECIFIC MODULES -->
<!-- Names all DTD-specific external modules -->
<!ENTITY % journalpubcustom-modules.ent
PUBLIC
"-//NLM//DTD Journal Publishing DTD-Specific Modules v3.0 20080202//EN"
"journalpubcustom-modules3.ent" >
%journalpubcustom-modules.ent;
<!-- MODULE TO NAME THE MODULES -->
<!-- Declares all the external modules that are
part of the modular Journal Archiving and
Interchange DTD Suite library. Thus it does
NOT declare itself; the DTD-specific
module-of-modules; or the DTD-specific class,
mix, or model over-ride modules. Those are
declared in the DTD-specific module of modules.
Since this module declares but does not
invoke modules, this DTD invokes any modules
it uses by referencing the external
Parameter Entities defined in the Module of
Modules. To include a set of elements (such
as all the lists or the MathML elements) this
module defines the external Parameter Entity
for the module(s) that contains the MathML
declarations and the DTD references that
entity. -->
<!ENTITY % modules.ent PUBLIC
"-//NLM//DTD Archiving and Interchange DTD Suite Module of Modules v3.0 20080202//EN"
"modules3.ent" >
%modules.ent;
<!-- ============================================================= -->
<!-- CUSTOMIZATION MODULES INVOKED -->
<!-- Note: These modules must be called after -->
<!-- all Module of Modules but before any other -->
<!-- modules. Unlike any other grouping, order -->
<!-- of these modules matters. -->
<!-- ============================================================= -->
<!-- DTD-SPECIFIC CLASS CUSTOMIZATIONS MODULE -->
<!-- Names the module that holds the DTD-specific
class definitions for the Journal Publishing
DTD that will over-ride classes in the Suite.
(Defined in %journalpubcustom-modules.ent;)-->
%journalpubcustom-classes.ent;
<!-- DEFAULT ELEMENT CLASSES MODULE -->
<!-- Names the module that holds the standard
class definitions for the Journal Archiving
and Interchange DTD Suite. -->
%default-classes.ent;
<!-- DTD-SPECIFIC MIX CUSTOMIZATIONS MODULE -->
<!-- Set up the Parameter Entities and element
class definitions that will be used to
over-ride some element mixes in this DTD.
(Defined in %journalpubcustom-modules.ent;)-->
%journalpubcustom-mixes.ent;
<!-- DEFAULT MIX CUSTOMIZATIONS MODULE -->
<!-- Names the module that holds the standard
mix definitions for the Journal Archiving
and Interchange DTD Suite. -->
%default-mixes.ent;
<!-- DTD-SPECIFIC MODELS/ATTRIBUTES CUSTOMIZATIONS
MODULE -->
<!-- Names the module that holds the over-rides
of content models, attribute lists, elements
lists to be used in content models, and
attribute values. These are DTD-specific.
(Defined in %journalpubcustom-modules.ent;)-->
%journalpubcustom-models.ent;
<!-- ============================================================= -->
<!-- COMMON (SHARED) ELEMENTS MODULE INVOKED -->
<!-- ============================================================= -->
<!-- COMMON (SHARED) DECLARATIONS -->
<!-- Declarations for elements, attributes,
entities, and Notations that are shared by
more than one class module. Note: Must be
called before any of the class modules. -->
%common.ent;
<!-- ============================================================= -->
<!-- JOURNAL ARTICLE CLASS ELEMENTS (alpha) -->
<!-- ============================================================= -->
<!-- ARTICLE METADATA ELEMENTS -->
%articlemeta.ent;
<!-- BACK MATTER ELEMENTS -->
%backmatter.ent;
<!-- DISPLAY (GRAPHICAL) ELEMENTS -->
%display.ent;
<!-- FORMATTING ELEMENT CLASSES -->
<!-- Elements that change rendition/display. -->
%format.ent;
<!-- FUNDING ELEMENTS -->
<!-- Elements that describe the sponsorship or
open access -->
%funding.ent;
<!-- JOURNAL METADATA ELEMENTS -->
%journalmeta.ent;
<!-- LINK CLASS ELEMENTS -->
%link.ent;
<!-- LIST CLASS ELEMENTS -->
%list.ent;
<!-- MATH ELEMENTS -->
%math.ent;
<!-- NLM CITATION ELEMENT -->
%nlmcitation.ent;
<!-- PARAGRAPH-LEVEL ELEMENTS -->
%para.ent;
<!-- PHRASE-LEVEL ELEMENTS -->
%phrase.ent;
<!-- BIBLIOGRAPHIC REFERENCE (CITATION)
CLASS ELEMENTS -->
%references.ent;
<!-- RELATED OBJECT ELEMENT -->
<!-- Defines the <related-object> element to
describe a related object such as a
related book or a dataset. -->
%related-object.ent;
<!-- SECTION ELEMENTS -->
%section.ent;
<!-- ============================================================= -->
<!-- THE REST OF THE EXTERNAL MODULES INVOKED -->
<!-- ============================================================= -->
<!-- MATHML SETUP MODULE -->
<!-- Invoke the MathML modules -->
%mathmlsetup.ent;
<!-- XHTML TABLE SETUP MODULE -->
<!-- Set up the necessary Parameter Entity values
and then invoke XHTML (HTML 4.0) table
module -->
%XHTMLtablesetup.ent;
<!-- SPECIAL CHARACTERS DECLARATIONS -->
<!-- Standard XML special character entities
used in this DTD -->
%xmlspecchars.ent;
<!-- CUSTOM SPECIAL CHARACTERS DECLARATIONS -->
<!-- Custom special character entities created
specifically for use in this DTD Suite -->
%chars.ent;
<!-- Special chars for AAS -->
%aas.ent;
<!-- NOTATION DECLARATIONS MODULE -->
%notat.ent;
<!-- ============================================================= -->
<!-- PARAMETER ENTITIES FOR ATTRIBUTE LISTS -->
<!-- ============================================================= -->
<!-- DTD VERSION -->
<!-- What version of this DTD was used to make
the document instance under consideration.
Note that this is a fixed value that should
change every time the DTD changes versions or
revisions. -->
<!ENTITY % dtd-version
"dtd-version
CDATA #FIXED '3.0'" >
<!-- ARTICLE ATTRIBUTES -->
<!-- Attributes for the top-level element
<article> -->
<!ENTITY % article-atts
"article-type
CDATA #IMPLIED
%dtd-version;
xml:lang NMTOKEN 'en'
%XLINK.xmlns.attrib;
%MATHML.xmlns.attrib;
%Schema.xmlns.attrib;" >
<!-- SUB-ARTICLE ATTRIBUTES -->
<!-- Attributes for the <sub-article> element -->
<!ENTITY % sub-article-atts
"article-type
CDATA #IMPLIED
id ID #IMPLIED
xml:lang NMTOKEN 'en'" >
<!-- RESPONSE ATTRIBUTES -->
<!-- Attributes for the <response> element -->
<!ENTITY % response-atts
"response-type
CDATA #IMPLIED
id ID #IMPLIED
xml:lang NMTOKEN 'en'" >
<!-- ============================================================= -->
<!-- JOURNAL ARTICLE ELEMENTS -->
<!-- ============================================================= -->
<!-- ARTICLE MODEL (LIMITED) -->
<!-- Article-like model used for, for example,
a short sub-article such as a news brief that
is contained in side a journal article.
-->
<!ENTITY % article-short-model
"((front | front-stub), body?, back?,
floats-group?)" >
<!-- ARTICLE MODEL WITH SUBARTICLE OR RESPONSE -->
<!-- Typical journal article model, which may
contain extended components, such as
sub-articles or responses, but which usually
contains neither.
-->
<!ENTITY % article-full-model
"(front, body?, back?, floats-group?,
(sub-article* | response*) )" >
<!-- ARTICLE -->
<!-- The complete content of a journal article.
Details at:
http://dtd.nlm.nih.gov/publishing/tag-library/3.0/index.html?elem=article
-->
<!ELEMENT article %article-full-model; >
<!ATTLIST article
%article-atts; >
<!-- ============================================================= -->
<!-- FRONT MATTER ELEMENTS -->
<!-- ============================================================= -->
<!-- FRONT MATTER MODEL -->
<!-- Model for the <front> matter (the header
metadata) of a journal article) -->
<!ENTITY % front-model "(journal-meta, article-meta,
(%front-back.class;)? )" >
<!-- FRONT MATTER -->
<!-- The metadata concerning an article, such as
the name and issue of the journal in which it
appears and the name and author(s) of the
article.
Details at:
http://dtd.nlm.nih.gov/publishing/tag-library/3.0/index.html?elem=front
-->
<!ELEMENT front %front-model; >
<!-- ============================================================= -->
<!-- BODY ELEMENTS -->
<!-- ============================================================= -->
<!-- BODY MODEL -->
<!-- Content model for the Body (main textual
content) of a journal article. -->
<!ENTITY % body-model "((%para-level;)*, (%sec-level;)*,
sig-block?)" >
<!-- BODY OF THE ARTICLE -->
<!-- The main textual portion of the article that
conveys the content.
Details at:
http://dtd.nlm.nih.gov/publishing/tag-library/3.0/index.html?elem=body
-->
<!ELEMENT body %body-model; >
<!-- ============================================================= -->
<!-- BACK MATTER ELEMENTS -->
<!-- ============================================================= -->
<!-- BACK MATTER MODEL -->
<!-- Content model for the Back Matter (ancillary
material such as appendices) of a journal
article. -->
<!ENTITY % back-model "(label?, title*, (%doc-back-matter-mix;)* )">
<!-- BACK MATTER -->
<!-- Ancillary or supporting material not included
as part of the main textual content of a
journal article, for example appendices and
acknowledgments.
Details at:
http://dtd.nlm.nih.gov/publishing/tag-library/3.0/index.html?elem=back
-->
<!ELEMENT back %back-model; >
<!-- ============================================================= -->
<!-- SUBARTICLE -->
<!-- ============================================================= -->
<!-- SUBARTICLE MODEL -->
<!-- Content model for the <sub-article> element
-->
<!ENTITY % sub-article-model
"((front | front-stub), body?, back?,
floats-group?,
(sub-article* | response*) )" >
<!-- SUBARTICLE -->
<!-- An article that is completely contained
inside another article. Both the article and
the sub-article have their own metadata.
Details at:
http://dtd.nlm.nih.gov/publishing/tag-library/3.0/index.html?elem=sub-article
-->
<!ELEMENT sub-article %sub-article-model; >
<!ATTLIST sub-article
%sub-article-atts; >
<!-- FRONT MODEL STUB -->
<!-- Content model for the <front-stub> element,
a reduced metadata set for use in
sub-articles and responses -->
<!ENTITY % front-stub-model
"(article-id*, article-categories?,
title-group?, (contrib-group | aff)*,
author-notes?, pub-date*,
volume?, volume-id*, volume-series?,
issue?, issue-id*, 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*,
funding-group*, conference*, counts?,
custom-meta-group?)" >
<!-- STUB FRONT METADATA -->
<!-- A reduced metadata set for use in
sub-articles and responses, which will
inherit metadata not defined in the stub
from the enclosing article
Details at:
http://dtd.nlm.nih.gov/publishing/tag-library/3.0/index.html?elem=front-stub
-->
<!ELEMENT front-stub %front-stub-model; >
<!-- ============================================================= -->
<!-- RESPONSE ELEMENTS -->
<!-- ============================================================= -->
<!-- RESPONSE -->
<!-- Reply, response, or commentary concerning the
journal article. In the typical case, the
response is included in the same XML package
as the original article, and thus attached
at the end of the article proper.
Details at:
http://dtd.nlm.nih.gov/publishing/tag-library/3.0/index.html?elem=response
-->
<!ELEMENT response %article-short-model; >
<!ATTLIST response
%response-atts; >
<!-- ================== End Journal Publishing DTD =============== -->
Romain Loth