Guide to

WileyML 3G
Wiley's Unified XML
Content Model

Document History

Version Date Authors Comments

1 March 30, 2009 Steve Arany, Charo Bajo, Lindy Humphreys, Sharon Marshall, First public release
Simon Newton, John Pedersen, Davis Salisbury, Kevin Smith,
Kimi Sugeno, Ulrike Winter

2 September 7, 2009 Davis Salisbury Updates for v1.0.1

3 October 22, 2010 Sharon Marshall, Simon Newton, John Pedersen, Davis Updates for v1.0.3: changes in
Salisbury, Kimi Sugeno sections 1.4, 2.3, 5.2, 9.1,10.5-
10.7, 12.1, 12.3, 12.4, 12.6-12.8,
12.12, 13.1, 14, Appendix 1,2
4 June 2011 Sharon Marshall, John Pedersen Updates for v2.0: changes in
sections 1.1, 1.4, 2.2, 2.3, 2.4,
4.1, 4.2, 5.2, 12.6, 12.8, 12.12,
14. New sections: 1.5, 6.4, 9.3,
10.8, 10.9
5 September 4, 2012 John Pedersen Section 9.3.2: corrected typo
“JHET” to “jhet” in example.
6 April 23, 2013 Sharon Marshall, John Pedersen v.wiley.com:3535 changed to
vendors.wiley.com in URLs
throughout; Sections 12.6, 12.8
amended; Section 14 DOI entry
corrected; App 1 entry for CP
part corrected;
7 August 18, 2016 Steve Arany/Sharon Marshall Removed
"clIssueEditedVersionPublished"
from Appendix A (no longer an
allowed value for
number/@type).
Edited section 1.5 to allow for
UTF-8 characters, if directed by
Wiley.
8 February, 2019 Steve Arany Removed references to WileyML
2.1
Removed WileyPLUS section 11
Updated other content as
necessary for current
applications
9 December, 2020 Steve Arany All vendors.wiley.com URLs
changed to use "https".

2
Table of Contents

1 Introduction .................................................................................................................... 6
1.1 Overview ............................................................................................................................. 6
1.2 Naming ................................................................................................................................ 6
1.3 Elements and Attributes ...................................................................................................... 6
1.4 Attribute Values .................................................................................................................. 6
1.5 Character Encoding and Character Entities: XML and DOCTYPE Declarations ....................... 7
2 Structure ......................................................................................................................... 8
2.1 General ............................................................................................................................... 8
2.2 The Header: Publication and Content Metadata .................................................................. 8
2.3 The Body ............................................................................................................................. 9
2.4 Sections ............................................................................................................................. 10
3 Titles ............................................................................................................................. 10
3.1 General ............................................................................................................................. 10
3.2 Table of Contents .............................................................................................................. 10
4 Numbering .................................................................................................................... 11
4.1 Regular Numbering............................................................................................................ 11
4.2 Irregular Numbering: <label> and resumeNumberingAt ........................................... 11
5 Fixed and Floating Objects ............................................................................................ 12
5.1 General ............................................................................................................................. 12
5.2 <objectNameGroup>.................................................................................................... 13
6 Figures and Figure-Like Objects ..................................................................................... 15
6.1 General ............................................................................................................................. 15
6.2 Nonstandard Names (Illustrations, Plates, Schemes, etc.) .................................................. 16
6.3 Figures with Parts .............................................................................................................. 17
6.3.1 Captions .............................................................................................................................................. 17
6.3.2 Multipart Figures with Parts in a Single File ....................................................................................... 18
6.3.3 Multipart Figures with Parts in Multiple Files..................................................................................... 18
6.4 Figures with Notes ............................................................................................................. 20
7 Sources and Credits ....................................................................................................... 20
1.1 ................................................................................................................................................. 20
8 Theorems, Definitions, etc. ............................................................................................ 21
9 Enriching Content/Semantic Tags .................................................................................. 22

3
 9.1 <infoAsset> ................................................................................................................. 22
9.2 <accessionId>............................................................................................................. 22
9.3 Functional Chemistry ......................................................................................................... 22
9.3.1 <enrichedObjectGroup> ..................................................................................................................... 22
9.3.2 Figures with Regions ........................................................................................................................... 23
10 Journal-Specific Topics ............................................................................................... 24
10.1 Issue Titles ......................................................................................................................... 24
10.2 Supporting Information (Supplementary Material) ............................................................ 24
10.3 Journal TOCs ...................................................................................................................... 24
10.4 Focus Sections ................................................................................................................... 25
10.5 Associated Websites .......................................................................................................... 25
10.6 Alternate Versions ............................................................................................................. 25
10.7 Book Reviews .................................................................................................................... 25
10.8 Books Received ................................................................................................................. 26
10.9 Editorial, Letter to the Editor, Reply, and Erratum ............................................................. 26
11 MRW-Specific Topics ................................................................................................. 27
11.1 Type of Component ........................................................................................................... 27
11.2 Type of Unit ....................................................................................................................... 27
11.3 Difficulty Level ................................................................................................................... 27
11.4 Unit-Specific Subjects ........................................................................................................ 27
11.5 Blind Entries ...................................................................................................................... 28
11.6 Related Articles ................................................................................................................. 28
11.7 “qv” Cross References ....................................................................................................... 28
11.8 “fallback” Cross References and <link>s to External Content ......................................... 28
11.9 Updating Articles ............................................................................................................... 29
11.10 Updated by Staff ........................................................................................................... 29
11.11 Short Entries .................................................................................................................. 29
11.12 Volume Numbers .......................................................................................................... 29
11.13 Print versus Online ........................................................................................................ 30
12 Book- and Book Series-Specific Topics ........................................................................ 30
12.1 Multi-volume Books .......................................................................................................... 30
12.2 Series Metadata ................................................................................................................ 30
12.3 Series Number ................................................................................................................... 30
12.4 Series Volume Number ...................................................................................................... 30

4
 12.5 Sequence in Series ............................................................................................................. 30
13 Content–Element Mapping ........................................................................................ 31
Appendix 1: <numbering> within <publicationMeta> ............................................................ 32
Appendix 2: Graphical Examples ........................................................................................... 32
Journal Article................................................................................................................................ 32
Reference Work Article .................................................................................................................. 32
Book Chapter (Finance) .................................................................................................................. 32
Book Chapter (Programming)......................................................................................................... 32

5
1 Introduction
1.1 Overview
The WileyML 3G XML model aims to cover Wiley content across all locations and divisions, and includes
models for journals, books, MRWs, Current Protocols, content for WileyPLUS, Functional Chemistry,
database-driven content (e.g., The Cochrane Library), and, potentially, for content types yet to be defined.

Our model follows the DSDL paradigm (see www.dsdl.org) and is defined normatively in RELAX NG and
Schematron.

In our model, a “type” attribute is used on more generically named elements rather than using separate
elements for iterative or related items. Users of past versions of WileyML will find fewer elements. This
more generic approach results in more flexibility and easier updating, e.g., adding attribute values rather
than defining new elements.

