head 1.5;
access;
symbols;
locks; strict;
comment @# @;
1.5
date 2009.11.25.03.14.32; author GarryJolleyRogers; state Exp;
branches;
next 1.4;
1.4
date 2009.11.20.02.45.24; author LeeBelbin; state Exp;
branches;
next 1.3;
1.3
date 2007.03.06.17.30.00; author TWikiGuest; state Exp;
branches;
next 1.2;
1.2
date 2006.05.11.08.46.57; author GregorHagedorn; state Exp;
branches;
next 1.1;
1.1
date 2006.05.10.15.46.49; author GregorHagedorn; state Exp;
branches;
next ;
desc
@none
@
1.5
log
@none
@
text
@%META:TOPICINFO{author="GarryJolleyRogers" date="1259118872" format="1.1" version="1.5"}%
%META:TOPICPARENT{name="DELTAandBDI.SDD"}%
---+!! %TOPIC%
---++Broad comparison of DELTA and SDD features
---+++Synopsis
The primary object types of 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][SDD for DELTA experts]].
---+++Object classes of SDD
Note: the left side represents first-class and some second-class objects in SDD. Names in bracketed are not directly represented in SDD but are used to group objects.
| SDD model |
Notes on related DELTA features |
| |
|
|
|
Datasets |
(The root element of 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 |
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 SDD. |
| | |
|
(Biological Entities:) |
|
|
TaxonNames |
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 |
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 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 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 | |
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 SDD (0.9), supporting freely definable values and labels for these. Implementation attempts of SDD revealed, however, that this was not accepted well and caused significant application interoperability problems. The final release of 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". 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. 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 SDD and DELTA. The character definition in SDD also contains information from the DELTA !*CHAR TYPES, !*KEY STATES (= SDD Mappings) directives. In contrast to DELTA, the order of characters in 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 | |
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, 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 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. SDD allows external references, embedded resource data, and provides for a multilingual caption. |
-- Main.GregorHagedorn - 10 May 2006 (First version published outside of the Wiki by Gregor Hagedorn on 24. November 2003)@
1.4
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="LeeBelbin" date="1258685124" format="1.1" reprev="1.4" version="1.4"}%
d5 1
a5 1
---++Broad comparison of DELTA and BDI.SDD features
d9 1
a9 1
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]].
d11 1
a11 1
---+++Object classes of BDI.SDD
d13 1
a13 1
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.
d17 1
a17 1
| BDI.SDD model |
d24 1
a24 1
(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.) |
d27 1
a27 1
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) |
d34 1
a34 1
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.
d41 1
a41 1
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. |
d56 1
a56 1
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. |
d60 1
a60 1
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. |
d64 2
a65 2
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. |
d68 1
a68 1
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.). |
d72 1
a72 1
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. |
d77 1
a77 1
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.
d82 1
a82 1
| BDI.SDD States may be defined either local within a character (equivalent of DELTA states) or enabled by reference to concept states. |
d88 1
a88 1
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.
d112 1
a112 1
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. |
d120 1
a120 1
In DELTA images are directly identified through path and filename. BDI.SDD allows external references, embedded resource data, and provides for a multilingual caption. |
d123 1
a123 1
-- Main.GregorHagedorn - 10 May 2006 (First version published outside of the Wiki by Gregor Hagedorn on 24. November 2003)
@
1.3
log
@Added topic name via script
@
text
@d1 2
d5 1
a5 3
%META:TOPICINFO{author="GregorHagedorn" date="1147337217" format="1.1" version="1.2"}%
%META:TOPICPARENT{name="DELTAandSDD"}%
---++Broad comparison of DELTA and SDD features
d9 1
a9 1
The primary object types of 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 [[DELTAandSDD][SDD for DELTA experts]].
d11 1
a11 1
---+++Object classes of SDD
d13 1
a13 1
Note: the left side represents first-class and some second-class objects in SDD. Names in bracketed are not directly represented in SDD but are used to group objects.
d17 1
a17 1
| SDD model |
d24 1
a24 1
(The root element of 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.) |
d27 1
a27 1
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) |
d34 1
a34 1
The DELTA "*NUMBER OF CHARACTERS", "*MAXIMUM NUMBER OF STATES", and "*MAXIMUM NUMBER OF ITEMS" directives contain some technical project information which are redundant in SDD.
d41 1
a41 1
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. |
d56 1
a56 1
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 SDD, the concepts expressed in such hierarchies are defined here, and the relation to characters in the character trees detailed further below. |
d60 1
a60 1
In 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. |
d64 2
a65 2
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 SDD (0.9), supporting freely definable values and labels for these. Implementation attempts of SDD revealed, however, that this was not accepted well and caused significant application interoperability problems. The final release of SDD 1.0 has therefore reverted to globally defined semantics (controlled through enumerated values) for coding status values and statistical measures. |
d68 1
a68 1
DELTA has 3 fixed "special symbols" or "pseudo-values": "U", "-", and "V". 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.). |
d72 1
a72 1
DELTA has 5 fixed measures: minimum, undefined lower range, undefined central value, undefined upper range, maximum. SDD adds various defined ranges and central values, variance measures, sample size as well as a generic extensible mechanism to define these. |
d77 1
a77 1
The single flat character list containing states is relatively similar in SDD and DELTA. The character definition in SDD also contains information from the DELTA !*CHAR TYPES, !*KEY STATES (= SDD Mappings) directives. In contrast to DELTA, the order of characters in 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.
d82 1
a82 1
| SDD States may be defined either local within a character (equivalent of DELTA states) or enabled by reference to concept states. |
d88 1
a88 1
In contrast to DELTA, SDD can express multiple character hierarchies, and also alternative character sequences (order in which characters are arranged) by using multiple character trees.
d112 1
a112 1
No management of authors, editors, contributors, translators and their respective contributions is available in DELTA. In SDD, this is a central repository for names of persons or organization, and is used throughout the data when attributing intellectual work. |
d120 1
a120 1
In DELTA images are directly identified through path and filename. SDD allows external references, embedded resource data, and provides for a multilingual caption. |
@
1.2
log
@none
@
text
@d1 2
@
1.1
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="GregorHagedorn" date="1147276009" format="1.1" version="1.1"}%
d7 1
a7 1
The sections and subsections of the SDD schema are shown in a tabular display and annotations are provided pointing to relations and differences with the DELTA format. See also the overview SDD for DELTA experts.
d11 1
a11 2
| SDD model | | Notes on related DELTA features |
d13 13
a25 4
|
GenerationMetadata
|
(No information is available in DELTA on the version of DELTA in which the file is written, and on the program that created the file.) |
d27 43
a69 23
| |
|
ProjectDefinition
|
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 *NUMBER OF CHARACTERS, *MAXIMUM NUMBER OF STATES, and *MAXIMUM NUMBER OF ITEMS directives contain some technical project information which have no equivalent in SDD. |
| |
|
Terminology |
(= similar to CHARS file in CSIRO DELTA) |
| |
Glossary |
|
Provides definitions for characters, states, properties, structures, etc. A related feature of DELTA is the *CHAR NOTES directive. |
|
CodingStatus |
DELTA has 3 fixed "special symbols" or "pseudo-values": "U", "-", and "V". SDD does not support an equivalent to "V" but provides additional coding status values as well as a generic extensible mechanism to define these. |
|
StatisticalMeasures |
d71 39
a109 36
|
Modifiers |
DELTA uses free-form comments for probability, frequency ("rarely"), degree ("strongly", "weakly"), timing ("when mature"), location ("at the base"), etc. modifiers. DELTA comments have to be translated into a second language at every place they are used. In SDD all modifiers are centrally managed and translated. Probability, frequency, and by-misinterpretation further provide an analytical description. |
|
Characters |
The single flat character list containing states is relatively similar in SDD and DELTA. The character definition in SDD contains the information from the DELTA *CHAR TYPES, *KEY STATES (= SDD Mappings) directives. Note that in contrast to DELTA, the sequence of characters in SDD is not informative and is instead defined exclusively in concept trees. This allows different character sequences for different reporting purposes. |
|
Concept Trees |
Concept trees can express basic terminological concepts (structural hierarchy, property hierarchy, methods) not available in DELTA, as well as operational hierarchies for listing characters in a character definition report, in interactive keys, or in natural language reports. They define both a hierarchy (in DELTA compare the single level hierarchies *CHAR HEADINGS for character list report, *ITEM SUBHEADINGS for natural language reporting, *DEFINE CHARACTERS for Intkey) and a sequence. In contrast to DELTA, SDD can express multiple character sequences if desired. 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) |
| | |
| |
|
Entities |
|
| |
Classes |
|
Classes provide the equivalent of Item Names in DELTA. In SDD taxon names are centrally defined here and are linked to external taxonomic databases. |
|
ClassHierarchies |
DELTA does not support taxonomic hierarchies in general. It does provide a special multi-item taxon mechanism with main and variant items. |
|
Objects |
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. |
| | |
| |
|
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 |
|
d111 3
a113 2
|
Publications |
d115 3
a117 2
|
MediaResources |
a118 21
| | |
| |
|
Descriptions |
(= similar to ITEMS file in CSIRO DELTA) |
| |
NaturalLanguageDescriptions |
|
DELTA has no option to markup existing natural language descriptions. Note that this section has little to do with the DELTA option to produce formatted natural language descriptions from coded data. |
|
CodedDescriptions |
This is directly equivalent to *ITEM DESCRIPTIONS in DELTA. |
| | |
| |
|
Keys |
DELTA provides no data structure for dichotomous/multifurcating keys that are manually created or digitized from publications. |
d121 1
a121 2
-- Main.GregorHagedorn - 10 May 2006 (First version published outside of Wiki by Gregor Hagedorn on 24. November 2003)
@