Re: [tdwg-humboldt] FW: Humboldt Task Group Meeting Wed 29 Nov 2023, 12:00 UTC
Thanks Steve for this update and the effort. It would be good to have recognition of acceptance from an ALA representative in the respective Github issues for all resolutions proposed by the Task Group. That would leave all open issues with clear status with respect to consensus.
On Wed, Nov 29, 2023 at 11:37 AM Baskauf, Steven James < steve.baskauf@vanderbilt.edu> wrote:
Sorry, I just did “reply-all”.
s
--
Steven J. Baskauf, Ph.D. he/him/his
Data Science and Data Curation Specialist / Librarian III
Digital Lab, Jean & Alexander Heard Libraries, Vanderbilt University
Nashville, TN 37235, USA
Biodiversity Information Standards (TDWG) Executive Committee/Technical Architecture Group Chair
*From: *Baskauf, Steven James steve.baskauf@Vanderbilt.Edu *Date: *Wednesday, November 29, 2023 at 8:03 AM *To: *Humboldt Core TG tdwg-humboldt@lists.tdwg.org, Wesley M. Hochachka wmh6@cornell.edu, John Wieczorek tuco@berkeley.edu *Subject: *Re: [tdwg-humboldt] Humboldt Task Group Meeting Wed 29 Nov 2023, 12:00 UTC
Hi Yani et al.,
Peter, Rob S., and I met this morning and thrashed our way through the Miscellaneous section from ALA in the Google doc https://docs.google.com/document/d/1OxJ_H5vBd9pucjdgQDa6qMaQKl4O89gf/edit?us... that you referred to in your email below.
In the Miscellaneous section, we believe that we have addressed the issues that were raised; for each of them there is a description of our conclusion in the notes (following “Steve:” in each case). In each of the cases, we concluded that no action was required based on the reasons we gave. We spent quite a bit of time discussing whether the term samplingEffortProtocolReferences should be added. Our conclusion was that it should not, since the specific amount of effort applied in a particular survey would often be unique to that survey and therefore not likely to actually be published anywhere. It’s really a specialization of a published protocol that would be cited in protocolReferences. If for some reason multiple users found a real need for the term it could be added later using the normal DwC term addition process. If you concur with this reasoning, then Issue #87 would need to be closed without taking action.
Based on discussion in previous meetings, we concurred that adding verbatimTargetScope was probably necessary, so we also created the new term verbatimTargetScope in Issue #96 https://github.com/tdwg/hc/issues/96.
We pressed on with the discussion beyond the normal meeting time in order to wrap this up. We were in agreement that it would be really desirable to have this done by the end of calendar 2023. Yani, if you can verify that we’ve actually addressed all of the issues that ALA raised and ping John about that, we can set the 30 day clock running prior to the end of November. That would allow us to submit before or soon after Jan 1. Once the clock is running, Yani, John, and Steve could be working on making sure that the spreadsheet is up to date with any changes that we made so that the QRG and List of Terms can be updated for final submission by the DwC Maintenance Group to the Executive for ratification.
We are so close!
Steve
--
Steven J. Baskauf, Ph.D. he/him/his
Data Science and Data Curation Specialist / Librarian III
Digital Lab, Jean & Alexander Heard Libraries, Vanderbilt University
Nashville, TN 37235, USA
Biodiversity Information Standards (TDWG) Executive Committee/Technical Architecture Group Chair
*From: *tdwg-humboldt tdwg-humboldt-bounces@lists.tdwg.org on behalf of Yanina Sica yanina.sica@gmail.com *Date: *Tuesday, November 28, 2023 at 4:47 AM *To: *Humboldt Core TG tdwg-humboldt@lists.tdwg.org, Wesley M. Hochachka wmh6@cornell.edu, John Wieczorek tuco@berkeley.edu *Subject: *[tdwg-humboldt] Humboldt Task Group Meeting Wed 29 Nov 2023, 12:00 UTC
Dear all,
End of the year is getting closer and many people will start going on holidays. We still have some things to discuss but let's aim to finish them this week. *The goal is to submit all our responses to the GitHub issues and potential new terms or changes by end Nov or beginning Dec. After this, the clock will restart and we will have to wait for another month before ratifying. *
In order to be effective over the next week, *I will ask you to share your comments (either in the meeting or over email) about a few points:*
- Please review the *Miscellaneous* section from ALA (page 16 here
https://docs.google.com/document/d/1OxJ_H5vBd9pucjdgQDa6qMaQKl4O89gf/edit ).
- Please revise the *new term proposed* (see below) about reporting of
scope in a more descriptive way. This term should be used as a last resort and in no way should replace the other scope trms. This term will allow to capture targets that are not included in the more explicits target scopes (e.g. targetTaxonomicScope) at least until new target scopes are proposed, and give more flexibility in the scope reporting, that is why we propose to include it as a verbatim term. This term will not allow completeness or absence inference.
- New term: eco:verbatimTargetScope
scope.’
- Definition: ‘The verbatim original description of the dwc:Event
explicit scope terms to the fullest extent possible (e.g. eco:targetTaxonomicScope). It is not recommended to use this term in assessing absence or completeness.’ Scope of last resort! :)
- Comments: ‘Recommended best practice is first to populate
animals’
- Examples: ‘small mammals’; ‘freshwater macroinvertebrates’; ‘dead
*Peggy*, do you think you can join our next meeting? If not, can you suggest some time slots that work for you? I know it will be hard to coordinate a time that works for everybody and you have already spoken with Peter but it might be nice for some of us to meet with you and discuss your very appreciated feedback. In the meetine, we have collected some thoughts in this document https://docs.google.com/document/d/1OxJ_H5vBd9pucjdgQDa6qMaQKl4O89gf/edit .
Unfortunately, I will not be able to meet this week. My flight to Argentina got cancelled and now I am travelling tonight and will not be in time for our meeting.
All the best!
Yani
Yani
John, thanks for your comment. I think Yani is traveling and Peter our direct link to Peggy is on vacation.
Pater said in the meeting that he has been talking to Peggy about her comments. He expressed confidence that the team was addressing the issues but we do need confirmation from Peggy.
I think it is best to let Yani handle this as she said she was going to be in contact with Peggy.
Best Rob
I was hoping that we could start the clock today and with fingers crossed finish this process in 2023 but I think we will have to wait to complete our check with Peggy. :)
On Wed, Nov 29, 2023 at 9:51 AM John Wieczorek gtuco.btuco@gmail.com wrote:
Thanks Steve for this update and the effort. It would be good to have recognition of acceptance from an ALA representative in the respective Github issues for all resolutions proposed by the Task Group. That would leave all open issues with clear status with respect to consensus.
On Wed, Nov 29, 2023 at 11:37 AM Baskauf, Steven James < steve.baskauf@vanderbilt.edu> wrote:
Sorry, I just did “reply-all”.
s
--
Steven J. Baskauf, Ph.D. he/him/his
Data Science and Data Curation Specialist / Librarian III
Digital Lab, Jean & Alexander Heard Libraries, Vanderbilt University
Nashville, TN 37235, USA
Biodiversity Information Standards (TDWG) Executive Committee/Technical Architecture Group Chair
*From: *Baskauf, Steven James steve.baskauf@Vanderbilt.Edu *Date: *Wednesday, November 29, 2023 at 8:03 AM *To: *Humboldt Core TG tdwg-humboldt@lists.tdwg.org, Wesley M. Hochachka wmh6@cornell.edu, John Wieczorek tuco@berkeley.edu *Subject: *Re: [tdwg-humboldt] Humboldt Task Group Meeting Wed 29 Nov 2023, 12:00 UTC
Hi Yani et al.,
Peter, Rob S., and I met this morning and thrashed our way through the Miscellaneous section from ALA in the Google doc https://docs.google.com/document/d/1OxJ_H5vBd9pucjdgQDa6qMaQKl4O89gf/edit?us... that you referred to in your email below.
In the Miscellaneous section, we believe that we have addressed the issues that were raised; for each of them there is a description of our conclusion in the notes (following “Steve:” in each case). In each of the cases, we concluded that no action was required based on the reasons we gave. We spent quite a bit of time discussing whether the term samplingEffortProtocolReferences should be added. Our conclusion was that it should not, since the specific amount of effort applied in a particular survey would often be unique to that survey and therefore not likely to actually be published anywhere. It’s really a specialization of a published protocol that would be cited in protocolReferences. If for some reason multiple users found a real need for the term it could be added later using the normal DwC term addition process. If you concur with this reasoning, then Issue #87 would need to be closed without taking action.
Based on discussion in previous meetings, we concurred that adding verbatimTargetScope was probably necessary, so we also created the new term verbatimTargetScope in Issue #96 https://github.com/tdwg/hc/issues/96.
We pressed on with the discussion beyond the normal meeting time in order to wrap this up. We were in agreement that it would be really desirable to have this done by the end of calendar 2023. Yani, if you can verify that we’ve actually addressed all of the issues that ALA raised and ping John about that, we can set the 30 day clock running prior to the end of November. That would allow us to submit before or soon after Jan 1. Once the clock is running, Yani, John, and Steve could be working on making sure that the spreadsheet is up to date with any changes that we made so that the QRG and List of Terms can be updated for final submission by the DwC Maintenance Group to the Executive for ratification.
We are so close!
Steve
--
Steven J. Baskauf, Ph.D. he/him/his
Data Science and Data Curation Specialist / Librarian III
Digital Lab, Jean & Alexander Heard Libraries, Vanderbilt University
Nashville, TN 37235, USA
Biodiversity Information Standards (TDWG) Executive Committee/Technical Architecture Group Chair
*From: *tdwg-humboldt tdwg-humboldt-bounces@lists.tdwg.org on behalf of Yanina Sica yanina.sica@gmail.com *Date: *Tuesday, November 28, 2023 at 4:47 AM *To: *Humboldt Core TG tdwg-humboldt@lists.tdwg.org, Wesley M. Hochachka wmh6@cornell.edu, John Wieczorek tuco@berkeley.edu *Subject: *[tdwg-humboldt] Humboldt Task Group Meeting Wed 29 Nov 2023, 12:00 UTC
Dear all,
End of the year is getting closer and many people will start going on holidays. We still have some things to discuss but let's aim to finish them this week. *The goal is to submit all our responses to the GitHub issues and potential new terms or changes by end Nov or beginning Dec. After this, the clock will restart and we will have to wait for another month before ratifying. *
In order to be effective over the next week, *I will ask you to share your comments (either in the meeting or over email) about a few points:*
- Please review the *Miscellaneous* section from ALA (page 16 here
https://docs.google.com/document/d/1OxJ_H5vBd9pucjdgQDa6qMaQKl4O89gf/edit ).
- Please revise the *new term proposed* (see below) about reporting
of scope in a more descriptive way. This term should be used as a last resort and in no way should replace the other scope trms. This term will allow to capture targets that are not included in the more explicits target scopes (e.g. targetTaxonomicScope) at least until new target scopes are proposed, and give more flexibility in the scope reporting, that is why we propose to include it as a verbatim term. This term will not allow completeness or absence inference.
- New term: eco:verbatimTargetScope
scope.’
- Definition: ‘The verbatim original description of the dwc:Event
explicit scope terms to the fullest extent possible (e.g. eco:targetTaxonomicScope). It is not recommended to use this term in assessing absence or completeness.’ Scope of last resort! :)
- Comments: ‘Recommended best practice is first to populate
‘dead animals’
- Examples: ‘small mammals’; ‘freshwater macroinvertebrates’;
*Peggy*, do you think you can join our next meeting? If not, can you suggest some time slots that work for you? I know it will be hard to coordinate a time that works for everybody and you have already spoken with Peter but it might be nice for some of us to meet with you and discuss your very appreciated feedback. In the meetine, we have collected some thoughts in this document https://docs.google.com/document/d/1OxJ_H5vBd9pucjdgQDa6qMaQKl4O89gf/edit .
Unfortunately, I will not be able to meet this week. My flight to Argentina got cancelled and now I am travelling tonight and will not be in time for our meeting.
All the best!
Yani
Yani
tdwg-humboldt mailing list tdwg-humboldt@lists.tdwg.org https://lists.tdwg.org/mailman/listinfo/tdwg-humboldt
Thanks Rob. Yes, we should be able to start the clock againfrom the last time a change was made to a proposal.
On Fri, Dec 1, 2023 at 8:33 AM Rob Stevenson rdstevenson10@gmail.com wrote:
John, thanks for your comment. I think Yani is traveling and Peter our direct link to Peggy is on vacation.
Pater said in the meeting that he has been talking to Peggy about her comments. He expressed confidence that the team was addressing the issues but we do need confirmation from Peggy.
I think it is best to let Yani handle this as she said she was going to be in contact with Peggy.
Best Rob
I was hoping that we could start the clock today and with fingers crossed finish this process in 2023 but I think we will have to wait to complete our check with Peggy. :)
On Wed, Nov 29, 2023 at 9:51 AM John Wieczorek gtuco.btuco@gmail.com wrote:
Thanks Steve for this update and the effort. It would be good to have recognition of acceptance from an ALA representative in the respective Github issues for all resolutions proposed by the Task Group. That would leave all open issues with clear status with respect to consensus.
On Wed, Nov 29, 2023 at 11:37 AM Baskauf, Steven James < steve.baskauf@vanderbilt.edu> wrote:
Sorry, I just did “reply-all”.
s
--
Steven J. Baskauf, Ph.D. he/him/his
Data Science and Data Curation Specialist / Librarian III
Digital Lab, Jean & Alexander Heard Libraries, Vanderbilt University
Nashville, TN 37235, USA
Biodiversity Information Standards (TDWG) Executive Committee/Technical Architecture Group Chair
*From: *Baskauf, Steven James steve.baskauf@Vanderbilt.Edu *Date: *Wednesday, November 29, 2023 at 8:03 AM *To: *Humboldt Core TG tdwg-humboldt@lists.tdwg.org, Wesley M. Hochachka wmh6@cornell.edu, John Wieczorek tuco@berkeley.edu *Subject: *Re: [tdwg-humboldt] Humboldt Task Group Meeting Wed 29 Nov 2023, 12:00 UTC
Hi Yani et al.,
Peter, Rob S., and I met this morning and thrashed our way through the Miscellaneous section from ALA in the Google doc https://docs.google.com/document/d/1OxJ_H5vBd9pucjdgQDa6qMaQKl4O89gf/edit?us... that you referred to in your email below.
In the Miscellaneous section, we believe that we have addressed the issues that were raised; for each of them there is a description of our conclusion in the notes (following “Steve:” in each case). In each of the cases, we concluded that no action was required based on the reasons we gave. We spent quite a bit of time discussing whether the term samplingEffortProtocolReferences should be added. Our conclusion was that it should not, since the specific amount of effort applied in a particular survey would often be unique to that survey and therefore not likely to actually be published anywhere. It’s really a specialization of a published protocol that would be cited in protocolReferences. If for some reason multiple users found a real need for the term it could be added later using the normal DwC term addition process. If you concur with this reasoning, then Issue #87 would need to be closed without taking action.
Based on discussion in previous meetings, we concurred that adding verbatimTargetScope was probably necessary, so we also created the new term verbatimTargetScope in Issue #96 https://github.com/tdwg/hc/issues/96.
We pressed on with the discussion beyond the normal meeting time in order to wrap this up. We were in agreement that it would be really desirable to have this done by the end of calendar 2023. Yani, if you can verify that we’ve actually addressed all of the issues that ALA raised and ping John about that, we can set the 30 day clock running prior to the end of November. That would allow us to submit before or soon after Jan 1. Once the clock is running, Yani, John, and Steve could be working on making sure that the spreadsheet is up to date with any changes that we made so that the QRG and List of Terms can be updated for final submission by the DwC Maintenance Group to the Executive for ratification.
We are so close!
Steve
--
Steven J. Baskauf, Ph.D. he/him/his
Data Science and Data Curation Specialist / Librarian III
Digital Lab, Jean & Alexander Heard Libraries, Vanderbilt University
Nashville, TN 37235, USA
Biodiversity Information Standards (TDWG) Executive Committee/Technical Architecture Group Chair
*From: *tdwg-humboldt tdwg-humboldt-bounces@lists.tdwg.org on behalf of Yanina Sica yanina.sica@gmail.com *Date: *Tuesday, November 28, 2023 at 4:47 AM *To: *Humboldt Core TG tdwg-humboldt@lists.tdwg.org, Wesley M. Hochachka wmh6@cornell.edu, John Wieczorek tuco@berkeley.edu *Subject: *[tdwg-humboldt] Humboldt Task Group Meeting Wed 29 Nov 2023, 12:00 UTC
Dear all,
End of the year is getting closer and many people will start going on holidays. We still have some things to discuss but let's aim to finish them this week. *The goal is to submit all our responses to the GitHub issues and potential new terms or changes by end Nov or beginning Dec. After this, the clock will restart and we will have to wait for another month before ratifying. *
In order to be effective over the next week, *I will ask you to share your comments (either in the meeting or over email) about a few points:*
- Please review the *Miscellaneous* section from ALA (page 16 here
https://docs.google.com/document/d/1OxJ_H5vBd9pucjdgQDa6qMaQKl4O89gf/edit ).
- Please revise the *new term proposed* (see below) about reporting
of scope in a more descriptive way. This term should be used as a last resort and in no way should replace the other scope trms. This term will allow to capture targets that are not included in the more explicits target scopes (e.g. targetTaxonomicScope) at least until new target scopes are proposed, and give more flexibility in the scope reporting, that is why we propose to include it as a verbatim term. This term will not allow completeness or absence inference.
- New term: eco:verbatimTargetScope
scope.’
- Definition: ‘The verbatim original description of the dwc:Event
explicit scope terms to the fullest extent possible (e.g. eco:targetTaxonomicScope). It is not recommended to use this term in assessing absence or completeness.’ Scope of last resort! :)
- Comments: ‘Recommended best practice is first to populate
‘dead animals’
- Examples: ‘small mammals’; ‘freshwater macroinvertebrates’;
*Peggy*, do you think you can join our next meeting? If not, can you suggest some time slots that work for you? I know it will be hard to coordinate a time that works for everybody and you have already spoken with Peter but it might be nice for some of us to meet with you and discuss your very appreciated feedback. In the meetine, we have collected some thoughts in this document https://docs.google.com/document/d/1OxJ_H5vBd9pucjdgQDa6qMaQKl4O89gf/edit .
Unfortunately, I will not be able to meet this week. My flight to Argentina got cancelled and now I am travelling tonight and will not be in time for our meeting.
All the best!
Yani
Yani
tdwg-humboldt mailing list tdwg-humboldt@lists.tdwg.org https://lists.tdwg.org/mailman/listinfo/tdwg-humboldt
-- Robert D Stevenson Associate Professor Department of Biology UMass Boston _______________________________________________ tdwg-humboldt mailing list tdwg-humboldt@lists.tdwg.org https://lists.tdwg.org/mailman/listinfo/tdwg-humboldt
Hi all
Apologies, I’ve been travelling and am back at my desk today. I’ll be able to have a look at this on Wednesday.
Could somebody send me the details of the call this week? I don’t have them. I’ll come along so we can get this finalised. Yani, if you want to get in touch separately, let me know.
Cheers Peggy
Peggy Newman Data Manager Atlas of Living Australia
From: tdwg-humboldt tdwg-humboldt-bounces@lists.tdwg.org on behalf of John Wieczorek gtuco.btuco@gmail.com Date: Saturday, 2 December 2023 at 5:18 am To: Humboldt Core TG tdwg-humboldt@lists.tdwg.org Cc: Wesley M. Hochachka wmh6@cornell.edu Subject: Re: [tdwg-humboldt] FW: Humboldt Task Group Meeting Wed 29 Nov 2023, 12:00 UTC Thanks Rob. Yes, we should be able to start the clock againfrom the last time a change was made to a proposal.
On Fri, Dec 1, 2023 at 8:33 AM Rob Stevenson <rdstevenson10@gmail.commailto:rdstevenson10@gmail.com> wrote: John, thanks for your comment. I think Yani is traveling and Peter our direct link to Peggy is on vacation.
Pater said in the meeting that he has been talking to Peggy about her comments. He expressed confidence that the team was addressing the issues but we do need confirmation from Peggy.
I think it is best to let Yani handle this as she said she was going to be in contact with Peggy.
Best Rob
I was hoping that we could start the clock today and with fingers crossed finish this process in 2023 but I think we will have to wait to complete our check with Peggy. :)
On Wed, Nov 29, 2023 at 9:51 AM John Wieczorek <gtuco.btuco@gmail.commailto:gtuco.btuco@gmail.com> wrote: Thanks Steve for this update and the effort. It would be good to have recognition of acceptance from an ALA representative in the respective Github issues for all resolutions proposed by the Task Group. That would leave all open issues with clear status with respect to consensus.
On Wed, Nov 29, 2023 at 11:37 AM Baskauf, Steven James <steve.baskauf@vanderbilt.edumailto:steve.baskauf@vanderbilt.edu> wrote: Sorry, I just did “reply-all”. s
-- Steven J. Baskauf, Ph.D. he/him/his Data Science and Data Curation Specialist / Librarian III Digital Lab, Jean & Alexander Heard Libraries, Vanderbilt University Nashville, TN 37235, USA
Biodiversity Information Standards (TDWG) Executive Committee/Technical Architecture Group Chair https://baskauf.github.io/
From: Baskauf, Steven James steve.baskauf@Vanderbilt.Edu Date: Wednesday, November 29, 2023 at 8:03 AM To: Humboldt Core TG <tdwg-humboldt@lists.tdwg.orgmailto:tdwg-humboldt@lists.tdwg.org>, Wesley M. Hochachka <wmh6@cornell.edumailto:wmh6@cornell.edu>, John Wieczorek <tuco@berkeley.edumailto:tuco@berkeley.edu> Subject: Re: [tdwg-humboldt] Humboldt Task Group Meeting Wed 29 Nov 2023, 12:00 UTC Hi Yani et al.,
Peter, Rob S., and I met this morning and thrashed our way through the Miscellaneous section from ALA in the Google doc https://docs.google.com/document/d/1OxJ_H5vBd9pucjdgQDa6qMaQKl4O89gf/edit?us... that you referred to in your email below.
In the Miscellaneous section, we believe that we have addressed the issues that were raised; for each of them there is a description of our conclusion in the notes (following “Steve:” in each case). In each of the cases, we concluded that no action was required based on the reasons we gave. We spent quite a bit of time discussing whether the term samplingEffortProtocolReferences should be added. Our conclusion was that it should not, since the specific amount of effort applied in a particular survey would often be unique to that survey and therefore not likely to actually be published anywhere. It’s really a specialization of a published protocol that would be cited in protocolReferences. If for some reason multiple users found a real need for the term it could be added later using the normal DwC term addition process. If you concur with this reasoning, then Issue #87 would need to be closed without taking action.
Based on discussion in previous meetings, we concurred that adding verbatimTargetScope was probably necessary, so we also created the new term verbatimTargetScope in Issue #96 https://github.com/tdwg/hc/issues/96.
We pressed on with the discussion beyond the normal meeting time in order to wrap this up. We were in agreement that it would be really desirable to have this done by the end of calendar 2023. Yani, if you can verify that we’ve actually addressed all of the issues that ALA raised and ping John about that, we can set the 30 day clock running prior to the end of November. That would allow us to submit before or soon after Jan 1. Once the clock is running, Yani, John, and Steve could be working on making sure that the spreadsheet is up to date with any changes that we made so that the QRG and List of Terms can be updated for final submission by the DwC Maintenance Group to the Executive for ratification.
We are so close! Steve
-- Steven J. Baskauf, Ph.D. he/him/his Data Science and Data Curation Specialist / Librarian III Digital Lab, Jean & Alexander Heard Libraries, Vanderbilt University Nashville, TN 37235, USA
Biodiversity Information Standards (TDWG) Executive Committee/Technical Architecture Group Chair https://baskauf.github.io/
From: tdwg-humboldt <tdwg-humboldt-bounces@lists.tdwg.orgmailto:tdwg-humboldt-bounces@lists.tdwg.org> on behalf of Yanina Sica <yanina.sica@gmail.commailto:yanina.sica@gmail.com> Date: Tuesday, November 28, 2023 at 4:47 AM To: Humboldt Core TG <tdwg-humboldt@lists.tdwg.orgmailto:tdwg-humboldt@lists.tdwg.org>, Wesley M. Hochachka <wmh6@cornell.edumailto:wmh6@cornell.edu>, John Wieczorek <tuco@berkeley.edumailto:tuco@berkeley.edu> Subject: [tdwg-humboldt] Humboldt Task Group Meeting Wed 29 Nov 2023, 12:00 UTC Dear all,
End of the year is getting closer and many people will start going on holidays. We still have some things to discuss but let's aim to finish them this week. The goal is to submit all our responses to the GitHub issues and potential new terms or changes by end Nov or beginning Dec. After this, the clock will restart and we will have to wait for another month before ratifying.
In order to be effective over the next week, I will ask you to share your comments (either in the meeting or over email) about a few points:
* Please review the Miscellaneous section from ALA (page 16 herehttps://docs.google.com/document/d/1OxJ_H5vBd9pucjdgQDa6qMaQKl4O89gf/edit). * Please revise the new term proposed (see below) about reporting of scope in a more descriptive way. This term should be used as a last resort and in no way should replace the other scope trms. This term will allow to capture targets that are not included in the more explicits target scopes (e.g. targetTaxonomicScope) at least until new target scopes are proposed, and give more flexibility in the scope reporting, that is why we propose to include it as a verbatim term. This term will not allow completeness or absence inference.
* New term: eco:verbatimTargetScope * Definition: ‘The verbatim original description of the dwc:Event scope.’ * Comments: ‘Recommended best practice is first to populate explicit scope terms to the fullest extent possible (e.g. eco:targetTaxonomicScope). It is not recommended to use this term in assessing absence or completeness.’ Scope of last resort! :) * Examples: ‘small mammals’; ‘freshwater macroinvertebrates’; ‘dead animals’ Peggy, do you think you can join our next meeting? If not, can you suggest some time slots that work for you? I know it will be hard to coordinate a time that works for everybody and you have already spoken with Peter but it might be nice for some of us to meet with you and discuss your very appreciated feedback. In the meetine, we have collected some thoughts in this documenthttps://docs.google.com/document/d/1OxJ_H5vBd9pucjdgQDa6qMaQKl4O89gf/edit.
Unfortunately, I will not be able to meet this week. My flight to Argentina got cancelled and now I am travelling tonight and will not be in time for our meeting.
All the best!
Yani
Yani _______________________________________________ tdwg-humboldt mailing list tdwg-humboldt@lists.tdwg.orgmailto:tdwg-humboldt@lists.tdwg.org https://lists.tdwg.org/mailman/listinfo/tdwg-humboldt
-- Robert D Stevenson Associate Professor Department of Biology UMass Boston _______________________________________________ tdwg-humboldt mailing list tdwg-humboldt@lists.tdwg.orgmailto:tdwg-humboldt@lists.tdwg.org https://lists.tdwg.org/mailman/listinfo/tdwg-humboldt
participants (3)
-
John Wieczorek -
Newman, Peggy (NCMI, Clayton) -
Rob Stevenson