oborel / obo-relations

RO is an ontology of relations for use with biological ontologies
http://oborel.github.io/
Other
92 stars 47 forks source link

Ensure metadata fields are populated for inverse properties #51

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 9 years ago
We frequently leave metadata fields unpopulated for inverses, as these 
trivially correspond to their partner. In many cases it would be undesirable to 
manually populate these, because it would lead to maintenance and synchrony 
issues.

Instead it would be useful to auto-populate these, for example:

 * def: The inverse of P
 * alternate term: manually populate (warn if P has more of these than Q)
 * obo unique label: manually populate (warn if present only on P)
 * curator status: copy value from P
 * editor and curator notes: add canned text that says "see notes for P"

This may involve an annotation property that designates a 'primary' 
direction/partner (P or Q), which has no semantic meaning but is used to assist 
in metadata population

Original issue reported on code.google.com by cmung...@gmail.com on 5 Mar 2015 at 3:24

cmungall commented 8 years ago

We can now run sparql/addMetadataForInverse.sparql to periodically populate definitions for inverse properties.

cmungall commented 1 year ago

unfortunately OLS does not show inverses

matentzn commented 1 year ago

The new OLS could; we could make an issue to that end: https://github.com/EBISPOT/ols4/issues