Hierarchy issues?     
Comment submitted by whetzel about 1 year ago on Unknown or Deprecated Class in Adverse Event Reporting ontology
Is the term adverse event intended to be a root level term?
 
Responses    hide all | show all
 
Adverse event is a defined class by mcourtot@gmail.com 12 months ago
It is a defined class. Running a reasoner would infer it at its proper position in the hierarchy. I know that there was a request earlier this morning on the IAO list for that to be supported by BioPortal; is that an option? Alternatively, I'll update this version to be the inferred one. Thanks, Melanie ps: is there a way to get automatic notification, maybe via email, when someone leaves a note on your project? I had missed your comment.

Add Note

Comment Propose New Term Propose Relationship Change Propose Property Value Change

Comment

* required
Subject *

Body *

Preferred name *

Synonyms (comma-separated list)

Definition *

Parent (start typing to autocomplete) *

Contact information (publically visible)

New Term

* required
Reason for change *

New relationship target (start typing to autocomplete) *

Old relationship target (start typing to autocomplete)

New relationship type *

Contact information (publically visible)

New Relationship / Change Hierarchy

* required
Reason for change *

New property value *

Property id *

Old property value

Contact information (publically visible)

Change Property Value

* required
Reason for change *

Please login to submit notes with your user (to submit anonymously, fill in the CAPTCHA)

Add Note

Comment Propose New Term Propose Relationship Change Propose Property Value Change

Comment

* required
Subject *

Body *

Preferred name *

Synonyms (comma-separated list)

Definition *

Parent (start typing to autocomplete) *

Contact information (publically visible)

New Term

* required
Reason for change *

New relationship target (start typing to autocomplete) *

Old relationship target (start typing to autocomplete)

New relationship type *

Contact information (publically visible)

New Relationship / Change Hierarchy

* required
Reason for change *

New property value *

Property id *

Old property value

Contact information (publically visible)

Change Property Value

* required
Reason for change *

Please login to submit notes with your user (to submit anonymously, fill in the CAPTCHA)