Showing:

Annotations
Attributes
Diagrams
Facets
Instances
Properties
Source
Used by
Main schema doi_resources4.3.6.xsd
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Properties
attribute form default: unqualified
element form default: unqualified
Included schema common4.3.7.xsd
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Properties
attribute form default: unqualified
element form default: unqualified
Included schema mathml3-content.xsd
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Properties
attribute form default: unqualified
element form default: qualified
Included schema mathml3-strict-content.xsd
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Properties
attribute form default: unqualified
element form default: qualified
Included schema mathml3-presentation.xsd
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Properties
attribute form default: unqualified
element form default: qualified
Included schema mathml3-common.xsd
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Properties
attribute form default: unqualified
element form default: qualified
Included schema common4.3.5.xsd
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Properties
attribute form default: unqualified
element form default: unqualified
Element doi_batch
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Diagram
Diagram NO_NAMESPACE.tmp#doi_batch_version 4_3_6.tmp#head 4_3_6.tmp#body
Properties
content: complex
Model head , body
Children body, head
Instance
<doi_batch version="4.3.6">
  <head>{1,1}</head>
  <body>{1,1}</body>
</doi_batch>
Attributes
QName Type Fixed Default Use Annotation
version xsd:string 4.3.6 optional
Source
<xsd:element name="doi_batch">
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element ref="head"/>
      <xsd:element ref="body"/>
    </xsd:sequence>
    <xsd:attribute name="version" type="xsd:string" fixed="4.3.6"/>
  </xsd:complexType>
</xsd:element>
Element head
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Diagram
Diagram 4_3_6.tmp#doi_batch_id 4_3_6.tmp#depositor
Properties
content: complex
Used by
Element doi_batch
Model doi_batch_id , depositor
Children depositor, doi_batch_id
Instance
<head>
  <doi_batch_id>{1,1}</doi_batch_id>
  <depositor>{1,1}</depositor>
</head>
Source
<xsd:element name="head">
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element ref="doi_batch_id"/>
      <xsd:element ref="depositor"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
Element doi_batch_id
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Annotations
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 insure that this number is unique
for every submission to CrossRef.
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
minLength 4
maxLength 100
Used by
Element head
Source
<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 insure 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>
Element depositor
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Annotations
Information about the organization submitting DOI metadata to
CrossRef
Diagram
Diagram 4_3_6.tmp#depositor_name 4_3_6.tmp#email_address
Properties
content: complex
Used by
Element head
Model depositor_name , email_address
Children depositor_name, email_address
Instance
<depositor>
  <depositor_name>{1,1}</depositor_name>
  <email_address>{1,1}</email_address>
</depositor>
Source
<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>
Element depositor_name
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Annotations
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.
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
minLength 1
maxLength 130
Used by
Element depositor
Source
<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>
Element email_address
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Annotations
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.
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
minLength 6
maxLength 200
pattern [\p{L}\p{N}!/+\-_]+(\.[\p{L}\p{N}!/+\-_]+)*@[\p{L}\p{N}!/+\-_]+(\.[\p{L}_-]+)+
Used by
Element depositor
Source
<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>
Element body
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Diagram
Diagram 4_3_6.tmp#doi_citations 4_3_6.tmp#doi_resources 4_3_6.tmp#crossmark_data 4_3_6.tmp#fundref_data 4_3_6.tmp#lic_ref_data 4_3_6.tmp#doi_relations 4_3_6.tmp#clinicaltrial_data
Properties
content: complex
Used by
Element doi_batch
Model doi_citations* , doi_resources* , crossmark_data* , fundref_data* , lic_ref_data* , doi_relations* , clinicaltrial_data*
Children clinicaltrial_data, crossmark_data, doi_citations, doi_relations, doi_resources, fundref_data, lic_ref_data
Instance
<body>
  <doi_citations>{0,unbounded}</doi_citations>
  <doi_resources>{0,unbounded}</doi_resources>
  <crossmark_data>{0,unbounded}</crossmark_data>
  <fundref_data>{0,unbounded}</fundref_data>
  <lic_ref_data>{0,unbounded}</lic_ref_data>
  <doi_relations>{0,unbounded}</doi_relations>
  <clinicaltrial_data>{0,unbounded}</clinicaltrial_data>
</body>
Source
<xsd:element name="body">
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element ref="doi_citations" minOccurs="0" maxOccurs="unbounded"/>
      <xsd:element ref="doi_resources" minOccurs="0" maxOccurs="unbounded"/>
      <xsd:element ref="crossmark_data" minOccurs="0" maxOccurs="unbounded"/>
      <xsd:element ref="fundref_data" minOccurs="0" maxOccurs="unbounded"/>
      <xsd:element ref="lic_ref_data" minOccurs="0" maxOccurs="unbounded"/>
      <xsd:element ref="doi_relations" minOccurs="0" maxOccurs="unbounded"/>
      <xsd:element ref="clinicaltrial_data" minOccurs="0" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
Element doi_citations
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Diagram
Diagram 4_3_6.tmp#doi 4_3_6.tmp#citation_list
Properties
content: complex
Used by
Element body
Model doi , citation_list
Children citation_list, doi
Instance
<doi_citations>
  <doi>{1,1}</doi>
  <citation_list>{1,1}</citation_list>
</doi_citations>
Source
<xsd:element name="doi_citations">
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element ref="doi"/>
      <xsd:element ref="citation_list"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
Element doi
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Annotations
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 http://help.crossref.org/#ID5755
Diagram
Diagram
Type doi_t
Type hierarchy
Properties
content: simple
Facets
minLength 6
maxLength 2048
Used by
Source
<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 http://help.crossref.org/#ID5755</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="doi_t"/>
  </xsd:simpleType>
</xsd:element>
Element citation_list
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Annotations
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.
Diagram
Diagram 4_3_6.tmp#citation
Properties
content: complex
Used by
Element doi_citations
Model citation*
Children citation
Instance
<citation_list>
  <citation key="">{0,unbounded}</citation>
</citation_list>
Source
<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>
Element citation
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Annotations
citation is used to deposit each citation in the reference list of
the item for which the DOI is being deposited. The citations in the list will be run
by the CrossRef system as queries looking for the DOI of the articles being cited.
NOTE: Because the citation list is used to support forward linking, the more
information supplied in the citation the better the chance of finding a match. For
each citation that is deposited, one of four models should be used: 1. Parsed
journal data 2. Parsed book or conference data 3. DOI 4. Unstructured citation (not
yet supported for resolution) When parsed journal, book or conference data is
deposited, CrossRef will perform a lookup to find the DOI. Each citation must be
given a unique ID in the key attribute. It is recommended that this number be the
citation number if the reference list is numbered in the published article, or the
underlying XML ID if the reference list is name/date style in article. When
submitting a journal citation, it should include an issn, journal_title or both.
journal_title only is preferred over issn only. In addition the first author and
first_page number should be submitted. The first_page number is preferred, but for
those citations that are "in press", the author should be submitted. All elements
are optional, however for best linking results, as much information as is known
should be submitted. When submitting a book or conference citation, it should
include an isbn, series_title, volume_title, or any combination of these three
elements as may be available. All elements are optional, however for best linking
results, as much information as is known should be submitted. When a DOI is already
known for a citation, you may submit just the doi without additional information.
When parsed information is not available for a citation, or the citation is of a
type other than journal, book, or conference proceeding that is supported by
CrossRef (e.g. standard, patent, thesis, newspaper, personal communication, etc.),
it may be submitted using the unstructured_citation element. CrossRef is able to
process some unstructured citations. When submitting unstructured citations, it is
helpful, but not required to include all available face markup (e.g. bold, italic,
etc) as this will make possible future parsing of the unstructured citation more
accurate. In such cases, it is preferred, but not required, if the citation number
(when Vancouver style is used) be removed from the unparsed citation. This number
can be submitted using the key attribute Only the first author of a citation should
be submitted, not the entire author list. Only the surname is required. Initials may
be included, but are not recommended because the best linking results can be
provided if initials are omitted. Author titles, roles and generation information
should not be included. If the first author is an organization, the organization
name should be submitted in the author 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", whenever possible. Citations that are "in press" should be
submitted with as much information as is available.
Diagram
Diagram 4_3_6.tmp#issn 4_3_6.tmp#journal_title 4_3_6.tmp#author 4_3_6.tmp#volume 4_3_6.tmp#issue 4_3_6.tmp#first_page 4_3_6.tmp#cYear 4_3_6.tmp#doi 4_3_6.tmp#isbn 4_3_6.tmp#series_title 4_3_6.tmp#volume_title 4_3_6.tmp#edition_number 4_3_6.tmp#component_number 4_3_6.tmp#article_title 4_3_6.tmp#std_designator 4_3_6.tmp#standards_body 4_3_6.tmp#unstructured_citation 4_3_6.tmp#citation_t 4_3_6.tmp#citation_key.atts
Type extension of citation_t
Type hierarchy
Properties
content: complex
Used by
Element citation_list
Model ALL(issn{0,1} journal_title{0,1} author{0,1} volume{0,1} issue{0,1} first_page{0,1} cYear{0,1} doi{0,1} isbn{0,1} series_title{0,1} volume_title{0,1} edition_number{0,1} component_number{0,1} article_title{0,1} std_designator{0,1} standards_body{0,1} unstructured_citation{0,1})
Children article_title, author, cYear, component_number, doi, edition_number, first_page, isbn, issn, issue, journal_title, series_title, standards_body, std_designator, unstructured_citation, volume, volume_title
Instance
<citation key="">
  <issn media_type="print">{0,1}</issn>
  <journal_title>{0,1}</journal_title>
  <author>{0,1}</author>
  <volume>{0,1}</volume>
  <issue>{0,1}</issue>
  <first_page>{0,1}</first_page>
  <cYear>{0,1}</cYear>
  <doi>{0,1}</doi>
  <isbn media_type="print">{0,1}</isbn>
  <series_title>{0,1}</series_title>
  <volume_title>{0,1}</volume_title>
  <edition_number>{0,1}</edition_number>
  <component_number>{0,1}</component_number>
  <article_title>{0,1}</article_title>
  <std_designator>{0,1}</std_designator>
  <standards_body>{0,1}</standards_body>
  <unstructured_citation>{0,1}</unstructured_citation>
