<p dir="ltr">Hi all<br>
I agree on the good work and heads up. Small face to face workshops on the standards when it wss possible to organize them proofed indeed very useful and productive.<br>
In the executive we are aware of this. If you feel that there would be a need for such one on this topic a dress it to the executive so we can look into it. Similar to the small Darwin core extension meeting organized a couple of years ago in Belgium.<br>
With my best wishes<br>
Pat<br>
</p>
<div class="gmail_quote">On 27 May 2016 05:51, "Shorthouse, David" <<a href="mailto:davidpshorthouse@gmail.com">davidpshorthouse@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">All,<br>
<br>
I second, third, and fourth similar spirited support. John, you have<br>
inspired growth & have helped our community to lift ourselves up from<br>
drudgery. We've failed to see it, but collecting and depositing<br>
specimens is the highest form of academic and social responsibility.<br>
<br>
What strikes me most from this dialogue is the implicit, unwritten<br>
word. Email signatures have included nicely structured,<br>
without-a-second-thought links to ORCID profiles. Can we please<br>
inspire to do the same for specimens as we've now very quickly done<br>
for ourselves? Failure to do so with its legacy of excuses is no<br>
longer an option.<br>
<br>
David<br>
<br>
On Thu, May 26, 2016 at 11:31 PM, Lee Belbin <<a href="mailto:leebelbin@gmail.com">leebelbin@gmail.com</a>> wrote:<br>
> Hi John et al,<br>
><br>
> Ditto (to Annie's comment) from me.<br>
><br>
> As most of you know, I have been standing back from TDWG for a few years<br>
> now, but it has been hard to avoid interest in the development of TDWG's<br>
> most significant standard. I have been aware of at least three independent<br>
> suggestions that are relevant to my interests.<br>
><br>
> As from the beginning, the difficulty remains in getting wise heads together<br>
> (face-to-face) and getting consensus on recommendations in a timely manner.<br>
> The TDWG meetings are too busy without sufficient time to achieve outcomes.<br>
> Teleconferencing is great in theory but hopeless in practice. The only<br>
> alternative is to find time and $ for dedicated meetings adjacent to, or<br>
> separate from the TDWG Conference. It has been done before to good effect.<br>
><br>
> I raise this as I believe that the time for such a meeting is well and truly<br>
> here.<br>
><br>
> Cheers<br>
><br>
> Lee<br>
><br>
> Lee Belbin<br>
> Blatant Fabrications Pty Ltd<br>
> Tasmania<br>
><br>
> On Thu, May 26, 2016 at 4:04 AM, Quentin Groom<br>
> <<a href="mailto:quentin.groom@plantentuinmeise.be">quentin.groom@plantentuinmeise.be</a>> wrote:<br>
>><br>
>> I second Annie, this is a real problem in Biodiversity Informatics in<br>
>> general. Unless you can turn maintenance tasks into peer reviewed papers<br>
>> then you get little credit for it.<br>
>> Quentin<br>
>><br>
>><br>
>><br>
>> Dr. Quentin Groom<br>
>> (Botany and Information Technology)<br>
>><br>
>> Botanic Garden Meise<br>
>> Domein van Bouchout<br>
>> B-1860 Meise<br>
>> Belgium<br>
>><br>
>> ORCID: 0000-0002-0596-5376<br>
>><br>
>> Landline; <a href="tel:%2B32%20%280%29%20226%20009%2020%20ext.%20364" value="+3222600920">+32 (0) 226 009 20 ext. 364</a><br>
>> FAX: <a href="tel:%2B32%20%280%29%20226%20009%2045" value="+3222600945">+32 (0) 226 009 45</a><br>
>><br>
>> E-mail: <a href="mailto:quentin.groom@plantentuinmeise.be">quentin.groom@plantentuinmeise.be</a><br>
>> Skype name: qgroom<br>
>> Website: <a href="http://www.botanicgarden.be" rel="noreferrer" target="_blank">www.botanicgarden.be</a><br>
>><br>
>><br>
>> On 25 May 2016 at 17:57, John Wieczorek <<a href="mailto:tuco@berkeley.edu">tuco@berkeley.edu</a>> wrote:<br>
>>><br>
>>> Thanks Annie. I don't plan to give up, it's just that I don't feel I have<br>
>>> been doing it justice for a while now.<br>
>>><br>
>>> On Wed, May 25, 2016 at 12:52 PM, Simpson, Annie <<a href="mailto:asimpson@usgs.gov">asimpson@usgs.gov</a>><br>
>>> wrote:<br>
>>>><br>
>>>> Chiming in now, very briefly...<br>
>>>><br>
>>>> John, you are the DwC champion who has kept it moving forward in a<br>
>>>> comprehensible and useful way. The TDWG community is very grateful for your<br>
>>>> work on this and I personally hope you don't give up the good fight.<br>
>>>><br>
>>>> Annie Simpson, biologist & information scientist<br>
>>>> <a href="http://orcid.org/0000-0001-8338-5134" rel="noreferrer" target="_blank">http://orcid.org/0000-0001-8338-5134</a><br>
>>>> BISON project (<a href="http://bison.usgs.ornl.gov" rel="noreferrer" target="_blank">http://bison.usgs.ornl.gov</a>)<br>
>>>> Core Science Analytics, Synthesis, & Libraries Program<br>
>>>> U.S. Geological Survey, MS 302<br>
>>>> 12201 Sunrise Valley Drive<br>
>>>> Reston, Virginia 20192<br>
>>>> =================<br>
>>>> <a href="mailto:asimpson@usgs.gov">asimpson@usgs.gov</a><br>
>>>> 703.648.4281 desk<br>
>>>><br>
>>>> On Wed, May 25, 2016 at 7:26 AM, John Wieczorek <<a href="mailto:tuco@berkeley.edu">tuco@berkeley.edu</a>><br>
>>>> wrote:<br>
>>>>><br>
>>>>> One primary idea behind the BCO is indeed as the proving ground you<br>
>>>>> mention. The challenge is having consistent available resources to do that<br>
>>>>> work. With BCO it could be a particular challenge, I think, since it can<br>
>>>>> cover so much semantic space. I would love to be in a position to be a<br>
>>>>> proper BCO caretaker, but I have not even been able to do a good job with<br>
>>>>> Darwin Core as it is.<br>
>>>>><br>
>>>>> On Wed, May 25, 2016 at 2:00 AM, Quentin Groom<br>
>>>>> <<a href="mailto:quentin.groom@plantentuinmeise.be">quentin.groom@plantentuinmeise.be</a>> wrote:<br>
>>>>>><br>
>>>>>> Interesting! I had not come across Apple Core before. Isn't this<br>
>>>>>> proving-ground role something that the Biological Collections Ontology can<br>
>>>>>> also do?<br>
>>>>>> I like the idea of a Darwin Core with different levels of adherence to<br>
>>>>>> rules. I agree that strict enforcement of rules will inhibit the flow of<br>
>>>>>> data, but in my own experience there are simple fields that I could have<br>
>>>>>> easily completed in a standardized way, if only I could have found a<br>
>>>>>> suitable recommendation to follow. Hierarchical vocabularies are<br>
>>>>>> particularly useful here, because they have built in flexibility.<br>
>>>>>> Regards<br>
>>>>>> Quentin<br>
>>>>>><br>
>>>>>><br>
>>>>>><br>
>>>>>> Dr. Quentin Groom<br>
>>>>>> (Botany and Information Technology)<br>
>>>>>><br>
>>>>>> Botanic Garden Meise<br>
>>>>>> Domein van Bouchout<br>
>>>>>> B-1860 Meise<br>
>>>>>> Belgium<br>
>>>>>><br>
>>>>>> ORCID: 0000-0002-0596-5376<br>
>>>>>><br>
>>>>>> Landline; <a href="tel:%2B32%20%280%29%20226%20009%2020%20ext.%20364" value="+3222600920">+32 (0) 226 009 20 ext. 364</a><br>
>>>>>> FAX: <a href="tel:%2B32%20%280%29%20226%20009%2045" value="+3222600945">+32 (0) 226 009 45</a><br>
>>>>>><br>
>>>>>> E-mail: <a href="mailto:quentin.groom@plantentuinmeise.be">quentin.groom@plantentuinmeise.be</a><br>
>>>>>> Skype name: qgroom<br>
>>>>>> Website: <a href="http://www.botanicgarden.be" rel="noreferrer" target="_blank">www.botanicgarden.be</a><br>
>>>>>><br>
>>>>>><br>
>>>>>> On 25 May 2016 at 03:17, John Wieczorek <<a href="mailto:tuco@berkeley.edu">tuco@berkeley.edu</a>> wrote:<br>
>>>>>>><br>
>>>>>>> I think it is indeed worthwhile to have content standards to go with<br>
>>>>>>> the term definitions. Applce Core (now under renewed development at<br>
>>>>>>> <a href="https://github.com/tdwg/applecore" rel="noreferrer" target="_blank">https://github.com/tdwg/applecore</a>) is a good example of this.<br>
>>>>>>><br>
>>>>>>> On Tue, May 24, 2016 at 6:16 PM, Chuck Miller<br>
>>>>>>> <<a href="mailto:Chuck.Miller@mobot.org">Chuck.Miller@mobot.org</a>> wrote:<br>
>>>>>>>><br>
>>>>>>>> John,<br>
>>>>>>>><br>
>>>>>>>> It’s interesting how long that text has been out there, and without<br>
>>>>>>>> much comment. It seems to presume there is a binary situation: tightly<br>
>>>>>>>> controlled vocabulary that is exclusive or loosely controlled that is<br>
>>>>>>>> inclusive. Maybe it’s time now to consider something additional in the<br>
>>>>>>>> middle. We know a lot more about how the Darwin Core standard is being<br>
>>>>>>>> used, or at least have plenty of examples. With the addition of use cases<br>
>>>>>>>> into the standards for terms, progress could be made on use-case-based<br>
>>>>>>>> standard vocabulary that could reduce the “garbage in/garbage out” problem<br>
>>>>>>>> that comes from being totally inclusive.<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> TDWG standards in the 80s and 90s were a little more about<br>
>>>>>>>> controlled vocabulary and reducing garbage than they have been in the 00s<br>
>>>>>>>> and 10s. Maybe we should spend some time on that aspect of data exchange<br>
>>>>>>>> again and use cases could be a method.<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> Best regards,<br>
>>>>>>>><br>
>>>>>>>> Chuck<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> From: tdwg-content [mailto:<a href="mailto:tdwg-content-bounces@lists.tdwg.org">tdwg-content-bounces@lists.tdwg.org</a>] On<br>
>>>>>>>> Behalf Of John Wieczorek<br>
>>>>>>>> Sent: Tuesday, May 24, 2016 2:48 PM<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> To: Quentin Groom<br>
>>>>>>>> Cc: TDWG Content Mailing List<br>
>>>>>>>> Subject: Re: [tdwg-content] A proposal to improve Darwin Core for<br>
>>>>>>>> invasive species data<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> I would say that the primary factor driving the philosophy for loose<br>
>>>>>>>> controlled vocabulary recommendations is a desire to promote the stability<br>
>>>>>>>> of Darwin Core term definitions, because changes can be disruptive. Section<br>
>>>>>>>> 1.4 on the Simple Darwin Core page<br>
>>>>>>>> (<a href="http://rs.tdwg.org/dwc/terms/simple/index.htm" rel="noreferrer" target="_blank">http://rs.tdwg.org/dwc/terms/simple/index.htm</a>) gives further practical<br>
>>>>>>>> arguments for this stance. I have copied the relevant text here for<br>
>>>>>>>> convenience:<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> "There is a difference between having data in a field and requiring<br>
>>>>>>>> that field to have a value from among a legal set of values. The Darwin Core<br>
>>>>>>>> is simple in that it has minimal restrictions on the contents of fields. The<br>
>>>>>>>> term comments give recommendations about the use of controlled vocabularies<br>
>>>>>>>> and how to structure content wherever appropriate. Data contributors are<br>
>>>>>>>> encouraged to follow these recommendations as well as possible. You might<br>
>>>>>>>> argue that having no restrictions will promote "dirty" data (data of low<br>
>>>>>>>> quality or dubious value). Consider the simple axiom "It's not what you<br>
>>>>>>>> have, but what you do with it that matters." If data restrictions were in<br>
>>>>>>>> place at the fundamental level, then a record having any non-compliant data<br>
>>>>>>>> in any of its fields could not be shared via the standard. Not only would<br>
>>>>>>>> there be a dearth of shared data in that case (or an unused standard), but<br>
>>>>>>>> also there would be no way to use the standard to build shared data cleaning<br>
>>>>>>>> tools to actually improve the situation, nor to use data services to look up<br>
>>>>>>>> alternative representations (language translations, for example) to serve a<br>
>>>>>>>> broader audience. The rest is up to how the records will be used - in other<br>
>>>>>>>> words, it is up to applications to enforce further restrictions if<br>
>>>>>>>> appropriate, and it is up to the stakeholders of those applications to<br>
>>>>>>>> decide what the restrictions will be for the purpose the application is<br>
>>>>>>>> trying to serve."<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> On Tue, May 24, 2016 at 3:44 PM, Quentin Groom<br>
>>>>>>>> <<a href="mailto:quentin.groom@plantentuinmeise.be">quentin.groom@plantentuinmeise.be</a>> wrote:<br>
>>>>>>>><br>
>>>>>>>> Hi Paco,<br>
>>>>>>>><br>
>>>>>>>> I'm glad to hear Plinian Core is active, I only recently discovered<br>
>>>>>>>> it and think it is a good initiative. The species data I've seen is in quite<br>
>>>>>>>> diverse and in unstandardised formats. It would be nice to see some of the<br>
>>>>>>>> big providers using Plinian Core.<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> I'm not so worried about imposing limitations on users, because as<br>
>>>>>>>> far as I can see Darwin Core only recommends vocabularies, it doesn't<br>
>>>>>>>> enforce them. Having said that, it would be useful to know what is meant by<br>
>>>>>>>> "Recommended best practice is to use a controlled vocabulary", because if<br>
>>>>>>>> Darwin Core doesn't impose a vocabulary and there is no field to specify<br>
>>>>>>>> which vocabulary you are using then it doesn't help interoperability much.<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> I'm happy to also discuss off list. Invasiveness and impact are<br>
>>>>>>>> difficult to standardize and so far I've chosen other fields that I consider<br>
>>>>>>>> easier to gain consensus on.<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> Regards<br>
>>>>>>>><br>
>>>>>>>> Quentin<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> Dr. Quentin Groom<br>
>>>>>>>><br>
>>>>>>>> (Botany and Information Technology)<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> Botanic Garden Meise<br>
>>>>>>>><br>
>>>>>>>> Domein van Bouchout<br>
>>>>>>>><br>
>>>>>>>> B-1860 Meise<br>
>>>>>>>><br>
>>>>>>>> Belgium<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> ORCID: 0000-0002-0596-5376<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> Landline; <a href="tel:%2B32%20%280%29%20226%20009%2020%20ext.%20364" value="+3222600920">+32 (0) 226 009 20 ext. 364</a><br>
>>>>>>>><br>
>>>>>>>> FAX: <a href="tel:%2B32%20%280%29%20226%20009%2045" value="+3222600945">+32 (0) 226 009 45</a><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> E-mail: <a href="mailto:quentin.groom@plantentuinmeise.be">quentin.groom@plantentuinmeise.be</a><br>
>>>>>>>><br>
>>>>>>>> Skype name: qgroom<br>
>>>>>>>><br>
>>>>>>>> Website: <a href="http://www.botanicgarden.be" rel="noreferrer" target="_blank">www.botanicgarden.be</a><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> On 24 May 2016 at 19:08, Francisco Pando <<a href="mailto:pando@gbif.es">pando@gbif.es</a>> wrote:<br>
>>>>>>>><br>
>>>>>>>> Quentin et al.,<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> Plinian Core is active and backed up by an international group that<br>
>>>>>>>> seeks expansion. A session is planned in TDWG 2016 about it within the<br>
>>>>>>>> Species Information Interest Group slot.<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> "Invasiveness" is a section within the Plinian Core schema:<br>
>>>>>>>> <a href="https://github.com/PlinianCore/Documentation/wiki/InvasivenessClass" rel="noreferrer" target="_blank">https://github.com/PlinianCore/Documentation/wiki/InvasivenessClass</a><br>
>>>>>>>><br>
>>>>>>>> It is much based on the GISIN schema. This can be revisited,<br>
>>>>>>>> updated and harmonized with current initiatives, some mentioned in this<br>
>>>>>>>> thread. Quentin, we may do a bit of exchange of-list<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> Whereas shared vocabularies bring plenty of good things , I share<br>
>>>>>>>> Chuck’s concerns about imposing some unwanted limitations for some potential<br>
>>>>>>>> users of the schema.<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> Best,<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> Paco<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> Francisco Pando<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> Investigador<br>
>>>>>>>><br>
>>>>>>>> Real Jardín Botánico - CSIC<br>
>>>>>>>><br>
>>>>>>>> Plaza de Murillo, 2<br>
>>>>>>>><br>
>>>>>>>> 28014 Madrid, Spain<br>
>>>>>>>><br>
>>>>>>>> Tel.<a href="tel:%2B34%2091%20420%203017%20x%20172" value="+34914203017">+34 91 420 3017 x 172</a><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> From: tdwg-content [mailto:<a href="mailto:tdwg-content-bounces@lists.tdwg.org">tdwg-content-bounces@lists.tdwg.org</a>] On<br>
>>>>>>>> Behalf Of Quentin Groom<br>
>>>>>>>> Sent: Monday, May 23, 2016 10:10 PM<br>
>>>>>>>> To: Chuck Miller<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> Cc: TDWG Content Mailing List<br>
>>>>>>>> Subject: Re: [tdwg-content] A proposal to improve Darwin Core for<br>
>>>>>>>> invasive species data<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> Hi Chuck,<br>
>>>>>>>><br>
>>>>>>>> thanks for your point. The use cases I'm thinking of are<br>
>>>>>>>> conservation red-listing; horizon-scanning for potential new invasives;<br>
>>>>>>>> early warning of new aliens; impact assessment and invasion monitoring. We<br>
>>>>>>>> have recently be discussing the possibility of automating all of these<br>
>>>>>>>> process so that they can be repeated regularly, or as soon as new data<br>
>>>>>>>> becomes available. Obviously, for this we need observations, but we also<br>
>>>>>>>> need check-lists to tell us what is considered native or alien, present or<br>
>>>>>>>> extinct.<br>
>>>>>>>><br>
>>>>>>>> I know more about invasive species research than red-listing, but I<br>
>>>>>>>> am aware that the current rate of red-listing is so slow that most things<br>
>>>>>>>> will become extinct before they are assessed. Given that the IUCN criteria<br>
>>>>>>>> are so clear, it should be possible to automate the whole process using<br>
>>>>>>>> GBIF. The only limitation with then be mobilizing the observations.<br>
>>>>>>>><br>
>>>>>>>> Regards<br>
>>>>>>>><br>
>>>>>>>> Quentin<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> Dr. Quentin Groom<br>
>>>>>>>><br>
>>>>>>>> (Botany and Information Technology)<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> Botanic Garden Meise<br>
>>>>>>>><br>
>>>>>>>> Domein van Bouchout<br>
>>>>>>>><br>
>>>>>>>> B-1860 Meise<br>
>>>>>>>><br>
>>>>>>>> Belgium<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> ORCID: 0000-0002-0596-5376<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> Landline; <a href="tel:%2B32%20%280%29%20226%20009%2020%20ext.%20364" value="+3222600920">+32 (0) 226 009 20 ext. 364</a><br>
>>>>>>>><br>
>>>>>>>> FAX: <a href="tel:%2B32%20%280%29%20226%20009%2045" value="+3222600945">+32 (0) 226 009 45</a><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> E-mail: <a href="mailto:quentin.groom@plantentuinmeise.be">quentin.groom@plantentuinmeise.be</a><br>
>>>>>>>><br>
>>>>>>>> Skype name: qgroom<br>
>>>>>>>><br>
>>>>>>>> Website: <a href="http://www.botanicgarden.be" rel="noreferrer" target="_blank">www.botanicgarden.be</a><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> On 23 May 2016 at 21:10, Chuck Miller <<a href="mailto:Chuck.Miller@mobot.org">Chuck.Miller@mobot.org</a>><br>
>>>>>>>> wrote:<br>
>>>>>>>><br>
>>>>>>>> Quentin,<br>
>>>>>>>><br>
>>>>>>>> I think in addition to defining the community that needs the new<br>
>>>>>>>> Origin term, you also need to define the use cases to which the proposed<br>
>>>>>>>> controlled vocabularies for establishmentMeans and occurenceStatus apply.<br>
>>>>>>>> Darwin Core is used in multiple ways. I think there may be use cases for<br>
>>>>>>>> these terms that don’t match the invasive species use cases. One controlled<br>
>>>>>>>> vocabulary may not work for all Darwin Core users.<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> Best regards,<br>
>>>>>>>><br>
>>>>>>>> Chuck<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> Chuck Miller | VP-IT & CIO | Missouri Botanical Garden<br>
>>>>>>>><br>
>>>>>>>> 4344 Shaw Boulevard | Saint Louis, MO 63110 | Phone 314-577-9419<br>
>>>>>>>><br>
>>>>>>>> From: tdwg-content [mailto:<a href="mailto:tdwg-content-bounces@lists.tdwg.org">tdwg-content-bounces@lists.tdwg.org</a>] On<br>
>>>>>>>> Behalf Of John Wieczorek<br>
>>>>>>>> Sent: Monday, May 23, 2016 1:36 PM<br>
>>>>>>>> To: Quentin Groom<br>
>>>>>>>> Cc: TDWG Content Mailing List<br>
>>>>>>>> Subject: Re: [tdwg-content] A proposal to improve Darwin Core for<br>
>>>>>>>> invasive species data<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> Hi Quentin,<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> Thank you for your effort in putting forth these welll thought out<br>
>>>>>>>> proposals. At various times I have heard discussions on the inadequecy of<br>
>>>>>>>> establishmentMeans. Your work encapsulates the problem well.<br>
>>>>>>>><br>
>>>>>>>> One of the things that helps when proposing to add a Darwin Core<br>
>>>>>>>> term is demonstrating that there is a community that needs it. Can you tell<br>
>>>>>>>> us who has a demonstrated need to share this information? Anyone out there<br>
>>>>>>>> who has this interest is also welcome to share that here to provide evidence<br>
>>>>>>>> of demand from more than one group, project or individual.<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> Cheers,<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> John<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> On Mon, May 23, 2016 at 3:23 PM, Quentin Groom<br>
>>>>>>>> <<a href="mailto:quentin.groom@plantentuinmeise.be">quentin.groom@plantentuinmeise.be</a>> wrote:<br>
>>>>>>>><br>
>>>>>>>> I've been working on a proposal to improve Darwin Core for use with<br>
>>>>>>>> invasive species data.<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> The proposal is detailed on GitHub at<br>
>>>>>>>> <a href="https://github.com/qgroom/ias-dwc-proposal/blob/master/proposal.md" rel="noreferrer" target="_blank">https://github.com/qgroom/ias-dwc-proposal/blob/master/proposal.md</a>.<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> The proposal is for a new term "origin" and suggested vocabularies<br>
>>>>>>>> for establishmentMeans and occurrenceStatus.<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> I'd welcome your feedback on the proposal.<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> From my perspective it provides some needed clarity on the<br>
>>>>>>>> establishmentMeans and occurrenceStatus fields, but also adds the origin<br>
>>>>>>>> that is needed for invasive species research and for conservation<br>
>>>>>>>> assessments.<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> I'm not sure of the best way to discuss this, but if you have<br>
>>>>>>>> concrete proposals for changes you might raise them as issues on GitHub, as<br>
>>>>>>>> well as mentioning them here.<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> Regards<br>
>>>>>>>><br>
>>>>>>>> Quentin<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> Dr. Quentin Groom<br>
>>>>>>>><br>
>>>>>>>> (Botany and Information Technology)<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> Botanic Garden Meise<br>
>>>>>>>><br>
>>>>>>>> Domein van Bouchout<br>
>>>>>>>><br>
>>>>>>>> B-1860 Meise<br>
>>>>>>>><br>
>>>>>>>> Belgium<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> ORCID: 0000-0002-0596-5376<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> Landline; <a href="tel:%2B32%20%280%29%20226%20009%2020%20ext.%20364" value="+3222600920">+32 (0) 226 009 20 ext. 364</a><br>
>>>>>>>><br>
>>>>>>>> FAX: <a href="tel:%2B32%20%280%29%20226%20009%2045" value="+3222600945">+32 (0) 226 009 45</a><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> E-mail: <a href="mailto:quentin.groom@plantentuinmeise.be">quentin.groom@plantentuinmeise.be</a><br>
>>>>>>>><br>
>>>>>>>> Skype name: qgroom<br>
>>>>>>>><br>
>>>>>>>> Website: <a href="http://www.botanicgarden.be" rel="noreferrer" target="_blank">www.botanicgarden.be</a><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><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>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><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>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><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>
>>>>>>>><br>
>>>>>>><br>
>>>>>>><br>
>>>>>><br>
>>>>><br>
>>>>><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>
>>>><br>
>>><br>
>><br>
>><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>
><br>
><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>
_______________________________________________<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>
</blockquote></div>