[Taxacom] the hurdle for all biodiv informatics initiatives
RichardsK at landcareresearch.co.nz
Thu Feb 18 13:09:29 CST 2010
This is great Rich. A fantastic description of the GNUB, etc.
This sort of description should be documented on a wiki/web somewhere (GlobalNames.org?) - is it?
From: taxacom-bounces at mailman.nhm.ku.edu [mailto:taxacom-bounces at mailman.nhm.ku.edu] On Behalf Of Richard Pyle
Sent: Thursday, 18 February 2010 10:33 p.m.
To: 'Doug Yanega'; TAXACOM at MAILMAN.NHM.KU.EDU
Subject: Re: [Taxacom] the hurdle for all biodiv informatics initiatives
I started writing a reply to this, but it ended up being WAY too long (and I
was only about 1/4 done writing what I intended to write). Suffice it to
say that there are MANY issues here, and it would take a long time to write
(and read) an adequate response to all of them.
So here's the highly abridged reply to Doug's post:
> In *principle*, there should be one-to-many mapping (and,
> unless I'm mistaken, the informatics people intend it to work
> this way) - and, as such, it WOULD be useful. In Wolfgang's
> original example, that would mean all six of the known
> combinations used historically for Cyclotrachelus sodalis
> would have the SAME LSID; that way (for example), any
> hyperlinked text version of any of those six names would link
> to the same record in any particular taxon registry, even if
> different registries used different names (as might well be
> the case for a group such as butterflies, where multiple
> authorities may differ on generic placement).
I would agree with you in the context of ZooBank, where each LSID represents
a Nomenclatural Act (in this case, the Act that establishes the species
epithet "sodalis" as a Code-compliant species-group name). This is what we
are calling a "Protonym" (similar in concept to a botanical basionym, but
broader in scope, and slightly different in other ways).
But in the case of uBio (and GNI, and others), LSIDs (and/or other GUIDs)
are intended to represent other "things" -- such as variations on text
strings purported to represent taxon names (with or without authorship
information). If that's the item you want to identify, then it's perfectly
appropriate to have a different GUID (e.g., LSID) assigned to each text
string. (There are other issues about assigning GUIDs to text strings --
and I actually agree there is potential for superfluous identifiers -- but
that's another topic for another post).
Other taxon data managers (e.g., CoL) need GUIDs to represent taxon concepts
-- which are neither text strings nor protonyms. In fact, there are dozens
of different meanings of the notion of a "taxon name" -- which is part of
the reason why conversations of this sort are always so confusing (and
frustrating -- especially for those of us who have been having such
conversations for multiple decades).
So....how can we ever achieve any sort of community standard if some people
want to represent text strings via GUIDs; others want to represent Protonyms
via GUIDs, others want to represent taxon concepts via GUIDs, and so on and
Well....Paul Kirk already hinted at the answer (and so did I). Last week
there was a meeting in Santa Cruz to discuss the Global Names Usage Bank
(GNUB), which is part of the emerging "Global Names Architecture" (GNA).
Another part of the GNI is the Global Names Index (GNI). Most of the Axis
of Evil (GBIF, EoL, ALA, etc.) were represented, and we all felt it was an
extremely productive gathering. With luck, there will be a public report
and a bunch of other detailed documentation forthcoming.
It would take several large emails to explain what GNUB is all about, but
I'll provide a quick synopsis here. You can see more at these two URLs:
In a nutshell: The "least common denominator" for all of these variant
taxonomic objects (text strings and their myriad variations, protonyms and
other Code-governed nomenclatural acts, taxon concept definitions, etc.,
etc., etc.) is what we're somewhat awkwardly referring to as a "Taxon Name
Usage" (TNU). It's not complicated -- the idea is to build an index of all
occurrences where people have documented a taxon name in some form or
another. The documentation source is most often a publication, but it could
also be a database, personal correspondence, field notebook, and many, many
other forms. A small subset of these TNU instances represent Code-governed
Acts (and, hence, the foundational units for nomenclators such as ZooBank
and other zoological nomenclators, Index Fungorum, IPNI, etc.). Other
subsets represent taxon concept definitions. Basically, almost anything you
want to reference in the world of taxonomy exists through one or more TNU
instances. Dave Remsen refers to these TNUs as the "Atoms" of taxonomy --
the basic, high-resolution building blocks of the much more complex
"molecules" of taxonomic revisions and checklists and so on.
The idea with GNUB is to build a simple, common, shared, open-access index
of all TNUs, and assign GUIDs to them. These GUIDs could then be
cross-linked (in ways somewhat analogous to what Rod described for
CrossRef). Ultimately, this would allow for one-click jumps from (say), an
EoL page, to a CoL taxon concept definition, to a ZooBank name registration
record, to a BHL page image of the original description, to listing of all
taxonomic treatments of that name (including all synonyms and spelling
variations), to an index of all specimens identified as any subset of those
synonyms, to a global distribution map ...and on and on and on. Because it
will be open-access and shared, if I enter a new record in my copy in
Hawaii, a taxonomist in India will have access to that information almost
immediately. When someone corrects an error in Australia, someone else will
have access to that correction in France. In short: electronic taxonomic
You haven't heard much about GNA/GNUB/GNI/etc. because it's mostly been just
a Good Idea, with only rudiments of implementation. But as the Axis of Evil
increasingly gets behind it, some of those dollars stolen from primary
taxonomy (yeah, right....) will be put into developing rich content and
services for this Global Names Architecture. The more people begin to
understand what it's all about, them more they think it's a Good Idea. The
more who play, the more effective it becomes. Contrary to some
misconceptions, it is most definitely *NOT* "yet another taxonomic
database". Rather, it is the glue that will allow all the various existing
databases to interlink with each other seamlessly. It is analogous in many
ways to the function on DNS in making the internet work.
Believe it or not, that's the SHORT explanation.
But getting back to Doug's post:
> This would help non-specialists make sense out of situations
> where a single taxon has appeared historically under a
> variety of names.
Yup, GNUB will definitely do that (and much more).
> If, as in Wolfgang's example, a single taxon with multiple
> names (objectively speaking, as in "based unambiguously on
> the same type specimen," and not subjective synonymies) is
> being given multiple LSIDs on TOP of the multiple names, then
> - unless I have misunderstood the purpose of LSIDs - I think
> something is being done incorrectly.
It's not so much that you've misunderstood the purpose of LSIDs (they are
just one kind of identifier, that can be, and have been, used to identify
all sorts of digital and real-world objects of relevance to Life Sciences).
But rather, you seem to have a very narrow scope of what we in the taxonomic
community need to apply GUIDs to. As I said, the
one-identifier-per-name-unit approach you describe is very-much what
nomenclators do, but that's only one part of the much broader applications
of electronic information as used in taxonomy.
> Given that ubio seems to have generated the majority of the
> 18 LSIDs for C. sodalis, maybe someone like Rod Page can
> clarify what, exactly, is happening here - if it is indeed a
> problem, or if there's something that is not immediately
> evident that can make this all make sense.
As I said, in the case of uBio (and GNI), the unit being indexed is the text
string. Many people misunderstand why it's important to do this.
Basically, it's a necessary step to bridge the vast quantities of data and
other information labeled by a HUGE morass of
text-strings-purported-to-represent-taxon-names, which exist (again, as Dave
Remsen likes to say) "in the wild". That is, in scanned literature, in
databases, on Museum specimen labels, etc., etc. Many taxonomists would
like all this taxonomic/nomenclatural "noise" to just "go away" -- and
certainly it's important to *not* perpetuate or amplify the noise. But to
discard all of the noise would also discard all the sea of information that
is labeled with the noise -- and frankly, in my experience, the vast
majority of information important to taxonomy involves an enormous amount of
this noise. As distasteful as the messy noise is to look at with our
taxonomist eyeballs, it's absolutely necessary to index it if we ever want
to clean it up.
So...that is the highly abridged version of what I was planning to post.....
Richard L. Pyle, PhD
Database Coordinator for Natural Sciences
and Associate Zoologist in Ichthyology
Department of Natural Sciences, Bishop Museum
1525 Bernice St., Honolulu, HI 96817
Ph: (808)848-4115, Fax: (808)847-8252
email: deepreef at bishopmuseum.org
Taxacom Mailing List
Taxacom at mailman.nhm.ku.edu
The Taxacom archive going back to 1992 may be searched with either of these methods:
Or (2) a Google search specified as: site:mailman.nhm.ku.edu/pipermail/taxacom your search terms here
Please consider the environment before printing this email
Warning: This electronic message together with any attachments is confidential. If you receive it in error: (i) you must not read, use, disclose, copy or retain it; (ii) please contact the sender immediately by reply email and then delete the emails.
The views expressed in this email may not be those of Landcare Research New Zealand Limited. http://www.landcareresearch.co.nz
More information about the Taxacom