1.2 Naming
Element naming follows some general rules:
• Elements relating to a specific topic have the same prefix, so that they sort together. For example,
the elements related to lists begin with “list” (<listItem>, <listPaired>, etc.).
• Element names for containers of a single element that may be repeated multiple times end in
“Group”. For example, <titleGroup> may contain several <title>s, but no other immediate
children.
• Element names for containers of differently named children end in “Info”. For example,
<fundingInfo> may contain <fundingAgency> and <fundingNumber>.

1.3 Elements and Attributes

As much as possible this model follows the rule that elements are reserved for items that appear as content,
while attributes are for “metadata” about an element’s content. Attribute values are not expected to appear
explicitly in published content, although they may influence the appearance or functionality of the content.
For example, a “sort title”, which gives a string that determines the position of the actual title in a table of
contents, is modeled as an attribute because the sort title string is not expected to appear explicitly in a
rendered version of the WileyML.

1.4 Attribute Values

Some attribute values are unconstrained, and allow any string of text (e.g., alt for <mediaResource>).
Alternatively, attribute values may be constrained in one of several ways:

a) Defined in the schema. These values are listed in the Attributes table in the Element Reference
Manual, e.g., the numbered attribute that occurs on several elements can only have the values
"yes" and "no"
b) Controlled by a values list. This list can be accessed in the Element Reference Manual by clicking
on the link in the Attributes section. This approach allows updating the model without touching
the schema definition files. Controlled values updates, which are backwards-compatible, can be
released more frequently than schema updates.
c) Declaration in the <attributeValueGroup>. This approach is used for certain type and
similar attributes that have a potentially limitless possible set of values, so cannot be handled with
the controlled values approach, but for which it is still crucial to have consistency within a product.
See the Element Reference Manual pages for attributeValueGroup and attributeValue
for more information.
d) ID and URN schemes defined by the businesses. The values for xml:id, href, and all attributes
whose names end in “Ref” (e.g. affiliationRef) must conform to these schemes. Because
the schemes may vary across content types and divisions, the businesses will supply the
appropriate specification when requesting XML.

6
Defaults: Some optional attributes have a “default” value specified in the Element Reference Manual; if the
attribute is not present in the XML, the default is assumed. For example, the eRights attribute that occurs
on several elements has a default value "yes", so it is only necessary to include the attribute if its value is
"no". Default values may be defined explicitly or, in the following four cases, by inheritance from their
containing elements (inheritance is from the closest containing element on which the value is explicitly
specified): xml:lang (required on <component>); numbered on <section>, <appendix>, and
<protocol>, inherited from sectionsNumbered on <body>; and the style and cited attributes on
<bibSection>, inherited from <bibliography>. See the Element Reference Manual for details. When
an element does not have a default value specified, omission of the attribute does not imply any specific
value for it.

1.5 Character Encoding and Character Entities: XML and DOCTYPE Declarations
WileyML allows different character encoding, based on the requirements of the business. ASCII and UTF-
8 are the most common encodings used at Wiley.

If content uses named character entities (for example, &alpha;), it should have standalone="no" in the
XML declaration and include a DOCTYPE referring to Wiley’s named entity set, (an extension of the W3C
standard "XML Entity Definitions for Characters"), as follows:

<?xml version="1.0" encoding="US-ASCII" standalone="no"?>

<!DOCTYPE WileyML3G [
<!ENTITY % wileyml3g.ent SYSTEM
"https://vendors.wiley.com/schemas/wileyml3g/wiley.ent">
%wileyml3g.ent; ]>

Note that Wiley has defined some characters for special chemical symbols etc. in Unicode’s Private Use
Area: these are defined on the WileyML 3G site and they are included in wiley.ent.

If all character entities are given in numeric form, and no DTD declaration is required, then the XML
declaration should be:

<?xml version="1.0" encoding="US-ASCII" standalone="yes"?>

If all special characters are instead given directly in UTF-8, and no DTD declaration is required, then the
XML declaration would be:

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

7
Some systems, such as Wiley’s Global Ed CMS, require a DTD declaration. The named character entity
definitions from wiley.ent are included in the DTD for WileyML 3G that Wiley makes available. In this case
the XML and DOCTYPE declarations should be, for example:

<?xml version="1.0" encoding="US-ASCII" standalone="no"?>

<!DOCTYPE component PUBLIC "-//JWS//DTD WileyML 20110801 Vers
3Gv2.0//EN" "Wileyml3gv20-flat.dtd">

(or wherever the DTD file is located).

For further details on the use of character entities, refer to this document.

2 Structure
2.1 General
A <component> (the top-level structure) is divided into a <header> and a <body>:

<component …>
<header>
… [metadata, title, author, etc.]
</header>
<body>
… [the narrative content, references, appendices, etc.]
</body>
</component>

The <header> contains metadata and other information about a product that may be shared with
abstracting and indexing services (in a journal print rendition, header information often appears above a
horizontal line). <header> contains information such as <title>, <creator>s, and <affiliation>s.
The <body> contains the original narrative content, along with acknowledgments, references, and all other
non-<header> items.

The <header> is required, but the <body> is optional (e.g., some journals and oBooks only capture
headers in the XML).

2.2 The Header: Publication and Content Metadata

This model separates “publication” metadata from “content” metadata. This structure was influenced by the
prospect of content re-use and by the many levels of hierarchy (e.g., series, publication, volume, part,
subpart, section, article) found in some publications. By having a generic “publication” metadata model
available for all levels of structure in which an article/chapter may appear, there is no need to define
separate “product metadata”, “part metadata”, “subpart metadata”, and “unit-level metadata” structures.
There are some gray areas in this separation, and, in those cases, a pragmatic choice has been made. In
general:

• <publicationMeta> contains header items that are artifacts of the existing publication's content
incarnation. A <publicationMeta> element is included in a document only for each level that is
appropriate. For a journal, this would be product (journal), part (issue), and unit (article); see the
outline below. For a book, the levels might be product (book) and unit (chapter).
<publicationMeta> may contain the identifier that an article may receive as part of the
publication process, book editors for an edited book, and all details of the publication (journal, book,
eMRW, etc.) in which the content appears.
• <contentMeta> contains only header items that would not change if the content were re-used (in
full). This element may contain content such as authors, keywords, and an abstract, since these
are inherently related to the content.

8
An outline for a journal <header> is as follows:

<header>
<publicationMeta level="product">
… [journal title, publisher info, etc.]
</publicationMeta>

<publicationMeta level="part" position="150">

… [issue number, cover date, etc.]
</publicationMeta>

<publicationMeta level="unit" position="70"

type="article">
… [article id, page numbers, copyright, etc.]
</publicationMeta>

<contentMeta>
… [article title, authors, abstract, etc.]
</content>
</header>

Some of the elements available within <publicationMeta> should only be used at certain levels, e.g.,
<coverDate> will only be used at the “part” (issue) level. Some of this usage is enforced by the model in
the Schematron layer, but in general users are expected to apply the elements as is appropriate to the
content.

For a traditional publication, the “product” level of the <publicationMeta> will refer to the journal, book,
MRW, Current Protocol title, Cochrane database, etc. For example, for an article in an MRW that has parts
and subparts, <publicationMeta> elements with the levels product, part, subpart, and unit need to be
included.

2.3 The Body

