From zkachian at fieldmuseum.org Wed Feb 1 04:47:50 2023 From: zkachian at fieldmuseum.org (Zachary Kachian) Date: Tue, 31 Jan 2023 22:47:50 -0600 Subject: [tdwg-humboldt] Humboldt Task Group Meeting Wed 1 February 2023, 08:00 EST In-Reply-To: References: Message-ID: Hi everyone, My apologies, but I will not be able to attend our meeting tomorrow. I have another early meeting that I need to be at the museum for. If there is anything that comes up that I can help with, please let me know. Thanks, Zach On Tue, Jan 31, 2023, 5:08 PM ys628 wrote: > Hi all! > > Let's meet tomorrow and revise: > > - D*efinition and comments for *isInventoryComplete (?) (see these > slides > for > reference) > - eventType term proposal and > how it relates to hc::inventoryTypes > - start planning for the ?*implementation experience report*? > > > Zoom link: https://yale.zoom.us/j/97318391101 > > > Hope you are all well, > Saludos! > > > > Yani > > > > Yanina V. Sica, PhD > Lead Data Team > Map of Life | Center for Biodiversity and Global Change > > Yale University > pronouns: she/her/hers > *If you are receiving this email outside of your working hours, I am not > expecting you to read or respond.* > _______________________________________________ > tdwg-humboldt mailing list > tdwg-humboldt at lists.tdwg.org > https://lists.tdwg.org/mailman/listinfo/tdwg-humboldt > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ymgan at naturalsciences.be Wed Feb 1 10:16:21 2023 From: ymgan at naturalsciences.be (Yi Ming Gan) Date: Wed, 1 Feb 2023 10:16:21 +0000 Subject: [tdwg-humboldt] Humboldt Task Group Meeting Wed 1 February 2023, 08:00 EST In-Reply-To: References: Message-ID: Hi all My apologies too! I am in a time crunch for last minute data management preparatory work for an upcoming antarctic expedition, so I might not be able to make it to the meeting. It will be great if someone could take notes for the meeting! Thanks a lot! Cheers Ming On 1 Feb 2023, at 05:47, Zachary Kachian wrote: Hi everyone, My apologies, but I will not be able to attend our meeting tomorrow. I have another early meeting that I need to be at the museum for. If there is anything that comes up that I can help with, please let me know. Thanks, Zach On Tue, Jan 31, 2023, 5:08 PM ys628 > wrote: Hi all! Let's meet tomorrow and revise: * Definition and comments for isInventoryComplete (?) (see these slides for reference) * eventType term proposal and how it relates to hc::inventoryTypes * start planning for the ?implementation experience report? Zoom link: https://yale.zoom.us/j/97318391101 Hope you are all well, Saludos! Yani Yanina V. Sica, PhD Lead Data Team Map of Life | Center for Biodiversity and Global Change Yale University pronouns: she/her/hers If you are receiving this email outside of your working hours, I am not expecting you to read or respond. _______________________________________________ tdwg-humboldt mailing list tdwg-humboldt at lists.tdwg.org https://lists.tdwg.org/mailman/listinfo/tdwg-humboldt _______________________________________________ tdwg-humboldt mailing list tdwg-humboldt at lists.tdwg.org https://lists.tdwg.org/mailman/listinfo/tdwg-humboldt -------------- next part -------------- An HTML attachment was scrubbed... URL: From kathryn.ingenloff at gmail.com Wed Feb 1 10:39:22 2023 From: kathryn.ingenloff at gmail.com (Kate Ingenloff) Date: Wed, 1 Feb 2023 11:39:22 +0100 Subject: [tdwg-humboldt] Humboldt Task Group Meeting Wed 1 February 2023, 08:00 EST In-Reply-To: References:

Message-ID: No worries. I'll be able to attend this week and will happily take notes. Cheers, Kate On Wed, Feb 1, 2023 at 11:16 AM Yi Ming Gan wrote: > Hi all > > > My apologies too! I am in a time crunch for last minute data management > preparatory work for an upcoming antarctic expedition, so I might not be > able to make it to the meeting. > It will be great if someone could take notes for the meeting! > > Thanks a lot! > > > Cheers > Ming > > > On 1 Feb 2023, at 05:47, Zachary Kachian wrote: > > Hi everyone, > > My apologies, but I will not be able to attend our meeting tomorrow. I > have another early meeting that I need to be at the museum for. If there is > anything that comes up that I can help with, please let me know. > > Thanks, > Zach > > On Tue, Jan 31, 2023, 5:08 PM ys628 wrote: > >> Hi all! >> >> Let's meet tomorrow and revise: >> >> - D*efinition and comments for *isInventoryComplete (?) (see these >> slides >> for >> reference) >> - eventType term proposal >> and >> how it relates to hc::inventoryTypes >> - start planning for the ?*implementation experience report*? >> >> >> Zoom link: https://yale.zoom.us/j/97318391101 >> >> >> Hope you are all well, >> Saludos! >> >> >> Yani >> >> >> >> Yanina V. Sica, PhD >> Lead Data Team >> Map of Life >> >> | Center for Biodiversity and Global Change >> >> Yale University >> pronouns: she/her/hers >> *If you are receiving this email outside of your working hours, I am not >> expecting you to read or respond.* >> _______________________________________________ >> tdwg-humboldt mailing list >> tdwg-humboldt at lists.tdwg.org >> https://lists.tdwg.org/mailman/listinfo/tdwg-humboldt >> >> > _______________________________________________ > tdwg-humboldt mailing list > tdwg-humboldt at lists.tdwg.org > https://lists.tdwg.org/mailman/listinfo/tdwg-humboldt > > > _______________________________________________ > tdwg-humboldt mailing list > tdwg-humboldt at lists.tdwg.org > https://lists.tdwg.org/mailman/listinfo/tdwg-humboldt > -- ------------------------------ Kate Ingenloff, PhD Pronouns: she/her(s) (+45) 51 44 13 23 "When one tugs at a single thread in nature, he finds it attached to the rest of the world." ~John Muir -------------- next part -------------- An HTML attachment was scrubbed... URL: From yanina.sica at yale.edu Tue Feb 7 14:56:51 2023 From: yanina.sica at yale.edu (ys628) Date: Tue, 7 Feb 2023 14:56:51 +0000 Subject: [tdwg-humboldt] Humboldt Task Group Meeting Wed 8 February 2023, 08:00 EST/13:00 UTC Message-ID: Hi team, Hope you are all good! We have been having some great discussions lately and hopefully we will have another good one tomorrow. Peter Desmet has contacted us (thanks Steve for making the link!). He has been coordinating the development of the Camera Trap Data Package (Camtrap DP) and would like to discuss with us some terms that overlap with their use case. This relates a lot to the mapping exercise we did with the Wildlife Insights data (see slide 2 here to find the feedback we received). Peter will join us tomorrow to review some terms (see in agenda below) and hopefully discuss the transition from https://tdwg.github.io/hc/terms/ to the new TDWG design, see e.g. https://dwc.tdwg.org/ If it is ok with you, we can push the discussion regarding the addition of new terms (see slide 8 and 9 here) for the following week. Proposed agenda for this week's meeting: * Brief into to Camtrap DP (Peter Desmet) * Discuss Camtrap DP that may overlap with HE: * samplingPerformedBy ---> Would this apply to the person who setup the camera (but didn't take the actual photos)? * Geospatial Scope & Habitat ---> Geospatial scope is recorded in Camtrap DP, but as a geojson object. It does not specify the totalAreaSampledInSquareKilometer, siteCount, reportedWeather, etc. * verbatimSiteNames ---> location name is recorded, but there is no property listing all verbatimSiteNames . * habitat can be recorded, but there is no Camtrap DP property for the habitatScope. * eventDuration + eventDurationUnit ?---> Temporal scope as well as deployment duration is recorded in Camtrap DP, but as a start-end date(time). * targetTaxonomicScope ---> Taxonomic scope in Camtrap DP records the observed species, not the target/excluded species, but see #41 (comment) * targetLifestageScope, targetDegreeOfEstablishmentScope, targetGrowthFormScope are not recorded. * isAbundanceReported ---> Abundance is often reported, but not the fact whether or not that is the case (isAbundanceReported) * Methodology + Completeness & Effort ---> to be discussed * Transition from https://tdwg.github.io/hc/terms/ to the new TDWG design, see e.g. https://dwc.tdwg.org/ (Peter Desmet) * If time allows, review taxonomic scope related terms (see slide 8 and 9 here) See you soon! Zoom link: https://yale.zoom.us/j/97318391101 Yani Yanina V. Sica, PhD Lead Data Team Map of Life | Center for Biodiversity and Global Change Yale University pronouns: she/her/hers If you are receiving this email outside of your working hours, I am not expecting you to read or respond. -------------- next part -------------- An HTML attachment was scrubbed... URL: From yanina.sica at yale.edu Tue Feb 14 19:54:28 2023 From: yanina.sica at yale.edu (ys628) Date: Tue, 14 Feb 2023 19:54:28 +0000 Subject: [tdwg-humboldt] Humboldt Task Group Meeting Wed 15 February 2023, 08:00 EST/13:00 UTC Message-ID: Hi valentines! I hope everybody is great. Let meet tomorrow and discuss the following items: * review taxonomic scope related terms (see slide 13 and 14 here) * discuss the need for isReportedAbundanceAdditive (?) (slide 15 here) --> john is still thinking about this * discuss the need for IdentificationConfidence (slide 15 here) * start writing the implementation report!! See you soon! Zoom link: https://yale.zoom.us/j/97318391101 Yani Yanina V. Sica, PhD Lead Data Team Map of Life | Center for Biodiversity and Global Change Yale University pronouns: she/her/hers If you are receiving this email outside of your working hours, I am not expecting you to read or respond. -------------- next part -------------- An HTML attachment was scrubbed... URL: From yanina.sica at gmail.com Wed Feb 15 01:57:10 2023 From: yanina.sica at gmail.com (Yanina Sica) Date: Tue, 14 Feb 2023 20:57:10 -0500 Subject: [tdwg-humboldt] Humboldt Task Group Meeting Wed 15 February 2023, 08:00 EST/13:00 UTC Message-ID: [sorry if you receive this message twice!] Hi valentines! I hope everybody is great. Let meet tomorrow and discuss the following items: - review *taxonomic scope related terms* (see slide 13 and 14 here ) - *discuss the need for isReportedAbundanceAdditive (?) (slide 15 here ) --> john is still thinking about this* - *discuss the need for IdentificationConfidence (slide 15 here ) * - *start writing the implementation report!!* See you soon! Zoom link: https://yale.zoom.us/j/97318391101 Yani -------------- next part -------------- An HTML attachment was scrubbed... URL: From ymgan at naturalsciences.be Wed Feb 15 09:02:13 2023 From: ymgan at naturalsciences.be (Yi Ming Gan) Date: Wed, 15 Feb 2023 09:02:13 +0000 Subject: [tdwg-humboldt] Humboldt Task Group Meeting Wed 15 February 2023, 08:00 EST/13:00 UTC In-Reply-To: References: Message-ID: Thanks Yani!! I won?t be able to attend the meeting today due to schedule conflict, but please see my comment below: isInventoryComplete A statement about whether user reported every species observed - Thanks Wesley for the definition, I appreciate it! - My only remarks is it is possible that the non-target taxa observed is reported but could not be identified it to species level. So I am not sure how to document this seeing its use is intended for species-level observations? Should targetSizeScope be included? I am not sure. In my humboldt opinion, it is probably a good idea to have data provider document the sampling effort such as mesh size of the net for the trawl. The information about target size scope can perhaps can be inferred? identificationConfidence We have some discussions about the need in OBIS: https://github.com/iobis/quality-taskteam/issues/35 There is a similar term in cam trap-dp: https://github.com/tdwg/camtrap-dp/issues/217, https://tdwg.github.io/camtrap-dp/data/#observations.classificationconfidence My concern is will this vary across different taxa? If so, how to document this at Event level? (since Humboldt is an extension to the Event?) Maybe it?s a term to be proposed for Identification class? Looking at the terms again, I have some concern about the amount of boolean terms that is dependent on other table such as the Event core table and Occurrence extension table. For example, hasMaterialSample, isAbundanceReported, isAbsenceReported. On average, I work with 3 tables (excluding Humboldt). I think it is a little error prone to have the fields dependent on other table IF it is something that can be derived. The reason is, data provider often change things in different tables and that including the IDs (eventID, occurrenceID). It is very common that information on one table is updated but not the other. In my experience, many data providers are still using spreadsheet, so I am a little worried that these fields may lead to inconsistencies or people will not use it because it is a lot of work. isAbundanceReported - if there is a value in individualCount or organismQuantity, organismQuantityType of the occurrence records of the Event, would that perhaps sufficient to imply that the abundance is reported? (Please correct me if I am wrong) isAbsenceReported - same as above, but looking at occurrenceStatus column. hasMaterialSample - same as above, but looking at the MaterialSampleID column. If materialSampleTypes (Humboldt term) has a value, then perhaps that is sufficient to imply that hasMaterialSample is true? I hope I am making sense~ Thank you all very much for the hard work! Sincerely Ming PS: I got a date for Valentine?s! It?s February 14 (haha) :) On 15 Feb 2023, at 02:57, Yanina Sica wrote: [sorry if you receive this message twice!] Hi valentines! I hope everybody is great. Let meet tomorrow and discuss the following items: * review taxonomic scope related terms (see slide 13 and 14 here) * discuss the need for isReportedAbundanceAdditive (?) (slide 15 here) --> john is still thinking about this * discuss the need for IdentificationConfidence (slide 15 here) * start writing the implementation report!! See you soon! Zoom link: https://yale.zoom.us/j/97318391101 Yani _______________________________________________ tdwg-humboldt mailing list tdwg-humboldt at lists.tdwg.org https://lists.tdwg.org/mailman/listinfo/tdwg-humboldt -------------- next part -------------- An HTML attachment was scrubbed... URL: From Peter.Brenton at csiro.au Wed Feb 15 11:38:18 2023 From: Peter.Brenton at csiro.au (Brenton, Peter (NCMI, Black Mountain)) Date: Wed, 15 Feb 2023 11:38:18 +0000 Subject: [tdwg-humboldt] Humboldt Task Group Meeting Wed 15 February 2023, 08:00 EST/13:00 UTC In-Reply-To: References:

