[Esip-semanticharmonization] Are people prepared for an ESIP Semantic Harmonization Cluster 2 hour group meeting in April

Wed Apr 3 18:15:38 EDT 2024

In the SemTech committee meetings we have briefly discussed a session: There will be demo/training from the KnowWhere KG group (Wenwen Li), Tyler Stevens is interested to talk about some recent work on GCMD keywords. My colleagues at University of Idaho are interested to present their work on semantics-infused data portals.
On Apr 09 there will be a council meeting and I can report that. Can also briefly report the work of the semantic harmonization group and the plan for the July meeting.

Best,
Marshall

Xiaogang (Marshall) Ma
Associate Professor, Computer Science
College of Engineering Dean’s Distinguished Fellow
University of Idaho

On Apr 3, 2024, at 11:27 AM, Gary Berg-Cross <gbergcross at gmail.com> wrote:

WARNING: Stop. Think. Read.
This message came from outside your organization.
Additional information about Email Warning Tags<https://support.uidaho.edu/TDClient/40/Portal/KB/ArticleDet?ID=2902>
The next Semantic Harmonization meeting is  scheduled for April 17 @ 4:00 PM - 6:00 PM EDT to again overlap with the SWEET meeting.
A Question is whether we will have the right people to be able to discuss CMECS and harmonization with both SWEET and ENVO.
To have a productive meeting we would need a course set of vocabulary items (Like Beach or sand  or habitat/Aquatic Setting areas like Estuarine System ) from CMECS  along with definitions and some idea about how they could align with SWEETand ENVO.
Having Kate and Pier available would be instrumental to a productive session.
So we should know if they are available before using this session for CMECS harmonization...and if they have a start on a core vocabulary.

Below is a small example illustrating Beach as an concept in ENVO and CMECS.

surface landform<https://urldefense.com/v3/__https://ontobee.org/ontology/ENVO?iri=http:**Apurl.obolibrary.org*obo*ENVO_01001884__;Ly8vLw!!JYXjzlvb!lNf0RtlWVQC0B7NclX2lZwPdetO21qdA-b7JUGYwExobwa7Rlm8WpYoV5x9WDRzjLwtTpP2su6EDDHvbOQ$> in  Envo

  *
+ beach<https://urldefense.com/v3/__https://ontobee.org/ontology/ENVO?iri=http:**Apurl.obolibrary.org*obo*ENVO_00000091__;Ly8vLw!!JYXjzlvb!lNf0RtlWVQC0B7NclX2lZwPdetO21qdA-b7JUGYwExobwa7Rlm8WpYoV5x9WDRzjLwtTpP2su6G5Utwkpw$> A landform consisting of loose rock particles such as sand, gravel, shingle, pebbles, cobble, or even shell fragments along the shoreline of a body of water.
  *
surface landform<https://urldefense.com/v3/__https://ontobee.org/ontology/ENVO?iri=http:**Apurl.obolibrary.org*obo*ENVO_01001884__;Ly8vLw!!JYXjzlvb!lNf0RtlWVQC0B7NclX2lZwPdetO21qdA-b7JUGYwExobwa7Rlm8WpYoV5x9WDRzjLwtTpP2su6EDDHvbOQ$>

  *
part of<https://urldefense.com/v3/__https://ontobee.org/ontology/ENVO?iri=http:**Apurl.obolibrary.org*obo*BFO_0000050__;Ly8vLw!!JYXjzlvb!lNf0RtlWVQC0B7NclX2lZwPdetO21qdA-b7JUGYwExobwa7Rlm8WpYoV5x9WDRzjLwtTpP2su6Gg5wZvhQ$> some shore<https://urldefense.com/v3/__https://ontobee.org/ontology/ENVO?iri=http:**Apurl.obolibrary.org*obo*ENVO_00000304__;Ly8vLw!!JYXjzlvb!lNf0RtlWVQC0B7NclX2lZwPdetO21qdA-b7JUGYwExobwa7Rlm8WpYoV5x9WDRzjLwtTpP2su6GGEZv21w$>
  *
composed primarily of<https://urldefense.com/v3/__https://ontobee.org/ontology/ENVO?iri=http:**Apurl.obolibrary.org*obo*RO_0002473__;Ly8vLw!!JYXjzlvb!lNf0RtlWVQC0B7NclX2lZwPdetO21qdA-b7JUGYwExobwa7Rlm8WpYoV5x9WDRzjLwtTpP2su6Fj-IMB0g$> some (sediment<https://urldefense.com/v3/__https://ontobee.org/ontology/ENVO?iri=http:**Apurl.obolibrary.org*obo*ENVO_00002007__;Ly8vLw!!JYXjzlvb!lNf0RtlWVQC0B7NclX2lZwPdetO21qdA-b7JUGYwExobwa7Rlm8WpYoV5x9WDRzjLwtTpP2su6H0-CDs7Q$> and (composed primarily of<https://urldefense.com/v3/__https://ontobee.org/ontology/ENVO?iri=http:**Apurl.obolibrary.org*obo*RO_0002473__;Ly8vLw!!JYXjzlvb!lNf0RtlWVQC0B7NclX2lZwPdetO21qdA-b7JUGYwExobwa7Rlm8WpYoV5x9WDRzjLwtTpP2su6Fj-IMB0g$> some (pebble<https://urldefense.com/v3/__https://ontobee.org/ontology/ENVO?iri=http:**Apurl.obolibrary.org*obo*ENVO_00002139__;Ly8vLw!!JYXjzlvb!lNf0RtlWVQC0B7NclX2lZwPdetO21qdA-b7JUGYwExobwa7Rlm8WpYoV5x9WDRzjLwtTpP2su6HaQh6lyw$> or cobble<https://urldefense.com/v3/__https://ontobee.org/ontology/ENVO?iri=http:**Apurl.obolibrary.org*obo*ENVO_00002140__;Ly8vLw!!JYXjzlvb!lNf0RtlWVQC0B7NclX2lZwPdetO21qdA-b7JUGYwExobwa7Rlm8WpYoV5x9WDRzjLwtTpP2su6HQQ0uqRw$> or sand<https://urldefense.com/v3/__https://ontobee.org/ontology/ENVO?iri=http:**Apurl.obolibrary.org*obo*ENVO_01000017__;Ly8vLw!!JYXjzlvb!lNf0RtlWVQC0B7NclX2lZwPdetO21qdA-b7JUGYwExobwa7Rlm8WpYoV5x9WDRzjLwtTpP2su6Fa8p5N8A$> or gravel<https://urldefense.com/v3/__https://ontobee.org/ontology/ENVO?iri=http:**Apurl.obolibrary.org*obo*ENVO_01000018__;Ly8vLw!!JYXjzlvb!lNf0RtlWVQC0B7NclX2lZwPdetO21qdA-b7JUGYwExobwa7Rlm8WpYoV5x9WDRzjLwtTpP2su6EEKdsDPQ$> or shell<https://urldefense.com/v3/__https://ontobee.org/ontology/ENVO?iri=http:**Apurl.obolibrary.org*obo*UBERON_0006612__;Ly8vLw!!JYXjzlvb!lNf0RtlWVQC0B7NclX2lZwPdetO21qdA-b7JUGYwExobwa7Rlm8WpYoV5x9WDRzjLwtTpP2su6FZ1pFcxg$>)))

  *

     *
- sea beach<https://urldefense.com/v3/__https://ontobee.org/ontology/ENVO?iri=http:**Apurl.obolibrary.org*obo*ENVO_00000092__;Ly8vLw!!JYXjzlvb!lNf0RtlWVQC0B7NclX2lZwPdetO21qdA-b7JUGYwExobwa7Rlm8WpYoV5x9WDRzjLwtTpP2su6HMK2ot8w$>
     *
+ raised beach<https://urldefense.com/v3/__https://ontobee.org/ontology/ENVO?iri=http:**Apurl.obolibrary.org*obo*ENVO_00000415__;Ly8vLw!!JYXjzlvb!lNf0RtlWVQC0B7NclX2lZwPdetO21qdA-b7JUGYwExobwa7Rlm8WpYoV5x9WDRzjLwtTpP2su6F4nIyOwQ$>
     *
- shingle beach<https://urldefense.com/v3/__https://ontobee.org/ontology/ENVO?iri=http:**Apurl.obolibrary.org*obo*ENVO_00000545__;Ly8vLw!!JYXjzlvb!lNf0RtlWVQC0B7NclX2lZwPdetO21qdA-b7JUGYwExobwa7Rlm8WpYoV5x9WDRzjLwtTpP2su6EX5FXBqg$>
     *
- sandy beach<https://urldefense.com/v3/__https://ontobee.org/ontology/ENVO?iri=http:**Apurl.obolibrary.org*obo*ENVO_00002199__;Ly8vLw!!JYXjzlvb!lNf0RtlWVQC0B7NclX2lZwPdetO21qdA-b7JUGYwExobwa7Rlm8WpYoV5x9WDRzjLwtTpP2su6H3uaPWSg$>
     *