A simple <body> will consist of <section>s and optional items, such as <appendix>,
<bibliography>, and <exerciseSection> (reminder: elements are for items that appear as content,
while attributes are for “metadata” about an element’s content). Like DTD4, but unlike JWSART and
WileyML 2.1, <section> nests recursively rather than having the iterative elements <sect1>, <sect2>,
<sect3>, etc. For example:

<body sectionsNumbered="yes">
<section><title type="main">…</title>
<section>…</section>
<section>…</section>
</section>
<section><title type="main">…</title>
<section>…</section>
<section>…</section>
</section>
<section numbered="no"
type="acknowledgments">…</section>
<bibliography …>
…
</bibliography>
</body>

The model for <body> does not prescribe the order of the elements within it (i.e., sections, bibliographies,
appendices, exercise sections, etc. are allowed to appear in any order). Elements must be placed in the
order they are expected to appear in the rendered version since there is no expectation for rendering
applications to reorder the content.

9
2.4 Sections
Sections (also appendices and protocols) are numbered or not according to the value of the
sectionsNumbered attribute on <body>. This can be overridden on a particular section (or appendix,
protocol) by using its “numbered” attribute, which is then inherited by its subsections unless they in turn
have this attribute specified.

Within sections, “floating” objects such as figures, tables, and features are modeled parallel to paragraphs,
not within them. For featured content occurring at the end of a chapter that is presented similarly to a first-
level section, use <feature sectional="yes"> parallel to a first-level <section>.

For the most common case of a <section> with a single <title>, give the title directly, for example:

<section><title type="main">…</title>
<p>…</p>
<p>…</p>
<figure>…</figure>
<p>…</p>
<tabular>…</tabular>
<p>…</p>
</section>

When additional <title>(s) are needed, such as when a title contains a cross-reference or other text
unsuitable for listing in a table of contents, use <titleGroup> to contain the various forms. See the Titles
section for more detail.

3 Titles
3.1 General
A generic <title type="…"> is used for all titles in the <header> and <body>. In the header, <title>s
will always occur within a <titleGroup>, even if there is only one <title>. There will normally be more
than one <title> element in the header and it makes it convenient for processing to wrap them in
<titleGroup>. However, in the body, the most common use of <title> is for section titles; here there
will usually be only one <title> element, so the <titleGroup> wrapper is not required.

A note about trailing punctuation in <title>s: The content of a <title> (both in the
<header> and in the <body>) should only include punctuation that is part of the title itself.
For example, a question mark, exclamation point, period (full stop) at the end of an
abbreviation, or ellipsis that is part of the title should be included; a period that separates
the title from text that follows should not.

3.2 Table of Contents

WileyML 3G does not explicitly model levels of publication higher than the unit level (article/chapter).
Constructs such as the table of contents for a journal issue or book are expected to be generated from
information available in each article or chapter. For subheadings within a journal table of contents, use the
<title> element with type attribute values tocHeading1, tocHeading2, and tocHeading3, for
the different levels of subheadings (see the section on Journal-Specific Topics for more information). If the
form of a title in a table of contents differs from that in the main text, then use <title type="tocForm">
to provide the alternative form. See the Element Reference page for <title> at
https://vendors.wiley.com/schemas/wileyml3g/doc/html/wng_title.html.

10
4 Numbering
4.1 Regular Numbering
WileyML 3G expects numbers to be automatically generated for objects that are typically numbered. This
applies to figures, tables, equations (<displayedItem>), numbered list items, numbered bibliographic
entries, protocol steps*, notes, chemical structures, features, mathematical statements (theorems,
definitions, etc.), exercises, and exercise sections. Their numbers typically should not be part of the
WileyML source content.

For <section> <appendix> and <protocol> automatic numbering is assumed if the value of
@sectionsNumbered on <body> is "yes". If the value of @sectionsNumbered is "no", these elements will
not have numbering applied by the rendering engine.

Most elements that are automatically numbered have the attribute numbered. Set this to "no" for
unnumbered objects (e.g., an unnumbered displayed equation). This attribute can also be used to change
the numbered status of a <section>, <appendix> or <protocol> if it differs from its inherited value.

Two further attributes may be used to control numbering situations that occur specifically for equations and
chemical structures:
1. If these objects are repeated with the same number as when they first appeared (for the reader’s
convenience), use the repeatOfRef attribute.
2. To give equation numbers such as (7)’, with ’ outside the parentheses, use extraLabel (for this
example, extraLabel="&#x2032;").

4.2 Irregular Numbering: <label> and resumeNumberingAt

For irregular numbering, use <label> to supply the irregular numbers (anything except the next
consecutive number or letter, depending on style). The content of <label> should be just the number, letter
or symbol itself, and should not include any additional text or punctuation, or any chapter number (if that is
the style of the product). When regular numbering resumes, include the attribute resumeNumberingAt to
specify the restart of generated numbering.

For example, for Figures 1, 2, 3A, 3B, 4, and 5, the markup would be:

<figure …>…</figure> (no <label>, this is Figure 1)

<figure …>…</figure> (no <label>, this is Figure 2)
<figure …><label>3A</label>…</figure> (this is Figure 3A)
<figure …><label>3B</label>…</figure> (this is Figure 3B)
<figure … resumeNumberingAt="4">…</figure> (no <label>, this is Figure 4)
<figure …>…</figure> (no <label>, this is Figure 5)

For a group of related consecutive equations numbered as “3a,” “3b,” and “3c,” <label>s are needed, and
the following equation “4” would use resumeNumberingAt="4".

11
resumeNumberingAt and <label> would be used for bibliographic entries, e.g., in an erratum where
only a few of the references in the original article are cited and numbers are not consecutive, and/or
additional references are added. For example, if there are only references 3, 4, and 17b, the WileyML
markup would be:

<bib resumeNumberingAt="3"><citation>…</citation></bib> (ref 3)

<bib><citation>…</citation></bib> (ref 4)
<bib><label>17b</label><citation>…</citation></bib> (ref 17b)

To facilitate content re-use, and minimize QA, use of <label> should be kept to a minimum so that numbers
are generated automatically wherever possible.

Always use an arabic number as the value for resumeNumberingAt, e.g., for items with Roman numerals,
resumeNumberingAt="3" will generate III (the stylesheet will convert to Roman numerals).

5 Fixed and Floating Objects

5.1 General
Objects are separated into two broad classes:
1. Fixed (or in-flow): These objects must remain in the position in which they occur relative to the
surrounding “base” text because the surrounding text would no longer make sense if the fixed
content were removed. Some fixed objects have their own specialized elements, such as
<displayedItem> for displayed equations and <mathStatement> for theorems, definitions,
etc., because they have their own particular structure. Other objects are similar enough to be
handled by a generic <blockFixed> element.
2. Floating (or out-of-flow): These objects can be moved to a different position without disrupting the
flow of the content.

The criterion for whether something is floating or fixed is simply whether it can or cannot be moved, relative
to the surrounding text, without compromising what the content is conveying.

Examples of fixed objects include the following:

