$Rev: 14336 $ BWmeta is a general-purpose metadata format capable of describing entities such as: academic articles, books, audio recordings, laws, or molecular sequences. A distinguishing feature of BWmeta is non-redundant, hierarchical storage of information. For example, metadata for an article is typically distributed across four records: one for the article, one for the issue in which the article was published, one for the volume, and one for the journal. The root tag of any BWmeta document is <bwmeta/>, which may contain any number of top-level objects (<person/>, <element/>, <license/>, etc.). BWmeta is a flexible format: there are no enumerations of accepted values (most notably in various "type" attributes). Instead, data providers are encouraged to define their own vocabularies. This is type defined for rich text. It would be used in more then one element so it coud be better to take it to separate type. Contributors' affiliation. Contains an identifier (see: id attribute) that may be referenced by one or more <affiliation-ref/> tags. Presentational form is stored in <text/>. The optional <identity/> child tag references an institution (see: <institution/> tag). Affiliation identifier. Referenced by <affiliation-ref/>. Reference to an affiliation. Identifier of an affiliation. Ancestor element in element structure. Level on which the ancestor is located. Reference to the ancestor element. Position within the level. A tree-like structure with a key-value pair in each node. May be used to hold information that does not map well to other tags. Attribute's key. Root of any BWmeta document. Top-level objects, such as persons or elements, are direct descendants. Category within a classification. Contains code, name and description of the category, as well as code of the parent category (if applicable). Identifier of the classification to which the category belongs. Code of the category. Examples: 83A05, 03.30.+p. The parent category's code. If present, both the category and its parent must belong to the same classification. Reference to a given category. Identifier of the classification containing the referenced category. Code of the referenced category. Classification or taxonomy, a hierarchical structure of categories. Notable examples include subject classifications, such as: MSC or PACS. Files and directories containing the element. A person or institution that contributed to this element. Whether the contributor is an institution or a person. This is a boolean field. Value "true" indicates an institution, "false" indicates a person. Contributor's role. Examples: author, editor, translator. Current element in element structure. Current element's level. Current element's relative position within this level. Date of an event associated with a given element. The text present in tag's body contains a presentational form of the date, while year, month and day attributes contain the actual (parsed) date. Lack of day (or day and month) attribute(s) should be interpreted as a date specified with a coarser granularity. For example: <date type="published" year="1809" month="9">September 1809</date> should be interpreted as indication of a month. Day. Month. If not present, day should not be present either. Type of date. Examples: accepted, published, received. Year. If absent, day and month should be absent as well. Multi-line description of an object. Language in which the description is written. Only ISO 639-1 and 639-2 language codes are allowed. Type of the description. Examples: abstract, comment, summary. Directory containing files and other directories. It provides a logical, hierarchical structure of files. Directory identifier. List of languages of this content. Only ISO 639-1 and 639-2 language codes are allowed. Type of content. Examples: pages. Element describes a document, or in the case of compound documents, an atomic part of it. For example — in the case of academic articles in journals — the article, the issue containing it, the volume and the journal, are each respresented by a separate element. Description of a file containing the element or part of it. File is understood as a fixed array of bytes that can be stored in one or more locations. MIME format of the file. File identifier. List of languages of this content. Only ISO 639-1 and 639-2 language codes are allowed. Size of the file in bytes. Type of content. Examples: cover, full-text, plain-text, thumbnail. Format of identifiers in a given <id-scheme/> as a regular expression. Hierarchy defines a logical organization of content in various types of compound documents. Examples: journal-volume-issue-article, series-book-chapter, album-disc-track. See <level/> for more details. Element identifier in a given scheme (such as: DOI, ISBN). Identifier of the scheme (refers to <id-scheme/>). Element identifier within a given scheme. Reference to an object (<person/>, <institution/>) that matches a given textual representation. Provides a semantics to what is otherwise a presentational form of an object. For example, <contributor/> within <element/> may list a John Smith as an author and <identity/> may link this name to an actual <person/>. Identifier of the referenced object. Describes a standard of identifing documents. Serves as a kind of identifier namespace. Examples of identifier schemes: DOI, ISBN, ISSN, PMID. Information on an institution. Parent institution. Language of an element. ISO 639-1 or ISO 639-2 language code. Level within a given hierarchy describes an element type. Examples: journal, journal volume, journal issue, article in a journal, book series, book in a series, chapter in a book, music album, disc in an album, track on a disc. Levels are grouped into hierarchies. Identifier of the hierarchy in which the given level is located. Example: journal issue is located in the journal-volume-issue-article hierarchy. Identifier of the parent level. Example: journal volume is the parent of journal issue. Description of a license. License of a given element (refers to <license/>). Identifier of the license on which a given element is distributed. URL describing location of a given file. One-line name of an object. Language in which the name is written. Only ISO 639-1 and 639-2 language codes are allowed. Key to be used in collation. Type of the name. Examples: abbreviation, romanization, subtitle, surname, title. Information on a person. Relation between the given element and some other element. Identifier scheme. Identifier of the other element withing the given identifier scheme. Type of relation. Examples: references, updates. Checksum of a binary file. Checksum type. Examples (non-normative): SHA1, MD5. Structure provides links to upper-level elements according to a given hierarchy. Hierarchy of this structure. A single tag within a set of tags. See <tags/>. A set of tags describing the given element. Language of the tags. Only ISO 639-1 and 639-2 language codes are allowed. Tag type. Examples: genre, keyword, subject. Text of an affiliation. This is a presentational form of the affiliation, as in the described document. Object identifier. Object version. Primary identifier of entities in the model. Each exportable entity contains a unique extId. List of languages. Version information as well as 'deleted' or 'merged' flag. Version regexp: [0-9]+(D|M(.+))?. 'D' stands for deleted, 'M' for merged and everything after letter 'M' is id of object to which this object should be merged.