<!– ============================================================= –> <!– MODULE: Paragraph-Like Elements –> <!– VERSION: 1.0 –> <!– DATE: December 2002 –> <!– –> <!– ============================================================= –>

<!– ============================================================= –> <!– PUBLIC DOCUMENT TYPE DEFINITION –> <!– TYPICAL INVOCATION –> <!– “-//NLM//DTD Archiving and Interchange DTD Suite Paragraph-Like Elements v1.0 20021201//EN”

Delivered as file "para.ent"                                  -->

<!– ============================================================= –>

<!– ============================================================= –> <!– SYSTEM: Archiving and Interchange DTD Suite –> <!– –> <!– PURPOSE: Names structural elements that will appear in –> <!– the same places as a paragraph –> <!– –> <!– CONTAINS: 1) Default definition of the paragraph class –> <!– 2) Paragraph <p> –> <!– 3) Displayed Quote <disp-quote> –> <!– –> <!– 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.” –> <!– –> <!– Suggestions for refinements and enhancements to –> <!– the DTD suite should be sent in email to: –> <!– archive-dtd@ncbi.nlm.nih.gov –> <!– –> <!– ORIGINAL CREATION DATE: –> <!– December 2002 –> <!– –> <!– CREATED BY: Jeff Beck (NCBI) –> <!– Deborah Lapeyre (Mulberry Technologies, Inc.) –> <!– Bruce Rosenblum (Inera Inc.) –> <!– –> <!– 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 –> <!– Bruce Rosenblum's collaboration with other DTD –> <!– authors in completing Version 1.0. The Andrew W. –> <!– Mellon Foundation provided support for these –> <!– important contributions. –> <!– –> <!– ============================================================= –>

<!– ============================================================= –> <!– DTD VERSIONCHANGE HISTORY –> <!– ============================================================= –> <!–

=============================================================
Version  Reason/Occasion              (who) vx.x (yyyy-mm-dd)
=============================================================
Version 1.0 Changes Before Public Release
                                  (Lapeyre) V1.0 (2002-12-25)
  1. DIALOG/SPEECH - Element <dialog> renamed <speech>

    -->

<!– ============================================================= –> <!– PARAMETER ENTITY DEPENDENCIES

Requires the following parameter entities
be defined before calling this module, 
usually accomplished in the Customization
Module for the specific DTD:
  %emphasized.text;
  %inside-para;
  %para-level;
  %person-name.class;
  %simple-link.class;
  %simple-text;                              
                                           -->

<!– ============================================================= –>

<!– ============================================================= –> <!– DEFAULT DEFINITION OF PARAGRAPH CLASSES –> <!– ============================================================= –>

<!– REST OF PARAGRAPH CLASS (MINUS PARAGRAPH) –> <!– Full paragraph class, minus the paragraph

element itself, so this PE can be used inside
the content model of a paragraph           -->

<!ENTITY % rest-of-para.class

"ack | speech | disp-quote | statement | 
 verse-group"                                >

<!– PARAGRAPH CLASS –> <!– Information for the reader that is at the

same structural level as a Paragraph
Note: While most DTDs limit <ack> to inside
Back Matter, the Wiley journal article DTD 
allows <ack> at either a paragraph or a 
section level, so it was added here.       -->

<!ENTITY % para.class “p | %rest-of-para.class;” >

<!– IN TABLE PARAGRAPH CLASS –> <!– The simpler of the paragraph-level elements

that might be found inside a table cell    -->

<!ENTITY % intable-para.class

"speech | disp-quote | statement | 
 verse-group"                                >

<!– ============================================================= –> <!– PARAGRAPH-LEVEL ELEMENTS –> <!– ============================================================= –>

