Structure

1. De Gruyter requires XML deliveries to include one or more PDF representations of the content and, if applicable, figure and media files. Deliveries shall be compressed in ZIP files following the DG folder structure and naming conventions. (🡪 section Delivery packages)

2. The XML document(s) must comply with the relevant schema. (🡪 section Schema)

3. The source element (book/article) must include predefined attributes and namespaces (🡪 section Attributes and Namespaces)

4. Details regarding tagging instructions can be found within the following sections:

   1. Metadata (🡪 section Metadata Elements)

   2. Frontmatter (Books only) (🡪 section Frontmatter)

   3. Fulltext (🡪 section Fulltext Elements)

   4. Backmatter (🡪 section Backmatter Elements)

Requirement Level

The key words "must", "must not", "required", "shall", "shall not", "should", "should not", "recommended", "may", and "optional" in this document are to be interpreted as described in RFC 2119 [6].

They are underlined throughout the document and its significance is shown on mouse over.

XML Declaration

The XML declaration must follow the following RegEx: <?xml\sversion="1.0"\sencoding="UTF-8"?>[\n\s ]*

<?xml version="1.0" encoding="UTF-8"?>

Namespaces

The following namespaces must be defined within all XML files:

The following namespace must be defined whenever free acess tagging is used (see section Free Access):

Entities

Only predefined entities and numerical character references shall be used.

Any entities other than predefined general entities for XML delimiters (lt, gt, amp, apos, quot) and numeric character references [14] must not be referenced and/or be declared in XML documents delivered to De Gruyter. Also external entities which might be declared in a DTD must not be referenced.

The XML special character module of the NLM DTDs declares many entities for characters which are not within the range of printable ASCII 32-127 [15] (often referred to as “special characters”). An XML document that references these entities might be well formed, and a valid instance of the DTD, but will be considered incorrect by De Gruyter.

Unicode

For character encoding in De Gruyter-XML files usage of UTF-8 [16] is required.

In order to avoid problems with rendering the XML, De Gruyter restricts the ranges of characters to be used to a subset of the available range.

Characters should be represented by the according byte/byte sequence as per UTF-8. However, in some cases, e.g. where there is no actual glyph for a character (whitespace characters) it might be beneficial to capture a numerical character representation (NCR).

