Public:BWMeta format/BWMeta model
From YaddaWiki
(→element) |
(→element) |
||
| Line 13: | Line 13: | ||
For example — in the case of academic articles in journals — the article, the issue containing it, the volume and the journal, are each represented by a separate element. | For example — in the case of academic articles in journals — the article, the issue containing it, the volume and the journal, are each represented by a separate element. | ||
In element information is described using following other xml elements: | In element information is described using following other xml elements: | ||
| - | + | ||
| - | + | * affiliation | |
| - | + | * attribute | |
| - | + | * category-ref | |
| - | + | * contents | |
| - | + | * contributor | |
| - | + | * date | |
| - | + | * description | |
| - | + | * id | |
| - | + | * language | |
| - | + | * license-ref | |
| - | + | * name | |
| - | + | * relation | |
| - | + | * structure | |
| + | * tags | ||
==person== | ==person== | ||
Revision as of 13:55, 16 April 2012
| Service details | |
|---|---|
| Name | BWmeta |
| Code location (relative to SVN root) | projects/dir/bwmeta-core |
| Javadoc | |
| Contact person | Jakub Jurkiewicz |
On this page toplevel elements of bwmeta are presented. (Actually only bwmeta is only root element for xmls, but it is a container for other elements).
Contents |
bwmeta
Root of any BWmeta document. Top-level objects, such as persons or elements, are direct descendants. It could contain more then one such elemnt to avoid big number of small files.
Data elements
This elemnts comes from publishers, or are generated using automatic technics. They contain information about data - information that changes.
element
Element describes a thing that has been published, 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 represented by a separate element. In element information is described using following other xml elements:
- affiliation
- attribute
- category-ref
- contents
- contributor
- date
- description
- id
- language
- license-ref
- name
- relation
- structure
- tags
person
Information on a identified person. When one person is connected to more then one articles this means that this articles has been written by the same person. When two articles are connected to different person then this articles has been not written by the same person. It very important to consider that before adding person elements. Information about person taht has written article could be also contained by contributor elemnt in article
institution
Information on an institution.
knowledge elements
This elemnts has been created usually by CEON team - they are not coming with data, but they are used to describe data. They reduces number of information that has to be hardcoded into system or in configuration.
hierarchy
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.
level
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.
classification
Classification or taxonomy, a hierarchical structure of categories. Notable examples include subject classifications, such as: MSC or PACS.
category
Category within a classification. Contains code, name and description of the category, as well as code of the parent category (if applicable).
id-scheme
Describes a standard of identifing documents. Serves as a kind of identifier namespace. Examples of identifier schemes: DOI, ISBN, ISSN, PMID.
license
Description of a license - deprecated
