EXAMPLE

In an article written in Finnish, it is better to use phrases “Julkaisussa” (“In” in Finnish) and “Saatavissa” (“Available from” in Finnish) instead of “In” and “Available from”.

EXAMPLE 1

For a publication written in Latin script, any data element in a non-Roman alphabet in the cited information resource is Romanized, with the Romanized portion appended to the data element as associated information.

EXAMPLE 2

For a publication not written in Latin script, any data element in a Roman alphabet in the cited information resource is transliterated or transcribed to the script used, with the converted portion appended to the data element as associated information.

EXAMPLE 1

==== Roles

==== Selection

==== Personal names

===== General

===== Variant forms

===== Additions

==== Organization or group names

===== Form of name

===== Disambiguation of names

===== Subordinate body

===== Parent body

==== Multiple creators

===== Title first

===== Conferences

===== Subsidiary creator

===== Originators of multiple editions

===== Derivative work creator

==== Pseudonyms

==== Anonymous works

ISO 690, Clause 4.1 classifies the various possible roles a creator can have with regard to a resource into six broad categories in order of priority, with more refined classifications typically named for the creator. These classifications are retained in the model: bibitem/contributor/role@type provides the broad category of role (author, performer, compiler, adaptor, publisher, distributor), while bibitem/contributor/role/description contains one or more specific descriptions of the role of the contributor.

The content of the bibitem/contributor/role element is optional, and contains a more specific expression of the creator role. The description can be strictly a noun, e.g. “librettist”, or it can be a phrase, corresponding to how it will be rendered in a citation (“libretto by”); the choice is at the discretion of the bibliographer, and is determined by how the citation is expected to be rendered (as rendering systems are unlikely to be sophisticated enough to convert the one into the other.)

Whether subsidiary creators should be included in a bibliographic item, and which creators should be included, is at the discretion of the bibliographer.

Exceptionally, “translator” is differentiated from the other “adaptor” roles, because it is so different from other adaptor roles such as engraver or photographer.

For derivative works, the creator and title of the original resource can be mentioned as a bibliographic note (bibitem/note); however best practice is to treat the original resource as a distinct related bibliographic item, related through the “derivedFrom” relation ([doc-relations]). Likewise, different originators of different editions should be modelled by modelling the editions as distinct related items, each with its own distinct editor as contributor. (For example, the later edition given as the main item, and the earlier edition related through a “updatedBy” relation.)

<bibitem type="incollection">
  <title>Object play in great apes: Studies in nature and captivity</title>
  <date type="published"><on>2005</on></date>
  <contributor>
    <role type="author"/>
    <person>
      <name>
        <surname>Ramsey</surname>
        <initials>J. K.</initials>
      </name>
    </person>
  </contributor>
  <contributor>
    <role type="author"/>
    <person>
      <name>
        <surname>McGrew</surname>
        <initials>W. C.</initials>
      </name>
    </person>
  </contributor>
  <relation type="includedIn">
    <bibitem>
      <title>The nature of play: Great apes and humans</title>
      <contributor>
        <role type="editor"/>
        <person>
          <name>
            <surname>Pellegrini</surname>
            <initials>A. D.</initials>
          </name>
        </person>
      </contributor>
      <contributor>
        <role type="editor"/>
        <person>
          <name>
            <surname>Smith</surname>
            <initials>P. K.</initials>
          </name>
        </person>
      </contributor>
      <contributor>
        <role type="publisher"/>
        <organization>
          <name>Guilford Press</name>
        </organization>
      </contributor>
      <place>New York, NY</place>
    </bibitem>
  </relation>
  <extent type="page">
    <referenceFrom>89</referenceFrom>
    <referenceTo>112</referenceTo>
  </extent>
</bibitem>

<bibitem type="book">
  <title>Speeches 50-59</title>
  <date type="published"><on>2003</on></date>
  <contributor>
    <role type="author"/>
    <person>
      <name>
        <completename>Demosthenes</completename>
      </name>
    </person>
  </contributor>
  <contributor>
    <role type="translator"/>
    <person>
      <name>
        <surname>Bers</surname>
        <initials>Victor</initials>
      </name>
    </person>
  </contributor>
  <contributor>
    <role type="publisher"/>
    <organization>
      <name>University of Texas Press</name>
    </organization>
  </contributor>
  <language>en</language>
  <relation type="translatedFrom">
    <bibitem>
      <title>Speeches 50-59</title>
      <language>grc</language>
    </bibitem>
  </relation>
  <place>Austin</place>
</bibitem>

<bibitem type="book">
  <title>Roget's Thesaurus</title>
  <date type="created"><on>1852</on></date>
  <date type="updated"><on>1982</on></date>
  <date type="published"><on>1982</on></date>
  <contributor>
    <role type="author"/>
    <person>
      <name>
        <surname>Roget</surname>
        <forename>Peter</forename>
        <forename>Mark</forename>
      </name>
    </person>
  </contributor>
  <contributor>
    <role type="editor">revised</role>
    <person>
      <name>
        <surname>Lloyd</surname>
        <forename>Susan</forename>
        <forename>M.</forename>
      </name>
    </person>
  </contributor>
  <contributor>
    <role type="publisher"/>
    <organization>
      <name>Longman Group Limited</name>
    </organization>
  </contributor>
  <place>Burnt Mill, Harlow, Essex</place>
</bibitem>

<bibitem type="music">
  <title>All' Lust und Freud'</title>
  <date type="published"><on>1983</on></date>
  <contributor>
    <role type="performer"/>
    <organization>
      <name>Winsbacher Knabenchor</name>
    </organization>
  </contributor>
  <contributor>
    <role type="author">composer</role>
    <person><name><completename>Gastoldi, Giovanni Giacomo</completename></name></person>
  </contributor>
  <contributor>
    <role type="author">composer</role>
    <person><name><completename>Isaak, Heinrich</completename></name></person>
  </contributor>
  <contributor>
    <role type="author">composer</role>
    <person><name><completename>Othmayr, Caspar</completename></name></person>
  </contributor>
  <contributor>
    <role type="author">composer</role>
    <person><name><completename>Demantius, Christoph</completename></name></person>
  </contributor>
  <contributor>
    <role type="publisher"/>
    <organization>
      <name>Bellaphon</name>
    </person>
  </organization>
  <medium>
    <carrier>audio disc</carrier>
  </medium>
  <place>Frankfurt</place>
</bibitem>

=== Personal names

Names may be modelled either broken up into their constituent components (prefix, forename, initials, surname, addition), or as a complete name string. The latter is useful if (contrary to the recommendation of ISO 690, Clause 4.1) language-specific conventions for ordering of name components are to be observed; e.g. “James CLARK, John COWAN, MURATA Makoto”.

If there are multiple contributors named in a role, all contributors are expected to be represented in the bibliographic entry. This reflects practice in electronic bibliographic tools, and renderers may choose to truncate contributors with “et al.” beyond a certain cuttoff point.. If this information is not available, a dummy contributor can be named with “et al.” as their completename, but this is not preferred.

The initials component is used if all forenames are replaced by initials. If only the middle name is replaced by an initial, it is still treated as a forename.

<person>
  <name>
    <surname>Bach</surname>
    <initials>J. S.</initials>
  </name>
</person>

<person>
  <name>
    <surname>Picasso</surname>
    <forename>Pablo</forename>
  </name>
</person>

<person>
  <name>
    <prefix>Dr.</prefix>
    <surname>King</surname>
    <forename>Martin</forename>
    <forename>Luther</forename>
    <addition>Jr.</addition>
    <addition>Rev.</addition>
  </name>
</person>

<person>
  <name>
    <completename>KING, Martin Luther, Jr.</completename>
  </name>
</person>

<person>
  <name>
    <surname>Stewart</surname>
    <forename>John</forename>
    <forename>H.</forename>
  </name>
</person>

=== Organisations

The model caters for both full names and abbreviations of organisations. Subordinate body names are modelled separately from the parent body name; the choice of whether to model parent + subordinate or a single name depends on the degree of independence of the subordinate body, as outlined in ISO 690, Clause 4.1.

<organization>
  <name>St. Thomas University [Florida]</name>
</organization>

<organization>
  <name>St. Thomas University [New Brunswick]</name>
</organization>

<organization>
  <name>Academy of Athens</name>
  <subdivision>Research Centre for Modern Greek Dialects</subdivision>
</organization>

=== Pseudonyms and Variant Names

Variant names, and assumed names, can both be modelled as notes on names. However, for greater clarity, and for modelling of the internal structure of the variant or assumed name, a variant name can be modelled, with the same level of detail as default names. The type of variant, or relation between the name and variant, needs to be made explicit in that case. For example pseudonym/pseudonymOf for literary pseudonyms, or username/usernameOf for social media usernames.

Variant names can be applied to personal names, organization names, and organization subdivision names.

<person>
  <surname>Twain</surname>
  <forename>Mark</forename>
  <note>pseud. of Samuel Langhorne CLEMENS</note>
</person>

<person>
  <surname>Twain</surname>
  <forename>Mark</forename>
  <variant type="pseudonymOf">
    <surname>Clemens</surname>
    <forename>Samuel</forename>
    <forename>Langhorne</forename>
  </variant>
  <variant type="transliteration">
    <surname language="el">Τουαίην</surname>
    <forename language="el">Μαρκ</forename>
  </variant>
</person>

=== Anonymous and Varii

Descriptors of authors, such as “Anon” or “Various Authors”, should be given as completename elements. The model does not standardise the designations of authors. As with pseudonyms, the real name of the creator if known can be modelled as a note, or as a name variant.

<bibitem type="book">
  <title>Sir Gawain and the Green Knight</title>
  <date type="published"><on>1970</on></date>
  <contributor>
    <role type="author"/>
    <person><name><completename>Anon</completename></name></person>
  </contributor>
  <contributor>
    <role type="editor"/>
    <person><name><completename>R. A. WALDRON</completename></name></person>
  </contributor>
  <contributor>
    <role type="publisher"/>
    <organization>
      <name>Northwestern University Press</name>
    </person>
  </organization>
  <place>Evanston</place>
</bibitem>

<bibitem type="book">
  <title>An Essay on the Principle of Population</title>
  <date type="published"><on>1798</on></date>
  <contributor>
    <role type="author"/>
    <person><name><completename>Anon</completename></name></person>
    <variantname type="realname">
      <completename>Thomas Robert MALTHUS</completename>
    </variantname>
  </contributor>
  <contributor>
    <role type="publisher"/>
    <person><name><completename>J. Johnson</completename></name></person>
  </contributor>
  <edition>1st edition</edition>
  <place>London</place>
</bibitem>

== Contribution and contributor models

=== Title

==== Preferred form

The wording and spelling of the title should be given in the form in which it appears in the cited information resource (see Clause 6, Paragraph 1).