</citation>
Attributes
QName Type Fixed Default Use Annotation
key xsd:string required
Source
<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. The citations in the list will be run by the CrossRef system as queries looking for the DOI of the articles being cited. NOTE: Because the citation list is used to support forward linking, the more information supplied in the citation the better the chance of finding a match. For each citation that is deposited, one of four models should be used: 1. Parsed journal data 2. Parsed book or conference data 3. DOI 4. Unstructured citation (not yet supported for resolution) When parsed journal, book or conference data is deposited, CrossRef will perform a lookup to find the DOI. Each citation must be given a unique ID in the key attribute. It is recommended that this number be the citation number if the reference list is numbered in the published article, or the underlying XML ID if the reference list is name/date style in article. When submitting a journal citation, it should include an issn, journal_title or both. journal_title only is preferred over issn only. In addition the first author and first_page number should be submitted. The first_page number is preferred, but for those citations that are "in press", the author should be submitted. All elements are optional, however for best linking results, as much information as is known should be submitted. When submitting a book or conference citation, it should include an isbn, series_title, volume_title, or any combination of these three elements as may be available. All elements are optional, however for best linking results, as much information as is known should be submitted. When a DOI is already known for a citation, you may submit just the doi without additional information. When parsed information is not available for a citation, or the citation is of a type other than journal, book, or conference proceeding that is supported by CrossRef (e.g. standard, patent, thesis, newspaper, personal communication, etc.), it may be submitted using the unstructured_citation element. CrossRef is able to process some unstructured citations. When submitting unstructured citations, it is helpful, but not required to include all available face markup (e.g. bold, italic, etc) as this will make possible future parsing of the unstructured citation more accurate. In such cases, it is preferred, but not required, if the citation number (when Vancouver style is used) be removed from the unparsed citation. This number can be submitted using the key attribute Only the first author of a citation should be submitted, not the entire author list. Only the surname is required. Initials may be included, but are not recommended because the best linking results can be provided if initials are omitted. Author titles, roles and generation information should not be included. If the first author is an organization, the organization name should be submitted in the author 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", whenever possible. Citations that are "in press" should be submitted with as much information as is available.</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>
Element issn
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Annotations
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.
Diagram
Diagram 4_3_6.tmp#issn_t 4_3_6.tmp#media_type.atts
Type extension of issn_t
Type hierarchy
Properties
content: complex
Used by
Complex Type citation_t
Element citation
Attributes
QName Type Fixed Default Use Annotation
media_type restriction of xsd:NMTOKEN print optional
Source
<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>
Element journal_title
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Annotations
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.
Diagram
Diagram
Type xsd:string
Properties
content: simple
Used by
Complex Type citation_t
Element citation
Source
<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>
Element author
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Annotations
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>
Diagram
Diagram
Type xsd:string
Properties
content: simple
Used by
Complex Type citation_t
Element citation
Source
<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>
Element volume
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Annotations
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.
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
minLength 1
maxLength 32
Used by
Complex Type citation_t
Element citation
Source
<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>
Element issue
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Annotations
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>
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
minLength 1
maxLength 32
Used by
Complex Type citation_t
Element citation
Source
<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>
Element first_page
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Annotations
First page number where an entity is located. Data may be alpha,
numeric or a combination.
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
minLength 1
maxLength 32
Used by
Complex Type citation_t
Elements citation, pages
Source
<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>
Element cYear
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Annotations
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.
Diagram
Diagram
Type xsd:string
Properties
content: simple
Used by
Complex Type citation_t
Element citation
Source
<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>
Element isbn
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Annotations
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.
Diagram
Diagram 4_3_6.tmp#isbn_t 4_3_6.tmp#media_type.atts
Type extension of isbn_t
Type hierarchy
Properties
content: complex
Used by
Complex Type citation_t
Element citation
Attributes
QName Type Fixed Default Use Annotation
media_type restriction of xsd:NMTOKEN print optional
Source
<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>
Element series_title
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Annotations
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.
Diagram
Diagram
Type xsd:string
Properties
content: simple
Used by
Complex Type citation_t
Element citation
Source
<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>
Element volume_title
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Annotations
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.
Diagram
Diagram
Type xsd:string
Properties
content: simple
Used by
Complex Type citation_t
Element citation
Source
<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>
Element edition_number
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Annotations
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>
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
minLength 1
maxLength 15
Used by
Complex Type citation_t
Element citation
Source
<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>
Element component_number
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Annotations
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.
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
minLength 1
maxLength 50
Used by
Complex Type citation_t
Element citation
Source
<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>
Element article_title
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Annotations
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.
Diagram
Diagram
Type xsd:string
Properties
content: simple
Used by
Complex Type citation_t
Element citation
Source
<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>
Element std_designator
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Diagram
Diagram 4_3_6.tmp#std_designatorvalue_t
Type std_designatorvalue_t
Properties
content: simple
Facets
minLength 2
maxLength 150
Used by
Source
<xsd:element name="std_designator" type="std_designatorvalue_t"/>
Element standards_body
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Annotations
A wrapper for standards body information.
Diagram
Diagram 4_3_6.tmp#standards_body_name 4_3_6.tmp#standards_body_acronym
Properties
content: complex
Used by
Complex Type citation_t
Element citation
Model standards_body_name , standards_body_acronym
Children standards_body_acronym, standards_body_name
Instance
<standards_body>
  <standards_body_name>{1,1}</standards_body_name>
  <standards_body_acronym>{1,1}</standards_body_acronym>
</standards_body>
Source
<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>
Element standards_body_name
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Annotations
Name of the standards organization / publisher.
Required.
Diagram
Diagram
Used by
Element standards_body
Source
<xsd:element name="standards_body_name">
  <xsd:annotation>
    <xsd:documentation>Name of the standards organization / publisher. Required.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
