-
Notifications
You must be signed in to change notification settings - Fork 0
/
articlemeta.ent
1431 lines (1214 loc) · 75.5 KB
/
articlemeta.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 Article Metadata Elements -->
<!-- VERSION: 1.0 -->
<!-- DATE: December 2002 -->
<!-- -->
<!-- ============================================================= -->
<!-- ============================================================= -->
<!-- PUBLIC DOCUMENT TYPE DEFINITION -->
<!-- TYPICAL INVOCATION -->
<!--
"-//NLM//DTD Archiving and Interchange DTD Suite Journal Article Metadata Elements v1.0 20021201//EN"
Delivered as file "articlemeta.ent" -->
<!-- ============================================================= -->
<!-- ============================================================= -->
<!-- SYSTEM: Archiving and Interchange DTD Suite -->
<!-- -->
<!-- PURPOSE: Names all elements used to describe the journal -->
<!-- in which the journal article is published. -->
<!-- -->
<!-- CONTAINS: 1. Article element parameter entity -->
<!-- 2. Article metadata elements in alphabetical -->
<!-- order -->
<!-- -->
<!-- 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:
Classes and Mixes
%address.elems;
%break.class;
%conference.class;
%contrib-info;
%emphasis.class;
%inline-display.class;
%inline-math;
%link.class;
%just-rendition;
%references.class;
%rendition-plus;
%simple-link.class;
%simple-phrase.class;
%simple-text;
%subsup.class;
%title-elements;
Complete Content Models
%article-meta-model;
%date-model;
%sec-opt-title-model;
Attribute Values
%pub-id-types;
Attribute Lists
%might-link-atts;
-->
<!-- ============================================================= -->
<!-- ============================================================= -->
<!-- PARAMETER ENTITIES FOR ATTRIBUTE VALUES -->
<!-- ============================================================= -->
<!-- PUBLICATION TYPES -->
<!-- Used to record the type of publication, for
example a print-only publication versus
an electronic-only publication, in any of
several life stages.
This Parameter Entity is intended to name
the values of the "pub-type" attribute, but
in Version 1.0 of this DTD Suite, the
"pub-type" attribute is defined with a
Declared Value of CDATA and this Parameter
Entity is not used or provide its values.
Suggested values include:
epub - Electronic publication
ppub - Print publication
epub-ppub - Published in both print and
electronic form
epreprint - Electronic preprint
dissemination
ppreprint - Print preprint dissemination
ecorrected - Corrected in electronic
pcorrected - Corrected in print
eretracted - Retracted in electronic
pretracted - Retracted in print -->
<!ENTITY % pub-types "epub | ppub | epub-ppub | epreprint |
ppreprint | ecorrected | pcorrected |
eretracted | pretracted" >
<!-- ============================================================= -->
<!-- PARAMETER ENTITIES FOR ATTRIBUTE LISTS -->
<!-- ============================================================= -->
<!-- ABSTRACT ATTRIBUTES -->
<!-- Attributes for the <abstract> element and
the <trans-abstract> element -->
<!ENTITY % abstract-atts
"abstract-type
CDATA #IMPLIED
xml:lang NMTOKEN #IMPLIED" >
<!-- ALTERNATE TITLE ATTRIBUTES -->
<!-- Attributes for the <alt-title> element -->
<!-- alt-title-type
Why this title was created, for example,
"short" for a short version of the title,
"toc" for use in a Table of Contents, "ASCII"
for an ASCII title, "right-running" for
a right-running-head title, etc. -->
<!ENTITY % alt-title-atts
"alt-title-type
CDATA #IMPLIED" >
<!-- CONTRIBUTOR ATTRIBUTES -->
<!-- Attributes for the Contributor <contrib>
element -->
<!-- contrib-type
What was the contribution of this person,
for example: author, editor, contributor,
translator, illustrator, designer,
research assistant, etc.
id Unique identifier, so the contributor can be
referenced
corresp Corresponding Author (Set to 'yes' if this
contributor is a corresponding author.)
equal-contrib
Contributed equally (Set to 'yes' if all
contributors contributed equally.)
deceased Deceased (Set to 'yes' if the contributor
has died.)
rid May be used to point to information concerning
the contributor, for example to the <corresp>
Corresponding Information element. There
is no limit to the number of contributors
that can be designated as corresponding.
xlink:href Provides an address or identifier of the
object to which the link points, for
example a URI or a filename. -->
<!ENTITY % contrib-atts
"contrib-type
CDATA #IMPLIED
id ID #IMPLIED
corresp (no | yes) #IMPLIED
equal-contrib
(no | yes) #IMPLIED
deceased (no | yes) #IMPLIED
rid IDREFS #IMPLIED
%might-link-atts; " >
<!-- KEYWORD GROUP ATTRIBUTES -->
<!-- Attributes for the <kwd-group> element -->
<!ENTITY % kwd-group-atts
"id ID #IMPLIED
kwd-group-type
CDATA #IMPLIED
xml:lang NMTOKEN #IMPLIED" >
<!-- PRODUCT ATTRIBUTES -->
<!-- Attributes for the Product <product>
element -->
<!-- product-type
Type of product being reviewed, for example:
book, software package, journal or journal
issue, website, film, hardware component,
etc.
xlink:href Provides an address or identifier of the
object to which the link points, for
example a URI or a filename -->
<!ENTITY % product-atts
"product-type
CDATA #IMPLIED
%might-link-atts;" >
<!-- PUBLICATION DATE ATTRIBUTES -->
<!-- Attributes for the <pub-date> element -->
<!-- Used to record the type of publication, for
example a print-only publication versus
an electronic-only publication, in any of
several life stages.
Suggested values include:
epub - Electronic publication
ppub - Print publication
epub-ppub - Published in both print and
electronic form
epreprint - Electronic preprint
dissemination
ppreprint - Print preprint dissemination
ecorrected - Corrected in electronic
pcorrected - Corrected in print
eretracted - Retracted in electronic
pretracted - Retracted in print
-->
<!ENTITY % pub-date-atts
"pub-type CDATA #IMPLIED" >
<!-- SUBJECT GROUP ATTRIBUTES -->
<!-- Attributes for the <subj-group> element -->
<!-- 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).
subj-group-type
Identification of the subject, information
class, or type of this particular subject
group -->
<!ENTITY % subj-group-atts
"xml:lang NMTOKEN #IMPLIED
subj-group-type
CDATA #IMPLIED" >
<!-- SUPPLEMENT ATTRIBUTES -->
<!-- Attributes for the <supplement> element -->
<!-- supplement-type
Indicates what sort of supplement, if the
for example: "issue" meaning a supplement to
a particular journal issue; "conference",
meaning the supplement contains information
from a conference, symposium, or other
gathering; "periodic" for supplements issued
at regular intervals, etc. -->
<!ENTITY % supplement-atts
"supplement-type
CDATA #IMPLIED" >
<!-- ============================================================= -->
<!-- PARAMETER ENTITIES FOR CONTENT MODELS -->
<!-- ============================================================= -->
<!-- CONTRIBUTOR INFORMATION -->
<!ENTITY % contrib-info "address | aff | author-comment | bio |
email | ext-link | on-behalf-of |
role | xref" >
<!-- ============================================================= -->
<!-- ARTICLE METADATA -->
<!-- ============================================================= -->
<!-- ARTICLE METADATA MODEL -->
<!ENTITY % article-meta-model
"article-id*, article-categories?,
title-group?, (contrib-group | aff)*,
author-notes?, pub-date*, volume?, issue?,
supplement?,
((fpage, lpage?) | elocation-id)?,
(ext-link|product|supplementary-material)*,
history?, copyright-statement?,
copyright-year?,
self-uri*, related-article*, abstract*,
trans-abstract*, kwd-group*,
contract-num*, contract-sponsor*,
conference*, counts?" >
<!-- ARTICLE METADATA -->
<!-- Metadata that identifies this article -->
<!ELEMENT article-meta (%article-meta-model;) >
<!--ELEM copyright-statement
Defined in %common.ent" -->
<!-- ============================================================= -->
<!-- ARTICLE METADATA ELEMENTS -->
<!-- ============================================================= -->
<!-- ============================================================= -->
<!-- ARTICLE IDENTIFICATION -->
<!-- ============================================================= -->
<!-- ARTICLE IDENTIFIER -->
<!-- Optional element, used to hold one of the
"unique identifiers" that have been assigned
at various times to an article. Such
identifiers may come from the publisher, the
jobber, or from inside PMC. Examples of such
numbers are the publishers tracking number,
the PNAS number, etc. PMC tries to carry
all identifiers associated with an article,
whether they came in as elements or attributes
on the original article.
The "type attribute" should only be used if
the type is known, for example, to identify
DOIs. -->
<!ELEMENT article-id (#PCDATA) >
<!-- pub-id-type
Publication (article) Identifier Type
Names the type of identifier, or the
organization or system that defined this
identifier for the identifier of the journal
article or a cited publication.
Used on the <article-id> element, which
holds an identifier for the entire article.
Also used on the <pubid> element, which
is an identifier for a publication cited in
a bibliographic reference (citation).
Valid Types include:
coden - Obsolete PDB/CCDC identifier (may
be present on older articles)
doi - Digital Object Identifier
medline- NLM Medline identifier
other - None of the named identifiers
pii - Publisher Item Identifier, see
http://pubs.acs.org/epub/piius.htm
or
http://www.aip.org/epub/piipr.html
pmid - PUBMED ID (see
www.ncbi.nlm.nih.gov/entrez/
query.fcgi?db=PubMed)
publisher-id
- Publisher's identifier such
as an 'article-id', 'artnum',
'identifier', 'article- number',
'pub-id', etc.
sici - Serial Item and Contribution
Identifier (SICI). A journal
article may have more than one
SICI, one for a print version and
one for an electronic version. -->
<!ATTLIST article-id
pub-id-type
(%pub-id-types;) #IMPLIED >
<!-- ============================================================= -->
<!-- ARTICLE GROUPING DATA (ARTICLE METADATA) -->
<!-- ============================================================= -->
<!-- ARTICLE GROUPING DATA -->
<!-- Container for elements that may be used to
group articles into related clusters -->
<!ELEMENT article-categories
(subj-group*, series-title*, series-text?) >
<!-- GROUPING ARTICLES IN TITLED CATEGORIES
For some journals, articles are grouped into
categories, with the category indicated in
the article's display.
Sometimes the grouping or category refers
to the type of article, such as "Essay",
"Commentary", or "Article". Sometimes the
grouping refers to subject areas, such as
"Physical Sciences", "Biological Sciences",
or "Social Sciences". Sometimes the grouping
refers to topics within the larger subject
areas, such as "Applied Math", "Biology", or
"Chemistry".
In a printed journal as well as on the PMC
website, articles may be grouped or arranged
under these headings (here are all the
Essays, here are all the Biology articles,
etc.) Some journals divide articles into
three layers of grouping, some into two, and
some into only one.
For example, a three level grouping might be:
<subj-group>
<subject>Articles</subject>
<subj-group>
<subject>Biological Sciences</subject>
<subj-group>
<subject>Entomology</subject>
</subj-group>
</subj-group>
</subj-group>
And a one-level grouping might be
<subj-group>
<subject>Retraction</subject>
</subj-group>
or, alternatively
<subj-group>
<subject>Essay</subject>
</subj-group>
Articles may also be assigned to more than
one grouping. For example, if an article is
classified as "Biochemistry" under
"Biological Sciences" and "Chemistry" under
"Physical Sciences," the subj-group wrapper
may repeat.
For example,
<subj-group>
<subject>Articles</subject>
<subj-group>
<subject>Biological Sciences</subject>
<subj-group>
<subject>Biochemistry</subject>
</subj-group>
</subj-group>
<subj-group>
<subject>Physical Sciences</subject>
<subj-group>
<subject>Chemistry</subject>
</subj-group>
</subj-group>
-->
<!ELEMENT subj-group (subject+, subj-group*) >
<!-- 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).
subj-group-type
Identification of the subject, information
class, or type of this particular subject
group -->
<!ATTLIST subj-group
%subj-group-atts; >
<!-- SUBJECT GROUPING NAME ELEMENTS -->
<!-- Elements that may be used, along with data
characters inside the content model of the
<subject> element -->
<!ENTITY % subject-elements
"| %emphasis.class; | %inline-display.class; |
%inline-math; | %subsup.class;" >
<!-- SUBJECT GROUPING NAME -->
<!-- The name of one of the subject groups used
to describe an article. Such groups are
used, typically, to provide headings for
groups of articles in a printed or online
generated Table of Contents. -->
<!ELEMENT subject (#PCDATA %subject-elements;)* >
<!-- ============================================================= -->
<!-- SERIES INFORMATION -->
<!-- ============================================================= -->
<!-- GROUPING ARTICLES IN SERIES
Series (as used in the <series-title> and
<series-text> elements described below) is
used in two different senses. Some issues of
journals are part of a series and will have
series information just as they have an
issue number as part of the article metadata,
to describe the issue of the journal in which
the article is published. The second usage
is for groupings of articles within one
issue of a journal. For example, in some
journals, articles are grouped into a
series such as "From the Cover" and
identified as part of a series.
The Series Title element names the series
and the Series Text element provides textual
description (if any) describing the series.-->
<!-- SERIES TITLE -->
<!-- Title of the journal series (bibliographic
meaning) or the title of a series of
articles internal to one issue of a journal
-->
<!ELEMENT series-title (#PCDATA %rendition-plus;)* >
<!-- SERIES TEXT: HEADER TEXT to DESCRIBE -->
<!-- Textual description of the series of articles
that are named in a <series-title> element -->
<!ELEMENT series-text (#PCDATA %rendition-plus;)* >
<!-- ============================================================= -->
<!-- TOP-LEVEL ARTICLE METADATA CONTINUED -->
<!-- ============================================================= -->
<!-- AUTHOR NOTE GROUP -->
<!-- Footnotes to authors or notes about authors
(and, potentially other contributors) are
collected in the Author note group.
References to these footnotes are made
using the <xref> element. -->
<!ELEMENT author-notes
(title?, (corresp | fn)+) >
<!-- id Unique identifier so that the note group
may be referenced, for example by an author
rid May be used to point to an author, if the
source has recorded connections in both
directions -->
<!ATTLIST author-notes
id ID #IMPLIED
rid IDREFS #IMPLIED >
<!--ELEM volume Defined in %common.ent; -->
<!--ELEM issue Defined in %common.ent; -->
<!--ELEM supplement Defined in %common.ent; -->
<!--ELEM fpage Defined in %common.ent; -->
<!--ELEM lpage Defined in %common.ent; -->
<!--ELEM elocation-id Defined in %common.ent; -->
<!--ELEM ext-link Defined in %common.ent; -->
<!--ELEM lpage Defined in %common.ent; -->
<!-- ============================================================= -->
<!-- PRODUCT REVIEW INFORMATION (PRODUCT METADATA) -->
<!-- ============================================================= -->
<!-- PRODUCT ELEMENTS -->
<!-- Elements that may be used inside the
<product> element -->
<!ENTITY % product-elements
"| %break.class; | %link.class; |
%references.class; | %simple-text;" >
<!-- PRODUCT INFORMATION -->
<!-- Used as a wrapper for metadata for a product
(such as a book, software package, hardware
component, website etc.) that is being
reviewed.
Authoring and Conversion Note: This element
should be used when the value of the
"article-type" attribute on the element
<article> is "book-review" or
"product-review".
Authoring and Conversion Note: A review of
a book, journal, website, etc. should
include as much information about the item
being reviewed as is practical, for example:
<product>
<name>
<surname>Lapeyre</surname>
<given-names>Deborah A.</given-names>
</name>
<name>
<surname>Usdin</surname>
<given-names>B. Tommie</given-names>
</name>
<source>Wildflowers of the
Washington Area</source>
<year>2002</year>
<publisher-name>Lippman Ltd.
</publisher-name>
<publisher-loc>Bethesda, MD
</publisher-loc>
<isbn>0-23-8675-309</isbn>,
includes a CD-ROM,
<bold>$19.95</bold> (Used 12.50 when
available)
</product>
-->
<!ELEMENT product (#PCDATA %product-elements;)* >
<!-- product-type
Type of product being reviewed, for example:
book, software package, journal or journal
issue, website, film, hardware component,
etc.
xlink:href Provides an address or identifier of the
object to which the link points, for
example a URI or a filename -->
<!ATTLIST product
%product-atts; >
<!-- ============================================================= -->
<!-- PUBLICATION HISTORY ELEMENTS -->
<!-- ============================================================= -->
<!-- HISTORY: DOCUMENT HISTORY -->
<!-- Used as a container for dates related to the
processing history of the document, such as
received date and accepted date.
Authoring and Conversion Note: The dates
inside the <history> element are used to
preserve events other than publication dates
in the lifecycle of the article. Publication
dates are considered to be an important
part of the metadata. History dates include
accepted date, received date, reviewed
date, and other dates that may be important
to the publisher but are not a likely part
of the article metadata for searching,
building a DOI, etc. -->
<!ELEMENT history (date+) >
<!-- ============================================================= -->
<!-- FURTHER METADATA ELEMENTS -->
<!-- ============================================================= -->
<!-- COPYRIGHT YEAR -->
<!-- Year of the copyright. Need not be used, if,
for example, having the year as part of the
copyright statement is sufficient.
Note: since Copyright Statement is intended
for display, Copyright Year is not expected
to be displayed (but will be available for
searching). -->
<!ELEMENT copyright-year
(#PCDATA) >
<!-- URI FOR THIS SAME ARTICLE ONLINE -->
<!-- Sometimes an article is available in several
forms, for example there is the version that
was published in print and there is the same
article (possibly expanded or with different
graphics) available online.
The URI (such as a URL) may be used as a
live link, typically naming a website or the
element content may name the URL, e.g., and
use the link attributes to hold the real link:
<self-uri xlink:href="...">An expanded
version of this article is available
online</self-uri> -->
<!ELEMENT self-uri (#PCDATA) >
<!ATTLIST self-uri
%might-link-atts; >
<!--ELEM related-article
Defined in %common.ent; -->
<!-- ============================================================= -->
<!-- ABSTRACTS -->
<!-- ============================================================= -->
<!-- ABSTRACT MODEL -->
<!-- Content model for an <abstract> element -->
<!ENTITY % abstract-model
"%sec-opt-title-model;" >
<!-- ABSTRACT -->
<!ELEMENT abstract (%abstract-model;) >
<!-- abstract-type
What type of abstract, for the various
styles of abstracts that publishers
identify, such as:
ASCII Without special characters or
equations so it can be sent in
email or displayed on primitive
browsers
executive-summary
A non-technical summation of
the major findings of the
article
graphical The abstract is a picture
editor For an abstract written by an
editor and not the author
key-points An abstract which is a list of
the key points made by the
document
objectives Used for Learning Objectives
or article objectives
short An abbreviated form of the
abstract, for use, for example
inside a generated Table of
Contents, or to be returned
in addition to the article
title during a search
stereochemical
An abstract containing only
the details of a chemical
compound (For example, the
Elsevier DTD "stereochem"
summary Summation of the article,
typically used in conjunction
with other types of abstracts
teaser A short abstract specifically
written to draw the attention
of the reader
toc A line or two that displays
in a table of contents
web-summary
Short summary intended for
distribution on a website -->
<!ATTLIST abstract
%abstract-atts; >
<!-- TRANSLATED ABSTRACT MODEL -->
<!-- Content model for an <trans-abstract> element
-->
<!ENTITY % trans-abstract-model
"%sec-opt-title-model;" >
<!-- TRANSLATED ABSTRACT -->
<!-- An abstract that has been translated into
another language -->
<!ELEMENT trans-abstract
(%trans-abstract-model;) >
<!-- abstract-type
What type of abstract, for the various
unusual styles of abstracts that publishers
identify, such as "short" abstract, "graphic"
abstract, "ASCII" abstract, "stereochemical"
abstract, etc.
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 trans-abstract
%abstract-atts; >
<!-- ============================================================= -->
<!-- KEYWORD ELEMENTS -->
<!-- ============================================================= -->
<!-- KEYWORD GROUP -->
<!-- Container element for one set of keywords
used to describe a document.
Remarks: A document may have multiple sets
of keywords, each with a source named in
the "kwd-group-type" attribute. -->
<!ELEMENT kwd-group (title?, kwd+) >
<!-- id Unique identifier so the element may be
referenced
kwd-group-type
Name of the source of the keywords, for
example "MESH", "IEEE", "author",
"ICD9-codes", etc.
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 kwd-group
%kwd-group-atts; >
<!--ELEM title Defined in %common.ent; -->
<!-- KEYWORD CONTENT ELEMENTS -->
<!-- The elements that can be included along with
data characters inside the content model of
a keyword. -->
<!ENTITY % kwd-elements
"| %emphasis.class; | %inline-display.class; |
%inline-math; | %simple-link.class; |
%subsup.class;" >
<!-- KEYWORD -->
<!-- One subject term, critical expression, key
phrase, abbreviation, indexing word, etc.
that is associated with the whole document
and can be used for identification and
indexing purposes.
There maybe several sets of keywords,
identified by language or vocabulary source
at the Keyword Group level <kwd-group>.
Conversion Note: Keywords are not allowed to
nest. There are a few journal DTDs in which
keyword nesting is used to simulate a two-
part list. These keyword list should be
tagged as definition lists instead. -->
<!ELEMENT kwd (#PCDATA %kwd-elements;)* >
<!-- id Unique identifier so the element may be
referenced -->
<!ATTLIST kwd
id ID #IMPLIED >
<!-- ============================================================= -->
<!-- STILL FURTHER ARTICLE METADATA -->
<!-- ============================================================= -->
<!-- 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-elements; | %emphasis.class; |
%subsup.class;" >
<!-- CORRESPONDENCE INFORMATION -->
<!-- Optional element, used as a container for
information concerning which of the authors
(or other contributors) is the corresponding
contributor, to whom information requests
should be addressed.
A cross-reference element may point to the
identifier attribute. -->
<!ELEMENT corresp (#PCDATA %corresp-elements;)* >
<!-- id Unique identifier, so the element can be
referenced -->
<!ATTLIST corresp
id ID #IMPLIED >
<!-- PUBLICATION DATE -->
<!-- Date of publication or release of the
material in one particular format. Inside
the article metadata, the Publication Date
is allowed to repeat, and each date can take
a "pub-type" attribute to distinguish
which form of release or publication. -->
<!ELEMENT pub-date (%date-model;) >
<!-- Used to record the type of publication, that
was released or published on this date, for
example a print-only publication versus
an electronic-only publication, in any of
several life stages.
Suggested values include:
epub - Electronic publication
ppub - Print publication
epub-ppub - Published in both print and
electronic form
epreprint - Electronic preprint
dissemination
ppreprint - Print preprint dissemination
ecorrected - Corrected in electronic
pcorrected - Corrected in print
eretracted - Retracted in electronic
pretracted - Retracted in print -->
<!ATTLIST pub-date
%pub-date-atts; >
<!-- ============================================================= -->
<!-- CONTRACT/GRANT INFORMATION ELEMENTS -->
<!-- ============================================================= -->
<!-- CONTRACT/GRANT NUMBER ELEMENTS -->
<!-- The elements that can be included along with
data characters inside the content model of
the contract number. -->
<!ENTITY % contract-elements "| %simple-text;" >
<!-- CONTRACT/GRANT NUMBER -->
<!-- Contract or grant number of the supported
work described in the article.
Authoring Conversion Note: If an acronym of
the sponsor is available, it should be
inserted before the number. -->
<!ELEMENT contract-num
(#PCDATA %contract-elements;)* >
<!-- CONTRACT/GRANT SPONSOR ELEMENTS -->
<!-- The elements that can be included along with
data characters inside the content model of
the contract sponsor. -->
<!ENTITY % contract-sponsor-elements
"| %simple-text;" >
<!-- CONTRACT/GRANT SPONSOR -->
<!-- Name of the organization that sponsored the
work described in the article.
proceedings. -->
<!ELEMENT contract-sponsor
(#PCDATA %contract-sponsor-elements;)* >
<!-- ============================================================= -->
<!-- CONFERENCE INFORMATION ELEMENTS -->
<!-- ============================================================= -->
<!-- CONFERENCE MODEL -->
<!ENTITY % conference-model
"(%conference.class;)*" >
<!-- CONFERENCE INFORMATION -->
<!-- The container element for the information
about a single conference and its
proceedings.
Design Note: Conference elements were largely