A title is serialised as bibitem/title, with its type in title/@type and its language and script in the language attributes (see Clause 8.1).

Additional information such as the format or date may be provided, if necessary.

A work identifier (e.g., ISAN) may be added after the title, preceded by the identifier type. The identifier should be used if the title alone does not uniquely identify the cited resource.

==== Alternative forms

If alternative forms of title are given in the cited information source, the most prominent should be used. If several forms are given equal prominence, the form used should be one of the following, listed in order of preference:

A resource can have multiple titles, including alternative titles and subtitles. Titles are classified through title@type; the model allows for “alternative”, “subtitle”, “unofficial” (i.e. a title that has become prevalent but has never been the official/intended title of the resource), “original” (including the source language title of a translated resource), and “main” (for the proper title or titles of the resource). If a title type is not given, it is assumed to be a main title.

<bibitem type="book">
  <title type="original">Travels into Several Remote Nations of the World. In Four Parts</title>
  <title type="unofficial">Gulliver's Travels</title>
  <date type="published"><from>1726</from><to>1727</to></date>
  <contributor>
    <role type="author"/>
    <person><name><completename>Lemuel Gulliver</completename></name></person>
    <note>pseud. of Jonathan Swift</note>
  </contributor>
  <contributor>
    <role type="publisher"/>
    <person><name><completename>Benj. Motte</completename></name></person>
  </contributor>
  <place>London</place>
</bibitem>

==== Popular or original title

If the information resource used is widely known by, or was originally issued under, a title different from that of the cited version, the alternative may also be given. The alternative title shall be placed in brackets immediately following the original title.

A popular title is serialised as title@type = "unofficial", and the source language title of a translated resource as title@type = "original".

<bibitem type="book">
  <title type="original" lang="zh" script="Hant">孫子兵法</title>
  <title type="main">The Art of War</title>
  <date type="published"><on>1963</on></date>
  <contributor>
    <role type="author"/>
    <person><name><completename>Sun Tzu</completename></name></person>
  </contributor>
  <contributor>
    <role type="translator"/>
    <person><name><completename>Samuel B. Griffith</completename></name></person>
  </contributor>
  <contributor>
    <role type="publisher"/>
    <organization><name>Oxford University Press</name></organization>
  </contributor>
  <place>Oxford</place>
</bibitem>

==== Long title

A title that is inconveniently long may be shortened by the omission of some words, but initial words, other than the definite or indefinite article, should not be omitted, nor should the sense be altered. The omitted words, except for omitted articles, should be replaced by an ellipsis indicated by three dots (for abbreviation of periodical titles, see [series_abbreviation]).

Even the truncated title should enable unique identification of the cited information resource. Generic titles, even if long, should not be truncated.

==== Additional title parts

Subtitles shall be included if they are required for the identification of the cited information resource (see [ambiguous_title]), otherwise they may be omitted. A subtitle is serialised as title@type = "subtitle".

If the cited information resource consists of two or more parts, the full title of the part used shall be included.

==== Ambiguous or incorrect title

Elucidation of a title that is ambiguous or fails to indicate clearly the content of the cited information resource may be supplied in brackets after the title. If a title contains an obscure abbreviation, the full form, if known, may be supplied.

==== No title

If there is no clear title in the cited information resource or in embedded / external metadata, a popular or traditional title may be given, if one exists. Otherwise, a title should be supplied in brackets, giving the following information:

“Untitled” can be treated as a main title.

==== Translated title

A translation of the title (and/or its Romanized form) of the cited information resource in the language of the publication may be supplied immediately after the original title.

A translated title is serialised as an additional bibitem/title with its language and script attributes.

If both translated title and its Romanized form are given, a semicolon may be used as a delimiter between them.

==== Titles of translated works

The original title of a work, or its translation or Romanized form, may be supplied immediately after the title used in the cited information resource.

==== Representation

The title element can have a key role in enabling the users to locate the cited information resource. Therefore, the title may be emphasized.

For translated and Romanized titles placed in brackets, the emphasis should be used in order to differentiate between this title-derived information and other supplementary information also in brackets.

Titles in scripts that are not traditionally emphasized, should not be emphasized.

<bibitem type="music">
  <title>Untitled</title>
  <title type="unofficial">Vaka</title>
  <date type="published"><on>2002</on></date>
  <contributor>
    <role type="author">composer</role>
    <organization><name>Sigur Rós</name></organization>
  </contributor>
  <medium>
    <form>compact disc</form>
  </medium>
  <relation type="includedIn">
    <bibitem>
      <title>( )</title>
      <contributor>
        <role type="author">composer</role>
        <organization><name>Sigur Rós</name></organization>
      </contributor>
      <contributor>
        <role type="publisher"/>
        <organization><name>Sundlaugin</name></organization>
      </contributor>
      <place>Mosfellsbær, Iceland</place>
    </bibitem>
    <locality type="track">
      <referenceFrom>1</referenceFrom>
    </locality>
  </relation>
</bibitem>

=== Component parts

==== General

Citable information resources can be component parts of host resources, other citable information resources.

Component parts include articles in periodicals, newspapers and Web sites, individual tracks (and their lyrics) in LPs and CDs, poems and short stories published in books, episodes in TV series, conference presentations published in proceedings, and so on.

A component part is serialised as a relation of the item within its host item (see [doc-relations]); the position of the component part within the host item is given in relation/locality, and its extent in bibitem/extent.

<bibitem type="poem">
  <title>Strange meeting</title>
  <contributor>
    <role type="author"/>
    <person><name><completename>W. Owen</completename></name></person>
  </contributor>
  <relation type="includedIn">
    <bibitem type="book">
      <title>Poems by Wilfred Owen</title>
      <contributor>
        <role type="author"/>
        <person><name><completename>W. Owen</completename></name></person>
      </contributor>
      <contributor>
        <role type="publisher"/>
        <organization><name>Chatto &amp; Windus</name></organization>
      </contributor>
      <place>London</place>
      <date type="published"><on>1920</on></date>
    </bibitem>
    <locality type="page">
      <referenceFrom>1</referenceFrom>
      <referenceTo>2</referenceTo>
    </locality>
  </relation>
</bibitem>

==== Representation

===== General

If the host information resource is not a serial, a connector phrase. “In:” or equivalent in the language of the publication should precede the title of the host item.

The method of representation is given below, where {hostItemTitle} is the title of the host item.

In: {hostItemTitle}

It is also possible to provide a more complete description of the host resource, where hostResourceReference is the reference to the host item:

In: {hostResourceReference}

Locality information within the host item may be provided, where locality is the location of the component part within the host item:

In: {hostItemReference}, {locality}

===== Serials

The use of the connector phrase is not needed for citations which are contributions from journals. It is optional for other types of serials.

===== Emphasis for locatability

Reference should enable the users to locate the cited information resource, no matter how granular it is (for instance, a component part of a component part, such as an image in a journal article).

=== Formats and resource type categorization

==== Formats

An information resource with identical content can be published in multiple formats, potentially manifesting via multiple types of media.

In specifying format, it is recommended not to specify the reading or interpreting device used. It is generally unnecessary to indicate the actual digital file format.

ISO 690 differentiates between the content type of the item, the media type (which includes file format for electronic media), the carrier type, the size of the item (which can include duration, and electronic file size, as well as physical medium size), and for maps, the scale of the item. These are all modelled as elements of the item medium; the media type or file format is modelled as medium/form.

There is no fixed vocabulary modelled for any of the elements of medium (although ISO 690 suggests closed Resource Description and Access (RDA) vocabularies for medium/content and medium/carrier, and IANA Media Type is best practice for medium/form for electronic resources. As ISO 690 allows, there may be instances where the medium descriptions need to be discursive.

ISO 690 suggests specifying detailed information about the type of electronic information resource (e.g. “statistical dataset”), which cannot be represented in the type of bibliographic item (bibitem/@type), and is likely to be to specific for the RDA triple of content, carrier and form. The medium/genre element is intended to convey this kind of information, and can be used more generally as a well-recognised subclass of bibliographic type or content.

Information about alternate formats should be modelled as related bibliographic items (through the “instance” document relation), each with their own medium information.

The size and scale of the item (medium/size, medium/scale) usually contains numerical information, but is modelled as a string, given the complications of how size and scale can be described, particularly for cartographic material.

<bibitem type="music">
  <title>Untitled</title>
  <title type="unofficial">Vaka</title>
  <date type="published"><on>2002</on></date>
  <contributor>
    <role type="author">composer</role>
    <organization><name>Sigur Rós</name></organization>
  </contributor>
  <medium>
    <form>compact disc</form>
  </medium>
  <relation type="includedIn">
    <bibitem>
      <title>( )</title>
      <contributor>
        <role type="author">composer</role>
        <organization><name>Sigur Rós</name></organization>
      </contributor>
      <contributor>
        <role type="publisher"/>
        <organization><name>Sundlaugin</name></organization>
      </contributor>
      <place>Mosfellsbær, Iceland</place>
    </bibitem>
    <locality type="track">
      <referenceFrom>1</referenceFrom>
    </locality>
  </relation>
</bibitem>

<bibitem type="map">
  <title>Geologic Map of Western Whatcom County, Washington</title>
  <date type="published"><on>1976</on></date>
  <contributor>
    <role type="author"/>
    <person><name><completename>Easterbrook, Don J.</completename></name></person>
  </contributor>
  <contributor>
    <role type="publisher"/>
    <organization><name>U.S. Geological Survey</name></organization>
  </contributor>
  <medium>
    <form>map</form>
    <size>col. 68 x 69 cm. fold. in envelope 30 x 24 cm.</size>
    <scale>1:62500</scale>
  </medium>
  <series>
    <title>Miscellaneous Investigations Series</title>
    <number>map 1-854-B</number>
  </series>
  <place>Reston, VA</place>
</bibitem>

<bibitem type="electronic resource">
  <title>#Polio is 99% eradicated. Join me & @FCBarcelona as we work to finish the job and #EndPolio</title>
  <date type="published"><on>2013-02-26</on></date>
  <date type="accessed"><on>2016-07-06T12:30:15+02:00</on></date>
  <contributor>
    <role type="author"/>
    <person>
      <name>
        <surname>Gates</surname>
        <initial>B.</initial>
      </name>
      <variant type="username">
        <completename>BillGates</completename>
      </variant>
    </person>
  </contributor>
  <uri>https://twitter.com/BillGates/status/306195345845665792</uri>
  <medium>
    <form>Twitter</form>
    <genre>tweet</genre>
  </medium>
  <relation type="complements">
    <bibitem type="video">
       <uri>http://b-gat.es/X75Lvy</uri>
    </bibitem>
  </relation>
</bibitem>

==== Resource type categorization

===== General

Content, media and carrier type should be specified if they have a significant impact on the intellectual content, look and feel, or usage of the cited information resource.

The information should be taken from the resource if it is provided. Otherwise, an external reference may be used when necessary for identification purposes, such as:

Resource type description does not always provide added value for citations.

===== Content type

Content type should be provided when it is required for the identification of the cited work. For instance, there may be several related interrelated works which share the same title.

===== Carrier type

Digital information resources can be fragile. In order to preserve them, it will be necessary to transfer them to new carriers. For instance, audio tapes last only up to 30 years, but their lifespan can be even shorter if the tapes are not stored correctly. And even if the carrier itself is still fine, finding a player for an outdated carrier type (e.g. a C-cassette deck) may be difficult.

Since carrier type information will become outdated, carrier type should not be specified if the same version of the information resource is known to be available on multiple carriers (e.g. LP, C-cassette, CD) or if the information used is available even on versions published on other carriers.

Carrier type should be provided if the carrier type is relevant for the citation.

==== Digital file formats

The digital file format of the cited online electronic information resource should be specified. This is especially the case when the carrier type is not provided or if the carrier type does not provide sufficient detail about the file format.

Identification of digital file formats may utilize the following information:

If the format of the cited resource is uncommon, sufficient technical metadata or a link to such metadata should be provided. In cases where the cited resource is from an archive with a digital preservation program, this may be covered by the archive.

If the format is widely known and supported (e.g., HTML), the RDA term “online resource” or just “online” may be used instead of the file format designation. Type of the resource may also be specified.

The specific type of electronic information resource may also be specified, if it is not clear from the context. The level of specificity may be chosen, as appropriate.

Information about other file formats in which the cited information resource is available (e.g., a PDF version of an HTML document which was originally used) may be provided in addition to the cited resource. Information about alternative formats should be clearly separated from the information pertaining to the file format used, and it should be preceded by an appropriate phrase, including the file format and the online host if necessary.

If an alternative file format is included in the reference, a check should be made to verify that the alternative resource contains the cited information. Digital surrogates of printed resources can differ significantly from the original documents.

==== Migrated medium

If the information resource used has been migrated and the original resource is no longer accessible, the migrated resource may be used if it contains the cited information. A note about the original version may be added.

=== Edition and version

==== Editions

Editions are used to differentiate significant content revisions, including draft stages.

Editions are modelled as free text, given the variety of ways they can be represented. For that reason, the full word “edition” needs to appear after any ordinal. The optional number attribute can be used to provide a numeric equivalent.

An edition number shall be provided if the information resource is of a second edition or higher. The edition should be specified in the terms, including symbols, used in the cited information resource. The word for “edition” or equivalent term in the language of the cited information resource may be abbreviated.

If there is a reasonable expectation of forthcoming editions, an edition number should be provided even when the cited information resource is a first edition.

If a program or research dataset cited is updated often, edition (or version) should be included only if necessary, since the information provided becomes outdated very quickly, and locating and/or running the indicated version is likely to be difficult. An edition number is required if other (earlier or later) editions of the program or research dataset are not applicable.

If an edition (or version) number is provided for programs and research datasets, a first edition is not an exception. The first official release of a program may not be the first version that has been available for the public. Edition is also important since hardware and software requirements are dependent on version information.

<bibitem type="book">
  <title>An Essay on the Principle of Population</title>
  <date type="published"><on>1798</on></date>
  <contributor>
    <role type="author"/>
    <person><name><completename>Anon</completename></name></person>
    <note>Thomas Robert MALTHUS</note>
  </contributor>
  <contributor>
    <role type="publisher"/>
    <person><name><completename>J. Johnson</completename></name></person>
  </contributor>
  <edition number="1">1st edition</edition>
  <place>London</place>
</bibitem>

<bibitem type="book">
  <title>The Structure of Production</title>
  <date type="published"><on>2015</on></date>
  <contributor>
    <role type="author"/>
    <person>
      <name>
        <surname>Skousen</surname>
        <forename>Mark</forename>
      </name>
    </person>
  </contributor>
  <contributor>
    <role type="publisher"/>
    <organization><name>New York University Press</name></organization>
  </contributor>
  <edition>New revised edition</edition>
  <place>New York</place>
</bibitem>

Some information resources may be appropriately cited prior to formal publication. For instance, it is possible to cite a preprint of a scientific article before it is published, or a standard when it is still under preparation (see [standards-section]).

Citing an unfinished information resource shall follow the guidelines provided either within the information resource or by the publisher. Draft stage indication (such as “Preprint” or “work in progress” shall be incorporated into the reference according to such guidance.

Reprints should also be specified as such, with the phrase “Reprint” or equivalent after the title.

==== Audience differentiated content

If an information resource is published in different languages in different countries, the country of publication should be given after the title in the language used in the source and separated from the main title with a colon.

If the edition of the cited resource shown to a user depends on his or her geographical location, a note indicating the edition used should be provided. If the content of a resource can be personified with e.g., cookies or some other technique, citation should be based on a non-personified basic version of the page.

==== Version

If the cited information resources has been updated or expanded, it usually has a version statement. The number and other designation for the version should be recorded in the terms given in the cited information resource.

The version element can be used to give more detailed information about resource versions, including version numbers (drafts) and version dates (which are differentiated from date, since they are often used as version identifiers).

As described in [datetypes], dates when a resource was last accessed are modelled as date[@type = "accessed"]; dates when a resource was last updated are modelled as date[@type = "updated"].

If a change in a file format version has an impact on the usage (for instance, different tool is needed to render the resource), the version information should be provided.

Personified Web resources should not be used for referencing, since other users may not be able to verify whether the resource does contain or did contain the cited information.

If a specific version of an information resource is cited, the version should be indicated by giving the name and/or number of the release, update or equivalent, and, if necessary, the year, with (if necessary) month, day and time (see [season_month_day_time]), when that version was created or updated. It is also possible to specify the date when the information resource was viewed or accessed.

<bibitem type="webresource">
  <title>When did the sounds of 'w' and 'v' change in High German?</title>
  <uri>https://linguistics.stackexchange.com/questions/22872/when-did-the-sounds-of-w-and-v-change-in-high-german</uri>
  <date type="updated"><on>2017-05-08</on></date>
  <date type="accessed"><on>2018-05-10</on></date>
  <relation type="includedIn">
    <bibitem type="website">
      <title>Stack Exchange: Linguistics Beta</title>
    </bibitem>
  </relation>
</bibitem>

<bibitem type="software">
  <title>Mozilla Firefox</title>
  <uri>https://www.mozilla.org/</uri>
  <date type="accessed">2019-01-11</date>
  <contributor>
    <role type="author"/>
    <organization>
      <name>Mozilla Foundation</name>
    </organization>
  </contributor>
  <version>
    <draft>60.4.0 ESR</draft>
  </version>
  <medium>
    <content>computer program</content>
  </medium>
</bibitem>

Guidelines for citing versions of Web pages and their component parts are described in detail in [network_location].

=== Date

==== General

The date of publication, manufacture, distribution, execution, transmission, etc., should be cited if necessary. For physical items such as printed books, providing the year is often sufficient to facilitate locatability, but for intangible works (e.g., Internet documents, serials, research datasets and patents), the explicit date and time of the last modification and/or date and time the document was viewed may be necessary.

If appropriate, date may be expressed as shown in the cited information resource or external metadata describing the resource, e.g., the name of a season or a university term.

The format of the date information should be based on representations provided in the ISO 8601 series if the information should be machine readable and understandable.

A date is serialised as date/@type (the lifecycle phase, from the BibliographicDateType vocabulary) with either the point date date/on, or the range date/from and date/to, each in the ISO 8601 format. A date that cannot be expressed as a Gregorian date is serialised as text in date/@text.

<bibitem type="article">
  <title>DNA's double helix: 60 years since life's deep molecular secrets was discovered</title>
  <date type="published"><on>2013-02-22</on></date>
  <relation type="includedIn">
    <bibitem type="periodical">
      <title>The Guardian</title>
    </bibitem>
  </relation>
</bibitem>

==== Model

For a point date, only date/on is populated. For a date range, date/from and date/to are populated. If the range is ongoing, the date/to element is left out.

The date for date/on, date/from and date/to is by default given as a Gregorian date/time, following the conventions of ISO 8601-1; in an XML serialisation, they would be expected to follow the XML Schema xs:datetime representation (Clause 8.2.1.1, Example 1). However bibliographic dates often contain information that cannot be restricted to an ISO 8601 date (dates in other calendars, date corrections; other subdivisions of the year; approximate date or no date.) For that reason, the model allows dates to be expressed in text instead of as an ISO 8601 date (date/on@text, date/from@text, date/to@text), or as well as an ISO 8601 date if a Gregorian date is still applicable. If the textual value of a date is a date range, and ISO 8601 dates are still to be provided for the start and end of the date range, then the textual value is repeated for date/from@text and date/to@text.

Date corrections may also involve indications of provenance ([provenance]).

The date of copyright is associated expressly with the copyright holder, in bibitem/copyright/date/from. Unlike other bibliographic dates, the copyright date can only have a year value.

<bibitem type="book">
  <title>Roget's Thesaurus</title>
  <date type="created"><on>1852</on></date>
  <date type="updated"><on>1982</on></date>
  <date type="published"><on>1982</on></date>
  <contributor>
    <role type="author"/>
    <person>
      <name>
        <surname>Roget</surname>
        <forename>Peter</forename>
        <forename>Mark</forename>
      </name>
    </person>
  </contributor>
  <contributor>
    <role type="editor">revised</role>
    <person>
      <name>
        <surname>Lloyd</surname>
        <forename>Susan</forename>
        <forename>M.</forename>
      </name>
    </person>
  </contributor>
  <contributor>
    <role type="publisher"/>
    <organization>
      <name>Longman Group Limited</name>
    </organization>
  </contributor>
  <place>Burnt Mill, Harlow, Essex</place>
</bibitem>

===== Date types

Dates are associated with specific phases of the production of a bibliographic item, and those phases are named through date@type. The default type used in bibliography is the date of publication (date[@type = "published"]), but the “created”, “updated”, “unchanged”, and “copied” dates in particular are often given where they differ from the date of publication. The date of transmission is used instead of the date of publication for a broadcast.

The repertoire of date types is expanded to deal with the particular requirements of standards:

Normal bibliographic dates:

Standards bibliographic dates:

The date of publication is taken to be the date when the current version of the resource was published, unless a separate “unchanged”, “updated” or “copied” date is given; in that case, the date of publication is assumed to be the date of initial publication.

The date of creation is taken to apply to the work instantiated by the resource, rather than to a specific format or edition. The latter are represented by the date of adaptation and of update, respectively.

==== Representation

===== Year

The year should usually be given as it appears in the cited information resource, however, years written as words in the cited information resource should be given as Arabic numerals in the reference.

If the cited information resource bears a date from a calendar system other than the Common Era (CE), the date should be given together with its ISO 8601-1 equivalent in the CE calendar system supplied as associated information.

===== Season, month, day, time

If a machine readable date is required, it should be provided in a format compliant with the ISO 8601 series, including, if necessary, time. In that case, the time zone may also be provided.

The precise date may be provided with the season or month spelled out, either in full or abbreviated, and with day, month, year and time given in the order and language used in the cited resource (see Clause 6, Paragraph 1). If so, an ISO 8601 equivalent of the date may also be provided as associated information after the date from the cited resource.

====== Uncertain, unknown, approximate or missing date

If the year of publication is not given but can be ascertained, it should be supplied. If the date is uncertain, an approximate date, followed by a question mark should be provided.

The character X may be used in place of one or more rightmost digits to indicate that the value of that digit is unspecified. Approximate date may be specified with tilde (“~”), uncertain and approximate date with percent character (“%”).

If no date can be given, the Latin phrase “s. a.”, English phrase “no date” (or “n. d.”), or an equivalent in the language of the publication may be supplied.

====== Date ranges

Date ranges should be created using the Unicode “hyphen-minus” as the separator character. Open ranges are acceptable.

If the date range has to be machine readable, it may be expressed as specified in ISO 8601. The standard uses solidus (“/”) as the separator character in ranges.

===== Date of publication

The year (and, if necessary, full date or date and time) on which the cited information resource was published should be given.

In a reference to the whole or a limited run of any item issued in parts over a period of years, the years of publication of the first part issued (which is not necessarily numerically the first part) and the part last issued should be given.

If the run is in progress, the year of the first item should be provided, followed by a hyphen-minus. The numeration and pagination (see [numeration]), if any, should also be given.

===== Date of citation

The full date (and, if necessary, time) on which the cited information resource was viewed should be given if:

The date of citation should be preceded by an appropriate term such as “viewed” and “accessed” (for human and machine-readable information resources, respectively) or equivalent terms in the language of the publication.

The date the cited resource was viewed should follow the link used. Even a single citation may contain several links to different copies or versions of the cited information resource, and it may be important to indicate when the functionality of these links was checked.

<date type="accessed"><on>2016-09-03</on></date>

===== Surrogate dates

In a reference to a reprint, facsimile, digital surrogate or other copy of the original information resource, the date of publication of that edition or, for a copy, the date of the original, should be given, along with the date of reprinting or copying.

===== Incorrect dates

If the date given on the cited information resource is known to be incorrect, the correct year should also be supplied in brackets after the date in the cited resource.

If the date on the cited information resource is known to be different from the actual publication date, both dates may be given; the actual date in brackets after the date in the cited resource.

=== Production information

==== Roles

===== General

The organizations or people responsible are likely to be variously described in different kinds of resources. The order of preference should be:

The publisher is a subclass of creator (Clause 8.2). Of the classes of creator that can be used as the publisher, “publisher or production company” and “printer or manufacturer” have bibitem/contributor/role@type = "publisher"; “distributor or issuing body” and “sponsoring body” have bibitem/contributor/role@type = "distributor". ISO 690 allows that distributors, issuers and sponsors can be named in addition to publishers.

===== Publisher

The organization or person shown most prominently in the cited information resource (see Clause 6, Paragraph 1) as responsible for the production of the resource should be given as publisher.

Publishers’ names may be abbreviated by omitting details not essential for identification.

A public identity identifier (ISNI or other) may be added after the publisher’s name, preceded by the identifier type. The identifier should be used if the name alone does not uniquely identify the publisher or if the publisher has changed name.

If a publisher is unknown, an indication such as “publisher not known”, or an equivalent abbreviation such as the Latin “s.n.” may be provided.

===== Multiple roles

If the names of two or more organizations appear equally prominently in the same role, only one need to be given; the other names may be omitted if they do not provide added value.

===== Distributor, issuing body or online host

The name of the distributor, issuing body, or online host should be given in the citation if appropriate and known.

Any restrictions on access to a resource imposed by an online host (e.g. geographical restrictions) should be indicated in bibitem/note.

A well-known acronym may be used, and a translation of the name may be given.

If the online host is different than the publisher, both should be given.

If two copies of the information resource have been used, both should be cited if it is not known whether the copies are technically identical. If they are different or if they have different access restrictions, both shall be cited.

Online hosts may have technical requirements which have an impact on the usage of information resources on their sites. Site specific hardware and software requirements should not be included in references, since such requirements do change often.

If an online host limits access to information resources permanently on e.g., geographical basis, the access barrier should be indicated.

===== Printer or manufacturer

The name of the printer and manufacturer, if applicable and known, should be provided in the citation.

===== Sponsor

Sponsors may have many roles, including funder, contributor, distributor or online host.

The name and, if appropriate and known, the role of a sponsoring body may be given after the publisher’s information.

If the publisher is also a sponsor, sponsorship information can be shown with the publisher.

A publication that is published on behalf of another entity can be described after the publisher.

==== Place

===== General

The place of production should be given as it appears most prominently in the cited information resource. If the place is known but not mentioned in the cited resource, it may be supplied.

For well-known places, the place name alone may be given. If there is another, less well-known place with the same name or if the place is less known, one or more qualifiers should be added (e.g., county, department, state, province, country) to the place name to avoid confusion and to aid correct localization.

Strictly speaking the place of production is an attribute of the publisher, and it can in fact be modelled as bibitem/contributor[role@type = "publisher"]/organization/address/city. However, it is modelled as a top-level attribute of the bibliographic item to allow the place to be extracted by consumers of the serialisation more readily, to allow multiple locations to be associated with the publisher, and to allow only one of the places of the publisher to be associated with the production of the item.

A URI in a geographical registry may optionally be given as place/@uri. A region within which the place is located may be given as place/@region, for disambiguation purposes; using a ISO 3166 code for a country or subnational region is recommended.

<bibitem type="book">
  <title>Roman Jakobson and beyond</title>
  <date type="published"><on>1984</on></date>
  <contributor>
    <role type="author"/>
    <person>
      <name>
        <surname>Sangster</surname>
        <initial>R. B.</initial>
      </name>
    </person>
  </contributor>
  <contributor>
    <role type="publisher"/>
    <organization>
      <name>Mouton</name>
    </organization>
  </contributor>
  <place>Berlin</place>
  <place>New York</place>
  <place>The Hague</place>
</bibitem>

<place uri="https://en.wikipedia.org/wiki/London,_Ontario" region="CA-ON">London (Ontario)</place>

===== Place codes

Names of countries and their subdivisions may be encoded in accordance with ISO 3166-1 and ISO 3166-2.

===== Place identifiers

An identifier may be added after the place name. The identifier may be used instead of a qualifier if the name alone does not uniquely identify the place.

===== Multiple places

If two or more place names appear equally prominently in association with one publisher, distributor, producer, etc., all names after the first in the cited information resource may be omitted.

===== Unknown place

If a publisher is given and no place is known for them, an indication such as “place not known” or a similar phrase in the language of the publication, or an equivalent abbreviation such as the Latin “s. l.” or the English “n.p.” may be provided.

=== Numeration and pagination

==== General

The components of the cited information resource should be referred in the terms used in the resource, their order following the principle that the larger precedes the smaller.

Components of an item are modelled under the bibitem/extent element as one or more “localities”; these consist of a locality type (bibitem/extent@type), a locality value (bibitem/extent/referenceFrom), and optionally a locality range endpoint (bibitem/extent/referenceTo). The extent gives the part of the host item being cited, if this is a contained item ([host-item]), such as a journal article or book chapter (e.g. “pp. 25-45”).

Some electronic formats such as PDF may retain the pagination of the original (printed) resource, but some other formats may not have the pagination. If so, logical components of the cited information resource should be used.

A hierarchical locality is expressed by repeating the extent element with the different applicable locality types; these should be given in hierarchical order. However localities in an extent may be complimentary instead (e.g. “xiii+179 pp” for prefatory and main pagination; “114pp + 3 plates” for plates outside the main page numeration).

Discontinuous ranges are modelled by repeating the extent element for the same locality type.

Extent includes the volume and issues of a journal, if the item is an article in the journal.

If the item is not a component of another item, then the extent gives the locality value for the entire work (e.g. page count: “[7 pp.]”). This is expressed by giving an empty bibitem/extent/referenceFrom, and populating only bibitem/extent/referenceTo (“[7 pp.]” = pp. 1-7).

If a locality is labelled conventionally with a range, but is in fact a single item (as often occurs with volumes and issues; e.g. issue 18–19 is in fact a single issue), the label should be associated with bibitem/extent/referenceFrom rather than being treated as a true range. However the rendering of the item will typically not be any different.

A part of a contained item may be cited, and this has posed difficulty for some citation schemes (e.g. citing a page within a journal article, which itself covers a page range: “Dedes, D. 1993. Ποίηματα του Μαυλανά Ρουμή [Poems by Mevlana Rumi]. Ta Istorika 10.18-19: 3-22. pp. 7-19”.) However, the model copes with this by separating the extent of a citation Clause 7 from the extent of a bibliograhic item, and the extent of a contained item from the extent of a host item. In this instance, “pp. 7-19” would be treated normally as part of the citation, not part of the bibliographic item.

<bibitem type="article">
  <title lang="en">Poems by Mevlana Rumi</title>
  <title type="original" lang="ell">Ποίηματα του Μαυλανά Ρουμή</title>
  <date type="published"><on>1993</on></date>
  <contributor>
    <role type="author"/>
    <person>
      <name>
        <surname>Dedes</surname>
        <forename>Dimitrios</forename>
      </name>
    </person>
  </contributor>
  <series>
    <title>Ta Istorika</title>
  </series>
  <extent type="volume">
    <referenceFrom>10</referenceFrom>
  </extent>
  <extent type="issue">
    <referenceFrom>18–19</referenceFrom>
  </extent>
  <extent type="page">
    <referenceFrom>3</referenceFrom>
    <referenceTo>22</referenceTo>
  </extent>
</bibitem>

<bibitem type="article">
  <title>Tiffany glass and other tales from the crypt</title>
  <date type="published"><on>1999-09-05</on></date>
  <contributor>
    <role type="author"/>
    <person>
      <name>
        <surname>Brown</surname>
        <initials>P. L.</initials>
      </name>
    </person>
  </contributor>
  <series>
    <title>The New York Times</title>
  </series>
  <extent type="page">
    <referenceFrom>1</referenceFrom>
  </extent>
  <extent type="page">
    <referenceFrom>5</referenceFrom>
  </extent>
</bibitem>

==== Part cited

The reference should identify the part of the information resource that is cited. For a component part, the number and designation of the smallest separately identified component should be given.

If the entire information resource is being cited, its extent may optionally be stated in brackets. The extent should be given, if the cited resource is large.

<bibitem type="incollection">
  <title>Object play in great apes: Studies in nature and captivity</title>
  <date type="published"><on>2005</on></date>
  <contributor>
    <role type="author"/>
    <person>
      <name>
        <surname>Ramsey</surname>
        <initials>J. K.</initials>
      </name>
    </person>
  </contributor>
  <contributor>
    <role type="author"/>
    <person>
      <name>
        <surname>McGrew</surname>
        <initials>W. C.</initials>
      </name>
    </person>
  </contributor>
  <relation type="includedIn">
    <bibitem>
      <title>The nature of play: Great apes and humans</title>
      <contributor>
        <role type="editor"/>
        <person>
          <name>
            <surname>Pellegrini</surname>
            <initials>A. D.</initials>
          </name>
        </person>
      </contributor>
      <contributor>
        <role type="editor"/>
        <person>
          <name>
            <surname>Smith</surname>
            <initials>P. K.</initials>
          </name>
        </person>
      </contributor>
      <contributor>
        <role type="publisher"/>
        <organization>
          <name>Guilford Press</name>
        </organization>
      </contributor>
      <place>New York, NY</place>
      <extent type="page">
        <referenceTo>308</referenceTo>
      </extent>
    </bibitem>
  </relation>
  <extent type="page">
    <referenceFrom>89</referenceFrom>
    <referenceTo>112</referenceTo>
  </extent>
</bibitem>

==== Omission of terms

Previous editions of this document allowed omission of the term “volume” and terms for smaller component parts of serial publications. Typographic means were then used to distinguish the volume number and the part number, with the volume number in bold type and the part number, if required, in parentheses.

In this edition, such practice is no longer allowed. Font styles should not be used to replace or indicate information, because individuals with limited sight or reading disabilities may not be able to distinguish between bold and regular font. Also, generally, a proprietary software, such as Microsoft Word is needed to view bold or italics. In preparation for machine-readable citations, it is important for citation data to be provided in a format that is easily recognizable by a machine, such as a plain text file.

<bibitem type="book">
  <title>Pluralism in the Soviet Union: Essays in Honour of H. Gordon Skilling</title>
  <date type="published"><on>1983</on></date>
  <contributor>
    <role type="editor"/>
    <person>
      <name>
        <surname>Solonom</surname>
        <forename>Susan</forename>
        <forename>Gross</forename>
      </name>
    </person>
  </contributor>
  <contributor>
    <role type="publisher"/>
    <organization>
      <name>St Martin's Press</name>
    </organization>
  </contributor>
  <note>$27.50</note>
  <place>New York</place>
  <extent type="page">
    <referenceTo>xiii</referenceTo>
  </extent>
  <extent type="page">
    <referenceTo>179</referenceTo>
  </extent>
</bibitem>

<bibitem type="book">
  <title>Geology and mineral deposits of Lander County, Nevada</title>
  <date type="published"><on>1977</on></date>
  <contributor>
    <role type="author"/>
    <person>
      <name>
        <surname>Stewart</surname>
        <forename>John</forename>
        <forename>H.</forename>
      </name>
    </person>
  </contributor>
  <contributor>
    <role type="author"/>
    <person>
      <name>
        <surname>McKee</surname>
        <forename>Edwin</forename>
        <forename>H.</forename>
      </name>
    </person>
  </contributor>
  <contributor>
    <role type="author"/>
    <person>
      <name>
        <surname>Stager</surname>
        <forename>Harold</forename>
        <forename>K.</forename>
      </name>
    </person>
  </contributor>
  <contributor>
    <role type="publisher"/>
    <organization>
      <name>University of Nevada</name>
    </organization>
  </contributor>
  <place>Reno</place>
  <series>
    <title>Nevada Bureau of Mines and Geology Bulletin</title>
    <number>88</number>
  </series>
  <extent type="page">
    <referenceTo>114</referenceTo>
  </extent>
  <extent type="plate">
    <referenceTo>3</referenceTo>
  </extent>
</bibitem>

=== Series title and number

==== General

Articles have their journal title modelled as the series title of the article item. However, the journal volume and issue should be modelled as part of the article item extent [numeration], rather than as part of the series.

Standards body identifiers for standards are modelled as series numbers.

<bibitem type="standard">
  <title>Information and documentation -- Guidelines for bibliographic references and citations to information resources</title>
  <contributor>
    <role type="publisher"/>
    <organization>
      <name>International Organization for Standardization</name>
    </organization>
  </contributor>
  <series>
    <title>ISO</title>
    <number>690</number>
  </series>
</bibitem>

The collection or fonds of archival material is modelled as a series.

==== Qualifiers for titles

If the title of a serial issued by a society or similar organization is insufficient to identify the cited information resource and the key title is not known, the organization’s name should be added as specified in [organization_names].

Organization and Place of Publication can be added to series titles for disambiguation. Organization in this instance is only modelled as a strings, rather than as a detailed object (cf. [organisation]). The formattedTitle element is used to enforce the formatting of the series title and its qualifiers.

The title may also by qualified by the place of publication or ISSN in order to support the identification of the serial.

<series>
  <title>Life</title>
  <place>Basel</place>
  <organization>MDPI</organization>
  <formattedTitle>_Life_ (Basel)</formattedTitle>
</series>

<series>
  <title>Life</title>
  <place>New York</place>
</series>

==== Key title and the abbreviated key title

Serials with the same title should be distinguished from each other with the key title. These titles are available from the ISSN Portal⁶.

Abbreviated key title is a specific title established by the ISSN network by replacing each significant word of a key title with the corresponding abbreviation from the List of Title Word Abbreviations⁷ managed by the ISO 3297 for ISO 4. Abbreviations are based on ISO 4, Documentation—Rules for the Abbreviation of Title Words and Titles of Publications and in accordance with the specific rules spelled out in the ISSN Manual.

The abbreviated key title should be used when it appears in the cited information resource (see Clause 6, Paragraph 1). The ISSN should be included with the abbreviated title (see [international_standard_identifiers]).

If there is any risk of ambiguity, the title shall be given in full.

==== Earlier titles

If the title of a cited serial has changed, earlier title of the serial should be given with the years when the title was in use.

The current title of a series is given with series@type as “main” (which is the default); alternate titles, including historical titles, are given with series@type as “alt”. Different time spans for historical titles are given with series/dateFrom and series/dateTo.

<series type="alt">
  <title>New Scientist</title>
  <dateFrom>1956</dateFrom>
  <dateTo>1956</dateTo>
</series>
<series type="alt">
  <title>New Scientist and Science Journal</title>
  <dateFrom>1971-01-21</dateFrom>
  <dateTo>1971-09-30</dateTo>
</series>
<series type="main">
  <title>New Scientist</title>
  <dateFrom>1971-09-30</dateFrom>
</series>

==== Regular conferences

If regular conferences are held with the same title, the date and place of the conference should be added, in the format used in the cited information resource.

==== Carried title

If the cited information resource also carries the title of a series of which it forms a numbered or unnumbered component, the series title and the numeration within that series may be included in the reference. The series title and number should be recorded as they appear on the cited resource.

The ISSN of the series may be a part of the citation.

A report number should be included.

==== New series

Journals may re-start their series number without changing the journal title. Then it is necessary to differentiate the “old series” and the “new series”, using “new series” or “n.s.” as appropriate.

If a series restarts numbering its volumes, that is typically indicated in citations by giving an ordinal number for the series run, given after the series name: 1st series, 2nd series, 3rd series. More commonly, there are only two series runs for a series, and the second run is indicated as “new series”, or the abbreviation “n.s.”.

<bibitem type="article">
  <title lang="en">Durkheim's Division of Labour in Society</title>
  <date type="published"><on>1966</on></date>
  <contributor>
    <role type="author"/>
    <person>
      <name>
        <surname>Barnes</surname>
        <initials>J. A.</initials>
      </name>
    </person>
  </contributor>
  <series>
    <title>Man</title>
    <number>1</number>
    <partnumber>2</partnumber>
    <run>new series</run>
  </series>
  <extent type="page">
    <referenceFrom>158</referenceFrom>
    <referenceTo>175</referenceTo>
  </extent>
</bibitem>

Subsequent re-starts followed by “new series” would be indicated by the ordinal number of the series preceded by the letters “ser.”, starting from “3rd ser.”

The series number should be recorded as it appears on the cited resource.

=== Identifiers

==== International standard identifiers

ISO 690 states that unique international standard identifiers must be included in the bibliography. In practice, identifiers are included at the discretion of the bibliographer: they are routinely included in bibliographic databases, but seldom in references within documents.

If the cited information resource has an international standard identifier (e.g., ISSN, ISBN, ISMN, ISRC, etc.) that uniquely identifies the resource, it may be included in the reference (see [key_title]) in a human readable form.

The namespace of an identifier is indicated through its type attribute. The scope of an identifier is introduced to disambiguate the identifier referent, when it is not obvious. So it is introduced where an identifier identifies only a component of the item (e.g. a document included in the item), or a superset of the item (e.g. a series). It can also be used if the identifier identifies a specific instantiation of the document as an entity; in terms of the Functional Requirements for Bibliographic Records Clause 8.2.1.1, Example 1, for example, an identifier may identify a work, an expression of the work (e.g. an edition), a manifestation of the work (e.g. a format), or an item of the manifestation (e.g. a single physical copy).

Neither the type nor the scope of the identifier have an associated controlled vocabulary, and one is unlikely to be derived. Identifier type should follow established practice in the domain; most well-known identifiers have a widely used short name or abbreviation.

Cited information resources can have both manifestation and work identifiers. These identifiers have different roles in information retrieval. For instance, a track published on a CD can have ISWC (International Standard Musical Work Code) assigned to the composition, and ISRC (International Standard Recording Code) assigned to a specific recording of the composition. With the latter it is possible to find different copies of the same recording in the Internet or on other carriers; with the former a user can find other recordings or interpretations of the same work, if no manifestations of the cited recording can be located.

Depending on how the information resource is cited, either the work identifier or the manifestation identifier may be the best choice. The former is a good choice if any manifestation of the work will do. Both identifiers may be included in the reference, if appropriate.

<bibitem type="journal">
  <title>International Journal of Islamic Thought</title>
  <docidentifier scope="digital" type="e-ISSN">2289-6023</docidentifier>
  <docidentifier scope="print" type="ISSN">2232-1314</docidentifier>
</bibitem>

If other metadata elements in the reference do not guarantee unique identification of the cited information resource (for instance, if there are several periodicals sharing the same title) the identifier of the cited information resource should be included.

If the cited information resource has more than one identifier (for instance, a book published in a series may have both ISSN and ISBN), only the one that most precisely identifies the resource used should be included in the reference.

If the cited information resource has both ISBN-10 and ISBN-13, only ISBN-13 should be included in the reference.

If the identifier in the cited information resource is cancelled or invalid, it may be included, preceded by term “Invalid” or “Cancelled” or an appropriate phrase in the language of the publication.

Invalid or cancelled identifiers should be so identified through the identifier scope: the cancellation of the identifier does not impact its namespace, but its connnection to a referent.

If the correct identifier is known, it should be used in the citation. The invalid or cancelled identifier may also be included in brackets, preceded by term “Invalid” or “Cancelled” or an appropriate phrase in the language of the publication.

Standards body identifiers for standards may be modelled as series numbers or as identifiers ([series_title_number]). We recommend that the canonical identifier issued for a standard by a standards body be encoded as an identifier; other identifiers assigned to the same document may be better identified with a series title, as a named and numbered grouping of documents.

Identifiers can be expressed as HTTP URIs may be so expressed, without changing the identifier type. A DOI for example may be expressed as either the DOI proper, or as a doi.org URI.

==== Persistent identifiers

If the cited information resource has a persistent identifier (PID) such as ARK, DOI name, Handle or URN, it shall be included in the reference.

Actionable PIDs should be expressed as hyperlinks (HTTP URIs). Un-actionable versions of persistent identifiers such as doi:10.3886/ICPSR31521.v1 or URN:NBN:fi:au:cn:39756A should not be used.

If the PID is present in the reference as a hyperlink, the network location (URL) of the cited information resource shall not be used.

If the cited Web resource has both a traditional identifier and a persistent identifier based on it (for instance ISBN and URN:ISBN or ISBN-A), both should be included in the reference.

If the cited resource is a component part, the traditional identifier of the host information resource should be included in addition to the persistent identifiers of the cited information resource. For instance, a journal article may have a DOI name, and the journal itself an ISSN.

<bibitem type="article">
  <title>International Journal of Islamic Thought</title>
  <docidentifier scope="journal" type="doi">10.24035/ijit</docidentifier>
  <docidentifier scope="article" type="doi">https://doi.org/10.24035/ijit.14.2018.001</docidentifier>
</bibitem>

If the cited information resource has more than one persistent identifier, they may all be included in the reference. Each PID facilitates access to a different copy of the cited resource, and these copies may have different access rights (for instance, one provides a link to a copy in a system maintained by the publisher, another to an open archive hosted by a university). If only one PID is included, it should provide a link to a copy that does not have access limitations.

Persistent identifiers often resolve to URLs of landing pages, which contain links to the actual resources. In such cases, it is sometimes not obvious if the PID identifies the cited resource or its landing page (or both), but such PIDs should nevertheless always be included in references, since they facilitate access to the cited resources.

=== Availability and location

==== Model

Unpublished items with a limited number of copies that are held at a repository should be referenced through bibitem/accessLocation, which gives the repository that the cited copy is held in, and the locator used by the repository. The repository and locator are not differentiated, and are treated as a single string. The bibitem/accessLocation element is also used for online locations of digital resources, where a single URL (bibitem/uri) is not sufficient, and either a navigation path, or an in-document object identifier is used.

An archival URI can be differentiated from an original URI for a resource, through using “archival” as the uri/@type. Alternatively, the archival copy and the original copy may be treated as related items (through an “instance” relation), although that is typically not necessary.

Persistent identifiers and other identifiers expressed as actionable URIs should still be represented as bibitem/docidentifier rather than bibitem/uri, so long as they are managed in a distinct namespace. That applies to such identifiers as DOI, ARK, Handle, ISSN, etc.

==== Physical location

===== General

If only a single or a limited number of copies of an information resource such as artwork or archival material are known to exist, or if a specific item is referenced, the place name shall be provided in a citation.

===== Place and repository

“At:” or an equivalent phrase in the language of the publication should be given before the place name.

The method of representation is given below, where {placeName} is the name of the place.

At: {placeName}

<bibitem type="booklet">
  <title>[Untitled]</title>
  <uri>http://papyri.info/hgv/26540/</uri>
  <uri>http://aquila.zaw.uni-heidelberg.de/hgv/26540</uri>
  <uri>https://www.trismegistos.org/text/26540</uri>
  <docidentifier type="papyri.info">P.Vind.Tand.25a</docidentifier>
  <docidentifier type="HGV">P.Vindob. Tandem 25 a</docidentifier>
  <docidentifier type="Trismegistos">26540</docidentifier>
  <accessLocation>P.Vindob.Gr. Inv. Nr. 12424 + 24718 + 28384.</accessLocation>
</bibitem>

<bibitem type="booklet">
  <title>[Untitled]</title>
  <uri>http://papyri.info/hgv/26540/</uri>
  <uri>http://aquila.zaw.uni-heidelberg.de/hgv/26540</uri>
  <uri>https://www.trismegistos.org/text/26540</uri>
  <docidentifier type="papyri.info">P.Vind.Tand.25a</docidentifier>
  <docidentifier type="HGV">P.Vindob. Tandem 25 a</docidentifier>
  <docidentifier type="Trismegistos">26540</docidentifier>
  <relation type="includedIn">
    <bibItem>
        <title>Fünfunddreißig Wiener Papyri (P. Vindob. Tandem)</title>
        <date type="published">1976</date>
        <contributor>
          <role type="editor"/>
          <person><name><completeName>Pieter Johannes Sijpesteijn</completeName></name></person>
        </contributor>
        <contributor>
          <role type="editor"/>
          <person><name><completeName>Klaas Anthony Worp</completeName></name></person>
        </contributor>
        <contributor>
          <role type="publisher"/>
          <organization><name>Terra</name></organization>
        </contributor>
        <series>
          <title>Studia Amstelodamensia ad epigraphicam, ius antiquum et papyrologicam pertinentia</title>
          <number>6</number>
        </series>
    </bibItem>
    <bibLocality type="part">
      <referenceFrom>25a</referenceFrom>
    </bibLocality>
  </relation>
  <accessLocation>National Library of Vienna. P.Vindob.Gr. Inv. Nr. 12424 + 24718 + 28384.</accessLocation>
</bibitem>

The language of the information resource shall be used in representing the place name.

The place name should be qualified if necessary (see [place_general]).

If the cited resource is held within a repository (within for instance, an item or a collection), the name of the repository that it belongs to and its locator (such as the call number, locator or identifier) in the form used by the repository.

It is possible to cite surrogates of information resources that no longer exist, such as temporary or destroyed work.

Examples of full references are provided below.

==== Network location and access

===== General

If the cited information resource is available in the Internet, a hyperlink such as HTTP URI, shall be provided to allow retrieval of the resource.

Internet addresses are often unreliable and therefore, URLs should be used with caution. Recommended practice is to use URIs based on persistent identifiers (PIDs), permalinks or a URI of an archived copy of the resource. If these approaches are not possible or practical, URL may be used, but with caution (see Example 249 below).

The elements of URI as specified in Clause 8.2.1.1, Example 1, URI Generic syntax (e.g., scheme, authority, path, query and fragment) should be transcribed with the same punctuation, upper-case and lower-case letters as given in the cited information resource.

In URIs, the scheme and host are case-insensitive and normally provided in lower case; all other URI components may be case-sensitive and should be treated as such. The name of the service may be added before the URI. Some services (for instance, Google Maps) apply internal URI syntaxes which differ from the URI syntax defined in Clause 8.2.1.1, Example 1. In such case, the syntax of the service may be used.

===== Network access

To indicate network access location of the cited information resource, a phrase equivalent to “Available from:”, in the language of the publication, should be given before the URI.

The following indicates the method of representation, where {URI} indicates expression of the URI:

Available from: {URI}

Name of the service (for instance, an institutional repository) holding the cited resource may be included. Below {URI} indicates expression of the URI and {service-name} the name of the service:

Available from {service-name}: {URI}

Specific features of the cited information resource should be provided, if they have an impact on its use:

{type} available from: {URI}

===== Related locations

If the cited information resource is for instance a program, it may be useful to include in the citation a link to additional information about the resource. A phrase “See also:” or equivalent in the language of the publication should be prefixed to a URI.

===== Archival access

Web archives make it possible to cite Web sites or individual pages that have been lost, and past versions of resources which are still available but in an edited form.

A link to an archived copy of the cited information resource may be added to the citation even if the cited information resource is static and there is a reason to believe that it will be available on the Web for a long term.

<bibitem type="website">
  <title>British Library Web site February 1997</title>
  <date type="copied">1997-02-18</date>
  <date type="accessed">2019-02-28</date>
  <uri type="original">http://www.bl.uk/</uri>
  <uri type="archival">https://web.archive.org/web/19970218190613/http://www.bl.uk/</uri>
  <contributor>
    <role type="author"/>
    <organization>
      <name>British Library</name>
    </organization>
  </contributor>
  <contributor>
    <role type="distributor"/>
    <organization>
      <name>archive.org</name>
    </organization>
  </contributor>
</bibitem>

<bibitem type="website">
  <title>British Library Web site February 1997</title>
  <uri type="original">http://www.bl.uk/</uri>
  <contributor>
    <role type="author"/>
    <organization>
      <name>British Library</name>
    </organization>
  </contributor>
  <relation type="instance">
    <bibitem type="website">
      <uri type="archival">https://web.archive.org/web/19970218190613/http://www.bl.uk/</uri>
      <date type="copied">1997-02-18</date>
      <date type="accessed">2019-02-28</date>
      <contributor>
        <role type="distributor">web archive</role>
        <organization>
          <name>archive.org</name>
        </organization>
      </contributor>
    </bibitem>
  </relation>
</bibitem>

===== Specific versions

If the cited Web page is dynamic and a specific version is used, an archived version of the resource shall be cited. If an accurate archived copy of the page does not exist, one shall be made using an archiving facility if possible, e.g. The Internet Archive.

The citation shall contain the name of the cited resource and the dates it has been used and archived.

===== Nonspecific versions

A link to an archived copy is not required if the cited information resource is dynamic, but no specific version of the resource is cited.

===== Representing lengthy locations

If the location information needs to be broken at the end of a line, the break should be made after a single or double solidus or a hyphen, but before other punctuation marks.

===== Providing navigation path instead of URI

If the cited information resource has long and/or complex location information, the navigation path to the resource may be provided instead of the full URI.

Navigation path may have 1-n levels, indicated in an appropriate manner.

<bibitem type="dataset">
  <title>Latest Weather Observations for Dumont D'Urville</title>
  <uri>http://www.bom.gov.au/fwo/IDT60803/IDT60803.89642.json</uri>
  <date type="accessed"><on>2018-03-10</on></date>
  <contributor>
    <role type="publisher"/>
    <organization>
      <name>Australian Government</name>
      <subdivision>Bureau of Meteorology</subdivision>
    </organization>
  </contributor>
  <accessLocation>http://www.bom.gov.au. Path: Antarctica: Antarctic Observations: Latest observations: Dumont D'Urville: JavaScript Object Notation format (JSON) in row-major order</accessLocation>
</bibitem>

===== Providing PID

HTTP URI based on the actionable persistent identifier (PID) assigned to the cited information resource shall be provided instead of the actual location (URL) of the resource. If the location changes, it may not be redirected to the new URL, whereas the PID will most likely be resolved to the new location or locations.

===== Outdated location information

Due to HTTP redirection, outdated URLs may still provide access to the cited information resource. However, all URLs should be up to date by the time citations are made, since URLs that require redirection are likely to be more short-lived than the current ones.

If the cited information resource has already disappeared from the Web or if the current version has already changed by the time the citation is written, the original URL and the retrieval date of the cited resource should be included, alongside the URI of the Web archive copy of the resource.

Non-operational URLs shall be preceded by a phrase “Originally available from:”, “Previously available from:” or equivalent phrases in the language of the publication.

If there is no Web archive copy of the cited Web resource, or if the existing copy or copies are not identical to the cited information resource, the Web resource shall not be used for reference, even if the author has a local copy of the resource. Proving the authenticity of such a copy may prove difficult.

==== Permanent links

Permanent link systems support issuing of URIs “intended to remain unchanged for many years into the future” (Clause 8.2.1.1, Example 1). They work by issue of persistent URL or pattern for persistent URLs, which redirects to the URL of the requested web resource. Widely used permanent link systems include PURL (Persistent Uniform Resource Locator, see Clause 8.2.1.1, Example 1) and Clause 8.2.1.1, Example 1.

URL shorteners (Clause 8.2.1.1, Example 1) (providing URL shortening and redirection services), which may be seen as permanent link systems, should not be used for referencing, because:

Functionality supported by these systems is simpler than in PID systems and unlike PIDs, permanent links are usually technology (HTTP) dependent.⁸

Permanent links may be used if:

If the permanent link system is discontinued due to, e.g., technical or financial issues, all URIs based on the system may fail at once. Therefore, references should contain also a link to an archived copy of the page if one exists, and the date/time the cited resource has been viewed.

It can be difficult to find out if the cited information resource does have a permanent link. It is usually not embedded in the resource itself, and the permalink is not be part of the URL to which the permalink is redirected.

==== Access restrictions

The cited information resource may be located behind a paywall or there may be legal restrictions that significantly restrict access the use of the resource. Such restrictions should be specified after the URI, with the date the restriction will end (if applicable). The name of the commercial access provider may be given before the URI.

A note on the access limitation may be given after the URI.

If the cited information resource is no longer available online and there is no appropriate Web archive URL to refer to (e.g. due to changing archive interface tools), the reference may be made to the archival metadata including the name of the archive, archiving date and the archive URL.

A full reference example provided below.

=== Surrogate

A digital surrogate of a work is serialised as a relation from the surrogate to the resource it embodies or reproduces (see [docrelation-types]).

If the cited information resource is a work of art, there may be many digital surrogates of it available in the Internet. They may differ significantly from one another, with respect to reproduction fidelity and quality.

If the cited information resource is a surrogate in Internet, HTTP URIs of the surrogates shall be included. If several surrogates of the same work have been used, they should all be included.

The name or nom de plume of the person or organization which uploaded the resource, date and the distributor should be included.

<bibitem type="audiovisual">
  <title>Violin concerto in D minor, Op. 47</title>
  <uri type="src">https://www.youtube.com/watch?v=YsbrRAgv1b4</uri>
  <date type="accessed"><on>2018-03-12</on></date>
  <relation type="reproductionOf">
    <bibitem type="audiovisual">
      <title>Violin concerto in D minor, Op. 47</title>
      <contributor>
        <role type="performer"/>
        <person><name><completename>Maxim Vengerov</completename></name></person>
      </contributor>
      <place>Chicago</place>
      <date type="published"><on>1996</on></date>
    </bibitem>
  </relation>
</bibitem>

For clarity, the phrase “digital surrogate” in the language of citation may be used to indicate the nature of the copy.

All surrogates used should be included in the reference.

Names of the online hosts and URIs of the surrogates should be provided. Specific features of surrogates such as size may be included when deemed relevant.

=== Relationship

==== General

A cited information resource is often related with other information resources.

For derivative works, the original information resource should be referenced within the reference to the derivative work.

The original work, if available, should be provided as an embedded reference before the date of citation in the following form, where relationLabel is the relation label of the relationship, and originalWorkReference is the reference to the original work.

{relationLabel}: {originalWorkReference}.

In order to minimize confusion, relations are considered the second type of data elements in Clause 8.1.1, so they can be placed accordingly.

An embedded reference to the original work is serialised as relation with the target item in relation/bibitem, the kind of relationship in relation/@type (the vocabulary of [docrelation-types]), and, for a part-whole relationship, the extent in relation/locality.

<bibitem type="book">
  <title>The Annotated Alice: The Definitive Edition</title>
  <contributor>
    <role type="editor"/>
    <person><name><completename>Martin Gardner</completename></name></person>
  </contributor>
  <relation type="annotationOf">
    <bibitem type="book">
      <title>Alice in Wonderland</title>
      <contributor>
        <role type="author"/>
        <person><name><completename>Lewis Carroll</completename></name></person>
      </contributor>
    </bibitem>
  </relation>
</bibitem>

==== Model

The vocabulary of relation types is given in [docrelation-types].

==== Translation

Translations are expressions of the original (translated) work, and are usually indexed under the original author’s name. The translator should be considered a subsidiary creator with the role of “translator” or its abbreviation (see [creator_roles]).

If the translated information resource is an exact counterpart of the original information resource, the source and destination languages shall be included if the original and translated title do not clearly indicate them.

The phrase “Translated from …​ to …​” or its equivalent in the language of the publication should be shown as an attribute of the cited information resource (see Clause 8.1.1).

If the cited information resource has been translated to the language of the publication, the destination language may be omitted.

Both the source and destination language may be omitted if the titles indicate them.

A reference to the original work should be included in the citation reference as a data element if the translation has been made via an intermediate language. The phrase “Translation of:” or equivalent in the language of the publication should be used as the relation label to the translated expression. The phrase “Original work:” should be used to indicate the source.

Information about the original work or the manifestation used as the source may be included even if there is no intermediate language.

If it is uncertain on what original work, expression or manifestation the translation is based on, the source shall not be mentioned in the reference.

A translation is serialised as relation/@type = "translatedFrom" with the original work as the target bibitem, and its inverse as hasTranslation.

<bibitem type="book">
  <title>The Brothers Karamazov</title>
  <title type="original" language="ru" script="Cyrl">Братья Карамазовы</title>
  <contributor>
    <role type="author"/>
    <person><name><completename>F. Dostoevsky</completename></name></person>
  </contributor>
  <contributor>
    <role type="translator"/>
    <person><name><completename>C. Garnett</completename></name></person>
  </contributor>
  <relation type="translatedFrom">
    <bibitem type="book">
      <title language="ru" script="Cyrl">Братья Карамазовы</title>
    </bibitem>
  </relation>
</bibitem>

==== Commentary

Commentaries are considered expressions instead of new work. They should be indexed under the original author’s name.

A reference to the original work, if available, should be inserted to the citation reference (see Clause 8.1.1) with the relation label “Commentary on:” or equivalent.

==== Annotations

Annotations are considered expressions instead of new works. They are usually marketed under the original author’s name.

A reference to the original work, if available, should be inserted to the citation reference (see Clause 8.1.1) with the relation label “Annotation on:” or equivalent.

==== Arranger

Arrangements are considered expression instead of new work, similar to translation. They are usually marketed under the original author’s name.

The reference should indicate the arranger and purpose of arrangement.

The arranger should be considered a subsidiary creator with the role of “arranger” or its abbreviation (see [creator_roles]).

The phrase “Arranged for {purpose}” (where “purpose” is the purpose of arrangement) or its equivalent should be shown as an attribute of the cited information resource (see Clause 8.1.1).

==== Abridgement

Abridgements are treated as expressions and not original works. They are usually marketed under the original author’s name.

The person who made the abridgement should be considered a subsidiary creator with the role of “adapter” or its abbreviation (see [creator_roles]).

If a reference to the original work is available, it should be inserted in the citation reference as a data element, with the original reference considered as a relation with the current (see Clause 8.1.1).

The phrase “Abridgement of:” or equivalent should be used as the relation label.

Otherwise, the label “abridgement” should be provided immediately after the title to indicate it is an abridgement of the original.

Translations may be abridged as well. If such translation is cited, the reference should specify differences using the terminology of the cited information resource, translated to the language of the publication.

==== Reviews and critiques

Reviews are new works, indexed under the reviewer’s name.

The phrase “Review of:” or its equivalent may be used to reference the work reviewed.

The reviewer is considered the most prominent creator for a review. The original reference should also be given if available as a relation (see Clause 8.1.1).

The phrase “Review of:” or equivalent should be used as the relation label.

In some cases, where the title already provides a reference to the original work, the embedded reference to the original work may be omitted.

=== Relation types

bibitem/relation/@type gives the base class of the relation between two bibliographic items.

The base class of relation types is taken from ISO 690, and represents generic bibliographical requirements, particularly inclusion in a host item ([host-item]: includedIn, includes) and translation ([relation-translation]: translatedFrom, hasTranslation). The class has been expanded substantially to deal with the requirements of standards documents.

The complete vocabulary, with definitions, is maintained in the relaton-models repository as the DocumentRelationType enumeration; it is reproduced here in the model order.

=== Other elements

==== General

Additional categories of information that may be included are given below. When such information is included in a reference, it should comply with the guidelines provided.

==== Classification

Classification codes may be included, if they have been recorded in the cited information resource. The classification scheme should be indicated if a code is provided.

The classification scheme is given in classification/@type.

<bibitem type="book">
  <title>Canada Remembers the Korean War</title>
  <docidentifier type="ISBN">0662674979</docidentifier>
  <date type="published"><on>2003</on></date>
  <contributor>
    <role type="author"/>
    <person>
      <name>
        <surname>Giesler</surname>
        <forename>Patricia</forename>
      </name>
    </person>
  </contributor>
  <contributor>
    <role type="publisher"/>
    <organization>
      <name>Veterans Affairs Canada</name>
    </organization>
  </contributor>
  <place>Charlottetown, P.E.I.</place>
  <classification type="Dewey">971.06 GIE 2003</classification>
</bibitem>

==== Keywords

Keywords associated with a bibliographic item may be given as plain strings, or as terms from controlled vocabularies (with the vocabulary identifier and term code). Taxonomic names may also be given as a taxon hierarchy.

<keyword>Homo sapiens</keyword>

<keyword>
  <vocab>Homo sapiens</vocab>
  <vocabid type="wikidata" uri="https://www.wikidata.org/wiki/Q15978631">
    <code>Q15978631</code>
    <term>Homo sapiens</term>
  </vocabid>
  <vocabid type="National Biodiversity Network">
    <code>NHMSYS0000376773</code>
  </vocabid>
</keyword>

<keyword>
  <taxon>Hominidae</taxon>
  <taxon>Homininae</taxon>
  <taxon>Hominini</taxon>
  <taxon>Hominina</taxon>
  <taxon>Homo</taxon>
  <taxon>Homo sapiens</taxon>
  <vocabid type="wikispecies"><term>Homo_sapiens</term></vocabid>
</keyword>

==== Size

The size of a printed document may be included in a reference. It may, if appropriate, be given as:

If the printed document cited is exceptionally large, the size should be specified.

==== File size

The file size of a cited digital information resource may be given after the URI of the resource. If the file is exceptionally large, the size should be specified.

==== Price

Information about price may be given, as quoted by the publisher.

Price is marked up as a distinct element, which contains the currency code, represented in ISO 4217. The price should be treated as nominal, rather than capturing all possible pricings at a given time.

Availability information for a bibliographic item is treated as a note. This also applies to the availability of an online resource, and any access limitations, but not to licensing, which is encoded separately.

Price and format ([formats]) availability may be given together.

<bibitem type="book">
  <title>Pluralism in the Soviet Union: Essays in Honour of H. Gordon Skilling</title>
  <date type="published"><on>1983</on></date>
  <contributor>
    <role type="editor"/>
    <person>
      <name>
        <surname>Solonom</surname>
        <forename>Susan</forename>
        <forename>Gross</forename>
      </name>
    </person>
  </contributor>
  <contributor>
    <role type="publisher"/>
    <organization>
      <name>St Martin's Press</name>
    </organization>
  </contributor>
  <note>Available on request to the author</note>
  <place>New York</place>
  <price currency="USD">27.50</price>
  <extent type="page">
    <referenceFrom>xiii</referenceFrom>
  </extent>
  <extent type="page">
    <referenceFrom>179</referenceFrom>
  </extent>
</bibitem>

==== Registered trademark

A registered trademark may be denoted by the symbol “®” next to the trademarked phrase(s) or symbol(s).

==== Rights metadata

Copyright status of the information resource may be provided, if known.

Where available, URIs should be used to identify licenses unambiguously. If a URI is not available, a commonly accepted abbreviation or short name of the license should be used.

Copyright is privileged with a separate element, incorporating copyright date and owner.

If it is certain that no exclusive intellectual property rights apply to the cited information resource, e.g., it is in the public domain or is not subject to copyright, this information may be included in the reference. The phrase “Public domain” or its equivalent in the language of the publication should be used.

Materials may enter the public domain in one country sooner than they may in another. A work marked to be in the public domain in a jurisdiction may still be under copyright protection in another jurisdiction. Therefore, the jurisdiction where the cited information resource is in the public domain should be indicated whenever necessary.

Some created works are automatically placed in the public domain since they are not copyrightable. The jurisdiction where the cited information resource where this condition applies should be indicated.

If intellectual property rights apply, the copyright date may be cited, preceded by the symbol “©” or “cop”. Alternatively, the English word “copyright” or its equivalent in the language of the citation may be used. If the copyright date is different from that of the publication date, both may be given.

If intellectual property rights apply but there is a well-known license which allows the usage, the acronym of the license should be provided with the version number (if any). Language of the license may be included as the ISO 639-1 code. The acronym should be preceded by the English word “license” or its equivalent in the language of the citation.

Example references are provided below.

==== Provenance and authenticity

The scope of provenance information varies depending on the information resource described. Traditionally, it has been limited to a record of ownership of a work of art, but provenance information may also describe the historical context of the data and its origins, including the workflows and applications used to generate the research data.

If the cited information resource is a Web document, the citation may contain a checksum with which a user can make sure that the document she has retrieved is the one cited.

If the cited resource consists of multiple files, checksums should be calculated for all of them.

Notes on bibliographical provenance, and checksums for digital resources, are both given as bibliographic notes.

Checksum algorithm should precede the checksum value. A standardized algorithm such as SHA3-256 (Clause 8.2.1.1, Example 1) should be used.

An example reference is provided below.

===== Provenance of reference information

Information in a reference typically comes from the publisher of a resource, and is included in the resource itself, as described in ISO 690, Clause 4.1.2. ISO 690, Clause 4.1.2 permits information to be supplied by other parties, and differentiated by including it in brackets. This can include both missing information (e.g. “[Untitled]”), and corrections (e.g. “1959 [i.e. 1995]”).

The party supplying emendations to reference information is identified in ISO 690, Clause 4.1.2 as the citer of the reference. However, the citer should be differentiated from the bibliographer, in the case of bibliographies as consumable resources (e.g. as bibliographic databases):

The bibliographer and the publisher in the contemporary bibliography universe are more active parties than in the traditional model, which relies exclusively on citer discretion. Bibliographers and publishers are invested in asserting that they are sources of truth about bibliographic resources; and the bibliographies covered by any model of electronic exchange include references provided by bibliographers and publishers, in bibliographic databases—as well as the references consumed and adjusted by citers from bibliographic databases.

So the original reference as obtained from a bibliographic database may need to be differentiated from any adjustments made to the reference by a citer; and the citer adjustments in some contexts may need to be overridden.

If the serialisation of bibliographic items is to reflect such adjustments to content, it will need to indicate the provenance of bibliographic information, and allow multiple versions of the same information, with differing provenance. At the simplest level there will simply be two or more different versions of the reference serialisation, some representing the publisher or bibliographer’s source of truth, and some representing the citer’s adjustments (in brackets). Adjustments made by the bibliographer would also be represented in brackets; this is long-standing routine practice in library catalogues.

A more granular approach would be to permit multiple instances of any element in the reference model, differentiated by provenance: this could be done with a child element (e.g. an XML attribute), or with a nested container. If no provenance is indicated, the information is assumed to be unchanged from the source of truth. A renderer can then choose which alternative to render depending on local requirements:

<bibitem>
  <date><on>1959</on></date>
</bibitem>

<bibitem source="citer">
  <date><on>1959 [i.e. 1995]</on></date>
</bibitem>

<bibitem>
  <date><on>1959</on></date>
  <date source="citer"><on>1959 [i.e. 1995]</on></date>
</bibitem>

==== System requirements

In order to facilitate access to electronic resources, references may specify the requirements for accessing and rendering the cited information resources. In practice, providing this information is complicated for some information resource types. For instance, research data sets often require specific software tools and documentation of the content. In such cases, system requirements should be included in references since otherwise re-use of these resources may be difficult or impossible.

Content providers may impose different site-specific technical requirements to access the same information resource. For instance, a user may be required to have a Flash player and support JavaScript in one site, whereas another site may require HTML5 to access the same content. These provider specific system requirements should not be included in references, since the lifetime of such information is often short.

System requirements for programs are application specific and may be provided in a note. The note may include:

The wording supplied by the program itself or the related documentation should be used. To reduce ambiguity, the words “system requirements” or an equivalent phrase precede this information. A URI to a Web page giving additional information may be provided.

System requirements are technology dependent and therefore become outdated quickly (see Example 327). But even when the described system has become outdated, information about it may still be useful because the description will enable potential users of the cited information resource to have a general idea of emulation requirements (and choose migration strategy, if emulation is too complicated).

==== Restoration

If the cited information resource is a restored version of the original such as digitally remastered version of a film or a recording, restoration year should also be provided. If the resource has been significantly altered during restoration, or if it has been restored multiple times, restoration year is mandatory.

==== Other information

Other information relevant to the purposes of the particular reference may be included. Such information may include, for instance, links to the datasets the cited information resource is based on, or links to the documentation which enables the usage of the resource.

== Resource types

=== General

While ISO 690 does not prescribe a list of possible bibliographic types, there are categories specific to particular information resource categories (ISO 690, Clause 5), as well as rendering rules specific to information resource categories (e.g. ISO 690, Clause 5.5: series title appears before item title for broadcasts). For that reason, bibliographic items should indicate what bibliographic type they belong to.

The list maintains a distinction between the following resources, all of which are necessarily included in another resource:

The overloaded type “electronic resource” should be avoided where possible, particularly if the resource corresponds closely to a paper bibliographic type, such as “book” or “article”. The following types have been added, as specialisations of “electronic resource” with no print or physical counterpart:

The following types have been added, as specialisations of “electronic resource” with a physical but not a print counterpart:

Bibliographic types can overlap; for example much social media can be treated as webresources, and webresources are electronic resources; a Facebook status update can be treated as an alert, or as social media. However each bibliographic type is associated with a particular set of conventions around citation, so classifying an item as belonging to a given bibliographic type determines how it will be cited. Following the classification of citations in ISO 690, social_media takes priority over other types where it is applicable, particularly for publicly visible communications (such as status updates).

=== Monographs

==== Metadata elements

Table 1 shows the elements, in order, to be included in references to books and other separately issued monographs.

==== Simple monographs

A printed monograph, such as a book, may be referenced using typical monographic citation rules.

A digital copy of a monograph should be referred to with an online link, if the book is available in the Internet.

==== Composed of multiple volumes

Monographs that are composed of multiple volumes may be indicated so.

==== E-books

Edition, carrier type, media type and/or file format of the cited e-book should be specified, but in a form that does not become obsolete quickly. For instance, giving the precise version of the e-book format or reading device used should be avoided unless it is relevant from the usage point of view.

If the cited e-book does not have page numbers, in-text citation may use any of the following:

If the cited e-book has numbered chapters, sections, and paragraphs, they may be used.

==== Audiobooks

The narrator of the cited information resource should be included if mentioned in the publication. Duration of the audiobook may be specified either in ISO 8601 format or in a more human readable form.

In-text citation for an audiobook should specify the relevant section.

=== Monograph components

==== Metadata elements

Table 2 shows the metadata elements, in order, to be included in references to component parts within monographs.

==== Component parts of a monograph

If a component part of a monograph (e.g., an article within an encyclopaedia) is cited, information about the host information resource shall be provided along with locality information on the location of the cited information resource within the host information resource.

If the identifier and creator of the host information resource are known, they shall be provided to facilitate identification of the resource.

The locality of the cited component part of an information resource should be stated according to hierarchical navigation, in order to facilitate the reader to locate the cited component part.

Component parts of monographs presented on non-printed medium may be referred to in the same way.

=== Serials and their component parts

==== General

Continuing resources include serials and ongoing integrating resources such as web sites. Examples of their component parts include journal articles and web pages.

Serials have traditionally been published in successive issues which had numerical and/or chronological designations. Publication patterns of digital journals may differ from this; for instance, there may still be volumes and articles but not issues. Citation guidelines must take this diversity into account.

==== Metadata elements

===== Referencing an entire serial or entire issue of a serial

Table 3 shows the metadata elements, in order, to be included in references to serials.

===== Referencing a component part within a serial

Table 4 shows the elements, in order, to be included in references to articles or other component parts within a serial.