<div dir="ltr">Hi John et al,<div><br></div><div>Ditto (to Annie's comment) from me. </div><div><br></div><div>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.</div><div><br></div><div>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.</div><div><br></div><div>I raise this as I believe that the time for such a meeting is well and truly here.</div><div><br></div><div>Cheers</div><div><br></div><div>Lee</div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature">Lee Belbin<br>Blatant Fabrications Pty Ltd<br>Tasmania<br></div></div>
<br><div class="gmail_quote">On Thu, May 26, 2016 at 4:04 AM, Quentin Groom <span dir="ltr"><<a href="mailto:quentin.groom@plantentuinmeise.be" target="_blank">quentin.groom@plantentuinmeise.be</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">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 class="HOEnZb"><font color="#888888"><div>Quentin</div></font></span></div><div class="gmail_extra"><span class=""><br clear="all"><div><div><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></span><div><div class="h5"><div class="gmail_quote">On 25 May 2016 at 17:57, John Wieczorek <span dir="ltr"><<a href="mailto:tuco@berkeley.edu" target="_blank">tuco@berkeley.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">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.</div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, May 25, 2016 at 12:52 PM, Simpson, Annie <span dir="ltr"><<a href="mailto:asimpson@usgs.gov" target="_blank">asimpson@usgs.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Chiming in now, very briefly...<div><br></div><div>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.</div><div class="gmail_extra"><br clear="all"><div><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><b style="font-weight:normal"><font size="1" face="arial narrow, sans-serif"><span style="vertical-align:baseline;white-space:pre-wrap">Annie Simpson, biologist & information scientist</span></font></b></div><div dir="ltr"><font face="arial narrow, sans-serif" size="1"><span style="white-space:pre-wrap"><a href="http://orcid.org/0000-0001-8338-5134" target="_blank">http://orcid.org/0000-0001-8338-5134</a></span><br></font><div><b style="font-weight:normal"><font size="1" face="arial narrow, sans-serif"><span style="white-space:pre-wrap">BISON project (<a href="http://bison.usgs.ornl.gov" target="_blank">http://bison.usgs.ornl.gov</a>)</span><br></font></b><div><b style="font-weight:normal"><font size="1" face="arial narrow, sans-serif"><span style="vertical-align:baseline;white-space:pre-wrap">Core Science Analytics, Synthesis, & Libraries Program</span></font></b><div><b style="font-weight:normal"><font size="1" face="arial narrow, sans-serif"><span style="vertical-align:baseline;white-space:pre-wrap">U.S. Geological Survey, MS 302</span><br><span style="vertical-align:baseline;white-space:pre-wrap">12201 Sunrise Valley Drive</span><br><span style="vertical-align:baseline;white-space:pre-wrap">Reston, Virginia 20192</span><br><span style="vertical-align:baseline;white-space:pre-wrap">=================</span><br><span style="white-space:pre-wrap"><a href="mailto:asimpson@usgs.gov" target="_blank">asimpson@usgs.gov</a></span><br><span style="vertical-align:baseline;white-space:pre-wrap"><a href="tel:703.648.4281" value="+17036484281" target="_blank">703.648.4281</a> desk</span></font></b></div></div></div></div></div></div></div></div></div></div><div><div>
<br><div class="gmail_quote">On Wed, May 25, 2016 at 7:26 AM, John Wieczorek <span dir="ltr"><<a href="mailto:tuco@berkeley.edu" target="_blank">tuco@berkeley.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">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. </div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, May 25, 2016 at 2:00 AM, Quentin Groom <span dir="ltr"><<a href="mailto:quentin.groom@plantentuinmeise.be" target="_blank">quentin.groom@plantentuinmeise.be</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Interesting! I had not come across Apple Core before. Isn't this proving-ground role something that the Biological Collections Ontology can also do?<div>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.</div><div>Regards</div><span><font color="#888888"><div>Quentin</div></font></span></div><div class="gmail_extra"><span><br clear="all"><div><div><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></span><div><div><div class="gmail_quote">On 25 May 2016 at 03:17, John Wieczorek <span dir="ltr"><<a href="mailto:tuco@berkeley.edu" target="_blank">tuco@berkeley.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">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.</div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 24, 2016 at 6:16 PM, Chuck Miller <span dir="ltr"><<a href="mailto:Chuck.Miller@mobot.org" target="_blank">Chuck.Miller@mobot.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-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">John,<u></u><u></u></span></p>
<p class="MsoNormal"><span 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.
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span 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.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Best regards,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Chuck<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<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 [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></p><div><div><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></div></div><p></p><div><div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">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></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">"<span 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>"<u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">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></p>
<div>
<p class="MsoNormal">Hi Paco,<u></u><u></u></p>
<div>
<p class="MsoNormal">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></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">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></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">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></p>
</div>
<div>
<p class="MsoNormal"><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 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></p>
<div>
<div>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri","sans-serif"">Quentin et al.,</span><u></u><u></u></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri","sans-serif""> </span><u></u><u></u></p>
<p style="margin:0in;margin-bottom:.0001pt"><span 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><u></u><u></u></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri","sans-serif""> </span><u></u><u></u></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri","sans-serif"">"Invasiveness" is a section within the Plinian Core schema:</span>
<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></p>
<p style="margin:0in;margin-bottom:.0001pt"><span 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><u></u><u></u></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><u></u><u></u></p>
<p style="margin:0in;margin-bottom:.0001pt"><span 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><u></u><u></u></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><u></u><u></u></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Best,</span><u></u><u></u></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><u></u><u></u></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Paco</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span lang="ES-TRAD" style="font-size:10.5pt;font-family:Consolas;color:#1f497d">Francisco Pando</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="ES-TRAD" style="font-size:10.5pt;font-family:Consolas;color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span lang="ES-TRAD" style="font-size:10.5pt;font-family:Consolas;color:#1f497d">Investigador </span><u></u><u></u></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><u></u><u></u></p>
<p class="MsoNormal"><span lang="ES-TRAD" style="font-size:10.5pt;font-family:Consolas;color:#1f497d">Plaza de Murillo, 2
</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="ES" style="font-size:10.5pt;font-family:Consolas;color:#1f497d">28014 Madrid, Spain </span><u></u><u></u></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><u></u><u></u></p>
<p class="MsoNormal"><span lang="ES" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<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 [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><u></u><u></u></p>
<div>
<div>
<p class="MsoNormal"><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></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
<div>
<p class="MsoNormal">Hi Chuck,<u></u><u></u></p>
<div>
<p class="MsoNormal">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></p>
</div>
<div>
<p class="MsoNormal">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></p>
</div>
<div>
<p class="MsoNormal">Regards<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Quentin<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>
<p class="MsoNormal">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></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Quentin,</span><u></u><u></u></p>
<p class="MsoNormal"><span 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><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Best regards,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Chuck</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><i><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#00b050">Chuck Miller | VP-IT & CIO | Missouri Botanical Garden</span></i><u></u><u></u></p>
<p class="MsoNormal"><i><span 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><u></u><u></u></p>
<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 [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><u></u><u></u></p>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
<div>
<p class="MsoNormal">Hi Quentin,<u></u><u></u></p>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">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></p>
</div>
<div>
<p class="MsoNormal">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></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">John<u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
<div>
<p class="MsoNormal">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></p>
<div>
<div>
<p class="MsoNormal">I've been working on a proposal to improve Darwin Core for use with invasive species data.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">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></p>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">The proposal is for a new term "origin" and suggested vocabularies for establishmentMeans and occurrenceStatus.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">I'd welcome your feedback on the proposal.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">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></p>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">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></p>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Regards<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Quentin<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</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>
</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>
</div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
</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>
</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>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div></div></div>
</div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div></div></div>
</blockquote></div><br></div>
<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" rel="noreferrer" target="_blank">http://lists.tdwg.org/mailman/listinfo/tdwg-content</a><br>
<br></blockquote></div><br></div></div></div></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div></div></div>
<br>_______________________________________________<br>
tdwg-content mailing list<br>
<a href="mailto:tdwg-content@lists.tdwg.org">tdwg-content@lists.tdwg.org</a><br>
<a href="http://lists.tdwg.org/mailman/listinfo/tdwg-content" rel="noreferrer" target="_blank">http://lists.tdwg.org/mailman/listinfo/tdwg-content</a><br>
<br></blockquote></div><br></div>