SDD_EnumLib.xsd schema file overview
(Version: Unified Biosciences Information Framework (UBIF) 1.1)
TDWG working group: Structure of Descriptive Data (SDD)
Introduction
This document gives an overview of the schema components present in a single schema file, similar to the entry view provided by graphical schema editors. It documents only the root level annotations and components (elements, global attributes, simple and complex types, and groups). The definition of the components listed here is documented separately (hyperlinking could not yet be implemented).
Because the UBIF schema is designed as a type library, complex types represent class definitions and most schema files contain only a single root-level element.
Please see the schema documentation resource directory for schema overviews of other files and detailed component documentation.
Schema file content
The following content is generated automatically from the documentation inside the schema file:
This file will be included into the UBIF/SDD integration schema 'SDD.xsd' (SDD uses the same namespace as UBIF).
Copyright © 2006 TDWG (Taxonomic Databases Working Group, www.tdwg.org). See the file SDD_(c).xsd for authorship and licensing information.
Enumerations to support interoperability:
Internal formatting note: Annotations of individual enumerated values should be written as "short label" + " -- " + "detailed information" or "[abbreviation]" + " -- " + "short label" + " -- " + "detailed information". An xslt script transforms such schema annotations into a data document that can directly be used in user interfaces.
Please read: An important feature of this schema file is that these enumerations may be turned into data, many of them including extra specification data. Please see UBIF-EnumerationTools for further information. Using the data files in application development rather than hardcoding enumerations in code enables simple adaption to future versions of UBIF.
- NatLangPhraseRoleEnum (Simple type, based on xs:QName by restriction): Enumerated value expressing the kind of phrase or "wording fragment" used to create natural language reports (especially object descriptions). These are currently highly constrained, but either additional values or free extensibility (by union of this type with xs:anyURI) are expected for future releases of UBIF.
- CharacterTreeRoleEnum (Simple type, based on xs:QName by restriction): Defines the intended roles that a designer may assign to a character tree (list of enumerated values to support application interoperability). Note: no values for designing the terminology are given; in the use cases all character trees are available.
- RatingContextEnum (Simple type, based on xs:QName by restriction): Defines the topic of a concept/character rating.
- DataOriginEnum (Simple type, based on xs:QName by restriction): Defines the origin of data that may have been entered, calculated, aggregated or inherited
- ModifierClassEnum (Simple type, based on xs:QName by restriction): Defines a subset of possible modifier classes. Used only on those modifiers that need to be typed to achieve application interoperability (especially when modifier specifications add a value-based interpretation for a modifier, like frequency or certainty values). More values may be added to this enumeration in the future.
- UnivarStatMeasureClassEnum (Simple type, based on xs:QName by restriction): When mapping numerical ranges to categorical states (as in a histogram), several methods which statistical measures are used for the mapping are possible. Using the central value compares a point with the mapping range, whereas using ranges or extremes results in a comparison of two kind of ranges for overlap. Only the central value method can guarantee an unambiguous partitioning into categories. However, the ranges or extremes methods may be desirable because of their improved error tolerance.
- StateCollectionModelEnum (Simple type, based on xs:QName by restriction): Used in descriptive data (not in terminology): Collections of states in instance documents may be ordered (sequence) or unordered (set), and may be connected with 'and', 'or', 'with', or 'between'. Since set/sequence and operators are dependent on each other, the two aspects are combined into a 'model' enumeration
- MolecularSequenceTypeEnum (Simple type, based on xs:QName by restriction): Currently limited to 'Nucleotide' and 'Protein', but future SDD versions may expand this after appropriate discussion. A distinction between nucleotide type-subtypes RNA/DNA is currently not considered necessary; the symbols U (RNA) and T (DNA) should be considered equal for the purpose of analysis.
(Generated on 23. May 2006 by DiversitySchemaTools Version 0.5. Copyright (c) G. Hagedorn 2006.)