<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=iso-8859-1">
<meta name="Generator" content="Microsoft Word 12 (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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
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;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Times New Roman","serif";
color:#002060;
font-weight:normal;
font-style:normal;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
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="color:#002060">As I said, if DwC has to stay flat, the only way is to add the various typification events in a remark field, unless there is duplication of spm record with one identification per record, but I suppose nobody
wants that.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#002060">And then hoping that you can find the specimen by querying through a synonymy system, either developed by the user itself, of by the queried system, e.g., GBIF, eventually through GNA (?).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#002060"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#002060">BW<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#002060">Nicolas.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#002060"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<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""> tdwg-content-bounces@lists.tdwg.org [mailto:tdwg-content-bounces@lists.tdwg.org]
<b>On Behalf Of </b>Richard Pyle<br>
<b>Sent:</b> Wednesday, 2013 December 04 8:20 PM<br>
<b>To:</b> 'Gregor Hagedorn'<br>
<b>Cc:</b> 'TDWG Content Mailing List'<br>
<b>Subject:</b> Re: [tdwg-content] New Term Request - typifiedName<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">Yes, I understand that – as I mentioned. But what about my question regarding the same specimen being used to typify multiple taxa?<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:0cm 0cm 0cm 4.0pt">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<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""> Gregor Hagedorn [<a href="mailto:gregor.hagedorn@mfn-berlin.de">mailto:gregor.hagedorn@mfn-berlin.de</a>]
<br>
<b>Sent:</b> Wednesday, December 04, 2013 7:16 PM<br>
<b>To:</b> Richard Pyle<br>
<b>Cc:</b> John R. Wieczorek; TDWG Content Mailing List<br>
<b>Subject:</b> Re: [tdwg-content] New Term Request - typifiedName<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">I endorse Markus proposal enthusiastically.<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">What Rich writes is appropriate if you use DwC in a structured way, with Identification instances that support a 1:n relation between specimen and identification instances. However, this cannot be assumed for all uses of DwC.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Gregor<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On 4 December 2013 11:51, Richard Pyle <<a href="mailto:deepreef@bishopmuseum.org" target="_blank">deepreef@bishopmuseum.org</a>> wrote:<o:p></o:p></p>
<p class="MsoNormal">Hmmm.....<br>
<br>
This is the reason that typeStatus was included in the Identification class<br>
-- so that it always is associated with both a specimen (manifest as an<br>
occurrence), and to a taxon (name) -- to which the specimen is Identified.<br>
This is in keeping with what the concept of a "type specimen" really is --<br>
that is, a specimen is not a type inherently, but rather a specimen is<br>
*designated* as a type by someone at some time, via an Identification<br>
instance.<br>
<br>
Of course, because DwC classes are not really intended to be used in an<br>
ontological sense, and because most Museums put their "typeStatus" field in<br>
their specimen table (rather than in an Identification table), I can<br>
certainly understand the need for this proposed new term.<br>
<br>
I guess my main concern/question is: how to deal with specimens that<br>
represent types of more than one name? (not common, but not necessarily an<br>
Edge-case either)<br>
<br>
Aloha,<br>
Rich<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><br>
> -----Original Message-----<br>
> From: <a href="mailto:tdwg-content-bounces@lists.tdwg.org" target="_blank">tdwg-content-bounces@lists.tdwg.org</a> [mailto:<a href="mailto:tdwg-content-" target="_blank">tdwg-content-</a><br>
> <a href="mailto:bounces@lists.tdwg.org" target="_blank">bounces@lists.tdwg.org</a>] On Behalf Of John Wieczorek<br>
> Sent: Wednesday, December 04, 2013 4:13 AM<br>
> To: TDWG Content Mailing List<br>
> Subject: [tdwg-content] New Term Request - typifiedName<br>
><br>
> Dear all,<br>
><br>
> This message is to open public commentary on a request for a new term,<br>
> typifiedName, submitted by Markus Döring to the Darwin Core issue tracker<br>
> at <a href="https://code.google.com/p/darwincore/issues/detail?id=197" target="_blank">
https://code.google.com/p/darwincore/issues/detail?id=197</a>.<br>
> The justification given for inclusion of the term is:<br>
><br>
> "Clear separation of the type status and the typified scientific name that<br>
is<br>
> typified by a type specimen, the subject. Looking at how dwc:typeStatus<br>
has<br>
> been used in all of GBIFs specimen data one can see there is the need to<br>
> express this, but it should better be handled with a term on its own and<br>
> leave typeStatus for the status of the type only. The term name itself is<br>
also<br>
> used by ABCD:<br>
> <a href="http://wiki.tdwg.org/twiki/bin/view/ABCD/AbcdConcept0603" target="_blank">
http://wiki.tdwg.org/twiki/bin/view/ABCD/AbcdConcept0603</a>."<br>
><br>
> The proposal is as follows:<br>
><br>
> Definition:<br>
> The scientific name that is based on the type specimen.<br>
><br>
> Comment:<br>
> It is recommended to also indicate the typeStatus of the specimen.<br>
><br>
> Refines:<br>
><br>
> Has Domain:<br>
><br>
> Has Range:<br>
><br>
> Replaces:<br>
><br>
> ABCD 2.06:<br>
> DataSets/DataSet/Units/Unit/SpecimenUnit/NomenclaturalTypeDesignation<br>
> s/NomenclaturalTypeDesignation/TypifiedName<br>
> _______________________________________________<br>
> tdwg-content mailing list<br>
> <a href="mailto:tdwg-content@lists.tdwg.org" target="_blank">tdwg-content@lists.tdwg.org</a><br>
> <a href="http://lists.tdwg.org/mailman/listinfo/tdwg-content" target="_blank">http://lists.tdwg.org/mailman/listinfo/tdwg-content</a><br>
<br>
_______________________________________________<br>
tdwg-content mailing list<br>
<a href="mailto:tdwg-content@lists.tdwg.org" target="_blank">tdwg-content@lists.tdwg.org</a><br>
<a href="http://lists.tdwg.org/mailman/listinfo/tdwg-content" target="_blank">http://lists.tdwg.org/mailman/listinfo/tdwg-content</a><o:p></o:p></p>
</div>
</div>
</div>
<p class="MsoNormal"><br>
<br clear="all">
<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">-- <o:p></o:p></p>
<div>
<p class="MsoNormal">-- <br>
<br>
---------------------------------<br>
Dr. Gregor Hagedorn<br>
Head of Digital World<br>
Museum für Naturkunde<br>
Leibniz-Institut für Evolutions- und Biodiversitätsforschung<br>
Invalidenstrasse 43, 10115 Berlin <br>
<a href="tel:%2B49%20%280%2930%202093%208576" target="_blank">+49 (0)30 2093 8576</a> (work)<br>
<a href="tel:%2B49-%280%2930-831%205785" target="_blank">+49-(0)30-831 5785</a> (private)<br>
<a href="mailto:gregor.hagedorn@mfn-berlin.de" target="_blank">gregor.hagedorn@mfn-berlin.de</a><br>
<a href="http://www.naturkundemuseum-berlin.de" target="_blank">http://www.naturkundemuseum-berlin.de</a><br>
<a href="http://linkedin.com/in/gregorhagedorn" target="_blank">http://linkedin.com/in/gregorhagedorn</a><br>
<br>
This communication, together with any attachments, is intended only for the person(s) to whom it is addressed. Redistributing or publishing it without permission may be a violation of copyright or privacy rights.<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>