Re: [tdwg-humboldt] Humboldt Extension namespace abbreviation
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" <wmh6@cornell.edu> Date: Wednesday, February 15, 2023 at 9:27 AM To: Steve Baskauf <steve.baskauf@vanderbilt.edu>, Yanina Sica <yanina.sica@gmail.com>, "tuco@berkeley.edu" <tuco@berkeley.edu>, Humboldt Core TG <tdwg-humboldt@lists.tdwg.org> 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 <steve.baskauf@vanderbilt.edu> Sent: Wednesday, February 15, 2023 10:02 To: Yanina Sica <yanina.sica@gmail.com>; tuco@berkeley.edu <tuco@berkeley.edu>; Humboldt Core TG <tdwg-humboldt@lists.tdwg.org> Cc: Wesley M. Hochachka <wmh6@cornell.edu> 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<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flov.linkeddata.es%2Fdataset%2Flov&data=05%7C01%7Csteve.baskauf%40vanderbilt.edu%7Cb889e01b1bab494de8f908db0f68a14c%7Cba5a7f39e3be4ab3b45067fa80faecad%7C0%7C0%7C638120716366256398%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=yfBEEs0Fk%2BqxXyImDKG28j18z14uL7XEdvxohzkCc1Y%3D&reserved=0> 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 <yanina.sica@gmail.com> Date: Wednesday, February 15, 2023 at 8:59 AM To: "tuco@berkeley.edu" <tuco@berkeley.edu>, Humboldt Core TG <tdwg-humboldt@lists.tdwg.org> Cc: Steve Baskauf <steve.baskauf@vanderbilt.edu>, "wmh6@cornell.edu" <wmh6@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 <tuco@berkeley.edu<mailto:tuco@berkeley.edu>> 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@vanderbilt.edu<mailto:steve.baskauf@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<https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Frs.tdwg.org%2Feco%2Fterm%2Ffoo&data=05%7C01%7Csteve.baskauf%40vanderbilt.edu%7Cb889e01b1bab494de8f908db0f68a14c%7Cba5a7f39e3be4ab3b45067fa80faecad%7C0%7C0%7C638120716366256398%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=nOJCkyNICt4OZ05pHaiKnINo9Mi9CaS%2FZCEuOCfUSJw%3D&reserved=0> or http://rs.tdwg.org/inv/term/foo<https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Frs.tdwg.org%2Finv%2Fterm%2Ffoo&data=05%7C01%7Csteve.baskauf%40vanderbilt.edu%7Cb889e01b1bab494de8f908db0f68a14c%7Cba5a7f39e3be4ab3b45067fa80faecad%7C0%7C0%7C638120716366256398%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=MVGOpcocsQxcZ6YGYuS9mVLkuCwdaKLFqJ3ekKuAxxQ%3D&reserved=0> 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/<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbaskauf.github.io%2F&data=05%7C01%7Csteve.baskauf%40vanderbilt.edu%7Cb889e01b1bab494de8f908db0f68a14c%7Cba5a7f39e3be4ab3b45067fa80faecad%7C0%7C0%7C638120716366256398%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2Fw4tE1f74sW3B%2F93mphlMz7tOk3qU37h1xV7lgMHtVk%3D&reserved=0> From: tdwg-humboldt <tdwg-humboldt-bounces@lists.tdwg.org<mailto:tdwg-humboldt-bounces@lists.tdwg.org>> on behalf of ys628 <yanina.sica@yale.edu<mailto:yanina.sica@yale.edu>> Reply-To: Humboldt Core TG <tdwg-humboldt@lists.tdwg.org<mailto:tdwg-humboldt@lists.tdwg.org>> Date: Tuesday, February 14, 2023 at 1:55 PM To: Humboldt Core TG <tdwg-humboldt@lists.tdwg.org<mailto:tdwg-humboldt@lists.tdwg.org>>, "wmh6@cornell.edu<mailto:wmh6@cornell.edu>" <wmh6@cornell.edu<mailto:wmh6@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<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.google.com%2Fpresentation%2Fd%2F18n83tttDvWDLI5UM30LIsfqrbpH5nbyrwIKjuUY_glE%2Fedit%23slide%3Did.g2037ee016fb_3_0&data=05%7C01%7Csteve.baskauf%40vanderbilt.edu%7Cb889e01b1bab494de8f908db0f68a14c%7Cba5a7f39e3be4ab3b45067fa80faecad%7C0%7C0%7C638120716366256398%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=4tZfK8Ln57M%2BmlmMtMXBPSxCiHIIf6qLSkEp2VKtj5U%3D&reserved=0>) * discuss the need for isReportedAbundanceAdditive (?) (slide 15 here<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.google.com%2Fpresentation%2Fd%2F18n83tttDvWDLI5UM30LIsfqrbpH5nbyrwIKjuUY_glE%2Fedit%23slide%3Did.g2037ee016fb_3_0&data=05%7C01%7Csteve.baskauf%40vanderbilt.edu%7Cb889e01b1bab494de8f908db0f68a14c%7Cba5a7f39e3be4ab3b45067fa80faecad%7C0%7C0%7C638120716366256398%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=4tZfK8Ln57M%2BmlmMtMXBPSxCiHIIf6qLSkEp2VKtj5U%3D&reserved=0>) --> john is still thinking about this * discuss the need for IdentificationConfidence (slide 15 here<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.google.com%2Fpresentation%2Fd%2F18n83tttDvWDLI5UM30LIsfqrbpH5nbyrwIKjuUY_glE%2Fedit%23slide%3Did.g2037ee016fb_3_0&data=05%7C01%7Csteve.baskauf%40vanderbilt.edu%7Cb889e01b1bab494de8f908db0f68a14c%7Cba5a7f39e3be4ab3b45067fa80faecad%7C0%7C0%7C638120716366256398%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=4tZfK8Ln57M%2BmlmMtMXBPSxCiHIIf6qLSkEp2VKtj5U%3D&reserved=0>) * start writing the implementation report!! See you soon! Zoom link: https://yale.zoom.us/j/97318391101<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Furl%3Fq%3Dhttps%3A%2F%2Fyale.zoom.us%2Fj%2F97318391101%26sa%3DD%26source%3Dcalendar%26usd%3D2%26usg%3DAOvVaw131_ZV9o-84ivZDjGbSTBJ&data=05%7C01%7Csteve.baskauf%40vanderbilt.edu%7Cb889e01b1bab494de8f908db0f68a14c%7Cba5a7f39e3be4ab3b45067fa80faecad%7C0%7C0%7C638120716366256398%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=3UvD%2FyoDxjrKwt6qtMOj5hW8RhvNJLNjIUIDe4PAkWI%3D&reserved=0> Yani Yanina V. Sica, PhD Lead Data Team Map of Life<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmol.org%2F&data=05%7C01%7Csteve.baskauf%40vanderbilt.edu%7Cb889e01b1bab494de8f908db0f68a14c%7Cba5a7f39e3be4ab3b45067fa80faecad%7C0%7C0%7C638120716366256398%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=NpzprMeQPSzTvwoopgZH2RU8kw8gAV6%2FivyOg5YiXaY%3D&reserved=0> | Center for Biodiversity and Global Change<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbgc.yale.edu%2F&data=05%7C01%7Csteve.baskauf%40vanderbilt.edu%7Cb889e01b1bab494de8f908db0f68a14c%7Cba5a7f39e3be4ab3b45067fa80faecad%7C0%7C0%7C638120716366412638%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=lUyypWoZghqB3n1vpZqv8Rf1VvXGB9Fe9BZ2DIdJCoQ%3D&reserved=0> 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@lists.tdwg.org<mailto:tdwg-humboldt@lists.tdwg.org> https://lists.tdwg.org/mailman/listinfo/tdwg-humboldt<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.tdwg.org%2Fmailman%2Flistinfo%2Ftdwg-humboldt&data=05%7C01%7Csteve.baskauf%40vanderbilt.edu%7Cb889e01b1bab494de8f908db0f68a14c%7Cba5a7f39e3be4ab3b45067fa80faecad%7C0%7C0%7C638120716366412638%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=e604OvVG74XbdjLc3Cu1pY3dduzC5PUOvEaO16%2FuNRQ%3D&reserved=0>
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@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
participants (2)
-
Baskauf, Steven James -
John Wieczorek