SDD proposal: Adding misinterpretation hints

TDWG working group: Structure of Descriptive Data (SDD)

Introduction

To achieve good identification rates, common misinterpretations of characters or states must be taken care of. If the designer of a data set adds false statements to preempt misinterpretations of users without distinguishing them from true statements, the data set degenerates and becomes difficult to manage and revise. Furthermore, it can then only be used for identification purposes and not, for example, for phylo­genetic analysis.

Among the current identification packages, only LucID fully supports a separate markup for misinterpretations. In DELTA the information itself can be stored as a comment, but is not available for further analysis. DeltaAccess supports misinterpretation markers through modifiers, but the initial versions had the same problems as DELTA, i. e. a misinterpretation preemption could not be recognized during analysis. Starting with version 1.8, DeltaAccess has added a new attribute to identify these modifiers.

Several types of misinterpretation can be distinguished:

  1. The organism part (= structure) is generally likely to be misinterpreted
    Examples: a phylloclade (= cladode) is interpreted as a leaf, or a rhizome as a root.
  2. The organism part is likely to be misinterpreted within a given taxonomic group
    Example: the inflorescence is often interpreted as a flower in Euphorbia. Or the bracts of Cornus florida (dogwood) are interpreted as petals.
  3. The property state is generally likely to be misinterpreted.
    Example: a spore surface that is visibly rough in a good microscope may be interpreted as smooth because of insufficient optics or inappropriate handling of the microscope.
  4. The property state is likely to be misinterpreted within a given taxonomic group.
    Example: Leaves of Lotus corniculatus are palmate with 3 leaflets plus 2 leaflet-like stipules, but often misinterpreted as pinnate with 5 leaflets.

The cases differ in how they ideally would be handled:

All cases can in principle be managed with the single mechanism of description x state-specific misinterpretation attributes, although this would require extensive work by the designer (e. g. adding potentially misinterpreted statements to a number of characters if the confusion is really about a misinterpretation of the part that is being described.

Proposal

Request for discussion

Please send your criticism or suggestions to the SDD mailing list or to any of the authors.

Gregor Hagedorn; Version 2; 11. November 2003
Earlier versions: Version 1



Return to the SDD starting page.

First published 2002-02-20, last update: 2003-11-11.

Valid XHTML 1.0! Valid CSS1! Viewable With Any Browser