• Computer code (raw, not part of a numbered series listing); see the example below.
• A fragment of poetry.
• A graphic that must appear in a particular location (and is not captioned as a “Figure” or similar).
• Inline tables/tabular text.
• Text blocks, i.e., pieces of text (or a graphic) set off from the surrounding text in some way, but not
“captioned” in any way, e.g., quotations (see the example below) or dialogue.
• Pedagogical, or other, featured content that must appear in a set position.

In this example, the displayed computer code:

would be marked up with <computerCode> (the inline code is marked up with <span>).

12
This block quotation:

would be marked up with <blockFixed type="quotation">.

Examples of floating objects include the following:

• Figures and other types of captioned objects, the focus of which is a graphic or image.
• Tables.
• Case studies, or other boxed types of content (usually numbered pedagogical features or other
chunks of featured text that can float).
• Pull-quotes.

For example, this pull-quote:

would be marked up with <block type="pullQuote">.

The elements to use in various cases are indicated in the following table:

Floating Fixed
Tables, text with tabular layout <tabular> <tabularFixed>
Figures and figure-like objects <figure>, <chemicalStructure> N/A
Blocks of computer code, poetry, <feature> (for program listings) <computerCode>,
quotations, sidebars, pull-quotes, <block type="…"> <blockFixed type="…">
stand-firsts, boxes, raw graphics box box
floatQuote dialogue
graphic graphic
pullQuote poetry
sidebar quotation
signatureBlock
standFirst
Features (none of the above) <feature> <featureFixed>

5.2 <objectNameGroup>
Use <objectNameGroup> in the <header> to declare all the names for <figure>s, <feature>s,
<featureFixed>s, <mathStatement>s, <appendix>es, <exerciseSection>s, <exercise>s,

13
<list>s and <tabular>s. To do this, supply an <objectName> for each series of <feature>s,
<mathStatement>s, etc., with the corresponding elementName attribute value; it is only necessary to
supply one <objectName> per series, even if there are multiple occurrences of that name in the content.
The name of a feature typically appears at the top or side of it. In the example below, "Special Topic", it
may also carry its own title, e.g., “Molecular Orbitals”. For <exercise>s and <exerciseSection>s the
use of <title type="exercise[Section]Name"> is limited to cases where a specific resource is
linked to the exercise(Section), so declarations for these elements in objectNameGroup will be relatively
rare.

In the body, each feature, theorem, etc., must begin with a <title type="featureName"> or
"mathStatementName", etc. The name of the feature must be given exactly as it is declared in the
<objectNameGroup>; any variation in casing, spacing, or anything else will result in a document that does
not parse. This is to ensure consistency of the <feature> name throughout the document and so enable
decisions on presentation to be made based on the name.

Exception: The name "Figure" (or "Fig.") does not need to be declared; that is, for "Figure"
(or "Fig.") <title type="figureName"> is not needed.

For this example:

the <objectNameGroup> would appear as:

<objectNameGroup>
<objectName elementName="feature">Special Topic</objectName>
…
</objectNameGroup>

And in the body, the <feature> itself would appear as:

<feature …>
<titleGroup>
<title type="featureName">Special Topic</title>
<title type="main">Molecular Orbitals</title>
</titleGroup>
…
</feature>

Note: Features (floating and fixed) are not always just one type of feature. They can be of two or more
types simultaneously; in such a case provide each type of <title type="featureName"> that applies.
The featureName that is given first in the <titleGroup> determines the numbering because numbering

14
is expected to be in a separate sequence for each different first-given <title type="featureName">
(this applies to mathStatementName etc. as well).

For this example:

The <feature> within the <body>, and the <objectNameGroup> in the <header>, would appear as
shown below. In this example, the <span type="highlight"> provides a hint to rendering to apply
the shaded box and the italics around "Do It!" in the first <title type="featureName">.

<feature …>
<titleGroup>
<title type="featureName">Comprehensive <span type="highlight">Do It!</span></title>
<title type="featureName">WileyPLUS</title>
</titleGroup>
…
</feature>

<objectNameGroup>
<objectName elementName="feature">Comprehensive <span type="highlight">Do
It!</span></objectName>
<objectName elementName="feature" iconRef="…" displayTitle="no"
onlyChannels="print">WileyPLUS</objectName>
…
</objectNameGroup>

6 Figures and Figure-Like Objects

6.1 General
The element <figure> is used for one of a numbered series of floating objects comprised of an image
and textual content (<caption>) that describes the image. They are numbered so that they can be referred
to from within the text. Examples are Figures, Schemes, Illustrations, and Plates.

15
For example:

Figure 1. Neuromuscular Junctions. The electric organs of Torpedo consist of stacks of

modified neuromuscular junctions located on each side of the body. (FROM Z. W. HALL, AN
INTRODUCTION TO NEUROBIOLOGY, SINAUER ASSOCIATES, INC., SUNDERLAND, MA © 1992.)

would be marked up as:

<figure xml:id="c03-fig-0001">
<title type="main">Neuromuscular Junctions</title>
<mediaResource href="urn:…" alt="…"/>
<caption>The electric organs of <i>Torpedo</i> consist of stacks of modified
neuromuscular junctions located on each side of the body.
<source>(From Z.W. Hall, An Introduction to Neurobiology, Sinauer Associates,
Inc., Sunderland, MA &copy; 1992.)</source></caption>
</figure>

In this example:
• The name (“Figure”) and label (“1”) are not included in the <caption> content.
• Figures named “Figure” do not use <title type="figureName">; all other kinds of figure-like
objects must use it (see next section).
• Regular numbering does not require <label>; numbering is generated.
• The bold formatting of the title is not marked up; it will be generated as a result of the <title>
markup.
• The cap/small-cap formatting of the source is not marked up; the style for sources in the product is
expected to be generated when the content is rendered.
• There is a single <mediaResource> specifying a URN. This could be resolved to multiple image
formats (e.g., thumbnail, normal, magnified) depending on context. However, for certain classes of
content, <mediaResourceGroup> may be required to provide all of the formats explicitly. See the
Element Reference Manual page for <mediaResource> at
https://vendors.wiley.com/schemas/wileyml3g/doc/html/wng_mediaResource.html.

6.2 Nonstandard Names (Illustrations, Plates, Schemes, etc.)

As noted in the section covering <objectNameGroup>, if a name other than “Figure” is used for a figure-
like object, then:
• Declare the name in the <objectNameGroup> in the <header>.
• Include the name as a <title type="figureName"> within the <figure>.

For example, for “Scheme 1,” the <header> would contain

<objectNameGroup>
<objectName elementName="figure">Scheme</objectName>
…
</objectNameGroup>

and the <body> would contain:

<figure xml:id="c01-fig-0013">
<title
type="figureName">Scheme</title>
…
</figure>

It is a validation error if a <title> of type "figureName" occurs in a <figure>, but does not occur in
the <objectNameGroup>. This is to guard against accidental typographical variations in the names.

16
6.3 Figures with Parts

6.3.1 Captions
The caption may refer to the parts whether or not the images for parts of a multipart figure are physically
combined into a single image file. For example, this multipart figure and caption:

Figure 6.42. Comparison of a prokaryotic cell and eukaryotic cell. Note that the prokaryotic cell (A) lacks
a true nucleus, whereas the eukaryotic cell contains a true nucleus and various organelles. Also, prokaryotic
cells are smaller, ranging in size from 0.5 to 1.0 millimeters as compared with 10 to 100 millimeters for
eukaryotic cells. (B) A false-color electron micrograph of the living prokaryote Bacillus subtilus that is about
to complete cell division. Magnification × 335,000. (B, Photo Researchers, Inc.)

would be marked up as:

<figure xml:id="c06-fig-0001">
<title type="main">Comparison of a Prokaryotic Cell and Eukaryotic Cell</title>
<mediaResource href="urn:…" alt="…"/>
<caption>Note that the prokaryotic cell (<i>A</i>) lacks a true nucleus… for
eukaryotic cells. (<i>B</i>) A false&hyphen;color electron… Magnification
&times; 335,000. <source>(B, Photo Researchers, Inc.)</source></caption>
</figure>

17
In the following example each part of the figure has its own title. There is no special modeling for this; it is
dealt with via formatting, not <title>.

Figure 6.17. (A) Jupiter, photographed by Voyager 1 spacecraft from a distance of 33,000,000
kilometers. (B) A close-up of Jupiter's Great Red Spot. Note the turbulence to the west (left) of the Great
Red Spot. (Courtesy of NASA.)

It would be marked up as:

<figure xml:id="c11-fig-0017">
<mediaResource href="urn:…" alt="…"/>
<caption><b>(<i>A</i>) Jupiter, photographed… kilometers.(<i>B</i>) A
close&hyphen;up of… Red Spot.</b> Note the turbulence … Red Spot.
<source>(Courtesy of NASA.)</source>
</caption>
</figure>

6.3.2 Multipart Figures with Parts in a Single File

Wherever possible, parts for a multipart figure should be combined into a single graphic file (as in the
examples above). See the next section for handling cases where this is not possible.

6.3.3 Multipart Figures with Parts in Multiple Files

Occasionally, for a variety of reasons, such as rights, size, history, or structure, the graphics comprising a
single figure are split across more than one file. There are two cases:
1. A single caption: For this case, use multiple <mediaResourceGroup>s and a single <caption>.
If different <source>s are indicated for each of the parts, these can be marked up in the
<caption>; <source> may occur more than once. The order in which <source>s are listed
should correspond to the order of the parts.
2. A caption for each graphic/part: Use <figurePart>.

18
The following is an example of a multipart figure with multiple captions:

In this case, <figurePart> is used to group each part’s <mediaResource> with its <caption>:

<figure xml:id="c08-fig-0007">
<title type="main">Clarifying Butter</title>
<figurePart>
<mediaResource href="urn:…" alt="…"/>
<caption>(a) Skim the foam from the top of the melted butter.</caption>
</figurePart>
<figurePart>
<mediaResource href="urn:…" alt="…"/>
<caption>(b) Ladle off the clear, melted fat.</caption>
</figurePart>
<figurePart>
<mediaResource href="urn:…" alt="…"/>
<caption>(c) Continue until only the milky liquid remains…pan.</caption>
</figurePart>
</figure>

19
6.4 Figures with Notes
In some products, footnote indicators are present in figures (as shown in the example below). Use <note
labelOnNoteOnly="yes"> in the <caption> of the graphic so that no label is generated as a link,
and the note number or label only appears at the beginning of the text of the note.

Page footnote: **Con Brío With gusto, determination and courage

Los romanos conquistan la Península Ibérica (218-204a. C.)
<blockFixed type="graphic" xml:id="…">
<mediaResource href="urn:…" alt="…"/>
<caption>Los romanos conquistan … (218&ndash;204a. C.)<note xml:id="…"
labelOnNoteOnly="yes"><label>**</label><b>Con Br&iacute;o</b> With gusto,
determination and courage</note></caption>
</blockFixed>

7 Sources and Credits

Sources (for tables, figures, and text) can be presented in a number of ways. If they are distinctly formatted,
or separated from the caption text, then <source> must be used. When this is not the case, the decision
to apply source markup depends on the workflow for a product. For example, if a source (or credit) is clearly
identified at the time of WileyML production, either in a separate permissions spreadsheet or in the
manuscript, source markup may be requested; otherwise source markup may not be applied.

20
8 Theorems, Definitions, etc.
Theorems, definitions, proofs, etc. are marked up using <mathStatement>. Each series of
<mathStatement> (designated by their <title type="mathStatementName"> and declared in the
<objectNameGroup> in the header) will be automatically numbered by default, beginning at 1 (use
numbered="no" for unnumbered instances). For example:
We aim at calculating probability …
Theorem 2. The area size…
Lemma 7. The relation between …
Definition 4. Let …
Lemma 8. Assuming a random uniform …

would be marked up as:

<p>We aim at calculating probability…

<mathStatement xml:id="c02-mthst-0006">
<title type="mathStatementName">Theorem</title>
<p>The area size ...</p>
</mathStatement>
<mathStatement xml:id="c02-mthst-0007">
<title type="mathStatementName">Lemma</title>
<p>The relation between …</p>
</mathStatement>
<mathStatement xml:id="c02-mthst-0008">
<title type="mathStatementName">Definition</title>
<p>Let …</p>
</mathStatement>
<mathStatement xml:id="c02-mthst-0009">
<title type="mathStatementName">Lemma</title>
<p>Assuming a random uniform …</p>
</mathStatement>
…
</p>

and the <objectNameGroup> for this article/chapter would include (but might also contain name
declarations for <figure>s, <feature>s, etc.):

<objectNameGroup>
<objectName elementName="mathStatement">Theorem</objectName>
<objectName elementName="mathStatement">Lemma</objectName>
<objectName elementName="mathStatement">Definition</objectName>
</objectNameGroup>

21
In this example, a proof:

Proof.
m(A) = m(B) + m(A – B) ³ m(B). For the second statement…
Let B1 = A1, and for …
For the increasing sequence… … □

would be marked up as:

<mathStatement xml:id="c02-mthst-0001" numbered="no">

<title type="mathStatementName">Proof</title>
<p><math>…</math>. For the second statement </p>
<p>Let <math>…</math>, and for …</p>
<p>For the increasing sequence… &box;</p>
</mathStatement>

9 Enriching Content/Semantic Tags

9.1 <infoAsset>
If required, use <infoAsset> to mark up text representing semantically significant information, such as a
chemical formula, enzyme, or product name:

<p><infoAsset type="genusSpecies"><i>Helicobacter pylori</i></infoAsset> is a

bacterium that …</p>

9.2 <accessionId>
Use <accessionId> for an accession key that allows access to a record in a database, e.g. GenBank
accession numbers, PubMed IDs, Digital Object Identifiers (DOIs), patent numbers, and standards.

When accession numbers are explicit in the text, use <accessionId> to mark them up:

<p>… under Accession No. <accessionId ref="info:ddbj-embl-

genbank/AF114696">AF114696</accessionId>.</p>

If accession numbers are not explicit in the text, they may still be provided using an empty <accessionId>
within <infoAsset>:

<p><infoAsset type="enzyme"><accessionId
ref="info:x-wiley/ec/1.11.1.11"/>Ascorbate peroxidase</infoAsset> is an enzyme
that …</p>

Note: For DOIs, ISBNs, and ISSNs within the body, including within all <citation>s, use
<accessionId>. For DOIs, ISBNs, and ISSNs within <publicationMeta>, use <doi>,
<isbn>, and <issn>, respectively.

9.3 Functional Chemistry

9.3.1 <enrichedObjectGroup>
Use <enrichedObjectGroup type="chemicalCompound"> in <contentMeta> to provide a list of
all relevant compounds in an article. Each <enrichedObject> in the <enrichedObjectGroup>
captures all the information about a compound in one place, which can be referenced from anywhere in
the article, and will be the target of any <link> to the compound. Capture the xml:id of any elements
that relate to the compound (e.g. a figure that contains the structure of the compound, or a chemical

22
 formula containing it) using the attribute associatedDataRef on <enrichedObject>; multiple values
are marked up as a space-separated list of IDs as shown in the example below.

<enrichedObject xml:id="…" associatedDataRef="#jhet528-reg-0004 #jhet528-info-

0041">
<accessionId ref="info:x-wiley/casrn/633-96-5"/>
</enrichedObject>

9.3.2 Figures with Regions

In chemistry content, when several structures appear in a single image, a part of the image that contains
the structure for a compound can be specified in the <enrichedObject> that represents the compound
using the associatedDataRef attribute to reference a <region> declaration in the
<mediaResource> for the image. In this case, the region is taken to be rectangular and is described by
its upper left and lower right coordinates in relative measurement to the whole image, as shown in the
example below.

How a <region>’s boundary is arrived

at:

Top Left corner is:

6mm in from left border of whole
image
29mm down from top border of whole
image
Giving:
6/120 = .05 as @upperLeftX
29/79 = .37 as @upperLeftY
79mm
Bottom Right corner is:
32mm in from left border
56mm down from top border
Giving:
32/120 = .27 as @lowerRightX
56/79 = .71 as @lowerRightY

OR, finally:
<region xml:id=" jhet528-reg-0004"
upperLeftX=".05"
upperLeftY=".37"
lowerRightX=".27"
lowerRightY=".71">

120mm
<mediaResource alt="image" href="urn:x-wiley:0022152X:media:jhet528:sch001"
eRights="yes" copyright="Hetero Corporation">
<region xml:id="jhet528-reg-0004" upperLeftX=".05" upperLeftY=".37"
lowerRightX=".27" lowerRightY=".71"><caption>7a&hyphen;g</b></caption></region>
</mediaResource>

<region> is marked up as part of the <mediaResource> for the graphic containing the structure
of a compound; if the <mediaResource> is part of a <mediaResourceGroup>, it must be given
in the first <mediaResource>.

23
10 Journal-Specific Topics
See also the Journal Article example at
https://vendors.wiley.com/dtds/wileyml3g/examples/journal-article.pdf.

10.1 Issue Titles

An issue can have three main types of title, viz., a straightforward issue title, a special issue title, and a
supplement title.

1. Issue Titles: In some journals it is simply the practice to give titles to some or all issues. This does
not mean that the issue is a "special" issue or a "supplement;" the issue simply has a title. When
an issue title is required, use:

<publicationMeta level="part">
…
<title type="main">

2. Special Issue Titles: A special issue is a regular/budgeted issue devoted to a specific topic. It
needs to be denoted as a "Special Issue" and have a title that reflects the topic. (There is an
expectation that the phrase "Special Issue" will be rendered on Wiley's publication platform in front
of the special issue title.) When a special issue title is required, use:

<publicationMeta level="part">
…
<title type="specialIssueTitle">

If necessary, a subtitle can also be added using <title type="specialIssueSubtitle">.

3. Supplement Titles: Such issues are extra to budgeted issues, i.e., not numbered within the normal
sequence, but delivered/associated with an issue. The issue number should be recorded. (There
is an expectation that the phrase "Supplement" will be rendered on Wiley's publication platform in
front of the supplement title.) The supplement title is supplied using:

<publicationMeta level="part">
…
<title type="supplementTitle">

If present, a subtitle can also be added using <title type="supplementSubtitle">.

If the supplement is part of a series, where the issues have a common title, then that series title should
also be added using <title type="supplementSeriesTitle">.

10.2 Supporting Information (Supplementary Material)

Details of additional material provided for an article, such as large data tables, videos, etc., are given with
<supportingInformation> (in <contentMeta>). See the Element Reference page for
<supportingInformation> at
https://vendors.wiley.com/schemas/wileyml3g/doc/html/wng_supportingInformation.html.

10.3 Journal TOCs

The section of an issue where a journal article appears is often indicated at the beginning of the article
itself, such as with “Research Article” appearing above the article title. This is the singular form of the
<title type="tocHeading1"> and is modeled with <title type="articleCategory">. For a
given journal, this <title> only needs to be provided explicitly in the WileyML <header> if it cannot be
reliably generated from the "type" value given on <publicationMeta level="unit">. (Basically,
ex-Wiley journals need it, but ex-Blackwell journals do not.) See section 3 on Titles for more information.

24
10.4 Focus Sections
A few journals (Cancer, American Journal of Medical Genetics (AJMG)) have “Focus Sections.” These are
recurring journal issues devoted to a specific aspect, e.g. Cancer Cytopathology. Such an issue should be
handled as a regular journal issue with two additional pieces of issue- ("part")-level
<publicationMeta>:

1. A <title type="focusSection">: The presence of a title of this type indicates that this issue
belongs to a Focus Section, and the content of this element is its title.
2. An <id type="focusSection">: This provides the “section number” for this particular Focus
Section. This is used in online processing of the issue; internal systems append it to the ISSN,
creating essentially a separate journal for each Focus Section.

10.5 Associated Websites

If there is an associated website for the journal, provide a <link type="associatedUrl"> (in
<linkGroup>) within <publicationMeta level="product">. Provide the associated URL itself as
the value of href:

<linkGroup>
<link type="associatedUrl" href="http://www.wiley.com/go/neuropsych"/>
</linkGroup>

10.6 Alternate Versions

When a journal must provide alternate versions of the content—e.g., a typeset version of an article
(typically a PDF), a plain text version of an article, or the first page of an article in place of an abstract (for
use in Google)—provide a <link> (in <linkGroup>) within <publicationMeta level="unit">.
The <link> must have a type value appropriate to the alternate version, e.g.,
type="toTypesetVersion", "toPlainTextVersion", or "toTypesetVersionPage1". The
value of href should be a URN specifying the resource or an explicit file location, as in the following
example:

<linkGroup>
<link type="toTypesetVersion" href="file:4_ftp.pdf"/>
</linkGroup>

10.7 Book Reviews

Whenever possible, each review of a book (or software, website, etc.) should be provided as a separate,
standalone file (<component>). Provide the bibliographic details of the reviewed item, e.g. the book title,
author(s), publishing info, etc. in a <citation> within the <title type="main"> within
<contentMeta> for the article (provide the citation information in the order it is to appear). Use <title
type="tocForm"> as necessary to provide the version of the title for the Table of Contents of the issue.

When a list of book reviews is preceded by, interspersed with, or followed by editorial text that can't be
published other than with that set of reviews as a whole, the reviews should be provided as a single article
(<component>). The <publicationMeta level="unit"> for the article must have
type="bookReview" and the <title type="main"> for the <contentMeta> should contain the
overall "title" of the list of book reviews (which may just be "Book Reviews"). If necessary, the <title
type="tocForm"> may be used to control what would appear in the issue TOC (e.g., a list of all of the
book titles under review). The details of the reviewed items should still be provided as <citation>s within
the appropriate elements within the content, typically the <title type="main"> of a <section> or,
occasionally, within regular paragraph text. If the same author(s) was responsible for the reviewed books,
provide the details for the author(s) in the <creatorGroup> within the <header> for the article. If each

25
review has a different set of authors, provide them all in the <header> and use the responsibleForRef
attribute on <creator> to connect the authors to their review(s).

10.8 Books Received

If a journal article consists solely of a "Books Received" list, the whole list of references should be marked
up as a single untitled <bibliography> directly in <body>, with the article title "Books Received". See
the Element Reference page for <bibliography> at
https://vendors.wiley.com/dtds/wileyml3g/doc/html/wng_bibliography.html.

10.9 Editorial, Letter to the Editor, Reply, and Erratum

A journal article can also contain several other types of content:

• Editorial: An editorial is a general article usually written by the journal editor to all of the readers.
This type of article should be identified in the <publicationMeta> as:

<publicationMeta level "unit" position="10" type="editorial" status="forIssue">

The title of the article also needs to be declared in the <titleGroup> as:

<titleGroup>
<title type="articleCategory">Editorial</title>
</titleGroup>

• Letter to the Editor and Reply: Readers will sometimes write a letter to the journal editor about a
specific article in a journal issue. These letters usually offer suggested changes or omissions in an
article. The journal editor will consult with the author(s) of the original article, and that will trigger a
reply. These types of articles should be identified in the <publicationMeta> as:

<publicationMeta level="unit" position="350" type="letter status="forIssue">

The title of the article needs to be declared in the <titleGroup> as:

<titleGroup>
<title type="articleCategory">Correspondence</title>
</titleGroup>
• Erratum: An erratum is an article written by the original journal author(s) that corrects and/or
updates information in the article. This type of article should be identified in the
<publicationMeta> as:

<publicationMeta level="unit" position="40" type="erratum" status="forIssue">

The title of the article needs to be declared in the <titleGroup> as:

<titleGroup>
<title type="articleCategory">Corrigendum</title>
</titleGroup>

For more information on these types of articles, see the sample files available at:
https://vendors.wiley.com/schemas/wileyml3g/

26
11 MRW-Specific Topics
See also the MRW Article example at
https://vendors.wiley.com/schemas/wileyml3g/examples/mrw-article.pdf.

11.1 Type of Component

Typically, <component type="mrwArticle"> will be correct. Wiley will supply details if another value
is to be used.

11.2 Type of Unit

Use the "type" attribute on <publicationMeta level="unit"> to capture the type of unit
(unitType was used in WileyML 2.1). A mapping of unitTypes can be found at
https://vendors.wiley.com/schemas/wileyml3g/WileyML_3G_ContentTypes.xls.

11.3 Difficulty Level

To capture the difficulty level, use the href attribute on <subject> within <publicationMeta
level="unit"> (the difficulty attribute on <unitType> was used in WileyML 2.1). The value for
difficulty must be "introductory", "intermediate", or "advanced".

<subjectGroup>
<subject href="http://psi.wiley.com/difficulty/introductory"/>
<subject href="http://psi.wiley.com/subject/978123456789X/PY10">Polymer
Processing<subject>
<subjectGroup>

11.4 Unit-Specific Subjects

For online MRWs, unit-specific subjects may be required. Capture these in <publicationMeta
level="unit">. The values will be supplied by Wiley and will include the product ISBN.

<subjectGroup>
<subject href="http://psi.wiley.com/difficulty/introductory"/>
<subject href="http://psi.wiley.com/subject/978123456789X/PY10">Polymer
Processing<subject>
<subjectGroup>

27
11.5 Blind Entries
To mark up blind entries in MRWs, use <title type="blindEntry"> in <publicationMeta
level="unit"> in the referenced article. The type="blindEntry" requires a “sort” attribute; this is
checked by a validation rule.

<publicationMeta level="unit">
...
<titleGroup>
<title type="blindEntry" sort="ALDEHYDE RESINS">Aldehyde Resins</title>
<title type="blindEntry" sort="POLYACETALS">Polyacetals</title>
</titleGroup>
...
</publicationMeta>
<contentMeta>
...
<titleGroup>
<title type="main" xml:lang="en" sort="ACETALDEHYDE">Acetaldehyde</title>
</titleGroup>
...
</contentMeta>

This markup would be expected to produce two “blind entries” in the alphabetic list of articles that may be
rendered something like this:

Aldehyde Resins see Acetaldehyde

Polyacetals see Acetaldehyde

11.6 Related Articles

Mark up related articles with either <link style="fallback">,for incrementally-published MRWs, or
<link style="seeAlso"> in <section type="relatedArticles">. If there is a title for the section
(i.e., "Related Articles"), a <title> must be supplied. Any necessary formatting and punctuation must also
be provided; no line breaks or punctuation will be generated. The rendering for the product will determine
whether or not the <section type="relatedArticles"> will be displayed.

11.7 “qv” Cross References

Mark up “qv” cross references with <link style="qv">. All "qv" links must have content. The rendering
application will never overwrite content for <link style="qv">, and the content of the <link> should
be provided as supplied in the manuscript. If “(qv)” follows the reference, it will not be generated and should
be included in the text after the <link>.

11.8 “fallback” Cross References and <link>s to External Content

If a link is supposed to point to another article (or specific part of another article) within the same product,
either use <link style="fallback">, for incrementally-published MRWs, or <link
style="seeAlso"> with the href attribute giving the URL or URN of the targeted element. For MRWs,
unlike other content, all links to external targets must also have content. All "fallback" links must have
content. If the <link> has style=”fallback”, the rendering for the product is expected to search the product
for the target object and, if found, to substitute either the number or <title type="main"> of the object
instead of the content of the <link>. If the target is not found, then the content of the <link> will be
displayed. This is to allow for MRWs that publish over time, so some articles may not be available, while
others may have their titles updated. Consider for example

