Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 23 Next »

This page gives an overview of issues that occur in the XML (and should be avoided) and special points of attention.

Accessibility

Note that following the XML-instructions for both journals and books, it is obliged to add an alternative text to each illustration. This is required to meet relevant accessibility guidelines. As specified the <alt-text>-element should be used. The content of the element is either the caption-text or a dedicated text specified in the manuscript. If both are not present, the author or production editor should be asked to supply at least a caption text.

BOM-marker

Many XML processing applications (such as our Highwire Online platforms) do not process XML with the BOM Marker in place. Files including a BOM marker cannot be loaded. Existence of the marker should be avoided. XML-editors offer different options for avoiding the BOM-marker in the output. in Oxygen for example it is possible to set the in Preferences->"Encoding" the "UTF-8 BOM handling" to "Don't Write". In case of a file with a BOM-marker, the file should be saved again after making this change in the Preferences.

Citations

The for reference section at the end of an article or chapter, the <mixed-citation> element is used. When properly tagged, a DOI to the cited publication will be added, resulting from a CrossRef search. The following guidelines should be taken into account for the tagging within the <mixed-citation>-element:

elementguideline
<volume>

The volume tagging should only contain a volume number and NOT the complete title of the volume. A <volume>-element that contains the complete title will in general block the DOI registration of the publication. As described in the JATS/BITS description, the <volume>-element is for the number only. Below, a sample of correct tagging

Example of correct volume-tagging
<mixed-citation publication-type="book">
	<person-group person-group-type="author"><string-name><surname>Omobowale</surname>, 
		<given-names>Ayokunle Olumuyiwa</given-names></string-name>, and 
		<string-name><given-names>Olufikayo Kunle</given-names> <surname>Oyelade</surname></string-name>
	</person-group>. <date><year>2017</year></date>. 
	‘<chapter-title>Spiritual Embodiment in Yoruba Pentecostalism in Southwestern Nigeria</chapter-title>’. 
	In <person-group person-group-type="editor"><string-name><given-names>Michael</given-names> <surname>Wilkinson</surname></string-name> and 
	<string-name><given-names>Peter</given-names> <surname>Althouse</surname></string-name></person-group> (eds.), 
	<source>Annual Review of Sociology of Religion</source>, 
	vol. <volume>8</volume>: Pentecostals and the Body. 
	<publisher-loc>Leiden</publisher-loc>: <publisher-name>Brill</publisher-name>, <fpage>196</fpage>–<lpage>214</lpage>.
</mixed-citation>

Contributor email addresses

See the dedicated page Contributor email address with samples. The contributor email address triggers the access to the article, chapter or book at the brill.com platform. It is therefore important to ALWAYS include the email address.

DOI information

The DOI information in a BITS or JATS XML file should only contain the DOI itself, NOT the full URL: For example in a JATS XML-file for an article:

<article-id pub-id-type="doi">10.1163/15685330-bja10082</article-id>

Figures in abstract

Some articles for the imprint Brill | Wageningen Academic use a "graphical abstract" that should be included in the article abstract. These can be included using the standard <fig>-element. An example is given below. Note that the filenames at the online server are case-sensitive. The filename in the XML should therefore match exactly with the name of the JPG with the illustration.

Figure as part of an abstract
<abstract xml:lang="eng">
	<p>The edible insect ... inflammatory obesity alterations.</p>
	<p><fig position="float" orientation="portrait">
			<graphic xlink:href="ga_jiff2022.0043.jpg" position="float" orientation="portrait"/>
		</fig></p>
</abstract>

The online result is visible in JIFF Volume 9 - issue 2.

Name alternatives

in case of multiple variants of a contributor name, the <name-alternatives>-element must be used as a wrapper around the different versions, as in the example below.

Use of name alternatives
<contrib contrib-type="author">
   <name-alternatives>
    <name name-style="eastern" xml:lang="ja-Jpan">
     <surname>中西</surname>
     <given-names>秀彦</given-names>
    </name>
    <name name-style="western" xml:lang="en">
     <surname>Nakanishi</surname>
     <given-names>Hidehiko</given-names>
    </name>
    <name name-style="eastern" xml:lang="ja-Kana">
     <surname>ナカニシ</surname>
     <given-names>ヒデヒコ</given-names>
    </name>
   </name-alternatives>
   <xref ref-type="aff" rid="aff2">**</xref>
  </contrib>

Important Addition

Although the above is accorsding to the JATS and BITS standard, brill.com has a currently a problem with loading XML using multiple <name>-elements within a single contributor. The workaround that - until further - notice needs to be applied is to use the <string-name>-element for each 2nd and next name. The sample above should thus be coded as:

<contrib contrib-type="author"><name-alternatives> <name name-style="eastern" xml:lang="ja-Jpan"> <surname>中西</surname> <given-names>秀彦</given-names> </name> <string-name name-style="western" xml:lang="en"> <surname>Nakanishi</surname> <given-names>Hidehiko</given-names> </string-name> <string-name name-style="eastern" xml:lang="ja-Kana"> <surname>ナカニシ</surname> <given-names>ヒデヒコ</given-names> </string-name> </name-alternatives> <xref ref-type="aff" rid="aff2">**</xref> </contrib>



Open Access articles

Open access to an article is specified in the <permissions>-group in the XML. Relevant elements are:

  • <copyright-statement>
  • <copyright-year>
  • <copyright-holder> - in general the name(s) of the author(s)
  • <license> - to specify the  type of open access license in the attributes @license-type, @xlink:href and @xlink:title. (see table below for the values)
  • <license-p> - A textual description of the license information

The following table specified the values for the attributes in the <license>-element and the text for the <license-p> element.

xlink:titlelicense-typexlink:href<license-p>
CC BYopen-accesshttps://creativecommons.org/licenses/by/4.0/This is an open access article distributed under the terms of the CC BY 4.0 license.
CC BY-NCopen-accesshttps://creativecommons.org/licenses/by-nc/4.0/This is an open access article distributed under the terms of the CC BY-NC 4.0 license.
CC BY-NC-NDopen-accesshttps://creativecommons.org/licenses/by-nc-nd/4.0/This is an open access article distributed under the terms of the CC BY-NC-ND 4.0 license.

See Article permissions for detailed XML and PDF instructions.