Element standards_body_acronym
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Annotations
Acronym for standards body. Will be used for query matching -
required.
Diagram
Diagram
Used by
Element standards_body
Source
<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>
Element unstructured_citation
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Annotations
A citation that is to an item other than a journal article, book, or
conference paper and cannot be structured with the CrossRef citation model. Also, it
is used for a citation to a journal article, book, or conference paper for which the
depositing publisher does not have structured information. unstructured_citation
allows a publisher to deposit references for which no structural information is
available. These may be journal, book, or conference references for which the
supplier did not provide markup, or other types of references (e.g. standards,
patents, etc) which are not supported by CrossRef. This structure permits publishers
to deposit complete reference lists, without regard to the availability of markup,
or the need to parse references beyond those types that CrossRef supports.
CrossRef's ability to process unstructured citations is limited, for details see
http://help.crossref.org/#ID38855
Diagram
Diagram 4_3_6.tmp#b 4_3_6.tmp#i 4_3_6.tmp#u 4_3_6.tmp#ovl 4_3_6.tmp#sup 4_3_6.tmp#sub 4_3_6.tmp#scp 4_3_6.tmp#tt 4_3_6.tmp#font MathML.tmp#math 4_3_6.tmp#face_markup
Properties
content: complex
mixed: true
Used by
Complex Type citation_t
Element citation
Model b | i | u | ovl | sup | sub | scp | tt | font | m:math
Children b, font, i, m:math, ovl, scp, sub, sup, tt, u
Instance
<unstructured_citation>
  <b>{1,1}</b>
  <i>{1,1}</i>
  <u>{1,1}</u>
  <ovl>{1,1}</ovl>
  <sup>{1,1}</sup>
  <sub>{1,1}</sub>
  <scp>{1,1}</scp>
  <tt>{1,1}</tt>
  <font>{1,1}</font>
  <m:math accent="" accentunder="" align="" alignmentscope="" altimg="" altimg-height="" altimg-valign="" altimg-width="" alttext="" bevelled="" cdgroup="" charalign="" charspacing="" class="" close="" columnalign="" columnlines="" columnspacing="" columnspan="" columnwidth="" crossout="" decimalpoint="" denomalign="" depth="" dir="" display="" displaystyle="" edge="" equalcolumns="" equalrows="" fence="" form="" frame="" framespacing="" groupalign="" height="" href="" id="" indentalign="" indentalignfirst="" indentalignlast="" indentshift="" indentshiftfirst="" indentshiftlast="" indenttarget="" infixlinebreakstyle="" largeop="" leftoverhang="" length="" linebreak="" linebreakmultchar="" linebreakstyle="" lineleading="" linethickness="" location="" longdivstyle="" lquote="" lspace="" macros="" mathbackground="" mathcolor="" mathsize="" mathvariant="" maxsize="" maxwidth="" minlabelspacing="" minsize="" mode="" movablelimits="" mslinethickness="" notation="" numalign="" open="" other="" overflow="" position="" rightoverhang="" rowalign="" rowlines="" rowspacing="" rowspan="" rquote="" rspace="" scriptlevel="" scriptminsize="" scriptsizemultiplier="" selection="" separator="" separators="" shift="" side="" stackalign="" stretchy="" style="" subscriptshift="" superscriptshift="" symmetric="" valign="" width="" xref="">{1,1}</m:math>
</unstructured_citation>
Source
<xsd:element name="unstructured_citation">
  <xsd:annotation>
    <xsd:documentation>A citation that is to an item other than a journal article, book, or conference paper and cannot be structured with the CrossRef citation model. Also, it is used for a citation to a journal article, book, or conference paper for which the depositing publisher does not have structured information. unstructured_citation allows a publisher to deposit references for which no structural information is available. These may be journal, book, or conference references for which the supplier did not provide markup, or other types of references (e.g. standards, patents, etc) which are not supported by CrossRef. This structure permits publishers to deposit complete reference lists, without regard to the availability of markup, or the need to parse references beyond those types that CrossRef supports. CrossRef's ability to process unstructured citations is limited, for details see http://help.crossref.org/#ID38855</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>
Element b
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Diagram
Diagram 4_3_6.tmp#b 4_3_6.tmp#i 4_3_6.tmp#u 4_3_6.tmp#ovl 4_3_6.tmp#sup 4_3_6.tmp#sub 4_3_6.tmp#scp 4_3_6.tmp#tt 4_3_6.tmp#font MathML.tmp#math 4_3_6.tmp#face_markup 4_3_6.tmp#xrefFaces
Type xrefFaces
Properties
content: complex
mixed: true
Used by
Element Group face_markup
Model b | i | u | ovl | sup | sub | scp | tt | font | m:math
Children b, font, i, m:math, ovl, scp, sub, sup, tt, u
Instance
<b>
  <b>{1,1}</b>
  <i>{1,1}</i>
  <u>{1,1}</u>
  <ovl>{1,1}</ovl>
  <sup>{1,1}</sup>
  <sub>{1,1}</sub>
  <scp>{1,1}</scp>
  <tt>{1,1}</tt>
  <font>{1,1}</font>
  <m:math accent="" accentunder="" align="" alignmentscope="" altimg="" altimg-height="" altimg-valign="" altimg-width="" alttext="" bevelled="" cdgroup="" charalign="" charspacing="" class="" close="" columnalign="" columnlines="" columnspacing="" columnspan="" columnwidth="" crossout="" decimalpoint="" denomalign="" depth="" dir="" display="" displaystyle="" edge="" equalcolumns="" equalrows="" fence="" form="" frame="" framespacing="" groupalign="" height="" href="" id="" indentalign="" indentalignfirst="" indentalignlast="" indentshift="" indentshiftfirst="" indentshiftlast="" indenttarget="" infixlinebreakstyle="" largeop="" leftoverhang="" length="" linebreak="" linebreakmultchar="" linebreakstyle="" lineleading="" linethickness="" location="" longdivstyle="" lquote="" lspace="" macros="" mathbackground="" mathcolor="" mathsize="" mathvariant="" maxsize="" maxwidth="" minlabelspacing="" minsize="" mode="" movablelimits="" mslinethickness="" notation="" numalign="" open="" other="" overflow="" position="" rightoverhang="" rowalign="" rowlines="" rowspacing="" rowspan="" rquote="" rspace="" scriptlevel="" scriptminsize="" scriptsizemultiplier="" selection="" separator="" separators="" shift="" side="" stackalign="" stretchy="" style="" subscriptshift="" superscriptshift="" symmetric="" valign="" width="" xref="">{1,1}</m:math>
</b>
Source
<xsd:element name="b" type="xrefFaces"/>
Element i
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Diagram
Diagram 4_3_6.tmp#b 4_3_6.tmp#i 4_3_6.tmp#u 4_3_6.tmp#ovl 4_3_6.tmp#sup 4_3_6.tmp#sub 4_3_6.tmp#scp 4_3_6.tmp#tt 4_3_6.tmp#font MathML.tmp#math 4_3_6.tmp#face_markup 4_3_6.tmp#xrefFaces
Type xrefFaces
Properties
content: complex
mixed: true
Used by
Element Group face_markup
Model b | i | u | ovl | sup | sub | scp | tt | font | m:math
Children b, font, i, m:math, ovl, scp, sub, sup, tt, u
Instance
<i>
  <b>{1,1}</b>
  <i>{1,1}</i>
  <u>{1,1}</u>
  <ovl>{1,1}</ovl>
  <sup>{1,1}</sup>
  <sub>{1,1}</sub>
  <scp>{1,1}</scp>
  <tt>{1,1}</tt>
  <font>{1,1}</font>
  <m:math accent="" accentunder="" align="" alignmentscope="" altimg="" altimg-height="" altimg-valign="" altimg-width="" alttext="" bevelled="" cdgroup="" charalign="" charspacing="" class="" close="" columnalign="" columnlines="" columnspacing="" columnspan="" columnwidth="" crossout="" decimalpoint="" denomalign="" depth="" dir="" display="" displaystyle="" edge="" equalcolumns="" equalrows="" fence="" form="" frame="" framespacing="" groupalign="" height="" href="" id="" indentalign="" indentalignfirst="" indentalignlast="" indentshift="" indentshiftfirst="" indentshiftlast="" indenttarget="" infixlinebreakstyle="" largeop="" leftoverhang="" length="" linebreak="" linebreakmultchar="" linebreakstyle="" lineleading="" linethickness="" location="" longdivstyle="" lquote="" lspace="" macros="" mathbackground="" mathcolor="" mathsize="" mathvariant="" maxsize="" maxwidth="" minlabelspacing="" minsize="" mode="" movablelimits="" mslinethickness="" notation="" numalign="" open="" other="" overflow="" position="" rightoverhang="" rowalign="" rowlines="" rowspacing="" rowspan="" rquote="" rspace="" scriptlevel="" scriptminsize="" scriptsizemultiplier="" selection="" separator="" separators="" shift="" side="" stackalign="" stretchy="" style="" subscriptshift="" superscriptshift="" symmetric="" valign="" width="" xref="">{1,1}</m:math>
</i>
Source
<xsd:element name="i" type="xrefFaces"/>
Element u
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Diagram
Diagram 4_3_6.tmp#b 4_3_6.tmp#i 4_3_6.tmp#u 4_3_6.tmp#ovl 4_3_6.tmp#sup 4_3_6.tmp#sub 4_3_6.tmp#scp 4_3_6.tmp#tt 4_3_6.tmp#font MathML.tmp#math 4_3_6.tmp#face_markup 4_3_6.tmp#xrefFaces
Type xrefFaces
Properties
content: complex
mixed: true
Used by
Element Group face_markup
Model b | i | u | ovl | sup | sub | scp | tt | font | m:math
Children b, font, i, m:math, ovl, scp, sub, sup, tt, u
Instance
<u>
  <b>{1,1}</b>
  <i>{1,1}</i>
  <u>{1,1}</u>
  <ovl>{1,1}</ovl>
  <sup>{1,1}</sup>
  <sub>{1,1}</sub>
  <scp>{1,1}</scp>
  <tt>{1,1}</tt>
  <font>{1,1}</font>
  <m:math accent="" accentunder="" align="" alignmentscope="" altimg="" altimg-height="" altimg-valign="" altimg-width="" alttext="" bevelled="" cdgroup="" charalign="" charspacing="" class="" close="" columnalign="" columnlines="" columnspacing="" columnspan="" columnwidth="" crossout="" decimalpoint="" denomalign="" depth="" dir="" display="" displaystyle="" edge="" equalcolumns="" equalrows="" fence="" form="" frame="" framespacing="" groupalign="" height="" href="" id="" indentalign="" indentalignfirst="" indentalignlast="" indentshift="" indentshiftfirst="" indentshiftlast="" indenttarget="" infixlinebreakstyle="" largeop="" leftoverhang="" length="" linebreak="" linebreakmultchar="" linebreakstyle="" lineleading="" linethickness="" location="" longdivstyle="" lquote="" lspace="" macros="" mathbackground="" mathcolor="" mathsize="" mathvariant="" maxsize="" maxwidth="" minlabelspacing="" minsize="" mode="" movablelimits="" mslinethickness="" notation="" numalign="" open="" other="" overflow="" position="" rightoverhang="" rowalign="" rowlines="" rowspacing="" rowspan="" rquote="" rspace="" scriptlevel="" scriptminsize="" scriptsizemultiplier="" selection="" separator="" separators="" shift="" side="" stackalign="" stretchy="" style="" subscriptshift="" superscriptshift="" symmetric="" valign="" width="" xref="">{1,1}</m:math>
</u>
Source
<xsd:element name="u" type="xrefFaces"/>
Element ovl
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Diagram
Diagram 4_3_6.tmp#b 4_3_6.tmp#i 4_3_6.tmp#u 4_3_6.tmp#ovl 4_3_6.tmp#sup 4_3_6.tmp#sub 4_3_6.tmp#scp 4_3_6.tmp#tt 4_3_6.tmp#font MathML.tmp#math 4_3_6.tmp#face_markup 4_3_6.tmp#xrefFaces
Type xrefFaces
Properties
content: complex
mixed: true
Used by
Element Group face_markup
Model b | i | u | ovl | sup | sub | scp | tt | font | m:math
Children b, font, i, m:math, ovl, scp, sub, sup, tt, u
Instance
<ovl>
  <b>{1,1}</b>
  <i>{1,1}</i>
  <u>{1,1}</u>
  <ovl>{1,1}</ovl>
  <sup>{1,1}</sup>
  <sub>{1,1}</sub>
  <scp>{1,1}</scp>
  <tt>{1,1}</tt>
  <font>{1,1}</font>
  <m:math accent="" accentunder="" align="" alignmentscope="" altimg="" altimg-height="" altimg-valign="" altimg-width="" alttext="" bevelled="" cdgroup="" charalign="" charspacing="" class="" close="" columnalign="" columnlines="" columnspacing="" columnspan="" columnwidth="" crossout="" decimalpoint="" denomalign="" depth="" dir="" display="" displaystyle="" edge="" equalcolumns="" equalrows="" fence="" form="" frame="" framespacing="" groupalign="" height="" href="" id="" indentalign="" indentalignfirst="" indentalignlast="" indentshift="" indentshiftfirst="" indentshiftlast="" indenttarget="" infixlinebreakstyle="" largeop="" leftoverhang="" length="" linebreak="" linebreakmultchar="" linebreakstyle="" lineleading="" linethickness="" location="" longdivstyle="" lquote="" lspace="" macros="" mathbackground="" mathcolor="" mathsize="" mathvariant="" maxsize="" maxwidth="" minlabelspacing="" minsize="" mode="" movablelimits="" mslinethickness="" notation="" numalign="" open="" other="" overflow="" position="" rightoverhang="" rowalign="" rowlines="" rowspacing="" rowspan="" rquote="" rspace="" scriptlevel="" scriptminsize="" scriptsizemultiplier="" selection="" separator="" separators="" shift="" side="" stackalign="" stretchy="" style="" subscriptshift="" superscriptshift="" symmetric="" valign="" width="" xref="">{1,1}</m:math>
</ovl>
Source
<xsd:element name="ovl" type="xrefFaces"/>
Element sup
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Diagram
Diagram 4_3_6.tmp#b 4_3_6.tmp#i 4_3_6.tmp#u 4_3_6.tmp#ovl 4_3_6.tmp#sup 4_3_6.tmp#sub 4_3_6.tmp#scp 4_3_6.tmp#tt 4_3_6.tmp#font MathML.tmp#math 4_3_6.tmp#face_markup 4_3_6.tmp#xrefFaces
Type xrefFaces
Properties
content: complex
mixed: true
Used by
Element Group face_markup
Model b | i | u | ovl | sup | sub | scp | tt | font | m:math
Children b, font, i, m:math, ovl, scp, sub, sup, tt, u
Instance
<sup>
  <b>{1,1}</b>
  <i>{1,1}</i>
  <u>{1,1}</u>
  <ovl>{1,1}</ovl>
  <sup>{1,1}</sup>
  <sub>{1,1}</sub>
  <scp>{1,1}</scp>
  <tt>{1,1}</tt>
  <font>{1,1}</font>
  <m:math accent="" accentunder="" align="" alignmentscope="" altimg="" altimg-height="" altimg-valign="" altimg-width="" alttext="" bevelled="" cdgroup="" charalign="" charspacing="" class="" close="" columnalign="" columnlines="" columnspacing="" columnspan="" columnwidth="" crossout="" decimalpoint="" denomalign="" depth="" dir="" display="" displaystyle="" edge="" equalcolumns="" equalrows="" fence="" form="" frame="" framespacing="" groupalign="" height="" href="" id="" indentalign="" indentalignfirst="" indentalignlast="" indentshift="" indentshiftfirst="" indentshiftlast="" indenttarget="" infixlinebreakstyle="" largeop="" leftoverhang="" length="" linebreak="" linebreakmultchar="" linebreakstyle="" lineleading="" linethickness="" location="" longdivstyle="" lquote="" lspace="" macros="" mathbackground="" mathcolor="" mathsize="" mathvariant="" maxsize="" maxwidth="" minlabelspacing="" minsize="" mode="" movablelimits="" mslinethickness="" notation="" numalign="" open="" other="" overflow="" position="" rightoverhang="" rowalign="" rowlines="" rowspacing="" rowspan="" rquote="" rspace="" scriptlevel="" scriptminsize="" scriptsizemultiplier="" selection="" separator="" separators="" shift="" side="" stackalign="" stretchy="" style="" subscriptshift="" superscriptshift="" symmetric="" valign="" width="" xref="">{1,1}</m:math>
</sup>
Source
<xsd:element name="sup" type="xrefFaces"/>
Element sub
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Diagram
Diagram 4_3_6.tmp#b 4_3_6.tmp#i 4_3_6.tmp#u 4_3_6.tmp#ovl 4_3_6.tmp#sup 4_3_6.tmp#sub 4_3_6.tmp#scp 4_3_6.tmp#tt 4_3_6.tmp#font MathML.tmp#math 4_3_6.tmp#face_markup 4_3_6.tmp#xrefFaces
Type xrefFaces
Properties
content: complex
mixed: true
Used by
Element Group face_markup
Model b | i | u | ovl | sup | sub | scp | tt | font | m:math
Children b, font, i, m:math, ovl, scp, sub, sup, tt, u
Instance
<sub>
  <b>{1,1}</b>
  <i>{1,1}</i>
  <u>{1,1}</u>
  <ovl>{1,1}</ovl>
  <sup>{1,1}</sup>
  <sub>{1,1}</sub>
  <scp>{1,1}</scp>
  <tt>{1,1}</tt>
  <font>{1,1}</font>
  <m:math accent="" accentunder="" align="" alignmentscope="" altimg="" altimg-height="" altimg-valign="" altimg-width="" alttext="" bevelled="" cdgroup="" charalign="" charspacing="" class="" close="" columnalign="" columnlines="" columnspacing="" columnspan="" columnwidth="" crossout="" decimalpoint="" denomalign="" depth="" dir="" display="" displaystyle="" edge="" equalcolumns="" equalrows="" fence="" form="" frame="" framespacing="" groupalign="" height="" href="" id="" indentalign="" indentalignfirst="" indentalignlast="" indentshift="" indentshiftfirst="" indentshiftlast="" indenttarget="" infixlinebreakstyle="" largeop="" leftoverhang="" length="" linebreak="" linebreakmultchar="" linebreakstyle="" lineleading="" linethickness="" location="" longdivstyle="" lquote="" lspace="" macros="" mathbackground="" mathcolor="" mathsize="" mathvariant="" maxsize="" maxwidth="" minlabelspacing="" minsize="" mode="" movablelimits="" mslinethickness="" notation="" numalign="" open="" other="" overflow="" position="" rightoverhang="" rowalign="" rowlines="" rowspacing="" rowspan="" rquote="" rspace="" scriptlevel="" scriptminsize="" scriptsizemultiplier="" selection="" separator="" separators="" shift="" side="" stackalign="" stretchy="" style="" subscriptshift="" superscriptshift="" symmetric="" valign="" width="" xref="">{1,1}</m:math>
