-
Notifications
You must be signed in to change notification settings - Fork 18
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.
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
exposure event is a process #58
Comments
exposure event is already a process, inherited from ExO. |
In the ecto.owl file, So, I am unsure what you mean by |
@wdduncan is right, I dont think it is actually aligned right now.. Again a case for EXO. |
See CTDbase/exposure-ontology#10 |
This issue hasn't been discussed in while. Since we discussed taking over ExO and/or using COB as the top-level ontology, perhaps we should revisit this. |
Update after meeting:
#4 seems to be the easiest, but we need others to weigh in. Ideally, we should also try to get @wdduncan will make ticket on RO. |
I have submitted a ticket to RO to change the label of RO's |
Also submitted a ticket to COB. |
To align with BFO / OBO core, exposure event should be a subtype of BFO:process (see #57).
In
ecto.owl (http://purl.obolibrary.org/obo/ecto/releases/2019-09-20/ecto.owl)
, exposure event is a top level term.The text was updated successfully, but these errors were encountered: