Bothrocara
| Bothrocara | |
|---|---|
 | |
| Bothrocara brunneum | |
| Scientific classification | |
| Kingdom: | |
| Phylum: | |
| Class: | |
| Order: | |
| Family: | |
| Genus: | Bothrocara Bean, 1890 |
| Species | |
|
about 8, see text | |
Bothrocara is a genus of eelpouts.
Species include:[1]
- Bothrocara brunneum - twoline eelpout
- Bothrocara elongatum
- Bothrocara hollandi
- Bothrocara molle - soft eelpout, pighead eelpout, shortsnout eelpout
- Bothrocara nyx
- Bothrocara pusillum - Alaska eelpout
- Bothrocara soldatovi
- Bothrocara tanakae
Notes
- Froese, R. and D. Pauly, Eds. Bothrocara. FishBase. 2013.
gollark: Probably. The main issue I can see is that you would have to rewrite the entire metadata block on changes, because start/end in XTMF are offsets from the metadata region's end.
gollark: I thought about that, but:- strings in a binary format will be about the same length- integers will have some space saving, but I don't think it's very significant- it would, in a custom one, be harder to represent complex objects and stuff, which some extensions may be use- you could get some savings by removing strings like "title" which XTMF repeats a lot, but at the cost of it no longer being self-describing, making extensions harder and making debugging more annoying- I am not convinced that metadata size is a significant issue
gollark: I mean, "XTMF with CBOR/msgpack and compression" was being considered as a hypothetical "XTMF2", but I'd definitely want something, well, self-describing.
gollark: Also also, why a binary format?
gollark: Also, XTMF can do runtime update, you just need to allocate, say, 4KB at the start of the tape, and write metadata to that. The offsets might be fiddly, though.
References
- "Bothrocara". Integrated Taxonomic Information System. Retrieved 6 June 2006.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.