Home  
  Model Schemas
     - BrainMetaL base
     - BrainML base
     - Protocols
  Validation
  Purpose
     - Usage
     - FAQ
  Architecture
     - Components
     - Specification
  Extensions
     - Protocols
  About this Site
     - How to Query
     - How to Submit
  Contributors
  Workshops
  Links
 
User ID
Password


  View Structure:



Model BrainMetaL
Submitter LNI Account
Version Version 1 (2004/09/17)
Namespace urn:bml/brainml.org:internal/BrainMetaL/1
Comments Initial version.
View Structure   Vocabulary   (with IDs)

Composite Model

This model contains multiple submodels (defined in separate XML schemas):

  1. brainmetal
  2. units
  3. relations
  4. vocabulary
  5. citation

BrainML Model: "brainmetal"

This is a tabular description of the entities and fields making up the "brainmetal" data model. Regular expression notation is used to indicate quantities -- i.e., '?' following a term means 0 or 1 occurrence, '*' means 0 or more occurrences, '+' means 1 or more occurrences, and no following character means exactly 1 occurrence. Fields with names in (parentheses) are attributes in the XML; all others are subelements with text content. The term "ANY" under 'Contains:' means an element can contain any other element as content. This description is also available in XML format.

This schema specifies top-level elements that BrainML elements should inherit from, and utility elements to be used by BrainML schemas and/or instance documents. Included are: - the Quintessence elements, abstract top-level data "classes" - a 'link' element for linking between quintessence elements, both within and between documents, and for referencing external resources such as journal article PDFs - a 'unit' element which supports reference to unit definitions defined in instance documents conforming to the "units" schema - a 'vocab' element which supports reference to term declarations in instance documents conforming to the "vocabulary" schema - utility complex data type elements - [temporary] elements defining the structure of a data submission, so that instance documents can be validated directly against this.. these will be moved to one or more "brainml" schemas defining document types for exchange

Depends on models: (none)
Index of Entities


datasetSuperclass for different dataset formats.
container: labeled_dataset, data_documentcontains: ANY
inherits: (none)links: (none)
Return to top


labeled_datasetConsists of two datasets. The first contains the values, the second, which should have exactly the same dimensions, contains the labels (as strings).
container: data_documentcontains: dataset+, datasetB+, datasetC+, datasetR+, datasetX+
inherits: (none)links: (none)
Return to top


datasetBData container: Base-64 encoded binary, in which values are encoded in IEEE standard, network byte order. Rectangular multi-dimensional data is given as a linear array as in the whitespace/comma-separated case.
container: datasetX, labeled_dataset, data_documentcontains: (none)
inherits: datasetlinks: (none)
FieldTypeDescription
(dimensions)tokenDescribes the dimensions of the dataset, as a space-separated list consisting of numbers or "*". Each number indicates the number of values the dataset contains on a dimension. Thus, a one-dimensional dataset such as a time series will have just one number -- the length of the time series. A two-dimensional dataset such as a grid of values has two numbers -- the sizes of the X and Y axes of the grid. Alternatively, two numbers may be used to indicate a number of tuples and the length of each tuple. (Containing element should specify which usage is valid.) For example, "* 2" indicates a list of ordered pairs. Non-rectangular or unknown length data is accomodated through use of the special '*' value. A list of five time series, each of a different length, would have dimensions "5 *". Each individual time series entry contained under this would have its own dimensions entry of a single number giving its length.
(type)tokenThe data type of this data set. Valid values are integer, decimal, and string. Integer and decimal types can be of arbitrary size and precision, however BrainML applications MAY process these as 4-byte signed integers, and 8-byte IEEE doubles respectively. Strings are in whatever encoding the XML document itself declares.
Return to top


