NTR: 'is contact information for' #778
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
and dependencies.
jmwhorton
changed the title
cthoyt
reviewed
Jan 8, 2024
wdduncan
previously approved these changes
Jan 16, 2024
|
There was consensus in #653 to add cc @cmungall @balhoff @bpeters42 @jamesaoverton @nataled @addiehl @matentzn |
|
From the perspective of 'is contact information for", "is about" having an
RO id does not create an issue for me.
I do agree that there might be concerned about changing the id of "is
about". Would this change be coordinate with IAO or OBI to ensure we don't
end up with two "is about" object properties in the OBO Foundry?
Best,
Mathias
…On Tue, Mar 26, 2024 at 12:03 PM Bill Duncan ***@***.***> wrote:
is contact information is a subproperty of is about
<http://purl.obolibrary.org/obo/IAO_0000136>. However, is about is not
included in RO.
There was consensus
<#653 (comment)>
in #653 <#653> to add is
about, but to give it an RO id. @mbrochhausen
<https://github.com/mbrochhausen> would a different cause issues for you?
I am concerned about having a different IRI for such a widely used relation.
cc @cmungall <https://github.com/cmungall> @balhoff
<https://github.com/balhoff> @bpeters42 <https://github.com/bpeters42>
@jamesaoverton <https://github.com/jamesaoverton> @nataled
<https://github.com/nataled> @addiehl <https://github.com/addiehl>
@matentzn <https://github.com/matentzn>
—
Reply to this email directly, view it on GitHub
<#778 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACF6DLTZN522WERNQ44ZL3TY2GS6BAVCNFSM6AAAAABBHAN6NGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRQHE4TONZQGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
This PR has not seen any activity in 90 days and has been marked as stale. If it is no longer needed, please close the PR. Otherwise, please update the PR with a status update. |
|
Hi, can someone in the RO community please let me know, what I can or need to do to move this forward. Thx |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Addresses issue #713