Skip to content
This repository has been archived by the owner on Mar 7, 2020. It is now read-only.

Write SOP for merging/moving GOREL relations to RO #4

Open
dosumis opened this issue May 13, 2015 · 1 comment
Open

Write SOP for merging/moving GOREL relations to RO #4

dosumis opened this issue May 13, 2015 · 1 comment
Assignees

Comments

@dosumis
Copy link
Contributor

dosumis commented May 13, 2015

In a merge or a move, we need some way to maintain the GOREL URI - should this be as an alt_id in gorel.owl or as an obsolete object property in gorel.owl?

For a merge to work, we need to be able to reliably track on the shorthand (old style OBO relation ID). This will not be possible if the RO relation has a shorthand that is already in use in AE. @cmungall - any suggestions for the latter case?

Timings: For a move, the RO relation will need to be added first. Then once it shows up in the import in go-rel.edit, the URI of the existing relation can be changed to the new RO one.

@dosumis dosumis self-assigned this May 13, 2015
@dosumis
Copy link
Contributor Author

dosumis commented May 13, 2015

This is more problematic than I though: at least under some circumstances, the obo id is being automatically generated from the label!

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

No branches or pull requests

1 participant