</sub>
Source
<xsd:element name="sub" type="xrefFaces"/>
Element scp
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Diagram
Diagram 4_3_6.tmp#b 4_3_6.tmp#i 4_3_6.tmp#u 4_3_6.tmp#ovl 4_3_6.tmp#sup 4_3_6.tmp#sub 4_3_6.tmp#scp 4_3_6.tmp#tt 4_3_6.tmp#font MathML.tmp#math 4_3_6.tmp#face_markup 4_3_6.tmp#xrefFaces
Type xrefFaces
Properties
content: complex
mixed: true
Used by
Element Group face_markup
Model b | i | u | ovl | sup | sub | scp | tt | font | m:math
Children b, font, i, m:math, ovl, scp, sub, sup, tt, u
Instance
<scp>
  <b>{1,1}</b>
  <i>{1,1}</i>
  <u>{1,1}</u>
  <ovl>{1,1}</ovl>
  <sup>{1,1}</sup>
  <sub>{1,1}</sub>
  <scp>{1,1}</scp>
  <tt>{1,1}</tt>
  <font>{1,1}</font>
  <m:math accent="" accentunder="" align="" alignmentscope="" altimg="" altimg-height="" altimg-valign="" altimg-width="" alttext="" bevelled="" cdgroup="" charalign="" charspacing="" class="" close="" columnalign="" columnlines="" columnspacing="" columnspan="" columnwidth="" crossout="" decimalpoint="" denomalign="" depth="" dir="" display="" displaystyle="" edge="" equalcolumns="" equalrows="" fence="" form="" frame="" framespacing="" groupalign="" height="" href="" id="" indentalign="" indentalignfirst="" indentalignlast="" indentshift="" indentshiftfirst="" indentshiftlast="" indenttarget="" infixlinebreakstyle="" largeop="" leftoverhang="" length="" linebreak="" linebreakmultchar="" linebreakstyle="" lineleading="" linethickness="" location="" longdivstyle="" lquote="" lspace="" macros="" mathbackground="" mathcolor="" mathsize="" mathvariant="" maxsize="" maxwidth="" minlabelspacing="" minsize="" mode="" movablelimits="" mslinethickness="" notation="" numalign="" open="" other="" overflow="" position="" rightoverhang="" rowalign="" rowlines="" rowspacing="" rowspan="" rquote="" rspace="" scriptlevel="" scriptminsize="" scriptsizemultiplier="" selection="" separator="" separators="" shift="" side="" stackalign="" stretchy="" style="" subscriptshift="" superscriptshift="" symmetric="" valign="" width="" xref="">{1,1}</m:math>
</scp>
Source
<xsd:element name="scp" type="xrefFaces"/>
Element tt
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Diagram
Diagram 4_3_6.tmp#b 4_3_6.tmp#i 4_3_6.tmp#u 4_3_6.tmp#ovl 4_3_6.tmp#sup 4_3_6.tmp#sub 4_3_6.tmp#scp 4_3_6.tmp#tt 4_3_6.tmp#font MathML.tmp#math 4_3_6.tmp#face_markup 4_3_6.tmp#xrefFaces
Type xrefFaces
Properties
content: complex
mixed: true
Used by
Element Group face_markup
Model b | i | u | ovl | sup | sub | scp | tt | font | m:math
Children b, font, i, m:math, ovl, scp, sub, sup, tt, u
Instance
<tt>
  <b>{1,1}</b>
  <i>{1,1}</i>
  <u>{1,1}</u>
  <ovl>{1,1}</ovl>
  <sup>{1,1}</sup>
  <sub>{1,1}</sub>
  <scp>{1,1}</scp>
  <tt>{1,1}</tt>
  <font>{1,1}</font>
  <m:math accent="" accentunder="" align="" alignmentscope="" altimg="" altimg-height="" altimg-valign="" altimg-width="" alttext="" bevelled="" cdgroup="" charalign="" charspacing="" class="" close="" columnalign="" columnlines="" columnspacing="" columnspan="" columnwidth="" crossout="" decimalpoint="" denomalign="" depth="" dir="" display="" displaystyle="" edge="" equalcolumns="" equalrows="" fence="" form="" frame="" framespacing="" groupalign="" height="" href="" id="" indentalign="" indentalignfirst="" indentalignlast="" indentshift="" indentshiftfirst="" indentshiftlast="" indenttarget="" infixlinebreakstyle="" largeop="" leftoverhang="" length="" linebreak="" linebreakmultchar="" linebreakstyle="" lineleading="" linethickness="" location="" longdivstyle="" lquote="" lspace="" macros="" mathbackground="" mathcolor="" mathsize="" mathvariant="" maxsize="" maxwidth="" minlabelspacing="" minsize="" mode="" movablelimits="" mslinethickness="" notation="" numalign="" open="" other="" overflow="" position="" rightoverhang="" rowalign="" rowlines="" rowspacing="" rowspan="" rquote="" rspace="" scriptlevel="" scriptminsize="" scriptsizemultiplier="" selection="" separator="" separators="" shift="" side="" stackalign="" stretchy="" style="" subscriptshift="" superscriptshift="" symmetric="" valign="" width="" xref="">{1,1}</m:math>
</tt>
Source
<xsd:element name="tt" type="xrefFaces"/>
Element font
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Diagram
Diagram 4_3_6.tmp#b 4_3_6.tmp#i 4_3_6.tmp#u 4_3_6.tmp#ovl 4_3_6.tmp#sup 4_3_6.tmp#sub 4_3_6.tmp#scp 4_3_6.tmp#tt 4_3_6.tmp#font MathML.tmp#math 4_3_6.tmp#face_markup 4_3_6.tmp#xrefFaces
Type xrefFaces
Properties
content: complex
mixed: true
Used by
Element Group face_markup
Model b | i | u | ovl | sup | sub | scp | tt | font | m:math
Children b, font, i, m:math, ovl, scp, sub, sup, tt, u
Instance
<font>
  <b>{1,1}</b>
  <i>{1,1}</i>
  <u>{1,1}</u>
  <ovl>{1,1}</ovl>
  <sup>{1,1}</sup>
  <sub>{1,1}</sub>
  <scp>{1,1}</scp>
  <tt>{1,1}</tt>
  <font>{1,1}</font>
  <m:math accent="" accentunder="" align="" alignmentscope="" altimg="" altimg-height="" altimg-valign="" altimg-width="" alttext="" bevelled="" cdgroup="" charalign="" charspacing="" class="" close="" columnalign="" columnlines="" columnspacing="" columnspan="" columnwidth="" crossout="" decimalpoint="" denomalign="" depth="" dir="" display="" displaystyle="" edge="" equalcolumns="" equalrows="" fence="" form="" frame="" framespacing="" groupalign="" height="" href="" id="" indentalign="" indentalignfirst="" indentalignlast="" indentshift="" indentshiftfirst="" indentshiftlast="" indenttarget="" infixlinebreakstyle="" largeop="" leftoverhang="" length="" linebreak="" linebreakmultchar="" linebreakstyle="" lineleading="" linethickness="" location="" longdivstyle="" lquote="" lspace="" macros="" mathbackground="" mathcolor="" mathsize="" mathvariant="" maxsize="" maxwidth="" minlabelspacing="" minsize="" mode="" movablelimits="" mslinethickness="" notation="" numalign="" open="" other="" overflow="" position="" rightoverhang="" rowalign="" rowlines="" rowspacing="" rowspan="" rquote="" rspace="" scriptlevel="" scriptminsize="" scriptsizemultiplier="" selection="" separator="" separators="" shift="" side="" stackalign="" stretchy="" style="" subscriptshift="" superscriptshift="" symmetric="" valign="" width="" xref="">{1,1}</m:math>
</font>
Source
<xsd:element name="font" type="xrefFaces"/>
Element doi_resources
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Diagram
Diagram 4_3_6.tmp#doi 4_3_6.tmp#collection
Properties
content: complex
Used by
Element body
Model doi , collection
Children collection, doi
Instance
<doi_resources>
  <doi>{1,1}</doi>
  <collection multi-resolution="" property="">{1,1}</collection>
</doi_resources>
Source
<xsd:element name="doi_resources">
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element ref="doi"/>
      <xsd:element ref="collection"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
Element collection
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Annotations
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 (this
option is not currently active, contact support@crossref.org for more info)
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 The multi-resolution attribute may be used to lock or unlock
DOIs for multiple resolution.
Diagram
Diagram NO_NAMESPACE.tmp#collection_property NO_NAMESPACE.tmp#collection_multi-resolution 4_3_6.tmp#item
Properties
content: complex
Used by
Model item*
Children item
Instance
<collection multi-resolution="" property="">
  <item country="" crawler="" label="">{0,unbounded}</item>
</collection>
Attributes
QName Type Fixed Default Use Annotation
multi-resolution restriction of xsd:NMTOKEN optional
property restriction of xsd:NMTOKEN required
Source
<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 (this option is not currently active, contact support@crossref.org for more info) 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 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: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>
Element item
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Annotations
A container used to associate a collection, doi, or resource (URI)
with zero or more property elements. item is currently used for supplying as-crawled
URLs (http://help.crossref.org/#as-crawled-urls)
Diagram
Diagram NO_NAMESPACE.tmp#item_crawler NO_NAMESPACE.tmp#item_label NO_NAMESPACE.tmp#item_country 4_3_6.tmp#doi 4_3_6.tmp#resource
Properties
content: complex
Used by
Element collection
Model (doi | resource)
Children doi, resource
Instance
<item country="" crawler="" label="">
  <doi>{1,1}</doi>
  <resource content_version="" mime_type="">{1,1}</resource>
</item>
Attributes
QName Type Fixed Default Use Annotation
country restriction of xsd:NMTOKEN optional
crawler restriction of xsd:NMTOKEN optional
label restriction of xsd:string optional
Source
<xsd:element name="item">
  <xsd:annotation>
    <xsd:documentation>A container used to associate a collection, doi, or resource (URI) with zero or more property elements. item is currently used for supplying as-crawled URLs (http://help.crossref.org/#as-crawled-urls)</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:choice minOccurs="0">
        <xsd:element ref="doi"/>
        <xsd:element ref="resource"/>
      </xsd:choice>
    </xsd:sequence>
    <xsd:attribute name="crawler" use="optional">
      <xsd:simpleType>
        <xsd:restriction base="xsd:NMTOKEN">
          <xsd:enumeration value="altavista"/>
          <xsd:enumeration value="google"/>
          <xsd:enumeration value="msn"/>
          <xsd:enumeration value="scirus"/>
          <xsd:enumeration value="yahoo"/>
          <xsd:enumeration value="iParadigms"/>
        </xsd:restriction>
      </xsd:simpleType>
    </xsd:attribute>
    <xsd:attribute name="label" use="optional">
      <xsd:simpleType>
        <xsd:restriction base="xsd:string">
          <xsd:maxLength value="128"/>
          <xsd:minLength value="3"/>
        </xsd:restriction>
      </xsd:simpleType>
    </xsd:attribute>
    <xsd:attribute name="country" use="optional">
      <xsd:simpleType>
        <xsd:restriction base="xsd:NMTOKEN">
          <xsd:enumeration value="AX"/>
          <xsd:enumeration value="AF"/>
          <xsd:enumeration value="AL"/>
          <xsd:enumeration value="DZ"/>
          <xsd:enumeration value="AS"/>
          <xsd:enumeration value="AD"/>
          <xsd:enumeration value="AO"/>
          <xsd:enumeration value="AI"/>
          <xsd:enumeration value="AQ"/>
          <xsd:enumeration value="AG"/>
          <xsd:enumeration value="AR"/>
          <xsd:enumeration value="AM"/>
          <xsd:enumeration value="AW"/>
          <xsd:enumeration value="AU"/>
          <xsd:enumeration value="AT"/>
          <xsd:enumeration value="AZ"/>
          <xsd:enumeration value="BS"/>
          <xsd:enumeration value="BH"/>
          <xsd:enumeration value="BD"/>
          <xsd:enumeration value="BB"/>
          <xsd:enumeration value="BY"/>
          <xsd:enumeration value="BE"/>
          <xsd:enumeration value="BZ"/>
          <xsd:enumeration value="BJ"/>
          <xsd:enumeration value="BM"/>
          <xsd:enumeration value="BT"/>
          <xsd:enumeration value="BO"/>
          <xsd:enumeration value="BA"/>
          <xsd:enumeration value="BW"/>
          <xsd:enumeration value="BV"/>
          <xsd:enumeration value="BR"/>
          <xsd:enumeration value="IO"/>
          <xsd:enumeration value="BN"/>
          <xsd:enumeration value="BG"/>
          <xsd:enumeration value="BF"/>
          <xsd:enumeration value="BI"/>
          <xsd:enumeration value="KH"/>
          <xsd:enumeration value="CM"/>
          <xsd:enumeration value="CA"/>
          <xsd:enumeration value="CV"/>
          <xsd:enumeration value="KY"/>
          <xsd:enumeration value="CF"/>
          <xsd:enumeration value="TD"/>
          <xsd:enumeration value="CL"/>
          <xsd:enumeration value="CN"/>
          <xsd:enumeration value="CX"/>
          <xsd:enumeration value="CC"/>
          <xsd:enumeration value="CO"/>
          <xsd:enumeration value="KM"/>
          <xsd:enumeration value="CD"/>
          <xsd:enumeration value="CG"/>
          <xsd:enumeration value="CK"/>
          <xsd:enumeration value="CR"/>
          <xsd:enumeration value="CI"/>
          <xsd:enumeration value="HR"/>
          <xsd:enumeration value="CU"/>
          <xsd:enumeration value="CY"/>
          <xsd:enumeration value="CZ"/>
          <xsd:enumeration value="DK"/>
          <xsd:enumeration value="DJ"/>
          <xsd:enumeration value="DM"/>
          <xsd:enumeration value="DO"/>
          <xsd:enumeration value="EC"/>
          <xsd:enumeration value="EG"/>
          <xsd:enumeration value="SV"/>
          <xsd:enumeration value="GQ"/>
          <xsd:enumeration value="ER"/>
          <xsd:enumeration value="EE"/>
          <xsd:enumeration value="ET"/>
          <xsd:enumeration value="FK"/>
          <xsd:enumeration value="FO"/>
          <xsd:enumeration value="FJ"/>
          <xsd:enumeration value="FI"/>
          <xsd:enumeration value="FR"/>
          <xsd:enumeration value="GF"/>
          <xsd:enumeration value="PF"/>
          <xsd:enumeration value="TF"/>
          <xsd:enumeration value="GA"/>
          <xsd:enumeration value="GM"/>
          <xsd:enumeration value="GE"/>
          <xsd:enumeration value="DE"/>
          <xsd:enumeration value="GH"/>
          <xsd:enumeration value="GI"/>
          <xsd:enumeration value="GR"/>
          <xsd:enumeration value="GL"/>
          <xsd:enumeration value="GD"/>
          <xsd:enumeration value="GP"/>
          <xsd:enumeration value="GU"/>
          <xsd:enumeration value="GT"/>
          <xsd:enumeration value="GN"/>
          <xsd:enumeration value="GW"/>
          <xsd:enumeration value="GY"/>
          <xsd:enumeration value="HT"/>
          <xsd:enumeration value="HM"/>
          <xsd:enumeration value="HN"/>
          <xsd:enumeration value="HK"/>
          <xsd:enumeration value="HU"/>
          <xsd:enumeration value="IS"/>
          <xsd:enumeration value="IN"/>
          <xsd:enumeration value="ID"/>
          <xsd:enumeration value="IR"/>
          <xsd:enumeration value="IQ"/>
          <xsd:enumeration value="IE"/>
          <xsd:enumeration value="IL"/>
          <xsd:enumeration value="IT"/>
          <xsd:enumeration value="JM"/>
          <xsd:enumeration value="JP"/>
          <xsd:enumeration value="JO"/>
          <xsd:enumeration value="KZ"/>
          <xsd:enumeration value="KE"/>
          <xsd:enumeration value="KI"/>
          <xsd:enumeration value="KP"/>
          <xsd:enumeration value="KR"/>
          <xsd:enumeration value="KW"/>
          <xsd:enumeration value="KG"/>
          <xsd:enumeration value="LA"/>
          <xsd:enumeration value="LV"/>
          <xsd:enumeration value="LB"/>
          <xsd:enumeration value="LS"/>
          <xsd:enumeration value="LR"/>
          <xsd:enumeration value="LY"/>
          <xsd:enumeration value="LI"/>
          <xsd:enumeration value="LT"/>
          <xsd:enumeration value="LU"/>
          <xsd:enumeration value="MO"/>
          <xsd:enumeration value="MK"/>
          <xsd:enumeration value="MG"/>
          <xsd:enumeration value="MW"/>
          <xsd:enumeration value="MY"/>
          <xsd:enumeration value="MV"/>
          <xsd:enumeration value="ML"/>
          <xsd:enumeration value="MT"/>
          <xsd:enumeration value="MH"/>
          <xsd:enumeration value="MQ"/>
          <xsd:enumeration value="MR"/>
          <xsd:enumeration value="MU"/>
          <xsd:enumeration value="YT"/>
          <xsd:enumeration value="MX"/>
          <xsd:enumeration value="FM"/>
          <xsd:enumeration value="MD"/>
          <xsd:enumeration value="MC"/>
          <xsd:enumeration value="MN"/>
          <xsd:enumeration value="MS"/>
          <xsd:enumeration value="MA"/>
          <xsd:enumeration value="MZ"/>
          <xsd:enumeration value="MM"/>
          <xsd:enumeration value="NA"/>
          <xsd:enumeration value="NR"/>
          <xsd:enumeration value="NP"/>
          <xsd:enumeration value="NL"/>
          <xsd:enumeration value="AN"/>
          <xsd:enumeration value="NC"/>
          <xsd:enumeration value="NZ"/>
          <xsd:enumeration value="NI"/>
          <xsd:enumeration value="NE"/>
          <xsd:enumeration value="NG"/>
          <xsd:enumeration value="NU"/>
          <xsd:enumeration value="NF"/>
          <xsd:enumeration value="MP"/>
          <xsd:enumeration value="NO"/>
          <xsd:enumeration value="OM"/>
          <xsd:enumeration value="PK"/>
          <xsd:enumeration value="PW"/>
          <xsd:enumeration value="PS"/>
          <xsd:enumeration value="PA"/>
          <xsd:enumeration value="PG"/>
          <xsd:enumeration value="PY"/>
          <xsd:enumeration value="PE"/>
          <xsd:enumeration value="PH"/>
          <xsd:enumeration value="PN"/>
          <xsd:enumeration value="PL"/>
          <xsd:enumeration value="PT"/>
          <xsd:enumeration value="PR"/>
          <xsd:enumeration value="QA"/>
          <xsd:enumeration value="RE"/>
          <xsd:enumeration value="RO"/>
          <xsd:enumeration value="RU"/>
          <xsd:enumeration value="RW"/>
          <xsd:enumeration value="SH"/>
          <xsd:enumeration value="KN"/>
          <xsd:enumeration value="LC"/>
          <xsd:enumeration value="PM"/>
          <xsd:enumeration value="VC"/>
          <xsd:enumeration value="WS"/>
          <xsd:enumeration value="SM"/>
          <xsd:enumeration value="ST"/>
          <xsd:enumeration value="SA"/>
          <xsd:enumeration value="SN"/>
          <xsd:enumeration value="CS"/>
          <xsd:enumeration value="SC"/>
          <xsd:enumeration value="SL"/>
          <xsd:enumeration value="SG"/>
          <xsd:enumeration value="SK"/>
          <xsd:enumeration value="SI"/>
          <xsd:enumeration value="SB"/>
          <xsd:enumeration value="SO"/>
          <xsd:enumeration value="ZA"/>
          <xsd:enumeration value="GS"/>
          <xsd:enumeration value="ES"/>
          <xsd:enumeration value="LK"/>
          <xsd:enumeration value="SD"/>
          <xsd:enumeration value="SR"/>
          <xsd:enumeration value="SJ"/>
          <xsd:enumeration value="SZ"/>
          <xsd:enumeration value="SE"/>
          <xsd:enumeration value="CH"/>
          <xsd:enumeration value="SY"/>
          <xsd:enumeration value="TW"/>
          <xsd:enumeration value="TJ"/>
          <xsd:enumeration value="TZ"/>
          <xsd:enumeration value="TH"/>
          <xsd:enumeration value="TL"/>
          <xsd:enumeration value="TG"/>
          <xsd:enumeration value="TK"/>
          <xsd:enumeration value="TO"/>
          <xsd:enumeration value="TT"/>
          <xsd:enumeration value="TN"/>
          <xsd:enumeration value="TR"/>
          <xsd:enumeration value="TM"/>
          <xsd:enumeration value="TC"/>
          <xsd:enumeration value="TV"/>
          <xsd:enumeration value="UG"/>
          <xsd:enumeration value="UA"/>
          <xsd:enumeration value="AE"/>
          <xsd:enumeration value="GB"/>
          <xsd:enumeration value="US"/>
          <xsd:enumeration value="UM"/>
          <xsd:enumeration value="UY"/>
          <xsd:enumeration value="UZ"/>
          <xsd:enumeration value="VU"/>
          <xsd:enumeration value="VA"/>
          <xsd:enumeration value="VE"/>
          <xsd:enumeration value="VN"/>
          <xsd:enumeration value="VG"/>
          <xsd:enumeration value="VI"/>
          <xsd:enumeration value="WF"/>
          <xsd:enumeration value="EH"/>
          <xsd:enumeration value="YE"/>
          <xsd:enumeration value="ZM"/>
          <xsd:enumeration value="ZW"/>
        </xsd:restriction>
      </xsd:simpleType>
    </xsd:attribute>
  </xsd:complexType>
</xsd:element>
Element resource
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Annotations
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).
Diagram
Diagram 4_3_6.tmp#resource_t 4_3_6.tmp#mime_type.atts NO_NAMESPACE.tmp#resource_content_version
Type extension of resource_t
Type hierarchy
Properties
content: complex
Used by
Elements doi_data, item
Attributes
QName Type Fixed Default Use Annotation
content_version restriction of xsd:string optional
mime_type restriction of xsd:string optional
Source
<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>
Element crossmark_data
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Diagram
Diagram 4_3_6.tmp#doi 4_3_6.tmp#crossmark
Properties
content: complex
Used by
Element body
Model doi , crossmark
Children crossmark, doi
Instance
<crossmark_data>
  <doi>{1,1}</doi>
  <crossmark>{1,1}</crossmark>
</crossmark_data>
Source
<xsd:element name="crossmark_data">
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element ref="doi"/>
      <xsd:element ref="crossmark"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
Element crossmark
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Annotations
Container element for CrossMark data.
Diagram
Diagram 4_3_6.tmp#crossmark_version 4_3_6.tmp#crossmark_policy 4_3_6.tmp#crossmark_domains 4_3_6.tmp#crossmark_domain_exclusive 4_3_6.tmp#updates 4_3_6.tmp#custom_metadata
Properties
content: complex
Used by
Element crossmark_data
Model crossmark_version{0,1} , crossmark_policy , crossmark_domains , crossmark_domain_exclusive{0,1} , updates{0,1} , custom_metadata{0,1}
Children crossmark_domain_exclusive, crossmark_domains, crossmark_policy, crossmark_version, custom_metadata, updates
Instance
<crossmark>
  <crossmark_version>{0,1}</crossmark_version>
  <crossmark_policy>{1,1}</crossmark_policy>
  <crossmark_domains>{1,1}</crossmark_domains>
  <crossmark_domain_exclusive>{0,1}</crossmark_domain_exclusive>
  <updates>{0,1}</updates>
  <custom_metadata>{0,1}</custom_metadata>
</crossmark>
Source
<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"/>
      <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>
Element crossmark_version
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Diagram
Diagram
Type xsd:string
Properties
content: simple
Used by
Element crossmark
Source
<xsd:element name="crossmark_version" type="xsd:string"/>
Element crossmark_policy
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Annotations
A DOI which points to a publisher's CrossMark policy document.
Publishers might have different policies for different
publications.
Diagram
Diagram 4_3_6.tmp#doi_t
Type doi_t
Properties
content: simple
Facets
minLength 6
maxLength 2048
Used by
Element crossmark
Source
<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>
Element crossmark_domains
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Annotations
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
Diagram
Diagram 4_3_6.tmp#crossmark_domain
Properties
content: complex
Used by
Element crossmark
Model crossmark_domain+
Children crossmark_domain
Instance
<crossmark_domains>
  <crossmark_domain>{1,unbounded}</crossmark_domain>
</crossmark_domains>
Source
<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>
Element crossmark_domain
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Annotations
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.
Diagram
Diagram 4_3_6.tmp#http___www.crossref.org_doi_resources_schema_4.3.6_domain 4_3_6.tmp#filter
Properties
content: complex
Used by
Model domain , filter{0,1}
Children domain, filter
Instance
<crossmark_domain>
  <domain>{1,1}</domain>
  <filter>{0,1}</filter>
</crossmark_domain>
Source
<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>
Element domain
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Annotations
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.
Diagram
Diagram 4_3_6.tmp#cm_domain
Type cm_domain
Properties
content: simple
Facets
minLength 4
maxLength 1024
pattern [A-Za-z0-9_]+([-.][A-Za-z0-9_]+)*\.[A-Za-z0-9_]+([-.][A-Za-z0-9_]+)*
Used by
Source
<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>
Element filter
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Annotations
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.
Diagram
Diagram
Type xsd:string
Properties
content: simple
Used by
Source
<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>
Element crossmark_domain_exclusive
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Diagram
Diagram
Type xsd:boolean
Properties
content: simple
Used by
Element crossmark
Source
<xsd:element name="crossmark_domain_exclusive" type="xsd:boolean"/>
Element updates
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Annotations
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.
Diagram
Diagram 4_3_6.tmp#update
Properties
content: complex
Used by
Element crossmark
Model update+
Children update
Instance
<updates>
  <update date="" type="">{1,unbounded}</update>
</updates>
Source
<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>
Element update
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Annotations
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.
Diagram
Diagram 4_3_6.tmp#doi_t NO_NAMESPACE.tmp#update_type NO_NAMESPACE.tmp#update_date
Type extension of doi_t
Type hierarchy
Properties
content: complex
mixed: true
Used by
Element updates
Attributes
QName Type Fixed Default Use Annotation
date xsd:date required
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.
type cm_update_type required
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>
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>
Element custom_metadata
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Annotations
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.
Diagram
Diagram 4_3_6.tmp#assertion fundref_xsd.tmp#program AccessIndicators_xsd.tmp#http___www.crossref.org_AccessIndicators.xsd_program clinicaltrials_xsd.tmp#http___www.crossref.org_clinicaltrials.xsd_program fundref_xsd.tmp#program AccessIndicators_xsd.tmp#http___www.crossref.org_AccessIndicators.xsd_program clinicaltrials_xsd.tmp#http___www.crossref.org_clinicaltrials.xsd_program AccessIndicators_xsd.tmp#http___www.crossref.org_AccessIndicators.xsd_program clinicaltrials_xsd.tmp#http___www.crossref.org_clinicaltrials.xsd_program clinicaltrials_xsd.tmp#http___www.crossref.org_clinicaltrials.xsd_program
Properties
content: complex
Used by
Element crossmark
Model (assertion+ , program{0,1} , program{0,1} , program{0,1}) | (program , program{0,1} , program{0,1}) | (program , program{0,1}) | program
Children assertion, program
Instance
<custom_metadata>
  <assertion explanation="" group_label="" group_name="" href="" label="" name="" order="">{1,unbounded}</assertion>
  <program name="fundref">{0,1}</program>
  <program name="AccessIndicators">{0,1}</program>
  <program>{0,1}</program>
  <program name="fundref">{1,1}</program>
  <program name="AccessIndicators">{0,1}</program>
  <program>{0,1}</program>
  <program name="AccessIndicators">{1,1}</program>
  <program>{0,1}</program>
  <program>{1,1}</program>
</custom_metadata>
Source
<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>
Element assertion
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Annotations
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.
Diagram
Diagram NO_NAMESPACE.tmp#assertion_explanation NO_NAMESPACE.tmp#assertion_group_label NO_NAMESPACE.tmp#assertion_group_name NO_NAMESPACE.tmp#assertion_label NO_NAMESPACE.tmp#assertion_name NO_NAMESPACE.tmp#assertion_order NO_NAMESPACE.tmp#assertion_href 4_3_6.tmp#b 4_3_6.tmp#i 4_3_6.tmp#u 4_3_6.tmp#ovl 4_3_6.tmp#sup 4_3_6.tmp#sub 4_3_6.tmp#scp 4_3_6.tmp#tt 4_3_6.tmp#font MathML.tmp#math 4_3_6.tmp#face_markup
Properties
content: complex
mixed: true
Used by
Element custom_metadata
Model b | i | u | ovl | sup | sub | scp | tt | font | m:math
Children b, font, i, m:math, ovl, scp, sub, sup, tt, u
Instance
<assertion explanation="" group_label="" group_name="" href="" label="" name="" order="">
  <b>{1,1}</b>
  <i>{1,1}</i>
  <u>{1,1}</u>
  <ovl>{1,1}</ovl>
  <sup>{1,1}</sup>
  <sub>{1,1}</sub>
  <scp>{1,1}</scp>
  <tt>{1,1}</tt>
  <font>{1,1}</font>
  <m:math accent="" accentunder="" align="" alignmentscope="" altimg="" altimg-height="" altimg-valign="" altimg-width="" alttext="" bevelled="" cdgroup="" charalign="" charspacing="" class="" close="" columnalign="" columnlines="" columnspacing="" columnspan="" columnwidth="" crossout="" decimalpoint="" denomalign="" depth="" dir="" display="" displaystyle="" edge="" equalcolumns="" equalrows="" fence="" form="" frame="" framespacing="" groupalign="" height="" href="" id="" indentalign="" indentalignfirst="" indentalignlast="" indentshift="" indentshiftfirst="" indentshiftlast="" indenttarget="" infixlinebreakstyle="" largeop="" leftoverhang="" length="" linebreak="" linebreakmultchar="" linebreakstyle="" lineleading="" linethickness="" location="" longdivstyle="" lquote="" lspace="" macros="" mathbackground="" mathcolor="" mathsize="" mathvariant="" maxsize="" maxwidth="" minlabelspacing="" minsize="" mode="" movablelimits="" mslinethickness="" notation="" numalign="" open="" other="" overflow="" position="" rightoverhang="" rowalign="" rowlines="" rowspacing="" rowspan="" rquote="" rspace="" scriptlevel="" scriptminsize="" scriptsizemultiplier="" selection="" separator="" separators="" shift="" side="" stackalign="" stretchy="" style="" subscriptshift="" superscriptshift="" symmetric="" valign="" width="" xref="">{1,1}</m:math>
</assertion>
Attributes
QName Type Fixed Default Use Annotation
explanation xsd:anyURI optional
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.
group_label cm_assertion_group_label optional
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.
group_name cm_assertion_group_name optional
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.
href xsd:anyURI optional
Optional attribute
label cm_assertion_label optional
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)
name cm_assertion_name required
Required attribute. This is the machine-readable name of the
assertion. Use the "label" attribute to provide a human-readable version of
the name.
order xsd:integer optional
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.
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>
Element fundref_data
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Diagram
Diagram 4_3_6.tmp#doi fundref_xsd.tmp#program
Properties
content: complex
Used by
Element body
Model doi , program
Children doi, program
Instance
<fundref_data>
  <doi>{1,1}</doi>
  <program name="fundref">{1,1}</program>
