## Introduction

This Product Information Format Specification (the Specification) defines ONIX for Books Release 3.1 revision 2. Release 3.1 was the first new release since 2009, and this revision wholly replaces the original specification for 3.1 and its earlier revisions.

There is an accompanying ONIX for Books Implementation and Best Practice Guide (the Guide, doi:10.4400/zuim) that provides numerous examples of real-world use of the ONIX standard. There is a also separate specification for an Acknowledgement message (doi:10.4400/ewea) which may be sent in response to receipt of an ONIX Product Information message, and which may form part of a message ‘choreography’ between data sender and recipient.

This Specification is subject to further revision, not only to correct any errors that are found in the documentation or during the early stages of implementation, but also to add material that may make it easier to use. Release 3.1 revision 2 itself is also subject to further revision to add new data elements supporting new functionality. The previous release, 3.0 was subject to eight such revisions (revisions 3.0.1 to 3.0.8) over a dozen years. The codelists – which form an important part of the standard – are also regularly updated. Any revisions will be notified through the ONIX for Books implementation forum onix@groups.io. If you are not already a member of this mailing list, you may wish to sign up through the EDItEUR website or by sending a blank e‑mail to onix+subscribe@groups.io.

Numbering of data elements, blocks, sections etc within this Specification remains in alignment with the documentation for Release 3.0 – where a previously-deprecated element has been removed from Release 3.1, subsequent data elements have not been renumbered.

If you believe that you have found an error, or you have a question about this document, please contact EDItEUR either through the implementation forum mailing list or by e‑mail to info@editeur.org.

#### Introduction to Release 3.1

This new release of the ONIX Product Information Format is characterized by two key changes. First, the removal of a handful of elements from release 3.0 that have been deprecated up to a decade, and second, the addition of a range of new data elements, including tags to describe hybrid open access products, tags to prioritize marketing collateral, and a new <MarketReference> tag for enabling per-market block updates of Block 6. The removal of deprecated elements means that release 3.1 is not fully backwards compatible with the previous version, so is labelled Release 3.1 rather than Release 3.0 revision 9.

Removal of deprecated elements should have a relatively limited impact, as only a couple of the elements removed from the Product record have ever seen more than occasional real-world use. Of the two that have seen significant use, <DateFormat> can easily be replaced with the dateformat attribute, and <AudienceCode> can be replaced with use of the <Audience> composite.

The addition of <MarketReference> changes the processing of Block 6 partial updates. Without <MarketReference>, Block 6 must be considered as a non-repeatable block containing one or more repeats of <ProductSupply>, and a change to the metadata in one <ProductSupply> implies that all repeats of <ProductSupply> must be included in a Block 6 update. With the addition of <MarketReference>, Block 6 can be considered as a truly repeatable block, each repeat containing a single <ProductSupply>, and each <ProductSupply> can be block updated individually without having to repeat unchanged <ProductSupply> composites for other markets. This greatly improves the efficiency of many price and availability updates.

This release also includes a number of relatively minor updates such as addition of an Affiliation identifier and explicit ordering of collateral material to improve the usability of ONIX metadata by recipients, and one more significant addition – the inclusion of an extended <EpubLicense>, <EpubUsageConstraint>, <Publisher> and <CopyrightStatement> within <ContentItem> in Block 3. This enables a rich description of hybrid open access monographs, where each chapter of the product may be licensed differently.

The newly-added data elements are marked ‘New in 3.1’ in the main body of the specification, and with an Omega symbol (Ω) in the Data element summary. Changes are dated 29 Mar 2023 in the Document history below, and use of data elements introduced in 3.1 may require Codelists Issue 60 or later.

#### Introduction to Release 3.1 revision 1 (3.1.1)

This minor revision includes a new option for expressing Usage constraints and Licensing that apply to collateral material such as descriptive text and cover images. It also adds two other improvements, to <CopyrightStatement> and to <Prize>. Full use of the new data elements introduced in version 3.1.1 requires Codelists Issue 65 or later. The newly-added data elements are marked ‘New in 3.1.1’ in the main body of the specification, and with a Pi symbol (Π) in the Data element summary.

#### Introduction to Release 3.1 revision 2 (3.1.2)

This minor revision adds provision for postal addresses to <ProductContact> and <SupplyContact>. Full use of version 3.1.2 requires Codelists Issue 65 or later. The newly-added data elements are marked ‘New in 3.1.2’ in the main body of the specification, and with a Lamda symbol (Λ) in the Data element summary.

#### Introduction to Release 3.0

This major new release of ONIX for Books – the first such since 2001 – introduces a large number of changes to the ONIX standard, aimed at introducing new functionality, removing outdated data elements and increasing both the consistency and interoperability of ONIX data and the ease with which this new release can be maintained and developed in the future. Inevitably, this means that ONIX 3.0 is not compatible with earlier releases and revisions – although many parts of the ONIX message are unchanged.

This Product Information Format Specification (the Specification) replaces, for ONIX for Books Release 3.0, the separate documents which in previous ONIX releases were given the titles Product Record Format, XML Message Specification and Overview and Data Elements. The change of title reflects the fact that the single Specification document now includes sections describing the top-level XML message structure and the message header as well as the Product record itself. This Specification also includes a complete sample message, an overview of the XML data elements and complete lists of ONIX XML tags.

Other documentation for Release 3.0 comprises an Introduction to ONIX for Books 3.0, the ONIX for Books Codelists (Issue 12 or later), the ONIX for Books Implementation and Best Practice Guide (the Guide), together with a small number of How to… guides on particular aspects of ONIX 3.0 usage, with detailed examples. There is a separate specification for an Acknowledgement message which may be sent in response to an ONIX Product Information message, and which may form part of a message ‘choreography’ between data sender and recipient.

Although this issue of the Specification is complete in terms of its coverage of the structure and data elements in ONIX 3.0, it may be subject to further revision, not only to correct any errors that are found during the early stages of implementation, but also to add material that may make it easier to use. The codelists – which form an important part of the standard – are also regularly updated. Any revisions will be notified through the ONIX for Books implementation listserv. If you are not already a member, you may wish to sign up through the EDItEUR website.

The Specification includes a number of corrections and additions made after the initial release of ONIX 3.0 documentation, following early proof-of-concept implementation – please note especially the list of corrections below dated 29 October 2010 and earlier. In particular, attention is drawn to the new <ROWSalesRightsType> element which is intended to reduce the variations in interpretation regarding product sales rights information from different ONIX data suppliers. Any ONIX 3 implementations developed prior to this date will likely need updating to incorporate this element. There are also important clarifications in the repeatability of <SupplyDetail> and <Supplier>.

#### Introduction to Release 3.0 revision 1 (3.0.1)

This revision includes a number of changes which form version 3.0.1 of the Specification. These include additions to ensure ONIX 3.0 is suitable for use with East Asian writing systems and multi-language supply chains, a handful of other additions, and some deprecations intended to simplify implementation.

Please note the list of changes dated 27 Jan 2012 in the Document history below. New data elements and composites are marked ‘New in 3.0.1’ in the main body of the specification and with a dagger symbol (†) in the Data element summary. Use of data elements introduced in version 3.0.1 may require Codelists Issue 16 or later.

#### Introduction to Release 3.0 revision 2 (3.0.2)

This revision includes a number of new data elements which form version 3.0.2 of the Specification. These include additional elements for specifying more detailed physical stock information, new price identifiers, and additional information about licensing of digital products and locations associated with contributors. New data elements and composites are marked ‘New in 3.0.2’ in the main body of the specification, with a double dagger symbol (‡) in the Data element summary, and the changes are dated 24 Jan 2014 in the Document history below. Use of data elements introduced in version 3.0.2 may require Codelists Issue 24 or later.

There is also a new preferred method for specifying sales restrictions acting within a specific territory, and the original method is deprecated. This and other changes are covered in the associated Guide.

#### Introduction to Release 3.0 revision 3 (3.0.3)

This revision includes a number of new data elements and other improvements which form version 3.0.3 of the Specification. These include inter alia a new <PriceConstraint> composite for specifying various commercial terms and conditions associated with a price, new elements for minimum order quantities, star ratings for reviews and a new <Gender> element. The <Conference> composite is renamed as <Event> and broadened in scope. Collateral material in Block 2 can be targeted at particular territories, and treatment of unnamed contributors and unpriced items is improved. New data elements and composites are marked ‘New in 3.0.3’ in the main body of the specification, with a section symbol (§) in the Data element summary, and the changes are dated 25 Apr 2016 in the Document history below. Use of data elements introduced in version 3.0.3 may require Codelists Issue 33 or later.

#### Introduction to Release 3.0 revision 4 (3.0.4)

This revision includes additional elements and composites and other changes which comprise version 3.0.4 of the Specification. Among these improvements are a new <SupplyContact> composite within <SupplyDetail> to specify ordering, customer care, or returns authorization contacts at the supplier, an <EpubLicense> composite within <Price> for products where price constraints are in use, and additional <PricePartDescription> within <Tax> for products that have price components with varying tax rates. A key limitation on the use of <NameAsSubject> for real people or organizations is relaxed. Newly-added data elements and composites are marked ‘New in 3.0.4’ in the main body of the specification, and with a Delta symbol (Δ) in the Data element summary. Changes are dated 26 Oct 2017 in the Document history below. Use of data elements introduced in version 3.0.4 may require Codelists Issue 39 or later.

#### Introduction to Release 3.0 revision 5 (3.0.5)

This minor revision includes only one substantive addition – the <AVItem> composite in Block 3 – and a very small number of other minor additions. AV Item enables Block 3 to be used for detailed tables of contents for time-based media products such as audiobooks, and specifically allows timecodes for chapter starts to be included. The newly-added data elements and composites are marked ‘New in 3.0.5’ in the main body of the specification, and with a Phi symbol (Φ) in the Data element summary. Changes are dated 26 Oct 2018 in the Document history below. Use of data elements introduced in version 3.0.5 may require Codelists Issue 43 or later.

#### Introduction to Release 3.0 revision 6 (3.0.6)

This revision includes only two minor updates – the addition of <Measure> within <ProductPart> and a change to the cardinality and attributes of <WebsiteLink>. The newly-added data elements and composites are marked ‘New in 3.0.6’ in the main body of the specification, and with an Xi symbol (Ξ) in the Data element summary. Changes are dated 26 Apr 2019 in the Document history below.

#### Introduction to Release 3.0 revision 7 (3.0.7)

This significant revision introduces a new Block 7 – Promotional event detail – into ONIX 3.0, as well as a small number of minor updates. This is intended to enable a Product record to carry details of events such as author reading and signing tours or festival appearances promoting sales of the book. Widespread use would raise the profile of such events, and event aggregation services could notify subscribers of events in their locality.

Note that the numbering of Block 7 and its constituent Group P.27 do not follow the message order because of the block’s position between the existing Blocks 2 and 3. The newly-added block, its data elements and composites are marked ‘New in 3.0.7’ in the main body of the specification, and with a Sigma symbol (Σ) in the Data element summary. Changes are dated 31 Oct 2019 in the Document history below. Use of data elements introduced in version 3.0.7 may require Codelists Issue 47 or later.

#### Introduction to Release 3.0 revision 8 (3.0.8)

This revision of the ONIX 3.0 standard introduces a new Block 8 – Production detail – which is intended to allow communication of detailed specifications and source file manifests between a publisher and a technical services provider. These details can include all the information needed by the services provider to create the product itself from the components supplied – for example details of the source files, specifications for on-demand printing, transcoding and packaging parameters for audiobooks and conversion requirements for e‑books. As such, Block 8 is not intended for general use right across the supply chain, and should be ignored by recipients not providing such services. However, it is intended to eliminate the need for so-called ‘sidecar files’, additional product specifications and manifests that hitherto were exchanged in parallel with ONIX data.

In message order, Block 8 and its constituent Group P.28 are positioned between the existing Blocks 5 and 6. The newly-added block, its data elements and composites are marked ‘New in 3.0.8’ in the main body of the specification, and with a Psi symbol (Ψ) in the Data element summary. Changes are dated 29 June 2021 in the Document history below. Use of data elements introduced in version 3.0.8 may require Codelists Issue 54 or later.

Revision 3.0.8 is the final revision of ONIX 3.0. Further development will be based on Release 3.1, which removes elements that are listed in Appendix A.4. Any valid ONIX 3.0.8 message that does not contain any of those deprecated elements – or the <Gender> element, which has also been removed – can be converted to ONIX 3.1 by changing only the <ONIXMessage> release and xmlns attributes.

#### Document history

1 Apr 2009
  Initial release (as PDF).
8 May 2009
  A broken link to Code List 2 in P.3.1 has been repaired.
17 July 2009
  Examples containing ampersands in P.8.12, P.19.4, P.20.12, P.21.14 and P.24.9 have been clarified with respect to the XML representation of the symbol &.
  In P.3.1, the short tag for <ProductComposition> has been corrected to read ‘<x314>’.
  In P.3.13, a reference to <MeasureTypeCode> has been corrected to read ‘<MeasureType>’.
  In P.4.5 and P.4.6 the code list links have been corrected.
  The rules expressed in the text introducing the <ProductPart> composite, and in P.4.12 and P.4.13, have been adjusted to allow <NumberOfCopies> to be sent without a <ProductIdentifier> if no identifier is available.
  After P.5.13 and P.6.8, an ‘End of title element composite’ strapline has been added.
  In P.7.48, the Format definition wrongly gave the impression that the element could carry multiple region codes: in fact it is intended only for a single code.
  The ‘End of title detail composite’ strapline after P.8.18 has been corrected.
  Following P.11.4, errors in the short tag version of the second example of the <Extent> composite have been corrected.
  In P.14.3, a reference to <OtherText> has been corrected to read ‘<TextContent>’.
  In P.15.1, multiple errors resulting from cut-and-paste have been corrected.
  Immediately before P.16.7, an error in the first sentence of the text describing the <ResourceVersion> composite has been corrected.
  In P.16.7, the short tag for <ResourceForm> has been corrected to read ‘<x441>’.
  In P.16.9, a reference to ‘free text in <FeatureValue>’ has been corrected to read ‘free text in <FeatureNote>’.
  In P.16.11, the text has been corrected to read ‘Mandatory in each occurrence of the <ResourceVersion> composite’.
  In P.18, in the <Contributor> composite, references to elements P.8.19 to P.8.66 have been corrected to read ‘P.18.19 to P.18.66’.
  In P.18, in the <RelatedWork> composite, references to ‘supporting resource’ have been corrected to read ‘related work’.
  Immediately before P.20.7, the wording describing the <CopyrightStatement> composite has been corrected.
  The ‘End of related material composite’ strapline after P.23.4 has been corrected.
  In P.26.1, the text has been corrected to read ‘Mandatory in each occurrence of the <Supplier> composite’.
  Following P.26.1, in the text introducing the <Supplier> composite, a reference to <SupplyDetail> has been corrected to read ‘<Supplier>’.
  Immediately before P.26.9, in the description of the <Website> composite, a reference to <SupplyDetail> has been corrected to read ‘<Supplier>’.
  After P.26.11, an ‘End of supplier composite’ strapline has been added.
  On the last page of P.26, errors in the data element number ranges have been corrected.
21 Sept 2009
  In H.15, added reference to ISO 8601, on which the date/time format is based.
  Immediately after P.3.14, the examples have been corrected so that the short tag for <MeasureType> is now shown as ‘<x315>’.
  In P.9.1, the short tag for <EditionType> has been corrected to read ‘<x419>’.
  In P.20.3, the short tag for <PublishingDateRole> has been corrected to read ‘<x448>’, and the Code list link has been corrected so that it now specifies List 163.
18 Nov 2009
  In H.15, clarified the range of date/time options supported in the schema.
  In P.3.1, the code value in the example has been corrected.
  In P.7.39, the suggested maximum length has been changed to 200, to be consistent with the <CorporateName> element.
  In P.7.40, the suggested maximum length has been removed. However, in the light of recent discussion on the ONIX_Implement listserv, the future usefulness of these suggested lengths is likely to be reviewed.
22 Dec 2009
  In the examples following P.3.14, and in the text above relating to corrections issued in September, the reference name <MeasureUnit> has been corrected to read ‘<MeasureUnitCode>’.
  In the examples in P.5.7 and P.6.2, the code value has been corrected.
  In P.7.47.and P.7.48, wording has been added to clarify that there must be at least one occurrence of either or both of the <CountryCode> and <RegionCode> elements in each occurrence of the <ContributorPlace> composite.
  In the example in P.19.1, the code value has been corrected.
  In P.19.6, the short tag for <PublisherIDType> has been corrected to read ‘<x447>’.
18 Mar 2010
  Multiple errors in P.26.15 have been corrected.
  In P.16.8, the short tag for <ResourceVersionFeatureType> has been corrected to read ‘<x442>’.
18 May 2010
  The text describing P.7.14 has been amended to indicate that the Key Name(s) element is required if name part elements are used to represent a person name.
  An error in the example in P.25.13 has been corrected.
29 Oct 2010
  Missing short tags have been inserted in P.1.5 and P.5.3.
  Notes on P.16.9 have been expanded to include a link to Code List 178.
  New <ROWSalesRightsType> element has been inserted in P.21.10, the example of the use of <SalesRights> composite corrected (to incorporate both the <ROWSalesRightsType> element and the <Territory> composite), and the remainder of elements in P.21 renumbered. Reference to the <ROWSalesRightsType> element has been added in the introductory text to P.21.
  Description of cardinality of <SupplyDetail> and <Supplier> has been changed, so the former is repeatable and the latter non-repeatable.
  Added new <CorporateNameInverted> element at P.7.20. Note this new element may also be used within the <AlternativeName> and <NameAsSubject> composites. Remainder of P.7 elements renumbered, revised P.7 introductory text. Renumbering of P.7 affects numbering of several other parts of the document.
  Modified <DateFormat> and <Date> elements within various composites carrying dates at P.7.36, P.14.8, P.15.10, P.16.13, P.20.4, P.25.14, P.26.19, P.26.75, to incorporate reference to the dateformat attribute, and to deprecate <DateFormat>. Also modified <ConferenceDate>, <CopyrightYear>, <StartDate>, <EndDate>, <ExpectedDate> and <ReissueDate> to use the dateformat attribute. The attribute may take a range of values from List 55.
  Made <NameType> optional within <NameAsSubject>.
  Added ability to carry <ProductForm> and <ProductFormDetail> codes at P.23.5 and P.23.6 within <RelatedProduct>. Note that these elements should not normally be included in a <RelatedProduct> composite, but may optionally be included if required by a specific recipient.
  Made P.23.1 <ProductRelationCode> repeatable within a single <RelatedProduct> composite, where the related product has multiple types of relationship to the product described in the ONIX record.
  Removed erroneous reference to List 155 in text describing the <PublishingDate> composite.
  Added new optional element <MarketPublishingStatusNote> in P.25, renumbered remaining elements within P.25.
  Made the <MarketDate> composite optional within P.25. Changed <MarketDateRole> to use codelist 163 (same list as ‘global’ <PublishingDateRole>).
  Added new <PriceCoded> composite to support prices expressed as discrete price points, bands or tiers rather than as currency amounts. A new Code list 179 is introduced for use with <PriceCodeType>. <PriceAmount> becomes optional. Renumbered remainder of P.26.
  Deprecated use of <CurrencyZone> data element.
  Added new <ComparisonProductPrice> composite to support notification of prices of comparable products. Note that this composite should not normally be included in a <Price> composite, but may optionally be included if required by a specific recipient. Renumbered remainder of P.26.
  Removed references that suggest <RecordReference> should necessarily be a number, and increased the suggested maximum data size for this element.
  Clarified that a contributor’s primary name is the name used on the product, and any alternative name merely provides additional information (eg if the book is written under a pseudonym, where the real identity of the author is well-known, the primary contributor name should be the pseudonym and the real name of the contributor may be provided as an alternative name).
  In P.12.6, <SubjectHeadingText>, increased the suggested maximum data length from 100 to 250 characters, to account for the possibility of supplying long semicolon-separated lists of keywords (ie where <SubjectSchemeIdentifier> is 20).
  Clarified that XHTML is enabled in the <SalesRestrictionNote> element P.24.10.
  Deprecated the <Complexity> composite in favor of incorporating Lexile measures in the <Audience> composite. No other schemes had been identified for use within <Complexity>.
  Minor correction to example of simple <Header> composite.
  Corrected error in description of the <RegionsExcluded> element in P21.5: it may only occur if <CountriesIncluded> is present.
25 Nov 2010
  Corrected <x408> to <x406> in <MarketPublishingStatusNote>.
  Corrected format note for <PriceCode> to refer to <PriceCodeType>.
6 Jan 2011
  HTML format with enhanced content.
  Note this is draft HTML5, and does not display correctly in all browsers. Added notes on Copyright page indicating browser compatibility, and the need for Unicode font support.
  Added navigation behavior so that a click on any heading links to the parent section, and multiple clicks eventually return to the Table of Contents. Shift-click returns immediately to the Table of Contents, and on most headings, alt-click switches to the equivalent heading in the related Implementation and Best Practice Guide.
  Added note on requirement to contact EDItEUR before translation or other localization.
  Added explicit cardinality statements and valid attributes in descriptions of composites and data elements. These were previously only available in the ONIX for Book: Product Information Format Data Element Summary.
  Added element tags to examples. The choice of reference name or short tag on any particular example is not meaningful – they are interchangeable, excepting that they cannot be mixed within any one ONIX message. Some element examples illustrate the use of appropriate attributes.
  Added explicit links to codelists. Codelist HTML documents must be in ‘codelist’ folder in the same location as this document.
  Added examples illustrating use of <ProductIdentifier>, <Barcode>, <ProductFormFeature>, <EpubTechnicalProtection>, <ProductClassification, <NameIdentifier>, <Website>, <Language>, <AncillaryContent>, <Subject>, <NameAsSubject>, <Audience>, <Prize>, <SupportingResource>, <CitedContent>, <Imprint>, <Publisher>, <SalesRestriction>, <RelatedWork>, <RelatedProduct>, <DiscountCoded>, <PriceCoded> composites; extended existing examples using <Header>, <ProductPart>, <TitleDetail>, <Contributor>, <Extent>, <SalesRights>, <Price> composites.
  Added diagrams illustrating inclusion/exclusion of Countries, Regions within <SalesRights>, sequencing of <PublishingStatus> and <ProductAvailability> codes. Note these diagrams use embedded SVG, and will show only in very modern browsers.
  If no ‘spectacles’ icon is visible here, the diagrams will not display.
  Incorporated restructured and partly rewritten content from ONIX for Books: Product Information Format XML Technical Notes document to form Section 1.
  Incorporated some content from ONIX for Books: Product Information Format Data Element Summary to form Part 1 of Section 5 Appendix.
  Incorporated revised and extended content from ONIX for Books: Product Information Format Annotated Sample Message document to form Part 2 of Section 5 Appendix.
  Added sorted lists of tags in Part 3 of Section 5 Appendix.
  Other minor editorial corrections and additions for clarity and style.
14 Apr 2011
  Extended suggested max length of <ProductFormFeatureDescription> from 100 to 500 characters, to ensure adequate capacity for EU Toy Safety warning wording.
15 May 2011
  Minor correction to numbering of elements of <Contributor> composite within Group P.5. <NoCollection/> becomes P.5.64 instead of P.5.62.
  Corrected two references to <ReligiousTextID> to <ReligiousTextIdentifier>.
13 July 2011
  Corrected allowed formats for datestamp attribute and <SentDateTime> element.
  Corrected cardinality for <Percent> element.
  Corrected one reference to <PersonNameIdentifier> to <NameIdentifier>.
  Clarification that <EpubUsageConstraint> can be used even if product does not enforce constraints through technical protection.
  Added note about use of a BOM in UTF‑16.
15 Oct 2011
  Corrected cardinality of <KeyNames> – it is only mandatory if other structured name elements are used.
  Change of namespace for ONIX 3 (see Using Release 3.0 and 3.1 schemas for validation).
27 Jan 2012
  Release 3.0 revision 1.
  Removed legacy limitation to ASCII character set in elements within <Header>.
  Added new collationkey attribute, attached to data elements within <TitleElement> and <Contributor> composites, to carry phonetic or other non-alphabetic sorting information.
  Added new textscript attribute, attached to data elements within the <AlternativeName> composite, to carry transliterated names.
  Added two notes in X.13 and X.14 about XHTML <ruby> markup and Unicode interlinear annotation delimiters for East Asian writing systems.
  Added new <CollectionSequence> composite in Group P.5, for sequential ordering of products within collections.
  Added <ContributorStatement> within Group P.5 for consistency with Group P.7.
  Added new <SequenceNumber> element within <TitleElement> composite in Groups P.5 and P.6, to provide an explicit preferred display order for parts of a title.
  Added new <TitleStatement> element in Group P.6, to provide a title for display purposes (only) when concatenation of the title elements may not be adequate.
  Added new <ProductContact> composite in Group P.19, and in P.25, for per-product contact details.
  Changed data format of <SubjectSchemeIdentifier> from two digits to two alphanumeric characters, to allow more than 100 subject schemes.
  Changed data format of sourcename attribute, <SenderName>, <AddresseeName> to increase suggested maximum length of text to 50 characters.
  Modified <ThesisYear> to take dateformat attribute.
  Inserted reference to EU Toy Safety hazard warnings and e-publication accessibility in <ProductFormFeatureValue>.
  Deprecated the entire <Reissue> composite in Group P.26, in favor of providing reissue information and collateral material in the main body of the Product record – for example, providing collateral material within Block 2 with an appropriate <ContentDate>.
  Deprecated <AudienceCode> in Group P.13, in favor of providing the same information within the <Audience> composite.
  Deprecated <PromotionContact>, <TelephoneNumber>, <FaxNumber> and <EmailAddress> data elements in Group P.25, in favor of using the <ProductContact> composite.
  Improvements to the Data element summary Appendix: added hyperlinked data element numbering, flagged XHTML-enabled data elements, corrected spelling of <BibleTextOrganization> and P.18 <titleelement> tags.
  Corrected description and cardinality of <CountryCode> and <RegionCode> elements within Group P.7.
  Added language attribute to <MessageNote> and <AudienceCodeTypeName>.
  Modified cardinality of <MessageNote>, <DeletionText>, <ProductFormFeatureDescription>, <ProductFormDescription>, <BiographicalNote>, <ContributorDescription>, <ProfessionalPosition>, <WebsiteDescription>, <ContributorStatement>, <EditionStatement>, <ReligiousTextFeatureDescription>, <IllustrationsNote>, <AncillaryContentDescription>, <SubjectHeadingText>, <AudienceDescription>, <Text>, <FeatureNote>, <CitationNote>, <PublishingStatusNote>, <SalesRestrictionNote>, <MarketPublishingStatusNote> and <PriceTypeDescription>, to allow supply of textual metadata in multiple languages ‘in parallel’ within a single Product record.
  Corrected short tags in examples in X.14 and X.15 from <text> to <d104>.
24 Feb 2012
  Added keywords into example record.
  Clarified relationship between <TitleText>, <TitlePrefix> and <TitleWithoutPrefix>.
  Corrected spelling of ‘identifer’ to ‘identifier’ in some tag names.
25 Apr 2012
  Added ISNI example, and added ISNI to sample record.
  Corrected documented cardinality of <CopyrightStatement> (it is repeatable).
3 Aug 2012
  Corrected example showing use of <Imprint> composite.
  Corrected typos in P.7.8 and after P.26.16, and aligned the example for <ProductIdentifier> with best practice.
  Corrected <CollectionIdentifierType> tagname to <CollectionIDType> in appendix.
19 Oct 2012
  Corrected example showing positive indication of no barcode.
19 Mar 2013
  Corrected typos in heading of P.7.6, and in attributes for P.5.13a within A.1.
19 July 2013
  Corrected typo in format of P.1.7.
24 Jan 2014
  Release 3.0 revision 2.
  Added <EpubLicense> composite for digital product licensing.
  Added <LocationName> within <ContributorPlace> (and renumbered P.5.63a to P.5.63b), to associate a contributor with a town or city.
  Added <NoPrefix/> empty element to indicate positively that titles have no prefix, and modified sample message.
  Added <PrizeStatement> within <Prize>, to allow use of exact terminology for each prize.
  Added <CopyrightType> within <CopyrightStatement>, to allow phonogram rights to be listed.
  Added <SalesRestriction> within <SalesRights>, and deprecated <SalesRestriction> in previous location within <PublishingDetail>, to clarify that restrictions operate within territories.
  Added <SupplierCodeTypeName> within <SupplierOwnCoding>.
  Added <Proximity> and <Velocity>, and changed cardinality of <StockQuantityCoded>, within <Stock>, to improve stock reporting functionality.
  Added <PriceIdentifier> within <Price>, for improved revenue reporting.
  Added <ToQuantity> to allow more complex discounts.
  Added <ProductIdentifier> within <PriceCondition>, for linked price offers.
  Added <NoProduct/> for ‘empty’ delta updates.
  Allowed XHTML markup in <EditionStatement> and increased maximum recommended length.
  Removed deprecation from <Complexity> composite.
  Deprecated use of textformat attribute on <ConferenceTheme>.
  Changed cardinality on <PromotionCampaign>, <InitialPrintRun>, <ReprintDetail>, <CopiesSold>, <BookClubAdoption>, <PrizeName>, <ListName>, <SourceTitle> to allow repeats in parallel languages.
  Added language attribute to <SourceTitle>, <PartNumber>, <ImprintName>, <CityOfPublication>, <ConferencePlace> and contributor name elements, and added textscript elements to publication title elements, to improve consistency of treatment of various textual data elements.
  Added further notes on specific versions of e-publication file formats.
  Added notes on use of HTML 5.
  Clarified the required format for <YearOfAnnual>.
  Corrected a statement about inclusion of smart quotes in the Latin‑1 character set and a small number of minor typos.
17 Feb 2014
  Corrected typos – fixed spelling of <titleelement> in A.1.
29 Mar 2014
  Corrected documented cardinality of <AgentRole> in P.25.1 (it is mandatory).
21 Aug 2014
  Corrected link to List 220 in P.3.5.
24 Jan 2015
  Changed reference to removing the xmlns attribute on <ONIXMessage> for DTD validation.
  Added note in P.26.62 to clarify that a zero <PriceAmount> is not valid.
  Added reference to Acknowledgement Message specification.
25 Apr 2016
  Release 3.0 revision 3.
  Added <ProductPackaging> to <ProductPart>.
  Added <Prize> to <Contributor>, to support ‘body of work’ prizes.
  Added <Gender> to <Contributor>, to support ISNI registrations.
  Restructured <UnnamedPersons>, so an anonymous author can have a name identifier or an alternative name. The previous structure is deprecated.
  Added <Event> as an alternative to <Conference>. The latter is now deprecated.
  Added <AlternativeName>, <SubjectDate> and <ProfessionalAffiliation> within <NameAsSubject>, to improve discoverability.
  Added <Territory> within <TextContent>, <CitedContent> and <SupportingResource>, to support market-specific collateral material.
  Added <ReviewRating> within <TextContent> and <CitedContent>, to support structured star ratings for reviews.
  Added <RelatedProduct> within <ContentItem>, to improve support for citations.
  Added new <Funding> composite within <Publisher> to support tracking of grants and awards for open access publishing.
  Added elements for specifying minimum order quantities.
  Added <ReturnsNote> in <Supplier>, for special returns instructions.
  Added <PriceConstraint> within <Price>, to support contractual terms and conditions such as library lending limits as part of a particular commercial offer.
  Added <UpricedItemType> within <Price>, to support products which are available both priced and unpriced from the same supplier.
  Added new <ProductIdentifier> composite within <Tax> to support German tax requirements.
  For consistency, changed cardinality on <LocationIdentifier> and <LocationName> within <Stock> to allow parallel identifiers and multi-language place names, added language attribute to cited content and supporting resource links.
  Documented restrictions on positive and positive or zero numbers in numeric fields, in line with notes published Jan 2015.
  Increased suggested maximum length for elements within <Territory>, <SubjectHeadingText>.
  Clarified semantics of datestamp attribute.
24 May 2016
  Corrected minor typos, fixed reference to <PublishingRole> in <Funding> composite, and added a sentence clarifying use of <UnpricedItemType> within <Price> composite.
16 Aug 2016
  Corrected typo in definition of <UnpricedItemType>.
11 Nov 2016
  Noted incompatibility between embedded HTML and XSLT processing in X.15.
14 July 2017
  Fixed error in change history for Sept 2009, corrected two links in Appendix A.1, minor clarification of wording in <Tax>.
26 Oct 2017
  Release 3.0 revision 4
  Added <SupplyContact> within <SupplyDetail> to support multiple contacts at the supplier organization.
  Added <PricePartDescription> within <Tax>, to support French tax requirements.
  Added <EpubTechnicalProtection> and <EpubLicense> within <Price>, to specify DRM and licenses that form a part of a particular commercial offer; renumbered existing <PriceConstraint> P.26.44a–d to P.26.44b–e.
  Modified allowed format of <CollectionSequenceNumber> to support more flexible collection ordering.
  Added <Reserved> within <Stock> to support frozen stock quantities.
  Added <Language> within <ContentItem> to support chapters in different languages.
  <ContributorStatement> and <NoContributor/> also added in <ContentItem>, and <NoContributor/> in <Collection>.
  Clarification that <NameAsSubject> can be applied to names of fictional characters.
26 Oct 2018
  Release 3.0 revision 5
  Added <AVItem> in Block 3 to support chapter-level audio timecodes.
  Added <PalletQuantity> in Block 6. Renumbered P.26.41a–c to 41b–d.
  Added <TaxExempt/> as an empty element in <Price>. Renumbered P.26.70a to 70b.
  In block updates (only), Blocks 2, 3, 5 may now be empty.
  Corrected documented cardinality of <SalesOutletIdentifier> in P.24.
  Minor updates of wording to clarify how particular composites should be repeated.
24 Dec 2018
  Corrected documented cardinality of P.25.9.
26 Apr 2019
  Release 3.0 revision 6
  Added <Measure> within <ProductPart> in Block 1.
  Revised cardinality of <WebsiteLink> within the <Website> composite.
31 Oct 2019
  Release 3.0 revision 7
  Added <PromotionalEvent> within a new Block 7, Group P.27.
  Added <ProductClassificationTypeName> within <ProductClassification>.
  Added <TextSourceDescription> in <TextContent>.
  Added a region code element in <Language> and <Prize>.
  Allowed XHTML markup in <PrizeStatement> and increased maximum recommended length.
  Modified <ImprintName>, <PublisherName>, <SupplierName>, <AgentName> to allow a collationkey attribute.
  Modified cardinality of <CopyrightYear>.
29 June 2021
  Release 3.0 revision 8
  Added <ProductionManifest> within a new Block 8, Group P.28.
  Added <TelephoneNumber> in <ProductContact>, <SupplyContact>, <Sender> and <Addressee>.
  Added <AudienceHeadingText> in <Audience>.
  Added Supporting resources in <PromotionalEvent>.
  Added sample Block update message in Appendix A.2.
  Other minor updates of wording for clarification.
20 Aug 2021
  Added note about URL-encoding to <ResourceLink>, <WebsiteLink> etc.
6 Jan 2022
  Minor corrections to some headings.
3 Aug 2022
  Minor corrections to cardinality of some Block 8 composites in Appendix A.1.
  Clarification of text around <AudienceCodeValue> and <AudienceHeadingText>, corrected documented cardinality of <AudienceCodeValue>, reduced suggested maximum length of <AudienceDescription>.
29 Mar 2023
  Release 3.1
  Added <MarketReference> to enable market-specific partial (‘Block’) updates.
  Added <EpubLicenseDate> in <EpubLicense> within <DescriptiveDetail> (but not within <Price>), to enable future licensing changes.
  Added <CollectionFrequency> to carry frequency of publication of products in a collection.
  Added <CollectionElementLevel> to enable linking of Collection identifiers to specific collection title elements.
  Added <AffiliationIdentifier> within <ProfessionalAffiliation>.
  Added <AwardingBody> within <Prize>.
  Added <SequenceNumber> to allow explicit prioritization of collateral material.
  Added <EpubUsageConstraint>, extended <EpubLicense>, <Publisher> and <CopyrightStatement> within <ContentItem> for hybrid open access (ie per-chapter licensing).
  Added <Website> within <NewSupplier>, added <FaxNumber> within <ProductContact>, <SupplyContact>, removed deprecation from contact details within <PublisherRepresentative>, <Supplier>, to improve consistency of various composites.
  Removed elements deprecated in previous version of ONIX, and also removed <Gender> since it is no longer used for ISNI registrations.
  Modified cardinality <CorporateName> and <CorporateNameInverted> within <Contributor>, and of <PublisherName>, for corporate names that are in multiple specific languages.
  Emphasized that recommended and fixed lengths of textual data are specified in characters, not bytes, and clarified that any HTML or XHTML markup is not included in the character count. Extended recommended maximum lengths of <IDTypeName> and <EditionVersionNumber>.
  Deprecated various defaults set in the message header, and the <TitleText> tag. These may be removed in the next release of ONIX.
  Switched document codelist links to use ns.editeur.org/onix/en.
28 Mar 2024
  Release 3.1 revision 1
  Added <EpubUsageConstraint> and <EpubLicense> to <TextContent> and <SupportingResource> composites in Block 2 and elsewhere.
  Added <CopyrightStatementText> and <PrizeIdentifier>.
12 Apr 2024
  Corrected documented cardinality of <CollectionFrequency> in P.5.1a (it was correct in the Appendix and the schema).
3 May 2024
  Corrected format of <PrizeIDType> to two alphanumeric characters.
28 Oct 2024
  Release 3.1 revision 2
  Added <PostalCode>, included postal addresses within <ProductContact> and <SupplyContact>.
  Increased suggested maximum length of Product form feature description.
20 Mar 2025
  Further increased suggested maximum length of Product form feature description.
2 Oct 2025
  Fixed inconsistency in specified format of codes in List 251.
31 Oct 2025
  Increased suggested maximum length of Product form feature description to 10,000 chararacters, to accommodate 400+ point polygons for EUDR purposes.

## ONIX for Books message

#### High-level structure and conformance

ONIX for Books is a standard data format based on XML. It is used primarily to convey information about book and book-related products between computer systems.

Data files, or ‘messages’, conforming to the ONIX for Books Product Information Format are typically sent from data sender (eg a publisher) to data recipient (eg a retailer or a library) as part of a routine and largely automated exchange of data – often termed a ‘data feed’ – within a metadata supply chain. Distributors, wholesalers, specialist data aggregators and other service vendors may both receive and send messages, acting as intermediaries in that metadata supply chain.

An ONIX for Books message can be regarded as having four component parts: the start of message, whose format and content is dictated by the XML standard; a message header block; the body of the message describing a number of products; and the end of message.

The start and the end of message are described in Sections X.1 and X.2.

The message header carries a number of data elements, specifying the sender and date of message (mandatory), the addressee (optional), and optionally stating message default values for language, price type, and currency. For further details, see Section 3. ONIX for Books message header in this document.

The body of an ONIX for Books Product Information Format message normally consists of one or more Product records, with no theoretical limit on the number of records. Each Product record consists of some identifiers for the record and for the product it describes, plus up to eight blocks of information – each of which is optional. There are blocks dedicated to describing the product in bibliographic terms, to marketing collateral, to publishing details and territorial rights, etc. The final block – Block 6, carrying details of commercial distribution and pricing – may be treated as a repeatable block if the product is available in several different and independent markets. In earlier versions of ONIX, Block 6 was mostly treated as a single (and non-repeatable) block comprising all the market information.

The content and format of the Product record are detailed in Section 4. ONIX for Books Product record in this document.

From time to time, the message format is revised. Revisions – for example 3.0.6 was a very limited revision of 3.0.5 – add new and optional data elements and composites in order to add new functionality to the message, and revisions may occasionally deprecate data elements or composites. However, revisions never remove data elements altogether, nor do they add new mandatory elements. Revisions thus maintain full backward compatibility with their predecessors. ONIX message senders and recipients should avoid continued use of deprecated data elements, composites and codes (see below) since they are liable to be removed from a future release of the message format. A new minor Release such as 3.1 (after successive revisions of 3.0.x) may forego full backward compatibility, for example through removal previously-deprecated data elements or addition of new mandatory data elements, but the degree of back compatibility remains high. A new major Release – such as when 3.0 succeeded various minor releases and revisions of 2.x – may compromise backward compatibility very significantly.

Many data elements within an ONIX for Books Product Information Format message take their content from code lists – controlled vocabularies – to ensure common understanding of the data where message creator and recipient need not be in direct contact, and where they may operate in quite different markets. These code lists also form an integral part of the specification of an ONIX for Books message. Code lists are also revised from time to time to add new codes. Old codes are never deleted, though they may be deprecated. The earliest issue of the code lists that might realistically be used with this Specification is Issue 12, but for many elements marked as ‘New in 3.0.2’, ‘New in 3.1’ etc, a later issue is required:

- for full use of elements and composites marked ‘New in 3.0.1’, Issue 16 or later may be required;
- 3.0.2 may require Issue 24;
- 3.0.3 may require Issue 33;
- 3.0.4 may require Issue 39;
- 3.0.5 or 6 may require Issue 43;
- 3.0.7 may require Issue 47;
- 3.0.8 may require Issue 54 or later;
- release 3.1 may require Issue 60 or later;
- 3.1.1 and 3.1.2 may require Issue 65 or later.

An overriding requirement is that an ONIX for Books Product Information Format message must conform to the XML standard, ie it must be well-formed XML. It is also a requirement that ONIX messages are valid according to the associated RNG and XSD schemas (which are equivalent, excepting that the XSD schemas implement a number of uniqueness constraints that cannot be implemented in the RNG schema). A key aspect of this requirement is that the schemas specify the order of the various data elements that occur in an ONIX message – it must match the order in the Specification.

Previous releases of the ONIX for Books Product Information Format message were supported by formal definitions in one or two schema formats: DTD and (later) XSD. From Release 3.0, EDItEUR maintained formal definitions in three schema formats: RNG, XSD and DTD. The RNG and XSD formats differ from the DTD format in that they make extensive use of formal specifications of the code lists, whereas the DTD format makes almost no use of the code lists. Validation using the DTD is not sufficient and not recommended, as data element code values cannot be validated by this method. From Release 3.1, the DTD format is no longer maintained. ONIX message senders and recipients are free to choose which of the available ONIX for Books schemas to use in validating the ONIX messages that they create or receive, but if a DTD format is chosen (for releases prior to 3.1), implementers will need to find other methods for checking that all code values are valid, checking uniqueness constraints etc.

Each schema is available in two separate ‘flavors’ with differing but equivalent XML markup, and any message must choose one or other markup flavor – either Reference names or Short tags. The former means that message filesizes are larger, but messages are more easily human-readable – this can be useful during development and testing, or onboarding new data partners. Flavors must not be mixed within any one message. ONIX message senders and recipients may choose to implement either or both markup flavors, and best practice guidelines within any ONIX community may guide that choice. An XSLT script available from EDItEUR can be used to convert messages from one flavor to the other.

Finally there are both implicit and explicit business rules within the Specification. Many of these cannot be enforced through validation, though some can be checked using an enhanced or ‘strict’ XSD that EDItEUR also maintains.

All implementers are expected to check that all requirements of the ONIX for Books Product Record specification are met, irrespective of whether or not these requirements are formally specified and enforced by any of the schemas. In particular, the Specification defines requirements such as presence or absence of certain XML elements based on data values elsewhere in the message. These ‘business rule’ requirements cannot be specified in RNG, ‘classic’ XSD or DTD schema languages. They may or may not be encoded and enforced in the ‘strict’ XSD.

Your attention is drawn to the terms and conditions of use which appear in the ONIX for Books schemas themselves, in the EDItEUR license (doi:10.4400/nwgj) and on the copyright page of this Specification.

  XML is defined by W3C Recommendation Extensible Markup Language (XML) 1.0 (Fifth Edition) – see https://www.w3.org/TR/xml/ for more details.
  The DTD format is defined by the XML standard itself.
  The XML Schema Definition (XSD) format is defined by W3C Recommendation XML Schema Part 1: Structures (Second Edition) – see https://www.w3.org/TR/xmlschema-1 for more details.
  The advanced XSD v1.1 format used by the ‘strict’ schema is defined by W3C Recommendation XML Schema Definition Language (XSD) 1.1 Part 1: Structures – see https://www.w3.org/TR/xmlschema11-1/. The ‘strict’ schema also incorporates embedded Schematron, defined by ISO/IEC 19757-3:2016 – see https://standards.iso.org/ittf/​PubliclyAvailableStandards/​c055982_ISO_IEC_19757-3_2016.zip.
  The RELAX NG (RNG) format is defined by ISO/IEC 19757-2:2008, published by ISO, Geneva.

##### X.1 Start of message

The start of an ONIX for Books message must consist of, as a minimum, two lines of XML as shown:

  using Reference names |
  --- | ---
  `<?xml version="1.0"?>` |
  `<ONIXMessage release="3.1">` | Upper case ‘M’

  using Short tags |
  --- | ---
  `<?xml version="1.0"?>` |
  `<ONIXmessage release="3.1">` | Lower case ‘m’

The XML declaration line may additionally declare a character encoding attribute. Further details of this are given in the Character sets and special characters section below.

The <ONIXMessage> line may additionally declare an XML namespace attribute. Further details of this are given in the Using ONIX schemas for validation section below. Both character encoding declaration and namespace attribute are recommended.

For the purposes of validation of an ONIX message against one of the schemas it may be necessary to insert some additional information, to include an explicit reference to the schema against which to validate the message. The precise XML that needs to be inserted will depend upon the schema format and the tools being used for validation. Further details of this are also given in the Using ONIX schemas for validation section below. For communication purposes it is recommended that all such schema references be omitted from the message, as the recipient will frequently need to use a different version of the schema and different tools for validation to those used by the originator.

##### X.2 End of message

The end of message ‘trailer’ must consist of a single line as shown:

  using Reference names |
  --- | ---
  `</ONIXMessage>` | Upper case ‘M’

  using Short tags |
  --- | ---
  `</ONIXmessage>` | Lower case ‘m’

##### X.3 Layout of a complete message

In summary, the layout of a typical ONIX for Books Product Information Message is like this:

  using Reference names |
  --- | ---
  `<?xml version="1.0"?>` | Start of message
  `<ONIXMessage release="3.1">`
  `<Header>` | Header
  `<!-- message header data elements -->`
  `</Header>`
  `<Product>` | Body of message
  `<!-- record reference for product 1 -->`
  `<!-- product identifiers for product 1 -->`
  `<!-- block 1 product description -->`
  `<!-- block 2 marketing collateral detail -->`
  `<!-- block 7 promotion detail -->`
  `<!-- block 3 content detail -->`
  `<!-- block 4 publishing detail -->`
  `<!-- block 5 related material -->`
  `<!-- block 8 production detail -->`
  `<!-- block 6 product supply -->`
  `</Product>`
  `<Product>`
  `<!-- record reference for product 2 -->`
  `<!-- product identifiers for product 2 -->`
  `<!-- data blocks for product 2 -->`
  `</Product>`
  `<!-- further product records… -->`
  `<Product>`
  `<!-- record reference for product n -->`
  `<!-- product identifiers for product n -->`
  `<!-- data blocks for product n -->`
  `</Product>`
  `</ONIXMessage>` | End of message

  using Short tags |
  --- | ---
  `<?xml version="1.0"?>` | Start of message
  `<ONIXmessage release="3.1">`
  `<header>` | Header
  `<!-- message header data elements -->`
  `</header>`
  `<product>` | Body of message
  `<!-- record reference for product 1 -->`
  `<!-- product identifiers for product 1 -->`
  `<!-- block 1 product description -->`
  `<!-- block 2 marketing collateral detail -->`
  `<!-- block 7 promotion detail -->`
  `<!-- block 3 content detail -->`
  `<!-- block 4 publishing detail -->`
  `<!-- block 5 related material -->`
  `<!-- block 8 production detail -->`
  `<!-- block 6 product supply -->`
  `</product>`
  `<product>`
  `<!-- record reference for product 2 -->`
  `<!-- product identifiers for product 2 -->`
  `<!-- data blocks for product 2 -->`
  `</product>`
  `<!-- further product records… -->`
  `<product>`
  `<!-- record reference for product n -->`
  `<!-- product identifiers for product n -->`
  `<!-- data blocks for product n -->`
  `</product>`
  `</ONIXmessage>` | End of message

  Note the use of multiple Product records (from <Product> to </Product>). The number of Product records in a message may vary from one to many thousands, and a message with no Product records (but with a <NoProduct/> tag – see X.4 below) is also possible.
  Note also that ONIX messages can contain XML comments, introduced with ‘<!--’ and terminated with ‘-->’. Comments may be helpful during development, when data may have to be checked ‘by eye’. However, they are of no significant benefit in production, as they should be ignored by automated XML processing systems.

##### X.4 Empty XML elements

There are a very few elements in the ONIX for Books format which are defined as empty elements in XML, and whose function is to act as ‘flags’ which may be either present or absent. These elements do not carry any data content. An example in ONIX 3.1 is the <MainSubject/> element, used to flag a <Subject> composite to show that it represents the primary subject of a product (within any one particular subject classification scheme).

All other elements are defined as carrying data content, and must not be sent as empty elements. If an element is mandatory, data content must be supplied, or the message will be invalid. If an element is optional, and there is no content for it, it must be omitted entirely. These rules are enforced in the RNG and XSD schemas, but cannot be enforced by a DTD.

An exceptional empty element is <NoProduct/>. The sole valid use of this is to denote an ‘empty message’ within a stream of updates sent on a prearranged timetable, providing a positive indication that there have been no changes since the previous update:

  using Reference names |
  --- | ---
  `<?xml version="1.0"?>` |
  `<ONIXMessage release="3.1">` |
  `<Header>` |
  `<!-- message header data elements -->` |
  `</Header>` |
  `<NoProduct/>` |
  `</ONIXMessage>` |

  using Short tags |
  --- | ---
  `<?xml version="1.0"?>` |
  `<ONIXmessage release="3.1">` |
  `<header>` |
  `<!-- message header data elements -->` |
  `</header>` |
  `<x507/>` |
  `</ONIXmessage>` |

Another exceptional group consists of the five ‘empty blocks’: <CollateralDetail/>, <PromotionDetail/>, <ContentDetail/>, <RelatedMaterial/> and <ProductionDetail/> may only be empty within a partial ‘block update’ (see P.1.2) where the intention is to ‘reset’ or delete any previously supplied collateral material, promotional event detail, content detail, links to related products and works, or production manifest detail. The other blocks <DescriptiveDetail> and <PublishingDetail> contain mandatory elements and cannot be empty in any circumstances – though the blocks can be omitted entirely within block updates. <ProductSupply> is another exception – it cannot be entirely empty, but may – in a block update – contain only a <MarketReference> tag if the intention is to ‘delete’ references to a particular market, for example when another market is expanded to contain the territory of the former market.

Note that in all cases, the XML ‘self-closing’ syntax is conventional for empty elements and blocks in ONIX (ie use <NoProduct/> rather than <NoProduct></NoProduct>).

Although superficially similar, ONIX and XML empty elements are different from modern HTML5 ‘void elements’ which do not have closing tags (ie HTML5 recommends just <br> instead of <br /> or <br/> or <br></br>). In XML and ONIX, tags must have explicit end tags or use the self-closing syntax.

#### Use of XML attributes

In all ONIX applications, a number of XML attributes may be used where applicable to carry information about the content of an associated element. The view which has been taken in the development of ONIX is that it is undesirable to use XML attributes to carry portions of the actual data content of the ONIX message. However, it is appropriate to use them to carry information which qualifies the data itself and its representation – metadata about metadata, as it were.

Accordingly, a number of general attributes are defined in ONIX for Books. Three attributes may be used with any ONIX element, and they are not noted individually for each data element in the Specification:

- datestamp
- sourcename
- sourcetype

If used on the start tag of a composite, these attributes can be understood to apply to the whole composite, unless overridden by an attribute attached to a particular element within the composite. For example, they might be used to indicate that data within the <Stock> composite comes from a source other than the Record source named at the beginning of the Product record or the Sender of the message named in the Header.

Further attributes may be used with a limited selection of data elements, as noted individually for each element in the Specification:

- collationkey
- dateformat
- language
- release
- textcase
- textformat
- textscript

Other than release (which has a special role), these attributes relate to the content of individual data elements.

Attributes are carried within an XML start tag. The attribute name is lower case, separated from the name of the element by a space, and the attribute value is placed in double quotes. If there are two or more attributes in a single tag, they too are separated by a space. Multiple attributes in a single tag may occur in any order.

The built-in XML attributes xml:lang and xml:space are not used in ONIX for Books: these attributes are available by default in all XML applications and cannot be prohibited technically, but they should never be included in ONIX messages. If received in an ONIX message, the recipient should ignore them – in particular, xml:space should not have any effect on the default white space normalization of ONIX metadata.

##### X.5 Datestamp attribute

Enables any data element or composite to carry the date or date and time when it was last updated or confirmed as correct (for example when it is not managed directly within the message sender’s system and the ‘age’ of the data is significantly older than the remainder of the message).

The attribute therefore indicates the currency of the data, not necessarily when it was last changed. If not supplied, there is no default value, and recipients should assume that un-datestamped data is current at the time the message was sent. Data recipients should if necessary identify recently-changed data elements by comparison with any data previously supplied. If used on a composite, the datestamp indicates the most recent date when any individual data element within the composite was updated or confirmed as correct.

The datestamp attribute is particularly useful on frequently-changing data such as price, stock quantities and availability, and in circumstances where an ONIX recipient may receive data from varying sources, in order that they may select the most current data.

  Permitted formats, where ‘T’ and ‘Z’ represent themselves (ie the letters T and Z), and where the symbol ‘±’ represents either ‘+’ or ‘-’ to indicate a timezone offset from UTC.
  YYYYMMDD | Date only
  YYYYMMDDThhmm | Date and time (local time of sender)
  YYYYMMDDThhmmZ | Universal time (UTC) †
  YYYYMMDDThhmm±hhmm | With time zone offset from UTC †
  YYYYMMDDThhmmss | Date and time (with seconds)
  YYYYMMDDThhmmssZ | Universal time (with seconds)
  YYYYMMDDThhmmss±hhmm | With time zone offset from UTC (with seconds)
  | † indicates the preferred formats

  datestamp
  `<CopiesSold datestamp="20100621">6400 copies of this edition sold</CopiesSold>` (Sales figure last confirmed June 2010)
  The calendar date must use the Gregorian calendar, even if other dates within the message use a different calendar. For practical purposes, UTC is the same as GMT.

##### X.6 Sourcename attribute

Enables a data element or composite to carry the name of the source or authority for the data content. This is particularly useful when an ONIX record is issued based on information received from another party (eg a wholesaler passing information received from a publisher or distributor to a retailer). If not supplied, the data authority should be assumed to be the sender of the ONIX message.

  Variable length text, suggested maximum 50 characters
  sourcename
  `<x313 sourcename="XYZ Livres SA">01</x313>` (XYZ is source of information)

##### X.7 Sourcetype attribute

Enables a data element or composite to carry a code indicating the type of source or authority for the data content. This is particularly useful when an ONIX record is issued based on information from another party (eg a wholesaler passing information received from a publisher or distributor to a retailer). If not supplied, the data source should be assumed to be the sender of the ONIX message.

  Fixed length, two digits
  List 3
  sourcetype
  `<x313 sourcetype="01">01</x313>` (Source of information is publisher)

##### X.7a Collation key attribute

Enables a data element to carry the key to be used for sorting, when the sort order is not inherent to the data itself. For example, with Chinese or Japanese contributor names, the collationkey attribute may carry phonetic information required to sort records by contributor.

  Variable length text, suggested maximum 50 characters
  collationkey
  `<b037 collationkey="むらかみはるき">村上春樹</b037>`

##### X.8 Dateformat attribute

Used with a range of date elements to specify the format of the date. Each data element on which this attribute may be used specifies a default dateformat if the attribute is not supplied – for most date elements, this is format ‘00’, YYYYMMDD.

  Fixed length, two digits
  List 55
  dateformat
  `<Date dateformat="03">20104</Date>` (Calendar quarter 4 of 2010)

##### X.9 Language attribute

Enables the language of any text element to be specified when it is not the expected language of the message. The expected language of the message (ie of the metadata) is generally set by agreement between sender and recipient, and is separate from (though usually identical to) the language of the text used within the products described within the message (for the latter, see the <Language> composite in Group P.10 or <DefaultLanguageOfText> in the Message header – though the latter is deprecated).

Many data elements that carry the language attribute are repeatable in order to allow parallel text to be provided in multiple languages. Data recipients able to support only a single language should select the repeat that carries the most appropriate language attribute.

Generally, a language also implies a particular script. (There are a very few languages that are commonly written in more than one script.) However, personal names are not considered to be ‘in’ a particular language, but are commonly transliterated from one script to another, and a limited number of data elements carry the textscript attribute. These may also carry a language attribute in order that distinct transliterations that match the orthography norms of a particular language can be distinguished, cf the Cyrillic name ‘Александр Солженицын’ and the transliterations into Latin script ‘Aleksandr Solzhenitsyn’ (English), and ‘Alexandre Soljenitsyne’ (French).

  Fixed length, three lower-case letters, based on ISO 639-2/B. Note that ISO 639 specifies that these codes should always be in lower-case
  List 74
  language
  `<TitleText language="fre" textcase="01">Les misèrables</TitleText>` (Title is in French [and in sentence case])

Note that ONIX for Books does not use the xml:lang attribute.

##### X.10 Release attribute

From ONIX for Books Release 3.0, identifies the release of the ONIX format standard to which the message conforms. Used only in the top-level element <ONIXMessage> (short tag <ONIXmessage>), and is mandatory. The value will change with each new release, so that all messages will show explicitly the release to which they are intended to conform.

  must be “3.1” for this release
  release
  `<ONIXmessage release="3.1">`

##### X.11 Textcase attribute

Enables the case of the text of a title or subtitle to be specified. If not supplied, the default value is ‘00’, indicating the case is Undefined.

  Fixed length, two digits
  List 14
  textcase
  `<TitleText textcase="03" language="spa">MÉXICO EN LA OBRA DE OCTAVIO PAZ</TitleText>` (Title is all upper case [and in Spanish])

##### X.12 Textformat attribute

Used with a limited range of text elements that are allowed to contain formatted text, to enable the markup format such as XHTML to be specified. If not supplied, the default is ‘06’, indicating the text format is plain text in the character encoding declared in the XML declaration at the top of message, without additional markup. If the XML declaration does not specify a character encoding, the XML default character set should be assumed to be the basic ASCII characters. See the Character sets and special characters section below for further details of how a character encoding declaration is used.

  Fixed length, two digits
  List 34
  textformat
  `<Text textformat="05"><p> … descriptive text … </p></Text>` (Descriptive text contains XHTML markup)

##### X.12a Textscript attribute

Used with a limited range of text elements that are used to provide transliterated alternatives to names within the <AlternativeName> composite, and to titles.

  Fixed length, four letters, based on ISO 15924. Note that ISO 15924 specifies that script codes shall be sent as one upper case followed by three lower case letters
  List 121
  textscript
  `<PersonName textscript="Latn">Daniel Domscheit-Berg</PersonName>`

#### Using ONIX schemas for validation

The main use of the ONIX for Books schemas is for making automated checks of the validity of an ONIX message: does it use the right tags and the right code values in the right place?

Prior to Release 2.1 Revision 02 there was only one official form of schema published by EDItEUR: DTDs, one for each flavor (Reference name and Short tag) of the format. It was a requirement of earlier Releases that every ONIX message used for supply chain communication purposes should include a URL pointing to the reference copy of the appropriate DTD on the EDItEUR website. From Release 2.1 Revision 02 onwards the alternative of using an XSD form of the schema for validation was available, and the DTD link could be omitted, but only by prior arrangement between the parties concerned. The DTD remained the official tool of reference for determining whether or not an ONIX message was valid.

From Release 3.0, the DTD no longer had primary status, and implementers were free to choose between the forms available – for Release 3.0, this was initially DTD, XSD and RNG – according to their own implementation requirements and constraints.

From Release 3.1, DTD schemas are no longer supported, but XSD, RNG and ‘strict’ XSD (using XSD 1.1 and Schematron) forms of schema are available.

The availability of the Release 3.0 and 3.1 schemas in different forms means an increase in the validation options. The XSD and RNG forms are both much more expressive than the DTD form, enabling validation of code values, dates, quantities and link addresses where appropriate. The XSD and RNG forms are also easier for software developers to work with, and are therefore likely to make Releases 3.0 and 3.1 quicker to implement.

For validation of ONIX messages against a Release 3.0 or 3.1 schema EDItEUR recommends that implementers adopt the following approach:

1. Decide which form of schema to use for validation purposes;
2. Download from the EDItEUR website a copy of the selected schema and install this copy in an accessible location on a local server (eg on a corporate intranet or on a stand-alone PC);
   - the local copy of the schema should be updated regularly to incorporate the latest issues of the codelists and any technical improvements in the schema itself;
3. Configure the software tools used for validation purposes to refer to the local copy of the schema.

When using an XSD or RNG schema to validate ONIX messages, an appropriate xmlns namespace attribute is required in the top-level <ONIXMessage> start tag. For this Release, if you are using Reference names, the namespace URI for Release 3.1 should be “http://ns.editeur.org/onix/3.1/reference”. If you are using Short tags, the namespace URI should be “http://ns.editeur.org/onix/3.1/short”. These namespace URIs are the same as those specified within the corresponding ONIX XSD and RNG schemas. For all revisions of Release 3.0, the namespace attribute should include ‘/3.0/’. Note that these URIs do not correspond to an actual web address that is reachable by a browser. They are simply a device for creating an unambiguous reference to the authority for the defined ONIX namespaces. Inclusion of the xmlns attribute in all messages is recommended.

  using Reference names
  `<ONIXMessage release="3.1" xmlns="http://ns.editeur.org/onix/3.1/reference">`

  using Short tags
  `<ONIXmessage release="3.1" xmlns="http://ns.editeur.org/onix/3.1/short">`

When using a DTD (with Release 3.0 only), the namespace attribute is optional. However, a suitable DOCTYPE declaration must be added.

Depending on the software tools used for validation, further changes to this start tag may be necessary. For example, with some validation software it may be necessary to identify within the ONIX message the location of the .xsd file to be used for validation. This location would normally be on a local disc or internal network. The xsi:schemaLocation attribute links the ONIX namespace URI to the .xsd location, and this location would correspond to a real address reachable by a browser (from the machine doing the validation).

  locating the XSD schema on an internal network
  using Reference names
  `<ONIXMessage release="3.1" xmlns="http://ns.editeur.org/onix/3.1/reference" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://ns.editeur.org/onix/3.1/reference http://intranet/onix/ONIX_BookProduct_3.1_reference.xsd">`

  using Short tags
  `<ONIXmessage release="3.1" xmlns="http://ns.editeur.org/onix/3.1/short" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://ns.editeur.org/onix/3.1/short http://intranet/onix/ONIX_BookProduct_3.1_short.xsd">`

  The intranet location would be different for each organization’s validation scenario.

Any link to a local copy of the relevant schema that has been added to an ONIX message by a sender for validation purposes – for example the xsi:schemaLocation attribute or any DOCTYPE declaration – must be removed prior to making the ONIX message available to supply chain partners. They will make their own arrangements for validation of incoming messages to suit their own internal systems. Note that the xmlns namespace attribute need not be removed.

#### Character sets and special characters

In principle, XML data files may include any Unicode character with the exception of control codes other than tab, line feed and return, and the default encoding is either UTF‑8 or UTF‑16. In practice, unless the XML declaration at the beginning of the ONIX message includes an explicit ‘encoding declaration’, you should restrict the character set to the printable characters of ASCII (ie those characters whose Unicode numbers fall between 32 and 126 inclusive). This limited character set is unlikely to be adequate for anything except the most basic data in English, so it is expected that most – and outside of the English language markets, all – ONIX messages will include an encoding declaration or other special coding of non-ASCII characters described in the Extended character sets and encoding declarations section below.

For reference, here is a list of the basic character set for which no special coding is necessary, all of which can be found on a standard English computer keyboard:

- space character
- capital letters A–Z
- lower-case letters a–z
- digits 0–9
- punctuation ! " ' , - . : ; ?
- brackets ( ) [ ] { }
- symbols # $ % * + / = > \ @ _ ` | ~

The tab, line feed and carriage return characters are also allowed, but most XML software will treat them as spaces. Other ‘control characters’ (non-printing characters with an ASCII code number below 32) are not allowed.

This set deliberately does not include the characters ‘&’ and ‘<’. These characters have special significance in all XML applications, and therefore cannot be used as text characters in any ONIX data elements (or in attribute values). If you need to include either of these ‘reserved characters’ within a data element (for example in the name of an organization such as ‘AT&T’ that by convention uses ‘&’ rather than ‘and’, or as a part of a URI that includes multiple query parameters such as https://www.booktees.org?​color=yellow&size=large), you must use the XML character entity reference form of expression in place of the ‘&’ or ‘<’:

  entity | represents
  --- | ---
  `&amp;` | &
  `&lt;` | <

  `<CorporateName>AT&amp;T</CorporateName>`
  `<WebsiteLink>https://www.booktees.org?​color=yellow&amp;size=large</WebsiteLink>`

You may also use character entity references in place of the following characters, although these entities are not generally used in ONIX:

  entity | represents
  --- | ---
  `&quot;` | "
  `&apos;` | '
  `&gt;` | >

Beyond these five, character entity references are not valid in ONIX 3.1 or 3.0.

This replacement of the characters &, <, ", ' and > does not apply within XML ‘CDATA sections’.

ONIX for Books markup (XML element and composite names, attribute names, and code values drawn from the ONIX codelists) is limited to this basic set of ASCII characters, plus the literal ‘&’ and ‘<’ symbols.

Note that the currency symbols ‘£’, ‘¥’ and ‘€’ (the Pound Sterling, Yen and Euro symbols) are not in the basic set, nor are there standard character entity references that may be used in their stead. En and em rules, ellipsis and bullet characters, accented and other uncommon characters are also missing from the basic set. Note also that some office applications insert so-called ‘smart’ apostrophes and quotation marks (single or double, open or closed), and these too are not in the basic set.

If your ONIX message contains no characters beyond this basic set, then no special coding is necessary. However, without special precautions, if your ONIX message contains even a single character beyond this basic set, there is a significant risk that a recipient will reject your ONIX because it contains invalid text. This is because XML without a character encoding declaration will be assumed to use the UTF‑8 encoding – and even one extended character, for example from the common Latin‑1 or Windows-1252 character sets, is likely to cause a UTF‑8 text error.

##### X.13 Extended character sets and encoding declarations

If the basic ASCII character set is not adequate – and in most cases it will not be – there are two ways to incorporate non-ASCII characters into your ONIX data: either use Unicode numerical character references, or use an encoding declaration.

Numerical character references take the form defined in Section 4.1 of the XML 1.0 Recommendation. For example, the character ‘ž’ (z háček or z caron, used in Czech and some other languages) can be expressed as ‘&#382;’ or ‘&#x017e;’ where 382 and 017e are the Unicode character numbers in decimal and hexadecimal (base 16 numbers) respectively. In principle, any Unicode character can be included in ONIX data this way.

  using a decimal character reference – é is character 233
  `<TitleText>Les Mis&#233;rables</TitleText>` (Les Misérables)

  using a hexadecimal character reference – é is character e9
  `<TitleText>Les Mis&#xe9;rables</TitleText>` (Les Misérables)

  Character references between &#127; and &#159; (or between &#x7f; and &#x9f; in hexadecimal) should never be used. In Unicode, these are control codes. It is a common error to use these numbers (eg &#158; or &#x9e; for ‘ž’), since they are valid character numbers in the Windows‑1252 character set, and they often appear to work in web browsers, but they are strongly discouraged in XML applications.

If you have a relatively small number of non-ASCII characters in your ONIX data, this approach using numerical character references might well be suitable. But beware: as above, in the absence of an encoding declaration, even a single character that is not in the basic ASCII set and not encoded into a numerical character reference can cause a text validation error.

If your ONIX data is not primarily in English, or if you make extensive use of extended characters even in English text, then it is likely to be simpler to use a message-wide encoding declaration. This must be included in the XML declaration at the beginning of the ONIX message.

  `<?xml version="1.0" encoding="ISO-8859-1"?>` (message uses ISO Latin‑1 character set and encoding)
  `<?xml version="1.0" encoding="Windows-1252"?>` (message uses Windows‑1252 character set and encoding)
  `<?xml version="1.0" encoding="ISO-8859-15"?>` (message uses ISO Latin‑9 character set and encoding)

Declaring the ISO Latin‑1 character set with ISO‑8859‑1 encoding allows characters and diacritics used in most Western European languages to be included in the ONIX message without any special encoding, as well as some other extended characters. However, note that Latin‑1 does not include a ‘€’ symbol (Latin‑9 – also known as ISO‑8859‑15 – is an alternative character set that does), nor does it contain smart quotes (“ ” and ‘ ’), en and em dashes or the ellipsis character. Local circumstances may favor the use of other character sets and encodings, such as any of Parts 2 through 16 of ISO 8859, the common Windows‑1252 (which is likely to be used by many older Windows-based applications in North America and Western Europe, and which does include smart quotes, en and em dashes and the ellipsis), or various Asian language encodings such as Shift-JIS.

Alternatively, a Unicode encoding like UTF‑8 or -16 can include characters from any and all of these character sets. Despite the fact that UTF‑8, UTF‑16BE or UTF‑16LE are the ‘default’ character encodings used in all XML applications, it is strongly recommended that they are declared explicitly when used in an ONIX for Books message. A byte order mark should not be included in UTF encodings. EDItEUR recommends the use of UTF‑8 encoding in ONIX messages that will be exchanged outside a particular national market.

  `<?xml version="1.0" encoding="UTF-8"?>` (UTF‑8 encoding, Unicode character set)

Using a suitable message-wide encoding means that no special encoding needs to be used for individual non-ASCII characters, making it straightforward to include metadata in any language.

  `<Text>« Je viens détruire la fatalité humaine, écrit Hugo, je condamne l’esclavage, je chasse la misère, j’enseigne l’ignorance, je traite la maladie, j’éclaire la nuit, je hais la haine. Voilà ce que je suis et voilà pourquoi j’ai fait Les Misérables. »</Text>`
  Note that the French text above includes ‘non-breaking spaces’ adjacent to the guillemet quotation marks, as well as several non-ASCII apostrophes and vowels with diacritical marks (accents).

This applies equally to languages that use a Latin-based script, such as French above, and to languages that use other scripts:

  data in Cyrillic script
  `<PersonNameInverted>Достоевский, Фёдор</PersonNameInverted>` (Fyodor Dostoyevsky)

  data in simplified Chinese script
  `<PersonName>刘慈欣</PersonName>` (Liú Cíxīn)

  right-to-left reading data in Arabic script
  `<TitleText>عمارة يعقوبيان</TitleText>` (Imārat Yaʿqūbīān)
  `1--------> <··············2 3--------->`

Note that for Arabic, as above, and other scripts normally rendered right-to-left, the order of characters in the message follows the logical reading order for each script (as indicated by the arrows): that is, the letters ain and meem forming the first syllable of the book title (the ‘Im’ in ‘Imārat’) immediately follow the <TitleText> start tag in the message data, even though they are displayed right to left, starting adjacent to the </TitleText> end tag, and the last Arabic character, the letter noon (the ‘n’ in ‘Yaʿqūbīān’), is followed immediately by the end tag, even though it is displayed adjacent to the start tag.

Whichever encoding is declared, ONIX implementers need to ensure the character set and encoding are controlled throughout the process of creating the ONIX data, so that data that is declared as being, say, ISO‑8859‑1, really is encoded as ISO‑8859‑1 and does not include any characters that are not present in the Latin‑1 character set: simple cutting and pasting text from a variety of sources, for example, is likely to introduce character encoding inconsistencies (a character would be understood by the recipient as some different character entirely) and may even result in completely invalid text. Software used to create XML with a rich character set needs careful configuration.

The two methods of incorporating non-ASCII characters can be combined: if your message uses the ISO Latin‑1 character set and ISO‑8859‑1 encoding, it can include characters such as é, ø or £ ‘natively’. And although Latin‑1 does not include the ‘ž’ character, it can still be included in your data using the numerical character reference ‘&#382;’ (or the hexadecimal equivalent ‘&#x017e;’). In contrast, if you use UTF‑8, no numerical character references are necessary – effectively all characters can be included ‘natively’.

Implementers should note that it is not a requirement that recipients of ONIX messages should be able to handle correctly any character encodings other than ASCII, but supporting at least UTF‑8 as an encoding is very strongly recommended. Equally, it is not a requirement for recipients to support any characters beyond the basic ASCII set, but in practice it is expected that recipients support the characters used in the commonly-used languages and scripts in their area of operation. For further technical guidance on character encodings in XML see Section 4.3.3 of the XML 1.0 Recommendation.

In earlier releases of ONIX for Books it was recommended that named HTML character entity references be used in preference to numerical character references, and these were supported by the inclusion of special named entities such as ‘&ouml;’, ‘&hellip;’ or ‘&ndash;’ in the ONIX for Books DTD. This recommendation no longer applies, and character entity references other than the five mandatory entities required for XML (&amp;, &lt;, &gt;, &apos; and &quot;) are not supported in either ONIX 3.0 or 3.1. Special characters that are not available in the character set and encoding used for the message may only be represented by numerical character references (ie an ellipsis may be included as ‘&#8230;’ or ‘&#x2026;’, where in previous ONIX versions, ‘&hellip;’ could have been used).

For textual data in an East Asian writing system which uses text glosses (for example Chinese or Japanese), glosses should be incorporated in one of two ways. In ONIX text fields that allow the inclusion of XHTML or HTML markup (see below), glosses should be incorporated using the (X)HTML <ruby> tag. In ONIX text fields that do not allow inclusion of XHTML or HTML markup, Unicode’s interlinear annotation delimiters (numerical character references &#xfff9;–&#xfffb;) may be used to delimit the gloss.

  data in Japanese kanji script, including hiragana gloss
  `<PersonNameInverted>&#xfff9;村上春樹&#xfffa;むらかみ はるき&#xfffb;</PersonNameInverted>` (Haruki Murakami)

  This should typically be displayed as 村上 春樹むらかみ はるき. Note that the interlinear annotation delimiters do not need to be included as numerical character references – they can be ‘native’ characters if the character encoding allows – but numerical references are used here for clarity because the characters are otherwise invisible. If a recipient application cannot properly process the interlinear annotations, then &#xfff9; should be ignored, and &#xfffa; should be replaced with ‘ (’ and &#xfffb with ‘) ’ for display purposes.

#### Using XHTML, HTML, XML, JSON within ONIX text fields

Given the frequent requirement for ONIX messages to convey rich product information in a form suitable for use in web pages, guidance is provided below on how to incorporate content intended for use on the web – or any other text with XHTML or HTML markup – in an ONIX Product record. However, in order to apply this guidance correctly, a user must already have some knowledge of different forms of web content. Those already familiar with the differences between HTML and XHTML may skip this section.

Web content that is largely text-based is generally styled for presentation in a web page using the HyperText Markup Language (HTML). HTML has been the language of the World Wide Web since its inception and is still the most popular language for constructing web pages. HTML was based upon the Standard Generalized Markup Language (SGML), which has been in use for preparing electronic content in academic and professional publishing since the early 1990s.

XML was developed in the late 1990s as demand grew for ways to use the web for exchanging data and messages that didn’t have to be presented as human-readable web pages. XML is a much stricter language than SGML, so it is generally not possible to incorporate HTML-tagged content directly into an XML message. Responding to demand to make it possible to embed HTML in XML, the World Wide Web Consortium has defined an XML-compatible version of HTML, called XHTML. XHTML text fragments can be embedded in XML messages, provided this is allowed by the tagging rules of the XML application.

The tagging rules of ONIX specify that XHTML text fragments may be embedded in certain ONIX data elements, but within very strict constraints. These constraints are set out in section X.14 below, along with a list of the appropriate data elements.

HTML text fragments – and indeed any fragment of tagged text, regardless of the tagging language – can also be embedded in ONIX data elements, but only by using XML techniques that ‘hide’ these fragments from any XML-aware software that is processing the ONIX message. Two such methods for embedding HTML or other tagged text in an ONIX data element are described in section X.15 below. These methods are available by default in all XML applications, and cannot be prohibited in ONIX applications, but their use is strongly discouraged. All ONIX users are encouraged to convert HTML text fragments to be valid XHTML fragments before incorporating them in ONIX messages. In any event, these methods should only be used in, and HTML should only be embedded in, the ONIX data elements that may also be used with XHTML (and which are listed below). The range of HTML tags and attributes used should be restricted in the same way as the usable XHTML tags.

Note that where an ONIX data element containing text with markup has a suggested or a fixed character length limit, for example, the length of <Text> with <TextType> code 02 within Group P.14 – a short description or annotation which is strictly limited to 350 characters – this length does not count the characters of any HTML or XHTML markup that is included within <Text>. Note also that suggested or fixed length limits count characters, not bytes of data or Unicode codepoints. This means that the specified maximum length of the data is independent of the way that it is encoded in the ONIX – and that the amount of storage space required in bytes depends on both the encoding method and the presence of any markup.

##### X.14 Using XHTML (Version 1.0 or 1.1)

The ONIX Product Information Message DTD and the XSD and RNG schemas enable the inclusion of XHTML-tagged text within specific data elements where this has been deemed appropriate. This is, for example, the expected way to include multiple paragraphs of text in long descriptive data. In these cases the data element may contain any well-formed fragment of XHTML-tagged text – the allowed set of tags is based around XHTML 1.1 with the following restrictions:

1. It must be the case that, if the fragment were to be placed in an otherwise empty <body> element in an XHTML document, the resulting document would be valid. Ideally, all text within the fragment should be enclosed in block-level XHTML tags (for example <p> or <ul>);
2. The fragment may not include any XHTML forms, embedded objects, or script or document revision elements;
3. The fragment may not use ‘event’ attributes and others that may affect browser behavior;
4. The fragment may not include special character named character entity references (other than the five available to all XML applications, where literal <, >, ', " and & characters occur in the XHTML text content. Note these entities should not be used to replace XHTML markup).

The intention of the first three of these restrictions is to prevent the unwitting or malicious transmittal of viruses in ONIX messages. The intention of the fourth of these restrictions is to enable validation of ONIX for Books messages against any of the three schema formats in which the ONIX for Books schemas are available.

If the XHTML markup complies with these restrictions, then it can be included without any special coding – other than the required textformat attribute – within the ONIX data elements below.

Note that some ONIX recipients may be reluctant to use XHTML text that contains links, images, tables, or that uses attributes such as style. Therefore, although a wide range of tags is allowed, it is strongly recommended that XHTML tags are limited to the following set:

- <p>
- <strong>
- <ul>
- <sub>
- <dl>
- <ruby>
- <br />
- <em>
- <ol>
- <sup>
- <dt>
- <rp>
- <b>
- <li>
- <dd>
- <rb>
- <i>
- <rt>
- <cite>

Use of XHTML attributes should be limited to the type and start attributes to control bullets and list item numbering with the <ol> tag used for ordered lists.

The data elements within which XHTML markup may be used are:

- <AncillaryContentDescription>
- <AudienceDescription>
- <BiographicalNote>
- <BookClubAdoption>
- <CitationNote>
- <CopiesSold>
- <ContributorDescription>
- <ContributorStatement>
- <CopyrightStatementText>
- <EditionStatement>
- <EventDescription>
- <FeatureNote>
- <IllustrationsNote>
- <InitialPrintRun>
- <MarketPublishingStatusNote>
- <PrizeJury>
- <PrizeStatement>
- <PromotionCampaign>
- <PublishingStatusNote>
- <ReligiousTextFeatureDescription>
- <ReprintDetail>
- <SalesRestrictionNote>
- <Text>
- <TextSourceDescription>
- <TitleStatement>
- <VenueNote>
- <WebsiteDescription>

The use of XHTML tags within any of these data elements should be signaled by including the textformat attribute with value ‘05’ in the start tag of the data element in question:

  using Reference names
  `<Text textformat="05"><p>XHTML-tagged text…</p><p>…may be multiple paragraphs.</p></Text>`

  using Short tags
  `<d104 textformat="05"><p>XHTML-tagged text…</p><p>…may be multiple paragraphs.</p></d104>`

Note that XHTML tags such as <p> or <strong> must be properly closed, correctly nested, and must be lower case. It may be useful with self-closing elements such as <br/> to use the modified form <br /> – the extra space character makes no significant difference in XHTML, but improves compatibility if the XHTML is inadvertently used by the recipient in an HTML context.

For XHTML textual data in an East Asian writing system which uses text glosses (for example, Chinese or Japanese), the <ruby> tag should be used. Both ‘simple’ and ‘complex’ ruby from XHTML 1.1 (see https://www.w3.org/TR/ruby/) are supported by the ONIX for Books schemas, though browser support for complex ruby is not universal. Note that XHTML markup must not be mixed with Unicode interlinear annotation delimiters within a single data element.

Most of the XHTML-enabled data elements listed above are also repeatable, to provide parallel text in multiple languages. (<TitleStatement> appears to be an exception, but it may be repeated per language using a separate <TitleDetail> composite.) In contrast, the following data elements are repeatable for multiple languages, but are not XHTML-enabled:

- <AwardingBody>
- <CorporateName>
- <CorporateNameInverted>
- <DeletionText>
- <EpubLicenseName>
- <EventAcronym>
- <EventPlace>
- <EventName>
- <EventTheme>
- <ListName>
- <LocationName>
- <MessageNote>
- <PricePartDescription>
- <PriceTypeDescription>
- <ProductFormDescription>
- <ProductFormFeatureDescription>
- <ProfessionalPosition>
- <RatingUnits>
- <ReturnsNote>
- <SourceTitle>
- <SubjectHeadingText>
- <WebsiteLink>

##### X.15 Using HTML (Version 4.01 or earlier), and other XML

The inclusion of text tagged in accordance with HTML version 4.01 or earlier in an ONIX data element is possible using one of two methods described below, but use of either method is strongly discouraged – if possible, use XHTML instead. In the event that HTML is included, in either of these ways, it may only be included in the elements listed in X.14 above, and the textformat attribute on the start tag for the element should be specified with the value ‘02’ (HTML, other than XHTML). It is strongly recommended that the range of HTML tags is limited to the small set listed for XHTML above (<p>, <br />, <strong> etc).

XML-tagged text (using a non-ONIX XML schema) can be included in the same selection of ONIX data elements, using the same two methods. ONIX data elements containing such XML-tagged text should use the textformat attribute with value ‘03’ (XML). Non-ONIX XML used within individual ONIX data fields may be an option for ONIX that remains strictly internal to an organization, for example for transfer of data between IT systems within an organization, but note that this makes the data much less interoperable in the broader metadata supply chain. Thus the textformat attribute with code 03 should never appear in ONIX exchanged with other organizations.

To embed HTML or XML (other than XHTML) in an ONIX data element, either:

1. Replace the ‘<’ character at the start of every HTML or XML start and end tag with its entity reference ‘&lt;’, or
2. Enclose the entire content of the data element within an XML ‘CDATA section’ (see Section 2.7 of the W3C’s XML 1.0 Recommendation for details of this).

In general, method 2 using CDATA is strongly preferred to method 1.

Note: using embedded HTML markup with either method presents significant difficulties for data senders and recipients who process the ONIX data using XSLT. Any named character entities encapsulated within CDATA will make the ONIX invalid after processing, since XSLT processing cannot output ONIX using method 2: conversion to numerical character references or native characters is required. And for method 1, special precautions need to be taken to avoid double-escaping of & or other named character entities or numerical character references after XSLT processing. Using XHTML as described in X.14 is strongly recommended as it avoids these issues.

  HTML method 1 – replace < in HTML markup with &lt;
  using Reference names
  `<Text textformat="02">&lt;P>Maj Sjöwall is best known for the &lt;I>Martin Beck&lt;/I> novels.&lt;/P></Text>`

  using Short tags (illustrating double-escaping issue)
  `<d104 textformat="02">&lt;P>Maj Sj&amp;#246;wall is best known for the &lt;I>Martin Beck&lt;/I> novels.&lt;/P></d104>`

  Note that upper case HTML tags are used here, to make it clear that the markup is HTML and not XHTML. In real-world HTML markup, lower case tags are generally preferred for improved compatibility.
  With HTML markup, only the < character should be changed. In HTML, some end tags such as </P> are optional. Note the use of a ‘double-escaped’ numerical character reference instead of native character ‘ö’ or the character reference &#246; in the Short tags example – this double escaping is strongly discouraged. Use just &#246; without double-escaping, instead of &amp;#246;. (And to avoid doubt, this means that if an & character is intended to appear in the final rendered HTML, it should be included in the ONIX data as &amp;, not as &amp;amp;.) Using this method, there may be issues when the < character is intended to appear in the final rendered HTML, and using the numerical character reference &#60; may help avoid these issues.

  HTML method 2 – encapsulate HTML in <![CDATA[ … ]]>
  using Reference names
  `<Text textformat="02"><![CDATA[<P>Maj Sjöwall is best known for the <I>Martin Beck</I> novels.]]></Text>`

  using Short tags (illustrating use of named character entity)
  `<d104 textformat="02"><![CDATA[<P>Maj Sj&ouml;wall is best known for the <I>Martin Beck</I> novels.]]></d104>`

  No special treatment of the < character in markup is necessary. Note the use of a named character entity &ouml; instead of native character ‘ö’. Since text within CDATA is not parsed by the recipient XML system, this may work, even though named character entities are not allowed within parsed ONIX data. However, if extended characters are incorporated into HTML using a named character entity or numerical character reference, special attention should be paid to those characters during testing of the ONIX data exchange. Note also that for the example HTML above, upper case tags are used only to make it clear the markup is HTML and not XHTML – upper case is allowed but not encouraged for HTML, whereas XHTML tags must be lower case.

  XML method 1 – replace < in XML markup with &lt;
  using Reference names
  `<Text textformat="03">&lt;para>XML-tagged paragraph with &lt;emph>emphasized&lt;/emph> text&lt;/para></Text>`

  using Short tags
  `<d104 textformat="03">&lt;para>XML-tagged paragraph with &lt;emph>emphasized&lt;/emph> words.&lt;/para></d104>`

  XML method 2 – encapsulate XML in <![CDATA[ … ]]>
  using Reference names
  `<Text textformat="03"><![CDATA[<para>XML-tagged paragraph with <emph>emphasized</emph> words.</para>]]></Text>`

  using Short tags
  `<d104 textformat="03"><![CDATA[<para>XML-tagged paragraph with <emph>emphasized</emph> words.</para>]]></d104>`

Note that the validity of the HTML or XML markup cannot be checked via the ONIX schemas, since with either method, the markup is effectively ‘hidden’ from the validation process.

The use of CDATA for anything other than inclusion of HTML or XML-tagged text should be avoided. In particular, note that XHTML should use the method outlined in X.14.

##### X.16 Using HTML5

HTML5 can be embedded using either method for HTML 4.

Note that in HTML5, void elements such as <br> (for a line break) should ideally be used without a closing / character. In contrast, in XHTML5 (the XML serialization of HTML5), void elements must include the closing /.

XHTML5 may be embedded using the method for XHTML 1.0 and 1.1, provided that in addition to the rules that apply to all XHTML, new elements introduced only in XHTML5 are avoided – for example <article> or <section>. Some new elements may be allowed in a future version of the XHTML subset. A full list of allowed and disallowed elements is given in the Guide.

##### X.17 Using JSON-LD

One data element in ONIX allows the embedding of JSON-LD data – specifically the <Text> data element in Group P.14, and only when <TextType> indicates the text is a JSON-LD snippet (eg using code 24).

Each JSON-LD snippet should be enclosed in braces (that is, the { and } characters), and must begin with the @context and @type attributes required by JSON-LD.

Note that JSON requires the use of Unicode, so embedding JSON-LD within ONIX requires a Unicode encoding is used for the entire ONIX message (ie encoding="UTF‑8" or similar in the XML declaration of the file – see X.13). The textformat attribute of the ONIX data element containing the JSON-LD data should be omitted (ie it should default to the overall text encoding of the message).

  Embedding JSON-LD in <Text>
  using Reference names (and formatted for clarity)
  `<TextContent>`
  `<TextType>24<TextType>`
  `<ContentAudience>09</ContentAudience>`
  `<Text> { "@context" : "http://schema.org/", "@type" : "Audiobook", "name" : "Burley Cross Postbox Theft" } </Text>`
  `</TextContent>`

  using short tags
  `<textcontent>`
  `<x426>24<x426>`
  `<x427>09</x427>`
  `<d104>{"@context":"http://schema.org/","@type":"Audiobook","name":"Burley Cross Postbox Theft"}</d104>`
  `</textcontent>`

  Note that any ampersand in the JSON-LD data must be replaced by &amp; when the JSON is embedded inside an XML data element, and when extracted, it must be converted back to a plain ampersand before it’s used as JSON data.

## ONIX for Books Message header

### Header composite

A group of data elements which together constitute a message header. Mandatory in any ONIX for Books message to provide metadata about the message itself, and non-repeating.

  Header
  header
  1

##### Sender composite

A group of data elements which together specify the sender of an ONIX for Books message. Mandatory in any ONIX for Books message, and non-repeating.

  Sender
  sender
  1

##### Sender identifier composite

A group of data elements which together define an identifier of the sender. The composite is optional, and repeatable if more than one identifier of different types is sent; but either a <SenderName> or a <SenderIdentifier> must be included.

  SenderIdentifier
  senderidentifier
  0…n

##### H.1 Sender identifier type

An ONIX code identifying a scheme from which an identifier in the <IDValue> element is taken. Mandatory in each occurrence of the <SenderIdentifier> composite, and non-repeating.

  Fixed length, two digits
  List 44
  SenderIDType
  m379
  1
  `<m379>01</m379>`

##### H.2 Identifier type name

A name which identifies a proprietary identifier scheme (ie a scheme which is not a standard and for which there is no individual ID type code). Must be included when, and only when, the code in the <SenderIDType> element indicates a proprietary scheme. Optional and non-repeating.

  Variable length text, suggested maximum 100 characters
  IDTypeName
  b233
  0…1
  language
  ``

##### H.3 Identifier value

An identifier of the type specified in the <SenderIDType> element. Mandatory in each occurrence of the <SenderIdentifier> composite, and non-repeating.

  According to the identifier type specified in <SenderIDType>
  IDValue
  b244
  1
  ``

##### End of Sender identifier composite

##### H.4 Sender name

The name of the sender organization, which should always be stated in a standard form agreed with the addressee. Optional and non-repeating, but either a <SenderName> element or a <SenderIdentifier> composite must be included.

  Variable length text, suggested maximum 50 characters
  SenderName
  x298
  0…1
  `<SenderName>HarperCollins London</SenderName>`

##### H.5 Sender contact name

Free text giving the name, department, etc for a contact person in the sender organization who is responsible for the content of the message. Optional and non-repeating.

  Variable length text, suggested maximum 300 characters
  ContactName
  x299
  0…1
  `<x299>Jackie Brown</x299>`

##### H.5a Sender telephone number

A telephone number of the contact person in the sender organization, wherever possible including the plus sign and the international dialing code. Optional, and non-repeating.

  Variable length text, suggested maximum length 20 characters
  TelephoneNumber
  j270
  0…1
  `<j270>+44 20 8843 8607</j270>`

##### H.6 Sender contact e‑mail address

A text field giving the e‑mail address for a contact person in the sender organization who is responsible for the content of the message. Optional and non-repeating.

  Variable length text, suggested maximum 100 characters
  EmailAddress
  j272
  0…1
  `<j272>jackie.brown@bigpublisher.co.uk</j272>`

##### End of Sender composite

##### Addressee composite

A group of data elements which together specify the addressee of an ONIX for Books message. Optional, and repeatable if there are several addressees.

  Addressee
  addressee
  0…n

##### Addressee identifier composite

A group of data elements which together define an identifier of the addressee. The composite is optional, and repeatable if more than one identifier of different types for the same addressee is sent; but either an <AddresseeName> or an <AddresseeIdentifier> must be included.

  AddresseeIdentifier
  addresseeidentifier
  0…n

##### H.7 Addressee identifier type

An ONIX code identifying a scheme from which an identifier in the <IDValue> element is taken. Mandatory in each occurrence of the <AddresseeIdentifier> composite, and non-repeating.

  Fixed length, two digits
  List 44
  AddresseeIDType
  m380
  1
  `<AddresseeIDType>02</AddresseeIDType>`

##### H.8 Identifier type name

A name which identifies a proprietary identifier scheme (ie a scheme which is not a standard and for which there is no individual ID type code). Must be included when, and only when, the code in the <AddresseeIDType> element indicates a proprietary scheme. Optional and non-repeating.

  Variable length text, suggested maximum 100 characters
  IDTypeName
  b233
  0…1
  language
  `<b233>BigPublisher Customer ID</b233>`

##### H.9 Identifier value

An identifier of the type specified in the <AddresseeIDType> element. Mandatory in each occurrence of the <AddresseeIdentifier> composite, and non-repeating.

  According to the identifier type specified in <AddresseeIDType>
  IDValue
  b244
  1

##### End of Addressee identifier composite

##### H.10 Addressee name

The name of the addressee organization, which should always be stated in a standard form agreed with the addressee. Optional and non-repeating; but either a <AddresseeName> element or a <AddresseeIdentifier> composite must be included.

  Variable length text, suggested maximum 50 characters
  AddresseeName
  x300
  0…1
  `<x300>BiblioAggregator Ltd</x300>`

##### H.11 Addressee contact name

Free text giving the name, department, etc for a contact person in the addressee organization to whom the message is to be directed. Optional and non-repeating.

  Variable length text, suggested maximum 300 characters
  ContactName
  x299
  0…1
  `<ContactName>Mel Carter</ContactName>`

##### H.11a Addressee telephone number

A telephone number of the contact person in the addressee organization, wherever possible including the plus sign and the international dialing code. Optional, and non-repeating.

  Variable length text, suggested maximum length 20 characters
  TelephoneNumber
  j270
  0…1
  `<TelephoneNumber>+44 1632 457890</TelephoneNumber>`

##### H.12 Addressee contact e‑mail address

A text field giving the e‑mail address for a contact person in the addressee organization. Optional and non-repeating.

  Variable length text, suggested maximum 100 characters
  EmailAddress
  j272
  0…1
  `<j272>carterm@aggregator.co.uk</j272>`

##### End of Addressee composite

##### H.13 Message sequence number

A monotonic sequence number of the messages in a series sent between trading partners, to enable the receiver to check against gaps and duplicates. Optional and non-repeating.

  Positive integer, suggested maximum length 8 digits
  MessageNumber
  m180
  0…1
  `<m180>1234</m180>`

##### H.14 Message repeat number

A number which distinguishes any repeat transmissions of a message. If this element is used, the original is numbered 1 and repeats are numbered 2, 3 etc. Optional and non-repeating.

  Positive integer, suggested maximum length 4 digits
  MessageRepeat
  m181
  0…1
  `<m181>2</m181>`

##### H.15 Message creation date/time

The date on which the message is sent. Optionally, the time may be added, using the 24-hour clock, with an explicit indication of the time zone if required, in a format based on ISO 8601. Mandatory and non-repeating.

  Permitted formats, where ‘T’ and ‘Z’ represent themselves (ie the letters T and Z), and where the symbol ‘±’ represents either ‘+’ or ‘-’ to indicate a timezone offset from UTC.
  YYYYMMDD | Date only
  YYYYMMDDThhmm | Date and time (local time of sender)
  YYYYMMDDThhmmZ | Universal time (UTC) †
  YYYYMMDDThhmm±hhmm | With time zone offset from UTC †
  YYYYMMDDThhmmss | Date and time (with seconds)
  YYYYMMDDThhmmssZ | Universal time (with seconds)
  YYYYMMDDThhmmss±hhmm | With time zone offset from UTC (with seconds)
  | † indicates the preferred formats

  SentDateTime
  x307
  1
  `<x307>20100522T1230Z</x307>` (12.30pm UTC, 22 May 2010)
  The calendar date must use the Gregorian calendar, even if other dates within the message use a different calendar. For all practical purposes, UTC is the same as GMT.

##### H.16 Message note

Free text giving additional information about the message. Optional, and repeatable in order to provide a note in multiple languages. The language attribute is optional for a single instance of <MessageNote>, but must be included in each instance if <MessageNote> is repeated.

  Variable length text, suggested maximum 500 characters
  MessageNote
  m183
  0…n
  language
  `<MessageNote>Updates for titles to be published September 2009</MessageNote>`

##### H.17 Default language of text

An ONIX code indicating the default language which is assumed for the text content of products listed in the message, unless the language is explicitly stated by sending a ‘language of text’ in Group P.10 of each Product record. Optional and non-repeating. To avoid any possible ambiguity, use of this default is deprecated, but any default supplied will be assumed for all Product records which do not specify the language of the text explicitly in Group P.10. It is strongly recommended that the language of the text should be specified in the <Language> composite for each product.

  Fixed length, three lower-case letters, based on ISO 639-2/B. Note that ISO 639 specifies that these codes should always be in lower-case
  List 74
  DefaultLanguageOfText
  m184
  0…1
  `<m184>eng</m184>`

##### H.18 Default price type

An ONIX code indicating the default price type which is assumed for prices of products listed in the message, unless the Price type is explicitly stated by sending a Price type code in each <Price> composite for each Product record. Optional and non-repeating. To avoid any possible ambiguity, use of this default is deprecated, but any default supplied will be assumed for all prices in Group P.26 which do not specify the Price type explicitly. It is strongly recommended that the price type should be specified in the <Price> composite for each individual price.

  Fixed length, two digits
  List 58
  DefaultPriceType
  x310
  0…1
  `<x310>01</x310>`

##### H.19 Default currency

An ONIX code indicating the default currency which is assumed for prices of products listed in the message, unless the Currency code is explicitly stated by sending a Currency code in each <Price> composite for each Product record. Optional and non-repeating. To avoid any possible ambiguity, use of this default is deprecated, but any default supplied will be assumed for all prices in Group P.26 which do not specify the Currency code explicitly. It is strongly recommended that the Currency code should be specified in the <Price> composite for each individual price.

  Fixed length, three letters, based on ISO 4217. Note that ISO 4217 specifies that currency codes shall be sent as upper case only
  List 96
  DefaultCurrencyCode
  m186
  0…1
  `<DefaultCurrencyCode>USD</DefaultCurrencyCode>`

### End of Header composite

  a simple <Header> composite
  using Reference names |
  --- | ---
  `<Header>` |
  `<Sender>` |
  `<SenderIdentifier>` |
  `<SenderIDType>06</SenderIDType>` |
  `<IDValue>0614141800001</IDValue>` |
  `</SenderIdentifier>` |
  `<SenderName>XYZ Publishers</SenderName>` |
  `<ContactName>Jane Smith</ContactName>` |
  `<TelephoneNumber>+1 212 555 0123</TelephoneNumber>` |
  `<EmailAddress>jane.smith@xyzbooks.com</EmailAddress>` |
  `</Sender>` |
  `<Addressee>` |
  `<AddresseeName>Cooks Books</AddresseeName>` |
  `</Addressee>` |
  `<MessageNumber>781</MessageNumber>` |
  `<SentDateTime>20090408T0750-0500</SentDateTime>` |
  `<MessageNote>New cookery titles for May 2009</MessageNote>` |
  `<DefaultLanguageOfText>eng</DefaultLanguageOfText>` |
  `</Header>` |

  using Short tags |
  --- | ---
  `<header>` |
  `<sender>` |
  `<senderidentifier>` |
  `<m379>06</m379>` | GLN
  `<b244>0614141800001</b244>` |
  `</senderidentifier>` |
  `<x298>XYZ Publishers</x298>` |
  `<x299>Jane Smith</x299>` |
  `<j270>+1 212 555 0123</j270>` |
  `<j272>jane.smith@xyzbooks.com</j272>` |
  `</sender>` |
  `<addressee>` |
  `<x300>Cooks Books</x300>` |
  `</addressee>` |
  `<m180>781</m180>` |
  `<x307>20090408T0750-0500</x307>` | 12:50pm UTC
  `<m183>New cookery titles for May 2009</m183>` |
  `<m184>eng</m184>` | Is deprecated
  `</header>` |

## ONIX for Books Product record

Every ONIX message must contain either one or more <Product> composites or a single <NoProduct/> empty element.

### Product composite

A product is described by a group of data elements beginning with an XML label <Product> and ending with an XML label </Product>. The entire group of data elements which is enclosed between these two labels constitutes an ONIX Product record. The Product record is the fundamental unit within an ONIX Product Information message. In almost every case, each Product record describes an individually tradable item; and in all circumstances, each tradable item identified by a recognized product identifier should be described by one, and only one, ONIX Product record.

In ONIX 3.0 and later, a Product record has a mandatory ‘preamble’ comprising data Groups P.1 and P.2, and carrying data that identifies the record and the product to which it refers. This is followed by up to eight ‘blocks’, each of which is optional. Of these blocks, Blocks 1 to 5, plus 7 and 8 are not repeatable. Block 6 appears to be repeatable, but it is often more useful to think of a singular Block 6 comprising all repeats of its contained <ProductSupply> composites. In special circumstances – with partial (‘Block’) updates and only when <MarketReference> is used to label each individual <ProductSupply> composite – Block 6 can be thought of as a truly repeatable block, each repeat consisting of a single <ProductSupply> composite.

  Product
  product
  0…n

### Block 0: Product record preamble

#### P.1 Record reference, type and source

Two mandatory data elements must be included at the beginning of every Product record or update. The first, <RecordReference>, is a string of text which uniquely identifies the record. The second, <NotificationType>, is a code which specifies the type of notification or update and how it should be treated by a recipient of the ONIX message.

If the record is sent as a deletion, the reason for deletion can optionally be indicated as plain text in <DeletionText>.

The source of the record can optionally be indicated by one or more of the elements <RecordSourceType>, <RecordSourceIdentifier> and <RecordSourceName>.

##### P.1.1 Record reference

For every product, you must choose a single record reference which will uniquely identify the Information record which you send out about that product, and which will remain as its permanent identifier every time you send an update. It doesn’t matter what reference you choose, provided that it is unique and permanent. This record reference doesn’t identify the product – even though you may choose to use the ISBN or another product identifier as a part of your record reference – it identifies your information record about the product, so that the person to whom you are sending an update can match it with what you have previously sent. It is not recommended to use a product identifier as the whole of the record reference. A good way of generating references which are not part of a recognized product identification scheme but which can be guaranteed to be unique is to prefix a product identifier or a meaningless row ID from your internal database with a reversed Internet domain name which is registered to your organization (reversal prevents the record reference appearing to be a resolvable URL). Alternatively, use a UUID.

This field is mandatory and non-repeating.

  Variable length alphanumeric, suggested maximum length 100 characters
  RecordReference
  a001
  1
  `<a001>com.xyzpublishers.onix.36036</a001>` (36036 is a row ID in an internal database that is the source of the data in the record)
  `<RecordReference>72b32344-01c5-4af2-82aa-4d8d12b0df22</RecordReference>` (a UUID)

##### P.1.2 Notification or update type code

An ONIX code which indicates the type of notification or update which you are sending. Mandatory and non-repeating.

  Fixed length, two digits
  List 1
  NotificationType
  a002
  1
  `<NotificationType>02</NotificationType>` (Advance notification)

##### P.1.3 Reason for deletion

Free text which indicates the reason why an ONIX record is being deleted. Optional and repeatable, and may occur only when the <NotificationType> element carries the code value 05. The language attribute is optional for a single instance of <DeletionText>, but must be included in each instance if <DeletionText> is repeated. Note that it refers to the reason why the record is being deleted, not the reason why a product has been ‘deleted’ (in industries which use this terminology when a product is withdrawn).

A product cancellation or abandonment prior to publication, or a product becoming unavailable (eg as a result of being Out of print) are changes of <PublishingStatus> or of <ProductAvailability>, not reasons for deletion.

  Variable length text, suggested maximum length 100 characters
  DeletionText
  a199
  0…n
  language
  `<a199>Issued in error</a199>`

##### P.1.4 Record source type code

An ONIX code which indicates the type of source which has issued the ONIX record. Optional and non-repeating, independently of the occurrence of any other field.

  Fixed length, two digits
  List 3
  RecordSourceType
  a194
  0…1
  `<a194>01</a194>` (Publisher)

##### Record source identifier composite

A group of data elements which together define an identifier of the organization which is the source of the ONIX record. Optional, and repeatable in order to send multiple identifiers for the same organization.

  RecordSourceIdentifier
  recordsourceidentifier
  0…n

##### P.1.5 Record source identifier type code

An ONIX code identifying the scheme from which the identifier in the <IDValue> element is taken. Mandatory in each occurrence of the <RecordSourceIdentifier> composite, and non-repeating.

  Fixed length, two digits
  List 44
  RecordSourceIDType
  x311
  1
  `<x311>03</x311>` (Deutsche Bibliothek publisher identifier)

##### P.1.6 Identifier type name

A name which identifies a proprietary identifier scheme (ie a scheme which is not a standard and for which there is no individual ID type code). Used when, and only when, the code in the <RecordSourceIDType> element indicates a proprietary scheme. Optional and non-repeating.

  Variable length text, suggested maximum length 100 characters
  IDTypeName
  b233
  0…1
  language
  `<b233>KNV</b233>`

##### P.1.7 Identifier value

An identifier of the type specified in the <RecordSourceIDType> element. Mandatory in each occurrence of the <RecordSourceIdentifier> composite, and non-repeating.

  According to the identifier type specified in <RecordSourceIDType>
  IDValue
  b244
  1
  `<b244>8474339790</b244>`

##### End of Record source identifier composite

##### P.1.8 Record source name

The name of the party which issued the record, as free text. Optional and non-repeating, independently of the occurrence of any other field.

  Variable length text, suggested maximum length 100 characters
  RecordSourceName
  a197
  0…1
  `<RecordSourceName>Cambridge University Press</RecordSourceName>`
  The record source need not be the same as the <Sender> specified in the message header: an aggregator may be the sender of a message containing records sourced from several different record suppliers.

#### P.2 Product identifiers

A valid product identifier must be included in every <Product> record. The GTIN-13 (formerly EAN-13) article number is the preferred identifier for international use across a range of product types. Otherproduct numbers may be included where they exist. The XML Schema or DTD requires at least one number to be sent, but does not enforce or rule out any particular types or combinations.

##### Product identifier composite

A group of data elements which together specify an identifier of a product in accordance with a particular scheme. Mandatory within <Product>, and repeatable with different identifiers for the same product. As well as standard identifiers, the composite allows proprietary identifiers (for example SKUs assigned by wholesalers or vendors) to be sent as part of the ONIX record.

ISBN-13 numbers in their unhyphenated form constitute a range of GTIN-13 numbers that has been reserved for the international book trade. Effective from 1 January 2007, it was agreed by ONIX national groups that it should be mandatory in an ONIX <Product> record for any item carrying an ISBN-13 to include the ISBN-13 labelled as a GTIN-13 number (ie as <ProductIDType> code 03), since this is how the ISBN-13 will be used in book trade transactions. For many ONIX applications this will also be sufficient.

For some ONIX applications, however, particularly when data is to be supplied to the library sector, there may be reasons why the ISBN-13 must also be sent labelled distinctively as an ISBN-13 (ie as <ProductIDType> code 15). Users should consult ‘good practice’ guidelines and/or discuss with their trading partners.

Note that for some identifiers such as ISBN, punctuation (typically hyphens or spaces for ISBNs) is used to enhance readability when printed, but the punctuation is dropped when carried in ONIX data. But for other identifiers – for example DOI – the punctuation is an integral part of the identifier and must always be included.

  ProductIdentifier
  productidentifier
  1…n

##### P.2.1 Product identifier type code

An ONIX code identifying the scheme from which the identifier in the <IDValue> element is taken. Mandatory in each occurrence of the <ProductIdentifier> composite, and non-repeating.

  Fixed-length text, two digits
  List 5
  ProductIDType
  b221
  1
  `<ProductIDType>03</ProductIDType>` (GTIN-13)

##### P.2.2 Identifier type name

A name which identifies a proprietary identifier scheme (ie a scheme which is not a standard and for which there is no individual ID type code). Must be included when, and only when, the code in the <ProductIDType> element indicates a proprietary scheme, eg a wholesaler’s own code. Optional and non-repeating.

  Variable length text, suggested maximum length 100 characters
  IDTypeName
  b233
  0…1
  language
  `<IDTypeName>KNV</IDTypeName>`

##### P.2.3 Identifier value

An identifier of the type specified in the <ProductIDType> element. Mandatory in each occurrence of the <ProductIdentifier> composite, and non-repeating.

  According to the identifier type specified in <ProductIDType>
  IDValue
  b244
  1
  `<b244>9780300117264</b244>`

##### End of Product identifier composite

  GTIN-13, ISBN-13 and DOI (ISBN-A) for same product
  using Reference names |
  --- | ---
  `<ProductIdentifier>` |
  `<ProductIDType>03</ProductIDType>` |
  `<IDValue>9780001234567</IDValue>` |
  `</ProductIdentifier>` |
  `<ProductIdentifier>` |
  `<ProductIDType>15</ProductIDType>` |
  `<IDValue>9780001234567</IDValue>` |
  `</ProductIdentifier>` |
  `<ProductIdentifier>` |
  `<ProductIDType>06</ProductIDType>` |
  `<IDValue>10.978.000/1234567</IDValue>` |
  `</ProductIdentifier>` |
  `<ProductIdentifier>` |
  `<ProductIDType>26</ProductIDType>` |
  `<IDValue>10.978.000/1234567</IDValue>` |
  `</ProductIdentifier>` |

  using Short tags |
  --- | ---
  `<productidentifier>` |
  `<b221>03</b221>` | GTIN-13
  `<b244>9780001234567</b244>` |
  `</productidentifier>` |
  `<productidentifier>` |
  `<b221>15</b221>` | ISBN
  `<b244>9780001234567</b244>` |
  `</productidentifier>` |
  `<productidentifier>` |
  `<b221>06</b221>` | DOI
  `<b244>10.978.000/1234567</b244>` |
  `</productidentifier>` |
  `<productidentifier>` |
  `<b221>26</b221>` | ISBN-A
  `<b244>10.978.000/1234567</b244>` |
  `</productidentifier>` |

##### Barcode composite

A group of data elements which together specify a barcode type and its position on a product. Optional: expected to be used only in North America. Repeatable if more than one type of barcode is carried on a single product. The absence of this composite does not mean that a product is not bar-coded.

  Barcode
  barcode
  0…n

##### P.2.4 Barcode type

An ONIX code indicating whether, and in what form, a barcode is carried on a product. Mandatory in any instance of the <Barcode> composite, and non-repeating.

  Fixed length, two digits
  List 141
  BarcodeType
  x312
  1
  `<x312>03</x312>` (GTIN-13+5 – US dollar price encoded)

##### P.2.5 Position on product

An ONIX code indicating a position on a product; in this case, the position in which a barcode appears. Required if the <BarcodeType> element indicates that the barcode appears on the product, even if the position is ‘unknown’. Omitted if the <BarcodeType> element specifies that the product does not carry a barcode. Non-repeating.

  Fixed length, two digits
  List 142
  PositionOnProduct
  x313
  0…1
  `<x313>01</x313>` (Cover 4 – the back cover of a book)

##### End of Barcode composite

  barcode in conventional position on back cover
  using Reference names |
  --- | ---
  `<Barcode>` |
  `<BarcodeType>02</BarcodeType>` |
  `<PositionOnProduct>01</PositionOnProduct>` |
  `</Barcode>` |

  using Short tags |
  --- | ---
  `<barcode>` |
  `<x312>02</x312>` | GTIN-13 (no extension)
  `<x313>01</x313>` | Cover 4 (outside back cover)
  `</barcode>` |

  positive indication of no barcode
  using Reference names |
  --- | ---
  `<Barcode>` |
  `<BarcodeType>00</BarcodeType>` |
  `</Barcode>` |

  using Short tags |
  --- | ---
  `<barcode>` |
  `<x312>00</x312>` | No barcode on product
  `</barcode>` |

### Block 1: Product description

#### Descriptive detail composite

The descriptive detail block covers data Groups P.3 to P.13, all of which are essentially part of the factual description of the form and content of a product. The block as a whole is non-repeating. It is mandatory in any <Product> record unless the <NotificationType> in Group P.1 indicates that the record is an update notice which carries only those blocks in which changes have occurred.

  DescriptiveDetail
  descriptivedetail
  0…1

#### P.3 Product form

Group P.3 carries elements that describe the form of a product, its key content type (text, audio, etc) and, in the case of digital products, any usage constraints that are enforced through DRM protection or otherwise.

Additional guidance on the description of digital products in ONIX 3.0 and later will be found in a separate document ONIX for Books Product Information Message: How to Describe Digital Products in ONIX 3 and in other Application notes available from EDItEUR.

##### P.3.1 Product composition

An ONIX code which indicates whether a product consists of a single item or multiple items or components. Mandatory in an occurrence of <DescriptiveDetail>, and non-repeating.

  Fixed length, two digits
  List 2
  ProductComposition
  x314
  1
  `<x314>00</x314>` (Single-item product)

##### P.3.2 Product form code

An ONIX code which indicates the primary form of a product. Mandatory in an occurrence of <DescriptiveDetail>, and non-repeating.

Note that in ONIX 3.0 and later, the handling of multiple-item and multi-component products requires that the form of the contained items or components is specified only in the <ProductPart> composite (equivalent to <Contained Item> in earlier releases of ONIX). <ProductPart> forms Group P.4 and must be included for full description of any multiple-item or multi-component product.

  Fixed length, two letters (or the digits 00)
  List 150
  ProductForm
  b012
  1
  `<ProductForm>BB</ProductForm>` (Hardback book)

##### P.3.3 Product form detail

An ONIX code which provides added detail of the medium and/or format of the product. Optional, and repeatable in order to provide multiple additional details.

  Fixed length, four characters: one letter followed by three digits
  List 175
  ProductFormDetail
  b333
  0…n
  `<b333>B206</b333>` (Pop-up book)

##### Product form feature composite

An optional group of data elements which together describe an aspect of product form that is too specific to be covered in the <ProductForm> and <ProductFormDetail> elements. Repeatable in order to describe different aspects of the product form.

  ProductFormFeature
  productformfeature
  0…n

##### P.3.4 Product form feature type

An ONIX code which specifies the feature described by an instance of the <ProductFormFeature> composite, eg binding color. Mandatory in each occurrence of the composite, and non-repeating.

  Fixed length, two digits
  List 79
  ProductFormFeatureType
  b334
  1
  `<b334>02</b334>` (Page edge color)

##### P.3.5 Product form feature value

A controlled value that describes a product form feature. Presence or absence of this element depends on the <ProductFormFeatureType>, since some product form features (eg color of cover binding) require an accompanying value, while some (eg text font) require free text in <ProductFormFeatureDescription>. Others may have both code value and free text. Non-repeating.

  Dependent on the scheme specified in <ProductFormFeatureType>
  Dependent on the scheme specified in <ProductFormFeatureType>
  For cover binding color, see List 98
  For page edge color, see List 98
  For special cover material, see List 99
  For text font, use free text in <ProductFormFeatureDescription>, which should include a font name for the main body text. <ProductFormFeatureValue> may include the body text size in points
  For DVD region codes, see List 76
  For CPSIA choking hazard warning, see List 143
  For EU Toy Safety hazard warnings, see List 184
  For various paper certification schemes (FSC, PEFC etc), see List 79. <ProductFormFeatureType> identifies the certification scheme, and <ProductFormFeatureValue> may carry a Chain of Custody (COC) number. For certified recycled paper, a separate repeat of the <ProductFormFeature> composite may carry the percent post-consumer waste used in a product
  For specific versions of common e-publication file formats, (eg the IDPF’s EPUB 3.0.1), use <ProductFormFeatureType> code 15 and a value from List 220. For e-publication formats not covered in List 220, use <ProductFormFeatureType> code 10 and a period-separated list of numbers (eg ‘7’, ‘1.5’ or ‘3.10.7’) in <ProductFormFeatureValue>
  For required operating system for a digital product, see List 176. You should in addition include operating system version information (major and minor version numbers as necessary, eg ‘10.6.4 or later’ for Mac OS 10.6.4, ‘7 SP1 or later’ for Windows 7 Service Pack 1) in <ProductFormFeatureDescription>. For other system requirements for a digital product (eg specific memory, storage or other hardware requirements), use free text in <ProductFormFeatureDescription> within a separate repeat of the <ProductFormFeature> composite
  For e-publication accessibility features for print-impaired readers, see List 196
  Further features with corresponding code lists may be added from time to time without a re-issue of this document – see the latest release of List 79
  ProductFormFeatureValue
  b335
  0…1
  `<b335>BLK</b335>` (Black color)

##### P.3.6 Product form feature description

If the <ProductFormFeatureType> requires free text rather than a code value, or if the code in <ProductFormFeatureValue> does not adequately describe the feature, a short text description may be added. Optional, and repeatable to provide parallel descriptive text in multiple languages. The language attribute is optional for a single instance of <ProductFormFeatureDescription>, but must be included in each instance if <ProductFormFeatureDescription> is repeated.

  Variable length text, suggested maximum length 10,000 characters
  ProductFormFeatureDescription
  b336
  0…n
  language
  `<b336>11pt Helvetica</b336>`

##### End of Product form feature composite

  use of <ProductFormFeature> to describe large print for visually impaired readers
  using Reference names |
  --- | ---
  `<ProductFormFeature>` |
  `<ProductFormFeatureType>03</ProductFormFeatureType>` |
  `<ProductFormFeatureValue>18</ProductFormFeatureValue>` |
  `<ProductFormFeatureDescription>Tiresias LP</ProductFormFeatureDescription>` |
  `</ProductFormFeature>` |

  using Short tags |
  --- | ---
  `<productformfeature>` |
  `<b334>03</b334>` | Text font
  `<b335>18</b335>` | Points
  `<b336>Tiresias LP</b336>` |
  `</productformfeature>` |

  denoting use of FSC-certified paper
  using Reference names |
  --- | ---
  `<ProductFormFeature>` |
  `<ProductFormFeatureType>32</ProductFormFeatureType>` |
  `<ProductFormFeatureValue>SW-COC-1806</ProductFormFeatureValue>` |
  `</ProductFormFeature>` |

  using Short tags |
  --- | ---
  `<productformfeature>` |
  `<b334>32</b334>` | FSC mixed sources
  `<b335>SW-COC-1806</b335>` | Chain of custody number
  `</productformfeature>` |

  book packaged as mobile phone ‘app’, including audio and video content
  using Reference names |
  --- | ---
  `<ProductForm>ED</ProductForm>` |
  `<ProductFormDetail>E134</ProductFormDetail>` |
  `<ProductFormFeature>` |
  `<ProductFormFeatureType>06</ProductFormFeatureType>` |
  `<ProductFormFeatureValue>03</ProductFormFeatureValue>` |
  `<ProductFormFeatureDescription>4.1 or later</ProductFormFeatureDescription>` |
  `</ProductFormFeature>` |
  `<PrimaryContentType>10</PrimaryContentType>` |
  `<ProductContentType>06</ProductContentType>` |
  `<ProductContentType>13</ProductContentType>` |

  using Short tags |
  --- | ---
  `<b012>ED</b012>` | Digital download
  `<b333>E134</b333>` | Phone ‘app’ for iOS
  `<productformfeature>` |
  `<b334>06</b334>` | Operating system
  `<b335>03</b335>` | iOS
  `<b336>4.1 or later</b336>` | Version 4.1
  `</productformfeature>` |
  `<x416>10</x416>` | Eye-readable text
  `<b385>06</b385>` | Enhanced with video
  `<b385>13</b385>` | and audio content

##### P.3.7 Product packaging type code

An ONIX code which indicates the type of outer packaging used for the product. Optional and non-repeating.

  Fixed length, two digits
  List 80
  ProductPackaging
  b225
  0…1
  `<ProductPackaging>05</ProductPackaging>` (Jewel case)

##### P.3.8 Product form description

If product form codes do not adequately describe the product, a short text description may be added to give a more detailed specification of the product form. The field is optional, and repeatable to provide parallel descriptions in multiple languages. The language attribute is optional for a single instance of <ProductFormDescription>, but must be included in each instance if <ProductFormDescription> is repeated to provide parallel descriptions in multiple languages.

  Variable length text, suggested maximum length 200 characters
  ProductFormDescription
  b014
  0…n
  language
  `<ProductFormDescription language="eng">Hardback book die-cut into car shape, with wheels attached to front and back covers</ProductFormDescription>`

##### P.3.9 Trade category code

An ONIX code which indicates a trade category which is somewhat related to, but not properly an attribute of, product form. Optional and non-repeating.

  Fixed length, two digits
  List 12
  TradeCategory
  b384
  0…1
  `<TradeCategory>03</TradeCategory>` (Sonderausgabe – Germany)

##### P.3.10 Primary content type code

An ONIX code which indicates the primary or only content type included in a product. The element is intended to be used in particular for digital products, when the sender wishes to make it clear that one of a number of content types (eg text, audio, video) is the primary type for the product. Other content types may be specified in the <ProductContentType>. Optional and non-repeating.

  Fixed length, two digits
  List 81
  PrimaryContentType
  x416
  0…1
  `<x416>10</x416>` (Eye-readable text)

##### P.3.11 Product content type code

An ONIX code which indicates a content type included in a product. The element is intended to be used in particular for digital products, to specify content types other than the primary type, or to list content types when none is singled out as the primary type. Optional, and repeatable to list multiple content types.

  Fixed length, two digits
  List 81
  ProductContentType
  b385
  0…n
  `<ProductContentType>11</ProductContentType>` (Musical notation)

##### Measure composite

An optional group of data elements which together identify a measurement and the units in which it is expressed; used to specify the overall dimensions of a physical product including its packaging (if any). Repeatable to provide multiple combinations of dimension and unit.

  Measure
  measure
  0…n

##### P.3.12 Measure type code

An ONIX code indicating the dimension which is specified by an occurrence of the measure composite. Mandatory in each occurrence of the <Measure> composite, and non-repeating.

  Fixed length, two digits
  List 48
  MeasureType
  x315
  1
  `<x315>01</x315>` (Height)

##### P.3.13 Measurement

The number which represents the dimension specified in <MeasureType> in the measure units specified in <MeasureUnitCode>. Mandatory in each occurrence of the <Measure> composite, and non-repeating.

  Positive real number, with explicit decimal point when required, suggested maximum length 6 characters
  Measurement
  c094
  1
  `<c094>8.25</c094>`

##### P.3.14 Measure unit code

An ONIX code indicating the measure unit in which dimensions are given. Mandatory in each occurrence of the <Measure> composite, and non-repeating. This element must follow the dimension to which the measure unit applies. See example below.

  Fixed length, two letters
  List 50
  MeasureUnitCode
  c095
  1
  `<c095>mm</c095>`

##### End of Measure composite

  use of the <Measure> composite
  using Reference names |
  --- | ---
  `<Measure>` |
  `<MeasureType>01</MeasureType>` | Height
  `<Measurement>235</Measurement>` | 235
  `<MeasureUnitCode>mm</MeasureUnitCode>` | millimeters
  `</Measure>` |
  `<Measure>` |
  `<MeasureType>02</MeasureType>` | Width
  `<Measurement>159</Measurement>` | 159
  `<MeasureUnitCode>mm</MeasureUnitCode>` | millimeters
  `</Measure>` |
  `<Measure>` |
  `<MeasureType>03</MeasureType>` | Spine thickness
  `<Measurement>30.5</Measurement>` | 30.5
  `<MeasureUnitCode>mm</MeasureUnitCode>` | millimeters
  `</Measure>` |
  `<Measure>` |
  `<MeasureType>08</MeasureType>` | Weight
  `<Measurement>980</Measurement>` | 980
  `<MeasureUnitCode>gr</MeasureUnitCode>` | grams
  `</Measure>` |

  using Short tags, with American customary units |
  --- | ---
  `<measure>` |
  `<x315>01</x315>` |
  `<c094>9.25</c094>` |
  `<c095>in</c095>` |
  `</measure>` |
  `<measure>` |
  `<x315>02</x315>` |
  `<c094>6.25</c094>` |
  `<c095>in</c095>` |
  `</measure>` |
  `<measure>` |
  `<x315>03</x315>` |
  `<c094>1.2</c094>` |
  `<c095>in</c095>` |
  `</measure>` |
  `<measure>` |
  `<x315>08</x315>` |
  `<c094>34.5625</c094>` |
  `<c095>oz</c095>` |
  `</measure>` |

##### P.3.15 Country of manufacture

An ONIX code identifying the country of manufacture of a single-item product, or of a multiple-item product when all items are manufactured in the same country. This information is needed in some countries to meet regulatory requirements. Optional and non-repeating.

  Fixed length, two letters, based on ISO 3166-1. Note that ISO 3166-1 specifies that country codes shall be sent as upper case only
  List 91
  CountryOfManufacture
  x316
  0…1
  `<x316>US</x316>`

##### P.3.16 Digital product technical protection

An ONIX code specifying whether a digital product has DRM or other technical protection features. Optional, and repeatable if a product has two or more kinds of protection (ie different parts of a product are protected in different ways).

  Fixed length, two digits
  List 144
  EpubTechnicalProtection
  x317
  0…n
  `<x317>03</x317>` (Has digital watermarking)
  ‘Epub’ (‘e-publication’) here and in other element names below refers to any digital product, and has no necessary link with the .epub file format developed by the IDPF

##### Usage constraint composite (digital products)

An optional group of data elements which together describe a usage constraint on a digital product (or the absence of such a constraint), whether enforced by DRM technical protection, inherent in the platform used, or specified by license agreement. Repeatable in order to describe multiple constraints on usage.

  EpubUsageConstraint
  epubusageconstraint
  0…n

##### P.3.17 Usage type (digital products)

An ONIX code specifying a usage of a digital product. Mandatory in each occurrence of the <EpubUsageConstraint> composite, and non-repeating.

  Fixed length, two digits
  List 145
  EpubUsageType
  x318
  1
  `<x318>05</x318>` (Text-to-speech)

##### P.3.18 Usage status (digital products)

An ONIX code specifying the status of a usage of a digital product, eg permitted without limit, permitted with limit, prohibited. Mandatory in each occurrence of the <EpubUsageConstraint> composite, and non-repeating.

  Fixed length, two digits
  List 146
  EpubUsageStatus
  x319
  1
  `<x319>03</x318>` (Prohibited)

##### Usage limit composite (digital products)

An optional group of data elements which together specify a quantitative limit on a particular type of usage of a digital product. Repeatable in order to specify two or more limits on the usage type.

  EpubUsageLimit
  epubusagelimit
  0…n

##### P.3.19 Usage quantity (digital products)

A numeric value representing the maximum permitted quantity of a particular type of usage. Mandatory in each occurrence of the <EpubUsageLimit> composite, and non-repeating.

  Positive real number, with explicit decimal point when required, or zero, as appropriate for the units specified in <EpubUsageUnit>
  Quantity
  x320
  1
  `<Quantity>10</Quantity>`

##### P.3.20 Usage unit (digital products)

An ONIX code for a unit in which a permitted usage quantity is stated. Mandatory in each occurrence of the <EpubUsageLimit> composite, and non-repeating.

  Fixed length, two digits
  List 147
  EpubUsageUnit
  x321
  1
  `<EpubUsageUnit>07</EpubUsageUnit>` (Maximum number of concurrent users)

##### End of Usage limit composite (digital products)

##### End of Usage constraint composite (digital products)

##### Digital product license composite

An optional composite carrying the name or title of the license governing use of the product, a link to the license terms in eye-readable or machine-readable form, and optional dates when the license is valid. Repeatable in order to specify multiple licenses with differing periods of validity.

Note that in the case of multiple Digital product license composites, any Usage constraints (above) apply to the current license.

  EpubLicense
  epublicense
  0…n

##### P.3.20a Digital product license name

The name or title of the license. Mandatory in any <EpubLicense> composite, and repeatable to provide the license name in multiple languages. The language attribute is optional for a single instance of <EpubLicenseName>, but must be included in each instance if <EpubLicenseName> is repeated.

  Variable length text, suggested maximum length 100 characters
  EpubLicenseName
  x511
  1…n
  language
  `<x511>Elsevier e‑book EULA v5</x511>`

##### Digital product license expression composite

An optional composite that carries details of a link to an expression of the license terms, which may be in human-readable or machine-readable form. Repeatable when there is more than one expression of the license.

  EpubLicenseExpression
  epublicenseexpression
  0…n

##### P.3.20b License expression type

An ONIX code identifying the nature or format of the license expression specified in the <EpubLicenseExpressionLink> element. Mandatory within the <EpubLicenseExpression> composite, and non-repeating.

  Fixed-length text, two digits
  List 218
  EpubLicenseExpressionType
  x508
  1
  `<x508>10</x508>` (ONIX-PL license expression)

##### P.3.20c License expression type name

A short free-text name for a license expression type, when the code in <EpubLicenseExpressionType> provides insufficient detail – for example when a machine-readable license is expressed using a particular proprietary encoding scheme. Optional and non-repeating, and must be included when (and only when) the <EpubLicenseExpressionType> element indicates the expression is encoded in a proprietary way.

  Variable length text, suggested maximum length 50 characters
  EpubLicenseExpressionTypeName
  x509
  0…1
  language
  `<x509>ABC-XML</x509>`

##### P.3.20d License expression link

The URI for the license expression. Mandatory in each instance of the <EpubLicenseExpression> composite, and non-repeating.

  Variable length text, suggested maximum length 300 characters
  EpubLicenseExpressionLink
  x510
  1
  `<EpubLicenseExpressionLink>http://creativecommons.org/​licenses/​by/​3.0/​deed.en_GB</EpubLicenseExpressionLink>`

##### End of Digital product license expression composite

##### Digital product license date

An optional group of date elements which together specify a date associated with the license in an occurrence of the <EpubLicense> composite, eg a date when a license expires. Repeatable to specify different dates with their various roles.

Note that if no dates are specified, the license is effective at the time the ONIX message is sent.

  EpubLicenseDate
  epublicensedate
  0…n

##### P.3.20e Digital product license date role code

An ONIX code indicating the significance of the date in relation to the license. Mandatory in each occurrence of the <EpubLicenseDate> composite, and non-repeating.

  Fixed length, two digits
  List 260
  EpubLicenseDateRole
  x585
  1
  `<EpubLicenseDateRole>14</EpubLicenseDateRole>` (license becomes effective)

##### P.3.20f Date

The date specified in the <EpubLicenseDateRole> field. Mandatory in each occurrence of the <EpubLicenseDate> composite, and non-repeating. <Date> may carry a dateformat attribute: if the attribute is missing, then the default format is YYYYMMDD.

  As specified by the value in the dateformat attribute, or the default YYYYMMDD
  Date
  b306
  1
  dateformat
  `<Date>20221028</Date>`
  Note that all dates are inclusive, so ‘Valid from’ is the first date on which the license is effective, and ‘Valid until’ is the last date on which it is effective.

##### End of Digital product license date composite

##### End of Digital product license composite

  e‑book with certain usage limits enforced by DRM, and link to license
  using Reference names |
  --- | ---
  `<EpubTechnicalProtection>03</EpubTechnicalProtection>` |
  `<EpubUsageConstraint>` |
  `<EpubUsageType>05</EpubUsageType>` |
  `<EpubUsageStatus>01</EpubUsageStatus>` |
  `</EpubUsageConstraint>` |
  `<EpubUsageConstraint>` |
  `<EpubUsageType>03</EpubUsageType>` |
  `<EpubUsageStatus>02</EpubUsageStatus>` |
  `<EpubUsageLimit>` |
  `<Quantity>10</Quantity>` |
  `<EpubUsageUnit>05</EpubUsageUnit>` |
  `</EpubUsageLimit>` |
  `</EpubUsageConstraint>` |
  `<EpubUsageConstraint>` |
  `<EpubUsageType>06</EpubUsageType>` |
  `<EpubUsageStatus>02</EpubUsageStatus>` |
  `<EpubUsageLimit>` |
  `<Quantity>1</Quantity>` |
  `<EpubUsageUnit>10</EpubUsageUnit>` |
  `</EpubUsageLimit>` |
  `<EpubUsageLimit>` |
  `<Quantity>14</Quantity>` |
  `<EpubUsageUnit>09</EpubUsageUnit>` |
  `</EpubUsageLimit>` |
  `</EpubUsageConstraint>` |
  `<EpubLicense>` |
  `<EpubLicenseName>MyPublisher EULA v3</EpubLicenseName>` |
  `<EpubLicenseExpression>` |
  `<EpubLicenseExpressionType>01</EpubLicenseExpressionType>` |
  `<EpubLicenseExpressionLink>http://www.mypublisher.com/​licenses/​EULA_v3.pdf​</EpubLicenseExpressionLink>` |
  `</EpubLicenseExpression>` |
  `</EpubLicense>` |

  using Short tags |
  --- | ---
  `<x317>03</x317>` | ACS4 DRM
  `<epubusageconstraint>` |
  `<x318>05</x318>` | Text to speech
  `<x319>01</x319>` | is unrestricted
  `</epubusageconstraint>` |
  `<epubusageconstraint>` |
  `<x318>03</x318>` | Copy/paste
  `<x319>02</x319>` | is limited
  `<epubusagelimit>` |
  `<x320>10</x320>` | Ten
  `<x321>05</x321>` | percent
  `</epubusagelimit>` |
  `</epubusageconstraint>` |
  `<epubusageconstraint>` |
  `<x318>06</x318>` | Lending
  `<x319>02</x319>` | is limited
  `<epubusagelimit>` |
  `<x320>1</x320>` | Only one
  `<x321>10</x321>` | occasion
  `</epubusagelimit>` |
  `<epubusagelimit>` |
  `<x320>14</x320>` | For fourteen
  `<x321>09</x321>` | days
  `</epubusagelimit>` |
  `</epubusageconstraint>` |
  `<epublicense>` |
  `<x511>MyPublisher EULA v3</x511>` |
  `<epublicenseexpression>` |
  `<x508>01</x508>` | Human-readable
  `<x510>http://www.mypublisher.com/​licenses/​EULA_v3.pdf​</x510>` | text of license
  `</epublicenseexpression>` |
  `</epublicense>` |

##### P.3.21 Map scale

The scale of a map, expressed as a ratio 1:nnnnn; only the number nnnnn is carried in the data element, without spaces or punctuation. Optional, and repeatable if a product comprises maps with two or more different scales.

  Positive integer, suggested maximum length 8 digits
  MapScale
  b063
  0…n
  `<b063>50000</b063>` (One to 50,000, 2cm = 1km)

##### Product classification composite

An optional group of data elements which together define a product classification (not to be confused with a subject classification). The intended use is to enable national or international trade classifications (also known as commodity codes) to be carried in an ONIX record. The composite is repeatable if parts of the product are classified differently within a single product classification scheme, or to provide classification codes from multiple classification schemes.

  ProductClassification
  productclassification
  0…n

##### P.3.22 Product classification type code

An ONIX code identifying the scheme from which the identifier in <ProductClassificationCode> is taken. Mandatory in each occurrence of the <ProductClassification> composite, and non-repeating.

  Fixed length, two digits
  List 9
  ProductClassificationType
  b274
  1
  `<b274>02</b274>` (UNSPSC)

##### P.3.22a Product classification type name

A name which identifies a proprietary classification scheme (ie a scheme which is not a standard and for which there is no individual scheme type code). Should be included when, and only when, the code in the <ProductClassificationType> element indicates a proprietary scheme, ie the sender’s own category scheme. Optional and non-repeating.

  Variable length text, suggested maximum length 50 characters
  ProductClassificationTypeName
  x555
  0…1
  language
  `<x555>PublishipGoodsCode</x555>`

##### P.3.23 Product classification code

A classification code from the scheme specified in <ProductClassificationType>. Mandatory in each occurrence of the <ProductClassification> composite, and non-repeating.

  According to the identifier type specified in <ProductClassificationType>
  ProductClassificationCode
  b275
  1
  `<b275>55101514</b275>` (Sheet music in UNSPSC classification scheme)

##### P.3.24 Percentage

The percentage of the unit value of the product that is assignable to a designated product classification. Optional and non-repeating. Used when a mixed product (eg book and CD) belongs partly to two or more product classes within a particular scheme. If omitted, the product classification code applies to 100% of the product.

  Real number between zero and 100 (inclusive), with explicit decimal point when required, suggested maximum length 7 characters
  Percent
  b337
  0…1
  `<Percent>66.67</Percent>`

##### End of Product classification composite

  supplying a commodity code
  using Reference names |
  --- | ---
  `<ProductClassification>` |
  `<ProductClassificationType>02</ProductClassificationType>` |
  `<ProductClassificationCode>55101509</ProductClassificationCode>` |
  `</ProductClassification>` |

  using Short tags |
  --- | ---
  `<productclassification>` |
  `<b274>02</b274>` | UN Standard Products and Services Code
  `<b275>55101509</b275>` | Educational or vocational textbooks
  `</productclassification>` |

#### P.4 Product parts

Elements in Group P.4 are used only when the <ProductComposition> and <ProductForm> codes for the product indicate that it is either a multiple-component or multiple-item retail product, or a trade pack. In either of these circumstances, ONIX 3.0 and later require that there must be at least one instance of the <ProductPart> composite, to describe the items or components that together make up the product.

Additional guidance on the description of product parts in ONIX 3.0 and later will be found in a separate document ONIX for Books Product Information Format: How to describe sets, series and multiple-item products and in other Application notes available from EDItEUR.

##### Product part composite

A group of data elements which together describe an item which is part of or contained within a multiple-component or multiple-item product or a trade pack. The composite must be used with all multi-component or multi-item products and packs to specify (for example) the item(s) and item quantities included in a combined book plus audiobook product, a multi-volume set, a filled dumpbin, or a classroom pack. In other cases, where parts are not individually identified, it is used to state the product form(s) and the quantity or quantities of each form contained within the product. The composite must be repeated for each individually-identified item or component, or for each unidentified type of item or component.

Each instance of the <ProductPart> composite must carry a <ProductForm> code and a quantity, even if the quantity is ‘1’. If the composite refers to a number of copies of a single item, the quantity must be sent as <NumberOfCopies>, normally accompanied by a <ProductIdentifier>. If the composite refers to a number of different items of the same form, without identifying them individually, the quantity must be sent as <NumberOfItemsOfThisForm>.

  ProductPart
  productpart
  0…n

##### P.4.1 ‘Primary part’ indicator

An empty element that allows a sender to identify a product part as the ‘primary’ part of a multiple-item product. For example, in a ‘book and toy’ or ‘book and DVD’ product, the book may be regarded as the primary part. Optional and non-repeating.

  XML empty element
  PrimaryPart/
  x457/
  0…1
  `<PrimaryPart/>`

##### Product identifier composite (product part)

A group of data elements which together define an identifier of a product in accordance with a specified scheme, used here to carry the product identifier of a product part. Optional, but required when an occurrence of <ProductPart> specifies an individual item with its own identifier, and repeatable with different identifiers for the same product part.

  ProductIdentifier
  productidentifier
  0…n

##### P.4.2 Product identifier type code

An ONIX code identifying the scheme from which the identifier in the <IDValue> element is taken. Mandatory in each occurrence of the <ProductIdentifier> composite, and non-repeating.

  Fixed-length text, two digits
  List 5
  ProductIDType
  b221
  1
  `<ProductIDType>03</ProductIDType>` (GTIN-13)

##### P.4.3 Identifier type name

A name which identifies a proprietary identifier scheme (ie a scheme which is not a standard and for which there is no individual ID type code). Must be included when, and only when, the code in the <ProductIDType> element indicates a proprietary scheme, eg a wholesaler’s own code. Optional and non-repeating.

  Variable length text, suggested maximum length 100 characters
  IDTypeName
  b233
  0…1
  language
  `<IDTypeName>KNV</IDTypeName>`

##### P.4.4 Identifier value

An identifier of the type specified in the <ProductIDType> element. Mandatory in each occurrence of the <ProductIdentifier> composite, and non-repeating.

  According to the identifier type specified in <ProductIDType>
  IDValue
  b244
  1
  `<b244>9780300117264</b244>`

##### End of Product identifier composite (product part)

##### P.4.5 Product form code (product part)

An ONIX code which indicates the primary form of a product part. Mandatory in each occurrence of <ProductPart>, and non-repeating.

  Fixed length, two letters (or the digits 00)
  List 150
  ProductForm
  b012
  1
  `<b012>BB</b012>` (Hardback book)

##### P.4.6 Product form detail (product part)

An ONIX code which provides added detail of the medium and/or format of a product part. Optional, and repeatable in order to provide multiple additional details.

  Fixed length, four characters: one letter followed by three digits
  List 175
  ProductFormDetail
  b333
  0…n
  `<b333>B206</b333>` (Pop-up book)

##### Product form feature composite (product part)

An optional group of data elements which together describe an aspect of product form that is too specific to be covered in the <ProductForm> and <ProductFormDetail> elements. Repeatable in order to describe different aspects of the form of the product part. The composite is included here so that it can for example be used to carry consumer protection data related to a product part.

  ProductFormFeature
  productformfeature
  0…n

##### P.4.7 to P.4.9: elements in the Product form feature composite

Elements P.4.7 to P.4.9 in the <ProductFormFeature> composite are identical to P.3.4 to P.3.6 as specified in Group P.3.

##### End of Product form feature composite (product part)

##### P.4.9a Product packaging type code (product part)

An ONIX code which indicates the type of packaging used for the product part. Optional, and not repeatable.

  Fixed length, two digits
  List 80
  ProductPackaging
  b225
  0…1
  `<b225>05</b225>` (Jewel case)

##### P.4.10 Product form description (product part)

If product form codes do not adequately describe the contained item, a short text description may be added. Optional and repeatable. The language attribute is optional for a single instance of <ProductFormDescription>, but must be included in each instance if <ProductFormDescription> is repeated.

  Variable length text, suggested maximum length 200 characters
  ProductFormDescription
  b014
  0…n
  language
  `<b014>Birdsong recordings illustrating the accompanying text</b014>`

##### P.4.11 Product content type code (product part)

An ONIX code which indicates certain types of content which are closely related to but not strictly an attribute of product form, eg audiobook. Optional and repeatable.

  Fixed-length text, two digits
  List 81
  ProductContentType
  b385
  0…n
  `<ProductContentType>01</ProductContentType>` (Audiobook)

##### Measure composite (product part)

An optional group of data elements which together identify a measurement and the units in which it is expressed; used to specify the overall dimensions of a physical product part including its inner packaging (if any). Repeatable to provide multiple combinations of dimension and unit.

  Measure
  measure
  0…n

##### P.4.11a to P.4.11c: elements in the Measure composite

Elements P.4.11a to P.4.11c in the <Measure> composite are identical to P.3.12 to P.3.14 as specified in Group P.3.

##### End of Measure composite (product part)

##### P.4.12 Number of items of a specified form (product part)

When product parts are listed as a specified number of different items in a specified form, without identifying the individual items, <NumberOfItemsOfThisForm> must be used to carry the quantity, even if the number is ‘1’. Consequently the element is mandatory and non-repeating in an occurrence of the <ProductPart> composite if <NumberOfCopies> is not present; and it must not be used if <ProductIdentifier> is present.

  Positive integer, suggested maximum length 4 digits
  NumberOfItemsOfThisForm
  x322
  0…1
  `<x322>3</x322>`

##### P.4.13 Number of copies (product part)

When product parts are listed as a specified number of copies of a single item, usually identified by a <ProductIdentifier>, <NumberOfCopies> must be used to specify the quantity, even if the number is ‘1’. It must be used when a multiple-item product or pack contains (a) a quantity of a single item; or (b) one of each of several different items (as in a multi-volume set); or (c) one or more of each of several different items (as in a dumpbin carrying copies of two different books, or a classroom pack containing a teacher’s text and twenty student texts). Consequently the element is mandatory, and non-repeating, in an occurrence of the <ProductPart> composite if <NumberOfItemsOfThisForm> is not present. It is normally accompanied by a <ProductIdentifier>; but in exceptional circumstances, if the sender’s system is unable to provide an identifier at this level, it may be sent with product form coding and without an ID.

  Positive integer, suggested maximum length 4 digits
  NumberOfCopies
  x323
  0…1
  `<x323>24</x323>` (24 copies of a single item in eg a classroom pack of textbooks)

##### P.4.14 Country of manufacture (product part)

An ONIX code identifying the country in which a product part was manufactured, if different product parts were manufactured in different countries. This information is needed in some countries to meet regulatory requirements. Optional and non-repeating.

  Fixed length, two letters, based on ISO 3166-1. Note that ISO 3166-1 specifies that country codes shall be sent as upper case only
  List 91
  CountryOfManufacture
  x316
  0…1
  `<CountryOfManufacture>US</CountryOfManufacture>`

##### End of Product part composite

  three-volume work, slip-cased
  using Reference names |
  --- | ---
  `<ProductComposition>10</ProductComposition>` |
  `<ProductForm>SC</ProductForm>` |
  `<!-- Measure composites omitted for brevity -->` |
  `<ProductPart>` |
  `<ProductForm>BB</ProductForm>` |
  `<NumberOfItemsOfThisForm>3</NumberOfItemsOfThisForm>` |
  `</ProductPart>` |

  using Short tags |
  --- | ---
  `<x313>10</x313>` | Multi-item retail product
  `<b012>SC</b012>` | Slip-cased set
  `<!-- measure composites omitted -->` |
  `<productpart>` |
  `<b012>BB</b012>` | Hardback
  `<x322>3</x322>` | 3 vols
  `</productpart>` |

  book with two-disc audiobook in sleeve attached to inside back cover
  using Reference names |
  --- | ---
  `<ProductComposition>10</ProductComposition>` |
  `<ProductForm>SF</ProductForm>` |
  `<!-- Measure composites omitted for brevity -->` |
  `<ProductPart>` |
  `<PrimaryPart/>` |
  `<ProductIdentifier>` |
  `<ProductIDType>03</ProductIDType>` |
  `<IDValue>9780001234567</IDValue>` |
  `</ProductIdentifier>` |
  `<ProductForm>BC</ProductForm>` |
  `<NumberOfCopies>1</NumberOfCopies>` |
  `</ProductPart>` |
  `<ProductPart>` |
  `<ProductForm>AC</ProductForm>` |
  `<ProductFormDetail>A101</ProductFormDetail>` |
  `<NumberOfItemsOfThisForm>2</NumberOfItemsOfThisForm>` |
  `</ProductPart>` |

  using Short tags |
  --- | ---
  `<x313>10</x313>` | Multi-item retail product
  `<b012>SF</b012>` | Multi-item retail product, part(s) enclosed
  `<!-- measure composites omitted -->` |
  `<productpart>` |
  `<x457/>` | Book is the primary part of the product
  `<productidentifier>` |
  `<b221>03</b221>` | GTIN-13
  `<b244>9780001234567</b244>` | (of book as separate product)
  `</productidentifier>` |
  `<b012>BC</b012>` | Paperback
  `<x323>1</x323>` |
  `</productpart>` |
  `<productpart>` |
  `<b012>AC</b012>` | CD-Audio
  `<b333>A101</b333>` | ‘Red Book’ audio format
  `<x322>2</x322>` | Two discs
  `</productpart>` |

#### P.5 Collection

Group P.5 is used to describe attributes of a bibliographic collection to which a product belongs.

A bibliographic collection in ONIX 3.0 and later means a fixed or indefinite number of products, published over a fixed or indefinite time period, which share collective attributes (including a collective title) that are required as part of the bibliographic record of each individual product. In this respect, such a collection is most often thought of as a series. A bibliographic collection may, however, also be traded as a single product (often thought of as a set), but this does not alter the way in which its collective attributes are described in the ONIX records for the individual products.

In other words, from Release 3.0, ONIX doesn’t care whether a collection is most naturally thought of as a series or a set. If a fixed or indefinite number of products have a collective title and – possibly – other collective attributes that are required as part of the bibliographic record of each individual product, then those products are regarded as forming a collection.

ONIX 3.0 and 3.1 recognize two major types of collection: a publisher collection, and an ascribed collection. A publisher collection is one that is identified either on the products themselves or in product information originating from the publisher. An ascribed collection is one that is identified by another party in the information supply chain, usually an aggregator, for the benefit of retailers and consumers.

If the collection title, in full and word-for-word, is treated as part of the product title, then it will appear as part of <TitleDetail> in Group P.6, and the <Collection> composite is either not needed or is used to carry collection information other than the collection title. If the collection title is not treated as part of the product title, it must be sent in an instance of the <Collection> composite.

A product may (rarely) belong to two or more bibliographic collections. Consequently the collection-related elements constitute a repeatable composite (and a maximum of one bibliographic collection title – inevitably a publisher collection – may be included in Group P.6).

Additional guidance and extensive examples will be found in a separate document ONIX for Books: Product Information Format: How to describe sets, series and multiple-item products and in other Application notes available from EDItEUR.

##### Collection composite

An optional group of data elements which carry attributes of a collection of which the product is part. (For a publisher collection, these attributes may or may not include the collection title.) The composite is repeatable, to provide details when the product belongs to multiple collections.

Collection-related data elements within a <Collection> composite that does not carry collection title information must relate to a publisher collection whose title is included in Group P.6.

  Collection
  collection
  0…n

##### P.5.1 Collection type code

An ONIX code indicating the type of a collection: publisher collection, ascribed collection, or unspecified. Mandatory in each occurrence of the <Collection> composite, and non-repeating.

  Fixed-length text, two digits
  List 148
  CollectionType
  x329
  1
  `<x329>10</x329>` (Publisher collection)

##### P.5.1a Collection frequency

An ONIX code specifying the approximate or expected publication frequency for addition of new products to the collection. Optional, and non-repeating.

  Fixed-length text, one alphabetic character
  List 259
  CollectionFrequency
  x582
  0…s1
  `<x582>q</x582>` (Four times per year)

##### P.5.2 Source name

If the <CollectionType> code indicates an ascribed collection (ie a collection which has been identified and described by a supply chain organization other than the publisher), this element may be used to carry the name of the organization responsible. Optional and non-repeating.

  Variable length text, suggested maximum length 50 characters
  SourceName
  x330
  0…1
  `<SourceName>Bowker</SourceName>`

##### Collection identifier composite

A repeatable group of data elements which together specify an identifier of a bibliographic collection. The composite is optional, and may only repeat if two or more identifiers of different types are sent for the same collection. It is not permissible to have two identifiers of the same type.

  CollectionIdentifier
  collectionidentifier
  0…n

##### P.5.2a Collection title element level

An ONIX code indicating the level of the collection title element (collection level or sub-collection level) to which the identifier in the <IDValue> element is assigned. Optional in each occurrence of the <CollectionIdentifier> composite, and non-repeating.

When used, the specified level must match the level of a <TitleElement> within the same Collection composite, or – is there is no <TitleDetail> within the Collection composite – the level of a <TitleElement> within Group P.6.

  Fixed-length text, two digits
  List 149 Note that codes 01, 04 cannot be used.
  CollectionElementLevel
  x586
  0…1
  `<x586>03</x586>` (Identifier is assigned to the sub-collection)

##### P.5.3 Collection identifier type code

An ONIX code identifying a scheme from which an identifier in the <IDValue> element is taken. Mandatory in each occurrence of the <CollectionIdentifier> composite, and non-repeating.

  Fixed-length text, two digits
  List 13
  CollectionIDType
  x344
  1
  `<x344>02</x344>` (ISSN)

##### P.5.4 Identifier type name

A name which identifies a proprietary identifier scheme (ie a scheme which is not a standard and for which there is no individual ID type code). Must be included when, and only when, the code in <CollectionIDType> indicates a proprietary scheme, eg a publisher’s own code. Optional and non-repeating.

  Variable length text, suggested maximum length 100 characters
  IDTypeName
  b233
  0…1
  language
  `<b233>Springer</b233>`

##### P.5.5 Identifier value

An identifier of the type specified in the <CollectionIDType> field. Mandatory in each occurrence of the <CollectionIdentifier> composite, and non-repeating.

  According to the identifier type specified in <CollectionIDType>
  IDValue
  b244
  1
  `<b244>12345678</b244>`

##### End of Collection identifier composite

##### Collection sequence composite

An optional and repeatable group of data elements which indicates some ordinal position of a product within a collection. Different ordinal positions may be specified using separate repeats of the composite – for example, a product may be published first while also being third in narrative order within a collection.

  CollectionSequence
  collectionsequence
  0…n

##### P.5.5a Collection sequence type

An ONIX code identifying the type of ordering used for the product’s sequence number within the collection. Mandatory and non-repeating within the <CollectionSequence> composite.

  Fixed length, two digits
  List 197
  CollectionSequenceType
  x479
  1
  `<x479>03</x479>` (Order of publication)

##### P.5.5b Collection sequence type name

A name which describes a proprietary order used for the product’s sequence number within the collection. Must be included when, and only when, the code in the <CollectionSequenceType> field indicates a proprietary scheme. Optional and non-repeating.

  Variable length text, suggested maximum length 50 characters
  CollectionSequenceTypeName
  x480
  0…1
  language
  `<x480>Order of TV series transmission</x480>`

##### P.5.5c Collection sequence number

A number which specifies the ordinal position of the product in a collection. The ordinal position may be a simple number (1st, 2nd, 3rd etc) or may be multi-level (eg 3.2) if the collection has a multi-level structure (ie there are both collection and sub-collection title elements). Mandatory and non-repeating within the <CollectionSequence> composite.

New from 3.0.4 A hyphen may be used in place of an integer within a multi-level number, where a particular level of the hierarchy is unnumbered, for example -.3 where a product is the third in a sub-collection, and the sub-collections are in no particular order within the collection.

  Variable length string of one or more positive integers or hyphens, each successive integer or hyphen being separated by a period character, suggested maximum length 50 characters
  CollectionSequenceNumber
  x481
  1
  `<CollectionSequenceNumber>2.4</CollectionSequenceNumber>`

##### End of Collection sequence composite

##### Title detail composite (collection)

A group of data elements which together give the text of a collection title and specify its type. Optional, but the composite is required unless the only collection title is carried in full, and word-for-word, as an integral part of the product title in P.6, in which case it should not be repeated in P.5. The composite is repeatable with different title types.

  TitleDetail
  titledetail
  0…n

##### P.5.6 Title type code

An ONIX code indicating the type of a title. Mandatory in each occurrence of the <TitleDetail> composite, and non-repeating.

  Fixed-length text, two digits
  List 15
  TitleType
  b202
  1
  `<TitleType>01</TitleType>` (Distinctive title)

##### Title element composite (collection)

A group of data elements which together represent an element of a collection title. At least one title element is mandatory in each occurrence of the <TitleDetail> composite. The composite is repeatable with different sequence numbers and/or title element levels. An instance of the <TitleElement> composite must include at least one of: <PartNumber>; <YearOfAnnual>; <TitleText>, <NoPrefix/> together with <TitleWithoutPrefix>, or <TitlePrefix> together with <TitleWithoutPrefix>. In other words, it must carry either the text of a title element or a part or year designation, and it may carry both.

A title element must be designated as belonging to product level, collection level, or subcollection level (the first of these may not occur in a title element representing a collective identity, and the last-named may only occur in the case of a multi-level collection).

In the simplest case, title detail sent in a <Collection> composite will consist of a single title element, at collection level. However, the composite structure in ONIX 3.0 and 3.1 allows more complex combinations of titles and part designations in multi-level collections to be correctly represented.

  TitleElement
  titleelement
  1…n

##### P.5.6a Title element sequence number

A number which specifies a single overall sequence of title elements, which is the preferred order for display of the various title elements when constructing a complete title. Optional and non-repeating. It is strongly recommended that each occurrence of the <TitleElement> composite should carry a <SequenceNumber>.

  Positive integer, 1, 2, 3 etc, suggested maximum length 3 digits
  SequenceNumber
  b034
  0…1
  `<b034>2</b034>`

##### P.5.7 Title element level

An ONIX code indicating the level of a title element: collection level, sub-collection level, or product level. Mandatory in each occurrence of the <TitleElement> composite, and non-repeating.

  Fixed-length text, two digits
  List 149
  TitleElementLevel
  x409
  1
  `<x409>02</x409>` (Collection level)

##### P.5.8 Part number

When a title element includes a part designation within a larger whole (eg Part I, or Volume 3), this field should be used to carry the number and its ‘caption’ as text. Optional and non-repeating.

  Variable length text, suggested maximum 20 characters
  PartNumber
  x410
  0…1
  language, textscript
  `<PartNumber>Volume 17</PartNumber>`

##### P.5.9 Year of annual

When the year of an annual is part of a title, this field should be used to carry the year (or, if required, a spread of years such as 2009–2010). Optional and non-repeating.

  Year or range of years, in the format YYYY or YYYY-YYYY
  YearOfAnnual
  b020
  0…1
  `<b020>2009</b020>`

##### P.5.10 Title text

The text of a title element, excluding any subtitle. Optional and non-repeating, may only be used where <TitlePrefix>, <NoPrefix/> and <TitleWithoutPrefix> are not used.

This element is deprecated – except in cases where the language of the title does not use explicit definite or indefinite articles (eg The, A) or where national practice is to include these articles for alphabetic sorting purposes. Other than in such languages, the element is intended to be used only when the sending system cannot reliably provide prefixes that are ignored for sorting purposes in a separate data element. If the system can reliably separate prefixes, it should state whether a prefix is present (using <TitlePrefix> and <TitleWithoutPrefix>) or absent (using <NoPrefix/> and <TitleWithoutPrefix>).

  Variable length text, suggested maximum 300 characters
  TitleText
  b203
  0…1
  collationkey, language, textscript, textcase
  `<b203 language="eng" textcase="01">Dickens classics</b203>`

##### P.5.11 Title prefix

Text at the beginning of a title element which is to be ignored for alphabetical sorting. Optional and non-repeating; can only be used when <TitleText> is omitted, and if the <TitleWithoutPrefix> element is also present. These two elements may be used in combination in applications where it is necessary to distinguish an initial word or character string which is to be ignored for filing purposes, eg in library systems and in some bookshop databases.

  Variable length text, suggested maximum 20 characters
  TitlePrefix
  b030
  0…1
  collationkey, language, textscript, textcase
  `<TitlePrefix language="eng">The</TitlePrefix>`

##### P.5.11a “No prefix” indicator

An empty element that provides a positive indication that a title element does not include any prefix that is ignored for sorting purposes. Optional and non-repeating, and must only be used when <TitleWithoutPrefix> is used and no <TitlePrefix> element is present.

  XML empty element
  NoPrefix/
  x501/
  0…1
  `<NoPrefix/>`

##### P.5.12 Title text without prefix

The text of a title element without the title prefix; and excluding any subtitle. Optional and non-repeating; can only be used if one of the <NoPrefix/> or <TitlePrefix> elements is also present.

  Variable length text, suggested maximum 300 characters
  TitleWithoutPrefix
  b031
  0…1
  collationkey, language, textscript, textcase
  `<TitleWithoutPrefix language="eng" textcase="01">shameful life of Salvador Dali</TitleWithoutPrefix>`

##### P.5.13 Subtitle

The text of a subtitle, if any. ‘Subtitle‘ means any added words which appear with the title element given in an occurrence of the <TitleElement> composite, and which amplify and explain the title element, but which are not considered to be part of the title element itself. Optional and non-repeating.

  Variable length text, suggested maximum 300 characters
  Subtitle
  b029
  0…1
  collationkey, language, textscript, textcase
  `<Subtitle textcase="02">The Russian Revolution 1891–1924</Subtitle>`

##### End of Title element composite (collection)

##### P.5.13a Collection title statement

Free text showing how the collection title should be presented in any display, particularly when a standard concatenation of individual title elements from Group P.5 (in the order specified by the <SequenceNumber> data elements) would not give a satisfactory result. Optional and non-repeating. When this field is sent, the recipient should use it to replace all collection title detail sent in Group P.5 for display purposes only. The individual collection title element detail must also be sent, for indexing and retrieval purposes.

  Variable length text, suggested maximum length 1000 characters. XHTML is enabled in this element – see Using XHTML, HTML, XML, JSON within ONIX text fields
  TitleStatement
  x478
  0…1
  language, textformat

##### End of Title detail composite (collection)

##### Contributor composite (collection)

A group of data elements which together describe a personal or corporate contributor to a collection. Optional, and repeatable to describe multiple contributors. The <Contributor> composite is included here for use only by those ONIX communities whose national practice requires contributors to the collection as a whole (eg Series editors) to be identified at collection level. In many countries, including the UK, USA, Canada and Spain, the required practice is to identify all contributors at product level in Group P.7.

  Contributor
  contributor
  0…n

##### P.5.14 to P.5.63a: elements in the Contributor composite

Elements P.5.14 to P.5.63a in the <Contributor> composite are identical to P.7.1 to P.7.50a as specified under Group P.7.

##### End of Contributor composite (collection)

##### P.5.63b Collection contributor statement

Free text showing how the collection authorship should be described in an online display, when a standard concatenation of individual collection contributor elements would not give a satisfactory presentation. Optional but must only be used if one or more instances of <Contributor> are present within <Collection>, and repeatable where parallel text is provided in multiple languages. The language attribute is optional for a single instance of <ContributorStatement>, but must be included in each instance if <ContributorStatement> is repeated. When the <ContributorStatement> element is sent, the recipient should use it to replace all name detail sent in the <Contributor> composites within <Collection> for display purposes only. It does not replace the <Contributor> composite (or any element within it) for individual contributors. The individual name detail must also be sent in one or more <Contributor> composites for indexing and retrieval purposes.

The <ContributorStatement> element is provided here for use only by those ONIX communities whose national practice requires contributors to the collection to be identified at collection level. It should not be sent in a context where collection contributors are normally identified in Group P.6.

  Variable length text, suggested maximum length 1000 characters. XHTML is enabled in this element – see Using XHTML, HTML, XML, JSON within ONIX text fields
  ContributorStatement
  b049
  0…n
  language, textformat
  `<b049>Series conceived and edited by Samantha and Darrin Stephens</b049>`

##### P.5.63c “No authorship” indicator

An empty element that provides a positive indication that a collection has no stated authorship. Optional and non-repeating. Must only be sent in a record that has no <Contributor> data in Group P.5.

The <NoContributor/> element is provided here for use only by those ONIX communities whose national practice requires contributors to the collection to be identified at collection level. It should not be sent in a context where collection contributors are normally identified in Group P.6.

  XML empty element
  NoContributor/
  n339/
  0…1
  `<NoContributor/>`

##### End of Collection composite

##### P.5.64 “No collection” indicator

An empty element that provides a positive indication that a product does not belong to a collection (a ‘set’ or ‘series’). This element is intended to be used in an ONIX accreditation scheme to confirm that collection information is being consistently supplied in publisher ONIX feeds. Optional and non-repeating. Must only be sent in a record that has no instances of the <Collection> composite and has no collection level title elements in Group P.6.

  XML empty element
  NoCollection/
  x411/
  0…1
  `<NoCollection/>`

#### P.6 Product title detail

Group P.6 carries the title or titles of the product described in the ONIX record, and includes the primary occurrence of the <TitleDetail> composite, which is also used in Group P.5. The purpose of this extended title composite in ONIX 3.0 and 3.1 is to make it possible to deliver a distinctive title for a product when that title includes elements relating to a collection (as defined in P.5), or what may be commonly referred to as a series. By structuring a complex title in this way, it is possible to identify correctly the collection level and product level elements, and to deliver them in whatever is the publisher’s preferred arrangement (eg ‘A Game of Thrones: A Song of Ice and Fire, Book 1’, where the collection-level title follows the product-level title).

For more information on the handling of complex titles, users should refer to the additional guidance and extensive examples to be found in a separate document ONIX for Books: Product Information Format: How to describe sets, series and multiple-item products.

##### Title detail composite

A group of data elements which together give the text of a title and specify its type. At least one title detail element is mandatory in each occurrence of the <DescriptiveDetail> composite, to give the primary form of the product title. The composite is repeatable with different title types.

  TitleDetail
  titledetail
  1…n

##### P.6.1 Title type code

An ONIX code indicating the type of a title. Mandatory in each occurrence of the <TitleDetail> composite, and non-repeating.

  Fixed length, two digits
  List 15
  TitleType
  b202
  1
  `<TitleType>01<TitleType>` (Distinctive title)

##### Title element composite

A group of data elements which together represent an element of a title. At least one title element is mandatory in each occurrence of the <TitleDetail> composite. The composite is repeatable with different sequence numbers and/or title element levels, each repeat carrying a different part of the title. An instance of the <TitleElement> composite must include at least one of: <PartNumber>; <YearOfAnnual>; <TitleText>, <NoPrefix/> together with <TitleWithoutPrefix>, or <TitlePrefix> together with <TitleWithoutPrefix>. In other words it must carry either the text of a title or a part or year designation, and it may carry both.

A title element must be designated as belonging to product level, collection level, subcollection or sub- subcollection level (the two last-named only in the case of a multi-level collection).

In the simplest case, a product title will consist of a single title element, at product level. However, the composite structure in ONIX 3.0 and 3.1 allows complex titles to be correctly represented, in the sequence in which the publisher wishes the elements to be displayed.

Note that key parts of the Title element – including <TitleText>, <TitleWithoutPrefix> and <Subtitle> – should appear on the title page of the book, or exceptionally on the cover or spine, and should not include any other information. This principle should be followed for all conventional titles, though may not be relevant to, for example, a distributor’s title or the name of an ascribed collection.

  TitleElement
  titleelement
  1…n

##### P.6.1a Title element sequence number

A number which specifies a single overall sequence of title elements, which is the preferred order for display of the various title elements when constructing a complete title. Optional and non-repeating. It is strongly recommended that where there are multiple title elements within a <TitleDetail> composite, each occurrence of the <TitleElement> composite should carry a <SequenceNumber>.

  Positive integer, 1, 2, 3 etc, suggested maximum length 3 digits
  SequenceNumber
  b034
  0…1
  `<b034>2</b034>`

##### P.6.2 Title element level

An ONIX code indicating the level of a title element: collection level, subcollection level, or product level. Mandatory in each occurrence of the <TitleElement> composite, and non-repeating.

  Fixed length, two digits
  List 149
  TitleElementLevel
  x409
  1
  `<x409>02</x409>` (Collection level)

##### P.6.3 Part number

When a title element includes a part designation within a larger whole (eg Part I, or Volume 3), this field should be used to carry the number and its ‘caption’ as text. Optional and non-repeating.

  Variable length text, suggested maximum 20 characters
  PartNumber
  x410
  0…1
  language, textscript
  `<x410>Volume 17</x410>`

##### P.6.4 Year of annual

When the year of an annual is part of a title, this field should be used to carry the year (or, if required, a spread of years such as 2009–2010). Optional and non-repeating.

  Year or range of years, in the format YYYY or YYYY-YYYY
  YearOfAnnual
  b020
  0…1
  `<b020>2009</b020>`

##### P.6.5 Title text

The text of a title element, excluding any subtitle. Optional and non-repeating, may only be used where <TitlePrefix>, <NoPrefix/> and <TitleWithoutPrefix> are not used.

This element is deprecated – except in cases where the language of the title does not use explicit definite or indefinite articles (eg The, A) or where national practice is to include these articles for alphabetic sorting purposes. Other than in such languages, the element is intended to be used only when the sending system cannot reliably provide prefixes that are ignored for sorting purposes in a separate data element. If the system can reliably separate prefixes, it should state whether a prefix is present (using <TitlePrefix> and <TitleWithoutPrefix>) or absent (using <NoPrefix/> and <TitleWithoutPrefix>).

  Variable length text, suggested maximum 300 characters
  TitleText
  b203
  0…1
  collationkey, language, textscript, textcase
  `<b203>Mannen på balkongen</b203>` (Swedish does not use non-sorting articles)

##### P.6.6 Title prefix

Text at the beginning of a title element which is to be ignored for alphabetical sorting. Optional and non-repeating; can only be used when <TitleText> is omitted, and if the <TitleWithoutPrefix> element is also present. These two elements may be used in combination in applications where it is necessary to distinguish an initial word or character string which is to be ignored for filing purposes, eg in library systems and in some bookshop databases.

  Variable length text, suggested maximum 20 characters
  TitlePrefix
  b030
  0…1
  collationkey, language, textscript, textcase
  `<TitlePrefix textcase="01">The</TitlePrefix>`

##### P.6.6a “No prefix” indicator

An empty element that provides a positive indication that a title element does not include any prefix that is ignored for sorting purposes. Optional and non-repeating, and must only be used when <TitleWithoutPrefix> is used and no <TitlePrefix> element is present.

  XML empty element
  NoPrefix/
  x501/
  0…1
  `<NoPrefix/>`

##### P.6.7 Title without prefix

The text of a title element without the title prefix; and excluding any subtitle. Optional and non-repeating; can only be used if one of the <NoPrefix/> or <TitlePrefix> elements is also present.

  Variable length text, suggested maximum 300 characters
  TitleWithoutPrefix
  b031
  0…1
  collationkey, language, textscript, textcase
  `<TitleWithoutPrefix textcase="01">shameful life of Salvador Dali</TitleWithoutPrefix>` (text is in sentence case)

##### P.6.8 Subtitle

The text of a subtitle, if any. ‘Subtitle’ means any added words which appear with the title element given in an occurrence of the <TitleElement> composite, and which amplify and explain the title element, but which are not considered to be part of the title element itself. Optional and non-repeating.

Note that subtitles should appear as they do on the title page of the book (or exceptionally, on the cover). For text that appears on the cover but not on the title page – especially text which is purely promotional – see Group P.14 and in particular, <TextType> codes for Cover line, Endorsement or Promotional headline.

  Variable length text, suggested maximum 300 characters
  Subtitle
  b029
  0…1
  collationkey, language, textscript, textcase
  `<b029 textcase="02">The Russian Revolution 1891–1924</b029>` (text is in title case)

##### End of Title element composite

##### P.6.8a Title statement

Free text showing how the overall title (including any collection level title, if the collection title is treated as part of the product title and included in P.6) should be presented in any display, particularly when a standard concatenation of individual title elements from Group P.6 (in the order specified by the <SequenceNumber> data elements) would not give a satisfactory result. Optional and non-repeating. When this field is sent, the recipient should use it to replace all title detail sent in Group P.6 for display purposes only. The individual title element detail must also be sent, for indexing and retrieval purposes.

  Variable length text, suggested maximum length 1000 characters. XHTML is enabled in this element – see Using XHTML, HTML, XML, JSON within ONIX text fields
  TitleStatement
  x478
  0…1
  language, textformat
  `<TitleStatement>Granta – the magazine of new writing: The Best of Young Spanish Language Novelists</TitleStatement>`

##### End of Title detail composite

  <TitleDetail> composite for a ‘simple’ product title
  using Reference names, title as a single text string |
  --- | ---
  `<NoCollection/>` | For confirmation
  `<TitleDetail>` |
  `<TitleType>01<TitleType>` | Distinctive title
  `<TitleElement>` |
  `<TitleElementLevel>01</TitleElementLevel>` | Product level
  `<TitleText textcase="01">The all-true travels and adventures of Lidie Newton</TitleText>` | Sentence case
  `</TitleElement>` |
  `</TitleDetail>` |

  using Short tags, with prefix and remainder of title text separate |
  --- | ---
  `<x411/>` |
  `<titledetail>` |
  `<b202>01<b202>` |
  `<titleelement>` |
  `<x409>01</x409>` |
  `<b030 textcase="02">The</b030>` | Title case
  `<b031 textcase="02">All-True Travels and Adventures of Lidie Newton</b031>` | Without prefix
  `</titleelement>` |
  `</titledetail>` |

  <TitleDetail> composite for a more ‘complex’ product title
  using Reference names, with collection level title and subtitle |
  --- | ---
  `<TitleDetail>` |
  `<TitleType>01</TitleType>` | Distinctive title
  `<TitleElement>` |
  `<TitleElementLevel>02</TitleElementLevel>` | Collection level
  `<TitleText textcase="02">Granta</TitleText>` | Title case
  `<Subtitle textcase="01">The magazine of new writing</Subtitle>` | Sentence case
  `</TitleElement>` |
  `<TitleElement>` |
  `<TitleElementLevel>01</TitleElementLevel>` | Product level
  `<PartNumber>113</PartNumber>` |
  `<TitlePrefix textcase="02">The</TitlePrefix>` |
  `<TitleWithoutPrefix textcase="02">Best of Young Spanish Language Novelists​</TitleWithoutPrefix>` |
  `</TitleElement>` |
  `<TitleStatement>Granta – the magazine of new writing: The Best of Young Spanish Language Novelists​</TitleStatement>` |
  `</TitleDetail>` |

  using Short tags, and with additional alternative language title |
  --- | ---
  `<titledetail>` |
  `<b202>01</b202>` | Distinctive title
  `<titleelement>` |
  `<x409>02</x409>` | Collection level
  `<b203 textcase="02">Granta</b203>` |
  `<b029 textcase="01">The magazine of new writing</b029>` |
  `</titleelement>` |
  `<titleelement>` |
  `<x409>01</x409>` | Product level
  `<x410>113</x410>` |
  `<b030 textcase="02">The</b030>` |
  `<b031 textcase="02">Best of Young Spanish Language Novelists​</b031>` |
  `</titleelement>` |
  `<x478>Granta – the magazine of new writing: The Best of Young Spanish Language Novelists​</x478>` |
  `</titledetail>` |
  `<titledetail>` |
  `<b202>11</b202>` | Alternative title
  `<titleelement>` |
  `<x409>01</x409>` | Product level
  `<b030 language="spa" textcase="02">Los</b203>` | Title in Spanish
  `<b031 language="spa" textcase="02">Mejores Narradores Jóvenes en Español</b203>` |
  `</titleelement>` |
  `</titledetail>` |

##### P.6.9 Thesis type code

An ONIX code identifying a thesis type, when the ONIX record describes an item which was originally presented as an academic thesis or dissertation. Optional and non-repeating.

  Fixed length, two digits
  List 72
  ThesisType
  b368
  0…1
  `<b368>01</b368>` (Habilitationsschrift, post-doctoral dissertation)

##### P.6.10 Thesis presented to

The name of an academic institution to which a thesis was presented. Optional and non-repeating, but if this element is present, <ThesisType> must also be present.

  Variable length text, suggested maximum length 300 characters
  ThesisPresentedTo
  b369
  0…1
  language

##### P.6.11 Year of thesis

The year in which a thesis was presented. Optional and non-repeating, but if this element is present, <ThesisType> must also be present.

  As specified by the value in the dateformat attribute, or the default of YYYY if the attribute is missing
  ThesisYear
  b370
  0…1
  dateformat
  `<ThesisYear>2002</ThesisYear>`

#### P.7 Authorship

Authorship and other forms of contribution are described by repeats of the <Contributor> composite, within which the recommended form of representation of a person name is the structured data element group consisting of Person name part 1 to Person name part 8. In addition, more than one representation of the same name may be sent: the preferred structured name may be supplemented or replaced by a simple <PersonName> and/or <PersonNameInverted>. Where the contributor is not a person, but is a named group or a corporate contributor, <CorporateName> and/or <CorporateNameInverted> must be used instead.

A single occurrence of the composite may carry both the primary name of a contributor, and one or more alternative names, for example if a contributor is referenced both by their real name and by a pseudonym, or by the name given on the title page and by an authority-controlled name.

A contributor composite is valid in terms of the XML Schema provided it contains at least a <ContributorRole> code and:

- one or more of the forms of representation of a person name, with or without an occurrence of the <NameIdentifier> composite; or
- one or more of the forms of representation of a corporate name, with or without an occurrence of the <NameIdentifier> composite; or
- an <UnnamedPersons> element, with or without an occurrence of the <NameIdentifier> composite; or
- an occurrence of the <NameIdentifier> composite without any accompanying name element(s).

Other elements are optional, except that <ProfessionalAffiliation> should not be used with corporate contributors.

The <ContributorStatement> element may be used to provide a free text statement of the whole of the authorship of the product in the form in which the publisher intends it to be displayed. The individual name detail must still be sent in the <Contributor> composite for indexing and retrieval.

An optional element <NoContributor/> may be used to make a positive statement in an ONIX record that the item has no credited authorship.

##### Contributor composite

A group of data elements which together describe a personal or corporate contributor to the product. Optional, and repeatable to describe multiple contributors.

  Contributor
  contributor
  0…n

##### P.7.1 Contributor sequence number

A number which specifies a single overall sequence of contributor names (across the contributors in Groups P.7 and P.5). Optional and non-repeating. It is strongly recommended that each occurrence of the <Contributor> composite should carry a <SequenceNumber>.

  Positive integer, 1, 2, 3 etc, suggested maximum length 3 digits
  SequenceNumber
  b034
  0…1
  `<b034>3</b034>`

##### P.7.2 Contributor role

An ONIX code indicating the role played by a person or corporate body in the creation of the product. Mandatory in each occurrence of a <Contributor> composite, and may be repeated if the same person or corporate body has more than one role in relation to the product.

  Fixed length, one letter and two digits
  List 17
  ContributorRole
  b035
  1…n
  `<b035>A01</b035>` (Written by)

##### P.7.3 Source language of a translation

Used only when the <ContributorRole> code value is B06, B08 or B10 indicating a translator, to specify the source language from which the translation was made. This element makes it possible to specify a translator’s exact responsibility when a work involves translation from two or more languages. Optional, and repeatable in the event that a single person has been responsible for translation from two or more languages.

  Fixed length, three lower-case letters, based on ISO 639-2/B. Note that ISO 639 specifies that these codes should always be in lower-case
  List 74
  FromLanguage
  x412
  0…n
  `<FromLanguage>eng</FromLanguage>`

##### P.7.4 Target language of a translation

Used only when the <ContributorRole> code value is B06, B08 or B10 indicating a translator, to specify the target language into which the translation was made. This element makes it possible to specify a translator’s exact responsibility when a work involves translation into two or more languages. Optional, and repeatable in the event that a single person has been responsible for translation to two or more languages.

  Fixed length, three lower-case letters, based on ISO 639-2/B. Note that ISO 639 specifies that these codes should always be in lower-case
  List 74
  ToLanguage
  x413
  0…n
  `<x413>swe</x413>`

##### P.7.5 Primary name type

An ONIX code indicating the type of a primary name. Optional, and non-repeating. If omitted, the default is ‘unspecified’ (ie the name as it is presented on the book).

  Fixed length, two digits
  List 18
  NameType
  x414
  0…1
  `<NameType>01</NameType>` (Pseudonym)

##### Name identifier composite

A group of data elements which together specify a name identifier, used here to carry an identifier for a person or organization name given in an occurrence of the <Contributor> composite. Optional: see Group P.7 introductory text for valid options. Repeatable to specify name identifiers of different types for the same person or organization name.

  NameIdentifier
  nameidentifier
  0…n

##### P.7.6 Name identifier type

An ONIX code which identifies the scheme from which the value in the <IDValue> element is taken. Mandatory in each occurrence of the <NameIdentifier> composite, and non-repeating.

  Fixed length, two digits
  List 44
  NameIDType
  x415
  1
  `<x415>01</x415>` (Proprietary)

##### P.7.7 Identifier type name

A name which identifies a proprietary identifier scheme (ie a scheme which is not a standard and for which there is no individual ID type code). Must be included when, and only when, the code in the <NameIDType> element indicates a proprietary scheme. Optional and non-repeating.

  Variable length text, suggested maximum length 100 characters
  IDTypeName
  b233
  0…1
  language
  `<b233>BigPublisher Internal Author ID</b233>`

##### P.7.8 Identifier value

A code value taken from the scheme specified in the <NameIDType> element. Mandatory in each occurrence of the composite, and non-repeating.

  Determined by the scheme specified in <NameIDType>
  IDValue
  b244
  1
  `<b244>7148</b244>`

##### End of Name identifier composite

  supplying an ISNI and the publisher’s internal contributor ID
  using Reference names |
  --- | ---
  `<NameIdentifier>` |
  `<NameIDType>01</NameIDType>` |
  `<IDTypeName>XYZ Author ID</IDTypeName>` |
  `<IDValue>580</IDValue>` |
  `</NameIdentifier>` |
  `<NameIdentifier>` |
  `<NameIDType>16</NameIDType>` |
  `<IDValue>0000000068287141</IDValue>` |
  `</NameIdentifier>` |

  using Short tags |
  --- | ---
  `<nameidentifier>` |
  `<x415>01</x415>` | Proprietary list
  `<b233>XYZ Author ID</b233>` | Name of list
  `<b244>580</b244>` |
  `</nameidentifier>` |
  `<nameidentifier>` |
  `<x415>16</x415>` | ISNI
  `<b244>0000000068287141</b244>` |
  `</nameidentifier>` |

##### P.7.9 Person name

The name of a person who contributed to the creation of the product, unstructured, and presented in normal order. Optional and non-repeating: see Group P.7 introductory text for valid options.

  Variable length text, suggested maximum length 100 characters
  PersonName
  b036
  0…1
  collationkey, language, textscript
  `<PersonName>James J. Johnson III</PersonName>`

##### P.7.10 Person name, inverted

The name of a person who contributed to the creation of the product, presented with the element used for alphabetical sorting placed first (‘inverted order’). Optional and non-repeating: see Group P.7 introductory text for valid options.

  Variable length text, suggested maximum length 100 characters
  PersonNameInverted
  b037
  0…1
  collationkey, language, textscript
  `<b037>Johnson, James J., III</b037>`

##### P.7.11 Person name part 1: titles before names

The first part of a structured name of a person who contributed to the creation of the product: qualifications and/or titles preceding a person’s names, eg ‘Professor’ or ‘HRH Prince’ or ‘Saint’. Optional and non-repeating: see Group P.7 introductory text for valid options.

  Variable length text, suggested maximum length 100 characters
  TitlesBeforeNames
  b038
  0…1
  collationkey, language, textscript
  `<TitlesBeforeNames>HRH Prince</TitlesBeforeNames>`

##### P.7.12 Person name part 2: names before key names

The second part of a structured name of a person who contributed to the creation of the product: name(s) and/or initial(s) preceding a person’s key name(s), eg James J. Optional and non-repeating.

  Variable length text, suggested maximum length 100 characters
  NamesBeforeKey
  b039
  0…1
  collationkey, language, textscript
  `<b039>James J.</b039>`

##### P.7.13 Person name part 3: prefix to key names

The third part of a structured name of a person who contributed to the creation of the product: a prefix which precedes the key name(s) but which is not to be treated as part of the key name, eg ‘van’ in Ludwig van Beethoven. This element may also be used for titles that appear after given names and before key names, eg ‘Lord’ in Alfred, Lord Tennyson. Optional and non-repeating.

  Variable length text, suggested maximum length 100 characters
  PrefixToKey
  b247
  0…1
  collationkey, language, textscript
  `<PrefixToKey>van</PrefixToKey>`

##### P.7.14 Person name part 4: key name(s)

The fourth part of a structured name of a person who contributed to the creation of the product: key name(s), ie the name elements normally used to open an entry in an alphabetical list, eg ‘Smith’ or ‘Garcia Marquez’ or ‘Madonna’ or ‘Francis de Sales’ (in Saint Francis de Sales). Non-repeating. Required if name part elements P.7.11 to P.7.18 are used.

  Variable length text, suggested maximum length 100 characters
  KeyNames
  b040
  0…1
  collationkey, language, textscript
  `<b040>Beethoven</b040>`

##### P.7.15 Person name part 5: names after key names

The fifth part of a structured name of a person who contributed to the creation of the product: name suffix, or name(s) following a person’s key name(s), eg ‘Ibrahim’ (in Anwar Ibrahim). Optional and non-repeating.

  Variable length text, suggested maximum length 100 characters
  NamesAfterKey
  b041
  0…1
  collationkey, language, textscript
  `<b041>Ibrahim</b041>`

##### P.7.16 Person name part 6: suffix after key names

The sixth part of a structured name of a person who contributed to the creation of the product: a suffix following a person’s key name(s), eg ‘Jr’ or ‘III’. Optional and non-repeating.

  Variable length text, suggested maximum length 100 characters
  SuffixToKey
  b248
  0…1
  collationkey, language, textscript
  `<SuffixToKey>Jr.</SuffixToKey>`

##### P.7.17 Person name part 7: qualifications and honors after names

The seventh part of a structured name of a person who contributed to the creation of the product: qualifications and honors following a person’s names, eg ‘CBE FRS’. Optional and non-repeating.

  Variable length text, suggested maximum length 100 characters
  LettersAfterNames
  b042
  0…1
  collationkey, language, textscript
  `<b042>MB FRCS</b042>`

##### P.7.18 Person name part 8: titles after names

The eighth part of a structured name of a person who contributed to the creation of the product: titles following a person’s names, eg ‘Duke of Edinburgh’. Optional and non-repeating.

  Variable length text, suggested maximum length 100 characters
  TitlesAfterNames
  b043
  0…1
  collationkey, language, textscript
  `<TitlesAfterNames>Duke of Edinburgh</TitlesAfterNames>`

##### P.7.19 Corporate contributor name

The name of a corporate body which contributed to the creation of the product, unstructured, and presented in normal order. Optional: see Group P.7 introductory text for valid options. Repeatable, to provide parallel names for a single organization in multiple languages (eg ‘World Health Organization’ and « Organisation mondiale de la santé »).The language attribute is optional for a single instance of <CorporateName>, but must be included in each instance if <CorporateName> is repeated.

  Variable length text, suggested maximum length 200 characters
  CorporateName
  b047
  0…n
  collationkey, language, textscript
  `<CorporateName>Good Housekeeping Institute</CorporateName>`

##### P.7.20 Corporate contributor name, inverted

The name of a corporate body which contributed to the creation of the product, presented in inverted order, with the element used for alphabetical sorting placed first. Optional: see Group P.7 introductory text for valid options. Repeatable, to provide parallel names for a single organization in multiple languages (eg ‘Polar Research Foundation, The’ and ‚Polarforschungsinstitut, Das‘).The language attribute is optional for a single instance of <CorporateNameInverted>, but must be included in each instance if <CorporateNameInverted> is repeated.

  Variable length text, suggested maximum length 200 characters
  CorporateNameInverted
  x443
  0…n
  collationkey, language, textscript
  `<x443>Countryside Commission, The</x443>`

##### P.7.20a Unnamed person(s)

An ONIX code allowing a positive indication to be given when authorship is unknown or anonymous, or when as a matter of editorial policy only a limited number of contributors are named. Optional and non-repeating: see Group P.7 introductory text for valid options.

  Fixed length, two digits
  List 19
  UnnamedPersons
  b249
  0…1
  `<b249>02</b249>` (Anonymous)

##### Alternative name composite

A group of data elements which together represent an alternative name of a contributor, and specify its type. The <AlternativeName> composite is optional, and is repeatable to give multiple alternative names for the contributor. It may be used to send a pseudonym as well as a real name, where both names are on the product, eg to handle such cases as ‘Ian Rankin writing as Jack Harvey’; or to send an authority-controlled form of a name; or to identify the real name of the contributor where the book is written under a pseudonym (and the real identity need not be kept private) or is anonymous. Note that in all cases, the primary name is that used on the product, and the alternative name merely provides additional information.

Each instance of the composite must contain the <NameType> element with either:

- one or more of the forms of representation of a person name, with or without an occurrence of the <NameIdentifier> composite; or
- one or more of the forms of representation of a corporate name, with or without an occurrence of the <NameIdentifier> composite; or
- an occurrence of the <NameIdentifier> composite without any accompanying name element(s).

  AlternativeName
  alternativename
  0…n

##### P.7.21 Alternative name type

An ONIX code indicating the type of the name sent in an occurrence of the <AlternativeName> composite. Mandatory in each occurrence of the composite, and non-repeating.

  Fixed length, two digits
  List 18
  NameType
  x414
  1
  `<x414>01</x414>` (Pseudonym)

##### P.7.22 to P.7.36: other elements in the Alternative name composite

Elements P.7.22 to P.7.36 in the <AlternativeName> composite are identical to P.7.6 to P.7.20 as specified above.

##### End of Alternative name composite

  George Orwell was the pen name of Eric Blair
  using Reference names |
  --- | ---
  `<Contributor>` |
  `<SequenceNumber>1</SequenceNumber>` |
  `<ContributorRole>A01</ContributorRole>` | Author
  `<NamesBeforeKey>George</NamesBeforeKey>` | George Orwell
  `<KeyNames>Orwell</KeyNames>` |
  `<AlternativeName>` |
  `<NameType>04</NameType>` | Real name
  `<NamesBeforeKey>Eric</NamesBeforeKey>` | Eric Blair
  `<KeyNames>Blair</KeyNames>` |
  `</AlternativeName>` |
  `</Contributor>` |

  using Short tags |
  --- | ---
  `<contributor>` |
  `<b034>1</b034>` |
  `<b035>A01</b035>` |
  `<b039>George</b039>` |
  `<b040>Orwell</b040>` |
  `<alternativename>` |
  `<x414>04</x414>` |
  `<b039>Eric</b039>` |
  `<b040>Blair</b040>` |
  `</alternativename>` |
  `</contributor>` |

  ‘writing as’ – both names are on book
  using Reference names |
  --- | ---
  `<Contributor>` |
  `<SequenceNumber>1</SequenceNumber>` |
  `<ContributorRole>A01</ContributorRole>` | Author
  `<NamesBeforeKey>Ian</NamesBeforeKey>` | Ian Rankin
  `<KeyNames>Rankin</KeyNames>` |
  `<AlternativeName>` |
  `<NameType>01</NameType>` | Pseudonym
  `<NamesBeforeKey>Jack</NamesBeforeKey>` | Jack Harvey
  `<KeyNames>Harvey</KeyNames>` |
  `</AlternativeName>` |
  `</Contributor>` |

  using Short tags |
  --- | ---
  `<contributor>` |
  `<b034>1</b034>` |
  `<b035>A01</b035>` |
  `<b039>Ian</b039>` |
  `<b040>Rankin</b040>` |
  `<alternativename>` |
  `<x414>01</x414>` |
  `<b039>Jack</b039>` |
  `<b040>Harvey</b040>` |
  `</alternativename>` |
  `</contributor>` |

##### Contributor date composite

A group of data elements which together specify a date associated with the person or organization identified in an occurrence of the <Contributor> composite, eg birth or death. Optional, and repeatable to allow multiple dates to be specified.

  ContributorDate
  contributordate
  0…n

##### P.7.37 Contributor date role code

An ONIX code indicating the significance of the date in relation to the contributor name. Mandatory in each occurrence of the <ContributorDate> composite, and non-repeating.

  Fixed length, two digits
  List 177
  ContributorDateRole
  x417
  1
  `<ContributorDateRole>50</ContributorDateRole>` (Date of birth)

##### P.7.39 Date

The date specified in the <ContributorDateRole> field. Mandatory in each occurrence of the <ContributorDate> composite, and non-repeating. <Date> may carry a dateformat attribute: if the attribute is missing, then the default format is YYYYMMDD.

  As specified by the value in the dateformat attribute, or the default YYYYMMDD
  Date
  b306
  1
  dateformat
  `<Date>20010106</Date>`

##### End of Contributor date composite

##### Professional affiliation composite

An optional group of data elements which together identify a contributor’s professional position and/or affiliation, repeatable to allow multiple positions and affiliations to be specified.

  ProfessionalAffiliation
  professionalaffiliation
  0…n

##### P.7.40 Professional position

A professional position held by a contributor to the product at the time of its creation. Optional, and repeatable to provide parallel text in multiple languages. The language attribute is optional for a single instance of <ProfessionalPosition>, but must be included in each instance if <ProfessionalPosition> is repeated.

  Variable length text, suggested maximum length 100 characters
  ProfessionalPosition
  b045
  0…n
  language
  `<b045>Humboldt Professor of Oceanography</b045>`

##### Affiliation identifier composite

A group of data elements which together define an identifier for an organization to which the contributor to the product was affiliated at the time of its creation, and – if the <ProfessionalPosition> element is also present – where the contributor held that position. Optional, and repeatable to specify organization identifiers of different types for the same organization.

  AffiliationIdentifier
  affiliationidentifier
  0…n

##### P.7.40a Affiliation identifier type

An ONIX code which identifies the scheme from which the value in the <IDValue> element is taken. Mandatory in each occurrence of the <AffiliationIdentifier> composite, and non-repeating.

  Fixed length text, two digits
  List 44
  AffiliationIDType
  x580
  1
  `<x580>16</x580>` (ISNI)

##### P.7.40b Identifier type name

A name which identifies a proprietary identifier scheme (ie a scheme which is not a standard and for which there is no individual ID type code). Must be included when, and only when, the code in the <AffiliationIDType> element indicates a proprietary scheme. Optional and non-repeating.

  Variable length text, suggested maximum length 100 characters
  IDTypeName
  b233
  0…1
  language
  `<b233>Wellcome Internal Org ID</b233>`

##### P.7.40c Identifier value

A code value taken from the scheme specified in the <AffiliationIDType> element. Mandatory in each occurrence of the composite, and non-repeating.

  Determined by the scheme specified in <AffiliationIDType>
  IDValue
  b244
  1
  `<b244>0000000121060879</b244>` (ISNI of Universidad de La Laguna)

##### End of Affiliation identifier composite

##### P.7.41 Affiliation

An organization to which a contributor to the product was affiliated at the time of its creation, and – if the <ProfessionalPosition> element is also present – where the contributor held that position. Optional and non-repeating.

  Variable length text, suggested maximum length 200 characters
  Affiliation
  b046
  0…1
  language
  `<b046 language="spa">Universidad de La Laguna</b046>`

##### End of Professional affiliation composite

##### Prize composite

An optional group of data elements which together describe a prize or award won by the contributor for a body of work (rather than for this or other specific works or products). Repeatable to describe multiple prizes or awards.

  Prize
  prize
  0…n

##### P.7.41a to P.7.41l: elements in the Prize composite

Elements P.7.41a to P.7.41l in the <Prize> composite are identical to P.17.1 to P.17.5 as specified in Group P.17. Note that the prize’s <SequenceNumber> should indicate the sequence within the context of the contributor’s prizes only.

##### End of Prize composite

##### P.7.42 Biographical note

A biographical note about a contributor to the product. (See the <TextContent> composite in Group P.14 for a biographical note covering all contributors to a product in a single text.) Optional, and repeatable to provide parallel biographical notes in multiple languages. The language attribute is optional for a single instance of <BiographicalNote>, but must be included in each instance if <BiographicalNote> is repeated. May occur with a person name or with a corporate name. A biographical note in ONIX should always contain the name of the person or body concerned, and it should always be presented as a piece of continuous text consisting of full sentences. Some recipients of ONIX data feeds will not accept text which has embedded URLs. A contributor website link can be sent using the <Website> composite below.

  Variable length text, no suggested maximum length (since there is no suggested length for the text in a <TextContent> composite, where a biographical note can alternatively be sent). XHTML is enabled in this element – see Using XHTML, HTML, XML, JSON within ONIX text fields
  BiographicalNote
  b044
  0…n
  language, textformat
  `<b044 language="eng" textformat="05"><p><strong>Umberto Eco</strong>, professor of semiotics at the University of Bologna, and author of <cite>The Name Of The Rose</cite> and <cite>Foucault’s Pendulum</cite>, is one of the world’s bestselling novelists.</p><p>As well as novels, he also writes children’s books and academic works.</p></b044>`
  `<b044 language="ita" textformat="05"><p><strong>Umberto Eco</strong>, professore di semiotica all’Università di Bologna e autore di <cite>Il nome della rosa</cite> e <cite>Il pendolo di Foucault</cite>, è uno dei romanzieri più venduto al mondo.</p><p>Così come romanzi, lui scrive anche libri per bambini e opere accademici.</p></b044>` (text is marked up with XHTML, and both English and Italian versions are provided)
  `<b044>Umberto Eco, professor of semiotics at the University of Bologna, and author of ‘The Name Of The Rose’ and ‘Foucault’s Pendulum’, is one of the world’s bestselling novelists. As well as novels, he also writes children’s books and academic works.</b044>` (text is not marked up)
  Beware of biographical notes including phrases such as ‘her latest work is…’, as they are somewhat time-sensitive, and consider the use of the datestamp attribute if such phrases cannot be avoided.

##### Website composite

An optional group of data elements which together identify and provide a pointer to a website which is related to the person or organization identified in an occurrence of the <Contributor> composite. Repeatable to provide links to multiple websites.

  Website
  website
  0…n

##### P.7.43 Website purpose

An ONIX code which identifies the role or purpose of the website which is linked through the <WebsiteLink> element. Optional and non-repeating.

  Fixed length, two digits
  List 73
  WebsiteRole
  b367
  0…1
  `<b367>07</b367>` (Publisher’s website relating to specified contributor)

##### P.7.44 Website description

Free text describing the nature of the website which is linked through the <WebsiteLink> element. Optional, and repeatable to provide parallel descriptive text in multiple languages. The language attribute is optional for a single instance of <WebsiteDescription>, but must be included in each instance if <WebsiteDescription> is repeated.

  Variable length text, suggested maximum length 300 characters. XHTML is enabled in this element – see Using XHTML, HTML, XML, JSON within ONIX text fields
  WebsiteDescription
  b294
  0…n
  language, textformat
  `<b294>Includes author bio, gallery of photos, interview, complete bibliography and links to download book covers as mobile phone wallpapers</b294>`

##### P.7.45 Link to website

The URL for the website. Mandatory in each occurrence of the <Website> composite, and repeatable to provide multiple URLs where the website content is available in multiple languages. The language attribute is optional for a single instance of <WebsiteLink>, but must be included in each instance if <WebsiteLink> is repeated.

  Uniform Resource Locator, expressed in full URI syntax in accordance with W3C standards, suggested maximum length 300 characters. Note that non-ASCII characters, spaces and a handful of other special characters should be ‘URL-encoded’. Any ampersand used to separate parameters in the URL must be expressed as &amp;
  WebsiteLink
  b295
  1…n
  language
  `<b295>https://xyzbooks.com/joe_bloggs.htm</b295>`

##### End of Website composite

  using Reference names |
  --- | ---
  `<Website>` |
  `<WebsiteRole>06</WebsiteRole>` |
  `<WebsiteLink>https://www.jkrowling.com/</WebsiteLink>` |
  `</Website>` |

  using Short tags |
  --- | ---
  `<website>` |
  `<b367>06</b367>` | Contributor’s own website
  `<b295>https://www.jkrowling.com/</b295>` |
  `</website>` |

##### P.7.46 Contributor description

Brief text describing a contributor to the product, at the publisher’s discretion. Optional, and repeatable to provide parallel descriptions in multiple languages. The language attribute is optional for a single instance of <ContributorDescription>, but must be included in each instance if <ContributorDescription> is repeated. It may be used with either a person or corporate name, to draw attention to any aspect of a contributor’s background which supports the promotion of the book.

  Variable length text, suggested maximum length 200 characters. XHTML is enabled in this element – see Using XHTML, HTML, XML, JSON within ONIX text fields
  ContributorDescription
  b048
  0…n
  language, textformat
  `<ContributorDescription>Skipper of the winning crew in the Americas Cup, 1998</ContributorDescription>`

##### Contributor place composite

An optional group of data elements which together identify a geographical location with which a contributor is associated, used to support ‘local interest’ promotions. Repeatable to identify multiple geographical locations, each usually with a different relationship to the contributor.

  ContributorPlace
  contributorplace
  0…n

##### P.7.48 Contributor place relator

An ONIX code identifying the relationship between a contributor and a geographical location. Mandatory in each occurrence of <ContributorPlace> and non-repeating.

  Fixed length, two digits
  List 151
  ContributorPlaceRelator
  x418
  1
  `<x418>01</x418>` (Born in)

##### P.7.49 Country code

An ONIX code identifying a country with which a contributor is particularly associated. Optional and non-repeatable. There must be an occurrence of either the <CountryCode> or the <RegionCode> elements in each occurrence of <ContributorPlace>.

  Fixed length, two letters, based on ISO 3166-1. Note that ISO 3166-1 specifies that country codes shall be sent as upper case only
  List 91
  CountryCode
  b251
  0…1
  `<CountryCode>US</CountryCode>`

##### P.7.50 Region code

An ONIX code identifying a region with which a contributor is particularly associated. Optional and non-repeatable. There must be an occurrence of either the <CountryCode> or the <RegionCode> elements in each occurrence of <ContributorPlace>. A region is an area which is not a country, but which is precisely defined in geographical terms, eg Northern Ireland, Australian Capital Territory. If both country and region are specified, the region must be within the country. Note that US States have region codes, while US overseas territories have distinct ISO Country Codes.

  Variable length code, consisting of upper case letters, with or without a hyphen and further upper case letters or digits. Suggested maximum length 8 characters
  List 49 Where possible and appropriate, country subdivision codes are derived from the UN LOCODE scheme based on ISO 3166-2
  RegionCode
  b398
  0…1
  `<RegionCode>CA-NL</RegionCode>` (Newfoundland and Labrador)

##### P.7.50a Location name

The name of a city or town location within the specified country or region with which a contributor is particularly associated. Optional, and repeatable to provide parallel names for a single location in multiple languages (eg Baile Átha Cliath and Dublin, or Bruxelles and Brussel). The language attribute is optional for a single instance of <LocationName>, but must be included in each instance if <LocationName> is repeated.

  Variable length text, suggested maximum length 100 characters
  LocationName
  j349
  0…n
  language
  `<j349>Stephenville</j349>`

##### End of Contributor place composite

##### End of Contributor composite

##### P.7.51 Contributor statement

Free text showing how the authorship should be described in an online display, when a standard concatenation of individual contributor elements would not give a satisfactory presentation. Optional but must only be used if one or more instances of <Contributor> are present, and repeatable if parallel text is provided in multiple languages. The language attribute is optional for a single instance of <ContributorStatement>, but must be included in each instance if <ContributorStatement> is repeated. When the <ContributorStatement> field is sent, the receiver should use it to replace all name detail sent in the <Contributor> composite for display purposes only. It does not replace the <Contributor> composite (or any element within it) for individual contributors. The individual name detail must also be sent in the <Contributor> composite for indexing and retrieval purposes.

  Variable length text, suggested maximum length 1000 characters. XHTML is enabled in this element – see Using XHTML, HTML, XML, JSON within ONIX text fields
  ContributorStatement
  b049
  0…n
  language, textformat
  `<b049>Written and illustrated by Fred and Emily Jackson</b049>`

##### P.7.52 “No authorship” indicator

An empty element that provides a positive indication that a product has no stated authorship. Intended to be used in an ONIX accreditation scheme to confirm that author information is being consistently supplied in publisher ONIX feeds. Optional and non-repeating. Must only be sent in a record that has no other elements from Group P.7.

  XML empty element
  NoContributor/
  n339/
  0…1
  `<NoContributor/>`

#### P.8 Event

Data element Group P.8 describes an event or multiple events to which the product is related – for example when the book is the proceedings of a conference, or commemorates a particular event.

Note this Group was formerly known as P.8 Conference.

##### Event composite

A group of data elements which together describe an event to which the product is related. Optional, and repeatable if the product contains material from or is related to two or more events.

  Event
  event
  0…n

##### P.8.16 Event role

An ONIX code which indicates the relationship between the product and an event to which it is related, eg Proceedings of conference / Selected papers from conference / Programme for sporting event / Guide for art exhibition. Mandatory and non-repeating.

  Fixed length, two digits
  List 20
  EventRole
  x515
  1
  `<x515>03</x515>` (Selected papers from conference)

##### P.8.17 Event name

The name of an event or series of events to which the product is related. This element is mandatory in each occurrence of the <Event> composite, and repeatable to provide parallel names for a single event in multiple languages (eg ‘United Nations Climate Change Conference’ and « Conférences des Nations unies sur les changements climatiques »). The language attribute is optional for a single instance of <EventName>, but must be included in each instance if <EventName> is repeated.

  Variable length text, suggested maximum length 200 characters
  EventName
  x516
  1…n
  language
  `<x516 language="fre">Conférences des Nations unies sur les changements climatiques</x516>` (United Nations Climate Change Conference)

##### P.8.18 Event acronym

An acronym used as a short form of the name of an event or series of events given in the <EventName> element. Optional, and repeatable to provide parallel acronyms for a single event in multiple languages. The language attribute is optional for a single instance of <EventAcronym>, but must be included in each instance if <EventAcronym> is repeated.

  Variable length text, suggested maximum length 20 characters
  EventAcronym
  x517
  0…n
  language
  `<EventAcronym>UNFCCC COP21</EventAcronym>`

##### P.8.19 Event number

The number of an event to which the product is related, within a series of events. Optional and non-repeating.

  Positive integer, suggested maximum length 4 digits
  EventNumber
  x518
  0…1
  `<x518>21</x518>`

##### P.8.20 Event thematic title

The thematic title of an individual event in a series that has an event series name in the <EventName> element. Optional, and repeatable to provide parallel thematic titles for a single event in multiple languages. The language attribute is optional for a single instance of <EventTheme>, but must be included in each instance if <EventTheme> is repeated.

  Variable length text, suggested maximum length 200 characters
  EventTheme
  x519
  0…n
  language
  `<EventTheme>Building a better world</EventTheme>`

##### P.8.21 Event date

The date of an event to which the product is related. Optional and non-repeating.

  As specified by the value in the dateformat attribute, or the default of YYYY if the attribute is missing. Note that the dateformat attribute allows exact dates to be supplied if necessary, including the cases where an event spreads over a range of dates or the date can only be supplied as a text string
  EventDate
  x520
  0…1
  dateformat
  `<EventDate dateformat="06">2015113020151215</EventDate>` (30 November–15 December 2015)

##### P.8.22 Event place

The place of an event to which the product is related. Optional, and repeatable to provide parallel placenames for a single location in multiple languages. The language attribute is optional for a single instance of <EventPlace>, but must be included in each instance if <EventPlace> is repeated.

  Variable length text, suggested maximum length 100 characters
  EventPlace
  x521
  0…n
  language
  `<EventPlace>Aix-les-Bains, France</EventPlace>`

##### Event sponsor composite

An optional group of data elements which together identify an organizer or sponsor of an event. Either an identifier, or one or other of <PersonName> or <CorporateName>, or both an identifier and a name, must be present in each occurrence of the composite. The composite is repeatable in order to specify multiple organizers and sponsors.

  EventSponsor
  eventsponsor
  0…n

##### Event sponsor identifier composite

An optional and repeatable group of data elements which together carry a coded identifier for an organizer or sponsor of an event.

  EventSponsorIdentifier
  eventsponsoridentifier
  0…n

##### P.8.23 Event sponsor identifier type

An ONIX code which identifies the scheme from which the value in the <IDValue> element is taken. Mandatory in each occurrence of the <EventSponsorIdentifier> composite, and non-repeating.

  Fixed length, two digits
  List 44
  EventSponsorIDType
  x522
  1
  `<x522>01</x522>` (Proprietary)

##### P.8.24 Identifier type name

A name which identifies a proprietary identifier scheme when, and only when, the code in the <EventSponsorIDType> element indicates a proprietary scheme. Optional and non-repeating.

  Variable length text, suggested maximum length 100 characters
  IDTypeName
  b233
  0…1
  language

##### P.8.25 Identifier value

A code value taken from the scheme specified in the <EventSponsorIDType> element. Mandatory in each occurrence of the composite, and non-repeating.

  Determined by the scheme specified in <EventSponsorIDType>
  IDValue
  b244
  1

##### End of Event sponsor identifier composite

##### P.8.26 Person name

The name of a person, used here for a personal organizer or sponsor of an event. Optional and non-repeating. Only one of <PersonName> or <CorporateName> can be sent in each occurrence of the <EventSponsor> composite.

  Variable length text, suggested maximum length 100 characters
  PersonName
  b036
  0…1
  collationkey, language, textscript
  `<PersonName>James J. Johnson III</PersonName>`

##### P.8.27 Corporate name

The name of a corporate body, used here for a corporate organizer or sponsor of an event. Optional and non-repeating. Only one of <PersonName> or <CorporateName> can be sent in each occurrence of the <EventSponsor> composite.

  Variable length text, suggested maximum length 200 characters
  CorporateName
  b047
  0…1
  collationkey, language, textscript
  `<b047>Johnson &amp; Johnson</b047>` (note ‘&’ is a reserved character in XML)

##### End of Event sponsor composite

##### Website composite

An optional group of data elements which together identify and provide a pointer to a website which is related to the event identified in an occurrence of the <Event> composite. Repeatable in order to provide links to multiple websites.

  Website
  website
  0…n

##### P.8.28 Website purpose

An ONIX code which identifies the role or purpose of the website which is linked through the <WebsiteLink> element. Optional and non-repeating.

  Fixed length, two digits
  List 73
  WebsiteRole
  b367
  0…1
  `<WebsiteRole>04</WebsiteRole>` (Journal home page)

##### P.8.29 Website description

Free text describing the nature of the website which is linked through the <WebsiteLink> element. Optional, and repeatable to provide parallel descriptive text in multiple languages. The language attribute is optional for a single instance of <WebsiteDescription>, but must be included in each instance if <WebsiteDescription> is repeated.

  Variable length text, suggested maximum length 300 characters. XHTML is enabled in this element – see Using XHTML, HTML, XML, JSON within ONIX text fields
  WebsiteDescription
  b294
  0…n
  language, textformat

##### P.8.30 Link to website

The URL for the website. Mandatory in each occurrence of the <Website> composite, and repeatable to provide multiple URLs where the website content is available in multiple languages. The language attribute is optional for a single instance of <WebsiteLink>, but must be included in each instance if <WebsiteLink> is repeated.

  Uniform Resource Locator, expressed in full URI syntax in accordance with W3C standards, suggested maximum length 300 characters. Note that non-ASCII characters, spaces and a handful of other special characters should be ‘URL-encoded’. Any ampersand used to separate parameters in the URL must be expressed as &amp;
  WebsiteLink
  b295
  1…n
  language
  `<b295 language="spa">https://www.xyzsociety.com/es/conferencia%20anual.htm</b295>` (file is named ‘conferencia anual.htm’)

##### End of Website composite

##### End of Event composite

#### P.9 Edition

Data element Group P.9 describes an edition or version of a derived work which is manifested in the product. Edition information is often closely related to – but is not a part of – the title of the product. Its use should generally be limited to describing an edition or version whose content is materially different from an earlier source work (eg a ‘third edition’, an ‘abridged edition’). However, it may sometimes be used to specify a product feature (eg ‘bilingual edition’, ‘large print edition’) without necessarily implying that another, different, edition also exists.

##### P.9.1 Edition type code

An ONIX code, indicating the type of a version or edition. Optional, and repeatable if the product has characteristics of two or more types (eg ‘revised’ and ‘annotated’).

  Fixed length, three upper-case letters
  List 21
  EditionType
  x419
  0…n
  `<EditionType>ILL</EditionType>` (Illustrated edition)

##### P.9.2 Edition number

The number of a numbered edition. Optional and non-repeating. Normally sent only for the second and subsequent editions, but by agreement between parties to an ONIX exchange or when a first and a subsequent edition are available at the same time, a first edition may be explicitly numbered.

  Positive integer, suggested maximum length 4 digits
  EditionNumber
  b057
  0…1
  `<b057>3</b057>` (Third edition)

##### P.9.3 Edition version number

The number of a numbered revision within an edition number. To be used only where a publisher uses such two-level numbering to indicate revisions which do not constitute a new edition under a new ISBN or other distinctive product identifier. Optional and non-repeating. If this field is used, an <EditionNumber> must also be present.

  Variable length text, suggested maximum length 50 characters
  EditionVersionNumber
  b217
  0…1
  `<b217>2</b217>` (Second revised impression of this edition)

##### P.9.4 Edition statement

A short free-text description of a version or edition. Optional, and repeatable if parallel text is provided in multiple languages. The language attribute is optional for a single instance of <EditionStatement>, but must be included in each instance if <EditionStatement> is repeated. When used, an <EditionStatement> must be complete in itself, ie it should not be treated as merely supplementary to an <EditionType> or an <EditionNumber>, nor as a replacement for them. Appropriate edition type and number must also be sent, for indexing and retrieval. An <EditionStatement> should be strictly limited to describing features of the content of the edition, and should not include aspects such as rights or market restrictions which are properly covered elsewhere in the ONIX record.

  Variable length text, suggested maximum length 200 characters. XHTML is enabled in this element – see Using XHTML, HTML, XML, JSON within ONIX text fields
  EditionStatement
  b058
  0…n
  language, textformat
  `<b058>3rd edition, revised with an introduction and notes</b058>`

##### P.9.5 “No edition” indicator

An empty element that provides a positive indication that a product does not carry any edition information. Intended to be used in an ONIX accreditation scheme to confirm that edition information is being consistently supplied in publisher ONIX feeds. Optional and non-repeating. Must only be sent in a record that has no instances of any of the four preceding Edition elements.

  XML empty element
  NoEdition/
  n386/
  0…1
  `<NoEdition/>`

##### Religious text composite

An optional, non-repeating, group of data elements which together describe features of the content of an edition of a religious text, and intended to meet the special needs of religious publishers and booksellers. The <ReligiousText> composite may carry either a <Bible> composite or a <ReligiousTextIdentifier> element accompanied by multiple repeats of the <ReligiousTextFeature> composite. This approach is adopted to enable other devotional texts to be included if need arises without requiring a new ONIX release.

  ReligiousText
  religioustext
  0…1

##### Bible composite

A group of data elements which together describe features of an edition of the Bible or of a selected Biblical text. Mandatory in each occurrence of the <ReligiousText> composite that does not include a <ReligiousTextIdentifier> element, and non-repeating.

  Bible
  bible
  0…1

##### P.9.6 Bible contents

An ONIX code indicating the content of an edition of the Bible or selected Biblical text, for example ‘New Testament’, ‘Apocrypha’, ‘Pentateuch’. Mandatory in each occurrence of the <Bible> composite, and repeatable so that a list such as ‘Old Testament and Apocrypha’ can be expressed.

  Fixed length, two letters
  List 82
  BibleContents
  b352
  1…n
  `<b352>OT</b352>` (Old Testament)

##### P.9.7 Bible version

An ONIX code indicating the version of a Bible or selected Biblical text, for example ‘King James’, ‘Jerusalem’, ‘New American Standard’, ‘Reina Valera’. Mandatory in each occurrence of the <Bible> composite, and repeatable if a work includes text in two or more versions.

  Fixed length, three letters
  List 83
  BibleVersion
  b353
  1…n
  `<BibleVersion>JER</BibleVersion>` (Jerusalem)

##### P.9.8 Study Bible type

An ONIX code identifying a particular study version of a Bible or selected Biblical text, for example ‘Life Application’. Optional and non-repeating. Some study Bibles are available in different editions based on different text versions.

  Fixed length, three letters
  List 84
  StudyBibleType
  b389
  0…1
  `<b389>OXF</b389>` (Oxford Annotated)

##### P.9.9 Bible purpose

An ONIX code indicating the purpose for which a Bible or selected Biblical text is intended, for example ‘Family’, ‘Lectern/pulpit’. Optional, and repeatable to list multiple purposes.

  Fixed length, two letters
  List 85
  BiblePurpose
  b354
  0…n
  `<BiblePurpose>LP</BiblePurpose>` (Lectern/pulpit)

##### P.9.10 Bible text organization

An ONIX code indicating the way in which the content of a Bible or selected Biblical text is organized, for example ‘Chronological’, ‘Chain reference’. Optional and non-repeating.

  Fixed length, three letters
  List 86
  BibleTextOrganization
  b355
  0…1
  `<b355>CHA</b355>` (Chain reference)

##### P.9.11 Bible reference location

An ONIX code indicating where references are located as part of the content of a Bible or selected Biblical text, for example ‘Center column’. Optional and non-repeating.

  Fixed length, three letters
  List 87
  BibleReferenceLocation
  b356
  0…1
  `<b356>CCL</b356>` (Center column)

##### P.9.12 Bible text feature

An ONIX code specifying a feature of a Bible text not covered elsewhere, eg red letter. Optional, and repeatable to specify multiple features.

  Fixed length, two letters
  List 97
  BibleTextFeature
  b357
  0…n
  `<BibleTextFeature>RL</BibleTextFeature>` (Red letter)

##### End of Bible composite

##### P.9.13 Religious text identifier

An ONIX code indicating a religious text other than the Bible. Mandatory in each occurrence of the <ReligiousText> composite that does not include a <Bible> composite, and non-repeating.

  Fixed length, two digits
  List 88
  ReligiousTextIdentifier
  b376
  0…1

##### Religious text feature composite

A repeatable group of data elements which together specify and describe a feature of a religious text. Mandatory if and only if <ReligiousTextIdentifier> is present.

  ReligiousTextFeature
  religioustextfeature
  0…n

##### P.9.14 Religious text feature type

An ONIX code specifying a feature described in the associated <ReligiousTextFeatureCode> element. Mandatory in each occurrence of the <ReligiousTextFeature> composite, and non-repeating.

  Fixed length, two digits
  List 89
  ReligiousTextFeatureType
  b358
  1
  `<b358>01</b358>` (Church season or activity)

##### P.9.15 Religious text feature code

An ONIX code describing a feature specified in the associated <ReligiousTextFeatureType> element. Mandatory in each occurrence of the <ReligiousTextFeature> composite, and non-repeating.

  Fixed length, two digits
  List 90
  ReligiousTextFeatureCode
  b359
  1
  `<ReligiousTextFeatureCode>10</ReligiousTextFeatureCode>` (Lent)

##### P.9.16 Religious text feature description

Free text describing a feature that is not adequately defined by code values alone. Optional, and repeatable if parallel descriptive text is provided in multiple languages. The language attribute is optional for a single instance of <ReligiousTextFeatureDescription>, but must be included in each instance if <ReligiousTextFeatureDescription> is repeated.

  Variable length text, suggested maximum 100 characters. XHTML is enabled in this element – see Using XHTML, HTML, XML, JSON within ONIX text fields
  ReligiousTextFeatureDescription
  b360
  0…n
  language, textformat

##### End of Religious text feature composite

##### End of Religious text composite

#### P.10 Language

These elements specify the language(s) of the text of a product and/or of an original work of which it is a translation. Group P.10 is optional, but is strongly recommended. A default language of text can be declared in an ONIX message header – see Header field H.17 – but this is deprecated. Where applicable, the national or regional variation of the language as well as the script in which the language is represented can also be specified.

##### Language composite

A group of data elements which together represent a language, and specify its role and, where required, whether it is a country variant. Optional, and repeatable to specify multiple languages and their various roles.

  Language
  language
  0…n

##### P.10.1 Language role

An ONIX code indicating the ‘role’ of a language in the context of the ONIX record. Mandatory in each occurrence of the <Language> composite, and non-repeating.

  Fixed length, two digits
  List 22
  LanguageRole
  b253
  1
  `<LanguageRole>01</LanguageRole>` (Language of text)

##### P.10.2 Language code

An ONIX code indicating a language. Mandatory in each occurrence of the <Language> composite, and non-repeating.

  Fixed length, three lower-case letters, based on ISO 639-2/B. Note that ISO 639 specifies that these codes should always be in lower-case
  List 74
  LanguageCode
  b252
  1
  `<b252>eng</b252>` (English)

##### P.10.3 Country code

An ONIX code identifying a country when this specifies a variant of the language, eg US English. Optional and non-repeating.

  Fixed length, two letters, based on ISO 3166-1. Note that ISO 3166-1 specifies that country codes shall be sent as upper case only
  List 91
  CountryCode
  b251
  0…1
  `<CountryCode>US</CountryCode>` (US [English])

##### P.10.3a Region code

An ONIX code identifying the region when this specifies a variant of the language eg Flemish – Dutch as used in the Flemish region of Belgium. Optional and non-repeatable. A region is an area which is not a country (in the sense that it does not have a distinct country code), but which is precisely defined in geographical terms, eg Quebec, Scotland. In general, if a region is specified, the country may be omitted. If both country and region are specified, the region must be within the country. Note that US States have region codes, while US overseas territories have distinct ISO Country Codes.

  Variable length code, consisting of upper case letters, with or without a hyphen and further upper case letters or digits. Suggested maximum length 8 characters
  List 49 Where possible and appropriate, country subdivision codes are derived from the UN LOCODE scheme based on ISO 3166-2
  RegionCode
  b398
  0…1
  `<RegionCode>BE-VLG</RegionCode>` (Flemish region)

##### P.10.4 Script code

An ONIX code identifying the script in which the language is represented. Optional and non-repeating.

  Fixed length, four letters, based on ISO 15924. Note that ISO 15924 specifies that script codes shall be sent as one upper case followed by three lower case letters
  List 121
  ScriptCode
  x420
  0…1
  `<ScriptCode>Cyrl</ScriptCode>` (Cyrillic)

##### End of Language composite

  product is in French, translated from original work in Old Norse
  using Reference names |
  --- | ---
  `<Language>` |
  `<LanguageRole>01</LanguageRole>` |
  `<LanguageCode>fre</LanguageCode>` |
  `</Language>` |
  `<Language>` |
  `<LanguageRole>02</LanguageRole>` |
  `<LanguageCode>non</LanguageCode>` |
  `</Language>` |

  using Short tags |
  --- | ---
  `<language>` |
  `<b253>01</b253>` | Language of text
  `<b252>fre</b252>` |
  `</language>` |
  `<language>` |
  `<b253>02</b253>` | Language of original
  `<b252>non</b252>` |
  `</language>` |

#### P.11 Extents and other content

Group P.11 covers product extents, in terms of pages, running times, file sizes etc, as may be appropriate to each media type. For products whose content is primarily readable text, it also covers illustrations and other kinds of ancillary matter such as the inclusion of a bibliography or index.

##### Extent composite

A group of data elements which together describe an extent pertaining to the product. Optional, but in practice required for most products, eg to give the number of pages in a printed book or paginated e‑book, or to give the running time of an audiobook. Repeatable to specify different extent types or units.

  Extent
  extent
  0…n

##### P.11.1 Extent type code

An ONIX code which identifies the type of extent carried in the composite, eg running time for an audio or video product. Mandatory in each occurrence of the <Extent> composite, and non-repeating. From Issue 9 of the code lists, an extended set of values for <ExtentType> has been defined to allow more accurate description of pagination.

  Fixed length, two digits
  List 23
  ExtentType
  b218
  1
  `<ExtentType>09</ExtentType>` (Duration [running time])

##### P.11.2 Extent value

The numeric value of the extent specified in <ExtentType>. Optional, and non-repeating. However, either <ExtentValue> or <ExtentValueRoman>, or both, must be present in each occurrence of the <Extent> composite; and it is very strongly recommended that <ExtentValue> should always be included, even when the original product uses Roman numerals.

  Positive real number, with explicit decimal point when required, as appropriate for the units specified in <ExtentUnit>. Suggested maximum length 8 characters
  ExtentValue
  b219
  0…1
  `<b219>2.5</b219>`

##### P.11.3 Extent value in Roman numerals

The value of the extent expressed in Roman numerals. Optional, and non-repeating. Used only for page runs which are numbered in Roman.

  Letters forming a valid Roman numeral
  ExtentValueRoman
  x421
  0…1
  `<ExtentValueRoman>xxiii</ExtentValueRoman>` (23)

##### P.11.4 Extent unit

An ONIX code indicating the unit used for the <ExtentValue> and the format in which the value is presented. Mandatory in each occurrence of the <Extent> composite, and non-repeating.

  Fixed length, two digits
  List 24
  ExtentUnit
  b220
  1
  `<b220>04</b220>` (Hours as integer and decimals)

##### End of Extent composite

  use of Main content page count
  using Reference names |
  --- | ---
  `<Extent>` |
  `<ExtentType>00</ExtentType>` | Main content pages
  `<ExtentValue>260</ExtentValue>` |
  `<ExtentUnit>03</ExtentUnit>` | Pages
  `</Extent>` |

  using Short tags |
  --- | ---
  `<extent>` |
  `<b218>00</b218>` |
  `<b219>260</b219>` |
  `<b220>03</b220>` |
  `</extent>` |

  Front matter and Main content page count
  using Reference names |
  --- | ---
  `<Extent>` |
  `<ExtentType>03</ExtentType>` | Front matter pages
  `<ExtentValue>23</ExtentValue>` | In Arabic numerals
  `<ExtentValueRoman>xxiii</ExtentValueRoman>` | In Roman numerals
  `<ExtentUnit>03</ExtentUnit>` | Pages
  `</Extent>` |
  `<Extent>` |
  `<ExtentType>00</ExtentType>` | Main content pages
  `<ExtentValue>260</ExtentValue>` |
  `<ExtentUnit>03</ExtentUnit>` | Pages
  `</Extent>` |

  using Short tags |
  --- | ---
  `<extent>` |
  `<b218>03</b218>` |
  `<b219>23</b219>` |
  `<x421>xxiii</x421>` |
  `<b220>03</b220>` |
  `</extent>` |
  `<extent>` |
  `<b218>00</b218>` |
  `<b219>260</b219>` |
  `<b220>03</b220>` |
  `</extent>` |

  Running time eg of an audiobook
  using Reference names, time in hours and minutes |
  --- | ---
  `<Extent>` |
  `<ExtentType>09</ExtentType>` | Duration
  `<ExtentValue>00305</ExtentValue>` | 3hrs 5mins
  `<ExtentUnit>15</ExtentUnit>` | Time in HHHMM
  `</Extent>` |

  using Short tags, time in minutes |
  --- | ---
  `<extent>` |
  `<b218>09</b218>` |
  `<b219>185</b219>` | 185 mins
  `<b220>05</b220>` | Time in mins
  `</extent>` |

##### P.11.5 Illustrated yes/no

An ONIX code indicating whether a book or other textual (usually printed) product has illustrations. The more informative free text field <IllustrationsNote> and/or the <AncillaryContent> composite are strongly preferred. This element has been added specifically to cater for a situation where a sender of product information maintains only a yes/no flag, and it should not otherwise be used. Optional and non-repeating.

  Fixed length, two digits
  List 152
  Illustrated
  x422
  0…1
  `<Illustrated>01</Illustrated>` (No)

##### P.11.6 Number of illustrations

The total number of illustrations in a book or other printed product. The more informative free text field <IllustrationsNote> and/or the <AncillaryContent> composite are strongly preferred, but where a sender of product information maintains only a simple numeric field, the <NumberOfIllustrations> element may be used. Optional and non-repeating.

  Positive integer or zero, suggested maximum length 6 digits
  NumberOfIllustrations
  b125
  0…1
  `<NumberOfIllustrations>64</NumberOfIllustrations>`

##### P.11.7 Illustrations and other contents note

For books or other text media only, this data element carries text stating the number and type of illustrations. The text may also include other content items, eg maps, bibliography, tables, index etc. Optional, and repeatable if parallel notes are provided in multiple languages. The language attribute is optional for a single instance of <IllustrationsNote>, but must be included in each instance if <IllustrationsNote> is repeated.

  Variable length text, suggested maximum length 200 characters. XHTML is enabled in this element – see Using XHTML, HTML, XML or JSON with ONIX text fields
  IllustrationsNote
  b062
  0…n
  language, textformat
  `<b062>500 illustrations, 210 in full color</b062>`

##### Ancillary content composite

A group of data elements which together specify the number of illustrations or other content items of a stated type which the product carries. Use of the <AncillaryContent> composite is optional, but is repeatable if necessary to specify different types of content items.

  AncillaryContent
  ancillarycontent
  0…n

##### P.11.8 Illustration or other content type code

An ONIX code which identifies the type of illustration or other content to which an occurrence of the composite refers. Mandatory in each occurrence of the <AncillaryContent> composite, and non-repeating.

  Fixed length, two digits
  List 25
  AncillaryContentType
  x423
  1
  `<x423>09</x423>` (Illustrations, unspecified)

##### P.11.9 Illustration or other content type description

Text describing the type of illustration or other content to which an occurrence of the composite refers, when a code is insufficient. Optional, and repeatable if parallel descriptive text is provided in multiple languages. Required when <AncillaryContentType> carries the value 00. The language attribute is optional for a single instance of <AncillaryContentDescription>, but must be included in each instance if <AncillaryContentDescription> is repeated.

  Variable length text, suggested maximum length 100 characters. XHTML is enabled in this element – see Using XHTML, HTML, XML, JSON within ONIX text fields
  AncillaryContentDescription
  x424
  0…n
  language, textformat
  `<x424 language="eng">Full color stickers</x424>`

##### P.11.10 Number of illustrations or other content items

The number of illustrations or other content items of the type specified in <AncillaryContentType>. Optional and non-repeating.

  Positive integer or zero, suggested maximum length 6 digits
  Number
  b257
  0…1
  `<Number>12</Number>`

##### End of Ancillary content composite

  insert (plate section) with 51 color plates, plus index
  using Reference names |
  --- | ---
  `<AncillaryContent>` |
  `<AncillaryContentType>24</AncillaryContentType>` |
  `<Number>51</Number>` |
  `</AncillaryContent>` |
  `<AncillaryContent>` |
  `<AncillaryContentType>25</AncillaryContentType>` |
  `</AncillaryContent>` |

  using Short tags |
  --- | ---
  `<ancillarycontent>` |
  `<x423>24</x423>` | Color plates
  `<b257>51</b257>` |
  `</ancillarycontent>` |
  `<ancillarycontent>` |
  `<x423>25</x423>` | Index
  `</ancillarycontent>` |

#### P.12 Subject

Group P.12 has been simplified in ONIX 3.0 and 3.1 so that all subject codes and/or headings are sent using a single <Subject> composite, with a new <MainSubject/> flag to indicate what the sender regards as the main subject of the product.

While the XML Schema will allow an ONIX record to be sent without subject elements, it is expected that all ONIX descriptions should carry at least a main subject. US users are reminded that most US retailers and wholesalers require a BISAC subject category; in many other countries, a Thema subject category is preferred, and for UK users in particular a Thema subject category is mandatory in order to meet BIC Basic standards.

##### Subject composite

An optional group of data elements which together specify a subject classification, category or subject heading. Repeatable, both to express multiple subject categories or headings in a scheme, and to specify subjects using multiple schemes.

  Subject
  subject
  0…n

##### P.12.1 Main subject flag

An empty element that identifies an instance of the <Subject> composite as representing the primary or main subject category for the product. The main category may be expressed in more than one subject scheme, ie there may be two or more instances of the <Subject> composite, using different schemes, each carrying the <MainSubject/> flag, so long as there is only one main category per scheme (ie per value of <SubjectSchemeIdentifier>). Optional, though for some subject schemes (eg Thema), <MainSubject/> can be vital in order to prevent potential misinterpretation of a group of subject codes, and for other schemes which by their nature only allow one code (eg Dewey), <MainSubject> is not relevant. Non-repeating in each occurrence of the <Subject> composite.

  XML empty element
  MainSubject/
  x425/
  0…1
  `<MainSubject/>`

##### P.12.2 Subject scheme identifier

An ONIX code which identifies the category or subject heading scheme which is used in an occurrence of the <Subject> composite. Mandatory in each occurrence of the composite, and non-repeating.

For category schemes that use code values, use the associated <SubjectCode> element to carry the value (if so required, the <SubjectHeadingText> element can be used simultaneously to carry the text equivalent of the code). For schemes that use text headings, use the <SubjectHeadingText> element to carry the text of the category heading.

  Fixed length, two alphanumeric characters
  List 27
  SubjectSchemeIdentifier
  b067
  1
  `<b067>03</b067>` (US Library of Congress classification)

##### P.12.3 Proprietary subject scheme name

A name identifying a proprietary subject scheme (ie a scheme which is not a standard and for which there is no individual identifier code) when <SubjectSchemeIdentifier> is coded ‘24’. Optional and non-repeating.

  Variable length text, suggested maximum length 100 characters
  SubjectSchemeName
  b171
  0…1
  language
  `<b121>RetailCo ShelfScheme</b121>`

##### P.12.4 Subject scheme version number

A number which identifies a version or edition of the subject scheme specified in the associated <SubjectSchemeIdentifier> element. Optional and non-repeating.

  Variable length alphanumeric, suggested maximum length 10 characters for consistency with other version number elements
  SubjectSchemeVersion
  b068
  0…1
  `<SubjectSchemeVersion>2.1</SubjectSchemeVersion>`

##### P.12.5 Subject code

A single subject class or category code from the scheme specified in the <SubjectSchemeIdentifier> element. Either <SubjectCode> or <SubjectHeadingText> or both must be present in each occurrence of the <Subject> composite. Non-repeating.

  Variable length alphanumeric, suggested maximum length 20 characters
  The scheme specified in the associated <SubjectSchemeIdentifier> element
  SubjectCode
  b069
  0…1
  `<SubjectCode>623.95</SubjectCode>`

##### P.12.6 Subject heading text

The text of a subject heading taken from the scheme specified in the <SubjectSchemeIdentifier> element, or of free language keywords if the scheme is specified as ‘keywords’; or the text equivalent to the <SubjectCode> value, if both code and text are sent. Either <SubjectCode> or <SubjectHeadingText> or both must be present in each occurrence of the <Subject> composite.

Optional, and repeatable if the heading text is sent in multiple languages. The language attribute is optional for a single instance of <SubjectHeadingText>, but must be included in each instance if <SubjectHeadingText> is repeated.

  Variable length text, suggested maximum length 500 characters
  SubjectHeadingText
  b070
  0…n
  language
  `<b070>Labor and industrial relations</b070>`

##### End of Subject composite

  delivering both BISAC and Thema subject codes plus keywords
  using Reference names |
  --- | ---
  `<Subject>` |
  `<MainSubject/>` |
  `<SubjectSchemeIdentifier>10</SubjectSchemeIdentifier>` |
  `<SubjectSchemeVersion>2016</SubjectSchemeVersion>` |
  `<SubjectCode>GAR006000</SubjectCode>` |
  `</Subject>` |
  `<Subject>` |
  `<SubjectSchemeIdentifier>10</SubjectSchemeIdentifier>` |
  `<SubjectSchemeVersion>2016</SubjectSchemeVersion>` |
  `<SubjectCode>GAR028000</SubjectCode>` |
  `</Subject>` |
  `<Subject>` |
  `<MainSubject/>` |
  `<SubjectSchemeIdentifier>93</SubjectSchemeIdentifier>` |
  `<SubjectSchemeVersion>1.2</SubjectSchemeVersion>` |
  `<SubjectCode>WMD</SubjectCode>` |
  `</Subject>` |
  `<Subject>` |
  `<SubjectSchemeIdentifier>20</SubjectSchemeIdentifier>` |
  `<SubjectHeadingText>garden design; urban; patio; container gardening</SubjectHeadingText>` |
  `</Subject>` |

  using Short tags |
  --- | ---
  `<subject>` |
  `<x425/>` | Main subject code
  `<b067>10</b067>` | BISAC scheme
  `<b068>2016</b068>` | 2016 version
  `<b069>GAR006000</b069>` |
  `</subject>` |
  `<subject>` |
  `<b067>10</b067>` | BISAC
  `<b068>2016</b068>` |
  `<b069>GAR028000</b069>` | secondary code
  `</subject>` |
  `<subject>` |
  `<x425/>` | Main subject code
  `<b067>93</b067>` | Thema scheme
  `<b068>1.2</b068>` | Version 1.2
  `<b069>WMD</b069>` |
  `</subject>` |
  `<subject>` |
  `<b067>20</b067>` | Keywords
  `<b070>garden design; urban; patio; container gardening</b070>` |
  `</subject>` |

##### Name as subject composite

An optional group of data elements which together represent the name of a person or organization – real or fictional – that is part of the subject of a product. Repeatable in order to name multiple persons or organizations.

Each instance of the composite must contain either:

- one or more of the forms of representation of a person name, with or without an occurrence of the <NameIdentifier> composite; or
- one or more of the forms of representation of a corporate name, with or without an occurrence of the <NameIdentifier> composite; or
- an occurrence of the <NameIdentifier> composite without any accompanying name element(s).

The name of a person (not of a corporation) may optionally be followed by details of that person’s professional affiliation.

  NameAsSubject
  nameassubject
  0…n

##### P.12.7 to P.12.22: elements in the Name as subject composite

Elements P.12.7 to P.12.22 in the <NameAsSubject> composite are identical to P.7.5 to P.7.20 as specified in Group P.7.

##### Alternative name composite

A repeatable group of data elements which together represent an alternative name of a person or organization that is part of the subject of a product, and specify its type. The <AlternativeName> composite is optional.

  AlternativeName
  alternativename
  0…n

##### P.12.23 to P.12.38: elements in the Alternative name composite

Elements P.12.23 to P.12.38 in the <AlternativeName> composite are identical to P.7.21 to P.7.36 as specified in Group P.7.

##### End of Alternative name composite

##### Subject date composite

A group of data elements which together specify a date associated with the person or organization identified in an occurrence of the <NameAsSubject> composite, eg birth or death. Optional, and repeatable to provide multiple dates with their various roles.

  SubjectDate
  subjectdate
  0…n

##### P.12.39 Subject date role code

An ONIX code indicating the significance of the date in relation to the subject name. Mandatory in each occurrence of the <SubjectDate> composite, and non-repeating.

  Fixed length, two digits
  List 177
  SubjectDateRole
  x534
  1
  `<x534>50</x534>` (Date of birth)

##### P.12.41 Date

The date specified in the <SubjectDateRole> field. Mandatory in each occurrence of the <SubjectDate> composite, and non-repeating. <Date> may carry a dateformat attribute: if the attribute is missing, then the default format is YYYYMMDD.

  As specified by the value in the dateformat attribute, or the default YYYYMMDD
  Date
  b306
  1
  dateformat
  `<b306 dateformat="05">1381</b306>`

##### End of Subject date composite

##### Professional affiliation composite

An optional group of data elements which together identify a subject’s professional position and/or affiliation, repeatable to allow multiple positions and affiliations to be specified.

  ProfessionalAffiliation
  professionalaffiliation
  0…n

##### P.12.42 to P.12.43: elements in the Professional affiliation composite

Elements P.12.42 and P.12.43 in the <ProfessionalAffiliation> composite are identical to P.7.40 and P.7.41 as specified in Group P.7.

##### End of Professional affiliation composite

##### End of Name as subject composite

  using Reference names |
  --- | ---
  `<NameAsSubject>` |
  `<NameType>00</NameType>` |
  `<NameIdentifier>` |
  `<NameIDType>16</NameIDType>` |
  `<IDValue>000000010935660X</IDValue>` |
  `</NameIdentifier>` |
  `<PersonNameInverted>Thesiger, Wilfred</PersonNameInverted>` |
  `</NameAsSubject>` |

  using Short tags |
  --- | ---
  `<nameassubject>` |
  `<x414>00</x414>` | Type unspecified
  `<nameidentifier>` |
  `<x415>16</x415>` | ISNI
  `<b244>000000010935660X</b244>` |
  `</nameidentifier>` |
  `<b037>Thesiger, Wilfred</b037>` |
  `</nameassubject>` |

#### P.13 Audience

Data element Group P.13 covers a range of methods of indicating the intended audience for a product. None is defined as mandatory in the XML Schema.

##### Audience composite

An optional group of data elements which together describe an audience to which the product is directed. Repeatable, both to specify multiple distinct audiences, and to express audiences using multiple schemes.

  Audience
  audience
  0…n

##### P.13.1a Main audience flag

An empty element that identifies an instance of the <Audience> composite as representing the primary or main audience for the product. The main audience may be expressed in more than one audience scheme, ie there may be two or more instances of the <Audience> composite, using different schemes, each carrying the <MainAudience/> flag, so long as there is only one main audience per scheme (ie per value of <AudienceCodeType>). Optional and non-repeating in each occurrence of the <Audience> composite.

  XML empty element
  MainAudience/
  x583/
  0…1
  `<x583/>`

##### P.13.2 Audience code type

An ONIX code which identifies the scheme from which the code in <AudienceCodeValue> is taken. Mandatory in each occurrence of the <Audience> composite, and non-repeating.

  Fixed length, two digits
  List 29
  AudienceCodeType
  b204
  1
  `<AudienceCodeType>02</AudienceCodeType>` (Proprietary)

##### P.13.3 Audience code type name

A name which identifies a proprietary audience scheme when the code in <AudienceCodeType> indicates a proprietary scheme, eg a vendor’s own coding scheme. Optional and non-repeating.

  Variable length text, suggested maximum length 50 characters
  AudienceCodeTypeName
  b205
  0…1
  language
  `<b205>Fortnightly Books target selector</b205>`

##### P.13.4 Audience code value

A code value taken from the scheme specified in <AudienceCodeType>. Either <AudienceCodeValue> or <AudienceHeadingText> or both must be present in each occurrence of the <Audience> composite. Non-repeating.

  Determined by the scheme specified in <AudienceCodeType>
  AudienceCodeValue
  b206
  0…1
  `<AudienceCodeValue>06</AudienceCodeValue>` (Professional and scholarly)

##### P.13.4a Audience heading text

The text of an audience heading taken from the scheme specified in the <AudienceCodeType> element; or the text equivalent to the <AudienceCodeValue> if both code and text are sent. Either <AudienceCodeValue> or <AudienceHeadingText> or both must be present in each occurrence of the <Audience> composite.

Optional, and repeatable if the text is sent in multiple languages. The language attribute is optional for a single instance of <AudienceHeadingText>, but must be included in each instance if <AudienceHeadingText> is repeated.

  Variable length text, suggested maximum length 500 characters
  AudienceHeadingText
  x578
  0…n
  language
  `<x578 language="eng">Priority Parents</x578>`

##### End of Audience composite

  using Reference names |
  --- | ---
  `<Audience>` |
  `<MainAudience/>` |
  `<AudienceCodeType>01</AudienceCodeType>` |
  `<AudienceCodeValue>03</AudienceCodeValue>` |
  `</Audience>` |
  `<Audience>` |
  `<AudienceCodeType>01</AudienceCodeType>` |
  `<AudienceCodeValue>01</AudienceCodeValue>` |
  `</Audience>` |
  `<Complexity>` |
  `<ComplexitySchemeIdentifier>06</ComplexitySchemeIdentifier>` |
  `<ComplexityCode>HL720L</ComplexityCode>` |
  `</Complexity>` |

  using Short tags |
  --- | ---
  `<audience>` |
  `<x583/>` | Main audience
  `<b204>01</b204>` | ONIX audience code
  `<b206>03</b206>` | Teenage
  `</audience>` |
  `<audience>` | Secondary audience
  `<b204>01</b204>` |
  `<b206>01</b206>` | General / adult
  `</audience>` |
  `<complexity>` |
  `<b077>06</b077>` | Lexile measure
  `<b078>HL720L</b078>` |
  `</complexity>` |

##### Audience range composite

An optional group of data elements which together describe an audience or readership range for which a product is intended. The composite can carry a single value from, to, or exact, or a pair of values with an explicit from and to. Repeatable to specify the audience range with different qualifiers.

  AudienceRange
  audiencerange
  0…n

##### P.13.5 Audience range qualifier

An ONIX code specifying the attribute (interest age, school grade etc) which is measured by the value in the <AudienceRangeValue> element. Mandatory in each occurrence of the <AudienceRange> composite, and non-repeating.

  Fixed length, two digits
  List 30
  AudienceRangeQualifier
  b074
  1
  `<b074>11</b074>` (US school grade)

##### P.13.6 Audience range precision (1)

An ONIX code specifying the ‘precision’ of the value in the <AudienceRangeValue> element which follows (from, to, exact). Mandatory in each occurrence of the <AudienceRange> composite, and non-repeating.

  Fixed length, two digits
  List 31
  AudienceRangePrecision
  b075
  1
  `<b075>03</b075>` (From)

##### P.13.7 Audience range value (1)

A value indicating an exact position within a range, or the upper or lower end of a range.

  Variable length string, suggested maximum 10 characters, according to the scheme specified in <AudienceRangeQualifier>. (This element was originally defined as a variable-length integer, but its definition was extended in ONIX 2.1 to enable non-numeric values to be carried. For values that BISAC has defined for US school grades and pre-school levels, see List 77)
  AudienceRangeValue
  b076
  1
  `<AudienceRangeValue>10</AudienceRangeValue>`

##### P.13.8 Audience range precision (2)

An ONIX code specifying the ‘precision’ of the value in <AudienceRangeValue> element which follows. Optional and non-repeating. This second occurrence of the two elements <AudienceRangePrecision> and <AudienceRangeValue> is required only when a ‘from … to …’ range is specified.

  Fixed length, two digits
  List 31 The only value which is valid in this element is 04 (‘To’)
  AudienceRangePrecision
  b075
  0…1
  `<AudienceRangePrecision>04</AudienceRangePrecision>` (To)

##### P.13.9 Audience range value (2)

A value indicating the upper end of a range.

  Variable length string, suggested maximum 10 characters, according to the scheme specified in <AudienceRangeQualifier>. (This element was originally defined as a variable-length integer, but its definition was extended in ONIX 2.1 to enable non-numeric values to be carried. For values that BISAC has defined for US school grades and pre-school levels, see List 77)
  AudienceRangeValue
  b076
  0…1
  `<AudienceRangeValue>11</AudienceRangeValue>`

##### End of Audience range composite

  up to US school grade 4
  using Reference names |
  --- | ---
  `<AudienceRange>` |
  `<AudienceRangeQualifier>11</AudienceRangeQualifier>` |
  `<AudienceRangePrecision>04</AudienceRangePrecision>` |
  `<AudienceRangeValue>4</AudienceRangeValue>` |
  `</AudienceRange>` |

  using Short tags |
  --- | ---
  `<audiencerange>` |
  `<b074>11</b074>` | US school grade
  `<b075>04</b075>` | Up to
  `<b076>4</b076>` | Grade 4
  `</audiencerange>` |

  from US school grade 9 up to grade 12
  using Reference names |
  --- | ---
  `<AudienceRange>` |
  `<AudienceRangeQualifier>11</AudienceRangeQualifier>` |
  `<AudienceRangePrecision>03</AudienceRangePrecision>` |
  `<AudienceRangeValue>9</AudienceRangeValue>` |
  `<AudienceRangePrecision>04</AudienceRangePrecision>` |
  `<AudienceRangeValue>12</AudienceRangeValue>` |
  `</AudienceRange>` |

  using Short tags |
  --- | ---
  `<audiencerange>` |
  `<b074>11</b074>` | US school grade
  `<b075>03</b075>` | From
  `<b076>9</b076>` | Grade 9
  `<b075>04</b075>` | Up to
  `<b076>12</b076>` | Grade 12
  `</audiencerange>` |

##### P.13.10 Audience description

Free text describing the audience for which a product is intended. Optional, and repeatable if parallel descriptive text is provided in multiple languages. The language attribute is optional for a single instance of <AudienceDescription>, but must be included in each instance if <AudienceDescription> is repeated.

  Variable length text, suggested maximum length 500 characters. XHTML is enabled in this element – see Using XHTML, HTML, XML, JSON within ONIX text fields
  AudienceDescription
  b207
  0…n
  language, textformat

##### Complexity composite

An optional group of data elements which together describe the level of complexity of a text. Repeatable to specify the complexity using different schemes.

  Complexity
  complexity
  0…n

##### P.13.11 Complexity scheme identifier

An ONIX code specifying the scheme from which the value in <ComplexityCode> is taken. Mandatory in each occurrence of the <Complexity> composite, and non-repeating.

  Fixed length, two digits
  List 32
  ComplexitySchemeIdentifier
  b077
  1
  `<b077>06</b077>` (Lexile measure)

##### P.13.12 Complexity code

A code specifying the level of complexity of a text. Mandatory in each occurrence of the <Complexity> composite, and non-repeating.

  Variable length alphanumeric, suggested maximum length 20 characters, according to the code type specified in the <ComplexitySchemeIdentifier> element
  ComplexityCode
  b078
  1
  `<ComplexityCode>880L</ComplexityCode>`

##### End of Complexity composite

#### End of Descriptive detail composite

### Block 2: Marketing collateral detail

#### Collateral detail composite

The collateral detail block covers data Groups P.14 to P.17, all of which are primarily concerned with information and/or resources which in one way or another support the marketing of the product. The block as a whole is non-repeating.

The block is not mandatory within the <Product> record, nor are any of the individual sections mandatory within an occurrence of the block. However, in most circumstances, the block should contain at least one instance of <TextContent>, <CitedContent>, <SupportingResource> or <Prize>. It may be empty only within a partial or ‘block update’ (Notification or update type 04, see P.1.2), when the intention is to remove all previously-supplied collateral material.

  CollateralDetail
  collateraldetail
  0…1

#### P.14 Descriptions and other supporting text

For ONIX 3.0 and 3.1, Group P.14 partly replaces the <OtherText> composite in Release 2.1. It is different, however, in that the new <TextContent> composite is strictly for supporting text that is carried in the ONIX record. Text that is cited from a third-party source is now covered in Group P.15. Text that is offered for online access or download by the publisher or other sender of an ONIX record is covered in Group P.16.

##### Supporting text content composite

An optional group of data elements which together carry a supporting text related to the product, repeatable in order to deliver multiple texts (often of different types, though for some text types there many be multiple instances of that type).

  TextContent
  textcontent
  0…n

##### P.14.1 Supporting text sequence number

A number which specifies a single overall sequence of supporting texts. Optional and non-repeating. It is strongly recommended that if any occurrence of the <TextContent> composite of a specific <TextType> carries a <SequenceNumber>, then all of that type should carry a <SequenceNumber> – though there is no requirement to number supporting texts where there is a single instance of that type.

  Positive integer, 1, 2, 3 etc, suggested maximum length 3 digits
  SequenceNumber
  b034
  0…1
  `<b034>3</b034>`

##### P.14.1a Text type code

An ONIX code which identifies the type of text which is sent in the <Text> element. Mandatory in each occurrence of the <TextContent> composite, and non-repeating.

  Fixed length, two digits
  List 153
  TextType
  x426
  1
  `<TextType>04</TextType>` (Table of contents)

##### P.14.2 Text audience

An ONIX code which identifies the audience for which the text in the <Text> element is intended. Mandatory in each occurrence of the <TextContent> composite, and repeatable.

  Fixed length, two digits
  List 154
  ContentAudience
  x427
  1…n
  `<x427>03</x427>` (End customers)

##### Territory composite

A group of data elements which together define a territory for which the text in the <Text> element is specifically intended. Optional in each occurrence of the <TextContent> composite, and non-repeating. If omitted, the text is intended for use wherever the product may be sold (see Territorial sales rights in Group P.21). If included, the text should be used by recipients in the specified territory only, and in preference to any text that lacks a specified territory.

For valid combinations of <CountriesIncluded>, <RegionsIncluded> etc within <Territory>, see the notes describing the use of <Territory> within Group P.21.

Care should be taken to avoid ambiguities (for example two different ‘short descriptions’ – without language attributes or with the same language attribute – marked for use in the same country or region), and to ensure that appropriate descriptions and supporting text are supplied for all countries and regions where the product may be sold. The simplest way to accomplish the latter is to ensure at least one version of the text does not have a territory specified. Where multiple texts of the same type are provided, those without specific <Territory> composites are intended for use only where no appropriate targeted text is present.

  Territory
  territory
  0…1

##### P.14.2a Countries included

One or more ONIX codes identifying countries included in the territory. Successive codes must be separated by spaces. Optional and non-repeating, but either <CountriesIncluded> or <RegionsIncluded> is mandatory in each occurrence of the <Territory> composite.

  One or more fixed-length codes based on ISO 3166-1, each consisting of two upper case letters, and with successive codes being separated by spaces. Suggested maximum length 750 characters. Note that ISO 3166-1 specifies that country codes shall be sent as upper case only
  List 91
  CountriesIncluded
  x449
  0…1
  `<CountriesIncluded>US CA</CountriesIncluded>` (USA and Canada)

##### P.14.2b Regions included

One or more ONIX codes identifying regions included in the territory. A region is an area which is not a country, but which is precisely defined in geographical terms, eg the World, Northern Ireland, Australian Capital Territory. Successive codes must be separated by spaces. Optional and non-repeating, but either <CountriesIncluded> or <RegionsIncluded> is mandatory in each occurrence of the <Territory> composite.

Note that if used, the ‘WORLD’ region code cannot be combined with other region codes.

  One or more variable-length codes, each consisting of upper case letters, with or without a hyphen and further upper case letters or digits, and with successive codes being separated by spaces. Suggested maximum length 750 characters
  List 49 Where possible and appropriate, country subdivision codes are derived from the UN LOCODE scheme based on ISO 3166-2
  RegionsIncluded
  x450
  0…1
  `<x450>GB-SCT GB-NIR GB-WLS</x450>` (Includes Scotland, Northern Ireland, Wales)

##### P.14.2c Countries excluded

One or more ONIX codes identifying countries excluded from the territory. Successive codes must be separated by spaces. Optional and non-repeating, and can only occur if the <RegionsIncluded> element is also present and includes a supra-national region code (such as ‘WORLD’).

  One or more fixed-length codes based on ISO 3166-1, each consisting of two upper case letters, and with successive codes being separated by spaces. Suggested maximum length 750 characters. Note that ISO 3166-1 specifies that country codes shall be sent as upper case only
  List 91
  CountriesExcluded
  x451
  0…1
  `<CountriesExcluded>US CA</CountriesExcluded>` (Excludes USA and Canada)

##### P.14.2d Regions excluded

One or more ONIX codes identifying regions excluded from the territory. Successive codes must be separated by spaces. Optional and non-repeating, and can only occur if the <CountriesIncluded> element is also present (and specifies countries of which the excluded regions are a part), or if <RegionsIncluded> is present and includes a supra-national region code (such as ‘WORLD’).

  One or more variable-length codes, each consisting of upper case letters, with or without a hyphen and further upper case letters or digits, and with successive codes being separated by spaces. Suggested maximum length 750 characters
  List 49 Where possible and appropriate, country subdivision codes are derived from the UN LOCODE scheme based on ISO 3166-2
  RegionsExcluded
  x452
  0…1
  `<x452>CA-QC</x452>` (Excludes Quebec)

##### End of Territory composite

##### P.14.3 Supporting text

The text specified in the <TextType> element. Mandatory in each occurrence of the <TextContent> composite, and repeatable when essentially identical text is supplied in multiple languages. The language attribute is optional for a single instance of <Text>, but must be included in each instance if <Text> is repeated.

  Variable length text. XHTML is enabled in this element – see Using XHTML, HTML, XML, JSON within ONIX text fields. Note that certain Text types impose a strict limit on the number of characters, and such limits do not count the characters of any (X)HTML markup
  Text
  d104
  1…n
  language, textformat
  `<Text textformat="05"><ul><li>Introduction: aesthetics and modernity; aesthetics and post-modernity</li><li>Part 1: Modern philosophy and the emergence of aesthetic theory – Kant: self-consciousness, knowledge and freedom; the unity of the subject; the unification of nature; the purpose of beauty; the limits of beauty</li><li>Part 2: German idealism and early German Romanticism: the ‘new mythology’; the romantic ‘new mythology’</li><li>Part 3: Reflections on the subject – Fichte, Holderlin and Novalis</li><li>Part 4: Schelling – art as the ‘organ of philosophy’: the development of consciousness; the structure of the ‘system of transcendental idealism’; the aesthetic absolute; mythology, art and language; mythology, language and being</li><li>Part 5…</li></ul></Text>` (Table of contents supplied as a list, with XHTML markup)

  `<d104 language="eng">‘The Name of the Rose’ is the author’s first novel. It is a historical murder mystery set in an Italian monastery in the year 1327, and at the same time, it’s an intellectual puzzle weaving semiotics, biblical analysis, medieval studies and literary theory into gripping fiction.</d104>`
  `<d104 language="ita">“Il nome della rosa” è il primo romanzo dell’autore. Si tratta di un misterioso omicidio storico ambientato in un monastero italiano nel corso dell’anno 1327, e allo stesso tempo, è un mistero intellettuale che unisce semiotica, analisi biblici, studi medievali e teoria letteraria nella narrativa avvincente.</d104>` (Parallel short description text provided in two languages)

##### Review rating composite

An optional group of data elements which together specify a ‘star rating’ awarded as part of a review of the publication, used when <TextType> indicates the text is a review. Not repeatable.

  ReviewRating
  reviewrating
  0…1

##### P.14.3a Review rating

The ‘star rating’ awarded as part of a review of the publication. Mandatory within an occurrence of the <ReviewRating> composite, and non-repeating.

  Positive real number, with explicit decimal point when required, or zero, as appropriate for the limit specified in <RatingLimit>. Suggested maximum length 7 characters
  Rating
  x525
  1
  `<Rating>4.5</Rating>` (4.5 out of 5 stars)

##### P.14.3b Review rating limit

The maximum possible rating that may be awarded as part of a review of the publication. Optional, but where used, it must be greater than or equal to the specified <Rating>.

  Positive integer number, suggested maximum length 4 digits
  RatingLimit
  x526
  0…1
  `<RatingLimit>5</RatingLimit>` (4.5 out of 5 stars)

##### P.14.3c Review rating units

The ‘units’ used by a rating, eg stars, tomatoes etc. Optional, and repeatable to provide the units in multiple languages. The language attribute is optional for a single instance of <RatingUnits>, but must be included in each instance if <RatingUnits> is repeated.

  Variable length text, suggested maximum length 50 characters
  RatingUnits
  x527
  0…n
  language
  `<RatingUnits>stars</RatingUnits>` (4.5 out of 5 stars)

##### End of Review rating composite

##### P.14.4 Author of text

The name of an author of text sent in the <Text> element, eg if it is a review or promotional quote. Optional, and repeatable if the text is jointly authored.

  Variable length text, suggested maximum length 300 characters
  TextAuthor
  d107
  0…n
  language
  `<d107>Martin Amis</d107>`

##### P.14.5 Corporate source of text

The name of a company or corporate body responsible for the text sent in the <Text> element. Optional and non-repeating.

  Variable length text, suggested maximum length 200 characters
  TextSourceCorporate
  b374
  0…1
  language
  `<TextSourceCorporate>Random House Group</TextSourceCorporate>`

##### P.14.5a Text source description

Brief text describing or providing context for the text author or corporate source, at the publisher’s discretion, and intended to be used in addition to <TextAuthor> or <TextSourceCorporate>. Optional, and repeatable to provide parallel descriptions in multiple languages. The language attribute is optional for a single instance of <TextSourceDescription>, but must be included in each instance if <TextSourceDescription> is repeated. The description may be used with either a person or corporate name, to draw attention to any aspect of the text source’s background which provides context for the text in <Text>.

  Variable length text, suggested maximum length 200 characters. XHTML is enabled in this element – see Using XHTML, HTML, XML, JSON within ONIX text fields
  TextSourceDescription
  x557
  0…n
  language, textformat
  `<TextSourceDescription textformat="05">Literary editor of <cite>The Spectator</cite></TextSourceDescription>`

##### P.14.6 Source title

The title of a publication from which the text sent in the <Text> element was taken, eg if it is a review quote. Optional, and repeatable to provide the title in multiple languages. The language attribute is optional for a single instance of <SourceTitle>, but must be included in each instance if <SourceTitle> is repeated.

  Variable length text, suggested maximum length 300 characters
  SourceTitle
  x428
  0…n
  language
  `<x428>New York Times</x428>`

##### P.14.6a Text source link

A URL which provides a link to a full text accessible in digital form, from which the supporting text in <Text> is an extract. Use, for example, to link to an original review. Optional, and repeatable if the resource can be linked in more than one way, eg by URL or DOI, or where a linked full text is available in multiple parallel languages. Where multiple languages are used, all repeats must carry the language attribute.

  Uniform Resource Locator, expressed in full URI syntax in accordance with W3C standards, suggested maximum length 300 characters. Note that non-ASCII characters, spaces and a handful of other special characters should be ‘URL-encoded’. Any ampersand used to separate parameters in the URL must be expressed as &amp;
  TextSourceLink
  x581
  0…n
  language
  `<x581>https://www.nytimes.com/archives/2012-08-04/Berni%e8res.htm</x581>` (note URL-encoding of è)

##### Usage constraint composite (supporting text)

An optional group of data elements which together describe a usage constraint on the supporting text sent in <Text> (or the absence of such a constraint). Repeatable in order to describe multiple constraints on usage.

  EpubUsageConstraint
  epubusageconstraint
  0…n

##### P.14.6b to P.14.6e: elements in the EpubUsageConstraint composite

Elements P.14.6b to P.14.6e in the <EpubUsageConstraint> composite are identical to P.3.17 to P.3.20 in Group P.3.

##### End of Usage constraint composite

##### Digital license composite (supporting text)

An optional composite carrying the name or title of the license governing use of the supporting text sent in <Text>, a link to the license terms in eye-readable or machine-readable form, and optional dates when the license is valid. Repeatable in order to specify multiple licenses with differing periods of validity.

Note that in the case of multiple Digital license composites, any Usage constraints (above) apply to the current license.

  EpubLicense
  epublicense
  0…n

##### P.14.6f to P.14.6k: elements in the EpubLicense composite

Elements P.14.6f to P.14.6k in the <EpubLicence> composite are identical to P.3.20a to P.3.20f in Group P.3.

##### End of Digital license composite

##### Content date composite

An optional group of data elements which together specify a date associated with the text carried in an occurrence of the <TextContent> composite, eg date when quoted text was published. Repeatable to specify different dates with their various roles.

  ContentDate
  contentdate
  0…n

##### P.14.7 Content date role code

An ONIX code indicating the significance of the date in relation to the text content. Mandatory in each occurrence of the <ContentDate> composite, and non-repeating.

  Fixed length, two digits
  List 155
  ContentDateRole
  x429
  1
  `<ContentDateRole>01</ContentDateRole>` (Publication date)

##### P.14.9 Date

The date specified in the <ContentDateRole> field. Mandatory in each occurrence of the <ContentDate> composite, and non-repeating. <Date> may carry a dateformat attribute: if the attribute is missing, then the default format is YYYYMMDD.

  As specified by the value in the dateformat attribute, or the default YYYYMMDD
  Date
  b306
  1
  dateformat
  `<b306 dateformat="00">20010106</b306>`

##### End of Content date composite

##### End of Text content composite

#### P.15 Cited content

Group P.15 describes cited material, with links to digital sources and/or references to conventional printed sources. In ONIX 3.0 and later, cited content means content owned and/or published by a third party which is relevant to a product. The key distinction between supporting resources (P.16) and cited content is that a supporting resource comes with a clear invitation to the receiver to use it (subject to any specified limitations), while cited content is the intellectual property of a third party, subject to that party’s copyright or other rights, and can only be referenced.

##### Cited content composite

An optional group of data elements which together describe a piece of cited content. The composite is repeatable to describe and link to multiple items of cited material.

  CitedContent
  citedcontent
  0…n

##### P.15.1 Cited content sequence number

A number which specifies a single overall sequence of cited content. Optional and non-repeating. It is strongly recommended that if any occurrence of the <CitedContent> composite of a specific <CitedContentType> carries a <SequenceNumber>, then all of that type should carry a <SequenceNumber> – though there is no requirement to number cited content where there is a single instance of that type.

  Positive integer, 1, 2, 3 etc, suggested maximum length 3 digits
  SequenceNumber
  b034
  0…1
  `<b034>3</b034>`

##### P.15.1a Cited content type code

An ONIX code indicating the type of content which is being cited. Mandatory in each occurrence of the <CitedContent> composite, and non-repeating.

  Fixed length, two digits
  List 156
  CitedContentType
  x430
  1
  `<CitedContentType>01</CitedContentType>` (Full text of review)

##### P.15.2 Target audience

An ONIX code which identifies the audience for which a piece of cited content is intended. Optional and repeatable.

  Fixed length, two digits
  List 154
  ContentAudience
  x427
  0…n
  `<x427>04</x427>` (Librarians)

##### Territory composite

A group of data elements which together define a territory for which the cited content is specifically intended. Optional in each occurrence of the <CitedContent> composite, and non-repeating. If omitted, the content is intended to be cited (linked to) wherever the product may be sold (see Territorial sales rights in Group P.21). If included, the content should be cited by recipients in the specified territory only, and in preference to any cited content that lacks a specified territory.

For valid combinations of <CountriesIncluded>, <RegionsIncluded> etc within <Territory>, see the notes describing the use of <Territory> within Group P.21.

Care should be taken to avoid ambiguities (for example two different citations of the same type marked for use in the same country or region), and to ensure that appropriate citations are supplied for all countries and regions where the product may be sold. The simplest way to accomplish the latter is to ensure at least one version of the citation does not have a territory specified. Where multiple citations of the same type are provided, those without specific <Territory> composites are intended for use only where no appropriate targeted citation is present.

  Territory
  territory
  0…1

##### P.15.2a to P.15.2d: elements in the Territory composite

Elements P.15.2a to P.15.2d in the <Territory> composite are identical to P.14.2a to P.14.2d as specified in Group P.14.

##### End of Territory composite

##### P.15.3 Source type

An ONIX code indicating the type of source from which the cited material originated, eg radio, TV. Optional, and non-repeating.

  Fixed length, two digits
  List 157
  SourceType
  x431
  0…1
  `<SourceType>03</SourceType>` (Radio)

##### Review rating composite

An optional group of data elements which together specify a ‘star rating’ awarded as part of a review of the publication, used where <CitedContentType> indicates the cited content is a review. Not repeatable.

  ReviewRating
  reviewrating
  0…1

##### P.15.3a Review rating

An optional ‘star rating’ awarded as part of a review of the publication. Mandatory within an occurrence of the <ReviewRating> composite, and non-repeating.

  Positive real number, with explicit decimal point when required, or zero, as appropriate for the limit specified in <RatingLimit>. Suggested maximum length 7 characters
  Rating
  x525
  1
  `<Rating>4.5</Rating>` (4.5 out of 5 stars)

##### P.15.3b Review rating limit

The maximum possible rating that may be awarded as part of a review of the publication. Optional, but where used, it must be greater than or equal to the specified <Rating>.

  Positive integer number, suggested maximum length 4 digits
  RatingLimit
  x526
  0…1
  `<RatingLimit>5</RatingLimit>` (4.5 out of 5 stars)

##### P.15.3c Review rating units

The ‘units’ used by a rating, eg stars, tomatoes etc. Optional, and repeatable to provide the units in multiple languages. The language attribute is optional for a single instance of <RatingUnits>, but must be included in each instance if <RatingUnits> is repeated.

  Variable length text, suggested maximum length 50 characters
  RatingUnits
  x527
  0…n
  language
  `<RatingUnits>stars</RatingUnits>` (4.5 out of 5 stars)

##### End of Review rating composite

##### P.15.4 Source title

The title, name or short description of a publication, broadcast, website or other source of cited content. Optional, and repeatable; required unless the cited content refers to a bestseller list, and <ListName> is present. <SourceTitle> may be repeated to provide the title in multiple languages. The language attribute is optional for a single instance of <SourceTitle>, but must be included in each instance if <SourceTitle> is repeated.

  Variable length text, suggested maximum length 300 characters
  SourceTitle
  x428
  0…n
  language
  `<SourceTitle>New York Times</SourceTitle>`

##### P.15.5 Name of bestseller list

The name of a bestseller list, when the <CitedContent> composite is used to refer to a position which a product has reached on such a list. Optional, and repeatable to provide a parallel list name in multiple languages. The language attribute is optional for a single instance of <ListName>, but must be included in each instance if <ListName> is repeated.

  Variable length text, suggested maximum length 100 characters
  ListName
  x432
  0…n
  language
  `<x432>Sunday Times Hardback Fiction</x432>`

##### P.15.6 Position on list

The position that a product has reached on a bestseller list specified in <ListName>. Optional and non-repeating. The <ListName> element must also be present if <PositionOnList> is included.

  Positive integer, suggested maximum length 3 digits
  PositionOnList
  x433
  0…1
  `<PositionOnList>1</PositionOnList>`

##### P.15.7 Citation note

A free text note giving any additional information about cited content, for example a detailed volume, issue and page reference to content cited from a periodical. Optional, and repeatable when parallel text is provided in multiple languages. The language attribute is optional for a single instance of <CitationNote>, but must be included in each instance if <CitationNote> is repeated.

  Variable length text, suggested maximum length 300 characters. XHTML is enabled in this element – see Using XHTML, HTML, XML, JSON within ONIX text fields
  CitationNote
  x434
  0…n
  language, textformat
  `<CitationNote>Volume 3, page 7</CitationNote>`

##### P.15.8 Resource link

A URL which provides a link to cited content which is accessible in digital form. Optional, and repeatable if the resource can be linked in more than one way, eg by URL or DOI, or where a cited resource is available in multiple parallel languages. Where multiple languages are used, all repeats must carry the language attribute.

  Uniform Resource Locator, expressed in full URI syntax in accordance with W3C standards, suggested maximum length 300 characters. Note that non-ASCII characters, spaces and a handful of other special characters should be ‘URL-encoded’. Any ampersand used to separate parameters in the URL must be expressed as &amp;
  ResourceLink
  x435
  0…n
  language
  `<x435>https://www.zzzzzzzz.com/resource.htm</x435>`

##### Content date composite

An optional and repeatable group of data elements which together specify a date associated with cited content, eg date on which it was published or broadcast.

  ContentDate
  contentdate
  0…n

##### P.15.9 Content date role code

An ONIX code indicating the significance of the date in relation to the cited content. Mandatory in each occurrence of the <ContentDate> composite, and non-repeating.

  Fixed length, two digits
  List 155
  ContentDateRole
  x429
  1
  `<ContentDateRole>01</ContentDateRole>` (Publication date)

##### P.15.11 Date

The date specified in the <ContentDateRole> field. Mandatory in each occurrence of the <ContentDate> composite, and non-repeating. <Date> may carry a dateformat attribute: if the attribute is missing, then the default format is YYYYMMDD.

  As specified by the value in the dateformat attribute, or the default YYYYMMDD
  Date
  b306
  1
  dateformat
  `<b306 dateformat="00">20010106</b306>`

##### End of Content date composite

##### End of Cited content composite

  citing a review
  using Reference names |
  --- | ---
  `<CitedContent>` |
  `<SequenceNumber>1</SequenceNumber>` |
  `<CitedContentType>01</CitedContentType>` |
  `<ContentAudience>00</ContentAudience>` |
  `<SourceType>01</SourceType>` |
  `<SourceTitle>The Guardian</SourceTitle>` |
  `<CitationNote>Review of Jonathan Franzen’s ‘Freedom’ by Blake Morrison</CitationNote>` |
  `<ResourceLink>http://www.​guardian.​co.​uk/​books/​2010/​sep/​18/​jonathan-​franzen-​freedom-​blake-​morrison</ResourceLink>` |
  `<ContentDate>` |
  `<ContentDateRole>01</ContentDateRole>` |
  `<Date dateformat="00">20100918</Date>` |
  `</ContentDate>` |
  `</CitedContent>` |

  using Short tags |
  --- | ---
  `<citedcontent>` |
  `<b034>1</b034>` |
  `<x430>01</x430>` | Review
  `<x427>00</x427>` | Any audience
  `<x431>01</x431>` | Printed media
  `<x428>The Guardian</x428>` |
  `<x434>Review of Jonathan Franzen’s ‘Freedom’ by Blake Morrison</x434>` |
  `<x435>http://www.​guardian.​co.​uk/​books/​2010/​sep/​18/​jonathan-​franzen-​freedom-​blake-​morrison</x435>` | URL
  `<contentdate>` |
  `<x429>01</x429>` | Published
  `<b306 dateformat="00">20100918</b306>` |
  `</contentdate>` |
  `</citedcontent>` |

#### P.16 Links to supporting resources

Group P.16 describes supporting resources, with links to their web addresses. In ONIX 3.0 and later, a supporting resource is a piece of content in digital form which is offered by a publisher or other supply chain participant to be used by the receiver of an ONIX feed for promotional purposes, or as additional information. The key distinction between supporting resources and cited content (P.15) is that a supporting resource comes with a clear invitation to the receiver to use it (subject to any specified limitations), while cited content is the intellectual property of a third party, subject to that party’s copyright or other rights, and can only be referenced.

##### Supporting resource composite

An optional group of data elements which together describe a supporting resource. The composite is repeatable to describe and link to multiple resources. Note that different forms of the same resource (for example a cover image in separate low and high resolution versions) should be specified in a single instance of the composite.

  SupportingResource
  supportingresource
  0…n

##### P.16.1 Supporting resource sequence number

A number which specifies a single overall sequence of supporting resources. Optional and non-repeating. It is strongly recommended that if any occurrence of the <SupportingResource> composite of a specific <ResourceContentType> carries a <SequenceNumber>, then all of that type should carry a <SequenceNumber> – though there is no requirement to number supporting resources where there is a single instance of that type.

  Positive integer, 1, 2, 3 etc, suggested maximum length 3 digits
  SequenceNumber
  b034
  0…1
  `<SequenceNumber>3</SequenceNumber>`

##### P.16.1a Resource content type code

An ONIX code indicating the type of content carried in a supporting resource. Mandatory in each occurrence of the <SupportingResource> composite, and non-repeating.

  Fixed length, two digits
  List 158
  ResourceContentType
  x436
  1
  `<ResourceContentType>01</ResourceContentType>` (Front cover)

##### P.16.2 Target audience

An ONIX code which identifies the audience for which the supporting resource is intended. Mandatory in each occurrence of the <SupportingResource> composite, and repeatable.

  Fixed length, two digits
  List 154
  ContentAudience
  x427
  1…n
  `<x427>00</x427>` (Unrestricted [any audience])

##### Territory composite

A group of data elements which together define a territory for which the supporting resource is specifically intended. Optional in each occurrence of the <SupportingResource> composite, and non-repeating. If omitted, the supporting resource is intended for use wherever the product may be sold (see Territorial sales rights in Group P.21). If included, the resource should be used by recipients in the specified territory only, and in preference to any supporting resource that lacks a specified territory.

For valid combinations of <CountriesIncluded>, <RegionsIncluded> etc within <Territory>, see the notes describing the use of <Territory> within Group P.21.

Care should be taken to avoid ambiguities (for example two different cover images marked for use in the same country or region), and to ensure that appropriate resources are supplied for all countries and regions where the product may be sold. The simplest way to accomplish the latter is to ensure at least one version of the resource does not have a territory specified. Where multiple resources of the same type are provided, those without specific <Territory> composites are intended for use only where no appropriate targeted resource is present.

  Territory
  territory
  0…1

##### P.16.2a to P.16.2d: elements in the Territory composite

Elements P.16.2a to P.16.2d in the <Territory> composite are identical to P.14.2a to P.14.2d as specified in Group P.14.

##### End of Territory composite

##### P.16.3 Resource mode

An ONIX code indicating the mode of the supporting resource, eg audio, video. Mandatory in each occurrence of the <SupportingResource> composite, and non-repeating.

  Fixed length, two digits
  List 159
  ResourceMode
  x437
  1
  `<ResourceMode>03</ResourceMode>` (Still image)

##### Resource feature composite

A group of data elements which together describe a feature of a supporting resource which is common to all versions in which the resource is offered. Optional, and repeatable in order to describe multiple features of the resource.

  ResourceFeature
  resourcefeature
  0…n

##### P.16.4 Resource feature type

An ONIX code which specifies the feature described by an instance of the <ResourceFeature> composite. Mandatory in each occurrence of the composite, and non-repeating.

  Fixed length, two digits
  List 160
  ResourceFeatureType
  x438
  1
  `<x438>01</x438>` (Required credit)

##### P.16.5 Resource feature value

A controlled value that describes a resource feature. Presence or absence of this element depends on the <ResourceFeatureType>, since some features may not require an accompanying value, while others may require free text in <FeatureNote>; and others may have both code and free text. Non-repeating.

  Dependent on the scheme specified in <ResourceFeatureType>
  Dependent on the scheme specified in <ResourceFeatureType>
  FeatureValue
  x439
  0…1
  `<FeatureValue>4</FeatureValue>`

##### P.16.6 Resource feature note

If the <ResourceFeatureType> requires free text rather than a code value, or if the code in <FeatureValue> does not adequately describe the feature, a short text note may be added. Optional, and repeatable when parallel notes are provided in multiple languages. The language attribute is optional for a single instance of <FeatureNote>, but must be included in each instance if <FeatureNote> is repeated.

  Variable length text, suggested maximum length 300 characters. XHTML is enabled in this element – see Using XHTML, HTML, XML, JSON within ONIX text fields
  FeatureNote
  x440
  0…n
  language, textformat
  `<FeatureNote>Photo by Jerry Bauer</FeatureNote>`

##### End of Resource feature composite

##### Resource version composite

A group of data elements which together describe a single version of a supporting resource, for example a particular format of a cover image. At least one instance is mandatory in each occurrence of the <SupportingResource> composite, and the composite should be repeated as necessary if the resource is offered in multiple versions.

  ResourceVersion
  resourceversion
  1…n

##### P.16.7 Resource form

An ONIX code indicating the form of a version of a supporting resource. Mandatory in each occurrence of the <ResourceVersion> composite, and non-repeating.

  Fixed length, two digits
  List 161
  ResourceForm
  x441
  1
  `<ResourceForm>02</ResourceForm>` (Downloadable file)

##### Resource version feature composite

A group of data elements which together describe a feature of a supporting resource which is specific to a particular version in which the resource is offered. Formally optional, but it is unlikely that a supporting resource version could be adequately described without specifying some of its features. Repeatable in order to specify multiple features of the version of the resource.

  ResourceVersionFeature
  resourceversionfeature
  0…n

##### P.16.8 Resource version feature type

An ONIX code which specifies a feature described by an instance of the <ResourceVersionFeature> composite. Mandatory in each occurrence of the composite, and non-repeating.

  Fixed length, two digits
  List 162
  ResourceVersionFeatureType
  x442
  1
  `<x442>03</x442>` (Image width in pixels)

##### P.16.9 Resource version feature value

A controlled value that describes a resource version feature. Presence or absence of this element depends on the <ResourceVersionFeatureType>, since some features may not require an accompanying value, while others may require free text in <FeatureNote>, and others may have both a value and free text. Non-repeating.

  Dependent on the feature specified in <ResourceVersionFeatureType>; the feature value may or may not be taken from a code list
  Dependent on the feature specified in <ResourceVersionFeatureType>
  For file format, use List 178
  FeatureValue
  x439
  0…1
  `<FeatureValue>250</FeatureValue>`

##### P.16.10 Resource version feature note

If the <ResourceVersionFeatureType> requires free text rather than a code value, or if the code in <FeatureValue> does not adequately describe the feature, a short text note may be added. Optional, and repeatable when parallel notes are provided in multiple languages. The language attribute is optional for a single instance of <FeatureNote>, but must be included in each instance if <FeatureNote> is repeated.

  Variable length text, suggested maximum length 300 characters. XHTML is enabled in this element – see Using XHTML, HTML, XML, JSON within ONIX text fields
  FeatureNote
  x440
  0…n
  language, textformat

##### End of Resource version feature composite

##### P.16.11 Resource link

A URL which provides a link to a supporting resource. Mandatory in each occurrence of the <ResourceVersion> composite, and repeatable if the resource can be linked in more than one way, eg by URL or DOI, or where a supporting resource is available in multiple parallel languages. Where multiple languages are used, all repeats must carry the language attribute.

  Uniform Resource Locator, expressed in full URI syntax in accordance with W3C standards, suggested maximum length 300 characters. Note that non-ASCII characters, spaces and a handful of other special characters should be ‘URL-encoded’. Any ampersand used to separate parameters in the URL must be expressed as &amp;
  ResourceLink
  x435
  1…n
  language
  `<x435>https://www.zzzzzzzz.com/resource.jpg</x435>`

##### Usage constraint composite (supporting resource)

An optional group of data elements which together describe a usage constraint specific to a particular version of the resource offered. Repeatable in order to describe multiple constraints on usage.

  EpubUsageConstraint
  epubusageconstraint
  0…n

##### P.16.11a to P.16.11d: elements in the EpubUsageConstraint composite

Elements P.16.11a to P.16.11d in the <EpubUsageConstraint> composite are identical to P.3.17 to P.3.20 in Group P.3.

##### End of Usage constraint composite

##### Digital license composite (supporting resource)

An optional composite carrying the name or title of the license governing use of the specific version of the resource offered, a link to the license terms in eye-readable or machine-readable form, and optional dates when the license is valid. Repeatable in order to specify multiple licenses with differing periods of validity.

Note that in the case of multiple Digital license composites, any Usage constraints (above) apply to the current license.

  EpubLicense
  epublicense
  0…n

##### P.16.11e to P.16.11j: elements in the EpubLicense composite

Elements P.16.11e to P.16.11j in the <EpubLicense> composite are identical to P.3.20a to P.3.20f in Group P.3.

##### End of Digital license composite

##### Content date composite

An optional group of data elements which together specify a date associated with a supporting resource version, eg the date until which the resource version will be available for download. Repeatable to specify different dates with their various roles.

  ContentDate
  contentdate
  0…n

##### P.16.12 Content date role code

An ONIX code indicating the significance of the date in relation to the supporting resource. Mandatory in each occurrence of the <ContentDate> composite, and non-repeating.

  Fixed length, two digits
  List 155
  ContentDateRole
  x429
  1
  `<x429>15</x429>` ([Resource available] Until)

##### P.16.14 Date

The date specified in the <ContentDateRole> field. Mandatory in each occurrence of the <ContentDate> composite, and non-repeating. <Date> may carry a dateformat attribute: if the attribute is missing, then the default format is YYYYMMDD.

  As specified by the value in the dateformat attribute, or the default YYYYMMDD
  Date
  b306
  1
  dateformat
  `<b306 dateformat="00">20100106</b306>`

##### End of Content date composite

##### End of Resource version composite

##### End of Supporting resource composite

  Front cover, available as either a large TIFF or a JPEG thumbnail
  using Reference names |
  --- | ---
  `<SupportingResource>` |
  `<ResourceContentType>01</ResourceContentType>` |
  `<ContentAudience>00</ContentAudience>` |
  `<ResourceMode>03</ResourceMode>` |
  `<!-- Resource features go here -->` |
  `<ResourceVersion>` |
  `<ResourceForm>02</ResourceForm>` |
  `<ResourceVersionFeature>` |
  `<ResourceVersionFeatureType>01 </ResourceVersionFeatureType>` |
  `<FeatureValue>D504</FeatureValue>` |
  `</ResourceVersionFeature>` |
  `<ResourceLink>http://www.publisher.com/covers/ 9780001234567.tif</ResourceLink>` |
  `<ContentDate>` |
  `<ContentDateRole>17</ContentDateRole>` |
  `<Date dateformat="00">20100412</Date>` |
  `</ContentDate>` |
  `</ResourceVersion>` |
  `<ResourceVersion>` |
  `<ResourceForm>01</ResourceForm>` |
  `<ResourceVersionFeature>` |
  `<ResourceVersionFeatureType>01 </ResourceVersionFeatureType>` |
  `<FeatureValue>D502</FeatureValue>` |
  `</ResourceVersionFeature>` |
  `<ResourceVersionFeature>` |
  `<ResourceVersionFeatureType>02 </ResourceVersionFeatureType>` |
  `<FeatureValue>171</FeatureValue>` |
  `</ResourceVersionFeature>` |
  `<ResourceVersionFeature>` |
  `<ResourceVersionFeatureType>03 </ResourceVersionFeatureType>` |
  `<FeatureValue>125</FeatureValue>` |
  `</ResourceVersionFeature>` |
  `<ResourceLink>http://www.publisher.com/covers/ 9780001234567.jpg</ResourceLink>` |
  `<ContentDate>` |
  `<ContentDateRole>17</ContentDateRole>` |
  `<Date dateformat="00">20100412</Date>` |
  `</ContentDate>` |
  `</ResourceVersion>` |
  `</SupportingResource>` |

  using Short tags |
  --- | ---
  `<supportingresource>` | A resource
  `<x436>01</x436>` | Is front cover
  `<x427>00</x427>` | For all audiences
  `<x437>03</x437>` | Is an image
  `<!-- resource features go here -->` | eg caption, credit
  `<resourceversion>` | Resource version 1
  `<x441>02</x441>` | Downloadable
  `<resourceversionfeature>` |
  `<x442>01</x442>` | File format
  `<x439>D504</x439>` | TIFF
  `</resourceversionfeature>` |
  `<x435>http://www.publisher.com/covers/ 9780001234567.tif</x435>` | URL
  `<contentdate>` |
  `<x429>17</x429>` | Last updated
  `<b306 dateformat="00">20100412</b306>` |
  `</contentdate>` |
  `</resourceversion>` |
  `<resourceversion>` | Resource version 2
  `<x441>01</x441>` | Linkable
  `<resourceversionfeature>` |
  `<x442>01</x442>` | File format
  `<x439>D502</x439>` | JPEG
  `</resourceversionfeature>` |
  `<resourceversionfeature>` |
  `<x442>02</x442>` | Image height
  `<x439>171</x439>` | 171 pixels
  `</resourceversionfeature>` |
  `<resourceversionfeature>` |
  `<x442>03</x442>` | Image width
  `<x439>125</x439>` | 125 pixels
  `</resourceversionfeature>` |
  `<x435>http://www.publisher.com/covers/ 9780001234567.jpg</x435>` | URL
  `<contentdate>` |
  `<x429>17</x429>` | Last updated
  `<b306 dateformat="00">20100412</b306>` |
  `</contentdate>` |
  `</resourceversion>` |
  `</supportingresource>` |

#### P.17 Prizes

Group P.17 covers details of any prizes or awards that have been won by a product or by a work which is manifested in the product.

##### Prize or award composite

An optional group of data elements which together describe a prize or award won by the product or work, and repeatable where it has gained multiple prizes or awards.

  Prize
  prize
  0…n

##### P.17.1 Prize sequence number

A number which specifies a single overall sequence of prizes. Optional and non-repeating. It is strongly recommended that if any occurrence of the <Prize> composite carries a <SequenceNumber>, then all should carry a <SequenceNumber>.

  Positive integer, 1, 2, 3 etc, suggested maximum length 3 digits
  SequenceNumber
  b034
  0…1
  `<b034>3</b034>`

##### Prize identifier composite

A group of data elements which together specify an identifier for the Prize. The composite is optional, and repeatable if more than one identifier for the same prize is sent.

  PrizeIdentifier
  prizeidentifier
  0…n

##### P.17.1a Prize identifier type

An ONIX code identifying a scheme from which an identifier in the <IDValue> element is taken. Mandatory in each occurrence of the <PrizeIdentifier> composite, and non-repeating.

  Fixed length, two alphanumeric characters
  List 263
  PrizeIDType
  x589
  1
  `<x589>01</x589>` (Proprietary)

##### P.17.1b Identifier type name

A name which identifies a proprietary identifier scheme (ie a scheme which is not a standard and for which there is no individual ID type code). Must be included when, and only when, the code in the <PrizeIDType> element indicates a proprietary scheme. Optional and non-repeating.

  Variable length text, suggested maximum length 100 characters
  IDTypeName
  b233
  0…1
  language
  `<IDTypeName>Boek.be Prijs ID</IDTypeName>`

##### P.17.1c Identifier value

An identifier of the type specified in the <PrizeIDType> element. Mandatory in each occurrence of the <PrizeIdentifier> composite, and non-repeating.

  According to the identifier type specified in <PrizeIDType>
  IDValue
  b244
  1
  `<IDValue>78256920-64e0-489b-aea5-841e66f12a48</IDValue>` (UUID)

##### End of Prize identifier composite

##### P.17.1d Prize or award name

The name of a prize or award which the product or work has received. Mandatory in each occurrence of the <Prize> composite, and repeatable to provide a parallel award name in multiple languages. The language attribute is optional for a single instance of <PrizeName>, but must be included in each instance if <PrizeName> is repeated.

  Variable length text, suggested maximum length 100 characters
  PrizeName
  g126
  1…n
  language
  `<PrizeName>Man Booker Prize</PrizeName>`

##### P.17.2 Prize or award year

The year in which a prize or award was given. Optional and non-repeating.

  Four digits, YYYY
  PrizeYear
  g127
  0…1
  `<PrizeYear>1999</PrizeYear>`

##### P.17.2a Awarding body

The name of the organization(s) that awarded the prize. Optional, and repeatable if the text is provided in more than one language. The language attribute is optional for a single instance of <AwardingBody>, but must be included in each instance if <AwardingBody> is repeated.

  Variable length text, suggested maximum length 100 characters
  AwardingBody
  x584
  0…n
  language
  `<AwardingBody>Deutsche Akademie für Sprache und Dichtung</AwardingBody>`

##### P.17.3 Prize or award country

An ONIX code identifying the country in which a prize or award is given. Optional and non-repeating.

  Fixed length, two letters, based on ISO 3166-1. Note that ISO 3166-1 specifies that country codes shall be sent as upper case only
  List 91/dd>
  PrizeCountry
  g128
  0…1
  `<g128>US</g128>`

##### P.17.3a Prize or award region

An ONIX code identifying the region in which a prize or award is given. Optional and non-repeatable. A region is an area which is not a country, but which is precisely defined in geographical terms, eg Newfoundland and Labrador, Florida. If both country and region are specified, the region must be within the country. Note that US States have region codes, while US overseas territories have distinct ISO Country Codes.

  Variable length code, consisting of upper case letters, with or without a hyphen and further upper case letters or digits. Suggested maximum length 8 characters
  List 49 Where possible and appropriate, country subdivision codes are derived from the UN LOCODE scheme based on ISO 3166-2
  PrizeRegion
  x556
  0…1
  `<PrizeRegion>GB-WLS</PrizeRegion>` (Wales)

##### P.17.4 Prize or award achievement code

An ONIX code indicating the achievement of the product in relation to a prize or award, eg winner, runner-up, shortlisted. Optional and non-repeating.

  Fixed length, two digits
  List 41
  PrizeCode
  g129
  0…1
  `<PrizeCode>02</PrizeCode>` (Runner up)

##### P.17.4a Prize statement

A short free-text description of the prize or award, intended primarily for display. Optional, and repeatable if the text is provided in more than one language. The language attribute is optional for a single instance of <PrizeStatement>, but must be included in each instance if <PrizeStatement> is repeated.

<PrizeStatement> is intended for display purposes only. When used, a <PrizeStatement> must be complete in itself, ie it should not be treated as merely supplementary to other elements within the <Prize> composite. Nor should <PrizeStatement> be supplied instead of those other elements – at minimum, the <PrizeCode> element, and whenever appropriate the <PrizeYear> element should be supplied.

  Variable length text, suggested maximum length 500 characters. XHTML is enabled in this element – see Using XHTML, HTML, XML, JSON within ONIX text fields
  PrizeStatement
  x503
  0…n
  language, textformat
  `<PrizeStatement language="eng" textformat="05"><p>Joint winner of the <cite>Mao Dun Literature Prize</cite>, 2000</p></PrizeStatement>`

##### P.17.5 Prize or award jury

Free text listing members of the jury that awarded the prize. Optional, and repeatable if the text is provided in more than one language. The language attribute is optional for a single instance of <PrizeJury>, but must be included in each instance if <PrizeJury> is repeated.

  Variable length text, suggested maximum length 500 characters. XHTML is enabled in this element – see Using XHTML, HTML, XML, JSON within ONIX text fields
  PrizeJury
  g343
  0…n
  language, textformat
  `<g343>Russell Banks, Victoria Glendinning and Alistair MacLeod</g343>`

##### End of Prize or award composite

  multiple prizewinner
  using Reference names |
  --- | ---
  `<Prize>` |
  `<SequenceNumber>1</SequenceNumber>` |
  `<PrizeName>Giller Prize</PrizeName>` |
  `<PrizeYear>1996</PrizeYear>` |
  `<AwardingBody>Giller Prize Foundation</AwardingBody>` |
  `<PrizeCountry>CA</PrizeCountry>` |
  `<PrizeCode>01</PrizeCode>` |
  `<PrizeJury>Bonnie Burnard, Carol Shields and David Staines</PrizeJury>` |
  `</Prize>` |
  `<Prize>` |
  `<SequenceNumber>2</SequenceNumber>` |
  `<PrizeName>Booker Prize</PrizeName>` |
  `<PrizeYear>1996</PrizeYear>` |
  `<PrizeCountry>GB</PrizeCountry>` |
  `<PrizeCode>04</PrizeCode>` |
  `<PrizeStatement>Among the six novels shortlisted for the 1996 Booker Prize</PrizeStatement>` |
  `</Prize>` |

  using Short tags |
  --- | ---
  `<prize>` |
  `<b034>1</b034>` |
  `<g126>Giller Prize</g126>` |
  `<g127>1996</g127>` |
  `<x584>Giller Prize Foundation</x584>` |
  `<g128>CA</g128>` |
  `<g129>01</g129>` | Winner
  `<g343>Bonnie Burnard, Carol Shields and David Staines</g343>` |
  `</prize>` |
  `<prize>` |
  `<b034>2</b034>` |
  `<g126>Booker Prize</g126>` |
  `<g127>1996</g127>` |
  `<g128>GB</g128>` |
  `<g129>04</g129>` | Shortlisted
  `<x503>Among the six novels shortlisted for the 1996 Booker Prize</x503>` |
  `</prize>` |

#### End of Collateral detail composite

### Block 7: Promotion detail

#### Promotion detail composite

The promotion detail block comprises the single data Group P.27. The block as a whole is optional and non-repeating, and is used only when there is a need to describe various promotional events intended to promote the product in a structured way. When used, the block usually consists of one or more instances of <PromotionalEvent>. It may be empty only within a partial or ‘block update’ (Notification or update type 04, see P.1.2), when the intention is to remove all previously-supplied promotion detail.

  PromotionDetail
  promotiondetail
  0…1

#### P.27 Promotional events

Block 7 may contain one or more repeats of the <PromotionalEvent> composite, each describing a single event such as an author tour organized to promote the product or work. The event consists of one or more occurrences, for example a particular stop on a tour. Each occurrence shares key attributes such as the event type and the participants with other occurrences, while having unique attributes such as the date, time and location.

##### Promotional event composite

An group of data elements which together describe a promotional event or series of event occurrences such as an author tour. Optional in any occurrence of the <PromotionDetail> composite, but it may be omitted only within a partial or ‘block update’ (Notification or update type 04, see P.1.2) when the intention is to remove all previously supplied promotional event detail. When used normally, it is repeatable to describe multiple events linked to promotion of the product.

The promotional event composite must contain at least one <EventOccurrence>. It may optionally contain one or more contributors to the event, listing those that are also contributors to the product using <ContributorReference> and those that are not contributors to the product using <Contributor>. If there are no contributors to the event of either type, an optional <NoContributor/> flag may be included instead.

  PromotionalEvent
  promotionalevent
  0…n

##### Event identifier composite

An optional group of data elements which together define an identifier for an event. The composite is repeatable in order to specify multiple identifiers for the same event.

  EventIdentifier
  eventidentifier
  0…n

##### P.27.1 Event identifier type

An ONIX code which identifies the scheme from which the value in the <IDValue> element is taken. Since there is no suitable standard event identifier scheme, the only valid option is to use a proprietary identifier. Mandatory in each occurrence of the <EventIdentifier> composite.

  Fixed length, two digits
  List 244
  EventIDType
  x547
  1
  `<EventIDType>01</EventIDType>` (Proprietary)

##### P.27.2 Identifier type name

A name which identifies a proprietary identifier scheme (ie a scheme which is not a standard and for which there is no individual ID type code). Must be included when, and only when, the code in the <EventIDType> element indicates a proprietary scheme. Optional and non-repeating.

  Variable length text, suggested maximum length 100 characters
  IDTypeName
  b233
  0…1
  language
  `<b233>XYZ Publishers Event Number</b233>`

##### P.27.3 Identifier value

A code value taken from the scheme specified in the <EventIDType> element. Mandatory in each occurrence of the <EventIdentifier> composite, and non-repeating.

  Determined by the scheme specified in <EventIDType>
  IDValue
  b244
  1
  `<b244>9887933e-314b-4295-862b-12acfebd1a60</b244>` (this is a UUID – see https://uuidgenerator.net)

##### End of Event identifier composite

##### P.27.4 Event type

A mandatory ONIX code which specifies the type of promotional event. Repeatable for promotional events which combine different event types.

  Fixed length, two digits
  List 245
  EventType
  x548
  1…n
  `<x548>01</x548>` (Book signing)

##### P.27.5 Event status

An ONIX code which specifies the status of a promotional event. Optional within each instance of the <PromotionalEvent> composite, and non-repeatable.

  Fixed length, single character
  List 246
  EventStatus
  x549
  0…1
  `<EventStatus>A</EventStatus>` (Announced)

##### P.27.6 Target audience

An ONIX code which identifies the audience for which a promotional event is intended. Mandatory within in each instance of the <PromotionalEvent> composite, and repeatable.

  Fixed length, two digits
  List 154
  ContentAudience
  x427
  1…n
  `<ContentAudience>03</ContentAudience>` (End customers)

##### P.27.7 Event name

The name of or headline for a promotional event or series of events which relate to the product. This element is mandatory within each instance of the <PromotionalEvent> composite, and repeatable to provide parallel names for a single event in multiple languages. The language attribute is optional for a single instance of <EventName>, but must be included in each instance if <EventName> is repeated.

  Variable length text, suggested maximum length 200 characters
  EventName
  x516
  1…n
  language
  `<x516>Meet the Writer: Daniel Handler (aka Lemony Snicket)</x516>`

##### Contributor by reference composite

Optional composite that identifies a contributor – a person or corporate body – participating in the promotional event who is also a contributor to the product, or who is its subject (ie who is fully described in an instance of the <Contributor> composite within Groups P.5, P.7 or P.18, or in an instance of <NameAsSubject> within Groups P.12 or P.18, in the same Product record). Repeatable to refer to multiple contributors.

Note that an instance of <PromotionalEvent> may also contain one or more <Contributor> composites – the latter listing participants to the event who are not contributors to the product.

  ContributorReference
  contributorreference
  0…n

##### P.27.8 Event contributor sequence number

A number which specifies a single overall sequence of event participant names. Optional and non-repeating. It is strongly recommended that each occurrence of the <ContributorReference> and <Contributor> composites within <PromotionalEvent> should carry a <SequenceNumber>. The sequence is independent of the sequence of contributors to the product specified in Groups P.5, P.7 or P.18.

  Positive integer, 1, 2, 3 etc, suggested maximum length 3 digits
  SequenceNumber
  b034
  0…1
  `<SequenceNumber>3</SequenceNumber>`

##### P.27.9 Event contributor role

An ONIX code indicating the role played by a person or corporate body participating in a promotional event, which need not be the same role as specified for the contributor referenced in Groups P.5, P.7 or P.18. Mandatory in each instance of the <ContributorReference> composite, and may be repeated if the same person or corporate body has more than one role in relation to the event.

  Fixed length, one letter and two digits
  List 17
  ContributorRole
  b035
  1…n
  `<b035>E09</b035>` (Speaker)

##### Name identifier composite

A group of data elements which together specify a name identifier, used here to carry an identifier for a personal or organizational name which must match a name identifier in an instance of the <Contributor> composite within Groups P.5, P.7 or P.18, or in an instance of <NameAsSubject> within Groups P.12 or P.18, in the same Product record. The <NameIdentifier> composite is mandatory within each instance of the <ContributorReference> composite, and is repeatable to specify name identifiers of different types for the same person or organization name.

  NameIdentifier
  nameidentifier
  1…n

##### P.27.10 to P.27.12: elements in the Name identifier composite

Elements P.27.10 to P.27.12 in the <NameIdentifier> composite are identical to P.7.6 to P.7.8 as specified in Group P.7.

##### End of Name identifier composite

##### End of Contributor by reference composite

  reference to author participating in a promotional event
  using Reference names |
  --- | ---
  `<ContributorReference>` |
  `<SequenceNumber>1</SequenceNumber>` |
  `<ContributorRole>E09</ContributorRole>` |
  `<NameIdentifier>` |
  `<NameIDType>16</NameIDType>` |
  `<IDValue>0000000121466844</IDValue>` |
  `</NameIdentifier>` |
  `</ContributorReference>` |

  using Short tags |
  --- | ---
  `<contributorreference>` |
  `<b034>1</b034>` |
  `<b035>E09</b035>` | Speaker
  `<nameidentifier>` |
  `<x415>16</x415>` | ISNI
  `<b244>0000000121466844</b244>` |
  `</nameidentifier>` |
  `</contributorreference>` |

##### Contributor composite

Optional composite that describes a contributor – a person or corporate body – participating in the promotional event who is neither a contributor to the product, nor its subject (ie is not described in an instance of the <Contributor> composite within Groups P.5, P.7 or P.18, or in an instance of <NameAsSubject> within Groups P.12 or P.18, in the same Product record). Repeatable to identify multiple contributors.

  Contributor
  contributor
  0…n

##### P.27.13 to P.27.62a: elements in the Contributor composite

Elements P.27.13 to P.27.62a in the <Contributor> composite are identical to P.7.1 to P.7.50a as specified in Group P.7. Note the contributor sequence number should indicate the sequence within the context of the event participants (see also P.27.8). The sequence is independent of the sequence of contributors to the product specified in Groups P.5, P.7 or P.18.

##### End of Contributor composite

##### P.27.63 Contributor statement

Free text showing how the participants at a promotional event should be described in an online display, when a standard concatenation of individual Contributor reference and Contributor elements would not give a satisfactory presentation. Optional, and repeatable if parallel text is provided in multiple languages. The language attribute is optional for a single instance of <ContributorStatement>, but must be included in each instance if <ContributorStatement> is repeated. When the <ContributorStatement> field is sent, the receiver should use it to replace all name detail (though not the biographical, date or place details) sent in the <Contributor> composites for display purposes only for the promotional event. The individual name detail must also be sent in the <ContributorReference> and <Contributor> composites for indexing and retrieval.

  Variable length text, suggested maximum length 1000 characters. XHTML is enabled in this element – see Using XHTML, HTML, XML, JSON within ONIX text fields
  ContributorStatement
  b049
  0…n
  language, textformat

##### P.27.64 “No contributor” indicator

An empty element that provides a positive indication that a promotional event has no named participants. Optional and non-repeating. Must only be sent in a <PromotionalEvent> composite that has neither <ContributorReference> nor <Contributor> composites.

  XML empty element
  NoContributor/
  n339/
  0…1
  `<n339/>`

##### P.27.65 Event description

Free text describing the promotional event as a whole. Optional, and repeatable if parallel text is provided in multiple languages. The language attribute is optional for a single instance of <EventDescription>, but must be included in each instance if <EventDescription> is repeated.

  Variable length text, suggested maximum length 1000 characters. XHTML is enabled in this element – see Using XHTML, HTML, XML, JSON within ONIX text fields
  EventDescription
  x550
  0…n
  language, textformat
  `<EventDescription textformat="05"><p>Daniel Handler will be reading from his latest hardback <cite>Bottle Grove</cite>, and signing copies of this and his earlier novels.</p></EventDescription>`

##### Event occurrence composite

A group of data elements which together describe a single occurrence of the promotional event. At least one occurrence is mandatory within the <PromotionalEvent> composite, and <EventOccurrence> is repeatable in order to list a group of more or less similar occurrences such as a series of book signings.

  EventOccurrence
  eventoccurrence
  1…n

##### Event occurrence identifier composite

An optional group of data elements which together define an identifier for an event occurrence. The composite is repeatable in order to specify multiple identifiers for the same occurrence.

  EventIdentifier
  eventidentifier
  0…n

##### P.27.66 Event occurrence identifier type

An ONIX code which identifies the scheme from which the value in the <IDValue> element is taken. Since there is no suitable standard event occurrence identifier scheme, the only valid option is to use a proprietary identifier. Mandatory in each occurrence of the <EventIdentifier> composite.

  Fixed length, two digits
  List 244
  EventIDType
  x547
  1
  `<EventIDType>01</EventIDType>` (Proprietary)

##### P.27.67 Identifier type name

A name which identifies a proprietary identifier scheme (ie a scheme which is not a standard and for which there is no individual ID type code). Must be included when, and only when, the code in the <EventIDType> element indicates a proprietary scheme. Optional and non-repeating.

  Variable length text, suggested maximum length 100 characters
  IDTypeName
  b233
  0…1
  language
  `<b233>XYZ Publishers Event Number</b233>`

##### P.27.68 Identifier value

A code value taken from the scheme specified in the <EventIDType> element. Mandatory in each occurrence of the <EventIdentifier> composite, and non-repeating.

  Determined by the scheme specified in <EventIDType>
  IDValue
  b244
  1
  `<b244>9887933e-314b-4295-862b-12acfebd1a60</b244>`

##### End of Event occurrence identifier composite

##### Event occurrence date composite

A group of data elements which together specify a date associated with the event occurrence. At least the date (and typically also the time) the event occurrence begins must be specified, and other dates related to the event occurrence can be sent in further repeats of the composite.

  OccurrenceDate
  occurrencedate
  1…n

##### P.27.69 Occurrence date role

An ONIX code indicating the significance of the date, eg the date of the occurrence, last date of ticket availability etc. Mandatory in each instance of the <OccurrenceDate> composite, and non-repeating.

  Fixed length, two digits
  List 247
  OccurrenceDateRole
  x554
  1
  `<x554>01</x554>` (Date of occurrence)

##### P.27.71 Date

The date specified in the <OccurrenceDateRole> field. Mandatory in each occurrence of the <OccurrenceDate> composite, and non-repeating. <Date> may carry a dateformat attribute: if the attribute is missing, then the default format is YYYYMMDDThhmm (local time at the venue). Note that this date format may include a time zone offset (Z for times in UTC, or ±hhmm), and this should always be included where there is any doubt, eg when the event is available online.

  As specified by the value in the dateformat attribute, or the default YYYYMMDDThhmm
  Date
  b306
  1
  dateformat
  `<b306>20190405T1830+0200</b306>`(6:30pm CEST)

##### End of Event occurrence date composite

##### P.27.72 Event status

An ONIX code which specifies the status of a particular occurrence of a promotional event occurrence. Mandatory within each instance of the <EventOccurrence> composite, and non-repeatable.

  Fixed length, single character
  List 246
  EventStatus
  x549
  1
  `<x549>C</x549>` (Cancelled after having been announced)

##### P.27.73 Event country

An ONIX code identifying a country within which an event occurrence takes place. Optional and non-repeatable. For a physical event, at least one of the <CountryCode> or <RegionCode> elements is required in each instance of <EventOccurrence>. For purely digital events, both must be omitted.

  Fixed length, two letters, based on ISO 3166-1. Note that ISO 3166-1 specifies that country codes shall be sent as upper case only
  List 91
  CountryCode
  b251
  0…1
  `<b251>DE</b251>`

##### P.27.74 Event region

An ONIX code identifying a region within which an event occurrence takes place. Optional and non-repeatable. For a physical event, at least one of the <CountryCode> or <RegionCode> elements is required in each instance of <EventOccurrence>. For purely digital events, both must be omitted.

  Variable length code, consisting of upper case letters, with or without a hyphen and further upper case letters or digits. Suggested maximum length 8 characters
  List 49 Where possible and appropriate, country subdivision codes are derived from the UN LOCODE scheme based on ISO 3166-2
  RegionCode
  b398
  0…1
  `<b398>CN-BJ</b398>` (Beijing municipality, China)

##### P.27.75 Location name

The name of a city or town location within the specified country or region at which an event occurrence takes place. Optional, but required for a physical event and omitted for a purely digital event, and repeatable to provide parallel names for a single location in multiple languages (eg Baile Átha Cliath and Dublin, or Bruxelles and Brussel). It may if necessary include a postal code (eg 10680 Αθήνα, or 20090 Assago). The language attribute is optional for a single instance of <LocationName>, but must be included in each instance if <LocationName> is repeated.

  Variable length text, suggested maximum length 100 characters
  LocationName
  j349
  0…n
  language
  `<LocationName>Stephenville</LocationName>`

##### P.27.76 Venue name

The name of the venue at which the event occurrence takes place, for example the name of the bookstore. Optional, but required for a physical event and omitted for a purely digital event.

  Variable length text, suggested maximum length 100 characters
  VenueName
  x551
  0…1
  language
  `<VenueName>The Crime Blotter Bookstore</VenueName>`

##### P.27.77 Venue street address

The street address of the named venue. Optional, but typically required for physical events and omitted for a purely digital event. Care should be taken that if the Street address is provided, then the Venue name, Street address, Location name, any Postal code or Region code, and the Country code can be combined into a complete postal address, without repetition.

  Variable length text, suggested maximum length 200 characters
  StreetAddress
  x552
  0…1
  language
  `<x552>555 Crystal Parkway, Suite 2021, Spar Hill</x552>`

##### P.27.77a Venue postal code

The postal code (postcode, zip code etc), forming part of the postal address of the venue. Optional and non-repeatable if a Street address is present, but otherwise omitted.

  Variable length text, suggested maximum 20 characters
  PostalCode
  x590
  0…1
  `<x590>OH 44240</x590>`

##### P.27.78 Venue note

Free text of a short note related to the venue. Optional, and repeatable to provide parallel notes in multiple languages. The language attribute is optional for a single instance of <VenueNote>, but must be included in each instance if <VenueNote> is repeated.

  Variable length text, suggested maximum length 1000 characters. XHTML is enabled in this element – see Using XHTML, HTML, XML, JSON within ONIX text fields
  VenueNote
  x553
  0…n
  language, textformat
  `<x553 language="eng">Visitors requiring wheelchair access: please contact the venue in advance.</x553>`

##### P.27.79 Event occurrence description

Free text describing the promotional event occurrence. Optional, and repeatable to provide parallel text in multiple languages. The language attribute is optional for a single instance of <EventDescription>, but must be included in each instance if <EventDescription> is repeated.

  Variable length text, suggested maximum length 1000 characters. XHTML is enabled in this element – see Using XHTML, HTML, XML, JSON within ONIX text fields
  EventDescription
  x550
  0…n
  language, textformat
  `<EventDescription textformat="05"><p>The author will read excerpts from her new novel <cite>Crimetime</cite>, and answer audience questions.</p></EventDescription>`

##### Supporting resource composite (event occurrence)

An optional group of data elements which together describe a supporting resource related to an occurrence of a promotional event. The composite is repeatable to describe and link to multiple resources. Note that different forms of the same resource (for example a cover image in separate low and high resolution versions) should be specified in a single instance of the composite.

  SupportingResource
  supportingresource
  0…n

##### P.27.79a to P.27.79β: elements in the Supporting resource composite

P.27.79a to P.27.79β in the <SupportingResource> composite are identical to P.16.1 to P.16.14 specified in Group P.16.

##### End of Supporting resource composite (event occurrence)

##### Event occurrence sponsor composite

An optional group of data elements which together identify an organizer or sponsor of an event occurrence. Either an <EventSponsorIdentifier>, or one or other of <PersonName> or <CorporateName>, or both an identifier and a name, must be present in each occurrence of the composite. The composite is repeatable in order to specify multiple organizers and sponsors.

  EventSponsor
  eventsponsor
  0…n

##### P.27.80 to P.27.84: elements in the Event sponsor composite

P.27.80 to P.27.84 in the <EventSponsor> composite for a single occurrence of the promotional event are identical to P.8.23 to P.8.27 in Group P.8.

##### End of Event occurrence sponsor composite

##### Website composite

An optional group of data elements which together identify and provide pointers to a website which is related to the event occurrence – for example a website providing a ticketing service. Repeatable to provide links to multiple websites.

  Website
  website
  0…n

##### P.27.85 to P.27.87: elements in the Website composite

P.27.85 to P.27.87 in the <Website> composite are identical to P.8.28 to P.8.30 specified in Group P.8.

##### End of Website composite

##### End of Event occurrence composite

##### Supporting resource composite (promotional event)

An optional group of data elements which together describe a supporting resource related to a promotional event. The composite is repeatable to describe and link to multiple resources. Note that different forms of the same resource (for example a cover image in separate low and high resolution versions) should be specified in a single instance of the composite.

  SupportingResource
  supportingresource
  0…n

##### P.27.87a to P.27.87β: elements in the Supporting resource composite

P.27.87a to P.27.87β in the <SupportingResource> composite are identical to P.16.1 to P.16.14 specified in Group P.16.

##### End of Supporting resource composite (promotional event)

##### Event sponsor composite

An optional group of data elements which together identify an organizer or sponsor of an event or series of event occurrences. Either an <EventSponsorIdentifier>, or one or other of <PersonName> or <CorporateName>, or both an identifier and a name, must be present in each occurrence of the composite. The composite is repeatable in order to specify multiple organizers and sponsors.

  EventSponsor
  eventsponsor
  0…n

##### P.27.88 to P.27.92: elements in the Event sponsor composite

P.27.88 to P.27.92 in the <EventSponsor> composite for a promotional event or series of event occurrences are identical to P.8.23 to P.8.27 in Group P.8.

##### End of Event sponsor composite

##### Website composite

An optional group of data elements which together identify and provide pointers to a website which is related to the event in an instance of the <PromotionalEvent> composite. Repeatable to provide links to multiple websites.

  Website
  website
  0…n

##### P.27.93 to P.27.95: elements in the Website composite

P.27.93 to P.27.95 in the <Website> composite are identical to P.8.28 to P.8.30 specified in Group P.8.

##### End of Website composite

##### End of Promotional event composite

#### End of Promotion detail composite

### Block 3: Content detail

#### Content detail composite

The Content detail block comprises the single data Group P.18. The block as a whole is non-repeating. It is not mandatory within the <Product> record, and is used only when there is a requirement to describe individual chapters or parts within a product in a fully structured way. The more usual ONIX practice is to send a table of contents as text, possibly in XHTML, in Group P.14.

When used, the block should normally contain at least one instance of <ContentItem>. It may be empty only within a partial or ‘block update’ (Notification or update type 04, see P.1.2), when the intention is to remove all previously-supplied content detail.

  ContentDetail
  contentdetail
  0…1

#### P.18 Content items

In principle, most parts of a complete ONIX description could be nested within a <ContentItem> composite. From Release 3.0, the composite has been updated with changes that follow automatically from changes in the corresponding elements that are used elsewhere in the <Product> record, and some redundant elements have been removed.

##### Content item composite

A group of data elements which together describe a content item within a product. Optional in any occurrence of the <ContentDetail> composite, but it may be omitted only within a partial or ‘block update’ (Notification or update type 04, see P.1.2) when the intention is to remove all previously supplied content detail. When used normally, it is repeatable for each content item within the product.

  ContentItem
  contentitem
  0…n

##### P.18.1 Level sequence number

A number which specifies the position of a content item in a multi-level hierarchy of such items. Numbering starts at the top level in the hierarchy, which may represent (eg) chapters in a printed book, and the first item at the top level is numbered 1. Numbers should be assigned solely with a view to the logic of the ONIX description and not in relation to any other characteristics of the items being numbered (such as their actual numbering or their typographical layout in a printed table of contents). So for example, Chapter 2 could have a level sequence number of 3, and the second sub-section within Chapter 2 could be numbered 3.2. <LevelSequenceNumber> is not a required field, but it is strongly recommended for structured tables of contents. If used, it must occur once and only once in each occurrence of the <ContentItem> composite.

  Variable length string of positive integers, each successive integer being separated by a period character, suggested maximum length 100 characters
  LevelSequenceNumber
  b284
  0…1
  `<LevelSequenceNumber>2.24.1</LevelSequenceNumber>`

##### Text item composite

A group of data elements which are specific to text content. Optional, but exactly one of either the <TextItem> composite or the similar <AVItem> composite must occur in a <ContentItem> composite which describes a particular content item. (Similar composites may be defined for other media, and the occurrence of one of them will be mandatory in any <ContentItem> composite.)

  TextItem
  textitem
  0…1

##### P.18.2 Text item type code

An ONIX code which identifies the nature of a text item. Mandatory in each occurrence of the <TextItem> composite, and non-repeatable.

  Fixed length, two digits
  List 42
  TextItemType
  b290
  1
  `<TextItemType>04</TextItemType>` (Back matter)

##### Text item identifier composite

A repeatable group of data elements which together define an identifier of a text item in accordance with a specified scheme. The composite is optional.

  TextItemIdentifier
  textitemidentifier
  0…n

##### P.18.3 Text item identifier type code

An ONIX code identifying the scheme from which the identifier in <IDValue> is taken. Mandatory in each occurrence of the <TextItemIdentifier> composite, and non-repeating.

  Fixed length, two digits
  List 43
  TextItemIDType
  b285
  1
  `<TextItemIDType>01</TextItemIDType>` (Proprietary)

##### P.18.4 Identifier type name

A name which identifies a proprietary identifier scheme (ie a scheme which is not a standard and for which there is no individual ID type code). Must be included when, and only when, the code in <TextItemIDType> indicates a proprietary scheme, eg a publisher’s own code. Optional and non-repeating

  Variable length text, suggested maximum length 100 characters
  IDTypeName
  b233
  0…1
  language
  `<b233>McGraw</b233>`

##### P.18.5 Identifier value

An identifier of the type specified in <TextItemIDType>. Mandatory in each occurrence of the <TextItemIdentifier> composite, and non-repeating.

  According to the identifier type specified in <TextItemIDType>
  IDValue
  b244
  1
  `<b244>12345678</b244>`

##### End of Text item identifier composite

##### Page run composite

A repeatable group of data elements which together define a run of contiguous pages on which a text item appears. The composite is optional, but may be repeated where the text item covers two or more separate page runs.

  PageRun
  pagerun
  0…n

##### P.18.6 First page number

The number of the first page of a sequence of contiguous pages. Mandatory in each occurrence of the <PageRun> composite, and non-repeating. Note that here and in the <LastPageNumber> element a page ‘number’ may be Arabic, Roman, or an alphanumeric string (eg L123).

  Variable length alphanumeric, suggested maximum length 20 characters
  FirstPageNumber
  b286
  1
  `<FirstPageNumber>23</FirstPageNumber>`

##### P.18.7 Last page number

The number of the last page of a sequence of contiguous pages (ignoring any blank verso which is left after the last text page). This element is omitted if an item begins and ends on the same page; otherwise it should occur once and only once in each occurrence of the <PageRun> composite.

  Variable length alphanumeric, suggested maximum length 20 characters
  LastPageNumber
  b287
  0…1
  `<b287>35</b287>`

##### End of Page run composite

##### P.18.8 Number of pages

The page extent of a text item within a paginated product. Optional and non-repeating, but normally expected when the text item is being referenced as part of a structured table of contents.

  Positive integer, suggested maximum length 6 digits
  NumberOfPages
  b061
  0…1
  `<NumberOfPages>12</NumberOfPages>`

##### End of Text item composite

##### AV item composite

An optional group of data elements which are specific to audio or audiovisual (ie time-based) content. Exactly one of either the <AVItem> composite or the similar <TextItem> composite must occur in a <ContentItem> composite which describes a content item.

  AVItem
  avitem
  0…1

##### P.18.8a AV item type code

An ONIX code which identifies the nature of an audio or audiovisual content item. Mandatory in each occurrence of the <AVItem> composite, and non-repeatable.

  Fixed length, two digits
  List 240
  AVItemType
  x540
  1
  `<x540>03</x540>` (Body matter)

##### AV item identifier composite

A group of data elements which together define an identifier of an audio or audiovisual content item in accordance with a specified identifier scheme. The composite is optional, and repeatable in order to provide multiple identifiers for the content item.

  AVItemIdentifier
  avitemidentifier
  0…n

##### P.18.8b AV item identifier type code

An ONIX code identifying the scheme from which the identifier in <IDValue> is taken. Mandatory in each occurrence of the <AVItemIdentifier> composite, and non-repeating.

  Fixed length, two digits
  List 241
  AVItemIDType
  x541
  1
  `<AVItemIDType>01</TextItemIDType>` (Proprietary)

##### P.18.8c Identifier type name

A name which identifies a proprietary identifier scheme (ie a scheme which is not a standard and for which there is no individual ID type code). Must be used when, and only when, the code in <AVItemIDType> indicates a proprietary scheme, eg a publisher’s own code. Optional and non-repeating

  Variable length text, suggested maximum length 100 characters
  IDTypeName
  b233
  0…1
  language
  `<b233>Pearson AVID</b233>`

##### P.18.8d Identifier value

An identifier of the type specified in <AVItemIDType>. Mandatory in each occurrence of the <AVItemIdentifier> composite, and non-repeating.

  According to the identifier type specified in <AVItemIDType>
  IDValue
  b244
  1
  `<b244>12345678</b244>`

##### End of AV item identifier composite

##### Time run composite

A repeatable group of data elements which together define the time period which an AV item takes up. The composite is optional, but may be repeated where the AV item covers two or more separate periods of time.

  TimeRun
  timerun
  0…n

##### P.18.8e Start time

The time (relative to the beginning of the product’s audio or audiovisual content) of the beginning of a continuous sequence of audiovisual content. Mandatory in each occurrence of the <TimeRun> composite, and non-repeating.

  Hours, minutes and seconds in the form HHHMMSS or HHHMMSScc (hundredths of a second)
  StartTime
  x542
  1
  `<StartTime>0011206</StartTime>` (One hour, 12 minutes and six seconds)

##### P.18.8f End time

The time (relative to the beginning of the product’s audio or audiovisual content) of the end of a continuous sequence of audio or audiovisual content. Optional in each occurrence of the <TimeRun> composite, and non-repeating.

  Hours, minutes and seconds in the form HHHMMSS or HHHMMSScc (hundredths of a second)
  EndTime
  x543
  0…1
  `<x543>0014154</x543>` (One hour, 41 minutes and 54 seconds)

##### End of Time run composite

##### P.18.8g Duration of AV item

The duration of an audio or audiovisual item within the time-based content of a product. Optional and non-repeating, but normally expected when the AV content item is being referenced as part of a structured table of contents.

  Hours, minutes and seconds in the form HHHMMSS or HHHMMSScc (hundredths of a second)
  AVDuration
  x544
  0…1
  `<AVDuration>0002948</AVDuration>` (29 minutes and 48 seconds)

##### End of AV item composite

##### Usage constraint composite (content item)

An optional group of data elements which together describe a usage constraint on a content item within a digital product (or the absence of such a constraint), whether enforced by DRM technical protection, inherent in the platform used, or specified by license agreement. Repeatable in order to describe multiple constraints on usage.

  EpubUsageConstraint
  epubusageconstraint
  0…n

##### P.18.8h Usage type (content item)

An ONIX code specifying a usage of a content item within a digital content item. Mandatory in each occurrence of the <EpubUsageConstraint> composite, and non-repeating.

  Fixed length, two digits
  List 145
  EpubUsageType
  x318
  1
  `<x318>05</x318>` (Text-to-speech)

##### P.18.8i Usage status (content item)

An ONIX code specifying the status of a usage of a content item within a digital product, eg permitted without limit, permitted with limit, prohibited. Mandatory in each occurrence of the <EpubUsageConstraint> composite, and non-repeating.

  Fixed length, two digits
  List 146
  EpubUsageStatus
  x319
  1
  `<x319>03</x318>` (Prohibited)

##### Usage limit composite (content item)

An optional group of data elements which together specify a quantitative limit on a particular type of usage of a content item within a digital product. Repeatable in order to specify two or more limits on the usage type.

  EpubUsageLimit
  epubusagelimit
  0…n

##### P.18.8j Usage quantity (content item)

A numeric value representing the maximum permitted quantity of a particular type of usage. Mandatory in each occurrence of the <EpubUsageLimit> composite, and non-repeating.

  Positive real number, with explicit decimal point when required, or zero, as appropriate for the units specified in <EpubUsageUnit>
  Quantity
  x320
  1
  `<Quantity>10</Quantity>`

##### P.18.8k Usage unit (content item)

An ONIX code for a unit in which a permitted usage quantity is stated. Mandatory in each occurrence of the <EpubUsageLimit> composite, and non-repeating.

  Fixed length, two digits
  List 147
  EpubUsageUnit
  x321
  1
  `<EpubUsageUnit>07</EpubUsageUnit>` (Maximum number of concurrent users)

##### End of Usage limit composite (content item)

##### End of Usage constraint composite (content item)

##### Digital content item license composite

An optional composite carrying the name or title of the license governing use of the content item within the product, a link to the license terms in eye-readable or machine-readable form, and optional dates when the license is valid. Repeatable in order to specify multiple licenses with differing periods of validity.

Note that in the case of multiple Digital product license composites, any Usage constraints (above) apply to the current license.

  EpubLicense
  epublicense
  0…n

##### P.18.8l Digital content item license name

The name or title of the license. Mandatory in any <EpubLicense> composite, and repeatable to provide the license name in multiple languages. The language attribute is optional for a single instance of <EpubLicenseName>, but must be included in each instance if <EpubLicenseName> is repeated.

  Variable length text, suggested maximum length 100 characters
  EpubLicenseName
  x511
  1…n
  language
  `<x511>Elsevier e‑book chapter EULA v5</x511>`

##### Digital content item license expression composite

An optional composite that carries details of a link to an expression of the license terms, which may be in human-readable or machine-readable form. Repeatable when there is more than one expression of the license.

  EpubLicenseExpression
  epublicenseexpression
  0…n

##### P.18.8m License expression type (content item)

An ONIX code identifying the nature or format of the license expression specified in the <EpubLicenseExpressionLink> element. Mandatory within the <EpubLicenseExpression> composite, and non-repeating.

  Fixed-length text, two digits
  List 218
  EpubLicenseExpressionType
  x508
  1
  `<x508>10</x508>` (ONIX-PL license expression)

##### P.18.8n License expression type name (content item)

A short free-text name for a license expression type, when the code in <EpubLicenseExpressionType> provides insufficient detail – for example when a machine-readable license is expressed using a particular proprietary encoding scheme. Optional and non-repeating, and must be included when (and only when) the <EpubLicenseExpressionType> element indicates the expression is encoded in a proprietary way.

  Variable length text, suggested maximum length 100 characters
  EpubLicenseExpressionTypeName
  x509
  0…1
  language
  `<x509>ABC-XML</x509>`

##### P.18.8o License expression link (content item)

The URI for the license expression. Mandatory in each instance of the <EpubLicenseExpression> composite, and non-repeating.

  Variable length text, suggested maximum length 300 characters
  EpubLicenseExpressionLink
  x510
  1
  `<EpubLicenseExpressionLink>http://creativecommons.org/​licenses/​by/​3.0/​deed.en_GB</EpubLicenseExpressionLink>`

##### End of Digital content item license expression composite

##### Digital content item license date

An optional group of date elements which together specify a date associated with the content item license in an occurrence of the <EpubLicense> composite, eg a date when a license expires. Repeatable to specify different dates with their various roles.

Note that if no dates are specified, the license is effective at the time the ONIX message is sent.

  EpubLicenseDate
  epublicensedate
  0…n

##### P.18.8p Digital content item license date role code

An ONIX code indicating the significance of the date in relation to the license. Mandatory in each occurrence of the <EpubLicenseDate> composite, and non-repeating.

  Fixed length, two digits
  List 260
  EpubLicenseDateRole
  x585
  1
  `<EpubLicenseDateRole>14</EpubLicenseDateRole>` (license becomes effective)

##### P.18.8q Date

The date specified in the <EpubLicenseDateRole> field. Mandatory in each occurrence of the <EpubLicenseDate> composite, and non-repeating. <Date> may carry a dateformat attribute: if the attribute is missing, then the default format is YYYYMMDD.

  As specified by the value in the dateformat attribute, or the default YYYYMMDD
  Date
  b306
  1
  dateformat
  `<Date>20221028</Date>`
  Note that all dates are inclusive, so ‘Valid from’ is the first date on which the license is effective, and ‘Date until’ is the last date on which it is effective.

##### End of Digital content item license date composite

##### End of Digital content item license composite

##### P.18.9 Component type name

The generic name (if any) which is given in the product to the type of section which the content item represents, eg Chapter, Part, Track. Optional and non-repeating; but either this field or a title (in the <TitleDetail> composite), or both, must be present in each occurrence of the <ContentItem>.

  Variable length alphanumeric, suggested maximum length 20 characters
  ComponentTypeName
  b288
  0…1
  language
  `<b288>Chapter</b288>`

##### P.18.10 Component number

The number (if any) which is given to the content item in the product, in the form (eg Arabic or Roman) in which it is given in the product. Optional and non-repeating.

  Variable length alphanumeric, suggested maximum length 20 characters
  ComponentNumber
  b289
  0…1
  `<ComponentNumber>XX</ComponentNumber>`

##### Title detail composite (content item)

A repeatable group of data elements which together give the text of a title of a content item and specify its type. Optional.

  TitleDetail
  titledetail
  0…n

##### P.18.11 to P.18.18a: elements in the Title detail composite

Elements P.18.11 to P.18.18a in the <TitleDetail> composite are identical to P.6.1 to P.6.8a as specified in Group P.6.

##### End of Title detail composite (content item)

##### Contributor composite (content item)

A group of data elements which together describe a personal or corporate contributor to a content item. Optional and repeatable.

  Contributor
  contributor
  0…n

##### P.18.19 to P.18.68a: elements in the Contributor composite

Elements P.18.19 to P.18.68a in the <Contributor> composite are identical to P.7.1 to P.7.50a as specified in Group P.7. Note the contributor’s <SequenceNumber> should indicate the sequence within the context of the content item contributors. The sequence is independent of the sequence of contributors to the product specified in Groups P.5 and P.7.

##### End of Contributor composite (content item)

##### P.18.68b Contributor statement

Free text showing how the authorship of a content item should be described in an online display, when a standard concatenation of individual contributor elements would not give a satisfactory presentation. Optional, and repeatable if parallel text is provided in multiple languages. The language attribute is optional for a single instance of <ContributorStatement>, but must be included in each instance if <ContributorStatement> is repeated. When the <ContributorStatement> field is sent, the receiver should use it to replace all name detail (though not the biographical, date or place details) sent in the <Contributor> composite for display purposes only. The individual name detail must also be sent in the <Contributor> composite for indexing and retrieval.

  Variable length text, suggested maximum length 1000 characters. XHTML is enabled in this element – see Using XHTML, HTML, XML, JSON within ONIX text fields
  ContributorStatement
  b049
  0…n
  language, textformat
  `<b049>Written and illustrated by Fred and Emily Jackson</b049>`

##### P.18.68c “No authorship” indicator

An empty element that provides a positive indication that a content item has no stated authorship. Optional and non-repeating. Must only be sent in a <ContentItem> composite that has no <Contributor> elements.

  XML empty element
  NoContributor/
  n339/
  0…1
  `<NoContributor/>`

##### Language composite (content item)

An optional and repeatable group of data elements which together represent a language, and specify its role and, where required, whether it is a country variant.

  Language
  language
  0…n

##### P.18.68d to P.18.68h: elements in the Language composite

Elements P.18.68d to P.18.68h in the <Language> composite are identical to P.10.1 to P.10.4 as specified in Group P.10.

##### End of Language composite (content item)

##### Subject composite (content item)

A group of data elements which together specify a subject classification or a subject heading relating to a content item. Optional and repeatable.

  Subject
  subject
  0…n

##### P.18.69 to P.18.74: elements in the Subject composite

Elements P.18.69 to P.18.74 in the <Subject> composite are identical to P.12.1 to P.12.6 as specified in Group P.12.

##### End of Subject composite (content item)

##### Name as subject composite (content item)

An optional and repeatable group of data elements which together represent the name of a person or organization – real or fictional – that is part of the subject of a content item.

  NameAsSubject
  nameassubject
  0…n

##### P.18.75 to P.18.90y: elements in the Name as subject composite

Elements P.18.75 to P.18.90y in the <NameAsSubject> composite are identical to P.12.7 to P.12.443 as specified in Group P.12.

##### End of Name as subject composite (content item)

##### Text content composite (content item)

A group of data elements which together carry text related to a content item. Optional and repeatable.

  TextContent
  textcontent
  0…n

##### P.18.91 to P.18.99: elements in the Text content composite

Elements P.18.91 to P.18.99 in the <TextContent> composite are identical to P.14.1 to P.14.9 as specified in Group P.14.

##### End of Text content composite (content item)

##### Cited content composite (content item)

A group of data elements which together describe a piece of cited content. Optional and repeatable.

  CitedContent
  citedcontent
  0…n

##### P.18.100 to P.18.110: elements in the Cited content composite

Elements P.18.100 to P.18.110 in the <CitedContent> composite are identical to P.15.1 to P.15.11 as specified in Group P.15.

##### End of Cited content composite (content item)

##### Supporting resource composite (content item)

A group of data elements which together describe a supporting resource. Optional and repeatable.

  SupportingResource
  supportingresource
  0…n

##### P.18.111 to P.18.124: elements in the Supporting resource composite

Elements P.18.111 to P.18.124 in the <SupportingResource> composite are identical to P.16.1 to P.16.14 as specified in Group P.16.

##### End of Supporting resource composite (content item)

##### Publisher composite (content item)

A group of data elements which together identify an entity which is associated with the publishing of a content item, included here to allow roles such as Funder, Sponsor to be associated with a specific content item rather than the product as a whole. The composite allows additional publishing roles to be introduced without adding new fields. Each occurrence of the composite must carry a publishing role code and either a name identifier or a name or both. Optional, and repeatable in order to identify multiple entities.

  Publisher
  publisher
  0…n

##### P.18.124a to P.18.124k: elements in the Publisher composite

Elements P.18.124a to P.18.124j in the <Publisher> composite are identical to P.19.5 to P.19.12 as specified in Group P.19.

##### End of Publisher composite (content item)

##### Copyright statement composite (content item)

An optional and repeatable group of data elements which together represent a copyright or neighboring right statement for the content item. At least one <CopyrightYear> or one instance of the <CopyrightOwner> composite must be sent within an instance of the composite, but it is recommended that all elements in the composite are explicitly populated. The Copyright statement may be repeated to provide a full structured rights statement listing year(s) and rights holder(s).

  CopyrightStatement
  copyrightstatement
  0…n

##### P.18.124l to P.18.124r: elements in the Copyright statement composite

Elements P.18.124l to P.18.124r in the <CopyrightStatement> composite are identical to P.20.6a to P.20.12 as specified in Group P.20.

##### End of Copyright statement composite (content item)

##### P.18.124s Copyright statement text (content item)

Free text showing how the copyright of the content item should be described, when a standard concatenation of individual copyright statements would not give a satisfactory presentation. Optional but must only be used if one or more instances of <CopyrightStatement> are present, and repeatable if parallel text is provided in multiple languages. The language attribute is optional for a single instance of <CopyrightStatementText>, but must be included in each instance if <CopyrightStatementText> is repeated. When the <CopyrightStatementText> field is sent, the receiver should use it to replace all detail for the content item sent in the <CopyrightStatement> composite for display purposes only. It does not replace the <CopyrightStatement> element. The individual rightsholder detail must also be sent in one or more <CopyrightStatement> composites for indexing and retrieval purposes.

  Variable length text, suggested maximum length 500 characters. XHTML is enabled in this element – see Using XHTML, HTML, XML, JSON within ONIX text fields
  CopyrightStatementText
  x588
  0…n
  language, textformat
  `<CopyrightStatementText textformat="05"><p>Text © 2023 Amelia Winstanley, music © and ℗ 2021 Three sisters</p></CopyrightStatementText>`

##### Related work composite (content item)

A group of data elements which together describe a work which has a specified relationship to a content item. Optional and repeatable.

  RelatedWork
  relatedwork
  0…n

##### P.18.125 to P.18.128: elements in the Related work composite

Elements P.18.125 to P.18.128 in the <RelatedWork> composite are identical to P.22.1 to P.22.4 as specified in Group P.22.

##### End of Related work composite (content item)

##### Related product composite (content item)

A group of data elements which together describe a product which has a specified relationship to a content item. Optional and repeatable.

  RelatedProduct
  relatedproduct
  0…n

##### P.18.129 to P.18.134: elements in the Related product composite

Elements P.18.129 to P.18.134 in the <RelatedProduct> composite are identical to P.23.1 to P.23.6 as specified in Group P.23.

##### End of Related product composite (content item)

##### End of Content item composite

#### End of Content detail composite

### Block 4: Publishing detail

#### Publishing detail composite

The publishing detail block covers data Groups P.19 to P.21, carrying information on the publisher(s), ‘global’ publishing status, and rights attaching to a product. The block as a whole is non-repeating. It is mandatory in any <Product> record unless the <NotificationType> in Group P.1 indicates that the record is an update notice which carries only those blocks in which changes have occurred.

  PublishingDetail
  publishingdetail
  0…1

#### P.19 Publisher

Group P.19 carries details of the imprint and/or publisher of the product, as well as those of other associated entities, eg co-publishers. It may also carry details of a contact responsible for responding to promotional or sales queries about the product.

The XML Schema or DTD makes it mandatory for either <Imprint> or <Publisher> or both to be sent in any occurrence of the <PublishingDetail> block. However, inclusion of <ProductContact> is optional.

##### Imprint or brand composite

An optional group of data elements which together identify an imprint or brand under which the product is marketed. The composite must carry either a name identifier or a name or both, and is repeatable to specify multiple imprints or brands.

  Imprint
  imprint
  0…n

##### Imprint or brand identifier composite

A group of data elements which together define the identifier of an imprint name. Optional, but mandatory if the <Imprint> composite does not carry an <ImprintName>. The composite is repeatable in order to specify multiple identifiers for the same imprint or brand.

  ImprintIdentifier
  imprintidentifier
  0…n

##### P.19.1 Imprint identifier type

An ONIX code which identifies the scheme from which the value in the <IDValue> element is taken. Mandatory in each occurrence of the <ImprintIdentifier> composite.

  Fixed length, two digits
  List 44
  ImprintIDType
  x445
  1
  `<x445>01</x445>` (Proprietary)
  ‘Proprietary’ in this context indicates the code list from which <IDValue> is drawn is proprietary; it is not an indicator of trademark or proprietary rights held over the brand or imprint name itself.

##### P.19.2 Identifier type name

A name which identifies a proprietary identifier scheme (ie a scheme which is not a standard and for which there is no individual ID type code). Must be included when, and only when, the code in the <ImprintIDType> element indicates a proprietary scheme. Optional and non-repeating.

  Variable length text, suggested maximum length 100 characters
  IDTypeName
  b233
  0…1
  language
  `<IDTypeName>XYZ Publishers Imprint Code</IDTypeName>`

##### P.19.3 Identifier value

A code value taken from the scheme specified in the <ImprintIDType> element. Mandatory in each occurrence of the <ImprintIdentifier> composite, and non-repeating.

  Determined by the scheme specified in <ImprintIDType>
  IDValue
  b244
  1
  `<b244>XYZ123</b244>`

##### End of Imprint or brand identifier composite

##### P.19.4 Imprint or brand name

The name of an imprint or brand under which the product is issued, as it appears on the product. Mandatory if there is no imprint identifier in an occurrence of the <Imprint> composite, and optional if an imprint identifier is included. Non-repeating.

  Variable length text, suggested maximum length 100 characters
  ImprintName
  b079
  0…1
  language, collationkey
  `<ImprintName>Secker &amp; Warburg</ImprintName>` (note ‘&’ is a reserved character in XML)

##### End of Imprint or brand composite

  imprint name plus a proprietary list code
  using Reference names |
  --- | ---
  `<Imprint>` |
  `<ImprintIdentifier>` |
  `<ImprintIDType>01</ImprintIDType>` |
  `<IDTypeName>HCP UK List Codes<IDTypeName>` |
  `<IDValue>HCF</IDValue>` |
  `</ImprintIdentifier>` |
  `<ImprintName>Harper</ImprintName>` |
  `</Imprint>` |

  using Short tags |
  --- | ---
  `<imprint>` |
  `<imprintidentifier>` |
  `<x445>01</x445>` | Proprietary list gives
  `<b233>HCP UK List Codes</b233>` | more granular details
  `<b244>HCF</b244>` | where business units
  `</imprintidentifier>` | share an imprint/brand
  `<b079>Harper</b079>` |
  `</imprint>` |

##### Publisher composite

An optional group of data elements which together identify an entity which is associated with the publishing of a product. The composite allows additional publishing roles to be introduced without adding new fields. Each occurrence of the composite must carry a publishing role code and either a name identifier or a name or both, and the composite is repeatable in order to identify multiple entities.

  Publisher
  publisher
  0…n

##### P.19.5 Publishing role code

An ONIX code which identifies a role played by an entity in the publishing of a product. Mandatory in each occurrence of the <Publisher> composite, and non-repeating.

  Fixed length, two digits
  List 45
  PublishingRole
  b291
  1
  `<PublishingRole>02</PublishingRole>` (Co-publisher)

##### Publisher identifier composite

An optional group of data elements which together define the identifier of a publisher name. Optional, but mandatory if the <Publisher> composite does not carry a <PublisherName>. The composite is repeatable in order to specify multiple identifiers for the same publisher.

  PublisherIdentifier
  publisheridentifier
  0…n

##### P.19.6 Publisher identifier type

An ONIX code which identifies the scheme from which the value in the <IDValue> element is taken. Mandatory in each occurrence of the <PublisherIdentifier> composite.

  Fixed length, two digits
  List 44
  PublisherIDType
  x447
  1
  `<x447>03</x447>` (Deutsche Bibliothek publisher identifier)

##### P.19.7 Identifier type name

A name which identifies a proprietary identifier scheme (ie a scheme which is not a standard and for which there is no individual ID type code). Must be included when, and only when, the code in the <PublisherIDType> element indicates a proprietary scheme. Optional and non-repeating.

  Variable length text, suggested maximum length 100 characters
  IDTypeName
  b233
  0…1
  language
  `<b233>GBIPublisherCode</b233>` (GBI is a placeholder for the ‘owner’ of a proprietary code scheme)

##### P.19.8 Identifier value

A code value taken from the scheme specified in the <PublisherIDType> element. Mandatory in each occurrence of the <PublisherIdentifier> composite, and non-repeating.

  Determined by the scheme specified in <PublisherIDType>
  IDValue
  b244
  1
  `<IDValue>17499</IDValue>` (Börsenverein Verkehrsnummer)

##### End of Publisher identifier composite

  use of public identifier for publisher
  using Reference names |
  --- | ---
  `<Publisher>` |
  `<PublishingRole>01<PublishingRole>` |
  `<PublisherIdentifier>` |
  `<PublisherIDType>19</PublisherIDType>` |
  `<IDValue>09</IDValue>` |
  `</PublisherIdentifier>` |
  `<PublisherName>小学館</PublisherName>` |
  `</Publisher>` |

  using Short tags |
  --- | ---
  `<publisher>` |
  `<b291>01<b291>` | Publisher
  `<publisheridentifier>` |
  `<x447>19</x447>` | Japanese Publisher Identifier
  `<b244>09</b244>` |
  `</publisheridentifier>` |
  `<b081>小学館</b081>` | Shogakukan
  `</publisher>` |

##### P.19.9 Publisher name

The name of an entity associated with the publishing of a product. Mandatory if there is no publisher identifier in an occurrence of the <Publisher> composite, and optional if a publisher identifier is included. Repeatable if the entity is officially known by names in multiple languages. The language attribute is optional for a single instance of <PublisherName>, but must be included in each instance if <PublisherName> is repeated.

  Variable length text, suggested maximum length 100 characters
  PublisherName
  b081
  0…n
  collationkey, language, textscript
  `<PublisherName>Reed International Books</PublisherName>`
  `<b081 language="eng">World Health Organization</b081>`
  `<b081 language="fre">Organisation mondiale de la santé</b081>`

##### Funding composite

An optional group of data elements which together identify a grant or award provided by the entity specified as a funder in an occurrence of the <Publisher> composite, to subsidize research or publication. Repeatable when the funder provides multiple grants or awards. Used only when <PublishingRole> indicates the role of a funder.

  Funding
  funding
  0…n

##### Funding identifier composite

A group of data elements which together identify a particular grant or award. At least one <FundingIdentifier> composite must occur in each instance of the <Funding> composite. Repeatable when the grant or award has multiple identifiers.

  FundingIdentifier
  fundingidentifier
  1…n

##### P.19.9a Funding identifier type code

An ONIX code identifying the scheme from which the identifier in the <IDValue> element is taken. Mandatory in each occurrence of the <FundingIdentifier> composite, and non-repeating.

  Fixed length, two digits
  List 228
  FundingIDType
  x523
  1
  `<FundingIDType>01</FundingIDType>` (proprietary)

##### P.19.9b Identifier type name

A name which identifies a proprietary identifier scheme (ie a scheme which is not a standard and for which there is no individual ID type code). Must be included when, and only when, the code in the <FundingIDType> element indicates a proprietary scheme, eg a funder’s own code. Optional and non-repeating.

  Variable length text, suggested maximum length 100 characters
  IDTypeName
  b233
  0…1
  language
  `<IDTypeName>Wellcome Grant Number</IDTypeName>`

##### P.19.9c Identifier value

An identifier of the type specified in the <FundingIDType> element. Mandatory in each occurrence of the <FundingIdentifier> composite, and non-repeating.

  According to the identifier type specified in <FundingIDType>
  IDValue
  b244
  1
  `<b244>2015-16674</b244>`

##### End of Funding identifier composite

##### End of Funding composite

##### Website composite

An optional group of data elements which together identify and provide a pointer to a website which is related to the publisher identified in an occurrence of the <Publisher> composite. Repeatable in order to provide links to multiple websites.

  Website
  website
  0…n

##### P.19.10 Website purpose

An ONIX code which identifies the role or purpose of the website which is linked through the <WebsiteLink> element. Optional and non-repeating.

  Fixed length, two digits
  List 73
  WebsiteRole
  b367
  0…1
  `<WebsiteRole>18</WebsiteRole>` (Publisher’s consumer-facing website)

##### P.19.11 Website description

Free text describing the nature of the website which is linked through the <WebsiteLink> element. Optional, and repeatable to provide parallel descriptive text in multiple languages. The language attribute is optional for a single instance of <WebsiteDescription>, but must be included in each instance if <WebsiteDescription> is repeated.

  Variable length text, suggested maximum length 300 characters. XHTML is enabled in this element – see Using XHTML, HTML, XML, JSON within ONIX text fields
  WebsiteDescription
  b294
  0…n
  language, textformat

##### P.19.12 Link to website

The URL for the website. Mandatory in each occurrence of the <Website> composite, and repeatable to provide multiple URLs where the website content is available in multiple languages. The language attribute is optional for a single instance of <WebsiteLink>, but must be included in each instance if <WebsiteLink> is repeated.

  Uniform Resource Locator, expressed in full URI syntax in accordance with W3C standards, suggested maximum length 300 characters. Note that non-ASCII characters, spaces and a handful of other special characters should be ‘URL-encoded’. Any ampersand used to separate parameters in the URL must be expressed as &amp;
  WebsiteLink
  b295
  1…n
  language
  `<WebsiteLink>http://xyzbooks.com</WebsiteLink>`

##### End of Website composite

##### End of Publisher composite

  imprint and publisher names, with links to corporate websites
  using Reference names |
  --- | ---
  `<Imprint>` |
  `<ImprintName>Éditions Grasset</ImprintName>` |
  `<Imprint>` |
  `<Publisher>` |
  `<PublishingRole>01</PublishingRole>` |
  `<PublisherName>Hachette Livres</PublisherName>` |
  `<Website>` |
  `<WebsiteRole>01</WebsiteRole>` |
  `<WebsiteLink>http://www.hachette.com</WebsiteLink>` |
  `</Website>` |
  `<Website>` |
  `<WebsiteRole>01</WebsiteRole>` |
  `<WebsiteDescription>Site web pour la marque d’éditeur</WebsiteDescription>` |
  `<WebsiteLink>http://www.grasset.fr</WebsiteLink>` |
  `</Website>` |
  `</Publisher>` |
  `<CityOfPublication>Paris</CityOfPublication>` |
  `<CountryOfPublication>FR</CountryOfPublication>` |

  using Short tags |
  --- | ---
  `<imprint>` |
  `<b079>Éditions Grasset</b079>` |
  `<imprint>` |
  `<publisher>` |
  `<b291>01</b291` | Publisher
  `<b081>Hachette Livres</b081>` |
  `<website>` |
  `<b367>01</b367>` | Corporate website
  `<b295>http://www.hachette.com</b295>` |
  `</website>` |
  `<website>` |
  `<b367>01</b367>` | Corporate website
  `<b294>Site web pour la marque d’éditeur</b294>` | For the publisher’s imprint/​brand
  `<b295>http://www.grasset.fr</b295>` |
  `</website>` |
  `</publisher>` |
  `<b209>Paris</b209>` |
  `<b083>FR</b083>` |

##### P.19.13 City or town of publication

The name of a city or town associated with the imprint or publisher. Optional, and repeatable if parallel names for a single location appear on the title page in multiple languages, or if the imprint carries two or more cities of publication.

Where necessary to avoid ambiguity, a state, province or region may be included – for example ‘Springfield, IL’.

A place of publication is normally given in the form in which it appears on the title page. If the place name appears in more than one language, <CityOfPublication> may be repeated. The language attribute is optional with a single instance of <CityOfPublication>, but must be included in each instance if <CityOfPublication> is repeated.

  Variable length text, suggested maximum length 50 characters
  CityOfPublication
  b209
  0…n
  language
  `<CityOfPublication>New York</CityOfPublication>`

##### P.19.14 Country of publication

An ONIX code identifying the country where the product is published (ie where the publisher is based). Optional and non-repeating.

  Fixed length, two letters, based on ISO 3166-1. Note that ISO 3166-1 specifies that country codes shall be sent as upper case only
  List 91
  CountryOfPublication
  b083
  0…1
  `<b083>US</b083>`

##### Product contact composite

An optional group of data elements which together specify an organization (which may or may not be the publisher) responsible for dealing with enquiries related to the product. Repeatable in order to specify multiple responsible organizations.

  ProductContact
  productcontact
  0…n

##### P.19.15 Product contact role

An ONIX code which identifies the role played by the product contact in relation to the product – for example answering enquiries related to sales or to promotion.

  Fixed length, two digits
  List 198
  ProductContactRole
  x482
  1
  ``

##### Product contact identifier composite

A group of data elements which together define an identifier of the product contact. The composite is optional, and repeatable if more than one identifier of different types is sent; but either a <ProductContactName> or a <ProductContactIdentifier> must be included.

  ProductContactIdentifier
  productcontactidentifier
  0…n

##### P.19.16 Product contact identifier type

An ONIX code identifying a scheme from which an identifier in the <IDValue> element is taken. Mandatory in each occurrence of the <ProductContactIdentifier> composite, and non-repeating.

  Fixed length, two digits
  List 44
  ProductContactIDType
  x483
  1
  ``

##### P.19.17 Identifier type name

A name which identifies a proprietary identifier scheme (ie a scheme which is not a standard and for which there is no individual ID type code). Must be included when, and only when, the code in the <ProductContactIDType> element indicates a proprietary scheme. Optional and non-repeating.

  Variable length text, suggested maximum 100 characters
  IDTypeName
  b233
  0…1
  language
  ``

##### P.19.18 Identifier value

An identifier of the type specified in the <ProductContactIDType> element. Mandatory in each occurrence of the <ProductContactIdentifier> composite, and non-repeating.

  According to the identifier type specified in <ProductContactIDType>
  IDValue
  b244
  1
  ``

##### End of Product contact identifier composite

##### P.19.19 Product contact name

The name of the product contact organization, which should always be stated in a standard form. Optional and non-repeating; but either a <ProductContactName> element or a <ProductContactIdentifier> composite must be included.

  Variable length text, suggested maximum 50 characters
  ProductContactName
  x484
  0…1
  `<ProductContactName>Little Brown Book Group</ProductContactName>`

##### P.19.20 Contact name

Free text giving the name, department, etc for a contact person in the product contact organization who is responsible for the product. Optional and non-repeating.

  Variable length text, suggested maximum 300 characters
  ContactName
  x299
  0…1
  `<x299>Jackie Brown</x299>`

##### P.19.20a Product contact telephone number

A telephone number of the contact person in the product contact organization who is responsible for the product, wherever possible including the plus sign and the international dialing code. Optional, and repeatable to provide multiple numbers for the same contact.

  Variable length text, suggested maximum length 20 characters
  TelephoneNumber
  j270
  0…n
  `<TelephoneNumber>+44 20 7946 0921</TelephoneNumber>`

##### P.19.20b Product contact fax number

A fax number for the contact person in the product contact organization who is responsible for the product, wherever possible including the plus sign and the international dialing code. Optional, and repeatable to provide multiple numbers for the same contact.

  Variable length text, suggested maximum length 20 characters
  FaxNumber
  j271
  0…n
  `<FaxNumber>+44 20 7946 0921</FaxNumber>`

##### P.19.21 Product contact e‑mail address

A text field giving the e‑mail address for a contact person in the product contact organization who is responsible for the product. Optional, and repeatable to provide multiple e‑mail addresses for the same contact.

  Variable length text, suggested maximum 100 characters
  EmailAddress
  j272
  0…n
  `<j272>jackie.brown@bigpublisher.co.uk</j272>`

##### P.19.22 Product contact street address

A text field giving a street address and forming the first part of the postal address of the product contact organization. Optional and non-repeatable. Care should be taken that the Product contact name (plus optionally the Contact name), Street address, Location name, any Postal code or Region code, and the Country code can be combined into a complete postal address, without repetition.

  Variable length text, suggested maximum 100 characters
  StreetAddress
  x552
  0…1
  `<x552>Via Mondadori 1</x552>`

##### P.19.23 Product contact location name

The name of a city or town location, forming part of the postal address of the product contact organization. Mandatory and non-repeatable if a Street address is present, but otherwise omitted.

  Variable length text, suggested maximum 50 characters
  LocationName
  j349
  0…1
  `<j349>Sagrate</j349>`

##### P.19.24 Product contact postal code

The postal code (postcode, zip code etc), forming part of the postal address of the product contact organization. Optional and non-repeatable if a Street address is present, but otherwise omitted.

  Variable length text, suggested maximum 20 characters
  PostalCode
  x590
  0…1
  `<x590>MI 20090</x590>`

##### P.19.25 Product contact region code

An ONIX code identifying the region within which the product contact organization is located. Optional and non-repeatable if a Street address is present, but otherwise omitted.

For some addresses, a Region code is useful in addition to the Postal code and Country code. In other addresses, a region is unnecessary because it is clearly encoded within the Postal code.

  Variable length code, consisting of upper case letters, with or without a hyphen and further upper case letters or digits. Suggested maximum length 8 characters
  List 49 Where possible and appropriate, country subdivision codes are derived from the UN LOCODE scheme based on ISO 3166-2
  RegionCode
  b398
  0…1
  `<RegionCode>GB-SCT</RegionCode>` (Scotland)

##### P.19.26 Product contact country code

An ONIX code identifying the country within which the product contact organization is located. Mandatory and non-repeatable if a Street address is present, but otherwise omitted.

  Fixed length, two letters, based on ISO 3166-1. Note that ISO 3166-1 specifies that country codes shall be sent as upper case only
  List 91
  CountryCode
  b251
  0…1
  `<CountryCode>IT</CountryCode>` (Italy)

##### End of Product contact composite

#### P.20 Global publishing status and dates / copyright

Group P.20 covers elements that specify a publishing status and any publishing dates which apply ‘globally’ to a product, ie which are not specific to a geographical market. An important difference between ONIX 3.0 and 3.1, and all earlier releases is that it is no longer mandatory (thought it is still recommended as good practice) to specify a ‘global’ status and publication date, provided that a <ProductSupply> block carries this information in respect of each territorial market in which a product is distributed. It is expected that for those markets that are essentially international, eg the English-speaking countries, ONIX senders will prefer to provide publishing status and dates at market level in P.25 and also provide a global status and publication date in P.20. However, for those markets that are essentially national, ONIX feeds can continue to use Group P.20 (alone).

For all markets, any copyright statement attached to a product should continue to be carried in P.20, if it is required in the ONIX record.

##### P.20.1 Publishing status

An ONIX code which identifies the status of a published product. Optional and non-repeating, but required if publishing status is not identified at market level in <MarketPublishingDetail> (P.25).

Where the element is sent by a sender who is not the publisher, based on information that has been previously supplied by the publisher, it is strongly recommended that it should carry a datestamp attribute to indicate its likely reliability. See Section 1 for further details of the datestamp attribute.

  Fixed length, two digits
  List 64
  PublishingStatus
  b394
  0…1
  `<PublishingStatus>02</PublishingStatus>` (Forthcoming)

  Note the typical progression of publishing status, from announcement to out-of-print, through the life cycle of a product. The pale shaded area shows when the product is ‘orderable’ from the publisher or the publisher’s distributor, though if the product is ‘Forthcoming’ (and is later postponed indefinitely or cancelled) or the product ‘Out of stock indefinitely’, the order may not be fulfilled. Statuses ‘Withdrawn’, ‘Recalled’ are not shown on the diagram, but would normally be preceded by ‘Active’. Statuses ‘No longer our product’ and ‘Unknown’ are also not shown. In exceptional circumstances, products that are ‘Out of print’ are occasionally reactivated, returned to ‘Active’ status, via a reprint or print-on-demand decision, and a ‘Cancelled’ product may be reviewed and the title re-announced:

  This element and the equivalent <MarketPublishingStatus> in P.25 are frequently confused with <ProductAvailability> in P.26. The latter describes whether the product is available from a particular supplier (eg a distributor or wholesaler) – it is an attribute of the supply chain – whereas the publishing status of a product describes decisions made solely by the publisher or the publisher’s representative in a market. For example, a publisher may decide that a product is ‘out of print’ even while there are many copies available in the supply chain – the OP decision would be reflected in <PublishingStatus> while the continued availability of copies would be reflected in <ProductAvailability>.

##### P.20.2 Publishing status note

Free text that describes the status of a published product, when the code in <PublishingStatus> is insufficient. Optional, but when used, must be accompanied by the <PublishingStatus> element. Repeatable if parallel notes are provide in multiple languages. The language attribute is optional for a single instance of <PublishingStatusNote>, but must be included in each instance if <PublishingStatusNote> is repeated.

  Variable length text, suggested maximum 300 characters. XHTML is enabled in this element – see Using XHTML, HTML, XML, JSON within ONIX text fields
  PublishingStatusNote
  b395
  0…n
  language, textformat
  `<b395>Lost contact with publisher</b395>`

##### Publishing date composite

A group of data elements which together specify a date associated with the publishing of the product. Optional, but where known, at least a date of publication must be specified either here (as a ‘global’ pub date) or in <MarketPublishingDetail> (P.25). Other dates related to the publishing of a product can be sent in further repeats of the composite.

  PublishingDate
  publishingdate
  0…n

##### P.20.3 Publishing date role code

An ONIX code indicating the significance of the date, eg publication date, announcement date, latest reprint date. Mandatory in each occurrence of the <PublishingDate> composite, and non-repeating.

  Fixed length, two digits
  List 163
  PublishingDateRole
  x448
  1
  `<x448>01</x448>` (Publication date)
  A date such as a publication date here should be interpreted as the ‘global’ publication date. There may be market-specific ‘publication dates’ in Group P.25 which are later than the ‘global’ date.

##### P.20.5 Date

The date specified in the <PublishingDateRole> field. Mandatory in each occurrence of the <PublishingDate> composite, and non-repeating. <Date> may carry a dateformat attribute: if the attribute is missing, then the default format is YYYYMMDD.

  As specified by the value in the dateformat attribute, or the default YYYYMMDD
  Date
  b306
  1
  dateformat
  `<Date dateformat="01">199206</Date>` (June 1992)

##### End of Publishing date composite

  public announcement date and date work was first published
  using Reference names |
  --- | ---
  `<PublishingDate>` |
  `<PublishingDateRole>09</PublishingDateRole>` | Public announcement date
  `<Date dateformat="00">20101206</Date>` | Dateformat=YYYYMMDD
  `</PublishingDate>` |
  `<PublishingDate>` |
  `<PublishingDateRole>11</PublishingDateRole>` | Year first published
  `<Date dateformat="05">1972</Date>` | Dateformat=YYYY
  `</PublishingDate>` |

  using Short tags |
  --- | ---
  `<publishingdate>` |
  `<x448>09</x448>` |
  `<b306 dateformat="00">20101206</b306>` |
  `</publishingdate>` |
  `<publishingdate>` |
  `<x448>11</x448>` |
  `<b306 dateformat="05">1972</b306>` |
  `</publishingdate>` |

##### P.20.6 Latest reprint number

The number of the most recent reprint (or current ‘impression number’) of the product. Optional and non-repeating. This element is used only in certain countries where there is a legal requirement to record reprints.

  Positive integer, suggested maximum four digits
  LatestReprintNumber
  x446
  0…1
  `<LatestReprintNumber>12</LatestReprintNumber>`

##### Copyright statement composite

An optional and repeatable group of data elements which together represent a summary copyright or neighboring right statement for the product. At least one <CopyrightYear> or one instance of the <CopyrightOwner> composite must be sent within an instance of the composite, but it is recommended that all elements in the composite are explicitly populated. The Copyright statement may be repeated to provide a full structured rights statement listing year(s) and rights holder(s).

  CopyrightStatement
  copyrightstatement
  0…n

##### P.20.6a Copyright statement type

An optional ONIX code indicating the type of right covered by the statement, typically a copyright or neighboring right. If omitted, the default is that the statement represents a copyright.

  Fixed length, one letter
  List 219
  CopyrightType
  x512
  0…1
  `<CopyrightType>P</CopyrightType>` (℗ phonogram right)

##### P.20.7 Copyright year

The copyright year as it appears in a copyright statement on the product. Optional in each occurrence of the <CopyrightStatement> composite but may be omitted only if <CopyrightOwner> is present, and repeatable if several years or periods are listed.

  As specified by the value in the dateformat attribute, or the default of YYYY if the attribute is missing)
  CopyrightYear
  b087
  0…n
  dateformat
  `<b087 dateformat="11">20032008</b087>` (2003–2008)

##### Copyright owner composite

A repeatable group of data elements which together name a copyright owner. Optional, but may be omitted only if <CopyrightYear> is present. Each occurrence of the <CopyrightOwner> composite must carry a single name (personal or corporate), or an identifier, or both.

  CopyrightOwner
  copyrightowner
  0…n

##### Copyright owner identifier composite

A group of data elements which together represent a coded identification of a copyright owner. Optional, and repeatable if sending more than one identifier of different types. May be sent either instead of or as well as a name.

  CopyrightOwnerIdentifier
  copyrightowneridentifier
  0…n

##### P.20.8 Copyright owner identifier type

An ONIX code which identifies the scheme from which the value in the <IDValue> element is taken. Mandatory in each occurrence of the <CopyrightOwnerIdentifier> composite, and non-repeating.

  Fixed length, two digits
  List 44
  CopyrightOwnerIDType
  b392
  1
  `<CopyrightOwnerIDType>18</CopyrightOwnerIDType>` (LCCN)

##### P.20.9 Identifier type name

A name which identifies a proprietary identifier scheme (ie a scheme which is not a standard and for which there is no individual ID type code). Must be included when, and only when, the code in the <CopyrightOwnerIDType> element indicates a proprietary scheme. Optional and non-repeating.

  Variable length text, suggested maximum length 100 characters
  IDTypeName
  b233
  0…1
  language

##### P.20.10 Identifier value

A code value taken from the scheme specified in the <CopyrightOwnerIDType> element. Mandatory in each occurrence of the <CopyrightOwnerIdentifier> composite, and non-repeating.

  Determined by the scheme specified in <CopyrightOwnerIDType>
  IDValue
  b244
  1
  `<IDValue>0000000121475396</IDValue>`

##### End of Copyright owner identifier composite

##### P.20.11 Person name

The name of a person, used here for a personal copyright owner. Optional and non-repeating. Each occurrence of the <CopyrightOwner> composite may carry a single name (personal or corporate), or an identifier, or both a name and an identifier.

  Variable length text, suggested maximum length 100 characters
  PersonName
  b036
  0…1
  collationkey, language, textscript
  `<PersonName>James J. Johnson III</PersonName>`

##### P.20.12 Corporate name

The name of a corporate body, used here for a corporate copyright owner. Optional and non- repeating. Each occurrence of the <CopyrightOwner> composite may carry a single name (personal or corporate), or an identifier, or both a name and an identifier.

  Variable length text, suggested maximum length 200 characters
  CorporateName
  b047
  0…1
  collationkey, language, textscript
  `<CorporateName>Johnson &amp; Johnson Inc</CorporateName>` (note this is represented as ‘Johnson &amp; Johnson Inc’, since & is a reserved character in XML)

##### End of Copyright owner composite

##### End of Copyright statement composite

##### P.20.12a Copyright statement text

Free text showing how the copyright should be described, when a standard concatenation of individual copyright statements would not give a satisfactory presentation. Optional but must only be used if one or more instances of <CopyrightStatement> are present, and repeatable if parallel text is provided in multiple languages. The language attribute is optional for a single instance of <CopyrightStatementText>, but must be included in each instance if <CopyrightStatementText> is repeated. When the <CopyrightStatementText> field is sent, the receiver should use it to replace all detail sent in the <CopyrightStatement> composite for display purposes only. It does not replace the <CopyrightStatement> element. The individual name detail must also be sent in one or more <CopyrightStatement> composites for indexing and retrieval purposes.

  Variable length text, suggested maximum length 500 characters. XHTML is enabled in this element – see Using XHTML, HTML, XML, JSON within ONIX text fields
  CopyrightStatementText
  x588
  0…n
  language, textformat
  `<CopyrightStatementText textformat="05"><p>Text © 2023 Amelia Winstanley, music © and ℗ 2021 Three sisters</p></CopyrightStatementText>`

#### P.21 Territorial sales rights and other sales restrictions

Releases 3.0 and 3.1 allow sales rights to be specified for any geographical territory. Group P.21 details the rights that the publisher chooses to exercise in the product described by the ONIX record. These may be different from (narrower than) the publication rights owned by the publisher in the underlying work, and may be different from (broader than) the distribution rights held by a particular supplier or group of suppliers in a market (see Group P.24). The P.21 sales rights should be a subset of (or the same as) the publication rights owned by the publisher, and the P.24 market should be a subset of (or the same as) the sales rights. Note that ONIX for Books says nothing directly about the publisher’s publication rights, except in so far as they are reflected in the sales rights.

The aim is to provide precise and reliable geographical rights information that can be used in a computer system to determine whether a product can or cannot be sold in a particular territory. There are no defaults. If no information is known about some range of territories, this should be stated explicitly using the <ROWSalesRightsType> data element.

The <SalesRights> composite allows rights to be specified as exclusive or non-exclusive or not-for-sale in any combination of countries or regions. It is also possible to specify rights as ‘worldwide’ or ‘worldwide with specified exclusions’ if this enables them to be stated more concisely.

The composite also allows details of an equivalent product to be sent in respect of a territory in which the product described in the ONIX record is not for sale. This information is particularly helpful in enabling international online booksellers to ensure that territorial rights are correctly identified and observed.

Underlying these sales rights are more specific rights, ultimately derived from the creator’s copyright. In particular, the sales rights indicate that the publisher holds – and is willing to pass on to its supply chain partners – the ‘right to distribute’ and the ‘right to make available’ (and for POD and digital products, also the ‘right of reproduction’). Without holding these necessary rights, the publisher cannot legitimately express these sales rights.

Special note on US and UK ‘Open Market’, and UK ‘Airport’ or ‘Airside’ editions. It is expected that such editions, like any others, should carry a full statement of the territories in which they are available for sale. If it is desired, as a matter of convenience, to refer to them as ‘Open Market’ or ‘Airside’, this should be additional to, not instead of, a full territorial rights statement, and should be handled through the <TradeCategory> element in Group P.3. Coding for ‘UK Airports’ and ‘UK Airside’ is included in the <Territory> composite, as these need to be distinguished as specific ‘territories’, but there should be no coding for ‘Open Market’ within this data element group.

Additional guidance on the description of sales rights in ONIX 3.0 and 3.1 will be found in a separate document ONIX for Books Product Information Message: How to Specify Markets and Suppliers in ONIX 3.

##### Sales rights composite

An optional and repeatable group of data elements which together identify territorial sales rights which a publisher chooses to exercise in a product. When specifying a territory in which the product is not for sale, the publisher and product ID for an edition which is available in the specified territory can optionally be included. (In releases prior to 3.0, this functionality was provided in a <NotForSale> composite, which is now redundant and has been deleted.) See examples at the end of the sales rights composite.

  SalesRights
  salesrights
  0…n

##### P.21.1 Sales rights type code

An ONIX code which identifies the type of sales right or exclusion which applies in the territories which are associated with it. Mandatory in each occurrence of the <SalesRights> composite, and non-repeating. Values include: for sale with exclusive rights, for sale with non-exclusive rights, not for sale.

  Fixed length, two digits
  List 46
  SalesRightsType
  b089
  1
  `<SalesRightsType>02</SalesRightsType>` (For sale with non-exclusive rights in the specified territory)

##### Territory composite

A group of data elements which together identify a territory in which the rights specified in <SalesRightsType> are applicable. Mandatory in each occurrence of the <SalesRights> composite, and non-repeating.

  Territory
  territory
  1

  Note the nesting of countries and sub-national regions within the <Territory> composite within the Euler diagram below. Do not exclude smaller geographical areas that have not been included as part of a larger geographical unit. The rights specified apply within the shaded area. Supra-national regions that are included may have both countries and regions excluded:

  The only supra-national region that may be used is WORLD. Country codes do not necessarily identify complete sovereign countries. Where a geographical unit has both a sub-national region code and a country code, use only the country code – for example, for Hong Kong, use HK from List 91, not CN-HK from List 49. And although Puerto Rico is a territory of the United States of America, because Puerto Rico has a country code of its own (PR in List 91), the US country code must be interpreted as not including Puerto Rico. In order to include all of the United States, multiple country codes including US, PR, AS, VI (and others) are required.

##### P.21.2 Countries included

One or more ONIX codes identifying countries included in the territory. Successive codes must be separated by spaces. Optional and non-repeating, but either <CountriesIncluded> or <RegionsIncluded> is mandatory in each occurrence of the <Territory> composite.

  One or more fixed-length codes based on ISO 3166-1, each consisting of two upper case letters, and with successive codes being separated by spaces. Suggested maximum length 750 characters. Note that ISO 3166-1 specifies that country codes shall be sent as upper case only
  List 91
  CountriesIncluded
  x449
  0…1
  `<CountriesIncluded>US CA</CountriesIncluded>` (USA and Canada)

##### P.21.3 Regions included

One or more ONIX codes identifying regions included in the territory. A region is an area which is not a country, but which is precisely defined in geographical terms, eg World, Northern Ireland, Australian Capital Territory. Successive codes must be separated by spaces. Optional and non-repeating, but either <CountriesIncluded> or <RegionsIncluded> is mandatory in each occurrence of the <Territory> composite.

Note that if used, the ‘WORLD’ region code cannot be combined with other region codes.

  One or more variable-length codes, each consisting of upper case letters, with or without a hyphen and further upper case letters or digits, and with successive codes being separated by spaces. Suggested maximum length 750 characters
  List 49 Where possible and appropriate, country subdivision codes are derived from the UN LOCODE scheme based on ISO 3166-2
  RegionsIncluded
  x450
  0…1
  `<x450>WORLD</x450>` (Whole world)
  `<x450>GB-ENG GB-SCT GB-WLS</x450>` (UK excluding Northern Ireland and islands)

##### P.21.4 Countries excluded

One or more ONIX codes identifying countries excluded from the territory. Successive codes must be separated by spaces. Optional and non-repeating, and can only occur if the <RegionsIncluded> element is also present and includes a supra-national region code (such as ‘WORLD’).

  One or more fixed-length codes based on ISO 3166-1, each consisting of two upper case letters, and with successive codes being separated by spaces. Suggested maximum length 750 characters. Note that ISO 3166-1 specifies that country codes shall be sent as upper case only
  List 91
  CountriesExcluded
  x451
  0…1
  `<CountriesExcluded>US CA</CountriesExcluded>` (Excludes USA and Canada)

##### P.21.5 Regions excluded

One or more ONIX codes identifying regions excluded from the territory. Successive codes must be separated by spaces. Optional and non-repeating, and can only occur if the <CountriesIncluded> element is also present (and specifies countries of which the excluded regions are a part), or if <RegionsIncluded> is present and includes a supra-national region code (such as ‘WORLD’).

  One or more variable-length codes, each consisting of upper case letters, with or without a hyphen and further upper case letters or digits, and with successive codes being separated by spaces. Suggested maximum length 750 characters
  List 49 Where possible and appropriate, country subdivision codes are derived from the UN LOCODE scheme based on ISO 3166-2
  RegionsExcluded
  x452
  0…1
  `<x452>GB-NIR</x452>` (Excludes Northern Ireland)

##### End of Territory composite

##### Sales restriction composite

A group of data elements which together identify a non-territorial sales restriction which a publisher applies to a product within a particular territory. Optional, and repeatable if more than a single restriction applies.

  SalesRestriction
  salesrestriction
  0…n

##### P.21.5a Sales restriction type code

An ONIX code which identifies a non-territorial sales restriction. Mandatory in each occurrence of the <SalesRestriction> composite, and non-repeating.

  Fixed length, two digits
  List 71
  SalesRestrictionType
  b381
  1
  `<b381>04</b381>` (Retailer exclusive)

##### Sales outlet composite

An optional group of data elements which together identify a sales outlet to which a restriction is linked. Each occurrence of the composite must include a <SalesOutletIdentifier> composite or a <SalesOutletName> or both. Repeatable in order to identify multiple sales outlets subject to the restriction.

  SalesOutlet
  salesoutlet
  0…n

##### Sales outlet identifier composite

An optional group of data elements which together represent a coded identification of an organization, used here to identify a sales outlet. Repeatable in order to specify multiple identifiers for the same sales outlet.

  SalesOutletIdentifier
  salesoutletidentifier
  0…n

##### P.21.5b Sales outlet identifier type

An ONIX code which identifies the scheme from which the value in the <IDValue> element is taken. Mandatory in each occurrence of the <SalesOutletIdentifier> composite, and non-repeating.

  Fixed length, two digits
  List 102
  SalesOutletIDType
  b393
  1
  `<b393>03</b393>` (ONIX sales outlet ID code)

##### P.21.5c Identifier type name

A name which identifies a proprietary identifier scheme (ie a scheme which is not a standard and for which there is no individual ID type code). Must be included when, and only when, the code in the <SalesOutletIDType> element indicates a proprietary scheme. Optional and non-repeating.

  Variable length text, suggested maximum length 100 characters
  IDTypeName
  b233
  0…1
  language

##### P.21.5d Identifier value

A code value taken from the scheme specified in the <SalesOutletIDType> element. Mandatory in each occurrence of the <SalesOutletIdentifier> composite, and non-repeating.

  Determined by the scheme specified in <SalesOutletIDType>
  IDValue
  b244
  1
  `<b244>GOS</b244>` (Blinkbox)

##### End of Sales outlet identifier composite

##### P.21.5e Sales outlet name

The name of a wholesale or retail sales outlet to which a sales restriction is linked. Non-repeating.

  Variable length text, suggested maximum length 200 characters
  SalesOutletName
  b382
  0…1
  language
  `<SalesOutletName>Marks &amp; Spencer</SalesOutletName>` (note ‘&’ is a reserved character in XML)

##### End of Sales outlet composite

##### P.21.5f Sales restriction note

A free text field describing an ‘unspecified’ restriction, or giving more explanation of a coded restriction type. Optional, and repeatable if parallel text is provided in multiple languages. The language attribute is optional for a single instance of <SalesRestrictionNote>, but must be included in each instance if <SalesRestrictionNote> is repeated.

  Variable length text, suggested maximum length 300 characters. XHTML is enabled in this element – see Using XHTML, HTML, XML, JSON within ONIX text fields
  SalesRestrictionNote
  x453
  0…n
  language, textformat

##### P.21.5g Start date

The date from which a sales restriction is effective. Optional and non-repeating.

  As specified by the value in the dateformat attribute, or the default of YYYYMMDD if the attribute is missing
  StartDate
  b324
  0…1
  dateformat
  `<StartDate>20090327</StartDate>`

##### P.21.5h End date

The date until which a sales restriction is effective. Optional and non-repeating.

  As specified by the value in the dateformat attribute, or the default of YYYYMMDD if the attribute is missing
  EndDate
  b325
  0…1
  dateformat
  `<b325 dateformat="00">20090930</b325>`

##### End of Sales restriction composite

  temporary retailer-exclusive sales restriction
  using Reference names |
  --- | ---
  `<SalesRights>` |
  `<SalesRightsType>01</SalesRightsType>` |
  `<Territory>` |
  `<CountriesIncluded>AS GU MH MP PH PR UM US VI​</CountriesIncluded>` |
  `</Territory>` |
  `<SalesRestriction>` |
  `<SalesRestrictionType>04</SalesRestrictionType>` |
  `<SalesOutlet>` |
  `<SalesOutletIdentifier>` |
  `<SalesOutletIDType>03</SalesOutletIDType>` |
  `<IDValue>BKM</IDValue>` |
  `</SalesOutletIdentifier>` |
  `</SalesOutlet>` |
  `<SalesRestrictionNote>For sale only through Books-a-Million until October 2011</SalesRestrictionNote>` |
  `<EndDate dateformat="00">20110930</EndDate>` |
  `</SalesRestriction>` |
  `</SalesRights>` |
  `<ROWSalesRightsType>06</ROWSalesRightsType>` |

  using Short tags |
  --- | ---
  `<salesrights>` |
  `<b089>01</b089>` | For sale, exclusive
  `<territory>` |
  `<x449>AS GU MH MP PH PR UM US VI​</x449>` | ‘US market’
  `</territory>` |
  `<salesrestriction>` |
  `<b381>04</b381>` | But exclusive to retailer
  `<salesoutlet>` |
  `<salesoutletidentifier>` |
  `<b393>03</b393>` | ONIX outlet ID code
  `<b244>BKM</b244>` | Books-a-Million
  `</salesoutletidentifier>` |
  `</salesoutlet>` |
  `<x453>For sale only through Books-a-Million until October 2011</x453>` |
  `<b325 dateformat="00">20110930</b325>` | Restriction ends. After expiry, book will be for sale throughout stated salesrights territory
  `</salesrestriction>` |
  `</salesrights>` |
  `<x456>06</x456>` | NFS in ROW (publisher lacks rights)

##### Equivalent product identifier composite

An optional group of data elements which together define the identifier of a product in accordance with a specified scheme. Used here only if <SalesRightsType> has a value indicating ‘not for sale’, in order to specify an equivalent product which is available to be sold in the territory in question. Repeatable with different identifiers for the same product.

  ProductIdentifier
  productidentifier
  0…n

##### P.21.6 Product identifier type code

An ONIX code identifying the scheme from which the identifier in the <IDValue> element is taken. Mandatory in each occurrence of the <ProductIdentifier> composite, and non-repeating.

  Fixed length, two digits
  List 5
  ProductIDType
  b221
  1
  `<ProductIDType>03</ProductIDType>` (GTIN-13)

##### P.21.7 Identifier type name

A name which identifies a proprietary identifier scheme (ie a scheme which is not a standard and for which there is no individual ID type code). Must be included when, and only when, the code in the <ProductIDType> element indicates a proprietary scheme, eg a wholesaler’s own code. Optional and non-repeating.

  Variable length text, suggested maximum length 100 characters
  IDTypeName
  b233
  0…1
  language
  `<IDTypeName>KNO</IDTypeName>`

##### P.21.8 Identifier value

An identifier of the type specified in the <ProductIDType> element. Mandatory in each occurrence of the <ProductIdentifier> composite, and non-repeating.

  According to the identifier type specified in <ProductIDType>
  IDValue
  b244
  1
  `<b244>9780330413206</b244>`

##### End of Equivalent product identifier composite

##### P.21.9 Publisher name

The name of the publisher of an equivalent product which is available in the territory specified in the <SalesRights> composite, used only when <SalesRightsType> has a value indicating ‘not for sale’. Optional, and repeatable if the name is sent in multiple languages. The language attribute is optional for a single instance of <PublisherName>, but must be included in each instance if <PublisherName> is repeated.. Except where they are essential to the recognized form of the name, it is recommended that suffixes denoting incorporation (‘Co’, ‘Inc’, ‘Ltd’, ‘SA’, ‘GmbH’ etc) should be omitted.

  Variable length text, suggested maximum length 100 characters
  PublisherName
  b081
  0…n
  language, collationkey
  `<b081>Reed International Books</b081>`

##### End of Sales rights composite

##### P.21.10 Rest of World sales rights type code

An ONIX code describing the sales rights applicable in territories not specifically associated with a sales right within an occurrence of the <SalesRights> composite. Must be preceded by at least one <SalesRights> composite. Optional, but required in all cases where no sales rights type is associated with the region ‘WORLD’, and in all cases where a sales rights type is associated with ‘WORLD’ but with exclusions that are not themselves associated with a sales rights type. Not repeatable. Note the value ‘00’ should be used to indicate where sales rights are genuinely unknown, or are unstated for any reason – in this case, data recipients must not assume anything about the rights that are applicable.

  Fixed length, two digits
  List 46
  ROWSalesRightsType
  x456
  0…1
  `<x456>00</x456>` (Unknown or unstated)

The extended example below illustrates the use of <SalesRights> and <ROWSalesRightsType>.

  exclusive rights in UK, Ireland, Australia, New Zealand, South Africa; not for sale in USA or Canada; non-exclusive rights in rest of world. The ISBN of the edition available in USA and Canada is shown
  using Reference names |
  --- | ---
  `<SalesRights>` |
  `<SalesRightsType>01</SalesRightsType>` |
  `<Territory>` |
  `<CountriesIncluded>GB IE AU NZ ZA</CountriesIncluded>` |
  `</Territory>` |
  `</SalesRights>` |
  `<SalesRights>` |
  `<SalesRightsType>03</SalesRightsType>` |
  `<Territory>` |
  `<CountriesIncluded>US CA</CountriesIncluded>` |
  `</Territory>` |
  `<ProductIdentifier>` |
  `<ProductIDType>03</ProductIDType>` |
  `<IDValue>9780123456784</IDValue>` |
  `</ProductIdentifier>` |
  `</SalesRights>` |
  `<ROWSalesRightsType>02</ROWSalesRightsType>` |

  using Short tags |
  --- | ---
  `<salesrights>` |
  `<b089>01</b089>` | For sale (exclusive rights)
  `<territory>` |
  `<x449>GB IE AU NZ ZA</x449>` |
  `</territory>` |
  `</salesrights>` |
  `<salesrights>` |
  `<b089>03</b089>` | Not for sale
  `<territory>` |
  `<x449>US CA</x449>` |
  `</territory>` |
  `<productidentifier>` |
  `<b221>03</b221>` | alternative US/Canada GTIN-13
  `<b244>9780123456784</b244>` |
  `</productidentifier>` |
  `</salesrights>` |
  `<x456>02</x456>` | For sale (non-exclusive) in ROW

  worldwide exclusive rights
  using Reference names |
  --- | ---
  `<SalesRights>` |
  `<SalesRightsType>01</SalesRightsType>` |
  `<Territory>` |
  `<RegionsIncluded>WORLD</RegionsIncluded>` |
  `</Territory>` |
  `</SalesRights>` |

  using Short tags |
  --- | ---
  `<salesrights>` |
  `<b089>01</b089>` | For sale (exclusive rights)
  `<territory>` |
  `<x450>WORLD</x450>` |
  `</territory>` |
  `</salesrights>` |

  exclusive rights in contiguous 48 states of USA only, not for sale elsewhere
  using Reference names |
  --- | ---
  `<SalesRights>` |
  `<SalesRightsType>01</SalesRightsType>` |
  `<Territory>` |
  `<CountriesIncluded>US</CountriesIncluded>` |
  `<RegionsExcluded>US-AK US-HI</RegionsExcluded>` |
  `</Territory>` |
  `</SalesRights>` |
  `<ROWSalesRightsType>03</ROWSalesRightsType>` |

  using Short tags |
  --- | ---
  `<salesrights>` |
  `<b089>01</b089>` | For sale (exclusive rights)
  `<territory>` |
  `<x449>US</x449>` | USA (50 states + 1 district)
  `<x452>US-AK US-HI</x452>` | Excluding Alaska, Hawaii
  `</territory>` |
  `</salesrights>` |
  `<x456>03</x456>` | Not for sale in ROW

#### End of Publishing detail composite

### Block 5: Related material

#### Related material composite

The related material block covers data Groups P.22 and P.23, providing links to related works and related products. The block as a whole is optional and non-repeating.

None of the individual sections are mandatory within an occurrence of the block. However, in most circumstances, the block should contain at least one instance of <RelatedWork> or <RelatedProduct>. It may be empty only within a partial or ‘block update’ (Notification or update type 04, see P.1.2), when the intention is to remove all previously-supplied information about related works and products.

  RelatedMaterial
  relatedmaterial
  0…1

#### P.22 Related works

The <RelatedWork> composite in Group P.22 allows the relationship between a product and one or more works to be specified, normally by using a proprietary or proxy work identifier to identify the work in question. Note that the ISTC standard formerly used to identify some works has been withdrawn.

##### Related work composite

An optional group of data elements which together describe a work which has a specified relationship to the product described in the ONIX record. Repeatable in order to specify multiple works and their various relationships to the product.

  RelatedWork
  relatedwork
  0…n

##### P.22.1 Work relation code

An ONIX code which identifies the nature of the relationship between a product and a work. Mandatory in each occurrence of the <RelatedWork> composite, and non-repeating.

  Fixed length, two digits
  List 164
  WorkRelationCode
  x454
  1
  `<WorkRelationCode>01</WorkRelationCode>` (Manifestation of)

##### Work identifier composite

A group of data elements which together define an identifier of a work in accordance with a specified scheme. Mandatory in each occurrence of the <RelatedWork> composite, and repeatable if two or more identifiers for the same work are sent using different identifier schemes (eg proprietary ID and DOI).

  WorkIdentifier
  workidentifier
  1…n

##### P.22.2 Work identifier type code

An ONIX code identifying the scheme from which the identifier in the <IDValue> element is taken. Mandatory in each occurrence of the <WorkIdentifier> composite, and non-repeating.

  Fixed length, two digits
  List 16
  WorkIDType
  b201
  1
  `<WorkIDType>11</WorkIDType>` (ISTC – though note the ISTC standard has been withdrawn)

##### P.22.3 Identifier type name

A name which identifies a proprietary identifier scheme (ie a scheme which is not a standard and for which there is no individual ID type code). Must be included when, and only when, the code in the <WorkIDType> element indicates a proprietary scheme. Optional and non-repeating.

  Variable length text, suggested maximum length 100 characters
  IDTypeName
  b233
  0…1
  language

##### P.22.4 Identifier value

An identifier of the type specified in the <WorkIDType> element. Mandatory in each occurrence of the <WorkIdentifier> composite, and non-repeating.

  According to the identifier type specified in <WorkIDType>
  IDValue
  b244
  1
  `<IDValue>0A920080000000FC</IDValue>`

##### End of Work identifier composite

##### End of Related work composite

  this product is a manifestation of a particular work
  using Reference names |
  --- | ---
  `<RelatedWork>` |
  `<WorkRelationCode>01</WorkRelationCode>` |
  `<WorkIdentifier>` |
  `<WorkIDType>11</WorkIDType>` | ISTC, now withdrawn
  `<IDValue>A022009000001BE9</IDValue>` |
  `</WorkIdentifier>` |
  `</RelatedWork>` |

  using Short tags, using proprietary UUID and ISBN proxy as work identifiers, and with additional link to the ‘grandparent work’
  `<relatedwork>` |
  `<x454>01</x454>` | Is manifestation of
  `<workidentifier>` |
  `<b201>01</b201>` | Proprietary ID scheme
  `<b233>BigPublisher WorkID</b233>` | Name of proprietary ID scheme
  `<b244>035b5d64-ca35-11ed-afa1-0242ac120002</b244>` | UUID of this work, within this specific scheme
  `</workidentifier>` |
  `</relatedwork>` |
  `<relatedwork>` |
  `<x454>02</x454>` | Is manifestation of work derived from
  `<workidentifier>` |
  `<b201>15</b201>` | ISBN of first manifestation
  `<b244>9780001234567</b244>` | of grandparent work, acting as
  `</workidentifier>` | a proxy for a work identifier
  `</relatedwork>` |

#### P.23 Related products

The <RelatedProduct> composite in Group P.23 allows a relationship between one product and another to be specified, normally using an ISBN in GTIN-13 format to identify the related product. By general agreement among ONIX user groups, the composite has been substantially reduced in ONIX 3.0 and 3.1 so that it carries only a link to the related product, and little or (ideally) no other detail. This is on the principle that detail of the related product should be accessed through its own metadata, and not repeated in several different places.

##### Related product composite

An optional group of data elements which together describe a product which has a specified relationship to the product described in the ONIX record. The composite is repeatable in order to specify different products which each have a relationship to the product described.

  RelatedProduct
  relatedproduct
  0…n

##### P.23.1 Product relation code

An ONIX code which identifies the nature of the relationship between two products, eg ‘replaced-by’. Mandatory in each occurrence of the <RelatedProduct> composite, and repeatable where the related product has multiple types of relationship to the product described.

  Fixed length, two digits
  List 51
  ProductRelationCode
  x455
  1…n
  `<x455>06</x455>` (Alternative format)

##### Product identifier composite (related product)

A group of data elements which together define an identifier of a product in accordance with a specified scheme. Mandatory in each occurrence of the <RelatedProduct> composite. Repeatable only if two or more identifiers for the same product are sent using different identifier schemes.

  ProductIdentifier
  productidentifier
  1…n

##### P.23.2 Product identifier type code

An ONIX code identifying the scheme from which the identifier in the <IDValue> element is taken. Mandatory in each occurrence of the <ProductIdentifier> composite, and non-repeating.

  Fixed length, two digits
  List 5
  ProductIDType
  b221
  1
  `<ProductIDType>03</ProductIDType>` (GTIN-13)

##### P.23.3 Identifier type name

A name which identifies a proprietary identifier scheme (ie a scheme which is not a standard and for which there is no individual ID type code). Must be included when, and only when, the code in the <ProductIDType> element indicates a proprietary scheme, eg a wholesaler’s own code. Optional and non-repeating.

  Variable length text, suggested maximum length 100 characters
  IDTypeName
  b233
  0…1
  language
  `<b233>KNO</b233>`

##### P.23.4 Identifier value

An identifier of the type specified in the <ProductIDType> element. Mandatory in each occurrence of the <ProductIdentifier> composite, and non-repeating.

  According to the identifier type specified in <ProductIDType>
  IDValue
  b244
  1
  `<IDValue>9780300117264</IDValue>`

##### End of Product identifier composite (related product)

##### P.23.5 Related product form code

An ONIX code which indicates the primary form of a related product. Optional in an occurrence of <RelatedProduct>, and non-repeating. If supplied, should be identical to the <ProductForm> element supplied in the <DescriptiveDetail> block of the full ONIX record describing the related product itself.

Since this and the following element provide data about a related product, ONIX suppliers are cautioned of the risk of contradictory data in separate data feeds. This and the following element should not be supplied unless specifically requested by a particular recipient.

  Fixed length, two letters (or the digits 00)
  List 150
  ProductForm
  b012
  0…1
  `<ProductForm>BC</ProductForm>` (Paperback book)

##### P.23.6 Related product form detail

An ONIX code which provides added detail of the medium and/or format of a related product. Optional and repeatable.

  Fixed length, four characters: one letter followed by three digits
  List 175
  ProductFormDetail
  b333
  0…n
  `<b333>B206</b333>` (Pop-up book)

##### End of Related product composite

  linking an e-publication to the paperback it was based on
  using Reference names |
  --- | ---
  `<RelatedProduct>` |
  `<ProductRelationCode>13</ProductRelationCode>` |
  `<ProductRelationCode>06</ProductRelationCode>` |
  `<ProductIdentifier>` |
  `<ProductIDType>03</ProductIDType>` |
  `<IDValue>9780007120765</IDValue>` |
  `</ProductIdentifier>` |
  `<ProductForm>BC</ProductForm>` |
  `</RelatedProduct>` |

  using Short tags, also with link to alternative hardback format
  `<relatedproduct>` |
  `<x455>13</x455>` | E-publication based on
  `<x455>06</x455>` | Alternative format
  `<productidentifier>` |
  `<b221>03</b221>` | GTIN-13
  `<b244>9780007120765</b244>` | Paperback ISBN
  `</productidentifier>` |
  `<b012>BC</b012>` | (Do not use, unless required by recipient)
  `</relatedproduct>` |
  `<relatedproduct>` |
  `<x455>06</x455>` | Alternative format
  `<productidentifier>` |
  `<b221>03</b221>` |
  `<b244>9780007234387</b244>` | Hardback ISBN
  `</productidentifier>` |
  `</relatedproduct>` |

#### End of Related material composite

### Block 8: Production detail

#### Production detail composite

The Production detail block comprises the single data Group P.28. The block as a whole is non-repeating. It is optional within the <Product> record, and is used only when there is a requirement to communicate specification and file manifest detail relating to intermediary services within the supply chain, for example manufacturing on demand, e‑book conversion services or distribution of digital audio. It is not expected to be present in most ONIX messages – though recipients not requiring the data should be able to ignore the entire block if it is supplied.

When used, the block should normally contain at least one instance of <ProductionManifest>. It may be empty only within a partial or ‘block update’ (Notification or update type 04, see P.1.2), when the intention is to remove all previously-supplied manifest detail.

  ProductionDetail
  productiondetail
  0…1

#### P.28 Production manifest

The Production manifest composite provides specification and file manifest detail for a Product, or – where the Product contains multiple Product parts as listed in Group P.4 – for a single Product part. Optional in any occurrence of the <ProductionDetail> composite, but it may be omitted only within a partial or ‘block update’ (Notification type 04, see P.1.2) when the intention is to remove all previously supplied production detail. When used normally, the composite is repeatable to carry manifests for multiple Product parts.

Each manifest consists of:

- a <ProductIdentifier> to link the manifest to a specific Product part (this is required only where there are Product parts, and must be omitted when there are none);
- an optional cover manifest;
- a mandatory body manifest;
- optional and repeatable insert manifests;
- optional and repeatable manifests for supplements (this might include a small PDF ‘booklet’ supplied with a digital audio product, or an item of packaging);
  - supplements may themselves have cover, body and insert manifests.

All manifests, whether for cover, body or inserts, carry specification information for creation of the physical or digital product, and a list of the file resources required. Each file resource can carry details of the resource itself and the URL link from which it can be obtained by the intermediate service provider (with the correct credentials).

##### Production manifest composite

A group of data elements which together carry manifest details for a single Product or Product part.

  ProductionManifest
  productionmanifest
  0…n

##### Product identifier composite (product part)

A group of data elements which together specify a product identifier, used here to carry an identifier which must match a product identifier in an instance of the <ProductPart> composite within Group P.4. The composite is mandatory and repeatable when <ProductPart> is present within the Product record, but must be omitted if there are no product parts. Where multiple product identifiers are provided in any one occurrence of the <ProductionManifest> composite, they must all identify the same product part.

  ProductIdentifier
  productidentifier
  0…n

##### P.28.1 to P.28.3: elements in the Product identifier composite

Elements P.28.1 to P.28.3 in the <ProductIdentifier> composite are identical to P.4.2 to P.4.4 as specified in Group P.4.

##### End of Product identifier composite (product part)

##### Cover manifest composite

A group of data elements which together provide manifest details for the cover of a Product or Product part. These details include:

- technical specifications for the cover;
- details of the file resources required to create the cover.

Note that the high-level specifications such as the Product form or overall size are carried in Block 1 – the manifest specifications are more detailed in nature, and must be consistent with the high-level specifications.

Technical specifications in the manifest can be provided either as a pre-defined and named ‘bundle’ encompassing all the required technical details, and/or as a set of individually-specified details. Bundle names are inevitably proprietary. It is possible to provide two or more bundle names if, for example, a physical book is set up for on-demand manufacturing by multiple POD suppliers, and a supplier who does not pre-define bundles can use the individually-specified details.

The composite is optional – it may be omitted where the Product or Product part has no cover – and is not repeatable.

  CoverManifest
  covermanifest
  0…1

##### P.28.4 to P.28.10: elements in the Cover manifest composite

Elements P.28.4 to P.28.10 (<SpecificationBundleName> to <SpecificationDescription>) are identical to those specified in P.28.31 to P.28.37.

##### Cover resource composite

A group of data elements that together provide details of a single file or resource of which the cover is composed. At least one resource is required in each <CoverManifest>, and the <CoverResource> composite is repeatable to describe multiple resources.

The composite must contain either a Resource file link or a No resource indicator.

  CoverResource
  coverresource
  1…n

##### P.28.11 Sequence number

A number which (in combination with any <SalesOutlet> composite) specifies a single overall sequence of cover resources. Optional and non-repeating. It is strongly recommended that each occurrence of the <CoverResource> composite should carry a <SequenceNumber>.

Note that with <SalesOutlet> below, the provision of vendor-specific resources can require the use of duplicate sequence numbers.

  Positive integer, 1, 2, 3 etc, suggested maximum length 3 digits
  SequenceNumber
  b034
  0…1
  `<SequenceNumber>2</SequenceNumber>`

##### Sales outlet composite

A group of data elements which together identify a specific retail outlet. Optional in each occurrence of the <CoverResource> composite, and repeatable with multiple outlets.

Normally omitted, but for vendor-specific resources, the <SalesOutlet> composite lists an outlet for which the resource is relevant. The <SalesOutlet> composite may be repeated where a single resource is relevant for multiple outlets. Where <SalesOutlet> is omitted, the resource is appropriate for all – or all other – outlets, depending on the use of the resource’s Sequence number.

Manifest consisting of three resources: | Manifest consisting of two or three resources:
sequence number 1 – no sales outlet sequence number 2 – exclusive to Amazon sequence number 2 – no sales outlet (ie alternative resource for third parties other than Amazon) sequence number 3 – no sales outlet | sequence number 1 – no sales outlet sequence number 2 – exclusive to Amazon/Kobo sequence number 2 – exclusive to publisher’s direct sales sequence number 2 – no sales outlet and <NoResource/> (ie no alternative resource for third parties other than Amazon, Kobo and the publisher’s direct sales) sequence number 3 – no sales outlet

In the first example, the insert always consists of three resources. Resources #1 and #3 are used for all vendors, with the vendor-specific resource #2 for Amazon replacing resource #2 used for all other vendors. In the second example, the same vendor-specific resource #2 is used for Amazon and Kobo, a different #2 resource is used for the publisher’s own direct sales, whereas the cover for other vendors consists of only two resources (#1 and #3).

  SalesOutlet
  salesoutlet
  0…n

##### P.28.12 to P.28.15: elements in the Sales outlet composite

Elements P.28.12 to P.28.15 in the <SalesOutlet> composite are identical to P.21.5b to P21.5e as specified in Group P.21.

##### End of Sales outlet composite

##### Resource identifier composite

A group of data elements which together specify an identifier of the resource, in accordance with the specified scheme. The composite is optional, and repeatable to specify multiple identifiers for the resource, but may only be used when <ResourceFileLink> is present.

  ResourceIdentifier
  resourceidentifier
  0…n

##### P.28.16 Resource identifier type code

An ONIX code identifying the scheme from which the identifier in <IDValue> is taken. Mandatory in each occurrence of the <ResourceIdentifier> composite, and non-repeating.

  Fixed length, two digits
  List 250
  ResourceIDType
  x565
  1
  `<ResourceIDType>09</ResourceIDType>` (ISCC)

##### P.28.17 Identifier type name

A name which identifies a proprietary identifier scheme (ie a scheme which is not a standard and for which there is no individual ID type code). Must be included when, and only when, the code in <ResourceIDType> indicates a proprietary scheme, eg a publisher’s own identifier type. Optional and non-repeating.

  Variable length text, suggested maximum length 100 characters
  IDTypeName
  b233
  0…1
  language
  `<IDTypeName>Bloomsbury WDAM</IDTypeName>`

##### P.28.18 Identifier value

An identifier of the type specified in the <ResourceIDType> element. Mandatory in each occurrence of the <ResourceIdentifier> composite, and non-repeating.

  According to the identifier type specified in <ResourceIDType>
  IDValue
  b244
  1
  `<b244>CCgQtRrfyeorp-CTWPsEfB7epkk-CD3a6B6kovUpj-CRX4sSi2iC9U8</b244>` (ISCC)

##### End of Resource identifier composite

##### P.28.19 Resource role code

An ONIX code which identifies the role or purpose of the resource file which is specified in <ResourceFileLink>. Optional and non-repeating, and may only be used when <ResourceFileLink> is present.

  Fixed length, three characters: one letter followed by two digits
  List 251
  ResourceRole
  x566
  0…1
  `<ResourceRole>01</ResourceRole>`

##### P.28.20 Resource file detail

An ONIX code which provides added detail of the resource file which is specified in <ResourceFileLink>, eg the file type of the resource. Optional, and repeatable in order to provide multiple additional details, but may only be used when <ResourceFileLink> is present.

  Fixed length, four characters: one letter followed by three digits
  List 252
  ResourceFileDetail
  x567
  0…n
  `<ResourceFileDetail>A412</ResourceFileDetail>` (44.1kHz)

##### Resource file feature composite

An optional group of data elements which together describe an aspect of a resource file specified in <ResourceFileLink> that is too specific to be covered in the <ResourceFileDetail> element. It may only be used when <ResourceFileLink> is present, and is repeatable in order to describe different aspects of the resource file.

  ResourceFileFeature
  resourcefilefeature
  0…n

##### P.28.21 Resource file feature type

An ONIX code which specifies the feature of the resource file described by an instance of the <ResourceFileFeature> composite, eg a checksum or hash for the resource file. Mandatory in each occurrence of the composite, and non-repeating.

  Fixed length, two digits
  List 253
  ResourceFileFeatureType
  x568
  1
  `<x568>07</x568>` (exact download file size in bytes)

##### P.28.22 Resource file feature value

A controlled value that specifies a feature of the resource file. Presence or absence of this element depends on the <ResourceFileFeatureType>, since some feature types may not require an accompanying value, while others may require free text in <ResourceFileFeatureDescription> and some may have both code and free text. Non-repeating.

  Dependent on the scheme specified in <ResourceFileFeatureType>
  ResourceFileFeatureValue
  x569
  0…1
  `<ResourceFileFeatureValue>2134516</ResourceFileFeatureValue>` (bytes)

##### P.28.23 Resource file feature description

If the <ResourceFileFeatureType> requires free text rather than a code value, or if the code in <ResourceFileFeatureValue> does not adequately specify the feature of the insert, a short text description may be added. Optional, and repeatable to provide parallel descriptive text in multiple languages. The language attribute is optional for a single instance of <ResourceFileFeatureDescription>, but must be included in each instance if <ResourceFileFeatureDescription> is repeated.

  Variable length text, suggested maximum length 500 characters
  ResourceFileFeatureDescription
  x570
  0…n
  language
  ``

##### End of Resource file feature composite

##### P.28.24 Resource file description

If the Resource file details and features do not adequately describe the resource, a short text description may be added to give a more detailed description. The field is optional but may only be used when <ResourceFileLink> is present, and is repeatable to provide parallel specifications in multiple languages. The language attribute is optional for a single instance of <ResourceFileDescription>, but must be included in each instance if <ResourceFileDescription> is repeated to provide parallel descriptions in multiple languages.

  Variable length text, suggested maximum length 500 characters
  ResourceFileDescription
  x571
  0…n
  language
  `<ResourceFileDescription>96kHz sampling frequency, 16-bit sample depth, uncompressed</ResourceFileDescription>`

##### P.28.25 Resource file content description

The content contained in the resource may be described, for manual confirmation – for example ‘Foil block overlay’ or ‘CMYK separations of rear cover’.

Note that individual resources do not need to be aligned with the physical organization of the book (eg with the folded signatures of a print-on-demand product), nor with the logical organization (eg with the chapters in the work).

The field is optional but may only be used when <ResourceFileLink> is present, and is repeatable to provide parallel descriptions in multiple languages. The language attribute is optional for a single instance of <ResourceFileContentDescription>, but must be included in each instance if <ResourceFileContentDescription> is repeated to provide parallel descriptions in multiple languages.

  Variable length text, suggested maximum length 500 characters
  ResourceFileContentDescription
  x576
  0…n
  language
  `<ResourceFileContentDescription>Chapters 2 and 3</ResourceFileContentDescription>`

##### P.28.26 Resource file link

A URL which provides a link to a resource. Mandatory in each occurrence of the <CoverResource> composite unless <NoResource/> is present, and repeatable if the resource can be linked in more than one way, eg by HTTP, FTP and DOI URLs.

  Uniform Resource Locator, expressed in full URI syntax in accordance with W3C standards, suggested maximum length 300 characters. Note that non-ASCII characters, spaces and a handful of other special characters should be ‘URL-encoded’. Any ampersand used to separate parameters in the URL must be expressed as &amp;
  ResourceFileLink
  x572
  1…n
  `<x572>https://www.e-pblshr.com/9780001234567/plates%202.pdf</x572>` (file is named ‘plates 2.pdf’)

##### Resource file date composite

An optional group of data elements which together specify a date associated with the resource file specified in <ResourceFileLink>, eg date when the resource was last updated. Repeatable to specify different dates with their various roles, but may only be used when <ResourceFileLink> is present.

  ResourceFileDate
  resourcefiledate
  0…n

##### P.28.27 Resource file date role

An ONIX code indicating the significance of the date in relation to the resource file. Mandatory in each occurrence of the <ResourceFileDate> composite, and non-repeating.

  Fixed length, two digits
  List 254
  ResourceFileDateRole
  x573
  1
  `<ResourceFileDateRole>17</ResourceFileDateRole>` (last updated)

##### P.28.29 Date

The date specified in the <ResourceFileDateRole> field. Mandatory in each occurrence of the <ResourceFileDate> composite, and non-repeating. <Date> may carry a dateformat attribute: if the attribute is missing, then the default format is YYYYMMDD.

  As specified by the value in the dateformat attribute, or the default YYYYMMDD
  Date
  b306
  1
  dateformat
  `<Date dateformat="13">20200621T1545+0100</Date>` (3:45pm BST, June 21st)

##### End of Resource file date composite

##### P.28.30 “No resource” indicator

An empty element that provides a positive indication that there is no alternative ‘generic’ resource to be used in cases where there is a vendor-specific resource (indicated using <SalesOutlet>) with the same <SequenceNumber> specified within the manifest. The empty <NoResource/> must be used – and must only be used – when no <ResourceFileLink> is present.

  XML empty element
  NoResource/
  x577/
  0…1
  `<NoResource/>`

##### End of Cover resource composite

##### End of Cover manifest composite

##### Body manifest composite

A group of data elements which together provide manifest details for the body of a Product or Product part. These details include:

- technical specifications for the body;
- details of the file resources required to create the body.

Note that the high-level specifications such as the Product form and size are carried in Block 1 – the manifest specifications are more detailed in nature, and must be consistent with the high-level specifications.

Technical specifications in the manifest can be provided either as a pre-defined and named ‘bundle’ encompassing all the required technical details, and/or as a set of individually-specified details. Bundle names are inevitably proprietary. It is possible to provide two or more bundle names if, for example, a physical book is set up for on-demand manufacturing by multiple POD suppliers, and a supplier who does not pre-define bundles can use the individually-specified details.

The composite is mandatory and is not repeatable.

  BodyManifest
  bodymanifest
  1

##### Specification bundle name composite

A group of data elements that together identify a named ‘bundle’ of detailed technical specifications necessary for creation of the body of the final Product or Product part. Bundle names are inevitably proprietary, so both a Name type name and the Name value must be included.

  SpecificationBundleName
  specificationbundlename
  0…n

##### P.28.31 Bundle name type name

A name which identifies a particular proprietary naming scheme. Must be included to indicate the proprietary naming scheme from which the <SpecificationBundleNameValue> is taken. Mandatory and non-repeating.

  Variable length text, suggested maximum length 50 characters
  SpecificationBundleNameTypeName
  x558
  1
  language
  `<x558>Ingram POD ProdType</x558>`

##### P.28.32 Bundle name value

The proprietary name of a ‘bundle’ of technical specifications, taken from the naming scheme in <SpecificationBundleNameTypeName>.

  Variable length text matching the format for the name type specified in <SpecificationBundleNameTypeName>, suggested maximum length 50 characters
  SpecificationBundleNameValue
  x559
  1
  `<x559>Standard B16</x559>`

##### End of Specification bundle name composite

##### P.28.33 Specification detail code

An ONIX code which specifies added detail of the medium and/or format of the body of the Product or Product part. Optional, and repeatable in order to provide multiple additional details.

  Fixed length, four characters: one letter followed by three digits
  List 248
  SpecificationDetail
  x560
  0…n
  `<SpecificationDetail>B003</SpecificationDetail>` (Monochrome)

##### Specification feature composite

An optional group of data elements which together specify an aspect of the body of the Product or Product part that is too specific to be covered in the <SpecificationDetail> element. Repeatable in order to describe different aspects of the product form.

  SpecificationFeature
  specificationfeature
  0…n

##### P.28.34 Specification feature type code

An ONIX code which specifies the feature described by an instance of the <SpecificationFeature> composite, eg paper color for the body. Mandatory in each occurrence of the composite, and non-repeating.

  Fixed length, two digits
  List 249
  SpecificationFeatureType
  x561
  1
  `<SpecificationFeatureType>43</SpecificationFeatureType>` (Paper color)

##### P.28.35 Specification feature value

A controlled value that specifies a feature of the body of the product. Presence or absence of this element depends on the <SpecificationFeatureType>, since some feature types may not require an accompanying value, while others may require free text in <SpecificationFeatureDescription> and some may have both controlled value and free text. Non-repeating.

  Dependent on the scheme specified in <SpecificationFeatureType>
  SpecificationFeatureValue
  x562
  0…1
  `<SpecificationFeatureValue>CRE</SpecificationFeatureValue>` (Cream, from List 257)

##### P.28.36 Specification feature description

If the <SpecificationFeatureType> requires free text rather than a controlled value, or if the code in <SpecificationFeatureValue> does not adequately specify the feature of the body, a short text description may be added. Optional, and repeatable to provide parallel descriptive text in multiple languages. The language attribute is optional for a single instance of <SpecificationFeatureDescription>, but must be included in each instance if <SpecificationFeatureDescription> is repeated.

  Variable length text, suggested maximum length 500 characters
  SpecificationFeatureDescription
  x563
  0…n
  language
  `<x563>Tip-in card with perforation</x563>`

##### End of Specification feature composite

##### P.28.37 Specification description

If Specification details and features do not adequately specify the body of the product, a short text description may be added to give a more detailed specification. The field is optional, and repeatable to provide parallel specifications in multiple languages. The language attribute is optional for a single instance of <SpecificationDescription>, but must be included in each instance if <SpecificationDescription> is repeated to provide parallel descriptions in multiple languages.

  Variable length text, suggested maximum length 500 characters
  SpecificationDescription
  x564
  0…n
  language
  `<x564>With die-cut in outer bottom corner of leaves</x564>`

##### Body resource composite

A group of data elements that together provide details of a single file or resource of which the body is composed. At least one resource is required in each <BodyManifest>, and the <BodyResource> composite is repeatable to describe multiple resources.

  BodyResource
  bodyresource
  1…n

##### P.28.38 Sequence number

A number which specifies a single overall sequence of body resources. Optional and non-repeating. It is strongly recommended that each occurrence of the <BodyResource> composite should carry a <SequenceNumber>, and that primary resources are numbered in ‘spine order’. Ancillary resources (eg an image file referenced by a primary HTML file) should be numbered after the primary resources.

  Positive integer, 1, 2, 3 etc, suggested maximum length 3 digits
  SequenceNumber
  b034
  0…1
  `<SequenceNumber>2</SequenceNumber>`

##### Resource identifier composite

A group of data elements which together specify an identifier of the resource, in accordance with the specified scheme. The composite is optional, and repeatable to specify multiple identifiers for the resource.

  ResourceIdentifier
  resourceidentifier
  0…n

##### P.28.39 Resource identifier type code

An ONIX code identifying the scheme from which the identifier in <IDValue> is taken. Mandatory in each occurrence of the <ResourceIdentifier> composite, and non-repeating.

  Fixed length, two digits
  List 250
  ResourceIDType
  x565
  1
  `<ResourceIDType>09</ResourceIDType>` (ISCC)

##### P.28.40 Identifier type name

A name which identifies a proprietary identifier scheme (ie a scheme which is not a standard and for which there is no individual ID type code). Must be included when, and only when, the code in <ResourceIDType> indicates a proprietary scheme, eg a publisher’s own identifier. Optional and non-repeating.

  Variable length text, suggested maximum length 100 characters
  IDTypeName
  b233
  0…1
  language
  `<IDTypeName>Bloomsbury WDAM</IDTypeName>`

##### P.28.41 Identifier value

An identifier of the type specified in the <ResourceIDType> element. Mandatory in each occurrence of the <ResourceIdentifier> composite, and non-repeating.

  According to the identifier type specified in <ResourceIDType>
  IDValue
  b244
  1
  `<b244>CCgQtRrfyeorp-CTWPsEfB7epkk-CD3a6B6kovUpj-CRX4sSi2iC9U8</b244>` (ISCC)

##### End of Resource identifier composite

##### P.28.42 Resource role code

An ONIX code which identifies the role or purpose of the resource file which is specified in <ResourceFileLink>. Optional and non-repeating.

  Fixed length, three characters: one letter followed by two digits
  List 251
  ResourceRole
  x566
  0…1
  `<ResourceRole>01</ResourceRole>`

##### P.28.43 Resource file detail

An ONIX code which provides added detail of the resource file which is specified in <ResourceFileLink>, eg the file type of the resource. Optional, and repeatable in order to provide multiple additional details.

  Fixed length, four characters: one letter followed by three digits
  List 252
  ResourceFileDetail
  x567
  0…n
  `<ResourceFileDetail>B001</ResourceFileDetail>` (with crop marks)

##### Resource file feature composite

An optional group of data elements which together describe an aspect of a resource file specified in <ResourceFileLink> that is too specific to be covered in the <ResourceFileDetail> element. The composite is repeatable in order to describe different aspects of the resource file.

  ResourceFileFeature
  resourcefilefeature
  0…n

##### P.28.44 Resource file feature type

An ONIX code which specifies the feature of the resource file described by an instance of the <ResourceFileFeature> composite, eg a checksum or hash for the resource file. Mandatory in each occurrence of the composite, and non-repeating.

  Fixed length, two digits
  List 253
  ResourceFileFeatureType
  x568
  1
  `<x568>06</x568>` (MD5 hash value of resource file)

##### P.28.45 Resource file feature value

A controlled value that specifies a feature of the resource file. Presence or absence of this element depends on the <ResourceFileFeatureType>, since some feature types may not require an accompanying value, while others may require free text in <ResourceFileFeatureDescription> and some may have both code and free text. Non-repeating.

  Dependent on the scheme specified in <ResourceFileFeatureType>
  ResourceFileFeatureValue
  x569
  0…1
  `<ResourceFileFeatureValue>55986583052a9df850ec2e9f​4084b6a4</ResourceFileFeatureValue>` (MD5 hash)

##### P.28.46 Resource file feature description

If the <ResourceFileFeatureType> requires free text rather than a code value, or if the code in <ResourceFileFeatureValue> does not adequately specify the feature of the insert, a short text description may be added. Optional, and repeatable to provide parallel descriptive text in multiple languages. The language attribute is optional for a single instance of <ResourceFileFeatureDescription>, but must be included in each instance if <ResourceFileFeatureDescription> is repeated.

  Variable length text, suggested maximum length 500 characters
  ResourceFileFeatureDescription
  x570
  0…n
  language
  `<x570>96KHz 24-bit samples</x570>`

##### End of Resource file feature composite

##### P.28.47 Resource file description

If the Resource file details and features do not adequately describe the resource, a short text description may be added to give a more detailed description. The field is optional, and is repeatable to provide parallel specifications in multiple languages. The language attribute is optional for a single instance of <ResourceFileDescription>, but must be included in each instance if <ResourceFileDescription> is repeated to provide parallel descriptions in multiple languages.

  Variable length text, suggested maximum length 500 characters
  ResourceFileDescription
  x571
  0…n
  language
  `<ResourceFileDescription>Preseparated PDF, process black and spot blue</ResourceFileDescription>`

##### P.28.48 Resource file content description

The content contained in the resource may be described, for manual confirmation – for example ‘Chapters 2 and 3’ or ‘CMYK separations pages 16–31’.

Note that individual resources do not need to be aligned with the physical organization of the book (eg with the folded signatures of a print-on-demand product), nor with the logical organization (eg with the chapters in the work).

The field is optional, and is repeatable to provide parallel descriptions in multiple languages. The language attribute is optional for a single instance of <ResourceFileContentDescription>, but must be included in each instance if <ResourceFileContentDescription> is repeated to provide parallel descriptions in multiple languages.

  Variable length text, suggested maximum length 500 characters
  ResourceFileContentDescription
  x576
  0…n
  language
  `<ResourceFileContentDescription>Chapters 2 and 3</ResourceFileContentDescription>`

##### P.28.49 Resource file link

A URL which provides a link to a resource. Mandatory in each occurrence of the <BodyResource> composite, and repeatable if the resource can be linked in more than one way, eg by HTTP, FTP and DOI URLs.

  Uniform Resource Locator, expressed in full URI syntax in accordance with W3C standards, suggested maximum length 300 characters. Note that non-ASCII characters, spaces and a handful of other special characters should be ‘URL-encoded’. Any ampersand used to separate parameters in the URL must be expressed as &amp;
  ResourceFileLink
  x572
  1…n
  `<x572>https://www.e-pblshr.com/9780001234567/plates%202.pdf</x572>` (file is named ‘plates 2.pdf’)

##### Resource file date composite

An optional group of data elements which together specify a date associated with the resource file specified in <ResourceFileLink>, eg date when the resource was last updated. Repeatable to specify different dates with their various roles.

  ResourceFileDate
  resourcefiledate
  0…n

##### P.28.50 Resource file date role

An ONIX code indicating the significance of the date in relation to the resource file. Mandatory in each occurrence of the <ResourceFileDate> composite, and non-repeating.

  Fixed length, two digits
  List 254
  ResourceFileDateRole
  x573
  1
  `<ResourceFileDateRole>27</ResourceFileDateRole>` (Available from)

##### P.28.52 Date

The date specified in the <ResourceFileDateRole> field. Mandatory in each occurrence of the <ResourceFileDate> composite, and non-repeating. <Date> may carry a dateformat attribute: if the attribute is missing, then the default format is YYYYMMDD.

  As specified by the value in the dateformat attribute, or the default YYYYMMDD
  Date
  b306
  1
  dateformat
  `<Date dateformat="13">20200621T1545+0100</Date>` (3:45pm BST, June 21st)

##### End of Resource file date composite

##### End of Body resource composite

##### End of Body manifest composite

##### Insert manifest composite

A group of data elements which together provide manifest details for a single insert within the Product or Product part. These details include:

- technical specifications for the insert within the final product;
- details of the file resources required to create the insert;

Note that the high-level specifications such as the Product form, trimmed page size or file type for final delivery are carried in Block 1 – the manifest specifications are more detailed in nature, and must be consistent with the high-level specifications.

Technical specifications in the manifest can be provided either as a pre-defined and named ‘bundle’ encompassing all the required technical details, and/or as a set of individually-specified details. Bundle names are inevitably proprietary. It is possible to provide two or more bundle names if, for example, a physical book is set up for on-demand manufacturing by multiple POD suppliers, and a supplier who does not pre-define bundles can use the individually-specified details.

The composite is optional – it may be omitted where the Product or Product part has no inserts – and is repeatable to provide manifest details for multiple inserts.

  InsertManifest
  insertmanifest
  0…n

##### P.28.53 to P.28.59: elements in the Insert manifest composite

Elements P.28.53 to P.28.59, <SpecificationBundleName> to <SpecificationDescription>, are identical to those specified in P.28.4 to P.28.10.

##### Insertion point composite

A group of data elements which together specify where within the body of the product the insert must be positioned. For a physical product, this is normally specified as a page number – either a physical printed page number or a ‘logical’ page number which counts all pages in the book block irrespective of any printed page numbers. For physical numbers, an insert may be placed immediately following an even numbered page or preceding an odd numbered page.

  InsertPoint
  insertpoint
  1

##### P.28.60 Insertion point type

An ONIX code specifying the format in which the insertion point is included in <InsertPointValue>.

  Fixed length, three letters
  List 255
  InsertPointType
  x574
  1
  `<InsertPointType>ALP</InsertPointType>` (Adjacent to logical page)

##### P.28.61 Insertion point value

The point at which the insert must be positioned, in the format specified in <InsertPointType>.

  Dependent on the positioning specified in <InsertPointType>
  InsertPointValue
  x575
  1
  `<x575>49</x575>` (Before [logical or physical] page 49)

##### End of Insertion point composite

##### Insert resource composite

A group of data elements that together provide details of a single file or resource of which the insert is composed. At least one <InsertResource> composite is required in each <InsertManifest>, and the <InsertResource> composite is repeatable to describe multiple resources.

The composite must contain either a Resource file link or a No resource indicator.

  InsertResource
  insertresource
  1…n

##### P.28.62 Sequence number

A number which (in combination with any <SalesOutlet> composite) specifies a single overall sequence of insert resources. Optional and non-repeating. It is strongly recommended that each occurrence of the <InsertResource> composite should carry a <SequenceNumber>, and that primary resources are numbered in ‘spine order’ (within the insert). Ancillary resources (eg an image file referenced by a primary HTML file) should be numbered after the primary resources.

  Positive integer, 1, 2, 3 etc, suggested maximum length 3 digits
  SequenceNumber
  b034
  0…1
  `<b034>2</b034>`

##### P.28.63 to P.28.81: elements in the Insert resource composite

Elements P.28.63 to P.28.81, <SalesOutlet> to <NoResource/>, are identical to those specified in P.28.12 to P.28.30.

##### End of Insert resource composite

##### End of Insert manifest composite

##### Supplement manifest composite

An optional group of data elements detailing a simple subset of Group P.1 to specify the Product form, an optional cover, mandatory body and optionally one or more insert manifests for a single Supplement – an additional item supplied with the product at retail that is NOT considered a <ProductPart>, for example a booklet supplied in PDF form that accompanies a downloadable audio product. Each of these cover, body and insert sections within <SupplementManifest> mirrors the structure of the parts of a <ProductionManifest>.

These manifests may be preceded by a <SequenceNumber> and one or more <SalesOutlet> composites to enable vendor-specific supplements, and a simple <NoSupplement/> indicator may replace the Product form and cover, body and insert manifests to provide a positive indication that a vendor-specific supplement has no ‘generic’ alternative.

  SupplementManifest
  supplementmanifest
  0…n

##### P.28.82 Sequence number

A number which (in combination with any <SalesOutlet> composite) specifies a single overall sequence of supplements. Optional and non-repeating. It is strongly recommended that each occurrence of the <SupplementManifest> composite should carry a <SequenceNumber>.

Note that with <SalesOutlet> below the provision of vendor-specific supplements can require the use of duplicate sequence numbers.

  Positive integer, 1, 2, 3 etc, suggested maximum length 3 digits
  SequenceNumber
  b034
  0…1
  `<SequenceNumber>2</SequenceNumber>`

##### Sales outlet composite (supplement)

A group of data elements which together identify a specific sales outlet. Optional in each occurrence of the <SupplementManifest> composite, and repeatable with multiple outlets.

Normally omitted, but for vendor-specific supplements, the <SalesOutlet> composite lists an outlet for which the supplement is relevant. The <SalesOutlet> composite may be repeated where a single supplement is relevant for multiple outlets. Where <SalesOutlet> is omitted, the supplement is appropriate for all – or all other – outlets, depending on the use of the supplement’s Sequence number. See the use of <SequenceNumber> and <SalesOutlet> within the Cover resource composite.

  SalesOutlet
  salesoutlet
  0…n

##### P.28.83 to P.28.86: elements in the Sales outlet composite

Elements P.28.83 to P.28.86 in the <SalesOutlet> composite are identical to P.21.5b to P.21.5e as specified in Group P.21.

##### End of Sales outlet composite (supplement)

##### Product identifier composite (supplement)

A group of data elements which together specify a product identifier, used here to carry an identifier for the supplement which must not match a product identifier within Group P.2 or in an instance of the <ProductPart> composite within Group P.4. The composite is optional, but at least a proprietary identifier for the supplement is recommended.

  ProductIdentifier
  productidentifier
  0…n

##### P.28.87 to P.28.89: elements in the Product identifier composite

Elements P.28.87 to P.28.89 in the <ProductIdentifier> composite are identical to P.2.1 to P.2.3 as specified in Group P.2.

##### End of Product identifier composite (supplement)

##### P.28.90 Product form (supplement)

An ONIX code which indicates the primary form of a supplement. Mandatory in an occurrence of <SupplementManifest>, and non-repeating.

  Fixed length, two letters (or the digits 00)
  List 150
  ProductForm
  b012
  1
  `<ProductForm>ED</ProductForm>` (Digital download)

##### P.28.91 Product form detail (supplement)

An ONIX code which provides added detail of the medium and/or format of a supplement. Optional, and repeatable in order to provide multiple additional details.

  Fixed length, four characters: one letter followed by three digits
  List 175
  ProductFormDetail
  b333
  0…n
  `<ProductFormDetail>E101</ProductFormDetail>` (EPUB)

##### P.28.92 Product form description (supplement)

If product form codes do not adequately describe the supplement, a short text description may be added to give a more detailed specification of the product form. The field is optional, and repeatable to provide parallel descriptions in multiple languages. The language attribute is optional for a single instance of <ProductFormDescription>, but must be included in each instance if <ProductFormDescription> is repeated to provide parallel descriptions in multiple languages.

  Variable length text, suggested maximum length 200 characters
  ProductFormDescription
  b014
  0…n
  language
  `<b014>32pp e‑booklet in EPUB format</b014>`

##### Measure composite (supplement)

An optional group of data elements which together identify a measurement and the units in which it is expressed; used to specify the overall dimensions of a physical supplement. Repeatable to provide multiple combinations of dimension and unit.

  Measure
  measure
  0…n

##### P.28.93 to P.28.95: elements in the Measure composite

Elements P.28.93 to P.28.95 in the <Measure> composite are identical to P.3.12 to P.3.14 as specified in Group P.3.

##### End of Measure composite (supplement)

##### Cover manifest composite (supplement)

An optional group of data elements which together provide manifest details for the cover of a supplement. These details include:

- technical specifications of the cover of the supplement;
- details of the file resources required to create the cover.

The Cover manifest for the supplement has the same structure as the Cover manifest for a Product or Product Part. However, relevant high-level specifications such as the Product form or overall size of the supplement are carried within the <SupplementManifest> itself, rather than within Block 1.

  CoverManifest
  covermanifest
  0…1

##### P.28.96 to P.28.122: elements in the Cover manifest composite

P.28.96 to P.28.122 (<SpecificationBundleName> to <NoResource/>) are identical to P.28.4 to P.28.30.

##### End of Cover manifest composite (supplement)

##### Body manifest composite (supplement)

A group of data elements which together provide manifest details for the body of a supplement. These details include:

- technical specifications of the body of the supplement;
- details of the file resources required to create the body.

The Body manifest for the supplement has the same structure as the Body manifest for a Product or Product part. However, relevant high-level specifications such as the Product form or overall size of the supplement are carried within the <SupplementManifest> itself, rather than within Block 1.

  BodyManifest
  bodymanifest
  1

##### P.28.123 to P.28.144: elements in the Body manifest composite

P.28.123 to P.28.144 (<SpecificationBundleName> to <Date>) are identical to P.28.31 to P.28.52.

##### End of Body manifest composite (supplement)

##### Insert manifest composite (supplement)

An optional and repeatable group of data elements which together provide manifest details for any inserts in a supplement. These details include:

- technical specifications for an insert within the final supplement;
- details of the file resources required to create the insert.

The Insert manifest for the supplement has the same structure as the Insert manifest for a Product or Product Part. However, relevant high-level specifications such as the Product form or overall size of the supplement are carried within the <SupplementManifest> itself, rather than within Block 1.

  InsertManifest
  insertmanifest
  0…n

##### P.28.145 to P.28.173: elements in the Insert manifest composite

P.28.145 to P.28.173 (<SpecificationBundleName> to <NoResource/>) are identical to P.28.53 to P.28.81.

##### End of Insert manifest composite (supplement)

##### P.28.174 “No supplement” indicator

An empty element that provides a positive indication there is no alternative ‘generic’ supplement to be used in cases where there is a vendor-specific supplement (indicated using <SalesOutlet> with the same <SequenceNumber> specified within the Supplement manifest). The empty <NoSupplement/> must be used – and must only be used – when no <BodyManifest> is present within the Supplement manifest.

  XML empty element
  NoSupplement/
  x579/
  0…1
  `<NoSupplement/>`

##### End of Supplement manifest composite

##### End of Production manifest composite

#### End of Production detail composite

  simple Production manifest for POD product
  using Reference names |
  --- | ---
  `<ProductionDetail>` |
  `<ProductionManifest>` |
  `<CoverManifest>` |
  `<SpecificationBundleName>` |
  `<SpecificationBundleNameTypeName>LSI 2020</SpecificationBundleNameTypeName>` |
  `<SpecificationBundleNameValue>Standard PB Bleed</SpecificationBundleNameValue>` |
  `</SpecificationBundleName>` |
  `<SpecificationDetail>B004</SpecificationDetail>` |
  `<CoverResource>` |
  `<SequenceNumber>1</SequenceNumber>` |
  `<SalesOutlet>` |
  `<SalesOutletIdentifier>` |
  `<SalesOutletIDType>03</SalesOutletIDType>` |
  `<IDValue>BNO</IDValue>` |
  `</SalesOutletIdentifier>` |
  `</SalesOutlet>` |
  `<ResourceFileDescription>Special cover for B&N</ResourceFileDescription>` |
  `<ResourceFileLink>https://mypblishr.com/​productiongateway/​9780001234567/​cover_BandN.pdf</ResourceFileLink>` |
  `</CoverResource>` |
  `<CoverResource>` |
  `<SequenceNumber>1</SequenceNumber>` |
  `<ResourceFileDescription>Generic cover for all except B&amp;N</ResourceFileDescription>` |
  `<ResourceFileLink>https://mypblishr.com/​productiongateway/​9780001234567/​cover.pdf</ResourceFileLink>` |
  `</CoverResource>` |
  `</CoverManifest>` |
  `<BodyManifest>` |
  `<SpecificationBundleName>` |
  `<SpecificationBundleNameTypeName>LSI 2020</SpecificationBundleNameTypeName>` |
  `<SpecificationBundleNameValue>Standard PB NoBleed</SpecificationBundleNameValue>` |
  `</SpecificationBundleName>` |
  `<SpecificationDetail>B003</SpecificationDetail>` |
  `<SpecificationDetail>B001</SpecificationDetail>` |
  `<BodyResource>` |
  `<SequenceNumber>1</SequenceNumber>` |
  `<ResourceFileFeature>` |
  `<ResourceFileFeatureType>06</ResourceFileFeatureType>` |
  `<ResourceFileFeatureValue>3b452923564374ef​ebc5bfe1059f5fd2</ResourceFileFeatureValue>` |
  `</ResourceFileFeature>` |
  `<ResourceFileContentDescription>Title, prelims, chs 1–7</ResourceFileContentDescription>` |
  `<ResourceFileLink>https://mypblshr.com/​productiongateway/​9780001234567/​body_1.pdf</ResourceFileLink>` |
  `</BodyResource>` |
  `<BodyResource>` |
  `<SequenceNumber>2</SequenceNumber>` |
  `<ResourceFileFeature>` |
  `<ResourceFileFeatureType>06</ResourceFileFeatureType>` |
  `<ResourceFileFeatureValue>e6078dacd6d495f9​386acfdbf3e3d639</ResourceFileFeatureValue>` |
  `</ResourceFileFeature>` |
  `<ResourceFileContentDescription>chs 8–14, end matter</ResourceFileContentDescription>` |
  `<ResourceFileLink>https://mypblshr.com/​productiongateway/​9780001234567/​body_2.pdf</ResourceFileLink>` |
  `</BodyResource>` |
  `</BodyManifest>` |
  `<!-- no inserts -->` |
  `</ProductionManifest>` |
  `</ProductionDetail>` |

  using Short tags |
  --- | ---
  `<productiondetail>` |
  `<productionmanifest>` |
  `<covermanifest>` | Cover
  `<specificationbundlename>` | Standard LSI spec
  `<x558>LSI 2020</x558>` |
  `<x559>Standard PB Bleed</x559>` |
  `</specificationbundlename>` |
  `<x560>B004</x560>` | CMYK
  `<coverresource>` | Vendor-specific cover…
  `<b034>1</b034>` |
  `<salesoutlet>` | …for…
  `<salesoutletidentifier>` |
  `<b393>03</b393>` |
  `<b244>BNO</b244>` | …Barnes and Noble
  `</salesoutletidentifier>` |
  `</salesoutlet>` |
  `<x571>Special cover for B&N</x571>` |
  `<x572>https://mypblishr.com/​productiongateway/​9780001234567/​cover_BandN.pdf</x572>` | URL of vendor-specific cover resource
  `</coverresource>` |
  `<coverresource>` | Generic cover (for other vendors)…
  `<b034>1</b034>` | …with same seq number
  `<x571>Generic cover for all except B&amp;N</x571>` |
  `<x572>https://mypblishr.com/​productiongateway/​9780001234567/​cover.pdf</x572>` | URL of generic cover resource
  `</coverresource>` |
  `</covermanifest>` |
  `<bodymanifest>` | Body
  `<specificationbundlename>` | Standard LSI spec
  `<x558>LSI 2020</x558>` |
  `<x559>Standard PB NoBleed</x559>` |
  `</specificationbundlename>` |
  `<x560>B003</x560>` |
  `<x560>B001</x560>` |
  `<bodyresource>` | First half of book
  `<b034>1</b034>` |
  `<resourcefilefeature>` |
  `<x568>06</x568>` | MD5 hash
  `<x569>​3b452923564374ef​ebc5bfe1059f5fd2​</x569>` |
  `</resourcefilefeature>` |
  `<x576>Title, prelims, chs 1–7</x576>` |
  `<x572>https://​mypblishr.com/​productiongateway/​9780001234567/​body_1.pdf</x572>` | URL of body resource 1
  `</bodyresource>` |
  `<bodyresource>` | Second half of book
  `<b034>2</b034>` |
  `<resourcefilefeature>` |
  `<x568>06</x568>` | MD5 hash
  `<x569>​e6078dacd6d495f9​386acfdbf3e3d639​</x569>` |
  `</resourcefilefeature>` |
  `<x576>chs 8–14, end matter</x576>` |
  `<x572>https://​mypblishr.com/​productiongateway/​9780001234567/​body_2.pdf</x572>` | URL of body resource 2
  `</bodyresource>` |
  `</bodymanifest>` |
  `<!-- no inserts -->` |
  `</productionmanifest>` |
  `</productiondetail>` |

### Block 6: Product supply

#### Product supply composite

The product supply block covers data Groups P.24 to P.26, specifying a market, the publishing status and representation detail of the product in that market, and the supply arrangements for the product in that market. The <ProductSupply> composite is repeatable within the block to describe multiple markets. At least one occurrence is expected in a <Product> record unless the <NotificationType> in Group P.1 indicates that the record is a partial update notice which carries only those blocks in which changes have occurred.

Note that for many products with simple supply arrangements and a single market, many details of that market are ‘inherited’ from Block 4 and need not be repeated.

  ProductSupply
  productsupply
  0…n

#### P.24 Market

Group P.24 specifies the geographical extent of a market in which a product is distributed, and any applicable non-geographical sales restrictions, together with an optional reference or label for the market.

It is open to an ONIX user community where all trading takes place within a single geographical market, so that all ONIX records apply to this market, to agree to dispense with Group P.24; and it is therefore not defined as mandatory in the Schema. Where more complex trading relationships apply, the product may be available in multiple markets – where separate markets are distinguished partly through their geographical extent and distribution arrangements, and partly through details such as differing publication arrangements or availability across those markets.

Additional guidance on the description of markets in ONIX 3.0 and 3.1 will be found in a separate document ONIX for Books Product Information Message: How to Specify Markets and Suppliers in ONIX 3.

##### P.24.1 Market reference

For every market, a single market reference which will uniquely identify the <ProductSupply> composite which describes the market within this Product record, and which will remain as its permanent identifier every time you send an update.

The Market reference is optional and non-repeating, but it is strongly recommended unless there is only a single market. It is intended to be used to label each repeat of <ProductSupply> for use in subsequent partial updates and reporting.

Note that the scope of the Market reference is limited to a single Product record – a geographically identical market for a different product may have a different Market reference, and a geographically different market in another Product record may use the same reference.

  Variable length alphanumeric, suggested maximum length 100 characters
  MarketReference
  x587
  0…1
  `<x587>jp.kadokawa.onix.market.アジア太平洋1</x587>` (Asia-Pacific 1)

##### Market composite

A group of data elements which together give details of a geographical territory and any non-geographical sales restrictions that apply within it. Optional in terms of the schema definitions, but required in most ONIX applications. If omitted, the geographical extent of the market must be assumed to be the area defined by the sales rights.

The <Market> composite is repeatable, but in almost all cases only a single instance is required. It may be repeated if a non-geographical sales restriction applies only to a part of a geographically-defined market – for example where a product is sold throughout the European Union, but exclusive to a single retailer in France.

  Market
  market
  0…n

##### Market territory composite

A group of data elements which together identify a territory forming part or all of a market for which supply detail is given. Mandatory in each occurrence of the <Market> composite, and non-repeating.

For valid combinations of <CountriesIncluded>, <RegionsIncluded> etc within <Territory>, see the notes describing the use of <Territory> within Group P.21.

  Territory
  territory
  1

##### P.24.1a Countries included

One or more ONIX codes identifying countries included in the territory. Successive codes must be separated by spaces. Optional and non-repeating, but either <CountriesIncluded> or <RegionsIncluded> is mandatory in each occurrence of the <Territory> composite.

  One or more fixed-length codes based on ISO 3166-1, each consisting of two upper case letters, and with successive codes being separated by spaces. Suggested maximum length 750 characters. Note that ISO 3166-1 specifies that country codes shall be sent as upper case only
  List 91
  CountriesIncluded
  x449
  0…1
  `<CountriesIncluded>US CA</CountriesIncluded>` (USA and Canada)

##### P.24.2 Regions included

One or more ONIX codes identifying regions included in the territory. A region is an area which is not a country, but which is precisely defined in geographical terms, eg World, Northern Ireland, Australian Capital Territory. Successive codes must be separated by spaces. Optional and non-repeating, but either <CountriesIncluded> or <RegionsIncluded> is mandatory in each occurrence of the <Territory> composite.

Note that if used, the ‘WORLD’ region code cannot be combined with other region codes.

  One or more variable-length codes, each consisting of upper case letters, with or without a hyphen and further upper case letters or digits, and with successive codes being separated by spaces. Suggested maximum length 750 characters
  List 49 Where possible and appropriate, country subdivision codes are derived from the UN LOCODE scheme based on ISO 3166-2
  RegionsIncluded
  x450
  0…1
  `<x450>WORLD</x450>` (Whole world)
  `<x450>GB-NIR</x450>` (Northern Ireland)

##### P.24.3 Countries excluded

One or more ONIX codes identifying countries excluded from the territory. Successive codes must be separated by spaces. Optional and non-repeating, and can only occur if the <RegionsIncluded> element is also present and includes a supra-national region code (such as ‘WORLD’).

  One or more fixed-length codes based on ISO 3166-1, each consisting of two upper case letters, and with successive codes being separated by spaces. Suggested maximum length 750 characters. Note that ISO 3166-1 specifies that country codes shall be sent as upper case only
  List 91
  CountriesExcluded
  x451
  0…1
  `<CountriesExcluded>US CA</CountriesExcluded>` (Excludes USA and Canada)

##### P.24.4 Regions excluded

One or more ONIX codes identifying regions excluded from the territory. Successive codes must be separated by spaces. Optional and non-repeating, and can only occur if the <CountriesIncluded> element is also present (and specifies countries of which the excluded regions are a part), or if <RegionsIncluded> is present and includes a supra-national region code (such as ‘WORLD’).

  One or more variable-length codes, each consisting of upper case letters, with or without a hyphen and further upper case letters or digits, and with successive codes being separated by spaces. Suggested maximum length 750 characters
  List 49 Where possible and appropriate, country subdivision codes are derived from the UN LOCODE scheme based on ISO 3166-2
  RegionsExcluded
  x452
  0…1
  `<x452>US-CA</x452>` (Excludes California)

##### End of Market territory composite

##### Market sales restriction composite

A group of data elements which together identify a non-territorial sales restriction which applies within a geographical market. Optional, and repeatable if more than a single restriction applies.

  SalesRestriction
  salesrestriction
  0…n

##### P.24.5 Sales restriction type code

An ONIX code which identifies a non-territorial sales restriction. Mandatory in each occurrence of the <SalesRestriction> composite, and non-repeating.

  Fixed length, two digits
  List 71
  SalesRestrictionType
  b381
  1
  `<b381>07</b381>` (Schools-only edition)

##### Sales outlet composite

An optional and repeatable group of data elements which together identify a sales outlet to which a restriction is linked. Each occurrence of the composite must include a <SalesOutletIdentifier> composite or a <SalesOutletName> or both. Repeatable in order to identify multiple sales outlets subject to the restriction.

  SalesOutlet
  salesoutlet
  0…n

##### Sales outlet identifier composite

An optional group of data elements which together represent a coded identification of a person or organization, used here to identify a sales outlet. Repeatable in order to identify multiple identifiers for the same sales outlet.

  SalesOutletIdentifier
  salesoutletidentifier
  0…n

##### P.24.6 Sales outlet identifier type

An ONIX code which identifies the scheme from which the value in the <IDValue> element is taken. Mandatory in each occurrence of the <SalesOutletIdentifier> composite, and non-repeating.

  Fixed length, two digits
  List 102
  SalesOutletIDType
  b393
  1
  `<b393>03</b393>` (ONIX sales outlet ID code)

##### P.24.7 Identifier type name

A name which identifies a proprietary identifier scheme (ie a scheme which is not a standard and for which there is no individual ID type code). Must be included when, and only when, the code in the <SalesOutletIDType> element indicates a proprietary scheme. Optional and non-repeating.

  Variable length text, suggested maximum length 100 characters
  IDTypeName
  b233
  0…1
  language

##### P.24.8 Identifier value

A code value taken from the scheme specified in the <SalesOutletIDType> element. Mandatory in each occurrence of the <SalesOutletIdentifier> composite, and non-repeating.

  Determined by the scheme specified in <SalesOutletIDType>
  IDValue
  b244
  1

##### End of Sales outlet identifier composite

##### P.24.9 Sales outlet name

The name of a wholesale or retail sales outlet to which a sales restriction is linked. Non-repeating.

  Variable length text, suggested maximum length 200 characters
  SalesOutletName
  b382
  0…1
  language
  `<SalesOutletName>Marks &amp; Spencer</SalesOutletName>` (note ‘&’ is a reserved character in XML)

##### End of Sales outlet composite

##### P.24.10 Sales restriction note

A free text field describing an ‘unspecified’ restriction, or giving more explanation of a coded restriction type. Optional, and repeatable if parallel notes are provided in multiple languages. The language attribute is optional for a single instance of <SalesRestrictionNote>, but must be included in each instance if <SalesRestrictionNote> is repeated.

  Variable length text, suggested maximum length 300 characters. XHTML is enabled in this element – see Using XHTML, HTML, XML, JSON within ONIX text fields
  SalesRestrictionNote
  x453
  0…n
  language, textformat

##### P.24.11 Start date

The date from which a sales restriction is effective. Optional and non-repeating.

  As specified by the value in the dateformat attribute, or the default of YYYYMMDD if the attribute is missing
  StartDate
  b324
  0…1
  dateformat
  `<b324>20090327</b324>`

##### P.24.12 End date

The date until which a sales restriction is effective. Optional and non-repeating.

  As specified by the value in the dateformat attribute, or the default of YYYYMMDD if the attribute is missing
  EndDate
  b325
  0…1
  dateformat
  `<EndDate dateformat="00">20090930</EndDate>`

##### End of Market sales restriction composite

##### End of Market composite

#### P.25 Market publishing detail

Group P.25 carries information about the publishing status of a product within a specified market. This includes details of the publisher’s representation in that market (where applicable); the publishing status of a product in the market, together with publishing dates; and information about promotional activity.

It is open to an ONIX user community where all trading takes place within a single geographical market, so that all ONIX records apply to this market, to agree to dispense with Group P.25; and it is therefore not defined as mandatory in the Schema. In this event, a ‘global’ publishing status and publication date must be included in Group P.20. For products traded in international markets, Group P.25 is expected to be used.

##### Market publishing detail composite

A group of data elements which together give details of the publishing status of a product within a specified market. Optional and non-repeating within an occurrence of the <ProductSupply> block.

  MarketPublishingDetail
  marketpublishingdetail
  0…1

##### Publisher representative composite

A repeatable group of data elements which together identify a publisher representative in a specified market. Optional, and repeated only if the publisher has two or more representatives.

  PublisherRepresentative
  publisherrepresentative
  0…n

##### P.25.1 Agent role

An ONIX code identifying the role of an agent in relation to the product in the specified market, eg Exclusive sales agent, Local publisher, etc. Mandatory in each occurrence of the <PublisherRepresentative> composite.

  Fixed length, two digits
  List 69
  AgentRole
  j402
  1
  `<AgentRole>07</AgentRole>` (Local publisher)

##### Agent identifier composite

A group of data elements together defining the identifier of an agent or local publisher in accordance with a specified scheme. Optional, but each occurrence of the <PublisherRepresentative> composite must carry either at least one agent identifier, or an <AgentName>. Repeatable only if two or more identifiers are sent using different schemes.

  AgentIdentifier
  agentidentifier
  0…n

##### P.25.2 Agent identifier type code

An ONIX code identifying the scheme from which the identifier in the <IDValue> element is taken. Mandatory in each occurrence of the <AgentIdentifier> composite, and non-repeating.

  Fixed length, two digits
  List 92
  AgentIDType
  j400
  1
  `<AgentIDType>06</AgentIDType>` (GLN)

##### P.25.3 Identifier type name

A name which identifies a proprietary identifier scheme (ie a scheme which is not a standard and for which there is no individual ID type code). Must be included when, and only when, the code in the <AgentIDType> element indicates a proprietary scheme. Optional and non-repeating.

  Variable length text, suggested maximum length 100 characters
  IDTypeName
  b233
  0…1
  language
  `<b244>KNO</b244>`

##### P.25.4 Identifier value

An identifier of the type specified in the <AgentIDType> element. Mandatory in each occurrence of the <AgentIdentifier> composite, and non-repeating.

  According to the identifier type specified in <AgentIDType>
  IDValue
  b244
  1
  `<IDValue>12345678</IDValue>`

##### End of Agent identifier composite

##### P.25.5 Agent name

The name of an agent or local publisher. Optional and non-repeating; required if no agent identifier is sent in an occurrence of the <PublisherRepresentative> composite.

  Variable length text, suggested maximum length 100 characters
  AgentName
  j401
  0…1
  language, collationkey
  `<AgentName>Littlehampton Book Services</AgentName>`

##### P.25.6 Agent telephone number

A telephone number of an agent or local publisher. Optional and repeatable. Use to provide contact details for the organization as a whole, but prefer <ProductContact> for individual functions or contacts within the organization.

  Variable length text, suggested maximum length 20 characters
  TelephoneNumber
  j270
  0…n
  `<j270>+44 20 8843 8607</j270>`

##### P.25.7 Agent fax number

A fax number of an agent or local publisher. Optional and repeatable. Use to provide contact details for the organization as a whole, but prefer <ProductContact> for individual functions or contacts within the organization.

  Variable length text, suggested maximum length 20 characters
  FaxNumber
  j271
  0…n
  `<FaxNumber>+44 20 8843 8744</FaxNumber>`

##### P.25.8 Agent e‑mail address

An e‑mail address for an agent or local publisher. Optional and repeatable. Use to provide contact details for the organization as a whole, but prefer <ProductContact> for individual functions or contacts within the organization.

  Variable length text, suggested maximum length 100 characters
  EmailAddress
  j272
  0…n
  `<j272>david@polecat.dircon.co.uk</j272>`

##### Website composite

An optional group of data elements which together identify and provides pointer to a website which is related to the agent or local publisher identified in an occurrence of the <PublisherRepresentative> composite. Repeatable in order to provide links to multiple websites.

  Website
  website
  0…n

##### P.25.9 Website purpose

An ONIX code which identifies the role or purpose of the website which is linked through the <WebsiteLink> element. Optional and non-repeating.

  Fixed length, two digits
  List 73
  WebsiteRole
  b367
  0…1
  `<WebsiteRole>33</WebsiteRole>` (Supplier’s corporate website)

##### P.25.10 Website description

Free text describing the nature of the website which is linked through the <WebsiteLink> element. Optional, and repeatable to provide parallel descriptive text in multiple languages. The language attribute is optional for a single instance of <WebsiteDescription>, but must be included in each instance if <WebsiteDescription> is repeated.

  Variable length text, suggested maximum length 300 characters. XHTML is enabled in this element – see Using XHTML, HTML, XML, JSON within ONIX text fields
  WebsiteDescription
  b294
  0…n
  language, textformat

##### P.25.11 Link to website

The URL for the website. Mandatory in each occurrence of the <Website> composite, and repeatable to provide multiple URLs where the website content is available in multiple languages. The language attribute is optional for a single instance of <WebsiteLink>, but must be included in each instance if <WebsiteLink> is repeated.

  Uniform Resource Locator, expressed in full URI syntax in accordance with W3C standards, suggested maximum length 300 characters. Note that non-ASCII characters, spaces and a handful of other special characters should be ‘URL-encoded’. Any ampersand used to separate parameters in the URL must be expressed as &amp;
  WebsiteLink
  b295
  1…n
  language
  `<b295>http://xyzbooks.com</b295>`

##### End of Website composite

##### End of Publisher representative composite

##### Product contact composite

A group of data elements which together specify an organization (which may or may not be the publisher’s representative) responsible for dealing with enquiries related to the product in the market. Optional, and repeatable in order to specify multiple contacts.

  ProductContact
  productcontact
  0…n

##### P.25.11a Product contact role

An ONIX code which identifies the role played by the product contact in relation to the product – for example answering enquiries related to sales or to promotion.

  Fixed length, two digits
  List 198
  ProductContactRole
  x482
  1
  `<x482>01</x482>` (Accessibility request)

##### Product contact identifier composite

A group of data elements which together specify an identifier of the product contact. The composite is optional, and repeatable if more than one identifier of different types is sent; but either a <ProductContactName> or a <ProductContactIdentifier> must be included.

  ProductContactIdentifier
  productcontactidentifier
  0…n

##### P.25.11b Product contact identifier type

An ONIX code identifying a scheme from which an identifier in the <IDValue> element is taken. Mandatory in each occurrence of the <ProductContactIdentifier> composite, and non-repeating.

  Fixed length, two digits
  List 44
  ProductContactIDType
  x483
  1
  ``

##### P.25.11c Identifier type name

A name which identifies a proprietary identifier scheme (ie a scheme which is not a standard and for which there is no individual ID type code). Must be included when, and only when, the code in the <ProductContactIDType> element indicates a proprietary scheme. Optional and non-repeating.

  Variable length text, suggested maximum 100 characters
  IDTypeName
  b233
  0…1
  language
  ``

##### P.25.11d Identifier value

An identifier of the type specified in the <ProductContactIDType> element. Mandatory in each occurrence of the <ProductContactIdentifier> composite, and non-repeating.

  According to the identifier type specified in <ProductContactIDType>
  IDValue
  b244
  1
  ``

##### End of Product contact identifier composite

##### P.25.11e Product contact name

The name of the product contact organization, which should always be stated in a standard form. Optional and non-repeating; but either a <ProductContactName> element or a <ProductContactIdentifier> composite must be included.

  Variable length text, suggested maximum 50 characters
  ProductContactName
  x484
  0…1
  `<ProductContactName>Little Brown Book Group</ProductContactName>`

##### P.25.11f Contact name

Free text giving the name, department, etc for a contact person in the product contact organization who is responsible for the product. Optional and non-repeating.

  Variable length text, suggested maximum 300 characters
  ContactName
  x299
  0…1
  `<x299>Jackie Brown</x299>`

##### P.25.11g Product contact telephone number

A telephone number of the contact person in the product contact organization who is responsible for the product, wherever possible including the plus sign and the international dialing code. Optional, and repeatable to provide multiple numbers for the same contact.

  Variable length text, suggested maximum length 20 characters
  TelephoneNumber
  j270
  0…n
  `<TelephoneNumber>+44 20 7946 0921</TelephoneNumber>`

##### P.25.11h Product contact fax number

A fax number for the contact person in the product contact organization who is responsible for the product, wherever possible including the plus sign and the international dialing code. Optional, and repeatable to provide multiple numbers for the same contact.

  Variable length text, suggested maximum length 20 characters
  FaxNumber
  j271
  0…n
  `<FaxNumber>+44 20 7946 0921</FaxNumber>`

##### P.25.11i Product contact e‑mail address

A text field giving the e‑mail address for a contact person in the product contact organization who is responsible for the product. Optional, and repeatable to provide multiple e‑mail addresses for the same contact.

  Variable length text, suggested maximum 100 characters
  EmailAddress
  j272
  0…n
  `<j272>jackie.brown@bigpublisher.co.uk</j272>`

##### P.25.11j Product contact street address

A text field giving a street address and forming the first part of the postal address of the product contact organization. Optional and non-repeatable. Care should be taken that the Product contact name (plus optionally the Contact name), Street address, Location name, any Postal code or Region code, and the Country code can be combined into a complete postal address, without repetition.

  Variable length text, suggested maximum 100 characters
  StreetAddress
  x552
  0…1
  `<x552><Via Mondadori 1</x552>`

##### P.25.11k Product contact location name

The name of a city or town location, forming part of the postal address of the product contact organization. Mandatory and non-repeatable if a Street address is present, but otherwise omitted.

  Variable length text, suggested maximum 50 characters
  LocationName
  j349
  0…1
  `<j349>Sagrate</j349>`

##### P.25.11l Product contact postal code

The postal code (postcode, zip code etc), forming part of the postal address of the product contact organization. Optional and non-repeatable if a Street address is present, but otherwise omitted.

  Variable length text, suggested maximum 20 characters
  PostalCode
  x590
  0…1
  `<x590>MI 20090</x590>`

##### P.25.11m Product contact region code

An ONIX code identifying the region within which the product contact organization is located. Optional and non-repeatable if a Street address is present, but otherwise omitted.

For some addresses, a Region code is useful in addition to the Postal code and Country code. In other addresses, a Region code is unnecessary because it is is clearly encoded within the Postal code.

  Variable length code, consisting of upper case letters, with or without a hyphen and further upper case letters or digits. Suggested maximum length 8 characters
  List 49 Where possible and appropriate, country subdivision codes are derived from the UN LOCODE scheme based on ISO 3166-2
  RegionCode
  b398
  0…1
  `<RegionCode>GB-SCT</RegionCode>` (Scotland)

##### P.25.11n Product contact country code

An ONIX code identifying the country within which the product contact organization is located. Mandatory and non-repeatable if a Street address is present, but otherwise omitted.

  Fixed length, two letters, based on ISO 3166-1. Note that ISO 3166-1 specifies that country codes shall be sent as upper case only
  List 91
  CountryCode
  b251
  0…1
  `<CountryCode>IT</CountryCode>` (Italy)

##### End of Product contact composite

##### P.25.12 Market publishing status

An ONIX code which identifies the status of a published product in a specified market. Mandatory in each occurrence of the <MarketPublishingDetail> composite, and non-repeating.

  Fixed length, two digits
  List 68
  MarketPublishingStatus
  j407
  1
  `<MarketPublishingStatus>02</MarketPublishingStatus>` (Forthcoming)

##### P.25.13 Market publishing status note

Free text that describes the status of a product in a specified market, when the code in <MarketPublishingStatus> is insufficient. Optional, but when used, must be accompanied by the <MarketPublishingStatus> element. Repeatable if parallel text is provided in multiple languages. The language attribute is optional for a single instance of <MarketPublishingStatusNote>, but must be included in each instance if <MarketPublishingStatusNote> is repeated.

  Variable length text, suggested maximum 300 characters. XHTML is enabled in this element – see Using XHTML, HTML, XML, JSON within ONIX text fields
  MarketPublishingStatusNote
  x406
  0…n
  language, textformat
  `<x406>Agent has lost contact with publisher</x406>`

##### Market date composite

A group of data elements which together specify a date associated with the publishing status of the product in a specified market, eg ‘local publication date’. Optional, but if known, a date of publication must be specified either here as a ‘local publication date’ or in P.20. Other dates relating to the publication of the product in the specific market may be sent in further repeats of the composite.

  MarketDate
  marketdate
  0…n

##### P.25.14 Market date role code

An ONIX code indicating the significance of the date. Mandatory in each occurrence of the <MarketDate> composite, and non-repeating.

  Fixed length, two digits
  List 163
  MarketDateRole
  j408
  1
  `<j408>01</j408>` (Publication date)
  A date such as a publication date should be interpreted as the ‘publication’ or first availability date within the market, and not as a ‘global’ publication date.

##### P.25.16 Date

The date specified in the <MarketDateRole> field. Mandatory in each occurrence of the <MarketDate> composite, and non-repeating. <Date> may carry a dateformat attribute: if the attribute is missing, then the default format is YYYYMMDD.

  As specified by the value in the dateformat attribute, or the default YYYYMMDD
  Date
  b306
  1
  dateformat
  `<b306>20010106</b306>`

##### End of Market date composite

##### P.25.17 Promotion campaign information

Free text describing the promotion and adverting campaign for the product. Optional, and repeatable if parallel text is provided in multiple languages. The language attribute is optional for a single instance of <PromotionCampaign>, but must be included in each instance if <PromotionCampaign> is repeated.

  Variable length text, suggested maximum length 2,000 characters. XHTML is enabled in this element – see Using XHTML, HTML, XML, JSON within ONIX text fields
  PromotionCampaign
  k165
  0…n
  language, textformat

##### P.25.19 Initial print run

In advance information about a new book, free text detailing the number of copies which will be printed and any related aspects of the initial publishing effort. Optional, and repeatable if parallel text is provided in multiple languages. The language attribute is optional for a single instance of <InitialPrintRun>, but must be included in each instance if <InitialPrintRun> is repeated.

  Variable length text, suggested maximum length 200 characters. XHTML is enabled in this element – see Using XHTML, HTML, XML, JSON within ONIX text fields
  InitialPrintRun
  k167
  0…n
  language, textformat
  `<InitialPrintRun>450 numbered copies</InitialPrintRun>`

##### P.25.20 Reprint detail

Free text used to give details of the reprint history as part of the promotion of a book. Optional, and repeatable if parallel text is provided in multiple languages. The language attribute is optional for a single instance of <ReprintDetail>, but must be included in each instance if <ReprintDetail> is repeated.

  Variable length text, suggested maximum length 200 characters. XHTML is enabled in this element – see Using XHTML, HTML, XML, JSON within ONIX text fields
  ReprintDetail
  k309
  0…n
  language, textformat
  `<ReprintDetail textformat="05"><dl><dt>Jan 2016</dt><dd>Initial printing</dd><dt>Mar 2016</dt><dd>Second impression</dd></dl>`

##### P.25.21 Copies sold

Free text detailing the number of copies already sold, eg for a new paperback, the copies sold in hardback. Optional, and repeatable if parallel text is provided in multiple languages. The language attribute is optional for a single instance of <CopiesSold>, but must be included in each instance if <CopiesSold> is repeated.

  Variable length text, suggested maximum length 200 characters. XHTML is enabled in this element – see Using XHTML, HTML, XML, JSON within ONIX text fields
  CopiesSold
  k168
  0…n
  language, textformat
  `<CopiesSold>6400 copies sold of this edition in hardback</CopiesSold>`

##### P.25.22 Book club adoption

Free text describing the adoption of the product as a book club selection. Optional, and repeatable if parallel text is provided in multiple languages. The language attribute is optional for a single instance of <BookClubAdoption>, but must be included in each instance if <BookClubAdoption> is repeated.

  Variable length text, suggested maximum length 200 characters. XHTML is enabled in this element – see Using XHTML, HTML, XML, JSON within ONIX text fields
  BookClubAdoption
  k169
  0…n
  language, textformat
  `<k169>Book-Of-The-Month Club selection for May 2000</k169>`

##### End of Market publishing detail composite

#### P.26 Supply detail

Group P.26 carries information about the distribution arrangements, availability and price, and other aspects of the supply status, of a product in a specified market. The geographical extent and other restrictions of the market itself are described in P.24, and the status of the product in that market in P.25. P.26 is conceptually the most complex group of an ONIX for Books Product record, though largely because of the number of purely optional composites.

The general structure of the Supply detail group is as follows, with the nesting of elements and composites within larger composites shown by indentation:

- Block 6 Product supply composite – repeatable: each repeat deals with a single market
  - P.24 Market composite – geographical details of the market (if different from the ‘global’ sales rights and restrictions in Group P.21)
  - P.25 Market publishing detail composite
    - Publisher representative in the market (if not the publisher in Group P.19)
    - Publishing status in the market (if different from the ‘global’ status in Group P.20)
    - Publishing dates in the market (if different from the ‘global’ dates in Group P.20)
  - P.26 Supply detail composite – repeatable: each repeat deals with a single supplier
    - Supplier composite – the supplier’s identity and contact details
      - Supplier role
      - Supplier identifier composite
      - Supplier name and contact details
      - Supplier website composite
    - Supply contact composite
    - Supplier own coding composite – may carry proprietary information to or from the supplier
    - Returns conditions composite
    - Product availability – from the supplier
    - Supply date composite – eg expected availability or last date for returns
    - Order lead time – expected time for supplier to fulfill an order
    - New supplier composite – use where supply details are changing
      - Supplier identifier composite
      - Supplier name and contact details
    - Stock quantity composite – use to communicate physical stock levels
      - Location identifier composite
      - Location name
      - Stock quantity coded composite
      - Stock quantities
      - On order detail composite
      - Velocity composite
    - Pack or carton quantity
    - Minimum order quantity
    - Unpriced item type – as an alternative to…
    - Price composite – repeatable for each different price the supplier may charge
      - Price identifier composite
      - Price type – eg rrp, inc or exc tax, agency price, special prices
      - Price constraint composite – eg library lending constraints
      - Price condition composite – eg previous qualifying product purchases
      - Minimum qualifying order quantity
      - Batch bonus composite
      - Discount code composite – discount or commission terms
      - Discount composite
      - Price status
      - Price amount – the price in a specific currency…
      - Price coded composite – or a price tier
      - Tax composite – details of any tax included in the price
      - Unpriced item type – as an alternative to a single price amount
      - Currency code – currency in which the price is expressed
      - Territory composite – territory within which the price is valid
      - Comparison product price composite – use primarily in e‑book Product records to deliver prices of directly-comparable physical products
      - Price date composite – limits on price validity (including future changes)
      - Price printed on product

##### Supply detail composite

A group of data elements which together give details of a supply source, and price and availability from that source. Mandatory in each ordinary occurrence of the <ProductSupply> block, and repeatable to give details of multiple supply sources.

Exceptionally, <SupplyDetail> may be omitted only within a partial or ‘block update’ (Notification or update type 04, see P.1.2) where a <MarketReference> is supplied, when the intention is to remove all previously-supplied Supply details for the referenced market (for example when one market is being merged into another).

  SupplyDetail
  supplydetail
  0…n

##### Supplier composite

A group of data elements which together identify a specific supplier. Mandatory in each occurrence of the <SupplyDetail> composite, and not repeatable.

  Supplier
  supplier
  1

##### P.26.1 Supplier role

An ONIX code identifying the role of the supplier in relation to the product, eg Publisher, Publisher’s exclusive distributor, etc. Mandatory in each occurrence of the <Supplier> composite, and non-repeating.

  Fixed length, two digits
  List 93
  SupplierRole
  j292
  1
  `<SupplierRole>01</SupplierRole>` (Publisher)

##### Supplier identifier composite

A group of data elements which together specify an identifier of the supplier in accordance with a specified scheme, and repeatable to allow different types of supplier identifier to be included without defining additional data elements. Optional, but each occurrence of the <Supplier> composite must carry either at least one supplier identifier, or a <SupplierName>, or both.

  SupplierIdentifier
  supplieridentifier
  0…n

##### P.26.2 Supplier identifier type code

An ONIX code identifying the scheme from which the identifier in the <IDValue> element is taken. Mandatory in each occurrence of the <SupplierIdentifier> composite, and non-repeating.

  Fixed length, two digits
  List 92
  SupplierIDType
  j345
  1
  `<j345>12</j345>` (Distributeurscode Boekenbank, Flemish supplier code)

##### P.26.3 Identifier type name

A name which identifies a proprietary identifier scheme (ie a scheme which is not a standard and for which there is no individual ID type code). Must be included when, and only when, the code in the <SupplierIDType> element indicates a proprietary scheme, eg a wholesaler’s own code. Optional and non-repeating.

  Variable length text, suggested maximum length 100 characters
  IDTypeName
  b233
  0…1
  language
  `<b233>KNO</b233>`

##### P.26.4 Identifier value

An identifier of the type specified in the <SupplierIDType> element. Mandatory in each occurrence of the <SupplierIdentifier> composite, and non-repeating.

  According to the identifier type specified in <SupplierIDType>
  IDValue
  b244
  1
  `<IDValue>12345678</IDValue>`

##### End of Supplier identifier composite

##### P.26.5 Supplier name

The name of a supply source from which the product may be ordered by a trade customer. Optional and non-repeating; required if no supplier identifier is sent.

  Variable length text, suggested maximum length 100 characters
  SupplierName
  j137
  0…1
  language, collationkey
  `<j137>Littlehampton Book Services</j137>`

##### P.26.6 Supplier telephone number

A telephone number of a supply source from which the product may be ordered by a trade customer. Optional and repeatable. Use to provide contact details for the organization as a whole, but prefer <SupplyContact> for individual functions or contacts within the organization.

  Variable length text, suggested maximum length 20 characters
  TelephoneNumber
  j270
  0…n
  `<TelephoneNumber>+44 20 8843 8607</TelephoneNumber>`

##### P.26.7 Supplier fax number

A fax number of a supply source from which the product may be ordered by a trade customer. Optional and repeatable. Use to provide contact details for the organization as a whole, but prefer <SupplyContact> for individual functions or contacts within the organization.

  Variable length text, suggested maximum length 20 characters
  FaxNumber
  j271
  0…n
  `<j271>+44 20 8843 8744</j271>`

##### P.26.8 Supplier e‑mail address

An e‑mail address for a supply source from which the product may be ordered by a trade customer. Optional and repeatable. Use to provide contact details for the organization as a whole, but prefer <SupplyContact> for individual functions or contacts within the organization.

  Variable length text, suggested maximum length 100 characters
  EmailAddress
  j272
  0…n
  `<j272>david@polecat.dircon.co.uk</j272>`

##### Website composite

An optional group of data elements which together identify and provide a pointer to a website which is related to the organization identified in an occurrence of the <Supplier> composite. Repeatable in order to provide links to multiple websites.

  Website
  website
  0…n

##### P.26.9 Website purpose

An ONIX code which identifies the role or purpose of the website which is linked through the <WebsiteLink> element. Optional and non-repeating.

  Fixed length, two digits
  List 73
  WebsiteRole
  b367
  0…1
  `<b367>34</b367>` (Supplier’s B2B website)

##### P.26.10 Website description

Free text describing the nature of the website which is linked through the <WebsiteLink> element. Optional, and repeatable to provide parallel descriptive text in multiple languages. The language attribute is optional for a single instance of <WebsiteDescription>, but must be included in each instance if <WebsiteDescription> is repeated.

  Variable length text, suggested maximum length 300 characters. XHTML is enabled in this element – see Using XHTML, HTML, XML, JSON within ONIX text fields
  WebsiteDescription
  b294
  0…n
  language, textformat

##### P.26.11 Link to website

The URL for the website. Mandatory in each occurrence of the <Website> composite, and repeatable to provide multiple URLs where the website content is available in multiple languages. The language attribute is optional for a single instance of <WebsiteLink>, but must be included in each instance if <WebsiteLink> is repeated.

  Uniform Resource Locator, expressed in full URI syntax in accordance with W3C standards, suggested maximum length 300 characters. Note that non-ASCII characters, spaces and a handful of other special characters should be ‘URL-encoded’. Any ampersand used to separate parameters in the URL must be expressed as &amp;
  WebsiteLink
  b295
  1…n
  language
  `<WebsiteLink>https://orders.xyzbooks.com</WebsiteLink>`

##### End of Website composite

##### End of Supplier composite

##### Supply contact composite

An optional group of data elements which together specify an organization (which may or may not be the supplier) responsible for dealing with enquiries related to the product. Repeatable in order to specify multiple contacts.

  SupplyContact
  supplycontact
  0…n

##### P.26.11a Supply contact role

An ONIX code which identifies the role played by the supply contact in relation to the product – for example answering enquiries related to orders or to returns.

  Fixed length, two digits
  List 239
  SupplyContactRole
  x537
  1
  `<SupplyContactRole>07</SupplyContactRole>` (Returns authorization contact)

##### Supply contact identifier composite

A group of data elements which together specify an identifier for the supply contact. The composite is optional, and repeatable if more than one identifier of different types is sent; but either a <SupplyContactName> or a <SupplyContactIdentifier> must be included.

  SupplyContactIdentifier
  supplycontactidentifier
  0…n

##### P.26.11b Supply contact identifier type

An ONIX code identifying a scheme from which an identifier in the <IDValue> element is taken. Mandatory in each occurrence of the <SupplyContactIdentifier> composite, and non-repeating.

  Fixed length, two digits
  List 44
  SupplyContactIDType
  x538
  1

##### P.26.11c Identifier type name

A name which identifies a proprietary identifier scheme (ie a scheme which is not a standard and for which there is no individual ID type code). Must be included when, and only when, the code in the <SupplyContactIDType> element indicates a proprietary scheme. Optional and non-repeating.

  Variable length text, suggested maximum 100 characters
  IDTypeName
  b233
  0…1
  language

##### P.26.11d Identifier value

An identifier of the type specified in the <SupplyContactIDType> element. Mandatory in each occurrence of the <SupplyContactIdentifier> composite, and non-repeating.

  According to the identifier type specified in <SupplyContactIDType>
  IDValue
  b244
  1

##### End of Supply contact identifier composite

##### P.26.11e Supply contact name

The name of the supply contact organization, which should always be stated in a standard form. Optional and non-repeating; but either a <SupplyContactName> element or a <SupplyContactIdentifier> composite must be included.

  Variable length text, suggested maximum 50 characters
  SupplyContactName
  x539
  0…1
  `<SupplyContactName>Marston Book Services</SupplyContactName>`

##### P.26.11f Contact name

Free text giving the name, department, etc for a contact person in the supply contact organization who is responsible for the product. Optional and non-repeating.

  Variable length text, suggested maximum length 300 characters
  ContactName
  x299
  0…1
  `<x299>Jackie Brown</x299>`

##### P.26.11g Supply contact telephone number

A telephone number of the contact person in the supply contact organization who is responsible for the product, wherever possible including the plus sign and the international dialing code. Optional, and repeatable to provide multiple numbers for the same contact.

  Variable length text, suggested maximum length 20 characters
  TelephoneNumber
  j270
  0…n
  `<j270>+44 20 8843 8607</j270>`

##### P.26.11h Supply contact fax number

A fax number for the contact person in the supply contact organization who is responsible for the product, wherever possible including the plus sign and the international dialing code. Optional, and repeatable to provide multiple numbers for the same contact.

  Variable length text, suggested maximum length 20 characters
  FaxNumber
  j271
  0…n
  `<j271>+44 20 8843 8607</j271>`

##### P.26.11i Supply contact e‑mail address

A text field giving the e‑mail address for a contact person in the supply contact organization who is responsible for the product. Optional, and repeatable to provide multiple e‑mail addresses for the same contact.

  Variable length text, suggested maximum 100 characters
  EmailAddress
  j272
  0…n
  `<j272>Jackie.brown@bigpublisher.co.uk</j272>`

##### P.26.11j Supply contact street address

A text field giving a street address and forming the first part of the postal address of the supply contact organization. Optional and non-repeatable. Care should be taken that the Supply contact name (plus optionally the Contact name), Street address, Location name, any Postal code or Region code, and Country code can be combined into a complete postal address, without repetition.

  Variable length text, suggested maximum 100 characters
  StreetAddress
  x552
  0…1
  `<x552>Via Mondadori 1</x552>`

##### P.26.11k Supply contact location name

The name of a city or town location, forming part of the postal address of the supply contact organization. Mandatory if a Street address is present, but otherwise omitted.

  Variable length text, suggested maximum 50 characters
  LocationName
  j349
  0…1
  `<j349>Sagrate</j349>`

##### P.26.11l Supply contact postal code

The postal code (postcode, zip code etc), forming part of the postal address of the supply contact organization. Optional and non-repeatable if a Street address is present, but otherwise omitted.

  Variable length text, suggested maximum 20 characters
  PostalCode
  x590
  0…1
  `<x590>MI 20090</x590>`

##### P.26.11m Supply contact region code

An ONIX code identifying the region within which the supply contact organization is located. Optional and non-repeatable if a Street address is present, but otherwise omitted.

For some addresses, a Region code is useful in addition to the Postal code and Country code. In other addresses, a region is unnecessary because it is clearly encoded within the Postal code.

  Variable length code, consisting of upper case letters, with or without a hyphen and further upper case letters or digits. Suggested maximum length 8 characters
  List 49 Where possible and appropriate, country subdivision codes are derived from the UN LOCODE scheme based on ISO 3166-2
  RegionCode
  b398
  0…1
  `<RegionCode>GB-WLS</RegionCode>` (Wales)

##### P.26.11n Supply contact country code

An ONIX code identifying the country within which the supply contact organization is located. Mandatory and non-repeatable if a Street address is present, but otherwise omitted.

  Fixed length, two letters, based on ISO 3166-1. Note that ISO 3166-1 specifies that country codes shall be sent as upper case only
  List 91
  CountryCode
  b251
  0…1
  `<CountryCode>IT</CountryCode>` (Italy)

##### End of Supply contact composite

##### Supplier own coding composite

An optional and repeatable group of data elements which together allow a supplier to send coded data of a specified type, using its own coding schemes.

  SupplierOwnCoding
  supplierowncoding
  0…n

##### P.26.12 Supplier code type

An ONIX code identifying the type of a supplier own code. Mandatory in each occurrence of the <SupplierOwnCoding> composite, and non-repeating.

  Fixed length, two digits
  List 165
  SupplierCodeType
  x458
  1
  `<SupplierCodeType>01</SupplierCodeType>` (Supplier’s sales classification)

##### P.26.12a Supplier code type name

A name which identifies the proprietary coding scheme used. Optional and non-repeating.

  Variable length text, suggested maximum length 50 characters
  SupplierCodeTypeName
  x513
  0…1
  language
  `<x513>AppleFBC</x513>`

##### P.26.13 Supplier code value

A supplier-defined code of the type specified in the <SupplierCodeType> element. Mandatory in each occurrence of the <SupplierOwnCoding> composite, and non-repeating.

  According to the supplier’s own format for the code type specified in <SupplierCodeType>
  SupplierCodeValue
  x459
  1
  `<x459>B</x459>`

##### End of Supplier own coding composite

##### Returns conditions composite

An optional and repeatable group of data elements which together allow the supplier’s returns conditions to be specified in coded form.

  ReturnsConditions
  returnsconditions
  0…n

##### P.26.14 Returns code type

An ONIX code identifying the scheme from which the returns conditions code in <ReturnsCode> is taken. Mandatory in each occurrence of the <ReturnsConditions> composite, and non-repeating.

  Fixed length, two digits
  List 53
  ReturnsCodeType
  j268
  1
  `<ReturnsCodeType>01</ReturnsCodeType>` (CLIL French book trade returns code)

##### P.26.15 Returns code type name

A name which identifies a proprietary returns code scheme. Must be used when, and only when, the code in the <ReturnsCodeType> element indicates a proprietary scheme, eg a wholesaler’s own code. Optional and non-repeating.

  Variable length text, suggested maximum length 50 characters
  ReturnsCodeTypeName
  x460
  0…1
  language
  `<ReturnsCodeTypeName>KNO</ReturnsCodeTypeName>`

##### P.26.16 Returns conditions code

A returns conditions code from the scheme specified in <ReturnsCodeType>. Mandatory in each occurrence of the <ReturnsConditions> composite, and non-repeating.

  According to the scheme specified in <ReturnsCodeType>
  For values defined by BISAC for US use, see List 66. For other uses, see List 204
  ReturnsCode
  j269
  1
  `<j269>S</j269>` (Stripped cover returnable)

##### P.26.16a Returns conditions note

Free text note explaining the returns conditions or special returns instructions, where the code alone is not sufficient. Optional, and repeatable if parallel text is provided in multiple languages. The language attribute is optional for a single instance of <ReturnsNote>, but must be included in each instance if <ReturnsNote> is repeated.

  Variable length text, suggested maximum length 200 characters
  ReturnsNote
  x528
  0…n
  language
  `<x528 language="eng">Obtain return authorization in advance</x528>`

##### End of Returns conditions composite

##### P.26.17 Product availability

An ONIX code indicating the availability of a product from a supplier. Mandatory in each occurrence of the <SupplyDetail> composite, and non-repeating.

  Fixed length, two digits
  List 65
  ProductAvailability
  j396
  1
  `<j396 datestamp="20101029">41</j396>` (Replaced by new product)

  Note the typical progression of product availability, from initial announcement to one of the forms of ‘unavailable’. Not all possible availability codes are shown, particularly within the ‘Unavailable’ group where there are many more possible options:

  Transitions within and between the shaded groups are greatly simplified – for example, it would be unexpected if ‘Reprinting’ or ‘Reissuing’ statuses (32 and 33 on List 65) would be followed by anything other than ‘In stock’ (21), but on occasion where the publisher changes plans, ‘Available via POD’ (23), ‘Only to order’ (22), or an ‘Unavailable’ (4x) code are all possible. Ideally, ‘Abandoned’ (01) and the ‘Unavailable’ (4x) codes indicate the end of the product’s life, but as with <PublishingStatus>, cancelled or out of print products are occasionally re-activated or re-announced.

##### Supply date composite

An optional group of data elements which together specify a date associated with the supply status of the product, eg expected ship date. Repeatable in order to specify multiple dates.

  SupplyDate
  supplydate
  0…n

##### P.26.18 Supply date role code

An ONIX code indicating the significance of the date. Mandatory in each occurrence of the <SupplyDate> composite, and non-repeating.

  Fixed length, two digits
  List 166
  SupplyDateRole
  x461
  1
  `<SupplyDateRole>02</SupplyDateRole>` (Embargo date)

##### P.26.20 Date

The date specified in the <SupplyDateRole> field. Mandatory in each occurrence of the <SupplyDate> composite, and non-repeating. <Date> may carry a dateformat attribute: if the attribute is missing, then the default format is YYYYMMDD.

  As specified by the value in the dateformat attribute, or the default YYYYMMDD
  Date
  b306
  1
  dateformat
  `<b306>20100106</b306>`

##### End of Supply date composite

##### P.26.21 Order time

The expected average number of business days from receipt of order to dispatch (for items ‘manufactured on demand’ or ‘only to order’). Optional and non-repeating.

  Positive integer or zero, one or two digits only. Zero indicates expected ‘same day’ dispatch
  OrderTime
  j144
  0…1
  `<OrderTime>7</OrderTime>`

##### New supplier composite

An optional group of data elements which together specify a new supply source to which orders are referred. Use only when the code in <ProductAvailability> indicates ‘no longer available from us, refer to new supplier’. Only one occurrence of the composite is permitted in this context.

  NewSupplier
  newsupplier
  0…1

##### New supplier identifier composite

A group of data elements which together define the identity of a supplier in accordance with a specified scheme, and repeatable to allow different types of supplier identifier to be included without defining additional data elements. Optional, but each occurrence of the <NewSupplier> composite must carry either at least one supplier identifier, or a <SupplierName>, or both.

  SupplierIdentifier
  supplieridentifier
  0…n

##### P.26.22 Supplier identifier type code

An ONIX code identifying the scheme from which the identifier in the <IDValue> element is taken. Mandatory in each occurrence of the <SupplierIdentifier> composite, and non-repeating.

  Fixed length, two digits
  List 92
  SupplierIDType
  j345
  1
  `<j345>12</j345>` (Distributeurscode Boekenbank, Flemish supplier code)

##### P.26.23 Identifier type name

A name which identifies a proprietary identifier scheme (ie a scheme which is not a standard and for which there is no individual ID type code). Must be included when, and only when, the code in the <SupplierIDType> element indicates a proprietary scheme, eg a wholesaler’s own code. Optional and non-repeating.

  Variable length text, suggested maximum length 100 characters
  IDTypeName
  b233
  0…1
  language
  `<b233>KNO</b233>`

##### P.26.24 Identifier value

An identifier of the type specified in the <SupplierIDType> element. Mandatory in each occurrence of the <SupplierIdentifier> composite, and non-repeating.

  According to the identifier type specified in <SupplierIDType>
  IDValue
  b244
  1
  `<IDValue>12345678</IDValue>`

##### End of New supplier identifier composite

##### P.26.25 New supplier name

The name of a new supplier. Optional and non-repeating; required if no supplier identifier is sent in an occurrence of the <NewSupplier> composite.

  Variable length text, suggested maximum length 100 characters
  SupplierName
  j137
  0…1
  language, collationkey
  `<j137>Littlehampton Book Services</j137>`

##### P.26.26 New supplier telephone number

A telephone number of a supply source from which the product may be ordered by a trade customer. Optional and repeatable.

  Variable length text, suggested maximum length 20 characters
  TelephoneNumber
  j270
  0…n
  `<TelephoneNumber>+44 20 8843 8607</TelephoneNumber>`

##### P.26.27 New supplier fax number

A fax number of a supply source from which the product may be ordered by a trade customer. Optional and repeatable.

  Variable length text, suggested maximum length 20 characters
  FaxNumber
  j271
  0…n
  `<j271>+44 20 8843 8744</j271>`

##### P.26.28 New supplier e‑mail address

An e‑mail address for a supply source from which the product may be ordered by a trade customer. Optional and repeatable.

  Variable length text, suggested maximum length 100 characters
  EmailAddress
  j272
  0…n
  `<j272>david@polecat.dircon.co.uk</j272>`

##### Website composite

An optional group of data elements which together identify and provide a pointer to a website which is related to the organization identified in an occurrence of the <NewSupplier> composite. Repeatable in order to provide links to multiple websites.

  Website
  website
  0…n

##### P.26.28a Website purpose

An ONIX code which identifies the role or purpose of the website which is linked through the <WebsiteLink> element. Optional and non-repeating.

  Fixed length, two digits
  List 73
  WebsiteRole
  b367
  0…1
  `<b367>34</b367>` (New supplier’s B2B website)

##### P.26.28b Website description

Free text describing the nature of the website which is linked through the <WebsiteLink> element. Optional, and repeatable to provide parallel descriptive text in multiple languages. The language attribute is optional for a single instance of <WebsiteDescription>, but must be included in each instance if <WebsiteDescription> is repeated.

  Variable length text, suggested maximum length 300 characters. XHTML is enabled in this element – see Using XHTML, HTML, XML, JSON within ONIX text fields
  WebsiteDescription
  b294
  0…n
  language, textformat

##### P.26.28c Link to website

The URL for the website. Mandatory in each occurrence of the <Website> composite, and repeatable to provide multiple URLs where the website content is available in multiple languages. The language attribute is optional for a single instance of <WebsiteLink>, but must be included in each instance if <WebsiteLink> is repeated.

  Uniform Resource Locator, expressed in full URI syntax in accordance with W3C standards, suggested maximum length 300 characters. Note that non-ASCII characters, spaces and a handful of other special characters should be ‘URL-encoded’. Any ampersand used to separate parameters in the URL must be expressed as &amp;
  WebsiteLink
  b295
  1…n
  language
  `<WebsiteLink>https://orders.xyzbooks.com</WebsiteLink>`

##### End of Website composite

##### End of New supplier composite

##### Stock quantity composite

An optional group of data elements which together specify a quantity of stock, repeatable where a supplier has more than one warehouse or supplier location.

Within a single instance of the <Stock> composite, the location name and identifier are both optional. If <Stock> is repeated, at least one identifier or a location name must be included in each instance.

  Stock
  stock
  0…n

##### Location identifier composite

An optional group of data elements which together define the identifier of a stock location in accordance with a specified scheme, and repeatable to allow different types of location identifier to be supported without defining additional data elements.

  LocationIdentifier
  locationidentifier
  0…n

##### P.26.29 Location identifier type

An ONIX code identifying the scheme from which the identifier in the <IDValue> element is taken. Mandatory in each occurrence of the <LocationIdentifier> composite, and non-repeating.

  Fixed length, two digits
  List 92
  LocationIDType
  j377
  1
  `<LocationIDType>06</LocationIDType>` (GLN)

##### P.26.30 Identifier type name

A name which identifies a proprietary identifier scheme (ie a scheme which is not a standard and for which there is no individual ID type code). Must be used when, and only when, the code in the <LocationIDType> element indicates a proprietary scheme, eg a wholesaler’s own code. Optional and non-repeating.

  Variable length text, suggested maximum length 100 characters
  IDTypeName
  b233
  0…1
  language
  `<b233>IngramSID</b233>`

##### P.26.31 Identifier value

An identifier of the type specified in the <LocationIDType> element. Mandatory in each occurrence of the <LocationIdentifier> composite, and non-repeating.

  According to the identifier type specified in <LocationIDType>
  IDValue
  b244
  1
  `<IDValue>12345678</IDValue>`

##### End of Location identifier composite

##### P.26.32 Location name

The name of a stock location. Optional, and repeatable to provide parallel names for a single location in multiple languages (eg Baile Átha Cliath and Dublin, or Bruxelles and Brussel). It may if necessary include a postal code (eg 10680 Αθήνα, or 20090 Assago). The language attribute is optional for a single instance of <LocationName>, but must be included in each instance if <LocationName> is repeated.

  Variable length text, suggested maximum length 100 characters
  LocationName
  j349
  0…n
  language
  `<j349>Momence</j349>`

##### Stock quantity coded composite

A group of data elements which together specify a stock level in a coded way without stating the exact quantity of stock. Either <StockQuantityCoded> or <OnHand> is mandatory in each occurrence of the <Stock> composite, even if the quantity on hand is zero. Repeatable, so that it is possible to provide coded quantities on hand, quantities on order etc separately.

  StockQuantityCoded
  stockquantitycoded
  0…n

##### P.26.33 Stock quantity code type

An ONIX code identifying the scheme from which the value in the <StockQuantityCode> element is taken. Mandatory in each occurrence of the <StockQuantityCoded> composite, and non-repeating.

  Fixed length, two digits
  List 70
  StockQuantityCodeType
  j293
  1
  `<StockQuantityCodeType>02</StockQuantityCodeType>` (APA stock quantity code)

##### P.26.34 Stock quantity code type name

A name that identifies a proprietary stock quantity coding scheme (ie a scheme which is not a standard and for which there is no individual ID type code). Must be used when, and only when the code in the <StockQuantityCodeType> element indicates a proprietary scheme, eg a wholesaler’s own code. Optional, and non-repeating.

  Variable length text, suggested maximum length 100 characters
  StockQuantityCodeTypeName
  j296
  0…1
  language
  `<j296>IngramSQ</j296>`

##### P.26.35 Stock quantity code

A code value taken from the scheme specified in the <StockQuantityCodeType> element. Mandatory in each occurrence of the <StockQuantityCoded> composite, and non-repeating.

  According to the scheme specified in <StockQuantityCodeType>
  StockQuantityCode
  j297
  1
  `<StockQuantityCode>LOW</StockQuantityCode>`

##### End of Stock quantity coded composite

##### P.26.36 Quantity on hand

The quantity of stock on hand and available to fulfill new orders. Either <StockQuantityCoded> or <OnHand> is mandatory in each occurrence of the <Stock> composite, even if the quantity on hand is zero. Non-repeating.

  Positive or negative integer or zero, suggested maximum length 7 digits. Negative numbers indicate order commitments in excess of the copies on hand for which no further stock has been ordered
  OnHand
  j350
  0…1
  `<OnHand>4259</OnHand>`

##### P.26.36a Quantity on hand proximity

An ONIX code which specifies the precision of the stock quantity on hand. Optional, non-repeating and may only be used if an <OnHand> value is specified.

  Fixed length, two digits
  List 215
  Proximity
  x502
  0…1
  `<Proximity>05</Proximity>` (About – generally interpreted as ‘within a factor of two’)

##### P.26.36b Quantity reserved

The quantity of stock on hand but unavailable to fulfil new orders for any reason – for example because the stock is reserved to fulfill existing orders or frozen to prevent dispatch. Optional and non-repeating.

  Positive integer or zero, suggested maximum length 7 digits.
  Reserved
  x536
  0…1
  `<Reserved>500</Reserved>`

##### P.26.36c Quantity reserved proximity

An ONIX code which specifies the precision of the reserved stock quantity. Optional, non-repeating, and may only be used if a <Reserved> value is specified.

  Fixed length, two digits
  List 215
  Proximity
  x502
  0…1
  `<Proximity>07</Proximity>` (More than)

##### P.26.37 Quantity on order

The quantity of stock on order. Optional and non-repeating.

  Positive integer or zero, suggested maximum length 7 digits
  OnOrder
  j351
  0…1
  `<OnOrder>600</OnOrder>`

##### P.26.37a Quantity on order proximity

An ONIX code which specifies the precision of the stock quantity on order. Optional, non-repeating and may only be used if an <OnOrder> value is specified.

  Fixed length, two digits
  List 215
  Proximity
  x502
  0…1
  `<x502>03</x502>` (Exactly)

##### P.26.38 Committed backorder quantity

The quantity of stock on order which is already committed to meet backorders. Optional and non-repeating.

  Positive integer or zero, suggested maximum length 7 digits
  CBO
  j375
  0…1
  `<CBO>244</CBO>`

##### P.26.38a Committed backorder quantity proximity

An ONIX code which specifies the precision of the committed backorder quantity. Optional, non-repeating and may only be used if an <CBO> value is specified.

  Fixed length, two digits
  List 215
  Proximity
  x502
  0…1
  `<Proximity>01</Proximity>` (Less than)

##### On order detail composite

A repeatable group of data elements which together specify details of a stock shipment currently awaited, normally from overseas. Optional and repeatable if more than a single shipment is outstanding.

Note that quantities in the <OnOrderDetail> composite must be included in any total quantity on order given in P.26.37 <OnOrder>, and detail need not be given for all outstanding shipments (ie the P.26.37 <OnOrder> must be greater than or equal to the total of the <OnOrder> elements in repeats of the composite).

  OnOrderDetail
  onorderdetail
  0…n

##### P.26.39 Quantity in shipment

The quantity of stock on order in a particular shipment. Mandatory in each occurrence of the <OnOrderDetail> composite, and non-repeating.

  Positive integer or zero, here necessarily positive, suggested maximum length 7 digits
  OnOrder
  j351
  1
  `<j351>600</j351>`

##### P.26.39a Quantity in shipment proximity

An ONIX code which specifies the precision of the stock quantity in a shipment. Optional, and non-repeating.

  Fixed length, two digits
  List 215
  Proximity
  x502
  0…1
  `<Proximity>07</Proximity>` (More than)

##### P.26.40 Shipment expected date

The date on which a stock shipment is expected. Mandatory in each occurrence of the <OnOrderDetail> composite, and non-repeating.

  As specified by the value in the dateformat attribute, or the default of YYYYMMDD if the attribute is missing
  ExpectedDate
  j302
  1
  dateformat
  `<ExpectedDate>20060227</ExpectedDate>`

##### End of On order detail composite

##### Velocity composite

An optional group of data elements which together specify the rate of stock depletion – or equally, a rate of accumulation of backorders. Repeatable if the rate of depletion is specified using more than one metric (eg specifying both a minimum and maximum daily sale).

  Velocity
  velocity
  0…n

##### P.26.40a Velocity metric

An ONIX code that specifies how the rate of stock depletion is measured. Mandatory within the <Velocity> composite, and non-repeating.

  Fixed length, two digits
  List 216
  VelocityMetric
  x504
  1
  `<x504>02</x504>` (Mean daily sale)

##### P.26.40b Velocity rate

The stock depletion rate (as a number of copies, rounded to the nearest integer), measured according to the metric in <VelocityMetric>.

  Positive or negative integer or zero, suggested maximum length 7 digits. Negative numbers indicate returns exceed the fulfillment rate
  Rate
  x505
  1
  `<Rate>315</Rate>`

##### P.26.40c Velocity rate proximity

An ONIX code which specifies the precision of the rate of stock depletion. Optional, and non-repeating.

  Fixed length, two digits
  List 215
  Proximity
  x502
  0…1
  `<Proximity>06</Proximity>` (More than)

##### End of Velocity composite

##### End of Stock quantity composite

##### P.26.41 Pack or carton quantity

The quantity in each carton or binder’s pack in stock currently held by the supplier. Optional and non-repeating.

Note that orders do not have to be aligned with multiples of the pack quantity, but such orders may be more convenient to handle.

  Positive integer, suggested maximum length 4 digits
  PackQuantity
  j145
  0…1
  `<PackQuantity>24</PackQuantity>`

##### P.26.41a Pallet quantity

The quantity (number of copies) on each complete pallet in stock currently held by the supplier. Optional and non-repeating. Of course, orders do not have to be aligned to the pallet quantity, but for bulk orders, it may be useful to know how many pallets will be required for a delivery.

  Positive integer, suggested maximum length 7 digits
  PalletQuantity
  x545
  0…1
  `<PalletQuantity>960</PalletQuantity>`

##### P.26.41b Minimum order quantity

The minimum quantity of the product that may be ordered in a single order placed with the supplier. Optional. If omitted, any number may be ordered.

If supplied without a succeeding Minimum initial order quantity, the Minimum order quantity applies to all orders for the product. If followed by a Minimum initial order quantity, the Minimum order quantity applies to the second and subsequent orders for the product.

  Positive integer, suggested maximum length 4 digits
  OrderQuantityMinimum
  x532
  0…1
  `<x532>6</x532>`

##### P.26.41c Minimum initial order quantity

The minimum quantity of the product that may be ordered in the very first order placed for a new product with the supplier, where it is different from the Minimum order quantity for subsequent orders. Optional, but when supplied, it must be preceded by a Minimum order quantity that applies to second and subsequent orders.

  Positive integer, suggested maximum length 4 digits
  OrderQuantityMinimum
  x532
  0…1
  `<x532>12</x532>`

##### P.26.41d Order quantity multiple

The order quantity multiple that must be used in any order for the product placed with the supplier. Optional, but where supplied, must be preceded by at least one <OrderQuantityMinimum> element. For example with a minimum order quantity of 6 and a multiple of 4, orders for 6, 10 or 14 copies are acceptable, but orders for fewer than 6, or for 7, 8, 9 or 11 copies are not. If omitted, the minimum or any larger quantity may be ordered.

  Positive integer, suggested maximum length 4 digits
  OrderQuantityMultiple
  x533
  0…1
  `<OrderQuantityMultiple>4</OrderQuantityMultiple>`

##### P.26.42 Unpriced item type

An ONIX code which specifies the product is free of charge, or a reason why a price is not sent. If code value 02 is used to send advance information without giving a price, the price must be confirmed as soon as possible. Optional and non-repeating, but required if the <SupplyDetail> composite does not carry a price.

Use here in preference to P.26.70b when the product is available only under free of charge or unpriced terms from the supplier.

  Fixed length, two digits
  List 57
  UnpricedItemType
  j192
  0…1
  `<j192>01</j192>` (Free of charge)

##### Price composite

An optional group of data elements which together specify a unit price, repeatable in order to specify multiple prices. Each <SupplyDetail> composite must include either one or more prices, or a single <UnpricedItemType> element (see P.26.42).

Where multiple prices are specified for a product, each price option should specify a distinct combination of its terms of trade and the group of end customers it is applicable to, any relevant price conditions, periods of time, currency and territory etc, so that the data recipient can clearly select the correct pricing option. If, under a particular combination, the product is free of charge or its price is not yet set, an <UnpricedItemType> element (P.26.70b) must be used in place of a <PriceAmount>. Each pricing option may optionally be given an identifier for use in subsequent revenue reporting or for other internal purposes.

  Price
  price
  0…n

##### Price identifier composite

An optional group of elements that provide an identifier, reference or persistent label for a particular price. For products that may be available at potentially many different prices, to different groups of purchasers or under different terms and conditions, this identifier may then be used in subsequent revenue reporting to specify which price the product was traded at.

Note that the price identifier will always be proprietary and must be unique across multiple pricing options for one product, but need not be unique across all products, nor need it be the same across all products offered at the same price point or under the same terms.

The composite is repeatable in order to provide multiple identifiers for the same price.

  PriceIdentifier
  priceidentifier
  0…n

##### P.26.42a Price identifier type code

An ONIX code identifying the scheme from which the identifier in the <IDValue> element is taken. Mandatory in each occurrence of the <PriceIdentifier> composite, and non-repeating.

There is no particular public ‘standard’ for price identifiers, so at present only proprietary identifiers may be specified.

  Fixed-length text, two digits
  List 217
  PriceIDType
  x506
  1
  `<x506>01<x506>` (Proprietary)

##### P.26.42b Identifier type name

A name which identifies a proprietary identifier scheme (ie a scheme which is not a standard and for which there is no individual ID type code). Must be included when, and only when, the code in the <PriceIDType> element indicates a proprietary scheme, eg a publisher’s own identifier scheme. Optional and non-repeating.

  Variable length text, suggested maximum length 100 characters
  IDTypeName
  b233
  0…1
  language
  `<IDTypeName>PRHG PUUID</IDTypeName>`

##### P.26.42c Identifier value

An identifier of the type specified in the <PriceIDType> element. Mandatory in each occurrence of the <PriceIdentifier> composite, and non-repeating.

  According to the identifier type specified in <PriceIDType>
  IDValue
  b244
  1
  `<b244>f47ac10b-58cc-4372-a567-0e02b2c3d479</b244>` (from a scheme using a UUID)

##### End of Price identifier composite

##### P.26.43 Price type code

An ONIX code indicating the type of the price in the <PriceAmount> field within the <Price> composite. Mandatory unless a <DefaultPriceType> has been specified in the message header, and non-repeating.

  Fixed length, two digits
  List 58
  PriceType
  x462
  0…1
  `<PriceType>21</PriceType>` (Pre-publication RRP excluding tax)

##### P.26.44 Price type qualifier

An ONIX code which further specifies the type of price, eg member price, reduced price when purchased as part of a set. Optional and non-repeating.

  Fixed length, two digits
  List 59
  PriceQualifier
  j261
  0…1
  `<PriceQualifier>01</PriceQualifier>` (Member/subscriber price)

##### P.26.44a Digital product technical protection (Price)

An ONIX code specifying whether a digital product has DRM or other technical protection features that form or enforce part of the commercial offer for a product. Optional, and repeatable if a product has two or more kinds of protection.

The Digital product technical protection element is also present in Group P.3. Use here where a single product is available under multiple commercial offers with differing Price constraints, to indicate whether the constraints are enforced via technical protection measures.

  Fixed length, two digits
  List 144
  EpubTechnicalProtection
  x317
  0…n
  `<x317>03</x317>` (Has digital watermarking)
  ‘Epub’ (‘e-publication’) here and in other element names below refers to any digital product, and has no necessary link with the .epub file format developed by the IDPF

##### Price constraint composite

An optional group of data elements which together describe a contractual term or constraint (or the absence of such a constraint) that forms part of the commercial offer for a product. Repeatable in order to describe multiple constraints on usage.

The Price constraint composite has the same structure as <EpubUsageConstraint>. Use <EpubUsageConstraint> for constraints that limit the user experience of the product, whether or not they are enforced by technical protection measures (DRM). Use <PriceConstraint> where a single product is available under multiple terms and conditions (ie multiple commercial offers for the same product which differ in their Price constraints, and whether or not they are enforced by DRM).

  PriceConstraint
  priceconstraint
  0…n

##### P.26.44b Price constraint type

An ONIX code specifying a type of commercial term or constraint forming part of the commercial offer for a digital product. Mandatory in each occurrence of the <PriceConstraint> composite, and non-repeating.

  Fixed length, two digits
  List 230
  PriceConstraintType
  x529
  1
  `<PriceConstraintType>06</PriceConstraintType>` (lend to library patrons)

##### P.26.44c Price constraint status

An ONIX code specifying the status of a contractual term or constraint, eg permitted without limit, permitted with limit, prohibited. Mandatory in each occurrence of the <PriceConstraint> composite, and non-repeating.

  Fixed length, two digits
  List 146
  PriceConstraintStatus
  x530
  1
  `<PriceConstraintStatus>02</PriceConstraintStatus>` (Allowed with limits)

##### Price constraint limit composite

An optional and repeatable group of data elements which together specify a quantitative limit on a particular type of contractual term or constraint.

  PriceConstraintLimit
  priceconstraintlimit
  0…n

##### P.26.44d Usage quantity

A numeric value representing the maximum permitted quantity or limit of a particular type of constraint. Mandatory in each occurrence of the <PriceConstraintLimit> composite, and non-repeating.

  Positive real number, with explicit decimal point when required, or zero, as appropriate for the units specified in <PriceConstraintUnit>
  Quantity
  x320
  1
  `<Quantity>2</Quantity>`

##### P.26.44e Usage unit

An ONIX code for a unit in which a maximum permitted quantity or limit is stated. Mandatory in each occurrence of the <PriceConstraintLimit> composite, and non-repeating.

  Fixed length, two digits
  List 147
  PriceConstraintUnit
  x531
  1
  `<x531>07</x531>` (Concurrent users)

##### End of Price constraint limit composite

##### End of Price constraint composite

##### Digital product license composite (price)

An optional and non-repeatable composite carrying the name or title of the usage license forming part of the commercial offer for the product, and a link to the license terms in eye-readable or machine-readable form.

  EpubLicense
  epublicense
  0…1

##### P.26.44f to P.26.44i: elements in the Digital product license composite

Elements P.26.44f to P.26.44i are identical to P.3.20a to P.3.20d in the Digital product license composite in Group P.3.

Note that <EpubLicenseDate> cannot be included here.

##### End of Digital product license composite (price)

##### P.26.45 Price type description

Free text which further describes the price type, qualifier, constraints and other parameters of the price. Optional, and repeatable if parallel descriptions are provided in multiple languages. The language attribute is optional for a single instance of <PriceTypeDescription>, but must be included in each instance if <PriceTypeDescription> is repeated in multiple languages. In the Netherlands and elsewhere, when the <PriceQualifier> code identifies a ‘voucher price’, the <PriceTypeDescription> should give the ‘EAN action number’ that identifies the offer.

  Variable length text, suggested maximum length 200 characters
  PriceTypeDescription
  j262
  0…n
  language
  `<j262>When purchased as part of a three-item set with…</j262>`

##### P.26.46 Unit of pricing

An ONIX code indicating the unit of product which is the basis for the price carried in an occurrence of the <Price> composite. Optional and non-repeating. Where the price applies to a copy of the whole product, this field is normally omitted.

  Fixed length, two digits
  List 60
  PricePer
  j239
  0…1
  `<PricePer>01</PricePer>` (Per page [for printed loose-leaf content only])

##### Price condition composite

An optional group of data elements which together specify a condition relating to a price, repeatable in order to specify multiple conditions.

  PriceCondition
  pricecondition
  0…n

##### P.26.47 Price condition type

An ONIX code identifying a type of price condition. Mandatory in each occurrence of the <PriceCondition> composite, and non-repeating.

  Fixed length, two digits
  List 167
  PriceConditionType
  x463
  1
  `<x463>02</x463>` (Must also purchase updates)

##### Price condition quantity composite

An optional and repeatable group of data elements which together specify a price condition quantity, for example a minimum number of copies, or a period of time for which updates are supplied or must be purchased.

  PriceConditionQuantity
  priceconditionquantity
  0…n

##### P.26.48 Price condition quantity type

An ONIX code identifying a type of price condition quantity. Mandatory in each occurrence of the <PriceConditionQuantity> composite, and non-repeating.

  Fixed length, two digits
  List 168
  PriceConditionQuantityType
  x464
  1
  `<x464>01</x464>` (Time period)

##### P.26.49 Quantity

A quantity associated with a price condition. Mandatory in each occurrence of the <PriceConditionQuantity> composite, and non-repeating.

  Positive real number, here normally but not necessarily an integer, or zero, as appropriate for the units specified in <QuantityUnit>
  Quantity
  x320
  1
  `<Quantity>12</Quantity>`

##### P.26.50 Quantity unit code

An ONIX code value specifying the unit in which a price condition quantity is stated. Mandatory in each occurrence of the <PriceConditionQuantity> composite, and non-repeating.

  Fixed length, two digits
  List 169
  QuantityUnit
  x466
  1
  `<QuantityUnit>09</QuantityUnit>` (Months)

##### End of Price condition quantity composite

##### Product identifier composite (price condition)

A group of data elements which together define an identifier of a product in accordance with a specified scheme. Optional, and used here if and only if <PriceConditionType> has a value that requires specification of a linked product upon which the price is dependent. Repeatable with different identifiers for the same product.

  ProductIdentifier
  productidentifier
  0…n

##### P.26.50a to P.26.50c: elements in the Product identifier composite

Elements P.26.50a to P.26.50c in the <ProductIdentifier> composite are identical to elements P.2.1 to P.2.3 as specified in Group P.2 (and to elements P.23.2 to P.23.4 in Group P.23).

##### End of Product identifier composite (price condition)

##### End of Price condition composite

##### P.26.51 Minimum qualifying order quantity

The minimum number of copies which must be ordered to obtain the price carried in an occurrence of the <Price> composite. Optional and non-repeating. If the field is present, the price is a quantity price (and only whole multiples of the qualifying quantity may be ordered at that price). If the field is omitted, the price applies to a single unit.

Note the similarity between <MinimumOrderQuantity> and <OrderQuantityMinimum> in P.26.41b: only <MinimumOrderQuantity> has an effect on the specification of <Price>. Use of <MinimumOrderQuantity> is close in effect to a multi-item trade pack (see <ProductComposition>).

  Positive integer, suggested maximum length 4 digits
  MinimumOrderQuantity
  j263
  0…1
  `<MinimumOrderQuantity>50</MinimumOrderQuantity>`

##### Batch bonus composite

A repeatable group of data elements which together specify a batch bonus, ie a quantity of free copies which are supplied (typically to a reseller) with a certain order quantity. The <BatchBonus> composite is optional.

  BatchBonus
  batchbonus
  0…n

##### P.26.52 Batch quantity

The number of copies which must be ordered to obtain the free copies specified in <FreeQuantity>. Mandatory in each occurrence of the <BatchBonus> composite, and non-repeating.

  Positive integer, suggested maximum length 4 digits
  BatchQuantity
  j264
  1
  `<j264>20</j264>`

##### P.26.53 Free quantity

The number of free copies which will be supplied with an order for the batch quantity specified in the <BatchQuantity> field. Mandatory in each occurrence of the <BatchBonus> composite, and non-repeating.

  Positive integer, suggested maximum length 4 digits
  FreeQuantity
  j265
  1
  `<FreeQuantity>1</FreeQuantity>`

##### End of Batch bonus composite

##### Discount code composite

An optional group of data elements which together define a discount code from a specified scheme, and repeatable to allow different discount code schemes to be supported without defining additional data elements. For prices specified as Agency prices in <PriceType>, this code is interpreted as a ‘commission code’.

A discount code is generally used when the exact percentage discount (or commission, in an agency business model) that a code represents may vary from reseller to reseller (or from agent to agent), or if terms must be kept confidential. If the discount (or commission) is the same for all resellers (or agents) and need not be kept confidential, use <Discount> and <DiscountPercent> instead.

  DiscountCoded
  discountcoded
  0…n

##### P.26.54 Discount code type code

An ONIX code identifying the scheme from which the value in the <DiscountCode> element is taken. Mandatory in each occurrence of the <DiscountCoded> composite, and non-repeating.

  Fixed length, two digits
  List 100
  DiscountCodeType
  j363
  1
  `<j363>02</j363>` (Proprietary)

##### P.26.55 Discount code type name

A name which identifies a proprietary discount code scheme. Must be included when, and only when the code in the <DiscountCodeType> element indicates a proprietary scheme, eg a wholesaler’s own code. Optional and non-repeating.

  Variable length text, suggested maximum length 100 characters
  DiscountCodeTypeName
  j378
  0…1
  language
  `<j378>IngramDC</j378>`

##### P.26.56 Discount code value

A discount or commission code from the scheme specified in the <DiscountCodeType> element. Mandatory in each occurrence of the <DiscountCoded> composite, and non-repeating.

  According to the scheme specified in <DiscountCodeType>
  DiscountCode
  j364
  1
  `<DiscountCode>AHACP033</DiscountCode>`

##### End of Discount code composite

  recommended retail price and discount code (typical ‘reseller’ business model)
  using Reference names |
  --- | ---
  `<Price>` |
  `<PriceType>02</PriceType>` |
  `<DiscountCoded>` |
  `<DiscountCodeType>01</DiscountCodeType>` |
  `<DiscountCode>AHACP033</DiscountCode>` |
  `</DiscountCoded>` |
  `<PriceAmount>7.99</PriceAmount>` |
  `<CurrencyCode>GBP</CurrencyCode>` |
  `</Price>` |

  using Short tags |
  --- | ---
  `<price>` |
  `<x462>02</x462>` | RRP inc tax
  `<discountcoded>` |
  `<j363>01</j363>` | BIC discount group code
  `<j364>AHACP033</j364>` |
  `</discountcoded>` |
  `<j151>7.99</j151>` |
  `<j152>GBP</j152>` |
  `</price>` |

  listing an ‘agency’ price and proprietary commission code with <DiscountCoded>
  using Reference names |
  --- | ---
  `<Price>` |
  `<PriceType>41</PriceType>` |
  `<DiscountCoded>` |
  `<DiscountCodeType>05</DiscountCodeType>` |
  `<DiscountCodeTypeName>XYZ Books Agency Rate List</DiscountCodeTypeName>` |
  `<DiscountCode>A5</DiscountCode>` |
  `</DiscountCoded>` |
  `<PriceAmount>12.99</PriceAmount>` |
  `<CurrencyCode>USD</CurrencyCode>` |
  `</Price>` |

  using Short tags |
  --- | ---
  `<price>` |
  `<x462>41</x462>` | Publisher’s retail price ex tax
  `<discountcoded>` |
  `<j363>05</j363>` | Proprietary commission code
  `<j378>XYZ Books Agency Rate List</j378>` | Name of codelist
  `<j364>A5</j364>` | Commission rate code
  `</discountcoded>` |
  `<j151>12.99</j151>` |
  `<j152>USD</j152>` |
  `</price>` |

##### Discount composite

An optional group of data elements which together define a discount either as a percentage or as an absolute amount. Repeatable in order to specify a more complex arrangement such as a progressive or tiered discount. Used only when an ONIX message is sent within the context of a specific trading relationship.

  Discount
  discount
  0…n

##### P.26.57 Discount type

An ONIX code identifying a discount type or reason. Optional, and non-repeating. When omitted, the default is a simple or rising discount (the discount is applied to all units in a qualifying order).

  Fixed length, two digits
  List 170
  DiscountType
  x467
  0…1

##### P.26.58 Quantity

A minimum order quantity required to qualify for a specified discount. Optional, and non-repeating. Where omitted, the discount applies regardless of the order quantity (ie the minimum qualifying order quantity is 1).

  Positive number, here necessarily an integer, or zero. Suggested maximum length 7 digits
  Quantity
  x320
  0…1
  `<Quantity>12</Quantity>`

##### P.26.58a To Quantity

A maximum order quantity eligible for a specified discount, used only in the case of ‘progressive’ discounts. Optional, but where used, must be preceded by a minimum qualifying order quantity (even if that minimum is 1). For the special case where there is no maximum (ie in the repeat of the <Discount> composite that specifies the highest progressive discount), use zero.

  Positive number, here necessarily an integer, or zero. Suggested maximum length 7 digits
  ToQuantity
  x514
  0…1
  `<ToQuantity>25</ToQuantity>`

##### P.26.59 Discount percentage

A discount percentage applicable to the price carried in an occurrence of the <Price> composite. Optional and non-repeating; but either <DiscountPercent> or <DiscountAmount> or both must be present in each occurrence of the <Discount> composite.

  Real number between zero and 100 (inclusive), including explicit decimal point when required, suggested maximum length 6 characters
  DiscountPercent
  j267
  0…1
  `<DiscountPercent>37.5</DiscountPercent>`

##### P.26.60 Discount amount

A discount expressed as an absolute amount per copy. Optional and non-repeating; but either <DiscountPercent> or <DiscountAmount> or both must be present in each occurrence of the <Discount> composite. Note that when both are present, they represent two different expressions of the same discount – the discounts are not cumulative.

  Positive real number, with explicit decimal point when required, or zero, suggested maximum length 12 characters
  DiscountAmount
  x469
  0…1
  `<DiscountAmount>4.59</DiscountAmount>`

##### End of Discount composite

  Simple discount: a discount of 20% is applied irrespective of the number of copies ordered
  using Reference names |
  --- | ---
  `<Discount>` |
  `<DiscountPercent>20</DiscountPercent>` |
  `</Discount>` |

  using Short tags |
  --- | ---
  `<discount>` |
  `<j267>20</j267>` | no minimum quantity for qualification
  `</discount>` |

  Rising discount with a break at 10 copies: if 15 copies are ordered, a discount of 30% is applied to the price of all 15 copies
  using Reference names |
  --- | ---
  `<Discount>` |
  `<DiscountPercent>20</DiscountPercent>` |
  `</Discount>` |
  `<Discount>` |
  `<Quantity>11</Quantity>` |
  `<DiscountPercent>30</DiscountPercent>` |
  `</Discount>` |

  using Short tags |
  --- | ---
  `<discount>` |
  `<j267>20</j267>` | lower discount applies if number of copies
  `</discount>` | ordered does not qualify for higher discount
  `<discount>` |
  `<x320>11</x320>` | higher overall discount applies if number of
  `<j267>30</j267>` | copies qualifies (if 11 or more copies ordered)
  `</discount>` |

  Progressive discount with a break at 10 copies: if 15 copies are ordered, a discount of 30% is applied only to the last five copies, and the discount applied to the first ten is only 20%. The aggregate discount on the order for 15 items is around 23%
  using Reference names |
  --- | ---
  `<Discount>` |
  `<DiscountType>03</DiscountType>` |
  `<Quantity>1</Quantity>` |
  `<ToQuantity>10</ToQuantity>` |
  `<DiscountPercent>20</DiscountPercent>` |
  `</Discount>` |
  `<Discount>` |
  `<DiscountType>03</DiscountType>` |
  `<Quantity>11</Quantity>` |
  `<ToQuantity>0</ToQuantity>` |
  `<DiscountPercent>30</DiscountPercent>` |
  `</Discount>` |

  using Short tags |
  --- | ---
  `<discount>` |
  `<x467>03</x467>` | progressive discount
  `<x320>1</x320>` | lower discount applies
  `<x514>10</x514>` | to first through 10th copies
  `<j267>20</j267>` |
  `</discount>` |
  `<discount>` |
  `<x467>03</x467>` | progressive discount
  `<x320>11</x320>` | higher discount applies only
  `<x514>0</x514>` | to 11th and all subsequent copies
  `<j267>30</j267>` |
  `</discount>` |

##### P.26.61 Price status

An ONIX code which specifies the status of a price. Optional and non-repeating. If the field is omitted, the default ‘unspecified’ will apply.

  Fixed length, two digits
  List 61
  PriceStatus
  j266
  0…1
  `<PriceStatus>01</PriceStatus>` (Provisional)

##### P.26.62 Price amount

The amount of a price, dependent on the <PriceType> and other elements present within the <Price> composite. Optional and non-repeating, but each occurrence of the <Price> composite must include either a <PriceAmount> or a <PriceCoded> composite, with optional tax details, or an <UnpricedItemType> element. Note that free-of-charge products must use <UnpricedItemType> rather than a zero price.

  Positive real number, with explicit decimal point when required, suggested maximum length 12 characters
  PriceAmount
  j151
  0…1
  `<j151>18.99</j151>`

##### Price coded composite

An optional group of data elements to carry a price that is expressed as one of a discrete set of price points, tiers or bands, rather than actual currency amounts. Each occurrence of the <Price> composite must include either a <PriceAmount> or a <PriceCoded> composite, with optional tax details, or an <UnpricedItemType> element.

  PriceCoded
  pricecoded
  0…1

##### P.26.63 Price code type code

An ONIX code identifying the scheme from which the value in the <PriceCode> element is taken. Mandatory in an occurrence of the <PriceCoded> composite, and non-repeating.

  Fixed length, two digits
  List 179
  PriceCodeType
  x465
  1
  `<PriceCodeType>01</PriceCodeType>` (Proprietary)

##### P.26.64 Price code type name

A name which identifies a proprietary price code type. Must be used when, and only when the code in the <PriceCodeType> element indicates a proprietary scheme, eg a retailer’s price banding scheme. Optional and non-repeating.

  Variable length text, suggested maximum length 100 characters
  PriceCodeTypeName
  x477
  0…1
  language
  `<x477>Retailer Inc. Ebook Tier Number</x477>`

##### P.26.65 Price code

A price code from the scheme specified in the <PriceCodeType> element. Mandatory in each occurrence of the <PriceCoded> composite, and non-repeating.

  According to the scheme specified in <PriceCodeType>
  PriceCode
  x468
  1
  `<PriceCode>07a</PriceCode>`

##### End of Price coded composite

  specifying a price tier
  using Reference names |
  --- | ---
  `<PriceCoded>` |
  `<PriceCodeType>01</PriceCodeType>` |
  `<PriceCodeTypeName>EbookVendor.com tier list</PriceCodeTypeName>` |
  `<PriceCode>7a</PriceCode>` |
  `</PriceCoded>` |

  using Short tags |
  --- | ---
  `<pricecoded>` |
  `<x465>01</x465>` | Proprietary code list
  `<x477>EbookVendor.com tier list</x477>` |
  `<x468>7a</x468>` | List indicates real price associated with tier 7a
  `</pricecoded>` |

##### Tax composite

A repeatable group of data elements which together specify tax included within a price amount. Optional, and used only when <PriceType> indicates an inc-tax price. For items to which different taxes or tax rates apply (eg mixed media products in the UK which are partly taxed at standard rate and partly at zero rate), the composite is repeated for each separate tax or tax rate. Although only one of <TaxRatePercent> or <TaxAmount> is mandatory within the composite, it is recommended that all tax elements in the composite should be explicitly populated.

If the tax regime requires separate tax rates and amounts linked explicitly to particular product parts (eg in Germany), the <ProductIdentifier> composite may be included in each <Tax> composite. Where tax is payable on multiple product parts, each should have its own instance of the <Tax> composite.

  Tax
  tax
  0…n

##### Product identifier composite (product part)

Optional and repeatable group of data elements which together specify one or more identifiers of a product part in accordance with a specified scheme, used here only when it is necessary to link a particular tax rate or amount with a particular product part contained within a multiple-item product or a trade pack. All identifiers included here must also be included in an instance of <ProductPart>, and where multiple identifiers are provided in any one occurrence of the <Tax> composite, they must all identify the same product part.

  ProductIdentifier
  productidentifier
  0…n

##### P.26.65a to P.26.65c: elements in the Product identifier composite

Elements P.26.65a to P.26.65c in the <ProductIdentifier> composite are identical to P.4.2 to P.4.4 as specified in Group P.4.

##### End of Product identifier composite (product part)

##### P.26.65d Price part description

A name or description which identifies a part of the product price that is subject to the relevant tax, for example a product part that may be taxed with a particular tax rate or amount (separately from other components), or a levy added to a product price that is itself subject to tax. Optional, and repeatable to provide parallel descriptive text in multiple languages. The language attribute is optional for a single instance of <PricePartDescription>, but must be included in each instance if <PricePartDescription> is repeated.

  Variable length text, suggested maximum length 100 characters
  PricePartDescription
  x535
  0…n
  language
  `<x535 language="fre">Eco-mobilier</x535>`

##### P.26.66 Tax type

An ONIX code identifying a tax type, eg VAT. Optional, and non-repeating.

  Fixed length, two digits
  List 171
  TaxType
  x470
  0…1
  `<TaxType>01</TaxType>` (VAT)

##### P.26.67 Tax rate code

An ONIX code which specifies a tax rate. Optional and non-repeating.

  Fixed length, one letter
  List 62
  TaxRateCode
  x471
  0…1
  `<x471>Z</x471>` (Zero-rated)

##### P.26.68 Tax rate percent

A tax rate expressed numerically as a percentage. Optional and non-repeating; but either <TaxRatePercent> or <TaxAmount> or both must be present in each occurrence of the <Tax> composite.

  Real number between zero and 100 (inclusive), with explicit decimal point when required, suggested maximum length 7 characters
  TaxRatePercent
  x472
  0…1
  `<TaxRatePercent>17.5</TaxRatePercent>`

##### P.26.69 Amount of price taxable

The amount of the unit price of the product, excluding tax, which is taxable at the rate specified in an occurrence of the <Tax> composite. Optional and non-repeating; but required if tax is charged on part of the price. Omission of this element implies that tax is charged on the full amount of the price.

  Positive real number, with explicit decimal point when required, suggested maximum length 12 characters
  TaxableAmount
  x473
  0…1
  `<x473>10.64</x473>`

##### P.26.70 Tax amount

The amount of tax chargeable at the rate specified in an occurrence of the <Tax> composite. Optional and non-repeating; but either <TaxRatePercent> or <TaxAmount> or both must be present in each occurrence of the <Tax> composite.

  Positive real number, with explicit decimal point when required, or zero, suggested maximum length 12 characters
  TaxAmount
  x474
  0…1
  `<TaxAmount>1.86</TaxAmount>`

##### End of Tax composite

##### P.26.70a Tax exempt flag

An empty element that identifies a product price as being specifically exempted from tax. Optional, and used only when <PriceType> indicates an exc-tax price.

Note that tax exempt status is rare: it applies in only a very few countries. Tax exempt is distinct from the case where tax details are not specified (as is the case with most North American Prices) and also distinct from the case where tax is levied at zero percent (as is the case for physical books in the UK, for example).

  XML empty element
  TaxExempt/
  x546/
  0…1
  `<TaxExempt/>`

##### P.26.70b Unpriced item type

An ONIX code which specifies that the product is free of charge, or a reason why a price amount or price code is not sent. If code value 02 is used to send advance information without giving a price, the price must be confirmed as soon as possible. Optional and non-repeating, but required if the <Price> composite does not carry a price amount or price code.

Use here in preference to P.26.42 when the product is available under a variety of priced and unpriced terms from the same supplier.

  Fixed length, two digits
  List 57
  UnpricedItemType
  j192
  0…1
  `<UnpricedItemType>01</UnpricedItemType>` (Free of charge)

##### P.26.71 Currency code

An ONIX code identifying the currency in which all monetary amounts in an occurrence of the <Price> composite are stated. Optional and non-repeating, but required if the currency is not the default currency for the message (this default may be set in <DefaultCurrencyCode> – but doing so is deprecated). All ONIX messages must include an explicit statement of the currency used for any prices. To avoid any possible ambiguity, it is strongly recommended that the currency should be stated here for each individual price.

  Fixed length, three letters, based on ISO 4217. Note that ISO 4217 specifies that currency codes shall be sent as upper case only
  List 96
  CurrencyCode
  j152
  0…1
  `<j152>ZAR</j152>` (South African Rand)

##### Price territory composite

A group of data elements which together identify a territory within which the price stated in an occurrence of the <Price> composite is applicable. Optional and non-repeating.

For valid combinations of <CountriesIncluded>, <RegionsIncluded> etc within <Territory>, see the notes describing the use of <Territory> within Group P.21.

Additional guidance on the description of price territories in ONIX 3.0 and 3.1 will be found in a separate document ONIX for Books Product Information Message: How to Specify Markets and Suppliers in ONIX 3.

  Territory
  territory
  0…1

##### P.26.72 Countries included

One or more ONIX codes identifying countries included in the territory. Successive codes must be separated by spaces. Optional and non-repeating, but either <CountriesIncluded> or <RegionsIncluded> is mandatory in each occurrence of the <Territory> composite.

  One or more fixed-length codes based on ISO 3166-1, each consisting of two upper case letters, and with successive codes being separated by spaces. Suggested maximum length 750 characters. Note that ISO 3166-1 specifies that country codes shall be sent as upper case only
  List 91
  CountriesIncluded
  x449
  0…1
  `<CountriesIncluded>US CA</CountriesIncluded>` (USA and Canada)

##### P.26.73 Regions included

One or more ONIX codes identifying regions included in the territory. A region is an area which is not a country, but which is precisely defined in geographical terms, eg World, Northern Ireland, Australian Capital Territory. Successive codes must be separated by spaces. Optional and non-repeating, but either <CountriesIncluded> or <RegionsIncluded> is mandatory in each occurrence of the <Territory> composite.

Note that if used, the ‘WORLD’ region code cannot be combined with other region codes.

  One or more variable-length codes, each consisting of upper case letters, with or without a hyphen and further upper case letters or digits, and with successive codes being separated by spaces. Suggested maximum length 750 characters
  List 49 Where possible and appropriate, country subdivision codes are derived from the UN LOCODE scheme based on ISO 3166-2
  RegionsIncluded
  x450
  0…1
  `<x450>WORLD</x450>` (Whole world)
  `<x450>US-CA</x450>` (California)

##### P.26.74 Countries excluded

One or more ONIX codes identifying countries excluded from the territory. Successive codes must be separated by spaces. Optional and non-repeating, and can only occur if the <RegionsIncluded> element is also present and includes a supra-national region code such as ‘WORLD’.

  One or more fixed-length codes based on ISO 3166-1, each consisting of two upper case letters, and with successive codes being separated by spaces. Suggested maximum length 750 characters. Note that ISO 3166-1 specifies that country codes shall be sent as upper case only
  List 91
  CountriesExcluded
  x451
  0…1
  `<CountriesExcluded>US CA</CountriesExcluded>` (Excludes USA and Canada)

##### P.26.75 Regions excluded

One or more ONIX codes identifying regions excluded from the territory. Successive codes must be separated by spaces. Optional and non-repeating, and can only occur if the <CountriesIncluded> element is also present (and specifies countries of which the excluded regions are a part), or if <Regions Included> is present and includes a supra-national region code (such as ‘WORLD’).

  One or more variable-length codes, each consisting of upper case letters, with or without a hyphen and further upper case letters or digits, and with successive codes being separated by spaces. Suggested maximum length 750 characters
  List 49 Where possible and appropriate, country subdivision codes are derived from the UN LOCODE scheme based on ISO 3166-2
  RegionsExcluded
  x452
  0…1
  `<x452>GB-ENG GB-SCT GB-WLS</x452>` (Excludes England, Wales and Scotland – and therefore includes Northern Ireland)

##### End of Price territory composite

  a simple <Price> composite, with a single global price
  using Reference names |
  --- | ---
  `<Price>` |
  `<PriceType>01</PriceType>` | RRP excluding tax
  `<PriceAmount>15.99</PriceAmount>` |
  `<CurrencyCode>USD</CurrencyCode>` | US$
  `<Territory>` | Price applies
  `<RegionsIncluded>WORLD</RegionsIncluded>` | throughout world
  `</Territory>` |
  `<PrintedOnProduct>02</PrintedOnProduct>` | Is on product
  `<PositionOnProduct>01</PositionOnProduct>` | On back cover
  `</Price>` |

  using short tags |
  --- | ---
  `<price>` |
  `<x462>01</x462>` |
  `<j151>15.99</j151>` |
  `<j152>USD</j152>` |
  `<territory>` |
  `<x450>WORLD</x450>` |
  `</territory>` |
  `<x301>02</x301>` |
  `<x313>01</x313>` |
  `</price>` |

##### Comparison product price composite

Optional group of data elements that together define a price for a directly comparable product, to facilitate supply of price data to retailers who do not receive a full ONIX record for that comparable product. This is primarily intended for use within a <Product> record for a digital product, to provide a price for a comparable physical product. The composite is repeatable in order to define multiple comparison prices.

Those using this composite should be wary of the volatile nature of product prices: special note should be taken of the risk of stale data being stored in data recipients’ systems when prices for the comparison product are updated, as those updates to the comparison product may occur outside the context of the main product being described in the <Product> record. Because of this, ONIX suppliers are cautioned of the risk of contradictory data in separate data feeds. This composite should not be supplied unless specifically requested by a particular recipient.

The inclusion of a comparison price in itself implies nothing about the availability or status of the comparable product. However, there may be legal requirements in particular territories relating to the use of comparison prices in promotion that users of this data must comply with.

Note that the comparison product price composite does not include all the features of the <Price> composite: for example, <PriceQualifier> is not included. Thus data providers should ensure that any conditions attached to the comparison product price are such that it is directly comparable to the price of the main product being described.

  ComparisonProductPrice
  comparisonproductprice
  0…n

##### Product identifier composite (comparison product)

A group of data elements which together define an identifier for a comparison product in accordance with a specified scheme. At least one <ProductIdentifier> composite is mandatory within an occurrence of <ComparisonProductPrice>, to identify the product to which the comparison price applies. Repeatable with different identifiers for the same product.

It is strongly advised that the relationship between the comparison product and the product described in the <Product> record is defined in a <RelatedProduct> composite in P.23 – typically this might be <ProductRelationCode> 06 (related product is alternative format with same content as product) and may in many circumstances also be 13 (product is e-publication based on related product).

  ProductIdentifier
  productidentifier
  1…n

##### P.26.77 to P.26.79: elements in the Product identifier composite

Elements P.26.77 to P.26.79 in the <ProductIdentifier> composite are identical to elements P.2.1 to P.2.3 as specified in Group P.2 (and to elements P.23.2 to P.23.4 in Group P.23).

##### End of Product identifier composite (comparison product)

##### P.26.80 Price type code

An ONIX code indicating the type of the comparison price in the <PriceAmount> element within the <ComparisonProductPrice> composite. Mandatory, unless a <DefaultPriceType> has been specified in the message header although use of such a default is deprecated. Non-repeating.

  Fixed length, two digits
  List 58
  PriceType
  x462
  0…1
  `<PriceType>01</PriceType>` (RRP excluding tax)

##### P.26.81 Price amount

The amount of the comparison product price. Mandatory and non-repeating within any occurrence of the <ComparisonProductPrice> composite.

  Positive real number, with explicit decimal point when required, suggested maximum length 12 characters
  PriceAmount
  j151
  1
  `<PriceAmount>18.99</PriceAmount>`

##### P.26.82 Currency code

An ONIX code identifying the currency in which the <PriceAmount> in an occurrence of the <ComparisonProductPrice> composite is stated. Optional and non-repeating, but required if the currency is not the default currency for the ONIX message. To avoid any possible ambiguity, it is strongly recommended that the currency should be stated here.

  Fixed length, three letters, based on ISO 4217. Note that ISO 4217 specifies that currency codes shall be sent as upper case only
  List 96
  CurrencyCode
  j152
  0…1
  `<j152>GBP</j152>` (UK Pound Sterling)

##### End of Comparison product price composite

##### Price date composite

An optional group of data elements which together specify a date associated with a price, repeatable in order to specify multiple associated dates.

Note that if no dates are specified, the price is effective at the time the ONIX message is sent.

  PriceDate
  pricedate
  0…n

##### P.26.83 Price date role code

An ONIX code indicating the significance of the date. Mandatory in each occurrence of the <PriceDate> composite, and non-repeating.

  Fixed length, two digits
  List 173
  PriceDateRole
  x476
  1
  `<PriceDateRole>14</PriceDateRole>` (From date [date on which a price becomes effective])

##### P.26.85 Date

The date specified in the <PriceDateRole> field. Mandatory in each occurrence of the <PriceDate> composite, and non-repeating. <Date> may carry a dateformat attribute: if the attribute is missing, then the default format is YYYYMMDD.

  As specified by the value in the dateformat attribute, or the default YYYYMMDD
  Date
  b306
  1
  dateformat
  `<Date>20100106</Date>`
  Note that all dates are inclusive, so ‘Date from’ is the first date on which the price is effective, and ‘Date until’ is the last date on which it is effective.

##### End of Price date composite

##### P.26.86 Price printed on product

An ONIX code indicating whether the price in a <Price> composite is printed on the product. Optional and non-repeating. Omission of this element must not be interpreted as indicating that the price is not printed on the product.

  Fixed length, two digits
  List 174
  PrintedOnProduct
  x301
  0…1
  `<x301>02</x301>` (Price is printed on product)

##### P.26.87 Position on product

An ONIX code indicating a position on a product; in this case, the position in which a price appears. Optional, but must be included if (and only if) the <PrintedOnProduct> element indicates that the price appears on the product, even if the position is ‘unknown’. Non-repeating.

  Fixed length, two digits
  List 142
  PositionOnProduct
  x313
  0…1
  `<x313>01</x313>` (Cover 4 [the back cover of a book])

##### End of Price composite

  use of the <Price> composite with a future planned price rise
  using Reference names |
  --- | ---
  `<Price>` |
  `<PriceType>01</PriceType>` | RRP excluding tax
  `<PriceAmount>15.99</PriceAmount>` |
  `<CurrencyCode>USD</CurrencyCode>` | US$
  `<Territory>` | Price applies in
  `<CountriesIncluded>US</CountriesIncluded>` | USA only
  `</Territory>` |
  `<PriceDate>` |
  `<PriceDateRole>15</PriceDateRole>` | Until date
  `<Date>20110104</Date>` | Default format
  `</PriceDate>` |
  `<PrintedOnProduct>02</PrintedOnProduct>` | Is on product
  `<PositionOnProduct>01</PositionOnProduct>` | On back cover
  `</Price>` |
  `<Price>` |
  `<PriceType>01</PriceType>` | RRP excluding tax
  `<PriceAmount>17.99</PriceAmount>` | Higher price
  `<CurrencyCode>USD</CurrencyCode>` | US$
  `<Territory>` | Price applies in
  `<CountriesIncluded>US</CountriesIncluded>` | USA only
  `</Territory>` |
  `<PriceDate>` |
  `<PriceDateRole>14</PriceDateRole>` | From date
  `<Date>20110105</Date>` | Default format
  `</PriceDate>` |
  `<PrintedOnProduct>02</PrintedOnProduct>` | Is on product
  `<PositionOnProduct>01</PositionOnProduct>` | On back cover
  `</Price>` |

  using short tags |
  --- | ---
  `<price>` |
  `<x462>01</x462>` |
  `<j151>15.99</j151>` |
  `<j152>USD</j152>` |
  `<territory>` |
  `<x449>US</x449>` |
  `</territory>` |
  `<pricedate>` |
  `<x476>15</x476>` |
  `<b306>20110104</b306>` |
  `</pricedate>` |
  `<x301>02</x301>` |
  `<x313>01</x313>` |
  `</price>` |
  `<price>` |
  `<x462>01</x462>` |
  `<j151>17.99</j151>` |
  `<j152>USD</j152>` |
  `<territory>` |
  `<x449>US</x449>` |
  `</territory>` |
  `<pricedate>` |
  `<x476>14</x476>` |
  `<b306>20110105</b306>` |
  `</pricedate>` |
  `<x301>02</x301>` |
  `<x313>01</x313>` |
  `</price>` |

##### End of Supply detail composite

#### End of Product supply composite

### End of Product composite

##### P.26.149 “No product” indicator

An empty element that provides a positive indication that a message does not carry any Product records. Intended to be used only in empty ‘delta’ update messages to provide confirmation that there have been no updates since the previous message. Optional and non-repeating, but must be used in an ONIX message that contains no <Product> composites.

  XML empty element
  NoProduct/
  x507/
  0…1
  `<x507/>`

## Appendix

#### A.1 ONIX for Books data element summary

The summary table shows all the data elements which occur in Release 3.1 revision 1, in the order they must occur in a message, with both Reference names and the equivalent Short tags.

Data elements are linked back to their definitions. Leader dots and indentation of Reference names indicate the nesting structure of the composites and data elements. Red coloring of elements indicates the element is deprecated.

The rightmost column indicates the cardinality of each data element – whether the element is optional (0…1), optional and repeatable (0…n), mandatory (1) or mandatory and repeatable (1…n) – within its parent element.

Where data element content is controlled by a code list, the list number is shown in the adjacent List/Attr column. This column also indicates data elements that may carry XHTML-formatted text, or a collationkey, dateformat, language, release, textcase, textformat, textscript or xmlns attribute, using the abbreviations x, ck, df, la, rl, tc, tf, ts and ns. Note that all elements and composites may carry the datestamp, sourcename and sourcetype attributes. A dagger symbol (†) in this column indicates a data element or composite new in 3.0.1, a double dagger (‡) indicates new in 3.0.2, a section symbol (§) indicates new in 3.0.3, Greek Delta (∆) indicates new in 3.0.4, Phi (Φ) indicates new in version 3.0.5, a Xi symbol (Ξ) indicates new in version 3.0.6, a Sigma (Σ) indicates new in version 3.0.7, Psi (Ψ) indicates new in version 3.0.8, an Omega (Ω) indicates new in release 3.1, and a Pi (Π) is appended to the new elements in revision 3.1.1. Lamda (Λ) indicates an addition in ONIX 3.1.2. Data elements that have been removed from Release 3.1 are not shown in the table, but are listed in Appendix A.4.

  data element summary
  # | Reference name | Short tag | List/Attr | Card
  --- | --- | --- | --- | ---
  Message
  X.1 | `<ONIXMessage>` | `<ONIXmessage>` | ns rl | 1
  Message header
  ○ | `. <Header>` | `<header>` |  | 1
  ○ | `. . <Sender>` | `<sender>` |  | 1
  ○ | `. . . <SenderIdentifier>` | `<senderidentifier>` |  | 0…n
  H.1 | `. . . . <SenderIDType>` | `<m379>` | 44 | 1
  H.2 | `. . . . <IDTypeName>` | `<b233>` | la | 0…1
  H.3 | `. . . . <IDValue>` | `<b244>` |  | 1
  H.4 | `. . . <SenderName>` | `<x298>` |  | 0…1
  H.5 | `. . . <ContactName>` | `<x299>` |  | 0…1
  H.5a | `. . . <TelephoneNumber>` | `<j270>` | Ψ | 0…1
  H.6 | `. . . <EmailAddress>` | `<j272>` |  | 0…1
  ○ | `. . <Addressee>` | `<addressee>` |  | 0…n
  ○ | `. . . <AddresseeIdentifier>` | `<addresseeidentifier>` |  | 0…n
  H.7 | `. . . . <AddresseeIDType>` | `<m380>` | 44 | 1
  H.8 | `. . . . <IDTypeName>` | `<b233>` | la | 0…1
  H.9 | `. . . . <IDValue>` | `<b244>` |  | 1
  H.10 | `. . . <AddresseeName>` | `<x300>` |  | 0…1
  H.11 | `. . . <ContactName>` | `<x299>` |  | 0…1
  H.11a | `. . . <TelephoneNumber>` | `<j270>` | Ψ | 0…1
  H.12 | `. . . <EmailAddress>` | `<j272>` |  | 0…1
  H.13 | `. . <MessageNumber>` | `<m180>` |  | 0…1
  H.14 | `. . <MessageRepeat>` | `<m181>` |  | 0…1
  H.15 | `. . <SentDateTime>` | `<x307>` |  | 1
  H.16 | `. . <MessageNote>` | `<m183>` | la | 0…n
  H.17 | `. . <DefaultLanguageOfText>` | `<m184>` | 74 | 0…1
  H.18 | `. . <DefaultPriceType>` | `<x310>` | 58 | 0…1
  H.19 | `. . <DefaultCurrencyCode>` | `<m186>` | 96 | 0…1
  Product record
  ○ | `. <Product>` | `<product>` |  | 0…n
  Group P.1 Record reference, type and source
  P.1.1 | `. . <RecordReference>` | `<a001>` |  | 1
  P.1.2 | `. . <NotificationType>` | `<a002>` | 1 | 1
  P.1.3 | `. . <DeletionText>` | `<a199>` | la | 0…n
  P.1.4 | `. . <RecordSourceType>` | `<a194>` | 3 | 0…1
  ○ | `. . <RecordSourceIdentifier>` | `<recordsourceidentifier>` |  | 0…n
  P.1.5 | `. . . <RecordSourceIDType>` | `<x311>` | 44 | 1
  P.1.6 | `. . . <IDTypeName>` | `<b233>` | la | 0…1
  P.1.7 | `. . . <IDValue>` | `<b244>` |  | 1
  P.1.8 | `. . <RecordSourceName>` | `<a197>` |  | 0…1
  Group P.2 Product identifiers
  ○ | `. . <ProductIdentifier>` | `<productidentifier>` |  | 1…n
  P.2.1 | `. . . <ProductIDType>` | `<b221>` | 5 | 1
  P.2.2 | `. . . <IDTypeName>` | `<b233>` | la | 0…1
  P.2.3 | `. . . <IDValue>` | `<b244>` |  | 1
  ○ | `. . <Barcode>` | `<barcode>` |  | 0…n
  P.2.4 | `. . . <BarcodeType>` | `<x312>` | 141 | 1
  P.2.5 | `. . . <PositionOnProduct>` | `<x313>` | 142 | 0…1
  Block 1: Product description
  ○ | `. . <DescriptiveDetail>` | `<descriptivedetail>` |  | 0…1
  Group P.3 Product form
  P.3.1 | `. . . <ProductComposition>` | `<x314>` | 2 | 1
  P.3.2 | `. . . <ProductForm>` | `<b012>` | 150 | 1
  P.3.3 | `. . . <ProductFormDetail>` | `<b333>` | 175 | 0…n
  ○ | `. . . <ProductFormFeature>` | `<productformfeature>` |  | 0…n
  P.3.4 | `. . . . <ProductFormFeatureType>` | `<b334>` | 79 | 1
  P.3.5 | `. . . . <ProductFormFeatureValue>` | `<b335>` | various | 0…1
  P.3.6 | `. . . . <ProductFormFeature​Description>` | `<b336>` | la | 0…n
  P.3.7 | `. . . <ProductPackaging>` | `<b225>` | 80 | 0…1
  P.3.8 | `. . . <ProductFormDescription>` | `<b014>` | la | 0…n
  P.3.9 | `. . . <TradeCategory>` | `<b384>` | 12 | 0…1
  P.3.10 | `. . . <PrimaryContentType>` | `<x416>` | 81 | 0…1
  P.3.11 | `. . . <ProductContentType>` | `<b385>` | 81 | 0…n
  ○ | `. . . <Measure>` | `<measure>` |  | 0…n
  P.3.12 | `. . . . <MeasureType>` | `<x315>` | 48 | 1
  P.3.13 | `. . . . <Measurement>` | `<c094>` |  | 1
  P.3.14 | `. . . . <MeasureUnitCode>` | `<c095>` | 50 | 1
  P.3.15 | `. . . <CountryOfManufacture>` | `<x316>` | 91 | 0…1
  P.3.16 | `. . . <EpubTechnicalProtection>` | `<x317>` | 144 | 0…n
  ○ | `. . . <EpubUsageConstraint>` | `<epubusageconstraint>` |  | 0…n
  P.3.17 | `. . . . <EpubUsageType>` | `<x318>` | 145 | 1
  P.3.18 | `. . . . <EpubUsageStatus>` | `<x319>` | 146 | 1
  ○ | `. . . . <EpubUsageLimit>` | `<epubusagelimit>` |  | 0…n
  P.3.19 | `. . . . . <Quantity>` | `<x320>` |  | 1
  P.3.20 | `. . . . . <EpubUsageUnit>` | `<x321>` | 147 | 1
  ○ | `. . . <EpubLicense>` | `<epublicense>` | ‡ | 0…n
  P.3.20a | `. . . . <EpubLicenseName>` | `<x511>` | la ‡ | 1…n
  ○ | `. . . . <EpubLicenseExpression>` | `<epublicenseexpression>` | ‡ | 0…n
  P.3.20b | `. . . . . <EpubLicenseExpression​Type>` | `<x508>` | 218 ‡ | 1
  P.3.20c | `. . . . . <EpubLicenseExpression​TypeName>` | `<x509>` | la ‡ | 0…1
  P.3.20d | `. . . . . <EpubLicenseExpression​Link>` | `<x510>` | ‡ | 1
  ○ | `. . . . <EpubLicenseDate>` | `<epublicensedate>` | Ω | 0…n
  P.3.20e | `. . . . . <EpubLicenseDateRole>` | `<x585>` | 260 Ω | 1
  P.3.20f | `. . . . . <Date>` | `<b306>` | df Ω | 1
  P.3.21 | `. . . <MapScale>` | `<b063>` |  | 0…n
  ○ | `. . . <ProductClassification>` | `<productclassification>` |  | 0…n
  P.3.22 | `. . . . <ProductClassificationType>` | `<b274>` | 9 | 1
  P.3.22a | `. . . . <ProductClassificationTypeName>` | `<x555>` | la Σ | 0…1
  P.3.23 | `. . . . <ProductClassificationCode>` | `<b275>` |  | 1
  P.3.24 | `. . . . <Percent>` | `<b337>` |  | 0…1
  Group P.4 Product parts
  ○ | `. . . <ProductPart>` | `<productpart>` |  | 0…n
  P.4.1 | `. . . . <PrimaryPart/>` | `<x457/>` |  | 0…1
  ○ | `. . . . <ProductIdentifier>` | `<productidentifier>` |  | 0…n
  P.4.2 | `. . . . . <ProductIDType>` | `<b221>` | 5 | 1
  P.4.3 | `. . . . . <IDTypeName>` | `<b233>` | la | 0…1
  P.4.4 | `. . . . . <IDValue>` | `<b244>` |  | 1
  P.4.5 | `. . . . <ProductForm>` | `<b012>` | 150 | 1
  P.4.6 | `. . . . <ProductFormDetail>` | `<b333>` | 175 | 0…n
  ○ | `. . . . <ProductFormFeature>` | `<productformfeature>` |  | 0…n
  P.4.7 | `. . . . . <ProductForm​FeatureType>` | `<b334>` | 79 | 1
  P.4.8 | `. . . . . <ProductForm​FeatureValue>` | `<b335>` | various | 0…1
  P.4.9 | `. . . . . <ProductForm​FeatureDescription>` | `<b336>` | la | 0…n
  P.4.9a | `. . . . <ProductPackaging>` | `<b225>` | 80 § | 0…1
  P.4.10 | `. . . . <ProductFormDescription>` | `<b014>` | la | 0…n
  P.4.11 | `. . . . <ProductContentType>` | `<b385>` | 81 | 0…n
  ○ | `. . . . <Measure>` | `<measure>` | Ξ | 0…n
  P.4.11a | `. . . . . <MeasureType>` | `<x315>` | 48 Ξ | 1
  P.4.11b | `. . . . . <Measurement>` | `<c094>` | Ξ | 1
  P.4.11c | `. . . . . <MeasureUnitCode>` | `<c095>` | 50 Ξ | 1
  P.4.12 | `. . . . <NumberOfItemsOfThisForm>` | `<x322>` |  | 0…1
  P.4.13 | `. . . . <NumberOfCopies>` | `<x323>` |  | 0…1
  P.4.14 | `. . . . <CountryOfManufacture>` | `<x316>` | 91 | 0…1
  Group P.5 Collection
  ○ | `. . . <Collection>` | `<collection>` |  | 0…n
  P.5.1 | `. . . . <CollectionType>` | `<x329>` | 148 | 1
  P.5.1a | `. . . . <CollectionFrequency>` | `<x582>` | 259 Ω | 0…1
  P.5.2 | `. . . . <SourceName>` | `<x330>` |  | 0…1
  ○ | `. . . . <CollectionIdentifier>` | `<collectionidentifier>` |  | 0…n
  P.5.2a | `. . . . . <Collection​Element​Level>` | `<x586>` | 146 Ω | 0…1
  P.5.3 | `. . . . . <Collection​IDType>` | `<x344>` | 13 | 1
  P.5.4 | `. . . . . <IDTypeName>` | `<b233>` | la | 0…1
  P.5.5 | `. . . . . <IDValue>` | `<b244>` |  | 1
  ○ | `. . . . <CollectionSequence>` | `<collectionsequence>` | † | 0…n
  P.5.5a | `. . . . . <CollectionSequenceType>` | `<x479>` | 197 † | 1
  P.5.5b | `. . . . . <CollectionSequence​TypeName>` | `<x480>` | la † | 0…1
  P.5.5c | `. . . . . <CollectionSequence​Number>` | `<x481>` | † | 1
  ○ | `. . . . <TitleDetail>` | `<titledetail>` |  | 0…n
  P.5.6 | `. . . . . <TitleType>` | `<b202>` | 15 | 1
  ○ | `. . . . . <TitleElement>` | `<titleelement>` |  | 1…n
  P.5.6a | `. . . . . . <SequenceNumber>` | `<b034>` | † | 0…1
  P.5.7 | `. . . . . . <Title​ElementLevel>` | `<x409>` | 149 | 1
  P.5.8 | `. . . . . . <PartNumber>` | `<x410>` | la ts | 0…1
  P.5.9 | `. . . . . . <YearOfAnnual>` | `<b020>` |  | 0…1
  P.5.10 | `. . . . . . <TitleText>` | `<b203>` | ck la ts tc | 0…1
  P.5.11 | `. . . . . . <TitlePrefix>` | `<b030>` | ck la ts tc | 0…1
  P.5.11a | `. . . . . . <NoPrefix/>` | `<x501/>` | ‡ | 0…1
  P.5.12 | `. . . . . . <Title​WithoutPrefix>` | `<b031>` | ck la ts tc | 0…1
  P.5.13 | `. . . . . . <Subtitle>` | `<b029>` | ck la ts tc | 0…1
  P.5.13a | `. . . . . <TitleStatement>` | `<x478>` | x la tf † | 0…1
  ○ | `. . . . <Contributor>` | `<contributor>` |  | 0…n
  P.5.14 | `. . . . . <SequenceNumber>` | `<b034>` |  | 0…1
  P.5.15 | `. . . . . <ContributorRole>` | `<b035>` | 17 | 1…n
  P.5.16 | `. . . . . <FromLanguage>` | `<x412>` | 74 | 0…n
  P.5.17 | `. . . . . <ToLanguage>` | `<x413>` | 74 | 0…n
  P.5.18 | `. . . . . <NameType>` | `<x414>` | 18 | 0…1
  ○ | `. . . . . <NameIdentifier>` | `<nameidentifier>` |  | 0…n
  P.5.19 | `. . . . . . <NameIDType>` | `<x415>` | 44 | 1
  P.5.20 | `. . . . . . <IDTypeName>` | `<b233>` | la | 0…1
  P.5.21 | `. . . . . . <IDValue>` | `<b244>` |  | 1
  P.5.22 | `. . . . . <PersonName>` | `<b036>` | ck la ts | 0…1
  P.5.23 | `. . . . . <PersonNameInverted>` | `<b037>` | ck la ts | 0…1
  P.5.24 | `. . . . . <TitlesBeforeNames>` | `<b038>` | ck la ts | 0…1
  P.5.25 | `. . . . . <NamesBeforeKey>` | `<b039>` | ck la ts | 0…1
  P.5.26 | `. . . . . <PrefixToKey>` | `<b247>` | ck la ts | 0…1
  P.5.27 | `. . . . . <KeyNames>` | `<b040>` | ck la ts | 0…1
  P.5.28 | `. . . . . <NamesAfterKey>` | `<b041>` | ck la ts | 0…1
  P.5.29 | `. . . . . <SuffixToKey>` | `<b248>` | ck la ts | 0…1
  P.5.30 | `. . . . . <LettersAfterNames>` | `<b042>` | ck la ts | 0…1
  P.5.31 | `. . . . . <TitlesAfterNames>` | `<b043>` | ck la ts | 0…1
  P.5.32 | `. . . . . <CorporateName>` | `<b047>` | ck la ts | 0…n
  P.5.33 | `. . . . . <CorporateNameInverted>` | `<x443>` | ck la ts | 0…n
  P.5.33a | `. . . . . <UnnamedPersons>` | `<b249>` | 19 § | 0…1
  ○ | `. . . . . <AlternativeName>` | `<alternativename>` |  | 0…n
  P.5.34 | `. . . . . . <NameType>` | `<x414>` | 18 | 1
  ○ | `. . . . . . <NameIdentifier>` | `<nameidentifier>` |  | 0…n
  P.5.35 | `. . . . . . . <NameIDType>` | `<x415>` | 44 | 1
  P.5.36 | `. . . . . . . <IDTypeName>` | `<b233>` | la | 0…1
  P.5.37 | `. . . . . . . <IDValue>` | `<b244>` |  | 1
  P.5.38 | `. . . . . . <PersonName>` | `<b036>` | ck la ts | 0…1
  P.5.39 | `. . . . . . <Person​NameInverted>` | `<b037>` | ck la ts | 0…1
  P.5.40 | `. . . . . . <TitlesBeforeNames>` | `<b038>` | ck la ts | 0…1
  P.5.41 | `. . . . . . <NamesBeforeKey>` | `<b039>` | ck la ts | 0…1
  P.5.42 | `. . . . . . <PrefixToKey>` | `<b247>` | ck la ts | 0…1
  P.5.43 | `. . . . . . <KeyNames>` | `<b040>` | ck la ts | 0…1
  P.5.44 | `. . . . . . <NamesAfterKey>` | `<b041>` | ck la ts | 0…1
  P.5.45 | `. . . . . . <SuffixToKey>` | `<b248>` | ck la ts | 0…1
  P.5.46 | `. . . . . . <LettersAfterNames>` | `<b042>` | ck la ts | 0…1
  P.5.47 | `. . . . . . <TitlesAfterNames>` | `<b043>` | ck la ts | 0…1
  P.5.48 | `. . . . . . <CorporateName>` | `<b047>` | ck la ts | 0…n
  P.5.49 | `. . . . . . <Corporate​NameInverted>` | `<x443>` | ck la ts | 0…n
  ○ | `. . . . . <ContributorDate>` | `<contributordate>` |  | 0…n
  P.5.50 | `. . . . . . <Contributor​DateRole>` | `<x417>` | 177 | 1
  P.5.52 | `. . . . . . <Date>` | `<b306>` | df | 1
  ○ | `. . . . . <ProfessionalAffiliation>` | `<professionalaffiliation>` |  | 0…n
  P.5.53 | `. . . . . . <ProfessionalPosition>` | `<b045>` | la | 0…n
  ○ | `. . . . . . <Affiliation​Identifier>` | `<affiliationidentifier>` | Ω | 0…n
  P.5.53a | `. . . . . . . <AffiliationIDType>` | `<x580>` | 44 Ω | 1
  P.5.53b | `. . . . . . . <IDTypeName>` | `<b233>` | la Ω | 0…1
  P.5.53c | `. . . . . . . <IDValue>` | `<b244>` | Ω | 1
  P.5.54 | `. . . . . . <Affiliation>` | `<b046>` | la | 0…1
  ○ | `. . . . . <Prize>` | `<prize>` | § | 0…n
  P.5.54a | `. . . . . . <SequenceNumber>` | `<b034>` | Ω | 0…1
  ○ | `. . . . . . <PrizeIdentifier>` | `<prizeidentifier>` | Π | 0…n
  P.5.54b | `. . . . . . . <PrizeIDType>` | `<x589>` | 263 Π | 1
  P.5.54c | `. . . . . . . <IDTypeName>` | `<x589>` | la Π | 0…1
  P.5.54d | `. . . . . . . <IDValue>` | `<b244>` | Π | 1
  P.5.54e | `. . . . . . <PrizeName>` | `<g126>` | la § | 1…n
  P.5.54f | `. . . . . . <PrizeYear>` | `<g127>` | § | 0…1
  P.5.54g | `. . . . . . <AwardingBody>` | `<x584>` | la Ω | 0…n
  P.5.54h | `. . . . . . <PrizeCountry>` | `<g128>` | 91 § | 0…1
  P.5.54i | `. . . . . . <PrizeRegion>` | `<x556>` | 49 Σ | 0…1
  P.5.54j | `. . . . . . <PrizeCode>` | `<g129>` | 41 § | 0…1
  P.5.54k | `. . . . . . <PrizeStatement>` | `<x503>` | x la tf § | 0…n
  P.5.54l | `. . . . . . <PrizeJury>` | `<g343>` | x la tf § | 0…n
  P.5.55 | `. . . . . <BiographicalNote>` | `<b044>` | x la tf | 0…n
  ○ | `. . . . . <Website>` | `<website>` |  | 0…n
  P.5.56 | `. . . . . . <WebsiteRole>` | `<b367>` | 73 | 0…1
  P.5.57 | `. . . . . . <WebsiteDescription>` | `<b294>` | x la tf | 0…n
  P.5.58 | `. . . . . . <WebsiteLink>` | `<b295>` | la | 1…n
  P.5.59 | `. . . . . <ContributorDescription>` | `<b048>` | x la tf | 0…n
  ○ | `. . . . . <ContributorPlace>` | `<contributorplace>` |  | 0…n
  P.5.61 | `. . . . . . <Contributor​PlaceRelator>` | `<x418>` | 151 | 1
  P.5.62 | `. . . . . . <CountryCode>` | `<b251>` | 91 | 0…1
  P.5.63 | `. . . . . . <RegionCode>` | `<b398>` | 49 | 0…1
  P.5.63a | `. . . . . . <LocationName>` | `<j349>` | la ‡ | 0…n
  P.5.63b | `. . . . <ContributorStatement>` | `<b049>` | x la tf † | 0…n
  P.5.63c | `. . . . <NoContributor/>` | `<n339/>` | ∆ | 0…1
  P.5.64 | `. . . <NoCollection/>` | `<x411/>` |  | 0…1
  Group P.6 Product title detail
  ○ | `. . . <TitleDetail>` | `<titledetail>` |  | 1…n
  P.6.1 | `. . . . <TitleType>` | `<b202>` | 15 | 1
  ○ | `. . . . <TitleElement>` | `<titleelement>` |  | 1…n
  P.6.1a | `. . . . . <SequenceNumber>` | `<b034>` | † | 0…1
  P.6.2 | `. . . . . <TitleElementLevel>` | `<x409>` | 149 | 1
  P.6.3 | `. . . . . <PartNumber>` | `<x410>` | la ts | 0…1
  P.6.4 | `. . . . . <YearOfAnnual>` | `<b020>` |  | 0…1
  P.6.5 | `. . . . . <TitleText>` | `<b203>` | ck la ts tc | 0…1
  P.6.6 | `. . . . . <TitlePrefix>` | `<b030>` | ck la ts tc | 0…1
  P.6.6a | `. . . . . <NoPrefix/>` | `<x501/>` | ‡ | 0…1
  P.6.7 | `. . . . . <TitleWithoutPrefix>` | `<b031>` | ck la ts tc | 0…1
  P.6.8 | `. . . . . <Subtitle>` | `<b029>` | ck la ts tc | 0…1
  P.6.8a | `. . . . <TitleStatement>` | `<x478>` | x la tf † | 0…1
  P.6.9 | `. . . <ThesisType>` | `<b368>` | 72 | 0…1
  P.6.10 | `. . . <ThesisPresentedTo>` | `<b369>` | la | 0…1
  P.6.11 | `. . . <ThesisYear>` | `<b370>` | df | 0…1
  Group P.7 Authorship
  ○ | `. . . <Contributor>` | `<contributor>` |  | 0…n
  P.7.1 | `. . . . <SequenceNumber>` | `<b034>` |  | 0…1
  P.7.2 | `. . . . <ContributorRole>` | `<b035>` | 17 | 1…n
  P.7.3 | `. . . . <FromLanguage>` | `<x412>` | 74 | 0…n
  P.7.4 | `. . . . <ToLanguage>` | `<x413>` | 74 | 0…n
  P.7.5 | `. . . . <NameType>` | `<x414>` | 18 | 0…1
  ○ | `. . . . <NameIdentifier>` | `<nameidentifier>` |  | 0…n
  P.7.6 | `. . . . . <NameIDType>` | `<x415>` | 44 | 1
  P.7.7 | `. . . . . <IDTypeName>` | `<b233>` | la | 0…1
  P.7.8 | `. . . . . <IDValue>` | `<b244>` |  | 1
  P.7.9 | `. . . . <PersonName>` | `<b036>` | ck la ts | 0…1
  P.7.10 | `. . . . <Person​NameInverted>` | `<b037>` | ck la ts | 0…1
  P.7.11 | `. . . . <TitlesBeforeNames>` | `<b038>` | ck la ts | 0…1
  P.7.12 | `. . . . <NamesBeforeKey>` | `<b039>` | ck la ts | 0…1
  P.7.13 | `. . . . <PrefixToKey>` | `<b247>` | ck la ts | 0…1
  P.7.14 | `. . . . <KeyNames>` | `<b040>` | ck la ts | 0…1
  P.7.15 | `. . . . <NamesAfterKey>` | `<b041>` | ck la ts | 0…1
  P.7.16 | `. . . . <SuffixToKey>` | `<b248>` | ck la ts | 0…1
  P.7.17 | `. . . . <LettersAfterNames>` | `<b042>` | ck la ts | 0…1
  P.7.18 | `. . . . <TitlesAfterNames>` | `<b043>` | ck la ts | 0…1
  P.7.19 | `. . . . <CorporateName>` | `<b047>` | ck la ts | 0…n
  P.7.20 | `. . . . <Corporate​NameInverted>` | `<x443>` | ck la ts | 0…n s
  P.7.20a | `. . . . <UnnamedPersons>` | `<b249>` | 19 § | 0…1
  ○ | `. . . . <AlternativeName>` | `<alternativename>` |  | 0…n
  P.7.21 | `. . . . . <NameType>` | `<x414>` | 18 | 1
  ○ | `. . . . . <NameIdentifier>` | `<nameidentifier>` |  | 0…n
  P.7.22 | `. . . . . . <NameIDType>` | `<x415>` | 44 | 1
  P.7.23 | `. . . . . . <IDTypeName>` | `<b233>` | la | 0…1
  P.7.24 | `. . . . . . <IDValue>` | `<b244>` |  | 1
  P.7.25 | `. . . . . <PersonName>` | `<b036>` | ck la ts | 0…1
  P.7.26 | `. . . . . <Person​NameInverted>` | `<b037>` | ck la ts | 0…1
  P.7.27 | `. . . . . <TitlesBeforeNames>` | `<b038>` | ck la ts | 0…1
  P.7.28 | `. . . . . <NamesBeforeKey>` | `<b039>` | ck la ts | 0…1
  P.7.29 | `. . . . . <PrefixToKey>` | `<b247>` | ck la ts | 0…1
  P.7.30 | `. . . . . <KeyNames>` | `<b040>` | ck la ts | 0…1
  P.7.31 | `. . . . . <NamesAfterKey>` | `<b041>` | ck la ts | 0…1
  P.7.32 | `. . . . . <SuffixToKey>` | `<b248>` | ck la ts | 0…1
  P.7.33 | `. . . . . <LettersAfterNames>` | `<b042>` | ck la ts | 0…1
  P.7.34 | `. . . . . <TitlesAfterNames>` | `<b043>` | ck la ts | 0…1
  P.7.35 | `. . . . . <CorporateName>` | `<b047>` | ck la ts | 0…n
  P.7.36 | `. . . . . <Corporate​NameInverted>` | `<x443>` | ck la ts | 0…n
  ○ | `. . . . <ContributorDate>` | `<contributordate>` |  | 0…n
  P.7.37 | `. . . . . <Contributor​DateRole>` | `<x417>` | 177 | 1
  P.7.39 | `. . . . . <Date>` | `<b306>` | df | 1
  ○ | `. . . . <Professional​Affiliation>` | `<professionalaffiliation>` |  | 0…n
  P.7.40 | `. . . . . <Professional​Position>` | `<b045>` | la | 0…n
  ○ | `. . . . . <Affiliation​Identifier>` | `<affiliationidentifier>` | Ω | 0…n
  P.7.40a | `. . . . . . <AffiliationIDType>` | `<x580>` | 44 Ω | 1
  P.7.40b | `. . . . . . <IDTypeName>` | `<b233>` | la Ω | 0…1
  P.7.40c | `. . . . . . <IDValue>` | `<b244>` | Ω | 1
  P.7.41 | `. . . . . <Affiliation>` | `<b046>` | la | 0…1
  ○ | `. . . . <Prize>` | `<prize>` | § | 0…n
  P.7.41a | `. . . . . <SequenceNumber>` | `<b034>` | Ω | 0…1
  ○ | `. . . . . <PrizeIdentifier>` | `<prizeidentifier>` | Π | 0…n
  P.7.41b | `. . . . . . <PrizeIDType>` | `<x589>` | 263 Π | 1
  P.7.41c | `. . . . . . <IDTypeName>` | `<b233>` | la Π | 0…1
  P.7.41d | `. . . . . . <IDValue>` | `<b244>` | Π | 1
  P.7.41e | `. . . . . <PrizeName>` | `<g126>` | la § | 1…n
  P.7.41f | `. . . . . <PrizeYear>` | `<g127>` | § | 0…1
  P.7.41g | `. . . . . <AwardingBody>` | `<x584>` | la Ω | 0…n
  P.7.41h | `. . . . . <PrizeCountry>` | `<g128>` | 91 § | 0…1
  P.7.41i | `. . . . . <PrizeRegion>` | `<x556>` | 49 Σ | 0…1
  P.7.41j | `. . . . . <PrizeCode>` | `<g129>` | 41 § | 0…1
  P.7.41k | `. . . . . <PrizeStatement>` | `<x503>` | x la tf § | 0…n
  P.7.41l | `. . . . . <PrizeJury>` | `<g343>` | x la tf § | 0…n
  P.7.42 | `. . . . <BiographicalNote>` | `<b044>` | x la tf | 0…n
  ○ | `. . . . <Website>` | `<website>` |  | 0…n
  P.7.43 | `. . . . . <WebsiteRole>` | `<b367>` | 73 | 0…1
  P.7.44 | `. . . . . <WebsiteDescription>` | `<b294>` | x la tf | 0…n
  P.7.45 | `. . . . . <WebsiteLink>` | `<b295>` | la | 1…n
  P.7.46 | `. . . . <ContributorDescription>` | `<b048>` | x la tf | 0…n
  ○ | `. . . . <ContributorPlace>` | `<contributorplace>` |  | 0…n
  P.7.48 | `. . . . . <Contributor​PlaceRelator>` | `<x418>` | 151 | 1
  P.7.49 | `. . . . . <CountryCode>` | `<b251>` | 91 | 0…1
  P.7.50 | `. . . . . <RegionCode>` | `<b398>` | 49 | 0…1
  P.7.50a | `. . . . . <LocationName>` | `<j349>` | la ‡ | 0…n
  P.7.51 | `. . . <ContributorStatement>` | `<b049>` | x la tf | 0…n
  P.7.52 | `. . . <NoContributor/>` | `<n339/>` |  | 0…1
  Group P.8 Event
  ○ | `. . . <Event>` | `<event>` | § | 0…n
  P.8.16 | `. . . . <EventRole>` | `<x515>` | 20 § | 1
  P.8.17 | `. . . . <EventName>` | `<x516>` | la § | 1…n
  P.8.18 | `. . . . <EventAcronym>` | `<x517>` | la § | 0…n
  P.8.19 | `. . . . <EventNumber>` | `<x518>` | § | 0…1
  P.8.20 | `. . . . <EventTheme>` | `<x519>` | la § | 0…n
  P.8.21 | `. . . . <EventDate>` | `<x520>` | df § | 0…1
  P.8.22 | `. . . . <EventPlace>` | `<x521>` | la § | 0…n
  ○ | `. . . . <EventSponsor>` | `<eventsponsor>` | § | 0…n
  ○ | `. . . . . <Event​SponsorIdentifier>` | `<event​sponsoridentifier>` | § | 0…n
  P.8.23 | `. . . . . . <Event​SponsorIDType>` | `<x522>` | 44 § | 1
  P.8.24 | `. . . . . . <IDTypeName>` | `<b233>` | la § | 0…1
  P.8.25 | `. . . . . . <IDValue>` | `<b244>` | § | 1
  P.8.26 | `. . . . . <PersonName>` | `<b036>` | ck la ts § | 0…1
  P.8.27 | `. . . . . <CorporateName>` | `<b047>` | ck la ts § | 0…1
  ○ | `. . . . <Website>` | `<website>` | § | 0…n
  P.8.28 | `. . . . . <WebsiteRole>` | `<b367>` | 73 § | 0…1
  P.8.29 | `. . . . . <WebsiteDescription>` | `<b294>` | x la tf § | 0…n
  P.8.30 | `. . . . . <WebsiteLink>` | `<b295>` | la § | 1…n
  Group P.9 Edition
  P.9.1 | `. . . <EditionType>` | `<x419>` | 21 | 0…n
  P.9.2 | `. . . <EditionNumber>` | `<b057>` |  | 0…1
  P.9.3 | `. . . <EditionVersionNumber>` | `<b217>` |  | 0…1
  P.9.4 | `. . . <EditionStatement>` | `<b058>` | x la tf | 0…n
  P.9.5 | `. . . <NoEdition/>` | `<n386/>` |  | 0…1
  ○ | `. . . <ReligiousText>` | `<religioustext>` |  | 0…1
  ○ | `. . . . <Bible>` | `<bible>` |  | 0…1
  P.9.6 | `. . . . . <BibleContents>` | `<b352>` | 82 | 1…n
  P.9.7 | `. . . . . <BibleVersion>` | `<b353>` | 83 | 1…n
  P.9.8 | `. . . . . <StudyBibleType>` | `<b389>` | 84 | 0…1
  P.9.9 | `. . . . . <BiblePurpose>` | `<b354>` | 85 | 0…n
  P.9.10 | `. . . . . <Bible​TextOrganization>` | `<b355>` | 86 | 0…1
  P.9.11 | `. . . . . <Bible​ReferenceLocation>` | `<b356>` | 87 | 0…1
  P.9.12 | `. . . . . <BibleTextFeature>` | `<b357>` | 97 | 0…n
  P.9.13 | `. . . . <Religious​TextIdentifier>` | `<b376>` | 88 | 0…1
  ○ | `. . . . <Religious​TextFeature>` | `<religioustextfeature>` |  | 0…n
  P.9.14 | `. . . . . <ReligiousTextFeatureType>` | `<b358>` | 89 | 1
  P.9.15 | `. . . . . <ReligiousTextFeatureCode>` | `<b359>` | 90 | 1
  P.9.16 | `. . . . . <ReligiousText​FeatureDescription>` | `<b360>` | x la tf | 0…n
  Group P.10 Language
  ○ | `. . . <Language>` | `<language>` |  | 0…n
  P.10.1 | `. . . . <LanguageRole>` | `<b253>` | 22 | 1
  P.10.2 | `. . . . <LanguageCode>` | `<b252>` | 74 | 1
  P.10.3 | `. . . . <CountryCode>` | `<b251>` | 91 | 0…1
  P.10.3a | `. . . . <RegionCode>` | `<b398>` | 49 Σ | 0…1
  P.10.4 | `. . . . <ScriptCode>` | `<x420>` | 121 | 0…1
  Group P.11 Extents and other content
  ○ | `. . . <Extent>` | `<extent>` |  | 0…n
  P.11.1 | `. . . . <ExtentType>` | `<b218>` | 23 | 1
  P.11.2 | `. . . . <ExtentValue>` | `<b219>` |  | 0…1
  P.11.3 | `. . . . <ExtentValueRoman>` | `<x421>` |  | 0…1
  P.11.4 | `. . . . <ExtentUnit>` | `<b220>` | 24 | 1
  P.11.5 | `. . . <Illustrated>` | `<x422>` | 152 | 0…1
  P.11.6 | `. . . <NumberOfIllustrations>` | `<b125>` |  | 0…1
  P.11.7 | `. . . <IllustrationsNote>` | `<b062>` | x la tf | 0…n
  ○ | `. . . <AncillaryContent>` | `<ancillarycontent>` |  | 0…n
  P.11.8 | `. . . . <Ancillary​ContentType>` | `<x423>` | 25 | 1
  P.11.9 | `. . . . <Ancillary​ContentDescription>` | `<x424>` | x la tf | 0…n
  P.11.10 | `. . . . <Number>` | `<b257>` |  | 0…1
  Group P.12 Subject
  ○ | `. . . <Subject>` | `<subject>` |  | 0…n
  P.12.1 | `. . . . <MainSubject/>` | `<x425/>` |  | 0…1
  P.12.2 | `. . . . <SubjectSchemeIdentifier>` | `<b067>` | 27 | 1
  P.12.3 | `. . . . <SubjectSchemeName>` | `<b171>` | la | 0…1
  P.12.4 | `. . . . <SubjectSchemeVersion>` | `<b068>` |  | 0…1
  P.12.5 | `. . . . <SubjectCode>` | `<b069>` |  | 0…1
  P.12.6 | `. . . . <SubjectHeadingText>` | `<b070>` | la | 0…n
  ○ | `. . . <NameAsSubject>` | `<nameassubject>` |  | 0…n
  P.12.7 | `. . . . <NameType>` | `<x414>` | 18 | 0…1
  ○ | `. . . . <NameIdentifier>` | `<nameidentifier>` |  | 0…n
  P.12.8 | `. . . . . <NameIDType>` | `<x415>` | 44 | 1
  P.12.9 | `. . . . . <IDTypeName>` | `<b233>` | la | 0…1
  P.12.10 | `. . . . . <IDValue>` | `<b244>` |  | 1
  P.12.11 | `. . . . <PersonName>` | `<b036>` | ck la ts | 0…1
  P.12.12 | `. . . . <PersonName​Inverted>` | `<b037>` | ck la ts | 0…1
  P.12.13 | `. . . . <TitlesBeforeNames>` | `<b038>` | ck la ts | 0…1
  P.12.14 | `. . . . <NamesBeforeKey>` | `<b039>` | ck la ts | 0…1
  P.12.15 | `. . . . <PrefixToKey>` | `<b247>` | ck la ts | 0…1
  P.12.16 | `. . . . <KeyNames>` | `<b040>` | ck la ts | 0…1
  P.12.17 | `. . . . <NamesAfterKey>` | `<b041>` | ck la ts | 0…1
  P.12.18 | `. . . . <SuffixToKey>` | `<b248>` | ck la ts | 0…1
  P.12.19 | `. . . . <LettersAfterNames>` | `<b042>` | ck la ts | 0…1
  P.12.20 | `. . . . <TitlesAfterNames>` | `<b043>` | ck la ts | 0…1
  P.12.21 | `. . . . <CorporateName>` | `<b047>` | ck la ts | 0…n
  P.12.22 | `. . . . <Corporate​NameInverted>` | `<x443>` | ck la ts | 0…n
  ○ | `. . . . <AlternativeName>` | `<alternativename>` | § | 0…n
  P.12.23 | `. . . . . <NameType>` | `<x414>` | 18 § | 1
  ○ | `. . . . . <NameIdentifier>` | `<nameidentifier>` | § | 0…n
  P.12.24 | `. . . . . . <NameIDType>` | `<x415>` | 44 § | 1
  P.12.25 | `. . . . . . <IDTypeName>` | `<b233>` | la § | 0…1
  P.12.26 | `. . . . . . <IDValue>` | `<b244>` | § | 1
  P.12.27 | `. . . . . <PersonName>` | `<b036>` | ck la ts § | 0…1
  P.12.28 | `. . . . . <PersonName​Inverted>` | `<b037>` | ck la ts § | 0…1
  P.12.29 | `. . . . . <TitlesBeforeNames>` | `<b038>` | ck la ts § | 0…1
  P.12.30 | `. . . . . <NamesBeforeKey>` | `<b039>` | ck la ts § | 0…1
  P.12.31 | `. . . . . <PrefixToKey>` | `<b247>` | ck la ts § | 0…1
  P.12.32 | `. . . . . <KeyNames>` | `<b040>` | ck la ts § | 0…1
  P.12.33 | `. . . . . <NamesAfterKey>` | `<b041>` | ck la ts § | 0…1
  P.12.34 | `. . . . . <SuffixToKey>` | `<b248>` | ck la ts § | 0…1
  P.12.35 | `. . . . . <LettersAfterNames>` | `<b042>` | ck la ts § | 0…1
  P.12.36 | `. . . . . <TitlesAfterNames>` | `<b043>` | ck la ts § | 0…1
  P.12.37 | `. . . . . <CorporateName>` | `<b047>` | ck la ts § | 0…n
  P.12.38 | `. . . . . <Corporate​NameInverted>` | `<x443>` | ck la ts § | 0…n
  ○ | `. . . . <SubjectDate>` | `<subjectdate>` | § | 0…n
  P.12.39 | `. . . . . <SubjectDateRole>` | `<x534>` | 177 § | 1
  P.12.41 | `. . . . . <Date>` | `<b306>` | df § | 1
  ○ | `. . . . <ProfessionalAffiliation>` | `<professionalaffiliation>` | § | 0…n
  P.12.42 | `. . . . . <ProfessionalPosition>` | `<b045>` | la § | 0…n
  ○ | `. . . . . <Affiliation​Identifier>` | `<affiliationidentifier>` | Ω | 0…n
  P.12.42a | `. . . . . . <AffiliationIDType>` | `<x580>` | Ω | 1
  P.12.42b | `. . . . . . <IDTypeName>` | `<b233>` | la Ω | 0…1
  P.12.42c | `. . . . . . <IDValue>` | `<b244>` | Ω | 1
  P.12.43 | `. . . . . <Affiliation>` | `<b046>` | la § | 0…1
  Group P.13 Audience
  ○ | `. . . <Audience>` | `<audience>` |  | 0…n
  P.13.1a | `. . . . <MainAudience/>` | `<x583/>` | Ω | 0…1
  P.13.2 | `. . . . <AudienceCodeType>` | `<b204>` | 29 | 1
  P.13.3 | `. . . . <AudienceCodeTypeName>` | `<b205>` | la | 0…1
  P.13.4 | `. . . . <AudienceCodeValue>` | `<b206>` |  | 0…1
  P.13.4a | `. . . . <AudienceHeadingText>` | `<x578>` | la Ψ | 0…n
  ○ | `. . . <AudienceRange>` | `<audiencerange>` |  | 0…n
  P.13.5 | `. . . . <AudienceRangeQualifier>` | `<b074>` | 30 | 1
  P.13.6 | `. . . . <AudienceRangePrecision>` | `<b075>` | 31 | 1
  P.13.7 | `. . . . <AudienceRangeValue>` | `<b076>` |  | 1
  P.13.8 | `. . . . <AudienceRangePrecision>` | `<b075>` | 31 | 0…1
  P.13.9 | `. . . . <AudienceRangeValue>` | `<b076>` |  | 0…1
  P.13.10 | `. . . <AudienceDescription>` | `<b207>` | x la tf | 0…n
  ○ | `. . . <Complexity>` | `<complexity>` |  | 0…n
  P.13.11 | `. . . . <Complexity​SchemeIdentifier>` | `<b077>` | 32 | 1
  P.13.12 | `. . . . <ComplexityCode>` | `<b078>` |  | 1
  Block 2: Marketing collateral
  ○ | `. . <CollateralDetail>` | `<collateraldetail>` |  | 0…1
  Group P.14 Descriptions and other supporting text
  ○ | `. . . <TextContent>` | `<textcontent>` |  | 0…n
  P.14.1 | `. . . . <SequenceNumber>` | `<b034>` | Ω | 0…1
  P.14.1a | `. . . . <TextType>` | `<x426>` | 153 | 1
  P.14.2 | `. . . . <ContentAudience>` | `<x427>` | 154 | 1…n
  ○ | `. . . . <Territory>` | `<territory>` | § | 0…1
  P.14.2a | `. . . . . <CountriesIncluded>` | `<x449>` | 91 § | 0…1
  P.14.2b | `. . . . . <RegionsIncluded>` | `<x450>` | 49 § | 0…1
  P.14.2c | `. . . . . <CountriesExcluded>` | `<x451>` | 91§ | 0…1
  P.14.2d | `. . . . . <RegionsExcluded>` | `<x452>` | 49 § | 0…1
  P.14.3 | `. . . . <Text>` | `<d104>` | x la tf | 1…n
  ○ | `. . . . <ReviewRating>` | `<reviewrating>` | § | 0…1
  P.14.3a | `. . . . . <Rating>` | `<x525>` | § | 1
  P.14.3b | `. . . . . <RatingLimit>` | `<x526>` | § | 0…1
  P.14.3c | `. . . . . <RatingUnits>` | `<x527>` | la § | 0…n
  P.14.4 | `. . . . <TextAuthor>` | `<d107>` | la | 0…n
  P.14.5 | `. . . . <TextSourceCorporate>` | `<b374>` | la | 0…1
  P.14.5a | `. . . . <TextSourceDescription>` | `<x557>` | x la tf Σ | 0…n
  P.14.6 | `. . . . <SourceTitle>` | `<x428>` | la | 0…n
  P.14.6a | `. . . . <TextSourceLink>` | `<x581>` | la Ω | 0…n
  ○ | `. . . . <EpubUsageConstraint>` | `<epubusageconstraint>` | Π | 0…n
  P.14.6b | `. . . . . <EpubUsageType>` | `<x318>` | 145 Π | 1
  P.14.6c | `. . . . . <EpubUsageStatus>` | `<x319>` | 146 Π | 1
  ○ | `. . . . . <EpubUsageLimit>` | `<epubusagelimit>` | Π | 0…n
  P.14.6d | `. . . . . . <Quantity>` | `<x320>` | Π | 1
  P.14.6e | `. . . . . . <EpubUsageUnit>` | `<x321>` | 147 Π | 1
  ○ | `. . . . <EpubLicense>` | `<epublicense>` | Π | 0…n
  P.14.6f | `. . . . . <EpubLicenseName>` | `<x511>` | la Π | 1…n
  ○ | `. . . . . <EpubLicenseExpression>` | `<epublicenseexpression>` | Π | 0…n
  P.14.6g | `. . . . . . <EpubLicenseExpression​Type>` | `<x508>` | 218 Π | 1
  P.14.6h | `. . . . . . <EpubLicenseExpression​TypeName>` | `<x509>` | la Π | 0…1
  P.14.6i | `. . . . . . <EpubLicenseExpression​Link>` | `<x510>` | Π | 1
  ○ | `. . . . . <EpubLicenseDate>` | `<epublicensedate>` | Π | 0…n
  P.14.6j | `. . . . . . <EpubLicenseDateRole>` | `<x585>` | 260 Π | 1
  P.14.6k | `. . . . . . <Date>` | `<b306>` | df Π | 1
  ○ | `. . . . <ContentDate>` | `<contentdate>` |  | 0…n
  P.14.7 | `. . . . . <ContentDateRole>` | `<x429>` | 155 | 1
  P.14.9 | `. . . . . <Date>` | `<b306>` | df | 1
  Group P.15 Cited content
  ○ | `. . . <CitedContent>` | `<citedcontent>` |  | 0…n
  P.15.1 | `. . . . <SequenceNumber>` | `<b034>` | Ω | 0…1
  P.15.1a | `. . . . <CitedContentType>` | `<x430>` | 156 | 1
  P.15.2 | `. . . . <ContentAudience>` | `<x427>` | 154 | 0…n
  ○ | `. . . . <Territory>` | `<territory>` | § | 0…1
  P.15.2a | `. . . . . <CountriesIncluded>` | `<x449>` | 91 § | 0…1
  P.15.2b | `. . . . . <RegionsIncluded>` | `<x450>` | 49 § | 0…1
  P.15.2c | `. . . . . <CountriesExcluded>` | `<x451>` | 91 § | 0…1
  P.15.2d | `. . . . . <RegionsExcluded>` | `<x452>` | 49 § | 0…1
  P.15.3 | `. . . . <SourceType>` | `<x431>` | 157 | 0…1
  ○ | `. . . . <ReviewRating>` | `<reviewrating>` | § | 0…1
  P.15.3a | `. . . . . <Rating>` | `<x525>` | § | 1
  P.15.3b | `. . . . . <RatingLimit>` | `<x526>` | § | 0…1
  P.15.3c | `. . . . . <RatingUnits>` | `<x527>` | la § | 0…n
  P.15.4 | `. . . . <SourceTitle>` | `<x428>` | la | 0…n
  P.15.5 | `. . . . <ListName>` | `<x432>` | la | 0…n
  P.15.6 | `. . . . <PositionOnList>` | `<x433>` |  | 0…1
  P.15.7 | `. . . . <CitationNote>` | `<x434>` | x la tf | 0…n
  P.15.8 | `. . . . <ResourceLink>` | `<x435>` | la | 0…n
  ○ | `. . . . <ContentDate>` | `<contentdate>` |  | 0…n
  P.15.9 | `. . . . . <ContentDateRole>` | `<x429>` | 155 | 1
  P.15.11 | `. . . . . <Date>` | `<b306>` | df | 1
  Group P.16 Links to supporting resources
  ○ | `. . . <SupportingResource>` | `<supportingresource>` |  | 0…n
  P.16.1 | `. . . . <SequenceNumber>` | `<b034>` | Ω | 0…1
  P.16.1a | `. . . . <ResourceContentType>` | `<x436>` | 158 | 1
  P.16.2 | `. . . . <ContentAudience>` | `<x427>` | 154 | 1…n
  ○ | `. . . . <Territory>` | `<territory>` | § | 0…1
  P.16.2a | `. . . . . <CountriesIncluded>` | `<x449>` | 91 § | 0…1
  P.16.2b | `. . . . . <RegionsIncluded>` | `<x450>` | 49 § | 0…1
  P.16.2c | `. . . . . <CountriesExcluded>` | `<x451>` | 91 § | 0…1
  P.16.2d | `. . . . . <RegionsExcluded>` | `<x452>` | 49 § | 0…1
  P.16.3 | `. . . . <ResourceMode>` | `<x437>` | 159 | 1
  ○ | `. . . . <ResourceFeature>` | `<resourcefeature>` |  | 0…n
  P.16.4 | `. . . . . <Resource​FeatureType>` | `<x438>` | 160 | 1
  P.16.5 | `. . . . . <FeatureValue>` | `<x439>` |  | 0…1
  P.16.6 | `. . . . . <FeatureNote>` | `<x440>` | x la tf | 0…n
  ○ | `. . . . <ResourceVersion>` | `<resourceversion>` |  | 1…n
  P.16.7 | `. . . . . <ResourceForm>` | `<x441>` | 161 | 1
  ○ | `. . . . . <ResourceVersion​Feature>` | `<resourceversionfeature>` |  | 0…n
  P.16.8 | `. . . . . . <ResourceVersion​FeatureType>` | `<x442>` | 162 | 1
  P.16.9 | `. . . . . . <FeatureValue>` | `<x439>` |  | 0…1
  P.16.10 | `. . . . . . <FeatureNote>` | `<x440>` | x la tf | 0…n
  P.16.11 | `. . . . . <ResourceLink>` | `<x435>` | la | 1…n
  ○ | `. . . . . <EpubUsageConstraint>` | `<epubusageconstraint>` | Π | 0…n
  P.16.11a | `. . . . . . <EpubUsageType>` | `<x318>` | 145 Π | 1
  P.16.11b | `. . . . . . <EpubUsageStatus>` | `<x319>` | 146 Π | 1
  ○ | `. . . . . . <EpubUsageLimit>` | `<epubusagelimit>` | Π | 0…n
  P.16.11c | `. . . . . . . <Quantity>` | `<x320>` | Π | 1
  P.16.11d | `. . . . . . . <EpubUsageUnit>` | `<x321>` | 147 Π | 1
  ○ | `. . . . . <EpubLicense>` | `<epublicense>` | Π | 0…n
  P.16.11e | `. . . . . . <EpubLicenseName>` | `<x511>` | la Π | 1…n
  ○ | `. . . . . . <EpubLicenseExpression>` | `<epublicenseexpression>` | Π | 0…n
  P.16.11f | `. . . . . . . <EpubLicenseExpression​Type>` | `<x508>` | 218 Π | 1
  P.16.11g | `. . . . . . . <EpubLicenseExpression​TypeName>` | `<x509>` | la Π | 0…1
  P.16.11h | `. . . . . . . <EpubLicenseExpression​Link>` | `<x510>` | Π | 1
  ○ | `. . . . . . <EpubLicenseDate>` | `<epublicensedate>` | Π | 0…n
  P.16.11i | `. . . . . . . <EpubLicenseDateRole>` | `<x585>` | 260 Π | 1
  P.16.11j | `. . . . . . . <Date>` | `<b306>` | df Π | 1
  ○ | `. . . . . <ContentDate>` | `<contentdate>` |  | 0…n
  P.16.12 | `. . . . . . <ContentDateRole>` | `<x429>` | 155 | 1
  P.16.14 | `. . . . . . <Date>` | `<b306>` | df | 1
  Group P.17 Prizes
  ○ | `. . . <Prize>` | `<prize>` |  | 0…n
  P.17.1 | `. . . . <SequenceNumber>` | `<b034>` | Ω | 0…1
  ○ | `. . . . <PrizeIdentifier>` | `<prizeidentifier>` | Π | 0…n
  P.17.1a | `. . . . . <PrizeIDType>` | `<x589>` | 263 Π | 1
  P.17.1b | `. . . . . <IDTypeName>` | `<b233>` | la Π | 0…1
  P.17.1c | `. . . . . <IDValue>` | `<b244>` | Π | 1
  P.17.1d | `. . . . <PrizeName>` | `<g126>` | la | 1…n
  P.17.2 | `. . . . <PrizeYear>` | `<g127>` |  | 0…1
  P.17.2a | `. . . . <AwardingBody>` | `<x584>` | la Ω | 0…n
  P.17.3 | `. . . . <PrizeCountry>` | `<g128>` | 91 | 0…1
  P.17.3a | `. . . . <PrizeRegion>` | `<x556>` | 49 Σ | 0…1
  P.17.4 | `. . . . <PrizeCode>` | `<g129>` | 41 | 0…1
  P.17.4a | `. . . . <PrizeStatement>` | `<x503>` | x la tf ‡ | 0…n
  P.17.5 | `. . . . <PrizeJury>` | `<g343>` | x la tf | 0…n
  Block 7: Promotion detail
  ○ | `. . <PromotionDetail>` | `<promotiondetail>` | Σ | 0…1
  Group P.27 Promotional events
  ○ | `. . . <PromotionalEvent>` | `<promotionalevent>` | Σ | 0…n
  ○ | `. . . . <EventIdentifier>` | `<eventidentifier>` | Σ | 0…n
  P.27.1 | `. . . . . <EventIDType>` | `<x547>` | 244 Σ | 1
  P.27.2 | `. . . . . <IDTypeName>` | `<b233>` | la Σ | 0…1
  P.27.3 | `. . . . . <IDValue>` | `<b244>` | Σ | 1
  P.27.4 | `. . . . <EventType>` | `<x548>` | 245 Σ | 1…n
  P.27.5 | `. . . . <EventStatus>` | `<x549>` | 246 Σ | 0…1
  P.27.6 | `. . . . <ContentAudience>` | `<x427>` | 154 Σ | 1…n
  P.27.7 | `. . . . <EventName>` | `<x516>` | la Σ | 1…n
  ○ | `. . . . <ContributorReference>` | `<contributorreference>` | Σ | 0…n
  P.27.8 | `. . . . . <SequenceNumber>` | `<b034>` | Σ | 0…1
  P.27.9 | `. . . . . <ContributorRole>` | `<b035>` | 17 Σ | 1…n
  ○ | `. . . . . <NameIdentifier>` | `<nameidentifier>` | Σ | 1…n
  P.27.10 | `. . . . . . <NameIDType>` | `<x415>` | 44 Σ | 1
  P.27.11 | `. . . . . . <IDTypeName>` | `<b233>` | la Σ | 0…1
  P.27.12 | `. . . . . . <IDValue>` | `<b244>` | Σ | 1
  ○ | `. . . . <Contributor>` | `<contributor>` | Σ | 0…n
  P.27.13 | `. . . . . <SequenceNumber>` | `<b034>` | Σ | 0…1
  P.27.14 | `. . . . . <ContributorRole>` | `<b035>` | 17 Σ | 1…n
  P.27.15 | `. . . . . <FromLanguage>` | `<x412>` | 74 Σ | 0…n
  P.27.16 | `. . . . . <ToLanguage>` | `<x413>` | 74 Σ | 0…n
  P.27.17 | `. . . . . <NameType>` | `<x414>` | 18 Σ | 0…1
  ○ | `. . . . . <NameIdentifier>` | `<nameidentifier>` | Σ | 0…n
  P.27.18 | `. . . . . . <NameIDType>` | `<x415>` | 44 Σ | 1
  P.27.19 | `. . . . . . <IDTypeName>` | `<b233>` | la Σ | 0…1
  P.27.20 | `. . . . . . <IDValue>` | `<b244>` | Σ | 1
  P.27.21 | `. . . . . <PersonName>` | `<b036>` | ck la ts Σ | 0…1
  P.27.22 | `. . . . . <Person​NameInverted>` | `<b037>` | ck la ts Σ | 0…1
  P.27.23 | `. . . . . <TitlesBeforeNames>` | `<b038>` | ck la ts Σ | 0…1
  P.27.24 | `. . . . . <NamesBeforeKey>` | `<b039>` | ck la ts Σ | 0…1
  P.27.25 | `. . . . . <PrefixToKey>` | `<b247>` | ck la ts Σ | 0…1
  P.27.26 | `. . . . . <KeyNames>` | `<b040>` | ck la ts Σ | 0…1
  P.27.27 | `. . . . . <NamesAfterKey>` | `<b041>` | ck la ts Σ | 0…1
  P.27.28 | `. . . . . <SuffixToKey>` | `<b248>` | ck la ts Σ | 0…1
  P.27.29 | `. . . . . <LettersAfterNames>` | `<b042>` | ck la ts Σ | 0…1
  P.27.30 | `. . . . . <TitlesAfterNames>` | `<b043>` | ck la ts Σ | 0…1
  P.27.31 | `. . . . . <CorporateName>` | `<b047>` | ck la ts Σ | 0…n
  P.27.32 | `. . . . . <Corporate​NameInverted>` | `<x443>` | ck la ts Σ | 0…n
  P.27.32a | `. . . . . <UnnamedPersons>` | `<b249>` | 19 Σ | 0…1
  ○ | `. . . . . <AlternativeName>` | `<alternativename>` | Σ | 0…n
  P.27.33 | `. . . . . . <NameType>` | `<x414>` | 18 Σ | 1
  ○ | `. . . . . . <NameIdentifier>` | `<nameidentifier>` | Σ | 0…n
  P.27.34 | `. . . . . . . <NameIDType>` | `<x415>` | 44 Σ | 1
  P.27.35 | `. . . . . . . <IDTypeName>` | `<b233>` | la Σ | 0…1
  P.27.36 | `. . . . . . . <IDValue>` | `<b244>` | Σ | 1
  P.27.37 | `. . . . . . <PersonName>` | `<b036>` | ck la ts Σ | 0…1
  P.27.38 | `. . . . . . <Person​NameInverted>` | `<b037>` | ck la ts Σ | 0…1
  P.27.39 | `. . . . . . <TitlesBeforeNames>` | `<b038>` | ck la ts Σ | 0…1
  P.27.40 | `. . . . . . <NamesBeforeKey>` | `<b039>` | ck la ts Σ | 0…1
  P.27.41 | `. . . . . . <PrefixToKey>` | `<b247>` | ck la ts Σ | 0…1
  P.27.42 | `. . . . . . <KeyNames>` | `<b040>` | ck la ts Σ | 0…1
  P.27.43 | `. . . . . . <NamesAfterKey>` | `<b041>` | ck la ts Σ | 0…1
  P.27.44 | `. . . . . . <SuffixToKey>` | `<b248>` | ck la ts Σ | 0…1
  P.27.45 | `. . . . . . <LettersAfterNames>` | `<b042>` | ck la ts Σ | 0…1
  P.27.46 | `. . . . . . <TitlesAfterNames>` | `<b043>` | ck la ts Σ | 0…1
  P.27.47 | `. . . . . . <CorporateName>` | `<b047>` | ck la ts Σ | 0…n
  P.27.48 | `. . . . . . <Corporate​NameInverted>` | `<x443>` | ck la ts Σ | 0…n
  ○ | `. . . . . <ContributorDate>` | `<contributordate>` | Σ | 0…n
  P.27.49 | `. . . . . . <Contributor​DateRole>` | `<x417>` | 177 Σ | 1
  P.27.51 | `. . . . . . <Date>` | `<b306>` | df Σ | 1
  ○ | `. . . . . <Professional​Affiliation>` | `<professionalaffiliation>` | Σ | 0…n
  P.27.52 | `. . . . . . <Professional​Position>` | `<b045>` | la Σ | 0…n
  ○ | `. . . . . . <Affiliation​Identifier>` | `<affiliationidentifier>` | Ω | 0…n
  P.27.52a | `. . . . . . . <AffiliationIDType>` | `<x580>` | 44 Ω | 1
  P.27.52b | `. . . . . . . <IDTypeName>` | `<b233>` | la Ω | 0…1
  P.27.52c | `. . . . . . . <IDValue>` | `<b244>` | Ω | 1
  P.27.53 | `. . . . . . <Affiliation>` | `<b046>` | la Σ | 0…1
  ○ | `. . . . . <Prize>` | `<prize>` | Σ | 0…n
  P.27.53a | `. . . . . . <SequenceNumber>` | `<b034>` | Ω | 0…1
  ○ | `. . . . . . <PrizeIdentifier>` | `<prizeidentifier>` | Π | 0…n
  P.27.53b | `. . . . . . . <PrizeIDType>` | `<x589>` | 263 Π | 1
  P.27.53c | `. . . . . . . <IDTypeName>` | `<233>` | la Π | 0…1
  P.27.53d | `. . . . . . . <IDValue>` | `<b244>` | Π | 1
  P.27.53e | `. . . . . . <PrizeName>` | `<g126>` | la Σ | 1…n
  P.27.53f | `. . . . . . <PrizeYear>` | `<g127>` | Σ | 0…1
  P.27.53g | `. . . . . . <AwardingBody>` | `<x584>` | la Ω | 0…n
  P.27.53h | `. . . . . . <PrizeCountry>` | `<g128>` | 91 Σ | 0…1
  P.27.53i | `. . . . . . <PrizeRegion>` | `<x556>` | 49 Σ | 0…1
  P.27.53j | `. . . . . . <PrizeCode>` | `<g129>` | 41 Σ | 0…1
  P.27.53k | `. . . . . . <PrizeStatement>` | `<x503>` | x la tf Σ | 0…n
  P.27.53l | `. . . . . . <PrizeJury>` | `<g343>` | x la tf Σ | 0…n
  P.27.54 | `. . . . . <BiographicalNote>` | `<b044>` | x la tf Σ | 0…n
  ○ | `. . . . . <Website>` | `<website>` | Σ | 0…n
  P.27.55 | `. . . . . . <WebsiteRole>` | `<b367>` | 73 Σ | 0…1
  P.27.56 | `. . . . . . <WebsiteDescription>` | `<b294>` | x la tf Σ | 0…n
  P.27.57 | `. . . . . . <WebsiteLink>` | `<b295>` | la Σ | 1…n
  P.27.58 | `. . . . . <ContributorDescription>` | `<b048>` | x la tf Σ | 0…n
  ○ | `. . . . . <ContributorPlace>` | `<contributorplace>` | Σ | 0…n
  P.27.60 | `. . . . . . <Contributor​PlaceRelator>` | `<x418>` | 151 Σ | 1
  P.27.61 | `. . . . . . <CountryCode>` | `<b251>` | 91 Σ | 0…1
  P.27.62 | `. . . . . . <RegionCode>` | `<b398>` | 49 Σ | 0…1
  P.27.62a | `. . . . . . <LocationName>` | `<j349>` | la Σ | 0…n
  P.27.63 | `. . . . <ContributorStatement>` | `<b049>` | x la tf Σ | 0…n
  P.27.64 | `. . . . <NoContributor/>` | `<n339/>` | Σ | 0…1
  P.27.65 | `. . . . <EventDescription>` | `<x550>` | x la tf Σ | 0…n
  ○ | `. . . . <EventOccurrence>` | `<eventoccurrence>` | Σ | 1…n
  ○ | `. . . . . <EventIdentifier>` | `<eventidentifier>` | Σ | 0…n
  P.27.66 | `. . . . . . <EventIDType>` | `<x547>` | 244 Σ | 1
  P.27.67 | `. . . . . . <IDTypeName>` | `<b233>` | la Σ | 0…1
  P.27.68 | `. . . . . . <IDValue>` | `<b244>` | Σ | 1
  ○ | `. . . . . <OccurrenceDate>` | `<occurrencedate>` | Σ | 1…n
  P.27.69 | `. . . . . . <OccurrenceDateRole>` | `<x554>` | 247 Σ | 1
  P.27.71 | `. . . . . . <Date>` | `<b306>` | df Σ | 1
  P.27.72 | `. . . . . <EventStatus>` | `<x549>` | 246 Σ | 1
  P.27.73 | `. . . . . <CountryCode>` | `<b251>` | 91 Σ | 0…1
  P.27.74 | `. . . . . <RegionCode>` | `<b398>` | 49 Σ | 0…1
  P.27.75 | `. . . . . <LocationName>` | `<j349>` | la Σ | 0…n
  P.27.76 | `. . . . . <VenueName>` | `<x551>` | la Σ | 0…1
  P.27.77 | `. . . . . <StreetAddress>` | `<x552>` | Σ | 0…1
  P.27.77a | `. . . . . <PostalCode>` | `<x590>` | Λ | 0…1
  P.27.78 | `. . . . . <VenueNote>` | `<x553>` | x la tf Σ | 0…n
  P.27.79 | `. . . . . <EventDescription>` | `<x550>` | x la tf Σ | 0…n
  ○ | `. . . . . <SupportingResource>` | `<supportingresource>` | Ψ | 0…n
  P.27.79a | `. . . . . . <SequenceNumber>` | `<b034>` | Ω | 0…1
  P.27.79b | `. . . . . . <ResourceContentType>` | `<x436>` | 158 Ψ | 1
  P.27.79c | `. . . . . . <ContentAudience>` | `<x427>` | 154 Ψ | 1…n
  ○ | `. . . . . . <Territory>` | `<territory>` | Ψ | 0…1
  P.27.79d | `. . . . . . . <CountriesIncluded>` | `<x449>` | 91 Ψ | 0…1
  P.27.79e | `. . . . . . . <RegionsIncluded>` | `<x450>` | 49 Ψ | 0…1
  P.27.79f | `. . . . . . . <CountriesExcluded>` | `<x451>` | 91 Ψ | 0…1
  P.27.79g | `. . . . . . . <RegionsExcluded>` | `<x452>` | 49 Ψ | 0…1
  P.27.79h | `. . . . . . <ResourceMode>` | `<x437>` | 159 Ψ | 1
  ○ | `. . . . . . <ResourceFeature>` | `<resourcefeature>` | Ψ | 0…n
  P.27.79i | `. . . . . . . <Resource​FeatureType>` | `<x438>` | 160 Ψ | 1
  P.27.79j | `. . . . . . . <FeatureValue>` | `<x439>` | Ψ | 0…1
  P.27.79k | `. . . . . . . <FeatureNote>` | `<x440>` | x la tf Ψ | 0…n
  ○ | `. . . . . . <ResourceVersion>` | `<resourceversion>` | Ψ | 1…n
  P.27.79l | `. . . . . . . <ResourceForm>` | `<x441>` | 161 Ψ | 1
  ○ | `. . . . . . . <ResourceVersion​Feature>` | `<resourceversionfeature>` | Ψ | 0…n
  P.27.79m | `. . . . . . . . <ResourceVersion​FeatureType>` | `<x442>` | 162 Ψ | 1
  P.27.79n | `. . . . . . . . <FeatureValue>` | `<x439>` | Ψ | 0…1
  P.27.79o | `. . . . . . . . <FeatureNote>` | `<x440>` | x la tf Ψ | 0…n
  P.27.79p | `. . . . . . . <ResourceLink>` | `<x435>` | la Ψ | 1…n
  ○ | `. . . . . . . <EpubUsageConstraint>` | `<epubusageconstraint>` | Π | 0…n
  P.27.79q | `. . . . . . . . <EpubUsageType>` | `<x318>` | 145 Π | 1
  P.27.79r | `. . . . . . . . <EpubUsageStatus>` | `<x319>` | 146 Π | 1
  ○ | `. . . . . . . . <EpubUsageLimit>` | `<epubusagelimit>` | Π | 0…n
  P.27.79s | `. . . . . . . . . <Quantity>` | `<x320>` | Π | 1
  P.27.79t | `. . . . . . . . . <EpubUsageUnit>` | `<x321>` | 147 Π | 1
  ○ | `. . . . . . . <EpubLicense>` | `<epublicense>` | Π | 0…n
  P.27.79u | `. . . . . . . . <EpubLicenseName>` | `<x511>` | la Π | 1…n
  ○ | `. . . . . . . . <EpubLicenseExpression>` | `<epublicenseexpression>` | Π | 0…n
  P.27.79v | `. . . . . . . . . <EpubLicenseExpression​Type>` | `<x508>` | 218 Π | 1
  P.27.79w | `. . . . . . . . . <EpubLicenseExpression​TypeName>` | `<x509>` | la Π | 0…1
  P.27.79x | `. . . . . . . . . <EpubLicenseExpression​Link>` | `<x510>` | Π | 1
  ○ | `. . . . . . . . <EpubLicenseDate>` | `<epublicensedate>` | Π | 0…n
  P.27.79y | `. . . . . . . . . <EpubLicenseDateRole>` | `<x585>` | 260 Π | 1
  P.27.79z | `. . . . . . . . . <Date>` | `<b306>` | df Π | 1
  ○ | `. . . . . . . <ContentDate>` | `<contentdate>` | Ψ | 0…n
  P.27.79α | `. . . . . . . . <ContentDateRole>` | `<x429>` | 155 Ψ | 1
  P.27.79β | `. . . . . . . . <Date>` | `<b306>` | df Ψ | 1
  ○ | `. . . . . <EventSponsor>` | `<eventsponsor>` | Σ | 0…n
  ○ | `. . . . . . <Event​SponsorIdentifier>` | `<event​sponsoridentifier>` | Σ | 0…n
  P.27.80 | `. . . . . . . <Event​SponsorIDType>` | `<x522>` | 44 Σ | 1
  P.27.81 | `. . . . . . . <IDTypeName>` | `<b233>` | la Σ | 0…1
  P.27.82 | `. . . . . . . <IDValue>` | `<b244>` | Σ | 1
  P.27.83 | `. . . . . . <PersonName>` | `<b036>` | ck la ts Σ | 0…1
  P.27.84 | `. . . . . . <CorporateName>` | `<b047>` | ck la ts Σ | 0…1
  ○ | `. . . . . <Website>` | `<website>` | Σ | 0…n
  P.27.85 | `. . . . . . <WebsiteRole>` | `<b367>` | 73 Σ | 0…1
  P.27.86 | `. . . . . . <WebsiteDescription>` | `<b294>` | x la tf Σ | 0…n
  P.27.87 | `. . . . . . <WebsiteLink>` | `<b295>` | la Σ | 1…n
  ○ | `. . . . <SupportingResource>` | `<supportingresource>` | Ψ | 0…n
  P.27.87a | `. . . . . <SequenceNumber>` | `<b034>` | Ω | 0…1
  P.27.87b | `. . . . . <ResourceContentType>` | `<x436>` | 158 Ψ | 1
  P.27.87c | `. . . . . <ContentAudience>` | `<x427>` | 154 Ψ | 1…n
  ○ | `. . . . . <Territory>` | `<territory>` | Ψ | 0…1
  P.27.87d | `. . . . . . <CountriesIncluded>` | `<x449>` | 91 Ψ | 0…1
  P.27.87e | `. . . . . . <RegionsIncluded>` | `<x450>` | 49 Ψ | 0…1
  P.27.87f | `. . . . . . <CountriesExcluded>` | `<x451>` | 91 Ψ | 0…1
  P.27.87g | `. . . . . . <RegionsExcluded>` | `<x452>` | 49 Ψ | 0…1
  P.27.87h | `. . . . . <ResourceMode>` | `<x437>` | 159 Ψ | 1
  ○ | `. . . . . <ResourceFeature>` | `<resourcefeature>` | Ψ | 0…n
  P.27.87i | `. . . . . . <Resource​FeatureType>` | `<x438>` | 160 Ψ | 1
  P.27.87j | `. . . . . . <FeatureValue>` | `<x439>` | Ψ | 0…1
  P.27.87k | `. . . . . . <FeatureNote>` | `<x440>` | x la tf Ψ | 0…n
  ○ | `. . . . . <ResourceVersion>` | `<resourceversion>` | Ψ | 1…n
  P.27.87l | `. . . . . . <ResourceForm>` | `<x441>` | 161 Ψ | 1
  ○ | `. . . . . . <ResourceVersion​Feature>` | `<resourceversionfeature>` | Ψ | 0…n
  P.27.87m | `. . . . . . . <ResourceVersion​FeatureType>` | `<x442>` | 162 Ψ | 1
  P.27.87n | `. . . . . . . <FeatureValue>` | `<x439>` | Ψ | 0…1
  P.27.87o | `. . . . . . . <FeatureNote>` | `<x440>` | x la tf Ψ | 0…n
  P.27.87p | `. . . . . . <ResourceLink>` | `<x435>` | la Ψ | 1…n
  ○ | `. . . . . . <EpubUsageConstraint>` | `<epubusageconstraint>` | Π | 0…n
  P.27.87q | `. . . . . . . <EpubUsageType>` | `<x318>` | 145 Π | 1
  P.27.87r | `. . . . . . . <EpubUsageStatus>` | `<x319>` | 146 Π | 1
  ○ | `. . . . . . . <EpubUsageLimit>` | `<epubusagelimit>` | Π | 0…n
  P.27.87s | `. . . . . . . . <Quantity>` | `<x320>` | Π | 1
  P.27.87t | `. . . . . . . . <EpubUsageUnit>` | `<x321>` | 147 Π | 1
  ○ | `. . . . . . <EpubLicense>` | `<epublicense>` | Π | 0…n
  P.27.87u | `. . . . . . . <EpubLicenseName>` | `<x511>` | la Π | 1…n
  ○ | `. . . . . . . <EpubLicenseExpression>` | `<epublicenseexpression>` | Π | 0…n
  P.27.87v | `. . . . . . . . <EpubLicenseExpression​Type>` | `<x508>` | 218 Π | 1
  P.27.87w | `. . . . . . . . <EpubLicenseExpression​TypeName>` | `<x509>` | la Π | 0…1
  P.27.87x | `. . . . . . . . <EpubLicenseExpression​Link>` | `<x510>` | Π | 1
  ○ | `. . . . . . . <EpubLicenseDate>` | `<epublicensedate>` | Π | 0…n
  P.27.87y | `. . . . . . . . <EpubLicenseDateRole>` | `<x585>` | 260 Π | 1
  P.27.87z | `. . . . . . . . <Date>` | `<b306>` | df Π | 1
  ○ | `. . . . . . <ContentDate>` | `<contentdate>` | Ψ | 0…n
  P.27.87α | `. . . . . . . <ContentDateRole>` | `<x429>` | 155 Ψ | 1
  P.27.87β | `. . . . . . . <Date>` | `<b306>` | df Ψ | 1
  ○ | `. . . . <EventSponsor>` | `<eventsponsor>` | Σ | 0…n
  ○ | `. . . . . <Event​SponsorIdentifier>` | `<event​sponsoridentifier>` | Σ | 0…n
  P.27.88 | `. . . . . . <Event​SponsorIDType>` | `<x522>` | 44 Σ | 1
  P.27.89 | `. . . . . . <IDTypeName>` | `<b233>` | la Σ | 0…1
  P.27.90 | `. . . . . . <IDValue>` | `<b244>` | Σ | 1
  P.27.91 | `. . . . . <PersonName>` | `<b036>` | ck la ts Σ | 0…1
  P.27.92 | `. . . . . <CorporateName>` | `<b047>` | ck la ts Σ | 0…1
  ○ | `. . . . <Website>` | `<website>` | Σ | 0…n
  P.27.93 | `. . . . . <WebsiteRole>` | `<b367>` | 73 Σ | 0…1
  P.27.94 | `. . . . . <WebsiteDescription>` | `<b294>` | x la tf Σ | 0…n
  P.27.95 | `. . . . . <WebsiteLink>` | `<b295>` | la Σ | 1…n
  Block 3: Content detail
  ○ | `. . <ContentDetail>` | `<contentdetail>` |  | 0…1
  Group P.18 Content items
  ○ | `. . . <ContentItem>` | `<contentitem>` |  | 0…n
  P.18.1 | `. . . . <LevelSequenceNumber>` | `<b284>` |  | 0…1
  ○ | `. . . . <TextItem>` | `<textitem>` |  | 0…1
  P.18.2 | `. . . . . <TextItemType>` | `<b290>` | 42 | 1
  ○ | `. . . . . <TextItemIdentifier>` | `<textitemidentifier>` |  | 0…n
  P.18.3 | `. . . . . . <TextItemIDType>` | `<b285>` | 43 | 1
  P.18.4 | `. . . . . . <IDTypeName>` | `<b233>` | la | 0…1
  P.18.5 | `. . . . . . <IDValue>` | `<b244>` |  | 1
  ○ | `. . . . . <PageRun>` | `<pagerun>` |  | 0…n
  P.18.6 | `. . . . . . <First​PageNumber>` | `<b286>` |  | 1
  P.18.7 | `. . . . . . <Last​PageNumber>` | `<b287>` |  | 0…1
  P.18.8 | `. . . . . <NumberOfPages>` | `<b061>` |  | 0…1
  ○ | `. . . . <AVItem>` | `<avitem>` | Φ | 0…1
  P.18.8a | `. . . . . <AVItemType>` | `<x540>` | 240 Φ | 1
  ○ | `. . . . . <AVItemIdentifier>` | `<avitemidentifier>` | Φ | 0…n
  P.18.8b | `. . . . . . <AVItemIDType>` | `<x541>` | 241 Φ | 1
  P.18.8c | `. . . . . . <IDTypeName>` | `<b233>` | la Φ | 0…1
  P.18.8d | `. . . . . . <IDValue>` | `<b244>` | Φ | 1
  ○ | `. . . . . <TimeRun>` | `<timerun>` | Φ | 0…n
  P.18.8e | `. . . . . . <Start​Time>` | `<x542>` | Φ | 1
  P.18.8f | `. . . . . . <End​Time>` | `<x543>` | Φ | 0…1
  P.18.8g | `. . . . . <AVDuration>` | `<x544>` | Φ | 0…1
  ○ | `. . . . <EpubUsageConstraint>` | `<epubusageconstraint>` | Ω | 0…n
  P.18.8h | `. . . . . <EpubUsageType>` | `<x318>` | 145 Ω | 1
  P.18.8i | `. . . . . <EpubUsageStatus>` | `<x319>` | 146 Ω | 1
  ○ | `. . . . . <EpubUsageLimit>` | `<epubusagelimit>` | Ω | 0…n
  P.18.8j | `. . . . . . <Quantity>` | `<x320>` | Ω | 1
  P.18.8k | `. . . . . . <EpubUsageUnit>` | `<x321>` | 147 Ω | 1
  ○ | `. . . . <EpubLicense>` | `<epublicense>` | Ω | 0…n
  P.18.8l | `. . . . . <EpubLicenseName>` | `<x511>` | la Ω | 1…n
  ○ | `. . . . . <EpubLicenseExpression>` | `<epublicenseexpression>` | Ω | 0…n
  P.18.8m | `. . . . . . <EpubLicenseExpression​Type>` | `<x508>` | 218 Ω | 1
  P.18.8n | `. . . . . . <EpubLicenseExpression​TypeName>` | `<x509>` | la Ω | 0…1
  P.18.8o | `. . . . . . <EpubLicenseExpression​Link>` | `<x510>` | Ω | 1
  ○ | `. . . . . <EpubLicenseDate>` | `<epublicensedate>` | Ω | 0…n
  P.18.8p | `. . . . . . <EpubLicenseDateRole>` | `<x585>` | 260 Ω | 1
  P.18.8q | `. . . . . . <Date>` | `<b306>` | df Ω | 1
  P.18.9 | `. . . . <ComponentTypeName>` | `<b288>` | la | 0…1
  P.18.10 | `. . . . <ComponentNumber>` | `<b289>` |  | 0…1
  ○ | `. . . . <TitleDetail>` | `<titledetail>` |  | 1…n
  P.18.11 | `. . . . . <TitleType>` | `<b202>` | 15 | 1
  ○ | `. . . . . <TitleElement>` | `<titleelement>` |  | 1…n
  P.18.11a | `. . . . . . <SequenceNumber>` | `<b034>` | † | 0…1
  P.18.12 | `. . . . . . <Title​ElementLevel>` | `<x409>` | 149 | 1
  P.18.13 | `. . . . . . <PartNumber>` | `<x410>` | la ts | 0…1
  P.18.14 | `. . . . . . <YearOfAnnual>` | `<b020>` |  | 0…1
  P.18.15 | `. . . . . . <TitleText>` | `<b203>` | ck la ts tc | 0…1
  P.18.16 | `. . . . . . <TitlePrefix>` | `<b030>` | ck la ts tc | 0…1
  P.18.16a | `. . . . . . <NoPrefix/>` | `<x501/>` | ‡ | 0…1
  P.18.17 | `. . . . . . <Title​WithoutPrefix>` | `<b031>` | ck la ts tc | 0…1
  P.18.18 | `. . . . . . <Subtitle>` | `<b029>` | ck la ts tc | 0…1
  P.18.18a | `. . . . . <TitleStatement>` | `<x478>` | x la tf † | 0…1
  ○ | `. . . . <Contributor>` | `<contributor>` |  | 0…n
  P.18.19 | `. . . . . <SequenceNumber>` | `<b034>` |  | 0…1
  P.18.20 | `. . . . . <ContributorRole>` | `<b035>` | 17 | 1…n
  P.18.21 | `. . . . . <FromLanguage>` | `<x412>` | 74 | 0…n
  P.18.22 | `. . . . . <ToLanguage>` | `<x413>` | 74 | 0…n
  P.18.23 | `. . . . . <NameType>` | `<x414>` | 18 | 0…1
  ○ | `. . . . . <NameIdentifier>` | `<nameidentifier>` |  | 0…n
  P.18.24 | `. . . . . . <NameIDType>` | `<x415>` | 44 | 1
  P.18.25 | `. . . . . . <IDTypeName>` | `<b233>` | la | 0…1
  P.18.26 | `. . . . . . <IDValue>` | `<b244>` |  | 1
  P.18.27 | `. . . . . <PersonName>` | `<b036>` | ck la ts | 0…1
  P.18.28 | `. . . . . <Person​NameInverted>` | `<b037>` | ck la ts | 0…1
  P.18.29 | `. . . . . <TitlesBeforeNames>` | `<b038>` | ck la ts | 0…1
  P.18.30 | `. . . . . <NamesBeforeKey>` | `<b039>` | ck la ts | 0…1
  P.18.31 | `. . . . . <PrefixToKey>` | `<b247>` | ck la ts | 0…1
  P.18.32 | `. . . . . <KeyNames>` | `<b040>` | ck la ts | 0…1
  P.18.33 | `. . . . . <NamesAfterKey>` | `<b041>` | ck la ts | 0…1
  P.18.34 | `. . . . . <SuffixToKey>` | `<b248>` | ck la ts | 0…1
  P.18.35 | `. . . . . <LettersAfterNames>` | `<b042>` | ck la ts | 0…1
  P.18.36 | `. . . . . <TitlesAfterNames>` | `<b043>` | ck la ts | 0…1
  P.18.37 | `. . . . . <CorporateName>` | `<b047>` | ck la ts | 0…n
  P.18.38 | `. . . . . <Corporate​NameInverted>` | `<x443>` | ck la ts | 0…n
  P.18.38a | `. . . . . <UnnamedPersons>` | `<b249>` | 19 § | 0…1
  ○ | `. . . . . <AlternativeName>` | `<alternativename>` |  | 0…n
  P.18.39 | `. . . . . . <NameType>` | `<x414>` | 18 | 1
  ○ | `. . . . . . <NameIdentifier>` | `<nameidentifier>` |  | 0…n
  P.18.40 | `. . . . . . . <NameIDType>` | `<x415>` | 44 | 1
  P.18.41 | `. . . . . . . <IDTypeName>` | `<b233>` | la | 0…1
  P.18.42 | `. . . . . . . <IDValue>` | `<b244>` |  | 1
  P.18.43 | `. . . . . . <PersonName>` | `<b036>` | ck la ts | 0…1
  P.18.44 | `. . . . . . <Person​NameInverted>` | `<b037>` | ck la ts | 0…1
  P.18.45 | `. . . . . . <TitlesBeforeNames>` | `<b038>` | ck la ts | 0…1
  P.18.46 | `. . . . . . <NamesBeforeKey>` | `<b039>` | ck la ts | 0…1
  P.18.47 | `. . . . . . <PrefixToKey>` | `<b247>` | ck la ts | 0…1
  P.18.48 | `. . . . . . <KeyNames>` | `<b040>` | ck la ts | 0…1
  P.18.49 | `. . . . . . <NamesAfterKey>` | `<b041>` | ck la ts | 0…1
  P.18.50 | `. . . . . . <SuffixToKey>` | `<b248>` | ck la ts | 0…1
  P.18.51 | `. . . . . . <LettersAfterNames>` | `<b042>` | ck la ts | 0…1
  P.18.52 | `. . . . . . <TitlesAfterNames>` | `<b043>` | ck la ts | 0…1
  P.18.53 | `. . . . . . <CorporateName>` | `<b047>` | ck la ts | 0…n
  P.18.54 | `. . . . . . <Corporate​NameInverted>` | `<x443>` | ck la ts | 0…n
  ○ | `. . . . . <ContributorDate>` | `<contributordate>` |  | 0…n
  P.18.55 | `. . . . . . <ContributorDateRole>` | `<x417>` | 177 | 1
  P.18.57 | `. . . . . . <Date>` | `<b306>` | df | 1
  ○ | `. . . . . <Professional​Affiliation>` | `<professionalaffiliation>` |  | 0…n
  P.18.58 | `. . . . . . <Professional​Position>` | `<b045>` | la | 0…n
  ○ | `. . . . . . <Affiliation​Identifier>` | `<affiliationidentifier>` | Ω | 0…n
  P.18.58a | `. . . . . . . <AffiliationIDType>` | `<x580>` | Ω | 1
  P.18.58b | `. . . . . . . <IDTypeName>` | `<b233>` | la Ω | 0…1
  P.18.58c | `. . . . . . . <IDValue>` | `<b244>` | Ω | 1
  P.18.59 | `. . . . . . <Affiliation>` | `<b046>` | la | 0…1
  ○ | `. . . . . <Prize>` | `<prize>` |  | 0…n
  P.18.59a | `. . . . . . <SequenceNumber>` | `<b034>` | Ω | 0…1
  ○ | `. . . . . . <PrizeIdentifier>` | `<prizeidentifier>` | Π | 0…n
  P.18.59b | `. . . . . . . <PrizeIDType>` | `<x589>` | 263 Π | 1
  P.18.59c | `. . . . . . . <IDTypeName>` | `<b233>` | la Π | 0…1
  P.18.59d | `. . . . . . . <IDValue>` | `<b244>` | Π | 1
  P.18.59e | `. . . . . . <PrizeName>` | `<g126>` | la § | 1…n
  P.18.59f | `. . . . . . <PrizeYear>` | `<g127>` | § | 0…1
  P.18.59g | `. . . . . . <AwardingBody>` | `<x584>` | la Ω | 0…n
  P.18.59h | `. . . . . . <PrizeCountry>` | `<g128>` | 91 § | 0…1
  P.18.59i | `. . . . . . <PrizeRegion>` | `<x555>` | 49 Σ | 0…1
  P.18.59j | `. . . . . . <PrizeCode>` | `<g129>` | 41 § | 0…1
  P.18.59k | `. . . . . . <PrizeStatement>` | `<x503>` | x la tf § | 0…n
  P.18.59l | `. . . . . . <PrizeJury>` | `<g343>` | x la tf § | 0…n
  P.18.60 | `. . . . . <BiographicalNote>` | `<b044>` | x la tf | 0…n
  ○ | `. . . . . <Website>` | `<website>` |  | 0…n
  P.18.61 | `. . . . . . <WebsiteRole>` | `<b367>` | 73 | 0…1
  P.18.62 | `. . . . . . <WebsiteDescription>` | `<b294>` | x la tf | 0…n
  P.18.63 | `. . . . . . <WebsiteLink>` | `<b295>` | la | 1…n
  P.18.64 | `. . . . . <ContributorDescription>` | `<b048>` | x la tf | 0…n
  ○ | `. . . . . <ContributorPlace>` | `<contributorplace>` |  | 0…n
  P.18.66 | `. . . . . . <Contributor​PlaceRelator>` | `<x418>` | 151 | 1
  P.18.67 | `. . . . . . <CountryCode>` | `<b251>` | 91 | 0…1
  P.18.68 | `. . . . . . <RegionCode>` | `<b398>` | 49 | 0…1
  P.18.68a | `. . . . . . <LocationName>` | `<j349>` | la ‡ | 0…n
  P.18.68b | `. . . . <ContributorStatement>` | `<b049>` | x la tf ∆ | 0…n
  P.18.68c | `. . . . <NoContributor/>` | `<n339/>` | ∆ | 0…1
  ○ | `. . . . <Language>` | `<language>` | ∆ | 0…n
  P.18.68d | `. . . . . <LanguageRole>` | `<b253>` | 22 ∆ | 1
  P.18.68e | `. . . . . <LanguageCode>` | `<b252>` | 74 ∆ | 1
  P.18.68f | `. . . . . <CountryCode>` | `<b251>` | 91 ∆ | 0…1
  P.18.68g | `. . . . . <RegionCode>` | `<b398>` | 49 Σ | 0…1
  P.18.68h | `. . . . . <ScriptCode>` | `<x420>` | 121 ∆ | 0…1
  ○ | `. . . . <Subject>` | `<subject>` |  | 0…n
  P.18.69 | `. . . . . <MainSubject/>` | `<x425/>` |  | 0…1
  P.18.70 | `. . . . . <SubjectSchemeIdentifier>` | `<b067>` | 27 | 1
  P.18.71 | `. . . . . <SubjectSchemeName>` | `<b171>` | la | 0…1
  P.18.72 | `. . . . . <SubjectSchemeVersion>` | `<b068>` |  | 0…1
  P.18.73 | `. . . . . <SubjectCode>` | `<b069>` |  | 0…1
  P.18.74 | `. . . . . <SubjectHeadingText>` | `<b070>` | la | 0…1
  ○ | `. . . . <NameAsSubject>` | `<nameassubject>` |  | 0…n
  P.18.75 | `. . . . . <NameType>` | `<x414>` | 18 | 0…1
  ○ | `. . . . . <NameIdentifier>` | `<nameidentifier>` |  | 0…n
  P.18.76 | `. . . . . . <NameIDType>` | `<x415>` | 44 | 1
  P.18.77 | `. . . . . . <IDTypeName>` | `<b233>` | la | 0…1
  P.18.78 | `. . . . . . <IDValue>` | `<b244>` |  | 1
  P.18.79 | `. . . . . <PersonName>` | `<b036>` | ck la ts | 0…1
  P.18.80 | `. . . . . <Person​NameInverted>` | `<b037>` | ck la ts | 0…1
  P.18.81 | `. . . . . <TitlesBeforeNames>` | `<b038>` | ck la ts | 0…1
  P.18.82 | `. . . . . <NamesBeforeKey>` | `<b039>` | ck la ts | 0…1
  P.18.83 | `. . . . . <PrefixToKey>` | `<b247>` | ck la ts | 0…1
  P.18.84 | `. . . . . <KeyNames>` | `<b040>` | ck la ts | 0…1
  P.18.85 | `. . . . . <NamesAfterKey>` | `<b041>` | ck la ts | 0…1
  P.18.86 | `. . . . . <SuffixToKey>` | `<b248>` | ck la ts | 0…1
  P.18.87 | `. . . . . <LettersAfterNames>` | `<b042>` | ck la ts | 0…1
  P.18.88 | `. . . . . <TitlesAfterNames>` | `<b043>` | ck la ts | 0…1
  P.18.89 | `. . . . . <CorporateName>` | `<b047>` | ck la ts | 0…n
  P.18.90 | `. . . . . <Corporate​NameInverted>` | `<x443>` | ck la ts | 0…n
  ○ | `. . . . . <AlternativeName>` | `<alternativename>` | § | 0…n
  P.18.90a | `. . . . . . <NameType>` | `<x414>` | 18 § | 1
  ○ | `. . . . . . <NameIdentifier>` | `<nameidentifier>` | § | 0…n
  P.18.90b | `. . . . . . . <NameIDType>` | `<x415>` | 44 § | 1
  P.18.90c | `. . . . . . . <IDTypeName>` | `<b233>` | la § | 0…1
  P.18.90d | `. . . . . . . <IDValue>` | `<b244>` | § | 1
  P.18.90e | `. . . . . . <PersonName>` | `<b036>` | ck la ts § | 0…1
  P.18.90f | `. . . . . . <PersonName​Inverted>` | `<b037>` | ck la ts § | 0…1
  P.18.90g | `. . . . . . <TitlesBeforeNames>` | `<b038>` | ck la ts § | 0…1
  P.18.90h | `. . . . . . <NamesBeforeKey>` | `<b039>` | ck la ts § | 0…1
  P.18.90i | `. . . . . . <PrefixToKey>` | `<b247>` | ck la ts § | 0…1
  P.18.90j | `. . . . . . <KeyNames>` | `<b040>` | ck la ts § | 0…1
  P.18.90k | `. . . . . . <NamesAfterKey>` | `<b041>` | ck la ts § | 0…1
  P.18.90l | `. . . . . . <SuffixToKey>` | `<b248>` | ck la ts § | 0…1
  P.18.90m | `. . . . . . <LettersAfterNames>` | `<b042>` | ck la ts § | 0…1
  P.18.90n | `. . . . . . <TitlesAfterNames>` | `<b043>` | ck la ts § | 0…1
  P.18.90p | `. . . . . . <CorporateName>` | `<b047>` | ck la ts § | 0…n
  P.18.90q | `. . . . . . <Corporate​NameInverted>` | `<x443>` | ck la ts § | 0…n
  ○ | `. . . . . <SubjectDate>` | `<subjectdate>` | § | 0…n
  P.18.90r | `. . . . . . <SubjectDateRole>` | `<x534>` | 177 § | 1
  P.18.90t | `. . . . . . <Date>` | `<b306>` | df § | 1
  ○ | `. . . . . <ProfessionalAffiliation>` | `<professionalaffiliation>` | § | 0…n
  P.18.90u | `. . . . . . <ProfessionalPosition>` | `<b045>` | la § | 0…n
  ○ | `. . . . . . <Affiliation​Identifier>` | `<affiliationidentifier>` | Ω | 0…n
  P.18.90v | `. . . . . . . <AffiliationIDType>` | `<x580>` | 44 Ω | 1
  P.18.90w | `. . . . . . . <IDTypeName>` | `<b233>` | la Ω | 0…1
  P.18.90x | `. . . . . . . <IDValue>` | `<b244>` | Ω | 1
  P.18.90y | `. . . . . . <Affiliation>` | `<b046>` | la § | 0…1
  ○ | `. . . . <TextContent>` | `<textcontent>` |  | 0…n
  P.18.91 | `. . . . . <SequenceNumber>` | `<b034>` | Ω | 0…1
  P.18.91a | `. . . . . <TextType>` | `<x426>` | 153 | 1
  P.18.92 | `. . . . . <ContentAudience>` | `<x427>` | 154 | 1…n
  ○ | `. . . . . <Territory>` | `<territory>` | § | 0…1
  P.18.92a | `. . . . . . <CountriesIncluded>` | `<x449>` | 91 § | 0…1
  P.18.92b | `. . . . . . <RegionsIncluded>` | `<x450>` | 49 § | 0…1
  P.18.92c | `. . . . . . <CountriesExcluded>` | `<x451>` | 91 § | 0…1
  P.18.92d | `. . . . . . <RegionsExcluded>` | `<x452>` | 49 § | 0…1
  P.18.93 | `. . . . . <Text>` | `<d104>` | x la tf | 1…n
  ○ | `. . . . . <ReviewRating>` | `<reviewrating>` | § | 0…1
  P.18.93a | `. . . . . . <Rating>` | `<x525>` | § | 1
  P.18.93b | `. . . . . . <RatingLimit>` | `<x526>` | § | 0…1
  P.18.93c | `. . . . . . <RatingUnits>` | `<x527>` | la § | 0…n
  P.18.94 | `. . . . . <TextAuthor>` | `<d107>` | la | 0…n
  P.18.95 | `. . . . . <TextSourceCorporate>` | `<b374>` | la | 0…1
  P.18.95a | `. . . . . <TextSourceDescription>` | `<x557>` | x la tf Σ | 0…n
  P.18.96 | `. . . . . <SourceTitle>` | `<x428>` | la | 0…n
  P.18.96a | `. . . . . <TextSourceLink>` | `<x581>` | la Ω | 0…n
  ○ | `. . . . . <EpubUsageConstraint>` | `<epubusageconstraint>` | Π | 0…n
  P.18.96b | `. . . . . . <EpubUsageType>` | `<x318>` | 145 Π | 1
  P.18.96c | `. . . . . . <EpubUsageStatus>` | `<x319>` | 146 Π | 1
  ○ | `. . . . . . <EpubUsageLimit>` | `<epubusagelimit>` | Π | 0…n
  P.18.96d | `. . . . . . . <Quantity>` | `<x320>` | Π | 1
  P.18.96e | `.. . . . . . <EpubUsageUnit>` | `<x321>` | 147 Π | 1
  ○ | `. . . . . <EpubLicense>` | `<epublicense>` | Π | 0…n
  P.18.96f | `. . . . . . <EpubLicenseName>` | `<x511>` | la Π | 1…n
  ○ | `. . . . . . <EpubLicenseExpression>` | `<epublicenseexpression>` | Π | 0…n
  P.18.96g | `. . . . . . . <EpubLicenseExpression​Type>` | `<x508>` | 218 Π | 1
  P.18.96h | `. . . . . . . <EpubLicenseExpression​TypeName>` | `<x509>` | la Π | 0…1
  P.18.96i | `. . . . . . . <EpubLicenseExpression​Link>` | `<x510>` | Π | 1
  ○ | `. . . . . . <EpubLicenseDate>` | `<epublicensedate>` | Π | 0…n
  P.18.96j | `. . . . . . . <EpubLicenseDateRole>` | `<x585>` | 260 Π | 1
  P.18.96k | `. . . . . . . <Date>` | `<b306>` | df Π | 1
  ○ | `. . . . . <ContentDate>` | `<contentdate>` |  | 0…n
  P.18.97 | `. . . . . . <ContentDateRole>` | `<x429>` | 155 | 1
  P.18.99 | `. . . . . . <Date>` | `<b306>` | df | 1
  ○ | `. . . . <CitedContent>` | `<citedcontent>` |  | 0…n
  P.18.100 | `. . . . . <SequenceNumber>` | `<b034>` | Ω | 01
  P.18.100a | `. . . . . <CitedContentType>` | `<x430>` | 156 | 1
  P.18.101 | `. . . . . <ContentAudience>` | `<x427>` | 154 | 0…n
  ○ | `. . . . . <Territory>` | `<territory>` | § | 0…1
  P.18.101a | `. . . . . . <CountriesIncluded>` | `<x449>` | 91 § | 0…1
  P.18.101b | `. . . . . . <RegionsIncluded>` | `<x450>` | 49 § | 0…1
  P.18.101c | `. . . . . . <CountriesExcluded>` | `<x451>` | 91§ | 0…1
  P.18.101d | `. . . . . . <RegionsExcluded>` | `<x452>` | 49 § | 0…1
  P.18.102 | `. . . . . <SourceType>` | `<x431>` | 157 | 0…1
  ○ | `. . . . . <ReviewRating>` | `<reviewrating>` | § | 0…1
  P.18.102a | `. . . . . . <Rating>` | `<x525>` | § | 1
  P.18.102b | `. . . . . . <RatingLimit>` | `<x526>` | § | 0…1
  P.18.102c | `. . . . . . <RatingUnits>` | `<x527>` | la § | 0…n
  P.18.103 | `. . . . . <SourceTitle>` | `<x428>` | la | 0…n
  P.18.104 | `. . . . . <ListName>` | `<x432>` | la | 0…n
  P.18.105 | `. . . . . <PositionOnList>` | `<x433>` |  | 0…1
  P.18.106 | `. . . . . <CitationNote>` | `<x434>` | la tf | 0…n
  P.18.107 | `. . . . . <ResourceLink>` | `<x435>` | la | 0…n
  ○ | `. . . . . <ContentDate>` | `<contentdate>` |  | 0…n
  P.18.108 | `. . . . . . <ContentDateRole>` | `<x429>` | 155 | 1
  P.18.110 | `. . . . . . <Date>` | `<b306>` | df | 1
  ○ | `. . . . <SupportingResource>` | `<supportingresource>` |  | 0…n
  P.18.111 | `. . . . . <SequenceNumber>` | `<b034>` | Ω | 0…1
  P.18.111a | `. . . . . <ResourceContentType>` | `<x436>` | 158 | 1
  P.18.112 | `. . . . . <ContentAudience>` | `<x427>` | 154 | 1…n
  ○ | `. . . . . <Territory>` | `<territory>` | § | 0…1
  P.18.112a | `. . . . . . <CountriesIncluded>` | `<x449>` | 91 § | 0…1
  P.18.112b | `. . . . . . <RegionsIncluded>` | `<x450>` | 49 § | 0…1
  P.18.112c | `. . . . . . <CountriesExcluded>` | `<x451>` | 91§ | 0…1
  P.18.112d | `. . . . . . <RegionsExcluded>` | `<x452>` | 49 § | 0…1
  P.18.113 | `. . . . . <ResourceMode>` | `<x437>` | 159 | 1
  ○ | `. . . . . <ResourceFeature>` | `<resourcefeature>` |  | 0…n
  P.18.114 | `. . . . . . <Resource​FeatureType>` | `<x438>` | 160 | 1
  P.18.115 | `. . . . . . <FeatureValue>` | `<x439>` |  | 0…1
  P.18.116 | `. . . . . . <FeatureNote>` | `<x440>` | x la tf | 0…n
  ○ | `. . . . . <ResourceVersion>` | `<resourceversion>` |  | 1…n
  P.18.117 | `. . . . . . <ResourceForm>` | `<x441>` | 161 | 1
  ○ | `. . . . . . <ResourceVersion​Feature>` | `<resourceversionfeature>` |  | 0…n
  P.18.118 | `. . . . . . . <ResourceVersion​FeatureType>` | `<x442>` | 162 | 1
  P.18.119 | `. . . . . . . <FeatureValue>` | `<x439>` |  | 0…1
  P.18.120 | `. . . . . . . <FeatureNote>` | `<x440>` | x la tf | 0…n
  P.18.121 | `. . . . . . <ResourceLink>` | `<x435>` | la | 1…n
  ○ | `. . . . . . <EpubUsageConstraint>` | `<epubusageconstraint>` | Π | 0…n
  P.18.121a | `. . . . . . . <EpubUsageType>` | `<x318>` | 145 Π | 1
  P.18.121b | `. . . . . . . <EpubUsageStatus>` | `<x319>` | 146 Π | 1
  ○ | `. . . . . . . <EpubUsageLimit>` | `<epubusagelimit>` | Π | 0…n
  P.18.121c | `. . . . . . . . <Quantity>` | `<x320>` | Π | 1
  P.18.121d | `. . . . . . . . <EpubUsageUnit>` | `<x321>` | 147 Π | 1
  ○ | `. . . . . . <EpubLicense>` | `<epublicense>` | Π | 0…n
  P.16.11e | `. . . . . . . <EpubLicenseName>` | `<x511>` | la Π | 1…n
  ○ | `. . . . . . . <EpubLicenseExpression>` | `<epublicenseexpression>` | Π | 0…n
  P.18.121f | `. . . . . . . . <EpubLicenseExpression​Type>` | `<x508>` | 218 Π | 1
  P.18.121g | `. . . . . . . . <EpubLicenseExpression​TypeName>` | `<x509>` | la Π | 0…1
  P.18.121h | `. . . . . . . . <EpubLicenseExpression​Link>` | `<x510>` | Π | 1
  ○ | `.. . . . . . <EpubLicenseDate>` | `<epublicensedate>` | Π | 0…n
  P.18.121i | `. . . . . . . . <EpubLicenseDateRole>` | `<x585>` | 260 Π | 1
  P.186.121j | `. . . . . . . . <Date>` | `<b306>` | df Π | 1
  ○ | `. . . . . . <ContentDate>` | `<contentdate>` |  | 0…n
  P.18.122 | `. . . . . . . <ContentDateRole>` | `<x429>` | 155 | 1
  P.18.124 | `. . . . . . . <Date>` | `<b306>` | df | 1
  ○ | `. . . . <Publisher>` | `<publisher>` | Ω | 0…n
  P.18.124a | `. . . . . <PublishingRole>` | `<b291>` | 45 Ω | 1
  ○ | `. . . . . <PublisherIdentifier>` | `<publisheridentifier>` | Ω | 0…n
  P.18.124b | `. . . . . . <PublisherIDType>` | `<x447>` | 44 Ω | 1
  P.18.124c | `. . . . . . <IDTypeName>` | `<b233>` | la Ω | 0…1
  P.18.124d | `. . . . . . <IDValue>` | `<b244>` | Ω | 1
  P.18.124e | `. . . . . <PublisherName>` | `<b081>` | ck la ts Ω | 0…n
  ○ | `. . . . . <Funding>` | `<funding>` | Ω | 0…n
  ○ | `. . . . . . <FundingIdentifier>` | `<fundingidentifier>` | Ω | 1…n
  P.18.124f | `. . . . . . . <FundingIDType>` | `<x523>` | 228 Ω | 1
  P.18.124g | `. . . . . . . <IDTypeName>` | `<b233>` | la Ω | 0…1
  P.18.124h | `. . . . . . . <IDValue>` | `<b244>` | Ω | 1
  ○ | `. . . . . <Website>` | `<website>` | Ω | 0…n
  P.18.124i | `. . . . . . <WebsiteRole>` | `<b367>` | 73 Ω | 0…1
  P.18.124j | `. . . . . . <WebsiteDescription>` | `<b294>` | x la tf Ω | 0…n
  P.18.124k | `. . . . . . <WebsiteLink>` | `<b295>` | la Ω | 1…n
  ○ | `. . . . <CopyrightStatement>` | `<copyrightstatement>` | Ω | 0…n
  P.18.124l | `. . . . . <CopyrightType>` | `<x512>` | 219 Ω | 0…1
  P.18.124m | `. . . . . <CopyrightYear>` | `<b087>` | df Ω | 0…n
  ○ | `. . . . . <CopyrightOwner>` | `<copyrightowner>` | Ω | 0…n
  ○ | `. . . . . . <CopyrightOwnerIdentifier>` | `<copyrightowneridentifier>` | Ω | 0…n
  P.18.124n | `. . . . . . . <CopyrightOwnerIDType>` | `<b392>` | 44 Ω | 1
  P.18.124o | `. . . . . . . <IDTypeName>` | `<b233>` | la Ω | 0…1
  P.18.124p | `. . . . . . . <IDValue>` | `<b244>` | Ω | 1
  P.18.124q | `. . . . . . <PersonName>` | `<b036>` | ck la ts Ω | 0…1
  P.18.124r | `. . . . . . <CorporateName>` | `<b047>` | ck la ts Ω | 0…1
  P.18.124s | `. . . . <CopyrightStatementText>` | `<x588>` | la df Π | 0…n
  ○ | `. . . . <RelatedWork>` | `<relatedwork>` |  | 0…n
  P.18.125 | `. . . . . <WorkRelationCode>` | `<x454>` | 164 | 1
  ○ | `. . . . . <WorkIdentifier>` | `<workidentifier>` |  | 1…n
  P.18.126 | `. . . . . . <WorkIDType>` | `<b201>` | 16 | 1
  P.18.127 | `. . . . . . <IDTypeName>` | `<b233>` | la | 0…1
  P.18.128 | `. . . . . . <IDValue>` | `<b244>` |  | 1
  ○ | `. . . . <RelatedProduct>` | `<relatedproduct>` | § | 0…n
  P.18.129 | `. . . . . <ProductRelationCode>` | `<x455>` | 51 § | 1…n
  ○ | `. . . . . <ProductIdentifier>` | `<productidentifier>` | § | 1…n
  P.18.130 | `. . . . . . <ProductIDType>` | `<b221>` | 5 § | 1
  P.18.131 | `. . . . . . <IDTypeName>` | `<b233>` | la § | 0…1
  P.18.132 | `. . . . . . <IDValue>` | `<b244>` | § | 1
  P.18.133 | `. . . . . <ProductForm>` | `<b012>` | 150 § | 0…1
  P.18.134 | `. . . . . <ProductFormDetail>` | `<b333>` | 175 § | 0…n
  Block 4: Publishing detail
  ○ | `. . <PublishingDetail>` | `<publishingdetail>` |  | 0…1
  Group P.19 Publisher
  ○ | `. . . <Imprint>` | `<imprint>` |  | 0…n
  ○ | `. . . . <ImprintIdentifier>` | `<imprintidentifier>` |  | 0…n
  P.19.1 | `. . . . . <ImprintIDType>` | `<x445>` | 44 | 1
  P.19.2 | `. . . . . <IDTypeName>` | `<b233>` | la | 0…1
  P.19.3 | `. . . . . <IDValue>` | `<b244>` |  | 1
  P.19.4 | `. . . . <ImprintName>` | `<b079>` | ck la | 0…1
  ○ | `. . . <Publisher>` | `<publisher>` |  | 0…n
  P.19.5 | `. . . . <PublishingRole>` | `<b291>` | 45 | 1
  ○ | `. . . . <PublisherIdentifier>` | `<publisheridentifier>` |  | 0…n
  P.19.6 | `. . . . . <PublisherIDType>` | `<x447>` | 44 | 1
  P.19.7 | `. . . . . <IDTypeName>` | `<b233>` | la | 0…1
  P.19.8 | `. . . . . <IDValue>` | `<b244>` |  | 1
  P.19.9 | `. . . . <PublisherName>` | `<b081>` | ck la ts | 0…n
  ○ | `. . . . <Funding>` | `<funding>` | § | 0…n
  ○ | `. . . . . <FundingIdentifier>` | `<fundingidentifier>` | § | 1…n
  P.19.9a | `. . . . . . <FundingIDType>` | `<x523>` | 228 § | 1
  P.19.9b | `. . . . . . <IDTypeName>` | `<b233>` | la § | 0…1
  P.19.9c | `. . . . . . <IDValue>` | `<b244>` | § | 1
  ○ | `. . . . <Website>` | `<website>` |  | 0…n
  P.19.10 | `. . . . . <WebsiteRole>` | `<b367>` | 73 | 0…1
  P.19.11 | `. . . . . <WebsiteDescription>` | `<b294>` | x la tf | 0…n
  P.19.12 | `. . . . . <WebsiteLink>` | `<b295>` | la | 1…n
  P.19.13 | `. . . <CityOfPublication>` | `<b209>` | la | 0…n
  P.19.14 | `. . . <CountryOfPublication>` | `<b083>` | 91 | 0…1
  ○ | `. . . <ProductContact>` | `<productcontact>` | † | 0…n
  P.19.15 | `. . . . <ProductContactRole>` | `<x482>` | 198 † | 1
  ○ | `. . . . <ProductContactIdentifier>` | `<productcontactidentifier>` | † | 0…n
  P.19.16 | `. . . . . <ProductContactIDType>` | `<x483>` | 44 † | 1
  P.19.17 | `. . . . . <IDTypeName>` | `<b233>` | la † | 0…1
  P.19.18 | `. . . . . <IDValue>` | `<b244>` | † | 1
  P.19.19 | `. . . . <ProductContactName>` | `<x484>` | † | 0…1
  P.19.20 | `. . . . <ContactName>` | `<x299>` | † | 0…1
  P.19.20a | `. . . . <TelephoneNumber>` | `<j270>` | Ψ | 0…n
  P.19.20b | `. . . . <FaxNumber>` | `<j271>` | Ω | 0…n
  P.19.21 | `. . . . <EmailAddress>` | `<j272>` | † | 0…n
  P.19.22 | `. . . . <StreetAddress>` | `<x552>` | Λ | 0…1
  P.19.23 | `. . . . <LocationName>` | `<j349>` | Λ | 0…1
  P.19.24 | `. . . . <PostalCode>` | `<x590>` | Λ | 0…1
  P.19.25 | `. . . . <RegionCode>` | `<b398>` | 49 Λ | 0…1
  P.19.26 | `. . . . <CountryCode>` | `<b251>` | 91 Λ | 0…1
  Group P.20 Global publishing status and dates / copyright
  P.20.1 | `. . . <PublishingStatus>` | `<b394>` | 64 | 0…1
  P.20.2 | `. . . <PublishingStatusNote>` | `<b395>` | x la tf | 0…n
  ○ | `. . . <PublishingDate>` | `<publishingdate>` |  | 0…n
  P.20.3 | `. . . . <PublishingDateRole>` | `<x448>` | 163 | 1
  P.20.5 | `. . . . <Date>` | `<b306>` | df | 1
  P.20.6 | `. . . <LatestReprintNumber>` | `<x446>` |  | 0…1
  ○ | `. . . <CopyrightStatement>` | `<copyrightstatement>` |  | 0…n
  P.20.6a | `. . . . <CopyrightType>` | `<x512>` | 219 ‡ | 0…1
  P.20.7 | `. . . . <CopyrightYear>` | `<b087>` | df | 0…n
  ○ | `. . . . <CopyrightOwner>` | `<copyrightowner>` |  | 0…n
  ○ | `. . . . . <Copyright​OwnerIdentifier>` | `<copyrightowneridentifier>` |  | 0…1
  P.20.8 | `. . . . . . <Copyright​OwnerIDType>` | `<b392>` | 44 | 1
  P.20.9 | `. . . . . . <IDTypeName>` | `<b233>` | la | 0…1
  P.20.10 | `. . . . . . <IDValue>` | `<b244>` |  | 1
  P.20.11 | `. . . . . <PersonName>` | `<b036>` | ck la ts | 0…1
  P.20.12 | `. . . . . <CorporateName>` | `<b047>` | ck la ts | 0…1
  P.20.12a | `. . . <CopyrightStatementText>` | `<x588>` | la df Π | 0…n
  Group P.21 Territorial rights and other sales restrictions
  ○ | `. . . <SalesRights>` | `<salesrights>` |  | 0…n
  P.21.1 | `. . . . <SalesRightsType>` | `<b089>` | 46 | 1
  ○ | `. . . . <Territory>` | `<territory>` |  | 1
  P.21.2 | `. . . . . <CountriesIncluded>` | `<x449>` | 91 | 0…1
  P.21.3 | `. . . . . <RegionsIncluded>` | `<x450>` | 49 | 0…1
  P.21.4 | `. . . . . <CountriesExcluded>` | `<x451>` | 91 | 0…1
  P.21.5 | `. . . . . <RegionsExcluded>` | `<x452>` | 49 | 0…1
  ○ | `. . . . <SalesRestriction>` | `<salesrestriction>` | ‡ | 0…n
  P.21.5a | `. . . . . <Sales​RestrictionType>` | `<b381>` | 71 ‡ | 1
  ○ | `. . . . . <SalesOutlet>` | `<salesoutlet>` | ‡ | 0…n
  ○ | `. . . . . . <Sales​OutletIdentifier>` | `<sales​outletidentifier>` | ‡ | 0…n
  P.21.5b | `. . . . . . . <Sales​OutletIDType>` | `<b393>` | 102 ‡ | 1
  P.21.5c | `. . . . . . . <IDTypeName>` | `<b233>` | la ‡ | 0…1
  P.21.5d | `. . . . . . . <IDValue>` | `<b244>` | ‡ | 1
  P.21.5e | `. . . . . . <Sales​OutletName>` | `<b382>` | la ‡ | 0…1
  P.21.5f | `. . . . . <SalesRestrictionNote>` | `<x453>` | x la tf ‡ | 0…n
  P.21.5g | `. . . . . <StartDate>` | `<b324>` | df ‡ | 0…1
  P.21.5h | `. . . . . <EndDate>` | `<b325>` | df ‡ | 0…1
  ○ | `. . . . <ProductIdentifier>` | `<productidentifier>` |  | 0…n
  P.21.6 | `. . . . . <ProductIDType>` | `<b221>` | 5 | 1
  P.21.7 | `. . . . . <IDTypeName>` | `<b233>` | la | 0…1
  P.21.8 | `. . . . . <IDValue>` | `<b244>` |  | 1
  P.21.9 | `. . . . <PublisherName>` | `<b081>` | ck la ts | 0…n
  P.21.10 | `. . . <ROWSalesRightsType>` | `<x456>` | 46 | 0…1
  Block 5: Related material
  ○ | `. . <RelatedMaterial>` | `<relatedmaterial>` |  | 0…1
  Group P.22 Related works
  ○ | `. . . <RelatedWork>` | `<relatedwork>` |  | 0…n
  P.22.1 | `. . . . <WorkRelationCode>` | `<x454>` | 164 | 1
  ○ | `. . . . <WorkIdentifier>` | `<workidentifier>` |  | 1…n
  P.22.2 | `. . . . . <WorkIDType>` | `<b201>` | 16 | 1
  P.22.3 | `. . . . . <IDTypeName>` | `<b233>` | la | 0…1
  P.22.4 | `. . . . . <IDValue>` | `<b244>` |  | 1
  Group P.23 Related products
  ○ | `. . . <RelatedProduct>` | `<relatedproduct>` |  | 0…n
  P.23.1 | `. . . . <ProductRelationCode>` | `<x455>` | 51 | 1…n
  ○ | `. . . . <ProductIdentifier>` | `<productidentifier>` |  | 1…n
  P.23.2 | `. . . . . <ProductIDType>` | `<b221>` | 5 | 1
  P.23.3 | `. . . . . <IDTypeName>` | `<b233>` | la | 0…1
  P.23.4 | `. . . . . <IDValue>` | `<b244>` |  | 1
  P.23.5 | `. . . . <ProductForm>` | `<b012>` | 150 | 0…1
  P.23.6 | `. . . . <ProductFormDetail>` | `<b333>` | 175 | 0…n
  Block 8: Production detail
  ○ | `. . <ProductionDetail>` | `<productiondetail>` | Ψ | 0…1
  Group P.28 Production manifest
  ○ | `. . . <ProductionManifest>` | `<productionmanifest>` | Ψ | 0…n
  ○ | `. . . . <ProductIdentifier>` | `<productidentifier>` | Ψ | 0…n
  P.28.1 | `. . . . . <ProductIDType>` | `<b221>` | 5 Ψ | 1
  P.28.2 | `. . . . . <IDTypeName>` | `<b233>` | la Ψ | 0…1
  P.28.3 | `. . . . . <IDValue>` | `<b244>` | Ψ | 1
  ○ | `. . . . <CoverManifest>` | `<covermanifest>` | Ψ | 0…1
  ○ | `. . . . . <SpecificationBundle​Name>` | `<specificationbundle​name>` | Ψ | 0…n
  P.28.4 | `. . . . . . <SpecificationBundle​NameTypeName>` | `<x558>` | la Ψ | 1
  P.28.5 | `. . . . . . <SpecificationBundle​NameValue>` | `<x559>` | Ψ | 1
  P.28.6 | `. . . . . <Specification​Detail>` | `<x560>` | 248 Ψ | 0…n
  ○ | `. . . . . <Specification​Feature>` | `<specification​feature>` | Ψ | 0…n
  P.28.7 | `. . . . . . <Specification​FeatureType>` | `<x561>` | 249 Ψ | 1
  P.28.8 | `. . . . . . <Specification​FeatureValue>` | `<x562>` | Ψ | 0…1
  P.28.9 | `. . . . . . <SpecificationFeature​Description>` | `<x563>` | la Ψ | 0…n
  P.28.10 | `. . . . . <Specification​Description>` | `<x564>` | la Ψ | 0…n
  ○ | `. . . . . <CoverResource>` | `<coverresource>` | Ψ | 1…n
  P.28.11 | `. . . . . . <SequenceNumber>` | `<b034>` | Ψ | 0…1
  ○ | `. . . . . . <SalesOutlet>` | `<salesoutlet>` | Ψ | 0…n
  ○ | `. . . . . . . <Sales​OutletIdentifier>` | `<sales​outletidentifier>` | Ψ | 0…n
  P.28.12 | `. . . . . . . . <Sales​OutletIDType>` | `<b393>` | 102 Ψ | 1
  P.28.13 | `. . . . . . . . <IDTypeName>` | `<b233>` | la Ψ | 0…1
  P.28.14 | `. . . . . . . . <IDValue>` | `<b244>` | Ψ | 1
  P.28.15 | `. . . . . . . <Sales​OutletName>` | `<b382>` | la Ψ | 0…1
  ○ | `. . . . . . <ResourceIdentifier>` | `<resourceidentifier>` | Ψ | 0…n
  P.28.16 | `. . . . . . . <ResourceIDType>` | `<x565>` | 250 Ψ | 1
  P.28.17 | `. . . . . . . <IDTypeName>` | `<b233>` | la Ψ | 0…1
  P.28.18 | `. . . . . . . <IDValue>` | `<b244>` | Ψ | 1
  P.28.19 | `. . . . . . <ResourceRole>` | `<x566>` | 251 Ψ | 0…1
  P.28.20 | `. . . . . . <ResourceFileDetail>` | `<x567>` | 252 Ψ | 0…n
  ○ | `. . . . . . <ResourceFile​Feature>` | `<resourcefile​feature>` | Ψ | 0…n
  P.28.21 | `. . . . . . . <ResourceFile​FeatureType>` | `<x568>` | 253 Ψ | 1
  P.28.22 | `. . . . . . . <ResourceFile​FeatureValue>` | `<x569>` | Ψ | 0…1
  P.28.23 | `. . . . . . . <ResourceFile​FeatureDescription>` | `<x570>` | la Ψ | 0…n
  P.28.24 | `. . . . . . <ResourceFile​Description>` | `<x571>` | la Ψ | 0…n
  P.28.25 | `. . . . . . <ResourceFile​Content​Description>` | `<x576>` | la Ψ | 0…n
  P.28.26 | `. . . . . . <ResourceFileLink>` | `<x572>` | Ψ | 1…n
  ○ | `. . . . . . <ResourceFileDate>` | `<resourcefiledate>` | Ψ | 0…n
  P.28.27 | `. . . . . . . <ResourceFile​DateRole>` | `<x573>` | 254 Ψ | 1
  P.28.29 | `. . . . . . . <Date>` | `<b306>` | df Ψ | 1
  P.28.30 | `. . . . . . <NoResource/>` | `<x577/>` | Ψ | 0…1
  ○ | `. . . . <BodyManifest>` | `<bodymanifest>` | Ψ | 1
  ○ | `. . . . . <Specification​Bundle​Name>` | `<specification​bundle​name>` | Ψ | 0…n
  P.28.31 | `. . . . . . <SpecificationBundle​NameTypeName>` | `<x558>` | la Ψ | 1
  P.28.32 | `. . . . . . <SpecificationBundle​NameValue>` | `<x559>` | Ψ | 1
  P.28.33 | `. . . . . <Specification​Detail>` | `<x560>` | 248 Ψ | 0…n
  ○ | `. . . . . <Specification​Feature>` | `<specification​feature>` | Ψ | 0…n
  P.28.34 | `. . . . . . <SpecificationFeature​Type>` | `<x561>` | 249 Ψ | 1
  P.28.35 | `. . . . . . <SpecificationFeature​Value>` | `<x562>` | Ψ | 0…1
  P.28.36 | `. . . . . . <SpecificationFeature​Description>` | `<x563>` | la Ψ | 0…n
  P.28.37 | `. . . . . <Specification​Description>` | `<x564>` | la Ψ | 0…n
  ○ | `. . . . . <BodyResource>` | `<bodyresource>` | Ψ | 1…n
  P.28.38 | `. . . . . . <SequenceNumber>` | `<b034>` | Ψ | 0…1
  ○ | `. . . . . . <ResourceIdentifier>` | `<resourceidentifier>` | Ψ | 0…n
  P.28.39 | `. . . . . . . <ResourceIDType>` | `<x565>` | 250 Ψ | 1
  P.28.40 | `. . . . . . . <IDTypeName>` | `<b233>` | la Ψ | 0…1
  P.28.41 | `. . . . . . . <IDValue>` | `<b244>` | Ψ | 1
  P.28.42 | `. . . . . . <ResourceRole>` | `<x566>` | 251 Ψ | 0…1
  P.28.43 | `. . . . . . <ResourceFileDetail>` | `<x567>` | 252 Ψ | 0…n
  ○ | `. . . . . . <ResourceFile​Feature>` | `<resourcefile​feature>` | Ψ | 0…n
  P.28.44 | `. . . . . . . <ResourceFile​FeatureType>` | `<x568>` | 253 Ψ | 1
  P.28.45 | `. . . . . . . <ResourceFile​FeatureValue>` | `<x569>` | Ψ | 0…1
  P.28.46 | `. . . . . . . <ResourceFile​FeatureDescription>` | `<x570>` | la Ψ | 0…n
  P.28.47 | `. . . . . . <ResourceFile​Description>` | `<x571>` | la Ψ | 0…n
  P.28.48 | `. . . . . . <ResourceFile​Content​Description>` | `<x576>` | la Ψ | 0…n
  P.28.49 | `. . . . . . <ResourceFileLink>` | `<x572>` | Ψ | 1…n
  ○ | `. . . . . . <ResourceFileDate>` | `<resourcefiledate>` | Ψ | 0…n
  P.28.50 | `. . . . . . . <ResourceFile​DateRole>` | `<x573>` | 254 Ψ | 1
  P.28.52 | `. . . . . . . <Date>` | `<b306>` | df Ψ | 1
  ○ | `. . . . <InsertManifest>` | `<insertmanifest>` | Ψ | 0…n
  ○ | `. . . . . <Specification​Bundle​Name>` | `<specification​bundle​name>` | Ψ | 0…n
  P.28.53 | `. . . . . . <SpecificationBundle​NameTypeName>` | `<x558>` | la Ψ | 1
  P.28.54 | `. . . . . . <SpecificationBundle​NameValue>` | `<x559>` | Ψ | 1
  P.28.55 | `. . . . . <Specification​Detail>` | `<x560>` | 248 Ψ | 0…n
  ○ | `. . . . . <Specification​Feature>` | `<specification​feature>` | Ψ | 0…n
  P.28.56 | `. . . . . . <Specification​FeatureType>` | `<x561>` | 249 Ψ | 1
  P.28.57 | `. . . . . . <Specification​FeatureValue>` | `<x562>` | Ψ | 0…1
  P.28.58 | `. . . . . . <SpecificationFeature​Description>` | `<x563>` | la Ψ | 0…n
  P.28.59 | `. . . . . <Specification​Description>` | `<x564>` | la Ψ | 0…n
  ○ | `. . . . . <InsertPoint>` | `<insertpoint>` | Ψ | 1
  P.28.60 | `. . . . . . <InsertPointType>` | `<x574>` | 255 Ψ | 1
  P.28.61 | `. . . . . . <InsertPointValue>` | `<x575>` | Ψ | 1
  ○ | `. . . . . <InsertResource>` | `<insertresource>` | Ψ | 1…n
  P.28.62 | `. . . . . . <SequenceNumber>` | `<b034>` | Ψ | 0…1
  ○ | `. . . . . . <SalesOutlet>` | `<salesoutlet>` | Ψ | 0…n
  ○ | `. . . . . . . <Sales​OutletIdentifier>` | `<sales​outletidentifier>` | Ψ | 0…n
  P.28.63 | `. . . . . . . . <Sales​OutletIDType>` | `<b393>` | 102 Ψ | 1
  P.28.64 | `. . . . . . . . <IDTypeName>` | `<b233>` | la Ψ | 0…1
  P.28.65 | `. . . . . . . . <IDValue>` | `<b244>` | Ψ | 1
  P.28.66 | `. . . . . . . <Sales​OutletName>` | `<b382>` | la Ψ | 0…1
  ○ | `. . . . . . <ResourceIdentifier>` | `<resourceidentifier>` | Ψ | 0…n
  P.28.67 | `. . . . . . . <ResourceIDType>` | `<x565>` | 250 Ψ | 1
  P.28.68 | `. . . . . . . <IDTypeName>` | `<b233>` | la Ψ | 0…1
  P.28.69 | `. . . . . . . <IDValue>` | `<b244>` | Ψ | 1
  P.28.70 | `. . . . . . <ResourceRole>` | `<x566>` | 251 Ψ | 0…1
  P.28.71 | `. . . . . . <ResourceFileDetail>` | `<x567>` | 252 Ψ | 0…n
  ○ | `. . . . . . <ResourceFile​Feature>` | `<resourcefile​feature>` | Ψ | 0…n
  P.28.72 | `. . . . . . . <ResourceFile​FeatureType>` | `<x568>` | 253 Ψ | 1
  P.28.73 | `. . . . . . . <ResourceFile​FeatureValue>` | `<x569>` | Ψ | 0…1
  P.28.74 | `. . . . . . . <ResourceFile​FeatureDescription>` | `<x570>` | la Ψ | 0…n
  P.28.75 | `. . . . . . <ResourceFile​Description>` | `<x571>` | la Ψ | 0…n
  P.28.76 | `. . . . . . <ResourceFile​Content​Description>` | `<x576>` | la Ψ | 0…n
  P.28.77 | `. . . . . . <ResourceFileLink>` | `<x572>` | Ψ | 1…n
  ○ | `. . . . . . <ResourceFileDate>` | `<resourcefiledate>` | Ψ | 0…n
  P.28.78 | `. . . . . . . <ResourceFile​DateRole>` | `<x573>` | 254 Ψ | 1
  P.28.80 | `. . . . . . . <Date>` | `<b306>` | df Ψ | 1
  P.28.81 | `. . . . . . <NoResource/>` | `<x577/>` | Ψ | 0…1
  ○ | `. . . . <SupplementManifest>` | `<supplementmanifest>` | Ψ | 0…n
  P.28.82 | `. . . . . <SequenceNumber>` | `<b034>` | Ψ | 0…1
  ○ | `. . . . . <SalesOutlet>` | `<salesoutlet>` | Ψ | 0…n
  ○ | `. . . . . . <Sales​OutletIdentifier>` | `<sales​outletidentifier>` | Ψ | 0…n
  P.28.83 | `. . . . . . . <Sales​OutletIDType>` | `<b393>` | 102 Ψ | 1
  P.28.84 | `. . . . . . . <IDTypeName>` | `<b233>` | la Ψ | 0…1
  P.28.85 | `. . . . . . . <IDValue>` | `<b244>` | Ψ | 1
  P.28.86 | `. . . . . . <Sales​OutletName>` | `<b382>` | la Ψ | 0…1
  ○ | `. . . . . <ProductIdentifier>` | `<productidentifier>` | Ψ | 0…n
  P.28.87 | `. . . . . . <ProductIDType>` | `<b221>` | 5 Ψ | 1
  P.28.88 | `. . . . . . <IDTypeName>` | `<b233>` | la Ψ | 0…n
  P.28.89 | `. . . . . . <IDValue>` | `<b244>` | Ψ | 1
  P.28.90 | `. . . . . <ProductForm>` | `<b012>` | 150 Ψ | 1
  P.28.91 | `. . . . . <ProductFormDetail>` | `<b333>` | 175 Ψ | 0…n
  P.28.92 | `. . . . . <ProductFormDescription>` | `<b014>` | la Ψ | 0…n
  ○ | `. . . . . <Measure>` | `<measure>` | Ψ | 0…n
  P.28.93 | `. . . . . . <MeasureType>` | `<x315>` | 48 Ψ | 1
  P.28.94 | `. . . . . . <Measurement>` | `<c094>` | Ψ | 1
  P.28.95 | `. . . . . . <MeasureUnitCode>` | `<c095>` | 50 Ψ | 1
  ○ | `. . . . . <CoverManifest>` | `<covermanifest>` | Ψ | 0…1
  ○ | `. . . . . . <Specification​Bundle​Name>` | `<specification​bundle​name>` | Ψ | 0…n
  P.28.96 | `. . . . . . . <SpecificationBundle​NameTypeName>` | `<x558>` | la Ψ | 1
  P.28.97 | `. . . . . . . <SpecificationBundle​NameValue>` | `<x559>` | Ψ | 1
  P.28.98 | `. . . . . . <SpecificationDetail>` | `<x560>` | 248 Ψ | 0…n
  ○ | `. . . . . . <Specification​Feature>` | `<specification​feature>` | Ψ | 0…n
  P.28.99 | `. . . . . . . <Specification​FeatureType>` | `<x561>` | 249 Ψ | 1
  P.28.100 | `. . . . . . . <Specification​FeatureValue>` | `<x562>` | Ψ | 0…1
  P.28.101 | `. . . . . . . <SpecificationFeature​Description>` | `<x563>` | la Ψ | 0…n
  P.28.102 | `. . . . . . <Specification​Description>` | `<x564>` | la Ψ | 0…n
  ○ | `. . . . . . <CoverResource>` | `<coverresource>` | Ψ | 1…n
  P.28.103 | `. . . . . . . <SequenceNumber>` | `<b034>` | Ψ | 0…1
  ○ | `. . . . . . . <SalesOutlet>` | `<salesoutlet>` | Ψ | 0…n
  ○ | `. . . . . . . . <Sales​OutletIdentifier>` | `<sales​outletidentifier>` | Ψ | 0…n
  P.28.104 | `. . . . . . . . . <Sales​OutletIDType>` | `<b393>` | 102 Ψ | 1
  P.28.105 | `. . . . . . . . . <IDTypeName>` | `<b233>` | la Ψ | 0…1
  P.28.106 | `. . . . . . . . . <IDValue>` | `<b244>` | Ψ | 1
  P.28.107 | `. . . . . . . . <Sales​OutletName>` | `<b382>` | la Ψ | 0…1
  ○ | `. . . . . . . <ResourceIdentifier>` | `<resourceidentifier>` | Ψ | 0…n
  P.28.108 | `. . . . . . . . <ResourceIDType>` | `<x565>` | 250 Ψ | 1
  P.28.109 | `. . . . . . . . <IDTypeName>` | `<b233>` | la Ψ | 0…1
  P.28.110 | `. . . . . . . . <IDValue>` | `<b244>` | Ψ | 1
  P.28.111 | `. . . . . . . <ResourceRole>` | `<x566>` | 251 Ψ | 0…1
  P.28.112 | `. . . . . . . <ResourceFileDetail>` | `<x567>` | 252 Ψ | 0…n
  ○ | `. . . . . . . <ResourceFile​Feature>` | `<resourcefile​feature>` | Ψ | 0…n
  P.28.113 | `. . . . . . . . <ResourceFile​FeatureType>` | `<x568>` | 253 Ψ | 1
  P.28.114 | `. . . . . . . . <ResourceFile​FeatureValue>` | `<x569>` | Ψ | 0…1
  P.28.115 | `. . . . . . . . <ResourceFile​FeatureDescription>` | `<x570>` | la Ψ | 0…n
  P.28.116 | `. . . . . . . <ResourceFile​Description>` | `<x571>` | la Ψ | 0…n
  P.28.117 | `. . . . . . . <ResourceFile​Content​Description>` | `<x576>` | la Ψ | 0…n
  P.28.118 | `. . . . . . . <ResourceFileLink>` | `<x572>` | Ψ | 1…n
  ○ | `. . . . . . . <ResourceFileDate>` | `<resourcefiledate>` | Ψ | 0…n
  P.28.119 | `. . . . . . . . <ResourceFile​DateRole>` | `<x573>` | 254 Ψ | 1
  P.28.121 | `. . . . . . . . <Date>` | `<b306>` | df Ψ | 1
  P.28.122 | `. . . . . . . <NoResource/>` | `<x577/>` | Ψ | 0…1
  ○ | `. . . . . <BodyManifest>` | `<bodymanifest>` | Ψ | 1
  ○ | `. . . . . . <Specification​Bundle​Name>` | `<specification​bundle​name>` | Ψ | 0…n
  P.28.123 | `. . . . . . . <SpecificationBundle​NameTypeName>` | `<x558>` | la Ψ | 1
  P.28.124 | `. . . . . . . <SpecificationBundle​NameValue>` | `<x559>` | Ψ | 1
  P.28.125 | `. . . . . . <Specification​Detail>` | `<x560>` | 248 Ψ | 0…n
  ○ | `. . . . . . <Specification​Feature>` | `<specification​feature>` | Ψ | 0…n
  P.28.126 | `. . . . . . . <Specification​FeatureType>` | `<x561>` | 249 Ψ | 1
  P.28.127 | `. . . . . . . <Specification​FeatureValue>` | `<x562>` | Ψ | 0…1
  P.28.128 | `. . . . . . . <SpecificationFeature​Description>` | `<x563>` | la Ψ | 0…n
  P.28.129 | `. . . . . . <Specification​Description>` | `<x564>` | la Ψ | 0…n
  ○ | `. . . . . . <BodyResource>` | `<bodyresource>` | Ψ | 1…n
  P.28.130 | `. . . . . . . <SequenceNumber>` | `<b034>` | Ψ | 0…1
  ○ | `. . . . . . . <ResourceIdentifier>` | `<resourceidentifier>` | Ψ | 0…n
  P.28.131 | `. . . . . . . . <ResourceIDType>` | `<x565>` | 250 Ψ | 1
  P.28.132 | `. . . . . . . . <IDTypeName>` | `<b233>` | la Ψ | 0…1
  P.28.133 | `. . . . . . . . <IDValue>` | `<b244>` | Ψ | 1
  P.28.134 | `. . . . . . . <ResourceRole>` | `<x566>` | 251 Ψ | 0…1
  P.28.135 | `. . . . . . . <ResourceFileDetail>` | `<x567>` | 252 Ψ | 0…n
  ○ | `. . . . . . . <ResourceFile​Feature>` | `<resourcefile​feature>` | Ψ | 0…n
  P.28.136 | `. . . . . . . . <ResourceFile​FeatureType>` | `<x568>` | 253 Ψ | 1
  P.28.137 | `. . . . . . . . <ResourceFile​FeatureValue>` | `<x569>` | Ψ | 0…1
  P.28.138 | `. . . . . . . . <ResourceFile​FeatureDescription>` | `<x570>` | la Ψ | 0…n
  P.28.139 | `. . . . . . . <ResourceFile​Description>` | `<x571>` | la Ψ | 0…n
  P.28.140 | `. . . . . . . <ResourceFile​Content​Description>` | `<x576>` | la Ψ | 0…n
  P.28.141 | `. . . . . . . <ResourceFileLink>` | `<x572>` | Ψ | 1…n
  ○ | `. . . . . . . <ResourceFileDate>` | `<resourcefiledate>` | Ψ | 0…n
  P.28.142 | `. . . . . . . . <ResourceFile​DateRole>` | `<x573>` | 254 Ψ | 1
  P.28.144 | `. . . . . . . . <Date>` | `<b306>` | df Ψ | 1
  ○ | `. . . . . <InsertManifest>` | `<insertmanifest>` | Ψ | 0…n
  ○ | `. . . . . . <Specification​Bundle​Name>` | `<specification​bundle​name>` | Ψ | 0…n
  P.28.145 | `. . . . . . . <SpecificationBundle​NameTypeName>` | `<x558>` | la Ψ | 1
  P.28.146 | `. . . . . . . <SpecificationBundle​NameValue>` | `<x559>` | Ψ | 1
  P.28.147 | `. . . . . . <Specification​Detail>` | `<x560>` | 248 Ψ | 0…n
  ○ | `. . . . . . <SpecificationFeature>` | `<specificationfeature>` | Ψ | 0…n
  P.28.148 | `. . . . . . . <Specification​FeatureType>` | `<x561>` | 249 Ψ | 1
  P.28.149 | `. . . . . . . <Specification​FeatureValue>` | `<x562>` | Ψ | 0…1
  P.28.150 | `. . . . . . . <SpecificationFeature​Description>` | `<x563>` | la Ψ | 0…n
  P.28.151 | `. . . . . . <Specification​Description>` | `<x564>` | la Ψ | 0…n
  ○ | `. . . . . . <InsertPoint>` | `<insertpoint>` | Ψ | 1
  P.28.152 | `. . . . . . . <InsertPointType>` | `<x574>` | 255 Ψ | 1
  P.28.153 | `. . . . . . . <InsertPointValue>` | `<x575>` | Ψ | 1
  ○ | `. . . . . . <InsertResource>` | `<insertresource>` | Ψ | 1…n
  P.28.154 | `. . . . . . . <SequenceNumber>` | `<b034>` | Ψ | 0…1
  ○ | `. . . . . . . <SalesOutlet>` | `<salesoutlet>` | Ψ | 0…n
  ○ | `. . . . . . . . <Sales​OutletIdentifier>` | `<sales​outletidentifier>` | Ψ | 0…n
  P.28.155 | `. . . . . . . . . <Sales​OutletIDType>` | `<b393>` | 102 Ψ | 1
  P.28.156 | `. . . . . . . . . <IDTypeName>` | `<b233>` | la Ψ | 0…1
  P.28.157 | `. . . . . . . . . <IDValue>` | `<b244>` | Ψ | 1
  P.28.158 | `. . . . . . . . <Sales​OutletName>` | `<b382>` | la Ψ | 0…1
  ○ | `. . . . . . . <ResourceIdentifier>` | `<resourceidentifier>` | Ψ | 0…n
  P.28.159 | `. . . . . . . . <ResourceIDType>` | `<x565>` | 250 Ψ | 1
  P.28.160 | `. . . . . . . . <IDTypeName>` | `<b233>` | la Ψ | 0…1
  P.28.161 | `. . . . . . . . <IDValue>` | `<b244>` | Ψ | 1
  P.28.162 | `. . . . . . . <ResourceRole>` | `<x566>` | 251 Ψ | 0…1
  P.28.163 | `. . . . . . . <ResourceFileDetail>` | `<x567>` | 252 Ψ | 0…n
  ○ | `. . . . . . . <ResourceFile​Feature>` | `<resourcefile​feature>` | Ψ | 0…n
  P.28.164 | `. . . . . . . . <ResourceFile​FeatureType>` | `<x568>` | 253 Ψ | 1
  P.28.165 | `. . . . . . . . <ResourceFile​FeatureValue>` | `<x569>` | Ψ | 0…1
  P.28.166 | `. . . . . . . . <ResourceFile​FeatureDescription>` | `<x570>` | la Ψ | 0…n
  P.28.167 | `. . . . . . . <ResourceFile​Description>` | `<x571>` | la Ψ | 0…n
  P.28.168 | `. . . . . . . <ResourceFile​Content​Description>` | `<x576>` | la Ψ | 0…n
  P.28.169 | `. . . . . . . <ResourceFileLink>` | `<x572>` | Ψ | 1…n
  ○ | `. . . . . . . <ResourceFileDate>` | `<resourcefiledate>` | Ψ | 0…n
  P.28.170 | `. . . . . . . . <ResourceFile​DateRole>` | `<x573>` | 254 Ψ | 1
  P.28.172 | `. . . . . . . . <Date>` | `<b306>` | df Ψ | 1
  P.28.173 | `. . . . . . . <NoResource/>` | `<x577/>` | Ψ | 0…1
  P.28.174 | `. . . . . <NoSupplement/>` | `<x579/>` | Ψ | 0…1
  Block 6: Product supply
  ○ | `. . <ProductSupply>` | `<productsupply>` |  | 0…n
  Group P.24 Market
  P.24.1 | `. . . <MarketReference>` | `<x587>` | Ω | 0…1
  ○ | `. . . <Market>` | `<market>` |  | 0…n
  ○ | `. . . . <Territory>` | `<territory>` |  | 1
  P.24.1a | `. . . . . <CountriesIncluded>` | `<x449>` | 91 | 0…1
  P.24.2 | `. . . . . <RegionsIncluded>` | `<x450>` | 49 | 0…1
  P.24.3 | `. . . . . <CountriesExcluded>` | `<x451>` | 91 | 0…1
  P.24.4 | `. . . . . <RegionsExcluded>` | `<x452>` | 49 | 0…1
  ○ | `. . . . <SalesRestriction>` | `<salesrestriction>` |  | 0…n
  P.24.5 | `. . . . . <Sales​RestrictionType>` | `<b381>` | 71 | 1
  ○ | `. . . . . <SalesOutlet>` | `<salesoutlet>` |  | 0…n
  ○ | `. . . . . . <Sales​OutletIdentifier>` | `<sales​outletidentifier>` |  | 0…n
  P.24.6 | `. . . . . . . <Sales​OutletIDType>` | `<b393>` | 102 | 1
  P.24.7 | `. . . . . . . <IDTypeName>` | `<b233>` | la | 0…1
  P.24.8 | `. . . . . . . <IDValue>` | `<b244>` |  | 1
  P.24.9 | `. . . . . . <Sales​OutletName>` | `<b382>` | la | 0…1
  P.24.10 | `. . . . . <Sales​RestrictionNote>` | `<x453>` | x la tf | 0…n
  P.24.11 | `. . . . . <StartDate>` | `<b324>` | df | 0…1
  P.24.12 | `. . . . . <EndDate>` | `<b325>` | df | 0…1
  Group P.25 Market publishing detail
  ○ | `. . . <MarketPublishingDetail>` | `<marketpublishing​detail>` |  | 0…1
  ○ | `. . . . <PublisherRepresentative>` | `<publisher​representative>` |  | 0…n
  P.25.1 | `. . . . . <AgentRole>` | `<j402>` | 69 | 1
  ○ | `. . . . . <AgentIdentifier>` | `<agentidentifier>` |  | 0…n
  P.25.2 | `. . . . . . <AgentIDType>` | `<j400>` | 92 | 1
  P.25.3 | `. . . . . . <IDTypeName>` | `<b233>` | la | 0…1
  P.25.4 | `. . . . . . <IDValue>` | `<b244>` |  | 1
  P.25.5 | `. . . . . <AgentName>` | `<j401>` | ck la | 0…1
  P.25.6 | `. . . . . <TelephoneNumber>` | `<j270>` |  | 0…n
  P.25.7 | `. . . . . <FaxNumber>` | `<j271>` |  | 0…n
  P.25.8 | `. . . . . <EmailAddress>` | `<j272>` |  | 0…n
  ○ | `. . . . . <Website>` | `<website>` |  | 0…n
  P.25.9 | `. . . . . . <WebsiteRole>` | `<b367>` | 73 | 0…1
  P.25.10 | `. . . . . . <WebsiteDescription>` | `<b294>` | x la tf | 0…n
  P.25.11 | `. . . . . . <WebsiteLink>` | `<b295>` | la | 1…n
  ○ | `. . . . <ProductContact>` | `<productcontact>` | † | 0…n
  P.25.11a | `. . . . . <ProductContactRole>` | `<x482>` | 198 † | 1
  ○ | `. . . . . <ProductContact​Identifier>` | `<productcontact​identifier>` | † | 0…n
  P.25.11b | `. . . . . . <ProductContactIDType>` | `<x483>` | 44 † | 1
  P.25.11c | `. . . . . . <IDTypeName>` | `<b233>` | la † | 0…1
  P.25.11d | `. . . . . . <IDValue>` | `<b244>` | † | 1
  P.25.11e | `. . . . . <ProductContactName>` | `<x484>` | † | 0…1
  P.25.11f | `. . . . . <ContactName>` | `<x299>` | † | 0…1
  P.25.11g | `. . . . . <TelephoneNumber>` | `<j270>` | Ψ | 0…n
  P.25.11h | `. . . . . <FaxNumber>` | `<j271>` | Ω | 0…n
  P.25.11i | `. . . . . <EmailAddress>` | `<j272>` | † | 0…n
  P.25.11j | `. . . . . <StreetAddress>` | `<x552>` | Λ | 0…1
  P.25.11k | `. . . . . <LocationName>` | `<j349>` | Λ | 0…1
  P.25.11l | `. . . . . <PostalCode>` | `<x590>` | Λ | 0…1
  P.25.11m | `. . . . . <RegionCode>` | `<b398>` | 49 Λ | 0…1
  P.25.11n | `. . . . . <CountryCode>` | `<b251>` | 91 Λ | 0…1
  P.25.12 | `. . . . <MarketPublishingStatus>` | `<j407>` | 68 | 1
  P.25.13 | `. . . . <MarketPublishing​StatusNote>` | `<x406>` | x la tf | 0…n
  ○ | `. . . . <MarketDate>` | `<marketdate>` |  | 0…n
  P.25.14 | `. . . . . <MarketDateRole>` | `<j408>` | 163 | 1
  P.25.16 | `. . . . . <Date>` | `<b306>` | df | 1
  P.25.17 | `. . . . <PromotionCampaign>` | `<k165>` | x la tf | 0…n
  P.25.19 | `. . . . <InitialPrintRun>` | `<k167>` | x la tf | 0…n
  P.25.20 | `. . . . <ReprintDetail>` | `<k309>` | x la tf | 0…n
  P.25.21 | `. . . . <CopiesSold>` | `<k168>` | x la tf | 0…n
  P.25.22 | `. . . . <BookClubAdoption>` | `<k169>` | x la tf | 0…n
  Group P.26 Supply detail
  ○ | `. . . <SupplyDetail>` | `<supplydetail>` |  | 1…n
  ○ | `. . . . <Supplier>` | `<supplier>` |  | 1
  P.26.1 | `. . . . . <SupplierRole>` | `<j292>` | 93 | 1
  ○ | `. . . . . <SupplierIdentifier>` | `<supplieridentifier>` |  | 0…n
  P.26.2 | `. . . . . . <SupplierIDType>` | `<j345>` | 92 | 1
  P.26.3 | `. . . . . . <IDTypeName>` | `<b233>` | la | 0…1
  P.26.4 | `. . . . . . <IDValue>` | `<b244>` |  | 1
  P.26.5 | `. . . . . <SupplierName>` | `<j137>` | ck la | 0…1
  P.26.6 | `. . . . . <TelephoneNumber>` | `<j270>` |  | 0…n
  P.26.7 | `. . . . . <FaxNumber>` | `<j271>` |  | 0…n
  P.26.8 | `. . . . . <EmailAddress>` | `<j272>` |  | 0…n
  ○ | `. . . . . <Website>` | `<website>` |  | 0…n
  P.26.9 | `. . . . . . <WebsiteRole>` | `<b367>` | 73 | 0…1
  P.26.10 | `. . . . . . <WebsiteDescription>` | `<b294>` | x la tf | 0…n
  P.26.11 | `. . . . . . <WebsiteLink>` | `<b295>` | la | 1…n
  ○ | `. . . . <SupplyContact>` | `<supplycontact>` | ∆ | 0…n
  P.26.11a | `. . . . . <SupplyContactRole>` | `<x537>` | 239 ∆ | 1
  ○ | `. . . . . <SupplyContactIdentifier>` | `<supplycontactidentifier>` | ∆ | 0…n
  P.26.11b | `. . . . . . <SupplyContactIDType>` | `<x538>` | 44 ∆ | 1
  P.26.11c | `. . . . . . <IDTypeName>` | `<b233>` | la ∆ | 0…1
  P.26.11d | `. . . . . . <IDValue>` | `<b244>` | ∆ | 1
  P.26.11e | `. . . . . <SupplyContactName>` | `<x539>` | ∆ | 0…1
  P.26.11f | `. . . . . <ContactName>` | `<x299>` | ∆ | 0…1
  P.26.11g | `. . . . . <TelephoneNumber>` | `<j270>` | Ψ | 0…n
  P.26.11h | `. . . . . <FaxNumber>` | `<j271>` | Ω | 0…n
  P.26.11i | `. . . . . <EmailAddress>` | `<j272>` | ∆ | 0…n
  P.26.11j | `. . . . . <StreetAddress>` | `<x552>` | Λ | 0…1
  P.26.11k | `. . . . . <LocationName>` | `<j349>` | Λ | 0…1
  P.26.11l | `. . . . . <PostalCode>` | `<x590>` | Λ | 0…1
  P.26.11m | `. . . . . <RegionCode>` | `<b398>` | 49 Λ | 0…1
  P.26.11n | `. . . . . <CountryCode>` | `<b251>` | 91 Λ | 0…1
  ○ | `. . . . <SupplierOwnCoding>` | `<supplierowncoding>` |  | 0…n
  P.26.12 | `. . . . . <SupplierCodeType>` | `<x458>` | 165 | 1
  P.26.12a | `. . . . . <SupplierCodeTypeName>` | `<x513>` | la ‡ | 0…1
  P.26.13 | `. . . . . <SupplierCodeValue>` | `<x459>` |  | 1
  ○ | `. . . . <ReturnsConditions>` | `<returnsconditions>` |  | 0…n
  P.26.14 | `. . . . . <ReturnsCodeType>` | `<j268>` | 53 | 1
  P.26.15 | `. . . . . <ReturnsCodeTypeName>` | `<x460>` | la | 0…1
  P.26.16 | `. . . . . <ReturnsCode>` | `<j269>` | various | 1
  P.26.16a | `. . . . . <ReturnsNote>` | `<x528>` | la § | 0…n
  P.26.17 | `. . . . <ProductAvailability>` | `<j396>` | 65 | 1
  ○ | `. . . . <SupplyDate>` | `<supplydate>` |  | 0…n
  P.26.18 | `. . . . . <SupplyDateRole>` | `<x461>` | 166 | 1
  P.26.20 | `. . . . . <Date>` | `<b306>` | df | 1
  P.26.21 | `. . . . <OrderTime>` | `<j144>` |  | 0…1
  ○ | `. . . . <NewSupplier>` | `<newsupplier>` |  | 0…1
  ○ | `. . . . . <SupplierIdentifier>` | `<supplieridentifier>` |  | 0…n
  P.26.22 | `. . . . . . <SupplierIDType>` | `<j345>` | 92 | 1
  P.26.23 | `. . . . . . <IDTypeName>` | `<b233>` | la | 0…1
  P.26.24 | `. . . . . . <IDValue>` | `<b244>` |  | 1
  P.26.25 | `. . . . . <SupplierName>` | `<j137>` | ck la | 0…1
  P.26.26 | `. . . . . <TelephoneNumber>` | `<j270>` |  | 0…n
  P.26.27 | `. . . . . <FaxNumber>` | `<j271>` |  | 0…n
  P.26.28 | `. . . . . <EmailAddress>` | `<j272>` |  | 0…n
  ○ | `. . . . . <Website>` | `<website>` | Ω | 0…n
  P.26.28a | `. . . . . . <WebsiteRole>` | `<b367>` | 73 Ω | 0…1
  P.26.28b | `. . . . . . <WebsiteDescription>` | `<b294>` | x la tf Ω | 0…n
  P.26.28c | `. . . . . . <WebsiteLink>` | `<b295>` | la Ω | 1…n
  ○ | `. . . . <Stock>` | `<stock>` |  | 0…n
  ○ | `. . . . . <LocationIdentifier>` | `<locationidentifier>` |  | 0…n
  P.26.29 | `. . . . . . <LocationIDType>` | `<j377>` | 92 | 1
  P.26.30 | `. . . . . . <IDTypeName>` | `<b233>` | la | 0…1
  P.26.31 | `. . . . . . <IDValue>` | `<b244>` |  | 1
  P.26.32 | `. . . . . <LocationName>` | `<j349>` | la | 0…n
  ○ | `. . . . . <StockQuantityCoded>` | `<stockquantitycoded>` |  | 0…n
  P.26.33 | `. . . . . . <StockQuantity​CodeType>` | `<j293>` | 70 | 1
  P.26.34 | `. . . . . . <StockQuantity​CodeTypeName>` | `<j296>` | la | 0…1
  P.26.35 | `. . . . . . <StockQuantity​Code>` | `<j297>` |  | 1
  P.26.36 | `. . . . . <OnHand>` | `<j350>` |  | 0…1
  P.26.36a | `. . . . . <Proximity>` | `<x502>` | 215 ‡ | 0…1
  P.26.36b | `. . . . . <Reserved>` | `<x536>` | ∆ | 0…1
  P.26.36c | `. . . . . <Proximity>` | `<x502>` | 215 ∆ | 0…1
  P.26.37 | `. . . . . <OnOrder>` | `<j351>` |  | 0…1
  P.26.37a | `. . . . . <Proximity>` | `<x502>` | 215 ‡ | 0…1
  P.26.38 | `. . . . . <CBO>` | `<j375>` |  | 0…1
  P.26.38a | `. . . . . <Proximity>` | `<x502>` | 215 ‡ | 0…1
  ○ | `. . . . . <OnOrderDetail>` | `<onorderdetail>` |  | 0…n
  P.26.39 | `. . . . . . <OnOrder>` | `<j351>` |  | 1
  P.26.39a | `. . . . . . <Proximity>` | `<x502>` | 215 ‡ | 0…1
  P.26.40 | `. . . . . . <ExpectedDate>` | `<j302>` | df | 1
  ○ | `. . . . . <Velocity>` | `<velocity>` | ‡ | 0…n
  P.26.40a | `. . . . . . <VelocityMetric>` | `<x504>` | 216 ‡ | 1
  P.26.40b | `. . . . . . <Rate>` | `<x505>` | ‡ | 1
  P.26.40c | `. . . . . . <Proximity>` | `<x502>` | 215 ‡ | 0…1
  P.26.41 | `. . . . <PackQuantity>` | `<j145>` |  | 0…1
  P.26.41a | `. . . . <PalletQuantity>` | `<x545>` | Φ | 0…1
  P.26.41b | `. . . . <OrderQuantityMinimum>` | `<x532>` | § | 0…1
  P.26.41c | `. . . . <OrderQuantityMinimum>` | `<x532>` | § | 0…1
  P.26.41d | `. . . . <OrderQuantityMultiple>` | `<x533>` | § | 0…1
  P.26.42 | `. . . . <UnpricedItemType>` | `<j192>` | 57 | 0…1
  ○ | `. . . . <Price>` | `<price>` |  | 0…n
  ○ | `. . . . . <PriceIdentifier>` | `<priceidentifier>` | ‡ | 0…n
  P.26.42a | `. . . . . . <PriceIDType>` | `<x506>` | 217 ‡ | 1
  P.26.42b | `. . . . . . <IDTypeName>` | `<b233>` | la ‡ | 0…1
  P.26.42c | `. . . . . . <IDValue>` | `<b244>` | ‡ | 1
  P.26.43 | `. . . . . <PriceType>` | `<x462>` | 58 | 0…1
  P.26.44 | `. . . . . <PriceQualifier>` | `<j261>` | 59 | 0…1
  P.26.44a | `. . . . . <EpubTechnicalProtection>` | `<x317>` | 144 ∆ | 0…n
  ○ | `. . . . . <PriceConstraint>` | `<priceconstraint>` | § | 0…n
  P.26.44b | `. . . . . . <PriceConstraintType>` | `<x529>` | 230 § | 1
  P.26.44c | `. . . . . . <PriceConstraintStatus>` | `<x530>` | 146 § | 1
  ○ | `. . . . . . <PriceConstraintLimit>` | `<priceconstraintlimit>` | § | 0…n
  P.26.44d | `. . . . . . . <Quantity>` | `<x320>` | § | 1
  P.26.44e | `. . . . . . . <PriceConstraintUnit>` | `<x531>` | 147 § | 1
  ○ | `. . . . . <EpubLicense>` | `<epublicense>` | ∆ | 0…1
  P.26.44f | `. . . . . . <EpubLicenseName>` | `<x511>` | la ∆ | 1…n
  ○ | `. . . . . . <EpubLicenseExpression>` | `<epublicenseexpression>` | ∆ | 0…n
  P.26.44g | `. . . . . . . <EpubLicenseExpression​Type>` | `<x508>` | 218 ∆ | 1
  P.26.44h | `. . . . . . . <EpubLicenseExpression​TypeName>` | `<x509>` | la ∆ | 0…1
  P.26.44i | `. . . . . . . <EpubLicenseExpression​Link>` | `<x510>` | ∆ | 1
  P.26.45 | `. . . . . <PriceTypeDescription>` | `<j262>` | la | 0…n
  P.26.46 | `. . . . . <PricePer>` | `<j239>` | 60 | 0…1
  ○ | `. . . . . <PriceCondition>` | `<pricecondition>` |  | 0…n
  P.26.47 | `. . . . . . <PriceCondition​Type>` | `<x463>` | 167 | 1
  ○ | `. . . . . . <PriceCondition​Quantity>` | `<pricecondition​quantity>` |  | 0…n
  P.26.48 | `. . . . . . . <PriceCondition​QuantityType>` | `<x464>` | 168 | 1
  P.26.49 | `. . . . . . . <Quantity>` | `<x320>` |  | 1
  P.26.50 | `. . . . . . . <QuantityUnit>` | `<x466>` | 169 | 1
  ○ | `. . . . . . <ProductIdentifier>` | `<productidentifier>` | ‡ | 0…n
  P.26.50a | `. . . . . . . <ProductIDType>` | `<b221>` | 5 ‡ | 1
  P.26.50b | `. . . . . . . <IDTypeName>` | `<b233>` | ‡ | 0…1
  P.26.50c | `. . . . . . . <IDValue>` | `<b244>` | ‡ | 1
  P.26.51 | `. . . . . <MinimumOrderQuantity>` | `<j263>` |  | 0…1
  ○ | `. . . . . <BatchBonus>` | `<batchbonus>` |  | 0…n
  P.26.52 | `. . . . . . <BatchQuantity>` | `<j264>` |  | 1
  P.26.53 | `. . . . . . <FreeQuantity>` | `<j265>` |  | 1
  ○ | `. . . . . <DiscountCoded>` | `<discountcoded>` |  | 0…n
  P.26.54 | `. . . . . . <DiscountCode​Type>` | `<j363>` | 100 | 1
  P.26.55 | `. . . . . . <DiscountCode​TypeName>` | `<j378>` | la | 0…1
  P.26.56 | `. . . . . . <DiscountCode>` | `<j364>` |  | 1
  ○ | `. . . . . <Discount>` | `<discount>` |  | 0…n
  P.26.57 | `. . . . . . <DiscountType>` | `<x467>` | 170 | 0…1
  P.26.58 | `. . . . . . <Quantity>` | `<x320>` |  | 0…1
  P.26.58a | `. . . . . . <ToQuantity>` | `<x514>` | ‡ | 0…1
  P.26.59 | `. . . . . . <DiscountPercent>` | `<j267>` |  | 0…1
  P.26.60 | `. . . . . . <DiscountAmount>` | `<x469>` |  | 0…1
  P.26.61 | `. . . . . <PriceStatus>` | `<j266>` | 61 | 0…1
  P.26.62 | `. . . . . <PriceAmount>` | `<j151>` |  | 0…1
  ○ | `. . . . . <PriceCoded>` | `<pricecoded>` |  | 0…1
  P.26.63 | `. . . . . . <PriceCodeType>` | `<x465>` | 179 | 1
  P.26.64 | `. . . . . . <PriceCodeTypeName>` | `<x477>` | la | 0…1
  P.26.65 | `. . . . . . <PriceCode>` | `<x468>` |  | 1
  ○ | `. . . . . <Tax>` | `<tax>` |  | 0…n
  ○ | `. . . . . . <ProductIdentifier>` | `<productidentifier` | § | 0…n
  P.26.65a | `. . . . . . . <ProductIDType>` | `<b221>` | 5 § | 1
  P.26.65b | `. . . . . . . <IDTypeName>` | `<b233>` | la § | 0…1
  P.26.65c | `. . . . . . . <IDValue>` | `<b244>` | § | 1
  P.26.65d | `. . . . . . <PricePartDescription>` | `<x535` | la ∆ | 0…n
  P.26.66 | `. . . . . . <TaxType>` | `<x470>` | 171 | 0…1
  P.26.67 | `. . . . . . <TaxRateCode>` | `<x471>` | 62 | 0…1
  P.26.68 | `. . . . . . <TaxRatePercent>` | `<x472>` |  | 0…1
  P.26.69 | `. . . . . . <TaxableAmount>` | `<x473>` |  | 0…1
  P.26.70 | `. . . . . . <TaxAmount>` | `<x474>` |  | 0…1
  P.26.70a | `. . . . . <TaxExempt/>` | `<x546/>` | Φ | 0…1
  P.26.70b | `. . . . . <UnpricedItemType>` | `<j192>` | 57 § | 0…1
  P.26.71 | `. . . . . <CurrencyCode>` | `<j152>` | 96 | 0…1
  ○ | `. . . . . <Territory>` | `<territory>` |  | 0…1
  P.26.72 | `. . . . . . <CountriesIncluded>` | `<x449>` | 91 | 0…1
  P.26.73 | `. . . . . . <RegionsIncluded>` | `<x450>` | 49 | 0…1
  P.26.74 | `. . . . . . <CountriesExcluded>` | `<x451>` | 91 | 0…1
  P.26.75 | `. . . . . . <RegionsExcluded>` | `<x452>` | 49 | 0…1
  ○ | `. . . . . <Comparison​ProductPrice>` | `<comparison​productprice>` |  | 0…n
  ○ | `. . . . . . <ProductIdentifier>` | `<productidentifier>` |  | 1…n
  P.26.77 | `. . . . . . . <ProductIDType>` | `<b221>` | 5 | 1
  P.26.78 | `. . . . . . . <IDTypeName>` | `<b233>` | la | 0…1
  P.26.79 | `. . . . . . . <IDValue>` | `<b244>` |  | 1
  P.26.80 | `. . . . . . <PriceType>` | `<x462>` | 58 | 0…1
  P.26.81 | `. . . . . . <PriceAmount>` | `<j151>` |  | 1
  P.26.82 | `. . . . . . <CurrencyCode>` | `<j152>` | 96 | 0…1
  ○ | `. . . . . <PriceDate>` | `<pricedate>` |  | 0…n
  P.26.83 | `. . . . . . <PriceDateRole>` | `<x476>` | 173 | 1
  P.26.85 | `. . . . . . <Date>` | `<b306>` | df | 1
  P.26.86 | `. . . . . <PrintedOnProduct>` | `<x301>` | 174 | 0…1
  P.26.87 | `. . . . . <PositionOnProduct>` | `<x313>` | 142 | 0…1
  P.26.149 | `. <NoProduct/>` | `<x507/>` | ‡ | 0…1

#### A.2 Sample messages

While it is clearly impossible for a single, realistic example message to illustrate all features of ONIX for Books, the annotated sample message below has been chosen so that it highlights a number of the features of Releases 3.0 and 3.1 which will be most commonly used. It illustrates a single, ‘typical’ Product record, rather than trying to include all possible features that could occur in a single Product record. The sample message is based on a real book from a real publisher (HarperCollins’ 2006 paperback version of Roseanna by Maj Sjöwall and Per Wahlöö, ISBN 978‑0‑00‑723283‑3), but is not that publisher’s real ONIX output: it’s a constructed example that purports to have been sent by a fictitious data aggregator to an equally fictitious Internet-based international bookseller, based on information supplied by the publisher.

There are two versions of the sample message, using Reference names and Short tags, and their content is identical. Throughout the examples, data in red indicates values taken from the ONIX code lists, text in blue indicates free text or other content not taken from ONIX code lists – though note that it may still be subject to specific format requirements such as XHTML markup, or an identifier or date/time format, or drawn from some external controlled vocabulary. Lines are numbered and annotated for convenience – an actual ONIX message would contain only the XML in the middle column of the table. The examples are indented for clarity, but a real message should (ideally) not be indented.

Note that the message is sent using the UTF‑8 character encoding, so non-ASCII characters (such as ‘ö’ in the authors’ names) need no special encoding.

In addition to the complete example message, an example block update that provides replacement prices (a ‘P&A update’) is also included. Note that in a block update, blocks that remain unchanged are omitted entirely – only blocks that contain additional or updated data are included in the Product record. Contrarily, unchanged data within an updated block must still be included: the updated block must be complete.

Although the two examples contain only a single Product record in each message file, multiple full records and multiple block updates can be freely mixed within a single ONIX message.

The sample message files can be downloaded from the EDItEUR website.

  complete sample message
  # | using Reference names | Commentary
  --- | --- | ---
  | `<?xml version="1.0" encoding="UTF-8"?>` | File may contain extended characters without need for special coding
  | `<ONIXMessage release="3.1" xmlns="http://ns.editeur.org/​onix/​3.1/​reference">` | Upper case M, mandatory release attribute
  | `<Header>` |
  | `<Sender>` |
  | `<SenderName>Global Bookinfo​</SenderName>` | From fictitious aggregator…
  | `<ContactName>Jane King​</ContactName>` |
  | `<TelephoneNumber>+1 212 555 0123​</TelephoneNumber>` |
  | `<EmailAddress>jbk@globalbookinfo.com​</EmailAddress>` |
  | `</Sender>` |
  | `<Addressee>` |
  | `<AddresseeName>BooksBooksBooks.com​</AddresseeName>` | …to fictitious bookseller
  | `</Addressee>` |
  | `<MessageNumber>231​</MessageNumber>` | Allows recipient to check for missed messages
  | `<SentDateTime>20100510T1115-0400​</SentDateTime>` | 10 May 2010, 11:15am EDT (3:15pm UTC)
  | `<MessageNote>Sample message​</MessageNote>` |
  | `</Header>` |
  | `<!-- product record 1 of 1 in message -->` |
  | `<Product>` | Start of Product record
  | `<RecordReference>com.globalbookinfo.​onix.​01734529​</RecordReference>` | Unique record reference assured by using reversed web domain plus internal product ID
  | `<NotificationType>03​</NotificationType>` | Confirmed post-publication
  | `<RecordSourceType>04​</RecordSourceType>` | Bibliographic agency
  | `<RecordSourceIdentifier>` |
  | `<RecordSourceIDType>06​</RecordSourceIDType>` | GLN
  | `<IDValue>0614141800001​</IDValue>` |
  | `</RecordSourceIdentifier>` |
  | `<RecordSourceName>Global Bookinfo​</RecordSourceName>` |
  | `<ProductIdentifier>` |
  | `<ProductIDType>03​</ProductIDType>` | ISBN as GTIN-13
  | `<IDValue>9780007232833​</IDValue>` |
  | `</ProductIdentifier>` |
  | `<ProductIdentifier>` |
  | `<ProductIDType>15​</ProductIDType>` | Explicitly an ISBN
  | `<IDValue>9780007232833​</IDValue>` |
  | `</ProductIdentifier>` |
  | `<DescriptiveDetail>` | Start of Block 1
  | `<ProductComposition>00​</ProductComposition>` | Single-item retail product
  | `<ProductForm>BC​</ProductForm>` | Paperback
  | `<ProductFormDetail>B105​</ProductFormDetail>` | B-format
  | `<Measure>` |
  | `<MeasureType>01​</MeasureType>` | Height
  | `<Measurement>197​</Measurement>` |
  | `<MeasureUnitCode>mm​</MeasureUnitCode>` |
  | `</Measure>` |
  | `<Measure>` |
  | `<MeasureType>02​</MeasureType>` | Width
  | `<Measurement>130​</Measurement>` |
  | `<MeasureUnitCode>mm​</MeasureUnitCode>` |
  | `</Measure>` |
  | `<Measure>` |
  | `<MeasureType>03​</MeasureType>` | Spine thickness
  | `<Measurement>18​</Measurement>` |
  | `<MeasureUnitCode>mm​</MeasureUnitCode>` |
  | `</Measure>` |
  | `<Measure>` |
  | `<MeasureType>08​</MeasureType>` | Weight
  | `<Measurement>195​</Measurement>` |
  | `<MeasureUnitCode>gr​</MeasureUnitCode>` |
  | `</Measure>` |
  | `<CountryOfManufacture>GB​</CountryOfManufacture>` |
  | `<ProductClassification>` |
  | `<ProductClassificationType>03​</ProductClassificationType>` | HMRC commodity code
  | `<ProductClassificationCode>49019900​</ProductClassificationCode>` |
  | `</ProductClassification>` |
  | `<Collection>` | Collection detail
  | `<CollectionType>10​</CollectionType>` | Publisher collection
  | `<TitleDetail>` |
  | `<TitleType>01​</TitleType>` | Distinctive title (of collection)
  | `<TitleElement>` |
  | `<SequenceNumber>2​</SequenceNumber>` |
  | `<TitleElementLevel>02​</TitleElementLevel>` | Collection level
  | `<TitlePrefix textcase="01">The​</TitlePrefix>` |
  | `<TitleWithoutPrefix textcase="01">Martin Beck series​</TitleWithoutPrefix>` | Sentence case
  | `</TitleElement>` |
  | `<TitleElement>` |
  | `<SequenceNumber>3​</SequenceNumber>` |
  | `<TitleElementLevel>01​</TitleElementLevel>` | Product level
  | `<PartNumber>1​</PartNumber>` | First in collection
  | `</TitleElement>` |
  | `</TitleDetail>` |
  | `</Collection>` |
  | `<TitleDetail>` |
  | `<TitleType>01​</TitleType>` | Distinctive title
  | `<TitleElement>` |
  | `<SequenceNumber>1​</SequenceNumber>` |
  | `<TitleElementLevel>01​</TitleElementLevel>` | Product level
  | `<NoPrefix/>` |
  | `<TitleWithoutPrefix textcase="01">Roseanna​</TitleWithoutPrefix>` |
  | `</TitleElement>` |
  | `</TitleDetail>` |
  | `<TitleDetail>` |
  | `<TitleType>10​</TitleType>` | Distributor’s title
  | `<TitleElement>` |
  | `<TitleElementLevel>01​</TitleElementLevel>` | Product level
  | `<TitleText>ROSEANNA (MARTIN BECK #1)​</TitleText>` |
  | `</TitleElement>` |
  | `</TitleDetail>` |
  | `<Contributor>` |
  | `<SequenceNumber>1​</SequenceNumber>` | Contributor 1
  | `<ContributorRole>A01​</ContributorRole>` | Written by
  | `<NameIdentifier>` |
  | `<NameIDType>01​</NameIDType>` | Proprietary
  | `<IDTypeName>HCP Author ID​</IDTypeName>` |
  | `<IDValue>7421​</IDValue>` |
  | `</NameIdentifier>` |
  | `<NameIdentifier>` |
  | `<NameIDType>16​</NameIDType>` | ISNI
  | `<IDValue>0000000121479135​</IDValue>` |
  | `</NameIdentifier>` |
  | `<NamesBeforeKey>Maj​</NamesBeforeKey>` |
  | `<KeyNames>Sjöwall​</KeyNames>` |
  | `<BiographicalNote textformat="05"><p><strong>Maj Sjöwall</strong> was born in Stockholm in 1935. She is a poet, novelist and translator, and is best known for the ten <cite>Martin Beck</cite> novels she wrote with husband Per Wahlöö.</p>​</BiographicalNote>` |
  | `</Contributor>` |
  | `<Contributor>` |
  | `<SequenceNumber>2​</SequenceNumber>` | Contributor 2
  | `<ContributorRole>A01​</ContributorRole>` | Written by
  | `<NameIdentifier>` |
  | `<NameIDType>01​</NameIDType>` | Proprietary
  | `<IDTypeName>HCP Author ID​</IDTypeName>` |
  | `<IDValue>7422​</IDValue>` |
  | `</NameIdentifier>` |
  | `<NameIdentifier>` |
  | `<NameIDType>16​</NameIDType>` | ISNI
  | `<IDValue>0000000121222604​</IDValue>` |
  | `</NameIdentifier>` |
  | `<NamesBeforeKey>Per​</NamesBeforeKey>` |
  | `<KeyNames>Wahlöö​</KeyNames>` |
  | `<BiographicalNote textformat="05"><p><strong>Per Wahlöö</strong> was born in Göteborg. After graduating from the University of Lund in 1946, he worked as a journalist, covering criminal and social issues for a number of newspapers and magazines. In the 1950s, Wahlöö became involved with radical political causes, activities that resulted in his deportation from Franco’s Spain in 1957. After returning to Sweden, he wrote a number of television and radio plays, and was managing editor of several magazines, before becoming a full-time writer.</p><p>He is best known for the series of ten <cite>Martin Beck</cite> novels he wrote with wife Maj Sjöwall, which they completed immediately before his death in 1975.</p>​</BiographicalNote>` |
  | `</Contributor>` |
  | `<Contributor>` |
  | `<SequenceNumber>3​</SequenceNumber>` | Contributor 3
  | `<ContributorRole>B06​</ContributorRole>` | Translator
  | `<FromLanguage>swe​</FromLanguage>` | from Swedish
  | `<NameIdentifier>` |
  | `<NameIDType>01​</NameIDType>` | Proprietary
  | `<IDTypeName>HCP Author ID​</IDTypeName>` |
  | `<IDValue>11150​</IDValue>` |
  | `</NameIdentifier>` |
  | `<NamesBeforeKey>Lois​</NamesBeforeKey>` |
  | `<KeyNames>Roth​</KeyNames>` |
  | `</Contributor>` |
  | `<Contributor>` |
  | `<SequenceNumber>4​</SequenceNumber>` | Contributor 4
  | `<ContributorRole>A24​</ContributorRole>` | Introduction by
  | `<NameIdentifier>` |
  | `<NameIDType>01​</NameIDType>` | Proprietary
  | `<IDTypeName>HCP Author ID​</IDTypeName>` |
  | `<IDValue>11151​</IDValue>` |
  | `</NameIdentifier>` |
  | `<NameIdentifier>` |
  | `<NameIDType>16​</NameIDType>` | ISNI
  | `<IDValue>0000000122824957​</IDValue>` |
  | `</NameIdentifier>` |
  | `<NamesBeforeKey>Henning​</NamesBeforeKey>` |
  | `<KeyNames>Mankell​</KeyNames>` |
  | `</Contributor>` |
  | `<ContributorStatement>By Maj Sjöwall and Per Wahlöö, translated by Lois Roth and with an introduction by Henning Mankell​</ContributorStatement>` | Text may be used for display by websites
  | `<NoEdition/>` |
  | `<Language>` | No default language in header
  | `<LanguageRole>01​</LanguageRole>` | Language of text
  | `<LanguageCode>eng​</LanguageCode>` | English
  | `</Language>` |
  | `<Language>` |
  | `<LanguageRole>02​</LanguageRole>` | Language of original
  | `<LanguageCode>swe​</LanguageCode>` | Swedish
  | `</Language>` |
  | `<Extent>` |
  | `<ExtentType>00​</ExtentType>` | Main content page count
  | `<ExtentValue>245​</ExtentValue>` |
  | `<ExtentUnit>03​</ExtentUnit>` | Pages
  | `</Extent>` |
  | `<Extent>` |
  | `<ExtentType>04​</ExtentType>` | Back matter page count
  | `<ExtentValue>16​</ExtentValue>` |
  | `<ExtentUnit>03​</ExtentUnit>` | Pages
  | `</Extent>` |
  | `<Subject>` |
  | `<MainSubject/>` | Main
  | `<SubjectSchemeIdentifier>93​</SubjectSchemeIdentifier>` | Thema subject category code
  | `<SubjectSchemeVersion>1.3​</SubjectSchemeVersion>` | Version 1.3
  | `<SubjectCode>FFP​</SubjectCode>` | Police procedural
  | `</Subject>` |
  | `<Subject>` |
  | `<SubjectSchemeIdentifier>93​</SubjectSchemeIdentifier>` | Thema subject category code
  | `<SubjectSchemeVersion>1.3​</SubjectSchemeVersion>` |
  | `<SubjectCode>FYT​</SubjectCode>` | Fiction in translation
  | `</Subject>` |
  | `<Subject>` |
  | `<SubjectSchemeIdentifier>94​</SubjectSchemeIdentifier>` | Thema place qualifier
  | `<SubjectSchemeVersion>1.3​</SubjectSchemeVersion>` |
  | `<SubjectCode>1DNS​</SubjectCode>` | Sweden
  | `</Subject>` |
  | `<Subject>` |
  | `<SubjectSchemeIdentifier>96​</SubjectSchemeIdentifier>` | Thema time period qualifier
  | `<SubjectSchemeVersion>1.3​</SubjectSchemeVersion>` |
  | `<SubjectCode>3MPQS​</SubjectCode>` | 1960s
  | `</Subject>` |
  | `<Subject>` |
  | `<MainSubject/>` | Main
  | `<SubjectSchemeIdentifier>10​</SubjectSchemeIdentifier>` | BISAC subject heading code
  | `<SubjectSchemeVersion>2017​</SubjectSchemeVersion>` | 2017 version
  | `<SubjectCode>FIC022000​</SubjectCode>` | Mystery and detective
  | `</Subject>` |
  | `<Subject>` |
  | `<SubjectSchemeIdentifier>20​</SubjectSchemeIdentifier>` | Keywords
  | `<SubjectHeadingText>Martin Beck; Roseanna McGraw; Lake Vättern; Stockholm; police procedural​</SubjectHeadingText>` |
  | `</Subject>` |
  | `<Audience>` |
  | `<AudienceCodeType>01​</AudienceCodeType>` | ONIX audience code
  | `<AudienceCodeValue>01​</AudienceCodeValue>` | General/trade
  | `</Audience>` |
  | `<Audience>` |
  | `<AudienceCodeType>22​</AudienceCodeType>` | ONIX adult audience rating
  | `<AudienceCodeValue>01​</AudienceCodeValue>` | Any adult audience
  | `</Audience>` |
  | `</DescriptiveDetail>` | End of Block 1
  | `<CollateralDetail>` | Start of Block 2
  | `<TextContent>` |
  | `<TextType>02​</TextType>` | Short description
  | `<ContentAudience>00​</ContentAudience>` | Any audience
  | `<Text textformat="05"><p><strong>Perennial relaunches the first novel in the classic Martin Beck detective series from the 1960s</strong> – the novels that have inspired all crime fiction written ever since.</p>​</Text>` | XHTML markup
  | `</TextContent>` |
  | `<TextContent>` |
  | `<TextType>03​</TextType>` | (Long) Description
  | `<ContentAudience>00​</ContentAudience>` | Any audience
  | `<Text textformat="05"><p>Widely recognized as the among the greatest crime fiction ever written, this is the first of a series of stories that pioneered the police procedural genre. The series was translated into 35 languages, sold over 10 million copies around the world, and inspired writers from Henning Mankell to Jonathan Franzen.</p><p>Written in 1965, <cite>Roseanna</cite> is the work of Maj Sjöwall and Per Wahlöö – a husband and wife team from Sweden, and this volume has a new introduction to help bring their work to a new audience. The novel follows the fortunes of the detective Martin Beck, whose enigmatic and taciturn character has inspired countless other policemen in crime fiction.</p><p><cite>Roseanna</cite> begins on a July afternoon: the body of a young woman is dredged from a canal near Sweden’s beautiful Lake Vättern. Three months later, all that Police Inspector Martin Beck knows is that her name is Roseanna, that she came from Lincoln, Nebraska, and that she could have been strangled by any one of eighty-five people.</p><p>With its authentically rendered settings and vividly realized characters, and its command over the intricately woven details of police detection, <cite>Roseanna</cite> is a masterpiece of suspense and sadness.</p>​</Text>` | Multiple paragraphs
  | `</TextContent>` |
  | `<TextContent>` |
  | `<SequenceNumber>1​</SequenceNumber>` | First
  | `<TextType>06​</TextType>` | Review quote
  | `<ContentAudience>00​</ContentAudience>` | Any audience
  | `<Text textformat="05"><p>‘The writing is elegant and surprisingly humorous – if you haven’t come across Beck before, you’re in for a treat.’</p>​</Text>` |
  | `<SourceTitle>The Guardian​</SourceTitle>` |
  | `</TextContent>` |
  | `<TextContent>` |
  | `<SequenceNumber>2​</SequenceNumber>` | Second
  | `<TextType>06​</TextType>` | Review quote
  | `<ContentAudience>00​</ContentAudience>` | Any audience
  | `<Text textformat="05"><p>‘Their mysteries don’t just read well; they reread even better. Witness, wife, petty cop or crook – they’re all real characters even if they get just a few sentences. The plots hold, because they’re ingenious but never inhuman.’</p>​</Text>` |
  | `<SourceTitle>New York Times​</SourceTitle>` |
  | `</TextContent>` |
  | `<TextContent>` |
  | `<TextType>10​</TextType>` | Promotional headline
  | `<ContentAudience>00​</ContentAudience>` | Any audience
  | `<Text>One of the greatest masterpieces of crime fiction​</Text>` |
  | `</TextContent>` |
  | `<CitedContent>` |
  | `<CitedContentType>03​</CitedContentType>` | Media mention (feature article)
  | `<ContentAudience>00​</ContentAudience>` | Any audience
  | `<SourceType>01​</SourceType>` | Printed media
  | `<SourceTitle>Observer Magazine​</SourceTitle>` |
  | `<CitationNote>Interview with Maj Sjöwall by Louise France​</CitationNote>` |
  | `<ResourceLink>https://www.​guardian.​co.​uk/​books/​2009/​nov/​22/​crime-​thriller-​maj-​sjowall-​sweden​</ResourceLink>` | URL
  | `<ContentDate>` |
  | `<ContentDateRole>01</ContentDateRole>` | Publication date (of article)
  | `<Date dateformat="00">20091122</Date>` |
  | `</ContentDate>` |
  | `</CitedContent>` |
  | `<SupportingResource>` |
  | `<ResourceContentType>01​</ResourceContentType>` | Front cover
  | `<ContentAudience>00​</ContentAudience>` | All audiences
  | `<ResourceMode>03​</ResourceMode>` | Image
  | `<ResourceVersion>` |
  | `<ResourceForm>02​</ResourceForm>` | Downloadable
  | `<ResourceVersionFeature>` |
  | `<ResourceVersionFeatureType>01​</ResourceVersionFeatureType>` | File format
  | `<FeatureValue>D502​</FeatureValue>` | JPEG
  | `</ResourceVersionFeature>` |
  | `<ResourceVersionFeature>` |
  | `<ResourceVersionFeatureType>02​</ResourceVersionFeatureType>` | Image height
  | `<FeatureValue>341​</FeatureValue>` | in pixels
  | `</ResourceVersionFeature>` |
  | `<ResourceVersionFeature>` |
  | `<ResourceVersionFeatureType>03​</ResourceVersionFeatureType>` | Image width
  | `<FeatureValue>222​</FeatureValue>` | in pixels
  | `</ResourceVersionFeature>` |
  | `<ResourceLink>https://www.harpercollins.​co.​uk/​covers/​9780007232833.​jpg​</ResourceLink>` | URL
  | `<ContentDate>` |
  | `<ContentDateRole>17​</ContentDateRole>` | Last updated
  | `<Date dateformat="00">20060412​</Date>` |
  | `</ContentDate>` |
  | `</ResourceVersion>` |
  | `</SupportingResource>` |
  | `<SupportingResource>` |
  | `<ResourceContentType>15​</ResourceContentType>` | Sample content
  | `<ContentAudience>00​</ContentAudience>` | All audiences
  | `<ResourceMode>06​</ResourceMode>` | Multi-mode (a web page)
  | `<ResourceVersion>` |
  | `<ResourceForm>01​</ResourceForm>` | Linkable resource
  | `<ResourceLink>https://browseinside.​harpercollins.​co.​uk/​pageview?​isbn=​9780007232833​</ResourceLink>` | URL
  | `</ResourceVersion>` |
  | `</SupportingResource>` |
  | `</CollateralDetail>` | End of Block 2
  | `<!-- there is no Block 3 or Block 7 -->` |
  | `<PublishingDetail>` | Start of Block 4
  | `<Imprint>` |
  | `<ImprintName>HarperPerennial​</ImprintName>` |
  | `</Imprint>` |
  | `<Publisher>` |
  | `<PublishingRole>01​</PublishingRole>` | Publisher
  | `<PublisherIdentifier>` |
  | `<PublisherIDType>16</PublisherIDType>` | ISNI
  | `<IDValue>0000000404222532</IDValue>` |
  | `</PublisherIdentifier>` |
  | `<PublisherName>HarperCollins Publishers​</PublisherName>` |
  | `<Website>` |
  | `<WebsiteRole>01</WebsiteRole>` | Corporate site
  | `<WebsiteLink>https://​www.harpercollins.co.uk​</WebsiteLink>` |
  | `</Website>` |
  | `</Publisher>` |
  | `<CityOfPublication>London​</CityOfPublication>` |
  | `<CountryOfPublication>GB​</CountryOfPublication>` |
  | `<PublishingStatus datestamp="20100508">04​</PublishingStatus>` | Active
  | `<PublishingDate>` |
  | `<PublishingDateRole>01​</PublishingDateRole>` | Date of publication (of product)
  | `<Date dateformat="00">20060807​</Date>` | dateformat=YYYYMMDD
  | `</PublishingDate>` |
  | `<PublishingDate>` |
  | `<PublishingDateRole>11​</PublishingDateRole>` | Date of first publication (of work)
  | `<Date dateformat="05">1968​</Date>` | dateformat=YYYY
  | `</PublishingDate>` |
  | `<PublishingDate>` |
  | `<PublishingDateRole>20​</PublishingDateRole>` | Pub date in original language
  | `<Date dateformat="05">1965​</Date>` | dateformat=YYYY
  | `</PublishingDate>` |
  | `<CopyrightStatement>` |
  | `<CopyrightType>C</CopyrightType>` | Text copyright
  | `<CopyrightYear>1965</CopyrightYear>` | dateformat=default (YYYY)
  | `<CopyrightOwner>` |
  | `<PersonName>Maj Sjöwall</PersonName>` | Joint rightsholders
  | `</CopyrightOwner>` |
  | `<CopyrightOwner>` |
  | `<PersonName>Per Wahlöö</PersonName>` |
  | `</CopyrightOwner>` |
  | `</CopyrightStatement>` |
  | `<CopyrightStatementText>© Maj Sjöwall and Per Wahlöö 1965</CopyrightStatementText>` |
  | `<SalesRights>` |
  | `<SalesRightsType>01​</SalesRightsType>` | For sale (publisher has exclusive rights in territory)
  | `<Territory>` |
  | `<CountriesIncluded>AG AI AU BB BD BM BN BS BW BZ CM CY DM EG FJ FK GB GD GG GH GI GM GY HK IE IL IM IN IO JE JM JO KE KI KN KW KY LC LK LS MT MU MV MW MY MZ NA NG NR NZ PG PK PN SB SC SD SG SH SL SO SZ TC TO TT TV TZ UG VC VG VU WS YE RS ME ZA ZM ZW​</CountriesIncluded>` | Broadly, this is ‘Commonwealth excluding Canada’
  | `</Territory>` |
  | `</SalesRights>` |
  | `<SalesRights>` |
  | `<SalesRightsType>06​</SalesRightsType>` | Not for sale (publisher has no rights in territory)
  | `<Territory>` |
  | `<CountriesIncluded>AS CA GU MP PH PR US VI​</CountriesIncluded>` | Broadly, the ‘US Market’ and Canada
  | `</Territory>` |
  | `</SalesRights>` |
  | `<SalesRights>` |
  | `<SalesRightsType>02​</SalesRightsType>` | For sale (publisher has non-exclusive rights in rest of world)
  | `<Territory>` |
  | `<RegionsIncluded>WORLD​</RegionsIncluded>` | Everywhere…
  | `<CountriesExcluded>AG AI AU BB BD BM BN BS BW BZ CM CY DM EG FJ FK GB GD GG GH GI GM GY HK IE IL IM IN IO JE JM JO KE KI KN KW KY LC LK LS MT MU MV MW MY MZ NA NG NR NZ PG PK PN SB SC SD SG SH SL SO SZ TC TO TT TV TZ UG VC VG VU WS YE RS ME ZA ZM ZW AS CA GU MP PH PR US VI​</CountriesExcluded>` | other than the countries where rights type is 01 or 06
  | `</Territory>` |
  | `</SalesRights>` |
  | `<!-- no ROW sales rights type needed -->` |
  | `</PublishingDetail>` | End of Block 4
  | `<RelatedMaterial>` | Start of Block 5
  | `<RelatedWork>` |
  | `<WorkRelationCode>01​</WorkRelationCode>` | Is manifestation of
  | `<WorkIdentifier>` |
  | `<WorkIDType>11​</WorkIDType>` | (former) ISTC
  | `<IDValue>A0220090000154FA​</IDValue>` |
  | `</WorkIdentifier>` |
  | `</RelatedWork>` |
  | `<RelatedProduct>` |
  | `<ProductRelationCode>06​</ProductRelationCode>` | Alternative format
  | `<ProductRelationCode>27​</ProductRelationCode>` | E-version
  | `<ProductIdentifier>` |
  | `<ProductIDType>03​</ProductIDType>` | GTIN-13
  | `<IDValue>9780007324378​</IDValue>` |
  | `</ProductIdentifier>` |
  | `<ProductIdentifier>` |
  | `<ProductIDType>15​</ProductIDType>` | ISBN
  | `<IDValue>9780007324378​</IDValue>` |
  | `</ProductIdentifier>` |
  | `</RelatedProduct>` |
  | `</RelatedMaterial>` | End of Block 5
  | `<!-- there is no Block 8 -->` |
  | `<ProductSupply>` | Start of Block 6
  | `<MarketReference>NAAU3</MarketReference>` | Arbitrary label for market
  | `<Market>` |
  | `<Territory>` |
  | `<RegionsIncluded>WORLD​</RegionsIncluded>` | Market is world…
  | `<CountriesExcluded>AS AU CA GU MP NZ PH PR US VI ZA​</CountriesExcluded>` | …minus countries with no rights and three countries with separate exclusive distributorships (the latter could additionally be represented by separate <ProductSupply> sections)
  | `</Territory>` |
  | `</Market>` |
  | `<MarketPublishingDetail>` |
  | `<MarketPublishingStatus>04​</MarketPublishingStatus>` | Active
  | `<MarketDate>` |
  | `<MarketDateRole>01​</MarketDateRole>` | Pub date in this market
  | `<Date dateformat="00">20060807​</Date>` | dateformat=YYYYMMDD
  | `</MarketDate>` |
  | `</MarketPublishingDetail>` |
  | `<SupplyDetail>` |
  | `<Supplier>` |
  | `<SupplierRole>01​</SupplierRole>` | Publisher supplying to retailers
  | `<SupplierIdentifier>` |
  | `<SupplierIDType>06​</SupplierIDType>` | GLN for orders
  | `<IDValue>5051366000000​</IDValue>` |
  | `</SupplierIdentifier>` |
  | `<SupplierIdentifier>` |
  | `<SupplierIDType>07​</SupplierIDType>` | SAN for orders
  | `<IDValue>0091073​</IDValue>` |
  | `</SupplierIdentifier>` |
  | `<SupplierName>HarperCollins Publishers​</SupplierName>` |
  | `<TelephoneNumber>+44 1417 723200​</TelephoneNumber>` |
  | `</Supplier>` |
  | `<ReturnsConditions>` |
  | `<ReturnsCodeType>04​</ReturnsCodeType>` | ONIX returns indicator
  | `<ReturnsCode>03​</ReturnsCode>` | Sale or return
  | `</ReturnsConditions>` |
  | `<ProductAvailability datestamp="20100507">21​</ProductAvailability>` | In stock
  | `<PackQuantity>16​</PackQuantity>` | 16 copies in a carton
  | `<Price>` | Price 1 for UK
  | `<PriceType>02​</PriceType>` | RRP including tax
  | `<DiscountCoded>` |
  | `<DiscountCodeType>01​</DiscountCodeType>` | BIC discount group code
  | `<DiscountCode>AHACP029​</DiscountCode>` | HCP discount group 29
  | `</DiscountCoded>` |
  | `<PriceStatus>02​</PriceStatus>` | Firm price
  | `<PriceAmount>7.99​</PriceAmount>` |
  | `<Tax>` |
  | `<TaxType>01​</TaxType>` | VAT
  | `<TaxRateCode>Z​</TaxRateCode>` | Zero-rated
  | `<TaxRatePercent>0</TaxRatePercent>` | 0%
  | `<TaxableAmount>7.99​</TaxableAmount>` |
  | `<TaxAmount>0.00</TaxAmount>` |
  | `</Tax>` |
  | `<CurrencyCode>GBP​</CurrencyCode>` | Pounds Sterling
  | `<Territory>` | Price applicable to…
  | `<CountriesIncluded>GB​</CountriesIncluded>` |
  | `</Territory>` |
  | `<PrintedOnProduct>02​</PrintedOnProduct>` | Price on product
  | `<PositionOnProduct>01​</PositionOnProduct>` | On outside back cover
  | `</Price>` |
  | `<Price>` | Price 2 for Eurozone
  | `<PriceType>01​</PriceType>` | RRP excluding tax
  | `<Discount>` |
  | `<DiscountPercent>37.5​</DiscountPercent>` | 37.5% discount
  | `</Discount>` |
  | `<PriceStatus>02​</PriceStatus>` | Firm price
  | `<PriceAmount>8.99​</PriceAmount>` |
  | `<CurrencyCode>EUR​</CurrencyCode>` | Euro
  | `<Territory>` | Price applicable to…
  | `<CountriesIncluded>AT BE CY FI FR DE ES GR IE IT LU MT NL PT SI SK AD MC ME SM VA​</CountriesIncluded>` | Euro-using countries in Europe
  | `</Territory>` |
  | `<PrintedOnProduct>01​</PrintedOnProduct>` | Price not on product
  | `</Price>` |
  | `<Price>` | Price 3 for remainder of market
  | `<PriceType>01​</PriceType>` | RRP excluding tax
  | `<Discount>` |
  | `<DiscountPercent>42.5​</DiscountPercent>` | 42.5% discount
  | `</Discount>` |
  | `<PriceStatus>02​</PriceStatus>` | Firm price
  | `<PriceAmount>7.99​</PriceAmount>` |
  | `<CurrencyCode>GBP​</CurrencyCode>` | Pounds Sterling
  | `<Territory>` | Price applicable to…
  | `<RegionsIncluded>WORLD​</RegionsIncluded>` | Remainder of market, ie world…
  | `<CountriesExcluded>GB AT BE CY FI FR DE ES GR IE IT LU MT NL PT SI SK AD MC ME SM VA AS AU CA GU MP NZ PH PR US VI ZA​</CountriesExcluded>` | …minus GB, Euro-using countries in Europe and countries without sales rights
  | `</Territory>` |
  | `<PrintedOnProduct>01​</PrintedOnProduct>` | Price not on product
  | `</Price>` |
  | `</SupplyDetail>` |
  | `</ProductSupply>` | End of Block 6
  | `<!-- aggregator could add other ProductSupply sections here, for AU/NZ and ZA distributors -->` |
  | `</Product>` |
  | `</ONIXMessage>` |

  # | using Short tags | Commentary
  --- | --- | ---
  | `<?xml version="1.0" encoding="UTF-8"?>` | File may contain extended characters without need for special coding
  | `<ONIXmessage release="3.1" xmlns="http://ns.editeur.org/​onix/​3.1/​short">` | Lower case m, mandatory release attribute
  | `<header>` |
  | `<sender>` |
  | `<x298>Global Bookinfo​</x298>` | From fictitious aggregator…
  | `<x299>Jane King​</x299>` |
  | `<j270>+1 212 555 0123​</j270>` |
  | `<j272>jbk@globalbookinfo.com​</j272>` |
  | `</sender>` |
  | `<addressee>` |
  | `<x300>BooksBooksBooks.com​</x300>` | …to fictitious bookseller
  | `</addressee>` |
  | `<m180>231​</m180>` | Allows recipient to check for missed messages
  | `<x307>20100510T1115-0400​</x307>` | 10 May 2010, 11:15am EDT (3:15pm UTC)
  | `<m183>Sample message​</m183>` |
  | `</header>` |
  | `<!-- product record 1 of 1 in message -->` |
  | `<product>` | Start of Product record
  | `<a001>com.globalbookinfo.​onix.​01734529​</a001>` | Unique record reference assured by using reversed web domain plus internal product ID
  | `<a002>03​</a002>` | Confirmed post-publication
  | `<a194>04​</a194>` | Bibliographic agency
  | `<recordsourceidentifier>` |
  | `<x311>06​</x311>` | GLN
  | `<b244>0614141800001​</b244>` |
  | `</recordsourceidentifier>` |
  | `<a197>Global Bookinfo​</a197>` |
  | `<productidentifier>` |
  | `<b221>03​</b221>` | ISBN as GTIN-13
  | `<b244>9780007232833​</b244>` |
  | `</productidentifier>` |
  | `<productidentifier>` |
  | `<b221>15​</b221>` | Explicitly an ISBN
  | `<b244>9780007232833​</b244>` |
  | `</productidentifier>` |
  | `<descriptivedetail>` | Start of Block 1
  | `<x314>00​</x314>` | Single-item retail product
  | `<b012>BC​</b012>` | Paperback
  | `<b333>B105​</b333>` | B-format
  | `<measure>` |
  | `<x315>01​</x315>` | Height
  | `<c094>197​</c094>` |
  | `<c095>mm​</c095>` |
  | `</measure>` |
  | `<measure>` |
  | `<x315>02​</x315>` | Width
  | `<c094>130​</c094>` |
  | `<c095>mm​</c095>` |
  | `</measure>` |
  | `<measure>` |
  | `<x315>03​</x315>` | Spine thickness
  | `<c094>18​</c094>` |
  | `<c095>mm​</c095>` |
  | `</measure>` |
  | `<measure>` |
  | `<x315>08​</x315>` | Weight
  | `<c094>195​</c094>` |
  | `<c095>gr​</c095>` |
  | `</measure>` |
  | `<x316>GB​</x316>` |
  | `<productclassification>` |
  | `<b274>03​</b274>` | HMRC commodity code
  | `<b275>49019900​</b275>` |
  | `</productclassification>` |
  | `<collection>` | Collection detail
  | `<x329>10​</x329>` | Publisher collection
  | `<titledetail>` |
  | `<b202>01​</b202>` | Distinctive title (of collection)
  | `<titleelement>` |
  | `<b034>2​</b034>` |
  | `<x409>02​</x409>` | Collection level
  | `<b030 textcase="01">The​</b030>` |
  | `<b031 textcase="01">Martin Beck series​</b031>` | Sentence case
  | `</titleelement>` |
  | `<titleelement>` |
  | `<b034>3​</b034>` |
  | `<x409>01​</x409>` | Product level
  | `<x410>1​</x410>` | First in collection
  | `</titleelement>` |
  | `</titledetail>` |
  | `</collection>` |
  | `<titledetail>` |
  | `<b202>01​</b202>` | Distinctive title
  | `<titleelement>` |
  | `<b034>1​</b034>` |
  | `<x409>01​</x409>` | Product level
  | `<x501/>` |
  | `<b031 textcase="01">Roseanna​</b031>` |
  | `</titleelement>` |
  | `</titledetail>` |
  | `<titledetail>` |
  | `<b202>10​</b202>` | Distributor’s title
  | `<titleelement>` |
  | `<x409>01​</x409>` | Product level
  | `<b203>ROSEANNA (MARTIN BECK #1)​</b203>` |
  | `</titleelement>` |
  | `</titledetail>` |
  | `<contributor>` |
  | `<b034>1​</b034>` | Contributor 1
  | `<b035>A01​</b035>` | Written by
  | `<nameidentifier>` |
  | `<x415>01​</x415>` | Proprietary
  | `<b233>HCP Author ID​</b233>` |
  | `<b244>7421​</b244>` |
  | `</nameidentifier>` |
  | `<nameidentifier>` |
  | `<x415>16​</x415>` | ISNI
  | `<b244>0000000121479135​</b244>` |
  | `</nameidentifier>` |
  | `<b039>Maj​</b039>` |
  | `<b040>Sjöwall​</b040>` |
  | `<b044 textformat="05"><p><strong>Maj Sjöwall</strong> was born in Stockholm in 1935. She is a poet, novelist and translator, and is best known for the ten <cite>Martin Beck</cite> novels she wrote with husband Per Wahlöö.</p>​</b044>` |
  | `</contributor>` |
  | `<contributor>` |
  | `<b034>2​</b034>` | Contributor 2
  | `<b035>A01​</b035>` | Written by
  | `<nameidentifier>` |
  | `<x415>01​</x415>` | Proprietary
  | `<b233>HCP Author ID​</b233>` |
  | `<b244>7422​</b244>` |
  | `</nameidentifier>` |
  | `<nameidentifier>` |
  | `<x415>16​</x415>` | ISNI
  | `<b244>0000000121222604​</b244>` |
  | `</nameidentifier>` |
  | `<b039>Per​</b039>` |
  | `<b040>Wahlöö​</b040>` |
  | `<b044 textformat="05"><p><strong>Per Wahlöö</strong> was born in Göteborg. After graduating from the University of Lund in 1946, he worked as a journalist, covering criminal and social issues for a number of newspapers and magazines. In the 1950s, Wahlöö became involved with radical political causes, activities that resulted in his deportation from Franco’s Spain in 1957. After returning to Sweden, he wrote a number of television and radio plays, and was managing editor of several magazines, before becoming a full-time writer.</p><p>He is best known for the series of ten <cite>Martin Beck</cite> novels he wrote with wife Maj Sjöwall, which they completed immediately before his death in 1975.</p>​</b044>` |
  | `</contributor>` |
  | `<contributor>` |
  | `<b034>3​</b034>` | Contributor 3
  | `<b035>B06​</b035>` | Translator
  | `<x412>swe​</x412>` | from Swedish
  | `<nameidentifier>` |
  | `<x415>01​</x415>` | Proprietary
  | `<b233>HCP Author ID​</b233>` |
  | `<b244>11150​</b244>` |
  | `</nameidentifier>` |
  | `<b039>Lois​</b039>` |
  | `<b040>Roth​</b040>` |
  | `</contributor>` |
  | `<contributor>` |
  | `<b034>4​</b034>` | Contributor 4
  | `<b035>A24​</b035>` | Introduction by
  | `<nameidentifier>` |
  | `<x415>01​</x415>` | Proprietary
  | `<b233>HCP Author ID​</b233>` |
  | `<b244>11151​</b244>` |
  | `</nameidentifier>` |
  | `<nameidentifier>` |
  | `<x415>16​</x415>` | ISNI
  | `<b244>0000000122824957​</b244>` |
  | `</nameidentifier>` |
  | `<b039>Henning​</b039>` |
  | `<b040>Mankell​</b040>` |
  | `</contributor>` |
  | `<b049>By Maj Sjöwall and Per Wahlöö, translated by Lois Roth and with an introduction by Henning Mankell​</b049>` | Text may be used for display by websites
  | `<n386/>` | No edition information
  | `<language>` | No default language in header
  | `<b253>01​</b253>` | Language of text
  | `<b252>eng​</b252>` | English
  | `</language>` |
  | `<language>` |
  | `<b253>02​</b253>` | Language of original
  | `<b252>swe​</b252>` | Swedish
  | `</language>` |
  | `<extent>` |
  | `<b218>00​</b218>` | Main content page count
  | `<b219>245​</b219>` |
  | `<b220>03​</b220>` | Pages
  | `</extent>` |
  | `<extent>` |
  | `<b218>04​</b218>` | Back matter page count
  | `<b219>16​</b219>` |
  | `<b220>03​</b220>` | Pages
  | `</extent>` |
  | `<subject>` |
  | `<x425/>` | Main
  | `<b067>93​</b067>` | Thema subject category code
  | `<b068>1.3​</b068>` | Version 1.3
  | `<b069>FFP​</b069>` | Police procedural
  | `</subject>` |
  | `<subject>` |
  | `<b067>93​</b067>` | Thema subject category code
  | `<b068>1.3​</b068>` |
  | `<b069>FYT​</b069>` | Fiction in translation
  | `</subject>` |
  | `<subject>` |
  | `<b067>93​</b067>` | Thema place qualifier
  | `<b068>1.3​</b068>` |
  | `<b069>1DNS​</b069>` | Sweden
  | `</subject>` |
  | `<subject>` |
  | `<b067>96​</b067>` | Thema time period qualifier
  | `<b068>1.3​</b068>` |
  | `<b069>3MPQS​</b069>` | 1960s
  | `</subject>` |
  | `<subject>` |
  | `<x425/>` | Main
  | `<b067>10​</b067>` | BISAC subject heading code
  | `<b068>2017​</b068>` | 2017 version
  | `<b069>FIC022000​</b069>` | Mystery and detective
  | `</subject>` |
  | `<subject>` |
  | `<b067>20​</b067>` | Keywords
  | `<b070>Martin Beck; Roseanna McGraw; Lake Vättern; Stockholm; police procedural​</b070>` |
  | `</subject>` |
  | `<audience>` |
  | `<b204>01​</b204>` | ONIX audience code
  | `<b206>01​</b206>` | General/trade
  | `</audience>` |
  | `<audience>` |
  | `<b204>22​</b204>` | ONIX adult audience rating
  | `<b206>01​</b206>` | Any adult audience
  | `</audience>` |
  | `</descriptivedetail>` | End of Block 1
  | `<collateraldetail>` | Start of Block 2
  | `<textcontent>` |
  | `<x426>02​</x426>` | Short description
  | `<x427>00​</x427>` | Any audience
  | `<d104 textformat="05"><p><strong>Perennial relaunches the first novel in the classic Martin Beck detective series from the 1960s</strong> – the novels that have inspired all crime fiction written ever since.</p>​</d104>` | XHTML markup
  | `</textcontent>` |
  | `<textcontent>` |
  | `<x426>03​</x426>` | (Long) Description
  | `<x427>00​</x427>` | Any audience
  | `<d104 textformat="05"><p>Widely recognized as the among the greatest crime fiction ever written, this is the first of a series of stories that pioneered the police procedural genre. The series was translated into 35 languages, sold over 10 million copies around the world, and inspired writers from Henning Mankell to Jonathan Franzen.</p><p>Written in 1965, <cite>Roseanna</cite> is the work of Maj Sjöwall and Per Wahlöö – a husband and wife team from Sweden, and this volume has a new introduction to help bring their work to a new audience. The novel follows the fortunes of the detective Martin Beck, whose enigmatic and taciturn character has inspired countless other policemen in crime fiction.</p><p><cite>Roseanna</cite> begins on a July afternoon: the body of a young woman is dredged from a canal near Sweden’s beautiful Lake Vättern. Three months later, all that Police Inspector Martin Beck knows is that her name is Roseanna, that she came from Lincoln, Nebraska, and that she could have been strangled by any one of eighty-five people.</p><p>With its authentically rendered settings and vividly realized characters, and its command over the intricately woven details of police detection, <cite>Roseanna</cite> is a masterpiece of suspense and sadness.</p>​</d104>` | Multiple paragraphs
  | `</textcontent>` |
  | `<textcontent>` |
  | `<b034>1​</b034>` | First
  | `<x426>06​</x426>` | Review quote
  | `<x427>00​</x427>` | Any audience
  | `<d104 textformat="05"><p>‘The writing is elegant and surprisingly humorous – if you haven’t come across Beck before, you’re in for a treat.’</p>​</d104>` |
  | `<x428>The Guardian​</x428>` |
  | `</textcontent>` |
  | `<textcontent>` |
  | `<b034>2​</b034>` | Second
  | `<x426>06​</x426>` | Review quote
  | `<x427>00​</x427>` | Any audience
  | `<d104 textformat="05"><p>‘Their mysteries don’t just read well; they reread even better. Witness, wife, petty cop or crook – they’re all real characters even if they get just a few sentences. The plots hold, because they’re ingenious but never inhuman.’</p>​</d104>` |
  | `<x428>New York Times​</x428>` |
  | `</textcontent>` |
  | `<textcontent>` |
  | `<x426>10​</x426>` | Promotional headline
  | `<x427>00​</x427>` | Any audience
  | `<d104>One of the greatest masterpieces of crime fiction​</d104>` |
  | `</textcontent>` |
  | `<citedcontent>` |
  | `<x430>03​</x430>` | Media mention (feature article)
  | `<x427>00​</x427>` | Any audience
  | `<x431>01​</x431>` | Printed media
  | `<x428>Observer Magazine​</x428>` |
  | `<x434>Interview with Maj Sjöwall by Louise France​</x434>` |
  | `<x435>https://www.​guardian.​co.​uk/​books/​2009/​nov/​22/​crime-​thriller-​maj-​sjowall-​sweden​</x435>` | URL
  | `<contentdate>` |
  | `<x429>01​</x429>` | Publication date (of article)
  | `<b306 dateformat="00">20091122​</b306>` |
  | `</contentdate>` |
  | `</citedcontent>` |
  | `<supportingresource>` |
  | `<x436>01​</x436>` | Front cover
  | `<x427>00​</x427>` | All audiences
  | `<x437>03​</x437>` | Image
  | `<resourceversion>` |
  | `<x441>02​</x441>` | Downloadable
  | `<resourceversionfeature>` |
  | `<x442>01​</x442>` | File format
  | `<x439>D502​</x439>` | JPEG
  | `</resourceversionfeature>` |
  | `<resourceversionfeature>` |
  | `<x442>02​</x442>` | Image height
  | `<x439>341​</x439>` | in pixels
  | `</resourceversionfeature>` |
  | `<resourceversionfeature>` |
  | `<x442>03​</x442>` | Image width
  | `<x439>222​</x439>` | in pixels
  | `</resourceversionfeature>` |
  | `<x435>https://www.harpercollins.​co.​uk/​covers/​9780007232833.​jpg​</x435>` | URL
  | `<contentdate>` |
  | `<x429>17​</x429>` | Last updated
  | `<b306 dateformat="00">20060412​</b306>` |
  | `</contentdate>` |
  | `</resourceversion>` |
  | `</supportingresource>` |
  | `<supportingresource>` |
  | `<x436>15​</x436>` | Sample content
  | `<x427>00​</x427>` | All audiences
  | `<x437>06​</x437>` | Multi-mode (a web page)
  | `<resourceversion>` |
  | `<x441>01​</x441>` | Linkable resource
  | `<x435>https://browseinside.​harpercollins.​co.​uk/​pageview?​isbn=​9780007232833​</x435>` | URL
  | `</resourceversion>` |
  | `</supportingresource>` |
  | `</collateraldetail>` | End of Block 2
  | `<!-- there is no Block 3 or Block 7 -->` |
  | `<publishingdetail>` | Start of Block 4
  | `<imprint>` |
  | `<b079>HarperPerennial​</b079>` |
  | `</imprint>` |
  | `<publisher>` |
  | `<b291>01​</b291>` | Publisher
  | `<publisheridentifier>` |
  | `<x447>16</x447>` | ISNI
  | `<b244>0000000404222532</b244>` |
  | `</publisheridentifier>` |
  | `<b081>HarperCollins Publishers​</b081>` |
  | `<website>` |
  | `<b367>01</b367>` | Corporate website
  | `<b295>https://​www.harpercollins.co.uk​</b295>` |
  | `</website>` |
  | `</publisher>` |
  | `<b209>London​</b209>` |
  | `<b083>GB​</b083>` |
  | `<b394 datestamp="20100508">04​</b394>` | Active
  | `<publishingdate>` |
  | `<x448>01​</x448>` | Date of publication (of product)
  | `<b306 dateformat="00">20060807​</b306>` | dateformat=YYYYMMDD
  | `</publishingdate>` |
  | `<publishingdate>` |
  | `<x448>11​</x448>` | Date of first publication (of work)
  | `<b306 dateformat="05">1968​</b306>` | dateformat=YYYY
  | `</publishingdate>` |
  | `<publishingdate>` |
  | `<x448>20​</x448>` | Pub date in original language
  | `<b306 dateformat="05">1965​</b306>` | dateformat=YYYY
  | `</publishingdate>` |
  | `<copyrightstatement>` |
  | `<x512>C</x512>` | Text copyright
  | `<b087>1965</b087>` | dateformat=default (YYYY)
  | `<copyrightowner>` |
  | `<b036>Maj Sjöwall</b036>` | Joint rightsholders
  | `</copyrightowner>` |
  | `<copyrightowner>` |
  | `<b036>Per Wahlöö</b036>` |
  | `</copyrightowner>` |
  | `</copyrightstatement>` |
  | `<x588>© Maj Sjöwall and Per Wahlöö 1965</x588>` |
  | `<salesrights>` |
  | `<b089>01​</b089>` | For sale (publisher has exclusive rights in territory)
  | `<territory>` |
  | `<x449>AG AI AU BB BD BM BN BS BW BZ CM CY DM EG FJ FK GB GD GG GH GI GM GY HK IE IL IM IN IO JE JM JO KE KI KN KW KY LC LK LS MT MU MV MW MY MZ NA NG NR NZ PG PK PN SB SC SD SG SH SL SO SZ TC TO TT TV TZ UG VC VG VU WS YE RS ME ZA ZM ZW​</x449>` | Broadly, this is ‘Commonwealth excluding Canada’
  | `</territory>` |
  | `</salesrights>` |
  | `<salesrights>` |
  | `<b089>06​</b089>` | Not for sale (publisher has no rights in territory)
  | `<territory>` |
  | `<x449>AS CA GU MP PH PR US VI​</x449>` | Broadly, the ‘US Market’ and Canada
  | `</territory>` |
  | `</salesrights>` |
  | `<salesrights>` |
  | `<salesrightstype>02​</salesrightstype>` | For sale (publisher has non-exclusive rights in rest of world)
  | `<territory>` |
  | `<x450>WORLD​</x450>` | Everywhere…
  | `<x451>AG AI AU BB BD BM BN BS BW BZ CM CY DM EG FJ FK GB GD GG GH GI GM GY HK IE IL IM IN IO JE JM JO KE KI KN KW KY LC LK LS MT MU MV MW MY MZ NA NG NR NZ PG PK PN SB SC SD SG SH SL SO SZ TC TO TT TV TZ UG VC VG VU WS YE RS ME ZA ZM ZW AS CA GU MP PH PR US VI​</x451>` | other than the countries where rights type is 01 or 06
  | `</territory>` |
  | `</salesrights>` |
  | `<!-- no ROW sales rights type needed -->` |
  | `</publishingdetail>` | End of Block 4
  | `<relatedmaterial>` | Start of Block 5
  | `<relatedwork>` |
  | `<x454>01​</x454>` | Is manifestation of
  | `<workidentifier>` |
  | `<b201>11​</b201>` | (former) ISTC
  | `<b244>A0220090000154FA​</b244>` |
  | `</workidentifier>` |
  | `</relatedwork>` |
  | `<relatedproduct>` |
  | `<x455>06​</x455>` | Alternative format
  | `<x455>27​</x455>` | E-version
  | `<productidentifier>` |
  | `<b221>03​</b221>` | GTIN-13
  | `<b244>9780007324378​</b244>` |
  | `</productidentifier>` |
  | `<productidentifier>` |
  | `<b221>15​</b221>` | ISBN
  | `<b244>9780007324378​</b244>` |
  | `</productidentifier>` |
  | `</relatedproduct>` |
  | `</relatedmaterial>` | End of Block 5
  | `<!-- there is no Block 8 -->` |
  | `<productsupply>` | Start of Block 6
  | `<x587>NAAU3</x587>` | Label market as ‘NAAU3’
  | `<market>` |
  | `<territory>` |
  | `<x450>WORLD​</x450>` | Market is world…
  | `<x451>AS AU CA GU MP NZ PH PR US VI ZA​</x451>` | …minus countries with no rights and three countries with separate exclusive distributorships (the latter could additionally be represented by separate <ProductSupply> sections)
  | `</territory>` |
  | `</market>` |
  | `<marketpublishingdetail>` |
  | `<j407>04​</j407>` | Active
  | `<marketdate>` |
  | `<j408>01​</j408>` | Pub date in this market
  | `<b306 dateformat="00">20060807​</b306>` | dateformat=YYYYMMDD
  | `</marketdate>` |
  | `</marketpublishingdetail>` |
  | `<supplydetail>` |
  | `<supplier>` |
  | `<j292>01​</j292>` | Publisher supplying to retailers
  | `<supplieridentifier>` |
  | `<j345>06​</j345>` | GLN for orders
  | `<b244>5051366000000​</b244>` |
  | `</supplieridentifier>` |
  | `<supplieridentifier>` |
  | `<j345>07​</j345>` | SAN for orders
  | `<b244>0091073​</b244>` |
  | `</supplieridentifier>` |
  | `<j137>HarperCollins Publishers​</j137>` |
  | `<j270>+44 1417 723200​</j270>` |
  | `</supplier>` |
  | `<returnsconditions>` |
  | `<j268>04​</j268>` | ONIX returns indicator
  | `<j269>03​</j269>` | Sale or return
  | `</returnsconditions>` |
  | `<j396 datestamp="20100507">21​</j396>` | In stock
  | `<j145>16​</j145>` | 16 copies in a carton
  | `<price>` | Price 1 for UK
  | `<x462>02​</x462>` | RRP including tax
  | `<discountcoded>` |
  | `<j363>01​</j363>` | BIC discount group code
  | `<j364>AHACP029​</j364>` | HCP discount group 29
  | `</discountcoded>` |
  | `<j266>02​</j266>` | Firm price
  | `<j151>7.99​</j151>` |
  | `<tax>` |
  | `<x470>01​</x470>` | VAT
  | `<x471>Z​</x471>` | Zero-rated
  | `<x472>0</x472>` | 0%
  | `<x473>7.99​</x473>` |
  | `<x474>0.00</x474>` |
  | `</tax>` |
  | `<j152>GBP​</j152>` | Pounds Sterling
  | `<territory>` | Price applicable to…
  | `<x449>GB​</x449>` |
  | `</territory>` |
  | `<x301>02​</x301>` | Price on product
  | `<x313>01​</x313>` | On outside back cover
  | `</price>` |
  | `<price>` | Price 2 for Eurozone
  | `<x462>01​</x462>` | RRP excluding tax
  | `<discount>` |
  | `<j267>37.5​</j267>` | 37.5% discount
  | `</discount>` |
  | `<j266>02​</j266>` | Firm price
  | `<j151>8.99​</j151>` |
  | `<j152>EUR​</j152>` | Euro
  | `<territory>` | Price applicable to…
  | `<x449>AT BE CY FI FR DE ES GR IE IT LU MT NL PT SI SK AD MC ME SM VA​</x449>` | Euro-using countries in Europe
  | `</territory>` |
  | `<x301>01​</x301>` | Price not on product
  | `</price>` |
  | `<price>` | Price 3 for remainder of market
  | `<x462>01​</x462>` | RRP excluding tax
  | `<discount>` |
  | `<j267>42.5​</j267>` | 42.5% discount
  | `</discount>` |
  | `<j266>02​</j266>` | Firm price
  | `<j151>7.99​</j151>` |
  | `<j152>GBP​</j152>` | Pounds Sterling
  | `<territory>` | Price applicable to…
  | `<x450>WORLD​</x450>` | Remainder of market, ie world…
  | `<x451>GB AT BE CY FI FR DE ES GR IE IT LU MT NL PT SI SK AD MC ME SM VA AS AU CA GU MP NZ PH PR US VI ZA​</x451>` | …minus GB, Euro-using countries in Europe and countries without sales rights
  | `</territory>` |
  | `<x301>01​</x301>` | Price not on product
  | `</price>` |
  | `</supplydetail>` |
  | `</productsupply>` | End of Block 6
  | `<!-- aggregator could add other ProductSupply sections here, for AU/NZ and ZA distributors -->` |
  | `</product>` |
  | `</ONIXmessage>` |

  sample block update message
  # | using Reference names | Commentary
  --- | --- | ---
  | `<?xml version="1.0" encoding="UTF-8"?>` |
  | `<ONIXMessage release="3.1" xmlns="http://ns.editeur.org/​onix/​3.1/​reference">` | Upper case M, mandatory release attribute
  | `<Header>` |
  | `<Sender>` |
  | `<SenderName>Global Bookinfo​</SenderName>` | Same fictitious aggregator…
  | `<ContactName>Jane King​</ContactName>` |
  | `<TelephoneNumber>+1 212 555 0123​</TelephoneNumber>` |
  | `<EmailAddress>jbk@globalbookinfo.com​</EmailAddress>` |
  | `</Sender>` |
  | `<Addressee>` |
  | `<AddresseeName>BooksBooksBooks.com​</AddresseeName>` | …to same fictitious bookseller
  | `</Addressee>` |
  | `<MessageNumber>332​</MessageNumber>` |
  | `<SentDateTime>20140911T0905-0400​</SentDateTime>` | 11 Sept 2014, 9:05am EDT (1:05pm UTC)
  | `<MessageNote>Sample block update message​</MessageNote>` |
  | `</Header>` |
  | `<!-- product record 1 of 1 in message -->` |
  | `<Product>` | Start of Product record
  | `<!-- ‘block zero’ is always required -->` |
  | `<RecordReference>com.globalbookinfo.​onix.​01734529​</RecordReference>` | Matching record reference identifies record to be updated
  | `<NotificationType>04​</NotificationType>` | Block update
  | `<RecordSourceType>04​</RecordSourceType>` |
  | `<RecordSourceIdentifier>` |
  | `<RecordSourceIDType>06​</RecordSourceIDType>` | GLN
  | `<IDValue>0614141800001​</IDValue>` |
  | `</RecordSourceIdentifier>` |
  | `<RecordSourceName>Global Bookinfo​</RecordSourceName>` |
  | `<ProductIdentifier>` |
  | `<ProductIDType>03​</ProductIDType>` | ISBN as GTIN-13
  | `<IDValue>9780007232833​</IDValue>` |
  | `</ProductIdentifier>` |
  | `<ProductIdentifier>` |
  | `<ProductIDType>15​</ProductIDType>` | Explicitly an ISBN
  | `<IDValue>9780007232833​</IDValue>` |
  | `</ProductIdentifier>` |
  | `<!-- There are no blocks 1–5, 7 or 8 -->` |
  | `<ProductSupply>` | Start of replacement Block 6
  | `<MarketReference>NAAU3</MarketReference>` | Only replacing ‘NAAU3’ market, other <ProductSupply> repeats remain unaffected
  | `<Market>` |
  | `<Territory>` |
  | `<RegionsIncluded>WORLD​</RegionsIncluded>` |
  | `<CountriesExcluded>AS AU CA GU MP NZ PH PR US VI ZA​</CountriesExcluded>` |
  | `</Territory>` |
  | `</Market>` |
  | `<MarketPublishingDetail>` |
  | `<MarketPublishingStatus>04​</MarketPublishingStatus>` | Still active
  | `<MarketDate>` |
  | `<MarketDateRole>01​</MarketDateRole>` | Pub date in this market
  | `<Date dateformat="00">20060807​</Date>` |
  | `</MarketDate>` |
  | `</MarketPublishingDetail>` |
  | `<SupplyDetail>` |
  | `<Supplier>` |
  | `<SupplierRole>01​</SupplierRole>` |
  | `<SupplierIdentifier>` |
  | `<SupplierIDType>06​</SupplierIDType>` | GLN for orders
  | `<IDValue>5051366000000​</IDValue>` |
  | `</SupplierIdentifier>` |
  | `<SupplierIdentifier>` |
  | `<SupplierIDType>07​</SupplierIDType>` | SAN for orders
  | `<IDValue>0091073​</IDValue>` |
  | `</SupplierIdentifier>` |
  | `<SupplierName>HarperCollins Publishers​</SupplierName>` |
  | `<TelephoneNumber>+44 1417 723200​</TelephoneNumber>` |
  | `</Supplier>` |
  | `<ReturnsConditions>` |
  | `<ReturnsCodeType>04​</ReturnsCodeType>` |
  | `<ReturnsCode>03​</ReturnsCode>` |
  | `</ReturnsConditions>` |
  | `<ProductAvailability datestamp="20100507">21​</ProductAvailability>` | Still in stock
  | `<PackQuantity>16​</PackQuantity>` |
  | `<Price>` | Replacement price 1 for UK
  | `<PriceType>02​</PriceType>` | RRP including tax
  | `<DiscountCoded>` |
  | `<DiscountCodeType>01​</DiscountCodeType>` | BIC discount group code
  | `<DiscountCode>AHACP029​</DiscountCode>` | HCP discount group 29
  | `</DiscountCoded>` |
  | `<PriceStatus>02​</PriceStatus>` | Firm price
  | `<PriceAmount>8.99​</PriceAmount>` | Price raised by £1.00
  | `<Tax>` |
  | `<TaxType>01​</TaxType>` | VAT
  | `<TaxRateCode>Z​</TaxRateCode>` | Zero-rated
  | `<TaxRatePercent>0</TaxRatePercent>` | 0%
  | `<TaxableAmount>8.99​</TaxableAmount>` |
  | `<TaxAmount>0.00</TaxAmount>` |
  | `</Tax>` |
  | `<CurrencyCode>GBP​</CurrencyCode>` | Pounds Sterling
  | `<Territory>` | Price applicable to…
  | `<CountriesIncluded>GB​</CountriesIncluded>` |
  | `</Territory>` |
  | `<PrintedOnProduct>02​</PrintedOnProduct>` | Price on product
  | `<PositionOnProduct>01​</PositionOnProduct>` | On outside back cover
  | `</Price>` |
  | `<Price>` | Replacement price 2 for Eurozone
  | `<PriceType>01​</PriceType>` | RRP excluding tax
  | `<Discount>` |
  | `<DiscountPercent>37.5​</DiscountPercent>` | 37.5% discount
  | `</Discount>` |
  | `<PriceStatus>02​</PriceStatus>` | Firm price
  | `<PriceAmount>9.99​</PriceAmount>` | Price raised by €1.00
  | `<CurrencyCode>EUR​</CurrencyCode>` | Euro
  | `<Territory>` | Price applicable to…
  | `<CountriesIncluded>AT BE CY FI FR DE ES GR IE IT LU MT NL PT SI SK AD MC ME SM VA​</CountriesIncluded>` | Euro-using countries in Europe
  | `</Territory>` |
  | `<PrintedOnProduct>01​</PrintedOnProduct>` | Price not on product
  | `</Price>` |
  | `<Price>` | Replacement price 3 for remainder of market
  | `<PriceType>01​</PriceType>` | RRP excluding tax
  | `<Discount>` |
  | `<DiscountPercent>42.5​</DiscountPercent>` | 42.5% discount
  | `</Discount>` |
  | `<PriceStatus>02​</PriceStatus>` | Firm price
  | `<PriceAmount>8.99​</PriceAmount>` | Price raised by £1.00
  | `<CurrencyCode>GBP​</CurrencyCode>` | Pounds Sterling
  | `<Territory>` | Price applicable to…
  | `<RegionsIncluded>WORLD​</RegionsIncluded>` | Remainder of market, ie world…
  | `<CountriesExcluded>GB AT BE CY FI FR DE ES GR IE IT LU MT NL PT SI SK AD MC ME SM VA AS AU CA GU MP NZ PH PR US VI ZA​</CountriesExcluded>` | …minus GB, Euro-using countries in Europe and countries without sales rights
  | `</Territory>` |
  | `<PrintedOnProduct>01​</PrintedOnProduct>` | Price not on product
  | `</Price>` |
  | `</SupplyDetail>` |
  | `</ProductSupply>` | End of Block 6
  | `</Product>` |
  | `</ONIXMessage>` |

  # | using Short tags | Commentary
  --- | --- | ---
  | `<?xml version="1.0" encoding="UTF-8"?>` |
  | `<ONIXmessage release="3.1" xmlns="http://ns.editeur.org/​onix/​3.1/​short">` | Lower case m, mandatory release attribute
  | `<header>` |
  | `<sender>` |
  | `<x298>Global Bookinfo​</x298>` | Same fictitious aggregator…
  | `<x299>Jane King​</x299>` |
  | `<j270>+1 212 555 0123​</j270>` |
  | `<j272>jbk@globalbookinfo.com​</j272>` |
  | `</sender>` |
  | `<addressee>` |
  | `<x300>BooksBooksBooks.com​</x300>` | …to same fictitious bookseller
  | `</addressee>` |
  | `<m180>231​</m180>` |
  | `<x307>20140911T0905-0400​</x307>` | 11 Sept 2014, 9:05am EDT (1:05pm UTC)
  | `<m183>Sample block update message​</m183>` |
  | `</header>` |
  | `<!-- product record 1 of 1 in message -->` |
  | `<product>` | Start of Product record
  | `<!-- ‘block zero’ is always required -->` |
  | `<a001>com.globalbookinfo.​onix.​01734529​</a001>` | Matching record reference identifies record to be updated
  | `<a002>04​</a002>` | Block update
  | `<a194>04​</a194>` |
  | `<recordsourceidentifier>` |
  | `<x311>06​</x311>` | GLN
  | `<b244>0614141800001​</b244>` |
  | `</recordsourceidentifier>` |
  | `<a197>Global Bookinfo​</a197>` |
  | `<productidentifier>` |
  | `<b221>03​</b221>` | ISBN as GTIN-13
  | `<b244>9780007232833​</b244>` |
  | `</productidentifier>` |
  | `<productidentifier>` |
  | `<b221>15​</b221>` | Explicitly an ISBN
  | `<b244>9780007232833​</b244>` |
  | `</productidentifier>` |
  | `<!-- There are no blocks 1–5, 7 or 8 -->` |
  | `<productsupply>` | Start of replacement Block 6
  | `<x587>NAAU3</x587>` | Only replacing ‘NAAU3’ market, other <productsupply> repeats remain unaffected
  | `<market>` |
  | `<territory>` |
  | `<x450>WORLD​</x450>` |
  | `<x451>AS AU CA GU MP NZ PH PR US VI ZA​</x451>` |
  | `</territory>` |
  | `</market>` |
  | `<marketpublishingdetail>` |
  | `<j407>04​</j407>` | Still active
  | `<marketdate>` |
  | `<j408>01​</j408>` | Pub date in this market
  | `<b306 dateformat="00">20060807​</b306>` |
  | `</marketdate>` |
  | `</marketpublishingdetail>` |
  | `<supplydetail>` |
  | `<supplier>` |
  | `<j292>01​</j292>` |
  | `<supplieridentifier>` |
  | `<j345>06​</j345>` | GLN for orders
  | `<b244>5051366000000​</b244>` |
  | `</supplieridentifier>` |
  | `<supplieridentifier>` |
  | `<j345>07​</j345>` | SAN for orders
  | `<b244>0091073​</b244>` |
  | `</supplieridentifier>` |
  | `<j137>HarperCollins Publishers​</j137>` |
  | `<j270>+44 1417 723200​</j270>` |
  | `</supplier>` |
  | `<returnsconditions>` |
  | `<j268>04​</j268>` |
  | `<j269>03​</j269>` |
  | `</returnsconditions>` |
  | `<j396 datestamp="20100507">21​</j396>` | Still in stock
  | `<j145>16​</j145>` |
  | `<price>` | Replacement price 1 for UK
  | `<x462>02​</x462>` | RRP including tax
  | `<discountcoded>` |
  | `<j363>01​</j363>` | BIC discount group code
  | `<j364>AHACP029​</j364>` | HCP discount group 29
  | `</discountcoded>` |
  | `<j266>02​</j266>` | Firm price
  | `<j151>8.99​</j151>` | Price raised by £1.00
  | `<tax>` |
  | `<x470>01​</x470>` | VAT
  | `<x471>Z​</x471>` | Zero-rated
  | `<x472>0</x472>` | 0%
  | `<x473>8.99​</x473>` |
  | `<x474>0.00</x474>` |
  | `</tax>` |
  | `<j152>GBP​</j152>` | Pounds Sterling
  | `<territory>` | Price applicable to…
  | `<x449>GB​</x449>` |
  | `</territory>` |
  | `<x301>02​</x301>` | Price on product
  | `<x313>01​</x313>` | On outside back cover
  | `</price>` |
  | `<price>` | Replacement price 2 for Eurozone
  | `<x462>01​</x462>` | RRP excluding tax
  | `<discount>` |
  | `<j267>37.5​</j267>` | 37.5% discount
  | `</discount>` |
  | `<j266>02​</j266>` | Firm price
  | `<j151>9.99​</j151>` | Price raised by €1.00
  | `<j152>EUR​</j152>` | Euro
  | `<territory>` | Price applicable to…
  | `<x449>AT BE CY FI FR DE ES GR IE IT LU MT NL PT SI SK AD MC ME SM VA​</x449>` | Euro-using countries in Europe
  | `</territory>` |
  | `<x301>01​</x301>` | Price not on product
  | `</price>` |
  | `<price>` | Replacement price 3 for remainder of market
  | `<x462>01​</x462>` | RRP excluding tax
  | `<discount>` |
  | `<j267>42.5​</j267>` | 42.5% discount
  | `</discount>` |
  | `<j266>02​</j266>` | Firm price
  | `<j151>8.99​</j151>` | Price raised by £1.00
  | `<j152>GBP​</j152>` | Pounds Sterling
  | `<territory>` | Price applicable to…
  | `<x450>WORLD​</x450>` | Remainder of market, ie world…
  | `<x451>GB AT BE CY FI FR DE ES GR IE IT LU MT NL PT SI SK AD MC ME SM VA AS AU CA GU MP NZ PH PR US VI ZA​</x451>` | …minus GB, Euro-using countries in Europe and countries without sales rights
  | `</territory>` |
  | `<x301>01​</x301>` | Price not on product
  | `</price>` |
  | `</supplydetail>` |
  | `</productsupply>` | End of Block 6
  | `</product>` |
  | `</ONIXmessage>` |

#### A.3 List of all ONIX for Books Release 3.1 XML tags

The tables show equivalent Reference names and Short tags, first in Reference name order, then in Short tag order. Note that in any one ONIX message, Reference names and Short tags cannot be mixed.

Around 20 tags marked ‘New in 3.0’ were merely renamed from very similar tags in earlier releases of ONIX, for reasons of consistency or to highlight minor changes in meaning – for example <SentDateTime> was previously <SentDate> and <PersonNameIdentifier> is now <NameIdentifier>. Tags present in Release 3.0 but removed from 3.1 are not shown in the table.

  complete list of tag names
  Reference name | equivalent Short tag | Notes
  --- | --- | ---
  `Addressee` | `addressee` |
  `AddresseeIdentifier` | `addresseeidentifier` |
  `AddresseeIDType` | `m380` |
  `AddresseeName` | `x300` |
  `Affiliation` | `b046` |
  `AffiliationIdentifier` | `affiliationidentifier` |
  `AffiliationIDType` | `x580` |
  `AgentIdentifier` | `agentidentifier` |
  `AgentIDType` | `j400` |
  `AgentName` | `j401` |
  `AgentRole` | `j402` |
  `AlternativeName` | `alternativename` |
  `AncillaryContent` | `ancillarycontent` |
  `AncillaryContentDescription` | `x424` |
  `AncillaryContentType` | `x423` |
  `Audience` | `audience` |
  `AudienceCodeType` | `b204` |
  `AudienceCodeTypeName` | `b205` |
  `AudienceCodeValue` | `b206` |
  `AudienceDescription` | `b207` |
  `AudienceHeadingText` | `x578` |
  `AudienceRange` | `audiencerange` |
  `AudienceRangePrecision` | `b075` |
  `AudienceRangeQualifier` | `b074` |
  `AudienceRangeValue` | `b076` |
  `AVDuration` | `x544` |
  `AVItem` | `avitem` |
  `AVItemIdentifier` | `avitemidentifier` |
  `AVItemIDType` | `x541` |
  `AVItemType` | `x540` |
  `AwardingBody` | `x584` |
  `Barcode` | `barcode` |
  `BarcodeType` | `x312` |
  `BatchBonus` | `batchbonus` |
  `BatchQuantity` | `j264` |
  `Bible` | `bible` |
  `BibleContents` | `b352` |
  `BiblePurpose` | `b354` |
  `BibleReferenceLocation` | `b356` |
  `BibleTextFeature` | `b357` |
  `BibleTextOrganization` | `b355` |
  `BibleVersion` | `b353` |
  `BiographicalNote` | `b044` |
  `BodyManifest` | `bodymanifest` |
  `BodyResource` | `bodyresource` |
  `BookClubAdoption` | `k169` |
  `CBO` | `j375` |
  `CitationNote` | `x434` |
  `CitedContent` | `citedcontent` |
  `CitedContentType` | `x430` |
  `CityOfPublication` | `b209` |
  `CollateralDetail` | `collateraldetail` |
  `Collection` | `collection` |
  `CollectionElementLevel` | `x586` |
  `CollectionFrequency` | `x582` |
  `CollectionIdentifier` | `collectionidentifier` |
  `CollectionIDType` | `x344` |
  `CollectionSequence` | `collectionsequence` |
  `CollectionSequenceNumber` | `x481` |
  `CollectionSequenceType` | `x479` |
  `CollectionSequenceTypeName` | `x480` |
  `CollectionType` | `x329` |
  `ComparisonProductPrice` | `comparisonproductprice` |
  `Complexity` | `complexity` |
  `ComplexityCode` | `b078` |
  `ComplexitySchemeIdentifier` | `b077` |
  `ComponentNumber` | `b289` |
  `ComponentTypeName` | `b288` |
  `ContactName` | `x299` |
  `ContentAudience` | `x427` |
  `ContentDate` | `contentdate` |
  `ContentDateRole` | `x429` |
  `ContentDetail` | `contentdetail` |
  `ContentItem` | `contentitem` |
  `Contributor` | `contributor` |
  `ContributorDate` | `contributordate` |
  `ContributorDateRole` | `x417` |
  `ContributorDescription` | `b048` |
  `ContributorPlace` | `contributorplace` |
  `ContributorPlaceRelator` | `x418` |
  `ContributorReference` | `contributorreference` |
  `ContributorRole` | `b035` |
  `ContributorStatement` | `b049` |
  `CopiesSold` | `k168` |
  `CopyrightOwner` | `copyrightowner` |
  `CopyrightOwnerIdentifier` | `copyrightowneridentifier` |
  `CopyrightOwnerIDType` | `b392` |
  `CopyrightStatement` | `copyrightstatement` |
  `CopyrightStatementText` | `x588` |
  `CopyrightType` | `x512` |
  `CopyrightYear` | `b087` |
  `CorporateName` | `b047` |
  `CorporateNameInverted` | `x443` |
  `CountriesExcluded` | `x451` |
  `CountriesIncluded` | `x449` |
  `CountryCode` | `b251` |
  `CountryOfManufacture` | `x316` |
  `CountryOfPublication` | `b083` |
  `CoverManifest` | `covermanifest` |
  `CoverResource` | `coverresource` |
  `CurrencyCode` | `j152` |
  `Date` | `b306` |
  `DefaultCurrencyCode` | `m186` |
  `DefaultLanguageOfText` | `m184` |
  `DefaultPriceType` | `x310` |
  `DeletionText` | `a199` |
  `DescriptiveDetail` | `descriptivedetail` |
  `Discount` | `discount` |
  `DiscountAmount` | `x469` |
  `DiscountCode` | `j364` |
  `DiscountCoded` | `discountcoded` |
  `DiscountCodeType` | `j363` |
  `DiscountCodeTypeName` | `j378` |
  `DiscountPercent` | `j267` |
  `DiscountType` | `x467` |
  `EditionNumber` | `b057` |
  `EditionStatement` | `b058` |
  `EditionType` | `x419` |
  `EditionVersionNumber` | `b217` |
  `EmailAddress` | `j272` |
  `EndDate` | `b325` |
  `EndTime` | `x543` |
  `EpubLicense` | `epublicense` |
  `EpubLicenseDate` | `epublicensedate` |
  `EpubLicenseDateRole` | `x585` |
  `EpubLicenseExpression` | `epublicenseexpression` |
  `EpubLicenseExpressionType` | `x508` |
  `EpubLicenseExpressionTypeName` | `x509` |
  `EpubLicenseExpressionLink` | `x510` |
  `EpubLicenseName` | `x511` |
  `EpubTechnicalProtection` | `x317` |
  `EpubUsageConstraint` | `epubusageconstraint` |
  `EpubUsageLimit` | `epubusagelimit` |
  `EpubUsageStatus` | `x319` |
  `EpubUsageType` | `x318` |
  `EpubUsageUnit` | `x321` |
  `Event` | `event` |
  `EventAcronym` | `x517` |
  `EventDate` | `x520` |
  `EventDescription` | `x550` |
  `EventIdentifier` | `eventidentifier` |
  `EventIDType` | `x547` |
  `EventName` | `x516` |
  `EventNumber` | `x518` |
  `EventOccurrence` | `eventoccurrence` |
  `EventPlace` | `x521` |
  `EventRole` | `x515` |
  `EventSponsor` | `eventsponsor` |
  `EventSponsorIdentifier` | `eventsponsoridentifier` |
  `EventSponsorIDType` | `x522` |
  `EventStatus` | `x549` |
  `EventTheme` | `x519` |
  `EventType` | `x548` |
  `ExpectedDate` | `j302` |
  `Extent` | `extent` |
  `ExtentType` | `b218` |
  `ExtentUnit` | `b220` |
  `ExtentValue` | `b219` |
  `ExtentValueRoman` | `x421` |
  `FaxNumber` | `j271` |
  `FeatureNote` | `x440` |
  `FeatureValue` | `x439` |
  `FirstPageNumber` | `b286` |
  `FreeQuantity` | `j265` |
  `FromLanguage` | `x412` |
  `Funding` | `funding` |
  `FundingIdentifier` | `fundingidentifier` |
  `FundingIDType` | `x523` |
  `Header` | `header` |
  `IDTypeName` | `b233` |
  `IDValue` | `b244` |
  `Illustrated` | `x422` |
  `IllustrationsNote` | `b062` |
  `Imprint` | `imprint` |
  `ImprintIdentifier` | `imprintidentifier` |
  `ImprintIDType` | `x445` |
  `ImprintName` | `b079` |
  `InitialPrintRun` | `k167` |
  `InsertManifest` | `insertmanifest` |
  `InsertPoint` | `insertpoint` |
  `InsertPointType` | `x574` |
  `InsertPointValue` | `x575` |
  `InsertResource` | `insertresource` |
  `KeyNames` | `b040` |
  `Language` | `language` |
  `LanguageCode` | `b252` |
  `LanguageRole` | `b253` |
  `LastPageNumber` | `b287` |
  `LatestReprintNumber` | `x446` |
  `LettersAfterNames` | `b042` |
  `LevelSequenceNumber` | `b284` |
  `ListName` | `x432` |
  `LocationIdentifier` | `locationidentifier` |
  `LocationIDType` | `j377` |
  `LocationName` | `j349` |
  `MainAudience/` | `x583/` |
  `MainSubject/` | `x425/` |
  `MapScale` | `b063` |
  `Market` | `market` |
  `MarketDate` | `marketdate` |
  `MarketDateRole` | `j408` |
  `MarketPublishingDetail` | `marketpublishingdetail` |
  `MarketPublishingStatus` | `j407` |
  `MarketPublishingStatusNote` | `x406` |
  `MarketReference` | `x587` |
  `Measure` | `measure` |
  `Measurement` | `c094` |
  `MeasureType` | `x315` |
  `MeasureUnitCode` | `c095` |
  `MessageNote` | `m183` |
  `MessageNumber` | `m180` |
  `MessageRepeat` | `m181` |
  `MinimumOrderQuantity` | `j263` |
  `NameAsSubject` | `nameassubject` |
  `NameIdentifier` | `nameidentifier` |
  `NameIDType` | `x415` |
  `NamesAfterKey` | `b041` |
  `NamesBeforeKey` | `b039` |
  `NameType` | `x414` |
  `NewSupplier` | `newsupplier` |
  `NoCollection/` | `x411/` |
  `NoContributor/` | `n339/` |
  `NoEdition/` | `n386/` |
  `NoPrefix/` | `x501/` |
  `NoProduct/` | `x507/` |
  `NoResource/` | `x577/` |
  `NoSupplement/` | `x579/` |
  `NotificationType` | `a002` |
  `Number` | `b257` |
  `NumberOfCopies` | `x323` |
  `NumberOfIllustrations` | `b125` |
  `NumberOfItemsOfThisForm` | `x322` |
  `NumberOfPages` | `b061` |
  `OccurrenceDate` | `occurrencedate` |
  `OccurrenceDateRole` | `x554` |
  `OnHand` | `j350` |
  `ONIXMessage` | `ONIXmessage` |
  `OnOrder` | `j351` |
  `OnOrderDetail` | `onorderdetail` |
  `OrderQuantityMinimum` | `x532` |
  `OrderQuantityMultiple` | `x533` |
  `OrderTime` | `j144` |
  `PackQuantity` | `j145` |
  `PalletQuantity` | `x545` |
  `PageRun` | `pagerun` |
  `PartNumber` | `x410` |
  `Percent` | `b337` |
  `PersonName` | `b036` |
  `PersonNameInverted` | `b037` |
  `PositionOnList` | `x433` |
  `PositionOnProduct` | `x313` |
  `PostalCode` | `x590` |
  `PrefixToKey` | `b247` |
  `Price` | `price` |
  `PriceAmount` | `j151` |
  `PriceCode` | `x468` |
  `PriceCoded` | `pricecoded` |
  `PriceCodeType` | `x465` |
  `PriceCodeTypeName` | `x477` |
  `PriceCondition` | `pricecondition` |
  `PriceConditionQuantity` | `priceconditionquantity` |
  `PriceConditionQuantityType` | `x464` |
  `PriceConditionType` | `x463` |
  `PriceConstraint` | `priceconstraint` |
  `PriceConstraintLimit` | `priceconstraintlimit` |
  `PriceConstraintStatus` | `x530` |
  `PriceConstraintType` | `x529` |
  `PriceConstraintUnit` | `x531` |
  `PriceDate` | `pricedate` |
  `PriceDateRole` | `x476` |
  `PriceIdentifier` | `priceidentifier` |
  `PriceIDType` | `x506` |
  `PricePartDescription` | `x535` |
  `PricePer` | `j239` |
  `PriceQualifier` | `j261` |
  `PriceStatus` | `j266` |
  `PriceType` | `x462` |
  `PriceTypeDescription` | `j262` |
  `PrimaryContentType` | `x416` |
  `PrimaryPart/` | `x457/` |
  `PrintedOnProduct` | `x301` |
  `Prize` | `prize` |
  `PrizeCode` | `g129` |
  `PrizeCountry` | `g128` |
  `PrizeIdentifier` | `prizeidentifier` |
  `PrizeIDType` | `x589` |
  `PrizeJury` | `g343` |
  `PrizeName` | `g126` |
  `PrizeRegion` | `x556` |
  `PrizeStatement` | `x503` |
  `PrizeYear` | `g127` |
  `Product` | `product` |
  `ProductAvailability` | `j396` |
  `ProductClassification` | `productclassification` |
  `ProductClassificationCode` | `b275` |
  `ProductClassificationType` | `b274` |
  `ProductClassificationTypeName` | `x555` |
  `ProductComposition` | `x314` |
  `ProductContact` | `productcontact` |
  `ProductContactIdentifier` | `productcontactidentifier` |
  `ProductContactIDType` | `x483` |
  `ProductContactName` | `x484` |
  `ProductContactRole` | `x482` |
  `ProductContentType` | `b385` |
  `ProductForm` | `b012` |
  `ProductFormDescription` | `b014` |
  `ProductFormDetail` | `b333` |
  `ProductFormFeature` | `productformfeature` |
  `ProductFormFeatureDescription` | `b336` |
  `ProductFormFeatureType` | `b334` |
  `ProductFormFeatureValue` | `b335` |
  `ProductIdentifier` | `productidentifier` |
  `ProductIDType` | `b221` |
  `ProductionDetail` | `productiondetail` |
  `ProductionManifest` | `productionmanifest` |
  `ProductPackaging` | `b225` |
  `ProductPart` | `productpart` |
  `ProductRelationCode` | `x455` |
  `ProductSupply` | `productsupply` |
  `ProfessionalAffiliation` | `professionalaffiliation` |
  `ProfessionalPosition` | `b045` |
  `PromotionalEvent` | `promotionalevent` |
  `PromotionCampaign` | `k165` |
  `PromotionDetail` | `promotiondetail` |
  `Proximity` | `x502` |
  `Publisher` | `publisher` |
  `PublisherIdentifier` | `publisheridentifier` |
  `PublisherIDType` | `x447` |
  `PublisherName` | `b081` |
  `PublisherRepresentative` | `publisherrepresentative` |
  `PublishingDate` | `publishingdate` |
  `PublishingDateRole` | `x448` |
  `PublishingDetail` | `publishingdetail` |
  `PublishingRole` | `b291` |
  `PublishingStatus` | `b394` |
  `PublishingStatusNote` | `b395` |
  `Quantity` | `x320` |
  `QuantityUnit` | `x466` |
  `Rate` | `x505` |
  `Rating` | `x525` |
  `RatingLimit` | `x526` |
  `RatingUnits` | `x527` |
  `RecordReference` | `a001` |
  `RecordSourceIdentifier` | `recordsourceidentifier` |
  `RecordSourceIDType` | `x311` |
  `RecordSourceName` | `a197` |
  `RecordSourceType` | `a194` |
  `RegionCode` | `b398` |
  `RegionsExcluded` | `x452` |
  `RegionsIncluded` | `x450` |
  `RelatedMaterial` | `relatedmaterial` |
  `RelatedProduct` | `relatedproduct` |
  `RelatedWork` | `relatedwork` |
  `ReligiousText` | `religioustext` |
  `ReligiousTextFeature` | `religioustextfeature` |
  `ReligiousTextFeatureCode` | `b359` |
  `ReligiousTextFeatureDescription` | `b360` |
  `ReligiousTextFeatureType` | `b358` |
  `ReligiousTextIdentifier` | `b376` |
  `ReprintDetail` | `k309` |
  `Reserved` | `x536` |
  `ResourceContentType` | `x436` |
  `ResourceFeature` | `resourcefeature` |
  `ResourceFeatureType` | `x438` |
  `ResourceFileContentDescription` | `x576` |
  `ResourceFileDate` | `resourcefiledate` |
  `ResourceFileDateRole` | `x573` |
  `ResourceFileDescription` | `x571` |
  `ResourceFileDetail` | `x567` |
  `ResourceFileFeature` | `resourcefilefeature` |
  `ResourceFileFeatureDescription` | `x570` |
  `ResourceFileFeatureType` | `x568` |
  `ResourceFileFeatureValue` | `x569` |
  `ResourceFileLink` | `x572` |
  `ResourceForm` | `x441` |
  `ResourceIdentifier` | `resourceidentifier` |
  `ResourceIDType` | `x565` |
  `ResourceLink` | `x435` |
  `ResourceMode` | `x437` |
  `ResourceRole` | `x566` |
  `ResourceVersion` | `resourceversion` |
  `ResourceVersionFeature` | `resourceversionfeature` |
  `ResourceVersionFeatureType` | `x442` |
  `ReturnsCode` | `j269` |
  `ReturnsCodeType` | `j268` |
  `ReturnsCodeTypeName` | `x460` |
  `ReturnsConditions` | `returnsconditions` |
  `ReturnsNote` | `x528` |
  `ReviewRating` | `reviewrating` |
  `ROWSalesRightsType` | `x456` |
  `SalesOutlet` | `salesoutlet` |
  `SalesOutletIdentifier` | `salesoutletidentifier` |
  `SalesOutletIDType` | `b393` |
  `SalesOutletName` | `b382` |
  `SalesRestriction` | `salesrestriction` |
  `SalesRestrictionNote` | `x453` |
  `SalesRestrictionType` | `b381` |
  `SalesRights` | `salesrights` |
  `SalesRightsType` | `b089` |
  `ScriptCode` | `x420` |
  `Sender` | `sender` |
  `SenderIdentifier` | `senderidentifier` |
  `SenderIDType` | `m379` |
  `SenderName` | `x298` |
  `SentDateTime` | `x307` |
  `SequenceNumber` | `b034` |
  `SourceName` | `x330` |
  `SourceTitle` | `x428` |
  `SourceType` | `x431` |
  `SpecificationBundleName` | `specificationbundlename` |
  `SpecificationBundleNameTypeName` | `x558` |
  `SpecificationBundleNameValue` | `x559` |
  `SpecificationDescription` | `x564` |
  `SpecificationDetail` | `x560` |
  `SpecificationFeature` | `specificationfeature` |
  `SpecificationFeatureDescription` | `x563` |
  `SpecificationFeatureType` | `x561` |
  `SpecificationFeatureValue` | `x562` |
  `StartDate` | `b324` |
  `StartTime` | `x542` |
  `Stock` | `stock` |
  `StockQuantityCode` | `j297` |
  `StockQuantityCoded` | `stockquantitycoded` |
  `StockQuantityCodeType` | `j293` |
  `StockQuantityCodeTypeName` | `j296` |
  `StreetAddress` | `x552` |
  `StudyBibleType` | `b389` |
  `Subject` | `subject` |
  `SubjectCode` | `b069` |
  `SubjectDate` | `subjectdate` |
  `SubjectDateRole` | `x534` |
  `SubjectHeadingText` | `b070` |
  `SubjectSchemeIdentifier` | `b067` |
  `SubjectSchemeName` | `b171` |
  `SubjectSchemeVersion` | `b068` |
  `Subtitle` | `b029` |
  `SuffixToKey` | `b248` |
  `SupplementManifest` | `supplementmanifest` |
  `Supplier` | `supplier` |
  `SupplierCodeType` | `x458` |
  `SupplierCodeTypeName` | `x513` |
  `SupplierCodeValue` | `x459` |
  `SupplierIdentifier` | `supplieridentifier` |
  `SupplierIDType` | `j345` |
  `SupplierName` | `j137` |
  `SupplierOwnCoding` | `supplierowncoding` |
  `SupplierRole` | `j292` |
  `SupplyContact` | `supplycontact` |
  `SupplyContactIdentifier` | `supplycontactidentifier` |
  `SupplyContactRole` | `x537` |
  `SupplyContactIDType` | `x538` |
  `SupplyContactName` | `x539` |
  `SupplyDate` | `supplydate` |
  `SupplyDateRole` | `x461` |
  `SupplyDetail` | `supplydetail` |
  `SupportingResource` | `supportingresource` |
  `Tax` | `tax` |
  `TaxableAmount` | `x473` |
  `TaxAmount` | `x474` |
  `TaxExempt/` | `x546/` |
  `TaxRateCode` | `x471` |
  `TaxRatePercent` | `x472` |
  `TaxType` | `x470` |
  `TelephoneNumber` | `j270` |
  `Territory` | `territory` |
  `Text` | `d104` |
  `TextAuthor` | `d107` |
  `TextContent` | `textcontent` |
  `TextItem` | `textitem` |
  `TextItemIdentifier` | `textitemidentifier` |
  `TextItemIDType` | `b285` |
  `TextItemType` | `b290` |
  `TextSourceCorporate` | `b374` |
  `TextSourceDescription` | `x557` |
  `TextSourceLink` | `x581` |
  `TextType` | `x426` |
  `ThesisPresentedTo` | `b369` |
  `ThesisType` | `b368` |
  `ThesisYear` | `b370` |
  `TimeRun` | `timerun` |
  `TitleDetail` | `titledetail` |
  `TitleElement` | `titleelement` |
  `TitleElementLevel` | `x409` |
  `TitlePrefix` | `b030` |
  `TitlesAfterNames` | `b043` |
  `TitlesBeforeNames` | `b038` |
  `TitleStatement` | `x478` |
  `TitleText` | `b203` |
  `TitleType` | `b202` |
  `TitleWithoutPrefix` | `b031` |
  `ToLanguage` | `x413` |
  `ToQuantity` | `x514` |
  `TradeCategory` | `b384` |
  `UnnamedPersons` | `b249` |
  `UnpricedItemType` | `j192` |
  `Velocity` | `velocity` |
  `VelocityMetric` | `x504` |
  `VenueName` | `x551` |
  `VenueNote` | `x553` |
  `Website` | `website` |
  `WebsiteDescription` | `b294` |
  `WebsiteLink` | `b295` |
  `WebsiteRole` | `b367` |
  `WorkIdentifier` | `workidentifier` |
  `WorkIDType` | `b201` |
  `WorkRelationCode` | `x454` |
  `YearOfAnnual` | `b020` |

  equivalent Reference name | Short tag | Notes
  --- | --- | ---
  `RecordReference` | `a001` |
  `NotificationType` | `a002` |
  `RecordSourceType` | `a194` |
  `RecordSourceName` | `a197` |
  `DeletionText` | `a199` |
  `ProductForm` | `b012` |
  `ProductFormDescription` | `b014` |
  `YearOfAnnual` | `b020` |
  `Subtitle` | `b029` |
  `TitlePrefix` | `b030` |
  `TitleWithoutPrefix` | `b031` |
  `SequenceNumber` | `b034` |
  `ContributorRole` | `b035` |
  `PersonName` | `b036` |
  `PersonNameInverted` | `b037` |
  `TitlesBeforeNames` | `b038` |
  `NamesBeforeKey` | `b039` |
  `KeyNames` | `b040` |
  `NamesAfterKey` | `b041` |
  `LettersAfterNames` | `b042` |
  `TitlesAfterNames` | `b043` |
  `BiographicalNote` | `b044` |
  `ProfessionalPosition` | `b045` |
  `Affiliation` | `b046` |
  `CorporateName` | `b047` |
  `ContributorDescription` | `b048` |
  `ContributorStatement` | `b049` |
  `EditionNumber` | `b057` |
  `EditionStatement` | `b058` |
  `NumberOfPages` | `b061` |
  `IllustrationsNote` | `b062` |
  `MapScale` | `b063` |
  `SubjectSchemeIdentifier` | `b067` |
  `SubjectSchemeVersion` | `b068` |
  `SubjectCode` | `b069` |
  `SubjectHeadingText` | `b070` |
  `AudienceRangeQualifier` | `b074` |
  `AudienceRangePrecision` | `b075` |
  `AudienceRangeValue` | `b076` |
  `ComplexitySchemeIdentifier` | `b077` |
  `ComplexityCode` | `b078` |
  `ImprintName` | `b079` |
  `PublisherName` | `b081` |
  `CountryOfPublication` | `b083` |
  `CopyrightYear` | `b087` |
  `SalesRightsType` | `b089` |
  `NumberOfIllustrations` | `b125` |
  `SubjectSchemeName` | `b171` |
  `WorkIDType` | `b201` |
  `TitleType` | `b202` |
  `TitleText` | `b203` |
  `AudienceCodeType` | `b204` |
  `AudienceCodeTypeName` | `b205` |
  `AudienceCodeValue` | `b206` |
  `AudienceDescription` | `b207` |
  `CityOfPublication` | `b209` |
  `EditionVersionNumber` | `b217` |
  `ExtentType` | `b218` |
  `ExtentValue` | `b219` |
  `ExtentUnit` | `b220` |
  `ProductIDType` | `b221` |
  `ProductPackaging` | `b225` |
  `IDTypeName` | `b233` |
  `IDValue` | `b244` |
  `PrefixToKey` | `b247` |
  `SuffixToKey` | `b248` |
  `UnnamedPersons` | `b249` |
  `CountryCode` | `b251` |
  `LanguageCode` | `b252` |
  `LanguageRole` | `b253` |
  `Number` | `b257` |
  `ProductClassificationType` | `b274` |
  `ProductClassificationCode` | `b275` |
  `LevelSequenceNumber` | `b284` |
  `TextItemIDType` | `b285` |
  `FirstPageNumber` | `b286` |
  `LastPageNumber` | `b287` |
  `ComponentTypeName` | `b288` |
  `ComponentNumber` | `b289` |
  `TextItemType` | `b290` |
  `PublishingRole` | `b291` |
  `WebsiteDescription` | `b294` |
  `WebsiteLink` | `b295` |
  `Date` | `b306` |
  `StartDate` | `b324` |
  `EndDate` | `b325` |
  `ProductFormDetail` | `b333` |
  `ProductFormFeatureType` | `b334` |
  `ProductFormFeatureValue` | `b335` |
  `ProductFormFeatureDescription` | `b336` |
  `Percent` | `b337` |
  `BibleContents` | `b352` |
  `BibleVersion` | `b353` |
  `BiblePurpose` | `b354` |
  `BibleTextOrganization` | `b355` |
  `BibleReferenceLocation` | `b356` |
  `BibleTextFeature` | `b357` |
  `ReligiousTextFeatureType` | `b358` |
  `ReligiousTextFeatureCode` | `b359` |
  `ReligiousTextFeatureDescription` | `b360` |
  `WebsiteRole` | `b367` |
  `ThesisType` | `b368` |
  `ThesisPresentedTo` | `b369` |
  `ThesisYear` | `b370` |
  `TextSourceCorporate` | `b374` |
  `ReligiousTextIdentifier` | `b376` |
  `SalesRestrictionType` | `b381` |
  `SalesOutletName` | `b382` |
  `TradeCategory` | `b384` |
  `ProductContentType` | `b385` |
  `StudyBibleType` | `b389` |
  `CopyrightOwnerIDType` | `b392` |
  `SalesOutletIDType` | `b393` |
  `PublishingStatus` | `b394` |
  `PublishingStatusNote` | `b395` |
  `RegionCode` | `b398` |
  `Measurement` | `c094` |
  `MeasureUnitCode` | `c095` |
  `Text` | `d104` |
  `TextAuthor` | `d107` |
  `PrizeName` | `g126` |
  `PrizeYear` | `g127` |
  `PrizeCountry` | `g128` |
  `PrizeCode` | `g129` |
  `PrizeJury` | `g343` |
  `SupplierName` | `j137` |
  `OrderTime` | `j144` |
  `PackQuantity` | `j145` |
  `PriceAmount` | `j151` |
  `CurrencyCode` | `j152` |
  `UnpricedItemType` | `j192` |
  `PricePer` | `j239` |
  `PriceQualifier` | `j261` |
  `PriceTypeDescription` | `j262` |
  `MinimumOrderQuantity` | `j263` |
  `BatchQuantity` | `j264` |
  `FreeQuantity` | `j265` |
  `PriceStatus` | `j266` |
  `DiscountPercent` | `j267` |
  `ReturnsCodeType` | `j268` |
  `ReturnsCode` | `j269` |
  `TelephoneNumber` | `j270` |
  `FaxNumber` | `j271` |
  `EmailAddress` | `j272` |
  `SupplierRole` | `j292` |
  `StockQuantityCodeType` | `j293` |
  `StockQuantityCodeTypeName` | `j296` |
  `StockQuantityCode` | `j297` |
  `ExpectedDate` | `j302` |
  `SupplierIDType` | `j345` |
  `LocationName` | `j349` |
  `OnHand` | `j350` |
  `OnOrder` | `j351` |
  `DiscountCodeType` | `j363` |
  `DiscountCode` | `j364` |
  `CBO` | `j375` |
  `LocationIDType` | `j377` |
  `DiscountCodeTypeName` | `j378` |
  `ProductAvailability` | `j396` |
  `AgentIDType` | `j400` |
  `AgentName` | `j401` |
  `AgentRole` | `j402` |
  `MarketPublishingStatus` | `j407` |
  `MarketDateRole` | `j408` |
  `PromotionCampaign` | `k165` |
  `InitialPrintRun` | `k167` |
  `CopiesSold` | `k168` |
  `BookClubAdoption` | `k169` |
  `ReprintDetail` | `k309` |
  `MessageNumber` | `m180` |
  `MessageRepeat` | `m181` |
  `MessageNote` | `m183` |
  `DefaultLanguageOfText` | `m184` |
  `DefaultCurrencyCode` | `m186` |
  `SenderIDType` | `m379` |
  `AddresseeIDType` | `m380` |
  `NoContributor/` | `n339/` |
  `NoEdition/` | `n386/` |
  `SenderName` | `x298` |
  `ContactName` | `x299` |
  `AddresseeName` | `x300` |
  `PrintedOnProduct` | `x301` |
  `SentDateTime` | `x307` |
  `DefaultPriceType` | `x310` |
  `RecordSourceIDType` | `x311` |
  `BarcodeType` | `x312` |
  `PositionOnProduct` | `x313` |
  `ProductComposition` | `x314` |
  `MeasureType` | `x315` |
  `CountryOfManufacture` | `x316` |
  `EpubTechnicalProtection` | `x317` |
  `EpubUsageType` | `x318` |
  `EpubUsageStatus` | `x319` |
  `Quantity` | `x320` |
  `EpubUsageUnit` | `x321` |
  `NumberOfItemsOfThisForm` | `x322` |
  `NumberOfCopies` | `x323` |
  `CollectionType` | `x329` |
  `SourceName` | `x330` |
  `CollectionIDType` | `x344` |
  `MarketPublishingStatusNote` | `x406` |
  `TitleElementLevel` | `x409` |
  `PartNumber` | `x410` |
  `NoCollection/` | `x411/` |
  `FromLanguage` | `x412` |
  `ToLanguage` | `x413` |
  `NameType` | `x414` |
  `NameIDType` | `x415` |
  `PrimaryContentType` | `x416` |
  `ContributorDateRole` | `x417` |
  `ContributorPlaceRelator` | `x418` |
  `EditionType` | `x419` |
  `ScriptCode` | `x420` |
  `ExtentValueRoman` | `x421` |
  `Illustrated` | `x422` |
  `AncillaryContentType` | `x423` |
  `AncillaryContentDescription` | `x424` |
  `MainSubject/` | `x425/` |
  `TextType` | `x426` |
  `ContentAudience` | `x427` |
  `SourceTitle` | `x428` |
  `ContentDateRole` | `x429` |
  `CitedContentType` | `x430` |
  `SourceType` | `x431` |
  `ListName` | `x432` |
  `PositionOnList` | `x433` |
  `CitationNote` | `x434` |
  `ResourceLink` | `x435` |
  `ResourceContentType` | `x436` |
  `ResourceMode` | `x437` |
  `ResourceFeatureType` | `x438` |
  `FeatureValue` | `x439` |
  `FeatureNote` | `x440` |
  `ResourceForm` | `x441` |
  `ResourceVersionFeatureType` | `x442` |
  `CorporateNameInverted` | `x443` |
  `ImprintIDType` | `x445` |
  `LatestReprintNumber` | `x446` |
  `PublisherIDType` | `x447` |
  `PublishingDateRole` | `x448` |
  `CountriesIncluded` | `x449` |
  `RegionsIncluded` | `x450` |
  `CountriesExcluded` | `x451` |
  `RegionsExcluded` | `x452` |
  `SalesRestrictionNote` | `x453` |
  `WorkRelationCode` | `x454` |
  `ProductRelationCode` | `x455` |
  `ROWSalesRightsType` | `x456` |
  `PrimaryPart/` | `x457/` |
  `SupplierCodeType` | `x458` |
  `SupplierCodeValue` | `x459` |
  `ReturnsCodeTypeName` | `x460` |
  `SupplyDateRole` | `x461` |
  `PriceType` | `x462` |
  `PriceConditionType` | `x463` |
  `PriceConditionQuantityType` | `x464` |
  `PriceCodeType` | `x465` |
  `QuantityUnit` | `x466` |
  `DiscountType` | `x467` |
  `PriceCode` | `x468` |
  `DiscountAmount` | `x469` |
  `TaxType` | `x470` |
  `TaxRateCode` | `x471` |
  `TaxRatePercent` | `x472` |
  `TaxableAmount` | `x473` |
  `TaxAmount` | `x474` |
  `PriceDateRole` | `x476` |
  `PriceCodeTypeName` | `x477` |
  `TitleStatement` | `x478` |
  `CollectionSequenceType` | `x479` |
  `CollectionSequenceTypeName` | `x480` |
  `CollectionSequenceNumber` | `x481` |
  `ProductContactRole` | `x482` |
  `ProductContactIDType` | `x483` |
  `ProductContactName` | `x484` |
  `NoPrefix/` | `x501/` |
  `Proximity` | `x502` |
  `PrizeStatement` | `x503` |
  `VelocityMetric` | `x504` |
  `Rate` | `x505` |
  `PriceIDType` | `x506` |
  `NoProduct/` | `x507/` |
  `EpubLicenseExpressionType` | `x508` |
  `EpubLicenseExpressionTypeName` | `x509` |
  `EpubLicenseExpressionLink` | `x510` |
  `EpubLicenseName` | `x511` |
  `CopyrightType` | `x512` |
  `SupplierCodeTypeName` | `x513` |
  `ToQuantity` | `x514` |
  `EventRole` | `x515` |
  `EventName` | `x516` |
  `EventAcronym` | `x517` |
  `EventNumber` | `x518` |
  `EventTheme` | `x519` |
  `EventDate` | `x520` |
  `EventPlace` | `x521` |
  `EventSponsorIDType` | `x522` |
  `FundingIDType` | `x523` |
  `Rating` | `x525` |
  `RatingLimit` | `x526` |
  `RatingUnits` | `x527` |
  `ReturnsNote` | `x528` |
  `PriceConstraintType` | `x529` |
  `PriceConstraintStatus` | `x530` |
  `PriceConstraintUnit` | `x531` |
  `OrderQuantityMinimum` | `x532` |
  `OrderQuantityMultiple` | `x533` |
  `SubjectDateRole` | `x534` |
  `PricePartDescription` | `x535` |
  `Reserved` | `x536` |
  `SupplyContactRole` | `x537` |
  `SupplyContactIDType` | `x538` |
  `SupplyContactName` | `x539` |
  `AVItemType` | `x540` |
  `AVItemIDType` | `x541` |
  `StartTime` | `x542` |
  `EndTime` | `x543` |
  `AVDuration` | `x544` |
  `PalletQuantity` | `x545` |
  `TaxExempt/` | `x546/` |
  `EventIDType` | `x547` |
  `EventType` | `x548` |
  `EventStatus` | `x549` |
  `EventDescription` | `x550` |
  `VenueName` | `x551` |
  `StreetAddress` | `x552` |
  `VenueNote` | `x553` |
  `OccurrenceDateRole` | `x554` |
  `ProductClassificationTypeName` | `x555` |
  `PrizeRegion` | `x556` |
  `TextSourceDescription` | `x557` |
  `SpecificationBundleNameTypeName` | `x558` |
  `SpecificationBundleNameValue` | `x559` |
  `SpecificationDetail` | `x560` |
  `SpecificationFeatureType` | `x561` |
  `SpecificationFeatureValue` | `x562` |
  `SpecificationFeatureDescription` | `x563` |
  `SpecificationDescription` | `x564` |
  `ResourceIDType` | `x565` |
  `ResourceRole` | `x566` |
  `ResourceFileDetail` | `x567` |
  `ResourceFileFeatureType` | `x568` |
  `ResourceFileFeatureValue` | `x569` |
  `ResourceFileFeatureDescription` | `x570` |
  `ResourceFileDescription` | `x571` |
  `ResourceFileLink` | `x572` |
  `ResourceFileDateRole` | `x573` |
  `InsertPointType` | `x574` |
  `InsertPointValue` | `x575` |
  `ResourceFileContentDescription` | `x576` |
  `NoResource/` | `x577/` |
  `AudienceHeadingText` | `x578` |
  `NoSupplement/` | `x579/` |
  `AffiliationIDType` | `x580` |
  `TextSourceLink` | `x581` |
  `CollectionFrequency` | `x582` |
  `MainAudience/` | `x583/` |
  `AwardingBody` | `x584` |
  `EpubLicenseDateRole` | `x585` |
  `CollectionElementLevel` | `x586` |
  `MarketReference` | `x587` |
  `CopyrightStatementText` | `x588` |
  `PrizeIDType` | `x589` |
  `PostalCode` | `x590` |
  `Addressee` | `addressee` |
  `AddresseeIdentifier` | `addresseeidentifier` |
  `AffiliationIdentifier` | `affiliationidentifier` |
  `AgentIdentifier` | `agentidentifier` |
  `AlternativeName` | `alternativename` |
  `AncillaryContent` | `ancillarycontent` |
  `Audience` | `audience` |
  `AudienceRange` | `audiencerange` |
  `AVItem` | `avitem` |
  `AVItemIdentifier` | `avitemidentifier` |
  `Barcode` | `barcode` |
  `BatchBonus` | `batchbonus` |
  `Bible` | `bible` |
  `BodyManifest` | `bodymanifest` |
  `BodyResource` | `bodyresource` |
  `CitedContent` | `citedcontent` |
  `CollateralDetail` | `collateraldetail` |
  `Collection` | `collection` |
  `CollectionIdentifier` | `collectionidentifier` |
  `CollectionSequence` | `collectionsequence` |
  `ComparisonProductPrice` | `comparisonproductprice` |
  `Complexity` | `complexity` |
  `ContentDate` | `contentdate` |
  `ContentDetail` | `contentdetail` |
  `ContentItem` | `contentitem` |
  `Contributor` | `contributor` |
  `ContributorDate` | `contributordate` |
  `ContributorPlace` | `contributorplace` |
  `ContributorReference` | `contributorreference` |
  `CopyrightOwner` | `copyrightowner` |
  `CopyrightOwnerIdentifier` | `copyrightowneridentifier` |
  `CopyrightStatement` | `copyrightstatement` |
  `CoverManifest` | `covermanifest` |
  `CoverResource` | `coverresource` |
  `DescriptiveDetail` | `descriptivedetail` |
  `Discount` | `discount` |
  `DiscountCoded` | `discountcoded` |
  `EpubLicense` | `epublicense` |
  `EpubLicenseDate` | `epublicensedate` |
  `EpubLicenseExpression` | `epublicenseexpression` |
  `EpubUsageConstraint` | `epubusageconstraint` |
  `EpubUsageLimit` | `epubusagelimit` |
  `Event` | `event` |
  `EventIdentifier` | `eventidentifier` |
  `EventOccurrence` | `eventoccurrence` |
  `EventSponsor` | `eventsponsor` |
  `EventSponsorIdentifier` | `eventsponsoridentifier` |
  `Extent` | `extent` |
  `Funding` | `funding` |
  `FundingIdentifier` | `fundingidentifier` |
  `Header` | `header` |
  `Imprint` | `imprint` |
  `ImprintIdentifier` | `imprintidentifier` |
  `InsertManifest` | `insertmanifest` |
  `InsertPoint` | `insertpoint` |
  `InsertResource` | `insertresource` |
  `Language` | `language` |
  `LocationIdentifier` | `locationidentifier` |
  `Market` | `market` |
  `MarketDate` | `marketdate` |
  `MarketPublishingDetail` | `marketpublishingdetail` |
  `Measure` | `measure` |
  `NameAsSubject` | `nameassubject` |
  `NameIdentifier` | `nameidentifier` |
  `NewSupplier` | `newsupplier` |
  `OccurrenceDate` | `occurrencedate` |
  `ONIXMessage` | `ONIXmessage` |
  `OnOrderDetail` | `onorderdetail` |
  `PageRun` | `pagerun` |
  `Price` | `price` |
  `PriceCoded` | `pricecoded` |
  `PriceCondition` | `pricecondition` |
  `PriceConditionQuantity` | `priceconditionquantity` |
  `PriceConstraint` | `priceconstraint` |
  `PriceConstraintLimit` | `priceconstraintlimit` |
  `PriceDate` | `pricedate` |
  `PriceIdentifier` | `priceidentifier` |
  `Prize` | `prize` |
  `PrizeIdentifier` | `prizeidentifier` |
  `Product` | `product` |
  `ProductClassification` | `productclassification` |
  `ProductContact` | `productcontact` |
  `ProductContactIdentifier` | `productcontactidentifier` |
  `ProductFormFeature` | `productformfeature` |
  `ProductIdentifier` | `productidentifier` |
  `ProductionDetail` | `productiondetail` |
  `ProductionManifest` | `productionmanifest` |
  `ProductPart` | `productpart` |
  `ProductSupply` | `productsupply` |
  `ProfessionalAffiliation` | `professionalaffiliation` |
  `PromotionalEvent` | `promotionalevent` |
  `PromotionDetail` | `promotiondetail` |
  `Publisher` | `publisher` |
  `PublisherIdentifier` | `publisheridentifier` |
  `PublisherRepresentative` | `publisherrepresentative` |
  `PublishingDate` | `publishingdate` |
  `PublishingDetail` | `publishingdetail` |
  `RecordSourceIdentifier` | `recordsourceidentifier` |
  `RelatedMaterial` | `relatedmaterial` |
  `RelatedProduct` | `relatedproduct` |
  `RelatedWork` | `relatedwork` |
  `ReligiousText` | `religioustext` |
  `ReligiousTextFeature` | `religioustextfeature` |
  `ResourceFeature` | `resourcefeature` |
  `ResourceFileDate` | `resourcefiledate` |
  `ResourceFileFeature` | `resourcefilefeature` |
  `ResourceIdentifier` | `resourceidentifier` |
  `ResourceVersion` | `resourceversion` |
  `ResourceVersionFeature` | `resourceversionfeature` |
  `ReturnsConditions` | `returnsconditions` |
  `ReviewRating` | `reviewrating` |
  `SalesOutlet` | `salesoutlet` |
  `SalesOutletIdentifier` | `salesoutletidentifier` |
  `SalesRestriction` | `salesrestriction` |
  `SalesRights` | `salesrights` |
  `Sender` | `sender` |
  `SenderIdentifier` | `senderidentifier` |
  `SpecificationBundleName` | `specificationbundlename` |
  `SpecificationFeature` | `specificationfeature` |
  `Stock` | `stock` |
  `StockQuantityCoded` | `stockquantitycoded` |
  `Subject` | `subject` |
  `SubjectDate` | `subjectdate` |
  `SupplementManifest` | `supplementmanifest` |
  `Supplier` | `supplier` |
  `SupplierIdentifier` | `supplieridentifier` |
  `SupplierOwnCoding` | `supplierowncoding` |
  `SupplyContact` | `supplycontact` |
  `SupplyContactIdentifier` | `supplycontactidentifier` |
  `SupplyDate` | `supplydate` |
  `SupplyDetail` | `supplydetail` |
  `SupportingResource` | `supportingresource` |
  `Tax` | `tax` |
  `Territory` | `territory` |
  `TextContent` | `textcontent` |
  `TextItem` | `textitem` |
  `TextItemIdentifier` | `textitemidentifier` |
  `TimeRun` | `timerun` |
  `TitleDetail` | `titledetail` |
  `TitleElement` | `titleelement` |
  `Velocity` | `velocity` |
  `Website` | `website` |
  `WorkIdentifier` | `workidentifier` |

#### A.4 List of elements removed from Release 3.1

Release 3.1 removes a number of XML tags and data structures that were present in the previous versions (Release 3.0 up to revision 8). Nearly all of these were deprecated in previous revisions of ONIX. Note that any ONIX message that is valid ONIX 3.0 and which does not use any of the following removed data elements and structures is ‘3.1-ready’, and requires only a change of the release and xmlns namespace attributes to create a valid ONIX 3.1 message.

  List of removed tag names
  Reference name | equivalent Short tag | Notes
  --- | --- | ---
  `AudienceCode` | `b073` | use <Audience> instead
  `Conference` | `conference` | use <Event> with <EventRole> code 01, and equivalent tags within <Event> instead
  `ConferenceAcronym` | `b341`
  `ConferenceDate` | `b054`
  `ConferenceName` | `b052`
  `ConferenceNumber` | `b053`
  `ConferencePlace` | `b055`
  `ConferenceRole` | `b051`
  `ConferenceSponsor` | `conferencesponsor`
  `ConferenceSponsorIdentifier` | `conferencesponsoridentifier`
  `ConferenceSponsorIDType` | `b391`
  `ConferenceTheme` | `b342`
  `CurrencyZone` | `x475` | use <Territory> within <Price> instead
  `DateFormat` | `j260` | use dateformat attribute instead
  `Gender` | `x524` | no equivalent in release 3.1
  `PromotionContact` | `k166` | use <ProductContact> instead
  `Reissue` | `reissue` | use composites in Block 2 with <ContentDate> for reissue collateral instead
  `ReissueDate` | `j365` | use <PublishingDate> and/or <MarketDate> instead
  `ReissueDescription` | `j366` | no equivalent in release 3.1

In addition to the above removed data elements, two data structures have been removed without removing the XML tags themselves. Specifically, the previously-deprecated use of <SalesRestriction> outside of <SalesRights> in Block 4 has been removed (this was P.21.11 to P.21.18 in previous documentation), together with the use of <UnnamedPersons> after contributor fields such as Contributor dates, Affiliations, Biographical notes, Places etc (ie P.7.47 in previous documentation).

  list of removed tag contexts
  Reference name | equivalent Short tag | Notes
  --- | --- | ---
  `SalesRestriction` | `salesrestriction` | use <SalesRestriction> inside of <SalesRights> instead (ie at P.21.5a to P.21.5h)
  `UnnamedPersons` | `b249` | use <UnnamedPersons> before contributor date, affiliation, biographical note, place fields instead (ie at P.7.20a)