New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vocabularies / ontologies to support, and framework for linking synonyms #31

Open
dlebauer opened this Issue May 24, 2016 · 18 comments

Comments

Projects
None yet
7 participants
@dlebauer
Member

dlebauer commented May 24, 2016

Vocabularies to support and framework for relating synonyms across vocabularies, enable to search datasets with translation across vocabularies

Vocabularies to support:

Related issues:

See also:

EarthCube GeoSemantics project

@lmarini

@dlebauer dlebauer added the meta-data label Jun 17, 2016

@dlebauer dlebauer added this to the July 2016 milestone Jul 11, 2016

@dlebauer dlebauer added the 1 - Ready label Jul 11, 2016

@craig-willis

This comment has been minimized.

craig-willis commented Jul 14, 2016

As per discussion with @dlebauer, for this task I'll focus on a system to support vocabulary mapping, initially focusing on the listed vocabularies/ontologies. I'll review existing solutions, particularly the EC Geosemantics server, and flesh out requirements. The basic requirement here appears to be a software-based solution and process for mapping these vocabularies where the resulting mapping can be leveraged by existing systems (e.g., BETYdb, cross-database search).

@craig-willis

This comment has been minimized.

craig-willis commented Aug 3, 2016

Spoke with IN-CORE project team at NCSA -- they have evaluated a number of vocabulary servers and seem to have closely aligned needs. Will try to setup a meeting with ECGS and IN-CORE team in the coming week or so to share information and requirements.

@craig-willis

This comment has been minimized.

craig-willis commented Aug 11, 2016

I've been reviewing several services considered by the IN-CORE team for vocabulary management -- iQvoc, TemaTres, LOV, and Skosmos. I've also reached out to the Marine Metadata Interoperability (MMI) project about their ontology registry (http://mmisw.org/orr/). The MMI ORR was selected by the Earth Science Information Partners (ESIP) federation. While MMI ORR is ontology-centric, it is designed specifically for the development of cross vocabulary/ontology mappings.

@craig-willis

This comment has been minimized.

craig-willis commented Aug 15, 2016

@JeffWhiteAZ @chporter @dlebauer

We've discussed one goal of this task as mapping the TERRAref output data and BETYdb to the ICASA vocabulary, possibly hosting a mapping service. Most of the services I've explored so far (ECGS-KIS, MMI ORR, etc) rely on vocabularies or ontologies being represented in standard formats such as OWL or SKOS to take advantage of semantic mapping operations such as owl:sameAs, skos:exactMatch, etc.

From my understanding, the ICASA master variable list is published as a Google spreadsheet. Do you know if there's been any discussion of publishing or rendering this in a more linked-data suitable format? If not, do you see any problems with us doing so for TERRA -- for example, writing an interface to the spreadsheet that publishes the variables via permanent URLs.

@JeffWhiteAZ

This comment has been minimized.

JeffWhiteAZ commented Aug 15, 2016

Craig,
We have had several discussions about "ontologizing" the ICASA master variable list and as a first step, have considered publishing in a more readily viewed and searched format. That work hasn't moved ahead due to lack of funding. I expect Cheryl would support me in saying "yes" to any effort by TERRA to help us move in that direction. Thanks for the offer.
What sort of effort would this require? What approach would you suggest beyond what you outline above?

@craig-willis

This comment has been minimized.

craig-willis commented Aug 15, 2016

Thank you, Jeff. Now that I know you're open to it, I'll put together a few options for discussion this week.

@nfahlgren

This comment has been minimized.

nfahlgren commented Aug 23, 2016

@craig-willis @dlebauer I saw the note about a standard/interchange format for PlantCV, do we want to have that discussion here or a separate issue?

@craig-willis

This comment has been minimized.

craig-willis commented Aug 24, 2016

@nfahlgren I think #18 is the right forum for this. I've added a Google Doc with a rough sketch of my thinking and welcome your feedback.

@craig-willis

This comment has been minimized.

craig-willis commented Aug 24, 2016

@JeffWhiteAZ @chporter @dlebauer

I've added a (rough) document to the computing pipeline folder with some options for creating a linked-data suitable version of the ICASA model.

https://docs.google.com/document/d/1fTcTpKxcanPfRKPC-ZG8KjufGHscx5OCCB-5Ti58ARg/edit?usp=drive_web

Any feedback welcome.

@chporter

This comment has been minimized.

chporter commented Aug 24, 2016

@craig-willis
This is a really nice framing of the issues involved in using the ICASA vocabulary for linked data.
For what we are doing in AgMIP and DSSAT currently, the flat data dictionary is sufficient, but we understand the need for linked data and we want to support the efforts of groups that need that capability. We don't currently have resources to put a lot of effort into making that transition, but we welcome the opportunity to guide those efforts. Can we set up a call between Jeff, Cheryl, and Craig (and anyone else interested) to discuss where to go next?
For a while we had regular Skype calls with Celine Aubert, Elizabeth Arnaud, Medha Devare and others regarding the mapping of ICASA variables to the Crop Ontology and Agronomy Ontology. We may want to consider restarting that effort, including Craig Willis in the conversation.

@craig-willis

This comment has been minimized.

craig-willis commented Aug 25, 2016

Thank you, @chporter. I'll bring this up in our weekly meeting tomorrow and report back.

@craig-willis

This comment has been minimized.

craig-willis commented Aug 26, 2016

@chporter @JeffWhiteAZ
We discussed this at the meeting yesterday and do want to move forward with the effort to put together a RDF or similar version of the ICASA data dictionary and model -- the task will be assigned to me. I'll setup a call to discuss. Thanks for your feedback.

@chporter

This comment has been minimized.

chporter commented Aug 26, 2016

@craig-willis @JeffWhiteAZ
Glad to hear it, Craig.

@craig-willis

This comment has been minimized.

craig-willis commented Sep 23, 2016

Why is this closed? The related work is incomplete.

@dlebauer

This comment has been minimized.

Member

dlebauer commented May 3, 2017

Should we turn this into an epic, close, or ?

There are many subtasks associated with this.

@dlebauer dlebauer modified the milestones: May 2017, February 2017 May 3, 2017

@craig-willis

This comment has been minimized.

craig-willis commented Jun 8, 2017

Late response, but this should probably be an epic.

@dlebauer

This comment has been minimized.

Member

dlebauer commented Jun 22, 2017

@craig-willis could you please update the milestone on this? turn it into an epic if necessary?

@craig-willis craig-willis modified the milestones: July 2017, May 2017 Jun 22, 2017

@dlebauer dlebauer removed this from the July 2017 milestone Apr 18, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment