Skip to content

Update fp-007-relations.md #2696

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.

Sign up for GitHub

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

Closed
nataled wants to merge 2 commits into from
Closed

Update fp-007-relations.md #2696

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c9fddd2
Update fp-007-relations.md
nataled Apr 8, 2025
4102b03
Merge branch 'master' into nataled-patch-2
nataled Apr 8, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 19 additions & 1 deletion principles/fp-007-relations.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,8 +30,26 @@ submitted to the [RO tracker](https://github.com/oborel/obo-relations/issues).

Reuse means that the actual relations PURLs are used. Ontology developers should be aware that RO relations (in rare instances) can evolve over time and previous relations might become obsolete. This means developers should monitor the state of the RO relations they use.

- If the domain of the proposed relation is a class in the same ontology as that relation, it is fine to keep in the ontology; if a suitable RO parent exists, the new relation MUST be declared a sub-property of that parent.
- If the domain of the proposed relation is a class outside of the ontology defining that relation, the relation MUST be added to RO.
- If the relation seems generally usable (that is, could potentially be used by other ontologies), the relation MUST be added to RO.
- If there are any doubts about how to proceed based on the above, there SHOULD be an attempt to add to RO.
- It is never a bad idea to add to RO, even for those relations that are 'self-contained' (as described in the first bullet point).

Note regarding property chains: If a proposed property chain makes use of relations that are themselves in RO, the property chain SHOULD be submitted to RO.

## Examples

## Counter-Examples

<Category:Principles> <Category:Accepted> <Category:Definitions>
## Criteria for Review

Each definition MUST be unique. Each entity MUST NOT have more than one textual definition (tagged using [IAO:0000115](http://purl.obolibrary.org/obo/IAO_0000115)). Textual definitions SHOULD be provided for most terms, and for top level terms especially.

[This check is automatically validated.](checks/fp_007)

## Feedback and Discussion

To suggest revisions or begin a discussion pertaining to this principle, please [create an issue on GitHub](https://github.com/OBOFoundry/OBOFoundry.github.io/issues/new?labels=attn%3A+Editorial+WG,principles&title=Principle+%237+%22Relations%22+%3CENTER+ISSUE+TITLE%3E).

To suggest revisions or begin a discussion pertaining to the automated validation of this principle, please [create an issue on GitHub](https://github.com/OBOFoundry/OBOFoundry.github.io/issues/new?labels=attn%3A+Technical+WG,automated+validation+of+principles&title=Principle+%237+%22Relations%22+-+automated+validation+%3CENTER+ISSUE+TITLE%3E).