Closed wdduncan closed 2 months ago
I have no objection but this should be taken to the main stakeholders of this relation, which would include OBI. I am not sure who else uses these abstract relations.
Discussed in OBI call 1/9/2023. Relaxing the domain from 'specifically dependent continuant' only to add 'process' should be okay from OBI's point of view.
@anitacaron @matentzn I opened a new branch for this issue (branch issue-650
). After I made my changes, it reverted the license annotation back to http://purl.org/dc/elements/1.1/license
:
- <!-- http://purl.org/dc/terms/license -->
+ <!-- http://purl.org/dc/elements/1.1/license -->
- <owl:AnnotationProperty rdf:about="http://purl.org/dc/terms/license"/>
+ <owl:AnnotationProperty rdf:about="http://purl.org/dc/elements/1.1/license"/>
Any ideas why?
I commented in the PR.
Summarizing from RO call today.
I'm going to rewrite the original ask more precisely: the goal is to relax the domain to change it from SDC to a union SDC or biological process
, to be consistent with BFO (http://purl.obolibrary.org/obo/BFO_0000059 -- simply "concretizes" in http://purl.obolibrary.org/obo/bfo/2020/bfo-core.owl)
If we do this, then we should:
As an aside, we also noticed that we are manually duplicating annotations for inverses. This is not good practice, it violates DRY. @cmungall will look for documentation on existing practice and what we should do here (refer vs automatically propagate in release file).
In BFO-2020 the domain of
concretizes at some time
isprocess or 'specifically dependent continuant'
. The domain of RO'sconcretizes
should be updated to includeprocess
for sake of consistency.