Message-ID: I am also not able to join today, sorry about that. Peter From: tdwg-humboldt On Behalf Of Yi Ming Gan Sent: Wednesday, 15 February 2023 8:02 PM To: Humboldt Core TG Cc: Wesley M. Hochachka Subject: Re: [tdwg-humboldt] Humboldt Task Group Meeting Wed 15 February 2023, 08:00 EST/13:00 UTC Thanks Yani!! I won?t be able to attend the meeting today due to schedule conflict, but please see my comment below: isInventoryComplete A statement about whether user reported every species observed - Thanks Wesley for the definition, I appreciate it! - My only remarks is it is possible that the non-target taxa observed is reported but could not be identified it to species level. So I am not sure how to document this seeing its use is intended for species-level observations? Should targetSizeScope be included? I am not sure. In my humboldt opinion, it is probably a good idea to have data provider document the sampling effort such as mesh size of the net for the trawl. The information about target size scope can perhaps can be inferred? identificationConfidence We have some discussions about the need in OBIS: https://github.com/iobis/quality-taskteam/issues/35 There is a similar term in cam trap-dp: https://github.com/tdwg/camtrap-dp/issues/217, https://tdwg.github.io/camtrap-dp/data/#observations.classificationconfidence My concern is will this vary across different taxa? If so, how to document this at Event level? (since Humboldt is an extension to the Event?) Maybe it?s a term to be proposed for Identification class? Looking at the terms again, I have some concern about the amount of boolean terms that is dependent on other table such as the Event core table and Occurrence extension table. For example, hasMaterialSample, isAbundanceReported, isAbsenceReported. On average, I work with 3 tables (excluding Humboldt). I think it is a little error prone to have the fields dependent on other table IF it is something that can be derived. The reason is, data provider often change things in different tables and that including the IDs (eventID, occurrenceID). It is very common that information on one table is updated but not the other. In my experience, many data providers are still using spreadsheet, so I am a little worried that these fields may lead to inconsistencies or people will not use it because it is a lot of work. isAbundanceReported - if there is a value in individualCount or organismQuantity, organismQuantityType of the occurrence records of the Event, would that perhaps sufficient to imply that the abundance is reported? (Please correct me if I am wrong) isAbsenceReported - same as above, but looking at occurrenceStatus column. hasMaterialSample - same as above, but looking at the MaterialSampleID column. If materialSampleTypes (Humboldt term) has a value, then perhaps that is sufficient to imply that hasMaterialSample is true? I hope I am making sense~ Thank you all very much for the hard work! Sincerely Ming PS: I got a date for Valentine?s! It?s February 14 (haha) :) On 15 Feb 2023, at 02:57, Yanina Sica > wrote: [sorry if you receive this message twice!] Hi valentines! I hope everybody is great. Let meet tomorrow and discuss the following items: * review taxonomic scope related terms (see slide 13 and 14 here) * discuss the need for isReportedAbundanceAdditive (?) (slide 15 here) --> john is still thinking about this * discuss the need for IdentificationConfidence (slide 15 here) * start writing the implementation report!! See you soon! Zoom link: https://yale.zoom.us/j/97318391101 Yani _______________________________________________ tdwg-humboldt mailing list tdwg-humboldt at lists.tdwg.org https://lists.tdwg.org/mailman/listinfo/tdwg-humboldt -------------- next part -------------- An HTML attachment was scrubbed... URL: From steve.baskauf at vanderbilt.edu Wed Feb 15 14:44:21 2023 From: steve.baskauf at vanderbilt.edu (Baskauf, Steven James) Date: Wed, 15 Feb 2023 14:44:21 +0000 Subject: [tdwg-humboldt] Humboldt Extension namespace abbreviation Message-ID: <269A9C05-BDDA-40FE-8332-23C9297315F0@vanderbilt.edu> Hi all, This is a follow-up to the brief discussion at the end of our meeting today. I had an idea in the shower (where I frequently have creative thoughts ? must be something about being more relaxed) about what to use as a short abbreviation for Humboldt extension IRIs. As an official name for Humboldt, we call it the ?Humboldt Extension for Ecological Inventories? or something like that. That already has the benefit of telling people what it?s about. Then for the abbreviation we either use ?eco? or ?inv? as the abbreviation instead of ?humboldt? or ?hmbldt?. That would make the IRIs either http://rs.tdwg.org/eco/term/foo or http://rs.tdwg.org/inv/term/foo which would be abbreviated as ?eco:foo? or ?inv:foo? respectively, following the established patterns we already are using in TDWG. This would have the added benefit of not confusing anybody if we suddenly discover that Humboldt was an evil space alien or something and decide we don?t want to name the extension after him anymore. Yes, I know that sounds weird, but Audubon Core is rebranding as Audiovisual Core and fortunately we can still use ?ac:? without confusing anybody. This solution would also dodge that potential future problem. I haven?t checked to see if ?eco? or ?inv? are already being used by any well-known vocabularies, but I?ll do that if this idea gets any traction. Thoughts? -- Steven J. Baskauf, Ph.D. he/him/his Data Science and Data Curation Specialist / Librarian III 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 on behalf of ys628 Reply-To: Humboldt Core TG Date: Tuesday, February 14, 2023 at 1:55 PM To: Humboldt Core TG , "wmh6 at cornell.edu" Subject: [tdwg-humboldt] Humboldt Task Group Meeting Wed 15 February 2023, 08:00 EST/13:00 UTC Hi valentines! I hope everybody is great. Let meet tomorrow and discuss the following items: * review taxonomic scope related terms (see slide 13 and 14 here) * discuss the need for isReportedAbundanceAdditive (?) (slide 15 here) --> john is still thinking about this * discuss the need for IdentificationConfidence (slide 15 here) * start writing the implementation report!! See you soon! Zoom link: https://yale.zoom.us/j/97318391101 Yani Yanina V. Sica, PhD Lead Data Team Map of Life | Center for Biodiversity and Global Change Yale University pronouns: she/her/hers If you are receiving this email outside of your working hours, I am not expecting you to read or respond. -------------- next part -------------- An HTML attachment was scrubbed... URL: From tuco at berkeley.edu Wed Feb 15 14:48:28 2023 From: tuco at berkeley.edu (John Wieczorek) Date: Wed, 15 Feb 2023 11:48:28 -0300 Subject: [tdwg-humboldt] Humboldt Extension namespace abbreviation In-Reply-To: <269A9C05-BDDA-40FE-8332-23C9297315F0@vanderbilt.edu> References: <269A9C05-BDDA-40FE-8332-23C9297315F0@vanderbilt.edu> Message-ID: I really like your idea. Solves all kinds of issues. I'll be surprised if "eco:" isn't already in common use, but if it isn't, we should jump on it. On Wed, Feb 15, 2023 at 11:44 AM Baskauf, Steven James < steve.baskauf at vanderbilt.edu> wrote: > Hi all, > > > > This is a follow-up to the brief discussion at the end of our meeting > today. I had an idea in the shower (where I frequently have creative > thoughts ? must be something about being more relaxed) about what to use as > a short abbreviation for Humboldt extension IRIs. As an official name for > Humboldt, we call it the ?Humboldt Extension for Ecological Inventories? or > something like that. That already has the benefit of telling people what > it?s about. Then for the abbreviation we either use ?eco? or ?inv? as the > abbreviation instead of ?humboldt? or ?hmbldt?. That would make the IRIs > either > > http://rs.tdwg.org/eco/term/foo > > or > > http://rs.tdwg.org/inv/term/foo > > > > which would be abbreviated as ?eco:foo? or ?inv:foo? respectively, > following the established patterns we already are using in TDWG. > > > > This would have the added benefit of not confusing anybody if we suddenly > discover that Humboldt was an evil space alien or something and decide we > don?t want to name the extension after him anymore. Yes, I know that sounds > weird, but Audubon Core is rebranding as Audiovisual Core and fortunately > we can still use ?ac:? without confusing anybody. This solution would also > dodge that potential future problem. > > > > I haven?t checked to see if ?eco? or ?inv? are already being used by any > well-known vocabularies, but I?ll do that if this idea gets any traction. > > > > Thoughts? > > > > -- > > Steven J. Baskauf, Ph.D. he/him/his > > Data Science and Data Curation Specialist / Librarian III > > 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 on behalf of > ys628 > *Reply-To: *Humboldt Core TG > *Date: *Tuesday, February 14, 2023 at 1:55 PM > *To: *Humboldt Core TG , "wmh6 at cornell.edu" > > *Subject: *[tdwg-humboldt] Humboldt Task Group Meeting Wed 15 February > 2023, 08:00 EST/13:00 UTC > > > > Hi valentines! > > > > I hope everybody is great. > > > > Let meet tomorrow and discuss the following items: > > - review *taxonomic scope related terms *(see slide 13 and 14 here > > ) > - discuss the need for *isReportedAbundanceAdditive (?)* (slide 15 here > ) > --> john is still thinking about this > - discuss the need for *IdentificationConfidence *(slide 15 here > > ) > - start writing the implementation report!! > > See you soon! > > > > Zoom link: https://yale.zoom.us/j/97318391101 > > > > > Yani > > > > Yanina V. Sica, PhD > > Lead Data Team > > Map of Life > > | Center for Biodiversity and Global Change > > > Yale University > > pronouns: she/her/hers > > *If you are receiving this email outside of your working hours, I am not > expecting you to read or respond.* > -------------- next part -------------- An HTML attachment was scrubbed... URL: From yanina.sica at gmail.com Wed Feb 15 20:59:43 2023 From: yanina.sica at gmail.com (Yanina Sica) Date: Wed, 15 Feb 2023 15:59:43 -0500 Subject: [tdwg-humboldt] Humboldt Extension namespace abbreviation In-Reply-To: References: <269A9C05-BDDA-40FE-8332-23C9297315F0@vanderbilt.edu> Message-ID: Great suggestion! I agree and am very supportive of the change in namespace removing Humboldt. Is a combination of your suggestions too much? ecoInv maybe? Yani On Wed, Feb 15, 2023 at 9:48 AM John Wieczorek wrote: > I really like your idea. Solves all kinds of issues. I'll be surprised if > "eco:" isn't already in common use, but if it isn't, we should jump on it. > > On Wed, Feb 15, 2023 at 11:44 AM Baskauf, Steven James < > steve.baskauf at vanderbilt.edu> wrote: > >> Hi all, >> >> >> >> This is a follow-up to the brief discussion at the end of our meeting >> today. I had an idea in the shower (where I frequently have creative >> thoughts ? must be something about being more relaxed) about what to use as >> a short abbreviation for Humboldt extension IRIs. As an official name for >> Humboldt, we call it the ?Humboldt Extension for Ecological Inventories? or >> something like that. That already has the benefit of telling people what >> it?s about. Then for the abbreviation we either use ?eco? or ?inv? as the >> abbreviation instead of ?humboldt? or ?hmbldt?. That would make the IRIs >> either >> >> http://rs.tdwg.org/eco/term/foo >> >> or >> >> http://rs.tdwg.org/inv/term/foo >> >> >> >> which would be abbreviated as ?eco:foo? or ?inv:foo? respectively, >> following the established patterns we already are using in TDWG. >> >> >> >> This would have the added benefit of not confusing anybody if we suddenly >> discover that Humboldt was an evil space alien or something and decide we >> don?t want to name the extension after him anymore. Yes, I know that sounds >> weird, but Audubon Core is rebranding as Audiovisual Core and fortunately >> we can still use ?ac:? without confusing anybody. This solution would also >> dodge that potential future problem. >> >> >> >> I haven?t checked to see if ?eco? or ?inv? are already being used by any >> well-known vocabularies, but I?ll do that if this idea gets any traction. >> >> >> >> Thoughts? >> >> >> >> -- >> >> Steven J. Baskauf, Ph.D. he/him/his >> >> Data Science and Data Curation Specialist / Librarian III >> >> 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 on behalf >> of ys628 >> *Reply-To: *Humboldt Core TG >> *Date: *Tuesday, February 14, 2023 at 1:55 PM >> *To: *Humboldt Core TG , "wmh6 at cornell.edu" >> >> *Subject: *[tdwg-humboldt] Humboldt Task Group Meeting Wed 15 February >> 2023, 08:00 EST/13:00 UTC >> >> >> >> Hi valentines! >> >> >> >> I hope everybody is great. >> >> >> >> Let meet tomorrow and discuss the following items: >> >> - review *taxonomic scope related terms *(see slide 13 and 14 here >> >> ) >> - discuss the need for *isReportedAbundanceAdditive (?)* (slide 15 >> here >> ) >> --> john is still thinking about this >> - discuss the need for *IdentificationConfidence *(slide 15 here >> >> ) >> - start writing the implementation report!! >> >> See you soon! >> >> >> >> Zoom link: https://yale.zoom.us/j/97318391101 >> >> >> >> >> Yani >> >> >> >> Yanina V. Sica, PhD >> >> Lead Data Team >> >> Map of Life >> >> | Center for Biodiversity and Global Change >> >> >> Yale University >> >> pronouns: she/her/hers >> >> *If you are receiving this email outside of your working hours, I am not >> expecting you to read or respond.* >> > _______________________________________________ > tdwg-humboldt mailing list > tdwg-humboldt at lists.tdwg.org > https://lists.tdwg.org/mailman/listinfo/tdwg-humboldt > -------------- next part -------------- An HTML attachment was scrubbed... URL: From steve.baskauf at vanderbilt.edu Wed Feb 15 15:02:23 2023 From: steve.baskauf at vanderbilt.edu (Baskauf, Steven James) Date: Wed, 15 Feb 2023 15:02:23 +0000 Subject: [tdwg-humboldt] Humboldt Extension namespace abbreviation In-Reply-To: References: <269A9C05-BDDA-40FE-8332-23C9297315F0@vanderbilt.edu> Message-ID: <528DA5D4-29FB-4BB9-B400-5254CFD320EE@vanderbilt.edu> I think shorter is better, although ecoinv: isn?t that long. The Linked Open Vocabularies https://lov.linkeddata.es/dataset/lov website, where I normally go to see what abbreviations people are using seems to be down. I don?t know if that is temporary or permanent. I?ll try check the various suggestions later. I agree with John that if eco: isn?t used, we should jump on it. It is simple and memorable. Steve -- Steven J. Baskauf, Ph.D. he/him/his Data Science and Data Curation Specialist / Librarian III 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: Yanina Sica Date: Wednesday, February 15, 2023 at 8:59 AM To: "tuco at berkeley.edu" , Humboldt Core TG Cc: Steve Baskauf , "wmh6 at cornell.edu" Subject: Re: [tdwg-humboldt] Humboldt Extension namespace abbreviation Great suggestion! I agree and am very supportive of the change in namespace removing Humboldt. Is a combination of your suggestions too much? ecoInv maybe? Yani On Wed, Feb 15, 2023 at 9:48 AM John Wieczorek > wrote: I really like your idea. Solves all kinds of issues. I'll be surprised if "eco:" isn't already in common use, but if it isn't, we should jump on it. On Wed, Feb 15, 2023 at 11:44 AM Baskauf, Steven James > wrote: Hi all, This is a follow-up to the brief discussion at the end of our meeting today. I had an idea in the shower (where I frequently have creative thoughts ? must be something about being more relaxed) about what to use as a short abbreviation for Humboldt extension IRIs. As an official name for Humboldt, we call it the ?Humboldt Extension for Ecological Inventories? or something like that. That already has the benefit of telling people what it?s about. Then for the abbreviation we either use ?eco? or ?inv? as the abbreviation instead of ?humboldt? or ?hmbldt?. That would make the IRIs either http://rs.tdwg.org/eco/term/foo or http://rs.tdwg.org/inv/term/foo which would be abbreviated as ?eco:foo? or ?inv:foo? respectively, following the established patterns we already are using in TDWG. This would have the added benefit of not confusing anybody if we suddenly discover that Humboldt was an evil space alien or something and decide we don?t want to name the extension after him anymore. Yes, I know that sounds weird, but Audubon Core is rebranding as Audiovisual Core and fortunately we can still use ?ac:? without confusing anybody. This solution would also dodge that potential future problem. I haven?t checked to see if ?eco? or ?inv? are already being used by any well-known vocabularies, but I?ll do that if this idea gets any traction. Thoughts? -- Steven J. Baskauf, Ph.D. he/him/his Data Science and Data Curation Specialist / Librarian III 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 > on behalf of ys628 > Reply-To: Humboldt Core TG > Date: Tuesday, February 14, 2023 at 1:55 PM To: Humboldt Core TG >, "wmh6 at cornell.edu" > Subject: [tdwg-humboldt] Humboldt Task Group Meeting Wed 15 February 2023, 08:00 EST/13:00 UTC Hi valentines! I hope everybody is great. Let meet tomorrow and discuss the following items: * review taxonomic scope related terms (see slide 13 and 14 here) * discuss the need for isReportedAbundanceAdditive (?) (slide 15 here) --> john is still thinking about this * discuss the need for IdentificationConfidence (slide 15 here) * start writing the implementation report!! See you soon! Zoom link: https://yale.zoom.us/j/97318391101 Yani Yanina V. Sica, PhD Lead Data Team Map of Life | Center for Biodiversity and Global Change Yale University pronouns: she/her/hers If you are receiving this email outside of your working hours, I am not expecting you to read or respond. _______________________________________________ tdwg-humboldt mailing list tdwg-humboldt at lists.tdwg.org https://lists.tdwg.org/mailman/listinfo/tdwg-humboldt -------------- next part -------------- An HTML attachment was scrubbed... URL: From steve.baskauf at vanderbilt.edu Wed Feb 15 15:36:16 2023 From: steve.baskauf at vanderbilt.edu (Baskauf, Steven James) Date: Wed, 15 Feb 2023 15:36:16 +0000 Subject: [tdwg-humboldt] Humboldt Extension namespace abbreviation In-Reply-To: References: <269A9C05-BDDA-40FE-8332-23C9297315F0@vanderbilt.edu> <528DA5D4-29FB-4BB9-B400-5254CFD320EE@vanderbilt.edu> Message-ID: Forwarding Wesley?s message, which bounced from the HCTG email list. -- Steven J. Baskauf, Ph.D. he/him/his Data Science and Data Curation Specialist / Librarian III 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: "Wesley M. Hochachka" Date: Wednesday, February 15, 2023 at 9:27 AM To: Steve Baskauf , Yanina Sica , "tuco at berkeley.edu" , Humboldt Core TG Subject: Re: [tdwg-humboldt] Humboldt Extension namespace abbreviation HI all, I'm slightly more inclined toward "ecoinv", because "eco" by itself feels to me like it is too generic. Darwin Core, for example, also contains ecological data, and "ecology" and "ecological" have all sorts of meanings even in English, and the meanings are even more diverse when one starts to look at other languages (e.g. "?ko", the German-language equivalent to "eco" refers to organic food). Of source, "eco" is still a clearer descriptor of a type of information content than "Darwin", which in addition to being a surname is a surname associated with evolutionary more than ecological phenomena. Anyway, either "eco" or "ecoinv" feel appropriate to me, and thinking laterally from the name "Humboldt" was a great idea. Wesley ******************* Wesley Hochachka Senior Research Associate Cornell Lab of Ornithology ph. (607) 254-2484 ******************* ________________________________ From: Baskauf, Steven James Sent: Wednesday, February 15, 2023 10:02 To: Yanina Sica ; tuco at berkeley.edu ; Humboldt Core TG Cc: Wesley M. Hochachka Subject: Re: [tdwg-humboldt] Humboldt Extension namespace abbreviation I think shorter is better, although ecoinv: isn?t that long. The Linked Open Vocabularies https://lov.linkeddata.es/dataset/lov website, where I normally go to see what abbreviations people are using seems to be down. I don?t know if that is temporary or permanent. I?ll try check the various suggestions later. I agree with John that if eco: isn?t used, we should jump on it. It is simple and memorable. Steve -- Steven J. Baskauf, Ph.D. he/him/his Data Science and Data Curation Specialist / Librarian III 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: Yanina Sica Date: Wednesday, February 15, 2023 at 8:59 AM To: "tuco at berkeley.edu" , Humboldt Core TG Cc: Steve Baskauf , "wmh6 at cornell.edu" Subject: Re: [tdwg-humboldt] Humboldt Extension namespace abbreviation Great suggestion! I agree and am very supportive of the change in namespace removing Humboldt. Is a combination of your suggestions too much? ecoInv maybe? Yani On Wed, Feb 15, 2023 at 9:48 AM John Wieczorek > wrote: I really like your idea. Solves all kinds of issues. I'll be surprised if "eco:" isn't already in common use, but if it isn't, we should jump on it. On Wed, Feb 15, 2023 at 11:44 AM Baskauf, Steven James > wrote: Hi all, This is a follow-up to the brief discussion at the end of our meeting today. I had an idea in the shower (where I frequently have creative thoughts ? must be something about being more relaxed) about what to use as a short abbreviation for Humboldt extension IRIs. As an official name for Humboldt, we call it the ?Humboldt Extension for Ecological Inventories? or something like that. That already has the benefit of telling people what it?s about. Then for the abbreviation we either use ?eco? or ?inv? as the abbreviation instead of ?humboldt? or ?hmbldt?. That would make the IRIs either http://rs.tdwg.org/eco/term/foo or http://rs.tdwg.org/inv/term/foo which would be abbreviated as ?eco:foo? or ?inv:foo? respectively, following the established patterns we already are using in TDWG. This would have the added benefit of not confusing anybody if we suddenly discover that Humboldt was an evil space alien or something and decide we don?t want to name the extension after him anymore. Yes, I know that sounds weird, but Audubon Core is rebranding as Audiovisual Core and fortunately we can still use ?ac:? without confusing anybody. This solution would also dodge that potential future problem. I haven?t checked to see if ?eco? or ?inv? are already being used by any well-known vocabularies, but I?ll do that if this idea gets any traction. Thoughts? -- Steven J. Baskauf, Ph.D. he/him/his Data Science and Data Curation Specialist / Librarian III 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 > on behalf of ys628 > Reply-To: Humboldt Core TG > Date: Tuesday, February 14, 2023 at 1:55 PM To: Humboldt Core TG >, "wmh6 at cornell.edu" > Subject: [tdwg-humboldt] Humboldt Task Group Meeting Wed 15 February 2023, 08:00 EST/13:00 UTC Hi valentines! I hope everybody is great. Let meet tomorrow and discuss the following items: * review taxonomic scope related terms (see slide 13 and 14 here) * discuss the need for isReportedAbundanceAdditive (?) (slide 15 here) --> john is still thinking about this * discuss the need for IdentificationConfidence (slide 15 here) * start writing the implementation report!! See you soon! Zoom link: https://yale.zoom.us/j/97318391101 Yani Yanina V. Sica, PhD Lead Data Team Map of Life | Center for Biodiversity and Global Change Yale University pronouns: she/her/hers If you are receiving this email outside of your working hours, I am not expecting you to read or respond. _______________________________________________ tdwg-humboldt mailing list tdwg-humboldt at lists.tdwg.org https://lists.tdwg.org/mailman/listinfo/tdwg-humboldt -------------- next part -------------- An HTML attachment was scrubbed... URL: From steve.baskauf at vanderbilt.edu Wed Feb 15 18:24:11 2023 From: steve.baskauf at vanderbilt.edu (Baskauf, Steven James) Date: Wed, 15 Feb 2023 18:24:11 +0000 Subject: [tdwg-humboldt] Humboldt Extension namespace abbreviation In-Reply-To: References: <269A9C05-BDDA-40FE-8332-23C9297315F0@vanderbilt.edu> <528DA5D4-29FB-4BB9-B400-5254CFD320EE@vanderbilt.edu> Message-ID: Hi all, LOV is back up again: https://lov.linkeddata.es/ I checked the vocabs https://lov.linkeddata.es/dataset/lov/vocabs for ?eco?, ?env?, and ?ecoenv? and did not see any usage. However, I also checked dwc and ac and they don?t come up either (not sure why, I think I submitted them long ago). So that doesn?t mean for sure that they aren?t being used. Steve -- Steven J. Baskauf, Ph.D. he/him/his Data Science and Data Curation Specialist / Librarian III 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: "Wesley M. Hochachka" Date: Wednesday, February 15, 2023 at 9:27 AM To: Steve Baskauf , Yanina Sica , "tuco at berkeley.edu" , Humboldt Core TG Subject: Re: [tdwg-humboldt] Humboldt Extension namespace abbreviation HI all, I'm slightly more inclined toward "ecoinv", because "eco" by itself feels to me like it is too generic. Darwin Core, for example, also contains ecological data, and "ecology" and "ecological" have all sorts of meanings even in English, and the meanings are even more diverse when one starts to look at other languages (e.g. "?ko", the German-language equivalent to "eco" refers to organic food). Of source, "eco" is still a clearer descriptor of a type of information content than "Darwin", which in addition to being a surname is a surname associated with evolutionary more than ecological phenomena. Anyway, either "eco" or "ecoinv" feel appropriate to me, and thinking laterally from the name "Humboldt" was a great idea. Wesley ******************* Wesley Hochachka Senior Research Associate Cornell Lab of Ornithology ph. (607) 254-2484 ******************* ________________________________ From: Baskauf, Steven James Sent: Wednesday, February 15, 2023 10:02 To: Yanina Sica ; tuco at berkeley.edu ; Humboldt Core TG Cc: Wesley M. Hochachka Subject: Re: [tdwg-humboldt] Humboldt Extension namespace abbreviation I think shorter is better, although ecoinv: isn?t that long. The Linked Open Vocabularies https://lov.linkeddata.es/dataset/lov website, where I normally go to see what abbreviations people are using seems to be down. I don?t know if that is temporary or permanent. I?ll try check the various suggestions later. I agree with John that if eco: isn?t used, we should jump on it. It is simple and memorable. Steve -- Steven J. Baskauf, Ph.D. he/him/his Data Science and Data Curation Specialist / Librarian III 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: Yanina Sica Date: Wednesday, February 15, 2023 at 8:59 AM To: "tuco at berkeley.edu" , Humboldt Core TG Cc: Steve Baskauf , "wmh6 at cornell.edu" Subject: Re: [tdwg-humboldt] Humboldt Extension namespace abbreviation Great suggestion! I agree and am very supportive of the change in namespace removing Humboldt. Is a combination of your suggestions too much? ecoInv maybe? Yani On Wed, Feb 15, 2023 at 9:48 AM John Wieczorek > wrote: I really like your idea. Solves all kinds of issues. I'll be surprised if "eco:" isn't already in common use, but if it isn't, we should jump on it. On Wed, Feb 15, 2023 at 11:44 AM Baskauf, Steven James > wrote: Hi all, This is a follow-up to the brief discussion at the end of our meeting today. I had an idea in the shower (where I frequently have creative thoughts ? must be something about being more relaxed) about what to use as a short abbreviation for Humboldt extension IRIs. As an official name for Humboldt, we call it the ?Humboldt Extension for Ecological Inventories? or something like that. That already has the benefit of telling people what it?s about. Then for the abbreviation we either use ?eco? or ?inv? as the abbreviation instead of ?humboldt? or ?hmbldt?. That would make the IRIs either http://rs.tdwg.org/eco/term/foo or http://rs.tdwg.org/inv/term/foo which would be abbreviated as ?eco:foo? or ?inv:foo? respectively, following the established patterns we already are using in TDWG. This would have the added benefit of not confusing anybody if we suddenly discover that Humboldt was an evil space alien or something and decide we don?t want to name the extension after him anymore. Yes, I know that sounds weird, but Audubon Core is rebranding as Audiovisual Core and fortunately we can still use ?ac:? without confusing anybody. This solution would also dodge that potential future problem. I haven?t checked to see if ?eco? or ?inv? are already being used by any well-known vocabularies, but I?ll do that if this idea gets any traction. Thoughts? -- Steven J. Baskauf, Ph.D. he/him/his Data Science and Data Curation Specialist / Librarian III 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 > on behalf of ys628 > Reply-To: Humboldt Core TG > Date: Tuesday, February 14, 2023 at 1:55 PM To: Humboldt Core TG >, "wmh6 at cornell.edu" > Subject: [tdwg-humboldt] Humboldt Task Group Meeting Wed 15 February 2023, 08:00 EST/13:00 UTC Hi valentines! I hope everybody is great. Let meet tomorrow and discuss the following items: * review taxonomic scope related terms (see slide 13 and 14 here) * discuss the need for isReportedAbundanceAdditive (?) (slide 15 here) --> john is still thinking about this * discuss the need for IdentificationConfidence (slide 15 here) * start writing the implementation report!! See you soon! Zoom link: https://yale.zoom.us/j/97318391101 Yani Yanina V. Sica, PhD Lead Data Team Map of Life | Center for Biodiversity and Global Change Yale University pronouns: she/her/hers If you are receiving this email outside of your working hours, I am not expecting you to read or respond. _______________________________________________ tdwg-humboldt mailing list tdwg-humboldt at lists.tdwg.org https://lists.tdwg.org/mailman/listinfo/tdwg-humboldt -------------- next part -------------- An HTML attachment was scrubbed... URL: From tuco at berkeley.edu Wed Feb 15 19:20:10 2023 From: tuco at berkeley.edu (John Wieczorek) Date: Wed, 15 Feb 2023 16:20:10 -0300 Subject: [tdwg-humboldt] Humboldt Extension namespace abbreviation In-Reply-To: References: <269A9C05-BDDA-40FE-8332-23C9297315F0@vanderbilt.edu> <528DA5D4-29FB-4BB9-B400-5254CFD320EE@vanderbilt.edu>

