Metadata
Product ID: "productID"
Article status: ""
MedLine journal title: ""
Content type: ""
Special issue: "yes" (title "This is a Special Issue Title")
Article URL: ""
Volume number: "2"
Issue number: "3" (sequence "1") (in press "")
Page range: "12" - "15" (total "")
PDF file: "" (size "") (pages "")
Full text link: ""
Colour graphics: "no"
Audience: "" (secondary "")
Reference style: "Math"
journalcode
:
XYZ
issn [type='print' ]
:
0092-1234
issn [type='electronic' ]
:
1532-9876
coden
:
Coden text
sici
:
A-999
pubitemid
:
S0001-9999(00)00100-3
pubmedabbrev
:
PUBMED Abbreviation
author [primaryauthor='yes' corresponding='yes' seq='1' ]
:
name
:
HonorificPrefixGivennameASurnameSuffixDegree1Degree2
Query Q0001: This a query requesting a correction to the author's name.
contactinfo
:
contact [corresponding='no' postpub='no' biocontact='no' ]
:
Contact Address Line OneContact Address Line TwoContact CityContact StateZip CodeContact Country+99 (0) 123 456 7890 +99 (0) 123 456 7899
[email protected]www.SecondContact.orgAdditional Note on Address
bioinfo
:
biography
:
First biography paragraph.
Second biography paragraph.
authornote
:
Author note (type not specified).
authornote [type='member' ]
:
Author note (type: "member" of something).
author [primaryauthor='no' corresponding='no' seq='2' ]
:
name
:
SecondaryAuthor
contactinfo
:
contact [corresponding='no' postpub='no' biocontact='no' ]
:
Contact Address Line OneContact Address Line TwoContact CityContact StateZip CodeContact Country+99 (0) 123 456 7890 +99 (0) 123 456 7899
[email protected]www.SecondContact.orgAdditional Note on Address
Query Q0002: This is a query for correction added to an affiliation USA-formatted address.
affiliations
:
affiliation [id='AFF0001' ]
:
Institution NameDepartment
International Address LineCityPost Code Country
www.detica.comFirst Address NoteSecond Address Note
Query Q0003: This is a query for correction added to an affiliation address.
affiliation [id='AFF0002' ]
:
Another InstitutionUSA CityStateUSA
fundingdetails
:
fundingaward [awardtype='gift' ]
:
Taylor & Francis Group
ABCD
1234
fundingrecipient
:
name
:
Dr.MarkSign
Department of TaggingMetadata University
principalinvestigator
:
name
:
Dr.MarkSign
<-- <relatedmaterial relatedas="followup" relationtype="errata" articleid="262358" doi="10.1080/10428190701625081">
<ref-periodic id="REL0001"><authorfield><author-ref><surname>Au</surname>
<givenname>Wing-Yan</givenname></author-ref><author-ref><surname>Tam</surname>
<givenname>Sidney</givenname></author-ref><author-ref><surname>Fong</surname>
<givenname>Bonnie</givenname><middlename>M.</middlename></author-ref><author-ref><etal />
</author-ref></authorfield><articletitle>Prolonged oral arsenic trioxide therapy and neprholithiasis</articletitle>
<journaltitle>Leukemia and Lymphoma</journaltitle><periodicpubfield><year>2007</year>
<volume>48</volume><issue>11</issue></periodicpubfield><pagefield><firstpage>2233</firstpage>
<lastpage>2234</lastpage></pagefield><doi>10.1080/10428190701625081</doi></ref-periodic>
<relationnote>While we don't like to have errata, they sometimes are needed.</relationnote>
</relatedmaterial> -->
supplementmaterial [id='suppmat1' contenttype='video' doi='10.1234/XXX-123456789-suppmat1' freedownload='no' attachtoissue='no' ]
:
search
:
MajorCategoryKeyword
PrimarySubCategoryKeyword
SubCategoryKeyword
SecondSubCategoryKeyword
TopicKeyword
SubTopicKeyword
AnotherSubTopicKeyword
production-dates [receiveddate='01Jan2004' reviseddate='Mar2004' acceptdate='2004' qaapprovdate='04Apr2004' finalapprovdate='05May2004' webpubdate='06Jun2004' projectedprintpubdate='07Jul2004' printpubdate='07Jul2004' ]
:
This is a comment. Such comments in this test article will be used where it is not feasible to put self-describing text into a structure.
This is a comment about the metadata. Several comments can appear, but only at the end of the metadata section
This article XML last modified: $Date: 2011-10-28 09:35:10 -0400 (Fri, 28 Oct 2011) $ $Rev: 895 $
Givenname A. Surname and Secondary Author
Part A
Article Structure (Part Title)
Issue number: ""
Article ID: ""
DOI: ""
Type: ""
Year of publication: ""
Colour graphics: "no"
Page range: "" - "" (total "")
Full text link: ""
Sect 1
First Section in Part 1 (Section 1 Title)
Short Section Header
This is a section in the first part of the article.
Issue number: ""
Article ID: ""
DOI: ""
Type: ""
Year of publication: ""
Colour graphics: "no"
Page range: "" - "" (total "")
Full text link: ""
Second Section in Part 1 (Section 1 Title)
This second section contains sub-sections:
Issue number: ""
Article ID: ""
DOI: ""
Type: ""
Year of publication: ""
Colour graphics: "no"
Page range: "" - "" (total "")
Sect 1.2
First Sub-Section (Section 2 Title)
This subsection is the first subsection in the second section of the first part of the article.
The next subsection is the last in this section, but contains further section levels.
Issue number: ""
Article ID: ""
DOI: ""
Type: ""
Year of publication: ""
Colour graphics: "no"
Page range: "" - "" (total "")
Second Sub-Section (Section 2 Title)
This subsection contains three further levels of section, to the maximum possible level of section nesting (5 levels).
A Sub-Sub-Section (title)
This is subsection level three.
A Sub-Sub-Sub-Section (title)
This is subsection level four
A Sub-Sub-Sub-Sub-Section (title)
This is subsection level five. It is not possible to nest sections any further than this. However, headings for one more level could be simulated using bold text in short paragraphs.
Issue number: ""
Article ID: ""
DOI: ""
Type: ""
Year of publication: ""
Colour graphics: "no"
Page range: "" - "" (total "")
Full text link: ""
Inline Elements
This section demonstrates the use of elements that can occur within blocks (such as titles and paragraphs).
Text can be made superscript or subscript. Other styles include overline and strikethrough.
A number of emphasis styles are allowed, including bold, italic, small caps, underline, |box|, roman, monospaced and script.
It is possible to embed an empasis element within another emphasis element, so any combination of styles can be produced, including a bold word in italic phrase, and a subscript word in underlined text, and an italic word in superscript text, among many other combinations.
An image can be inserted inline, as in

