diff --git a/articlemeta/export_crossref.py b/articlemeta/export_crossref.py index 88794ca..c223113 100644 --- a/articlemeta/export_crossref.py +++ b/articlemeta/export_crossref.py @@ -27,9 +27,13 @@ def transform(self, data): } el = ET.Element('doi_batch', nsmap=nsmap) - el.set('version', '4.4.0') - el.set('xmlns', 'http://www.crossref.org/schema/4.4.0') - el.set('{http://www.w3.org/2001/XMLSchema-instance}schemaLocation', 'http://www.crossref.org/schema/4.4.0 http://www.crossref.org/schemas/crossref4.4.0.xsd') + el.set('version', '5.5.0') + el.set('xmlns', 'http://www.crossref.org/schema/5.5.0') + el.set( + '{http://www.w3.org/2001/XMLSchema-instance}schemaLocation', + 'http://www.crossref.org/schema/5.5.0 ' + 'https://data.crossref.org/schemas/crossref5.5.0.xsd' + ) return data, el @@ -340,7 +344,6 @@ def _create_journal_article(language=None): if language: el.set('language', language) el.set('publication_type', 'full_text') - el.set('reference_distribution_opts', 'any') return el def transform(self, data): @@ -449,6 +452,30 @@ def precond(data): if not raw.authors: raise plumber.UnmetPrecondition() + @staticmethod + def _create_institution(affiliation): + institution_name = affiliation.get('institution') + if not institution_name or not institution_name.strip(): + return None + + institution = ET.Element('institution') + + name = ET.Element('institution_name') + name.text = institution_name + institution.append(name) + + place_parts = [ + affiliation.get(field) + for field in ('city', 'state', 'country') + if affiliation.get(field) and affiliation.get(field).strip() + ] + if place_parts: + place = ET.Element('institution_place') + place.text = ', '.join(place_parts) + institution.append(place) + + return institution + @plumber.precondition(precond) def transform(self, data): """ @@ -494,29 +521,20 @@ def transform(self, data): author_index = [i.upper() for i in authors.get('xref', []) or []] if raw.affiliations: - affs_list = [] + affiliations = ET.Element('affiliations') for aff in raw.affiliations: - affiliation = ET.Element('affiliation') - if 'index' not in aff: + affiliation_index = aff.get('index') + if not affiliation_index: + continue + if affiliation_index.upper() not in author_index: continue - if aff['index'].upper() in author_index: - aff_list = [] - if 'institution' in aff: - aff_list.append(aff['institution']) - if 'addr_line' in aff: - aff_list.append(aff['addr_line']) - if 'country' in aff: - aff_list.append(aff['country']) - - aff_info = ', '.join(aff_list) - if len(aff_info.strip()) == 0: - continue - affs_list.append(aff_info) - - affs = '; '.join(affs_list) - if len(affs) > 0: - affiliation.text = affs - author.append(affiliation) + + institution = self._create_institution(aff) + if institution is not None: + affiliations.append(institution) + + if len(affiliations): + author.append(affiliations) if 'orcid' in authors and authors['orcid']: orcid = ET.Element('ORCID') diff --git a/setup.py b/setup.py index 0185dc9..136c5e7 100644 --- a/setup.py +++ b/setup.py @@ -21,7 +21,13 @@ 'crossrefapi>=1.3', ] -test_requires = ['mocker', 'nose>=1.0', 'coverage', 'mongomock'] +test_requires = [ + 'mocker', + 'nose>=1.0', + 'coverage', + 'mongomock', + 'xmlschema', +] setup( name="articlemeta", diff --git a/tests/test_export_crossref.py b/tests/test_export_crossref.py index 361b7d9..be309c2 100644 --- a/tests/test_export_crossref.py +++ b/tests/test_export_crossref.py @@ -2,16 +2,39 @@ import unittest import json import os -import io -from unittest.mock import patch, PropertyMock +from unittest.mock import Mock, patch, PropertyMock from lxml import etree as ET +import xmlschema from articlemeta import export_crossref from articlemeta import export from articlemeta.export import CustomArticle as Article +SCHEMA_DIR = os.path.join( + os.path.dirname(__file__), 'xsd', 'scielo_crossref') +CROSSREF_SCHEMA_PATH = os.path.join(SCHEMA_DIR, 'crossref5.5.0.xsd') +CROSSREF_SCHEMA_LOCATIONS = [ + ( + 'http://www.ncbi.nlm.nih.gov/JATS1', + 'https://data.crossref.org/schemas/' + 'JATS-journalpublishing1-3d2-mathml3.xsd' + ), +] +_CROSSREF_SCHEMA = None + + +def get_crossref_schema(): + global _CROSSREF_SCHEMA + if _CROSSREF_SCHEMA is None: + _CROSSREF_SCHEMA = xmlschema.XMLSchema11( + CROSSREF_SCHEMA_PATH, + locations=CROSSREF_SCHEMA_LOCATIONS, + ) + return _CROSSREF_SCHEMA + + def _get_article(data=None): article_json = { "fulltexts": { @@ -251,6 +274,19 @@ def test_doi_batch_element(self): raw, xml = xmlcrossref.transform(data) self.assertEqual('doi_batch', xml.tag) + self.assertEqual('5.5.0', xml.get('version')) + self.assertEqual( + 'http://www.crossref.org/schema/5.5.0', + xml.get('xmlns') + ) + self.assertEqual( + 'http://www.crossref.org/schema/5.5.0 ' + 'https://data.crossref.org/schemas/crossref5.5.0.xsd', + xml.get( + '{http://www.w3.org/2001/XMLSchema-instance}' + 'schemaLocation' + ) + ) def test_doi_batch_id_element(self): @@ -514,7 +550,7 @@ def test_journal_article_element(self): xmlcrossref = export_crossref.XMLJournalArticlePipe() raw, xml = xmlcrossref.transform(data) - self.assertEqual(b'', ET.tostring(xml)) + self.assertEqual(b'', ET.tostring(xml)) def test_journal_article_element_without_doi_and_lang(self): xmlcrossref = ET.Element('doi_batch') @@ -535,8 +571,6 @@ def test_journal_article_element_without_doi_and_lang(self): self.assertEqual(1, len(journal_articles)) self.assertEqual('pt', journal_articles[0].get('language')) self.assertEqual('full_text', journal_articles[0].get('publication_type')) - self.assertEqual( - 'any', journal_articles[0].get('reference_distribution_opts')) def test_article_titles_element(self): @@ -633,7 +667,89 @@ def test_article_contributors_element(self): xmlcrossref = export_crossref.XMLArticleContributorsPipe() raw, xml = xmlcrossref.transform(data) - self.assertEqual(b'Mariangela LealCherchigliaUniversidade Federal de Minas Gerais, BRAZILElaine LeandroMachadoUniversidade Federal de Minas Gerais, BRAZILDaniele Araújo CampoSzusterUniversidade Federal de Minas Gerais, BRAZILEli Iola GurgelAndradeUniversidade Federal de Minas Gerais, BRAZILFrancisco de AssisAcúrcioUniversidade Federal de Minas Gerais, BRAZILWaleska TeixeiraCaiaffaUniversidade Federal de Minas Gerais, BRAZILRicardoSessoUniversidade Federal de São Paulo, BRAZILAugusto AGuerra JuniorUniversidade Federal de Minas Gerais, BRAZIL; Universidade Federal de São Paulo, BRAZILOdilon Vanni deQueirozUniversidade Federal de Minas Gerais, BRAZILIsabel CristinaGomesUniversidade Federal de Minas Gerais, BRAZIL', ET.tostring(xml)) + persons = xml.findall('.//contributors/person_name') + self.assertEqual(10, len(persons)) + self.assertEqual( + ['editor', 'author', 'translator'] + ['author'] * 7, + [person.get('contributor_role') for person in persons] + ) + self.assertEqual([], xml.findall('.//affiliation')) + + first_institution = persons[0].find( + './affiliations/institution') + self.assertEqual( + 'Universidade Federal de Minas Gerais', + first_institution.findtext('institution_name') + ) + self.assertEqual( + 'Belo Horizonte, MG, BRAZIL', + first_institution.findtext('institution_place') + ) + + multiple_institutions = persons[7].findall( + './affiliations/institution') + self.assertEqual(2, len(multiple_institutions)) + self.assertEqual( + [ + 'Universidade Federal de Minas Gerais', + 'Universidade Federal de São Paulo', + ], + [ + institution.findtext('institution_name') + for institution in multiple_institutions + ] + ) + + def test_article_affiliations_skip_invalid_entries_and_precede_orcid(self): + raw = Mock() + raw.authors = [ + { + 'given_names': 'Jane', + 'surname': 'Doe', + 'xref': ['A1', 'A2', 'A3'], + 'orcid': '0000-0002-1825-0097', + } + ] + raw.affiliations = [ + { + 'index': 'A1', + 'institution': 'Example University', + 'city': 'Example City', + 'state': 'EX', + 'country': 'Example Country', + }, + { + 'index': 'A2', + 'institution': ' ', + 'city': 'Ignored City', + }, + { + 'index': 'A3', + 'institution': 'Name Only Institute', + 'city': ' ', + 'country': '', + }, + ] + + xml = ET.fromstring( + '' + '' + ) + pipe = export_crossref.XMLArticleContributorsPipe() + _, xml = pipe.transform([raw, xml]) + + person = xml.find('.//person_name') + self.assertEqual( + ['given_name', 'surname', 'affiliations', 'ORCID'], + [child.tag for child in person] + ) + institutions = person.findall('./affiliations/institution') + self.assertEqual(2, len(institutions)) + self.assertEqual( + 'Example City, EX, Example Country', + institutions[0].findtext('institution_place') + ) + self.assertIsNone(institutions[1].find('institution_place')) def test_article_publication_date_element(self): @@ -812,17 +928,10 @@ def test_xmlclose_pipe(self): def test_validating_against_schema(self): xml = export.Export(self._raw_json).pipeline_crossref() + schema = get_crossref_schema() - xmlio = ET.parse(io.BytesIO(xml)) - - fp = open(os.path.dirname(__file__)+'/xsd/scielo_crossref/crossref4.4.0.xsd') - schema_root = ET.parse(fp) - schema = ET.XMLSchema(schema_root) - fp.close() - - schema.assertValid(xmlio) - self.assertTrue(schema.validate(xmlio)) - self.assertEqual(None, schema.assertValid(xmlio)) + self.assertTrue(schema.is_valid(xml)) + self.assertEqual(None, schema.validate(xml)) def test_related_articles_validating_against_schema(self): related_documents = [ @@ -844,16 +953,10 @@ def test_related_articles_validating_against_schema(self): return_value=related_documents): xml = export.Export(self._raw_json).pipeline_crossref() - xmlio = ET.parse(io.BytesIO(xml)) - schema_path = ( - os.path.dirname(__file__) + - '/xsd/scielo_crossref/crossref4.4.0.xsd' - ) - with open(schema_path) as fp: - schema = ET.XMLSchema(ET.parse(fp)) - - schema.assertValid(xmlio) - relations = xmlio.findall( + schema = get_crossref_schema() + schema.validate(xml) + xmlroot = ET.fromstring(xml) + relations = xmlroot.findall( './/{http://www.crossref.org/relations.xsd}' 'inter_work_relation' ) @@ -2738,14 +2841,14 @@ def setUp(self): ET.register_namespace('fr', "http://www.crossref.org/fundref.xsd") self.xmlcrossref = ET.Element( - '{http://www.crossref.org/schema/4.4.0}doi_batch', + '{http://www.crossref.org/schema/5.5.0}doi_batch', nsmap=namespace_map, attrib={ '{http://www.w3.org/2001/XMLSchema-instance}schemaLocation': ( - "http://www.crossref.org/schema/4.4.0 " - "http://www.crossref.org/schemas/crossref4.4.0.xsd" + "http://www.crossref.org/schema/5.5.0 " + "https://data.crossref.org/schemas/crossref5.5.0.xsd" ), - 'version': '4.4.0' + 'version': '5.5.0' } ) journal = ET.Element('journal') diff --git a/tests/xsd/scielo_crossref/AccessIndicators.xsd b/tests/xsd/scielo_crossref/AccessIndicators.xsd index 1ae7aa0..431de7d 100644 --- a/tests/xsd/scielo_crossref/AccessIndicators.xsd +++ b/tests/xsd/scielo_crossref/AccessIndicators.xsd @@ -1,27 +1,24 @@ + xmlns="http://www.crossref.org/AccessIndicators.xsd" version="1.2"> - Version: 1.1 This is CrossRef's schema for defining the applicable - licenses for a given item. This schema was available and in use prior to the completion - of the NISO working group Access and License Indicators - (http://www.niso.org/publications/rp/rp-22-2015). That effort produced a schema - (http://www.niso.org/schemas/ali/1.0/ali.xsd) that extended the CrossRef definition but - at the same time omitted necessary CrossRef features. This schema will continue as the - basis for CrossRef metadata deposits, but will incorporate the NISO work where possible. - Change history: 2/23/15 CSK added Niso free_to_read element - 4/21/15 CSK added start and end attributes to the free-to-read element as in the Niso ALI schema - but will make both attributes optional. + + +Version 1.2: updated to include stm-asf value for @applies_to attribute + +Version 1.1 notes: + +This is CrossRef's schema for defining the applicable licenses for a given item. This schema was available and in use prior to the completion of the NISO working group Access and License Indicators (http://www.niso.org/publications/rp/rp-22-2015). That effort produced a schema (http://www.niso.org/schemas/ali/1.0/ali.xsd) that extended the CrossRef definition but at the same time omitted necessary CrossRef features. This schema will continue as the basis for CrossRef metadata deposits, but will incorporate the NISO work where possible. + Change history: 2/23/15 CSK added Niso free_to_read element + 4/21/15 CSK added start and end attributes to the free-to-read element as in the Niso ALI schema but will make both attributes optional. - Accommodates deposit of license metadata. The license_ref value will - be a URL. Values for the "applies_to" attribute are vor (version of record),am - (accepted manuscript), and tdm (text and data mining). + Accommodates deposit of license metadata. The license_ref value will be a URL. Values for the "applies_to" attribute are vor (version of record),am (accepted manuscript), tdm (text and data mining), and stm-asf (STM Article Sharing Framework license). @@ -42,6 +39,7 @@ + diff --git a/tests/xsd/scielo_crossref/common4.3.5.xsd b/tests/xsd/scielo_crossref/common4.3.5.xsd deleted file mode 100644 index 9e07c14..0000000 --- a/tests/xsd/scielo_crossref/common4.3.5.xsd +++ /dev/null @@ -1,2719 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - language attributes are based on iso 639 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Mime types for component format. For mime types refer to - http://www.iana.org/assignments/media-types/ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Use to flag metadata for distribution. "query" is the default and - follows current protocol - bibliographic metadata is distributed to anyone in a - query response, bulk distribution is only allowed per CMS rules. "any" allows bulk - distribution of metadata to anyone using OAI-PMH queries. - - - - - - - - - - - - - Use to flag references for distribution. "none" is the default and - follows current protocol - references are only distributed to everyone if the prefix - level permission is set, otherwise reference distribution is limited to the DOI - owner. Setting the value to "query" releases references to anyone making a query - request (this overrides any established prefix level permission). Value "any" allows - bulk distribution to anyone (using a CrossRef query account) using the OAI-PMH - protocol, and also releases references to anyone making a query - request. - - - - - - - - - - - - - - - - - - - - The following are basic data types for face markup. Face markup that - appears in the title, subtitle, and original_language_title elements should be - retained when depositing metadata. Face markup in other elements (e.g. small caps in - author names) must be dropped. Face markup support includes bold (b), italic (i), - underline (u), over-line (ovl), superscript (sup), subscript (sub), small caps - (scp), and typewriter text (tt). See - http://help.crossref.org/#face_markup - -MathML may also be included using the 'mml' namespace prefix. - - - - - - - - - - - - - - - - - - - - - - - - - - The following are basic data types for date - parts. - - - - - - - - - - - - - - - - - - - - - - - - - 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. - - - - - - - - - - - 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. - - - - - Information about the organization submitting DOI metadata to - CrossRef - - - - - - - - - - - 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. - - - - - - - - - - - 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. - - - - - - - - - - - - - The organization that owns the information being registered. - - - - - - - - - - - - - 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. - - - - - - - - - - - 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. 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. - - - - - - - - - - - - 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 - - 1999 - - - 74 - - 3 - Volume 74, Spring 1999 - - 1999 - - - 74 - - Spring - Volume 74, issue 3 Spring 1999 - - 21 - 1999 - - - 74 - - 3 - - - - - - - - - - - - - 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. - - - - - - - - - - - - - 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). - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 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. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 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) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 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. - - - - - - - - - - - - The container for all who contributed to authoring or editing an - entity. - - - - - - - - - - - - - - - - - - - - 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. - - - - - - - - - - - - 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. - - - - - - - - - - - - - - - - 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. - - - - - - - - - - - - - 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.: Leonardo - da Vinci 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. - - - - - - - - - - - - - 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. - - - - - - - - - - - - - - - - - The ORCID for an author. The schema performs basic pattern validation, checksum validation is performed upon deposit via a system check. - - - - - - - - - - - - - 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. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - A container for the title and original language title - elements. - - - - - - - - - - - - - - - - - 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://help.crossref.org/#face_markup - - - - - - - - - - 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. - - - - - - - - - - - - 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: The Human - Brain - A Handbook Correct but not optimal tagging: The Human - Brain: A Handbook Incorrect: The Human Brain: - A Handbook - The Human Brain - : A Handbook - - - - - - - - - - - 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. - - - - - Day of publication. The should must be expressed with a leading zero - if it is less than 10 (e.g. submit "05", not "5"). - - - - - Year of publication. - - - - - 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. - - - - - - - - - - - - - - - - - - - - - - - - - - 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. - - - - - - - - - - - - First page number where an entity is located. Data may be alpha, - numeric or a combination. - - - - - - - - - - - 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. - - - - - - - - - - - Used to capture additional page information when items do not - encompass contiguous page ranges. When an entity has non-contiguous page - information, you should capture the first page range in first_page and last_page. - Any additional page information should be captured in other_pages. You should - include commas or hyphens to express discrete pages or page ranges. endash entities - should be converted to ASCII hyphens. Spaces should not be included. Note that - punctuation should never appear in first_page and last_page. Data may be alpha, - numeric or a combination. - - - - - - - - - - - - - - - - - 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 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 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. - - - - - - - - - - - - Identifies books or conference proceedings that have no ISBN - assigned. In very limited cases a book may never have an ISBN, this is particularly - true for older texts. Conference proceedings, however, may regularly have a volume - number but no ISBN or volume title. - - - - - - - - - - - - - - - - - - - - - - - - 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. - - - - - - - - - - - - The coden assigned to a journal or conference - proceedings. - - - - - - - - - - - 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. - - - - - - - - - - - - - - Container element for archive. - - - - - - - - - - Used to indicate the designated archiving organization(s) for an - item. Values for the name attribute are CLOCKSS, LOCKSS Portico, KB, DWT (Deep Web - Technologies), Internet Archive,WebCite - - - - - - - - - - - - - - - - - - - - - The date on which a dissertation was accepted by the institution - awarding the degree, a report was approved, or a standard was accepted. - approval_date includes the same elements as publication_date, but it has no - attributes. It is a distinct element from publication_date to reflect that an - important but different semantic meeting from publication_date - - - - - - - - - - - - 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. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 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. - - - - - - - - - - - - - - citation_key allows the publisher to assign a unique ID to each - citation that is deposited. It is recommended that this attribute be given the - reference number if the publication uses reference numbers. For those publications - that use name/date style citations, it is recommended that this attribute be used to - indicate the sequential number of the citation in the reference list. However, some - schema must be utilized as this is a required attribute. The system will use this - key value to track the specific reference query and will return this value along - with the DOI. - - - - - - - - - - - - - - - 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 - - - - - - - - - - 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 - Proc. Natl. Acad. Sci. U.S.A. and - Proceedings of the National Academy of Sciences of the United - States of America are valid journal titles to use in this - element. - - - - - 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. - - - - - 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. - - - - - 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 Doe or - Doe J, 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: World Health Organization - - - - - 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. - - - - - 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. - - - - - - - The element for depositing a stand alone component. The parent DOI - must already exist (created in an earlier deposit or via some other registration - process). - - - - - - - - - - - - - - - - - - The wrapper element for including a group of components under a - journal article, conference proceeding, book chapter, stand alone component, - dissertation, technical report or working paper, standard, or - database. - - - - - - - - - - A container element that allows registration of supplemental - information for a journal article, book chapter, or conference paper such as - figures, tables, videos, or data sets. Currently, the deposit of components - primarily achieves only the first objective as the CrossRef system is not setup yet - to support queries for components. The metadata associated with a component is - intended to enable simple lookup searches of components in the future. When - deposited as part of the metadata for a higher level work the parent DOI is - implicitly known via the XML hierarchy. When deposited separately the DOI of the - higher level work must be provided explicitly (see sa_component) All descriptive - elements are optional allowing for the creation of simple anonymous DOIs. The - 'parent_relation' attribute is mandatory and refers to the DOI described in the - component's direct parent. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Normally book content that is published as a series is required to - have a series title with an ISSN and a book title and/or a book volume number along - with a book ISBN. An exception is when book chapters are published on line first - prior to being assigned to a specific book in which case only the series title (and - ISSN) is known at time of DOI registration. Element unassigned_content is used as a - placeholder to force recognition of this condition and thus prevent accidental - omission of book level title information. When unassigned_content is present the - system will allow omission of the ISBN. If unassigned_content is not present the - system will require an ISBN for the book title. - - - - - - - - - - - - - - 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. - - - - - - - - - - - - - - - - - A narrative description of a component's file format and/or the file - extension (for mime types refer to http://www.iana.org/assignments/media-types/) The - format element may contain only the mime_type attribute, or in addition it may - contain a narrative description of the file format. Be sure to use the narrative - portion to description only the format of the component and not the actual content - of the component (use description to describe the component's - content). - - - - - - - - - - - - - - Container element for CrossMark data. - - - - - - - - - Required element. 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). - - - - - - - - - - - - A DOI which points to a publisher's CrossMark policy document. - Publishers might have different policies for different - publications. - - - - - - 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 - - - - - - - - - - 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. - - - - - - - - - - - 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. - - - - - 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. - - - - - - 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. - - - - - - - - - - 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. - - - - - - - Required attribute. This attribute should be used to - list the update type. Allowed update types are: -
    -
  • addendum
    • -
  • clarification
    • -
  • correction
    • -
  • corrigendum
    • -
  • erratum
    • -
  • expression_of_concern
    • -
  • new_edition
    • -
  • new_version
    • -
  • partial_retraction
    • -
  • removal
    • -
  • retraction
    • -
  • withdrawal
    • -
- - - - - - - 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. - - - - - - - - - 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. - - - - - - - - - - - - - - - - - - - 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. - - - - - - - - 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. - - - - - 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. - - - - - 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. - - - - - 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) - - - - - Required attribute. This is the machine-readable name of the - assertion. Use the "label" attribute to provide a human-readable version of - the name. - - - - - 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. - - - - - Optional attribute - - - - - - - - - A wrapper for designators or other primary identifiers for a - standard. - - - - - - - - - - - - - - Designator or other primary identifier for the standard being - deposited. Required. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Designator for standard replacing the standard being deposited. - - - - - - - - - - - - - - Designator for standard from which the current deposit is adopted. - - - - - - - - - - - - - - Designator for the previous revision of the standard being deposited. - - - - - - - - - - - - - - A wrapper for standards body information. - - - - - - - - - - - Name of the standards organization / publisher. - Required. - - - - - Acronym for standards body. Will be used for query matching - - required. - - - - - - - - - - - - - - - - - - - - - - - diff --git a/tests/xsd/scielo_crossref/common4.4.0.xsd b/tests/xsd/scielo_crossref/common4.4.0.xsd deleted file mode 100644 index 859ac41..0000000 --- a/tests/xsd/scielo_crossref/common4.4.0.xsd +++ /dev/null @@ -1,2846 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - language attributes are based on iso 639 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Mime types for component format. For mime types refer to - http://www.iana.org/assignments/media-types/ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Use to flag metadata for distribution. "query" is the default and - follows current protocol - bibliographic metadata is distributed to anyone in a - query response, bulk distribution is only allowed per CMS rules. "any" allows bulk - distribution of metadata to anyone using OAI-PMH queries. - - - - - - - - - - - - - Use to flag references for distribution. "none" is the default and - follows current protocol - references are only distributed to everyone if the prefix - level permission is set, otherwise reference distribution is limited to the DOI - owner. Setting the value to "query" releases references to anyone making a query - request (this overrides any established prefix level permission). Value "any" allows - bulk distribution to anyone (using a CrossRef query account) using the OAI-PMH - protocol, and also releases references to anyone making a query - request. - - - - - - - - - - - - - - - - - - - - The following are basic data types for face markup. Face markup that - appears in the title, subtitle, and original_language_title elements should be - retained when depositing metadata. Face markup in other elements (e.g. small caps in - author names) must be dropped. Face markup support includes bold (b), italic (i), - underline (u), over-line (ovl), superscript (sup), subscript (sub), small caps - (scp), and typewriter text (tt). See - http://help.crossref.org/#face_markup - -MathML may also be included using the 'mml' namespace prefix. - - - - - - - - - - - - - - - - - - - - - - - - - - The following are basic data types for date - parts. - - - - - - - - - - - - - - - - - - - - - - - - - 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. - - - - - - - - - - - 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. - - - - - Information about the organization submitting DOI metadata to - CrossRef - - - - - - - - - - - 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. - - - - - - - - - - - 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. - - - - - - - - - - - - - The organization that owns the information being registered. - - - - - - - - - - - - - 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. - - - - - - - - - - - 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. 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. - - - - - - - - - - - - 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 - - 1999 - - - 74 - - 3 - Volume 74, Spring 1999 - - 1999 - - - 74 - - Spring - Volume 74, issue 3 Spring 1999 - - 21 - 1999 - - - 74 - - 3 - - - - - - - - - - - - - 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. - - - - - - - - - - - - - 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). - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 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. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 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) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 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. - - - - - - - - - - - - The container for all who contributed to authoring or editing an - entity. - - - - - - - - - - - - - - - - - - - - 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. - - - - - - - - - - - - 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. - - - - - - - - - - - - - - - - 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. - - - - - - - - - - - - - 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.: Leonardo - da Vinci 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. - - - - - - - - - - - - - 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. - - - - - - - - - - - - - - - - - The ORCID for an author. The schema performs basic pattern validation, checksum validation is performed upon deposit via a system check. - - - - - - - - - - - - - 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. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - A container for the title and original language title - elements. - - - - - - - - - - - - - - - - - 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://help.crossref.org/#face_markup - - - - - - - - - - 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. - - - - - - - - - - - - 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: The Human - Brain - A Handbook Correct but not optimal tagging: The Human - Brain: A Handbook Incorrect: The Human Brain: - A Handbook - The Human Brain - : A Handbook - - - - - - - - - - - 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. - - - - - - - - Day of publication. The should must be expressed with a leading zero - if it is less than 10 (e.g. submit "05", not "5"). - - - - - Year of publication. - - - - - database_date records key dates in the life of a database or dataset item. - - Within database_date, creation_date is the date the item was first created, publication_date is the date the item was first published, and update_date is the date the item was last updated. - - - - - - - - - - - - The date a database or dataset item was created. - - - - - - - - - - - The date a content item was created. - - - - - - - - - - - The date a pre-print was posted to a repository. - - - - - - - - - - - The date a manuscript was accepted for publication. - - - - - - - - - - - The date a database or dataset item was updated. - - - - - - - - - - - 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. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 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. - - - - - - - - - - - - First page number where an entity is located. Data may be alpha, - numeric or a combination. - - - - - - - - - - - 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. - - - - - - - - - - - Used to capture additional page information when items do not - encompass contiguous page ranges. When an entity has non-contiguous page - information, you should capture the first page range in first_page and last_page. - Any additional page information should be captured in other_pages. You should - include commas or hyphens to express discrete pages or page ranges. endash entities - should be converted to ASCII hyphens. Spaces should not be included. Note that - punctuation should never appear in first_page and last_page. Data may be alpha, - numeric or a combination. - - - - - - - - - - - - - - - - - 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 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 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. - - - - - - - - - - - - Identifies books or conference proceedings that have no ISBN - assigned. In very limited cases a book may never have an ISBN, this is particularly - true for older texts. Conference proceedings, however, may regularly have a volume - number but no ISBN or volume title. - - - - - - - - - - - - - - - - - - - - - - - - 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. - - - - - - - - - - - - The coden assigned to a journal or conference - proceedings. - - - - - - - - - - - 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. - - - - - - - - - - - - - - Container element for archive. - - - - - - - - - - Used to indicate the designated archiving organization(s) for an - item. Values for the name attribute are CLOCKSS, LOCKSS Portico, KB, DWT (Deep Web - Technologies), Internet Archive - - - - - - - - - - - - - - - - - - - - The date on which a dissertation was accepted by the institution - awarding the degree, a report was approved, or a standard was accepted. - approval_date includes the same elements as publication_date, but it has no - attributes. It is a distinct element from publication_date to reflect that an - important but different semantic meeting from publication_date - - - - - - - - - - - - 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. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 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. - - - - - - - - - - - - - - citation_key allows the publisher to assign a unique ID to each - citation that is deposited. It is recommended that this attribute be given the - reference number if the publication uses reference numbers. For those publications - that use name/date style citations, it is recommended that this attribute be used to - indicate the sequential number of the citation in the reference list. However, some - schema must be utilized as this is a required attribute. The system will use this - key value to track the specific reference query and will return this value along - with the DOI. - - - - - - - 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 - - - - - - - - - - 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 - Proc. Natl. Acad. Sci. U.S.A. and - Proceedings of the National Academy of Sciences of the United - States of America are valid journal titles to use in this - element. - - - - - 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. - - - - - 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. - - - - - 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 Doe or - Doe J, 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: World Health Organization - - - - - 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. - - - - - 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. - - - - - - - The element for depositing a stand alone component. The parent DOI - must already exist (created in an earlier deposit or via some other registration - process). - - - - - - - - - - - - - - - - - - The wrapper element for including a group of components under a - journal article, conference proceeding, book chapter, stand alone component, - dissertation, technical report or working paper, standard, or - database. - - - - - - - - - - A container element that allows registration of supplemental - information for a journal article, book chapter, or conference paper such as - figures, tables, videos, or data sets. Currently, the deposit of components - primarily achieves only the first objective as the CrossRef system is not setup yet - to support queries for components. The metadata associated with a component is - intended to enable simple lookup searches of components in the future. When - deposited as part of the metadata for a higher level work the parent DOI is - implicitly known via the XML hierarchy. When deposited separately the DOI of the - higher level work must be provided explicitly (see sa_component) All descriptive - elements are optional allowing for the creation of simple anonymous DOIs. The - 'parent_relation' attribute is mandatory and refers to the DOI described in the - component's direct parent. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Normally book content that is published as a series is required to - have a series title with an ISSN and a book title and/or a book volume number along - with a book ISBN. An exception is when book chapters are published on line first - prior to being assigned to a specific book in which case only the series title (and - ISSN) is known at time of DOI registration. Element unassigned_content is used as a - placeholder to force recognition of this condition and thus prevent accidental - omission of book level title information. When unassigned_content is present the - system will allow omission of the ISBN. If unassigned_content is not present the - system will require an ISBN for the book title. - - - - - - - - - - - - - - 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. - - - - - - - - - - - - Pubsliher's custom statement for their intent to publish content for which a pre-register DOI has been created - - - - - - - - - - - - - - - - - - A narrative description of a component's file format and/or the file - extension (for mime types refer to http://www.iana.org/assignments/media-types/) The - format element may contain only the mime_type attribute, or in addition it may - contain a narrative description of the file format. Be sure to use the narrative - portion to description only the format of the component and not the actual content - of the component (use description to describe the component's - content). - - - - - - - - - - - - - - Container element for CrossMark data. - - - - - - - - - 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). - - - - - - - - - - - - A DOI which points to a publisher's CrossMark policy document. - Publishers might have different policies for different - publications. - - - - - - 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 - - - - - - - - - - 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. - - - - - - - - - - - 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. - - - - - 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. - - - - - - 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. - - - - - - - - - - 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. - - - - - - - Required attribute. This attribute should be used to - list the update type. Allowed update types are: -
    -
  • addendum
    • -
  • clarification
    • -
  • correction
    • -
  • corrigendum
    • -
  • erratum
    • -
  • expression_of_concern
    • -
  • new_edition
    • -
  • new_version
    • -
  • partial_retraction
    • -
  • removal
    • -
  • retraction
    • -
  • withdrawal
    • -
- - - - - - - 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. - - - - - - - - - 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. - - - - - - - - - - - - - - - - - - - - - - - - - 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. - - - - - - - - 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. - - - - - 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. - - - - - 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. - - - - - 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) - - - - - Required attribute. This is the machine-readable name of the - assertion. Use the "label" attribute to provide a human-readable version of - the name. - - - - - 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. - - - - - Optional attribute - - - - - - - - - A wrapper for designators or other primary identifiers for a - standard. - - - - - - - - - - - - - - - - - - - - - - - - - - - Designator or other primary identifier for the standard being - deposited. Required. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Provides for defining a DOI for a broad grouping of standards. - - - - - - - Provides for defining a DOI for a set of standards (sometimes know as truncated form). - - - - - - - - - - - - - - Provides for defining a DOI for a group of closely related standard documents (undated form is a stem for any dated form) - - - - - - - - - - - - - - Designator for standard being replaced by the standard being deposited. - - - - - - Designator for standard from which the current deposit is adopted. - - - - - - Designator for the previous revision of the standard being deposited. (note: use alt_as_published for revisions within designators having common stem) - - - - - - A wrapper for standards body information. - - - - - - - - - - - Name of the standards organization / publisher. - Required. - - - - - Acronym for standards body. Will be used for query matching - - required. - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/tests/xsd/scielo_crossref/common5.5.0.xsd b/tests/xsd/scielo_crossref/common5.5.0.xsd new file mode 100644 index 0000000..77f8425 --- /dev/null +++ b/tests/xsd/scielo_crossref/common5.5.0.xsd @@ -0,0 +1,1266 @@ + + + + + + + + + + + + + + + + + + + + + + + The following are basic data types for face markup. Face markup that appears in the title, subtitle, and original_language_title elements should be retained when depositing metadata. Face markup in other elements (e.g. small caps in author names) must be dropped. Face markup support includes bold (b), italic (i), underline (u), over-line (ovl), superscript (sup), subscript (sub), small caps (scp), and typewriter text (tt). See https://support.crossref.org/hc/en-us/articles/214532023 + +MathML may also be included using the 'mml' namespace prefix. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + content is "Inline" except that anchors shouldn't be nested + + + + + + + + + + + + + + Publisher generated ID that uniquely identifies the DOI submission batch. + + + + + + + + + + + An integer representation of date and time that serves as a version number for the record that is being deposited, used to uniquely identify batch files and DOI values when a DOI has been updated one or more times. + + + + + Information about the organization submitting DOI metadata to Crossref + + + + + + + + + + + Name of the organization registering the DOIs. + + + + + + + + + + + e-mail address to which batch success and/or error messages are sent. + + + + + + + + + + + The organization responsible for the information being registered. + + + + + + + + + + + + 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. + + + + + + + + + + + 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. + + + + + + + + + + + + The issue number or name in which an article is published. 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. + + + + + + + + + + + + The container for elements related directly to a DOI. + + + + + + + + + + + + + The URI associated with a DOI. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Container for item elements containing non-primary URIs associated with the item being registered. Collections are supported for the following (defined in the property attribute): +
    +
  • list-based: Multiple Resolution, more info: https://www.crossref.org/education/content-registration/creating-and-managing-dois/multiple-resolution/
    • +
  • country-based: more info: https://www.crossref.org/education/content-registration/creating-and-managing-dois/multiple-resolution/#00130
    • +
  • crawler-based: for Similarity Check URLs, more info: https://www.crossref.org/education/similarity-check/participate/urls-for-new-deposits/
    • +
  • text-mining: supply specific URLs for text and data mining, more info: https://www.crossref.org/education/retrieve-metadata/rest-api/text-and-data-mining-for-members/
    • +
  • unspecified: can be used for additional URLs
    • +
  • syndication: identifies resources to be used for syndication
    • +
  • link-header: identifies resources to be used as an endpoint
    • +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + A container used to associate a URI with the DOI being registered. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + DOI for an entity being registered with Crossref. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + The ISBN assigned to an entity. + + + + + + + + + + + + + + + + + + + + + The ISSN assigned to the title being registered. + + + + + + + + + + + + + The volume number of a published journal, or the number of a printed volume for a book or conference proceedings. + + + + + + + + + + + + A list of articles, books, and other content cited by the item being registered + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + citation is used to deposit each reference in the reference list of the item for which the DOI is being deposited. For details see: + https://www.crossref.org/education/metadata-stewardship/maintaining-your-metadata/add-references/ + + + + + + + + + + + + + Used to assign a unique ID to each reference that is deposited. We use this key value to track the specific reference query and will return this value along with the DOI in your query results. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + A citation to an item that is not structured with the Crossref citation model. 'unstructured_citation' supports deposit of references for which no structural information is available. + + + + + + + + + + Journal title in a citation. + + + + + Book series title in a citation. + + + + + Book volume title in a citation. + + + + + First author in a citation. + + + + + Year of publication in citation. + + + + + Article title in a citation. + + + + + article identifier or e-location id of the item + + + + + + + Container element for CrossMark data. + + + + + + + + + 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). + + + + + + + + + + + + A DOI which points to a publisher's CrossMark policy document. Publishers might have different policies for different publications. + + + + + + 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 + + + + + + + + + + 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 sub-elements; a "domain" and a "filter". The filter 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. + + + + + + + + + + + A 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. + + + + + 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. + + + + + + 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. + + + + + + + + + + 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. + + + + + + + This attribute should be used to list the update type. Allowed update types are:
    +
  • addendum
    • +
  • clarification
    • +
  • correction
    • +
  • corrigendum
    • +
  • erratum
    • +
  • expression_of_concern
    • +
  • new_edition
    • +
  • new_version
    • +
  • partial_retraction
    • +
  • removal
    • +
  • retraction
    • +
  • withdrawal
    • +
+ + + + + + The date of the update will be displayed in the CrossMark dialog and can help the researcher easily tell whether they are likely to have seen the update. + + + + + + + + + Publishers are encouraged to provide 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. + + + + + + + + + + + + + + + + + + + + + + + + + An assertion is a piece of custom, non-bibliographic metadata that the publisher is asserting about the content to which the Crossmark refers. + + + + + + + + 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. + + + + + 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. + + + + + 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. + + + + + 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) + + + + + This is the machine-readable name of the assertion. Use the "label" attribute to provide a human-readable version of the name. + + + + + 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. + + + + + + + + + A wrapper for designators or other primary identifiers for a standard. + + + + + + + + + + + + + + + + + + + + + + + + + + + Designator or other primary identifier for the standard being deposited. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Provides for defining a DOI for a broad grouping of standards. + + + + + + + Provides for defining a DOI for a set of standards (sometimes know as truncated form). + + + + + + + + + + + + + Provides for defining a DOI for a group of closely related standard documents (undated form is a stem for any dated form) + + + + + + + + + + + + + Designator for standard being replaced by the standard being deposited. + + + + + Designator for standard from which the current deposit is adopted. + + + + + + Designator for the previous revision of the standard being deposited. (note: use alt_as_published for revisions within designators having common stem) + + + + + + A wrapper for standards body information. + + + + + + + + + + + Name of the standards organization / publisher. + + + + + Acronym for standards body. + + + + + + + + + + + + + + + + + + + + + + + + + + + + A wrapper for Scholarly Sharing Network (SCN) policy information + + + + + + + + + + + + A group of related SCN policies + + + + + + + + + + + + An individual SCN policy + + + + + + + + + + + + + + + + + + + + + + First page number of an item. + + + + + + + + + + + Last page number of an item. + + + + + + + + + + + When an item has non-contiguous page information, capture the first page range in first_page and last_page. Any additional page information should be captured in other_pages. + + + + + + + + + \ No newline at end of file diff --git a/tests/xsd/scielo_crossref/crossref4.4.0.xsd b/tests/xsd/scielo_crossref/crossref4.4.0.xsd deleted file mode 100644 index b2de142..0000000 --- a/tests/xsd/scielo_crossref/crossref4.4.0.xsd +++ /dev/null @@ -1,2086 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - Top level element for a metadata submission to CrossRef. This element - indicates the start and end of the XML file. The version number is fixed to the - version of the schema. Be sure to set the name space attributes as shown above in - order for the Xerces parser to process the instance correctly. For the purposes of - parsing, you may also set xsi:schemaLocation to http://www.crossref.org/schema/4.x.x - http://www.crossref.org /schema/4.x.x/crossref.xsd. A copy of the schema is located - on the CrossRef server at this URL and will remain constant for a given version of - the schema. This location permits you to have a constant location for the schema for - parsing without relying on a hardwired local directory on your development platform. - - - - - - - - - - - - - The container for information related to the DOI batch submission. - This element uniquely identifies the batch deposit to CrossRef and contains - information that will be used as a reference in error messages sent by the MDDB. - - - - - - - - - - - - - - The container for the main body of a DOI record submission. The body - contains a set of journal, book, conference proceedings or stand alone component - records. It is not possible to mix genres within a single DOI submission. It is - possible to include records for multiple journals, books, conferences, or stand - alone components in a single submission. - - - - - - - - - - - - - - - - - - - The container for all information about a single journal and the - articles being registered within the journal. journal is the core container for - information about a single journal and articles submitted for registration from that - journal. Within a journal instance, you may register articles from a single issue, - detailed in journal_issue. If you want to register items from more than one issue, - you must use multiple journal instances, which can be done within a single batch - submission. If you have articles that have not been assigned to an issue, you may - register them within a single journal instance. In this case, do not include a - journal_issue. You may chose to submit only top level journal_metadata and - journal_issue metadata for any journal or issue, allowing you to register DOIs for - an entire journal, or any issue or volume within a journal. - - - - - - - - - - - - The container for metadata that defines a - journal. - - - - - - - - - - - - - - - - - - The full title by which a journal is commonly known or cited. - full_title and abbrev_title must both be submitted even if they are identical. Note: - In version 4.1.0 and later, this element is allowed up to 10 times to allow for a) - journal name changes over time, b) translated journal names (e.g. the Japanese name - and the English equivalent), and c) common author mis-spellings of a given journal - name. - - - - - - - - - - - - This element contains the common abbreviation or abbreviations used - when citing this journal. It is preferred, but not required, that periods be - included after abbreviated words within the title. full_title and abbrev_title must - both be submitted, and they can be identical. If you do not know the abbreviated - title for a specific journal, please supply the full title in the abbrev_title - element. Note: In version 4.1.0 and later, this element is no longer required in - journal_metadata because some journals do not have abbreviated journal names. - - - - - - - - - - - - The container for metadata that defines a single issue of a journal. - Special issue numbering information for a journal should be placed in - special_numbering. You may register a DOI for an entire issue by including doi_data - in journal_issue. The URI should resolve to the table of contents for the issue. - contributors is included in journal_issue to allow inclusion of editors of special - issues. This element allows linking from a reference such as: R.Glaser, L.Bond - (Eds.), Testing: concepts and research, American Psychologist 36 (10-12) (1981) - (special issue). You should not include contributors for the regular editors of - regular issues. - - - - - - - - - - - Issue level numbering for supplements or special issues. - Text defining the type of special issue (e.g. "suppl") should be - included in this element along with the number. - - - - - - - - - - The container for the journal volume and DOI assigned to an entire - journal volume. You may register a DOI for an entire volume by including doi_data in - journal_volume. - - - - - - - - - - - - - Issue level numbering for supplements or special issues. Text - defining the type of special issue (e.g. "suppl") should be included in this element - along with the number. - - - - - - - - - - - The container for all information about a single journal article. A - journal article is required to have title and doi_data. All other information is - optional. When registering items that do not have titles, use the appropriate - heading from the journal section or table of contents (e.g. "Errata") in title. - journal_article allows for multiple titles per entity. In some cases it may be - helpful to submit multiple titles. For example, if an erratum carries title of the - original article and the heading "Errata", both should be submitted by using two - titles elements. - - - - - - - - The abstract element allows depositors to include - abstracts extracted from NLM or JATS XML in CrossRef deposits. The jats: - namespace prefix must be included. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - The container for all information about a single conference and its - proceedings. conference is the core container for information about a single - conference and its proceedings. If a conference proceedings spans multiple volumes, - each volume must be contained in a unique conference element. You may choose to - submit only top level contributors, event_metadata and proceedings_metadata for any - conference, or you may choose to submit these elements along with metadata for each - conference_paper. It is not necessary to submit metadata for all items listed on the - proceedings table of contents. You may chose to drop items of lesser significance - such as front and back matter. NOTE: The CrossRef system currently uses the - proceedings_title and conference_acronym in the query matching process. This system - can cause problems when the proceedings have a simple non-changing title (e.g - PRoceedings of SPIE) and the conference event name, conference_name, is used to - differentiate conference topics (e.g. Optoelectronic Integrated Circuits II). To - avoid this problem, CrossRef recommends that you make sure the conference_acronym - accurately reflects the event name (e.g OpIC II in this - example). - - - - - - - - - - - - - - - - A container for all information that applies to a conference event. - event_metadata captures information about a conference event. Data about conference - proceedings is captured in proceedings_metadata. NOTE: The CrossRef system currently - uses the proceedings_title and conference_acronym in the query matching process. - This system can cause problems when the proceedings have a simple non-changing title - (e.g PRoceedings of SPIE) and the conference event name, conference_name, is used to - differentiate conference topics (e.g. Optoelectronic Integrated Circuits II). To - avoid this problem, CrossRef recommends that you make sure the conference_acronym - accurately reflects the event name (e.g OpIC II in this - example). - - - - - - - - - - - - - - - - The official name of the conference. conference_name does not include - "Proceedings of". For example, "The 23rd Annual Meeting of the American Society for - Information Science" is a correct conference name. It is quite common for a - conference name to include the conference number or subject. When any of these - metadata items appear in the conference name, they should be included in this - element, and also in the respective sub-element, conference_number or - proceedings_subject. The following example shows incorrect tagging of a conference - name and then the corrected version: INCORRECT: - the second international conference - IEA/AIE '89 - 1989 - Tullahoma, TN - - - - Proceedings of the second international conference on - Industrial and engineering applications of artificial intelligence and - expert systems - IEA/AIE'89 - Industrial and engineering applications of artificial - intelligence and expert systems - CORRECT: - The second international conference on Industrial and - engineering applications of artificial intelligence and expert - systems - IEA/AIE '89 - 2 - Tullahoma, TN - - - - Proceedings of the second international conference on - Industrial and engineering applications of artificial intelligence and - expert systems - IEA/AIE '89 - Industrial and engineering applications of artificial - intelligence and expert systems - Authors commonly cite a conference by the official name, so - it is important to provide this information as accurately as - possible. - - - - - - - - - - - The theme is the slogan or special emphasis of a conference in a - particular year. The theme is the slogan of the conference. It differs from the - subject of a conference in that the subject is stable over the years while the theme - may vary from year to year. For example, the American Society for Information - Science and Technology conference theme was "Knowledge: Creation, Organization and - Use" in 1999 and "Defining Information Architecture" in 2000. - - - - - - - - - - - The popularly known as or jargon name (e.g. SIGGRAPH for "Special - Interest Group on Computer Graphics"). Authors commonly cite the conference acronym - rather than the full conference or proceedings name, so it is best to include this - element when it is available. The conference acronym often includes the year of the - conference (e.g. SGML '97) or, less often, the conference number. It is preferred, - but not required, that submission of metadata exclude number or year information - from the conference acronym. It is better to include such information in - conference_number, or conference_date, respectively. - - - - - - - - - - - The sponsoring organization(s) of a conference. Multiple sponsors may - be given if a conference is hosted by more than one - organization. - - - - - - - - - - - The number of a conference. conference_number should include only the - number of the conference without any extra text. For example, "The 24th Annual - Conference on..." should be tagged as shown in the example above, and "th" should - not be included. Roman numerals are acceptable. When a conference is named such that - the year of the conference indicates the number (e.g. "SGML 1994"), the year appears - in conference_name, conference_date, and conference_number, as in: - SGML 1994 - SGML - 1994 - November 7-10, 1994 - - - - - - - - - - - - The location of the conference. The city and country of the - conference. If the conference is in the United States, the appropriate state should - also be provided, and the country may be omitted. If the conference is in Canada, - the province should be provided, and the country may be omitted. The specific venue - or address within a city (e.g. conference center, hotel, etc.) should not be - provided. - - - - - - - - - - - - - - - - - The start and end dates of a conference event. conference_date may be - used in three ways: 1. If publishers that do not have parsed date values, provide - just text with the conference dates. The date text should be taken from the - proceedings title page. 2. If publishers have parsed date values, provide them in - the attributes. 3. If both parsed date values and the date text are available, both - should be provided. This is the preferred tagging for conference_date. For example: - Jan. 15-17, 1997 - - - - - - - - - - - - - - - - - - A container for all information that applies to a non-series - conference proceeding. proceedings_metadata captures information about conference - proceedings. Data about conference events is captured in - event_metadata - - - - - - - - - - - - - - - - - - - - - - - A container for all information that applies to a specific conference - proceeding that is part of a series. A conference proceedings published as a series - can sometimes look just like a journnal in that there is no volume information (no - volume title, no ISBN). In these cases the conference proceeding may be deposited as - a journal (which more accurately should have been called a 'series_publication'). To - allow for the use of a consistent XML heirarchy we will allow a - proceedings_series_metadata root element to also describe such a publication. Note: - this structure is organized to allow backward compatibility with previous schema - versions by maintaining the prior sequence of elements. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - The title of the conference proceedings as printed on title page of - the published conference proceedings. proceedings_title is the undifferentiated - title of a conference proceedings. It should generally be the title as it appears on - the cover of the printed proceedings. In some cases, proceedings_title may differ - from conference_name only in that the text "Proceedings of" often appears at the - start of the proceedings_title, and it this text should never be included in - conference_name. In other cases, the proceedings_title and conference_name may be - quite different. - - - - - - - - - - - The subject of the printed conference proceedings, e.g. "Computer - Graphics" is the subject matter of SIGGRAPH. This element is useful because an - author may cite a conference paper by the conference subject. For example, - "Proceedings of the 1999 ACM Conference on Computer Graphics" - - - - - - - - - - - The container for all information about a single conference paper. A - conference paper is required to have contributors, title and doi_data. All other - information is optional. - - - - - - - - The abstract element allows depositors to include - abstracts extracted from NLM or JATS XML in CrossRef deposits. The jats: - namespace prefix must be included. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - The container for all information about a single book. book is the - core container for information about a specific book. Books may be in the form of - edited books (i.e. a contributed volume with one or more editors), monographs - (single-authored works), or reference works (e.g. encyclopedias). If a book contains - multiple volumes, each volume must be contained in a unique book element. You may - chose to submit only top level contributors and book_metadata for any book, or you - may chose to submit these elements along with metadata for each content_item. A - content item is typically any entity that is listed on the table of contents such as - a chapter, section, etc. It is not necessary to submit metadata for all items listed - on the table of contents. You may chose to drop items of lesser significance such as - front and back matter. Book-level metadata is captured within book_metadata, - book_series_metadata, or book_set_metadata. If a books is a single-volume work, use - book_metadata. If the book is a volume from a multi-volume work that is also a - serial publication (and therefore has an ISSN), use book_series_metadata. If the - book is a volume of non-serial publication, then it is considered a set and you - should use book_set_metadata book_type should be set to "monograph" when the same - author or authors wrote the majority of the content. It should be set to - "edited_book" when a book primarily consists of contributed chapters, each chapter - written by different authors. It should be set to "reference" for major reference - works such as encyclopedias. Use "other" when the author of the content does not fit - any of the other categories. - - - - - - - - - - - - - - - - - - - - - - - - - A container for all information that applies to a monograph. It does - not include metadata about individual chapters. The language of the book should be - specified in the book_metadata language attribute. If a book contains items in - multiple languages this attribute should be set for the predominant language of the - book. Individual items may have their language specified in content_item. If all - content items are the same language, it is only necessary to specify the language of - the book in this element. The contributors are the author(s) or editor(s) of the - entire work. When using book_metadata, specify the title of the book within - book_metadata. edition_number, when given, should include only a number and not - additional text such as "edition" or "ed". publisher_item, when given, specifies - this information for the entire book or volume. This element also appears in - content_item. doi_data is required for each book or volume that you submit. It is - not possible to submit DOI information for individual chapters without assigning a - DOI to the entire work. Note: citation_list should only be used in book_metadata - instead of content_item when the reference list is a separate section of the book, - and content_items are not included in the deposit (e.g. you are depositing a book - with a bibliography, but not the chapters of the book) In very limited circumstances - a book may be deposited without an ISBN, in which case the noisbn element must be - supplied to explicitly declare that an ISBN is not accidentily omitted. Great care - should be taken when choossing to use noisbn since it may adversely effect matching. - This provision is primarily being made to allow for the deposit of DOIs for - historical volumes that are difficult to obtain ISBNs. - - - - - - - - The abstract element allows depositors to include - abstracts extracted from NLM or JATS XML in CrossRef deposits. The jats: - namespace prefix must be included. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - A container for all information that applies to an individual volume - of a book series. It does not include metadata about individual chapters. The - language of the book should be specified in the book_series_metadata language - attribute. If a book contains items in multiple languages this attribute should be - set for the predominant language of the book. Individual items may have their - language specified in content_item. If all content items are the same language, it - is only necessary to specify the language of the book in this element. The - contributors are the author(s) or editor(s) of the entire work. If a multi- volume - work has separate editors for each volume, those editors should be specified in this - element, and the series editors are listed in the series_metadata contributors. - Series titles should be specified within series_metadata. Volume titles (when - present) are captured in book_series_metadata. If the volumes of a series only have - volume numbers and not individual titles, you may specify the volume number within - volume_metadata, and no title is required. volume and edition_number, when given, - should include only a number and not additional text such as "volume" or "edition". - For example, you should submit "3", not "third edition". If a work spans multiple - volumes with a unique ISBN for each volume and the whole series, you should specify - the series ISBN in isbn in series_metadata and the volume ISBN in isbn in - book_series_metadata. WARNING: Care must be taken when submitting books with series. - If a series title is submitted and no book title is supplied but an ISBN is supplied - at the book_series_metadata level and not with the series title, the CrossRef system - will index a series title with no ISBN and an ISBN with no title. Please take care - to associate the ISBN at the correct level of the XML hierarchy. publisher_item, - when given, specifies this information for the entire book or volume. This element - also appears in content_item. doi_data is required for each book or volume that you - submit. It is not possible to submit DOI information for individual chapters without - assigning a DOI to the entire work. Note: citation_list should only be used in - book_series_metadata instead of content_item when the reference list is a separate - section of the book, and content_items are not included in the deposit (e.g. you are - depositing a book with a bibliography, but not the chapters of the book) Normally - book content that is published as a series is required to have a series title with - an ISSN and a book title and/or a book volume number along with a book ISBN. An - exception is when book chapters are published on line first prior to being assigned - to a specific book in which case only the series title (and ISSN) is known at time - of DOI registration. Element unassigned_content is used as a placeholder to force - recognition of this condition and thus prevent accidental omission of book level - title information. - - - - - - - - - - - - - The abstract element allows depositors to - include abstracts extracted from NLM or JATS XML in - CrossRef deposits. The jats: namespace prefix must be - included. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - A container for all information that applies to an individual volume - of a book set. It does not include metadata about individual chapters. A set is a - finite series, and does not have an ISSN The language of the book should be - specified in the book_set_metadata language attribute. If a book contains items in - multiple languages this attribute should be set for the predominant language of the - book. Individual items may have their language specified in content_item. If all - content items are the same language, it is only necessary to specify the language of - the book in this element. The contributors are the author(s) or editor(s) of the - entire work. If a multi- volume work has separate editors for each volume, those - editors should be specified in this element, and the series editors are listed in - the series_metadata contributors. When using book_set_metadata, specify the title of - the entire set and the isbn of the set. Specify the title of the volume in - volume_metadata. If the volumes of a set only have volume numbers and not individual - titles, you may specify the volume number within volume_metadata, and no title is - required. volume and edition_number, when given, should include only a number and - not additional text such as "volume" or "edition". For example, you should submit - "3", not "third edition". If a work spans multiple volumes with a unique ISBN for - each volume and the whole series, you should specify the series ISBN in isbn in - series_metadata and the volume ISBN in isbn in book_series_metadata. publisher_item, - when given, specifies this information for the entire book or volume. This element - also appears in content_item. doi_data is required for each book or volume that you - submit. It is not possible to submit DOI information for individual chapters without - assigning a DOI to the entire work. Note: citation_list should only be used in - book_series_metadata instead of content_item when the reference list is a separate - section of the book, and content_items are not included in the deposit (e.g. you are - depositing a book with a bibliography, but not the chapters of the - book) - - - - - - - - - - - The abstract element allows depositors to include - abstracts extracted from NLM or JATS XML in CrossRef deposits. - The jats: namespace prefix must be included. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - An entity in a book, such as a chapter, for which a DOI is being - registered. A content item is typically an entity listed on the table of contents. - There need not be a one-to-one correlation between content listings and content - items (e.g. you may choose not to register front and back matter items listed in the - table of contents). The language of a content_item only need be set if it differs - from the language of book_metadata. The component_type indicates the type of content - item you are registering. Please see the example of a book submission in this - documentation for a better understanding of how this attribute may be used in nested - tables of contents. level_sequence_number indicates the level of nesting for content - items. For example, you may use it to indicate when one content item, such as a - chapter, is actually inside another content item, such as a section. Please see the - example of a book submission in this documentation for a better understanding of how - this attribute may be used in nested tables of contents. Note: Because the CrossRef - schema uses a flat model to indicate hierarchically nested content items, there is - an implicit assumption that content items will be listed in the CrossRef submission - in the same order in which they appear in the table of contents. Please follow this - protocol when submitting DOI data for books. This order is not required for journal - and conference data. contributors for a content_item need not be listed if all items - in a book have the same contributors listed in book_metadata. In other words, - contributors must be listed for edited books, but they should not be listed for each - content_item in a monograph. The exception case is when a content item such as a - Preface or Forward for a monograph has a different author from that of the - monograph. In this case, the contributors should be given. The title of each content - item must be submitted. If, however, you are submitted data for a monograph that - simply has "Chapter 1", "Chapter 2", etc., you should put this information in - component_number, not titles. - - - - - - - - The abstract element allows depositors to include - abstracts extracted from NLM or JATS XML in CrossRef deposits. The jats: - namespace prefix must be included. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - The container for metadata about a series publication. When a book, - conference proceeding, or report consists of multiple volumes, series_metadata is - used to describe information about the entire series. If a work spans multiple - volumes, you should use titles in series_metadata. If a work spans multiple volumes - with a unique title for each volume and the whole series, you should specify the - series title in titles in series_metadata and the volume title in titles in - book_series_metadata. If a unique ISBN has been assigned to the entire series (as - opposed to the individual volumes), it should given in series_metadata. You may - assign and register a DOI that encompasses an entire series by adding doi_data in - series_metadata. This element is optional for a series. - - - - - - - - The abstract element allows depositors to include - abstracts extracted from NLM or JATS XML in CrossRef deposits. The jats: - namespace prefix must be included. - - - - - - - - - - - - - - - - - - - - - When a book consists of multiple volumes that are not part of a - serial publication (series), set_metadata is used to describe information about the - entire set. - - - - - - - - - - - - - - - - - - - The series number within a specific published conference discipline. - The series number is different from the volume number. A volume number is the number - of a book in a physically printed set and typically appears in sequence. The series - number is not tied to the physical manifestation of the printed volume and need not - be strictly in sequence. It is most commonly used in "Lectures" published by - Springer-Verlag. This element is available in series_metadata, however it should - only be used for conference proceedings, not for books. - - - - - - - - - - - The part number of a given volume. Deposited within - book_set_metadata. In some cases, a book set will have multiple parts, and then one - or more volumes within each part. The part number of a given volume should be - deposited in this element. - - - - - - - - - - - A container for information about the publisher of a book or - conference proceedings. - - - - - - - - - - - The city where the publisher of this work is located. publisher_place - gives the primary city location of the publisher. When the location is a major city - (e.g. New York, Amsterdam), no qualifying country, U.S. state, or Canadian province - need be given. If the city is not a major city, the appropriate country, U.S. state, - or Canadian province should be added. - - - - - - - - - - - The name of the publisher of a book or conference proceedings. - publisher_name is the imprint of the publication (what the author will likely cite), - not the organization registering the DOI, if for any reason they are different. When - registering a translation, the translation publisher, not the original publisher, - should be given. - - - - - - - - - - - - A container for item identification numbers set by a publisher. - item_number within publisher_item may also be used to provide an article number when - a first_page is not available or applicable. In certain cases it may be deemed - in-appropriate to 'misuse' the first_page element to provide a value that has - meaning in an on-line only publication and does not convey an form of page number. - In these circumstances the attribute <item_number - item_number_type="article-number"> will instruct the CrossRef system to treat the - value of item_number in the same manner as first_page. This value then becomes a - critical part of the query process. If both <item_number - item_number_type="article-number"> and first_page are present, first_page will - take precedence. - - - - - - - - - - - - - - - - - A publisher identifier that can be used to uniquely identify the - entity being registered. This identifier is a publisher-assigned number that - uniquely identifies the entity being registered. This element should be used for - identifiers based on publisher internal standards. Use identifier for a publisher - identifier that is based on a public standard such as PII or SICI. If the - item_number and identifier are identical, there is no need to submit both. In this - case, the preferred element to use is identifier. Data may be alpha, numeric or a - combination. item_number has an optional attribute, item_number_type. It is assigned - by the publisher to provide context for the data in item_number. If item_number - contains only a publisher's tracking number, this attribute need not be supplied. If - the item_number contains other data, this attribute can be used to define the - content. For example, if a journal is published online (i.e. it has no page - numbers), and each article on the table of contents is assigned a sequential number, - this article number can be placed in item_number, and the item_number_type attribute - can be set to "article_number". Although CrossRef has not provided a set of - enumerated types for this attribute, please check with CrossRef before using this - attribute to determine if a standard attribute has already been defined for your - specific needs. If a dissertation DAI has been assigned, it should be deposited in - the identifier element with the id_type attribute set to "dai". If an institution - has its own numbering system, it should be deposited in item_number, and the - item_number_type should be set to "institution" If the report number of an item - follows Z39.23, the number should be deposited in the identifier element with the - id_type attribute set to "Z39.23". If a report number uses its own numbering system, - it should be deposited in the identifier element, and the id_type should be set to - "report-number" The designation for a standard should be placed inside the - identifier element with the id_type attribute set to "ISO-std-ref" or - "std-designation" (more generic label) - - - - - - - - - - - - - - - - - - A public standard identifier that can be used to uniquely identify - the entity being registered. This identifier is a publisher-assigned number that - uniquely identifies the entity being registered. This element should be used for - identifiers based on public standards. Use item_number for a publisher identifier - that is based on a publisher's internal systems rather than on a public standard. - The supported standards are: PII - Publisher Item Identifier SICI - Serial Item and - Contribution Identifier DOI - Digital Object Identifier - - - - - - - - - - - - - - - - - - - - - - - - - - - dissertation is the top level element for deposit of metadata about - one or more dissertations. The dissertation element does not have publisher, or issn - elements. It is expected that the dissertation element will be used for deposit of - items that have not been published in books or journals. If a dissertation is - published as a book or within a serial, it should be deposited using the top-level - element for the appropriate publication type. If a DAI has been assigned, it should - be deposited in the identifier element with the id_type attribute set to "dai". If - an institution has its own numbering system, it should be deposited in item_number, - and the item_number_type should be set to "institution" - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - report-paper is the top level element for deposit of metadata about - one or more reports or working papers. component_list is included in report-paper to - handle items that have components but do not have content_item elements (i.e. a - report that is not divided into multiple chapters). If an item has content_item - elements, then component_list inside of content_item must be used rather than the - element available in report-paper - - - - - - - - - - - - - - - - report-paper_metadata is used as a wrapper for the metadata related - to a Technical Report or Working Paper. report-paper_metadata is almost identical to - book_metadata. It differs only in that report-paper_metadata removes the volume - number and adds the elements institution and contract_number. Please see the - comments for book_metadata about the usage of most elements in report- - paper_metadata. Reports and Working Papers are often sponsored by either - universities or by a non-academic organization (corporate or government). Such - institutions are not typically considered "publishers" and so the item may be - deposited using the institution element. Multiple element instances are permitted so - the sponsoring institution and publishing institution can both be deposited as - authors may cite either. If the report number of an item follows Z39.23, the number - should be deposited in the identifier element with the id_type attribute set to - "Z39.23". If a report number uses its own numbering system, it should be deposited - in item_number. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - report-paper_series_metadata is used as a wrapper for the metadata - related to a Technical Report or Working Paper that is part of a series. - report-paper_series_metadata is almost identical to book_series_metadata. It differs - only in that report-paper_metadata removes the volume number and adds the elements - institution and contract_number. Please see the comments for book_series_metadata - about the usage of most elements in report- paper_series_metadata. Reports and - Working Papers are often sponsored by either universities or by a non-academic - organization (corporate or government). Such institutions are not typically - considered "publishers" and so the item may be deposited using the institution - element. Multiple element instances are permitted so the sponsoring institution and - publishing institution can both be deposited as authors may cite either. If the - report number of an item follows Z39.23, the number should be deposited in the - identifier element with the id_type attribute set to "Z39.23". If a report number - uses its own numbering system, it should be deposited in - item_number. - - - - - - - - - - - The abstract element allows depositors to include - abstracts extracted from NLM or JATS XML in CrossRef deposits. - The jats: namespace prefix must be included. - - - - - - - - - - - - - - - - - - - - - - - - - - - standard is the top level element for deposit of metadata about - standards developed by Standards Development Organizations (SDOs) or Consortia. - CrossRef does not determine if a new DOI should be created for each revision or - reaffirmation of a standard. The decision will be left to the individual standards - organizations. As of schema version 4.3.3, CrossRef recommends that the full - standard designation be placed in the as_published element (within - standard_designator). For backwards compatibility, the full designation may also be - included in the identifier element with the id_type attribute set to "ISO-std-ref". - In addition, CrossRef requires that the publisher of the standard be included in - standards_body_name, and the acronym within standards_acronym. The as_published and - standards_acronym elements will be combined to identify a standard for query - matching. component_list is included in standard to handle items that have - components but do not have content_item elements (i.e. a standard that is not - divided into multiple chapters). If an item has content_item elements, then - component_list inside of content_item must be used rather than the parent standard - element. - - - - - - - - - - - - - - - - Standard_metadata is used as a wrapper for the metadata related to a - Standard that is not part of a series. standard_metadata is similar to - book_metadata. It differs in that standard_metadata adds the elements institution - and approval_date. contributors contains the author(s) of the standard. In most - cases, it is expected that the organization element will be used rather than - person_name element for standards. However in some cases, standards are cited by - their individual authors. In such cases, individual authors should be deposited with - person_name, and the SDO or consortia name should be deposited with the organization - element in contributors and also the standards_body_name element in standards_body - Note that when the organization element is used in contributors, it should have the - name of the committee (when appropriate) that developed the standard, not the name - of the Standards Development Organization (SDO) or consortia. The SDO or consortia - name should be placed in the publisher or standards_body element (as appropriate) - Standards more often have version numbers than edition numbers. However the - edition_number element can be used for deposit of the version number of a standard - approval_date should be used for the date that a standard has been accepted or - re-affirmed if different from the date of publication. Both may be provided even if - identical Within publisher_item, the designation should be placed inside the - item_number element, and the id_type should be set to "designation" to indicate a - standard designation. Standards are typically sponsored or hosted by SDOs or - Consortia. In some cases standards are published by a traditional publisher rather - than by the owning organization. Such cases may be deposited with one or more - publishers. - - - - - - - - The abstract element allows depositors to include - abstracts extracted from NLM or JATS XML in CrossRef deposits. The jats: - namespace prefix must be included. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - database is the top level element for deposit of metadata about one - or more datasets or records in a database. Database structures allow for the - assignment of DOIs to entire databases at the aggregate level and at two lower - levels. The top level may be a physical/functional database or a logical abstration - acting as a collection much the same as a journal is a collection of articles. The - need to assign specific fields of metadata at each level depends on the nature of - the top most level (e.g. publication date may be appropriate at the top level for a - physical object but only at lower levels for an abstract top level object) The first - sub-level is the dataset which may be a basic record of the top level object or a - collection in its own right. In either case dataset must represent a physical - construct. A third level is provided in the component_list. NOTE: component_list in - <database> (rather than in dataset may be used as a second level when no third - level is required and the second level objects derive most of their qualities from - the parent. NOTE: This model is not intended to show relationships between different - dataset entries in the form of a relational database. However in the future it is - possible that multiple resolution may be used to express such - relationships - - - - - - - - - - - - - - database_metadata contains metadata about the database. contributors - contains the author(s) of the database. In most cases, it is expected that the - organization element will be used rather than person_name element for the primary - database authoring information. contributors should not be confused with publisher - and institution. In many cases, databases are more likely to have one or both of the - latter elements rather than contributors at the top level (dataset elements are more - likely to have contributors). In most cases, the institution element may be the best - choice to deposit the database host organization because it includes the - institution_acronym element along with the name. The titles element is used to - capture the name of the database. The description element can be used to capture a - fuller description of the nature of the database than might be inferred from the - title. database_date should be used to capture the date that a database was first - created. Whenever updated records are deposited with CrossRef, the update_date - should be set to the date of the most recent CrossRef deposit. publisher_item may be - used to record an identifying number for the database other than the - DOI. - - - - - - - - - - - - - - - - - - - - - - dataset is used to capture information about one or more database - records or collections. The dataset_type attribute should be set to either "record" - or "collection" to indicate the type of deposit. The default value of this attribute - is "record". dataset entries are not intended to contain the entire database record - or collection. They are only intended to contain the metadata for each database - record or collection. The metadata can include: contributors: the author(s) of a - database record or collection titles: the title of a database record or collection - database_date: the creation date, publication date (if different from the creation - date) and the date of last update of the record publisher_item: the record number of - the dataset item. In this context, publisher_item can be used for the record number - of each item in the database. description: a brief summary description of the - contents of the database format: the format type of the dataset item if it includes - files rather than just text. Note the format element here should not be used to - describe the format of items deposited as part of the component_list doi_data: the - doi of the item. citation_list: a list of items (e.g. journal articles) cited by the - dataset item. For example, dataset entry from a taxonomy might cite the article in - which a species was first identified. component_list: a list of components included - in the dataset item such as supporting figures - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Posted-content is for the assignment of DOIs to content that may - subsequently be formally published. Non-DOI identifiers associated with the content - may be recorded in the item_number element. We encourage the inclussion of an - abstract. The relation program (rel:program) should be used to link this content - item to other DOIs including the DOI of the published version of record. Pre-print - should not be used to assign DOIs to accepted manuscripts. A DOI may be assigned to - an accepted manuscript using the content type appropriate for early registration. - DOIs assigned to accepted manuscripts should be reused (e.g. reassigned to the - published article). POsted-contnet DOIs must be continuously supported by maintaining - their metadata and the URL at which the content is available. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Prepublication content items may be organzed into groupings within a given publisher. - This element provides for naming the group. It is expected that publishers will have a small number of groups - each of which reflect a topic or subject area. - - - - - - - - - - - - Wrapper element for information about an organization that sponsored - or hosted an item but is not the publisher of the item. The institution element - should be used to deposit metadata about an organization that sponsored or hosted - the research or development of the published material but was not actually the - publisher of the information. The institution is distinctly different from the - publisher because it may not be a publishing organization. It is typically an - organization such as a university, corporation, government agency, NGO or consortia. - If the content was published by an organization other than the sponsor, the use of - both the publisher and institution elements is encouraged because authors may cite - either one in a reference, and the availability of both may allow for more precise - matching in queries. - - - - - - - - - - - - - The full name of an institution. Examples are: World Health - Organization; University of California, Davis. Corresponding institution_acronym - content for these organizations would be WHO and UCD, - respectively. - - - - - - - - - - - The acronym of the institution. Note that authors often cite with - acronyms and this information can be important in matching a query Examples: WHO, - UCDavis, UCD Note: as shown above, an institution may be know by multiple acronyms, - in which case all common acronyms should be deposited. - - - - - - - - - - - The primary city location of the institution. institution_place gives - the primary city location of the institution. When the location is a major city - (e.g. New York, Amsterdam), no qualifying country or U.S. state need be given. If - the city is not a major city, the appropriate country and/or state or province - should be added. - - - - - - - - - - - The department within an institution. institution_department gives - the department within an institution. A common use is the department under which a - dissertation was completed. Note that the institution_department is repeatable. If - multiple departments are to be deposited, each one should be given in a unique - institution_department element. Example: Department of Psychology - - - - - - - - - - - - - - The degree(s) awarded for a dissertation. - - - - - - - - - - - The contract number under which a report or paper was - written. - - - - - - - - - diff --git a/tests/xsd/scielo_crossref/crossref5.5.0.xsd b/tests/xsd/scielo_crossref/crossref5.5.0.xsd new file mode 100644 index 0000000..5bf9b79 --- /dev/null +++ b/tests/xsd/scielo_crossref/crossref5.5.0.xsd @@ -0,0 +1,2210 @@ + + + + + + + + + + + + + + + + + + + + + + + + Top level element for a metadata record submission. This element indicates the start and end of the XML file. The version number is fixed to the version of the schema. + + + + + + + + + + + + Container for information related to the DOI batch submission. This element uniquely identifies the batch deposit to Crossref and contains information that will be used as a reference in error messages triggered during submission processing. + + + + + + + + + + + + + + + Container for the main body of a DOI record submission. While it is possible to include records for multiple journals, books, conferences, or other types of content in a single submission, it is not possible to mix content types within a single DOI submission. + + + + + + + + + + + + + + + + + + + + + + + Container for all information about a single journal and the volumes, issues, and articles being registered within the journal. Within a journal instance you may register articles from a single issue, detailed in journal_issue. If you want to register items from more than one issue you must use multiple journal instances within your XML file. + + + + + + + + + + + + Container for metadata that defines a journal. + + + + + + + + + + + + + + + + The full title by which a journal is commonly known or cited. + + + + + + + + + + + + Common abbreviation or abbreviations used when citing a journal. It is recommended that periods be included after abbreviated words within the title. + + + + + + + + + + + + Container for metadata that defines a single issue of a journal. + + + + + + + + + + + + + + + + + Container for the journal volume and DOI assigned to an entire journal volume. You may register a DOI for an entire volume by including doi_data in journal_volume. + + + + + + + + + + + + + Issue level numbering for supplements or special issues. Text defining the type of special issue (e.g. "suppl") should be included in this element along with the number. + + + + + + + + + + + Container for all information about a single journal article. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Container for all information about a single conference and its proceedings. If a conference proceedings spans multiple volumes, each volume must be contained in a unique conference element. + + + + + + + + + + + + + + + + A container for all information that applies to a conference event. event_metadata captures information about a conference event. Data about conference proceedings is captured in proceedings_metadata. + + + + + + + + + + + + + + + + The official name of the conference, excluding numbers commonly provided in conference + + + + + + + + + + + The theme is the slogan or special emphasis of a conference in a particular year. It differs from the subject of a conference in that the subject is stable over the years while the theme may vary from year to year. For example, the American Society for Information Science and Technology conference theme was "Knowledge: Creation, Organization and Use" in 1999 and "Defining Information Architecture" in 2000. + + + + + + + + + + + The popularly known as or jargon name (e.g. SIGGRAPH for "Special Interest Group on Computer Graphics"). Authors commonly cite the conference acronym rather than the full conference or proceedings name, so it is best to include this element when it is available. + + + + + + + + + + + The sponsoring organization(s) of a conference. Multiple sponsors may be given if a conference is hosted by more than one organization. + + + + + + + + + + + The number of a conference. conference_number should include only the number of the conference without any extra text + + + + + + + + + + + The location of the conference. The city, state, province or country of the conference may be provided as appropriate. + + + + + + + + + + + + + + + + + The start and end dates of a conference event. conference_date may be used in three ways: + 1. If publishers that do not have parsed date values, provide just text with the conference dates. The date text should be taken from the proceedings title page. + 2. If publishers have parsed date values, provide them in the attributes. + 3. If both parsed date values and the date text are available, both should be provided. This is the preferred tagging for conference_date. For example: + Jan. 15-17, 1997 + + + + + + + + + + + + + + + + + + Container for all information that applies to a non-series conference proceeding. + + + + + + + + + + + + + + + + + + + + + + Container for all information that applies to a specific conference proceeding that is part of a series. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + The undifferentiated title of a conference proceeding. + + + + + + + + + + + The subject of the conference proceeding, e.g. "Computer Graphics" is the subject matter of SIGGRAPH. + + + + + + + + + + + Container for all information about a single conference paper. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Container for all information about a single book. + + + + + + + + + + + + + + + + + + + + + + + + + A container for all title-level metadata for a single book that is not part of a series or set. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + A container for all information that applies to an individual volume of a book series. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + A container for all information that applies to an individual volume of a book set. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + A segment of a book, report, or standard for which a DOI is being registered. Most commonly used for book chapters. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Container for metadata about a series publication. + + + + + + + + The abstract element allows depositors to include abstracts extracted from NLM or JATS XML in Crossref deposits. The jats: namespace prefix must be included. + + + + + + + + + + + + + + + + + + + + + + When a book consists of multiple volumes that are not part of a serial publication (series), set_metadata is used to describe information about the entire set. + + + + + + + + + + + + + + + + + + + The series number within a specific published conference discipline. + + + + + + + + + + + The part number of a given volume. In some cases, a book set will have multiple parts, and then one or more volumes within each part. The part number of a given volume should be deposited in this element. + + + + + + + + + + + + + + dissertation is the top level element for deposit of metadata about one or more dissertations. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + report-paper is the top level element for deposit of metadata about one or more reports or working papers. + + + + + + + + + + + + + + + + Container for the metadata related to a Technical Report or Working Paper. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Container for the metadata related to a technical report or working paper that is part of a series. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + standard is the top level element for deposit of metadata about standards developed by Standards Development Organizations (SDOs) or Consortia. + + + + + + + + + + + + + + + + Container for the metadata related to a Standard that is not part of a series. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + database is the top level element for deposit of metadata about one or more datasets or records in a database. + + + + + + + + + + + + + + database_metadata contains metadata about the database. + + + + + + + + + + + + + + + + + + + + + + dataset is used to capture information about one or more database records or collections. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Used to define a publication (book, journal, etc.) for pending publication content. A title must be supplied, as well as an ISSN, ISBN, or title-level DOI + + + + + + + + + + + + + + + + + + + + + + + + + + Member's custom statement of intent to publish content for which a pending publication DOI has been created + + + + + + + + + + + + + + + + The peer_review content type is intended for assigning DOIs to the reports and other artifacts associated with the review of published content. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Required attribute. First submission defined as revision round zero + + + + + + + + + + + Statement of competing interest supplied by a review author during the review process. + + + + + + + + + + + + Running numbers to specify the various reports (ex: RC1 to RC4) + + + + + + + + + + + Container for 'pending publication' metadata. Pending publication DOIs are used to create a DOI for a content item that is not yet available online or in print. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Container for posted content metadata. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Posted content may be organized into groupings within a given publisher. This element provides for naming the group. It is expected that publishers will have a small number of groups each of which reflect a topic or subject area. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Container element for information about an institution or organization associated with an item. + + + + + + + + + + + + + + + + + + + The full name of an institution. + + + + + + + + + + + Identifier for an institution or organization (currently supported: ROR, ISNI, Wikidata). Identifiers must be included as a URI + + + + + + + + + + + + + + + + + + + + + + + + + The acronym of the institution. + + + + + + + + + + + The primary city location of the institution. institution_place gives the primary city location of the institution. When the location is a major city (e.g. New York, Amsterdam), no qualifying country or U.S. state need be given. If the city is not a major city, the appropriate country and/or state or province should be added. + + + + + + + + + + + The department within an institution. + + + + + + + + + + + + + The degree(s) awarded for a dissertation. + + + + + + + + + + + The contract number under which a report or paper was written. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + specific contribution made by an individual or organisation to research + + + + + + + + + + + + + The container for all who contributed to authoring or editing an item. + + + + + + + + + + + + + + + + + + + + + The name of an organization (as opposed to a person) that contributed to an item. If an item was authored by individuals in addition to one or more organizations, person_name and organization may be freely intermixed within contributors. + + + + + + + + + + + + The name of a person (as opposed to an organization) that contributed to an item. + + + + + + + + + + + + + + + + + + Used to capture anonymous contributors. + + + + + + + + + + + + A contributor's given name. + + + + + + + + + + + + The family name of a contributor. + + + + + + + + + + + + The suffix of an author name, e.g. junior, senior, III. + + + + + + + + + + + + + + + + The ORCID iD for an author. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Container for component metadata if the component is being registered after the parent record/DOI is created. + + + + + + + + + + + + + + + + + + Container for a group of components + + + + + + + + + + Container for component metadata. Supplemental materials, figures, tables, and other items that can be considered a citeable part of a registered item may be registered as components. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + A container for the title and original language title elements. + + + + + + + + + + + + + + + + + The title of the item being registered. + + + + + + + + + + The title of an item in its original language if the registration is for a translation of a work. + + + + + + + + + + + The sub-title portion of a title. + + + + + + + + + + + + + + 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. + + + + + Day of publication. The day must be expressed with a leading zero if it is less than 10 (e.g. submit "05", not "5"). + + + + + Year of publication. + + + + + Container for key dates in the life of a database or dataset. + + + + + + + + + + + + The date a database or dataset item was created. + + + + + + + + + + The date a piece of content was created. + + + + + + + + + + The date a pre-print was posted to a repository. + + + + + + + + + + The date a manuscript was accepted for publication. + + + + + + + + + + The date a dataset or database was last updated. + + + + + + + + + + The date of publication. Multiple dates are allowed to allow for different dates of publication for online and print versions. + + + + + + + + + + + + + + + + + + + + + + + + + + The date a review was published to a repository. + + + + + + + + + + + + The date on which a dissertation was accepted by the institution awarding the degree, a report was approved, or a standard was accepted. + + + + + + + + + + Basic data types for date parts. + + + + + + + + + + + + + + + + + + + + + + + + + + The container for information about page ranges. + + + + + + + + + + + + + Identifies books or conference proceedings that have no ISBN assigned. + + + + + + + + + + + + + + + + The coden assigned to a journal or conference proceedings. + + + + + + + + + + + A container for item identification numbers set by a publisher. + + + + + + + + + + + + + + + + + A publisher-assigned number that uniquely identifies the item being registered. + + + + + + + + + + + + + + + + + + A public standard identifier that can be used to uniquely identify the item being registered. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + A container for information about the publisher of the item being registered + + + + + + + + + + + + + + publisher_place gives the primary city location of the publisher. If the city is not a major city, the appropriate country, state, or province should be added. + + + + + + + + + + + The name of the publisher of a book or conference proceedings. This name may differ from that of the organization registering or maintaining the metadata record. + + + + + + + + + + + + A narrative description of a file (e.g. a figure caption or video description). + + + + + + + + + + + + + + + + + + + + + A narrative description of a component's file format and/or file extension. + + + + + + + + + + + + Container element for archive information + + + + + + + + + + Used to indicate the designated archiving organization(s) for an item. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/tests/xsd/scielo_crossref/fundingdata5.5.0.xsd b/tests/xsd/scielo_crossref/fundingdata5.5.0.xsd new file mode 100644 index 0000000..31346e4 --- /dev/null +++ b/tests/xsd/scielo_crossref/fundingdata5.5.0.xsd @@ -0,0 +1,62 @@ + + + + + + + + Information about registering funding data is available in our documentation: https://www.crossref.org/documentation/funder-registry/funding-data-deposits/ + + + + + + + + + + + Funding data attributes included in assertion are: + * fundgroup: used to group funding metadata for items with multiple funding sources. Required for items with multiple award_number assertions, optional for items with a single award_number + * funder_identifier: funding agency identifier + * ror: ROR ID of a funder + * funder_name: name of the funding agency + * award_number: grant number or other fund identifier + * grant_doi: awards or grants registered as grant IDs (DOIs) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/tests/xsd/scielo_crossref/fundref.xsd b/tests/xsd/scielo_crossref/fundref.xsd index 1b2b58e..030e9cb 100644 --- a/tests/xsd/scielo_crossref/fundref.xsd +++ b/tests/xsd/scielo_crossref/fundref.xsd @@ -4,35 +4,14 @@ xmlns="http://www.crossref.org/fundref.xsd"> - - - FundRef documentation and examples: http://help.crossref.org/#fundref - - As part of CrossMark metadata, a deposit may contain what is called FundRef info. This details the funding behind a published article. The schema is a sequence of nested <assertion> tags. - - If a DOI is not participating in CrossMark, FundRef data may be deposited as part of the <journal_article> metadata. - - Note: Some rules will be enforced by the deposit logic (e.g. not the schema). - - FundRef data includes one or more award numbers (award_number), each of which may have one or more funders (funder_name). Each funder may have one or more optional identifiers (funder_identifier). - - A FundRef deposit begins with a <fr:program> tag within the <crossmark> structure (where fr is the namespace for the FundRef program). - - The <program> element is an implicit funder_group and will typically contain: - - A) one or more funder_name assertions and an award_number assertion. - - or - - B) one or more funder_group assertions where each funder_group should contain one or more funder_name assertions and at least one award_number assertion. - - Multiple 'award_number's may be included in a single program or fundgroup. Deposits without an award_number will be accepted, but award_number should be provided whenever possible. Items with several award numbers associated with a single funding organization should be grouped together by enclosing the "funder_name", "funder_identifier", and award_number(s) within a "fundgroup" assertion. - + Information about registering funding data is available in our documentation: https://www.crossref.org/documentation/funder-registry/funding-data-deposits/ @@ -43,15 +22,14 @@ - FundRef attributes included in assertion are: - -fundgroup: used to group funding info for items with multiple funding sources. Required for items with multiple award_number assertions, optional for items with a single award_number - -funder_identifier: funding agency identifier, must be nested within the funder_name assertion - -funder_name: name of the funding agency (required) - -award_number: grant number or other fund identifier + Funding data attributes included in assertion are: + * fundgroup: used to group funding metadata for items with multiple funding sources. Required for items with multiple award_number assertions, optional for items with a single award_number + * funder_identifier: funding agency identifier + * ror: ROR ID of a funder + * funder_name: name of the funding agency + * award_number: grant number or other fund identifier + * grant_doi: awards or grants registered as grant IDs (DOIs) + @@ -59,24 +37,21 @@ award_number: grant number or other fund identifier - - - - + + + + - - + - - + diff --git a/tests/xsd/scielo_crossref/languages5.5.0.xsd b/tests/xsd/scielo_crossref/languages5.5.0.xsd new file mode 100644 index 0000000..95a0626 --- /dev/null +++ b/tests/xsd/scielo_crossref/languages5.5.0.xsd @@ -0,0 +1,8123 @@ + + + 2 and 3 character language codes taken from ISO 639-1 and ISO 639-3 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/tests/xsd/scielo_crossref/mediatypes5.5.0.xsd b/tests/xsd/scielo_crossref/mediatypes5.5.0.xsd new file mode 100644 index 0000000..67daae8 --- /dev/null +++ b/tests/xsd/scielo_crossref/mediatypes5.5.0.xsd @@ -0,0 +1,2211 @@ + + + + + Media / mime types for component format. Based on https://www.iana.org media types. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/tests/xsd/scielo_crossref/relations.xsd b/tests/xsd/scielo_crossref/relations.xsd index c5891af..5676dda 100644 --- a/tests/xsd/scielo_crossref/relations.xsd +++ b/tests/xsd/scielo_crossref/relations.xsd @@ -2,52 +2,24 @@ - - 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 - - ====== 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. + + + + + + This schema provides for creating relationships between items identified by Crossref DOIs, non-Crossref DOIs, and other identifiers. See: https://support.crossref.org/hc/en-us/articles/214357426 - + - Accommodates deposit of relationship claims between items. + Wrapper element for relationship metadata @@ -83,7 +55,7 @@ - + @@ -115,6 +87,9 @@ + + + @@ -127,9 +102,7 @@ - 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. + Used to define relations between items that are essentially the same work but may differ in some way that impacts citation, for example a difference in format, language, or revision. 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. @@ -184,7 +157,8 @@ - + + @@ -203,5 +177,250 @@ + + + + + A narrative description of the relationship target item + + + + + + + + + + + + + + + + + Basic data types for face markup in the target related item + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Language attributes are based on ISO 639 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +