-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathJATS-archivecustom-models1.ent
1119 lines (902 loc) · 55.1 KB
/
JATS-archivecustom-models1.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
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!-- ============================================================= -->
<!-- MODULE: Journal Archiving DTD Customize Content and -->
<!-- Attributes 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 Content and Attributes Module v1.0 20120330//EN"
Delivered as file "JATS-archivecustom-models1.ent" -->
<!-- ============================================================= -->
<!-- ============================================================= -->
<!-- SYSTEM: Journal Archiving and Interchange DTD of the -->
<!-- JATS DTD Suite -->
<!-- -->
<!-- PURPOSE: To declare the Parameter Entities (PEs) used to -->
<!-- over-ride the content models, parts of content -->
<!-- models, or attribute lists of the JATS 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. -->
<!-- -->
<!-- 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: -->
<!-- [email protected] -->
<!-- ============================================================= -->
<!-- ============================================================= -->
<!-- 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/
18. RELATED OBJECT - Added <related-object> everywhere
<related-article> was used, including inside
<article-meta> using article-meta-model.
17. CONTRIBUTOR MODEL - Added "contrib-id.class" to the
<contrib> model, to hold identifiers for people,
such as publishers-specific IDs, and ORCIDs.
16. VERSE-LINE ELEMENTS - Added the PE %verse-line-elements to
this module because the default expanded, and Archiving did
not need to expand as it already was expanded.
14. DATE ATTRIBUTES - Added attributes to <date> through @date-atts:
a) @iso-8601-date - ISO 8601 standard date format
of the publication date. Format YYYY-MM-DDThh:mm:ss
b) @calendar - Name of the calendar used (@calendar) in
naming this publication date (such as "Gregorian",
"Japanese" (Emperor years), or "Islamic").
c) Added @publication-format, so that both publication
dates and history dates can separate the format of the
publication from the version/lifecycle event. Thus
both an "article" and a "manuscript" might be received.
13. STANDARDS ORGANIZATION - Added std-organization-elements
to increase what was allowed in the names of standards bodies.
12. XREF REF TYPES - #9 below says "XREF ATTRIBUTES - Removed
the %xref-atts PE from this module since the regular version
(in xlink3.ent) was equally inclusive. But it is NOT.
Brought back %xref-atts;
11. ISSN-L ELEMENTS - Added <X> TO <issn-l> via
%issn-l-elements;
=============================================================
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.
10. Updated the DTD-version attribute to "0.4"
9. 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.
7. XREF ATTRIBUTES - Removed the %xref-atts PE from this module
since the regular version (in xlink3.ent) was equally inclusive.
6. ISSUE - Allowed to repeat inside <article-meta>
5. AFFILIATION ALTERNATIVES - Added the element <aff-alternatives>
to <article-meta> through %article meta-model;. This element
will hold multiple <aff>s that are a representation of a
single affiliation, for example, the name of an institution
in two languages or two scripts.
4. PERSON-GROUP - Became a mixed-content model, so the parameter
entity %person-group-model: was changed to
%person-group-elements;, which will be mixed with #PCDATA
as defined in references.ent. The PE person-group-model has
been retained in references.ent for compatibility, but has been
set to the mixed model using person-group-elements.
3. @SPECIFIC-USE and @XML:LANG - Added the @specific-use and
@xml:lang to %display-atts;. Also added these attributes
to the following over-rides:
- article-id through article-id-atts (@specific-user only)
- award-id through award-id-atts (both)
- date through date-atts (@specific-use only)
- funding-statement through funding-statement-atts (both)
- pub-id through pub-id-atts (@specific-use only)
- trans-title through pub-id-atts (@specific-use only;
@xml:lang already)
- xref through xref-atts (both)
2. STRING-DATE - Added <string-date> back to the following
elements using %citation-additions.class;. It was accidentally
deleted during the 3.0 revision of references.class:
- product (%product-elements;)
- related-article (%related-article-elements;)
- related-object (%related-object-elements;)
- funding-statement through funding-statement-atts (both)
=============================================================
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;" >
<!-- 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;" >
<!-- 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;" >
<!-- ISSN-L ELEMENTS -->
<!-- Elements for use with data characters inside
the model for the <issn-l> element -->
<!ENTITY % issn-l-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; |
%citation-additions.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; |
%citation-additions.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; |
%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;" >
<!-- 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;" >
<!-- STANDARDS ORGANIZATION ELEMENTS -->
<!-- The elements that can be included along with
data characters inside the content model of
<std-organization>. -->
<!ENTITY % std-organization-elements
"| %all-phrase; | %break.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;" >
<!-- VERSE-LINE ELEMENTS -->
<!-- The elements that can be included along with
data characters inside the content model of
a <verse-line>
Design Note: All inline mixes begin with an
OR bar, but since %simple-text; is an inline
mix, the OR bar is already there. -->
<!ENTITY % verse-line-elements
"%simple-text;" >
<!-- 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 #IMPLIED
xlink:type (simple) #IMPLIED
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) -->
<!-- ============================================================= -->
<!-- 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.class; |
%aff-alternatives.class; | %x.class;)*,
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.class;)*,
abstract*,
trans-abstract*, kwd-group*, 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
"(%contrib-id.class; | %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;)+ )" >
<!-- PUBLICATION DATE MODEL -->
<!-- Content model for the element <pub-date> -->
<!ENTITY % pub-date-model