-
Notifications
You must be signed in to change notification settings - Fork 0
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
Display Crop Ontology following TDv5 format allowing to distinguish the compsoition of a variable. #501
Comments
To address this FR we need to :
To be refine |
For information, this is how it looks on Cropontology.org: |
is this not specific to AgroPortal how to make it generic for ontoportal? @jonquet |
This issue and the TDv5 format is speciifc to AgroPortal. |
Crop Ontology has adopted the TDv5 format for years that represent Variable as a composition of a Trait, a Method and a Scale.
When browsing/searching the ontologies users need to be able to the related variables of a given trait, method or scale ... and the other way arround, they need to see, when browsing a variable, the 3 component of that variable.
If we take C0_356 as an example
For some reason, we have an issue related to OWL parsing that "prevent" the OWL restriction statments to be flatten. So inour case the relation is lost: #499
Assuming this is fixed (i.e., the flatten relation appears), this issue is about improving and customizing the UI for the Crop Ontology (more than 30 resources in AgroPortal and another 10 waiting).
For variable https://agroportal.lirmm.fr/ontologies/CO_356?p=classes&conceptid=https%3A%2F%2Fcropontology.org%2Frdf%2FCO_356%3A1000013
This is how Protégé does
(this assume issue 499 above is completly fixed and we have the RDF restriction)
And the Variable somehow appear under the Trait (or Method or Scale) in the tree:
The desired UI is the one from URGI browser: https://urgi.versailles.inra.fr/ephesis/ephesis/ontologyportal.do
Where for a given Variable (discovered thru the Trait only) one cleary see the Trait, Method and Scale involved.
The text was updated successfully, but these errors were encountered: