SddMapping

DonovanSharp - Wed Aug 30 2006 - Version 1.14
Parent topic: SddCharacters

SDD Part 0: Introduction and Primer to the SDD Standard

3.13 Mapping one character onto another

Mapping allows the definition of measurement units and the mapping of one character to another. Categorical states can be mapped onto other categorical states (i.e sub-ovate may be mapped onto ovate for identification purposes) and quantitative characters can be mapped onto categorical characters (i.e. 'length in mm' can be mapped onto the states 'small', 'medium' and 'large'.

3.13.1 Mapping a categorical character state onto another

Character states which are designed for a particular role (i.e. natural language descriptions) may be ambiguous in another role (i.e. identification keys) or for a different audience. For example Mapping allows the categorical state "sub-ovate" (useful for natural language descriptions to be mapped to the state "ovate" for the generation of dichotomous keys. In essence the state "ovate" becomes a parent state of a sub-state "sub-ovate". Multiple states can be mapped to a single state in this way, for example the states "yellowish" and "translucent" could be mapped to the state "white".

			<CategoricalCharacter id="c4">
				<Representation>
					<Label> Leaf shape</Label>
				</Representation>
				<States>
					<StateDefinition id="s3">
						<Representation>
							<Label>Round</Label>
						</Representation>
					</StateDefinition>
					<StateDefinition id="s4">
						<Representation>
							<Label>Ovate</Label>
						</Representation>
					</StateDefinition>
					<StateDefinition id="s5">
						<Representation>
							<Label>Sub-ovate</Label>
						</Representation>
					</StateDefinition>
				</States>
				<Mappings>
					<Mapping>
						<From ref="s5"/>
						<To ref="s4"/>
					</Mapping>
				</Mappings>
			</CategoricalCharacter>

3.13.2 Mapping a quantitative character onto a categorical character

Specific ranges of a quantitative character data can be mapped onto states of categorical characters, for example, to simplify the data for interactive key purposes. For example the data to populate the character "Leaf Area (Webb and Tracy Units)" with the four states "nanophyll", "microphyll", "mesophyll" and "macrophyll" would be automatically generated from the data in the quantitative character "Leaf Area".

Example 3.13.2.1 - Units and mapping within quantitative characters.

<QuantitativeCharacter id="c2">
  <Representation>
    <Label>Leaf length</Label>
  </Representation>
  <Assumptions>
    <MeasurementScale>Ratio</MeasurementScale>
  </Assumptions>
  <Mappings>
    <Mapping>
      <From lower="0" upper="3"/>
      <ToState ref="s1"/>
    </Mapping>
    <Mapping>
      <From lower="3" upper="10"/>
      <ToState ref="s2"/>
    </Mapping>
    <Mapping>
      <From lower="4" upper="10000000"/>
      <ToState ref="s3"/>
    </Mapping>
  </Mappings>
  <MeasurementUnit>
    <Label role="Abbrev">m</Label>
  </MeasurementUnit>
  <Default>
    <MeasurementUnitPrefix>milli</MeasurementUnitPrefix>
  </Default>
</QuantitativeCharacter>

<From> gives an inclusive range defined through the two attributes "lower" and "upper".

<ToState> specifies the categorical state corresponding to the range defined in <From>. If <ToState> is missing then <From> governs partitioning into range classes automatically generated from the "upper" and "lower" values.

-- Main.DonovanSharp - 06 Jun 2006