Open gaurav opened 6 years ago
An alternative would be to use the same formatting at Uberon use in their paper, which is to render OWL terms in fixed-width fonts, to italicize properties and to surround classes and , e.g. 'pulmonary alveolus' SubClassOf
part_of some
'lung'.
We will also want to make the properties into links so that users can look up their definitions.
Sounds like some kind of "expert mode"?
Note that the JSON-LD file produced by the Curation Tool can be opened in Protege and the OWL property restriction viewed there. Protege's display of the definition uses labels instead of term IDs and allows the user to click on individual specifiers. So, implementing this issue only makes sense if we can provide something here that is missing from Protege.
Agreed!
In order to implement reasoning (#3), we will need to produce an OWL property restriction corresponding to each phyloreference in a PHYX file. For the purpose of explaining how phyloreferencing works, it would be useful to allow users to display this OWL expression through the interface. This is also a chance to find the best way to display these expressions: in a previous experiment, we found that italicizing OWL Manchester terms worked well.