Giter Club home page Giter Club logo

Comments (5)

cmungall avatar cmungall commented on June 5, 2024

@mbrush I believe we were going with correlated_with as the grouping predicate and would allow for various types of correlation contexts, e.g. in the literature

from biolink-model.

mbrush avatar mbrush commented on June 5, 2024

@cmungall I would consider a new relation specific for correlated mentions, which could potentially live under 'correlates_with'. If we use the parent 'correlated_with' for literature-co-occurrence, we may end up with assertions in our KGs about correlations between entities like chemicals and diseases where some describe correlation of the actually entities in biological setting, and others that describe correlated occurrence in the literature. e.g. HER2 and breast cancer may be correlated biologically, and their mentions in the literature may also be correlated. We need to be able to distinguish between these cases.

I might propose a correlated_with sub-property to handle the literature co-occurrence - perhaps something like 'mentions_correlated_with'. Or maybe it doesn't even make to have this be a correlated_with subproperty - as the entities represented by the subject and object of this predicate in a KG (e.g. a variant and disease) don't themselves correlate with each other in the way that the correlated_with predicate is defined (from RO: "A relationship that holds between two entities, where the entities exhibit a statistical dependence relationship. The entities may be statistical variables, or they may be other kinds of entities such as diseases, chemical entities or processes.")

Curious what peoples thoughts are here.

from biolink-model.

nlharris avatar nlharris commented on June 5, 2024

Is this still relevant?

from biolink-model.

sierra-moxon avatar sierra-moxon commented on June 5, 2024

I'm going to assign this to the predicates WG - thanks @nlharris! :)

from biolink-model.

sierra-moxon avatar sierra-moxon commented on June 5, 2024

Right now in the model, @cbizon - we have 'correlated with' (as per @cmungall's proposal above), which specifies namedthing and namedthing as domain/range specifically. There are also several children of correlated with in the model that might address some of @mbrush's concerns. I am going to close this case (please definitely reopen if I missed a use case).

from biolink-model.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.