State:

Dtd:

state.dtd

<!-- # state.dtd defining the structure of each character state under character group of a taxon -->
<!-- # Based on notes taken in March 2003 -->
<!-- # Last updated 16 September 2003 -->

<!-- http://www.isrl.uiuc.edu/~openkey/shared/state.dtd -->

<!ELEMENT State (StateName*, Definition?, Image*, Example*, Synonym*, BroaderTerm*, NarrowerTerm*, RelatedTerm*, Prevelence?, Certainty?, (DisplayBefore?, DisplayFor?, DisplayAfter?)?)>

<!ELEMENT StateName (#PCDATA)>
<!-- StateName: should not be named state here because the whole record is state -->
<!ATTLIST StateName
name CDATA #IMPLIED
file CDATA #IMPLIED>
<!ELEMENT Definition (#PCDATA)>
<!ELEMENT Image (#PCDATA)>
<!ATTLIST Image
name CDATA #IMPLIED
file CDATA #IMPLIED
reason CDATA #IMPLIED>
<!ELEMENT Example (#PCDATA)>
<!ELEMENT Synonym (#PCDATA)>
<!ELEMENT BroaderTerm (#PCDATA)>
<!ELEMENT NarrowerTerm (#PCDATA)>
<!ELEMENT RelatedTerm (#PCDATA)>
<!ELEMENT Prevelence (#PCDATA)>
<!-- Prevelence: always, usually, blue_moon -->
<!ELEMENT Certainty (#PCDATA)>
<!-- Certainty: positive, wild_guess, 50% sure -->
<!ELEMENT DisplayBefore (#PCDATA)>
<!ELEMENT DisplayFor (#PCDATA)>
<!ELEMENT DisplayAfter (#PCDATA)>


<!-- OBSOLETE?? !ELEMENT CharacterType (#PCDATA) -->
<!-- CharacterType should now be handled in character.dtd. Comment added PBH 8/8/03 -->
<!-- OBSOLETE?? !ELEMENT Wording (#PCDATA) -->
<!-- Wording has been replaced with DisplayBefore, DisplayFor and DisplayAfter but will need to be restored by concatination of these fields to conform to the standard used by other interactive key software packages. Comment added PBH 8/8/03 -->
<!-- OBSOLETE?? ELEMENT LegalValue (#URI) -->
<!-- do we want the path to the character group? -->
<!--
was up to spetember 15, 2003
ELEMENT State ((StatePath* | CharacterGroup* | Character* | Value*)+, Definition?, Image*, Example*, Synonym*, BroaderTerm*, NarrowerTerm*, RelatedTerm*, Prevelence?, Certainty?, (DisplayBefore?, DisplayFor?, DisplayAfter?)?)
-->
<!--
obsolete
ELEMENT StatePath (#PCDATA)
-->
<!-- StatePath will allow our input form to use the same dtd, store the stuff (if needed) in path format before we change it to CharacterGroup format
ELEMENT CharacterGroup (CharacterGroup*, Character?)
ATTLIST CharacterGroup
name CDATA #IMPLIED
file CDATA #IMPLIED>
<!ELEMENT Character (Value* | Image*)>
<!ATTLIST Character
name CDATA #IMPLIED
file CDATA #IMPLIED
type (range | count | size | text) "text">
-->


XML:

acute.xml

<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE State (View Source for full doctype...)>
- <!-- created by split_definitions.pl 2003_9_29_0_12
-->
- <State>
<StateName name="acute" file="/home/openkey/public_html/prairieplant/state/xml/acuteiii. repeated characters .xml">acute</StateName>
<Definition><em>(iii. repeated characters )</em> [Leaflets, Leaves, Petals, Phyllaries, Sepals] Tapering to a pointed apex with more or less straight sides, the sides coming together at an angle of less than 90º. (Compare with acuminate and obtuse.) [H&H2, p. 153, modified] [Illustrations: RDMB, p. 135, Fig. 6-15; H&H2, p. 154, Fig. 1585a; L, p. 744, Fig. 307; W&K, p. 37, Fig. 3-8]</Definition>
<Image>none yet</Image>
<Example />
<Synonym />
<Synonym />
<BroaderTerm />
<NarrowerTerm />
<RelatedTerm>acuminate and obtuse</RelatedTerm>
<Prevelence />
<Certainty />
<DisplayBefore />
<DisplayFor>acute</DisplayFor>
<DisplayAfter>,</DisplayAfter>
</State>

 

back to top

Home -Contact - Sitemap
Last updated on Feb 9, 2004