<div dir="ltr">Dear Donald,<div>that's a fantastic manifesto and challenge.</div><div><br></div><div>In discussions over DwC changes for invasive species the lack of understanding on the uses of DwC and its fields was evident. In this light, Donald's wishlist to find a balance between human and computer usability seems very sensible. The lack of knowledge in the community is not the fault of DwC, but if DwC field names and vocabularies were more adopted within collection databases and other software understanding would improve.</div><div><br></div><div>A common problem of understanding was DwC's usage for checklists, as opposed to observations and specimens. These different perspectives give different meanings to fields. For example, occurrenceStatus make sense from the perspective of a checklist, but one could easily imagine it being competed by a diligent researcher for a specimen where is has ambiguous meaning.</div><div><br></div><div>Regarding what workshops might be needed, I'll leave this to the TDWG people, but I'm certainly trying to get to the annual TDWG conference this year and I hope some of this can be discussed there.</div><div><br></div><div>Regards</div><div>Quentin</div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><br></div><div><br></div><div>Dr. Quentin Groom</div><div>(Botany and Information Technology)</div><div><br></div><div>Botanic Garden Meise</div><div>Domein van Bouchout</div><div>B-1860 Meise</div><div>Belgium</div><div><br></div><div><a href="http://orcid.org/0000-0002-0596-5376" target="_blank">ORCID: 0000-0002-0596-5376</a></div><div><br></div><div>Landline; +32 (0) 226 009 20 ext. 364</div><div>FAX: +32 (0) 226 009 45</div><div><br></div><div>E-mail: <a href="mailto:quentin.groom@plantentuinmeise.be" target="_blank">quentin.groom@plantentuinmeise.be</a></div><div>Skype name: qgroom</div><div>Website: <a href="http://www.botanicgarden.be" target="_blank">www.botanicgarden.be</a></div><div><br></div></div></div></div></div></div></div></div>
<br><div class="gmail_quote">On 27 May 2016 at 16:28, Donald Hobern <span dir="ltr"><<a href="mailto:dhobern@gbif.org" target="_blank">dhobern@gbif.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-AU" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><a name="m_3604662825080543888__MailEndCompose"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">On behalf of the GBIF Secretariat, I’d like to emphasise our extreme interest in assisting with the next phase in developing
Darwin Core and TDWG standards generally.<u></u><u></u></span></a></p>
<p class="MsoNormal"><span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><u></u> <u></u></span></span></p>
<p class="MsoNormal"><span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Many important points have already been made. Flexibility to accommodate plain text and URIs in the same
fields leaves some problems for data aggregators and users but is clearly the only workable way to enable data publishing from the widest possible range of sources.<u></u><u></u></span></span></p>
<p class="MsoNormal"><span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><u></u> <u></u></span></span></p>
<p class="MsoNormal"><span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">However, I think it is essential that we use this opportunity to revisit the whole architecture of how
we represent share, and use biodiversity data. There are several interconnected aspects that should be included in this debate.<u></u><u></u></span></span></p>
<p class="MsoNormal"><span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><u></u> <u></u></span></span></p>
<p class="MsoNormal"><span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">I take it as a given that our shared vision should include enabling human users and machines to find all
of the information and to traverse all of the data connections that a knowledgeable researcher can see in the biodiversity literature, collections and other resources. By this, I mean that we should be able to start from any point in the biodiversity data
graph and find the meaningful links to associated data objects. From specimen to taxon concept to taxon name to publication; from sequence to associated sequences to taxon concepts to species occurrences; etc., etc.
<u></u><u></u></span></span></p>
<p class="MsoNormal"><span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><u></u> <u></u></span></span></p>
<p class="MsoNormal"><span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">This means that our data architecture needs to pay attention to the following matters (quite independently
of the challenges of delivering the infrastructures that underpin their successful implementation):<u></u><u></u></span></span></p>
<p class="MsoNormal"><span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><u></u> <u></u></span></span></p>
<p><span><span style="font-size:11.0pt;font-family:Symbol">·</span></span><span><span style="font-size:7.0pt">
</span></span><span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Agreement on the set of core data classes within the biodiversity domain which we consider important enough to
standardise (specimen, collection, taxon name, taxon concept, sequence, gene, publication, taxon trait, … - or whatever we all agree).<u></u><u></u></span></span></p>
<p><span><span style="font-size:11.0pt;font-family:Symbol">·</span></span><span><span style="font-size:7.0pt">
</span></span><span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Agreement on the set of core relationships between instances of these classes that we consider important enough
to standardise (specimen identifiedAs taxon concept, taxon name publishedIn publication, etc.).<u></u><u></u></span></span></p>
<p><span><span style="font-size:11.0pt;font-family:Symbol">·</span></span><span><span style="font-size:7.0pt">
</span></span><span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Making sure that our data publishing mechanisms (cores, extensions, etc.) align accurately with these classes
and support these relationships – this mainly means reworking the current confused interplay between cores, DwC classes, use of dcterms:type and use of basisOfRecord – every record should be clearly identified as an instance of a class (or a view of several
linked class instances) and (for the core data classes) this should form the basis for inference and interpretation.<u></u><u></u></span></span></p>
<p><span><span style="font-size:11.0pt;font-family:Symbol">·</span></span><span><span style="font-size:7.0pt">
</span></span><span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">An ongoing process of defining for each core class what properties are mandatory (maybe only: id, class), highly
desirable (depending on the class, things like: decimal coordinates, scientific name, identifiedAs, publishedIn), generally agreed (many other properties for which we have working vocabularies and do not want unnecessary multiplication, e.g.: waterbody, maximumDepthInMeters)
or optional/bespoke (anything else that any data publisher wishes to include). In other words, allow any properties to be shared but ensure that the contours of the data are clear to standard tools.<u></u><u></u></span></span></p>
<p><span><span style="font-size:11.0pt;font-family:Symbol">·</span></span><span><span style="font-size:7.0pt">
</span></span><span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">A set of good examples of datasets mapped into this model, using various serialisations.<u></u><u></u></span></span></p>
<p class="MsoNormal"><span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><u></u> <u></u></span></span></p>
<p class="MsoNormal"><span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">It would be valuable to get a feeling for what workshops might be needed, when might be best to hold them,
and how much funding would be required to ensure the right attendance. GBIF may be able to contribute some of this.<u></u><u></u></span></span></p>
<p class="MsoNormal"><span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><u></u> <u></u></span></span></p>
<p class="MsoNormal"><span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Donald
<u></u><u></u></span></span></p>
<p class="MsoNormal"><span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><u></u> <u></u></span></span></p>
<p class="MsoNormal"><span><span style="font-size:11.0pt;font-family:"Courier New"">----------------------------------------------------------------------<u></u><u></u></span></span></p>
<p class="MsoNormal"><span><span style="font-size:11.0pt;font-family:"Courier New"">Donald Hobern - GBIF Executive Secretary - <a href="mailto:dhobern@gbif.org" target="_blank">dhobern@gbif.org</a><u></u><u></u></span></span></p>
<p class="MsoNormal"><span><span style="font-size:11.0pt;font-family:"Courier New"">Global Biodiversity Information Facility <a href="http://www.gbif.org/" target="_blank">http://www.gbif.org/</a><u></u><u></u></span></span></p>
<p class="MsoNormal"><span><span style="font-size:11.0pt;font-family:"Courier New"">GBIF Secretariat, Universitetsparken 15, DK-2100 Copenhagen Ø, Denmark<u></u><u></u></span></span></p>
<p class="MsoNormal"><span><span style="font-size:11.0pt;font-family:"Courier New"">Tel: <a href="tel:%2B45%203532%201471" value="+4535321471" target="_blank">+45 3532 1471</a> Mob: <a href="tel:%2B45%202875%201471" value="+4528751471" target="_blank">+45 2875 1471</a> Fax: <a href="tel:%2B45%202875%201480" value="+4528751480" target="_blank">+45 2875 1480</a><u></u><u></u></span></span></p>
<p class="MsoNormal"><span><span style="font-size:11.0pt;font-family:"Courier New"">----------------------------------------------------------------------<u></u><u></u></span></span></p>
<p class="MsoNormal"><span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><u></u> <u></u></span></span></p>
<span></span>
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> tdwg-content [mailto:<a href="mailto:tdwg-content-bounces@lists.tdwg.org" target="_blank">tdwg-content-bounces@lists.tdwg.org</a>]
<b>On Behalf Of </b>Lee Belbin<br>
<b>Sent:</b> Friday, 27 May 2016 5:31 AM<br>
<b>To:</b> Quentin Groom <<a href="mailto:quentin.groom@plantentuinmeise.be" target="_blank">quentin.groom@plantentuinmeise.be</a>><br>
<b>Cc:</b> TDWG Content Mailing List <<a href="mailto:tdwg-content@lists.tdwg.org" target="_blank">tdwg-content@lists.tdwg.org</a>></span></p><div><div class="h5"><br>
<b>Subject:</b> Re: [tdwg-content] A proposal to improve Darwin Core for invasive species data<u></u><u></u></div></div><p></p><div><div class="h5">
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">Hi John et al,<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Ditto (to Annie's comment) from me. <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">As most of you know, I have been standing back from TDWG for a few years now, but it has been hard to avoid interest in the development of TDWG's most significant standard. I have been aware of at least three independent suggestions that
are relevant to my interests.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">As from the beginning, the difficulty remains in getting wise heads together (face-to-face) and getting consensus on recommendations in a timely manner. The TDWG meetings are too busy without sufficient time to achieve outcomes. Teleconferencing
is great in theory but hopeless in practice. The only alternative is to find time and $ for dedicated meetings adjacent to, or separate from the TDWG Conference. It has been done before to good effect.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">I raise this as I believe that the time for such a meeting is well and truly here.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Cheers<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Lee<u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal"><br clear="all">
<u></u><u></u></p>
<div>
<div>
<p class="MsoNormal">Lee Belbin<br>
Blatant Fabrications Pty Ltd<br>
Tasmania<u></u><u></u></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">On Thu, May 26, 2016 at 4:04 AM, Quentin Groom <<a href="mailto:quentin.groom@plantentuinmeise.be" target="_blank">quentin.groom@plantentuinmeise.be</a>> wrote:<u></u><u></u></p>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<p class="MsoNormal">I second Annie, this is a real problem in Biodiversity Informatics in general. Unless you can turn maintenance tasks into peer reviewed papers then you get little credit for it.<span><span style="color:#888888"><u></u><u></u></span></span></p>
<div>
<p class="MsoNormal"><span style="color:#888888">Quentin</span><u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal"><br clear="all">
<u></u><u></u></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Dr. Quentin Groom<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">(Botany and Information Technology)<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Botanic Garden Meise<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Domein van Bouchout<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">B-1860 Meise<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Belgium<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal"><a href="http://orcid.org/0000-0002-0596-5376" target="_blank">ORCID: 0000-0002-0596-5376</a><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Landline; +32 (0) 226 009 20 ext. 364<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">FAX: +32 (0) 226 009 45<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">E-mail: <a href="mailto:quentin.groom@plantentuinmeise.be" target="_blank">
quentin.groom@plantentuinmeise.be</a><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Skype name: qgroom<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Website: <a href="http://www.botanicgarden.be" target="_blank">www.botanicgarden.be</a><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<div>
<p class="MsoNormal">On 25 May 2016 at 17:57, John Wieczorek <<a href="mailto:tuco@berkeley.edu" target="_blank">tuco@berkeley.edu</a>> wrote:<u></u><u></u></p>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<p class="MsoNormal">Thanks Annie. I don't plan to give up, it's just that I don't feel I have been doing it justice for a while now.<u></u><u></u></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">On Wed, May 25, 2016 at 12:52 PM, Simpson, Annie <<a href="mailto:asimpson@usgs.gov" target="_blank">asimpson@usgs.gov</a>> wrote:<u></u><u></u></p>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<p class="MsoNormal">Chiming in now, very briefly...<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">John, you are the DwC champion who has kept it moving forward in a comprehensible and useful way. The TDWG community is very grateful for your work on this and I personally hope you don't give up the good fight.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><br clear="all">
<u></u><u></u></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:7.5pt;font-family:"Arial Narrow",sans-serif">Annie Simpson, biologist & information scientist</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:7.5pt;font-family:"Arial Narrow",sans-serif"><a href="http://orcid.org/0000-0001-8338-5134" target="_blank">http://orcid.org/0000-0001-8338-5134</a></span><u></u><u></u></p>
<div>
<p class="MsoNormal"><span style="font-size:7.5pt;font-family:"Arial Narrow",sans-serif">BISON project (<a href="http://bison.usgs.ornl.gov" target="_blank">http://bison.usgs.ornl.gov</a>)</span><u></u><u></u></p>
<div>
<p class="MsoNormal"><span style="font-size:7.5pt;font-family:"Arial Narrow",sans-serif">Core Science Analytics, Synthesis, & Libraries Program</span><u></u><u></u></p>
<div>
<p class="MsoNormal"><span style="font-size:7.5pt;font-family:"Arial Narrow",sans-serif">U.S. Geological Survey, MS 302<br>
12201 Sunrise Valley Drive<br>
Reston, Virginia 20192<br>
=================<br>
<a href="mailto:asimpson@usgs.gov" target="_blank">asimpson@usgs.gov</a><br>
<a href="tel:703.648.4281" target="_blank">703.648.4281</a> desk</span><u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">On Wed, May 25, 2016 at 7:26 AM, John Wieczorek <<a href="mailto:tuco@berkeley.edu" target="_blank">tuco@berkeley.edu</a>> wrote:<u></u><u></u></p>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<p class="MsoNormal">One primary idea behind the BCO is indeed as the proving ground you mention. The challenge is having consistent available resources to do that work. With BCO it could be a particular challenge, I think, since it can cover so much semantic
space. I would love to be in a position to be a proper BCO caretaker, but I have not even been able to do a good job with Darwin Core as it is. <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">On Wed, May 25, 2016 at 2:00 AM, Quentin Groom <<a href="mailto:quentin.groom@plantentuinmeise.be" target="_blank">quentin.groom@plantentuinmeise.be</a>> wrote:<u></u><u></u></p>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<p class="MsoNormal">Interesting! I had not come across Apple Core before. Isn't this proving-ground role something that the Biological Collections Ontology can also do?<u></u><u></u></p>
<div>
<p class="MsoNormal">I like the idea of a Darwin Core with different levels of adherence to rules. I agree that strict enforcement of rules will inhibit the flow of data, but in my own experience there are simple fields that I could have easily completed in
a standardized way, if only I could have found a suitable recommendation to follow. Hierarchical vocabularies are particularly useful here, because they have built in flexibility.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Regards<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#888888">Quentin<u></u><u></u></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><br clear="all">
<u></u><u></u></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Dr. Quentin Groom<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">(Botany and Information Technology)<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Botanic Garden Meise<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Domein van Bouchout<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">B-1860 Meise<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Belgium<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal"><a href="http://orcid.org/0000-0002-0596-5376" target="_blank">ORCID: 0000-0002-0596-5376</a><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Landline; +32 (0) 226 009 20 ext. 364<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">FAX: +32 (0) 226 009 45<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">E-mail: <a href="mailto:quentin.groom@plantentuinmeise.be" target="_blank">
quentin.groom@plantentuinmeise.be</a><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Skype name: qgroom<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Website: <a href="http://www.botanicgarden.be" target="_blank">www.botanicgarden.be</a><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<div>
<p class="MsoNormal">On 25 May 2016 at 03:17, John Wieczorek <<a href="mailto:tuco@berkeley.edu" target="_blank">tuco@berkeley.edu</a>> wrote:<u></u><u></u></p>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<p class="MsoNormal">I think it is indeed worthwhile to have content standards to go with the term definitions. Applce Core (now under renewed development at
<a href="https://github.com/tdwg/applecore" target="_blank">https://github.com/tdwg/applecore</a>) is a good example of this.<u></u><u></u></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">On Tue, May 24, 2016 at 6:16 PM, Chuck Miller <<a href="mailto:Chuck.Miller@mobot.org" target="_blank">Chuck.Miller@mobot.org</a>> wrote:<u></u><u></u></p>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">John,</span><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">It’s interesting how long that text has been out there, and without much comment. It
seems to presume there is a binary situation: tightly controlled vocabulary that is exclusive or loosely controlled that is inclusive. Maybe it’s time now to consider something additional in the middle. We know a lot more about how the Darwin Core standard
is being used, or at least have plenty of examples. With the addition of use cases into the standards for terms, progress could be made on use-case-based standard vocabulary that could reduce the “garbage in/garbage out” problem that comes from being totally
inclusive. </span><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">TDWG standards in the 80s and 90s were a little more about controlled vocabulary and reducing
garbage than they have been in the 00s and 10s. Maybe we should spend some time on that aspect of data exchange again and use cases could be a method.</span><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Best regards,</span><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Chuck</span><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma",sans-serif">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma",sans-serif"> tdwg-content
[mailto:<a href="mailto:tdwg-content-bounces@lists.tdwg.org" target="_blank">tdwg-content-bounces@lists.tdwg.org</a>]
<b>On Behalf Of </b>John Wieczorek<br>
<b>Sent:</b> Tuesday, May 24, 2016 2:48 PM</span><span lang="EN-US"><u></u><u></u></span></p>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US"><br>
<b>To:</b> Quentin Groom<br>
<b>Cc:</b> TDWG Content Mailing List<br>
<b>Subject:</b> Re: [tdwg-content] A proposal to improve Darwin Core for invasive species data<u></u><u></u></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US">I would say that the primary factor driving the philosophy for loose controlled vocabulary recommendations is a desire to promote the stability of Darwin Core
term definitions, because changes can be disruptive. Section 1.4 on the Simple Darwin Core page (<a href="http://rs.tdwg.org/dwc/terms/simple/index.htm" target="_blank">http://rs.tdwg.org/dwc/terms/simple/index.htm</a>) gives further practical arguments for
this stance. I have copied the relevant text here for convenience:<u></u><u></u></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US">"</span><span lang="EN-US" style="font-family:"Verdana",sans-serif;color:black">There is a difference between having data in a field and requiring that field
to have a value from among a legal set of values. The Darwin Core is simple in that it has minimal restrictions on the contents of fields. The term comments give recommendations about the use of controlled vocabularies and how to structure content wherever
appropriate. Data contributors are encouraged to follow these recommendations as well as possible. You might argue that having no restrictions will promote "dirty" data (data of low quality or dubious value). Consider the simple axiom "It's not what you have,
but what you do with it that matters." If data restrictions were in place at the fundamental level, then a record having any non-compliant data in any of its fields could not be shared via the standard. Not only would there be a dearth of shared data in that
case (or an unused standard), but also there would be no way to use the standard to build shared data cleaning tools to actually improve the situation, nor to use data services to look up alternative representations (language translations, for example) to
serve a broader audience. The rest is up to how the records will be used - in other words, it is up to applications to enforce further restrictions if appropriate, and it is up to the stakeholders of those applications to decide what the restrictions will
be for the purpose the application is trying to serve.</span><span lang="EN-US">"<u></u><u></u></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US">On Tue, May 24, 2016 at 3:44 PM, Quentin Groom <<a href="mailto:quentin.groom@plantentuinmeise.be" target="_blank">quentin.groom@plantentuinmeise.be</a>> wrote:<u></u><u></u></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US">Hi Paco,<u></u><u></u></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US">I'm glad to hear Plinian Core is active, I only recently discovered it and think it is a good initiative. The species data I've seen is in quite diverse and in
unstandardised formats. It would be nice to see some of the big providers using Plinian Core.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">I'm not so worried about imposing limitations on users, because as far as I can see Darwin Core only recommends vocabularies, it doesn't enforce them. Having
said that, it would be useful to know what is meant by "<i>Recommended best practice is to use
<u>a</u> controlled vocabulary</i>", because if Darwin Core doesn't impose a vocabulary and there is no field to specify which vocabulary you are using then it doesn't help interoperability much.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">I'm happy to also discuss off list. Invasiveness and impact are difficult to standardize and so far I've chosen other fields that I consider easier to gain consensus
on.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Regards<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="color:#888888">Quentin</span><span lang="EN-US"><u></u><u></u></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><br clear="all">
<u></u><u></u></span></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Dr. Quentin Groom<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">(Botany and Information Technology)<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Botanic Garden Meise<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Domein van Bouchout<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">B-1860 Meise<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Belgium<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><a href="http://orcid.org/0000-0002-0596-5376" target="_blank">ORCID: 0000-0002-0596-5376</a><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Landline; +32 (0) 226 009 20 ext. 364<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">FAX: +32 (0) 226 009 45<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">E-mail:
<a href="mailto:quentin.groom@plantentuinmeise.be" target="_blank">quentin.groom@plantentuinmeise.be</a><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Skype name: qgroom<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Website: <a href="http://www.botanicgarden.be" target="_blank">www.botanicgarden.be</a><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
<div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US">On 24 May 2016 at 19:08, Francisco Pando <<a href="mailto:pando@gbif.es" target="_blank">pando@gbif.es</a>> wrote:<u></u><u></u></span></p>
<div>
<div>
<p style="margin:0cm;margin-bottom:.0001pt"><span lang="EN-US" style="font-family:"Calibri",sans-serif">Quentin et al.,</span><span lang="EN-US"><u></u><u></u></span></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span lang="EN-US" style="font-family:"Calibri",sans-serif"> </span><span lang="EN-US"><u></u><u></u></span></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span lang="EN-US" style="font-family:"Calibri",sans-serif">Plinian Core is active and backed up by an international group that seeks expansion. A session is planned in TDWG 2016 about it within the Species Information
Interest Group slot.</span><span lang="EN-US"><u></u><u></u></span></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span lang="EN-US" style="font-family:"Calibri",sans-serif"> </span><span lang="EN-US"><u></u><u></u></span></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span lang="EN-US" style="font-family:"Calibri",sans-serif">"Invasiveness" is a section within the Plinian Core schema:</span><span lang="EN-US">
<a href="https://github.com/PlinianCore/Documentation/wiki/InvasivenessClass" target="_blank">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">https://github.com/PlinianCore/Documentation/wiki/InvasivenessClass</span></a><u></u><u></u></span></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">It is much based on the GISIN schema. This can be revisited, updated and harmonized with current initiatives, some mentioned in this thread.
Quentin, we may do a bit of exchange of-list</span><span lang="EN-US"><u></u><u></u></span></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><span lang="EN-US"><u></u><u></u></span></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Whereas shared vocabularies bring plenty of good things , I share Chuck’s concerns about imposing some unwanted limitations for some potential
users of the schema.</span><span lang="EN-US"><u></u><u></u></span></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><span lang="EN-US"><u></u><u></u></span></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Best,</span><span lang="EN-US"><u></u><u></u></span></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><span lang="EN-US"><u></u><u></u></span></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Paco</span><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="ES-TRAD" style="font-size:10.5pt;font-family:Consolas;color:#1f497d">Francisco Pando</span><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="ES-TRAD" style="font-size:10.5pt;font-family:Consolas;color:#1f497d"> </span><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="ES-TRAD" style="font-size:10.5pt;font-family:Consolas;color:#1f497d">Investigador </span><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="ES-TRAD" style="font-size:10.5pt;font-family:Consolas;color:#1f497d">Real Jardín Botánico - CSIC
</span><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="ES-TRAD" style="font-size:10.5pt;font-family:Consolas;color:#1f497d">Plaza de Murillo, 2
</span><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="ES" style="font-size:10.5pt;font-family:Consolas;color:#1f497d">28014 Madrid, Spain </span><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="ES-TRAD" style="font-size:10.5pt;font-family:Consolas;color:#1f497d">Tel.<a href="tel:%2B34%2091%20420%203017%20x%20172" target="_blank">+34 91 420 3017 x 172</a></span><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="ES" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma",sans-serif">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma",sans-serif"> tdwg-content
[mailto:<a href="mailto:tdwg-content-bounces@lists.tdwg.org" target="_blank">tdwg-content-bounces@lists.tdwg.org</a>]
<b>On Behalf Of </b>Quentin Groom<br>
<b>Sent:</b> Monday, May 23, 2016 10:10 PM<br>
<b>To:</b> Chuck Miller</span><span lang="EN-US"><u></u><u></u></span></p>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US"><br>
<b>Cc:</b> TDWG Content Mailing List<br>
<b>Subject:</b> Re: [tdwg-content] A proposal to improve Darwin Core for invasive species data<u></u><u></u></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US">Hi Chuck,<u></u><u></u></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US">thanks for your point. The use cases I'm thinking of are conservation red-listing; horizon-scanning for potential new invasives; early warning of new aliens;
impact assessment and invasion monitoring. We have recently be discussing the possibility of automating all of these process so that they can be repeated regularly, or as soon as new data becomes available. Obviously, for this we need observations, but we
also need check-lists to tell us what is considered native or alien, present or extinct.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">I know more about invasive species research than red-listing, but I am aware that the current rate of red-listing is so slow that most things will become extinct
before they are assessed. Given that the IUCN criteria are so clear, it should be possible to automate the whole process using GBIF. The only limitation with then be mobilizing the observations.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Regards<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Quentin<u></u><u></u></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><br clear="all">
<u></u><u></u></span></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Dr. Quentin Groom<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">(Botany and Information Technology)<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Botanic Garden Meise<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Domein van Bouchout<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">B-1860 Meise<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Belgium<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><a href="http://orcid.org/0000-0002-0596-5376" target="_blank">ORCID: 0000-0002-0596-5376</a><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Landline; +32 (0) 226 009 20 ext. 364<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">FAX: +32 (0) 226 009 45<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">E-mail:
<a href="mailto:quentin.groom@plantentuinmeise.be" target="_blank">quentin.groom@plantentuinmeise.be</a><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Skype name: qgroom<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Website: <a href="http://www.botanicgarden.be" target="_blank">www.botanicgarden.be</a><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US">On 23 May 2016 at 21:10, Chuck Miller <<a href="mailto:Chuck.Miller@mobot.org" target="_blank">Chuck.Miller@mobot.org</a>> wrote:<u></u><u></u></span></p>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Quentin,</span><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">I think in addition to defining the community that needs the new Origin term, you also
need to define the use cases to which the proposed controlled vocabularies for establishmentMeans and occurenceStatus apply. Darwin Core is used in multiple ways. I think there may be use cases for these terms that don’t match the invasive species use cases.
One controlled vocabulary may not work for all Darwin Core users. </span><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Best regards,</span><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Chuck</span><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><i><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#00b050">Chuck Miller | VP-IT & CIO | Missouri Botanical Garden</span></i><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><i><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#00b050">4344 Shaw Boulevard | Saint Louis, MO 63110 | Phone
<a href="tel:314-577-9419" target="_blank">314-577-9419</a></span></i><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma",sans-serif">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma",sans-serif"> tdwg-content
[mailto:<a href="mailto:tdwg-content-bounces@lists.tdwg.org" target="_blank">tdwg-content-bounces@lists.tdwg.org</a>]
<b>On Behalf Of </b>John Wieczorek<br>
<b>Sent:</b> Monday, May 23, 2016 1:36 PM<br>
<b>To:</b> Quentin Groom<br>
<b>Cc:</b> TDWG Content Mailing List<br>
<b>Subject:</b> Re: [tdwg-content] A proposal to improve Darwin Core for invasive species data</span><span lang="EN-US"><u></u><u></u></span></p>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US">Hi Quentin,<u></u><u></u></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Thank you for your effort in putting forth these welll thought out proposals. At various times I have heard discussions on the inadequecy of establishmentMeans.
Your work encapsulates the problem well. <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">One of the things that helps when proposing to add a Darwin Core term is demonstrating that there is a community that needs it. Can you tell us who has a demonstrated
need to share this information? Anyone out there who has this interest is also welcome to share that here to provide evidence of demand from more than one group, project or individual.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Cheers,<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">John<u></u><u></u></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US">On Mon, May 23, 2016 at 3:23 PM, Quentin Groom <<a href="mailto:quentin.groom@plantentuinmeise.be" target="_blank">quentin.groom@plantentuinmeise.be</a>> wrote:<u></u><u></u></span></p>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US">I've been working on a proposal to improve Darwin Core for use with invasive species data.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">The proposal is detailed on GitHub at
<a href="https://github.com/qgroom/ias-dwc-proposal/blob/master/proposal.md" target="_blank">
https://github.com/qgroom/ias-dwc-proposal/blob/master/proposal.md</a>.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">The proposal is for a new term "origin" and suggested vocabularies for establishmentMeans and occurrenceStatus.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">I'd welcome your feedback on the proposal.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">From my perspective it provides some needed clarity on the establishmentMeans and occurrenceStatus fields, but also adds the origin that is needed for invasive
species research and for conservation assessments.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">I'm not sure of the best way to discuss this, but if you have concrete proposals for changes you might raise them as issues on GitHub, as well as mentioning them
here.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Regards<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Quentin<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US"><br clear="all">
<u></u><u></u></span></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Dr. Quentin Groom<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">(Botany and Information Technology)<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Botanic Garden Meise<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Domein van Bouchout<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">B-1860 Meise<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Belgium<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><a href="http://orcid.org/0000-0002-0596-5376" target="_blank">ORCID: 0000-0002-0596-5376</a><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Landline; +32 (0) 226 009 20 ext. 364<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">FAX: +32 (0) 226 009 45<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">E-mail:
<a href="mailto:quentin.groom@plantentuinmeise.be" target="_blank">quentin.groom@plantentuinmeise.be</a><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Skype name: qgroom<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Website: <a href="http://www.botanicgarden.be" target="_blank">www.botanicgarden.be</a><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-US"><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><u></u><u></u></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-US"><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><u></u><u></u></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-US"><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><u></u><u></u></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><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><u></u><u></u></p>
</blockquote>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><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><u></u><u></u></p>
</blockquote>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div></div></div>
</div>
</blockquote></div><br></div>