</fundref_data>
Source
<xsd:element name="fundref_data">
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element ref="doi"/>
      <xsd:element ref="fr:program"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
Element lic_ref_data
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Diagram
Diagram 4_3_6.tmp#doi AccessIndicators_xsd.tmp#http___www.crossref.org_AccessIndicators.xsd_program
Properties
content: complex
Used by
Element body
Model doi , program
Children doi, program
Instance
<lic_ref_data>
  <doi>{1,1}</doi>
  <program name="AccessIndicators">{1,1}</program>
</lic_ref_data>
Source
<xsd:element name="lic_ref_data">
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element ref="doi"/>
      <xsd:element ref="ai:program"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
Element doi_relations
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Diagram
Diagram 4_3_6.tmp#doi relations_xsd.tmp#http___www.crossref.org_relations.xsd_program
Properties
content: complex
Used by
Element body
Model doi , program
Children doi, program
Instance
<doi_relations>
  <doi>{1,1}</doi>
  <program name="relations">{1,1}</program>
</doi_relations>
Source
<xsd:element name="doi_relations">
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element ref="doi"/>
      <!-- the enitity making the claim that a relationship exists -->
      <xsd:element ref="rel:program"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
Element clinicaltrial_data
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Diagram
Diagram 4_3_6.tmp#doi clinicaltrials_xsd.tmp#http___www.crossref.org_clinicaltrials.xsd_program
Properties
content: complex
Used by
Element body
Model doi , program
Children doi, program
Instance
<clinicaltrial_data>
  <doi>{1,1}</doi>
  <program>{1,1}</program>
