Skip to content
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

Open
wdduncan opened this issue Nov 21, 2019 · 9 comments
Open

exposure event is a process #58

wdduncan opened this issue Nov 21, 2019 · 9 comments
Assignees

Comments

@wdduncan
Copy link
Member

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.

@diatomsRcool
Copy link
Contributor

exposure event is already a process, inherited from ExO.

@wdduncan
Copy link
Member Author

In the ecto.owl file, exposure event (ExO_0000002) is a top level term. There is also an exposure event or process (RO_0002310) under process (BFO_0000015).

So, I am unsure what you mean by exposure event is already a process, inherited from ExO.

@matentzn
Copy link
Contributor

@wdduncan is right, I dont think it is actually aligned right now.. Again a case for EXO.

@diatomsRcool
Copy link
Contributor

See CTDbase/exposure-ontology#10
If they don't respond in one week, contact directly.

@wdduncan
Copy link
Member Author

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.

@matentzn
Copy link
Contributor

matentzn commented Apr 6, 2022

@wdduncan
Copy link
Member Author

wdduncan commented Apr 6, 2022

Update after meeting:
Options:

  1. remove the RO class exposure event or process
  2. make exposure event a subclass of exposure event or process
  3. ask RO to change label of exposure event or process to be exposure event
  4. just use the RO class exposure event or process and create an alternate label (or skos:prefLabel) exposure event

#4 seems to be the easiest, but we need others to weigh in.

Ideally, we should also try to get exposure event into COB.

@wdduncan will make ticket on RO.

@wdduncan
Copy link
Member Author

wdduncan commented Apr 6, 2022

I have submitted a ticket to RO to change the label of RO's exposure event or process to exposure event.

See oborel/obo-relations#599

@wdduncan
Copy link
Member Author

wdduncan commented Apr 6, 2022

Also submitted a ticket to COB.

OBOFoundry/COB#192

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants