forked from plazi/TaxPub
-
Notifications
You must be signed in to change notification settings - Fork 0
/
default-mixes3.ent
292 lines (248 loc) · 16.1 KB
/
default-mixes3.ent
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
<!-- ============================================================= -->
<!-- MODULE: Default Element Mixes Module -->
<!-- VERSION: 3.0 -->
<!-- DATE: Feb 2008 -->
<!-- -->
<!-- ============================================================= -->
<!-- ============================================================= -->
<!-- PUBLIC DOCUMENT TYPE DEFINITION -->
<!-- TYPICAL INVOCATION -->
<!--
"-//NLM//DTD Default Element Mixes Module v3.0 20080202//EN"
Delivered as file "default-mixes3.ent" -->
<!-- ============================================================= -->
<!-- ============================================================= -->
<!-- SYSTEM: Journal Archiving and Interchange DTD of the -->
<!-- Archiving and Interchange 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). -->
<!-- -->
<!-- CONTAINS: 1) PEs that define the element mixes (such as -->
<!-- phrase-level elements, para-level elements, -->
<!-- inside-a-table-cell elements) -->
<!-- -->
<!-- CREATED FOR: -->
<!-- Digital Archive of Journal Articles -->
<!-- National Center for Biotechnology Information -->
<!-- (NCBI) -->
<!-- National Library of Medicine (NLM) -->
<!-- -->
<!-- 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: -->
<!-- [email protected] -->
<!-- ============================================================= -->
<!-- ============================================================= -->
<!-- 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" -->
<!-- ============================================================= -->
<!-- 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; |
%just-para.class; | %list.class; |
%math.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 no 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 ==== -->