-
Notifications
You must be signed in to change notification settings - Fork 0
/
common.ent
1609 lines (1380 loc) · 85.9 KB
/
common.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: Common (Shared) Elements Module -->
<!-- VERSION: 1.0 -->
<!-- DATE: December 2002 -->
<!-- -->
<!-- ============================================================= -->
<!-- ============================================================= -->
<!-- PUBLIC DOCUMENT TYPE DEFINITION -->
<!-- TYPICAL INVOCATION -->
<!--
"-//NLM//DTD Archiving and Interchange DTD Suite Common (Shared) Elements Module v1.0 20021201//EN"
Delivered as file "common.ent" -->
<!-- ============================================================= -->
<!-- ============================================================= -->
<!-- SYSTEM: Archiving and Interchange DTD Suite -->
<!-- -->
<!-- PURPOSE: Defines the common parameter entities, calls the -->
<!-- shared modules (such as special characters and -->
<!-- notations) and provides declarations for elements -->
<!-- that do not properly fit into one class, since -->
<!-- they can be used at more than one structural level-->
<!-- -->
<!-- CONTAINS: 1) Default classes for elements defined in this -->
<!-- module. May be overridden by values in the -->
<!-- DTD's Customization Module -->
<!-- 2) Parameter Entities for attribute values -->
<!-- 3) Parameter Entities for content models -->
<!-- 4) Parameter Entities for attribute lists -->
<!-- 5) Elements used in many modules/classes -->
<!-- - Address elements -->
<!-- - Date elements -->
<!-- - Personal name elements -->
<!-- - Common metadata elements (shared by both -->
<!-- article metadata and bibliographic -->
<!-- reference metadata -->
<!-- -->
<!-- MODULES REQUIRED: -->
<!-- 1) Standard XML Special Characters Module -->
<!-- (%xmlspecchars.ent;) -->
<!-- 2) Custom XML Special Characters (%chars.ent;) -->
<!-- 3) Notation Declarations (%notat.ent;) -->
<!-- -->
<!-- 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: -->
<!-- archive-dtd@ncbi.nlm.nih.gov -->
<!-- -->
<!-- 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)
=============================================================
Version 1.0 Changes Before Public Release
(Lapeyre) V1.0 (2002-12-25)
1. ETAL - Changed the content model of <etal> to replace the
entier content model with a Parameter Entity, not just name some
elements that may mix with #PCDATA. Rationale: The Authoring DTD
would like to make <etal> EMPTY. -->
<!-- ============================================================= -->
<!-- PARAMETER ENTITY DEPENDENCIES
Requires the following parameter entities
be defined before calling this module,
usually accomplished in the Customization
Module for the specific DTD:
%address-elements;
%break.class;
%emphasis.class;
%ext-links.class;
%inline-display.class;
%just-rendition;
%label.class;
%link.class;
%para-level;
%references.class;
%rendition-plus;
%sec-back-matter-elements;
%sec-level;
%sec-opt-title-model;
%simple-link.class;
%simple-phrase;
%simple-text;
%subsup.class;
%might-link-atts; -->
<!-- ============================================================= -->
<!-- ============================================================= -->
<!-- DEFAULT CLASSES FOR ELEMENTS IN COMMON -->
<!-- ============================================================= -->
<!-- ACCESSIBILITY CLASS ELEMENTS -->
<!-- Elements added to make it easier to process
journal articles in ways that are more
accessible to people and devices with special
needs, for example the visually handicapped.
<alt-text> is a short phrase description of
an objects, <long-desc> is a more complete
description of the content or intent of an
object, and the <ext-link> in this grouping
would point to an alternate form of the
object. -->
<!ENTITY % access.class "alt-text | ext-link | long-desc" >
<!-- ADDRESS CLASS ELEMENTS -->
<!-- Potential element components of an address;
not a proper class -->
<!ENTITY % address-elements
"addr-line | country | email | fax |
institution | phone | uri" >
<!-- ADDRESS ELEMENTS INSIDE A PARAGRAPH -->
<!-- Address elements that are allowed loose inside
a paragraph -->
<!ENTITY % inpara-address
"email" >
<!-- MODELS FOR NAMES OF INDIVIDUALS CLASS -->
<!ENTITY % person-name.class
"given-names | surname | suffix" >
<!-- CITATION CLASS ELEMENTS -->
<!-- Reference to an external document, as used
within, for example, the text of a
paragraph -->
<!ENTITY % citation.class
"citation" >
<!-- CONFERENCE CLASS -->
<!-- The element components of the description
of a conference; not a proper class -->
<!ENTITY % conference.class
"conf-date | conf-name | conf-num |
conf-loc | conf-sponsor | conf-theme |
conf-acronym" >
<!-- LABEL CLASS -->
<!-- The label element, used to hold the number
or character of a labeled object such as a
table or footnote -->
<!ENTITY % label.class "label" >
<!-- PERSONAL NAMES CLASS -->
<!-- The element components of a person's name,
for the name of a contributor -->
<!ENTITY % person-name.class
"given-names | prefix | surname | suffix" >
<!-- ============================================================= -->
<!-- PARAMETER ENTITIES FOR ATTRIBUTE VALUES -->
<!-- ============================================================= -->
<!-- HISTORY DATE TYPES -->
<!-- The <history> element contains one or more
<date> elements that record events in the
life of a publication.
date-type Attribute should only be used if the date
is one of the known types; otherwise omit
the attribute.
Values are:
accepted - Date manuscript was
accepted
received - Date manuscript received
rev-request - Date revisions were
requested or manuscript
was returned
rev-recd - Date revised manuscript
was received -->
<!ENTITY % date-types "accepted | received | rev-request |
rev-recd" >
<!-- ARTICLE/PUBLICATION IDENTIFIER TYPES -->
<!-- The "pub-id-type" attribute 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 <pub-id> 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 for
the article
medline- NLM Medline identifier
other - None of the named identifiers
pii - Publisher Item Identifier, see
/epub/piius.htm
pmid - PUBMED ID (see
www.ncbi.nlm.nih.gov/entrez/
query.fcgi?db=PubMed)
publisher-id -
Publisher's identifying number
such as an 'article-id', 'artnum',
'identifier', 'article- number',
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. -->
<!ENTITY % pub-id-types "coden | doi | medline | other | pii |
pmid | publisher-id | sici" >
<!-- ============================================================= -->
<!-- PARAMETER ENTITIES FOR COMMENT MODELS -->
<!-- ============================================================= -->
<!-- DATE ELEMENTS MODEL -->
<!-- The content models for elements that describe
dates, such as Publication Date <pub-date>
and History Dates <date>. The <string-date>
element holds dates for which months and
years are not given, for example "first
quarter", "spring", etc. -->
<!ENTITY % date-model "(((day?, month?) | season)?,
year?, string-date?)" >
<!-- CONTENT MODEL FOR A STRUCTURAL SECTION -->
<!-- The model for a section that requires that a
section title be present, used for elements
such as Section and Appendix. -->
<!ENTITY % sec-model "label?, title, (%para-level;)*,
(%sec-level;)*,
(%sec-back-matter-elements;)*" >
<!-- 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
"label?, title?, (%para-level;)*,
(%sec-level;)*,
(%sec-back-matter-elements;)*" >
<!-- LINK ELEMENTS -->
<!-- Elements for use in the linking elements
such as <xref>, <target>, and <ext-link> -->
<!ENTITY % link-elements
"| %emphasis.class; | %subsup.class;" >
<!-- ARTICLE TITLES ELEMENTS -->
<!-- Elements for use in all the title elements
such as <title>, <subtitle>, <trans-title>,
etc. -->
<!ENTITY % title-elements
"| %break.class; | %simple-phrase;" >
<!-- ============================================================= -->
<!-- PARAMETER ENTITIES FOR LINKING ATTRIBUTES -->
<!-- ============================================================= -->
<!-- XLINK LINK ATTRIBUTES -->
<!-- Used for elements that are a link by
definition, such as the <xref> element.
xlink:href Provides an address or identifier of the
object to which the link points, for
example a URI or a filename
xlink:role Provides a URI reference pointing to some
resource that describes the role or function
of this link
xlink:title
Describes the meaning of the link in a
human-readable and displayable fashion
xlink:show Describes the requested presentation when
the link is traversed.
Values are:
embed Load the new presentation in the
place of the link
new Load a new window, frame, pane, or
other presentation
none No clue for the application
other Look to other markup for a clue
replace Load the new resource in the same
window, frame, pane, or other
presentation context as the link
started in
xlink:actuate
When is the link traversed, and under whose
control.
Values are:
none No clue for the application
onLoad Traverse the link immediately
upon loading the link
onRequest
User or software requests that the
link be traversed
other Look to other markup for a clue
-->
<!ENTITY % link-atts
"xmlns:xlink CDATA #FIXED
'http://www.w3.org/1999/xlink'
xlink:type (simple) #FIXED 'simple'
xlink:href CDATA #REQUIRED
xlink:role CDATA #IMPLIED
xlink:title CDATA #IMPLIED
xlink:show (embed | new | none | other | replace)
#IMPLIED
xlink:actuate
(none | onLoad | onRequest | other)
#IMPLIED" >
<!-- 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 #FIXED
'http://www.w3.org/1999/xlink'
xlink:type (simple) #FIXED 'simple'
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" >
<!-- ============================================================= -->
<!-- PARAMETER ENTITIES FOR ATTRIBUTES LISTS -->
<!-- ============================================================= -->
<!-- AFFILIATION ATTRIBUTES -->
<!-- Attributes for the Affiliation <aff>
element -->
<!ENTITY % aff-atts
"id ID #IMPLIED
rid IDREFS #IMPLIED" >
<!-- COLLABORATION ATTRIBUTES -->
<!-- Attributes for <collab> -->
<!-- collab-type
The type or role of the collaborators,
what function did they play in the
publication.
Suggested values include:
assignee
- Group or company to whom a patent
is awarded
authors - Content creators
editors - Content editors
compliers
- Put together a composite work
from multiple sources
guest-editors
- A group of editors that have been
invited to edit all or part of a
work
inventors
- Idea, software, or machine
creators
translators
- Translated the cited work from
one language into another
id unique identifier so that the collaboration
can be referenced
xlink:href Provides an address or identifier of the
object to which the link points, for
example a URI or a filename
-->
<!ENTITY % collab-atts
"collab-type
CDATA #IMPLIED
id ID #IMPLIED
%might-link-atts;" >
<!-- EXTERNAL LINK ATTRIBUTES -->
<!-- Attribute list for external links
ext-link-type
Type of external link. Use this attribute
if the type of external link is one of the
ones below or another named type.
Suggested values include:
ec Enzyme nomenclature - see
http://www.chem.qmw.ac.uk/iubmb/enzyme/
gen GenBank identifier
genpept Translated Protein-encoding
sequence Database
highwire HighWire press intrajournal
medline Medline or pubmed id
pdb Protein data bank. See
http://www.rcsb.org/pdb/
pgr Plant gene register. See
http://www.tarweed.com/pgr/
pir Protein Information Resource
see http://pir.georgetown.edu
pirdb Protein Information Resource
see http://pir.georgetown.edu
pmc Used to link between articles
in PubMedCentral access is
PMID
sprot Swiss-Prot. See
http://www.ebi.ac.uk/swissprot/
aoi Astronomical Object Identifier
doi Digital Object Identifier
ftp File transfer protocol
uri Website or web service
xlink:href Provides an address or identifier of the
object to which the link points, for
example a URI or a filename -->
<!ENTITY % ext-link-atts
"ext-link-type CDATA #IMPLIED
%might-link-atts;" >
<!-- CITATION ATTRIBUTES -->
<!-- Attributes for <citation>
citation-type
Defines the type of work being referenced.
Suggested values include:
book Book
conf-proceedings
Conference proceedings
discussion Dicussion among a group in
some forum - public, private,
or electronic, which may or
may not be moderated
gov Government publication
journal Journal article
list Listserv
other None of the listed types
patent Patent or patent application
personal-communication
Informal or personal
communication, such as a
phone call or an email
message
standard Standards document issued by
a recognized standards body,
such as ISO, ANSI, IEEE,
OASIS, etc.
thesis Work written as part of the
completion of an advanced
degree
web Website
id Unique identifier so the element may be
referenced
xlink:href Provides an address or identifier of the
object to which the link points, for
example a URI or a filename -->
<!ENTITY % citation-atts
"citation-type
CDATA #IMPLIED
id ID #IMPLIED
%might-link-atts;" >
<!-- ISSN ATTRIBUTES -->
<!-- Attribute list for <issn> -->
<!-- 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 % issn-atts
"pub-type CDATA #IMPLIED" >
<!-- NOTE ATTRIBUTES -->
<!-- Attribute list for <note> -->
<!-- notes-type To identify the type of note, if the type can
be/has been identified, for example,
"note-in-proof" -->
<!ENTITY % notes-atts
"notes-type CDATA #IMPLIED" >
<!-- RELATED ARTICLE ATTRIBUTES -->
<!-- Attributes for <related-article>
related-article-type
addendum Additional material for an
article, generated too late
to be added to the main text
commentary-article
Used in an commentary or
editorial to link to the
article on which it is
commenting
companion Used in an article to link
to a companion (related
or sibling) article
corrected-article
Used in a correction to link
to the article being
corrected. Sometimes called
erratum.
in-this-issue Related article in the same
journal issue
letter A letter to the publication
or a reply to such a
letter
commentary Used in an article to link
to its associated commentary
or editorial
correction-forward
Used in an article to link
forward to its associated
correction (rarely used)
retracted-article
Used in a retraction to link
to the article being retracted
retraction-forward
Used in an article to link
forward to its associated
retraction (rare)
vol Volume of the journal in which the related
article exists. It is best practice to
limit the scope to the current journal,
the one in which the current article
resides.
page Page number of the related article. It is
best practice to limit the scope to the
current journal, the one in which the
current article resides. The values for this
attribute should be a first page or a page
range.
xlink:href Provides an address or identifier of the
object to which the link points, for
example a URI or a filename. -->
<!ENTITY % related-article-atts
"related-article-type
CDATA #REQUIRED
vol CDATA #IMPLIED
page CDATA #IMPLIED
%might-link-atts;" >
<!-- BIOGRAPHY ATTRIBUTES -->
<!-- Attributes for <bio> element
id Unique identifier so the element may be
referenced
rid Points to the identifier of an author or
or authors
xlink:href Provides an address or identifier of the
object to which the link points, for
example a URI or a filename. -->
<!ENTITY % bio-atts
"id ID #IMPLIED
rid IDREFS #IMPLIED
%might-link-atts;" >
<!-- ============================================================= -->
<!-- ELEMENT USED BY MORE THAN ONE CLASS -->
<!-- ============================================================= -->
<!-- ============================================================= -->
<!-- COMMON METADATA/BIBLIOGRAPHIC ELEMENTS -->
<!-- ============================================================= -->
<!-- ARTICLE TITLE -->
<!-- The title of the article in the language
in which the article was originally
published
Remarks: The related element Translated Title
<trans-title> should be used for a
translation of the article into another
language, for example, to hold the English
version of a Japanese article title. -->
<!ELEMENT article-title
(#PCDATA %title-elements;)* >
<!-- 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 article-title
xml:lang NMTOKEN #IMPLIED >
<!-- AFFILIATION ELEMENTS -->
<!-- Elements for use in the <aff> element -->
<!ENTITY % aff-elements "| %address-elements; | %break.class; |
%emphasis.class; | %link.class; |
%subsup.class;" >
<!-- AFFILIATION -->
<!-- Name of a institution or organization such as
a university or corporation.
Authoring and Conversion Note: In a typical
case, the "id" attribute will be pointed to
by one or more contributors.
Conversion Note: Any explicitly tagged numbers
or symbols for author linkages should be
discarded, as the linkage will be recreated
from the "id" connection. -->
<!ELEMENT aff (#PCDATA %aff-elements;)* >
<!-- id Unique identifier so that the affiliated
institution may be referenced, for example
by a contributor
rid May be used to point to affiliation-related
information within the document
-->
<!ATTLIST aff
%aff-atts; >
<!-- COLLABORATIVE (GROUP) AUTHOR ELEMENTS -->
<!-- Elements for use in the <collab> element -->
<!ENTITY % collab-elements
" | %ext-links.class; | %simple-link.class; |
%simple-text;" >
<!-- COLLABORATIVE (GROUP) AUTHOR -->
<!-- Used for groups of authors credited under
one name, either as a collaboration in the
strictest sense, or when an organization,
institution, or corporation is the group.
Remarks: When an author is an organization
rather than a person, use the <collab>
element rather than <surname>, for
example:
<collab>Aardvark Institute</collab>
-->
<!ELEMENT collab (#PCDATA %collab-elements;)* >
<!-- collab-type
The type or role of the collaborators,
what function did they play in the
publication.
Suggested values include:
assignee
- Group or company to whom a patent
is awarded
authors - Content creators
editors - Content editors
compliers
- Put together a composite work
from multiple sources
guest-editors
- A group of editors that have been
invited to edit all or part of a
work
inventors
- Idea, software, or machine
creators
translators
- Translated the cited work from
one language into another
one language into another
id unique identifier so that the collaboration
can be referenced
xlink:href Provides an address or identifier of the
object to which the link points, for
example a URI or a filename. -->
<!ATTLIST collab
%collab-atts; >
<!-- CONFERENCE DATE -->
<!-- The date(s) on which the conference was held.
Conference dates in journal headers are
traditionally stored in one of two forms:
as a single date ("May 1906") or as the
first day and last day of the conference.
Both types should be stored in this element;
the dates that come from separate first and
last elements should be combined:
<conf-start>August 4, 2002</conf-start>
<conf-end>August 9, 2002<conf-end>
should become:
<conf-date>August 4, 2002 - August 9,
2002</conf-date>
-->
<!ELEMENT conf-date (#PCDATA) >
<!-- CONFERENCE LOCATION ELEMENTS -->
<!-- Elements for use in the <conf-loc> element -->
<!ENTITY % conf-loc-elements
"| %simple-text;" >
<!-- CONFERENCE LOCATION -->
<!-- The physical location(s) of the conference.
This may include a city, a country, or a
campus or organization location if that is
the only location available.
Authoring and Conversion Note: If the
conference is in the United States, the
state should also be provided. A specific
venue or address (e.g. conference hotel)
should not be provided unless there is no
other location information. -->
<!ELEMENT conf-loc (#PCDATA %conf-loc-elements;)* >
<!-- CONFERENCE NAME ELEMENTS -->
<!-- Elements for use in the <conf-name> element-->
<!ENTITY % conf-name-elements
"| %simple-text;" >
<!-- CONFERENCE NAME -->
<!-- The full name of the conference, including any
qualifiers such as "43rd Annual". When the
name includes the year of the conference,
(e.g. "Extreme 2002"), the year should appear
in both the conference Name and the Conference
Date elements. -->
<!ELEMENT conf-name (#PCDATA %conf-name-elements;)* >
<!-- COPYRIGHT STATEMENT -->
<!-- Copyright notice or statement, suitable for
printing or display. Within the statement the
copyright year should be identified, if
expected to be displayed. -->
<!ELEMENT copyright-statement
(#PCDATA %rendition-plus;)* >
<!-- ISSN -->
<!-- International Standard Series Number -->
<!ELEMENT issn (#PCDATA) >
<!-- Used to record the type of publication, for
which this ISSN was issued, 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 issn
%issn-atts; >
<!-- ISSUE -->
<!-- The issue number, issue name, or other
identifier of an issue of a journal -->
<!ELEMENT issue (#PCDATA %just-rendition;)* >
<!-- ============================================================= -->
<!-- COMMON METADATA ELEMENTS CONTINUED -->
<!-- PUBLISHER IDENTIFICATION ELEMENTS -->
<!-- (COMMON ARTICLE METADATA/BIBLIOGRAPHIC) -->
<!-- Used in article metadata and also inside -->
<!-- a bibliographic reference (citation) -->
<!-- ============================================================= -->
<!-- ET AL CONTENT MODEL -->
<!-- The content model for the <etal> element -->
<!ENTITY % etal-model "(#PCDATA %just-rendition;)*" >
<!-- ET AL -->
<!-- Although most journals modeled this as an
EMPTY element, typically used to generate
the text "et al." in a stylesheet, some
journal DTDs (Blackwell's, for example) expect
content for this element, with such text as
"Associates, coworkers, and colleagues". -->
<!ELEMENT etal %etal-model; >
<!-- PUBLISHER'S NAME -->
<!-- Name of the publisher of the work -->
<!ELEMENT publisher-name
(#PCDATA %just-rendition;)* >
<!-- PUBLISHER'S LOCATION ELEMENTS -->
<!-- Elements for use in the Publisher Location
<publisher-loc> element -->
<!ENTITY % publisher-loc-elements
"| %address-elements; | %emphasis.class; |
%subsup.class;" >
<!-- PUBLISHER'S LOCATION -->
<!-- Place of publication, usually a city such
as New York or London -->
<!ELEMENT publisher-loc
(#PCDATA %publisher-loc-elements;)* >
<!-- ============================================================= -->
<!-- COMMON METADATA ELEMENTS CONTINUED -->
<!-- ============================================================= -->
<!-- TRANSLATED TITLE -->
<!-- An alternate version of the title that has
been translated into a language other than
that of the article title <article-title>
Remarks: The related element Article Title
<atitle-title> should be used for the title
of the article in the original language in
which it was published, this element used
for a translation of that title, for example
the English version of a Japanese article. -->
<!ELEMENT trans-title (#PCDATA %title-elements;)* >
<!-- 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).
Authoring and Conversion Note: For the
Translated Title element, the xml:lang
attribute should always be set if the
value is known. The only reason the
attribute was not made #REQUIRED was that
there may be cases where the language is
not known. -->
<!ATTLIST trans-title
xml:lang NMTOKEN #IMPLIED >
<!-- VOLUME -->
<!ELEMENT volume (#PCDATA %just-rendition;)* >
<!-- ============================================================= -->
<!-- COMMON METADATA ELEMENTS CONTINUED -->
<!-- PAGE NUMBERING ELEMENTS -->
<!-- ============================================================= -->
<!-- FIRST PAGE -->
<!-- The page number on which the article starts,
for print journals that have page numbers -->
<!ELEMENT fpage (#PCDATA) >
<!-- seq Used for sequence number or letter for
journals (such as continuous makeup journals)
with more than one article starting on the
same page -->
<!ATTLIST fpage
seq CDATA #IMPLIED >
<!-- LAST PAGE -->
<!-- The page number on which the article ends,
for print journals that have page numbers -->
<!ELEMENT lpage (#PCDATA) >
<!-- ELECTRONIC LOCATION IDENTIFIER -->
<!-- Used to identify an article that
does not have traditional page numbers.
For a printed article, when citations are
sent through the Medline matcher to be turned
into live links or when the metadata about an
article is collected for complete
identification, the first page number (and
sometimes also the last page number) of the
article is recorded to help indicate which
article is being referenced. Electronic only
journals have no page numbers, so this
element is used as the equivalent identifier,
the "electronic page number" that helps to
identify the article. The value could be an
article identifier, a doi, etc., for
example, "E70".
Remarks: This element is more accurately an
electronic identifier, and it was considered
renaming this element to that. The purpose
of the name is to be a parallel with the
<fpage>...<lpage> model. When neither first
page or last page is appropriate, because
the electronic journal has no pages, the
<elocation-id> element is used instead. -->
<!ELEMENT elocation-id (#PCDATA) >
<!-- ============================================================= -->
<!-- CITATION (BIBLIOGRAPHIC REFERENCE) -->