Version: beta 0.3 This schema provides for creating relationships between items represented by crossref DOIs and other items that may be defined by a DOI (crossref or other RA) or by some other identifier. New relation types will be added as they're needed. Please contact support@crossref.org to request additions or changes. Certain relationship types are covered elsewhere in the main deposit schema due primarily to specific processing or the need to logically group those relations alongside other relevant metadata. For example cited-by relations are created by the deposit of a citation_list. Crossmark->Updates addresses relationships between DOIs where a primary item is updated, revised, hasErratum, withdrawn ... etc. When constructing relations please be sure to use the the most appropriate metadata structure. Relationships between DOIs in crossref are established bidirectionally between those DOIs making it unnecessary to deposit relationship metadata for both DOIs. Example: DOI A metadata contains 'hasTranslation' with a target of DOI B will automatically make this claim visible in metadata for B. Seen from the perspective of B: A claims it hasTranslation of which B is the target of the claim. Change history: 10/3/14 CSK removed reg-agency attribute. This is not necessary, can be derived from the DOI 10/3/14 CSK split into inter and intra relation elements 10/3/14 CSK pulled in common crossref schema for description element and language attributes 12/21/16 CSK added comments to each relation type indicating the appropriate inverse relation type 3/6/17 PDF added accession as identifier-type ====== C O N V E N T I O N ============================================================================================== Relationships between two objects have an implicit directionality that in natural language terms dictate which object is the actor and which is acted-upon. This directionality is semantically based on the relationship name. Crossref's model makes no attempt to automatically 'understand' this semantic. The identifier parent to the PROGRAM element is considered the claimant of the relationship (e.g. the entity that establishes the relationship). yes: 10.1234/abcd references 10.5678/efgh => 10.1234/abcd claims that it references 10.5678/efgh yes: 10.1234/abcd referencedBy 10.5678/efgh => 10.1234/abcd claims that it is referenced by 10.5678/efgh ==========================================================================================================================
<xsd:element name="related_item"><xsd:complexType><xsd:sequence><xsd:annotation><xsd:documentation>Description of the relationship to the target item or of the target item itself</xsd:documentation></xsd:annotation><xsd:element ref="description" minOccurs="0" maxOccurs="1"/><xsd:choice><xsd:element ref="inter_work_relation" minOccurs="1" maxOccurs="1"/><xsd:element ref="intra_work_relation" minOccurs="1" maxOccurs="1"/></xsd:choice></xsd:sequence></xsd:complexType></xsd:element>
A narrative description of a file (e.g. a figure caption orvideo description) which may be independent of the host document context. Thedescription element may be present more than once to provide alternative languagevalues.
<xsd:element name="description"><xsd:annotation><xsd:documentation>A narrative description of a file (e.g. a figure caption or video description) which may be independent of the host document context. The description element may be present more than once to provide alternative language values.</xsd:documentation></xsd:annotation><xsd:complexType mixed="true"><xsd:choice minOccurs="0" maxOccurs="unbounded"><xsd:group ref="face_markup"/></xsd:choice><xsd:attributeGroup ref="language.atts"/></xsd:complexType></xsd:element>
Used to define relations between items that are essentially the same work but may differ in format, language, revision ... etc. Assigning different identifers to exactly the same itemavailable in one place or as copies in multiple places can be problematic and should be avoided.
Source
<xsd:element name="intra_work_relation"><xsd:complexType mixed="true"><xsd:attribute name="relationship-type" use="required"><xsd:annotation><xsd:documentation>Used to define relations between items that are essentially the same work but may differ in format, language, revision ... etc. Assigning different identifers to exactly the same item available in one place or as copies in multiple places can be problematic and should be avoided.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><!-- Crossref --><xsd:enumeration value="isTranslationOf"/><!-- hasTranslation --><xsd:enumeration value="hasTranslation"/><!-- isTranslationOf --><xsd:enumeration value="isPreprintOf"/><!-- hasPreprint --><xsd:enumeration value="hasPreprint"/><!-- isPreprintOf --><xsd:enumeration value="isManuscriptOf"/><!-- hasManuscript --><xsd:enumeration value="hasManuscript"/><!-- isManuscriptOf --><xsd:enumeration value="isExpressionOf"/><!-- hasExpression --><xsd:enumeration value="hasExpression"/><!-- isExpressionOf --><xsd:enumeration value="isManifestationOf"/><!-- hasManifestation --><xsd:enumeration value="hasManifestation"/><!-- isManifestationOf --><xsd:enumeration value="isReplacedBy"/><!-- replaces --><xsd:enumeration value="replaces"/><!-- isReplacedBy --><xsd:enumeration value="isSameAs"/><!-- isSameAs --><!-- Common with DataCite --><xsd:enumeration value="isIdenticalTo"/><!-- isIdenticalTo --><xsd:enumeration value="isVariantFormOf"/><!-- isOriginalFormOf --><xsd:enumeration value="isOriginalFormOf"/><!-- isVariantFormOf --><!-- From Dublin core --><xsd:enumeration value="isVersionOf"/><!-- hasVersion --><xsd:enumeration value="hasVersion"/><!-- isVersionOf --><xsd:enumeration value="isFormatOf"/><!-- hasFormat --><xsd:enumeration value="hasFormat"/><!-- isFormatOf --></xsd:restriction></xsd:simpleType></xsd:attribute><xsd:attributeGroup ref="relations_type.atts"/></xsd:complexType></xsd:element>
Publisher generated ID that uniquely identifies the DOI submissionbatch. It will be used as a reference in error messages sent by the MDDB, and can beused for submission tracking. The publisher must insure that this number is uniquefor every submission to CrossRef.
Diagram
Type
restriction of xsd:string
Properties
content
simple
Facets
minLength
4
maxLength
100
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>
Indicates version of a batch file instance or DOI. timestamp is usedto uniquely identify batch files and DOI values when a DOI has been updated one ormore times. timestamp is an integer representation of date and time that serves as aversion number for the record that is being deposited. Because CrossRef uses it as aversion number, the format need not follow any public standard and therefore thepublisher can determine the internal format. The schema format is a double of atleast 64 bits, insuring that a fully qualified date/time stamp of 19 digits can besubmitted. When depositing data, CrossRef will check to see if a DOI has alreadybeen deposited for the specific doi value. If the newer data carries a time stampvalue that is equal to or greater than the old data based on a strict numericcomparison, the new data will replace the old data. If the new data value is lessthan the old data value, the new data will not replace the old data. timestamp isoptional in doi_data and required in head. The value from the head instancetimestamp will be used for all instances of doi_data that do not include a timestampelement.
<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>
<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>
Name of the organization registering the DOIs. The name placed inthis element should match the name under which a depositing organization hasregistered with CrossRef.
<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>
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 organizationsubmitting data (e.g. "doi@...") rather than unique to a person. In this way, thealias for delivery of this mail can be changed as responsibility for submission ofDOI data within the organization changes from one person to another.
<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>
The organization that owns the information being registered.
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>
The chapter, section, part, etc. number for a content item in a book.Unlike volume and edition_number, component_number should include any additionaltext 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 alsoacceptable, however the former treatment is preferred. The type of the component isgiven the component_type attribute of content_item.
<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>
The edition number of a book. edition_number should include only anumber and not additional text such as "edition". For example, you should submit"3", not "third edition" or "3rd edition". Roman numerals are acceptable. Publisherswill update a print edition with a new edition number when more than ten percent ofthe content has changed. However, publishers expect to continuously update onlineeditions 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: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>
The issue number in which an article is published. Only one issuename should be used for the issue. The issue number takes precedence over any othername. For example, if an issue has only a seasonal name, then the season should belisted in issue. However, if an issue has a number and a season, then only thenumber should be listed in issue, and the season should be placed in month (see thetable in month, below, for proper encoding of the season) if the specific month ofpublication is not known. Do not include the words "issue", "No" or "number" in thiselement. When submitting DOIs for journal articles published online ahead of print,you should submit the issue number, when known, even if the pagination informationfor 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: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>
The container for elements related directly to a DOI. doi_datacontains the doi, timestamp (version) and corresponding resource (URI) data for thedoi. 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 areto be proved the <collection> element may also be used. The single URLprovided in the <resource> is mandatory and serves as the single resolutiontarget for the DOI. Note: A timestamp value placed inside doi_data will override anytimestamp value placed in the <head> element.
<xsd:element name="doi_data"><xsd:annotation><xsd:documentation>The container for elements related directly to a DOI. doi_data contains the doi, timestamp (version) and corresponding resource (URI) data for the doi. Cases of single-resolution (i.e. one DOI with a single corresponding URI) should be tagged with a doi/resource pair in doi_data. If additional resources are to be proved the <collection> element may also be used. The single URL provided in the <resource> is mandatory and serves as the single resolution target for the DOI. Note: A timestamp value placed inside doi_data will override any timestamp value placed in the <head> element.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="doi"/><xsd:element ref="timestamp" minOccurs="0"/><xsd:element ref="resource"/><xsd:element ref="collection" minOccurs="0" maxOccurs="unbounded"/></xsd:sequence></xsd:complexType></xsd:element>
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 additionalinformation on DOI syntax, see http://0-help.crossref.org.brum.beds.ac.uk/#ID5755
<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://0-help.crossref.org.brum.beds.ac.uk/#ID5755</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="doi_t"/></xsd:simpleType></xsd:element>
The element that contains a URI associated with a DOI. URLs arereferred to as resources in the 2.0 CrossRef schema because they can be any validURI. 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 allowedper 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: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>
A collection is a container for one or more items each holding a doior 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 themulti-resolution attribute. property attributes: list-based: uses an interim pageand 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 (thisoption 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 beused for syndication The multi-resolution attribute may be used to lock or unlockDOIs for multiple resolution.
<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>
A container used to associate a collection, doi, or resource (URI)with zero or more property elements. item is currently used for supplying as-crawledURLs (http://0-help.crossref.org.brum.beds.ac.uk/#as-crawled-urls)
property elements qualify the semantic meaning of a item orcollection. property elements consist of a type/value pair where the property typeis found in the type attribute and the value is found in the element content. Theproperty element is not currently in use.
<xsd:element name="property"><xsd:annotation><xsd:documentation>property elements qualify the semantic meaning of a item or collection. property elements consist of a type/value pair where the property type is found in the type attribute and the value is found in the element content. The property element is not currently in use.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:simpleContent><xsd:extension base="property_t"><xsd:attribute name="type" type="xsd:string" use="required"/></xsd:extension></xsd:simpleContent></xsd:complexType></xsd:element>
<xsd:element name="contributors"><xsd:annotation><xsd:documentation>The container for all who contributed to authoring or editing an entity.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:choice maxOccurs="unbounded"><xsd:element ref="organization"/><xsd:element ref="person_name"/></xsd:choice></xsd:sequence></xsd:complexType></xsd:element>
The name of an organization (as opposed to a person) that contributedto authoring an entity. If multiple organizations authored an entity, each oneshould be captured in a unique organization element. If an entity was authored byindividuals in addition to one or more organizations, person_name and organizationmay be freely intermixed within contributors. contributor_role should be set, asappropriate, to author or editor. When a contributor translated a work, setcontributor_role to "translator". "chair" should only be used for conferenceproceedings to indicate a conference chair.
<xsd:element name="organization"><xsd:annotation><xsd:documentation>The name of an organization (as opposed to a person) that contributed to authoring an entity. If multiple organizations authored an entity, each one should be captured in a unique organization element. If an entity was authored by individuals in addition to one or more organizations, person_name and organization may be freely intermixed within contributors. contributor_role should be set, as appropriate, to author or editor. When a contributor translated a work, set contributor_role to "translator". "chair" should only be used for conference proceedings to indicate a conference chair.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:simpleContent><xsd:extension base="organization_t"><xsd:attributeGroup ref="contributor.atts"/></xsd:extension></xsd:simpleContent></xsd:complexType></xsd:element>
The name of a person (as opposed to an organization) that contributedto authoring an entity. Authors with name suffixes should have the suffix capturedin suffix, not in surname. Author prefixes such as "Dr.", "Prof.", or "President"should not be included in person_name or any other element. Author degrees (e.g.M.D., Ph.D.) also should not be included in CrossRef submissions. contributor_roleshould be set, as appropriate, to author or editor. When a contributor translated awork, set contributor_role to "translator". "chair" should only be used forconference proceedings to indicate a conference chair.
<xsd:element name="person_name"><xsd:annotation><xsd:documentation>The name of a person (as opposed to an organization) that contributed to authoring an entity. Authors with name suffixes should have the suffix captured in suffix, not in surname. Author prefixes such as "Dr.", "Prof.", or "President" should not be included in person_name or any other element. Author degrees (e.g. M.D., Ph.D.) also should not be included in CrossRef submissions. contributor_role should be set, as appropriate, to author or editor. When a contributor translated a work, set contributor_role to "translator". "chair" should only be used for conference proceedings to indicate a conference chair.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="given_name" minOccurs="0"/><xsd:element ref="surname"/><xsd:element ref="suffix" minOccurs="0"/><xsd:element ref="affiliation" minOccurs="0" maxOccurs="5"/><xsd:element ref="ORCID" minOccurs="0" maxOccurs="1"/><xsd:element ref="alt-name" minOccurs="0"/></xsd:sequence><xsd:attributeGroup ref="contributor.atts"/></xsd:complexType></xsd:element>
A contributor's given name. The given_name, combined with surname,forms the name of an author or editor. given_name may be submitted as eitherinitials or a full name. Do not place given_name within the surname unless it isunclear how to distinguish the given name from the surname, as may be the case innon-Western names. Do not include titles such as "Dr.", "Prof.", or "President" ingiven_name. These titles should not be submitted to CrossRef.
<xsd:element name="given_name"><xsd:annotation><xsd:documentation>A contributor's given name. The given_name, combined with surname, forms the name of an author or editor. given_name may be submitted as either initials or a full name. Do not place given_name within the surname unless it is unclear how to distinguish the given name from the surname, as may be the case in non-Western names. Do not include titles such as "Dr.", "Prof.", or "President" in given_name. These titles should not be submitted to CrossRef.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="35"/><xsd:minLength value="1"/><xsd:pattern value="[^\d\?]*"/><xsd:whiteSpace value="collapse"/></xsd:restriction></xsd:simpleType></xsd:element>
The surname of an author or editor. The surname, combined withgiven_name, forms the name of an author or editor. Whenever possible, the given nameshould not be included in the surname element. In cases where the given name is notclear, as may happen with non-Western names or some societies in which surnames arenot distinguished, you may place the entire name in surname, e.g.:<surname>Leonardo da Vinci</surname>If an author is an organization, you should use organization,not surname. Suffixes should be tagged with suffix. Author degrees (e.g. M.D.,Ph.D.) should not be included in CrossRef submissions.
<xsd:element name="surname"><xsd:annotation><xsd:documentation>The surname of an author or editor. The surname, combined with given_name, forms the name of an author or editor. Whenever possible, the given name should not be included in the surname element. In cases where the given name is not clear, as may happen with non-Western names or some societies in which surnames are not distinguished, you may place the entire name in surname, e.g.:<surname>Leonardo da Vinci</surname>If an author is an organization, you should use organization, not surname. Suffixes should be tagged with suffix. Author degrees (e.g. M.D., Ph.D.) should not be included in CrossRef submissions.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="45"/><xsd:minLength value="1"/><xsd:pattern value="[^\d\?]*[^\d\?\s]+[^\d\?]*"/><xsd:whiteSpace value="collapse"/></xsd:restriction></xsd:simpleType></xsd:element>
The suffix of an author name, e.g. junior or senior. A name suffix,that typically denotes a generation distinction, is tagged with suffix. Authordegrees (e.g. M.D., Ph.D.) should not be included in CrossRefsubmissions.
<xsd:element name="suffix"><xsd:annotation><xsd:documentation>The suffix of an author name, e.g. junior or senior. A name suffix, that typically denotes a generation distinction, is tagged with suffix. Author degrees (e.g. M.D., Ph.D.) should not be included in CrossRef submissions.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="10"/><xsd:minLength value="1"/></xsd:restriction></xsd:simpleType></xsd:element>
The institution(s) with which a contributor is affiliated. Thiselement may hold the name and location of an affiliation with which a contributor isaffiliated. Please note the following points when using this element: 1. Acontributor may have up to five affiliations. Each affiliation should be in a unique<affiliation> element. The following is correct: <affiliation>Universityof New Mexico</affiliation> <affiliation>Sandia NationalLaboratories</affiliation> The following is NOT correct<affiliation>University of New Mexico; Sandia NationalLaboratories</affiliation> 2. The name of the institution is required in thiselement. The location is optional. Both of the following are correct:<affiliation>Harvard University</affiliation> <affiliation>HarvardUniversity, Cambridge, MA</affiliation> 3. Additional address information suchas a URL or email address should NOT be deposited in this element 4. Visual linkingindicators used in publication to connect authors with their affiliations such asfootnote symbols or initials should NOT be included in the <affiliation>element 5. If you have only a single string that has the affiliation for multiplecontributors to a work and that string is not broken out into the individualaffliations for each author, please do NOT deposit the affilation information. Thiselement is to be used only for affiliation information that is directly connected tothe author with whom this information is included within the person_name element.
<xsd:element name="affiliation"><xsd:annotation><xsd:documentation>The institution(s) with which a contributor is affiliated. This element may hold the name and location of an affiliation with which a contributor is affiliated. Please note the following points when using this element: 1. A contributor may have up to five affiliations. Each affiliation should be in a unique <affiliation> element. The following is correct: <affiliation>University of New Mexico</affiliation> <affiliation>Sandia National Laboratories</affiliation> The following is NOT correct <affiliation>University of New Mexico; Sandia National Laboratories</affiliation> 2. The name of the institution is required in this element. The location is optional. Both of the following are correct: <affiliation>Harvard University</affiliation> <affiliation>Harvard University, Cambridge, MA</affiliation> 3. Additional address information such as a URL or email address should NOT be deposited in this element 4. Visual linking indicators used in publication to connect authors with their affiliations such as footnote symbols or initials should NOT be included in the <affiliation> element 5. If you have only a single string that has the affiliation for multiple contributors to a work and that string is not broken out into the individual affliations for each author, please do NOT deposit the affilation information. This element is to be used only for affiliation information that is directly connected to the author with whom this information is included within the person_name element.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="512"/><xsd:minLength value="1"/></xsd:restriction></xsd:simpleType></xsd:element>
<xsd:element name="ORCID"><xsd:annotation><xsd:documentation>The ORCID for an author. The schema performs basic pattern validation, checksum validation is performed upon deposit via a system check.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:simpleContent><xsd:extension base="orcid_t"><xsd:attribute default="false" name="authenticated" type="xsd:boolean"/></xsd:extension></xsd:simpleContent></xsd:complexType></xsd:element>
<xsd:element name="titles"><xsd:annotation><xsd:documentation>A container for the title and original language title elements.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:sequence><xsd:element ref="title"/><xsd:element ref="subtitle" minOccurs="0"/></xsd:sequence><xsd:sequence minOccurs="0"><xsd:element ref="original_language_title"/><xsd:element ref="subtitle" minOccurs="0"/></xsd:sequence></xsd:sequence></xsd:complexType></xsd:element>
The title of the entity being registered. When a title contains asubtitle, it is preferable to capture the subtitle portion in the subtitle element.Only minimal face markup is supported, see See http://0-help.crossref.org.brum.beds.ac.uk/#face_markup
<xsd:element name="title"><xsd:annotation><xsd:documentation>The title of the entity being registered. When a title contains a subtitle, it is preferable to capture the subtitle portion in the subtitle element. Only minimal face markup is supported, see See http://0-help.crossref.org.brum.beds.ac.uk/#face_markup</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>
The sub-title portion of an entity title. When possible, it is betterto tag a title and subtitle with separate elements. If this information is notavailable, it is acceptable to submit the title and subtitle all within the titleelement with punctuation (preferably a colon) used to separate the subtitle from thetitle. When a subtitle is tagged, the space and punctuation between the title andsubtitle text should not be included. The following examples illustrate correct andincorrect tagging practices: Correct and optimal tagging:<title>The Human Brain</title><subtitle>A Handbook</subtitle>Correct but not optimal tagging:<title>The Human Brain: A Handbook</title>Incorrect:<title>The Human Brain:</title><subtitle>A Handbook</subtitle><title>The Human Brain</title><subtitle>: A Handbook</subtitle>
<xsd:element name="subtitle"><xsd:annotation><xsd:documentation>The sub-title portion of an entity title. When possible, it is better to tag a title and subtitle with separate elements. If this information is not available, it is acceptable to submit the title and subtitle all within the title element with punctuation (preferably a colon) used to separate the subtitle from the title. When a subtitle is tagged, the space and punctuation between the title and subtitle text should not be included. The following examples illustrate correct and incorrect tagging practices: Correct and optimal tagging:<title>The Human Brain</title><subtitle>A Handbook</subtitle>Correct but not optimal tagging:<title>The Human Brain: A Handbook</title>Incorrect:<title>The Human Brain:</title><subtitle>A Handbook</subtitle><title>The Human Brain</title><subtitle>: A Handbook</subtitle></xsd:documentation></xsd:annotation><xsd:complexType mixed="true"><xsd:choice minOccurs="0" maxOccurs="unbounded"><xsd:group ref="face_markup"/></xsd:choice></xsd:complexType></xsd:element>
The title of an entity in its original language if the registrationis for a translation of a work. When providing the original language of a title, youshould set the language attribute.
<xsd:element name="original_language_title"><xsd:annotation><xsd:documentation>The title of an entity in its original language if the registration is for a translation of a work. When providing the original language of a title, you should set the language attribute.</xsd:documentation></xsd:annotation><xsd:complexType mixed="true"><xsd:choice minOccurs="0" maxOccurs="unbounded"><xsd:group ref="face_markup"/></xsd:choice><xsd:attributeGroup ref="language.atts"/></xsd:complexType></xsd:element>
Month of publication. The month must be expressed in numeric formatrather spelling out the name (e.g.. submit "10", not "October"). The month must beexpressed with a leading zero if it is less than 10 (e.g. submit "05", not "5").When a journal issue has both an issue number and a season, the issue number shouldbe placed in issue. If the month of publication is not known, the season should beplaced in month as a two-digit value as follows: Season Value Spring 21 Summer 22Autumn 23 Winter 24 First Quarter 31 Second Quarter 32 Third Quarter 33 FourthQuarter 34 In cases when an issue covers multiple months, e.g. "March-April",include only the digits for the first month of the range.
<xsd:element name="month" type="xrefMonth"><xsd:annotation><xsd:documentation>Month of publication. The month must be expressed in numeric format rather spelling out the name (e.g.. submit "10", not "October"). The month must be expressed with a leading zero if it is less than 10 (e.g. submit "05", not "5"). When a journal issue has both an issue number and a season, the issue number should be placed in issue. If the month of publication is not known, the season should be placed in month as a two-digit value as follows: Season Value Spring 21 Summer 22 Autumn 23 Winter 24 First Quarter 31 Second Quarter 32 Third Quarter 33 Fourth Quarter 34 In cases when an issue covers multiple months, e.g. "March-April", include only the digits for the first month of the range.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="day" type="xrefDay"><xsd:annotation><xsd:documentation>Day of publication. The should must be expressed with a leading zero if it is less than 10 (e.g. submit "05", not "5").</xsd:documentation></xsd:annotation></xsd:element>
The date of publication. In all cases, multiple dates are allowed toallow for different dates of publication for online and print versions. This elementwas previously called date, but was renamed publication_date to distinguish moreclearly from conference_date.
<xsd:element name="publication_date"><xsd:annotation><xsd:documentation>The date of publication. In all cases, multiple dates are allowed to allow for different dates of publication for online and print versions. This element was previously called date, but was renamed publication_date to distinguish more clearly from conference_date.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:complexContent><xsd:extension base="date_t"/></xsd:complexContent></xsd:complexType></xsd:element>
The container for information about page ranges. When an entity hasnon-contiguous page information, you should capture the first page range infirst_page and last_page. Any additional page information should be captured inother_pages. Punctuation is only allowed in other_pages. It should not appear infirst_page and last_page. Page number letter prefixes or suffixes should beincluded. Roman numeral pages are permitted in both upper case and lower case. Datamay be alpha, numeric or a combination.
<xsd:element name="pages"><xsd:annotation><xsd:documentation>The container for information about page ranges. When an entity has non-contiguous page information, you should capture the first page range in first_page and last_page. Any additional page information should be captured in other_pages. Punctuation is only allowed in other_pages. It should not appear in first_page and last_page. Page number letter prefixes or suffixes should be included. Roman numeral pages are permitted in both upper case and lower case. Data may be alpha, numeric or a combination.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element ref="first_page"/><xsd:element ref="last_page" minOccurs="0"/><xsd:element ref="other_pages" minOccurs="0"/></xsd:sequence></xsd:complexType></xsd:element>
<xsd:element name="first_page"><xsd:annotation><xsd:documentation>First page number where an entity is located. Data may be alpha, numeric or a combination.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="32"/><xsd:minLength value="1"/></xsd:restriction></xsd:simpleType></xsd:element>
The last page number of an entity. last_page should not be used whenthe last page number is the same as the first page number (i.e. when the entireentity fits on one page). Do not include punctuation for a page range in last_page.If the entity has non-contiguous paging, use last_page for the last page of thefirst range and place all other page information into other_pages. Data may bealpha, numeric or a combination.
<xsd:element name="last_page"><xsd:annotation><xsd:documentation>The last page number of an entity. last_page should not be used when the last page number is the same as the first page number (i.e. when the entire entity fits on one page). Do not include punctuation for a page range in last_page. If the entity has non-contiguous paging, use last_page for the last page of the first range and place all other page information into other_pages. Data may be alpha, numeric or a combination.</xsd:documentation></xsd:annotation><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="32"/><xsd:minLength value="1"/></xsd:restriction></xsd:simpleType></xsd:element>
Used to capture additional page information when items do notencompass contiguous page ranges. When an entity has non-contiguous pageinformation, you should capture the first page range in first_page and last_page.Any additional page information should be captured in other_pages. You shouldinclude commas or hyphens to express discrete pages or page ranges. endash entitiesshould be converted to ASCII hyphens. Spaces should not be included. Note thatpunctuation should never appear in first_page and last_page. Data may be alpha,numeric or a combination.