-
Notifications
You must be signed in to change notification settings - Fork 0
/
JATS-archivecustom-mixes1.ent
357 lines (306 loc) · 19.7 KB
/
JATS-archivecustom-mixes1.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
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
<!-- ============================================================= -->
<!-- MODULE: Journal Archiving DTD Customize Mixes Module -->
<!-- VERSION: ANSI/NISO JATS Version 1.0 (Z39.96-2012) -->
<!-- DATE: March 2012 -->
<!-- -->
<!-- ============================================================= -->
<!-- ============================================================= -->
<!-- PUBLIC DOCUMENT TYPE DEFINITION -->
<!-- TYPICAL INVOCATION -->
<!--
"-//NLM//DTD JATS (Z39.96) Journal Archiving DTD Customize Mixes Module v1.0 20120330//EN"
Delivered as file "JATS-archivecustom-mixes1.ent" -->
<!-- ============================================================= -->
<!-- ============================================================= -->
<!-- SYSTEM: Journal Archiving and Interchange DTD of the -->
<!-- JATS DTD Suite -->
<!-- -->
<!-- PURPOSE: To declare the Parameter Entities (PEs) used to -->
<!-- over-ride the JATS DTD Suite default named, -->
<!-- general purpose mixes. (Mixes for particular -->
<!-- elements are declared in the Archive Custom -->
<!-- Models module.) -->
<!-- -->
<!-- Note: Since PEs must be declared before they -->
<!-- are used, this module must be called before the -->
<!-- default mixes modules (%default-mixes;) -->
<!-- -->
<!-- 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. -->
<!-- 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: -->
<!-- August 2004 -->
<!-- -->
<!-- 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 Journal Archiving and Interchange DTD is -->
<!-- built from the JATS DTD Suite. -->
<!-- -->
<!-- This DTD and the Suite are a continuation of -->
<!-- the work done by NCBI, Mulberry Technologies, -->
<!-- and Inera, Inc. on the NLM Journal Archiving -->
<!-- and Interchange DTD Suite, which was originally -->
<!-- released in December, 2002. -->
<!-- -->
<!-- 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 -->
<!-- Inera Inc.'s collaboration with other DTD -->
<!-- authors in completing NLM Version 1.0. The -->
<!-- Andrew W. Mellon Foundation provided support for -->
<!-- these important contributions. -->
<!-- -->
<!-- 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/
5. RELATED OBJECT - Added <related-object> everywhere
<related-article> was used.
4. PARA-LEVEL PARAMETER ENTITY CONFLICT - Changed the parameter
entity %para-level; to use the PE %nothing-but-para.class;,
removing the similar PE "just-para.class;". It is possible to
add element(s) to %just-para.class;, so that the added element(s)
may be used everywhere <p> is used. Such elements would also be
named in %block-display.class;. This would lead to a conflict
in %para-level; if both %just-para.class; and
%block-display.class; named <p>. So %just-para; is replaced
here in %para-level;. This is backward compatible for all XML
documents. If a JATS customization has modified %just-para.class;
they may need to change their customization to accommodate.
=============================================================
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.
3. Updated the DTD-version attribute to "0.4"
2. 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.
=============================================================
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) -->
<!-- ============================================================= -->
<!-- ============================================================= -->
<!-- EXCEPTION: A MIX USED IN OTHER MIXES -->
<!-- ============================================================= -->
<!-- ALL PHRASE-LEVEL ELEMENTS -->
<!-- This Parameter Entity contains all of the
phrase-level elements in the entire
Archival Tag Set EXCEPT THE <break> element.
MAINTENANCE NOTE:
Since this is used inside other mixes
(like a class and unlike all other mixes)
all-phrase must
- be declared first in this module.
- does not start with an OR bar, as all
other inline mixes do -->
<!ENTITY % all-phrase "%address-link.class; | %article-link.class; |
%appearance.class; | %emphasis.class; |
%inline-display.class; |
%inline-math.class; | %math.class; |
%phrase.class; | %simple-link.class; |
%subsup.class; | %x.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.
MAINTENANCE 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 "%all-phrase; | %block-math.class; |
%break.class; | %chem-struct-wrap.class; |
%citation.class; |
%list.class; |
%simple-display-noalt.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.
-->
<!ENTITY % doc-back-matter-mix
"%back.class; | %front-back.class; |
%sec.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; |
%list.class; | %math.class; |
%nothing-but-para.class; |
%related-article.class; |
%rest-of-para.class; | %x.class;" >
<!-- ============================================================= -->
<!-- INLINE ELEMENT MIXES -->
<!-- ============================================================= -->
<!-- EMPHASIS MIX ELEMENTS -->
<!-- Elements that may be used inside most of the
emphasis class elements -->
<!ENTITY % emphasized-text
"| %all-phrase; | %break.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 . -->
<!ENTITY % just-rendition
"| %all-phrase;" >
<!-- 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 . -->
<!ENTITY % rendition-plus
"| %all-phrase;" >
<!-- 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. -->
<!ENTITY % simple-phrase
"| %all-phrase;" >
<!-- 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 in the original, this contained
no math and no links, thus is was even
simpler than %simple-phrase; (As of v2 2004)
the two are the same. -->
<!ENTITY % simple-text "| %all-phrase;" >
<!-- ================== End Archiving DTD Mixes Customization ==== -->