ONIX Serials Coverage Statement
Version 0.9 User Guide
Date issued: January 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.
Copyright © 2007
EDItEUR Limited. All rights reserved.
The structural diagrams have been produced using
XML Spy™ from Altova
General guidance on schema use
This schema provides a formal specification of what constitutes valid use of XML to construct an ONIX Serials Coverage Statement. 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.
Note that the Coverage Statement is not a message format, but rather a structure that is included in other ONIX for Serials formats. The Coverage Statement may also be used to express holdings or coverage in XML structures other than those specified in ONIX for Serials.
The schema to which this document refers comprises four 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_Coverage_n.n.xsd ||definitions of the message-level element and of complex types
specific to Coverage Statements (the number 'n.n' is the version number of this
|ONIX_Serials_CodeLists.xsd ||definitions of datatypes common to all ONIX Serials
For further information see
XML Schema Part 1: Structures
and XML Schema Part 2:
It is intended that this schema be used to guide implementation of systems for either originating or receiving Coverage statements. Used in conjunction with a suitable “schema parser” it may also be used to validate the structure and contents of an individual message.
ONIX for Serials schemas define how the substance, or “payload”, of ONIX for Serials messages are to be represented in XML, but are silent on the question of how the messages are 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
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
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|
The ONIX for Serials Coverage Statement is an XML structure capable of carrying simple or complex statements of holdings of serial resources, in paper or electronic form, to be included in ONIX for Serials messages for a variety of applications; for example, to express:
- The holdings of a particular serial version by a library
- The coverage of a particular serial version supplied by an online content hosting system
- The coverage of a particular serial version included in a subscription or offering
The coverage composite supports the expression of both enumeration and chronology.
The coverage composite may also be used to express holdings or coverage in XML structures other than those specified in ONIX for Serials.
Please see the ONIX Serials Coverage Overview for a more detailedl introduction to the Coverage Statement and its applications.
Some words or phrases are used throughout ONIX for Serials with a very specific meaning. These are defined in the ONIX for Serials Glossary.
Please refer to the following documents for a more detailed introduction to the Coverage Statement:
- Coverage Overview Version 0.9
- ONIX Serials Glossary