<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:"Trebuchet MS";
panose-1:2 11 6 3 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
code
{mso-style-priority:99;
font-family:"Courier New",serif;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New",serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Courier New",serif;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">I am trying to answer two questions in this tread.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Taxonx.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Chuck asked about TaxonX. We are moving away from TaxonX to use an archival version of TaxPuB, TaxPub-green (<a href="https://github.com/plazi/TaxPubJATS-green">https://github.com/plazi/TaxPubJATS-green</a>
), which is related to TaxPub that Pensoft already uses for the publishing, and which is based on NLM JATS, that is a widely used “standard” albeit in different flavors. But to have all based on JATS-TaxPub makes it easier to make use of legacy (articles converted
into TaxPub) and prospective (born digital based on TaxPub) articles. Once we have this move finished we will release and note and explain in detail. But in brief, let’s focus on TaxPub.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Taxonomic names<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">For our work with taxonomic publications we tag all scientific taxonomic names we discover in the articles. Our main focus are names for which a taxonomic treatment is provided
in the respective article, or which are cited as a reference to an earlier usage and with that a taxonomic treatment.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">As an example: </span><u><span style="font-size:10.5pt;font-family:"Trebuchet MS",sans-serif;color:#333333;background:white"><a href="http://treatment.plazi.org/id/87F5BDFA-6C63-C7B7-4A85-A1B39AE6CACE">http://treatment.plazi.org/id/87F5BDFA-6C63-C7B7-4A85-A1B39AE6CACE</a>
</span></u><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Agosti (1990) provides a treatment of Catagylphis turcomanicus (Emery). He cites all the earlier usages of this name, beginning from the protonym to all the latter changes
in combination.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">With that he says, that under this understanding of this taxon, he subsumes all the earlier name usages. He does this by citing them. A visualization is provided on the right
hand und “taxonomy”<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">A more recent example is this crab:
</span><u><span style="font-size:10.5pt;font-family:"Trebuchet MS",sans-serif;color:#333333;background:white"><a href="http://treatment.plazi.org/id/F017F605-AC1E-BB43-FF2A-90F9555CF9CD">http://treatment.plazi.org/id/F017F605-AC1E-BB43-FF2A-90F9555CF9CD</a><o:p></o:p></span></u></p>
<p class="MsoNormal"><u><span style="font-size:10.5pt;font-family:"Trebuchet MS",sans-serif;color:#333333;background:white"><o:p><span style="text-decoration:none"> </span></o:p></span></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">This treatmentCitation allows us to build a citation graph which is specific in a sense that this type of taxonomic names have a relationship to an earlier specified usage.
Whilst names that are found in the next have this relationship implicit, known probably to the author in most cases, and few exceptional cases to a community that maintains a name server including the currently accepted name (and then there the history that
eventually leads to the protonym, such as is the case for ants (and mony more hymenoptera) on the Hymenopter Name Server). But this is a discussion in itself.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">In Taxpub this is dealt with (somewhat cryptic)
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal" style="background:#F7F7F7"><span style="font-size:10.0pt;font-family:Consolas;color:#333333;border:none windowtext 1.0pt;padding:0in"><nomenclature-citation-list><o:p></o:p></span></p>
<p class="MsoNormal" style="background:#F7F7F7"><span style="font-size:10.0pt;font-family:Consolas;color:#333333;border:none windowtext 1.0pt;padding:0in"> <nomenclature-citation><o:p></o:p></span></p>
<p class="MsoNormal" style="background:#F7F7F7"><span style="font-size:10.0pt;font-family:Consolas;color:#333333;border:none windowtext 1.0pt;padding:0in"> </nomenclature-citation><o:p></o:p></span></p>
<p class="MsoNormal" style="background:#F7F7F7"><span style="font-size:10.0pt;font-family:Consolas;color:#333333;border:none windowtext 1.0pt;padding:0in"> <nomenclature-citation><o:p></o:p></span></p>
<p class="MsoNormal" style="background:#F7F7F7"><span style="font-size:10.0pt;font-family:Consolas;color:#333333;border:none windowtext 1.0pt;padding:0in"> </nomenclature-citation><o:p></o:p></span></p>
<p class="MsoNormal" style="background:#F7F7F7"><span style="font-size:10.0pt;font-family:Consolas;color:#333333;border:none windowtext 1.0pt;padding:0in"> </nomenclature-citation-list></span><span style="font-size:10.0pt;font-family:Consolas;color:#333333"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">See
<a href="https://htmlpreview.github.io/?https://raw.githubusercontent.com/tcatapano/TaxPub/master/documentation/tp-nomenclature-citation-list.html">
https://htmlpreview.github.io/?https://raw.githubusercontent.com/tcatapano/TaxPub/master/documentation/tp-nomenclature-citation-list.html</a>
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">In RDF we make use of CITO (</span><span style="font-size:10.0pt;font-family:"Courier New",serif;color:#1A1AA6">http://purl.org/spar/cito/) to model this relationship</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><a href="https://github.com/plazi/TreatmentOntologies">https://github.com/plazi/TreatmentOntologies</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">and here an example<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><a href="http://tb.plazi.org/GgServer/rdf/87F5BDFA6C63C7B74A85A1B39AE6CACE">http://tb.plazi.org/GgServer/rdf/87F5BDFA6C63C7B74A85A1B39AE6CACE</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Donat<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> tdwg-content [mailto:tdwg-content-bounces@lists.tdwg.org]
<b>On Behalf Of </b>Richard Pyle<br>
<b>Sent:</b> Wednesday, April 20, 2016 12:30 AM<br>
<b>To:</b> 'Nico Franz' <nico.franz@asu.edu><br>
<b>Cc:</b> tdwg-content@lists.tdwg.org; vocab@noreply.github.com; 'Michael Rosenberg (Faculty)' <msr@asu.edu><br>
<b>Subject:</b> Re: [tdwg-content] Taxonomic name usage files<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Good questions! Note that the stuff I was describing isn’t just GNUB; it’s embedded in the DwC terms as well. And the few elements that are missing from DwC
are embedded in TCS. The main other aspects are the Reference metadata (the ill-fated TDWG Reference standard; now looking towards NLMS), and Agents (most people I know follow FOAF). Other than those, the main missing holes (in both GNUB and DwC) are the
Appearance stuff, and perhaps a more robust approach to the relationshipAssertion stuff.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Maybe a task for TCS 2.0?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Once the standards fleshed out, I imagine the way to implement this stuff in new literature is via something along the lines of Pensoft’s PWT (now arpha):
<a href="http://arpha.pensoft.net/">http://arpha.pensoft.net/</a> The natural group to focus on this would be PLAZI, which has been going gangbusters in recent months on capturing structured treatments from existing literature. [Pssst… Donat…. That’s your
cue….]<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Rich<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif"> Nico Franz [<a href="mailto:nico.franz@asu.edu">mailto:nico.franz@asu.edu</a>]
<br>
<b>Sent:</b> Tuesday, April 19, 2016 11:58 AM<br>
<b>To:</b> Richard Pyle<br>
<b>Cc:</b> Gaurav Vaidya; greg whitbread; <a href="mailto:tdwg-content@lists.tdwg.org">
tdwg-content@lists.tdwg.org</a>; <a href="mailto:vocab@noreply.github.com">vocab@noreply.github.com</a>; Michael Rosenberg (Faculty)<br>
<b>Subject:</b> Re: [tdwg-content] Taxonomic name usage files<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Thanks, Rich, for catching me up.<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"> So then if we can apparently cover a good bit of ground (with what I assume you'd call a "smart [or the only] way of implementing GNUB"), this does raise the question of how to bring this as close as possible to the peer-review/publication
process where an author team may be motivated to express their intentions related to name usages in various explicit, structurally recorded ways.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Best, Nico<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Tue, Apr 19, 2016 at 2:09 PM, Richard Pyle <<a href="mailto:deepreef@bishopmuseum.org" target="_blank">deepreef@bishopmuseum.org</a>> wrote:<o:p></o:p></p>
<p class="MsoNormal">> 1. Given a multitude of well established and precise historical name usages, I explicitly don't want to commit to one in particular<br>
> that my present usage is congruent with, or not. (Indeed, I kind of think this is what the name withOUT a sec. does, "explicitly").<br>
<br>
Yes! Exactly!<br>
<br>
> I choose to be vague - any past usage is ok with me, here.<br>
<br>
During the TCS days, this is what we referred to as a "Nomenclatural Concept", which is roughly the sum/average of all historical treatments, more or less (ambiguity and vagueness deliberate/intentional).<br>
<br>
> I think we can presently model the vagueness (by integrating on the strings alone), but not the deliberateness thereof (in contrast to other situations where vagueness is not intended)?<br>
<br>
Yes - a TNU without any relationshipAssertions. Basically, the only implied associations with other TNUs is via the Protonym link (i.e., a Nomenclatural Assertion).<br>
<br>
> 2. Franz. 2010. Revision of Apotomoderes (Insecta: Coleoptera). => Actually, "Insecta" here is more of a social concession to an outdated data filing paradigm than<br>
> a claim to an active speaker role (related to name usages that I actually care about). I am not intending to apply my taxonomic expertise to "Insecta";<br>
> that is *out of scope* (though the string is being written).<br>
<br>
So... in that case, the question is whether to represent "Insecta" as used in Franz 2010 as a scientific name, or vernacular name (two different ways of modelling names, as the latter do not have structured Codes). Even if you fall on the side of using it
as a scientific (taxon) name, you can still create a TNU for it. In the spirit of Walter's pioneering work on this stuff, TNUs only represent "potential" taxa.<br>
<br>
Aloha,<br>
Rich<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>