forked from hdietze/protege-obo-plugins
-
Notifications
You must be signed in to change notification settings - Fork 1
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
Extend obsoletion action to allow replaced_by and support OBO merge semantics #7
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From @cmungall on May 19, 2015 15:22
The obsolete action current adds the
owl:deprecated
axiom and removes logical axioms, as well as label prefixing to get around the protege rendering bug, all good.We would also like a way to easily add
consider
orreplaced_by
annotations. This is not too painful in the annotation editor, but OE users are used to doing this with a drag. No idea how easy this...Another useful feature would be support OBO merge semantics. This means adding an annotation
i.e. 'has obsolescence reason' = 'terms merged'
to the class. In combination with a replaced_by, this will generate an alt_id in OBOF, as specced here:
owlcs/owlapi#317 (comment)
This may be best served by a different action, "Obsolete term for merge" that adds the merge annotation, but leaves it to the user to specify replaced_by?
@balhoff sorry to invade your github repo, we're not presupposing you will do this, I just wanted a place to track this, and your plugin seems the best start
Copied from original issue: balhoff/obo-actions#1
The text was updated successfully, but these errors were encountered: