%META:TOPICINFO{author="GarryJolleyRogers" date="1259118872" format="1.1" version="1.5"}% %META:TOPICPARENT{name="DELTAandBDI.SDD"}% ---+!! %TOPIC% ---++Broad comparison of DELTA and BDI.SDD_ features ---+++Synopsis The primary object types of BDI.SDD_ are shown in a tabular display and annotations are provided pointing to relations and differences with the [[http://biodiversity.bio.uno.edu/delta/][DELTA]] format. See also the overview [[DELTAandBDI.SDD][BDI.SDD_ for DELTA experts]]. ---+++Object classes of BDI.SDD_ Note: the left side represents first-class and some second-class objects in BDI.SDD_. Names in bracketed are not directly represented in BDI.SDD_ but are used to group objects.
BDI.SDD_ model | Notes on related DELTA features | |||
Datasets | (The root element of BDI.SDD_ is called Datasets; containing a single TechnicalMetadata element and an unlimited number of Dataset elements. All other objects are inside one of the Dataset elements.) | |||
TechnicalMetadata | BDI.SDD_ provides creation date/time, metadata about the software (name, version) that created the file (in /Generator), etc. No equivalent information is available in DELTA, often leading to problems in recognizing "DELTA dialects" (e.g. between CSIRO Delta, Pankey, and DeltaAccess) | |||
Dataset /Representation |
Project or data set metadata is sparse in DELTA. Some information about the entire descriptive project (title, date, authors) may be available in "*SHOW" and "*COMMENT" directives. No information (including copyright statement) is required, however. The DELTA "*NUMBER OF CHARACTERS", "*MAXIMUM NUMBER OF STATES", and "*MAXIMUM NUMBER OF ITEMS" directives contain some technical project information which are redundant in BDI.SDD_. | |||
(Biological Entities:) | ||||
TaxonNames | BDI.SDD_ provides a controlled vocabulary for taxon names (including concepts) which may be linked to or derived from external taxonomic databases. DELTA provides taxon names only through the Item Name, which may be a mixture or taxon name, specimen information, sex, etc. | |||
TaxonHierarchies | DELTA does not support a general taxonomic hierarchy. It does provide one-level hierarchy through the multi-item taxon mechanism with main and variant items. | |||
Specimens | If biological specimens are studied in DELTA, it is possible to add the specimen identifier or description (Collector, date, etc.) as comments in the Item Name. | |||
(Descriptive Terminology:) | (= similar to content of CHARS file in CSIRO DELTA) | |||
!DescriptiveConcepts | BDI.SDD_ !DescriptiveConcepts express basic terminological concepts (structural hierarchy, property hierarchy, methods) not directly available in DELTA. DELTA has limited support for "headings" to define concepts more general than characters. These single-level-hierarchies are "*CHAR HEADINGS" for character list report, "*ITEM SUBHEADINGS" for natural language reporting, and "*DEFINE CHARACTERS" for Intkey. In BDI.SDD_, the concepts expressed in such hierarchies are defined here, and the relation to characters in the character trees detailed further below. | |||
(Second-class objects:) | ||||
Modifiers | In BDI.SDD_ all modifiers for probability, frequency ("rarely"), degree ("strongly", "weakly"), timing ("when mature"), location ("at the base"), etc. are centrally managed and may be centrally translated; probability, frequency, and by-misinterpretation modifiers further provide an analytical description. In contrast, DELTA can express modifier information only through free-form text comments. When translating descritions into multiple languages, such DELTA comments have to be translated in every description. | |||
ConceptStates | BDI.SDD_ provides a mechanism to centrally define state values that are reusable in multiple characters. DELTA has no equivalent of this. | |||
The following Coding Status and Statistical Measures used to be second-class objects in early versions of BDI.SDD_ (0.9), supporting freely definable values and labels for these. Implementation attempts of BDI.SDD_ revealed, however, that this was not accepted well and caused significant application interoperability problems. The final release of BDI.SDD_ 1.0 has therefore reverted to globally defined semantics (controlled through enumerated values) for coding status values and statistical measures. | ||||
(Coding Status) | DELTA has 3 fixed "special symbols" or "pseudo-values": "U", "-", and "V". BDI.SDD_ supports DELTA "U" (Data not available) and "-" (not applicable), has rejected support for an equivalent to DELTA "V", and adds further status values (not interpretable, data withheld, not to be coded, etc.). | |||
(Statistical Measures) | DELTA has 5 fixed measures: minimum, undefined lower range, undefined central value, undefined upper range, maximum. BDI.SDD_ adds various defined ranges and central values, variance measures, sample size as well as a generic extensible mechanism to define these. | |||
Characters | The single flat character list containing states is relatively similar in BDI.SDD_ and DELTA. The character definition in BDI.SDD_ also contains information from the DELTA !*CHAR TYPES, !*KEY STATES (= BDI.SDD_ Mappings) directives. In contrast to DELTA, the order of characters in BDI.SDD_ is not informative and is instead defined exclusively in the character trees. This enables different character sequences for different reporting purposes and splitting characters into multiple files or reusing characters from different terminologies. Representation/Detail with role="Description" or role="Normative" enables to supply simple textual definitions and is related to the DELTA !*CHAR NOTES directive. | |||
(Second-class objects:) | ||||
States | BDI.SDD_ States may be defined either local within a character (equivalent of DELTA states) or enabled by reference to concept states. | |||
!CharacterTrees | These define operational hierarchies for listing characters in a character definition report, in interactive keys, or in natural language reports. The nodes may be labeled by reference to descriptive concepts. Character trees define both a hierarchy and an order for the unstructured and unordered list of characters. In contrast to DELTA, BDI.SDD_ can express multiple character hierarchies, and also alternative character sequences (order in which characters are arranged) by using multiple character trees. Furthermore, when used for natural language reporting (equivalent to the CSIRO DELTA TONAT command), the format and structure of the natural language description is defined here as well (!*LINK CHAR, !*NEW PARAGRAPHS AT CHARACTERS, !*Replace Semicolon By Comma, etc. directives) | |||
(Descriptions and keys:) | (= similar to ITEMS file in CSIRO DELTA) | |||
NaturalLanguageDescriptions | DELTA has no option to markup existing natural language descriptions. Note that this type of description is not related to the creation of formatted natural language descriptions from coded data. | |||
CodedDescriptions | This is directly equivalent to !*ITEM DESCRIPTIONS in DELTA. | |||
IdentificationKeys | DELTA provides no data structure for dichotomous/multifurcating keys that are manually created or digitized from publications. | |||
(General resources:) | DELTA has no similar feature, but the proposal for a DELTA II system contains !*NUMBERED LIST and !*ALPHABETIC LIST directives with a similar aim. The DELTA II proposal provides only for DELTA-internal lists, not for linking with external data providers. | |||
Agents | No management of authors, editors, contributors, translators and their respective contributions is available in DELTA. In BDI.SDD_, this is a central repository for names of persons or organization, and is used throughout the data when attributing intellectual work. | |||
Publications | Publications are not handled in the original DELTA (but proposal were made for DELTA II). Commonly information from published sources is handled as a free-form comment in DELTA. | |||
MediaObjects | In DELTA images are directly identified through path and filename. BDI.SDD_ allows external references, embedded resource data, and provides for a multilingual caption. |