Skip to main content

Notice

We are in the process of rolling out a soft launch of the RDA website, which includes a new member platform. Existing RDA members PLEASE REACTIVATE YOUR ACCOUNT using this link: https://rda-login.wicketcloud.com/users/confirmation. Visitors may encounter functionality issues with group pages, navigation, missing content, broken links, etc. As you explore the new site, please provide your feedback using the UserSnap tool on the bottom right corner of each page. Thank you for your understanding and support as we work through all issues as quickly as possible. Stay updated about upcoming features and functionalities: https://www.rd-alliance.org/rda-web-platform-upcoming-features-and-functionalities/

Practical implementations of the I-ADOPT framework and future directions

  • Creator
    Discussion
  • #133963

     
    Collaborative session notes: https://docs.google.com/document/d/1pCBu4mA1vtO-Ig2PTZgynqqnGnN0Sc7DIJvi…
     
    1- Barbara Magagna: Introduction to the meeting objectives and the I-ADOPT framework (5’)
    2- Lightning talks on real case implementations (30’): 3-slides max (4 min each) presenting a) the use case(s)  addressed; b) what worked well; c) what did not work so well
    Current suggestions:

    Gwen Moncoiffé (NOC-BODC, UK): Implementation in the NERC Vocabulary Server

    Alison Pamment (STFC, UK): Implementation with the CF Standard Names

    Veronique Chaffard (IRD, France): Implementation with the Theia/OZCAR thesaurus

    Barbara Magagna (GO-FAIR foundation): Implementation of eLTER Standard Observations in EnvThes

    Robert H (PANGAEA, Germany): Implementation in PANGAEA Terminology Server

    Stuart Chalk (University of North Florida, US): I-Adopt Implemented in the SciData Framework

    Natalia Queiroz de Oliveira (University of Rio de Janeiro, Brazil): Use of Measurement Ontology Pattern Language (M-OPL) in the ontology of the I-ADOPT framework

    3- Future directions: discussion on gaps, integration with other activities, challenges at the interfaces, priorities (55’)

    Additional links to informative material
    Recommendation package DOI: 10.15497/RDA00071 (contains all essential links to the latest up-to-date material)
     

    Avoid conflict with the following group (1)
    Vocabulary Services IG

    Brief introduction describing the activities and scope of the group
    I-ADOPT Working Group was set up to address the lack of a common framework to enable interoperability between diverse terminologies used to represent observable properties/ variables and to provide the necessary level of detail needed for seamless data discovery and integration. In the course of its 18-month workplan, it developed the I-ADOPT Interoperability Framework. The framework is a set of guidelines based on a simple non-domain specific ontology that supports the decomposition of complex observable properties into their essential atomic parts represented through the concepts in FAIR terminologies. The I-ADOPT Interoperability Framework is a substantial contribution to enabling the interoperability of terminologies, within and across domains without sacrificing any prior efforts. It serves as a common layer of abstraction through which concepts from different terminologies can be systematically aligned and extended, as needed. On-going activities are focusing on implemeneting the framework in operational systems in as many diverse infrastructures and disciplines as possible, addressing some of the use cases identified early in the project, and testing the framework in real-life scenarios.

    Group chair serving as contact person
    Gwenaëlle Moncoiffé

    Meeting objectives
    1- Report on progress with real case implementation of the I-ADOPT framework in operational Research Infrastructures and identify opportunities for future development;
    2- Discuss issues faced and invite comments and feedback on the framework and its application;
    3- Explore connections/synergies with other semantic / linked data activities.

    Privacy Policy
    1

Log in to reply.