<!– PARAGRAPH –> <!ELEMENT p (#PCDATA | %inside-para;)* > <!– xml:lang The language in which the value of the

element is expressed.  Recommended best 
practice is to use values as defined in
RFC 1766, typically 2-letter language
codes such as "FR" (French), "EN" (English),
and "DE" (German). These values are NOT
case sensitive, so "EN" = "en". The values
may include hyphenated differentiators such 
as "EN-AU" (Australian English) and "EN-US"
(United States English).                   -->

<!ATTLIST p

xml:lang   NMTOKEN                            #IMPLIED  >

<!– SPEECH –> <!– One exchange in a real or imaginary

conversation between two or more entities, 
for example, between a an interviewer and the 
person being interviewed, between a nurse or 
doctor and a patient, between a person and a 
computer, etc.
Authoring and Conversion Note: Speechs are
modeled as a full paragraph, even if what is
spoken is only a few words.                
Design Note: Speeches are not gathered into
a larger structure, because there is no
consistency in how this is done in existing
journal DTDs, nor any real need for a
full wrapper.                              -->

<!ELEMENT speech (speaker, p+) > <!– xml:lang The language in which the value of the

element is expressed.  Recommended best 
practice is to use values as defined in
RFC 1766, typically 2-letter language
codes such as "FR" (French), "EN" (English),
and "DE" (German). These values are NOT
case sensitive, so "EN" = "en". The values
may include hyphenated differentiators such 
as "EN-AU" (Australian English) and "EN-US"
(United States English).                   -->

<!ATTLIST speech

xml:lang   NMTOKEN                            #IMPLIED  >

<!– SPEAKER ELEMENTS –> <!– The elements that can be included along with

data characters inside the content model of
a speaker.                                 -->

<!ENTITY % speaker-elements

"| %person-name.class; | %simple-link.class;">

<!– SPEAKER –> <!– One who utters a speech as part of a

speech, for example the computer "HAL" in
the exchange 'Hal: "Hi Dave"'.             -->

<!ELEMENT speaker (#PCDATA %speaker-elements;)* >

<!– QUOTE, DISPLAYED MODEL –> <!– Content model for the Display Quote element–> <!ENTITY % disp-quote-model

"title?, (%para-level;)*, attrib?"           >

<!– QUOTE, DISPLAYED –> <!– Extract or extended quoted passage from

another work, usually made typographically 
distinct from the surrounding text.
Authoring and Conversion Note: Use this 
element for epigraphs as well as block
quotes and extracts within the text.       -->

<!ELEMENT disp-quote (%disp-quote-model;) > <!– xml:lang The language in which the value of the

element is expressed.  Recommended best 
practice is to use values as defined in
RFC 1766, typically 2-letter language
codes such as "FR" (French), "EN" (English),
and "DE" (German). These values are NOT
case sensitive, so "EN" = "en". The values
may include hyphenated differentiators such 
as "EN-AU" (Australian English) and "EN-US"
(United States English).                   -->

<!ATTLIST disp-quote

xml:lang   NMTOKEN                            #IMPLIED  >

<!– ATTRIBUTION ELEMENTS –> <!– The elements that can be included along with

data characters inside the content model of
an attribution                             -->

<!ENTITY % attrib-elements

"| %emphasized-text;"                        >

<!– ATTRIBUTION –> <!– Source, author, formal thanks, copyright

material, or other information concerning 
the origins of an extract, a poem 
<verse-group> or similar element.
Formatting Note: Typically displayed on 
a separate line (or lines, following the 
material it concerns, inheriting that
material's margins.                        -->

<!ELEMENT attrib (#PCDATA %attrib-elements;)* >

<!– STATEMENT, FORMAL MODEL –> <!– Content model for the <statement> element –> <!ENTITY % statement-model

"label?, title?, p+"                         >

<!– STATEMENT, FORMAL –> <!– A Theorem, Lemma, Proof, Postulate,

Hypothesis, Proposition, Corollary, or
other formal statement, identified as such
with a label, usually made typographically 
distinct from the surrounding text         -->

<!ELEMENT statement (%statement-model;) > <!– id Unique identifier so that the statement can

be referenced by a <xref> element          -->

<!ATTLIST statement

id         ID                                 #IMPLIED  >

<!– VERSE FORM FOR POETRY –> <!– A song, poem, or verse.

Implementer's Note: No attempt has been made
to retain the look or visual form of the
original.
Remarks: Many physics journals include both
initial epigraphs to articles and short
articles that contain nothing but a topical,
humorous, or elegiac poem.
Related Elements: Poetry may also be tagged 
with the <preformat> if spacing is critical, 
but usually poetry should be tagged with the
<verse-group> element, which may not preserve
the exact indentation but is likely to be
displayed in a proportional font.          -->

<!ELEMENT verse-group ((verse-line | verse-group)+, attrib?) > <!– xml:lang The language in which the value of the

element is expressed.  Recommended best 
practice is to use values as defined in
RFC 1766, typically 2-letter language
codes such as "FR" (French), "EN" (English),
and "DE" (German). These values are NOT
case sensitive, so "EN" = "en". The values
may include hyphenated differentiators such 
as "EN-AU" (Australian English) and "EN-US"
(United States English).                   -->

<!ATTLIST verse-group

xml:lang   NMTOKEN                            #IMPLIED  >

<!– LINE OF A VERSE –> <!– One line of a poem or verse –> <!ELEMENT verse-line (#PCDATA | %simple-text;)* >

<!– ================== End Paragraph Class Module =============== –>