</clinicaltrial_data>
Source
<xsd:element name="clinicaltrial_data">
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element ref="doi"/>
      <!-- the enitity making the claim that a relationship exists -->
      <xsd:element ref="ct:program"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
Element timestamp
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Annotations
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.
Diagram
Diagram
Type xsd:double
Properties
content: simple
Used by
Element doi_data
Source
<xsd:element name="timestamp" type="xsd:double">
  <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>
Element registrant
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Annotations
The organization that owns the information being registered.
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
minLength 1
maxLength 255
Source
<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>
Element doi_data
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Annotations
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.
Diagram
Diagram 4_3_6.tmp#doi 4_3_6.tmp#timestamp 4_3_6.tmp#resource 4_3_6.tmp#collection
Properties
content: complex
Used by
Element component
Model doi , timestamp{0,1} , resource , collection*
Children collection, doi, resource, timestamp
Instance
<doi_data>
  <doi>{1,1}</doi>
  <timestamp>{0,1}</timestamp>
  <resource content_version="" mime_type="">{1,1}</resource>
  <collection multi-resolution="" property="">{0,unbounded}</collection>
</doi_data>
Source
<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>
Element property
Namespace http://www.crossref.org/doi_resources_schema/4.3.6
Annotations
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.
Diagram
Diagram 4_3_6.tmp#property_t NO_NAMESPACE.tmp#property_type
Type extension of property_t
Type hierarchy
Properties
content: complex
Attributes
QName Type Fixed Default Use Annotation
type xsd:string required
Source
<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>