]> input schema for the reference database (refdb) component of the ePublishingToolkit. this schema will be publicly available from the schema location &epubtkNS;&importNS;.xsd the schema is split in three schema documents. the first one (this one) defines the fixed components which need to be kept for compatibility with the database structure. the other two schema documents can be created dynamically from a reference database to validate keywords and journal names against controlled lists of values. the static (publicly available) schema documents do not provide for this kind of checking. the main schema document is also used by import filter applications to infer the metadata model. to allow for this, the following interfaces need to be provided: 1) the genre-types have to be declared as 'xsd:element' children (having the genre-name as value of their 'ref' attribute) of a 'xsd:group' with 'name' attribute set to 'genre'. 2) fields have to be declared as xsd:element with a 'name' attribute and an 'id' attribute with a unique value of the format 'field-*' where * is an integer number. the order imposed on the bibData items in records is given by the element's 'id'-attribute. note: the format of the id-value needs to correspond to the parser! 3) if a field requires non-default processing, it must provide information in a 'epubtk' child of its 'xsd:appinfo' child. note: a field of type complexTex should be specified with 'keepTex' set to 'true'. additional information for the bibtex import filter may be provided in a 'bibtex' child of the 'epubtk' element. the following attributes are recognized: - 'field': specifies the bibtex-field name, the value of which should be mapped to the xml-field. - 'separatorPattern': can be used to specify a patter used to split the bibtex value, if it is mapped to a repeatable field. note: the field of dataType 'author' is treated completely different; and it must be taken care, to declare exactly one field with this dataType! bibliographical records are imported as lists of references the main structure 'record' may contain one of the genre elements defined in one of the included schema documents. genre elements themselves contain various bibData elements. the attribute 'id' is used to store the citation key. a group with name "genre" has to be provided by one of the included schema documents. the attribute 'ord' is used to store the order of records within the reference list. the 'genre' group is the container for the different entry types in the reference database. note: this group implements the required interface between the schema's main document and the definition of bibliographic records. this type implements a required interface to the schema's main document. the pattern matches 'Living Reviews in Relativity'-type article identifiers. notes: 1) imposing an order on the elements in the content of records is somewhat artificial. we do it to make the schema less complex and because of the non-standard implementation of the 'xsd:all' element in the schema validator we want to use. once the validator handles the 'xsd:all' element correctly, all bibData elements which can occur only at most once may be grouped within an 'xsd:all' element to allow their appearance in any order. but as complying schema instances are assumed to be created automatically this order is just a question of implementation in the import filter applications. 2) the "format" bibData-element specifies a category within a genre. its valid values are defined per genre. depending on the genre, the categorisation by 'format' may be based on different criteria; hence may have to be mapped to different dc-elements. Article published in a journal, magazine. Includes also article published in e-journal. article inejournal categorisation by media of dissemination Book, including an edited book. book categorisation by media of dissemination; Specific chapter of book (which is not a collection of articles). inbook categorisation by media of dissemination Part of collection (complete collection however cited as book) inbook categorisation by media of dissemination Paper published in conference proceedings. inproceedings categorisation by media of dissemination Catchall category, including e.g. Private communication, but also CD-ROMs, etc., if online version is availabe - genre online. misc categorisation as appropriate ('catchall' genre!) Resources available online: entire www, ftp or gopher site, animations, and computer software. Does not include articles published on preprint server -> extra genre, does not include articles published in e journals - those are articles. online lr_url categorisation by type of serving web site; maps to dc:type article available on preprint server, not yet published online categorisation by preprint server Conference proceedings. proceedings categorisation by media of dissemination; maps to dc:format Technical reports or working papers (if part of a series with an ISSN, they are regarded as journal articles). techreport categorisation by media of dissemination dissertation written to obtain a degree mastersthesis phdthesis categorisation by corresponding degree Print articles not formally published. Includes conference papers, articles in preparation, or submitted for publication, or accepted for publication. Does not include articles ot this kind that are already published on preprint server or are elsewhere available online. unpublished categorisation by status of publication process article published in (possibly the online version of) a newspaper categorisation by media of dissemination the single bibData items are defined independent of the genres - although some may be used exclusively for one genre. bibData elements may have the following attributes: @tex (xsd:string): attribute to store tex-source of element content. @scope (scopeType): used to distinguish general bibliographic data from citation-context specific data. @dataType (dataTypeType): controls how the data will be interpreted. grouping is used to model exclusive-or relations between different bibData elements. due to the global order we impose on the fields, a group is restricted to neighbouring fields (with respect to the genre). name of a person, 'et al.', or name of (Collaboration). author names follow the pattern: (lastname),+[(\s+(initial)\.)+[\-(initial)\.]] examples: Forkel, R. Forkel, R.-R. field for (in)proceedings to provide additional data about the conference they are related to. note: journalType will be defined in the dynamically created schema document journals.xsd field to store identifiers (which cannot be described in the traditional, i.e. print-related way by pages, volume, etc.) url for online resources note: see also onlineversion! url which points to a related online resource for a non-online reference specifies the date at which a cited online-resource was accessed by the author citing it. to store information about a related published version of a preprint note: keywordType will be defined in the dynamically created schema document keywords.xsd the actual format elements need to be defined per genre, because their valid values vary. the declaration here is to provide documentation and application info! dc:subject a digital object identifier preprint id of e.g. arXiv ADS record url ISI identifier archive identifier arXiv identifier google books identifier total number of pages additional field for team of authors or project group complex text plus tex- and dataType-attribute A chapter (or section or whatever) identifier. A volume identifier. The number of a journal, magazine, or of a work in a series. An issue of a journal or magazine is usually identified by its volume and number; and sometimes books are given numbers in a named series. Name(s) of editor(s), typed as indicated in the LaTeX book. If there is also an author field, then the editor field gives the editor of the book or collection in which the reference appears. One or more page numbers or range of numbers, such as 42-111 or 7,41,73-97 or 43+ (the `+' in this last example indicates pages following that don't form a simple range). The year of publication or, for an unpublished work, the year it was written. Generally it should consist of four numerals, such as 1984. Although the standard styles can handle any year whose last four nonpunctuation characters are numerals, such as `(about 1984)', it is decided here to keep the year limited to four numerals, as such a type is pre-defined in XML Schema. type only used with author element type for bibData element content. this type of mixed content corresponds to refdb's extended unicode strings