species-brainstorming: Difference between revisions
AndyMabbett (talk | contribs) m (fix) |
AndyMabbett (talk | contribs) m (fmt) |
||
Line 12: | Line 12: | ||
This would also allow of the marking-up of superseded scientific names: | This would also allow of the marking-up of superseded scientific names: | ||
:< | :<pre><nowiki>The species was classified <abbr class="sci" title="Bartramia longicauda">Tringa longicauda</abbr> by Johann Matthaus Bechstein, in 1812.</nowiki></pre> | ||
The microformat would allow user agents to be configured to perform look-ups on on-line databases of species, according to user preferences. Specification of the taxonomic class would help user agents to know which such databases were applicable (i.e., use database A for plants, but database B for mammals and database C for insects.) | The microformat would allow user agents to be configured to perform look-ups on on-line databases of species, according to user preferences. Specification of the taxonomic class would help user agents to know which such databases were applicable (i.e., use database A for plants, but database B for mammals and database C for insects.) | ||
Line 48: | Line 48: | ||
where all except "bin" are optional, and it is possible to infer from simply: | where all except "bin" are optional, and it is possible to infer from simply: | ||
:< | :<pre><nowiki><abbr class="bin" title="Anas platyrhynchos">Mallard</abbr></nowiki></pre>> | ||
or | or | ||
:< | :<pre><nowiki><span class="bin">Anas platyrhynchos</span></nowiki></pre> | ||
that the genus is ''Anas'' and the species is ''platyrhynchos'' (and, thus, "bin" is to "sci"; as "adr" is to "vcard") | that the genus is ''Anas'' and the species is ''platyrhynchos'' (and, thus, "bin" is to "sci"; as "adr" is to "vcard") | ||
Revision as of 15:17, 19 September 2006
Species Brainstorming
Andy Mabbett
Proposal
There should, I believe, be a microformat for the markup of plant and animal names, to include their scientific names. Consider:
<abbr class="sci" title="Anas platyrhynchos">Mallard</abbr>
or
<span class="sci">Anas platyrhynchos</span>
This would also allow of the marking-up of superseded scientific names:
The species was classified <abbr class="sci" title="Bartramia longicauda">Tringa longicauda</abbr> by Johann Matthaus Bechstein, in 1812.
The microformat would allow user agents to be configured to perform look-ups on on-line databases of species, according to user preferences. Specification of the taxonomic class would help user agents to know which such databases were applicable (i.e., use database A for plants, but database B for mammals and database C for insects.)
It would also allow for more specific searching (do I mean "crow" or do I mean "Corvus corone"?).
The specification should encourage, but not mandate, the correct capitalisation of scientific names "Anas platyrhynchos" not "anas platyrhynchos".
A first draft
I'm tending towards this model:
- sci (scientific name)
- kingdom
- phylum
- class
- order
- family
- bin ("binomial name")
- genus
- species
- sub ("subspecies")
- var ("variety")
- subvar ("subvariety")
- form
- subform
- cult ("cultivar")
- cultgp ("cultivar group")
- trade ("trade name")
- cross (e.g. "F1")
- strain
- authority
- year (...of authority)
- cname ("common name")
where all except "bin" are optional, and it is possible to infer from simply:
<abbr class="bin" title="Anas platyrhynchos">Mallard</abbr>
>
or
<span class="bin">Anas platyrhynchos</span>
that the genus is Anas and the species is platyrhynchos (and, thus, "bin" is to "sci"; as "adr" is to "vcard")
Other examples
<span class="sci"> <span class="bin">Larus glaucoides</span> <span class="sub">kumlieni</span> </span>
<span class="sci"> <span class="bin">Pisum sativum</span> var. <span class="var">macrocarpon</span> </span>
<span class="sci"> <abbr class="bin" title="Larus thayeri"> <span class="common">Thayer's Gull</span> </abbr> </span>
<span class="sci"> <abbr class="common" title="Thayer's Gull"> <span class="bin" Larus thayeri</span> </abbr> </span>
<span class="sci"> <abbr class="kingdom" title="Fungi"> <span class="bin">Amanita muscaria</span> </abbr> </span>
<span class="sci"> <span class="bin">Pica pica</span> <span class="authority">Linnaeus</span>, (<span class="year">1758</span>) </span>
Questions
- Is "sci" the best attribute name for the top-level?
- Should "bin", var", "cult", etc., be written in full? (I think not, to save bloating file sizes)
- Should other attribute names be abbreviated for brevity?
- Is "class" a potentially confusing attribute name, and what should replace it ("taxoclass", perhaps?)
- What other attribute names are needed, if any (we could do with help from a taxonomist!)
- How to deal with: "Podiceps sp." (a grebe of unknown species)
- Should we allow divisions of "bin" with no parent "sci", such as:
Larus glaucoides kumlieni
- Does "year of authority" need to be an hcal?
Embedding within other microforamts
The proosed plant microformat (with care regime, supplier, etc.), listing or hReview could contain a scientific name microformat, in the same way that an hCal can contain an hCard.
References
- Wikipedia: Scientific classification
- International Commission on Zoological Nomenclature
- International Code of Botanical Nomenclature *[1]