<response>

Response

Reply, response, or commentary concerning the journal article. In the typical case, the response is included in the same XML package as the original article, attached at the end of the article proper. Metadata that differs from that of original article (e.g., title, author), may be captured using the <front-stub> element; if the <front-stub> element is used, any metadata not specifically tagged is inherited from the original article.

Remarks

For a detailed discussion on the use of <response>, see Tagging Letters and Replies.

Conversion Note: Frequently, a reply or response is an article in its own right, not included as part of the original article. Such an article could use the <related-article> element in the article metadata to record the metadata for the original article.

Conversion Note: The response construction can also be used for the pathological case, rarely seen, in which several responses to an article are lumped together in a single container which is not the original article, merely a collection of responses. (In one example we examined, the first two responses were to an original article which was elsewhere, and the third response was a response to the first two responses.)

A journal article <article> may be divided into several components:

  1. the <front> (the article metadata or header information, which contains both journal and article metadata);
  2. the <body> (the textual and graphical content of the article);
  3. any <back> (any ancillary information such as a glossary, reference list, or appendix);
  4. a <floats-group> (single container element some publishers and archives use to hold all floating elements such as figures and tables that are referenced in the article body or back matter); and
  5. either a series of <response> elements or a series of <sub-article> elements. (A <response> is a commentary on the article itself, such as a summation by an editor, an answer to a letter-article, or words from the author responding to peer-review comments. Sub-articles are articles such as news pieces, abstracts, or committee reports that are completely contained within a main article.)

Attributes

id Identifier
response-type Type of Response
xml:lang Language

Content Model

<!ELEMENT  response     %article-short-model;                        >

Expanded Content Model

((front | front-stub), 
body?, back?, floats-group?)

Description

The following, in order:

This element may be contained in:

<article>, <sub-article>

Example

<article>
<front>
<journal-meta>
<journal-id journal-id-type="publisher">JCM</journal-id>
<issn>0095-1137</issn>
<publisher>
<publisher-name>JCM</publisher-name></publisher>
</journal-meta>
<article-meta>
<article-id pub-id-type="pmid">0547</article-id>
<article-categories>
<subj-group><subject>Letter to the Editor</subject>
</subj-group>
</article-categories>
<title-group>
<article-title><italic>Acrophialophora fusispora</italic>
Misidentified as <italic>Scedosporium prolificans</italic>
</article-title>
</title-group>
<contrib-group>
<contrib contrib-type="author"><string-name>
<surname>Guarro&ast;</surname> 
<given-names>Josep</given-names></string-name>
<xref ref-type="aff">
<sup><italic>a</italic></sup></xref></contrib>
<contrib contrib-type="author">
<name><surname>Gen&eacute;</surname> 
<given-names>Josepa</given-names></name>
<xref ref-type="aff">
<sup><italic>a</italic></sup></xref></contrib>
</contrib-group>
<aff>...</aff>
<pub-date pub-type="pub">
<year>2002</year></pub-date>
<volume>40</volume>
<issue>9</issue>
<fpage>000</fpage><lpage>000</lpage>
<permissions>
<copyright-statement>Copyright &#x00A9; 2002, British
Medical Journal
</copyright-statement>
</permissions>
</article-meta>
</front>
<body>
<sec>
<title>Comment Letter 1</title>
<p>Arthur et al. reported an interesting case of human keratouveitis
associated with the intraocular long-term retention of a contact lens,
...</p>
</sec>
</body>
<back>
<ref-list>
...
</ref-list>
</back>

<response response-type="reply">
<front>
<article-meta>
<title-group>
<article-title>Comment Letter 2</article-title>
</title-group>
<contrib-group>
<contrib contrib-type="author"><string-name>
<surname>Sigler&ast;</surname>, 
<given-names>Lynne</given-names></string-name>
<xref ref-type="aff">
<sup><italic>a</italic></sup></xref></contrib>
<contrib contrib-type="author">
<string-name><surname>Sutton</surname>, 
<given-names>Deanna A.</given-names></string-name>
<xref ref-type="aff">
<sup><italic>b</italic></sup></xref>
</contrib>
</contrib-group>
<aff>...</aff>
</article-meta>
</front>
<body>
<p>We are writing concerning the identification of the fungus causing
keratouveitis ...</p>
</body>
<back>
<ref-list>
...
</ref-list>
</back>
</response>

<response response-type="reply">
<front>
<article-meta>
<title-group><article-title>Authors&apos; Reply</article-title></title-group>
<contrib-group>
<contrib contrib-type="author"><string-name><surname>Arthur&ast;</surname>, 
<given-names>Stella</given-names></string-name>
<xref ref-type="aff">
<sup><italic>a</italic></sup></xref></contrib>
<contrib contrib-type="author">
<string-name><surname>Steed</surname>, <given-names>Lisa L.</given-names></string-name>
<xref ref-type="aff">
<sup><italic>a</italic></sup></xref>
</contrib>
</contrib-group>
<aff><sup><italic>a</italic></sup>Center for Research on Ocular Therapeutics
and Biodevices<break/>Department of Ophthalmology<break/>
Storm Eye Institute<break/>Department of Pathology and Laboratory Medicine<break/>
Medical University of South Carolina<break/>Charleston, South Carolina<break/>
&ast;Phone: (843) 792-2393<break/>Fax: (843) 792-1014<break/>
<email>E-mail: &bull;&bull;&bull;</email></aff>
</article-meta>
</front>
<body>
<p>We read with great interest and much chagrin the letters to the editor by
Drs. Sigler and Sutton and Drs. Guarro and Gene correcting our misidentification
of <italic>Acrophialophora fusispora</italic> as <italic>Scedosporium
prolificans</italic> (<xref rid="R7" ref-type="bibr">1</xref>). The original
identification was indeed made by an inexperienced technologist, although it
was confirmed by a more experienced person. However, both were unaware of the
existence of <italic>A. fusispora</italic>, as were the authors.</p>
<p>In defense of our reviewers, Fig. 2 was added to the manuscript at the
recommendation of one of the reviewers. We don&apos;t know if the reviewers
were given the opportunity to examine the added figure prior to publication.</p>
<p>Should we be so fortunate as to grow either organism again, we will not make
this same mistake. Our error emphasizes the need for technical staff trained in
mycology to keep up with recent journal publications. We hope others will learn
from our error.</p>
<p>On the bright side, the literature now contains the first report of
<italic>A. fusispora</italic> keratouveitis in association with a contact lens
retained intraocularly over a long term.</p>
</body>
<back>
<ref-list>
...
</ref-list>
</back>
</response>
</article>

Module

archivearticle3.dtd