Principle #7 relations - automated validation mechanism

[nataled]

Here, we discuss the types of automated checks that could be implemented to see if a particular ontology is meeting principle 7. We consider the use of RO for relations as meeting the objective, even if the RO relation is undefined or poorly defined (not ideal, but better than minting new relations covering the same object property).

Validation of relations:

1. Extract all object properties.
2. Identify any that do not use RO purls: a) Do any share a label with a RO relation? If so, throw an Error b) For those that have no label in common with RO, throw a Warning

The above is a suitable start for ROBOT. However, ideally, for the sake of ontology reviews we'd have the following tagged:

1. RO purl relations used
2. Non-RO relations that share a label with RO (2a above)
3. Non-RO relations that share a label with relations in another ontology
4. Non-RO relations that lack a shared label with relations in any other ontology
5. Non-RO relations in the tested ontology that lack definition in that ontology

Note that while 1, 2, 3, and 4 are mutually exclusive, 5 is not mutually exclusive with 2, 3, or 4.

[nlharris]

What's the status of this? Is this covered by the dashboard checks?

[nataled]

Unsure of the status. The EWG has been going through old tickets at each meeting as time allows. This and related tickets regarding automated validation are for discussion about whether or not the dashboard check is an accurate check for the principle.