datasetCData container: Whitespace- or comma-separated values contained under a single XML tag. Rectangular multi-dimensional data is given as a linear array which must be stepped through by the application.
container: datasetX, labeled_dataset, data_documentcontains: (none)
inherits: datasetlinks: (none)
FieldTypeDescription
(delimiter)?short textCharacter(s) used to delimit individual data values.
(group)?short textCharacters used to delimit dimensional groups in the dataset. The left and right delimiters should be given, as in "()". Group delimiters are required to express multi-dimensional nonrectangular datasets. For example, an integer dataset with dimensions "2 *" might be expressed as '(23,25,29) (25,26)'.
(dimensions)tokenDescribes the dimensions of the dataset, as a space-separated list consisting of numbers or "*". Each number indicates the number of values the dataset contains on a dimension. Thus, a one-dimensional dataset such as a time series will have just one number -- the length of the time series. A two-dimensional dataset such as a grid of values has two numbers -- the sizes of the X and Y axes of the grid. Alternatively, two numbers may be used to indicate a number of tuples and the length of each tuple. (Containing element should specify which usage is valid.) For example, "* 2" indicates a list of ordered pairs. Non-rectangular or unknown length data is accomodated through use of the special '*' value. A list of five time series, each of a different length, would have dimensions "5 *". Each individual time series entry contained under this would have its own dimensions entry of a single number giving its length.
(type)tokenThe data type of this data set. Valid values are integer, decimal, and string. Integer and decimal types can be of arbitrary size and precision, however BrainML applications MAY process these as 4-byte signed integers, and 8-byte IEEE doubles respectively. Strings are in whatever encoding the XML document itself declares.
Return to top


datasetRData reference: a reference to external data. The contents of this element should be a URI pointing to the data. The 'formatType' and 'formatRef' attributes should describe the data format and the optional 'info' attribute can be used for application- or format-specific information.
container: datasetX, labeled_dataset, data_documentcontains: (none)
inherits: datasetlinks: (none)
FieldTypeDescription
(dimensions)tokenDescribes the dimensions of the dataset, as a space-separated list consisting of numbers or "*". Each number indicates the number of values the dataset contains on a dimension. Thus, a one-dimensional dataset such as a time series will have just one number -- the length of the time series. A two-dimensional dataset such as a grid of values has two numbers -- the sizes of the X and Y axes of the grid. Alternatively, two numbers may be used to indicate a number of tuples and the length of each tuple. (Containing element should specify which usage is valid.) For example, "* 2" indicates a list of ordered pairs. Non-rectangular or unknown length data is accomodated through use of the special '*' value. A list of five time series, each of a different length, would have dimensions "5 *". Each individual time series entry contained under this would have its own dimensions entry of a single number giving its length.
(type)tokenThe data type of this data set. Valid values are integer, decimal, and string. Integer and decimal types can be of arbitrary size and precision, however BrainML applications MAY process these as 4-byte signed integers, and 8-byte IEEE doubles respectively. Strings are in whatever encoding the XML document itself declares.
(formatType)short textA short string describing the format of the referenced unit. This could be a MIME string if such exists for this data type.
(formatRef)uriA URL to a specification or description of the format of the referenced unit.
(info)?long textAny required additional information describing this file or its relation to others in this dataset may go here.
Return to top


datasetXData container: Full XML format, where every data value is contained in its own tag, and dimensional structure is reflected in tag containment.
container: datasetX, labeled_dataset, data_documentcontains: datasetX*, datasetC*, datasetB*, datasetR*
inherits: datasetlinks: (none)
FieldTypeDescription
(dimensions)tokenDescribes the dimensions of the dataset, as a space-separated list consisting of numbers or "*". Each number indicates the number of values the dataset contains on a dimension. Thus, a one-dimensional dataset such as a time series will have just one number -- the length of the time series. A two-dimensional dataset such as a grid of values has two numbers -- the sizes of the X and Y axes of the grid. Alternatively, two numbers may be used to indicate a number of tuples and the length of each tuple. (Containing element should specify which usage is valid.) For example, "* 2" indicates a list of ordered pairs. Non-rectangular or unknown length data is accomodated through use of the special '*' value. A list of five time series, each of a different length, would have dimensions "5 *". Each individual time series entry contained under this would have its own dimensions entry of a single number giving its length.
(type)tokenThe data type of this data set. Valid values are integer, decimal, and string. Integer and decimal types can be of arbitrary size and precision, however BrainML applications MAY process these as 4-byte signed integers, and 8-byte IEEE doubles respectively. Strings are in whatever encoding the XML document itself declares.
datum*tokenA single data point, possibly multi-dimensional.
Return to top


reference_elementQuintessence element. These simply allow an unlimited content model beneath them, but explicitly declare some optional contents so that BrainML applications know to expect them. Reference element for bibliographic and other references to external material.
container: (none)contains: link*
inherits: (none)links: (none)
FieldTypeDescription
(id)?tokenThis attribute is needed so that others may link to it.
(base)?uriSee http://www.w3.org/TR/xmlbase/ for information about this attribute.
Return to top


linkGeneric element for linking to another element within the same or another document. The href attribute should be of form #id, where 'id' is an XML ID in the current document (no whitespace, cannot start with number). This will be resolved relative to the local value of xml:base (see http://www.w3.org/TR/xmlbase/). To ensure a local reference when there might be an externally-referencing xml:base value in the context, set xml:base="" within the link.
container: reference_element, method_element, model_element, entity_element, data_element, collectioncontains: (none)
inherits: (none)links: (none)
FieldTypeDescription
(base)?uriSee http://www.w3.org/TR/xmlbase/ for information about this attribute.
(href)uriReference to linked resource; should be a URL or URN.
(role)?uriShould be a URL referring to a relation defined in a file conforming to "relations.xsd".
(dest)?uriIf this is a link to another BrainML element (not an external resource), the definition of this element is given here, in the form URI,element, as in "urn:bml/brainml.org:internal/BrainML/1,experiment".
Return to top


method_elementQuintessence element. These simply allow an unlimited content model beneath them, but explicitly declare some optional contents so that BrainML applications know to expect them. Method element for methods, techniques, procedures, analytical algorithms.
container: (none)contains: link*
inherits: (none)links: (none)
FieldTypeDescription
(id)?tokenThis attribute is needed so that others may link to it.
(base)?uriSee http://www.w3.org/TR/xmlbase/ for information about this attribute.
Return to top


