Comments (9)
Maybe we can make 'plant secondary metabolite' a subclass of plant metabolite CHEBI:76924, hence the definition would be:
A plant metabolite [CHEBI:76924] that is not essential for growth or division of plant cells.
from cdno.
Hey @kaiiam, I would like to know your opinion on this please, it's related to the role in CHEBI again.
One of the roles from CHEBI, the term 'secondary metabolite' [CHEBI:26619] doesn't appear in CHEBI webpage but it appears in [OLS].
And in CHEBI webpage, the term 'plant metabolite' [CHEBI:76924] has synonym 'plant secondary metabolites'
It's a bit confusing, but I think we could use 'secondary metabolite' [CHEBI:26619] from OLS
Where the definition is:
"A metabolite that is not directly involved in the normal growth, development or reproduction of an organism".
Or create 'create secondary metabolite' in CDNO.
from cdno.
Interesting @LilyAndres the above links are not from CHEBI but is instead from CHIRO https://github.com/obophenotype/chiro the chebi integrated role ontology, looks like attempts by Chris Mungall and others to connect CHEBI roles more explicitly to other OBO ontologies. I didn't know about CHIRO. Looks like they grabbed everything under role from chebi and are trying to fix/align them with other ontologies.
The CHIRO term 'secondary metabolite' [CHEBI:26619] redirects to the chebi term CHEBI:25212 - metabolite with CHEBI:26619 as a secondary ID. And as you say CHEBI:76924 - plant metabolite has syn plant secondary metabolites
. Both classes are under role. You'd think that a new term plant secondary metabolite
should be subclass to plant metabolite.
Chebi's metabolite has the def:
Any intermediate or product resulting from metabolism. The term 'metabolite' subsumes the classes commonly known as primary and secondary metabolites.
I have no idea why CHRIO has CHEBI:26619 but CHEBI doesn't, however, maybe the thing to do for now for our purposes is to ask to add or yourself add to CHEBI the term plant secondary metabolite
as subclass to CHEBI plant metabolite.
from cdno.
Ok, so I have an idea. It has been highlighted that the secondary metabolites are also called 'specialized metabolites' (1), (2), (3), (4), (5)
If we use this term I can have it ready in CHEBI in a few minutes, being a subclass of 'eukaryotic metabolite' [CHEBI:75763].
This will help in defining a term that has some problems in CHEBI...
from cdno.
CHEBI:75763 is eukaryotic metabolite, which has as subclass plant metabolite. My suggestion is to make the term plant secondary metabolite
as subclass to plant metabolite. That fits with my understanding of the theory you're describing.
from cdno.
Ok, so if it's okay I think it could be of value to have this term in CDNO rather than CHEBI. Adnan has expressed that
"terms used interchangeably in nutrition science will lead to more confusion among CHEBI users since ChEBI is a chemistry database and the introduction of additional terms will make the ChEBI ontology more complex for their users who come from various domains" (email).
So I suggest we create it in CDNO and later if they think it's necessary in CHEBI, they can take it.
If this is ok then we will have the label plant secondary metabolite
with the synonym secondary metabolite
and the definition:
A plant metabolite [CHEBI:76924] that is not essential for growth or division of plant cells.
from cdno.
Sounds reasonable, were just trying to uphold OBO principal 5 aka reuse other OBO domain ontologies and don't reinvent the wheel. In this case since Adan said CHEBI might not be appropriate then it should be a nutrition ontology and as far as I know CDNO is the first in OBO (but don't quote me on that and we should double check that). Thus if they want to re-direct terms to a nutrition ontology its in scope for us to pick them up. Sorting this out more generally (aka all chebi terms which should be in a nutrition ontology) is probably a larger overall issue which we might not be able to solve in the short term but we should keep this in mind moving forward.
@LilyAndres your plan for plant secondary metabolite
sounds good for now I'd say go for it!
from cdno.
Great, thanks @kaiiam.
Yes, as we have discussed before, CDNO could evolve to be DNO integrating all those terms that might not fit in CHEBI. The nutrition ontologies that exist in OBO are the Ontology for Nutritional Epidemiology (ONE), Ontology for Nutritional Studies (ONS) and Food-Biomarker Ontology (FOBI), but they have a very simple and inconsistent classification of dietary nutritional components. So, at the moment CDNO would be managing this domain, but maybe it can evolve to DNO including other nutritional components derived from other kingdoms and not only from plants.
I moved the definition of 'plant secondary metabolite' and made the changes in the ROBOT template. I will close this issue now, thanks for all the feedback and help with the creation of the terms :)
from cdno.
Great!
from cdno.
Related Issues (20)
- Error in the design pattern during the release HOT 12
- version IRI in OLS does not resolve HOT 14
- duplicate terms under different ids now under 'concentration of' HOT 18
- xrefs are malformed - CURIEs should not have space after the colon HOT 1
- Multiple labels for ChEBI chemicals HOT 13
- Update CDNO/tooling to lastest owl API HOT 7
- Add term deprication/obsolete template HOT 2
- Create CDNO annotation documentation HOT 2
- Lignin should be a subclass of insoluble fibre? HOT 3
- Addition of dietary energy and related terms to CDNO HOT 1
- protein class suggested updates HOT 1
- floating term at top level PR_000000001 HOT 1
- Update USDA compoent prefix in mappings HOT 3
- CDNO Ontology Description missing from OLS HOT 1
- Suggestion to update template for consistency HOT 1
- Suggestion to import vitamin (role) from ChEBI
- Change parent terms for amino acid HOT 1
- Synonyms in nutritional_components_framework.csv template overriding imported synonyms HOT 1
- CDNO has some CHEBI terms with right bracket hidden in URI HOT 9
- Dietary Fiber Ontology Working Group: Fiber term updates HOT 6
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
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.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cdno.