Message-ID: Meanwhile, I asked ChatGPT, 'To your knowledge is there any namespace abbreviation "eco:" in common use?' To which it replied, 'I'm not aware of any widely recognized or commonly used namespace abbreviation "eco:" that has a specific or standardized meaning. However, namespace abbreviations can be used in various contexts, such as in XML or RDF documents, and may have specific meanings within those contexts. It's possible that "eco:" is used as a namespace abbreviation within a specific community or domain, but without more information about the context or purpose, it's difficult to determine its meaning.' Then I asked, by way of gauging it's depth of knowledge, 'What about "envo:"?' To which it replied, 'Yes, "envo:" is a commonly used namespace abbreviation that refers to the "Environment Ontology" (ENVO), which is a community-driven ontology that provides standard terminology for describing environmental systems. The "envo:" namespace is used to identify terms in the ENVO ontology within various contexts, such as in RDF and OWL documents. The ENVO ontology is widely used in the life sciences, particularly in the fields of ecology, microbiology, and biodiversity research, to enable data integration and interoperability across different datasets and research domains.' Then, 'And "dwc:"?' To which it replied: 'Yes, "dwc:" is also a commonly used namespace abbreviation that refers to the "Darwin Core" standard. The Darwin Core is a set of standards for sharing biodiversity and ecological data, and is widely used in the life sciences and natural history communities. The "dwc:" namespace is used to identify terms in the Darwin Core standard within various contexts, such as in RDF and XML documents. The Darwin Core standard provides a set of terms for describing various aspects of biodiversity and ecological data, such as taxonomic names, geographic locations, and measurements of organismal traits. The use of the Darwin Core standard and the "dwc:" namespace abbreviation enables data integration and interoperability across different datasets and research domains.' So, finally, 'And "ecoinv:"?' To which it replied, 'The namespace abbreviation "ecoinv:" does not appear to have a widely recognized or commonly used meaning in the scientific community or in the context of data standards. It's possible that "ecoinv:" is used as a namespace abbreviation within a specific project or domain, but without more information about the context or purpose, it's difficult to determine its meaning. It's worth noting that the use of namespace abbreviations can vary depending on the context, and there may be multiple different meanings or uses for a given namespace abbreviation.' On Wed, Feb 15, 2023 at 3:24 PM Baskauf, Steven James < steve.baskauf at vanderbilt.edu> wrote: > Hi all, > > > > LOV is back up again: https://lov.linkeddata.es/ > > > > I checked the vocabs https://lov.linkeddata.es/dataset/lov/vocabs > > > > for ?eco?, ?env?, and ?ecoenv? and did not see any usage. However, I also > checked dwc and ac and they don?t come up either (not sure why, I think I > submitted them long ago). So that doesn?t mean for sure that they aren?t > being used. > > > > Steve > > > > -- > > Steven J. Baskauf, Ph.D. he/him/his > > Data Science and Data Curation Specialist / Librarian III > > Jean & Alexander Heard Libraries, Vanderbilt University > > Nashville, TN 37235, USA > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Peter.Brenton at csiro.au Wed Feb 15 23:00:02 2023 From: Peter.Brenton at csiro.au (Brenton, Peter (NCMI, Black Mountain)) Date: Wed, 15 Feb 2023 23:00:02 +0000 Subject: [tdwg-humboldt] Humboldt Extension namespace abbreviation In-Reply-To: References: <269A9C05-BDDA-40FE-8332-23C9297315F0@vanderbilt.edu> Message-ID: I?m supportive of this too and I like ?eco? more than any of the other proposed abbreviations. However, as John suggests, that might already be taken. If eco is not available, perhaps using ?inventory? in full would be more intuitive and explicit. Peter From: tdwg-humboldt On Behalf Of Yanina Sica Sent: Thursday, 16 February 2023 8:00 AM To: tuco at berkeley.edu; Humboldt Core TG Cc: wmh6 at cornell.edu Subject: Re: [tdwg-humboldt] Humboldt Extension namespace abbreviation Great suggestion! I agree and am very supportive of the change in namespace removing Humboldt. Is a combination of your suggestions too much? ecoInv maybe? Yani On Wed, Feb 15, 2023 at 9:48 AM John Wieczorek > wrote: I really like your idea. Solves all kinds of issues. I'll be surprised if "eco:" isn't already in common use, but if it isn't, we should jump on it. On Wed, Feb 15, 2023 at 11:44 AM Baskauf, Steven James > wrote: Hi all, This is a follow-up to the brief discussion at the end of our meeting today. I had an idea in the shower (where I frequently have creative thoughts ? must be something about being more relaxed) about what to use as a short abbreviation for Humboldt extension IRIs. As an official name for Humboldt, we call it the ?Humboldt Extension for Ecological Inventories? or something like that. That already has the benefit of telling people what it?s about. Then for the abbreviation we either use ?eco? or ?inv? as the abbreviation instead of ?humboldt? or ?hmbldt?. That would make the IRIs either http://rs.tdwg.org/eco/term/foo or http://rs.tdwg.org/inv/term/foo which would be abbreviated as ?eco:foo? or ?inv:foo? respectively, following the established patterns we already are using in TDWG. This would have the added benefit of not confusing anybody if we suddenly discover that Humboldt was an evil space alien or something and decide we don?t want to name the extension after him anymore. Yes, I know that sounds weird, but Audubon Core is rebranding as Audiovisual Core and fortunately we can still use ?ac:? without confusing anybody. This solution would also dodge that potential future problem. I haven?t checked to see if ?eco? or ?inv? are already being used by any well-known vocabularies, but I?ll do that if this idea gets any traction. Thoughts? -- Steven J. Baskauf, Ph.D. he/him/his Data Science and Data Curation Specialist / Librarian III 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 > on behalf of ys628 > Reply-To: Humboldt Core TG > Date: Tuesday, February 14, 2023 at 1:55 PM To: Humboldt Core TG >, "wmh6 at cornell.edu" > Subject: [tdwg-humboldt] Humboldt Task Group Meeting Wed 15 February 2023, 08:00 EST/13:00 UTC Hi valentines! I hope everybody is great. Let meet tomorrow and discuss the following items: * review taxonomic scope related terms (see slide 13 and 14 here) * discuss the need for isReportedAbundanceAdditive (?) (slide 15 here) --> john is still thinking about this * discuss the need for IdentificationConfidence (slide 15 here) * start writing the implementation report!! See you soon! Zoom link: https://yale.zoom.us/j/97318391101 Yani Yanina V. Sica, PhD Lead Data Team Map of Life | Center for Biodiversity and Global Change Yale University pronouns: she/her/hers If you are receiving this email outside of your working hours, I am not expecting you to read or respond. _______________________________________________ tdwg-humboldt mailing list tdwg-humboldt at lists.tdwg.org https://lists.tdwg.org/mailman/listinfo/tdwg-humboldt -------------- next part -------------- An HTML attachment was scrubbed... URL: From Peter.Brenton at csiro.au Wed Feb 15 23:05:44 2023 From: Peter.Brenton at csiro.au (Brenton, Peter (NCMI, Black Mountain)) Date: Wed, 15 Feb 2023 23:05:44 +0000 Subject: [tdwg-humboldt] Humboldt Extension namespace abbreviation In-Reply-To: References: <269A9C05-BDDA-40FE-8332-23C9297315F0@vanderbilt.edu> Message-ID: I should have taken the time to fully read the whole thread and other related emails before commenting, there seems to be general agreement to settle on something more descriptive anyway. I?m cool with majority view. Peter From: Brenton, Peter (NCMI, Black Mountain) Sent: Thursday, 16 February 2023 10:00 AM To: Humboldt Core TG ; tuco at berkeley.edu Cc: wmh6 at cornell.edu Subject: RE: [tdwg-humboldt] Humboldt Extension namespace abbreviation I?m supportive of this too and I like ?eco? more than any of the other proposed abbreviations. However, as John suggests, that might already be taken. If eco is not available, perhaps using ?inventory? in full would be more intuitive and explicit. Peter From: tdwg-humboldt > On Behalf Of Yanina Sica Sent: Thursday, 16 February 2023 8:00 AM To: tuco at berkeley.edu; Humboldt Core TG > Cc: wmh6 at cornell.edu Subject: Re: [tdwg-humboldt] Humboldt Extension namespace abbreviation Great suggestion! I agree and am very supportive of the change in namespace removing Humboldt. Is a combination of your suggestions too much? ecoInv maybe? Yani On Wed, Feb 15, 2023 at 9:48 AM John Wieczorek > wrote: I really like your idea. Solves all kinds of issues. I'll be surprised if "eco:" isn't already in common use, but if it isn't, we should jump on it. On Wed, Feb 15, 2023 at 11:44 AM Baskauf, Steven James > wrote: Hi all, This is a follow-up to the brief discussion at the end of our meeting today. I had an idea in the shower (where I frequently have creative thoughts ? must be something about being more relaxed) about what to use as a short abbreviation for Humboldt extension IRIs. As an official name for Humboldt, we call it the ?Humboldt Extension for Ecological Inventories? or something like that. That already has the benefit of telling people what it?s about. Then for the abbreviation we either use ?eco? or ?inv? as the abbreviation instead of ?humboldt? or ?hmbldt?. That would make the IRIs either http://rs.tdwg.org/eco/term/foo or http://rs.tdwg.org/inv/term/foo which would be abbreviated as ?eco:foo? or ?inv:foo? respectively, following the established patterns we already are using in TDWG. This would have the added benefit of not confusing anybody if we suddenly discover that Humboldt was an evil space alien or something and decide we don?t want to name the extension after him anymore. Yes, I know that sounds weird, but Audubon Core is rebranding as Audiovisual Core and fortunately we can still use ?ac:? without confusing anybody. This solution would also dodge that potential future problem. I haven?t checked to see if ?eco? or ?inv? are already being used by any well-known vocabularies, but I?ll do that if this idea gets any traction. Thoughts? -- Steven J. Baskauf, Ph.D. he/him/his Data Science and Data Curation Specialist / Librarian III 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 > on behalf of ys628 > Reply-To: Humboldt Core TG > Date: Tuesday, February 14, 2023 at 1:55 PM To: Humboldt Core TG >, "wmh6 at cornell.edu" > Subject: [tdwg-humboldt] Humboldt Task Group Meeting Wed 15 February 2023, 08:00 EST/13:00 UTC Hi valentines! I hope everybody is great. Let meet tomorrow and discuss the following items: * review taxonomic scope related terms (see slide 13 and 14 here) * discuss the need for isReportedAbundanceAdditive (?) (slide 15 here) --> john is still thinking about this * discuss the need for IdentificationConfidence (slide 15 here) * start writing the implementation report!! See you soon! Zoom link: https://yale.zoom.us/j/97318391101 Yani Yanina V. Sica, PhD Lead Data Team Map of Life | Center for Biodiversity and Global Change Yale University pronouns: she/her/hers If you are receiving this email outside of your working hours, I am not expecting you to read or respond. _______________________________________________ tdwg-humboldt mailing list tdwg-humboldt at lists.tdwg.org https://lists.tdwg.org/mailman/listinfo/tdwg-humboldt -------------- next part -------------- An HTML attachment was scrubbed... URL: From ymgan at naturalsciences.be Thu Feb 16 14:39:46 2023 From: ymgan at naturalsciences.be (Yi Ming Gan) Date: Thu, 16 Feb 2023 14:39:46 +0000 Subject: [tdwg-humboldt] Humboldt Extension namespace abbreviation In-Reply-To: References: <269A9C05-BDDA-40FE-8332-23C9297315F0@vanderbilt.edu> Message-ID: +1 with Peter :) I feel threatened by the intelligence of ChatGPT hahaha! I also like ?eco?! ?inv? is nice too but I feel like not everyone uses the term inventory, so ?inv? may not be intuitive for some. The first word that comes to my mind with ?inv? was ?invertebrate? hahaha! Thanks for thinking about this Steve! Happy to hear that this team is in your mind even during shower! Cheers Ming On 16 Feb 2023, at 00:05, Brenton, Peter (NCMI, Black Mountain) wrote: I should have taken the time to fully read the whole thread and other related emails before commenting, there seems to be general agreement to settle on something more descriptive anyway. I?m cool with majority view. Peter From: Brenton, Peter (NCMI, Black Mountain) Sent: Thursday, 16 February 2023 10:00 AM To: Humboldt Core TG ; tuco at berkeley.edu Cc: wmh6 at cornell.edu Subject: RE: [tdwg-humboldt] Humboldt Extension namespace abbreviation I?m supportive of this too and I like ?eco? more than any of the other proposed abbreviations. However, as John suggests, that might already be taken. If eco is not available, perhaps using ?inventory? in full would be more intuitive and explicit. Peter From: tdwg-humboldt > On Behalf Of Yanina Sica Sent: Thursday, 16 February 2023 8:00 AM To: tuco at berkeley.edu; Humboldt Core TG > Cc: wmh6 at cornell.edu Subject: Re: [tdwg-humboldt] Humboldt Extension namespace abbreviation Great suggestion! I agree and am very supportive of the change in namespace removing Humboldt. Is a combination of your suggestions too much? ecoInv maybe? Yani On Wed, Feb 15, 2023 at 9:48 AM John Wieczorek > wrote: I really like your idea. Solves all kinds of issues. I'll be surprised if "eco:" isn't already in common use, but if it isn't, we should jump on it. On Wed, Feb 15, 2023 at 11:44 AM Baskauf, Steven James > wrote: Hi all, This is a follow-up to the brief discussion at the end of our meeting today. I had an idea in the shower (where I frequently have creative thoughts ? must be something about being more relaxed) about what to use as a short abbreviation for Humboldt extension IRIs. As an official name for Humboldt, we call it the ?Humboldt Extension for Ecological Inventories? or something like that. That already has the benefit of telling people what it?s about. Then for the abbreviation we either use ?eco? or ?inv? as the abbreviation instead of ?humboldt? or ?hmbldt?. That would make the IRIs either http://rs.tdwg.org/eco/term/foo or http://rs.tdwg.org/inv/term/foo which would be abbreviated as ?eco:foo? or ?inv:foo? respectively, following the established patterns we already are using in TDWG. This would have the added benefit of not confusing anybody if we suddenly discover that Humboldt was an evil space alien or something and decide we don?t want to name the extension after him anymore. Yes, I know that sounds weird, but Audubon Core is rebranding as Audiovisual Core and fortunately we can still use ?ac:? without confusing anybody. This solution would also dodge that potential future problem. I haven?t checked to see if ?eco? or ?inv? are already being used by any well-known vocabularies, but I?ll do that if this idea gets any traction. Thoughts? -- Steven J. Baskauf, Ph.D. he/him/his Data Science and Data Curation Specialist / Librarian III 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 > on behalf of ys628 > Reply-To: Humboldt Core TG > Date: Tuesday, February 14, 2023 at 1:55 PM To: Humboldt Core TG >, "wmh6 at cornell.edu" > Subject: [tdwg-humboldt] Humboldt Task Group Meeting Wed 15 February 2023, 08:00 EST/13:00 UTC Hi valentines! I hope everybody is great. Let meet tomorrow and discuss the following items: * review taxonomic scope related terms (see slide 13 and 14 here) * discuss the need for isReportedAbundanceAdditive (?) (slide 15 here) --> john is still thinking about this * discuss the need for IdentificationConfidence (slide 15 here) * start writing the implementation report!! See you soon! Zoom link: https://yale.zoom.us/j/97318391101 Yani Yanina V. Sica, PhD Lead Data Team Map of Life | Center for Biodiversity and Global Change Yale University pronouns: she/her/hers If you are receiving this email outside of your working hours, I am not expecting you to read or respond. _______________________________________________ tdwg-humboldt mailing list tdwg-humboldt at lists.tdwg.org https://lists.tdwg.org/mailman/listinfo/tdwg-humboldt _______________________________________________ tdwg-humboldt mailing list tdwg-humboldt at lists.tdwg.org https://lists.tdwg.org/mailman/listinfo/tdwg-humboldt -------------- next part -------------- An HTML attachment was scrubbed... URL: From yanina.sica at yale.edu Thu Feb 16 20:13:50 2023 From: yanina.sica at yale.edu (ys628) Date: Thu, 16 Feb 2023 20:13:50 +0000 Subject: [tdwg-humboldt] Humboldt Extension namespace abbreviation In-Reply-To: References: <269A9C05-BDDA-40FE-8332-23C9297315F0@vanderbilt.edu>

