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" <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 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> 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> 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
From: tdwg-humboldt <tdwg-humboldt-bounces@lists.tdwg.org> on behalf of ys628 <yanina.sica@yale.edu>
Reply-To: Humboldt Core TG <tdwg-humboldt@lists.tdwg.org>
Date: Tuesday, February 14, 2023 at 1:55 PM
To: Humboldt Core TG <tdwg-humboldt@lists.tdwg.org>, "wmh6@cornell.edu" <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:
Yanina V. Sica, PhD
Lead Data Team
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
https://lists.tdwg.org/mailman/listinfo/tdwg-humboldt