unitElement for referencing predefined units. (Defined in documents conforming to units.xsd. You should subclass / substitute this element to define your own semantics. (See examples.)
container: (none)contains: (none)
inherits: (none)links: (none)
FieldTypeDescription
(name)?token(Optional) Name of the unit (excluding hierarchical context).
(href)uriReference to linked resource; should be a URL or URN.
Return to top


vocabType for referencing predefined vocabulary terms.
container: (none)contains: (none)
inherits: (none)links: (none)
FieldTypeDescription
(domain)?tokenDomain of applicability for the term (including hierarchical context).
(term)?tokenName of the term (including hierarchical context).
(href)uriReference to linked resource; should be a URL or URN.
Return to top


data_documentTop-level element for a stand-alone document containing a dataset.
container: (none)contains: dataset*, labeled_dataset*, datasetC*, datasetR*, datasetX*, datasetB*
inherits: (none)links: (none)
Return to top


model_elementQuintessence element. These simply allow an unlimited content model beneath them, but explicitly declare some optional contents so that BrainML applications know to expect them. Model element for theories, hypotheses.
container: (none)contains: link*
inherits: (none)links: (none)
FieldTypeDescription
(id)?tokenThis attribute is needed so that others may link to it.
(base)?uriSee http://www.w3.org/TR/xmlbase/ for information about this attribute.
Return to top


entity_elementQuintessence element. These simply allow an unlimited content model beneath them, but explicitly declare some optional contents so that BrainML applications know to expect them. Entity element for recording sites, chemical substances, genes, anything that has a physical existence.
container: (none)contains: link*
inherits: (none)links: (none)
FieldTypeDescription
(id)?tokenThis attribute is needed so that others may link to it.
(base)?uriSee http://www.w3.org/TR/xmlbase/ for information about this attribute.
Return to top


data_elementQuintessence element. These simply allow an unlimited content model beneath them, but explicitly declare some optional contents so that BrainML applications know to expect them. Data element for numerical data and container structures, including entire submission.
container: (none)contains: link*
inherits: (none)links: (none)
FieldTypeDescription
(id)?tokenThis attribute is needed so that others may link to it.
(base)?uriSee http://www.w3.org/TR/xmlbase/ for information about this attribute.
Return to top


collectionDesignates a collection of BrainML elements, identified by links, which may themselves go to collections. More precisely, this element consists of a list of zero or more links to other collections, followed by a list of zero or more links to non-collection items. An empty collection is legal. The order of the links may be ignored by the processing application unless the attribute 'ordered' is set to "true". This element can be extended to add any metadata for describing the collection that is needed.
container: (none)contains: link*
inherits: (none)links: collection
FieldTypeDescription
(id)token
(name)?tokenOptional name for the collection.
(ordered)?booleanOrder of contents may be ignored unless present and set to "true".
Return to top


BrainML Model: "units"

This is a tabular description of the entities and fields making up the "units" data model. Regular expression notation is used to indicate quantities -- i.e., '?' following a term means 0 or 1 occurrence, '*' means 0 or more occurrences, '+' means 1 or more occurrences, and no following character means exactly 1 occurrence. Fields with names in (parentheses) are attributes in the XML; all others are subelements with text content. The term "ANY" under 'Contains:' means an element can contain any other element as content. This description is also available in XML format.

This schema specifies the format for unit definitions. Definitions occur in special-purpose documents containing nothing else, that are made accessible on the internet. BrainML instance documents may refer to these by use of a 'unit' element that is defined in the main brainml schema. They may NOT define units themselves. If a unit needs to be added, a schema authority should submit a unit definitions document to the schema repository.

Depends on models: (none)
Index of Entities


external-equivalentSupports linking of a unit declaration to a corresponding term or definition in an external system.
container: unit-definitioncontains: (none)
inherits: (none)links: (none)
FieldTypeDescription
(href)uriReference to linked resource; should be a URL or URN.
Return to top


unit-definitionSingle unit definition. This could be used outside of a special-purpose unit-definition document if desired.
container: unit-definitionscontains: name, external-equivalent?
inherits: (none)links: (none)
FieldTypeDescription
(id)tokenThis is the identifier by which the unit will be referenced. Valid characters in identifiers are ONLY letters, numbers, underscore, period, and dash, and an identifier cannot start with a number. The identifier for a domain should be unique within its containing document among both domains and terms.
classtokenQuantity measured by unit. E.g., "electric-potential".
symbolshort textSymbol used for unit. E.g., "kg".
Return to top


nameName of a unit (composite).
container: unit-definitioncontains: (none)
inherits: (none)links: (none)
FieldTypeDescription
base-nametokenStem of unit name (e.g., "gram", "meter").
prefix?tokenPower-of-ten prefix (e.g., "kilo", "centi").
Return to top


unit-definitionsCollection of unit definitions, and valid unit definition document root.
container: (none)contains: unit-definition+
inherits: (none)links: (none)
Return to top


BrainML Model: "relations"

This is a tabular description of the entities and fields making up the "relations" data model. Regular expression notation is used to indicate quantities -- i.e., '?' following a term means 0 or 1 occurrence, '*' means 0 or more occurrences, '+' means 1 or more occurrences, and no following character means exactly 1 occurrence. Fields with names in (parentheses) are attributes in the XML; all others are subelements with text content. The term "ANY" under 'Contains:' means an element can contain any other element as content. This description is also available in XML format.

This schema specifies the format for lists of allowable relations. Lists occur in special-purpose documents containing nothing else, that are made accessible on the internet. BrainML links documents may refer to these by use of an 'xlink:role' attribute that is defined in the main brainmetal schema. They may NOT define relations themselves. If terms need to be added, a schema authority should submit a relation definitions document to the schema repository. Relation definitions are a bit simpler than term definitions -- there is no domain, and hierarchy is available but not often used.

Depends on models: (none)
Index of Entities


relationA 'relation' is an atomic descriptor that exists in an ISA hierarchy and is associated with a particular domain of applicability. One or more 'external-equivalent' children may exist to link the term to equivalents in non-BrainML systems, such as the UMLS.
container: relation, relationscontains: internal-equivalent*, external-equivalent*, relation*
inherits: (none)links: (none)
FieldTypeDescription
(id)tokenThis is the identifier by which the relation will be referenced. Valid characters in identifiers are ONLY letters, numbers, underscore, period, and dash, and an identifier cannot start with a number. The identifier for a relation should be unique within its containing document.
Return to top


internal-equivalentIt is not fully decided whether the ISA hierarchy is a tree or a DAG in which a relation may have multiple parents. In the latter case, the relation actually would occur in two or more different places in the XML element hierarchy with the same name but different IDs. One or more 'internal-equivalent' children is used to link each instance of the term to all the others. This approach is similar to that used in the HDF5 XML format to represent directed graphs. (see http://hdf.ncsa.uiuc.edu/HDF5/XML/design-notes.html)
container: relationcontains: (none)
inherits: (none)links: (none)
FieldTypeDescription
(href)uriReference to linked resource; should be a URL or URN.
Return to top


external-equivalentUsed to link a relation with an equivalent term or definition in another system, such as the UMLS. BrainML does not explicitly support structured term definition, but through linking to another system that does, existing semantic structure can be maintained when metadata is expressed in BrainML.
container: relationcontains: (none)
inherits: (none)links: (none)
FieldTypeDescription
(href)uriReference to linked resource; should be a URL or URN.
Return to top


relationsTop-level element for a relations vocabulary document.
container: (none)contains: relation+
inherits: (none)links: (none)
Return to top


BrainML Model: "vocabulary"

This is a tabular description of the entities and fields making up the "vocabulary" data model. Regular expression notation is used to indicate quantities -- i.e., '?' following a term means 0 or 1 occurrence, '*' means 0 or more occurrences, '+' means 1 or more occurrences, and no following character means exactly 1 occurrence. Fields with names in (parentheses) are attributes in the XML; all others are subelements with text content. The term "ANY" under 'Contains:' means an element can contain any other element as content. This description is also available in XML format.

This schema specifies the format for vocabulary lists. Lists occur in special-purpose documents containing nothing else, that are made accessible on the internet. BrainML instance documents may refer to these by use of a 'vocab' element that is defined in the main BrainMetaL schema. They may NOT define vocabulary themselves. If terms need to be added, a schema authority should submit a vocabulary definitions document to the schema repository.

Depends on models: (none)
Index of Entities


external-equivalentUsed to link a controlled vocabulary term with an equivalent term or definition in another system, such as the UMLS. BrainML does not explicitly support structured term definition, but through linking to another system that does, existing semantic structure can be maintained when metadata is expressed in BrainML.
container: domain, termcontains: (none)
inherits: (none)links: (none)
FieldTypeDescription
(href)uriReference to linked resource; should be a URL or URN.
Return to top


internal-equivalentIt is not fully decided whether the ISA hierarchy is a tree or a DAG in which a term may have multiple parents. In the latter case, the term actually would occur in two or more different places in the XML element hierarchy with the same name but different IDs. One or more 'internal-equivalent' children is used to link each instance of the term to all the others. This approach is similar to that used in the HDF5 XML format to represent directed graphs. (see http://hdf.ncsa.uiuc.edu/HDF5/XML/design-notes.html)
container: termcontains: (none)
inherits: (none)links: (none)
FieldTypeDescription
(href)uriReference to linked resource; should be a URL or URN.
Return to top


lexiconThis is the top-level element for a document listing term declarations.
container: (none)contains: domain+
inherits: (none)links: (none)
Return to top


domainA 'domain' describes the content domain a term applies to. Domains may be nested to create subdomains, sub-subdomains, etc..
container: domain, lexiconcontains: external-equivalent*, term*, domain*
inherits: (none)links: (none)
FieldTypeDescription
(id)tokenThis is the identifier by which the domain will be referenced. Valid characters in identifiers are ONLY letters, numbers, underscore, period, and dash, and an identifier cannot start with a number. The identifier for a domain should be unique within its containing document among both domains and terms. By convention, this ID should be an underscore followed by a number beginning with 1,2,3, or 4. This should be added automatically by the VocabConverter tool, and if you are hand-editing a file just put "_".
(name)tokenThis is the simple name of the domain, without any hierarchy or context.
(description)?tokenDescription of the domain's meaning and intended usage. (Optional)
Return to top


termA 'term' is an atomic descriptor that exists in an ISA hierarchy and is associated with a particular domain of applicability.
container: term, domaincontains: internal-equivalent*, external-equivalent*, term*
inherits: (none)links: (none)
FieldTypeDescription
(id)tokenThis is the identifier by which the term will be referenced. Valid characters in identifiers are ONLY letters, numbers, underscore, period, and dash, and an identifier cannot start with a number. The identifier for a term should be unique within its containing document among both domains and terms. By convention, this ID should be an underscore followed by a number beginning with 5,6,7 or 8. This should be added automatically by the VocabConverter tool, and if you are hand-editing a file just put "_".
(name)tokenThis is the simple name of the term, without any hierarchy or context.
(description)?tokenDescription of the term's meaning and intended usage. (Optional)
Return to top


BrainML Model: "citation"

This is a tabular description of the entities and fields making up the "citation" data model. Regular expression notation is used to indicate quantities -- i.e., '?' following a term means 0 or 1 occurrence, '*' means 0 or more occurrences, '+' means 1 or more occurrences, and no following character means exactly 1 occurrence. Fields with names in (parentheses) are attributes in the XML; all others are subelements with text content. The term "ANY" under 'Contains:' means an element can contain any other element as content. This description is also available in XML format.

This schema specifies the format for citations, which come under the "reference" quintessence element. Two top-level citation tags are defined. The first is a BrainML-specific format, defining tags for journal articles, book chapters, and books. The second allows the use of external citation schemas such as bibtex-ml. It acts as a container for tags from these external schemas, but allows some standard tags from the BrainML format as well.

Depends on models: (none)
Index of Entities


citation_externalIf you wish to use an alternative XML syntax for expressing a bibliographic reference (e.g., Open URL, or BibTeXML), use this element as the container so that BrainML processors will recognize it as such.
container: citationscontains: link*; ANY
inherits: reference_elementlinks: (none)
FieldTypeDescription
(type)tokenDeclares the type of material being cited. Valid values are "article", "chapter", or "book".
(id)?tokenThis attribute is needed so that others may link to it.
(base)?uriSee http://www.w3.org/TR/xmlbase/ for information about this attribute.
Return to top


reference_elementQuintessence element. These simply allow an unlimited content model beneath them, but explicitly declare some optional contents so that BrainML applications know to expect them. Reference element for bibliographic and other references to external material.
container: (none)contains: link*
inherits: (none)links: (none)
FieldTypeDescription
(id)?tokenThis attribute is needed so that others may link to it.
(base)?uriSee http://www.w3.org/TR/xmlbase/ for information about this attribute.
Return to top


linkGeneric element for linking to another element within the same or another document. The href attribute should be of form #id, where 'id' is an XML ID in the current document (no whitespace, cannot start with number). This will be resolved relative to the local value of xml:base (see http://www.w3.org/TR/xmlbase/). To ensure a local reference when there might be an externally-referencing xml:base value in the context, set xml:base="" within the link.
container: reference_element, method_element, citation_external, author, citation, editor, person_full, model_element, entity_element, data_element, person, collectioncontains: (none)
inherits: (none)links: (none)
FieldTypeDescription
(base)?uriSee http://www.w3.org/TR/xmlbase/ for information about this attribute.
(href)uriReference to linked resource; should be a URL or URN.
(role)?uriShould be a URL referring to a relation defined in a file conforming to "relations.xsd".
(dest)?uriIf this is a link to another BrainML element (not an external resource), the definition of this element is given here, in the form URI,element, as in "urn:bml/brainml.org:internal/BrainML/1,experiment".
Return to top


authorAn author of a publication.
container: citationcontains: link*
inherits: entity_elementlinks: (none)
FieldTypeDescription
(id)?tokenThis attribute is needed so that others may link to it.
(base)?uriSee http://www.w3.org/TR/xmlbase/ for information about this attribute.
initials?short textInitials of name (use instead of first/middle).
first?short textFirst given name.
middle?short textSecond and subsequent given names.
prelast?short textPrefix such as "van" or "von der".
lastshort textSurname.
lineage?short textSuffixes such as "Jr.", "III".
email?short textEmail address.
phone?short textPhone number, including international dialing codes.
institution?short textInstitution or company where researcher works.
homepage?short textHome page of researcher, lab, or institution.
Return to top


entity_elementQuintessence element. These simply allow an unlimited content model beneath them, but explicitly declare some optional contents so that BrainML applications know to expect them. Entity element for recording sites, chemical substances, genes, anything that has a physical existence.
container: (none)contains: link*
inherits: (none)links: (none)
FieldTypeDescription
(id)?tokenThis attribute is needed so that others may link to it.
(base)?uriSee http://www.w3.org/TR/xmlbase/ for information about this attribute.
Return to top


citationRepresents a literature citation. Currently journal articles, book chapters and conference papers (BibTeX 'incollection'), and books are supported. Author, title, and year are required for all types, and pages is required for all but books. Journal articles additionally require journal (abbreviation is preferred), volume (volume only, no issue number). In-collection types require collection_title.
container: citationscontains: link*, author*, editor*
inherits: reference_elementlinks: author, editor
FieldTypeDescription
(type)tokenDeclares the type of material being cited. Valid values are "article", "chapter", or "book".
(id)?tokenThis attribute is needed so that others may link to it.
(base)?uriSee http://www.w3.org/TR/xmlbase/ for information about this attribute.
titleshort textTitle of work being cited (article, chapter, or book).
yearintegerYear of publication.
journal?short textJournal (abbreviation preferred) an article is published in.
volume?short textVolume of journal an article is published in.
pubmedID?integerPubMed numerical ID (PMID) of an article.
collection_title?short textTitle for book or proceedings volume an article is in.
pages?short textPage range of an article or chapter.
publisher?short textPublisher (not required for journals).
Return to top


editorAn editor of a publication.
container: citationcontains: link*
inherits: entity_elementlinks: (none)
FieldTypeDescription
(id)?tokenThis attribute is needed so that others may link to it.
(base)?uriSee http://www.w3.org/TR/xmlbase/ for information about this attribute.
initials?short textInitials of name (use instead of first/middle).
first?short textFirst given name.
middle?short textSecond and subsequent given names.
prelast?short textPrefix such as "van" or "von der".
lastshort textSurname.
lineage?short textSuffixes such as "Jr.", "III".
email?short textEmail address.
phone?short textPhone number, including international dialing codes.
institution?short textInstitution or company where researcher works.
homepage?short textHome page of researcher, lab, or institution.
Return to top


person_fullSame as person-content but make contact info mandatory. You can use this directly, or use the type person-type, or extend from it.
container: (none)contains: link*
inherits: personlinks: (none)
FieldTypeDescription
(id)?tokenThis attribute is needed so that others may link to it.
(base)?uriSee http://www.w3.org/TR/xmlbase/ for information about this attribute.
initials?short textInitials of name (use instead of first/middle).
first?short textFirst given name.
middle?short textSecond and subsequent given names.
prelast?short textPrefix such as "van" or "von der".
lastshort textSurname.
lineage?short textSuffixes such as "Jr.", "III".
emailshort textEmail address.
phoneshort textPhone number, including international dialing codes.
institutionshort textInstitution or company where researcher works.
homepage?short textHome page of researcher, lab, or institution.
Return to top


personAn entity element based on bibtexml 'person'. You can use this directly, or use the type person-type, or extend from it.
container: (none)contains: link*
inherits: entity_elementlinks: (none)
FieldTypeDescription
(id)?tokenThis attribute is needed so that others may link to it.
(base)?uriSee http://www.w3.org/TR/xmlbase/ for information about this attribute.
initials?short textInitials of name (use instead of first/middle).
first?short textFirst given name.
middle?short textSecond and subsequent given names.
prelast?short textPrefix such as "van" or "von der".
lastshort textSurname.
lineage?short textSuffixes such as "Jr.", "III".
email?short textEmail address.
phone?short textPhone number, including international dialing codes.
institution?short textInstitution or company where researcher works.
homepage?short textHome page of researcher, lab, or institution.
Return to top


citationsUsable as a top-level element in a stand-alone document containing only citations.
container: (none)contains: citation*, citation_external*
inherits: (none)links: (none)
Return to top





 Webmaster

Weill Medical College of Cornell University