<xsd:element name="doi_batch"><xsd:annotation><xsd:documentation>Top level element for a metadata submission to Crossref. This element indicates the start and end of the XML file. The version number is fixed to the version of the schema. Be sure to set the name space attributes as shown above in order for the Xerces parser to process the instance correctly. For the purposes of parsing, you may also set xsi:schemaLocation to http://www.crossref.org/schema/4.x.x http://www.crossref.org /schema/4.x.x/crossref.xsd. A copy of the schema is located on the Crossref server at this URL and will remain constant for a given version of the schema. This location permits you to have a constant location for the schema for parsing without relying on a hardwired local directory on your development platform.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="head"/><xsd:element ref="body"/></xsd:sequence><xsd:attribute name="version" type="xsd:string" fixed="4.4.2"/></xsd:complexType></xsd:element>
<xsd:element name="head"><xsd:annotation><xsd:documentation>The container for information related to the DOI batch submission. This element uniquely identifies the batch deposit to Crossref and contains information that will be used as a reference in error messages sent by the MDDB.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="doi_batch_id"/><xsd:element ref="timestamp"/><xsd:element ref="depositor"/><xsd:element ref="registrant"/></xsd:sequence></xsd:complexType></xsd:element>
<xsd:element name="doi_batch_id"><xsd:annotation><xsd:documentation>Publisher generated ID that uniquely identifies the DOI submission batch. It will be used as a reference in error messages sent by the MDDB, and can be used for submission tracking. The publisher must ensure that this number is unique for every submission to Crossref.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="100"/><xsd:minLength value="4"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="timestamp" type="xsd:nonNegativeInteger"><xsd:annotation><xsd:documentation>Indicates version of a batch file instance or DOI. timestamp is used to uniquely identify batch files and DOI values when a DOI has been updated one or more times. timestamp is an integer representation of date and time that serves as a version number for the record that is being deposited. Because Crossref uses it as a version number, the format need not follow any public standard and therefore the publisher can determine the internal format. The schema format is a double of at least 64 bits, insuring that a fully qualified date/time stamp of 19 digits can be submitted. When depositing data, Crossref will check to see if a DOI has already been deposited for the specific doi value. If the newer data carries a time stamp value that is equal to or greater than the old data based on a strict numeric comparison, the new data will replace the old data. If the new data value is less than the old data value, the new data will not replace the old data. timestamp is optional in doi_data and required in head. The value from the head instance timestamp will be used for all instances of doi_data that do not include a timestamp element.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="depositor"><xsd:annotation><xsd:documentation>Information about the organization submitting DOI metadata to Crossref</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="depositor_name"/><xsd:element ref="email_address"/></xsd:sequence></xsd:complexType></xsd:element>
<xsd:element name="depositor_name"><xsd:annotation><xsd:documentation>Name of the organization registering the DOIs. The name placed in this element should match the name under which a depositing organization has registered with Crossref.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="130"/><xsd:minLength value="1"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="email_address"><xsd:annotation><xsd:documentation>e-mail address to which batch success and/or error messages are sent. It is recommended that this address be unique to a position within the organization submitting data (e.g. "doi@...") rather than unique to a person. In this way, the alias for delivery of this mail can be changed as responsibility for submission of DOI data within the organization changes from one person to another.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="200"/><xsd:minLength value="6"/><xsd:pattern value="[\p{L}\p{N}!/+\-_]+(\.[\p{L}\p{N}!/+\-_]+)*@[\p{L}\p{N}!/+\-_]+(\.[\p{L}_-]+)+"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="registrant"><xsd:annotation><xsd:documentation>The organization that owns the information being registered.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="255"/><xsd:minLength value="1"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="body"><xsd:annotation><xsd:documentation>The container for the main body of a DOI record submission. The body contains a set of journal, book, conference proceedings or stand alone component records. It is not possible to mix genres within a single DOI submission. It is possible to include records for multiple journals, books, conferences, or stand alone components in a single submission.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:choice><xsd:element ref="journal" maxOccurs="unbounded"/><xsd:element ref="book" maxOccurs="unbounded"/><xsd:element ref="conference" maxOccurs="unbounded"/><xsd:element ref="sa_component" maxOccurs="unbounded"/><xsd:element ref="dissertation" maxOccurs="unbounded"/><xsd:element ref="report-paper" maxOccurs="unbounded"/><xsd:element ref="standard" maxOccurs="unbounded"/><xsd:element ref="database" maxOccurs="unbounded"/><xsd:element ref="peer_review" maxOccurs="unbounded"/><xsd:element ref="pending_publication" maxOccurs="unbounded"/><xsd:element ref="posted_content" maxOccurs="unbounded"/></xsd:choice></xsd:complexType></xsd:element>
<xsd:element name="journal"><xsd:annotation><xsd:documentation>The container for all information about a single journal and the articles being registered within the journal. journal is the core container for information about a single journal and articles submitted for registration from that journal. Within a journal instance, you may register articles from a single issue, detailed in journal_issue. If you want to register items from more than one issue, you must use multiple journal instances, which can be done within a single batch submission. If you have articles that have not been assigned to an issue, you may register them within a single journal instance. In this case, do not include a journal_issue. You may chose to submit only top level journal_metadata and journal_issue metadata for any journal or issue, allowing you to register DOIs for an entire journal, or any issue or volume within a journal.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="journal_metadata"/><xsd:element ref="journal_issue" minOccurs="0"/><xsd:element ref="journal_article" minOccurs="0" maxOccurs="unbounded"/></xsd:sequence></xsd:complexType></xsd:element>
<xsd:element name="full_title"><xsd:annotation><xsd:documentation>The full title by which a journal is commonly known or cited. full_title and abbrev_title must both be submitted even if they are identical. Note: In version 4.1.0 and later, this element is allowed up to 10 times to allow for a) journal name changes over time, b) translated journal names (e.g. the Japanese name and the English equivalent), and c) common author mis-spellings of a given journal name.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="255"/><xsd:minLength value="1"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="abbrev_title"><xsd:annotation><xsd:documentation>This element contains the common abbreviation or abbreviations used when citing this journal. It is preferred, but not required, that periods be included after abbreviated words within the title. full_title and abbrev_title must both be submitted, and they can be identical. If you do not know the abbreviated title for a specific journal, please supply the full title in the abbrev_title element. Note: In version 4.1.0 and later, this element is no longer required in journal_metadata because some journals do not have abbreviated journal names.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="150"/><xsd:minLength value="1"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="issn"><xsd:annotation><xsd:documentation>The ISSN assigned to an entity. The ISSN must consist of eight digits (where the last digit may be an X), or it must consist of eight digits in two groups of four with a hyphen between the two groups. Spaces or other delimiters should not be included in an ISSN. For more information, please see http://www.issn.org:8080/English/pub/getting- checking/checking or http://www.issn.org. The text "ISSN" should not be included in the issn element in Crossref submissions. Crossref validates all ISSNs supplied in deposits, only valid ISSNs will be accepted.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:simpleContent><xsd:extension base="issn_t"><xsd:attributeGroup ref="media_type.atts"/></xsd:extension></xsd:simpleContent></xsd:complexType></xsd:element>
<xsd:element name="coden"><xsd:annotation><xsd:documentation>The coden assigned to a journal or conference proceedings.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="6"/><xsd:minLength value="1"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="archive_locations"><xsd:annotation><xsd:documentation>Container element for archive.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element maxOccurs="unbounded" minOccurs="0" ref="archive"/></xsd:sequence></xsd:complexType></xsd:element>
<xsd:element name="archive"><xsd:annotation><xsd:documentation>Used to indicate the designated archiving organization(s) for an item. Values for the name attribute are CLOCKSS, LOCKSS Portico, KB, DWT (Deep Web Technologies), Internet Archive</xsd:documentation></xsd:annotation><xsd:complexType><xsd:attribute name="name" use="required"><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:enumeration value="CLOCKSS"/><xsd:enumeration value="LOCKSS"/><xsd:enumeration value="Portico"/><xsd:enumeration value="KB"/><xsd:enumeration value="Internet Archive"/><xsd:enumeration value="DWT"/></xsd:restriction></xsd:simpleType></xsd:attribute></xsd:complexType></xsd:element>
<xsd:element name="doi_data"><xsd:annotation><xsd:documentation>The container for elements related directly to a DOI. doi_data contains the doi, timestamp (version) and corresponding resource (URI) data for the doi. Cases of single-resolution (i.e. one DOI with a single corresponding URI) should be tagged with a doi/resource pair in doi_data. If additional resources are to be proved the <collection> element may also be used. The single URL provided in the <resource> is mandatory and serves as the single resolution target for the DOI. Note: A timestamp value placed inside doi_data will override any timestamp value placed in the <head> element.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="doi"/><xsd:element ref="timestamp" minOccurs="0"/><xsd:element ref="resource"/><xsd:element ref="collection" minOccurs="0" maxOccurs="unbounded"/></xsd:sequence></xsd:complexType></xsd:element>
<xsd:element name="doi"><xsd:annotation><xsd:documentation>DOI for an entity being registered with Crossref. In 2008 Crossref restricted DOI suffix characters to the following: "a-z", "A-Z", "0-9" and "-._;()/" Existing DOIs with suffix characters outside of the allowed set are still supported. For additional information on DOI syntax, see https://support.crossref.org/hc/en-us/articles/214669823</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="doi_t"/></xsd:simpleType></xsd:element>
<xsd:element name="resource"><xsd:annotation><xsd:documentation>The element that contains a URI associated with a DOI. URLs are referred to as resources in the 2.0 Crossref schema because they can be any valid URI. Cases of single-resolution (i.e. one DOI with a single corresponding URI) should be tagged with a doi/resource pair in doi_data. Only one resource is allowed per doi_data, the exception being resource elements within a collection element. Values for the "content_version" attribute are vor (version of record) and am (advance manuscript).</xsd:documentation></xsd:annotation><xsd:complexType><xsd:simpleContent><xsd:extension base="resource_t"><xsd:attributeGroup ref="mime_type.atts"/><xsd:attribute name="content_version"><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:enumeration value="vor"/><xsd:enumeration value="am"/></xsd:restriction></xsd:simpleType></xsd:attribute></xsd:extension></xsd:simpleContent></xsd:complexType></xsd:element>
<xsd:element name="collection"><xsd:annotation><xsd:documentation>A collection is a container for one or more items each holding a doi or a resource (URI) which is related to the DOI in the ancestor <doi_data> element. A collection must be qualified by a property attibute or the multi-resolution attribute. property attributes: list-based: uses an interim page and presents the list of items to the user (via Multiple Resolution) country-based: proxy picks destination based on the country code of the user's location crawler-based: identifies resource to be crawled by the specified crawlers. text-mining: identifies resource to be used for text and data mining unspecified: identifies resource with unspecified usage syndication: identifies resource to be used for syndication link-header: identifies resource to be used as an endpoint The multi-resolution attribute may be used to lock or unlock DOIs for multiple resolution.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="item" minOccurs="0" maxOccurs="unbounded"/></xsd:sequence><xsd:attribute name="property" use="required"><xsd:simpleType><xsd:restriction base="xsd:NMTOKEN"><xsd:enumeration value="list-based"/><xsd:enumeration value="country-based"/><xsd:enumeration value="crawler-based"/><xsd:enumeration value="text-mining"/><xsd:enumeration value="unspecified"/><xsd:enumeration value="syndication"/><xsd:enumeration value="link-header"/></xsd:restriction></xsd:simpleType></xsd:attribute><xsd:attribute name="multi-resolution"><xsd:simpleType><xsd:restriction base="xsd:NMTOKEN"><xsd:enumeration value="lock"/><xsd:enumeration value="unlock"/></xsd:restriction></xsd:simpleType></xsd:attribute></xsd:complexType></xsd:element>
<xsd:element name="journal_issue"><xsd:annotation><xsd:documentation>The container for metadata that defines a single issue of a journal. Special issue numbering information for a journal should be placed in special_numbering. You may register a DOI for an entire issue by including doi_data in journal_issue. The URI should resolve to the table of contents for the issue. contributors is included in journal_issue to allow inclusion of editors of special issues. This element allows linking from a reference such as: R.Glaser, L.Bond (Eds.), Testing: concepts and research, American Psychologist 36 (10-12) (1981) (special issue). You should not include contributors for the regular editors of regular issues.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="contributors" minOccurs="0"/><xsd:element ref="titles" minOccurs="0" maxOccurs="1"/><xsd:element ref="publication_date" maxOccurs="10"/><xsd:element ref="journal_volume" minOccurs="0"/><xsd:element ref="issue" minOccurs="0"/><xsd:element ref="special_numbering" minOccurs="0"><xsd:annotation><xsd:documentation>Issue level numbering for supplements or special issues. Text defining the type of special issue (e.g. "suppl") should be included in this element along with the number.</xsd:documentation></xsd:annotation></xsd:element><xsd:element ref="archive_locations" minOccurs="0" maxOccurs="1"/><xsd:element ref="doi_data" minOccurs="0"/></xsd:sequence></xsd:complexType></xsd:element>
<xsd:element name="contributors"><xsd:annotation><xsd:documentation>The container for all who contributed to authoring or editing an entity.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:choice maxOccurs="unbounded"><xsd:element ref="organization"/><xsd:element ref="person_name"/><xsd:element ref="anonymous"/></xsd:choice></xsd:sequence></xsd:complexType></xsd:element>
<xsd:element name="organization"><xsd:annotation><xsd:documentation>The name of an organization (as opposed to a person) that contributed to authoring an entity. If multiple organizations authored an entity, each one should be captured in a unique organization element. If an entity was authored by individuals in addition to one or more organizations, person_name and organization may be freely intermixed within contributors. contributor_role should be set, as appropriate, to author or editor. When a contributor translated a work, set contributor_role to "translator". "chair" should only be used for conference proceedings to indicate a conference chair.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:simpleContent><xsd:extension base="organization_t"><xsd:attributeGroup ref="contributor.atts"/></xsd:extension></xsd:simpleContent></xsd:complexType></xsd:element>
<xsd:element name="person_name"><xsd:annotation><xsd:documentation>The name of a person (as opposed to an organization) that contributed to authoring an entity. Authors with name suffixes should have the suffix captured in suffix, not in surname. Author prefixes such as "Dr.", "Prof.", or "President" should not be included in person_name or any other element. Author degrees (e.g. M.D., Ph.D.) also should not be included in Crossref submissions. contributor_role should be set, as appropriate, to author or editor. When a contributor translated a work, set contributor_role to "translator". "chair" should only be used for conference proceedings to indicate a conference chair.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="given_name" minOccurs="0"/><xsd:element ref="surname"/><xsd:element ref="suffix" minOccurs="0"/><xsd:element ref="affiliation" minOccurs="0" maxOccurs="5"/><xsd:element ref="ORCID" minOccurs="0" maxOccurs="1"/><xsd:element ref="alt-name" minOccurs="0"/></xsd:sequence><xsd:attributeGroup ref="contributor.atts"/></xsd:complexType></xsd:element>
<xsd:element name="given_name"><xsd:annotation><xsd:documentation>A contributor's given name. The given_name, combined with surname, forms the name of an author or editor. given_name may be submitted as either initials or a full name. Do not place given_name within the surname unless it is unclear how to distinguish the given name from the surname, as may be the case in non-Western names. Do not include titles such as "Dr.", "Prof.", or "President" in given_name. These titles should not be submitted to Crossref.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="60"/><xsd:minLength value="1"/><xsd:pattern value="[^\d\?]*"/><xsd:whiteSpace value="collapse"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="surname"><xsd:annotation><xsd:documentation>The surname of an author or editor. The surname, combined with given_name, forms the name of an author or editor. Whenever possible, the given name should not be included in the surname element. In cases where the given name is not clear, as may happen with non-Western names or some societies in which surnames are not distinguished, you may place the entire name in surname, e.g.:<surname>Leonardo da Vinci</surname>If an author is an organization, you should use organization, not surname. Suffixes should be tagged with suffix. Author degrees (e.g. M.D., Ph.D.) should not be included in Crossref submissions.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="60"/><xsd:minLength value="1"/><xsd:pattern value="[^\d\?]*[^\?\s]+[^\d]*"/><xsd:whiteSpace value="collapse"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="suffix"><xsd:annotation><xsd:documentation>The suffix of an author name, e.g. junior or senior. A name suffix, that typically denotes a generation distinction, is tagged with suffix. Author degrees (e.g. M.D., Ph.D.) should not be included in Crossref submissions.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="10"/><xsd:minLength value="1"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="affiliation"><xsd:annotation><xsd:documentation>The institution(s) with which a contributor is affiliated. This element may hold the name and location of an affiliation with which a contributor is affiliated. Please note the following points when using this element: 1. A contributor may have up to five affiliations. Each affiliation should be in a unique <affiliation> element. The following is correct: <affiliation>University of New Mexico</affiliation> <affiliation>Sandia National Laboratories</affiliation> The following is NOT correct <affiliation>University of New Mexico; Sandia National Laboratories</affiliation> 2. The name of the institution is required in this element. The location is optional. Both of the following are correct: <affiliation>Harvard University</affiliation> <affiliation>Harvard University, Cambridge, MA</affiliation> 3. Additional address information such as a URL or email address should NOT be deposited in this element 4. Visual linking indicators used in publication to connect authors with their affiliations such as footnote symbols or initials should NOT be included in the <affiliation> element 5. If you have only a single string that has the affiliation for multiple contributors to a work and that string is not broken out into the individual affliations for each author, please do NOT deposit the affilation information. This element is to be used only for affiliation information that is directly connected to the author with whom this information is included within the person_name element.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="512"/><xsd:minLength value="1"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="ORCID"><xsd:annotation><xsd:documentation>The ORCID for an author. The schema performs basic pattern validation, checksum validation is performed upon deposit via a system check.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:simpleContent><xsd:extension base="orcid_t"><xsd:attribute default="false" name="authenticated" type="xsd:boolean"/></xsd:extension></xsd:simpleContent></xsd:complexType></xsd:element>
<xsd:element name="titles"><xsd:annotation><xsd:documentation>A container for the title and original language title elements.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:sequence><xsd:element ref="title"/><xsd:element ref="subtitle" minOccurs="0"/></xsd:sequence><xsd:sequence minOccurs="0"><xsd:element ref="original_language_title"/><xsd:element ref="subtitle" minOccurs="0"/></xsd:sequence></xsd:sequence></xsd:complexType></xsd:element>
<xsd:element name="title"><xsd:annotation><xsd:documentation>The title of the entity being registered. When a title contains a subtitle, it is preferable to capture the subtitle portion in the subtitle element. Only minimal face markup is supported, see https://support.crossref.org/hc/en-us/articles/214532023</xsd:documentation></xsd:annotation><xsd:complexType mixed="true"><xsd:choice minOccurs="0" maxOccurs="unbounded"><xsd:group ref="face_markup"/></xsd:choice></xsd:complexType></xsd:element>
<xsd:element name="subtitle"><xsd:annotation><xsd:documentation>The sub-title portion of an entity title. When possible, it is better to tag a title and subtitle with separate elements. If this information is not available, it is acceptable to submit the title and subtitle all within the title element with punctuation (preferably a colon) used to separate the subtitle from the title. When a subtitle is tagged, the space and punctuation between the title and subtitle text should not be included. The following examples illustrate correct and incorrect tagging practices: Correct and optimal tagging:<title>The Human Brain</title><subtitle>A Handbook</subtitle>Correct but not optimal tagging:<title>The Human Brain: A Handbook</title>Incorrect:<title>The Human Brain:</title><subtitle>A Handbook</subtitle><title>The Human Brain</title><subtitle>: A Handbook</subtitle></xsd:documentation></xsd:annotation><xsd:complexType mixed="true"><xsd:choice minOccurs="0" maxOccurs="unbounded"><xsd:group ref="face_markup"/></xsd:choice></xsd:complexType></xsd:element>
<xsd:element name="original_language_title"><xsd:annotation><xsd:documentation>The title of an entity in its original language if the registration is for a translation of a work. When providing the original language of a title, you should set the language attribute.</xsd:documentation></xsd:annotation><xsd:complexType mixed="true"><xsd:choice minOccurs="0" maxOccurs="unbounded"><xsd:group ref="face_markup"/></xsd:choice><xsd:attributeGroup ref="language.atts"/></xsd:complexType></xsd:element>
<xsd:element name="publication_date"><xsd:annotation><xsd:documentation>The date of publication. In all cases, multiple dates are allowed to allow for different dates of publication for online and print versions. This element was previously called date, but was renamed publication_date to distinguish more clearly from conference_date.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:complexContent><xsd:extension base="date_t"/></xsd:complexContent></xsd:complexType></xsd:element>
<xsd:element name="month" type="xrefMonth"><xsd:annotation><xsd:documentation>Month of publication. The month must be expressed in numeric format rather spelling out the name (e.g.. submit "10", not "October"). The month must be expressed with a leading zero if it is less than 10 (e.g. submit "05", not "5"). When a journal issue has both an issue number and a season, the issue number should be placed in issue. If the month of publication is not known, the season should be placed in month as a two-digit value as follows: Season Value Spring 21 Summer 22 Autumn 23 Winter 24 First Quarter 31 Second Quarter 32 Third Quarter 33 Fourth Quarter 34 In cases when an issue covers multiple months, e.g. "March-April", include only the digits for the first month of the range.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="day" type="xrefDay"><xsd:annotation><xsd:documentation>Day of publication. The should must be expressed with a leading zero if it is less than 10 (e.g. submit "05", not "5").</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="journal_volume"><xsd:annotation><xsd:documentation>The container for the journal volume and DOI assigned to an entire journal volume. You may register a DOI for an entire volume by including doi_data in journal_volume.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="volume"/><xsd:element ref="publisher_item" minOccurs="0"/><xsd:element ref="archive_locations" minOccurs="0" maxOccurs="1"/><xsd:element ref="doi_data" minOccurs="0"/></xsd:sequence></xsd:complexType></xsd:element>
<xsd:element name="volume"><xsd:annotation><xsd:documentation>The volume number of a published journal, or the number of a printed volume for a book or conference proceedings. A journal volume is contained in the journal_volume element to allow for the assignment of a DOI to an entire journal volume. Do not include the words "Volume" or "vol." in this element. Data may be alpha, numeric or a combination. Roman numerals are acceptable.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="32"/><xsd:minLength value="1"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="publisher_item"><xsd:annotation><xsd:documentation>A container for item identification numbers set by a publisher. item_number within publisher_item may also be used to provide an article number when a first_page is not available or applicable. In certain cases it may be deemed in-appropriate to 'misuse' the first_page element to provide a value that has meaning in an on-line only publication and does not convey an form of page number. In these circumstances the attribute <item_number item_number_type="article-number"> will instruct the Crossref system to treat the value of item_number in the same manner as first_page. This value then becomes a critical part of the query process. If both <item_number item_number_type="article-number"> and first_page are present, first_page will take precedence.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="item_number" minOccurs="0" maxOccurs="3"/><xsd:element ref="identifier" minOccurs="0" maxOccurs="10"/></xsd:sequence></xsd:complexType></xsd:element>
<xsd:element name="item_number"><xsd:annotation><xsd:documentation>A publisher identifier that can be used to uniquely identify the entity being registered. This identifier is a publisher-assigned number that uniquely identifies the entity being registered. This element should be used for identifiers based on publisher internal standards. Use identifier for a publisher identifier that is based on a public standard such as PII or SICI. If the item_number and identifier are identical, there is no need to submit both. In this case, the preferred element to use is identifier. Data may be alpha, numeric or a combination. item_number has an optional attribute, item_number_type. It is assigned by the publisher to provide context for the data in item_number. If item_number contains only a publisher's tracking number, this attribute need not be supplied. If the item_number contains other data, this attribute can be used to define the content. For example, if a journal is published online (i.e. it has no page numbers), and each article on the table of contents is assigned a sequential number, this article number can be placed in item_number, and the item_number_type attribute can be set to "article_number". Although Crossref has not provided a set of enumerated types for this attribute, please check with Crossref before using this attribute to determine if a standard attribute has already been defined for your specific needs. If a dissertation DAI has been assigned, it should be deposited in the identifier element with the id_type attribute set to "dai". If an institution has its own numbering system, it should be deposited in item_number, and the item_number_type should be set to "institution" If the report number of an item follows Z39.23, the number should be deposited in the identifier element with the id_type attribute set to "Z39.23". If a report number uses its own numbering system, it should be deposited in the identifier element, and the id_type should be set to "report-number" The designation for a standard should be placed inside the identifier element with the id_type attribute set to "ISO-std-ref" or "std-designation" (more generic label)</xsd:documentation></xsd:annotation><xsd:complexType><xsd:simpleContent><xsd:extension base="item_number_t"><xsd:attribute name="item_number_type" type="xsd:string" use="optional"/></xsd:extension></xsd:simpleContent></xsd:complexType></xsd:element>
<xsd:element name="identifier"><xsd:annotation><xsd:documentation>A public standard identifier that can be used to uniquely identify the entity being registered. This identifier is a publisher-assigned number that uniquely identifies the entity being registered. This element should be used for identifiers based on public standards. Use item_number for a publisher identifier that is based on a publisher's internal systems rather than on a public standard. The supported standards are: PII - Publisher Item Identifier SICI - Serial Item and Contribution Identifier DOI - Digital Object Identifier</xsd:documentation></xsd:annotation><xsd:complexType><xsd:simpleContent><xsd:extension base="identifier_t"><xsd:attribute name="id_type" use="required"><xsd:simpleType><xsd:restriction base="xsd:NMTOKEN"><xsd:enumeration value="pii"/><xsd:enumeration value="sici"/><xsd:enumeration value="doi"/><xsd:enumeration value="dai"/><xsd:enumeration value="Z39.23"/><xsd:enumeration value="ISO-std-ref"/><xsd:enumeration value="std-designation"/><xsd:enumeration value="report-number"/><xsd:enumeration value="pmid"/><xsd:enumeration value="other"/></xsd:restriction></xsd:simpleType></xsd:attribute></xsd:extension></xsd:simpleContent></xsd:complexType></xsd:element>
<xsd:element name="issue"><xsd:annotation><xsd:documentation>The issue number in which an article is published. Only one issue name should be used for the issue. The issue number takes precedence over any other name. For example, if an issue has only a seasonal name, then the season should be listed in issue. However, if an issue has a number and a season, then only the number should be listed in issue, and the season should be placed in month (see the table in month, below, for proper encoding of the season) if the specific month of publication is not known. Do not include the words "issue", "No" or "number" in this element. When submitting DOIs for journal articles published online ahead of print, you should submit the issue number, when known, even if the pagination information for the entity is not yet known. Data may be alpha, numeric or a combination. Examples: 74(3):1999<journal_issue><publication_date media_type="print"><year>1999</year></publication_date><journal_volume><volume>74</volume></journal_volume><issue>3</issue></journal_issue>Volume 74, Spring 1999<journal_issue><publication_date media_type="print"><year>1999</year></publication_date><journal_volume><volume>74</volume></journal_volume><issue>Spring</issue></journal_issue>Volume 74, issue 3 Spring 1999<journal_issue><publication_date media_type="print"><month>21</month><year>1999</year></publication_date><journal_volume><volume>74</volume></journal_volume><issue>3</issue></journal_issue></xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="32"/><xsd:minLength value="1"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="special_numbering"><xsd:annotation><xsd:documentation>Issue level numbering for supplements or special issues. Text defining the type of special issue (e.g. "suppl") should be included in this element along with the number.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="15"/><xsd:minLength value="1"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="journal_article"><xsd:annotation><xsd:documentation>The container for all information about a single journal article. A journal article is required to have title and doi_data. All other information is optional. When registering items that do not have titles, use the appropriate heading from the journal section or table of contents (e.g. "Errata") in title. journal_article allows for multiple titles per entity. In some cases it may be helpful to submit multiple titles. For example, if an erratum carries title of the original article a nd the heading "Errata", both should be submitted by using two titles elements.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="titles" maxOccurs="20"/><xsd:element ref="contributors" minOccurs="0"/><xsd:element ref="jats:abstract" minOccurs="0" maxOccurs="unbounded"/><xsd:element ref="publication_date" maxOccurs="10"/><xsd:element ref="acceptance_date" minOccurs="0" maxOccurs="1"/><xsd:element ref="pages" minOccurs="0"/><xsd:element ref="publisher_item" minOccurs="0"/><xsd:choice><xsd:element ref="crossmark" minOccurs="0"/><xsd:sequence><xsd:element ref="fr:program" minOccurs="0" maxOccurs="1"/><xsd:element ref="ai:program" minOccurs="0" maxOccurs="1"/><xsd:element ref="ct:program" minOccurs="0" maxOccurs="1"/></xsd:sequence></xsd:choice><xsd:element ref="rel:program" minOccurs="0"/><xsd:element ref="archive_locations" minOccurs="0" maxOccurs="1"/><xsd:element ref="scn_policies" minOccurs="0" maxOccurs="1"/><!-- cs-3495 --><xsd:element ref="doi_data"/><xsd:element ref="citation_list" minOccurs="0"/><xsd:element ref="component_list" minOccurs="0"/></xsd:sequence><xsd:attributeGroup ref="publication_type.atts"/><xsd:attributeGroup ref="language.atts"/><xsd:attributeGroup ref="reference_distribution_opts.att"/></xsd:complexType></xsd:element>
<xsd:element name="acceptance_date"><xsd:annotation><xsd:documentation>The date a manuscript was accepted for publication.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:complexContent><xsd:extension base="date_t"/></xsd:complexContent></xsd:complexType></xsd:element>
<xsd:element name="pages"><xsd:annotation><xsd:documentation>The container for information about page ranges. When an entity has non-contiguous page information, you should capture the first page range in first_page and last_page. Any additional page information should be captured in other_pages. Punctuation is only allowed in other_pages. It should not appear in first_page and last_page. Page number letter prefixes or suffixes should be included. Roman numeral pages are permitted in both upper case and lower case. Data may be alpha, numeric or a combination.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="first_page"/><xsd:element ref="last_page" minOccurs="0"/><xsd:element ref="other_pages" minOccurs="0"/></xsd:sequence></xsd:complexType></xsd:element>
<xsd:element name="first_page"><xsd:annotation><xsd:documentation>First page number where an entity is located. Data may be alpha, numeric or a combination.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="32"/><xsd:minLength value="1"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="last_page"><xsd:annotation><xsd:documentation>The last page number of an entity. last_page should not be used when the last page number is the same as the first page number (i.e. when the entire entity fits on one page). Do not include punctuation for a page range in last_page. If the entity has non-contiguous paging, use last_page for the last page of the first range and place all other page information into other_pages. Data may be alpha, numeric or a combination.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="32"/><xsd:minLength value="1"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="other_pages"><xsd:annotation><xsd:documentation>Used to capture additional page information when items do not encompass contiguous page ranges. When an entity has non-contiguous page information, you should capture the first page range in first_page and last_page. Any additional page information should be captured in other_pages. You should include commas or hyphens to express discrete pages or page ranges. endash entities should be converted to ASCII hyphens. Spaces should not be included. Note that punctuation should never appear in first_page and last_page. Data may be alpha, numeric or a combination.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="100"/><xsd:minLength value="1"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="crossmark"><xsd:annotation><xsd:documentation>Container element for CrossMark data.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence minOccurs="0"><xsd:element ref="crossmark_version" minOccurs="0"/><xsd:element ref="crossmark_policy"/><xsd:element ref="crossmark_domains" minOccurs="0" maxOccurs="unbounded"/><xsd:element ref="crossmark_domain_exclusive" minOccurs="0"><xsd:annotation><xsd:documentation>Some publishers encourage broad third party hosting of the publisher's content. Other publishers do not. And still others vary their policy depending on whether a particular article has been published under an OA policy or not. This boolean flag allows the publisher to indicate whether the Crossmarked content will only legitimately be updated on the Crossmark domain (true) or whether the publisher encourages updating the content on other sites as well (false).</xsd:documentation></xsd:annotation></xsd:element><xsd:sequence minOccurs="0"><xsd:element ref="updates" minOccurs="0"/><xsd:element ref="custom_metadata" minOccurs="0"/></xsd:sequence></xsd:sequence></xsd:complexType></xsd:element>
<xsd:element name="crossmark_policy" type="doi_t"><xsd:annotation><xsd:documentation>A DOI which points to a publisher's CrossMark policy document. Publishers might have different policies for different publications.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="crossmark_domains"><xsd:annotation><xsd:documentation>Container element for crossmark_domain. A list of domains where the publisher maintains updates and corrections to their content. Minimally, one of these should include the Internet domain name of the publisher's web site(s), but the publisher might also decide to include 3rd party aggregators (e.g. Ebsco, IngentaConnect) or archives with which the publisher has agreements to update the content</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element maxOccurs="unbounded" ref="crossmark_domain"/></xsd:sequence></xsd:complexType></xsd:element>
<xsd:element name="crossmark_domain"><xsd:annotation><xsd:documentation>This should be a simple Internet domain name or subdomain name (e.g. www.psychoceramics.org or psychoceramics.org). It is used to identify when a referring URL is coming from a CrossMark domain. A "crossmark_domain" is made up of two subelements; a "domain" and a "filter". The domain is required but the filter is optional and is only needed for use in situations where content from multiple publishers/publications is on the same host with the same domain name (e.g. an aggregator) and one needs to use the referrer's URI "path" to further determine whether the content in a crossmark domain.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="domain"/><xsd:element minOccurs="0" ref="filter"/></xsd:sequence></xsd:complexType></xsd:element>
<xsd:element name="domain" type="cm_domain"><xsd:annotation><xsd:documentation>Required element. This should be a simple Internet domain name or subdomain name (e.g. www.psychoceramics.org or psychoceramics.org). It is used to identify when a referring URL is coming from a CrossMark domain.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="filter" type="xsd:string"><xsd:annotation><xsd:documentation>Optional element. The filter element is used to disambiguate content in situations where multiple publishers share the same host (e.g. when on an aggregated platform). It should contain a substring of the path that can be used to uniquely identify a publisher's or publication's content. For instance, using the string "alpsp" here would help the CrossMark system distinguish between ALPSP publications on the ingentaconnect host and other publications on the same host.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="updates"><xsd:annotation><xsd:documentation>Optional element. A document might provide updates (e.g. corrections, clarifications, retractions) to several other documents. When this is the case, the DOIs of the documents that are being *updated* should be listed here.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element maxOccurs="unbounded" ref="update"/></xsd:sequence></xsd:complexType></xsd:element>
Required attribute. The date of the update will bedisplayed in the CrossMark dialog and can help the researcher easilytell whther they are likley to have seen theupdate.
Required attribute. This attribute should be used tolist the update type. Allowed update types are:<ul><li>addendum</li><li>clarification</li><li>correction</li><li>corrigendum</li><li>erratum</li><li>expression_of_concern</li><li>new_edition</li><li>new_version</li><li>partial_retraction</li><li>removal</li><li>retraction</li><li>withdrawal</li></ul>
Source
<xsd:element name="update"><xsd:annotation><xsd:documentation>The DOI of the content being updated (e.g. corrected, retracted, etc.) In the CrossMark Terms and Conditions "updates" are defined as changes that are likely to "change the reader’s interpretation or crediting of the work." That is, *editorially significant* changes. "Updates" should not include minor changes to spelling, punctuation, formatting, etc. Attributes: label: Required attribute. This should be a human-readable version of the "type" attribute. This is what gets displayed in the CrossMark dialog when there is an update. type: Required attribute. This attribute should be used to give the machine-readable name of the update type. The human-readable version of the type should be but in the "label" attribute. There are many "types" of updates. "Corrections, "clarifications", "retractions" and "withdrawals" are just a few of the better-known types. For these common types we recommend you use the values "correction", "clarification", "retraction" and "withdrawal" respectively as per your editorial policy. However, different publishers sometimes have to support different, custom update types- for instance, "protocol amendments", "letters of concern", "comments", etc. The attribute supports custom types as well. date: The date of the update will be displayed in the CrossMark dialog and can help the researcher easily tell whther they are likley to have seen the update.</xsd:documentation></xsd:annotation><xsd:complexType mixed="true"><xsd:simpleContent><xsd:extension base="doi_t"><xsd:attribute name="type" use="required" type="cm_update_type"><xsd:annotation><xsd:documentation>Required attribute. This attribute should be used to list the update type. Allowed update types are:<ul><li>addendum</li><li>clarification</li><li>correction</li><li>corrigendum</li><li>erratum</li><li>expression_of_concern</li><li>new_edition</li><li>new_version</li><li>partial_retraction</li><li>removal</li><li>retraction</li><li>withdrawal</li></ul></xsd:documentation></xsd:annotation></xsd:attribute><xsd:attribute name="date" use="required" type="xsd:date"><xsd:annotation><xsd:documentation>Required attribute. The date of the update will be displayed in the CrossMark dialog and can help the researcher easily tell whther they are likley to have seen the update.</xsd:documentation></xsd:annotation></xsd:attribute></xsd:extension></xsd:simpleContent></xsd:complexType></xsd:element>
<xsd:element name="custom_metadata"><xsd:annotation><xsd:documentation>Optional element. Publishers are encouraged to provided any non-bibliographical metadata that they feel might help the researcher evaluate and make better use of the content that the Crossmark record refers to. For example, publishers might want to provide funding information, clinical trial numbers, information about the peer-review process or a summary of the publication history of the document.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:choice><xsd:sequence><xsd:element maxOccurs="unbounded" minOccurs="1" ref="assertion"/><xsd:element maxOccurs="1" ref="fr:program" minOccurs="0"/><xsd:element maxOccurs="1" ref="ai:program" minOccurs="0"/><xsd:element maxOccurs="1" ref="ct:program" minOccurs="0"/></xsd:sequence><xsd:sequence><xsd:element maxOccurs="1" ref="fr:program" minOccurs="1"/><xsd:element maxOccurs="1" ref="ai:program" minOccurs="0"/><xsd:element maxOccurs="1" ref="ct:program" minOccurs="0"/></xsd:sequence><xsd:sequence><xsd:element maxOccurs="1" ref="ai:program" minOccurs="1"/><xsd:element maxOccurs="1" ref="ct:program" minOccurs="0"/></xsd:sequence><xsd:element ref="ct:program" minOccurs="1" maxOccurs="1"/></xsd:choice></xsd:complexType></xsd:element>
Optional attribute. If the publisher wants to provide afurther explanation of what the particular "assertion" means, they can linkto such an explanation by providing an appropriate url on the "explanation"attribute.
Optional attribute. This is the human-readable form of the"group_name" attribute. This is what will be displayed in the group headingson the CrossMark metadata record dialog.
Optional attribute. Some assertions could be logically"grouped" together in the CrossMark dialog. For instance, if the publisheris recording several pieces of metadata related to funding sources (sourcename, percentage, grant number), they may want to make sure that these threeassertions are grouped next to each-other in the CrossMark dialog. Thegroup_name attribute is the machine-readable value that will be used forgrouping such assertions.
Optional attribute. This is the human-readable version of thename attribute which will be displayed in the CrossMark dialog. If thisattribute is missing, then the value of the assertion will *not* bedisplayed in the dialog. Publishers may want to "hide" assertions this wayin cases where the assertion value is too large or too complex to display inthe dialog, but where the assertion is nonetheless valuable enough toinclude in API queries and metadata dumps (e.g. detailed licensingterms)
Optional attribute. The publisher may want to control theorder in which assertions are displayed to the user in the CrossMark dialog.All assertions will be sorted by this element if it ispresent.
Source
<xsd:element name="assertion"><xsd:annotation><xsd:documentation>An assertion is a piece of custom, non-bibliographic metadata that the publisher is asserting about the content to which the CrossMark refers. assertion attributes: explanation: If the publisher wants to provide a further explanation of what the particular "assertion" means, they can link to such an explanation by providing an appropriate url on the "explanation" attribute. group_label: This is the human-readable form of the "group_name" attribute. This is what will be displayed in the group headings on the CrossMark metadata record dialog. group_name: Some assertions could be logically "grouped" together in the CrossMark dialog. For instance, if the publisher is recording several pieces of metadata related to funding sources (source name, percentage, grant number), they may want to make sure that these three assertions are grouped next to each-other in the CrossMark dialog. The group_name attribute is the machine-readable value that will be used for grouping such assertions. label: This is the human-readable version of the name attribute which will be displayed in the CrossMark dialog. If this attribute is missing, then the value of the assertion will *not* be displayed in the dialog. Publishers may want to "hide" assertions this way in cases where the assertion value is too large or too complex to display in the dialog, but where the assertion is nonetheless valuable enough to include in API queries and metadata dumps (e.g. detailed licensing terms). name: This is the machine-readable name of the assertion. Use the "label" attribute to provide a human-readable version of the name. order: The publisher may want to control the order in which assertions are displayed to the user in the CrossMark dialog. All assertions will be sorted by this element if it is present.</xsd:documentation></xsd:annotation><xsd:complexType mixed="true"><xsd:choice minOccurs="0" maxOccurs="unbounded"><xsd:group ref="face_markup"/></xsd:choice><xsd:attribute name="explanation" type="xsd:anyURI"><xsd:annotation><xsd:documentation>Optional attribute. If the publisher wants to provide a further explanation of what the particular "assertion" means, they can link to such an explanation by providing an appropriate url on the "explanation" attribute.</xsd:documentation></xsd:annotation></xsd:attribute><xsd:attribute name="group_label" type="cm_assertion_group_label"><xsd:annotation><xsd:documentation>Optional attribute. This is the human-readable form of the "group_name" attribute. This is what will be displayed in the group headings on the CrossMark metadata record dialog.</xsd:documentation></xsd:annotation></xsd:attribute><xsd:attribute name="group_name" type="cm_assertion_group_name"><xsd:annotation><xsd:documentation>Optional attribute. Some assertions could be logically "grouped" together in the CrossMark dialog. For instance, if the publisher is recording several pieces of metadata related to funding sources (source name, percentage, grant number), they may want to make sure that these three assertions are grouped next to each-other in the CrossMark dialog. The group_name attribute is the machine-readable value that will be used for grouping such assertions.</xsd:documentation></xsd:annotation></xsd:attribute><xsd:attribute name="label" type="cm_assertion_label"><xsd:annotation><xsd:documentation>Optional attribute. This is the human-readable version of the name attribute which will be displayed in the CrossMark dialog. If this attribute is missing, then the value of the assertion will *not* be displayed in the dialog. Publishers may want to "hide" assertions this way in cases where the assertion value is too large or too complex to display in the dialog, but where the assertion is nonetheless valuable enough to include in API queries and metadata dumps (e.g. detailed licensing terms)</xsd:documentation></xsd:annotation></xsd:attribute><xsd:attribute name="name" use="required" type="cm_assertion_name"><xsd:annotation><xsd:documentation>Required attribute. This is the machine-readable name of the assertion. Use the "label" attribute to provide a human-readable version of the name.</xsd:documentation></xsd:annotation></xsd:attribute><xsd:attribute name="order" type="xsd:integer"><xsd:annotation><xsd:documentation>Optional attribute. The publisher may want to control the order in which assertions are displayed to the user in the CrossMark dialog. All assertions will be sorted by this element if it is present.</xsd:documentation></xsd:annotation></xsd:attribute><xsd:attribute name="href" type="xsd:anyURI"><xsd:annotation><xsd:documentation>Optional attribute</xsd:documentation></xsd:annotation></xsd:attribute></xsd:complexType></xsd:element>
<xsd:element name="scn_policy_set"><xsd:annotation><xsd:documentation>A group of related SCN policies</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="scn_policy_ref" minOccurs="0" maxOccurs="unbounded"/></xsd:sequence><xsd:attribute name="start_date" type="xsd:date" use="optional"/></xsd:complexType></xsd:element>
<xsd:element name="citation_list"><xsd:annotation><xsd:documentation>A list of articles, books, and other items cited by the parent item for which the DOI in the doi_data is being deposited. Some articles may have multiple lists of citations (e.g. main reference list, appendix reference list, etc.). All citations for one article should be included in a single citation_list regardless of whether one or more citation lists were in the original item. When combining multiple reference lists from an item into one citation_list element, but sure to give each citation a unique key attribute value. For example, if an appendix in an item has a separate citation list that restarts numbering at 1, these citations should be given key attributes such as "ab1" rather than "b1". Some articles may contain "Further Reading" or "Bibliography" lists. The distinguishing factor in these lists is that the references have not been cited from the article—they only provide a list of additional related reading material. It will be left to the discretion of the publisher if these items are to be considered citations and should be deposited. NOTE: If a citation_list element is given and is empty then all citations for the given DOI will be deleted, otherwise any existing citations for the given DOI are left intact in the database. It is quite common that a publisher wants to fix the DOI's metadata without resubmitting the citations. Leaving out the citation_list element will do that. Also note that any given citations will override older citations for the given DOI so citation_lists are not cumulative over multiple records or submissions.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="citation" minOccurs="0" maxOccurs="unbounded"/></xsd:sequence></xsd:complexType></xsd:element>
<xsd:element name="citation"><xsd:annotation><xsd:documentation>citation is used to deposit each citation in the reference list of the item for which the DOI is being deposited. For details see: https://crossref.zendesk.com/hc/en-us/articles/215578403</xsd:documentation></xsd:annotation><xsd:complexType><xsd:complexContent><xsd:extension base="citation_t"><xsd:attributeGroup ref="citation_key.atts"/></xsd:extension></xsd:complexContent></xsd:complexType></xsd:element>
<xsd:element name="journal_title" type="xsd:string"><xsd:annotation><xsd:documentation>Journal title in a citation. Only used in the citation element. Journal title in citation deposits is used for both abbreviated and spelled out journal names. No attribute is required to distinguish between name types. Both<journal_title>Proc. Natl. Acad. Sci. U.S.A.</journal_title>and<journal_title>Proceedings of the National Academy of Sciences of the United States of America</journal_title>are valid journal titles to use in this element.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="author" type="xsd:string"><xsd:annotation><xsd:documentation>First author in a citation. Only used in the citation element. The author element tags one author name in a citation without the hierarchy required by the contributors or person_name elements Only the first author should be deposited for each item. The author surname is required. Author initials may be added but are not recommended because queries work best when only the last name is provided. For example, the author "John Doe" can be deposited as<author>Doe</author>or<author>Doe J</author>, but the former style is recommended. If the author of a work is an organization rather than a person, the organization may be deposited as in:<author>World Health Organization</author></xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="elocation_id" type="xsd:string"><xsd:annotation><xsd:documentation>article number or other page identifier for an article that does not have page numbers, used typically for electronic-only journals.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="cYear" type="xsd:string"><xsd:annotation><xsd:documentation>Year of publication in citation. Unlike the year element, cYear has a loose text model that can accommodate non-standard years such as year ranges such as "1998-1999". Note that years such as "1998a" or "1999b" should be deposited without the letter, e.g. "1998" or "1999". The letter is used for internal source document linking in name/date (Harvard) style documents rather than external cross reference linking to the original item.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="isbn"><xsd:annotation><xsd:documentation>The ISBN assigned to an entity. If a multi-volume work has one ISBN per volume and a unique ISBN for the series, all may be registered. The ISBN for the series must be in series_metadata, and the ISBN for each volume in proceedings_metadata, or book_metadata, respectively. The text "ISBN" should not be included in the ISBN element in Crossref submissions. Although not required, the ISBN number should retain spaces or hyphens that appear in the formatted number because they aid in human-readability. For more information, please see http://www.isbn.org/standards/home/isbn/international/hyphenation- instructions.asp or http://www.isbn.org.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:simpleContent><xsd:extension base="isbn_t"><xsd:attributeGroup ref="media_type.atts"/></xsd:extension></xsd:simpleContent></xsd:complexType></xsd:element>
<xsd:element name="series_title" type="xsd:string"><xsd:annotation><xsd:documentation>Book series title in a citation. Only used in the citation element. series_title is an element for the deposit of book or conference series titles in citations without the hierarchy required by the series_metadata element. Note that face markup is not permitted when this element is deposited as part of a citation.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="volume_title" type="xsd:string"><xsd:annotation><xsd:documentation>Book volume title in a citation. Only used in the citation element. volume_title is an element for the deposit of book or conference volume titles in citations without the hierarchy required by the titles element. Note that face markup is not permitted when this element is deposited as part of a citation.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="edition_number"><xsd:annotation><xsd:documentation>The edition number of a book. edition_number should include only a number and not additional text such as "edition". For example, you should submit "3", not "third edition" or "3rd edition". Roman numerals are acceptable. Publishers will update a print edition with a new edition number when more than ten percent of the content has changed. However, publishers expect to continuously update online editions of books without changing the edition number.<i>The ability to update the electronic version independent of the print version could be problematic for researchers. For example, if a research article cites the print version of a chapter, and a researcher subsequently links to the online version of the same chapter, the content may be different from the print version without the typical indication of a new edition. This topic requires further discussion outside of the scope of this specification.</i></xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="15"/><xsd:minLength value="1"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="component_number"><xsd:annotation><xsd:documentation>The chapter, section, part, etc. number for a content item in a book. Unlike volume and edition_number, component_number should include any additional text that helps identify the type of component. In the example above, the text "Section 8" appeared on the table of contents and it is reflected here. "8" is also acceptable, however the former treatment is preferred. The type of the component is given the component_type attribute of content_item.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="50"/><xsd:minLength value="1"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="article_title" type="xsd:string"><xsd:annotation><xsd:documentation>Article title in a citation. Use care to remove face markup (such as italic applied to genus or species names) from article titles as this markup is not supported by Crossref.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="standards_body"><xsd:annotation><xsd:documentation>A wrapper for standards body information.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="standards_body_name"/><xsd:element ref="standards_body_acronym"/></xsd:sequence></xsd:complexType></xsd:element>
<xsd:element name="standards_body_name"><xsd:annotation><xsd:documentation>Name of the standards organization / publisher. Required.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="standards_body_acronym"><xsd:annotation><xsd:documentation>Acronym for standards body. Will be used for query matching - required.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="unstructured_citation"><xsd:annotation><xsd:documentation>A citation to an item that is not structured with the Crossref citation model. 'unstructured_citation' supports deposit of references for which no structural information is available.</xsd:documentation></xsd:annotation><xsd:complexType mixed="true"><xsd:choice minOccurs="0" maxOccurs="unbounded"><xsd:group ref="face_markup"/></xsd:choice></xsd:complexType></xsd:element>
<xsd:element name="component_list"><xsd:annotation><xsd:documentation>The wrapper element for including a group of components under a journal article, conference proceeding, book chapter, stand alone component, dissertation, technical report or working paper, standard, or database.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="component" minOccurs="0" maxOccurs="unbounded"/></xsd:sequence></xsd:complexType></xsd:element>
<xsd:element name="component"><xsd:annotation><xsd:documentation>A container element that allows registration of supplemental information for a journal article, book chapter, or conference paper such as figures, tables, videos, or data sets. Currently, the deposit of components primarily achieves only the first objective as the Crossref system is not setup yet to support queries for components. The metadata associated with a component is intended to enable simple lookup searches of components in the future. When deposited as part of the metadata for a higher level work the parent DOI is implicitly known via the XML hierarchy. When deposited separately the DOI of the higher level work must be provided explicitly (see sa_component) All descriptive elements are optional allowing for the creation of simple anonymous DOIs. The 'parent_relation' attribute is mandatory and refers to the DOI described in the component's direct parent.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="titles" minOccurs="0"/><xsd:element ref="contributors" minOccurs="0"/><xsd:element ref="publication_date" minOccurs="0"/><xsd:element ref="description" minOccurs="0"/><xsd:element ref="format" minOccurs="0"/><xsd:element ref="ai:program" minOccurs="0"/><xsd:choice><xsd:element ref="doi_data"/><xsd:element ref="doi"/></xsd:choice></xsd:sequence><xsd:attribute name="parent_relation" use="required"><xsd:simpleType><xsd:restriction base="xsd:NMTOKEN"><xsd:enumeration value="isPartOf"/><xsd:enumeration value="isReferencedBy"/><xsd:enumeration value="isRequiredBy"/><xsd:enumeration value="isTranslationOf"/></xsd:restriction></xsd:simpleType></xsd:attribute><xsd:attribute name="reg-agency" use="optional"><xsd:simpleType><xsd:restriction base="xsd:string"/></xsd:simpleType></xsd:attribute><xsd:attributeGroup ref="language.atts"/><xsd:attribute name="component_size"><xsd:simpleType><xsd:restriction base="xsd:nonNegativeInteger"/></xsd:simpleType></xsd:attribute></xsd:complexType></xsd:element>
<xsd:element name="description"><xsd:annotation><xsd:documentation>A narrative description of a file (e.g. a figure caption or video description) which may be independent of the host document context. The description element may be present more than once to provide alternative language values.</xsd:documentation></xsd:annotation><xsd:complexType mixed="true"><xsd:choice minOccurs="0" maxOccurs="unbounded"><xsd:group ref="face_markup"/></xsd:choice><xsd:attributeGroup ref="language.atts"/></xsd:complexType></xsd:element>
<xsd:element name="format"><xsd:annotation><xsd:documentation>A narrative description of a component's file format and/or the file extension (for mime types refer to http://www.iana.org/assignments/media-types/) The format element may contain only the mime_type attribute, or in addition it may contain a narrative description of the file format. Be sure to use the narrative portion to description only the format of the component and not the actual content of the component (use description to describe the component's content).</xsd:documentation></xsd:annotation><xsd:complexType><xsd:simpleContent><xsd:extension base="format_t"><xsd:attributeGroup ref="mime_type.atts"/></xsd:extension></xsd:simpleContent></xsd:complexType></xsd:element>
<xsd:element name="book"><xsd:annotation><xsd:documentation>The container for all information about a single book. book is the core container for information about a specific book. Books may be in the form of edited books (i.e. a contributed volume with one or more editors), monographs (single-authored works), or reference works (e.g. encyclopedias). If a book contains multiple volumes, each volume must be contained in a unique book element. You may chose to submit only top level contributors and book_metadata for any book, or you may chose to submit these elements along with metadata for each content_item. A content item is typically any entity that is listed on the table of contents such as a chapter, section, etc. It is not necessary to submit metadata for all items listed on the table of contents. You may chose to drop items of lesser significance such as front and back matter. Book-level metadata is captured within book_metadata, book_series_metadata, or book_set_metadata. If a books is a single-volume work, use book_metadata. If the book is a volume from a multi-volume work that is also a serial publication (and therefore has an ISSN), use book_series_metadata. If the book is a volume of non-serial publication, then it is considered a set and you should use book_set_metadata book_type should be set to "monograph" when the same author or authors wrote the majority of the content. It should be set to "edited_book" when a book primarily consists of contributed chapters, each chapter written by different authors. It should be set to "reference" for major reference works such as encyclopedias. Use "other" when the author of the content does not fit any of the other categories.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:choice><xsd:element ref="book_metadata"/><xsd:element ref="book_series_metadata"/><xsd:element ref="book_set_metadata"/></xsd:choice><xsd:element ref="content_item" minOccurs="0" maxOccurs="unbounded"/></xsd:sequence><xsd:attribute name="book_type" use="required"><xsd:simpleType><xsd:restriction base="xsd:NMTOKEN"><xsd:enumeration value="edited_book"/><xsd:enumeration value="monograph"/><xsd:enumeration value="reference"/><xsd:enumeration value="other"/></xsd:restriction></xsd:simpleType></xsd:attribute></xsd:complexType></xsd:element>
<xsd:element name="book_metadata"><xsd:annotation><xsd:documentation>A container for all information that applies to a monograph. It does not include metadata about individual chapters. The language of the book should be specified in the book_metadata language attribute. If a book contains items in multiple languages this attribute should be set for the predominant language of the book. Individual items may have their language specified in content_item. If all content items are the same language, it is only necessary to specify the language of the book in this element. The contributors are the author(s) or editor(s) of the entire work. When using book_metadata, specify the title of the book within book_metadata. edition_number, when given, should include only a number and not additional text such as "edition" or "ed". publisher_item, when given, specifies this information for the entire book or volume. This element also appears in content_item. doi_data is required for each book or volume that you submit. It is not possible to submit DOI information for individual chapters without assigning a DOI to the entire work. Note: citation_list should only be used in book_metadata instead of content_item when the reference list is a separate section of the book, and content_items are not included in the deposit (e.g. you are depositing a book with a bibliography, but not the chapters of the book) In very limited circumstances a book may be deposited without an ISBN, in which case the noisbn element must be supplied to explicitly declare that an ISBN is not accidentily omitted. Great care should be taken when choossing to use noisbn since it may adversely effect matching. This provision is primarily being made to allow for the deposit of DOIs for historical volumes that are difficult to obtain ISBNs.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="contributors" minOccurs="0"/><xsd:element ref="titles"/><xsd:element ref="jats:abstract" minOccurs="0" maxOccurs="unbounded"/><xsd:element ref="edition_number" minOccurs="0"/><xsd:element ref="publication_date" maxOccurs="10"/><xsd:element ref="acceptance_date" minOccurs="0" maxOccurs="1"/><xsd:choice><xsd:element ref="isbn" maxOccurs="6"/><xsd:element ref="noisbn"/></xsd:choice><xsd:element ref="publisher"/><xsd:element ref="publisher_item" minOccurs="0"/><xsd:choice><xsd:element ref="crossmark" minOccurs="0"/><xsd:sequence><xsd:element ref="fr:program" minOccurs="0" maxOccurs="1"/><xsd:element ref="ai:program" minOccurs="0" maxOccurs="1"/></xsd:sequence></xsd:choice><xsd:element ref="rel:program" minOccurs="0"/><xsd:element ref="archive_locations" minOccurs="0" maxOccurs="1"/><xsd:element ref="doi_data" minOccurs="0"/><xsd:element ref="citation_list" minOccurs="0"/></xsd:sequence><xsd:attributeGroup ref="language.atts"/><xsd:attributeGroup ref="reference_distribution_opts.att"/></xsd:complexType></xsd:element>
<xsd:element name="noisbn"><xsd:annotation><xsd:documentation>Identifies books or conference proceedings that have no ISBN assigned. In very limited cases a book may never have an ISBN, this is particularly true for older texts. Conference proceedings, however, may regularly have a volume number but no ISBN or volume title.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:attribute name="reason" use="required"><xsd:simpleType><xsd:restriction base="xsd:NMTOKEN"><xsd:enumeration value="archive_volume"/><xsd:enumeration value="monograph"/><xsd:enumeration value="simple_series"/></xsd:restriction></xsd:simpleType></xsd:attribute></xsd:complexType></xsd:element>
<xsd:element name="publisher"><xsd:annotation><xsd:documentation>A container for information about the publisher of a book or conference proceedings.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="publisher_name"/><xsd:element ref="publisher_place" minOccurs="0"/></xsd:sequence></xsd:complexType></xsd:element>
<xsd:element name="publisher_name"><xsd:annotation><xsd:documentation>The name of the publisher of a book or conference proceedings. publisher_name is the imprint of the publication (what the author will likely cite), not the organization registering the DOI, if for any reason they are different. When registering a translation, the translation publisher, not the original publisher, should be given.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="255"/><xsd:minLength value="1"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="publisher_place"><xsd:annotation><xsd:documentation>The city where the publisher of this work is located. publisher_place gives the primary city location of the publisher. When the location is a major city (e.g. New York, Amsterdam), no qualifying country, U.S. state, or Canadian province need be given. If the city is not a major city, the appropriate country, U.S. state, or Canadian province should be added.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="255"/><xsd:minLength value="2"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="book_series_metadata"><xsd:annotation><xsd:documentation>A container for all information that applies to an individual volume of a book series. It does not include metadata about individual chapters. The language of the book should be specified in the book_series_metadata language attribute. If a book contains items in multiple languages this attribute should be set for the predominant language of the book. Individual items may have their language specified in content_item. If all content items are the same language, it is only necessary to specify the language of the book in this element. The contributors are the author(s) or editor(s) of the entire work. If a multi- volume work has separate editors for each volume, those editors should be specified in this element, and the series editors are listed in the series_metadata contributors. Series titles should be specified within series_metadata. Volume titles (when present) are captured in book_series_metadata. If the volumes of a series only have volume numbers and not individual titles, you may specify the volume number within volume_metadata, and no title is required. volume and edition_number, when given, should include only a number and not additional text such as "volume" or "edition". For example, you should submit "3", not "third edition". If a work spans multiple volumes with a unique ISBN for each volume and the whole series, you should specify the series ISBN in isbn in series_metadata and the volume ISBN in isbn in book_series_metadata. WARNING: Care must be taken when submitting books with series. If a series title is submitted and no book title is supplied but an ISBN is supplied at the book_series_metadata level and not with the series title, the Crossref system will index a series title with no ISBN and an ISBN with no title. Please take care to associate the ISBN at the correct level of the XML hierarchy. publisher_item, when given, specifies this information for the entire book or volume. This element also appears in content_item. doi_data is required for each book or volume that you submit. It is not possible to submit DOI information for individual chapters without assigning a DOI to the entire work. Note: citation_list should only be used in book_series_metadata instead of content_item when the reference list is a separate section of the book, and content_items are not included in the deposit (e.g. you are depositing a book with a bibliography, but not the chapters of the book) Normally book content that is published as a series is required to have a series title with an ISSN and a book title and/or a book volume number along with a book ISBN. An exception is when book chapters are published on line first prior to being assigned to a specific book in which case only the series title (and ISSN) is known at time of DOI registration. Element unassigned_content is used as a placeholder to force recognition of this condition and thus prevent accidental omission of book level title information.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="series_metadata"/><xsd:choice><xsd:sequence><xsd:element ref="contributors" minOccurs="0"/><xsd:choice><xsd:sequence><xsd:element ref="titles"/><xsd:element ref="jats:abstract" minOccurs="0" maxOccurs="unbounded"/><xsd:element ref="volume" minOccurs="0"/></xsd:sequence><xsd:element ref="volume"/></xsd:choice><xsd:element ref="edition_number" minOccurs="0"/><xsd:element ref="publication_date" maxOccurs="10"/><xsd:choice><xsd:element ref="isbn" maxOccurs="6"/><xsd:element ref="noisbn"/></xsd:choice></xsd:sequence><xsd:element ref="publication_date" maxOccurs="10"/></xsd:choice><xsd:element ref="publisher"/><xsd:element ref="publisher_item" minOccurs="0"/><xsd:choice><xsd:element ref="crossmark" minOccurs="0"/><xsd:sequence><xsd:element ref="fr:program" minOccurs="0" maxOccurs="1"/><xsd:element ref="ai:program" minOccurs="0" maxOccurs="1"/></xsd:sequence></xsd:choice><xsd:element ref="rel:program" minOccurs="0"/><xsd:element ref="archive_locations" minOccurs="0" maxOccurs="1"/><xsd:element ref="doi_data" minOccurs="0"/><xsd:element ref="citation_list" minOccurs="0"/></xsd:sequence><xsd:attributeGroup ref="language.atts"/><xsd:attributeGroup ref="reference_distribution_opts.att"/></xsd:complexType></xsd:element>
<xsd:element name="series_metadata"><xsd:annotation><xsd:documentation>The container for metadata about a series publication. When a book, conference proceeding, or report consists of multiple volumes, series_metadata is used to describe information about the entire series. If a work spans multiple volumes, you should use titles in series_metadata. If a work spans multiple volumes with a unique title for each volume and the whole series, you should specify the series title in titles in series_metadata and the volume title in titles in book_series_metadata. If a unique ISBN has been assigned to the entire series (as opposed to the individual volumes), it should given in series_metadata. You may assign and register a DOI that encompasses an entire series by adding doi_data in series_metadata. This element is optional for a series.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="contributors" minOccurs="0"/><xsd:element ref="titles"/><xsd:element ref="jats:abstract" minOccurs="0" maxOccurs="unbounded"><xsd:annotation><xsd:documentation>The abstract element allows depositors to include abstracts extracted from NLM or JATS XML in Crossref deposits. The jats: namespace prefix must be included.</xsd:documentation></xsd:annotation></xsd:element><xsd:element ref="issn" maxOccurs="6"/><xsd:element ref="coden" minOccurs="0"/><xsd:element ref="series_number" minOccurs="0"/><xsd:element ref="publisher_item" minOccurs="0"/><xsd:choice><xsd:element ref="crossmark" minOccurs="0"/><xsd:sequence><xsd:element ref="fr:program" minOccurs="0" maxOccurs="1"/><xsd:element ref="ai:program" minOccurs="0" maxOccurs="1"/></xsd:sequence></xsd:choice><xsd:element ref="archive_locations" minOccurs="0" maxOccurs="1"/><xsd:element ref="doi_data" minOccurs="0"/></xsd:sequence></xsd:complexType></xsd:element>
<xsd:element name="series_number"><xsd:annotation><xsd:documentation>The series number within a specific published conference discipline. The series number is different from the volume number. A volume number is the number of a book in a physically printed set and typically appears in sequence. The series number is not tied to the physical manifestation of the printed volume and need not be strictly in sequence. It is most commonly used in "Lectures" published by Springer-Verlag. This element is available in series_metadata, however it should only be used for conference proceedings, not for books.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="15"/><xsd:minLength value="1"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="book_set_metadata"><xsd:annotation><xsd:documentation>A container for all information that applies to an individual volume of a book set. It does not include metadata about individual chapters. A set is a finite series, and does not have an ISSN The language of the book should be specified in the book_set_metadata language attribute. If a book contains items in multiple languages this attribute should be set for the predominant language of the book. Individual items may have their language specified in content_item. If all content items are the same language, it is only necessary to specify the language of the book in this element. The contributors are the author(s) or editor(s) of the entire work. If a multi- volume work has separate editors for each volume, those editors should be specified in this element, and the series editors are listed in the series_metadata contributors. When using book_set_metadata, specify the title of the entire set and the isbn of the set. Specify the title of the volume in volume_metadata. If the volumes of a set only have volume numbers and not individual titles, you may specify the volume number within volume_metadata, and no title is required. volume and edition_number, when given, should include only a number and not additional text such as "volume" or "edition". For example, you should submit "3", not "third edition". If a work spans multiple volumes with a unique ISBN for each volume and the whole series, you should specify the series ISBN in isbn in series_metadata and the volume ISBN in isbn in book_series_metadata. publisher_item, when given, specifies this information for the entire book or volume. This element also appears in content_item. doi_data is required for each book or volume that you submit. It is not possible to submit DOI information for individual chapters without assigning a DOI to the entire work. Note: citation_list should only be used in book_series_metadata instead of content_item when the reference list is a separate section of the book, and content_items are not included in the deposit (e.g. you are depositing a book with a bibliography, but not the chapters of the book)</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="set_metadata"/><xsd:element ref="contributors" minOccurs="0"/><xsd:choice><xsd:sequence><xsd:element ref="titles"/><xsd:element ref="jats:abstract" minOccurs="0" maxOccurs="unbounded"/><xsd:element ref="volume" minOccurs="0"/></xsd:sequence><xsd:element ref="volume"/></xsd:choice><xsd:element ref="edition_number" minOccurs="0"/><xsd:element ref="publication_date" maxOccurs="10"/><xsd:choice><xsd:element ref="isbn" maxOccurs="6"/><xsd:element ref="noisbn"/></xsd:choice><xsd:element ref="publisher"/><xsd:element ref="publisher_item" minOccurs="0"/><xsd:choice><xsd:element ref="crossmark" minOccurs="0"/><xsd:sequence><xsd:element ref="fr:program" minOccurs="0" maxOccurs="1"/><xsd:element ref="ai:program" minOccurs="0" maxOccurs="1"/></xsd:sequence></xsd:choice><xsd:element ref="rel:program" minOccurs="0"/><xsd:element ref="archive_locations" minOccurs="0" maxOccurs="1"/><xsd:element ref="doi_data" minOccurs="0"/><xsd:element ref="citation_list" minOccurs="0"/></xsd:sequence><xsd:attributeGroup ref="language.atts"/><xsd:attributeGroup ref="reference_distribution_opts.att"/></xsd:complexType></xsd:element>
<xsd:element name="set_metadata"><xsd:annotation><xsd:documentation>When a book consists of multiple volumes that are not part of a serial publication (series), set_metadata is used to describe information about the entire set.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="titles"/><xsd:choice><xsd:element ref="isbn" maxOccurs="6"/><xsd:element ref="noisbn"/></xsd:choice><xsd:element ref="contributors" minOccurs="0"/><xsd:element ref="part_number" minOccurs="0"/><xsd:element ref="publisher_item" minOccurs="0"/><xsd:element ref="archive_locations" minOccurs="0" maxOccurs="1"/><xsd:element ref="doi_data" minOccurs="0"/></xsd:sequence></xsd:complexType></xsd:element>
<xsd:element name="part_number"><xsd:annotation><xsd:documentation>The part number of a given volume. Deposited within book_set_metadata. In some cases, a book set will have multiple parts, and then one or more volumes within each part. The part number of a given volume should be deposited in this element.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="15"/><xsd:minLength value="1"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="content_item"><xsd:annotation><xsd:documentation>An entity in a book, such as a chapter, for which a DOI is being registered. A content item is typically an entity listed on the table of contents. There need not be a one-to-one correlation between content listings and content items (e.g. you may choose not to register front and back matter items listed in the table of contents). The language of a content_item only need be set if it differs from the language of book_metadata. The component_type indicates the type of content item you are registering. Please see the example of a book submission in this documentation for a better understanding of how this attribute may be used in nested tables of contents. level_sequence_number indicates the level of nesting for content items. For example, you may use it to indicate when one content item, such as a chapter, is actually inside another content item, such as a section. Please see the example of a book submission in this documentation for a better understanding of how this attribute may be used in nested tables of contents. Note: Because the Crossref schema uses a flat model to indicate hierarchically nested content items, there is an implicit assumption that content items will be listed in the Crossref submission in the same order in which they appear in the table of contents. Please follow this protocol when submitting DOI data for books. This order is not required for journal and conference data. contributors for a content_item need not be listed if all items in a book have the same contributors listed in book_metadata. In other words, contributors must be listed for edited books, but they should not be listed for each content_item in a monograph. The exception case is when a content item such as a Preface or Forward for a monograph has a different author from that of the monograph. In this case, the contributors should be given. The title of each content item must be submitted. If, however, you are submitted data for a monograph that simply has "Chapter 1", "Chapter 2", etc., you should put this information in component_number, not titles.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="contributors" minOccurs="0"/><xsd:element ref="titles" minOccurs="0"/><xsd:element ref="jats:abstract" minOccurs="0" maxOccurs="unbounded"/><xsd:element ref="component_number" minOccurs="0"/><xsd:element ref="publication_date" minOccurs="0" maxOccurs="10"/><xsd:element ref="acceptance_date" minOccurs="0" maxOccurs="1"/><xsd:element ref="pages" minOccurs="0"/><xsd:element ref="publisher_item" minOccurs="0"/><xsd:choice><xsd:element ref="crossmark" minOccurs="0"/><xsd:sequence><xsd:element ref="fr:program" minOccurs="0" maxOccurs="1"/><xsd:element ref="ai:program" minOccurs="0" maxOccurs="1"/><xsd:element ref="ct:program" minOccurs="0" maxOccurs="1"/></xsd:sequence></xsd:choice><xsd:element ref="rel:program" minOccurs="0"/><xsd:element ref="archive_locations" minOccurs="0" maxOccurs="1"/><xsd:element ref="scn_policies" minOccurs="0" maxOccurs="1"/><xsd:element ref="doi_data"/><xsd:element ref="citation_list" minOccurs="0"/><xsd:element ref="component_list" minOccurs="0"/></xsd:sequence><xsd:attribute name="component_type" use="required"><xsd:simpleType><xsd:restriction base="xsd:NMTOKEN"><xsd:enumeration value="chapter"/><xsd:enumeration value="section"/><xsd:enumeration value="part"/><xsd:enumeration value="track"/><xsd:enumeration value="reference_entry"/><xsd:enumeration value="other"/></xsd:restriction></xsd:simpleType></xsd:attribute><xsd:attribute name="level_sequence_number" default="1"><xsd:simpleType><xsd:restriction base="xsd:positiveInteger"><xsd:maxInclusive value="9"/><xsd:minInclusive value="1"/><xsd:totalDigits value="1"/></xsd:restriction></xsd:simpleType></xsd:attribute><xsd:attributeGroup ref="publication_type.atts"/><xsd:attributeGroup ref="language.atts"/><xsd:attributeGroup ref="reference_distribution_opts.att"/></xsd:complexType></xsd:element>
<xsd:element name="conference"><xsd:annotation><xsd:documentation>The container for all information about a single conference and its proceedings. conference is the core container for information about a single conference and its proceedings. If a conference proceedings spans multiple volumes, each volume must be contained in a unique conference element. You may choose to submit only top level contributors, event_metadata and proceedings_metadata for any conference, or you may choose to submit these elements along with metadata for each conference_paper. It is not necessary to submit metadata for all items listed on the proceedings table of contents. You may chose to drop items of lesser significance such as front and back matter. NOTE: The Crossref system currently uses the proceedings_title and conference_acronym in the query matching process. This system can cause problems when the proceedings have a simple non-changing title (e.g PRoceedings of SPIE) and the conference event name, conference_name, is used to differentiate conference topics (e.g. Optoelectronic Integrated Circuits II). To avoid this problem, Crossref recommends that you make sure the conference_acronym accurately reflects the event name (e.g OpIC II in this example).</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="contributors" minOccurs="0"/><xsd:element ref="event_metadata"/><xsd:choice><xsd:element ref="proceedings_series_metadata"/><xsd:element ref="proceedings_metadata"/></xsd:choice><xsd:element ref="conference_paper" minOccurs="0" maxOccurs="unbounded"/></xsd:sequence></xsd:complexType></xsd:element>
<xsd:element name="event_metadata"><xsd:annotation><xsd:documentation>A container for all information that applies to a conference event. event_metadata captures information about a conference event. Data about conference proceedings is captured in proceedings_metadata. NOTE: The Crossref system currently uses the proceedings_title and conference_acronym in the query matching process. This system can cause problems when the proceedings have a simple non-changing title (e.g PRoceedings of SPIE) and the conference event name, conference_name, is used to differentiate conference topics (e.g. Optoelectronic Integrated Circuits II). To avoid this problem, Crossref recommends that you make sure the conference_acronym accurately reflects the event name (e.g OpIC II in this example).</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="conference_name"/><xsd:element ref="conference_theme" minOccurs="0"/><xsd:element ref="conference_acronym" minOccurs="0"/><xsd:element ref="conference_sponsor" minOccurs="0" maxOccurs="10"/><xsd:element ref="conference_number" minOccurs="0"/><xsd:element ref="conference_location" minOccurs="0"/><xsd:element ref="conference_date" minOccurs="0"/></xsd:sequence></xsd:complexType></xsd:element>
<xsd:element name="conference_name"><xsd:annotation><xsd:documentation>The official name of the conference. conference_name does not include "Proceedings of". For example, "The 23rd Annual Meeting of the American Society for Information Science" is a correct conference name. It is quite common for a conference name to include the conference number or subject. When any of these metadata items appear in the conference name, they should be included in this element, and also in the respective sub-element, conference_number or proceedings_subject. The following example shows incorrect tagging of a conference name and then the corrected version: INCORRECT:<event_metadata><conference_name>the second international conference</conference_name><conference_acronym>IEA/AIE '89</conference_acronym><conference_number>1989</conference_number><conference_location>Tullahoma, TN</conference_location><conference_date start_year="1989"/></event_metadata><proceedings_metadata language="en"><proceedings_title>Proceedings of the second international conference on Industrial and engineering applications of artificial intelligence and expert systems - IEA/AIE'89</proceedings_title><proceedings_subject>Industrial and engineering applications of artificial intelligence and expert systems</proceedings_subject></proceedings_metadata>CORRECT:<event_metadata><conference_name>The second international conference on Industrial and engineering applications of artificial intelligence and expert systems</conference_name><conference_acronym>IEA/AIE '89</conference_acronym><conference_number>2</conference_number><conference_location>Tullahoma, TN</conference_location><conference_date start_year="1989"/></event_metadata><proceedings_metadata language="en"><proceedings_title>Proceedings of the second international conference on Industrial and engineering applications of artificial intelligence and expert systems - IEA/AIE '89</proceedings_title><proceedings_subject>Industrial and engineering applications of artificial intelligence and expert systems</proceedings_subject></proceedings_metadata>Authors commonly cite a conference by the official name, so it is important to provide this information as accurately as possible.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="512"/><xsd:minLength value="3"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="conference_theme"><xsd:annotation><xsd:documentation>The theme is the slogan or special emphasis of a conference in a particular year. The theme is the slogan of the conference. It differs from the subject of a conference in that the subject is stable over the years while the theme may vary from year to year. For example, the American Society for Information Science and Technology conference theme was "Knowledge: Creation, Organization and Use" in 1999 and "Defining Information Architecture" in 2000.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="255"/><xsd:minLength value="1"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="conference_acronym"><xsd:annotation><xsd:documentation>The popularly known as or jargon name (e.g. SIGGRAPH for "Special Interest Group on Computer Graphics"). Authors commonly cite the conference acronym rather than the full conference or proceedings name, so it is best to include this element when it is available. The conference acronym often includes the year of the conference (e.g. SGML '97) or, less often, the conference number. It is preferred, but not required, that submission of metadata exclude number or year information from the conference acronym. It is better to include such information in conference_number, or conference_date, respectively.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="127"/><xsd:minLength value="1"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="conference_sponsor"><xsd:annotation><xsd:documentation>The sponsoring organization(s) of a conference. Multiple sponsors may be given if a conference is hosted by more than one organization.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="255"/><xsd:minLength value="1"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="conference_number"><xsd:annotation><xsd:documentation>The number of a conference. conference_number should include only the number of the conference without any extra text. For example, "The 24th Annual Conference on..." should be tagged as shown in the example above, and "th" should not be included. Roman numerals are acceptable. When a conference is named such that the year of the conference indicates the number (e.g. "SGML 1994"), the year appears in conference_name, conference_date, and conference_number, as in:<conference_name>SGML 1994</conference_name><conference_acronym>SGML</conference_acronym><conference_number>1994</conference_number><conference_date start_day="07" start_month="11" start_year="1994" end_day="10" end_month="11" end_year="1994">November 7-10, 1994</conference_date></xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="15"/><xsd:minLength value="1"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="conference_location"><xsd:annotation><xsd:documentation>The location of the conference. The city and country of the conference. If the conference is in the United States, the appropriate state should also be provided, and the country may be omitted. If the conference is in Canada, the province should be provided, and the country may be omitted. The specific venue or address within a city (e.g. conference center, hotel, etc.) should not be provided.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="255"/><xsd:minLength value="2"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="conference_date"><xsd:annotation><xsd:documentation>The start and end dates of a conference event. conference_date may be used in three ways: 1. If publishers that do not have parsed date values, provide just text with the conference dates. The date text should be taken from the proceedings title page. 2. If publishers have parsed date values, provide them in the attributes. 3. If both parsed date values and the date text are available, both should be provided. This is the preferred tagging for conference_date. For example:<conference_date start_month="01" start_year="1997" start_day="15" end_year="1997" end_month="01" end_day="17">Jan. 15-17, 1997</conference_date></xsd:documentation></xsd:annotation><xsd:complexType><xsd:simpleContent><xsd:extension base="conference_date_t"><xsd:attribute name="start_day" type="xrefDay" use="optional"/><xsd:attribute name="start_month" type="xrefMonth" use="optional"/><xsd:attribute name="start_year" type="xrefYear" use="optional"/><xsd:attribute name="end_day" type="xrefDay" use="optional"/><xsd:attribute name="end_month" type="xrefMonth" use="optional"/><xsd:attribute name="end_year" type="xrefYear" use="optional"/></xsd:extension></xsd:simpleContent></xsd:complexType></xsd:element>
<xsd:element name="proceedings_series_metadata"><xsd:annotation><xsd:documentation>A container for all information that applies to a specific conference proceeding that is part of a series. A conference proceedings published as a series can sometimes look just like a journnal in that there is no volume information (no volume title, no ISBN). In these cases the conference proceeding may be deposited as a journal (which more accurately should have been called a 'series_publication'). To allow for the use of a consistent XML heirarchy we will allow a proceedings_series_metadata root element to also describe such a publication. Note: this structure is organized to allow backward compatibility with previous schema versions by maintaining the prior sequence of elements.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="series_metadata"/><xsd:choice><xsd:sequence><xsd:choice><xsd:sequence><xsd:element ref="proceedings_title"/><xsd:element ref="volume" minOccurs="0"/></xsd:sequence><xsd:element ref="volume"/></xsd:choice><xsd:element ref="proceedings_subject" minOccurs="0"/><xsd:element ref="publisher" maxOccurs="5"/><xsd:element ref="publication_date" maxOccurs="10"/><xsd:choice><xsd:element ref="isbn" maxOccurs="6"/><xsd:element ref="noisbn"/></xsd:choice></xsd:sequence><xsd:sequence><xsd:element ref="proceedings_subject" minOccurs="0"/><xsd:element ref="publisher" maxOccurs="5"/><xsd:element ref="publication_date" maxOccurs="10"/></xsd:sequence></xsd:choice><xsd:element ref="publisher_item" minOccurs="0"/><xsd:element ref="archive_locations" minOccurs="0" maxOccurs="1"/><xsd:element ref="doi_data" minOccurs="0"/></xsd:sequence><xsd:attributeGroup ref="reference_distribution_opts.att"/></xsd:complexType></xsd:element>
<xsd:element name="proceedings_title"><xsd:annotation><xsd:documentation>The title of the conference proceedings as printed on title page of the published conference proceedings. proceedings_title is the undifferentiated title of a conference proceedings. It should generally be the title as it appears on the cover of the printed proceedings. In some cases, proceedings_title may differ from conference_name only in that the text "Proceedings of" often appears at the start of the proceedings_title, and it this text should never be included in conference_name. In other cases, the proceedings_title and conference_name may be quite different.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="511"/><xsd:minLength value="1"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="proceedings_subject"><xsd:annotation><xsd:documentation>The subject of the printed conference proceedings, e.g. "Computer Graphics" is the subject matter of SIGGRAPH. This element is useful because an author may cite a conference paper by the conference subject. For example, "Proceedings of the 1999 ACM Conference on Computer Graphics"</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="255"/><xsd:minLength value="1"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="proceedings_metadata"><xsd:annotation><xsd:documentation>A container for all information that applies to a non-series conference proceeding. proceedings_metadata captures information about conference proceedings. Data about conference events is captured in event_metadata</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="proceedings_title"/><xsd:element ref="proceedings_subject" minOccurs="0"/><xsd:element ref="publisher" maxOccurs="5"/><xsd:element ref="publication_date" maxOccurs="10"/><xsd:choice><xsd:element ref="isbn" maxOccurs="6"/><xsd:element ref="noisbn"/></xsd:choice><xsd:element ref="publisher_item" minOccurs="0"/><xsd:element ref="archive_locations" minOccurs="0" maxOccurs="1"/><xsd:element ref="doi_data" minOccurs="0"/></xsd:sequence><xsd:attributeGroup ref="language.atts"/><xsd:attributeGroup ref="reference_distribution_opts.att"/></xsd:complexType></xsd:element>
<xsd:element name="conference_paper"><xsd:annotation><xsd:documentation>The container for all information about a single conference paper. A conference paper is required to have contributors, title and doi_data. All other information is optional.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="contributors" minOccurs="0"/><xsd:element ref="titles"/><xsd:element ref="jats:abstract" minOccurs="0" maxOccurs="unbounded"/><xsd:element ref="publication_date" minOccurs="0" maxOccurs="10"/><xsd:element ref="acceptance_date" minOccurs="0" maxOccurs="1"/><xsd:element ref="pages" minOccurs="0"/><xsd:element ref="publisher_item" minOccurs="0"/><xsd:choice><xsd:element ref="crossmark" minOccurs="0"/><xsd:sequence><xsd:element ref="fr:program" minOccurs="0" maxOccurs="1"/><xsd:element ref="ai:program" minOccurs="0" maxOccurs="1"/><xsd:element ref="ct:program" minOccurs="0" maxOccurs="1"/></xsd:sequence></xsd:choice><xsd:element ref="rel:program" minOccurs="0"/><xsd:element ref="archive_locations" minOccurs="0" maxOccurs="1"/><xsd:element ref="scn_policies" minOccurs="0" maxOccurs="1"/><!-- cs-3495 --><xsd:element ref="doi_data"/><xsd:element ref="citation_list" minOccurs="0"/><xsd:element ref="component_list" minOccurs="0"/></xsd:sequence><xsd:attributeGroup ref="publication_type.atts"/><xsd:attributeGroup ref="language.atts"/><xsd:attributeGroup ref="reference_distribution_opts.att"/></xsd:complexType></xsd:element>
<xsd:element name="sa_component"><xsd:annotation><xsd:documentation>The element for depositing a stand alone component. The parent DOI must already exist (created in an earlier deposit or via some other registration process).</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="component_list"/></xsd:sequence><xsd:attribute name="parent_doi" use="required"><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="2048"/><xsd:minLength value="6"/></xsd:restriction></xsd:simpleType></xsd:attribute></xsd:complexType></xsd:element>
<xsd:element name="dissertation"><xsd:annotation><xsd:documentation>dissertation is the top level element for deposit of metadata about one or more dissertations. The dissertation element does not have publisher, or issn elements. It is expected that the dissertation element will be used for deposit of items that have not been published in books or journals. If a dissertation is published as a book or within a serial, it should be deposited using the top-level element for the appropriate publication type. If a DAI has been assigned, it should be deposited in the identifier element with the id_type attribute set to "dai". If an institution has its own numbering system, it should be deposited in item_number, and the item_number_type should be set to "institution"</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:choice><xsd:element ref="person_name" minOccurs="1" maxOccurs="unbounded"/><xsd:element ref="contributors"/></xsd:choice><xsd:element ref="titles"/><xsd:element ref="jats:abstract" minOccurs="0" maxOccurs="unbounded"/><xsd:element ref="approval_date" maxOccurs="10"/><xsd:element ref="institution" maxOccurs="6"/><xsd:element ref="degree" minOccurs="0" maxOccurs="10"/><xsd:element ref="isbn" minOccurs="0" maxOccurs="6"/><xsd:element ref="publisher_item" minOccurs="0"/><xsd:choice><xsd:element ref="crossmark" minOccurs="0"/><xsd:sequence><xsd:element ref="fr:program" minOccurs="0" maxOccurs="1"/><xsd:element ref="ai:program" minOccurs="0" maxOccurs="1"/></xsd:sequence></xsd:choice><xsd:element ref="rel:program" minOccurs="0"/><xsd:element ref="archive_locations" minOccurs="0" maxOccurs="1"/><xsd:element ref="scn_policies" minOccurs="0" maxOccurs="1"/><xsd:element ref="doi_data"/><xsd:element ref="citation_list" minOccurs="0"/><xsd:element ref="component_list" minOccurs="0"/></xsd:sequence><xsd:attributeGroup ref="publication_type.atts"/><xsd:attributeGroup ref="language.atts"/><xsd:attributeGroup ref="reference_distribution_opts.att"/></xsd:complexType></xsd:element>
<xsd:element name="approval_date"><xsd:annotation><xsd:documentation>The date on which a dissertation was accepted by the institution awarding the degree, a report was approved, or a standard was accepted. approval_date includes the same elements as publication_date, but it has no attributes. It is a distinct element from publication_date to reflect that an important but different semantic meeting from publication_date</xsd:documentation></xsd:annotation><xsd:complexType><xsd:complexContent><xsd:extension base="date_t"/></xsd:complexContent></xsd:complexType></xsd:element>
<xsd:element name="institution"><xsd:annotation><xsd:documentation>Wrapper element for information about an organization that sponsored or hosted an item but is not the publisher of the item. The institution element should be used to deposit metadata about an organization that sponsored or hosted the research or development of the published material but was not actually the publisher of the information. The institution is distinctly different from the publisher because it may not be a publishing organization. It is typically an organization such as a university, corporation, government agency, NGO or consortia. If the content was published by an organization other than the sponsor, the use of both the publisher and institution elements is encouraged because authors may cite either one in a reference, and the availability of both may allow for more precise matching in queries.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="institution_name"/><xsd:element ref="institution_acronym" minOccurs="0" maxOccurs="6"/><xsd:element ref="institution_place" minOccurs="0" maxOccurs="6"/><xsd:element ref="institution_department" minOccurs="0" maxOccurs="6"/></xsd:sequence></xsd:complexType></xsd:element>
<xsd:element name="institution_name"><xsd:annotation><xsd:documentation>The full name of an institution. Examples are: World Health Organization; University of California, Davis. Corresponding institution_acronym content for these organizations would be WHO and UCD, respectively.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="1024"/><xsd:minLength value="1"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="institution_acronym"><xsd:annotation><xsd:documentation>The acronym of the institution. Note that authors often cite with acronyms and this information can be important in matching a query Examples: WHO, UCDavis, UCD Note: as shown above, an institution may be know by multiple acronyms, in which case all common acronyms should be deposited.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="255"/><xsd:minLength value="1"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="institution_place"><xsd:annotation><xsd:documentation>The primary city location of the institution. institution_place gives the primary city location of the institution. When the location is a major city (e.g. New York, Amsterdam), no qualifying country or U.S. state need be given. If the city is not a major city, the appropriate country and/or state or province should be added.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="255"/><xsd:minLength value="2"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="institution_department"><xsd:annotation><xsd:documentation>The department within an institution. institution_department gives the department within an institution. A common use is the department under which a dissertation was completed. Note that the institution_department is repeatable. If multiple departments are to be deposited, each one should be given in a unique institution_department element. Example: Department of Psychology</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="255"/><xsd:minLength value="2"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="degree"><xsd:annotation><xsd:documentation>The degree(s) awarded for a dissertation.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="255"/><xsd:minLength value="2"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="report-paper"><xsd:annotation><xsd:documentation>report-paper is the top level element for deposit of metadata about one or more reports or working papers. component_list is included in report-paper to handle items that have components but do not have content_item elements (i.e. a report that is not divided into multiple chapters). If an item has content_item elements, then component_list inside of content_item must be used rather than the element available in report-paper</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:choice><xsd:element ref="report-paper_metadata"/><xsd:element ref="report-paper_series_metadata"/></xsd:choice><xsd:element ref="content_item" minOccurs="0" maxOccurs="unbounded"/><xsd:element ref="component_list" minOccurs="0"/></xsd:sequence><xsd:attributeGroup ref="publication_type.atts"/></xsd:complexType></xsd:element>
<xsd:element name="report-paper_metadata"><xsd:annotation><xsd:documentation>report-paper_metadata is used as a wrapper for the metadata related to a Technical Report or Working Paper. report-paper_metadata is almost identical to book_metadata. It differs only in that report-paper_metadata removes the volume number and adds the elements institution and contract_number. Please see the comments for book_metadata about the usage of most elements in report- paper_metadata. Reports and Working Papers are often sponsored by either universities or by a non-academic organization (corporate or government). Such institutions are not typically considered "publishers" and so the item may be deposited using the institution element. Multiple element instances are permitted so the sponsoring institution and publishing institution can both be deposited as authors may cite either. If the report number of an item follows Z39.23, the number should be deposited in the identifier element with the id_type attribute set to "Z39.23". If a report number uses its own numbering system, it should be deposited in item_number.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="contributors" minOccurs="0"/><xsd:element ref="titles"/><xsd:element ref="edition_number" minOccurs="0"/><xsd:element ref="jats:abstract" minOccurs="0" maxOccurs="unbounded"/><xsd:element ref="publication_date" maxOccurs="10"/><xsd:element ref="approval_date" minOccurs="0" maxOccurs="10"/><xsd:element ref="isbn" minOccurs="0" maxOccurs="6"/><xsd:element ref="publisher" minOccurs="0"/><xsd:element ref="institution" minOccurs="0" maxOccurs="5"/><xsd:element ref="publisher_item" minOccurs="0"/><xsd:element ref="contract_number" minOccurs="0"/><xsd:choice><xsd:element ref="crossmark" minOccurs="0"/><xsd:sequence><xsd:element ref="fr:program" minOccurs="0" maxOccurs="1"/><xsd:element ref="ai:program" minOccurs="0" maxOccurs="1"/></xsd:sequence></xsd:choice><xsd:element ref="rel:program" minOccurs="0"/><xsd:element ref="archive_locations" minOccurs="0" maxOccurs="1"/><xsd:element ref="scn_policies" minOccurs="0" maxOccurs="1"/><xsd:element ref="doi_data" minOccurs="0"/><xsd:element ref="citation_list" minOccurs="0"/></xsd:sequence><xsd:attributeGroup ref="language.atts"/><xsd:attributeGroup ref="reference_distribution_opts.att"/></xsd:complexType></xsd:element>
<xsd:element name="contract_number"><xsd:annotation><xsd:documentation>The contract number under which a report or paper was written.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="255"/><xsd:minLength value="2"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="report-paper_series_metadata"><xsd:annotation><xsd:documentation>report-paper_series_metadata is used as a wrapper for the metadata related to a Technical Report or Working Paper that is part of a series. report-paper_series_metadata is almost identical to book_series_metadata. It differs only in that report-paper_metadata removes the volume number and adds the elements institution and contract_number. Please see the comments for book_series_metadata about the usage of most elements in report- paper_series_metadata. Reports and Working Papers are often sponsored by either universities or by a non-academic organization (corporate or government). Such institutions are not typically considered "publishers" and so the item may be deposited using the institution element. Multiple element instances are permitted so the sponsoring institution and publishing institution can both be deposited as authors may cite either. If the report number of an item follows Z39.23, the number should be deposited in the identifier element with the id_type attribute set to "Z39.23". If a report number uses its own numbering system, it should be deposited in item_number.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="series_metadata"/><xsd:element ref="contributors" minOccurs="0"/><xsd:choice><xsd:sequence><xsd:element ref="titles"/><xsd:element ref="jats:abstract" minOccurs="0" maxOccurs="unbounded"/><xsd:element ref="volume" minOccurs="0"/></xsd:sequence><xsd:element ref="volume"/></xsd:choice><xsd:element ref="edition_number" minOccurs="0"/><xsd:element ref="publication_date" maxOccurs="10"/><xsd:element ref="approval_date" minOccurs="0" maxOccurs="10"/><xsd:element ref="isbn" minOccurs="0" maxOccurs="6"/><xsd:element ref="publisher" minOccurs="0"/><xsd:element ref="institution" minOccurs="0" maxOccurs="5"/><xsd:element ref="publisher_item" minOccurs="0"/><xsd:element ref="contract_number" minOccurs="0"/><xsd:element ref="archive_locations" minOccurs="0" maxOccurs="1"/><xsd:element ref="doi_data" minOccurs="0"/><xsd:element ref="citation_list" minOccurs="0"/><xsd:element ref="rel:program" minOccurs="0"/></xsd:sequence><xsd:attributeGroup ref="language.atts"/><xsd:attributeGroup ref="reference_distribution_opts.att"/></xsd:complexType></xsd:element>
<xsd:element name="standard"><xsd:annotation><xsd:documentation>standard is the top level element for deposit of metadata about standards developed by Standards Development Organizations (SDOs) or Consortia. Crossref does not determine if a new DOI should be created for each revision or reaffirmation of a standard. The decision will be left to the individual standards organizations. As of schema version 4.3.3, Crossref recommends that the full standard designation be placed in the as_published element (within standard_designator). For backwards compatibility, the full designation may also be included in the identifier element with the id_type attribute set to "ISO-std-ref". In addition, Crossref requires that the publisher of the standard be included in standards_body_name, and the acronym within standards_acronym. The as_published and standards_acronym elements will be combined to identify a standard for query matching. component_list is included in standard to handle items that have components but do not have content_item elements (i.e. a standard that is not divided into multiple chapters). If an item has content_item elements, then component_list inside of content_item must be used rather than the parent standard element.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:choice><xsd:element ref="standard_metadata"/></xsd:choice><xsd:element ref="content_item" minOccurs="0" maxOccurs="unbounded"/><xsd:element ref="component_list" minOccurs="0"/></xsd:sequence><xsd:attributeGroup ref="publication_type.atts"/></xsd:complexType></xsd:element>
<xsd:element name="standard_metadata"><xsd:annotation><xsd:documentation>Standard_metadata is used as a wrapper for the metadata related to a Standard that is not part of a series. standard_metadata is similar to book_metadata. It differs in that standard_metadata adds the elements institution and approval_date. contributors contains the author(s) of the standard. In most cases, it is expected that the organization element will be used rather than person_name element for standards. However in some cases, standards are cited by their individual authors. In such cases, individual authors should be deposited with person_name, and the SDO or consortia name should be deposited with the organization element in contributors and also the standards_body_name element in standards_body Note that when the organization element is used in contributors, it should have the name of the committee (when appropriate) that developed the standard, not the name of the Standards Development Organization (SDO) or consortia. The SDO or consortia name should be placed in the publisher or standards_body element (as appropriate) Standards more often have version numbers than edition numbers. However the edition_number element can be used for deposit of the version number of a standard approval_date should be used for the date that a standard has been accepted or re-affirmed if different from the date of publication. Both may be provided even if identical Within publisher_item, the designation should be placed inside the item_number element, and the id_type should be set to "designation" to indicate a standard designation. Standards are typically sponsored or hosted by SDOs or Consortia. In some cases standards are published by a traditional publisher rather than by the owning organization. Such cases may be deposited with one or more publishers.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="contributors" minOccurs="0"/><xsd:element ref="titles"/><xsd:element ref="jats:abstract" minOccurs="0" maxOccurs="unbounded"/><xsd:element ref="designators" minOccurs="1" maxOccurs="1"/><xsd:element ref="edition_number" minOccurs="0"/><xsd:element ref="approval_date" minOccurs="0" maxOccurs="1"/><xsd:element ref="isbn" minOccurs="0" maxOccurs="6"/><xsd:element ref="publisher" minOccurs="0"/><xsd:element ref="standards_body"/><xsd:element ref="publisher_item" minOccurs="0"/><xsd:choice><xsd:element ref="crossmark" minOccurs="0"/><xsd:sequence><xsd:element ref="fr:program" minOccurs="0" maxOccurs="1"/><xsd:element ref="ai:program" minOccurs="0" maxOccurs="1"/></xsd:sequence></xsd:choice><xsd:element ref="rel:program" minOccurs="0"/><xsd:element ref="archive_locations" minOccurs="0" maxOccurs="1"/><xsd:element ref="doi_data" minOccurs="1" maxOccurs="1"/><xsd:element ref="citation_list" minOccurs="0"/></xsd:sequence><xsd:attribute name="publication_status" use="optional"><xsd:simpleType><xsd:restriction base="xsd:NMTOKEN"><xsd:enumeration value="released"/><xsd:enumeration value="withdrawn"/></xsd:restriction></xsd:simpleType></xsd:attribute><xsd:attributeGroup ref="language.atts"/><xsd:attributeGroup ref="reference_distribution_opts.att"/></xsd:complexType></xsd:element>
<xsd:element name="std_family_designator" type="std_designator_t"><xsd:annotation><xsd:documentation>Provides for defining a DOI for a broad grouping of standards.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="std_set_designator"><xsd:annotation><xsd:documentation>Provides for defining a DOI for a set of standards (sometimes know as truncated form).</xsd:documentation></xsd:annotation><xsd:complexType><xsd:complexContent><xsd:extension base="std_designator_t"><xsd:attribute name="family" type="xsd:string"/></xsd:extension></xsd:complexContent></xsd:complexType></xsd:element>
<xsd:element name="std_undated_designator"><xsd:annotation><xsd:documentation>Provides for defining a DOI for a group of closely related standard documents (undated form is a stem for any dated form)</xsd:documentation></xsd:annotation><xsd:complexType><xsd:complexContent><xsd:extension base="std_designator_t"><xsd:attribute name="family" type="xsd:string"/><xsd:attribute name="set" type="xsd:string"/></xsd:extension></xsd:complexContent></xsd:complexType></xsd:element>
<xsd:element name="std_as_published"><xsd:annotation><xsd:documentation>Designator or other primary identifier for the standard being deposited. Required.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:complexContent><xsd:extension base="std_designator_t"><xsd:attribute name="family" type="xsd:string"/><xsd:attribute name="set" type="xsd:string"/><xsd:attribute name="undated" type="xsd:string"/></xsd:extension></xsd:complexContent></xsd:complexType></xsd:element>
<xsd:element name="std_supersedes" type="std_designatorvalue_t"><xsd:annotation><xsd:documentation>Designator for standard being replaced by the standard being deposited.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="std_adopted_from" type="std_designatorvalue_t"><xsd:annotation><xsd:documentation>Designator for standard from which the current deposit is adopted.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="std_revision_of" type="std_designatorvalue_t"><xsd:annotation><xsd:documentation>Designator for the previous revision of the standard being deposited. (note: use alt_as_published for revisions within designators having common stem)</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="database"><xsd:annotation><xsd:documentation>database is the top level element for deposit of metadata about one or more datasets or records in a database. Database structures allow for the assignment of DOIs to entire databases at the aggregate level and at two lower levels. The top level may be a physical/functional database or a logical abstration acting as a collection much the same as a journal is a collection of articles. The need to assign specific fields of metadata at each level depends on the nature of the top most level (e.g. publication date may be appropriate at the top level for a physical object but only at lower levels for an abstract top level object) The first sub-level is the dataset which may be a basic record of the top level object or a collection in its own right. In either case dataset must represent a physical construct. A third level is provided in the component_list. NOTE: component_list in <database> (rather than in dataset may be used as a second level when no third level is required and the second level objects derive most of their qualities from the parent. NOTE: This model is not intended to show relationships between different dataset entries in the form of a relational database. However in the future it is possible that multiple resolution may be used to express such relationships</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="database_metadata"/><xsd:choice><xsd:element ref="dataset" minOccurs="0" maxOccurs="unbounded"/><xsd:element ref="component_list" minOccurs="0"/></xsd:choice></xsd:sequence></xsd:complexType></xsd:element>
<xsd:element name="database_metadata"><xsd:annotation><xsd:documentation>database_metadata contains metadata about the database. contributors contains the author(s) of the database. In most cases, it is expected that the organization element will be used rather than person_name element for the primary database authoring information. contributors should not be confused with publisher and institution. In many cases, databases are more likely to have one or both of the latter elements rather than contributors at the top level (dataset elements are more likely to have contributors). In most cases, the institution element may be the best choice to deposit the database host organization because it includes the institution_acronym element along with the name. The titles element is used to capture the name of the database. The description element can be used to capture a fuller description of the nature of the database than might be inferred from the title. database_date should be used to capture the date that a database was first created. Whenever updated records are deposited with Crossref, the update_date should be set to the date of the most recent Crossref deposit. publisher_item may be used to record an identifying number for the database other than the DOI.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="contributors" minOccurs="0"/><xsd:element ref="titles"/><xsd:element ref="description" minOccurs="0"/><xsd:element ref="database_date" minOccurs="0" maxOccurs="10"/><xsd:element ref="publisher" minOccurs="0"/><xsd:element ref="institution" minOccurs="0" maxOccurs="10"/><xsd:element ref="publisher_item" minOccurs="0"/><xsd:element ref="archive_locations" minOccurs="0" maxOccurs="1"/><xsd:element ref="doi_data" minOccurs="0"/><xsd:element ref="rel:program" minOccurs="0"/></xsd:sequence><xsd:attributeGroup ref="language.atts"/><xsd:attributeGroup ref="reference_distribution_opts.att"/></xsd:complexType></xsd:element>
<xsd:element name="database_date"><xsd:annotation><xsd:documentation>database_date records key dates in the life of a database or dataset item. Within database_date, creation_date is the date the item was first created, publication_date is the date the item was first published, and update_date is the date the item was last updated.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="creation_date" minOccurs="0"/><xsd:element ref="publication_date" minOccurs="0"/><xsd:element ref="update_date" minOccurs="0"/></xsd:sequence></xsd:complexType></xsd:element>
<xsd:element name="creation_date"><xsd:annotation><xsd:documentation>The date a database or dataset item was created.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:complexContent><xsd:extension base="date_t"/></xsd:complexContent></xsd:complexType></xsd:element>
<xsd:element name="update_date"><xsd:annotation><xsd:documentation>The date a database or dataset item was updated.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:complexContent><xsd:extension base="date_t"/></xsd:complexContent></xsd:complexType></xsd:element>
<xsd:element name="dataset"><xsd:annotation><xsd:documentation>dataset is used to capture information about one or more database records or collections. The dataset_type attribute should be set to either "record" or "collection" to indicate the type of deposit. The default value of this attribute is "record". dataset entries are not intended to contain the entire database record or collection. They are only intended to contain the metadata for each database record or collection. The metadata can include: contributors: the author(s) of a database record or collection titles: the title of a database record or collection database_date: the creation date, publication date (if different from the creation date) and the date of last update of the record publisher_item: the record number of the dataset item. In this context, publisher_item can be used for the record number of each item in the database. description: a brief summary description of the contents of the database format: the format type of the dataset item if it includes files rather than just text. Note the format element here should not be used to describe the format of items deposited as part of the component_list doi_data: the doi of the item. citation_list: a list of items (e.g. journal articles) cited by the dataset item. For example, dataset entry from a taxonomy might cite the article in which a species was first identified. component_list: a list of components included in the dataset item such as supporting figures</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="contributors" minOccurs="0"/><xsd:element ref="titles" minOccurs="0"/><xsd:element ref="database_date" minOccurs="0" maxOccurs="10"/><xsd:element ref="publisher_item" minOccurs="0"/><xsd:element ref="description" minOccurs="0"/><xsd:element ref="format" minOccurs="0"/><xsd:choice><xsd:element ref="crossmark" minOccurs="0"/><xsd:sequence><xsd:element ref="fr:program" minOccurs="0" maxOccurs="1"/><xsd:element ref="ai:program" minOccurs="0" maxOccurs="1"/></xsd:sequence></xsd:choice><xsd:element ref="rel:program" minOccurs="0"/><xsd:element ref="archive_locations" minOccurs="0" maxOccurs="1"/><xsd:element ref="doi_data"/><xsd:element ref="citation_list" minOccurs="0"/><xsd:element ref="component_list" minOccurs="0"/></xsd:sequence><xsd:attribute name="dataset_type" default="record"><xsd:simpleType><xsd:restriction base="xsd:NMTOKEN"><xsd:enumeration value="record"/><xsd:enumeration value="collection"/><xsd:enumeration value="crossmark_policy"/><xsd:enumeration value="other"/></xsd:restriction></xsd:simpleType></xsd:attribute></xsd:complexType></xsd:element>
<xsd:element name="review_date"><xsd:annotation><xsd:documentation>The date a review was published to a repository.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="month"/><xsd:element ref="day"/><xsd:element ref="year"/></xsd:sequence></xsd:complexType></xsd:element>
<xsd:element name="competing_interest_statement"><xsd:annotation><xsd:documentation>Statement of competing interest supplied by a review author during the review process.</xsd:documentation></xsd:annotation><xsd:complexType mixed="true"><xsd:choice minOccurs="0" maxOccurs="unbounded"><xsd:group ref="face_markup"/></xsd:choice><xsd:attributeGroup ref="language.atts"/></xsd:complexType></xsd:element>
<xsd:element name="running_number" type="xsd:string"><xsd:annotation><xsd:documentation>Running numbers to specify the various reports (ex: RC1 to RC4)</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="pending_publication"><xsd:annotation><xsd:documentation>Pending publication (formeraly knows as Pre-register or early content registration) DOIs are used to create a DOI for a content item that is not yet available online or in print. The intended use is for a pubisher to create the DOI upon manuscript acceptance where publication might not occur for some period. This establishes the acceptance date and intent to publish and provides on online presence that allows confirmation of intent to publish. The URL for early content DOIs will point to a page maintained by Crossref. Early content registration is intended for titles that have already been deposited at Crossref. Therefor the publication data provided must identify a title (journal or book) that already exists within the Crossref system</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="contributors" minOccurs="0"/><xsd:element ref="publication"/><xsd:element ref="titles" minOccurs="0"/><xsd:element ref="acceptance_date" minOccurs="1" maxOccurs="1"/><xsd:element ref="institution" minOccurs="0" maxOccurs="5"/><xsd:element ref="item_number" minOccurs="0" maxOccurs="3"/><xsd:element ref="intent_statement" minOccurs="0" maxOccurs="1"/><xsd:element ref="jats:abstract" minOccurs="0" maxOccurs="unbounded"/><xsd:choice><xsd:element ref="crossmark" minOccurs="0"/><xsd:sequence><xsd:element ref="fr:program" minOccurs="0" maxOccurs="1"/><xsd:element ref="ai:program" minOccurs="0" maxOccurs="1"/></xsd:sequence></xsd:choice><xsd:element ref="rel:program" minOccurs="0"/><xsd:element ref="doi" minOccurs="1" maxOccurs="1"/></xsd:sequence><xsd:attributeGroup ref="language.atts"/></xsd:complexType></xsd:element>
<xsd:element name="publication"><xsd:annotation><xsd:documentation>Used to define a publication (book, journal, etc) for pending publication content. A title must be supplied, as well as an ISSN, ISBN, or title-level DOI</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="full_title" maxOccurs="10"/><xsd:choice><xsd:sequence><xsd:choice><xsd:element ref="issn" minOccurs="1" maxOccurs="1"/><xsd:element ref="isbn" minOccurs="1" maxOccurs="1"/></xsd:choice></xsd:sequence><xsd:sequence><xsd:element ref="doi" minOccurs="1" maxOccurs="1"/><xsd:choice><xsd:element ref="issn" minOccurs="0" maxOccurs="1"/><xsd:element ref="isbn" minOccurs="0" maxOccurs="1"/></xsd:choice></xsd:sequence></xsd:choice></xsd:sequence></xsd:complexType></xsd:element>
<xsd:element name="intent_statement"><xsd:annotation><xsd:documentation>Publisher's custom statement for their intent to publish content for which a pre-register DOI has been created</xsd:documentation></xsd:annotation><xsd:complexType mixed="true"><xsd:choice minOccurs="0" maxOccurs="unbounded"><xsd:element ref="b"/><xsd:element ref="i"/><xsd:element ref="u"/><xsd:element ref="a"/></xsd:choice><xsd:attributeGroup ref="language.atts"/></xsd:complexType></xsd:element>
<xsd:element name="a"><xsd:annotation><xsd:documentation>content is "Inline" except that anchors shouldn't be nested</xsd:documentation></xsd:annotation><xsd:complexType mixed="true"><xsd:simpleContent><xsd:extension base="xsd:string"><xsd:attribute name="href" type="xsd:anyURI"/></xsd:extension></xsd:simpleContent></xsd:complexType></xsd:element>
<xsd:element name="posted_content"><xsd:annotation><xsd:documentation>Posted-content is for the assignment of DOIs to content that may subsequently be formally published. Non-DOI identifiers associated with the content may be recorded in the item_number element. We encourage the inclussion of an abstract. The relation program (rel:program) should be used to link this content item to other DOIs including the DOI of the published version of record. Pre-print should not be used to assign DOIs to accepted manuscripts. A DOI may be assigned to an accepted manuscript using the content type appropriate for early registration. DOIs assigned to accepted manuscripts should be reused (e.g. reassigned to the published article). POsted-contnet DOIs must be continuously supported by maintaining their metadata and the URL at which the content is available.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="group_title" minOccurs="0" maxOccurs="1"/><xsd:element ref="contributors" minOccurs="0"/><xsd:element ref="titles"/><xsd:element ref="posted_date" minOccurs="1" maxOccurs="1"/><xsd:element ref="acceptance_date" minOccurs="0" maxOccurs="1"/><xsd:element ref="institution" minOccurs="0" maxOccurs="5"/><xsd:element ref="item_number" minOccurs="0" maxOccurs="3"/><xsd:element ref="jats:abstract" minOccurs="0" maxOccurs="unbounded"/><xsd:element maxOccurs="1" ref="fr:program" minOccurs="0"/><xsd:element ref="ai:program" minOccurs="0" maxOccurs="1"/><xsd:element ref="rel:program" minOccurs="0"/><xsd:element ref="scn_policies" minOccurs="0" maxOccurs="1"/><!-- cs-3495 --><xsd:element ref="doi_data" minOccurs="1"/><xsd:element ref="citation_list" minOccurs="0"/></xsd:sequence><xsd:attribute name="type" default="preprint"><xsd:simpleType><xsd:restriction base="xsd:NMTOKEN"><xsd:enumeration value="preprint"/><xsd:enumeration value="working_paper"/><xsd:enumeration value="letter"/><xsd:enumeration value="dissertation"/><xsd:enumeration value="report"/><xsd:enumeration value="review"/><xsd:enumeration value="other"/></xsd:restriction></xsd:simpleType></xsd:attribute><xsd:attributeGroup ref="language.atts"/></xsd:complexType></xsd:element>
<xsd:element name="group_title"><xsd:annotation><xsd:documentation>Prepublication content items may be organzed into groupings within a given publisher. This element provides for naming the group. It is expected that publishers will have a small number of groups each of which reflect a topic or subject area.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="1024"/><xsd:minLength value="1"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="posted_date"><xsd:annotation><xsd:documentation>The date a pre-print was posted to a repository.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:complexContent><xsd:extension base="date_t"/></xsd:complexContent></xsd:complexType></xsd:element>
<xsd:element name="property"><xsd:annotation><xsd:documentation>property elements qualify the semantic meaning of a item or collection. property elements consist of a type/value pair where the property type is found in the type attribute and the value is found in the element content. The property element is not currently in use.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:simpleContent><xsd:extension base="property_t"><xsd:attribute name="type" type="xsd:string" use="required"/></xsd:extension></xsd:simpleContent></xsd:complexType></xsd:element>
<xsd:element name="content_date"><xsd:annotation><xsd:documentation>The date a content item was created.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:complexContent><xsd:extension base="date_t"/></xsd:complexContent></xsd:complexType></xsd:element>
<xsd:element name="unassigned_content"><xsd:annotation><xsd:documentation>Normally book content that is published as a series is required to have a series title with an ISSN and a book title and/or a book volume number along with a book ISBN. An exception is when book chapters are published on line first prior to being assigned to a specific book in which case only the series title (and ISSN) is known at time of DOI registration. Element unassigned_content is used as a placeholder to force recognition of this condition and thus prevent accidental omission of book level title information. When unassigned_content is present the system will allow omission of the ISBN. If unassigned_content is not present the system will require an ISBN for the book title.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:attribute name="type" use="required"><xsd:simpleType><xsd:restriction base="xsd:NMTOKEN"><xsd:enumeration value="aheadOfPrint"/></xsd:restriction></xsd:simpleType></xsd:attribute></xsd:complexType></xsd:element>
<xsd:simpleType name="xrefYear"><xsd:annotation><xsd:documentation>The following are basic data types for date parts.</xsd:documentation></xsd:annotation><xsd:restriction base="xsd:positiveInteger"><xsd:maxInclusive value="2200"/><xsd:minInclusive value="1400"/><xsd:totalDigits value="4"/></xsd:restriction></xsd:simpleType>
<xsd:attributeGroup name="reference_distribution_opts.att"><xsd:annotation><xsd:documentation>Use to flag references for distribution. "none" is the default and follows current protocol - references are only distributed to everyone if the prefix level permission is set, otherwise reference distribution is limited to the DOI owner. Setting the value to "query" releases references to anyone making a query request (this overrides any established prefix level permission). Value "any" allows bulk distribution to anyone (using a Crossref query account) using the OAI-PMH protocol, and also releases references to anyone making a query request.</xsd:documentation></xsd:annotation><xsd:attribute name="reference_distribution_opts" use="optional" default="none"><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:enumeration value="none"/><xsd:enumeration value="query"/><xsd:enumeration value="any"/></xsd:restriction></xsd:simpleType></xsd:attribute></xsd:attributeGroup>
<xsd:attributeGroup name="citation_key.atts"><xsd:annotation><xsd:documentation>citation_key allows the publisher to assign a unique ID to each citation that is deposited. It is recommended that this attribute be given the reference number if the publication uses reference numbers. For those publications that use name/date style citations, it is recommended that this attribute be used to indicate the sequential number of the citation in the reference list. However, some schema must be utilized as this is a required attribute. The system will use this key value to track the specific reference query and will return this value along with the DOI.</xsd:documentation></xsd:annotation><xsd:attribute name="key" use="required"><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:minLength value="1"/><xsd:maxLength value="128"/><xsd:whiteSpace value="collapse"/></xsd:restriction></xsd:simpleType></xsd:attribute></xsd:attributeGroup>