You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 7, 2020. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: