<name-alternatives>
Name Alternatives
Container element for more than one version of a personal
name, the element <name> (for
example, the name written in both Japanese Kana characters and the
Latin alphabet).
Remarks
The <name-alternatives> element is intended to collect multiple
versions of a single name without appearing to multiply the number of names. (Three versions of a
author name is not the same as three different contributors.) Like the element <alternatives>, which is a similar construction for objects such as
graphics, an application must determine how multiple versions of a single name are to be processed. The @specific-use, @content-type, and @xml:lang attributes can be used to distinguish the cases for separate processing.
Usage: The <name-alternatives> element can be used to record:
- A name in multiple languages (For example, a name in Korean or Chinese-Han characters and a transliterated version of the same name in the Latin alphabet);
- A name in multiple language/script combinations (For example, a name in Japanese [xml:lang="ja-Jpan" for Han + Hiragana + Katakana] and the same name written in Kanji [xml:lang="ja-Hani"]);
- An alternate name for sorting or searching (For example, a name in French with accented letters [such as an “é”] and a plain-letter lower-ASCII version of the same name with “é” replaced by “e” for sorting. The @specific-use attribute can be used to indicate that the ASCII version is only for sort, not for display.);
- An alternate name for indexing (For example, a publisher may choose to record name variants for an individual, as examples: a nickname, author-pseudonym, maiden name, religious name, or tribal name. The attribute @specific-use could be used to record the rationale for the name variant, such as “primary” , “index”, or “table-of-contents”. Alternatively, or in addition, the attribute @content-type could be used to record the type of name variant, such as “nickname”, “maiden-name”, or “pseudonym”, etc.);
- A version of the name in a different arrangement (For example, since the order of the <surname> and <given-names> is fixed in JATS, a publisher might also wish to record a byline-style version of the name in given-surname order and could use a <string-name> of @content-type="byline" to accompany the name inside a <name-alternatives> element.); or
- Both validated and known-to-be-incorrect names. (For example, in the PubMed DTD, there is an attribute called “ValidYN” [valid yes or no], that can be used to record the fact that one version of a name was received, found to be in error, and then corrected. An application might be set up to display only the corrected version, while both name variants might be retained for searching or quality control. In JATS, this information can be recorded as two <name> elements inside a <name-alternatives> wrapper, with the @content-type attribute used to tell the correct from the incorrect.)
ID Attribute:
The names inside a <name-alternatives> do not generally have a unique identifier because they are all the same name. This Tag Set assumes that any necessary unique identifier will be placed on the enclosing element (such as the <contrib> element or the
<principal-investigator> element) that contains the <name-alternatives> wrapper.
String Name Best Practice:
Both <name> and
<string-name> are allowed inside <name-alternatives>. However, for this Tag Set, the <string-name> within a <name-alternatives> should not be used for the primary name. The primary name should be tagged with a <name> element. Within a
<name-alternatives>, the element
<string-name> can be used to hold, for example, an
undifferentiated transliteration (one not tagged with specific name elements such as <surname>) or a search-specific name.
Content Model
<!ELEMENT name-alternatives
%name-alternatives-model; >Expanded Content Model
((name | string-name)+)
Description
Any one of:
- One or more of any of:
This element may be contained in:
Example 1
A name given in two forms:
...
<name-alternatives>
<name name-style="western"><surname>Chu</surname>
<given-names>J. H.</given-names></name>
<string-name name-style="eastern" xml:lang="zh">褚君浩</string-name>
</name-alternatives>
...Example 2
In article metadata, to provide alternative names:
... <article-meta> ... <contrib-group> <contrib contrib-type="author"> <name-alternatives> <name name-style="western"><surname>Zhang</surname> <given-names>Y. P.</given-names></name> <string-name name-style="eastern" xml:lang="zh">张轶泼</string-name> </name-alternatives> <xref ref-type="aff" rid="a1">1</xref> <xref ref-type="author-notes" rid="n1">a)</xref> </contrib> <contrib contrib-type="author"> <name-alternatives> <name name-style="western"><surname>Isobe</surname> <given-names>M.</given-names></name> <string-name name-style="eastern" xml:lang="zh">磯部光孝</string-name> </name-alternatives> <xref ref-type="aff" rid="a2">2</xref> </contrib> <contrib contrib-type="author"> <name-alternatives> <name name-style="western"><surname>Liu</surname> <given-names>Yi</given-names></name> <string-name name-style="eastern" xml:lang="zh">刘仪</string-name> </name-alternatives> <xref ref-type="aff" rid="a1">1</xref> </contrib> </contrib-group> <aff id="a1">...</aff> <aff id="a2">...</aff> <author-notes id="n1">...</author-notes> ... </article-meta> ...
Example 3
The name of a contributor given in two languages (one given in two scripts):
...
<article-meta>
<title-group>...</title-group>
<contrib-group>
<contrib contrib-type="author">
<name-alternatives>
<name name-style="eastern" xml:lang="ja-Jpan">
<surname>中西</surname>
<given-names>秀彦</given-names>
</name>
<name name-style="western" xml:lang="en">
<surname>Nakanishi</surname>
<given-names>Hidehiko</given-names>
</name>
<name name-style="eastern" xml:lang="ja-Kana">
<surname>ナカニシ</surname>
<given-names>ヒデヒコ</given-names>
</name>
</name-alternatives>
<xref ref-type="aff" rid="aff2">**</xref>
</contrib>
<aff-alternatives id="aff2">
<aff>
<institution xml:lang="ja-Jpan">国立言語学博物館</institution>
</aff>
<aff>
<institution xml:lang="en">National Museum of Linguistics</institution>
</aff>
</aff-alternatives>
</contrib-group>
...
</article-meta>
...
Example 4
The correct name given with an sz ligature, with an alternate name for indexing:
...
<contrib contrib-type="author">
<name-alternatives>
<name specific-use="primary" name-style="western">
<surname>Stoeßel</surname>
<given-names>Jan</given-names></name>
<name specific-use="index" name-style="western">
<surname>Stoessel</surname>
<given-names>Helen</given-names></name>
</name-alternatives>
</contrib>
...
Example 5
Preserving both incorrect (as delivered) and as-corrected names:
...
<contrib contrib-type="author">
<name-alternatives>
<name><surname>Smyth</surname>
<given-names>John</given-names></name>
<name specific-use="invalid">
<surname>Smith</surname>
<given-names>John</given-names></name>
</name-alternatives>
</contrib>
...
Example 6
<name-alternatives> for indexing (Vietnamese):
...
<name-alternatives>
<string-name content-type="display">
<given-names>Le Thi Tuyet</given-names> <surname>Lan</surname>
</string-name>
<string-name content-type="index">
<surname>Lan</surname> <given-names>Le TT</given-names>
</string-name>
</name-alternatives>
...
Example 7
<name-alternatives> for indexing (Hispanic):
...
<name-alternatives>
<name content-type="display">
<surname initials="S">Sánchez Pérez-Castejón</surname>
<given-names>Pedro</given-names>
</name>
<name content-type="index">
<surname>Sánchez</surname>
<given-names>Pedro</given-names>
</name>
</name-alternatives>
...
Example 8
Ethiopian name with abbreviated surname:
...
<name-alternatives>
<name content-type="display">
<surname>G/Selassie</surname>
<given-names>Getachew</given-names>
</name>
<name content-type="index">
<surname>Gebreselassie</surname>
<given-names>Getachew</given-names>
</name>
</name-alternatives>
...