- lacustrine beach<https://urldefense.com/v3/__https://ontobee.org/ontology/ENVO?iri=http:**Apurl.obolibrary.org*obo*ENVO_00000093__;Ly8vLw!!JYXjzlvb!lNf0RtlWVQC0B7NclX2lZwPdetO21qdA-b7JUGYwExobwa7Rlm8WpYoV5x9WDRzjLwtTpP2su6HQgBl7lQ$>  A beach which is part of a lake shore.

CMECS

Beach (Levels 1 & 2) – A gently sloping zone formed by unconsolidated material at the shoreline, typically with a concave profile. This zone extends landward from the low-water line to either (a) the place where there is a definite change in material or physiographic form (such as a cliff) or (b) the line of permanent vegetation. Only those portions of the beach within the splash zone would be within the CMECS system; areas of the beach further inland are terrestrial systems.

Sub-types - Barrier Beach, Mainland Beach, Pocket Beach, Tide-Modified Beach, Tide-Dominated Beach and Wave-Dominated Beach

Gary Berg-Cross
Potomac, MD
240-426-0770

On Wed, Mar 20, 2024 at 8:10 AM Gary Berg-Cross <gbergcross at gmail.com<mailto:gbergcross at gmail.com>> wrote:
Below is info for this Wednesday's  2 hour session.
We decided to try having only one meeting a month for the cluster and this one will start an hour later (at 3 Eastern rather than 2)  to
allow Brandon to participate. since the idea is  to start harmonizing CMECS with ENVO and SWEET.  By moving our Semantic Harmonization meeting to the 3rd week of March we will overlap with the SWEET meeting which takes place at 4 eastern time.
 Kate should have some ideas on core items from CMECS  to consider.
Here is some context from last month's meeting:

Brandon was able to attend the Feb. meeting and we looked at his spreadsheet mapping some  CMECS  terms to SWEET.

SWEET -> CMECS matches - Google Sheets<https://urldefense.com/v3/__https://docs.google.com/spreadsheets/d/1r34bzoIv8U3Zu5TMWHBaX8SSMx-u64pKRali-p279Pk/edit*gid=0__;Iw!!JYXjzlvb!lNf0RtlWVQC0B7NclX2lZwPdetO21qdA-b7JUGYwExobwa7Rlm8WpYoV5x9WDRzjLwtTpP2su6GpYIfdcg$>

Some of the conversation about this is in the text below

We also talked about the simple problems with alignment to SWEET, which lacks enough of the concepts that ENVO has.

 And so we looked there too to see some placements and recognized that there would be quite a bit of development in ENVO based on CMECS under the habitat concept.

We hope that , Pier might take a look at this and help us develop a way forward aligning  CMECS   on the one hand to SWEET and also to the more difficult concepts in ENVO

 Brandon  may have  developed more spreadsheets for this meeting and Kate will be looking at her terminologies.

A question was whether Pier would be able to attend this meeting to facilitate moving forward on the mapping of  CMECS.

Meeting ID853 4485 3594
 Invite Link https://esipfed-org.zoom.us/j/85344853594?pwd=cENuRUY1QW4wTDk2Z212K3cxSUVUQT09<https://urldefense.com/v3/__https://esipfed-org.zoom.us/j/85344853594?pwd=cENuRUY1QW4wTDk2Z212K3cxSUVUQT09__;!!JYXjzlvb!lNf0RtlWVQC0B7NclX2lZwPdetO21qdA-b7JUGYwExobwa7Rlm8WpYoV5x9WDRzjLwtTpP2su6G-gZZQjg$>
  https://esipfed-org.zoom.us/j/85344853594?pwd=cENuRUY1QW4wTDk2Z212K3cxSUVUQT09<https://urldefense.com/v3/__https://esipfed-org.zoom.us/j/85344853594?pwd=cENuRUY1QW4wTDk2Z212K3cxSUVUQT09__;!!JYXjzlvb!lNf0RtlWVQC0B7NclX2lZwPdetO21qdA-b7JUGYwExobwa7Rlm8WpYoV5x9WDRzjLwtTpP2su6G-gZZQjg$>

Gary Berg-Cross
Potomac, MD
240-426-0770

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.esipfed.org/pipermail/esip-semanticharmonization/attachments/20240403/4494ca4b/attachment-0001.htm>