- <path>value</path>
The importance of paths has already been mentioned under the section explaining 20q controls.
The first path in the data section above is telling the system where the genus Bombus is located. The second path is telling
the system where the "Genus species" pair "Bombus abnormis" is located.
Note: If the path is incorrect and files cannot be found, error messages will appear telling you what cannot be found.
- <set type="taxon" level="genus">...other XML tags & data...</set>
It goes without saying that when the taxon level is set as "genus," the data immediately following
will be about that genus. Also note that at the end of each segment dealing with each genus or species, there is a corresponding
</set>. This completes the wraparound of the set type.
- <name>value</name>
The organism you are specifying the path for must be wrapped in the name tags.
Example:
<name>Genus species</name>
- <authority>value</authority>
Put the authority for the organism here. Make sure this authority is correct, adding
parentheses if necessary. If possible, include a date with the authority.
- <easy_name>value</easy_name>
Easy names are arbitrarily assigned names to a particular organism. This is meant to be a simplifying tool,
especially for younger children.
- <common_name>value</common_name>
The common name is the most widely known name or names for the organisms. Example: Papilio glaucus is better
known as the Tiger Swallowtail. This tag has the ability to feature other languages than english.
- <attributes>...other XML tags and data...</attributes>
The attributes section holds all the characters and states you are including for the organism.
- <character>...other XML tags and data...</character>
The most important part of your file will probably be what is contained within the characters and states. Choose characters
carefully, trying to separate as many organisms as possible without including extraneous information or words.
- <state>value</state>
States define a precise characteristic of the organism in question.
Example:
<path>Insecta/Lepidoptera/Pieridae/Coliadinae</path>
<set type="taxon" level="species">
<name>Anteos clorinde</name><authority>(Godart), 1824</authority>
<easy_name>Ghost Brimstone</easy_name>
<common_name language="english">White Angled-Sulphur</common_name>
<attributes>
<character>Antenna shape</character>
<state>Club, rounded</state>
<character>Leg number</character>
<state>6</state>
</attributes>
</set>
As an example of how the characters and states are used as exclusions within the system, we can also include in the file
another butterfly that does not have clubbed antennae. In this circumstance, you will have to decide what you will call this new kind
of antennae and replace "Club, rounded" with that definition. When the guide for this file is displayed on
the web, there will be two options beneath the character "Antennae shape," and choosing the correct option
for your specimen will allow you to identify it properly. When you are first developing the file, you will decide what
characters are necessary and can continue developing states for the various individuals from that point.
- <include>value</include>
The value is the URL to another 20q.xml file that is to be included in the present file. You may have multiple
<include> tags and values within one file.
|