[Esip-semanticharmonization] [EXT]Re: SKOS problem, Re: Reminder to join Wednesday's (2/16/2022 2-3 Eastern US, 6-7 UTC) ESIP Semantic Harmonization

[Kai Blumberg]

In the SSSOM example see the readme on this page
<https://github.com/mapping-commons/SSSOM/> they set the table column up as
*subject_id*,* predicate_id*,* object_i* where subject is the first
ontology, predicate is the match type and object is the 2nd ontology. So
I'm guessing we can follow that for the order of the mapping. For example
the way we have it currently setup, the subject is ENVO and object is
SWEET. So if we were to for a given mapping say the match type is broader
following your above logic we'd be saying the SWEET term is broader than
the ENVO term.

I hope we're on the same page, let me know if we're not.
Cheers,
Kai

On Wed, Feb 16, 2022 at 11:57 PM Ruth Duerr <ruth.duerr3 at gmail.com> wrote:

> *External Email*
> You know Nancy this is exactly why I brought the question up during the
> meeting.  It is VERY confusing!!!  But I think (crossing-my-fingers) you
> have it correctly.
>
> Ruth
>
> PS: Your message did actually go through via the email list, so I did get
> it twice….
>
> On Feb 16, 2022, at 3:18 PM, Nancy Wiegand <wiegand at cs.wisc.edu> wrote:
>
> I can't send to the group, so I'm forwarding to just the 4 of you. I'm
> sorry if I screwed things up. It is confusing.
>
> Nancy
> -------- Forwarded Message --------
> Subject: SKOS problem, Re: Reminder to join Wednesday's (2/16/2022 2-3
> Eastern US, 6-7 UTC) ESIP Semantic Harmonization
> Date: Wed, 16 Feb 2022 16:15:48 -0600
> From: Nancy Wiegand <wiegand at cs.wisc.edu> <wiegand at cs.wisc.edu>
> To: gbergcross at gmail.com, Ruth Duerr <ruth.duerr3 at gmail.com>
> <ruth.duerr3 at gmail.com>, Pier Buttigieg <pbuttigi at mpi-bremen.de>
> <pbuttigi at mpi-bremen.de>, Mark Schildhauer <schild at nceas.ucsb.edu>
> <schild at nceas.ucsb.edu>, Brandon Whitehead <brandon.p.whitehead at gmail.com>
> <brandon.p.whitehead at gmail.com>, Kai Blumberg <kblumber at mpi-bremen.de>
> <kblumber at mpi-bremen.de>, Kate Rose <Kate.rose at noaa.gov>
> <Kate.rose at noaa.gov>
> CC: Simon Cox <Simon.Cox at csiro.au> <Simon.Cox at csiro.au>, Charlesl.lm8ms
> F. Vardeman II <charles.vardeman at gmail.com> <charles.vardeman at gmail.com>,
> Robert rovetto <ontologos at yahoo.com> <ontologos at yahoo.com>, Megan Carter
> <megancarter at esipfed.org> <megancarter at esipfed.org>,
> Esip-semanticharmonization <esip-semanticharmonization at lists.esipfed.org>
> <esip-semanticharmonization at lists.esipfed.org>, Lewis John McGibbney
> Ph.D., B.Sc. <lewis.j.mcgibbney at jpl.nasa.gov>
> <lewis.j.mcgibbney at jpl.nasa.gov>, Anne Thessen <annethessen at gmail.com>
> <annethessen at gmail.com>, Lindsay Barbieri <barbieri at esipfed.org>
> <barbieri at esipfed.org>, cverhey at oceannetworks.ca, Nancy Wiegand
> <wiegand at cs.wisc.edu> <wiegand at cs.wisc.edu>
>
> I might have the wrong direction regarding SKOS. At least it says (in
> https://www.w3.org/TR/skos-primer/#secrel):
>
> *"Note on skos:broader direction:* for historic reasons, the name of the
> skos:broader property (the word "broader") does not provide an explicit
> indication of its direction. The word "broader" should read here as "has
> broader concept"; the subject of a skos:broader statement is the more
> specific concept involved in the assertion and its object is the more
> generic one."
>
> and:
>
> ex:mammals rdf:type skos:Concept;
>   skos:prefLabel "mammals"@en;
>   skos:broader ex:animals.
>
> So, top to bottom, apparently the above would read as mammals 'has broader concept animals'. So, if our
>  spreadsheet is read left to right, and if we consider left is top and right is bottom, then it would be:
> mammals  animals  broader
> This would read as 'mammals has broader concept animals'. But, I don't know. Since it's our own spreadsheet,
> maybe we could do it either way, although top=left and bottom=right probably is more similar.
>
> Anyone know for sure?
>
> Nancy
>
>
> On 2/15/2022 11:27 AM, gbergcross at gmail.com wrote:
>
>
>  Our next Semantic Harmonization 1 hour session is tomorrow. The usual
> agenda for the 1 hour session is
>  to work on actual harmonization.  There is an opportunity discussed on
> Monday (Brandon, Kate, Pier and Gary) from the Marine domain.
> There is some thought of updates for Coastal and Marine Ecological
> Classification Standard (CMECS
> <https://iocm.noaa.gov/standards/cmecs-home.html>) - a "structured
> catalog of ecological terms that also provides a framework for
> interpreting, classifying, and inter-relating observational data from all
> types of sensors and platforms. "
>
>  Alignment with SWEET and ENVO is of interest starting with using SKOS to
> enhance the vocabularies.
> We can discuss what role SH might play in this.
>
> Zoom Meeting Info
>> https://us02web.zoom.us/j/85344853594?pwd=cENuRUY1QW4wTDk2Z212K3cxSUVUQT09
>> Meeting ID: 853 4485 3594
>> Passcode: 532583
>>
>> One tap mobile
>> +13017158592,,85344853594# US (Washington DC) etc....
>>
>> Gary Berg-Cross
>> Potomac, MD
>> 240-426-0770
>>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.esipfed.org/pipermail/esip-semanticharmonization/attachments/20220217/b6a2eac9/attachment-0001.htm>