Message-ID: Thanks for engaging so actively in this topic! (from getting ideas in the shower to artificial intelligence...this group is amazing!) I was not sure if everybody was getting the emails with the options and responses so I created a small survey to make sure everybody votes. It is anonymous (at least I think so..) and takes less than a minute. https://www.surveymonkey.com/r/humboldtTDWG We can discuss the results next week! best! Yanina V. Sica, PhD Lead Data Team Map of Life | Center for Biodiversity and Global Change Yale University pronouns: she/her/hers If you are receiving this email outside of your working hours, I am not expecting you to read or respond. ________________________________ From: tdwg-humboldt on behalf of Yi Ming Gan Sent: Thursday, February 16, 2023 9:39 AM To: Humboldt Core TG Cc: tuco at berkeley.edu ; wmh6 at cornell.edu Subject: Re: [tdwg-humboldt] Humboldt Extension namespace abbreviation +1 with Peter :) I feel threatened by the intelligence of ChatGPT hahaha! I also like ?eco?! ?inv? is nice too but I feel like not everyone uses the term inventory, so ?inv? may not be intuitive for some. The first word that comes to my mind with ?inv? was ?invertebrate? hahaha! Thanks for thinking about this Steve! Happy to hear that this team is in your mind even during shower! Cheers Ming On 16 Feb 2023, at 00:05, Brenton, Peter (NCMI, Black Mountain) wrote: I should have taken the time to fully read the whole thread and other related emails before commenting, there seems to be general agreement to settle on something more descriptive anyway. I?m cool with majority view. Peter From: Brenton, Peter (NCMI, Black Mountain) Sent: Thursday, 16 February 2023 10:00 AM To: Humboldt Core TG ; tuco at berkeley.edu Cc: wmh6 at cornell.edu Subject: RE: [tdwg-humboldt] Humboldt Extension namespace abbreviation I?m supportive of this too and I like ?eco? more than any of the other proposed abbreviations. However, as John suggests, that might already be taken. If eco is not available, perhaps using ?inventory? in full would be more intuitive and explicit. Peter From: tdwg-humboldt > On Behalf Of Yanina Sica Sent: Thursday, 16 February 2023 8:00 AM To: tuco at berkeley.edu; Humboldt Core TG > Cc: wmh6 at cornell.edu Subject: Re: [tdwg-humboldt] Humboldt Extension namespace abbreviation Great suggestion! I agree and am very supportive of the change in namespace removing Humboldt. Is a combination of your suggestions too much? ecoInv maybe? Yani On Wed, Feb 15, 2023 at 9:48 AM John Wieczorek > wrote: I really like your idea. Solves all kinds of issues. I'll be surprised if "eco:" isn't already in common use, but if it isn't, we should jump on it. On Wed, Feb 15, 2023 at 11:44 AM Baskauf, Steven James > wrote: Hi all, This is a follow-up to the brief discussion at the end of our meeting today. I had an idea in the shower (where I frequently have creative thoughts ? must be something about being more relaxed) about what to use as a short abbreviation for Humboldt extension IRIs. As an official name for Humboldt, we call it the ?Humboldt Extension for Ecological Inventories? or something like that. That already has the benefit of telling people what it?s about. Then for the abbreviation we either use ?eco? or ?inv? as the abbreviation instead of ?humboldt? or ?hmbldt?. That would make the IRIs either http://rs.tdwg.org/eco/term/foo or http://rs.tdwg.org/inv/term/foo which would be abbreviated as ?eco:foo? or ?inv:foo? respectively, following the established patterns we already are using in TDWG. This would have the added benefit of not confusing anybody if we suddenly discover that Humboldt was an evil space alien or something and decide we don?t want to name the extension after him anymore. Yes, I know that sounds weird, but Audubon Core is rebranding as Audiovisual Core and fortunately we can still use ?ac:? without confusing anybody. This solution would also dodge that potential future problem. I haven?t checked to see if ?eco? or ?inv? are already being used by any well-known vocabularies, but I?ll do that if this idea gets any traction. Thoughts? -- Steven J. Baskauf, Ph.D. he/him/his Data Science and Data Curation Specialist / Librarian III 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 > on behalf of ys628 > Reply-To: Humboldt Core TG > Date: Tuesday, February 14, 2023 at 1:55 PM To: Humboldt Core TG >, "wmh6 at cornell.edu" > Subject: [tdwg-humboldt] Humboldt Task Group Meeting Wed 15 February 2023, 08:00 EST/13:00 UTC Hi valentines! I hope everybody is great. Let meet tomorrow and discuss the following items: * review taxonomic scope related terms (see slide 13 and 14 here) * discuss the need for isReportedAbundanceAdditive (?) (slide 15 here) --> john is still thinking about this * discuss the need for IdentificationConfidence (slide 15 here) * start writing the implementation report!! See you soon! Zoom link: https://yale.zoom.us/j/97318391101 Yani Yanina V. Sica, PhD Lead Data Team Map of Life | Center for Biodiversity and Global Change Yale University pronouns: she/her/hers If you are receiving this email outside of your working hours, I am not expecting you to read or respond. _______________________________________________ tdwg-humboldt mailing list tdwg-humboldt at lists.tdwg.org https://lists.tdwg.org/mailman/listinfo/tdwg-humboldt _______________________________________________ tdwg-humboldt mailing list tdwg-humboldt at lists.tdwg.org https://lists.tdwg.org/mailman/listinfo/tdwg-humboldt -------------- next part -------------- An HTML attachment was scrubbed... URL: From yanina.sica at yale.edu Tue Feb 21 17:50:23 2023 From: yanina.sica at yale.edu (ys628) Date: Tue, 21 Feb 2023 17:50:23 +0000 Subject: [tdwg-humboldt] Humboldt Task Group Meeting Wed 22 February 2023, 08:00 EST/13:00 UTC Message-ID: Hallo! Hope everybody is good! In tomorrow's meeting, we need to start planning for the implementation report for TDWG. In order to do this, I will kindly ask you to: * review new scope related terms (see slide 14 here) * suggest ways to move forward with the term isReportedAbundanceAdditive (?) (slide 15 here) * Vote to change or not the namespace: https://www.surveymonkey.com/r/humboldtTDWv [https://www.surveymonkey.com/collect/images/default_custom_meta_image.jpg] Humboldt Extension (previously Humboldt Core) namespace abbreviation Take this survey powered by surveymonkey.com. Create your own surveys for free. www.surveymonkey.com See you soon! Zoom link: https://yale.zoom.us/j/97318391101 Yanina V. Sica, PhD Lead Data Team Map of Life | Center for Biodiversity and Global Change Yale University pronouns: she/her/hers If you are receiving this email outside of your working hours, I am not expecting you to read or respond. -------------- next part -------------- An HTML attachment was scrubbed... URL: