Coverage
<Coverage>
A composite showing coverage or holdings of a serial resource.
Must include one and only one occurrence of each of <CoverageDescriptionLevel>, <SupplementInclusion>, and <IndexInclusion>. It must include one occurrence of <FixedCoverage>, or one occurrence of <MovingCoverage>, or one of each. <SupplementCoverage> is optional and non-repeating.
<Coverage>
<CoverageDescriptionLevel>
Mandatory within <Coverage>
Not repeatable
The degree of explicitness used in expressing sequences in the coverage statement. The following values are permitted:
01 (Predictive): the coverage statement contains open or moving sequences. It may also contain fixed sequences.
02 (Compressed): the coverage statement contains only fixed coverage. It may include sequences or individual item lists, but does not include any moving coverage.
03 (ItemByItem): the coverage statement lists each release individually, with no sequences.
Permissible code values:
01 Predictive
02 Compressed
03 ItemByItem
<Coverage>
<SupplementInclusion>
Mandatory within <Coverage>
Not repeatable
Specifies whether supplements are included in the coverage statement. The following values are permitted:
01 (Explicit): all included supplements are detailed in a <SupplementCoverage> composite.
02 (Implicit): all supplements that were released during the time period(s) included in this coverage statement are assumed to be included.
03 (None): there are no supplements within the stated coverage.
04 (Unspecified): the coverage statement carries no information about the inclusion or exclusion of supplements.
If <SupplementInclusion> = “Explicit”, then <SupplementCoverage> must be present.
Permissible code values:
01 Explicit
02 Implicit
03 None
04 Unspecified
<Coverage>
<IndexInclusion>
Mandatory within <Coverage>
Not repeatable
Specifies whether indexes are included in the coverage statement. The following values are permitted:
01 (Explicit): all included indexes are detailed in a <SupplementCoverage> composite
02 (Implicit): all indexes that were released during the time period(s) included in this coverage statement are assumed to be included
03 (None): there are no indexes within the stated coverage
04 (Unspecified): the coverage statement carries no information about the inclusion or exclusion of indexes.
If <IndexInclusion> = “Explicit”, then <SupplementCoverage> must be present.
Permissible code values:
01 Explicit
02 Implicit
03 None
04 Unspecified
<Coverage>
<FixedCoverage>
Optional within <Coverage>
Not repeatable
Describes coverage in terms of sequences with a defined start and end, and/or lists of individual releases.
<FixedCoverage> must include at least one instance of <Sequence> or <Release> or both. Single or multiple instances of <Sequence> can be freely interleaved with single or multiple instances of <Release>. This is useful if there are gaps in holdings or coverage.
Either <FixedCoverage> or <MovingCoverage> or both must be included in any occurrence of <Coverage>.
<Coverage> <FixedCoverage>
<Sequence>
Optional within <FixedCoverage>
Repeatable
A range of consecutive releases with a fixed start and end. Repeatable to specify multiple sequences.
<Sequence> must include both <SequenceStart> and <SequenceEnd>.
<Coverage> <FixedCoverage> <Sequence>
<SequenceStart>
Mandatory within <Sequence>
Not repeatable
The enumeration and/or chronology of the first in a sequence of consecutive releases. Must include either <Enumeration> or <NominalDate> or both.
<Coverage> <FixedCoverage> <Sequence> <SequenceStart>
<Enumeration>
Optional within <SequenceStart>
Not repeatable
Enumeration of the first in a sequence of consecutive releases.
The <Leveln> composites carry the enumeration of a release, in descending hierarchical order, always starting with Level 1. Up to 6 levels of enumeration may be specified.
Example 1: This is an example of 3 levels of enumeration: Volume 541, Number 1, Part 1.
<Enumeration>
<Level1>
<Unit>Volume</Unit>
<Number>541</Number>
</Level1>
<Level2>
<Unit>Number</Unit>
<Number>1</Number>
</Level2>
<Level3>
<Unit>Part</Unit>
<Number>1</Number>
</Level3>
</Enumeration>
Example 2: This is an example of <AdditionalEnumeration>. The release is numbered both with Volume/Issue and alternatively with consecutive Issue numbers. It also illustrates the use of the “nscript” attribute.
<Enumeration>
<Level1>
<Unit>Volume</Unit>
<Number nscript=”rn”>XCIII</Number> rn = Roman numeral
</Level1>
<Level2>
<Unit>Number</Unit>
<Number>4</Number>
</Level2>
<AdditionalEnumeration>
<Level1>
<Unit>Issue</Unit>
<Number>4269</Number>
<Level1>
</AdditionalEnumeration>
</Enumeration>
Example 3: This example illustrates <EnumerationNote> and the “ntype” attribute.
<Enumeration>
<Level1>
<Unit>Legislature</Unit>
<Number ntype=”2”>24</Number> 2 = ordinal
</Level1>
<Level2>
<Unit>Session</Unit>
<Number ntype=”2”>4</Number> 2 = ordinal
</Level2>
<Level3>
<Unit>Issue</Unit>
<Number>20</Number>
</Level3>
<EnumerationNote>24th Legislature, 4th Session, Issue 20</Enumeration Note>
</Enumeration>
<Coverage> <FixedCoverage> <Sequence> <SequenceStart> <Enumeration>
<Level1>
Mandatory within <Enumeration>
Not repeatable
The <Leveln> composites carry the enumeration of a release, in descending hierarchical order, always starting with Level 1. Up to 6 levels of enumeration may be specified.
A <Leveln> composite may contain only one of the elements <Unit>, <ImpliedUnit> or <NamedUnit>.
All of the Enumeration levels 2-6 are optional and structured identically to <Level1>. Each level must be preceded by the previous level. Levels must appear in order and there may be no gaps.
Example 1: Implied Unit.
Wording on the piece is “2002-5: septembre 2002”
“Year” and “Number” are assumed, expressed in the language of the piece.
This example also illustrates the use of the “language” attribute.
<Enumeration>
<Level1>
<ImpliedUnit language=”fre”>Année</ImpliedUnit>
<Number>2002</Number>
</Level1>
<Level2>
<ImpliedUnit language=”fre”>Numéro</ImpliedUnit>
<Number>5</Number>
</Level2>
</Enumeration>
Example 2: Named Unit. Here the enumeration of the serial has started over again with a “New Series”. This is the enumeration of the first issue in the new series numbering.
<Enumeration>
<Level1>
<NamedUnit>New Series</NamedUnit>
</Level1>
<Level2>
<Unit>Volume</Unit>
<Number>1</Number>
</Level2>
<Level3>
<Unit>Number</Unit>
<Number>1</Number>
</Level3>
</Enumeration>
Example 3: Unit Abbreviation.
Wording on piece: v. 22, no. 36
<Enumeration>
<Level1>
<Unit>Volume</Unit>
<UnitAbbr>
<UnitAbbrType>00</UnitAbbrType> 00 = “unspecified”
<Abbreviation>v.</Abbreviation>
</UnitAbbr>
<Number>22</Number>
</Level1>
<Level2>
<Unit>Number</Unit>
<UnitAbbr>
<UnitAbbrType>00</UnitAbbrType> 00 = “unspecified”
<Abbreviation>no.</Abbreviation>
</UnitAbbr>
<Number>36</Number>
</Level2>
</Enumeration>
<Coverage> <FixedCoverage> <Sequence> <SequenceStart> <Enumeration> <Level1>
<Unit>
Optional within <Leveln>
Repeatable if multiple languages are used on the piece
Has optional “language” attribute (see code list 74 for values – these are equivalent to ISO 639-2/B)
Enumeration unit stated on the piece: name in full. Optional, but inclusion is strongly recommended whenever applicable. If the unit is abbreviated on the piece, the full name should be used here, and the abbreviation placed in <UnitAbbr>.
If <Unit> is present, <Number> must also be present
<Coverage> <FixedCoverage> <Sequence> <SequenceStart> <Enumeration> <Level1>
<ImpliedUnit>
Optional within <Leveln>
Repeatable if multiple languages are used on the piece
Has optional “language” attribute (see code list 74 for values – these are equivalent to ISO 639-2/B)
Enumeration unit, not named on the piece. Optional, but inclusion is strongly recommended whenever applicable. <Unit> and <ImpliedUnit> are mutually exclusive elements.
If <ImpliedUnit> is present, <Number> must also be present
<Coverage> <FixedCoverage> <Sequence> <SequenceStart> <Enumeration> <Level1>
<UnitAbbr>
Optional within <Leveln>
Not repeatable
An abbreviated form of the name of the enumeration unit. May be used in addition to <Unit> or <ImpliedUnit>, or in place of either of them.
<Coverage> <FixedCoverage> <Sequence> <SequenceStart> <Enumeration> <Level1> <UnitAbbr>
<UnitAbbrType>
Optional within <UnitAbbr>
Not repeatable
A code specifying the source of the abbreviation.
Permissible code values:
00 Unspecified
01 Proprietary
02 AACR2 (1998)
03 ISO 832:1984
<Coverage> <FixedCoverage> <Sequence> <SequenceStart> <Enumeration> <Level1> <UnitAbbr>
<AbbrTypeName>
Optional within <UnitAbbr>
Not repeatable
The name of the source of the abbreviation, used only when <AbbrType> = 01 (“proprietary”)
<Coverage> <FixedCoverage> <Sequence> <SequenceStart> <Enumeration> <Level1> <UnitAbbr>
<Abbreviation>
Mandatory within <UnitAbbr>
Repeatable if multiple languages are used on the piece
Has optional “language” attribute (see code list 74 for values – these are equivalent to ISO 639-2/B)
The abbreviation itself.
<Coverage> <FixedCoverage> <Sequence> <SequenceStart> <Enumeration> <Level1>
<Number>
Optional within <Leveln>
Not repeatable
Has optional attributes nformat, ntype, nscript, textscript
A numeric or alphanumeric string that specifies an enumeration unit in a sequence of such units.
If <Number> is present, <NamedUnit> may not be present.
Values for attribute “nformat” are found in code list 118
Values for attribute “ntype” are found in code list 120
Values for attribute “nscript” are found in code list 119
Values for attribute “textscript” are taken from ISO 15924 (http://www.unicode.org/iso15924)
Please see ONIX Serials Coverage Overview for more details about the use of these attributes.
<Coverage> <FixedCoverage> <Sequence> <SequenceStart> <Enumeration> <Level1>
<NamedUnit>
Optional within <Leveln>
Repeatable if multiple languages are used on the piece
Has optional “language” attribute (see code list 74 for values – these are equivalent to ISO 639-2/B)
Text naming a unit in the enumeration that has no associated sequence numbering. Used, for example, for New Series or its equivalent.
If <NamedUnit> is present, <Number> may not be present.
<Coverage> <FixedCoverage> <Sequence> <SequenceStart> <Enumeration>
<Level2>
Optional within <Enumeration>
Not repeatable
All of the Enumeration levels 2-6 are optional and structured identically to <Level1>. Each level must be preceded by the previous level. Levels must appear in order and there may be no gaps.
<Coverage> <FixedCoverage> <Sequence> <SequenceStart> <Enumeration>
<Level3>
Optional within <Enumeration>
Not repeatable
All of the Enumeration levels 2-6 are optional and structured identically to <Level1>. Each level must be preceded by the previous level. Levels must appear in order and there may be no gaps.
<Coverage> <FixedCoverage> <Sequence> <SequenceStart> <Enumeration>
<Level4>
Optional within <Enumeration>
Not repeatable
All of the Enumeration levels 2-6 are optional and structured identically to <Level1>. Each level must be preceded by the previous level. Levels must appear in order and there may be no gaps.
<Coverage> <FixedCoverage> <Sequence> <SequenceStart> <Enumeration>
<Level5>
Optional within <Enumeration>
Not repeatable
All of the Enumeration levels 2-6 are optional and structured identically to <Level1>. Each level must be preceded by the previous level. Levels must appear in order and there may be no gaps.
<Coverage> <FixedCoverage> <Sequence> <SequenceStart> <Enumeration>
<Level6>
Optional within <Enumeration>
Not repeatable
All of the Enumeration levels 2-6 are optional and structured identically to <Level1>. Each level must be preceded by the previous level. Levels must appear in order and there may be no gaps.
<Coverage> <FixedCoverage> <Sequence> <SequenceStart> <Enumeration>
<EnumerationNote>
Optional within <Enumeration>
Repeatable if expressed in multiple languages
Has optional “language” attribute. (see code list 74 for values – these are equivalent to ISO 639-2/B)
A free text note clarifying the enumeration.
<Coverage> <FixedCoverage> <Sequence> <SequenceStart> <Enumeration>
<AdditionalEnumeration>
Optional within <Enumeration>
Repeatable for multiple additional or alternate enumerations.
Additional or alternative enumeration of a release, if any. This would be used, for example, if a release was given a volume/issue enumeration and also a sequential issue-only enumeration. Repeatable if there are multiple alternate enumerations. The <AdditionalEnumeration> composite is structured identically to <Enumeration> found earlier in this document, except that it does not include <AdditionalEnumeration>.
<Coverage> <FixedCoverage> <Sequence> <SequenceStart>
<NominalDate>
Optional within <SequenceStart>
Repeatable if date is expressed in more than one calendar
The “cover” date of the first release in a sequence: repeatable if the date is given under more than one calendar, eg Hebrew and Gregorian.
Example:
<NominalDate>
<Calendar>00</Calendar> 00 = “Gregorian”
<DateFormat>00</DateFormat> 00 = “YYYYMMDD”
<Date>20060402</Date>
</NominalDate>
<Coverage> <FixedCoverage> <Sequence> <SequenceStart> <NominalDate>
<Calendar>
Optional within <NominalDate>
Not repeatable
A code indicating the calendar in which the date is given. If omitted, the default is "00” (Gregorian).
Permissible code values:
00 Gregorian (default)
01 Hebrew
<Coverage> <FixedCoverage> <Sequence> <SequenceStart> <NominalDate>
<Date>
Mandatory within <NominalDate>
Not repeatable
A date, or spread of dates, in the specified calendar and format.
<Coverage> <FixedCoverage> <Sequence>
<SequenceEnd>
Mandatory within <Sequence>
Not repeatable
The enumeration and/or chronology of the last in a sequence of consecutive releases. Must include either <Enumeration> or <NominalDate> or both.
This composite is structured identically to <SequenceStart> above.
<Coverage> <FixedCoverage>
<Release>
Optional within <FixedCoverage>
Repeatable
Enumeration, chronology and other details about an individual release. <Release> must contain at least one of <Enumeration> or <NominalDate> or <IncludedRelease>. The composites <Enumeration> and <NominalDate> are structured identically to these composites found earlier in this document.
<Coverage> <FixedCoverage> <Release>
<ReleaseTitle>
Optional within <Release>
Repeatable if multiple title types are sent
The title of an individual release, for releases that have a specific title, used for example when a journal issue has a thematic title. If multiple types of title are sent, the entire <ReleaseTitle> composite is repeated.
<Coverage> <FixedCoverage> <Release> <ReleaseTitle>
<TitleType>
Optional within <ReleaseTitle>
Not repeatable.
A code showing the type of title. If omitted, the title type defaults to “00” (undefined).
Permissible code values:
00 Undefined
01 Distinctive title(book); cover title (serial)
09 Sender's catalog title
<Coverage> <FixedCoverage> <Release> <ReleaseTitle>
<TitleText>
Mandatory within <ReleaseTitle>
Repeatable if title is expressed in multiple languages
Has optional “language” attribute (see code list 74 for values – these are equivalent to ISO 639-2/B)
The text of the title, excluding subtitle.
<Coverage> <FixedCoverage> <Release> <ReleaseTitle>
<Subtitle>
Optional within <ReleaseTitle>
Repeatable if subtitle is expressed in multiple languages
Has optional “language” attribute (see code list 74 for values – these are equivalent to ISO 639-2/B)
The text of the subtitle, if there is one.
<Coverage> <FixedCoverage> <Release>
<IncludedRelease>
Optional within <Release>
Repeatable 2 or more times
The enumeration, chronology and/or title of a component of a combined release. Repetitions of the <IncludedRelease> composite are used to identify each included item within the <Release> composite. If present, there will be two or more occurrences. If the combined release has enumeration of its own, then <Enumeration> will also be present within <Release>.
Must contain one or more of <Enumeration>, <NominalDate>, or <ReleaseTitle>. These composites are expanded as shown earlier in this document.
<Coverage>
<MovingCoverage>
Optional within <Coverage>
Not repeatable
An open-ended coverage sequence, from either a defined start or a “moving start” to either the present or to a “moving end”.
Either <FixedStart> or <MovingStart>, but not both, must appear in <MovingCoverage>. If no <MovingEnd> composite appears, the sequence ends with the current (most recent) release.
<MovingCoverage> is explained in further detail in ONIX Serials Coverage Overview.
<Coverage> <MovingCoverage>
<FixedStart>
Optional within <MovingCoverage>
Not repeatable
The enumeration and/or chronology of the first in a sequence of consecutive releases. Must include either <Enumeration> or <NominalDate> or both. These composites are expanded as shown earlier in this document.
<Coverage> <MovingCoverage>
<MovingStart>
Optional within <MovingCoverage>
Not repeatable
The beginning of a sequence of consecutive releases, where the beginning of the sequence moves in relation to the present time.
<MovingStart> must contain either <BackBySpecifiedPeriod> or <BackToSpecifiedDay> or both.
Example 1: Access to this resource begins 12 months ago. This is sometimes known as a “rolling start.”
<MovingStart>
<BackBySpecifiedPeriod>
<CountUnit>Month</Month>
<CountBack>12</CountBack>
</BackBySpecifiedPeriod>
</MovingStart>
Example 2: Access to this resource begins 2 Januaries ago. (Count back twice to January 1). This is sometimes known as a “jumping start”
<MovingStart>
<BackToSpecifiedDay>
<DayFormat>01</DayFormat> “01” = month and day, MMYY
<Day>0101</Day> January 1
<CountBack>2</CountBack> count back twice
</BackToSpecifiedDay>
</MovingStart>
<Coverage> <MovingCoverage> <MovingStart>
<BackBySpecifiedPeriod>
Optional within <MovingStart>
Not repeatable
Indicates that the sequence begins a certain period from the present (or latest release). This is sometimes known as a “rolling start;” for example, “latest 12 months available.”
Must include both <CountUnit> and <CountBack>.
<Coverage> <MovingCoverage> <MovingStart> <BackBySpecifiedPeriod>
<CountUnit>
Mandatory within <BackBySpecifiedPeriod>
Not repeatable
The unit in which <BackBySpecifiedPeriod> is counted.
Permissible code values:
01 Number of issues
02 Number of days
03 Number of months
04 Number of years
<Coverage> <MovingCoverage> <MovingStart> <BackBySpecifiedPeriod>
<CountBack>
Mandatory within <BackBySpecifiedPeriod>
Not repeatable
The number of units to count back.
<Coverage> <MovingCoverage> <MovingStart>
<BackToSpecifiedDay>
Optional within <MovingStart>
Not repeatable
Indicates that the sequence begins on a certain day related either to the present or to the period specified in <BackBySpecifiedPeriod>. This is sometimes known as a “jumping start;” for example, “current calendar year available online,” indicating that coverage begins on Jan. 1 of the current year.
Must include <DayFormat>, <Day>, and <CountBack>.
<Coverage> <MovingCoverage> <MovingStart> <BackToSpecifiedDay>
<Calendar>
Optional within <BackToSpecifiedDay>
Not repeatable
Calendar in which days are specified. If omitted, defaults to “Gregorian.”
Permissible code values:
00 Gregorian (default)
01 Hebrew
<Coverage> <MovingCoverage> <MovingStart> <BackToSpecifiedDay>
<Day>
Mandatory within <BackToSpecifiedDay>
Not repeatable
A day in the format specified in <DayFormat>
<Coverage> <MovingCoverage> <MovingStart> <BackToSpecifiedDay>
<CountBack>
Mandatory within <BackToSpecifiedDay>
Not repeatable
The number of times to count back.
<Coverage> <MovingCoverage>
<MovingEnd>
Optional within <MovingCoverage>
Not repeatable
The end of a sequence of consecutive releases, where the end of the sequence moves in relation to the present time.
<MovingEnd> is structured identically to the <MovingStart> composite. It must contain either <BackBySpecifiedPeriod> or <BackToSpecifiedDay> or both, as described earlier in this document.
Common examples of a moving end are an “embargo” (e.g. last 6 months not available online) and a “moving wall” (e.g. previous 5 calendar years not available online).
Example 1: the last 6 months of this resource are not accessible online.
<MovingEnd>
<BackBySpecifiedPeriod>
<CountUnit>03</CountUnit> “03” = month
<CountBack>6</CountBack> count back 6 months
</BackBySpecifiedPeriod>
</MovingEnd>
Example 2: the current calendar year and the previous 4 calendar years are not accessible online.
<MovingEnd>
<BackToSpecifiedDay>
<DayFormat>01</DayFormat> “01” = month and day, MMYY
<Day>0101</Day> January 1
<CountBack>5</CountBack> count back to January 1 five times
</BackToSpecifiedDay>
</MovingEnd>
<Coverage>
<SupplementCoverage>
Optional within <Coverage>
Not repeatable
Enumeration, chronology and other details of supplements and/or indexes (indexes are treated as a special case of supplements, in <Coverage>). All supplement and index enumeration and chronology are kept in this composite. Used when and only when <SupplementInclusion> or <IndexInclusion> = Explicit.
<Coverage> <SupplementCoverage>
<SupplementRun>
Mandatory within <SupplementCoverage>
Repeatable
The coverage of each supplement or index run is described in its own <SupplementRun> composite. Supplement runs are distinguished from one another by having differing enumeration schemes, or they may have unique supplement series titles and/or identifying numbers.
Each <SupplementRun> must include either a <SupplementFixedCoverage> composite or a <SupplementMovingCoverage> composite, or both.
<Coverage> <SupplementCoverage> <SupplementRun>
<IndexRun/>
Optional within <SupplementRun>
Not repeatable
An empty element indicating that a supplement run consists of indexes.
<Coverage> <SupplementCoverage> <SupplementRun>
<SeriesIdentifier>
Optional within <SupplementRun>
Repeatable if there are multiple identifiers
Identifier of a supplement series. Used only if the supplement run is a series that carries an identifying number, usually an ISSN.
<Coverage> <SupplementCoverage> <SupplementRun> <SeriesIdentifier>
<SeriesIDType>
Mandatory within <SeriesIdentifier>
Not repeatable
The scheme from which an identifier is taken.
Permissible code values:
01 Proprietary
02 ISSN
06 DOI
<Coverage> <SupplementCoverage> <SupplementRun> <SeriesIdentifier>
<IDTypeName>
Optional within <SeriesIdentifier>
Not repeatable
The name of an identifier scheme, if <SeriesIDType> = “Proprietary.”
<Coverage> <SupplementCoverage> <SupplementRun> <SeriesIdentifier>
<IDValue>
Mandatory within <SeriesIdentifier>
Not repeatable
An identifier value, from the specified scheme.
<Coverage> <SupplementCoverage> <SupplementRun>
<SeriesTitle>
Optional within <SupplementRun>
Repeatable if multiple title types are sent
Title of a supplement series. Used only if the supplement run is a series that carries its own title. If multiple title types are sent, the entire <SeriesTitle> composite is repeated.
<Coverage> <SupplementCoverage> <SupplementRun> <SeriesTitle>
<TitleType>
Optional within <SeriesTitle>
Not repeatable
The type of title. If omitted, defaults to “Undefined.”
Permissible code values:
00 Undefined
01 Distinctive title(book); cover title (serial)
09 Sender's catalog title
<Coverage> <SupplementCoverage> <SupplementRun> <SeriesTitle>
<TitleText>
Mandatory within <SeriesTitle>
Repeatable if title is expressed in multiple languages
Has optional “language” attribute (see code list 74 for values – these are equivalent to ISO 639-2/B)
The text of the title proper of the supplement series.
<Coverage> <SupplementCoverage> <SupplementRun> <SeriesTitle>
<Subtitle>
Optional within <SeriesTitle>
Repeatable if subtitle is expressed in multiple languages
Has optional “language” attribute (see code list 74 for values – these are equivalent to ISO 639-2/B)
The text of the subtitle of the supplement series, if any.
<Coverage> <SupplementCoverage> <SupplementRun>
<SupplementFixedCoverage>
Optional within <SupplementCoverage>
Not repeatable
Describes supplement coverage in terms of sequences of consecutive supplements with a defined start and end, and/or lists of individual supplements.
<SupplementFixedCoverage> must include at least one instance of <SupplementSequence> or <Supplement> or both. Single or multiple instances of <SupplementSequence> can be freely interleaved with single or multiple instances of <Supplement>. This is useful if there are gaps in holdings or coverage.
Either <SupplementFixedCoverage> or <SupplementMovingCoverage> or both must be included in any occurrence of <SupplementRun>.
<Coverage> <SupplementCoverage> <SupplementRun> <SupplementFixedCoverage>
<SupplementSequence>
Optional within <SupplementFixedCoverage>
Repeatable to specify multiple sequences
A range of consecutive supplements, with a fixed start and end. Must contain one and only one occurrence of each of <SupplementSequenceStart> and <SupplementSequenceEnd>
<Coverage> <SupplementCoverage> <SupplementRun> <SupplementFixedCoverage> <SupplementSequence>
<SupplementSequenceStart>
Mandatory within <SupplementSequence>
Not repeatable
The first in a sequence of consecutive supplements. Must include at least one of <DependentEnumeration> or <IndependentEnumeration> or <SupplementNominalDate>.
<Coverage> <SupplementCoverage> <SupplementRun> <SupplementFixedCoverage> <SupplementSequence> <SupplementSequenceStart>
<DependentEnumeration>
Optional within <SupplementSequenceStart>
Not repeatable
Enumeration of a supplement when the enumeration of the main run is required to definitively identify the supplement. Must be preceded by <MainRunEnumeration> and/or <MainRunNominalDate>.
<DependentEnumeration> is expanded identically to <Enumeration> found earlier in this document, except that <AdditionalEnumeration> is named <AdditionalDependentEnumeration> here.
<Coverage> <SupplementCoverage> <SupplementRun> <SupplementFixedCoverage> <SupplementSequence> <SupplementSequenceStart>
<IndependentEnumeration>
Optional within <SupplementSequenceStart>
Not repeatable
Enumeration of a supplement, when the supplement carries enumeration of its own not requiring MainRunEnumeration for unique identification.
<MainRunEnumeration> may also be present, if the supplement has independent enumeration but is also associated with a part of the main run.
<IndependentEnumeration> is expanded identically to <Enumeration> found earlier in this document, except that <AdditionalEnumeration> is named <AdditionalIndependentEnumeration> here.
<Coverage> <SupplementCoverage> <SupplementRun> <SupplementFixedCoverage> <SupplementSequence>
<SupplementSequenceEnd>
Mandatory within <SupplementSequence>
Not repeatable
The last in a sequence of consecutive supplements. Must include at least one of <DependentEnumeration> or <IndependentEnumeration> or <SupplementNominalDate>.
Expansion of <SupplementSequenceEnd> is identical to that of <SupplementSequenceStart> found earlier in this document.
<Coverage> <SupplementCoverage> <SupplementRun> <SupplementFixedCoverage> <SupplementSequence>
<IndexedSequence>
Optional within <SupplementSequence>
Not repeatable
Range of main run volumes or issues covered by a sequence of indexes. Used only when a supplement run consists of indexes; that is, <SupplementRun> includes the empty element <IndexRun/>.
Includes both <StartEnumeration> and optionally <EndEnumeration>, which are both expanded identically to <Enumeration> found earlier in this document. If the indexes cover only one Enumeration (e.g. “volume 4), then <SequenceEnd> may be omitted.
<Coverage> <SupplementCoverage> <SupplementRun> <SupplementFixedCoverage> <SupplementSequence>
<IndexedPeriod>
Optional within <SupplementSequence>
Not repeatable
Range of dates covered by a sequence of indexes. Used only when a supplement run consists of indexes; that is, <SupplementRun> includes the empty element <IndexRun/>.
The expansion of <IndexedPeriod> is identical to that of <NominalDate> found earlier in this document.
<Coverage> <SupplementCoverage> <SupplementRun> <SupplementFixedCoverage>
<Supplement>
Optional within <SupplementFixedCoverage>
Repeatable
Details and enumeration or chronology of an individual supplement. Must include one or more of <DependentEnumeration> or <IndependentEnumeration> or <SupplementReleaseTitle> or <SupplementNominalDate>.
<Coverage> <SupplementCoverage> <SupplementRun> <SupplementFixedCoverage> <Supplement>
<Index/>
Optional within <Supplement>
Not repeatable
An empty element indicating that an individual supplement is an index.
<Coverage> <SupplementCoverage> <SupplementRun> <SupplementFixedCoverage> <Supplement>
<MainRunEnumeration>
Optional within <Supplement>
Not repeatable
Enumeration of a main run volume, issue or part. used when the supplement is explicitly associated with a part of the main run of the serial version.
<
