<!doctype html public "-//W3C//DTD W3 HTML//EN">
<html><head><style type="text/css"><!--
blockquote, dl, ul, ol, li { padding-top: 0 ; padding-bottom: 0 }
--></style><title>Re: GUIDs for Taxon Names and Taxon
Concepts</title></head><body>
<div>Dear Roger,</div>
<div><br></div>
<div>One puzzling thing for me to be explained in more detail is the
following:</div>
<div><br></div>
<div>Extending the example of Richard:</div>
<div><br></div>
<div>1. Aus Smith 1995<br>
2. Xea Jones 2000<br>
3. Aus bus Smith 1995</div>
<div>4. Xea bus (Smith 1995) Jones 2000</div>
<div>5. Xea ba (Smith 1995) Jones 2000</div>
<div>6. Xea bus (Smith 1995) Jones 2000 as it appears in Pyle
2005</div>
<div> = Xea ba (Smith 1995) Jones 2000</div>
<div><br></div>
<div>I agree with Richard that it is ambiguous whether nos 4 & 5
should get TaxonName</div>
<div>GUIDs or TaxonConcept GUIDs, but I believe this is a matter of
defintion we can solve.</div>
<div><br></div>
<div>However, how to discriminate between the TaxonConcept of no. 4
and the TaxonConcept of no. 6 which includes subjective synonymy? I
assume you need a GUID for each documentable usage instance?</div>
<div><br></div>
<div>Kind regards,</div>
<div><br></div>
<div>Yde</div>
<div><br></div>
<div><br></div>
<hr>
<div><br></div>
<div><br></div>
<blockquote type="cite" cite>Hi Rich,<br>
<br>
So you define a NameUsage as:</blockquote>
<blockquote type="cite" cite><tt>"Any occurrence of a NameString
as it appears or is explicitly implied<br>
within some form of static documentation."</tt></blockquote>
<blockquote type="cite" cite>Let us explore this definition! Picking a
volume almost at random (I like the cover) I chose Porley &
Hodgett (2005)<i> Mosses & Liverworts.</i><br>
<br>
<a
href="http://www.tdwg.hyam.net/images/bryo_01.jpg"
>http://www.tdwg.hyam.net/images/bryo_01.jpg</a><br>
<br>
and picking a page at random - in this case 136<br>
<br>
<a
href="http://www.tdwg.hyam.net/images/bryo_02.jpg"
>http://www.tdwg.hyam.net/images/bryo_02.jpg</a><br>
<br>
So we have a 'static' document and it is chuck full of NameStrings. I
have circled some of them.<br>
<br>
We have<i> Ditrichum cornubicum</i> (a red data book moss). It is
mentioned, with a picture on the previous page and at the top of this
page it is mentioned a few more times. Further down this page we
have<i> Buxbaumia aphylla</i> which is also mentioned twice. There is
a picture of it on the next page.<br>
<br>
So how many name usages do we have here? There seem to be loads.<br>
</blockquote>
<blockquote type="cite" cite>
<ul>
<li>Does each mention of the name on the page count as a usage? -
would seem to be a silly thing to do.
<li>Does mentioning the name on different pages mean different usages?
- would also be silly but we don't have anyway to judge (different
pages within a journal or combined work for example?)
<li>How about same page but different context? The picture may be of a
different moss to the one that they mention in the text.
<li>If a subspecies is mentioned does that count as a usage of the
specific name (it has been used) and likewise a binomial implies a
usage of the genus name.
<li>There are around 1100 species mentioned in this publication. They
are probably mentioned on average 3 times each (a guess) so that is
3300 new name usages. Plus they are all binomials or subspecific names
so double that for the different usages or genera etc. So 6,600 name
usages in this volume. I wonder how many publications like this come
out a year globally?</ul>
</blockquote>
<blockquote type="cite" cite>I really can't see how one would apply
your definition. Perhaps if you restricted it to taxonomic works but
then you have to define a taxonomic work and you are still limited to
how it has to be stated to act as a 'usage'. It certainly isn't clear
to me.<br>
<br>
We can easily define what a TaxonConcept is because it implies<b>
intent</b>. If I want to create an object that I want you to refer to
as a definition of a taxon then I am creating a TaxonConcept and
should issue a GUID to make it easy for you to refer to it. If not
then I shouldn't bother. If I want to use the services of a
nomenclator to define the publication and typification of the name I
am using then I can use a TaxonName GUID within my definition - but I
don't have to. I can't see how that can be any simpler than
that.<br>
<br>
Porley & Hodgetts (2005) have no intension whatsoever of
'committing' nomenclatural acts or of defining any taxa that people
will later refer to. They are simple<b> referring</b> to existing
concepts. Yet by your definition they have created over 6k name usages
that a diligent publisher might issue GUIDs for.<br>
<br>
Have I completely misinterpreted you definition? If so could you
define it a little tighter? If you imply that the author has to have
meant to describe something then you are just creating the
TaxonConcept definition I am working with here. How else can you
subset all the times names appear in print?</blockquote>
<blockquote type="cite" cite><br>
This is all great fun but we do need to nail it down and move on.<br>
<br>
All the best,<br>
</blockquote>
<blockquote type="cite" cite>Roger<br>
</blockquote>
<blockquote type="cite" cite>
<hr></blockquote>
<blockquote type="cite" cite><br>
<blockquote type="cite" cite><tt>Hi Roger,</tt></blockquote>
<blockquote type="cite" cite><tt><br></tt>
<blockquote type="cite" cite><tt>Could you attempt a concise
definition of a</tt></blockquote>
<blockquote type="cite" cite><tt>UsageInstance we can all agree on
then :)</tt></blockquote>
</blockquote>
<blockquote type="cite" cite><tt><br>
Sure: Any occurrence of a NameString as it appears or is explicitly
implied<br>
within some form of static documentation.<br>
<br>
"NameString" refers to a string of textual characters meant
to represent a<br>
name of biological organisms. This can be defined more
restrictively to<br>
"ScientificNameString" (names that conform to one of a
designated set of<br>
nomenclatural Codes), or more broadly to include vernacular
NameStrings.<br>
<br>
"static documentation" can be defined broadly, to include
publications,<br>
databases, and any other form of documented medium of human
communication.<br>
The "static" part means that it must represent a snapshot in
time. In the<br>
case of dynamic databases, this would require a "date stamp"
for each<br>
UsageInstance -- either for an individual record, or for a snapshot of
the<br>
entire dataset.<br>
<br>
The "explicitly implied" part addresses zoological-style
nomenclatural<br>
listings along the lines of what Yde has sent to this list, where a
genus is<br>
listed once as a header, and species epithets are enumerated
below,<br>
explicitly implying a series of binomials, even if they are not
actually<br>
printed on papaer as such.<br>
<br>
The point is, the definition is highly flexible, yet mostly
unambiguous<br>
(assuming sufficient metadata for identifying a documentation
instance).<br>
<br>
I think it only makes informatic sense to distinguish two "kinds"
of GUID<br>
for taxonomic objects if the distinction between the objects is
unambiguous.<br>
Given these NameStrings:<br>
<br>
1. Aus Smith 1995<br>
2. Xea Jones 2000<br>
3. Aus bus Smith 1995<br>
4. Xea bus (Smith 1995) Jones 2000<br>
5. Xea ba (Smith 1995) Jones 2000<br>
<br>
It is ambiguous whether there are three, four, or five distinct
NameObjects<br>
represented (i.e., it is ambiguous whether #s 4 & 5 should get
TaxonName<br>
GUIDs, or TaxonConcept GUIDs via SEC instances).<br>
<br>
However, given this list:<br>
<br>
1. "Aus" as it appears in Smith 1995<br>
2. "Xea" as it appears in Jones 2000<br>
3. "Aus bus" as it appears in Smith 1995<br>
4. "Xea bus" as it appears in Jones 2000<br>
5. "Xea" as it appears in Pyle 2005<br>
6. "Xea ba" as it appears in Pyle 2005<br>
7. "Xea" as it appears in ITIS Nov. 11, 2005 snapshot
dataset<br>
8. "Xea bus" as it appears in ITIS Nov. 11, 2005 snapshot
dataset<br>
9. "Xea ba" as it appears in ITIS Nov. 11, 2005 snapshot
dataset<br>
<br>
There is very little ambiguity that each item in this list gets its
own<br>
GUID. Until a universal definition of a "NameObject"
emerges, certain usage<br>
instances can serve as surrogates for basionyms (1, 2, 3), or
botanical new<br>
combinations (4), or TaxonConcepts (1-6) -- in whatever way that a
data<br>
manager needs or wishes to establish linkages among GUIDs (e.g.,
linking #s<br>
4, 6, 8 & 9 to #3 via "is basionym of"; or linking #s 4,
6, 8 & 9 to #2 via<br>
"is combined with"; or linking #5 to #6, #2 to #4, and #1 to
#3 via<br>
"contains").<br>
<br>
Several people have expressed a desire for "simple" and
"flexible", and I<br>
think this approach maximizes both.<br>
<br>
Aloha,</tt></blockquote>
<blockquote type="cite" cite><tt>Rich</tt></blockquote>
</blockquote>
</body>
</html>