The section Allowed Unicode Ranges offers details for which characters an NCR is either allowed or required. NCRs should be captured with hexadecimal numbers, 4 digits, uppercase letters (Regex: ^&#x[0-9A-F]{4}$).

Characters which are canonically equivalent must be normalized to Normalization Form C [17] [18]. Ligatures (FB00 to FB06) must be replaced by the respective individual Unicode characters that are represented within the ligature.

If single characters cannot be represented using Unicode characters, they must be replaced by the element <private-char> containing an <inline-graphic> . The attributes @name and @description may be used to describe the character. Please get back to your Production Editor if this is the case.

<p>This is some text showing a private char <private-char description="number eight in white on a black background within a white circle" name="eight"><inline-graphic xlink:href="graphic/b_9783110365344-003_ingr_004.png"/></private-char> inline</p>

Empty Elements

Elements (without attributes) that are supposed to contain content must not be empty. In case there is no matching value for a given element related with the respective article, the element must be omitted. If the element is required, do not capture placeholder text or whitespace. Instead contact your respective production editor or the author in order to obtain the required information.

Formatted Text

As a rule, use formatted text (<bold>, <italic>, <sc>, etc) only to emphasize a piece of information. Do not set entire elements in formatted text. For example, if a <title> is set completely in boldface, do not tag the <bold>. However, if a title has a word or some words set in boldface for emphasis, tag those words using <bold>. Mainly this will apply to <title>, <p> in <abstract>, and <label>. It might also show up in <aff> and “special” sections, like <ack>.

Languages

Every content needs to be identified with @xml:lang. Unlike nearly all other attributes in XML, the value of language is inherited. This means that all elements inside the one with the language attribute (its descendants) are assumed to be in the same language, unless they explicitly set their own @xml:lang attribute.

In general, the rule for tagging language is that the main language of the book/article must be set in the @xml:lang on <book> or <article>. Any paragraph within the Book or Article-XML file that is in a different language must be tagged with an @xml:lang to identify the language of that piece. To identify certain words, phrases, or sentences that use another language within a paragraph, use <styled-content> and the @xml:lang attribute (see section Formatted Text).

Language values need to be inserted using the ISO 639-1 standard values [12].

<p>The title says <named-content content-type="rtl" specific-use="bidi">"פעילות הבינאום, W3C"</named-content> in Hebrew.</p>

Collection Meta

Series, sub-series or multi-volume works, or combination thereof, must contain <collection-meta> to convey (sub-)series or multi-volume-work related information. The attribute @collection-type shall be used to distinguish between different types of collections:

Attribute: @collection-type

Attribute values: series, sub-series, multi-volume-work

<collection-meta collection-type="series">
  <title-group>
    <title>Phonology and Phonetics</title>
  </title-group>
  <contrib-group>
    <contrib contrib-type="editor">
      <name>
        <surname>Lahiri</surname>
        <given-names>Aditi</given-names>
      </name>
    </contrib>
  </contrib-group>
  <volume-in-collection>
    <volume-number>12</volume-number>
  </volume-in-collection>
  <issn>1861-4191</issn>
</collection-meta>
<collection-meta collection-type="multi-volume-work">
  <title-group>
    <title>Tones and Tunes</title>
  </title-group>
  <volume-in-collection>
    <volume-number>1</volume-number>
  </volume-in-collection>
</collection-meta>

IDs

Information on how to build the DOI can be found within the De Gruyter Variables and ID guidelines [1]. The DOIs must conform to these specifications.

<book-id book-id-type="title">514363</book-id>

/book/book-meta/book-id

<book-id pub-id-type="title">514363</book-id>

/book/book-meta/book-id

<book-id book-id-type="doi">10.1515/9783110339406</book-id>

<book-id pub-id-type="doi">10.1515/9783110339406</book-id>

//book-part-meta[not(parent::book-part[@book-part-type='part'])]/book-part-id

<book-part-id book-part-id-type="doi">10.1515/9783110339406-017</book-part-id>

<book-part-id pub-id-type="doi">10.1515/9783110339406-017</book-part-id>

/book/book-meta/abstract/sec-meta/object-id

/book/front-matter/ack/sec-meta/object-id

/book/book-back/glossary/sec-meta/object-id

...

<object-id pub-id-type="doi">10.1515/9783110339406-003</object-id> 

/issue-xml/journal-meta/journal-id

/article/front/journal-meta/journal-id

<journal-id journal-id-type="journal-code">hsz</journal-id>

<journal-id journal-id-type="publisher-id">bchm</journal-id>

<journal-id journal-id-type="doi-code">hsz</journal-id>

/issue-xml/issue-meta/issue-id

<issue-id pub-id-type="publisher-id">jbca.2013.32.issue-4</issue-id>

/article/front/article-meta/article-id

<article-id pub-id-type="publisher-id">hsz-2015-0068</article-id>

<article-id pub-id-type="doi">10.1515/hsz-2015-0068</article-id>

Contributors

/book/collection-meta/contrib-group

/book/book-meta/contrib-group

//book-part/book-part-meta/contrib-group

/article/front/journal-meta/contrib-group

/issue-xml/issue-meta/contrib-group

/article/front/article-meta/contrib-group/contrib

//sec/sec-meta/contrib-group

The element <contrib-group> contains the contributors of a book series, an entire book, a chapter or an article. The elements <surname> and <given-names> should be included within each <contrib>. In cases where authors have just one name or where it's unclear which part is the given name, only <surname> should be used. Use <email> including the attribute @xlink:href to insert the email address of the contributor. @xlink:href is required and shall start with "mailto:". It must also follow the formal definitions described in RFC 5322 [27] (sections 3.2.3 and 3.4.1) and RFC 5321 [28]. In case a salutation or title information is present, this must be tagged using <prefix>. To indicate that the contributor was deceased when the article or book has been published, the attribut @deceased="yes" shall be used.

Element name: surname

Element value: ^([\p{L}’‘.][-\s]?)+$

Each <contrib> must contain the element <name> or <collab>.

The attribute @corresp="yes" must be used for the corresponding author only. If there is a contributors affiliation, this information will be tagged within the element <aff>. To connect the contributor and the affiliation, the element <xref> including the attributes @rid and @ref-type="aff" is used.

<contrib-group>
  <contrib contrib-type="series_editor">
    <name>
      <prefix>Prof. Dr.</prefix>
      <surname>Michael</surname>
      <given-names>Heaney</given-names>
    </name>
    <email xlink:href="mailto:clemens.heydenreich@xmltest.com">
      clemens.heydenreich@xmltest.com
    </email>
    <xref ref-type="aff" rid="j_hsz-2013-0008_aff_001"/>
    <xref ref-type="aff" rid="j_hsz-2013-0008_aff_003"/>
  </contrib>
</contrib-group>

If the author provides his/her email address, but does not want to publish it along with the publication the @specific-use="company-only" must be used:

<email specific-use="company-only" xlink:href="mailto:karen.miller@xmltest.com">karen.miller@xmltest.com</email>

<contrib contrib-type="author">
  <name-alternatives>
    <name name-style="western" xml:lang="en">
      <surname>Zhang</surname>
      <given-names>Y. P.</given-names>
    </name>
        <name name-style="eastern" xml:lang="ja">
      <surname>石橋</surname>
      <given-names>忍月</given-names>
    </name>
  </name-alternatives>
</contrib>

<contrib contrib-type="author">
  <collab>The Mouse Genome Sequencing Consortium
    <contrib-group>
      <contrib>
        <name>
          <surname>Kelly</surname><given-names>Laura A.</given-names>
        </name>
      </contrib>
      <contrib>
        <name>
          <surname>Randall</surname><given-names>Daniel Lee</given-names>
          <suffix>Jr.</suffix>
        </name>
      </contrib>
    </contrib-group>
  </collab>
</contrib>

<contrib contrib-type="author">
  <collab>The <institution>European Federation of Clinical Chemistry and Laboratory Medicine (EFLM)</institution> – <institution>European Society of Pharmacogenomics and Personalised Therapy (ESPT)</institution> Joint Working Group on Personalized Laboratory Medicine (WG-PLM)</collab>
</contrib>

<contrib-group>
  <contrib contrib-type="author">
    <name>
      <surname>Michael</surname>
      <given-names>Heaney</given-names>
    </name>
    <on-behalf-of>Berlin-Brandenburgische Akademie der Wissenschaften</on-behalf-of>
  </contrib>
</contrib-group>

<contrib-group>
  <contrib>
    <name>
      <surname>Kelly</surname><given-names>Laura A.</given-names>
    </name>
  </contrib>
  <contrib>
    <name>
      <surname>Randall</surname>
      <given-names>Daniel Lee</given-names>
      <suffix>Jr.</suffix>
    </name>
  </contrib>
  <on-behalf-of>Berlin-Brandenburgische Akademie der Wissenschaften</on-behalf-of>
</contrib-group>

//contrib/contrib-id

<contrib-id contrib-id-type="orcid">https://orcid.org/0000-0002-7361-560X</contrib-id>

//contrib/bio

<bio>
  <fig fig-type="contrib">
    <graphic xlink:href="graphic/j_hsz-2015-0068_cv_001.jpg"/>
  </fig>
  <p>Alexey V. Shevelkin received his PhD at the P.K. Anokhin Institute of Normal Physiology. Currently, he is a Postdoctoral Research Fellow at the Pletnikov Laboratory in the Department of Psychiatry and Behavioral Sciences, Johns Hopkins University School of Medicine.</p>
</bio>

Affiliation

//contrib-group/aff

The element <aff> includes information about the affiliation of an author. The attribute @id is used to link <contrib> entries with the affiliation. The element <country> includes the corresponding country information. It must contain one <country> element including the attribute @country using the ISO 3166-1 Alpha-2 code [24]. Further detailed tagged information shall be included by using one or more <institution> elements and one <city> element.

Required Information: @id, institution OR institution-wrap/institution, city, country/@country

Optional Information: institution[@content-type="dept"], institution-wrap/institution-id, institution-wrap/institution, addr-line, postal-code, state

<aff id="j_hsz-2013-0008_aff_002">
  <institution-wrap>
    <institution-id institution-id-type="ROR">https://ror.org/046ak2485</institution-id>
    <institution content-type="university">Freie Universität Berlin</institution>
  </institution-wrap>
  <institution>Botanic Garden and Botanical Museum Berlin</institution>, 
  <city>Berlin</city>, 
  <postal-code>14195</postal-code>, 
  <country country="DE">Germany</country>.
</aff>

Any affiliation information that is not institution, postal code, city, state or country shall be tagged using <addr-line>. Punctuation must be preserved.

//contrib-group/aff/institution-wrap

<institution-wrap>
  <institution-id institution-id-type="Ringgold">1812</institution-id>
  <institution content-type="university">Harvard University</institution>
</institution-wrap>

<institution-wrap>
  <institution-id institution-id-type="ROR">https://ror.org/046ak2485</institution-id>
  <institution content-type="university">Freie Universität Berlin</institution>
</institution-wrap>

<institution-wrap>
  <institution-id institution-id-type="ROR">https://ror.org/046ak2485</institution-id>
  <institution-id institution-id-type="Ringgold">9166</institution-id>
  <institution content-type="university">Freie Universität Berlin</institution>
</institution-wrap>

<aff id="j_cmam-2016-0011_aff_003"><institution content-type="private"/>
  <city>Berlin</city><country country="DE"/></aff>

<aff id="b_9783110365344-003_aff_002" specific-use="company-only">
  <institution>Cancer Research UK Cell Signalling Group and Weatherall</institution>, 
  <institution content-type="dept">Institute of Molecular Medicine</institution>,
  <city>Oxford</city>, 
  <postal-code>OX3 9DS</postal-code>, 
  <country country="GB">United Kingdom</country>.
</aff>

<aff id="b_9783110365344-003_aff_002" specific-use="company-only" content-type="private">
  <addr-line>41 Charles St.</addr-line>, 
  <city>Oxford</city>, 
  <postal-code>OX3 9DS</postal-code>, 
  <country country="GB">United Kingdom</country>.
</aff>

Author Notes

/book/book-meta/author-notes

//book-part/book-part-meta/author-notes

/article/front/article-meta/author-notes

The element <author-notes> is used to capture additional author information. For example:

• which of the authors (or other contributors) is the corresponding contributor and to whom information requests should be addressed using the element <corresp>

• (The "communicated by" information has been moved to section Additional Information.)

<author-notes>
  <corresp>Prof. Dr. W. Mohammed S.A. Gaby, Medizinisches Labor Bremen, Haferwende 12, 28357 Bremen, Germany, gaby@mail.com</corresp>
  <p>The authors contributed equally to this work.</p>  
</author-notes>

Publication Date

/book/book-meta/pub-date

/issue-xml/issue-meta/pub-date

/article/front/article-meta/pub-date

The element <pub-date> holds the publication date of the book, issue or article and can be used once or twice within one document. The attribute @pub-type and the elements <day>, <month>, <year> are required.

The date must be valid and for the tags <day>, <month> and <year> only digits are allowed:

• day: [01-31]

• month: [01-12]

• year: \d{4}

The element <year> should not be used as second element within <pub-date>.

<pub-date publication-format="ppub">
  <day>01</day>
  <month>11</month>
  <year>2015</year>
</pub-date>

<pub-date pub-type="ppub">
  <day>01</day>
  <month>11</month>
  <year>2015</year>
</pub-date>

<pub-date pub-type="ppub">
  <day>01</day>
  <month>11</month>
  <year>2015</year>
</pub-date>

/article/front/article-meta/pub-date

/issue-xml/issue-meta/pub-date

<pub-date pub-type="ppub">
  <day>01</day>
  <month>04</month>
  <year>2017</year>
</pub-date>
<pub-date pub-type="actual_ppub">
  <day>24</day>
  <month>04</month>
  <year>2017</year>
</pub-date>

Volume Information

/book/collection-meta/volume-in-collection/volume-number

<collection-meta collection-type="series">
  <title-group>
    <title>Phonology and Phonetics</title>
  </title-group>
  <contrib-group/>
  <volume-in-collection>
    <volume-number>12</volume-number>
  </volume-in-collection>
  <issn>1861-4191</issn>
</collection-meta>
<collection-meta collection-type="multi-volume-work">
  <title-group>
    <title>Tones and Tunes</title>
  </title-group>
  <volume-in-collection>
    <volume-number>1</volume-number>
  </volume-in-collection>
</collection-meta>

/book/book-meta/volume

<volume-number>85</volume-number>

/issue-xml/issue-meta/volume

/article/front/article-meta/volume

<volume>32</volume>

<volume content-type="open-issue">32</volume>

<volume content-type="ahead-of-print">0</volume>

ISSN

The element <issn> holds the ISSN of a book series or a journal.

/issue-xml/journal-meta/issn

/article/front/journal-meta/issn

<issn pub-type="epub">1437-4315</issn>
<issn pub-type="ppub">1431-6730</issn>

/book/collection-meta/issn

<issn publication-format="ppub">0440-7562</issn>

<issn publication-format="epub">0440-7164</issn>

Publisher

/book/book-meta/publisher

/article/front/journal-meta/publisher

The element <publisher> holds the publisher information of the book, chapter or article. The allowed values for <publisher-name> and the corresponding {DOI-prefix} are specified within the list of predefined publisher names that are listed within the De Gruyter Variables and ID Guidelines [1].

<publisher>
  <publisher-name>De Gruyter</publisher-name>
</publisher>

First/Last Page

//book-part/book-part-meta/fpage

//book-part/book-part-meta/lpage

/article/front/article-meta/fpage

/article/front/article-meta/lpage

The tag <fpage> and <lpage> include the first and last page number of an article, chapter or book. Within these tags the use of the following prefixes is allowed: “e”; “A”; “eA”; “s”; “r”. Please make sure that once a prefix is used it is included in both tags. The use is case sensitive and there shall be no whitespace between the prefix and the page number. Furthermore the following roman numericals may be included: i, v, x, l, c, d, m.

Regex: ^((eA|A|e|r|s)?(\d+))|[ivxlcdm]|[u2|u3]+$

For endpaper material front or back ( book-app[@book-part-type="endpaper"] ), the values u2 and u3 are allowed.

<fpage>587</fpage>

<lpage>606</lpage>

This element must not be included within the metadata together with <elocation-id>. Either <fpage> and <lpage> or <elocation-id> shall be present.

Supplementary Material

Supplementary Material is used for description of and pointer to additional data files that contain information directly supportive of the document (for example, audio clip, applet, raw research data).

To add information about the Supplementary Material itself, please see section Supplementary Material Note.

//book-part/book-part-meta/supplementary-material

<supplementary-material xlink:href="suppl/9783110339406_sound_files.zip">
  <caption><p>Sound files (as ZIP file)</p></caption>
</supplementary-material>

<supplementary-material xlink:href="suppl/9783110339406_sound_files.zip">
  <label>Sound files (as ZIP file)</label>
</supplementary-material>

/article/front/article-meta/related-article

<related-article related-article-type="supplement" xlink:href="suppl/snde1799_supplementary_0.zip">Supplementary Material Details</related-article>

<related-article related-article-type="supplement" xlink:href="suppl/suppl_verbal-detection-error-tradeoff.zip">
  Verbal Detection Error Tradeoff (DET). Also available here:
  <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.24433/CO.154591c8-9d3f-47eb-b656-3aff245fd5c1">
    https://doi.org/10.24433/CO.154591c8-9d3f-47eb-b656-3aff245fd5c1
  </ext-link>
</related-article>
<related-article related-article-type="code-ocean" xlink:href="https://doi.org/10.24433/CO.154591c8-9d3f-47eb-b656-3aff245fd5c1">
  Detection Error Tradeoff (DET)
</related-article>

Permissions

/book/book-meta/permissions

//book-part/book-part-meta/permissions

/article/front/article-meta/permissions

This information is required for each book, chapter and journal article.

<permissions>
  <copyright-statement>© 2024 Walter de Gruyter GmbH, Berlin/Boston</copyright-statement>
  <copyright-year>2024</copyright-year>
  <copyright-holder>Walter de Gruyter GmbH, Berlin/Boston</copyright-holder>
</permissions>

<permissions>
  <copyright-statement content-type="cover">© by the author</copyright-statement>
  <copyright-statement>© 2020 Walter de Gruyter GmbH, Berlin/Boston</copyright-statement>
  <copyright-year>2020</copyright-year>
  <copyright-holder>Walter de Gruyter GmbH, Berlin/Boston</copyright-holder>
</permissions>

<permissions>
  <copyright-statement>© 2017 Saskia Schuster2024 The author(s), published by Walter de Gruyter GmbH, Berlin/Boston</copyright-statement>
  <copyright-year>20172024</copyright-year>
  <copyright-holder>Saskia SchusterThe author(s), published by Walter de Gruyter GmbH, Berlin/Boston</copyright-holder>
  <license license-type="open-access" xlink:href="http://creativecommons.org/licenses/by-nc-nd/3.0" specific-use="rights-object-archive-dnb">
    <license-p>This work is licensed under the Creative Commons Attribution-NonCommercial-
    NoDerivatives 3.0 License.</license-p>
  </license>
</permissions>

<permissions>
  <copyright-statement>© 2016 by De Gruyter</copyright-statement>
  <copyright-year>2016</copyright-year>
  <ali:free_to_read/>
</permissions>

<license license-type="free">
  <license-p>This content is free.</license-p>
</license>

<permissions>
  <copyright-statement>© 2016 by De Gruyter</copyright-statement>
  <copyright-year>2016</copyright-year>
  <ali:free_to_read start_date="2020-03-01" end_date="2020-07-31"/>
</permissions>

Abstract

/book/book-meta/abstract

//book-part/book-part-meta/abstract

/article/front/article-meta/abstract

The element <abstract> holds the abstract of a book, chapter or article. The elements <title> and <p> or <sec> are required in this context.

<abstract>
  <title>Abstract</title>
  <p>This is the abstract text.</p>
</abstract>

The title element must not contain a colon (":"). Only one abstract can be tagged without @abstract-type. If there is more than one <abstract> present, the following abstracts must be tagged using @abstract-type. See Highlights and Graphical Abstract.

<abstract>
  <title>Abstract</title>
  <sec>
    <title>Background</title>
    <p>Cigarette smoking is a major risk factor for several chronic diseases.
    Epidemiological data indicate the use of smokeless tobacco (ST) is associated
    with significantly lower risk for smoking-related diseases compared to cigarettes.
    Several biomarkers of exposure (BioExp) and effect (BioEff) associated with
    smoking and use of moist snuff (ST) were evaluated.</p>
  </sec>
  <sec>
    <title>Methods</title>
    <p>A single site, cross-sectional clinical study enrolled three groups of
    generally healthy male smokers (SMK), moist snuff consumers (MSC), and non-tobacco
    consumers (NTC), and several BioExp and BioEff were evaluated.</p>
  </sec>
</abstract>

/book/book-meta/trans-abstract

//book-part/book-part-meta/trans-abstract

/article/front/article-meta/trans-abstract

<trans-abstract xml:lang="de">
  <title>Zusammenfassung</title>
  <p>Dies ist der Text der Zusammenfassung.</p>
</trans-abstract>

<abstract abstract-type="highlight">
  <title>Highlights</title>
  <p>
    <list id="j_jcim-2020-0485_list_001" list-type="custom">
      <list-item id="j_jcim-2020-0485_li_001">
        <label>–</label>
          <p>COVID-19 has affected the lives of millions worldwide and unfortunately no precise treatment available till today.</p>
      </list-item>
      <list-item id="j_jcim-2020-0485_li_002">
        <label>–</label>
          <p>Trikatu an <italic>ayurvedic</italic> formulation suggested by various authorities in India.</p>
      </list-item>
        <list-item id="j_jcim-2020-0485_li_003">
          <label>–</label>
          <p>Trikatu found to be a potential anti-inflammatory; anti-dyslipidaemia and immune-modulatory drug can be used for combating flu like illnesses.</p>
      </list-item>
    </list>
  </p>
</abstract>

/article/front/article-meta/abstract/@abstract-type="graphical"

<abstract abstract-type="graphical">
  <title>Graphical Abstract</title>
  <p>
    <fig fig-type="graphical">
      <caption>
        <p>Various synthesis methods and electrochemical applications are reviewed.</p>
      </caption>
      <graphic xlink:href="graphic/hsz-2015-0068-graphabs.jpg"/>
    </fig>
  </p>
</abstract>

Keywords

/book/book-meta/kwd-group

//book-part/book-part-meta/kwd-group

/article/front/article-meta/kwd-group

The element <kwd-group> is used for one set of keywords used to describe a document. The element <title> as well as at least one <kwd> or <nested-kwd> are required.

<kwd-group>
  <title>Keywords</title>
  <kwd>XML</kwd>
  <kwd>metadata</kwd>
</kwd-group>

For keywords, that are used in another language than the document language, the attribute @xml:lang must be used:

Attribute: @xml:lang

Attribute value: ISO 639-1 Language codes [12] in lower case letters.

A <kwd-group> including the attribute @xml:lang must only be used in combination with a <kwd-group> without the language attribute.

The title element must not contain a colon (":").

Classification Codes

/article/front/article-meta/kwd-group[@kwd-group-type]

/book/book-meta/kwd-group[@kwd-group-type]

//book-part/book-part-meta/kwd-group[@kwd-group-type]

To tag classification codes the attribute @kwd-group-type in combination with the corresponding <title> must be used.

<kwd-group kwd-group-type="MSC">
  <title>MSC 2010</title>
  <kwd>14M30</kwd>
  <kwd>14A22</kwd>
  <kwd>17B20</kwd>
</kwd-group>

The title element must not contain a colon (":").

<kwd-group kwd-group-type="ACM_CCS">
  <title>ACM CCS</title>
  <nested-kwd>
    <kwd>Information systems</kwd>
    <nested-kwd>
      <kwd>Data management systems</kwd>
      <nested-kwd>
        <kwd>Database design and models</kwd>
        <nested-kwd>
          <kwd>Data model extensions</kwd>
          <nested-kwd>
            <kwd>Uncertainty</kwd>
          </nested-kwd>
        </nested-kwd>
      </nested-kwd>
    </nested-kwd>
  </nested-kwd>
</kwd-group>

Funding Information

/book/book-meta/funding-group

/article/front/article-meta/funding-group

The element <funding-group> includes information concerning grants, contracts, sponsors, or other funding for the research reported in the article.

<award-group> contains information concerning one award under which the work was supported. The element <funding-source> includes an agency or organization (such as a foundation, corporation, or an educational institution) that funded the research on which a work was based. Use the attribute @xlink:href to indicate the DOI of the funder.

For values of the element <funding-source> and its attribute @xlink:href the entries within the CrossRef list of the funder names and identifiers [32] must be used. If an institution is not listed there, please contact us.

The <award-id> contains an identifier that has been assigned to the award, for example, a grant number, a grant reference number, or a contract number.

<funding-group>
  <award-group>
    <funding-source xlink:href="http://doi.org/10.13039/501100000848">University Of Edinburgh</funding-source>
    <award-id>FFI2010-18214</award-id>
  </award-group>
  <funding-statement>This work was supported by a research grant from the University Of Edinburgh (FFI2010-18214)</funding-statement>
</funding-group>

The elements <funding-source> including the attribute @xlink:href and <award-id> are required in this context.

Page Count

/article/front/article-meta/counts/page-count

<page-count count="29"/>

/book/book-meta/counts/book-page-count

//book-part/book-part-meta/counts/book-page-count

<book-page-count count="120" />

//book-part/book-part-meta/counts/book-count[@count-type="chapter-page-count"]

< book-count count="15" count-type="chapter-page-count"/>

/book/book-meta/counts/page-count

//book-part/book-part-meta/counts/page-count

<page-count count="29"/>

Additional Information

/article/front/notes

/book/book-meta/notes

//book-part/book-part-meta/notes

The element <notes> contains additional article information that cannot be represented by any other JATS/BITS metadata tag (like fn-group/fn[fn-type] (see section Additional Information). The attribute @notes-type is required.

Attribute: @notes-type

Attribute values: added-post-electronic-publication, other, software, post-publication-correction, retraction

<notes notes-type="added-post-electronic-publication" id="j_snde-2018-1234_notes_001">
  <sec>
    <title>Correction note</title>
    <p>Correction added after online publication February 12, 2015: Mistakenly this article was already published ahead of print under the title of the entire special issue “Adiposopathy in cancer and (cardio)metabolic diseases: an endocrine approach”.</p>
  </sec>
</notes>

<notes notes-type="software" id="j_snde-2018-1234_notes_002">
    <p>MATLAB and Simulink are registered trademarks of The MathWorks, Inc. See www.mathworks.com trademarks for a list of additional trademarks. The MathWorks Publisher Logo identifies books that contain MATLAB and Simulink content. Used with permission. The MathWorks does not warrant the accuracy of the text or exercises in this book. This book ́s use or discussion of MATLAB and Simulink software or related products does not constitute endorsement or sponsorship by The MathWorks of a particular use of the MATLAB and Simulink software or related products.</p>
</notes>

<notes notes-type="post-publication-correction">
  <p>The original version of this chapter was revised: [xyz] has been corrected. An Erratum is available at DOI:<related-article related-article-type="correction-forward" ext-link-type="doi" xlink:href="https://doi.org/9783110339406-005">https://doi.org/9783110339406-005</related.article></p>
</notes>

Counting ID

/article/front/article-meta/custom-meta-group/custom-meta[meta-name/text()='counting-id']/meta-value
/book/book-meta/custom-meta-group/custom-meta[meta-name/text()='counting-id']/meta-value

In order to count electronic access for the german VG Wort [33] an invisible counting Pixel must be included within the content page online [34]. This includes a {counting-id} which identifies the book title or article being accessed. Usually our online platform will create this information when the content is uploaded based on the DOI. Whenever another {counting-id} must be used it shall be tagged as follows:

<custom-meta-group>
  <custom-meta>
    <meta-name>counting-id</meta-name>
    <meta-value>vgzm.378750-03401812-MDR-2015-15-A-02</meta-value>
  </custom-meta>
</custom-meta-group>

If no {counting-id} is to be created by the platform, it must be tagged using an empty <meta-value> element:

<custom-meta-group>
  <custom-meta>
    <meta-name>counting-id</meta-name>
    <meta-value/>
  </custom-meta>
</custom-meta-group>

Please not that this information must only be included upon request.

Other frontmatter parts

Whenever there are no semantically suitable elements in the front- or backmatter, <front-matter-part> within <front-matter> or <book-part> within <book-back> may be used with the attribute @book-part-type="chapter".

<front-matter-part book-part-type="chapter" id="b_9783110755787-205">
  <book-part-meta>
    <book-part-id book-part-id-type="doi">10.1515/9783110755787-205</book-part-id>
    <title-group>
      <title>Autor:innenverzeichnis</title>
    </title-group>
    <fpage>XXXIX</fpage>
    <lpage>XLII</lpage>
    <self-uri content-type="pdf" xlink:href="9783110755787-205.pdf"/>
    <counts>
      <book-page-count count="4"/>
    </counts>
  </book-part-meta>
  <named-book-part-body>...</named-book-part-body>
</front-matter-part>

Dedication

/book/front-matter/dedication

<dedication>
  <book-part-meta>
    <book-part-id book-part-id-type="doi">10.1515/9783111145310-202</book-part-id>
    <title-group>
      <title>Dedication</title>
    </title-group>
    <fpage>V</fpage>
    <lpage>V</lpage>
    <permissions>
      <copyright-statement>© 2023 Walter de Gruyter GmbH, Berlin/Boston</copyright-statement>
      <copyright-year>2023</copyright-year>
      <copyright-holder>Walter de Gruyter GmbH, Berlin/Boston</copyright-holder>
    </permissions>
    <self-uri content-type="pdf" xlink:href="9783111145310-202.pdf"/>
    <counts>
      <book-page-count count="1" count-type="chapter-page-count"/>
    </counts>
  </book-part-meta>
  <named-book-part-body>
    <p><italic>For my son Jonas</italic></p>
  </named-book-part-body>
</dedication>

/book/book-front/notes[@notes-type="dedication"]

<notes notes-type="dedication">
  <p><italic>For my son Jonas</italic></p>
</notes>

/article/front/notes[@notes-type="dedication"]

<notes notes-type="dedication">
  <p>We dedicate this paper to our professor, Dr. Robert Jemmings, whose critique of the underlying study identified potential bias in the analysis and strengthened our argument.</p>
</notes>

Sections

The element <sec> is used to structure content within articles and chapters. The attribute @id shall be present.

Attribute: @id

Attribute Value: {section-id}

<sec id="b_9783110339406-005_s_001_s_002_s_003">
  <label>1.2.3</label>
  <title>A Chapter Titel</title>
  <p>Here comes the content.</p>
</sec>

Use the element whenever a section is structured with a label or title. If that is not present, do not use <sec>.

<sec id="b_9783110339406-005_s_001" disp-level="4">
 ...
</sec>

Headings

Section headings are stated within the <sec> element using the tag <title>. In case of numbered titles, the <label> tag must be used to capture the numbering.

<sec id="b_9783110339406-005_s_001_s_002_s_003">
  <label>1.2.3</label>
  <title>A Provisional Hierarchy of the Six Modes</title>
  ...
</sec>

Abbreviations

Abbreviations should be tagged within the text where they appear using the element <abbrev> including the attribute @xlink:title to name the written-out version.

<abbrev xlink:title="Abbildung(en)">Abb.</abbrev>

If there are different abbreviation types within the document the element needs to contain the attribute @content-type.

<abbrev content‐type="Abbreviated Literature" xlink:title="Acta Sanctorum, begründet von J. Bolland, Antwerpen 1643 ff.">AASS</abbrev>

Quotation

Quotations can be placed at the beginning or within a chapter/article. They are tagged within the element <disp-quote>. If the element is used for quotations, the attribute @content-type is not required.

<disp-quote>
  <p>Now is the winter of our discontent.</p>
  <attrib>William Shakespeare, Richard III</attrib>
</disp-quote>

Footnotes

Footnotes are placed where they are in the text using the element <fn>.

<p>This is a normal paragraph with a footnote.<fn id="b_9783110339406-005_fn_002" symbol="2"><p>I am the footnote for a normal paragraph.</p></fn></p>

<fn id="b_9783110339406-005_fn_003" symbol="3"><label>Translation:</label><p>I am a special footnote for a normal paragraph.</p></fn>

<fn fn-type="endnote" id="b_9781501513152-002_fn_001" symbol="1">
  <p>In <italic>Magical Imaginations: Instrumental Aesthetics in the English Renaissance</italic> (Toronto: University of Toronto Press, 2012), Genevieve Juliette Guenther discusses the motif of the poet as magician in the 1590 <italic>Faerie Queene</italic> and <italic>The Tempest</italic> (4).</p>
</fn>

Formatted Paragraphs

To format whole paragraphs, use the attribute @content-type within the element <p>.

Attribute: @content-type

Attribute values: center, right, spaced, no_indent

<p content-type="center">This is some centered text.</p>

Paragraphs without a @content-type will be left aligned.

Formatted Text

In addition to standard formatting elements such as <bold>, <italic>, <underline>, <monospace>, <sc> for small caps, <sub> for subscript etc., the element <styled-content> can be used. It requires either @style-type attribute for styling or the @xml:lang attribute to tag content in another language.

<styled-content style-type="spaced">some spaced words</styled-content>

The attribute @style must not be used in this context.

<underline underline-style="double">important</underline>

Images and Media Files

Image and Media Files are tagged using the element <fig>. The attributes @id, @position and @fig-type are required. As a default, all image and media files are set to @position="float", except when they have a fixed position in the text (e.g. following a colon), then use @position="anchor".

<fig id="j_hsz-2015-0068_fig_001"  fig-type="figure">
  <label>Figure 1</label>
  <caption>
    <p>I am the caption for Figure 1.</p>
  </caption>
  <graphic xlink:href="graphic/j_hsz-2015-0068_fig_001.jpg"/>
</fig>

<p>The data presented below demonstrates the trends and key variables associated with this phenomenon.</p>
<graphic xlink:href="graphic/b_9783110365344-003_fig_002.tiff"/>
<p>As illustrated in the graphic...</p>

<fig>
  ...
  <permissions>
    <copyright-statement>© 1997 Cold Spring Harbor Laboratory Press</copyright-statement>
    <copyright-year>1997</copyright-year>
    <copyright-holder>Cold Spring Harbor Laboratory Press</copyright-holder>
  </permissions>
</fig>

fig/graphic

<graphic xlink:href="graphic/j_hsz-2015-0068_fig_001.jpg">
  <alt-text>A bell curve ranging from IQ 40 to IQ 160 with a norming sample median raw score defined as IQ 100.</alt-text>
</graphic>

<alt-text>see caption</alt-text>

<alt-text content-type="machine-generated">A bell curve ranging from IQ 40 to IQ 160 with a sample median raw score defined as IQ 100.</alt-text>

<graphic xlink:href="graphic/j_hsz-2015-0068_fig_001.jpg">
  <alt-text>Diagram with 8 dots showing the steady increase of measured weight fractions (in percent) in relation to the process duration (in hours).</alt-text>
  <long-desc>Dot diagram showing the steady increase of measured weight fractions (expressed in percent, ranging from zero to 25 on the y-axis) in relation to the process duration (expressed in hours, ranging from zero to 90 on the x-axis). While the weight fraction is barely 1% after 8 hours, it reaches 21% after 90 hours.</long-desc>
</graphic>

<fig>
  ...
  <alternatives>
    <graphic specific-use="original_epub epub" xlink:href="graphic/b_9783110365344-003_fig_002.png">
      <permissions>
        <copyright-statement>© 2019 Walter de Gruyter GmbH, Berlin/Boston</copyright-statement>
      </permissions>
    </graphic>
    <graphic specific-use="ppub" xlink:href="graphic/b_9783110365344-003_fig_002.tiff">
      <permissions>
        <copyright-statement>© 2018 Walter de Gruyter GmbH, Berlin/Boston</copyright-statement>
      </permissions>
    </graphic>
  </alternatives>
</fig>

<fig id="j_hsz-2015-0068_fig_001" fig-type="figure">
  <label>Figure 1</label>
  <caption> <p>I am the caption for Figure 1.</p> </caption>
  <graphic xlink:href="graphic/j_hsz-2015-0068_fig_001.jpg" specific-use="teaser-image"/>
</fig>

<p>This paragraph has an inline figure <inline-graphic link:href="graphic/b_9783110339406-005_ingr_001.png"/>.</p>

<fig id="j_hsz-2015-0068_audio_004"  fig-type="audio">
  <label>Audio 4</label>
  <caption>
    <p>gives an audio clip.</p>
  </caption>
  <media mimetype="audio/mpeg" mime-subtype="mpeg" xlink:href="media/j_hsz-2015-0068_audio_0047.mp3"/>
  <media mimetype="audio/mp4" mime-subtype="mp4" xlink:href="media/j_hsz-2015-0068_audio_004.m4a"/>
</fig>

<fig id="j_hsz-2015-0068_video_001"  fig-type="video">
  <label>Video 1</label>
  <caption>
    <p>gives a video clip.</p>
  </caption>
  <media mimetype="video/mp4" mime-subtype="mp4" xlink:href="media/j_hsz-2015-0068_video_001.mp4"/>
  <media mimetype="video/webm" mime-subtype="webm" xlink:href="media/j_hsz-2015-0068_video_001.webm"/>
</fig>

<fig fig-type="video" id="b_9783110365344-003_video_002" position="anchor">
  <label>Video 2</label>
  <caption><p>gives a video clip.</p></caption>
  <alternatives>
    <media mime-subtype="mp4" mimetype="video/mp4" xlink:href="media/b_9783110365344-003_video_001.mp4"/>
    <media mime-subtype="webm" mimetype="video/webm" xlink:href="media/b_9783110365344-003_video_001.webm"/>
    <graphic xlink:href="media/b_9783110365344-003_video_001.jpg" specific-use="print-only"/>
  </alternatives>
</fig>

<media mimetype="video/mp4" mime-subtype="mp4" xlink:href="media/j_hsz-2015-0068_video_001.mp4">
  <xref ref-type="custom" custom-type="transcript" rid="j_hsz-2015-0068_transcript_001"/>
</media>

<app content-type=”transcript”>
  <title>Transcript to video 1</title>
  ...
</app>

<media mimetype="video/mp4" mime-subtype="mp4" xlink:href="media/j_hsz-2015-0068_video_001.mp4">
 <long-desc>The video shows an... </long-desc>
</media>

Tables

Tables should always have @position="float", except when they have a fixed position in the text (e.g. following a colon), then use @position="anchor". Tables must always include the attribute @position. If it contains a caption, a <label> must be included too.

Each <th> and <td> shall not contain a <p> element.

When there are properties that should apply to specific columns in general, (such as @width, @align, @valign), the element <colgroup> may be used.

<table-wrap id="b_9783110339406-005_tab_005" position="float" orientation="portrait">
  <label>Table 5</label>
  <caption>
    <p>I am the caption for Table 5.</p>
  </caption>
  <table>
  <colgroup>
    <col align="center" width="25%"/>
    <col align="right" width="50%"/>
    <col valign="bottom" width="25%"/>
  </colgroup>
    <thead>
      <tr>
        <th>City</th>
        <th>Name</th>
        <th>Country</th>
      </tr>
    </thead>
    <tbody>
      <tr>
        <td>Berlin</td>
        <td>Bernd</td>
        <td>Belgium</td>
      </tr>
      ...
    </tbody>
  </table>
</table-wrap>

Table headers should always be captured using the elements <thead> and <th>.

<thead>
  <tr>
    <th valign="top">Name</th>
    <th align="right" valign="top">Year</th>
    <th align="right" valign="top">Place</th>
  </tr>
  <tr>
    <th colspan="3">A horizontal Ruler<hr/></th>
  </tr>
</thead>

<thead>
  <tr>
    <th>Year<break/>1990</th>
    <th>Year<break/>2000</th>
    <th>Year<break/>2010</th>
    <th>Explanation</th>
  </tr>
</thead>

<table-wrap-foot>
  <fn-group>
    <fn><p>* Data not available for 1 trial. <sup>a</sup>P&lt;0.05 (random effects model).</p></fn>
  </fn-group>
</table-wrap-foot>

<td style="color: #7799ff; background-color: #dddddd;">City</td>

Lists

Lists are tagged using the element <list>, the @list-type attribute must be used to specify the type.

Attribute: @list-type

Attribute values: order, bullet, alpha-lower, alpha-upper, roman-lower, roman-upper, simple, custom

<list list-type="order">
  <title>Cities</title>
  <list-item>
    <p>Berlin</p>
  </list-item>
  <list-item>
    <p>London</p>
  </list-item>
</list>

The element <label> must only be used in combination with @list-type="custom".

<list id="j_hsz-2013-0008_list_003" list-type="order">
  ...
</list>
<p>...</p>
<list continued-from="j_hsz-2013-0008_list_003" list-type="order">
  ...
</list>

<list list-type="custom">
  <list-item>
    <label>Step 1</label>
    <p>Read the instructions.</p>
  </list-item>
  <list-item>
    <label>Step 2</label>
    <p>Understand it.</p>
  </list-item>
  <list-item>
    <label>Step 3</label>
    <p>Ask questions.</p>
  </list-item>
</list>

<list list-type="custom">
  <list-item>
    <label>–</label>
    <p>Option One</p>
  </list-item>
  <list-item>
    <label>–</label>
    <p>Option Two</p>
  </list-item>
</list>

Equations and Formula

For mathematical equations and formulas the MathML, Tex Math and graphics equivalents are required for each entry. It is also recommended to include Tex Math. These ways to display equations/formulas must be combined in the XML file with the element <alternatives>.

The namespace of MathML must be declared in the <article>/<book> tag with the attribute @xmlns:mml="http://www.w3.org/1998/Math/MathML (see section Namespaces).

Tag all mathematical formula with <inline-formula>/<disp-formula>. Use them to tag mathematical expressions only, not single characters (such as "ℝ" or "π").

Within the <tex-math> the delimiters that are normally used to switch into and out of math mode must be omitted. Please make sure to validate the TeX sections for each delivery.

<inline-formula>
  <alternatives>
    <inline-graphic xlink:href="graphic/b_9783110339406-005_eq_001.png"/>
    <mml:math>
      <mml:mrow>
        <mml:msup>
          <mml:mi>L</mml:mi>
          <mml:mi>p</mml:mi>
        </mml:msup>
        <mml:mspace width="0.166667em"/>
       <mml:mrow>
        <mml:mo>(</mml:mo>
        <mml:mn>1</mml:mn>
        <mml:mo>&lt;</mml:mo>
        <mml:mi>p</mml:mi>
        <mml:mo>&lt;</mml:mo>
        <mml:mi>∞</mml:mi>
        <mml:mo>)</mml:mo>
      </mml:mrow>
    </mml:mrow>
  </mml:math>
  <tex-math><![CDATA[L^p\,(1<p<\infty )]]></tex-math>
  </alternatives>
</inline-formula>

<disp-formula id="b_9783110339406-005_eq_002">
  <label>(2)</label>
  <alternatives>
    <graphic xlink:href="graphic/b_9783110339406-005_eq_002.png"/>
    <mml:math>
      <mml:mstyle displaystyle="true" scriptlevel="0">
        <mml:mi mathvariant="normal">Δ</mml:mi>
        <mml:mi>x</mml:mi>
        <mml:mi mathvariant="normal">Δ</mml:mi>
        <mml:mi>p</mml:mi>
        <mml:mo>≥</mml:mo>
        <mml:mfrac>
          <mml:mn>1</mml:mn>
          <mml:mn>2</mml:mn>
        <mml:/mfrac>
        <mml:mi class="MJX-variant">ℏ</mml:mi>
      <mml:/mstyle>
    <mml:/math>
    <tex-math><![CDATA[\displaystyle \Delta x \Delta p \geq \frac{1}{2} \hbar]]></tex-math>
  </alternatives>
</disp-formula>

Equations with multiple labels

If an equation needs to contain multiple labels to cite different parts of it (see Figure 1, the element <disp-formula-groups> must be used. The equation should be split into single <disp-formula>.

Example:

<disp-formula-group>
  <disp-formula id="b_9783110339406-005_eq_001">
    <label>(1)</label>
    <alternatives>
      <graphic xlink:href="graphic/b_9783110339406-005_eq_001.png"/>
      <mml:math>
        <mml:mrow>...</mml:mrow>
      </mml:math>
      <tex-math>...</tex-math>
    </alternatives>
  </disp-formula>
  <disp-formula id="b_9783110339406-005_eq_002">
    <label>(2)</label>
    <alternatives>
      <graphic xlink:href="graphic/b_9783110339406-005_eq_002.png"/>
      <mml:math>
        <mml:mrow>...</mml:mrow>
      </mml:math>
      <tex-math>...</tex-math>
    </alternatives>
  </disp-formula>
</disp-formula-group>

Complex Equations

For equations that are very complex (see Figure 2) and for this reason can not be represented in MathML, the element <mml:math> may be omitted. They are tagged with <disp-formula @content-type="complex">:

Example:

<disp-formula id="b_9783110339406-005_eq_002" content-type="complex">
  <label>(2)</label>
  <alternatives>
    <graphic xlink:href="graphic/b_9783110339406-005_eq_002.png"/>
    <tex-math><![CDATA[...]]></tex-math>
  </alternatives>
</disp-formula>

Margin Numbers

Margin numbers are tagged using the element <named-content> including the required attributes @content-type="margin-number"and @id. Additionally the attribute @id shall be present within the parapgraph element containing the margin number.

<p id="b_9783110339406-005_mn_018"><named-content content-type="margin_number">18</named-content>§ 186 entspricht nahezu wortgleich der Vorgängerregelung.</p>

Line Numbers

The elements <milestone-start> and <milestone-end> mark the line, where a line-number should be associated with. The attributes @id and @rationale="line" are required for <milestone-start>. The element <named-content> including the required attribute @content-type="line-number" contains the line number itself.

<p>
  <milestone-start id="j_hsz-2015-0068_line_001" rationale="line"/><named-content content-type="line_number">1</named-content>Mithin müßen diese Bilder allgemein<milestone-end/>
  <milestone-start id="j_hsz-2015-0068_line_002" rationale="line"/><named-content content-type="line_number">2</named-content>und schon für sich verständlich gewesen seyn.<milestone-end/>
</p>

If the line number could be generated (e.g. if whole chapters use line-numbers and there is no reference to a specific line necessary), the line-number should be omitted.

<p>
  <milestone-start id="j_hsz-2015-0068_line_001" rationale="line"/>Mithin müßen diese Bilder allgemein<milestone-end/>
</p>

Please do not use this tagging for songs, poems or verses, use <verse-group> instead.

Verse

Songs, poems or verses are tagged within the element <verse-group>, each <verse-line> represents a poem or verse line.

<verse-group>
  <verse-line>Some say the world will end in fire,</verse-line>
  <verse-line>Some say in ice.</verse-line>
  <attrib>—Robert Frost “Fire and Ice”</attrib>
</verse-group>

If line numbers are necessary, this information must to be tagged for each verse line using the element <named-content> including the attribute @content-type="line_number".

<verse-line><named-content content-type="line_number">3</named-content>Some say the world will end in fire,</verse-line>

<fig id="j_hsz-2015-0068_verse_001" position="anchor" fig-type="verse">
  <graphic xlink:href="graphic/j_hsz-2015-0068_verse_001.jpg"/>
</fig>

Tree Structure

Content that is represented as a tree structure, such as syntactic trees, must be tagged as <fig fig-type="tree">.

<fig id="j_hsz-2015-0068_tree_001" position="anchor" fig-type="tree">
  <graphic xlink:href="graphic/j_hsz-2015-0068_tree_001.jpg"/>
</fig>

Please note that this should only be used if there are only a few incidences of tree structures.

Speech

Speeches within the text are tagged using the element <speech>.

<speech>
  <speaker>Speaker 1:</speaker>
  <p>I have to say something.</p>
</speech>
<speech>
  <speaker>Speaker 2:</speaker>
  <p>Me too.</p>
</speech>

Preformatted text

This section has been replaced by Transcriptions.

Transcriptions

Transcriptions are a systematic representations of language and are usually displayed in a monospace font to preserve character alignment. This is used to indicate multiple persons speaking at the same time or overlapping each other. Transcriptions shall be tagged using the element <preformat>. The attribute @preformat-type="transcription" is required.

<preformat preformat-type="transcription">
00 A: also ich bin [der meinung dass man hier 
00 B:              [du lässt mich ja [nicht 
00 C:                                [aber 
   A: zunächst einmal   ] 
   B: mal ganz aus]reden] 
   C: echt ey     ] 
00 A:                das stimmt doch gar nicht
</preformat>

Attribute: @preformat-type

Attribute Value: transcription

Programming Code

To tag technical content such as programming language code, pseudo-code, schemas, or a markup fragment, the element <code> must be used. To distinguish between different languages, the attribute @language should be used.

<code language="javascript">function myFunction() {
    var x, text;
    x = document.getElementById("numb").value;
    if (isNaN(x) || x < 1 || x > 10) {
        text = "Input not valid";
    } else {
        text = "Input OK";
    }
    document.getElementById("demo").innerHTML = text;
}</code>

When a label and/or caption is required, the element <code> must be wrapped within <fig fig-type="code"> including the element <label> and/or <caption>. If these elements are not present, <fig> must not be used.

<fig id="j_cmam-2016-0011_code_002" fig-type="code">
  <label>Listing: 8</label>
  <caption>
    <p>This is a code listing of a crazy script.</p>
  </caption>
  <code language="bash">#!/bin/bash
# script for creating standalone PDFs of depending figures of our article.
# note: due to random score simulations underlying these examples, PDFs will slightly differ by each run.
# note: on first run, if an environment needs to be set-up from scrath, it may take 10 minutes - otherwise: &lt; 1 minute.
           
mkdir -p /results/tex
mkdir -p /results/pdf
...</code>
</fig>

<p>The syntax of the JavaScript <monospace>for ... in<monospace> loop is as follows:</p>

Interlinear gloss

An interlinear gloss is used to help the reader follow the relationship between the source text and its translation, and the structure of the original language [45]. To preserve this relationship, they're tagged using tables. This table must be placed within <boxed-text>, whenever there's a new division between examples (new numbering), these parts need to be put into separate table and boxed-text elements. (The attribute @content-type="ling_example" is required in this context.)

<boxed-text content-type="ling_example" id="b_9783110339406-005_box_001">
  <label>(1)</label>
  <boxed-text content-type="ling_example">
    <label>a.</label>
    <table-wrap position="anchor" orientation="portrait">
      <table>
        <tbody>
          <tr>
            <td><italic>Red mored</italic></td>
            <td><italic>penter</italic></td>
            <td><italic>rowa</italic></td>
            <td><italic>lulus</italic></td>
            <td><italic>tes.</italic></td>
          </tr>
          <tr>
            ...
          </tr>
        </tbody>
      </table>
      <table-wrap-foot>
        <p>‘Those smart students passed the test.’</p>
      </table-wrap-foot>
    </table-wrap>
  </boxed-text>
</boxed-text>

These instructions should be used in conjunction with the De Gruyter Style Guide, section “Interlinear type, discourse transcriptions” [46].

There are very rare instances in which it is not possible to represent the gloss using a table. In those cases, a graphic may be used.

<boxed-text content-type="ling_example" id="j_lingvan-2024-0068_box_001">
  <label>(1)</label>
  <graphic xlink:href="graphic/j_lingvan-2024-0068_fig_026.jpg"/>
</boxed-text>

Formal statements

Formal statements such as theorems are tagged using the element <statement> including the required attribute @content-type. Within each statement the element <title> or <label> and at least one <p> element must be present.

Attribute: @content-type

Attribute values: theorem, proposition, lemma, assertion, corollary, proof, premise, example, remark, definition, assumption, result, notation, conclusion, problem, exercise, algorithm, solution, claim, fact, hint, summary, benefits, mode, description

<statement content-type="premise">
  <title>Premise 1</title>
  <p>XML is good.</p>
</statement>

Textual Material

Textual Material such as examples, tasks and summaries are tagged within the element <boxed-text> including the required attributes @content-type and @id. Within this element more complex content is possible by adding multiple sections.

Attribute: @content-type

Attribute values: example, learningtarget, takehomemessage, summary, margin, solution, exercise, question, consider, attention, info, other

When converting boxes defined within our guidelines [46], the following @content-types apply:

Housestyle Icon	@content-type
	attention
	info
	exercise
	consider
	question

<boxed-text id="b_9783110339406-005_box_003" content-type="example">
  <label>Example 3</label>
  <p>This is an example</p>
</boxed-text>

Margins

If text parts should not be placed within the normal text flow, but within the margin, the attribute @position="margin" should be used. This shall only be used within the following contexts:

• <boxed-text>

• <graphic>

• <media>

• <supplementary-material>

<boxed-text id="b_9783110365344-003_box_015"
               position="margin"> <p>This is a Margin Text.</p> </boxed-text>

Columns/Spaltensatz

Content that has a strict left-right relationship shall be tagged within the element <array> using tables.

<array>
  <tbody>
    <tr>
      <td>Suborder</td>
      <td><sc>Goniatitina</sc> (Hyatt, 1884)</td>
    </tr>
    <tr>
      <td>Superfamily</td>
      <td><sc>Pericyclaceae</sc> (Hyatt, 1900)</td>
    </tr>
  </tbody>
</array>

Links

<p>...this has been proofed by <xref ref-type="bibr" rid="j_hsz-2015-0068_ref_023">Smith (1999)</xref>.</p>
<p><xref ref-type="fig" rid="j_hsz-2015-0068_fig_011">Figure 11</xref> shows the developement of... .</p>
<p>As described within section <xref ref-type="sec" rid="j_hsz-2015-0068_s_008_s_001">8.1</xref> the effect regarding... .</p>
<p>This has been shown within equation (<xref ref-type="disp-formula" rid="j_hsz-2015-0068_eq_021">21</xref>).</p>

[<xref>1</xref>], [<xref>2</xref>], [<xref>3</xref>]

<p>Bergbauberechtigungen, die vor Inkrafttreten des Bundesberggesetzes erteilt worden sind, werden unter den Voraussetzungen des <xref ref-type="norm" rid="b_9783899498776_n_149">§ 149</xref> mit zahlreichen Maßgaben in das neue Berechtsamssystem überführt <xref ref-type="norm" rid="b_9783899498776_n_151">(§§ 151 ff.)</xref>; für die Aufsuchung und Gewinnung von Bodenschätzen, die Gegenstand dieser Berechtigungen sind, bedarf es keiner neuen Bergbauberechtigung <xref ref-type="norm" rid="b_9783899498776_n_149">(§ 149 Abs. 7).</xref></p>

<p>Beim Einsatz entsprechender Bewertungstools zur automatisierten Festlegung der jeweils erforderlichen Maßnahmen handelt es sich nicht um Scoring i. S. d. § 28b BDSG, sodass die einschränkenden Voraussetzungen dieser Norm hier keine Anwendung finden (siehe dazu oben <xref ref-type="margin-number" rid="b_9783899498776-002_s_003_s_001_mn_067">Rn 67</xref>).</p>

<ext-link ext-link-type="uri" xlink:href="http://www.degruyter.com">
  De Gruyter Online
</ext-link>

<ext-link ext-link-type="uri" xlink:href="https://jats.nlm.nih.gov/index.html">
  https://jats.nlm.nih.gov/index.html
</ext-link>

<ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1515/aot-2013-0054">
  https://doi.org/10.1515/aot-2013-0054
</ext-link>

Page Breaks

As of June 28, 2025, these requirements will be updated. In the current version, compliance is recommended. With the forthcoming update (version 2.1), compliance will become mandatory ("must").

If requested, page breaks may be included using the element <target> to tag the start of a new page. If used, the attributes @id and @target-type must be present.

<target id="page-20" target-type="next-page">20</target>

Please note that <target> shall not be placed within footnotes, links or references.

Universal trial number

/article/back/sec[@sec-type="clinical-trial"]

If applicable, the universal trial number (UTN) must be specified. A UTN is a unique number generated by WHO for each clinical trial registered in one of the WHO primary registries. It is intended to facilitate study identification and is displayed on the WHO International Clinical Trials Registry Platform (ICTRP) search portal [38].

The UTN must be published as a separate section (sec[@sec-type="clinical-trial"]) within the <back>. Within that section the element <related-object> should contain the Clinical Trail statement as well as the following attributes:

<back>
  ...
  <sec id="j_cclm-2024-1234_s_034" sec-type="clinical-trial">
    <title>Clinical trial registration</title>
    <related-object id="RO1" source-type="clinical-trials-registry" source-id="https://ClinicalTrials.gov" source-id-type="registry-name" document-id="NCT02550236" document-id-type="clinical-trial-number" xlink:href="https://clinicaltrials.gov/show/NCT02550236" >
     This study is registered with http://ClinicalTrials.gov as NCT02550236.
    </related-object>
  </sec>
</abstract>

Supplementary Material Note

/article/back/notes[@notes-type="supplement"]

/book/book-back/notes[@notes-type="supplement"]

//book-part/back/notes[@notes-type="supplement"]

The element <notes> with the attribute @notes-type="supplement" must contain additional information regarding the Supplementary Material, that is attached to the article or chapter.

Instructions how to tag the link to the Supplementary Material file can be found within section Supplementary Material.

<notes notes-type="supplement" id="j_hsz-2015-0068_notes_001" specific-use="print-only">
  <sec>
    <title>Supplementary Material</title>
    <p>This publication contains supplementary materialThe online version of this article offers supplementary material (DOI:<ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1515/hsz-2015-0068">https://doi.org/10.1515/hsz-2015-0068</ext-link>).</p>
  </sec>
</notes>

Acknowledgements

/article/back/ack

/book/front-matter/ack

/book/book-back/ack

The element <ack> includes the acknowledgments of an article, book or chapter. If there is funding information mentioned in the acknowledgements please extract and place it within the tag <funding-group>. (See section Funding Information.)

<ack id="b_9783110339406-005_ack_001">
  <title>Acknowledgements</title>
  <p>We thank B. Beltchev for purification of Hfq, S. Cusack and A. J. Carpousis for the gift of PAP I, A. Ishihama for Hfq antibodies used in Hfq purification.</p>
</ack>

<ack id="b_9783110339406-005">
  <sec-meta>
    <object-id pub-id-type="doi">10.1515/9783110339406-005</object-id>
    <self-uri content-type="pdf" xlink:href="9783110339406-005.pdf"/>
  </sec-meta>
  <title>Acknowledgements</title>
  <p>We thank B. Beltchev for purification of Hfq, S. Cusack and A. J. Carpousis for the gift of PAP I, A. Ishihama for Hfq antibodies used in Hfq purification.</p>
</ack>

Additional Information

/book/book-back/fn-group/fn

//book-part/back/fn-group/fn

/article/back/fn-group/fn

This element contains additional information to the article, chapter or book which aren’t part of the narrative flow. In comparison to the <note> element, <fn-group> is used, when the information can be specified clearly according to the predefined list of @fn-type values within the element <fn>. The attribute @fn-type is required.

Attribute: @fn-type

Attribute values: conflict, com, con, financial-disclosure, presented-by, presented-at, other

<fn-group>
  <fn fn-type="presented-at">
    <p>This paper has been presented previously at the International Standards Conference.</p>
  </fn>
  <fn fn-type="conflict">
    <p><bold>Conflicts of interest:</bold>The funding organization(s) played no role in the study design; in the collection, analysis, and interpretation of data; in the writing of the report; or in the decision to submit the report for publication</p>
  </fn>
  <fn fn-type="com">
    <p><bold>Communicated by:</bold> Marianne Grunberg-Manago, Institute of Physico-Chemical Biology, Paris, France</p>
  </fn>
  <fn id="j_almed-2019-0012_fn_006" fn-type="other">
    <p><bold>Article Note:</bold> A translation of this article can be found here:
    <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1515/almed-2019-0009" >https://doi.org/10.1515/almed-2019-0009</ext-link></p>
  </fn>
</fn-group>

Please see the following table for a mapping between specific information and the corresponding @fn-type:

* Funding Information, that includes a funding agency and award identifier, must be tagged using <funding-group>

** This applies to Book XML deliveries only.

<fn-group>
  <title>Author’s statement</title>
  <fn fn-type="conflict" id="j_bnm-2017-0002_s_998">
    <p><bold>Conflict of interest:</bold> Authors state no conflict of interest.</p>
  </fn>
</fn-group>
<fn-group>
  <title>Materials and methods</title>
  <fn fn-type="other" id="j_bnm-2017-0002_s_996">
    <p><bold>Informed consent:</bold> Informed consent has been obtained from all individuals
       included in this study.</p>
  </fn>
  <fn fn-type="other" id="j_bnm-2017-0002_s_995">
    <p><bold>Ethical approval:</bold> The research related to human use has been complied with
      all the relevant national regulations, institutional policies and in accordance the tenets
      of the Helsinki Declaration, and has been approved by the authors’ institutional
      review board or equivalent committee.</p>
  </fn>
</fn-group>

Notes

/article/back/notes

/book/book-back/notes

//book-part/back/notes

The element <notes> contains notes to the article/chapter which aren’t part of the narrative flow but must be placed to the article/chapter (e.g. a prepublication information) and can't be expressed within fn-group/fn[@fn-type] information (see section Additional Information).

Attribute: @notes-type

Attribute values: prepublication, software

<notes notes-type="prepublication" id="b_9783110339406-005_notes_002">
  <p>This article has been previously published within the Journal of Standards.<p>
</notes>

<notes notes-type="software" id="j_snde-2018-1234_notes_002">
  <sec>
    <title>Code and Datasets</title>
    <p>The author(s) published code and data associated with this article is on Code Ocean, a computational reproducibility platform. We recommend Code Ocean to SNDE contributors who wish share, discover, and run code in published research articles. (See: <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.24433/CO.154591c8-9d3f-47eb-b656-3aff245fd5c1">https://doi.org/10.24433/CO.154591c8-9d3f-47eb-b656-3aff245fd5c1</ext-link>)</p>
  </sec>
</notes>

Glossary

/book/back/glossary

/book/book-back/glossary

//book-part/back/glossary

/article/back/glossary

Lists of terms and definitions are tagged using the element <glossary>. It contains the element <term> and, if applicable, a definition <def>. In order to add the DOI information, it must be included into an <sec> element containing the <object-id> .

<sec>
  <object-id pub-id-type="doi">10.1515/9783110339406-003</object-id>
<glossary>
  <sec-meta>
    <object-id pub-id-type="doi">10.1515/9783110339406-003</object-id>
    <self-uri content-type="pdf" xlink:href="9783110339406-003.pdf"/>
  </sec-meta>
  <title>Glossary</title>
  <def-list>
    <def-item>
      <term>A cappella</term>
      <def><p>Vocal music without instrumental accompaniment.</p></def>
    </def-item>
    <def-item>
      <term>Abgesang</term>
      <def><p> Second section of the → Barform.</p></def>
    </def-item>
    <def-item>
      <term>Accentus</term>
      <def><p>In contrast with → concentus, a style of singing which prizes clear delivery (→ syllabic style, melodic sobriety) over aesthetic beauty.</p></def>
    </def-item>
  </def-list>
</glossary>
</sec>

References

/book/back/ref-list

/book/book-back/ref-list

//book-part/back/ref-list

/article/back/ref-list

References are required within the element <ref> in two ways: To preserve spacing and punctuation <mixed-citation> must to be used. Within <element-citation> all detailed tagged information is required and the element does not include untagged text, spacing or punctuation.

If references are numbered, the <label> must be used within <ref> directly rather than within <element-citation> or <mixed-citation>.

<ref-list id="b_9783110339406-005_reflist_001">
  <title>III. Kommentierte Literaturhinweise</title>
  <p>Einführungen und Überblicksdarstellungen zur Sprachphilosophie:</p>
  <ref id="b_9783110339406-032_ref_023">
    <label>[23]</label>
    <mixed-citation>Petitti DB, Crooks VC, Buckwalter JG, Chiu V. Blood pressure levels before dementia. Arch Neurol. 2005 Jan;62(1):112-116. <pub-id pub-id-type="doi">10.1515/cclm-2015-0068</pub-id>
    </mixed-citation>
    <element-citation publication-type="journal" publication-format="print">
      <name><surname>Petitti</surname><given-names>DB</given-names></name>
      <name><surname>Crooks</surname><given-names>VC</given-names></name>
      <name><surname>Buckwalter</surname><given-names>JG</given-names></name>
      <name><surname>Chiu</surname><given-names>V</given-names></name>
      <etal/>
      <article-title>Blood pressure levels before dementia</article-title>
      <source>Arch Neurol</source>
      <year>2005</year>
      <month>Jan</month>
      <volume>62</volume>
      <issue>1</issue>
      <fpage>112</fpage>
      <lpage>116</lpage>
      <pub-id pub-id-type="doi">10.1515/cclm-2015-0068</pub-id>
    </element-citation>
  </ref>
  ...
</ref-list>

Please note, that both reference versions (<mixed-citation> and <element-citation> are required for each <ref>.

For more examples, please visit the PubMed Citation Samples Page [48].

<ref-list id="b_9783110339406-032">
  <sec-meta>
    <object-id pub-id-type="doi">10.1515/9783110339406-032</object-id>
    <self-uri content-type="pdf" xlink:href="9783110339406-032.pdf"/>
    <permissions>
      <copyright-statement>© 2025 Walter de Gruyter GmbH, Berlin/Boston</copyright-statement>
      <copyright-year>2025</copyright-year>
      <copyright-holder>Walter de Gruyter GmbH</copyright-holder>
    </permissions>
  </sec-meta>
  <title>III. Kommentierte Literaturhinweise</title>
  ...
</ref-list>

<article-title>Generalized inf-sup conditions for <italic>Chebyshev</italic> spectral approximation of the Stokes problem</article-title>

<element-citation publication-type="journal" publication-format="print">
  <name><surname>Meneton</surname><given-names>P</given-names></name>
  <name><surname>Jeunemaitre</surname><given-names>X</given-names></name>
  <article-title>Links between dietary salt intake, renal salt handling, blood pressure, and cardiovascular diseases</article-title>
  <source>Physiol Rev</source>
  <year>2005</year>
  <month>Apr</month>
  <volume>85</volume>
  <issue>2</issue>
  <fpage>679</fpage>
  <lpage>715</lpage>
</element-citation>
                  

<element-citation publication-type="book" publication-format="print">
  <name><surname>Jenkins</surname><given-names>PF</given-names></name>
  <source>Making sense of the chest x-ray: a hands-on guide</source>
  <publisher-loc>New York</publisher-loc>
  <publisher-name>Oxford University Press</publisher-name>
  <year>2005</year>
  <size units="page">194 p</size>
</element-citation>

<element-citation publication-type="thesis">
  <name><surname>Liu-Ambrose</surname><given-names>TY</given-names></name>
  <source>Studies of fall risk and bone morphology in older women with low bone mass [dissertation]</source>
  <publisher-loc>[Vancouver (BC)]</publisher-loc>
  <publisher-name>University of British Columbia</publisher-name>
  <year>2004</year>
  <size units="page">290 p</size>
</element-citation>

<element-citation publication-type="database" publication-format="web">
  <source>Faculty of 1000. Medicine [Internet]</source>
  <publisher-loc>London</publisher-loc>
  <publisher-name>Medicine Reports Ltd</publisher-name>
  <year>c2007 - </year>
  <date-in-citation>cited 2007 Feb 1</date-in-citation>
  <comment>Available from: <uri>http://www.f1000medicine.com/</uri>.</comment>
</element-citation>

<element-citation publication-type="webpage">
  <source>AMA: helping doctors help patients [Internet]</source>
  <publisher-loc>Chicago</publisher-loc>
  <publisher-name>American Medical Association</publisher-name>
  <year>c1995-2007</year>
  <date-in-citation>cited 2007 Feb 22</date-in-citation>
  <comment>Available from:<uri>http://www.ama-assn.org/</uri>.</comment>
</element-citation>

<name>
  <surname>Smith</surname>
  <given-names>Johan M.</given-names>
</name>

Appendix

/book/book-back/app-group or /book/book-back/app

//book-part/back/app-group or //book-part/back/app

/article/back/app-group or /article/back/app

<app-group>
   <title>Appendix</title>
   <app id="b_9783110339406-005_app_001">
      <label>A</label>
      <title>Scientific Evidence and Consumers</title>
      …
      <sec>
        <label>A.1</label>
        <title>Consumers</title>
        ...
      </sec>
   </app>
      <app id="b_9783110339406-005_app_002">
      <label>B</label>
      <title>Perceptions of Food Irradiation</title>
      …
   </app>
</app-group>

/book/book-back/book-app-group or /book/book-back/book-app

<book-app>
  <book-part-meta>
    <book-part-id book-part-id-type="doi">10.1515/9783110365344-203</book-part-id>
    <title-group>
      <title>Appendix A</title>
    </title-group>
    <fpage>521</fpage>
    <lpage>532</lpage>
    <counts>
      <book-page-count count="12" count-type="chapter-page-count"/>
    </counts>
  </book-part-meta>
  <body>
    <sec id="b_9783110365344-203_s_001">
      <title>Scientific Evidence and Consumers</title>
      ...
    </sec>
  </body>
</book-app>

File Naming Conventions

hsz-2015-0068.pdf

hsz-2015-0068.xml

9783110339406-002.pdf

9783110339406-002.xml

9783110339406.xml

9783110339406.pdf

9783110339406-002.pdf

9783110339406-002.xml

9783110295207.epub

j_hsz-2013-0068_fig_011.jpg

b_9783110339406-002_fig_003.jpg

cmam.2016.16.issue-1_cover.pdf

cmam.2016.16.issue-1_cover.jpg

{book-delivery-id}=epub_dgo_{eISBN_pdf}.zip

epub_dgo_9783110339406.zip

{book-delivery-id}=xml_cont_{isbn}.zip

xml_cont_9783110295207.zip

{issue-delivery-id}={journal-code-online}_{issue-id}_{timestamp}.zip

bchm_bchm.2012.1.issue-2_2013-06-10--18-45-01.zip

{article-delivery-id}={journal-code-online}_{article-id}_{article-delivery-type}_{timestamp}.zip

bchm_hsz-2012-0006_ja_2013-06-28--10-30-25.zip

bchm_hsz-2013-0010_aop_2013-05-16--14-30-25.zip

Folder structure and content

epub_dgo_{eISBN_pdf}.zip
|--{eISBN_pdf}.xml
|--{eISBN_epub}.epub
|--{eISBN_pdf}.pdf
|--{eISBN_pdf}-{chapter-suffix}.xml
|--{eISBN_pdf}-{chapter-suffix}.pdf
|--{eISBN_pdf}-{chapter-suffix}.xml
|--{eISBN_pdf}-{chapter-suffix}.pdf
|--graphic
|  |--{element-id}.jpg
|  |--...
|--suppl
|  |--{filename}.{fn-ext}
|  |--...
|--media
|  |--{element-id}.m4a
|  |--{element-id}.mp3
|  |--...

epub_dgo_{eISBN_pdf}.zip
|--{eISBN_pdf}
|  |--{eISBN_pdf}
|  |  |--{eISBN_pdf}.xml
|  |  |--{eISBN_epub}.epub
|  |  |--{eISBN_pdf}.pdf
|  |--{eISBN_pdf}-{chapter-suffix}
|  |  |--{eISBN_pdf}-{chapter-suffix}.xml
|  |  |--{eISBN_pdf}-{chapter-suffix}.pdf
|  |--{eISBN_pdf}-{chapter-suffix}
|  |  |--{eISBN_pdf}-{chapter-suffix}.xml
|  |  |--{eISBN_pdf}-{chapter-suffix}.pdf
|  |  |--graphic
|  |  |  |--{element-id}.jpg
|  |  |  |--...
|  |  |--suppl
|  |  |  |--{filename}.{fn-ext}
|  |  |  |--...
|  |  |--media
|  |  |  |--{element-id}.m4a
|  |  |  |--{element-id}.mp3
|  |  |  |--...

xml_cont_{isbn}.zip
|--{isbn}.xml
|--graphic
|  |--{element-id}.jpg
|  |--...
|--media
|  |--{element-id}.m4a
|  |--{element-id}.mp3
|  |--...
|--suppl
|  |--{filename}.{fn-ext}
|  |--...

{journal-code-online}_{issue-id}{timestamp}.zip
|--{issue-id}
|  |--{article-id}
|  |  |--{article-id}.xml	
|  |  |--{article-id}.pdf
|  |  |--graphic
|  |  |  |--figure files
|  |  |--suppl
|  |  |  |--supplementary files
|  |  |--media
|  |  |  |--media files 
|  |--{frontmatter-id}
|  |  |--{frontmatter-id}.xml
|  |  |--{frontmatter-id}.pdf
|  |--{graphical-abstract-id}
|  |  |--{graphical-abstract-id}.xml
|  |  |--{graphical-abstract-id}.pdf
|  |--issue-files
|  |  |--{issue-id}.xml
|  |  |--{issue-id}_cover.pdf

{journal-code-online}_{article-id}_{article-delivery-type}_{timestamp}.zip
|--{journal-code-online}.ahead-of-print	OR
|--{journal-code-online}.just-accepted
|  |--{article-id}
|  |  |--{article-id}.xml	
|  |  |--{article-id}.pdf
|  |  |--graphic
|  |  |  |--figure files
|  |  |--suppl
|  |  |  |--supplementary files
|  |  |--media
|  |  |  |--media files

{journal-code-online}_{article-id}_oi_{timestamp}.zip
|--{article-id}.open-issue
| |--{article-id}
| | |--{article-id}.xml
| | |--{article-id}.pdf
| | |--graphic
| | | |--figure files
| | |--suppl
| | | |--supplementary files
| | |--media
| | | |--media files 
|--issue-files
| |--{issue-id}.xml

Supplementary Material

Please always create an additional folder named “suppl” which contains the supplementary material for an article, a book chapter or the whole book. Please place the “suppl” folder in the book-chapter or article folder it belongs to.

These files are allowed for supplementary material:

html | htm | css | ico | js | pdf | png | jpeg | jpg | gif | xls | xlsx | doc | docx | csv | txt | ppt | flv | fla | mrc | mpg | mpeg | zip | mov | csv | wmv | rar | pptx | tsv | wma | avi | mp4 | m4v | cif | ogg | webm | oga | weba | acc | mp3 | epub | wav | odt | ods | odp | dot | dotx | m4a

In case you receive files in a different format than mentioned above please put them in a zip file which combines all supplementary data.