, but other image-related elements should be used for special purposes, such as for figures, logos and article author photographs.
When a new page starts in the initial print publication of an article, the location of the page-break is preserved. This text appears at the end of page 2, and ... this text appears at the start of page 3.
A paragraph can be broken into lines using the break elements, in order to include poetry:
line of text one
line of text two
line of text three.
Note that there is a block-level element for computer text that is described later, but it is also possible to include computer code, or other lines of monospaced text, using a mixture of the break element and the monospaced emphasis element, as in :
monospaced line 1
monospaced line 2
Objects in the text can be isolated and identified using the "name" related elements, including famous names, company names and institution names: Einstein, IBM and NASA. A trademark such as Java can be identified. In addition, an acronym such as BBC (British Broadcasting Corporation) can be identified, as well as terms, such as XML. Names can still be identified within styled ranges of text, such as italic text with a famous person (Einstein) within it.
Text may include references to various objects within the same article. There is a different element for references to different kinds of object in the article, including:
chemical equation,
chemical formulae,
chemical structure,
citation,
end note,
figure,
supplementary material,
footnote,
list item,
list,
math equation,
table,
enunciation and
cross (x-ref). These links can contain superscript, subscript and emphasis, such as
link-to-W3C-Web-site.
Issue number: ""
Article ID: ""
DOI: ""
Type: ""
Year of publication: ""
Colour graphics: "no"
Page range: "" - "" (total "")
Full text link: ""
Text Blocks
This section introduces the elements that construct blocks of text, including paragraphs (such as this one).
A paragraph can be indented to various levels (this is level one)
This is level two
This is level three
This is level four
This is level five
Apart from the paragraph elements containing this text, there are also several alternatives, starting with an address:
address line one
address line two
City Name
Country Name
It is not necessary to display an address vertically. Simply leaving out the break-line elements allows for the alternative presentation:
77 Shaftesbury Avenue, London Englandtel: 0001 999 1234 or fax: 0001 999 1235, or email to [email protected] and see the Website at
www.detica.com
Blocks of computer text can be isolated. Each line of the computer text is separated from other lines using the br (break) element:
line of computer text
second line of computer text
third line of computer text
A letter to someone:
A normal paragraph, with bold styling, serves as a title for the letter
salutation
:
Salutation, as in "Dear Sir," with only subscript and superscript allowed.
Paragraph of letter content between salutation and closing.
closing [align='right' ]
:
Closing text - often just a signature (by default "left" aligned, but this time "right" aligned
signature
:
This is my signature (could be a graphic, but if text only subscript and superscript allowed!
An extract from another work:
By default, the extract is part of the main narrative flow, but an attribute can be set to make it an independent "side-box", as in the following example:
Sidebox Title
This extract has a sidebox value of "yes", so it not part of the main narrative flow, and can be floated to any convenient location on a page or screen.
Source of the extract
Poetry can be identified, and individual stanzas and lines of the poem isolated:
poem
:
single line of first stanza,
single line of first stanza,
single line of first stanza,
single line of first stanza
single line of second stanza,
single line of second stanza,
single line of second stanza,
single line of second stanza
But stanza markup is optional, and redundant when there is a single stanza presented. Either way, the source
of the poem can be added at the end:
poem
:
So, although unlisted in atlas or text-book,
Her Garden is easy to find. In no time
one reaches the gait over which is written
large: MAKE PEACE NOT WAR
W.H. Auden, 'Circe'
The questions and answers in an examination can be listed:
exam
:
Q: 1.What is two plus two?
Show workings
A: four
Because one plus one is two, twice!
Q: 2.What is the meaning of life?
An index of simple or complex nature can be included:
index [type='subject' ]
:
Index Title
This is a subject index (not an author or miscellaneous index
The following three entries are not in a group.
Subjects and Compound Entries
simple name
this subject is in the same entry as a simple name.
this entry is a
subject, with a second paragraph.
Second paragraph explaining this subject
See Other Entries
entry with reference
See ...see target entry one
entry with two references
See ...see target entry one
See also ...see also target entry two
Enunciations are identified:
enunciation [id='enunciation1' ]
:
Paragraph in enunciation.
Second paragraph in enunciation.
Finally, a footnote can be defined:
. A symbol is generated automatically and is added to the footnote reference and to the footnote itself in order to link the two.
Issue number: ""
Article ID: ""
DOI: ""
Type: ""
Year of publication: ""
Colour graphics: "no"
Page range: "" - "" (total "")
Old Sidebox
The DTD has not always allowed a title element inside an extract. Two mechanisms have been used to get around this limitation:
| |
|
item
|
Wrap the extract in a section element that contains a title and the extract only.
|
| |
|
item
|
Use text formatting elements to style the first para in bold.
|
The DTD now allows title within extract so these workarounds can be avoided. However, processing software must still support the workarounds for older content.
Issue number: ""
Article ID: ""
DOI: ""
Type: ""
Year of publication: ""
Colour graphics: "no"
Page range: "" - "" (total "")
Full text link: ""
Text Blocks Within Text
A text block, such as an extract, can be placed within a paragraph. When placed at the end of a paragraph, there is no real difference to it appearing immediately after the paragraph, but when placed in the middle of a paragraph, it splits the paragraph into two separate text blocks. However, the first text block in the paragraph might be formatted to indicate that a new paragraph has begun (such as by indeting the first line, and putting vertical space above it), while the second will appear directly below the embedded block, as in the text beneath this extract:
so this text is not really a separate paragraph, but a continuation of the original paragraph above the extracted text.
Issue number: ""
Article ID: ""
DOI: ""
Type: ""
Year of publication: ""
Colour graphics: "no"
Page range: "" - "" (total "")
Full text link: ""
Lists
This section demonstrates the elements that are used to construct lists.
This is a simple paragraph.
A simple (bulleted/random) list consists of a number of items:
| |
|
item
|
Simple list item, containing one paragraph.
|
| |
|
item
|
Longer list item, containing two paragraphs.
This is the second paragraph in the item.
|
| |
|
item
|
As well as paragraphs, an item may contain other block-level elements, including embedded lists:
| |
|
item
|
This list is in the third item of the outer list
|
| |
|
item
|
It consists of two items.
|
There may be any number of lists and paragraphs within a list item.
|
The second kind of list is an itemized list, with a prefix that can be pre-defined using the listitemlabel attribute (in this case set to the value "="):
| |
|
=
|
Itemized list item Three
|
The third kind of list is an ordered (numbered) list. By default, items are numbered using Arabic numerals:
However, this kind of numbering can be made explicit using the numeration attribute:
Alternatively, upper-case letters can be used:
or lowercase:
Roman numerals can also be used:
Lowercase Roman numerals are the final option:
An itemized list may contain multiple paragraphs and embedded lists.
| |
|
(1)
|
First item - single paragraph.
|
| |
|
(2)
|
Second item - embedded simple list:
| |
|
item
|
Simple list item in numbered list.
|
| |
|
item
|
Another simple list item in numbered list.
|
|
A numbered list can contain other numbered lists, and rendering software must not become confused and make mistakes in numbering each outer and inner item:
The third and final kind of list is a definition list, which is useful for glossaries:
| |
|
|
eXtensible Markup Language
|
|
|
eXtensible Stylesheet Language:
| |
|
item
|
XSLT - Transformations
|
| |
|
item
|
XSL-FO - Formatting Objects
|
|
Issue number: ""
Article ID: "999999999"
DOI: ""
Type: ""
Year of publication: ""
Colour graphics: "no"
Page range: "" - "" (total "")
Full text link: ""
Tables
Issue number: ""
Article ID: ""
DOI: ""
Type: ""
Year of publication: ""
Colour graphics: "no"
Page range: "" - "" (total "")
Tables In File "999999999_suppl.xml"
Tables should always now be created as an object (that could be floating).
The "table" element is deprecated, and note that the "tbl" element is the equivalent of
the CALS default "table" element.
<-- TABLE 1 - test basic table structure -->
The following table has no attributes set, so text should appear vertically in the middle,
and left justified (the frame attribute is set to "sides"). It is a "formal" table, and
has a title:
formaltable [id='table1' ]
:
[1]
Title Of Table One - (these titles are optional in formal tables)
col: 1 ('col-1') width: 1*
|
col: 2 ('col-2') width: 1*
|
| Body Rows |
|
cell 1,1
|
cell 1,2
|
|
cell 2,1. A cell is only able to contain a single paragraph of text. There cannot be an embedded table or list.
|
cell 2,2. styles in a table cell include bold, italic, underline, script, smallcaps, subscript and superscript.
|
<-- TABLE 2 - cell alignment tests (align and valign on entry element) -->
The following table tests text alignments, both horizontally and vertically (the frame attribute is set to "topbot"):
informaltable
:
col: 1 ('col-1') width: 1*
|
col: 2 ('col-2') width: 1*
|
col: 3 ('col-3') width: 1*
|
| Body Rows |
|
The cells below this one are aligned horizontally and vertical in all the possible combinations...
|
This column holds a lot of text to help make middle alignments in the first column more obvious.
|
This column is added to help ensure that the second column is narrow enough to force the cell in the first column to occupy at least three lines.
|
|
Middle Left.
|
There is a lot of text here to make sure that this row spans at least three lines, and therefore shows that the middle-left text in the previous cell really is not at the top or bottom of its cell (and is left justified).
|
|
|
Top Left.
|
There is a lot of text here to make sure that this row spans at least three lines, and therefore shows that the top-left text in the previous cell really is at the top of its cell (and is left justified).
|
|
|
Bottom Left
|
There is a lot of text here to make sure that this row spans at least three lines, and therefore shows that the bottom-left text in the previous cell really is at the bottom of its cell (and left justified).
|
|
|
Middle Center
|
There is a lot of text here to make sure that this row spans at least three lines, and therefore shows that the middle-center text in the previous cell really is in the middle (and centered).
|
|
|
Top Center
|
There is a lot of text here to make sure that this row spans at least three lines, and therefore shows that the top-center text in the previous cell really is at the top (and centered horizontally).
|
|
|
Bottom Center
|
There is a lot of text here to make sure that this row spans at least three lines, and therefore shows that the bottom-center text in the previous cell really is at the bottom (and centered horizontally).
|
|
|
Middle Right
|
There is a lot of text here to make sure that this row spans at least three lines, and therefore shows that the middle-right text in the previous cell really is in the middle (and right justified horizontally).
|
|
|
Top Right
|
There is a lot of text here to make sure that this row spans at least three lines, and therefore shows that the top-right text in the previous cell really is at the top (and right justified horizontally).
|
|
|
Bottom Right
|
There is a lot of text here to make sure that this row spans at least three lines, and therefore shows that the bottom-right text in the previous cell really is at the bottom (and right justified horizontally).
|
|
<-- TABLE 3 - cell alignment overriding tests (rov, tbody and colspec) -->
The following table tests overriding text alignments (entry overrides row, which
overrides tbody), both horizontally and vertically (the frame attribute is set to "top"):
informaltable
:
col: 1 ('col-1') width: 1*
|
col: 2 ('col-2') width: 1*
|
col: 3 ('col-3') width: 1*
|
| Body Rows |
|
Right (tgroup element) and Bottom (tbody element).
|
Top (entry element).
|
There is a lot of text here to make sure that
this row spans at least three lines, and therefore shows that the
cell alignments described in the other cells can really be seen to work
as advertised. Quite a lot of text is needed here to ensure that the other cells
will be large enough to show vertical alignments properly. This is the final sentence to
make this cell sufficiently large. Hope this is enough.
|
<-- TABLE 4 - cell alignment on character -->
The following table tests horizontal alignment on a given character ("." and ":"), specified
at the tgroup and colspec levels (also, multiple tgroup elements) (the frame attribute is set to "all"):
informaltable
:
col: 1 ('col-1') width: 1*
|
col: 2 ('col-2') width: 1*
|
| Body Rows |
|
The cells below this one are aligned on decimal point. (align on ".")
|
The cells below this one are also aligned on decimal point,
because the align attribute is on the tgroup element. (align on ".")
|
|
123.4 (align on ".")
|
5.6789 (align on ".")
|
|
12.34 (align on ".")
|
56.789 (align on ".")
|
|
1.234 (align on ".")
|
5677.89 (align on ".")
|
|
1234 (align on ".")
|
56778.9 (align on ".")
|
|
1234.0 (align on ".")
|
567789 (align on ".")
|
col: 1 ('col-1') width: 1*
|
col: 2 ('col-2') width: 1*
|
| Body Rows |
|
Next cell is character aligned on ":"
|
abcde:f (align on ":")
|
|
Next cell is character aligned on ":"
|
abcd:ef (align on ":")
|
|
Next cell is character aligned on ":"
|
abc:def (align on ":")
|
|
Next cell is character aligned on ":"
|
ab:cdef (align on ":")
|
|
Next cell is character aligned on ":"
|
a:bcdef (align on ":")
|
<-- TABLE 5 - row and column spanning cells -->
The following table tests row and column spanning cells, using the morerows attribute
and the namest and nameend attributes (the frame attribute is set to "bottom"):
informaltable
:
col: 1 ('col-1') width: 1*
|
col: 2 ('col-2') width: 1*
|
col: 3 ('col-3') width: 1*
|
| Body Rows |
|
Normal non-spanning cell.
|
Normal non-spanning cell.
|
Normal non-spanning cell.
|
|
Normal non-spanning cell.
|
This cell spans down into the next row, using morerows="1", so should in part occupy the same horizontal space as cells in the next row down.
|
Normal non-spanning cell.
|
|
Normal non-spanning cell.
|
Normal non-spanning cell (there is no entry element for the occupied cell before this one).
|
|
Normal non-spanning cell.
|
Normal non-spanning cell.
|
Normal non-spanning cell.
|
|
Normal non-spanning cell.
|
This cell spans into the next column,
and there is no final entry element in this row. It refers to
the colspec elements for the second and third columns by their names.
|
|
Normal non-spanning cell.
|
Normal non-spanning cell.
|
Normal non-spanning cell.
|
|
This cell spans across and down (it occupies four cells in total)
|
Normal non-spanning cell (and absent entry element before this one).
|
|
Normal non-spanning cell (and absent entry elements before this one).
|
|
Normal non-spanning cell.
|
Normal non-spanning cell.
|
Normal non-spanning cell.
|
Issue number: ""
Article ID: ""
DOI: ""
Type: ""
Year of publication: ""
Colour graphics: "no"
Page range: "" - "" (total "")
Full text link: ""
Images and Media
Figures and other graphics are commonly found in articles.
There is a single inline image element, which is used here to refer to the photograph of the author of this article (Einstein himself)...

. All of the other images are block-level, including the photograph and logo at the top of this article, but also including:
The final place that an image can be referenced is from within a mathematical structure:
[STRUCTURE]
.
Note that the height and width can be set, in this case to 50x20 pixels:

An image that has a title, caption and reference number is really a figure:
figure [articleid='999999999' productid='none' id='figure1' colorgraphics='no' ]
:
[1]
More interesting is the DTD's support for multimedia objects, including video, audio, datasets, and other supplementary material. Supplementary material be tagged as article metadata, or placed in the flow of article text.
supplementmaterial [id='suppmat2' contenttype='video' articleid='999999999' productid='productID' doi='10.1234/XXX-123456789-suppmat2' freedownload='yes' attachtoissue='yes' yearofpub='2010' ]
:
supplementmaterial [id='suppmat3' contenttype='video' freedownload='no' attachtoissue='no' ]
:
supplementmaterial [contenttype='dataset' id='suppmat4' freedownload='no' attachtoissue='no' ]
:
Issue number: ""
Article ID: ""
DOI: ""
Type: ""
Year of publication: ""
Colour graphics: "no"
Page range: "" - "" (total "")
Full text link: ""
Maths and Chemistry
There are numerous elements for handling maths and chemistry.
A mathematical equation must be either an equation or a compound (a set of equations).
First, a single equation, containing just the fomula in text (not the possible TeX markup and graphic versions):
Now a compound, which consists of two equations:
The same element can occur within a paragraph (
) which completes after the equation.
But there is a variant of this element that indicates that it must not break the paragraph apart. This is the "inline" variant: inline math formula. Such formulae will also not be numbered.
Block level equations are usually numbered, but an alternative element can be used to create an unnumbered equation:
A chemical equation also consists of a single chemical object, or a compound of objects.
First, a single chemical object, which consists of a formula or reference to a structure image:
Now a compound formula:
The same element can occur within a paragraph, as in
.
But, as with mathematical formulae, a chemical formulae can be officially "inline", using a different element: inline chemical formula. Again, such formula will not be numbered.
Block chemical equations are usually numbered, but a different element is used to create an unnumbered equation:
A structure is represented by an image of the structure, referenced by file name or by entity reference:
[STRUCTURE]