EDItEUR logo

ONIX Serials Release Notification Message Formats

Issue Notice

Version 0.92 User Guide

Date issued: May 2008

This User Guide has been prepared for the EDItEUR / NISO Joint Working Party for the Exchange of Serials Subscription Information by Katharina Klemperer, David Martin and Francis Cave. It is designed to accompany a machine-readable specification of the formats written in XML Schema, which has been developed by Francis Cave.

General guidance on schema use

This schema provides a formal specification of what constitutes valid use of XML to construct ONIX Serials Release Notification (SRN) messages of type Issue Notice. A complete list of schemas in the SRN family is given below.

As well as specifying the XML tags that may be used and in what sequence, it also specifies valid ranges of data values for data contained in XML elements, i.e. between matching pairs of XML tags.

The schema to which this document refers comprises two files, which together form an XML document that conforms to the XML Schema Recommendation of the World Wide Web Consortium (W3C). The two files are:

Filename

  

Description of content

  

ONIX_SerialsReleaseNotification_n.n.xsd

  

definitions of the message-level element and of complex types specific to this type of message (the number 'n.n' is the version number of this schema)

  

ONIX_Serials_CodeLists.xsd

  

definitions of datatypes common to all ONIX Serials schemas.

  

For further information see XML Schema Part 1: Structures and XML Schema Part 2: Datatypes.

It is intended that this schema be used to guide implementation of systems for either originating or receiving SRN messages. Used in conjunction with a suitable “schema parser” it may also be used to validate the structure and contents of an individual message.

This schema defines how the substance, or “payload”, of SRN messages are to be represented in XML, but is silent on the question of how this message is to be conveyed from originator to recipient. It is likely that supply chain partners will need to adopt different approaches to message transport, packaging and delivery, depending upon the specific business systems in which this message format is being implemented.

Guidance on reading the message format specifications

In this user guide, examples are given for entire composites in order to illustrate situations in which the composites are used. Generally examples are not given for the lowest level elements.

In this user guide each successive XML element is illustrated by a graphic which shows any “child” elements. Clicking on any “child” element will take you to the description of that element. Clicking “Back” will return you to the “parent”.

If a “child” element is shown with a solid outline, the element is mandatory in any occurrence of the “parent”. If it is shown with a dotted outline, it is conditional in this context. If it is repeatable, the element box has the legend “1..∞” or “0..∞” immediately below it, indicating “mandatory and repeatable” or “conditional and repeatable”.

All data types are based upon built-in primitive data types defined in XML Schema Part 2: Datatypes. The names of all pre-defined data types are prefixed by “xs:” and include:

xs:string

  

a string of characters

  

xs:decimal

  

a number that may have a decimal part

  

xs:int

  

an integer between -2147483648 and +2147483647 inclusive

  

Introduction

The ONIX Serials Release Notification (SRN) format defines a family of XML messages used to exchange information about the planned or confirmed publication or electronic availability of one or more serial releases from a party that supplies the resources, or from an intermediary, to a party that needs this information in its systems. Please see the ONIX Serials Release Notification Overview for a general introduction to the SRN messages and their applications. The following messages have been defined:

ONIXSRNIssueNotice. Used to announce the confirmed physical publication date or online availability date of an issue of a serial publication or a supplement to a monograph. Also used to announce the provisional or expected physical publication date or online availability date of an issue of a serial publication or a supplement to a monograph.

ONIXSRNContentItemDescription. Used to transmit information describing individual items within the release, for confirmed or provisional releases. In the journal context, a content item would be an article, but in other contexts it may be a chapter, a track on a recording or . May also be used to announce the release or forthcoming release of individual content items (usually articles) that are not associated with a particular issue; for example, articles made available online prior to publication of a journal issue. Content item description messages include enough information to generate a bibliographic citation for individual articles.

ONIXSRNContentItemExtendedDescription. Used to transmit detailed information about the individual content items (usually articles) in a release, including such information as abstracts, subject headings and details of reviewed resources (when a content item is a review). Content item extended description messages include enough information to create entries in abstracting and indexing databases.

Some words or phrases are used throughout ONIX for Serials with a very specific meaning. These are defined in the ONIX for Serials Glossary.

Related Documents

Please refer to the following documents for a more detailed introduction to the SRN format:

SRN Overview Version 0.92
(http://www.editeur.org/onixserials/ONIX_SRN_Overview_0.92.pdf)
ONIX Serials Glossary
(http://www.editeur.org/onixserials/ONIX_Serials_glossary.pdf)

ONIX SRN Issue Notice

<ONIXSRNIssueNotice>

The ONIXSRNIssueNotice is used to announce the confirmed physical publication date or online availability date of an issue of a serial publication or a supplement to a monograph. Also used to announce the provisional or expected physical publication date or online availability date of an issue of a serial publication or a supplement to a monograph.

<ONIXSRNIssueNotice>
<Header>

Mandatory and non-repeatable within <ONIXSRNIssueNotice> .

The <Header> contains administrative information including metadata and contact information about the sender and the addressee(s) of the message and “housekeeping” information such as message number and date and time sent.

<ONIXSRNIssueNotice> <Header>
<Sender>

Mandatory and non-repeatable within <Header> .

Identification of the organization that is sending the message.

Must contain either <SenderIdentifier> or <SenderName> or both.

Example:

<Sender>

            <SenderIdentifier>

                        <SenderIDType>07</SenderIDType>    07 = “SAN”

                        <IDValue>1234567</IDValue>

            </SenderIdentifier>

            <SenderName>Oxford University Press</SenderName>

            <SenderContact>Subscriptions Department</SenderContact>

            <SenderEmail>subscriptions@oupjournals.org</SenderEmail>

</Sender>

<ONIXSRNIssueNotice> <Header> <Sender>
<SenderIdentifier>

Optional and repeatable within <Sender> .

Identification of the sender, using a value from a standard or proprietary identification scheme.

<ONIXSRNIssueNotice> <Header> <Sender> <SenderIdentifier>
<SenderIDType>

Mandatory and non-repeatable within <SenderIdentifier> .

A code indicating the scheme or standard from which the sender identifier is taken. If <SenderIDType> is 01 (proprietary), then the name of the scheme should appear in <IDTypeName>.

Permissible code values (code list 44A):

01     Proprietary

06     EAN-UCC GLN – Global location number (formerly EAN location number)

07     SAN – Book trade Standard Address Number - US, UK etc

08     MARC21 organizations code – MARC code list for organizations - www.loc.gov/marc/organizations/orgshome.html

09     ISIL – International Standard Identifier for Libraries and Related Organizations - ISO 15511

<ONIXSRNIssueNotice> <Header> <Sender> <SenderIdentifier>
<IDTypeName>

Optional and non-repeatable within <SenderIdentifier> .

The name of the identification scheme from which the <IDValue> is taken, used only when <SenderIDType> is “01” (proprietary).

<ONIXSRNIssueNotice> <Header> <Sender> <SenderIdentifier>
<IDValue>

Mandatory and non-repeatable within <SenderIdentifier> .

An identifier of the type specified in <SenderIDType>.

<ONIXSRNIssueNotice> <Header> <Sender>
<SenderName>

Optional and repeatable within <Sender> .

Has optional "language" attribute.

The text name of the sending organization. Repeatable if expressed in multiple languages.

<ONIXSRNIssueNotice> <Header> <Sender>
<SenderContact>

Optional and non-repeatable within <Sender> .

The name of a contact person or group at the sending organization.

<ONIXSRNIssueNotice> <Header> <Sender>
<SenderEmail>

Optional and non-repeatable within <Sender> .

An email address that may be used to contact the sending organization.

<ONIXSRNIssueNotice> <Header>
<Addressee>

Optional and repeatable within <Header> .

Identification of the intended recipient organization(s) for the message.

May be omitted from broadcast messages or those intended for general distribution.

May be repeated if the same message is sent to multiple recipients

Must contain either <AddresseeIdentifier> or <AddresseeName> or both.

Example:

<Addressee>

            <AddresseeIdentifier>

                        <AddresseeIDType>07</AddresseeIDType>     07 = “SAN”

                        <IDValue>1234567</IDValue>

            </AddresseeIdentifier>

            <AddresseeName>Sample University Library</AddresseeName>

            <AddresseeContact>John Q. Librarian</AddresseeContact>

            <AddresseeEmail>jqlibrarian@sampleuniv.edu</AddresseeEmail>

</Addressee>

<ONIXSRNIssueNotice> <Header> <Addressee>
<AddresseeIdentifier>

Optional and repeatable within <Addressee> .

Identification of an Addressee using a value from a standard or proprietary identification scheme.

<ONIXSRNIssueNotice> <Header> <Addressee> <AddresseeIdentifier>
<AddresseeIDType>

Mandatory and non-repeatable within <AddresseeIdentifier> .

A code indicating the scheme or standard from which the Addressee identifier is taken.  If <AddresseeIDType> is “01” (proprietary), then the name of the scheme should appear in <IDTypeName>.

Permissible code values (code list 44A):

01     Proprietary

06     EAN-UCC GLN – Global location number (formerly EAN location number)

07     SAN – Book trade Standard Address Number - US, UK etc

08     MARC21 organizations code – MARC code list for organizations - www.loc.gov/marc/organizations/orgshome.html

09     ISIL – International Standard Identifier for Libraries and Related Organizations - ISO 15511

<ONIXSRNIssueNotice> <Header> <Addressee> <AddresseeIdentifier>
<IDTypeName>

Optional and non-repeatable within <AddresseeIdentifier> .

The name of the identification scheme from which <IDValue> is taken, used only when <AddresseeIDType> is “01” (proprietary).

<ONIXSRNIssueNotice> <Header> <Addressee> <AddresseeIdentifier>
<IDValue>

Mandatory and non-repeatable within <AddresseeIdentifier> .

An identifier of the type specified in <AddresseeIDType>.

<ONIXSRNIssueNotice> <Header> <Addressee>
<AddresseeName>

Optional and repeatable within <Addressee> .

Has optional "language" attribute.

The text name of the sending organization. Repeatable if expressed in multiple languages.

<ONIXSRNIssueNotice> <Header> <Addressee>
<AddresseeContact>

Optional and non-repeatable within <Addressee> .

The name of a contact person or group at the recipient organization.

<ONIXSRNIssueNotice> <Header> <Addressee>
<AddresseeEmail>

Optional and non-repeatable within <Addressee> .

An email address that may be used to contact the recipient organization.

<ONIXSRNIssueNotice> <Header>
<MessageNumber>

Optional and non-repeatable within <Header> .

<MessageNumber> carries a sequence number for ONIX messages of this type sent as part of a series of such messages.  The element is optional and non-repeating, but its use is recommended to underpin process integrity and to act as a check against missed or repeated messages.

Example:

<MessageNumber>1</MessageNumber>

<ONIXSRNIssueNotice> <Header>
<MessageRepeat>

Optional and non-repeatable within <Header> .

A sequence number showing how many times this particular message has been sent, starting with “1” for the first transmission of the message.

<ONIXSRNIssueNotice> <Header>
<SentDateTime>

Mandatory and non-repeatable within <Header> .

A date/time stamp, showing when the message was sent.  The following formats may be used:

YYYYMMDD

YYYYMMDDTHHMM

YYYYMMDDTHHMMZ  (universal time)

YYYYMMDDTHHMM±HHMM (time zone)

where “T” and "Z" are constants; that is, the letters T and Z.  The recommended form is YYYYMMDDTHHMMZ, using universal time (UTC/GMT).

Example:

<SentDateTime>20051020T1550Z</SentDateTime>

<ONIXSRNIssueNotice> <Header>
<MessageNote>

Optional and repeatable within <Header> .

Has optional "language" attribute.

A free-text note about the message. Repeatable if expressed in multiple languages.

Example:

<MessageNote>This message announces all issues of Journal ABC to be released during the month of January, 2007</MessageNote>

<ONIXSRNIssueNotice> <Header>
<NumberDefaultsUnspecified/>

Optional and non-repeatable within <Header> .

An empty element that overrules the regular default values for <Number> attributes (nformat, ntype, nscript, and textscript) in cases where the sender is unable reliably to specify values for those attributes: if this element is not sent, standard defaults are assumed.

<ONIXSRNIssueNotice>
<ReleaseNotice>

Mandatory and repeatable within <ONIXSRNIssueNotice> .

Details of one or more releases belonging either to the same serial version, in which case the <SerialVersion> composite is used to identify the parent serial, series or set; or to a series of supplements to a monograph, in which case the <Monograph> composite is used. In the <ONIXSRNIssueNotice> message, each <ReleaseNotice> must contain either one <SerialVersion> or one <Monograph>, but not both. The <ReleaseNotice> composite is repeated for each <SerialVersion> or <Monograph> for which releases are being announced.

Each <ReleaseNotice> must contain at least one occurrence of <Release>.

<ONIXSRNIssueNotice> <ReleaseNotice>
<SerialVersion>

Optional and non-repeatable within <ReleaseNotice> .

Identification and description of a serial version of which the release(s) described in the ensuing <Release> composite(s) is/are a part. <SerialVersion> must include either <SerialVersionIdentifier> or <SerialWork> or both.

Example: this example shows details of a print Serial Version. <SerialVersionName> has been omitted.  An example of <SerialWork> may be found later in this document.

<SerialVersion>

            <SerialVersionIdentifier>

                        <SerialVersionIDType>07</SerialVersionIDType>      07 = “ISSN”

                        <IDValue>13679430</IDValue>     ISSN for the print version

            </SerialVersionIdentifier>

            <SerialWork>

                        [Serial Work information would appear here]

            </SerialWork>

            <SerialVersionForm>JB</SerialVersionForm>    JB = “Printed Serial”

</SerialVersion>

<ONIXSRNIssueNotice> <ReleaseNotice> <SerialVersion>
<SerialVersionIdentifier>

Optional and repeatable within <SerialVersion> .

A coded identifier of a serial version. Repeatable if multiple identifiers are sent.

<ONIXSRNIssueNotice> <ReleaseNotice> <SerialVersion> <SerialVersionIdentifier>
<SerialVersionIDType>

Mandatory and non-repeatable within <SerialVersionIdentifier> .

A code indicating the scheme or standard from which the serial version identifier is taken.  If <SerialVersionIDType> is “01” (proprietary), then the name of the scheme should appear in <IDTypeName>.

If an ISSN (IDType = “07”), is sent, it should identify only the serial version in question.  An ISSN for a print version should not be used to identify an electronic version, and vice versa.

ISSNs are always sent in their unhyphenated form in ONIX.

Permissible code values (code list 103S):

01     Proprietary

02     ISBN-10 – International Standard Book Number, pre-2007, unhyphenated (10 characters)

03     EAN.UCC-13 – EAN-UCC article number (13 digits)

06     DOI – Digital Object Identifier (variable length and character set)

07     ISSN – International Standard Serial Number, unhyphenated, 8 characters

15     ISBN-13 – International Standard Book Number, from 2007, unhyphenated (13 characters)

<ONIXSRNIssueNotice> <ReleaseNotice> <SerialVersion> <SerialVersionIdentifier>
<IDTypeName>

Optional and non-repeatable within <SerialVersionIdentifier> .

The name of the identification scheme from which the <IDValue> is taken, used only when <SerialVersionIdentifier> is “01” (proprietary).

<ONIXSRNIssueNotice> <ReleaseNotice> <SerialVersion> <SerialVersionIdentifier>
<IDValue>

Mandatory and non-repeatable within <SerialVersionIdentifier> .

An identifier of the type specified in <SerialVersionIDType>.

<ONIXSRNIssueNotice> <ReleaseNotice> <SerialVersion>
<SerialVersionName>

Optional and repeatable within <SerialVersion> .

Has optional "language" attribute.

Name of the serial version.  Used when the serial version has a unique name (different from the title of the serial work). Repeatble if expressed in multiple languages.

<ONIXSRNIssueNotice> <ReleaseNotice> <SerialVersion>
<SerialWork>

Optional and non-repeatable within <SerialVersion> .

The work of which the <SerialVersion> is a manifestation.

Example: This Serial Work has 2 publishers with different Publishing Roles.  It is published by one organization on behalf of another. The <Imprint> and <MirrorSite> composites have been omitted from this example.

<SerialWork>

            <SerialWorkIdentifier>

                        <WorkIDType>01</WorkIDType>     01 = “proprietary”

                        <IDTypeName>Agent’s product dentifier</IDTypeName>

                        <IDValue>ANI0001</IDValue>

            </SerialWorkIdentifier>

            <Title>

                        <TitleType>01</TitleType>     01 = “cover title”

                        <TitleText>Animal Conservation</TitleText>

                        <Subtitle>Quantitative studies for the conservation of populations, species and communities</Subtitle>

            </Title>

            <Imprint> may appear here

            <Publisher>

                        <PublishingRole>01</PublishingRole>     01 = “Publisher”

                        <PublisherIdentifier>

                                    <PublisherIDType>07</PublisherIDType>     07 = “SAN”

                                    <IDValue>1234567</IDValue>

                                    <PublisherName>Blackwell Publishing</PublisherName>

                        </PublisherIdentifier>

            </Publisher>

            <Publisher>

                        <PublishingRole>06</PublishingRole>     06 = “Published on behalf of”

                        <PublisherIdentifier>

                                    <PublisherIDType>07</PublisherIDType>     07 = “SAN”

                                    <IDValue>1234567</IDValue>

                                    <PublisherName>Zoological Society of London</PublisherName>

                        </PublisherIdentifier>

            </Publisher>

            <Website>

                        <WebsiteRole>04</WebsiteRole>     04 = “Journal Home Page”

                        <WebsiteDescription>Journal home page</WebsiteDescription>

                        <WebsiteLink>http://www.blackwellpublishing.com/submit.asp?ref=1367-9430</WebsiteLink>

                        <MirrorSite> may appear here

            </Website>

</SerialWork>

<ONIXSRNIssueNotice> <ReleaseNotice> <SerialVersion> <SerialWork>
<SerialWorkIdentifier>

Optional and repeatable within <SerialWork> .

Identification of a serial work using a value from a standard or proprietary identification scheme.

Repeatable if multiple identifiers are sent.

<ONIXSRNIssueNotice> <ReleaseNotice> <SerialVersion> <SerialWork> <SerialWorkIdentifier>
<WorkIDType>

Mandatory and non-repeatable within <SerialWorkIdentifier> .

A code indicating the scheme or standard from which the serial work identifier is taken.  If <SerialWorkIDType> is “01” (proprietary), then the name of the scheme should appear in <IDTypeName>.

Permissible code values (code list 16S):

01     Proprietary

06     DOI – Digital Object Identifier (variable length and character set)

08     CODEN

11     ISTC – International Standard Text Code (sixteen characters: numerals and letters A-F)

16     ISSN-L – Linking ISSN, (previously known as medium-neutral ISSN), 8 characters, unhyphenated

<ONIXSRNIssueNotice> <ReleaseNotice> <SerialVersion> <SerialWork> <SerialWorkIdentifier>
<IDTypeName>

Optional and non-repeatable within <SerialWorkIdentifier> .

The name of the identification scheme from which the <IDValue> is taken, used only when <SerialWorkIDType> is “01” (proprietary).

<ONIXSRNIssueNotice> <ReleaseNotice> <SerialVersion> <SerialWork> <SerialWorkIdentifier>
<IDValue>

Mandatory and non-repeatable within <SerialWorkIdentifier> .

An identifier of the type specified in <SerialWorkIDType>.

<ONIXSRNIssueNotice> <ReleaseNotice> <SerialVersion> <SerialWork>
<Title>

Mandatory and repeatable within <SerialWork> .

The title of the work of which the serial version is a manifestation.

Repeatable if different title types are sent.

<ONIXSRNIssueNotice> <ReleaseNotice> <SerialVersion> <SerialWork> <Title>
<TitleType>

Optional and non-repeatable within <Title> .

An ONIX code showing the type of title.  If omitted, the title type defaults to “00” (undefined).

Permissible code values (code list 15A):

00     Undefined

01     Cover title – The full text of the title as it appears on the work, without abbreviation or abridgement.

09     Sender's catalog title

<ONIXSRNIssueNotice> <ReleaseNotice> <SerialVersion> <SerialWork> <Title>
<TitleText>

Mandatory and repeatable within <Title> .

Has optional "language" attribute.

The text of the title, excluding subtitle.  Repeatable if expressed in multiple languages.

<ONIXSRNIssueNotice> <ReleaseNotice> <SerialVersion> <SerialWork> <Title>
<Subtitle>

Optional and repeatable within <Title> .

Has optional "language" attribute.

The text of the subtitle, if there is one. Repeatable if expressed in multiple languages.

<ONIXSRNIssueNotice> <ReleaseNotice> <SerialVersion> <SerialWork>
<Imprint>

Optional and non-repeatable within <SerialWork> .

The imprint under which the work is published.

May only appear if <Publisher> also appears within <SerialWork>.

Must contain either <ImprintIdentifier> or <ImprintName> or both.

<ONIXSRNIssueNotice> <ReleaseNotice> <SerialVersion> <SerialWork> <Imprint>
<ImprintIdentifier>

Optional and repeatable within <Imprint> .

Identification of an imprint using a value from a standard or proprietary identification scheme.

Repeatable if multiple identifiers are sent.

<ONIXSRNIssueNotice> <ReleaseNotice> <SerialVersion> <SerialWork> <Imprint> <ImprintIdentifier>
<ImprintIDType>

Mandatory and non-repeatable within <ImprintIdentifier> .

A code indicating the scheme or standard from which the imprint identifier is taken.  If <ImprintIDType> is “01” (proprietary), then the name of the scheme should appear in <IDTypeName>.

Permissible code values (code list 44C):

01     Proprietary

<ONIXSRNIssueNotice> <ReleaseNotice> <SerialVersion> <SerialWork> <Imprint> <ImprintIdentifier>
<IDTypeName>

Optional and non-repeatable within <ImprintIdentifier> .

The name of the identification scheme from which the <IDValue> is taken, used only when <ImprintIDType> is “01” (proprietary).

<ONIXSRNIssueNotice> <ReleaseNotice> <SerialVersion> <SerialWork> <Imprint> <ImprintIdentifier>
<IDValue>

Mandatory and non-repeatable within <ImprintIdentifier> .

An identifier of the type specified in <ImprintIDType>.

<ONIXSRNIssueNotice> <ReleaseNotice> <SerialVersion> <SerialWork> <Imprint>
<ImprintName>

Optional and repeatable within <Imprint> .

Has optional "language" attribute.

The text name of the imprint. Repeatable if expressed in multiple languages.

<ONIXSRNIssueNotice> <ReleaseNotice> <SerialVersion> <SerialWork>
<Publisher>

Optional and repeatable within <SerialWork> .

Publisher of the intellectual content of the work; repeatable if there are co-publishers or if there are publishers with different Publisher Roles.

Must contain either <PublisherIdentifier> or <PublisherName> or both.

<ONIXSRNIssueNotice> <ReleaseNotice> <SerialVersion> <SerialWork> <Publisher>
<PublishingRole>

Mandatory and non-repeatable within <Publisher> .

The role of the publisher. If a Serial Work has co-publishers, then there will be multiple occurrences of <Publisher>, each with a Publishing Role of “02” (co-publisher). If a Serial Work has multiple publishers with different roles; e.g., published by one organization on behalf of another, then there will be multiple occurrences of <Publisher> with different Publishing Roles.

Permissible code values (code list 45C):

01     Publisher

02     Co-publisher

06     Published for/on behalf of

07     Published in association with – Use also for “Published in cooperation with”

<ONIXSRNIssueNotice> <ReleaseNotice> <SerialVersion> <SerialWork> <Publisher>
<PublisherIdentifier>

Optional and repeatable within <Publisher> .

Identification of a publisher using a value from a standard or proprietary identification scheme. Repeatable if multiple identifiers are sent.

<ONIXSRNIssueNotice> <ReleaseNotice> <SerialVersion> <SerialWork> <Publisher> <PublisherIdentifier>
<PublisherIDType>

Mandatory and non-repeatable within <PublisherIdentifier> .

A code indicating the scheme or standard from which the publisher identifier is taken. If <PublisherIDType> is “01” (proprietary), then the name of the scheme should appear in <IDTypeName>.

Permissible code values (code list 44D):

01     Proprietary

06     EAN-UCC GLN – Global location number (formerly EAN location number)

07     SAN – Book trade Standard Address Number - US, UK etc

<ONIXSRNIssueNotice> <ReleaseNotice> <SerialVersion> <SerialWork> <Publisher> <PublisherIdentifier>
<IDTypeName>

Optional and non-repeatable within <PublisherIdentifier> .

The name of the identification scheme from which the <IDValue> is taken, used only when <PublisherIDType> is “01” (proprietary).

<ONIXSRNIssueNotice> <ReleaseNotice> <SerialVersion> <SerialWork> <Publisher> <PublisherIdentifier>
<IDValue>

Mandatory and non-repeatable within <PublisherIdentifier> .

An identifier of the type specified in <PublisherIDType>.

<ONIXSRNIssueNotice> <ReleaseNotice> <SerialVersion> <SerialWork> <Publisher>
<PublisherName>

Optional and repeatable within <Publisher> .

Has optional "language" attribute.

The text name of the publisher of the work. Repeatable if expressed in multiple languages.

<ONIXSRNIssueNotice> <ReleaseNotice> <SerialVersion> <SerialWork>
<Website>

Optional and repeatable within <SerialWork> .

Details of a website for the serial work as a whole; that is, the serial’s “home page.” Repeatable if there is more than one website related to the serial work, other than mirror sites.

Example: This is the journal home page for the American Journal of Clinical Nutrition, which has a mirror site for access outside North America.

<Website>

            <WebsiteRole>04</WebsiteRole>     04 = “Journal home page”

            <WebsiteLink>http://www.ajcn.org/</WebsiteLink>

            <MirrorSite>

                        <WebsiteDescription>For faster access from Australia, Brazil, China, France, Germany, Hong Kong, Ireland, Israel, Italy, Japan, Mexico, Russia, Singapore, South Africa, South Korea, Spain, Sweden, Switzerland, Taiwan, The Netherlands, UK<WebsiteDescription>

                        <WebsiteLink>http://intl.ajcn.org/</WebsiteLink>

            </MirrorSite>

</Website>

<ONIXSRNIssueNotice> <ReleaseNotice> <SerialVersion> <SerialWork> <Website>
<WebsiteRole>

Mandatory and non-repeatable within <Website> .

The role of a website.  In this context, always “04” (journal home page).

Permissible code values (code list 73C):

04     Journal home page – A webpage giving general information about a serial, in print or electronic format or both.

<ONIXSRNIssueNotice> <ReleaseNotice> <SerialVersion> <SerialWork> <Website>
<WebsiteDescription>

Optional and repeatable within <Website> .

Has optional "language" attribute.

A free-text description of the nature or function of a website. Repeatable if expressed in multiple languages.

<ONIXSRNIssueNotice> <ReleaseNotice> <SerialVersion> <SerialWork> <Website>
<MirrorSite>

Optional and repeatable within <Website> .

Details of a site that mirrors a <Website>.

<ONIXSRNIssueNotice> <ReleaseNotice> <SerialVersion> <SerialWork> <Website> <MirrorSite>
<WebsiteDescription>

Optional and repeatable within <MirrorSite> .

Has optional "language" attribute.

A free-text description of the nature or function of a website. Repeatable if expressed in multiple languages.

<ONIXSRNIssueNotice> <ReleaseNotice> <SerialVersion>
<SerialVersionForm>

Mandatory and non-repeatable within <SerialVersion> .

A code indicating the medium in which the <SerialVersion> is delivered.

Permissible code values (code list 7A):

JB     Printed serial

JC     Serial distributed electronically by carrier

JD     Electronic serial distributed online

MA     Microform – Microform – detail unspecified

MB     Microfiche

MC     Microfilm – Roll microfilm

<ONIXSRNIssueNotice> <ReleaseNotice>
<Monograph>

Optional and non-repeatable within <ReleaseNotice> .

Identification and description of a monographic item, when the release type specifies that the release is part of a series of supplements to a monograph.

<Monograph> must include either <ProductIdentifier> or <Title> or both.

Example: The Piano Book is a monograph that is supplemented with an e-book each year.  To announce the release of such a supplement, the <Monograph> composite is used instead of <SerialVersion>.

<Monograph>

            <ProductIdentifier>

                        <ProductIDType>02</ProductIDType>     02 = ISBN-10

                        <IDValue>0961751258</IDValue>

            <Title>

                        <TitleText>The Piano Book</TitleText>

                        <Subtitle>Buying & Owning a New or Used Piano</Subtitle>

            </Title>

            <Publisher>

                        <PublishingRole>01</PublishingRole>     01 = publisher

                        <PublisherName>Brookside Press</PublisherName>

</Monograph>

<ONIXSRNIssueNotice> <ReleaseNotice> <Monograph>
<ProductIdentifier>

Optional and repeatable within <Monograph> .

A coded identifier of the monograph. Repeatable if multiple identifiers are sent.

<ONIXSRNIssueNotice> <ReleaseNotice> <Monograph> <ProductIdentifier>
<ProductIDType>

Mandatory and non-repeatable within <ProductIdentifier> .

A code indicating the scheme or standard from which the product identifier is taken.  If <ProductIDType> is 01 (proprietary), then the name of the scheme should appear in <IDTypeName>.

Permissible code values (code list 5A):

01     Proprietary – For example, a publisher’s or wholesaler’s product number.

02     ISBN-10 – International Standard Book Number, pre-2007, unhyphenated (10 characters)

03     EAN.UCC-13 – EAN-UCC article number (13 digits)

06     DOI – Digital Object Identifier (variable length and character set)

15     ISBN-13 – International Standard Book Number, from 2007, unhyphenated (13 characters)

<ONIXSRNIssueNotice> <ReleaseNotice> <Monograph> <ProductIdentifier>
<IDTypeName>

Optional and non-repeatable within <ProductIdentifier> .

The name of the identification scheme from which the <IDValue> is taken, used only when <ProductIDType> is “01” (proprietary). 

<ONIXSRNIssueNotice> <ReleaseNotice> <Monograph> <ProductIdentifier>
<IDValue>

Mandatory and non-repeatable within <ProductIdentifier> .

An identifier of the type specified in <ProductIDType>

<ONIXSRNIssueNotice> <ReleaseNotice> <Monograph>
<Title>

Optional and repeatable within <Monograph> .

The title of the monograph. Repeatable if different title types are sent.

<ONIXSRNIssueNotice> <ReleaseNotice> <Monograph> <Title>
<TitleType>

Optional and non-repeatable within <Title> .

An ONIX code showing the type of title.  If omitted, the title type defaults to “00” (undefined).

Permissible code values (code list 15A):

00     Undefined

01     The full text of the distinctive title of the monograph, without abbreviation or abridgement. For books, where the title alone is not distinctive, elements may be taken from a set or series title and part number etc to create a distinctive title. Where the item is an omnibus edition containing two or more works by the same author, and there is no separate combined title, a distinctive title may be constructed by concatenating the individual titles, with suitable punctuation, as in Pride and prejudice / Sense and sensibility / Northanger Abbey.

09     Sender's catalog title

<ONIXSRNIssueNotice> <ReleaseNotice> <Monograph> <Title>
<TitleText>

Mandatory and repeatable within <Title> .

Has optional "language" attribute.

The text of the title, excluding subtitle.  Repeatable if expressed in multiple languages.

<ONIXSRNIssueNotice> <ReleaseNotice> <Monograph> <Title>
<Subtitle>

Optional and repeatable within <Title> .

Has optional "language" attribute.

The text of the subtitle, if there is one. Repeatable if expressed in multiple languages.

<ONIXSRNIssueNotice> <ReleaseNotice> <Monograph>
<Imprint>

Optional and non-repeatable within <Monograph> .

The imprint under which the monograph is published.

May only appear if <Publisher> also appears within <Monograph>

Must contain either <ImprintIdentifier> or <ImprintName> or both.

<ONIXSRNIssueNotice> <ReleaseNotice> <Monograph> <Imprint>
<ImprintIdentifier>

Optional and repeatable within <Imprint> .

Identification of an imprint using a value from a standard or proprietary identification scheme.

Repeatable if multiple identifiers are sent.

<ONIXSRNIssueNotice> <ReleaseNotice> <Monograph> <Imprint> <ImprintIdentifier>
<ImprintIDType>

Mandatory and non-repeatable within <ImprintIdentifier> .

A code indicating the scheme or standard from which the imprint identifier is taken.  If <ImprintIDType> is “01” (proprietary), then the name of the scheme should appear in <IDTypeName>.

Permissible code values (code list 44C):

01     Proprietary

<ONIXSRNIssueNotice> <ReleaseNotice> <Monograph> <Imprint> <ImprintIdentifier>
<IDTypeName>

Optional and non-repeatable within <ImprintIdentifier> .

The name of the identification scheme from which the <IDValue> is taken, used only when <ImprintIDType> is “01” (proprietary).

<ONIXSRNIssueNotice> <ReleaseNotice> <Monograph> <Imprint> <ImprintIdentifier>
<IDValue>

Mandatory and non-repeatable within <ImprintIdentifier> .

An identifier of the type specified in <ImprintIDType>.

<ONIXSRNIssueNotice> <ReleaseNotice> <Monograph> <Imprint>
<ImprintName>

Optional and repeatable within <Imprint> .

Has optional "language" attribute.

The text name of the imprint. Repeatable if expressed in multiple languages.

<ONIXSRNIssueNotice> <ReleaseNotice> <Monograph>
<Publisher>

Optional and repeatable within <Monograph> .

Publisher of the intellectual content of the work; repeatable if there are co-publishers or if there are publishers with different Publisher Roles.

Must contain either <PublisherIdentifier> or <PublisherName> or both.

<ONIXSRNIssueNotice> <ReleaseNotice> <Monograph> <Publisher>
<PublishingRole>

Mandatory and non-repeatable within <Publisher> .

The role of the publisher. If a Monograph has co-publishers, then there will be multiple occurrences of <Publisher>, each with a Publishing Role of “02” (co-publisher). If a Monograph has multiple publishers with different roles; e.g., published by one organization on behalf of another, then there will be multiple occurrences of <Publisher> with different Publishing Roles.

Permissible code values (code list 45C):

01     Publisher

02     Co-publisher

06     Published for/on behalf of

07     Published in association with – Use also for “Published in cooperation with”

<ONIXSRNIssueNotice> <ReleaseNotice> <Monograph> <Publisher>
<PublisherIdentifier>

Optional and repeatable within <Publisher> .

Identification of a publisher using a value from a standard or proprietary identification scheme. Repeatable if multiple identifiers are sent.

<ONIXSRNIssueNotice> <ReleaseNotice> <Monograph> <Publisher> <PublisherIdentifier>
<PublisherIDType>

Mandatory and non-repeatable within <PublisherIdentifier> .

A code indicating the scheme or standard from which the publisher identifier is taken. If <PublisherIDType> is “01” (proprietary), then the name of the scheme should appear in <IDTypeName>.

Permissible code values (code list 44D):

01     Proprietary

06     EAN-UCC GLN – Global location number (formerly EAN location number)

07     SAN – Book trade Standard Address Number - US, UK etc

<ONIXSRNIssueNotice> <ReleaseNotice> <Monograph> <Publisher> <PublisherIdentifier>
<IDTypeName>

Optional and non-repeatable within <PublisherIdentifier> .

The name of the identification scheme from which the <IDValue> is taken, used only when <PublisherIDType> is “01” (proprietary).

<ONIXSRNIssueNotice> <ReleaseNotice> <Monograph> <Publisher> <PublisherIdentifier>
<IDValue>

Mandatory and non-repeatable within <PublisherIdentifier> .

An identifier of the type specified in <PublisherIDType>.

<ONIXSRNIssueNotice> <ReleaseNotice> <Monograph> <Publisher>
<PublisherName>

Optional and repeatable within <Publisher> .

Has optional "language" attribute.

The text name of the publisher of the work. Repeatable if expressed in multiple languages.

<ONIXSRNIssueNotice> <ReleaseNotice>
<Release>

Mandatory and repeatable within <ReleaseNotice> .

Enumeration, chronology, and other details of a release. Repeatable for multiple releases belonging to the same serial version or to the same series of supplements to a monograph.

A <Release> must contain

<Enumeration> with or without <NominalDate>, or

<SupplementEnumeration> with or without <NominalDate>, or

<IncludedRelease> with or without <NominalDate>, or

<NominalDate> on its own.

A <Release> may not contain both <Enumeration> and <SupplementEnumeration>

<IncludedRelease> may coexist with either <Enumeration> or <SupplementEnumeration>

In addition, <NotificationType>, <ReleaseType>, <SRNContentItem> and either <ExpectedReleaseDate> or <ReleaseDate> (but not both) are mandatory within <Release>.

Example 1: The first example announces the release of a print issue of a journal.  (Examples of <Enumeration> and <NominalDate> may be found later in this document.)

<Release>

            <NotificationType>10</NotificationType>     10 = confirmed release

            <ReleaseType>01</ReleaseType>     01 = Release of a serial issue in normal enumeration sequence

            <Enumeration>

                        Enumeration of the release appears here

            </Enumeration>

            <NominalDate>

                        “Cover date” of the release appears here

            </NominalDate>

            <ReleaseDate>     Confirmed date on which the release was or is about to be released

                        <DateFormat>00</DateFormat>     00 = year, month, day

                        <Date>20070501</Date>

            </ReleaseDate>

</Release>

Example 2: This example illustrates a notification of the release of an online issue of a journal which is part of a hosted collection.  (Examples of <Enumeration>, <NominalDate> and <Website> may be found later in this document.)

<Release>

            <NotificationType>10</NotificationType>     10 = confirmed release

            <ReleaseType>01</ReleaseType>     01 = serial issue in normal enumeration sequence

            <Enumeration>

                        Enumeration of the release appears here

            </Enumeration>

            <NominalDate>

                        “Cover date” of the release appears here

            </NominalDate>

            <ReleaseDate>

                        <Date>20050901</Date>     default date format = YYYYMMDD

            </ReleaseDate>

            <HostedCollection>

                        <HostedCollectionName>Basic Research Collection</HostedCollectionName>

                        <OnlinePublisher>     The vendor of an online hosted collection

                                    <PublishingRole>05</PublishingRole>   05 = host/distributor of electronic content

                                    <PublisherName>Project Muse</PublisherName>

                        </OnlinePublisher>

            </HostedCollection>

            <ContentHostingSystem>Project Muse</ContentHostingSystem>

            <Website>

                        Website for the issue appears here

            </Website>

</Release>

<ONIXSRNIssueNotice> <ReleaseNotice> <Release>
<NotificationType>

Mandatory and non-repeatable within <Release> .

A code indicating what kind of notification is being sent in this <Release>: either that a release has occurred or is about to occur, with a confirmed release date, or that a release will take place on an expected but unconfirmed future date.

Permissible code values (code list 1B):

10     Notice of serial release – Notice of serial release with a confirmed release date

11     Advance notice of serial release – Advance notice of serial release with a provisional release date

<ONIXSRNIssueNotice> <ReleaseNotice> <Release>
<ReleaseType>

Mandatory and non-repeatable within <Release> .

A code specifying the type of a release.

Permissible code values (code list 115A):

01     Normal release – Serial release in normal enumeration sequence (other than type 02)

02     Replacement release – Serial release in normal enumeration sequence that replaces some or all earlier releases

03     Extra release – Serial release extra to, or temporarily extending, normal enumeration sequence (including when an expected release is split into two parts)

04     Periodic supplement to a serial – Release of a part of a series of periodic supplements to a serial

05     Periodic supplement to a monograph – Release of a part of a series of periodic supplements to a monograph

06     Occasional supplement to a serial – Release of an occasional supplement to a serial (ie not a part of a series of periodic supplements)

07     Index – Release of an index issued as a separate part

<ONIXSRNIssueNotice> <ReleaseNotice> <Release>
<CombinedRelease/>

Optional and non-repeatable within <Release> .

An “empty element” signifying that this release is a combined release, combining two or more expected releases in normal enumeration sequence. When <CombinedRelease/> is present, then two or more occurrences of <IncludedRelease> will also be present.

<ONIXSRNIssueNotice> <ReleaseNotice> <Release>
<ReleaseForm>

Optional and non-repeatable within <Release> .

A code indicating the form of the release, when the release is part of a series of supplements to a monograph.  If the release belongs to a Serial Version, then the form will already have been indicated in <SerialVersion> <SerialVersionForm>; however, <ReleaseForm> may be used to override <SerialVersionForm> if a release has a different form from its parent serial.

For example, if a print journal publishes one issue as a CD-ROM, the <SerialVersionForm> would be JB, but the <ReleaseForm> for the CD-ROM issue would carry the <ReleaseForm> of JC.

Permissible code values (code list 7S):

DG     Electronic book text – Electronic book text in proprietary or open standard format

JB     Printed serial

JC     Serial distributed electronically by carrier

JD     Electronic serial distributed online

MA     Microform – Microform – detail unspecified

MB     Microfiche

MC     Microfilm – Roll microfilm

<ONIXSRNIssueNotice> <ReleaseNotice> <Release>
<ReleaseIdentifier>

Optional and repeatable within <Release> .

Identification of a release using a value from a standard or proprietary identification scheme. Repeatable if there is a need to send two or more identifiers of different types; for example, a SICI and an ISBN for a serial release that is also traded as a monograph.

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <ReleaseIdentifier>
<ReleaseIDType>

Mandatory and non-repeatable within <ReleaseIdentifier> .

A code identifying the scheme from which a release identifier is taken.

Permissible code values (code list 5S):

01     Proprietary – For example, a publisher’s or wholesaler’s product number.

02     ISBN-10 – International Standard Book Number, pre-2007, unhyphenated (10 characters)

03     EAN.UCC-13 – EAN-UCC article number (13 digits)

06     DOI – Digital Object Identifier (variable length and character set)

10     SICI – Serial Item and Contribution Identifier

15     ISBN-13 – International Standard Book Number, from 2007, unhyphenated (13 digits)

18     ISRC – International Standard Recording Code

19     ISAN – International Standard Audiovisual Number

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <ReleaseIdentifier>
<IDTypeName>

Optional and non-repeatable within <ReleaseIdentifier> .

A name for a proprietary scheme, used only when <ReleaseIDType> is “proprietary.”

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <ReleaseIdentifier>
<IDValue>

Mandatory and non-repeatable within <ReleaseIdentifier> .

The identifier value, from the specified scheme.

<ONIXSRNIssueNotice> <ReleaseNotice> <Release>
<SequenceNumber>

Optional and non-repeatable within <Release> .

A consecutive number applied across all successive releases of a serial version.

<ONIXSRNIssueNotice> <ReleaseNotice> <Release>
<Enumeration>

Optional and non-repeatable within <Release> .

The enumeration of a release that is neither a supplement nor an index; that is, <ReleaseType> = 01, 02, or 03. If the release is a supplement or an index, then the <SupplementEnumeration> composite will be used instead. <Enumeration> must contain <Level1>. 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: 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 “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>

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <Enumeration>
<Level1>

Mandatory and non-repeatable within <Enumeration> .

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>

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <Enumeration> <Level1>
<Unit>

Optional and repeatable within <Leveln> .

Has optional "language" attribute.

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>.

Repeatable if multiple languages are used on the piece.

If <Unit> is present, <Number> must also be present.

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <Enumeration> <Level1>
<ImpliedUnit>

Optional and repeatable within <Leveln> .

Has optional "language" attribute.

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.

Repeatable if multiple languages are used on the piece.

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <Enumeration> <Level1>
<UnitAbbr>

Optional and non-repeatable within <Leveln> .

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.

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <Enumeration> <Level1> <UnitAbbr>
<UnitAbbrType>

Optional and non-repeatable within <UnitAbbr> .

A code specifying the source of the abbreviation.

Permissible code values (code list 116S):

00     Unspecified

01     Proprietary

02     AACR2 (1998)

03     ISO 832:1984 – ISO rules for the abbreviation of bibliographic terms

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <Enumeration> <Level1> <UnitAbbr>
<AbbrTypeName>

Optional and non-repeatable within <UnitAbbr> .

The name of the source of the abbreviation, used only when <AbbrType> = 01 (“proprietary”).

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <Enumeration> <Level1> <UnitAbbr>
<Abbreviation>

Mandatory and repeatable within <UnitAbbr> .

Has optional "language" attribute.

The abbreviation itself. Repeatable if multiple languages are used on the piece.

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <Enumeration> <Level1>
<Number>

Optional and non-repeatable within <Leveln> .

Has optional "nformat", "nscript", "ntype", and "textscript" attributes.

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.

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <Enumeration> <Level1>
<NamedUnit>

Optional and repeatable within <Leveln> .

Has optional "language" attribute.

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.

Repeatable if multiple languages are used on the piece.

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <Enumeration>
<EnumerationNote>

Optional and repeatable within <Enumeration> .

Has optional "language" attribute.

A free text note clarifying the enumeration. Repeatable if expressed in multiple languages.

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <Enumeration>
<AdditionalEnumeration>

Optional and repeatable within <Enumeration> .

Additional or alternative enumeration applied to the 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>, except that it does not include <AdditionalEnumeration>.

<ONIXSRNIssueNotice> <ReleaseNotice> <Release>
<NominalDate>

Optional and repeatable within <Release> .

The “cover” date of a release: repeatable if the date is given using more than one calendar, eg Hebrew and Gregorian.  Note that this is not the same as the Release Date, which is the date on which the release was made available or is to be made available.

Example:

<NominalDate>

            <Calendar>00</Calendar>     00 = “Gregorian”

            <DateFormat>00</DateFormat>     00 = “YYYYMMDD”

            <Date>20060402</Date>

</NominalDate>

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <NominalDate>
<Calendar>

Optional and non-repeatable within <NominalDate> .

A code indicating the calendar in which the date is given. If omitted, the default is "00” (Gregorian).

Permissible code values (code list 110S):

00     Gregorian (default) – Gregorian or Common Era

01     Hebrew

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <NominalDate>
<DateFormat>

Mandatory and non-repeatable within <NominalDate> .

A code indicating the format in which the date is given. Code values 06-11 are used in the case where the cover date of an issue is a range of dates.

Permissible code values (code list 55S):

00     YYYYMMDD – Year month day (default)

01     YYYYMM – Year and month

02     YYYYWW – Year and week number

03     YYYYQ – Year and quarter (Q = 1, 2, 3, 4)

04     YYYYS – Year and season (S = 1, 2, 3, 4, with 1 = “Spring”)

05     YYYY – Year

06     YYYYMMDDYYYYMMDD – Spread of exact dates

07     YYYYMMYYYYMM – Spread of months

08     YYYYWWYYYYWW – Spread of week numbers

09     YYYYQYYYYQ – Spread of quarters

10     YYYYSYYYYS – Spread of seasons

11     YYYYYYYY – Spread of years

12     Text string – For complex, approximate or uncertain dates

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <NominalDate>
<Date>

Mandatory and non-repeatable within <NominalDate> .

A date, or spread of dates, in the specified calendar and format.

<ONIXSRNIssueNotice> <ReleaseNotice> <Release>
<SupplementEnumeration>

Optional and non-repeatable within <Release> .

Enumeration of a supplement or index release; that is, <ReleaseType> = 04, 05, 06, or 07. If the release is not a supplement or an index, then the <Enumeration> composite is used instead.

If a release is part of a series of periodic supplements to a serial or monograph, the <SeriesIdentifier> and/or <SeriesTitle> are included as applicable.

If the supplement enumeration is dependent on the enumeration or chronology of a part of the main run of the serial version, <DependentEnumeration> is used with one or more of <MainRunEnumeration> or <MainRunNominalDate> or <MainRunReleaseTitle>. The use of <MainRunEnumeration> is preferred if available, but <MainRunNominalDate> or <MainRunReleaseTitle> or both may also be included in addition to <MainRunEnumeration> to help define a main run release. <MainRunEnumeration> would not appear in the case of a supplement to a release that carries no enumeration.

If the supplement enumeration is associated with a part of the main run of the serial, but not dependent on it, <IndependentEnumeration> is used along with one or more of <MainRunEnumeration>, <MainRunNominalDate> and <MainRunReleaseTitle>.

If the supplement enumeration is completely independent of the main run enumeration, only <IndependentEnumeration> is used.

If an index is delivered as part of a normal issue of a serial, it is not treated specially in the SRN message. If an index is delivered separately from the normal issues, it is treated as a supplement, and a <SupplementEnumeration> composite is defined, including the optional <IndexedSequence> and <IndexedPeriod> composites to describe the enumeration and date range, respectively, of the main run that are indexed by the release.

Example 1: A supplement whose enumeration is dependent on a main run volume. Piece is marked: Vol 32, Supplement A. July 3, 2005. (Supplement numbering begins anew with each volume of the journal)

<SupplementEnumeration>

            <MainRunEnumeration>

                        <Level1>

                                    <Unit>Volume</Unit>

                                    <Number>32</Number>

                        </Level1>

            </MainRunEnumeration>

            <DependentEnumeration>

                        <Level1>

                                    <Unit>Supplement</Unit>

                                    <Number nformat=”b”>A</Number>     nformat b = letters

                        </Level1>

            </DependentEnumeration>

            <NominalDate>     Cover date of the supplement

                        <DateFormat>00</DateFormat>     00 = YYYYMMDD

                        <Date>20050703</Date>

            <NominalDate>

</SupplementEnumeration>

Example 2: A supplement whose enumeration is entirely independent of the main run enumeration. Piece is marked as follows: Supplement 1462. July 3, 2005. (All supplements are numbered sequentially with no reference to the main run)

<SupplementEnumeration>

            <IndependentEnumeration>

                        <Level1>

                                    <Unit>Supplement</Unit>

                                    <Number>1462</Number>

                        </Level1>

            </IndependentEnumeration>

            <NominalDate>     Cover date of the supplement

                        <DateFormat>00</DateFormat>     00 = YYYYMMDD

                        <Date>20050703</Date>

            <NominalDate>

</SupplementEnumeration>

Example 3: A supplement whose enumeration is independent of the main run enumeration, but which is nevertheless associated with a main run volume. Piece is marked as follows: Volume 32, Supplement 1462. July 3, 2005. (All supplements are numbered sequentially but they are issued as part of a specific volume)

<SupplementEnumeration>

            <MainRunEnumeration>

                        <Level1>

                                    <Unit>Volume</Unit>

                                    <Number>32</Number>

                        </Level1>

            </MainRunEnumeration>

            <IndependentEnumeration>

                        <Level1>

                                    <Unit>Supplement</Unit>

                                    <Number>1462</Number>

                        </Level1>

            </IndependentEnumeration>

            <NominalDate>     Cover date of the supplement

                        <DateFormat>00</DateFormat>     00 = YYYYMMDD

                        <Date>20050703</Date>

            <NominalDate>

</SupplementEnumeration>

Example 4: A supplement that is part of a supplement series that has its own enumeration. This is the enumeration for Volume 108 Number 1 (January 1997) of The Astrophysical Journal Supplement Series (ISSN 1538-4365)The enumeration of the supplement is independent of the enumeration of the main journal.

<SupplementEnumeration>

            <SeriesIdentifier>

                        <SeriesIDType>07</SeriesIDType>     07 = ISSN of the supplement series

                        <IDValue>15384365</IDValue>

            </SeriesIdentifier>

            <SeriesTitle>

                        <TitleText>The Astrophysical Journal Supplement Series</TitleText>

            </SeriesTitle>

            <IndependentEnumeration>

                        <Level1>

                                    <Unit>Volume</Unit>

                                    <Number>108</Number>

                        </Level1>

                        <Level2>

                                    <Unit>Number</Unit>

                                    <Number>1</Number>

                        </Level2>

            </IndependentEnumeration>

            <NominalDate> Cover date of the supplement

                        <DateFormat>01</DateFormat>     01 = YYYYMM

                        <Date>199701</Date>

            <NominalDate>

</SupplementEnumeration>

Example 5: A supplement that is an indexThis example announces the release of an index titled “Subject index” which covers v.33, no. 1-25 (2005 Jan-June) of the main journal (the main journal is described in the <SerialVersion> portion of the <ReleaseNotice>).  The index has no enumeration of its own.

<Release>

            <NotificationType>10</NotificationType>     10 = confirmed

            <ReleaseType>08</ReleaseType>     08 = index issued as a separate part

            <SupplementEnumeration>

                        <IndexedSequence>     Range of issues indexed

                                    <StartEnumeration>

                                                <Level1>

                                                            <Unit>Volume</Unit>

                                                            <Number >33</Number>

                                                </Level1>

                                                <Level2>

                                                            <Unit>Number</Unit>

                                                            <Number>1</Number>

                                                </Level2>

                                    </StartEnumeration>

                                    <EndEnumeration>

                                                <Level1>

                                                            <Unit>Volume</Unit>

                                                            <Number >33</Number>

                                                </Level1>

                                                <Level2>

                                                            <Unit>Number</Unit>

                                                            <Number>25</Number>

                                                </Level2>

                                    </EndEnumeration>

                        </IndexedSequence>

                        <IndexedPeriod>

                                    <DateFormat>07</DateFormat>     07 = spread of months, YYYYMMYYYYMM

                                    <Date>200501200506</Date>

                        </IndexedPeriod>

            </SupplementEnumeration>

            <ReleaseTitle>

                        <TitleText>Subject Index</TitleText>

            </ReleaseTitle>

            <ReleaseDate>

                        <DateFormat>00</DateFormat>     00 = year, month, day

                        <Date>20050727</Date>     Actual date of release

            </ReleaseDate>

</Release>

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <SupplementEnumeration>
<SeriesIdentifier>

Optional and repeatable within <SupplementEnumeration> .

A coded dentifier of a supplement or index series. Used only if the supplement or index is part of a series that carries an identifying number, usually an ISSN. Repeatable if more than one identifier is sent.

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <SupplementEnumeration> <SeriesIdentifier>
<SeriesIDType>

Mandatory and non-repeatable within <SeriesIdentifier> .

A code identifying the scheme from which a series identifier is taken.

Permissible code values (code list 13S):

01     Proprietary – For example, publisher’s own series ID

02     ISSN – International Standard Serial Number, unhyphenated, 8 characters

06     DOI – Digital Object Identifier (variable length and character set)

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <SupplementEnumeration> <SeriesIdentifier>
<IDTypeName>

Optional and non-repeatable within <SeriesIdentifier> .

The name of the identification scheme from which the <IDValue> is taken, used only when <SeriesIDType> is “01” (proprietary).

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <SupplementEnumeration> <SeriesIdentifier>
<IDValue>

Mandatory and non-repeatable within <SeriesIdentifier> .

An identifier of the type specified in <SeriesIDType>.

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <SupplementEnumeration>
<SeriesTitle>

Optional and repeatable within <SupplementEnumeration> .

The title of a supplement series. Repeatable if more than one form of the title is sent.

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <SupplementEnumeration> <SeriesTitle>
<TitleType>

Optional and non-repeatable within <SeriesTitle> .

A code showing the type of title. If omitted, the title type defaults to “00” (undefined).

Permissible code values (code list 15A):

00     Undefined

01     Cover title – The full text of the title as it appears on the work, without abbreviation or abridgement.

09     Sender's catalog title

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <SupplementEnumeration> <SeriesTitle>
<TitleText>

Mandatory and repeatable within <SeriesTitle> .

Has optional "language" attribute.

The text of the title, excluding subtitle.  Repeatable if expressed in multiple languages.

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <SupplementEnumeration> <SeriesTitle>
<Subtitle>

Optional and repeatable within <SeriesTitle> .

Has optional "language" attribute.

The text of the subtitle, if there is one. Repeatable if expressed in multiple languages.

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <SupplementEnumeration>
<MainRunEnumeration>

Optional and non-repeatable within <SupplementEnumeration> .

Enumeration of a main run volume, issue or part. Used when the supplement or index is explicitly associated with a part of the main run of the serial version. This will happen either when the supplement enumeration is dependent on the enumeration of a part of the main run of the serial version or when the supplement enumeration is associated with a part of the main run of the serial, but not dependent on it.

The expansion of <MainRunEnumeration> is identical to that of <Enumeration>, except that <AdditionalEnumeration> is named <AdditionalMainRunEnumeration>

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <SupplementEnumeration>
<MainRunNominalDate>

Optional and non-repeatable within <SupplementEnumeration> .

“Cover date” of a main run volume, issue or part. May be included if necessary to identify a main run volume, issue or part.

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <SupplementEnumeration>
<MainRunReleaseTitle>

Optional and repeatable within <SupplementEnumeration> .

Title of the main run release; optional, for Main Run releases with a specific title. May be used when announcing a supplement or index to a single Main Run release.

The expansion of the <MainRunReleaseTitle> composite is identical to that of <ReleaseTitle>.

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <SupplementEnumeration>
<DependentEnumeration>

Optional and non-repeatable within <SupplementEnumeration> .

Enumeration of a supplement or index, used when the enumeration of the main run is required to definitively identify it, eg, if supplement enumeration begins anew with each new volume of the main run. Must be preceded by one or more of <MainRunEnumeration>, <MainRunNominalDate> or <MainRunReleaseTitle>.

The expansion of <DependentEnumeration> is identical to that of <Enumeration>, except that <AdditionalEnumeration> is named <AdditionalDependentEnumeration>.

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <SupplementEnumeration>
<IndependentEnumeration>

Optional and non-repeatable within <SupplementEnumeration> .

Enumeration of a supplement or index, when it carries enumeration of its own, not requiring MainRunEnumeration for unique identification. If the supplement or index is also identified as being issued in association with a particular main run volume or issue, then one or more of <MainRunEnumeration>, <MainRunNominalDate> or <MainRunReleaseTitle> should precede <IndependentEnumeration>, to identify that volume or issue.

The expansion of <IndependentEnumeration> is identical to that of <Enumeration>, except that <AdditionalEnumeration> is named <AdditionalIndependentEnumeration>.

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <SupplementEnumeration>
<IndexedSequence>

Optional and non-repeatable within <SupplementEnumeration> .

The range of volumes/issues covered by an index. Used only when <ReleaseType> = 07 (Index).

<IndexedSequence> contains two enumeration composites, one for the start and one for the end of the volumes/issues covered by an index. <StartEnumeration> is mandatory, but <EndEnumeration> may be omitted if the index covers a single level of enumeration, eg, “Index to Volume 4.” The expansion of each is identical to that of <Enumeration>.

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <SupplementEnumeration>
<IndexedPeriod>

Optional and non-repeatable within <SupplementEnumeration> .

Range of dates covered by an index. Used only when <ReleaseType> = 07 (Index).

The expansion of <IndexedPeriod> is identical to that of <NominalDate> found earlier in this document.

<ONIXSRNIssueNotice> <ReleaseNotice> <Release>
<ReleaseTitle>

Optional and repeatable within <Release> .

A distinctive title given to an individual release, used for example when a journal issue has a thematic title. Repeatable if different title types are sent.

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <ReleaseTitle>
<TitleType>

Optional and non-repeatable within <ReleaseTitle> .

An ONIX code showing the type of title.  If omitted, the title type defaults to “00” (undefined).

Permissible code values (code list 15A):

00     Undefined

01     Distinctive title – The full text of the distinctive title of the release, without abbreviation or abridgement.

09     Sender's catalog title

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <ReleaseTitle>
<TitleText>

Mandatory and repeatable within <ReleaseTitle> .

Has optional "language" attribute.

The text of the title, excluding subtitle.  Repeatable if expressed in multiple languages.

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <ReleaseTitle>
<Subtitle>

Optional and repeatable within <ReleaseTitle> .

Has optional "language" attribute.

The text of the subtitle, if there is one. Repeatable if expressed in multiple languages.

<ONIXSRNIssueNotice> <ReleaseNotice> <Release>
<IncludedRelease>

Optional, but if included, must be repeated 2 or more times within <Release> .

The enumeration, chronology and/or title of a component of a combined release. If present, there will be two or more occurrences. If present, then <CombinedRelease/> must also be present.

Must contain one or more of <Enumeration>, <SupplementEnumeration>, or <NominalDate>. These composites are expanded as shown earlier in this document.

<Enumeration> and <SupplementEnumeration> may not both be present.

<ONIXSRNIssueNotice> <ReleaseNotice> <Release>
<ExpectedReleaseDate>

Optional and non-repeatable within <Release> .

The date on which a future release is expected to be issued, mandatory in a provisional release notice (<NotificationType> = 11).

Either <ExpectedReleaseDate> or <ReleaseDate> must be present within <Release>.

<ExpectedReleaseDate> is always sent using the Gregorian calendar, and using <DateFormat> “00” (YYYYMMDD).

<ONIXSRNIssueNotice> <ReleaseNotice> <Release>
<ReleaseDate>

Optional and non-repeatable within <Release> .

The actual date on which a release is issued, mandatory in a confirmed release notice (<NotificationType> = 10).

Either <ExpectedReleaseDate> or <ReleaseDate> must be present within <Release>.

<ReleaseDate> is always sent using the Gregorian calendar, and using <DateFormat> “00” (YYYYMMDD).

<ONIXSRNIssueNotice> <ReleaseNotice> <Release>
<HostedCollection>

Optional and non-repeatable within <Release> .

The hosted collection of which this release is a part, for an online release that is part of a hosted collection. If a release is part of multiple hosted collections, then the <Release> composite should be repeated.

Must contain either <HostedCollectionIdentifier> or <HostedCollectionName> or both.

If <HostedCollection> is present, then <ContentHostingSystem> must also be present.

Example:

            <HostedCollection>

                        <HostedCollectionName>Basic Research Collection</HostedCollectionName>

                        <OnlinePublisher>        The vendor of an online hosted collection

                                    <PublishingRole>05</PublishingRole>     05 = host/distributor of electronic content

                                    <PublisherName>Project Muse</PublisherName>

                        </OnlinePublisher>

            </HostedCollection>

            <ContentHostingSystem>Project Muse</ContentHostingSystem>

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <HostedCollection>
<HostedCollectionIdentifier>

Optional and repeatable within <HostedCollection> .

Identification of a hosted collection using a value from a standard or proprietary identification scheme. Repeatable if multiple identifiers are sent.

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <HostedCollection> <HostedCollectionIdentifier>
<HostedCollectionIDType>

Mandatory and non-repeatable within <HostedCollectionIdentifier> .

A code indicating the scheme or standard from which the sender identifier is taken. If <HostedCollectionIDType> is 01 (proprietary), then the name of the scheme should appear in <IDTypeName>.

Permissible code values (code list 117S):

01     Proprietary

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <HostedCollection> <HostedCollectionIdentifier>
<IDTypeName>

Optional and non-repeatable within <HostedCollectionIdentifier> .

The name of the identification scheme from which the <IDValue> is taken, used only when <HostedCollectionIDType> is “01” (proprietary).

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <HostedCollection> <HostedCollectionIdentifier>
<IDValue>

Mandatory and non-repeatable within <HostedCollectionIdentifier> .

An identifier of the type specified in <HostedCollectionIDType>.

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <HostedCollection>
<HostedCollectionName>

Mandatory and repeatable within <HostedCollection> .

Has optional "language" attribute.

The text name of the hosted collection. Repeatable if expressed in multiple languages.

<ONIXSRNIssueNotice> <ReleaseNotice> <Release>
<ContentHostingSystem>

Optional and repeatable within <Release> .

Has optional "language" attribute.

The name of the system that hosts the content of an online release. See “content hosting system” in the ONIX Serials Glossary. If <HostedCollection> is present, then <ContentHostingSystem> must also be present. Repeatable if expressed in multiple languages.

Example:

<ContentHostingSystem>JSTOR</ContentHostingSystem>

<ONIXSRNIssueNotice> <ReleaseNotice> <Release>
<OnlinePublisher>

Optional and non-repeatable within <Release> .

The vendor or distributor of an online release. See “online publisher” in the ONIX Serials Glossary.

<OnlinePublisher> must contain either <PublisherIdentifier> or <PublisherName> or both.

Example:

<OnlinePublisher>

            <PublishingRole>05</PublishingRole>     05 = host/distributor of electronic content

            <PublisherName>Project Muse</PublisherName>

</OnlinePublisher>

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <OnlinePublisher>
<PublishingRole>

Mandatory and non-repeatable within <OnlinePublisher> .

The role of the publisher; in this context, always “05” (host/disributor on electronic content).

Permissible code values (code list 45A):

05     Host/distributor of electronic content

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <OnlinePublisher>
<PublisherIdentifier>

Optional and repeatable within <OnlinePublisher> .

Identification of a publisher using a value from a standard or proprietary identification scheme. Repeatable if multiple identifiers are sent.

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <OnlinePublisher> <PublisherIdentifier>
<PublisherIDType>

Mandatory and non-repeatable within <PublisherIdentifier> .

A code indicating the scheme or standard from which the publisher identifier is taken. If <PublisherIDType> is “01” (proprietary), then the name of the scheme should appear in <IDTypeName>.

Permissible code values (code list 44D):

01     Proprietary

06     EAN-UCC GLN – Global location number (formerly EAN location number)

07     SAN – Book trade Standard Address Number - US, UK etc

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <OnlinePublisher> <PublisherIdentifier>
<IDTypeName>

Optional and non-repeatable within <PublisherIdentifier> .

The name of the identification scheme from which the <IDValue> is taken, used only when <PublisherIDType> is “01” (proprietary).

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <OnlinePublisher> <PublisherIdentifier>
<IDValue>

Mandatory and non-repeatable within <PublisherIdentifier> .

An identifier of the type specified in <PublisherIDType>.

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <OnlinePublisher>
<PublisherName>

Optional and repeatable within <OnlinePublisher> .

Has optional "language" attribute.

The name of the online publisher. Repeatable if expressed in multiple languages.

<ONIXSRNIssueNotice> <ReleaseNotice> <Release>
<Website>

Optional and repeatable within <Release> .

For an online release, details of the website(s) where the release may be accessed. Repeatable only if there is more than one website related to the serial release, excluding mirror sites.

Example:

<Website>

            <WebsiteRole>19</WebsiteRole>     19 = website for a serial release

            <WebsiteLink>http://www.journals.uchicago.edu/ApJ/journal/contents/ApJS/v160n2.html </WebsiteLink>

            <MirrorSite>

                        <WebsiteDescription>CDS mirror site</WebsiteDescription>

                        <WebsiteLink>http://cdsaas.u-strasbg.fr:2001/ApJ/journal/contents/ApJS/v160n2.html </WebsiteLink>

            </MirrorSite>   

</Website>      

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <Website>
<WebsiteRole>

Mandatory and non-repeatable within <Website> .

The role of a website.  In this context, always “19” (website for a specified serial release).

Permissible code values (code list 73E):

19     Website for a specified serial release

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <Website>
<WebsiteDescription>

Optional and repeatable within <Website> .

Has optional "language" attribute.

A free-text description of the nature or function of a website. Repeatable if expressed in multiple languages.

<ONIXSRNIssueNotice> <ReleaseNotice> <Release> <Website>
<MirrorSite>

Optional and repeatable within <Website> .

Details of a site that mirrors a <Website>. The expansion of the <MirrorSite> composite is identical to that of <MirrorSite> found earlier in this document.