Git Product home page Git Product logo

planarian-phenotype-ontology's Introduction

Build Status

Planarian Phenotype Ontology (PLANP)

This ontology is a collection of phenotypes observed in the planarian Schmidtea mediterranea. The majority of these phenotypes are likely relevant to other species of planarians.

Versions

Stable release versions

The latest version of the ontology can always be found at:

http://purl.obolibrary.org/obo/planp.owl

Editors' version

Editors of this ontology should use the edit version, src/ontology/planp-edit.owl

Contact

Please use this GitHub repository's Issue tracker to request new terms/classes or report errors or specific concerns related to the ontology.

Acknowledgements

This ontology repository was created using the ontology starter kit

planarian-phenotype-ontology's People

Contributors

matentzn avatar srobb1 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

planarian-phenotype-ontology's Issues

How to find all abnormal parts of the visual system?

I have imported the planarian anatomy ontology into PLANP.

When I do a DLQuery for finding all anatomical terms that are part of the visual system I get this:
Query: 'part of' some 'visual system
Results:
'commissural neuron'
'optic chiasma'
'optic cup'
'photoreceptor neuron'
'pigment cup cell'
'trail cell'
eye
owl:Nothing

This looks good.

Using a pattern I generated new terms for each term in PLANA:
text: "'has_part' some ('quality' and ('inheres_in' some %s) and ('qualifier' some 'abnormal'))"

When I query for: ('has part' some ('inheres in' some 'visual system'))
I get nothing.

I would like to find:
'abnormal optic cup', ‘abnormal eye’, etc. but I do not. I only get back 'abnormal visual system'.

When I query for: ('part of' some ('inheres in' some 'visual system'))
I get nothing

How do I need to change my anatomy ontology to get this back? Should I be using ‘has part’ instead of ‘part of’ relationships? Or what am I doing wrong.

ventralized dorsalized anterioralized posterioralized animals

Here is what I am thinking about for ventralized/dorsalized/anterioralized/posterioralized animals. Does this look right to everyone?

  • abnormal dorsal surface
    • ventralized (PATO_0030003) dorsal surface is ventralized
  • abnormal ventral surface
    • dorsalized (PATO_0030001) ventral surface is dorsalized
  • abnormal posterior region (or is surface better ??)
    • anterioralized (PATO_0030000) posterior region is anterioralized?
  • abnormal anterior region (or is surface better ??)
    • posterioralized (PATO_0030002) anterior region is posterioralized?

Refresh PLANA import and make a new release

There are currently a number of empty synonyms in PLANP which come from an old version of PLANA. Would it be possible to make a new PLANA release, then refresh the PLANA import (ideal all imports) in PLANP and then make a new PLANP release? :)

Thank you!

terms to add

  • total loss of anatomical entity due to degeneration
  • abnormal motility of whole organism
  • decreased motility of whole organism
  • presence of edema MP:edema
  • inch worm like movement
  • head/tail pinching. hourglass-shaped head/tail? does this work?
  • pinching along lateral epithelium
  • epithelial ruffles
  • bullet hole =? loss of pharynx
  • patchy pigmentation. similar pattern to increased/decreased pigmentation? NTR?
  • increased fission rate
  • scrunched animal?
  • animal with extremely visible central nervous system
  • animal and tissue lysis

Avoid redefining terms in external ontologies

To ensure interoperability between different ontologies, terms in external ontologies such as GO should not be re-defined. For example:

<owl:Class rdf:about="http://purl.obolibrary.org/obo/GO_0007006">
        <owl:equivalentClass>
            <owl:Class>
                <owl:intersectionOf rdf:parseType="Collection">
                    <rdf:Description rdf:about="http://purl.obolibrary.org/obo/GO_0061024"/>
                    <owl:Restriction>
                        <owl:onProperty rdf:resource="http://purl.obolibrary.org/obo/BFO_0000066"/>
                        <owl:someValuesFrom rdf:resource="http://purl.obolibrary.org/obo/PLANA_0007512"/>
                    </owl:Restriction>
                </owl:intersectionOf>
            </owl:Class>
        </owl:equivalentClass>
        <rdfs:subClassOf rdf:resource="http://purl.obolibrary.org/obo/GO_0007005"/>
        <rdfs:subClassOf rdf:resource="http://purl.obolibrary.org/obo/GO_0061024"/>
        <rdfs:subClassOf>
            <owl:Restriction>
                <owl:onProperty rdf:resource="http://purl.obolibrary.org/obo/BFO_0000066"/>
                <owl:someValuesFrom rdf:resource="http://purl.obolibrary.org/obo/PLANA_0007512"/>
            </owl:Restriction>
        </rdfs:subClassOf>
        <obo:IAO_0000115 rdf:datatype="http://www.w3.org/2001/XMLSchema#string">A process that is carried out at the cellular level which results in the assembly, arrangement of constituent parts, or disassembly of a mitochondrial membrane, either of the lipid bilayer surrounding a mitochondrion.</obo:IAO_0000115>
        <oboInOwl:hasExactSynonym rdf:datatype="http://www.w3.org/2001/XMLSchema#string">mitochondrial membrane organisation</oboInOwl:hasExactSynonym>
        <oboInOwl:hasOBONamespace rdf:datatype="http://www.w3.org/2001/XMLSchema#string">biological_process</oboInOwl:hasOBONamespace>
        <oboInOwl:hasRelatedSynonym rdf:datatype="http://www.w3.org/2001/XMLSchema#string">mitochondrial membrane organization and biogenesis</oboInOwl:hasRelatedSynonym>
        <oboInOwl:id rdf:datatype="http://www.w3.org/2001/XMLSchema#string">GO:0007006</oboInOwl:id>
        <rdfs:label rdf:datatype="http://www.w3.org/2001/XMLSchema#string">mitochondrial membrane organization</rdfs:label>
    </owl:Class>

You basically re-define a GO term in terms of some PLANA concepts. If you do that, then all ontologies that will use PLANP (such as Upheno, one day!) will inherit that re-definition; with potentially far reaching consequences.

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.