28
 <p>… is modeled (see <link style="fallback"
href="urn:x-wiley:9780470548455:xml-
component:w9780470548455c04:c04-sec2-
0014">Climatology</link>). This …</p>

If the specified chapter does not yet have XML (or if there is no xml:id="c04-sec2-0014" in it), then
“Climatology” will be used; if it does exist, then the title for that section in the document may have been
updated to “Climatology Research”, and that would be used. If the <link> does not have
style="fallback" then the usual behavior of using the <link>'s content, if any, is followed.

11.9 Updating Articles

For updated versions of articles that already have been published online (for which <unitHistoryInfo>
was used in WileyML 2.1) use <id type="precedingVersionDoi"> and <id
type="precedingVersionFileID"> in <publicationMeta level="unit"> to list the unit-level
DOI (<doi>) and file ID (<id type="file">) of the previous version of content. If the new version is the
result of a merge of articles, include the precedingVersionDoi and precedingVersionFileID for
each article.

11.10 Updated by Staff

For articles that are updated by in-house staff, capture this with <event type="updatedByStaff">
with the date that the XML is updated at the vendor.

11.11 Short Entries

There is no specific model for short entries; model these with component, using the appropriate "type"
value for <publicationMeta level="unit"> (e.g., shortArticle, definitionEntry).

11.12 Volume Numbers

Capture volume numbers in <numbering type="bookVolume">. Use <title type="name"> to
capture the word associated with the number (e.g., “Volume”). A <title type="main"> may optionally
be included if the volume has a title that is distinct from the product title. Often MRWs are “multi-volume
books” and therefore the volume information would go in <publicationMeta level="part">. See
Appendix 1 for a summary of <numbering> types.

<publicationMeta level="product">
<titleGroup>
<title sort="ENCYCLOPEDIA OF SCIENCE" type="main">Encyclopedia of
Science</title>
</titleGroup>
</publicationMeta>

<publicationMeta level="part">
<titleGroup>
<title sort="A–C" type="main">A&ndash;C</title>
<title type="name">Volume</title>
</titleGroup>
<numberingGroup>
<numbering type="bookVolume">A&ndash;C</numbering>
</numberingGroup>
</publicationMeta>

29
11.13 Print versus Online
For an MRW or other product where parts are published online over time, the <event
type="publishedPrint"> is captured at the product level. For the online product, the <event
type="publishedOnlineFinalForm"> is recorded at the unit level for each unit. The date of online
publication of the product as a whole is captured at the product level using <event
type="publishedOnlineProduct">; if the product does not publish as a whole on a single date, the
first date that any piece of it appeared online is captured.

12 Book- and Book Series-Specific Topics

See also the Book Chapter examples at
https://vendors.wiley.com/schemas/wileyml3g/EXAMPLES/book-chapter-finance.pdf,
https://vendors.wiley.com/schemas/wileyml3g/EXAMPLES/book-chapter-programming.pdf and
http://vendors.wiley.com/schemas/wileyml3g/examples/textbook-chapter.pdf.
See an example of a book in a series at http://dx.doi.org/10.1002/9780470175422.

12.1 Multi-volume Books

If it is necessary to capture the volume number(s) for multi-volume books, use <numbering
type="bookVolume">. If the product is split into multiple volumes, place <numbering type="bookVolume">
in <publicationMeta level="part"> with the relevant volume number in each chapter. If the product is a
standalone volume, i.e. all the chapters in it belong to the same volume, place <numbering
type="bookVolume"> in <publicationMeta level="product">. See Appendix 1 for a summary of
<numbering> types.

12.2 Series Metadata

<publicationMeta level="series"> should only include series information that is consistent across
all books in the series. Typically, this is the series title, subtitle, and series number.

For oBook Series books, this also would include ISSN, DOI, and subject information. If series information
is needed for oBook Series books, it will be supplied by Wiley.

12.3 Series Number

Capture the Wiley series number in <id type="series"> in <publicationMeta level="series">.

12.4 Series Volume Number

Capture series volume number in <numbering type="main"> in <publicationMeta
level="product">. Use <title type="name"> to capture the word associated with the number (e.g.,
“Volume”). The presence of <publicationMeta level="series"> makes it clear that it is a series
volume number. See Appendix 1 for a summary of <numbering> types.

12.5 Sequence in Series

Capture the sequence in series via the “position” attribute on <publicationMeta level="product">.
This need not be captured for content that is not being used directly for an oBook Series. The values for
oBook series titles will be pulled via the oBook production system.

30
13 Content–Element Mapping
This table provides guidance for the appropriate WileyML 3G element/attribute for cases where this may
not be intuitive.

Concept Element
abbreviation term type="abbreviation"
abbreviations list definitionList
acknowledgments section type="acknowledgments"
block equation displayedItem type="mathematics"
collaboration (as author) groupName
company name infoAsset type="corporateName"
computer code (raw) computerCode
computer code (listing) <feature …><title type="featureName">Listing</title>
corporate author groupName
chart <figure …><title type="figureName">Chart</title>
chemical reaction displayedItem type="chemicalReaction"
definition (mathematical) <mathStatement …>
<title type="mathStatementName">Definition</title>
definition list definitionList, listPaired
displayed equation displayedItem type="mathematics"
DOI (in header) doi
DOI (in body) accessionId ref="info:doi/…"
epigraph section type="epigraph"
equation (displayed) displayedItem type="mathematics"
feedback (on correctness of explanation
an answer)
first page (in a citation) pageFirst
first page (in metadata) numbering type="pageFirst"
focus section (in a journal) title type="focusSection"
id type="focusSection"
genus/species infoAsset type="genusSpecies"
glossary definitionList
issue number (metadata) numbering type="journalIssue"
journal ID id type="product"
key terms definitionList, definitionListGenerated
monospace span cssStyle="font-family:monospace"
overline span cssStyle="text-decoration:overline"
online-only onlyChannels="online"
print-only onlyChannels="print"
problem exercise
program listing feature (with <computerCode> inside)
pull-quote block type="pullQuote"
question exercise
quotation blockFixed type="quotation" (fixed in place)
block type="floatQuote" (can float)
related articles section type="relatedArticles"
running head title type="short"
title type="shortAuthors"
scheme <figure…><title type="figureName">Scheme</title>
sequence in product publicationMeta level="unit" position="…"
theorem <mathStatement…>
<title type="mathStatementName">Theorem</title>
underline span cssStyle="text-decoration:underline"

31
Appendix 1: <numbering> within <publicationMeta>
The table below details the different type values for <numbering> and how they are used in different
levels of <publicationMeta> for different content types.

Content serial book MRW CP CDSR

type
publication
Meta level
series - - - - -
product - "edition" "edition" - -

"main" (Series -
Volume number
when in a Book
Series)

"bookVolume" "bookVolume"
(Volume number (Volume number
when product is a when MRW is a
single volume) single volume)
part "journalVolume" "bookVolume" "bookVolume" "journalVolume" "journalVolume"
(Volume Number (Volume Number (CP supplement) (=year)
"journalIssue" for multi-volume for multi-volume
book: single book MRW product) "main" ( CP "journalIssue"
"includedIssue" spans multiple Chapter number) (=issue number)
volumes)
"supplement"
"main" "main"
"supplementSeri (Part number) (Part number)
esVolume"
subpart - "main" "main" "main" (=Section -
(subpart number) (subpart number) number)
subSubpart - "main" "main" - -
(subSubpart (subSubpart
number) number)
unit - "main" "main" - -
(Chapter number) (Chapter/Article
number)

Appendix 2: Graphical Examples

Journal Article
https://vendors.wiley.com/dtds/wileyml3g/examples/journal-article.pdf.

Reference Work Article

https://vendors.wiley.com/dtds/wileyml3g/examples/mrw-article.pdf.

Book Chapter (Finance)

https://vendors.wiley.com/dtds/wileyml3g/examples/book-chapter-finance.pdf.

Book Chapter (Programming)

https://vendors.wiley.com/dtds/wileyml3g/examples/book-chapter-programming.pdf.

32