...
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
For the 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:
| element | guideline | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| <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
|
Contributor email addresses
...
<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.
| Code Block | ||||
|---|---|---|---|---|
| ||||
<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.
| Code Block | ||||
|---|---|---|---|---|
| ||||
<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> |
| Info | ||
|---|---|---|
| ||
The earlier instruction to use the <string-name>element for the 2nd name alternative to avoid loading issues at brill.com is no longer valid. The problems at brill.com are solved. Articles with multiple <name>-elements within a <contrib>-element load without problems. |
Open Access articles
Open access to an article is specified in the <permissions>-group in the XML. Relevant elements are:
...
| xlink:title | license-type | xlink:href | <license-p> |
|---|---|---|---|
| CC BY | open-access | https://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-NC | open-access | https://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-ND | open-access | https://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. |
...
| language | xml |
|---|---|
| title | An example of the <permissions>-group |
...
...
See Article permissions for detailed XML and PDF instructions.
