</td>

*SHOW: Gentianella - character list. Last revised 16 April 1997.

*CHARACTER LIST

#1. plants/
1. monocarpic/
2. polycarpic/

#2. <plants lifecycle>/
1. annual/
2. biennial/
3. perennial/

#3. height in flower/
<> cm/

#4. caudex/
1. unbranched/
2. branched/

*ITEM DESCRIPTIONS

# Gentianella amabilis/
1,2 2,3 3,3-13 4,1

# Gentianella antarctica/
1,1 2,1<Godley 1982> 3,1.6-22.0<Godley 1982> 4,1

# Gentianella antipoda/
1,1<Godley 1982> 2,2 3,3.5-9.8-24 4,1/2<depends on size of plant>

# Gentianella astonii/
1,2 2,3 3,15 4,2

# Gentianella cerina/
1,2 2,3 3,9-17 4,1/2

#Gentianella concinna/
1,1 2,1 3,2.7-15.0 4,1
 </div>

</td>

 </td> </tr> </table>

</div>

Coded summary descriptions record the range of characteristics found in a taxon (such as a family, genus, species etc). To record raw (sample) data for individual specimens, see the topic Using Main.BDI for raw (sample) data.

A coded sample description requires three essential items: the names of the taxa being described, a set of descriptors (characters and states) used to describe the taxa, and the coded descriptions themselves.

A simple Main.BDI instance document for coded summary data has the basic structure shown below and in Example 2.1.1.

Example 2.1.1 - A simple coded description

<?xml version="1.0" encoding="UTF-8"?>
<Datasets xsi:schemaLocation="http://ns.tdwg.org/UBIF/2006/ 
  http://www.lucidcentral.org/2006/SDD/SDD1.1-RC1/SDD.xsd" 
  xmlns="http://ns.tdwg.org/UBIF/2006" 
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <Dataset xml:lang="en-us">
    <TaxonNames>
      <TaxonName id="t1">
        <Representation>
          <Label>Acanthaceae</Label>
        </Representation>
      </TaxonName>
          ...etc
    </TaxonNames>
    <Characters>
      <CategoricalCharacter id="c1">
        <Representation>
          <Label>Habit</Label>
        </Representation>
        <States>
          <StateDefinition id="s1">
            <Representation>
              <Label>tree</Label>
            </Representation>
          </StateDefinition>
          <StateDefinition id="s2">
            <Representation>
              <Label>shrub</Label>
            </Representation>
          </StateDefinition>
          <StateDefinition id="s3">
            <Representation>
              <Label>herb</Label>
            </Representation>
          </StateDefinition>
        </States>
      </CategoricalCharacter>
          ...etc
    </Characters>
    <CodedDescriptions>
      <CodedDescription id="cd1">
        <Representation>
          <Label>Acanthaceae</Label>
        </Representation>
        <Scope>
          <TaxonName ref="t1"/>
        </Scope>
        <SummaryData>
          <Categorical ref="c1">
            <State ref="s2"/>
            <State ref="s3"/>
          </Categorical>
        </SummaryData>
          ...etc
      </CodedDescription>
    </CodedDescriptions>
    <MediaObjects/>
  </Dataset>
</Datasets>

For more information on defining taxon names using the <TaxonNames> element, see the topic Defining taxon names. For more infirmation on defining characters and states using the <Characters> element, see the topic Defining characters and states.

Both taxa and characters can be arranged into hierarchies; see Defining taxon hierarchies and Defining character hierarchies for more information.

The <Representation> element provides a label for the description. This reflects the fact that a single taxon may have several descriptions. In a butterfly, "Gonepteryx rhamni, male" and "Gonepteryx rhamni, female", and "caterpillar of Gonepteryx rhamni" may be three different descriptions. Other examples are descriptions scoped to a geographic region ("in Australia"), to a small number of defined specimens, or to a given publication (which may have been kept separate because less trusted). Each coded description in Main.BDI may express these scopes of a description in the Scope element. To allow human users a simple and consistent access to descriptions, the separate description label is provided.

One problem that Main.BDI cannot solve itself is the fact that while some data models make a distinction between a taxon and multiple descriptions, many do not. Most current programs either have no formal taxon name (e.g. DELTA, Xper, etc. are careful to avoid the name "taxon description") or they handle male/female as pseudo-taxa (Lucid, ETI-Linneaus II). Software importing and exporting Main.BDI therefore needs to take care to accept both datasets that have only a Description Label and those that have explicit Taxon names.

<Scope> describes the taxon or set of taxa to which the description applies.

Characters used in the description are listed under <SummaryData>. Main.BDI distinguishes between different kinds of characters (see the topic Defining characters and states for more information). For categorical characters (characters with states) the states occurring in the taxon being described are listed by reference. In the example given above, the taxon Acanthaceae is described as being a shrub or herb (states s2 and s3 of character c1). Note that states that are not listed are inferred to not occur in the taxon being described.

States used in a description can also be modified using a predefined set of modifiers (such as "rare", "uncertain" etc.). See the topic <DescriptiveConcepts> for more information

-- Main.KevinThiele - 06 Jul 2006