-
Notifications
You must be signed in to change notification settings - Fork 0
/
display.ent
988 lines (865 loc) · 55.1 KB
/
display.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
<!-- ============================================================= -->
<!-- MODULE: Display Class Elements -->
<!-- VERSION: 1.0 -->
<!-- DATE: December 2002 -->
<!-- -->
<!-- ============================================================= -->
<!-- ============================================================= -->
<!-- PUBLIC DOCUMENT TYPE DEFINITION -->
<!-- TYPICAL INVOCATION -->
<!--
"-//NLM//DTD Archiving and Interchange DTD Suite Display Class Elements v1.0 20021201//EN"
Delivered as file "display.ent" -->
<!-- ============================================================= -->
<!-- ============================================================= -->
<!-- SYSTEM: Archiving and Interchange DTD Suite -->
<!-- -->
<!-- PURPOSE: Describes display-related elements such as -->
<!-- Figures, Graphics, Math, Chemical Structures, -->
<!-- Graphics, etc. -->
<!-- -->
<!-- CONTAINS: 1) Default values for display classes -->
<!-- 2) Parameter Entities for attribute lists -->
<!-- 3) Parameter Entities for content models -->
<!-- 4) The display class elements (alpha order) -->
<!-- a) Array -->
<!-- b) Boxed text -->
<!-- c) Chemical Structure -->
<!-- d) Figure -->
<!-- e) Graphic -->
<!-- f) Inline Graphic -->
<!-- g) Pre-formatted text -->
<!-- e) Supplementary Information -->
<!-- h) Table Group -->
<!-- i) Table Wrapper -->
<!-- j) Table (invoked module) -->
<!-- -->
<!-- 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: -->
<!-- [email protected] -->
<!-- -->
<!-- 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 VERSION\CHANGE HISTORY -->
<!-- ============================================================= -->
<!--
=============================================================
Version Reason/Occasion (who) vx.x (yyyy-mm-dd)
-->
<!-- ============================================================= -->
<!-- PARAMETER ENTITY DEPENDENCIES
Requires the following parameter entities
be defined before calling this module,
usually accomplished in the Customization
Module for the specific DTD:
Element Classes and Groups
%access.class;
%block-math;
%break.class;
%emphasis.class;
%inside-table-wrapper;
%intable-para.class;
%label.class;
%list.class;
%math.class;
%simple-display.class;
%simple-link.class;
%subsup.class;
Content Models
%sec-opt-title-model;
Attribute Lists
%link-atts;
%might-link-atts;
%other-table-wrap-atts;
-->
<!-- ============================================================= -->
<!-- ============================================================= -->
<!-- DEFAULT DEFINITION OF THE DISPLAY CLASS -->
<!-- ============================================================= -->
<!-- DISPLAY CLASS ELEMENTS -->
<!-- Graphical or other image-related elements.
The display elements may occur within
the text of a table cell or paragraph
although they are typically at the same
hierarchical level as a paragraph. -->
<!ENTITY % block-display.class
"array | boxed-text | chem-struct |
chem-struct-wrapper |
fig | fig-group | graphic | preformat |
supplementary-material | table-wrap |
table-wrap-group" >
<!-- INLINE DISPLAY CLASS ELEMENTS -->
<!-- Non-block display elements that set or
display inline with the text -->
<!ENTITY % inline-display.class
"inline-graphic" >
<!-- SIMPLE DISPLAY ELEMENTS -->
<!-- The simplest and most basic of the Display
Class elements, which may be allowed in many
places, for example, inside other Display
Class elements. -->
<!ENTITY % simple-display.class
"array | chem-struct | graphic | preformat" >
<!-- ============================================================= -->
<!-- DEFAULT PES FOR ATTRIBUTE LISTS -->
<!-- ============================================================= -->
<!-- DISPLAY ATTRIBUTES OPTIONAL ID -->
<!-- position Must this display object (figure, boxed text,
etc.) be anchored in its exact location
within the text or may it float, for example
to the top of the next page, next column, or
within a separate window? Values are:
anchor Object must remain in place
float Object is not anchored and
may be moved to a new column,
a new window, etc.
margin In print, item should be placed
in the margin or gutter.
Online the item should
remain closely associated
with the text. -->
<!ENTITY % display-atts
"position (anchor | float | margin) 'float'" >
<!-- BOXED TEXT ATTRIBUTES -->
<!-- Attributes for the boxed text <boxed-text>
element -->
<!ENTITY % boxed-text-atts
"id ID #IMPLIED
%display-atts;
xml:lang NMTOKEN #IMPLIED" >
<!-- CHEMICAL STRUCTURE WRAPPER ATTRIBUTES -->
<!-- Attributes for the <chem-struct-wrapper>
element, the outer wrapper around one or more
chemical structures -->
<!ENTITY % chem-struct-wrapper-atts
"id ID #IMPLIED
%display-atts;" >
<!-- CHEMICAL STRUCTURE ATTRIBUTES -->
<!-- Attributes for <chem-struct> -->
<!ENTITY % chem-struct-atts
"%might-link-atts;" >
<!-- FIGURE GROUP ATTRIBUTES -->
<!-- Attributes for Figure Groups <fig-group> -->
<!ENTITY % fig-group-atts
"id ID #IMPLIED
%display-atts;" >
<!-- FIGURE ATTRIBUTES -->
<!-- Attributes for Figures <fig> -->
<!ENTITY % fig-atts
"id ID #IMPLIED
%display-atts;
xml:lang NMTOKEN #IMPLIED
fig-type CDATA #IMPLIED" >
<!-- GRAPHIC ATTRIBUTES -->
<!-- Attributes for Graphic <graphic> -->
<!ENTITY % graphic-atts
"id ID #IMPLIED
%display-atts;
alt-version
(yes | no) 'no'
%link-atts;" >
<!-- PREFORMATTED TEXT ATTRIBUTES -->
<!-- Attributes for Preformatted Text <preform> -->
<!ENTITY % preformat-atts
"id ID #IMPLIED
%display-atts;
preformat-type
CDATA #IMPLIED
xml:space (default | preserve) #FIXED 'preserve'
xml:lang NMTOKEN #IMPLIED" >
<!-- SUPPLEMENTARY INFORMATION ATTRIBUTES -->
<!-- Attributes for Supplementary Information
<supplementary-material> -->
<!ENTITY % supplementary-material-atts
"id ID #IMPLIED
%display-atts;
%might-link-atts;
mimetype CDATA #IMPLIED
xml:lang NMTOKEN #IMPLIED" >
<!-- TABLE GROUP ATTRIBUTES -->
<!-- Attributes for Table Groups
<table-wrap-group> -->
<!ENTITY % table-wrap-group-atts
"id ID #IMPLIED
%display-atts;" >
<!-- TABLE WRAPPER ATTRIBUTES -->
<!-- Attributes for Table Wrapper <table-wrap> -->
<!ENTITY % table-wrap-atts
"id ID #IMPLIED
xml:lang NMTOKEN #IMPLIED
%display-atts;
%other-table-wrap-atts;" >
<!-- ============================================================= -->
<!-- PARAMETER ENTITIES FOR CONTENT MODELS -->
<!-- ============================================================= -->
<!-- DISPLAY ELEMENT BACK MATTER -->
<!-- Miscellaneous stuff at the end of a display
element such as a figure or a boxed text
element such as a sidebar -->
<!ENTITY % display-back-matter
"copyright-statement" >
<!-- FIGURE-LIKE CONTENT MODEL -->
<!-- Content model for the Figure element and any
similarly structured elements -->
<!ENTITY % fig-model "label?, caption?, (%access.class;)*,
(%block-math; | %intable-para.class; |
%list.class; | %simple-display.class; |
p | table-wrap)*,
(%display-back-matter;)*" >
<!-- TABLE WRAPPER CONTENT MODEL -->
<!-- Content model for the container element that
surrounds the standard table models for row
and columns. -->
<!ENTITY % table-wrap-model
"label?, caption?, (%access.class;)*,
(%inside-table-wrapper;)*,
(table-wrap-foot | %display-back-matter;)*" >
<!-- ============================================================= -->
<!-- ARRAY ELEMENTS -->
<!-- ============================================================= -->
<!-- ARRAY CONTENT MODEL -->
<!-- The element used to contain material in
rows and columns that is just a block insert
into the text flow, not numbered or called a
table, and not titled or captioned -->
<!ENTITY % array-model "(%access.class;)*, (graphic | tbody),
(%display-back-matter;)*" >
<!-- ARRAY (SIMPLE TABULAR ARRAY) -->
<!-- Used to define in-text table-like (columnar)
material. Uses the XHTML table body element
or a graphic to express the rows and columns.
These have neither labels nor captions,
arrays with labels and captions are table
wrappers.
Remarks: Arrays are not allowed to float,
they are tied to their position in the
text. -->
<!ELEMENT array (%array-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).
Display Note: An Array element is assumed
to be anchored at its position within the
text. -->
<!ATTLIST array
xml:lang NMTOKEN #IMPLIED >
<!-- ============================================================= -->
<!-- BOXED TEXT ELEMENTS -->
<!-- ============================================================= -->
<!-- BOXED TEXT MODEL -->
<!-- Complete content model for the boxed text
element, made into a PE so that it could be
redefined, for example, by an authoring DTD.
-->
<!ENTITY % boxed-text-model
"%sec-opt-title-model;,
(%display-back-matter;)*" >
<!-- BOXED TEXT -->
<!-- Textual material that is outside the flow
of the narrative text, for example, a
sidebar, marginalia, text insert, caution or
note box, etc. -->
<!ELEMENT boxed-text (%boxed-text-model;) >
<!-- id Unique identifier so the element may be
referenced
position Must this display object (figure, boxed text,
etc.) be anchored in its exact location
within the text or may it float, for example
to the top of the next page, next column, or
within a separate window? Values are:
anchor Object must remain in place
float Object is not anchored and
may be moved to a new column,
a new window, etc.
margin In print, item should be placed
in the margin or gutter.
Online the item should
remain closely associated
with the text.
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 boxed-text
%boxed-text-atts; >
<!-- ============================================================= -->
<!-- CHEMICAL STRUCTURE ELEMENTS -->
<!-- ============================================================= -->
<!-- CHEMICAL STRUCTURE WRAPPER MODEL -->
<!-- Content model for the Chemical Structure
Wrapper <chem-struct-wrapper> element -->
<!ENTITY % chem-struct-wrapper-model
"label?, caption?, (%access.class;)*,
(chem-struct | graphic)+,
(%display-back-matter;)*" >
<!-- CHEMICAL STRUCTURE WRAPPER -->
<!-- A chemical expression, reaction, equation,
etc. that is set apart within the text.
These may be numbered. They may be modeled
as ASCII characters or as one or more
graphics.
Implementer's Note: CML will go here, if
added.
Display Note: A chemical structure is assumed
to be anchored at its position within the
text. -->
<!ELEMENT chem-struct-wrapper
(%chem-struct-wrapper-model;) >
<!-- id A unique identifier for the chemical structure
position Must this display object (figure, boxed text,
etc.) be anchored in its exact location
within the text or may it float, for example
to the top of the next page, next column, or
within a separate window? Values are:
anchor Object must remain in place
float Object is not anchored and
may be moved to a new column,
a new window, etc.
margin In print, item should be placed
in the margin or gutter.
Online the item should
remain closely associated
with the text. -->
<!ATTLIST chem-struct-wrapper
%chem-struct-wrapper-atts; >
<!-- CHEMICAL STRUCTURE MODEL -->
<!-- A chemical expression, reaction, equation,
etc. that is set apart within the text
Design Note: The list class was added to
cover the Elsevier DTD <compound-info>
element.
Authoring Note: This model allows for a
<graphic> element inside of the <chem-struct>
that holds the structure or for using the
linking attributes to point directly to the
URI of such as graphic.
Authoring Note: Accessibility elements should
not be used with this element if they can be
used as part of the <chem-struct-wrapper>
wrapper element. They are allowed as part of
this element only for those
<chem-struct-wrapper> elements that
contain more than one <chem-struct>. -->
<!ENTITY % chem-struct-model
"(#PCDATA | %access.class; | %break.class; |
%emphasis.class; | %list.class; |
%math.class; | %simple-display.class; |
%simple-link.class; | %subsup.class;)*" >
<!-- CHEMICAL STRUCTURE (DISPLAY) -->
<!-- A chemical expression, reaction, equation,
etc. that is set apart within the text -->
<!ELEMENT chem-struct %chem-struct-model; >
<!ATTLIST chem-struct
%chem-struct-atts; >
<!-- ============================================================= -->
<!-- FIGURE ELEMENTS -->
<!-- ============================================================= -->
<!-- FIGURE GROUP MODEL -->
<!ENTITY % fig-group-model "label?, caption?, (%access.class;)*,
(fig |graphic)*" >
<!-- FIGURE GROUP -->
<!-- Used for a group of figures that must be
displayed together -->
<!ELEMENT fig-group (%fig-group-model;) >
<!-- id Unique identifier so the element may be
referenced
Authoring Note: The value of the "id"
attribute for a Figure Group should begin
with "FG" (FG1, FG2, FGIII).
position Must this display object (figure, boxed text,
etc.) be anchored in its exact location
within the text or may it float, for example
to the top of the next page, next column, or
within a separate window? Values are:
anchor Object must remain in place
float Object is not anchored and
may be moved to a new column,
a new window, etc.
margin In print, item should be placed
in the margin or gutter.
Online the item should
remain closely associated
with the text. -->
<!ATTLIST fig-group
%fig-group-atts; >
<!-- FIGURE -->
<!-- A block of graphic or textual material that
is identified as a "Figure", usually with
a caption and a label such as "Figure" or
"Figure 3.".
The content of a Figure need not be
graphical in nature, for example a list or a
table may be the content of a Figure.
Authoring and Conversion Note: Unlabeled
graphical objects found in the content
should be tagged as <graphic>s. A common
test for Figure versus Graphic is to ask
yourself whether, if you were to create a
"List of Figures" for this article, the
object would or would not appear in such a
list. -->
<!ELEMENT fig (%fig-model;) >
<!-- id Unique identifier so the element may be
referenced
Authoring Note: The value of the "id"
attribute for a Figure should begin with "F"
(F1, F2, FIII).
Authoring Note: The value of the "id"
attribute for a scheme should begin with "S"
(S1, S2). The value of the "id" attribute
for a plate should begin with "P" (P1, P2).
position Must this display object (figure, boxed text,
etc.) be anchored in its exact location
within the text or may it float, for example
to the top of the next page, next column, or
within a separate window? Values are:
anchor Object must remain in place
float Object is not anchored and
may be moved to a new column,
a new window, etc.
margin In print, item should be placed
in the margin or gutter.
Online the item should
remain closely associated
with the text.
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).
fig-type Some DTDs make a distinction between
different types of graphical objects, some
with attributes, some with elements. This
attribute is for use in preserving that
intellectual content. For example, this
attribute could record the fact that the
contents of this figure are: a cartoon,
chart, diagram, drawing, exhibit,
illustration, map, plate, scheme, workflow,
etc. -->
<!ATTLIST fig
%fig-atts; >
<!-- CAPTION OF A FIGURE, TABLE, ETC. -->
<!-- Wrapper element for the textual description
associated with a figure, table, etc. In
some source document captions, the first
sentence is set off from the rest as a title.
In some source document, figures may posses
both a title and a caption, in which case
the title will be moved inside the caption
during conversion. -->
<!ELEMENT caption (title?, 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 caption
xml:lang NMTOKEN #IMPLIED >
<!--ELEM title Defined in %common.ent; -->
<!--ELEM p Defined in %common.ent; -->
<!-- ============================================================= -->
<!-- THE GRAPHIC ELEMENT -->
<!-- ============================================================= -->
<!-- GRAPHIC MODEL -->
<!-- Content model for the <graphic> element -->
<!ENTITY % graphic-model
"(%access.class; | %label.class; |
caption | copyright-statement)*" >
<!-- GRAPHIC -->
<!-- An external file that holds a picture,
illustration, etc., usually as some form of
binary object. The "content" of the <graphic>
element is not the object, but merely
information about the object.
Authoring and Conversion Note: Internal
elements such as <caption> should always be
used at the highest possible level, in
other words, if a Graphic is inside a
Figure, the <caption>, <long-desc>, etc.
should be part of the Figure, not part of
the Graphic. Elements such as <caption>
are used when a standalone graphic requires
them or when multiple graphics within a
container element such as a Figure need
them individually. Similarly, the "position"
attribute should not be used on a <graphic>
that is inside a larger display, container
such as a Paragraph. -->
<!ELEMENT graphic %graphic-model; >
<!-- id Unique identifier so the element may be
referenced. The "id" attribute such as
should be used at the highest level
possible, therefore a graphic only needs an
"id" when it is standalone.
position Must this display object (figure, boxed text,
etc.) be anchored in its exact location
within the text or may it float, for example
to the top of the next page, next column, or
within a separate window? Values are:
anchor Object must remain in place
float Object is not anchored and
may be moved to a new column,
a new window, etc.
margin In print, item should be placed
in the margin or gutter.
Online the item should
remain closely associated
with the text.
alt-version
Has an alternate version of the graphic also
been provided, for example a thumbnail or
a different resolution? Values are:
yes There is an alternative version
no There is not
Note: This is only a flag and does not
provide the URI of the alternate.
xlink:href Provides an address or identifier of the
object to which the link points, for
example a URI or a filename
NOTE: A graphic will always have an
"xlink:href" attribute that points to the
URI where the graphic may be found.
Authoring and Conversion Note: Best practice
for graphic file names is to limit the names
and path names to the characters: letters,
numbers, underscore, hyphen, and period. All
such names are assumed to be case sensitive.
DOS-style file extensions may be used. -->
<!ATTLIST graphic
%graphic-atts; >
<!-- ============================================================= -->
<!-- INLINE GRAPHIC -->
<!-- ============================================================= -->
<!-- INLINE GRAPHIC -->
<!-- A small graphic such as an icon or a small
picture symbol that is displayed or set
in the same line as the text.
Authoring and Conversion Note: Although the
DTD cannot enforce it, this element should
NOT be used for custom-built or private
characters, such as those in the Unicode
private use areas. For such characters,
use the <private-char> element, see
%chars.ent; -->
<!ELEMENT inline-graphic
(alt-text?) >
<!-- xlink:href Provides an address or identifier of the
object to which the link points, for
example a URI or a filename
NOTE: An inline graphic will always have an
"xlink:href" attribute that points to the
URI where the graphic may be found. -->
<!ATTLIST inline-graphic
%link-atts; >
<!-- ============================================================= -->
<!-- PRESERVE THE WHITESPACE TEXT -->
<!-- ============================================================= -->
<!-- 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; | %emphasis.class; |
%display-back-matter; | %subsup.class;" >
<!-- PREFORMATTED TEXT -->
<!-- Used for preformatted text such as
computer code in which whitespace, such as
tabs, line feeds, and spaces, should be
preserved. Typically displayed or printed
in a monofont to preserve character
alignment.
Related Elements: Poetry may be tagged with
<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 preformat (#PCDATA | %preformat-elements;)* >
<!-- id Unique identifier so the element may be
referenced.
position Must this display object (figure, boxed text,
etc.) be anchored in its exact location
within the text or may it float, for example
to the top of the next page, next column, or
within a separate window? Values are:
anchor Object must remain in place
float Object is not anchored and
may be moved to a new column,
a new window, etc.
margin In print, item should be placed
in the margin or gutter.
Online the item should
remain closely associated
with the text.
preformat-type
What kind of content, for example:
code Computer code
poetry Poems
ascii ASCII art
This attribute is added to preserve the
intellectual content of DTDs that provide
this information. Many documents will not
be able to provide this data.
xml:space Request that, when printing or displaying
this element, all white space such as tabs
and spaces and line breaks be preserved.
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 preformat
%preformat-atts; >
<!-- ============================================================= -->
<!-- SUPPLEMENTARY MATERIAL -->
<!-- ============================================================= -->
<!-- SUPPLEMENTARY MATERIAL MODEL -->
<!-- Content model for the
<supplementary-material> element -->
<!ENTITY % supplementary-material-model
"%fig-model;" >
<!-- SUPPLEMENTARY MATERIAL -->
<!-- Additional data files that contain
information directly supportive of the item,
for example, an audio clip, movie, database,
spreadsheet, applet, or other external file.
Remarks: This is similar to the audio-visual
element in some DTDs and the unprinted-item
element (meaning that it is used only for
electronic files) in other DTDs.
Remarks: This element is used in two senses:
inside the article front matter as an alert
to the existence of supplementary material
and as part of the textual flow, where it is
similar to a Figure, in that it can be
positioned as a floating or anchored object
and may take a caption.
In addition, the supplementary material
may identify its file type with the
"mimetype" attribute.
Authoring Note: Supplementary material may
contain a preview image (e.g., the first
frame of a movie, tagged as a <graphic>),
with the caption/preview placed in a manner
similar to a Figure and a cross-reference
made to the material from the text.
Related Elements: See related element
<inline-supplementary-material> for
a simpler form that can be used to mark up
text references to supplementary material
where the reference appears in the regular
flow of the text and does not have a preview
image or separate caption. -->
<!ELEMENT supplementary-material
(%supplementary-material-model;) >
<!-- id Unique identifier so the element may be
referenced
position Must this display object (figure, boxed text,
etc.) be anchored in its exact location
within the text or may it float, for example
to the top of the next page, next column, or
within a separate window? Values are:
anchor Object must remain in place
float Object is not anchored and
may be moved to a new column,
a new window, etc.
margin In print, item should be placed
in the margin or gutter.
Online the item should
remain closely associated
with the text.
xlink:href Provides an address or identifier of the
object to which the link points, for
example a URI or a filename
mimetype The mime type of the supplementary material
Authoring Note: This attribute will be
required when creating new articles.
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 supplementary-material
%supplementary-material-atts; >
<!-- ============================================================= -->
<!-- TABLE ELEMENTS -->
<!-- ============================================================= -->
<!-- TABLE WRAPPER GROUP MODEL -->
<!-- Content model for the <table-wrap-group>
element -->
<!ENTITY % table-wrap-group-model
"label?, caption?, (%access.class;)*,
table-wrap+" >
<!-- TABLE WRAPPER GROUP -->
<!-- Used as a wrapper tag to contain a group of
tables that must be displayed together -->
<!ELEMENT table-wrap-group
(%table-wrap-group-model;) >
<!-- id Unique identifier so the element may be
referenced
Authoring Note: id of table group should
begin with "TG" (TG1, TGIV, TG43)
position Must this display object (figure, boxed text,
etc.) be anchored in its exact location
within the text or may it float, for example
to the top of the next page, next column, or
within a separate window? Values are:
anchor Object must remain in place
float Object is not anchored and
may be moved to a new column,
a new window, etc.
margin In print, item should be placed
in the margin or gutter.
Online the item should
remain closely associated
with the text. -->
<!ATTLIST table-wrap-group
%table-wrap-group-atts; >
<!-- TABLE WRAPPER -->
<!-- Used to hold a complete table, that is, not
only the rows and columns that make up a
table, but also the table captions, list
of table footnotes, alternative descriptions
for accessibility, etc. Within the Table
Wrapper element, the row and column tags that
describe the table cells are defined by one
of the popular "standard" table models, for
example the XHTML table model, OASIS Exchange
(CALS) table model, of the Elsevier Science
Full Length Article table body <tblbody>
model, et al.)
Remarks: This model has been designed to allow
for a "table" that is just a graphic or a list
rather than the explicit rows and columns of a
table element such as XHTML <table>.
Authoring and Conversion Note: Many journal
DTDs use an element Called Table Footnote,
with a tag such as <tblfn> for the footnotes
inside a table. This DTD uses <fn> inside
tables as well as everywhere. They are
differentiated by context. Footnotes inside
a Table Wrapper are assumed to be footnotes
to the table and part of the table,
printed at the bottom of it, etc. -->
<!ELEMENT table-wrap (%table-wrap-model;) >
<!-- id Unique identifier so the element may be
referenced
Authoring Note: The value of the "id"
attribute of table should begin with
"T" (T1, TIV, T43)
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 table-wrap
%table-wrap-atts; >
<!-- TABLE WRAP FOOTER MODEL -->
<!-- Content model for the <table-wrap-foot>
element -->
<!ENTITY % table-wrap-foot-model
"title?, (p | fn | %display-back-matter;)+" >
<!-- TABLE WRAP FOOTER -->
<!-- Wrapper element to hold a group of footnotes
or other notes or general paragraphs at the
end of a table. Not the same as the
Table Foot <tfoot>, which contains rows
and columns like the rest of the table. -->
<!ELEMENT table-wrap-foot
(%table-wrap-foot-model;) >
<!-- ================== End Display Class Module ================= -->